Replace bower-asset with npm-asset

Related f.ex. to https://github.com/hiqdev/asset-packagist/issues/163 and especially to https://github.com/hiqdev/asset-packagist/issues/163#issuecomment-1805642726 .
composer update results to some packages downgrade.
Question is if/how it's related to https://bower.io/, it (as stated there) is maintained, but f.ex.

it's officially stated that "...we recommend using Yarn and Vite..."
package search on https://bower.io/search/ does not work at all

All packages required by Yii2 are available as npm-asset/package and versions seem to be correct in that case.

Just replacing bower with npm might lead to problems, since both services work very differently.
In a nutshell: Bower was actually made in a way how we use it in Yii 2 for (pre-bundled) frontend assets, npm is more meant to be build with ie. webpack, although most packages have dist files, but it's not required. Also the dependencies may vary a lot.
I'd strongly recommend to wait for a fix in asset-packagist.
@bizley @terabytesoftw A change from bower to npm might be an option for 2.2, but please not for 2.0.

Is there any workaround?
Does not look like there will be someone wo will fix it from the asset-packagist side.

A the moment bower-asset/jquery is not installable anymore for us. @karelvasicek do you have any workaround?

@ItsReddi

do you have any workaround?

No, we unfortunately don't have any. We updated our main project some time ago and it hadn't worked either initially (packages had been downgraded), but started to work some time later (packages were updated again). It seems to work from time to time.

In composer.json:
add (this makes composer believe these packages are installed)
    "bower-asset/jquery": "*",
    "bower-asset/jquery-ui": "*"
}

Next install the depencies with npm,
 "jquery-ui"<EMAIL_ADDRESS> "jquery": "^3.0.0"

Above dependency for jquery-ui, makes it being installed into jquery-ui instead of components-jqueryui, long ago - I think that fixes some issues with Yii and maybe older JS.
Lastly see here how to tell yii Asset Manager to load your npm files..
https://www.yiiframework.com/doc/guide/2.0/en/structure-assets#customizing-asset-bundles
Rinse and repeat for whatever library u need to replace.

@karelvasicek @ailmanki Thanks.
For reference:
https://github.com/hiqdev/asset-packagist/issues/167

Here i think it is worth considering two solutions for the future.

One possible solution is to use cdn, both in dev and prod versions.
The other is to extract the assets from the composer.json of the packages and use npm, all the packages used are compatible and have dist for use, in this case we can use npm or php-forge/foxy for this purpose.

It seems to me no issue; the framework allows perfectly to replace it with NPM or any other mechanism.
Maybe a guide would help - instead of my small post above?

I don't know what's been going on with Bower's jQuery but I clicked Fetch Updates just now on https://asset-packagist.org/package/bower-asset/jquery and it is now showing the newer releases of jQuery beyond 3.6.1. My composer project is no longer downgrading my bower jquery package.

I don't know what's been going on with Bower's jQuery but I clicked Fetch Updates just now on https://asset-packagist.org/package/bower-asset/jquery and it is now showing the newer releases of jQuery beyond 3.6.1. My composer project is no longer downgrading my bower jquery package.

Sadly that works only sometimes for some hours. It is already gone again.

@SilverFire, @hiqsol would you please take a look at this one?

we already use yarn in our projects and removed bower completely


Resolve SECURESIGN-1405

Done a quick test, on a cluster ran the cmd oc delete fulcio --all the fulcio cert secret does not seem to be getting deleted and the label is not being removed

The certificate is being revoked only if it needs to be changed.

The certificate is being revoked only if it needs to be changed.

Does this not block key rotation for operator generated certificates then?, Or maybe we don't care about the operator generated ones since, its more for dev?

I guess it can still be done if we remove the label then, delete the fulcio instance?

oh, yes, I was focusing on the SECURESIGN-1405 and totally forgot about key rotation. You need to invalidate key by removing "rhtas.redhat.com/fulcio_v1.crt.pem" label from the key before fulcio removal. Otherwise, the operator will try to compare the labeled secret and try to bind it with the new deployment.
You can use oc label secret -l rhtas.redhat.com/fulcio_v1.crt.pem  rhtas.redhat.com/fulcio_v1.crt.pem-

@bouskaJ can you update https://github.com/securesign/secure-sign-operator/blob/main/docs/fulcio-key-rotation.md with this :), thanks

@bouskaJ I think I found an issue with this, wdyt?, here is reproducers

Do a default deploy & install
Create the keys and patch as per https://gitlab.cee.redhat.com/software-supply-chain-documentation/doc-rhtas/-/merge_requests/28/diffs#dd4e4d702e5901308da5d6e314eed5afd9b09c0a
check the status for the secret:

➜  secure-sign-operator git:(SECURESIGN-1405) ✗ oc get ctlog securesign-sample -o jsonpath='{.status.rootCertificates[*].name}'
fulcio-config%
➜  secure-sign-operator git:(SECURESIGN-1405) ✗ oc get fulcio securesign-sample -o jsonpath='{.status.certificate.caRef.name}'
fulcio-config%
➜  secure-sign-operator git:(SECURESIGN-1405) ✗

that secret is the one you just created however it does not have the rhtas.redhat.com/fulcio_v1.crt.pem: cert

Ready for review. @JasonPowr @osmman

/lgtm


Enhance CSS for Better User Interface

Improve the CSS styling across the application to ensure a more user-friendly and visually appealing interface. Focus on refining the design on different pages, ensuring consistency, and enhancing the overall user experience. Address any responsive design issues and ensure the application is accessible on various devices and screen sizes.

I would like to work on this issue, can you assign it to me. Thanks!

@AdityaP7649 sure. Glad to have you with us.
As this is a multi task issue, rather than assigning, please submit a PR after October 1st and we will accept it. It will count towards your goal. Just tag the PR correctly with this issue.


Staged images - handle Left - T [Was :Staged image pattern]

There is an option for right-T but all of my images were staged as left-T. There is currently no option for this.

Looks like Left-T is an option now, can this issue be closed?

@kleintom thanks for this careful look!  We can indeed close this.


Add puppet-doc-lint

puppet-doc-lint has been deprecated in favor of puppet-strings, so I'm going to close this.


Update CONTRIBUTING.md

Corrected grammatical errors in the Contributing page
Fixes
Closes #1509
Relates #1553 and #1555

kindly merge the PR
THANK YOU


Storybook: .storybook/preview.ts is detected as unused

Sorry, but here's another Storybook issue I didn't notice before.  It seems that .storybook/preview.ts is detected as unused.  I checked other extensions like .js and .tsx and those were detected as unused as well.  From looking briefly at the code for the Storybook plugin, I'm confused why this would be, since you default to adding those files as entries.
Reproduction is the same as last time: https://stackblitz.com/edit/github-z465pp?file=package.json

:rocket: This issue has been resolved in v2.38.2. See Release 2.38.2 for release notes.

I've inter-twisted some logic here, should be fixed now :)

Works, thanks!


Fix quoting issue on generate sql statements

Using the previous method to generate the quote string could lead to incorrect sql statement where double quotes were used for select statements in MySql.
By using the quote_table_name function from Rails, the correct quoting mechnism will be automatically used for the specific database.
Fixes #1369
All Submissions:

[x] I've checked to ensure there aren't other open Pull Requests for the same update/change.
[x] I've submitted a ticket for my issue if one did not already exist.
[x] My submission passes all tests. (Please run the full test suite locally to cut down on noise from travis failures.)
[x] I've used Github auto-closing keywords in the commit message or the description.
[ ] I've added/updated tests for this change.

Bug fixes and Changes to Core Features:

[ ] I've included an explanation of what the changes do and why I'd like you to include them.
[ ] I've provided test(s) that fails without the change.

Test Plan:
Reviewer Checklist:

[ ] Maintains compliance with JSON:API
[ ] Adequate test coverage exists to prevent regressions

see https://github.com/cerebris/jsonapi-resources/pull/1400

Here is an example of getting a test to fail for this issue:
https://github.com/Kallin/jsonapi-resources/commit/174384862fde695a2c385cbd34792bf97e902e16
as others have said, adding MySQL to CI matrix would surface this issue.

resolved in v011-dev via https://github.com/cerebris/jsonapi-resources/pull/1400 and https://github.com/cerebris/jsonapi-resources/pull/1370 if this is needed in another branch, let's re-use those learnings and apply there


tcpdump not working on Mariner

root [ ~ ]# ./kdebug -t tcpdump
INFO[0000] Exec tcpdump [-nvvv ]
FATA[0000] exec: "tcpdump": executable file not found in $PATH

Improve error message and provide install guidance.
tdnf install -y tcpdump
tdnf search xxx


Define the Head and Body of an HTML Document for challenge solution

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] All the files I changed are in the same world language (for example: only English changes, or only Chinese changes, etc.)
[x] My changes do not use shortened URLs or affiliate links.

Closes #35757

@sil3nthill  It appears you did not test your code locally as your code fails for invalid syntax.
Also, you do not have to close the PR.  You just need to fix it.  Also, I don't believe we concluded exactly what the fix needed to be in the original issue.  The regex you are attempting on the 2nd to last test would fail if the body tags were missing but the test would fail for The head element should wrap around the title element if the body tags were missing, which would be confusing for the user.  I suggest the extra validation go in either the There should be only one body element on the page. test or the The body element should wrap around both the h1 and p elements. test to make more since to the campers.

hello  @RandellDawson , i see yeah , so just let me close my other pr for this , because i fixed that bug . maybe , i think we need to talk about it in the chat room

Reopen this PR then.

@sil3nthill Have you resolved this problem locally yet?  If not, how can we help?

hello @RandellDawson  i was working on it but i didnt get it do you want to add another test ?
text: The body element should wrap around both the h1and pelements
  testString: assert(code.match(/\s*?<title>\s*?.*?\s*?<\/title>\s*?<\/head>\s*?\s*?.*?\s*?<\/body>/gi), 'The head element should wrap around the title element.');

what do you think about this ?

hello @RandellDawson  just fixed the bug and tested it locally and all is good

will update the PR now

hello @RandellDawson  just tested the code again locally and everything seems ok ,  and the new PR passed.
tell me if you further details , cheers

???

@moT01  i will start working on it now ! thanks

if i understood clearly you want to take off the old tests for using
 and
 tags , and add them to the regex , correct me if i am wrong @moT01

Both of the bottom two tests say "The body element should wrap around both the h1 and p elements" - we only need one of these.

Both of the bottom two tests say "The body element should wrap around both the h1 and p elements" - we only need one of these.

@moT01  hello again , i fixed it again and tested it locally tell me if you are okey with this , and make my day with another merge haha ! cheers
1st case all good :

second case if he puts p and h1 outside of body  :

3rd case no h1 or p

Also i made it possible to the user to enter h1 before p or p before h1 since the challenge doesnt mention anything about the order of tags

The test text is "The body element should wrap around both the h1 and p elements" but if you put the body tags in properly do what that sentence asks, it can still fail if the head or title aren't there. I may be nitpicking too much here, cause I tested it and it works. But could you also remove the checks for the head and title in your regex - then we should be golden. Sorry to keep asking for changes, it's really probably good enough like this. But that's one edge case that we can solve quick I think.

@moT01  yes i got you , i will change it as u want to no problem ! thanks !

@moT01  okey no problem i understand , i will just remove those checks for the title and the head

I gave it another quick test. I think it looks good now. Thanks for the PR and the prompt fixes @sil3nthill 😄

@moT01  my pleasure ! and thank you for your time !!

@sil3nthill Thank you for your contribution to the page! :+1:
We're happy to accept these changes, and look forward to future contributions. :memo:

hi, i made the form in Firefox 68 on Debian 10 32 bits and i get the error in the image. Then I did it in chromium 83 and it works perfectly.


Fix some Clippy lints

Sometimes my rust analyzer throws on my repositories as well, cargo clean tends to fix those undisplayed linting issues.
Also, there are some version bumps for the  esp-ieee802154-examples, I commit those as well if you want

Thanks! The version bump is probably worth a separate PR if you like to do that

Thanks! The version bump is probably worth a separate PR if you like to do that

You're welcome, I just added the version bump PR too


Unsure about leap parameter

I'm not sure what value to put for the leap parameter for CalendarChinese or what it's for, could you explain it in more detail?

Hi @r1zyn,
The leap month is determined by the chinese calendar.
So if you have a chinese date which falls into a leap month you'd need to set leap=true.
I recommend reading http://chineseastrologyforkids.weebly.com/leap-years.html


Issue with Neovim on MacOS M1

When I run :TSC it says "Type-checking already in progress" and it never shows anything else. It has been like that for almost an hour.
:TSCOpen shows an empty list and I know that there are some issues in the codebase
I configured it through LazyVim like this
return {
  'dmmulroy/tsc.nvim',
  opts = {},
}

And when using :Lazy it says the plugin is loaded.
I am also using typescript-tools
Any ideas what could be the issue?

Could you provide a minimal repo where this is reproducible 🙏

@dmmulroy what exactly do you need? My neovim config?

As barebones of a typescript repo where you can reproduce the issue 🙏


Better help for geocoder config

This is annoying:
(venv) RMT-ITS-152821:geocode-sqlite camico$ geocode-sqlite mapquest --help
Usage: geocode-sqlite [OPTIONS] DATABASE TABLE COMMAND [ARGS]...
Try 'geocode-sqlite --help' for help.

Error: Missing command.

I want to see what options I need to pass for a specific geocoder, but I can't currently without passing in a database and table name, and that's a lot of typing to see a help message.

Fixed in #9


Example should be added to the section of the documentation

For the "Signing a user into a specific tenant" section, in addition to showing the URL that references the tenant ID, also show an example of a URL that does so symbolically instead of using the ID, e.g.
https://login.microsoftonline.com/contoso.onmicrosoft.com
The current example only shows using the tenant ID in the URL for a specific tenant. It may save others time if the Contoso example was also included in the documentation.
Can you add an example in doc as required.

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

ID: 401c04b2-ff26-fda8-de7e-8ccc4b3a4d33
Version Independent ID: d2af39ff-0862-16e6-4845-6e793ecf20eb
Content: Configure identity providers (MSAL iOS/macOS) - Microsoft Entra
Content Source: articles/active-directory/develop/config-authority.md
Service: active-directory
Sub-service: develop
GitHub Login: @cilwerner
Microsoft Alias: cwerner

@cilwerner
Can you please check and add your comments on this doc update request as applicable.


Reminder to remove explicit OS constraint on Travis upgrade

As mentioned in #43 opting in early fixes HHVM, but once Travis pushes trusty as default then we won't need explicit dependence, so we should remove so that it isn't confusing in future.
More info here: https://blog.travis-ci.com/2017-07-11-trusty-as-default-linux-is-coming.
This issue should be closable by end of August.

https://blog.travis-ci.com/2017-08-31-trusty-as-default-status
It's technically closable tomorrow, but I'm going to go ahead and commit the change as part of the v1.2 release.


Forcing setProps to update viewState with DeckGL Standalone and Vue.js

Really enjoying using DeckGL!!
I've created a simple proof of concept, to see if I can get DeckGL to play nicely with Vue JS.
Demo on Glitch
All seems well, but I feel like I'm hacking the deckgl.setProps() function to get the viewState to update.
In my Vue application, in data, i have an object called "deckViewState" that contains the settings for lat,long, zoom, pitch etc. This object (this.deckViewState) is updated when the UI slider values are updated in the Vue Application.
However, because we need to call setProps() and pass in the new viewState when anything changes, if we pass in the this.deckViewState, deckgl doesn't change state because (I guess) it doesn't see a change, because it is constantly changing.
So, to "hack" this i'm passing the "this.deckViewState" as a new cloned object, and this seems to force deckgl to recognise a change of state, and update the view.
this.deckgl.setProps({ 	viewState: JSON.parse(JSON.stringify(this.deckViewState))  });
If this is OK, then great, but feels like this could be an overly intensive step, and could possibly(?) cause memory issues.
Really though, is there a way of telling to DeckGL, "hey, just update to these values", even if you don't "believe" anything has changed... Forcing it?
Thanks
Mike

You are correct, Deck does not consider a prop "changed" if it's the same object.  This is important for perf -- otherwise, we'll be constantly doing deep comparisons of all the things (view states, layers, etc.) on every animation frame. Using JSON.parse to clone the object is excessive, though. You can simply call
deck.setProps({viewState: {...this.deckViewState}});

Which is very cheap.

Makes sense... thanks!


Vmap-based parallelization possible with variable sized inputs?

Hi,
Apologies if this is a trivial question; I couldn't find a simple answer in the docs/tutorials, I thought I could ask for your input.
I would like to solve variably-sized linear entropic OT problems in a batch.
Assume I have $N$ cost matrices $\mathbf{C}=[\mathbf{C}_1,\ldots,\mathbf{C}_N]$, that are not of the same shape. Similarly I have appropriately-sized marginals, $[a_1,\ldots,a_N]$ and $[b_1,\ldots,b_N]$, for each such OT problem.
Would it be possible to vmap the Sinkhorn solver to solve these problems in parallel with ott?
I read this tutorial. If I understand correctly, it shows how to vmap to solve several same sized OT problems, but I have not seen an instance where one solves differently-sized OT problems. Could you please let me know if I missed something?
Thanks!

hi Sanketh, we're sorry for the very delayed answer.
I think you want to look at this : https://ott-jax.readthedocs.io/en/latest/_autosummary/ott.tools.segment_sinkhorn.segment_sinkhorn.html
we haven't written a tutorial for this functionality... but as usual, you can find proto-tutorials in tests:
https://github.com/ott-jax/ott/blob/main/tests/tools/segment_sinkhorn_test.py
Thanks again and apologies for not being more reactive!

Thanks @marcocuturi! This looks to be exactly what I need. I'll give it a shot and post here if it works, so it could be useful for future users.

@sankethvedula all good on this or shall we close the issue?


Toggling doesn't correctly trigger onChangeState

Sliding appears to work
I was able to fix by removing line 165
var callHandlers = this.start.state != state;
and replacing it with
var callHandlers = false;     if (this.start.stateChanged) {       callHandlers = this.start.state != state;     } else {       callHandlers = this.state.state != state;     }

this library needs some serious updates

I switched over to this https://github.com/xinthink/react-native-material-kit


Add your paper hyperlink

Could you please put your paper hyperlink on the README page? Thanks a lot!

We have already putit in the News (新闻) section:
[2023/5/25] 发布了Lawyer LLaMA技术报告。


uefi-services: Change panic handler log message.

The panic handler now displays its log message using println! instead of error!. The message prefix is altered from [ERROR] to [PANIC]. The extraneous filename and line number printed by error! are also removed from the log message.
Previously, the panic handler in uefi-services would use error! to print a log message. By using error!, the log message would also include the file name and line number of the panic handler function. As the file name and line number where the panic originated from are logged using the PanicInfo struct, this information is not necessary. By printing the log message with println! instead of error! this unnecessary information can be removed.
Example
I temporarily added a panic call to the uefi test runner to show the panic log messages:
    // ...

    // uefi-test-runner/src/main.rs@21
    // Initialize utilities (logging, memory allocation...)
    uefi_services::init(&mut st).expect("Failed to initialize utilities");

    // test a call to panic
    panic!("Here is a panic!");

    // unit tests here

    // output firmware-vendor (CStr16 to Rust string)
    let mut buf = String::new();

    // ...

Log message before this commit:
[ERROR]: uefi-services/src/lib.rs@184: panicked at 'Here is a panic!', uefi-test-runner/src/main.rs:25:5

Log message after commit:
[PANIC]: panicked at 'Here is a panic!', uefi-test-runner/src/main.rs:25:5

Checklist

[x] Sensible git history (for example, squash "typo" or "fix" commits): See the
Rewriting History guide for
help.
[x] Update the changelog (if necessary)

LGTM, thanks :)

Glad to contribute! :)

Very nice, thanks for the contribution!


How does inline script transpiling work?

I have had my best attempt at running source from within a script tag, but it doesn;t seem to run anything. Am i missing a config somewhere? I would expect the console to write something but absolutely nothing is run ... do I need to invoke the module somehow?
<html>
    <head>
        <script src="../node_modules/systemjs/dist/system.js"></script>
        <script>
          System.config({
              map: {
                  typescript: 'node_modules/typescript/lib/typescript.js',
               },
              transpiler: 'typescript',
              baseURL: '..'
          });
        </script>
    </head>

    <body>
    <script type="module">
      console.log("module loaded"); // not running
    </script>
    </body>
</html>

lol, wrong project :/


llm-eval: not responding to 'what is your name?' or 'what is the difference between star wars and star trek?'

On my Mac, I see the error
CLIENT ERROR: TUINSRemoteViewController does not override -viewServiceDidTerminateWithError: and thus cannot react to catastrophic errors beyond logging them

It does respond to compare python and swift fine though

That actually looks "right":
python -m mlx_lm.generate --model ~/Documents/huggingface/models/mlx-community/phi-2-hf-4bit-mlx --prompt 'Instruct: what is your name?. Output: '
Special tokens have been added in the vocabulary, make sure the associated word embeddings are fine-tuned or trained.
==========
Prompt: Instruct: what is your name?. Output:

==========
Prompt: 32.359 tokens-per-sec
Generation: 0.000 tokens-per-sec

The problem seems to be in the prompt template:
        "Instruct: \(prompt). Output: "

it should be:
        "Instruct: \(prompt)\nOutput: "

that gives a much better response, though in (perhaps) Chinese?
Nothing from 'what is the difference between star wars and star trek?' but the python version doesn't either.

It looks like phi2 can't answer that prompt -- maybe it doesn't cover that info or maybe it is tool small?  mistral7B4bit aka mlx-community/Mistral-7B-v0.1-hf-4bit-mlx seems to do an ok job, though sometimes a bit silly.
Three changes were made and I think this fixes or greatly improves the response here:

the prompt for Phi was adjusted to fit the format better -- it is sensitive to the exact wording
the temperature was set up to 0.6 to match the python code
a new random seed is generated for each time you generate -- you can explore a little

You may need to switch to a larger model like Mistral 7B to see more interesting responses for a wider range of inputs.

Closing this one:

some models can't answer those types of questions
in general the models perform the same on the swift and python mlx implementations (and I think roughly the same on other implementations
sometimes the output is wonky, but that seems to be "correct" in that the model can really produce unusual output


UBO Declaration submission impossible

I cannot seem to submit a UBO declaration with the SDK, though it works fine with an http request.

 This is why you got such message.

Hope it's clear,
Best regards

Hi @Riwak
Thanks for the help! I'll try that as soon as possible.
Since the http api only requires the IDs and the Status, I thought it was also the case for the SDK.

Update:
It still does not work even when first getting the full UboDeclaration, changing the Status and sending it with the api.UboDeclarations.update method.

Hello @Tidaren
About the Ubos field, it's only for UBO Objects. Please find below an example of a complete UboDeclaration with one Ubo in it.
{
    Id: 'AN_ID',
    UserId: 'AN_ID',
    CreationDate:<PHONE_NUMBER>,
    ProcessedDate: null,
    Status: 'VALIDATION_ASKED',
    Reason: null,
    Message: null,
    Ubos:
        [ {
                Id: 'AN_ID',
                CreationDate:<PHONE_NUMBER>,
                LastName: 'Michael_Node',
                FirstName: 'John_Node',
                Birthday:<PHONE_NUMBER>00,
                Nationality: 'FR',
                Address: {
                            "AddressLine1": "Street1",
                            "AddressLine2": "The Loop",
                            "City": "Paris",
                            "Region": "Ile de France",
                            "PostalCode": "75001",
                            "Country": "FR"
                               },
                Birthplace: {
                             "City": "Paris",
                             "Country": "FR"
                               },
                IsActive: true
            } ],
}

Does the object you are trying to send have the same structure?

Yes it does have the same structure.

@Tidaren could you find a solution as I am running in the same error

@zoolle Only solution I have is to use a custom http call for this operation instead of using the sdk until the issue is fixed. I didn't have much time to look into why it fails with the sdk.

Hello, @Tidaren .  I am trying to reproduce your issue by sending this object on the Update method:
{
Id: 'blabla',
UserId: 'blabla',
CreationDate:<PHONE_NUMBER>,
ProcessedDate: null,
Status: 'VALIDATION_ASKED',
Reason: null,
Message: null,
Ubos: [
{
Address: [Object],
Birthplace: [Object],
Id: 'blabla',
CreationDate:<PHONE_NUMBER>,
LastName: 'Doe_NodejsSDK',
FirstName: 'John_NodejsSDK',
Birthday:<PHONE_NUMBER>00,
Nationality: 'FR',
IsActive: true
}
]
}
It seems to work as it should, the status is updated correctly. Are you still having this issue? If yes, then what status does your UboDeclaration have before updating it?

@iulian03 Sorry I cannot test it as I'm on other projects now. If it now works, good. We can close the issue then. Could anyone else confirm?


Add WithField() companion to WithFields()

From time to time one only has a single field to log parametrically. In logrus this is typically done via WithField(). While this library was originally intended somewhat as a standard logging interface and not a 1:1 wrapping of logrus, I still think this is a potentially useful option to have as it avoids constructing an additional fields map with only one item.
It shouldn't be an issue later on if we swap out the logrus library as we can then simply call the WithFields() internal implementation with a single field.

Should we look at moving towards the style of the API in log/slog?


create normal example project without pod

Hi,
I don't like use pod to add any plugin, i want to add it normally, can you create a normal example of slider.
thanks

you can just download the project, and copy the files out of the Pod/Classes folder.


Added "User unauthorized" in 1020

Added "User unauthorized" for LDAP users who don't have group name and privilege.
Defect: https://jazz07.rchland.ibm.com:13443/jazz/web/projects/CSSD#action=com.ibm.team.workitem.viewWorkItem&id=620781


Need quick pointers

Hello I 've been trying using golden layout in one of the organization's project. I have gone through few tutorial online and wanted to customize the github source code as per our requirements. I need few quick pointers , if anybody help.

How to start this open source code? i can run index.html in browser, but was looking for any npm command (start, serve or anyother), which start it in as server publishing the pages.

If I run it in browser by running index.html, I am able to pup out only single panel at a time, and even then it won't get pop-in back by clicking the right-bottom icon. is it known issue or I must be doing something wrong.

Thanks for any help or pointers..

Did you check these?
https://www.golden-layout.com/docs
https://www.golden-layout.com/examples
Regarding Q1, I think you are looking for https://github.com/deepstreamIO/golden-layout/blob/master/gulpfile.js file, probably gulp dev is what you need to run while changing GL's source code.


Fix leave removing more than one node

When leaving a node (using an outside event or whatever to see if the node had died) liferaft would run end on the node you're leaving.
This would in turn emit the end event, which then would be caught in this once listener, resulting in it running leave again.
The second time around running leave, the end call will just break since the node is already in the STOPPED state. After this the splice will happen twice on the same index (one from the original call, and one from the event listener's call), effectively removing 2 nodes from the list (if there are more after the index we're deleting)
I added a failing test case and then fixed the issue.
Before fix:
  liferaft
    bugs
      1) correctly deletes nodes from the list on leave

  0 passing (19ms)
  1 failing

  1) liferaft bugs correctly deletes nodes from the list on leave:
     Unknown assertation failure occured, assumed `1` to equal (===) `2`
      1040.       assume(raft.nodes.length).equals(2);

After fix:
  liferaft
    bugs
      ✓ correctly deletes nodes from the list on leave
  1 passing (15ms)

Any update on getting this merged? Don't want to be maintaining my own npm version :)

@JamyDev great find! Will merge and get this published. Definitely let us know how you end up using this :).

Thanks! Will do!


Document how to enhance assets:precompile to provide compressed assets

https://github.com/rails/propshaft/issues/158 provided some good discussion and a code example for how to provide compressed assets. This seems like useful information to add to the documentation, especially for folks who want to use Propshaft and are running their application behind NGINX with the gzip_static configuration.

Nice one.
What do you think about changing the example to use gzip instead of Brotli since it's more supported out of the box by NGINX and other web servers? It could probably be a zero dependency "production ready" solution that uses: https://ruby-doc.org/3.2.0/exts/zlib/Zlib/GzipWriter.html

No strong preference from me. Would you mind using the "Add a suggestion" feature to suggest the specific changes you had in mind using GzipWriter (especially if you're able to verify the code locally - I'm on mobile at the moment)?

Would you mind using the "Add a suggestion" feature to suggest the specific changes you had in mind using GzipWriter (especially if you're able to verify the code locally - I'm on mobile at the moment)?

No problem. I can provide confirmation on if it works or not tomorrow morning EST.

Could you move this to the upgrade guide please?
Compressions is a feature we believe should be handled by something other than propshaft, so this could was just a suggestion for a specific use case and therefore not something we want to put emphasis (which placing on the README does)

I actually considered putting this in the "Upgrading from Sprockets to Propshaft" guide, but I hesitated because even though Sprockets provided this functionality, it's still useful to people who are starting a new application with Propshaft, and those people wouldn't have any reason to look at the "Upgrading from Sprockets to Propshaft" guide.
Is there another place besides that guide and the README where this could go? Do we want to add a new document, like FAQ.md or something else? Alternatively, we could keep this in the README but replace the inline code sample with a link to this comment: https://github.com/rails/propshaft/issues/158#issuecomment-1786039189 - that would prevent this section from taking too large a percentage of the README.

When running this code in production mode with Sprockets, we get this error after the assets get digested:
6.710 NoMethodError: undefined method `config' for nil:NilClass
6.710 /app/config/initializers/precompile.rb:3:in `block in <main>'

Line 3 is: output_path = assembly.config.output_path, assembly is defined on line 2 with assembly = Rails.application.assets.
Steps to reproduce in a repeatable project:

Clone and follow the readme in https://github.com/nickjj/docker-rails-example
Add this to config/initializers/precompile.rb:

Rake::Task["assets:precompile"].enhance do
  assembly    = Rails.application.assets
  output_path = assembly.config.output_path

  assembly.load_path.assets.each do |asset|
    asset_path      = output_path.join(asset.digested_path)
    compressed_path = output_path.join(asset.digested_path.to_s + ".gz")

    unless compressed_path.exist?
      Propshaft.logger.info "Compressing #{asset.digested_path}"

      Zlib::GzipWriter.open(compressed_path) do |gz|
        gz.mtime     = File.mtime(asset_path)
        gz.orig_name = asset_path
        gz.write IO.binread(asset_path)
      end
    end
  end
end if Rake::Task.task_defined?("assets:precompile")

In the .env file, set these env vars (they are already defined but with development settings) and docker compose build:

export COMPOSE_PROFILES=postgres,redis,web,worker,cable
export RAILS_ENV=production
export NODE_ENV=production
export RAILS_SERVE_STATIC_FILES=true

The error will happen during the build process.

When running this code in production mode with sprockets (propshaft isn't installed)

@nickjj This code is specific to Propshaft, which does not have a compression feature and should not be used in a project using Sprockets, which has that feature.

@rmacklin How about we take take a page out of Sprockets book and create a "guides" folder? Then we can move the upgrade guide to there too and create an "extending_propshaft.md" file and have this code and explanation there. Could also move the notice about the file watcher that is the readme me to there. And finally edit the readme to point to those guides.

This code is specific to Propshaft, which does not have a compression feature and should not be used in a project using Sprockets, which has that feature.

Right but code is failing on assembly    = Rails.application.assets because it's coming back as nil. Is Rails.application.assets something Propshaft adds to Rails?

If you are asking this just as a curiosity, then .assets variable is something that both Sprockets and Propshaft assign a value to during application boot. My best guess as to why you are getting a null pointer with Sprockets but it works with Propshaft, is that Sprockets sets it later than Propshaft.
You could probably use Rails to_prepare or after_initialize to fix the null pointer, but then you'd just get another error, since the object Sprockets assigns to assets does not have a load_path method.

I see. I don't want to clutter this PR with unrelated comments but Propshaft's upgrade guide mentions deleting the assets.rb initializer but my initializer had Rails.application.config.assets.paths << "/node_modules" and the Propshaft docs don't mention how to add new load paths.
I'll need to make that customization with Propshaft to be able to test this PR.

If you are using node_modules, you are probably using a bundler like webpack/esbuild.
In this cases there's not need to add node_modules to the path. Instead, simply have your bundler place the compiled assets (css/js) into app/assets/builds, and propshaft will pick them up automatically.
It's pretty much what the bundling gems (jsbundling-rails and cssbundling-rails) do.

I'm using esbuild and it's configured to place assets into /node_modules. It's important that the path doesn't change because it's a non-volume mounted location of the file system within Docker.
How can I configure Propshaft to include /node_modules as an assets path similar to sprockets?

Don’t do that. Propshaft paths do not work like Sprockets paths.
Anything you add to paths will be copied to the public/assets folder by Propshaft. I doubt you want the entirety of the node_modules folder there, as that would be thousands of files and hundreds of megabytes, and it would massively slow down the precompile.
Like I said, have your bundler, which uses node_modules folder as the source of the libs for your own js files, place the files it generates in app/assets/builds and from there propshaft will copy them to public/assets. That’s the correct workflow to integrate Propshaft with bundlers like webpack/esbuild/etc.

That said, if you really want to do that to see what happens, instead of removing the assets.rb file, place this line in it:
Rails.application.config.assets.paths.unshift Rails.root.join("node_modules").to_s

Just to make sure I'm 100% following here. Here's what I do today with sprockets and everything is working. Everything gets bundled, digested and gzipped as expected and my bundles only include my app's custom JS and CSS:

I configured esbuild to put my bundles in app/assets/builds for JS and CSS
I configured .yarnrc with --modules-folder /node_modules so that any JS dependencies I install end up in /node_modules
I configured Rails with Rails.application.config.assets.paths << "/node_modules" so that whatever tool needs this path (Rails, sprockets, etc.?) knows assets exist there and not in the relative node_modules/ directory that's the default

With Propshaft it sounds like step 1 doesn't change. Step 2 can't change because that's where I Yarn install everything to. The part I'm not clear on is step 3. The upgrade guide says to delete the initializer where this step was previously included but it has no alternative. Maybe this path configuration isn't needed at all with Propshaft and this whole concept goes away? In other words I'm good to go out of the box with my old steps 1 and 2 with Propshaft?

Correct, you don’t need step 3. Propshaft does not care about node modules. It’s esbuild responsibility to read stuff from there when compiling your files. Propshaft only cares about where your compiled files will be places and that’s the builds folder.

@nickjj Need to change the if in that code I gave you:
Rake::Task["assets:precompile"].enhance do
  # Code here
end if defined?(Rack) && Rake::Task.task_defined?("assets:precompile")

We are working on a new solution to provide compression out of the box without CDN. See the Airlock issue on the Rails 8 milestone. I think that's a better path.

Would it still be possible to provide a working initializer here in case Airlock doesn't solve this use case?
Based on the milestone it sounds like it would compress assets on the fly similar to how nginx would compress them, but the original issue for this use case was about pre-compressing them because it's more efficient. The original issue is here btw: https://github.com/rails/propshaft/issues/158

I don’t think that’ll be a concern of high enough importance for most to bother with. Airlock will only compress once per asset, though it will do so on demand. But computers are fast enough that it isn’t a concern I think most people should have to even think about.
I want to keep Propshaft as lean as possible. That includes which seeds to plant in people’s minds about what’s needed or not when reading the docs.

Ok thanks, I'll drop a request in the Rails forums to see if we can figure out debugging this almost-working-initializer for folks who plan to stick with using nginx which doesn't only compress assets once.

I understand to not include it in the readme, but maybe it would be helpful to put it in the upgrade guide in section about migrating from sprockets.
@dhh what do you think?

I think it'll all be moot because Thruster will be the default in Rails 8, and that'll provide the compression needed.

Now that Rails 8.0 is out and Propshaft is the default, can we come up with a working snippet that's documented in https://github.com/rails/propshaft/pull/161#issuecomment-1788304229? That comment and a few comments below it explain the errors it produces and I've hit a dead-end on troubleshooting it.
There are folks out there not using Thruster and would like to continue having nginx serve pre-compiled assets but still take advantage of Propshaft.


Combine canvas tests into DOM tests

tests/dom/ will contain tests for all of the classes in lib/dom.js.

@facebook-github-bot shipit


404s in browser dev console when viewing "Apps & Marketplace" for local cluster

Rancher Server Setup

Rancher version: master-head, 2e6926b
Installation option (Docker install/Helm Chart): Docker Install

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc):

Proxy/Cert Details: N/A - Docker install.

Information about the Cluster
N/A - Docker install.
Describe the bug
Some 404 messages appear in the browser's dev console when visiting "Apps & Marketplace" for the local dev cluster.
Example:
GET https://host/v1/catalog.cattle.io.clusterrepos/rancher-charts?chartName=rancher-alerting-drivers&link=icon&version=100.0.0 404 (Not Found)

To Reproduce

Run Rancher via a docker install
Login by setting up the password, etc.
In the left-hand menu, under Explore Cluster, click "local"
In the left-hand menu, click "Apps & Marketplace"
Check the dev console, you will see several 404s relating to rancher-charts

Result
404s in the dev console.
Expected Result
I expected not to find errors in the dev console. (Maybe my optimism is unfounded?)
Screenshots
Not applicable, relevant messages from the console are found above.
Additional context
No additional context.

I'm pretty sure this is because it's missing the icon in the chart as there are 4 of them and none of them have an icon in the chart.
@catastrophe-brandon Can you list the 4 of them that are in the console?

Related - https://github.com/rancher/dashboard/issues/3512#issuecomment-891554060
https://github.com/rancher/dashboard/issues/3512#issuecomment-891554809

Dev console log with IPs redacted attached, including 404s.
dev_console.log


Store attributes in dataframes

Three strategies are provided for serializing scalar Table attributes in dataframes.
"drop" will drop the attributes completely. "add_columns" will add repetitive columns that contain the attribute. "attrs" will store the attribute in df.attrs, a (hashable) metadata dictionary.

Fixes #56.

Er, fixed #55.


Support for generated files

Is it possible to have ko invoke commands to generate files, notably protoc? This seems to be a very common thing to do with go services.

It's possible, but I think it would be against ko's (and go's) philosophy, so we'd probably need a very strong motivation to make it part of ko proper.
The usual recommendation is to use go generate to generate files, then go build etc to build them, and I think ko should follow that pattern in place of go build. I'd be hesitant to have ko publish encompass both go generate and go build.

I understand the will to follow philosophies, but the reality is that go micro-services using protobuf definition is not an exception. GoRelease supports the pre/post hooks, are you open to a patch?

I'd much prefer to discuss an abstract design before asking you to write code for us to review. But even then, I don't think I'd be open to accepting a proposal to add pre/post hooks into ko without a stronger motivation than has been put forward so far.
Is there a reason go generate && ko publish is not suitable for your use case?

GoRelease supports the pre/post hooks, are you open to a patch?

I think the ideal end-state is that make it possible (or the default) to support everything goreleaser does. Right now, it's unclear to me what kind of relationship makes the most sense between the projects. I don't think it make sense to just vendor all of goreleaser or reimplement everything, but there may be some way to make this more pluggable...

My $0.02 tl;dr is that we're based on Go idioms, not goreleaser.
The overarching Go guidance around codegen (for better or worse) is to check it in.  Things like go {get,install} or even just vendoring libraries simply won't work if you don't check in the codegen.
The real place where I see this being useful is more inner-loop development where juggling tools is annoying, but generally things like proto definitions (or K8s API types) change orders of magnitude less often than the surrounding code.
Personally, from a security standpoint I really like the property that ko resolve doesn't execute any user-sourced code, which will become an increasingly important property as folks start to reason more about hermetic builds (and what should/shouldn't be run in the network jail).

On inner-loop development, Skaffold supports ko natively and provides lifecycle hooks.
By combining these hooks with profiles, you can run go generate locally as part of the inner dev loop, while skipping this step in a CI build (so the CI build uses only checked-in files).
An example config to achieve this:
apiVersion: skaffold/v2beta26
kind: Config
build:
  artifacts:
  - image: go-generate-build-hook-via-profile
    ko: {}
profiles:
- name: inner-loop
  activation:
  - command: debug
  - command: dev
  - command: run
  patches:
  - op: add
    path: /build/artifacts/0/hooks
    value:
      before:
      - command: ["go", "generate", "./..."]

With this config, Skaffold executes go generate when you run commands that are aimed at local development: skaffold run, skaffold dev, or skaffold debug.
Other commands that are aimed at CI build scenarios, such as skaffold build, skip the go generate step.

I'm liking this pattern of skaffold supporting use cases that feel inappropriate for ko ❤


Update dependency org.apache.cxf:cxf-rt-ws-addr to v3.3.2

This PR contains the following updates:

Package
Update
Change
References

org.apache.cxf:cxf-rt-ws-addr
patch
3.3.1 -> 3.3.2
homepage

Renovate configuration
:date: Schedule: At any time (no schedule defined).
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR is stale, or if you modify the PR title to begin with "rebase!".
:no_bell: Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

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


[stable/nats] api version of template in helm repo outdated

Describe the bug
I'm unable to proceed with installation of a default stable/nats (statefulset) due to outdated API version for Statefulset definition as per error message. Possibly not supporting a higher Kubernetes version (1.16) for the api definition.
Version of Helm and Kubernetes:
Helm version: v2.11.0
Kubernetes version: v1.16.1
Which chart:
stable/nats
What happened:
During helm install of NATS, I'm getting the following error:
$ helm install stable/nats
Error: validation failed: unable to recognize "": no matches for kind "StatefulSet" in version "apps/v1beta2"

How to reproduce it (as minimally and precisely as possible):
I'm able to deploy successfully using a lower Kubernetes version (1.14). I think the templates from the uploaded helm charts in stable/nats are outdated and needs to be updated. Please refer to the depricated APIs as of Kubernetes 1.16 (https://kubernetes.io/blog/2019/07/18/api-deprecations-in-1-16/)

Hi @mgmm13
What version of the NATS chart are you using? That API version was quite a long time ago (see https://github.com/helm/charts/pull/17282)
You can use the command below to update your charts:
$ helm repo update

@juan131 you're right, did that command and it proceeded. I totally forgot that. Thanks!


Improve examples docs for helm autodiscovery

Description
Provide examples for the new ignore dependencies/containers in helm autodiscovery

Always great to have more documentation, thank


fix: publish esm modules and TS types

Description
As in title: publish esm modules and TS types - update prepublishOnly script.

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 93.347%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1443

Relevant Lines:
1473

💛  - Coveralls


Improve nested swipers support and noSwiping logic. Added new demo for nested horizontal swipers.

I've improved Isaac Strack's noSwiping logic and it's now possible to have nested horizontal (I guess vertical too) swipers. There are two main changes:

when you touch somewhere, the most nested swiper grabs this event, it was ambigous previously,
noSwipingClass is checked by swiper only on it's own slides, wrapper and container. Previously it checked all nested slides, wrappers and containters which was faulty.

I've attached a new demo that shows this clearly. Play with this, then comment out current 2.1 version JS file and use development JS to see improvements.

Closing as new Swiper 3 released with different API and rewritten core


Beacon wording

What changed

Fixed some of the semantics issues in the beacon model, form, and templates
Related to #274

What's needed

Full column name changes for model (requires migration), with related form and template changes

Issues

should fully close #261 & #280

[added by Ben to trigger the issue closes]

closes #261
closes #280

Screencap

What's the difference between this and #274? Model changes?

@shellicious check the diff for more specifics, but yes, changes to model, form, views, and some template stuff.

You did the front end stuff, I updated the backend that didn't require a migration, then made sure the tests still work

:+1:

Does this close #280 as well? Can you attach a screenshot of the relevant part of conductor?

@bsmithgall funny story: this doesn't actually close #280 yet!
Working on that now...

:+1:

@hamhands will this address #316?

I mean, this is a larger test we may need: do all the routes work? It's
less a test of user actions and more a test that everything works when we
make a change.
On Thu, Aug 27, 2015 at 9:33 PM Ben Smithgall<EMAIL_ADDRESS>wrote:

@hamhands https://github.com/hamhands will this address #316
https://github.com/codeforamerica/pittsburgh-purchasing-suite/issues/316
?
—
Reply to this email directly or view it on GitHub
https://github.com/codeforamerica/pittsburgh-purchasing-suite/pull/296#issuecomment-135600613
.

@hamhands go ahead and write it, it should just involve a test that renders all of the appropriate pages.

That would probably mean a new test for Beacon and a new one for Conductor, though I'm pretty sure that this behavior is already covered by existing tests.

@bsmithgall @shellicious ok this should be done now if you want to murrrrrrrge!


CRT filter not working for NES games

The CRT filter causes significant audio, graphical, and gameplay issues. The 4:3 and Pixel Perfect displays seem to work with no issue.

+1 same issue, NESc games are unplayable in CRT mode

Yes also noticed this issue

It's comes from your installation. You should have created a text file for the hsqs too. Instead of dropping the hsqs directly onto Hakchi2, you would add a dummy file so that hakchi creates a new "game", upload the hsqs to /var/lib/hakchi/firmware/, and change the command line to /bin/hsqs /var/lib/hakchi/firmware/name_of_your.hsqs, be sure to update the command to reflect the actual filename.


Impossible to use Boom library for Hapi

I tried to generate http error by means Boom. It should call into apolloOptions as a function. Unfortunately, Boom error was catch by getApolloOptions and converted to error with status code 500.
Could you add support for using custom errors?

Here is example how to fix it.
https://github.com/rusfearuth/apollo-server/commit/9c721cd440b163f955280d527dea43e270b3a3f7

initially i tought that this is very poor solution as this will handle very specific cases.
but then i realized boom is part of hapi error handling, so it's looks good IMO,
would you mind rebase it upon the mono repo and open a PR?

well looks like @rusfearuth is not responding..
anyone else is interested in this?

I'm needing the same thing. I'll take this up.

Well, I spoke too early...
Based on how the mono repo was refactored, the options function still can't throw a Boom because it will get caught up in runHttpQuery. (https://github.com/apollostack/graphql-server/blob/master/packages/graphql-server-core/src/runHttpQuery.ts#L36)
It would require some duplication of code to pre-execute the options function in the runHttpQueryWrapper in the hapi package (https://github.com/apollostack/graphql-server/blob/master/packages/graphql-server-hapi/src/hapiApollo.ts#L22) and then sending the finalized options object to runHttpQuery (or throwing the Boom).
I was thinking we could have handled a Boom response from the actual execution of a request against the compiled schema, but the execute function from the graphql package only resolves and outputs an ExecutionResult, which is just { data: {}, errors: [] }.
If we want to go the code duplication route, I think I have the code completed for that, otherwise I suspect this request should be closed.

hi @PizzaBrandon since im not that familiar with Boom,
can you please submit a failing test so i can dig deeper?

I was coding by inspection before and don't have a failing test at this time. I'll see if I can pull something together by the end of this week, otherwise I think this issue can probably be closed based on the above analysis.

alright cool thanks @PizzaBrandon  :)

@PizzaBrandon @DxCx Hey just snooping around, any update on this?

Closing this based on comment from @PizzaBrandon on Jan 27.


perf,viz: remove subpackage yarn.lock

Where did they come from? What is their fate? Please tune in for next episode.
(Let's remove this maintenance overhead unless there are gotchas? @kumavis )

mistake or pre-dates monorepo? dont recall - seems fine to remove


flet build ipa Error - Swift Compiler Error (Xcode): No such module 'Python'

Discussed in https://github.com/flet-dev/flet/discussions/3748

Originally posted by Zeb152 July 31, 2024
Question
Error: Swift Compiler Error (Xcode): No such module 'Python'
Recently, I messed up python on my computer while I was trying to build toolchain modules (like it says in the documentation) and others for the flet build ipa command, and so I had to completely uninstall it and reinstall it using Homebrew. Python now works, but unfortunately, this caused my python interpreter to be in a different file /opt/homebrew/bin/python3 instead of whatever it was before (I believe it wasn't with Homebrew).
So, I am pretty sure that if I am able to change the file directory of where Xcode pulls python from, it will fix the error. I need to change it to opt/homebrew/bin/python3.
However, because flet doesn't build an Xcode project I am not quite sure how I could change the directory python file. Any ideas? Thanks in advance!
Code sample
No response
Error message
[09:39:07] Created Flutter bootstrap project from gh:flet-dev/flet-build-template with ref
           0.23.2 ✅
           Customized app icons and splash images ✅
[09:39:11] Generated app icons ✅
[09:39:13] Generated splash screens ✅
[09:39:18] Packaged Python app ✅
[09:40:04] Resolving dependencies...
           Downloading packages...
             collection 1.18.0 (1.19.0 available)
             fl_chart 0.65.0 (0.68.0 available)
             flutter_lints 2.0.3 (4.0.0 available)
             flutter_markdown 0.6.23 (0.7.3 available)
             http_parser 4.0.2 (4.1.0 available)
             js 0.6.7 (0.7.1 available)
             lints 2.1.1 (4.0.0 available)
             material_color_utilities 0.8.0 (0.12.0 available)
             meta 1.12.0 (1.15.0 available)
           ! package_info_plus 8.0.1 (overridden)
             sensors_plus 4.0.2 (6.0.0 available)
             sensors_plus_platform_interface 1.2.0 (2.0.0 available)
             toml 0.15.0 (0.16.0 available)
           ! wakelock_plus 1.2.7 (overridden)
             web 0.5.1 (1.0.0 available)
             web_socket_channel 2.4.5 (3.0.1 available)
           Got dependencies!
           14 packages have newer versions incompatible with dependency constraints.
           Try `flutter pub outdated` for more information.

           Archiving com.zebgames.plant...
           Updating minimum iOS deployment target to 12.0.
           Upgrading project.pbxproj
           Upgrading AppFrameworkInfo.plist
           Upgrading Podfile
           Updating project for Xcode compatibility.
           Upgrading project.pbxproj
           Upgrading Runner.xcscheme
           Automatically signing iOS for device deployment using specified development team in
           Xcode project: 6D6NPPFU98
           Running pod install...                                             10.1s
           Running Xcode build...
           Xcode archive done.                                         14.5s
           Failed to build iOS app

           Swift Compiler Error (Xcode): No such module 'Python'
           /Users/harperbledsoe/.pub-cache/hosted/pub.dev/serious_python_darwin-0.7.1/darwin/C
           lasses/SeriousPythonPlugin.swift:7:7

           Encountered error while archiving for device.

           Error building Flet app - see the log of failed command above.

------------------------------------------------------

[X] I have searched for answers to my question both in the issues and in previous discussions.

Mistake.

I had the same problem with flet build macos, see where to fix it.

@wssnail if you still having this issue, please provide complementary details.

@wssnail if you still having this issue, please provide complementary details. (full logs with --v, flet version, python version, etc)

I had the same problem with flet build macos

@wssnail if you still having this issue, please provide complementary details. (full logs with --v, flet version, python version, etc)

Everything worked fine on macOS Sonoma (version 14), but after upgrading to macOS Sequoia (version 15), flet build macos started failing with errors. Even after reinstalling Flutter and Flet, the issue persists. Here is the error message:
`
Building macOS bund  694.9s
--- xcodebuild: WARNING: Using the first of multiple matching destinations:
{ platform:macOS, arch:arm64, id:00008112-001241E00C06201E, name:My Mac }
{ platform:macOS, arch:x86_64, id:00008112-001241E00C06201E, name:My Mac }
/private/var/folders/qq/h1x1qc197w9f2yxfgkf2vxmw0000gn/T/flet_flutter_build_rXKqj1Swx5/build/macos/Build/Products/Release/XCFrameworkIntermediates/serious_python_darwin/Headers/module.modulemap:2:21: error: umbrella header 'Python.h' not found
umbrella header "Python.h"
^
/Users/alphabet/.pub-cache/hosted/pub.dev/serious_python_darwin-0.7.1/darwin/Classes/SeriousPythonPlugin.swift:8:8: error: could not build Objective-C module 'Python'
import Python
^
warning: Run script build phase 'Run Script' will be run during every build because it does not specify any outputs. To address this issue, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'Flutter Assemble' from project 'Runner')
** BUILD FAILED **
`
System: macos 15.0
Python: 3.10
Flutter : (Channel stable, 3.24.3, on macOS 15.0 24A335 darwin-arm64, locale
zh-Hans-CN)
Flet: 0.24
Xcode: 16.0 (15)

Try building with Flet pre-release.


Rendering goes bonkers with headless and wdisplays

Steps to reproduce:

swaymsg create_output
Run wdisplays
Move the headless display and "Apply"

Another issue with headless outputs: image capture is messed up (images contain two copies of the headless output): https://l.sr.ht/04m1.jpg

The following patch fixes the flickering on the main output when wdisplays is run:
diff --git a/backend/drm/renderer.c b/backend/drm/renderer.c
index 82077617..3e8079ca 100644
--- a/backend/drm/renderer.c
+++ b/backend/drm/renderer.c
@@ -127,7 +127,13 @@ static void finish_drm_surface(struct wlr_drm_surface *surf) {

 bool drm_surface_make_current(struct wlr_drm_surface *surf,
                int *buffer_damage) {
-       return wlr_egl_make_current(&surf->renderer->egl, surf->egl, buffer_damage);
+       if(!wlr_egl_make_current(&surf->renderer->egl, surf->egl, buffer_damage)) {
+               return false;
+       }
+
+       glBindFramebuffer(GL_FRAMEBUFFER, 0);
+
+       return true;
 }

 bool export_drm_bo(struct gbm_bo *bo, struct wlr_dmabuf_attributes *attribs) {

There still remains an issue that wdisplays doesn't exit when its window is closed, leaving the display name overlay on all outputs. It needs to be killed to go away. Running wdisplays again after killing it works but it doesn't show the display contents like before.

Hmm, weird, we're supposed to already reset the FB here: https://github.com/swaywm/wlroots/blob/master/backend/headless/output.c#L133

Ah, maybe swap the wlr_egl_make_current and the glBindFramebuffer calls?

Ah, maybe swap the wlr_egl_make_current and the glBindFramebuffer calls?

Doesn't do anything. :)

Maybe the problem is that rendering to different outputs can happen concurrently? If I do this:
diff --git a/types/wlr_output.c b/types/wlr_output.c
index 3316653a..24e779a6 100644
--- a/types/wlr_output.c
+++ b/types/wlr_output.c
@@ -436,6 +436,8 @@ static void output_state_clear_buffer(struct wlr_output_state *state) {
 }

 bool wlr_output_attach_render(struct wlr_output *output, int *buffer_age) {
+       printf("Attach render %p\n", output);
+
        if (!output->impl->attach_render(output, buffer_age)) {
                return false;
        }
@@ -555,6 +557,8 @@ bool wlr_output_test(struct wlr_output *output) {
 }

 bool wlr_output_commit(struct wlr_output *output) {
+       printf("Commit %p\n", output);
+
        if (!output_basic_test(output)) {
                wlr_log(WLR_ERROR, "Basic output test failed");
                return false;

and then run sway, I get some instances of attach_render being called twice in a row, like this:
Attach render 0x556c13a1abb0
Attach render 0x556c13848280
Commit 0x556c13848280
Attach render 0x556c13848280
Commit 0x556c13848280
Attach render 0x556c13a1abb0
Commit 0x556c13a1abb0

Can you add a log in wlr_output_rollback too?
Rendering can't happen concurrently, that would be a Sway bug.

Yes, indeed rollback is called before attach.

Running wf-recorder or wayvnc on the headless display also causes flickering on the display connected to HDMI, so that's most likely triggered by wlr-screencopy

Running with apitrace, I can see that the glFramebufferBind and the context is sometimes left hanging. Example:
133653 eglMakeCurrent(dpy = 0x55563f0135b0, draw = NULL, read = NULL, ctx = 0x55563f01c4b0) = EGL_TRUE
133654 glBindFramebuffer(target = GL_FRAMEBUFFER, framebuffer = 301)
133655 eglGetCurrentContext() = 0x55563f01c4b0
133656 glGetIntegerv(pname = GL_IMPLEMENTATION_COLOR_READ_FORMAT, params = &6408)
133657 glGetIntegerv(pname = GL_IMPLEMENTATION_COLOR_READ_TYPE, params = &5121)
133659 eglMakeCurrent(dpy = 0x55563f0135b0, draw = 0x55563fa80be0, read = 0x55563fa80be0, ctx = 0x55563f01c4b0) = EGL_TRUE
133660 eglQuerySurface(dpy = 0x55563f0135b0, surface = 0x55563fa80be0, attribute = EGL_BUFFER_AGE_KHR, value = &3) = EGL_TRUE
133661 eglGetCurrentContext() = 0x55563f01c4b0
133662 glViewport(x = 0, y = 0, width = 2560, height = 1440)
133663 glEnable(cap = GL_BLEND)
133664 glBlendFunc(sfactor = GL_ONE, dfactor = GL_ONE_MINUS_SRC_ALPHA)

The virtual output is 1080p, so that second eglMakeCurrent followed by glViewport with different dimensions means that a different output is suddenly being targeted.
It is perhaps a point of interest that  glGetIntegerv is a result of wlr_output_preferred_read_format which is called from screencopy when a client requests a new frame.

Ahh, I figured it out: https://github.com/swaywm/wlroots/blob/master/types/wlr_output.c#L451


Proposal: descriptive env var name for GitHub PAT

Proposing a new feature 👩💻
How about a more descriptive environment variable for the GitHub access token, for example, DEBGET_GITHUB_API_TOKEN, similarly to the Homebrew one?
Alternatively, an env var like GITHUB_AUTH_TOKEN or GITHUB_API_TOKEN, commonly used by other tools and possibly present in the environment already, would minimize the number of required tokens and env vars (they might have different scopes though).
Reasoning
If Gitlab, Codeberg, etc. PAT support is to be added in the future, it would require new env vars. Having them uniformly named is nice to have.
Caveats
Simply changing behavior to a new one would introduce breaking change for existing users. Checking both new and old env vars for existence can prevent that.

Having a distinct name allows users to chose not to put all their keys in one basket should they wish to have nuanced permissions for example.
They are at liberty to
export GH_TOKEN=$DEBGET_TOKEN
export GITHUB_AUTH_TOKEN=$GH_TOKEN

if they wish.  Everyone using the same ENV is a two-edged sword and where it impacts keys and permissions the default behaviour should be towards supporting and encouraging granularity and specificity.


[FR]: repin command

What is the current behavior?
JavaScript
After changing package.json, users must remember to bazel run -- @pnpm --dir $PWD install or else translate_pnpm_lock uses stale information from the pnpm-lock.yaml file. There's a hacky thing https://github.com/aspect-build/rules_js/blob/main/docs/pnpm.md#update_pnpm_lock that can automate it but I think we killed that for bzlmod / rules_js2 right @jbedard ?
Python
I added pip-compile as a write_source_files-style test that the requirements-lock.txt file is up-to-date. However it can only check on the current platform. It prints a bazel run command when the requirements need to be re-pinned.
Rust
Developers get an error when Cargo.Bazel.lock is out-of-date.
The current `lockfile` is out of date for 'crate_index'. Please re-run bazel using `CARGO_BAZEL_REPIN=true` if this is expected and the lockfile should be updated.

Java
https://github.com/bazelbuild/rules_jvm_external/tree/6.0?tab=readme-ov-file#requiring-lock-file-repinning-when-the-list-of-artifacts-changes

It can be easy to forget to update the maven_install.json lock file when updating artifacts in a maven_install. Normally, rules_jvm_external will print a warning to the console and continue the build when this happens

Go
Under bzlmod, rules_go reads the go.sum file to get integrity hashes. After changing go.mod they're expected to bazel run @go_sdk//:bin/go -- mod tidy
Describe the feature
It's a PITA that every language has a different setup and instructions for developers. Aspect CLI could give one DX on top of this variability, like aspect repin, which would take any changes to any third-party dependency listing and update the pinned/generated code.

update_pnpm_lock runs pnpm import to convert yarn or npm to pnpm-lock, not pnpm install. But pnpm import sounds like another use case for aspect repin? 👍

With bzlmod update_pnpm_lock can't reload the lockfile after updating it, so it must fail the build which then needs to be re-run.  With rules_js v2 workspace + bzlmod were just aligned to require reloading (https://github.com/aspect-build/rules_js/pull/1701).


Add option of auto billing

There is need to auto bill clients and have them pay before service. For instance immediately a Visit is started for a client then we can auto bill them

hii sthaiya,
i am trying to create patient list but i am getting unauthorized you are not authorized to access this db how tom fix this?

@chaitanya-y your issue is unrelated (see your actual issue) - try to keep conversations within issues to the actual stated issue


Unhandled stream error.

I'm trying to find an accessibility plugin that actually works. I have gulp experience, so it's not anything obvious.
[18:00:50] Starting 'a11y'...
stream.js:94
      throw er; // Unhandled stream error in pipe.
            ^
a11y: Command failed: /Users/X/Dropbox/Projects/XXX/Frontend/node_modules/gulp-a11y/node_modules/a11y/node_modules/phantomjs/lib/phantom/bin/phantomjs /Users/X/Dropbox/Projects/XXX/Frontend/node_modules/gulp-a11y/node_modules/a11y/audits.js {"delay":1,"url":"file:///Users/X/Dropbox/Projects/XXX/Frontend/dist/layout.html","width":1024,"height":768} --ignore-ssl-errors=true --ssl-protocol=tlsv1 --local-to-remote-url-access=true
Audit failed

Node v0.12.3

same here

Project seems dead, so closing comment. Shame.


Dev devr2 x merge

Do not squash, history log is required for smooth merge with dev

Do not squash, history log is required for smooth merge with dev


Fixed Small Typo in README

bot would login as guest if I used user, but when I changed it to email, it worked. it's also stated as email in the docs https://github.com/goto-bus-stop/miniplug/blob/master/docs/API.md#mp--miniplugopts

Oops! Thank you!


OS X support in new CMake build system

The current state of the new CMake build system doesn't work on OS X. There are a few platform-specific factors causing it.
I'm an OS X user and Homebrew maintainer and am working on getting it to build there, following up on https://github.com/Homebrew/legacy-homebrew/issues/44047#issuecomment-215642197. If I can get it running, I'll supply a PR for this, but wanted to get the bug report in place first, and get a little feedback.
See also #89.
Issues

/bin/uname vs /usr/bin/uname – on OS X, it's /usr/bin/uname, but the CMakeLists is hardcoded to use /bin/uname (may be same as #87)
No lib64 – OS X does not have separate lib and lib64 directories (at least on 10.9+), so 64-bit libraries should be installed in lib there; currently they're going to lib64.
Warning on unset Mac-specific policy CMP0042
Unresolved symbols linked dynamically at run time
Similar deferred linkage to OpenSSL when eventing is enabled (see #89)
Non-portable introspection of libssl.so (see #89)

Linking unresolved symbols at run time
Openwsman provides multiple DLLs, and the way they're structured and linked currently, many depend on each other and have symbols that are left unresolved at compile + link time. Looks like these are intended to defer the resolution to program run time, and a program using them must link against multiple Openwsman libs to get all the symbols resolved. CMake supports this, but it's not the default behavior on OS X. (Maybe it is on Linux.)
Defining a library as MODULE instead of SHARED in the add_library arguments supports this delayed resolution on OS X. But CMake doesn't permit cyclical dependencies between dynamic libraries. And there's a dependency cycle in the openwsman libraries. This may be a bit tricky to fix.
I was able to get it to build by manually adding the deferred-symbol-resolution linker flags instead of relying on CMake's MODULE support using the following target properties.
set_target_properties( ${WSMAN_CLIENTPP_PKG} PROPERTIES LINK_FLAGS "-undefined dynamic_lookup")

But that's kind of a hack, and may not work with all compilers on OS X.
Are the cyclical dependencies in the dylibs intentional?
Work in progress
Working on this at https://github.com/apjanke/openwsman/tree/osx-cmake-support.
I've got the uname, lib64, and policy issues handled. Waiting to tackle the deferred linkage until I hear back about whether the cyclical dependencies are intentional and necessary.

Bug #87 has the hard coded /bin/uname issue, but also the C_ALLOCA failure: as explained over there, cmake generates an incorrect wsman_config.h:
/* Define to 1 if using `alloca.c'. */
#if
#define C_ALLOCA 1
#endif
Note the lack of anything after the "#if" - more detail in bug #87. (Suggests that cmake isn't ready for prime time and that removing autoconf support is premature.)

I'd be very thankful if you provider separate PRs for the issues listed above.

The C_ALLOCA problem apparently appears if the alloca exists.

Where is the cycle in dynamic libraries ? This should be fixable by moving functions.

I cherry-picked a504592 and 6039945 from https://github.com/apjanke/openwsman/tree/osx-cmake-support to upstream/master.

@kkaempf Thanks for picking these! I guess as Homebrew maintainers (@apjanke and me), but not active users of this software, there's only so much we can do …


Class feedback: Use scatter plot?

In the ECDF examples, maybe
plt.plot(x, y, marker='.', linestyle='none');

can be replaced with
plt.scatter(x, y)

?

Absolutely :smile:.

Yes. Sometimes people like to plot ECDFs with the steps & it's easier to customize
plt.plot(x, y, marker='.', linestyle='none');

in this case

Ah, okay. Feel free to close if irrelevant. Thanks for the clarification.

Not irrelevant at all!


Asset management

Please include information about Enterprise Asset management like :

Is it supported for On-premise or not ??
If yes , please provide information about EAM On-premise.

LakshmiD365, thank you for providing feedback.  To help our team address this feedback, please provide the URL of the article this feedback applies to.

Hi sericks007,
Thank you for your response.
Below is the URL of the article I'm referring to:
https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/fin-ops/get-started/cloud-prem-comparison

@LakshmiD365, thank you! We'll look into this.

@LakshmiD365, Asset management is not supported for on-premises environments.  I've updated the documentation to reflect this.  This update will be published later today.


Use a more efficient compression method in the pipeline-cache

Currently, PipelineCache uses tar for compression. However, tar does not compress the file efficiently (almost 0), while it still takes some time to make a tar archive.
Based on my experience, the performance bottleneck of the current cache method is in the time it takes to "download" or "upload" the files. By using some level of compression such as 7z on the fastest mode, we can compress the cache and so reduce the time it takes on uploading and restoration.
For example, consider this node_modules caching. Most of this 1 min and 15 seconds is spent on "downloading" a 450 MB node_modules folder.

Another example
Here is a little benchmark I did for the compression/time of the bootstrapped Atom repository:
1.74 GB

7zip
-----
ultra 2:19 494MB
maximum 1:52 511MB
normal 1:12 528MB
fast 0:40 604MB
fastest 0:32 658MB

tar
----
tar 0:15 1.74 GB

As you see, by only spending 15s more, we can reduce the size from 1.74GB to 685MB!

Point of technical clarification that most everyone already knows: While this is probably a good enhancement, note that (AFAIK) tar doesn't have any compression capabilities itself. Depending on environment/version, having it pipe through gzip would be the "standard" method. IDK what is required to have it use a high-speed/lower compression flag.

Point of technical clarification that most everyone already knows: While this is probably a good enhancement, note that (AFAIK) tar doesn't have any compression capabilities itself. Depending on environment/version, having it pipe through gzip would be the "standard" method. IDK what is required to have it use a high-speed/lower compression flag.

I think the bottleneck is mostly compression/decompression time.

Thoughts on optimizing compression/decompression time:
(That can be optimized, too. Check out Fedora's recent look at compression performance as a case study. Zstd is really fast and space-efficient. Some benchmarks from other sources: [1] and [2]. Other than Zstd, LZ4 is interesting as it is way way fast to compress and decompress, but not as space-efficient.)
(I don't know how those FLOSS algorithms compare to 7z, but maybe the compression is arguably too aggressive and becoming severely CPU-bound rather than lightly network-bound? Worth a thought, especially if this might ultimately be LAN network usage within the same datacenter. Which is more precious, the network bandwidth or the CPU time?)

Evidence that we're waiting on compression/decompression time more than the network:
Decompression
Screenshot of "Enable system diagnostics" checkbox (click to expand)

(To reproduce these results, manually run a pipeline with the "[x] Enable system diagnostics" checkbox checked, and during cache restore you will see a lot of lines like this:x [path]. I assume this means the tar x command, for "extract".)
You can see the download progress lines are printed sandwiched in-between all of the extracting that is going on. https://dev.azure.com/DeeDeeG/b/_build/results?buildId=1009&view=logs&j=0c24d9d5-0e27-5404-37e0-91cb4d692d0c&t=ef37c6e4-1fe1-524c-2b36-45447b74650f&l=5779
Extraction apparently takes a ton of time, downloading maybe not so much.
Compression
I think compression takes a while, too. Here's a bunch of lines a [path] (I assume the "a" stands for "add"?).
https://dev.azure.com/DeeDeeG/b/_build/results?buildId=1009&view=logs&j=e2cf4b02-5697-54ad-cf7c-fc2a840d53af&t=7a5bb1d7-ddca-4fd6-90f8-e03a82bd0170&l=57610
(I was not watching closely which part took more time, adding files or uploading. If I ran again, I would try to look more closely. But anyone reading this with a pipeline using the cache@V2 task can try it out and see for themselves.)

I think the bottleneck is mostly compression/decompression time.

Thoughts on optimizing compression/decompression time:
(That can be optimized, too. Check out Fedora's recent look at compression performance as a case study. Zstd is really fast and space-efficient. Some benchmarks from other sources: [1] and [2]. Other than Zstd, LZ4 is interesting as it is way way fast to compress and decompress, but not as space-efficient.)
(I don't know how those FLOSS algorithms compare to 7z, but maybe the compression is arguably too aggressive and becoming severely CPU-bound rather than lightly network-bound? Worth a thought, especially if this might ultimately be LAN network usage within the same datacenter. Which is more precious, the network bandwidth or the CPU time?)

Evidence that we're waiting on compression/decompression time more than the network:
Decompression
Screenshot of "Enable system diagnostics" checkbox (click to expand)

(To reproduce these results, manually run a pipeline with the "[x] Enable system diagnostics" checkbox checked, and during cache restore you will see a lot of lines like this:x [path]. I assume this means the tar x command, for "extract".)
You can see the download progress lines are printed sandwiched in-between all of the extracting that is going on. https://dev.azure.com/DeeDeeG/b/_build/results?buildId=1009&view=logs&j=0c24d9d5-0e27-5404-37e0-91cb4d692d0c&t=ef37c6e4-1fe1-524c-2b36-45447b74650f&l=5779
Extraction apparently takes a ton of time, downloading maybe not so much.
Compression
I think compression takes a while, too. Here's a bunch of lines a [path] (I assume the "a" stands for "add"?).
https://dev.azure.com/DeeDeeG/b/_build/results?buildId=1009&view=logs&j=e2cf4b02-5697-54ad-cf7c-fc2a840d53af&t=7a5bb1d7-ddca-4fd6-90f8-e03a82bd0170&l=57610
(I was not watching closely which part took more time, adding files or uploading. If I ran again, I would try to look more closely. But anyone reading this with a pipeline using the cache@V2 task can try it out and see for themselves.)

@OranguTech is right that tar is usually used with any of a large variety of compression algorithms, popularly gzip or xz.
To compress with xz algorithm: tar cJf out.tar.xz [path_to_compress] (J shortflag is for xz)
To compress with gzip algorithm: tar czf out.tar.gzip [path_to_compress] (z shortflag is for gzip)

@OranguTech is right that tar is usually used with any of a large variety of compression algorithms, popularly gzip or xz.
To compress with xz algorithm: tar cJf out.tar.xz [path_to_compress] (J shortflag is for xz)
To compress with gzip algorithm: tar czf out.tar.gzip [path_to_compress] (z shortflag is for gzip)

I am confident Azure Pipelines caching already uses some decent compression. There is a reasonable possibility that it could be tuned better though, see comment above.

As I add the link to the original post, it just uses Tar which just wastes time and has no compression.

I am confident Azure Pipelines caching already uses some decent compression. There is a reasonable possibility that it could be tuned better though, see comment above.

As I add the link to the original post, it just uses Tar which just wastes time and has no compression.

But what about these statistics printed during the cache restore?
Download statistics:
Total Content: 482.9 MB
Physical Content Downloaded: 157.1 MB
Compression Saved: 325.7 MB
Local Caching Saved: 0.0 MB
Chunks Downloaded: 5,548
Nodes Downloaded: 11

The physical size downloaded is smaller than the actual content... About 1.5/5 (calculator says this is a bit under a third) of the original size.
Yes tar can make archives that aren't compressed. But it can makes compressed ones, and almost nobody uses tar without compression... Just because the word tar is involved, that doesn't mean it's being run with no compression.
Maybe there is better compression tuning that is possible. But I believe it is already compressed.

But what about these statistics printed during the cache restore?
Download statistics:
Total Content: 482.9 MB
Physical Content Downloaded: 157.1 MB
Compression Saved: 325.7 MB
Local Caching Saved: 0.0 MB
Chunks Downloaded: 5,548
Nodes Downloaded: 11

The physical size downloaded is smaller than the actual content... About 1.5/5 (calculator says this is a bit under a third) of the original size.
Yes tar can make archives that aren't compressed. But it can makes compressed ones, and almost nobody uses tar without compression... Just because the word tar is involved, that doesn't mean it's being run with no compression.
Maybe there is better compression tuning that is possible. But I believe it is already compressed.

Also it's not believable that the download takes minutes, but decompression takes zero seconds. The "download progress lines" are printed during the decompression task.
So I think the output for the cache task is misleading. It makes it look like the download is slow, but you're really seeing how long downloading and decompressing takes, combined.

Also it's not believable that the download takes minutes, but decompression takes zero seconds. The "download progress lines" are printed during the decompression task.
So I think the output for the cache task is misleading. It makes it look like the download is slow, but you're really seeing how long downloading and decompressing takes, combined.

Is there a way to manually specify the compressor's command line for given cache task?

FYI we do compression "under the hood" as part of our deduplication.

Totally agree. It'll save numerous CPU and netwok!


clarify use of profile version ID in category

Relates to #68 and discussion elsewhere. In order to ensure proper processing, the profile version is needed in category, and since all profile versions can be discovered quickly and there will generally only be a few profile versions, there doesn't seem to be a need to have the ID of the overall profile.

Also closes #22.


feat: DocString result names for Safe-DS stub results

Closes #100
Summary of Changes
Result names for stubs from Numpy docstring are now supported. Google and ReST don't support multiple results or named results, therefore they handle these a bit different:

For Google docstrings, if there are multiple results we only get the first result docstring (type & description).
For ReST we get all types, but only the last result description in the docstring.

@lars-reimann The linter failed to run
Run actions/upload-artifact@v4
Multiple search paths detected. Calculating the least common ancestor of all paths
The least common ancestor is /home/runner/work/Stub-Generator/Stub-Generator. This will be the root directory of the artifact
With the provided path, there will be 10 files uploaded
Artifact name is valid!
Root directory input is valid!
Beginning upload of artifact content to blob storage
Uploaded bytes 7[16](https://github.com/Safe-DS/Stub-Generator/actions/runs/8636183463/job/23675494721?pr=101#step:5:17)2
Finished uploading artifact content to blob storage!
SHA256 hash of uploaded artifact zip is eb6b45b691dee50ca3d7608b93b[18](https://github.com/Safe-DS/Stub-Generator/actions/runs/8636183463/job/23675494721?pr=101#step:5:19)b3b85f0a8ad228204896204a503d9caebe8
Finalizing artifact upload
Error: Failed to FinalizeArtifact: Received non-retryable error: Failed request: (403) Forbidden: Error from intermediary with HTTP status code 403 "Forbidden"

Nevermind, it runs now

@lars-reimann Could you merge this with higher priority? This is required for issue #80

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

v0.3.0
GitHub release

Your semantic-release bot :package::rocket:


.NET Standard port

[x] The library now have two targets : .NET Framework 4.5.2 (net452) and .NET Standard 2.0 (netstandard2.0)
[x] Dependency cleanup (libraries updated to target both frameworks)
[x] New project structure (documentation in docs, source project in src, test projects in tests)
[x] Travis now run the full test suite on Mono and .NET Core and both Debug and Release configuration

Mono tests are allowed to fail due to: https://bugzilla.xamarin.com/show_bug.cgi?id=59221
fixes #118

Can someone take a look? cc @Ergin008 @InbarGazit @mmallis87

Ok I'm using your @DavidRouyer code and compilation is all good however when running I get the following error:

":"Could not load type 'System.IdentityModel.Tokens.JwtSecurityTokenHandler' from assembly 'System.IdentityModel.Tokens.Jwt, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35'."}

Looks like you'll need to drop to version 4.0 based on this issue:  https://github.com/aspnet/AspNetKatana/issues/76
If you can drop that version to 4.0, I think it should work.  Let me know as well so I can grab your latest and test it out.

Are you sure you don't have mixed versions of the dependency as stated here?

@DavidRouyer I'm fairly certain, although I'm running into other issues at the moment.  Does your current branch work / tested with the call to apiClient.ConfigureJwtAuthorizationFlow()?  This is where it fails for me  using your original code.

@moraleslos Are you using .NET Core or the full framework?
ConfigureJwtAuthorizationFlow() is tested here

@DavidRouyer .NET Core 2.0:
<PropertyGroup>
  <TargetFramework>netcoreapp2.0</TargetFramework>
</PropertyGroup>

<ItemGroup>
  <PackageReference Include="Microsoft.AspNetCore.All" Version="2.0.3" />
  <PackageReference Include="Microsoft.EntityFrameworkCore.Tools" Version="2.0.1" PrivateAssets="All" />
  <PackageReference Include="Microsoft.VisualStudio.Web.CodeGeneration.Design" Version="2.0.1" PrivateAssets="All" />
</ItemGroup>

<ItemGroup>
  <DotNetCliToolReference Include="Microsoft.EntityFrameworkCore.Tools.DotNet" Version="2.0.1" />
  <DotNetCliToolReference Include="Microsoft.Extensions.SecretManager.Tools" Version="2.0.0" />
  <DotNetCliToolReference Include="Microsoft.VisualStudio.Web.CodeGeneration.Tools" Version="2.0.1" />
</ItemGroup>

@moraleslos What version of the .NET Core SDK are you using? You can type  dotnet --version

@DavidRouyer 2.1.2

@moraleslos I have the same version, have you tried to run the tests? They should work. I'll investigate when I have time

@DavidRouyer I actually just nuget your code into a local repo and added it to one of my projects  ;-)  I will test it out-- both just your solution and then integrated into my solution.  I'll keep you posted.

@moraleslos Are you using System.IdentityModel.Tokens.Jwt or is it linked by another dependency in your solution? Or is it a new project? If you're trying to use it in a existing project it can be a mixed version dependency error (check all of your dependencies), if not you can create a minimum reproducible example project on GitHub and pass it to me, it can save me some time :)

@DavidRouyer ok your tests pass.  must be something with my current project.  I'll look into it and follow up with you.  thanks!

Is there any maintainer who can take a look at this? It is there since the end of november.

I've cloned your branch and though it builds I get 8 failing tests.  Two of them are the OAuthResourceOwnerPasswordGrantTest - Not implemented.  But the other 6 are the Jwt and Legacy CreateEmbeddedConsoleViewTest, CreateEmbeddedSendingViewTest and CreateEmbeddedSigningViewTest tests.
They all fail with the error - The system cannot find the file specified pointing to the line where it calls System.Diagnostics.Process.Start(viewUrl.Url);  Do I need to reference something beyond what's included in the branch?

Some of them are integration tests (I tagged them with [Category("Manual")]) and they should launch your default browser. A few of them requires authentication, if you see a login page in the launched browser you need to log in.

After referencing the branch in my .net core mvc app I get to the point of calling the apiclient Login and get the error DocuSign.eSign.Client.ApiException: 'Error calling Login: Operation is not supported on this platform.'
LoginInformation loginInfo = authApi.Login();
This is after successfully getting the access token from the apiclient GetOAuthToken method.  Any idea why?

Which version of .NET Core are you using? Try the legacy authentication

I'm using .net core 2.  Sorry I'm still trying to figure all of this out.  What is the legacy authentication?

In the Readme, take a look at the part 'To send a signature request from a template using legacy authentication'
The error 'Operation is not supported on this platform.' comes from RestSharp (probably when you use OAuth)

Thanks.  Gave that a try and still get the same error.  I feel like giving up on the sdk and just using webclient requests for all of this stuff.  I have half of what I need working with that at this point.

Try to rollback to RestSharp 106.1.0, but it should work

Thanks @DavidRouyer for your attempt on the .Net Standard... We have published a pre-release version of the .Net Standard 2.0. Please try and let us know what you think.
https://github.com/docusign/docusign-csharp-client
https://www.nuget.org/packages/DocuSign.eSign.dll/3.0.0-rc
Regards


Issue#64 Add set and setIn operations (based on existing merge)

Add simple implementation of set and setIn by constructing a path and invoking merge, which already does all the hard stuff, checking, managing mutability, &c.

Refers to #64 (apparently the commit comment didn’t do the trick, sorry).
I’m not sure whether adding methods like this is really the right thing to do, but I followed to the model of merge. Perhaps it would be better to follow a lodash-like model of exported functions to avoid conflicts with named properties.

Generally looks good! Sorry I took so long reviewing it.
I left a couple of comments, and there's also a merge conflict to resolve.

Sorry I took even longer getting back! Added to README, changed a few random values to use JSC, not sure if that’s precisely what you meant: haven’t used JSC before (though if it’s inspired by QuickCheck, I expect to do so again).

Could this also be made to work with arrays as well? Currently it's cumbersome to update an item in an array.

It can be done with arrays; I added it to arrays. I also found some weird edge cases where the object versions didn't work properly (with nested paths); I didn't nail it down, as my main concern was making the tests pass for my added methods, but wonkiness seemed to ensue sometimes when e.g. merging a complex object with a {foo: NaN} value. The new version is a bit more straightforward (IMO) and doesn't use merge(), so it's not affected, but it could use more digging. I can't take more company time for it right now, though!

Thanks for this! :tada:


Fix GitHub ci workflow badge

See the linked GitHub issue from the previous version of the badge: https://github.com/badges/shields/issues/8671
In summary, these badges were changed in a breaking fashion such that the badges were just linking to the github issue rather than showing the data. Updating the url resolves this.
Also update the link of the badge to specify the workflow file rather than the name, which matches the new behaviour of the badge.
Let me know if I need to 'build' the generated README files or anything.

Thank you Elliot @EFord36. This is very cool and thank you for fixing this.
Merging.


hotfix: update vendor

这个 PR 实现什么功能/修复什么问题:
update vendor
是否需要 backport 到之前的 release 分支:

release/2.13

/area region
/cc @swordqiu

Codecov Report

Merging #4150 into master will decrease coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master   #4150      +/-   ##
=========================================
- Coverage    6.87%   6.86%   -0.02%
=========================================
  Files         519     519
  Lines       87546   87546
=========================================
- Hits         6021    6008      -13
- Misses      81027   81040      +13
  Partials      498     498

Flag
Coverage Δ

#aFlag
6.86% <ø> (-0.02%)
:arrow_down:

Impacted Files
Coverage Δ

pkg/cloudcommon/cronman/cronman.go
49.51% <0%> (-5.34%)
:arrow_down:

pkg/appsrv/response.go
66.15% <0%> (-3.08%)
:arrow_down:

Continue to review full report at Codecov.

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

/lgtm

/approve


Deprecation warning with Symfony 3.3's autowiring

When using the new autowiring feature of Symfony 3.3 - https://symfony.com/doc/current/service_container/3.3-di-changes.html - I get this deprecation warning:

Autowiring services based on the types they implement is deprecated since Symfony 3.3 and won't be supported in version 4.0. You should rename (or alias) the "endroid.qrcode.factory" service to "Endroid\QrCode\Factory\QrCodeFactory" instead.

I guess the referred endroid.qrcode.factory is the one that's being defined here: https://github.com/endroid/QrCode/blob/master/src/Bundle/Resources/config/services.yml#L2

For the time being, you can add this to your services.yml to get rid of the warning:
services:
    # Remove Symfony 3.3 Deprecation Notice:
    Endroid\QrCode\Factory\QrCodeFactory:
        alias: "endroid.qrcode.factory"

@endroid Maybe you can fix it like here: https://github.com/cocur/slugify/issues/179

Not relevant anymore since 3.x since the bundle now exposes services by class name.


how do use admob

I am using this template for my app. I want to use phonegap admob. I didn't found document say about it.
I try use admob in code vue file, but admob is undefined.
Please help me.

this is duplicated of https://github.com/caiobiodere/cordova-template-framework7-vue-webpack/issues/111


Queue builds up and introduces timing issues

We had a timing issue where we found a growing delay in the pose-messages that we receive through the bridge. In a ROS2-callback, we compared the reception time of the pose-message with the header.stamp and found a growing delay which made it impossible to use the data for navigation.
We have the suspicion that this was caused by the way how the data from the locator itself was queued:
The parsing function (that parses a single telegram) is called in the onReadEvent of the TCP-connection. If the parse-function (that also includes the publishers) can't keep up, new telegrams are only added to the queue, but there is no way to remove them again. As soon as we have more than one message in the queue, each time we get a new message, it will be added to end of the queue and we will parse the oldest one, but the queue length stays the same.
https://github.com/boschglobal/locator_ros_bridge/blob/6701960499b0baa0ae6bc6187c9d54c54554c068/bosch_locator_bridge/src/receiving_interface.cpp#L47
Do I interpret this behavior correctly?

Thanks for pointing this out! I could verify the described behavior by adding some artificial delay to the message parsing. The buffer fills up, but since tryToParseData is only called once per read event the buffer will never empty. I implemented a quick fix in #23.

We are using the 1.4.3 version of the locator with galactic, so we are on an older version. We are currently using our own fork with a similar fix (we just delete the whole queue after reading one message) and our delay problems are gone.

Ok, great to hear that!