text:
xpath won't match if namespaces contain capital letters

Expected behaviour
Custom namespaces defined in predicates using xpath shouldn't be case sensitive.
Actual behaviour
xpath doesn't evaluate correctly if a custom namespace in imposter definition contains upper case letters.
Steps to reproduce
Define an imposter with a predicate using xpath that uses uppercase letters in a custom namespace:
{   "port": 4545,   "protocol": "http",   "stubs": [     {       "predicates": [         {           "equals": {             "body": "A80135247"           },           "xpath": {             "selector": "//ns2:userid",             "ns": {               "soap": "http://schemas.xmlsoap.org/soap/envelope/",               "ns2": "http://www.SOMETHING.com"             }           }         }       ],       "responses": [         {           "is": {             "body": "xpath matched"           }         }       ]     }   ] }
Send a matching XML request:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:du0="http://www.SOMETHING.com">    <soapenv:Header/>    <soapenv:Body>       <du0:someservice>          <du0:someoperation>             <du0:service_information_in>                <du0:userid>A80135247</du0:userid>             </du0:service_information_in>          </du0:someoperation>       </du0:someservice>    </soapenv:Body> </soapenv:Envelope>
The response body will be empty. Change the namespace to be all small letters:
{   "port": 4545,   "protocol": "http",   "stubs": [     {       "predicates": [         {           "equals": {             "body": "A80135247"           },           "xpath": {             "selector": "//ns2:userid",             "ns": {               "soap": "http://schemas.xmlsoap.org/soap/envelope/",               "ns2": "http://www.something.com"             }           }         }       ],       "responses": [         {           "is": {             "body": "xpath matched"           }         }       ]     }   ] }
Send the same XML request again and the body will be 'xpath matched'.
...
Software versions used
OS         : Windows 7 x64
mountebank : 1.8.0
node.js    : v5.0.0
  (only if installed via npm)
Installation method :
  (npm, zip, tar, pkg, deb, rpm)

Log contents in mb.log when running mb --loglevel debug

info: [mb:2525] mountebank v1.8.0 now taking orders - point your browser to http://localhost:2525 for help
debug: [mb:2525] config: {"options":{"noParse":false,"nologfile":false,"allowInjection":false,"localOnly":false,"mock":false,"debug":false,"removeProxies":false,"heroku":false,"version":false,"help":false,"loglevel":"debug","configfile":".\
\imposter.json","port":2525,"pidfile":"mb.pid","logfile":"mb.log","ipWhitelist":["*"],"savefile":"mb.json"},"process":{"nodeVersion":"v5.0.0","architecture":"x64","platform":"win32"}}
info: [mb:2525] PUT /imposters
debug: [mb:2525] ::ffff:127.0.0.1:63430 => {"imposters":[{"port":4545,"protocol":"http","stubs":[{"predicates":[{"equals":{"body":"A80135247"},"xpath":{"selector":"//ns2:userid","ns":{"soap":"http://schemas.xmlsoap.org/soap/envelope/","ns2"
:"http://www.SOMETHING.com"}}}],"responses":[{"is":{"body":"xpath matched"}}]}]}]}
info: [http:4545] Open for business...
debug: [http:4545] ::1:63431 ESTABLISHED
info: [http:4545] ::1:63431 => POST /
debug: [http:4545] ::1:63431 => {"requestFrom":"::1:63431","method":"POST","path":"/","query":{},"headers":{"Host":"localhost:4545","Connection":"keep-alive","Content-Length":"443","Postman-Token":"84f361d2-af8b-120a-2f6e-0bc9e7bc0c5a","Cac
he-Control":"no-cache","Origin":"chrome-extension://fhbjgbiflinjbdggehcddcbncdddomop","User-Agent":"Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36","Content-Type":"text/plain;cha
rset=UTF-8","Accept":"*/*","Accept-Encoding":"gzip, deflate, br","Accept-Language":"en-US,en;q=0.8,de;q=0.6"},"body":"<soapenv:Envelope xmlns:soapenv=\"http://schemas.xmlsoap.org/soap/envelope/\" xmlns:du0=\"http://www.SOMETHING.com\">\r\n
  <soapenv:Header/>\r\n   <soapenv:Body>\r\n      <du0:someservice>\r\n         <du0:someoperation>\r\n            <du0:service_information_in>\r\n               <du0:userid>A80135247</du0:userid>\r\n            </du0:service_information_in
>\r\n         </du0:someoperation>\r\n      </du0:someservice>\r\n   </soapenv:Body>\r\n</soapenv:Envelope>"}
debug: [http:4545] ::1:63431 no predicate match
debug: [http:4545] ::1:63431 generating response from {"is":{}}
debug: [http:4545] ::1:63431 <= {"statusCode":200,"headers":{"Connection":"close"},"body":"","_mode":"text"}
debug: [http:4545] ::1:63431 CLOSED

Just confirmed that URL cases have to match, so the bug is only about capital letters, not also about mismatched cases. Appears to be a bug in the xpath npm library, working on it now.

Nope, the xpath module is fine. It has to do with the case insensitive matching code in predicates.js; the case transform isn't given to the namespace mapping.

authors: bbyars mkokott

repo: bbyars/mountebank


text:
1.2.8 release is in progress - waiting for conda recipe - installations could be unstable

1.2.8 release is in progress - waiting for conda recipe - installations could be unstable

bcbio 1.2.8 is released

source: gharchive/issue

repo: bcbio/bcbio-nextgen

license: MIT

license_type: permissive

license_source: github-api


text:
Cast receiver for bible kids

The bible kids app should have its own cast receiver with bible kids' logo etc.
Also, the way it is now, you can open a video in bcc media, then open bible kids and it will show in the mini player there too..

Has its own receiver/appId now from v4.6.5 but its not customized.

I'd wait for the app redesign to ensure the vibe is the same

sp?

2

Because we included actual casting from the device as well, this ended up a bit bigger. Maybe 3sp.

v5.0.8

authors: andreasgangso mulundapm

repo: bcc-code/bcc-media-app


text:
tmp disable changeDoc, until it will be implimented on the CMS (ATM t…

…he changeDoc's only slow down the api)

Hey @laurensgroeneveld
Thanx for the review, i made the changes you suggested.
I removed the test instead of just skipping them though, since we an any case removed the code that the test is related to

source: gharchive/pull-request

repo: bccsa/luminary


text:
Allow replacing entire components

Allow replacing an entire component from an output, if a component output's property value is empty.

@forman , what is the reason behind this issue? What problem are we solving here?

I have the following use case which should be typical:
If have a button supposed to start processing data. It has id "update". Once users click it, processing starts and I want to replace the button by a circular progress (of the same size) using the same id "update". As you can see, no properties involved.

authors: b-yogesh forman

repo: bcdev/chartlets


text:
DSTUMacs fail to auto-reset

The DSTU7564Mac and DSTU7624Mac implementations do not call reset() as part of doFinal(), leaving the two MACs as one shot implementations. In addition reset() is not called as part of init(), so that a second identical call to init() will change the MAC state instead of preserving it.
`   /**
* Run Tests.
* @param pArgs arguments
*/
public static void main(final String[] pArgs) {
TestDSTUreset(new DSTU7564Mac(512));
TestDSTUreset(new DSTU7624Mac(128, 128));
}
/**
 * Test DSTUreset.
 * @param pMac the mac
 */
private static void TestDSTUreset(final Mac pMac) {
    /* Define message and key */
    final byte[] myMessage = "1234567890123456".getBytes();
    final byte[] myKey = "A123456789B12345".getBytes();

    /* Define buffers */
    final int myOutSize = pMac.getMacSize();
    final byte[] myFirst = new byte[myOutSize];
    final byte[] mySecond = new byte[myOutSize];

    /* Run the Mac twice without reInitialising */
    pMac.init(new KeyParameter(myKey));
    pMac.update(myMessage, 0, myMessage.length);
    pMac.doFinal(myFirst, 0);
    pMac.update(myMessage, 0, myMessage.length);
    pMac.doFinal(mySecond, 0);
    if (!Arrays.areEqual(myFirst, mySecond)) {
        System.out.println(pMac.getAlgorithmName() + " did not reset after doFinal() properly");
    }

    /* Manually perform the reset */
    pMac.reset();

    /* Initialise the mac twice */
    pMac.init(new KeyParameter(myKey));
    pMac.init(new KeyParameter(myKey));
    pMac.update(myMessage, 0, myMessage.length);
    pMac.doFinal(mySecond, 0);
    if (!Arrays.areEqual(myFirst, mySecond)) {
        System.out.println(pMac.getAlgorithmName() + " did not re-init properly");
    }
}

`

I think you've just set a new record for us. Thanks, will get it fixed as soon as I've finished dealing with 1.62.

Now fixed, will show up in 163b07 in a couple of days. Thanks for the report.

authors: bcgit tonywasher

repo: bcgit/bc-java


text:
Update Poly.java

Fix the bug

This is not a bug, but the latest change NIST announced during their 5th PQC conference. More information can be found below
https://github.com/bcgit/bc-java/issues/1734#issuecomment-2214314034

authors: chchen-scholar roy-basmacier


text:
Separate Showcase Scenarios Frontend

Each scenario have its own number of steps
Separate each scenario in its own frontend folder/module
Update OpenShift deployments

To keep the demo in the same codebase I'm experimenting with using custom configurations like bcwallet

repo: bcgov/BC-Wallet-Demo


text:
Configure pg_tileserv to run as wwwsvr

Process currently being managed by s6

Still need to:

[ ] direct logs to log file
[ ] add the startup script to source code

Closing this as the new servers will use systemd to to control these services.

repo: bcgov/BCHeritage


text:
Obtain ministry Mapbox account and generate API Keys

[x] Obtain ministry MapBox account
[x] Generate BCFMS API Key
[x] Generate BCRHP API Key
[x] Install BCFMS API key in ansible config
[x] Install BCRHP API Key in Ansible config

To do

Determine if MapBox API keys should be limited by URL

Currently using same API key in all environments.
Public key not limited by URL works. Should look into whether we should/can lock that down.
Satellite base map to be used on public website


text:
Crashing Pods

Describe the bug
Pods are crashing and sysdig is sending notifications.  This ticket is to investigate and if the fix is low effort, fix it.  If the fix is medium or high effort, create tickets for fix.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behaviour
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Logs/tracebacks
Additional context
Add any other context about the problem here.

This seems to have been a database pod with crashing pgbackrest container due to OOM (out if memory) crash. We investigated it but were unable to find the cause so we reset it with patronictl reinit and then also completely killed the pod and restarted it.
We then manual ran the pgbackrest cronjobs and there were no issues, as well as checking on it today everything seems in order again. We will continue to monitor this and ensure it doesn't come up again and if so maybe try giving the container a little bit more cpu and memory.

authors: MarsRomer marcellmueller

repo: bcgov/CONN-CCBC-portal


text:
Moving SIMS PROD Staging changes to release v1.0.0 branch

Updating the release/v1.0.0 branch with the latest changes on Openshift files.

Thanks updating the release branch 👍

authors: andrewsignori-aot dheepak-aot

repo: bcgov/SIMS


text:
Strata/Host - UI: Strata learn more url

Issue:

bcgov/entity/issues/

Description of changes:

add missing strata doc learn more url in nuxt config
add document types to base layer to be used by strata and host
add document type to registration response

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the BC Registry and Digital Services BSD 3-Clause License

Temporary Url for review: https://strr-strata-hotel-dev--pr-421-bu8eszjk.web.app

Temporary Url for review: https://strr-hosts-dev--pr-421-mwr52swz.web.app

Temporary Url for review: https://strr-strata-hotel-dev--pr-421-bu8eszjk.web.app

Temporary Url for review: https://strr-hosts-dev--pr-421-mwr52swz.web.app

repo: bcgov/STRR


text:
SIMSBIOHUB-486: Update Manage Animals Species and Observations Table Species Menus with Lastest Component

Links to Jira Tickets

https://apps.nrs.gov.bc.ca/int/jira/browse/SIMSBIOHUB-486?

Description of Changes

updated critter interfaces to contain itis_tsn & itis_scientific_name
Integrated Species Auto Complete field on Animals Page for Add new Animal
Integrated Species Option Cards on observation species select

Testing Notes

{List any relevant testing considerations, necessary pre-reqs, and areas of the app to focus on. Specifically, include anything that will help the reviewers of this PR verify the code is functioning as expected.}

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 76.68%. Comparing base (a7cdac3) to head (109a840).

Additional details and impacted files
@@           Coverage Diff           @@
##              dev    #1224   +/-   ##
=======================================
  Coverage   76.68%   76.68%
=======================================
  Files         232      232
  Lines        9503     9503
  Branches     1344     1344
=======================================
  Hits         7287     7287
  Misses       1803     1803
  Partials      413      413

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

authors: KjartanE codecov-commenter

repo: bcgov/biohubbc


text:
SPIKE:  Multi-cloud PIM usage - Investigation on its capability to be used directly w AWS\GCP

Describe the Issue
A clear and concise description of what you want to happen.
Additional Context
Add any other context, attachments or screenshots
Acceptance Criteria
A set of pre-defined requirement that need to be met in order to mark the user story as ?done?.  See below for team agreement details.
.
.
.
.
.
.
.
.
.
.
.
Extra Template Info
Definition of Ready
These set of conditions will need to be met in order to bring a ticket into the sprint and start work. Protects the team from unclear requirements.
Issues (Task/Story/Spike) aligned to an EPIC and linked appropriately.
Assigned to the appropriate CPF MEMBER (and is not left blank in ZenHub) at the start of sprint (1st day of the sprint)
Acceptance has been defined for the issue and has been reviewed with CPF team and approved by the necessary approver.
Has been sized and estimated by the delivery team.
Detailed breakdown of the steps required to complete the story in the additional context
Any additional specifications have been documented, reviewed with CPF and approved by the necessary approver.
Acceptance Criteria
A set of pre-defined requirement that need to be met in order to mark the user story as ?done?.
It should be testable with no room for interpretation
It should be either ?pass? or ?fail?
It should be clear enough for business stake holders to understand
As part of the user story, it should be written from the user perspective
A well written acceptance criteria is great for

managing expectations
defining scope
reducing ambiguity
establishing testing criteria for QA
Given (Pre-condition)
When (Action)
Then (Outcome)

Definition of Done
These set of conditions are met for work to be considered as complete on an issue.
All acceptance criteria(s) have been validated.
All the necessary documentation for the issue has been uploaded to Teams.
Functionality has been tested when applicable.
Functionality has been demonstrated to the relevant stakeholders (where applicable).
Story has been scheduled for a Sprint Demo/community update and impacted teams invited to the Demo.
Stories accepted by PO and documented for potential sharing with impacted users.

Documented = Captured in Community Update (CU) deck
Release notes = aspirational goal of providing a bulleted list of features and changes that our users can touch. Was going to store them in our Cloud Pathfinder repo. Can also display to users in the CU

Closing this as all multi-cloud work will take place after the second cloud PaaS is available

authors: jon-mc-git lukegonis

repo: bcgov/cloud-pathfinder


text:
chore(ci): use Helm deployer action

That action may or may not be able to fix this PR.

Aged out.  Closing.

repo: bcgov/nr-oracle-service


text:
Adapt flyway to manage Registry database migrations

Describe the issue
As a developer, i'd like to adapt flyway to manage Registry database migrations.
Additional context
Have it integrated with the existing workflow.
Definition of done
Flyway is integrated with the existing workflow.

#192 can leverage this deliverable.

Document a plan to have this integrated to registry prod with zero downtime:

set up a new set of patroni db
set up a new registry api service using the updated deployment config with pre-hook migration container

ensure to pass the right params so dc will rollout on image change from IS platsrv-registry-flyway:prod

set up necessary nsp rules so the pre-hook migration container can run against new patroni master db
check inside new patroni master db to see if there is a schema table and schemas are up-to-date
migrate prod data to new patroni master db
if everything is running well, do a cutover to the new registry api from the oc route

repo: bcgov/platform-services-registry


text:
Debug Toolbar Array Post Data

The debug toolbar doesn't work when post data values are arrays.

Well, damn, I thought I had fixed that once before. Guess not. Will have to look into it.

Fixed in 6cd62f0

authors: EpicKris lonnieezell

license: mit

license_source: bigquery


text:
Add location to AST

I'm working on a tool that allows people to analyze regular expressions,
and as part of that I'd like to be able to output error messages with
character positions, and highlight relevant portions of the regular
expression.
I chose to add a loc property to each node to encapsulate the change,
but am open to other approaches if you'd prefer.

Looks good 👍
Please also update the changelog like here:

https://github.com/bd82/regexp-to-ast/commit/370369a88f97c72a262f864efbb27798f768829d

and I will trigger a release (maybe later today...)

@bd82 done!

0.5.0 is out, Thanks for the PR again 👍

https://www.npmjs.com/package/regexp-to-ast/v/0.5.0

Regarding your tool.
If what you are building includes a mini editor for regExps you may want to
evaluate building a Parser for RegExps using a higher level library, e.g Chevrotain.

https://github.com/SAP/chevrotain

I created a set of tools for building editor services for XML.

https://github.com/SAP/xml-tools

This includes functionality such as:

Partial Parsing (not stopping on first error).
Validations APIs.
Content Assist APIs.

I am not sure if the concept of RegExp editor is relevant for your use case.
Nor if the RegExp syntax is suitable for parsing by Chevrotain:

Can we tokenize regExps text? as Chevrotain has a separate lexing step.
Is Chevrotain's built-in error recovery even suitable for RegExp's syntax?

But maybe this is something you would like to investigate.
Cheers.
Shahar.


text:
Timetable fetching appears broken

Sup, just like the title suggests, the timetable fetching appears borked. No wonder since the WebUntis authors constantly change stuff around.
In order to reproduce:

Grab latest build directly from the GitHub CI, environment variables all set to the according credents
Boot container, try to access any lesson or timetable
Error appears in console, server returns generic 500 error

Docker logs are as following:
untis-server-1  | [Nest] 1  - 09/22/2024, 9:10:10 PM   DEBUG [UntisService] No cache for TIMETABLE.1 exists.
untis-server-1  | [Nest] 1  - 09/22/2024, 9:10:11 PM   DEBUG [UntisService] Session is invalid. Renewing now...
untis-server-1  | [Nest] 1  - 09/22/2024, 9:10:11 PM     LOG [UntisService] Fetching timetable range 9/15/2024 to 10/6/2024...
untis-server-1  | [Nest] 1  - 09/22/2024, 9:10:11 PM    WARN [ExpressAdapter] Content-Type doesn't match Reply body, you might need a custom ExceptionFilter for non-JSON responses
untis-server-1  | [Nest] 1  - 09/22/2024, 9:10:11 PM   ERROR [ExceptionsHandler] Server didn't return any result.
untis-server-1  | Error: Server didn't return any result.
untis-server-1  |     at Queue.onFailed (/app/node_modules/bull/lib/job.js:516:18)
untis-server-1  |     at Queue.emit (node:events:518:28)
untis-server-1  |     at module.exports.emitSafe (/app/node_modules/bull/lib/utils.js:50:20)
untis-server-1  |     at EventEmitter.messageHandler (/app/node_modules/bull/lib/queue.js:476:15)
untis-server-1  |     at EventEmitter.emit (node:events:518:28)
untis-server-1  |     at DataHandler.handleSubscriberReply (/app/node_modules/ioredis/built/DataHandler.js:80:32)
untis-server-1  |     at DataHandler.returnReply (/app/node_modules/ioredis/built/DataHandler.js:47:18)
untis-server-1  |     at JavascriptRedisParser.returnReply (/app/node_modules/ioredis/built/DataHandler.js:21:22)
untis-server-1  |     at JavascriptRedisParser.execute (/app/node_modules/redis-parser/lib/parser.js:544:14)
untis-server-1  |     at Socket. (/app/node_modules/ioredis/built/DataHandler.js:25:20)
OS: openSUSE Leap 15.5
Docker Version: Docker version 24.0.7-ce
Untis-ics-version: 0.7.2
If you need any further info I will provide it to you asap

As of recently Untis started combatting applications like mine by setting a secret limit as to the amount of classes you can fetch and will just randomly return with an empty body if you try to request over an unlisted amount of lessons. I had a 'workaround' on this that would fetch the lessons in separate requests but still all at once that I might bring back soon.
For the time being I suggest you put down the LESSONS_TIMETABLE_BEFORE and LESSONS_TIMETABLE_AFTER to a smaller number until it stops erroring out until I fix this issue. As I currently don't have access to a WebUntis instance I cannot work on it for a while, I'm in the process of trying to get access to a server in the meantime.

authors: bddvlpr doppelkorn

repo: bddvlpr/untis-ics-sync


text:
Advanced Generators Duping Gases

When Gas is inserted into the Gas Input, the Gas Input ignores the senders doTransfer parameter, resulting in the duping of the input gas.
I reported the gas dupe issue on Mekanism's issue tracker and they believe they found the cause:

It seems they are implementing handling for our gas incorrectly. In this line they are always inserting the gas as a fluid into their machines if they can. This is a mistake, as they are entirely ignoring our doTransfer parameter which is used for simulation.

So in essence what they are doing, when we ask their tile to simulate inserting gas (so we can see how much would fit and calculation an even distribution), they are just ignoring the fact it is a simulation, and increasing their contents regardless.
Versions

bdlib-1.14.3.12-mc1.12.2
generators-0.9.20.12-mc1.12.2
Forge 1.12.2-14.23.5.2847

The mod has been recently updated to MC 1.16, older versions are no longer supported.
I'm mass closing older issues to clear up clutter in the bug tracker.
If you find this issue still exists in the current version feel free to reopen it.

authors: NillerMedDild bdew

repo: bdew-minecraft/generators


text:
can not make & make install

[root@rudonx c]# pwd
/root/pg_subxact_counters-main/c
[root@rudonx c]# make
gcc -std=gnu99 -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Werror=vla -Wendif-labels -Wmissing-format-attribute -Wformat-security -fno-strict-aliasing -fwrapv -fexcess-precision=standard -O2 -fPIC -I. -I./ -I/usr/local/postgres12.9/include/server -I/usr/local/postgres12.9/include/internal  -D_GNU_SOURCE   -c -o pg_subxact_counters.o pg_subxact_counters.c
pg_subxact_counters.c: In function ‘pg_subxact_counters’:
pg_subxact_counters.c:198:15: error: ‘INT8OID’ undeclared (first use in this function)
               INT8OID, -1, 0);
               ^
pg_subxact_counters.c:198:15: note: each undeclared identifier is reported only once for each function it appears in
make: *** [pg_subxact_counters.o] Error 1

[root@rudonx c]# uname -r
3.10.0-1160.59.1.el7.x86_64

OS version : centos 7.9
PgSQL Version 12.9
May I know how to solve this issue，this extension can not support PgSQL 12.9 ？

Thanks for the report, fixed with https://github.com/bdrouvot/pg_subxact_counters/commit/e24d6effb4691fa2670f926e0eb0c56106392b73

authors: bdrouvot rudonx

license: PostgreSQL


text:
BVAL-508 Add the API for value extraction

@gunnarmorling I went for valueextraction for the package name as it's the title of your proposal.
I added the javadoc.

I fixed all your remarks.

@gsmet Are you going to add @ConstraintsApplyTo, too (replacement for HV's @UnwrapValidatedValue)?

I think we should get this committed first. @ConstraintsApplyTo is not a simple replacement of the existing annotation and we don't have an implementation yet. It should be part of a follow-up commit.

It should be part of a follow-up commit.

Ok.

Merged, thanks. I've pushed one more commit for some JavaDoc adjustments.

authors: gsmet gunnarmorling

repo: beanvalidation/beanvalidation-api


text:
Multiple column sorts?

Seems like this was partially discussed / referenced in the issue regarding turning off sorting, but I just wanted to clarify: are there any near-term plans / upcoming PRs to support multi-column / complex sorts (like in the way react-datagrid supports multiple column sorts basically by default)?
If not, perhaps we'll contribute one soon...
Thanks!

I don't have any concrete plans for multiple column sorting. I can see it's quite neat, though, and I can appreciate the idea.
Currently SurviveJS related efforts take most of time given that brings the bread to the table. My smaller projects like this are in "discuss issues and accept PRs" mode. :smile:
Given Reactabular's design, sorting logic (src/sort_column.js) isn't coupled with it. Now it's just provided with the distribution for convenience. I believe it would be a good idea to aim to extract that out of Reactabular and then provide instructions on how to use the logic with it. We might not need new hooks even. I think this would be a good way to solve it.
I did something similar with react-pagify. I was able to extract its core logic to segmentize.
The cool thing about this kind of split is that it allows you to reuse the logic outside of React. It's a little theoretical point at the moment, but I don't see any harm in that. Extension points like this are always good and consistent with the way people like to use npm.

Thanks for the quick response!
(Very much enjoyed the SurviveJS book by the way, glad you're continuing with that effort...)

There's support for sorting multiple columns now. I simplified the interface further in the current beta.

authors: JeffSanchez bebraw

repo: bebraw/reactabular


text:
"./run-latex swish" does not work

swish.log:
swish.log

Try running make instead. There are two supporting pdf's that are generated using dot that the makefile takes care of before rendering the swish document.

Fixed by installing Tex Live in its entirety and then making the docs

authors: laqrix vince-refiti

repo: becls/swish


text:
#213 - Added file param support for the API

Closes #213
Introduced Changes

The /api/v1/tasks endpoint now handles file input in the same way as the UI

The only caveat is that you cannot submit Tasks that rely on file parameters through the Swagger UI

Testing

Publish the demo package to Functionary
Fetch an authentication token from the API

curl -X POST http://localhost:8000/api/v1/api-token-auth -H 'accept: application/json' -F "username=" -F "password="

Submit a task to the num_chars_api test function

curl -X POST http://localhost:8000/api/v1/tasks/ -H 'accept: application/json' -H 'X-Environment-Id: <env uuid>' -H 'Content-Type: multipart/form-data' -F "function=<function uuid>" -F "file.function=@/path/to/file" -F 'parameters={"other_param": "hello world"}' -H "Authorization: Token <your auth token>"

Verify task runs as expected

New Changes:

All parameters, including file parameters, can be specified with param.<param_name>
You can now mix-and-match the way you write parameters

You can write out parameters as both -F param.<param_name>=val and -F 'parameters={"hello": "world"}' in the same request

File parameters still need to exist outside of the JSON string parameters if submitting through the command line

Migrated API request parameter parsing to the Serializers

repo: beer-garden/functionary


text:
SOR: debug DAI to USDC trade on mainnet

{
  sorGetSwaps(
    swapType: EXACT_IN
    tokenIn: "0x6b175474e89094c44da98b954eedeac495271d0f"
    tokenOut: "0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"
    swapAmount: "10"
    chain: MAINNET
    swapOptions: { maxPools: 5 }
  ) {
    returnAmount
  }
}

returns 0

GyroE pool is throwing when parsing fromRawPool

repo: beethovenxfi/beethovenx-backend


text:
Package Hoogle-5.0.1 and wreq-0.4.1.0 fail to build during install on Ubuntu 16.04

--- Installing helper binaries...
Progress: 2/3
--  While building package wreq-0.4.1.0 using:
      /tmp/stack21091/wreq-0.4.1.0/.stack-work/dist/x86_64-linux/Cabal-1.24.0.0/setup/setup --builddir=.stack-work/dist/x86_64-linux/Cabal-1.24.0.0 build --ghc-options " -ddump-hi -ddump-to-file"
    Process exited with code: ExitFailure 1
    Logs have been written to: /home/josiah/.stack/global-project/.stack-work/logs/wreq-0.4.1.0.log

    [1 of 2] Compiling Main             ( /tmp/stack21091/wreq-0.4.1.0/Setup.hs, /tmp/stack21091/wreq-0.4.1.0/.stack-work/dist/x86_64-linux/Cabal-1.24.0.0/setup/Main.o )

    /tmp/stack21091/wreq-0.4.1.0/Setup.hs:63:15: warning: [-Wdeprecations]
        In the use of type constructor or class ‘InstalledPackageId’
        (imported from Distribution.Package):
        Deprecated: "Use UnitId instead"
    [2 of 2] Compiling StackSetupShim   ( /home/josiah/.stack/setup-exe-src/setup-shim-mPHDZzAJ.hs, /tmp/stack21091/wreq-0.4.1.0/.stack-work/dist/x86_64-linux/Cabal-1.24.0.0/setup/StackSetupShim.o )
    Linking /tmp/stack21091/wreq-0.4.1.0/.stack-work/dist/x86_64-linux/Cabal-1.24.0.0/setup/setup ...
    Configuring wreq-0.4.1.0...
    Building wreq-0.4.1.0...
    Preprocessing library wreq-0.4.1.0...
    [ 1 of 15] Compiling Network.Wreq.Lens.Machinery ( Network/Wreq/Lens/Machinery.hs, .stack-work/dist/x86_64-linux/Cabal-1.24.0.0/build/Network/Wreq/Lens/Machinery.o )
    [ 2 of 15] Compiling Paths_wreq       ( .stack-work/dist/x86_64-linux/Cabal-1.24.0.0/build/autogen/Paths_wreq.hs, .stack-work/dist/x86_64-linux/Cabal-1.24.0.0/build/Paths_wreq.o )
    [ 3 of 15] Compiling Network.Wreq.Internal.OAuth1 ( Network/Wreq/Internal/OAuth1.hs, .stack-work/dist/x86_64-linux/Cabal-1.24.0.0/build/Network/Wreq/Internal/OAuth1.o )
    [ 4 of 15] Compiling Network.Wreq.Cache.Store ( Network/Wreq/Cache/Store.hs, .stack-work/dist/x86_64-linux/Cabal-1.24.0.0/build/Network/Wreq/Cache/Store.o )
    [ 5 of 15] Compiling Network.Wreq.Internal.Types ( Network/Wreq/Internal/Types.hs, .stack-work/dist/x86_64-linux/Cabal-1.24.0.0/build/Network/Wreq/Internal/Types.o )
    [ 6 of 15] Compiling Network.Wreq.Internal.Lens ( Network/Wreq/Internal/Lens.hs, .stack-work/dist/x86_64-linux/Cabal-1.24.0.0/build/Network/Wreq/Internal/Lens.o )
    <command line>: can't load .so/.DLL for: /home/josiah/.stack/snapshots/x86_64-linux/lts-7.13/8.0.1/lib/x86_64-linux-ghc-8.0.1/random-1.1-54KmMHXjttlERYcr1mvsAe/libHSrandom-1.1-54KmMHXjttlERYcr1mvsAe-ghc8.0.1.so (/home/josiah/.stack/snapshots/x86_64-linux/lts-7.13/8.0.1/lib/x86_64-linux-ghc-8.0.1/random-1.1-54KmMHXjttlERYcr1mvsAe/libHSrandom-1.1-54KmMHXjttlERYcr1mvsAe-ghc8.0.1.so: undefined symbol: timezm1zi6zi0zi1_DataziTimeziClockziCTimespec_getCTimespec1_closure)

--  While building package hoogle-5.0.1 using:
      /home/josiah/.stack/setup-exe-cache/x86_64-linux/Cabal-simple_mPHDZzAJ_1.24.0.0_ghc-8.0.1 --builddir=.stack-work/dist/x86_64-linux/Cabal-1.24.0.0 build --ghc-options " -ddump-hi -ddump-to-file"
    Process exited with code: ExitFailure 1
    Logs have been written to: /home/josiah/.stack/global-project/.stack-work/logs/hoogle-5.0.1.log

    Configuring hoogle-5.0.1...
    Building hoogle-5.0.1...
    Preprocessing library hoogle-5.0.1...
    [ 1 of 28] Compiling General.IString  ( src/General/IString.hs, .stack-work/dist/x86_64-linux/Cabal-1.24.0.0/build/General/IString.o )
    [ 2 of 28] Compiling General.Str      ( src/General/Str.hs, .stack-work/dist/x86_64-linux/Cabal-1.24.0.0/build/General/Str.o )
    [ 3 of 28] Compiling General.Conduit  ( src/General/Conduit.hs, .stack-work/dist/x86_64-linux/Cabal-1.24.0.0/build/General/Conduit.o )
    [ 4 of 28] Compiling General.Template ( src/General/Template.hs, .stack-work/dist/x86_64-linux/Cabal-1.24.0.0/build/General/Template.o )
    [ 5 of 28] Compiling Input.Set        ( src/Input/Set.hs, .stack-work/dist/x86_64-linux/Cabal-1.24.0.0/build/Input/Set.o )
    [ 6 of 28] Compiling Paths_hoogle     ( .stack-work/dist/x86_64-linux/Cabal-1.24.0.0/build/autogen/Paths_hoogle.hs, .stack-work/dist/x86_64-linux/Cabal-1.24.0.0/build/Paths_hoogle.o )
    [ 7 of 28] Compiling Input.Settings   ( src/Input/Settings.hs, .stack-work/dist/x86_64-linux/Cabal-1.24.0.0/build/Input/Settings.o )
    <command line>: can't load .so/.DLL for: /home/josiah/.stack/snapshots/x86_64-linux/lts-7.13/8.0.1/lib/x86_64-linux-ghc-8.0.1/random-1.1-54KmMHXjttlERYcr1mvsAe/libHSrandom-1.1-54KmMHXjttlERYcr1mvsAe-ghc8.0.1.so (/home/josiah/.stack/snapshots/x86_64-linux/lts-7.13/8.0.1/lib/x86_64-linux-ghc-8.0.1/random-1.1-54KmMHXjttlERYcr1mvsAe/libHSrandom-1.1-54KmMHXjttlERYcr1mvsAe-ghc8.0.1.so: undefined symbol: timezm1zi6zi0zi1_DataziTimeziClockziCTimespec_getCTimespec1_closure)

Current workaround I discovered (just now) is to use LTS-6.17 (GHC 7.10.3) instead of LTS-7.13 (GHC 8.0.1).

My personal philosophy about software is that it should "Just work".  If you aren't going to support all LTS versions, then my vote would be to build the IDE binaries in a Stack/Cabal sandbox which uses a supported LTS.  As a developer, I don't want my time to be spent troubleshooting why my IDE isn't installing - I just want to run the installer and start using it to work on projects I'm either being paid to deliver on within a specific timeline or that I'm pursuing for personal development as a hobby.
For background, I came to this project because my normal editor, Spacemacs, hasn't proven well suited for me for Haskell development.  If some module in the Haskell layer isn't working right, it pops-up a new split full of error messages every time I save a Haskell file in it - it was too verbose and invasive to be productive in.  I came this project because, although it wasn't working properly, it still got out of my way and let me do my work, even when all of the features/modules weren't working perfectly.  BUT - it would have been better had it been constructed in a way that enabled it to fully install automatically without errors, regardless of what my OS environment was like.

Totally understand. You're not abrasive at all; you make good points, and I appreciate the bug report. You correctly pointed out that it doesn't work on a more recent LTS version which is a problem because that is most likely what people will be using.
We could pin the LTS used to install the helper binaries, or make it work with all recent LTS versions. The advantage of the former is that things are known to work and keep working. The disadvantage, as you pointed out, is that ghc-mod built for an older version of the cabal library fails to work on new projects with newer cabal. A hybrid approach is pinning the LTS, but periodically trying to upgrade it and verifying that the install works.
The most flexible approach, of course, is making it work with all LTS versions. It makes sense to try to get to the bottom of the build failure you discovered. I'd love your help here to experiment with the install script and see if there's a change that will fix things. (I don't have time to investigate myself in the immediate future because I'm trying to iron out the last few issues on an overdue release of another project.)

My time is also limited, but if I can find a spare moment, I'll have a look into it.

My time is also limited, but if I can find a spare moment, I'll have a look into it.

(Ping, in case you're still interested)

repo: begriffs/haskell-vim-now


text:
Prevent connections from going idle

Is there a way to keep the connection to postgres open, even when there are no requests arriving?

No, the amount of time before the connection is closed after being idle is defined here
https://github.com/begriffs/postgrest/blob/master/main/Main.hs#L67
and it's 10s
If you want longer intervals, you need to compile from source

Ok, thanks.

We could theoretically expose this is a config file parameter... What's the use case?

I patched it already.
I'm running PL/Java for generating PDFs and other things. Every JDBC-Connection holds on to a JVM. The method calls are fast, I'm getting 50ms responses with hundreds of concurrent clients, but the JVM startup is very slow - sometimes a couple of seconds.
So what I would like is for postgrest to keep it's pooled connections open, so that the JVMs don't get destroyed (and also benefit from self-tuning over their runtime).

authors: begriffs fab1an ruslantalpa

repo: begriffs/postgrest


text:
Maze breaker turned into a tinker tool or tool part

The idea is that a maze breaker is made from some unknown material that has special properties.
I'm thinking that the mazebreaker should have a recipe made of three "mazebreaker ingots" and two sticks and that the only way to get mazebreaker ingots is to uncraft the mazebreaker. Then, you can use the mazebreaker's ingots to make a tool.
As far as tool properties, I'm thinking that the mazebreaker should have a high mining speed and durability akin to diamond. It should have a cobalt mining level.
Ideally, I want the mazebreaker to come with the Luck modifier (level 2) if I can manage it. It could also have a property that increases its mining speed when mining something that takes a significant amount of time to break, such as obsidian.
color: a pale green #bbd7bb

Head:

1561 durability
13.0 speed
7.45 damage
cobalt mining level
Traits: ?

Handle:

1.5 multiplier
+250 durability.
Traits: ?

Extra part:

+50 durability
Traits: ?

Bow:

0.75 draw speed
1.3 range (arrow speed?)
4 bonus damage
Traits: ?

I went through the trait documentation and we need to use the GetMiningSpeed function and access the block information from the IBlock field of the PlayerBreakEvent. It looks like we just need to set the newSpeed field based on the properties of the IBlock to speed up the block breaking.

repo: belathus/Wanderlust-Renewed


text:
Remove redundant using statements

I think the tool should remove redundant (duplicate or unused) using statements.
Expected:
using MyUsedHelper;

Actual:
using MyUsedHelper;
using MyUsedHelper;
using MyUnusedHelper;

CSharpier is unable to determine if a using is unused, it only works with the syntax tree of a file.
I am debating if removing redundant usings should be one of the exceptions to the "only change whitespace" rule.
On the surface it seems like it would be fairly easy to implement. The only part that could get a bit complicated is the syntax tree validation, which tries to ensure that CSharpier doesn't unintentionally eat any code.
However there are other tools that can remove them, and I don't know how often they show up. So perhaps it isn't worth the effort.

authors: belav will-molloy

repo: belav/csharpier


text:
csharpier does not support .net 7

I successfully installed csharpier 0.20.0 but it can not work at .net 7.
PS C:\Users\listl> dotnet --version
7.0.100

PS C:\Users\listl> dotnet csharpier
You must install or update .NET to run this application.

App: C:\Users\listl\.dotnet\tools\dotnet-csharpier.exe
Architecture: x64
Framework: 'Microsoft.NETCore.App', version '6.0.0' (x64)
.NET location: C:\Users\listl\scoop\apps\dotnet-sdk\current

The following frameworks were found:
  7.0.0 at [C:\Users\listl\scoop\apps\dotnet-sdk\current\shared\Microsoft.NETCore.App]

Learn about framework resolution:
https://aka.ms/dotnet/app-launch-failed

To install missing framework, download:
https://aka.ms/dotnet-core-applaunch?framework=Microsoft.NETCore.App&framework_version=6.0.0&arch=x64&rid=win10-x64

I have this resolved in #756 which isn't released yet. The new version will be out sometime tomorrow.

Thank you. I found it reported at #752. I'll close it.

authors: belav tanukihee


text:
docs: update deskripsi file readme.md

menambahkan spasi di deskripsi. (file readme.md)
Deskripsi (Description)

Checklist:
Umum:

[ ] Saya menambah kode basic terbaru.
[ ] Saya memperbaiki kode basic yang sudah ada.
[ ] Saya menambah template terbaru.
[ ] Saya memperbaiki template yang sudah ada.
[ ] Saya memperbaiki dokumentasi.
[ ] Saya menambah dokumentasi.
[x] Saya memperbaiki deskripsi file readme

Contributor Requirements (Syarat Kontributor) dan Lain-Lain:

[x] Saya sudah membaca (I have read) CONTRIBUTING dan sudah menyetujui semua syarat.
[ ] Saya telah menambahkan komentar kode yang memberikan penjelasan maksud dari kode yang saya buat.
[ ] Saya menggunakan bahasa Indonesia untuk memberikan penjelasan dari kode yang saya buat.

Environment
Saya menggunakan (I'm using):

os = linux / windows / macOS

Testing

[ ] link html
[ ] lint css

linked issue #NOMOR_ISSUE

pesan commit harap diperbaiki agar sesuai dengan CONTRIBUTING.md

pesan commit harap diperbaiki agar sesuai dengan CONTRIBUTING.md

done

@Teddir untuk pesan commit bisa di amend terlebih dahulu sebelum commit

repo: bellshade/HTML-CSS


text:
useVirtualized

В рамках работы над #95 осознал, что получающийся компонент в своей предельно кастомизированной версии возможно будет гораздо лучше смотреться в виде хука. Посему разумным может оказаться идея породить хук со следующим публичным API:
interface UseVirtualizedProps<T> {
  /**
  Коллекция, которую надо виртуализировать. Видится хорошей идеей
  типизировать ее через дженерик, как и весь хук.
  **/
  items: T[];

  /**
  Рендер-функция элемента виртуализованного списка. Принимает на
  вход объект с конкрентым элементом и стилем для обертки этого
  элемента, отдает ReactNode, которая потом пишется в children.
  **/
  renderElement({ element: T; style: CSSProperties}) => ReactNode;

  /**
 Оценочный размер элемента. Может быть числом, а может (для большей
 гибкости) быть функцией, принимающей конкретный элемент на вход и
 возвращающей размер на выходе)
 **/
 estimate: number | (T) => number;
}

interface UseVirtulizedResult {
  /**
 Пропсы для внешнего контейнера. Внутри находится реф, который нужно повесить на котейнер
 **/
 containerProps: { ref: Ref<HTMLElement> };

 /**
 Пропсы для иннера. Содержат стиль
**/
 innerProps: { style: CSSProperties };

 /**
Отрендеренные виртуализированные элементы
 **/
 children: ReactNode[];
}

Хук предлагается назвать не useVirtual а  useVirtualized, чтобы не было конфликтов имен с одноименной библиотекой, которая еще, возможно будет использоваться под капотом нашего хука.

Хорошо бы estimate в необязательный props переделать

authors: dkonasov polRk

repo: bem/web-platform


text:
Redo subdomain naming strategy

@brewhousedigital suggested  in #35 name-name-number rather than just name-name.
Since every instance gets a unique ID, I think the backend should always answer on that subdomain:
ctg834u9gc.pockethost.io
Then I think it's still valuable for users to be allowed to pick a globally-unique name if they want to:
foo.pockethost.io
That, along with #25 support, will create a nice tidy solution.
If they want to rename an instance, they can do that because metrics are linked to the uuid and not the subdomain name.
Proposed frontend changes:

Name: /[A-Za-z-]/ max 50 chars
Name must be globally unique
Name can be changed at any time
Name CANNOT match any instance uuid

Proposed daemon changes:

Recognize both uuids and names when resolving instance requests

Sounds like the user would still create their random word-word but in the backend we're saving word-word-uuid? That way, they could create a custom name like "brewhouse.pockethost.io" but in the backend it would be `brewhouse-109384.pockethost.io"?
Or do we need to differentiate a custom name vs a generated name?

@brewhousedigital Actually I think word-word.pockethost.io is still okay, and requiring word-word to be globally unique is okay too. They can always go word-word-2 if they really are dying to have that naming. Or associate a custom domain (probably a paid level for that). Since every record in a collection has an id field, doing <id>.pockethost.io is a third way they could access their instance. But we can allow them to change word-word as long as it doesn't conflict with anyone else's use. Metrics will be tracked based on the id field anyway, so word-word is just decorative.

Makes sense!
Do you have plans to create an API that can take in a parameter like /api/instances/verify-name?name=brewhouse  that we can use to receive a boolean back?
Do you think we'll need additional security on the Go side, perhaps by using OnRecordBeforeCreateRequest or OnModelBeforeCreate (not sure the difference), just incase someone tries to hit the API directly? or would setting the name field to be unique suffice? probably just unique right?
Now that I type all that out, perhaps we don't need that verify-name API. If the table as a whole will just return a 400, we can read the error response and then tell the user that the name was already chosen and they need to choose something else.

we can read the error response and then tell the user that the name was already chosen and they need to choose something else

Exactly, I think that's what it does now anyway.
I'm setting this for a later milestone, but I definitely would like it for v1.

moved to roadmap

authors: benallfree brewhousedigital

repo: benallfree/pockethost


text:
How to handle multiple data using rules

When there is a lot of data, how to deal with？Use clearRules() ？
public class Launcher {

    public static void main(String[] args) {

        //create a person instance
        Person tom = new Person("Tom", 16);
        System.out.println("Tom: Hi! can I have some Vodka please?");

        //create a rules engine
        RulesEngine rulesEngine = aNewRulesEngine().build();
        rule(rulesEngine,tom);
        Person devid = new Person("Devid", 18);
        rule(rulesEngine,devid);
    }

    public static void rule( RulesEngine rulesEngine,Person person){
    	//register rules
        rulesEngine.registerRule(new AgeRule(person));
        rulesEngine.registerRule(new AlcoholRule(person));
        //fire rules
        rulesEngine.fireRules();
        rulesEngine.clearRules();
    }

}

Hi, you can do it that way indeed, but actually you don't need to clear and re-register your rules each time the data changes.
You can simply add a default constructor and a setter for the person in each rule and update rules with new data before firing them. Here is an example:
public class Launcher {

    public static void main(String[] args) {

		//create persons
        Person tom = new Person("Tom", 16);
		Person devid = new Person("Devid", 18);

        //create a rules engine
        RulesEngine rulesEngine = aNewRulesEngine().build();
		AgeRule ageRule = new AgeRule();
		AlcoholRule alcoholRule = new AlcoholRule();

		rulesEngine.registerRule(ageRule);
		rulesEngine.registerRule(alcoholRule);

		//first run
        ageRule.setPerson(tom);
		alcoholRule.setPerson(tom);
		rulesEngine.fireRules();

		//second run
        ageRule.setPerson(devid);
		alcoholRule.setPerson(devid);
		rulesEngine.fireRules();
    }
}

Why use clearRules() the following code have different results?

public class Person {

    private String name;

    private int age;

    private int sex;

    private String say;

    public Person(String name, int age, int sex) {
        this.name = name;
        this.age = age;
        this.sex = sex;
    }

    public String getName() {
        return name;
    }

    public void setName(String name) {
        this.name = name;
    }

    public int getAge() {
        return age;
    }

    public void setAge(int age) {
        this.age = age;
    }

	public String getSay() {
		return say;
	}

	public void setSay(String say) {
		this.say = say;
	}

	public int getSex() {
		return sex;
	}

	public void setSex(int sex) {
		this.sex = sex;
	}
}

@Rule(name = "SexRule", description = "")
public class SexRule {

    private Person person;

    public SexRule(Person person) {
        this.person = person;
    }

    @Condition
    public boolean isAdult() {
        return person.getSex() == 1;
    }

    @Action
    public void markAsAdult(){
    	person.setSay("Sex");
    }

    @Priority
    public int getPriority() {
        return 2;
    }

}

@Rule(name = "AgeRule", description = "")
public class AgeRule {

    private static final int ADULT_AGE = 18;

    private Person person;

    public AgeRule(Person person) {
        this.person = person;
    }

    @Condition
    public boolean isAdult() {
        return person.getAge() > ADULT_AGE;
    }

    @Action
    public void markAsAdult(){
        person.setSay("Age");
    }

    @Priority
    public int getPriority() {
        return 3;
    }

}

public class Launcher {

    public static void main(String[] args) {
        Person tom = new Person("Tom", 19,1);
        RulesEngine rulesEngine = aNewRulesEngine().build();
        rulesEngine.registerRule(new AgeRule(tom));
        rulesEngine.registerRule(new SexRule(tom));
        rulesEngine.fireRules();
        //rulesEngine.clearRules();
        Person devid = new Person("Devid", 16,1);
        rulesEngine.registerRule(new AgeRule(devid));
        rulesEngine.registerRule(new SexRule(devid));
        rulesEngine.fireRules();

        System.out.println(tom.getSay());
        System.out.println(devid.getSay());
    }

}

Hi,
This is related to the question that has been asked here.
Rules have unique names with in a rules engine registry.
When you don't call clearRules and register a second time an instance of AgeRule and SexRule with devid, those 2 instances are actually not registered since they have the same name as instances that have been registered with tom. The same name that is specified in the Rule annotation (@Rule (name = "AgeRule"). Do you see the trick?
So to deal with multiple input data with the same rules, you can create single instances of your rules, register them once and then varies your data and re-fires rules (like the example I gave above). This is more efficient than recreating rules instances each time.
Kind regards
Mahmoud

Thank you for your answer

authors: benas bianyu

repo: benas/easy-rules


text:
Show doge value

Since dogeHouse related to doge maybe show the value of doge right now at
the top?

Could be added using this,
List of currencies
This returns JSON with the required data:
{
    "ticker":{
        "base":"DOGE",
        "target":"GBP",
        "price":"0.03581547",
        "volume":"18929690.43329700",
        "change":"0.00042681"
    },
    "timestamp":1614965522,
    "success":true,
    "error":"

I feel like it's supplemental functionality that really doesn't add much value to the application. It's also more data (JSON fetching, deserializing, component load, etc) (in @ZackaryH8's case) which really isn't a problem, but as the app scales up, it could lead to worse performance and longer load times.

repo: benawad/dogehouse


text:
Support string values

Hi, I've got a few battery powered devices I monitor, where the unit is: normal or low
When using your battery-entity-row, what unit should I be using for these devices?
Defaulting to % is great, in most cases, for these devices, it just shows 0%, when in-fact the state is actually normal. I've tried "unit:  " & "unit: string" but not getting the result I'd expect. Are their more options for unit than "%"?
cheers

Try unit: false. However, this card currently only supports numeric battery values, not strings like normal and low.

Understood. I tried it, after upgrading, no luck. Any chance of making this a feature request?

Make sure you clear cache/hard refresh your HA tab.. Hiding the unit works fine here.
I'll try to look into supporting string values. Let me know what the different values are. high, medium, normal, low, empty, etc..?

I've tried clearing the cache/hard refresh, and the binary sensor shows "Unknown" when the state of the sensor is actually "Low". I've got several binary_sensors, the 2 states I've seen are "Normal" or "Low".

Version 1.2.0 should now support string values like normal and low (and some others).

authors: benct xstrex

repo: benct/lovelace-battery-entity-row


text:
Making namespace matcher more relaxed so that it can match dot separa…

This PR relaxes the namespace matcher so that it doesn't just match a word - it matches the text before any subsequent properties, as well as period separated namespaces. This allows for the exported value to be the final object of the namespace, i.e.
{namespace com.foo.bar}

results in bar being exported rather than com.
Now, the initial implementation may have been intentional. Regardless, this is what I figure is correct behaviour. If people think otherwise, please let me know, and perhaps we can instead just make this matcher configurable, with the existing value as the default.

Would someone be able to review this and merge it?

@bendman if you aren't maintaining this library, would you be able to give me write access please?

Er I'm not sure what the thumbs up is supposed to mean :P

Ah, sorry, I thought it would send you a message.  You should have received and invite to collaborate on the project, which gives you write access.

Oh I didn't see that, sorry! Thanks a lot.
On Thursday, September 15, 2016, Ben Duncan notifications@github.com
wrote:

Ah, sorry, I thought it would send you a message. You should have received
and invite to collaborate on the project, which gives you write access.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bendman/soy-loader/pull/5#issuecomment-247386883, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AD2AuVw-xhvpcyugLTlTfqwVcEhYeI9wks5qqXkNgaJpZM4Hvbg4
.

authors: bendman kayneb

repo: bendman/soy-loader


text:
Update README.md

Used link to library with much larger weekly downloads.
https://www.npmjs.com/package/escape-regexp 791,252
vs
https://www.npmjs.com/package/escape-string-regexp 32,646,882

Thanks!

Thanks!

authors: benjamingr oliverfoster


text:
Ukraine - Kyiv region duplicate

State/Province list for the Ukraine has duplicate Kyiv options - Kiev and Kyїv. Kyiv will be the correct one. Thanks

Thanks, @mcmxc! I'll log this on the https://github.com/benkeen/country-region-data/ repo - we grab the data from there.

authors: benkeen mcmxc

repo: benkeen/country-region-selector


text:
"populate" command has hidden required argument "--sso-start-util" and "--region"

When running aws-sso-util configure populate an error is thrown:
No AWS SSO instance found
This provides no indication that the --sso-start-util option is needed which then immediately throws
Error: Missing arguments: --region
It's easy to find the --sso-region option first and attempt to use it to specify the region.
After providing both --sso-start-util and --region, I was able to successfully log into AWS. Subsequent calls to populate without any arguments provide an error:
`aws-sso-util configure populate
Usage: aws-sso-util configure populate [OPTIONS]
Error: Missing arguments: --region
`
Once provided, the start URL is reused and populate completes successfully.
What I would expect to happen:

Populate command has positional arguments for region and start url which are always required
Populate command either assumes both arguments or neither
When assuming arguments, the values are displayed to the user or the user is prompted to confirm reuse

The docs cover how the AWS SSO instance can be specified, and that a region is required. It also states the --verbose flag can be used to display the details of the AWS SSO instance finding.
Can you provide some examples of the combinations of input and resulting error message you're looking for?

authors: Shumakriss benkehoe

repo: benkehoe/aws-sso-util


text:
extensions: how to specify a default while specifying granular extensions?

I'd like the default to be "always" but i'd like js and jsx to be "never". How do I specify this? The schema only allows a string, or an object, but not both.

(Similarly, I should be able to specify "never" and have a specific extension be "always")
It's not clear to me how to ensure that.

Ah, interesting. I'm not sure how you'd do that, either. Sounds like a reasonable goal though.

My thinking was that the schema would allow a string and an object - the string constitutes the default, and the object has granular overrides.

Any update on this?

I like your proposal:

... the schema would allow a string and an object - the string constitutes the default, and the object has granular overrides.

Don't think it constitutes a breaking change, since the first arg can still be a string or object, but the second one must be an object if the first is a string, and the second must not be provided if the first is an object.
I'm not planning on working on this anytime soon. I'd be happy to accept and ship a PR, though.

Finally filed https://github.com/benmosher/eslint-plugin-import/pull/555 to fix this :-)

Yay, thanks! Waiting patiently now for the release :-)

authors: benmosher ljharb

repo: benmosher/eslint-plugin-import


text:
How get txHash?

I detecting new deposit from getAccountHistory method, but there is no txHash in the details. How do I get a transaction hash from api? What is a details.transfer_id for?

Hi @bossikkk, I searched on the official Coinbase Pro API reference and couldn't find anything related to "txHash" (Ethereum Transaction Hash). The code base of the deprecated Node.js library for Coinbase Pro also does not show anything related. Are you sure Coinbase Pro offers such functionality?
In your case I would ask on Reddit or the Coinbase Help service.
Are you sure that the account history details return a "transfer_id"? Telling from the TypeScript definition file there is only:
export interface AccountHistoryDetails {
  order_id: string;
  product_id: string;
  trade_id: string;
}

Hi, I also did not find on the official website of CoinBase Pro API a mention of how to get a Transaction Hash. I just saw in the interface that there is such a functional and thought that I was missing something in API.

Anyway, thanks for the answer. I will ask Coinbase directly.
getAccountHistory method does return details with transfer_id and transfer_type, but if the type of the item is transfer:
{
    id: '2135804119',
    amount: '0.0000847200000000',
    balance: '0.0000847200000000',
    created_at: '2020-04-26T15:24:59.853577Z',
    type: 'transfer',
    details: {
      transfer_id: '7bc26b85-aff0-49fe-8480-118c3aea0086',
      transfer_type: 'deposit'
    }
  }

And I thought maybe transfer_id will help me in solving the problem related to detect the sender by deposit. Because of all the information about the sender that I have stored in the database, I can only check the amount.

Hey @bossikkk, thanks for checking back in. Please report if you got an answer from Coinbase and let me know if we can add something to this library here to help you. I will close the issue while we have the information that we cannot get the txHash from the API.

authors: bennyn bossikkk

repo: bennyn/coinbase-pro-node


text:
OOM

sparqles_backend-svc_1  | 14-10-24 21:00:34 [ INFO] sparqles.core.EndpointTask:57 - EXECUTE ATask(http://http://opendata.intellidomo.es:8080/sparql/)
sparqles_backend-svc_1  | 14-10-24 21:00:34 [ INFO] sparqles.utils.ExceptionHandler:66 - EXC@1#46074
sparqles_backend-svc_1  | HttpException: -1 Unexpected error making the query: GET http://http://opendata.intellidomo.es:8080/sparql/?query=SELECT%20?s%20WHERE%7B?s%20?p%20?o%7D%20LIMIT%201
sparqles_backend-svc_1  |       at org.apache.jena.sparql.engine.http.QueryExceptionHTTP.rewrap(QueryExceptionHTTP.java:52)
sparqles_backend-svc_1  |       at org.apache.jena.sparql.exec.http.QueryExecHTTP.executeQuery(QueryExecHTTP.java:552)
sparqles_backend-svc_1  |       at org.apache.jena.sparql.exec.http.QueryExecHTTP.execRowSet(QueryExecHTTP.java:173)
sparqles_backend-svc_1  |       at org.apache.jena.sparql.exec.http.QueryExecHTTP.select(QueryExecHTTP.java:164)
sparqles_backend-svc_1  |       at org.apache.jena.sparql.exec.QueryExecutionAdapter.execSelect(QueryExecutionAdapter.java:108)
sparqles_backend-svc_1  |       at sparqles.core.availability.ATask.testSelect(ATask.java:89)
sparqles_backend-svc_1  |       at sparqles.core.availability.ATask.process(ATask.java:76)
sparqles_backend-svc_1  |       at sparqles.core.availability.ATask.process(ATask.java:27)
sparqles_backend-svc_1  |       at sparqles.core.EndpointTask.call(EndpointTask.java:67)
sparqles_backend-svc_1  |       at sparqles.core.EndpointTask.call(EndpointTask.java:19)
sparqles_backend-svc_1  |       at sparqles.schedule.Scheduler$SchedulerTimerTask.run(Scheduler.java:266)
sparqles_backend-svc_1  |       at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572)
sparqles_backend-svc_1  |       at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
sparqles_backend-svc_1  |       at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
sparqles_backend-svc_1  |       at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
sparqles_backend-svc_1  |       at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
sparqles_backend-svc_1  |       at java.base/java.lang.Thread.run(Thread.java:1583)
sparqles_backend-svc_1  | Caused by: java.io.IOException: selector manager closed
sparqles_backend-svc_1  |       at java.net.http/jdk.internal.net.http.HttpClientImpl.send(HttpClientImpl.java:964)
sparqles_backend-svc_1  |       at java.net.http/jdk.internal.net.http.HttpClientFacade.send(HttpClientFacade.java:133)
sparqles_backend-svc_1  |       at org.apache.jena.http.HttpLib.executeJDK(HttpLib.java:610)
sparqles_backend-svc_1  |       at org.apache.jena.http.auth.AuthLib.authExecute(AuthLib.java:51)
sparqles_backend-svc_1  |       at org.apache.jena.http.HttpLib.execute(HttpLib.java:570)
sparqles_backend-svc_1  |       at org.apache.jena.http.HttpLib.execute(HttpLib.java:527)
sparqles_backend-svc_1  |       at org.apache.jena.sparql.exec.http.QueryExecHTTP.executeQuery(QueryExecHTTP.java:548)
sparqles_backend-svc_1  |       ... 15 more
sparqles_backend-svc_1  | Caused by: java.io.IOException: selector manager closed
sparqles_backend-svc_1  |       at java.net.http/jdk.internal.net.http.HttpClientImpl$SelectorManager.selectorClosedException(HttpClientImpl.java:1126)
sparqles_backend-svc_1  |       at java.net.http/jdk.internal.net.http.HttpClientImpl.sendAsync(HttpClientImpl.java:1005)
sparqles_backend-svc_1  |       at java.net.http/jdk.internal.net.http.HttpClientImpl.send(HttpClientImpl.java:930)
sparqles_backend-svc_1  |       ... 21 more
sparqles_backend-svc_1  | Caused by: java.lang.OutOfMemoryError: Java heap space
sparqles_backend-svc_1  | 14-10-24 21:00:34 [ INFO] sparqles.utils.ExceptionHandler:66 - EXC@1#46075
sparqles_backend-svc_1  | HttpException: -1 Unexpected error making the query: GET http://http://opendata.intellidomo.es:8080/sparql/?query=SELECT%20?s%20WHERE%7B?s%20?p%20?o%7D%20LIMIT%201
sparqles_backend-svc_1  |       at org.apache.jena.sparql.engine.http.QueryExceptionHTTP.rewrap(QueryExceptionHTTP.java:52)
sparqles_backend-svc_1  |       at org.apache.jena.sparql.exec.http.QueryExecHTTP.executeQuery(QueryExecHTTP.java:552)
sparqles_backend-svc_1  |       at org.apache.jena.sparql.exec.http.QueryExecHTTP.execRowSet(QueryExecHTTP.java:173)
sparqles_backend-svc_1  |       at org.apache.jena.sparql.exec.http.QueryExecHTTP.select(QueryExecHTTP.java:164)
sparqles_backend-svc_1  |       at org.apache.jena.sparql.exec.QueryExecutionAdapter.execSelect(QueryExecutionAdapter.java:108)
sparqles_backend-svc_1  |       at sparqles.core.availability.ATask.testSelect(ATask.java:89)
sparqles_backend-svc_1  |       at sparqles.core.availability.ATask.process(ATask.java:76)
sparqles_backend-svc_1  |       at sparqles.core.availability.ATask.process(ATask.java:27)
sparqles_backend-svc_1  |       at sparqles.core.EndpointTask.call(EndpointTask.java:67)
sparqles_backend-svc_1  |       at sparqles.core.EndpointTask.call(EndpointTask.java:19)
sparqles_backend-svc_1  |       at sparqles.schedule.Scheduler$SchedulerTimerTask.run(Scheduler.java:266)
sparqles_backend-svc_1  |       at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572)
sparqles_backend-svc_1  |       at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
sparqles_backend-svc_1  |       at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
sparqles_backend-svc_1  |       at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
sparqles_backend-svc_1  |       at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
sparqles_backend-svc_1  |       at java.base/java.lang.Thread.run(Thread.java:1583)
sparqles_backend-svc_1  | Caused by: java.io.IOException: selector manager closed
sparqles_backend-svc_1  |       at java.net.http/jdk.internal.net.http.HttpClientImpl.send(HttpClientImpl.java:964)
sparqles_backend-svc_1  |       at java.net.http/jdk.internal.net.http.HttpClientFacade.send(HttpClientFacade.java:133)
sparqles_backend-svc_1  |       at org.apache.jena.http.HttpLib.executeJDK(HttpLib.java:610)
sparqles_backend-svc_1  |       at org.apache.jena.http.auth.AuthLib.authExecute(AuthLib.java:51)
sparqles_backend-svc_1  |       at org.apache.jena.http.HttpLib.execute(HttpLib.java:570)
sparqles_backend-svc_1  |       at org.apache.jena.http.HttpLib.execute(HttpLib.java:527)
sparqles_backend-svc_1  |       at org.apache.jena.sparql.exec.http.QueryExecHTTP.executeQuery(QueryExecHTTP.java:548)
sparqles_backend-svc_1  |       ... 15 more
sparqles_backend-svc_1  | Caused by: java.io.IOException: selector manager closed
sparqles_backend-svc_1  |       at java.net.http/jdk.internal.net.http.HttpClientImpl$SelectorManager.selectorClosedException(HttpClientImpl.java:1126)
sparqles_backend-svc_1  |       at java.net.http/jdk.internal.net.http.HttpClientImpl.sendAsync(HttpClientImpl.java:1005)
sparqles_backend-svc_1  |       at java.net.http/jdk.internal.net.http.HttpClientImpl.send(HttpClientImpl.java:930)
sparqles_backend-svc_1  |       ... 21 more
sparqles_backend-svc_1  | Caused by: java.lang.OutOfMemoryError: Java heap space
sparqles_backend-svc_1  | 14-10-24 21:00:34 [ WARN] sparqles.core.availability.ATask:157 - failed SELECT query for http://http://opendata.intellidomo.es:8080/sparql/, EXC@1#46075> QueryExceptionHTTP msg:Unexpected error making the query: GET http://http://opendata.intellidomo.es:8080/sparql/?query=SELECT%20?s%20WHERE%7B?s%20?p%20?o%7D%20LIMIT%201 cause:java.io.IOException: selector manager closed

There is likely some leak because it's not the response size - the URI is NXDOMAIN:
curl -I http://opendata.intellidomo.es:8080/sparql/\?query\=SELECT%20\?s%20WHERE%7B\?s%20\?p%20\?o%7D%20LIMIT%201
curl: (6) Could not resolve host: opendata.intellidomo.es

Also see https://github.com/OpenLinkSoftware/sparqles/commit/db897e8449e12a627a675229478573c41a42a9b7

https://github.com/berezovskyi/sparqles/commit/48cd85447e48530190c963966103ccefc12fccb7

repo: berezovskyi/sparqles


text:
Validate signatures on original query string

Before this commit:
signature validation on GET (Redirect binding) requests was done using
encodeURIComponent on the already parsed params
After:
the original query params are used to validate the request's signature
The reason for doing this is that Azure ADFS is using lowercase for url
encoding resulting in something like:
SAMLRequest=dead%2fbeef
The old processing logic would try to validate against:
SAMLRequest=dead%2Fbeef
and failed
see also:
https://github.com/onelogin/php-saml/issues/243

I want to make sure I understand the root cause here. Is it:
A. "%2f" and "%2F" aren't being decoded the same. *If that's the issue, it's a bug in the decoder, because URI percent encoding should not be case-sensitive
B. Because the URL has changed, the signature changed, so signature validation fails. This seems like a bug in Azure ADFS, but one we may want to workaround because Azure ADFS is popular.

I want to make sure I understand the root cause here. Is it:
A. "%2f" and "%2F" aren't being decoded the same. If that's the issue, it's a bug in the decoder, because [URI percent encoding should not be case-sensitive](https://stackoverflow.com/questions/7994287/is-url-percent-encoding-case-sensitive)

they're decoded ok, the issue is after the decode we do an encode to validate the signature. this encode can't derive if the original had lowercase or uppercase encodings. to amend I'm using the same parameters

B. Because the URL has changed, the signature changed, so signature validation fails. This seems like a bug in Azure ADFS, but one we may want to workaround because Azure ADFS is popular.

Azure just happens to forward lowercase encodings, while the encodeURI produces only uppercase ones

no this is another issue. if azure is configured with rsa-sha256 (lowercase) signing it would match with sha256 crypto algorithm. doing a case incentive search in the crypto algorithms resolves this.

I see. Is there any reason not to use the more precise approach of doing a case-insensitive lookup?
Thanks for the Azure fixes. One of the next customers I need to integrate with uses Azure.

I see. Is there any reason not to use the more precise approach of doing a case-insensitive lookup?

a stricter mapping might be the right thing here, but I didn't want to break any existing implementations (even if they might be working by accident)

Some more follow-up here: I found that algorithms arrive as URLs, so an exact match approach does not work, even case-insensitive. I committed an approach that was more precise than a basic substring match, though.  An example algorithm that arrives in an SAML response looks like this: http://www.w3.org/2001/04/xmlenc#sha256. I used a Regex match to extract the part after the # character. Then we try an exact-but-case-insensitive match against all the algorithms that Node.js supports.
Still, we could do strong validation. I looked up what valid algorithms are for SAML and how the names are formatted. SAML is using XML Encryption and XML Signatures, which each have their own W3C specs:

https://www.w3.org/TR/xmldsig-core/#sec-Algorithms
https://www.w3.org/TR/2002/REC-xmlenc-core-20021210/Overview.html#sha256

So, the algorithms we should actually support would be some sub-set of the algorithms defined there.
We could make signature validation even stronger by testing incoming algorithms against the list of algorithms supported in the XML Signatures spec. Since we don't do that now, it's possible that we could accept an algorithm that is weaker than was even intended to be used.

authors: markstos stavros-wb

repo: bergie/passport-saml


text:
🛑 SIDAP is down

In 130af93, SIDAP (http://uladap.adm.ula.ve/sidap/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SIDAP is back up in 3d4dd23 after 10 hours, 2 minutes.

repo: berlinserver/estatus


text:
Decrease Message Space and Some CSS Refactoring

Decrease space between messages.
Relate bottom padding of chat body and height of chatroom footer with variables.
Move legacy .box-footer styles to newer #chatroom-footer css.

should i delete any fall backs related to adminLTE.css?


text:
Abandonner l'attribut "références"

Je me rend comte que lister des références sans une note qui précise quelle page dans un PDF, ou autres informations contextuelles utiles, n'est pas une très bonne idée.
Je me retrouve souvent à préciser tout ça dans le champs note ou description.
Je propose donc de supprimer ce champs, et de faire en sorte que les pages de documentation compilent automatiquement les url présentes dans le markdown en bas de page.
Autre solution : utiliser un plugin markdown qui permet d'intégrer des notes de bas de page (je l'ai intégré sur nosgestesclimat).

sans une note qui précise quelle page dans un PDF

Sur ce point précis tu peux ajouter une ancre #page=30 qui est supporté par la plupart des clients PDF exemple

Merci ! Je savais pas ça.

Sinon c'est une idée intéressante de regrouper les références et notes de bas de page dans un champ description en markdown.
Peut-être même qu'on pourrait aller plus loin et passer à un modèle de « programmation littéraire » où on utiliserait un format de premier niveau compatible Markdown et où le code serait dans des section indentées : exemple sur le Publicodes entreprise. On mettrait ainsi en avant la documentation (incluant références et notes de bas de page donc) dans le code source et sur GitHub. Le code serait dans les sections indentées (mais c'est déjà le cas aujourd'hui car avec le yaml on doit indenter le contenu de la règle, alors qu'avec un titre markdown on peut écrire en dessous sans indentation).
Catala utilise aussi la programmation littéraire, j'ai ouvert une discussion sur leur Zulip pour avoir leur avis sur une syntaxe littérale compatible avec Markdown.
À réfléchir, mais je voulais partager la réflexion :)

Sinon c'est une idée intéressante de regrouper les références et notes de bas de page dans un champ description en markdown.
Peut-être même qu'on pourrait aller plus loin et passer à un modèle de « programmation littéraire » où on utiliserait un format de premier niveau compatible Markdown et où le code serait dans des section indentées : exemple sur le Publicodes entreprise. On mettrait ainsi en avant la documentation (incluant références et notes de bas de page donc) dans le code source et sur GitHub. Le code serait dans les sections indentées (mais c'est déjà le cas aujourd'hui car avec le yaml on doit indenter le contenu de la règle, alors qu'avec un titre markdown on peut écrire en dessous sans indentation).
Catala utilise aussi la programmation littéraire, j'ai ouvert une discussion sur leur Zulip pour avoir leur avis sur une syntaxe littérale compatible avec Markdown.
À réfléchir, mais je voulais partager la réflexion :)

Passer du yaml au md, ambitieux :)
J'ai beaucoup. Mais il faudrait voir à l'usage.
On pourrait même imaginer d'utiliser les niveaux de titre comme sémantique d'espace de nom.

Passer du yaml au md, ambitieux :)
J'ai beaucoup. Mais il faudrait voir à l'usage.
On pourrait même imaginer d'utiliser les niveaux de titre comme sémantique d'espace de nom.

C'est très intéressant en effet. Je me demande si on pourrait pas faire coexister facilement deux types de fichiers sources, en fonction des préférences ou des spécificités (volume de doc par exemple) du domaine implémenté?

C'est très intéressant en effet. Je me demande si on pourrait pas faire coexister facilement deux types de fichiers sources, en fonction des préférences ou des spécificités (volume de doc par exemple) du domaine implémenté?

Je confirme mon étonnement sur la capacité des non-dev que je côtoie à maîtriser le markdown :)
:+1: pour l'expérimentation. Par contre, peut-être créer une autre issue ? Je pense que ma 1ère demande reste valide et est simple à implémenter.
Surtout qu'il y a des pseudos standards aujourd'hui pour gérer les notes de bas de page en markdown.

authors: johangirod laem mquandalle

repo: betagouv/mon-entreprise


text:
parse_amount_in_cents malfunction

Good evening,
I recently tried to import a mt940 file that cut off trailing zeros and I got way to small amounts.
For example:
:61:1406300630DR30,NTRFNONREF//0932790011001014
instead of
:61:1406300630DR30,00NONREF//0932790011001014
The file was exported by HVB efin tool.
Is it possible to check this? For example within the parse_amount_in_cents(amount) method?
Thanks in advance

Hi,
I am using a regexp to scan the mt940 files for malformed lines and fix them. This strategy resolves this issue.


text:
🛑 You Psikoloji is down

In 5c0ae62, You Psikoloji (https://youpsikoloji.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: You Psikoloji is back up in 6ea5545 after 41 minutes.

repo: betterwithagency/status-page


text:
🛑 Uzman Randevu is down

In 9e2a48a, Uzman Randevu (https://uzmanrandevu.com.tr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Uzman Randevu is back up in c7279fe after 1 hour, 57 minutes.


text:
wgpu error: Validation Error - Dimension X is zero

Bevy version
079b3ade89195ef1aa4bcf1f8c0740a6572b84b6
Operating system & version
Windows 10
What you did
The game had its window in the background. This happened randomly
What actually happened
It caused a panic and crash
Additional information
I am not aware of any way to reproduce it currently. Also I guess due to limited knowledge (first time user as of writing this) I am very much able to miss something.
Crash log:
wgpu error: Validation Error

Caused by:
    In Device::create_texture
    Dimension X is zero

thread 'main' panicked at 'Handling wgpu errors as fatal by default', C:\Users\marce\.cargo\registry\src\github.com-1ecc6299db9ec823\wgpu-0.7.0\src\backend\direct.rs:1896:5
stack backtrace:
   0: std::panicking::begin_panic<str>
             at C:\Users\marce\.rustup\toolchains\nightly-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\panicking.rs:519
   1: wgpu::backend::direct::default_error_handler
             at C:\Users\marce\.cargo\registry\src\github.com-1ecc6299db9ec823\wgpu-0.7.0\src\backend\direct.rs:1896
   2: core::ops::function::Fn::call<fn(wgpu::Error),tuple<wgpu::Error>>
             at C:\Users\marce\.rustup\toolchains\nightly-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\core\src\ops\function.rs:70
   3: alloc::boxed::{{impl}}::call<tuple<wgpu::Error>,UncapturedErrorHandler,alloc::alloc::Global>
             at C:\Users\marce\.rustup\toolchains\nightly-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\alloc\src\boxed.rs:1560
   4: wgpu::backend::direct::ErrorSinkRaw::handle_error
             at C:\Users\marce\.cargo\registry\src\github.com-1ecc6299db9ec823\wgpu-0.7.0\src\backend\direct.rs:1883
   5: wgpu::backend::direct::Context::handle_error<wgpu_core::resource::CreateTextureError>
             at C:\Users\marce\.cargo\registry\src\github.com-1ecc6299db9ec823\wgpu-0.7.0\src\backend\direct.rs:109
   6: wgpu::backend::direct::{{impl}}::device_create_texture
             at C:\Users\marce\.cargo\registry\src\github.com-1ecc6299db9ec823\wgpu-0.7.0\src\backend\direct.rs:1132
   7: wgpu::Device::create_texture
             at C:\Users\marce\.cargo\registry\src\github.com-1ecc6299db9ec823\wgpu-0.7.0\src\lib.rs:1591
   8: bevy_wgpu::renderer::wgpu_render_resource_context::{{impl}}::create_texture
             at C:\Users\marce\.cargo\git\checkouts\bevy-f7ffde730c324c74\079b3ad\crates\bevy_wgpu\src\renderer\wgpu_render_resource_context.rs:258
   9: bevy_render::render_graph::nodes::window_texture_node::{{impl}}::update
             at C:\Users\marce\.cargo\git\checkouts\bevy-f7ffde730c324c74\079b3ad\crates\bevy_render\src\render_graph\nodes\window_texture_node.rs:73
  10: bevy_wgpu::renderer::wgpu_render_graph_executor::WgpuRenderGraphExecutor::execute
             at C:\Users\marce\.cargo\git\checkouts\bevy-f7ffde730c324c74\079b3ad\crates\bevy_wgpu\src\renderer\wgpu_render_graph_executor.rs:73
  11: bevy_wgpu::wgpu_renderer::WgpuRenderer::run_graph
             at C:\Users\marce\.cargo\git\checkouts\bevy-f7ffde730c324c74\079b3ad\crates\bevy_wgpu\src\wgpu_renderer.rs:113
  12: bevy_wgpu::wgpu_renderer::WgpuRenderer::update
             at C:\Users\marce\.cargo\git\checkouts\bevy-f7ffde730c324c74\079b3ad\crates\bevy_wgpu\src\wgpu_renderer.rs:124
  13: bevy_wgpu::get_wgpu_render_system::{{closure}}
             at C:\Users\marce\.cargo\git\checkouts\bevy-f7ffde730c324c74\079b3ad\crates\bevy_wgpu\src\lib.rs:107
  14: alloc::boxed::{{impl}}::call_mut<tuple<mut bevy_ecs::core::world::World*, mut bevy_ecs::resource::resources::Resources*>,FnMut<tuple<mut bevy_ecs::core::world::World*, mut bevy_ecs::resource::resources::Resources*>>,alloc::alloc::Global>
             at C:\Users\marce\.rustup\toolchains\nightly-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\alloc\src\boxed.rs:1553
  15: bevy_ecs::system::exclusive_system::{{impl}}::run
             at C:\Users\marce\.cargo\git\checkouts\bevy-f7ffde730c324c74\079b3ad\crates\bevy_ecs\src\system\exclusive_system.rs:31
  16: bevy_ecs::schedule::stage::{{impl}}::run
             at C:\Users\marce\.cargo\git\checkouts\bevy-f7ffde730c324c74\079b3ad\crates\bevy_ecs\src\schedule\stage.rs:580
  17: bevy_ecs::schedule::Schedule::run_once
             at C:\Users\marce\.cargo\git\checkouts\bevy-f7ffde730c324c74\079b3ad\crates\bevy_ecs\src\schedule\mod.rs:198
  18: bevy_ecs::schedule::{{impl}}::run
             at C:\Users\marce\.cargo\git\checkouts\bevy-f7ffde730c324c74\079b3ad\crates\bevy_ecs\src\schedule\mod.rs:209
  19: bevy_app::app::App::update
             at C:\Users\marce\.cargo\git\checkouts\bevy-f7ffde730c324c74\079b3ad\crates\bevy_app\src\app.rs:56
  20: bevy_winit::winit_runner_with::{{closure}}
             at C:\Users\marce\.cargo\git\checkouts\bevy-f7ffde730c324c74\079b3ad\crates\bevy_winit\src\lib.rs:486
  21: winit::platform_impl::platform::event_loop::{{impl}}::run_return::{{closure}}<tuple<>,closure-1>
             at C:\Users\marce\.cargo\registry\src\github.com-1ecc6299db9ec823\winit-0.24.0\src\platform_impl\windows\event_loop.rs:203
  22: alloc::boxed::{{impl}}::call_mut<tuple<winit::event::Event<tuple<>>, mut winit::event_loop::ControlFlow*>,FnMut<tuple<winit::event::Event<tuple<>>, mut winit::event_loop::ControlFlow*>>,alloc::alloc::Global>
             at C:\Users\marce\.rustup\toolchains\nightly-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\alloc\src\boxed.rs:1553
  23: winit::platform_impl::platform::event_loop::runner::{{impl}}::call_event_handler::{{closure}}<tuple<>>
             at C:\Users\marce\.cargo\registry\src\github.com-1ecc6299db9ec823\winit-0.24.0\src\platform_impl\windows\event_loop\runner.rs:245
  24: std::panic::{{impl}}::call_once<tuple<>,closure-0>
             at C:\Users\marce\.rustup\toolchains\nightly-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\panic.rs:344
  25: std::panicking::try::do_call<std::panic::AssertUnwindSafe<closure-0>,tuple<>>
             at C:\Users\marce\.rustup\toolchains\nightly-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\panicking.rs:379
  26: winit::platform_impl::platform::monitor::{{impl}}::fmt
  27: std::panicking::try<tuple<>,std::panic::AssertUnwindSafe<closure-0>>
             at C:\Users\marce\.rustup\toolchains\nightly-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\panicking.rs:343
  28: std::panic::catch_unwind<std::panic::AssertUnwindSafe<closure-0>,tuple<>>
             at C:\Users\marce\.rustup\toolchains\nightly-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\panic.rs:431
  29: winit::platform_impl::platform::event_loop::runner::EventLoopRunner<tuple<>>::catch_unwind<tuple<>,tuple<>,closure-0>
             at C:\Users\marce\.cargo\registry\src\github.com-1ecc6299db9ec823\winit-0.24.0\src\platform_impl\windows\event_loop\runner.rs:152
  30: winit::platform_impl::platform::event_loop::runner::EventLoopRunner<tuple<>>::call_event_handler<tuple<>>
             at C:\Users\marce\.cargo\registry\src\github.com-1ecc6299db9ec823\winit-0.24.0\src\platform_impl\windows\event_loop\runner.rs:239
  31: winit::platform_impl::platform::event_loop::runner::EventLoopRunner<tuple<>>::move_state_to<tuple<>>
             at C:\Users\marce\.cargo\registry\src\github.com-1ecc6299db9ec823\winit-0.24.0\src\platform_impl\windows\event_loop\runner.rs:341
  32: winit::platform_impl::platform::event_loop::runner::EventLoopRunner<tuple<>>::main_events_cleared<tuple<>>
             at C:\Users\marce\.cargo\registry\src\github.com-1ecc6299db9ec823\winit-0.24.0\src\platform_impl\windows\event_loop\runner.rs:227
  33: winit::platform_impl::platform::event_loop::flush_paint_messages<tuple<>>
             at C:\Users\marce\.cargo\registry\src\github.com-1ecc6299db9ec823\winit-0.24.0\src\platform_impl\windows\event_loop.rs:676
  34: winit::platform_impl::platform::event_loop::thread_event_target_callback::{{closure}}<tuple<>>
             at C:\Users\marce\.cargo\registry\src\github.com-1ecc6299db9ec823\winit-0.24.0\src\platform_impl\windows\event_loop.rs:1967
  35: std::panic::{{impl}}::call_once<isize,closure-0>
             at C:\Users\marce\.rustup\toolchains\nightly-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\panic.rs:344
  36: std::panicking::try::do_call<std::panic::AssertUnwindSafe<closure-0>,isize>
             at C:\Users\marce\.rustup\toolchains\nightly-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\panicking.rs:379
  37: winit::platform_impl::platform::monitor::{{impl}}::fmt
  38: std::panicking::try<isize,std::panic::AssertUnwindSafe<closure-0>>
             at C:\Users\marce\.rustup\toolchains\nightly-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\panicking.rs:343
  39: std::panic::catch_unwind<std::panic::AssertUnwindSafe<closure-0>,isize>
             at C:\Users\marce\.rustup\toolchains\nightly-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\panic.rs:431
  40: winit::platform_impl::platform::event_loop::runner::EventLoopRunner<tuple<>>::catch_unwind<tuple<>,isize,closure-0>
             at C:\Users\marce\.cargo\registry\src\github.com-1ecc6299db9ec823\winit-0.24.0\src\platform_impl\windows\event_loop\runner.rs:152
  41: winit::platform_impl::platform::event_loop::thread_event_target_callback<tuple<>>
             at C:\Users\marce\.cargo\registry\src\github.com-1ecc6299db9ec823\winit-0.24.0\src\platform_impl\windows\event_loop.rs:2151
  42: DefSubclassProc
  43: DefSubclassProc
  44: CallWindowProcW
  45: DispatchMessageW
  46: SendMessageTimeoutW
  47: KiUserCallbackDispatcher
  48: NtUserDispatchMessage
  49: DispatchMessageW
  50: winit::platform_impl::platform::event_loop::EventLoop<tuple<>>::run_return<tuple<>,closure-1>
             at C:\Users\marce\.cargo\registry\src\github.com-1ecc6299db9ec823\winit-0.24.0\src\platform_impl\windows\event_loop.rs:218
  51: winit::platform_impl::platform::event_loop::EventLoop<tuple<>>::run<tuple<>,closure-1>
             at C:\Users\marce\.cargo\registry\src\github.com-1ecc6299db9ec823\winit-0.24.0\src\platform_impl\windows\event_loop.rs:188
  52: winit::event_loop::EventLoop<tuple<>>::run<tuple<>,closure-1>
             at C:\Users\marce\.cargo\registry\src\github.com-1ecc6299db9ec823\winit-0.24.0\src\event_loop.rs:154
  53: bevy_winit::run<closure-1>
             at C:\Users\marce\.cargo\git\checkouts\bevy-f7ffde730c324c74\079b3ad\crates\bevy_winit\src\lib.rs:170
  54: bevy_winit::winit_runner_with
             at C:\Users\marce\.cargo\git\checkouts\bevy-f7ffde730c324c74\079b3ad\crates\bevy_winit\src\lib.rs:494
  55: bevy_winit::winit_runner
             at C:\Users\marce\.cargo\git\checkouts\bevy-f7ffde730c324c74\079b3ad\crates\bevy_winit\src\lib.rs:210
  56: core::ops::function::Fn::call<fn(bevy_app::app::App),tuple<bevy_app::app::App>>
             at C:\Users\marce\.rustup\toolchains\nightly-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\core\src\ops\function.rs:70
  57: alloc::boxed::{{impl}}::call<tuple<bevy_app::app::App>,Fn<tuple<bevy_app::app::App>>,alloc::alloc::Global>
             at C:\Users\marce\.rustup\toolchains\nightly-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\alloc\src\boxed.rs:1560
  58: bevy_app::app::App::run
             at C:\Users\marce\.cargo\git\checkouts\bevy-f7ffde730c324c74\079b3ad\crates\bevy_app\src\app.rs:66
  59: bevy_app::app_builder::AppBuilder::run
             at C:\Users\marce\.cargo\git\checkouts\bevy-f7ffde730c324c74\079b3ad\crates\bevy_app\src\app_builder.rs:50
  60: two_d_world_bevy::main
             at .\src\main.rs:19
  61: core::ops::function::FnOnce::call_once<fn(),tuple<>>
             at C:\Users\marce\.rustup\toolchains\nightly-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\core\src\ops\function.rs:227
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
Mar 16 00:57:18.605 ERROR gpu_descriptor::allocator: `DescriptorAllocator` is dropped while some descriptor sets were not deallocated

Code can be found at https://github.com/MTRNord/bevy_learning/tree/f06ca8e721aaf0591b561b7225026a03add7faaf

Just as a note: This also can apparently happen when trying to close the window.

This happened to me when resizing a window to zero in some dimension, should not be hard to fix, maybe I'll make a PR about that.

resizing to 0 should have been fixed by #1409

resizing to 0 should've been fixed by #1409
This also appears to be sort of a duplicate to
#170 #899 (and a few others)

authors: MTRNord NathanSWard atomicbitty mockersf

repo: bevyengine/bevy


text:
Unable to find integrated UDH 620 GPU

I'm running into the 'unable to find gpu' issue when trying to run a project. I've been trying to fix this with the developer but to no avail so figured I'd check here as well
I can run other things that need my Intel UDH 620 GPU fine, such as games, other software but Bevy projects fail stating they cannot find the GPU.
I do have the Intel Vulkan drivers installed, running under Arch Linux. Previously, on my last distro these projects ran flawlessly, however I've followed the advice from issues here which is simply to install Vulkan which I have done, but to no avail.
I'm not sure where to go next from here however, I have the needed Intel Vulkan drivers and followed both the advice here, and the Arch wiki and had no luck at all

closing to centralise in #3191

authors: celtichawk mockersf


text:
Add helper methods on Visibility

Fixes #14825
Edit: After feedback, these are the updated methods:

inherited_if(value: bool) -> Self

Returns Visibility::Inherited if true, else returns Visibility::Hidden.

visible_if(value: bool) -> Self

Returns Visibility::Visible if true, else returns Visibility::Hidden.

toggle_inherited_visible(&mut self)

Toggles between Visibility::Inherited and Visibility::Visible. If the value is Visibility::Hidden, it remains unaffected.

toggle_inherited_hidden(&mut self)

Toggles between Visibility::Inherited and Visibility::Hidden. If the value is Visibility::Visible, it remains unaffected.

toggle_visible_hidden(&mut self)

Toggles between Visibility::Visible and Visibility::Hidden. If the value is Visibility::Inherited, it remains unaffected.

I don't know why my commits from a previous PR which was merged are also included here, but they don't affect the files changed as it was merged anyway 🙄 github fail

I don't know why my commits from a previous PR which was merged are also included here, but they don't affect the files changed as it was merged anyway 🙄 github fail

yeah happens to me all the time 😅

Converted to draft as I feel like there is room for improvement here

Imo these methods do not have clear naming for an outsider and are nonetheless on the verge of being verbose enough that I would probably personally prefer a manual matches!.

from discussion on bevy discord, how about this instead:
toggle_inherited_visible()
toggle_inherited_hidden()
toggle_visible_hidden()

these methods toggle between the 2 states in the name

Yeah this problem is quite hard to solve but I'm determined to find a solution which covers at least some common use cases. I initially thought my wording was quite clear but from what you guys have said it seems to need work! Let me know what you think of the above suggestion (suggested by bestRanar on bevy discord)

@ThomasAlban assuming that these functions simply ignore the variant that is not being toggled, I think those are good :) I can see myself using them!
Btw, that would be @rparrett on GitHub

The Perhaps to bool methods should be removed in favour of simply doing a matches! statement or something, but Methods to convert from bool to visibility in some way would be particularly useful to me in my codebase. Does anyone have any alternate ideas on naming for these methods?

@ThomasAlban agreed that those two would be the most useful ones. Maybe Visibility::inherited_if and Visibility::visible_if?

@alice-i-cecile In my codebase there are loads of places where I have to do
if value {
    Visibility::Visible
} else {
    Visibility::Hidden
}

And it would be so nice if it could be cut down to a single function call such as what I proposed.
Are there any changes that could be made to the naming etc that would improve them for you?
If it's a definite no, I'll remove them :)

Can confirm that I have also seen that pattern crop up a few times. I personally don't use it much because I tend to make my UiNode explicitly visible or invisible through events, but I think this is a valid use-case.

IMO the if pattern is much more readable, sorry!

authors: ThomasAlban alice-i-cecile ickshonpe janhohenheim