"Vatra Moldoviței", "Ciumârna" and "Paltinu" villages are listed in the drop-down menu.

Description:
The villages are listed in the drop-down menu alongside its corresponding county and commune, according to the law
Preconditions:
The website (https://peviitor-ro.github.io/ui.orase/) is up and runing. After every step delete the text you typed from the search bar.

Step 1
Write in the search bar "Vatra Moldoviței".

Expected results
The location is listed in the drop-down menu as "Sat Vatra Moldoviței SUCEAVA (Vatra Moldoviței)".

Step 2
Write in the search bar "Ciumârna".

Expected results
The location is listed in the drop-down menu as "Sat Ciumârna SUCEAVA (Vatra Moldoviței)".

**Step 3 **
Write in the search bar "Paltinu".

Expected results
The location is listed in the drop-down menu as "Sat Paltinu SUCEAVA (Vatra Moldoviței)".


Absolute import will cause cranky types

Can you provide more detail? Thanks.

So the problem is specifically for Eden plugin.
For example, if in the tsConfig.json
{
  "compilerOptions": {
     "baseUrl": ".",
     "paths": {
       "@/*": ["./src/*"]
     }
  }
}

Any file that uses absolute import like import { userSchema } from '@/schema/user'.
Will cause edenTreaty to infer the return type as any.
This will cause return type to be any
import { db, user } from '@/drizzle/db';

// ....some other code
.get('/', async () => {
  const sth = await db.select().from(user);
  return sth
})

Note: somehow it only cause this inside the handler that uses the absolute import any other handler works just fine.

Assuming you are using monorepo where you set tsconfig to have absolute import on server.
You have to set the tsconfig.json on client to have the same file reference as server, so basically you have to add:
     "paths": {
       "@/*": ["../../apps/server/src/*"]
     }

Assuming you are using monorepo where you set tsconfig to have absolute import on server.
You have to set the tsconfig.json on client to have the same file reference as server, so basically you have to add:
     "paths": {
       "@/*": ["../../apps/server/src/*"]
     }

Hey there, thanks for the answer. But wouldnt that mess up the import path for the client? since on the client it already has something similar.
"paths": {
  "@/*": ["./src/"]
}

I had the same issue, my ugly hack is to use a different alias, @@ for server and @ for client, then add "@@/*": ["../server/src/*"] to client's tsconfig.


UnknownError: 2 root error(s) found

Hello! Hope your doing great. I just wanted to reproduce the results. Every thing was going smoothly then this error prompted at the end in predict.py file. I am trying this on  Google Colab Details of the error are given below, kindly check.

The code line to which the error points is:

The folders, files and results are inside another folder named as Filess and I have changed the directory to the that too.
Any help would be greatly appreciated. Thanks!

Hi
I think the path of the image is incorrect, that is why the function
cv2.imread is returning NULL value.
Best regards,
Nikhil
On Sun, 6 Dec 2020, 8:49 pm Asif Ahmad Khan<EMAIL_ADDRESS>wrote:

Hello! Hope your doing great. I just wanted to reproduce the results.
Every thing was going smoothly then this error prompted at the end in
predict.py file. I am trying this on Google Colab Details of the error
are given below, kindly check.
[image: error 1]
https://user-images.githubusercontent.com/54246513/101283893-2dd42c80-37ff-11eb-9773-f8c66411056c.PNG
[image: error 2]
https://user-images.githubusercontent.com/54246513/101283904-2f9df000-37ff-11eb-8940-4f26edf79e8d.PNG
The code line to which the error points is:
[image: error 3]
https://user-images.githubusercontent.com/54246513/101283964-7855a900-37ff-11eb-92a8-ecd89624812c.PNG
The folders, files and results are inside another folder named as Filess
and I have changed the directory to the that too.
Any help would be greatly appreciated. Thanks!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/nikhilroxtomar/Polyp-Segmentation-using-UNET-in-TensorFlow-2.0/issues/3,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AECEEMTLCZEXH3HWT4XA7JLSTOOGZANCNFSM4UPMIPZA
.

hello how do you fixed this error

mail me at @.*** @.**>
On Tue, Apr 13, 2021 at 1:51 PM Bel Hadj Slimen Nada <
@.***> wrote:

hello how do you fixed this error
[image: image]
https://user-images.githubusercontent.com/33868302/114525021-075b4d80-9c46-11eb-87ab-ec3075b94d2e.png
[image: image]
https://user-images.githubusercontent.com/33868302/114525154-2823a300-9c46-11eb-9f1a-e6646c562e19.png
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/nikhilroxtomar/Polyp-Segmentation-using-UNET-in-TensorFlow-2.0/issues/3#issuecomment-818567835,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM53Y4MQXPXBPA4ZASCIFWDTIQA2FANCNFSM4UPMIPZA
.

I can't read your email address

hello
thank you for your feedback
Any help would be greatly appreciated.
Le mar. 13 avr. 2021 à 11:03, Asif Ahmad Khan @.***> a
écrit :

mail me at @.*** @.**>
On Tue, Apr 13, 2021 at 1:51 PM Bel Hadj Slimen Nada <
@.***> wrote:

hello how do you fixed this error
[image: image]
<
https://user-images.githubusercontent.com/33868302/114525021-075b4d80-9c46-11eb-87ab-ec3075b94d2e.png
[image: image]
<
https://user-images.githubusercontent.com/33868302/114525154-2823a300-9c46-11eb-9f1a-e6646c562e19.png
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<
https://github.com/nikhilroxtomar/Polyp-Segmentation-using-UNET-in-TensorFlow-2.0/issues/3#issuecomment-818567835
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AM53Y4MQXPXBPA4ZASCIFWDTIQA2FANCNFSM4UPMIPZA
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/nikhilroxtomar/Polyp-Segmentation-using-UNET-in-TensorFlow-2.0/issues/3#issuecomment-818575832,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AICMUDW4275N2WTRGUEXJI3TIQCGZANCNFSM4UPMIPZA
.


Domain verification (walletconnect cloud)

📄 Context
We have a WalletConnect cloud project for the staking app. One pending check is the verification of domain ownership so we can access other features.
✔ Solution
Follow the instructions to allow the third-party service to validate the domain ownership.
📈 Subtasks

[x] implement the instructed steps to make the ownership validation

🎯 Definition of Done

[x] WalletConnect cloud can successfully validate the ownership.

The verification is completed. Listing below screenshots from the ledger live app when trying to establish a connection and the list of sessions.


Add "Resources Used" to Public Images API

What happened?
When I use "GET /api/v1/images" to get the image response, I find the value of model, which can let me know the name of the model used when the image is generated, but it seems to lack the specific ID value corresponding to this model on civitai. Is it possible to add the "Resources Used" association information displayed on the front page? This way you can use the image to return information about the corresponding model ID on civitai.com and then visit the page.
Steps to reproduce the problem
https://github.com/civitai/civitai/wiki/REST-API-Reference#get-apiv1images
What should have happened?
"GET /api/v1/images" should contain the "Resources Used" information when the image is returned.
What platforms do you use to access the site?
Windows
What browsers do you use to access the site?
Microsoft Edge
Additional information, context and logs
No response

Seems like a good idea. I'll convert this to an "enhancement" and get this into our backlog :)

@JustMaier @myweet Is this stale? I'm currently looking for ways to contribute.
I see details for "Resources Used" is currently being returned via https://civitai.com/api/trpc/image.getGenerationData. Does that address the issue?


Add TypeScript typings for ssr

I run my entryServer through webpack using TypeScript, so have found a need for these.

:+1:


add some cast flag to ExprNode

int to float cast(resolved in checkType)

close by commit 6bf04cfed3e49dd7c0583262459ec497700177b6


refactor(eg): move to separate repository

This PR moves EG into separate repository and back-ports all other changes, in particular to kit package, to make eg run.

@ericvicenti Where is EG stuff moving?

@ericvicenti Where is EG stuff moving?

https://github.com/ericvicenti/uprising


F40: missing os directory on dl.fp.o for the release

The F39 download directory for IoT on dl.fedoraproject.org includes three subdirs:  images, iso, os
https://dl.fedoraproject.org/pub/alt/iot/39/IoT/aarch64/
The F40 download directory for IoT on dl.fp.o only has two subdirs: images, iso
https://dl.fedoraproject.org/pub/alt/iot/40/IoT/aarch64/
What happened to the os subdir?  Is there rationale for it's omission?

This was a result of moving to osbuild for our deliverables . We decided to document how to use pxe .

Ah right. So this is basically a duplicate of #24.


Investigate why the ArtifactManagementServiceImplTest is failing

Task Description
We've had to disable the ArtifactManagementServiceImplTest, as a follow-up to #1246. We need to re-enable this test and resolve it's issues with high priority. This test needs to be re-worked to use the new test annotations, as explained in #1165. Once the test is re-enabled, it should start failing in our Travis build, as Travis is building the code under MacOS, where it seems to almost always be reproducible.
Acceptance Test

[ ] Building the code with mvn clean install -Dintegration.tests still works.
[ ] Running mvn spring-boot:run in the strongbox-web-core still starts up the application correctly.
[ ] Building the code and running the strongbox-distribution from a zip or tar.gz still works.
[ ] The tests in the strongbox-web-integration-tests still run properly.

Task Relationships
This task:

Is a sub-task of: #1165
Is a follow-up of: #1246
Relates to: #1101 , #1243 , #1165

Help

Our chat
Points of contact:

@carlspring
@sbespalov
@fuss86

@carlspring I was able to reproduce the test failure in ArtifactManagementServiceImplTest class. And investigated the cause of failure of ArtifactManagementServiceImplTest.testConcurrentReadWrite.
As per my understanding this test is failing due to multiple race condition occurring between different threads in the following piece of code(getResult() inside ArtifactManagementServiceImplTest class)-
return aBoolean.getAndSet(!aBoolean.get()) ?
                   new Store(new ByteArrayInputStream(loremIpsumContentArray[i / 2]), repository, path).call() :
                   new Fetch(repository, path).call();

here the first race condition occurs in aBoolean.getAndSet(!aBoolean.get()). This expression has two individual actions here, each, separately (!aBoolean.get() and aBoolean.getAndSet) are atomic; combined they are not. this is also called the anti-pattern "check than act".
And the second race condition is occurring in new Store(new ByteArrayInputStream(loremIpsumContentArray[i / 2]), repository, path).call()  and new Fetch(repository, path).call();.
As per my understanding the getResult() is supposed to do two things. first aBoolean is true so it stores the artifact by calling new Store().call() and it sets the aBoolean to false now which means next time it is supposed to call new Fetch().call() which means artifact is fetched. And again this is repeated as aBoolean alternates between true and false;
But due to use of parallel streams multiple threads can be there in getResult function at a time. I have tested this by putting print statements inside getResult and I can see multiple times aBoolean printed as true which means multiple threads are there in getResult and therefore a race exists.
But this race is not causing the issue. The issue is when a thread which is storing the artifcat by calling new Store().call and on the same time there is a different thread which is calling new Fetch().call trying to fetch the same artifact. Now if second thread wins the race then it means it will try to fetch the artifact which doesn't exist and we will see an ArtifactNotFoundException in the logs. I have found out the same exception in stack trace.
Now in my opinion in order to make this test pass we need to synchronize the access to both new Store().call() and new Fetch().call(). For this I created a lock instance and passed the same to both the call functions of Store and Fetch class. Once I did this I ran the ArtifactManagementServiceImplTest a number of times and I can see the test passing all the times.

@yugander-krishan-singh : Thanks for your extensive investigation and detailed description of the problem.
@fuss86 : Would you mind reviewing?

Hi @yugander-krishan-singh,
thank you for deep investigation, but unfortunately it does not highlight the real issue here.
The idea of this test is to ensure that N threads are able to store/read to/from the same location.

This expression has two individual actions here, each, separately (!aBoolean.get() and aBoolean.getAndSet) are atomic; combined they are not. this is also called the anti-pattern check than act.

I agree with you that these 2 operations are not atomic together. Expression aBoolean.getAndSet(!aBoolean.get()) provides some kind of randomness, that's fine. But we can be sure about one thing, it will always return true by the first Thread because we initialized it by new AtomicBoolean(true). So we know that new Store(...) will be called at least once (however, we can't be sure whether it will be the first action or not).
NullPointerException encountered during this test shouldn't be "fixed" this way you proposed. This exception occurred because we did something wrong in the core code, not in the test. This test could fail (yes, there is a probability if fetching threads have been waiting too long for storing thread), but exception from the core code signals some real problems.
@carlspring , @sbespalov the issue here is:
we are opening TempOutputStream based on TempRepositoryPath before writing and then we are trying to lock the path (let's say by Thread A). If this path is currently locked by some other Thread B, the content from the TempRepositoryPath will be moved to the target destination by Thread B, and TempRepositoryPath will be deleted. When the Thread B releases the path lock, Thread A acquires it and it wants to operate on non-existing TempRepositoryPath (because this path was deleted by Thread B) having opened TempOutputStream . This needs to be fixed in the core code.

@fuss86 Thanks for the explanation.
@carlspring I will remove the changes made and update the PR.

The initial implementation of ArtifactManagementServiceImplTest.getResult condition was the i % 2 == 0, to have same number of reads and writes, unlike of aBoolean.getAndSet(!aBoolean.get()) which seems really not thread safe and makes test results more unpredictable.
Anyway, is there any stack trace for this random ArtifactManagementServiceImplTest.testConcurrentReadWrite failures?

@carlspring , @sbespalov the issue here is:

@fuss86  thanks for explanation, actually I thought that this case should work fine because we start writing only after lock accrued by writer thread, but maybe you right and we should have a test for it.
@carlspring  I will do the unit test for the above scenario, and try to fix it if there will be any issues with it.

Okay, thanks for looking into it, @sbespalov ! :)

The initial implementation of ArtifactManagementServiceImplTest.getResult condition was the i % 2 == 0, to have same number of reads and writes,

Yes, but it failed many times because new Fetch Threads were able to be called many times before new Store Threads

unlike of aBoolean.getAndSet(!aBoolean.get()) which seems really not thread safe

it's not meant to be thread safe but ensure new Store is called by the first Thread

and makes test results more unpredictable.

it brings more randomness in the number of new Store/new Fetch operations

Anyway, is there any stack trace for this random ArtifactManagementServiceImplTest.testConcurrentReadWrite failures?

It's easily reproducible on my end. Here is the gist.
I can make logs more verbose for you, if you want.

I also found a deadlock within this task
thread dump


Replacing bun with yarn and vitest

Turned out there is an issue with unmocking modules in bun tester, still unresolved.

found a way to keep bun in #18


Hoist activity fields to the logging scope

Expose SpanId, TraceId and ParentId to logging scope properties
Added tests to verify the Hierarchical ID format

Fixes #9491
PS: I need to spend some time looking at allocations before I merge this.
cc @benaadams
cc @lmolkova @SergeyKanzhelev for review

Do you need to capture the fields to HostingLogScope directly? Is it safe to capture the Activity then output the values from that when needed?

Do you need to capture the fields to HostingLogScope directly? Is it safe to capture the Activity then output the values from that when needed?

I was going to but storing the async local felt strange. I'll need to experiment with that.

I was going to but storing the async local felt strange.

That's just a tangental bit of Activity? Hosting creates the Scope, Activity and starts it; as well as Disposing the Scope and ending the Activity, and the Activity doesn't get reused, so should be ok?

That's just a tangental bit of Activity? Hosting creates the Scope, Activity and starts it; as well as Disposing the Scope and ending the Activity, and the Activity doesn't get reused, so should be ok?

Yes, you're right, it would just be storing the activity object on 2 async locals (Activity.Current and the logging scope). It does mean it would have similar issues to holding onto the HttpContext but maybe it won't be as big a problem since not much is stored on the activity currently.

🆙 📅


The 'path' argument must be of type string. Received type object

Converting a multipart post script throws an ERR_INVALID_ARG_TYPE.
jhewitt@JimsMac LoadTest % postman-to-k6 PostmanCollection.json k6-script.js
The "path" argument must be of type string. Received type object
TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received type object
at validateString (internal/validators.js:125:11)
at basename (path.js:1289:5)
at fileLoad (/usr/local/lib/node_modules/postman-to-k6/lib/render/index.js:190:16)
at files (/usr/local/lib/node_modules/postman-to-k6/lib/render/index.js:180:18)
at render (/usr/local/lib/node_modules/postman-to-k6/lib/render/index.js:20:5)
at convertObject (/usr/local/lib/node_modules/postman-to-k6/lib/convert/object.js:45:10)
at convertJson (/usr/local/lib/node_modules/postman-to-k6/lib/convert/json.js:26:10)
at convertFile (/usr/local/lib/node_modules/postman-to-k6/lib/convert/file.js:31:10)
at Command.run (/usr/local/lib/node_modules/postman-to-k6/bin/postman-to-k6.js:51:30)
at Command.listener (/usr/local/lib/node_modules/postman-to-k6/node_modules/commander/index.js:315:8)
The postman script being converted is as follows:
{
"info": {
"postman_id": "53810ff5-fa40-4971-9d83-9e0d7ef1f8a6",
"name": "Quidel Load Testing",
"schema": "https://schema.getpostman.com/json/collection/v2.1.0/collection.json"
},
"item": [
{
"name": "Post Assay, Both Images - Flu A Positive",
"event": [
{
"listen": "test",
"script": {
"id": "53f8e350-9de2-4cbb-9007-f16dc329e525",
"exec": [
"pm.test("Status Test", () => {",
"    pm.response.to.have.status(201);",
"});"
],
"type": "text/javascript"
}
},
{
"listen": "prerequest",
"script": {
"id": "8b675d75-b02a-4cab-99d8-1c1112620ca6",
"exec": [
"require('lodash');",
"pm.environment.set("barcodeData", Math.floor(.random(10000000000000000000000000000000000000000000000,<PHONE_NUMBER>9999999999999999999999999999999999999)).toLocaleString('fullwide', {useGrouping: false}));"
],
"type": "text/javascript"
}
}
],
"request": {
"method": "POST",
"header": [
{
"key": "Content-Type",
"name": "Content-Type",
"value": "application/json",
"type": "text"
},
{
"key": "api-key",
"value": "B051ED42-72C5-435A-B383-2D92346A9B6D",
"type": "text"
}
],
"body": {
"mode": "formdata",
"formdata": [
{
"key": "assayJson",
"value": "{\n  assayJson : {\n    barcodeData: "18382871446225358000000000000000000000000000000",\n    barcodeType: 1,\n    userId: "postman",\n    appVersion: "postman",\n    phoneId: "Postman",\n    phoneOs: "Postman",\n    expirationDate: "1/1/2020 12:00:00 AM",\n    serialNumber: "872930",\n    auxBoxId: "1234",\n    assayType: "90",\n    testDate: "1/1/2020 12:00:00 AM",\n    results : [\n      {\n        type: "fluBProb",\n        value: "0.85"\n      },\n      {\n        type: "fluAProb",\n        value: "0.75"\n      },\n      {\n        type: "rcPeakValue",\n        value: "100"\n      },\n      {\n        type: "fluAResult",\n        value: "positive"\n      },\n      {\n          type: "fluBResult",\n          value: "negative"\n       }\n    ],\n    images : [\n      {\n        type: "lightImage",\n        fileName: "18645_d1fd_DIMG_20201103T2218_5a8a345b-68b2-48f6-b537-74d084dc56c1.raw",\n        captureTime: "1/1/2020 12:00:00 AM"\n      },\n      {\n        type: "darkImage",\n        fileName: "18645_d1fd_LIMG_20201103T2218_4672fbab-048f-47b4-8698-4ae31ddf7551.raw",\n        captureTime: "1/1/2020 12:00:00AM"\n      },\n      {\n        type: "intermediate1",\n        fileName: "18645_d1fd_DBRGB_20201103T2218_0d3f5319-49a1-4bf5-b1ce-f6e1a75ac328.png",\n        captureTime: "1/1/2020 12:00:00AM"\n      },\n      {\n        type: "intermediate2",\n        fileName: "18645_d1fd_DBRD_20201103T2218_4146b8d3-7721-4497-9d21-4de3d3c5959a.png",\n        captureTime: "1/1/2020 12:00:00AM"\n      },\n      {\n        type: "intermediate3",\n        fileName: "18645_d1fd_NMRGB_20201103T2218_2e21a031-70cb-44a5-9811-992c2dbab6e9.png",\n        captureTime: "1/1/2020 12:00:00AM"\n      },\n      {\n        type: "intermediate4",\n        fileName: "18645_d1fd_RDCRP_20201103T2218_91be8f98-e335-432a-9c87-81cbd8cc045f.png",\n        captureTime: "1/1/2020 12:00:00AM"\n      },\n      {\n        type: "intermediate5",\n        fileName: "18645_d1fd_RGBCRP_20201103T2218_af5d97bf-99d9-4f95-b264-6f2ba4db8e3b.png",\n        captureTime: "1/1/2020 12:00:00AM"\n      },\n      {\n        type: "intermediate6",\n        fileName: "18645_d1fd_THBW_20201103T2218_3c660420-4af0-4604-b353-bc96ead36e3c.png",\n        captureTime: "1/1/2020 12:00:00AM"\n      }\n    ]\n  }\n}",
"contentType": "application/json",
"type": "text"
},
{
"key": "image[]\n",
"type": "file",
"src": [
"/Users/jhewitt/Source/Quidel/LoadTest/18645_d1fd_DBRGB_20201103T2218_0d3f5319-49a1-4bf5-b1ce-f6e1a75ac328.png",
"/Users/jhewitt/Source/Quidel/LoadTest/18645_d1fd_DBRD_20201103T2218_4146b8d3-7721-4497-9d21-4de3d3c5959a.png",
"/Users/jhewitt/Source/Quidel/LoadTest/18645_d1fd_THBW_20201103T2218_3c660420-4af0-4604-b353-bc96ead36e3c.png",
"/Users/jhewitt/Source/Quidel/LoadTest/18645_d1fd_RGBCRP_20201103T2218_af5d97bf-99d9-4f95-b264-6f2ba4db8e3b.png",
"/Users/jhewitt/Source/Quidel/LoadTest/18645_d1fd_RDCRP_20201103T2218_91be8f98-e335-432a-9c87-81cbd8cc045f.png",
"/Users/jhewitt/Source/Quidel/LoadTest/18645_d1fd_NMRGB_20201103T2218_2e21a031-70cb-44a5-9811-992c2dbab6e9.png",
"/Users/jhewitt/Source/Quidel/LoadTest/18645_d1fd_LIMG_20201103T2218_4672fbab-048f-47b4-8698-4ae31ddf7551.raw",
"/Users/jhewitt/Source/Quidel/LoadTest/18645_d1fd_DIMG_20201103T2218_5a8a345b-68b2-48f6-b537-74d084dc56c1.raw"
]
}
],
"options": {
"formdata": {}
}
},
"url": {
"raw": "",
"protocol": "https",
"host": [
"sniffles-api-dev",
"azurewebsites",
"net"
],
"path": [
"api",
"v1.0",
"assay",
"postassaywithimages"
]
}
},
"response": []
}
],
"protocolProfileBehavior": {}
}

try postman-to-k6 PostmanCollection.json -o k6-script.js

It gives me the same error, I suspect it is erring on the key: image[] type: file src:[] in the body?
jhewitt@JimsMac loadtest % postman-to-k6 PostmanCollection.json -o k6-script.js
The "path" argument must be of type string. Received type object
TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received type object
at validateString (internal/validators.js:125:11)
at basename (path.js:1289:5)
at fileLoad (/usr/local/lib/node_modules/postman-to-k6/lib/render/index.js:190:16)
at files (/usr/local/lib/node_modules/postman-to-k6/lib/render/index.js:180:18)
at render (/usr/local/lib/node_modules/postman-to-k6/lib/render/index.js:20:5)
at convertObject (/usr/local/lib/node_modules/postman-to-k6/lib/convert/object.js:45:10)
at convertJson (/usr/local/lib/node_modules/postman-to-k6/lib/convert/json.js:26:10)
at convertFile (/usr/local/lib/node_modules/postman-to-k6/lib/convert/file.js:31:10)
at Command.run (/usr/local/lib/node_modules/postman-to-k6/bin/postman-to-k6.js:51:30)
at Command.listener (/usr/local/lib/node_modules/postman-to-k6/node_modules/commander/index.js:315:8)

Thank you for bringing this to my attention! Will have a look at it and get back to you.

is there any update on this yet?

Sorry, I've been completely swamped so not yet unfortunately. 😅

@jhewitt
I'm trying to contribute but fixing the postman-to-k6 generation part and the way it handles an array [] of files.
This the output that I get in as a K6 script: k6-script.js.txt
Could you review if this is what you expect?
If it is, then I'll create a PR for the problem.

Apologies for the inactivity on this project.
Due to the inability to properly support this project, the k6 team has decided not to continue its development. The primary reason is that k6 scope has grown significantly with the launch of k6 extensions. The team is prioritizing extending k6 capabilities over the converters.
We suggest you post your issue at api-deck/postman-to-k6. The project is active and maintained on this fork.


Trovi 2.0: Implement native create/edit form

The handlers and spawners have been updated to pull down contents and metadata from Trovi. I haven't been able to test artifact spawning with a local portal yet, but I will be doing that while this is in review.

 Trovi 2.0: Implement native create/edit form


雪花算法的41bit计算公式少了  /24 。  41-bittimestamp=(1L<<41)/(1000/3600/24/365)

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
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

哪里少了？

发起了，你看下

还有下面俩个文档也存在该问题。
https://github.com/Ahoo-Wang/CosId/blob/7c15de3cc515f0b6269dd71d259c4e74ed834e1c/README.zh-CN.md?plain=1#L136
https://github.com/Ahoo-Wang/CosId/blob/main/document/docs/guide/README.md


minor documentation updates

addition to getting started that is helpful if someone chooses to create new .ipynb instead of modifying provided sample
suggestion to make it clear the best way to import your generated module if storing notebooks anywhere other than project root, without requiring sys.path hacks

Thanks! I'll also add the solution to create a simlink when you have a path for the notebooks that's not just the origin.


docs: Add CONTRIBUTING file and @all-contributors bot

@all-contributors please add @TimAstier for  code doc maintenance ideas


fix: add fallback value for language features

Types

[x] 🐛 Bug Fixes

Background or solution
fixed #829
Changelog

Codecov Report

Merging #908 (6d96e2f) into main (853bc05) will increase coverage by 0.00%.
The diff coverage is 53.16%.

@@           Coverage Diff           @@
##             main     #908   +/-   ##
=======================================
  Coverage   58.56%   58.56%
=======================================
  Files        1212     1212
  Lines       75181    75196   +15
  Branches    15650    15650
=======================================
+ Hits        44030    44041   +11
- Misses      28390    28396    +6
+ Partials     2761     2759    -2

Impacted Files
Coverage Δ

packages/extension/src/common/vscode/languages.ts
85.36% <ø> (ø)

...tension/src/hosted/api/vscode/ext.host.language.ts
46.52% <53.16%> (-0.58%)
:arrow_down:

...ages/file-service/src/node/file-service-watcher.ts
68.33% <0.00%> (+0.55%)
:arrow_up:

packages/file-service/src/browser/watcher.ts
100.00% <0.00%> (+4.34%)
:arrow_up:

...es/src/browser/userstorage/user-storage.service.ts
62.92% <0.00%> (+5.61%)
:arrow_up:

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 853bc05...6d96e2f. Read the comment docs.


Can not run the sample

Project Folder\eclipse-workspace\Whatsapp_Business\bin\src\main\java>gradle -q run
FAILURE: Build failed with an exception.

What went wrong:
Task 'run' not found in root project 'java'.

Try:
Run gradle tasks to get a list of available tasks. Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 1s

Which quickstart or sample are you trying to run?
You'll need navigate to the directory where the specific gradle files are to run that command.
For example, if I wanted to run the calendar quickstart, I'd need to navigate to:
/java-samples/calendar/quickstart
/java-samples/calendar/quickstart$ gradle -q run

friendly ping, let us know if you're still having this issue -- thanks!

I had the same problem. But I tried running the "gradle -q run" command where gradle files are as you said, and it worked.

Maybe we should add a README per quickstart directory.

Great to hear it worked


Please stop hiding the donation button in Sodium's video setting screen

As it appears here, you are shipping a config file which disables the prompt for a user to consider donating to our project. Please remove this config entry override so that users are shown the prompt again.
This is a single button in the video settings screen and should not bother anyone. If the user is bothered, they can click a single button (right next to our prompt) and permanently dismiss it.

Sorry about this. I understand that you want this enabled. I will fix the issue and release a new version by the end of the day.

I have fixed this issue in v.2.2.6. Thank you for reaching out, and I am always happy to help. Honestly this modpack started with me wanting all my mods together and I didn't know that so many people would use it. So I fully understand that you want the donate button visable.

It is no issue. I had just assumed that you had just copied the config file from a game directory which had option already hidden, since it is pretty easy to do. Thanks for changing it!

Yep thats what happened. No problem at all.


Ty

Tank you i am new

Hey @zipxxx1! Doesn't look like you have any of your own work in the is PR. Did you mean to contribute something to ImgBot?


The Monolithic Enum Hardening Thread

SDL_GPU_TEXTUREFORMAT_INVALID is defined as -1, which means that if someone forgets to initializes the arguments to a texture or swapchain they'll get a working system instead of an error as 0 is a valid enum entry.

Similarly, we need to have MAX values so that backends can have static assertions for their translation arrays. Making this consistent across all the enumerations should be done before we merge.

using _COUNT not _MAX as it doesn't collide with an existing _MAX entry in SDL_GpuBlendOp

Also added _MASKCHECK which tells which bits are allowed to be used in a bit flag enum

Ready for review/merge

Upgrading this to Beta, since it's a task that risks changing ABI.

I'm souring on this, both because I don't think 0 should be invalid and because I think including MAX in all our enums makes them too brittle and encourages clients to loop on them. There's very few examples of MAX values across public SDL enums. If we really want to validate enum values in functions we can always check internally what we know to be the largest enum value.

SDL does do static asserts for arrays based on enums, but only some enums actually have SDL_NUM_##thing at the end, so we'd have to come up with some other way to make sure the assertions are doing their job if stuff gets added (not likely for most of  them, but texture format in particular I could see getting additions over the next decade).
@slouken, any preferences for how enum/arraysize validation is set up?

I don't have a strong preference. Typically adding to the end of enums doesn't break application code that iterates until a previously known maximum, but you do have to be careful how you treat new enum values.
I think whatever works for you guys and ends up being the least brittle and accidentally broken by future us is fine.

#215 puts something together for TextureFormat which is the one we expect to get additions in the future. We may need to do this for swapchain composition as well but it's not as urgent; once that PR is in this can be bumped to Ship.

This recently got worked on via https://github.com/libsdl-org/SDL/pull/10786 but I don't think we do any validation yet.

There is validation on any enum that has an INVALID entry. I feel pretty good about where things are right now with respect to enums so I'm closing this.


Show errors from non-main threads in editor

The GDScript VM breaks out of the current function on error, such as assertion failures or general script errors.  These errors cause debug breakpoints when running under the debugger/editor.  However, threads that are not the main thread are not able to be debugged.  For any worker threads, these errors were just printed to stderr, and then the thread would silently exit the current frame, leading to unpredictable results.  There was no indication in the Editor itself.
This change submits such errors to the error reporting facility of the debugger also, so they can be displayed in the editor as Errors.  They still don't cause debug breakpoints, because that would require general support for thread debugging.  This is for notifications only.
Example program:
extends Node

var typed: int

func _ready():
	var thread = Thread.new()
	thread.start(_thread_function)
	thread.wait_to_finish()

func _thread_function():
	assert(typed > 0, "this was only shown on stderr before, with no indication in the Editor")

Does this solve #2446 ?

@akien-mga this PR is me learning the code base around VM and debugger enough to go work on 2446...

@Faless can I close this?   You mentioned elsewhere that you thought it was wrong, but that may have been a misunderstanding.

CC @Faless @vnen Is it mergeable/safe enough for 4.1? If not, I'll push the milestone to 4.2.

This may be superseded by #76582 which is planned for 4.2. Once that one is merged, this one should be re-evaluated to see if it's still relevant (partially or in full).

Seeing how https://github.com/godotengine/godot/pull/76582 is merged, is this still relevant?

The reproduction case from the OP is indeed well supported in 4.2-beta:

So this doesn't seem needed anymore. Thanks for the contribution!


Question about differences between v6 and v7

I just have a general question. Are there any breaking changes between 6 and 7? I'm trying to ugrade to 7 but by just upgrading, the range slider becomes immoveable, so I'm not sure what I need to update from my implementation, or how this could happen

Well, there is no breaking change per se, but there was a change in the structure that introduced a risk so I decided to use a new major.
Could you try to reproduce the problem in a minimal snack?

ok, I will try and put something together

There is a code sample in the Readme if you want to use this as a base.

You can use this as a starting point: https://snack.expo.dev/@sharcoux/ff0473?platform=android

Do you still have the problem?

I was asking for a colleague and he said he would be in touch.
Thanks for your prompt response, really appreciate it
Feel free to close this one
On Mon, Sep 18, 2023 at 6:48 PM François Billioud @.***>
wrote:

Do you still have the problem?
—
Reply to this email directly, view it on GitHub
https://github.com/Sharcoux/slider/issues/80#issuecomment-1724085415,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB32TFL4SGL4BDQGBGLQMUDX3CCNHANCNFSM6AAAAAA43VGQHA
.
You are receiving this because you authored the thread.Message ID:
@.***>


home-built clang doesn't find libstdc

https://godbolt.org/g/JLKxO0
yields
<source>:1:10: fatal error: 'type_traits' file not found
#include <type_traits>
^
1 error generated.
Compiler exited with result code 1

Fixed by mattgodbolt/compiler-explorer-image@52f85534559b41e11590b5bf5238da273c1bb94e


LobbyID in admin-box

Currently the LobbyID is only shown as text in the admin box.
Should be  properly designed with a copy-to-clipboard function.

Fixed with https://github.com/error401de/csgo-mapvote/commit/13e8a3a16f42bb96bfe4c352b9df0359a1bec21f


Vertical camera - rotate depth frames?

| Camera Model                       | {D400  |
| Firmware Version                   | V2.31.0 |
| Operating System & Version |   Linux / MacOS  |
| Kernel Version (Linux Only)    |  (e.g. 4.14.13)                                         |
| Platform                                 | PC |
| SDK Version                            |  { 2.X }                          |
| Language                            |  {python}                          |
| Segment			|  {/others }                          |
Issue Description
I have a developed application in python and some tests indicate the performance of the camera would be better if rotated 90 degrees.  It would be extremely time consuming (and confusing!) to rewrite and change all the code which assumes x is horizontal and y is vertical.  We use a lot of librealsense API calls.  Is there an easer to to rotate the camera and still have x, y behave correctly? e.g. in 480x640 resolution?

I believe that you wish to rotate the camera 90 degrees but rotate the image 90 degrees in the opposite direction so that it appears in its normal orientation, please?
If you are able to use OpenCV in your application, it has the ability to rotate an image.  the link below gives guidance about doing this with Python.
https://note.nkmk.me/en/python-opencv-numpy-rotate-flip/

no, thats not correct.
I want to turn the camera 90 degrees and still have X axis be horizontal, Y is vertical.  So, for example in landscape the camera is 640x480 and in portrait it is 480x640.
If the camera is NOT rotated the follow code is correct
dist = depth_frame.get_distance(x, y)
if the camera IS rotated then the code needs to be
dist = depth_frame.get_distance(y, x)
which will get confusing very quickly, every x must swapped for y.
A solution could be done at the frame level
depth_frame = depth_frame.rotate(rs2.90_DEGREES_CLOCKWISE)
dist = depth_frame.get_distance(x, y)
but would probably be better at the device level so the color and IR frames also do the 'right thing'
config = rs.config()
config.device_orientation(rs2.90_DEGREES_CLOCKWISE)
config.enable_stream(rs.stream.depth, 480, 640, rs.format.z16, 30)
config.enable_stream(rs.stream.color, 480, 640, rs.format.bgr8, 30)
Or something like that.  Does that help?

I considered your question carefully.   It sounds as though it would be much easier to keep the camera in its normal orientation and seek to improve the output results by other means.  Could you tell me please what problems you have with the camera in its normal orientation that seem to be better when it is rotated 90 degrees please?   Thanks very much!

I am measuring a tall vertical groove at close range.  When the camera is horizontal the cameras can not see deeply into the groove. When the camera is vertical it can.

On 11 Mar 2020, at 12:36, MartyG-RealSense<EMAIL_ADDRESS>wrote:
I considered your question carefully. It sounds as though it would be much easier to keep the camera in its normal orientation and seek to improve the output results by other means. Could you tell me please what problems you have with the camera in its normal orientation that seem to be better when it is rotated 90 degrees please? Thanks very much!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/IntelRealSense/librealsense/issues/6023#issuecomment-597607908, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAMO7CS5R4KDC2VKWEUANLRG6AWTANCNFSM4LFTPTIA.

Hi @keithahern
We have such capability on the upcoming L500 camera, and we may be able to port this to D400 cameras in one of the future releases. I agree it's not as easy as rotating the image, all calibration data and other parameters need to be updated, and we do want to enable it in the SDK at some point

Great.
Thank you Sergey and Marty.

On 11 Mar 2020, at 12:55, Sergey Dorodnicov<EMAIL_ADDRESS>wrote:
Hi @keithahern https://github.com/keithahern
We have such capability on the upcoming L500 camera, and we may be able to port this to D400 cameras in one of the future releases. I agree it's not as easy as rotating the image, all calibration data and other parameters need to be updated, and we do want to enable it in the SDK at some point
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/IntelRealSense/librealsense/issues/6023#issuecomment-597615585, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAMO7HC7VI45JNXKZ7TR5DRG6C5BANCNFSM4LFTPTIA.

@dorodnic @MartyG-RealSense I would like to upvote this request, as we would like to use it in our application, which involves detecting human faces. The point is that having the largest field of view in the vertical (i.e. a portrait orientation rather than landscape) helps to allow for a wider range of subject heights, potentially including people sitting in wheelchairs, etc. It would be most helpful to have the requested feature for our application, too!!

@RMichaelPickering   Thanks so much for your supportive input!
You could also increase the vertical field of view by having two cameras stacked vertically with their fields of view overlapping, and this should avoid the image rotation implications that Dorodnic mentioned.  I can appreciate that this has hardware cost implications for projects though.

any update on this? a vertical orientation parameter or a function that can rotate realsense frames would be very helpfull!

My solution has been to just used RealSense for initial depth and color frame acquisition and then move to the (also Intel backed) Open3D library and do my processing from there (i.e. I'm not using any RealSense projection/deprojection APIs.  In Open3d it's much easier to merge and manipulate point clouds, render to 2D, create cross platform UIs etc. The documentation is lacking in places but it's allowed me to move forward.
See below on how to get an rs frameset into an open3d PointCloud and transform it - its very fast.
`
depth_frame = frameset.get_depth_frame()
color_frame = frameset.get_color_frame()
depth_image = np.asanyarray(depth_frame.get_data())
color_image = np.asanyarray(color_frame.get_data())
img_depth = o3d.geometry.Image(depth_image)
img_color = o3d.geometry.Image(color_image)
img_rgbd = o3d.geometry.RGBDImage.create_from_color_and_depth(img_color,img_depth)
intrinsics = profile.as_video_stream_profile().get_intrinsics()
pinhole_camera_intrinsic = o3d.camera.PinholeCameraIntrinsic(intrinsics.width, intrinsics.height, intrinsics.fx, intrinsics.fy, intrinsics.ppx, intrinsics.ppy)
pcd = o3d.geometry.PointCloud.create_from_rgbd_image(img_rgbd, pinhole_camera_intrinsic)
pcd.transform([[1, 0, 0, 0], [0, -1, 0, 0], [0, 0, -1, 0], [0, 0, 0, 1]])
`

My solution has been to just used RealSense for initial depth and color frame acquisition and then move to the (also Intel backed) Open3D library and do my processing from there (i.e. I'm not using any RealSense projection/deprojection APIs. In Open3d it's much easier to merge and manipulate point clouds, render to 2D, create cross platform UIs etc. The documentation is lacking in places but it's allowed me to move forward.
See below on how to get an rs frameset into an open3d PointCloud and transform it - its very fast.
`
depth_frame = frameset.get_depth_frame()
color_frame = frameset.get_color_frame()
depth_image = np.asanyarray(depth_frame.get_data())
color_image = np.asanyarray(color_frame.get_data())
img_depth = o3d.geometry.Image(depth_image)
img_color = o3d.geometry.Image(color_image)
img_rgbd = o3d.geometry.RGBDImage.create_from_color_and_depth(img_color,img_depth)
intrinsics = profile.as_video_stream_profile().get_intrinsics()
pinhole_camera_intrinsic = o3d.camera.PinholeCameraIntrinsic(intrinsics.width, intrinsics.height, intrinsics.fx, intrinsics.fy, intrinsics.ppx, intrinsics.ppy)
pcd = o3d.geometry.PointCloud.create_from_rgbd_image(img_rgbd, pinhole_camera_intrinsic)
pcd.transform([[1, 0, 0, 0], [0, -1, 0, 0], [0, 0, -1, 0], [0, 0, 0, 1]])
`

Thanks this solves the problem!

@Kevin-Delnoije   The feature request related to this case remains active but I have no further updates to provide about it.  I see that the advice of @keithahern has solved your problem though, which is excellent news.
@keithahern  Thanks so much for the successful help you provided to @Kevin-Delnoije

Hi @keithahern We have such capability on the upcoming L500 camera, and we may be able to port this to D400 cameras in one of the future releases. I agree it's not as easy as rotating the image, all calibration data and other parameters need to be updated, and we do want to enable it in the SDK at some point

@dorodnic I am working with the L515. Could you kindly tell me how to do it in Python? I cant find it ...

FWIW, we've implemented some frame rotation code using OpenCV but it would
of course be far better to do as much of this as possible in the camera! If
the capability from the L500 could be ported to the D4xx cameras and fully
supported in the SDK that would be excellent!!
Mike
R. Michael Pickering CBIP
President & CEO
CloudConstable Incorporated
10271 Yonge Street, Suite 321
Richmond Hill, ON L4C 3B5
Canada
www.cloudconstable.com
@.***
Toronto:<PHONE_NUMBER>
Orlando:<PHONE_NUMBER>
On Fri, 3 Dec 2021 at 08:45, Qualityland @.***> wrote:

Hi @keithahern https://github.com/keithahern We have such capability on
the upcoming L500 camera, and we may be able to port this to D400 cameras
in one of the future releases. I agree it's not as easy as rotating the
image, all calibration data and other parameters need to be updated, and we
do want to enable it in the SDK at some point
@dorodnic https://github.com/dorodnic I am working with the L515. Could
you kindly tell me how to do it in Python? I cant find it ...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/IntelRealSense/librealsense/issues/6023#issuecomment-985532931,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEABETJN34AXB2B37JF6QI3UPDCX7ANCNFSM4LFTPTIA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Hi @RMichaelPickering  The official feature request to Intel to provide support on the 400 Series cameras for rotation of depth frames remains active but there is no progress to report at this time.
@qualityland27  At the time that the statement about L515 support for image rotation was made, the camera was in its pre-release phase.  I do not have any information regarding whether the suggested feature was included in the RealSense SDK post-launch.

Hi, I'm using L515 and I also need to rotate camera 180 degree for my project. This is very helpful to me, so can you tell me more about the usage ?

Hi @FeiSong123  If you rotate the L515 camera 180 degrees in the Y direction then although the image would be upside down, you would not need to make any changes to the image as its values should still be correct
If you needed to rotate / flip the image after rotating the camera 180 degrees so that the image was the 'right way up' then you could do that using the methods in this discussion or at https://github.com/IntelRealSense/librealsense/issues/4395#issuecomment-511113996 and https://github.com/IntelRealSense/librealsense/issues/9088

I also prefer to rotate at the camera level, and I see dorodinc commented that L515 has such capability. What should I do with C++(I can't find this function device_orientation with config).

The comment was made before the L515 was first released on sale, and not every planned feature is released for various reasons (for example, if the feature did not work well).  As far as I am aware there is not a dedicated image rotation feature for the L515.

That's a pity. Nevertheless, I still want to thank you for your guidance.

@dorodnic @MartyG-RealSense According to what @dorodnic has written: "I agree it's not as easy as rotating the image, all calibration data and other parameters need to be updated, and we do want to enable it in the SDK at some point".
I would like to know if we can expect same depth/image accuracy, quality, performance, reponse, etc. if the camera is rotated 90* left/right? For some reason calibration data is mentioned. So rotating those frames manually using some other software like OpenCV is to be considered sub-optimal because camera is not positioned up-right?

Hi @maciejandrzejewski-digica  There are no performance issues with physically rotating only the camera 90 degrees.  There would be a problem with calibration values if the frame was then rotated with software such as OpenCV to make the image display in the normal orientation.

Depending on the maximum depth range required, the RealSense D405 model (or its D401 PCB board version) may be an easy fit for a device case as it is a small square rather than wide horizontal shape.  Its ideal depth range is 0.7 cm to 50 cm, meaning that it is suited to very close range depth sensing applications rather than multiple-meter distances.
https://store.intelrealsense.com/buy-intel-realsense-depth-camera-d405.html
If a longer-distance camera model is required, a RealSense user earlier in this discussion at https://github.com/IntelRealSense/librealsense/issues/6023#issuecomment-785071263 shared a software workaround for frame rotation.
There is unfortunately not any further information available about the implications to camera parameters of frame rotation other than dorodnic's statement at https://github.com/IntelRealSense/librealsense/issues/6023#issuecomment-597615585

Hi everyone, have any of you been able to test the new rotation post-processing filter implemented on the development branch of librealsense, please?  Thanks!
https://github.com/IntelRealSense/librealsense/tree/development

I would like to test it but I haven't figured out how it even works.  Do you know how to use it?  My install is using the ROS 2 wrapper which he said it is not supported yet but I would like to know how to use it without the wrapper too.  Maybe I can figure out a way to make it work that way.

I would like to test it but I haven't figured out how it even works. Do you know how to use it? My install is using the ROS 2 wrapper which he said it is not supported yet but I would like to know how to use it without the wrapper too. Maybe I can figure out a way to make it work that way.

You can use this code reference as a usage example:
https://github.com/IntelRealSense/librealsense/blob/development/examples/post-processing/rs-post-processing.cpp

Thanks for the heads up.  Where can I find instructions for install/use?  Which repo branch of realsense library and wrapper do I need?

Please build from source librealsense development branch: https://github.com/IntelRealSense/librealsense/tree/development
and ros wrapper ros2-development branch: https://github.com/IntelRealSense/realsense-ros/tree/ros2-development
Both have install instructions when building from source

Thank you.  Can you tell me how to use the rotate filter in ROS after installation.  I just installed the development branch from both on Thursday.  Do I need to do it again or is there a way to just update them?

PR 3274  was merged on 12/12
Depends when you took it.
But you can git pull your forks to latest and it will be OK

I went through the instructions in both repo's and I can't figure out how
to use the rotation filter with ROS.  Where can I find instructions?  I
need to turn my images 90 degrees as my cameras are mounted narrow side
down.  I plan to use Aruco markers and human detection so I would like to
get the orientation of the image right first.
On Sun, Dec 15, 2024 at 1:58 PM Nir Azkiel @.***> wrote:

PR 3274 https://github.com/IntelRealSense/realsense-ros/pull/3274 was
merged on 12/12
Depends when you took it.
But you can git pull your forks to latest and it will be OK
—
Reply to this email directly, view it on GitHub
https://github.com/IntelRealSense/librealsense/issues/6023#issuecomment-2544010949,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHPBK3B2S3KILDAOZ2ZQT3T2FXI2HAVCNFSM6AAAAABR7OLXCGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBUGAYTAOJUHE
.
You are receiving this because you commented.Message ID:
@.***>

You can find instructions for using the rotation filter with ROS in this launch file:
rs_launch.py on the ros2-development branch
To enable and configure the rotation filter, you can use the following parameters:

rotation_filter.enable:

Default: false
Enable or disable the rotation filter.

rotation_filter.rotation:

Default: 0.0
Set the rotation angle. Supported values are 0.0, 90.0, -90.0, and 180.0.

You can configure these parameters  to rotate the images as needed for your setup.


Update configs in TaikoConfig.sol \ EIP1559Params for Alpha 3 testnet

Current config (we will change chainId for sure, and what else?):
library TaikoConfig {
    function getConfig() internal pure returns (TaikoData.Config memory) {
        return TaikoData.Config({
            chainId: 167,
            // Two weeks if avg block time is 10 seconds
            maxNumProposedBlocks: 120960,
            ringBufferSize: 120960 + 10,
            // Each time one more block is verified, there will be ~20k
            // more gas cost.
            maxVerificationsPerTx: 10,
            // Set it to 6M, since its the upper limit of the Alpha-2
            // testnet's circuits.
            blockMaxGasLimit: 6000000,
            // Set it to 79  (+1 TaikoL2.anchor transaction = 80),
            // and 80 is the upper limit of the Alpha-2 testnet's circuits.
            maxTransactionsPerBlock: 79,
            minEthDepositsPerBlock: 8,
            maxEthDepositsPerBlock: 32,
            maxEthDepositAmount: 10000 ether,
            minEthDepositAmount: 1 ether,
            // Set it to 120KB, since 128KB is the upper size limit
            // of a geth transaction, so using 120KB for the proposed
            // transactions list calldata, 8K for the remaining tx fields.
            maxBytesPerTxList: 120000,
            proofCooldownPeriod: 30 minutes,
            systemProofCooldownPeriod: 15 minutes,
            // Only need 1 real zkp per 10 blocks.
            // If block number is N, then only when N % 10 == 0, the real ZKP
            // is needed. For mainnet, this must be 0 or 1.
            realProofSkipSize: 10,
            ethDepositGas: 21000,
            ethDepositMaxFee: 1 ether / 10,
            txListCacheExpiry: 0,
            adjustmentQuotient: 16,
            relaySignalRoot: false
        });
    }
}

And we also need to create a EIP1559Params for the testnet:
struct EIP1559Params {
        uint64 basefee;
        uint64 gasIssuedPerSecond;
        uint64 gasExcessMax;
        uint64 gasTarget;
        uint64 ratio2x1x;
}

Do Sepolia faucets give users >= 1 ETH (to be able to test ETH deposits, minEthDepositAmount)?
In general looking at these ETH deposit parameters, the UX for ETH deposits is gonna be very challenging with the current system/values I think.

Do Sepolia faucets give users >= 1 ETH (to be able to test ETH deposits, minEthDepositAmount)?
In general looking at these ETH deposit parameters, the UX for ETH deposits is gonna be very challenging with the current system/values I think.

i believe some of them can give users >= 1 ETH, like the PoW one, but not sure the actual percentage, cc @d1onys1us . and hmm actually this feature is not supported in current bridge UI, so users have to do this by calling the TaikoL1.depositEtherToL2() manually, also not sure how many of them will use it.

Do Sepolia faucets give users >= 1 ETH (to be able to test ETH deposits, minEthDepositAmount)?
In general looking at these ETH deposit parameters, the UX for ETH deposits is gonna be very challenging with the current system/values I think.

i believe some of them can give users >= 1 ETH, like the PoW one, but not sure the actual percentage, cc @d1onys1us . and hmm actually this feature is not supported in current bridge UI, so users have to do this by calling the TaikoL1.depositEtherToL2() manually, also not sure how many of them will use it.

Yes it is possible for this faucet to give 1 ETH eventually but it is not easy, the user will need to wait for a period of time to get the 1 ETH.  If we can do 0.1 ETH it will definitely be better from the perspective of the users.

Smaller value shall be fine as long as it covers the fee. So I guess even 0.01 Ether will work.


Fix prepare and deploy

This fixes some bugs introduced recently which prevented the tool from being usable.
I would like to put some time into developing some kind of integration tests (ie, automated testing of the actual usage of the tool, rather than of its constituent parts) to prevent this sort of thing happening, as it's really tricky to actually test locally given that one probably doesn't want to deploy anything.
In the mean time, please can we have a freeze on any non-required changes? As you can see in this PR, the bugs that were introduced were non-trivial and were caused by changing components and writing tests for their new behaviour, without testing/changing the usage of these components by the higher-level parts of the tool.
In order to make refactors safe we should be (where possible) writing the tests before we change anything. A good percentage of yesterday was lost to these bugs and I would like to avoid that happening again!

In the mean time, please can we have a freeze on any non-required changes? As you can see in this PR, the bugs that were introduced were non-trivial and were caused by changing components and writing tests for their new behaviour, without testing/changing the usage of these components by the higher-level parts of the tool.


Test timeout when code is changed

If i comment out specific lines/functions from my code from specific files (for example, a redis queue job handling code) the tests are running fine. Otherwise the test result always goes to timeouts. The above mentioned lines of code is not even getting executed under the test conditions that I've written. The mere presence of it causes the timeouts.
Can anyone help me in figuring this out?
 ✖ timeout!

  test: TAP
  signal: SIGTERM
  handles:
    - type: Socket
      events:
        - end
        - error
        - close
        - data
        - timeout
    - type: Socket
      events:
        - end
        - error
        - close
        - data
        - timeout
    - type: Timer
    - type: Socket
      events:
        - end
        - error
        - close
        - data
        - timeout
    - type: Timer
  expired: TAP
  stack: |
    emit (node_modules/signal-exit/index.js:77:11)
    process.listener (node_modules/signal-exit/index.js:91:7)

 FAIL  test/demo.test.js 1 failed of 3 30s
 ✖ timeout!

 FAIL  test/newsletter.test.js
 ✖ timeout!

  test: TAP
  signal: SIGTERM
  handles:
    - type: Socket
      events:
        - end
        - error
        - close
        - data
        - timeout
    - type: Socket
      events:
        - end
        - error
        - close
        - data
        - timeout
    - type: Timer
    - type: Socket
      events:
        - end
        - error
        - close
        - data
        - timeout
    - type: Timer
  expired: TAP
  stack: |
    emit (node_modules/signal-exit/index.js:77:11)
    process.listener (node_modules/signal-exit/index.js:91:7)

 FAIL  test/newsletter.test.js 1 failed of 3 30s
 ✖ timeout!

  🌈 SUMMARY RESULTS 🌈

 FAIL  test/demo.test.js 1 failed of 3 30s
 ✖ timeout!

 FAIL  test/newsletter.test.js 1 failed of 3 30s
 ✖ timeout!

Suites:   2 failed, 2 of 2 completed
Asserts:  2 failed, 4 passed, of 6
Time:     30s

I figured this out from here. There were active DB connections.


PBR: Fix wrong parameter passed to clearcoat

See https://forum.babylonjs.com/t/nodematerial-contaning-clearcoatblock-fails-to-compile-in-webgl1/53422

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Snapshot stored with reference name:
refs/pull/15566/merge
Test environment:
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15566/merge/index.html
To test a playground add it to the URL, for example:
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15566/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/15566/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/15566/merge
https://gui.babylonjs.com/?snapshot=refs/pull/15566/merge
https://nme.babylonjs.com/?snapshot=refs/pull/15566/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/15566/merge#BCU1XR#0

Visualization tests for WebGPU (Experimental)
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15566/merge/testResults/webgpuplaywright/index.html

WebGL2 visualization test reporter:
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15566/merge/testResults/webgl2playwright/index.html


FE: Bump braces

[ ] Breaking change? (if so, please describe the impact and migration path for existing application instances)

What changes did you make? (Give an overview)
Bump braces 3.0.2 -> 3.0.3 to fix CVE-2024-4068.
https://nvd.nist.gov/vuln/detail/CVE-2024-4068
Is there anything you'd like reviewers to focus on?
How Has This Been Tested? (put an "x" (case-sensitive!) next to an item)

[ ] No need to
[ ] Manually (please, describe, if necessary)
[ ] Unit checks
[ ] Integration checks
[x] Covered by existing automation

Checklist (put an "x" (case-sensitive!) next to all the items, otherwise the build will fail)

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation (e.g. ENVIRONMENT VARIABLES)
[x] My changes generate no new warnings (e.g. Sonar is happy)
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged

Check out Contributing and Code of Conduct
A picture of a cute animal (not mandatory but encouraged)

@Haarolean PTAL


Is there a way to scroll to the top of Layout using List component in response to a button press?

💬 Question
UI Kitten and Eva version

Package
Version

@eva-design/eva

@ui-kitten/components
4.4

List is wrapper component around react native's FlatList component. Other than the properties listed in the List component docs, you can apply any property that react native's FlatList component expects. This includes the onScroll events.
Scrolling manually can be done by using this.myRef = React.createRef();, passing it to the <List ref={this.myRef} /> component, and manually calling this.myRef.current.scrollTo({ x:0, y: 100, animated: true }).

Thanks @CostachescuCristinel  works perfectly.
Here is my code
   const scrollRef = useRef<FlatList<any>>();
                <List                     ref={scrollRef}                     refreshing={refreshing}                     onRefresh={() => fetchData(false)}                     style={styles.list}                     contentContainerStyle={styles.listContent}                     data={dataSource}                     renderItem={renderItem}                     ListFooterComponent={() => <Button onPress={() => scrollRef.current.scrollToIndex({index: 0})}Back to top</Button>}                 />


Support Polkadot wallet connect on Vortex

As a Vortex user, i should be able to connect to Vortex using a Polkadot wallet
Acceptance criteria

User should be able to connect to vortex using Polkadot wallet
Polkadot wallets - Talisman, Subwallet

Hey team! Please add your planning poker estimate with Zenhub @ebma @gianfra-t @Sharqiewicz @TorstenStueber

@pendulum-chain/devs Let me know if any questions

I saw this ticket only after adding a comment to #272. I think this lacks the implications for the user experience. Similar to the question I put into the description of #272. How should we support both Polkadot and EVM wallets? What should the prototype show and how should it behave if a user connects to a Polkadot wallet?

Updated the ticket, let me know if any confusion

The tickets in the BSC USDT epic does not define the network switcher yet. What is the relative priority of that epic to this one here (Asset Hub)?
If this one here comes first, then let's not refer to BSC yet. Then the main user facing definition of this ticket is to introduce a network switcher (the fact that we would need to have different wallet integrations is then implied and would also be a requirement of this ticket).

Since the Binance USDT epic was picked up only as a fall back option, Asset Hub off ramp now holds higher relative priority between the 2 epics and should be progressed first, so that changes can be accommodated for the new EVM network (Binance) epic @TorstenStueber @prayagd

For Polkadot-wallet connection we can use the logic from Portal. This is the useConnectWallet hook. We can then customize the appearance of Dialog ourselves - or we can also simply use https://github.com/TalismanSociety/talisman-connect

Yes, let's reuse the UX from the Portal.

I will remove any reference to BSC from the ticket description.

@pendulum-chain/product @pendulum-chain/devs shall we store the selected network in the local storage (similar to the token selection) so that the network selection popup doesn't show up on the next reload?

shall we store the selected network in the local storage

Yes, let's do that.

Good, description added.

@TorstenStueber Let's store it in the localStorage. Zenlink has the same solution

@Sharqiewicz Updated the acceptance criteria, substrate connect wallet requirements


Debugger - Adding functionality to variable explorer.

Adding functionality to the variable explorer in debug mode.

Description and coloring of objects (such as Sprites).
Expand/contract objects and arrays.
Preview of arrays.

The coloring and design is subject to change.

Add screenshots or gif screen recordings.

We have:

Icons for expandable (and expanded) objects/arrays.
Expansion of objects and arrays.
Truncating long Strings and array's contents (and showing ...)
[To be changed] Colors for variables.

Closing as we'll be merging this changes in https://github.com/Microsoft/pxt/pull/5302.


Swapping between tabs on Ionic 2 for iOS has flickering white screen

Ionic version:  (check one with "x")
[ ] 1.x
[x] 2.x
I'm submitting a ...  (check one with "x")
[x] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
When swapping between ion tabs on ios device there is a brief moment of oblivion
Expected behavior:
Instant swapping of screens. No white flicker
Steps to reproduce:

Download the ionic 2 tabs starter template
Copy home content into about or contact template
Run on ios device or emulator (does not happen on browser)

Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
Cordova CLI: 6.4.0
Ionic Framework Version: 2.0.0
Ionic CLI Version: 2.2.1
Ionic App Lib Version: 2.2.0
Ionic App Scripts Version: 1.0.0
ios-deploy version: Not installed
ios-sim version: 5.0.4
OS: OS X El Capitan
Node Version: v6.9.4
Xcode version: Xcode 7.3.1 Build version 7D1014

I'm think this issue has been raised multiple times in the past but can't see any resolution on those posts other than updating Ionic. Now we're on 2.0.0 production I hoped this would have fixed it.

@adamhughes86 On a whim, I gave the WKWebView plugin another shot just now, and our app was able to launch (first time this has worked for me!). When running on WKWebView, I no longer see the flashing between tabs. You may want to give that a shot. https://github.com/driftyco/cordova-plugin-wkwebview-engine
For @jgw96, this issue may only apply to UIWebView.

@JustinPierce Not sure if I've installed that plugin right but it doesn't seem to be making a difference for me :(

+1 for WKWebView


Nightly: Update CPU and RAM in Nightly test

Updated the CPU and Memory in Nightly test and update kubernetes version
to 1.8
Signed-off-by: Eloy Coto<EMAIL_ADDRESS>

test-nightly

test-me-please

test-nightly

test-me-please

Hi @ianvernon
If you can review and merge if it's possible it'll be great. With this changes we can retrieve the Jenkins artifacts, and I can debug the Nightly issues on Monday.


Issues/kp 355 new search landing page filters

This PR is for adding search filters to search landing page.

The SidebarFilters and CollapsableFilters are now merged into one component called SearchFilers.


Out-of-order samples when relabeling metrics that contains timestamps.

What did you do?
Create an scrape job that scrapes cavisor and drops the id label using metric relabeling.
(This is the minimal working example for reproducing the issue, I've found it scraping cadvisor pods in a k8s cluster using prometheus' Kubernetes SD for discovery.)
What did you expect to see?
The metrics are scraped with the label id dropped.
What did you see instead? Under which circumstances?
A lot of Error on ingesting out-of-order samples errors in the logs. However, when it doesn't fail the metric is scrapped with the label correctly removed.
Environment

System information:

Linux 5.13.4-arch1-1 x86_64

Prometheus version:

prometheus, version 2.28.1 (branch: HEAD, revision: b0944590a1c9a6b35dc5a696869f75f422b107a1)
  build user:       root@2915dd495090
  build date:       20210701-15:20:10
  go version:       go1.16.5
  platform:         linux/amd64

Prometheus configuration file:

---
global:
  scrape_interval: 15s

scrape_configs:
  - job_name: 'cadvisor'
    static_configs:
      - targets: ['cadvisor:8080']
    metric_relabel_configs:
      - action: labeldrop
        regex: id

Logs:

level=warn ts=2021-07-26T18:06:28.352Z caller=scrape.go:1501 component="scrape manager" scrape_pool=cadvisor target=http://cadvisor:8080/metrics msg="Error on ingesting out-of-order samples" num_dropped=20
level=warn ts=2021-07-26T18:06:43.286Z caller=scrape.go:1501 component="scrape manager" scrape_pool=cadvisor target=http://cadvisor:8080/metrics msg="Error on ingesting out-of-order samples" num_dropped=643
level=warn ts=2021-07-26T18:06:58.281Z caller=scrape.go:1501 component="scrape manager" scrape_pool=cadvisor target=http://cadvisor:8080/metrics msg="Error on ingesting out-of-order samples" num_dropped=160
level=warn ts=2021-07-26T18:07:13.293Z caller=scrape.go:1501 component="scrape manager" scrape_pool=cadvisor target=http://cadvisor:8080/metrics msg="Error on ingesting out-of-order samples" num_dropped=1017
level=warn ts=2021-07-26T18:07:28.489Z caller=scrape.go:1501 component="scrape manager" scrape_pool=cadvisor target=http://cadvisor:8080/metrics msg="Error on ingesting out-of-order samples" num_dropped=877
level=warn ts=2021-07-26T18:07:43.288Z caller=scrape.go:1501 component="scrape manager" scrape_pool=cadvisor target=http://cadvisor:8080/metrics msg="Error on ingesting out-of-order samples" num_dropped=572
level=warn ts=2021-07-26T18:07:58.319Z caller=scrape.go:1501 component="scrape manager" scrape_pool=cadvisor target=http://cadvisor:8080/metrics msg="Error on ingesting out-of-order samples" num_dropped=767
level=warn ts=2021-07-26T18:08:13.353Z caller=scrape.go:1501 component="scrape manager" scrape_pool=cadvisor target=http://cadvisor:8080/metrics msg="Error on ingesting out-of-order samples" num_dropped=1050
level=warn ts=2021-07-26T18:08:28.316Z caller=scrape.go:1501 component="scrape manager" scrape_pool=cadvisor target=http://cadvisor:8080/metrics msg="Error on ingesting out-of-order samples" num_dropped=1070
level=warn ts=2021-07-26T18:08:43.470Z caller=scrape.go:1501 component="scrape manager" scrape_pool=cadvisor target=http://cadvisor:8080/metrics msg="Error on ingesting out-of-order samples" num_dropped=1073
level=warn ts=2021-07-26T18:08:58.355Z caller=scrape.go:1501 component="scrape manager" scrape_pool=cadvisor target=http://cadvisor:8080/metrics msg="Error on ingesting out-of-order samples" num_dropped=919
level=warn ts=2021-07-26T18:09:13.336Z caller=scrape.go:1501 component="scrape manager" scrape_pool=cadvisor target=http://cadvisor:8080/metrics msg="Error on ingesting out-of-order samples" num_dropped=523
level=warn ts=2021-07-26T18:09:28.328Z caller=scrape.go:1501 component="scrape manager" scrape_pool=cadvisor target=http://cadvisor:8080/metrics msg="Error on ingesting out-of-order samples" num_dropped=387
level=warn ts=2021-07-26T18:09:43.489Z caller=scrape.go:1501 component="scrape manager" scrape_pool=cadvisor target=http://cadvisor:8080/metrics msg="Error on ingesting out-of-order samples" num_dropped=486
level=warn ts=2021-07-26T18:09:58.320Z caller=scrape.go:1501 component="scrape manager" scrape_pool=cadvisor target=http://cadvisor:8080/metrics msg="Error on ingesting out-of-order samples" num_dropped=509

More info
cadvisor adds the timestamp to its metrics and if you add honor_timestamps: false to the scrape job the errors stop.
This makes me think that what is happening is that when the sample is relabeled the sample timestamp is replaced with the current time and stored like that, then when the next scrape happens if the sample still has the previous timestamp Prometheus says that is out-of-order as the latest sample known by Prometheus has a greater timestamp than the one from the sample.
Something like this:
Scrape 1 at time<PHONE_NUMBER>:

Sample: patata{type="frita",id="1234"} 1337<PHONE_NUMBER>
Is timestamp<PHONE_NUMBER> > timestamp of the last known sample by prometheus in patata series (no data in series yet)? No, continue.
Relabel, drop id. Result: patata{type="frita"} 1337<PHONE_NUMBER>
Store: patata{type="frita"} 1337<PHONE_NUMBER>

Scrape 2 at time<PHONE_NUMBER>:

Sample: patata{type="frita",id="1234"} 1337<PHONE_NUMBER>
Is timestamp<PHONE_NUMBER> > timestamp of the last known sample by prometheus in patata series<PHONE_NUMBER>)? Yes, drop sample and throw out-of-order sample ingestion error.

I created a docker-compose with a Prometheus config ready to go for reproducing this issue, just save this two files and run docker-compose up:

docker-compose.yml
---
version: '3'
services:
  cadvisor:
    image: gcr.io/cadvisor/cadvisor:v0.37.5
    ports:
      - 8080:8080
    volumes:
      - /:/rootfs:ro
      - /var/run:/var/run:rw
      - /sys:/sys:ro
      - /var/lib/docker/:/var/lib/docker:ro
  prometheus:
    image: quay.io/prometheus/prometheus:v2.28.1
    ports:
      - 9090:9090
    volumes:
      - ./prometheus.yml:/etc/prometheus/prometheus.yml

prometheus.yml
---
global:
  scrape_interval: 15s
scrape_configs:
  - job_name: 'cadvisor'
    # honor_timestamps: false
    static_configs:
      - targets: ['cadvisor:8080']
    metric_relabel_configs:
      - action: labeldrop
        regex: id

Ok after a further investigation is completely my fault. Removing the id label for cadvisor results in samples in the same scrape with the exact same set of labels with different values and timestamp, and was what was happening. I tried removing other labels that don't result in this and it works correctly.


Let all enabled modules participate in world configuration

Previously, only the module that defined the world generator and its dependencies participated in world configuration.  This allows the Cave module to present its settings alongside the default Perlin settings.

Refer to this link for build results (access rights to CI server needed):
http://jenkins.terasology.org/job/TerasologyPRs/346/
Hooray Jenkins reported success with all tests good!

Much cavey awesome!


No output files

Hi, first of all thanks for this wonderfully useful software!

Your pluginsFile threw an error from: /home/home/Documents/github/Laundry-IDs/cypress/plugins/index.js

Error [ERR_IPC_CHANNEL_CLOSED]: Channel closed
    at new NodeError (node:internal/errors:370:5)
    at ChildProcess.target.send (node:internal/child_process:724:16)
    at Object.send (/home/home/.cache/Cypress/9.5.4/Cypress/resources/app/packages/server/lib/plugins/util.js:32:25)
    at EventEmitter.<anonymous> (/home/home/.cache/Cypress/9.5.4/Cypress/resources/app/packages/server/lib/plugins/preprocessor.js:45:16)
    at EventEmitter.emit (node:events:406:35)
    at Object.removeFile (/home/home/.cache/Cypress/9.5.4/Cypress/resources/app/packages/server/lib/plugins/preprocessor.js:119:17)
    at Object.options.onBrowserClose (/home/home/.cache/Cypress/9.5.4/Cypress/resources/app/packages/server/lib/open_project.js:135:40)
    at EventEmitter.<anonymous> (/home/home/.cache/Cypress/9.5.4/Cypress/resources/app/packages/server/lib/browsers/index.js:212:19)
    at Object.onceWrapper (node:events:513:28)
    at EventEmitter.emit (node:events:394:28)
    at BrowserWindow.<anonymous> (/home/home/.cache/Cypress/9.5.4/Cypress/resources/app/packages/server/lib/browsers/electron.js:431:25)
    at Object.onceWrapper (node:events:514:26)
    at BrowserWindow.emit (node:events:406:35)

Unfortunately it never seems to scrape anything even after 30 minutes.

Hi there, thanks for letting me know about this issue. Just pushed an upgrade to the latest versions of Cypress and Node. Seems to be working again. Let me know if there's any other issues.


cAdvisor wont properly install on arm64/v8

W0224 21:55:03.758169       1 sysinfo.go:203] Nodes topology is not available, providing CPU topology
W0224 21:55:03.760123       1 machine.go:65] Cannot read vendor id correctly, set empty.

These messages are just warnings, they should not prevent the docker from working.


The garage directory will not been created automatically

The arg.save parameter will not been created successfully. Please open a branch so that I could fix it. Thanks

Have u already solved this problem? give me some guide please!

Have u already solved this problem? give me some guide please!


Update Get-FoxitReader to remove languages without out of date version

Get-FoxitReader returns languages automatically from the initial download URL that includes additional languages to those found at https://www.foxitsoftware.com/pdf-reader/.
This includes Portugese, Korean, Elex, Turkish - the versions returned for these languages are out of date and should be removed from the function output. This will require hard-coding languages in the FoxitReader.json manifest.

Released in 2104.355


Cannot set eastern position for map center

Seeing this in all architectures, cannot set the map center to 0E or anything further east than 1W. It will accept 0W but returns to setup on next boot with Err in the field.
Local builds on Debian and Raspbian don't reproduce this error.

This issue will be fixed in a future release of HamClock. It can also be resolved in the container build if I change the Docker base image from Alpine to something like Debian Bookworm-slim, but that increases the container image size by ~150 MB. Not terrible, but if I can avoid that for now I prefer to.
I will leave this issue open for tracking until HamClock updates.

@Aleziss can you see if the 3.06 version allows you to set an Eastern position for map center? You can either update your HamClock in place, or pull the latest Docker image from this project's repo.

Problem seems to be fixed now with the map centering in v3.06. 0E is working fine.
Thanks for the fix to both of you !


Add environment variable definitions in setup.sh

Also clean up redundant double slashes in paths in setup.sh.

Current coverage is 50.38% (diff: 100%)

Merging #283 into master will not change coverage

@@             master       #283   diff @@
==========================================
  Files             2          2
  Lines           909        909
  Methods          42         42
  Messages          0          0
  Branches        195        195
==========================================
  Hits            458        458
  Misses          368        368
  Partials         83         83

Powered by Codecov. Last update 95841d4...924d80a

Let's wait until the CI tests pass after I updated this PR by merging in from master. But after that, everything
LGTM

LGTM. All tests have passed so I'll merge and come this.
@zbeekman Stavros is waiting for this merge so I'll tell him it's ok to clone now.  Let's release tomorrow if possible.


Added XML test.

#427
Added XML generation test.

Actually, I saw that you are using an UML xml file as input for the tests. We decided to only use the templates related to the Entity infrastructure increment:

ApplicationPersistenceEntity
ApplicationEntity
{variables.className}Entity
{variables.className}

The rest will be discarded because we are trying to implement a multi-step generation. See this project and this issue.
Maybe you should change your input file.


can the background match my current theme?

is there a way to have blockmans backgrounds match my current theme (very light gray)?

Please try this:
"blockman.n33A01B2FromDepth0ToInwardForAllBackgrounds": "10,0,0,1; none",
Here, none does not mean transparent background, it means it will have the same color as VS Code editor background.
Well, yeah, transparent would be better thing, but because of some styling limitations of VS Code extensions, Blockman does not work well with transparent colors.


Add isRequired PropType for Checkbox, Radio

Needs a changelog entry. You'll need to run yarn test:jest -u to update snapshots too

Nice work. LGTM once Giles's comments are addressed.

I've added changes to the Changelog and updated the snapshots


Cherry-pick commit Support intermediate aggs in Orca plans (#13707)

Here I cherry-picked commit Jun 28, 2022 Support intermediate aggs in Orca plans (#13707) https://github.com/greenplum-db/gpdb-archive/commit/5bf9fd5d0fa616f7ad64fb51f6b385fb526fb62f
This commit conflicts with https://github.com/apache/cloudberry/commit/0a2bc5d61e713e3fe72438f020eea5fcc90b0f0b Move per-agg and per-trans duplicate finding to the planner. - refactoring made by hlinnaka@
The interesting thing is that the commit is from November 24th, 2020 (which is more than a year older than the CBDB fork date) and is absent in the original gpdb repository. Also, I didn't find a PR where it was committed. It seems for me like a CBDB feature.
So I decided to create separate PR only for that commit

Fixes #ISSUE_Number
What does this PR do?

Type of Change

[ ] Bug fix (non-breaking change)
[ ] New feature (non-breaking change)
[ ] Breaking change (fix or feature with breaking changes)
[ ] Documentation update

Breaking Changes

Test Plan

[ ] Unit tests added/updated
[ ] Integration tests added/updated
[ ] Passed make installcheck
[ ] Passed make -C src/test installcheck-cbdb-parallel

Impact

Performance:

User-facing changes:

Dependencies:

Checklist

[ ] Followed contribution guide
[ ] Added/updated documentation
[ ] Reviewed code for security implications
[ ] Requested review from cloudberry committers

Additional Context

⚠ To skip CI: Add [skip ci] to your PR title. Only use when necessary! ⚠

need waitting the ic-good-opt-on enable... current CI have not cover the ORCA in ICW tests..

need waitting the ic-good-opt-on enable... current CI have not cover the ORCA in ICW tests..

@edespino Ed, appreciate your help on it.

need waitting the ic-good-opt-on enable... current CI have not cover the ORCA in ICW tests..

@edespino Ed, appreciate your help on it.

I have a branch with the changes. My repos's workflow is running: https://github.com/edespino/cloudberry/actions/runs/12115945979

@my-ship-it & @jiaqizho
My branch has a single commit based on this PR branch that is necessary to enable the ic-good-opt-on  test configuration. Please note, it may have diffs that may or may not be related to this PR.
My branch: https://github.com/edespino/cloudberry/tree/refs/heads/CherryPickOrcaFeb2023_3-ic-good-opt-on
My workflow: https://github.com/edespino/cloudberry/actions/runs/12115945979

It seems to me that the ic-good-opt-off tests are flaky.
@edespino Ed, appreciate you help. ic-good-opt-on tests from Ed branch are green.

@leborchuk @jiaqizho We need to investigate what flaky and fix them, thanks!

It seems to me that the ic-good-opt-off tests are flaky.
@edespino Ed, appreciate you help. ic-good-opt-on tests from Ed branch are green.

Thanks for flagging this. Since these flaky test failures involve the orca query optimizer behavior, we should first have an engineer familiar with the orca query optimizer review the test issues. Once they can determine whether this is a product issue or an environmental/infrastructure problem, I can assist with any infrastructure-related fixes needed. Please loop me back in after that assessment.

I see here only failed
test uao_compaction/stats         ... FAILED      333 ms (diff  123 ms)
test uao_compaction/index_stats   ... FAILED      575 ms (diff  139 ms)
test uao_compaction/index         ... ok          161 ms (diff   59 ms)
test uao_compaction/drop_column   ... FAILED      165 ms (diff  122 ms)
``` tests in Apache Cloudberry Build / ic-good-opt-off (pull_request) workflow run

I'm sure they will succeed if I run them again. (I cannot do it myself; I do not have the rights to launch the tests one more time.)

I opened issue to fix it - https://github.com/apache/cloudberry/issues/789

rebase pls. ic-good-opt-on already added in CI

CREATE SEQUENCE complex_seq CACHE 1;
CREATE TABLE complex_ttbl (id INT4 DEFAULT NEXTVAL('complex_seq'), c COMPLEX) DISTRIBUTED BY (c);

INSERT INTO complex_ttbl(c) VALUES (COMPLEX(NEXTVAL('complex_seq'), NEXTVAL('complex_seq')));
INSERT INTO complex_ttbl(c) VALUES (COMPLEX(NEXTVAL('complex_seq'), NEXTVAL('complex_seq')));
INSERT INTO complex_ttbl(c) VALUES (COMPLEX(NEXTVAL('complex_seq'), NEXTVAL('complex_seq')));
INSERT INTO complex_ttbl(c) VALUES (COMPLEX(NEXTVAL('complex_seq'), NEXTVAL('complex_seq')));
INSERT INTO complex_ttbl(c) VALUES (COMPLEX(NEXTVAL('complex_seq'), NEXTVAL('complex_seq')));
INSERT INTO complex_ttbl(c) VALUES (COMPLEX(NEXTVAL('complex_seq'), NEXTVAL('complex_seq')));

INSERT INTO complex_ttbl(c) VALUES (COMPLEX(0, 0));
INSERT INTO complex_ttbl(c) VALUES (COMPLEX(0, -0));
INSERT INTO complex_ttbl(c) VALUES (COMPLEX(-0, 0));
INSERT INTO complex_ttbl(c) VALUES (COMPLEX(-0, -0));
SELECT COUNT(c) = 4 AS tr, COUNT(DISTINCT gp_segment_id) = 1 AS tr
	FROM complex_ttbl
	WHERE re(c) = 0 AND im(c) = 0;

hi @leborchuk,  check this case pls, i think executor missing some implements..


[AppConfig] Update appconfig help messages

Related command

Description
This PR updates the app config help messages. It updates the string  "App Configuration" to "App Configuration store", updates "keyvalues" strings to "key-value" and adds  the actual argument name in the description for the auth-mode.
Testing Guide

History Notes

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

[x] I adhere to the Error Handling Guidelines.

AppConfig

@yanzhudd or @zhoxing-ms this PR changes have been approved by @albertofori please help merge when you get some time.


Fixed Flakey Monitoring Test Backport 2.7

Issue: https://github.com/rancher/qa-tasks/issues/647
backport 2.7
Problem
Monitoring tests in validation were failing due to changes in configuration for alerts.
Solution
Modified the configuration of routes and receivers for alerts so they would successfully be configured and setting an alert could be verified.

I've got a few questions about the changes. Also, I just realized that there's a missing error check here https://github.com/rancher/rancher/blob/release/v2.8/tests/framework/extensions/charts/charts.go#L197. And I think it might be a false pass. Could you add an error check to this watch wait and run the test again?

This was how the original monitoring test was written. I didn't modify this part. Do I need to add an error check to the WatchAndWaitDeploymentForAnnotation method?

Yes, this was something that I had missed. Its main job is to watch the annotation of the deployment.
Even though it shouldn't be a failing point until now, a pod restart policy change might affect and we might want to see the results of it and update the extension. This change can also include watch times, or if it takes more than its watch time, we might want to simply log it


Possible mitigation for Python smoke flakes

I got it to flake... but it flaked on Vault not on Python.  Fie!

@itowlson is this change still something we'd like to get in?


gpt-4-1106-preview only has 4096 tokens?

I got this error while trying to generate with gpt-4-1106-preview:
Generating with model: gpt-4-1106-preview ...
Error while generating: Error code: 400 - {'error': {'message': 'max_tokens is too large: 5500. This model supports at most 4096 completion tokens, whereas you provided 5500.', 'type': 'invalid_request_error', 'param': 'max_tokens', 'code': None}}
This seems unexpected, since max_tokens is supposed to have a much higher ceiling than that.
Anyone now what could be happening? Thanks.

Same error as well. It also shows this error when I try on playground.

Just checked and I'm getting a similar error for gpt-3.5-turbo-1106.

These models can only output 4096 tokens but input tokens are 128k for 4 turbo and 16k for the new 3.5 turbo

Each of the new models returns a maximum of 4,096 output tokens. This includes:

GPT-4 Turbo gpt-4-1106-preview
GPT-4 Turbo with vision gpt-4-vision-preview gpt-4-1106-vision-preview
Updated GPT 3.5 Turbo gpt-3.5-turbo-1106

Thanks for adding the context Keith & dosen!

But why? This breaks a lot of apps... it used to work


Initial Tables API

This is a naive and incomplete binding to the ImGui Tables API.

APIs are thin rust wrappers around their C++ counterparts.  I believe I've followed the naming convention for overloads.
A couple of Table APIs are not implemented yet (I didn't have immediate need for them and they weren't dead-trivial to implement).
setup_columns_with_id uses an Id function from my docking2 branch.
I've not yet written doc comments.

This draft PR is to get a review on the general approach for the Tables API.  In my own experiments, I like the look of Tables much better than what I can achieve with the Columns API:
Example
Signed-off-by: Chris Frantz<EMAIL_ADDRESS>

Thank you for the PR! Will take a look ontight

Apologies for the delay -- I'm actually currently moving so things are slightly delayed!

Looked over this -- everything looks good, though table_begin should return a Token, since we typically use RAII instead of begin/end patterns.
I'd like to finish this work and will work on this branch, if that's alright with you? That mostly will mean adding doc comments and changing some of the code

Sounds good to me.

something messy happened in the git history there -- i'll do an interactive rebase when i merge this into main. it's not done though

@cfrantz I'm going to merge this in in soon. please let me know if you have any thoughts since you were the one kind enough to do the initial work on it!

merged manually -- we had some issues with updating to 1.84 that required me to update some submodules and made some issues automatically merging!
Thank you for starting this effort!


Items and help needed for a new release?

I wondered about the plans for a new release and what help might be needed to make it happen? There was some talk about beefing up the documentation for the next release, but I'm unsure what needs to be done since I found everything I needed in the docs.

Hey thanks for the comment and appologies for the slow uptake.
There's larger work being done on crispy-forms core but I think we can go ahead and get a release of this template pack out now.
Good to hear you found everything in the docs 👍


[linux] Add 6.0

https://lkml.org/lkml/2022/10/2/255
https://www.kernel.org/

Thanks for the review. I updated the requested changes. Please check again @usta

Thanks for the review. I updated the requested changes. Please check again @usta

sorry for late reply, it looks good for me thanks 👍 💯 🥇 🎉


Only hit short_path validation if short_path is present

Sorry for the delay on this, it solves issue #340

Looks good. Can you fix that one failing spec?

Hi there,
Curious as why this is failing, it's something i'm not understanding. The save works fine but when calling .reload it is checking the validation? Why is reload hitting the validation?

@greggawatt: Here's what's happening:
The failing test is re-running the validation because that line is calling #valid?.
The validation is failing because of how create_redirect and redirect_source_path_unique interact: create_redirect is creating a new Redirect object with the given short_path.  redirect_source_path_unique checks to see if a Redirect with the given short_path exists, which it does because we just created one.  This means articles with short_paths can never be edited because the validation will fail on subsequent saves.
My recommendation is to add a redirect association to the article model.  The association should be dependent so that the redirect is deleted if the article is deleted.  If short_path, published_at, or slug change on save, run the validation and update the values on the existent redirect.  If none of those fields change we can skip the validation.
Let me know if any of that was confusing or I can help explain anything else.

This seems good at first read. But I've got chemo brain right now. Let me revisit this in a day or two with clearer mind grapes.

Thank you. Feel better ❤
On Fri, May 12, 2017 at 9:36 PM Shane Becker<EMAIL_ADDRESS>wrote:

This seems good at first read. But I've got chemo brain right now. Let me
revisit this in a day or two with clearer mind grapes.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/crimethinc/website/pull/357#issuecomment-301224657,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AApquEiPDCCLbzta-JsQHr0h-F7jrZMXks5r5TNVgaJpZM4NIWV4
.

--
Gregg Horton
510-283-8734
gregghorton.com

👍🏻
PS. You know when you reply via email, your signature (including phone number) is posted publicly?

@greggawatt Did @guitsaru's answer make sense? You think you can get this buttoned up?

I think so, I've been overwhelmed this week. I'll try to take a look tonight and see if I can make progress.

@guitsaru Hey there, I was able to start this, added an article_id to redirects. I'm kinda confused about a few things

should articles have more than one redirect? (i say yes)
redirect_source_path_unique seems to not currently make sense on update, only on create. Not sure if it's even needed then.
I looked up how to do validations on change, should i have one validation for each field or is there a more elegant way to solve it.

Sorry for all the questions, just trying to wrap my head around the best way to do this.

I'm getting failures with heroku CI and i don't have access, could someone post the error?

Hey @greggawatt, thanks for jumping back in to try and get this finished.
Don't worry about the questions; I'm happy to them.

I can see instances where articles have multiple redirects, but in this instance there will only be one redirect that matches short_path.  I'd probably keep it at one redirect until we know we need more.  In the case where we would want multiple redirects the source_path will be different on all of them so your current method of looping through all redirects to update it won't work.

I think the logic in redirect_source_path_unique should be run any time a redirect's source_path will be changed.  You're currently duplicating the logic in update_redirect_source_paths.  It's really up to you how you want to structure this.

I noticed you're doing the redirect update as a validation when it should probably be an after_save or a before_save.  To do this on any column change I'd probably not do an if clause on the before_save statement, but move it into the method itself:

before_save :update_redirects

def update_redirect
  return true unless source_path_changed? || slug_changed? || published_at_changed?
  ...
end

This is probably what I'd do for validations that depend on column changes as well.

The redirect actually does keep track of these, just indirectly.  target_path is composed of the published_at date and the slug.  If either of these change, we'll want to update the redirect to reflect that.  This is not a super common occurrence, but we'll want to handle it anyway.

I hope that answers everything; don't hesitate to ask if you have any followups or any other questions come up.
I'll take a closer look at the code later.

Also, don't worry about the Heroku failure.  It's just using the wrong version of ruby.  We have a support ticket in with them to fix it.

Hi there,
I cleaned up a lot of the code so it's a little simpler, please take a look.

Just pinging on this, I can fix the conflict if the rest of the code looks good

@greggawatt Hey sorry for recent radio silence. Chemo's had me distracted. The rest of your PR looks good to me. If you fix up the merge conflicts, I'll merge it in. Sorry for the delay.

No worries, here you are conflict free!

@guitsaru Will you give this a final look before I merge it in, please?

Sorry for the wait.
It looks like it covers all of the use cases.  I think it's good to merge.

Thanks @guitsaru. No sorry necessary. :D

@greggawatt Thanks for sticking with this through the very slow process of getting it landed on master. ⭐⭐⭐⭐
@guitsaru Thanks for helping me review it as it moved along. ⭐⭐⭐⭐

Thank you!!!