Upload all training content to YouTube

Upload content from "Getting Started with CockroachDB" to YouTube.

Work with Dan to develop a format for the content description.
Upload all video content and apply a unique description for each adapted from their description in LearnDot.
Upload script file for each video.

Touched base with Dan and he is interested in assisting this project. We need to re-write all of the content descriptions to take advantage of the YouTube algorithm. This will be work intense, but it should worth it if we can catch the interest of the algorithm.
Working document for this effort can be found here: https://docs.google.com/document/d/1VqFgWRsIA_N04Uu5BbZskfxaOeIzrlFKZNfCLI1La7I/edit?usp=sharing

I sent content to Dan Kelly for review.

Dan reviewed the content and suggested minor changes.
I will now:
• upload them and add the descriptions.
• Add them all to the Cockroach University Playlist
• Let Dan know when they're all in there.
Then Dan will:
• Add tags
• Add Cards
• Add End Screens
• Publish
• Schedule Social Media

This is awesome, @SpicyThrow! Have you chatted with Dan about how to socialize these videos? We should create a docs issue to cross-reference these videos where relevant. Are you in favor of that?

@jseldess Yes, I just spoke with Dan and he is formulating some social media posts.
As discussed, yes would be good to cross-reference, but would need to identify appropriate docs and implementation strategy.

All content is now uploaded. Dan has been notified and will implement the items listed above sometime next week. Content is tentatively scheduled for release on Feb 28.

Content is now live.


Adding an undo mechanism to deleted items

Current behavior
When deleting a section there is no confirmation prompt so it would be nice to be able to undo it
Expected behavior
Have the ability to undo section deletions

Duplicate of #50 :)


AttributeError: 'BotProcess' object has no attribute '_agent_process'

Just installed luxai_s2 following instruction and try to run:
luxai-s2 Lux-Design-S2/kits/python/main.py Lux-Design-S2/kits/python/main.py -v 2 -o replay.json
got this error:
Python/3.9/lib/python/site-packages/luxai_runner/process.py", line 106, in write
self._agent_process.stdin.write(msg.encode())
AttributeError: 'BotProcess' object has no attribute '_agent_process'

This is because I only have python3 but not python2.
Resolved by running:
sudo ln -s /Library/Developer/CommandLineTools/usr/bin/python3 /Library/Developer/CommandLineTools/usr/bin/python


[bug] Connecting a wallet in React example fails on iOS

Is there an existing issue for this?

[X] I have searched the existing issues

RainbowKit Version
0.1.0
wagmi Version
0.3.5
Current Behavior
When I use the react example from the official repo, connecting to my wallet in a browser on a laptop works as expected but on iOS fails.
Clicking on the "connect" button will open the corresponding wallet app but will not prompt for a pairing request once the app is open. When testing with Metamask it just fails silently. When testing with Rainbow Wallet a text box pops up stating "Error initializing with WalletConnect."
Curiously, both of the next.js examples found in the official repo work as expected (on both laptop browser and mobile thick clients).
Expected Behavior
I expect the "connect" button to successfully open a wallet and initiate the pairing sequence on Android and iOS.
Steps To Reproduce

Clone the official examples repo at https://github.com/rainbow-me/rainbowkit-examples
Change directory to the with-create-react-app subdirectory
Install dependencies (npm install)
Run the server (npm start)
On a mobile phone, point your browser to the server spun up in the previous step
Click on the "connect" button
7a. Choose Metamask and observe that the Metamask app is opened but no prompt to pair the wallet is received
7b. Choose Rainbow Wallet and observe the error stating that there was a Wallet Connect misconfiguration

Link to Minimal Reproducible Example (CodeSandbox, StackBlitz, etc.)
No response
Anything else?
No response

@cgrayson-ch I'm going to close this now. Feel free to re-open and/or reach out if you're still having issues!


Doesn't work in IE

It says in the browser support section of the readme that this works in IE10+, however this is not the case. No version of IE supports native promises, and there is no substitute or polyfill for Promise, nor is it mentioned in any caveat that this needs to be polyfilled in order to work in IE.
So the question is -- am I missing something? Want me to PR in a readme caveat that Promise needs to be polyfilled in order for it to work in browsers that don't support it?

If you look at the installation section, it's explicitly mentioned you'll need to implement a promises polyfill for browsers that don't support it:

You will also need a Promise polyfill for older browsers.

Maybe it would make sense to add a note about this to the browser support section as well?


[FEATURE] Implement SKU File API

SKU File - Here you can consult, create, or update an SKU File. An SKU File is an image associated with an SKU.

After further investigation, it has been determined that the requested integration endpoint is no longer available and has been replaced by a new one. As a result, this issue is now invalid. We will address the new endpoint in a different issue in the future as per demand (if you need it, please, open an issue so we can prioritize it).
Therefore, I'm going to close this issue now. Please feel free to reach out if you have any further questions or need assistance with anything else.


Unsuccessful export of a CityGML dataset with many generic attributes.

I have a transport dataset converted from OpenDrive to CityGML 3.0, which is successfully imported into the 3DCityDB v5 using the citydb_tool. However, exporting the same data to a CityGML file takes too long while throwing no errors. For instance, in the dataset and setup described below, a successful import of all the features took 28 seconds, while I had to cancel the export after waiting for 6 hours.
The import/export works perfectly with another smaller transportation dataset (13MB, 805 features, 2,004 properties, and 8-10 attributes per feature).
Tools Setup
citydb_tool 0.6.1-beta
3DCityDB - v5-devel
Data Characteristics
Import  file size:	≈ 155MB
Import time:		≈ 28 seconds
Row counts
feature:        27,844
property:       430,915
geometry_data:  27,569
The number of generic attributes per feature varies, with many features having more than 40 attributes.
I will privately provide the dataset for testing.

Hey @joemureithi,
please add some details about your setup. Did you use the Docker images for both the database and citydb-tool or native installations? What PostgreSQL/PostGIS versions do you use?

Hi, let's move the issue to the citydb-tool. There is a better place, because the issue is caused by the java tool.


0.3 laravel

Updates the Laravel bridge to allow all the BREF work to be accomplished via Artisan. The goal is make the Laravel bridge work as simply and natively as possible for Laravel Developers that desire to leverage Lambda.
Given a new Laravel project, the following should handle everything required to publish the porject to Lambda.
composer require mnapoli/bref
artisan vendor:publish --tag bref-sam-template
echo 'BREF_NAME="<my-lambdas-name>"' >> .env
echo 'BREF_S3_BUCKET="<bucket-name>"' >> .env
artisan bref:config-sam
artisan bref:package
artisan bref:deploy

artisan bref:start-api is useful for testing locally in docker.
artisan bref:update is useful for simply pushing code changes to Lambda without dealing with Cloudformation via the artisan bref:deploy command.
I have also included the Documentation Update for Laravel.

Oh, this looks nice. We can probably also incorporate something similar for Symfony with the maker bundle. It'd be nice to make them both have the same behaviour :)

Yes. Artisan is built on the Symfony console package. Once I get the Laravel bridge sorted and merged, I can begin looking at refactoring the Symfony bridge to share the logic.

Hi, nice work! Given the size of this PR I'll try to properly review and write up my comments during the week.

@mnapoli would you prefer to make a branch and have me delete this and provide another pull request against said branch?

I've tried to note all the changes in this pull request to identify what to do with each:

Lumen support

That is interesting and ideally we should aim to support Lumen. Given the size of the PR I don't know if it is easy to do separately from that and what it actually implies.

Artisan commands that wrap SAM commands

I don't think we should add Laravel-specific commands for something that is global to Bref. Now the question is: should we wrap SAM into Bref commands. After Bref 0.2 I'm not convinced we should anymore, at least not if we have strong reasons. This is still an interesting discussions, and I have several ideas which could constitute good reasons for doing this.
In any case in this PR are there strong reasons to wrap SAM commands?
For the record I can detail why I think we should try to avoid this, but there are many things to review here (and it's late) so I won't go into those details now.

Laravel service provider to pre-configure Laravel

I love that idea!

Making sure the /tmp directories exist (via the service provider)

Love that!

Forcing the view.compiled config value to a sane value (via the service provider)

Love that as well, that will solve a very painful issue. I think this is acceptable to force that config because it's a low-level/internal config value.

Force session configuration to a sane value (via the service provider)

While I see the reason, I'm not a huge fan of silently overwriting the user's configuration. Maybe it would make more sense to turn that into validation: if the session is configured to go to disk, throw an exception. That will get their attention.
Yes that means that users have to spend some time configuring Laravel for Lambda, but ideally we are talking about 2-3 env variables. That's good, we should not hide too much, as long as it's simple to do and maintain. It's good that users understand why sessions (and logs) should not be written to disk. If they don't spend 30 seconds understanding that difference about Lambda they will have a lot of surprises along the way.

Pre-configuration of logs (via the service provider)

Same as with the session, ideally it should be a matter of simply setting one environment variable and that's it.
We could add that to the validation phase as well. And we could keep your idea of the LEAVE_MY_LOGS_ALONE  variable and turn it into something more generic, e.g. set BREF_LARAVEL_VALIDATION=0 and the validation will be bypassed.

Publishing the template.yaml via a Laravel command

This is a lot of added complexity, both to how Bref works and to using Bref. Now we have another piece of orchestration on top of SAM. Ideally I'd want to avoid that. (an alternative would be to wrap and hide sam entirely but this is a big job and that means isolating Bref from SAM's new features, community, documentation, etc.)
An alternative to this could be to start using parameters and variables in template.yaml. This is something I've been exploring in January, there are interesting things to do. We cannot however add complex behavior.
In any case given the size of the change I'm not sure I understood all the advantages the approach in this PR brings. Could you explain what we gain? That way we can see if there are other solutions to consider.

Ability to update the function code without going through SAM/CloudFormation

I'm not sure I understand the reasons for this, could you detail them?

Setting environment variables in template.yaml

From what I've seen this isn't necessary as the .env file is loaded with those variables. Do you see a reason to have this?

Excluding files from deployment

This is interesting but this isn't specific to Laravel, and this is not needed when using Bref with a "proper" CI/CD pipeline. Unless I'm mistaken this is useful when deploying from a local dev installation.
Wrapping SAM to control the archive process is a bit of work and yet another piece of complexity I'd try to avoid. Maybe we could take the problem differently and look at how other deployment systems/hosting platform work. That's what I did when I decided to remove bref deploy's wrapper in v0.3. It's now up to the user to use CI/CD, like most other solutions. I'd like however to help make that easier (e.g. with CodePipeline/CodeDeploy or with an interactive tutorial when deploying for the first time).

Did I miss other features added here? If so could you list them so that we can discuss them?

Perhaps, before we go through all of the details, it is more apt to determine if bref wants to provide this degree of support for framework bridges. It will necessarily add a lot more complexity, and if we desire bref to stick to simply providing the runtime, perhaps it makes more sense for us to have a separate package that handles this degree of integration?
Not only do separate packages reduce complexity for bref, it can also spread out support. If @nealio82 and I are interested in pursuing a Symfony/Laravel specific bridge, we go off and do that ... along with having to bear the consequences of support ourselves. :-)
However, if we do want to include this degree of framework bridging in bref itself, I will go through the points and address them from my perspective.

I think Laravel / Symfony bridge projects would be a good way of removing some implementation-specific concerns from the code (plus a lot of dependencies!). @mnapoli would then be free to concentrate on the core project while other contributors can donate code based upon their own use-cases (Lumen, Laravel, Symfony, Zend, etc) without muddying the water for every other possible user.
If we set up a Github org, in my mind we could have bref-php/bref, bref-php/laravel-bridge, bref-php/symfony-bridge, etc. Of course we'd need organisation & communication between everything so we know that the command syntax in the Laravel bridge is consistent with the command syntax in Symfony, for example, but we'd still need that in a mono-repo anyway.

I like this idea. Breaking the bits out into specialized repos/smaller projects should help move the entire project forward. However, there is also a concern around dedication to the project and how long people who are excited about it today will stick around to continue supporting/growing it.
Let's take that conversation to Slack, where we can be a bit more dynamic?

I'm doing a bit of cleaning in the issue tracker, closing this as it's stale and there are ideas to implement in smaller bits. There is also https://github.com/stechstudio/laravel-bref-bridge for those interested in the approach here.


IndexError when opening 1 Protein file

Describe the bug
Hi, I wanted to briefly check something on our Bruker IRT testfile. I had analyzed it with MaxQuant <IP_ADDRESS> (output files attached). When opening it and clicking on the protein, I get an IndexError. Maybe this is becuase there is only one Protein in the sample?
On another note: This was the Windows Release 1.0.7, however I got the notification that I could download the newer 1.0.5 on GitHub.
txt.zip

On the other note: This is because the release was triggered from the dev branch, which is ahead of the main branch that serves as a reference for the "latest" release


chore: Add Redis password option to helm chart

SUMMARY
Adds the ability to set Redis password and DB values in the Helm chart.
TEST PLAN
Config values tested locally. Deploy the updated Helm chart to confirm correct operation.
ADDITIONAL INFORMATION

[x] Has associated issue: Fixes #13995
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

Sorry but didnt you miss the celery config in setting the password?

Here: https://github.com/apache/superset/pull/14274/files#diff-7ec63d52f04a74d3ad45aff0ad20600bfbc42c5fa219d84d4495c696542054c4R91
Add:
password=env('REDIS_PASSWORD'),

@robdiciuccio just following up on the above to see if you saw it. If you did and are busy no worries. We might have time to fix it at some point.


call loop in swift

Hello, thank you very much, nice work!
I need save the data from Core data into Postgres database. For saveing I must call procedure in Postgres example: select savedata(id as string, name as string) What is best way call loop for this solution? The data are in [NSDictionary], code in Swift 5
best regards

Here's an example of calling a Postgres stored procedure.
import PostgresClientKit

/*

 Required setup:

 CREATE TABLE person (
 id TEXT PRIMARY KEY,
 name TEXT NOT NULL
 );

 CREATE PROCEDURE save_data_procedure(id TEXT, name TEXT)
 LANGUAGE SQL
 AS $$
 INSERT INTO person (id, name) VALUES (id, name);
 $$;

 */

do {
    var configuration = PostgresClientKit.ConnectionConfiguration()
    configuration.host = "<IP_ADDRESS>"
    configuration.ssl = true
    configuration.database = "example"
    configuration.user = "bob"
    configuration.credential = .md5Password(password: "welcome1")

    let connection = try PostgresClientKit.Connection(configuration: configuration)
    defer { connection.close() }

    let persons = [
        [ "id": "a1", "name": "Adam"],
        [ "id": "a2", "name": "Alison"],
        [ "id": "b1", "name": "Bob"]
    ]

    let text = "CALL save_data_procedure($1, $2);"
    let statement = try connection.prepareStatement(text: text)
    defer { statement.close() }

    for person in persons {
        try statement.execute(parameterValues: [ person["id"], person["name"] ])
    }
} catch {
    print(error) // better error handling goes here
}

// EOF

Does this answer your question?

Nice! Thank you so much.


Chrome ignores autocomplete="off"

Newer versions of Chrome completely ignore autocomplete="off". So if you have something like a ComboBox of States and you want to allow a user to filter the options via input, Chrome might recognize the input as part of an Address and try to autofill the State.
A possible solution is to set autocomplete="some_invalid_value" which causes Chrome to not prompt for an autofill value.
The problem with that is, Firefox will default to using autocomplete="on" on invalid values.
Per https://developer.mozilla.org/en-US/docs/Web/Security/Securing_your_site/Turning_off_form_autocompletion:

In some cases, the browser will continue suggesting autocompletion values even if the autocomplete  attribute is set to off. This unexpected behavior can be quite puzzling for developers. The trick to   really enforcing non-autocompletion is to assign an invalid value to the attribute, for example:
autocomplete="nope"
Since this value is not a valid one for the autocomplete attribute, the browser has no way to match it,  and stops trying to autocomplete the field. Please note that this does not work in Firefox; it completely disregards the invalid value and reverts to default autocompletion behavior.

In my mind, the only solution is to do a quick browser check before setting any hard values for autocomplete like https://github.com/salesforce/design-system-react/blob/master/components/combobox/combobox.jsx#L809.
Thanks

@interactivellama Should we expose autocomplete prop on SLDSInput? I can see it's exposed on the private component inner-input but not on SLDSInput.

Yea that would be great. Unless you guys think it's better to do browser
detection and set to some random string for chrome only. Your call. Either
is good for me.
On Fri, Feb 15, 2019 at 7:55 PM David<EMAIL_ADDRESS>wrote:

@interactivellama https://github.com/interactivellama Should we expose
autocomplete prop on SLDSInput? I can see it's exposed on the private
component inner-input but not on SLDSInput.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/salesforce/design-system-react/issues/1654#issuecomment-464265387,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AD3P9u-3ovNZeKzNc61AuBoExVFYVviWks5vN1cRgaJpZM4YtjJ7
.

--
Alex Boyce

Yes @davidlygagnon that's great idea! Let's add autocomplete to Input.
As part of that, can you pull the Input prop out of https://github.com/salesforce/design-system-react/pull/1430 so that <Combobox input={<Input autocomplete=""} /> can handle this for the Combobox via props spread composition.

The developer's passed in component controlled by the "grandparent" takes precedence and merges in last.

Oh great, you read my mind actually. I will also pull out the functionality to disable readonly combobox out of this PR because we need it. Sounds good?

Yes, please proceed.


strings can't be accessed after dump()->parse() - type is lost

Hi,
strangely, this code doesn't work and I can't find out what I'm doing wrong....
nlohmann::json out;
out[accessTokenField] = (const string&)accessToken;   // key and value std::strings
std::string tmp1 = out[accessTokenField]; // this works
std::string dump = out.dump(); // 'dump' is - {"accessToken": "b9c6f71f-0a10-4025-9628"}
nlohmann::json in;
in.parse(dump);
std::string tmp2 = in[accessTokenField]; // this fails!! error message- "type must be string, but is null"
update: using the static json::parse method works fine-
.
.
nlohmann::json in;
in = nlohmann::json::parse(dump);
std::string tmp2 = in[accessTokenField];

The parse function is static and returns the parsed JSON value. Instead of
in.parse(dump);

which does not alter in and leaves it as null, the code should read
in = nlohmann::json::parse(dump);


Multiple endpoints and PIDStore integration

Looks good to me. In the end I don't think that renaming restful files as views is an issue. Modules will most probably separate in directories the UI and the REST api anyway. Something like:

package

views.py (UI)
v1

ext.py
serializer.py
views.py (API)

v2

ext.py
....


Tweaked Deploy name in the pipeline + proper formatting for readability

I have added an - between Deploy and the name of the service instance.
Also I have formatted the text for better readability (the Jinja entry just above the tweak was misplaced and hard to resonate about when looking at the code)
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@mreferre - do we still want to implement this change or can we close this PR?

@adamjkeller I completely forgot about this PR (and I have not seen the discussion in the review). I honestly thought it was already merged. These are two minor fixes for readability. They are not critical for sure but I would merge them (unless someone has different opinions)


How using it offline ?

I am a noob and i can't use it offline. I have follow all the processus but it not working. Can some one explaint me how to do please ?
I downloaded whisper yesterday, but I needed the dictation feature. So I downloaded whispering desktop today. I open the software in the settings there are only 3 options:

OpenAl
Groq
faster-whisper-server

Since I managed to make whisper use the gpu, I copy and paste this code for gpu into the docker terminal:
docker run -e ALLOW_ORIGINS='["https://whispering.bradenwong.com"]' --gpus=all --publish 8000:8000 --volume ~/.cache/huggingface:/root/.cache/huggingface fedirz/faster-whisper-server:latest-cuda

Here is what is displayed.
 All rights reserved.

This container image and its contents are governed by the NVIDIA Deep Learning Container License.
By pulling and using the container, you accept the terms and conditions of this license:
https://developer.nvidia.com/ngc/nvidia-deep-learning-container-license

A copy of this license is made available in this container at /NGC-DL-CONTAINER-LICENSE for your convenience.

Traceback (most recent call last):
  File "/root/faster-whisper-server/.venv/bin/uvicorn", line 8, in <module>
    sys.exit(main())
             ^^^^^^
  File "/root/faster-whisper-server/.venv/lib/python3.12/site-packages/click/core.py", line 1157, in __call__
    return self.main(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/root/faster-whisper-server/.venv/lib/python3.12/site-packages/click/core.py", line 1078, in main
    rv = self.invoke(ctx)
         ^^^^^^^^^^^^^^^^
  File "/root/faster-whisper-server/.venv/lib/python3.12/site-packages/click/core.py", line 1434, in invoke
    return ctx.invoke(self.callback, **ctx.params)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/root/faster-whisper-server/.venv/lib/python3.12/site-packages/click/core.py", line 783, in invoke
    return __callback(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/root/faster-whisper-server/.venv/lib/python3.12/site-packages/uvicorn/main.py", line 410, in main
    run(
  File "/root/faster-whisper-server/.venv/lib/python3.12/site-packages/uvicorn/main.py", line 577, in run
    server.run()
  File "/root/faster-whisper-server/.venv/lib/python3.12/site-packages/uvicorn/server.py", line 65, in run
    return asyncio.run(self.serve(sockets=sockets))
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/asyncio/runners.py", line 194, in run
    return runner.run(main)
           ^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/asyncio/runners.py", line 118, in run
    return self._loop.run_until_complete(task)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/asyncio/base_events.py", line 687, in run_until_complete
    return future.result()
           ^^^^^^^^^^^^^^^
  File "/root/faster-whisper-server/.venv/lib/python3.12/site-packages/uvicorn/server.py", line 69, in serve
    await self._serve(sockets)
  File "/root/faster-whisper-server/.venv/lib/python3.12/site-packages/uvicorn/server.py", line 76, in _serve
    config.load()
  File "/root/faster-whisper-server/.venv/lib/python3.12/site-packages/uvicorn/config.py", line 434, in load
    self.loaded_app = import_from_string(self.app)
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/root/faster-whisper-server/.venv/lib/python3.12/site-packages/uvicorn/importer.py", line 19, in import_from_string
    module = importlib.import_module(module_str)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/importlib/__init__.py", line 90, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen importlib._bootstrap>", line 1387, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1360, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1331, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 935, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 995, in exec_module
  File "<frozen importlib._bootstrap>", line 488, in _call_with_frames_removed
  File "/root/faster-whisper-server/faster_whisper_server/main.py", line 31, in <module>
    from faster_whisper_server import hf_utils
  File "/root/faster-whisper-server/faster_whisper_server/hf_utils.py", line 7, in <module>
    from faster_whisper_server.logger import logger
  File "/root/faster-whisper-server/faster_whisper_server/logger.py", line 3, in <module>
    from faster_whisper_server.config import config
  File "/root/faster-whisper-server/faster_whisper_server/config.py", line 243, in <module>
    config = Config()
             ^^^^^^^^
  File "/root/faster-whisper-server/.venv/lib/python3.12/site-packages/pydantic_settings/main.py", line 144, in __init__
    super().__init__(
  File "/root/faster-whisper-server/.venv/lib/python3.12/site-packages/pydantic/main.py", line 211, in __init__
    validated_self = self.__pydantic_validator__.validate_python(data, self_instance=self)
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
pydantic_core._pydantic_core.ValidationError: 1 validation error for Config
allow_origins
  Input should be a valid list [type=list_type, input_value='[https://whispering.bradenwong.com]', input_type=str]
    For further information visit https://errors.pydantic.dev/2.9/v/list_type

It is complete gibberish to me. But I realize that it downloads whisper again. I would have liked to use the one already downloaded. Is it possible to use the whisper that I downloaded yesterday so as not to have it twice? What is the procedure to link whispering to whisper?
And so whispering doesn't work.
There are also these options there that I don't understand. What is it for?
faster-whisper-server URL
http://localhost:8000
faster-whisper-server Model
Systran/faster-whisper-medium.en
How to make whispering work offline?

Yeah, also having the same issue.

Try running:
docker run -e ALLOW_ORIGINS="[\"https://whispering.bradenwong.com\"]" --gpus=all --publish 8000:8000 --volume ~/.cache/huggingface:/root/.cache/huggingface fedirz/faster-whisper-server:latest-cuda
This created the docker container fine for me. It runs fine, is accessible at http://localhost:8000/ and it the transcription does work.
However, I can't get the Whispering desktop or web app to work with the faster-whisper-server that's running in the docker container.
Getting the error: An error occurred while sending the request to the transcription server. Please try again.


CB-4705 remove CRN from ThreadBasedUserCrnProvider in MDCCleanerThrea…

ThreadBasedUserCrnProvider is now not a bean anymore. In this case unit testing/mocking is harder. CCan we use a singleton bean please?

Bean is not necessary. It is a static class, so I can set user CRN in a normal way without mocking like this: ThreadBasedUserCrnProvider.setUserCrn(USER_CRN);


settings: reduce default number of threads

See #1885

Codecov Report

Merging #1888 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff           @@
##           master   #1888   +/-   ##
======================================
  Coverage    66.3%   66.3%
======================================
  Files          56      56
  Lines        6603    6603
  Branches     1318    1318
======================================
  Hits         4378    4378
  Misses       2002    2002
  Partials      223     223

Impacted Files
Coverage Δ

webapp/graphite/settings.py
75.15% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

POOL_WORKERS_PER_BACKEND = 1
But does reducing POOL_WORKERS to 1 making all pool thing useless?

I think that's fine, you end up with between 2 and N threads (with N-1 being the number of backends). That's usually way enough since you're not going to process requests in parallel most of the time.
Remember that the total number of threads is POOL_WORKERS_PER_BACKEND * len(CLUSTER_SERVERS) + POOL_WORKERS.

Remember that the total number of threads is POOL_WORKERS_PER_BACKEND * len(CLUSTER_SERVERS) + POOL_WORKERS.

Cool! Maybe it's worth to mention that somewhere in https://github.com/graphite-project/graphite-web/blob/master/webapp/graphite/local_settings.py.example#L248-L262 ?

Updated :)

Cool! 👍


'Create another?' link not present on limited sections

I've noticed that sections with a limit don't have the Create another? link in the header when an entry is created, even if the count is below the limit.
My assumption is that this is a limitation, that maybe the extension doesn't know the count when the entry is saved and so doesn't offer this link just in case, which is probably the best way to handle it - but thought I'd report it just in case it's a bug.

Fixed! Thanks!


Fixes initialisation process on the web frontend

Fix #165

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 63.81%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
3172

Relevant Lines:
4971

💛  - Coveralls

The setup process is quite shiny now:
https://user-images.githubusercontent.com/1918021/190392631-4a7a4523-6753-4a7d-a9cb-17f9220b1ce3.mov

I'm too far from this code base to be of much help, but I had a quick look and it seems a lot of state is just passed around between components. As per our (offline) discussion @nkcr, I'm pretty sure introducing something like Redux or Akita could provide significant benefits.
I say this because then it would allow big chunks of the logic to be moved into dedicated services, dealing only with the network and the state, whereas the components would focus on showing what's in the state and triggering the services. If the state is external, it can just be queried as needed.

Instead of pulling out the big boys, an interesting incremental step could be to use the native React context API to wrap all those properties.

Woohoo it works ! 🎉

Yay 🥳
Thank you very much for the review, I owe you one 🍺

Hahaha no problem (we were kind of fixing the mess I left anyway 😂) !


Reduce binary size with upx

Hey, did you try compressing the binary with https://github.com/upx/upx ? It may shrink size twice or more

Hi @vladgolubev. Yes I did. Unfortunately it increases the startup time by 1000-1500 ms on AWS Lambda which I felt was not a good trade-off. However, new stable builds are striped which helps reduce the binary size by around 45MB.

Thanks for the info ! Good to know !


feature/user-profile

Create user profile page that will display their user data that they used when registering.
Allow user to update info.

For the update user page I think allowing users to edit everything execpt for the password, since the password can already be edited using #6. Was thinking of using the same layout of register user since I think that's the best layout for this type of page.

Navbar must also be edited to add the edit user profile page

Need to update nav bar to add edit profile for users who are logged in. Currently im going to the edit page using the url which logs me out when i go to the url page, so an update to the nav bar or route guard will stop this from happening.

Only new item for the nav bar should be "Profile" button. The update user page should be a button on the profile page that takes them to that. There should also be another button to take the user to the reset password page.


Convert unittest to pytest

Fixes

Fixes #3425  by @AetherUnbound
Description

On catalog/tests/dags/common/sensors/test_single_run_external_dags_sensor.py, setUp function is renamed to setup_pool, set_pool will have a parameter sample_pool_fixture retrieved from conftest.TestExternalDAGsSensor class will be removed and all test function will be in the same module.
On ingestion_server/test/integration_test.py, setUpClass is rename to setup_fixture, setup_fixture use scope as module, autouse is set as True  and it will return a dictionary for other function to retrieve them. Install pytest-subtests to replace unittest subTest.
Testing Instructions

For catalog:
run just catalog/up
run just catalog/test
For ingestion server:
run just ingestion_server/test_local
if ingestion server fail:
run just ingestion_server/test-clean-dc
run just ingestion_server/test_local
Checklist

[x] My pull request has a descriptive title (not a vague title likeUpdate index.md).
[x] My pull request targets the default branch of the repository (main) or a parent feature branch.
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[N/A] I added or updated tests for the changes I made (if applicable).
[N/A] I added or updated documentation (if applicable).
[x] I tried running the project locally and verified that there are no visible errors.
[N/A] I ran the DAG documentation generator (if applicable).

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

@krysal @obulat are either of y'all able to review this PR this week? It'd be great to merge this.


Generate pypi website scraper dataset

Scrape pypi for all the info needed in the research phase that can not be gotten from pypi json api
the dataset output format and location should be documented
This should be a new command like python -m score.cli pypi-web

Fields unique to the PyPi Webscraper:

summary
author
license
requires
dev_status
first_release
last_release
releases
monthly_downloads_pypi

All fields gathered by the PyPi Webscraper:
All the fields are type string except for releases

name:
version:
summary:
author:
license:
maintainer:
maintainer_email:
requires:
dev_status:
first_release:
last_release:
releases:
monthly_downloads_pypi:
monthly_downloads_conda:

To run the scraper you can run:
python cli.py scrape-pypi-web --letter 0-9
Where scrape-pypi-web is a call to the web scraper and --letter (optional) specifies the range of letters that you would like to scrape
The output destination would be as follows:
./score/output/web/letter={letter}/pypi_packages.parquet


Are there any information  about the dataset and model architecture?

Hi sir:
I want to try to build for my own voice commands with coral board.
Are there any papers or information about the keyword dataset and the model architecture?
Thanks

It's a simple convolutional model. Hopefully more info on this with the next release.


o1VM: make the preimage oracle abstract

For test environment, we can implement a fake preimage oracle that will read/write values on disk/memory.
This PR implements the fake on-disk preimage oracle.
It consists of reading files from the directory o1vm/resources/test/, formatted as 0xPREIMAGE_KEY.txt, as given by the op-program. The content is the preimage data.
The interpreter uses the preimage oracle through request_preimage_write which calls the preimage_oracle.get_preimage (on-disk for the test).
Testing the syscall write can consist now in writing correctly the preimage key in the correct registers (+ preimage key offset, etc), call the interpreter on the syscall, and check if the memory has been set correctly.

Note that I would be careful to not push too many files to avoid growing the git repository space.


The solution of deeptree_damo can't download

I opened the link https://med-rt.oss-cn-zhangjiakou.aliyuncs.com/PuyangWang/deeptree_damo.zip?OSSAccessKeyId=LTAI5tKEhSFnzxThPXrSHGtN&Expires=2001983114&Signature=TilFECJyX8vzfAB%2FJAagG%2F1UMck%3D, and got the
This XML file does not appear to have any style information associated with it. The document tree is shown below.
<Error>
NoSuchKey
<Message>The specified key does not exist.</Message>
<RequestId>66286CA9C7728130326B6254</RequestId>
<HostId>med-rt.oss-cn-zhangjiakou.aliyuncs.com</HostId>
<Key>PuyangWang/deeptree_damo.zip</Key>
<EC>0026-00000001</EC>
<RecommendDoc>https://api.aliyun.com/troubleshoot?q=0026-00000001</RecommendDoc>
</Error>

I opened the link https://med-rt.oss-cn-zhangjiakou.aliyuncs.com/PuyangWang/deeptree_damo.zip?OSSAccessKeyId=LTAI5tKEhSFnzxThPXrSHGtN&Expires=2001983114&Signature=TilFECJyX8vzfAB%2FJAagG%2F1UMck%3D, and got the
This XML file does not appear to have any style information associated with it. The document tree is shown below.
<Error>
NoSuchKey
<Message>The specified key does not exist.</Message>
<RequestId>66286CA9C7728130326B6254</RequestId>
<HostId>med-rt.oss-cn-zhangjiakou.aliyuncs.com</HostId>
<Key>PuyangWang/deeptree_damo.zip</Key>
<EC>0026-00000001</EC>
<RecommendDoc>https://api.aliyun.com/troubleshoot?q=0026-00000001</RecommendDoc>
</Error>

Thank you for the concern, we are working on this issue and will let you know if this problem is fixed.
Best,

In addition to deeptree_damo's solution, the links in team Sammed_AI's and neu204's solutions are also not working
team_Sanmed_AI:
https://pan.baidu.com/s/1DBLbP9VEZz5pWn2qR7KWwA?pwd=ekfk
team_neu204:
https://drive.google.com/file/d/14t-C-SnQsMATRcMWvVqDz8VztxV6lg0j/view?usp=sharing

In addition to deeptree_damo's solution, the links in team Sammed_AI's and neu204's solutions are also not working
team_Sanmed_AI: https://pan.baidu.com/s/1DBLbP9VEZz5pWn2qR7KWwA?pwd=ekfk
team_neu204: https://drive.google.com/file/d/14t-C-SnQsMATRcMWvVqDz8VztxV6lg0j/view?usp=sharing

Thank you for this concern, we will renew this docker files recently.
BTW, the deeptree_damo's solution will be renewed soon.
Best,

In addition to deeptree_damo's solution, the links in team Sammed_AI's and neu204's solutions are also not working
team_Sanmed_AI: https://pan.baidu.com/s/1DBLbP9VEZz5pWn2qR7KWwA?pwd=ekfk
team_neu204: https://drive.google.com/file/d/14t-C-SnQsMATRcMWvVqDz8VztxV6lg0j/view?usp=sharing

The docker of team_Sanmed_AI and team_neu_204 have been updated, please feel free to try.
Best,

Hi, thanks for share the project. I also have the issue to get access to the 'team_deeptree_damo' 's link.

Hi, thanks for share the project. I also have the issue to get access to the 'team_deeptree_damo' 's link.

Hi,
Our collaborators are working on renew the docker link. We think it will be finished soon. Thank you for your patience.
Best,

Dear all,
Thank you for your patience, we have renew the docker of the 'team_deeptree_damo'.
Please refer to: https://github.com/EndoluminalSurgicalVision-IMR/ATM-22-Related-Work/tree/main/ATM22-Challenge-Top5-Solution/team_deeptree_damo for more details.
Best,


max-pods-to-evict-per-node default to 0?  and loglevel default to 0?

Hi
I found two things that

when with no -v option, descheduler pods have no output, so loglevel default to 0?

    Command:
      /bin/descheduler
    Args:
      --policy-config-file=/policy-dir/policy.yaml
      --dry-run

And I checked help info and found no such things metioned.
  -v, --v Level                          log level for V logs

when run with non-dry-run mode with no --max-pods-to-evict-per-node option no pod will be evicted, so the flag default to 0? also no declaration in help info

# oc logs -f descheduler-cronjob-1523411400-z2z8z
I0411 01:50:37.761513       1 round_trippers.go:436] GET https://<IP_ADDRESS>:443/api 200 OK in 124 milliseconds
I0411 01:50:37.882412       1 round_trippers.go:436] GET https://<IP_ADDRESS>:443/apis 200 OK in 15 milliseconds
I0411 01:50:37.898564       1 round_trippers.go:436] GET https://<IP_ADDRESS>:443/api/v1 200 OK in 15 milliseconds
I0411 01:50:37.903192       1 reflector.go:202] Starting reflector *v1.Node (1h0m0s) from github.com/kubernetes-incubator/descheduler/pkg/descheduler/node/node.go:84
I0411 01:50:37.903215       1 reflector.go:240] Listing and watching *v1.Node from github.com/kubernetes-incubator/descheduler/pkg/descheduler/node/node.go:84
I0411 01:50:37.919025       1 round_trippers.go:436] GET https://<IP_ADDRESS>:443/api/v1/nodes?limit=500&resourceVersion=0 200 OK in 15 milliseconds
I0411 01:50:37.963552       1 round_trippers.go:436] GET https://<IP_ADDRESS>:443/api/v1/nodes?resourceVersion=8694&timeoutSeconds=481&watch=true 200 OK in 25 milliseconds
I0411 01:50:38.011943       1 duplicates.go:50] Processing node: "ip-172-18-7-158.ec2.internal"
I0411 01:50:38.028600       1 round_trippers.go:436] GET https://<IP_ADDRESS>:443/api/v1/pods?fieldSelector=spec.nodeName%3Dip-172-18-7-158.ec2.internal%2Cstatus.phase%21%3DFailed%2Cstatus.phase%21%3DSucceeded 200 OK in 16 milliseconds
I0411 01:50:38.433484       1 duplicates.go:54] "ReplicationController/hello-1"
I0411 01:50:38.433510       1 duplicates.go:50] Processing node: "ip-172-18-14-173.ec2.internal"
I0411 01:50:38.461836       1 round_trippers.go:436] GET https://<IP_ADDRESS>:443/api/v1/pods?fieldSelector=spec.nodeName%3Dip-172-18-14-173.ec2.internal%2Cstatus.phase%21%3DFailed%2Cstatus.phase%21%3DSucceeded 200 OK in 28 milliseconds
I0411 01:50:38.479347       1 duplicates.go:54] "ReplicationController/hello-1"
I0411 01:50:38.495887       1 round_trippers.go:436] GET https://<IP_ADDRESS>:443/api/v1/pods?fieldSelector=spec.nodeName%3Dip-172-18-7-158.ec2.internal%2Cstatus.phase%21%3DFailed%2Cstatus.phase%21%3DSucceeded 200 OK in 16 milliseconds
I0411 01:50:38.568027       1 round_trippers.go:436] GET https://<IP_ADDRESS>:443/api/v1/pods?fieldSelector=spec.nodeName%3Dip-172-18-14-173.ec2.internal%2Cstatus.phase%21%3DFailed%2Cstatus.phase%21%3DSucceeded 200 OK in 15 milliseconds
I0411 01:50:38.569526       1 lownodeutilization.go:141] Node "ip-172-18-7-158.ec2.internal" is under utilized with usage: api.ResourceThresholds{"cpu":30, "memory":14.27776271919991, "pods":5.6}
I0411 01:50:38.569571       1 lownodeutilization.go:149] allPods:14, nonRemovablePods:9, bePods:4, bPods:1, gPods:0
I0411 01:50:38.569603       1 lownodeutilization.go:141] Node "ip-172-18-14-173.ec2.internal" is under utilized with usage: api.ResourceThresholds{"cpu":20, "memory":11.422210175359927, "pods":4.4}
I0411 01:50:38.569616       1 lownodeutilization.go:149] allPods:11, nonRemovablePods:3, bePods:8, bPods:0, gPods:0
I0411 01:50:38.569623       1 lownodeutilization.go:65] Criteria for a node under utilization: CPU: 40, Mem: 40, Pods: 40
I0411 01:50:38.569630       1 lownodeutilization.go:72] Total number of underutilized nodes: 2
I0411 01:50:38.569635       1 lownodeutilization.go:80] all nodes are underutilized, nothing to do here
I0411 01:50:38.569644       1 pod_antiaffinity.go:45] Processing node: "ip-172-18-7-158.ec2.internal"
I0411 01:50:38.585039       1 round_trippers.go:436] GET https://<IP_ADDRESS>:443/api/v1/pods?fieldSelector=spec.nodeName%3Dip-172-18-7-158.ec2.internal%2Cstatus.phase%21%3DFailed%2Cstatus.phase%21%3DSucceeded 200 OK in 15 milliseconds
I0411 01:50:38.595997       1 pod_antiaffinity.go:45] Processing node: "ip-172-18-14-173.ec2.internal"
I0411 01:50:38.635903       1 round_trippers.go:436] GET https://<IP_ADDRESS>:443/api/v1/pods?fieldSelector=spec.nodeName%3Dip-172-18-14-173.ec2.internal%2Cstatus.phase%21%3DFailed%2Cstatus.phase%21%3DSucceeded 200 OK in 39 milliseconds
I0411 01:50:38.659140       1 node_affinity.go:31] Evicted 0 pods

I will look into it today.

@aveshagarwal  and also loglevel, since log will be empty when loglevel=0

@aveshagarwal
I have to make some explains here that:
For the loglevel part, I expect there are something come out for the default installation parameters, but nothing currently, If you prefer to user -v explicitly, then I will open an installation issue for this.
For max-pod-to-evict-per-node part, I think better not make 0 as default value, If you want no pod will be evicted, this should be covered by dry-run mode.
How do you think?

For the loglevel part, I expect there are something come out for the default installation parameters, but nothing currently, If you prefer to user -v explicitly, then I will open an installation issue for this.

What you would like to see as default installation parameters? I

For max-pod-to-evict-per-node part, I think better not make 0 as default value, If you want no pod will be evicted, this should be covered by dry-run mode.

I agree, though I would say 0 is incorrect configuration in the context of descheduler.
Also see my comment here: https://github.com/kubernetes-incubator/descheduler/pull/87#issuecomment-381160175

@aveshagarwal Anyway there should have something come out or people do not know if descheduler is working or not.
And currently have no -v option:
https://github.com/openshift/openshift-ansible/blob/master/roles/openshift_descheduler/templates/descheduler-cronjob.yaml.j2#L23

@wjiangjay can you close this if it is taken care of?

@wjiangjay ping is it ok to close this?

@aveshagarwal should be ok now.


Bundle.total.value for search resource operation is null sometimes.

GOAL: To perform search operation on the resource (Encounter eg) and in return, the bundle resource total value is expected not to be null.
ISSUE:  Bundle.total.value in Bundle gets null value occasionally.
REQUEST WE ARE SENDING:
http://localhost:8080/fhir/Encounter?plsubject=urn%3Aoid%3A2.16.840.1.113883.3.44<IP_ADDRESS>6|90090811098&date=gt2020-05-08T00%3A00%3A00&date=lt2020-05-10T23%3A59%3A59&_getpagesoffset=0&_count=5&_sort=-date&_total=accurate
DIAGNOSIS:
The result of resource search operation is total value which gets occasionally null value, although the resources are returned.
We've done some research regarding _total issue and we've applied solution found on these websites:
https://github.com/jamesagnew/hapi-fhir/issues/1265
https://www.hl7.org/fhir/search.html#total

We've tried to add _total=accurate as in the sample request presented above.
Adding the _total attribute to the request reduced the incidence of Bundle.total.value = null but did not solve
the problem completely.
EXPECTED BEHAVIOR:
For every request of performing Encounter search operation expected result of "Bundle.total.value" should be never null.
To Reproduce
Steps to reproduce the behavior:

Save some unique encounter resources (5 eg).
Save searchParameter plsubject like below.
Prepare search request which was submitted above, set the identifier and the date range of the medical event that was recorded earlier.
Perform queries until you obtain Bundle.total.value = null.
Look for Bundle.total.value which occasionally gets null.

Environment:
HAPI FHIR 4.1.0-e05ea676
OS: WIN10
Browser FIREFOX 77.0.1 (64 bit) /Postman/REST

plsubject searchParameter:
<?xml version="1.0" encoding="UTF-8"?> <SearchParameter xmlns="http://hl7.org/fhir">     <id value="PLMedicalEventSubjectSearchParameter"/>     <text><status value="generated"/>
Search by encounter subject
</text>     <url value="https://ADDRESS/fhir/SearchParameter/encounter-plsubject"/>     <name value="PLMedicalEvent by subject Search Parameter"/>     <status value="active"/>     <experimental value="true"/>     <date value="2019-08-01"/>     <description value="Search by encounter subject"/>     <purpose value="Need to search PLMedicalEvent by subject"/>          <base value="Encounter"/>     <type value="token"/>     <expression value="Encounter.extension('https://ADDRESS/fhir/StructureDefinition/PLSubjectDepersonalizationId')"/>     <xpathUsage value="normal"/>     <modifier value="identifier"/> </SearchParameter>
Debugger window dump (total == null but entry == 5):

Hi,
Any update on this issue?
This is easily verified in the test server.
The request https://r4.smarthealthit.org/Patient?_format=json should return a total value but this is not present in the response.
Thanks

This is by design. Calculating the total adds complexity/time to the search when the search returns a lot of results so it's not done by default.
You can force the calculation using the _total parameter if you are ok with that tradeoff: https://r4.smarthealthit.org/Patient?_total=accurate

Sorry, it was brought to my attention that I didn't read this closely enough and you were already doing that. Thanks @tadgh


dt-parsing seems to try to interpret value (breaking it in some cases)

Regression from last release to master
Example site: https://aaronparecki.com/, which has
<div class="h-card">
<time class="dt-bday" datetime="--12-28"></time>
</div>

output:
{
   "type": ["h-entry"],
   "properties": {
                "bday": ["--12-2800"],
            }
 }

expected output: "bday": ["--12-28"]
This looks like php-mf2 tries to parse the date, instead of simply passing through the value it finds in the datetime=property.

Thanks for catching that! It's incorrectly interpreting "-28" as a TZ offset and normalizing it. I'll work on a fix.

It should not interpret anything from a non-VCP datetime. There's been suggestions to always do some dt parsing instead of only for VCP and to produce a more normalized format, but (from what I know) no clear proposed spec changes, so right now arguably anything that produces not exactly the input string is kind of a bug.


fix: 🐛 Handle asset type middleware scope conversion correctly

Description

Breaking Changes

JIRA Link

Checklist

[ ] Updated the Readme.md (if required) ?

/fast-forward

Triggered from https://github.com/PolymeshAssociation/polymesh-sdk/pull/1339#issuecomment-2426883503 by @prashantasdeveloper.
Trying to  fast forward beta (9460b22717ff2b0a599020066266e00968926ef6) to alpha (5b946f9044605edbaa355860bff846584cf9eadf).
Target branch (beta):
commit 9460b22717ff2b0a599020066266e00968926ef6 (HEAD -> beta, tag: v26.0.0-beta.1, tag: v26.0.0-alpha.5, origin/beta)
Author: Prashant Bajpai<EMAIL_ADDRESS>Date:   Thu Oct 17 13:42:35 2024 +0530

    feat: 🎸 Make `ticker` optional while creating an asset

Pull request (alpha):
commit 5b946f9044605edbaa355860bff846584cf9eadf (pull_request/alpha)
Author: Prashant Bajpai<EMAIL_ADDRESS>Date:   Mon Oct 21 16:28:49 2024 +0530

    test: 💍 update tests

Fast forwarding beta (9460b22717ff2b0a599020066266e00968926ef6) to alpha (5b946f9044605edbaa355860bff846584cf9eadf).
$ git push origin 5b946f9044605edbaa355860bff846584cf9eadf:beta
remote: error: GH006: Protected branch update failed for refs/heads/beta.
remote:
remote: - Required status check "Building and releasing project" is failing.
To https://github.com/PolymeshAssociation/polymesh-sdk.git
 ! [remote rejected]   5b946f9044605edbaa355860bff846584cf9eadf -> beta (protected branch hook declined)
error: failed to push some refs to 'https://github.com/PolymeshAssociation/polymesh-sdk.git'

/fast-forward

:tada: This PR is included in version 26.0.0-alpha.6 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 26.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Increase coverage, at 80% now

Add type hints, stricter checks in validate_jobinfo()
Add test for validate_jobinfo()
Increase API query test coverage
Add tests for output formatting

Sorry I didnt notice this was in draft mode!

The validate_jobinfo is removed in #80 so this is going to clash with your changes here.  Do you think it's worth adding similar typing in configure.get_job_info ?


mod crashes when dark-mode v4 is enabled again

Yeah mod crashes when dark mode v4 mod is enabled again!  Please fix again thanks :)

Bug caused by DarkMode V4, forwarding this to @iArtie


File format gff or bed and what format?

I am a PhD student doing a collaborative project between Trinity College Dublin and UCLondon and am using MCScanX. I am just getting to know the tool and have been trying to use the test data available in the package ( at_vv.gff, at_vv.blast etc.) and am running into a few problems.
Some of the information online says to use .gff and others say .bed, and the format of these files is also conflicting in the documentation. I was wondering if you could tell me how exactly the files needed for MCScan to run should be formatted and is it advisable to have just two (the .bed/.gff and .blast) in a single folder when running ./MCScan command.
I hope you can help me out.

I am just getting this running but I had to create a file with this information:
Chromosome Gene_name Start End
This is not actually a 'bed' file because .bed format is (my understanding at least) constrained to Chromosome; Start; End as the first 3 columns and gene names and other information can be added in columns 4+. I had
Chromosome Start End Gene_name
and rewrote it with this awk command
awk -F '\t' '{print $1,$4,$2,$3}' OFS='\t' "xyz.bed" > xyz.gff
If you check the test data the format is like this. Good luck!

I had the same problem and that definitively solved it!
Thank you so much @jannafierst!

@somnya Glad to know that you were able to make this program work. Could you please share you input file headers?

@gunjanpandey "I'll explain this issue in detail. The strange part is that the author requires a BED file, but this BED file is not standard. The standard format is chromosome name, start, end, gene name. However, what he needs is chromosome name, gene name, start, end, and this file needs to have a .gff suffix. It took me an entire day to figure this out."


1.19.2 Forge populateNeighborTable Game Crash

I don't know what is causing the crash, all I know is that it said to set populateNeighborTable to true.
I didn't find any crash-report, but I found this in the minecraft game output which might help
Caused by: java.lang.UnsupportedOperationException: A mod tried to access the state neighbor table directly. Please report this at https://github.com/malte0811/FerriteCore/issues. As a temporary workaround you can enable "populateNeighborTable" in the FerriteCore config
at TRANSFORMER/ferritecore@5.0.3/malte0811.ferritecore.fastmap.table.CrashNeighborTable.crashOnAccess(CrashNeighborTable.java:101)
at TRANSFORMER/ferritecore@5.0.3/malte0811.ferritecore.fastmap.table.CrashNeighborTable.rowKeySet(CrashNeighborTable.java:77)
at TRANSFORMER/radium@0.8.2/me.jellysquid.mods.lithium.common.state.FastImmutableTable.(FastImmutableTable.java:36)
at TRANSFORMER/minecraft@1.19.2/net.minecraft.world.level.block.state.StateHolder.handler$bgi000$postCreateWithTable(StateHolder.java:528)
at TRANSFORMER/minecraft@1.19.2/net.minecraft.world.level.block.state.StateHolder.m_61133_(StateHolder.java:1052)
at TRANSFORMER/minecraft@1.19.2/net.minecraft.world.level.block.state.StateDefinition.(StateDefinition.java:68)
at TRANSFORMER/minecraft@1.19.2/net.minecraft.world.level.block.state.StateDefinition$Builder.m_61101_(StateDefinition.java:157)
at TRANSFORMER/minecraft@1.19.2/net.minecraft.world.level.block.Block.(Block.java:176)
at TRANSFORMER/minecraft@1.19.2/net.minecraft.world.level.block.AirBlock.(AirBlock.java:12)
at TRANSFORMER/minecraft@1.19.2/net.minecraft.world.level.block.Blocks.(Blocks.java:39)

See https://github.com/malte0811/FerriteCore/issues/96#issuecomment-1278544397.


Fix bug that allowed containers to be set as a value in ValueNodes

Closes #324 .
I added tests but I think maybe I should remove the one in test_structured_config since is essentially the same as test_errors.
The variable should_set_value is getting pretty big but this fixed it.

I rebased incorrectly i'll re-commit.


Change the code owner to the new team cpp-client-team

Changed the code owner to the new team cpp-client-team.

Wrong pull request.

Windows test FAILed.

Linux test PASSed.


Added Prims [Java] Closes #116

Closes #116

By submitting this pull request I confirm I've read and complied with the below requirements.

[x] I have read the Contribution guidelines and I am confident that my PR reflects them.
[x] I have followed the coding guidelines for this project.
[x] My code follows the skeleton code structure.
[x] This pull request has a descriptive title. For example, Added {Algorithm/DS name} [{Language}], not Update README.md or Added new code.

@aviaryan @singhpratyush There was a issue raised by codacy bot about class or interface doesn't have a package description. I have just removed the import statements and issue is resolved. How is this so?

@yashLadha Codacy's check is still pending.

Sir i had rebase all the commits. It will pass

What should be the package name? @aviaryan

@yashLadha No need for package name. If I remember right, other Java codes don't have them.

So how should i correct it guide me. @aviaryan
On 30 Mar 2017 5:12 pm, "Avi Aryan"<EMAIL_ADDRESS>wrote:

@yashLadha https://github.com/yashLadha No need for package name. If I
remember right, other Java codes don't have them.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/iiitv/algos/pull/118#issuecomment-290386116, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ARMqT4B7GC3WvTIseaFRPSaeUZWdeIKYks5rq5UrgaJpZM4Mt8LP
.

@yashLadha Leave it empty, like https://github.com/iiitv/algos/blob/master/binary_search/BinarySearch.java

I don't get the difference

@aviaryan Please review it

There is no such need for package name in this code, in my opinion. What do u think? @singhpratyush @Monal5031

@aviaryan: Take a look.


Update yuta

First draft of Yuta update PR - mostly deletions in adjustment to the new conversion factor, waveform and lfp inclusions in spikeextractors, and other stylistic unifications across the buz repo. Final output NWBFile looks the same as before (aside from waveforms being in units table instead of SpikeEvents), but code is reduced and more in line with modern API.
Just need to check/polish a few things then I'll take out of draft and notify.

@bendichter This PR is ready for final review now.


Clear cache

Clear cache steps:

[ ] stop the sync process
- [ ]

@grod220  Can you check if these steps are correct? I've already done the 1st and 2nd point; for the 3rd we need a method with wasm; 4 I understand that so far only 1 value we have to change

For the viewServer, you should just need to re-initialize that class. I don't think you need a free method. Just throw the old class away. For networks custom values, not sure you need to clear anything there.
The rest seems right to me 👍

@grod220 can you check if I'm moving in the right direction-  https://github.com/penumbra-zone/web/compare/main...70-clear-cache

Yes, that looks like the right direction to me. If you open a PR, I can give more specific feedback. Does it work?

Query data cannot be undefined. Please make sure to return a value other than undefined from your query function. Affected query key: ["sync-blocks","https://grpc.testnet.penumbra.zone"]
Error: ["sync-blocks","https://grpc.testnet.penumbra.zone"] data is undefined
    at Object.onSuccess (vendor.js:145256:19)
    at resolve

works, but show errors from console this hooks -useSyncProgress


webview cann't load the local html at the release mode but debug is correct

Environment
"react": "16.5.0",
  "react-native": "0.57.0",

Description
I load the local html use the code like this:
 const _source = resolveAssetSource(require('../html/public/index.html'));
 var htmlAddress = Platform.select({
       android: {uri: `file:///android_asset/index.html`},
       ios: {uri: `${_source.uri}`},
});
this.state.url = htmlAddress.uri;
  <WebView source={{uri:this.state.url}} />

It can run normal on debug mode,can't on release.
I remenbered the version 0.54 is normal ,and some other version is also has the problem.

Thanks for filing this issue!
Unfortunately, we're in the process of removing WebViews from react-native (in an effort to decrease its surface area). That said, can you file this issue instead at: https://github.com/react-native-community/react-native-webview?


Rewarded Video test ad can't be dismissed by clicking in the close button (after 2.0.0)

Plugin Version
2.0.0
Steps to Reproduce
After 2.0.0 version, using test ads, the Rewarded Video can't be dismissed by clicking in the close button. The close button doesn't even become clickable. It only becomes clickable when the video ends, but the reward has already been given.

Until version 1.3.0, it was possible to click the close button when the timer was about 3~2 seconds, but after version 2.0.0 this is no longer possible (test ads). I'am using android emulator

[√] Flutter (Channel stable, 3.0.5, on Microsoft Windows [Version 10.0.19042.1110], locale en-029)
• Flutter version 3.0.5 at G:\SDKs e frameworks\flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision f1875d570e (6 weeks ago), 2022-07-13 11:24:16 -0700
• Engine revision e85ea0e79c
• Dart version 2.17.6
• DevTools version 2.12.2
[√] Android toolchain - develop for Android devices (Android SDK version 33.0.0-rc1)
• Android SDK at G:\sdk_android
• Platform android-31, build-tools 33.0.0-rc1
• ANDROID_HOME = G:/sdk_android
• Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
• Java version OpenJDK Runtime Environment (build 11.0.12+7-b1504.28-7817840)
• All Android licenses accepted.

Hi @Gilianp
I tried running version 1.3.0 but the result is still the same as 2.0.1. Could you please provide a recorded video for this case?
As defined here, rewarded ad units are non-skippable, but closeable.
Also, this issue may come from the native library as I can also reproduce it with example from googleads-mobile-android-examples.

Demo

There is also a open thread that you can follow up here: https://groups.google.com/g/google-admob-ads-sdk/c/hmx4mWfuDQA

Hi @huycozy, sorry for the delay.
So far I've always developed using test ads with this lib, and I've always been able to close the Rewarded Video before the countdown ends, thus displaying the message that I wouldn't receive the reward. Now that you mention it, I think the problem actually occurred from version 1.3.0 onwards, I'll try to provide a video, but this was really always possible. I just discovered this glitch now as I was no longer able to test the code that runs when the reward is not given (in fact, it would be weird not being able to test this using the test ads).
Finally, I didn't understand the difference between Rewarded Video being non-skippable, but closeable.
Thanks for you support!

Hi @Gilianp
Thanks, please try to provide the video, it will be helpful for us and others.

Finally, I didn't understand the difference between Rewarded Video being non-skippable, but closeable.

It's one of AdMob rewarded ad format & features. Please go to https://support.google.com/admob/answer/7372450?hl=en,  scrolling down and there is a section that explains this.


Take over running this bot

Need someone take over ownership of the running and maintenance of this bot.

I’d be interested in doing this if this is open to non-employees. Just depends on what maintenance entails. (And how the bounty structure works)


Input component improvements

This greatly simplifies the internal logic of the Input component, and at the same time exposes cursorPosition for control. The only breaking change is that onChange now has cursorPosition as an additional argument. value and cursorPositon can otherwise be controlled individually.
This refactoring was motivated by an experienced bug (but unreported I think) where mashing the keyboard caused the cursor to "lag" behind, getting positioned behind the last character and inputting characters in the wrong order. A fast typer on a slow machine might have been able to reproduce this in normal conditions, and given the complexity of the logic I would be surprised if this was the only bug.
I understand the motivation for the current implementation was to imitate React's input component as closely as possible (ref. #406), and while the motivation is understandable and the effort commendable, I don't think it's a good idea to go to such lengths that we reproduce the flawed design of the DOM. Specifically, because the DOM does not allow control over cursor position, React has no choice but to deal with that as best as it can. But since we do have control over it, we can yield control to the consumer when needed instead of trying to predict their intention, while at the same time providing a reasonably simple default implementation that will work in most use cases.
I've continued by adding a few more features (see below), and believe this now fixes #203, although this implements scrolling instead of wrapping.
Todo (but can be merged at any time if desired)

[x] Click to position caret
[x] Scroll instead of wrap overflowing text
Selection (edit: should be a separate PR)

Known issues

[x] Cursor "jumps" when going "out of bounds"
[x] Placeholder text renders over cursor

I'm not sure how to fix the last remaining issue, the placeholder text being rendered over the cursor. Also not sure it's worth it if the component and styling model is going to change anyway.
From what I can gather, it worked before even with the cursor being positioned "before" the text, because the cursor was both absolutely positioned AND a sibling of the text. Now, on the other hand, while the cursor is still absolutely positioned it is no longer a sibling, because the text needs to be contained in a clipping container and the cursor needs to not be clipped. I think z-ordering would have been the fix for this if it was the DOM, but I don't think we have that yet.
Also, CI failure seems to be a fluke.

This refactoring was motivated by an experienced bug (but unreported I think) where mashing the keyboard caused the cursor to "lag" behind, getting positioned behind the last character and inputting characters in the wrong order. A fast typer on a slow machine might have been able to reproduce this in normal conditions, and given the complexity of the logic I would be surprised if this was the only bug.

I really like the way you simplified the logic here (and I'm no longer able to repro the fast-typing issue!)

I don't think it's a good idea to go to such lengths that we reproduce the flawed design of the DOM. Specifically, because the DOM does not allow control over cursor position, React has no choice but to deal with that as best as it can. But since we do have control over it, we can yield control to the consumer when needed instead of trying to predict their intention, while at the same time providing a reasonably simple default implementation that will work in most use cases.

Good point. We have the opportunity with Revery to get control over these aspects w/o inheriting the quirks or flaws of the DOM, so we should take advantage of that.

I'm not sure how to fix the last remaining issue, the placeholder text being rendered over the cursor. Also not sure it's worth it if the component and styling model is going to change anyway.

I'm OK with the behavior as it is today. We can revisit the placeholder text in another issue, or once we have more control around layout / style to implement it cleanly.
Being able to type reliably is the most important aspect for an input control.

Oops. Good catch @Et7f3! Fixed in https://github.com/revery-ui/revery/pull/644/commits/e493a4a21c142546510cc106653c868944dd2686

Can't cursorPosition be in changedEvent ? Most user have {value; _} so it is a non-breaking change.

changedEvent is no longer used because it assumed the change originates from a key event, which it no longer does. It also didn't seem very useful. If you want to react to key strokes, use onKeyDown instead.
I see I've forgotten to remove the type though, which I should.

Many code have handler of the form ({value; _}). Can we have a InputEvent that have value and cursorPosition so we can add other field without break again.

Can we have a InputEvent that have value and cursorPosition so we can add other field without break again.

We could, but it seems unlikely that there should be more state to track. If there is, that seems to imply that the model has changed so much that it probably ought to break existing code. Breaking changes aren't inherently bad, and I usually prefer to err on the side of changes being breaking. That's why we have exhaustiveness checking, warnings on missing record fields in patterns etc. Records also aren't very ergonomic, as you need to bring the fields into scope to access them. There are of course plenty of reasons to use them too, but I don't think "just-in-case" is a good reason.

#472 is still present. Do you consider to fix in this PR or let this issue to be fixed by another PR.

The record came in scope when we include the Input component so it isn't a ergonomic problem.

We could, but it seems unlikely that there should be more state to track
Ok.

#472 is still present. Do you consider to fix in this PR or let this issue to be fixed by another PR.

I think the issue is orthogonal to this PR, so I don;t see why it should block it.

The record came in scope when we include the Input component so it isn't a ergonomic problem.

It is if you use named functions, which I think is a good pattern. You could of course then argue that it isn't particularly useful for this particular event since it'll usually just be dispatched right away, but it still sets a precedent.
I think the same rules should be applied here as we do generally. And if you want other rules to be applied I think you need to argue for it more generally. If the argument is, as I understand it is, that we should use a record just in case we need to add more fields later, I think that is not something we should do in general, and therefore I don't think we should do so here either. That's my reasoning at least.

Revamp are useful to reduce bug. You have fixed some issues when revamp the animation. That why I quoted #472.

Yeah it definitely could have, so good idea to check!


MWPW-139173 MEP Authoring Tag Operators - Add support for & and "not"

When creating a MEP manifest, column names currently support commas as an "OR" operator.  Example: a user on a iOS or Android device would qualify for a column named "ios, android". This PR:

adds support to use & as an "AND" operator on personalization tags (but not for Target experiences)
adds support of the word "not" as a "NOT" operator on personalization tags (but not for Target experiences).  Similar to ! in programming
removes support of the comma operator on target experiences because it causes a problem if the Target experience has a comma in the name.  Example: target-update marquee, banner & carousel should not "use" the comma or ampersand

Resolves: MWPW-139173
More test URL's in Jira but if I put them here they confuse the psi-check
Test URLs: (Spoof an android device first)

Before: https://main--milo--adobecom.hlx.page/drafts/vgoodrich/fragments/139173-mep-and/?pzn=on&martech=off
After: https://139173-mep-not-and--milo--adobecom.hlx.page/drafts/vgoodrich/fragments/139173-mep-and/?pzn=on&martech=off

Would be great if you can add a unit test for the new functionality

@mokimo added to the unit test to specifically test the & and not


Correction for raw affiliation LIP UMR 5668 of CNRS-ENS-INRIAedb, Université Lyon 1, Lyon, France

Correction needed for raw affiliation LIP UMR 5668 of CNRS-ENS-INRIAedb, Université Lyon 1, Lyon, France
raw_affiliation_name: LIP UMR 5668 of CNRS-ENS-INRIAedb, Université Lyon 1, Lyon, France
new_rors: 02feahw73;02kvxyf05;04zmssz18;029brtt94;04msnz457
previous_rors: 02feahw73;02kvxyf05;04zmssz18;029brtt94
works_examples: W2102077542
contact: 0e4725eb5ad6ec78b4ad601ab8652e36:1e6cb484e86311f4a9f80b64e40e @ ens-lyon.fr

This issue was accepted and ingested by the OpenAlex team on 2024-12-19. The new affiliations should be visible within the next 7 days.


fix: fixed minor typo in comment

minor fix

Thank you for your contribution @Homesteady.
I'm merging it!


Created Collapser with View More and Shrink #2051

issue resolved
#2051
https://user-images.githubusercontent.com/49303222/229061067-3f0e74c9-3f07-4977-bdb7-e2ba28ee89d3.mp4

Amazing @VaibhavTalkhande
Just add pointer-events-none in the button enclosing the svg of the icon beside Shrink, By adding this, if someone clicks on the icon, then also shrink will work

Ok

done


[help wanted] how to use cuda version

I compiled the cuda version of lightgbm by following https://lightgbm.readthedocs.io/en/latest/Installation-Guide.html#build-cuda-version-experimental
However, when I try to run the cuda version (with the same parameter used in GPU version based on OpenCL), I encounter the following error
"lightgbm.basic.LightGBMError: GPU Tree Learner was not enabled in this build, Please recompile with CMake option -DUSE_GPU=1"
Is the parameters in the cuda version different from the gpu version?
Could any one help me here?
Thanks.
Aimin

@7starsea Hi!
Good catch, thanks!
Please use device_type="cuda" instead of device_type="gpu".
I'll fix docs clarifying this.

I trained a project (project size (sample, feature) = (18909697, 128)) with the gpu version and the max gpu memory obsesrved is around 3000MB, however, I failed to train this project with the cuda version because of cuda out of memory error.

Please open a new issue with more details for out of memory error preferably with reproducible example on randomly generated data.
I guess this difference can be due to the fact that

in CUDA implementation only double precision is currently supported

and in OpenCL one single precision is used by default.
Maybe you can try to use multiple GPUs with CUDA version?


[prometheus-operator/stable] Overwriting table item 'extraArgs', with non table value

Describe the bug
During the deploy of prometheus-operator i receive the bellow warnings. Without the two values  prometheus don't collect very important metrics from my cluster.
Version of Helm and Kubernetes:

Kubernetes version information:
Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.2", GitCommit:"c97fe5036ef3df2967d086711e6c0c405941e14b", GitTreeState:"clean", BuildDate:"2019-10-15T19:18:23Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.2", GitCommit:"c97fe5036ef3df2967d086711e6c0c405941e14b", GitTreeState:"clean", BuildDate:"2019-10-15T19:09:08Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"linux/amd64"}

Helm version information:
Client: &version.Version{SemVer:"v2.15.0", GitCommit:"c2440264ca6c078a06e088a838b0476d2fc14750", GitTreeState:"clean"} Server: &version.Version{SemVer:"v2.15.0", GitCommit:"c2440264ca6c078a06e088a838b0476d2fc14750", GitTreeState:"clean"}

Which chart:
prometheus-operator/stable
How to reproduce it (as minimally and precisely as possible):
helm install stable/prometheus-operator
Anything else we need to know:

Prometheus Operator Logs:

2019/10/28 10:21:08 Warning: Merging destination map for chart 'prometheus-node-exporter'. Overwriting table item 'extraArgs', with non table value: [--collector.filesystem.ignored-mount-points=^/(dev|proc|sys|var/lib/docker/.+)($|/) --collector.filesystem.ignored-fs-types=^(autofs|binfmt_misc|cgroup|configfs|debugfs|devpts|devtmpfs|fusectl|hugetlbfs|mqueue|overlay|proc|procfs|pstore|rpc_pipefs|securityfs|sysfs|tracefs)$]
2019/10/28 10:21:08 Warning: Merging destination map for chart 'prometheus-node-exporter'. Overwriting table item 'extraArgs', with non table value: [--collector.filesystem.ignored-mount-points=^/(dev|proc|sys|var/lib/docker/.+)($|/) --collector.filesystem.ignored-fs-types=^(autofs|binfmt_misc|cgroup|configfs|debugfs|devpts|devtmpfs|fusectl|hugetlbfs|mqueue|overlay|proc|procfs|pstore|rpc_pipefs|securityfs|sysfs|tracefs)$]

@adyprico I've had the same issue after upgrading to 2.15.2. Reverting helm version to 2.13 helped

Hello , Thank you , i did the same thing and yes it worked. I am waiting for the next release maybe this it will be fixed.

Upgrading helm from 2.14.1 to 2.15.0 triggers those warnings.

Hi @vsliouniaev thanks for your PR, but I still get this issue

Hi @zackijack, are you installing through the main prometheus-operator chart? I think that needs it's requirements bumped to 1.7.3 for the prometheus-node-exporter dependency to be able to install without issue on 2.15.x helm.

The issue in the underlying chart has been fixed, now we need to bump the prometheus operator chart version. That portion is broken for now because the CI process in this repo is failing for everyone
https://github.com/helm/charts/issues/18584


Write prompt to metadata do not work fully

Hello, first thank for this helpful extension.
In settings I checked "Save template to metadata: Write prompt template into the PNG metadata"
When I write a inline template like {value1|value2] the saved metadata is the result for value1 or value2 but not the template with {}
For a more complete example of the problem, this is my inline template :
``
(masterpiece, black hair, ponytail, hair ribbon, ribbon, very long hair, purple eyes, shiny eyes, blush, closed mouth, {smile, parted lips|smile}, detailed face),
{
jester, jester cap, hat, puffy sleeves, short sleeves, pom pom clothes, bridal gauntlets, pajamas, star print, shuriken, navel, pants|
white shirt, green vest, green skirt, plaid skirt, school uniform, bowtie|
yellow shirt, pink skirt, pleated skirt|
bare shoulders, white shirt, off-shoulder shirt, cleavage, navel, shorts, gym shorts
}

And the saved metadata is
``
(masterpiece, black hair, ponytail, hair ribbon, ribbon, very long hair, purple eyes, shiny eyes, blush, closed mouth, smile),
jester, jester cap, hat, puffy sleeves, short sleeves, pom pom clothes, bridal gauntlets, pajamas, star print, shuriken, navel, pants

What is needed is to save the original prompt in metadata

Yes I see same thing, it worked before but break after an update to a new version

When you create an image as a wildcard, two images are displayed.
The first image will appear as a wildcard if, and the second image will appear as an if selected from that wildcard.
Auto-save is saved as the wildcard's selected prompt if; wildcard if is manual save.
I think it would be good to save both or selectively with automatic storage, but I think a1111 should support this.

Do you have adetailer installed? I have the same issue of the template being written as the chosen wildcard values and not the initial wildcard prompt itself. However, when I disable adetailer it seems to save the wildcard/variant prompt correctly as a template.
How to get them to both work together again though is the problem...

Do you have adetailer installed? I have the same issue of the template being written as the chosen wildcard values and not the initial wildcard prompt itself. However, when I disable adetailer it seems to save the wildcard/variant prompt correctly as a template.
How to get them to both work together again though is the problem...

Yes you are right. Without Adetailer it saves the raw prompt. Not where it used to save it at the end but in the middle of the Steps information paragraph.

Do you have adetailer installed? I have the same issue of the template being written as the chosen wildcard values and not the initial wildcard prompt itself. However, when I disable adetailer it seems to save the wildcard/variant prompt correctly as a template.
How to get them to both work together again though is the problem...

So THATS where this is coming from. It's random for me like every once in 4/5 gens, it will just spit out the raw prompt like you said, instead of activating the wildcards/variables.

Can confirm this is still a thing all this time later and it has simply not been fixed.
This is extremely unfortunate, as I like to deal with a lot of wildcards, and it basically means if I ever generate more than one image in a batch, saving the data to/from the image or to a CSV is 100% useless, effectively making any image besides the first one unable to be reproduced since I literally do not know what settings, seed, etc. was chosen.
Basically I can either generate a bunch of really nice images but not know what the parameters were that made it, or I can generate middling image quality and then am forced to use ADetailer after the fact.

Can confirm this is still a thing all this time later and it has simply not been fixed.
This is extremely unfortunate, as I like to deal with a lot of wildcards, and it basically means if I ever generate more than one image in a batch, saving the data to/from the image or to a CSV is 100% useless, effectively making any image besides the first one unable to be reproduced since I literally do not know what settings, seed, etc. was chosen.
Basically I can either generate a bunch of really nice images but not know what the parameters were that made it, or I can generate middling image quality and then am forced to use ADetailer after the fact in img2img.

What are you talking about?
Go to SETTINGS >INFOTEXT>Write infotext to metadata of the generated image
Go to SETTINGS>DYNAMIC PROMPTS>Save template to metadata: Write prompt template into the PNG metadata
While this DOES NOT save the raw wildcards, it saves all creation data.
To save the raw wildcard, generate one picture with ADETAILER disabled.

What are you talking about? Go to SETTINGS >INFOTEXT>Write infotext to metadata of the generated image "" >Create a text file with infotext next to every generated image
Go to SETTINGS>DYNAMIC PROMPTS>Save template to metadata: Write prompt template into the PNG metadata
While this DOES NOT save the raw wildcards, it saves all creation data. To save the raw wildcard, generate one picture with ADETAILER disabled.

I already have that on, which is how I figured out there's a problem, since as you said, it generates fine if you do one image, and one image ONLY.

I create a template. I set up a batch image generation based on that template. I run it.
What I expect: CSV stores both the template, and for each image in the batch that's rolled, the individual prompt that gets derived from the template. Each image has the generation data embedded in the image as well as a fallback (which yes, I have enabled). This is how it usually works without ADetailer, or at least, it's how it used to work on old Forge.
What happens: CSV stores no template, and whatever the first image was that it rolled (n) times over. If I tell it to do 50 images, it writes 50 prompts that are identical to the CSV, not the actual generation information. Info embedded into the generated image is also of this first prompt, regardless of what the actual generation parameters are.

Needless to say, this is a problem. Right now the only workaround is to not use ADetailer on txt2img at all and only use it on img2img, which is kind of a hacky workaround.
Granted, from what I see elsewhere, this might be due to how ADetailer "works" in that it calls things in a way that Dynamic Prompts doesn't like. I'm bringing it to their attention as well, on the off chance that they can somehow fix this.


package.json includes workspace:*

这个包没发好呀，用不了。

See https://registry.npmjs.com/@perfsee/webpack

fixed in 1.0.0-alpha.3 packages, you may want to reinstall the plugin by yarn add @perfsee/webpack@latest


Remote component sources from the registry

Background
Referencing a Wasm module from a remote bindle has been possible since #456. However, because of the infrastructure requirements for running Bindle, #890 introduced support for referencing a remote component source from an HTTP URL to simplify this scenario.
This made possible things like templates for the static fileserver and redirect components (#898), since all you need is to publish a Wasm module to a URL.
However, because the URL source points to a single file (similarly, you reference a single parcel from the remote bindle), this means you cannot use a component that requires additional assets or configuration in order to function properly. (examples for this could include components with static assets, ML models, logos, or https://github.com/radu-matei/spin-kv-explorer)
With spin registry publish, you can distribute an application to a remote registry service. spin registry publish also adds any asset referenced by the component in the distributed package.
Proposal
I would like to propose expanding the options for the module source to allow referencing a remote component from the registry. There are two (non-mutually exclusive) ways in which we could address this:

reference a single Wasm module from a remote registry reference — this would bring feature parity with the existing functionality. :

source = { reference = "ghcr.io/radu-matei/my-spin-app:v1", digest = "sha256:aaa" }

Note that digest here would require a user to either calculate the digest of the Wasm module locally, or inspect the generated manifest or lockfile, neither of which would be ideal. Alternatively, this could allow referencing the Wasm source of a given component ID instead — see next option.

reference an entire Spin component from a remote registry reference:

source = { reference = "ghcr.io/radu-matei/my-spin-app:v1", id = "my-spin-component" }

A component in Spin is a Wasm module together with configuration and assets. A user would choose to reference an entire component because its functionality is something they would like to reuse in their application. This raises the following question: what should be the bahavior for handling configuration, considering there are two sources of configuration for the new component — the component configuration in the registry, and potentially user-defined configuration in the current spin.toml.
There are two things to consider here:

the referenced component might not function at all without its default configuration it was distributed with
the referenced component is potentially a third party extension and it should not be implicitly granted access to resources (allowed hosts, KV stores, current files or configuration)

Given that the immediate value we get out of referencing an entire component is distributing other assets together with the Wasm module, we could treat files that were part of the component specially and use those (and potentially allow a user to override them with other files). Everything else in the component configuration must be defined by the user importing the component.
We could introduce a new component type (in preparation of eventually having "library components" as opposed to "executable components"), but how we handle configuration would still need to be carefully assessed.
Is supporting components from the registry something we want to enable?

The foundation of this feature has been added in https://github.com/fermyon/spin/pull/2524.  Wanted to cross-reference here as further work continues (eg around the A component in Spin is a Wasm module together with configuration and assets bit that @radu-matei mentions above.)


Fix error sending to client

Bones's custom logger middleware sends any captured errors directly to the client.
Unfortunately, there seems to be a bug — in at least some cases, this results in an empty JSON object showing up in the client side. We could omit the stack trace by doing a res.send(err.toString()), resulting in an HTML page with just the error message. If we also want the stack trace, we might have to do some more work. In any case though, it would be good to track down and understand precisely why res.send(err) results in an empty JSON response. I have a suspicion it may have to do with the default behavior for calling toJSON on an Error object, but that's just a hunch, I haven't looked into it yet.
Also, we may want to distinguish between production and development behavior here, if only for the sake of demonstrating good practices (and maybe init-time branching as a concept).

This seems to be because calling JSON.stringify skips non-enumerable properties, and an error's message, name, stack etc. are all non-enumerable.


Finalize DNS connections to firstgraphics.app and redirect .org domain

SSL is up https://www.firstgraphicsapp.org/

New domain is up https://www.firstgraphics.app/

Redirect change requests are in for both our .org domain and the naked www on our .app domain.

The .org redirect is working.

The naked domain is redirecting thanks to nakedssl.com. We're done here. https://firstgraphics.app


Only show latest version in each minor line when upgrading k3s/rke2 clusters

Background:
This has been controlled through KDM for k3s and rke2. In the rancher 2.5 line, this is working correctly because there is only ever one minor version at a time in that KDM line. However, in 2.6, with the introduction of provisioning, k3s and rke2 now follow a KDM pattern that is more similar to rke1 in that it has multiple versions available in a specific minor version line (for example 1.21.4, 1.21.5, and 1.21.6).
Description:
During cluster creation, this works properly and only shows the latest version. However, when upgrading an imported cluster, it shows all of these versions as available. I believe it should only show the latest version.
This is primarily cosmetic as the growing list could be frustrating for a user. The current view for example is:
Upgrading Imported Cluster:

My expectations here are for it to show, in this order:
v1.21.6+rke2r1
v1.20.12+rke2r1
v1.19.16+rke2r1
v1.19.15+rke2r2 (current version of the imported cluster)
Provisioning New Cluster:

This meets expectations.

While not the same issue, this is similar to https://github.com/rancher/dashboard/issues/4127 (PR https://github.com/rancher/dashboard/pull/4154) That change fixed this on the cluster creation page. We should do this as well for cluster edit (such as for k3s/rke2 upgrades).