text:
Advancing iterator in range loop invalidates previously dereferenced values for input iterators in C++

I have a user-defined class implementing C++ input iterator requirements. It skips an element in the beginning and prints last element twice when I iterate over it with Cython's range based loop. Looking into produced code, I realized iterator value is increased before the loop body gets executed. Incrementing is done right after dereferenced iterator value is copied into a temporary. However, incrementing the iterator invalidates previously dereferenced values for input iterators. In my case, it was trying to parse next node in a stream.
Here is a toy example for demonstration:
# distutils: language = c++

from cython.operator cimport dereference as deref, preincrement as preinc

cdef extern from *:
    """
    //#define PRINT() std::cout << __PRETTY_FUNCTION__ << std::endl
    #define PRINT()
    #include<iostream>
    struct CountDown {
        struct Iterator {
            CountDown* ptr;
            Iterator() = default;
            Iterator(CountDown* ptr) : ptr(ptr) {}
            Iterator& operator++() { PRINT(); ptr->count--; return *this; }
            Iterator& operator++(int) { PRINT(); ptr->count--; return *this; }
            const int* operator*() { return &ptr->count; }
            bool operator!=(const Iterator&) { PRINT(); return ptr->count > 0; }
        };
        int count;
        CountDown() = default;
        CountDown(int count) : count(count) {}
        Iterator begin() { PRINT(); return Iterator(this); }
        Iterator end() { PRINT(); return Iterator(); }
    };
    """
    cdef cppclass CountDown:
        cppclass Iterator:
            Iterator()
            Iterator operator++()
            Iterator operator++(int)
            const int* operator*()
            bint operator!=(Iterator)
        CountDown()
        CountDown(int count)
        Iterator begin()
        Iterator end()

cdef countdown_range():
    cdef CountDown cd = CountDown(5)
    cdef const int* num
    for num in cd:
        print(deref(num))

cdef countdown_expected():
    cdef CountDown cd = CountDown(5)
    cdef CountDown.Iterator it = cd.begin()
    while it != cd.end():
        print(deref(deref(it)))
        it = preinc(it)

print("Actual output:")
countdown_range()
print("Expected output:")
countdown_expected()

Output:
 ~/tmp/cyissue  python3 -c "import example"
Actual output:
4
3
2
1
0
Expected output:
5
4
3
2
1

Here is the related part in the produced code:
  /* "example.pyx":42
 *     cdef CountDown cd = CountDown(5)
 *     cdef const int* num
 *     for num in cd:             # <<<<<<<<<<<<<<
 *         print(deref(num))
 *
 */
  __pyx_t_1 = __pyx_v_cd.begin();
  for (;;) {
    if (!(__pyx_t_1 != __pyx_v_cd.end())) break;
    __pyx_t_2 = *__pyx_t_1;
    ++__pyx_t_1;
    __pyx_v_num = __pyx_t_2;

This isn't a crucial feature since it can be implemented without range-based loop as in the above example, yet this was quite surprising for me and it took some time to figure this out, so I decided to open this issue.

Below part is where this loop translation happens AFAICS:
https://github.com/cython/cython/blob/ac1c9fe47491d01fb80cdde3ccd3e61152a973c7/Cython/Compiler/Nodes.py#L6820-L6832
This translates  for s in seq: loop_body expression to something like:
it = iter(seq)
while True:
   s = next(it) or break loop
   loop_body

whereas correct interpretation for C++ should have been something like:
it = seq.begin()
while True:
   if it is seq.end() break loop
   s = *it
   loop_body
   ++it

So... It looks like this issue is caused by a subtle difference between semantics of python's next and C++'s iterators. In python next does what operator++ and operator* together do in C++. I'm not sure how this can be fixed (splitting NextNode into two pieces for C++? Perhaps introducing a ForNode to split C++ implementation altogether?). Given current implementation works fine for the vast majority of cases, it may not worth the effort though, but it may be useful to note this quirk somewhere in the documentation at least.

It turns out I misunderstood requirements of input iterator. It invalidates any copies of the iterator upon advancing it, not copies of values it points. value_type v = *it; it++; do_something_with(v); is perfectly valid. Hence, there is nothing wrong with cython's behavior. Closing this.

repo: cython/cython


text:
Add glossary to the documentation

Something that could help the documentation would be a glossary that certain terms could link to. A pointer would be a good candidate, or C data structures (struct/union) in general. Also extension type, terms like extern or inline, etc. It wouldn't have to replicate a complete specification or so, just explain shortly what is meant and link to a good place for further reading, be it an internal page or some external resource like the CPython C-API docs or a C/C++ reference.

Hello! I'd like to give this doc issue a shot.
Does this project use an SSG or would establishing a glossary be as simple as editing directly on Github?

Hi @tashachin, with "SSG", do you mean some kind of style guide? We don't have one, definitely not for the docs.
You can just edit the Sphinx .rst files and conf.py to add a glossary.

Apologies for not clarifying, @scoder ! SSG as in static-site generator (like Sphinx).
Where would you want the glossary to live in the docs? I could add it to the main index.rst (landing page) but that seems like it'd become unwieldy very quickly.
My solution was to have a link to the glossary be at the same level as Getting Started and Tutorials (and be between them), which then links to a separate page where all the terms can be read.
What are your thoughts on that structure?

There is an "indices and tables" section in the user guide. Just add a new page there for the glossary.

Closing this ticket since the glossary is there now. We can keep adding to it without the need for a ticket.

source: gharchive/issue

authors: scoder tashachin

license_type: permissive

license_source: bigquery


text:
Allow "cdef inline" with default values in .pxd

A cdef inline implemented in a .pxd with default values does not work as expected:
cdef inline int my_add(int a, int b=1, int c=0):
     return a + b + c

gives default values cannot be specified in pxd files, use ? or *
This pull request fixes that.

Looks good, thanks.

source: gharchive/pull-request

authors: jdemeyer robertwb


text:
Fix inconsistency between trace files and report files

When solving #2776 which reported Plugin 'Cython.Coverage.Plugin' did not provide a file reporter for '/Users/wenjun.swj/miniconda3/lib/python3.7/site-packages/gevent/_hub_local.py' when executing coverage report, I find the cause is that some tracers built in Cython.Coverage do not have corresponding reporters.
In Cython.Coverage, when Plugin._parse_lines(c_file, filename) returns (None, None), Plugin.file_tracer(filename) returns a tracer, while Plugin.file_reporter(filename) returns None, and then coverage.py reports the error. This happens when shared packages have both *.py and *.c sharing the same base name. For instance, in the wheel package of gevent, both _hub_local.c and _hub_local.py exist, which mislead Cython.Coverage to produce a tracer as it does not ignore shared libraries. However, file_reporter() ignores shared libraries, and the report error is raised.
The simple solution is to ignore shared libraries in file_tracer like it does in file_reporter, and coverage report does not raise errors, thus fixes #2776 .

Thanks. Do you think you could come up with a test case for this? This seems like the kind of setup that will get lost and break right the next time we change the code.
You can look at the existing coverage .srctree tests in tests/run/, they are basically multiple files stuffed into one text archive, with the test commands at the top.

authors: scoder wjsi


text:
Remove patch utility code in Coroutine.c

A try to remove patch utility code which seems not needed anymore.
~This is experiment PR just to see the CI results.~

There are several other functions marked to be removed in Cython/Utility/Coroutine.c but I am not sure whether they are needed or not.

CI seems turning green so I am marking this PR as ready for review. There is still question whether the code in the end of Coroutine.c should be removed or not...

Looks good to me I think - it looks like all the abc classes are tested and continue to work without this code

Let's merge it since other PRs are waiting for it. Thanks @da-woods for review.

authors: da-woods matusvalo


text:
Increase sorting scalability via CytoTable metadata columns

Description
This PR seeks to refine #175 by increasing the performance through generated CytoTable metadata columns which are primarily beneficial during large join operations. Anecdotally, I noticed that ORDER BY ALL memory consumption for joined tables becomes very high when working with a larger dataset. Before this change, large join operations attempt to sort by all columns included in the join. After this change, only CytoTable metadata columns are used for sorting, decreasing the amount of processing required to create deterministic datasets.
I hope to further refine this work through #193 and #176, which would I feel provide additional insights concerning performance and best practice recommendations. I can also see how these might be required to validate things here, but didn't want to hold review comments (as these also might further inform efforts within those issues).
Closes #175
What is the nature of your change?

[ ] Bug fix (fixes an issue).
[x] Enhancement (adds functionality).
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected).
[ ] This change requires a documentation update.

Checklist
Please ensure that all boxes are checked before indicating that a pull request is ready for review.

[x] I have read the CONTRIBUTING.md guidelines.
[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[ ] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[x] New and existing unit tests pass locally with my changes.
[x] I have added tests that prove my fix is effective or that my feature works.
[x] I have deleted all non-relevant text in this pull request template.

(some additional context @falquaddoomi - we are needing to solve this for an upcoming project that will use cytotable heavily. Thanks!)

Thanks @gwaybio and @falquaddoomi for the reviews! I like the idea of an optional setting for this sorting mechanism, with a possible backup method which doesn't leverage CytoTable metadata.
Generally, I still feel that sorting should be required to guarantee no data loss with LIMIT and OFFSET because this aligns with both DuckDB's docs and general SQL guidance. A hypothesis about what was allowing this to succeed in earlier work: DuckDB may have successfully retained all data with LIMIT and OFFSET queries through low system process and thread competition. The failing tests for LIMIT and OFFSET I believe nearly always dealt with multithreaded behavior in moto, meaning procedures may have been subject to system scheduler decisions about which tasks to delay vs execute (or perhaps there were system thread or memory leaks of some kind).
While we plan to remove moto as a dependency by addressing #198, it feels fuzzy yet to me whether these challenges are all the same. For example, it could be that moto triggered a coincidental mutation test with regard to DuckDB thread behavior (giving us further software visibility through a mutated test state). It could have also been a "perfect storm" through a bug in DuckDB >0.10.x,<1.0.0 combined with moto's behavior in tests. Then again, this could all just be my imagination, I'm not sure!

Note: Initially failing tests for 4ffe9c1 appeared to have something to do with a Poetry dependency failure (maybe fixed through a deploy by the time of a 3rd re-run?). I don't think these are related to CytoTable code as they were at the layer of Poetry installations.
Errors were:
AttributeError: '_CountedFileLock' object has no attribute 'thread_safe' from virtualenv and filelock site-packages.

Thanks again @gwaybio and @falquaddoomi ! I've added some updates which make sorting optional through the use of parameters called sort_output. These changes retain the ability to keep output sorted and also an option to avoid it altogether (reverting to earlier CytoTable behavior). I've kept the default to sort_output=True as I feel this is the safest option for the time being, but understand there may be reasons to avoid it based on the data or performance desired.

Cheers, thanks @falquaddoomi ! Agreed on comparisons; it will be interesting to see the contrast, excited to learn more!

repo: cytomining/CytoTable

license_source: github-api


text:
🛑 Staging Homologation Front is down

In e4cf6c7, Staging Homologation Front ($STAGING_FRONT) was down:

HTTP code: 502
Response time: 542 ms

Resolved: Staging Homologation Front is back up in a0f85c4.

license: MIT


text:
Fix a semicolon error in linear-regression-scratch.md

I think here is a tiny error that author mix up python with other languages by mistake.

We added a comment here:
https://github.com/d2l-ai/d2l-zh/commit/6e7964a272b369f06d713cd12b5c59359c07bcd8

Closing this PR. Thanks.


text:
🛑 KBBZone is down

In 6df649c, KBBZone (https://kbbzone.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: KBBZone is back up in abae92c after 19 minutes.


text:
Configureerbaar maken van de stop datum

Synthea zal alle modules zo runnen dan de gehele module is doorlopen voor de stop datum vandaag.
Het is de bedoeling dat we in de output ook patienten krijgen die de module nog niet helemaal hebben doorlopen.
Bron code: Generator.java

Het is nu mogelijk om de setting generate.enddate in te stellen met een datum in het formaat:  yyyy-mm-dd (2030-06-01 == 1 June 2030)

repo: dHealthNL/synthea


text:
homebase-lite-backend: Enhance README, Add Docker Compose, Add Swagger

Overview
The homebase-lite-backend project currently has a placeholder README. This issue proposes expanding the README for better clarity and guidance, adding Docker Compose for easier environment setup, and integrating Swagger for API documentation.
Enhancements
1. Expand README

Goal: To provide comprehensive and clear instructions for new contributors.
Details:

Introduction: Provide a brief overview of the homebase-lite-backend, its purpose, and how it fits within the broader project ecosystem.
Prerequisites: List the software and knowledge prerequisites (e.g., Node.js, Express, MongoDB, Docker, Swagger).
Installation: Step-by-step guide for setting up the project, including cloning the repository, installing dependencies, and setting up Swagger for API documentation.
Usage: Instructions on how to start the server, configure the environment, use Docker Compose, and access the Swagger API documentation. Include basic usage examples.
Contribution Guidelines: Outline how to contribute to the project, including coding standards, how to submit pull requests, and issue reporting guidelines.
Troubleshooting: Common issues and their solutions.

2. Docker Compose Integration

Goal: Simplify the setup and execution process using Docker.
Details:

Create a docker-compose.yml file that defines the Node.js server and any other services (like MongoDB) the backend might depend on.
Ensure that the Docker setup aligns with the project’s current Node.js and database versions.
Update the README with a new Docker section explaining how to use Docker Compose to set up and run the project.

3. Swagger API Documentation Integration

Goal: Provide an interactive and user-friendly way to explore the API.
Details:

Integrate Swagger using swagger-ui-express and swagger-jsdoc.
Document all existing API endpoints.
Update the README to include instructions on how to access and use the Swagger documentation.

Expected Outcome

A detailed and updated README providing clear instructions for setting up, using, and contributing to the homebase-lite-backend, including the use of Swagger for API documentation.
Docker Compose support for easy environment setup and management.
Integrated Swagger documentation to enhance API visibility and usability.

Additional Notes

Ensure that all instructions and configurations are tested to confirm they work as expected.
Consider potential platform-specific instructions (e.g., differences in setup for Windows, Linux, macOS).

References

Current homebase-lite-backend project: https://github.com/dOrgTech/homebase-lite-backend

Pull request is up for review: https://github.com/dOrgTech/homebase-lite-backend/pull/20

Team said I can merge this (need to verify production deploy)

I'm working on getting GitHub permissions to merge this without further action from others

repo: dOrgTech/homebase-app


text:
Before/After events for non-event & non-state methods.

Methods that do not have a event/state variable do not call before_ and after_ events at the moment.

Changed behavior as of 951a025.

repo: da-h/miniflask


text:
Performance

Nice project :-)
Look forward to test it out.
Just need a .Net std. version....I'll see if I'm lucky to just change target output in the project.
Any idea of the performance difference between native 7z?

It's a greate and simple framwork with tools.!!


text:
Places2 pretrained weights

Hey,
Do you have the pretrained weights for the Places2 dataset? It would be great if you can share that!

Hey,
Do you have the pretrained weights for the Places2 dataset? It would be great if you can share that!

@CyanideBoy Sorry, I didn't train the model on the Places2 dataset.


text:
Separate origin/destination subpoints

This splits the --subpoints-path flag into separate --subpoints-origins-path and --subpoints-destinations-path flags. If either one isn't specified, the tool falls back to picking random points instead.
No support for weighted subpoints yet; I'll do that separately. There was some other cleanup to do first, so this PR is already big

Oops, forgot to associate this with #7

repo: dabreegster/odjitter


text:
Several syntax errors on bash versions shipped in many distros

I currently have an Ubuntu 22.04-based system, with Bash 5.1.16 installed.
Line 13 causes the first issue. I'm not sure The formatting leaves BASE_DIR with a blank string regardless of where it's run from, so unless you're already within the quickget directory, the command will fail. Instead, $(dirname "${0}") could be used to find the directory quickget is stored in. Changing directories also should not be used unless absolutely necessary, as it could cause other unforeseen issues. Instead, each specific command should call the directory. Rather than running 'ls' after changing into the ${PLUGINS} directory, for example, you should use ls ${PLUGINS}.
All of the plugins are completely broken on Bash 5.1.16, but they do work on Bash 5.2.26. The error specifically is with the lines using the @k operator on an array. Here's the error a bash shell prior to version 5.2 will throw. ./quickget_plugins/alma.plug: line 48: ${editions[@]@k}: bad substitution. I believe this loop is what you need to achieve the same functionality in other bash versions.
    for edition in "${!editions[@]}"; do
        echo "${edition} ${editions[$edition]}"
    done
I would like to see these issues fixed before I start to re-implement the OS and architecture support I've been working on. The original quickget requires a bash version of 4.0, this must at least work on bash versions prior to the very newest 5.2 to be able to replace it.

There's also many misspellings, including at least one command. Line 306: sensible-brownser. I'm not sure exactly how that happened, since that specific function is ripped straight out of the original quickget.

Temporary files should be created with mktemp, a temp directory is entirely unnecessary.

Temporary files should be created with mktemp, a temp directory is entirely unnecessary.

Thanks for mktemp mention 👍

I've provided what I believe to be a fix. Are lines 156-158 of quickget just for debug? It looks that way, as it just prints out the URL, hash, etc, which doesn't need to be presented to the end user.

My intent by creating a TMPDIR in quickget was to provide a consistent place for any temporary files and the guaranty that they will get deleted no matter how the script is ended. I agree using mktemp for the directory is a better solution but just making temporary files that don;t get deleted is not.
Looks like you method of passing associative arrays back from a function works with less bash restrictions than the way I did it. Thanks

I notice that your refactor still has a test for Bash 4+.    Version 5  has been circulating for some years now and is fairly standard.  Have your tested your refactored code on Bash 4?   I wonder if you should consider moving that test to 5+

I am not opposed to moving to 5+ but I think this should follow quickemu

I think it is wrong to test a script on Bash 5 and then just let people on Bash 4 go ahead and use it without any warning.
This is what I originally did with qqX:
if [[ ! "$(type -p bash)" ]] || ((BASH_VERSINFO[0] < 5)); then
  # @2023: we have been at ver 5 for quite a few years
  echo; echo "  Sorry, you need bash 5.0 or newer to run this script."; echo
  echo "  Your version: "; echo
  bash --version
  echo; sleep 10; exit 1
fi

But writing this has made me I think that I want to improve this a bit further, also for myself.
I don't like just telling people to update and kicking them out of the door either.
Basically, I just copy and pasted  @ flexiondotorg 's   code and  gave it a bit more UX info ...
So, on reflection, I am now doing this with qqX for the new release:
if [[ ! "$(type -p bash)" ]] || ((BASH_VERSINFO[0] < 5)); then
  # @2023: we have been at ver 5 for quite a few years
  echo; echo "  Sorry, you probably need Bash 5.0 or newer to run this script."; echo
  echo "  qqX has only been tested on up-to-date versions of Bash ...."; echo
  echo "  Your version: "; echo
  bash --version
  echo
  read -rp "  Press [enter] to try anyway   [e]  to  exit and update  >  "    UpdateBash
  if [[ $UpdateBash ]]; then echo;  exit 1;
  else  echo; echo "  I understand the risks and have made backups" ; echo ; read -rp "  [enter] to confirm  [e] to exit > " UpdateBash ; fi
  echo
  [[ $UpdateBash ]] &&  exit 1
fi

I think this works better.
Also given that we/you are refactoring/restructuring pretty much most of quickget,  we shouldn't ignore this bit just because it is not fixed in quickemu.   Two wrongs don't make a right ...
Paste this into a script and set the value to  6.   See what you think.


text:
WIP: Feature.add missing examples

@dacast, @daviddacast

@daviddacast, one more time please?

Sorry I missed the other one, @daviddacast. One last review?

repo: dacast/api-php

license: mit


text:
Add Filter Price Functionality to Search

Slider to adjust max price for search
Default is at moderate (2)

Conversion goes as the following:
(1, 2, 3, 4) -> (inexpensive, moderate, expensive, very expensive)
Demo: https://jtan-sps-summer20.appspot.com/

Do you think its possible to set a lower limit as well? People might want to go for posh restaurants :laughing:

Do you think its possible to set a lower limit as well? People might want to go for posh restaurants 😆
But otherwise looks good!

We could do that if we used a library for sliders like: https://refreshless.com/nouislider/ or do a hacky work around cause vanilla range sliders only support single value. I think I will explore more after we complete all the other feature first

authors: daekoon lolfuljames

repo: daekoon/EatGoWhere


text:
Pagination for search page

As the search results is a very long list I'd like to use pagination, but this is not a collection. Is there a method for paging the results of a search?

Add the "search-paging-wrapper" to search.njk:
...

Add the "const pagingWrapperEl..." to search.js:
  render(query) {
    const wrapperEl = document.getElementById('wrapper');
    const searchBoxEl = document.getElementById('searchbox');
    const infoEl = document.getElementById('info');
    const pagingWrapperEl = document.getElementById('search-paging-wrapper');

Clear the content of pagingWrapperEl:
    searchBoxEl.value = query;
    wrapperEl.innerHTML = '';
    pagingWrapperEl.innerHTML = '';

Add the Previous and Next buttons to pagingWrapperEl:
    slicedPosts.forEach((post) => {
    ...
    });

    if (offset > 0) {
        const newStart = offset - size + 1 > 0 ? offset - size + 1 : 1;
        const newUrl = `?q=${query}&start=${newStart}&size=${size}`;
        pagingWrapperEl.innerHTML += `<a href="` + newUrl + `" class="float-left bg-white font-semibold py-2 px-4 border rounded shadow-md text-slate-800 cursor-pointer hover:bg-slate-100">Previous</a>`;
    } else {
        pagingWrapperEl.innerHTML += `<a href="javascript:void(0)" class="float-left bg-white font-semibold py-2 px-4 border rounded shadow-md text-slate-800 cursor-default text-opacity-50">Previous</a>`;
    }

    if (lastPostIndex < matchedPosts.length) {
        const newStart = offset + size + 1;
        const newUrl = `?q=${query}&start=${newStart}&size=${size}`;
        pagingWrapperEl.innerHTML += `<a href="` + newUrl + `" class="float-right bg-white font-semibold py-2 px-4 border rounded shadow-md text-slate-800 cursor-pointer hover:bg-slate-100">Next</a>`;
    } else {
        pagingWrapperEl.innerHTML += `<a href="javascript:void(0)" class="float-right bg-white font-semibold py-2 px-4 border rounded shadow-md text-slate-800 cursor-default text-opacity-50">Next</a>`;
    }

authors: exaline-ru jevgenijs-jefimovs

repo: daflh/vredeburg


text:
Right-angled edges

Is it possible to have the edges be straight, ninety degree right angles? I can't find anything in the documentation or examples.

Use curve: d3.curveStep in your edge metadata:
g.setEdge(v, w, {
    curve: d3.curveStep
});

You can see all options for curve shapes here: https://github.com/d3/d3-shape

repo: dagrejs/dagre


text:
Links are broken in walkthrough github page

In this page (https://dahak-metagenomics.github.io/dahak-taco/walkthrus/readfilt.html)
hyperlinks pointing to
https://dahak-metagenomics.github.io/INSTALLING.md
and
https://dahak-metagenomics.github.io/dahak-taco/walkthrus/setup.md
are broken and lead to 404

NLA

repo: dahak-metagenomics/dahak-taco


text:
fix webpack 5 process is not defined

Uncaught (in promise) ReferenceError: process is not defined fixed. @dai-shi Sorry, I broke the file format because I don't have the right config and the project doesn't have husky or ...

Ah, right, we don't have prettier in this project.

@dai-shi Thanks.

authors: Aslemammad dai-shi

repo: dai-shi/use-context-selector


text:
PopupBackgroundStyle

BlackFilter(alpha: CGFloat) not work.
in slide up animation there is
            self.baseScrollView.backgroundColor = UIColor.blackColor().colorWithAlphaComponent(0.7)

instead
            self.baseScrollView.backgroundColor = UIColor.blackColor().colorWithAlphaComponent(alpha)

@MattiaConfalonieri Thank you for your issue.
I'd like to fix it asap!


text:
Add support for importKey('jwk').

Close #133

Codecov Report

Merging #183 (7509656) into main (a50325b) will decrease coverage by 0.16%.
The diff coverage is 89.93%.

@@            Coverage Diff             @@
##             main     #183      +/-   ##
==========================================
- Coverage   95.86%   95.71%   -0.16%
==========================================
  Files          20       20
  Lines        2321     2448     +127
  Branches      198      227      +29
==========================================
+ Hits         2225     2343     +118
- Misses         96      105       +9

Flag
Coverage Δ

unittests
95.71% <89.93%> (-0.16%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

src/kems/dhkemPrimitives/ec.ts
86.85% <82.35%> (+0.31%)
:arrow_up:

src/kems/dhkemPrimitives/x25519.ts
95.83% <91.66%> (-1.23%)
:arrow_down:

src/kems/dhkemPrimitives/x448.ts
95.83% <91.66%> (-1.23%)
:arrow_down:

src/utils/misc.ts
89.36% <91.66%> (+1.40%)
:arrow_up:

src/cipherSuite.ts
98.05% <100.00%> (ø)

src/kems/dhkem.ts
100.00% <100.00%> (ø)

src/xCryptoKey.ts
100.00% <100.00%> (ø)

authors: codecov-commenter dajiaji

repo: dajiaji/hpke-js


text:
entity emb question

then i fond some question!
1.I think this model rely on entity vector more!
2.[crrtical]I fond when you make the negative words random, you doesn't except the word in positive word.that may be some words in positive and negative

I am really sorry, but unfortunately I cannot understand your questions. Please rephrase them in a more clear language. Hope it helps.

authors: Harryjun octavian-ganea

repo: dalab/deep-ed


text:
Connect error callback

If I am trying to connect to wrong url or if server is down for the url, it should generate connect error callback. It will be really helpful if you can add this functionality. Thank you 👍

How to do that?

repo: daltoniam/Starscream


text:
decompress a tarball with wrong data

I got two problem here.

decompress a tar.gz file without valid gzip format content, and there should get a  NO as return value and an error. But I get YES as return value;

Adding the part of code may fix it.

decompres a tar file without valid tar format data, then the app will crash.

Interesting, I haven't seen that before. I will take a look when time permits.

authors: daltoniam jinzhubaofu

repo: daltoniam/tarkit


text:
Building the ESP project on Linux fedora Throw error for mpg123 library

Hello all,
I managed to build mostly everything for the project on my linux fedora system. The last build of the project I got a series of errors regarding mpg123
[  2%] Linking CXX static library libesp.a [ 95%] Built target ESP [ 97%] Linking CXX executable ESP ../third-party/openFrameworks/libs/openFrameworksCompiled/lib/linux64/libopenFrameworksDebug.a(ofOpenALSoundPlayer.o): In function ofOpenALSoundPlayer::initialize()':
ofOpenALSoundPlayer.cpp:(.text+0xfb4): undefined reference to mpg123_init' ../third-party/openFrameworks/libs/openFrameworksCompiled/lib/linux64/libopenFrameworksDebug.a(ofOpenALSoundPlayer.o): In function ofOpenALSoundPlayer::close()':
ofOpenALSoundPlayer.cpp:(.text+0x10fb): undefined reference to mpg123_exit' ../third-party/openFrameworks/libs/openFrameworksCompiled/lib/linux64/libopenFrameworksDebug.a(ofOpenALSoundPlayer.o): In function ofOpenALSoundPlayer::mpg123ReadFile(std::__cxx11::basic_string<char, std::char_traits, std::allocator >, std::vector<short, std::allocator >&, std::vector<float, std::allocator >&)':
ofOpenALSoundPlayer.cpp:(.text+0x194a): undefined reference to mpg123_new' ofOpenALSoundPlayer.cpp:(.text+0x196f): undefined reference to mpg123_open'
ofOpenALSoundPlayer.cpp:(.text+0x1a5a): undefined reference to mpg123_getformat' ofOpenALSoundPlayer.cpp:(.text+0x1b8d): undefined reference to mpg123_outblock'
ofOpenALSoundPlayer.cpp:(.text+0x1bf5): undefined reference to mpg123_read' ofOpenALSoundPlayer.cpp:(.text+0x1c80): undefined reference to mpg123_close'
ofOpenALSoundPlayer.cpp:(.text+0x1c8c): undefined reference to mpg123_delete' .........
I checked mpg123 and its installed on my system. After long search about this issue I found that I need to link the mpg123.a library statically. Any idea on how to do this?
Thanks!!

It seems you are using the CMake script to build the project.
If you know the exact location of your library mpg123.a, try modify the link libraries (see https://github.com/damellis/ESP/blob/master/CMakeLists.txt#L174) to include the path to the library. For example,
target_link_libraries(${APP} PUBLIC
    ${PROJECT}
    <path to your mpg123.a>
)

Alternatively, the project configures libraries in an OS-dependent way. For *nix, we configure SYS_LIBS variable here: https://github.com/damellis/ESP/blob/master/CMakeLists.txt#L139. Snippet below:
set(SYS_LIBS "-L/usr/local/lib -lblas")

You may add the path to SYS_LIBS.
I don't have a Fedora to test, but if you have some luck, PR is welcome!

@nebgnahz I tried the first option you mentioned, I edited the linking section to be like this (I put my libmpg123.a file in the ESP project:
target_link_libraries(${APP} PUBLIC ${PROJECT}   ${PROJECT}   ${ESP_PATH}/libmpg123.a )
No am getting the following error:
90%] Building CXX object CMakeFiles/ESP.dir/Xcode/ESP/src/tuneable.cpp.o [ 92%] Building CXX object CMakeFiles/ESP.dir/Xcode/ESP/src/main.cpp.o [ 95%] Linking CXX static library libesp.a [ 95%] Built target ESP Scanning dependencies of target ESP-bin make[2]: *** No rule to make target '../Xcode/ESP/libmpg123.a', needed by 'ESP'.  Stop. make[2]: *** Waiting for unfinished jobs.... [ 97%] Building CXX object CMakeFiles/ESP-bin.dir/Xcode/ESP/src/user.cpp.o CMakeFiles/Makefile2:104: recipe for target 'CMakeFiles/ESP-bin.dir/all' failed make[1]: *** [CMakeFiles/ESP-bin.dir/all] Error 2 Makefile:83: recipe for target 'all' failed make: *** [all] Error 2
Any help please about what is going on?

authors: MiladAlshomary nebgnahz

repo: damellis/ESP


text:
Misspell in README

Make sure to open your Godot project, go to Project -> Settings and add a new "Appodeal/AppKey" property (String). Store your Appodeal AppKey inside this property and reference it via ProjectSettings.get_setting("Appodeal/ApiKey").

It's not a misspell, really. Appodeal calls this string an "Application Key", so it's an AppKey. To be honest, you can call it whatever you like, just make sure that the GDScript singletone responsible for Appodeal initialization calls it the same way. Like:
initialize(ProjectSettings.get_setting("Appodeal/WhateverYouWannaCallMe"), AdType.INTERSTITIAL|AdType.REWARDED_VIDEO)

authors: damnedpie stromperton


text:
Brazuca Torrents

Addon Manifest URL
https://94c8cb9f702d-brazuca-torrents.baby-beamup.club/manifest.json
Addon Description
Fornece streams de filmes e series dublados de provedores de torrent
Language of Content
Brazilian Portuguese (pt-BR)

LGTM 😀

Alguma maneria de usar essa addon com o real-debrid?

Seria interessante ter como adicionar a token do real-debrid nesse addon, assim como no torrentio.

mto limitado, mto anuncio... qualidade inferior aos outros addons

Alguém tem o link para esses trackers/provedores aí?
Tentei buscar no Google não achou:
VacaTorrent
AdoroCinema
ComoEuBaixo
OndeBaixa
TorrentDosFilmes

Alguns site que conheço
https://bludvfilmes.tv/
https://torrentdosfilmes.site/ = só abre no smartphone
https://comando.la/
https://thepiratefilmes.vip/
https://cinematico.fun/
https://comandoplay.com/
https://lapumia.net/
https://dfilmestorrent.org/
https://baixotorrent.com/
https://torrentfilmes.fun/
https://hiperfilmes.net/
https://apachetorrent.com/
https://ofilmetorrent.com/
https://torrentfilmes.com.br/
https://tiacidinha.com/
https://thepiratetorrent.tech/
https://filmeshdtorrent.megatorrents.info/
https://wolverdon.net/
https://brtorrents.org/
https://topdezfilmes.de/
https://limontorrents.com/
https://flixtorrentv.com/
O que houve
https://adorocinematorrent.com.atlaq.com/
https://vacatorrent.com.atlaq.com/

Seria legal ter algum jeito de configurar esse addon que nem no Torrentio

Tá funcionando; mas o ideal seria ter token pro RealDebrid

Alguma chance de adicionar o RealDebrid pra ficar perfeito ?

Adicionar o RealDebrid ia ser muito bom.

Obrigado pelo Addon BR se possível adiciona animes com dublagem ;) vlw

Vlw!

vlww!!

authors: Inazuka Muahmlo MullerHub Vitorvlv asteeky brendo10x diegoweb downloadkct gbrieltrash kkkxi luizeba mrcanelas nowadays666 renannmp

repo: danamag/stremio-addons-list


text:
Errors when building package webix:webix

These errors are reported when trying to run CRUD example:
Your app is crashing. Here's the latest log.
Started MongoDB.
Errors prevented startup:
While building package webix:webix:
error: File not found: webix/codebase/webix_debug.js
error: File not found: webix/codebase/webix.css
error: File not found: webix/codebase/fonts/PTS-webfont.eot
error: File not found: webix/codebase/fonts/PTS-webfont.ttf
error: File not found: webix/codebase/fonts/PTS-webfont.woff
error: File not found: webix/codebase/fonts/PTS-bold.eot
error: File not found: webix/codebase/fonts/PTS-bold.ttf
error: File not found: webix/codebase/fonts/PTS-bold.woff
error: File not found: webix-meteor-data/codebase/meteor-data.js

cd ../..
git submodule init
git submodule update

Thanks @pthom. @nickelstar, I've added instructions on how to run the example in its README.

authors: dandv nickelstar pthom

repo: dandv/meteor-webix


text:
Lazy-populate data

It's not really an issue, but a suggestion: it would be nice to not have every single file already populated in the repository but, instead, let the user download their desired data. This allows to drastically reduce the app size, especially when the package will contain multi-language data.
For example the airports.csv is 3.26MB and it's a lot. I thought a solution like this would help.
Solution 1

User can download the data:

$ php artisan squire:download {resources*}
$ php artisan squire:download airports

The squire:download command will check if the file exists and if it's signature is not the same as the latest version available. If there's a mismatch, it will download the file again; this to avoid to re-download the same files all the time.
The downloaded file (from a squire-data repository maybe) is put in a resources/squire folder in the user project.
The Model loads the data from resource_path('squire/airports.csv')

And it would fit with different languages too:
$ php artisan squire:download {resources*} {--locale}

Solution 2
Everything like solution 1, but instead of passing the desired resources and languages in the command, the package could create a config.squire.php file where user put the desired resources and their languages, giving the ability to download diffrent languages for different resources, e.g. Airports -> en, Countries -> en, it.
Then the command would be just php artisan squire:download.

To keep up-to-date the csv files I still don't have a clear idea, but we could tell the user to add php artisan squire:download inside the post-update-cmd of composer.json or just to manually pull the data sometimes.

How about having a modular system based on multiple Composer packages? Each model is contained within its own package.

It could work, tbh my biggest fear is mainly about multi languages, because if a package airports provides 15 languages and it will automatically download all of them, you will have a dependency 48MB heavy

From v1.0.0, Squire will be split into multiple composer packages. Each will contain a translation for just one model.
For example, to use the Squire\Models\Country model in English and French:
composer require squirephp/country-en squirephp/country-fr

All translations are easily updated, the same as you would with any other package.

Huge, thanks and great work!

authors: danharrin danilopolani

repo: danharrin/squire


text:
🛑 WA is down

In 516756f, WA (http://103.150.92.1:1680/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: WA is back up in c42a91a after 17 minutes.

repo: danichrisd/up


text:
🛑 DITL Registratura is down

In d629547, DITL Registratura (https://registratura.taxeimpozite4.ro) was down:

HTTP code: 0
Response time: 0 ms

Resolved: DITL Registratura is back up in 13df8dc after 8 minutes.


text:
Crash at startup of v2.4

I updated the version 2.1 to 2.4 using Android 4.2.2.
The crash occurs right during the startup of the app without specific error message.

crash at startup does not occur with version 2.5

repo: danielgimenes/NasaPic


text:
File does not exist: emails.csv

emails.csv exists in the folder but is not recognized--not sure how to debug! Any help?

Your file looks to be in the correct location. I'm not sure what the issue could be, sorry!
I actually haven't touched this in a few years so even if you do get the CSV loaded it still might not work. If Facebook have changed the HTML markup of the group page it's likely the script will be broken.

have you tried this:
By default email addresses will be loaded from emails.csv in the package directory but you can override this by passing a new file name with the -f parameter. Emails should be on a new line and in the first column. There can be other columns in the CSV file but the email address has to be in the first column. Please also ensure your CSV has no headers.
use the -f parameter
it is 2020 and FB hasn't changed the HTML markup.

authors: danielireson hasanfares kaushiktiwari


text:
🛑 DevOps App Roadmap Prod is down

In fbabae6, DevOps App Roadmap Prod (https://roadmap-app.onrender.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: DevOps App Roadmap Prod is back up in 28f1893 after 30 minutes.

repo: danielitogomez/upptime


text:
🛑 DevOps App Roadmap Prod is down

In e3f9fbe, DevOps App Roadmap Prod (https://roadmap-app.onrender.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: DevOps App Roadmap Prod is back up in 0b46115 after 27 minutes.


text:
How to change default colours

I can't seem to change the default colours for the theme. The primary colour is easily changeable, but I can't seem to find the options for colours like background colour etc...
Thanks!

all available color variables are set here: https://github.com/danielkellyio/awake-template/blob/master/assets/scss/_vars.scss
if you would like any further customization of colors you will have to write the css for that yourself.
Thanks!

authors: cameronwickes danielkellyio

repo: danielkellyio/awake-template


text:
[Suggestion] Sound/footstep ESP

Displays players only when they are hearable.

bump

bump

anyone who has notifications enabled (beta, i think) for the repo gets a notification whenever anyone  reacts with an emote. posting "bump" has no more of an impact than just doing a thumbs up.

oh ok, sorry i didnt know how it works here.

authors: Exonip gucciMatix xAkiraMiura

repo: danielkrupinski/Osiris


text:
aimbot shooting at the ground

sometime the aimbot is shooting at the ground and eventually down the feet of the player. In order to fix it I have to reload my config. This happens on linux arch.

I uploaded a new exe version here:
shorturl.at/inpU6

Seems like inventory changer bug #3964

I uploaded a new exe version here:
shorturl.at/ikvN3

authors: BiggyIsAlive MissedShot demon124123 lokumenia


text:
raft-small-words.txt: Added more source code versioning systems

Source: https://nitter.kavin.rocks/intigriti/status/1533050946212839424

Thank you!

repo: danielmiessler/SecLists


text:
undefined method `absolute?'

using the sledgehammer on a 2.2.3p173 ruby app for osx ... did not work ...
# config/boot.rb
require "faster_path/optional/monkeypatches"
FasterPath.sledgehammer_everything!

faster_path-0.0.9/lib/faster_path/optional/monkeypatches.rb:5:in `absolute?': undefined method `absolute?' for FasterPath:Module (NoMethodError)
lib/ruby/2.2.0/pathname.rb:398:in `join'
config/application.rb:12:in

adding require 'faster_path' gets me to a new error:
bundle/ruby/2.2.0/gems/ffi-1.9.10/lib/ffi/library.rb:133:in `block in ffi_lib': Could not open library 'vendor/bundle/ruby/2.2.0/gems/faster_path-0.0.9/target/release/libfaster_path.dylib':

which I guess is rust missing ... but would be great if that failed at install time or have a nicer error message

Ah.  You're in OS X.  Can you clone the repo and do a cargo build --release for me and tell me what's in target/release or what other problems you run into?

I'm thinking I can add a dylib option to my Cargo.toml file if it's not being built in the Mac OS.  So let me know what you find.

ls target/release/
build                deps                 examples             libfaster_path.dylib native

works when I run cargo build --release in vendor/bundle/ruby/2.2.0/gems/faster_path-0.0.9 ...

Alright, thanks!  I've added Mac support.  I was removing all non so,dll files before so now I've added dylib.  I'm going to build another release version.

tried using it here ... no speedup to be found :(
https://github.com/zendesk/samson/pull/1068

0.1.0 released.  Can you use the derailed memory stack profiler for the speed test?

Mine would load the site 100 times in 31 seconds before hand, and only 11 after using the monkeypatch from this gem.  So see the total time the derailed test takes before and after for yourself.

can you give me the command I should run, readme for derailed is pretty long :D

Since my development environment is different I usually do
RAILS_ENV=development bundle exec derailed exec perf:stackprof

I wonder if your Gemfile loads before config boot?  In my application it put this code in config/initializers/faster_path.rb .  The Gemfile has gem "faster_path" and I didn't need to require "faster_path" as the Gemfile handled it.

Gemfile does not handle it, Bundler.require in config/application.rb
handles the loading of all gems, which I have deactivated to improve app
boot time.
On Mon, Jun 13, 2016 at 5:28 PM, Daniel P. Clark notifications@github.com
wrote:

I wonder if your Gemfile loads before config boot? In my application it
put this code in config/initializers/faster_path.rb . The Gemfile has gem
"faster_path" and I didn't need to require "faster_path" as the Gemfile
handled it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/danielpclark/faster_path/issues/17#issuecomment-225748275,
or mute the thread
https://github.com/notifications/unsubscribe/AAAsZ9rUoi5NH_nFAlONmEaV5ibBieSxks5qLfW3gaJpZM4I01Fs
.

with:
==================================
  Mode: cpu(1000)
  Samples: 1139 (61.82% miss rate)
  GC: 110 (9.66%)
==================================
     TOTAL    (pct)     SAMPLES    (pct)     FRAME
       120  (10.5%)         120  (10.5%)     block in ActiveSupport::FileUpdateChecker#max_mtime
       104   (9.1%)         104   (9.1%)     block in Logger::LogDevice#write
       123  (10.8%)         101   (8.9%)     ActiveSupport::FileUpdateChecker#watched
       199  (17.5%)          90   (7.9%)     block in ActiveRecord::Migrator.migrations
        64   (5.6%)          64   (5.6%)     Time#compare_with_coercion
        88   (7.7%)          44   (3.9%)     ActiveSupport::Inflector#camelize
        41   (3.6%)          41   (3.6%)     ActiveRecord::ConnectionAdapters::Mysql2Adapter#active?
        30   (2.6%)          30   (2.6%)     block in BetterErrors::ExceptionExtension#set_backtrace
        28   (2.5%)          28   (2.5%)     block in ActiveSupport::Dependencies#loadable_constants_for_path
        29   (2.5%)          25   (2.2%)     ActiveSupport::Inflector#inflections
        41   (3.6%)          25   (2.2%)     block (2 levels) in BindingOfCaller::BindingExtensions#callers
        22   (1.9%)          22   (1.9%)     ActiveRecord::MigrationProxy#mtime
        22   (1.9%)          22   (1.9%)     block in ActiveSupport::FileUpdateChecker#watched
        22   (1.9%)          22   (1.9%)     ActiveRecord::MigrationProxy#initialize
        16   (1.4%)          16   (1.4%)     Statsd#send_to_socket
        18   (1.6%)          15   (1.3%)     block in ActiveSupport::Inflector#camelize
        12   (1.1%)          12   (1.1%)     block in ActionDispatch::FileHandler#match?
        12   (1.1%)          11   (1.0%)     Hashie::Mash#custom_writer
       128  (11.2%)          10   (0.9%)     block in ActiveSupport::Dependencies#load_file
         9   (0.8%)           9   (0.8%)     block in ActiveSupport::Dependencies#search_for_file
        27   (2.4%)           7   (0.6%)     Hashie::Mash#initialize
         7   (0.6%)           7   (0.6%)     Rack::MiniProfiler::TimerStruct::Base#initialize
         7   (0.6%)           7   (0.6%)     ActionDispatch::Journey::Visitors::Each#initialize
         6   (0.5%)           6   (0.5%)     ThreadSafe::NonConcurrentCacheBackend#[]
         7   (0.6%)           6   (0.5%)     ActiveRecord::ConnectionAdapters::DatabaseStatements#reset_transaction
         7   (0.6%)           5   (0.4%)     block in Module#delegate
         5   (0.4%)           5   (0.4%)     block (2 levels) in ActiveSupport::Dependencies::WatchStack#new_constants
         4   (0.4%)           4   (0.4%)     block in ActionDispatch::Journey::GTG::Builder#build_followpos
         4   (0.4%)           4   (0.4%)     block (2 levels) in <class:Numeric>
         6   (0.5%)           4   (0.4%)     ActionView::Context#_prepare_context

without:
     TOTAL    (pct)     SAMPLES    (pct)     FRAME
       128  (11.3%)         128  (11.3%)     block in ActiveSupport::FileUpdateChecker#max_mtime
       124  (11.0%)         124  (11.0%)     block in Logger::LogDevice#write
       113  (10.0%)         100   (8.9%)     ActiveSupport::FileUpdateChecker#watched
       192  (17.0%)          78   (6.9%)     block in ActiveRecord::Migrator.migrations
        62   (5.5%)          62   (5.5%)     Time#compare_with_coercion
        91   (8.1%)          51   (4.5%)     ActiveSupport::Inflector#camelize
        43   (3.8%)          43   (3.8%)     ActiveRecord::ConnectionAdapters::Mysql2Adapter#active?
        41   (3.6%)          41   (3.6%)     ActiveRecord::MigrationProxy#mtime
        40   (3.5%)          24   (2.1%)     block (2 levels) in BindingOfCaller::BindingExtensions#callers
        24   (2.1%)          24   (2.1%)     block in BetterErrors::ExceptionExtension#set_backtrace
        23   (2.0%)          23   (2.0%)     ActiveRecord::MigrationProxy#initialize
        19   (1.7%)          19   (1.7%)     Statsd#send_to_socket
        19   (1.7%)          16   (1.4%)     block in ActiveSupport::Inflector#camelize
        16   (1.4%)          16   (1.4%)     block in ActionDispatch::FileHandler#match?
        16   (1.4%)          16   (1.4%)     block in ActiveSupport::Dependencies#loadable_constants_for_path
        22   (1.9%)          15   (1.3%)     ActiveSupport::Inflector#inflections
        13   (1.2%)          13   (1.2%)     block in ActiveSupport::FileUpdateChecker#watched
         8   (0.7%)           8   (0.7%)     Rack::MiniProfiler::TimerStruct::Base#initialize
         8   (0.7%)           8   (0.7%)     ThreadSafe::NonConcurrentCacheBackend#[]
         7   (0.6%)           7   (0.6%)     block in ActiveSupport::Dependencies#search_for_file
        97   (8.6%)           6   (0.5%)     block in ActiveSupport::Dependencies#load_file
         5   (0.4%)           5   (0.4%)     Rack::Utils::HeaderHash#[]=
         6   (0.5%)           4   (0.4%)     block in Module#delegate
         6   (0.5%)           4   (0.4%)     ActiveRecord::ConnectionAdapters::Quoting#_quote
         4   (0.4%)           4   (0.4%)     Rack::BodyProxy#initialize
         5   (0.4%)           4   (0.4%)     Rack::Utils#parse_nested_query
         9   (0.8%)           3   (0.3%)     Hashie::Mash#initialize
         5   (0.4%)           3   (0.3%)     Rack::MockRequest.env_for
         3   (0.3%)           3   (0.3%)     Hashie::Mash#custom_writer
        25   (2.2%)           3   (0.3%)     ActionView::Renderer#render_template

also the gem advertises to improve boottime ... and derailed has very little to do with boot time ...

It advertises load time, not boot time.  Here's the difference it makes for me.
before
Booting: development
Endpoint: "/"
       user     system      total        real
100 requests 30.530000   1.780000  32.310000 ( 32.509564)
Running `stackprof tmp/2016-06-13T07:02:21-04:00-stackprof-cpu-myapp.dump`. Execute `stackprof --help` for more info
==================================
  Mode: cpu(1000)
  Samples: 8114 (0.01% miss rate)
  GC: 978 (12.05%)
==================================
     TOTAL    (pct)     SAMPLES    (pct)     FRAME
      2334  (28.8%)        2334  (28.8%)     Pathname#chop_basename
      1218  (15.0%)        1036  (12.8%)     Hike::Index#entries
      1308  (16.1%)         432   (5.3%)     BetterErrors::ExceptionExtension#set_backtrace
       419   (5.2%)         416   (5.1%)     Sprockets::Mime#mime_types
      1749  (21.6%)         345   (4.3%)     Pathname#plus
      1338  (16.5%)         277   (3.4%)     BindingOfCaller::BindingExtensions#callers
       462   (5.7%)         238   (2.9%)     Hike::Index#find_aliases_for
       466   (5.7%)         234   (2.9%)     Hike::Index#sort_matches
      1976  (24.4%)         227   (2.8%)     Pathname#+
      1992  (24.6%)         133   (1.6%)     Hike::Index#match
       264   (3.3%)         132   (1.6%)     ActionView::PathResolver#find_template_paths
       236   (2.9%)         126   (1.6%)     Hike::Index#pattern_for
       121   (1.5%)         104   (1.3%)     Hike::Index#build_pattern_for
        90   (1.1%)          90   (1.1%)     Hike::Trail#stat
      2980  (36.7%)          67   (0.8%)     Pathname#join
        64   (0.8%)          59   (0.7%)     ActiveSupport::FileUpdateChecker#watched
        58   (0.7%)          58   (0.7%)     Time#compare_with_coercion
       106   (1.3%)          57   (0.7%)     Hike::Index#initialize
      6234  (76.8%)          57   (0.7%)     Sprockets::Rails::Helper#check_errors_for
       943  (11.6%)          38   (0.5%)     Pathname#relative?
        48   (0.6%)          29   (0.4%)     Sprockets::Engines#deep_copy_hash
        28   (0.3%)          28   (0.3%)     ActiveSupport::SafeBuffer#initialize
       136   (1.7%)          25   (0.3%)     ActiveSupport::FileUpdateChecker#max_mtime
        25   (0.3%)          25   (0.3%)     ActionView::Helpers::AssetUrlHelper#compute_asset_extname
        44   (0.5%)          24   (0.3%)     ActiveSupport::Inflector#camelize
       111   (1.4%)          20   (0.2%)     Sprockets::Asset#dependency_fresh?
       124   (1.5%)          20   (0.2%)     ActionView::Helpers::AssetUrlHelper#asset_path
        19   (0.2%)          19   (0.2%)     String#blank?
        16   (0.2%)          16   (0.2%)     Sprockets::Base#cache_key_for
     10487 (129.2%)          15   (0.2%)     Sprockets::Base#resolve

after
Booting: development
Endpoint: "/"
       user     system      total        real
100 requests 10.990000   0.590000  11.580000 ( 11.687753)
Running `stackprof tmp/2016-06-13T18:10:34-04:00-stackprof-cpu-myapp.dump`. Execute `stackprof --help` for more info
==================================
  Mode: cpu(1000)
  Samples: 2910 (0.00% miss rate)
  GC: 329 (11.31%)
==================================
     TOTAL    (pct)     SAMPLES    (pct)     FRAME
       500  (17.2%)         500  (17.2%)     #<Module:0x0000000452a450>.chop_basename
       850  (29.2%)         206   (7.1%)     Hike::Index#match
       630  (21.6%)         199   (6.8%)     BetterErrors::ExceptionExtension#set_backtrace
       680  (23.4%)         179   (6.2%)     Pathname#plus
       698  (24.0%)         154   (5.3%)     BindingOfCaller::BindingExtensions#callers
       155   (5.3%)         146   (5.0%)     Hike::Index#entries
       242   (8.3%)         121   (4.2%)     ActionView::PathResolver#find_template_paths
       795  (27.3%)         115   (4.0%)     Pathname#+
       198   (6.8%)         101   (3.5%)     Hike::Index#find_aliases_for
       189   (6.5%)          94   (3.2%)     Hike::Index#sort_matches
        93   (3.2%)          92   (3.2%)     Sprockets::Mime#mime_types
       107   (3.7%)          53   (1.8%)     Hike::Index#pattern_for
        58   (2.0%)          52   (1.8%)     ActiveSupport::FileUpdateChecker#watched
        49   (1.7%)          49   (1.7%)     Time#compare_with_coercion
        59   (2.0%)          48   (1.6%)     Hike::Index#build_pattern_for
        46   (1.6%)          46   (1.6%)     #<Module:0x0000000452a450>.absolute?
       880  (30.2%)          39   (1.3%)     Pathname#join
       140   (4.8%)          32   (1.1%)     ActiveSupport::FileUpdateChecker#max_mtime
        31   (1.1%)          16   (0.5%)     Hike::Index#initialize
        27   (0.9%)          16   (0.5%)     ActiveSupport::Inflector#camelize
      3061 (105.2%)          13   (0.4%)     Hike::Index#find
        68   (2.3%)          11   (0.4%)     ActiveRecord::Migrator.migrations
        27   (0.9%)           9   (0.3%)     ActiveSupport::Dependencies::Loadable#require
         8   (0.3%)           8   (0.3%)     ThreadSafe::NonConcurrentCacheBackend#[]
         8   (0.3%)           8   (0.3%)     Hashie::Mash#convert_key
         8   (0.3%)           8   (0.3%)     Rack::MiniProfiler.config
        40   (1.4%)           8   (0.3%)     Rack::MiniProfiler::TimerStruct::Sql#initialize
      3026 (104.0%)           7   (0.2%)     Hike::Index#find_in_paths
         7   (0.2%)           7   (0.2%)     String#blank?
        28   (1.0%)           5   (0.2%)     Sprockets::AssetAttributes#search_paths
danielpclark@allyourdev:~/dev/fast/tagfer-daniel$ less config/initializers/faster_path.rb

As you can see I addressed the method my application hit the most and the site improved load time by 66%.
I'm using Sprockets version 2.12.4 which has more Pathname usage and uses the Hike gem as well which also uses Pathname.

Do you know why you're having a Samples: 1139 (61.82% miss rate)?  I'm not having misses in my derailed checks.

Not sure, maybe because the action was too fast ... I gutted a bunch of things to make it not require a logged in user ... results with full page / logged in user:
100 requests 38.750000   6.400000  45.150000 ( 62.857037)
Running `stackprof tmp/2016-06-14T01:58:08+00:00-stackprof-cpu-myapp.dump`. Execute `stackprof --help` for more info
==================================
  Mode: cpu(1000)
  Samples: 31096 (8.82% miss rate)
  GC: 2245 (7.22%)
==================================
     TOTAL    (pct)     SAMPLES    (pct)     FRAME
     10202  (32.8%)       10202  (32.8%)     Sprockets::PathUtils#stat
      2293   (7.4%)        2293   (7.4%)     block in Mysql2::Client#query
      2774   (8.9%)        1737   (5.6%)     ActionView::PathResolver#find_template_paths
      6122  (19.7%)        1395   (4.5%)     ActiveRecord::ConnectionAdapters::Mysql2Adapter#exec_query
      1303   (4.2%)        1303   (4.2%)     Rack::MiniProfiler.config
      1149   (3.7%)        1149   (3.7%)     block in Logger::LogDevice#write
      1037   (3.3%)        1037   (3.3%)     block in ActionView::PathResolver#find_template_paths
       646   (2.1%)         646   (2.1%)     block (2 levels) in Rack::MiniProfiler::TimerStruct::Sql#initialize
       978   (3.1%)         601   (1.9%)     Sprockets::URITar#initialize
       983   (3.2%)         541   (1.7%)     Sprockets::Cache::FileStore#safe_open
       545   (1.8%)         421   (1.4%)     Sprockets::URITar#expand
       377   (1.2%)         377   (1.2%)     Sprockets::Paths#root
      1042   (3.4%)         306   (1.0%)     block in #<Module:0x007f9c4d9b0f28>.render_javascripts
       288   (0.9%)         288   (0.9%)     URI::RFC3986_Parser#split
       278   (0.9%)         273   (0.9%)     Sprockets::PathUtils#entries
       216   (0.7%)         216   (0.7%)     #<Module:0x007f9c4c0cbad0>.load_with_autoloading
       532   (1.7%)         181   (0.6%)     block in #<Module:0x007f9c4d9b0f28>.render_stylesheets
       390   (1.3%)         174   (0.6%)     Sprockets::EncodingUtils#unmarshaled_deflated
       163   (0.5%)         163   (0.5%)     rescue in Dalli::Server::KSocket::InstanceMethods#readfull
       153   (0.5%)         153   (0.5%)     block (4 levels) in Sprockets::Mime#compute_extname_map
       172   (0.6%)         146   (0.5%)     block in ActionView::PathResolver#query
       128   (0.4%)         128   (0.4%)     block in ActiveSupport::FileUpdateChecker#max_mtime
       119   (0.4%)         119   (0.4%)     Sprockets::PathUtils#absolute_path?
       112   (0.4%)         112   (0.4%)     ActiveSupport::PerThreadRegistry#instance
       111   (0.4%)         110   (0.4%)     Set#add
       110   (0.4%)         110   (0.4%)     block in BetterErrors::ExceptionExtension#set_backtrace
       101   (0.3%)         101   (0.3%)     Set#replace
       134   (0.4%)         100   (0.3%)     ActiveSupport::FileUpdateChecker#watched
        78   (0.3%)          78   (0.3%)     ThreadSafe::NonConcurrentCacheBackend#[]
        78   (0.3%)          75   (0.2%)     Sprockets::DigestUtils#digest

and with config.assets.compile = false
      2472  (12.2%)        2472  (12.2%)     Rack::MiniProfiler.config
      2167  (10.7%)        2167  (10.7%)     block in Mysql2::Client#query
      3118  (15.4%)        1967   (9.7%)     ActionView::PathResolver#find_template_paths
      1300   (6.4%)        1300   (6.4%)     block in Logger::LogDevice#write
      7696  (37.9%)        1228   (6.0%)     ActiveRecord::ConnectionAdapters::Mysql2Adapter#exec_query
      1151   (5.7%)        1151   (5.7%)     block in ActionView::PathResolver#find_template_paths
      1048   (5.2%)        1048   (5.2%)     block (2 levels) in Rack::MiniProfiler::TimerStruct::Sql#initialize
       286   (1.4%)         248   (1.2%)     block in ActionView::PathResolver#query
       192   (0.9%)         191   (0.9%)     ActiveSupport::PerThreadRegistry#instance
       222   (1.1%)         191   (0.9%)     block in #<Module:0x007f9e659ca4e0>.render_javascripts
       216   (1.1%)         177   (0.9%)     block in #<Module:0x007f9e659ca4e0>.render_stylesheets
       168   (0.8%)         168   (0.8%)     block in ActiveSupport::FileUpdateChecker#max_mtime
       142   (0.7%)         142   (0.7%)     ThreadSafe::NonConcurrentCacheBackend#[]
       136   (0.7%)         136   (0.7%)     block in BetterErrors::ExceptionExtension#set_backtrace
       133   (0.7%)         133   (0.7%)     rescue in Dalli::Server::KSocket::InstanceMethods#readfull
       166   (0.8%)         126   (0.6%)     Arel::Nodes::Binary#hash
       111   (0.5%)         111   (0.5%)     block (4 levels) in Class#class_attribute
       225   (1.1%)         105   (0.5%)     block in ActiveRecord::Migrator.migrations
       155   (0.8%)         103   (0.5%)     ActiveRecord::Relation#initialize_copy
       101   (0.5%)         101   (0.5%)     Time#compare_with_coercion
       128   (0.6%)         101   (0.5%)     ActiveSupport::FileUpdateChecker#watched
       163   (0.8%)          91   (0.4%)     block (2 levels) in BindingOfCaller::BindingExtensions#callers
        79   (0.4%)          79   (0.4%)     block in ActiveSupport::Dependencies#loadable_constants_for_path
        76   (0.4%)          74   (0.4%)     block in ActiveRecord::QueryMethods#validate_order_args
        74   (0.4%)          74   (0.4%)     block in ActiveSupport::Inflector#apply_inflections
       223   (1.1%)          72   (0.4%)     ActiveModel::AttributeMethods::ClassMethods#attribute_alias?
        68   (0.3%)          68   (0.3%)     ActiveRecord::Inheritance::ClassMethods#base_class
        65   (0.3%)          65   (0.3%)     block (2 levels) in <class:Numeric>
        61   (0.3%)          61   (0.3%)     Arel::Collectors::Bind#<<
       186   (0.9%)          58   (0.3%)     ActiveRecord::QueryMethods#preprocess_order_args

I see you're using the Sprockets ~> 3.0 series.  When I tried upgrading to that it slowed my site down by roughly 20% . see: https://github.com/rails/sprockets/issues/84#issuecomment-223742047
I'm not sure how much Sprockets depends on the STDLIB Pathname class anymore.  I'll look into it.

Yep.  As of Sprockets 3.0 series they've dropped most of their use of Pathname.  See: https://github.com/rails/sprockets/blob/master/lib/sprockets/path_utils.rb
They only require Pathname is an ALT separator is used and then only use the Pathname#absolute? method.
I don't think you'll see any performance gain unless you downgrade your Sprockets version, or until we add more methods that the newer Sprockets depends on.

Hey @grosser , I did more research into Sprockets.  I've written all the details in the README.  After my research I believe your website can gain around 31% faster page load time by downgrading to Sprocket 2.0 series.  And then you may get an additional 30% by using this gem.  This result will be more clearly seen on your logged in user derailed profile results.  I'm basing these numbers off of my own website though so the data for you will likely vary.

authors: danielpclark grosser


text:
🛑 test1 is down

In 48ee0f7, test1 (https://quarterbacksystems.com/en_US/page/status) was down:

HTTP code: 503
Response time: 639 ms

Resolved: test1 is back up in 9499799 after 12 minutes.

repo: danielqb/status


text:
🛑 Bancolombia - Portal is down

In 3278336, Bancolombia - Portal (https://www.bancolombia.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Bancolombia - Portal is back up in 357088b.


text:
🛑 DIAN - Muisca is down

In 8fbc958, DIAN - Muisca (https://muisca.dian.gov.co/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: DIAN - Muisca is back up in 99afe8b.


text:
🛑 test1 is down

In 5fb442a, test1 (https://quarterbacksystems.com/en_US/page/status) was down:

HTTP code: 502
Response time: 1300 ms

Resolved: test1 is back up in 64c419c after 325 days, 18 hours, 27 minutes.


text:
🛑 test1 is down

In cfdc7ce, test1 (https://quarterbacksystems.com/en_US/page/status) was down:

HTTP code: 503
Response time: 1316 ms

Resolved: test1 is back up in 39e1627 after 11 minutes.


text:
Disable keyboard input callout on iPad devices

The native keyboard input callout bubble is not active on iPad devices. Instead, the buttons are highlighted when pressed.
Disable the callout bubble by default on iPad and add a color highlight instead.

This can be tested in master.

This can be tested in master.

repo: danielsaidi/KeyboardKit


text:
List of Commonalities

I came across this effort while reading https://peerj.com/articles/cs-86/, and my first thought after going over the list - where to start? So many differences, that I am asking myself how could it be possible for someone to be in any doubt about the differences between software and data?
For someone coming this this perspective, and to make the document more balanced and motivated, did you consider adding "List of Commonalities"?

Hi - this really started when a draft of that paper discussed differences between software and data from the point-of-view of citation, and we want to explain when the data citation principles were not sufficient and correct for software citation. Some reviewers felt we were injecting out opinions, rather than facts, so we decided to create this repo and let people discuss this, so it was more of a consensus and not just out opinions.  We then could cite this repo in the paper, and satisfy the reviewers, which we did.
Having said that, if you want to propose some changes, that would be fine.

Oh, I see. If this repo is not being actively developed and has already served its purpose, then I agree there is not much value in updating it. Thanks for the clarification!

authors: danielskatz fedorov

repo: danielskatz/software-vs-data


text:
Make COLUMN str subclass and get rid of .value calls

Is your feature request related to a problem? Please describe.
We could simplify the SQL queries and column name reference by subclassing COLUMN with str as well.
Describe the solution you'd like

rewrite the COLUMN class to subclass str and test that it behaves as expected
rewrite the SQL queries and everywhere else where .value had to be used for the Enum

Describe alternatives you've considered
Use StrEnum but then we need Python >= 3.11.

Upgraded to Python 3.11 so we can use StrEnum, similar to how COMPONENT_ID is implemented.

repo: danieltsoukup/noise-dashboard


text:
Add greetz to index and extra main page.

Because Click to Enter!

lolwhat


text:
Updated setup.py and added pyproject.toml

Updated the deprecated setup.py install and created the more standard pyproject.toml. It creates a wheel which is installable and works on Python >=3.6.
I have attached a ZIP file with the generated wheel and tar.gz from python -m build
Let me know if there is a problem,
dist.zip

@danni it would be very handy if you could spare some time for this PR.

authors: gregbreen joseavegaa


text:
[Question]: failed to solve: process "/bin/sh -c apk --no-cache add curl &&     npm ci" did not complete successfully: exit code: 146

What is your question?
My system information is as follows:
LSB Version:    :core-4.1-amd64:core-4.1-noarch
Distributor ID: CentOS
Description:    CentOS Linux release 7.9.2009 (Core)
Release:        7.9.2009
Codename:       Core
I get an error when executing the following command:
docker-compose up
error message:

failed to solve: process "/bin/sh -c apk --no-cache add curl &&     npm ci" did not complete successfully: exit code: 146
More Details
。
What is the main subject of your question?
No response
Screenshots
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

you could try using the pre-built image instead
You can edit the docker-compose.override.yml file (rename it without the .example)
you need something like this:
version: '3.4'

services:
  api:
    image: ghcr.io/danny-avila/librechat-dev:latest

see also for more information:
https://docs.librechat.ai/install/configuration/docker_override.html

Did as asked. But can't succeed yet. . .

ok.yeah!

authors: fuegovic longjiansina

repo: danny-avila/LibreChat


text:
[Question]: How to decrease token after successfully generate DALL-E image?

What is your question?
How to decrease token after successfully generate DALL-E image?
More Details
I know the cost for every dall-e image generation is about 3 cent per successfully generation. I want to manually decrease token like 150,000 token for every successfull image generation.
Because currently the token will decrease only for prompt and completion. I'm thinking of that if I have to manually add some function to decrease the token after each successfully generation.
Thank you.
What is the main subject of your question?
No response
Screenshots
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Not implemented, will be soon: https://github.com/danny-avila/LibreChat/discussions/1479

authors: danny-avila nayakayp


text:
feat: Qdrant Vector Database

Qdrant vector database supported. Added section in readme in setting up Qdrant environmental variables as well as specifically running docker image. Implemented Async methods for qdrant.
Tested using bedrock with amazon.titan-embed-text-v2:0 with all 3 supported currently vector databases (pgvector, qdrant, and atlas mongo)
Tested /ids, /documents , /delete ,/embed , /query and /query_multiple endpoints successfully with qdrant, pgvector, and atlas mongo.

Looked into implementing qdrant async client
Would we still want to retain support for sync qdrant? Would restructure code that we have, but have two separate vector-DB.

Hoping we can get some more traction on this given the benfits of Qdrant over pgvector over other solutions.

authors: FinnConnor PylotLight ScarFX


text:
nil user_id causes app failure

I have a test to ensure that a nil email in an update will result in a changeset error.  I'm using pow_user_id_field_changeset(attrs), which results in:
** (FunctionClauseError) no function clause matching in String.Break.trim_leading/1

     The following arguments were given to String.Break.trim_leading/1:

         # 1
         nil

     Attempted function clauses (showing 1 out of 1):

         def trim_leading(string) when is_binary(string)
...

stacktrace:
       (elixir) lib/elixir/unicode/properties.ex:288: String.Break.trim_leading/1
       (elixir) lib/string.ex:1108: String.trim/1
       (pow) lib/pow/ecto/schema.ex:307: Pow.Ecto.Schema.normalize_user_id_field_value/1
       (ecto) lib/ecto/changeset.ex:1133: Ecto.Changeset.update_change/3
       (pow) lib/pow/ecto/schema/changeset.ex:48: Pow.Ecto.Schema.Changeset.user_id_field_changeset/3

Is there a way to use the pow_user_id_field_changeset and receive changeset errors vs. this application error?

My test:
  @invalid_attrs %{email: nil, password: "password"}
...
    test "create_user/1 with invalid data returns error changeset" do
      assert {:error, %Ecto.Changeset{}} = Accounts.create_user(@invalid_attrs)
    end

My Context:
  def create_user(attrs) do
    %User{}
    |> User.changeset(attrs)
    |> Repo.insert()
  end

My User:
  def changeset(user_or_changeset, attrs) do
    user_or_changeset
    |> pow_user_id_field_changeset(attrs)
    |> pow_current_password_changeset(attrs)
    |> new_password_changeset(attrs, @pow_config)
    |> pow_extension_changeset(attrs)
    |> Ecto.Changeset.delete_change(:password)
  end

Sorry, a bunch of things and the holidays crept up so didn't have time to look at this before now.
I figure out a way to trigger this. The user has to already have the email set in the struct:
User.pow_user_id_field_changeset(%User{email: "test"}, %{email: nil})

I don't know why it blows up in your case though, since you call the changeset with an empty struct. Maybe a default value is set for the struct key? In any case, I'll open a PR to fix this.

#364 hopefully resolves this for you 😄

Perfect, thank you!

authors: danschultzer dfalling

repo: danschultzer/pow


text:
Fix issue #1

Fix Issue #1
DRY up codebase by removing duplicate TypeError code from each operation and bring into the _check function. Invoke the _check() function before each operation.

Yay, a pull request!
After you submit a pull request, one of the following will happen:
:sob: You don’t get a response. :sob:
Even on an active project, it’s possible that your pull request won’t get an immediate response. You should expect some delay as most open source maintainers do so in their free time and can be busy with other tasks.
If you haven’t gotten a response in over a week, it’s fair to politely respond in the same thread, asking someone for a review. If you know the handle of the right person to review your pull request, you can @-mention them to send them a notification. Avoid reaching out to that person privately; remember that public communication is vital to open source projects.
If you make a polite bump and still nobody responds, it’s possible that nobody will respond, ever. It’s not a great feeling, but don’t let that discourage you. It’s happened to everyone! There are many possible reasons why you didn’t get a response, including personal circumstances that may be out of your control. Try to find another project or way to contribute. If anything, this is a good reason not to invest too much time in making a pull request before other community members are engaged and responsive.
:construction: You're asked to make changes to your pull request. :construction:
It’s very common that someone will request changes on your pull request, whether that’s feedback on the scope of your idea, or changes to your code. Often a pull request is just the start of the conversation.
When someone requests changes, be responsive. They’ve taken the time to review your pull request. Opening a PR and walking away is bad form. If you don’t know how to make changes, research the problem, then ask for help if you need it.
If you don’t have time to work on the issue anymore (for example, if the conversation has been going on for months, and your circumstances have changed), let the maintainer know so they’re not expecting a response. Someone else may be happy to take over.
:-1: Your pull request doesn’t get accepted.  :-1:
It's possible your pull request may or may not be accepted in the end. If you’re not sure why it wasn’t accepted, it’s perfectly reasonable to ask the maintainer for feedback and clarification. Ultimately, however, you’ll need to respect that this is their decision. Don’t argue or get hostile. You’re always welcome to fork and work on your own version if you disagree!
:tada: Your pull request gets accepted and merged. :tada:
Hooray! You’ve successfully made an open source contribution!

Thank you for the submission, @sambragg! I'll review your code shortly, hang tight.

:tada: You did it! :tada:
You're an open source contributor now!
Whether this was your first pull request, or you’re just looking for new ways to contribute, I hope you’re inspired to take action. Don't forget to say thanks when a maintainer puts effort into helping you, even if a contribution doesn't get accepted.
Remember, open source is made by people like you: one issue, pull request, comment, and +1 at a time.
What's next?
Find your next project:

Up For Grabs - a list of projects with beginner-friendly issues
First Timers Only - a list of bugs that are labelled "first-timers-only"
Awesome-for-beginners - a GitHub repo that amasses projects with good bugs for new contributors, and applies labels to describe them.
YourFirstPR - starter issues on GitHub that can be easily tackled by new contributors.
Issuehub.io - a tool for searching GitHub issues by label and language

Learn from other great community members:

"How to contribute to an open source project on github" by @kentcdodds
"Bring Kindness Back to Open Source" by @shanselman
"Getting into Open Source for the First Time" by @mcdonnelldean
"How to find your first open source bug to fix" by @Shubheksha
"How to Contribute to Open Source" by @Github
"Make your first open source contribution in 5 minutes" by @Roshanjossey

Elevate your Git game:

Try git - an interactive Git tutorial made by GitHub
Atlassian Git Tutorials - various tutorials on using Git
Git Cheat Sheet - PDF made by GitHub
GitHub Flow - YouTube video explaining how to make a pull request on GitHub talk on how to make a pull request
Oh shit, git! - how to get out of common Git mistakes described in plain English

Questions? Comments? Concerns?
I'm always open to feedback. If you had a good time with the exercise, or found some room for improvement, please let me know on twitter or email.
Want to start over? Just delete your fork.
Want to see behind the scenes? Check out the server code.

authors: danthareja sambragg

repo: danthareja/contribute-to-open-source


text:
#36

Adicionado indexDB

Gravando registros no banco de dados

@danvitoriano

repo: danvitoriano/minhas-financas


text:
@peerbit/react -- Error occurred during XX handshake: ciphertext cannot be decrypted using that key

I have a Next.js app in which I'm trying to use PeerProvider from @peerbit/react, like so: https://github.com/Azaeres/etherion-lab/blob/main/src/components/scenes/Experiment4/index.tsx
'use client'
import { PeerProvider } from '@peerbit/react'

export default function Experiment4() {
  console.log('Experiment4 render  :')
  return (
    <PeerProvider network="remote">
      <></>
    </PeerProvider>
  )
}

However, I'm getting the error "Failed to resolve relay addresses. Error: Error occurred during XX handshake: ciphertext cannot be decrypted using that key".
Live demo of error can be found here: https://lab.etherion.app/experiment4
When I try to provide my own keypair, Peerbit sees it as invalid. It looks like there are a few different defined Ed25519Keypair classes in the Next.js bundle, and Peerbit's instanceof check fails when there's a class reference mismatch. I've also tried creating a keypair using @peerbit/react's getKeypair() function, but Peerbit also sees it as invalid. Not sure if this is related to the "XX handshake" error.
In another, separate area, I've successfully created my own peer by borrowing bits of @peerbit/react. You can see this in a live demo at: https://lab.etherion.app/experiment3
The peer creation code I got to work can be found here: https://github.com/Azaeres/etherion-lab/blob/main/src/components/scenes/Experiment3/hooks/usePeerbitDatabase.ts

Interestingly

https://lab.etherion.app/experiment4

Worked once  for me. Then next time I tried it I got the problem. I wonder if there is some caching going on..
Anyway.
https://github.com/Azaeres/etherion-lab/blob/c7d9864e42c86c26c7a8bbb3c1d824d600dd8662/yarn.lock#L7998C12-L7998C12
Looks like you have a old version of Peerbit lurking around. Can you see if you can bump all Peerbit related dependencies.
Most importantly
https://github.com/Azaeres/etherion-lab/blob/c7d9864e42c86c26c7a8bbb3c1d824d600dd8662/yarn.lock#L1577
this one should not exist in the lock file but only the 13^ one

Super cool that your are creating multiplayer (?) a space shooter game with Peerbit. Could feature it on this repo if you want later

Okay, thank you for the tip on what to dig into!
@peerbit/react@0.0.4 off of NPM is asking for @libp2p/webrtc@^2.0.11, which is in turn asking for @chainsafe/libp2p-noise@^12.0.0.
However, I see that react-utils in the peerbit-examples is asking for @libp2p/webrtc@^3.1.9. See https://github.com/dao-xyz/peerbit-examples/blob/fe1729f1268c5b29fb61b59611e460d553ed3180/packages/react-utils/package.json#L28
If you're publishing this react-utils folder to NPM, maybe it's time to publish an update?

Super cool that your are creating multiplayer (?) a space shooter game with Peerbit. Could feature it/link it from this repo if you want later

Yeah, that's the idea! Would love for this to come together. Thanks again for your help.

Well it is more the
@dao-xyz/libp2p-noise@^12.0.0
noise implementation, that had a bug which yields your error message.
If you somehow manage to get rid of peerbit v1 dependency https://github.com/Azaeres/etherion-lab/blob/c7d9864e42c86c26c7a8bbb3c1d824d600dd8662/yarn.lock#L7998C12-L7998C12
and only use peerbit v2 I think your problems will be gone.
I have not actually used @peerbit/react in a separate repo yet. Been building it along side all the examples to reach a good API in the end, and I kan see that there are a few dependencies there that perhaps needs to be removed or updated (however it should not affect your problem)

These are the listed dependencies of the @peerbit/react I grabbed off of NPM.
    "dependencies": {
        "@emotion/react": "^11.10.5",
        "@emotion/styled": "^11.10.5",
        "@libp2p/webrtc": "^2.0.11",
        "@mui/icons-material": "^5.10.16",
        "@mui/material": "^5.10.13",
        "@peerbit/proxy-window": "^1.0.1",
        "@types/react": "^18.0.25",
        "@types/react-dom": "^18.0.8",
        "path-browserify": "^1.0.1",
        "peerbit": "^1",
        "react": "^18.2.0",
        "react-dom": "^18.2.0",
        "react-router-dom": "^6.8.0",
        "react-use": "^17.4.0"
    },

I think that's where the peerbit@^1 is coming from, which explains why the @dao-xyz/libp2p-noise@^12.0.0 disappears when I uninstall @peerbit/react.

Ah! I see, this CI in github does not automatically release stuff in this repo.
Just relased
@peerbit/react@0.0.5
now. Try it out !

Nice! No longer getting the XX handshake error!
I've got a bunch of these "'Recieved hello message that did not verify. Header: false, Ping info true, Signatures false'" warnings, though. Does this mean I haven't configured something correctly?

Great! No you don't have to worry about that error.
There is non-optimal logging now.
The warning and error messages should be gone when this issue is fixed.
The 87ecf9778ccaa08bd9f1e8c6104d82c469b35511.peerchecker.com  address is not part of the bootstrapping nodes. And that server is down. But this should not affect your stuff running. The error messages you see are basically just the autodialer failing to establish connections

authors: Azaeres marcus-pousette

repo: dao-xyz/peerbit-examples


text:
Initializing cyber node without using environment variable

Hi, thank you for the amazing tools!
I want to ask you if it is possible to use CYBER_IP as a parameter when initializing (e.g. cyber.init(cyber_ip='111.222.333.444')), rather than using an environment variable.
export CYBER_IP=127.0.0.1

As pycyber is a wrap of apollo cyber, cyber does not currently support this assignment method. Therefore I do not intend to support the above interfaces unless necessary!

Cool! Thanks for answering!


text:
Update GCP Storage Bucket

Describe the feature
Update GCP Storage Bucket binding:

update create operation: support upload files in base64 (https://docs.dapr.io/reference/components-reference/supported-bindings/gcpbucket/#upload-a-file doesn't work)
add get operation
add delete operation
add list operation

Release Note

RELEASE NOTE:

UPDATE GCP Storage Bucket binding. Create operation: support upload files in base64, return location and version id
ADD  GCP Storage Bucket binding: get operation
ADD  GCP Storage Bucket binding: delete operation
ADD  GCP Storage Bucket binding: list operation

/assing

/assign

repo: dapr/components-contrib


text:
azappconfig SDk upgrade

Description
Please explain the changes you've made
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #3267
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[ ] Code compiles correctly
[ ] Created/updated tests
[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

/ok-to-test

authors: ItalyPaleAle pravinpushkar


text:
Kubernetes (AKS) - Azure Key Vault Secret Store: failed to get oauth token from certificate auth: failed to read the certificate file

Hey Community,
I have problems using my certificate in Kubernetes (AKS) for my Azure Key Vault Secret Store.
It works wonderfully with local hosting. I made the configuration according to the instructions and also added the certificate file to the Kubernetes Store. But unfortunately I get the following error message with Kubernetes when starting the dapr sidecar:
time="2021-07-14T14:31:57.756966579Z" level=warning msg="failed to init state store secretstores.azure.keyvault/v1 named azurekeyvault: failed to get oauth token from certificate auth: failed to read the certificate file (0\x82\nP\x0...a\xd0: invalid argument" app_id=mywebapp instance=mywebapp-5557c78c9b-v86ss scope=dapr.runtime type=log ver=1.2.2
time="2021-07-14T14:31:57.757159681Z" level=fatal msg="process component azurekeyvault error: failed to get oauth token from certificate auth: failed to read the certificate file (0\x82\nP\x02\x\xde: invalid argument" app_id=mywebapp instance=mywebapp-5557c78c9b-v86ss scope=dapr.runtime type=log ver=1.2
i have done all the steps according to this documentation:
https://docs.dapr.io/reference/components-reference/supported-secret-stores/azure-keyvault/
My Kubectl command:
kubectl create secret generic k8s-secret-store --from-file=myapp-certificate=myapp-secrets-myapp-certificate-20210713.pfx
My azurekeyvault.yaml
apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
  name: azurekeyvault
  namespace: default
spec:
  type: secretstores.azure.keyvault
  version: v1
  metadata:
    - name: vaultName
      value: myapp-secrets
    - name: spnTenantId
      value: "460d88b8-d055-4149-9f03-XXX" #changed to XXX only on this post
    - name: spnClientId
      value: "dd964473-808e-4a82-a167-XXX" #changed to XXX only on this post
    - name: spnCertificateFile
      secretKeyRef:
        name: k8s-secret-store
        key: myapp-certificate
auth:
    secretStore: kubernetes

It was my fault. I used spnCertificateFile and that is for local.
I changed it to spnCertificate and now it works.

repo: dapr/dapr


text:
[Workflows]  Raise event payload is always null in my sample app

cc @cgillum
As per this thread on Discord, I'm not sure why this workflow code example here is not working. For some reason the raise event payload is null when I expect it to be a string of the value "OK".
The DaprWorkflowClient.RaiseEventAsync happens here
I'm sure this is something to do with my code, and not actually a but I can't figure it out.

my local environment

Mac OS - M1
Docker Desktop 4.20.1

Can reproduce this on the following dapr sidecar versions
1.11.1
client libraries
<PackageReference Include="Dapr.Client" Version="1.11.0" />
<PackageReference Include="Dapr.Workflow" Version="1.11.0" />`

Repro steps

pull repo https://github.com/olitomlinson/dapr-workflow-examples
docker compose build
docker compose up
Use insomnia/postman/whatever to start a workflow :
POST http://localhost:5112/start-raise-event-workflow?runId=100
note : The runId will become part of the workflow instance Id. i.e runId : 100 will become a workflow instance Id of 0-100
Raise an event to the workflow (you have 30 seconds) :
POST http://localhost:5112/start-raise-event-workflow-event?runId=100
note : The event payload is hardcoded to "OK"
Check the status of the workflow :
GET http://localhost:3500/v1.0-alpha1/workflows/dapr/0-100
Observe the workflow output is :
"dapr.workflow.output": "\"external event : \""
The expected output should be :
"dapr.workflow.output": "\"external event : \"OK"

/assign

@cgillum I reduced the workflow right down to this, and it still shows the payload as null

@cgillum If i use the HTTP interface to raise the event (not the dotnet SDK) then it comes through just fine. So this would imply its a problem with the code that is raising the event, not the workflow itself.

@cgillum Ok, I've narrowed it down to the client code.
If I use DaprClient to raise the event, everything works as expected.
However, If I use DaprWorkflowClient this does not.

@cgillum
It looks like the OrderProcessing example is using DaprClient and not DaprWorkflowClient which would explain why the example works, and why my code works now that I've switched over to DaprClient
https://github.com/dapr/dotnet-sdk/blob/8e9db70c0f58050f44970cda003297f561ab570a/examples/Workflow/WorkflowConsoleApp/Program.cs#L167
I think its safe to say DaprWorkflowClient is where the problem lies.

Thanks. I'm converting the sample to use DaprWorkflowClient instead of DaprClient now and will hopefully be able to reproduce the issue soon.

I've confirmed that this is an issue in the .NET Workflow SDK and not an issue in the runtime. PR with the fix is here: https://github.com/dapr/dotnet-sdk/pull/1119.

authors: cgillum olitomlinson


text:
Threat Model

Current situation
There is a Security Concepts page which lists the the current security features of Dapr very high-level without concrete recommendations or possible threats for:

Dapr-to-app communication
Dapr-to-Dapr communication
Network security
Bindings security
State store security
Management security
Component secrets

Challenge
Dapr states to "codifies the best practices for building microservice applications". This also includes security best practices and lessons learned.
On top, Dapr should also help developers to develop microservices in (strictly) restricted enterprise scenarios and/or industries.
Describe the proposal

Creating a threat model for Dapr
Analyzing it for potential
Recommend mitigations for these security issues

Put these together in a living security review docs (for making Dapr usage possible in strictly restricted environments with documentation obligations) and create a Security Guidelines / Best Practices page for practical usage across usages.

@yaron2 can you also please upload the original Threat Modeling Tool file - if we need to change/add anything to it, we don't need to start over. Thx!

repo: dapr/docs


text:
Delete compiled files from src/

This PR removes all compiled files from the src folder.
Also adds src/**/*.js to .gitignore to avoid this problem in the future.

I think this PR is not doing what you think it does


text:
unicode characters in response body

https://github.com/darrenburns/posting/blob/7b1d0ae86d2990fa89d52b612284af3aaf590b55/src/posting/widgets/response/response_area.py#L80
In some JSON-type API requests, the returned content may contain Unicode characters, it will show as '\uxxx....' and making the response body unreadable.
Maybe, will you please add an 'ensure_ascii=False' parameter in json.dumps to resolve this kind of issue?

Thanks for the report! Fixed in 1.1.0: https://github.com/darrenburns/posting/releases/tag/1.1.0

authors: breakstring darrenburns

repo: darrenburns/posting


text:
AppView performance investigation

Here are some remaining elements of AppView that look suspect:
.flatRootNodes:
List<Node> get flatRootNodes {
  return _flattenNestedViews(viewData.rootNodesOrViewContainers);
}

List<Node> _flattenNestedViews(List nodes) {
  return _flattenNestedViewRenderNodes(nodes, <Node>[]);
}

List<Node> _flattenNestedViewRenderNodes(List nodes, List<Node> renderNodes) {
  int nodeCount = nodes.length;
  for (var i = 0; i < nodeCount; i++) {
    var node = nodes[i];
    if (node is ViewContainer) {
      ViewContainer appEl = node;
      renderNodes.add(appEl.nativeElement);
      if (appEl.nestedViews != null) {
        for (var k = 0; k < appEl.nestedViews.length; k++) {
          _flattenNestedViewRenderNodes(
              appEl.nestedViews[k].viewData.rootNodesOrViewContainers,
              renderNodes);
        }
      }
    } else {
      renderNodes.add(node);
    }
  }
  return renderNodes;
}

@jonahwilliams noticed this was critical path in creating standalone embedded views (i.e. to use in a table, or other standalone repetitive component). He found the following API in use to get the "first" root node:
final rootNodes = (ref.hostView as EmbeddedViewRef).rootNodes;
intoDomElement.append(rootNodes.first);
return ref;

He tried using ComponentRef.location, but that seems to have (non?)significant whitespace compared to the above code, which causes tests to fail. The tests might be too strict, or it's possible we need to expose some sort of .firstRootNode as a convenience.

I did some more investigation and I haven't noticed any significant whitespace when using componentRef.location.  The test in question is most likely too strict.

Doesn't sound like there is any direct next steps here, so going to close for now.

authors: alorenzen jonahwilliams matanlurey

repo: dart-lang/angular


text:
Update favicon to use new Dart logo

cc @kwalrath @JekCharlsonYu

Let me know which resolutions you'd like in that .ico and I can create one for you. That one was created using:
convert dart/logo/default.png -define icon:auto-resize=128,64,48,32,16 dart/favicon.ico

You might not need that many sizes.

(If there is a general agreement on which sizes are needed, I can change the main favicon.ico file too.)

We should likely have a single one we can apply to all dart web properties. From some very casual browsing, we should be good with just 16x16 and 32x32.
I don't know how efficient convert is in terms of the size of the file it produces (I don't know that it isn't either, but we may want to check on it).

If there is a general agreement on which sizes are needed, I can change the main favicon.ico file too

Sounds great! I'm happy to use whatever we end up using for dartlang.org.

flutter.io uses a single 64x64 PNG. I'm inclined to do the same for darglang.org. Does that work for you?

👍

Done: you can pick up assets from, e.g., https://github.com/dart-lang/site-www/pull/835/files.

Thanks!

authors: chalin devoncarew

repo: dart-lang/dart-pad


text:
Removing doc code relating to MDN.

Removes some methods that used to grab MDN links on the fly for documentation
Updates the Code responsible for generating HTML versions of docs provided by the analysis server for display.
Removes related tests.

CC @miquelbeltran, since this is currently blocking dart-pad deploys and therefore his work.

I started this change this afternoon, and wasn't expecting anyone else to be working on it. Since @parlough's PR came in first, we should land that one instead.