[Performance] Reduce Redundant Operations

Problem
In our getOrderedReportIDs  we have loops like forEach and sort. In there, we are invoking many utils functions and some of them have static translations in there. Which translates the same text on each loop iteration. For the lots of data, this becomes an issue for the application. Apart from this, we also have formatPhoneNumber  which parses the passed number and this util function leverages awesome-phone-number library. With further investigation, it appeared that the number we are trying to parse, might not be a number at all. It can also be an email like<EMAIL_ADDRESS>and it is not ideal to parse an email from a phone number library.
Solution
For translations, we created a separate file and there we are translating the text that was repeatedly reported in our audit. We also have Onyx connection to locale key, so if locale changes we have all the updated translations.
For phone number, we can early return if the passed number is a string or if it doesn’t contain sms domain.
https://github.com/Expensify/App/pull/37200

Hi @muttmuure 👋  Please assign this to me 👍

Done!

@fedirjh invited you to this job: https://www.upwork.com/jobs/~010796b6f68d39c46b

Offer sent

Paid. Closing out


Original Color Theme Is Overwritten When Restarting VS Code

Testing #145616
Steps:

Set a color theme in VS Code (no high contrast) -> Works
Enable high contrast theme in OS (Windows) -> VS Code switches to high contrast theme
Restart VS Code -> VS Code stays in high contrast theme
Disable high contrast theme in OS -> VS Code stays in high contrast theme!

For step 4, I would have expected that VS Code would go back to the normal color theme.
When leaving out step 3, it does so.

Yes, I know it's inconsistent, but it's something we do on purpose: Never switch away from a high contrast theme on restart. IMO it's time to remove that. @bpasero any objections?

No, feel free to change.


[BUG] Cannot add Data File Name column

Describe the bug
As @HLWeil mentioned in #201, it's currently not possible to add Data File Name to a swate table.
To Reproduce
You get a warning ("Swate table contains already one output column "Sample Name". Each Swate table can only contain exactly one output column type.").
Once you delete the Sample Name column, you can add a Data File Name.
Additional context
If I'm not mistaken, the idea was:
Sample Name and Data File Name columns are both considered "output" nodes and every assay can only either output to another sample (e.g. an extraction: plant sample - extraction - extracted plant sample) or to data (e.g. extracted plant sample - measurement - data).

Suggestion:
By default swate tables have Source/Sample columns. When trying to add a Data File Name, let swate replace the Sample Name column and display a message accordingly (~ "Sample Name" was replaced by "Data File Name"... )


emit_count_metrics has wrong name

Describe the bug
While digging through code I think I found a bug where emit_count_metrics has the wrong metrics_create name.
https://github.com/fluent/fluentd/blob/b28f7d70dac657cb390aabc56dcfee8857975b4b/lib/fluent/plugin/bare_output.rb#L73-L74
Both emit_count_metrics and emit_records_metrics call metrics_create(namespace: "fluentd", subsystem: "bare_output", name: "emit_records") with just different help_text. It seems like emit_count_metrics should have the name emit_count.
To Reproduce
Look at https://github.com/fluent/fluentd/blob/b28f7d70dac657cb390aabc56dcfee8857975b4b/lib/fluent/plugin/bare_output.rb#L73-L74
This also shows up in a few more places.
Expected behavior
Honestly, I expected fluentd_output_status_emit_count and fluentd_output_status_emit_records from the prometheus plugin to not look identical, which took me down a rabbit hole and led me here.
Your Environment
N/A, just digging through code

Your Configuration
k8s 1.21 in GKE

Your Error Log
N/A

Additional context
No response

@danielhoherd thank you for reporting!
Fixed via #3630


[BUG] Widgets are not sending X-Api-Key and Authorization headers

Environment
Self-Hosted (Docker)
System
Firefox 125.0.2
Version
3.0.0
Describe the problem
Summary: Widgets are not sending the X-Api-Key and Authorization headers.
This is based on troubleshooting the issue I posted in the 3.0.0 discussion https://github.com/Lissy93/dashy/discussions/1537#discussioncomment-9183382
Description: After upgrading to version 3.0.0 I noticed that my HealthChecks and Uptime-Kuma widgets were no longer working and failed with "Proxy returned error from target server". Looking in the console log (attached below), the proxy server was getting a 401 error from HealthChecks. Both HealthChecks and uptime-kuma servers are running on my local network and were working in Dashy version 2.1.2. After troubleshooting I've come to the conclusion that Widgets are not sending appropriate key/auth headers to the server endpoints. Both non-working widgets are supposed to send a header with this.makeRequest(this.endpoint, authHeaders). However, those headers are not being sent. The Weather widget works fine, which makes sense because for that widget, the apiKey is appended to the url instead.  It appears the headers are being sent to the Dashy cors proxy, but they are not being forwarded to the server. Details below.
Troubleshooting: I set up a new instance of Dashy using the default config to make sure nothing in my config was wrong (see example below), but it still had the proxy error. Using curl to query the endpoint from the host returns the proper response. Additionally, querying the endpoint within the Dashy container returned a correct response using docker exec -it dashy curl -H "X-Api-Key: yMu9uTiVQDCWas3hnRwlWTm22kAc4APY" http://<IP_ADDRESS>:3002. Finally, attempting the request in Firefox with the "Allow CORS" addon activated still failed.
Indeed, HealthChecks was rejecting the request with a 401 error:
    04/24/2024
    04:14:18 AM
    [pid: 188|app: 0|req: 1815/1886] <IP_ADDRESS> () {28 vars in 397 bytes} [Wed Apr 24 04:14:18 2024] GET /api/v1/checks => generated 0 bytes in 3 msecs (HTTP/1.1 301) 6 headers in 219 bytes (1 switches on core 0)
    04/24/2024
    04:14:18 AM
    [pid: 188|app: 0|req: 1816/1887] <IP_ADDRESS> () {28 vars in 399 bytes} [Wed Apr 24 04:14:18 2024] GET /api/v1/checks/ => generated 28 bytes in 1 msecs (HTTP/1.1 401) 11 headers in 374 bytes (1 switches on core 0)

These pieces of evidence led me to believe it was an issue with Dashy.
I intercepted the request and found that the X-Api-Key header was not being sent to the HealthChecks endpoint. These are the intercepted headers sent to HealthChecks, note the absence of the X-Api-Key header that should contain the apiKey passed in the config:
{
    accept: 'application/json, text/plain, */*',
    'user-agent': 'axios/1.6.8',
    'accept-encoding': 'gzip, compress, deflate, br',
    host: '<IP_ADDRESS>:3002',
    connection: 'keep-alive'
}

Interestingly, the x-api-key header was being sent to the Dashy cors proxy when looking in the console log, but was not being forwarded on:
GET /cors-proxy HTTP/1.1
Host: <IP_ADDRESS>:4000
User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:125.0) Gecko/20100101 Firefox/125.0
Accept: */*
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Referer: http://<IP_ADDRESS>:4000/
target-url: http://<IP_ADDRESS>:3002/api/v1/checks
x-api-key: yMu9uTiVQDCWas3hnRwlWTm22kAc4APY
DNT: 1
Connection: keep-alive

Additional info
Deprecation warning: The simple-icons entrypoint will be removed in the next major. Please switch to using import * as icons from "simple-icons/icons" if you need an object with all the icons. index.js:1:8
Dashy  V3.0.0 🚀 CoolConsole.js:6:10
XHRGET
http://<IP_ADDRESS>:4000/cors-proxy
[HTTP/1.1 500 Internal Server Error 16ms]
{
  "error": {
    "message": "Request failed with status code 401",
    "name": "AxiosError",
    "stack": "AxiosError: Request failed with status code 401\n    at settle (/app/node_modules/axios/dist/node/axios.cjs:1966:12)\n    at IncomingMessage.handleStreamEnd (/app/node_modules/axios/dist/node/axios.cjs:3065:11)\n    at IncomingMessage.emit (node:events:530:35)\n    at endReadableNT (node:internal/streams/readable:1696:12)\n    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)\n    at Axios.request (/app/node_modules/axios/dist/node/axios.cjs:3876:41)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)",
    "config": {
      "transitional": {
        "silentJSONParsing": true,
        "forcedJSONParsing": true,
        "clarifyTimeoutError": false
      },
      "adapter": ["xhr", "http"],
      "transformRequest": [null],
      "transformResponse": [null],
      "timeout": 0,
      "xsrfCookieName": "XSRF-TOKEN",
      "xsrfHeaderName": "X-XSRF-TOKEN",
      "maxContentLength": -1,
      "maxBodyLength": -1,
      "env": {},
      "headers": {
        "Accept": "application/json, text/plain, */*",
        "User-Agent": "axios/1.6.8",
        "Accept-Encoding": "gzip, compress, deflate, br"
      },
      "method": "get",
      "url": "http://<IP_ADDRESS>:3002/api/v1/checks",
      "json": {}
    },
    "code": "ERR_BAD_REQUEST",
    "status": 401
  }
}

GET /cors-proxy HTTP/1.1
Host: <IP_ADDRESS>:4000
User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:125.0) Gecko/20100101 Firefox/125.0
Accept: */*
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Referer: http://<IP_ADDRESS>:4000/
target-url: http://<IP_ADDRESS>:3002/api/v1/checks
x-api-key: yMu9uTiVQDCWas3hnRwlWTm22kAc4APY
DNT: 1
Connection: keep-alive

⚠ Warning ⚠
Proxy returned error from target server
This is likely not an issue with Dashy, but rather your configuration.
If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
Request failed with status code 401 CoolConsole.js:18:12
Uncaught (in promise) TypeError: t.checks is undefined
    processData HealthChecks.vue:80
    fetchData HealthChecks.vue:72
    promise callback*dac2/fetchData/< HealthChecks.vue:71
    fetchData HealthChecks.vue:69
    mounted WidgetMixin.js:26
    VueJS 25
    o WidgetBase.vue:1
    VueJS 24
HealthChecks.vue:80

Please tick the boxes

[X] You have explained the issue clearly, and included all relevant info
[X] You are using a supported version of Dashy
[X] You've checked that this issue hasn't already been raised
[X] You've checked the docs and troubleshooting guide
[X] You agree to the code of conduct

Confirmed with my Proxmox list widget. The reason is a change or a bug in the internal API. Most probably related to this commit
https://github.com/Lissy93/dashy/commit/f353780ad4508ed8a91c545c96a423cca5147f35
It looks like that the widget mixin used to collect all headers passed to the makeRequest method in a CustomHeaders header that is passed to the cors-proxy. This is broken now, and no headers are passed to the cors-proxy.
I confirmed the bug by manually passing the CustomHeaders header like this
    authHeaders() {
      if (this.userName && this.tokenName && this.tokenUuid) {
        const auth= { Authorization: `PVEAPIToken=${this.userName}!${this.tokenName}=${this.tokenUuid}` }
        return { CustomHeaders: JSON.stringify(auth)};
      }
      return false;
    },

I can send a PR for my widgets, but before that I think @Lissy93  should have a look at the code, and decide whether the widgets should be responsible for this CustomHeaders, or the mixin will be fixed to take care of it.

Thanks @alayham - this should be fixed in 3.0.1

I'm still seeing the issue in 3.0.1.

@Lissy93 I have  Confirmed that the issue still exists in the latest commit, and that my patch above resolves it for my Proxmox widgets.

Should be fixed in #1576 :)

Confirmed, the fix resolved the issue for me.


Options list closes on select in tags mode even with closeOnSelect set

Version

Vue version: 3

Description
Seems to be a bug where options closes after selecting an option. If using mode="tags" and :searchable="true" even if :close-on-select="false" . Also seems related to another bug where option list does not open on search focus which is described in this ticket #286
confirmed it is working correctly in 2.5.6
Demo
You can see it not working example #5 in https://jsfiddle.net/t421d7cg/

Still closing for me anyone to something about it ?


Can add skip Unmarshup?

Most of query service, just only need marshup.

Duplicate of #43 ?

Added proposal as PR #70

#70 is merged, thanks!


docs: various topics update

put how_to_setup_object_storage / p8s_metrics into the reference directory
add #warning-log-block-not-found-in-object-storage section, content copied from EE
explain --hash-prefix and --compress
rename #writeback into #client-write-cache to align with EE

awaiting approval from @davies or @xiaogaozi


Expectation/matcher for the app being in background?

Description
It would be nice to have a matcher/expect statement for the app being in background. For example, if I want to check that pressing on a button sends the user to the settings, I would be able to do
  it('Should send the user to the settings', async () => {
    await element(by.id('settingsButton')).tap();
    await expect(element(by.id('CurrentScreen'))).toBeNotVisible();
  });

@kirakik is this still relevant for you or can we close the issue?

No longer relevant, I’ll close this!


ERROR (MainThread) [root] https://api-iot.he.services/commands/v1/context - Error 403 - {"Message":"User is not authorized to access this resource with an explicit deny"}

Repeated error:

Hey, this is implemented a bit dirty at the moment, the token expires after 8 hours and if a HTTP error 403 is thrown, a new login is made. I will change it so that a new token is requested cleanly via the refresh token. I had prepared this in the last version and will try to finish it soon 🙂

Good job. Thank you.


Add Istio's mesh mode

Since Gateway API v0.4.0, Istio supports Mesh Traffic:
https://istio.io/latest/docs/tasks/traffic-management/ingress/gateway-api/#mesh-traffic
this should be included in the test/controller implementation.

/lifecycle frozen

re-opened this since it should probably be closed by a user vs. a bot


fix: use npm instead of http

What does this PR do?
Replaces http commands in favor of npm commands
What issues does this PR fix or reference?
@W-9642544@

Nice work getting all this cleaned up. Plugin-trust is super critical because it'll completely block plugin instalation if it's not working OK.
I'd like to see a NUT for this that

installs any known, good signed plugin (ex: plugin-user)
verifies it installs without the error message
puts an unsigned plugin on the allowlist
installs some known good unsigned plugin (see list https://github.com/mshanemc/awesome-sfdx-plugins.  I'd suggest Jochen's jayree plugin)
installs some unsigned plugin not on the allow list to verify the warning is happening

I'm not sure if there's a good NUT way to verify that this change solves private npm registry, but the NUT I'm describing would verify that the normal public repository functionality isn't impacted by these changes.

Hi @mshanemc I added the NUTs you suggested, luckily sfdx-trust and plugin-trust don't interfere with each other. because at this point we've both installed at the same time.

QA: can verify existing plugins are signed
published a private plugin at @salesforce/private-plugin-user which can be found if I'm auth'd on npm (but verifies as not-signed) and 404's when I logout of npm


Improve new constant color

VSCode Version: 1.45.0 (d69a79b73808559a91206d73d7717ff5f798f23c)
OS Version: MacOS Catalina 10.15.3

Variable highlighting is all over the place, there seems to be a new type of highlighting for a local variable, but its confusing/annoying.
The shade for it is too close to the unused variable color.
Steps to Reproduce:

Create a new File
Set the language to JS
Paste the snipped

function name(test) {
    const unused = 'unused';
    const { ola } = test;
    const test2 = ola.another;
    return { ola, test2 };
}

Does this issue occur when all extensions are disabled?: Yes/No
Yes
EDIT:
And if you access a prop from a shaded variable, the prop is not shaded, as shown in the ola.another.
If you use the variable inside an object it also doesn't get shaded. It looks like a diff variable.

This seems to be part of the new update https://code.visualstudio.com/updates/v1_45#_new-color-for-constants-in-the-default-dark-theme
However I wish they also provided a way to revert the change in that changelog because it makes it impossible to distinguish for me as well.

Same for TypeScript. Really poor choice of color here from the team.
Would love to disable this change or at least be able to override the color.

Would love to be able to disable this. As it looks now it seems all const variables are unused!

And if you access a prop from a shaded variable, the prop is not shaded, as shown in the ola.another.
If you use the variable inside an object it also doesn't get shaded.
@rauenzi did you find how to disable? I couldn't figure it out.

Got a fix that overrides the constants to their old value in default dark +. Add the following to the settings.json:
  "editor.tokenColorCustomizations": {
    "textMateRules": [
      {
        "scope": ["variable.other.constant", "variable.other.enummember"],
        "settings": {
          "foreground": "#9CDCFE"
        }
      }
    ]
  },

Got a fix that overrides the consts (and enums, these have the same shade) to their old value in default dark +. Add the following to the settings.json:
  "editor.tokenColorCustomizations": {
    "textMateRules": [
      {
        "scope": ["variable.other.constant", "variable.other.enummember"],
        "settings": {
          "foreground": "#9CDCFE"
        }
      }
    ]
  },

It works perfect :clap:! The new color looks too dark (it seems unused :disappointed:)

Please use the following setting if you prefer the previous coloring:
    "editor.tokenColorCustomizations": {
        "[Default Dark+]": {
            "textMateRules": [
                {
                    "scope": ["variable.other.constant", "variable.other.enummember"],
                    "settings": {
                        "foreground": "#9CDCFE"
                    }
                }
            ]
        },
        "[Default Light+]": {
            "textMateRules": [
                {
                    "scope": ["variable.other.constant", "variable.other.enummember"],
                    "settings": {
                        "foreground": "#001080"
                    }
                }
            ]
        }
    }

This needs to be a setting. As a person with impaired color vision it totally defeats the purpose of dimming unused variables. Side by side I can distinguish them with some efforts, but at a glance I cannot discern if there is a difference.

Here's a couple of variations that we've been exploring for the Dark theme. The intent is try to stay close to the "blue" color range so as to not be too different. You can test these out by using the instructions above.
Option 1 #8F9DFF

Option 2 #4FC1FF

Option 3 #82DFE8

Option 4 #3CD9E8

Once we've identified a version that works better we'll move to exploring one for the Light theme:

That's great. Personally, I will test option 2 for a while. Thanks!

I also like 2 the most.

I think this feature should be optional. I personally don't want to have separate color for constants. It only makes reading code harder, and does not worth it.

I also do not understand the benefit/need to separate color for constants. It makes no sense and the options above are not great. Why do we need a rainbow of colors? Whoever is doing that obviously doesn't work with VSCode on daily basis. Your last update for constants messed with a lot of people.
Imagine you come in to the office and your office is upside down. This is how I felt when I opened my laptop in the morning to work but instead spend hours debugging VSCode and searching for solution online. Finally asking you for the override to the original colors.


pull request for e2e test at 01/22/2017 08:45:15

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


no parameters in response

when I use the node library, the responses don't have any parameters, ie identified entities.
when I use the preview test console, or the copied curl query, the parameters do appear.
Is there some limitation to how the nodeSDK uses the text query? It seems somehow missing a lot of data in the response.
https://discuss.api.ai/t/parameters-dont-come-back-in-response/4815

Hi @dcsan,
See this example.
You shall pass language parameter for languages for non-english languages. So, this parameter default using as language of agent, but this is feature available only for console. In API you shall pass it yourself.

@sstepashka could you post the link example again? , it seems it's broken, thanks

yes there's nothing in the pointed directory except one file:
https://github.com/api-ai/apiai-nodejs-client/tree/master/examples
what param should we pass for language?


Youtube background stops after a while

Last week I got a new phone (Huawei Honor 10, COL-AL10) which has a newer Android version, 8.1.0
I downloaded the same addon, the firefox does play on background, but after a few songs, it stops.
When I unlock the phone again sometimes it starts playing next song (and I don't even have to open firefox)
But sometimes Youtube in Firefox shows this error "Invalid Response Received"
I looked around my phone, I found a setting which stated that screen off disables some WLAN connections, I disabled it.
Under battery management disabled all savings.
After these change, it still does not work.
There is an app called "stay alive", which is supposed to keep connections alive, but even that does not work and as soon as the phone goes sleep, no more connections pass through.
Currently, I am using an app "touch protector" to keep the screen alive.
Is there some way for your app to disable some settings what I as the user can't change so that my phone never loses connections?
Or my only option is to change Huawei software?
And can I even run for example Pixel 2 software on Huawei or every phone has to have its own software compatible with firmware?

This extension is only intended for the case where a web site itself blocks background playback. It cannot influence anything that's happening between Firefox and Android. Regarding manufacturers that use some overzealous power optimisation "features" (which apparently includes Huawei), even Firefox itself won't be able to change that kind of system settings.

Under battery management disabled all savings.

Was there any option to whitelist specific apps, and did you try whitelisting Firefox specifically?

And can I even run for example Pixel 2 software on Huawei or every phone has to have its own software compatible with firmware?

Each phone model requires its own customised firmware. Some googling  suggests that LineageOS builds are available for your phone, but installing a custom ROM shouldn't be done casually without knowing what you're doing and I cannot give you any further help there. Good luck, though...


related resource proposals does not address pagination

nesting of related resources needs to have a way to paginate the related resources.
For example, if you want to get all the spaces for an org or all the routes for an app.

perhaps mvp is to have a maximum of a given resource, if the amount exceeds the request we return an error and point the user to the nested endpoint which has pagination already included.
it also may be appropriate to only enable related resource inclusion for relationships we know will be safely capped

From second cage match:
Maybe cut off after 20/50 and return nothing with link to paginated endpoint? Mechanics uncertain. Not sure how common pagination will be needed if we limit including resources to reasonable endpoints.

Also this thread may be useful: https://github.com/json-api/json-api/issues/509

GET /v3/apps/123?include=routes
{
  guid: 123
  _included: {
    routes: {
      data: [{guid: 1}, {guid: 2}]

      _links: {
        related: /v3/apps/guid/routes
      },
     _pagination: {
       //some stuff
     }
  }
}

Finished :8ball:


Elliptical polarization birdcage coils

Hi, thank you for providing this great Python Birdcage Builder resource!  I was wondering if you had any plans to add elliptical birdcage coil capability to the Python app, similar to the original Birdcage Builder from Penn State.  Thanks!

The math for the elliptical birdcage is already implemented in the code, however it's not tested and the GUI is not yet prepared for it.
I will implement the elliptical birdcage and make a GUI for it, but I will need to add a disclaimer that it is still untested since the original Birdcagebuilder is unreachable nowadays so verifying the results will be difficult. If someone wants to double check the math code I'll be happy to implement any improvements they have.
And if someone has a way to run the original (elliptical) Birdcagebuilder please let me know.

A test version of the birdcagebuilder with elliptical mode support has been added as a separate branch in the repository. In the options menu in the program you can switch between circular and elliptical mode. For now only the short-axis mode is available.
Please report back with any problems you might have.


Challenge http://www.freecodecamp.com/challenges/waypoint-turn-an-image-into-a-link has an issue

Please tell us in detail here how we can make this challenge better.
Completion is triggered only by
###
###
###
###instead of
###
###
###

Thanks for the report. We've since hardened the tests!


Week 3: Deploying a Kubernetes Cluster

Week 3: Use Kubeadm Tool to Create and Manage your Kubernetes Cluster and Deploy Rancher to Manage your Kubernetes Cluster

Topics: Configure and Deploy Kubernetes Cluster across your OpenStack Cluster and deploy Rancher
Tasks:

Install Containerd Runtime across all nodes,

Configure and enable containerd service to start as cgroup

Install Kubectl, Kubeadm and Kubelet across all nodes,
Using Kubeadm initialize Cluster from head (master) node

Take note of the kubeadm join token and hash
Use kubeadm join to add Worker Nodes to the Cluster

Install Calico network plugin on master node
Test and verify cluster from the master node

Use kubectl to confirm status of all pods and nodes

Use kubectl to deploy test application (eg simple nginx server)
Deploy NGINX Ingress Controller using Helm
Install Helm (Kubernetes Package Manager)
Use helm to add the NGINX Ingress Repository
Use helm to install and deploy NGINX Ingress Controller
Install Cert-Manager
Install Ranger

Explore Ranger and discuss how your team would go about creating and running a containerized HPL benchmark

Hi Team,
I hope you are making progress on your project.

You need to have started your poster by now.

You need to have a fork of the Student Cluster Competition Git Repo, that your whole team and mentor has access to and a feature-branch for the project you are working on.

If you would like my direct assistance and guidance, you can add me to this repo.

You need to have started preparing your competition benchmarks, i.e.:

You should have a repo, with at the very least a folder for each of the competition benchmarks and a README.md for each with information that you've already researched regarding building, installing, compiling and running the various benchmarks.

You need to breakdown and allocate the various benchmarks and tasks amongst your team mates.

You need to start preparing a short presentation (lightning talk)... Each of your team members (excluding mentor) needs to start thinking about which benchmarking / aspect of your cluster they are responsible for, and think of some talking points to present to the judges

If you would like to arrange a meeting with me to discuss and review your progress please let me know.
DO NOT LEAVE THINGS TO THE LAST MINUTE!!!
Do a little bit of work every week, and ensure you're consistently making progress.
Good Luck with the remainder of your exams and assignments!

Good morning,
We have begun adding information to our poster and the competition benchmarking is going well. We still have two applications to go, but things are progressing well on that front. Various team members have done various applications and will be able to speak about those.
We slowed down with progress with the project due to exams, but are most of the way through the deployment of the Kubernetes cluster. We are currently running into an issue where if we attempt to run the test application using Nginx Server, it appears to break some of the Kubernetes setup software and we need to go back to "Using Kubeadm to initialize the cluster from the head (master) node".
We have made a fork of the repository and are aiming to submit our pull request as soon as possible, which will likely be this coming Tuesday.

Hi Team,
If you are done with these tasks, let us know so that this issue can be closed.

Hello @nyameko we have been facing an issue on the  Use kubectl to deploy test application (eg simple nginx server) part of this week.
The error we are facing is when we try to  run:
ubuntu@node1:~$ sudo kubectl get nodes

E1120 17:21:43.956816 1561162 memcache.go:265] "Unhandled Error" err="couldn't get current server API group list: Get \"http://localhost:8080/api?timeout=32s\": dial tcp <IP_ADDRESS>:8080: connect: connection refused"
E1120 17:21:43.958530 1561162 memcache.go:265] "Unhandled Error" err="couldn't get current server API group list: Get \"http://localhost:8080/api?timeout=32s\": dial tcp <IP_ADDRESS>:8080: connect: connection refused"
E1120 17:21:43.959907 1561162 memcache.go:265] "Unhandled Error" err="couldn't get current server API group list: Get \"http://localhost:8080/api?timeout=32s\": dial tcp <IP_ADDRESS>:8080: connect: connection refused"
E1120 17:21:43.961268 1561162 memcache.go:265] "Unhandled Error" err="couldn't get current server API group list: Get \"http://localhost:8080/api?timeout=32s\": dial tcp <IP_ADDRESS>:8080: connect: connection refused"
E1120 17:21:43.962714 1561162 memcache.go:265] "Unhandled Error" err="couldn't get current server API group list: Get \"http://localhost:8080/api?timeout=32s\": dial tcp <IP_ADDRESS>:8080: connect: connection refused"
The connection to the server localhost:8080 was refused - did you specify the right host or port?

This is even after we opened all the ports and also joined all the nodes with kubeadm join ...
Please may you assist.
If you need more clarity would it be possible to jump on a call to see if we can explain the issue better?

Specifically after you've open internal ports on tcp 8080?
Have you tried to reconfigure a separate know "open" port, i.e. the one you used for WireGuard, and just temporarily shutdown the WireGuard service?

The steps we took were:
Prerequisites:

Supported OS (e.g., Ubuntu 16.04+).
Minimum 2 CPUs and 2 GB RAM per node.
Disable swap.
Open required ports.

Install Kubernetes Tools:

Install kubeadm, kubectl, and kubelet on all nodes.
Mark packages to hold updates.

Master Node Setup:

Enable and start kubelet.
Initialize the cluster with kubeadm init.
Configure kubectl for the admin user.

Worker Node Join:

Use the join command generated by kubeadm init.

Install Calico:

Deploy the Calico operator.
Apply the custom resources.
Verify the Calico pods.

Test Cluster:

Check node and pod statuses with kubectl.

The first time we ran these commands we got until the ability to check the nodes are connected and up. Now we cant even check that. The below section is what we were able to get to when we went through it the first time.
nginx-deployment.yaml file
apiVersion: apps/v1
kind: Deployment
metadata:
  name: nginx-deployment
spec:
  replicas: 1
  selector:
    matchLabels:
      app: nginx
  template:
    metadata:
      labels:
        app: nginx
    spec:
      containers:
        - name: nginx
          image: nginx:latest
          ports:
            - containerPort: 80
---
apiVersion: v1
kind: Service
metadata:
  name: nginx-service
spec:
  selector:
    app: nginx
  ports:
    - protocol: TCP
      port: 80
      targetPort: 80
  type: LoadBalancer

Apply the YAML file to the Kubernetes Cluster
kubectl apply -f /home/nginx-deployment.yaml

ubuntu@node1:/home$ kubectl apply -f /home/nginx-deployment.yaml
deployment.apps/nginx-deployment created
service/nginx-service created
ubuntu@node1:/home$ kubectl get deployments
NAME               READY   UP-TO-DATE   AVAILABLE   AGE
nginx-deployment   0/1     1            0           14s
ubuntu@node1:/home$ kubectl get pods
NAME                                READY   STATUS              RESTARTS   AGE
nginx-deployment-54b9c68f67-vbdcw   0/1     ContainerCreating   0          29s
ubuntu@node1:/home$ kubectl get services
NAME            TYPE           CLUSTER-IP      EXTERNAL-IP   PORT(S)        AGE
kubernetes      ClusterIP      <IP_ADDRESS>       <none>        443/TCP        6h1m
nginx-service   LoadBalancer   <IP_ADDRESS>   <pending>     80:30223/TCP   43s
ubuntu@node1:/home$ kubectl port-forward svc/nginx-service 8080:80
error: unable to forward port because pod is not running. Current status=Pending

And even when we ran this we had an issue where the pods were stuck in the ContainerCreating status.

From what you recommended:
Open the ports
The blow configuration was used to open all the ports, including 8080.
sudo ufw allow 8080/tcp
sudo ufw allow 6443/tcp
sudo ufw allow 10250/tcp
sudo ufw allow 10251/tcp
sudo ufw allow 10252/tcp
sudo ufw allow 2379:2380/tcp
sudo ufw allow 30000:32767/tcp

Sadly it did not work
WireGuard
We have installed ZeroTier but we are not using it as we have created a link to each team members PC with SSH-KEYS to allow them to securely connect to the sebowa cluster.
I did run a port scan and what I can see is that there is no conflict in the ports.
$ sudo lsof -i -P -n
...
zerotier-     663    zerotier-one    6u  IPv4   969226      0t0  UDP <IP_ADDRESS>:9993
zerotier-     663    zerotier-one    7u  IPv4    21398      0t0  TCP *:9993 (LISTEN)
zerotier-     663    zerotier-one    8u  IPv6    21399      0t0  TCP *:9993 (LISTEN)
zerotier-     663    zerotier-one   15u  IPv4    21444      0t0  UDP <IP_ADDRESS>:9993
zerotier-     663    zerotier-one   16u  IPv4   969227      0t0  UDP <IP_ADDRESS>:47916
zerotier-     663    zerotier-one   17u  IPv4    21445      0t0  UDP <IP_ADDRESS>:47916
zerotier-     663    zerotier-one   18u  IPv4    21446      0t0  UDP <IP_ADDRESS>:27580
zerotier-     663    zerotier-one   19u  IPv4   969228      0t0  UDP <IP_ADDRESS>:27580
...

Moving forward
At the moment to minimize what we don't have control over, we will be recreating the cluster we have on sebowa on a local cluster and then seeing if the issue continues. We will update you as soon as we get a result.
Thank you for your response.

Working
After moving the cluster to google instances everything started working, there were some configuration stuff but all in all everything is working.
With regards to ingress do you want to see a test application on it or can we just show that it has installed? The reason I ask is that for Ingress we had to use the NodePort type to setup due to us using kubeadm at first. This makes a lot of issues with port linking and is hard to test. We can definitely see that the ingress server is up, as seen bellow:
  kubectl get svc -n ingress-nginx

NAME                                 TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)                      AGE
ingress-nginx-controller             NodePort    <IP_ADDRESS>    <none>        80:31256/TCP,443:31634/TCP   101s

Please advise further on this.

Hi @Talhahpatelia ,
Really good work!
Slight confusion or miscommunication or both.
"""Using a KNOWN OPEN PORT LIKE WIREGUAR""" I'd meant try and bind you nginx service to the WireGuard port, (i think it's 8889 or something in your instance, instead of 80)
Port 80, as a general principle will be blocked by many, many services, not just OpenStack...
But you've demonstrated progress in this regards, so please submit a PR on what you've done, or add me to your private fork and edits so I can directly advise further there.

Thank you @nyameko, I have added you to our private repo for the project.
Please advise for anything that should be edited or changed.


add a basic example using 2 or more different renderpipeline in the same frame

I'm working with WebGPU for months now and I realized today that the way to render multiple meshs using different pipelines is not crystal clear.
The sample called "two cubes" use the same renderPassEncoder, the same pipeline and same pipelineLayout , so it's a particular case not the common case.
Can you please add an example that show how to render a red square with its own renderpipeline and a green triangle over it using its own renderpipeline.
I tryed to do it one hour ago and I was surprised to see that the canvas was cleared before to draw the second pipeline.
I suspected that it was possible to configure it somewhere in the colorAttachment and I saw that it works if I set "loadOp" to " load" instead of "clear" ....
But all of your samples uses "clear" so I'm not sure if it's a good thing to use "load" or not.
A basic sample about this would be very usefull (and appreciated :) )

Well I think I figure it out.
I close the issue but just in case someone found this topic :
you must use renderPassDescriptor.colorAttachments[0].loadOp = "clear"
for the first mesh in order to keep the clearColor you defined in colorAttachment as background-color
then you must use renderPassDescriptor.colorAttachments[0].loadOp = "load" for every other renderPass


[bug]  instance in the hero of the interactive lab pages has elements that look off

Describe the bug
The way that the tiles in the hero were changed recently.

the linked heading no longer is blue
the "introductory lab" text is no longer 14px
the footer element "60 mins" should also be 14px

https://www.redhat.com/en/interactive-labs/openshift
Which Component?
rh-tile
Steps to reproduce

go to https://www.redhat.com/en/interactive-labs/openshift
look at the tile in the hero

Expected behaviour
The hero tile should match the styles of the cards below -- they seem fine
Screenshots
as is

should be

Element HTML
No response
Operating System (OS)
macOS
Browser
No response
More browser information
No response
Additional Info
No response

It looks like rh-tile is not available for "custom hero" in drupal, which is what these pages use. The cards in the hero are built in a general raw box to achieve the styles that are intended to match rh-tile.
Something in a recent update to rh-tile, must have changed the support of the manual styles.
Adam Lazzara has opened a ticket to add the ability to add rh-tile to the hero pattern. --> https://issues.redhat.com/browse/DXFED-1078 After which, we can add the component properly.
Closing for now because the bug wasn't with the component but with implementation.

@wesleymiles we don't have an rh-tile component on RHDS yet. It's still in development.


app shows "React Webpack Node" above the nav

Everything seemed correct (I installed some modules like react-toolbox which appears buggy, inline-grid, draftJS, radium and some minor ones) then I restarted the server : now the app is loaded & rendered correctly but it doesn't load any data and it shows "React Webpack Node" on top of the navbar. No error message whatsoever. As nothing tells me where the problem is coming from, do I get a chance to know what's going on without having to remove the app pieces after pieces ? Thanks a lot for your help.

Fun is back. Lightspeed with all features, it rocks. Problem may have been caused by :

Image server cant find
Real trouble with webpack loading fonts - I dont know where to put them at first...
Bug in react-toolbox list components. Ill figure out.
But by the time Id really love to know what happens when app shows "React Webpack Node" above the nav.

I've had that happen to me as well. It seems to happen when there is an issue with the hand off from what the server rendered to what the client has expected the server to render. If you try cleaning and rebuilding and you still see it, then I would just work backwards until you figure out which is the problem module.

gonna close this one. Please re-open if you have it happen again philohelp and I can try to reproduce. Thanks!


[Documentation Update]: ADD leetcode solution 931

Is there an existing issue for this?

[X] I have searched the existing issues

Issue Description
I would add the solution of the leetcode problem 931.
Suggested Change
Solution for the leetcode problem 931 will be added in all the major programming languages .
Rationale
No response
Urgency
High
Acknowledgements

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository
[X] I have read and followed the Contribution Guidelines
[X] I have followed the code style guidelines of this project
[X] I have checked for any existing open issues that my pull request may address
[X] I have ensured that my changes do not break any existing functionality
[X] Each contributor is allowed to create a maximum of 4 issues per day. This helps us manage and address issues efficiently
[X] I have read the resources for guidance listed below
[X] I have not used AI-generated content (e.g., ChatGPT, other AI tools)
[X] I have not used content from existing sites (e.g., text, images)
[X] I have followed all security rules and only shared trusted resources

@Nikhil11200 Please complete your task otherwise I will close it.


Unpin tox in AppVeyor config

Resolve TODO comment since tox==3.14.5 is released.

FYI, please ignore failed coverage checks, because Travis CI was skipped.

@auvipy thanks!


[release-1.19] Manual cherry-pick of changes in #46958

Please provide a description of this PR:
https://github.com/istio/istio/pull/46598 was done on the main branch for some changes in istio/api which required changes in istio. The api PR was cherry-picked to release-1.19 and merged. To get those working in istio, we need to either revert the first istio/api change or manually cherry-pick the istio changes. This PR is for the later.
To help us figure out who should review this PR, please put an X in all the areas that this PR affects.

[ ] Ambient
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

@ericvn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio_release-1.19
315f6a83ef06bc11622bebb4c0a533da986c94a0
link
true
/test gencheck

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ericvn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio_release-1.19
315f6a83ef06bc11622bebb4c0a533da986c94a0
link
true
/test gencheck

integ-ambient_istio_release-1.19
315f6a83ef06bc11622bebb4c0a533da986c94a0
link
true
/test integ-ambient

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Convert from godep to gomod

Follow the suggestion for golangci-lint (https://github.com/golangci/golangci-lint/issues/1037)

Tested locally for make build-typegen & make package-typegen commands, and release-typegen & release-gatekeeper-function workflows.


WIP: Add more tests

This is just a demonstration of expanding the testing system of Walrus.
Add tests:

regression: random tests
malformed: incorrect syntax tests
standalone: feature tests (with heavy wasi utilization)
proposal_features: features that are only just proposed in some way (for example anyref and array type)

This will be changed to fit the right licenses, it is just a demonstration.

Thank you! We can discuss what kind of tests we want to run. For example, malformed tests are testing wabt, do we need them?

Thanks for your great contribution!
Please consider the followings:

What about merging tools/run-tests-other.py into tools/run-tests.py file?
IMO we don't need to run tests for proposed-features

Initially we just wanted the files to be seperated so it's easier to keep track of  "other" tests but I will merge it if that is prefered.
Also if proposed-feature tests are not really needed then we can remove them, it was just in case if we implemented any of them then they could be tested instantly.

@clover2123 We have been trying out things in this patch and started to wonder how should the tests be added.
Just to clarify all of these tests have been collected from wamr but most of the complicated programs are open source and we can compile them if we would like to.
But the important thing is:
Should we add tests separately or together as one big patch? (like this)
Which tests should we add? Currently, we are thinking about:

Coremark
Dhrystone
c-ray

the problem is that it's more of a demo, only benchmark we can do is measuring the render time

regression tests from wamr

these come handily because walrus still fails on some of them and they are actual errors most of the time and not Insufficient impport errors

unit tests from wamr

some of these test optional features that we have not implemented yet

We would not add tests that are still failing though.
Lastly, there are still some tests that we are looking at. Should we contiue looking into them and search for more or should we rather focus on merging these into walrus?
Also, should we maybe introduce a new CI run for more complicated tests that take more time?


[Poplar] Fix URIs to github repositories for u-boot and Linux.

Building Yocto branch rocko for board poplar I got this errors:
ERROR: u-boot-poplar-v2017.09+gitAUTOINC+98469ebb7a-r0 do_fetch: Fetcher failure: Unable to find revision 98469ebb7afaacc742d6f651f8e676e755672a63 in branch latest even from upstream
ERROR: u-boot-poplar-v2017.09+gitAUTOINC+98469ebb7a-r0 do_fetch: Fetcher failure for URL: 'git://github.com/linaro/poplar-u-boot;protocol=git;branch=latest'. Unable to fetch URL from any source.
ERROR: u-boot-poplar-v2017.09+gitAUTOINC+98469ebb7a-r0 do_fetch: Function failed: base_do_fetch
ERROR: Logfile of failure stored in: /home/igalia/clopez/yocto/poplar/build_poplar/tmp/work/poplar-poky-linux/u-boot-poplar/v2017.09+gitAUTOINC+98469ebb7a-r0/temp/log.do_fetch.46598
ERROR: Task (/home/igalia/clopez/yocto/poplar/meta-96boards/recipes-bsp/u-boot/u-boot-poplar.bb:do_fetch) failed with exit code '1'

ERROR: linux-poplar-4.9+gitAUTOINC+e153b53cbd-r0 do_fetch: Fetcher failure: Unable to find revision e153b53cbd7047d7e6863c1850dda751f4a7f333 in branch poplar-4.9 even from upstream
ERROR: linux-poplar-4.9+gitAUTOINC+e153b53cbd-r0 do_fetch: Fetcher failure for URL: 'git://github.com/Linaro/poplar-linux.git;protocol=https;branch=poplar-4.9;name=kernel'. Unable to fetch URL from any source.
ERROR: linux-poplar-4.9+gitAUTOINC+e153b53cbd-r0 do_fetch: Function failed: base_do_fetch
ERROR: Logfile of failure stored in: /home/igalia/clopez/yocto/poplar/build_poplar/tmp/work/poplar-poky-linux/linux-poplar/4.9+gitAUTOINC+e153b53cbd-r0/temp/log.do_fetch.13069
ERROR: Task (/home/igalia/clopez/yocto/poplar/meta-96boards/recipes-kernel/linux/linux-poplar_git.bb:do_fetch) failed with exit code '1'

This patches fixes this.

@petegriffin fyi

LGTM

@shawnguo2 can you confirm the u-boot branch to use?

https://github.com/96boards-poplar/u-boot latest
https://github.com/96boards-poplar/linux poplar-4.9

@shawnguo2 Thanks. @clopez Please adjust your PR accordingly. U-Boot branch should be latest instead of alex/latest.

@shawnguo2 Thanks. @clopez Please adjust your PR accordingly. U-Boot branch should be latest instead of alex/latest.

Sorry, there isn't any U-Boot branch on the remote repository. And the only branch containing the referenced commit on the recipe is that alex branch:
$ git clone https://github.com/96boards-poplar/u-boot
[...]
$ cd u-boot
$ git branch -a
$ git branch -a
  * latest
    remotes/origin/HEAD -> origin/latest
    remotes/origin/alex/latest
    remotes/origin/latest
    remotes/origin/shawn/install

The referenced commit on the u-boot bitbake recipe is  98469ebb7afaacc742d6f651f8e676e755672a63 and git says this
$  git branch -a --contains 98469ebb7afaacc742d6f651f8e676e755672a63
   remotes/origin/alex/latest

@clopez You can keep using 'alex/latest' branch with the commit in the boot recipe, but we are not going to update the branch any more.  Instead, branch 'latest' is the one we are currently maintaining and updating.  So you are suggested to update the boot recipe to use the HEAD of this branch.

@clopez You can keep using 'alex/latest' branch with the commit in the boot recipe, but we are not going to update the branch any more. Instead, branch 'latest' is the one we are currently maintaining and updating. So you are suggested to update the boot recipe to use the HEAD of this branch.

That's a different history.
This patch only fixes the references to the repositories and allows Yocto to fetch those commits. With this patches It builds fine, otherwise a fetch error will happen.
But this patches doesn't update the reference commit that will be built. If you want to update the recipe to use a different commit feel free to do that in a follow-up commit. I won't do that as I can't currently test that what I have built runs ok because I don't know how to flash the built products I got. See: https://github.com/96boards-poplar/Documentation/issues/4

@clopez make sense. I'd like to move to latest so I'll do a follow up commit.


Doc should clearly state this package is not usable on any platform except IBM i

v1.1.9 is released. Close this issue for now.


Allow external configuration

This adds the ability to have a custom config.js file and custom.css file.
 Sad day -- have to reconfigure. =(
Would love it if I could keep the git changes clean while having my own config.
This will throw a little inconsequential error in the console if the config files don't exist, but there are no breaking changes. I could probably make it check for the script's existence first, but it seems like a pretty unnecessary use of time.
It's also blocking, which means it technically slows the page down extremely slightly, so it might be worth considering making CONFIG a thunk or something so we can load the config file at the end/asynchronously.

Thanks for the pr (: I see your point, but I'm not sure if it warrants this change. Git is really pretty good at merging changes to files. If I do happen to make a change that conflicts with your config/css, you have the opportunity to resolve those conflicts manually in a way that makes sense. Additionally, gitignoring those files doesn't work so well for people utilizing gh pages.
That said, I actually do like the idea of an external config file, but it's hard to pull off without loading a blocking resource or adding complexity/dependencies. If you really prefer having things separate, you can safely keep your changes and merge in any upstream changes just fine. Just keep in mind that there will probably be breaking changes between major versions.

Yeah, that's all true in theory, but in practice we can't all be that good at git on the whole. =) I messed up yesterday...
I think making the config a thunk rather than a plain object will resolve the issue, but it will add small amounts of complexity. That said, the diff from this one commit is significantly easier to handle than the diff from all of my changes, so I can manage this one alone.

True. I'm not really familiar with thunks. If it's not too complex, I'd be interested in seeing what that would look like.


add spec for Warning[category] = true|false to emit/suppress warnings

Hello :wave:
This time I'll try to cover this one from #745

[ ] Added Warning.[] and Warning.[]= to manage emitting/suppressing
some categories of warnings. Feature #16345 Feature #16420

However, I discovered that suppressing experimental (Warning[:experimental] = false) does not seem to work when invoking a script with ruby -e '...'. In irb it works as expected.
Example:
# Tested with Ruby v2.7.2 on macOS 10.15 (Catalina) and Debian 10 (buster)

# :deprecated
ruby -e 'Warning[:deprecated] = true; $; = ""'  # => -e:1: warning: `$;' is deprecated
ruby -e 'Warning[:deprecated] = false; $; = ""' # =>

# :experimental
ruby -e 'Warning[:experimental] = true; 0 in a'  # => -e:1: warning: Pattern matching is experimental ...
ruby -e 'Warning[:experimental] = false; 0 in a' # => -e:1: warning: Pattern matching is experimental ...

Is this expected, or am I missing something here?

I think it's because 0 in a is warned at parse time, vs $; warned on assignment.
Using eval() around 0 in a should make it work.

@eregon Once again, thank you for your precious feedback. 🙇
Today I Learned...

_"0 in a is warned at parse time, vs $; warned on assignment."

(and I guess, that's why it works in irb, because each command is put through eval(..)... ?!)

You are right, the warnings disappear with eval('0 in a'), but is this really the intention of Feature 16345?
Given this script.rb
Warning[:experimental] = false
0 in a

ruby ./script.rb
# ./script.rb:2: warning: Pattern matching is experimental, and the behavior may change in future versions of Ruby!

I'd expect that Warning[:experimental] = false suppresses this warning, without wrapping it into eval(..), no?
(Sorry for my annoying questions 😉)

Feel free to mention that drawback on the issue, but it is expected behavior, parse-time warnings can only be disabled if it's set before parsing of course. And pattern matching emits a parse-time warning.

@eregon 👍 Alright, in that case I think that part of the feature is kind of pointless, even if's technically explainable... 🤷 😀
Thanks for your explanation. I changed the specs accordingly and marked this PR as "Ready for review":

@eregon I rebased master and changed the default for :deprecated to false.
However, I had to change the spec n to use ruby_exe(), because the other way it still returned the old default true:
     3: ruby_version_is '2.7.2' do
     4:   describe "Warning.[]" do
     5:     it "returns default values for categories :deprecated and :experimental" do
     6:       ruby_exe('p Warning[:deprecated]').chomp.should == "false"
     7:       ruby_exe('p Warning[:experimental]').chomp.should == "true"
 =>  8:       binding.irb
     9:     end
    10:
    11:     it "raises for unknown category" do
    12:       -> { Warning[:noop] }.should raise_error(ArgumentError, /unknown category: noop/)
    13:     end

irb: warn: can't alias context from irb_context.
2.7.2 :001 > RUBY_VERSION
 => "2.7.2"

2.7.2 :002 > Warning[:deprecated]
 => true

I have no idea why this is 😏 ... do you?

I have no idea why this is  ... do you?

It's because of https://github.com/ruby/mspec/commit/e154fa1393786668a7dace3058bd1aac48a77375, which is intended but I did not think about it in this context.
Using ruby_exe is a good workaround here, especially useful to test global defaults that might be affected by the test harness.

It's because of ruby/mspec@e154fa1 ...

Thanks for that, I was very confused... 😂


Fix docs settings typo

This fixes a small typo in the docs.

Coverage remained the same at 96.931% when pulling 937162bd9709be2ab3aaaadd5a1abb05a77e5e2e on nattyg93:patch-1 into cbda9ee075a3ea916dc26a76215f489919bc51bd on Tivix:master.


bug: Setting filter: brightness outputs an error in cli

Type: bug
Ionic Version: 2.x
Platform: all
I have this scss for one div in my file:
    .bg {
      padding: 0;
      background-image: url('../../assets/images/bg-placeholder.jpg');
      background-size: cover;
      background-repeat: no-repeat;
      background-color: black;
      position: absolute;
      width: 100%;
      height: 100%;
      filter: brightness(0.5);
      background-size: cover;
    }

This error gets printed in CLI:
 ✗ node_modules\ionic-framework\util\functions.scss
Error: argument `$color` of `red($color)` must be a color

       Backtrace:
        node_modules/ionic-framework/util/functions.scss:6, in function `red`
        node_modules/ionic-framework/util/functions.scss:6, in function `brightness`
        app/app.scss:49
        on line 6 of node_modules/ionic-framework/util/functions.scss
>>   @return (red($color-value) * 0.299 + green($color-value) * 0.587 + blue($col
   -----------^

As soon as I remove the filter: brightness(0.5); part, it starts working. If I select any other filter (opacity, blur,..) it works.

Ok, it's because of a brightness function that I recently added, so Sass is using it instead of just the css value instead. I'll rename the sass function to fix this, thanks.


Autoload more history on scrolling

Works the same way as on Discord.
Related: #1131, #207, #1038

[x] Find the way to fix scroll bugs

How well does this work? Is it nice and smooth? The code looks really simple, but I'm just a little suspicious about it being so small and simple because @astorije tried this and had some bugs. I've not looked into how he did it, though.

How well does this work? Is it nice and smooth?

Yep, I didn't notice any problems.

I'm just a little suspicious about it being so small and simple because @astorije tried this and had some bugs.

This PR doesn't have any of that bugs:

#1045 fixed multiple load
"Show more" button is still here + message count check was added, so /clear works
.off("scroll") was added to fix multiple event listeners

Wait, found some bugs on mobile.

Finally fixed scroll bugs :weary:

We've ran into same problem with restoring scroll position when more history is loaded. Your solution is going to be a problem if more does not arrive instantly (e.g. slow mobile network), and will produce an unwanted jump (e.g. scroll up and down quickly).
You can see my code here https://github.com/thelounge/lounge/compare/xpaw/infinite-scroll
It uses IntersectionObserver to not deal with scroll position and counting how many messages there are.

In my instance more never arrive instantly (because of CF and PI) and I haven't noticed this before. Is this really an issue?
Anyway, I believe this can be easy fixed by updating scroll position in more event.

It should be noticeable on a slow network (think second delay)

It should be noticeable on a slow network (think second delay)

I have 2-3 seconds delay here and noticed this only after you mentioned it. Maybe it's because I usually don't scroll much while more is loading.

Wait... I already have this in more event, maybe this is the reason I don't see any bugs.

Try triggering the load event and scroll down quickly (e.g. page up then page down), I'd be surprised if that didn't jump you back after more messages loaded.

I'd be surprised if that didn't jump you back after more messages loaded.

Be surprised :rofl:
Also, why are you trying to reimplement the same feature instead of just merging this?

Using proper API for this is better than it checking scroll and counting messages.

Well, you can't fix this unless you start checking scroll :laughing: So you'll have a proper API with a scroll check :smiley:

I tested this PR, it definitely has it's own issues. Doing a pageup triggers it multiple times and it even gets visibly glitchy. There's a bit unrelated issue where position does not reset correctly when more messages get appended (this bug existed before).
I have fixed the scroll reset in my branch by using requestAnimationFrame by the way.

Doing a pageup triggers it multiple times and it even gets visibly glitchy.

Wat, it absolutely can't get triggered multiple times, look at the code. I also tested this to be sure. It may be some other bug with pageup (which is already fixed on master IIRC).

Wat, it absolutely can't get triggered multiple times, look at the code.

I tested whatever you currently had in the current state, and it absolutely did produce glitchy UI.

I definitely don't have such problem on my instance, so it isn't related to this PR. I'll test current branch again tomorrow.

Turned out you were right: it triggers multiple times (but only on good connection, so I don't have this on my instance). The reason for this was pageup animation, fixed it.

Tests not passing

It's because of conflicts. I'll fix them if we agree to merge this instead of #1318.

Turned out you were right: it triggers multiple times (but only on good connection, so I don't have this on my instance).

And this is precisely why you need to be calm instead of telling me to "look at the code".

And this is precisely why you need to be calm instead of telling me to "look at the code".

Yeah, but I still agreed to test it again. It's just hard to believe that tested for months code can have such obvious bugs.

I haven't tested this, but I'd rather this over #1318 due to more widespread browser support. No reason to use a brand new API

No reason to use a brand new API

The reason would be that new API is completely asynchronous, so it's a performance win.

Didn't mean to close this, damn github ui.

I also very much prefer #1318 over this PR for the fact that it leverages native browser interaction, and is properly async. This only applies if we ship the polyfill the spec authors came up with though.
And when it comes to API change... well, let's hope there won't be too many breaking changes 😅
Thanks for your help, @bews!

#1318 being in good shape to be merged (upon the official polyfill being fixed), it all seems like we will go for the browser-native solution instead. Thanks for triggering work on this, @bews!


transfer-sh: init at 1.6.0

Description of changes
Added a package and module for transfer.sh, addressing #239627
I'm sure there are things that can be done in a cleaner way, please let me know and I'll iterate over the code until it fits the quality standards.

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

The commit messages do not fit CONTRIBUTING.md.

Should module and pkg be separate commits or can I "init at xxx" both at once?

Should match the format now.

can we maybe put all the CAPSLOCK option inside a freeform submodule? and just document the couple ones which are important?

Should I close this PR in favor of https://github.com/NixOS/nixpkgs/pull/283660 ? I don't mind and think it makes sense to decide on one of the two PRs and focus work there to push it over the finish line.


Avast reports notifu.exe as a potential threat

So I just run npm update in one of my projects and this Avast window jumped out on me<EMAIL_ADDRESS>

Got an answer back from Avast and Notifu was whitelisted on January 13.

Brilliant. Thanks for the followup. I'll look into reupdating this


Add List of LLM's Supported

Please add list of all LLM's supported and all the one with future updates.
There are lots of details missing with Docs as well.
Please add them.
Thanks

tinyllm uses litellm to make LLM calls https://github.com/BerriAI/litellm/
litellm aggregates more than 20+ model providers. in tinyllm you can just set the model argument to whatever model you need like
agent(user_input='hii', model='gpt-4') or  agent(user_input='hii', model='hugginface/model_name')

Great then please add more documentation on README then about these examples with models.

Yes, I will add proper documentation when the library is fully stable.


Exporting without Xserver?

Case

BUG

Issue
I am running npm run export on a machine without an xserver, meaning Chrome won't launch.
Is there a way to compile the pdf only without opening chrome?
Info
Ubuntu 17
Reproduce
><EMAIL_ADDRESS>export /home/nova/repos/best-resume-ever
> concurrently "npm run dev" "npm run pdf" --success first --kill-others --raw

><EMAIL_ADDRESS>predev /home/nova/repos/best-resume-ever
> check-node-version --node ">= 8.0.0"

><EMAIL_ADDRESS>pdf /home/nova/repos/best-resume-ever
> node scripts/export.js

node: 8.7.0
npm: 5.4.2
yarn: not installed

><EMAIL_ADDRESS>dev /home/nova/repos/best-resume-ever
> node build/dev-server.js

> Starting dev server...

 DONE  Compiled successfully in 6791ms                                                                                17:02:49

> Listening at http://localhost:8080

Connected to server ...
Exporting ...
Finished exports.
(node:7229) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: Failed to launch chrome!
/home/nova/repos/best-resume-ever/node_modules/puppeteer/.local-chromium/linux-508693/chrome-linux/chrome: error while loading shared libraries: libX11-xcb.so.1: cannot open shared object file: No such file or directory

TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md

(node:7229) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:7229) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 2): Error: Failed to launch chrome!
/home/nova/repos/best-resume-ever/node_modules/puppeteer/.local-chromium/linux-508693/chrome-linux/chrome: error while loading shared libraries: libX11-xcb.so.1: cannot open shared object file: No such file or directory

TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md

(node:7229) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 3): Error: Failed to launch chrome!
/home/nova/repos/best-resume-ever/node_modules/puppeteer/.local-chromium/linux-508693/chrome-linux/chrome: error while loading shared libraries: libX11-xcb.so.1: cannot open shared object file: No such file or directory

TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md

(node:7229) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 4): Error: Failed to launch chrome!
/home/nova/repos/best-resume-ever/node_modules/puppeteer/.local-chromium/linux-508693/chrome-linux/chrome: error while loading shared libraries: libX11-xcb.so.1: cannot open shared object file: No such file or directory

TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md

(node:7229) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 5): Error: Failed to launch chrome!
/home/nova/repos/best-resume-ever/node_modules/puppeteer/.local-chromium/linux-508693/chrome-linux/chrome: error while loading shared libraries: libX11-xcb.so.1: cannot open shared object file: No such file or directory

TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md

(node:7229) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 6): Error: Failed to launch chrome!
/home/nova/repos/best-resume-ever/node_modules/puppeteer/.local-chromium/linux-508693/chrome-linux/chrome: error while loading shared libraries: libX11-xcb.so.1: cannot open shared object file: No such file or directory

TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md

(node:7229) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 7): Error: Failed to launch chrome!
/home/nova/repos/best-resume-ever/node_modules/puppeteer/.local-chromium/linux-508693/chrome-linux/chrome: error while loading shared libraries: libX11-xcb.so.1: cannot open shared object file: No such file or directory

TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md

As the script is supposed to work with puppeteer (headless chrome).
You may need to check some Ubuntu dependencies needed [here] https://gist.github.com/addyosmani/5336747)
You may still have TROUBLESHOOTING because the script will still try to open chrome but it headless mode is enabled by default in the project, it should'nt be a problem to generate the pdf.
I didn't tried myself but let me know if it works.

it doesn't work. Same issues.

I'm closing this now.
As @CorentinDy  mentioned, this is a puppeteer-issue which will not be resolved at this repo.


Import Guide Template Checkbox Options Share IDs

These checkboxes share the same IDs between both columns so clicking the label on the right column will select the checkbox in the left column.

Ah, thanks! I'll fix that in the next release, too.

Fixed in version 2.0.1


Add search field to manage articles page

https://trello.com/c/7Eu6Efcs/1-enhancementsearch-functionality-should-be-provided-on-the-manage-articles-page

Added css stylesheets and js files for data tables.
Added 'table_id" for the manage articles table
Tried with searching =true for the DataTable [Search box is not displayed]

Updated manage_articles.html file- added search box functionality
Added
Added js , datatables and css
Implemented column rendering for the search box functionality.[Resource : https://datatables.net/examples/advanced_init/column_render.html]

Verified.


Added dynamic accessor and mutators from $uuidAttributes

This solves the problem in #33. I have tested it in my own project, but haven't written any unit tests yet.

@westphalen Any updates on this? Do you still want to go through with it?

Hi @all
This is a nice feature. Go ahead with it pls.
Regards

@brendt I don't have time to look more into this, as I ended up not using the package anyway. You're welcome to use the pull request still.

I could pick this back up as I have a pretty urgent usage of the majority of this functionality. I'm just not sure how to pick up a PR from someone else.....Does it mean starting a new PR from my own fork and going from there?

@ragingdave

Does it mean starting a new PR from my own fork and going from there?

Yup.
I'll close this PR as there has been no activity in quite some time.


HTML language server throws exception when initialization options are empty

VSCode Version:
Version 1.7.2
Commit 7ba55c5860b152d999dda59393ca3ebeb1b5c85f
Date 2016-11-21T22:14:18.217Z
Shell 1.3.8
Renderer 52.0.2743.82
Node 6.5.0
OS Version: Fedora 25

Steps to Reproduce:

Use this request to initialize HTML language server

{
  "id": "1",
  "method": "initialize",
  "params": {
    "rootPath": "/home/wywrzal/development/ZEND/Che/runtime-IDE/Test",
    "capabilities": {},
    "clientName": "Eclipse Platform"
  },
  "jsonrpc": "2.0"
}

As an response error will be returned:

{
  "id": "1",
  "error": {
    "code": -32603,
    "message": "Request initialize failed with message: Cannot read property \u0027embeddedLanguages\u0027 of undefined"
  },
  "jsonrpc": "2.0"
}

Isn't a big problem but it would be nice to handle this simple case without exception.

Fixed in 1.8.
As a workaround for 1.7, pass in an initializationOptions.embeddedLanguages = {} to the service


feat: allow users to set security groups on scheduled apps;

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


Creation of XebiaLabs XLDeploy collector

Added XLDeploy collector (https://xebialabs.com/products/xl-deploy/). The project was based off of the UDeploy collector.
Note the following differences I found between XLDeploy and UDeploy:

I don't gather "component" information since as far as I know in XLD components (called deployables) are deployed with an application package (version of an application) in an all-or-nothing manner. Instead on the UI each application will have a single component with the name of the application.
I don't think XLD has a way to get environment health information (how many servers up/down) so instead that data isn't set. Each application will thus be listed as having 0 servers up and 0 servers down.
Complex scenarios like transitive application dependencies and composite packages are not handled. I may add them in the future depending on project needs.

The collector works by parsing through application deployment history. New applications or applications that have not been enabled in the past day or so (since beginning of yesterday) parse through 3 months of history. For efficiency applications that have recently been parsed (since the beginning of yesterday) only hit the past day or so of history (since the beginning of yesterday). XLD acts strange in that it doesn't archive a task when it completes but instead when it is closed in the UI. For that reason I look back an extra day to pick up any history items that could of been missed.
I have signed the license agreement.

@MarkRx
Awesome...This saves us a lot of effort... We are using XLDeploy & XLRelease as well. Currently we are building a collector for XLRelease, wondering if you are also using XLRelease.

@MarkRx Will merge this very soon. Thanks a lot for the PR.

I have not thought about how XLR would fit in yet. I am currently looking at being able to track multiple XLD deployment packages at once by having the UI + api be able to select more than one app at once.

Please see https://github.com/capitalone/Hygieia/issues/513 -
Enhancement request to pull in some release related information.


chore: Update bind.sh

Overview
Updates bind.sh to no longer attempt to pull from the rust configs, as it doesn't exist anymore.

#27
#26
#28  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @clabby and the rest of your teammates on  Graphite


Lint: Use … instead of ...

What
The ellipsis character … should be used in GUIs and docs instead of the similar-looking .... The former looks better over all, and the latter can have a linebreak inserted in the middle of it which doesn't look great. It is also for consistency.
Ideally we would only lint strings in Rust using something like https://github.com/trailofbits/dylint but I'll leave that as an exercise for later 😬
For our developers: I suggest you figure out how to type … quickly on your keyboard. On my Mac I press ⌥; (but I can't remember if that is something special I've configured…)
This one is for you @martenbjork
Checklist

[x] I have read and agree to Contributor Guide and the Code of Conduct
[x] I've included a screenshot or gif (if applicable)
[x] I have tested demo.rerun.io (if applicable)

PR Build Summary
Docs preview
Examples preview
Recent benchmark results
Wasm size tracking

I argue it is worth it for docstrings (///) so might as well do it in all comments. As yes, as I said in the PR body: learn how to type it :]


Hystrix properties not working

I have a similar error to issue 2230 using Spring Cloud Dalston.SR3 and Spring Boot 1.5.7 versions. I have the following hystrix dependency corresponding to this version in my gateway using ZuulProxy:
<dependency>
         <groupId>org.springframework.cloud</groupId>
         <artifactId>spring-cloud-starter-hystrix</artifactId>
</dependency>

The only hystrix properties available in my application.yml are:
hystrix:
   metrics:
     enabled: foo
     polling-interval-ms: foo

I wanted to set the isolation metrics beyond the default of 1000ms, for example:
hystrix.command.default.execution.isolation.thread.timeoutInMilliseconds: 15000
But it does not work, it does not recognize these commands -- neither my jar, nor the STS. When I check the /health, I only get a response without the set properties:
{
     ... ,
    "hystrix": {"status": "UP"}
}

What to do?

The ide won't recognize Hystrix properties at all

Do not recognize? Even if so, the set properties have no effect.

There is no metadata about them since they come from a 3rd party jar

How so? In several places, I have seen these settings defined through properties ...

Having them be valid for an application and completable by the ide are two very different things

Okay, but I created this component in main class, still in ZuulProxy, as seen in the documentation:
    @Component
    public class Teste {

        @HystrixCommand(groupKey = "Service",
                commandProperties = {
                @HystrixProperty(name = "execution.isolation.thread.timeoutInMilliseconds", value = "6000") })
        public String readingMockService() {
            System.out.println("asdpasdpokspoka");
            URI uri = URI
                    .create("https://localhost:8075/any/cached");
            return new RestTemplate().getForObject(uri, String.class);
        }

        public String reliableMock() {
            return "eae";
        }
    }

This properties, for example, not work. It's not that I want the IDE to be completable, I just want them working.

Can you explain what "But it does not work, it does not recognize these commands" means?

Well, I have some services that are being closed by the circuit breaker because of the timeout, which means they are delaying more than one second (default timeout), which would be normal for them (their functionality) and is closed (which I not want). I have tried some properties I see in some examples, documentation to solve this problem, like the following:

Routes in Zuul Proxy Server:

zuul:
  routes:
    AnyService:
      path: /any/**
      sensitive-headers: Set-Cookie, Authorization
   ...

Properties that I have tried to disable the timeout checking and did not work:

hystrix:
    command:
        AnyService:
            execution:
                isolation:
                    thread:
                        timeoutInMilliseconds: 15000
            circuitBreaker:
                ...
            metrics:
                ...

I get this error:
Caused by: com.netflix.hystrix.exception.HystrixRuntimeException: StilingueUrlFetchService timed-out and no fallback available.

Property for disable the circuit breaker that I tried last case (that also did not work):
hystrix.command.default.circuitBreaker.enabled: false

So I even tried to set these properties via java code and I also could not make things work, I'm new to Spring Cloud. I need a way forward, I need to deliver this functionality that is being a barrier in our development. Some idea for I debug this problem?

It was my mistake, the Hystrix properties are loaded into the system (they just do not appear in /health, which I think I should). The problem I had not solved was TIMEOUT from the Ribbon, and I thought it was Hystrix. I extended the default value of these properties and things worked fine:
ribbon:
  ReadTimeout: 60000
  ConnectTimeout: 60000

@christianf2029 I want to ask you how you solved it？I had a similar problem, and I added the following configuration to the application. YML configuration, but it didn't work, and I received the same error.

management:
endpoint:

hystrix:

  config:

    hystrix.command.default.execution.isolation.thread.timeoutInMilliseconds: 60000

    ribbon.ConnectTimeout: 3000

    ribbon.ReadTimeout: 60000

    ribbon.OkToRetryOnAllOperations: true

    ribbon.MaxAutoRetriesNextServer: 2

    ribbon.MaxAutoRetries: 2

@christianf2029
Please learn how to format code on GitHub.
If you have a question please use StackOverflow or Gitter.  If you believe there is a bug please open an issue with a sample to reproduce the problem.

hystrix:
command:
fallbackcmd:
execution:
isolation:
thread:
timeoutInMilliseconds: 400000
im getting error in hytrix


[BUG] Autotrain fails due to missing metadata.jsonl, after removing my metadata.jsonl file.

Prerequisites

[X] I have read the documentation.
[X] I have checked other issues for similar problems.

Backend
Hugging Face Space/Endpoints
Interface Used
UI
CLI Command
No response
UI Screenshots & Parameters

Error Logs
Removed file: /app/.cache/autotrain/863f2b2b-5c1e-40df-9c6c-bec8a6c71a6d/metadata.jsonl
INFO:     <IP_ADDRESS>:54118 - "POST /ui/create_project HTTP/1.1" 500 Internal Server Error
ERROR:    Exception in ASGI application
Traceback (most recent call last):
File "/app/env/lib/python3.10/site-packages/uvicorn/protocols/http/httptools_impl.py", line 411, in run_asgi
result = await app(  # type: ignore[func-returns-value]
File "/app/env/lib/python3.10/site-packages/uvicorn/middleware/proxy_headers.py", line 69, in call
return await self.app(scope, receive, send)
File "/app/env/lib/python3.10/site-packages/fastapi/applications.py", line 1054, in call
await super().call(scope, receive, send)
File "/app/env/lib/python3.10/site-packages/starlette/applications.py", line 123, in call
await self.middleware_stack(scope, receive, send)
File "/app/env/lib/python3.10/site-packages/starlette/middleware/errors.py", line 186, in call
raise exc
File "/app/env/lib/python3.10/site-packages/starlette/middleware/errors.py", line 164, in call
await self.app(scope, receive, _send)
File "/app/env/lib/python3.10/site-packages/starlette/middleware/sessions.py", line 85, in call
await self.app(scope, receive, send_wrapper)
File "/app/env/lib/python3.10/site-packages/starlette/middleware/exceptions.py", line 65, in call
await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send)
File "/app/env/lib/python3.10/site-packages/starlette/_exception_handler.py", line 64, in wrapped_app
raise exc
File "/app/env/lib/python3.10/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app
await app(scope, receive, sender)
File "/app/env/lib/python3.10/site-packages/starlette/routing.py", line 756, in call
await self.middleware_stack(scope, receive, send)
File "/app/env/lib/python3.10/site-packages/starlette/routing.py", line 776, in app
await route.handle(scope, receive, send)
File "/app/env/lib/python3.10/site-packages/starlette/routing.py", line 297, in handle
await self.app(scope, receive, send)
File "/app/env/lib/python3.10/site-packages/starlette/routing.py", line 77, in app
await wrap_app_handling_exceptions(app, request)(scope, receive, send)
File "/app/env/lib/python3.10/site-packages/starlette/_exception_handler.py", line 64, in wrapped_app
raise exc
File "/app/env/lib/python3.10/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app
await app(scope, receive, sender)
File "/app/env/lib/python3.10/site-packages/starlette/routing.py", line 72, in app
response = await func(request)
File "/app/env/lib/python3.10/site-packages/fastapi/routing.py", line 278, in app
raw_response = await run_endpoint_function(
File "/app/env/lib/python3.10/site-packages/fastapi/routing.py", line 191, in run_endpoint_function
return await dependant.call(**values)
File "/app/env/lib/python3.10/site-packages/autotrain/app/ui_routes.py", line 349, in handle_form
data_path = dset.prepare()
File "/app/env/lib/python3.10/site-packages/autotrain/dataset.py", line 223, in prepare
preprocessor = ObjectDetectionPreprocessor(
File "", line 11, in init
File "/app/env/lib/python3.10/site-packages/autotrain/preprocessor/vision.py", line 184, in post_init
raise ValueError(f"{self.train_data} should contain a metadata.jsonl file.")
ValueError: /app/.cache/autotrain/863f2b2b-5c1e-40df-9c6c-bec8a6c71a6d should contain a metadata.jsonl file.
Additional Information
I am trying to use autotrain to fine tune an image detection model, and the training fails to start. It throws a 500 error, saying that the metadata.jsonl file is missing, but right before this it gives a message saying that it removed my metadata.jsonl file. I have formatted my data acording to these docs, although there seem to be some contradictions in the instructions on this page.

thanks for reporting this.
fixed in version 0.7.104 and above.


"Include Selected Item in Import" Fails with exception

Selecting "Include Selected Item in Import" in the "Import" screen and then initiating an import, immediately throws the following exception. For the time being, this checkbox has been disabled in the bundled "external-content" sub-package.
[Emergency] Uncaught BadMethodCallException: Object->__call(): the method 'getType' does not exist on 'PhpTek\Exodus\Model\StaticSiteContentSource'

Any fix for this should include markdown and inline documentation for what this feature is and what it should do.


Feature test cql

Please review changes made for DateTime comparison.  Current DateTime comparison changes date passed in and never passes based on expected output demonstrated by the tool.  The modified approach checks for instanceof DateTime then utilizes simple toString() for left/right comparison.

The source for this test is actually the CQL specification repo here:
https://github.com/HL7/cql/blob/master/tests/cql/CqlTypeOperatorsTest.xml
If there are flaws in the test specification lets fix them in the upstream repo.


Introduce http probing

Introduces http probing.
The agents are now able to measure the duration of http requests that are sent to netchecker-server and to other hosts by URL provided via command-line argument "probeurls". "probeurls" can hold several URLs divided with ";" or ",". Measurement is implemented using "github.com/tcnksm/go-httpstat" library. Measurements for the each http host are done with "reportinterval" interval (http probes are started simultaneously for all the hosts). In order to get comparable results for every measurement connection is closed after every single probe completion.
Result of each probe is represented with a set of variables: "Total", "ContentTransfer", "Connect", "DNSLookup", "ServerProcessing", "TCPConnection". Those are packed and sent to the netchecker-server within keep-alive message using the following structure:
"network_probes":[     {"URL":"http://ipinfo.io/", "Result":1, "Total":473, "ContentTransfer":0, "TCPConnection":93, "DNSLookup":99, "Connect":193, "ServerProcessing":279},     {"URL":"http://www.kernel.org/", "Result":1, "Total":161, "ContentTransfer":162, "TCPConnection":51, "DNSLookup":39, "Connect":91, "ServerProcessing":47},     {"URL":"http://netchecker-service:8081/api/v1/ping", "Result":1, "Total":94, "ContentTransfer":0, "TCPConnection":0, "DNSLookup":1, "Connect":2, "ServerProcessing":91} ]
Netchecker-server now has all the required information to provide metrics on hosts availability and timings.
Closes: https://github.com/Mirantis/k8s-netchecker-agent/issues/11

This change is

Reviewed 2 of 4 files at r1, 3 of 3 files at r3.
Review status: all files reviewed at latest revision, 2 unresolved discussions.

Comments from Reviewable

Review status: all files reviewed at latest revision, 2 unresolved discussions.

Comments from Reviewable

-(in progress)

Review status: all files reviewed at latest revision, 2 unresolved discussions.

Comments from Reviewable


[CSSolver] Solve multi-statement closures in source order

Currently solver picks the first conjunction it can find,
which means - the earliest resolved closure. This is not
always correct because when calls are chained closures
passed to the lower members could be resolved sooner
than the ones higher up but at the same time they depend
on types inferred from members higher in the chain.
Let's make sure that multi-statement closures are always
solved in order they appear in the AST to make sure that
types are available to members lower in the chain.

@swift-ci please test source compatibility

@swift-ci please test macOS platform


Pack issue

Pack Name: Create: Above and Beyond
locates pack just fine by typing yes fails to download pack

same happend to me no fix yet

Nevermind i found a solution just follow these steps
first put half of the name of the modpack

second put your modpack name with the caps

then it should start downloading

I did just realise that was actually a problem. Did close this too early. But it is fixed after the month! Well at least its fixed.


Landsat Band 5?

NIR not interesting for this project?
Anyway, well done!

Thanks for publishing.


Add tournament total score

Add a column on the database to have the tournament total score

Re open because PR referenced invalid value


Maven issues

Came across the following two issues with Maven

Attributes related to Maven opts were set only if there are custom certs which is changed as part of a recent commit. This results in cluster build failures.
/usr/local/maven/conf/settings.xml is not getting updated when a custom Maven repo URL is provided resulting in using the default Maven repo.

I believe this is resolved.

I think we may have one more issue here. On an Internet connected hosts the following code runs but there is no MITM to worry about:
https://github.com/bloomberg/chef-bach/blob/805bc2cc407e720fad0d329c1b87ef0a5114e515/cookbooks/bcpc-hadoop/recipes/maven_config.rb#L33-L39


Failed to activate the spotify-linux package

[Enter steps to reproduce below:]

...
...

Atom Version: 0.207.0
System: elementary OS
Thrown From: Atom Core
Stack Trace
Failed to activate the spotify-linux package
At Module did not self-register.

Error: Module did not self-register.
    at Error (native)
    at Object.module.(anonymous function) (ATOM_SHELL_ASAR.js:118:20)
    at Object.module.(anonymous function) (ATOM_SHELL_ASAR.js:118:20)
    at Object.module.(anonymous function) [as .node] (ATOM_SHELL_ASAR.js:118:20)
    at Module.load (module.js:347:32)
    at Function.Module._load (module.js:302:12)
    at Module.require (module.js:357:17)
    at require (module.js:376:17)
    at bindings (/home/garox/node_modules/dbus-native/node_modules/abstract-socket/node_modules/bindings/bindings.js:76:44)
    at Object.<anonymous> (/home/garox/node_modules/dbus-native/node_modules/abstract-socket/lib/abstract_socket.js:4:34)

Commands

Config
{
  "core": {
    "themes": [
      "dark-flat-ui",
      "one-dark-syntax"
    ]
  },
  "editor": {
    "invisibles": {}
  }
}

Installed Packages
# User
dark-flat-ui, v1.1.4
minimap, v4.9.4
spotify-linux, v0.3.0

# Dev
No dev packages

Could you please move this to the spotify-linux package?  Thanks.


How to authorise eval command for user in docker-compose

I need my user to run the eval command on the admin db. Is it possible to set this in the docker-compose file?

Are you looking for something like https://github.com/docker-library/docs/tree/master/mongo#initializing-a-fresh-instance

yes, thank you!


Concurrent progress bars

Summary
Implements concurrent progress bars. Resolves https://github.com/astral-sh/uv/issues/1209.
Test Plan
https://github.com/astral-sh/uv/assets/34988408/b21bdfbb-8817-4873-a65c-16c9e8c7c460

could it be sorted (the largest at top)?

@T-256 I put the largest at the bottom which looks more natural, in my opinion.
https://github.com/astral-sh/uv/assets/34988408/52915706-5349-48b4-82e4-a72f8b1c9846

The code generally looks good (well done) but need to find a bit of time to play with this myself to see if I have any feedback on the UX.

Just tested this on a large requirements file, I think any downloads <250kb shouldn't be displayed. The output changes too fast for it to be useful.

We also probably want a way to disable this output.

We could consider making it opt-in. (That would also make it less risky to ship.)

What's the risk, specifically? It seems improbable that this will break people's workflows right?

We do have a preview option now though, if you really want to gate it. A dedicated setting might make sense too? but opt-in seems wrong.

I think the risk is just that it’s overly verbose for most package installs and may require tuning. I would be fine shipping it under preview so we can get feedback on the UI/UX. I haven’t had a chance to play with it myself yet though.

I don't mind iterating on display ux without opt-in, it feels much safer than other changes we make and we release very often.

Yes, from me at least - not sure if others are planning to review.

I'd love to get this merged, I don't think it's great to have it hanging for weeks. Anything I can do to move this forward?

I did test it and was happy with it but I can do more investigation.
@ibraheemdev can you rebase the branch?

I will review and merge today.

I'll rebase. I am a little concerned about the output when you have a lot of small downloads though, e.g. https://github.com/astral-sh/uv/issues/2706#issuecomment-2115781002. Even kitty was flickering a bit. We can probably buffer updates to the terminal a bit.

If anyone has "good" test cases post 'em here so we have some common ground when considering the behavior.

I'm also supportive of including an opt-out environment variable.

I would still be fine making it opt-in if we want to get more feedback before stabilizing :)

Testing with
cargo run -q -- pip install anyio --reinstall --no-cache
cargo run -q -- pip install pydantic --reinstall --no-cache
cargo run -q -- pip install prefect --reinstall --no-cache
cargo run -q -- pip install pyqt5 --reinstall --no-cache

All good to me

LGTM and as Charlie said, it could be opt-in via --preview and after stabilization make it default behavior. Also, as Zanie said we can have an option to opt-out from it.

We can probably buffer updates to the terminal a bit.

Let's get some feedback from users, then we can set this interval value with more confidence.

Should we just move behind preview to unblock the decision? @ibraheemdev do you want it to ship to stable?

I'm fine with merging this behind preview or an opt-in flag, as long as it's accessible because it can be useful for debugging.

I have a medium preference for shipping it in stable with an opt-out, but that requires a separate mechanism than --preview 🤷♀

Let's just move it to --preview to get it unblocked I think.

I like how pip's progress bars are left-aligned and have a default width -- as-is the display is too wide IMO on my monitor:

How hard is it to achieve something like that?

To achieve that, I guess we'd need to put the package name above the bar, or to the right of it, to achieve consistent alignment?

Or use a fixed size for the package name. I can play with it.

Here's a slightly different layout. The colors are washed out in the video but it's green on dim:
https://github.com/astral-sh/uv/assets/1309177/b7ada082-cb52-4553-9b1c-1d2e52d1bc62

Thoughts?

@charliermarsh your design looks quite nice, I would be happy to switch to that.

We can add a --no-progress flag?

After seeing this in the release notes i was afraid it would cause this
But in my testing it didn't, so that's great :)