"fixed" swaglines (lines that appear on a victory) and the eliminated popup in the middle of the screen

Could you also try add preloading of weapons??

Could you also try add preloading of weapons??

yea sure

Could you also try add preloading of weapons??

yea sure

Nice but i played a match with my friend on 7.40 but the eliminated player thing didnt show up

i will merge once he fixes ClientReceiveKillNotification  (which is the Elimated one), you are not supposed to call it on all players just the one that killed the player. iirc i had it commented out.

oh yea my bad I was dealing with multiple report functions I didn't notice it wasn't the right one

done


Write discussion guide for user research sessions

What
We need to write a discussion guide for our user research sessions.
Why
We need to know what questions we want to ask our research participants.
Done when

[ ] Identify questions we want to ask as a group
[ ] Write up discussion guide
[ ] Discussion guide reviewed by other members of the team

Link to discussion guide


Provided private key and latest private key fingerprints mismatch.

I have no idea where to post this but doe anyone have an idea what is wrong and why artifactory fails to start?
09-Mar-2017 11:21:41.912 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.listenerStart Exception sending context initialized event to listener instance of class org.artifactory.webapp.servlet.AccessServerStarter
java.lang.IllegalStateException: Provided private key and latest private key fingerprints mismatch. provided: 69bb6f7139e10fb1451354742734019fb8b76bb0a1b7ac66d11ded1d0671356c, latest: 72eb1d3af1a9035a7069450c0de547fded00575f856becc78d799ab86bbcb4c6
at org.jfrog.access.server.AccessServerBootstrap.verifyLatestPrivateKey(AccessServerBootstrap.java:251)
at org.jfrog.access.server.AccessServerBootstrap.copyPrivateKeyAndCertFromBootstrapIfExists(AccessServerBootstrap.java:210)
at org.jfrog.access.server.AccessServerBootstrap.initPrivateKeyAndCert(AccessServerBootstrap.java:128)
at org.jfrog.access.server.AccessServerBootstrap.(AccessServerBootstrap.java:80)
at org.artifactory.webapp.servlet.AccessServerStarter.startAccessServer(AccessServerStarter.java:51)
at org.artifactory.webapp.servlet.AccessServerStarter.contextInitialized(AccessServerStarter.java:34)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4853)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:753)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:729)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:717)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:587)
at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1798)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

Hi @pgeorgiev333 . Can you provide more details?

What did you install?
Are these based on the examples here?
What are the steps you took. Help us reproduce to try and help.

well i started artifactory 4.x and used it for a while with volumes for /etc/ , data/ , backup/ and logs/ folders.
Then i chnaged the image to 5.1 and everything was ok for a while. Today i upgraded docker engine to the latest release 17.03.0-ce and artifactory failed to start. This is the error that i see in the logs.
I searched google and i could not find even one result that contains this error. I had to delete the data in the volumes and start from scratch. But it's annoying that there is not a single google result for that error and it does not make any sense to me (as artifactory is not using SSL on the listeners...)
Any hints will be appreciated. I logged the issue here as i have no idea where to log it.
Thanks

This error is from a fairly new feature in Artifactory, noting that the already registered key (in DB) is not matching the new key found on file system.
This sounds like there was a change in the mount volume used by Artifactory after the Docker upgrade.
This caused Artifactory to recreate an access key, and it does not match the already registered one in DB.
Are you aware that on 5.X, there is now a single mount volume for all data + config?
I can't find a reason why it will happen after the docker upgrade...

Yes, am aware (i read it after the error). What i did was to keep the 4 volumes, stop/delete the 4.x container, change the image to the 5.x container and start it. Then it was working untill i had to stop docker to upgrade it. When i started artifactory after the docker upgrade it did not work.
SO i was forced to delete all 4 volumes, create a single one and move on. It would be nice to add some documentation on this feature and what do to when you hit this error.
Thanks

You are right - this should be better documented!
I will work on improving our Wiki and also add a note about the error you enountered.
Last request - can you share the command line you used to run Artifactory 4 and the 5? I want to confirm the cause.

I just use docker compose:
artifactory:
image: docker.bintray.io/jfrog/artifactory-oss:5.1.0
container_name: artifactory
mem_limit: 12g
memswap_limit: 12g
restart: always
environment:

TERM=linux
ports:
"8081:8081"
volumes:
/docker/artifactory/:/var/opt/jfrog/artifactory

The docker-compose section for the 4.x version is the same except:

I specified 4 volumes
The version of the image was 4.xx

Thanks

@pgeorgiev333  - I wanted to let you know we are documenting a recovery process for such an error, so it will come up in formal searches in our Wiki.
We were unable to reproduce your error, but are still working on trying to figure it our.
Once documentation is ready, I will close this issue.

Thanks
On Wed, Mar 15, 2017 at 2:07 PM, Eldad Assis<EMAIL_ADDRESS>wrote:

@pgeorgiev333 https://github.com/pgeorgiev333 - I wanted to let you
know we are documenting a recovery process for such an error, so it will
come up in formal searches in our Wiki.
We were unable to reproduce your error, but are still working on trying to
figure it our.
Once documentation is ready, I will close this issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/JFrogDev/artifactory-docker-examples/issues/12#issuecomment-286722775,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQK4tmGEIlT3ErDJDsJtIdgTcQnJsBaKks5rl9SNgaJpZM4MYKFI
.

We have a formal documentation for this error now.
Look in https://www.jfrog.com/confluence/display/RTF/Access+Tokens#AccessTokens-Troubleshooting
Closing.

Awesome! Thanks

@eldada The troubleshooting has us save the keys from the "first Artifactory instance."  Where are the keys on that instance?  I'm attempting to upgrade from 4.16.1, and havent been able to get it started successfully.  Currently at the key-mismatch error, but am puzzled because the docs make it sound like the keys didnt exist in 4.x.

The troubleshooting worked once i set permissions properly on all the files referenced by the troubleshooting steps.
On a related note, i'm happy that it's finally working, but encountered file-permission issues at about every step.  I'm not sure why.
Anyway, glad i found this!

@elordahl - thanks for the feedback. I'll pass it on to try and improve the troubleshooting section.

@eldada Please add the directory where this access token is stored to the list at (and other places applicable) https://www.jfrog.com/confluence/display/RTF/Installing+Artifactory
From what I gather it's $ARTIFACTORY_HOME/access/etc/keys?

@magnusart - you can see it here: https://www.jfrog.com/confluence/display/RTF/Access+Tokens#AccessTokens-SettingthePrivateKeyandRootCertificate
Is this not enough?

@eldada I've been trying to set up Artifactory in a containerized environment. I'm not going to read through all available documentation in detail and piece together different failure scenarios.
When I read the installation documentation that contains a directory structure title I expect to find all relevant folders on the root level with a comment. Access folder is not there.

@magnusart - I agree. It should also be listed there. I will work on adding it.

Thanks! @eldada

Done!

We had the problem too :
This happened when you start artifactory 5 with the 4 volumes layout.
Artifactory starts and create a new ephemeral volumes with a /access folder containing keys that it migrates from somewhere.
As long as you don't restart the container, everything works fine.
When you restart the container after the migration, the /access cease to exists because the volume is ephemeral and unexpected issues arise. To solve it, we had to :

Move to the new "one volume" layout.
Import the /access folder from the deceased volume (/var/lib/docker/volumes/{VOLUME ID}/_data/access/etc/keys/) with the right chmod(important)

This way we didn't have to start from scratch

Thx @fbouliane for the addition!


No raster loading

@ian29 is getting this error w/ fillfacets (while I am not w/ the same inputs) - the most probable reason is an empty array is loading from the raster.
Traceback (most recent call last):
  File "/usr/local/bin/makesurface", line 9, in <module>
    load_entry_point('makesurface==0.2.2dev', 'console_scripts', 'makesurface')()
  File "/usr/local/lib/python2.7/site-packages/click/core.py", line 610, in __call__
    return self.main(*args, **kwargs)
  File "/usr/local/lib/python2.7/site-packages/click/core.py", line 590, in main
    rv = self.invoke(ctx)
  File "/usr/local/lib/python2.7/site-packages/click/core.py", line 936, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/local/lib/python2.7/site-packages/click/core.py", line 782, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/lib/python2.7/site-packages/click/core.py", line 416, in invoke
    return callback(*args, **kwargs)
  File "/usr/local/lib/python2.7/site-packages/makesurface/scripts/cli.py", line 83, in fillfacets
    makesurface.fillfacets(input, sampleraster, noproject, output, bidxs, zooming, batchprint, outputgeojson, color)
  File "/usr/local/lib/python2.7/site-packages/makesurface/__init__.py", line 10, in fillfacets
    fill_facets.fillFacets(infile, sampleRaster, noproject, output, band, zooming, batchprint, outputGeom, color)
  File "/usr/local/lib/python2.7/site-packages/makesurface/scripts/fill_facets.py", line 167, in fillFacets
    rasArr = upsampleRaster(rasArr, featDims, zooming)
  File "/usr/local/lib/python2.7/site-packages/makesurface/scripts/fill_facets.py", line 105, in upsampleRaster
    zoomFactor = int(featDims / min(rasArr.shape[0:2])) * 3
ZeroDivisionError: integer division or modulo by zero

Figure out the cause of this error
Better handle these kind of errors

Cause was invalid raster windows. Fixed in https://github.com/mapbox/make-surface/pull/81

\o/


attempt to fix coplanar on subtraction

Trying to Fixes #87

Thanks! I need to think about the solution more. It's possible that a better solution is to detect coplanar faces ahead of time and track them separately so there's no risk of handling them incorrectly due to numerical precision in the existing clip method.

Fixed in #98


Compile in a non-async determined order

This change removes the task-based mechanism to get dependencies for
compilation. This ends up removing a lot of the async that was need
before and allows us to know that dependencies are available when
compilation is occuring.

@birojnayak this does something similar to what you were doing in yours, but reworks the ordering of the parsers. LMK what you think


Updating copyright to Trustees

The pull request appears to be brutal but it is not actually that long. I'd like to get this merged quickly since most of it has already been reviewed. I made these commits before implementing the new pull request model (small, bite-sized, single broad change) so lets get this behind us! Here are the changes:

Change
File
Comments

A
.codeclimate.yml
standard codeclimate analysis for python

A
scripts/util/get_y_class.py
renamed the knn.py script

D
scripts/util/knn.py
name no longer meaningful

M
LICENSE
removed my name and added Trustees

M
README.md
cleaned up codeclimate suggestions

edit - It looks like I had similar issues with this pull request as I have had with one in the TAD pathways project. Once I merged with upstream, the changes I thought I was making were only changes to copyright language:

Change
File
Comments

M
scripts/util/get_y_class.py
removed copyright claim

M
LICENSE
removed my name and added Trustees

M
README.md
removed copyright claim

There we go, that's better!

Files changed view just shows three small changes. Assuming that's right :+1:

Make sure you squash merge.
You can rebase now if you want to clean up the changed files list.


V3: Support for TypeScript plugins

Added esbuild-register to workers

Note: Plugins written in TypeScript that are type: module will not work until @atlaspack/core is migrated to either TypeScript or type: module.
I looked at converting just the worker code to be esm - but that's not viable due to the Flow. I guess we don't have any esm plugins anyway so it's probably fine for now.

Moved this to the consumer site


i  got those errors after buiding the project to android and i uploaded it into unity.

here is the screen shot of the errors can you guide me further how it runs..
here is some errors:
Error 1:
Assets/MediaPipe/SDK/Scripts/Annotation/AnnotationController.cs(3,32): error CS0234: The type or namespace name 'LocationData' does not exist in the namespace 'Mediapipe' (are you missing an assembly reference?)
Error 2:
Assets/MediaPipe/SDK/Scripts/Framework/CalculatorGraphConfig.cs(1,20): error CS0400: The type or namespace name 'Google' could not be found in the global namespace (are you missing an assembly reference?)
others are also like that.....

Did you run make install?

okay thank you it is installed\


1.12.1 light blue screen bug when looking at the schematica.

video When I look at the schematica in 1.12.1 this happends.

Do you have any other mods installed?

Closing due to lack of feedback.


1.83.1 ws1 cannot run code .

VS Code Version: 1.83.1 (via custom chocolatey)
OS Version: windows (windows server 2019 datacenter 10.0.17763 via amazon workspaces)
Using WSL1 Ubuntu

Steps to Reproduce:

Using the env above: upgrade vscode from 1.80 to 1.83.1
From wsl1 ubuntu terminal: try to run code path/to/workspace-file
Error:

node:net:413
      throw errnoException(err, 'open');
      ^

Error: open EISDIR
    at new Socket (node:net:413:13)
    at createWritableStdioStream (node:internal/bootstrap/switches/is_main_thread:78:18)
    at process.getStderr [as stderr] (node:internal/bootstrap/switches/is_main_thread:170:12)
    at console.get (node:internal/console/constructor:220:44)
    at console.value (node:internal/console/constructor:347:50)
    at console.warn (node:internal/console/constructor:382:61)
    at Object.d [as onError] (C:\Program Files\Microsoft VS Code\resources\app\out\cli.js:1:7727)
    at g.onError (C:\Program Files\Microsoft VS Code\resources\app\out\cli.js:1:12590)
    at d._onLoadError (C:\Program Files\Microsoft VS Code\resources\app\out\cli.js:3:7877)
    at u (C:\Program Files\Microsoft VS Code\resources\app\out\cli.js:3:9082)
    at Object.errorback (C:\Program Files\Microsoft VS Code\resources\app\out\cli.js:3:9457)
    at c.triggerErrorback (C:\Program Files\Microsoft VS Code\resources\app\out\cli.js:1:13508)
    at C:\Program Files\Microsoft VS Code\resources\app\out\cli.js:1:13259
    at n.load (C:\Program Files\Microsoft VS Code\resources\app\out\cli.js:2:1654)
    at c.load (C:\Program Files\Microsoft VS Code\resources\app\out\cli.js:1:13214)
    at u (C:\Program Files\Microsoft VS Code\resources\app\out\cli.js:3:9338)
    at Object.errorback (C:\Program Files\Microsoft VS Code\resources\app\out\cli.js:3:9457)
    at c.triggerErrorback (C:\Program Files\Microsoft VS Code\resources\app\out\cli.js:1:13508)
    at C:\Program Files\Microsoft VS Code\resources\app\out\cli.js:1:13259
    at n.load (C:\Program Files\Microsoft VS Code\resources\app\out\cli.js:2:1654)
    at c.load (C:\Program Files\Microsoft VS Code\resources\app\out\cli.js:1:13214)
    at u (C:\Program Files\Microsoft VS Code\resources\app\out\cli.js:3:9338)
    at d._loadModule (C:\Program Files\Microsoft VS Code\resources\app\out\cli.js:3:9466)
    at d._resolve (C:\Program Files\Microsoft VS Code\resources\app\out\cli.js:4:452)
    at d.defineModule (C:\Program Files\Microsoft VS Code\resources\app\out\cli.js:3:5561)
    at g (C:\Program Files\Microsoft VS Code\resources\app\out\cli.js:4:1741)
    at m (C:\Program Files\Microsoft VS Code\resources\app\out\cli.js:2:2448)
    at Object.<anonymous> (C:\Program Files\Microsoft VS Code\resources\app\out\vs\code\node\cli.js:31:28)
    at Object.<anonymous> (C:\Program Files\Microsoft VS Code\resources\app\out\vs\code\node\cli.js:31:27003)
    at n._createAndEvalScript (C:\Program Files\Microsoft VS Code\resources\app\out\cli.js:2:2492)
    at C:\Program Files\Microsoft VS Code\resources\app\out\cli.js:2:2133
    at FSReqCallback.readFileAfterClose [as oncomplete] (node:internal/fs/read_file_context:68:3) {
  errno: -4068,
  code: 'EISDIR',
  syscall: 'open'
}

Node.js v18.15.0

NOTE: Expected to be fixed by #192506 but not

Do you still see the issue?


Github Releases Download counter

possible combinations:

/github/downloads/:user/:repo/latest/total.svg
/github/downloads/:user/:repo/:release_id/total.svg
/github/downloads/:user/:repo/:release_id/:asset_name.svg

How about a combination that counts all downloads of all releases?
Something like /github/downloads/:user/:repo/all/total.svg.

@Alexander01998 I thought about that, but that could be heavy on resources as it would have to iterate over releases backward in history and make multiple HTTP calls to go through github pagination ...
happy to add it (real-simple)  if server maintainers think the server can handle it...

Computation-wise, I agree with ahmadnassri. That operation would be way cleaner to add on github's side. Were they to give direct access to that information, we could display it.

It's OK, I can make my own counter for my own repos.

Thanks a lot for your contribution!

@espadrine all done, though see my note about map vs. forEach for future reference.

@espadrine made some minor adjustments, mainly calling releases by the friendlier/commonly used tag name, rather than release id, which requires the author to call the API to find ...

added more examples as per your suggestion.

I believe this is now final / ready.
cheers.

Thanks a lot!

:+1:

@ahmadnassri

It would have to iterate over releases backward in history and make multiple HTTP calls.

Just curious: why multiple HTTP calls? This API call returns information on all releases in a single response. Or parsing this JSON is also a time-consuming operation?

Or parsing this JSON is also a time-consuming operation?

When having thousands of repos  each having hundred of releases, it can indeed be very time-consuming.
I made a counter for one of my own repos using Google Apps Script.
If you really need a counter for all downloads, you can use that: https://gist.github.com/Alexander01998/d5bda1558cfbc20a8ae3

Just curious: why multiple HTTP calls? This API call returns information on all releases in a single response. Or parsing this JSON is also a time-consuming operation?

@kefir500 you are correct, I had the impression at the time (for whatever reason) that it was paginated (and honestly it should be, some of those releases count in hundreds) which would have meant many many HTTP calls ...
and as @Alexander01998 pointed out, even then there would be a good amount of processing needed for a big / large project with many releases, we already know the service has been struggling with downtime recently, and a big refactor is due ..

and again, happy to add a big loop that goes through all releases and calculates the total if maintainers think its a good idea ...

I believe this is the subject of an ongoing PR.

ah yes: https://github.com/badges/shields/pull/535


bug at join existing organization in cpanel

https://openhubd.mymagic.my/organization/join?realm=cpanel

issue fixed


Preparation of test cases for Exception List Dashboard

Prepare the functional test cases for the below exception list reports

Periodic Assessment Test Exception
Semester Assessment Test Exception
Download Exception List
Student Attendance Exception Report
Teacher Attendance Exception Report

[ ] Periodic Assessment Test Exception

[ ] Semester Assessment Test Exception

[ ] Download Exception List

Completed preparation of test cases for

[ ] Student Attendance Exception Report

@RNarmatha this task completed please review the test cases let me know if any changes are required

There are some modifications that need to be taken care

Done with modifications


Feature request: set default headers for every request

And #177 can be resolved once this is implemented.

@seanmonstar If this request is acceptable, I'd like to work on it.

I'd love to hear what you think an exposed API would look like, first. This would be like a set of headers stored in the Client that are applied to all requests?

Yeah, as you said, we could add something like
Client::set_default_headers(mut self, headers: ::header::Headers) -> Self;

which saves the default headers in Client instance, and request::builder can inspect client and set the default headers of the request.
To be specific, I plan to set default headers as the following:
let mut client = reqwest::Client::new();
client.set_default_headers(headers) // for simplicity, only a set of headers is allowed for now
    .post(url)
    .body(body)
    .send()?

Alternatively, we could pass an option struct to the constructor of Client, like
let client = reqwest::Client::new(RequestOption {
    headers,
    // base_url,  // I think we could add this later
});
client.get(url).send()?;
...

and the Client should be extend as something like:
Client {
    inner: ClientHandle,
    headers: ::header::Headers,
}

then we could rewrite request::builder as:
pub fn builder(client: Client, req: ::Result<Request>) -> RequestBuilder {
    match req {
        Ok(mut req) => {
            req.headers_mut().extend(client.headers.iter());
            RequestBuilder {
                client: client,
                request: Some(req),
                err: None,
            },
        },
        Err(err) => RequestBuilder {
            client: client,
            request: None,
            err: Some(err)
        },
    }
}

How is it look like? Did I miss something?

The Client can be cloned and given to different threads, so it's probably best to not be able to mutate the Client itself. We do have a ClientBuilder, however. That seems like a fine place to customize  some default headers.

Perhaps we could save the headers in async_impl::client::ClientRef ?

As the eventually place store them, sure. They should probably reside right next to the other stuff that is needed to make a request.


zero gradient

Can this code be used for training? I printed gradients of weights of the last layer, and they are always zero.

I never met this problem...

If you set aggr_funcs or dist_func to "hard", then it's normal that there is no gradient, since standard rendering does not have gradient. Otherwise it's kind of weird.

I think it is because of very sharp sigmoid function because of sigma value. close the issue.

Did you check this code can be used in training stage? I successfully integrated this code to my project, however it encounters cuda illegal memory access when backwarding. When I use nerual 3D mesh renderer (https://github.com/daniilidis-group/neural_renderer) and rest of the code is exactly same, it is alright. Can you give me some help?

One possible reason I think of is the texture format. We use a different texture format than NMR, which is more memory efficient. Can you please make sure the texture is the same in the demo?

Thank you for your help. I've used vertex texture type and just removed RGB part in cuda code because only silhouette part is what I need. Problem resolved.

You mean the right format is 'vetex'?
In your demo, texture format is 'surface', and the format meaning seems same with NMR. Can you explain the difference of texture format more clear?

No. I think using vertex as a texture type was the reason of error. It seems like vertex means RGB colors are defined for each vertex. On the other hand, surface texture is defined as a small patch.

I use 'vertex' or 'surface' format, and view textures's gradient. If using 'vertex' format, nearly 3000 texture points has gradient, others remain zero. If using 'surface' format, only one texture part has gradient...

To correct this, when using surface format, only some fixed texture parts have gradients (their index numbers remain unchanged during training).

Oh I only checked grads of face_vertex part. I've not checked grads of texture parts.

Vertex always have gradient. Did you check grads of silhouette parts in your experiment? @mks0601
BTW, I'm still confused on the texture difference between NMR and SoftRas... In my mind, they have same texture format. @mks0601 @ShichenLiu

What I mean was silhouette part. It is fine.

Hi @mehameha998 , NMR using texture format as [num_faces, texture_size, texture_size, texture_size, 3], basically they project the texture space into a 3D cube. In our implementation, we setup a UV coordinate for each face, and project the texture into [num_faces, texture_size^2, 3]. I will push a pdf with detailed explanation later for better understanding.

To correct this, when using surface format, only some fixed texture parts have gradients (their index numbers remain unchanged during training).

Hi, I met the same problem, have you found a solution?

I solve this by setting minimum and maximum depth value (maybe near and far?) based on my case.


ELF support

Want to be able to run capa against Linux ELF files and get meaningful results. This is the master issue for tracking related features and steps.

we'll also want to add support for lightweight file limitation detection for ELF, like for PE here: https://github.com/fireeye/capa/blob/v2.0.0/capa/main.py#L874-L895

we may want to collect a meaningful FLIRT signature set for Linux programs compiled against glibc, musl, etc.

[ ] changelog
[ ] OS-specific rule features

this has been implemented


Green screen using Nvidia hardware transcoding

Hey, I'm using go2rtc 1.8.1 with Frigate running in a Docker on Unraid. I've passed through a 1050Ti to the container and Frigate can see and use it but I am trying to use go2rtc to transcode from h265 down to h264 for a Reolink Duo 2 camera but I get a green screen. When I remove the hardware flag (either generic or specified to cuda) it works fine using the cpu. The Reolink is set to 4096x1536 resolution.
Any suggestions what might be failing?
go2rtc:
  log:
    exec: trace
  streams:
    frontduo:
      - "ffmpeg:rtsp://user:password@192.168.x.xx:554/h265Preview_01_main#video=h264#audio=copy#audio=opus#hardware=cuda"

Input #0, rtsp, from 'rtsp://user:password@192.168.x.xx:554/h265Preview_01_main':
2023-10-29 18:59:50.145947295    Metadata:
2023-10-29 18:59:50.145952044      title           : Session streamed by "preview"
2023-10-29 18:59:50.145956793      comment         : h265Preview_01_main
2023-10-29 18:59:50.145961962    Duration: N/A, start: 0.000000, bitrate: N/A
2023-10-29 18:59:50.145966781    Stream #0:0: Video: hevc (Main), yuv420p(tv), 4096x1536, 20 fps, 16.67 tbr, 90k tbn
2023-10-29 18:59:50.145971879    Stream #0:1: Audio: aac (LC), 16000 Hz, mono, fltp
2023-10-29 18:59:50.231351170  frame=  999 fps= 12 q=-1.0 size=N/A time=00:01:23.90 bitrate=N/A speed=1.04x
frame=  740 fps= 12 q=-1.0 size=N/A time=00:01:03.14 bitrate=N/A speed=1.06x
Stream mapping:
2023-10-29 18:59:50.231358783    Stream #0:0 -> #0:0 (hevc (native) -> h264 (h264_nvenc))
2023-10-29 18:59:50.231363532    Stream #0:1 -> #0:1 (aac (native) -> aac (native))
2023-10-29 18:59:50.231368700    Stream #0:1 -> #0:2 (aac (native) -> opus (libopus))
2023-10-29 18:59:50.231373869  Press [q] to stop, [?] for help
2023-10-29 18:59:50.234352681  [libopus @ 0x5570d876c900] No bit rate set. Defaulting to 64000 bps.
2023-10-29 18:59:50.271900416  frame=  601 fps= 10 q=-1.0 size=N/A time=00:01:03.61 bitrate=N/A speed=1.07x
[hevc @ 0x5570d876d400] Could not find ref with POC 14
2023-10-29 18:59:50.362689425  18:59:50.362 DBG [exec] run launch=1.659828991s
2023-10-29 18:59:50.363004969  Output #0, rtsp, to 'rtsp://<IP_ADDRESS>:8554/6af4dbcd022eb644c625898f70252562':
2023-10-29 18:59:50.363052322    Metadata:
2023-10-29 18:59:50.363124259      title           : Session streamed by "preview"
2023-10-29 18:59:50.363196615      comment         : h265Preview_01_main
2023-10-29 18:59:50.363268482      encoder         : Lavf59.27.100
2023-10-29 18:59:50.363462571    Stream #0:0: Video: h264 (High), cuda(tv, progressive), 4096x1536, q=2-31, 2000 kb/s, 16.67 fps, 90k tbn
2023-10-29 18:59:50.363536813      Metadata:
2023-10-29 18:59:50.363654077        encoder         : Lavc59.37.100 h264_nvenc
2023-10-29 18:59:50.363756255      Side data:
2023-10-29 18:59:50.363912910        cpb: bitrate max/min/avg: 0/0/2000000 buffer size: 4000000 vbv_delay: N/A
2023-10-29 18:59:50.364081856    Stream #0:1: Audio: aac (LC), 16000 Hz, mono, fltp, 69 kb/s (default)
2023-10-29 18:59:50.364159381      Metadata:
2023-10-29 18:59:50.364280975        encoder         : Lavc59.37.100 aac
2023-10-29 18:59:50.364432810    Stream #0:2: Audio: opus, 16000 Hz, mono, flt, 64 kb/s
2023-10-29 18:59:50.364509566      Metadata:
2023-10-29 18:59:50.364631579        encoder         : Lavc59.37.100 libopus
2023-10-29 18:59:50.818532276  frame=   24 fps=0.0 q=30.0 size=N/A time=00:00:01.40 bitrate=N/A dup=23 drop=0 speed= 405x
frame=  996 fps= 12 q=-1.0 size=N/A time=00:01:23.64 bitrate=N/A speed=1.04x
frame= 1005 fps= 12 q=-1.0 size=N/A time=00:01:24.41 bitrate=N/A speed=1.04x
frame=  746 fps= 12 q=-1.0 size=N/A time=00:01:03.66 bitrate=N/A speed=1.06x
frame=  607 fps= 10 q=-1.0 size=N/A time=00:01:04.19 bitrate=N/A speed=1.07x
Impossible to convert between the formats supported by the filter 'Parsed_null_0' and the filter 'auto_scale_0'
2023-10-29 18:59:50.818802912  Error reinitializing filters!
2023-10-29 18:59:50.818810455  Failed to inject frame into filter network: Function not implemented
2023-10-29 18:59:50.818815274  Error while processing the decoded data for stream #0:0
2023-10-29 18:59:50.863749802  [aac @ 0x5570d876b400] Qavg: 9930.156
2023-10-29 18:59:50.863756926  [aac @ 0x5570d876b400] 2 frames left in the queue on closing
2023-10-29 18:59:50.863762164  [libopus @ 0x5570d876c900] 1 frames left in the queue on closing
2023-10-29 18:59:50.876560491  Conversion failed!
2023-10-29 18:59:50.884875130  18:59:50.884 WRN github.com/AlexxIT/go2rtc/internal/streams/producer.go:171 > error=EOF url=ffmpeg:rtsp://user:password@192.168.x.xx:554/h265Preview_01_main#video=h264#audio=aac#audio=opus#hardware
2023-10-29 18:59:50.885058674  18:59:50.884 DBG [exec] run url="exec:ffmpeg -hide_banner -hwaccel cuda -hwaccel_output_format cuda -allowed_media_types video+audio -fflags nobuffer -flags low_delay -timeout 5000000 -user_agent go2rtc/ffmpeg -rtsp_flags prefer_tcp -i rtsp://user:password@192.168.x.xx:554/h265Preview_01_main -map 0:v:0? -c:v:0 h264_nvenc -g 50 -bf 0 -profile:v:0 high -level:v:0 auto -preset:v:0 p2 -tune:v:0 ll -map 0:a:0? -c:a:0 aac -map 0:a:0? -c:a:1 libopus -application:a:1 lowdelay -frame_duration 20 -min_comp 0 -user_agent ffmpeg/go2rtc -rtsp_transport tcp -f rtsp {output}"
2023-10-29 18:59:50.922178768  18:59:50.922 TRC [exec] close url="exec:ffmpeg -hide_banner -hwaccel cuda -hwaccel_output_format cuda -allowed_media_types video+audio -fflags nobuffer -flags low_delay -timeout 5000000 -user_agent go2rtc/ffmpeg -rtsp_flags prefer_tcp -i rtsp://user:password@192.168.x.xx:554/h265Preview_01_main -map 0:v:0? -c:v:0 h264_nvenc -g 50 -bf 0 -profile:v:0 high -level:v:0 auto -preset:v:0 p2 -tune:v:0 ll -map 0:a:0? -c:a:0 aac -map 0:a:0? -c:a:1 libopus -application:a:1 lowdelay -frame_duration 20 -min_comp 0 -user_agent ffmpeg/go2rtc -rtsp_transport tcp -f rtsp {output}"
2023-10-29 18:59:52.321881025  frame= 1002 fps= 12 q=-1.0 size=N/A time=00:01:24.15 bitrate=N/A speed=1.04x
frame=  753 fps= 12 q=-1.0 size=N/A time=00:01:04.23 bitrate=N/A speed=1.06x
frame= 1012 fps= 12 q=-1.0 size=N/A time=00:01:24.99 bitrate=N/A speed=1.04x
frame=  613 fps= 10 q=-1.0 size=N/A time=00:01:04.70 bitrate=N/A speed=1.07x
frame= 1008 fps= 12 q=-1.0 size=N/A time=00:01:24.67 bitrate=N/A speed=1.04x
frame= 1019 fps= 12 q=-1.0 size=N/A time=00:01:25.50 bitrate=N/A speed=1.04x
frame=  760 fps= 12 q=-1.0 size=N/A time=00:01:04.74 bitrate=N/A speed=1.05x
frame=  618 fps= 10 q=-1.0 size=N/A time=00:01:05.21 bitrate=N/A speed=1.07x
frame= 1014 fps= 12 q=-1.0 size=N/A time=00:01:25.24 bitrate=N/A speed=1.04x
frame= 1025 fps= 12 q=-1.0 size=N/A time=00:01:26.01 bitrate=N/A speed=1.04x
frame=  766 fps= 12 q=-1.0 size=N/A time=00:01:05.26 bitrate=N/A speed=1.05x
Input #0, rtsp, from 'rtsp://user:password@192.168.x.xx:554/h265Preview_01_main':
2023-10-29 18:59:52.321888568    Metadata:
2023-10-29 18:59:52.321893318      title           : Session streamed by "preview"
2023-10-29 18:59:52.321898556      comment         : h265Preview_01_main
2023-10-29 18:59:52.321939273    Duration: N/A, start: 0.000000, bitrate: N/A
2023-10-29 18:59:52.321944442    Stream #0:0: Video: hevc (Main), yuv420p(tv), 4096x1536, 20 fps, 16.67 tbr, 90k tbn
2023-10-29 18:59:52.321971889    Stream #0:1: Audio: aac (LC), 16000 Hz, mono, fltp
2023-10-29 18:59:52.406434300  frame=  624 fps= 10 q=-1.0 size=N/A time=00:01:05.72 bitrate=N/A speed=1.06x
Stream mapping:
2023-10-29 18:59:52.406443729    Stream #0:0 -> #0:0 (hevc (native) -> h264 (h264_nvenc))
2023-10-29 18:59:52.406451272    Stream #0:1 -> #0:1 (aac (native) -> aac (native))
2023-10-29 18:59:52.406458326    Stream #0:1 -> #0:2 (aac (native) -> opus (libopus))
2023-10-29 18:59:52.406463564  Press [q] to stop, [?] for help
2023-10-29 18:59:52.408849980  [libopus @ 0x5634c318fd40] No bit rate set. Defaulting to 64000 bps.
2023-10-29 18:59:52.435804076  [hevc @ 0x5634c3132800] Could not find ref with POC 2
2023-10-29 18:59:52.521282751  18:59:52.521 DBG [exec] run launch=1.636223659s
2023-10-29 18:59:52.521542492  Output #0, rtsp, to 'rtsp://<IP_ADDRESS>:8554/6af4dbcd022eb644c625898f70252562':
2023-10-29 18:59:52.521550524    Metadata:
2023-10-29 18:59:52.521560930      title           : Session streamed by "preview"
2023-10-29 18:59:52.521568054      comment         : h265Preview_01_main
2023-10-29 18:59:52.521575667      encoder         : Lavf59.27.100
2023-10-29 18:59:52.521614499    Stream #0:0: Video: h264 (High), cuda(tv, progressive), 4096x1536, q=2-31, 2000 kb/s, 16.67 fps, 90k tbn
2023-10-29 18:59:52.521621064      Metadata:
2023-10-29 18:59:52.521628607        encoder         : Lavc59.37.100 h264_nvenc
2023-10-29 18:59:52.521636150      Side data:
2023-10-29 18:59:52.521643763        cpb: bitrate max/min/avg: 0/0/2000000 buffer size: 4000000 vbv_delay: N/A
2023-10-29 18:59:52.521651305    Stream #0:1: Audio: aac (LC), 16000 Hz, mono, fltp, 69 kb/s (default)
2023-10-29 18:59:52.521657032      Metadata:
2023-10-29 18:59:52.521662759        encoder         : Lavc59.37.100 aac
2023-10-29 18:59:52.521667858    Stream #0:2: Audio: opus, 16000 Hz, mono, flt, 64 kb/s
2023-10-29 18:59:52.521672677      Metadata:
2023-10-29 18:59:52.521708575        encoder         : Lavc59.37.100 libopus
2023-10-29 18:59:53.688096765  frame=   24 fps=0.0 q=30.0 size=N/A time=00:00:01.46 bitrate=N/A dup=23 drop=0 speed= 528x
frame= 1021 fps= 12 q=-1.0 size=N/A time=00:01:25.69 bitrate=N/A speed=1.04x
frame=  772 fps= 12 q=-1.0 size=N/A time=00:01:05.77 bitrate=N/A speed=1.05x
frame= 1031 fps= 12 q=-1.0 size=N/A time=00:01:26.52 bitrate=N/A speed=1.04x
frame=  629 fps= 10 q=-1.0 size=N/A time=00:01:06.23 bitrate=N/A speed=1.06x
frame=   34 fps=0.0 q=29.0 size=N/A time=00:00:02.04 bitrate=N/A dup=23 drop=0 speed=3.97x
frame= 1027 fps= 12 q=-1.0 size=N/A time=00:01:26.20 bitrate=N/A speed=1.04x
frame= 1038 fps= 12 q=-1.0 size=N/A time=00:01:27.03 bitrate=N/A speed=1.04x
frame=  779 fps= 12 q=-1.0 size=N/A time=00:01:06.28 bitrate=N/A speed=1.05x
frame=  635 fps= 10 q=-1.0 size=N/A time=00:01:06.81 bitrate=N/A speed=1.06x
frame=   42 fps= 41 q=28.0 size=N/A time=00:00:02.54 bitrate=N/A dup=23 drop=0 speed=2.47x
frame= 1034 fps= 12 q=-1.0 size=N/A time=00:01:26.71 bitrate=N/A speed=1.04x
Impossible to convert between the formats supported by the filter 'Parsed_null_0' and the filter 'auto_scale_0'
2023-10-29 18:59:53.688384513  Error reinitializing filters!
2023-10-29 18:59:53.688394360  Failed to inject frame into filter network: Function not implemented
2023-10-29 18:59:53.688401973  Error while processing the decoded data for stream #0:0
2023-10-29 18:59:53.734252473  [aac @ 0x5634c3138480] Qavg: 44659.863
2023-10-29 18:59:53.734259597  [aac @ 0x5634c3138480] 2 frames left in the queue on closing
2023-10-29 18:59:53.734294588  [libopus @ 0x5634c318fd40] 1 frames left in the queue on closing
2023-10-29 18:59:53.750277551  Conversion failed!
2023-10-29 18:59:53.757749062  18:59:53.757 WRN github.com/AlexxIT/go2rtc/internal/streams/producer.go:171 > error=EOF

@BurningTheSky I have a similar problem with the same camera, how did you fix it?

I don't remember I'm afraid, I think it was either the go2rtc version or that the camera didn't support the resolution at that codec. I sent the camera back so I don't have the config anymore.


Added an explanation and use case for customKey/customValue

I didn't really understand this till it suddenly clicked and I started using it.

I also withdraw an earlier proposal that makes no sense now I figured out I should be using customKey customValue instead.

We can certainly refine these together.

Reviewing this.

  So I thought I’d wait until I got back to thinking straight.   I’ll do my best to look and merge today or tomorrow. Before the weekend.

@daveajones this has been sitting so long it's now getting conflicts. The main thing I added was a very useful section on customKey customValue. I also added a nice regex.
My own repo is now a mess and I'm not sure how to recover and fix at this point.

I think I fixed the conflict.

Sorry, I've just been way behind on this type of work and needed to have a fresh brain to review this since it was a large PR.


bert and roberta models

Hi,
BERT-base and RoBERTa-base and most of the other models are not available now (anymore).
Is it planned to add them soon? Is it possible to use older versions of those?
Cheers,

Hi!
What issue are you seeing?
The models on the hub that end with -ipu like bert-base-ipu and roberta-base-ipu are intended only as IPUConfig files. The usage is:
from optimum.graphcore import IPUConfig
ipu_config = IPUConfig.from_pretrained("Graphcore/roberta-base-ipu")

For the weights of the actual model you can use the same weights as you would on CPU or GPU - e.g. bert-base-uncased.
Does this answer your question?

Yeah it can be initialized with those weights. Graphcore/bert-large-uncased is an equivalent version bert-large-uncased  that was pretrained on IPU. But either version will work for fine-tuning or inference on IPU.
The "models" on the hub that end with -ipu are intended just as IPUConfigs, if you want to use those, though you can  easily create your own if you want customization.


Add command to report classes without a repr

crepr report-missing <file_name>

The output should be something like:
<filename>
line number: class name

It reports all classes that do not have a __repr__  and crepr would be able to add one.

Hello @cleder
Was trying to get this issue done but there are some issues while I try to run crepr for the tests/run_test.py file.
I tried modifying crepr.py and added a report-missing method to it and all the methods work really well when it comes to custom generated test file by me, but the error given below still persists only for the run_test.py file, any caveat on how to run tests here, is there something I'm missing?

Here's the colab notebook for testing crepr - https://colab.research.google.com/drive/1Hi3NJjNhJ-IXCP7LB5PDXiJCAH_drBXW#scrollTo=l7XHJnueqF5F
Haven't made the changes in this notebook will add them after getting your input on the same. Thanks!:)

Hello @cleder working on this issue for quite sometime, will you please assign this me.

@cleder Apologies for creating these many PRs was unaware of the usage of pre-commit locally. Eventually figured it out here https://github.com/cleder/crepr/pull/63

Turns out with #56 this is a YAGNI and the functionality is covered


Send survey results to group email

Since we have the free version of Survey Monkey, we can not export the report, however I was able to gather the details and added them to the marketing folder:
https://drive.google.com/drive/u/0/folders/0BwjOr-60lG0lODhZX3hSbHpjeFE


compile error

Target dart2js failed: Exception:
../../../software/flutter/.pub-cache/hosted/mirrors.cloud.tencent.com%2547dart-pub/pluto_grid-2.6.1/lib/src/widgets/pluto_scrollbar.dart:433:11:
Error: No named parameter with the name 'supportedDevices'.
supportedDevices: supportedDevices,
^^^^^^^^^^^^^^^^
Error: Compilation failed.

What is your flutter channel?
Currently, PlutoGrid is being tested and developed in the stable channel.

Channel stable, 2.2.2

PlutoGrid 2.5.0 is compatible with flutter 2.5.0 and later versions.
You should be using version 2.4.1 or lower.

Upgrade to the latest flutter 2.8, the problem is solved。


Uncaught Exception after upgrading to recent version

Uncaught exception: /usr/lib/x86_64-linux-gnu/hhvm/extensions/newrelic.so was built for HHVM 3.5, and cannot be loaded with HHVM 3.7\n
hhvm 3.7.1
https://github.com/chregu/hhvm-newrelic-ext/commit/78b4fedb01e3098dfea2845aaf6d9e52c29ba9e3

Well, just recompile it with new version (after installing new version, so now).
BTW, how did you compiled? I always have some errors.
Now this for example.
[ 50%] Building CXX object CMakeFiles/newrelic.dir/newrelic.cpp.o
In file included from /usr/include/hphp/runtime/base/string-data.h:22:0,
                 from /usr/include/hphp/runtime/base/type-string.h:22,
                 from /usr/include/hphp/runtime/base/debuggable.h:19,
                 from /usr/include/hphp/runtime/ext/extension.h:21,
                 from /tmp/newrelic/ocaml-4.02.1/dev/hhvm-newrelic-ext/newrelic.cpp:1:
/usr/include/hphp/util/alloc.h: In function ‘int HPHP::low_mallocx_flags()’:
/usr/include/hphp/util/alloc.h:118:33: error: ‘MALLOCX_ARENA’ was not declared in this scope
   return MALLOCX_ARENA(low_arena);
                                 ^
/usr/include/hphp/util/alloc.h: In function ‘int HPHP::low_dallocx_flags()’:
/usr/include/hphp/util/alloc.h:129:33: error: ‘MALLOCX_ARENA’ was not declared in this scope
   return MALLOCX_ARENA(low_arena);
                                 ^
In file included from /usr/include/hphp/third-party/folly/ThreadLocal.h:53:0,
                 from /usr/include/hphp/third-party/folly/ThreadCachedInt.h:31,
                 from /usr/include/hphp/third-party/folly/AtomicHashArray.h:41,
                 from /usr/include/hphp/third-party/folly/AtomicHashMap.h:93,
                 from /usr/include/hphp/runtime/vm/named-entity.h:26,
                 from /usr/include/hphp/runtime/vm/type-constraint.h:20,
                 from /usr/include/hphp/runtime/vm/preclass.h:29,
                 from /usr/include/hphp/runtime/vm/class.h:32,
                 from /usr/include/hphp/runtime/base/object-data.h:26,
                 from /usr/include/hphp/runtime/base/tv-helpers.h:20,
                 from /usr/include/hphp/runtime/base/type-variant.h:22,
                 from /usr/include/hphp/runtime/base/ini-setting.h:20,
                 from /usr/include/hphp/runtime/ext/extension.h:22,
                 from /tmp/newrelic/ocaml-4.02.1/dev/hhvm-newrelic-ext/newrelic.cpp:1:
/usr/include/hphp/third-party/folly/detail/ThreadLocalDetail.h: In static member function ‘static void folly::threadlocal_detail::StaticMeta<Tag>::reserve(uint32_t)’:
/usr/include/hphp/third-party/folly/detail/ThreadLocalDetail.h:381:67: error: ‘MALLOCX_ZERO’ was not declared in this scope
         success = (xallocx(threadEntry->elements, newByteSize, 0, MALLOCX_ZERO)
                                                                   ^
/usr/include/hphp/third-party/folly/detail/ThreadLocalDetail.h:388:42: error: ‘MALLOCX_ZERO’ was not declared in this scope
                     mallocx(newByteSize, MALLOCX_ZERO))) != nullptr);
                                          ^
make[2]: *** [CMakeFiles/newrelic.dir/newrelic.cpp.o] Error 1
make[1]: *** [CMakeFiles/newrelic.dir/all] Error 2
make: *** [all] Error 2

I accidentally copied:
wget -O /usr/include/hphp/runtime/version.h https://raw.githubusercontent.com/facebook/hhvm/HHVM-3.5/hphp/runtime/version.h
So I needed to copy the correct version:
wget -O /usr/include/hphp/runtime/version.h https://raw.githubusercontent.com/facebook/hhvm/HHVM-3.9/hphp/runtime/version.h
And after that it worked like a charm!


I got 500 error

Hi, I got :
Cannot redefine property: $directus
when I run the app using npm run dev

Oh sorry my bad! I used directus sdk and this modules together and the issue caused! this module saved my life thank you

Hi, can you provide more info on this issue? a reproduction would be helpful.


Angular Material fails to render properly in some browsers

Reproduction
StackBlitz demo - https://angular-ivy-bjdkdj.stackblitz.io
StackBlitz Editable - https://stackblitz.com/edit/angular-ivy-bjdkdj?file=src/app/app.component.ts
Steps to reproduce:

I have used mat-card in my component. Checkout the Stackblitz demo.
Doesn't work on edge and some versions of chrome.

Expected Behavior
It should render the mat-card layout and color properly
Actual Behavior
Some portion of screen is grey
Environment

"@agm/core": "^1.0.0-beta.5",
"@angular-devkit/core": "7.0.2",
"@angular/animations": "^7.0.0",
"@angular/cdk": "^7.0.0",
"@angular/common": "7.0.0",
"@angular/compiler": "7.0.0",
"@angular/core": "7.0.0",
"@angular/flex-layout": "7.0.0-beta.19",
"@angular/material": "^7.0.0",
"@angular/material-moment-adapter": "^7.0.0",
"@angular/platform-browser": "7.0.0",
"@angular/platform-browser-dynamic": "7.0.0",

Browser(s): Chrome, Edge
Operating System: Windows

It seems like you're hitting some sort of browser bug due to the two hex colors with opacity values on .meter-log-fieldset. You should be able to work around it by changing the color to a solid hex color or an rgba one (see https://stackblitz.com/edit/angular-ivy-xdev6z?file=src%2Fapp%2Fapp.component.scss).
I'm closing the issue, because this is a browser bug and we can't do much about it.

Yea this started happening after I updated my chrome version to Version 87.0.4280.66. Before that it was working fine. Anyways thanks for replying.


terminal display issue

version
8.1.950
reproduce
:terminal<CR>
<C-\><C-n>i<C-\><C-n>

content of terminal buffer will not show

I seems bug of vim, I will report it to vim


Update the build to deploy to https://repo.spring.io/release/

Check also the doc.

FTR, the documentation already mentions https://repo.spring.io/release for a release.


Add cross-database macros

This adds the cross-database macros which were introduced in dbt v1,2,0. Most of of the default implementation is working for Exasol. This adds only Exasol specific syntax.

Have to re-create the branch as there are commits which shouldn't be merged...


Parse IEEE draft documents

IEEE draft documents can have the following patterns:
ANSI PC63.10/D14, April 2020
ANSI PC63.12/D12e, January 2015
IEEE 1250 /D11 May 2010
IEEE Std PC37.20.1b/D2
IEEE Std PC37.12.1/D2.0
IEEE Draft P802.11-REVmb/D3.0, March 2010 (Revision of IEEE Std 802.11-2007, as amended by IEEE Std 802.11k-2008, IEEE Std 802.11r-2008, IEEE Std 802.11y-2008, IEEE Std 802.11w-2009 and IEEE Std 802.11n-2009)

@ronaldtse there are document with "r" in identifier, e.g. "IEEE P11073-10101/D3r7, September 2018"
Is it a document revision or draft revision?

@mico I believe D3r7 means "3rd draft, revision 7". The concept of "revision" in the IEEE PubID does not seem to be in common use, but I guess there are 11 instances for 2 documents in the entire library!
IEEE P11073-10101/D3r7, September 2018
IEEE P11073-10101/D4r1, January 2019
IEEE P11073-10101/D5r4, February 2019
IEEE P11073-10101/D7r1, March 2019
IEEE P11073-10101/D9r1, April 2019
IEEE P11073-10471/D2r2, April 2020
IEEE P11073-10471/D3r2, November 2021
IEEE P11073-110101/D8r1, April 2019
IEEE P1242/D8r2, June 2016
IEEE P1242/D8r3, July 2016

I think these two patterns are identical in intention:

D{v}r{r}
D{v}.{r}

There are a lot more of the "dot notation" -- 1439 of them. Let's treat them as the same, and use the "dot notation" as the output format.

@ronaldtse "IEEE P1609.2.1/D12D14"
What is D14 here? Is it another draft? Tried to find out by myself but didn't find this document with "D12D14".

Looking at the examples:
IEEE P1609.2.1/D10, February 2020
IEEE P1609.2.1/D12, June 2020
IEEE P1609.2.1/D12D14, June 2020
IEEE P1609.2.1/D15, August 2020
IEEE P1609.2.1/D4, November 2021
IEEE P1609.2.1/D6, January 2022

I think this is a typo for D14. Let's make this a single time replacement (we should have a set of special cases to replace these errors) so it is not in the parse rules.

I think this is a typo for D14. Let's make this a single time replacement (we should have a set of special cases to replace these errors) so it is not in the parse rules.

There are 7 cases like this:
IEEE P11073-10420/D4D5, March 2020
IEEE P1609.2.1/D12D14, June 2020
IEEE P1653.5/D7d1 November, 2019
IEEE P3002.2/D6D7, April 2017
IEEE P515/D4D5, March 2017
IEEE PC57.143 /D24D25, October 2012
IEEE Unapproved Draft Std P1680/D4D6, Aug 2009

You're right. This is clearly intentional.
When I see these:
P3002.2/D6, Oct 2015
P3002.2/D6D7, Apr 2017
P3002.2/D7, Sept 2017

I think this means it is a "pre-D7 coming from D6".
Given that there are:
P1680/D4D6, Aug 2009
P1609.2.1/D12D14
P352/D4D6, Feb 2016

The pre-draft and intended target draft numbers are not consecutive.
So we have to have parse these two numbers separately.

@ronaldtse should I ignore "REV" here or just leave it as part of number?
IEEE P802-REV/D1.7
IEEE P802-REV/D1.9

@mico leave REV as part of the number.
Look at these two entries, the "REV" is part of the number (the first one in a superseding relationship, the second in a title):
"P802.11-REVma/D5.0 (Superseded by P802.11-REVma_D6.0)"
"P802.11ai/D11.0 Sept 2016 - IEEE Approved Draft Standard for Information technology-Telecommunications and information exchange between systems-Local and metropolitan area networks-Specific requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications: Amendment to IEEE P802.11-REVmc(TM)/D8.0: Fast Initial Link Setup"

@ronaldtse What to do with the documents like:
IEEE Unapproved Draft Std 11073-10471/D02, Feb 2008
IEEE Unapproved Draft Std 11073-10472/D02, Apr 2009
IEEE Active Unapproved Draft Std PC37.59/D11, Jul 2007
IEEE Active Unapproved Draft Std PC57.129/D10, Jul 2007
IEEE Active Unapproved Draft Std PC62.21/D2, Jul 2007
IEEE Approved Draft Std C57.12.35/D7, 07
IEEE Approved Draft Std P1076.1/D3.3, Feb 6, 2007
IEEE Approved Draft Std P11073-10415/D11, Aug 2008

Do we need to keep "Approved Draft", "Active Unapproved Draft", "Unapproved Draft" in resulting PubID?

@ronaldtse there are many identifiers with word "Unapproved" but without "Draft" after it. Should we add "Draft" to the output?
SShouddf
e.g.hou
IEEE Unapproved Std P277/D2,Mar 2007
IEEE Unapproved Std P487/D7 Feb 2007
IEEE Unapproved Std P495/D12 Mar 2007
IEEE Unapproved Std P802.16g/D8, Feb2007
IEEE Unapproved Std P802.1ag/D8, Feb 2007

I did a search for "IEEE Unapproved Std P277/D2,Mar 2007" and got this:
https://ieeexplore.ieee.org/document/4152680

The full title is apparently: "P277/D2,Mar 2007 - Unapproved Draft IEEE Recommended Practice for Cement Plant Power Distribution"
In fact, the original raw XML data for this entry is this:
<publication>
  <title><![CDATA[IEEE Unapproved Std P277/D2,Mar 2007]]></title>
  <normtitle><![CDATA[IEEE Unapproved Std P277/D2,Mar 2007]]></normtitle>
  <standardsfamilytitle>IEEE Recommended Practice for Cement Plant Power Distribution</standardsfamilytitle>
  <publicationinfo>
    <idamsid>0b000064807b4661</idamsid>
    <stdnumber>P277/D2,Mar 2007</stdnumber>
    <publicationtype>Standard</publicationtype>
    <publicationsubtype>Standard Docs</publicationsubtype>
    <standard_subtype>IEEE Standard</standard_subtype>
    <ieeeabbrev>IEEESTD</ieeeabbrev>
    <pubstatus>Active</pubstatus>
    <publicationopenaccess>F</publicationopenaccess>
    <standard_id>0</standard_id>
    <standard_status>Inactive</standard_status>
    <standardmodifierset>
      <standard_modifier>Draft</standard_modifier>
    </standardmodifierset>
    <packagememberset>
      <packagemember>STDSELECT</packagemember>
    </packagememberset>
    <standard_family>277</standard_family>
    <standardpackageset>
      <standard_package>3000 Standards Collection for Industrial and Commercial Power Systems</standard_package>
    </standardpackageset>
    <icscodes>
      <code_term codenum="91.100.10">Cement. Gypsum. Lime. Mortar</code_term>
    </icscodes>
    <pubtopicalbrowseset>
      <pubtopicalbrowse>Power, Energy and Industry Applications</pubtopicalbrowse>
    </pubtopicalbrowseset>
    <copyrightgroup>
      <copyright>
        <year>2007</year>
        <holder>IEEE</holder>
      </copyright>
    </copyrightgroup>
    <publisher>
      <publishername>IEEE</publishername>
      <address>
        <country>USA</country>
      </address>
    </publisher>
    <holdstatus>Hold</holdstatus>
    <confgroup>
      <doi_permission>F</doi_permission>
    </confgroup>
    <amsid>4152678</amsid>
  </publicationinfo>

      <title><![CDATA[Unapproved Draft IEEE Recommended Practice for Cement Plant Power Distribution]]></title>
      <articleinfo>
        <articleseqnum>1</articleseqnum>
        <idamsid>0b000064807b4665</idamsid>
        <articlestatus>Active</articlestatus>
        <articleopenaccess>F</articleopenaccess>
        <articleshowflag>F</articleshowflag>
        <articleplagiarizedflag>F</articleplagiarizedflag>
        <articlenodoiflag>F</articlenodoiflag>
        <articlecoverimageflag>F</articlecoverimageflag>
        <articlereferenceflag>F</articlereferenceflag>
        <articlepeerreviewflag>F</articlepeerreviewflag>
        <holdstatus>Publish</holdstatus>
        <articlecopyright holderisieee="Yes" year="0"/>
        <date datetype="OriginalPub">
          <year>2007</year>
        </date>
        <size>330403</size>
        <filename docpartition="5" filetype="MainPDF">04152680.pdf</filename>
        <artpagenums endpage="" startpage=""/>
        <amsid>4152680</amsid>
      </articleinfo>

  </volume>

If you look at the <stdnumber>, the "Unapproved..."  text is not present.
But look at the discrepancy between the title values of <publication> vs the <articleinfo>:
<publication>
  <normtitle><![CDATA[IEEE Unapproved Std P277/D2,Mar 2007]]></normtitle>
</publication>

  <volume>

    <title><![CDATA[Unapproved Draft IEEE Recommended Practice for Cement Plant Power Distribution]]></title>

  </volume>

Interestingly, the publication says "Unapproved Std" but the article says "Unapproved Draft".
The "Unapproved" part is not documented in the XML at all.
I found the following two files that are:

04152686.xml "IEEE Unapproved Std P1076.1/D3.3, Feb2007"
04278973.xml "IEEE Approved Draft Std P1076.1/D3.3, Feb 6, 2007"

Archive.zip
Notice this diff:
<   <title><![CDATA[IEEE Unapproved Std P1076.1/D3.3, Feb2007]]></title>
<   <normtitle><![CDATA[IEEE Unapproved Std P1076.1/D3.3, Feb2007]]></normtitle>
---
>   <title><![CDATA[IEEE Approved Draft Std P1076.1/D3.3, Feb 6, 2007]]></title>
>   <normtitle><![CDATA[IEEE Approved Draft Std P1076.1/D3.3, Feb 6, 2007]]></normtitle>
8,9c8,9
<     <idamsid>0b000064807b466f</idamsid>
<     <stdnumber>P1076.1/D3.3, Feb2007</stdnumber>
---
>     <idamsid>0b000064808ffb04</idamsid>
>     <stdnumber>P1076.1/D3.3, Feb 6, 2007</stdnumber>
24c24
<     <isbn isbntype="New-2005" mediatype="Electronic">978-1-5044-2834-7</isbn>
---
>     <isbn isbntype="New-2005" mediatype="Electronic">978-1-5044-2833-0</isbn>
52c52
<     <amsid>4152684</amsid>
---
>     <amsid>4278971</amsid>
57c57
<       <idamsid>0b000064820da92c</idamsid>
---
>       <idamsid>0b000064820daaee</idamsid>
59c59
<         <amsid>4152685</amsid>
---
>         <amsid>4278972</amsid>
64c64
<       <title><![CDATA[Unapproved IEEE Draft Standard VHDL Analog and Mixed-Signal Extensions (Revision of IEEE Std 1076.1-1999)]]></title>
---
>       <title><![CDATA[Approved IEEE Draft Standard VHDL Analog and Mixed-Signal Extensions (Revision of IEEE Std 1076.1-1999)]]></title>
67c67
<         <idamsid>0b000064807b4673</idamsid>
---
>         <idamsid>0b000064808ffb08</idamsid>
81,82c81,82
<         <size>6226635</size>
<         <filename docpartition="5" filetype="MainPDF">04152686.pdf</filename>
---
>         <size>6215274</size>
>         <filename docpartition="5" filetype="MainPDF">04278973.pdf</filename>
84c84
<         <amsid>4152686</amsid>
---
>         <amsid>4278973</amsid>

There is no difference in any of the statuses.
This tells me that the status of "Approved vs Unapproved" is not encoded in the XML data, and is only available in the PubID. Maybe we should store the parsed status of "Approved" and "Unapproved" and only display it out in the "full PubID style".

This tells me that the status of "Approved vs Unapproved" is not encoded in the XML data, and is only available in the PubID. Maybe we should store the parsed status of "Approved" and "Unapproved" and only display it out in the "full PubID style".

What about word "Draft"? Should we display it only for "full PubID style" as well? And for every draft document? (documents with /D suffix)

@mico I think you are right:

Should we display it only for "full PubID style" as well?
I think so.

And for every draft document? (documents with /D suffix)
Yes. For PubIDs that do not have these statements:

"Unapproved Draft"
"Unapproved Draft Std"
"Active Unapproved Draft Std"
"Approved Draft"
"Approved Draft Std"

We only know if it is a "Draft", but we do not know "Approved vs Unapproved" and whether it is "Active".

Found a new pattern to parse: "/D{\d+}+{\d+}"
IEEE 1647/D8+3, December 2010
IEEE P1031/D1+1, August 2010
IEEE P463/D1+1, May 2013
IEEE P751/D2+1, May 2018
P1857/D1+1, July 2012
P2745.1/D4+1, April 2019

@mico I checked online but know what these mean...
There is one instance of CEI/IEC 61000-4-15:1997+A1:2003, which means it is CEI/IEC 61000-4-15:1997 with Amendment 1 (A1:2003), the + here means "combined with Amendment 1". This instance is IEC practice.

@ronaldtse another identifier I don't know how to parse: "PC37.30.2/D043 Rev 18, May 2015"
Is it a revision of Draft? Any ideas how I should represent it?

@ronaldtse "IEEE P1680.4_D1 and NSF/ANSI 426, August 2016" should I represent it as "IEEE P1680.4-2016/D1 (NSF/ANSI 426)"? Better ideas?

Probably "IEEE P1680.4/D1, August 2016 (NSF/ANSI 426)"?
NSF is the "National Sanitary Foundation" which issues food safety and hygiene standard. They use PubIDs like "NSF/ANSI/CAN 61", "NSF/ANSI 61-2021", "NSF/ANSI 336-2011".
I think PC37.30.2/D043 Rev 18, May 2015 is a revision of a draft, yes. Maybe PC37.30.2/D43R18, May 2015. This is similar to the other patterns like:
IEEE P11073-10101/D3r7, September 2018
IEEE P11073-10101/D4r1, January 2019
IEEE P11073-10101/D5r4, February 2019
IEEE P11073-10101/D7r1, March 2019
IEEE P11073-10101/D9r1, April 2019

@ronaldtse IEEE Unapproved Std PC37.101/D13, Jun 2006 - as we can see it's a draft, so does it have missing "Draft" in the identifier? Should we add this to output so result will be ``IEEE Unapproved Draft Std PC37.101/D13, Jun 2006`?

@mico we just received clarification from IEEE:

If it's an "unapproved draft" it is not a standard yet, so none of them should have "Std" included. I'm sure many do though -- the working groups work on revisions based on the published version and are not necessarily aware of these subtleties.

i.e. "Unapproved Std" or "Unapproved Draft Std" should not have "Std".

@mico I checked online but know what these mean...
There is one instance of CEI/IEC 61000-4-15:1997+A1:2003, which means it is CEI/IEC 61000-4-15:1997 with Amendment 1 (A1:2003), the + here means "combined with Amendment 1". This instance is IEC practice.

@ronaldtse are you saying here that IEEE 1647/D8+3 is a Draft 8 + Amendment 3?

@ronaldtse what is the number after ISO stage like:

ISO/IEC/IEEE P15026-4/DIS2, February 2021
ISO/IEC/IEEE P24748-5-CD3, February 2015
?

@ronaldtse I'm struggling with identifier "ISO/IEC/IEEE P26513_D2, January 2017".
This seems to be ISO identifier, but IEEE format and have IEEE's draft part.
There is no way to reformat it to "ISO" format without losing "draft" part.
So seems the output should be "ISO/IEC/IEEE Draft Std P26513/D2, January 2017". Am I right?


Refactor DI support in DataProtection

@ajaybhargavb How close is this for check-in?
@Eilon Are we taking this in RC2?  Or postpone to 1.0.0?

I'll be sending an update to the PR today. But it will not include and test and documentation changes.

I'd like to get this for RC2 because there are public API changes in it, and I spoke to @ajaybhargavb about it and we had a short email thread too.

Looks like the PR is a little stale at the moment. Do we have any blockers on this?

Spoke to @Eilon and @rynowak this morning. This is being moved to RTM.

The latest code and samples are in https://github.com/aspnet/DataProtection/tree/ajbaaska/new-dataprotection branch.

@ajaybhargavb You're working on the DI bits, right? I ask because I was having a small problem with DI into the XmlDecryptor. https://github.com/aspnet/DataProtection/issues/154
The problem was that DI for XmlDecryptor wasn't working. I wanted to do this ...
public CustomXmlDecryptor(IOptions<CustomDataProtectionOptions> dataProtectionOptions)
{
    _key = dataProtectionOptions.Value.Key;
}

... but that wasn't working. I simply wasn't getting the value. It works using the ctor injection pattern for XmlEncryptor, just not for XmlDecryptor.
With a little help from @tillig, I was able to make it work on the decryptor side with a little hack, I ended up having to do this ...
public CustomXmlDecryptor(IServiceProvider services)
{
    var dataProtectionOptions =
        services.GetRequiredService<IOptions<CustomDataProtectionOptions>>();
    _key = dataProtectionOptions.Value.Key;
}

Is fixing this something that falls under this issue, or was this problem already addressed do you know?

@GuardRex - please make a separate issue for this. Having looked at the code, this isn't something that's been supported so far so it's a feature request

@rynowak Ok, thanks. Will do.

I reopened and re-titled that issue ... it basically describes the difference in success using DI with the ctors of IXmlDecryptor and IXmlEncryptor. Given the workaround there, I'm not blocked of course, so it really is just a nice-to-have if you like the idea.
https://github.com/aspnet/DataProtection/issues/154


Update PowerToys to latest version

https://github.com/lukesampson/scoop-extras/blob/740610842d2f76ff03b99aa4123ef88bf37a6f98/bucket/powertoys.json#L8
Currently the powertoys json file has the version as v0.21.1 while the latest version is actually v0.35

There's updated version in non-portable bucket FYI.

https://github.com/lukesampson/scoop-extras/blob/740610842d2f76ff03b99aa4123ef88bf37a6f98/bucket/powertoys.json#L8
Currently the powertoys json file has the version as v0.21.1 while the latest version is actually v0.35

It's because they stopped providing a MSI after v0.21.1.
Release v0.23.0 states:
The EXE installer should be at parity now with the MSI. Please go to the wiki for installer args

the wiki link in question : https://github.com/microsoft/PowerToys/wiki/Installer-arguments-for-exe
I tested a modified recipe locally but it ended up being pretty similar to powertoys-np.
You can apparently still extract the MSI with --extract_msi but I'm not sure it makes a difference with what powertoys-np does.
At this point, I feel powertoys and powertoys-np are gonna be a bit redundant.
What do you guys think ?


mediainfo: split packages replaced by one unique package

Description of package
Following the discussion here https://github.com/kiss-community/community/pull/729, I have tried to replace the packages libzen, libmediainfo and mediainfo with one unique package.  This is a first version to discuss. In this version, there is one single binary, statically linked. It contains everything (8 MB).
So libzen and libmediainfo are not needed anymore.  Those libraries are basically only for mediainfo,
take a look here under "Required by":
https://archlinux.org/packages/community/x86_64/libzen/
https://archlinux.org/packages/community/x86_64/libmediainfo/
The problem is it doesn't follow the usual path with configure, then make. A script CLI_Compile.sh
executes everything. configure is called inside the script so I have to patch it to modify some configure
parameters.
If we want a more traditionnal way, and a better control of the configure parameters, I could extract the necessary commands from CLI_Compile.sh and try to build mediainfo. This suits probably better to kiss.
Before I try It, I would like to know what do you prefer.
And there is a second problem: how to inform the user that the packages libmediainfo and libzen
should be removed ?
Installed manifest of package
(kiss manifest <pkg>)
/var/db/kiss/installed/mediainfo/version
/var/db/kiss/installed/mediainfo/sources
/var/db/kiss/installed/mediainfo/patches/fix_musl.patch
/var/db/kiss/installed/mediainfo/patches/fix_configure.patch
/var/db/kiss/installed/mediainfo/patches/
/var/db/kiss/installed/mediainfo/manifest
/var/db/kiss/installed/mediainfo/depends
/var/db/kiss/installed/mediainfo/checksums
/var/db/kiss/installed/mediainfo/build
/var/db/kiss/installed/mediainfo/
/var/db/kiss/installed/
/var/db/kiss/
/var/db/
/var/
/usr/bin/mediainfo
/usr/bin/
/usr/

Existing package

[x] I am the maintainer of this package.

So libzen and libmediainfo are not needed anymore. Those libraries are basically only for mediainfo,

Good to know; we bundle some things already anyways (libnl, libinih, etc).

The problem is it doesn't follow the usual path with configure, then make. A script CLI_Compile.sh
executes everything. configure is called inside the script so I have to patch it to modify some configure
parameters.

This seems fine

Before I try It, I would like to know what do you prefer.

If the script CLI_Compile.sh is intended for what you're proposing we do, then I'm fine with using it in this way :)
Bundling dependencies isn't usually the best call, but in cases (especially like this one), it's the overall better choice (what Dylan does with wpa_supplicant is also a good example; what we (used to do) with xfsprogs is perhaps a bad example). So I'm more than happy to accept this change.

And there is a second problem: how to inform the user that the packages libmediainfo and libzen
should be removed ?

This would simply be a matter of modifying their depends files to require this package and/or having the build scripts simply build this package; and adding post-install script making users aware of this change (see https://github.com/kisslinux/repo/blob/b60d6455092361f94b2e7590c193d08c19c23499/extra/wpa_supplicant/post-install).
Another option is symlinking those packages to this one but I like that idea less. I think it's better to simply cleave those now uneccessary packages as cleanly as possible. My recommendation is to bump their relver, add this package as a dependency to the ones it's replacing, and create a post-install file to notify users of the change. The replaced packages can then be dropped "after enough time has passed", which would be when this package sees a new update (or like, a month, depending on how often new releases are made).

I don't exactly understand the changes to the depends file. Let's take the example of libzen. I would add the
dependency mediainfo in the depends file. Why ?
If it's ok, I would proceed like this:

bump the relver in the version file
delete the depends file
change the buildfile like follows

#!/bin/sh -e

So the build file does nothing.

add a post-install like you suggest.

Is it ok for you ?


Latest version causes Multi::wait to block and ignore socket events

Since commit 7f0f5dad2458313e2800cf915c55f180184f6617, using Multi::wait() together with Multi::get_timeout() produces very strange results when combined with one or more extra WaitFds passed to wait().
I'm seeing two strange behaviors:
First scenario: When get_timeout() returns Ok(None), my understanding is that curl doesn't have enough info to specify an appropriate timeout value and I should pick a reasonable default. I pick 1s in this case.
When this happens, for some reason, calling wait() with the default timeout causes curl to block forever until the given timeout is reached, even if there is socket activity on one or more easy handles, or on an extra fd.
Below is an example program that reproduces the problem:
extern crate curl;

struct Handler;

impl curl::easy::Handler for Handler {}

fn main() -> Result<(), Box<std::error::Error>> {
    let mut easy = curl::easy::Easy2::new(Handler);
    easy.verbose(true)?;
    easy.get(true)?;
    easy.url("http://example.org")?;

    let multi = curl::multi::Multi::new();
    let _easy = multi.add2(easy)?;

    let mut extra_fds = [curl::multi::WaitFd::new()];
    extra_fds[0].set_fd(0);
    extra_fds[0].poll_on_read(true);

    while multi.perform()? > 0 {
        let timeout = multi.get_timeout()?.unwrap_or(std::time::Duration::from_secs(100));
        println!("timeout: {:?}", timeout);
        multi.wait(&mut extra_fds, timeout)?;
    }

    Ok(())
}

Second scenario: In this scenario, curl does return a recommended timeout, but is a very large number, such as 300 seconds. Normally this would be fine, but similar to the first scenario, curl blocks for the full timeout duration, even when there is socket activity that should interrupt it.
I'm still working on extracting an example from my code that reproduces this.
I'm not sure if upgrading the version of curl being used caused this problem and it is an upstream bug, or changing how curl is compiled introduced this issue. I've done some digging myself, but hopefully someone else with more knowledge might have a better idea of the cause.
My unproven theory is that somehow the latest change causes curl to use a really poor implementation for curl_multi_wait().
Tested on Linux.

Oh dear this sounds bad, thanks for the report! I tried digging in a bit last night but couldn't turn up much unfortunately. I'll play around today with switching submodules and see if this is a bug in the update or the build system changes.

Interesting to note: it seems like this behavior only happens if DNA resolution is required. When connecting to an IP address, it seems like the problem goes away. I haven't confirmed this, but I wonder if the flags changed which DNS resolved is being used.

Ok I believe I've now confirmed that the behavior of the program above changed in https://github.com/alexcrichton/curl-rust/commit/85d59946bcc53f68d7cfcd32f80fd7da50ee0b01, so I think it's due to that curl submodule update?

I did some further investigation tonight, this time armed with LLDB (stepping between Rust and C is magical!). Still no answers, but I think I have a grasp as to what behavior precisely has changed.
When calling perform(), while the easy handle is in a WAITRESOLVE state, the handle expiration timer is being set to the value of CURLOPT_CONNECTTIMEOUT_MS, which is in turn returned by get_timeout(). After a couple of iterations of perform and wait, the hostname gets resolved and the state transitions to WAITCONNECT. Once this happens, get_timeout() begins to return more reasonable timeouts and things begin to work properly.
Previously it would seem that get_timeout() would return either 0 or a small value like 1ms while the easy handle is in the WAITRESOLVE state.
I don't have any more time available to researching this bug, so I've employed a workaround for the time being. Here it is: when get_timeout() returns a duration that matches exactly the value of CURLOPT_CONNECTTIMEOUT_MS, treat it as likely to be this bug and truncate the timeout to a very small value.
I am now confident this is an upstream curl bug; the fact that revving the curl submodule causes this is good evidence. I will open an issue there and link it back here.

@alexcrichton Looks like the libcurl fix is on master now; updating the curl submodule should resolve the issue here.

Ok great! I actually updated to the master branch yesterday for other reasons, want to check out the most recently published version and see if it works?

Yep, already did. I cloned this repo, updated the submodule locally, and ran my problematic example against that, and it worked.

Oh sorry I mean the version of curl-sys published on crates.io which I believe should have all the support necessary now.

Ah I misunderstood; I will try that and verify it.

Nope, looks like the most recent curl-sys doesn't include commit https://github.com/curl/curl/commit/ec5d0991ccf1e04fc384b312fc1b24c21259c0f1.

Oops wow that is quite recent, should be fixed and published now!


Entity envelope in rest api

Changed REST API endpoint so that they don't return simply the stored event. Instead we wrap the sse events in an envelope which looks like:
{     "headear": {         "api_version": "2.0.0",         "network_name": "casper"     },     "payload": {(...)} }
Events in endpoints that return lists (like signatures for block) will also have each individual element of the list wrapped in such envelope.
In the above the header fields:

"api_version" is the api version which was reported in the ApiVersion message for the node that we fetched the event from.
"network_name" is the "chainspec_name" field that was returned in the "/status" endpoint for the node that we fetched the event from.

LGTM


Unit tests for subeditor.go

Add unit tests for all functions in the file.


Added iterutils w/ findAll for pred and val

Added iterutils module, with 2 functions (findAll with value, findAll with predicate function).

There appears to be some sort of bug, I am not sure why this is failing checks. I am not familiar with CI, but my code should work crossplatform


Factor out rxros_tf from rxros

See issue #3 . It should be possible to get the core part of rxros be completely independent from tf.

Some initial work: https://github.com/rosin-project/rxros/compare/master...gavanderhoorn:refactor_tf_support.

@henrik7264: I've noticed that observable is currently a class (here), but all methods are static (here fi).
Would it be possible to make an observable namespace instead of a class? That would make adding to the rxros namespace easier (from rxros_tf fi).
For now I've created an additional rxros_tf namespace to allow the second observable class to co-exist with the one in rxros.
(note: I've not actually used this yet, so it could be that this is a silly/stupid question/suggestion)

And just an observation: besides this:
https://github.com/rosin-project/rxros/blob/5bb5fb3fab9ab06e846728a44196c57434312b2a/rxros/include/rxros/rxros.h#L229
rxros_tf appears to be independent from rxros itself (the TF related code only uses rxcpp, roscpp and tf).

Hi Gijs
I shall look at it later this evening.
Regards Henrik
On 1 Sep 2019, at 13.11, G.A. vd. Hoorn <notifications<EMAIL_ADDRESS>wrote:
And just an observation: besides this:
https://github.com/rosin-project/rxros/blob/5bb5fb3fab9ab06e846728a44196c57434312b2a/rxros/include/rxros/rxros.h#L229https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Frosin-project%2Frxros%2Fblob%2F5bb5fb3fab9ab06e846728a44196c57434312b2a%2Frxros%2Finclude%2Frxros%2Frxros.h%23L229&data=02|01||f6ce462829d54d35da0408d72ecd1584|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637029330667637735&sdata=Km6CIU9pbKhKkGcSGoKunlDoLc0PDLCzcGH%2F3NWOMSc%3D&reserved=0
rxros_tf appears to be independent from rxros itself (the TF related code only uses rxcpp, roscpp and tf).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Frosin-project%2Frxros%2Fissues%2F8%3Femail_source%3Dnotifications%26email_token%3DAJYMVX5IT6GOEW3AZ2EXZALQHOPMTA5CNFSM4IQGQ4N2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5T77MI%23issuecomment-526909361&data=02|01||f6ce462829d54d35da0408d72ecd1584|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637029330667647745&sdata=qYpAZRGX0rPHF%2FyHSFRC1%2F1wOtYHp90M2g6kEFqWqj0%3D&reserved=0, or mute the threadhttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJYMVX7LC3ZYX4WMHGQBX3LQHOPMTANCNFSM4IQGQ4NQ&data=02|01||f6ce462829d54d35da0408d72ecd1584|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637029330667647745&sdata=HUFbcTw8%2FMforKnuQ%2Btv6rEY2a6TTInbJB3MvdmC4pA%3D&reserved=0.

I actually think there is a good chance that the class may be replaced by a namespace. Thinking about it I actually better like this approach.
I shall check it later to night. I am on work now.
On 1 Sep 2019, at 13.11, G.A. vd. Hoorn <notifications<EMAIL_ADDRESS>wrote:
And just an observation: besides this:
https://github.com/rosin-project/rxros/blob/5bb5fb3fab9ab06e846728a44196c57434312b2a/rxros/include/rxros/rxros.h#L229https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Frosin-project%2Frxros%2Fblob%2F5bb5fb3fab9ab06e846728a44196c57434312b2a%2Frxros%2Finclude%2Frxros%2Frxros.h%23L229&data=02|01||f6ce462829d54d35da0408d72ecd1584|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637029330667637735&sdata=Km6CIU9pbKhKkGcSGoKunlDoLc0PDLCzcGH%2F3NWOMSc%3D&reserved=0
rxros_tf appears to be independent from rxros itself (the TF related code only uses rxcpp, roscpp and tf).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Frosin-project%2Frxros%2Fissues%2F8%3Femail_source%3Dnotifications%26email_token%3DAJYMVX5IT6GOEW3AZ2EXZALQHOPMTA5CNFSM4IQGQ4N2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5T77MI%23issuecomment-526909361&data=02|01||f6ce462829d54d35da0408d72ecd1584|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637029330667647745&sdata=qYpAZRGX0rPHF%2FyHSFRC1%2F1wOtYHp90M2g6kEFqWqj0%3D&reserved=0, or mute the threadhttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJYMVX7LC3ZYX4WMHGQBX3LQHOPMTANCNFSM4IQGQ4NQ&data=02|01||f6ce462829d54d35da0408d72ecd1584|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637029330667647745&sdata=HUFbcTw8%2FMforKnuQ%2Btv6rEY2a6TTInbJB3MvdmC4pA%3D&reserved=0.

Here is a proposal for how the rxros.h and rxros_tf.h could be made.
rxros.zip

@henrik7264: looking at the contents of the zip file it appears the biggest changes are the introduction of the rxros_tf.h header and the fact that observable is now a namespace. Correct?
That all looks OK to me.
Would you want to submit that as a pull request against this repository?

@gavanderhoorn yes the zip file is a proposed split of the rxros.h into a rxros_tf.h and a rxros.h without tf. The second change is to use a namespace instead of the observable class.
Yes it would be nice to have this as a pull request against this repository.

@gavanderhoorn could I kindly ask you to make the necessary preparation with respect distributing the files to the appropriate repositories and setup up all the nice ROS workspace magic. I shall be happy to review and merge them later.

@henrik7264: see #24, which is a continuation of the work I mentioned in https://github.com/rosin-project/rxros/issues/8#issuecomment-526909032 combined with the changes you proposed in your .zip in https://github.com/rosin-project/rxros/issues/8#issuecomment-526928704.
If you could review that would be great.


Draw arrow from coming from and going to the same element

Is there any easy way to do this? Been playing around and by disabling the check I can get it to render an SVG but the it has no size, obviously due to the x/y coords being the same as it's the same element. Any painless ways to change the style to have an arch that returns to the element it came from?

Hi @James-Curran, thank you for the comment.
Sorry, my English is very poor, and I could not understand your question well.
Do you mean that you want to draw a line from an edge of an element to another edge of the element?

No problem, thank you for the quick reply!
Yes basically that is what I would like to do i.e. element1 -> element2, element2 -> element2, element2 -> element3

Is that this?
https://jsfiddle.net/6gafmuve/

Wow...brilliant! Thank you so much, will close now.

:smile:


Add support for Cube Map Rotation

Fixes #2505
Public API additions:
 * @class
 * @name pc.Scene
 *
 * @property {pc.Quat} skyboxRotation The rotation of the skybox to be displayed. Defaults to pc.Quat.IDENTITY

 * @class
 * @name pc.Texture
 *
 * @param {boolean} [options.isRenderTarget] - Specifies whether texture or cubemap was used as a render target. Defaults to false.

Example:
    var rot = new pc.Quat();
    rot.setFromEulerAngles(42, 42, 0);
    app.scene.skyboxRotation = rot;

I confirm I have signed the Contributor License Agreement.

Alternatively you could apply the -1x to the matrix when it's being set on the shader.

As a user, I think it's confusing that setting an identity rotation matrix results in a mirror transform. I'd much rather keep the -1x always and optionally multiply in the rotation matrix.
Also, is it possible to have this rotation logic (the -1x and optional rotation matrix) encapsulated into single chunk/function? This way we can modify/customise easily in future.
Alternatively you could apply the -1x to the matrix when it's being set on the shader.

I will move the rotation logic into a function and put it in a new chunk.
For the -1x flip, maybe the best way for users is to expose an extra boolean flag which defaults to true to determine is the -1x should be applied to the rotation - and maybe switch back to Quat from Mat3 for the rotation property?

For the -1x flip, maybe the best way for users is to expose an extra boolean flag which defaults to true to determine is the -1x should be applied to the rotation - and maybe switch back to Quat from Mat3 for the rotation property?

yep I agree with this. Ideally we don't convert quat->matrix each frame, so it would need to store additional Mat3 as well?

Will this fully address #189?

Just curious why the docs for each property have been made single line? We normally try to make an effort for JSDoc blocks to stick to a reasonable number of columns (the coding standards never specified this maximum though). But it's good to be able to read them without having to scroll horizontally.

I restored it to multi-line

Will this fully address #189?

It won't address #189 - this was touched on in the graphics sync - to allow a cube map to be reused at multiple different rotations, we would have to store the rotations of each instance - which we think should be in something like instances of light-probe components that reference cube maps.

OK, understood.

PR name is misleading - this is not cubemap rotation, but skybox rotation.
Is it possible to rotate cubemap that is applied on material directly?
Box projection cubemaps been limited by not able to rotate them, leading to limited use cases. One of them is moving objects, e.g. train with box projected cubemap inside.

PR name is misleading - this is not cubemap rotation, but skybox rotation.
Is it possible to rotate cubemap that is applied on material directly?
Box projection cubemaps been limited by not able to rotate them, leading to limited use cases. One of them is moving objects, e.g. train with box projected cubemap inside.

@Maksims - You are right, this PR now only exposes skybox rotation, even though the shader code does support any cubemap to be rotated. A subsequent PR will also expose non-skybox cube map rotation - and we are discussing the best place to store the rotation. I'll adjust the name of this PR.


cmp-cmdline automatically triggers commands without hitting

FAQ

[X] I have checked the FAQ and it didn't resolve my problem.

Announcement

[X] I have checked Breaking change announcement.

Minimal reproducible full config
Minimal init.lua:
vim.cmd('packadd packer.nvim')
require('packer').startup({
  function(use)
    use({ 'wbthomason/packer.nvim' })
    use({
      'voldikss/vim-floaterm',
      cmd = { 'FloatermNew', 'FloatermToggle' },
    })
    use({
      'hrsh7th/nvim-cmp',
      config = function()
        local cmp = require('cmp')
        cmp.setup()
        cmp.setup.cmdline(':', {
          enabled = true,
          sources = {
            { name = 'cmdline' },
          }
        })
      end,
    })
    use({
      'hrsh7th/cmp-cmdline',
      requires = 'nvim-cmp',
    })
  end,
})

Description
Floaterm is automatically triggered with cmp-cmdline enabled when user is typing in the command-line.
Disabling cmp-cmdline solves this issue.
Steps to reproduce

Replace init.lua with the minimal config provided.
Run PackerSync
Enter nvim
Type in command-line: FloatermNew
Hit Space
Floaterm automatically opens

Expected behavior
Floaterm should not be opened before the user hits .
Actual behavior
Floaterm is automatically opened before the user hits .
Additional context
A demo of this bug:
https://user-images.githubusercontent.com/76579810/207524716-1bb6c329-c548-4c18-b63a-b05b722401af.mp4
Disabling cmp-cmdline solves this issue.
Demo:
https://user-images.githubusercontent.com/76579810/207527517-f283f499-2def-40b7-a10a-72185acc46f4.mp4
It is also worth mentioning the bug might also be related to recent packer.nvim updates that changes the implementation of lazy-loading commands in its compiled file, so I also reported the bug there.

Also see the issue under packer.nvim:

Please create straight forward reproduction step. I can't understand how to reproduce the problem.

Please create straight forward reproduction step. I can't understand how to reproduce the problem.

Hi, thanks for your reply. It is pretty clear how to reproduce this issue. Just use the provided minimal init.lua as the config file for nvim, run PackerSync first and then run FloatermNew, after that, hit space to reproduce the bug.

The provided init.lua causes the error. the reproduction step does not contains the installation step of packer.nvim.

Please create the minimal init.vim that based on https://github.com/hrsh7th/nvim-cmp/blob/main/utils/vimrc.vim


I am getting error:

This file seems to be missing:
\composer/autoload_static.php see here:

It could be a cache issue - try deleting the entire vendor folder and running composer install again

It could be a cache issue - try deleting the entire vendor folder and running composer install again

Sir, the autoload_static.php file that it claims to be missing is not even there in your github repository. Please see:

Or I am a beginner and a fool who doesn't know something or missing some foundation knowledge?

Sir, the autoload_static.php file that it claims to be missing is not even there in your github repository. Please see:

Or I am a beginner and a fool who doesn't know something or missing some foundation knowledge?

autoload_static is generated by composer.
Did you run composer update ?

autoload_static is generated by composer.
Did you run composer update ?

It worked.

It worked.

One Humble request:
You are an awesome author, but if possible can you increase the code size or focus of the screen capture software in your future courses. Currently, it exerts pressure on the eye:

One Humble request:
You are an awesome author, but if possible can you increase the code size or focus of the screen capture software in your future courses. Currently, it exerts pressure on the eye:

Hi There, on XAMPP virtual server is configured like this →

My Pseudo/Vhost mvclogin.com is pointing correctly to the public folder:
<VirtualHost *:80>
DocumentRoot "G:/codegorithm/PHP/daveh/mvclogin/public/"
ServerName mvclogin.com
<Directory "G:/codegorithm/PHP/daveh/mvclogin/public/">
Allow from all
Require all granted
Options Indexes
</Directory>
</VirtualHost>

Still URL not Found →

Hi There, on XAMPP virtual server is configured like this →

My Pseudo/Vhost mvclogin.com is pointing correctly to the public folder:
<VirtualHost *:80>
DocumentRoot "G:/codegorithm/PHP/daveh/mvclogin/public/"
ServerName mvclogin.com
<Directory "G:/codegorithm/PHP/daveh/mvclogin/public/">
Allow from all
Require all granted
Options Indexes
</Directory>
</VirtualHost>

Still URL not Found →

@fastmarketo Please can you ask for support for the course inside the Q&A section on the course itself in Udemy? That way other students can benefit from and contribute to the discussion. Thanks!

@fastmarketo Please can you ask for support for the course inside the Q&A section on the course itself in Udemy? That way other students can benefit from and contribute to the discussion. Thanks!

Sure, Thanks.

Sure, Thanks.

Sir, before you close this ticket. I have a request.
You are such a knowledgeable person can you create a course in the future to create an e-commerce store independent of any framework, but only in: PHP, MYSQL, AJAX, and PDO.
Additionally, in case you can create an emphasis on how hooks are created as in WordPress.
Lastly maybe an additional project/course or one element of the same requested course where you can create an e-commerce plugin for wordpress.
I will be the first one among many who will buy the course.

Sir, before you close this ticket. I have a request.
You are such a knowledgeable person can you create a course in the future to create an e-commerce store independent of any framework, but only in: PHP, MYSQL, AJAX, and PDO.
Additionally, in case you can create an emphasis on how hooks are created as in WordPress.
Lastly maybe an additional project/course or one element of the same requested course where you can create an e-commerce plugin for wordpress.
I will be the first one among many who will buy the course.

I'm always on the lookout for new course ideas, so I'll add that to my list! Thanks!

I'm always on the lookout for new course ideas, so I'll add that to my list! Thanks!


Swift 3

I made a swift3 fork & branch. If you make a swift3 branch I can submit a pull request.

For others facing the issue, just a create a new swift file and use it like this:
import Foundation
extension Date {
func timeAgo() -> String {

    return self.timeAgo()

}

}


Add images: Android Basics in Compose

URL of codelab
https://developer.android.com/codelabs/basic-android-kotlin-compose-composables-practice-problems?continue=https%3A%2F%2Fdeveloper.android.com%2Fcourses%2Fpathways%2Fandroid-basics-compose-unit-1-pathway-3%23codelab-https%3A%2F%2Fdeveloper.android.com%2Fcodelabs%2Fbasic-android-kotlin-compose-composables-practice-problems#2
In which task and step of the codelab can this issue be found?
Step 5: Practice: Compose Basics
Then navigate to 'Task Manager' practice screen.
See UI specifications, point 2:
Set the first Text composable to a 24sp font size, 24dp padding top, and 8dp padding bottom.
Describe the problem
The image shown as a sample shows the text "All tasks completed" in bold. Making it bold is not mentioned in the step (point 2) which could teach fontWeight parameter of the Text Composable. Also, in the step description, it is written that the font size should be 24sp but in the sample image, it is not.
Additional information
The correct image should be something like:

Hello @ahujarahul,
Thank you for reaching out to us and sharing your concern. The UI specification is updated:


How to hook a function which's registered in JNI_ONLOAD?

I am wondering if any example to show the way to hook a function being register in JNI_ONLOAD function?
By using frida, In order to locate that function pointer being hooked. I need to do something like this
var JNI_LOAD_POINTER = Module.getExportByName('libnative.so', 'JNI_OnLoad'); //get absolute JNI_ONLOAD address from memory
// Getting base address by subtraction of relative address of JNI_ONLOAD, supposed it is 0x31A04
var BASE_ADDR = parseInt(JNI_LOAD_POINTER) - parseInt('0x31A04');
//The absolute function pointer can be got by adding base address and relative address of hooked function
var hookpointer = '0x' + parseInt(BASE_ADDR + parseInt('0x32168')).toString(16) //
var pointer = new NativePointer(hookpointer) //

I'll try to write an example in a seperate branch and we can discuss about the scenario I applied then...

I guess you could do the same with frida too right?

I guess you could do the same with frida too right?

Yes, Frida can do the same, but the frida server is banned by some Chinese brand mobile phones, the interesting thing is the frida detection logics was implemented in system layer not specific app. So far I have no idea how to bypass the tricks.
Although I can use frida on emulator but the problem is many apps do not support x86 emulator.
So I want to try chickenhook on arm platform..

I didn't know about any device used in europe that has frida detection on system level. Do you wanna tell me which device has this feature?
May they check for names, binary signature or blocked ptrace attach (may you know frida uses ptrace)...
There are plans for chickenhook to be able to be installed into existing binaries (static hooking) and also to apply the ptrace feature (hook other processes)... But this will take some time...

I updated the code a lil bit.. may it helps for your purposes!