text:
Desativar o desconto no meio de pagamento caso haja cupons de desconto aplicados.

Hoje a configuração de desconto acumulativo é feita apenas no CUPOM. Seria importante ter esse processo na forma de pagamento.
Ou seja, caso o cliente estiver utilizando o cupom, o desconto do meio de pagamento seria ‘desativado’.
Ter opção para desativar o desconto da forma de pagamento caso haja cupom de desconto aplicado.

Sugestão retirada da comunidade
.

@ThaisChaves como é uma alteração na configuração do app é necessário reinstalar ele pra ver a opção de configuração adicionada...

repo: ecomplus/app-paghiper


text:
Journeys Into HARK

@ericholscher @shaunagm,
Jan Rosa has been working with me to improve the HARK documentation, and I've had him look in particular for toolkits that do a good job of guiding new users into the substance of the toolkit, by constructing curated "journeys into HARK" for people with different backgrounds.  He's found some nice examples and what I would like to have him do is to create the rudiments of at least two different "journeys into HARK" -- one from the perspective of a first year PhD economics grad student, and one for someone with a lot of computer expertise but less economics grounding.  I'm sending this message because if the two of you have advice for him (esp about integration of such journeys into RTD), that would be useful to him.

I will be very grateful for your advice. Before, I added some auto documentation into RTD however, I have never integrated it with Jupyter notebook.

Great. All the integration with Sphinx is done via nbsphinx -- so that would be the best place to look for best practices. I haven't done much personally, but their docs are pretty good, and the maintainers are responsive.

Thank you! I will try this and start building the journeys!

@janrosa1 any updates on this?
I'm currently working on documentation aimed at those with more computer science experience, and less economics experience.

Hi,
I do not have any updates now - I sent the pull request in the late August
(all the notebooks integrate at my fork with nbshpinx). However if you
think that I should add something to the repositories, or have some
questions how I organized the "intro to HARK" for people with econ
experience (1st year PhD), please let me know. I will answer ASAP.
Best,
Jan
pon., 3 lut 2020 o 09:26 Sebastian Benthall notifications@github.com
napisał(a):

@janrosa1 https://github.com/janrosa1 any updates on this?
I'm currently working on documentation aimed at those with more computer
science experience, and less economics experience.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/econ-ark/HARK/issues/362?email_source=notifications&email_token=AENCRHWZ5WWUR5NHZHHYRWLRBBHTTA5CNFSM4IFZ53DKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKUV3DI#issuecomment-581524877,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AENCRHT4RK2SBQ225EH2K43RBBHTTANCNFSM4IFZ53DA
.

implemented in https://github.com/econ-ark/HARK/pull/380

source: gharchive/issue

authors: MridulS ericholscher janrosa1 llorracc sbenthall

repo: econ-ark/HARK

license_type: permissive

license_source: bigquery


text:
Cannot Export Context

import { zodiosContext } from '@zodios/express';
import z from 'zod';

const user = z.object({
  user: z
    .object({
      id: z.number(),
      name: z.string(),
      isAdmin: z.boolean(),
    })
    .optional(),
});

export const ctx = zodiosContext(user);

I'm trying to export ctx in a similar way to how it's done in the next.js example, but I'm getting an error that says Property 'context' of exported class expression may not be private or protected. ts(4094).

You need to not emit .d.ts files (if you are not a library aithor, no reason to emit them) so set  "declaration": false` in your tsconfig, it's an issue with typescript d.ts hability to represent private fields in classes when exporting d.ts files.
Since this behaviour is bad, if you are a library author, you can also also wait for version 9 of @zodios/express

fixed in version v0.3.4

repo: ecyrbe/zodios-express

license: MIT

license_source: github-api


text:
Upgrade composer v1 to composer v2 for php 7.4

Current version for php 7.4 is not compatible with composer v2.0

cau you remove hirak/prestissimo from the images with composer v2 too?
thanks

I removed this image from all php versions with composer v2, thanks for review.

PR #113 has been merged, so can this one about Composer v2 be completed now?

Any info on the conflicts?

Could this be added in such a way that I can choose to have composer 1 or 2 ?
Perhaps keep the current for composer 1
image: edbizarro/gitlab-ci-pipeline-php:7.4
and for composer 2:
image: edbizarro/gitlab-ci-pipeline-php:7.4-composer2

source: gharchive/pull-request

authors: GlennM edbizarro evs-xsarus jacobnollette rsereir

repo: edbizarro/gitlab-ci-pipeline-php


text:
Edde\Job: Initial implementation

Edde\Thread is now implementing whings not related to threads. There should be general Job package for this kind of tasks.

Done.

repo: edde-framework/edde-framework


text:
Se beskrivning

Tog bort gammal kod, fixa DB generering för SUM, Uppdatera TD, la till setup.bat fil för generering av exe.

we

repo: eddieKarlsson/automation-boilerplate


text:
WIP feat: add support for nullable types

This PR adds support for nullable types.
It changes the way schemas/expanders/flatteners are generated to support props that are pointers in kOps code.
This is a huge change and breaks the current terraform code but i think it's an important change to do.

Closing, it was too much changes and has been adressed in another PR.

repo: eddycharly/terraform-provider-kops


text:
Districts by Region and Settlements by district returns 404 error

Methods Districts by Region and Settlements by district  of the API UAaresses returns 404 error on DemoApi
Request: GET http://demo.ehealth.world/api/uaddresses/regions/45311788-3735-4ccf-884c-409c089f3a45/districts
Response: {"meta":{"url":"http://api-svc.uaddresses/regions/45311788-3735-4ccf-884c-409c089f3a45/districts","type":"object","request_id":"f81b493d-d5a9-4da9-942a-a4a136221062#8098","code":404},"error":{"type":"not_found"}}
But the region with this id is present:
Request: GET http://demo.ehealth.world/api/uaddresses/regions?koatuu=1200000000
Response: {"paging":{"total_pages":1,"total_entries":1,"page_size":10,"page_number":1},"meta":{"url":"http://api-svc.uaddresses/regions","type":"list","request_id":"e89715c9-d2ef-467a-b09a-419ca3888902#10486","code":200},"data":[{"name":"ДНІПРОПЕТРОВСЬКА","koatuu":"1200000000","id":"45311788-3735-4ccf-884c-409c089f3a45"}]}

Correct URL should look like:

http://demo.ehealth.world/api/uaddresses/details/region/45311788-3735-4ccf-884c-409c089f3a45/districts

The same problem with searching settlements by districts
Correct should be :

http://demo.ehealth.world/api/uaddresses/details/district/district_id/settlements

I was persuaded that the specification would be corrected

OK. That's good.

authors: Joyker lionsoft


text:
Add: Overcast

The Overcast logo was based on the logo seen on the page linked below.
https://overcast.fm/

Great stuff, thanks!

authors: Fmressel edent

repo: edent/SuperTinyIcons


text:
ImgBot savings

@edent As requested in https://github.com/edent/SuperTinyIcons/issues/478#issuecomment-723659800, this is what ImgBot has distilled. Each of the included files is just a few bytes smaller (mostly whitespace), so I don't know how welcome that is.  Also, I've included a custom .imgbotconfig which specifically excludes the reference folder.  Let me know what you think! 🙇🏾♂

I'll go through when I can & check for what savings other than whitespace, but why insist on such?  It's much easier to check before/after if both are with/without such, &, @ these sizes, removing whitespace tends to be significant.

I don't think I was clear enough. A \n takes up the same number of bytes as a space. So we use newlines for readability. That also makes it easier to see what a diff has done.
I've just pushed some changes which removed Windows style newlines from some files, and trailing newlines from the end of some files.
I'd be interested to see whether imgbot makes any file savings against these newer, smaller files.
Thanks for your work on this, it is appreciated.

Eyeballing it, it looks like it got some missed leading 0.→. & similar.  I'll have ImgBot regenerate against the repo's current iteration asap.

Replaced by #485

authors: TPS edent


text:
Rework SET command

Proposed:
SET CONFIG foo := 1;
SET GLOBAL var := 'aaa';
SET MODULE my_foo;
SET ALIAS bar AS MODULE mybar;

RESET CONFIG foo;
RESET GLOBAL var;
RESET MODULE;
RESET ALIAS bar;
RESET ALIAS *;

Using globals in queries:
CREATE GLOBAL my::foo;
SELECT (GLOBAL my::foo);

Using config values in queries:
SELECT
sys::Config.foo

where sys::Config is a special view containing all configuration variables.

Fixed in #354

With the "CONFIGURE" command implemented I think this issue is safe to close now.

repo: edgedb/edgedb


text:
edgedb.errors.ClientConnectionFailedError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate (_ssl.c:1129)

EdgeDB Version: image: edgedb/edgedb
EdgeDB CLI Version:
OS Version: windows 10 docker

using:
docker compose file
basic.py
Steps to Reproduce:
1.docker compose up -d
2.python -m basic
docker compose file:

edgedb docker container logs before connecting to edgedb

snippet in basic.py

edgedb docker container logs after connecting to edgedb

after connect to edgedb using basic.py

related issue:
https://github.com/edgedb/edgedb-python/issues/223
just can't figure out the problem related to which,  edgedb, container, python client, setting or code

Thanks for your reply. after further dig into the doc, I think I need more time to grasp all stuffs of edgedb. I found some doc contents and code examples need to be  updated. after some days, I will give you feedback.


text:
UPDATE of object tables over SQL adapter

Ref #7294

No, it does not.
The cleanup was in the second part (dispatch.resolve) of resolving. Instead of having _resolve_InsertStmt, _resolve_DeleteStmt and _resolve_UpdateStmt, I was able to generalize down to just _resolve_DMLQuery.
Maybe this should be two separate PRs.


text:
Update version to 0.5.0

Signed-off-by: Jeremy Phelps jphelps@linuxfoundation.org

recheck

authors: JPWKU trcox

repo: edgexfoundry/core-command


text:
feat: Enable REST Device service as one of the default services running.

Added REST device service to be running by default
closes #277

Spot-checked seems to work fine. Are there any blackbox tests to go with this?

Not at this time.

repo: edgexfoundry/developer-scripts


text:
fix: change redis username from redis5 to default

FIXES: #3860
Signed-off-by: Valina Li valina.li@intel.com

If your build fails  due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-go/blob/main/.github/Contributing.md
PR Checklist
Please check if your PR fulfills the following requirements:

[x] I am not introducing a breaking change (if you are, flag in conventional commit message with BREAKING CHANGE: describing the break)
[x] I am not introducing a new dependency (add notes below if you are)
[ ] I have added unit tests for the new feature or bug fix (if not, why?)
[x] I have fully tested (add details below) this the new feature or bug fix (if not, why?)
[ ] I have opened a PR for the related docs change (if not, why?)

Testing Instructions

New Dependency Instructions (If applicable)

Codecov Report

Merging #4031 (702d8bd) into main (87560f2) will not change coverage.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##             main    #4031   +/-   ##
=======================================
  Coverage   47.20%   47.20%
=======================================
  Files         114      114
  Lines        9832     9832
=======================================
  Hits         4641     4641
  Misses       4804     4804
  Partials      387      387

Impacted Files
Coverage Δ

internal/security/secretstore/init.go
17.12% <0.00%> (ø)

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 87560f2...702d8bd. Read the comment docs.

repo: edgexfoundry/edgex-go


text:
Update app-service V2 API test data to add apiVersion

Fix #307
Signed-off-by: Ginny Guan ginny@iotechsys.com

This causes SmokeTest and FunctionalTest fail.

repo: edgexfoundry/edgex-taf


text:
Add Cauchy / Sellmeier dispersion models

Lots of common materials have Cauchy or Sellmeier coefficients, and adding an option to add this type of dispersion model would make life nice and easy for me. Allowing the user to pass an arbitrary function of wavelength into the software would also be pretty trivial because this is python, and that would be a useful extension.

Added something better - support for arbitrary functions of wavelength to be used in b157a55a0b5618d715ab8753b8803a980dea862b.

repo: edmundsj/rcwa


text:
Error: error:0909006C:PEM routines:get_name:no start line

Hello,
I was setting up my own Staticman instance thanks to the instructions given here but I'm getting the following error :
2020-03-15T17:43:42.739406+00:00 app[web.1]: (node:24) UnhandledPromiseRejectionWarning: Error: error:0909006C:PEM routines:get_name:no start line
2020-03-15T17:43:42.739448+00:00 app[web.1]:     at Sign.sign (internal/crypto/sig.js:112:29)
2020-03-15T17:43:42.739449+00:00 app[web.1]:     at Object.sign (/app/node_modules/jwa/index.js:152:45)
2020-03-15T17:43:42.739450+00:00 app[web.1]:     at Object.jwsSign [as sign] (/app/node_modules/jws/lib/sign-stream.js:32:24)
2020-03-15T17:43:42.739450+00:00 app[web.1]:     at Object.module.exports [as sign] (/app/node_modules/jsonwebtoken/sign.js:204:16)
2020-03-15T17:43:42.739451+00:00 app[web.1]:     at getSignedJsonWebToken (/app/node_modules/@octokit/app/dist-node/index.js:31:30)
2020-03-15T17:43:42.739451+00:00 app[web.1]:     at GitHub._authenticate (/app/lib/GitHub.js:58:21)
2020-03-15T17:43:42.739452+00:00 app[web.1]:     at /app/lib/GitHub.js:31:32
2020-03-15T17:43:42.739453+00:00 app[web.1]:     at new GitHub (/app/lib/GitHub.js:46:7)
2020-03-15T17:43:42.739454+00:00 app[web.1]:     at Object.module.exports.create (/app/lib/GitServiceFactory.js:11:14)
2020-03-15T17:43:42.739454+00:00 app[web.1]:     at /app/lib/Staticman.js:32:35
2020-03-15T17:43:42.739454+00:00 app[web.1]:     at new Staticman (/app/lib/Staticman.js:46:7)
2020-03-15T17:43:42.739455+00:00 app[web.1]:     at module.exports (/app/controllers/process.js:126:27)
2020-03-15T17:43:42.739455+00:00 app[web.1]:     at Layer.handle [as handle_request] (/app/node_modules/express/lib/router/layer.js:95:5)
2020-03-15T17:43:42.739456+00:00 app[web.1]:     at next (/app/node_modules/express/lib/router/route.js:137:13)
2020-03-15T17:43:42.739456+00:00 app[web.1]:     at /app/server.js:169:14
2020-03-15T17:43:42.739456+00:00 app[web.1]:     at Layer.handle [as handle_request] (/app/node_modules/express/lib/router/layer.js:95:5)
2020-03-15T17:43:42.739457+00:00 app[web.1]:     at next (/app/node_modules/express/lib/router/route.js:137:13)
2020-03-15T17:43:42.739457+00:00 app[web.1]:     at /app/server.js:144:14
2020-03-15T17:43:42.739457+00:00 app[web.1]:     at Layer.handle [as handle_request] (/app/node_modules/express/lib/router/layer.js:95:5)
2020-03-15T17:43:42.739457+00:00 app[web.1]:     at next (/app/node_modules/express/lib/router/route.js:137:13)
2020-03-15T17:43:42.739458+00:00 app[web.1]:     at /app/server.js:129:14
2020-03-15T17:43:42.739458+00:00 app[web.1]:     at Layer.handle [as handle_request] (/app/node_modules/express/lib/router/layer.js:95:5)
2020-03-15T17:43:42.739499+00:00 app[web.1]: (node:24) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)
2020-03-15T17:43:42.739592+00:00 app[web.1]: (node:24) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
2020-03-15T17:44:01.677846+00:00 heroku[web.1]: Stopping all processes with SIGTERM
2020-03-15T17:44:01.771568+00:00 heroku[web.1]: Process exited with status 143
2020-03-15T17:44:01.696691+00:00 heroku[router]: at=error code=H13 desc="Connection closed without response" method=POST
path="/v3/entry/github/Skyost/Bacomathiques/master/comments" host=skyost-staticman.herokuapp.com request_id=58374025-eb41-4ec4-81c3-5e139ae2ff05 fwd="91.160.105.117" dyno=web.1 connect=0ms service=18989ms status=503 bytes=0 protocol=https

Okay, seems the private key must be entered without line breaks. But I'm now encountering a http 500 error on the client side. Nothing particular on the server side.

repo: eduardoboucas/staticman


text:
Contrib fixes

Please see each commit message for more info.
Thank you :grin:

LGTM. I thought using a, i, u, e and o is a good choice rather than a to z. I never heard before a place in Indonesia without vocal alphabet.
Thank you @feryardiant

You should update your readme thought :grin:

Oops, forgot. It's updated.

authors: edwardsamuel feryardiant

license: mit


text:
Show player only if recent tab is visible

JIRA: https://openedx.atlassian.net/browse/MOB-1134
cc @aleffert @shahidtamboli

I am still working on it. There is problem with changing orientation with this change.

I am done fixing this issue.  Please review, @aleffert @shahidtamboli

:+1:

:+1:

repo: edx/edx-app-android


text:
adding commandd.

Some experiment.

@awais786: If this goes beyond an experiment, can you add an explanation and also explain why this should live in this repo. No need to respond unless you push forward with this later. Thank you!

@awais786: If this goes beyond an experiment, can you add an explanation and also explain why this should live in this repo. No need to respond unless you push forward with this later. Thank you!

@robrap I am checking how management command works from this package. But missing some thing. Package is installed in shell but not command not runs successfully.

@awais786  I think you should move the manage_users_by.py file from the admin/ to the management/commands folder.

@awais786 I think you should move the manage_users_by.py file from the admin/ to the management/commands folder.

@regisb I am checking some thing. But If i continue with this I will move that there. Thanks.

authors: awais786 regisb robrap

repo: edx/edx-django-utils


text:
Pull from private sekkrit repo

@nedbat @singingwolfboy
We need to do this; how can the bot read from a private repo?
I tried merging as is but it failed:

https://bugsnag.com/openedx-webhooks/openedx-webhooks-1/errors/55df72d98c759b9d281a0c37?event_id=55df72d97a636bc5291cb898

@singingwolfboy ping on this

@sarina that error message looks like a permissions error from GitHub. The GitHub user that the bot runs under does not have permission to view that repository. It has nothing to do with the bot's code.

@singingwolfboy yes, I understand that. My question as stated in the PR description is: "We need to do this; how can the bot read from a private repo?"

@sarina it looks like the edx-webhook-admin team is the one we've been using for this purpose. You can add repos to that team, and the users in that team will get admin access to those repos. The only user in that team is @edx-webhook, so that should be what you need.

It would be nice if we had an organization-level webhook such that any time a repo is added to the edX organization on GitHub, it is also added to this team. GitHub provides organization-level webhooks, so we could totally do this, we just haven't yet.

Yeah that would be a good idea. OK I'm going to try to merge this now and see what happens.

thanks that worked!

authors: sarina singingwolfboy

repo: edx/openedx-webhooks


text:
🛑 Nodo UTT Ramos Mejia is down

In 2348e82, Nodo UTT Ramos Mejia (https://www.uttnodoramosmejia.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Nodo UTT Ramos Mejia is back up in d22472b.

repo: efecear/upptime


text:
🛑 Nodo UTT Ramos Mejia is down

In bb33547, Nodo UTT Ramos Mejia (https://www.uttnodoramosmejia.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Nodo UTT Ramos Mejia is back up in b08fa8f after 10 minutes.


text:
🛑 Nodo UTT Ramos Mejia is down

In d90c42f, Nodo UTT Ramos Mejia (https://www.uttnodoramosmejia.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Nodo UTT Ramos Mejia is back up in 029389c.


text:
🛑 La Semilla Que Crece is down

In 18ac3b4, La Semilla Que Crece (https://www.lasemillaquecrece.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: La Semilla Que Crece is back up in cd79661.


text:
🛑 Nodo UTT Ramos Mejia is down

In 67f45c1, Nodo UTT Ramos Mejia (https://www.uttnodoramosmejia.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Nodo UTT Ramos Mejia is back up in d78ea2f.


text:
🛑 Nodo UTT Ramos Mejia is down

In f722948, Nodo UTT Ramos Mejia (https://www.uttnodoramosmejia.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Nodo UTT Ramos Mejia is back up in b8d462e.


text:
🛑 Almacén Reina Batata is down

In fd59aa5, Almacén Reina Batata (https://www.reina-batata.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Almacén Reina Batata is back up in 52a18c8.


text:
feat : Customise Job Requisition Doctype.

Is this a Feature, Chore or Bug?

Feature

Clearly and concisely describe the feature, chore or bug.
1.  Add a Work Details section with the following fields:

[ ] -           Number of Days Off (Integer)
[ ] -           Employment Type (Link, option: Employment Type)
[ ] -           Travel Required for the Position (Check)
[ ] -           Is Shift Work Needed (Check)
[ ] -           Driving License Needed for this Position (Check, shown only if Travel Required is checked)
[ ] -           License Type (Select, options: Light, Heavy, Motor Bike; shown only if Driving License Needed is checked)

2.  Add a Education and Qualification Details section with the following fields:

[ ] -           Minimum Educational Qualification (Select, options: Post Graduate Diploma in Journalism/Media , etc)
[ ] -           Minimum Experience Required (Float)

3. Create Language Proficiency Child Table with the following fields:

[ ] -           Language (Link, option: Language, Mandatory)
[ ] -           Speak, Write, Read (Rating)

4. Create Skill Proficiency Child Table with the following fields:

[ ] -              Skill (Link, option: Skill, Mandatory)
[ ] -              Proficiency (Rating, Mandatory)

Solution description
1. Work Details Section:

[ ] -       Implement the fields as described above.
[ ] -       Use "depends_on" to show Driving License Needed for this Position only when Travel Required for the Position is checked.
[ ] -       Use "depends_on" to show License Type only when Driving License Needed is checked.

2. Education and Qualification Section:

[ ] Implement the educational qualification and experience fields as described.

3. Child Tables:

[ ] Create two child tables (Language Proficiency and Skill Proficiency) with the relevant fields for proficiency assessment.

Output screenshots (optional)
Screencast from 10-03-2024 11:29:39 AM.webm
Areas affected and ensured

beams/setup.py
beams/beams/doctype/language_proficiency/
beams/beams/doctype/skill_proficiency/

Is there any existing behavior change of other features due to this code change?

No

Did you test with the following dataset?

Existing Data
New Data

Is patch required?

No

The best PR I've reviewed until now.

repo: efeone/beams


text:
🛑 Efficast Website is down

In 1a3dc7b, Efficast Website ($EFFICAST_WEBSITE_URL) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Efficast Website is back up in a125150 after 6 minutes.

repo: efficastai/status


text:
🛑 MY-Mikrotik-3 is down

In f5bbad9, MY-Mikrotik-3 (http://103.158.231.11:64000) was down:

HTTP code: 0
Response time: 0 ms

Resolved: MY-Mikrotik-3 is back up in 58c341f after 25 minutes.


text:
fix/#94 modify CMVTest

delete the TestCMV function, it was a function to test initCMV() before and is skipped. The cmv is test in DecideTest now

close #94


text:
新增lazy分支

备份plugins-setup.lua文件
新增plugins-setup.lua文件，配置lazy，保留原来插件
删除nvim/plugin文件夹

谢谢大佬~~~

authors: chiniun eggtoopain


text:
[CDR-1460] Align EHR controller with 1.0.3 spec

Changes

Aligned ehr API with spec

create returns now 201 instead of 204
Updated swagger doc for create with all possible return codes 201, 400 and 409

Refactored the EHR controller to have more control about the returned http codes
Added Unit tests for the EHR controller

Pre-Merge checklist

[x] New code is tested
[x] Present and new tests pass
[x] Documentation is updated
[x] The build is working without errors
[x] No new Sonar issues introduced
[x] Changelog is updated
[ ] Code has been reviewed

@micha1970 We need to switch back to the latest robot tests before merge -> https://github.com/ehrbase/ehrbase/pull/1371/commits/e003fee2131ea439753689dde4930995e171bf09#diff-f3bf042f595bb7cd2f582786da0bb18ee5da158fbda5d21be1d5cbc72096c296L47-R47

repo: ehrbase/ehrbase


text:
Demo: URL параметры из одной демо программы передаются в другую демо программу

Зайдите в демо программу $mol_app_lamps_demo и выберите первую лампу. URL станет следующим http://mol.js.org/app/demo/#demo=mol_app_lamps_demo/lamp=1.
Перейдите в другую демо программу выбрав ее в меню слева. Например выберите Hello.

Строка URL станет http://mol.js.org/app/demo/#demo=mol_app_hello_demo/lamp=1. В ней сохраниться параметр /lamp=1.
Строка URL должна поменяться на http://mol.js.org/app/demo/#demo=mol_app_hello_demo без параметра /lamp=1.

Насколько я помню, Дмитрий, вы говорили что это тоже фича. Хотя, замечу, не очевидная.

Да, фича, позволяет при переключении между видами сохранять параметры. Но в демо-приложении она действительно не нужна.

authors: AlexRadch nin-jin wmakeev

repo: eigenmethod/mol


text:
Number #24

Make new component Number

Не надо в git пулять .map файлы. :)

authors: jgluhov shanhaichik


text:
MEV on Gnosis Chain :)

https://blockscout.com/xdai/mainnet/tx/0x7b8ea7e55beb16810a5f5e358197395834fd2f857a7f9e41274ab70ac60a612c

Hi @franz101, thanks for your participation. The community and our team all benefit from your partaking.
You may have noticed that we are working on a complex transaction analyzer. This tool is still in the private test phase that only opens to a few users.
Although it can not dissect tx on Gnosis Chain, you are still more than welcome to join the specified discord channel for it. We look forward to your suggestions on features, bugs, and improvements. C'mon in!
https://discord.gg/kmjNKFvV

Hello there, thanks for participating in our just concluded "Awesome Transactions Bounty" program. In other news, we have a great update for you! It's the new analyzing tool called "EigenTx" which you can use to analyze and dissect your submission and other transactions you deem necessary or intriguing! Follow the link below to enjoy the experience.
https://tx.eigenphi.io/

repo: eigenphi/AwesomeTx


text:
Add server streaming support

The CLI generated will try to receive all messages from server. If there is any error when receiving, just exit.

@yxd-ym Hi! We just updated the internals of the generator to require less code generation and use more runtime reflection. Is there an example server you could point to that would let us test this? We can port this from generated code to runtime reflection if we just have something to test against. Cheers!

Here is a demo of client code generated with the development branch of this PR.
https://github.com/ycj-ymatrix/stream-service
The client code generated can be used to access a grpc server streaming API.

authors: odsod yxd-ym

repo: einride/aip-cli-go


text:
feat: add optional middleware for inserting security headers

This pr provides an optional middleware to add (response) security headers

@odsod Thanks, I confirmed we can set the headers on on the API-gateway. I will close this PR.

repo: einride/cloudrunner-go


text:
Buffer overflow due to integer overflow

[dependencies]
transpose = "0.2.2"

fn main() {
    let input = [0];
    let mut output = input;
    let width = (1 << (usize::BITS - 1)) + 1;
    let height = width;
    transpose::transpose(&input, &mut output, width, height);
}

This panics on integer overflow in debug mode but results in a segmentation fault in release mode since overflows checks are off.
Current safety checks (fail on integer overflow):
assert_eq!(input_width*input_height, input.len());
assert_eq!(input_width*input_height, output.len());

Possible new safety checks (catch integer overflow):
let area = input_width.checked_mul(input_height).expect("area overflow");
assert_eq!(area, input.len());
assert_eq!(area, output.len());

Also transpose_inplace uses similar checks but doesn't have any unsafe.

Heads up: this issue has been included in the RustSec advisory database. It will be surfaced by tools such as cargo-audit or Dependabot from now on.
Once a fix is released to crates.io, please open a pull request to update the advisory with the patched version, or file an issue on the advisory database repository.

Thanks for reporting. The inline version doesn't use unsafe, but I replaced the raw multiplication with a checked multiplication there too.

Thank you!
Please let me know once the fix is published to crates.io, and I'll update the security advisory with the fixed version.

https://crates.io/crates/transpose/0.2.3
Thanks to @caibear for reporting, thanks to @torokati44 and @Shnatsel for notifying me of impacts/consequences of the bug.

Added patched version to the advisory in https://github.com/rustsec/advisory-db/pull/1897. Thanks!

authors: Shnatsel caibear ejmahler

repo: ejmahler/transpose


text:
Move GH pages to server

Move from GitHub pages to it's own server on the domain nowsearch.xyz

Or check out if it is possible to use the GitHub page but with the nowsearch.xyz domain?

GH-pages are okay for now.


text:
[rfc] disable S3Object by default

S3Object seems to be contention for new configs out of the gate and often times it's not needed and just needs to be excluded.
Idea for V4, as a breaking change, why not exclude S3Object by default, make it explicit that it needs to be turned on?

Closing to track with #380, S3Object will be disabled by default in the next version

repo: ekristen/aws-nuke


text:
Changes in resourcepack?

Hi,
i'd like change a few icons, logo and description of official txt for this plugin - can I? And if i have a demo version, and i use this for medium server (20-50 players)  (if i will have a money for full version, i buy it - i promise!), will you be angry for me? This plugin is wonderful - i'm creating a polish version (translate).

It's no problem at all - the plugin is free and open, there is no full version :)
If you'd like to share your Polish translation, I'd love to add it to the set of localizations I have, but that's entirely up to you.

repo: elBukkit/MagicPlugin


text:
Revise approach to mutability of standard data structures

New - Plan for transition

Rename current Array type to ArrayList , List type to ImmutableList - (leave Dictionary as is)
Change from [ ] to { } for Immutable List
Allow ArrayList literals to be created using [ ]
Provide ArrayList with methods for add, remove - like a regular JS list
Add a ImmutableDictionary<K,V> type, with suitable methods
Make symbol table aware of whether each type is mutable or immutable (should also do this for all classes, if not already)
Implement rule that functions can accept only immutable types (including classes) as arguments
Implement rule that neither procedure nor function parameters may be set (re-assigned) (though for procedures they may be mutated via procedure methods, or (for ArrayList) by re-assigning an indexed value.
Provide type aliases e.g. [Int] for ArrayList<Int>, {Int}forImmutableList, [String, Int]` for Dictionary, and {String, Int} for ImmutableDictionary

Lists & Arrays
Change from current set up (mutable Array and immutable List) - to having a mutable array/list (like Python's) and and immutable list.

Create a mutable 'array/list' with all the capability of an array and a list, and implemented as a bog standard JavaScript list.

Literal form:  [a, b, c, d, e]
Type form:   [String] or [Int]  (in contrast to current forms of List<of String> or Array<of Int>
How to initialise an empty arrayList:   var a set to [string]
How to initialise an arrayList with a fixed number of empty values (for emulating old arrays): [string].size(5) or maybe even just [string](5)

Create an immutable list:

Literal form: {1,2,3,4,5}  note that (per #408) we will then stop using curly braces for anything else.
Type form:   {String} or {Int}
Dictionaries

mutable dictionary
Literal form: ["a":1, "b":3, "c":2]
Type form:  `[String:Int]

immutable dictionary
Literal form: {"a":1, "b":3, "c":2}
Type form:  `{String:Int}

Tuples
Are always immutable - as before.
Stack, Queue, Tree, Graph
Proposal is that these are all and only immutable. - as now These data structures are more advanced concepts anyway and it would be good to get pupils onto immutable data structures. There is the additional advantage that with dequeue and pop we don't run into the command-query separation issue. Both methods return a tuple consisting of the sought item and the revised data structure
The type-forms retain the current syntax for generics e.g.
Stack<of Int>
Graph<of Place, Int>

Limit all function parameters to immutable types only

ordinary value types
immutable versions of all standard data structures (per above)
immutable user-defined classes

Immutable types can hold references only to values or other immutable types
This applies to standard immutable data structures (per above) or to a user-defined immutable class
In neither a functions nor a procedure can you `set' (re-assign) a parameter (this would be compile error)
However in a procedure, if a parameter is a mutable reference type, you can mutate it:

If it is an ordinary list/array or dictionary by index e.g.
set p[0] to 3
By adding/removing from an ordinary list/dictionary
By calling procedure methods on the parameter

A constant may be set only with an immutable type

Currently waiting on RP to make decision concerning the type syntax & other issues

repo: elan-language/IDE


text:
Disable metrics when active=false

Currently, even if the agent is deactivated, it still sends metrics. We should change that.

I think this is a rethink on what active means. For example- if set on startup, should we do health check? Should we even establish a connection?
Definitely requires updating the documentation for this property in any case.

authors: eyalkoren felixbarny

repo: elastic/apm-agent-java


text:
Upload agent binaries as artifacts

What does this PR do?
With jenkins a common workflow regarding support cases was to create a draft PR and provide the link to the resulting agent snapshot build artifact from jenkins to users.
Our current GH actions workflow does not upload the agent binaries as separate artifacts, this is fixed by this PR.
Tested on my fork of this repo.
Checklist

[x] This is something else

[ ] I have updated CHANGELOG.asciidoc

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2023-03-22T12:23:22.329+0000

Duration: 15 min 58 sec

:grey_exclamation: Flaky test report
No test was executed to be analysed.
:robot: GitHub comments
Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

run benchmark tests : Run the benchmark tests.

run jdk compatibility tests : Run the JDK Compatibility tests.

run integration tests : Run the Agent Integration tests.

run end-to-end tests : Run the APM-ITs.

run windows tests : Build & tests on windows.

run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

authors: JonasKunz apmmachine


text:
Document Tech Preview feature to collect Lambda extension logs

With https://github.com/elastic/apm-aws-lambda/issues/256 the lambda extension by default now has the Tech Preview feature enabled to collect logs from the lambda extension. The logs then show up in the Kibana APM UI.
The functionality is opt-out, users can disable it by setting ELASTIC_APM_LAMBDA_CAPTURE_LOGS=false.
When enabled, logs are collected and sent to the APM Server's new logs Intake API (also in Tech Preview) and indexed into Elasticsearch.

As this might create noisy logs if used against APM Server / Integration < 8.5, we should proceed documenting it if possible or switching to opt-in

authors: lucabelluccini simitt

repo: elastic/apm-aws-lambda


text:
[BUG] AssemblyVersion downgrade between 1.5.1 & 1.5.3

Hi,
I noticed that AssemblyVersion was downgraded from 1.5.0 in 1.5.1 to 1.0.0 in 1.5.3.

This leads to build errors in the following configuration:

Lib A referencing Elastic.CommonSchema.Serilog 1.5.1.
Project B referencing lib A and Elastic.CommonSchema.Serilog 1.5.3.
And building project B

CSC : error CS1705: Assembly 'A' with identity 'A, Version=2.1.0.0, Culture=neutral, PublicKeyToken=null' uses 'Elastic.CommonSchema.Serilog, Version=1.5.0.0, Culture=neutral, PublicKeyToken=069ca2728db333c1' which has a higher version than referenced assembly 'Elastic.CommonSchema.Serilog' with identity 'Elastic.CommonSchema.Serilog, Version=1.0.0.0, Culture=neutral, PublicKeyToken=069ca2728db333c1'

Is this downgrade intended?

It was intended, we use this technique to avoid assembly binding issues by giving all Major.x releases the same identify. This allows us to strong name our DLL's without issue.
The fact we didn't in 1.5.1 is the bug, one we have to live with sadly.
We built and use tooling (https://github.com/nullean/nupkg-validator) to assert our nugetpackages ship dll's with the correctly versions:
See e.g from our CI output:
[version] Assembly: 1.0.0.0
[version] AssemblyFile: 1.6.0.0
[version] Informational: 1.6.0-alpha1.54+a4d1bd8f42bc61e76dd37c3016cba3384d41a89f

This should prevent this from happening again: :crossed_fingers:
Thanks for bringing this to our attention @RomainHautefeuille :+1:

authors: Mpdreamz RomainHautefeuille

repo: elastic/ecs-dotnet


text:
[QUESTION] - customization of Elastic.Extensions.Logging

Hi all,
I'm working on a  logger for .NET6 (and .NET Standard 2.0) that logs directly to Elasticsearch.  We currently use serilog, but I would like to reduce dependencies on other frameworks.
I looked at the source code for Elastic.Extensions.Logging and I cannot find any "customization" options.  A lot of static methods, almost no overrides, no delegates to change LogEvents, ....
Here are some examples of logEvent manipulation that I was thinking of.:

How can we change the user name? Currently the name is obtained from "Thread.CurrentPrincipal?.Identity?.Name". This is not always correct. Sometimes ClaimsPrincipal needs to be used.
How can we add other "enrichers" (to keep with the Serilog terminology?
How can we customize error handling (like logging via another logger in case there is a problem with the Elistic logger.?

All information and feedback very welcome.
Peter

I've opened #448 to address being able to to log event manipulation. This existed for Serilog already but not Extensions logging.

How can we customize error handling (like logging via another logger in case there is a problem with the Elistic logger.

This one is a bit tougher to implement since at the time of instantiating of logging builder no fallback loggers are materialised.
Here's a quick example of how to be notified of elastic search export failures.
loggingBuilder.AddElasticsearch(options =>
{
	//options.BootstrapMethod = BootstrapMethod.Failure;
}, channel =>
{
	channel.ExportResponseCallback = (r, b) =>
		Console.WriteLine($"statusCode: {r.ApiCallDetails.HttpStatusCode} items: {b.Count} time since first write: {b.DurationSinceFirstWrite}");
});

authors: Mpdreamz PCDiver


text:
action: release

What
Use GH actions for the releases when:

merge commits in the main branch
or tag creation starting with <major>.<minor>.<patch>

Tasks

[x] Publish to nuget
[x] Publish the releases

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2023-01-26T12:07:54.583+0000

Duration: 17 min 4 sec

Test stats :test_tube:

Test
Results

Failed
0

Passed
206

Skipped
2

Total
208

:robot: GitHub comments
Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

| or tag creation starting with ..
Just double checking that this means we can publish 8.4.0-alpha1 just the same as always?

just the same as always?

'[0-9]+.[0-9]+.[0-9]+.*'  is the pattern I used so, it should support 8.4.0-alpha1 and 8.4.0 or 8.4.0-foo-bar
Previously it was a bit fine defined with tag pattern: '\\d+\\.\\d+\\.\\d+(-(alpha|beta|rc)\\d*)?', comparator: 'REGEXP'
If you prefer, I can use the previous defined pattern so, we ensure it provides the same experience

The only comment I have is it could be possible to combine these flows e.g:
https://github.com/elastic/elastic-ingest-dotnet/blob/main/.github/workflows/ci.yml
That way it's a tad easier to keep everything in sync and only one thing runs whether on a tag or not.

That way it's a tad easier to keep everything in sync and only one thing runs whether on a tag or not.

Let me propose a reusable action, so both workflows can benefit from that implementation and avoid the duplication

Wait a minutes, I misunderstood your question.
We are using a different approach, one workflow per event or so, such as releases, or PRs. This will help us to distinguish the access to secrets since they cannot be accessed by defaults on PRs.
By doing so, there might be duplications, but will also avoid the usage of if conditions.
If you prefer one workflow to rule everything, we can try, though, we internally discussed to sue the mentioned approach for the shake of simplicity even though it might produce duplicated code.
What do you prefer?

| If you prefer one workflow to rule everything, we can try, though, we internally discussed to sue the mentioned approach for the shake of simplicity even though it might produce duplicated code.
| What do you prefer?
Whatever has us fall in line with the rest of the repositories @elastic/ci-robots  help us automate! :cat:
I personally prefer one workflow so that I have more confidence whatever runs on tags/main integration branches is what was ran on PR's.

I personally prefer one workflow so that I have more confidence whatever runs on tags/main integration branches is what was ran on PR's.

https://github.com/elastic/ecs-dotnet/pull/238/commits/a484ada1d9456a3671a1f705fb12209e1424bcb6 was the change I made to have one workflow per release type, while it was originally one workflow for both releases main or tags releases.
@pazone and I discussed about the benefits and came up with havin several workflows with branches filter (on: push: branches: - ... ), but with simple actions. Rather than havin a single workflow and a powerful action handling all branches cases (like in the PR).
I'd somehow keep it as is if no strong opinion to merge both workflows as we are using the approach in other places.

| I'd somehow keep it as is if no strong opinion to merge both workflows as we are using the approach in other places.
:+1:  Consistency trumps this style discussion

authors: Mpdreamz apmmachine v1v


text:
Support for throttle time on indexing stats

https://github.com/elastic/elasticsearch/pull/7896

Already implemented: https://github.com/elastic/elasticsearch-net/blob/develop/src/Nest/Domain/Stats/IndexingStats.cs#L32

sweet!

authors: Mpdreamz gmarz

repo: elastic/elasticsearch-net


text:
Improve Index name inference docs

This commit improves the readability of the index name inference documentation,
and updates paragraphs in line with client changes.
Closes #3914

merging this small change in


text:
"no connection available" when using DiscoverNodesOnStart

I'm using the following code snippet to read documents from Elasticsearch.
If I enable node discovery on start, I end up getting a no connection available error on my test cluster, apparently due to the fact that all cluster nodes are have both data and master roles.
2021/04/21 14:09:47 connecting to ES
2021/04/21 14:09:47 successfully connected
Discovered node [xxxxxxx]; http://10.x.y.z1:9200; roles=[data master]; [SKIP]
Discovered node [yyyyyyy]; http://10.x.y.z2:9200; roles=[data master]; [SKIP]
Discovered node [zzzzzzz]; http://10.x.y.z3:9200; roles=[data master]; [SKIP]
2021/04/21 14:09:48 getting document
2021/04/21 14:09:48 error performing request: cannot get connection: no connection available
2021/04/21 14:09:49 getting document
2021/04/21 14:09:49 error performing request: cannot get connection: no connection available
2021/04/21 14:09:50 getting document
2021/04/21 14:09:50 error performing request: cannot get connection: no connection available
^Csignal: interrupt

Commenting the DiscoverNodesOnStart: true, part allows the code to work properly.
Is this an expected behavior ?
Using github.com/elastic/go-elasticsearch/v8 v8.0.0-20210421122141-109055da9e51 with Elasticsearch 7.10.2

This definitely is not intended, the expected behavior is to skip master only nodes.
The v8 client is intended to be used with the next major release, could you try with the 7.12 release instead ?

I get the same behavior with
require github.com/elastic/go-elasticsearch/v7 v7.12.0

The problem seems to be here: https://github.com/elastic/go-elasticsearch/blob/master/estransport/discovery.go#L79
My node is only "data" + "master", so it gets skipped because it's not "ingest" too. Think maybe the line there (and above) should be if !isDataNode && !isIngestNode {

The fix has been released in the 7.13 version of the client, closing this issue.

authors: Anaethelion lcosmin

repo: elastic/go-elasticsearch


text:
Change BulkIndexerConfig to improve comptability with both Client and TypedClient

Hello,
The BulkIndexerConfig ask for a Client *elasticsearch.Client
// BulkIndexerConfig represents configuration of the indexer.
type BulkIndexerConfig struct {
...
	Client      *elasticsearch.Client   // The Elasticsearch client.
...
}

Even though it only use the transport part :
func (r BulkRequest) Do(ctx context.Context, transport Transport) (*Response, error)

So, if you use a TypedClient, you can't use it in BulkIndexerConfig, you will have to instantiate a Client only for the BulkIndexerConfig.
What I propose is to change the BulkIndexerConfig to ask for a Transport so it can be compatible with both Client and TypedClient
// BulkIndexerConfig represents configuration of the indexer.
type BulkIndexerConfig struct {
...
	Transport   esapi.Transport         // The Elasticsearch transport.
...

If you want, I already push the changes in a branch => https://github.com/ludovic-franconieri/go-elasticsearch/tree/bulk_indexer_transport
Thanks

Another way to address the issue is to allow "converting" a TypedClient to a Client. You can kind-of already do this, and it works, but gives a go vet error. Patch to fix at: #905
Maybe a helper or some such might be nice too.
Personally I'd say that's enough to consider this fixed, and would be better than changing bulkindexer: it's fairly straight-forward, compatible, and simple.


text:
Logstash fails to start without x-pack

I have a simple docker image that uses the default one and uninstalls x-pack:
ARG VERSION
FROM docker.elastic.co/logstash/logstash:$VERSION

# https://www.elastic.co/guide/en/x-pack/current/installing-xpack.html#xpack-uninstalling
RUN logstash-plugin remove x-pack

Said image is being used in a docker-compose, but the container fails to start with the error message:
[FATAL][logstash.runner          ] An unexpected error occurred! {:error=>#<ArgumentError: Setting "xpack.monitoring.elasticsearch.url" hasn't been registered>, :backtrace=>["/usr/share/logstash/logstash-core/lib/logstash/settings.rb:32:in `get_setting'", "/usr/share/logstash/logstash-core/lib/logstash/settings.rb:64:in `set_value'", "/usr/share/logstash/logstash-core/lib/logstash/settings.rb:83:in `merge'", "org/jruby/RubyHash.java:1342:in `each'", "/usr/share/logstash/logstash-core/lib/logstash/settings.rb:83:in `merge'", "/usr/share/logstash/logstash-core/lib/logstash/settings.rb:135:in `validate_all'", "/usr/share/logstash/logstash-core/lib/logstash/runner.rb:244:in `execute'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/clamp-0.6.5/lib/clamp/command.rb:67:in `run'", "/usr/share/logstash/logstash-core/lib/logstash/runner.rb:209:in `run'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/clamp-0.6.5/lib/clamp/command.rb:132:in `run'", "/usr/share/logstash/lib/bootstrap/environment.rb:71:in `(root)'"]}

The semi-official image from DockerHub seems to be working just fine.

It seems that the error was caused by some leftover xpack properties in the /usr/share/logstash/config/logstash.yml configuration file. It can be worked around the issue by removing the 3 xpack configuration entries, but ideally this should be done automatically when removing the plugin.
For completeness sake here is the updated Dockerfile:
ARG VERSION
FROM docker.elastic.co/logstash/logstash:$VERSION

# https://www.elastic.co/guide/en/x-pack/current/installing-xpack.html#xpack-uninstalling
RUN logstash-plugin remove x-pack
RUN sed -i '/xpack/d' /usr/share/logstash/config/logstash.yml

Shouldn't the plugin validate its own configuration instead of logstash? Just got bitten by this issue as well.

Adding my 2 cents here:
Please note that x-pack-plugin may not be preinstalled in all logstash versions (build arg) so that the command (and thus building the Dockerfile) may fail.
I just tested with 5.0.0, which fails, and with 5.6.3, which succeeds.

authors: aldaris kvalev mkoertgen

repo: elastic/logstash-docker


text:
[Feature] Add the ability to set a default data view

Is your feature request related to a problem? Please describe.
When setting multiple data views there is no way to specify a default.
Describe the resource you would like to have implemented.
In elasticstack_kibana_data_view within the data_view an optional default could be set something like:
data_view = {
  name            = "logs-*"
  title           = "logs-*"
  time_field_name = "@timestamp"
  namespaces      = ["backend"]
  default         = true
}

Describe the solution you'd like
A default data view can be specified, this is most beneficial when multiple data views are being set.
Describe alternatives you've considered
The only alternative is to set a default using the API. This currently works as it does not impact the state. It would be much more elegant if this could be done in Terraform though.
Additional context
n/a

Duplicates https://github.com/elastic/terraform-provider-elasticstack/issues/603

authors: DBolge tobio

repo: elastic/terraform-provider-elasticstack


text:
Is there a way to support multi-tenant?

Is there a way to support multi-tenant?  We're using the apartment https://github.com/influitive/apartment gem do multi-tenant.

I am using elasticserach with multitenant app (rails)
In my app, elasticsearch indexes are created by tenant.
When a tenant is created, its index (name is "#{Rails.env}-#{tenant.schema_name}") is automatically created at the same time.
I hope this will help.

Yeah, @kizashi1122 is right, this is something you have to set up in your application code, preferably using the index_name method.
The index doesn't have to be the real Elasticsearch index, it can an alias as well. Just note that you cannot index documents into an alias which points to multiple indices.

@mingc Closing this issue.

authors: karmi kizashi1122 mingc

repo: elasticsearch/elasticsearch-rails


text:
Release 0.27 fixes

What this PR does / why we need it: fixes from the QA

@Xartos @viktor-f do we merge this? as Cristi is off this week

authors: crssnd davidumea

repo: elastisys/compliantkubernetes-apps


text:
Move restore instructions and resources to /restore

[!warning]
This is a public repository, ensure not to disclose:

[ ] personal data beyond what is necessary for interacting with this pull request, nor
[ ] business confidential information, such as customer names.

What kind of PR is this?
Required: Mark one of the following that is applicable:

[ ] kind/feature
[ ] kind/improvement
[ ] kind/deprecation
[ ] kind/documentation
[x] kind/clean-up
[ ] kind/bug
[ ] kind/other

Optional: Mark one or more of the following that are applicable:

[!important]
Breaking changes should be marked kind/admin-change or kind/dev-change depending on type
Critical security fixes should be marked with kind/security

[ ] kind/admin-change
[ ] kind/dev-change
[ ] kind/security
[ ] kind/adr

What does this PR do / why do we need this PR?
The resources related to restore were spread out in the repository, this collects them in a single place.
Neither /docs nor /scripts felt correct, that's why we put them under a new root directory. If we, in the future, create restore scripts it could make sense to move the scripts under /scripts and the instructions to /docs.
Information to reviewers

Checklist

[x] Proper commit message prefix on all commits

Change checks:

[ ] The change is transparent
[ ] The change is disruptive
[ ] The change requires no migration steps
[ ] The change requires migration steps
[ ] The change upgrades CRDs
[ ] The change updates the config and the schema

Documentation checks:

[ ] The public documentation required no updates
[x] The public documentation required an update - link to change

Metrics checks:

[ ] The metrics are still exposed and present in Grafana after the change
[ ] The metrics names didn't change (Grafana dashboards and Prometheus alerts are not affected)
[ ] The metrics names did change (Grafana dashboards and Prometheus alerts were fixed)

Logs checks:

[ ] The logs do not show any errors after the change

Pod Security Policy checks:

[ ] Any changed pod is covered by Pod Security Admission
[ ] Any changed pod is covered by Gatekeeper Pod Security Policies
[ ] The change does not cause any pods to be blocked by Pod Security Admission or Policies

Network Policy checks:

[ ] Any changed pod is covered by Network Policies
[ ] The change does not cause any dropped packets in the NetworkPolicy Dashboard

Audit checks:

[ ] The change does not cause any unnecessary Kubernetes audit events
[ ] The change requires changes to Kubernetes audit policy

Falco checks:

[ ] The change does not cause any alerts to be generated by Falco

Bug checks:

[ ] The bug fix is covered by regression tests

Should this be marked an admin change, perhaps?

Should this be marked an admin change, perhaps?

To me it doesn't feel noteworthy enough but if you or someone else insist I'll add an admin notice!

I hope any and all internal and public documentation is updated to point to the moved files?

Looks like these two will need updating:
https://github.com/elastisys/compliantkubernetes/blob/945c36e8f859ce8c57fcea6a151fa59655ec008e/docs/operator-manual/disaster-recovery.md#L35
https://github.com/elastisys/compliantkubernetes/blob/945c36e8f859ce8c57fcea6a151fa59655ec008e/docs/operator-manual/disaster-recovery.md#L306

The harbor readme needs to have paths updated as part of this.

Maybe this one as well
https://github.com/elastisys/compliantkubernetes-apps/blob/83f21bf64006390d5bcc3b3e77e9227d9f3bb92d/migration/v0.25.x-v0.26.x/upgrade-apps.md#L118

Maybe this one as well
https://github.com/elastisys/compliantkubernetes-apps/blob/83f21bf64006390d5bcc3b3e77e9227d9f3bb92d/migration/v0.25.x-v0.26.x/upgrade-apps.md#L118

I don't think so since that would be the correct path for that version. However, the migration directory could probably be cleaned up a bit. I don't expect anyone running v0.25 at this point. :smile:

authors: Zash aarnq simonklb


text:
Error on clearing build folder and other issues

Elba constantly complains that it can't clear the build folder:
[2/3] Building targets...
     [error] Couldn't clear build directory K:\Code\Idris\recursion_schemes\target\build: access denied。 (os error 5)

Other todos:

Allow more defaults in manifest (due to convention over configuration):

targets.lib.path -> ./src
targets.test.name -> project_name-main_name
add targets.bin.path, which defaults to ./src, and then the field main becomes a subpath of it.
add targets.test.path, which defaults to ./tests.

Don't fetch index repeatedly during a short interval (5 mins?). (Did it has the same strategy with git resolution? Retrieving packages of git resolution seemed to be quite faster than index.)

Coloring the summary display to distinguish between the name-version and resolution.

For example:
Retrieving git/specdris 0.1.0 (git+https://github.com/vmchale/specdris#master)
^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
cyan              white                             grey

The latest commit has added some defaults to aid in the goal of "convention over configuration."
I think it still makes sense to fetch an index repeatedly even in short intervals, because you don't know if within that interval if the package index has updated.

authors: andylokandy dcao

repo: elba/elba


text:
Modify Documentation to reflect recent changes in HACS 2

In the new version of HACS, the interface is totally different. This pull request updates the documentation to create installation instructions for the current version of HACS and the previous versions.

coverage: 99.866%. remained the same
when pulling e02f4a781b355251567ecbfc72f75240db286aa9 on modify_docs_to_reflect_hacs_recent_changes
into 82d2b3fec6530e7e0785ef78c0c4f9d13c969624 on master.

authors: coveralls elchininet

repo: elchininet/custom-sidebar


text:
🛑 Instagram is down

In 443d1a7, Instagram (https://www.instagram.com) was down:

HTTP code: 502
Response time: 22835 ms

Resolved: Instagram is back up in 38f3213 after 5 minutes.

repo: eldikra/monitoreo


text:
feat(electric): Add server-side validation of null values incoming from Satellite clients

Admitedly, we're relying on client-provided SatRelation messages to decide whether any given column is nullable or not. So it's not a good protection against malicious clients.
I wish we didn't have to pass nullability info via SatRelation message from the server to the client and back. But apparently that's what we have to do since we're not storing the history of schema changes for every individual client.
This has to be tagged as a feature because it changes the SatRelationColumn message in the protobuf definition.
This PR is based on the changes made in https://github.com/electric-sql/electric/pull/320. Related to VAX-813.

ignore my comment (😊) - i looked at the rest of that protobuf definitition and it seems my memory was at fault, not your code....

authors: alco magnetised

repo: electric-sql/electric


text:
chore(docs): Update Fly deployment doc

Preview: https://deploy-preview-101--electric-sql-website.netlify.app/docs/deployment/fly

I think it's fair enough to minimise the info on how to setup Fly Postgres. That's a task for the Fly docs. I do think we should signpost what Fly is good for at the top of this page and then echo the phrasing we use in the section headings.
I.e.: "You can use Fly deploy the Electric sync service and, optimally, to also deploy Postgres. This guide covers two main scenarios: (1) use Fly to deploy the Electric sync service and connect to an external Postgre and (2) use Fly to deploy both Electric and Postgres and connect them over the internal network."
Then you can have those two sections as top level ## h2s in the actor nav. Focus the content on the first one (cutting out the client section and instead ending up on showing the URLs that the client, generator and migrations proxy will connect on and linking out to the usage or deployment concepts docs for those). Then have a short second section saying "when using Fly Postgres, go here for the docs and swap out the database url like this". With a warning that Fly Postgres is changing to use Supabase (link) so you may want to wait for that.
With the migrations proxy, fair enough, given Fly supports TCP, let's just document the primary path and minimise branching.

@thruflo I have made the changes we've discussed earlier:

removed a detailed walkthrough of setting up a client app
moved the Fly Postgres section below the primary "connect an external database" guide and extended it
added a short section at the bottom mentioning the Quickstart and the Basic example
added an overview of the two scenarios at the top
added a couple of mentions of the Deployment Concepts guide

You can review the actual changes starting from this commit. Click Next to go the next one. There are 5 new commits in total.
The preview page - https://deploy-preview-101--electric-sql-website.netlify.app/docs/deployment/fly.

authors: alco thruflo


text:
Add conversion s28f() (int8_t to float)

Feature suggestion: it would be nice to have conversion int8_t to float to the daisy core.
https://github.com/electro-smith/libDaisy/blob/master/src/daisy_core.h
I used this today to use some 8bit SID noise code with DaisySP, that generates int8_t as its output.
#define S82F_SCALE 0.00390625f     /**< 1 / (2**8) */
#define F2S8_SCALE 255.0f          /**< (2 ** 8) - 1 */

FORCE_INLINE float s82f(int8_t x)
{
    return (float)x * S82F_SCALE;
}

FORCE_INLINE int8_t f2s8(float x)
{
    x = x <= FBIPMIN ? FBIPMIN : x;
    x = x >= FBIPMAX ? FBIPMAX : x;
    return (int32_t)(x * F2S8_SCALE);
}

Two small thoughts:

I think  S82F_SCALE should be 1/((2**8) - 1) = 1/255, that way we'll get all the way to 1.f at 255.
The conversion to float should probably be bipolar. i.e. 0 will map to -1.f and 255 will map to 1.f. This would look something like

#define S82F_SCALE 0.00784313f     /**< 2 / 255 */
FORCE_INLINE float s82f(int8_t x)
{
    return (float)x * S82F_SCALE - 1.f;
}

authors: beserge makingsoundmachines

repo: electro-smith/libDaisy


text:
[Help] how to run the built application and npm run dev at the same time?

On macos unable to run built app and npm run dev at the same time.
If built app is running, then npm run dev returns

otherwise nothing happens.

Need comment this:
if (!app.requestSingleInstanceLock()) {
  app.quit()
  process.exit(0)
}

)

Maybe the following code is better.
- if (!app.requestSingleInstanceLock()) {
-   app.quit()
-   process.exit(0)
- }

The compiled application and launched through npm run dev get one pid. Because of this, I cannot run both the built and developed applications at the same time.
@caoxiemeihao How to make the assembled application get a name not from package.json.name?

app.getName()

If I understand correctly, then the OS generates a PID based on the application name. When assembled, the name is taken from package.json.name. When I run the built app and when I run the app from npm run dev they have the same PID. Because of this, I can't run a built app and a development app at the same time.
But if I specify a different name when building in package.json.name, then the assembled application gets a different name. And, as a result, another PID. But it's not convenient.
I want to substitute a name during assembly that is different from what is in package.json.name. How to do it?

repo: electron-vite/electron-vite-vue


text:
Cache JSON, fixes #756

Cache JSON, fixes #756

This requires server-side changes to reflect the options changed here.

Add to live nginx config. Beta doesn't need / want caching

authors: gamerlv lewisgoddard

repo: elementary/mvp


text:
🛑 Plex is down

In 3ff0302, Plex (https://plex.lepallec.tv/web/index.html) was down:

HTTP code: 403
Response time: 516 ms

Resolved: Plex is back up in e2568d7.

repo: elepallec/upptime


text:
🛑 Tautulli is down

In bc5ff58, Tautulli (https://tautulli.lepallec.tv) was down:

HTTP code: 403
Response time: 54 ms

Resolved: Tautulli is back up in 72e5ca9.


text:
Bad merge on master

I should not be pushing on github at this hour, and I am very sorry. I wanted to merge a commit into beta, but merged it into master. It broke kind of everything.
I have managed to revert the #182 pull request in the branch reverting-master. It should be the same state as before the merge and should be mergable into master to fix the situation. But I will not be messing with master today anymore and hopefully when somebody reviews this tomorrow, the fix will be easy (merge in aforementioned branch).
Again, I am very sorry. I will be available on email tomorrow if anyone needs me.

How I reversed it is with these commands in reverse order:
git revert --no-commit 5d88b0b
git revert --no-commit f3d2915
git revert --no-commit c1b8873
git revert --no-commit b12caa1
git revert --no-commit 71bc55b
git revert --no-commit d074b17
git revert --no-commit cf36c32
git revert -m 1 --no-commit 9830707
git revert --no-commit 7b0d87d
git revert -m 2 --no-commit 8e001bb
git revert --no-commit 5d147cc

master branch seems to be working fine

authors: gareins rambousek

repo: elexis-eu/lexonomy


text:
🛑 UCU - Web is down

In 72ab3f6, UCU - Web (https://ucu.edu.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: UCU - Web is back up in 05b3b7d.

repo: elfoche/monitoreo


text:
🛑 MCU - GAF is down

In 6a6ae56, MCU - GAF (http://produccion.cdeluruguay.gob.ar/GAF/forms/login.jsp) was down:

HTTP code: 404
Response time: 242 ms

Resolved: MCU - GAF is back up in 43cd505 after 6 minutes.


text:
🛑 UNER - DDJJ is down

In a2dfced, UNER - DDJJ (https://autogestion.uner.edu.ar/) was down:

HTTP code: 502
Response time: 783 ms

Resolved: UNER - DDJJ is back up in a91f2f3.


text:
If function has a logger as parameter use it!

I've a function like this
fn get_something(log: Logger) -> Result<bool, Error> {
  Ok(true)
}

I would like to use this awesome lib in order to log the error using the first parameter.
For more generic usage
 #[logfn(Err = "Error", fmt = "Failed Sending Packet: {:?}", logger = "my_obj.log")]
fn get_something(my_obj: MyObj) -> Result<bool, Error> {
  Ok(true)
}

If you are interested, I may send a PR!

that's a nice add. I would hope there's a better UX to do this, but idk if that's possible.
Something like:
 #[logfn(Err = "Error", fmt = "Failed Sending Packet: {:?}", my_obj)]
or similiar (without adding a new attribute)

I hope i'll have time this week to test this and maybe also release a new version (already changed some stuff and a bit of the API)
but if you want to play with this and update me that's welcome :)

I'm not so familiar with quore! macro. I've tried to implement but some compile errors appears. Could you suggest me some tools for debugging?
Thanks

Oh, wait, you want to pass a logger not an attribute.

Is the Logger behaving the some as rust's log?
Can you show me a real example of this?

Actually I'm using https://docs.rs/sloggers/0.3.2/sloggers/ because I would have different loggers.
An example of usage can be found here: https://github.com/slog-rs/misc/blob/master/examples/features.rs. The primary feature of this kind of logger is the child: you can create a logger adding some info to it. That infos are printed in every log line.
I would like to use that kind of instance here.
Are you interested?

hmmmm this is a totally different facade.
I'm using log and you want slog compatibility.
this won't be easily done without feature gating or a separate crate.

authors: allevo elichai

repo: elichai/log-derive


text:
[FEATURE] - Native Winforms Dark Mode

It appears that with .NET 9, Windows Forms might be getting a native dark mode component! Opening an issue to track the integration of native dark mode with the new .NET 9 rollout.
Additional context
https://build.microsoft.com/en-US/sessions/b946ccb6-bb6b-4641-acc7-b5fadba2881e

.NET 9 as well has libraries for natively retrieving system color... no more registry pulls!

This isn't due to hit release until probably 24H2... Going to backlog for now

Ok 24H2 is in rollout... re-investigating this for a potential 1.3.2 or 1.4 release

Aha!
https://learn.microsoft.com/en-us/windows/apps/desktop/modernize/ui/apply-windows-themes

repo: eliweitzman/EnterpriseTechTool


text:
fix: add dynamic min height for group components

Description

Fixes #377
Checklist

[ ] My code follows the contributing guidelines of this project.
[ ] I am aware that all my commits will be squashed into a single commit, using the PR title as the commit message.
[ ] I have performed a self-review of my own code.
[ ] I have commented my code in hard-to-understand areas.
[ ] I have updated the user-facing documentation to describe any new or changed behavior.
[ ] My changes generate no new warnings.
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] I have not reduced the existing code coverage.

Comments

Summary by Sourcery
Bug Fixes:

Add dynamic minimum height for group components to ensure consistent layout.

@anuragxxd, I've added the changeset, please review.

Hey @SalihuDickson, I can now only see the change-log & no other changes. What can be the case? Are you sure no changes are being missed due to the merge conflicts or git?

yh, it seems i might have accidentally effected the same changes the other PR i merged, so pulling the changes from main made this PR effectively useless. I'll go ahead and close it.

authors: SalihuDickson anuragxxd

repo: elixir-cloud-aai/cloud-components


text:
Implementes table renaming

Usage:
def change
  rename table(:foo), table(:bar)
end

This will rename the table "foo" to "bar".
Works with backward migrations

@josevalim green with integration test

Beautiful!

authors: bcardarella josevalim

repo: elixir-lang/ecto


text:
Feature/upgrade to kc22.0.1

migration to KC22

merged on develop

repo: elkman/keycloak-radius-plugin


text:
Style the site

“Reality is wrong. Dreams are for real.”

#60 Added Sidebar and changed style to make a toggle record button instead of start/stop/pause.

authors: ellisken gyazbek

repo: ellisken/Ling


text:
Re-introduce inputText intermediate value.

Unfortunately, I'm unable to find a solution that works for all cases. I tried out a few different tactics, but none were able to solve for every issue. This simply rolls back the changes since 7.2.0, while keeping the Nightwatch tests. Before merging, however, it needs to be decided what to with the failing Nightwatch tests. Either remove them completely, comment them out, or disable them individually (my vote) (https://github.com/nightwatchjs/nightwatch-docs/blob/master/guide/running-tests/disabling-tests.md).
Alternatively, the repo could just be rolled back to 7.2.0, but then we lose the awesome acceptance tests.
As a stop-gap measure in my own use, we're simply using 7.2.0, which works perfectly well for us.

Spectacular! Thanks for teasing apart the changes and tests. I'll merge this and #70 at the same time, make sure everything passes, then release and close.

Great. Thanks all. @bbqbaron could you please re-open https://github.com/elm-community/elm-datepicker/issues/63?

authors: bbqbaron jnoggle mbylstra

repo: elm-community/elm-datepicker


text:
Not utilizing 4090 GPU?

I got this to run, but it's at like .05fps on my 12900k and isn't utilizing my 4090 GPU even though I'm using the default CFG. Any ideas what to do?

Hello,
Can you check out this issue: https://github.com/eloialonso/diamond/issues/9
And see if it resolves it?

Closing due to inactivity. Feel free to re-open if needed.

authors: GitInMotion Zenchiyu eloialonso

repo: eloialonso/diamond


text:
bootstrapper always tries to establish unsecure COS connection

In https://github.com/elyra-ai/kfp-notebook/blob/master/etc/docker-scripts/bootstrapper.py#L75-L78 the client is always configured to utilize an unsecured (http) connection even though the S3 endpoint might be secured (e.g. https://s3-openshift-storage.apps.zero.massopen.cloud/).
The following information is displayed in the pod log file:
...
[I 23:16:17.874] 'untitled-0422231504':'Untitled' - Packages installed (27.886 secs)
[I 23:16:17.985] 'untitled-0422231504':'Untitled' - processing dependencies
[D 23:16:17.986] Starting new HTTP connection (1): s3-openshift-storage.apps.zero.massopen.cloud:80
[D 23:16:17.993]
http://s3-openshift-storage.apps.zero.massopen.cloud:80
 "GET /opf-datacatalog?location= HTTP/1.1" 503 None
[D 23:16:17.994] Incremented Retry for (url='/opf-datacatalog?location='): Retry(total=4, connect=None, read=None, redirect=None, status=None)
[D 23:16:17.994] Retry: /opf-datacatalog?location=
[D 23:16:17.994] Resetting dropped connection: s3-openshift-storage.apps.zero.massopen.cloud
[D 23:16:17.996]
http://s3-openshift-storage.apps.zero.massopen.cloud:80
 "GET /opf-datacatalog?location= HTTP/1.1" 503 None
[D 23:16:17.997] Incremented Retry for (url='/opf-datacatalog?location='): Retry(total=3, connect=None, read=None, redirect=None, status=None)
[D 23:16:18.397] Retry: /opf-datacatalog?location=
[D 23:16:18.398] Resetting dropped connection: s3-openshift-storage.apps.zero.massopen.cloud
[D 23:16:18.401]
http://s3-openshift-storage.apps.zero.massopen.cloud:80
 "GET /opf-datacatalog?location= HTTP/1.1" 503 None
[D 23:16:18.401] Incremented Retry for (url='/opf-datacatalog?location='): Retry(total=2, connect=None, read=None, redirect=None, status=None)
[D 23:16:19.202] Retry: /opf-datacatalog?location=
[D 23:16:19.202] Resetting dropped connection: s3-openshift-storage.apps.zero.massopen.cloud
[D 23:16:19.205]
http://s3-openshift-storage.apps.zero.massopen.cloud:80
 "GET /opf-datacatalog?location= HTTP/1.1" 503 None
[D 23:16:19.206] Incremented Retry for (url='/opf-datacatalog?location='): Retry(total=1, connect=None, read=None, redirect=None, status=None)
[D 23:16:20.807] Retry: /opf-datacatalog?location=
[D 23:16:20.807] Resetting dropped connection: s3-openshift-storage.apps.zero.massopen.cloud
[D 23:16:20.810]
http://s3-openshift-storage.apps.zero.massopen.cloud:80
 "GET /opf-datacatalog?location= HTTP/1.1" 503 None
[D 23:16:20.811] Incremented Retry for (url='/opf-datacatalog?location='): Retry(total=0, connect=None, read=None, redirect=None, status=None)
[D 23:16:24.014] Retry: /opf-datacatalog?location=
[D 23:16:24.015] Resetting dropped connection: s3-openshift-storage.apps.zero.massopen.cloud
[D 23:16:24.018]
http://s3-openshift-storage.apps.zero.massopen.cloud:80
 "GET /opf-datacatalog?location= HTTP/1.1" 503 None
Traceback (most recent call last):
  File "bootstrapper.py", line 626, in <module>
    main()
  File "bootstrapper.py", line 614, in main
    file_op.process_dependencies()
  File "bootstrapper.py", line 98, in process_dependencies
    self.get_file_from_object_storage(archive_file)
  File "bootstrapper.py", line 283, in get_file_from_object_storage
    self.cos_client.fget_object(bucket_name=self.cos_bucket,
  File "/opt/app-root/src/jupyter-work-dir/python3/minio/api.py", line 719, in fget_object
    stat = self.stat_object(bucket_name, object_name, sse)
  File "/opt/app-root/src/jupyter-work-dir/python3/minio/api.py", line 1138, in stat_object
    response = self._url_open('HEAD', bucket_name=bucket_name,
  File "/opt/app-root/src/jupyter-work-dir/python3/minio/api.py", line 1984, in _url_open
    region = self._get_bucket_region(bucket_name)
  File "/opt/app-root/src/jupyter-work-dir/python3/minio/api.py", line 1919, in _get_bucket_region
    region = self._get_bucket_location(bucket_name)
  File "/opt/app-root/src/jupyter-work-dir/python3/minio/api.py", line 1948, in _get_bucket_location
    response = self._http.urlopen(method, url,
  File "/opt/app-root/src/jupyter-work-dir/python3/urllib3/poolmanager.py", line 336, in urlopen
    response = conn.urlopen(method, u.request_uri, **kw)
  File "/opt/app-root/src/jupyter-work-dir/python3/urllib3/connectionpool.py", line 815, in urlopen
    return self.urlopen(
  File "/opt/app-root/src/jupyter-work-dir/python3/urllib3/connectionpool.py", line 815, in urlopen
    return self.urlopen(
  File "/opt/app-root/src/jupyter-work-dir/python3/urllib3/connectionpool.py", line 815, in urlopen
    return self.urlopen(
  [Previous line repeated 2 more times]
  File "/opt/app-root/src/jupyter-work-dir/python3/urllib3/connectionpool.py", line 805, in urlopen
    retries = retries.increment(method, url, response=response, _pool=self)
  File "/opt/app-root/src/jupyter-work-dir/python3/urllib3/util/retry.py", line 439, in increment
    raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host='s3-openshift-storage.apps.zero.massopen.cloud', port=80): Max retries exceeded with url: /opf-datacatalog?location= (Caused by ResponseError('too many 503 error responses'))

See https://github.com/elyra-ai/elyra/blob/master/elyra/util/cos.py#L39 how this was handled i the pipeline editor.

repo: elyra-ai/kfp-notebook


text:
Donate this repo to an org

This extension repo should be donated to an open source org, we should decide which org it best belongs to and figure out the steps to take.
Potential orgs (in order of probability)

elyra-ai
CODAIT
jupyterlab

The repo is now in the elyra-ai org

repo: elyra-ai/streamlit-extension


text:
Support attribute segmentation

Add packet pool for GATT packets
Remove reference to controller in gatt server
Segment attribute pdus according to l2cap mtu

/test

/test

repo: embassy-rs/trouble


text:
[WIP] Adding debug info to test isolation validation

This PR builds on the existing work to detect when tests are not isolated.
Debug info is extracted from backburner using the new getDebugInfo method, which allows us to provide information, including stack trace information, to end users. We output that debug info to the console to allow 'click to open' functionality from within the stack traces, and additionally provide a summary of the debug info to test output.
TODO:

[x] Add tests to ensure that, when backburner.DEBUG = true we gather and output debug info
[ ] Figure out correct version of ember-source

@rwjblue I think we're good here. Anything else you think I should add?

What about awaiting the isSettled?

IMHO, that should be separate

authors: rwjblue scalvert

repo: emberjs/ember-qunit


text:
Fix version number in properties file

Goal

Testing

Release Notes

WHAT:
WHY:
WHO:

#506  👈
master

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

Join @bidetofevil and the rest of your teammates on  Graphite

repo: embrace-io/embrace-android-sdk


text:
Allow schema attributes to overwrite common attributes set by LogWriterImpl

Goal

Testing

Release Notes

WHAT:
WHY:
WHO:

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#763
#762  👈
#761
#760
master

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

Join @bidetofevil and the rest of your teammates on  Graphite


text:
Seed class for managing mnemonic word and hex secrets

Need to be able to interact with secret seeds as either a hexadecimal string or 12/24 word mnemonic seed (or 13/25 with checksums). Do the proper math to be able to convert them in accordance with Monero's c++ implementation of it.

Keeping this issue open since I still want to add this new class to documentation

All good here

repo: emesik/monero-python


text:
More than one category search Downloads page bug

Only first category search chosen works if attributes in two categories are chosen (apparently-- as appears in number of search results)

Multicategory search on Downloads page works

repo: emgeier/sesame-street-image-corpus


text:
Basic Timeline

Hi All,
I wanted to propose a timeline for generating ideas.

March 16 - All proposed rules submitted and discussed
March 23 - Final 10 rules decided, authors assigned to topics
April 13 - Rough draft of rules submitted to repo

I'm just sort of putting this out there for us all, but personally I find it useful to have a time line (to break) to help me prioritize all the other things I'm working on.  Please amend this if you think it's unreasonable I just put this together as a starting point.

+1

Agreed. I created milestones with dates. We use them in the lab not to miss deadlines, it's pretty efficient.

@emhart Can you define "submitted and discussed"? Have we completed this? Now we have three days for the final rules?

@dlebauer I was hoping that we would have completed our discussion of the rules and begun to finalize them.  I'm going to send out on more request for rules and then try and synthesize them.

:+1:

authors: dlebauer emhart snim2 tpoisot


text:
A shout out to everyone.

Can I just say that I think SWC community/ Twitter / the internet is rad?  In reading through this paper two thoughts struck me.

This paper is pretty good right?  I enjoyed reading it and thought it was full of really useful advice.

Most of the authors have never met each other in real life.  Essentially nine strangers from myriad disciplines came together and wrote the aforementioned awesome paper.  That's pretty amazing when you think about it.  We used all the open tools that we teach to accomplish a completely distributed collaborative project.  Maybe others aren't impressed, but I'm really impressed by everyone's efforts.  So thank you everyone for all your work.  :clap:

+100!
On Oct 16, 2015 2:39 AM, "Edmund Hart" notifications@github.com wrote:

Can I just say that I think SWC community/ Twitter / the internet is rad?
In reading through this paper two thoughts struck me.

This paper is pretty good right? I enjoyed reading it and thought it
was full of really useful advice.
2.
Most of the authors have never met each other in real life.
Essentially nine strangers from myriad disciplines came together and wrote
the aforementioned awesome paper. That's pretty amazing when you think
about it. We used all the open tools that we teach to accomplish a
completely distributed collaborative project. Maybe others aren't
impressed, but I'm really impressed by everyone's efforts. So thank you
everyone for all your work. [image: :clap:]
—
Reply to this email directly or view it on GitHub
https://github.com/emhart/10-simple-rules-data-storage/issues/89.

I agree, :clap: :clap: :clap: everyone!
Thanks @emhart for organizing this!

Yes, thanks @emhart.  Next scotch is on me.

:clap: -- it's been a great experience, and I too think it's a pretty good resource.

+1

authors: emhart fmichonneau jhollist snim2 tpoisot


text:
Integration reports inaccurate data

When stations report N/A for a given value, GIRO presents as such (foe for example):

Which is also correctly displayed on prop.kc2g.com (no value displayed):

However the integration seems to be substituting this with 0.000:

This is inaccurate, and causes lots of drops in graphs over time. Instead, the integration should simply report unavailable when a given value is reported N/A.
Given measurements are not available from all stations at all times, I've created aggregate template sensors that take nearby station data and handle gaps as a workaround. While cumbersome, this effectively takes the average of 1 or more datapoints, and if all datapoints are 0 the state will fail to render as you cannot average an empty list of values, and the sensor will correctly report unavailable.
    - unique_id: sensor.ham_radio_propagation_solar_hf_foe_average
      attributes:
        friendly_name: Solar Data HF foE Average
      icon: mdi:format-wrap-inline
      unit_of_measurement: MHz
      state_class: measurement
      state: >
        {% set sensor_list = [
            states('sensor.ham_radio_propagation_solar_hf_foe_ga762') | float(default=0),
            states('sensor.ham_radio_propagation_solar_hf_foe_mhj45') | float(default=0),
            states('sensor.ham_radio_propagation_solar_hf_foe_pf765') | float(default=0)
          ]
        %}
        {{ sensor_list | reject('==', 0) | average | round(3) }}

Results with all sources shown:

Average template sensor output with gaps coinciding with N/A:

Expected behavior would be for the integration to take care of this natively. If a station is reporting N/A, do not substitute a 0 value.

Thanks a lot Michael, I’ll study next days to export “unavailable” value instead of 0.00
I’ll build new releases soon.
73

Hi @prenetic i've changed backend parser and now i see in HA the Undefined value when data is null.
Please check your graphs and give me your feedback.
'73

I see the breaks now, thank you!

resolved

authors: emics prenetic


text:
🛑 asg netman is down

In 64e5a46, asg netman (https://gymamsee.zapto.org/login/login.html) was down:

HTTP code: 0
Response time: 0 ms

Resolved: asg netman is back up in abee48b.


text:
Fixed tape not running tests

Apparently tape prefers it when you manually add ".js" onto the name of
the test file you pass to the CLI. I have fixed this issue in this commit.

The test script is what fixes the issue.

@emilbayes You gonna pull this? It fixes a pretty big issue.

Not with the package lock file and the reordering of the package.json. Otherwise I appreciate the effort very much

Wow it really matters if it's reordered lol.

You just really don't wanna merge this do you lol

repo: emilbayes/nanoassert

license: ISC


text:
The main window is not centered correctly when the scale factor is not 1.

Describe the bug
The main window is not centered correctly when the scale factor is not 1(my default 1.25).
To Reproduce
Steps to reproduce the behavior:

cargo new example
add eframe = "0.20.0"
run the following code

fn main() {
    eframe::run_native(
        "app_name",
        eframe::NativeOptions {
            centered: true,
            initial_window_size: Some(eframe::egui::vec2(960.0, 670.0)),
            ..Default::default()
        },
        Box::new(|_| Box::new(Application::default())),
    );
}

#[derive(Default)]
struct Application;

impl eframe::App for Application {
    fn update(&mut self, ctx: &eframe::egui::Context, _frame: &mut eframe::Frame) {
        eframe::egui::CentralPanel::default().show(ctx, |ui| {
            ui.heading("Hello World");
        });
    }
}

Expected behavior
The window is centered correctly.
Desktop (please complete the following information):

OS: Windows10
Version: 21H2

Did https://github.com/emilk/egui/pull/2651 solve this?

Did #2651 solve this?

No, same issue. The position difference is even greater.
One solution is to use winit::dpi::PhysicalPosition, but multiply inner_size by monitor.scale_factor () in the calculation of X and Y position.
I'm not sure if there is a better way.

This issue has been fixed on the latest branch.

authors: emilk zhatuokun

repo: emilk/egui


text:
Use named placeholders for translations and logs

This PR includes:

A new localize() function for translating strings
Improve log() to support placeholders
Use named placeholders for translations and logs

Okay, no problems found.

authors: dagwieers mediaminister


text:
Caution: With tests

This PR updates the with_tests branch to match the latest state of main, and introduces some approval tests for Typescript. I'm not super confident that this set of merges went correctly, so it would be worthwhile checking the state for - particularly - csharp and python. I have validated that the tests build and pass with dotnet test and pytest respectively, but I had to merge a whole bunch of things, and then revert the early "reset to starting position" commit.

Unfortunately I think there is too much mixed up in this PR for me to accept it as it is. A bunch of python tests that I had deleted seem to have reappeared. There are also changes in all the other language versions. Can you fix this PR so it's only the typescript subfolder that has updates?

Let me close and have another go. I was trying to bring this branch up to date with all changes on main so that it's easy to maintain in future. Otherwise you'll always need to separately backport changes instead of merging off the main branch.

authors: bobthemighty emilybache

repo: emilybache/Necklace-Refactoring-Kata


text:
git项目提示不是git项目

你好，出现此bug 请检查当前打开的项目文件夹下面是否含有.git 文件夹，或尝试重新打开vscode窗口。如果情况没有解决，请补充你所使用的vscode版本和系统版本。

这是一个正常使用中的项目，因为需要频繁提交代码，所以找到了您开发的扩展，代码仓库本身没问题， 也重启电脑、重启应用、单独打开项目而不是使用多文件夹的工作区

你好，本项目依据 git log 状态和 git worktree list 进行git 合法性验证，请补充此两条命令在项目路径中的执行结果。

authors: Veyhunk emjio

repo: emjio/git-auto-commit


text:
Remove sub-fact++ modules importability

I.e., remove them as Python importable modules.
Ensure all files are still included in the package build.
Closes #213.
Note, this is a remake of #214, but using a branch from this repository instead of a fork.

Review comment by @francescalb.

Review comment by @francescalb.

This has been done now, I think, @francescalb.

repo: emmo-repo/EMMO-python


text:
Update intro slides on exercises

Fixes #46

[x] Explain input args to solution functions
[x] Explain how exercise sessions will be organized

Thanks, @edoardob90. I added below a few comments.
Also, shouldn't we remove the Quarto slides annotations from this notebook too?

Well, I do want to have slides for the intro, not just a notebook: there's no Python code to evaluate. If you want a notebook, than I'll move the slides stuff under slides/ and leave the notebook without any annotation.

Done! ✅

repo: empa-scientific-it/python-tutorial


text:
Support max-len in Vue components

EMP-1908
resolves #1063
Ref issue
TEST
1- Here are some examples for testing ignoreUrls, ignoreStrings, ignoreTemplateLiterals rules, that can be applied in, for example, Home.vue
2- Run eslint in your project:
run build eslint-plugin-x
run pnpm install —frozen-lockfile in x-components
run npm run lint  and check:

It should ignore long urls in vue files
It should ignore long classes, for example line 331 in Home.vue
It should ignore icon files as ‘user-filled.vue’

This config seems not to be working properly

repo: empathyco/x


text:
Spottable: added guards and removed focused state

Checklist

[x] I have read and understand the contribution guide

[x] A CHANGELOG entry is included

[x] At least one test case is included for this feature or bug fix

[x] Documentation was added or is not needed

[ ] This is an API breaking change

Issue Resolved / Feature Added
Spotlight was taking a long time to run focus and blur
Resolution
Removed focused state and have a guard for focusWhenDisabled
Additional Considerations
doing some hacky things to avoid lifecycle methods, but this works.
Links
ENYO-5878

I've removed the failing 'should not re-render when a non-Spottable prop does not change' test, which was added when we originally added the shouldComponentUpdate lifecycle to Spottable, so no functionality has been changed from the initial Spottable implementation. To run such a test, we would need to consider turning Spottable into a pure component

authors: germboy rundmt

repo: enactjs/enact


text:
WRQ-188: Update core/platform and webos/platform

Checklist

[x] I have read and understand the contribution guide
[ ] A CHANGELOG entry is included
[x] At least one test case is included for this feature or bug fix
[x] Documentation was added or is not needed
[x] This is an API breaking change

Issue Resolved / Feature Added
Some platforms detected by core/platform and webos/platform are outdated.

There are platforms over ten years from their end-of-life.
Some platforms are not rigorously tested several years.
Thanks to interop activities of browser vendors, app developers need just a major compatible browser name and version like Chrome, 120.

Some APIs look unclear in a viewpoint of modules' roles and responsibilities.

core/platform provides 'touch' and 'touchscreen', and it could lead misunderstanding or a human error.
core/platform's role is to support app devs to cover compatibility issues, so detecting 'webos' is a different kind of feature. It looks better to provide 'webos' info in webos/platform since apps using webOS features should import @enact/webos anyway.

Resolution
core/platform

Outdated platforms will be deprecated in Enact 5.0.0
'type' is added that is one of 'desktop', 'mobile', 'webos', 'node', and 'unknown'
'browserName' is added that is of 'chrome', 'safari', or 'firefox' (Note that the value of this new property is different from the existing 'platformName' that will be deprecated in Enact 5.0.0)
'browserVersion' is added as a number (Note that its value is a float for 'safari' so that minor numbers can be compared for compatibility issues)
'touch' is replaced with 'touchEvent' as its actual meaning
'touchscreen' is replaced with 'touchScreen' to match camel case (Note that we're trying to detect touch screen devices, but it can't be perfect.)

core/webos

'webos' is added to check if the platform is webOS
'version' is added to check webOS version (from 3.x to 23)
'chrome' is added to check chrome version (just for detected webOS vrersions; recommend to use core/platform in general purpose)

Additional Considerations
Links
WRQ-188
Comments
Enact-DCO-1.0-Signed-off-by: Seungcheon Baek (sc.baek@lge.com)

Let's add the Changelog


text:
Select from object list

Allow selecting from a list of object files, instead of using a file picker and generating the relative path.
Need to figure out what approach to use to find available objects.

Released in v0.4.0.

repo: encounter/objdiff


text:
Promise support

I wish we could use this library with Promises and other ES6+ features like that:
simpleCrypto.asym.generateEncryptKey({ /* params here */ })
    .then((key, params) => simpleCrypto.asym.encrypt(key.publicKey, data))
    .then((enc, key) => simpleCrypto.asym.decrypt(usedKey.privateKey, enc))
    .then((data, key) => /* Do something with data and used key */)
    .catch(logError)

Or:
let key = await simpleCrypto.asym.generateEncryptKey({ /* params here */ });
let enc = await simpleCrypto.asym.encrypt(key.publicKey, data);
let dec = await simpleCrypto.asym.decrypt(key.privateKey, enc);
/* Do something with data and used key */

Instead of:
simpleCrypto.asym.generateEncryptKey(logError, function(keys){
    simpleCrypto.asym.encrypt(key.publicKey, data, logError, function(encrypted) {
        simpleCrypto.asym.decrypt(key.privateKey, encrypted, logError.bind(null, done), function(decrypted){
            // Do something
        });
    });
});

Would be nice to see simpleCrypt updated and maybe split it up in asym / sym files to reduce file size if just one part is needed (and there is no dependency between...).
I tried to test simpleCrypt with short and longer data string, but it fails with the existing example code? See #6

repo: encryb/simplecrypto


text:
Endless Key branding, part 1

This just changes the basics (user visible strings, icon). We still don't have a symbolic icon, but it's in the works.
The loading page will deserve its own PR.

@GeorgesStavracas I've updated screenshots and metainfo in https://github.com/endlessm/endless-key-flatpak/pull/27; I reverted my icon-related changes since yours are better here. They should merge cleanly, now.

authors: GeorgesStavracas cassidyjames

repo: endlessm/endless-key-flatpak


text:
[Request] a new tag for products : description/productDescription

I think having a string tag called description/productDescription will nice to have
so we can do something like this [1] or [2] , sure also we can easily use it within our api system
The main idea is a short version of context will be in this tag [not more than a few lines]
example [1] :

example [2]:

@hugovk

Since we already have a clear blockquote (>) as part of our contribution template, maybe we can just do this in Jekyll. I don't want to define large HTML/markdown blobs in the front-matter. The only exception so far is LTSLabel where we stuff a abbr tag, but description feels incorrect.
Seeing if this can be done in liquid.

you are just looking for the frontend side , this will also allow users to get product information though api
it will be nice to used in cli applications that show product information which also needs it though api

Nice addition @usta / @captn3m0 :+1: !
Product pages without a logo looks a little strange. Maybe we should add a default logo or remove it entirely in that case ?

@marcwrobel @captn3m0 we can use [prepare same or similar icon for simpleicons] for NA icons

I doubt simpleicons will accept it, but we could try.

We can add it directly in our template as well.

i think that logo which i shown above perfect for all applications

authors: captn3m0 marcwrobel usta


text:
Rename endpoints to endpoints4s

Organization name is now org.endpoints4s instead of org.julienrf
Artifact names are not anymore prefixed by endpoints- (e.g., endpoints-algebra has been renamed to just algebra)
Documentation is updated
scmInfo points to endpoints4s/endpoints4s

Fixes #593

I should probably also rename the endpoints package to endpoints4s but I’m worried about the migration effort for users. I’ll see if I can come up with a scalafix migration rule for that before…

Actually, it seems to easy to implement a reliable rewrite rule that renames the package endpoints into endpoints4s in user code. So, I’m considering doing that change. Any objections?


text:
chore(actions): update GitHub workflow actions

Update the actions in the GitHub Actions workflows to their latest versions.

Are any of these updates breaking changes?

Are any of these updates breaking changes?

Most of their breaking changes are to update their default Node.js runtime version to v16, and similar but none of them affect their current usage in this repository.

Ok great, merging.

authors: HexF VoltrexKeyva

repo: engineer-man/piston