Allow subdirectory server configuration, e.g. https://example.com/isso

Allow sudirectory server configuration, , e.g. https://example.com/isso
Description
When the isso root location was
https://example.com/isso

the administration pages did not work correctly.  The changes in this pull request fix that and allow proper working with or without a subdirectory.  E.g. both of these become valid configurations:
https://example.com
https://example.com/isso

The subdirectory case only requires the subdirectory to be passed as a parameter in the proxy call.  Here is an example nginx setup:
location /isso {
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Script-Name /isso;      // <---- critical for subdirectory config
    proxy_set_header Host $host;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_pass http://localhost:1234;
}

If the line proxy_set_header X-Script-Name /isso; is omitted, communication with isso will fail.
Testing
Given the blog address "https:\example.com", isso was tested using the following sites:
https://example.com/isso
https://another.com
https://another.com/isso

Other bugs found, not fixed yet
The active and delete URLs sent by the isso mail notification system were found to fail under the following conditions, with the follow symptoms:

Condition: Blog and Isso servers differ.  E.g.  https://example.com/ and https://another.com/.
Symptom: The active/delete URLs use the blog server instead of the isso server.
Condition: Isso is cofigured as a subdirectory, e.g. https://example.com/isso.
Symptom: The isso part is not included in the URL.
Condition: Both 1 and 2 together.
Symptom: Both

I will try to address these mail bugs later.

Now I have read
https://github.com/posativ/isso/issues/420
which proposes a configuration setting for the isso server public url.
That would seemingly remove the need for the changes in this pull.

@blatinier - I have updated and pushed.  This page of differences now looks correct.

Something must be added to documentation about server setting for the subdirectory case:  E.g. the below information.  That can be added in another pull if this one is ready to go.  Or it can be added in this pull.

The subdirectory case only requires the subdirectory to be passed as a parameter in the proxy call. Here is an example nginx setup:
location /isso {
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Script-Name /isso;      // <---- critical for subdirectory config
proxy_set_header Host $host;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_pass http://localhost:1234;
}
If the line proxy_set_header X-Script-Name /isso; is omitted, communication with isso will fail.

I see that documentation about proxy_set_header X-Script-Name /isso; already exists under docs.

I have modified isso/views/comments.py to follow the policy started in pull 443, which that the so-called 'public_endpoint' will be read from the conf file general/public_endpoint, and if that is not present it will be taken from the internal variable local.host.
This pull 458 originally introduced  local.host usage to to enable isso service as a subdirectory of the host URL, e.g. https://example.com/isso, where /isso is the subdirectory.  In the particular test case isso is proxied from an nginx server, with the configuration as shown above.
The purpose of the config general/public_endpoint setting option is as fallback in case, due to an unusual setup, or whatever.
It is worth adding that there already exists a config setting general/name which may have duplicate functionality with general/public_endpoint.  When setting up a second isso, and serving from an nginx location 'isso-2':
location /isso-2 {
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Script-Name /isso-2;      // <---- critical for subdirectory config
    proxy_set_header Host $host;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_pass http://localhost:1234;
}

I found it was necessary to set
[general]
name = isso-2

in order to get the connection to work.  Indeed the isso documentation on Multiple Sites explains that it is necessary to specify the subdirectory in config under general/name.


[AKS] az aks create: add support for --private-dns-zone and --fqdn-subdomain feature

Description

This pr copies feature --private-dns-zone and --fqdn-subdomain from aks extension because we're going to GA these two features.
Testing Guide

History Notes

[AKS] az aks create: add support for --private-dns-zone and --fqdn-subdomain feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

[x] I adhere to the Error Handling Guidelines.

@fengzhou-msft Could you help merge the pr? It's ready now.


feat: add article page

Description
#12 Articles - Image module
#21 Articles Markdown styling
#11  Articles Header (Edit Side Nav + On this Page + Breadcrumbs) <- sidenav I didn't work on it yet.
#13 Articles - Rating module
#20 Articles - Related articles module
Type(s) of changes

[ ] Bug fix
[x] New feature
[ ] Update to an existing feature

Motivation for PR

How Has This Been Tested?

Applicable screenshots
https://www.loom.com/share/1fddc30664d942a79e3cbcc074c29dae?sid=1f72dce9-69f3-41b9-90da-a7c050407ef0
Follow-up PR

also noticed this bug on the theme switcher on mobile. will add this to the QA items:

did you also add image module in this PR? Images are rendered in this way, without any vertical paddings and the gray background(with icon+caption) as the design

https://uniswaplabs.zendesk.com/auth/v2/login/signin?return_to=https%3A%2F%2Funiswaplabs1730152595.zendesk.com%2Fhc%2Fen-us%2Farticles%2F31449357746573-What-are-these-sections-and-articles-doing-here&theme=hc&locale=en-us&brand_id=31433470015629&auth_origin=31433470015629%2Cfalse%2Ctrue

this is image on
https://uniswaplabs.zendesk.com/hc/en-us/articles/17674084283149-How-to-swap-on-UniswapX
this article. The caption is part of the image, and we can't really render it separately...
https://uniswaplabs.zendesk.com/hc/article_attachments/24477317213581

did you also add image module in this PR? Images are rendered in this way, without any vertical paddings and the gray background(with icon+caption) as the design

The link on the image doesn't seem to work anymore...
https://uniswaplabs.zendesk.com/hc/en-us/articles/31449357746573-What-are-these-sections-and-articles-doing-here

Updated preview!:
https://www.loom.com/share/89b25eede3fe4e14b425ecccf0d7d45d?sid=af11d0de-3b83-42e0-9989-ab8dc0d6cdf3


Update README.md

Hi,
This small PR adds a link to warn potential users that there is a F-Droid version. That was what I was looking for^^

@alexdwork2018
I was multitasking and forgot to merge, sorry :P

@Poussinou
Thanks for the improvement!


[Feature Request] Link categories or tags

Allow users to create categories or tags 🏷 for their links 🔗. Useful for those using this as a bookmark manager. 📑

Have already been thinking about it since I use Pckd daily, and felt the need for better categorization. I'll create a GitHub project spreadsheet on this repo and add it there...

Thanks for the quick replies. Just sent a donation 🥇 👍 💯

Thank you so much... Things like these make me super-excited about bringing something new to the table... Can't express how over-joyed I am 🤩😄 Will make sure the money goes towards the required human resources for making Pckd and other projects better 😊


Add endpoint for downloading .ics (iCal) files per event

Closes: #2743
Description of changes

Add endpoint for downloading .ics (iCal) files per event
The current online.ntnu.no has no "Export to calendar" functionality, as the old solution has. Thus, I've added an endpoint that will be used in onlineweb-frontend for downloading the .ics file. See the WIP frontend branch here for current progress.

For the reviewer

How much documentation is usually added?
Inspect localhost:8000/api/v1/event/events/{id}/calendar to see the endpoint
I see that there exists a couple of API tests in apps/events/tests/api_tests.py. Should I add tests for this calendar endpoint, or are we good?

Code Checklist

[ ] I have added tests
[ ] I have provided documentation

see https://github.com/dotkom/onlineweb-frontend/pull/683


Terraform 0.11 - Add NAT Gateway to Database route table

This commit corrects the configuration of the create_database_nat_gateway_route feature where it adds a route to allow the databse subnets access to the internet.
Previously this feature would add the NAT gateway to the private subnet route table and not the database route table causing a conlict in configuration as both aws_route.private_nat_gateway and aws_route.database_nat_gateway would both want to add a route for destination_cidr_block = "<IP_ADDRESS>/0" which will cause the following error
Error: Error applying plan:

3 errors occurred:
        * module.vpc.aws_route.database_nat_gateway[0]: 1 error occurred:
        * aws_route.database_nat_gateway.0: Error creating route: RouteAlreadyExists: The route identified by <IP_ADDRESS>/0 already exists.
        status code: 400, request id: f64ae1fb-e56d-4eed-9117-97d392f0e8c4

        * module.vpc.aws_route.database_nat_gateway[1]: 1 error occurred:
        * aws_route.database_nat_gateway.1: Error creating route: RouteAlreadyExists: The route identified by <IP_ADDRESS>/0 already exists.
        status code: 400, request id: f5ac8726-ea1c-46b1-9a76-794efc95542b

        * module.vpc.aws_route.database_nat_gateway[2]: 1 error occurred:
        * aws_route.database_nat_gateway.2: Error creating route: RouteAlreadyExists: The route identified by <IP_ADDRESS>/0 already exists.
        status code: 400, request id: 9edbe494-2407-4552-88bd-498379da7dc8

Because there is only a single route table for the Database subnets even if they are multi AZ enabled I have selected to follow the standard that is in the aws_route.database_internet_gateway resource where the association is done for the first route table and NAT gateway.

@antonbabenko Hey! Can this be merged, I did a VPC design, where we are managing ec2 resources in the DB subnet, this would come in handy.

hi all, this is fixed in #518 for the current versions supported. unfortunately, we are not supporting Terraform 0.11.x anymore


Pushing pages to gh-pages instead of docs branch

Coverage remained the same at 93.75% when pulling 25dbbfa881f6d671202f3cc9352cdef559494998 on fix-pages into 9edc6d4b02946c8bba1135324398bb5ab1d9581c on master.


Make unread direct messages easier to spot

Right now the direct message channel (user) list is long enough that you have to scroll it just to check on whether there are any unread messages.  To make it easier to tell if there are unread messages (but to preserve the ability to message anyone by scrolling to their name), I propose we sort the user list by most recent communication.  This could be annoying but it's also optimized for the common case by showing you users with whom you communicated most recently.  And if we have a good /focus command then it's no longer important to sort the list alphabetically.
Thoughts @dagit and @aisamanra?

(Put another way: I want to get away from making scrolling the most useful means of navigating the list.)

I also wanted to experiment with separating out channels that have unread messages and floating them to the top as a separate list entirely. I don't know if that's a good idea so I want to try it before committing to it.
Otherwise, what you're proposing sounds good. There are also some keybindings we could implement to help:

keybinding to jump to next channel with unread messages (I propose Alt+a)
keybinding jump back to most recently focused channel (I propose Alt+s)

Bindings for improved channel navigation sound good to me!

Related to this, I changed the indicator for unread messages in a channel (including direct message channels). Now it uses a cyan bg similar to how the focused channel works.

Given all the recent UI changes plus the keybindings in 4e94212, I consider this complete. Reopen if you want more.


Optional inclusion of emoticons/ascii emojis when converting to image

Are there any plans to add an option to also include emoticons/ascii emoji when converting to images?
For the time being I'll be adding a small script to do this outside of tweemoji, but think it could be a nice addition to the tweemoji lib

Not at the moment, and probably not in the future either. Our focus is providing support for emoji defined in the Unicode standard, which regrettably doesn't include any ASCII equivalents.

Not at the moment, and probably not in the future either. Our focus is providing support for emoji defined in the Unicode standard, which regrettably doesn't include any ASCII equivalents.

Fair enough :)

Fair enough :)


net/http: Request.Body locking should be interruptable on Close

The fix to issue #6995 made me realize that the new locking introduced in revision
00cce3a34d7eSimilar is too coarse.

It's now possible for a goroutine outside of the main server handler goroutine to be
blocked in a Request.Body.Read (a transfer.go *body.Read) indefinitely, holding the
*body mutex.

That mutex then prevents the server code from closing that body when the handler
completes.

Similar to how an io.Pipe's PipeReader.Read will be interrupted when the pipe is closed,
I think the http server's Request.Body.Read needs to be interruptable.  Perhaps it
should just use io.Pipe somewhere.

Example test showing the problem:

// Test that a hanging Request.Body.Read from another goroutine can't
// cause the Handler goroutine's Request.Body.Close to block.
// See golang.org/issue/7121
func TestRequestBodyCloseDoesntBlock(t *testing.T) {
        if testing.Short() {
                t.Skip("skipping in -short mode")
        }
        defer afterTest(t)

        readErrCh := make(chan error, 1)
        errCh := make(chan error, 2)

        server := httptest.NewServer(HandlerFunc(func(rw ResponseWriter, req *Request) {
                go func(body io.Reader) {
            _, err := body.Read(make([]byte, 100))
                        readErrCh <- err
            }(req.Body)
        time.Sleep(500 * time.Millisecond)
        }))
        defer server.Close()

    closeConn := make(chan bool)
        defer close(closeConn)
        go func() {
                conn, err := net.Dial("tcp", server.Listener.Addr().String())
                if err != nil {
            errCh <- err
                        return
            }
                defer conn.Close()
        _, err = conn.Write([]byte("POST / HTTP/1.1\r\nConnection: close\r\nHost: foo\r\nContent-Length: 100000\r\n\r\n"))
                if err != nil {
                        errCh <- err
                        return
        }
                // And now just block, making the server block on our
                // 100000 bytes of body that will never arrive.
                <-closeConn
        }()
        select {
    case err := <-readErrCh:
                t.Logf("Read error = %v", err)
        case err := <-errCh:
                t.Error(err)
    case <-time.After(5 * time.Second):
                t.Error("timeout")
        }
}

Are there any plans to fix this ?
When streaming data from the client, this makes it impossible to stop the streaming from the server side.

I had forgotten about this. I put it on my list to investigate for Go 1.8.

@bradfitz seems like it passes now, unless am missing something. Running on tip
$ go version
go version devel +b53f0f8 Sat Feb 4 16:46:11 2017 +0000 darwin/amd64

with the code you provided in the bug report ie also at https://github.com/odeke-em/bugs/blob/master/golang/7121/issue_test.go with just defer afterTest commented
the test passes but prints out
$ go test -v
=== RUN   TestRequestBodyCloseDoesntBlock
--- PASS: TestRequestBodyCloseDoesntBlock (0.50s)
	issue_test.go:54: Read error = read tcp <IP_ADDRESS>:60113-><IP_ADDRESS>:60114: i/o timeout
PASS
ok  	_/Users/emmanuelodeke/Desktop/openSrc/bugs/golang/7121	0.513s

I have traced back the fixer to be commit 736443c13a718f0a9c30327ebbf09f58ccbe6d49 or CL https://go-review.googlesource.com/c/31148/.
Am finna enable the previously skipped test with a CL in a few.

I have traced back the fixer to be commit faf882d1d427e8c8a9a1be00d8ddcab81d1e848e or CL https://go-review.googlesource.com/c/31173/.
Am finna enable the previously skipped test with a CL in a few.


Add option to set PDF metadata

This is an enhancement suggestion for adding the ability to set PDF metadata when exporting with page.pdf()
Something like what PDFKit does: foliojs/pdfkit Getting started – Setting document metadata

While the chomium api doesn't support this yet, I would suggest to use the exiftool to add the data.
https://github.com/Sobesednik/node-exiftool#readme
What do you think? Should we use this to implement an option for the pdf function?
e.g. meta {
title: string,
...
}

@akaleeroy Puppeteer doesn't bring much on itself around PDF generation; all we have comes from Headless Chromium project.

if you want Chromium to generate PDF metadata firsthand, I'd recommend filing this feature request over to https://crbug.com/new
meanwhile, using third-party solutions on top of Puppeteer seem to be a good workaround

Hope this helps

Ok thanks
https://bugs.chromium.org/p/chromium/issues/detail?id=907249

For anyone coming across this issue in hopes of seeing a way to set the values of the creation and modification date and time stamps in the PDFs so that the generated PDFs are deterministic given the same HTML, I have settled on patching the PDF buffer and zeroing those fields:
await page.goto('https://news.ycombinator.com', { waitUntil: 'networkidle0' });
await page.waitForFunction(() => [...document.images].every(i => i.complete));
const path = join(__dirname, 'news.ycombinator.com.pdf');
await page.pdf({ path });

// Wipe out date and time stamp ranges to make the PDFs deterministic
const buffer = await fs.readFile(path);
for (const offset of [97, 98, 99, 100, 132, 133, 134, 135]) {
  buffer[offset] = 0;
}

await fs.writeFile(path, buffer);

The rest of the PDF seems to be deterministic. It is possible the Chromium version also needs to be patched, it might get embedded in the PDF in a creator field, I have not checked that.


overflow in the coverage counters?

I've been fuzzing duktape (https://duktape.org/), and I'm getting some strange output regarding the coverage counters.  Duktape was compiled with hfuzz-clang for instrumentation. Is this an overflow somehow, or just program logic gone wrong?
------------------------[  4 days 08 hrs 44 mins 21 secs ]----------------------
  Iterations : 328,204 [328.20k]
  Mode [3/3] : Feedback Driven Mode
      Target : ./lava-hf/bin/duk ___FILE___
     Threads : 2, CPUs: 256, CPU%: 3394% [13%/CPU]
       Speed : 0/sec [avg: 0]
     Crashes : 38433 [unique: 6814, blacklist: 0, verified: 0]
    Timeouts : 10,345 [10 sec]
 Corpus Size : 95,680, max: 1,048,576 bytes, init: 1 files
  Cov Update : 0 days 00 hrs 00 mins 03 secs ago
    Coverage : edge: 8,908,447,096,139,219,040/10,320 [523352139134052%] pc: 13,018,899,449,539,872,429 cmp: 4,366,674,375,845,433,957
---------------------------------- [ LOGS ] ------------------/ honggfuzz 2.1 /-

Does it still happen? I've never noticed anything like this myself. Looks more like some kind of underflow to me. I guess 8,908,447,096,139,219,040 is closer to -1 for uint64_t.

Please re-open if it's still happening.


Does SunEditor prevents the dangerous code and JS Codes?

Hi, first of all thanks for this editor. Its great and really works good.
And i want to ask is suneditor preventing the dangerous code for example html injection or js code inside of html?
Version
Latest
Additional context
Add any other context about the problem here.

Hi @okandavutosf
Yes Script tags or JS codes are removing the inputable properties.
XSS attack related issues are being updated whenever they are found.

Thanks for your answer

@JiHong88  For iframes dowe have any option for the prevent js code?

The 2.41.1 version has been updated.
If this issue has not been resolved, please reopen this issue.
Thank you.


PWM sync

This sync up the FMU scheduling to the control outputs. We need to add a PWM signal generation sync as well and we might need a separate queue for FMU (or convert it back to a blocking thread). Then this pattern allows minimal latency PWM outputs.

Performance counter output:
fmu_pwm_sync: 12057 events, 0 overruns, 5943668us elapsed, 492us avg, min 38us max 1749us 536.311us rms

Need to to this differently.


PlugDiff mappings

Hoping you will be interested in this (obviously) and maybe try it out a bit (I've only been using it for a day).
This introduces some new mappings for :PlugDiff:
J and K can be used from the diff buffer to scroll the commit preview window without having to switch to it.
<C-N> and <C-P> can be used to jump straight to commit lines (sorta like jumping to files in fugitive's commit window).
I've also made the commit window unmodifiable and mapped q to :quit (while inside it).
This PR introduces a s:buffocus() utility function.  This is used to ensure that the J and K mappings will only ever scroll the commit preview window.  If you would like me to ditch it in favour of wincmd p--or just change its location in the file--I will oblige.
I've also documented the <CR> and o mappings for :PlugDiff.
If you're willing to accept this PR, I'm happy to make any other changes or edits but otherwise, thanks for this amazing plugin manager.

Thanks, looks useful. I'll review the code later in the day. Can you write test cases for these?

By the way, the same idea can be implemented without touching the core. This approach can be considered to be more flexible as it allows users to choose whatever keys they want. (e.g. CTRL-J/K instead of J/K) What do you think?
function! s:scroll_preview(down)
  silent! wincmd P
  if &previewwindow
    execute 'normal!' a:down ? "\<c-e>" : "\<c-y>"
    wincmd p
  endif
endfunction

function! s:setup_extra_keys()
  nnoremap <silent> <buffer> J :call <sid>scroll_preview(1)<cr>
  nnoremap <silent> <buffer> K :call <sid>scroll_preview(0)<cr>
  nnoremap <silent> <buffer> <c-n> :call search('^  \zs[0-9a-f]')<cr>
  nnoremap <silent> <buffer> <c-p> :call search('^  \zs[0-9a-f]', 'b')<cr>
endfunction

autocmd! FileType vim-plug call s:setup_extra_keys()

That's a lot more elegant than mine :+1:  I know I'm doing a bit much with the s:buffocus() to cover an edge case... I got overboard sometimes!
I chose J/K since it's very common for people to use CTRL-H/J/K/L for window navigation and I always appreciate it when the plugin makes the choices for mappings in unmodifiable buffers (as vim-plug does!)  This is the first time I've ever found myself wanting to scroll and alternate window, so I wanted some new mappings for that idea.
So you're just saying to use this in my vimrc?  If you don't want to include it, is it cool to at least make the preview window unmodifiable?  I'm always on a 13" laptop so I find myself jumping into it and pressing q to close it in order to see more of the update list.  I might be alone in this.
The other thing I was thinking <C-N>/<C-P> could do is jump to the first commit of the next plugin.  Not sure how you feel about that.
In any event, thanks for the attention to this!  I know I'm talking a lot about a small feature, but :PlugDiff is one of my favourite aspects of this plugin.
And yes, I can write tests for anything you are willing to accept!

+1 to unmodifiable and q. I'm a bit split on the other ones though. In principle, we know that the "right" way to have them is to provide <Plug> mappings for each one of them so that the users can customize if they do not like the default. But at the same time, I'm not a big fan of plugins with too many configuration knobs. And since I'm not certain yet which set of keys or behaviors should be the default, I'm leaning towards just putting the above code on the wiki page, so that the users can have it on their vimrcs however they like.

I'm fine with all that.  Thank you, sir!

Thanks, could you to update the PR to have only q and unmodifiable? The change becomes trivial then but I'd like to give you some credit for it.

Done.  Thanks a lot!

Merged, thanks! I'll create a wiki page and let you know.

So here's the page: https://github.com/junegunn/vim-plug/wiki/extra
You can freely update or add examples. Thanks.

Awesome, thanks for the credit :)
gx is also a great idea!

FYI, I just realized that making the buffer nomodifiable caused problem when o or enter is pressed again for the commit. Pushed the fix.

  I only tried opening different commits.  My
bad.  Thank you!
On Wed, Jul 8, 2015 at 12:27 PM, Junegunn Choi<EMAIL_ADDRESS>wrote:

FYI, I just realized that making the buffer nomodifiable caused problem
when o or enter is pressed again for the commit. Pushed the fix.
—
Reply to this email directly or view it on GitHub
https://github.com/junegunn/vim-plug/pull/255#issuecomment-119650560.

No problem!


[Task]: Fix OutputData type

Task description
There are some errors in the OutputData type, the following should be fixed:

OutputData is missing the metadata field
Output is one level too much. In the received output we don't have the {type: , data:} wrapping
Same for the OutputData.address:  address should be of type AddressTypes without the wrapping

Requirements
TBD
Acceptance criteria
TBD
Creation checklist

[ ] I have assigned this task to the correct people
[X] I have added the most appropriate labels
[X] I have linked the correct milestone and/or project

@MarkNerdi , @nicole-obrien , this should have been fixed with the new wallet version. Let me know if anything is still missing


Add any/all documentation

Adds documentation for the any/all statement blocks referenced in https://github.com/kyverno/kyverno/issues/1765 (see referenced PR and parent issue) which adds functionality to validate.deny.conditions and preconditions objects. The ultimate objective would be to link to the same section under the preconditions portion of these docs when this capability is expanded to other Kyverno sections as outlined in https://github.com/kyverno/kyverno/issues/1485 (such as pattern, anyPattern, matchExpressions, and matchLabels)
Closes #104

@yashvardhan-kukreja could you please review?

@JimBugwadia your review, please


Increment versions for schemaregistry releases

Increment package versions for schemaregistry releases

API change check
API changes are not detected in this pull request.


Use cache.adapter.apcu instead of deprecated validator and serializer

According to the https://github.com/symfony/symfony-standard/pull/965

We need to wait with merging this until the demo switched to Symfony 3.1.

I'm wondering when do we plan to switch on Symfony 3.x?

The master branch is now Symfony 3.1.

Should we merge this as it is now? Thanks.

:+1:

@bocharsky-bw it's merged now. Thanks!


Basic code optimizations

I suggest fill this issue with basic code optimization suggestions (performance and engineering) that are non-critical but could make code more correct.

[ ] Here static_pointer_cast is slow because of new shared_ptr creation and even unnecessary, I think using simple reference without a pointer is good here because we do not event want to pass null to underlying functions.
[ ] Here new instance of consensus is created every time we request access to it. However, I think it will be better to preallocate them and use already existed once instead of creating the same object on each call. Also handling such const objects there can be changed from vector to array because it is a good manner.

This is more of a code cleanup task, but there are a lot of conditionals in the code that are only relevant for older pre-2018 bitcoin releases which could be removed to simplify the code and improve performance slightly because pocketnet will never hit those code cases.

I would suggest that each participant make edits to the code without much regard for the team - every change will be reviewed anyway. Here we could post discussion links if needed.

The following functions are very generalized, although they do not make sense - only a few fields can be used in finite functions, or even just the fact of the presence/absence of an entry in the database.


Recursively get package data

Summary of changes
Recursively get package data
This should be called from within setup.py's setuptools.setup() function, e.g. package_data={'my_package': get_pkg_data(pkg_name='my_pckage', ...)}

Pull Request Checklist

[ ] 1. Changes have tests
[ ] 2. News fragment added in changelog. See documentation for details

Additional details
Will be getting to (1) and (2) shortly.

Hmmm. I do think it's reasonable to have a package data equivalent of find_packages, but should it maybe be called find_pkg_data?
That said, this is a new public API to maintain, and I find find_packages somewhat dangerous as it is (case in point: https://github.com/flask-admin/flask-admin/issues/1706). I do worry that we're going to be in a similarly dangerous situation here (though TBH accidentally installing extra package data is probably better than accidentally installing extra packages).
One thing to keep in mind is that we should probably try and keep this consistent with importlib.resources, since that seems to be the "new way" to get data resources.
In any case, we may want to spend a bit of time to discuss this before you spend too much more time on it @joeflack4.
@jaraco @benoit-pierre @warsaw Any thoughts on this?

Thanks for the consideration. Definitely you guys can let me know if you want me to work on this implementation in any of the ways so far mentioned (find_pkg_data and possibly importlib.resources sound like good ideas to me), or other ways.
I don't have much experience on the folly of expanding the public API. I feel though like this would be a first step in lowering the barrier of entry into packaging, which would make for more packages on PyPi (or internal builds), which I think would be overall a good thing. I think a nicer implementation would be to just accept glob patterns into package_data directly, but I know that would be a much tougher sell (and harder to implement).

That's a good point, on setup.cfg and setup.py. I would agree that if they're feature set is in sync now, it should be kept that way.
The use case for recursively adding package data is to make including package data easier / more maintainable. If I have a single folder that has a deeply nested tree structure, then without using recursion, I have to go through and manually list out each "leaf" (bottom level folder in the hierarchy) individually. And, if the folder structure changes, then this now breaks my import of package_data in setuptools. I have to remember to go back and edit the list to adhere to my new structure. In my case, I we forgot to do that, and we deployed without package_data included, causing bugs.
As far as implementation goes, I think ideally, a glob pattern would be better than a recursive function, but I would entrust that implementation to someone more familiar with setuptools.

@joeflack4 Can you provide an example package that illustrates the use-case (that's currently clumsy and would be more streamlined with this change)?

@jaraco I'd love to!
I brought this up because I have a package that serves as a Python API and CLI, and another package that is a web app. As background, the software converts certain kinds of Excel files into Word documents, etc. There are templates that allow for different documents format, and those are the package data I'm trying to include. Each template has its own folder, and tends to have subfolders.

The package: https://github.com/pma-2020/ppp
Templates folder: https://github.com/PMA-2020/ppp/tree/master/ppp/templates
My setup.py, which has the recursive get_pkg_data() function def and shows usage: https://github.com/PMA-2020/ppp/blob/master/setup.py

I think this PR relates to #1806.

Oh yes, definitely.
Wow, I didn't even know that glob() supported recursion. Yeah, if you can just support it that way, that would be more ideal than my PR here.

It sounds like a better approach here could be to add support for recursive globs. Would you explore that approach?


Keeps want to recreate users on every run

Every time I run puppet, I get:
Notice: /Stage[main]/Jenkins::Users/Jenkins::User[admin]/Jenkins::Cli::Exec[create-jenkins-user-admin]/Exec[create-jenkins-user-admin]/returns: executed successfully
Info: /Stage[main]/Jenkins::Users/Jenkins::User[admin]/Jenkins::Cli::Exec[create-jenkins-user-admin]/Exec[create-jenkins-user-admin]: Scheduling refresh of Class[Jenkins::Cli::Reload]
Info: Class[Jenkins::Cli::Reload]: Scheduling refresh of Exec[reload-jenkins]

Looks like a duplicate of  #684

I don't think this is a duplicate. ONCE I could get #684 to succeed, but I still got this [the 'try to create on every run'].


How to sort list items by date

On a page I have a field type list with some events. Now I want to sort this list of items by date. How can I achieve this?
This is my .yaml file:
title: Events
'@extends': default

form:
  fields:
    tabs:
      fields:
        content:
          fields:
            events:
              type: section
              title: Events
              underline: true

              fields:
                header.event.items:
                  name: event
                  type: list
                  label: Event
                  style: vertical
                  btnLabel: Event hinzufügen
                  collapsed: true
                  sort: false

                  fields:
                    .title:
                      type: text
                      label: Titel
                      validate:
                        required: true
                    .date:
                      type: date
                      label: Datum
                    .fromtime:
                      type: time
                      label: Uhrzeit Start
                    .totime:
                      type: time
                      label: Uhrzeit Ende
                    .text:
                      label: Text
                      type: markdown
                      validate:
                        type: textarea
                    .category:
                      type: text
                      label: Kategorie
            options:
              fields:
                header.events.enabled:
                  type: ignore

This is my twig file:
{% extends 'partials/base.html.twig' %}

{% block content %}

{{ page.header.title }}

{{ page.header.subtitle }}

	{{ page.content }}

	{% set events = page.header.event.items %}
	{% for event in events %}

{{ event.title }}

				{{ event.date|date("l") }}
				{{ event.date|date("d") }}
				{{ event.date|date("M") }}

			{{ event.text|markdown }}

	{% else %}

Keine Events vorhanden.

	{% endfor %}
{% endblock %}

Lists are simply arrays of values, those are inherently not ordered dynamically, they are output in the order they are stored.  You can re-order via the admin, or if you are working in the YAML file, you can reorder the file if you like.
Now to do it programmatically, you should be able to do this with sort_by_key filter -> https://learn.getgrav.org/themes/twig-filters-functions#sortbykey
{% set people =<EMAIL_ADDRESS>'id':34}<EMAIL_ADDRESS>'id':21}<EMAIL_ADDRESS>'id':2}]|sort_by_key('id') %}
{% for person in people %}{{ person.email }}:{{ person.id }}, {% endfor %}

Yeah nice, that's it. Thank you for the quick response!


silent record audio on mac os

I try to use sounddevice to record. But the output record audio is just silent on mac os.
It would be very grateful if someone could give me a hint. Thanks a lot.

Would you mind providing a bit more information?

Having a similar issue, the numpy array coming back from using the sounddevice.rec function returns a numpy array that contains all 0s. I am also using Mac OS mojave so could be related? I have confirmed that I can record via quicktime so the mic does not seem to be the issue.
Similar question asked here: https://stackoverflow.com/questions/53717870/unable-to-record-sound-with-sounddevice

I use pycharm and could record using pyaudio.

I had a similar problem because vscode's terminal wasn't asking permission from the OS to use the microphone. Once I launched it on a regular terminal and accepted the request, it worked just fine in both terminals. Hope I could help


The release workflow is blocked in a fork repo

Propose-a-new-feature
Description

https://github.com/Flouse/axon/actions/runs/5965844552
Describe the solution you'd like
A forked repo may want to release its own version for testing.

[x] fix: a forked repo doesn't have self-hosted runners
-> Maybe add a condition to handle this

fixed by
https://github.com/axonweb3/axon/blob/9ce5aa0cc8e554f3a655dc9dc6394cdad69b96ff/.github/workflows/build_image_ghcr.yml#L13-L19


IO; cross platform key:value api

See
https://github.com/underscorediscovery/luxe/issues/198

https://github.com/underscorediscovery/snow/commit/1077834c0a9c88bcadec9e2325faed4cce55c80a


Add more modules

[ ] Divide: two source modules, outputs the first divided by the second. Option to perform zero divisions silently?
[ ] Reciprocal: one source module, outputs one divided by the source value. Option to perform zero divisions silently?
[ ] Logarithm: one source module, outputs base-b logarithm of the source value. Parameter to control the base. Option to output NaN rather than throw an exception when value or base is non-positive?

At the moment the procedure to add more modules (in the json-noise-modules branch) is quite complex. Here are the steps:

Write the module header and implementation.
Add the header to noise/modules/WangscapeModules.h.
Write a spotify-json codec for the module.
Add the module to moduleDecodeTable in EncodedModuleGroup.cpp.
Add test cases:

JSON files for decoding.
`TestModuleDecode::type specialisation.
TestModuleDecode::compareModules specialisation.
TestModuleDecode constructor specialisation which builds modules for comparison to the JSON files.

Add Wrapper specialisations for setSeed, setControlModule, setDisplaceModule, if necessary.


Fix storage file path to data/sportspa.json

Codecov Report

Merging #261 (81252b7) into master (53b775b) will decrease coverage by 0.18%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master     #261      +/-   ##
============================================
- Coverage     76.24%   76.05%   -0.19%
- Complexity      892      894       +2
============================================
  Files           130      130
  Lines          2572     2577       +5
  Branches        303      306       +3
============================================
- Hits           1961     1960       -1
+ Misses          512      511       -1
- Partials         99      106       +7

Impacted Files
Coverage Δ

...eedu/address/logic/commands/FindMemberCommand.java
100.00% <ø> (ø)

src/main/java/seedu/address/model/UserPrefs.java
82.50% <100.00%> (ø)

.../address/logic/commands/MarkAttendanceCommand.java
83.33% <0.00%> (-16.67%)
:arrow_down:

...ddress/logic/commands/UnmarkAttendanceCommand.java
83.33% <0.00%> (-16.67%)
:arrow_down:

...ress/logic/parser/MarkAttendanceCommandParser.java
63.63% <0.00%> (-16.37%)
:arrow_down:

...ss/logic/parser/UnmarkAttendanceCommandParser.java
63.63% <0.00%> (-16.37%)
:arrow_down:

...va/seedu/address/model/person/TodayAttendance.java
81.81% <0.00%> (-1.52%)
:arrow_down:

...c/main/java/seedu/address/model/person/Member.java
80.00% <0.00%> (ø)

...ava/seedu/address/logic/commands/SplitCommand.java
88.23% <0.00%> (ø)

...va/seedu/address/model/person/TotalAttendance.java
63.63% <0.00%> (ø)

... and 2 more

Continue to review full report at Codecov.

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

Yup this looks good, should fix the current issues regarding saving to the data file. We might have to delete both sportspa.json and preferences.json and then run SportsPA for it to work properly again


add validation component

Validation Component
Wraps any number of inputs and validates them on either a set of build in rules or custom passed in rules. The child of the Validation component must be a function and that function is passed several arguments to work with.
Props Passed Through

validations
This is a required object that maps input fields to what rules their values need to adhere to. The keys need to match the name field on the inputs. The value needs to be an array of strings that correspond to the rules that need to be used for that input.

     const validations = {
        firstName: ["required"],
        email: ["required", "email"],
       password: ["required", "min:3", "max: 15"]
   }

rules
Rules is an optional object that can be passed through to add custom validations. These custom validations are then referenced in the validations prop. A rule consists of two things a test function and a message function. The key of the object is the name to reference the rule by.
The test function will be passed the value of the input at the point you validating and should evalute to true if the value is valid and false if it is not, and the message function will receive the name of the field to in order to display in any error message you may want to create. To create your own rule :

     const rules = {
        coolRule: {
          test: (val) => val.indexOf("cool") >= 0,
          message: (field) => `${field} should contain the word cool`,
        },
     };
    const validations = {
        firstName: ["required", "coolRule"],
    };

You can also overwrite just a test or message of any build in rule by just passing in the item you need to replace
     const rules = {
        required: {
          message: (field) => `${field} should be required and this message is custom`,
        },
     };
    const validations = {
        firstName: ["required"],
    };

Arguments Passed Through To Function

validate
a function that can be attached to any input event in order to validate that input. The event is passed through and the Validation component validates based on the rules passed in
errorMessages
an object of errorMessages. Keys are based on the inputs name field. An input with name="first" an access error messages from errorMessages.first
allValid
a boolean telling you if all fields attached to the validator are valid
errorCount
total error count

  <Validate
      validations={{
        firstName: ["required", "min:3"],
      }}
    >
      {(validate, errorMessages, allValid, errorCount) => (
         <input type="text" onChange={validate} name="firstName" />
         {errorMessages.firstName && errorMessages.firstName.map(val => <p>{val}</p>)}
      )}
 </Validate>

Built In Rules

required
email
min
max

Rules with arguments
Some built in rules and any custom rules have the ability to take arguments. For example the built in rule for min:3 Passes the argument 3 into both the test function and message function.
Rules with arguments are :

min
max

Creating your own rules that take arguments will need to define both the test function and message function a bit differently
       min: {
          test: (arg) => (val) => val.length >= arg,
          message: (arg) => (name) => `${name} must be at least ${arg} characters.`,
      },

You have to curry your functions to take the argument first and then return a function that takes the value.

@jcreamer898 talked about not leaving this in backpack but I wanted to make sure that we liked this approach before I pulled it into its own package. Let me know what your guys thoughts on that are.

Very thorough comment! I'll take a look.

This is cool, I'm all for it. Where do we think it could live? Would it be its own npm module?

react-validate-form is available. :)

@jcreamer898 @thomasthesecond so we are thinking this should be its own module? I am cool with that. react-validate-form under lonely planet works for me

That's what I'm thinking.

What are your thoughts @thomasthesecond?

moved into own package


[DRAFT] EECS 149 Lab Applications

LF adaptions of EECS 149 lab robot state machines for the buckler+nrf+romi platform.

Closing this PR to avoid confusion as it has been subsumed by https://github.com/icyphy/lf-buckler/pull/2.


test: unit test inflation rate for year fifteen

Motivation https://github.com/celestiaorg/celestia-app/pull/2030
Follow up https://github.com/celestiaorg/celestia-app/issues/2032

It's already tested for here:
https://github.com/celestiaorg/celestia-app/blob/965eafb4357376aec31f84f3628f7703c5587f9a/x/mint/types/minter_test.go#L40

oh phew 😅

Will leave this open b/c the refactor is a nice to have but not necessary.

Codecov Report

Merging #2031 (12823db) into main (3aaa69d) will decrease coverage by 0.55%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #2031      +/-   ##
==========================================
- Coverage   22.08%   21.54%   -0.55%
==========================================
  Files         130      127       -3
  Lines       14479    14293     -186
==========================================
- Hits         3198     3079     -119
+ Misses      10981    10922      -59
+ Partials      300      292       -8

see 15 files with indirect coverage changes


[Question] internal deployment replicas, it is safe to reduce for small cluster?

I have simple cluster, 1 master + 1 worker(for now).
i reduced storage class replicas to 1, since i have one worker yet.
But i looked into longhorn namespace and found out that csi-attacher, csi-provisioner, csi-resizer deployments also have several replicas.
Can i safely reduce that amount to 1 replica per deployment? and then increase back with increasing cluster size?

For non production clusters (evaluation, learning, testing, etc), it's safe to reduce the replica count for the kubernetes CSI components.

i start with small cluster, at first, later will add more workers to it.
so i just will need to add replicas back, right?

For the kubernetes CSI components that will work.

thank you.

thank you


feat: expanded on npm run push

What type of PR is this? (check all applicable)

[x] 🍕 Feature
[ ] 🐛 Bug Fix
[ ] 📝 Documentation Update
[ ] 🎨 Style
[ ] 🧑💻 Code Refactor
[ ] 🔥 Performance Improvements
[ ] ✅ Test
[ ] 🤖 Build
[ ] 🔁 CI
[ ] 📦 Chore (Release)
[ ] ⏩ Revert

Description
implemented the changes requested by @0-vortex. why using npm run push is important to release process.

Related Tickets & Documents
Fixes #39

Mobile & Desktop Screenshots/Recordings

Added tests?

[ ] 👍 yes
[x] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help

Added to documentation?

[ ] 📜 README.md
[ ] 📓 docs.opensauced.pizza
[ ] 🍕 dev.to/opensauced
[ ] 📕 storybook
[x] 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?

I guess the node update hasnt been in implemented in the netlify deploy preview.

I guess the node update hasnt been in implemented in the netlify deploy preview.

Don't worry about that, we will get it fixed eventually! 🍕


Feature request. Airbnb support in demo project

Hi
you can propose pull request for it, but I will no add myself
there is a wiki page, which describe how to add a provider
https://github.com/OAuthSwift/OAuthSwift/wiki/Demo-application#add-a-new-service-in-demo-app
maybe someone will do it one day
then when asking for something, the minimum its to provide the link to the airbnb documentation about authentification with oauth
http://airbnbapi.org/
it seems weid, you must use facebook or google oauth, there is specific HTTP header "X-Airbnb-OAuth-Token: 9nwld6we4td9vkwj160teb49a". Not a real oauth ...


Example does not compile

Cloning the qevy project then running:
cargo run --example first_person --features="xpbd"

Fails to compile. It seems like there have been api changes since the example was written. For example, is no "open_time" property for the Door component.

Here are all the errors i got from compilation (with a few path fixes due to new api):
mover.start_translation field not existing
mover.speed field not existing
door.triggered_time being an unknown field

I will try and fix the example and make a PR. Id love to use this project in my game!

Hey @fami-fish thanks for reporting this, I'm having a hard time finding the time to maintain this project at the moment so a PR fixing this example would be very much appreciated!

👋 I have a PR for updating to Bevy 0.14, (#9) it also fixes the example


Update logic to match GPUs only for optimized model selection

I know you didn't do this for giggles...what happens if someone specifies engine: vllm?  Or is the goal to remove that too?  (Not urgent, I'll catch on eventually.)

I know you didn't do this for giggles...what happens if someone specifies engine: vllm? Or is the goal to remove that too? (Not urgent, I'll catch on eventually.)

If it is explicitly specified, we match with only those backends/engines. If not, we assume "tensorrt" when GPU/ID filtering is provided, as that only applies to optimized models.


Do not merge - release docs

Update the release documentation to be more accurate and easier to follow

Looks good, I've followed these instructions as part of 8.7.0 release. I've also rebased this off master to update the branch.


Rewrite narrow links in messages

A message can contain a narrow link such as: https://chat.zulip.org/#narrow/stream/.... These links redirect users to a particular message when using the web app.
We should rewrite these links in the mobile app so that users jump to the appropriate place in the stream after clicking on them (instead of opening up a browser window with the web app)

Oh yeah, good idea.


Unable to find config options

Sorry If I missed it but I cannot fond the reference for the various config options that can be passed to the plugin factory function. A few are distributed around the docs and examples, some code snippets in the docs include others. Some look like they are vite config options that might be passed through.
I'd expect to see then listed or linked to here:
https://vite-plugin-pwa.netlify.app/guide/#configuring-vite-plugin-pwa

@SteveALee the types are in the README file: https://github.com/antfu/vite-plugin-pwa#-full-config.
I will add a link to the types to the docs: https://github.com/antfu/vite-plugin-pwa/blob/main/src/types.ts

@SteveALee I'm adding a PWA Build application, check this PR https://github.com/antfu/vite-plugin-pwa/pull/331.
You can also check the preview in previous PR, the app is WIP, the generate button does nothing...

For now  I found the the list of names and default values here - https://github.com/antfu/vite-plugin-pwa/blob/main/src/options.ts#L40-L59

@userquin Oops, seems I needed to refresh the page before adding my comment - thanks

Adding a link is good idea for folks like me reading the docs on their phone not using an IDE with intellisense. :)
PS Using the vite vanilla template plus this plugin is super simple way to create a PWA - thank you and team.

@SteveALee are you asking for client (virtual modules) or plugin types? anyway, in the README page (at bottom) you have both links.
I'll add both links to the docs.

@userquin
I'm after all the options and values for the object passed to the plugin factory function VitePWA used in vite.congif.js
import { VitePWA } from 'vite-plugin-pwa'
export default defineConfig({
  plugins: [
    VitePWA({
      registerType: 'autoUpdate',
      devOptions: {
        enabled: true
      }
    })
  ]
})

Nice little builder.
I used the vanilla vite template - no framework - and I notice neither docs or builder really address that choice.

@SteveALee check this repo: https://github.com/userquin/vite-plugin-pwa-vanillajs

@SteveALee added on FAQ, on the guide index and also in the frameworks index: check https://github.com/antfu/vite-plugin-pwa/pull/339

@userquin Looks good. Thank you!


Data Science with Python : Long Short-Term Memory tutorial "LSTM"

Description
Welcome to 'DSWP' Team, good to see you here
In this issue, you will make a tutorial and notebook  about LSTM
the notebooks one implement with TensorFlow and another one using Pytorch
To get assigned to this issue, add your serial numbers mentioned in the spreadsheet of "Data Science with Python", the approach one would follow, and choice you prefer (Documentation, Audio, Video). You can go with all three or any number of options you're interested to work on.
If you had referred any resources, add them up in "DS Resources". Similarly if you had used datasets, include them in "DS Datasets".
Domain: Machine Learning
Mentors Assigned : @Kareem-negm / @DhruvBajaj01
Start from: you can use this notebook to give you a sample overview
Points to Note :
The issues will be assigned on a first come first serve basis, 1 Issue == 1 PR.
"Issue Title" and "PR Title should be the same. Include issue number along with it.
Changes should be made inside the Datascience_With_Python/ directory & Datascience_With_Python branch.
Follow Contributing Guidelines & Code of Conduct before start Contributing.
This issue is only for 'GWOC' contributors of 'DSWP' domain.
All the best. Enjoy your open source journey ahead. 😎
Domain
Data science with Python
Type of Contribution
Video, Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

@prathimacode-hub Ma'am I would like to work on this issue.I will explain all the necessary information in detail  and code regarding it.
Type: Documentation
Sr No.: 146

Issued assigned go @srini047 for documentation


Add my project, please: [FarmCoin]

Thanks for using ethers and we look forward to including a link to your project on ethers.
Please include the following details:

Link to GitHub repository (currently only GitHub is supported, and the project must be public)
A 256x256 px image (JPG or PNG) for a logo to include (attach it to this issue or include a link)
A public e-mail address or Twitter account with DMs enabled (this is used to resolve dead links or other concerns with the project)

Notes:

All projects are previewed and vetted before inclusion, and monitored for changes and regularly reviewed
Project license should be compatible with Open Source Initiatives
Images will be hosted by ethers to protect privacy; contact me to update a logo

Roll-It, Smoke-It, Appreciate-It,


add EWMA as per #104

For functions that take more arguments than just seriesList the final target name in the response is "foo(series)" instead of "foo(series,bar)", i.e. the rest of the arguments is not included in the target name.


HTTPS Push

This is the set up:
Ruby 1.9
Rails 3.2
Redmine 2.6.1
jbox's redmine_git_hosting plugin
Trying to use git repo through HTTPS. Clone works fine. Push starts and hangs at
Counting objects: 3, done.
Writing objects: 100% (3/3), 206 bytes | 0 bytes/s, done.
Total 3 (delta 0), reused 0 (delta 0)
Apache says the issue is:
App 1013 stderr: [ 2015-02-03 16:33:59.3105 1036/0x0000000782d9b0(Worker 1) utils.rb:68 ]: *** Exception ArgumentError in Rack body object #each method (wrong number of arguments (3 for 1..2)) (process 1036, thread 0x0000000782d9b0(Worker 1)):
App 1013 stderr: from /home/r2d2/.bundler/ruby/1.9.1/grack-971b468103ac/lib/grack/server.rb:78:in popen' App 1013 stderr: from /home/r2d2/.bundler/ruby/1.9.1/grack-971b468103ac/lib/grack/server.rb:78:inblock in service_rpc'
App 1013 stderr: from /usr/lib/ruby/vendor_ruby/rack/response.rb:89:in call' App 1013 stderr: from /usr/lib/ruby/vendor_ruby/rack/response.rb:89:ineach'
App 1013 stderr: from /usr/lib/ruby/vendor_ruby/rack/body_proxy.rb:31:in each' App 1013 stderr: from /var/lib/gems/1.9.1/gems/activerecord-3.2.21/lib/active_record/query_cache.rb:46:ineach'
App 1013 stderr: from /var/lib/gems/1.9.1/gems/activerecord-3.2.21/lib/active_record/connection_adapters/abstract/connection_pool.rb:460:in each' App 1013 stderr: from /usr/lib/ruby/vendor_ruby/rack/body_proxy.rb:31:ineach'
App 1013 stderr: from /usr/lib/ruby/vendor_ruby/phusion_passenger/rack/thread_handler_extension.rb:140:in process_request' App 1013 stderr: from /usr/lib/ruby/vendor_ruby/phusion_passenger/request_handler/thread_handler.rb:142:inaccept_and_process_next_request'
App 1013 stderr: from /usr/lib/ruby/vendor_ruby/phusion_passenger/request_handler/thread_handler.rb:110:in main_loop' App 1013 stderr: from /usr/lib/ruby/vendor_ruby/phusion_passenger/request_handler.rb:448:inblock (3 levels) in start_threads'

can it be related with https://jbox-web.github.io/redmine_git_hosting/configuration/troubleshooting/#hook-errors-while-pushing-over-https ?

Unfortunately, no. Those are already set as described there.
Besides, I don't think the request even gets that far because of the
exception.

Any ideas / suggestions / fix-es would be appreciated.
@n-rodriguez This is a great plug in and is really mission critical for me at the moment. A big set up is depending (and currently not working) because of this issue. I'd really appreciate your help on this.
Let's solve the issue and test that donation button if it's working :)

@n-rodriguez This is a great plug in and is really mission critical for me at the moment. A big set up is depending (and currently not working) because of this issue.

I understand your stress and the emergency of your case but I'm very busy this time :
I've also a business to run and these days it's the first priority.

@n-rodriguez I fully understand and appreciate that. Hence my offer of making fixing the bug be worth your while.
Based on the call stack, I expect it to be a pretty quick fix for anyone familiar with the code and really hope you'd find the time to help me out.

I believe I have solved it. It seems to be working now.
Maybe you can just confirm the ramifications of my fix, am I braking something else, since this has been my first intervention in a ruby code :)
There are a couple of popen calls in the file mentioned in the stack.
Based on the documentation on different ruby versions and expected parameters, I removed the popen_env parameter.
Did a couple of tests now, seems to be working.

@BAndonovski : actually the issue is your Ruby version :
http://ruby-doc.org//core-1.9.3/IO.html#method-c-popen
http://ruby-doc.org//core-2.1.0/IO.html#method-c-popen
Support of Ruby 1.9.x has ended so I highly recommend you to upgrade to Ruby 2.1 or 2.0.0.

No more need to edit files. Fixed in commit https://github.com/jbox-web/redmine_git_hosting/commit/73c4d150572b6b29182043b88814d847f930da30 (the compatibility patch will be removed with Debian Jessie release)


Can't send an email in the app

** Expected behavior: **
Send email of any order status
** Actual behavior: **
does not send, and already configure, and send a test message and everything is correct
** Play the steps: **
in setting --- email - configuration I have everything correct.
I configure the notification in each state but it does not send it.
Version:
last version.
Additional Information:
I already read this Issues, and it gives me almost the same problem and I have no extensions installed, other than those that are required for the template to work
https://github.com/tastyigniter/TastyIgniter/issues/537

I already read this isuues .
https://github.com/tastyigniter/TastyIgniter/issues/719

Do you see any errors in System -> System logs?

Sorry for the delay, I'm not sure why its not working. I use postmark on our installs but we just use the smtp connection method for postmark - do you want to try that?
I know others have had issues with emails sending when using broadcast events, but you don't seem to be.

Could it be that I have to grant any permission? why not even the message test with the app log, and I already tried with postmark too

In /config/queue.php change the default queue from database to sync. Does that help?

I also have this problem - sending a test email does not work either. No errors anywhere from what I can see. SMTP worked before the latest version.

Did you try changing your queue.php setting?

Sorry, forgot to mention - I'm already using sync.

sorry for the delay, I did what you say, but try and just send the test mail

Its going to be impossible for us to move forward on this without further information and really an error trace. We're using laravel's mail features so its pretty battle hardened and unlikely to have issues like this.
My advice would be to look around the queue settings, and set to sync or database (if database make sure you have the artisan task set up to send the queue).
Do report back if you have an error stack or find the cause.

same here, test works, but nothing else


Docs update readme file for semaphore-stellar-docs

Docs update readme file for semaphore-stellar-docs
📝 Summary
This README file is updated to mention the boilerplate and SDK repository with links and context
🔗 Related Issues

Closes #9

🔄 Changes Made
I explained about the repositories boilerplate and SDK that were shared adding the URLs
Reference:
https://github.com/ZencypherSolutions/semaphore-stellar-boilerplate
https://github.com/ZencypherSolutions/semaphore-stellar-sdk
🧪 Testing
I tested with my github fork on desktop
🖼 Screenshots & Resources

✅ Self-Check for Contribution Requirements
Mark with an x all the checkboxes that apply (like [x]).

[x] Forked the repository and created a new branch with a meaningful name.
[x] Ensured that the content is clear and free of grammatical errors.
[x] Maintained consistency in tone and formatting throughout the document.
[x] Verified that all links work correctly and checked for typos before submitting the changes.

[x] Thoroughly tested changes, including unit tests if applicable.

💬 Comments
Any suggestion or feedback I will really appreciate it, thank you giving the opportunity

@evgongora Hello! PR ready with three last commits signed, let me know if I am missing something else.


Bad request

after put the token and use it, it say bad request

There is a new discord API version, so after that, bot throws bad request


Fix a Bootstrap conversion error and empty lines in forms

I noticed that there are a couple empty lines in forms on two pages in the Certificate Manager area, caused by using addInput instead of addGlobal to add hidden form inputs. This PR fixes them, along with all other such cases I could find throughout the GUI.
There's also a small logic error introduced during Bootstrap conversion, which is fixed as well.

[x] Redmine Issue: https://redmine.pfsense.org/issues/9449
[x] Ready for review

Done, I added the Redmine link to the PR description.
Should I generally assign a new issue to myself if I already made a PR or am about to?

You can leave the assignment blank, usually with a PR that would be set to whoever is testing it or merging it, or back to you if there are questions/problems that need additional development work.


Support publishing artifacts from a GH run with different artifact names

Charm and Image gh artifacts are generally stored with the following names

${CHARM_NAME}-charm
${CHARM_NAME}-images

If publishing for multiple architectures, it may be necessary for the same action run to publish multiple artifacts with different names for the same charm.
See this PR run
where the same charm creates multiple charm artifacts based on the support architectures.
When the publish workflow is called, it should pull the appropriate artifacts from the run.
The example PR run above has artifacts named k8s-arm64-charm and k8s-amd64-charm produced.  For the call to this workflow to complete, i will update the call to include the artifact-format input:
    with:
      channel: latest/edge
      working-directory: ${{ matrix.charm.path }}
      tag-prefix: ${{ matrix.charm.tagPrefix }}
      artifact-format: '${CHARM_NAME}-${{matrix.strategy.arch}}'

@cbartz and @arturo-seijas Hope you'll consider this or offer a better suggestion


[Bug]: Filebrowser template is broken

Description
When using filebrowser/filebrowser:latest docker image and the default config I'm getting 404 not found independent of the domain I use.
Using filebrowser/filebrowser:v2.28.0-amd64-s6 instead solves the issue for now, but that feels like a workaround.
Minimal Reproduction (if possible, example repository)

Create a new filebrowser resource with the default configuration
Observe the issue

Exception or Error
No errors are logged, everything looks fine.
Some observations:

Changing healthcheck port from 8080 to 80 somehow makes it return 502 Bad Gateway
Executing curl -f <IP_ADDRESS>:80 in "Execute Command" menu returns what seems like correct html for filebrowser

Version
v4.0.0-beta.297

@ershisan99 try this docker-compose.
https://github.com/iamEvanYT/coolify-stuff/blob/main/composes/filebrowser.yaml

changing SERVICE_FQDN_FILEBROWSER to SERVICE_FQDN_FILEBROWSER_80 fixed the issue for me.
services:
  filebrowser:
    image: filebrowser/filebrowser:latest
    environment:
-      - SERVICE_FQDN_FILEBROWSER
+      - SERVICE_FQDN_FILEBROWSER_80

...


docs: add conservation rules page

Describe how to use the conservation_rules module separately.

@Leongrim have a look at the conservation.ipynb notebook.


[WIP] parametrizing dns01 tests

Signed-off-by: Arsh Sharma<EMAIL_ADDRESS>
What this PR does / why we need it: Will parametrize the DNS01 tests so that they can be run on the infra created in cert-manager/test-infra
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
Release note:

NONE

/kind feature

Closing as stale, but please re-open if you have time to come back to this.


How to Upload images from the Nextjs backend API Route?

Hi Team,
I'm using Amplify Gen 2 for my NextJS project.
I have been searching through all the docs but didn't find any example on how to upload files that comes to the NextJS backend API route. I tried the "uploadData" function available from "aws-amplify/storage", but it only works in the frontend implementation and not in the backend because it doesn't have the Authenticator wrapper information at the backend. So my request throws "Unauthorized, Access Denied" error.
Here is my example route.ts code that throws the error:
import { uploadData } from "aws-amplify/storage";

export async function POST(req: Request) {
  try {
    const formData = await req.formData();
    const image = formData.get("image") as File | null;
    const prisma = await db();

    if (image) {
      const filename = image.name;
      const result = prisma.$transaction(async (tx) => {
        const result = await prisma.image.create({
          data: {
            name: image.name,
          },
        });
        await uploadData({
          data: image,
          path: `images/${filename}`,
        });
        return result;
      });
      return Response.json(
        { message: "Image uploaded", result },
        { status: 200 }
      );
    }
    return Response.json({ message: "No image provided" }, { status: 400 });
  } catch (error) {
    console.error(error);
    return Response.json({ error: "Internal server error" }, { status: 500 });
  }
}

The reason why I need to do this on the backend and not in the frontend is because I need to update the database at the same time as a transaction. So if the image upload goes wrong for some connectivity issue, the database update gets rolled back.
Can someone please help me to figure out the code? How can I authenticate the AWS image upload connection at the NextJS backend?

Hi @amalhub The Storage category uploadData API is currently not working on the server-side of a Next.js app, as this documentation lists. Could you open a feature request in the Amplify JS repository?

Hi @HuiSF,
Thanks for the response. It is very unfortunate that this feature is not available right now. It is a very essential feature to ensure proper data sync with the database and S3 content. Otherwise, occasionally the app ends up with orphan data in the S3 bucket.
Is there any other method or workaround I could implement to upload images from the backend API route until this feature becomes available?
PS: I opened the feature request: https://github.com/aws-amplify/amplify-js/issues/13636

@amalhub, left comments on the related issues linked above tied to the feature request.  We'll close this issue and ask you to follow #13636 for further updates on supporting the uploadData API within Storage for SSR usage.


Add client-side redirect from /training/overview.html to current training home

Fixes #2615

This change is

Review status: 0 of 1 files reviewed at latest revision, all discussions resolved, all commit checks successful.

Comments from Reviewable


colab result: Two legs are merged like wearing a dress   :-)

I'm experimenting on colab with different photos. This is my recent result:

You can see in the photos that the legs are spread out.

It seems that the cloth_smpl_link mode of digital_type failed in your case (which is used for the skirt case). you can close it by following steps:

openassets/configs/deploy.toml
change the value of digital_type to smpl (default value is cloth_smpl_link)
delete all results and rerun the code

Wow, problem fixed! Thank you so much.
I downloaded deploy.toml, modified it and transfered it back. It would be great if there's an option in the colab.

For some reason there's a black mark flashing around my left arm (right arm when I turn around) all the time:

I've tried the same reference video with other source images, with tight sleeves. The result was very clean.

The sleeves in your image are too wide compared to the body shape of the estimated SMPL model, so the deep network cannot be trained very well in the step of personalization, which causes the problem of "black mark".

I fixed the problem by modifying the sleeves smaller, thanks.
Another question, sometimes I get more "cloudy" edge than other even I was using the same input images:

Is there an parameter I can adjust?


Build Tower bug fix

Just Fixed a bug concerning tower placement.

@Hasakev it is intended because the first column has all the gap scanners that spawns the engineers


Problems in kkrt_ote

(1)	In iknp_ote.h, the path in see yacl/crypto-tools/rp.h should be yacl/crypto/tools/rp.h.
(2)	In line 48 of kkrt_ote.h, the annotation (1-out-of-2)    (1-out-of-n)  should be (1-out-of-2)    (1-out-of-2^n) .
(3)	In kkrt_ote.cc, it seems that the member batch_size_ of KkrtOtExtSender or  KkrtOtExtReceiver is not useful and can be deleted.

Thanks for your comment.

In iknp_ote.h, the path in see yacl/crypto-tools/rp.h should be yacl/crypto/tools/rp.h.

For question (1): Yes, it is a typos.

the annotation (1-out-of-2)    (1-out-of-n)  should be (1-out-of-2)    (1-out-of-2^n)

In the definition, n denotes the length of ROT or the number of KKRT OTE. Thus, I think it should be 1-out-of-N.
As described in KKRT 3.2 & 3.3, $\mathcal F((\mathbf q_j , s),r) = H(j || \mathbf q_j \otimes [ \mathcal{C}(r) \cdot s ] )$ where $(\mathbf q_j ,s )$ is PRF key, $r$ is the input of PRF or the input of pseudorandom code $\mathcal C$.
If we consider a pseudorandom code $\mathcal C: [N] \rightarrow \lbrace 0 , 1 \rbrace^t$, then it is appropriate to describe KKRT OTE as a 1-out-of-N OTE.
By the way, in our implementaion, pseudorandom code is defined as a function: $uint128 \rightarrow std::array⟨uint128, kKkrtWidth⟩$. It implies that $N = 2^{128}$.

it seems that the member batch_size_ of KkrtOtExtSender or  KkrtOtExtReceiver is not useful and can be deleted.

It seems that batch_size_ is the same as kBatchSize in kkrt_ote.cc.
But please don't remove them as we might support dynamic batch_size in the future work. :)

(4) In line 97 of kos_ote.cc, the annotation 3rd party (the rest bits): padding 1; may be wrong. It should be padding 0.
I have opened a PR for this.

Great!
In addition, there was a typo as 3rd party .... Would you mind to modify it to 3rd part .... :)


Redact sensitive informations like password in chart url

The chart name can also be an URL that contains basic authentication information. This information are printed out by helmfile. This PR tries to redact this information.
$ cat <<EOT >> helmfile.yaml
releases:
    - name: test
      chart<EMAIL_ADDRESS>EOT

$ helmfile template
> Templating release=test<EMAIL_ADDRESS>
With this patch the output looks like:
> Templating release=test<EMAIL_ADDRESS>

@dol Hey. Thanks for your contribution! This looks awesome, but we've recently moved to https://github.com/helmfile/helmfile/. Would you mind reopening this PR there?

@mumoshu Will do.


Fix #7828 add list/grid/tile views buttons to mw provider and entities

@miq-bot add_label ui, providers/hawkular, ui
@pilhuhn @karelhala @mtho11 fyi
@himdel @martinpovolny please review.

That is nice 👍


navbar doesn't change when logged in user goes to the log in page

Before the user logs in, the navbar is the before logged in navbar (with the register/login buttons).
After the user logs in, the navbar changes to the logged in navbar (with the logout buttons etc)
but if the user logs in and clicks on "back", user is brought back to login page but navbar is still the logged in navbar.

Backspace is not a logout. What should happen is when a user is logged in, attempting to go to the login page should redirect to main screen.


Bug squash Monday

[x] created by pulling wrong field (full user's name vs idir/username)
[x] drafts not waiting for context filters to load, i.e., it shows all data until you hit apply filters.
[x] plan trip page is still showing in web

[ ] fly to fade deletion bug


[FEATURE]: Append additional statements to migrations

Describe what you want
As a developer I want to customise migrations with some custom statements like PRAGMA journal_mode=WAL;

You can add this by generating a custom migration file: https://orm.drizzle.team/docs/kit-custom-migrations.


👷♂ Update fmt settings bracket_spacing = true

Description
Cuz OCD.
Checklist
Ensure you completed all of the steps below before submitting your pull request:

[x] Ran forge fmt?
[x] Ran forge snapshot?
[x] Ran forge test?

Pull requests with an incomplete checklist will be thrown out.

Nope nope... eww.
It should only affect the import brackets.


Add optional OSGI imports to scalatest.scala project file

This adds the resolution:=optional qualifier to imported packages that should be listed as optional in the artifact bundle META-INF/MANIFEST.MF file. If this is not done, you need to add maven (or sbt) dependencies for optional packages in artifacts that may never be used.

These changes are already in 3.0.x.


chore(deps): update common-dev-assets digest to 5c14bd5

This PR contains the following updates:

Package
Update
Change

common-dev-assets
digest
d20cae7 -> 5c14bd5

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

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

This PR has been generated by Renovate Bot.

/run pipeline

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

GitHub release
v4.1.0

Your semantic-release bot :package::rocket:


Backfill India IODC satellite imagery

Will run in GCP VM and push to the public dataset. Will wait for kbatch to be turned off before doing so. This takes priority over #237, but can probably be done in parallel.

In progress on VM. Expected to take ~2 weeks.

2024-04-29
Conversion is still ongoing.

This is now being done on a monthly basis. The starts of the data are available on the public bucket.

Nice! Is this going to be backfilled to the beginning of the IODC imagery? Or only moving forward?


doesnt work , unknown b3sum file , on arm 8 phone in proot debian via termux

hello ,
i am rust noob , otherwhere pro ..
i did rustup install nightly conplete
then did cargo install b3sum ( i think from readme i dunno , site says add
but i didnt know and did install , i just after fixing this will try add
.. the cargo installer did lots output and finally exited with b3sum installed
but i type b3sum it says unknown command
.. i found out its some special .. i dunno
the shell completes to .cargo/bin/b3sum but rest fails
root@localhost:~# file .cargo/bin/b3sum
.cargo/bin/b3sum: cannot open `.cargo/bin/b3sum' (No such file or directory)
root@localhost:~# ls -l .cargo/bin
ls: cannot access '.cargo/bin/b3sum': No such file or directory
total 198588
l??????????  ? ?    ?           ?            ? b3sum
-rwxr-xr-x. 13 root root 15624696 Feb 11 15:12 cargo
-rwxr-xr-x. 13 root root 15624696 Feb 11 15:12 cargo-clippy
-rwxr-xr-x. 13 root root 15624696 Feb 11 15:12 cargo-fmt
-rwxr-xr-x. 13 root root 15624696 Feb 11 15:12 cargo-miri
-rwxr-xr-x. 13 root root 15624696 Feb 11 15:12 clippy-driver
-rwxr-xr-x. 13 root root 15624696 Feb 11 15:12 rls
-rwxr-xr-x. 13 root root 15624696 Feb 11 15:12 rust-gdb
-rwxr-xr-x. 13 root root 15624696 Feb 11 15:12 rust-gdbgui
-rwxr-xr-x. 13 root root 15624696 Feb 11 15:12 rust-lldb
-rwxr-xr-x. 13 root root 15624696 Feb 11 15:12 rustc
-rwxr-xr-x. 13 root root 15624696 Feb 11 15:12 rustdoc
-rwxr-xr-x. 13 root root 15624696 Feb 11 15:12 rustfmt
-rwxr-xr-x. 13 root root 15624696 Feb 11 15:12 rustup
system is debian unstable / experimental on arm8 via proot ( noroot ) via termux terninal / system
greets

Hmm, getting a bunch of question marks from ls is very suspicious. I'm guessing the problem isn't with b3sum in particular, but with something about how your toolchain is installed. Could you try installing another Rust program (for example, cargo install ripgrep) and see if you get a similar result?

i tried and its same
last lines ..
Compiling grep v0.2.11
Finished release [optimized + debuginfo] target(s) in 2m 26s
Installing /root/.cargo/bin/rg
Installed package ripgrep v13.0.0 (executable rg)
root@localhost:~# rg
bash: rg: command not found
root@localhost:~#
i looked from outside the proot chroot
it fails also ..
im not sure , but maybe its simple cause it links ( maybe invalidly ) to some /tmp path ..
~ $ ls -l debian-fs/root/.cargo/bin
total 0
lrwxrwxrwx 1 u0_a268 u0_a268 111 Feb 11 16:23 b3sum -> /data/data/com.termux/files/home/debian-fs/tmp/cargo-installpF17KM/release/deps/.l2s.b3sum-8412ea923008c46a0001
lrwxrwxrwx 1 u0_a268 u0_a268  74 Feb 11 16:12 cargo -> /data/data/com.termux/files/home/debian-fs/root/.cargo/bin/.l2s.rustup0001
lrwxrwxrwx 1 u0_a268 u0_a268  74 Feb 11 16:12 cargo-clippy -> /data/data/com.termux/files/home/debian-fs/root/.cargo/bin/.l2s.rustup0001
lrwxrwxrwx 1 u0_a268 u0_a268  74 Feb 11 16:12 cargo-fmt -> /data/data/com.termux/files/home/debian-fs/root/.cargo/bin/.l2s.rustup0001
lrwxrwxrwx 1 u0_a268 u0_a268  74 Feb 11 16:12 cargo-miri -> /data/data/com.termux/files/home/debian-fs/root/.cargo/bin/.l2s.rustup0001
lrwxrwxrwx 1 u0_a268 u0_a268  74 Feb 11 16:12 clippy-driver -> /data/data/com.termux/files/home/debian-fs/root/.cargo/bin/.l2s.rustup0001
lrwxrwxrwx 1 u0_a268 u0_a268 108 Feb 12 08:22 rg -> /data/data/com.termux/files/home/debian-fs/tmp/cargo-installaMRU0H/release/deps/.l2s.rg-945c8d674ebab8cf0001
lrwxrwxrwx 1 u0_a268 u0_a268  74 Feb 11 16:12 rls -> /data/data/com.termux/files/home/debian-fs/root/.cargo/bin/.l2s.rustup0001
lrwxrwxrwx 1 u0_a268 u0_a268  74 Feb 11 16:12 rust-gdb -> /data/data/com.termux/files/home/debian-fs/root/.cargo/bin/.l2s.rustup0001
lrwxrwxrwx 1 u0_a268 u0_a268  74 Feb 11 16:12 rust-gdbgui -> /data/data/com.termux/files/home/debian-fs/root/.cargo/bin/.l2s.rustup0001
lrwxrwxrwx 1 u0_a268 u0_a268  74 Feb 11 16:12 rust-lldb -> /data/data/com.termux/files/home/debian-fs/root/.cargo/bin/.l2s.rustup0001
lrwxrwxrwx 1 u0_a268 u0_a268  74 Feb 11 16:12 rustc -> /data/data/com.termux/files/home/debian-fs/root/.cargo/bin/.l2s.rustup0001
lrwxrwxrwx 1 u0_a268 u0_a268  74 Feb 11 16:12 rustdoc -> /data/data/com.termux/files/home/debian-fs/root/.cargo/bin/.l2s.rustup0001
lrwxrwxrwx 1 u0_a268 u0_a268  74 Feb 11 16:12 rustfmt -> /data/data/com.termux/files/home/debian-fs/root/.cargo/bin/.l2s.rustup0001
lrwxrwxrwx 1 u0_a268 u0_a268  74 Feb 11 16:12 rustup -> /data/data/com.termux/files/home/debian-fs/root/.cargo/bin/.l2s.rustup0001
~ $ ls -l debian-fs/root/.cargo/bin/rg
lrwxrwxrwx 1 u0_a268 u0_a268 108 Feb 12 08:22 debian-fs/root/.cargo/bin/rg -> /data/data/com.termux/files/home/debian-fs/tmp/cargo-installaMRU0H/release/deps/.l2s.rg-945c8d674ebab8cf0001
~ $ debian-fs/root/.cargo/bin/rg
bash: debian-fs/root/.cargo/bin/rg: No such file or directory
~ $ ls -l /data/data/com.termux/files/home/debian-fs/tmp/cargo-installaMRU0H/release/deps/.l2s.rg-945c8d674ebab8cf0001
ls: cannot access '/data/data/com.termux/files/home/debian-fs/tmp/cargo-installaMRU0H/release/deps/.l2s.rg-945c8d674ebab8cf0001': No such file or directory
~ $ ls -l /data/data/com.termux/files/home/debian-fs/tmp/cargo-installaMRU0H/release/deps/
ls: cannot access '/data/data/com.termux/files/home/debian-fs/tmp/cargo-installaMRU0H/release/deps/': No such file or directory
.. btw thank you for your reply
.. greets

btw about rust , to update / nightly , do i have to run the rustup install line , or is there some update cmd

maybe link me to the rust mailing list ..

as i have not much rust exp , a mate suggested me
cargo build --release
which worked in the b3sum/ dir inside the git
and the outcome seems to work too
root@localhost:~/blake3.git/b3sum/target# cd release/                      root@localhost:~/blake3.git/b3sum/target/release# ls                       b3sum  b3sum.d  build  deps  examples  incremental                         root@localhost:~/blake3.git/b3sum/target/release# file b3sum               b3sum: ELF 64-bit LSB pie executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, BuildID[sha1]=9c9ae329080a7a223026fd7276b836e0d7cb0195, for GNU/Linux 3.7.0, with debug_info, not stripped

cargo install b3sum and cd BLAKE3/b3sum && cargo build --release should produce exactly the same binary, so I'm still not clear on exactly what could've been going wrong before. I will say that "debian unstable / experimental on arm8 via proot" sounds like a frightening combination :)
If you run into any more toolchain issues like this, I'd suggest asking folks on the Rust community Discord server. You can find a link here: https://www.rust-lang.org/community

ill try there
.. should the install cmd cp the b3sum bin into bin/ ? cause mine is only a sym link , to some in /tmp/

You can cp these executables wherever you like, yes. Normally I'd recommend adding ~/.cargo/bin to your $PATH, so that anything you cargo install is automatically runable in the terminal, but maybe that doesn't make sense until you figure out the ???????? problem that cargo install was giving you...


Add namespace for behavior

By polymer recommendation, our behaviors should be defined under their own namespace like so. Flagging it here with related PR #1
window.etoolsBehaviors = window.etoolsBehaviors || {};
  etoolsBehaviors.DynamicDialogBehavior = {

change already made ... closing issue


Unwanted blank space in RDF namespace creation

The RDF namespace (file: lib/namespaces.js, line: 3, link) is created by prepending a whitespace before the URL:
// Current
const rdf = namespace(' http://www.w3.org/1999/02/22-rdf-syntax-ns#')

Could you please remove that whitespace, as shown below?
// Wanted
const rdf = namespace('http://www.w3.org/1999/02/22-rdf-syntax-ns#')

Thanks

@floverde Thanks a lot for reporting and the PR!
Version changes in the package.json should be part of a separate version increase commit done by the npm version command. To avoid round trips, I created a separate PR with the same change and also some tests for the util functions. The fix is included in the v1.1.4 release.


Recursive DNS resolving?

I am trying to write a DNS server so that I can resolve to a custom tld. Currently, I have the non-recursive part working, but I cannot get the recursive part to work. Here is the code that I have so far:
package main

import (
        "fmt"
        "log"
        "strconv"

        "github.com/miekg/dns"
)

var records = map[string]string{
        "test.service.": "<IP_ADDRESS>",
}

func parseQuery(m *dns.Msg) {
        for _, q := range m.Question {
                switch q.Qtype {
                case dns.TypeA:
                        log.Printf("Query for %s\n", q.Name)
                        ip := records[q.Name]
                        if ip != "" {
                                rr, err := dns.NewRR(fmt.Sprintf("%s A %s", q.Name, ip))
                                if err == nil {
                                        m.Answer = append(m.Answer, rr)
                                }
                        }
                }
        }
}

func handleDnsRequest(w dns.ResponseWriter, r *dns.Msg) {
        m := new(dns.Msg)
        m.SetReply(r)
        m.Compress = false

        switch r.Opcode {
        case dns.OpcodeQuery:
                parseQuery(m)
        }

        w.WriteMsg(m)
}

func main() {
        // attach request handler func
        dns.HandleFunc("service.", handleDnsRequest)

        // start server
        port := 8080
        server := &dns.Server{Addr: ":" + strconv.Itoa(port), Net: "udp"}
        log.Printf("Starting at %d\n", port)
        err := server.ListenAndServe()
        defer server.Shutdown()
        if err != nil {
                log.Fatalf("Failed to start server: %s\n ", err.Error())
        }
}

To test it, I am using the dig command dig @<IP_ADDRESS> -p 8080 test.service and dig @<IP_ADDRESS> -p 8080 google.com. When I query the server for test.service, it works fine and resolves properly, but when I query the server for google.com, it fails to resolve. On each of the requests, there is a line that says that recursive resolving is not available.

; <<>> DiG 9.11.3-1ubuntu1.2-Ubuntu <<>> @<IP_ADDRESS> -p 8080 test.service
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4387
;; flags: qr rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;test.service.                  IN      A

;; ANSWER SECTION:
test.service.           3600    IN      A       <IP_ADDRESS>

;; Query time: 0 msec
;; SERVER: <IP_ADDRESS>#8080(<IP_ADDRESS>)
;; WHEN: Mon Oct 29 13:33:28 PDT 2018
;; MSG SIZE  rcvd: 58

How do I turn on recursive DNS resolving? I have not found some documentation that references it (here), but that is only for requesting to use recursive DNS. Am I forgetting to put something in or...?

Ok thanks. I ended up writing my own resolver, but this makes it far easier.


Uncaught Error: An error occurred. See https://github.com/styled-components/styled-components/blob/master/src/utils/errors.md#1 for more information. Additional arguments: [object Object]

Installed v4.1.2 and am receiving the following error in chrome console:

Uncaught Error: An error occurred. See https://github.com/styled-components/styled-components/blob/master/src/utils/errors.md#1 for more information. Additional arguments: [object Object]

Obviously not a very helpful message :(

Environment
System:

OS: macOS High Sierra 10.13.1
CPU: (4) x64 Intel(R) Core(TM) i5-5350U CPU @ 1.80GHz
Memory: 62.50 MB / 8.00 GB
Shell: 3.2.57 - /bin/bash

Binaries:

Node: 8.11.1 - ~/.nvm/versions/node/v8.11.1/bin/node
npm: 6.8.0 - ~/.nvm/versions/node/v8.11.1/bin/npm

Same here, had to downgrade

Make sure react-is is upgraded in your project to at least the same version # as react and react-dom

I'm having this same problem on ie11.
We currently have the following polyfills:
import 'react-app-polyfill/ie11';
import 'react-app-polyfill/stable';

some discussions on the same topic suggested we were missing import 'core-js';. Adding that throws our app into a frozen state we cant recover. Might not be related though... :/
relevant packages:
    "core-js": "^3.8.1",
    "react": "^17.0.1",
    "react-app-polyfill": "^2.0.0",
    "react-dom": "^17.0.1",
    "react-is": "^17.0.1",
    "react-scripts": "^4.0.1",
    "styled-components": "^5.2.1",

any ideas?

I was facing this same issue as well! It was mainly happening on production build, and I was unable to reproduce the bug locally!! I found no solution after several hours googling. At the end, I was running the production build locally and discovered I had circular dependent styled component on my split(lazy-load) pages and when one page was loading it didn’t have reference to the exported styled component defined on another page. It works locally because we have webpack running.
So the best practice is to move the styled components to a separate un-split file. Try not to export a styled component from a split page that needed reference on another page.


Uniquely unique

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

Thanks.

The failure here is due to clang-tools-extra and is getting beyond this point, going to merge this to improve master-next.


Consider improvide the re-usability of github actions workflow

dotnet sdk
dotnet tools
bonsai
check diffs
build and publish

Fixed by https://github.com/AllenNeuralDynamics/Aind.Behavior.GitHubActions


OH GOD

Thank you selggud, for bringing this issue to our attention.
Our team will do all that we can to fix it.


Update all dependencies in our main repositories

[ ] Upgrade GitHub-Actions to most current version (also do small refactorings)
[ ] Update to Node.JS 18.x
[ ] Update yarn to the most current version + add useful plugins (same config in all repositories)
[ ] Check whether there are unused or unnecessary dependencies which we can get rid of

[ ] Remove @types/jest for jest/globals?!

[ ] Update all dependencies to most current major version and fix issues regarding breaking changes. Examples:

[ ] https://github.com/serlo/database-layer/issues/343 (database-layer)
[ ] https://github.com/serlo/cloudflare-worker/issues/348

 Update dependencies unserer wichtigsten Repositories


Doing some stuff processing some stuff

It adds some best practices to the existing file but creates an entirely new script in Perl to parse genbank file, detect Cas(3,6,9) products and spit it out along with type. Hope it's OK, but please if it's not just tell me, I won't be able to do much stuff over the weekend but will be back to normal next Tuesday

In a few minutes I'm going to be trying to get Perl working and then try out this script. I might have some questions when I do.

In a few minutes, probably more like an hour.

If you need something more on that side, just assign me an issue, I'll try
to comply or help you anyhow.


Quick Start results in an empty page

Running the Quick Start (changed the port to 8090, otherwise same command), when I go to the http://<IP_ADDRESS>:8090, it produces a blank page. Note, <IP_ADDRESS> is my boot2docker ip and other containers work fine.
docker logs toran-proxy produces this:
Configure Toran Proxy...
Creating logs directories...
Installing Cron...
Loading Nginx vhosts...
Starting PHP-FPM...
Starting Cron...
Starting Nginx..

I don't have time to debug this, but I figured I'd bring it up.

Hello,
Please, share your docker command, I'll debug this ;).

Test new quick start please

yup, that fixed it, thanks!


Cannot move window via top bar or resize window after clicking the add account button

Describe the bug
After clicking the add account button, you cannot move the window using the top bar or resize using the edge of the application
To reproduce

Click and drag the window using the top bar, notice it works normally
Go to settings to add account, click add account
Close the window, close the settings

Screenshots
https://i.alazymeme.com/PeacefulUsualImage.gif
Chatterino version
commit a9b1af60d
Operating system
Windows 10

Can reproduce on Windows 10 1909

Can reproduce on Windows 10 1909

Still seeing this. Have to relaunch the app to reset it. Windows 10 21H2

same issue here, luckily closing and reopening fixes it

Still able to repo this:
Chatterino 2.3.5 (commit 81a62764c)
Windows 10 21H2

Still reproducible with commit 81a62764c
Windows 11

Still reproducible with commit 81a6276

That's why the issue is still open

Still reproducible with commit 81a6276

That's why the issue is still open edit: Also that commit is from April so even if we had fixed it you wouldn't have the fix.

This is fixed in https://github.com/Chatterino/chatterino2/pull/3636/commits/e269a75c1bd2e5d77e923c423711d49a1115c6a4 but was closed without being approved.
Using platform specific calls to lock Qt windows is less than ideal, and the original purpose is dubious, so just removing this macro qualified windows api call makes sense. The account panel is already "always on top" relative other chatterino windows while open, so being able to move or resize a window behind it doesn't seem like a benefit nor does it seem to pose any security risk to allow it to be moved afaik.
I might suggest disabling chat input while account panel is open to avoid accidental pastes to chat, but that is unrelated and not affected by this issue or fix.
Otherwise you probably have to fully redraw the main window to fix it; just calling ::SetWindowPos without the flags won't reset the permissions.

@derossm the reason why that PR wasn't merged is because it causes issues with chatterino's "Always On Top" setting when enabled.  If you wanna take a crack at fixing it be my guest - I haven't had the incentive to fix it as I don't use Windows.


Update gitter references to relevant discord channels

All products now have channels on the Consensys discord rather than gitter.  The 404 and footer templates include gitter.

@MadelineMurray can you paste the channel invite links here please?
Be careful to have permanent invites activated.

Teku - https://discord.gg/9mCVSY6
Orion - https://discord.gg/n8m22JK
EthSigner - https://discord.gg/5U9Jwp7
Eth2Signer - https://discord.gg/EA7WGzA


PSS Options GUI button on the main menu screen.  Check Comments

Use a small button (Ask me on discord if you don't understand). Recommended to use a wrench or smthing as the symbol, also we need a second button so that its centered, and not off-center

v0.0.3


Watch the window button showing ?

There is no close button in the popup that is displayed when clicking the YouTube view through the extended menu for each video. First of all, you can quit with the close button on the task bar. We will fix this issue for the next version.

The issue has been fixed and will be distributed to the next version.


Hover Issue

Hi Guys
https://kdl5bv3zorr5rv8c-24880840813.shopifypreview.com/products/banana-bread
The zoom is implemented on the product slider. However, it only seems to work when clicked? On the demos it was working by hovering.
Also, on mobile it doesn't seem to scroll
Thanks,
Rolen

@rolenzian648   make magnify css important or Disable  the slider hover and touch on slider working fine magnify I used on Shopify debt theme  all working fine
also, load the magnify.mobile.js


feat: Add Backup Format 3 Protobuf Schema

This adds the Protobuf schema for the version 3 backup format. Protobuf is going to enable us to statically verify backward and forward compatibility of the schema, and thus allow us to add fields without introducing a new version in the future. Protobuf uses a universal C extension for their dynamic languages, resulting in a massive speed-up. This is available starting with Protobuf 20, we thus will need to upgrade Protobuf to actually make use of this.

I didn't spot any issues with the backup format schema, but I think it should go in only with first implementation. Do you really want this to go in now before the implementation?

Yes. First, I don't want to have massive patches, but rather small ones that are easy to review. Second, having the Protobuf definition in master is what is going to allow us to add the breaking checks.

I'd propose the implementation to be done in a feature branch.

Why the complexity? We can implement it without affecting anything else. There is not even a need for feature flags or anything.

I think it would be nice to some reasoning about why we are inventing our own format here over Kafka's internal RecordBatch. A RecordBatch already seems to contain the same data, including headers, and has checksumming. Additionally, using RecordBatch it seems we would be available to directly stream data from files into Kafka without intermediate processing, possibly enabling speeding up the recovery process further?

I think it would be nice to some reasoning about why we are inventing our own format here over Kafka's internal RecordBatch. A RecordBatch already seems to contain the same data, including headers, and has checksumming. Additionally, using RecordBatch it seems we would be available to directly stream data from files into Kafka without intermediate processing, possibly enabling speeding up the recovery process further?

I raised this idea internally, we had a few discussions around it, and ultimately the idea was rejected on these grounds:

It's probably much more feasible in terms of existing tooling to implement the custom protobuf schema of this PR.
The proposed idea in this PR is probably fast enough.
It's unclear whether a full RecordBatch (at least all fields covered by checksum) can actually be produced at backup-time. If we can't, the idea is more or less useless.
OTOH, nothing would prevent us from revisiting this in the future, if our performance needs would surprisingly not be met by V3.

This has been superseded by #584.


remove onLoad from README.md

Removed the onLoad preference function as this doesn't work anymore with the new IPC serialization

Closes #40