backward function of CUDA

Hello, kwea123!  I'm trying to add one CUDA algorithm between the RayMarcher and VolumeRenderer, but my backward function is not working, it seems like it ignores my backward function. Could you give me some suggestions to debug? Could please tell me what steps or operations should be required or paid attention to during the backward function design to get it to work? Thank you very much!

I get it done today, haha! A little step forward to understanding the process of CUDA working~

Sorry for the late reply, I will cover this in my last cuda tutorial video that I will upload today. Basically you need to define a python  class like this
https://github.com/kwea123/ngp_pl/blob/8d04855eb3c2a6924a5f2a9a8eaa3720758fec51/models/custom_functions.py#L162-L173
that implements forward and backward, and call cuda kernel in the backward function which calculates the gradient mathematically

Thanks! Your tutorial videos are awesome, help me a lot~


The connection to the impossible scale so that all and good configurations

Hello, I install PufferPanel on a VPS with 4vCore, 4 GB RAM, 100 GB of storage and a connection to 100Mbps, and set up on the panel and on the scale but its makes me a little red on the right icon when I go on the list of nodes. What do I do?
[----------------------------------------------------------------------------]
I'm french so I use bing.com/translator, excuse me to the possible error

Problem solved, I use cloudflare but I forgot to remove the CDN option


Not an issue, just a question. Does unpackerr extract in place?

Hi David! Very cool program, I really want to start working with it, but I have a simple question before I do so.
So I have my download client create a new folder for every file that starts downloading such as
/Downloads/newmovie/
Does upackerr create the file inside of that folder, or does it leave it in the downloads folder? That may have sounded really confusing, below is what I'm basically talking about.

/Downloads/newmovie.mkv
or
2. /Downloads/newmovie/newmovie.mkv

thanks!

/Downloads/newmovie_unpackerr/newmovie.mkv is where it's extracted to. Once extraction finishes, all extracted files are moved into /Downloads/newmovie/.

In other words, it does exactly what Radarr expects to import the movie and subs.


added Results.tsx to display results as pie chart using mui x-charts

Added Results.tsx to show data in pie chart using Mui x-charts

Added Results.tsx component to display final results as pie chart using mui x-charts


same API can be deployed in multiple namespaces

Description:
Validations should be added to restrict by API context. APIs with same API contexts should not be able to deploy.
Suggested Labels:

Suggested Assignees:

Affected Product Version:
OS, DB, other environment details and versions:
Steps to reproduce:
Related Issues:

Fixed by https://github.com/wso2/apk/pull/561


Pallets pallets pallets

I put the pallets for each folder into a file. This makes it so we can't run them individually. We should probably split these out into their own pallets but I didn't.

Ideally a lot of these pallets should be in their respective project repositories. But I'm good with them being here for now. We can move them later.
LGTM

I thought the reason they were in the list below was that they didn't have repo's. Whoops.


Integer wrapping incorrect for large numbers

Integer wrapping is till incorrect for large numbers. E.g. the result for 2^30 * 2^30 overflows more than the constant that is subtracted in case of overflow.

Do you have a specific example? And are you sure that you are running the latest version? I can't reproduce that:

If you installed through pip, you can get a new version using the pip install --upgrade riscemu flag

Indeed. Thank you.


.babelrc incompatible with Babel 6

the current .babelrc uses the "stage: 2" option which is no longer supported in the latest Babel, which causes it to throw an error if you are using Babel >= 6.0.0.

Ok! Updating config to babel 6. Thanks for reporting!

I will be happy to accept any PR with a HMR configuration using Babel 6!

What's about Babel 6 updating? Thanks!

Yep, as I said in the previous comment, contribution here is very welcome. BTW, I don't know yet about babel 6 support in HMR which is very useful for development...

Waiting on this, https://github.com/gaearon/babel-plugin-react-transform/issues/46

Perfect, so as soon as we get support we can update!
Thanks @nathanmarks !

@javivelasco I think you can use react-hot-loader to achieve HMR with Babel 6, we did this in our projects and it works like a charm :)

Awesome! Gonna work on it during the afternoon. Thanks @Bernardstanislas :)

@javivelasco create a roadmap for upgrade to babel 6

Yeah we should. I was waiting for HMR to be updated and it seems it's coming. I'll have some time to work on toolbox during the weekend and I'll try to release some changes and set up next priorities. This should be one of them

@javivelasco create a roadmap, i create pull request for upgrade

@javivelasco It seems that this issue can be closed without further actions

Yep! thanks @guerrero !


Displaying entities on terrain

@mramato Can you take a look at the implementation for the RectangleGeometry? Once we get the correct way we want to do this, I'll hook it up for the other types.

[x] Corridor
[x] Ellipse
[x] Polygons
[x] Rectangle
[x] Billboards

Added by @mramato

[ ] Camera flyTo of an entity on terrain.
[ ] Camera tracking of an entity on terrain
[ ] Selection indicator of an entity on terrain
[ ] Point and Model clamping
[ ] Detecting if EXT_FRAG_DEPTH is missing and fallback to non-ground visualization; otherwise this branch breaks IE, Safari, and various mobile devices.
[ ] Performance

FYI, there is already an entity-clamp-to-ground branch for billboards and labels, but it needs work to be finished.  I would recommend eventually merging your efforts with that branch.
From a purely functional standpoint, here are the major problems I see that prevent us from having official Entity support for terrain.
General

There are problems with both the camera tracking and selection indicator because it is positioned where it thinks the entity is, not where it is actually drawn. Essentially, we need expose a way to easily query where an object is beind rendered, which shouldn't be too hard but will probably require some primitive tweaks and exposing some new functions.  This will get tricky pretty quick because of the way camera/selection tracking currently work.  It's a totally solvable problem though.

Geometry

The GroundPrimitive can't currently be batched, so performance is terrible when there are a bunch of them on the screen. Just 900 rectangles drops my fps to 20 (code below).
Geometry outlines can't be clamped to ground which will confuse users who will end up reporting it as a bug.
Geometry materials other than color doesn't work, which will also confuse users who will end up reporting it as a bug (but may not be as big of a deal as outlines).
Obviously lines aren't supported yet. I don't think using corridors as lines will work well at all, but I'm willing to entertain the idea and see where it ends up. (and they don't support materials/outline either)
I also noticed that if we go with the "no height/no extrusion means on terrain" approach, it can potentially break existing apps (who would need to set height to 0 explicitly as a workaround).  One solution would be to not put the geometry on terrain if it has a non-color material instead of just drawing it white (which is what you're doing now).

Billboards, Labels, Points, and Models

Neither PointPrimitive or Model support clamping to ground yet, but these are both often requested features that we should address.
No lines on terrain means that having a moving object clamped to ground will cause the line to not be clamped to ground, producing weird visual inconsistency which will confuse users who will definitely end up reporting it as a bug.

If we try and introduce terrain support to the Entity API without addressing the above issues, I think support will be very inconsistent and frustrate/confuse a lot of our users.  I'm probably willing to take incremental steps, but we need a solid plan going forward to that things don't languish.
Here's the test code I used to look into rectangle performance I mentioned above:
var viewer = new Cesium.Viewer('cesiumContainer');
viewer.scene.debugShowFramesPerSecond = true;

Cesium.Math.setRandomNumberSeed(0);
var granularity = 3;
var i = 0;
for (var lon = -45.0; lon < 45.0; lon += granularity) {
    for (var lat = -45.0; lat < 45.0; lat += granularity) {
        i++;

        viewer.entities.add({
            rectangle : {
                coordinates : Cesium.Rectangle.fromDegrees(lon, lat, lon + granularity, lat + granularity),
                material : Cesium.Color.fromRandom({
                    alpha : 0.75
                })
            }
        });
    }
}
console.log(i);

In general, this approach doesn't look too bad, and may be okay for a short-term fix (as far as exposing current primitive capabilities).  Longer term we really need to invest time in reworking visualization to better handle the new features and additional use cases that have come about in the past year.
We probably want to handle GeoJSON in a separate pull request (as well as improve KML support in another).  CZML shouldn't need any changes.
I mentioned this above, but I think the disconnect in geometry features is going to be really confusing, we need to figure out a way to address that or it will be a usability nightmare.
Add unit tests.

I don't know exactly how all the pieces fit together, but is it too big of a change to separate static, dynamic, and ground, instead of masquerading ground as dynamic?  Deep down in the engine, they are basically separated like this.  We did the same in STK.

Can we delete the entity-clamp-to-ground branch since it was merged into this?

There are problems with both the camera tracking and selection indicator because it is positioned where it thinks the entity is, not where it is actually drawn

I think this is fairly hard since the shadow volume is currently huge to account for min/max height across all of Earth.  Once we have min/max height for just the bounding rectangle (or k-DOP or whatever), we can expose something much more precise.  This will be part of the vector tile work for 3D Tiles since it is also a significant rendering optimization.
Is there something else I am missing for camera support here?

The GroundPrimitive can't currently be batched, so performance is terrible when there are a bunch of them on the screen. Just 900 rectangles drops my fps to 20 (code below).

We'll have the same problem with 3D Tiles, and we'll at least want to batch all the polygons in the tile of the same color.  As we discussed offline, this won't fly for when the color changes dynamically.
The best strategy for entities is to just wait to see what we do for 3D Tiles since the problem will be significantly worse there, and we will have not choice but to aggressively optimize.
Also, the other performance difference is that the fillrate for ground primitives is way more than regular primitives; this will be significantly improved with the local min/max height.

Is there something else I am missing for camera support here?

I assume your comment on shadow volumes applies only to geometry. The problem also exists for billboards and labels (and will for points and models too when we add support).

Geometry outlines can't be clamped to ground which will confuse users who will end up reporting it as a bug.

Geometry materials other than color doesn't work, which will also confuse users who will end up reporting it as a bug (but may not be as big of a deal as outlines).
Obviously lines aren't supported yet. I don't think using corridors as lines will work well at all, but I'm willing to entertain the idea and see where it ends up. (and they don't support materials/outline either)

For outlines and polylines, wait for 3D Tiles vector tiles - or hack around with corridors in the meantime.
If we can prioritize it, it would be nice to get broader material support soon (once we can compute texture coordinates, it should support all the same materials).  @bagnell how many days do you think this would take?  Including the fast paths for different sized polygons.

Is there something else I am missing for camera support here?

I assume your comment on shadow volumes applies only to geometry. The problem also exists for billboards and labels (and will for points and models too when we add support).

Ah, yes.  Those will be easier.

Most of the comments here seem to be around missing features that we also need for 3D Tiles.  Once this PR stabilizes if there is a reasonable way to just get "polygons on terrain" into the Entity API - even with some quirks - I think it is an incremental improvement that many users will be happy with.

I don't know exactly how all the pieces fit together, but is it too big of a change to separate static, dynamic, and ground, instead of masquerading ground as dynamic? Deep down in the engine, they are basically separated like this. We did the same in STK.

The only problem with this suggestion is that you still also have to handle dynamic ground primitives too.  Otherwise, yes, we can absolutely have a StaticGroundGeometryColorBatch class that handles ground geometry (first creating individual primitives and later batching them by color.
I have a pretty good understanding of what needs to change under the hood to dramatically improve both performance and cleanliness of the entity visualization layer, to better batch the new features and common requested use cases from the forum, but it's a largish effort and I unfortunately haven't had the time to work on it.

even with some quirks - I think it is an incremental improvement that many users will be happy with.

I'm not sure I agree.  There are too many caveats and performance isn't there (as of today).  However, if we can fix a fraction of the above issues and add support for GeoJSON and KML, then I could be convinced otherwise.  I really want the Entity API to support terrain, but we need to keep the quality bar high.

If we can prioritize it, it would be nice to get broader material support soon (once we can compute texture coordinates, it should support all the same materials). @bagnell how many days do you think this would take? Including the fast paths for different sized polygons.

I started in a branch. There is code for computing the attributes/uniforms necessary to get the texture coordinates. It isn't validated and I haven't started generating the texture coordinates in the shader. I believe there are three shader paths. Probably a couple weeks worth of work.
For full material support, ground primitives would need normal, tangent and bitangent attributes as well which is only possible when the terrain is an ellipsoid.

Is there something else I am missing for camera support here?

The camera would abruptly change position from collision with the terrain when the LOD changes.

@mramato Can you take a look at this again? I believe you can ignore the changes to GroundPrimitive.js as Dan's changes will be in master before/if this is merged.
I've added a StaticGroundGeometryColorBatch along with a test in the GeometryVisualizerSpec where all the other batch tests were.
I hooked it up to Corridor,  Ellipse, Polygon and Rectangle and added tests for when they should be drawn on terrain for dynamic & static updaters.
Added oneTimeWarning class along with a test suite for cases like when we tell users that outlines are disabled on terrain.

Load the attached geojson file with terrain and you will crash.  This is probably a bug at the primitive level, but we should probably fix it before shipping this. CC @bagnell
countries.geojson.txt

We also need a warning when a polygon on terrain has a material other than color, correct?  Since that won't get drawn on terrain either.

Please merge in master, since @bagnell's changes and fixes are all in.  Unfortunately, the batching did not help performance at all. I verified that the problem is related to our huge bounding volume.
The code here mostly looks okay, but I didn't review too thoroughly yet.  The general approach is fine given the current architecture.  That being said, this is still a long way from coming into master, there are just too many issues.  Here's a list of what I think (at a minimum) still needs to happen.

[ ] Camera flyTo of an entity on terrain.
[ ] Camera tracking of an entity on terrain
[ ] Selection indicator of an entity on terrain
[ ] Point and Model clamping
[ ] Detecting if EXT_FRAG_DEPTH is missing and fallback to non-ground visualization; otherwise this branch breaks IE, Safari, and various mobile devices.
[ ] Performance

Even with the above, we'll still have a bunch of caveats left, but they might not be a deal breaker at that point.

I moved my todo list to the original summary.  Hopefully we can get back this soonish.

I'm interested in this issue for work but as far as I understand there are some limitations at this moment:
most notably from what I'm looking into that entities only wrap terrain with color material, not image
@mramato Do we have a ETA on when this feature could be completed? Or does the current amount of work render it evaluation-proof?

Create a project
Save it.
Switch tot he Projects tab.
Globe goes away and nothing happens.  Check the console and there are errors.

@vrittis I can't provide any sort of official ETA, but I personally hope that terrain support for the Entity API and full material support for ground primitives are both done before the end of the year.  Our work on 3D Tiles will hopefully have some beneficial overlap here.  (And 3D Tiles themselves may help with a lot of the use cases that people are currently using the Entity API for).

What is the minimum amount of work needed to get a first cut of this into master?  Is it the task list above, https://github.com/AnalyticalGraphicsInc/cesium/pull/3406#issue-126028253?

In my opinion, yes, but we might be able to get away without Point and Model clamping (though this is already a common request on the mailing list).  Performance will have to be looked at at the end using typical geojson/czml/kml files and we could punt initially on it.
To me, the real question is, do we have a plan in place to fix the underlying large shadow volume problem, because I believe that's the cause of many of these issues and definitely causes the performance problem.  From my understanding, it's a data problem, because we need to know min/max terrain height, right?
One idea would be to ship a JSON file with rectangles with min/max height for sections of the earth.  Large enough that it's not too much data, but small enough that it gives much better values than hardcoding Mount Everset.

We're going to address the shadow volumes with 3D Tiles and, for, the general case, we might be able to get min/max from the loaded terrain.
I would not let this hold up this PR; so far users of the primitive API have soon that they would rather have the feature soon even with pre-optimized performance.  Then can opt in if you want.

This is probably the top feature we are looking to implement in the coming weeks with our application.  I'll give my vote for getting it into master and optimizing the performance later.

I would not let this hold up this PR; so far users of the primitive API have soon that they would rather have the feature soon even with pre-optimized performance. Then can opt in if you want.

All users will have to opt-in, that was a forgone conclusion.  Even if performance wasn't an issue (and I think it is a big one) that checklist was the bare minimum we could accept to get this into master.   We will have to have a big fat disclaimer on the opt-in options listing the myriad of issues they will encounter if they turn the option on.

This is probably the top feature we are looking to implement in the coming weeks with our application. I'll give my vote for getting it into master and optimizing the performance later.

@colek42 Can you explain some of the details of your use case?  Trust me, no one wants to get terrain support into the Entity API more than I do; but I also don't want a giant step back in quality, performance, and cross-browser compatibility.  I'm curious if your use case would actually work with this PR.  What kind of data are you loading (polygons, polylines, billboards, etc)?  How much of it is there?  Is it time-dynamic?  How big of an area, geographic, do you look at at a time?  Anything info you could provide would be useful.

We have sensor footprints that are described by four corners on the earth.  If we implement terrain these footprints will either be floating or hidden by terrain.  While we many have hundreds of these sensors on the globe at any time we  have some server side code, as well as a webworker, that ensures that only those footprints in the camera's current bounding box are in the entity collection array.  We are looking to implement terrain data in the coming weeks, without clamping for ground-based entities we do not have a clear development path.  We are confident that we can work around the performance issues as long as we can display a dozen or so polygons on the earth.

@colek42  Just to be clear, performance is the least of my worries and not the ultimate hold up for this PR.  If the Entity API doesn't have support when you start coding, for the simple use case you describe it would be trivial to use the Primitive API.  That being said, hopefully we can get this in by the release of 1.20 in April.

@mramato We are just happy we have an excellent open source product we can work on.  Keep doing what you guys are doing.  We have been very happy with our transition from GE thus far.

@mramato so it sounds like you would be OK with this going into master if the task list above (minus performance, initially) is finished, which is:

Camera flyTo and zoomTo of an entity on terrain.
Camera tracking of an entity on terrain
Selection indicator of an entity on terrain
Detecting if EXT_FRAG_DEPTH is missing and fallback to non-ground visualization; otherwise this branch breaks IE, Safari, and various mobile devices.
Point and Model clamping (maybe, https://github.com/AnalyticalGraphicsInc/cesium/pull/3406#issuecomment-189450572)

Is this anything else that is a near-term priority so that we can consolidate branches?

Is this anything else that is a near-term priority so that we can consolidate branches?

I think that list covers it.  As for the maybe next to Point and Model clamping, it it were up to me I would implement it, since everyone wants it and from my understanding the only reason we are holding off on it over possible performance concerns; but since it's ultimately is needed; I'm not sure that's a good reason to hold off.

Closing to move to move the branch out of my fork.


How to select upper bound and delta?

HI, I'm wondering what's the value you used for upper bound and delta in your experiments. I only found the upper bound \Chi=1e-4*n in the paper. Is this the UB used in the code? How about the delta? Thank you very much!

Upper bound is the output of the greedy search. You first run the greedy search then you use its value as the upper bound. Delta is also computed as ub+lb/2 as explained in the paper.

Thanks for your reply!
Another question, in the paper you mentioned  "activations of the final fc layers" are used as the feature. I just want to make sure that is this the logits (10 dimension as in SVHN) instead of the feature from the penultimate layer?

Sorry, we meant the penultimate layer. It is the layer before the softmax

So it is logits (10 dimension as in SVHN). Thanks.

No, it is the penultimate layer. Layer before the softmax. If you refer to here: http://torch.ch/blog/2015/07/30/cifar.html It is the 512 dimensional output before nn.Linear(512,10)


Getting error  (language: Java, type: com.intuit.karate.graal.JsMap) to Java, type: 'java.util.LinkedHashMap': Unsupported target type.

My target Java utility method expects "List<LinkedHashMap<String, Object>>" type. .
My utility method looks like below-
public String dbvsapi(List<Map<String, Object>> dbResults, List<LinkedHashMap<String, Object>> aPiResponse, String primaryKey).
It was working fine in Junit4...After upgrading to Junit5, It is throwing the below error-
org.graalvm.polyglot.PolyglotException: Cannot convert '{api response}', ..'(language: Java, type: com.intuit.karate.graal.JsMap) to Java, type: 'java.util.LinkedHashMap': Unsupported target type.'
Please let me know how to convert JsMap to List<LinkedHashMap<String,Object>> for my utility method to work

follow this process to reopen please: https://github.com/karatelabs/karate/wiki/How-to-Submit-an-Issue


Emoji and Internationalized Domain Names should be hyperlinked

Example: www.🍕💩.ws - GitHub does it correctly!

In my opinion to handle the characters emotions as the link is not correct. This may cause some mistakes if the text contains both the link and choose emotions. And in the plugin everything works correctly.

@dandv I've been looking to add this functionality in the form of a plugin. Will update here when we have support for it.

Any updates?

Heeeey, any progress on it? Can we make a plugin for Unicode (not Punycode) domains?

Hi all, thanks for your many years of patience on this one!
Internationalized domain support is officially in development and is now available for preliminary testing the the latest v3.0.0-beta.1. A production release coming soon.
If you can, please try it out and report any bugs you find

Fixed in v3


Resolve the warning "Avoid using actions" in the Deployment Manager

Resolve the warning displayed after the Deployment Manager job starts.
"Warning avoid using actions" (see image below)

I contacted Marketplace team for next steps.

Main documentation page for migrating away from custom actions: https://cloud.google.com/deployment-manager/docs/migrations/actions
Documentation for custom type providers (alternative to custom actions): https://cloud.google.com/deployment-manager/docs/migrations/custom-types-custom-backends


Data cache not functioning since 3.3.1

Hey.
I noticed that my data cache stopped functioning ever since I upgraded to 3.3.3 (from 3.2). I went through the code, debugged some, did some testing by myself and I feel like I found an issue.
When an event is extended in the 'request' nitro hook, any changes introduced to the event are lost, only event.context changes persist:

FYI - I am doing SSR in SWR mode (no pregenaration).
Apparently Nitro might create new events through lifecycle and it won't be able to copy over keys that it is not aware of.
This might also happen in middlewares.
Would you welcome a PR that puts stuff on event.context instead of just event?

I was under the impression that whenever a new event is created (for example when using $fetch in a component to get some data from a server handler) that the hooks that add the cache context are also called again. But I could be wrong here.
Originally, the context was actually set on event.context but I changed this in #65, because it was leaking across the lifecycle. For example, when using useRouteCache() inside a server handler that is called from within a page component, you would actually set the cacheability for both the server route and the page itself, since it's a single context object that is now shared in both cases.
Could you tell me in what scenario exactly the data cache was not working? I assume it's not generally not working, right? The data cache feature is covered by several E2E tests; I would be quite shocked if it works in tests but doesn't work in actual installations.

I updated to the latest Nuxt version in the module and ran the tests; and indeed a ton of tests started to fail, including one's for the data cache. So the data cache (and likely all caches) are broken. Not sure if its related to event.context, but I will investigate and hopefully find a fix.

I can reproduce the issue by using swr: true on a route that uses the data cache. Let's see if there's a way to fix this without breaking non-swr behaviour...


Moving additional paths into top level of object

As noted here:
https://github.com/apinf/restivus-swagger/issues/18

This looks fine. Lets just clean up the whitespace in the file, so that it is consistent. Previously, we had just one developer writing the plugin, but now we have multiple contributors.

@brylie I have the whitespace corrected file ready for a PR, should I kill this PR and create another?

We can still work from this PR, as long as you are making changes to the same branch. Is this PR ready for review?

Same branch


Error: invalid mount config for type "bind": bind source path does not exist

File: get-started/part5.md, CC @johndmulhausen
Step 2 in the Persistent Data section where we need to create a ./data folder on the manager node, isn't working for me because the Redis container outputs the error message invalid mount config for type "bind": bind source path does not exist after deploying the stack. But if I also create a ./data folder on my host (Mac), along with the data folder on the vm (VirtualBox), it will work. Although, no data is stored in the Mac folder. I'm not sure what is the correct way to handle this, probably I had to end my session and connect to the virtual machine again after creating the folder? I use the docker toolbox setup (on an older Mac).

I'm running the latest version of Docker for Mac, and running into what may be a similar issue, oddly enough with a /data dir (but not limited to it). The bind mounts documentation says:

The file or directory does not need to exist on the Docker host already.

Which is not the behavior I'm seeing.
Specifically, bind mounts do seem to work for some directories on the host as a source, notably /tmp:
03077-mbp:~ marc$ docker run -d \
  -it \
  --rm \
 ...
  --mount type=bind,source=/tmp,target=/data \
 ...
   73f66c914e091d6c830efd0f31b87a03613aaf8d07df1411e895033ad28fc536

Worked fine. I execed into bash, and the mount worked as expected. When I tried to run the same run with /tmp/f, which does not exist, I got:
03077-mbp:~ marc$ docker run -d \
  -it \
  --rm \
 ...
  --mount type=bind,source=/tmp/f,target=/data \
 ...
docker: Error response from daemon: invalid mount config for type "bind": bind source path does not exist.
See 'docker run --help'.

Lastly, when I originally tried what I actually wanted, map /data on the host to /data in the container, I got the same as above, except /data does exist on the host, with wide-open permissions:
docker: Error response from daemon: invalid mount config for type "bind": bind source path does not exist.
See 'docker run --help'.
03077-mbp:~ marc$ ls -hla / | grep data
drwxrwxrwx   2 root  wheel    68B Oct  1 22:11 data

There's a difference when using the -v or --mount flag; the -v flag (for historic reasons) creates the path, but the --mount flag does not.
From the same page in the documentation ;

If you use -v or --volume to bind-mount a file or directory that does not yet exist on the Docker host, -v will create the endpoint for you. It is always created as a directory.

If you use --mount to bind-mount a file or directory that does not yet exist on the Docker host, Docker does not automatically create it for you, but generates an error.

@thaJeztah thanks so much for calling that out! I missed that in large part because I was confused why it was complaining about a dir that does exist did not, and I'll admit I was flailing a bit. Your comment did lead me to the real issue, which seems like a bug, to me.
As above, when I used --mount type=bind,source=/data,target=/data, I got:
docker: Error response from daemon: invalid mount config for type "bind": bind source path does not exist.
See 'docker run --help'.

When I changed that to -v /data:/data, I got a very different error:
docker: Error response from daemon: Mounts denied:
The path /data
is not shared from OS X and is not known to Docker.
You can configure shared paths from Docker -> Preferences... -> File Sharing.
See https://docs.docker.com/docker-for-mac/osxfs/#namespaces for more info.

TBH, I haven't used docker locally since the boot2docker days, and this setting didn't even occur to me. The [different] response from -v helped me solve the issue in seconds.
IMO:

"The file or directory does not need to exist on the Docker host already," is still an unqualified topic sentence, and probably should be modified to be more clear.
--mount should emit the same error response as -v. It's odd [to me, not knowing the internals] that -v seems to be the one to carry around more historical baggage, but has the better error response.

Again, thank you, @thaJeztah!

It's odd [to me, not knowing the internals] that -v seems to be the one to carry around more historical baggage, but has the better error response.

Docker for Mac uses a proxy for the API, and I suspect that error is added inside that proxy on Docker for Mac (it's not an error that's generated by the "engine"); could you open an enhancement request for that in the Docker for Mac issue tracker? https://github.com/docker/for-mac/issues

Yep, will do.

This content has been rewritten since the issue was filed and I think the problem no longer exists.

When running Docker on macOS, the mini VM (xhyve) may not have the directory you're trying to bind mount. Here's a 1-liner to make those directories inside the VM (not on your macOS filesystem):
$ docker run -it --privileged --pid=host debian nsenter -t 1 -m -u -n -i \
        mkdir -p /some-required-path

try create mounted directories on host machine(s) before running

For the record.
You may run into this on Windows after you change your Windows account password.

Open Docker for Windows Settings.
Click Shared Drives / Reset credentials...
Share drive once again.

I did
docker-machine env myvm1 and then
docker stack deploy...
and similar message "invalid mount config for type "bind": bind mount source path does not exist: /home/docker/data" appeared.
I solved it by docker ssh myvm1 and creating folder 'data' inside docker user folder

Thanks @cztomek; that pointed me in the right direction for Mac. For anyone who's on Mac, in your docker preferences under 'File Sharing', make sure that the directory that you're trying to provide for the bind mount is covered by the directories listed there.

For the record.
You may run into this on Windows after you change your Windows account password.

Open Docker for Windows Settings.
Click Shared Drives / Reset credentials...
Share drive once again.

This worked for me. TY!

For MacOS: Depending on where you are binding from Docker might not have permission to access the directory. You can change that by adding Docker under MacOS Settings » Security » Privacy » Full Disk Access. And make sure as well to allow the directory to be bind mounted under Docker Settings Resources » File Sharing

If I am using Docker machine instead of Docker desktop this setting not coming for me. Any alternative ? I am using Docker machine because Mac OS 10.12.6 doesn't support Docker desktop.

I have the same issue, under Ubuntu 1804, $ docker --version Docker version 20.10.8, build 3967b7d
$ touch /data/wangjl/xxx012
$ docker run -it     -v /data/wangjl:/eMzMyO     --rm     openjdk:9.0.1-11-slim bash
docker: Error response from daemon: error while creating mount source path '/data/wangjl': mkdir /data: read-only file system.

The solution to my version of the problem was restarting Docker.

The solution to my version of the problem was restarting Docker.

Re-starting Docker does nothing help on my machine.
Hints by a post years ago,
I checked the install location of my Docker ps -aux | grep docker,  and I think it was installed by snap.
Then I removed it and re-installed by apt-get, now everything is fine, though they are the same version.

Reproduced on docker-compose up command (latest 4.0.1 for Windows). Solved by disabling "Use Docker Compose V2 release candidate" in experimental features tab

@At4m4n if you have steps to reproduce, can you open a ticket in https://github.com/docker/compose/ with details and minimal reproduction steps?

Same, just turned off release candidate for the mac 10.14.6 after upgrade docker

The solution for me on Mac was:
Docker > Preferences > General  > uncheck "Use Docker Compose V2"

did any of you experienced this issue while spawning a container from another container?
while binding folder between two of the containers ?
steps taken:

mac > runs container A
container A:  docker runs container B and dies
container B: docker runs and bind mounts a folder /tmp/MYFOLDER/MYFILE.conf to container C

for clarification using "/var/run/docker.sock:/var/run/docker.sock" and not DockerInDocker
I've checked in container B whether /tmp/MYFOLDER/MYFILE.conf is there and it is,
but when container B trying to run container C it errors with:
Bad Request ("invalid mount config for type "bind": bind source path does not exist: /tmp/MYFOLDER/MYFILE.conf")


polygon union bug

Please note
from shapely import geometry
from shapely import wkt
from shapely.ops import cascaded_union
from shapely.ops import unary_union
a = geometry.Polygon([(0,0),(10,0),(10,10),(0,10)],[[(6,6),(6,8),(8,8),(8,6)], [(2,2),(2,4),(4,4),(4,2)]])
b = geometry.Polygon([(10,0),(11,0),(11,10),(0,10)])
c = b.union(a)
d = cascaded_union([b, a])
e = unary_union([a,b])
print a.wkt
print c.wkt
print d.wkt
print e.wkt
Expected behavior and actual behavior.
a polygon with two holes, when union, one of the holes was disappeared
actual behavior
POLYGON ((0 0, 10 0, 10 10, 0 10, 0 0), (6 6, 6 8, 8 8, 8 6, 6 6), (2 2, 2 4, 4 4, 4 2, 2 2))
POLYGON ((10 10, 11 10, 11 0, 10 0, 0 0, 0 10, 10 10), (2 2, 4 2, 4 4, 2 4, 2 2))
POLYGON ((10 10, 11 10, 11 0, 10 0, 0 0, 0 10, 10 10), (2 2, 4 2, 4 4, 2 4, 2 2))
POLYGON ((10 0, 0 0, 0 10, 10 10, 11 10, 11 0, 10 0), (2 2, 4 2, 4 4, 2 4, 2 2))
expected behavior
POLYGON ((0 0, 10 0, 10 10, 0 10, 0 0), (6 6, 6 8, 8 8, 8 6, 6 6), (2 2, 2 4, 4 4, 4 2, 2 2))
POLYGON ((10 10, 11 10, 11 0, 10 0, 0 0, 0 10, 10 10), (6 6, 6 8, 8 8, 8 6, 6 6), (2 2, 4 2, 4 4, 2 4, 2 2))
POLYGON ((10 10, 11 10, 11 0, 10 0, 0 0, 0 10, 10 10),(6 6, 6 8, 8 8, 8 6, 6 6),  (2 2, 4 2, 4 4, 2 4, 2 2))
POLYGON ((10 0, 0 0, 0 10, 10 10, 11 10, 11 0, 10 0), (6 6, 6 8, 8 8, 8 6, 6 6), (2 2, 4 2, 4 4, 2 4, 2 2))
Steps to reproduce the problem.
Operating system
Linux
Shapely version and provenance
1.6.4

Hey @duanjianguo,
Here are your two original polygons, with a pinkish a underneath a light colored b.

And here is a purple overlay of the union(s) (they are all the same) which shapely produces in your example:

This, to me, is the expected result of a union here.


[alert/dv] Support reset logic alert in alert_esc_agent

I was working on special target sequence for alert_handler and found current agent's reset logic is a bit messy.
This PR cleans up the current reset logic and adding the missing reset support by:
1). Add fork join any to all alert and escalation drivers to handle reset. (instead of using "if under_reset()")
2). Avoid duplicated code in monitors by adding a common function reset_signals in base_monitor.
Signed-off-by: Cindy Chen<EMAIL_ADDRESS>

Thanks for your comments Rasmus. Sorry the title of this PR is confusing. This PR attempts to fully support reset logic in alert_esc_agent. The reason I used "more" because there are reset support in alert_esc_agent already, just not in a unified way, and there are some duplicated code.
Thanks for your suggestion, and I renamed the PR title and write more details about the description.

The latest force-push clean up the fork join_any code by moving the code inside to a separate task called drive_esc_resp(). No functional change.

The latest force-push added a wait(XXX.size()> 0 && !under_reset) condition for the forever loop, to avoid any deadloop.

@cindychip
nit: esc_monitor Line 75 change
end
// when it is not a ping
if (get_esc() === 1'b1) begin

to
end else  begin
there is no need to check both cases every time
get_esc() must be either 1 or 0

Hi Rasmus,
Thanks for your nit suggestions. (esc_monitor line 75)
end
// when it is not a ping
if (get_esc() === 1'b1) begin

I use a if (get_esc() === 1'b1) begin here because "when is not a ping" could be the case where: first it is a ping response, but it is interrupted by real escalation signals, then the ping transaction will be aborted, and goes into escalation response stage. Sorry about the confusion, my PR #2689 adds more comment for this.

Hi Rasmus,
Thanks for your nit suggestions. (esc_monitor line 75)
end
// when it is not a ping
if (get_esc() === 1'b1) begin

I use if (get_esc() === 1'b1) begin here because "when is not a ping" could be the case where: first it is a ping response, but it is interrupted by real escalation signals, then the ping transaction will be aborted, and goes into escalation response stage. Sorry about the confusion, my PR #2689 adds more comment for this.

@cindychip ahh ok - and this way you see it one clock earlier.


Align httpstatus fault validation with envoy

Fixes https://github.com/istio/istio/issues/15355
See https://github.com/envoyproxy/envoy/blob/master/api/envoy/config/filter/http/fault/v2/fault.proto#L28
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[x] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: howardjohn
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS [howardjohn]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@howardjohn: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
27a39830f44ac3c02c9f6358e9a1199efc343a80
link
/test istio-unit-tests-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
27a39830f44ac3c02c9f6358e9a1199efc343a80
link
/test istio-unit-tests-master

prow/codecov.sh
27a39830f44ac3c02c9f6358e9a1199efc343a80
link
/test istio-codecov-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
27a39830f44ac3c02c9f6358e9a1199efc343a80
link
/test istio-unit-tests-master

prow/codecov.sh
27a39830f44ac3c02c9f6358e9a1199efc343a80
link
/test istio-codecov-master

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
27a39830f44ac3c02c9f6358e9a1199efc343a80
link
/test istio-pilot-e2e-envoyv2-v1alpha3-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
27a39830f44ac3c02c9f6358e9a1199efc343a80
link
/test istio-unit-tests-master

prow/codecov.sh
27a39830f44ac3c02c9f6358e9a1199efc343a80
link
/test istio-codecov-master

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
27a39830f44ac3c02c9f6358e9a1199efc343a80
link
/test istio-pilot-e2e-envoyv2-v1alpha3-master

prow/integ-new-installer-k8s-presubmit-tests.sh
27a39830f44ac3c02c9f6358e9a1199efc343a80
link
/test integ-new-install-k8s-presubmit-tests-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
27a39830f44ac3c02c9f6358e9a1199efc343a80
link
/test istio-unit-tests-master

prow/codecov.sh
27a39830f44ac3c02c9f6358e9a1199efc343a80
link
/test istio-codecov-master

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
27a39830f44ac3c02c9f6358e9a1199efc343a80
link
/test istio-pilot-e2e-envoyv2-v1alpha3-master

prow/integ-new-installer-k8s-presubmit-tests.sh
27a39830f44ac3c02c9f6358e9a1199efc343a80
link
/test integ-new-install-k8s-presubmit-tests-master

prow/integ-mixer-k8s-presubmit-tests.sh
27a39830f44ac3c02c9f6358e9a1199efc343a80
link
/test integ-mixer-k8s-presubmit-tests-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
27a39830f44ac3c02c9f6358e9a1199efc343a80
link
/test istio-unit-tests-master

prow/codecov.sh
27a39830f44ac3c02c9f6358e9a1199efc343a80
link
/test istio-codecov-master

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
27a39830f44ac3c02c9f6358e9a1199efc343a80
link
/test istio-pilot-e2e-envoyv2-v1alpha3-master

prow/integ-new-installer-k8s-presubmit-tests.sh
27a39830f44ac3c02c9f6358e9a1199efc343a80
link
/test integ-new-install-k8s-presubmit-tests-master

prow/integ-mixer-k8s-presubmit-tests.sh
27a39830f44ac3c02c9f6358e9a1199efc343a80
link
/test integ-mixer-k8s-presubmit-tests-master

prow/racetest.sh
27a39830f44ac3c02c9f6358e9a1199efc343a80
link
/test istio-racetest-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
27a39830f44ac3c02c9f6358e9a1199efc343a80
link
/test istio-pilot-e2e-envoyv2-v1alpha3-master

prow/integ-mixer-k8s-presubmit-tests.sh
27a39830f44ac3c02c9f6358e9a1199efc343a80
link
/test integ-mixer-k8s-presubmit-tests-master

prow/racetest.sh
27a39830f44ac3c02c9f6358e9a1199efc343a80
link
/test istio-racetest-master

prow/integ-new-installer-k8s-presubmit-tests.sh
8546b0c23d7a5760386d795e9f480474c7dfe198
link
/test integ-new-install-k8s-presubmit-tests-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/racetest.sh
27a39830f44ac3c02c9f6358e9a1199efc343a80
link
/test istio-racetest-master

prow/integ-new-installer-k8s-presubmit-tests.sh
8546b0c23d7a5760386d795e9f480474c7dfe198
link
/test integ-new-install-k8s-presubmit-tests-master

prow/integ-mixer-k8s-presubmit-tests.sh
8546b0c23d7a5760386d795e9f480474c7dfe198
link
/test integ-mixer-k8s-presubmit-tests-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/assign @nmittler @GregHanson

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: howardjohn, nmittler
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS [howardjohn,nmittler]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


question about in memory accumulation

I have a question (but do not know if the issues are the appropriate place for this).  if not passed a block but "lazy" is called, will the objects still accumulate in memory?  for example, will objects still accmulate in memory when invoked like this?
        File.open(path, 'r') do |f|
          Json::Streamer.parser(file_io: f).get(nesting_level: 1).lazy
        end

if this does not have the desired effect, will wrapping things in Enumerator::Lazy.new help?

Hey @richardwan, I'm not sure but there's a spec for memory usage, you can play around with that.


Devilbox Release v1.0.0

Devilbox Release v1.0.0
READFIRST
This branch is constantly being rebased from master until final merge, therefore requires git force pushing. So how to update changes from this branch:
# Receive new commits
git fetch --all --prune

# Delete release/v1.0.0 branch
git checkout master
git branch -D release/v1.0.0

# Checkout release/v1.0.0 again
git checkout release/v1.0.0
git pull origin release/v1.0.0

Then you will have to ensure to remove container before starting them up again:
docker-compose stop
docker-compose rm
docker-compose up

IMPORTANT
When using this branch, you will loose all you current data for MySQL, PostgreSQL and MongoDB, so ensure to make a backup first.

Backup Mysql
Backup PostgreSQL
Backup MongoDB

Once you have backed up everything, start the Devilbox from this branch and import your data.

DOCUMENTATION
Documentation for this release is available here: https://devilbox.readthedocs.io/en/release-v1.0.0/
DESCRIPTION
This will be the first stable release of the Devilbox.
Features
PR's:

[x] Docker Volumes: https://github.com/cytopia/devilbox/pull/383
[ ] ~Internal DNS and Auto DNS separation: https://github.com/cytopia/devilbox/pull/411~: moved to Milestone 1.1
[X] Semantic versioning for faster+safer releases
[x] Official MySQL, MariaDB and Percona Docker container

Issues:

Refs: https://github.com/cytopia/devilbox/issues/175

Notable readings

CHANGELOG
UPDATING
CONTRIBUTING

What a good new !
BTW, could you envisage to use this changelog format

Hi, I am trying this branch and getting this error:
Recreating devilbox_bind_1 ... error

ERROR: for devilbox_bind_1  Cannot start service bind: driver failed programming external connectivity on endpoint devilbox_bind_1 (0cca32e8f31ea237b52a7257a1d84276f3d3376f1a6ba4f304f3598a418d1eab): Error starting userland proxy: Bind for <IP_ADDRESS>:1050: unexpected error Permission denied

ERROR: for bind  Cannot start service bind: driver failed programming external connectivity on endpoint devilbox_bind_1 (0cca32e8f31ea237b52a7257a1d84276f3d3376f1a6ba4f304f3598a418d1eab): Error starting userland proxy: Bind for <IP_ADDRESS>:1050: unexpected error Permission denied
ERROR: Encountered errors while bringing up the project.

I have deleted all the images, container , volumes.
I have also checked if the port is in used (There are not)
But changing the DNS port to 53 works.

@vikas5914 The DNS container (bind) will listen on both ports, TCP and UDP. Did you ensure that for both protocols there was nothing listening?

The release branch has been tagged with v1.0.0-alpha to provide a stable point in time.

@cytopia
I tried v1.0.0-alpha1 (ubuntu 18.04 server).

had to do this (currently I'm not using PostgreSQL)
#- PGDATA=/var/lib/postgresql/data/pgdata
to be able to rebuild containers
also, had to change (nginx)
image: devilbox/${HTTPD_SERVER}:0.30
to
image: devilbox/${HTTPD_SERVER}:0.28
to be able to access the devilbox site

Otherwise, it seems to be working (MySQL, mongoDB).
(nvm is working too; thank you)

@az09asdf

why do you need to comment the PGDATA directory?
Changing http image to image: devilbox/${HTTPD_SERVER}:0.28 should not be necessary at all

@cytopia I tried 1050, 1051, 1052 and 1049 ports. Same result. (on 12th Feb)

@cytopia

tried to reproduce error: now it's gone (false alarm; sorry; cannot remember error message)
still the same: change to 0.30 prevents access to the devilbox site (the same for 0.15 version)
(It's probably irrelevant, by I'm using somewhat specific setup: I'm working in Windows (coding, git, browsers) and using devilbox on an ubuntu 18.04 server virtual machine. However, never had such an issue before.)

@az09asdf I have a strong feeling that this might have been related to a Nginx configuration change. Do you get an error like this: nginx: [emerg] "client_max_body_size" directive is duplicate in /etc/httpd-custom.d/devilbox-custom.conf:1 via Docker logs?

@vikas5914 one thing I can suggest is to fully clean everything:
# Stop Devilbox and remove its stopped container
docker-compose stop
docker-compose rm -f
# Stop and remove all other container
docker ps -q | xargs docker stop
docker ps -qa | xargs docker rm

Then make sure that your .env file equals to the new env-example.
Also ensure there is for sure nothing else listening on UDP for that port.
And start Devilbox again.

@cytopia
Commenting client_max_body_size in my custom nginx.conf solved the issue.

do you know how to set  client_max_body_size for 0.30 ?
couldn't find the error you suggested: "via Docker logs" means devilbox/log/nginx-stable/ ?

@cytopia
Commenting client_max_body_size in my custom nginx.conf solved the issue.

do you know how to set  client_max_body_size for 0.30 ?
couldn't find the error you suggested: "via Docker logs" means devilbox/log/nginx-stable/ ?

Yes you can still overwrite this value if you are on a different context: http://nginx.org/en/docs/http/ngx_http_core_module.html#client_max_body_size
It currently has been set on the http context and you would need the server or location context to change this value. This can be achieved via custom vhost settings:

https://devilbox.readthedocs.io/en/latest/vhost-gen/customize-all-virtual-hosts-globally.html#vhost-gen-customize-all-virtual-hosts-globally
https://devilbox.readthedocs.io/en/latest/vhost-gen/customize-specific-virtual-host.html#vhost-gen-customize-specific-virtual-host

The actual issue that has information on why this was set (to 0 to be in sync with Apache 2.(2|4)) is here:  https://github.com/cytopia/devilbox/issues/356

I will postpone the planned merge until the current issues for Mac and MySQL are investigated.

@cytopia
I removed everything (images, volume, network and Devil) and tried again, it worked.

@vikas5914 just in time :-)
The freeze is removed, issue in question (#542) has been resolved


Custom functions not working when excluded from "compile" item group in VS

I'm trying to use custom functions in my project, but unable to make them work without including its .cs in the "compile" item group. I.e. it is not working when I do the following:
<ItemGroup>
	<Compile Remove="CustomFunctions.nt.cs" />
	<None Include="CustomFunctions.nt.cs" />
</ItemGroup>

The main reason to make that is to exclude NTypewriter custom code from my main code, since I consider it as service code, i.e. dev only. And in the NTypewriter docs there were said that it compiles custom functions code outside the project and its settings it was declared.
Is it a bug or what I'm doing wrong? Thank you in advance!
NTypewriter v0.3.0

Yes, there are compiled outside of the project that includes them. The problem is that Roslyn API is used to find configuration files, and Roslyn API only sees files that have build action set on "compile". The problematic code is here GetDecoratedSyntaxTreesWithAttribute.
Right now there is a no way of achieving what you want, but it may appear in future versions.


Can’t log into keybase

Hi, I changed phones and don’t have access to log into my keybase account. I think I need to reset it. Please help!
Ben

Help?


Frrist/refactor/docker wasm cli

A refactor of the CLI to align with the principles described here: https://github.com/spf13/cobra/blob/main/user_guide.md#organizing-subcommands

Without the deletions, could this be merged into main rather than another branch?  With it moving a lot of files about I'm going to be nervous about making changes to any of these 90+ files for fear of changes getting lost in a few months time when all the branches get merged into each other.

@rossjones (and all) I have rebased this onto main as a follow on to https://github.com/bacalhau-project/bacalhau/pull/2552


Implement fieldreplacementby3digits

Codecov Report

Merging #434 (5a25c3e) into main (e345ef3) will increase coverage by 0.61%.
The diff coverage is 72.00%.

@@            Coverage Diff             @@
##             main     #434      +/-   ##
==========================================
+ Coverage   48.23%   48.84%   +0.61%
==========================================
  Files          51       51
  Lines        6075     6029      -46
  Branches      993      996       +3
==========================================
+ Hits         2930     2945      +15
+ Misses       2960     2895      -65
- Partials      185      189       +4

Flag
Coverage Δ

unittests
48.84% <72.00%> (+0.61%)
:arrow_up:

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

Impacted Files
Coverage Δ

...ols/marc_rules_transformation/rules_mapper_base.py
71.95% <ø> (ø)

...ols/marc_rules_transformation/rules_mapper_bibs.py
62.95% <33.33%> (+3.11%)
:arrow_up:

...ration_tools/test_infrastructure/mocked_classes.py
90.74% <93.75%> (+44.07%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Code review with @branchedelac


Potentially broken links in free-programming-books.md

I scanned the file via HTTP link checker and go this:
Error: https://github.com/practicingruby/rbp-book/tree/gh-pages/pdfs on line 2588 is unreachable.
Error: https://github.com/mdipierro/nlib on line 336 is unreachable.
Error: https://github.com/google/styleguide/blob/gh-pages/objcguide.md on line 2159 is unreachable.
Error: http://stephane.ducasse.free.fr/FreeBooks.html on line 254 is unreachable.
Error: http://stephane.ducasse.free.fr/FreeBooks/ on line 271 is unreachable.
Error: https://cloud4scieng.org/chapters/ on line 381 is unreachable.
Error: https://docs.blender.org/manual/en/latest on line 283 is unreachable.
Error: http://homepages.inf.ed.ac.uk/rbf/BOOKS/BANDB/bandb.htm on line 427 is unreachable.
Error: http://homepages.inf.ed.ac.uk/rbf/BOOKS/PHILLIPS/ on line 644 is unreachable.
Error: https://people.math.gatech.edu/~cain/winter99/complex.html on line 545 is unreachable.
Error: https://people.math.gatech.edu/~herod/Hspace/Hspace.html on line 570 is unreachable.
Error: https://people.math.gatech.edu/~cain/notes/calculus.html on line 576 is unreachable.
Error: http://home.iitk.ac.in/~arlal/book/la.pdf on line 567 is unreachable.
Error: http://web4.cs.ucl.ac.uk/staff/D.Barber/pmwiki/pmwiki.php?n=Brml.HomePage on line 491 is unreachable.
Error: https://intelligent-optimization.org/LIONbook/lionbook_3v0.pdf on line 519 is unreachable.
Error: https://mitpress.ublish.com/ereader/7093/?preview=#page/Cover on line 496 is unreachable.
Error: https://pi.math.cornell.edu/~hatcher/AT/ATpage.html on line 532 is unreachable.
Error: https://mitpress.ublish.com/ereader/77/?preview#page/Cover on line 542 is unreachable.
Error: https://ithemes.com/wp-content/uploads/downloads/2012/09/10-keys-to-great-landing-pages-eBook.pdf on line 606 is unreachable.
Error: https://www.math.ucdavis.edu/~linear/linear-guest.pdf on line 568 is unreachable.
Error: http://book.mixu.net/distsys/single-page.html on line 701 is unreachable.
Error: https://open.sap.com on line 689 is unreachable.
Error: https://open.hpi.de on line 688 is unreachable.
Error: http://pages.di.unipi.it/ricci/501302.pdf on line 711 is unreachable.
Error: http://pages.cs.wisc.edu/~remzi/OSTEP/ on line 745 is unreachable.
Error: https://us.fixstars.com/products/opencl/book/OpenCLProgrammingBook/contents/ on line 768 is unreachable.
Error: https://papl.cs.brown.edu/2019/ on line 892 is unreachable.
Error: https://pages.apigee.com/rs/apigee/images/api-design-ebook-2012-03.pdf on line 868 is unreachable.
Error: https://download.microsoft.com/download/0/F/B/0FBFAA46-2BFD-478F-8E56-7BF3C672DF9D/Introducing ASP.NET Web Pages 2.pdf on line 983 is unreachable.
Error: https://bash.cyberciti.biz/guide/Main_Page on line 1049 is unreachable.
Error: http://daly.axiom-developer.org/clojure.pdf on line 1188 is unreachable.
Error: https://ptolemy.berkeley.edu/books/leeseshia/releases/LeeSeshia_DigitalV2_2.pdf on line 1329 is unreachable.
Error: https://archive.org/details/JavaJavaJavaObject-orientedProblemSolving/page/n0 on line 1635 is unreachable.
Error: http://singlepageappbook.com on line 1743 is unreachable.
Error: https://singlepagebook.supportbee.com on line 1780 is unreachable.
Error: https://www.dashingd3js.com/table-of-contents on line 1794 is unreachable.
Error: https://www.math.ust.hk/~machas/scientific-computing.pdf on line 2065 is unreachable.
Error: https://www.cs.cornell.edu/courses/cs3110/2019sp/textbook/ on line 2169 is unreachable.
Error: http://phpsec.org/projects/guide/ on line 2239 is unreachable.
Error: http://www.obeythetestinggoat.com/pages/book.html on line 2450 is unreachable.
Error: http://www.burns-stat.com/pages/Tutor/R_inferno.pdf on line 2537 is unreachable.
Error: https://ruby-doc.org/docs/ruby-doc-bundle/UsersGuide/rg/index.html on line 2596 is unreachable.
Error: http://homepages.inf.ed.ac.uk/stg/NOTES/ on line 2810 is unreachable.
Error: https://www.red-gate.com/products/sql-development/sql-source-control/entrypage/sql-server-source-control-basics on line 2795 is unreachable.
Error: https://leanpub.com/thebigbookofpowershellerrorhandling on line 2320 is unreachable.
Error: https://en.wikibooks.org/wiki/Clipper_Tutorial%3A_a_Guide_to_Open_Source_Clipper(s on line 2963 is unreachable.
Error: https://homepages.uc.edu/~thomam/Intro_Unix_Text/TOC.html on line 2889 is unreachable.
Error: http://www-inst.eecs.berkeley.edu/~cs61b/fa14/book2/data-structures.pdf on line 339 is unreachable.
Error: http://ocw.mit.edu/courses/mathematics/18-05-introduction-to-probability-and-statistics-spring-2014/ on line 560 is unreachable.
Error: http://ocw.mit.edu/ans7870/resources/Strang/Edited/Calculus/Calculus.pdf on line 540 is unreachable.
Error: http://ocw.mit.edu/resources/res-6-004-principles-of-computer-system-design-an-introduction-spring-2009/online-textbook/part_ii_open_5_0.pdf on line 668 is unreachable.
Error: http://ocw.mit.edu on line 686 is unreachable.
Error: http://ocw.mit.edu/courses/electrical-engineering-and-computer-science/6-02-introduction-to-eecs-ii-digital-communication-systems-fall-2012/readings/ on line 697 is unreachable.
Error: http://www.sp4comm.org on line 626 is unreachable.
Error: http://cs.gmu.edu/~sean/book/metaheuristics/ on line 555 is unreachable.
Error: http://people.math.umass.edu/~lavine/Book/book.html on line 562 is unreachable.
Error: http://cnx.org/contents/5e0744f9-9e79-4348-9237-ed012213a2d6%4040.9 on line 544 is unreachable.
Error: http://www.cse.buffalo.edu/~rapaport/Papers/phics.pdf on line 664 is unreachable.
Error: https://www.owasp.org/images/1/19/OTGv4.pdf on line 828 is unreachable.
Error: http://cyber.law.harvard.edu/wealth_of_networks/Main_Page on line 735 is unreachable.
Error: http://pages.tacc.utexas.edu/~eijkhout/istc/istc.html on line 763 is unreachable.
Error: http://www-inst.eecs.berkeley.edu/~cs61a/sp12/book/ on line 2447 is unreachable.
Error: http://www.cse.buffalo.edu/~shapiro/Commonlisp/ on line 2000 is unreachable.
Error: http://homepages.mcs.vuw.ac.nz/~tk/fps/fps-sans-escher.pdf on line 1291 is unreachable.
Error: https://itunes.apple.com/us/book/using-swift-cocoa-objective/id888894773?mt=11 on line 2828 is unreachable.
Error: http://use-the-index-luke.com on line 2769 is unreachable.
Error: http://blogs.msdn.com/b/microsoft_press/archive/2014/04/02/free-ebook-introducing-microsoft-sql-server-2014.aspx on line 2782 is unreachable.
Error: http://addyosmani.github.io/backbone-fundamentals/ on line 1781 is unreachable.
Error: http://effbot.org/librarybook/ on line 2457 is unreachable.
Error: http://www.cs.bu.edu/teaching/unix/reference/ on line 2891 is unreachable.
Error: http://www.linuxfromscratch.org/alfs/download.html on line 1958 is unreachable.
Error: http://www.linuxfromscratch.org/lfs/view/stable/ on line 1972 is unreachable.
Error: http://www.red-gate.com/products/sql-development/sql-prompt/entrypage/sql-query-optimizer-ebook3 on line 2779 is unreachable.
Error: http://www-01.ibm.com/support/docview.wss?uid=swg27036733 on line 1202 is unreachable.
Error: https://pages.apigee.com/oauth-big-picture-ebook.html on line 853 is unreachable.
Error: http://www.cs.berkeley.edu/~bh/ss-toc2.html on line 2705 is unreachable.
Error: http://python-ebook.blogspot.co.uk on line 2401 is unreachable.
Error: https://www.packtpub.com/free-ebooks/hands-cloud-administration-azure on line 384 is unreachable.
Error: https://www.packtpub.com/free-ebooks/artificial-intelligence-big-data on line 367 is unreachable.
Error: https://www.packtpub.com/free-ebooks/docker-cookbook-second-edition on line 436 is unreachable.
Error: https://usborne.com/browse-books/features/computer-and-coding-books/ on line 1009 is unreachable.
Error: https://www.packtpub.com/free-ebooks/full-stack-react-projects on line 1868 is unreachable.
Error: https://www.packtpub.com/free-ebooks/effective-devops-aws-second-edition on line 630 is unreachable.
Error: https://www.packtpub.com/free-ebooks/java-projects-second-edition on line 1640 is unreachable.
Error: https://www.packtpub.com/free-ebooks/industrial-cybersecurity on line 645 is unreachable.
Error: https://www.packtpub.com/free-ebooks/kubernetes-cookbook-second-edition on line 438 is unreachable.
Error: https://www.packtpub.com/free-ebooks/mastering-opencv-4-third-edition on line 430 is unreachable.
Error: https://www.packtpub.com/free-ebooks/big-data-analytics-hadoop-3 on line 1487 is unreachable.
Error: https://www.packtpub.com/free-ebooks/mastering-ros-robotics-programming-second-edition on line 655 is unreachable.
Error: https://www.packtpub.com/free-ebooks/serverless-design-patterns-and-best-practices on line 860 is unreachable.
Error: https://www.packtpub.com/free-ebooks/mastering-xamarin-ui-development-second-edition on line 1129 is unreachable.
Error: https://www.packtpub.com/free-ebooks/python-machine-learning-example on line 2437 is unreachable.
Error: https://www.packtpub.com/free-ebooks/building-applications-spring-5-and-vuejs-2 on line 1673 is unreachable.
Error: https://www.packtpub.com/free-ebooks/kali-linux-2018-assuring-security-penetration-testing-fourth-edition on line 1963 is unreachable.
Error: https://www.packtpub.com/free-ebooks/django-restful-web-services on line 2473 is unreachable.
Error: https://www.packtpub.com/free-ebooks/sql-server-2017-administrators-guide on line 2788 is unreachable.
Error: https://www.packtpub.com/free-ebooks/mastering-internet-things on line 1596 is unreachable.
Error: https://www.packtpub.com/free-ebooks/learn-python-programming-second-edition on line 2405 is unreachable.
Error: https://www.packtpub.com/free-ebooks/blockchain-example on line 616 is unreachable.
Error: https://www.packtpub.com/free-ebooks/expert-delphi on line 1275 is unreachable.
Error: https://www.packtpub.com/free-ebooks/software-architecture-spring-50 on line 1674 is unreachable.
Error: https://www.packtpub.com/free-ebooks/learn-powershell-core-60 on line 2311 is unreachable.
Error: https://www.packtpub.com/free-ebooks/splunk-7x-quick-start-guide on line 2760 is unreachable.

I tried 3 of the links. one (a packt) book, was dead. We should probably remove the packt links. another - a gatech link, was https but should be http. The github objcguide like worked fine.
Are you looking at the link checker we run as a github action?
Bad links should be removed; it's tedious to check all of them, and we very much appreciate the PRs.

I tried 3 of the links. one (a packt) book, was dead. We should probably remove the packt links. another - a gatech link, was https but should be http. The github objcguide like worked fine.
Are you looking at the link checker we run as a github action?
Bad links should be removed; it's tedious to check all of them, and we very much appreciate the PRs.

I used local extension on my Visual Studio Code, well, I just thought pasting them here if someone want to help 👍

5 days ago, the link-checking action found only 6 problems (I think it ignores some problems due to common false failure):

[L0449]  http://people.cs.aau.dk/~csj/Thesis/ Net::ReadTimeout
[L0462] 503 http://schoolofdata.org/handbook/
[L0567] 404 http://home.iitk.ac.in/~arlal/book/la.pdf
[L0842] 403 https://msdn.microsoft.com/en-us/library/jj554200.aspx
[L1187] 404 http://daly.axiom-developer.org/clojure.pdf
[L2238] 404 http://phpsec.org/projects/guide/

only #3 appears in your list!

I clicked the link & i founds these links are not reachable,

Specially related to this website https://www.packtpub.com

Its not loading anyting.

Error: https://www.packtpub.com/free-ebooks/hands-cloud-administration-azure on line 384 is unreachable.
Error: https://www.packtpub.com/free-ebooks/artificial-intelligence-big-data on line 367 is unreachable.
Error: https://www.packtpub.com/free-ebooks/docker-cookbook-second-edition on line 436 is unreachable.
Error: https://www.packtpub.com/free-ebooks/full-stack-react-projects on line 1868 is unreachable.
Error: https://www.packtpub.com/free-ebooks/effective-devops-aws-second-edition on line 630 is unreachable.
Error: https://www.packtpub.com/free-ebooks/java-projects-second-edition on line 1640 is unreachable.
Error: https://www.packtpub.com/free-ebooks/industrial-cybersecurity on line 645 is unreachable.
Error: https://www.packtpub.com/free-ebooks/kubernetes-cookbook-second-edition on line 438 is unreachable.
Error: https://www.packtpub.com/free-ebooks/mastering-opencv-4-third-edition on line 430 is unreachable.
Error: https://www.packtpub.com/free-ebooks/big-data-analytics-hadoop-3 on line 1487 is unreachable.
Error: https://www.packtpub.com/free-ebooks/mastering-ros-robotics-programming-second-edition on line 655 is unreachable.
Error: https://www.packtpub.com/free-ebooks/serverless-design-patterns-and-best-practices on line 860 is unreachable.
Error: https://www.packtpub.com/free-ebooks/mastering-xamarin-ui-development-second-edition on line 1129 is unreachable.
Error: https://www.packtpub.com/free-ebooks/python-machine-learning-example on line 2437 is unreachable.
Error: https://www.packtpub.com/free-ebooks/building-applications-spring-5-and-vuejs-2 on line 1673 is unreachable.
Error: https://www.packtpub.com/free-ebooks/kali-linux-2018-assuring-security-penetration-testing-fourth-edition on line 1963 is unreachable.
Error: https://www.packtpub.com/free-ebooks/django-restful-web-services on line 2473 is unreachable.
Error: https://www.packtpub.com/free-ebooks/sql-server-2017-administrators-guide on line 2788 is unreachable.
Error: https://www.packtpub.com/free-ebooks/mastering-internet-things on line 1596 is unreachable.
Error: https://www.packtpub.com/free-ebooks/learn-python-programming-second-edition on line 2405 is unreachable.
Error: https://www.packtpub.com/free-ebooks/blockchain-example on line 616 is unreachable.
Error: https://www.packtpub.com/free-ebooks/expert-delphi on line 1275 is unreachable.
Error: https://www.packtpub.com/free-ebooks/software-architecture-spring-50 on line 1674 is unreachable.
Error: https://www.packtpub.com/free-ebooks/learn-powershell-core-60 on line 2311 is unreachable.
Error: https://www.packtpub.com/free-ebooks/splunk-7x-quick-start-guide on line 2760 is unreachable.

I clicked the link & i founds these links are not reachable,

Specially related to this website https://www.packtpub.com

Its not loading anyting.

Error: https://www.packtpub.com/free-ebooks/hands-cloud-administration-azure on line 384 is unreachable.
Error: https://www.packtpub.com/free-ebooks/artificial-intelligence-big-data on line 367 is unreachable.
Error: https://www.packtpub.com/free-ebooks/docker-cookbook-second-edition on line 436 is unreachable.
Error: https://www.packtpub.com/free-ebooks/full-stack-react-projects on line 1868 is unreachable.
Error: https://www.packtpub.com/free-ebooks/effective-devops-aws-second-edition on line 630 is unreachable.
Error: https://www.packtpub.com/free-ebooks/java-projects-second-edition on line 1640 is unreachable.
Error: https://www.packtpub.com/free-ebooks/industrial-cybersecurity on line 645 is unreachable.
Error: https://www.packtpub.com/free-ebooks/kubernetes-cookbook-second-edition on line 438 is unreachable.
Error: https://www.packtpub.com/free-ebooks/mastering-opencv-4-third-edition on line 430 is unreachable.
Error: https://www.packtpub.com/free-ebooks/big-data-analytics-hadoop-3 on line 1487 is unreachable.
Error: https://www.packtpub.com/free-ebooks/mastering-ros-robotics-programming-second-edition on line 655 is unreachable.
Error: https://www.packtpub.com/free-ebooks/serverless-design-patterns-and-best-practices on line 860 is unreachable.
Error: https://www.packtpub.com/free-ebooks/mastering-xamarin-ui-development-second-edition on line 1129 is unreachable.
Error: https://www.packtpub.com/free-ebooks/python-machine-learning-example on line 2437 is unreachable.
Error: https://www.packtpub.com/free-ebooks/building-applications-spring-5-and-vuejs-2 on line 1673 is unreachable.
Error: https://www.packtpub.com/free-ebooks/kali-linux-2018-assuring-security-penetration-testing-fourth-edition on line 1963 is unreachable.
Error: https://www.packtpub.com/free-ebooks/django-restful-web-services on line 2473 is unreachable.
Error: https://www.packtpub.com/free-ebooks/sql-server-2017-administrators-guide on line 2788 is unreachable.
Error: https://www.packtpub.com/free-ebooks/mastering-internet-things on line 1596 is unreachable.
Error: https://www.packtpub.com/free-ebooks/learn-python-programming-second-edition on line 2405 is unreachable.
Error: https://www.packtpub.com/free-ebooks/blockchain-example on line 616 is unreachable.
Error: https://www.packtpub.com/free-ebooks/expert-delphi on line 1275 is unreachable.
Error: https://www.packtpub.com/free-ebooks/software-architecture-spring-50 on line 1674 is unreachable.
Error: https://www.packtpub.com/free-ebooks/learn-powershell-core-60 on line 2311 is unreachable.
Error: https://www.packtpub.com/free-ebooks/splunk-7x-quick-start-guide on line 2760 is unreachable.

yep, they're still dead. Time to delete these packtpub links.

yep, they're still dead. Time to delete these packtpub links.

Seems that some of them, probably all but didn't check each one, have just shifted from /free-ebooks to /products.
for example
https://www.packtpub.com/free-ebooks/hands-cloud-administration-azure
redirects to
https://www.packtpub.com/free-ebooks/virtualization-and-cloud/hands-cloud-administration-azure/9781789134964
which is no longer free and has been moved to
https://www.packtpub.com/product/hands-on-cloud-administration-in-azure/9781789134964
They still aren't free, so should still be removed. Just wanted to note on this issue that the resources haven't been removed, but they were previously free resources that just had a price put on them.

Seems that some of them, probably all but didn't check each one, have just shifted from /free-ebooks to /products.
for example
https://www.packtpub.com/free-ebooks/hands-cloud-administration-azure
redirects to
https://www.packtpub.com/free-ebooks/virtualization-and-cloud/hands-cloud-administration-azure/9781789134964
which is no longer free and has been moved to
https://www.packtpub.com/product/hands-on-cloud-administration-in-azure/9781789134964
They still aren't free, so should still be removed. Just wanted to note on this issue that the resources haven't been removed, but they were previously free resources that just had a price put on them.


AsciiDoc Cleanup Command

One of these days, I'll write a command to automatically clean up my ADOC files. I'll certainly make it available on demand with a key map, but I'll probably also add the option to have it run every time you save.

Enforce an exact number of consecutive blank lines above each heading (zero above the title, three above all others, except if a header immediately precedes a sub-header, then just one). Also, if there are attributes or comments just above the heading line, then the spacing goes above those. -- Actually I'll have it first scan to see what the deepest heading level used is (say, ====), then ==== lines would only be preceded by one blank line, while == and === would get 3 blank lines.
Remove trailing spaces
Add [] after http links that don't already have them
Reformat tables so that the delimiters align -- unless any one line is longer than 80(?), 120(?), then leave the whole table alone.
Convert old-style typographical curly quotes to new syntax.
What else?

That's an interesting idea, but also consider that different people have different styling and formatting preferences when it comes to AsciiDoc.

Remove trailing spaces

That's already achievable via ST syntax-specific settings, and also via EditorConfig.

Reformat tables so that the delimiters align -- unless any one line is longer than 80(?), 120(?), then leave the whole table alone.

That's tricky, since users' can specify an alternative delimiter (e.g. in nested tables), and because of the need to check out for nested tables (which would break this type of alignment), not to mention cells and raw spanning. Also, how are you going to deal with CSVs and other types of tables? the command script would have to be very careful in detecting the right type of table, e.g. by determining the exact number of columns specified, and the absence of cells' or rows' spans.
I believe this is going to be hard to achieve without a full-fledged parser, except for very simple and predictable tables.
Many people simply write one column per line, even with short cell contents.

Convert old-style typographical curly quotes to new syntax.

Not sure what you mean here.

What else?

Definitely: splitting paragraphs one-line-per sentence! I do this via a custom RegEx when I start working on converted documents, by always supervise each match and replace, for there are always edge cases even when considering question marks and exclamation marks.
Other useful functionality would be in the area of handling footnotes and their definitions; applying consistent formatting of same constructs which allow syntactic variations, etc. (basically, a linter).

Definitely: splitting paragraphs one-line-per sentence!

Guess what? I already have such code in a BASH script. I totally forgot about that. Give me a day to convert it to Python. I'll add it to the command palette as "AsciiDoc: Clean Up Converted Prose"

Other useful functionality would be in the area of handling footnotes and their definitions

What about them?

applying consistent formatting of same constructs which allow syntactic variations, etc. (basically, a linter).

I can do that. Why don't you start a new issue with some specifics? Start with how you would add it to the command palette. (My suggestions would be: "AsciiDoc: Standardize Syntax" -- assuming I understand you correctly.)

Other useful functionality would be in the area of handling footnotes and their definitions

What about them?

E.g. converting inline footnotes to externalized footnotes. I personally find this method very useful in books with many footnotes for it keeps the inline notation shorter and place all footnotes definitions at the top of the document.
:fn1: footnote:[Some note.]

Some text.{fn1}

Other possible functionality would be to process all footnotes and assign them an auto-generated target ID, e.g. with progressive numbering (replacing any previous target ID found).

footnote:[First note.] → footnote:fn1[First note.]
footnote:old_id[Second note.] → footnote:fn2[Second note.]

Again, enforcing a consistent formatting, notation and/or methodology.

Why don't you start a new issue with some specifics? Start with how you would add it to the command palette.

I don't really have any specifics in mind, and probably the suggested way to go about it proposed by the contributor is most likely to be better than any suggestion from my side, since the former would be the result of practical needs based on day to day experience.

(My suggestions would be: "AsciiDoc: Standardize Syntax" -- assuming I understand you correctly.)

I would personally suggest creating many individual functions, which end users are then free to either use one after the other, or to group into custom single commands they create on a per need base. The problem is that there isn't a standard syntax when it comes to AsciiDoc, there are multiple choices instead, and personal approaches.
When it comes to creating an AsciiDoc linter, I think the best approach would be to create a dedicated linter for an already existing linter package, like SublimeLinter, rather than include it in this package:

https://github.com/SublimeLinter/SublimeLinter
http://www.sublimelinter.com/en/stable/

I'm convinced that it's very hard to handle the AsciiDoc syntax without a proper parser that creates an AST, and I think that the only viable solution would be to create a Language Server package for AsciiDoc, which would not only be portable across all editors that support LSP, but also allow tailoring all sorts of functionality into the package as well (linting, refactoring, etc.).
But that would be quite hard to achieve, for such an LSP package would have to be fast enough to allow real-time highlighting while editing, and also be a "fault tolerant" parser which can recover from incomplete constructs without breaking the whole document (which is the main problem with the current ST package, which often breaks up mid-document and is unable to properly highlight and index the rest of the doc).

OK guys, check out pull request #14. Start by reading FIXUP_CONVERTED.adoc. How'd I do?

E.g. converting inline footnotes to externalized footnotes.

I added issue #15 for this.

process all footnotes and assign them an auto-generated target ID

Would that be in addition to the externalized method, or instead of? I think the externalized method is perfectly elegant.

I would personally suggest creating many individual functions

OK. I see that. I went ahead and batched up 20 operations in the one FIXUP_CONVERTED command because they really go together and it's a one-and-done. But going forward, I agree with the individualized approach.

When it comes to creating an AsciiDoc linter, ...

All good points. I'm moving your comments on this to its own issue for further discussion after we close this one.

What if the linter only promised to handle a small subset of AsciiDoc? -- i.e. it justs looks for the most common lint.

I think that this would be a good idea, also more realistic to achieve than a "full linter" (i.e. claiming to cover every possible AsciiDoc construct and context).

I've been thinking of putting forth the notion of establishing an "AsciiDoc-Lite" standard.

That could be beneficial and, as long as its goals are clearly stated to be an "opinionanted standard" for practical use, which doesn't claim to be official nor an alternative to the AsciiDoc standard efforts. Probably calling it a convention rather than a standard would be better (or wiser) — I'm sure that such a project, or calling it "AsciiDoc standard" would rise criticism, just like it happens whenever you mention terms like "GitHub-Flavored AsciiDoc".
You could start a repository proposing a draft for this convention, so that AsciiDoc users might join the discussion with their proposals and needs, in order to find out what minimum coverage of the syntax would be considered useful, how it would play out nicely with all available AsciiDoc implementations, etc.

I'm convinced that less than 5% of AsciiDoc notation handles more than 95% of the use cases out there.

That's a good estimate IMO.

Having such a known-quantity specification could make life easier on everyone (developers and users).

I'm not sure about "everybody", since some authors (especially old timers coming from Emacs and Vim) tend to our their own strongly established traditions when it comes to formatting (e.g. ALWAYS two spaces separating sentences on a same line, etc.), and because opinionated choices are unlikely to make everyone happy (e.g. should the "one-sentence-per-line" rule also apply to list items? to a sentences like "Sentence. E.g.", and so on).
But it is in an interesting challenge, especially when it comes to non-English documentation, since other locales have their own formatting needs (which were not always taken into account during AsciiDoc general design).


broken url from documentation website to this repo

Describe the bug
ALL of the urls on [https://docs.dolby.io/communications-apis/docs/](this page) under the section Project Sample Apps are broken. It seems to me as if the [https://dolby.io/project-gallery/](Project Gallery) page has been undergoing a big change and all of the old urls (for all of the sdks) don't work any more. Frustrating...

Thanks @alpalex for reporting this, we're looking at it.

We've temporarily removed the links, all of our sample apps are on GitHub.


Create AI copilot tools

Related to #646.
For example, tools to generate titles for working notes cards, this prompt works well:
Here is a short essay: "${CONTENT}".

Append a good, punchy summary in 35 characters or less with no other text or quotation marks.

Another could be to fetch a collection of related working-notes cards and then ask for a summary in 8 sentences or less.
The tools would need to go through a cloud function that kept the OpenAI private key and verified the user was an admin to prevent abuse of the key.

[ ]   A plain_content property on cards that's a concatenation of non-derived title, subtitle, body (with any html fields stripped) (Maintenance task to set it up)
[ ] An end point that takes card chunks, verifies the uid is an admin or edit_cards access, and an enum of different query types (e.g. generate_title, create_card_body)

Being developed in branch ai-tools

71967cbd4b607a8e03276e38e81d7078928a6034 is also a part of this ticket


pull changes from nvim-lua/kickstart.nvim main

No need for this pull request, managed to resolve this on machine.


cffi headers: respect $CC if defined

default behavior is unchanged, but fixes builds on e.g. conda where compilers have funky names (https://github.com/conda-forge/vic-feedstock/pull/4) or gcc is not what should be used.

[ ] closes #xxx
[ ] tests passed
[ ] new tests added
[ ] science test figures
[ ] ran uncrustify prior to final commit
[ ] ReleaseNotes entry

I ran uncrustify but didn't commit the changes because it changed a bunch of C files that aren't related to this PR. There isn't a release notes section for the next unreleased version, so I didn't feel ready to start one with such a minor fix.

Thanks @minrk - I'll take it from here. I'm really impressed by your persistence on this one. I'm guessing you aren't a user of the VIC model? Your efforts on conda-forge (and beyond) are much appreciated.

I'm guessing you aren't a user of the VIC model?

I'm not, this is with my conda-forge mpi maintainer hat on. I'm learning how to build and install lots of tools I don't use!


Cycle through & search for patients

Right now, one cannot look at the next or the previous patient when in the detail view. Also, it's not possible to display a subset of the dataset in a list (e.g. the one that was selected in the dashboard).

The solution could be HTML5 form attribute of <input> elements. See here for an explanation.


[Research] Create or process ESR codes with > 1 hour expiry

Describe the bug
There's some limit in ESR where we can't create transactions more than 1h in the future for expiry.
Figure out what that limit is all about
1 - Create QR code that expires 1 day from now
2 - Experiment with changing the expiry date inside the wallet, before firing off the transaction - this should be easy?!
3 - Talk to greymass team / Telegram ESR chat about this limit - it might be an EOSIO limit.

For real-world merchants (bricks & mortar, farmers market vendors) who want to use printed QR codes as price stickers, long-term validity is important.


Checkboxes and radio buttons do not render correctly with<EMAIL_ADDRESS>

Upon upgrading to PrimeVue version 3.47.2, I observed a rendering issue with checkboxes and radio buttons. Specifically, these components do not seem to apply their respective Tailwind presets correctly.
The issue is consistent across versions 3.47.0, 3.47.1 and 3.47.2.
This behavior was not present in version 3.46.0, suggesting that the issue may be a regression introduced in subsequent updates.
Here are some comparative screenshots of the Checkbox component:
Before:

After:

I am having the same issue and was sure I was doing something wrong (weather I change the preset to suit me or use the original as is)

I have looked at the diff between v3.46.0 and 3.47.0 and it seems there was quite a bit of refactoring, and also adding a ref to the box div, and also changing the methods, such as onClick to onChange as well as updating vmodel in the components/lib/checkbox/Checkbox.vue file. Unfortunately I don't have much time to investigate, so for now I went back to v3.46.0. But I think this might need to be opened in the main primevue repo

Hi, yes, with the last update, there have been changes to the checkbox & radio button structures in PrimeVue Core. I am currently working on this, and we will have a quick release for these changes.

@atakantepe no problem, and thank you. I reverted to 3.46.0 for now, as luckily for me my project is not in production yet :)

Fixed with https://github.com/primefaces/primevue-tailwind/issues/89. I will release this fix today👍


nimble/host: Add API to allow given address from whitelist

This patch adds a  API which allows host to remove a given address from whitelist.
Current existing APIs clear complete whitelist. This API provides flexibility to application to manage whitelist address by deleting a particular address from whitelist.

Existing API allows to set complete whitelist which means app manages whitelist contents on its own (add/remove/clear/whatever) and then calls that API to set whitelist. There's no need to have separate add/remove/clear API in such design and I'm reluctant to add new APIs which are redundant.
In any case, the name of API is incorrect (should be ble_gap_wl_remove) and there should be also add and clear APIs, if we decide to add it anyway.

@andrzej-kaczmarek  , ok . Thanks for explaining the architecture design. Closing the PR


Use refresh tokens

Store refresh tokens in ~/.force/accounts/<account>, and automatically refresh the access token when the http methods get a 401 response instead of requiring the user to re-authenticate using force login.
In order to get a refresh token, we need to either:

switch to web server flow and store the client secret locally. Each user should then create their own Connected App.
use a fixed port in startLocalHttpServer, instead of passing the port in state, and configure the callback URL to redirect directly back to localhost.  We'll need to move the javascript running on https://force-cli.herokuapp.com, which extracts the parameters in the fragment and redirects with them in the query string, to the local webserver.

This was added in #348, and included in v0.22.61.


Two culling calls when using monoscopic rendering mode.

When using monoscopic rendering, "OVRMonoscopicViewManager" calls "beforeDrawEyes()" from "onDrawFrame()". Since this class extends from "OVRViewManager"  and it is not overriding this method , the "beforeDrawEyes()" of the "OVRViewManager" gets called, where culling takes place.  It appears as if the removed culling call in this commit is redundant because is actually causing a second cull pass to happen.

Looks correct to me. I traced through the code and it calls GVRViewManager.beforeDrawEyes which calls cull() - the native function Java_org_gearvrf_GVRViewManager_cull. The monoscopic version of cull() calls Java_org_gearvrf_OvrNativeMonoscopicRenderer_cull. Both of these native functions do exactly the same thing.

Then the OvrMonoscopicRenderer.cull and Java_org_gearvrf_OvrNativeMonoscopicRenderer_cull should be removed too.


add KyudoScoreBook

Hi! @yshrsmz
Thanks for this beautiful library.
Used in my app　KyudoScoreBook.
Released it at google play.

many thanks! 🍻


db-link: Property current is not updated after changes

The property current is not updated when there are changes.
Reproducer

yarn create react-app my-app --template typescript
yarn add @db-ui/react-elements-enterprise
Follow the Get started with React
Add the following code to you App.tsx

// App.tsx
import<EMAIL_ADDRESS>import {DbFooter, DbHeader, DbLink, DbMainnavigation, DbPage} from "@db-ui/react-elements-enterprise";
import {useState} from "react";

function App() {
    const [active, setActive] = useState(true);

    return (
        <>
            <DbPage>
                <DbHeader slot="header">
                    <button onClick={() => setActive(!active)}>Toggle</button>
                    <DbMainnavigation>
                        <DbLink href="/" key="key1" current={active ? "page" : "false"}>First</DbLink>
                        <DbLink href="/whatever" key="key2" current={active ? "false" : "page"}>Second</DbLink>
                    </DbMainnavigation>
                    <div/>
                </DbHeader>
                <DbFooter slot="footer" copyright border/>
            </DbPage>
        </>
    );
}

export default App;

yarn start
Press the button Toggle

Expected behaviour
The active page should toggle between "First" and "Second"

Seems related: https://github.com/db-ui/elements/issues/394#issuecomment-1286726697

Issue is reproducible.
Culprit seem to be the componentWillLoad() lifecycle method of <DbMainnavigation>, which will not trigger a re-render of "children" upon a change.  <DbLink> works as expected when not being wrapped by <DbMainnavigation>


Indent guide is crazy in XML files

Reopening https://github.com/atom/language-xml/issues/42 in the right place.
See this pic and you will understand what I mean:

Atom 1.3.2. Fedora 23. No Emmet plugin installed. Issue happens with atom --safe.

I suspect that this is the same issue as #9369.  @Yajo can you please try increasing/decreasing the font size to see if the problem fixes itself at a certain font size?  If so then it's probably a duplicate of #9369.

Thanks, I tried. No matter the zoom, the lines stay the same.


Very low mIOU

I am training this model on VOC2012 dataset. But the mIOU value I'm getting is very less(0.07).What could be the possible reasons?

@vinaysingh5898 Hi, could you train on Cityscapes and tell me if you have the same issue?

@NoamRosenberg  Sure. How much time did it take for training on Cityscapes? What is the best mIOU value you got?

@vinaysingh5898 ** sorry for the delayed response. I've been traveling these last two weeks with very little internet access.
As per your question, last time I trained on CityScapes I got a 73.16% mIOU after training for several days on a very sluggish P14 GPU. Since then I've optimized the model a bit on my own data-set and I hope you should achieve better results with Cityscapes.  @vinaysingh5898 Have you trained on Cityscapes yet? Do you have any results?

@vinaysingh5898 Do you have any results yet? Would you like to work with me and contribute to the project?

I will publish that information soon, @vinaysingh5898 Do you have any results yet? Would you like to work with me and contribute to the project?

Could you please report the searched network performance on Cityscapes?

@DianaLi96 Due to some recent adjustments in the code. I plan on publishing the results along with a lot of other training data on cityscapes by end of next week.

@DianaLi96 Due to some recent adjustments in the code. I plan on publishing the results along with a lot of other data about training on cityscapes by end of next week. Please stay tuned.

ok，thanks for your reply.

@DianaLi96 we're currently testing out a smaller version of the model, i.e. image input size 224 instead of 321  and filter_multiplier 4 instead of 8 like in the paper. Do you by any chance have the resources to assist in testing at the original size of the paper?

@DianaLi96 we're currently testing out a smaller version of the model, i.e. image input size 224 instead of 321 and filter_multiplier 4 instead of 8 like in the paper. I don't personally have enough memory on my GPU, it looks like I'll need a GPU with 60GB memory. Do you by any chance have the resources to assist in testing at the original size of the paper?

Do you mean you need a single gpu with 60GB memory? Actually we have tesla p100 gpus. I am not sure i could help you test the performance. And what is the gpu type you are using?

@DianaLi96 I currently have 5 p40's at my disposal. And yes a p100 is excellent, it's exactly what the authors use.
If you'd be interested in contributing or assisting with some aspects, even some basics like testing, I would greatly appreciate it.
I wonder if you could contact me via email, hangouts or wechat and we could communicate about this further?
email/hangouts: noamsrosenberg
wechat: BuffaloNoam


Speakers: Implement thought through sorting, info, photo and other features

[ ] Standard sorting of speaker should be alphabetically. Currently I do not understand what is the sorting.
[ ] Photo missing in detail view of speakers
[ ] No links and social channels are given
[ ] Link to organization missing in all views
[ ] Sessions of the speaker missing
[ ] No sharing of social media links
[ ] Speakers overview starts with a comma

Compare with RP for example:

https://re-publica.de/member/1004#profile-speaker

sorting is implemented via pull req https://github.com/fossasia/open-event-webapp/pull/65

details of speaker in speaker dialog being added here https://github.com/fossasia/open-event-webapp/pull/69

I would really like to work on implementing these features.

almost all the things have been updated here #111 .Only speaker sessions is left.

@mariobehling Please have a look at this PR - https://github.com/fossasia/open-event-webapp/pull/130 . Please suggest in case if any other changes are required. Thanks. :smile:


Add new componente: Dropdown

Proposal for new Dropdown component, to be used when interacting with inputs such as Select and Multiselect.
You can find the documentation :

directly on Figma, where the component lies
on Confluence

BRUH

Implementation checklist:

[ ]: basic implementation of items with desired formatting
[ ]: cascading options
[ ]: customizable heading and footer
[ ]: search
[ ]: icon support