I have a troubleshooting suggestion

This is for the situation when you're dealing with a failing build pipeline and have no idea on what and where got built.  This is painful because you cannot download artifacts if the build pipeline fails, you can just stare at the logs.
Add into the build pipeline an "AzureBlob File Copy" Task, set its Source field to $(Build.Repository.LocalPath) and fill the 'RM Storage Account' and 'Container Name' fields with the details of your destination Blob Container.   That's all you need, everything will get dumped there.

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

ID: 1e834fd0-59c9-3f45-a09d-88571d94c62e
Version Independent ID: b798ba39-ef08-55eb-3fa0-731782a1d7e0
Content: Troubleshoot builds and releases - Azure Pipelines
Content Source: docs/pipelines/troubleshooting.md
Product: devops
Technology: devops-cicd
GitHub Login: @steved0x
Microsoft Alias: sdanie

"Azure File Copy" is the correct name of the task.

@eugen-nw Thank you for this idea - I am updating this article with some other changes and I would like to include this tip. To clarify, your suggestion is, for a failing pipeline running on Microsoft-hosted agents (since you can control access to self-hosted agents and inspect them after the fact) - to put this task somewhere to copy out the build directory so you can inspect it for clues? Where would you put the task? As the last step of a job, with previous steps containing continueOnError? Or am I misunderstanding? Thank you.

Hi @steved0x  Yes, the problem I were wrestling with was taking place in an Azure build pipeline, agent that I could not access.  I do not remember exactly where did I insert the "AzureBlob File Copy" Task, most likely just before the task that was failing.  I am not that sophisticated as to know about continueOnError - cannot say how many people are - so that was certainly not the spot I've used.

The problem I was having was that the build could not find something and I had no idea of what exists and where.


Added Ecplise and PyDev projects.

Any links to documentation to explain what these files are for, and why they can be safely ignored?

.project file

Both of your mods exist in the Global/Eclipse.gitignore. Include that in your base gitignore and you'll be just fine

OK Thanks.


Restore use of SHARE CHMDIR at NCCS

With the move of the L91, L181, etc. files into $SHARE/gmao_ops, we can "undo" the hacks for multiple levels.

Note that one #151 gets in first, this PR needs to be amended to remove the same hacks from scm_setup

SCM has been updated.
Note we might want a @mmanyin check on the new chem_setup scripts to make sure I didn't break GMI in my PR binge :)

The changes look straightforward.   When this gets merged into 'develop',  I will test the 3 alternate chemistry modules.  I don't anticipate a problem.


Include statement in profile

Hello!
Could you add possibility to include 1 profile into another profile?
E.g. I have base profile:
name: base
config:
  user.network_mode: link-local
  user.vendor-data: |
    #cloud-config
    system_info:
      apt_get_command:
        - 'apt-get'
        - '-y'
        - '--force-yes'
        - '--quiet'
...

vlan profile:
name: vlan556
config: {}
description: Container device for 556 vlan
devices:
  eth0:
    nictype: bridged
    parent: br0.556
    type: nic
usedby: []

And I need to create some project machine, which would have base profile and 1 of the vlan's profile (there may be many vlan profiles)
Now I need to write lxc launch ubuntu: container -p base -p vlan556
I want to shorter this to lxc launch ubuntu: container -p <containers_project>
where <containers_project> profile contains something like this:
name: <containers_project>
include:
  - base
  - vlan556

Hmm, I'd rather we not do that. It's already pretty painful to compute exactly what needs to apply to a given container without having to account for potential loops and dual-application of profile chains...

We can keep this open as a "maybe" and see if there's a lot of interest for it.

We've not seen any particularly good reason for this and profile resolution is already a bit of a headache both internally (cascading changes to running containers) and in people's mind.
Supporting includes and having to deal with potential loops and complex ordering doesn't seem worth it so I'm closing this. It's not to say we won't reconsider it, but for now, we have no plan to do this.


CLOUDSTACK-9699: Add global setting for enable/disable Metrics feature

The Metrics view for each type of entity basically fires APIs and calculates required values on the client end. For e.g. to display memory usage etc at the zone level, it will fetch all zones. For each zone it will fetch pods->cluster->host->VMs
For a very large Cloudstack installation this will have a major impact on the performance.
Ideally, there should be an API which calculates all metrics in the backend and the UI should simply show the values. However, for the time, introduce a global setting called enable.metrics which will be set to false. This will cause the metrics button not to be shown on any of the pages.
If the Admin changes this to true, then the button will be visible and Metrics functionality will work as usual.
In this pull request, have also added JUnit test case for listCapabilities API.
Additionally added a test case in marvin called test_global_settings as part of the smoke tests which test the output of the listCapabilities API and checks if this setting is present or not.
Refer to CLOUDSTACK-9699 for more details.

Thank you @jburwell. I will incorporate the comments in a couple of days and resubmit.

@rashmidixit I'm working on writing separate metrics view apis (backend/apis), they will improve the performance significantly. An explicit global settings is not necessary, pl. hold on this PR.

I'm working on improving the metrics view feature by implementing the logic as backend APIs, will post a PR this/next week. Thanks.

@rhtyd Thanks for the update.

This is not needed with PR #1944, though changes around capability refactoring can be separated.

Closing this based on the new PR  #1944.


Runtime: Investigate and fix too many open files error

Report:

The application went into a unusable state and I see following error in the logs (Anshul Khandelwal): The directory did not have too many files.

2023-11-06T22:19:58.819	ERROR	Stopped watching for file changes	{"err": "watch failed: \"/Users/kanshul/bug-bash/ag_news_csv/imdb/unsup/20164_0.txt\": too many open files"}
2023-11-06T22:19:58.819	ERROR	Reconcile failed	{"name": "parser", "kind": "ProjectParser", "elapsed": "10m58.933s", "error": "watch failed: \"/Users/kanshul/bug-bash/ag_news_csv/imdb/unsup/20164_0.txt\": too many open files"}

There might be legitimate reasons for this (you can't have very many files open by default unfortunately), but there might also be a leak in the file watcher that doesn't remove (or redundantly adds) file watches.

Haven't been able to reproduce this issue even after adding ~4k files. Did find one issue wrt directory deletion which is fixed here : https://github.com/rilldata/rill/pull/3496
Closing for now.


After the update to 2.1-preview2 new DocumentClient() fails only on Azure, killing the whole application

Posting this here because the DocumentClient library doesn't seem to have a proper separate repo. I've also filed it here: https://github.com/Azure/azure-documentdb-dotnet/issues/495, but it seems pretty dead to me.
I am having a very strange issue here. This all started happening after the update to preview2 of .NET Core 2.1.
The project works totally fine on my local machine, but fails after a few clicks when hosted on Azure. I have isolated the issue to a single line, which is
new DocumentClient(settings.Endpoint, settings.ReadKey);
The settings are fine, the same issue appears if I hardcode the strings.
This line is called in a constructor for a service that's registered in Startup.cs.
The strange thing is that I don't get any exceptions, I don't get any DI errors, after a few minutes it just says that the process was terminated and the whole application stops working. It also happens on exactly the 2nd time I'm calling the controller into which I'm injecting the service.
Any pointers or hints?
I'm using the latest (1.9.1.) version of the Microsoft.Azure.DocumentDB.Core assembly and the dotnet --version output is 2.1.300-preview2-008530, both on local and on Azure.

Can you share a small app that reproduces the issue?

Okay, so I've resolved the issue. I had to register DocumentClient as a singleton. That, however, does not explain why it was not failing on my local machine (and on local machines of many of my colleagues). An explanation would be fantastic.
It would be great if the rule about using a singleton was documented better and not hidden in a single blog post about performance tips. I will create an issue about this, as I believe this is extremely important in saving a lot of time for people in similar situations.


Progressive error logging when loading chunks

What kind of change does this PR introduce?
Now you can receive the status of the request code.
Did you add tests for your changes?
No.
Does this PR introduce a breaking change?
I dealt with the problem of downloading a certain number of chunks. And to understand the nature of the error, I need to know why the chunk was not loading.

This has problems in cross-origin scenarios. I also guess this doesn't use the Code Cache.


Add Contributors

This issue is for adding contributors. I will start us off, but this is by no means complete. Please help me complete it.
Bot usage: https://allcontributors.org/docs/en/bot/usage
Contribution types: https://allcontributors.org/docs/en/emoji-key
NOTE: Using the bot will automatically create a PR with the required changes for updates. We need to ensure there are no conflicts before merging.
Things will generally go smoother if you add one contributor at a time.

@all-contributors please add @spirosChv for code, test, infrastructure.

@all-contributors please add @ebatty for code, test, infrastructure.

@all-contributors please add @iamzoltan for code, test, infrastructure.


Review notes

It looks like the hidden .rspec file in this project is missing - probably due to copying and pasting the contents of this folder in Finder or another file manager. This would cause the specs to crash when you try to run them. You can get around this by manually entering the configuration when you run the specs like this:
bundle exec rspec --require spec_helper --format documentation --color

These are the failures I'm seeing:
Failures:

  1) MethodsPracticeHelpers#bootstrap_alert when passed both a message and a type div tag contains exactly 2 elements
     Failure/Error: expect( @alert.children.size ).to eq(2)

       expected: 2
            got: 3

       (compared using ==)
     # ./spec/helpers/methods_practice_helpers/bootstrap_alert_spec.rb:75:in `block (5 levels) in <top (required)>'

  2) MethodsPracticeHelpers#bootstrap_alert when passed both a message and a type div tag class attribute includes "alert-TYPE"
     Failure/Error: expect( @class_attr.value.include?("alert-#{@type}") ).to eq(true)

       expected: true
            got: false

       (compared using ==)
     # ./spec/helpers/methods_practice_helpers/bootstrap_alert_spec.rb:53:in `block (6 levels) in <top (required)>'

  3) MethodsPracticeHelpers#bootstrap_alert when passed only a message div tag class attribute includes "alert-info"
     Failure/Error: @contents = html_of bootstrap_alert(@message)
     ArgumentError:
       wrong number of arguments (1 for 2..3)
     # ./helpers/methods_practice_helpers.rb:10:in `bootstrap_alert'
     # ./spec/helpers/methods_practice_helpers/bootstrap_alert_spec.rb:213:in `block (4 levels) in <top (required)>'

See if you can resolve those, so that the Bootstrap alert acts as expected in the specifications. When you get 0 failures after running bundle exec rspec --require spec_helper --format documentation --color, the program is definitely working the way the hypothetical front-end devs are expecting.
If you get stuck, don't hesitate to let me know and I'll be happy to point you in the right direction. As I mentioned in our email, you have until the end of the day Friday to get everything fixed here, so you can focus on other projects today if you need to.

Should be fixed now

:+1: Excellent!


Console output in jenkins is not correct

From @andrea-raabe on November 23, 2017 13:57
The problem
The console output with the spec reporter in jenkins is not correct.
The checkmark (and special signs) displayed not correct: ✓
Environment

WebdriverIO version: 4.9.9
Node.js version:
Standalone mode or wdio testrunner:
if wdio testrunner, running synchronous or asynchronous tests:
Additional wdio packages used (if applicable):

Details
`
[chrome #0-1] Session ID: cc6195047bb0ee11656db99c50c73114
[chrome #0-1] Spec: /home/jenkins/workspace/Frontend/PortalDev-03-EndToEndChrome/tests/portal/angebotsalarm.js
[chrome #0-1] Running: chrome
[chrome #0-1]
[chrome #0-1]   Angebotsalarm
[chrome #0-1]       ✓ Bei Klick ...
[chrome #0-1]       ✓ Der Dialog ...
[chrome #0-1]
[chrome #0-1]
[chrome #0-1] 2 passing (21s)
[chrome #0-1]
`
Copied from original issue: webdriverio/webdriverio#2469

Not fullly fixed. In summary I still see it:
205 passing (1782.90s)
18 skipped
2 failing

1) People test navigate each group:
element ("span=036") still not existing after 10000ms
running chrome on linux
running firefox on linux
Error: element ("span=036") still not existing after 10000ms
    at Context.it (test/webclient/people/people.spec.ts:14:17)
    at Promise.F (node_modules/wdio-sync/node_modules/core-js/library/modules/_export.js:35:28)
    at elements("span=036") - isExisting.js:46:17
    at isExisting("span=036") - waitForExist.js:67:22

the output is still wrong

@sherlock1982 the other part will be tackled by webdriverio/webdriverio#878

But the issue #878 is very old.
The output is wrong since the version 4.9.6 (10.11.17).
[chrome #0-2]   /api/ URL Generator
[chrome #0-2]       ✓ /api/url/brochure/{id}
[chrome #0-2]       ✓ /api/url/brochure/{id}#page
[chrome #0-2]       ✓ /api/url/product/{id}
[chrome #0-2]       ✓ /api/url/store/{id}
[chrome #0-2]
[chrome #0-2]
[chrome #0-2] 4 passing (11s)

@andrea-raabe please check wdio-spec-reporter version 0.1.3. It was just published and this issue is fixed there. Except the footer mentioned here.

thx, now it works


Can we collect coverage statistics for tests written/run with Atomus?

Hi @krasimir / @sielay we are considering using Atomus for testing our projects (looks really good!)
however we have a question: can we collect test/code coverage statistics (e.g. using Istanbul) for tests we write with Atomus? is there an example somewhere where someone has done this? Thanks!

A really good question. Let me try to see how this may look like.


VSCode-like session management

I would like to suggest a more advanced way of managing sessions.
Instead of displaying a list of files from a session, it would be more convenient to immediately open the last state of the session and automatically save this state on exit. The states for each session could be .vim or .lua files that contains commands to execute and stored in a user-specified folder.
What do you think about it?

@Shatur95 I use https://github.com/tpope/vim-obsession for this purpose. I'm not sure if what your asking would be considered outside the scope as an extension of telescope. How would you expect it to work?

vim-obsession is a great plugin, but I can't switch between sessions using Telescope.
This plugin is also awesome, but it does not allow loading the session state, only allows switching between files.
So, I suggesting a slightly different behavior. It would be much more convenient to load the session immediately instead of selecting files. I would imagine that it works like vim-obession, but with the ability to select a session using Telescope.
Perhaps you are right, this can be considered as out of scope for this plugin and will require a complete redesign of the plugin. But I still think it's a good idea.

I think it's a really good idea @Shatur95 and a useful feature. Also something I've considered previously. I just need to figure out how exactly to implement it, and if it will be simple enough to be useful within the scope of a telescope plugin. Maybe something like pressing 's' on a project in project selection loads a project session. But then, do I also allow users to create sessions, and do I automatically update the session files, how vim-obsession does. I guess ideally the answer would be yes to both of those. I think I need to do this.

Maybe something like pressing 's' on a project in project selection loads a project session.

I would suggest to do it on <CR> and show list of the files on f.

But then, do I also allow users to create sessions, and do I automatically update the session files, how vim-obsession does. I guess ideally the answer would be yes to both of those. I think I need to do this.

It would be awesome.

I would suggest to do it on <CR> and show list of the files on f.
I think default behaviour for  should be file selection still, as telescope is ultimately a plugin for searching files, however I'll add the ability to customise it in their config to allow it to be used for sessions.

I think default behaviour for  should be file selection still, as telescope is ultimately a plugin for searching files, however I'll add the ability to customise it in the users config to allow it to be used for sessions.

I would say that Telescope is a general-purpose picker, not only for files. And in this case, it allows you to select sessions. Typically Telescope does not allow you to select something twice. But if it can be customized, it will be great :)

I decided to wrote a separate plugin for this purpose.

@Shatur95 No probs. Feel free to put in a PR if you want to add it here also.

Personally i want to switch to a project and just see the latest session that i was working on.

Second this notion. Having the ability to define projects is great. Yet, once the directory location and files are reinstated, the session state of the last time I worked on that project is the logical next step.


Additional transmutations

Something -> snow
Brown -> red mushroom
Red -> brown mushroom (conditions)

wool carpet on diorite -> snow


File changes in folder packages are not being detected to redeploy on Windows

Currently, I have my lambda function code and schema.graphql placed in the packages folder, for details the structure is like this:

packages/core
packages/functions
packages/graphql/schema.graphql

I expect that when I change any files in packages folder, the SST CLI should build and redeploy the changes for me, but it doesn't.
So I have to stop the CLI and run sst dev again.
Could you guys help me with this issue?
Also, I discussed with the team about this issue on Discord:
https://discordapp.com/channels/983865673656705025/1075623745022079027

Experiencing the same problem

Experiencing same with blank project created with npx create-sst@latest
Chaning the "Hello World." to "Hello World!" in packages\functions\src\lambda.ts doesn't update until running dev again.

What OS r u using? @harrycollin @GinIsTheAnswer

@fwang Windows 10 Pro 22H2

Windows 11

The PR is in https://github.com/serverless-stack/sst/releases/tag/v2.1.6. I'll close this issue for now? Feel free to reopen if you are still having this problem.


No aria-activedescendant on input

I'm using cmdk within a Radix Popover. Looks just like the example:
https://codesandbox.io/p/sandbox/radix-dropdown-combobox-forked-j8jjph?file=%2Fsrc%2FApp.tsx%3A22%2C49
For some reason, my input doesn't seem to have an aria-activedescendant value on it, so when I use the arrow keys up and down to select different values it doesn't read them out to me.
Is this a feature we should implement ourselves? The examples on the site have the attribute so I assumed it was built in.
Is this something that broke at some point?

Hey @leo-petrucci,
That was fixed in #108 and will be in the next release!


docs: update vite sveltekit instructions

Change plugin WindiCSS.default() to WindiCSS() to bring it in line with change https://github.com/windicss/vite-plugin-windicss/commit/713743fec2a2961351797fec8e549f13083fee94
Remove svelte-preprocess as it is not present by default and could potentially mislead users into thinking it is necessary
Rename renaming $layout.svelte to newer __layout.svelte, changed as of 1.0.0-next.102
The svelte config now actually looks like the svelte config that is default

welp i actually messed something up AGAIN. i'll be extra careful with the next PR

@steven-lay just a quick tip to learn some. You can actually force push to your own branch you used in the PR and the PR would be updated without the need to reopen a new one. :)

ah sorry about that, thanks for the tips


feature request: stack annotations

Stack annotations help to understand the opcode execution - see Foundry's debug:

Proposal:
add opcode annotations aside of the stack boxes

Thanks for the suggestion, will add a bounty for this one and perhaps someone from the community picks it up


Make SetString return errors more consistently

Previously, SetString wouldn't consistently return syntax errors.
Sometimes, it would set a syntax error in the Context's traps and not
return an error; sometimes it would do both. Now, it always both sets a
syntax error in the traps and returns an error.
I think this only actually affected invalid exponents, because the similar
issue in mantissa scanning was code that couldn't have been reached due
to form scanning.

lgtm


How do I extract the colors of each vertex after loading the .obj file ?

How do I extract the colors of each vertex after loading the .obj file? I am only able to extract the coordinates of each vertex using the code below. How about the colors of each vertex?
    object = Wavefront(object_name+".obj", create_materials=True, collect_faces=True)

    # collect faces
    faces = []
    for mesh in object.mesh_list:
        faces = faces + mesh.faces

    # collect vertices
    vertices = object.vertices

Colors should be in object.vertices and also interlaved in each material. You will have to look at the vertex format in the last case.
See: https://github.com/pywavefront/PyWavefront/issues/87#issuecomment-464348971


Fallback is being called twice

Considering that the circuit is closed and that the fallback function always returns a promise rejection: If the action triggered by the breaker is rejected and it took longer than the breaker timeout, the fallback function will be called twice.
First time it's called because the breaker timeout is achieved. Second time it's called because the action was finished with a rejection.
Due to the second call, we get the following error:

(node:14582) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 2): StatusCodeError: 500 - {"statusCode":500,"message":"Server error"}
(node:14582) [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.js Version: 8.9.4
Operating System: Darwin DuarteMendes.local 17.5.0 Darwin Kernel Version 17.5.0: Mon Mar  5 22:24:32 PST 2018; root:xnu-4570.51.1~1/RELEASE_X86_64 x86_64
Steps to Produce Error:
const circuitBreaker = require('opossum');

async function forceFallbackToBeExecutedTwiceOnTheSameExecution () {
    const breaker = circuitBreaker(timerBasedFunction, { timeout: 3500 });

    breaker.fallback((timer, err) => Promise.reject(err));
    breaker.on('fallback', () => console.log('Fallback was called!'));

    [0, 1, 2, 3, 4].forEach(async function (i) {
        try {
            const result = await breaker.fire(i * 1000);
            console.log(result);
        } catch (err) {
            console.log(err);
        }
    });
}

function timerBasedFunction (timer) {
    return new Promise((resolve, reject) => {
        setTimeout(() => {
            if (timer >= 4000) {
                return reject(`Error for the ${timer}ms timer`);
            }

            return resolve(`Result for the ${timer}ms timer`);
        }, timer);
    });
}

forceFallbackToBeExecutedTwiceOnTheSameExecution();

Result:
Result for the 0ms timer
Result for the 1000ms timer
Result for the 2000ms timer
Result for the 3000ms timer
Fallback was called!
{ Error: Timed out after 3500ms
    at Timeout.setTimeout (/Users/duartemendes/projects/testing-opossum/node_modules/opossum/lib/circuit.js:322:15)
    at ontimeout (timers.js:475:11)
    at tryOnTimeout (timers.js:310:5)
    at Timer.listOnTimeout (timers.js:270:5) code: 'ETIMEDOUT' }
Fallback was called!
(node:35201) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 2): Error for the 4000ms timer
(node:35201) [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.

@lance could you take a look at this? also at #200 please :)

Fixed in https://github.com/bucharest-gold/opossum/pull/201


Move env include/exclude to jfrog-client

[v] All tests passed. If this feature is not already covered by the tests, I added new tests.
[v] This pull request is on the dev branch.
[v] I used gofmt for formatting the code before submitting the pull request.

This PR should be merged only after https://github.com/jfrog/jfrog-client-go/pull/178 is merged.
This PR was created following the merge of https://github.com/jfrog/jfrog-client-go/pull/170 which moved the env include/exclude functionality to jfrog-client-go.

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


Fix some annotations

Coverage remained the same at 100.0% when pulling 5a3a675c4c71adae2d9032547f0f5182828c684c on 50bhan:master into 4dabd540d74799339687eb19f6d3605ee49e99b3 on mohammad-fouladgar:master.

Coverage remained the same at 100.0% when pulling 5a3a675c4c71adae2d9032547f0f5182828c684c on 50bhan:master into 4dabd540d74799339687eb19f6d3605ee49e99b3 on mohammad-fouladgar:master.


Health Check booster

similar to https://github.com/wildfly-swarm-openshiftio-boosters/wfswarm-health-check

i've started a little something here: https://github.com/bucharest-gold/nodejs-health-check

i've added it to our fork of the booster-catalog for testing, it seems to work fine.
Just need to add the docs back here: https://github.com/openshiftio/appdev-documentation/tree/master/docs/topics

booster-catalog PR's merged
just waiting on docs PR - https://github.com/openshiftio/appdev-documentation/pull/453


Table row highlight is truncated if table is displaying only 1 column

🐛 Bug Report

When hovering a row in a table that only has 1 column displayed (after other ones have been hidden), only half the row will be highlighted when hovered.
🤔 Expected Behavior

Hovering a row in a table which has all but one column hidden should highlight the whole row.
😯 Current Behavior

Hovering a row in this case will only highlight half of it.

(NOTE: highlighting works fine if table initially has 1 column. only shows when columns are changed from X->1)

💁 Possible Solution

Looks like the cell width is not being updated after the 2nd to last column is removed:
checkbox width: 55px
cell width: 422.5px
row width: 900px
🔦 Context

💻 Code Sample

see Table > hiding columns story. uncheck all checkboxes and highlight a row.
🌍 Your Environment

Software
Version(s)

react-spectrum
3.4.0

Browser
Chrome

Operating System
macOS Catalina 10.15.2

🧢 Your Company/Team

Adobe/quarry
🕷 Tracking Issue (optional)

This is potentially complex (>1 day) issue to solve


Export links in Management not working from subdirectory

Description / Beschreibung
The export links aka API URLs in Management GUI are not working if RDMO is running in subdirectory.
Expected behaviour / Erwartetes Verhalten
I would expect a link with the current subdirectory.
Therefore I would expect an API_URL setting in config/settings/__init__.py, if not already present somewhere deeper in the code.
Steps to reproduce / Schritte zum Reproduzieren

Configure webserver to serve RDMO from domain subdirectory
Set BASE_URL in config/settings/local.py to subdirectory
Go to "Management"
Click on a sidebar link within "Export"
See a HTTP 404 since the base URL is not included

Context / Kontext
RDMO 2.1.2

Hi @johlton , thanks for reporting, the fix will be released in RDMO 2.1.3 (hopefully today).

Will be part of the next release.


BUG: Updating a room name on two devices causes an error

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Sign in with any account
Create a workspace from the green plus (if needed)
Create a workspace room from the green plus (if needed)
Go offline
Click the header of the workspace room to open the room details page
Click "Settings"
Rename the room and hit save
Verify that the input is grayed out
Sign into the same account on another device or incognito window
Open the workspace room and click the header of the workspace room to open the room details page
Click "Settings"
Rename the room and hit save
Go back to the other device and go back online

Expected Result:
The room name input is no longer grayed out signaling that the name was update successfully.
When updating the room name we throw an error here if there's already a room with that name, but we should only throw an error if it is a different room that has the same name.
Actual Result:
There is a red dot and an error message saying "A room with this name already exists".
Workaround:
Dismiss and ignore the error
Platform:

Where is this issue occurring?

Web
iOS
Android
Desktop App
Mobile Web

Version Number: v1.2.15-3
Reproducible in staging?: Yes
Reproducible in production?: Yes
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:

Expensify/Expensify Issue URL:
Issue reported by: @neil-marcellini
Slack conversation:
View all open jobs on GitHub

This was fixed here. Closing


Async Client support & more

What kind of change does this PR introduce?

[x] Deprecates create_client
A Supabase client can be initialized by directly invoking the class, unlike the JS lib
[x] Renames Client to SupabaseClient
[x] Added async support (thanks to async postgrest-py)
[x] Moved custom exceptions to exceptions.py
[x] Rewrites README.md with typo, grammatical fixes, and includes async-related code, removes deprecated code

and, again i forgot to run poetry run pre-commit run --all-files so initial checks will fail

@J0 Hey, could you take a look at this? Also maybe I can DM you and become a listed maintainer while I'm working on adding realtime next.

Thanks for the PR! Looks like a great start. Left some nits - just have a few concerns:

Moving away from create_client to SupabaseClient -- this should be fine but let me check with the Supabase team if they have any concerns here as there was some past discussion around standardising client libraries. Do you mind briefly listing the advantages and disadvantages of using create_client as opposed to SupabaseClient?
async interface seems fine but not sure if we want to make use of unasync like in other libraries. Will defer to other maintainers for this one

About the first point, I'm against removing the create_client method, because at the moment the only implementation was synchronous but by adding the async option it may be necessary (if not necessary at the moment, in the future maybe) to create a create_async_client method that creates an instance of AsyncSupabaseClient asynchronously and a create_sync_client method that instantiates SyncSupabaseClient synchronously, and in the case of AsyncSupabaseClient instantiation (the "class constructor") is bound to be synchronous, so the solution in case an asynchronous process is required, such as calling an asynchronous "initialize" method, could be wrapped in the method create_async_client.

I don't see any problems with having the create_client method as we do right now, and I like to not fix things if they aren't broken for the time being 😄 What is your rationale behind this change?

Thanks for the PR! Looks like a great start. Left some nits - just have a few concerns:

Moving away from create_client to SupabaseClient -- this should be fine but let me check with the Supabase team if they have any concerns here as there was some past discussion around standardising client libraries. Do you mind briefly listing the advantages and disadvantages of using create_client as opposed to SupabaseClient?

async interface seems fine but not sure if we want to make use of unasync like in other libraries. Will defer to other maintainers for this one

About the first point, I'm against removing the create_client method, because at the moment the only implementation was synchronous but by adding the async option it may be necessary (if not necessary at the moment, in the future maybe) to create a create_async_client method that creates an instance of AsyncSupabaseClient asynchronously and a create_sync_client method that instantiates SyncSupabaseClient synchronously, and in the case of AsyncSupabaseClient instantiation (the "class constructor") is bound to be synchronous, so the solution in case an asynchronous process is required, such as calling an asynchronous "initialize" method, could be wrapped in the method create_async_client.

Not necessarily, a method to invoke an async class is not required, all you need is a base wrapper to initialize async def __ainit__(self):
See:
Async-Class on PyPi

I don't see any problems with having the create_client method as we do right now, and I like to not fix things if they aren't broken for the time being 😄 What is your rationale behind this change?

I quote you, The Zen of Python

Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.

Seeing that the create_client is derived from the JS lib, It's extra in Python, and provides zero value and lessens the readability, and simplicity of supabase-py, Invoking the class is much simpler, and easier to use.
In the case of async, we can add a async base wrapper to the actual class and use ainit;
Even changing/deprecating the method, or switching to class initialization, won't break anything because there is in fact, nothing special about the method.
My problem is that English is not my native language, and I suspect that my explanation is not enough, but I hope a proved a point here. We can choose simplicity, not complexity.

I agree with you, I don't see why there is any reason not to easily allow async. Hopefully someone can take a look at this again @anand2312

I'm a new Supabase user needing this and don't want to go 140 commits behind the main repo to get it. Someone please resolve it and merge asyncio support.

I sort of "gave up" working with supabase when i was working with realtime (and better async support) and messaged their team for something like a "sandbox" account so i could run my tests without paying anything. The agent said that "It was not their problem" and "They can't help me" even though i don't have a use for supabase myself. Just giving back to the community

If anyone is still waiting for this to get merged, just clone @rawandahmad698 's repo and downgrade postgrest-py to 0.10.3 httpx to 0.23.0 and pydantic to 1.10.2. I followed the readme and it works perfectly.

Hey @rawandahmad698,
I'm sorry to hear about your experience with seeking a sandbox account

The agent said that "It was not their problem" and "They can't help me" even though i don't have a use for supabase myself.

Do you mind sharing the relevant Discord or email thread where the exact words were used? We'll look into this and see how we can improve the support experience.
One of the features I personally like about Supabase is that it is that the stack is fully Open Source - it's possible to host supabase locally without the need for a hosted instance.  Let me know if you run into any issues getting that set up and I'd be happy to jump in.
With regards to the PR, we'll look into getting this PR updated and re-reviewed this week. Thanks for the contribution again!

Hey there! 👋
I've just released an async Supabase client for FastAPI and I'm looking for contributors to help it grow. If you're interested in collaborating on an open-source project and making an impact, your contributions are more than welcome!
Check out the repo and feel free to jump into the issues or discussions. Let's make something great together. 😃
Happy coding!

Hey everyone! 🌟 I've been diving deep into the community version of Supabase py and noticed a few areas that could use some tweaks. To address this, I've made some adjustments in my own repository, and I'd love for you to give it a try! Especially designed with FastAPI in mind, this revised version aims to enhance efficiency and compatibility.You know how Supabase js is crafted for frontend use, right? Well, I realized that the existing Supabase py is essentially a mirror of this js version, which doesn't quite fit the bill for Python web frameworks like FastAPI. In FastAPI, every request requires client instances, but I believe this approach isn't always necessary.My proposal? Let's introduce an 'auth clients dict' within the main async client. This way, we won't need to spawn excessive async clients. Instead, we can focus on auth clients, performing operations on Supabase through functions in the main async client (functions that will use the authclient with all the necessary info).I'm excited to collaborate and solve any bugs that might pop up. Let's work together to make the Supabase community even better! 😊 Feel free to join the discussion on GitHub and share your thoughts and suggestions!

Closing this out as async support has been added to the library now. Here is an example below showing how to use the async client.
from supabase._async.client import AsyncClient as Client, create_client

async def create_supabase() -> Client:
    return await create_client(url, key)


Remove ext_io_conf, otg_io_conf from usb_phy_config_t phy_config in usb_serial_init

Hello!
In attempting to use this lib with PlatformIO on a Lolin s2 mini, I came across this build error:
.pio/libdeps/lolin_s2_mini/esp32-usb-serial/src/esp32_usb_serial.cpp: In function 'esp_err_t usb_serial_init()':
.pio/libdeps/lolin_s2_mini/esp32-usb-serial/src/esp32_usb_serial.cpp:121:3: error: 'usb_phy_config_t' has no non-static data member named 'ext_io_conf'

In the test file https://github.com/luc-github/esp32-usb-serial/blob/83d29b9bdc04eef8108a65111c36396858232d8b/original_components/espressif__usb_host_cdc_acm/test/test_cdc_acm_host.c#L48 those fields aren't specified, so I figured it was probably safe to remove them.
My barebones PlatformIO example is available at https://github.com/smartin015/esp32-usb-serial-pio/ - currently builds, but I haven't attempted to run it on a device yet.

what idf version are you using with your arduino esp32 core?

no feedback means not valid issue
I close


Accept Chef License

This commit enables us to accept the chef license inside dokken
Description
[Describe what this change achieves]
Issues Resolved
[List any existing issues this PR resolves]
Check List

[ ] All tests pass. See TESTING.md for details
[ ] New functionality includes testing.
[ ] New functionality has been documented in the README if applicable

I am unable to approve this PR for some reason.


[FeatureReq - Partner Center]

Is your feature request related to a problem? Please describe.
I'm always frustrated when i open markdown files (.md). I need to install addons from third party.
Describe the solution you'd like
need to install third party addons.
Describe alternatives you've considered
I think Markdown file should be supported natively built-in edge browser and not need to install from third party addons this also make save the browser safe not to install anything.
Additional context

Hey @ebainto, thank you for contacting us. We are looking into this and will let you know as soon as we have an update.


Update documentation to address VSO.2387787: Need to document how to get side-loaded Office Online Add-Ins working in Edge

Update documentation to address VSO.2387787: Need to document how to get side-loaded Office Online Add-Ins working in Edge

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/images/allow-localhost-loopback.png
:white_check_mark:Succeeded

docs/testing/sideload-office-add-ins-for-testing.md
:white_check_mark:Succeeded

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.


Make it possible for PNG barcodes to have transparent background

Currently if you have a barcode in PNG, it will always have white
background. Given PNG supports alpha channel in images, it would be
really nice to be able to use that. This commit adds an option to
specify if you want the background to be transparent but keeps the WHITE
as default.

@toretore what do you think?

@toretore this PR won't break the existing behavior in case this is a concern, any reasons not to merge this?

Solved by e3cae50c8c29bd77fb9a9722afb6b9bde93820e9


Don't set upper limit on node version

Fixes issue https://github.com/jed/locale/issues/30

Looks like a dupe of @pahund's PR


[jaeger-v2] Consolidate v1 and v2 Configurations for GRPC Storage

Which problem is this PR solving?

Resolves #6041

Description of the changes

We were currently maintaining two entirely separate configurations for v1 and v2 for the GRPC Storage Component and were initializing v1 configurations and then translating them to the v2 configurations which were the ones actually being used. This caused an issue where one configuration field was left out of the translation method (see https://github.com/jaegertracing/jaeger/pull/6030 for more details).
In this PR, we consolidate the v1 and v2 configurations into a single config type that is directly initialized to avoid having configurations that diverge or running into issues like the one described above.

How was this change tested?

Unit tests were updated
Integration tests were not touched but should still pass since this was just an internal change and the interface was not touched

Checklist

[x] I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
[x] I have signed all commits
[x] I have added unit tests for the new functionality
[x] I have run lint and test steps successfully

for jaeger: make lint test
for jaeger-ui: yarn lint and yarn test

lgtm

@yurishkuro I don't believe this is a breaking change because the v2 Config was being used anyway. Let me know if that's incorrect.


Controller support Acl.

Now, we add a controller module, the namesrv will  have service invocations with broker, if broker open the acl feature and controller should also enable acl.

In normal conditions, the controller port is not exposed to users.


Cannot Bind app to New relic Service broker

After New Relic Service Broker tile is installed  a new Org (NewRelicServiceBroker-service-org) and new NewRelicServiceBroker-service-space Space get created hosting newrelic-broker-x.x.x app.
If the PCF admin removed the new relic app, space or org and tries to bind an app to the new relic service broker, operation will fail with "Status Code: 404 Not Found, Body: 404 Not Found: Requested route ('newrelic-xxxxxx.domain') does not exist" Error.

@jaironpm the service broker app which is wrapped in the service broker tile, runs in Org (NewRelicServiceBroker-service-org) and Space (NewRelicServiceBroker-service-space). If you remove them, the service broker app will be removed as well, and the service broker would not work.
Why does PCF admin want to remove the org?

PCF admin was using cf-mgmt to remove any org/space that was not whitelisted. they have now stopped that.
I was coming from the fact that our doc should probably mention new relic org/space is created after tile install and should not be removed for the service broker to work


chore: polkadot 0.9.26

Task linked: CU-2p79uye Upgrade to polkadot-v0.9.26

Closing in favor of #83


Update 04-refactor-state-management.md

Fix mislabelled link

Looks like this was already fixed. Thanks though!


Download Buttons for Recordings

Is your feature request related to a problem? Please describe.
When watching recordings you still need a steady internet connection. Being able to easily download e.g. lecture recordings to watch them on the go without having to rely on mobile connectivity would make the lecture more accessible to people with limited mobile data.
Describe the solution you'd like
A simple download feature to easily download recordings. Making the recordings downloadable could be an optional feature so each lecturer can decide if he or she wants the users to be able to download recordings.
Describe alternatives you've considered
Students can (and will) get the .m3u8 link from the site's sourcecode to record and/or download the videos. A feature like this will make this process more convenient.
Additional context
For example the Panopto service used for recordings of some lectures at TUM already offers this feature.

We're considering a download feature that can optionally be enabled by lecturers :+1:

I've implemented this but included a pretty steep rate limit of 250kbps for now until I know how the storage would perform when many folks download their lectures at once. You can try it out on the loadtest.

You should now be able to download lectures kind of fast.


Add Genome.contigs. Fixes #140.

This change is

Coverage decreased (-0.04%) to 80.054% when pulling 67a87ec7d654131701581dce88cb278e304b2a67 on contigs into 300f5a7f942624bcf67f8f85dee49a2fa682703e on master.


feat: Chat autocomplete tags

Pull Request Checklist

[X] Description: Briefly describe the changes in this pull request.
[X] Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.

Description
This simple pull request introduces autocomplete functionality to the "Add a tag" section in chats, improving user experience and reducing typing effort for common tags. This also partially addresses #1317. Extracting tags using the LLM can be done in another PR.

Changelog Entry
Added

Added autocomplete functionality (using datalist) to "Add a tag" section in chats
Added support for adding tags via the Enter key

Amazing work as always! LGTM!


Repeating sections on landing page

There are certain sections on the landing page which are getting repeated and I would like to work on it
So please assign  this task to me under gssoc_23

After Scrolling

I want to work on this issue . please assign to me


le.challenges[http-01].loopback should be defined as function (opts, domain, token, keyAuthorization, cb) { ... }

Hi there,
After trying in vane to make this work with my project, I can only ask for help from you guys. I'm getting the error:
le.challenges[http-01].loopback should be defined as function (opts, domain, token, keyAuthorization, cb) { ... } and should prove (by external means) that the ACME server challenge 'http-01' will succeed
This happens when I try to run my NodeJS app.
This is how I'm configuring LE:
le.create({
    server: 'https://acme-v01.api.letsencrypt.org/directory', // in production use 'https://acme-v01.api.letsencrypt.org/directory'; for testing use 'staging'
    configDir: require('os').homedir() + '/letsencrypt',
    approvedDomains: function (opts, certs, cb) {
        opts.domains = certs && certs.altnames || opts.domains;
        opts.email =<EMAIL_ADDRESS>        opts.agreeTos = true;

        cb(null, { options: opts, certs: certs });
    }
});

And here is how I start the app:
var server = https.createServer(le.httpsOptions, le.middleware(app.callback()));
server.listen(443, function () {
    log.info(`Listening at https://${this.address}`);
});

var redirectHtpps = koa().use(koaSslify()).callback();
http.createServer(le.middleware(redirectHtpps)).listen(80, function () {
    log.info('handle ACME http-01 challenge and redirect to https');
});

You'll notice that I'm following the instructions on the readme as close as possible, yet the thing does work.
I should mention that I'm using MacOS for development. Are there any prerequisites for this code to work, outside of the code itself?
Thanks for your help before hand!

The message you're seeing is a harmless warning which will disappear in a future release. There should be no particular issues or special requirements for running it on Mac OS X. Have you tried visiting the domain being served, etc.? What error do you see in your browser or on the console when you do? To be able to satisfy the challenge issued by the ACME server, of course the machine must be public facing and have the relevant DNS records for the domain pointed to it.

Hey @insightfuls! Thanks for the very prompt response. I guess if that's the case, then the real error is this:
var server = https.createServer(le.httpsOptions, le.middleware(app.callback()));

TypeError: le.middleware is not a function
    at Object.<anonymous> (/somepath/server.js:127:53)
    at Module._compile (module.js:541:32)
    at Object.Module._extensions..js (module.js:550:10)
    at Module.load (module.js:456:32)
    at tryModuleLoad (module.js:415:12)
    at Function.Module._load (module.js:407:3)
    at Function.Module.runMain (module.js:575:10)
    at startup (node.js:159:18)
    at node.js:444:3

That is happening at the same time, but I though the latter was a consequence of the first one [which now I know is not an error], which takes place first.
What can be happening here, then?

Uhmmm, I got it! Error on my side when creating the object. As you can see in the code above, I didn't assign the result of le.create(), and later on I use le, instead of the result of calling create() as I should have.
It's running now.


Double click to show/hide desktop icons

Guys first of all THANK YOU for such an amazing software!!!
Been using it for the last couple months and it completely changed my workflow.
Something I've really wanted for a long long (LONG) time was to be able to double click on any empty space on my desktop to instantly show/hide my desktop icons, mainly for cleanliness, but it's also because of pixel burn in! I always use clean wallpapers (dark grey, black, etc) and pixel burn in is a real issue with icons...
Let me know if this is doable, thanks and looking forwar to seeing it implemented in the next update!!
Much love <3

Tracked with #977

Tracked with #977

Guys first of all THANK YOU for such an amazing software!!!
Been using it for the last couple months and it completely changed my workflow.
Something I've really wanted for a long long (LONG) time was to be able to double click on any empty space on my desktop to instantly show/hide my desktop icons, mainly for cleanliness, but it's also because of pixel burn in! I always use clean wallpapers (dark grey, black, etc) and pixel burn in is a real issue with icons...
Let me know if this is doable, thanks and looking forwar to seeing it implemented in the next update!!
Much love <3

You should use: Stardock Fences <IP_ADDRESS> + Repack + hide desktop icons _by_xetrin
after install app on ur pc, u can show / hide icons Via Double click on your desktop
link : https://rsload.net/download?a%3AaHR0cHM6Ly9mMi4xcnNsb2FkLnJ1L2xvYWQxLzA3MC9TdGFyZG9ja19GZW5jZXNfdjUuMC4wLjFfUmVQYWNrX2J5X3hldHJpbi5yYXI%3D