Issue #8025. Ignoring HEADER and DATA frames for streams that may have existed in the past.

Motivation:
Correctly ignore frames that come in after a RST_STREAM is sent.
Modification:
Ignoring frames that are for a stream that may have existed in the past instead of throwing an exception.
Result:
Fixes #8025.

This is https://github.com/netty/netty/pull/8028 with followup cleanup... Sorry had to close the original PR to make progress :/

I would love to finally pull this in...

iirc, this work was spawned by https://github.com/grpc/grpc-java/issues/3548 which is basically some log entries that looks spooky but in reality are expected in the case of stream resets. It's been a while, but IMO, why can't we just decrease the log message to debug? I don't see the harm in sending additional RST frames since this isn't expected to be that expensive or common.

cc
Alluxio worker keep output this stream error warning

/cc @ejona86

@ejona86 WDYT ?

@ejona86 any thoughts ?

Reducing the log level sounds fine to me. But this is also like the 4-5th time we've "fixed" the logic surrounding this case, which means I'm happy if someone is able to spend the time to think seriously about it.
But yeah, I would just reduce the log level, especially given how the log messages I've seen have been triggered.

We see these being logged by Netty, almost certainly in Http2FrameCodec.onHttp2UnknownStreamError, and they 'are definitely spooky to see for our HTTP/2 users.

@bryce-anderson may want to do a PR to "fix" this ?

I can take a look, though it may be a few days. I don't recall what this PR does, but from the comments it seems like a reasonable approach as well.

@bryce-anderson that's fine :)

Even with log level adjusted this PR may still make sense to pull in... @ejona86 @bryce-anderson @mosesn @carl-mastrangelo @trustin WDYT ?

@bryce-anderson any updates related to a patch for the logging ?

Not yet, hoping to get to it this week. Sorry for the delay. With regard to
this change, it looks sound although I'm on the fence as to whether it's
worth the extra code. Perhaps someone else has a strong opinion one way or
the other.
On Mon, Nov 18, 2019 at 12:53 PM Norman Maurer<EMAIL_ADDRESS>wrote:

@bryce-anderson https://github.com/bryce-anderson any updates related
to a patch for the logging ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/netty/netty/pull/9402?email_source=notifications&email_token=AAWP3GRWYZTY3YJ2NY4BSOLQULXFLA5CNFSM4IHDAO7KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEELWKXY#issuecomment-555181407,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAWP3GWUOP3ZVJNGAWGNOWDQULXFLANCNFSM4IHDAO7A
.

@normanmaurer, I was thinking about this patch over the weekend and something came to mind that is all but certainly not worth the effort. 😄 What if we kept the streams that have been reset around in a terminal CLOSED state for a duration. That would keep a marker around for a bit and after a reasonable time frame (and 'reasonable' is probably the sticking point of this idea) we evict them from the Http2Connection.

lets just close this for now

Was a fix deployed for this ? At least for the logger ? Because this is a real issue for us.

Yes and it will be Part of the next release

Am 01.12.2019 um 20:23 schrieb Rigner<EMAIL_ADDRESS>
Was a fix deployed for this ? At least for the logger ? Because this is a real issue for us.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or unsubscribe.

When is the release or has it already happened? I am circling around in a loop between links on this thread and links on the page it navigates to, ending back here.

@bhavsi yes it was released as part of 4.1.44.Final as stated in the original issue


[Doc]Improve the geolocation documentation.

In geolocation documentation [1] an example is given only for the MySQL. It is better to add examples for the other databases like MsSQL, Oracle, IBM DB2, PostgreSQL as well.
[1] https://docs.wso2.com/display/AM220/Configuring+Geolocation+Based+Statistics

invalid due to analytics revamp in latest release.


Change back to string format and only stdout with evalResult

Use plain text as console stdout, and log data logging with fmt.Println

example
INFO[0006] started handling request                      method=POST remote="<IP_ADDRESS>:58344" request=/api/v1/evaluation
{"FlagEvalResult":{"evalContext":{"enableDebug":true,"entityContext":{"state":"NY"},"entityID":"127","entityType":"user","flagID":2},"evalDebugLog":{"segmentDebugLogs":[{"msg":"matched all constraints. rollout yes. {BucketNum:807 DistributionArray:{VariantIDs:[4] PercentsAccumulated:[1000]} VariantID:4 RolloutPercent:88}","segmentID":2}]},"flagID":2,"segmentID":2,"timestamp":"2017-10-28T00:25:59Z","variantAttachment":{"color":"simple-blue"},"variantID":4,"variantKey":"blue"}}


[WIP] feat: added automatic fetching/importing of IPFS CID/URLs

Description
Added automatic fetching/importing of IPFS URLs to the Player.
An IPFS v0 or v1 CID or URL (such as ipfs://<CID>, https://<CID>.ipfs.dweb.link/ or https://cloudflare-ipfs.com/ipfs/<CID>, but cannot be a directory) can be passed as the src or playbackID to the Player, and it will automatically detect if it is a valid CID and attempt to fetch the playback info for the CID. If the API does not have an Asset with the corresponding CID, the Player will automatically attempt to import the CID from IPFS, and then play the transcoded content back.

This shouldn't have been merged. The build is broken in main now

Can we not demo from the preview URL?


jumpy highlight (hold shift) feature request

Hi, was thinking it would be nice to have a "this is where your cursor is now, and now jump and highlight to this other spot"
So, jumpy while holding shift.
Looks like this repo hasn’t been updated in a while, but I thought it’s worth a shot to ask :)

@setek By "highlight", did you mean select? If so, you can try this extension, it supports Jumping/Selecting to the Start/End of a word.

@setek By "highlight", did you mean select? If so, you can try this extension, it supports Jumping/Selecting to the Start/End of a word.

I just get an error every time I try to use that extension

But yes, I did want to "be in  position, jump and select to  position" that's exactly the functionality I want

@setek I'm using the latest version without any issues, can you tell me a bit more about your setup?

Are other extensions disabled? Y/N
OS:
VSCode Version:
Jump Version:

@setek I just tested on several macs and windows PCs, couldn't reproduce your issue, does the issue persist after reinstallation?

@setek I just tested on several macs and windows PCs, couldn't reproduce your issue, does the issue persist after reinstalling the extension?

@setek I'm using the latest version without any issues, can you tell me a bit more about your setup?
* Are other extensions disabled? Y/N

Hi! So I did try it again and yeah, it works now! Very cool, thank you!

@setek Please give it a five stars rating if you enjoyed it ;).

@setek Please consider giving a five stars rating if you enjoyed it ;).

@setek Thanks for your kind review! After reading your comment, I found it's a bit hard to filter out Jump commands in the "Keyboard Shortcuts" editor, so in v0.7.0, I changed the command ID prefix from jump to jump-extension, you might need to update the keybindings after upgrading, cheers!


Can you index arbitrary, non unique attributes?

Hi,
It doesn't appear that your able to add attributes that are non-unique as an index. Is this correct, and is there a workaround for search purposes? (ie finding all records that have attribute x = value y)
Many thanks! 😄

@tyronedougherty, @Ryanc1256 Hi ya'll we are further cleaning up Sails issues by closing older ones. Let us know if you think this needs to be reopened.


Mattermost-desktop (via .deb package) utilizes an executable stack.

I confirm (by marking "x" in the [ ] below: [x]):

[X] This is not a troubleshooting question. Troubleshooting questions go here: http://www.mattermost.org/troubleshoot/.
[X] This doesn't reproduce on web browsers (such as in Chrome). If it does, issue reports go to the Mattermost Server repository.
[X] I have read contributing guidelines.

Summary

The public beta Linux package (.deb) installs a version of mattermost-desktop that marks the stack and the heap as Read,Write,eXecute and allocates ~ 230 RWX pages.
Steps to reproduce

Download Ubuntu 18.04 and install it into a VM
Download and install the latest mattermost-desktop AMD64 .deb package (https://releases.mattermost.com/desktop/4.0.1/mattermost-desktop-4.0.1-linux-amd64.deb)
Launch the mattermost-desktop application
Grep the process maps for mattermost-desktop and look at the permissions for the stack.
4a. Command: for i in $(pidof mattermost-desktop); do cat /proc/$i/maps | grep stack; done

Expected behavior
The output from the command in 4a should show that the stack is marked as RWX (Read,Write,eXecute)
Observed behavior
Mattermost-desktop running with an executable stack
test@test-virtual-machine:~$ for i in $(pidof mattermost-desktop); do cat /proc/$i/maps | grep stack; done
7ffecf983000-7ffecf9a4000 rwxp 00000000 00:00 0                          [stack]

Rough estimate of how many RWX allocations there are within the mattermost-desktop process.
test@test-virtual-machine:~$ for i in $(pidof mattermost-desktop); do cat /proc/$i/maps | grep rwxp | wc -l; done
242

Confirmed. As written at https://github.com/electron/electron/issues/11628, it's fixed in Electron 1.8.3. Our upcoming v4.1 uses Electron 1.8.4, so it would fix this problem.
@b1ack0wl Please let me confirm. Actually v4.1.0-rc3's stack is listed as rw-p. Is it the expected behavior in this issue?

My apologies for the delay, but yes! The stack and heap should be marked as rw-p. Thank you so much for following up with a solid action plan! I'll be closing this ticket to reduce ticket volume. :)
Thanks again!!

Now v4.1.0 is released, so I close this. Thanks!


⚠ Bofrost.fr has degraded performance

In d676d0f, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 837 ms

Resolved: Bofrost.fr performance has improved in 676c15d after 6 minutes.


addDataInFields: Underscorejs is undefined at (only) the time of instantiation

Underscorejs is not there at the time of instantiation (why? I don't know). It would be, when it is actually being used later (some events trigger the use of it). Could you have a look? I suggest a fix further below, that I agree might be a workaround.
Required Information

[ <IP_ADDRESS> ] AEM Version, including Service Packs, Cumulative Fix Packs, etc: _______
[ 5.0.4 ] ACS AEM Commons Version: _____
[ yes ] Reproducible on Latest? yes/no

Expected Behavior
Underscorejs should be assigned and later be used.
Actual Behavior
At the time of assignement, underscorejs is not there... later, when being used, it would be there! In our case, it could be fixed, if
var _ = window._;

would be removed and direct window access would be used instead.
So, where _.isEmpty() is being used, just use it like window._.isEmpty(). That would fix it for us, I have no idea where the problem originates from though.
Disclaimer: I am not at all familiar with AEM and I have little to no experience with it.
Steps to Reproduce
Uncaught TypeError: Cannot read property 'isEmpty' of undefined
    at instanceGenerator.addDataInFields (composite-multifield.54336e358380bcd5bb63ac5a001c8947.js:519)
    at HTMLDocument.<anonymous> (composite-multifield.54336e358380bcd5bb63ac5a001c8947.js:829)
    at HTMLDocument.dispatch (jquery.0811b5e7037ada110b591bbd86240386.js:5227)
    at HTMLDocument.elemData.handle (jquery.0811b5e7037ada110b591bbd86240386.js:4879)
    at Object.trigger (jquery.0811b5e7037ada110b591bbd86240386.js:5131)
    at HTMLDocument.<anonymous> (jquery.0811b5e7037ada110b591bbd86240386.js:5861)
    at Function.each (jquery.0811b5e7037ada110b591bbd86240386.js:371)
    at jQuery.fn.init.each (jquery.0811b5e7037ada110b591bbd86240386.js:137)
    at jQuery.fn.init.trigger (jquery.0811b5e7037ada110b591bbd86240386.js:5860)
    at Object.<anonymous> (core.395eb5cc065b51b27ae2833483a01095.js:657)

Links
Needs company login, so won't work.

Hi @davidjgonzalez, Is this issue fixed? No fixed version is mentioned here.
I'm getting the same issue after the AEM service pack upgrade.
AEM version: 6.5.11 & ACS Commons version: 4.3.2

Can you verify how youre proxying this in? Assuming youre hooking into the provided [1] clientlib category, that establishes a dependency on underscore.
Can you also check that on the HTML document that loads this (i think probably the Dialog doc, assume you're using it in a regular dialog?) that there is a script include to the underscore dep?
Also, any idea if this just started happening w/ SP11? (did it work for you in previous SP's?)
[1] https://github.com/Adobe-Consulting-Services/acs-aem-commons/blob/master/ui.apps/src/main/content/jcr_root/apps/acs-commons/touchui-widgets/composite-multifield/.content.xml

Hi @davidjgonzalez, thanks for the quick reply.
1st I want to reply to your last question :) - Yes, everything was fine on 6.5.6, the 'underscore' error started as we upgraded to 6.5.11 (service pack 11).
After deep analysis, here are a few points
1- we are not hooking composite-multifield directly/indirectly in our codebase. It is getting added in authoring mode somehow. maybe through 'cq.authoring.dialog' clientLibs in edit mode.
2- Error is coming because ACS Commons is using 'underscore' dependency which is removed from AEM from 6.5.10 onward I think.
Reference 1: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/after-updating-aem-6-5-10-underscore-dependency-is-not-loading/td-p/426336
Reference 2 (search for lodash): https://experienceleague.adobe.com/docs/experience-manager-65/release-notes/deprecated-removed-features.html?lang=en
Solution: As of now we are going to change the "underscore" to "lodash.underscore" in our codebase wherever we have used it. And also I'm going to change manually in ACS Commons 'composite-multifield' as of now until we get an update https://github.com/Adobe-Consulting-Services/acs-aem-commons/blob/master/ui.apps/src/main/content/jcr_root/apps/acs-commons/touchui-widgets/composite-multifield/.content.xml

If you agree, I'll create a new ticket for this issue?

@elfrenqv not yet.
I think underscore support was removed unplanned. I see issues in AEM service pack 11 code also under content fragment model create functionality.

I see this as closed, but I am not clear regarding the solution, any insights? Thanks.


[Bug]: NetGear graceful close doesn't work for pattern=2

Description
Hi, it seems that the underlying threads for the NetGear gears never join when an attempt is done to gracefully close the NetGear. This is for pub/sub pattern.
Example (with FastAPI) provided.
from fastapi import FastAPI
from vidgear.gears import NetGear
import threading

app = FastAPI()

gears = []

@app.get("/")
async def root():
    return {"message": "Hello World"}

@app.get("/hello/{name}")
async def say_hello(name: str):
    return {"message": f"Hello {name}"}

@app.on_event("startup")
async def startup():

    gear = NetGear(
        address="*",
        port="5555",
        protocol="tcp",
        pattern=2,
        receive_mode=True,
        logging=True
    )
    gears.append(gear)

@app.on_event("shutdown")
async def shutdown():

    for t in threading.enumerate():
        if t.is_alive() and t != threading.current_thread():
            print(f"background thread {t.name}:{t.ident} is still running")

    for gear in gears:
        gear.close()

This results in the following log trace:
INFO:     Uvicorn running on http://<IP_ADDRESS>:8003 (Press CTRL+C to quit)
INFO:     Started reloader process [21484] using WatchFiles
INFO:     Started server process [32944]
INFO:     Waiting for application startup.
18:54:33 ::    Helper     ::   INFO   :: Running VidGear Version: 0.3.0
18:54:33 ::    NetGear    ::  DEBUG   :: Threaded Queue Mode is enabled by default for this connection.
18:54:33 ::    NetGear    ::  DEBUG   :: Successfully Binded to address: tcp://*:5558 with pattern: 2.
18:54:33 ::    NetGear    ::  DEBUG   :: JPEG Frame-Compression is activated for this connection with Colorspace:`BGR`, Quality:`90`%, Fastdct:`enabled`, and Fastupsample:`disabled`.
18:54:33 ::    NetGear    ::  DEBUG   :: Multi-threaded Receive Mode is successfully enabled.
18:54:33 ::    NetGear    ::  DEBUG   :: Unique System ID is 48DS1MMQ.
18:54:33 ::    NetGear    ::  DEBUG   :: Receive Mode is now activated.
INFO:     Application startup complete.
INFO:     Shutting down
background thread NetGear:19236 is still running
INFO:     Waiting for application shutdown.
18:54:42 ::    NetGear    ::  DEBUG   :: Terminating various Receive Mode Processes.

It seems that the 'graceful' close function never gets passed this "Terminating various Receive Mode Processes" step.
Could it be because the close function tries to join the background threads but eternally waits for them to finish?
Issue Checklist

[X] I have searched open or closed issues for my problem and found nothing related or helpful.
[X] I have read the Documentation and found nothing related to my problem.
[X] I've read the Issue Guidelines and wholeheartedly agree.

Expected behaviour
I would expect that the close function continues to terminate the threads and sockets.
Actual behaviour
The termination never happens completely.
We need to kill the python process to stop the application.
Steps to reproduce
from fastapi import FastAPI
from vidgear.gears import NetGear
import threading

app = FastAPI()

gears = []

@app.get("/")
async def root():
    return {"message": "Hello World"}

@app.get("/hello/{name}")
async def say_hello(name: str):
    return {"message": f"Hello {name}"}

@app.on_event("startup")
async def startup():

    gear = NetGear(
        address="*",
        port="5555",
        protocol="tcp",
        pattern=2,
        receive_mode=True,
        logging=True
    )
    gears.append(gear)

@app.on_event("shutdown")
async def shutdown():

    for t in threading.enumerate():
        if t.is_alive() and t != threading.current_thread():
            print(f"background thread {t.name}:{t.ident} is still running")

    for gear in gears:
        gear.close()

Terminal log output
INFO:     Uvicorn running on http://<IP_ADDRESS>:8003 (Press CTRL+C to quit)
INFO:     Started reloader process [21484] using WatchFiles
INFO:     Started server process [32944]
INFO:     Waiting for application startup.
18:54:33 ::    Helper     ::   INFO   :: Running VidGear Version: 0.3.0
18:54:33 ::    NetGear    ::  DEBUG   :: Threaded Queue Mode is enabled by default for this connection.
18:54:33 ::    NetGear    ::  DEBUG   :: Successfully Binded to address: tcp://*:5558 with pattern: 2.
18:54:33 ::    NetGear    ::  DEBUG   :: JPEG Frame-Compression is activated for this connection with Colorspace:`BGR`, Quality:`90`%, Fastdct:`enabled`, and Fastupsample:`disabled`.
18:54:33 ::    NetGear    ::  DEBUG   :: Multi-threaded Receive Mode is successfully enabled.
18:54:33 ::    NetGear    ::  DEBUG   :: Unique System ID is 48DS1MMQ.
18:54:33 ::    NetGear    ::  DEBUG   :: Receive Mode is now activated.
INFO:     Application startup complete.
INFO:     Shutting down
background thread NetGear:19236 is still running
INFO:     Waiting for application shutdown.
18:54:42 ::    NetGear    ::  DEBUG   :: Terminating various Receive Mode Processes.

Python Code(Optional)
from fastapi import FastAPI
from vidgear.gears import NetGear
import threading

app = FastAPI()

gears = []

@app.get("/")
async def root():
    return {"message": "Hello World"}

@app.get("/hello/{name}")
async def say_hello(name: str):
    return {"message": f"Hello {name}"}

@app.on_event("startup")
async def startup():

    gear = NetGear(
        address="*",
        port="5555",
        protocol="tcp",
        pattern=2,
        receive_mode=True,
        logging=True
    )
    gears.append(gear)

@app.on_event("shutdown")
async def shutdown():

    for t in threading.enumerate():
        if t.is_alive() and t != threading.current_thread():
            print(f"background thread {t.name}:{t.ident} is still running")

    for gear in gears:
        gear.close()

VidGear Version
0.3.0
Python version
3.8
OpenCV version
<IP_ADDRESS>
Operating System version
Windows
Any other Relevant Information?
Also tested on python 3.6, jetpack 4.6.1 (Jetson) and vidgear 2.4.0

@brysd This is not a bug in vidgear but how ZMQ works. You need the server running to exit the client properly, since recv_json() is a blocking function which expects the connection to be made at some point of time. However I can add a flag that kill this process on close() forecfully.

Successfully resolved and merged in commit https://github.com/abhiTronix/vidgear/commit/3c0dd5d482e5eba37b41a5a2422f65f856e0f27c

@abhiTronix You added kill for the NetGear.close, but should not kill added for the CamGear.close() too? On Ctrl + C the process hangs forever in the background.

@AIGeneratedUsername I don't think server side is ever frozen and this problem only exist on receiver end, even you code is using receiver mode(receive_mode=True). Secondly, CamGear do provide THREAD_TIMEOUT to kill thread on a timeout. Thirdly,  kill for the NetGear.close is not the solution I provided, It is only the last resort when nothing is woking. You need to instead use subscriber_timeout optional flag in NetGear API to gracefully timeout if no server is able to connect.
For refrence:
subscriber_timeout(integer): Similar to request_timeout, this internal attribute also controls the timeout value (in seconds) but for non-synchronous zmq.PUB/zmq.SUB pattern in compression mode, after which the Client(Subscriber) exit itself with Nonetype value if it's unable to get any response from the socket. It's value can anything greater than 0, and its disabled by default (meaning the client will wait forever for response).


fix table headers

Based on the json2md documentation tables needs the headers element

Thank you @dmouse for your help. I just published v1.5.0 with your change


Allow adding request headers to ol.layer.VectorTile requests

Can we please have an easy way to add headers to a vector tile request. Passing authentication token using Header is a common use case.

You can configure the VectorTile source with a custom tileLoadFunction. Is that easy enough? See http://openlayers.org/en/master/apidoc/module-ol_source_VectorTile.html:
function(tile, url) {
  tile.setLoader(function() {
    var data = // ... fetch data
    var format = tile.getFormat();
    tile.setProjection(format.readProjection(data));
    tile.setFeatures(format.readFeatures(data, {
      // featureProjection is not required for ol/format/MVT
      featureProjection: map.getView().getProjection()
    }));
    // the line below is only required for ol/format/MVT
    tile.setExtent(format.getLastExtent());
  };
});

No response from issue creator, closing.

there is example code on the right side, if you scroll a bit down: https://openlayers.org/en/master/apidoc/module-ol_source_VectorTile.html
It uses fetch, and this describes how to add headers using fetch:
https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API/Using_Fetch#supplying_request_options
also: https://developer.mozilla.org/en-US/docs/Web/API/fetch


Update src address match logs to use the Mac::Address:ToString()

Codecov Report

Merging #1548 into master will decrease coverage by 1.77%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1548      +/-   ##
==========================================
- Coverage   71.06%   69.29%   -1.78%
==========================================
  Files         145      149       +4
  Lines       18223    19965    +1742
  Branches     2215     2429     +214
==========================================
+ Hits        12950    13834     +884
- Misses       4441     5216     +775
- Partials      832      915      +83

Impacted Files
Coverage Δ

src/core/mac/mac.cpp
79.91% <ø> (+1.17%)
:arrow_up:

src/core/thread/mle_router.cpp
79.27% <0%> (-0.11%)
:arrow_down:

examples/drivers/windows/ottmp/hdlc.cpp
77.77% <0%> (ø)

src/ncp/ncp_base.hpp
0% <0%> (ø)

src/ncp/ncp_base.cpp
36.56% <0%> (ø)

src/ncp/ncp_uart.cpp
75.67% <0%> (ø)

src/core/thread/mesh_forwarder.cpp
74.27% <0%> (+0.21%)
:arrow_up:

src/core/thread/network_data_leader_ftd.cpp
68.22% <0%> (+0.23%)
:arrow_up:

src/core/thread/lowpan.cpp
93.01% <0%> (+0.71%)
:arrow_up:

src/core/thread/network_data.cpp
87.64% <0%> (+0.74%)
:arrow_up:

... and 12 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 27ddb2d...cc0245d. Read the comment docs.


Work towards "Django inspired" web api

"meta" json wrapper around subsequent URL to vep_annotation, pfam_annotation, pdb_annotation, etc.

@n1zea144 just looking through the open issues. What is this exactly?

I had HATEOAS in mind when I suggest that.  Provide JSON which includes links back to genome nexus to get subsequent data instead of combining it all into a single JSON.

@n1zea144 Ok thanks! Seems Swagger v3 has that: https://blog.readme.io/an-example-filled-guide-to-swagger-3-2/

I guess with GraphQL you wouldn't use that, since you would send one object with all the data you want

I'm going to close this for now, since we sort of do this by allowing fields parameter to get the data that you want. Not as neat as HATEOAS but gets the job done. We can maybe revisit this for version 2 of the API


start_test produces weird error

Main file in ../src/
use Chrest,
    ChrestRouter;

config const API_HOST: string,
             API_PORT: int;

proc main() {
  var srv = new Chrest(API_HOST, API_PORT);
  srv.Listen();
  srv.Close();
}

And the test file in ../test/
use Apiyatollah,
    Curl,
    Spawn;

var sub = spawn(["..bin/apiyatollah"], stdout=PIPE);

produces this error
In file included from /var/folders/g5/4zwyfk513hd94tjs1fm5mdq00000gn/T//chpl-buddha-7252.deleteme/_main.c:2:
In file included from /var/folders/g5/4zwyfk513hd94tjs1fm5mdq00000gn/T//chpl-buddha-7252.deleteme/chpl__header.h:11:
/Users/buddha/github/buddha314/chrest/src/chrest.h:28:5: error: no previous prototype for function 'get_port_from_request' [-Werror,-Wmissing-prototypes]
int get_port_from_request(){
    ^
1 error generated.

This was originally filed in the wrong repo: https://github.com/marcoscleison/chapel-http/issues/1

This issue is related with some files utils coded in C. I removed the files because I can everything in Chapel.
I pushed it now. Please test the server example:
https://github.com/marcoscleison/chrest/blob/27a57f66f4f8590e8cd48a57e4247ed4fa383041/examples/srv.chpl#L126
With the client example:
https://github.com/marcoscleison/chrest/blob/27a57f66f4f8590e8cd48a57e4247ed4fa383041/examples/cli.chpl#L19


Traverse/Terrestria compatibility lumberjack

What would need to be done to add compatibility for these 2 mods and the lumberjack class?
Currently the bonus tree chopping doesn't work on their trees.
Thanks for you time.

Probably should consider adding Cinderscapes to the list


V1 of Tauri

Migrate to Tauri version 1.0.
This allows to go to a stable version of Tauri and also to add the features related with the issue  https://github.com/capacitor-community/tauri/issues/2.
Version 1 was released on 2022/06/19 => Tauri v1.0

Migrate to Tauri version 1.0.
This allows to go to a stable version of Tauri and also to add the features related with the issue #2.
Version 1 was released on 2022/06/19 => Tauri v1.0

This repo seems no longer maintained. I refactor it to nawbc/capacitor-tauri

Migrate to Tauri version 1.0.
This allows to go to a stable version of Tauri and also to add the features related with the issue #2.
Version 1 was released on 2022/06/19 => Tauri v1.0

This repo seems no longer maintained. I refactor it to nawbc/capacitor-tauri

Stop use Capacitor, because Tauri 2 integrate Mobile too.


PN532 mraa_i2c_write() error with example script

Hi, I'm trying to use a PN532 RFID reader from deek-robot [http://www.aliexpress.com/store/product/MINI-PN532-NFC-RFID-Controller-Shield-for-Arduino/1178065_32213388605.html]  in i2c mode on a Galileo Gen 2 on yocto linux image with the included exemple that come with the library [https://github.com/intel-iot-devkit/upm/blob/master/examples/python/pn532.py] , but every time I get that error (See screenshot below) I posted on Intel Galileo forum about that, and Peter, a guy from intel answer me that he got the same issue and suggest me open an issue for the exemple script.

When i use te command i2cdetect -y -r 0 the RFID reader is reconized at the address 24 (whitch disapear when i unplug the reader) on the i2c-0 bus , So the bus seems to work or at least recognize the reader, but I'm unable to use it in the example script
I use the pinout :
A4 -> SDA
A5 -> SCL
pin 2 ->RESET
pin 3 -> IRQ
MRAA and UPM are at their lastest versions  :
3.8.7-yocto-standard
MRAA v1.2.1
UPM v0.7.2
Node 4.4.3
I tested the RFID reader on an arduino UNO with an adafruit_PN532 library exemple and it works fine with the same pinout.
FYI, that arduino sketch DOESN'T works when I upload it to the arduino part the Galileo.

Hi and sorry for the wait.

FYI, that arduino sketch DOESN'T works when I upload it to the arduino part the Galileo.

Does this not run for you? Were you able to compile it to begin with? There was another thread on the forums on this topic, see here.
We developed this driver using the Adafruit PN532 Breakout and the examples worked for both the Galileo G2 and Edison boards. Interestingly enough the shield version of the PN532 did give us problems on I2C writes too and I think the part you have was designed using Adafruit's shield as a reference. I suspect the issue might be caused by missing or poorly selected I2C pull-up resistors. While there is a chance this is software based, it will take some time to investigate.
Any additional details you can provide will help, thanks!

Same thing happened to me(but on the edison) till I figure out what I was doing wrong.
After analysing the signals I found out that my I2C lines didnt have nay valid signals going through them. So I check my code again.
what I found was that I haven't set up my board connections properly. hence this is what I ended up using
var myNFCObj = new pn532.PN532(MRAA_IRQ, MRAA_RESET, I2C_BUS_NUMBER);


FileLoadException: Could not load file or assembly 'System.Memory

Getting this exception.
FileLoadException: Could not load file or assembly 'System.Memory, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference.
I have added below tag in app.config
<dependentAssembly>
        <assemblyIdentity name="System.Memory" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral"/>
        <bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>"/>
 </dependentAssembly>

Hi @yadavsachin , not enough information to investigate.
Can you share a minimal repro application that reproduces this?


Stylesheet + Javascript appear as child options on archive pages

When loading archive and sheets with an archive page: if you click to "Add Child" on the archive page you will see "Stylesheet" and "Javascript" as options. They should not be there.

fixed in fe287150a17eb015c9c326f88308b8bfd5817c5c


align output log

[l.example.MyApplication.main()] MainHttpServer                 INFO      http://<IP_ADDRESS>:8080/   (POST) (accept:application/json produce:application/json)
[l.example.MyApplication.main()] MainHttpServer                 INFO      http://<IP_ADDRESS>:8080/q/dev    (produce:text/plain,application/json)
[l.example.MyApplication.main()] MainHttpServer                 INFO      http://<IP_ADDRESS>:8080/q/health    (produce:application/json)
[l.example.MyApplication.main()] MainHttpServer                 INFO      http://<IP_ADDRESS>:8080/q/jolokia    (produce:text/plain,application/json)

You can maybe do so '%s:30.30` or whatever syntax to make the text more aligned as 3 columns in a spreadsheet.
You can also loop the lines and calculate the longest and then adjust the %sN..N syntax accordingly.

I wonder if there's a project that we could use that could take a bean as input and would pretty print the information as the output.
Quite frankly, this is very hard to read.

Obs.: no talking about your proposal. Just venting my frustration that we have to keep concatenating strings and doing a lot of ifs and elses on the code.
IMHO, the view should always be separated from the other layers on the code.

@orpiske I agree, I was thinking about using some kind of template, but seems a bit overkill for this use case, the latest commit uses format with %-Ns and seems a bit more readable, I am open to using some kind of template though.

@orpiske I agree, I was thinking about using some kind of template, but seems a bit overkill for this use case, the latest commit uses format with %-Ns and seems a bit more readable, I am open to using some kind of template though.

Yeah. I think the proposed change is OK given the constraints we have right now.
Longer term, I think we need to find something that could be used globally on the code and would allow us to separate the (usually messier) presentation code from the rest.

we use a table printer library in jbang

we use a table printer library in jbang

That one looks pretty cool


Update cookie-getter dependency

@HenrikJoreteg can you give me contributor access to the npm package? I'm ready to push an update.

oh, I forgot, sorry. Done!

Thanks for doing this! Nice work!

By the way, you should add yourself to the readme as maintainer :)


Deprecate CA2109

~Please wait until https://github.com/dotnet/roslyn-analyzers/pull/6198 is merged.~
This PR gets #31797 back with correction of package name and version.

@gewarren Related PR is now merged


chore(testing): fix typo in docs

Hey open-wc :).
I was using the test-helpers and spotted this typo.
Cheers,

uh thxxxx :)


Fix language model script

Description
Fix the parameter sharing using save_params and load_params between instances with the same parameter structure.
Checklist
Essentials

[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage
[ ] Code is well-documented

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

@piiswrong @szha thanks for the discussion.

Job PR-146/3 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-146/3/index.html


163 update docs for use in docsscscommunity

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.
TODOs:

[ ] squash commits
[ ] include documentation
[ ] add unit tests

@jschoone there was another linter issue with the "" tags...


CSS injection conflict detection?

Given that vscode-icons modifies workbench.main.css, which may conflict with other extensions that changes this file to implement custom CSS, is it possible to provide an option to add user’s custom CSS to the patch?

Could you elaborate this a little bit more? What would be the purpose of it?

@robertohuertasm
There are extensions modifies workbench.main.css either, like vscode-background. They may conflict with each other.

In the case of vscode-icons I only use a comment they have in the code and put some new stuff before it. I don't modify the existing code at all so I guess I won't be causing conflicts with other apps. Anyway, this would be impossible to control as this doesn't depend on something I can control. Everybody is free to do whatever they please so no matter what I do or say. What I've tried is to leave what it already existed exactly the same.


terraform fmt everything

This is from me running terraform fmt in the root directory of the repository, which is similar to go fmt.

Looks like terraform fmt is doing different things on my machine and on Travis, not sure why… will come back to this later.

The next version of Terraform (0.8.8 or 0.9) should have a fix for the issue I was seeing, planning on revisiting this once that is released.

Closing this to re-run terraform fmt against master.


Outdated packages (& misc. errors) when running bootstrap script on AWS Ubuntu 16.04

Prerequisites

[X] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
When running script/bootstrap, I receive the following errors:

npm WARN deprecated<EMAIL_ADDRESS>CoffeeScript on NPM has moved to "coffeescript" (no hyphen)
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
npm WARN deprecated<EMAIL_ADDRESS>CoffeeScript on NPM has moved to "coffeescript" (no hyphen)
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>to-iso-string has been deprecated, use @segment/to-iso-string instead.
npm WARN deprecated<EMAIL_ADDRESS>Jade has been renamed to pug, please install the latest version of pug instead of jade
npm WARN deprecated<EMAIL_ADDRESS>This package is unmaintained. Use @sinonjs/formatio instead
npm WARN prefer global<EMAIL_ADDRESS>should be installed with -g
npm WARN prefer global<EMAIL_ADDRESS>should be installed with -g

Steps to Reproduce

Clone atom
Change to atom directory
Run script/bootstrap

Expected behavior: The bootstrap script completes
Actual behavior: The bootstrap script fails
Reproduces how often: 100%
Versions
Ubuntu 16.04
Node 8.11.2
Npm 5.6.0
Python 2.7
Additional Information
I'd certainly be OK with fixing this myself, but I'm new here and don't know where to start

None of those entries you listed are errors, they are warnings. Unless you've configured things in a very specific way, they will not cause any build failures.
I suggest you look at how we run automated builds in atom/ci. If that doesn't resolve your problem, please open a new issue and provide enough details for us to reproduce the problem and verify that this is actually a problem in Atom. Since this is unlikely to be a problem with Atom itself based on your description, I would recommend asking for the community help in our Slack or on Discuss.


Add AWS_REGION env for S3 in TensorFlow

This fix tries to address the issue raised in #14951 where the region can only be specified with non-common S3_REGION environment variables.
This fix adds the support of AWS_REGION which takes precedence over S3_REGION.
This fix fixes #14951.
Signed-off-by: Yong Tang<EMAIL_ADDRESS>

Jenkins, test this please.

@tensorflow-jenkins test this please


[SPARSE] Add support for sparse gemv with MKLCPU

Description
This first PR is only adding support for sparse gemv and the necessary functions to set it up. This is only adding the MKLCPU backend for now.
The operations trsv and gemm are throwing unsupported for now.
Note that the examples are based on the oneapi dpcpp examples (like the other domains).
All Submissions

[x] Do all unit tests pass locally? Attach a log.
[x] Have you formatted the code using clang-format?

New interfaces

[N/A] Have you provided motivation for adding a new feature as part of RFC and
it was accepted? # (RFC)
[x] What version of oneAPI spec the interface is targeted?

This PR makes assumptions on the oneAPI sparse spec that are not applied yet. This matches with the close-source Sparse oneMKL spec (only some functions are not added yet).

[x] Complete New features checklist

New features

[x] Have you provided motivation for adding a new feature?
[x] Have you added relevant tests?

Made some more changes to follow some spec updates and make it easier to add MKLGPU backend in the future. Please let me know if you have more feedback.

@gajanan-choudhary I am sorry I squashed all the commits and forgot to keep the gemv commit separate. In a nutshell the gemv commit was only calling the MKLCPU gemv and optimize_gemv functions in src/sparse_blas/backends/mkl_common/mkl_operations.cxx and adding tests. You can still see the old diff here.

I have confirmed the tests are still passing locally using 2023.2.0 oneapi package: tests_cpu.txt
Tests log using a MKL nightly that supports complex: tests_cpu_nightly.txt


Implement cumulativeSum

MLOperand cumulativeSum(MLOperand input, unsigned long axis, optional MLCumulativeSumOptions options = {});

Refer to https://onnx.ai/onnx/operators/onnx__CumSum.html

Close it by #103.


updated steps

https://github.com/MicrosoftDocs/microsoft-365-docs/issues/476

@nenonix @JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks.

@VLG17 - please merge the commit on the copy/edit review made by JohanFreelancer9 or make the necessary changes on the PR following the suggestions made. Thank you.

@BrendaCarter - PR has been copy edited and is ready for final review. This is based on issue #476
Thank you.
cc: @kenwith


<!-- Have you read Atom's Code of Conduct? By filing an Issue, you are expected to comply with it, including treating everyone with respect: https://github.com/atom/.github/blob/master/CODE_OF_CONDUCT.md

Summary

Motivation

Describe alternatives you've considered

Additional context

Thanks for reaching out!
We require the template to be filled out on all new issues and pull requests. We do this so that we can be certain we have all the information we need to address your submission efficiently. This allows the maintainers to spend more time fixing bugs, implementing enhancements, and reviewing and merging pull requests.
Thanks for understanding and meeting us halfway :grinning:


Multi Touch Events on Mobile Devices

Any estimates when this issue will be ready for testing?

Not yet, tho Ahome now has a binding to Hammer.js, I'll look into that.
https://github.com/ahome-it/ahome-hammer


return custom headers

hi again!
I couldn't find a way to return headers with the paginate - I have headers that I would need to return with data from the page it pulls. Is there a way doing that?

Hi @jochman,
Sorry for long response.
You can access response using response function from fastapi_paganation.api package.
Here is an example:
from typing import Any, Optional, Sequence

from fastapi import FastAPI
from fastapi_pagination import Page, add_pagination, paginate, response
from fastapi_pagination.bases import AbstractParams

class MyPage[T](Page[T]):
    @classmethod
    def create(
        cls,
        items: Sequence[T],
        params: AbstractParams,
        *,
        total: Optional[int] = None,
        **kwargs: Any,
    ) -> Page[T]:
        page = super().create(items, params, total=total, **kwargs)

        response().headers["X-Total-Count"] = str(page.total)

        return page

app = FastAPI()
add_pagination(app)

@app.get("/items")
def route() -> MyPage[int]:
    return paginate([1, 2, 3, 4, 5, 6, 7, 8, 9, 10])

if __name__ == "__main__":
    import uvicorn

    uvicorn.run(app)

Wdyt about creating a plugin system like pydantic with Annotated and AfterValidator that  get a function with kwargs of page, response?

Makes sense to me, I already started working on smth like this.
You can check it here - https://uriyyo-fastapi-pagination.netlify.app/tutorials_advanced/customization/

@jochman Can I close this issue?

Hi @uriyyo,
thank you for the answer. This is exactly what i was looking for!
I have another question that builds on this one: I would like to have a pagination style like the GitHub REST API (using link in reponse header) but with the original content as the response (and not the content inside e.g. items list with the default Page). Is this also possible? Should i create a separate issue for this?


Bug: Editor freezes after opening the meta data option in posts

Issue Summary
The editor freezes when the Meta Data panel is opened in a new post. The panel itself is active but everything else stops responding to the mouse clicks. Can't even go back to the previous panel
Steps to Reproduce

Open a new post to edit it.
The body shouldn't contain any text (Title is fine)
Click on the gear icon and then on the Meta Data option

Technical details

Ghost Version: master - v1.0.0-beta.2 ( local install )
Client OS: Ubuntu 16.04 LTS
Node Version: 4.5.0
Browser: chrome Version 59.0.3071.104 (Official Build) (64-bit)
Database:mysql

I'm not able to replicate on Chrome or Firefox.
Ghost Version: beta.2
Client OS: Centos 7
Node Version: 6
Database: mariadb

@deecube sorry to hear you are having issues. Are you still able to replicate this? If so would you mind opening Web Inspector console (In Chrome, right click -> Inspect -> click Console tab) and see if you get an error when opening the meta data panel?

I'm not able to reproduce this on my Mac, Chrome version 59.0.3071.115, in Ghost 1.2.0.
Going to close this for now. If anyone else experiences it please let us know and we can reopen.


How does [Bug Report] set native attributes, such as the pattern property of input?

Element UI version
2.0.5
OS/Browsers version
chrome
Vue version
2.5.8
Reproduction Link
https://elementui.github.io/issue-generator
Steps to reproduce
none
What is Expected?
none
What is actually happening?
怎么设置原生属性 例如input的pattern属性？

I'm afraid you'll have to manipulate DOM.


Do not search excluded directories for packages

Previously, PackageFinder.find would search the whole directory tree looking for packages, then remove excluded packages from this list. This made building a package very slow under some circumstances where the file tree was large.
In my case, I have a Python project that includes JavaScript and CSS assets. These assets are compiled by a node.js build chain. Every time the Python package is built, setuptools searches the whole (rather large) node_modules tree for python packages, before rejecting the whole tree because node_modules/__init__.py does not exist. As the build process is happening in a Vagrant virtual machine, and VirtualBox shared directories are notoriously slow, this caused the build process for the Python package to take 30+ seconds just to find the packages!
This change stops PackageFinder.find from descending in to directories that will never be included. The public API should be 100% backwards compatible with previous versions. All the current tests pass without any modifications.
I am unsure if I should write new tests for this specific change, as it might require mocking os.walk to check that the excluded directories are not being searched.

This has been rebased on top of master, and the commit that restricts py.test to make the tests pass again.

The code for this patch is complete, barring any feedback. Is there anything more I can do to help this patch along?

Let's go for it. Can you add a one more commit to CHANGES.txt explaining in the target version what's changed?

I've rebased this on master, and added an entry to CHANGES.txt.

I've just noticed one potential problem with this. With a package set up like:
pkg/
    subpkg/__init_.py
    __init__.py
setup.py

Using the previous find_packages, find_packages(exclude=['pkg']) would return ['pkg.subpkg']. I am unsure whether this is desired behaviour, or even results in a valid package. The new implementation will return [], as pkg was excluded.
I can easily change it to restore the old behaviour, while still keeping (most of) the speed improvements from this patch.

I'm unsure how important this behavior is. I suspect a simpler implementation as is now merged would be preferable, assuming there are no complaints. How about instead update the changelog entry to indicate the backward incompatibility, and we'll field it and see if anyone requires the old behavior?

I've updated CHANGES.txt, and added a new test for the change in behaviour, in #798.

This change breaks backwards compatibility in order to accommodate an edge case, and even then it's just for performance reasons, not correctness. Additionally, the documentation hints that subpackages do get searched:
find_packages(exclude=["*.tests", "*.tests.*", "tests.*", "tests"])

Note that the documentation had tests.* as well as tests. The way I read it, the current release is not aligned with the documented behavior either.
This change also broke the include argument without noting that change in the release notes or documentation. Additionally, projects that want to be able to build on multiple versions of setuptools cannot use include (it doesn't exist on older versions) and so there isn't a way to get find_packages() to find subpackages without also finding unwanted superpackages.
I would like to suggest that this change be reverted, and that setuptools 29 be released with the previous behavior restored.

After writing the above comment, I see that @timheap has written a PR that might address my concerns. Thanks!
https://github.com/pypa/setuptools/pull/809


Issue/ttig claiming note

Summary
Closes #714
Changes
Note on claiming TTIG on TTS distributions other than CH and CE + removing old new-in-version tags
Checklist

[x] Scope: The referenced issue is addressed, there are no unrelated changes.
[x] Run Locally: Verified that the docs build using make server, posted screenshots, verified external links. Test with HUGO_PARAMS_SEARCH_ENABLED=true if style changes will affect the search bar.
[ ] New Features Marked: Documentation for new features is marked using the new-in-version shortcode, according to the guidelines in CONTRIBUTING.
[x] Style Guidelines: Documentation obeys style guidelines in CONTRIBUTING.
[x] Commits: Commit messages follow guidelines in CONTRIBUTING, there are no fixup commits left.

This is actually possible. The gateway has to first be claimed in TTS (Cloud/CE) and then can be configured to any private network. @nejraselimovic can you create an issue for me to document this process? I'll pick that up in the next milestone.

Having this said, I'm going to remove the part of this PR related to connecting TTIG to other deployments, and modify the PR to just remove the excessive new-in-version tags.
@KrishnaIyer, here's the new issue: https://github.com/TheThingsIndustries/lorawan-stack-docs/issues/728


Render raw (escaped) input for disallowed tags

If a user of this library doesn't want to support a specific Markdown feature (eg. blockquote) it would be nice to be able to just render the raw input, rather than having it hidden or unwrapped. Basically just don't parse a specific type of Markdown token, rather than parsing it and then handling it some way.
Looks like this would be possible by deleting a tokenizer from the remark parser at runtime: https://github.com/remarkjs/remark/tree/master/packages/remark-parse#turning-off-a-tokenizer
I'd be happy to submit a PR, if you agree this would make sense as a feature.
To say a bit more about our use case, we are parsing Markdown in clients on multiple platforms, and some of them won't be able to support full Markdown feature set. In order to make the rendered text consistent across platforms, it would make the most sense for us to just ignore certain parts of the Markdown spec.

Oops, just noticed this is a duplicate of https://github.com/rexxars/react-markdown/issues/111


Refactor servlet input for chat in Composum variant

The parameter "chat" should be "chatHistory" and give the messages before the chat. Also, enter should submit.

I recently started that during a refactoring, but then rolled it back because it has unpleasantly many changes in existing code which are not nice. Not important enough.


GLTF is generated with zero weight vertices

Taking the discussion back from here. I'm generating this gtlf with blender+exporter and some of the branches of the generated tree cannot be displayed in babylon.js.
They pointed out that some of the vertices are being exported with wights all in 0 that is not compliant with GLTF standard.
Is this correct? Should I do something in modelling time to avoid this issue?
thanks!

Hmm. On one hand, if engines are likely to be unhappy with zero-weight vertices, it seems like glTF is probably doing the right thing by disallowing that. On the other hand, if Blender does allow zero-weight vertices, it's not clear what this exporter should do when it finds them. Assign the vertex to an arbitrary bone? Add a new bone? Drop the vertex? Crash? 😣
@mcclure my website uses threejs and tries to stick to its default configuration for the most part. It does normalize skin weights. While the glTF spec tries to say "please don't do that", un-normalized weights seem to be pretty common with models coming out of DCC tools regardless of format. See: https://github.com/mrdoob/three.js/blob/8685a33e011f014eca88de8d49e1bc0efa845f4a/src/objects/SkinnedMesh.js#L60-L89.

@julienduroure it's not exactly a satisfying fix, but in practice using 1, 0, 0, 0 to when the weights would otherwise be zero has avoided these issues in threejs.
We've been meaning to get this case into the official validation suite (https://github.com/KhronosGroup/glTF-Validator), but haven't yet: https://github.com/KhronosGroup/glTF-Validator/issues/58.

@julienduroure "Can you please share your blend file? Want to check what happen"
I sent you the blend file via email as we discussed in https://developer.blender.org/T69673 .

Your model displays fine in https://gltf-viewer.donmccurdy.com/

He you want to be sure to not have 0 weights, move your controller_world bone, and check all parts that not moved. Then assign all these vertices to controller_world vertex group

@julienduroure Thanks— as explained above I am aware the model works right in the donmccurdy.com viewer, and Mr. McCurdy above says that his viewer normalizes weights (although this is not what the GLTF spec says to do). So to be totally clear I see short term I can get around my problem by either modifying the .blend or normalizing weights in my importer, but Blender is exporting noncompliant GLTFs and so long term there is a bug there…

so long term there is a bug there…

Don't worry, we agreed on that. I was only explain the root cause, and how to workaround, waiting a fix is pushed. This ticket is still open, bug remains, and still need to be fixed.
Blender allows something that is forbidden in glTF specification, so we have to found how to manage it, as explained by Don. Not sure yet what is the best solution

@julienduroure, you were correct, moving the meshes under the controller_world bone as you recommended fixed my file.
Also, just in case this is useful to anyone who finds this bug on Google: I have created a script that normalizes weights in GLTF files. You can find it in this repo https://github.com/mcclure/gltf-edit as "normalize.py". In my testing, running one of the incorrect "zero weight" blender GLBs through this script made it usable by my engine.

AFAICT, verts that aren't assigned groups in Blender stay in the same place they would be if they weren't skinned?
To do this in glTF we would need to export as if there were a new bone with the identity transform relative to the arma that all those verts were assigned to. Inserting a new bone in every arma would obviously hurt round-tripping though. I guess we could try to do it only when there are unassigned verts (propagating that information to the right places would be a pain...).

it's not exactly a satisfying fix, but in practice using 1, 0, 0, 0 when the weights would otherwise be zero has avoided these issues in threejs.

I think we should merge this as a stopgap, like, now. Obviously (*looks at filing date*) a real fix for this bug is not forthcoming. This is what everyone appears to be doing anyway, it has a non-zero chance of working correctly, and we might as well export a wrong-looking but valid file instead of a wrong-looking and invalid file.
Patch is:
diff --git a/addons/io_scene_gltf2/blender/exp/gltf2_blender_extract.py b/addons/io_scene_gltf2/blender/exp/gltf2_blender_extract.py
index c605a60..12c9060 100644
--- a/addons/io_scene_gltf2/blender/exp/gltf2_blender_extract.py
+++ b/addons/io_scene_gltf2/blender/exp/gltf2_blender_extract.py
@@ -286,6 +286,7 @@ def extract_primitives(glTF, blender_mesh, library, blender_object, blender_vert
                         bones.append((joint, weight))
                 bones.sort(key=lambda x: x[1], reverse=True)
                 bones = tuple(bones)
+                if not bones: bones = ((0, 1.0),)  # HACK for verts with zero weight
                 vert += (bones,)

             for shape_key in shape_keys:

I think we should merge this as a stopgap, like, now. Obviously (looks at filing date) a real fix for this bug is not forthcoming

I'm OK with this, if we include a comment and a link to this issue for future reference.

Okay, I PRed the stopgap for 2.90. I also opened #1151 to talk about the real fix.

Will be fixed by #1552


[HUDI-3994] - Added support for initializing DeltaStreamer without a defined Spark Master

Tips

Thank you very much for contributing to Apache Hudi.
Please review https://hudi.apache.org/contribute/how-to-contribute before opening a pull request.

What is the purpose of the pull request
Added support for initializing DeltaStreamer without a defined Spark Master. That will enable the usage of DeltaStreamer on environments such as AWS Glue or other serverless environments where the spark master is inherited and we do not have access to it.
Brief change log

Modify HoodieDeltaStreamer class in order to have an option to inherit Spark Master.
Modify UtilHelpers class to have an option to start the Spark Context without defined Master.
Modify HoodieMultiTableDeltaStreamer to have the same default Spark Master( although right now is not used).

Verify this pull request
(Please pick either of the following options)
This pull request is a trivial rework.
Committer checklist

[x] Has a corresponding JIRA in PR title & commit

[x] Commit message is descriptive of the change

[x] CI is green

[x] Necessary doc changes done or have another open PR

As seen here, a commiter is working with the CI (I could add the change but...): https://github.com/apachehudi-ci/hudi-branch-ci/commit/e6e03a78734f3a9c878014fa0841398da6af0b0e

@hudi-bot run azure

Will it be possible to add test cases for this change?

Hi @pratyakshsharma,
I could try to add a test for initialising the Spark Context. However, the change is very simple and looking for the tests I did not see any that test that tests the other constructors.
The only thing is that now, if no Spark master is not defined it will inherit or the application will fail as no Spark context is defined. Previously it would run with local[2] as Spark Master.
What do you have in mind? (looking for some guidance).

Hi,
Should I rebase it from latest stable version? Almost every time I merge somethings breaks ( and it´s not because my changes).
Thanks!

To be able to merge, you need to rebase it on master itself.


#146 Fixing Container Security Context Logic

Kubernetes rationalizes Container Security Context in conjuction with the
Pod Spec Security Context. In this scenario you can 'leave out' certain
security context settings and rely on the pod spec definition to still
set these settings for you. The RunAsNonRoot setting originally only checked
to see if the value was set at the container level, vs also checking if it
was enabled at the pod level.
I have attached the container's parent pod spec to the container validate
struct in case any other things like this arise in the future.
I have also refactored the logic for validating bool pointers, since these
can be tricky, if you want to avoid dereferences pointer issues.
Changes:

Added parent pod spec of container to validate certain settings which affect container spec
Refactored the logic statements for validating bool pointers (used helpers)
Added tests for this pod.container.securityContext condition

I'm interested if anyone has any other ideas on how to solve this issue of podSpec affecting unset values in containers. Another potential way to go about this is to check each container (while in the pod validation) if the security-context is set to false || nil at the pod level.

FYI I'm still missing the CHANGELOG additions (when this eventually is ready)

This is awesome, thanks for chasing it down! Tests look solid.
I looked a bit at SecurityContext vs PodSecurityContext, and this seems to be the only variable that's shared between the two.
Re: changelog, I've just been updating at release time (since we don't know the eventual version number). You're welcome to start an "In Progress" section though.
Other than the comment on bool helpers this LGTM.


Exporter is not available after restarting PrometheusTelemetry

When starting PrometheusTelemetry it does a :persistent_term.put/2:
https://github.com/theblitzapp/prometheus_telemetry_elixir/blob/1dbd3538def4152e4564f3cf5445d4dbd2c255e9/lib/prometheus_telemetry.ex#L149
But there is currently no way to correctly stop it again. When using Supervisor.stop(pid) it stops the supervisor, but the :persistent_term key won't be updated. So, when restarting PrometheusTelemetry, the :__exporter_ports__ still contains the port that is not used anymore, which prohibits starting the exporter again.
Before restaring PrometheusTelemetry, we currently need to do this:
Supervisor.stop(pid)
:persistent_term.put(:__exporter_ports__, :persistent_term.get(:__exporter_ports__) -- [port])

Would be cool to have a stop function for this which takes care about removing the port from the persistent term.

I'm curious what use case causes the exporter to need restarting. Great find though!

I have tests for my custom metrics. When doing something 10-times, I expect my metric to be set to 10.
To reset the metrics for each test, I need to restart PrometheusMetrics.

Probably just need to hook into termination and flag it for the supervisor to do cleanup, I will take a look at getting this in soon


LifetimeTracker is not working on Objective-C

When I installed it via CocoaPods and imported @import LifetimeTracker the only these two are exposed
FOUNDATION_EXPORT double LifetimeTrackerVersionNumber;
FOUNDATION_EXPORT const unsigned char LifetimeTrackerVersionString[];

I can't use anything else.

I have prepared pull request fixing this.
https://github.com/krzysztofzablocki/LifetimeTracker/pull/27


Eror testing with Vidio inference_video.py

I will testing model using fasterrcnn_resnet50_fpn_2 and I found an error in my program like the following:
Building from model name arguments...
Downloading: "https://download.pytorch.org/models/fasterrcnn_resnet50_fpn_coco-258fb6c6.pth" to /root/.cache/torch/hub/checkpoints/fasterrcnn_resnet50_fpn_coco-258fb6c6.pth
100% 160M/160M [00:03<00:00, 52.4MB/s]
Frame: 1, Forward pass FPS: 0.820, Forward pass time: 1.220 seconds, Forward pass + annotation time: 1.226 seconds
qt.qpa.xcb: could not connect to display
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "/usr/local/lib/python3.10/dist-packages/cv2/qt/plugins" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: xcb.

I tested using google colabs. Please give me information in the topic eror.

@WawanFirgiawan
I think the error is due to opencv-python-headless and opencv-python.
Can you please do:
pip uninstall opencv-python
pip install opencv-python-headless
And please do not pass --show argument to the inference command on Colab. OpenCV does not support OpenCV visualization.

bagimana saya bisa melakukan pengujian secara realtime?

Hello, if you are asking for more than 24 FPS inference on videos, then you will need a powerful GPU.
But you can also opt for smaller models in the library to get real-time FPS even on medium-range GPUs.


Example of Generation Notification via Context Object

I'm not sure what you meant by this, but is this now already covered by tests/test_inc_generation.py and examples/simple_ga.py since both of those use context objects?

Agreed! Closing.


"--iface=auto" is hard-code in socketplane.sh

I try to use socketplane in my openstack VMs. And I find that if I use "--iface=auto", the consul cluster can't work well. After I modify "--iface=eth0" in socketplane.sh, it works in my envorinment(My Openstack VMs have only one interface eth0). So I think it will be better if "--iface" is configurable in socketplane command .

thanks @LipingMao . Agreed.
We have #57 opened already for this. Also, there is another enhancement #69 which handles the static provisioning use-case with an option to listen on a particular interface.
If you agree, we should close this as a duplicate of #57
Please add any comments / suggestions / pull PR against #57 and #69 . Thanks.

Thanks @mavenugo for the info, I totally agree this  should be closed.  #57 LGTM  :-)

Closing the issue as this is a duplicate of #57


Aptly leave empty directory structure when droping published repo with prefix

When removing the last distribution from a published repo with a prefix, Aplty will empty directories, but leave the prefix structure in place.

This could be done is prefix is empty.

Changed it to use Remove() instead to avoid a race condition


Change to CMD shell form

This PR will use the docker CMD shell format. It allows for executables with command line arguments to be run properly.
Original docker that caused start cmd ./out my args to fail.
ENTRYPOINT [\"/bin/bahs\", \"-l\", \"-c\"]
CMD ["my command"]

This allows any start command to execute
CMD my command

We can remove the ENTRYPOINT because the new CMD format will run inside a shell.
I ran the test, everything passed up until it hit the Doc-tests nixpacks

closes #748

Unfortunately, I don't think this will work because the base -l is necessary to load things in ~/.profile on container start. (see this PR https://github.com/railwayapp/nixpacks/pull/487 and https://github.com/railwayapp/nixpacks/issues/658)
You can run commands with arguments by quoting everything. E.g. docker run my-image "./out arg 1 arg2"
Very open to suggestions on how to have both the CMD format as well as ensuring that everything in ~/.profile is loaded.

Alright, here are few ideas.

The golang start command does not get run as a string. It gets executed in a non-shell CMD, because it does not have an entrypoint.

Resulting in the following
docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "echo yoooo && ./out hello world \"yo bro\" 1 2 3": stat echo yoooo && ./out hello world "yo bro" 1 2 3: no such file or directory: unknown.
ERRO[0000] error waiting for container: context canceled

start.run_in_slim_image() adds this to the docker. Adding an entry point here fixes the golang issue.

This change passes all tests.

This is a just a random spitball... but we could just source ~/.profile as the first part of the CMD

sh has a special environment variable ENV. if this environment variable is set, it will execute any files specified in the variable when SH is invoked. Is there something similar for bash, so we can specify an ENV in the dockerfile?
https://stackoverflow.com/questions/38024160/how-to-get-etc-profile-to-run-automatically-in-alpine-docker

Good suggestions! We should defintely do 1 because that seems like a bug.
I am actually surprised that all the docker run tests pass in this PR. I will confirm that the -l -c is still need and if so can add a test that would fail without it. That way we can be sure of any solution moving forward.

The alternative could be a simple bash wrapper (like i posted in #658) that we run as the entrypoint:
#!/usr/bin/env bash

if [[ "$#" == "1" ]]; then
  exec bash -l -c "$@"
else
  exec bash -l "$@"
fi

And then the CMD for the image can just be the command that was passed. This would also allow docker run to be executed with arguments on commands vs a quoted command.


Steps added for binomial distribution pmf

Related Issue
Fixes #3372
fix #[issue number that will be closed through this PR]
Describe the changes you've made
A clear and concise description of what you have done to successfully close your assigned issue. Any new files? or anything you feel to let us know!
I have added the steps.
Checklist:

[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.

Actually you created a Calculator only, and haven't added steps for it, i.e. how it is working / how it's calculating.
Can you add steps? if not comfortable with it do tell us

@sairish2001 Yes I will add steps.

have a look to
calculators/solveFraction.html
and
library/logicjavascript.js -> function solveFraction(num1,num2)
be make sure you use same thing, as did in these. because we are planning to release it as a library also, so your function should follow these rules.

make separate file in Calculators folder
link with index.html by just calling loadcalculator('filename') in the navbar.
put the required function in the library/logicjavascript.js

have a look to
calculators/solveFraction.html
and
library/logicjavascript.js -> function solveFraction(num1,num2)
be make sure you use same thing, as did in these. because we are planning to release it as a library also, so your function should follow these rules.

make separate file in Calculators folder ( camelCase for filename )
link with index.html by just calling loadcalculator('filename') in the navbar.
put the required function in the library/logicjavascript.js

@Khushi-agarwal

@sairish2001 Can you please help me by telling me how to link the calculator file with index.html.

just call loadcalculator ('filename');
instead of calling on workink.js

Change file name from pmf.html to binomialDistributionPmf.html

Change file name from pmf.html to binomialDistributionPmf.html

Done.Kindly review it. @sairish2001


Pass views assembly to linker

Re-schedule target to run before linker
Add additional linker input item

Requires https://github.com/dotnet/sdk/pull/3539
Addresses AspNetCore#12064

@rynowak @pranavkm @mkArtakMSFT @sbomer Still draft as the SDK side needs testing, as does this side, though I could use some help with that.

The only way to test this is by building a franken-build. I'd be happy to sit with you and try stuff out if you have the bits :)

Any unfortunately there's no way to write an automated test for this scenario in our repo 😠

@rynowak @pranavkm This is ready for review. See updated description. I've tested with and without my sdk change. This works without it and future proofs it to work with it as well. We can take this small change independently through ask mode from the larger sdk change.

Code changes here look fine. Are you taking this through ask mode or are we? 👼

Sending the mail. I don't have permission to set the ask-mode label.

@dougbu does this need to target the release/3.0-preview9 branch if this needs to get in to 3.0-preview9?

@dougbu does this need to target the release/3.0-preview9 branch if this needs to get in to 3.0-preview9?

Yes, definitely.

I've changed the target branch

BTW, @nguerrera I know you know this but for @pranavkm and others: This PR has been QB approved though @SteveCarrollMSFT had a question (still open) about perf impact.


[Update Request]: RoyalTS V7 7.02.50703

What type of update are you requesting?
A new version of an existing package
Current Package Identifier
RoyalApps.RoyalTS.V7
Package Version
7.02.50703
Please describe the changes you would like to see
No response

Will be resolved by #161284


Extract era module from era supervisor.

This doesn't change any implementation; it just moves Era and EraId to their own module, since era_supervisor.rs is already pretty long.

bors merge


Game crash on m_pObject->GetName() call.

What is the game you are using with IL2CPP Resolver?
Waven
Details:
Game simply close after calling m_pObject->GetName() .
Screenshots/Video:
No response
Minimal, Complete and Verifiable Example code:
void Test() {
Unity::il2cppArrayUnity::CGameObject** m_pObjects = Unity::Object::FindObjectsOfTypeUnity::CGameObject(UNITY_GAMEOBJECT_CLASS);
printf("GameObjects found : %I64u", m_pObjects->m_uMaxLength);

for (uintptr_t u = 0U; m_pObjects->m_uMaxLength > u; ++u)
{
    Unity::CGameObject* m_pObject = m_pObjects->m_pValues[u];
    if (!m_pObject) continue; // Just in-case

    m_pObject->GetName();
}

}
void OnUpdate() {
}
void OnLoad() {
AllocConsole();
ReOpenConsoleStreams();
IL2CPP::Initialize();

IL2CPP::Callback::Initialize();
IL2CPP::Callback::OnUpdate::Add(OnUpdate);

Test();

}

the loop should be
Unity::CGameObject* m_pObject = m_pObjects->At(u);

However, I've been having the same problem in my recent code, but the triggering conditions are very random as far as I can tell, and it doesn't seem to raise the exception immediately when called, but rather after passing through several UnityEngine functions, and then crashing.


Message sequence in streams

Hi,
is the sequence in which messages are received in a stream always identical to the sequence the messages were sent in?
Thanks!

Yes.


More severity levels

We're proudly using haml-lint in our bot bot but we would like to use the same severity levels as RuboCop does. Would you accept a pull request which implements this enhancement?

Hey @skateman,
I think adding severity levels is inevitable, although I would keep it simple and only have warning and error, rather than the ones that RuboCop uses (lint, cop, fatal, etc.)
Most of the plumbing supporting this is already in place, so it should be easy to add. Feel free to submit a pull request, otherwise we'll get to it when we can.


Tracking Issue: Deployment Agent

Last week progress has been made on the deployment agent proto definition by @lorenz .
Now investigating the best way to ship operating systems. Likely going with original 'upstream' distribution images and integrating over cloud-init via “No Cloud” metadata over a separate partition.This would be created by the deployment agent, integrating discovered data from the initial OS and user-provided metadata.
With cloud-init we still have to decide which network configuration schema version we should be using. v2/netplan is the most attractive due to its capabilities, but we need to check which of our supported OS images actually are able to consume it.
To generate the cloud-init/netplan config we can either fully construct that ourselves (by autodiscovering on the host) or “steal” parts of it from the provider OS configuration.

Prototype for this is getting close, currently implementing reading support for the GPT library to be able to place NoCloud partitions. Prototype is still a bit rough, needs testing and un-hardcoding stuff. But a bunch of things have already been validated on it.

GPT library PR: https://review.monogon.dev/c/monogon/+/956

Split this into smaller issues, see milestone.


running effect in  Single Pass Instanced mode

Hi,
Is it possible to run it with single pass instanced stereo mode?

No. I'd recommend using Unity's post processing stack instead.


Doesn't connect to google on a PineA64

Hey! I'm using a PineA64 board, which I've managed to get AlexaPi working on.
The Alexa side works perfectly. No issues, in fact better than I thought it would.
Google, however, locks the whole thing up.
Upon trying to run the assistant manually using:
/opt/AlexaPi/env/bin/python -m googlesamples.assistant --credentials /etc/opt/AlexaPi/assistant_credentials.json
I get:
INFO:root:Connecting to embeddedassistant.googleapis.com
which sits there indefinitely.
Any thoughts on diagnosing/debugging this?
(just as an FYI, I'm using https://github.com/swkim01/RPi.GPIO-PineA64 which replaces the standard RPi.GPIO, but I can't imagine that has anything to do with it. Especially where Alexa works flawlessly)

Hi @kronflux ,
A little background first :) AssistantPi is basically AlexaPi, with Google Assistant Python SDK 0.2.1 hooked into it.
The installer runs the AlexaPi setup and then performs the necessary steps for installing Goggle Assistant seperately, and does the audio config for both.
When you fire it up, the AlexaPi script starts the Google Assistant process in the background too, and communicates with it via Pipes. So this is no seamless integration, but much more a proof of concept.
To finally answer your question :) I've mentioned the Google SDK version 0.2.1 specifically - I haven't updated to 0.3 yet as they introduced new libraries to communicate with Google Services. Those only work on certain Chip architectures (arm7 I think, you can find it in their repo's issues), which even breaks support for Raspberry Pi Zero (W), whereas not introducing too much other useful stuff...
Try grab the 0.2.1 Google SDK Release, install it standalone according to the README of that version (!) and try to debug it that way. Tbh, I think this won't work as Google made this sample client we're using specifically for RPi :(

To be entirely clear, I have had the google assistant working previously using their tutorial on this device.
What I didn't have, unfortunately, was hotword detection, which is what drew me to this.
That being said, this clears things up a lot for me. Thanks!
I have almost no experience with modifying python scripts, so I was mostly looking for a quick and easy solution to getting voice control to google assistant, rather than requiring a button press :)

You could try getting the latest standalone Google SDK, it supports voice control since 0.3 as well!


Upgrade to latest Ruby

Had some trouble installing Ruby 3.0.4 so figured might as well upgrade it.

Looks like the test matrix only has 3.1 not 3.2 - maybe worth adding?

Interesting, CI failed with
domain_name-0.6.20231109 requires ruby version >= 2.7.0, which is incompatible
with the current version, 2.6.10

Not sure where that comes from, will have another look tomorrow or so.
Appreciate the instant feedback on the PRs :bow: you guys rock

Found the culprit - it was actually the bot that cut the release with 398565cc4c248db5efcc7a899c5a792dab003de9
It upgrade domain_name from 0.5.x to 0.6.x which dropped Ruby 2.6 support - https://github.com/knu/ruby-domain_name/blob/master/CHANGELOG.md
However, as Ruby 2.6 and even 2.7 are officially EOL it probably makes sense to update the CI matrix to drop especially 2.6.
Ruby 3.0

status: security maintenance
release date: 2020-12-25
normal maintenance until: 2023-04-01
EOL: 2024-03-31 (expected)
Ruby 2.7

status: eol
release date: 2019-12-25
normal maintenance until: 2022-04-01
EOL: 2023-03-31
Ruby 2.6

status: eol
release date: 2018-12-25
normal maintenance until: 2021-04-01
EOL: 2022-04-12

from https://www.ruby-lang.org/en/downloads/branches
Will update the PR but this would need a major version upgrade

Also just to note this is less blocking than the http dependency upgrade that was merged in #71 - more of a housekeeping PR


Choose monitor with GTK dialog

Fixes: https://github.com/QubesOS/qubes-issues/issues/9282

@marmarta Can you please take a look?

I like it with one problem - the select monitor window I got was very small, with enough space to see just one screen, and I had to scroll to see the other (at first glance I thought it wasn't working at all).

@marmarta That is a zenity dialog relevant to another PR:

https://github.com/QubesOS/qubes-video-companion/pull/24

Which I thought I had done a good conditional size estimate, but I tested only on Debian and your Personal qube Zentiy program looks like Fedora. So Debian and Fedora Zenity behave differently. Anyway, please checkout the code relevant to this PR.

yeah, you're right... I'm learning to use qubes builder v2 and sometimes I end up with things switching to main when I wanted to test something, it's one of those times :/

Ok, I don't encounter this issue when I cancel on Dom0. My second monitor only appears listed in Dom0, my DomUs only list DUMMY0.
But your error happens with me when I call the script directly from the target emulating a call:
QREXEC_REMOTE_DOMAIN=disp1360 /usr/share/qubes-video-companion/sender/screenshare.py

Traceback (most recent call last):
  File "/usr/share/qubes-video-companion/sender/screenshare.py", line 170, in <module>
    screenshare = ScreenShare()
                  ^^^^^^^^^^^^^
  File "/usr/share/qubes-video-companion/sender/screenshare.py", line 26, in __init__
    self.main(self)
  File "/usr/share/qubes-video-companion/sender/service.py", line 155, in main
    self.start_transmission()
  File "/usr/share/qubes-video-companion/sender/service.py", line 124, in start_transmission
    width, height, fps, extra_params = self.parameters()
                                       ^^^^^^^^^^^^^^^^^
  File "/usr/share/qubes-video-companion/sender/screenshare.py", line 121, in parameters
    raise ValueError("Monitor index was not set")
ValueError: Monitor index was not set

Note that the following already happened before:
Traceback (most recent call last):
  File "/usr/share/qubes-video-companion/receiver/receiver.py", line 82, in <module>
    main(sys.argv)
  File "/usr/share/qubes-video-companion/receiver/receiver.py", line 17, in main
    width, height, fps = read_video_parameters()
                         ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/share/qubes-video-companion/receiver/receiver.py", line 63, in read_video_parameters
    raise RuntimeError("wrong number of bytes read")
RuntimeError: wrong number of bytes read

Now the ValueError("Monitor index was not set") only appears when emulating the call while the receiver now handles input with 0 bytes as an operation canceled by the sender.
Pushed changes.

PipelineRetry

Thanks for the review guys!


ActiveRel find_by_id should throw RecordNotFound when no results

Currently when doing ActiveRel.find(999), the method throws undefined method r for nil.
This PR handles ActiveRel.find similar to ActiveNode.find throwing a Neo4j::RecordNotFound.

Codecov Report

Merging #1482 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #1482      +/-   ##
==========================================
+ Coverage   96.85%   96.85%   +<.01%
==========================================
  Files         205      205
  Lines       12615    12620       +5
==========================================
+ Hits        12218    12223       +5
  Misses        397      397

Impacted Files
Coverage Δ

spec/e2e/active_rel_spec.rb
98.61% <100%> (ø)
:arrow_up:

lib/neo4j/active_rel/query.rb
95.91% <100%> (+0.26%)
:arrow_up:

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 961e28c...8cf41d7. Read the comment docs.

I'll merge this and release, but I would very much recommend not using ActiveRel.find, and it may go away at some point in the future.  Neo4j doesn't allow for any indexing for relationships, and so a query like this (()-[r]-()) will scale very poorly as your database grows.  Neo4j is (as I understand it) designed around the idea that you should start with nodes in your query as use relationships for traversal to other nodes.  Thus one of the nodes should be part of your query, or perhaps the relationship should be a node itself

(and after all of that explination, BTW: thanks for the submission!)

Released as 9.1.4

@cheerfulstoic mapping a neo4j db model to jsonapi.org resources is not straightforward. The choice we made was to model relationships with at least 1 property as resource. Consequently we made such resources addressable. I am not sure if it would have been better not to expose the show routes to such resources and if this is a viable option in our domain.

I'm also on a project where we used JSON API and when we represent relationships they are always either an extension of the URL from the source node or returned in the body of the data for a node.  It is my understanding (and I'm happy to be corrected if this is wrong) that relationships aren't first class citizens in Neo4j with regards to queries and you can be in for a bad time if you treat them that way.  If relationships were more directly queryable in Neo4j / Cypher then I would be happy to support query methods in ActiveRel, but as it is I feel the need to steer people away from them as a steward of the Ruby libraries


Aurora does not respond th what is happening in-game

Expected behavior:

Actual behavior:

How often does this problem occur?

This problem occurs... (Fill in here)
Please describe the steps to reproduce this issue:
The issue can be reproduced by doing following steps:

Download aurora
open a game
get base lighting pattern
4.expect light to change

What is the version of Aurora you are experiencing this issue with?

My version is... (Fill in here)
The latest version
Does the previous version of Aurora have this issue?
The previous version, (Fill in the version here), did/did not have this issue.
none, I had installed for about a week without touching it, telling myself I would fix the issue later
Please include any logs, screenshots, or files that are related to this issue:

Which game did you try and how did you expect the lights to change?

Wow I don't think I could've been more unhelpful if I tried, sorry about that


[5.7]Swift build with bootstrapping0 and -enable-cxx-interop cause error: missing required module 'SwiftShims'

Describe the bug
When I checkout the release/5.7 and release/5.7.0 branch (both behave the same), running:
./utils/update-checkout --clone --clean --scheme release/5.7.0
./utils/build-script --release-debuginfo --assertions

The build steps failds on the FAILED: bootstrapping1/SwiftCompilerSources/Basic.o:
[1290/2067][ 62%][491.748s] Building swift module Basic
FAILED: bootstrapping1/SwiftCompilerSources/Basic.o /Users/lizhuoli/Documents/ByteDance/toolchain/build/Ninja-RelWithDebInfoAssert/swift-macosx-arm64/bootstrapping1/SwiftCompilerSources/Basic.o
cd /Users/lizhuoli/Documents/ByteDance/toolchain/swift/SwiftCompilerSources && /Users/lizhuoli/Documents/ByteDance/toolchain/build/Ninja-RelWithDebInfoAssert/swift-macosx-arm64/bootstrapping0/bin/swiftc -c -o /Users/lizhuoli/Documents/ByteDance/toolchain/build/Ninja-RelWithDebInfoAssert/swift-macosx-arm64/bootstrapping1/SwiftCompilerSources/Basic.o -sdk /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk -target arm64-apple-macosx10.9 -module-name Basic -emit-module -emit-module-path /Users/lizhuoli/Documents/ByteDance/toolchain/build/Ninja-RelWithDebInfoAssert/swift-macosx-arm64/bootstrapping1/SwiftCompilerSources/Basic.swiftmodule -parse-as-library /Users/lizhuoli/Documents/ByteDance/toolchain/swift/SwiftCompilerSources/Sources/Basic/SourceLoc.swift /Users/lizhuoli/Documents/ByteDance/toolchain/swift/SwiftCompilerSources/Sources/Basic/Utils.swift -wmo -Xfrontend -validate-tbd-against-ir=none -Xfrontend -enable-cxx-interop -Xcc -UIBOutlet -Xcc -UIBAction -Xcc -UIBInspectable -O -cross-module-optimization -Xcc -I -Xcc /Users/lizhuoli/Documents/ByteDance/toolchain/swift/include -Xcc -I -Xcc /Users/lizhuoli/Documents/ByteDance/toolchain/build/Ninja-RelWithDebInfoAssert/swift-macosx-arm64/include -I /Users/lizhuoli/Documents/ByteDance/toolchain/build/Ninja-RelWithDebInfoAssert/swift-macosx-arm64/bootstrapping1/SwiftCompilerSources
<unknown>:0: error: missing required module 'SwiftShims'
ninja: build stopped: subcommand failed.
ERROR: command terminated with a non-zero exit status 1, aborting

Steps To Reproduce
Steps to reproduce the behavior:
cd swift
git checkout release/5.7.0
./utils/update-checkout --clone --clean --scheme release/5.7.0
./utils/build-script --release-debuginfo --assertions

I also tries the bootstrapping mode hosttools, similar and still failed.
./utils/build-script --release-debuginfo --assertions --bootstrapping=hosttools

Expected behavior
The bootstrapping should build success.
Screenshots
If applicable, add screenshots to help explain your problem.
See the build log, it actually what's output from terminal without any modification
Environment (please fill out the following information)

OS: macOS 12.4
Xcode Version/Tag/Branch:  Xcode Version 13.4.1 (13F100) and Xcode Version 14.0 beta 6 (14A5294g), both failed
Arch: Apple Silicon (arm64)

Additional context
Add any other context about the problem here.
After some log into the Compiler's Code, I found seems this issue is because of the -enable-cxx-interop, which implicit add the dep of module to the SwiftShims. However, the correct clang header path for the SwiftShims/module.modulemap did not get passed.
The output log I added shows like:

moduleID.Loc: <invalid loc>
moduleID.Item.str() SwiftShims
moduleID.Loc: <invalid loc>
moduleID.Item.str() SwiftShims
moduleID.Loc: <invalid loc>
moduleID.Item.str() SwiftShims
clangHeaderSearch:
module->failedToLoad()

So, I try again with the same compiler command without the -enable-cxx-interop, it works:

OK. I found the issue myself.
The upstream code seems OK, during my testing, I pick some internal patches which effect the Clang's default behavior about -fcxx-modules as false (Which is the Apple's Xcode clang behavior in Xcode 12).
Which is needed for -enable-cxx-interop, so it failed. After I revert my changes, it can build now.
Anyway, is the -enable-cxx-interop can explicit pass the -fcxx-modules  ?

Anyway, we fix the patches and build successfully now.


Feature/sorting

As requested in: #98 I've added sorting:

By default, it first sorts elements by the name of the operation (delete, get, post etc.), then by the name of the endpoint (add pet, update pet etc.)
You can use x-sort-order to override default sorting and arrange endpoints in any way you want, check redoc-vendor-extensions.md for description and example

If you want to see the effect, click here.
To get the file, click here.

Hey @Darkey999!
Thanks for you PR!
I will review it on Monday as I am not here tomorrow and on the weekends

Hey @RomanGotsiy!
Thanks for checking my PR, I'll make all necessary changes as fast as I can.

No idea if there are still plans for this, but I just used this code to get my operations sorted.
sort.ts just for operation comparing:
export const endpointComparator = (a, b) => {
  return (a.metadata.operation != null && b.metadata.operation != null)
    ? a.metadata.operation.localeCompare(b.metadata.operation)
    : 0;
}

side-menu.ts has a recursive menu sorter added:
  sortMenuItems(menuItems: MenuItem[]) {
    let menuItemsLength = menuItems.length;
    for (var menuItemIndex = 0; menuItemIndex < menuItemsLength; menuItemIndex++) {
      let subItems = menuItems[menuItemIndex].items;
      if (subItems !== undefined && subItems !== null && subItems.length > 0) {
        subItems = this.sortMenuItems(subItems);
      }
    }

    menuItems.sort(endpointComparator);
    return menuItems;
  }

and init has: this.menuItems = this.sortMenuItems(this.menuService.items);

Thank you, I want to finish all necessary changes, but since my academic year started, I can't find time for this. Bus as I said, I'll do it.

@RomanGotsiy @Darkey999 Any updates ?

@jsamr this PR is opened against 1.x version.
It needs to be rewritten against 2.x.
I don't have much time to do it right now.
Any help would be appreciated!

1.x version of Redoc is in maintenance mode. New features won't be added.
Closing this PR. If somebody want's this feature, please open a new PR against the React version.
Thanks @Darkey999 for amazing job and sorry for not merging this.


Add a count up timer

Just to see how much time I've been doing a task, sometimes restarting the session will be distraction and may lose fucus

+1 for this feature, having an accurate study time would be great.

+1

hi, i would like to work on this issue


Add descriptive names for contacts

The transplant contacts do not have informative names yet. Perhaps we should use "distance" and "VdW_overlap".

done


Export tool functions

Feature request 🚀
This maybe helpful  for some users, and additional documents need to be added.
Examples:
import { useClipboard } from '@zeit-ui'

const { copy } = useClipboard()

Update, this feature needs to wait for all test coverage.


[CHP-2481] - switch trace ID to X-Trace-ID, and allows to stack addit…

…ional trace ID headers

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Wei Li seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Fix adapter-netlify query params splitting (#1466)

Instead of manually recreating the query parameters object from Netlify Functions' queryStringParameters object it is directly using the rawQuery object to create the URLSearchParams.
Fixes #1466
Before submitting the PR, please make sure you do the following

[x] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[x] This message body should clearly illustrate what problems it solves.
[ ] Ideally, include a test that fails without this PR but passes with it.

Tests

[x] Run the tests with pnpm test and lint the project with pnpm lint

Changesets

[x] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpx changeset and following the prompts

It looks to me like adapter-begin should be updated in the same way:
https://github.com/sveltejs/kit/blob/06380d7c9eb40a8ade90ac1cedb30e797060d884/packages/adapter-begin/src/index.js#L10
Would you mind updating that one as well?

It looks to me like adapter-begin should be updated in the same way:
https://github.com/sveltejs/kit/blob/06380d7c9eb40a8ade90ac1cedb30e797060d884/packages/adapter-begin/src/index.js#L10
Would you mind updating that one as well?

Sure thing, I updated that one as well.