text:
General GitHub Actions fixes and updates

This fixes the posting of test results as a comment for contributor PRs from forks as per https://github.com/EnricoMi/publish-unit-test-result-action?tab=readme-ov-file#support-fork-repositories-and-dependabot-branches
The actions checkout, doxygen-action, and clang-format-lint-action have been updated to the latest versions.
There is a new workflow "Test Results" that will run once it has been merged into this repo's main branch.

lgtm! :shipit:

authors: beserge stellar-aria

repo: electro-smith/libDaisy


text:
Problem with electron-packager and osxSign

[x] I have read the contribution documentation for this project.
[x] I agree to follow the code of conduct that this project follows, as appropriate.
[x] I have searched the issue tracker for an issue that matches the one I want to file, without success.

Please describe your issue:
i'm trying to sign my app on mac, as electron-packager documentation says setting osxSign:true should sign app after packaging
here is my config:
"electronPackagerConfig": {
        "name": "SomeAppName",
        "icon": "./res/icon.icns",
        "osxSign": true
      },

for example name and icon properties work correctly but setting osxSign does not do anything
btw running signing command manually works correctly too:
electron-osx-sign "./out/myapp-darwin-x64/myapp.app" --platform=darwin --type=development

can anyone suggest anything?

Console output when you run electron-forge with the environment variable DEBUG=electron-forge:*. (Instructions on how to do so here). Please include the stack trace if one exists.
electron-forge:packager packaging with options { asar: false,
  overwrite: true,
  name: 'Ublend',
  icon: './res/icon.icns',
  osxSign: true,
  afterCopy: [ [Function], [Function], [Function], [Function] ],
  afterExtract: [],
  dir: '/Users/GURO/ublend/ublend-electron-app',
  arch: 'x64',
  platform: 'darwin',
  out: '/Users/GURO/ublend/ublend-electron-app/out',
  electronVersion: '1.4.15',
  quiet: true } +9ms
  electron-forge:lifecycle Process Succeeded: Preparing to Package Application for arch: x64 +12s
  electron-forge:lifecycle Process Started: Compiling Application +2ms
  electron-forge:lifecycle Process Succeeded: Compiling Application +919ms
  electron-forge:lifecycle Process Started: Preparing native dependencies +1ms
  electron-forge:lifecycle Process Succeeded: Preparing native dependencies +104ms
  electron-forge:lifecycle Process Started: Packaging Application +0ms
  electron-forge:lifecycle Process Succeeded: Packaging Application +8s

What command line arguments are you passing?
nothing

What does your config.forge data in package.json look like?
 "config": {
    "forge": {
      "make_targets": {
        "win32": [
          "squirrel"
        ],
        "darwin": [
          "dmg","zip"
        ],
        "linux": [
          "deb",
          "rpm"
        ]
      },
      "electronPackagerConfig": {
        "name": "MyApp",
        "icon": "./res/icon.icns",
        "osxSign": true
      },
      "electronWinstallerConfig": {
        "name": ""
      },
      "electronInstallerDebian": {},
      "electronInstallerRedhat": {},
      "github_repository": {
        "owner": "",
        "name": ""
      },
      "windowsStoreConfig": {
        "packageName": ""
      }
    }
  }

Please provide either a failing minimal testcase (with a link to the code) or detailed steps to
reproduce your problem. Using electron-forge init is a good starting point, if that is not the
source of your problem.

As answered on Slack.  electron-packager hasn't been released yet with a version that supports osxSign, in the mean time use osx-sign.
/cc @malept Am I correct ^^

That's correct. In fact I found some weirdness this morning related to the API naming change, so it's probably a good thing that I didn't release yet. 😰

is this working now or is osx-sign still prefered?

The change in Packager was released in 8.6.0, which was on March 14.

Any update here?
I'm absolutely confused on how to get electron-forge to properly sign the app.

Use osxSign inside forge.config.electronPackagerConfig, see the Electron Packager API docs for details.

Okay great figured it out. For anyone else stumbling on this thread, this is what worked for me:
"osxSign": {
  "identity": "Mac Developer: NAME (ID CODE HERE)"
},

@onassar Thank you so much for clarifying this. I felt like I was taking crazy pills looking for this. I suppose that's what happens when you have a umbrella framework that is puppeteering all of these other libraries and you have to go spelunking through each library to find what configuration is required.
Anyway, your config worked great. Mine ended up looking like this:
"electronPackagerConfig": {
  "osxSign": {
    "identity": "Developer ID Application: Joshua Pinter (<my_id>)"
  }
}

For anyone who finds this looking for a package.json config example, the new key is packagerConfig, not electronPackagerConfig, e.g.:
{
  "config": {
    "forge": {
      "packagerConfig": {
        "osxSign": {
          "identity": "Developer ID Application: Company (<id>)"
        }
      }
    }
  }
}

source: gharchive/issue

authors: Guro MarshallOfSound emcmanus joshuapinter justechn malept onassar

repo: electron-userland/electron-forge

license: mit

license_type: permissive

license_source: bigquery


text:
You must depend on an EXACT version of electron not a range (^3.0.0-beta.1)

[x] I have read the contribution documentation for this project.
[x] I agree to follow the code of conduct that this project follows, as appropriate.
[x] I have searched the issue tracker for an issue that matches the one I want to file, without success.

Why this? I setup a simple project with electron-webpack & it didn't give me an error which by the way can be found here. I don't why this error is thrown :(

We currently reccomend you pin your electron dependency so that you don't run in to side effects when new versions of Electron get released.  This is historically because Electron < 2.0 didn't follow semver, there is a proposal to change how we handle this in a > 2.0 world


text:
Cannot set an icon for windows

I tried every single way that I could find and still wasn't able to change the icon of the application. This problem was occuring on windows 7 64bit. Is there any non hacky way to change it?

There's not much to go on here, so I'm just going to give some guidelines.

Make sure you're setting icon to a .ico file that is valid
Make sure that the icon file contains a square image with dimensions that are compatible with Windows 7.

authors: Tembero malept

repo: electron-userland/electron-packager


text:
Fix: relative path for notarize file

original issue: #153
original PR: #154
broken PR: #169 (thanks @DanielMcAssey )
This is fixed PR, thanks for ASAP merge (@MarshallOfSound)

FYI, it's not really broken as appPath requires an absolute path as mentioned in the docs you updated

Ok, but my (previous) PR fixing abs/rel paths.
Why this limitation (abs path), if is easy implement both paths?

But, this it works with absolute path ...and, if some want use relative path (and know about "relative to what" issue), now it will be posible.

source: gharchive/pull-request

repo: electron/notarize

license: MIT

license_source: github-api


text:
Changes needed for README.md

In vehicle/dynamics.py file, the kinematic model is implanted like this:
v = self.velocity * np.array([np.cos(self.heading), np.sin(self.heading)])
self.position += v * dt
self.heading += self.velocity * np.tan(self.action['steering']) / self.LENGTH * dt
self.velocity += self.action['acceleration'] * dt

This is for the model which is based on rear wheel position, not center of gravity position mentioned in the README file. Maybe that file needs some corrections.
You can find further explanation here.

@mhtb32 you are absolutely right, I originally implemented the rear-wheel convention and (wrongly) wrote center of gravity, and it should be fixed.
But then I changed the rendering to rotate the car around its center of gravity for simplicity, which is inconsistent. Thus, I am actually switching to the center of gravity convention on a development branch, and this will be merged soon to master.

repo: eleurent/highway-env


text:
🛑 UNER - GitLab is down

In 769863e, UNER - GitLab (https://gitlab.uner.edu.ar/users/sign_in) was down:

HTTP code: 500
Response time: 829 ms

Resolved: UNER - GitLab is back up in cd6c9fb.

repo: elfoche/monitoreo


text:
🛑 MCU - GTH is down

In 5e14e38, MCU - GTH (http://produccion.cdeluruguay.gob.ar/GTH/forms/login.jsp) was down:

HTTP code: 0
Response time: 0 ms

Resolved: MCU - GTH is back up in 76a9d71.


text:
🛑 MCU - Owncloud is down

In 67c6570, MCU - Owncloud (https://cloud.cdeluruguay.gob.ar/login?redirect_url=/apps/dashboard/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: MCU - Owncloud is back up in 47430a0 after 8 minutes.


text:
feat: Add preview and publishing functionality for manuscripts

This commit introduces new functionality that allows manuscripts to be previewed and later published. Two new mock data files were added for preview and publishing states. Corresponding tests were written to ensure the functionality works as expected. Wiremock mappings were also added to simulate different states of the manuscript (preview, published, empty).

This is passing tests for me locally but unfortunately not in CI. We always knew that we might hit issues when adding tests and seeing how CI would fair but I'm surprised that it is failing so soon.
It is hitting a timeout so perhaps we should just increase the timeout again to some silly high number and see if it will eventually pass.
The good news in this experiment is to see how easy it can be to play out some valuable end2end scenarios. Wiremock FTW.

Moving a couple of changes in here to a new PR so we can get it in now.


text:
MSID: 90679 Version: 1 DOI: 2023.08.24.554619

"msas": "Cell Biology"
"msid": "90679"
"preprintDoi": "10.1101/2023.08.24.554619"
"Reviewed Preprint posted": "2023-10-17"
"Sent for peer review": "2023-07-31"
"Posted to bioRxiv": "2023-08-26" (link: "Go to bioRxiv": "https://www.biorxiv.org/content/10.1101/2023.08.24.554619v2/")
[PLACE PDF URL HERE WHEN AVAILABLE] See step 7
Step 1. Inform bioRxiv
Who can help: @QueenKraken, @nlisgo, @scottaubrey

[x] Manuscript is in data hub index (https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=90679)

Step 2. Create preview of manuscript
Who can help: @fred-atherden, @nlisgo, @scottaubrey

[ ] Manuscript is available for preview (https://prod--epp.elifesciences.org/preview/90679/v1)

[ ] Trigger import for staging: https://prod--epp.elifesciences.org/import
[ ] Sync data folder with s3://prod-elife-epp-data/data
[ ] Trigger import for staging: https://staging--epp.elifesciences.org/import
[ ] Sync data folder with s3://staging-elife-epp-data/data
[ ] Pull request created to enhanced-preprint-data
[ ] Post link to pull request below

Pull request: [PLACE LINK TO PULL REQUEST HERE]
Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-manuscript
Step 3: Awaiting public reviews and QC
Who can help: Production team

[ ] QC passed or QC not needed

Who can help: Editorial team

[x] Public reviews available on sciety (https://sciety.org/articles/activity/10.1101/2023.08.24.554619)
[x] Manuscript and editor details at the top of this issue (Supplied by Editorial team)
[x] Reviews returned by EPP - https://prod--epp.elifesciences.org/api/reviewed-preprints/90679/v1/reviews

Example
"msas": "Genetics and Genomics", "Neuroscience"
"msid": "84628"
"version": "1"
"preprintDoi": "10.1101/2022.10.28.514241"
"articleType": "Reviewed Preprint"
"status": "Published from the original preprint after peer review and assessment by eLife."

"Reviewed Preprint posted": "2023-01-02"
"Sent for peer review": "2022-10-28"
"Posted to bioRxiv": "2022-11-21" (link: "Go to bioRxiv": "https://www.biorxiv.org/content/10.1101/2022.10.28.514241v1")

Editors:
Reviewing Editor
Michael B Eisen
University of California, Berkeley, United States
Senior Editor
Michael B Eisen
University of California, Berkeley, United States

Step 4: Modify manuscripts.json (no PDF)

[ ] Reviewed preprint is published to EPP (https://elifesciences.org/reviewed-preprints/90679)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[ ] Request that a doi be registered

[ ] Post link to #enhanced-preprint comment below

Pull request: [PLACE LINK TO PULL REQUEST HERE]
#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]

Instructions to modify manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/publish-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/334/files
Once the pull request is merged in it should be available a few minutes later.

Request that a doi
Post the following in #enhanced-preprint:
@Fred can you register a doi for https://elifesciences.org/reviewed-preprints/90679

Step 5: Awaiting search reindex

[ ] Reviewed preprint is avaliable on journal homepage (https://elifesciences.org)

The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.

Additional info
If needed, the jenkins pipeline to reindex search can be triggered sooner.
https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 6: Published! Request PDF generation

[ ] Post the link to the PDF url at the top of the issue

[ ] Post link to #enhanced-preprint comment below

#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]
Post the following to the #enhanced-preprint on slack:
@Ryan Dix-Peek please can you generate a PDF for https://elifesciences.org/reviewed-preprints/90679

Step 7: Introduce PDF to data folder and git repo

[ ] PDF is avaliable at https://github.com/elifesciences/enhanced-preprints-data/raw/master/data/90679/v1/90679-v1.pdf

Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-pdf
Step 8: Add PDF url to manuscripts.json

[ ] Reviewed preprint PDF is available for download (https://prod--epp.elifesciences.org/reviewed-preprints/90679)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[PLACE LINK TO PULL REQUEST HERE]

Instructions to add PDF url to manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/add-pdf-url-to-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/397/files
Once the pull request is merged in it should be available a few minutes later.

Step 9: Done!

[ ] Kettle is on!

Need to ask authors to add affiliation for an author

Authors have posted a new version - we need to wait for it to be processed by bioRxiv

@acollings, please could you move the reviews over to the v2 version of the preprint? Many thanks

@fred-atherden, done!

Full text available, but the MECA package is not:
curl 'https://api.biorxiv.org/meca_index/elife/all/2023.08.24.554619' | jq
{
  "status": [
    {
      "count": 1,
      "messages": "ok"
    }
  ],
  "results": [
    {
      "msid": "554619",
      "tdm_doi": "10.1101/2023.08.24.554619",
      "ms_version": "1",
      "filedate": "2023-07-14",
      "tdm_path": "s3://transfers-elife/biorxiv_Current_Content/August_2023/28_Aug_23_Batch_1717/6433c1a2-6ef4-1014-ac9e-9901b68c55fc.meca",
      "transfer_type": "api"
    }
  ]
}

Need to check again later/tomorrow

MECA available at s3://transfers-elife/biorxiv_Current_Content/October_2023/27_Oct_23_Batch_1777/bc339cf1-71f4-1014-8346-c97a656b707f.meca

V2 is loaded. This is ready to check.

authors: acollings fred-atherden naushinthomson nlisgo

repo: elifesciences/enhanced-preprints-import


text:
MSID: 93429 Version: 1 DOI: 2023.02.28.530483

"msas": "Genetics and Genomics"
"msid": "93429"
"preprintDoi": "10.1101/2023.02.28.530483"
"Reviewed Preprint posted": "2023-12-15"
"Sent for peer review": "2023-10-18"
"Posted to bioRxiv": "2023-10-31" (link: "Go to bioRxiv": "https://www.biorxiv.org/content/10.1101/2023.02.28.530483v2/")
[PLACE PDF URL HERE WHEN AVAILABLE] See step 7
Step 1. Inform bioRxiv
Who can help: @QueenKraken, @nlisgo, @scottaubrey

[x] Manuscript is in data hub index (https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=93429)

Step 2. Create preview of manuscript
Who can help: @fred-atherden, @nlisgo, @scottaubrey

[ ] Manuscript is available for preview (https://prod--epp.elifesciences.org/preview/93429/v1)

[ ] Trigger import for staging: https://prod--epp.elifesciences.org/import
[ ] Sync data folder with s3://prod-elife-epp-data/data
[ ] Trigger import for staging: https://staging--epp.elifesciences.org/import
[ ] Sync data folder with s3://staging-elife-epp-data/data
[ ] Pull request created to enhanced-preprint-data
[ ] Post link to pull request below

Pull request: [PLACE LINK TO PULL REQUEST HERE]
Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-manuscript
Step 3: Awaiting public reviews and QC
Who can help: Production team

[ ] QC passed or QC not needed

Who can help: Editorial team

[x] Public reviews available on sciety (https://sciety.org/articles/activity/10.1101/2023.02.28.530483)
[x] Manuscript and editor details at the top of this issue (Supplied by Editorial team)
[ ] Reviews returned by EPP - https://prod--epp.elifesciences.org/api/reviewed-preprints/93429/v1/reviews

Example
"msas": "Genetics and Genomics", "Neuroscience"
"msid": "84628"
"version": "1"
"preprintDoi": "10.1101/2022.10.28.514241"
"articleType": "Reviewed Preprint"
"status": "Published from the original preprint after peer review and assessment by eLife."

"Reviewed Preprint posted": "2023-01-02"
"Sent for peer review": "2022-10-28"
"Posted to bioRxiv": "2022-11-21" (link: "Go to bioRxiv": "https://www.biorxiv.org/content/10.1101/2022.10.28.514241v1")

Editors:
Reviewing Editor
Michael B Eisen
University of California, Berkeley, United States
Senior Editor
Michael B Eisen
University of California, Berkeley, United States

Step 4: Modify manuscripts.json (no PDF)

[ ] Reviewed preprint is published to EPP (https://elifesciences.org/reviewed-preprints/93429)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[ ] Request that a doi be registered

[ ] Post link to #enhanced-preprint comment below

Pull request: [PLACE LINK TO PULL REQUEST HERE]
#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]

Instructions to modify manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/publish-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/334/files
Once the pull request is merged in it should be available a few minutes later.

Request that a doi
Post the following in #enhanced-preprint:
@Fred can you register a doi for https://elifesciences.org/reviewed-preprints/93429

Step 5: Awaiting search reindex

[ ] Reviewed preprint is avaliable on journal homepage (https://elifesciences.org)

The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.

Additional info
If needed, the jenkins pipeline to reindex search can be triggered sooner.
https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 6: Published! Request PDF generation

[ ] Post the link to the PDF url at the top of the issue

[ ] Post link to #enhanced-preprint comment below

#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]
Post the following to the #enhanced-preprint on slack:
@Ryan Dix-Peek please can you generate a PDF for https://elifesciences.org/reviewed-preprints/93429

Step 7: Introduce PDF to data folder and git repo

[ ] PDF is avaliable at https://github.com/elifesciences/enhanced-preprints-data/raw/master/data/93429/v1/93429-v1.pdf

Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-pdf
Step 8: Add PDF url to manuscripts.json

[ ] Reviewed preprint PDF is available for download (https://prod--epp.elifesciences.org/reviewed-preprints/93429)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[PLACE LINK TO PULL REQUEST HERE]

Instructions to add PDF url to manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/add-pdf-url-to-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/397/files
Once the pull request is merged in it should be available a few minutes later.

Step 9: Done!

[ ] Kettle is on!

The figure quality is poor, but not poor enough to stop publication IMO.
Lots of missing information from the references, but this is down to various factors (weird source content from the authors, issues in either Encoda or EPP)

authors: fred-atherden nlisgo


text:
component bazaar

It would be great if user defined components could be shared by the community. A first starting point could be to share ideas for components in github discussions and and a procedure to make them publicly available e.g. in a separate project.

see #375

Good idea. I have made a hierarchy navigation component using justpy and a
small functional wrapper I wrote on top of justpy. Would be happy to share
:).
On Sat, May 7, 2022 at 4:20 PM Wolfgang Fahl @.***>
wrote:

see #375 https://github.com/elimintz/justpy/discussions/375
—
Reply to this email directly, view it on GitHub
https://github.com/elimintz/justpy/issues/372#issuecomment-1120186048,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AF5DLBIDGMNF7EDM7SU5YL3VIZDITANCNFSM5U3K7KIQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

@sandeep-gh  - great - for a start just open a dicussion item and post your source code there. if we get enough such components we might start creating a special webpage for such components or a portal as i did for flask bootstrap features see: http://fb4demo.bitplan.com/.
I think the current wiki documentation approach in the tutorial could be improved in this respect.

@WolfgangFahl, Need to polish/cleanup somewhat more. Will share soon.

see http://jpdemo.bitplan.com/ for a first version of an online demo of some of the examples which could be extended to a component bazaar

authors: WolfgangFahl sandeep-gh

repo: elimintz/justpy


text:
Make .parse_html more useful?

Hi
I find the parse_html method useful for one time conversion of existing html  to code. But even then, it requires quite some work with adding id's and then using name_dict to hook up event handlers. Would it be possible to parse event handlers (like @click) in the html and hook them automatically to event handlers in code?
'''
html='<div @click="do_something/>'
def so_something(...):
...
c = jp.parse_html(html)
'''

Hi,
That is a good idea. I have been thinking about this also. I will add in a future version.

Cool! Thx

authors: elimintz mjmare


text:
Update readme with node package installation instructions.

This might be fairly obvious, since you get an error on start without
this step, it's probably better to include it.

Thank you and welcome @marcdel, I agree this is a good step to include 👍

authors: doomspork marcdel

repo: elixirschool/extracurricular


text:
Installer and admin section should discuss GZIp compression more thoroughly

During installation the ElkArte 1.1.0 Beta1 installer offers / suggests to enable GZip compression on the web application layer. This will often make sense when the web server and other intermediaries close to the web application (reverse proxy server, load balancer, smart firewalls / traffic filters) do not compress content on their own.
However, such intermediaries will often enable GZip compression. If they do, and if they are configured to also inspect or modify the traffic, this means that content needs to be compressed and expanded in real time multiple times for a single HTTP request.
For example, if a reverse proxy server installed next to the web server serving the application is configured to GZip compress all content towards the user, and also needs to inspect the traffic, it will have to GZip compress traffic towards both the user and the web application (assuming that GZip compression was enabled there). Doing so would negatively impact performance and decrease response times. And this is actually a rather commonly used architecture for shared hosting.
Ideally, ElkArte should try to determine whether the user received compressed content on his end already by the time the application does not compress. And if so, enabling GZip compression on the application layer should not be supported or at least discouraged, both on the installer and the admin web interface (post-install).

I personally don't use the "built in" compression, which is just gzip of the PHP output buffer before content is delivered to the web server.  I let the web server handle all of the compression tasks since I can fine tune when to do it (content length and type) as well as level of gzip (optimize compression vs effort)
We may be able to detect if DEFLATE/GZIP is enabled for a site, maybe a curl call and check the Accept-Encoding headers, that should work for Apache and nginx and others I would think ... not sure about that though.  One could check the loaded modules but that does not mean they are enabled for the output content.
We could also simply beef up the help text for that and note that if your server is configured to compress the output then leave the setting off.

authors: Spuds tomreyn

repo: elkarte/Elkarte


text:
Do not merge

Just a test for travis and scritinizer. :angel:
/me is too lazy to enable them for my repo. :stuck_out_tongue:

That was broken anyway.


text:
problem upgrading package

I upgraded elm-ui on an ellie to 1.1.5, but it still shows the bug it had from elm-ui 1.1.0.
https://ellie-app.com/6ny7kDgfTY3a1
Here's one I created from scratch that doesn't have the elm-ui lib problem.  The first text box should be 3 lines high, and here it works.
https://ellie-app.com/6ny8WkYDyfHa1
Both examples have the same Main.elm and the same package versions.

Uh, ok I just tried it over on Chrome, and it seems I got bitten by the dealio where it won't recompile unless there's a change in my code - library version changes don't merit a recompile.  Don't know if that's really in the bailywick of ellie, but I think it would be helpful to force a recompile on version changes.

Thanks for reporting back! Closing for now as I don't think I'll be making a change here.

authors: bburdette tbash

repo: ellie-app/ellie


text:
Add button

We need to add a button to the FormDetailPage which allows users to close a form, which will prevent respondents from filling out the form.
The new button should:

Be located to the left of the existing "View live form" button
Say "Close form" when is_open = true, and "Open form" when it's not
When clicked, the button should flip the boolean for the is_open column in the correct row in the database.  Use the supabase client for this.
Have a white background with red text.

Here are Supabase docs: https://supabase.com/docs/reference/javascript/update

lgtm

repo: ellipsis-dev/TalkFormAI


text:
[FEATURE] Ability to add extra options to hightlights

Is your feature request related to a problem? Please describe.
I want to make small tweaks (make some treesitter groups bold, some italic etc). I thought about some clever use of overrides = {}, but neovim doesn't currently support highlight constructs like { link = "GruvboxAqua", bold = true }. So I would have to either use plain colors from configuration, which I don't like, since I often change light and dark theme (I would have to change these values), or just forget about extra italics/bolds etc.
Describe the solution you'd like
I thought about something like:
require("gruvbox").setup({
    extras = {
        ["@boolean"] = { bold = true }
    }
}

This of course would use default colorscheme for @boolean but would add bold = true.
Or if it would be to painful to implement, maybe some predefined treesitter groups, like keyword, boolean, Macro, Directive, function etc.

As I looked into some other schemes, they allow overrides to be a function(colors) which returns table of overridden highlight groups.


text:
Missing descriptions

I just added missing descriptions to some lines

Yay you used my tags at the end :3

authors: Kavex xeBuz

repo: ellisonleao/magictools


text:
Remove usage of <<

Having explicit arguments is more efficient as it avoids the creation of an intermediate function

For people interested in this patch: I have merged this and the other performance improvements by @jfmengels in a fork called https://github.com/miniBill/elm-result-extra

repo: elm-community/result-extra


text:
Build failure with emacs 30

It happens when I try to build lsp-origami, but it looks like the root cause is origami-fold-header-face:
emacs-lsp-origami> Compiling /nix/store/x1iggzf256c280qp2964gsmgv1bnqsxw-emacs-lsp-origami-20230815.704/share/emacs/site-lisp/elpa/lsp-origami-20230815.704/lsp-origami.el...
emacs-lsp-origami> Error: error ("Invalid face box" :line-width 1 :color unspecified)
emacs-lsp-origami>   set-face-attribute(origami-fold-header-face #<frame F1 0xd3e6e0> :box (:line-width 1 :color unspecified) :background unspecified)
emacs-lsp-origami>   face-spec-set-2(origami-fold-header-face #<frame F1 0xd3e6e0> (:box (:line-width 1 :color unspecified) :background unspecified))
emacs-lsp-origami>   face-spec-recalc(origami-fold-header-face #<frame F1 0xd3e6e0>)
emacs-lsp-origami>   face-spec-set(origami-fold-header-face ((t (:box (:line-width 1 :color unspecified) :background unspecified))) face-defface-spec)
emacs-lsp-origami>   custom-declare-face(origami-fold-header-face ((t (:box (:line-width 1 :color unspecified) :background unspecified))) "Face used to display fold headers." :group origami)
emacs-lsp-origami>   require(origami)
emacs-lsp-origami>   byte-compile-file-form-require((require 'origami))
emacs-lsp-origami>   byte-compile-file-form((require 'origami))
emacs-lsp-origami>   #<subr F616e6f6e796d6f75732d6c616d626461_anonymous_lambda_50>((require 'origami))
emacs-lsp-origami>   byte-compile-recurse-toplevel((require 'origami) #<subr F616e6f6e796d6f75732d6c616d626461_anonymous_lambda_50>)
emacs-lsp-origami>   byte-compile-toplevel-file-form((require 'origami))
emacs-lsp-origami>   #f(compiled-function () #<bytecode 0xaa3d790c7be623>)()
emacs-lsp-origami>   bytecomp--displaying-warnings(#f(compiled-function () #<bytecode 0xaa3d790c7be623>))
emacs-lsp-origami>   byte-compile-from-buffer(#<buffer  *Compiler Input*>)
emacs-lsp-origami>   byte-compile-file("/nix/store/x1iggzf256c280qp2964gsmgv1bnqsxw-emacs-lsp-origami-20230815.704/share/emacs/site-lisp/elpa/lsp-origami-20230815.704/lsp-origami.el")
emacs-lsp-origami>   byte-recompile-file("/nix/store/x1iggzf256c280qp2964gsmgv1bnqsxw-emacs-lsp-origami-20230815.704/share/emacs/site-lisp/elpa/lsp-origami-20230815.704/lsp-origami.el" t 0)
emacs-lsp-origami>   #f(compiled-function () #<bytecode 0x1679791aa2d1bb4f>)()
emacs-lsp-origami>   bytecomp--displaying-warnings(#f(compiled-function () #<bytecode 0x1679791aa2d1bb4f>))
emacs-lsp-origami>   byte-recompile-directory("/nix/store/x1iggzf256c280qp2964gsmgv1bnqsxw-emacs-lsp-origami-20230815.704/share/emacs/site-lisp/elpa/lsp-origami-20230815.704" 0 t)
emacs-lsp-origami>   package--compile(#s(package-desc :name lsp-origami :version (20230815 704) :summary "origami.el support for lsp-mode" :reqs ((emacs (27 1)) (origami (1 0)) (lsp-mode (6 1))) :kind nil :archive nil :dir "/nix/store/x1iggzf256c280qp2964gsmgv1bnqsxw-emacs-lsp-origami-20230815.704/share/emacs/site-lisp/elpa/lsp-origami-20230815.704" :extras ((:url . "https://github.com/emacs-lsp/lsp-origami") (:keywords "languages" "lsp-mode")) :signed nil))
emacs-lsp-origami>   package-unpack(#s(package-desc :name lsp-origami :version (20230815 704) :summary "origami.el support for lsp-mode" :reqs ((emacs (27 1)) (origami (1 0)) (lsp-mode (6 1))) :kind single :archive nil :dir nil :extras ((:keywords "languages" "lsp-mode") (:url . "https://github.com/emacs-lsp/lsp-origami")) :signed nil))
emacs-lsp-origami>   (let ((pkg-desc (if (derived-mode-p 'tar-mode) (package-tar-file-info) (package-buffer-info)))) (package-unpack pkg-desc) pkg-desc)
emacs-lsp-origami>   elpa2nix-install-from-buffer()
emacs-lsp-origami>   (progn (if is-tar (insert-file-contents-literally file) (insert-file-contents file)) (if is-tar (progn (tar-mode))) (elpa2nix-install-from-buffer))
emacs-lsp-origami>   (unwind-protect (progn (if is-tar (insert-file-contents-literally file) (insert-file-contents file)) (if is-tar (progn (tar-mode))) (elpa2nix-install-from-buffer)) (and (buffer-name temp-buffer) (kill-buffer temp-buffer)))
emacs-lsp-origami>   (save-current-buffer (set-buffer temp-buffer) (unwind-protect (progn (if is-tar (insert-file-contents-literally file) (insert-file-contents file)) (if is-tar (progn (tar-mode))) (elpa2nix-install-from-buffer)) (and (buffer-name temp-buffer) (kill-buffer temp-buffer))))
emacs-lsp-origami>   (let ((temp-buffer (generate-new-buffer " *temp*" t))) (save-current-buffer (set-buffer temp-buffer) (unwind-protect (progn (if is-tar (insert-file-contents-literally file) (insert-file-contents file)) (if is-tar (progn (tar-mode))) (elpa2nix-install-from-buffer)) (and (buffer-name temp-buffer) (kill-buffer temp-buffer)))))
emacs-lsp-origami>   (let ((is-tar (string-match "\\.tar\\'" file))) (let ((temp-buffer (generate-new-buffer " *temp*" t))) (save-current-buffer (set-buffer temp-buffer) (unwind-protect (progn (if is-tar (insert-file-contents-literally file) (insert-file-contents file)) (if is-tar (progn (tar-mode))) (elpa2nix-install-from-buffer)) (and (buffer-name temp-buffer) (kill-buffer temp-buffer))))))
emacs-lsp-origami>   elpa2nix-install-file("/build/packages/lsp-origami-20230815.704.el")
emacs-lsp-origami>   (progn (setq package-user-dir elpa) (elpa2nix-install-file archive))
emacs-lsp-origami>   (let ((archive x0) (elpa x2)) (progn (setq package-user-dir elpa) (elpa2nix-install-file archive)))
emacs-lsp-origami>   (if (null x3) (let ((archive x0) (elpa x2)) (progn (setq package-user-dir elpa) (elpa2nix-install-file archive))))
emacs-lsp-origami>   (let* ((x2 (car-safe x1)) (x3 (cdr-safe x1))) (if (null x3) (let ((archive x0) (elpa x2)) (progn (setq package-user-dir elpa) (elpa2nix-install-file archive)))))
emacs-lsp-origami>   (if (consp x1) (let* ((x2 (car-safe x1)) (x3 (cdr-safe x1))) (if (null x3) (let ((archive x0) (elpa x2)) (progn (setq package-user-dir elpa) (elpa2nix-install-file archive))))))
emacs-lsp-origami>   (let* ((x0 (car-safe command-line-args-left)) (x1 (cdr-safe command-line-args-left))) (if (consp x1) (let* ((x2 (car-safe x1)) (x3 (cdr-safe x1))) (if (null x3) (let ((archive x0) (elpa x2)) (progn (setq package-user-dir elpa) (elpa2nix-install-file archive)))))))
emacs-lsp-origami>   (if (consp command-line-args-left) (let* ((x0 (car-safe command-line-args-left)) (x1 (cdr-safe command-line-args-left))) (if (consp x1) (let* ((x2 (car-safe x1)) (x3 (cdr-safe x1))) (if (null x3) (let ((archive x0) (elpa x2)) (progn (setq package-user-dir elpa) (elpa2nix-install-file archive))))))))
emacs-lsp-origami>   elpa2nix-install-package()
emacs-lsp-origami>   command-line-1(("-l" "/nix/store/0f21rid2as88mh6ghf6rpp1icr7fs1x7-elpa2nix.el" "-f" "elpa2nix-install-package" "/build/packages/lsp-origami-20230815.704.el" "/nix/store/x1iggzf256c280qp2964gsmgv1bnqsxw-emacs-lsp-origami-20230815.704/share/emacs/site-lisp/elpa"))
emacs-lsp-origami>   command-line()
emacs-lsp-origami>   normal-top-level()
emacs-lsp-origami> Invalid face box: :line-width, 1, :color, unspecified

I haven't started using Emacs 30, but I'll look into it!
Anyways, PRs are welcome! :D

Looks like it's similar to https://github.com/doomemacs/themes/issues/809 - emacs got stricter to invalid values inside box attribute :)


text:
Loose/less-effort body validation

What version of Elysia is running?
1.1.13
What platform is your computer?
Microsoft Windows NT 10.0.22631.0 x64
What steps can reproduce the bug?
Use this validation in a route
body: t.Union([
	t.Object({
		bookmarked: t.Optional(t.Boolean()),
		link: t.Optional(t.String({ format: "uri" })),
		timeSpent: t.Optional(t.String()),
		when: t.Optional(t.Date()),
	}),
	t.Object({
		bookmarked: t.Optional(t.Boolean()),
		mediaId: t.String(),
		number: t.Integer(),
		timeSpent: t.Optional(t.String()),
		when: t.Optional(t.Date()),
	}),
	t.Object({
		bookmarked: t.Optional(t.Boolean()),
		mediaId: t.Optional(t.String()),
		timeSpent: t.Optional(t.String()),
		when: t.Optional(t.Date()),
	}),
])

And provide this body:
{
"mediaId": "610132145125381",
"number": 1127,
"timeSpent": "PT4M35S",
"when":"2024-09-20T22:05:00.000-03:00"
}

What is the expected behavior?
This shouldn't be an edge case and it should recognize the body as the second type.
What do you see instead?
It recognizes the body as the first type and simply deletes mediaId and number from the body. They exist in ctx.body during onTransform;
Additional information
No response
Have you try removing the node_modules and bun.lockb and try again yet?
No response

If I add { additionalProperties: false }, to the first field it works.

Can u try it with plain typebox?

authors: hyoretsu kravetsone

repo: elysiajs/elysia


text:
(#137) global variable and init funcs

using malloc to sure elements are accessible after leaving init function
adding value wrapper to get element type for casting
create SizeOf(llvmtypes.Type) for 64bits system

Codecov Report

Merging #139 into master will decrease coverage by 1.91%.
The diff coverage is 23.88%.

@@            Coverage Diff             @@
##           master     #139      +/-   ##
==========================================
- Coverage   58.41%   56.49%   -1.92%
==========================================
  Files          14       14
  Lines         731      777      +46
==========================================
+ Hits          427      439      +12
- Misses        272      306      +34
  Partials       32       32

Impacted Files
Coverage Δ

src/irutil/irutil.go
58.82% <0%> (-12.61%)
:arrow_down:

src/elz/codegen/builtin.go
100% <100%> (ø)
:arrow_up:

src/elz/codegen/module.go
27.27% <14.89%> (-1.9%)
:arrow_down:

src/elz/codegen/codegen.go
64.78% <16.66%> (-4.45%)
: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 298d6d5...497172e. Read the comment docs.

authors: codecov-io dannypsnl

repo: elz-lang/elz


text:
Added HunSum2 dataset with results

Checklist for adding MMTEB dataset
Reason for dataset addition:
Added the first Hungarian Retrieval dataset to the benchmark.

[x] I have tested that the dataset runs with the mteb package.
[ x I have run the following models on the task (adding the results to the pr). These can be run using the mteb run -m {model_name} -t {task_name} command.

[x] sentence-transformers/paraphrase-multilingual-MiniLM-L12-v2
[x] intfloat/multilingual-e5-small

[x] I have checked that the performance is neither trivial (both models gain close to perfect scores) nor random (both models gain close to random scores).
[x] I have considered the size of the dataset and reduced it if it is too big (2048 examples is typically large enough for most tasks)
[x] Run tests locally to make sure nothing is broken using make test. I could not do this, as my computer doesn't have enough memory, it crashed multiple times trying to run the tests, everything I could run passes
[x] Run the formatter to format the code using make lint.
[ ] I have added points for my submission to the POINTS.md file.

Addresses #384, but I decided to use HunSum2 instead as it is an updated version of the same dataset.

I could not do this, as my computer doesn't have enough memory, it crashed multiple times trying to run the tests, everything I could run passes

Does it also crash if you only use pytest or pytest -n 4

Setting this to auto-merge!

authors: KennethEnevoldsen x-tabdeveloping

repo: embeddings-benchmark/mteb


text:
Remove active_model_serializers

Is it really depends on active_model_serializers? Just deleted from gemspec and tests passes. Shouldn't we remove it?

It seems reasonable to remove active_model_serializers as a hard dependency of ember-rails, especially since ember-rails makes no use whatsoever of AMS.  Further, ember-rails has to have callouts in the README for how to work around changes to render(:json) introduced in Rails by AMS.
Odd to force people to use AMS when they could easily render their own JSON in many cases. And, over the past few years, other alternatives have appeared (rabl, for example).
At the end of the day, ember-rails doesn't actually use AMS, so it seems wrong to list is as a hard dependency in the gemspec.

authors: nbibler wildchild

repo: emberjs/ember-rails


text:
Bump to v0.9.4-SNAPSHOT

Then, v0.9.4-SNAPSHOT.

Thanks. Merging this...

repo: embulk/embulk


text:
Problem installing package using pip

Ran pip install monero-python on an Ubuntu bash, received the following error. Help appreciated, thank you
Collecting monero-python
  Using cached https://files.pythonhosted.org/packages/ef/57/7fa1459cff9ddf603ffa43aeff88399290b7602bad34981224599d67c240/monero-python-0.2.tar.gz
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/tmp/pip-install-j96wybcp/monero-python/setup.py", line 5, in <module>
        version = __import__('monero').__version__
      File "/tmp/pip-install-j96wybcp/monero-python/monero/__init__.py", line 1, in <module>
        from . import address, account, daemon, wallet, numbers, prio, wordlists, seed
      File "/tmp/pip-install-j96wybcp/monero-python/monero/address.py", line 4, in <module>
        from sha3 import keccak_256
    ModuleNotFoundError: No module named 'sha3'

    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-install-j96wybcp/monero-python/

Try installing pysha3 first:
pip install pysha3 && pip install monero-python

Actually, pip should install dependencies automatically. Doesn't it?

yes, the problem is that setup.py which is supposed to do that, first tries to figure out the version number which it does by importing monero package, which in turn right of the bat tries to import sha3, hence the error

authors: emesik lalanza808 rooterkyberian vertangelx

repo: emesik/monero-python


text:
Added joined missions to profile page

Added joined missions to profile page

Hi @emhamza 👋
Can you please review this PR?

repo: emhamza/Space-X


text:
Problem with generation

INFO:     10.233.71.128:59692 - "POST /elements/generate/start?project_slug=hesutest HTTP/1.1" 200 OK
b'{"model":"llama3.1:70b","created_at":"2024-11-14T14:11:09.258166748Z","response":"DIVERSE","done":true,"done_reason":"stop","context":[128006,882,128007,271,2675,527,264,5505,3495,18328,13,4718,3465,374,311,1373,264,5224,11,323,311,3371,757,3508,433,34945,20057,13,720,35,3050,649,387,3721,11059,4669,3738,3878,320,614,113305,11,6651,11,21655,11,5370,11,8205,11,2204,11,5099,13,7026,719,1288,539,387,7347,311,433,13,720,2746,499,1505,430,433,3721,8099,20057,11,3350,423,19323,937,11,422,539,3350,4276,13,720,325,12116,1093,264,2523,2035,311,3974,13,3892,2204,9873,430,358,1053,1390,311,4034,13,1695,3691,323,16924,2671,13,128009,128006,78191,128007,271,35,19323,937],"total_duration":222875440,"load_duration":23692289,"prompt_eval_count":115,"prompt_eval_duration":38543000,"eval_count":4,"eval_duration":119212000}'
Error in the generating process a915edcd-4520-4a20-872b-f126b8ed465b

problem with index name, found

repo: emilienschultz/activetigger


text:
Advance wgpu version to 22.1, please.

Current wgpu version is now 22.1. (Yes, 22, not 0.22.)
egui-wgpu in crates.io depends upon wgpu 0.20.1.
So, crates out of sync, again, and because everybody passes low level types around, compiles fail.

That is already done on master. It just hasn't been released yet.

Is it? See
https://github.com/emilk/egui/blob/master/Cargo.toml
wgpu = { version = "22.0.0", default-features = false, features = [
    # Make the renderer `Sync` even on wasm32, because it makes the code simpler:
    "fragile-send-sync-non-atomic-wasm",
] }

WGPU is at 22.1.0 now. WGPU got a quick update because something was broken in 22.0.0.

22.1 is semver compatible with 22.0, so that is not a problem.

OK. But it still needs to be pushed to crates.io so that other crates which depend upon it can be updated.

Fixed on master, will be released in next egui release

authors: John-Nagle YgorSouza emilk

repo: emilk/egui


text:
No case for mechs when calculating armory points

ArmouryUtility.GetColonistArmouryPoints does not have a case for colony mechs.
Vanilla uses:
else if (p.IsColonyMech && !p.Downed)
            a = p.kindDef.combatPower * StorytellerUtility.PointsFactorForColonyMechsCurve.Evaluate(wealthForStoryteller);

With the curve ranging from 0.2 to 0.4. Or, put another way, 2-5x as much as animals.
Recommend adding a case for mechs, and a configuration option for mechs.

Thanks, should be added in 67f2446


text:
User profile mobile

closes #706

I też jak się ręcznie wpisze url profilu nie będąc zalogowanym to wejdziemy w niego i jakieś errory wywala, jeśli to nie czasochłonne to można przekierowanie na login page jak się nie jest zalogowanym

repo: emkarcinos/WMIAdventure


text:
Consider MarkDown header styling

EMMOntoPy - Python library for working with ontologies
EMMOntoPy is a Python library for woking with ontologies in general and the Elemental Multiperspective Material Ontology in particular.
Originally posted by @jesper-friis in https://github.com/emmo-repo/EMMO-python/pull/222#discussion_r717284193
As outlined in this review comment @jesper-friis prefers the underlining header-styling.
In my opinion it is not to be preferred simply due to the limitations of the header level that's possible with that styling; there is no possibility to go past level 2 headers with this styling.
However, we could definitely do mixed styling if this is so desired, as long as we, again, in my opinion, do it consequently for all files.

I see that we have ended up with the MarkDown hash header style. Lets stay with that (even though I personally prefer the mixed header styling)

authors: CasperWA jesper-friis

repo: emmo-repo/EMMO-python


text:
Fix year month params analytics

Изменение параметров запроса с даты начала и даты окончания на год и месяц для удобства фронтендеров

Привет, подскажи, а если будет нужна статистика не за месяц, а за 2, что тогда?

Тогда создадим еще один более общий ендпоинт, который будет служить скорее всего другой странице в макете, которой пока нет. То есть текущий макет прописывает поля год, месяц, показать статистику за такой год и месяц на более чем 6 экранах

authors: Bervy OsipovKonstantin


text:
An FVT scenario for Plugins management

An FVT scenario for Plugins management.

One FVT scenarios was added, and close the issue.

repo: emqx/kuiper


text:
Basic question about scope of this project

Is this project intended only for Firebase's Firestore Database? It seems that way, although I could be mistaken. For users who find this crate while looking for a Rust binding to Firebase Analytics, Realtime Database, Authentication, etc., this is confusing. Could you please clarify? There is no API that resembles that of the C++ bindings for Authentication, for example: https://firebase.google.com/docs/auth/cpp/start?authuser=0&hl=en

I think it should be renamed to indicate that it's only for Firestore and/or Realtime Database, since someone looking for a Firebase crate is probably looking for one that implements most (if not all) Firebase API features just like the official ones in other languages.

We will support all Firebase infrastructure. ASAP
@Skaldebane

authors: Skaldebane emreyalvac hut8

repo: emreyalvac/firebase-rs


text:
Inconsistent formats in cl_fix_sub

In the VHDL implementation, the sign bit is true:
constant TempFmt_c 	: FixFormat_t :=
	(
		Signed		=> true,
		IntBits		=> max (a_fmt.IntBits, b_fmt.IntBits) + toInteger (CarryBit_c),
		FracBits	=> max (a_fmt.FracBits, b_fmt.FracBits)
	);

This is consistent with the Python implementation:
fullFmt = FixFormat(True, max(aFmt.IntBits, bFmt.IntBits+int(bFmt.Signed)), max(aFmt.FracBits, bFmt.FracBits))

However, the MATLAB implementation is different:
temp_fmt = cl_fix_format (a_fmt.Signed || b_fmt.Signed, max (a_fmt.IntBits, b_fmt.IntBits)+1, max (a_fmt.FracBits, b_fmt.FracBits));

In its current state, I don't know if this affects the behavior or not. It would make sense to make it consistent anyway. I plan to do this in the near future.

This code has been significantly refactored in the feature/hcom-ideas  branch, plus the MATLAB function now calls the Python function to avoid any future inconsistency.


text:
HACKING.md contains broken links to http://hastebin.com

The HACKING.md documentation contains two broken links to http://hastebin.com : http://hastebin.com/fajomitewu.yaml and http://hastebin.com/gihahuguvu.http.
Those links should be either fixed or removed.

Those links were added by https://github.com/endoflife-date/endoflife.date/commit/fa5e84cb43c713313791871536ca62c01cb8f6ae. @captn3m0, any idea what to do with those links ?

Will change to a gist.

@marcwrobel moving this entry to #1206

authors: captn3m0 marcwrobel usta


text:
[emberjs] Automate LTS EOL retrieval

Based on https://emberjs.com/releases/lts/.

Expected diff:
diff --git i/releases/emberjs.json w/releases/emberjs.json
index 5be95ed..f923b5e 100644
--- i/releases/emberjs.json
+++ w/releases/emberjs.json
@@ -1,5 +1,102 @@
 {
-  "releases": {},
+  "releases": {
+    "5.4": {
+      "name": "5.4",
+      "lts": "2023-12-11",
+      "support": "2024-08-19",
+      "eol": "2024-12-23"
+    },
+    "4.8": {
+      "name": "4.8",
+      "lts": "2022-12-08",
+      "support": "2023-07-06",
+      "eol": "2023-12-21"
+    },
+    "4.4": {
+      "name": "4.4",
+      "lts": "2022-07-13",
+      "support": "2023-02-08",
+      "eol": "2023-07-26"
+    },
+    "4.12": {
+      "name": "4.12",
+      "lts": "2023-05-15",
+      "support": "2024-01-22",
+      "eol": "2024-05-27"
+    },
+    "3.8": {
+      "name": "3.8",
+      "lts": "2019-04-10",
+      "support": "2019-11-06",
+      "eol": "2020-04-22"
+    },
+    "3.4": {
+      "name": "3.4",
+      "lts": "2018-10-15",
+      "support": "2019-05-13",
+      "eol": "2019-10-28"
+    },
+    "3.28": {
+      "name": "3.28",
+      "lts": "2021-12-20",
+      "support": "2022-07-18",
+      "eol": "2023-01-02"
+    },
+    "3.24": {
+      "name": "3.24",
+      "lts": "2021-02-25",
+      "support": "2021-09-23",
+      "eol": "2022-03-10"
+    },
+    "3.20": {
+      "name": "3.20",
+      "lts": "2020-09-02",
+      "support": "2021-03-31",
+      "eol": "2021-09-15"
+    },
+    "3.16": {
+      "name": "3.16",
+      "lts": "2020-03-16",
+      "support": "2020-10-12",
+      "eol": "2021-03-29"
+    },
+    "3.12": {
+      "name": "3.12",
+      "lts": "2019-09-25",
+      "support": "2020-04-22",
+      "eol": "2020-10-07"
+    },
+    "2.8": {
+      "name": "2.8",
+      "lts": "2016-10-17",
+      "support": "2017-05-15",
+      "eol": "2017-10-30"
+    },
+    "2.4": {
+      "name": "2.4",
+      "lts": "2016-04-11",
+      "support": "2016-11-07",
+      "eol": "2017-04-24"
+    },
+    "2.18": {
+      "name": "2.18",
+      "lts": "2018-02-14",
+      "support": "2018-09-12",
+      "eol": "2019-02-27"
+    },
+    "2.16": {
+      "name": "2.16",
+      "lts": "2017-11-20",
+      "support": "2018-06-18",
+      "eol": "2018-12-03"
+    },
+    "2.12": {
+      "name": "2.12",
+      "lts": "2017-04-29",
+      "support": "2017-11-25",
+      "eol": "2018-05-12"
+    }
+  },
   "versions": {
     "5.6.0": {
       "name": "5.6.0",


text:
Wikigeeks: Wikigeeks stuck in infinite loop, timer keeps reseting itself when reaching 15 second mark

Not sure how this happened. I did start the session after waiting in the lobby with three players for a significantly long time to see if I could get kicked out. My ihpone6s went to sleep, and upon waking, was still on the "waiting for players" screen. When I started the game, all seemed normal except all sorts of issues started happening, including this looping
I am assuming the game was somehow readinging as disconnected, but still let me move forward since we were "still in it"

qa team please try and reproduce

unable to reproduce

authors: jpailthorpe mattwbenson

repo: engagementgamelab/emerging-citizens


text:
chore(main): release stowfiles 1.18.1

:robot: I have created a release beep boop
1.18.1 (2024-08-12)
Bug Fixes

bspwm: if picom does NOT exist ... exit 0 (c18db03)

Miscellaneous

zsh: ignore the zsh_functions directory (4b8d4aa)

Code Refactoring

zsh: move keychain calls to .profile and just source in .zshrc (edf84d8)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

stowfiles-v1.18.1
:sunflower:

repo: engeir/stowfiles


text:
Manage @template tags

This PR adds management of @template tags by adding the defined templates to the class name and method name.

Oups, I never noticed @template was not standard. It's in fact provided by closure compiler and used by several js libraries. I don't think it's a good thing to create a new @generic tag. It would be better to have a mechanism to say we want the support of closure compiler's tags.

Ah! Didn't realize it was a closure compiler tag, that makes more sense. In that case, can you just add a section mentioning supported CC tags and adding a link for that one to the docs for that tag?

Merged this, will manually fix the few issues I had.

authors: englercj osechet

repo: englercj/tsd-jsdoc


text:
Add Volume Control Support and UI

This Issue consists of two parts:

Implement volume adjustment in the player.
Implement a UI element to control and test the volume.

PR created.

repo: englishm/moq-js


text:
Helm installation fails using FlexCD.

The CronJob “kube-image-keeper-registry-garbage-collection” has too long a name, and prefixing it with Namespace would exceed the 52 character limit.
This is not a problem with kuik, but could the name be changed to something shorter, for example, “kuik-registry-garbage-collection”?
Warning  InstallFailed       8s                     helm-controller  Helm install failed for release kuik-system/kuik-system-kube-image-keeper with chart kube-image-keeper@1.10.0:
 1 error occurred: * CronJob.batch "kuik-system-kube-image-keeper-registry-garbage-collection" is invalid:
metadata.name: Invalid value: "kuik-system-kube-image-keeper-registry-garbage-collection": must be no more than 52 characters

duplicate of #425, closing

authors: chattytak paullaffitte

repo: enix/kube-image-keeper


text:
Improve certificate expiration alert

Hi. It seems that in the certificate expiration alert it is more informative to display the number of days until its expiration.

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

authors: Programmeris monkeynator


text:
Java Model

./enola -v get --load file:bazel-bin/java/dev/enola/cli/enola_deploy.jar enola:/ should list Java Class/Enum/etc. Type Things; get one of them should show its references.
This could then be used e.g. for #502.

should show its references

I have, so far, zoomed in to possibly using one of the following two libraries for this, but ... it's not super clear to me if either of them will find references to the types used in the implementation body of methods, and not just the methods' signatures, fields and class declarations... I should probably just try it out to see!

ArchUnit: Its Dependency looks like it might provide such details? ("class calls a method/constructor of another class")

ClassGraph: Has ignoreMethodVisibility, but glancing over its MethodInfo makes me think it cannot? @lukehutch am I getting this right - will ClassGraph provide metadata from signatures, but not method body implementations?  Or is there another way (API) which I'm missing? (Hi! We've interacted in the past.)

If they both do not provide this, then this probably requires BCEL or ByteBuddy or Javassist? That would likely be quite a bit more involved than I was thinking of doing here, only for this; and I de-prioritize this if that was the case.

ClassGraph: Has ignoreMethodVisibility, but glancing over its MethodInfo makes me think it cannot? @lukehutch am I getting this right - will ClassGraph provide metadata from signatures, but not method body implementations? Or is there another way (API) which I'm missing? (Hi! We've https://github.com/classgraph/classgraph/issues/256.)

https://github.com/classgraph/classgraph/wiki/ClassInfo-API#generating-a-graphviz-dot-file-for-class-graph-visualization seems to answer it...

but I still don't understand which ClassGraph API would provide me said ...

ClassGraph.enableInterClassDependencies() seems to explain it... I think I now see how this could be done!

Classgraph does not parse they bytecode in a classfile, it only parses the class metadata (including signatures of methods and fields, etc.). The bytecode format is complex and more likely to change than class metadata, so keeping up with the bytecode format is a non-goal for ClassGraph. The only reliable way to read bytecode is to use the ASM library.
So basically if the info you need is in the bytecode, ClassGraph can't help, and you have to use ASM. If it's not, ClassGraph can help.

authors: lukehutch vorburger

repo: enola-dev/enola


text:
Add capability to intelligently generate graphs incase numerical data is returned

It'd be great if big-agi can (optionally) include a chart using common charting libraries like d3js, plotly etc. incase the response returned from the bot includes data.

Great request. In some sense, one would detect that there's an underline grid data (markdown grid, csv data, etc), and activate either a Table view (already provided in Markdown mode, in Settings), or Charts.
What would be the top-priority charts for your use case? Would be great to find a simple and easy and lightweight library for charts, and wire it in a way that as much data as possible is plotted.
Ideas for Libraries, Data output parsing, Top priority charts to do, and how do handle multi-columns data are very welcome.

Thanks @enricoros, I did a very hacky implementation to support Bar Charts and Line Charts for a POC

I used ChartJS (react-chartjs-2) and that seemed to work well for these chart types, with slight animation, and ability to turn on and off chart series etc.
I think something like ChartJS or the new https://observablehq.com/plot/marks/auto "The magic ✨ auto mark automatically selects a mark type that best represents the given dimensions of the data according to some simple heuristics. " might be a good addition.
We can also let the LLM suggest the chart type and use that to instantiate the suggested chart type

This looks incredibly good!!
Would you be open to sending a PR? If you do, please develop on top of the next branch which has a better architecture and will replace the mainline in a few weeks.
Great project, that charting seems like magic.
I can see a vast utility for charting, especially if the model is injected with a tools pattern which pushes it to create more models, aka: a statistician or analyst persona.
I'm very open to picking up a PR, and if you so choose, make sure the charting library is not so heavy (for people that don't use charts).

P.S.: formerly I used:

Victory: great lib for professional looking results, but requires lots of code. Good to create well customized visual experiences (e.g. newspapers) but not flexible
ApexCharts: quick and easy, less controllable and configurable, may miss features or chart types
D3: OG, but requires quite some boilerplate and deep react knowledge

I like that Magic lib you pointed out above.

@saurabhgaur next branch is merged, and supports the latest models from Today's OpenAI announcement.
Did you experiment on this?

Thanks @enricoros, I did a very hacky implementation to support Bar Charts and Line Charts for a POC  I used ChartJS (react-chartjs-2) and that seemed to work well for these chart types, with slight animation, and ability to turn on and off chart series etc. I think something like ChartJS or the new https://observablehq.com/plot/marks/auto "The magic ✨ auto mark automatically selects a mark type that best represents the given dimensions of the data according to some simple heuristics. " might be a good addition. We can also let the LLM suggest the chart type and use that to instantiate the suggested chart type

Back to this - could you share the code for it? Looks pretty sweet and I'd love to productize it.

Hello All!
I Tried mermaid for this , and it works as expected(though not able to create bargraphs)(Had to enable mermaid rendering )

prompt-You are a mermaid diagram creator.Write code for mermaid diagram as per the users request and always output the code in a codeblock.

This can also create innovative mindmaps:

Systemprompt:
Create a mermaid mindmap based on user input like these examples:
(Output code in code block like below)
mindmap
\t\troot(("leisure activities weekend"))
\t\t\t\t["spend time with friends"]
\t\t\t\t::icon(fafa fa-users)
\t\t\t\t\t\t("action activities")
\t\t\t\t\t\t::icon(fafa fa-play)
\t\t\t\t\t\t\t\t("dancing at night club")
\t\t\t\t\t\t\t\t("going to a restaurant")
\t\t\t\t\t\t\t\t("go to the theater")
\t\t\t\t["spend time your self"]
\t\t\t\t::icon(fa fa-fa-user)
\t\t\t\t\t\t("meditation")
\t\t\t\t\t\t::icon(fa fa-om)
\t\t\t\t\t\t("\`take a sunbath ☀\`")
\t\t\t\t\t\t("reading a book")
\t\t\t\t\t\t::icon(fa fa-book)
text summary mindmap:
Barack Obama (born August 4, 1961) is an American politician who served as the 44th president of the United States from 2009 to 2017. A member of the Democratic Party, he was the first African-American president of the United States.
mindmap
\troot("Barack Obama")
\t\t("Born August 4, 1961")
\t\t::icon(fa fa-baby-carriage)
\t\t("American Politician")
\t\t\t::icon(fa fa-flag)
\t\t\t\t("44th President of the United States")
\t\t\t\t\t("2009 - 2017")
\t\t("Democratic Party")
\t\t\t::icon(fa fa-democrat)
\t\t("First African-American President")
cause and effects mindmap:
mindmap
\troot("Landlord sells apartment")
\t\t::icon(fa fa-sell)
\t\t("Renter must be notified of sale")
\t\t::icon(fa fa-envelope)
\t\t\t("Tenants may feel some uncertainty")
\t\t\t::icon(fa fa-question-circle)
\t\t("Notice periods must be observed")
\t\t::icon(fa fa-calendar)
\t\t\t("Landlord can submit notice of termination for personal use")
\t\t\t::icon(fa fa-home)
\t\t\t\t("Tenant has to look for a new apartment")
\t\t\t\t::icon(fa fa-search)
\t\t("New owner")
\t\t::icon(fa fa-user)
\t\t\t\t("New owner takes over existing rental agreement")
\t\t\t\t::icon(fa fa-file-contract)
\t\t\t\t\t\t("Tenant keeps previous apartment")
\t\t\t\t\t\t::icon(fa fa-handshake)
\t\t\t\t("New owner terminates newly concluded lease")
\t\t\t\t::icon(fa fa-ban)
\t\t\t\t\t\t("Tenant has to look for a new apartment")
\t\t\t\t\t\t::icon(fa fa-search)

I Tried mermaid for this , and it works as expected(though not able to create bargraphs)(Had to enable mermaid rendering )

This is really cool - do you have any code that we should productive?

Maybe I can pick that up myself if no-one is working on this

Update on this issue.
What we have:

Render of Mermaid code (```mermaid ... ```)
Rendering of PlantUML code (@startuml ... @enduml, @startmindmap ... @endmindmap, etc.)
Render of Markdown tables
A Visualize ... menu to turn Text into a chart (by using prompts to write code, which is then rendered)

For both of them, the code must be within the body of a message, or the message itself.
What we don't have

Table extraction: identification of markdown tables, or CSV fragments and treating them like table blocks
Custom render of Tables and data therein: with sorting, filtering, coloring, download of CSV, etc.
Auto-plotting of data: whenever a table is encountered, auto-plotting could be turned on by default
Data prompt switches*: when customizing a persona, add -mixin instructions to explain to generate visualization code when dealing with data and tables

Note that these 4 could as well be separate issues, so feel free to break them down.

[x] Table extraction: identification of markdown tables, or CSV fragments and treating them like table blocks

With #392 merged, which features tabular data extraction, this becomes very feasible now.
What we need to make this happen is:

[ ] detection of when Auto-Charting can be applied
[ ] adding a button besides the "Download table as .csv" button
[ ] detection of data types by column, to be able to (SAFELY) parse numerical data
[ ] choice of the right charting library: https://observablehq.com/plot/marks/auto, ChartJS,
[ ] formatting the data and options for the charting library
[ ] injecting the chart when the button is toggled

authors: edmondop enricoros saurabhgaur vaibhavard

repo: enricoros/big-agi


text:
Update to ensime website

Just completes the documentation migration over to ensime's website.

Thanks a lot for this @ChrisCoffey, really appreciated! Could you please link directly to the ensime-vim doc? https://ensime.github.io/editors/vim/

authors: ChrisCoffey jvican

repo: ensime/ensime-vim


text:
Update SQL builder to match with CTE PostgreSQL recursive query for LIMIT & ORDER in outer, initial and recursive queries

Fixed #2167

@a8m I Added extra tests to cover all dialects

repo: ent/ent


text:
User on blacklist was renamed

Per request on your talk you haven't seen yet :)

Thanks for the patch! I have decided to move the list onwiki (see https://en.wikipedia.org/w/index.php?title=User_talk:Enterprisey&oldid=969418502#Recently_active), so this patch is no longer necessary.

repo: enterprisey/recently-active


text:
🛑 905 (Managed - Web) - HTTPS is down

In 2dabf23, 905 (Managed - Web) - HTTPS ($URL_905) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 905 (Managed - Web) - HTTPS is back up in 3b085a6.

repo: envesko/status


text:
WASM http filters should be able to send an error to the downstream client after return from a callout

This would be necessary to re-implement the istio/proxy mixer filter as a wasm bundle.  AFAIK, it's possible to suspend a client request during the callout and resume it after the callout finishes, but I don't know if it's possible to reject the client request if the callout finishes with an error.
example:
// NOLINT(namespace-envoy)
#include <string>
#include <unordered_map>
#include "proxy_wasm_intrinsics.h"
#include "proxy_wasm_intrinsics_lite.pb.h"

class ExampleContext : public Context {
 public:
  explicit ExampleContext(uint32_t id, RootContext *root) : Context(id, root) {}

  FilterHeadersStatus onRequestHeaders() override;
};

static RegisterContextFactory
    register_ExampleContext(CONTEXT_FACTORY(ExampleContext));

class MyGrpcCallHandler : public GrpcCallHandler<google::protobuf::Value> {
 public:
  MyGrpcCallHandler(ExampleContext *context)
      : GrpcCallHandler<google::protobuf::Value>(context), context_(context) {}
  void onCreateInitialMetadata() override {}
  void onSuccess(google::protobuf::Value &&response) override {
    logInfo(response.string_value());
    continueRequest();
  }
  void onFailure(GrpcStatus status,
                 std::unique_ptr<WasmData> error_message) override {
    logInfo(std::string("failure ") + std::to_string(static_cast<int>(status)) +
            std::string(error_message->view()));

   HERE IS WHERE ONE WOULD WANT TO SEND AN ERROR RESPONSE TO THE DOWNSTREAM CLIENT AND ABORT THE TRANSACTION
  }

 private:
  ExampleContext *context_;
};

FilterHeadersStatus ExampleContext::onRequestHeaders() {
  GrpcService grpc_service;
  grpc_service.mutable_envoy_grpc()->set_cluster_name("callout_cluster");
  std::string grpc_service_string;
  grpc_service.SerializeToString(&grpc_service_string);

  google::protobuf::Value value;
  value.set_string_value("request");

  grpcCallHandler(grpc_service_string, "service", "method", value, 1000,
                  std::unique_ptr<GrpcCallHandlerBase>(new MyGrpcCallHandler(this)));
  return FilterHeadersStatus::StopIteration;
}

The call we need is sendLocalReply, which unfortunately has this signature:
void sendLocalReply(Code code, absl::string_view body,
std::function<void(HeaderMap& headers)> modify_headers,
const absl::optionalGrpc::Status::GrpcStatus grpc_status,
absl::string_view details).
Specifically the problem is with the std::function.  The headers are generated deep in source/http/utility.c which then calls the provided function to generate the final headers.  Since those generated headers are determined by the other arguments, I would suggest that we could simply include a set of headers in our API and fabricate a std::function which would just insert them.
Is that acceptable?

Yeah that sounds like a good plan

authors: duderino jplevyak

repo: envoyproxy/envoy-wasm


text:
Converge the buffer parameter and op, or not

Userspace Io Handle is following the IoSocketHandle pattern right now.

Respect the watermark.
Reserve and read. The reserve is an op that computing the upper limit of a move.

This io handle is not used anywhere until a specialized listener and connection factory is landed.
Create this issue to explore after

How to improve the reserve-and-read? Do we want to use the exact value in socket handle?
Since the internal socket represents a hidden and extra chain node betweens the downstream socket and upstream socket, should we aim at downstreamsocket to upstream socket fairness, or os socket to internal socket fairness?

Once we understand it, the next step is to either unify the buffer parameters(remove duplication definition) or admit the exception at the internal userspace socket.

CC @ggreenway @antoniovicente

Motivating comment thread: https://github.com/envoyproxy/envoy/pull/14917#discussion_r583844596
I think this relates to buffer move limits, amount of data that the filter pipeline can move in one go and connection write limits.  I agree that we want a consistent framework for these things.

authors: antoniovicente lambdai

repo: envoyproxy/envoy


text:
type.googleapis.com/envoy.extensions.stat_sinks.wasm.v3.Wasm  not work

If you are reporting any crash or any potential security issue, do not
open an issue in this repo. Please report the issue via emailing
envoy-security@googlegroups.com where the issue will be triaged appropriately.
Title: One line description
type.googleapis.com/envoy.extensions.stat_sinks.wasm.v3.Wasm  not work
Description:

What issue is being seen? Describe what should be happening instead of
the bug, for example: Envoy should not crash, the expected value isn't
returned, etc.
type.googleapis.com/envoy.extensions.stat_sinks.wasm.v3.Wasm  not work
Repro steps:
Include sample requests, environment, etc. All data and inputs
required to reproduce the bug.

Note: The Envoy_collect tool
gathers a tarball with debug logs, config and the following admin
endpoints: /stats, /clusters and /server_info. Please note if there are
privacy concerns, sanitize the data prior to sharing the tarball/pasting.

Admin and Stats Output:

Include the admin output for the following endpoints: /stats,
/clusters, /routes, /server_info. For more information, refer to the
admin endpoint documentation.

Note: If there are privacy concerns, sanitize the data prior to
sharing.

Config:

Include the config used to configure Envoy.

apiVersion: networking.istio.io/v1alpha3
kind: EnvoyFilter
metadata:
  name: ef-bootstrap
spec:
  workloadSelector:
    labels:
      app: productpage
  configPatches:
  - applyTo: BOOTSTRAP
    patch:
      operation: MERGE
      value:
          stats_sinks:
          - name: wasm
            typed_config:
              "@type": type.googleapis.com/envoy.extensions.stat_sinks.wasm.v3.Wasm
              config:
                root_id: my-wasm-root-id
                vm_config:
                  vm_id: my-wasm-vm-id
                  runtime: envoy.wasm.runtime.v8
                  code:
                    remote:
                      http_uri:
                        uri: http://my-wasm-binary-uri
                configuration:
                  "@type": "type.googleapis.com/google.protobuf.StringValue"
                  value: |
                    {}

Logs:

Include the access logs and the Envoy logs.

2022-03-23T07:07:48.021692Z     info    JWT policy is third-party-jwt
2022-03-23T07:07:48.266883Z     info    CA Endpoint istiod.istio-system.svc:15012, provider Citadel
2022-03-23T07:07:48.266909Z     info    Using CA istiod.istio-system.svc:15012 cert with certs: var/run/secrets/istio/root-cert.pem
2022-03-23T07:07:48.266954Z     info    citadelclient   Citadel client using custom root cert: var/run/secrets/istio/root-cert.pem
2022-03-23T07:07:48.279975Z     info    ads     All caches have been synced up in 260.415355ms, marking server ready
2022-03-23T07:07:48.280396Z     info    sds     SDS server for workload certificates started, listening on "etc/istio/proxy/SDS"
2022-03-23T07:07:48.280414Z     info    xdsproxy        Initializing with upstream address "istiod.istio-system.svc:15012" and cluster "Kubernetes"
2022-03-23T07:07:48.280865Z     info    Opening status port 15020
2022-03-23T07:07:48.296935Z     info    sds     Starting SDS grpc server
2022-03-23T07:07:48.297939Z     info    Pilot SAN: [istiod.istio-system.svc]
2022-03-23T07:07:48.298903Z     info    starting Http service at 127.0.0.1:15004
2022-03-23T07:07:48.422808Z     info    xdsproxy        connected to upstream XDS server: istiod.istio-system.svc:15012
2022-03-23T07:07:48.458945Z     error   failed to write updated envoy bootstrap: failed to marshal bootstrap as JSON: proto: not found
2022-03-23T07:07:48.560058Z     info    cache   generated new workload certificate      latency=278.491477ms ttl=23h59m59.439949755s
2022-03-23T07:07:48.560075Z     info    cache   Root cert has changed, start rotating root cert
2022-03-23T07:07:48.560087Z     info    ads     XDS: Incremental Pushing:0 ConnectedEndpoints:0 Version:
2022-03-23T07:07:48.560115Z     info    cache   returned workload trust anchor from cache       ttl=23h59m59.439885957s

Note: If there are privacy concerns, sanitize the data prior to
sharing.

Call Stack:

If the Envoy binary is crashing, a call stack is required.
Please refer to the Bazel Stack trace documentation.

Hi @13567436138 for a bug report to be useful it needs a little more information than you have provided
what are you trying to achieve ?
what different approaches have you tried ?
also the logs you have posted are not afaict envoy logs


text:
metrics_service_integration_test flaky on tsan

Apparently it hung on the tsan build, as mentioned in https://github.com/envoyproxy/envoy/pull/2530

Pretty sure this is fixed.


text:
Local reply modification body substitution

Title: Local reply modification body substitution
Description:
As it currently stands, one can use local reply format modification to do something such as the following:
mappers:
- filter:
    status_code_filter:
      comparison:
        op: EQ
        value:
          default_value: 400
          runtime_key: key_b
  status_code: 401
  body:
    inline_string: "not allowed"
body_format:
  text_format: "%LOCAL_REPLY_BODY% %CEL(request.id)%"

While this works for simple use cases, I would like to be able to treat %LOCAL_REPLY_BODY% as a template, meaning that if body looks like the following:
  body:
    inline_string: "not allowed! request id: %CEL(request.id)%"

%CEL(request.id)% should be replaced with the request ID, however no substitution can currently happen on %LOCAL_REPLY% from within body_format.
To circumvent this, I would need to have something along the lines of:
mappers:
- filter:
    status_code_filter:
      comparison:
        op: EQ
        value:
          default_value: 400
          runtime_key: key_b
  status_code: 401
  body:
    inline_string: "not allowed! request id:"
body_format:
  text_format: "%LOCAL_REPLY_BODY% %CEL(request.id)%"

However, this is also not a very viable solution since the response body needs to be split between body and body_format, with the separator being where the variable is to be inserted, and will also not work for multiple attributes. I have also tried putting the entire contents of my local reply in body_format, however Envoy will fail to load the configuration depending on what the content of the local reply is. Is there any currently supported way to go about this?

body_format is meant as the template I believe. can you elaborate on:

I have also tried putting the entire contents of my local reply in body_format, however Envoy will fail to load the configuration depending on what the content of the local reply is

Local reply body is meant as a short fixed string, because it's populated by the internals of Envoy for the standard codec errors.

body_format is meant as the template I believe. can you elaborate on:

I have also tried putting the entire contents of my local reply in body_format, however Envoy will fail to load the configuration depending on what the content of the local reply is

Local reply body is meant as a short fixed string, because it's populated by the internals of Envoy for the standard codec errors.

I mentioned that putting the entire contents of my reply in body_format doesn't work and assumed that this field may be strictly limited in the characters I can use without having to escape them, however I found out that Envoy was only rejecting my configuration because I was using the % symbol for some inline CSS. After I escaped the occurrences with another %, Envoy loaded the entire template fine. This approach works fine, so I will close out the issue.

authors: kyessenov pchaseh


text:
scheme field should be case-insensitive for the sake of robustness

Title: scheme field should be case-insensitive for the sake of robustness
Description:
When redirecting the request for envoyproxy.io to the local envoy 8000 service via the curl -x parameter, a 400 response error will occur.  The reasons for the error are as follows
https://github.com/envoyproxy/envoy/blob/2703a97f090524dddd04e100213eea4275976b7a/source/common/http/utility.cc#L415-L416
https://github.com/envoyproxy/envoy/blob/2703a97f090524dddd04e100213eea4275976b7a/source/common/http/http1/codec_impl.cc#L1141-L1144
$curl envoyproxy.io -x 127.0.0.1:8000 -v
* About to connect() to proxy 127.0.0.1 port 8000 (#0)
*   Trying 127.0.0.1...
* Connected to 127.0.0.1 (127.0.0.1) port 8000 (#0)
> GET HTTP://envoyproxy.io/ HTTP/1.1
> User-Agent: curl/7.29.0
> Host: envoyproxy.io
> Accept: */*
> Proxy-Connection: Keep-Alive
>
< HTTP/1.1 400 Bad Request
< content-length: 11
< content-type: text/plain
< date: Tue, 25 Jul 2023 04:08:33 GMT
< server: envoy
< connection: close
<
* Closing connection 0
Bad Request

Reference rfc3986 for the definition specification of scheme: Although schemes are case-insensitive, the canonical form is lowercase and documents that specify schemes must do so with lowercase letters.  An implementation should accept uppercase letters as equivalent to lowercase in scheme names (e.g., allow "HTTP" as well as "http") for the sake of robustness but should only produce lowercase scheme names for consistency.
So envoy implementation of scheme field should be case-insensitive for the sake of robustness.

cc @RyanTheOptimist

How does this relate to the CVE https://github.com/envoyproxy/envoy/security/advisories/GHSA-pvgm-7jpg-pw5g which was just fixed?

How does this relate to the CVE GHSA-pvgm-7jpg-pw5g which was just fixed?

Yeah, It seems to have been fixed in this PR https://github.com/envoyproxy/envoy/pull/28613/files#diff-c22054b3e08df13d3a78842825935cd41aa61f439170a34e5f055e826da4d9c1R1398.

authors: RyanTheOptimist mattklein123 wangfakang