default shortcuts and autocomplete disabled after ActualVim

After i installed actualvim, the shortcuts are not working anymore, e.g. Ctrl+b for build. The autocomplete and the auto closing brackets functions are also missing. Is that something i did wrong or is it the way ActualVim works? thx

overlaps these issues:
https://github.com/lunixbochs/ActualVim/issues/105 (key mapping)
https://github.com/lunixbochs/ActualVim/issues/94 (snippets)
https://github.com/lunixbochs/ActualVim/issues/97 (possible fix)
https://github.com/lunixbochs/ActualVim/issues/57 (auto completion)

thx so much for the detailed reply, I really appreciate it. But can you elaborate more about the key mapping? I have read the issues already.
{ "keys": ["ctrl+s"], "context": [{"key": "setting.actual_mode", "operand": true}],  "command": "actual_disable"},
{ "keys": ["ctrl+s"], "context": [{"key": "setting.actual_mode", "operand": false}], "command": "actual_enable"},
so if i press ctrl+s in sublime, it will diable vim and enable all sublime original keymaps?

That's the idea, yes. You can also use "Disable ActualVim" from the command palette.

You can bypass some keyboard shortcuts per mode in the 0.9.12 release coming out soon.
Basically set settings.vim.modes.normal.av:ctrl+b to true in one of the modes in ActualVim settings:
    "settings": {
        "vim": {
            "modes": {
                "normal": {
                    "av:ctrl+b": true,
                },
            }
        }
    }```

With key mapping fixed, I'm closing this as a duplicate of #97


.travis.yml: Initial travis configuration

Build with gcc, clang on glibc and gcc on musl libc via musl-gcc
wrapper
Execute tests

To the rest of the team -- do not merge this for now, but keep it open. I need to figure out whether travis is accessible to me or not.

I have opened https://bugs.gentoo.org/show_bug.cgi?id=621628 to inquire about stabilizing the Travis commandline client. I will follow that bug and look at this more once that is stabilized.

@williamh Is there still interest in this change?

Yes there is, I just haven't  looked at it much yet. On another note, I'm thinking about unit testing, I'm just not sure how to do that with OpenRC yet either.


Inserted lines for metalinks

Inserted lines for metalinks in params.pp and init.pp. Having these lines present will enable us to choose an absent value over an external metalink.

This is superseded by #82 which has been merged.


Add a check for SPDX license

Ensure that license tag is syntactically correct SPDX license expression and that each license is approved by Fedora.

The check has been added to https://src.fedoraproject.org/tests/javapackages/blob/main/f/runit/LicenseCheck.java


[BUG ] No requests working

Valorina returns the error
"Something went wrong :("
"Please try again"
When requesting any command such as store, balance etc. This is happening to all users in two of my servers and has been happening for a few days now.
Hope you can get it working again, this bot is very useful and I am very thankful for the work you have done creating it :)

Hey @ItsFilko This is fixed now


Rid of 'Made by Vermonster'

Code for Raleigh should represent!  Replace the logo/text in the footer.

Agreed. The license is MIT so we're good with doing.


When attachment loader is at 100%, set the value to null

This is so the progress goes from 100 to the infinitely spinning wheel. In my opinion, better UX than waiting for the progress bar, sitting at 100% for 10 seconds while a large video loads

My Branch


Cache any pre-computed steps

Describe the feature you'd like to request
This is going to take a bit more thought, but we might want to cache some pre-computation, to reduce the load on render.
As a naive strawman, we should check if we can run queries that group by date.
If not, should we pre-compute that?
Probably we want to wait on this till after
https://github.com/hypercerts-org/os-observer/issues/59
Describe the solution you'd like
TBD
Describe alternatives you've considered
TBD

TimescaleDB does pre-compute, let's try that

Timescale continuous aggregates does this for us
https://github.com/opensource-observer/oso/pull/258


API review for Messaging modules

Parent issue: #24356

[ ] Messaging modules: @yiliuTo https://github.com/Azure/azure-sdk-for-java/pull/25969
[ ] Integration modules: @hui1110 https://github.com/Azure/azure-sdk-for-java/pull/25939
[ ] Stream modules:  @hui1110 https://github.com/Azure/azure-sdk-for-java/pull/25971

Closing in favor of https://github.com/Azure/azure-sdk-for-java/issues/27112.


don't prune unnecessarily

In some cases, numpy.array slicing causes copies that can be avoided.

Slicing never produces copies. Can you give more details on the case that is problematic?

Here a simple testcase :
>>> import numpy as np
>>> from array import array
>>> a1 = np.arange(0, 100, 1)
>>> a1[:15].base is a1
True
>>> a_ = array('d', range(100))
>>> a2 = np.frombuffer(a_, dtype=a_.typecode)
>>> a2.base is a_
True
>>> a2[:15].base is a_
False

I wrote a Cython wrapper to load sparse matrices from libsvm files, and I want to avoid copies as much as possible.

Perhaps there's some way we can detect the cases in which slicing will trigger a copy, like checking for the OWNDATA flag? Or maybe it doesn't matter, and we can just add the test proposed in this PR.

According to documentation :

All arrays generated by basic slicing are always views of the original array.

So I think @pv is right. I was wrong about what I thought that base was recursive, which is not.
This test works for me  :
from array import array
import numpy as np
from scipy.sparse import csr_matrix

def _base(obj):
    while getattr(obj, 'base', None) is not None:
        obj = obj.base
    return obj

data = array('f', [1.,2.,5.,3.,4.])
indices = array('i', [0, 2, 4, 1, 3])
indptr = array('i', [0, 3, 5])

X = csr_matrix((np.frombuffer(data, dtype=data.typecode),
                np.frombuffer(indices, dtype=indices.typecode),
                np.frombuffer(indptr, dtype=indptr.typecode)), copy=False)

assert _base(X.data) is data, 'data has changed'
assert _base(X.indices) is indices, 'indices has changed'
assert _base(X.indptr) is indptr, 'indptr has changed'

However, maybe there is another problem here : _prune_array may in some case make a copy even if the user specifies copy=False in the matrix constructor.

Ah, that makes sense. Pruning when constructed with copy=False is a separate problem, so I'll close this PR and open a new issue for it.


perf: use fragment caching

enable fragment cache for partials that are expected to be same across every page.

haven't test yet

Hi bro, thanks for your contribution. It seems you are updating many themes of Hexo, which makes great improving for Hexo ecosystem.


Implement a solenoid

Description
Implement a thick and a thin solenoid in Xsuite.
Checklist
Mandatory:

[x] I have added tests to cover my changes
[x] All the tests are passing, including my new ones
[x] I described my changes in this PR description

Optional:

[x] The code I wrote follows good style practices (see PEP 8 and PEP 20).
[ ] I have updated the docs in relation to my changes, if applicable
[ ] I have tested also GPU contexts

I recommend performing comparisons with small relativistic beta. A benchmark against mad-x is useful but I would not use it as a test.
You could add a test checking that a thick solenoid with zero field gives the same results of a drift for px!=py!=0.
Do you have a  write out of the equation you implemented? Do they agree with what is in paragraph 12.5.2 in https://inspirehep.net/literature/487284 ?

I can put in some tests for a small beta, I can also check if the solenoid behaves like a drift with zero field, although having it as a test is maybe not very strong, as the code explicitly catches that case and does a drift.
I have looked at the book, but in the end the code that is here (and in MAD-X) is not obviously the same as there. I could implement those equations and check for agreement there.

The check with zero fields can catch bugs. I expect the equations from the book and MAD-X (https://github.com/MethodicalAcceleratorDesign/MAD-X/pull/1129)  to implement the same solution as it is exact. Do you suspect they can be different?

For the thin solenoid, you can have a look at:
https://cds.cern.ch/record/281283/files/sl-95-012.pdf
eq. 3.37
which obtains a formulation under some approximations


Coding Challenge 98: Found error in the code.

There could be more than 4 dots (this.capacity) in one rectangle.
I analysed the code and understood it.
Here is the image.

The reason is this that when we subDivide we do not relocate the points of the block into its children blocks.
So, that is why if the block contains 4 points, its children could also have another 4 points. This makes that particular area to have 8 points or so on. This is really very important.
Let's see this in working:
I am adding points by my cursor, one by one.

The first four points added.Here no division took place as the size of 'points' array was smaller than capacity.

And then I added another point. :-

The division took place.
But the first four points are of the Big block and the fifth point is of one its children.
So now that child block can hold 3 more points, before another division.

Now it looks like the child is having 9 points. but remember first four are of this parent.
This is the issue. I fixed it in the third commit of #552 in java version of quadTree.
Thanks.

You were right. It crashed. What to do now??
StackOverflow error.

My suggestion is make a minimum size for the rectangle and any attempts to make the rectangle smaller result in that quad tree getting increased capacity
if (rectangle.l*rectangle.w<=0.25) then capacity = infinity
I say that because the code is supposed to deal with points right? and if the points are smaller than any arbitrary value you could treat them as all occupying the same space, in this case I specified half a pixel by half a pixel which might be needlessly precise but the strategy can be extended to be as precise as any task demands.

Please elaborate I cannot understand it.

Thanks, that's done.
you can view at https://github.com/AryanGitHub/Code/blob/master/Processing/CoadingTrainWork/CC_98_QuadTree_Part_2_in Different_way/CC_98_QuadTree_Part_2inDifferentWay/quadtree.pde


E2: Implement link/unlink functionality (fixes #1900)

Fixes #1900.

This is work-in-progress; Beta version, works good so far in my testing. (It is not finished yet, there will be more commits later a bit. I will edit this post later to include more info, another issue has higher priority than this feature PR.)

Looks fine. Just need to verify that it works

Looks fine. Just need to verify that it works

It worked in my tests, notice, this is unfinished, I'll do more commits here (a bit later).

Is this ready for review or are you adding to it still?

are you adding to it still

Still WIP.


Revoked as option field

Pull Request summary:
In vManage 20.6 revoked is absent.
Description of changes:
Changed revoked to option field
Checklist:

[x] Make sure to run pre-commit before commiting changes
[x] Make sure all checks have passed
[x] PR description is clear and comprehensive
[ ] Mentioned the issue that this PR solves (if applicable)
[x] Make sure you test the changes

This issue was migrated from an old repository: https://github.com/CiscoDevNet/catalystwan/pull/242


BoxLib 1.20.4 not working

I tried to install Coordinates Display, but evertime I install BoxLib 12.1.1 I get following error.
The only mods I have installed are BoxLib and Fabric API
Uncaught exception in thread "main"
java.lang.RuntimeException: Error creating Mixin config boxlib.mixins.json for mod boxlib
at net.fabricmc.loader.impl.launch.FabricMixinBootstrap.init(FabricMixinBootstrap.java:96)
at net.fabricmc.loader.impl.launch.knot.Knot.init(Knot.java:151)
at net.fabricmc.loader.impl.launch.knot.Knot.launch(Knot.java:68)
at net.fabricmc.loader.impl.launch.knot.KnotClient.main(KnotClient.java:23)
Caused by: org.spongepowered.asm.launch.MixinInitialisationError: Error initialising mixin config boxlib.mixins.json
at org.spongepowered.asm.mixin.transformer.Config.create(Config.java:153)
at org.spongepowered.asm.mixin.Mixins.createConfiguration(Mixins.java:100)
at org.spongepowered.asm.mixin.Mixins.addConfiguration(Mixins.java:87)
at net.fabricmc.loader.impl.launch.FabricMixinBootstrap.init(FabricMixinBootstrap.java:94)
... 3 more
Caused by: java.lang.IllegalArgumentException: The requested compatibility level JAVA_21 could not be set. Level is not supported by the active JRE or ASM version (Java 17.0, ASM 9.6 (ASM10_EXPERIMENTAL))
at org.spongepowered.asm.mixin.MixinEnvironment.setCompatibilityLevel(MixinEnvironment.java:1627)
at org.spongepowered.asm.mixin.transformer.MixinConfig.initCompatibilityLevel(MixinConfig.java:557)
at org.spongepowered.asm.mixin.transformer.MixinConfig.postInit(MixinConfig.java:502)
at org.spongepowered.asm.mixin.transformer.MixinConfig.onLoad(MixinConfig.java:430)
at org.spongepowered.asm.mixin.transformer.MixinConfig.create(MixinConfig.java:1293)
at org.spongepowered.asm.mixin.transformer.Config.create(Config.java:148)
... 6 more

The pre 1.20.6 versions of this mod need to be compiled with java 17 not 21

Ah thanks

This is an issue on the developers side, there's no reason to close.


Add sleep to nginx test to wait for container to start

Fixes:
Related:
Pre-review Checklist

[ ] IMPORTANT: 'image-request' tag has been applied if this PR is adding any images, including new versions or variants

For new image PRs only
If you have an apko.yaml file in this PR you need to follow this checklist, otherwise feel free to remove.

[ ] Image is marked experimental or stable as appropriate
[ ] The last two minor versions are available
[ ] The latest tag points to the newest stable version
[ ] There is a dev tag available that includes a shell and apk tools (by depending on 'wolfi-base')
[ ] The image runs as nonroot and GID/UID are set to 65532

[ ] Alternatively the username and GID/UID may be a commonly used one from the ecosystem e.g: postgres
[ ] See above for exceptions to nonroot rule

[ ] ENTRYPOINT

[ ] For applications/servers/utilities call main program with no arguments e.g. [redis-server]
[ ] For base images leave empty
[ ] For dev variants set to entrypoint script that falls back to system

[ ] CMD:

[ ] For server applications give arguments to start in daemon mode (may be empty)
[ ] For utilities/tooling bring up help e.g. –help
[ ] For base images with a shell, call it e.g. [/bin/sh]

[ ] Consider where and how the image deviates from popular alternatives. Is there a good reason and is it documented?
[ ] Add annotations e.g:

annotations:
  "org.opencontainers.image.authors": "Chainguard Team https://www.chainguard.dev/"
  "org.opencontainers.image.url": https://edu.chainguard.dev/chainguard/chainguard-images/reference/busybox/ # use the academy site here
  "org.opencontainers.image.source": https://github.com/chainguard-images/images/tree/main/images/bazel # use github here

[ ] Check if environment variables are needed e.g. to set data locations
[ ] Ensure the image responds to SIGTERM

[ ] docker kill $(docker run -d --rm cgr.dev/chainguard/nginx)

[ ] Documentation. Let's make this excellent. Include usage example.
[ ] Error logs write to stderr and normal logs to stdout. DO NOT write to file.
[ ] Include tests, at the very least a basic smoke test.

In general sleep is bad, better to have retry and backoff

In general sleep is bad, better to have retry and backoff

I agree - if it fails even ONE MORE TIME, then I will do so


502 Bad Gateway

I'm getting the bad gateway for Deis apps when using DNS configured access to the platform :
2016/05/06 15:05:14 [error] 25#0: *1706 connect() failed (111: Connection refused) while connecting to upstream, client: <IP_ADDRESS>, server: ~^helloworld\.(?<domain>.+)$, request: "GET /favicon.ico HTTP/1.1", upstream: "http://<IP_ADDRESS>:80/favicon.ico", host: "helloworld.linxos.net", referrer: "http://helloworld.linxos.net/"
[06/May/2016:15:05:14 +0000] - <IP_ADDRESS> - - - 502 - "GET /favicon.ico HTTP/1.1" - 328 - "http://helloworld.linxos.net/" - "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/601.5.17 (KHTML, like Gecko) Version/9.1 Safari/601.5.17" - "~^helloworld\x5C.(?<domain>.+)$" - <IP_ADDRESS>:80 - helloworld.linxos.net - 0.000 - 0.000
2016/05/06 15:05:16 [error] 25#0: *1704 connect() failed (111: Connection refused) while connecting to upstream, client: <IP_ADDRESS>, server: ~^helloworld\.(?<domain>.+)$, request: "GET / HTTP/1.1", upstream: "http://<IP_ADDRESS>:80/", host: "helloworld.linxos.net"

@rimusz that looks like it was caused by the upstream refusing the connection.  What happens if you ssh out to some node in the cluster and curl http://<IP_ADDRESS>?

I have the same issue on two GKE clusters

Same

Have either of you tried accessing the upstream service directly?

when the deis-builder.... came in? it was not the case last Saturday for beta3, all demos worked just fine.

The builder domain change does not affect how applications are routed. What @krancour is trying to explain is to manually bypass the router by checking the pod IP address and see if the application itself is routing properly. That would eliminate whether or not the router is the issue here.

already cleaned up my clusters, will do from the scratch and see what happens

Im seeing this issue on apps not deployed through deis but are configured to be routable (grafana for instance)

What @krancour is trying to explain is to manually bypass the router by checking the pod IP address

Or the service IP address.  Check both.

curl by pod IP works fine from the node:
$ curl <IP_ADDRESS>
Welcome to Deis!
See the documentation at http://docs.deis.io/ for more information.

@rimusz this is on GKE, right?  Can you please document exact steps to reproduce?

yup, GKE, usual GKE cluster and workflow install steps

What is needed beyond that?  Are you using the workflow-dev chart?  Is this happening only specific test apps?

beta 3, latest deis cli, our example apps  (example-dockerfile-http, helloworld) Dockefile/docker image get that issue, but the build pack one example-go works fine

Have you tried with the workflow-dev chart?

not yet

tried dev chart, controller is crashing there:
$ kd logs deis-controller-26oou
system information:
Django Version: 1.9.5
Python 3.5.1
Django checks:
System check identified no issues (2 silenced).
Health Checks:
Checking if database is alive
There was a problem connecting to the database

deleting the pod did not help

Have you look at if your DB is broken?

I am not able to reproduce this.  I've used GKE with the workflow-dev chart, and loaded up the cluster with:

10 apps deployed via git push of Dockerfile
10 apps deployed via deis pull
5 apps built with a buildpack

All 25 apps and Grafana were accessible every time I tried:
for i in $(deis apps | grep "^\w");do curl http://$i.krancour.deis.ninja; done

@jchauncey says he hasn't run into this in about a week now.
@rimusz are you still able to reproduce?  If so, I'd want to know how my attempt to reproduce differs from what you are doing.

@krancour I was able to reproduce it in Berlin yesterday on the last week created cluster from beta3 chart. Bootstrapped a new GKE cluster today and used dev chart and cannot reproduce the problem anymore.
It looks like it was the GKE problem.
I think we can close this one for now.

@rimusz i haven't tried using beta3.  It's possible also that if there was a bug, it may have been isolated to that release and fixed (inadvertently) in the meantime.  Thanks for following up.


universal-cookie TypeError;

code:
import Cookies from 'universal-cookie';
let cookie = Cookies();

This is how we should we should this, please check the documentation for more details.
import Cookies from 'universal-cookie';

let cookie = new Cookies();


is adding expect no call check reasonable?

Hi,
I have been used CppUTest in my daily CI for a long time, and the requirements pop out from time to time that I need to check one mock function is not invoked in some case. I would like devote some time to add this functionality, do you guys think it's valuable?

Hi there,
Actually, this check is standard. Perhaps a call to mock().checkExpectations() might be missing, if an unexpected call does not cause a failure.
Simply not specifying an expectation is sufficient.
In my own work, I sometimes use:
mock().expectNcalls(0, "Somefunction");

rather than a comment, to make explicit in my test case that this call is not supposed to occur. This is purely for the benefit of the reader; it is not necessary for an unexpected call to "Somefunction" to fail the test.

Hi there,
Actually, this check is standard. Perhaps a call to mock().checkExpectations() might be missing, if an unexpected call does not cause a failure.
Simply not specifying an expectation is sufficient.
In my own work, I sometimes use:
mock().expectNcalls(0, "Somefunction");

rather than a comment, to make explicit in my test case that this call is not supposed to occur. This is purely for the benefit of the reader; it is not necessary for an unexpected call to "Somefunction" to fail the test.

Hi arstrube,
I think sometimes it's necessary to fail the test if an unexpected call happens.
say, I have a decorator class, and also there is a delegation class inside that decorator.
decorator::functionA(Interface *pInterface)
{
    if (NULL == pInterface)
            return;
    //some decoration here
    .....
    //delegate call to delegation class
    delegator->functionA(pInterface);

    //may be some decoration also here
    .....
}

in my decorator class's unit test, I should have one NULL test to ensure that, if one exceptional NULL value is passed as the parameter, then the decorator will not call the delegator's functionA.
In this case, in the decorator mock class, if I use one expect no call,  when someone modify my codes and remove the guard clause for NULL by mistake, the NULL test will fail, this will help me to protect my decorator class always has correct behavior.
if i use expectNcalls with number 0, , NULL test will still pass but functionality of this decorator::functionA is break.

Sure, but my point is that your NULL test will fail, in that case. It should be simple for you to try out, no? E.g. remove the guard clause and see what happens.

You might include the expectation below for the benefit of the reader, but it is not even necessary to make the test fail:
mock().expectNcalls(0, "functionA"); // functionA() must not be called

I have a CI server which hold many many test cases from different component and different author in one software system, it is easy for me to try that out, but isn't easy for the automatic CI since it just run the test cases and report if pass or not. If one case pass even with problem, may be no one will find it until it bomb.

The only reason that I can possibly imagine (if at all) for an unexpected mock call NOT to fail a test is, if you don't call mock().checkExpectations() in teardown().
Now, if that's a concern with your many components and different authors, you might (if you are not already doing so) make use of the Mock Plugin, which will do this call for you and everybody else. There is no way an unexpected call wouldn't fail the test under those circumstances.
You still need to get everybody else to write the NULL test case consistently - no test case, no failure :P. By monitoring condition coverage, it should be easy though to spot offenders.
I'm not entirely sure I am answering your question, but in my world, tests do the same thing on our CI server that they do for me, and they work the same for 30 other colleagues than they do for me, if I couldn't  trust CppUTest for that it would be, well, kind of pointless....

P.S. In the project I work for, we use the same main() for all tests. Nobody has their 'own' main(). In this way, if we decide to use a plugin (such as the Mock Plugin), it is guaranteed that it is used by everyone.

@arstrube Unexpected calls fail immediately and will fail even if a call to mock().checkExpectations() is omitted.
@cuitoldfish Can you provide some code that shows that an unexpected call is not treated as a failure? I am not able to reproduce this issue, and it is unclear to me whether you have actually seen this happen or whether you are making guesses about the behavior of CppUTest simply by looking at the API.

Hi,
I mean, if I set
void teardown()
{
     mock().checkExpectations()
}

and
void setup()
{
    mock().ignoreOtherCalls()
}

then for following test
mock("delegator").expectNcalls(0, "functionA");

will always pass no matter the funcionA in delegator mock is invoked 0 times or more than 0 times.
I do not know if your guys actually had try and met this case, but at least in my case it is.

Why would you put ignoreOtherCalls in the setup?

Actually in my real unit test environment, there are still other unit tests existed, and I use ignoreOtherCalls to ensure that only the mock functions I care about are checked, rather check every mock function. In my example above, I am still checking the functionA while not check others what is specified to be ignored.
So is using both ignoreOtherCalls and expectNCalls with 0 at the same time unreasonable and should be deposed?

Ok.. uhm, well it is rather unusual to have "ignoreOtherCalls" but fail if these happen. It would suggest some serious trouble in your tests.
That said, when you do ExeptNCalls(0, "xx") with ignoreOtherCalls on, I would indeed expect that to fail, and if it doesn't, then it would be good to fix that.

I think "ignoreOtherCalls" should only ignore other mock call check, not to ignore the actual call whose check is specified as "ExeptNCalls(0, "xx"),  so your point of view is, this is a valuable finding and can be enhanced?

Yes

I will  try to do that.

@cuitoldfish Having seen your test code, I would try not to use ignoreOtherCalls() in the test case that should fail on the unexpected call to functionA(). Then you can be sure to receive a failure.

@basvodde When I saw the ignoreOtherCalls() I realized what the trouble is. I guess the semantics of ExpectNCalls(0, "xx") has never been defined or documented. As I mentioned above, I used it as a convenience for the reader.
Currently, I believe the semantics of  ignoreOtherCalls() is something like:
"Ignore each and every call beyond explicit expectations, no matter what, including additional calls to existing expectations". That is, if I expect 3 calls, and get 5, the remaining 2 will (and should) be ignored."
Given those semantics the current behavior of ExpectNCalls(0, "XX") is indeed correct, and a method like expectNoCalls("XX"), with the semantics that even in the presence of ignoreOtherCalls() a call to XX() would result in failure, is very desirable.

@basvodde I would go with the additional method; changing the behavior of expectNCalls(0, "XX") does not seem like a good idea to me. It could be messy and/or break existing test code.

If I would conceptually think about what exceptNCalls(0, "XX") would do, then I would assume that it wouldn't be ignored by ignoreOtherCalls.
I wouldn't recommend ever using it, I think it is bad test writing, but I do think it should behave properly when people do do that.

Not so sure. I would rather be penalized for bad test writing and have expectNoCalls() to let me write better tests in the future ;-).
Besides, if we have expectNoCalls(), there is really no reason to do exceptNCalls(0, "XX") and we can officially discourage the latter as bad test writing :)

How hard would it be to implement?

No so hard, I guess... but lets see. If it is too much changed, it wouldn't be good.

To me (up to now), using ignoreOtherCall() when wanting to assert the absence of a call, would have been bad test writing...
But actually, conceptionally, it should be possible and I can think of situations where it would be handy to do (actually not the NULL test example, because no other calls are supposed to happen after that at all anyway).
I have also felt the need to explicitly say in a test that I expect a call NOT to happen, short of using one of those hateful comments ;-)

Well, lets see. If we got the 0 case, it should be easy to add NotExpect.
Not sure we want that in the interface though :)

Why not?

Not know yet :) If we wouldn't recommend it, should it be in the interface?

Would you recommend
/* call to xyz() must not occur here */

rather?

No, if its not there, then why put a comment that its not there :)

/* The next line won't say: a = b + c; */

The whole point of the test case is, that the call should not occur.

The whole 0 case idea was mine, that we use in our project to document that fact. But I thought that is bad test writing :-(

/* The next line won't say: a = b + c; */
That's not a fair comparison; as far as the test is concerned, a mock() call happens (or doesn't happen) asynchronously.

That's why I want to say "I expect it not to happen".

Sure, but any other call is not expected to happen, so calling out one doesn't feel right to me :) But lets see after the implementation, we can decide to add it anyway.

agree with arstrube, add a new method "expectNoCall". I have implemented simple codes to change correct behavior of "expectNCalls(0, "")", but that must result in changed semantic of "ignoreOtherCall", which might easily break existed codes.
So leaving what's has already existed, and extend one new method seems best solution.

I agree, this should add a new function.
If someone is using a helper function with a parameter for call count, they may be calling expectNCalls(count, "func") where count = 0.  In that case, if ignoreOtherCalls() is set, then they may not be looking for no calls, they are instead just not looking for any calls.  It's a pretty specific corner case I know, but it's still something that I think is probably valid currently that would break if we treat 0 differently.  I generally assume that expectNCalls() is equivalent to calling expectOneCall N times, just less work/code because the function handles calling it the right number of times for me.

have a try in the pull request, let's review and see if it can be the resolver candidate

@basvodde and @arstrube ,what's your comments and proposal for my pull request?


Fix migration rollback issue

This issue is already fixed in branch 1.x by PR #3073. It still exists in branch 1.1

That was intentional as we consider it a breaking change (you would need to publish the updated migration after updating Voyager).


FR: Add support for Oprf RISTRETTO255_SHA512 in opaque.

https://github.com/cloudflare/voprf-ts seems to have evolved quite a bit since the last release that this code depends on. On new versions, r255 was added. This would make this library compatible (with serialization differences) with libopaque among others.
Please consider updating the oprf library version and thus enabling support for 255. Thanks!

Lately I'm working on updating the libraries. So this feature will land at a near point the future.


Carthage Build Error with Swift 5

[x] I've read, understood, and done my best to follow the *CONTRIBUTING guidelines.

What did you do?
I am migrating a custom NetworkFoundation that is based on Alamofire to Swift 5.
"carthage update" (to alamofire 5.0.0-beta.5)-> success
build in Xcode -> success
"carthage build --no-skip-current" -> error
What did you expect to happen?
The framework to build to then archive it with "carthage archive".
What happened instead?
*** Building scheme "Alamofire iOS" in Alamofire.xcworkspace
*** Building scheme "Alamofire macOS" in Alamofire.xcworkspace
*** Building scheme "Alamofire watchOS" in Alamofire.xcworkspace
*** Building scheme "Alamofire tvOS" in Alamofire.xcworkspace
*** Building scheme "MyNetworkFoundation" in MyNetworkFoundation.xcodeproj
*** Building scheme "Alamofire iOS" in Alamofire.xcworkspace
"Task failed with exit code 65."
In the logfile this is stated:
error: SWIFT_VERSION '3.0' is unsupported, supported versions are: 4.0, 4.2, 5.0. (in target 'Alamofire iOS') ** ARCHIVE FAILED **
What confuses me is that in my project under "Build Settings" the Swift version is set to 5. When I check in "/MyNetworkFoundation/Carthage/Checkouts/Alamofire/Alamofire.xcodeproj", the Swift version of all targets of is set to 5 too. I cannot spot Swift 3 anywhere in my framework nor Alamofire.
Alamofire Environment
Alamofire version: 5.0.0-beta.5
AlamofireNetworkActivityIndicator: -
Xcode version: 10.2.1
Swift version: 5.0
macOS version running Xcode: 10.14.5

@leonhelg5 Did you solve this yet? I feel like I am running into a similar issue.

Indeed, I had a nested Cartfile somewhere in the project. This messed everything up and created the conflicts.


Building issue (maybe due to use of Cargo workspace)

Hi,
I've noticed that the building process of this library is different from classic Rust libs or maybe (for sure ;-)) I'm doing something wrong.
When I run in the main folder:
cargo build
I get this error (with stable Rust 1.11.0):
error: failed to parse manifest at /home/killkrt/Development/vulkano/Cargo.toml

Caused by:
  no package or project section found.

And this error with nightly (1.13.0-923bac459):
error: manifest path `/home/killkrt/Development/vulkano/Cargo.toml` is a virtual manifest, but this command requires running against an actual package in this workspace

Anyway I was able to build each crate by myself going in each folder and launching cargo build.
As I understood cargo workspace are a new feature, but they should work with nightly release.
Anyway I think it should be mentioned in the README.md that you need a nightly version in order to build this lib and how.
Thank you.

Yes the crate is using workspaces.
The fact that you have to go in each directory is normal. The purpose of using a workspace is that all the crates share the same target directory.

Thank you!


Add default fallback for render function on Component

Is this something that is wanted/needed? Did you create a feature-request issue first?
This was such an easy thing, so I thought I'd PR it directly.
Does it include tests if possible? (Not a deal-breaker, just a nice-to-have)
I did not write any tests for this.
If this gets pulled in, people who don't customize and just return the default view in render() can remove it. Maybe it could even be removed from the default stub if it's a common thing to do.
One less method on your component.
I have just been playing with Livewire for a few hours, so I don't know if this is a dumb suggestion, but might as well throw it out there!
Thanks!

Wow, this is totally awesome. Seriously haha, it's perfect!

Niiiiice!

@all-contributors please add @adevade for code


chore: release 0.1.0

:robot: I have created a release *beep* *boop*
0.1.0 (2021-12-21)
Features

added ecosystem link (#72) (0520bb9)
bzz.link support (#137) (1eb061d)
download button feedback (#134) (fd2206d)
download folders and websites with metadata and preview (#129) (6723b9a)
gateway mvp - upload and download single files (601cf96)
make last modified time of uploaded file for metadata (#96) (57fc31d)
node index by hash (#95) (d268072)
recognize swarm hash (#132) (9e8873e)
redirect /bzz/ requests to direct download (#105) (9718d6d)
updated legal highlights (#52) (6b144f5)
upload multiple files, folders or websites (#124) (3727f7b)

Bug Fixes

button feedback on copy and button styles (#131) (6009449)
disable encryption on gateway (554962d)
on iOS the app is now always fully visible (#59) (22561c2)
pressed button styles on mobile devices (#56) (3a7b4bf)
removed google apis for fonts (8581cb6)
some mime types for video and audio (#97) (63e596f)
terms and conditions alert (#51) (398ce9e)
terms conditions padding (#50) (1e60463)
use name for the generated zipfile (#138) (90a2f80)
webside icon visuals (in access and in preview for website type) (#133) (a5aec31)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/ethersphere/gateway/releases/tag/v0.1.0 :sunflower:


Bump android build versions for newer react native

Hello!
When building a react-native 0.61.5 project with this lib included by ./gradlew assembleRelease the build fails because this lib has too old android targets:

1 exception was raised by workers:
com.android.builder.internal.aapt.v2.Aapt2Exception: Android resource linking failed
error: resource android:style/TextAppearance.Material.Widget.Button.Borderless.Colored not found.
error: resource android:style/TextAppearance.Material.Widget.Button.Colored not found.

In this PR I matched the targets with the current targets  of the 0.61.5 version.
The yarn android --variant=release command works without this somehow, but the above mentioned assembleRelease gradle command does not!
The buildToolsVersion is not neccessary for react native libs I think, but if im wrong then it should be set to 28.0.3.

+1

+1


Support Binary.securityContext for Binary resources if the securityContext target is Patient

Describe the bug
Currently for binary resources there is no special support for the securityContext element. With https://github.com/linuxforhealth/fhir/issues/3716 , we now issue a warning (or an error if validateSecurityContext=true) when the user tries to specify a securityContext through the Binary.securityContext element.
However, in fhir-smart we already have logic for enforcing access control based on patient compartment membership.
Thus it should be possible to add support for Binary.securityContext if the securityContext target is a Patient.
For all other securityContext target types we should continue to either log a warning message or throw an error based on validateSecurityContext configuration.(Please check https://github.com/linuxforhealth/fhir/issues/3716 for more details)
Environment
Which version of LinuxForHealth FHIR Server? 6.0
To Reproduce
Steps to reproduce the behavior:

Go to 'AuthzPolicyEnforcementPersistenceInterceptor.validateSecurityContext()' method.

Expected behavior
If Binary.securityContext is populated and points to a Patient resource, then access to this Binary resource (create, update, delete, etc.) should be restricted in the same manner as other resources that are associated with that patient.
For example, if fhir-smart is configured, and the request has the patient/Binary.read scope, then the user can only access this resource if they can also access the corresponding Patient resource.
Additional context
Related to https://github.com/linuxforhealth/fhir/issues/3716
Workaround / alternative idea:  consider a Binary resource to be part of a Patient Compartment.
I believe that this could be done today just by registering a modified version of the Patient CompartmentDefinition (thanks to #2143).

thinking about this a little more, at least in the context of fhir-smart, I think we should be able to make this work with a securityContext that references ANY resource type.
if the securityContext references a resource, we'd attempt to dereference (i.e. read) the target resource and then check if the user has access to that resource or not (and has passed scopes to allow the interaction).  Then we'd use the result of that decision to decide whether the interaction with the Binary is permitted or not.
We'd need to decide

whether the patient/Basic.read scope would be needed to read the Basic resource, or if its access would be solely tied to the securityContext target
what to do if the target resource doesn't exist on the server...maybe we only need to dereference it if its a patient compartment resource and the user has passed one or more patient/ access scopes?

NOTE:  its not just about read access.  We also shouldn't allow a user to create a Binary resource that has a securityContext which references another resource that they do not have access to.  But we need to be careful there not to leak information about the presence/absence of that target.

whether the patient/Binary.read scope would be needed to read the Binary resource, or if its access would be solely tied to the securityContext target

Dag and I discussed this one and had a slight difference of opinion.
The way I saw it is this would be an additional check.  On top of requiring Binary.read permissions, the user also needs access to the resource referenced by the securityContext.
The way Dag saw it is that the proxy resource should be checked instead of performing this Binary.read permission check.


switching to nunuvut

I'm going to override this review since this is only a rename from pydsdlgen to nunuvut.

You seem to have misspelled it as nunuvut in the README (and in the issue title).

and this is why one should never skip reviews :/


Add telemetry CLI flag section

Description
The introduction of this new section will reduce confusion between the telemetry
configuration for the telemetry that Promscale produces and various other types
of telemetry Promscale is used to store and query.
Merge requirements
Please take into account the following non-code changes that you may need to make with your PR:

[x] CHANGELOG entry for user-facing changes (not needed, changelog already includes CLI renaming changes)
[x] Updated the relevant documentation

I'm not sure that I understand the motivation behind this change. I'm also not sure what it clears up exactly. The term telemetry seems to have three different meanings at the moment:

Tracking/sending promscale usage data (usage telemetry)
Promscale's telemetry (logs, metrics and traces that it emits about itself)
End-user telemetry (logs, metrics and traces that Promscale stores, the reason it's used).

I tend to agree with James. Are these flags related to the logs that the connector spits out about its own activity?

This change is about the Promscale telemetry it emits about itself. I understand there are multiple tracks of telemetry when talking about Promscale, maybe we can figure out a better name for this group.
I'm open to suggestions for naming, the main thing that we separate out these options from the other telemetry which will be ingested into Promscale.


Sheet order changing by simply reading and rewriting data to new file

I have this excel file.
s3data1.xlsx
I have this simple snippet.
const again = await XlsxPopulate.fromFileAsync('./s3data1.xlsx').then((workbook) => {
      workbook.toFileAsync('test.xlsx');
      return workbook.outputAsync()
    });

And I see a file test.xlsx created
test.xlsx
Now if you carefully look at both files.
Content in 2nd tab of first sheet has shifted to 4th tab of 2nd sheet.
What am I doing wrong? Any help at the earliest would be appreciated.

You only need the workbook.toFileAsync(). Calling workbook.outputAsync afterwards is not needed.

@NikhilCodes Did you get this issue fixed as i am facing the same problem. Would like to know more info.

@AmdEagle what i had to do was, read the file using python pandas and save it again. After that the xlsx-populate doesnt glitch if you work on newly saved file. Reasons unknown. But works


Float Text Overlap when not inputting text

After inputting text in a field that has a float label, the float text overlaps like below

Expected behaviour is:

Potential fix https://github.com/primefaces/primeng/issues/4277#issuecomment-410431901


[v.ifeng.com]Ifeng extractor

extractor of v.ifeng.com.
凤凰网

This PR should not contain changes unrelated to ifeng extractor.


Test failure: test_simulator[Language.QIR-H1-1E]

Error message is:
"1000: Compile error: 1 Encountered Unexpected Instruction   %0 = call i1* @create_creg(i64 2)"

This is with pytket 1.20.0rc3, pytket-qir 0.2.1rc1.

Still showing up with pytket-qir 0.3.0.

QIR tests have been commented out: please search for #236 and uncomment to ensure they pass (or open separate issues) before closing this one.


Allow key prop on SVG

I just tried this with unsafeCreateDOMComponent and it works, so I suppose there's no good reason for not having it.
If there's interest, I can try to add it.

Sure, I think it should be on all those elements

This one is a bit trickier because it uses the SVG props library. What would you suggest as an approach for this? Fork the library? Inline and modify it? Modify the values after importing it?

I had a similar issue with the HTML attributes, which used to come from the react-html-attributes package. There's simply too much friction to liaise with upstream over each change, so I decided to make a local copy of the JSON file from that package. Haven't upstreamed my changes yet, need to get round to that!

Hey thank you so much for addressing this? I don't understand what the linked PR does? Do you think you could explain it in one or two sentences?

Most of the PR was an unrelated change, but while I was altering the codegen anyway I changed it to always add ref, key, _data, and (optionally) children. Previously it was defined in the json file.

Ah thank you very much for explaining this!


Django 1.7 warnings

I had warnings for Django 1.7 in models:
.../env/local/lib/python2.7/site-packages/oauth_tokens/models.py:134: RemovedInDjango18Warning: commit_on_success is deprecated in favor of atomic.
  @transaction.commit_on_success

.../env/local/lib/python2.7/site-packages/vkontakte_api/models.py:167: RemovedInDjango18Warning: commit_on_success is deprecated in favor of atomic.
  @transaction.commit_on_success

.../env/local/lib/python2.7/site-packages/vkontakte_api/models.py:253: RemovedInDjango18Warning: commit_on_success is deprecated in favor of atomic.
  @transaction.commit_on_success

$ pip freeze
Django==1.7.4
MySQL-python==1.2.5
Pillow==2.7.0
argparse==1.2.1
...

thanks! commited new version 0.7.11


Week 2 - created a CCIP nft minting dapp for chains OP sepolia , Arbitrum , Polygon amoy and Avalanche Fuji and Tested the Cairo contract on Starknet

Week 2 PR Description
This PR covers the deployment and creation of the CCIP minting functionality for mulitple chains Like OP sepolia , Arbitrum , Polygon amoy and Avalanche Fuji
and Testing , Setup and Deployment of cairo contract on starknet and also setup of scaffold stark.

#1


command unshare broken

Toybox 0.8.9-android multicall binary, i am rooted user, and the unshare command refuses to work.
Tested commands
unshare --user --pid --map-root-user --fork bash
unshare: Invalid argument
NX729J-EEA:/ # toybox unshare --fork bash
works
NX729J-EEA:/ # toybox unshare --ipc --fork bash
unshare: Invalid argument
1|NX729J-EEA:/ # toybox unshare --pid --fork bash
unshare: Invalid argument
1|NX729J-EEA:/ # toybox unshare --uts --fork bash
works
NX729J-EEA:/ # toybox unshare --user --fork bash
unshare: Invalid argument
All of these commands work on AMD64 Arch Linux
is there anything i can do to update or fix this command?

i think that just means your kernel was compiled without those options. see the ERRORS section of https://man7.org/linux/man-pages/man2/unshare.2.html for details.


Support multi-threaded pool filling

Environment
HikariCP version: 3.2.0
JDK version     : 1.8.0_111
Database        : any
Driver version  : x.x.x

I read about Hikari having multi-threaded behavior when system property "com.zaxxer.hikari.blockUntilFilled" is set to true.
But this multi-threaded behavior is restricted only to pool initialization phase.
What is the reason for not having this feature for pool lifetime?
If it can be provided for specific scenarios for limited time period, then why not add it for pool lifetime? This can be added as new configuration to HikariConfig. This will help the pool to always fill faster and hence serve connections without delays.
Same parallel behavior can be applied for closer threads so that connection eviction process is faster and new connections get added quickly.
Similar requirement was filed in #934 before #1287 , but it wasn't taken up.
This (#934) has been a long standing requirement on Hikari from our side as it is really impacting the performance of our application and hence the customers. We do not want to go to Apache DBCP as we found Hikari much better in all aspects.
Please refer the following issues stating the demand for parallel connection creation and closure:

Adder thread execution behaviour #934
HikariCP getConnection blocks when establishing new connection #1287

I would like this behavior to be added in Hikari as it is a generic requirement for any end user and will help improve the performance of any application using Hikari. This would really give Hikari an edge over other connection pools.

During the lifetime of a connection pool, only a small portion of the time is actually spent on creating connections. The whole purpose of a connection pool is to allow reuse of connections which by definition reduces the frequency that new connections will be created. HikariCP is specifically designed so that multiple connections don't need to get evicted at the same time. There are many parts of the design that attempt to ensure that there will always be connections available. But this will fail if the application isn't using those connections wisely.
Can you explain more about the use case where you need to close and recreate connections rather than continuing to use the connections that are already available in the connection pool? My gut feeling is that if there is any contention closing connections and creating new connections, then there is likely a suboptimal configuration. Maybe the system is trying to run way too many connections simultaneously.
If you can provide an example use case that justifies the need for parallel connection creation, then I think we can investigate it. But currently we haven't heard any specific use case that hasn't had a much better alternative solution.
In the case of #934, that is an edge case. No normal database takes longer than even a second, and it is likely that it would better worth everyone's time to fix that database to allow for faster connections than to alter HikariCP which likely could have a negative effect on the other 99% of use cases.
In the case of #1287, that particular use case was handled by allowing the parallel connection creation on startup, but subsequent connection creation should not be a performance problem, as the connections should not all be being evicted simultaneously.
As a final note, any effort to improve the performance of connection creation for these edge cases actually has the side effect of reducing the absolute maximum performance for all the other use cases. As was stated in #1287, adding support for parallel connection creation while the pool is running can greatly increase the complexity which in turn would increase the risk of race conditions and other bugs. It also would likely hurt the top end performance by introducing the need for locks. The current architecture works without needing locks in cases where other connection pools need them. This is one of the reasons why the benchmarking generally has HikariCP much faster than other connection pools.
And lastly, as this is an open source project and no one is making any money off of it (that I know of), there isn't much expectation of developers going and investigating this without having a personal motivation to do so. Since you are motivated, you would be in a perfect position to try to implement a fix. If you were to create a Pull Request that adds support for this functionality and can demonstrate that it has no negative effect on performance, as well as being not needlessly complicated, then we can easily consider merging it in.

@lfbayer , databases do not take more than a second to create a connection. But in our case, we do not connect to databases or RDBMSs to be precise.
Our application is a middleware which connects to source and destination application systems and helps migrate the data. These applications can be like Teamcenter, SAP, WindChill, Primevera or any other application system for that matter.
The connection pool we are creating here is for the connections to these applications. These applications take time to connect to, which may vary from few seconds to around a minute as well. Teamcenter, for that matter, takes around 30 to 40 seconds to create a connection. For a connection pool with minimum idle set to 50 and maximum set to 100, it would take around 25 - 30 minutes to create those many minimum idle connections.
After our applications starts up (start up completes within 2 minutes), hundreds of requests (bulk load) come to acquire connections. Since the pool will not be filled by this time, users experience a huge delay in getting response.
We cannot block the connection acquisition from the pool for this time either as blocking the pool would only create a bottleneck and reduce the performance drastically.
Another use case is for closing and recreating connections. Teamcenter connections are observed to consume more memory on each use. This leads to high memory consumption which slows down the execution. This is solved by closing and recreating the connection. Since many consumers may return the connections to the pool after use, lots of connections can be evicted simultaneously thus reducing the pool size. Parallel connection creation in this case again would help serve the subsequent requests without delay.
We are using HikariCP to solve our use cases. Our time is spent on addressing the needs of our application, hence it would be difficult for us to investigate and understand HikariCP enough to effectively contribute to it and carry out all test cases. Since you guys are totally familiar with Hikari, you can address the requirement more effectively and perfectly.

Seems like it would be worthwhile for Teamcenter to work out their issues? Even if HikariCP did support parallel connection creation, based on what you are saying, there would still a big performance hit on the Teamcenter side.
There have been other cases where there were bugs in drivers and users have asked for a workaround to be created within HikariCP. The answer has almost always been no. And in most cases the fix was actually easily added to the driver itself. Sometimes it just takes a pull request against the right system. This way all the various systems involved can improve, instead of just using one of the systems as the catch all to solve every problem.
Would it be viable to have the performance issues resolved in those other applications?
Out of curiosity, do all of those application systems really provide JDBC data sources? HikariCP is explicitly a JDBC connection pool, so it is a little surprising to hear it being used something that isn't an RDBMS.

Teamcenter and other such systems are third party commercial applications. Getting any changes done on those would not be feasible.
These applications do not provide JDBC data sources. We adapt to those connections by wrapping them inside JDBC connections.

This is a use case outside of the scope of HikariCP, as HikariCP is specifically a JDBC connection pool.
It sounds like it might be better to use a generic object pool rather than something specifically designed for JDBC. This would also remove the need for wrapping connections in JDBC connections.
Something like apache commons pool might provide the flexibility that you are interested in.

@Ni3Aphle It sounds like you aren't using JDBC at all, and instead just using HikariCP as an object pool with faux JDBC connections that wrap some other third-party connection mechanism.
If this is what you are indeed doing, I recommend using stormpot or Apache Commons Pool.
You asked:

If it can be provided for specific scenarios for limited time period, then why not add it for pool lifetime?

The answer is, the add connection path using a lightweight locking mechanism with respect to borrowing from the pool that only allows a single-thread to add to the pool when borrow is possible.   This is for performance reasons, acknowledging that borrows are several orders of magnitude greater than adds -- and therefore should not be penalized by acquiring a heavyweight lock on every borrow just to avoid a rare collision with add.
Therefore, parallel add is only available during startup, when there is a guarantee that the pool is not yet available for borrow.
This is not something that is likely to change.
If you insist on using HikariCP when what you need is a generic object pool, at least don't abuse the pool by manually evicting connections.  Set a relatively short maxLifetime, like 15 minutes, to avoid your memory issue.  HikariCP contains logic to spread out connection retirement to avoid mass extinctions in the pool.  In time, retirements and replacements will spread out roughly evenly over the maxLifetime period.  By manually evicting connections, you can actually cause mass extinctions in the pool, thereby crushing your performance given your high acquisition times (so don't do that).
The reporters of #934 and #1287 were both satisfied with the parallel fill behavior on startup.  Unless your connection lifetimes are exceedingly short -- approaching 2x acquisition time -- it is hard to imagine running into any performance issues if your settings are properly tuned.


Draft: Change URL to point folks to next steps in the docs

@tayloramurphy I'm bringing this over from https://gitlab.com/meltano/meltano/-/issues/3093#note_750992714 (now https://github.com/meltano/internal-general/issues/326). Not sure if this is where this should point but wanted to at least get this rolling since meltano.com no longer shows a quickstart. Did you have thoughts on this?

@afolson lgtm!


ARROW-1864: [Java] Upgrade Netty to 4.1.17

Upgrade Netty to 4.1.17 since the Netty community will deprecate 4.0.x soon. This PR includes the following changes:

Bump Netty version.
Implement new ByteBuf APIs added in Netty 4.1.x: a bunch of get/setXXXLE methods. They are the opposite of get/setXXX method regarding byte order. E.g., as ArrowBuf is little endian, setInt will put an int to the buffer in little endian byte order, while setIntLE will put int in big byte endian order. The method naming seems confusing anyway, and I opened a Netty issue: https://github.com/netty/netty/issues/7465. The user can call these new methods to get or set multi-byte integers in big endian byte order.
Implement ArrowByteBufAllocator#calculateNewCapacity. This method was copied from AbstractByteBufAllocator. Netty 4.1.x moved this method from AbstractByteBuf to AbstractByteBufAllocator. However, as ArrowByteBufAllocator doesn't extend AbstractByteBufAllocator, it doesn't get the implementation automatically and we have to copy the codes.

Is netty upgrade requiring some changes? Why are we removing methods from ArrowBuf?
ArrowBuf and related memory classes bypass the class hierarchy structure in some places and that is by design for performance reasons -- instead of delegating, we directly interact with memory. If I am understanding the code changes correctly, seems like removal of certain functions will change this.
I don't think so we should be doing that unless there is a strong reason or netty upgrade is forcing this change.

Is netty upgrade requiring some changes?

Yes. Need to implement new APIs.

Why are we removing methods from ArrowBuf?

I will add them back.

Removal of getLong() will now require us to go down the hierarchy of other netty classes -- AbstractByteBuf, MutableByteBuf etc.

By the way, what I removed is getDouble, getFloat.. etc. The current diff is really weird and it's hard to find the real change...

@zsxwing , thanks for adding the methods back.
In case of implementing new APIs, can you please give some insight into why they are needed and how (if at all) they will be used by the existing vector classes?
It would be good if these can be properly documented in the PR or better to send out to the mailing list highlighting the rationale behind implementing new APIs and their corresponding consumers.

Rebased

@siddharthteotia I updated the PR description to add more details.

Thank you for working on this @zsxwing and reviewing @johnou. Since this impacts Spark, it would definitely be great to get this into 0.8.0

Thanks @zsxwing for addressing the earlier review comments and adding description to PR.
As you mentioned the new method names are slightly confusing.
If I understand it correctly, setIntLE will write a LE int to ArrowBuf in BE byte order and getIntLE will get a BE int. Both functions are essentially swapping the bytes when reading/writing from/to ArrowBuf
Can you add some javadoc for each such function to explain the behavior? Similarly there are some medium functions newly introduced. It would be good to add javadoc for the same.

@siddharthteotia added javadoc for new methods.

+1, fyi I tested this upgrade with Spark and it allows Spark Arrow tests to pass (after applying https://github.com/apache/spark/pull/19829 on top of https://github.com/apache/spark/pull/19884)

@siddharthteotia Any further comments?

@BryanCutler Thanks for your testing!

+1. Thanks @zsxwing.

Thanks all!


Spin up the Front End on Heroku

Overview
To spin up the front end based on react using Heroku so that QA can be done.

Facing Errors while deploying the app using a docker container.
Steps to replicate the issue

Clone the repo and checkout to master branch
Install Heroku CLI
On the local environment, using a terminal window on a mac go to the website folder where the repo is cloned

heroku login
heroku container:login

On Login Succeeded message,
docker build -t webmasterimage .
heroku container:push web -a cti-dev
heroku container:release web -a cti-dev
heroku open -a cti-dev

Leads to:

On Debugging,
heroku logs --tail -a cti-dev

Error Message:
2020-05-17T23:40:08.123266+00:00 app[api]: Release v1 created by user<EMAIL_ADDRESS>2020-05-17T23:40:08.123266+00:00 app[api]: Initial release by user<EMAIL_ADDRESS>2020-05-17T23:40:08.836798+00:00 app[api]: Release v2 created by user<EMAIL_ADDRESS>2020-05-17T23:40:08.836798+00:00 app[api]: Enable Logplex by user<EMAIL_ADDRESS>2020-05-18T23:45:17.564803+00:00 app[api]: Deployed web (96b052ed03cf) by user<EMAIL_ADDRESS>2020-05-18T23:45:17.564803+00:00 app[api]: Release v3 created by user<EMAIL_ADDRESS>2020-05-18T23:45:17.591933+00:00 app[api]: Scaled to web@1:Hobby by user<EMAIL_ADDRESS>2020-05-18T23:45:20.605212+00:00 heroku[web.1]: State changed from starting to crashed
2020-05-18T23:45:20.608217+00:00 heroku[web.1]: State changed from crashed to starting
2020-05-18T23:45:20.540370+00:00 app[web.1]: 2020/05/18 23:45:20 [warn] 4#4: the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /etc/nginx/nginx.conf:2
2020-05-18T23:45:20.540391+00:00 app[web.1]: nginx: [warn] the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /etc/nginx/nginx.conf:2
2020-05-18T23:45:20.541562+00:00 app[web.1]: 2020/05/18 23:45:20 [emerg] 4#4: bind() to <IP_ADDRESS>:80 failed (13: Permission denied)
2020-05-18T23:45:20.541562+00:00 app[web.1]: nginx: [emerg] bind() to <IP_ADDRESS>:80 failed (13: Permission denied)
2020-05-18T23:45:23.591426+00:00 heroku[web.1]: State changed from starting to crashed
2020-05-18T23:45:23.516925+00:00 app[web.1]: 2020/05/18 23:45:23 [warn] 4#4: the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /etc/nginx/nginx.conf:2
2020-05-18T23:45:23.516945+00:00 app[web.1]: nginx: [warn] the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /etc/nginx/nginx.conf:2
2020-05-18T23:45:23.518137+00:00 app[web.1]: 2020/05/18 23:45:23 [emerg] 4#4: bind() to <IP_ADDRESS>:80 failed (13: Permission denied)
2020-05-18T23:45:23.518138+00:00 app[web.1]: nginx: [emerg] bind() to <IP_ADDRESS>:80 failed (13: Permission denied)
2020-05-18T23:46:58.957338+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=cti-dev.herokuapp.com request_id=99014836-d102-4851-a8fc-6a14d944f829 fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https
2020-05-18T23:46:59.615920+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=cti-dev.herokuapp.com request_id=88855350-2aac-49bb-afb9-779cf963534f fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https
2020-05-18T23:56:52.492026+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=cti-dev.herokuapp.com request_id=746d4f08-a0c6-48fc-a364-201c38144826 fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https
2020-05-18T23:56:53.741810+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=cti-dev.herokuapp.com request_id=89abc1af-ce34-439f-ae3d-d08a595da1f7 fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https
2020-05-18T23:59:14.490837+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=cti-dev.herokuapp.com request_id=efea27c7-2264-4a8f-8f7e-8961a8637e4a fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https
2020-05-18T23:59:15.053352+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=cti-dev.herokuapp.com request_id=e05a2b81-99dd-4ee8-9528-2a0de462ceae fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https
2020-05-19T00:03:30.254166+00:00 app[api]: Starting process with command `rails console` by user<EMAIL_ADDRESS>2020-05-19T00:03:31.850821+00:00 heroku[run.2764]: State changed from starting to up
2020-05-19T00:03:37.091069+00:00 heroku[run.2764]: State changed from up to complete
2020-05-19T00:03:55.926615+00:00 heroku[web.1]: State changed from crashed to starting
2020-05-19T00:04:00.649682+00:00 heroku[web.1]: State changed from starting to crashed
2020-05-19T00:04:00.653287+00:00 heroku[web.1]: State changed from crashed to starting
2020-05-19T00:04:00.510263+00:00 app[web.1]: 2020/05/19 00:04:00 [warn] 4#4: the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /etc/nginx/nginx.conf:2
2020-05-19T00:04:00.510286+00:00 app[web.1]: nginx: [warn] the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /etc/nginx/nginx.conf:2
2020-05-19T00:04:00.514371+00:00 app[web.1]: 2020/05/19 00:04:00 [emerg] 4#4: bind() to <IP_ADDRESS>:80 failed (13: **Permission denied**)
2020-05-19T00:04:00.514384+00:00 app[web.1]: nginx: [emerg] bind() to <IP_ADDRESS>:80 failed (13: Permission denied)
2020-05-19T00:04:03.989925+00:00 heroku[web.1]: State changed from starting to crashed
2020-05-19T00:04:03.903366+00:00 app[web.1]: 2020/05/19 00:04:03 [warn] 4#4: the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /etc/nginx/nginx.conf:2
2020-05-19T00:04:03.903403+00:00 app[web.1]: nginx: [warn] the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /etc/nginx/nginx.conf:2
2020-05-19T00:04:03.905651+00:00 app[web.1]: 2020/05/19 00:04:03 [emerg] 4#4: bind() to <IP_ADDRESS>:80 failed (13: Permission denied)
2020-05-19T00:04:03.905715+00:00 app[web.1]: nginx: [emerg] bind() to <IP_ADDRESS>:80 failed (13: Permission denied)
2020-05-19T00:04:36.033089+00:00 heroku[web.1]: State changed from crashed to down
2020-05-19T00:04:35.581995+00:00 app[api]: Scaled to web@0:Hobby by user<EMAIL_ADDRESS>2020-05-19T00:07:38.763732+00:00 app[api]: Rollback to v1 by user<EMAIL_ADDRESS>2020-05-19T00:07:38.763732+00:00 app[api]: Release v4 created by user<EMAIL_ADDRESS>2020-05-19T00:09:25.541439+00:00 heroku[router]: **at=error code=H10 desc="App crashed" method=GET path="/"** host=cti-dev.herokuapp.com request_id=6f6354de-e8c8-4729-87c1-21fa7050f6bc fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https
2020-05-19T00:09:26.486905+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=cti-dev.herokuapp.com request_id=dba5d9fb-4fbd-44c3-ac01-4ea2fcb9f2f6 fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https
2020-05-19T00:10:15.976942+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=cti-dev.herokuapp.com request_id=0b497a14-be23-40bc-8842-564403820afc fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https

Insights
? Permission Denied
? at=error code=H10 desc="App crashed" method=GET path="/"
Next Steps

Debugging the issue when trying to deploy the app using docker container
Will try to deploy the application using GitHub

@ExperimentsInHonesty Could you approve my request to connect the cti-dev (heroku-app) to Github civictechindex organization

The most stable version is deployedhttps://cti-dev.herokuapp.com/ BUT switched off purposely.
Current State

Previous State

But there is a catch here, the dyno associated with it is a paid version - Dyno Hobby.
Researched online, how to downgrade dyno hobby to dyno free?
From the reply in the question from stackoverflow Turns out that if the Heroku app is created under a team $7 per month(hobby) is the lowest you can go.
@ExperimentsInHonesty I have switched to 0$(No Dyno associated) now so that we aren't billed.
We can use a personal account to spin up the website with zero charges.
Let me know whatever sounds feasible to you.

I authorized the $7 a month version.  So we are now live.  @Abhishek-AC is there anything else left to do on this issue or can we close it?

We can close this issue. I will reach out to someone in the ops team, to verify the creation of a pipeline and standards that should be followed while deploying the app to Heroku.


[feat] Only one application instance can be opened

Describe the problem
While the application is running, open again to show() the first running application.
Describe the solution you'd like
like:
https://www.electronjs.org/docs/latest/api/app#event-second-instance
Alternatives considered
No response
Additional context
No response

This is implemented as a plugin (for now): https://github.com/tauri-apps/tauri-plugin-single-instance


prometheus-kea-exporter: init at 0.4.1

Motivation for this change
This is the Prometheus exporter for the ISC Kea DHCP daemon, I want to monitor DHCP metrics with it.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Can you please add a module for the exporter?

Thanks for your patience, I did a thing.


Both or neither cases of tap-hold executing

Platform: Windows
Version: 0.4.1, downloaded from this repo
It's very possible I don't understand the mechanics at play here, please set me straight if I'm confusing something...
The thing I'm observing is that sometimes both or neither cases of my tap-hold are executing, like this: (note the long delay makes it easier to repro, I'm not sure if this is part of the problem, though strange behaviour even with low delays led me to start exploring this...)
(defalias z (tap-hold 2000 a b) )
(mapped to the z key)

In this example, I'm pressing this modded z key and also an unmodded c key. If I do this whole thing "kinda slowly", I can consistently get it to print an extra letter on one time, and neither letter on the next time.
Pz 1000 Pc 200 Rc 200 Rz
-> abc... c... abc... c... abc... c
Yikes!
On the first "double" set, the a appears when I release the z key, no keys are pressed at all, then some time later, b and c appear.
On the second "neither" set, the c appears the moment it is pressed.

This is definitely not a 100% repro, and there are lots of ways of pressing the keys that get correct output. But I feel like this alias and input sequence should always output two letters.
I'm happy to post logs or any other information I can!

log.txt
Okay, here is a more succinct log. Breakdown as I see it.

It looks like it might have something to do with key repeat. If you look at this log, you can see several Press <k> events being triggered in a row, even though I'm holding the key down.
So on the first Release <k>, it's under 2000ms so emits a c. This is expected.
Then it emits the stored Press <k> events, starting a new block/timer, the emits and re-stores the Press <w> and Release <w>.
There is no matching Release <k> event! Eventually it times out, so it emits a Release <c>, Press <d>, and then replays the Press/Release <w>
At this point, it has typed cdw. k has not been released, and d has not been released. (c and w both have had press/release pairs.
(I then pressed spaced to separate the two scenarios.)
After the space, I press k, and Press <k> events immediately start repeating, presumably because k was never released?
Then Press/Release <w> are handled immediately to emit a w because k has been pressed longer than the timeout, and is currently "holding d".
Finally, I release the physical k key. This receives the Release <k>, which, emits a Release <d>.
It has typed just c, but now all keys are properly released, so the cycle can continue.

cdw w cdw w cdw w cdw w....
So it seems like the bug is that when a trigger key gets "key repeat'd" inside a hold, it's re-emitting those repeated presses, basically getting pressed twice. (hence both branches being triggered). Additionally, this bonus press never gets a release, so on the next try, the press is ignored because the key is "already pressed".

log.txt
Here's another log where I don't even press w the second time (just space in between to illustrate the two physical presses). I typed this: Pk 1000 Pw Rw Rk Pspc Rspc Pk Rk.
The second press of K was basically ignored.
Hope this is clear and reproducible now!


refactor kernel_repack with new features to ease usage and maintenance

fairly large change, but has been tested and in use for a while.

new command: getchangelog -
new command: updatekernel - run an update

#9  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @NeilHanlon and the rest of your teammates on  Graphite


Seeding error occurred

In Chapter 6: Setting up the database, can anyone have an error in the Seeding process?
I followed all the steps given there.

#314


Issues with encoding of Spanish localisation

CI still complains about problems with the encoding of the Spanish localisation file:

Not sure what's causing it but at the same time its not really an issue since that file works


[Press] Add blog post from After Dark creator

https://habd.as/zero-to-http-2-aws-hugo/

Hello @jhabdas,
thank you for adding this post to the press section.
Cheers,
Digitalcraftsman


test(layout): adds nested layout test

Ref: https://github.com/poppinss/edge/issues/6

Replied on related issue


C# Dispatch startup code expects a subscription key for Dispatch, throws exception

Sample information

Sample type: samples
Sample language: dotnetcore
Sample name: 14.nlp-with-dispatch

Describe the bug
Following the readme instructions causes an exception at startup;
C# Dispatch startup code expects a subscription key for Dispacth, throws exception.
To Reproduce
Steps to reproduce the behavior:

Go to the README for the sample.
Follow the steps in the readme:

Install BotBuilder tools.
Manually configure required services.
Manually change the endpoint name in the .bot file to "development". (re: issue #606)
Run the bot in Visual Studio.

The app throws an exception in Startup.cs, line 216:

System.InvalidOperationException
  HResult=0x80131509
  Message=The Subscription Key ('subscriptionKey') is required to run this sample. Please update your '.bot' file.
  Source=NLP_With_Dispatch_Bot
  StackTrace:
   at NLP_With_Dispatch_Bot.Startup.InitBotServices(BotConfiguration config) in C:\Users\v-jofing\source\repos\BotBuilder-Samples\samples\csharp_dotnetcore\14.nlp-with-dispatch\Startup.cs:line 219
   at NLP_With_Dispatch_Bot.Startup.ConfigureServices(IServiceCollection services) in C:\Users\v-jofing\source\repos\BotBuilder-Samples\samples\csharp_dotnetcore\14.nlp-with-dispatch\Startup.cs:line 77

Expected behavior
Following the instructions should not cause an exception.
Additional context
Here are the offending lines. The instructions to construct the .bot file or the code in Startup should be updated so no exception is thrown.
BotConfiguration.bot (lines 42-55):
        {
            "type": "dispatch",
            "name": "NLP-With-Dispatch-BotDispatch",
            "appId": "5b0651a9-2f9f-4b90-826d-93005de692e4",
            "authoringKey": "<my-authoring-key>",
            "version": "Dispatch",
            "region": "westus",
            "serviceIds": [
                "178",
                "46",
                "54"
            ],
            "id": "138"
        },

Startup.cs (lines 193-217):
case ServiceTypes.Dispatch:
	...
	if (string.IsNullOrWhiteSpace(dispatch.SubscriptionKey))
	{
		throw new InvalidOperationException("The Subscription Key ('subscriptionKey') is required to run this sample. Please update your '.bot' file.");
	}
	...

[bug]

Closing via #613


isPlacable and isPathable are broken

Although, we fixed #4 the isPlacable and isPathable functions are still broken (always return false) for the 1bit case due to explicit checkout:
return value == 255 ? true : false;.

Fixed.


add makefile to define targets

make should minimally include targets for:

install

displays confirmation before continuing
checks system package requirements in PATH

exits with error code if not all requirements are present

installs perl deps through cpanm
creates sqlitedb if db doesn't exist
applies db patches
outputs instructions for adding mastodon credentials
outputs instructions for adding cronjob

upgrade

displays confirmation before continuing
updates repo
applies db patches which haven't been applied

for functionality not implemented yet (applying db patches requires a table to track applied patches), add echo "not yet implemented"

added install target and accompanying scripts in 5962b45

added upgrade makefile target and accompanying script in 7ff6ab0e


No longer loads on core-2021.6.0

after core-2021.6.0, existing integrations no longer load on start, and the integration is no longer visible in the integration list after this repo is installed via HACS

[homeassistant.loader] The custom integration 'uhoo' does not have a valid version key (None) in the manifest file and was blocked from loading. See https://developers.home-assistant.io/blog/2021/01/29/custom-integration-changes#versions for more details

This issue was resolved with release 0.0.3


[Public] Upgrade jQuery UI to 1.13.2

Purpose

Upgrade jQuery UI version to 1.13.2

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/2827350607

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/2827350607
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/2827371259

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/2829337668

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/2829337668
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/2829410962

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/2829410962
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/2829990330

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/2829990330
Status: success

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/2831486072

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/2831486072
Status: success


Improvness in LOGO

As you can see logo is not attractive
I can design more attractive logo
hey @07sumit1002 assign this task to me

Pull the latest code and then work on it

hello sir can you assign me this issue please

Hi there! 👋
I'm really excited about contributing to open-source projects during Hacktoberfest and GSSoC. I have a good eye for design and have previously worked on logo creation and web design. I've also designed a few websites, and I'd love to bring those skills to your project.
If you need help with designing a logo, improving the UI/UX of your website, or any other design-related tasks, I'd be happy to jump in! I think my skills could really add value to your project, and I'd love the chance to collaborate.
Looking forward to your response and to possibly working together!
Thank you
Best regards
Abhishek Saxena

Hi, I would like to work on this issue. Can I be assigned, please?

I'll complete my task till tomorrow's night
On Tue, 8 Oct, 2024, 11:18 pm Padmasree-Sangani, @.***>
wrote:

Hi, I would like to work on this issue. Can I be assigned, please?
—
Reply to this email directly, view it on GitHub
https://github.com/07sumit1002/CabRental/issues/222#issuecomment-2400473195,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BJUW362CQXB4VR6ZTOK2BULZ2QLG5AVCNFSM6AAAAABPN6NPVKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBQGQ3TGMJZGU
.
You are receiving this because you were assigned.Message ID:
@.***>


This repo is currently Delphi 11 specific

Took me ages to track this one down....
P4DPyPackage.dproj and dclP4DPyPackage.dproj are currently specifically targeting ver 280 / 22.0

Fixed the dproj
PR on the way with fix


Verify VkFormatProperties::linearTilingFeatures.

Verify VkFormatProperties::linearTilingFeatures when an application uses a linear texture.
Some implementations of Vulkan don't (officially) support any linear textures and various samples now use linear staging textures without explicitly checking whether or not they are supported:
https://github.com/KhronosGroup/Vulkan-LoaderAndValidationLayers/blob/master/demos/cube.c
https://github.com/KhronosGroup/Vulkan-LoaderAndValidationLayers/blob/master/demos/tri.c
https://github.com/LunarG/VulkanSamples/blob/master/API-Samples/inittexture/inittexture.cpp

But all of those samples do look at the linearTilingFeatures for the texture format they are using.  If the FEATURE_SAMPLED_IMAGE bit is set, they go ahead and use the linear format for the texture.  If the bit isn't set, they only use the linear image as a staging buffer (and they should really use a buffer instead of an image), map the memory, load the texture and use a CmdCopyImage to get the pixels out of the linear tiled image and into the optimal tiled texture image which is used for rendering.  Or am I misunderstanding your concern with the samples?

The concern is that vkCmdCopyImage copies from a linear texture without checking whether or not linear textures are supported at all.

Is vkCmdCopyImage always supposed to work with linear images? The spec does not explicitly state this, but that would make sense. There are also no feature bits to specify that this would not be supported.

We recently did some work on the screenshot layer (in VulkanTools) and put the following comment in screenshot.cpp:
    // There seems to be no way to tell if the swapchain image (image1) is tiled
    // or not.  We therefore assume that the BLIT operation can always read from
    // both linear and optimal tiled (swapchain) images.
    // There is therefore no point in looking at the BLIT_SRC properties.

The code in this area handles the job of getting the image bits out of a swapchain image and into a PPM file, so it needs to COPY or BLIT the image from the swapchain to another image that can be mapped by the CPU.  It also does a format conversion so that the code that copies the pixels to the PPM file only needs to work with one format.
Since there's no way to tell if the image is linear or tiled, we have to go ahead and assume that vkCmdCopyImage (and vkCmdBlitImage) can always read from linear images.  So I agree with you that this would make sense, even though it is not explicitly stated.
The code does check to see if CmdBlit can write to linear.  If it can't, then it does the CmdBlit to do the format conversion and then CmdCopy to convert optimal to linear.

The copy is from a linear image, not texture, and that image is discarded once the copy is done.  The linear image is only used as a texture (sampled) if the format feature bit is set.

Correct, I meant image instead of texture. My bad. I assumed a copy from a linear image wasn't a required feature.


Implement devpav

looks good to me - but I'll leave it to Peter to comment on whether this does what it should do. If you increase the version number in setup py we can make a new lir release to make it easier to use this?


[SP-4428] Backport of PDI-17278 - Repository Job Fails Using Variable…

… to Run Local Job (8.1 Suite)
This is the cherry pick of #5494.
@ricardosilva88 @cravobranco

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -B -fn -f 'pom.xml' -pl 'ui,engine,core' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'ui,engine,core' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  core/src/main/java/org/pentaho/di/core/ObjectLocationSpecificationMethod.java
  core/src/main/java/org/pentaho/di/core/util/StringUtil.java
  core/src/test/java/org/pentaho/di/core/util/StringUtilTest.java
  engine/src/main/java/org/pentaho/di/job/entries/job/JobEntryJob.java
  engine/src/test/java/org/pentaho/di/job/entries/job/JobEntryJobTest.java
  ui/src/main/java/org/pentaho/di/ui/job/entries/job/JobEntryJobDialog.java
  ui/src/test/java/org/pentaho/di/ui/job/entries/job/JobEntryJobDialogTest.java

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes (click to expand)
org.pentaho.di.job.entries.evalfilesmetrics.JobEntryEvalFilesMetrics

Branch Change: -0.4% :small_red_triangle_down:
Complexity Change: -0.5% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.job.entries.job.JobEntryJob

Branch Change: -7.7% :small_red_triangle_down:
Complexity Change: -8.6% :small_red_triangle_down:
Instruction Change: -15.9% :small_red_triangle_down:
Line Change: -16% :small_red_triangle_down:
Method Change: -22.7% :small_red_triangle_down:

org.pentaho.di.trans.steps.calculator.CalculatorMetaFunction

Branch Change: -8.7% :small_red_triangle_down:
Complexity Change: -3% :small_red_triangle_down:
Instruction Change: -0.7% :small_red_triangle_down:
Line Change: -0.9% :small_red_triangle_down:

org.pentaho.di.trans.steps.datagrid.DataGridMeta

Branch Change: -2% :small_red_triangle_down:
Complexity Change: -1.7% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:

org.pentaho.di.trans.steps.groupby.GroupByMeta

Branch Change: -2% :small_red_triangle_down:
Complexity Change: -2.1% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:
Line Change: -0.7% :small_red_triangle_down:

org.pentaho.di.trans.steps.singlethreader.SingleThreaderMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.tableoutput.TableOutputMeta

Branch Change: -0.9% :small_red_triangle_down:
Complexity Change: -0.8% :small_red_triangle_down:

org.pentaho.di.trans.steps.textfileinput.TextFileInputMeta

Branch Change: -0.5% :small_red_triangle_down:

org.pentaho.di.trans.steps.webservices.WebServiceMeta

Branch Change: -1.7% :small_red_triangle_down:
Complexity Change: -1.2% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.salesforceinsert.SalesforceInsertMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.salesforceupdate.SalesforceUpdateMeta

Instruction Change: -0.2% :small_red_triangle_down:


Unity3d permission error

Issue description
Unity seems to have some thoughts on the sandbox file's permissions:
Chromium Embedded Framework requires that the file '/nix/store/r911yc6y8yvw9s5ifrf7sxlgavzkc5qh-unity-editor-5.3.5f1/opt/Unity/Editor/chrome-sandbox' is owned by root and has permissions 4755.

Steps to reproduce
% nix-shell -p unity3d --command unity-editor

Technical details

System: 1fa75a5bb7cdb9f2413d8b20726ce69523bfe4c6
Nix version: 1.11.4
Nixpkgs version: "17.03.git.b02e6cc70d"

You need to install Chromium SUID binary (security.chromiumSuidSandbox.enable = true;).

Thanks, that works! Is this documented somewhere?
Nikolay Amiantov<EMAIL_ADDRESS>writes:

You need to install Chromium SUID binary (security.chromiumSuidSandbox.enable = true;).
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/NixOS/nixpkgs/issues/21579#issuecomment-269967595

--

Nope. I'm not sure where exactly we want to document this to be visible enough -- any ideas?


Splitter MK1 missing

I thought splitters had a different progression route but then discovered that the mk1 splitter is missing from this. Any assistance would be great


No null check for input params

https://github.com/alibaba/testable-mock/blob/f64b07e9da0e0644108ba6145eee7ed343c325bf/testable-core/src/main/java/com/alibaba/testable/core/accessor/PrivateAccessor.java#L22-L30

Not actually needed. For private accessor, if user ask to access a field of null or from a null instance, just let the NullPointerException goes, that's what should happen : )


android arm64 support

It seems that android arm64 (AKA aarch64 / arm64-v8a) is the standard now (meaning you cant technically use this library for android). I suppose adding support for it is as "simple" as https://github.com/veandco/go-sdl2/commit/cd80a890a1854d8ec41d8815948b110ac7691709
I would do it myself but I'm guessing you already have SDL cross-compiling set up (which does not exactly seem trivial according to SDL's docs). Seeing how I have no experience compiling C libraries I'm not sure I would figure it out in any reasonable timeframe. Anyhow if you are able to somewhat easily do this, I will do the testing of it for you, and also update the android example (which is really outdated).
If you don't have time for this, maybe you could point me in the right direction?

I just found https://github.com/veandco/sdl2-static-library-build-scripts
I can probably work with that.

Ahh sorry, I haven't managed to finalize the scripts. I will push what I have now tomorrow so it will be more up-to-date.

No worries. I'm thinking that library might be good for me to practise my github actions skills. If you would be interested in an automated solution? I have gained some experience with docker recently which I could put to use to have github produce the static libs.
I noticed that it's set up for the older android NDKs though, which I am not sure if supported arm64 (new ones use LLVM and is much easier to configure). In any case I can take care of updating that at the same time

That would be extremely helpful! I have met a couple stumbling blocks in building for android and darwin arm64 architecture so I greatly appreciate any help on those matters!

I started working on it: https://github.com/veandco/sdl2-static-library-build-scripts/pull/1 Now it should be possible to build using that container. No time for that today though ;)

Thanks @Lundis! I have also pushed the current state of the repository which may have affected the list of packages installed in the Dockerfile.

Hey there! Any progress on this? I was trying to build an SDL app for an aarch64 linux embedded system and getting an error:
# error "No ABI matched"
I'm assuming this is because there are no SDL libs for this platform. I'm happy to compile them myself if there are some instructions, but I haven't been able to find any.

Hi @n-i-x, you could try downloading the latest SDL2 library from GitHub at https://github.com/libsdl-org/SDL/releases
After extracting it, you could build it like this:
cd SDL2-2.24.0
mkdir build
cd build
../configure --prefix=$HOME/.local
make -j`nproc`
make install

and then make sure pkg-config can find it by setting the environment variable:
export PKG_CONFIG_PATH="$HOME/.local/lib/pkgconfig:$PKG_CONFIG_PATH" # perhaps put this in .profile or .bashrc
pkg-config --cflags sdl2 # to test if pkg-config can find it

After that, I believe you should be able to use the binding.

I don't think that'll let me statically compile though will it? I have all the .a files from the device I'm targeting and tried adding them to the repo... but it couldn't find them. Not sure what I missed.

FYI, I tried compiling SDL 2.0.7 (the version included in the embedded device) using your instructions and then building one of the examples and I get the following error:
$ GOOS=linux GOARCH=arm64 go build main.go
# command-line-arguments
./main.go:6:16: undefined: sdl.Init
./main.go:6:25: undefined: sdl.INIT_EVERYTHING
./main.go:9:12: undefined: sdl.Quit
./main.go:11:21: undefined: sdl.CreateWindow
./main.go:11:46: undefined: sdl.WINDOWPOS_UNDEFINED
./main.go:12:17: undefined: sdl.WINDOW_SHOWN
./main.go:24:14: undefined: sdl.Rect
./main.go:30:20: undefined: sdl.PollEvent

I've tried go mod tidy and go get -v github.com/veandco/go-sdl2/sdl and it sill gives me that error. If I don't try to cross-compile then it works fine.

@n-i-x That is because you need to explicitly enable cgo with CGO_ENABLED=1, Go will by default disable cgo when ever you try to cross-compile. It is a common error when one wants to cross-compile a cgo project just like that.
When you add CGO_ENABLED, the next error will probably be something that tells you that you must use the C compiler/toolchain for the target architecture, i.e. to set CC. Btw. you must also compile SDL with the same toolchain, not with your host CC.

Okay I tried all of that except compiling sdl with the aarch64 gcc I’ll try that next and report back.

$ export PKG_CONFIG_PATH="$HOME/.local/lib/pkgconfig:$PKG_CONFIG_PATH"
$ pkg-config --cflags sdl2
-D_REENTRANT -I/config/.local/include/SDL2

Then when trying to cross-compile I get the following:
$ CGO_ENABLED=1 CC=aarch64-linux-gnu-gcc GOOS=linux GOARCH=arm64 go build -tags static -ldflags "-s -w"
<snip>
/usr/lib/gcc-cross/aarch64-linux-gnu/9/../../../../aarch64-linux-gnu/bin/ld: /tmp/go-link-1068906841/000042.o: in function `delHintCallback':
/config/go/pkg/mod/github.com/veandco/go-sdl2@v0.4.25/sdl/hints.c:18: undefined reference to `SDL_DelHintCallback'
/usr/lib/gcc-cross/aarch64-linux-gnu/9/../../../../aarch64-linux-gnu/bin/ld: /tmp/go-link-1068906841/000043.o: in function `LogSetOutputFunction':
/config/go/pkg/mod/github.com/veandco/go-sdl2@v0.4.25/sdl/log.c:5: undefined reference to `SDL_LogSetOutputFunction'
collect2: error: ld returned 1 exit status

Is there something I need to do to make sure cgo can see the the libs in ~/.local? I have PKG_CONFIG_PATH="$HOME/.local/lib/pkgconfig:$PKG_CONFIG_PATH" exported. I'm also trying to compile SDL 2.0.7 which is the SDL included in the embedded device I'm working with, would I need to use a more updated SDL? I would assume if I am statically compiling against those SDL libs the SDL version wouldn't matter, so I'll try that next.

I also wonder if I just need to compile SDL -image,-mixer,-ttf,-gfx to get all the references needed by the bindings... I'll make my way through compiling those libs for aarch64 as well. I really appreciate you helping me through this.

Hi @n-i-x, the SDL2 build instructions written above are for dynamic compilation as we don't have static libraries for android arm64 yet. There shouldn't be a need to install the other SDL2 libraries such as SDL2_image if only sdl is imported.


Fix/plugin build

[x] plugin-docusaurus: update docusaurus version and remove react/react-dom from devDependencies
[x] plugin-docusaurus: use _createElement as praga which is exported by hijackCreateElement to support rpx
[x] plugin-rax-component: external helpers
[x] pkg: add install @swc/helpers warning if needed
[x] pkg: update externals default value from true to false and update doc

@ChrisCindy

可以 check 下为啥站点构建挂了, 一般来说是 md 文件引用路径错了, website 目录本地用 yarn 安装依赖


perf: inline gather_transitive_sources+gather_transitive_types into _js_library_impl

This change itself doesn't really bring much value and probably no perf gains, but allows https://github.com/aspect-build/rules_js/pull/1787 which may have gains
…

Changes are visible to end-users: no
Test plan

Covered by existing test cases

Moved into single PR which depends on this: https://github.com/aspect-build/rules_js/pull/1787


Improve double-import CSS

This improves our asset hashing code so that it makes fewer assumptions about the presence of a CSS hash, and so that it exposes a function that sub-themes could use to hash their own CSS/JS assets! Also adds some docs about this so others can discover it.

This un-breaks a bug that causes sub-themes to fail, so I'll merge this one if the tests are happy


Is Resize3D supported?

Is Resize3D supported?

Please check https://github.com/Tai-Wang/Depth-from-Motion/blob/ad167ac2a7cbf37df3e85417e6ca1cdf37d42f5d/mmdet3d/datasets/pipelines/transforms_3d.py#L2103

You can first refer to the provided implementation and we will support it in the next version.


Build Command

Hi there,
Which is the difference between this two command:

./vendor/bin/jigsaw build production && npm run production?

I have deployed a site on Netlify and I'm using a function which is served with netlify-lambda build <folder>.
Now I have to attach this command to the build production. Could you someone help me with that?
The documentation says that you guys use this approach to deploy on Github pages but I can't see anything that explains the difference between this two command.
Maybe there is no different, but I'm new so please be patient.

./vendor/bin/jigsaw build production runs Jigsaw's build command to create the production files for your site, but it doesn't run any npm scripts—meaning if you have any asset compilation steps to run (e.g. running CSS through a pre-processor like Less or Sass, or compiling JS), build will not run those.
npm run production runs the production script that's in package.json, which triggers webpack and runs your asset compilation, as well as running ./vendor/bin/jigsaw build.

So:

./vendor/bin/jigsaw build => builds site files only
npm run production => processes assets & builds site files

@damiani thanks for your fast reply.
Now it's more clear to me and very useful too,
Thanks.


Adjust GeneratedAdventureWorks to changed fromDbAndScripts type

It was changed in https://github.com/oyvindberg/typo/commit/a1488547fc349a8d23a1e4dd86fa9d9da15044bb

Lovely! This one time I tried to push to main without PR and this is how it went :D