Why Do we Need Pre-Computed for Test Images

Hello @Brummi, I was trying to run inference using scripts/images_decomposition_co3d.py, however, it looks like the code always relies on precomputed stuff e.g., depth, albedo, normal map etc. For example when running for the category = 'bench', the test_path_precompute is always set to 'datasets/co3d/extracted_bench/precomputed/val' and inspecting the dictionary (data_dict) shows all the tensors are already set essentially to non-zero values:
print('data_dict.keys(): ', data_dict.keys())
print(data_dict['input_im'].shape)
print(data_dict['recon_albedo'].shape)
print(data_dict['recon_depth'].shape)
print(data_dict['recon_normal'].shape)
print(data_dict['recon_normal'][0,0,:10,:10])

Shouldn't the test image be run without relying on any pre-computed inputs and just the single RGB image? as that is the perception I had reading the paper. All these tensors should be initialized to zero except the input_im. May be having a single minimum inference example can help here: loading the model and running inference for a sample face/object image.

Hi,
in this codebase "precomputed" and "extracted" correspond to the ground truth. You can set the corresponding path to None (as for the photos category, where I run the model on pictures I took with my phone) and they will not be loaded. The model does not rely on them during inference.
As the loss is calculated as part of the forward step, we pass this data with data datadict to the model. Within the model class at line 375, all these dict items get the prefix "lr_" for low resolution or coarse. In the visualization script, we load this data to show the comparison. They get plotted / saved from line 248 in the decomposition script onwards.
If you want to run the method on custom data, you actually just do it the same way I did with the photos. I think you should put the image under datasets/photos/imgs_cropped/val.

Thanks you for the detailed explanation! That path suggestion worked well for me.

Looks very cool!


Adding resources as per #384

Fixes Issue

Changes proposed

Screenshots

Note to reviewers

Added solana development project playlist


Add Solidity language heuristic

I added an entry to lib/linguist/heuristics.yml for .sol files. It checks a pragma that the vast majority of Solidity files have.
My understanding is that .sol wasn't already associated with Solidity, as it's commonly used for solutions in competitive programming environments. Luckily, most Solidity files have a program indicating the version of the language, as not including it leads to a warning. This makes creating a heuristic simple and safe.
Checklist:

[x] I am associating a language with a new file extension.

[x] The new extension is used in hundreds of repositories on GitHub.com

Search results for each extension

[x] I have included a change to the heuristics. to distinguish my language from others using the same extension

Thanks for the quick response, @pchaigno.
My understanding now is that any heuristic that associates .sol with Solidity can't be merged until one of these things happens:

The not-a-language feature is implemented.
I add heuristics for every language that uses .sol as an extension.

Is guess (1) is a major endeavor, and maybe not a good fit for being implemented by an external contributor. Is it?
If I were to go on with (2):

Do I have to create heuristics for any kind of .sol file that I find on Github, or just the ones that have language definitions in Linguist?
Is there a way to download every file with a given extension? Using the API maybe?

Is guess (1) is a major endeavor, and maybe not a good fit for being implemented by an external contributor. Is it?

Unfortunately, I would tend to think this is true for both (1) and (2). Both will require a lot of work and are likely hard to undertake as a first contribution.

Do I have to create heuristics for any kind of .sol file that I find on Github, or just the ones that have language definitions in Linguist?

We usually add support for all languages that (1) use an extension we're adding support for and (2) meet our requirement on in-the-wild usage (i.e., hundreds of repositories).

Is there a way to download every file with a given extension? Using the API maybe?

I don't know of a way to download all files with a given extension, but you can use Harvester to download all files returned by a given search query.

Please let me know if there's anything else I could match in older Solidity files that's unambiguous.

I don't think so. The other top-level constructs, apart from contract, weren't present in versions of Solidity without pragma.

Throughout Linguist's source code, we assume the list of extensions in languages.yml to be the source of truth in terms of what extensions we support. We refer to that list to know what to test, to find conflicts, to determine aliases... and to detect languages of course. I would really prefer to have all extensions we support listed in there.

I don't think that justifies the complexity involved with adding a new strategy or languages field. Especially when the underlying problem isn't really solved: Linguist still has no way of explicitly returning nothing.
Solutions I've considered:

Adding an isolate field to languages.yml to exclude an entry from candidate lists unless a strategy explicitly requests it. This is the approach I decided to implement before testing this PR for myself.
Adding a new heuristic strategy that isn't named Heuristic (since that's already taken 😜). Ditched the idea because it would repeat things other strategies already handle. Specifically, matching content and file extensions: that's already the job of our Heuristic and Extension strategies, respectively.
Adding a minimum_certainty field to languages.yml, where matches are required to score highly enough in the Bayessian classifier to be returned. Confidence would be be derived from tokenisation metrics (those displayed when LINGUIST_DEBUG=2 is set in the environment). Ditched the idea because:

Many smaller and less blatant files would slip through the cracks, causing some files to be recognised but not others
Setting the threshold requires some knowledge of how the tokenisation process works
Come on. We both know why this is a bad idea. 😉

Sorry @Alhadis but I agree with @pchaigno here. This doesn't feel like the right solution and whilst solves the immediate problem, it's likely to lead to confusion and inconsistency later.
I'm short on ideas—I've pondered this all day yesterday—but short of implementing the whole not-a-language idea (I'm not sure this will really solve our problems now I've thought about it due to all the complications that come with it), the best option I can think of for now might be to add support for the most prominent .sol extensions as best as we can.
Linguist has never professed to be perfect in matching languages, but "good enough" should do for most cases. Overrides exist for this reason and most current .sol files won't change until the repo changes.

I've pondered this all day yesterday

So did I. 😂 It's amazing how difficult it is to think of a satisfactory .solution to our problem.
I guess a bespoke Linguist::Strategy::Solidity is really the least awkward way of fixing this.

I guess a bespoke Linguist::Strategy::Solidity is really the least awkward way to do this. I trust you'd have no objections to a PR to add such a thing…?

I think that's starting down a dangerous road of creating a new strategy for each language that uses a very popular or generic extension.

The only other thing I can think of is a require_heuristic field in languages.yml that requires a heuristic to match in order for the extension or filename strategies to pass.

Just for the record, our heuristics are already assigning languages for extensions they're not associated with (e.g., INI → .props, .builds → Text, probably others).
The PR I'm preparing will address this by requiring heuristics to reference extensions in-use by their candidate languages.

#4936

Just for the record, our heuristics are already assigning languages for extensions they're not associated with (e.g., INI → .props, .builds → Text, probably others)

Those are bugs as far as I can see. We should probably have a test to ensure all extensions in heuristics.yml are listed in languages.yml. I always assumed that was already the case :-/
They were both merged in 2016 when we weren't as careful on these things: #2866 and #2954.

I already included a test for this as part of #4936

Closing in favour of #4936 (and so @stalebot will STFU).


PHOENIX-4728 The upsert select must project tuples

No the problem come from the querycompiler for the upsertselect the behavior is different than a simple select query
Le 23 mai 2018 16:04:46 HAE, James Taylor<EMAIL_ADDRESS>a écrit :

JamesRTaylor commented on this pull request.

@@ -549,7 +549,7 @@ public MutationPlan compile(UpsertStatement
upsert) throws SQLException {
select = SelectStatement.create(select, hint);
// Pass scan through if same table in upsert and select so that
projection is computed correctly
// Use optimizer to choose the best plan

       QueryCompiler compiler = new QueryCompiler(statement,

select, selectResolver, targetColumns, parallelIteratorFactoryToBe, new
SequenceManager(statement), false, false, null);

       QueryCompiler compiler = new QueryCompiler(statement,

select, selectResolver, targetColumns, parallelIteratorFactoryToBe, new
SequenceManager(statement), true, false, null);
This seems like too general of a change for the specific issue you're
trying to fix for ARRAY_APPEND. I'm also not sure why it would impact
it. Can't you make changes to ArrayAppendFunction or it's base class to
get the desired affect?
Any opinions, @maryannxue. Do you remember when/why we need this
projectTuples boolean for QueryCompiler?
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/phoenix/pull/301#pullrequestreview-122745792

--
Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté.


Updated link to Advanced Statistical Computing Course

Hi there,
I was going through some of the links and noticed the link to the to the Advanced Statistical Computing as course was broken. The course name has been updated from BIOS366 to BIOS8366 and this reflected in the link that I've made changes too.
I hope this is of some help as it's a great resource.
Mark

Very helpful, thank you Mark!


A little bug in decode code while restoring ckpt

Checkpoint saves files from index 1 by default, whereas the restoring code read ckpt file from index 0.In the athena/decode_main.py, the 55th line code could be modified with 'ckpt_path = p.ckpt + 'ckpt-' + str(idx + 1)'

Thanks for spotting this out. We will make a pr to fix it.


feat(inspector): implement console in the runtime. fix console logs in devtools inspector (#884)

Prerequisite - PR https://github.com/NativeScript/android-runtime/pull/893

Fixes #884 Console logs not displaying properly in the Console panel inside Chrome Devtools of Chrome 62 and later versions.
Fixes https://github.com/NativeScript/nativescript-cli/issues/3158 - console.log sources are not shown, making debugging of external libraries more difficult for users.
As a result of the fix above the scripts now display the source where the console methods were invoked (right hand-side).  A timestamp of when they've been logged is also displayed.

Another major change that occurred as part of the fix was refactoring of the console.js script, which previously resided in the tns-core-modules - which is now implemented in its own Console module as part of the NativeScript Android Runtime implementation - this eliminates the need for special checks, if-clauses and weird workarounds needed in the tns-core-modules code base to make script work in all cases.

The implementation of log, warn, info, error is such that they can now print a list of consecutive values, while the current implementation could only print 1 value at a time per call.
Currently a normally valid call to console.log() such as console.log(5, 12, "redundantString", { a: "Pesho", age: 22 }); would fail.
The new implementation would print 5 12 "redundantString" { a: "Pesho", age: 22 }, similar to what a nodeJS, or browser application would print out.

As a result of the refactoring the strings passed as arguments to console.log() and the likes will no longer support c-string-like format strings (%d, %s, etc.) interpolated with values from the argument list following the primary arguments to the log(..) call. - Users whose logs depended on that feature should migrate to using JavaScript template literals (backtick strings) - https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Template_literals

As part of the implementation, if an object is console.log()ed , the new implementation will JSONStringify the object now, instead of transforming it into [object Object]

console.time() and console.timeEnd() will work without passing them any arguments, default will be the identifier used in that case.

Tested with Chrome DevTools, and the VSCode extension in the most basic scenarios.

@Plamen5kov please review the changes

run ci

run ci

run ci

run ci

run ci

I found an error where the JSON.stringify inside the object transformation would crash the application if it tries to stringify an object with a circular reference. Will fix it before merging


MM-33580 Granular Data Retention

Summary
Add support for granular data retention on mobile.
Ticket Link
https://mattermost.atlassian.net/browse/MM-33580
Device Information
This PR was tested on: iPhone 11 Simulator, iOS 14.4
Release Note
Adds client support for the granular data retention policies

/update-branch

@anurag6713 tests are failing

@enahum .. had a lint error and it's fixed now.

@enahum https://docs.google.com/document/d/1BFzKdytL0YLSMbMOoLRaLuVORQZRwXrcD1dOovdCnaI

@anurag6713 have we tested this changes against an old server ?

Tested it on 5.34 branch, master branch and the feature branch. Is there any specific or breaking version we need to test against?  @enahum

@anurag6713 always with ESR

@anurag6713 Have we tedted against 5.31.3?

@Elias I have tested this against 5.31.5.

@furqanmlk I saw your test results, did you test multiple granularity in teams, channels and global?

@furqanmlk I saw your test results, did you test multiple granularity in teams, channels and global?

Hi @enahum
I am doing details testing in this PR https://github.com/mattermost/mattermost-server/pull/17417
for this PR Yes, I have tested Team, Channel and Global Policies, there is some issues in Global policy that I have updated in server PR.

@enahum I've added this tentatively to v1.44 as this feature may be shipping in v5.36 (June).

@amyblais why this got removed from the 1.44 release ?

@enahum I'm 0/5 but the feature is not in v5.36 yet.

@amyblais got it, thanks

@enahum I'm 0/5 but the feature is not in v5.36 yet.

If it's true, we might have to update code where we check for the server version.

@anurag6713 then I guess updating the server version is required, can you confirm?

Also mention the required server version in the release notes

@anurag6713 Kind note to merge this PR, unless you know of something blocking this PR.

@amyblais Confirmed the server version. Merging it now. Thank you 🙂


Performance benchmarks?

Are there any benchmark results now? Looking forward to performance comparisons with original attention, and official torch+CUDA implementation.

I am also curious, additionally maybe it is possible to use cuda code with jax ?
https://github.com/dfm/extending-jax

https://colab.research.google.com/drive/1-YCU9ps4gNuROJ3_8MLjSpbICGHaySxh?usp=sharing

Fantastic have you done experiment with the same data on original flash attention ?

Not yet

Hello, could I ask if this works with TPUs?

Here's an updated notebook that precompiles jit and blocks results until ready for anyone interested:
https://colab.research.google.com/drive/1-YCU9ps4gNuROJ3_8MLjSpbICGHaySxh?usp=sharing
Looks like JAX compiles vanilla attention in a way to be faster than flash attention, so no need to change to flash attention if you use JAX.

Wow this is open from almost a year ago...
I think someone could get a lot citations / clicks if they did a proper benchmark of transformer train/inference across platforms torch/jax GPU/TPU with standard tricks. I would cite you straight away for sure. It would also just be nice to settle this dispute that Google employees seem to have with everyone else, whether or not Jax is meaningfully more efficient or not (might just be up to TPU or GPU!?).

Wow this is open from almost a year ago...
I think someone could get a lot citations / clicks if they did a proper benchmark of transformer train/inference across platforms torch/jax GPU/TPU with standard tricks. I would cite you straight away for sure. It would also just be nice to settle this dispute that Google employees seem to have with everyone else, whether or not Jax is meaningfully more efficient or not (might just be up to TPU or GPU!?).

Would be definitely nice to see such benchmark, but I can imagine how hard is comparing JAX vs PyTorch (GPU/TPU), with many optimized implementations for each device. For PyTorch with GPU we have Triton/CUDA, but JAX recently has also added Triton-like mechanism for writing custom Kernels with GPU/TPU - Pallas. You can even find implementation of attention in it here.

@niemiaszek I just recently saw they named and added docs for pallas, looks very interesting. JAX is also improving our ability to customize how networks are sharded across accelerators and are publishing papers on their results wrt efficiency, pretty cool I think. Unfortunately I don't have time to do a fair comparison between torch and jax with attention but it seems that whoever takes the time to delve into it, especially jax's recent improvements, would certainly benefit if they have a need.
Even if we don't take the time, it looks like the jax team continually adds their efficiency findings into jax as defaults so we don't have to implement ourselves.

from what i've heard, flash attention doesn't work well on TPUs
Pallas is just a wrapper around Triton, developed at OpenAI for GPUs.

while this is a hard pill to swallow, i think existence of flash attention is a clear victory for having finely controlled GPGPU programming.

@lucidrains I'd agree as far as single-device optimizations go. I solely use jax because my work deals mainly with RL and I've already built everything out, but for things like language and vision models, resources like xformers are hard to beat. I do like jax's work toward multi-device customization especially from an RL perspective.

while this is a hard pill to swallow, i think existence of flash attention is a clear victory for having finely controlled GPGPU programming.

Well, I would argue that in this day, that's no longer such a hard pill given the wide adoption (torch - both codegen + incoming custom kernels, JAX - e.g. Pallas, hardware vendors including NVIDIA, AMD, Intel) of tiled programming paradigm like Triton which greatly reduces the effort and complexity of getting SOTA perf on GPUs.

@jon-chuang hmm, still a bit early to declare that imho
we'll see, i hope so!

I think these newish attention replacements will take time to be adopted particularly because the dust has not settled on them and it takes a while for wide-scale experimentation and large-scale training with them to truly prove them out.
IMO all it takes is a leap for a highly-funded industrial lab to go out on a limb and train an LLM with one of these...
For instance, Mistral AI essentially has a linear cost attention mechanism based on SWA - sliding window attention - one could argue of course how effective it is at truly capturing information across long context.

all these frameworks cannot do.

I think this is an overstatement? I think it simply has not been tried out in Triton yet. But it should not be that hard. But whether the performance matches is an open question.
I just hope that more devs become aware of how powerful triton is so that there's more experimentation with implementing these kernels.

@jon-chuang the author told me he couldn't get it to work with Triton.

@jon-chuang yea, let us just agree that we both wish for Triton and the like to succeed so us non-CUDA experts can have control over the entire stack

Interestingly, a basic building block for Mamba (associative scan) already has support in Triton: https://github.com/pytorch/pytorch/issues/95408#issuecomment-1653748896

@jon-chuang anyways, let us take the discussion elsewhere, as this is about flash attention

Flash attention is now available in jax-nightly with a cudnn implementation: jax.nn.dot_product_attention. It only supports Ampere architecture and later.
Note that the default is xla.


Lineage Stage 0

Closed #24 in favor of this one
This is an RFC describing the first iteration of Lineage related work.

@danwom use this one instead

the png in https://github.com/amundsen-io/rfcs/blob/59bd5b98c15e823fcf1757fcd5ff97790e215dae/rfcs/025-lineage-stage-0.md doesn't seem to work

I will take a look tonight

@danwom @allisonsuarez here is the preview (https://github.com/amundsen-io/rfcs/blob/59bd5b98c15e823fcf1757fcd5ff97790e215dae/rfcs/025-lineage-stage-0.md) . Could you update and fix the broken image links? thanks


travis: does not test py3

the .travis.yaml file is configured wrong (not the correct python version is tested...)

finally...


NCBI Taxdump Parser

[ ] get taxdump from ftp://ftp.ncbi.nlm.nih.gov/pub/taxonomy/

[ ] parse nodes.dmp and names.dmp

[ ] return a tree structure

[ ] tree can contain a map of taxId to taxonNode

The files are too large to upload on Github.
Should I upload them in a res folder like in the following?
https://git-lfs.github.com

@Zethson
Then no need to push them. Git LFS has a bandwith quota of 1GB per month. If all of us pull them, we'll already exceed it.

I see, good to know. But how should we get the files then? I thought that we would provide them in the res folder, because they are required for building the tree. The user shouldn't have to provide those two files to my mind.
Or will we simply just not push them?

We can think of this in future. But simply we can have an install script, which will download, extract and place them in the correct folder.
Right now we don't even have a main class yet. When we start building up one, we will discuss where and how to store those files by default.

All right, thanks!

So I just committed a resources folder - can you all put your 'names.dmp' and 'nodes.dmp' files right into that folder (without adding them to git)? That way, we can all use the same filepath for them without actually having them up in the repository.


Fix failing auto_mixed_precision test

The test, TEST_F(AutoMixedPrecisionTest, FusedBatchNorm), compares FP16 (emulated in Eigen when run on CPU) with float32 results. It is well known that float32 addition is not associative, so difference in results between different implementations is possible. Even using different number of threads leads to different values of variance computation (a part of FusedBatchNorm computation) as the reduction happens in different sequence.
Moreover, if we change the input shape to {1, 28, 28, 4} or {8, 28, 28, 16} and many others, even the Stock TF fails (i.e. with TF_ENABLE_ONEDNN_OPTS=0). Given these, we think it is appropriate to increase the rtol

Is this test failing at head right now that it needs a fix?

@rohan100jain : when oneDNN is enabled with the environment flag TF_ENABLE_ONEDNN_OPTS=1, then this test fails.
--config=cuda enables this test. Now, with config=cuda and oneDNN enabled, the test fails on CPU. And I put our analysis in the PR description above.


Updated build to fix bug introduced yesterday

Updated build to fix bug introduced yesterday. Implementation is now as follows:
MPI and BLAS implementations are by default user specified. If they are not specified, build defaults to no MPI implementation. For BLAS CMake first searches for the appropriate implementation depending on the system, and if nothing can be found it defaults to ATLAS.
Users must now specify the bin and root paths for their MPI installation should they be using it. If these are not specified, CMake will throw an error.

I left a comment in slack, but just to reiterate here for documentation purposes:
In our meeting today Dmitry said that the only thing that ExaTensor needs is the root directory for the user's MPI installation. Given our discussion today I’ve modified the CMake files to do the following:
-Users can input MPI or BLAS information. If they input MPI info, they must supply the implementation and the root directory for their install. If they don’t supply these, then exatn defaults to no MPI implementation. The CMake file also checks that both the root directory and the implementation are supplied; if not, an error is thrown.
-Similarly, the user can supply a BLAS implementation. After talking with Dmitry we decided to make it as transparent as possible, such that if no BLAS implementation is given by the user, exatn defaults to no BLAS implementation. This way there is nothing CMake is doing "behind the scenes" that the user may not necessarily know about.


AsyncExecution.completeOrRetry is not invoked when Error is thrown.

If async code throws AssertionError, OutOfMemoryError, or any other non-Exception Throwables, AsyncExecution.completeOrRetry is not invoked, which has some negative consequences:

It's not possible to use Failsafe in a testing context where AssertionError might be something you want to, for example, abort on.
It leaves things in an indeterminate state -- the FailsafeFuture never completes.

The solution would seem to be simple: catch Throwable instead of Exception where the exception is handed off to completeOrRetry. The changes seem confined only to the methods in Functions.

Submitted pull request: https://github.com/jhalterman/failsafe/pull/77 (I'm sure there's a more elegant way to do it...)

@awallgren - IMHO, I think Throwable or Error should not be catch.
In most case, when an error occurred, that implied the application was turned into some unexpected and fatal situation that was hard to recover.
If we try to recover from that situation, the application would result with an inconsistent and unknown state and will hard to evaluate what was happened.
What do you think!

@chhsiao90 - I can think of use cases where it's quite legitimate to want to involve non-Exception Throwables (most likely Error and its descendants, but I've seen code extend Throwable instead of Exception), and don't agree that "most cases" imply application problems.
First, it seems that it's the intent of Failsafe is to support this:

This is how synchronous code in Failsafe works -- SyncFailsafe.call catches Throwable and calls Execution.complete. I see no reason why the async code should be different.
Most of the API uses Throwable, e.g. RetryPolicy.abortOn accepts Class<? extends Throwable>, not Class<? extends Exception>.

Some use cases:

What triggered the question on my part is that I want to run some async code as part of JUnit tests. I want to use RetryPolicy.abortOn(AssertionError.class) to capture any assertion from the async code but have it retry under other conditions.
Third party code sometimes extends Throwable instead of Exception in their checked exceptions (e.g. maven-core).
Some parts of the JDK do this as well -- for example, java.util.zip.ZipError
It seems quite legitimate to want to handle OutOfMemoryError and perhaps retry in a way that consumes less memory.

@awallgren - Thanks your reply!
That was reasonable.
It's sound that there is still need the flexibility to let the user can handle with Throwable that was not extended Exception.
And if the sync version had the logic, then there is no reason to have different logic!

Hi @awallgren -
My intent with Failsafe, though maybe I didn't fully achieve this, was to favor the handling of Exceptions over Throwables (the various net.jodah.failsafe.function types throw Exception rather than Throwable) rather than Throwables or Errors since, as the Error docs mention, errors should not really be caught since an error represents something horrible having happened that can't reasonably be recovered from.
That said, handling AssertionError certainly sounds like a reasonable use case, at least for testing. I'm surprised to hear of Failsafe being used in testing, but hey, that's cool. Is that the only use case you have? Can you provide a little example or test that demonstrates how you're using it in this way?

This is how synchronous code in Failsafe works -- SyncFailsafe.call catches Throwable and calls Execution.complete. I see no reason why the async code should be different.

This is a completely valid point, so I'd like to at least improve things in this way. But first, help me understand your use cases a bit more if you can...

@jhalterman -- Thanks for the quick response.
It's true that the Error docs imply that Error should never be caught, though the wording is weaselly enough ("reasonable applications", "most such errors") that I would argue that's not a hard and fast rule in this context.
In addition, the facts on the ground are that existing code does throw Error in cases where it's necessary/appropriate for the caller to catch it. For example, the JDK itself: java.io.Console.readLine catches IOException and rethrows it as IOError, presumably in a misguided attempt to avoid declaring IOException on readLine (surely the authors didn't intend that any application using that class should exit the thread/process rather than handle Console problems).
Also, this only covers Error, not other descendants of Throwable, as I mentioned above, with Maven and the JDK itself.
Further, the very nature of Failsafe is such that it's very handy for dealing with "exceptional" circumstances - though perhaps the appropriate word should be "throwable"...
As for my actual use cases, I have two off the top of my head:

I'm testing my own use of Failsafe around some async code that uses retries/circuit breakers and in this context I want AssertionError to cause an abort in Failsafe, so I configured the RetryPolicy to abort on AssertionError. When I wrote tests for this code, the abort never happens since the AssertionError is not caught, so the FailsafeFuture never completes.
In certain cases, we do want to catch OutOfMemoryError and retry (or at least recover with some contextually appropriate error). For example, some JDBC drivers (rhymes with Sporacle...) have a propensity to allocate large amounts of memory and it's possible for that to trigger OOME in large-scale very busy servers. Since the resulting OOME doesn't always happen on the thread that allocated the memory, we want to handle OOME, flag a low-memory condition in the process, and retry the code that received an OOME but wasn't really the cause of the problem.

That last one is a bit long, but is probably the more relevant one.

@awallgren I think your pull request did resolve this. I also added a few tests. Let me know if anything else related to this pops up.

Thanks for adding the tests -- I should have done that myself before the pull request.
Keep up the good work -- I love dropping in useful libraries like this and deleting my own crufty code that tried to do the same thing, but  much less elegantly.

Thanks @awallgren. Feel free to spread the word about the project or give it a shoutout on Twitter or whatever :)
I just released 1.0.3 which includes this fix.


curl: (52) Empty reply from server

I send post request and got message 'curl: (52) Empty reply from server'.
I have built successfully and related container is up running, testing process should be OK.
This is environment and build process info.
1.dev environment
OS:Mac OS Sierra
Docker: Version 18.03.0-ce-mac60 (23751)

2./etc/hosts DNS.
<IP_ADDRESS>	auth
<IP_ADDRESS>	verify

2.docker compose ps
       Name                      Command               State                        Ports
---------------------------------------------------------------------------------------------------------------
backendauth_auth_1    /bin/sh -c npm start             Up      <IP_ADDRESS>:32782->3000/tcp, <IP_ADDRESS>:32781->4000/tcp
backendauth_redis_1   docker-entrypoint.sh redis ...   Up      <IP_ADDRESS>:32780->6379/tcp

3.docker-compose exec auth npm test
><EMAIL_ADDRESS>test /usr/src/app
> nyc mocha ./src/**/*.spec.ts

(node:91) Warning: process.on(SIGPROF) is reserved while debugging

  Application
    ✓ should return 404 and not contain X-Powered-By header
    ✓ should return 406 for unsupported Accept header
    ✓ should return 406 for unsupported Content-Type header

  Authenticate
    POST /auth
      ✓ should return 404 (54ms)
      ✓ should require login
      ✓ should require password
      ✓ should require deviceId
      ✓ should authenticate user (421ms)
      ✓ should respond with 403 error code when password is incorrect (416ms)
    POST /auth/logout
      ✓ should logout
      ✓ should respond with 400 code when logout with incorrect token
      ✓ should require token
    POST /auth/verify
      ✓ should be valid token
      ✓ should be invalid token
      ✓ should require token

  Tenants
    POST /tenant
      ✓ should create tenant (233ms)
      ✓ should not create tenant when email already exists (429ms)
      ✓ should require email
      ✓ should validate email
      ✓ should require password
      ✓ should validate password length
      ✓ should validate password format
      ✓ should use tenant IP whitelist
    POST /tenant/login
      ✓ should authenticate tenant (425ms)
      ✓ should not authenticate tenant with incorrect password (421ms)
      ✓ should not authenticate tenant with incorrect email (216ms)
      ✓ should require email
      ✓ should validate email
      ✓ should require password
      ✓ should validate password length
      ✓ should validate password format
    POST /tenant/logout
      ✓ should logout (424ms)
      ✓ should respond with error for incorrect token (429ms)
      ✓ should require token
    POST /tenant/verify
      ✓ should verify valid token (422ms)
      ✓ should respond with error for incorrect token (427ms)
      ✓ should require token

  Users
    POST /user
      ✓ should create user (210ms)
      ✓ should create user when additional fields are present in request (209ms)
      ✓ should create user when additional fields are present in request (209ms)
      ✓ should validate email
      ✓ should require email
      ✓ should require login
      ✓ should require password
      ✓ should require sub
    DELETE /user
      ✓ should delete user (209ms)
      ✓ should respond with 404 code if login is not found (42ms)
      ✓ should require login

  Auth Middleware
    Test Auth
      ✓ should require Authorization header
      ✓ should require Bearer
      ✓ should not auth incorrect token
      ✓ should not authorize non-tenant user
      ✓ should authorize tenant

  IP whitelist filter
    Test filter
      ✓ should respond with 403 if IP is not in whitelist
      ✓ should allow request if IP is in whitelist

  Request Throttler
    Test throttler
      ✓ should throttle
      ✓ should throttle white list IP

  jwtService
    #generate
      ✓ should return token
    #verify
      ✓ should verify token
      ✓ should verify token

  keyService
    #set
      ✓ should create session
    #get
      ✓ should return session
    #delete
      ✓ should delete session

  storageService
    #set
      ✓ should return "OK"
    #get
      ✓ should return value
      ✓ should return null
    #expire
      ✓ should return 1
      ✓ should return 0
    #del
      ✓ should return 1
      ✓ should return 0

  tenantService
    #create
      ✓ should create new tenant (220ms)
    #login
      ✓ should login tenant and return valid token (424ms)

  userService
    #create
      ✓ should create new user (221ms)
    #get
      ✓ should return user

  74 passing (16s)

------------------------|----------|----------|----------|----------|----------------|
File                    |  % Stmts | % Branch |  % Funcs |  % Lines |Uncovered Lines |
------------------------|----------|----------|----------|----------|----------------|
All files               |    98.47 |    81.73 |      100 |    98.37 |                |
 src                    |    95.77 |    73.33 |      100 |    95.71 |                |
  app.ts                |       90 |     62.5 |      100 |    89.66 |       16,17,20 |
  config.ts             |      100 |    77.27 |      100 |      100 |                |
  ioc.container.ts      |      100 |      100 |      100 |      100 |                |
 src/controllers        |    98.94 |       90 |      100 |    98.86 |                |
  jwt.controller.ts     |    97.56 |       90 |      100 |    97.44 |             67 |
  tenant.controller.ts  |      100 |     87.5 |      100 |      100 |                |
  user.controller.ts    |      100 |      100 |      100 |      100 |                |
 src/middlewares        |    97.53 |    88.24 |      100 |    97.53 |                |
  auth.ts               |      100 |      100 |      100 |      100 |                |
  ip.whitelist.ts       |    91.67 |    66.67 |      100 |    91.67 |             28 |
  request.throttler.ts  |    95.65 |       80 |      100 |    95.65 |             57 |
  request.validation.ts |      100 |      100 |      100 |      100 |                |
 src/services           |      100 |       75 |      100 |      100 |                |
  jwt.service.ts        |      100 |      100 |      100 |      100 |                |
  key.service.ts        |      100 |      100 |      100 |      100 |                |
  storage.service.ts    |      100 |       50 |      100 |      100 |                |
  tenant.service.ts     |      100 |      100 |      100 |      100 |                |
  user.service.ts       |      100 |      100 |      100 |      100 |                |
------------------------|----------|----------|----------|----------|----------------|

=============================== Coverage summary ===============================
Statements   : 98.47% ( 385/391 )
Branches     : 81.73% ( 85/104 )
Functions    : 100% ( 74/74 )
Lines        : 98.37% ( 363/369 )
================================================================================

4.send curl request.
curl --include \
     --request POST \
     --header "Content-Type: application/json" \
     --header "Accept: application/json" \
     --data-binary "{
    \"email\"<EMAIL_ADDRESS>    \"password\": \"Password2\"
}" \
'http://auth:3000/tenant'

I got 'curl: (52) Empty reply from server'.
By the way, the docs say the API endpoint is: http://auth:3000/,is my DNS setup steps correct?
Thanks

@AlekNS
Hi,I have update the curl request,I can got response from container.
But tenant endpoint  returned 403 Forbidden.
Is there anything wrong with my dev environment?
[john@~/Documents/src/backend-auth]curl --include \
>      --request POST \
>      --header "Content-Type: application/json" \
>      --header "Accept: application/json" \
>      --data-binary "{
>     \"email\"<EMAIL_ADDRESS>>     \"password\": \"Password1\"
> }" \
> 'http://auth: 32782/tenant'
HTTP/1.1 403 Forbidden
X-Content-Type-Options: nosniff
X-Frame-Options: deny
Content-Security-Policy: default-src 'none'
Content-Type: application/json; charset=utf-8
Content-Length: 21
ETag: W/"15-BOD3e569EKnzuMK5eYTqnA"
Date: Wed, 25 Apr 2018 07:03:31 GMT
Connection: keep-alive

{"error":"Forbidden"}

Thanks

I think the reason is in TENANT_WHITE_LIST, default value is <IP_ADDRESS> in docker-compose.prod.yml. This variable needs to prevent requests from unwanted hosts. Internally in the docker container, all external localhost requests will be forwarded on behalf of a default docker network gateway, that's why <IP_ADDRESS> doesn't match. Try to recreate containers like:
TENANT_WHITE_LIST="YOUR_REAL_HOST_IP" docker-compose -f docker-compose.prod.yml up --force-recreate -d

where YOUR_REAL_HOST_IP is ip address of your local network device.


Add issue support via Peril

@orta does this look about right? I'm looking to add support to issues.

Yep

:100: Thanks!


copyto/moveto puts files in a sub directory of the working directory on windows

What is the problem you are having with rclone?
copyto/moveto puts files in a sub directory of the working directory on windows.
E.G.  If the pwd is "C:\Users\JD", and I run:
rclone copyto "GDrive:Path/To/File.exe" "C:\Path\To\New_File.ext"
The file will end up in: "C:\Users\JD\Path\To\New_File.ext"
What is your rclone version (eg output from rclone -V)
1.42
Which OS you are using and how many bits (eg Windows 7, 64 bit)
Windows Server 2012 R2, 64 bit
Which cloud storage system are you using? (eg Google Drive)
Google Drive (but problem seems to be on windows side)
The command you were trying to run (eg rclone copy /tmp remote:tmp)
rclone copyto "GDrive:Doctor Who/Doctor Who (2005)/Season 01/Episode 01/DVD.480.mkv" "C:\PMM\Downloads\Film\TV Shows\Doctor Who (2005)\Season 01\Doctor Who (2005) - s01e01 - Rose.mkv" -vv
A log from the command with the -vv flag (eg output from rclone -vv copy /tmp remote:tmp)
2018/06/17 18:03:14 DEBUG : rclone: Version "v1.42" starting with parameters ["C:\Windows\system32\rclone.exe" "copyt
o" "GDrive:Doctor Who/Doctor Who (2005)/Season 01/Episode 01/DVD.480.mkv" "C:\PMM\Downloads\Film\TV Shows\Doctor Wh
o (2005)\Season 01\Doctor Who (2005) - s01e01 - Rose.mkv" "-vv"]
2018/06/17 18:03:14 DEBUG : Using config file from "C:\Users\jd\.config\rclone\rclone.conf"
2018/06/17 18:03:20 INFO  : Local file system at \?\C:\Users\jd: Modify window is 1ms
2018/06/17 18:03:20 DEBUG : DVD.480.mkv: Couldn't find file - need to transfer
2018/06/17 18:03:50 INFO  : DVD.480.mkv: Copied (new)
2018/06/17 18:03:50 INFO  :
Transferred:   1.802 GBytes (52.034 MBytes/s)
Errors:                 0
Checks:                 0
Transferred:            1
Elapsed time:       35.4s
2018/06/17 18:03:50 DEBUG : 6 go routines active
2018/06/17 18:03:50 DEBUG : rclone: Version "v1.42" finishing with parameters ["C:\Windows\system32\rclone.exe" "copy
to" "GDrive:Doctor Who/Doctor Who (2005)/Season 01/Episode 01/DVD.480.mkv" "C:\PMM\Downloads\Film\TV Shows\Doctor W
ho (2005)\Season 01\Doctor Who (2005) - s01e01 - Rose.mkv" "-vv"]
Even though it says the file was in "C:\PMM...", it landed again in "C:\Users\jd\PMM..."

I can confirm this problem.
The problem is to do with handing of \ in paths.  If you replace them with / then the command will work (except it will fall foul of #1754 unless you remove the initial C:).
I'll try to think of a good fix and post a beta to test.

Can you try this beta please and see if it fixes the problem?
https://beta.rclone.org/v1.42-006-g78374885-test/ (uploaded in 15-30 mins)

Can we windows users have hotfix for this?

Sorry that didn't build.  Try this
https://beta.rclone.org/branch/v1.42-026-g144c1a04-fix-2353-windows-copyto/ (uploaded in 15-30 mins)
I'd appreciate some feedback and if it works I'll merge it into the beta.

Works great with 1.42-026. Thanks.


Move pyinfra.api.connectors -> pyinfra.connectors

Let's treat them the same as facts or operatinos - they're an integral part of the different ways pyinfra can be used.

Released in v2


Don't enforce warnings.simplefilter('always')

Prevents turning warnings into exceptions and makes suppressing harder if it's necessary.
Setting the filter within this method is unnecessary and makes overriding it awkward, even if you want to turn warnings into exceptions.
My use-case for suppressing warnings:
I have an application which creates several processes, and I want to find and connect a pywinauto.Application instance to one of those processes. They are easy to find based on window title for which I'm using pywinauto.findwindow.find_windows, but occasionally another application (cmd) will show up as a false match.
This is exacerbated by my having to try in a loop for the window to appear, resulting in many repetitions of the UserWarning being printed.
Of course I can easily check the process name once I've attached the Application, but the warning is already emitted at that point, even though I won't actually try to automate the 64bit cmd.
(I could flip my logic around and attempt to find a matching window belonging to each matching process, but this way looks neater and requires significantly fewer find_windows calls).

Hi Matt, nice to see your efforts improving pywinauto.
The fix is working in py27 and py34+, but py33 tests are failing. Could you please take a look at py33 specific behavior?

Ok looking at why this failed on 3.3

So this is weird. Manually testing the same things on 3.3 shows that all the warnings are actually emitted, and also using pytest as a test runner also makes them all pass (I found that out because I wanted to use pytest's --pdb feature).

It looks like nose/unittest in 3.3 fiddles with the warnings filters after loading the modules it's testing, so the filters I add at the top of application.py get overridden.
Playing leapfrog and putting the filters in there again in setUp() seems to work locally. It does mean warnings.filters will keep growing during that test run though so it's not particularly neat...
If you're not happy with that then an alternative option could be:
Running the tests using py -${PYTHON_VERSION} -W all -m nose instead of nosetests makes them pass too, but makes the test output wordy (all deprecation warnings are now emitted).
Maybe that's not such a bad thing though?
How do you feel about that? I'd rather make the change for all versions but modifying runTestsuite.ps1 to just do that for 3.3 shouldn't be too difficult.

Another option is switch to pytest ))

I almost mentioned that too but thought I'd gone on enough :)
Is there an easy way to get appveyor etc. to run on a branch in my repo or should I just create another PR to test that?

Yeah, I've just thought about pytest too. :)
It's easy to create AppVeyor project for your fork. You just need to copy WebHook URL to the forked repo settings.

Hmm... it looks like setUp fix caused py33 tests to pass.
We can merge the PR now. Thank you, Matt!
We may consider porting the whole test suite to pytest later. I think it's interesting idea. But currently we have too many high-priority tasks with 0.6.0 milestone.

Current coverage is 96.84%

Merging #138 into master will not affect coverage as of add33d4

@@            master    #138   diff @@
======================================
  Files           22      22
  Stmts        16474   16471     -3
  Branches         0       0
  Methods          0       0
======================================
- Hit          15954   15951     -3
  Partial          0       0
  Missed         520     520

Review entire Coverage Diff as of add33d4

Powered by Codecov. Updated on successful CI builds.

Excellent. Do you want me to create a PR for UIA too, or will you do that?

Master and UIA are not auto mergable now. I'll do that later. Thanks. )


Keyboard backlight keys not working after update

Hi all - I know you're not my personal tech support but thought i would raise it here in case anyone is experiencing a similar issue or could point me in the right direction.
The keys of activate the keyboard backlight on my Thinkpad T450s have stopped responding - this includes all additional function keys like mute, mic indicator ect.
I'm able to turn the lights on with: light -Srs "sysfs/leds/tpacpi::kbd_backlight 1
As far as i know i didn't make any changes that should have caused this. I've tried rolling back to kernel 4.14, where it was previously working & also disabling tlp and powertop.
Any suggestions would be appreciated.
Regards

Apologies the hardware on my keyboard was damaged.


问题

运行指令时出现这样的错误：error in modulated_deformable_im2col_cuda: no kernel image is available for execution on the device,哪位大神可以帮忙讲解一下呢，我的微信号是15033351767，谢谢

您好，我也遇到了同样的问题，请问解决了吗

你好，请问你们解决了这个问题嘛?

您好，我也遇到了同样的问题，请问解决了吗

运行指令时出现这样的错误：error in modulated_deformable_im2col_cuda: no kernel image is available for execution on the device,哪位大神可以帮忙讲解一下呢，我的微信号是15033351767，谢谢

Hi all, sorry for the late response.
If this issue is still relavant to you, I would suggest to try our new GMStereo model: https://haofeixu.github.io/unimatch/ & https://github.com/autonomousvision/unimatch. No CUDA op is required. A Colab demo is also provided to try our model in your browser. Hope it helps, thanks.


Minor typo on CSS inline style lesson

Describe your problem and how to reproduce it:
There is a minor typo on the lesson for CSS inline styles as part of the Responsive Web Design curriculum.
The challenge part of the lesson reads as follows:
"Use an inline style to try to make our h1 element white. Remember, in line styles look like this:"
The second instance of inline is here written as “in line” which is incorrect.
Add a Link to the page with the problem:
https://www.freecodecamp.org/learn/responsive-web-design/basic-css/override-class-declarations-with-inline-styles
Tell us about your browser and operating system:
Not relevant (though FWIW, Firefox Developer Edition on MacOS Big Sur)
If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box):

Thank you, for taking the time to open this.
This is a simple issue. So, I have opened it up to first timers.

An issue with the help wanted or first timers only label is open for contribution. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors.
If you would like to contribute, and have not read the contributors docs, please do so here: https://contribute.freecodecamp.org/#/
If you have any issues with contributing, be sure to join us on the contributors channel, or on the contributors sub-forum

Can I work on this as my first code contribution to FCC?


Improve testability by extracting an interface for JWTVerifier

For the sake of unit testing, it would be nice if there was an an interface extracted from the implementation.

I have also run into the same issue; and since the class is final I can't mock it either.

Would it help making the class non-final?

That would solve my testing problem for sure.


[Improvement-14916][dolphinscheduler-alert] alert message contains the taskPriority

Purpose of the pull request
Fix https://github.com/apache/dolphinscheduler/issues/14916
Brief change log

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

(or)
If your pull request contain incompatible change, you should also add it to docs/docs/en/guide/upgrede/incompatible.md

Codecov Report

Merging #14919 (8baef8f) into dev (73e846d) will decrease coverage by 0.02%.
The diff coverage is 0.00%.

:exclamation: Current head 8baef8f differs from pull request most recent head f891543. Consider uploading reports for the commit f891543 to get more accurate results

@@             Coverage Diff              @@
##                dev   #14919      +/-   ##
============================================
- Coverage     38.85%   38.84%   -0.02%
- Complexity     4591     4592       +1
============================================
  Files          1234     1234
  Lines         43377    43380       +3
  Branches       4792     4792
============================================
- Hits          16856    16852       -4
- Misses        24658    24664       +6
- Partials       1863     1864       +1

Files Changed
Coverage Δ

...inscheduler/service/alert/ProcessAlertManager.java
35.84% <0.00%> (-5.87%)
:arrow_down:

... and 3 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


ELF: Detect OS from Go binaries

use the strategies pioneered by GoReSym to detect the target OS for ELF binaries compiled by Go:

find the GOOS configuration, and
find embedded Go source filenames

ref #1978
FYI @C0d3R3ad3r
FYI @stevemk14ebr
Checklist

[ ] No CHANGELOG update needed

[x] No new tests needed

[x] No documentation update needed

thank you for the feedback - i was being lazy. i'll add some test files and some test cases.

I would recommend testing on old go versions prior to 1.18 when buildinfo was added. I would also recommend testing with binaries emitted by garble and gobfuscate which can mess with symbol names. Otherwise LGTM with the above notes in mind

Tests are TODO / in progress? Getting the following when trying to resolve conflicts:
Failed to merge submodule tests/data (commits don't follow merge-base)
CONFLICT (submodule): Merge conflict in tests/data
Recursive merging with submodules currently only supports trivial cases.
Please manually handle the merging of each conflicted submodule.
This can be accomplished with the following steps:
 - go to submodule (tests/data), and either merge commit 9f7f3c5
   or update to an existing commit which has merged those changes
 - come back to superproject and run:

      git add tests/data

   to record the above merge or update
 - resolve any other conflicts in the superproject
 - commit the resulting index in the superproject

Before continuing, I wanted to confirm what the status here was/is.

Yeah, I owe tests here. I believe the implementation is solid but without tests I can't prove it.
At a comfortable effort level, I could have this done in maybe two weeks. If there's a pending deadline, let me know and I can squeeze it in sooner.

This is not urgent at all! I just thought I may be able to lend a hand.

This is ready to go, but I had pulled in #2146 (instead of master), so we should merge that PR before this one.

one issue with black: https://github.com/mandiant/capa/actions/runs/9496141307/job/26169887389?pr=1987#step:7:32


[Suggestion]: Multiline text

It would we nice if the label and the details label would support multiline text so that more text can fit in those.

The details label should already support that.

Should be doable with the latest master.


Ksecurity-2360 fix jose4j CVE

More detailed description of your change,
if necessary. The PR title and PR message become
the squashed commit message, so use a separate
comment to ping reviewers.
Summary of testing strategy (including rationale)
for the feature or bug fix. Unit and/or integration
tests are expected for any behaviour change and
system tests should be considered for larger changes.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

This is not needed as fixed upstream in AK
https://github.com/confluentinc/ce-kafka/blob/78e61abec03e9be12ca059841619be236ed097fa/gradle/dependencies.gradle#L156


custom fields for contact association do not display in web form

Environment

Nautobot version (Docker tag too if applicable): 2.3.6, 2.3.10, no docker
Python version: 3.8
Database platform, version: PSQL12
Middleware(s):

Steps to Reproduce

create custom field

name: myfield
content types: extras | contact association
required: checked

navigate to a location and click add contact
note that the custom field does not display in the form
complete the form and click assign.  notice the contact is not added because the custom field is required but cannot be set

this is also the case for adding contacts to circuits and most likely any object that allows contact associations
Expected Behavior
custom field shows up in contact associations form
Observed Behavior
custom field does not show up in contact associations form

Thanks for the report! Looks like fixing this might be as simple as adding {% include 'inc/extras_features_edit_form_fields.html' %} to templates/extras/object_assign_contact_or_team.html?

was that a question for me?  i'm not familiar with under the hood

No, sorry for the confusion - just a note to whoever picks this up to fix it. :-)


Fails to build with GCC on FreeBSD

Affects at least FreeBSD 11.3-RELEASE, 12.1-RELEASE, 13.0-RELEASE.
$ pkg install automake libtool gmake gcc9
$ sh bin/setup.sh
$ cd build
$ export MAKE=gmake CC=gcc9
$ ../configure --enable-warnings
$ gmake
[...]
../../libxo/xo_encoder.c: In function 'xo_encoder_discover':
../../libxo/xo_encoder.c:237:9: error: cast between incompatible function types from 'dlfunc_t' {aka 'void (*)(struct __dlfunc_arg)'} to 'int (*)(xo_encoder_init_args_t *)' {aka 'int (*)(struct xo_encoder_init_args_s *)'} [-Werror=cast-function-type]
  237 |  func = (xo_encoder_init_func_t) dlfunc(dlp, XO_ENCODER_INIT_NAME);
      |         ^

Very strange, considering that dlfunc is meant to be cast:
 The dlfunc() function implements all of the behavior of dlsym(), but has
 a return type which can be cast to a function pointer without triggering
 compiler diagnostics.  (The dlsym() function returns a data pointer; in
 the C standard, conversions between data and function pointer types are
 undefined.  Some compilers and lint(1) utilities warn about such casts.)
 The precise return type of dlfunc() is unspecified; applications must
 cast it to an appropriate function pointer type.

I guess the fix would involve "#pragma GCC diagnostic push/ignore/pop".
Thanks,
Phil

Sorry to be so insanely slow;  Fixed in "develop".
Thanks,
Phil


Figure 27: Coarse-level control

Hi, guys, thanks for your work!
Have the question, how can I reproduce results from Figure 27? (Coarse-level control)

there is no figure 27 or anything related to coarse-level control in the control net paper https://arxiv.org/abs/2302.05543


How do i set up the codespace

i dont know how to set up the codespace

i dont know how to set up the codespace

go to replit.com and set it up there then


fix: get upload tests working

Changes

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#572  👈
#571
#570
#566
#565
main

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

Join @MasterPtato and the rest of your teammates on  Graphite


Programmatically trigger Edit and View mode

I'm submitting a
Feature request
Current behavior
There's no way to trigger Edit & View mode programmatically. This would be a helpful feature
Expected behavior
An @Input() directive for both Edit as well as View mode activation.
Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?
Being able to trigger the View mode and Edit mode programmatically would be a great addition. Can be used in a lot of scenarios where we want some outside event to trigger the respective modes.
Environment
No response

You could take a component reference with "@Viewchild" and use functions displayEditMode() and cancelEdit() to toggle modes.

Thanks @bncunha


API for plugins to collaboratively render a node

The current API lets plugins add new renderer functions (for node types that dont have a default one) or override existing functions. There is no good way for plugins to collaborate on the same node type, however.
This would be useful e.g. for plugins to set character escape rules by collaboratively modifying renderers of paragraph and text syntaxes. This would solve issues like https://github.com/executablebooks/mdformat-tables/pull/10

Closed by https://github.com/executablebooks/mdformat/pull/175


Deployment

Deployment
User Story
As a Boot Camp Student,
I want the prework notes to be structured on a webpage,
So that I can easily find and read the information.
Acceptance Criteria
GIVEN a Prework Study Guide website,
WHEN I visit the website using the URL,
THEN I can access my website from any browser

Completed


DS-3636 Indexes and caching performance updates

Pull Request for JIRA ticket:
https://jira.duraspace.org/browse/DS-3636
Put indexes on several widely searched columns + use some additional caching for performance improvements.

Updated the indexes and code comments based on the feedback
Additionally, I noticed that the oracle flyway broke for both this and the previous flyway file
Fixed the following,

Added slashes between index checking declarations
Updated some of the index names (These are required to be under 30 characters in Oracle)

This pull request is a no-brainer for me as well. It greatly increases the performance of the XMLUI /submissions page in DSpace 5.5, for example. Before this, I observed hundreds or even thousands of locks on the resourcepolicy and metadatavalue tables during operations on that page. Deleting unfinished submissions would often take several minutes on beefy hardware with modern PostgreSQL 9.5, but complete almost instantly with these indexes.

@tomdesair : just a reminder for you to dismiss your "requested changes" review if you are now satisfied with this PR.  It looks to me like the changes you requested have now been made, but I hesitate to dismiss the review of any other Committer.

@kshepherd, should we consider this for 6.4? I haven't tried it yet but it seems relatively straightforward
if something along similar lines hasn't already been applied, it might be worth porting to 7? @tdonohue

@kshepherd, should we consider this for 6.4? I haven't tried it yet but it seems relatively straightforward
if something along similar lines hasn't already been applied, it might be worth porting to 7? @tdonohue

It looks good - is there a dspace 6 port?

Yeah, #1792 ...... but like I say, haven't tested this myself....


docs(api): update example link for webpack 5

I've submitted a pull request here https://github.com/webpack/webpack.js.org/pull/3537 two months ago which is unfortunately wrong as I found today.
According to webpack changelog https://github.com/webpack/changelog-v5#minor-changes:

Stats json errors and warnings no longer contain strings but objects with information splitted into properties.
MIGRATION: Access the information on the properties. i. e. message

Then example2.json is for webpack 5 while example1.json is for webpack 4.

Thanks! Although its a shame we did not realize this earlier :)


fix: escape json for string input

close #833
close #819

Pull Request Test Coverage Report for Build 2747
Details

0 of 16 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.3%) to 85.43%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

builtin/json.mbt
0
16
0.0%

Totals

Change from base Build 2745:
-0.3%

Covered Lines:
3729

Relevant Lines:
4365

💛  - Coveralls


Visible deletion interface

Currently the only interface for deleting a cell is hitting backspace, which is a secret interaction. There should be something discoverable for this, maybe an 'X' that appears when you hover to the left or something, or just copy the dragging+item-edit-menu interface from Notion.

I like the Notion UI for this pretty well. In any case, we should think through this issue in conjunction with #19.

This issue will become more urgent with #135. At the moment, there is no way to delete analysis cells.


Is is possible to use subscriptions with SSR?

I could not really find an answer and I am not sure if it is good place to ask.
yarn -v 0.22.0
npm -v 4.1.2
node -v 7.5.0
reactql version 2.1.0

Is is possible to use subscriptions with SSR? I am aware that nodejs does not have direct support for websockets, so we have  to install package/library to add desired functionality...
SubscriptionClient is used for client/browser.
Of course I use Graph.cool as my backend service.
webSocketImpl: Object - optional, WebSocket implementation. use this when your environment does not have a built-in native WebSocket (for example, with NodeJS client)
Here is part of my apollo.js file:
import WebSocket from 'ws';
import {SubscriptionClient, addGraphQLSubscriptions} from 'subscriptions-transport-ws';

const wsClient = new SubscriptionClient(APOLLO.socketsUri, {
  reconnect: true,
  connectionParams: {
  }
}, WebSocket); // webSocketImpl object

Error I am getting when I don't use webSocketImpl object

It does not seem to work when I use npm run build-run (console dump). Clearly I am doing something wrong, can I get guidance or can you point me to an example which shows how to implement subscriptions with SSR?

@loelsonk You actually don't want to enable the SubscriptionClient on the server. As the subscription is for reacting to a stream of real time of events, it's unneeded in the SSR phase. During SSR you just need to get the current state of the data you need. Then once your app mounts on the client-side, you can subscribe to changes.
Check out the client entry point from githunt-react, the semi-official example from the Apollo devs. https://github.com/apollographql/GitHunt-React/blob/master/ui/client.js#L24. Note how the subscription client is only added on the client entry and not the server.

I plan on writing a guide that demonstrates subscriptions in practice in a universal way. Like @jtmthf said, this would be done by fetching only the initial data on the server, piping it down to the client, and then letting the client subscribe directly.
I'll close this for now, and will drop a note back when the docs have been updated with the guide.

@leebenson  I will definitely check your guide, just let me know.
@jtmthf @leebenson Thanks for help I've got it to work, just tested it and my subscription works in production and in development mode.
So here are my small changes to apollo.js file. Changes are small but it is working as intended. What do you think? Are there any "gotchas" with this code or this is proper way of implementing subscriptions?
// Silly naming createNewNetworkInterface, networkInterface, createNetworkInterface
function createNewNetworkInterface() {
  const networkInterface = createNetworkInterface({
    uri: APOLLO.uri
  });

  // Auth0 token
  networkInterface.use([{
    applyMiddleware (req, next) {

      if (!req.options.headers) {
        req.options.headers = {};
      }

      if (!SERVER) {
        req.options.headers.authorization = `Bearer ${localStorage.getItem('id_token')}`;
      }

      next();
    },
  }]);

  if (SERVER) {
    return networkInterface;
  }

  // Client side only
  const wsClient = new SubscriptionClient(APOLLO.subscriptionUri, {
    reconnect: true
  });

  return addGraphQLSubscriptions(
    networkInterface,
    wsClient,
  );
}

function createClient(opt = {}) {
  return new ApolloClient(Object.assign({
    reduxRootSelector: state => state.apollo,
    networkInterface: createNewNetworkInterface()
  }, opt));
}

There is another thing I would like to ask, how to handle authentication with SSR? I am using Auth0 + GraphCool. For client side of course there is localStorage, but for server side with koa? I tried koa-generic-session to store my auth0_token, it actually works. But is this proper way to do it?
Should I create new issue for this(not really an issue but just a question)?

One way to handle authentication is to pass the auth token back to the client as a cookie.
This way, you're using the initial SSR as a 'proxy' for authentication - on the very first call from the server, any Bearer token received from the API server would be returned as a cookie (down to the browser), allowing future requests to the server to reuse that same token.
On the client, you could then store the request in localStorage, making it available to future direct requests to the GraphQL endpoint via a custom Authorization: header, like you've done in your example.
There are a few gotchas in this scenario to be aware of:

You will need to use cookies and localStorage. You can't use localStorage on its own, because any future requests back to the server handling SSR need to pass the auth token in the HTTP header of the request (localStorage is obviously only available after the request has already returned.) And you probably can't use cookies on their own, because...

Cookie security needs to be considered. Allowing programmatic access to cookies is generally a bad thing- it opens the door to rogue scripts that could potentially read the token, and pass it off-site via an AJAX request. If it's a cookie that does no kind of origin checking, then that could potentially give full access to the API to an attacker. Disallowing cookie reads means passing it downstream via some other means along with the cookie, so that you have Javascript access to it later (this could be a good use of your Redux store!)

Original headers might be a factor.  Per no. 2 above, if an auth token, say, hashes the User-Agent and some other identifying information, or returns a secondary cookie that is required along with auth, you may need to factor those considerations on the SSR render by copying over the original headers to effectively 'proxy' any server requests. This won't help if the API server is using your IP as part of its auth model, but if you're designing the GraphQL endpoint yourself, you might want to implement secondary vectors into your auth routine such as HTTP headers, as a sanity check against the origin.

There's probably no way to standardise this, because the implementation details are up to the GraphQL server. Some use HTTP headers to communicate bearer tokens; others might send a token back as part of the query data.
I think it makes sense to write an auth guide, though, that tackles some of these common scenarios and possibly make the default behaviour of the Apollo client on the server to mimic the headers it receives from the client to act more like a proxy.
I'll open a separate issue in reactql/docs as a reminder.


18848 - add court order / POA component on review page

Issue #: /bcgov/entity#18848
Description of changes:
Add court order / POA component (only for staff)
Invalid Court order:

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the bcrs-entities-create-ui license (Apache 2.0).

/gcbrun

Temporary Url for review: https://business-create-dev--pr-604-6itq7b59.web.app


Feature: Support AdminLTE for scaffolding

More and more people are moving into AdminLTE for greater admin interfaces.
It would be great that this package could support the AdminLTE scaffolding.

@viezel I am going to add field level and form level templates in some next releases. Then we can make another package which publishes templates of this generator which is compatible with AdminLTE. so we can make it fully modular without affecting a real generator package.

Sounds like a great plan

You should work on this first if you need the bladed files I  have them and can give them to you.

Check this, https://github.com/Leelam/Laravel-with-basic-packages


Croppie('destroy') doesn't destroy croppie instance

Expected to destroy croppie instance on hidden modal event
body of on hidden modal event is executed wonderfully however $('#demo').croppie('destroy') does not destroy the previous initialized croppie instance
Steps to Reproduce the Problem

Example Link
Please recreate your issue using JSbin, JSFiddle, or Codepen.

Link:
https://jsbin.com/juhoviwuva/edit?html,css,js,console,output

Specifications

Browser: chrome
Version: latest

This issue has been reported multiple times. Not sure if anyone is willing to take the time to fix it. That said, you'll find workaround code in this issue:
https://github.com/Foliotek/Croppie/issues/749
Basically, destroying the Croppie container isn't all that complex.


Failure Creating New Cluster

When I try to deploy a new flynn cluster based on a backup image, it times out on the mongodb-wait job. Any guidance you can give me would be greatly appreciated. The logs are below.
Using saved key pair (flynn)
Allocating domain
Fetching image manifest
Generating start script
Creating stack
AWS::CloudFormation::Stack (flynn-1471917979)	CREATE_IN_PROGRESS (User Initiated)
AWS::EC2::InternetGateway (Gateway)	CREATE_IN_PROGRESS
AWS::Route53::HostedZone (DNSZone)	CREATE_IN_PROGRESS
AWS::EC2::InternetGateway (Gateway)	CREATE_IN_PROGRESS (Resource creation Initiated)
AWS::EC2::VPC (VPC)	CREATE_IN_PROGRESS
AWS::Route53::HostedZone (DNSZone)	CREATE_IN_PROGRESS (Resource creation Initiated)
AWS::EC2::VPC (VPC)	CREATE_IN_PROGRESS (Resource creation Initiated)
AWS::EC2::InternetGateway (Gateway)	CREATE_COMPLETE
AWS::EC2::VPC (VPC)	CREATE_COMPLETE
AWS::EC2::SecurityGroup (PublicSecurityGroup)	CREATE_IN_PROGRESS
AWS::EC2::VPCGatewayAttachment (GatewayAttachment)	CREATE_IN_PROGRESS
AWS::EC2::Subnet (Subnet)	CREATE_IN_PROGRESS
AWS::EC2::VPCGatewayAttachment (GatewayAttachment)	CREATE_IN_PROGRESS (Resource creation Initiated)
AWS::EC2::RouteTable (GatewayRouteTable)	CREATE_IN_PROGRESS
AWS::EC2::Subnet (Subnet)	CREATE_IN_PROGRESS (Resource creation Initiated)
AWS::EC2::RouteTable (GatewayRouteTable)	CREATE_IN_PROGRESS (Resource creation Initiated)
AWS::EC2::RouteTable (GatewayRouteTable)	CREATE_COMPLETE
AWS::Route53::HostedZone (DNSZone)	CREATE_COMPLETE
AWS::EC2::SecurityGroup (PublicSecurityGroup)	CREATE_IN_PROGRESS (Resource creation Initiated)
AWS::EC2::VPCGatewayAttachment (GatewayAttachment)	CREATE_COMPLETE
AWS::EC2::Subnet (Subnet)	CREATE_COMPLETE
AWS::EC2::SecurityGroup (PublicSecurityGroup)	CREATE_COMPLETE
AWS::EC2::SubnetRouteTableAssociation (SubnetRoute)	CREATE_IN_PROGRESS
AWS::EC2::Route (GatewayRoute)	CREATE_IN_PROGRESS
AWS::EC2::SubnetRouteTableAssociation (SubnetRoute)	CREATE_IN_PROGRESS (Resource creation Initiated)
AWS::EC2::Route (GatewayRoute)	CREATE_IN_PROGRESS (Resource creation Initiated)
AWS::EC2::Instance (Instance0)	CREATE_IN_PROGRESS
AWS::EC2::Instance (Instance0)	CREATE_IN_PROGRESS (Resource creation Initiated)
AWS::EC2::SubnetRouteTableAssociation (SubnetRoute)	CREATE_COMPLETE
AWS::EC2::Route (GatewayRoute)	CREATE_COMPLETE
AWS::EC2::Instance (Instance0)	CREATE_COMPLETE
AWS::Route53::HealthCheck (Instance0HealthCheck)	CREATE_IN_PROGRESS
AWS::Route53::HealthCheck (Instance0HealthCheck)	CREATE_IN_PROGRESS (Resource creation Initiated)
AWS::Route53::HealthCheck (Instance0HealthCheck)	CREATE_COMPLETE
AWS::Route53::RecordSetGroup (DNSRecords)	CREATE_IN_PROGRESS
AWS::Route53::RecordSetGroup (DNSRecords)	CREATE_IN_PROGRESS (Resource creation Initiated)
AWS::Route53::RecordSetGroup (DNSRecords)	CREATE_COMPLETE
AWS::CloudFormation::Stack (flynn-1471917979)	CREATE_COMPLETE
Fetching stack
Configuring DNS
Uploading backup
dial tcp <IP_ADDRESS>:22: getsockopt: connection refused
dial tcp <IP_ADDRESS>:22: getsockopt: connection refused
dial tcp <IP_ADDRESS>:22: getsockopt: connection refused
dial tcp <IP_ADDRESS>:22: getsockopt: connection refused
dial tcp <IP_ADDRESS>:22: getsockopt: connection refused
dial tcp <IP_ADDRESS>:22: getsockopt: connection refused
dial tcp <IP_ADDRESS>:22: getsockopt: connection refused
dial tcp <IP_ADDRESS>:22: getsockopt: connection refused
dial tcp <IP_ADDRESS>:22: getsockopt: connection refused
dial tcp <IP_ADDRESS>:22: getsockopt: connection refused
dial tcp <IP_ADDRESS>:22: getsockopt: connection refused
Running bootstrap
online-hosts: start
online-hosts: done
discoverd: start
discoverd: done
flannel: start
flannel: done
wait-hosts: start
wait-hosts: done
postgres: start
postgres: done
postgres-wait: start
postgres-wait: done
mongodb: start
mongodb: done
mongodb-wait: start
Running `sudo flynn-host collect-debug-info` on <IP_ADDRESS>
sudo: unable to resolve host ip-10-0-6-233
t=2016-08-23T02:19:17+0000 lvl=info msg="uploading logs and debug information to a private, anonymous gist"
t=2016-08-23T02:19:17+0000 lvl=info msg="this may take a while depending on the size of your logs"
t=2016-08-23T02:19:17+0000 lvl=info msg="getting flynn-host logs"
t=2016-08-23T02:19:17+0000 lvl=info msg="getting scheduler state"
t=2016-08-23T02:19:17+0000 lvl=eror msg="error getting scheduler state" err="object_not_found: no leader found"
t=2016-08-23T02:19:17+0000 lvl=info msg="getting job logs"
t=2016-08-23T02:19:17+0000 lvl=info msg="getting system information"
t=2016-08-23T02:19:17+0000 lvl=info msg="creating anonymous gist"
Error: bootstrap: mongodb-wait wait error: bootstrap: timed out waiting for http://mongodb-api.discoverd/ping, last response 500

What version of flynn are you restoring from?
And was the URL for the gist containing the host logs part of the output? If not, can you rerun sudo flynn-host collect-debug-info on the server and post the logs (or email to logs@, you can output as a tar archive with the --tarball flag)?

restoring from v20160822.0 and the link to URL to the gist https://gist.github.com/0e8e32f02b344d0f1d2f2192e8008d03

The installer currently installs the current stable version, so you are restoring from a newer version. Backups are only forwards compatible, not backwards compatible. Well add an error message for this case.

Is there way that I can instruct the installer to install a specific version?

Not at this time (we currently only build stable AMIs).

Did you manually install the nightly and take a backup?

unfortunately yes

If you want to go back to the stable release exporting the individual app+databases with flynn export and then flynn import into a new cluster might work, I don't think there are any current incompatibilities there.


Chrome dev tool gets slow

Is anyone experiencing the chrome dev tool gets slow when using foundation?
When I select an element while inspecting on the dev tool, the mouse pointer freezes about 0.5sec. It's working smoothly after I disabled loading foundation.

Sorry, somehow I installed wrong old gem version, it was causing the issue. After specifying the gem version to the latest, it's working fine.


startup time is real slow

Hi, i am aware it is beta time but for info. Startup time of sample\HelloFSharp is 4.5 sec vs 0.5 sec of C# "hello world" with same dnx runtime. Windows 7 64-Bit.

This is due to several reasons. First of, when you're running the sample, your first compiling the F# compiler (not the actual compiler, but the YoloDev.Dnx.FSharp bridge), then you're loading the actual F# compiler, then your compiling your application to disk (which does a large amount of IO because the F# compiler was never made to support this kind of thing), then the compiled assembly is loaded into memory (so the on-disk ones can be cleaned up), and then your application can load and run. Most of these I can't do anything about, thus closing the issue.
Btw, try running a project with the compiled F# compiler instead. Should help a bit.


Unable to read data, Swift Foundation._GenericObjCError thrown when a rest request returns empty body

AFNetworking version: 2.6.0
Swift 2.1
AFNetworking handles an empty body (@"") returned for a GET rest request, by returning nil (at line 264) in the method
- (id)responseObjectForResponse:(NSURLResponse *)response
        data:(NSData *)data
        error:(NSError *__autoreleasing *)error

form the AFURLResponseSerialization.m file at line 231 (AFJSONResponseSerializer implementation).
The debug info before returning nil:

This method is called from the method
- (void)URLSession:(__unused NSURLSession *)session
                task:(NSURLSessionTask *)task
                didCompleteWithError:(NSError *)error

in the AFURLSessionManager.m file at line 186 (AFURLSessionManagerTaskDelegate implementation).
At this point, when the first method returns nil, the second method gets an error (called serializationError in the code):
_SwiftNativeNSError  -> domain: unable to read data - code: 0
NSError *serializationError = nil;
responseObject = [manager.responseSerializer responseObjectForResponse:task.response data:data error:&serializationError];

The debug after that Swift creates error out of the nil result:

And the GET method called in the AFHTTPSessionManager.m calls back the failure block with an error  (SwiftNativeNSError) Foundation._GenericObjCError with code 0.
The debug after that GET method's failure block is executed:

The rest call made succeeds with HTTP status 200 and returns empty body. But AFNetworking still calls back the failure block.
As I can see, AFNetworking needs to handle the nil (empty body) in a different way. I quess the problem is coming from Swift's way of handling optionals and errors.

There hasn't been any activity on this issue recently. I'm closing this now to clean up some old issues. If this issue persists with the latest version of AFNetworking, or you have a reproducible test case, please open a new issue and reference this issue.
Thanks! 🍻


Add homebrew instructions

Added details about homebrew and what archs are supported.
made minor style linting: add space surrounding shell code blocks, and headers.

please add label hacktoberfest-accepted <3


0.3.0 does not depend on jupyterlite-core

Description
This does not have PEP 621 dependencies on jupyterlite-javascript-kernel
Reproduce
Given:
# environment.yml
channels: [conda-forge]
dependencies:
- python
- pip
- pip:
  - jupyterlite-javascript-kernel

Then
mamba upgrade --file environment.yml --prefix .venv
source activate .venv
pip list | grep jupyter

See:
jupyterlite_javascript_kernel 0.3.0

Expected behavior
jupyter_core x.x.x
jupyterlite-core 0.3.0
jupyterlite_javascript_kernel 0.3.0

Context

https://github.com/conda-forge/jupyterlite-core-feedstock/issues/22
https://github.com/conda-forge/staged-recipes/pull/26440

Do we need the dependency on jupyterlite-core, if there is no JupyterLite addon? (similar to JupyterLab extension which which usually don't have a dependency on jupyterlab)

Welp... in theory that would work, but in practice (as there are no tests here) we're basically punting it to the site owner, or worse, a site user, to test whether a given configuration works. Indeed, lab at least has jupyter labextension list which would make it abundantly clear when things aren't going to work.
We can't really make a package more core than jupyterlite-core on which to advertise the liteserverextension/kernel API.
We could make another jupyterlite/matrix or something that tried to build demo sites of lots of extensions against lots of versions... but this would be a pretty unsatisfying site to visit, given the amount of issues with e.g. serviceworker registration.


Chocolatey GUI reverts to List View after making a change in settings

Starting with Chocolatey GUI 0.18.0, the default is to show both local and remote sources using the Tile View.  This works on application startup, and persists across closing and opening the application, however, if you modify another settings, i.e. toggling a feature on or off, when you return to the main screen, the Tile View will no longer be being used, and instead, it will have reverted to the List View.
Steps to reproduce

Open Chocolatey GUI
Verify that Tile View is shown by default
Click on the settings link
Toggle on (or off) the Show Console Output feature
Click the back button to return to main screen
See that the List View is now shown, rather than the default Tile View

@gep13 I also noticed this yesterday :-(

@gep13 This happens also if I change any of the other settings e.g. like the outdated package duration time.

@punker76 yip, I messed up 😢 I know where the issue is, and I have a local fix for it.  Yip, this isn't only on the Show Console Output feature, this was just an example.


Flags to configure include directories, linked libraries, etc.

As we use gradle objc compilation and cocoa pods, we should not have the user tell us multiple times common attributes like include directories and linked libraries by overriding command lines as flags.  Instead provide separate flags for each of these, and then convert those the command-line as appropriate for each tool in the chain.

prefix.properties is a bad example of this. I wrote the code to parse the
command line and find the file. Much better done as a distinctive set of
controls.
On Tue, Jun 2, 2015 at 2:27 PM Advay Mengle<EMAIL_ADDRESS>wrote:

As we use gradle objc compilation and cocoa pods, we should not have the
user tell us multiple times common attributes like include directories and
linked libraries by overriding command lines as flags. Instead provide
separate flags for each of these, and then convert those the command-line
as appropriate for each tool in the chain.
—
Reply to this email directly or view it on GitHub
https://github.com/brunobowden/j2objc-gradle/issues/85.

so i think i got all the right inputfiles in #110 except prefix.properties, can you capture that one here?


Can you provide the labels generating code?

ty very much, if you can provide the code that generate labels

Hi, we wish we could. But basically we used several different refinement techniques to get these labels for the training set. It's a little bit difficult to summarize them in one running program. Most of the cases we just used the Open3D p2plane ICP.

It would be great if you could provide code for central sampling.Thanks again.


Update the security agent deployment to 2 replicas

Update the security deployment to 2 replicas to allow for rebalancing to consider the pod

Thank you for creating this issue. Security agent now defaults to 2 replicas with leader election enabled. https://github.com/castai/kvisor/pull/188


feat: Allow Prisma client to be set on constructor

Closes https://github.com/node-casbin/prisma-adapter/issues/24

@dimino @hsluoyz plz review

Actually did the review earlier, but forgot to submit it..

LGTM thanks a ton for jumping on this so quickly!


GitPod compatibility

Hi everyone,
Explicit title: is there any plan to make this extension compatible with gitpod? (vscode online, linked to repo, very useful for contributors)
Thanks =)

Yes, we have plans to make both the extension and the language server in other environments.
These are mid-term plans, so I don't think we'll work on them in the next 2-3 months, unfortunately. If this changes (e.g. because we hire more people or priorities change), I'll update this issue.

One option to speed up support for vscode for web (and gitpod with it), would be to split syntax highlighting and maybe navigation from the compiler validation and warnings.
The barrier to running as a web extension is our access of the file system and those are mainly to support validation via solc (and hardhat dependency resolution). Navigation is based off of a solidity-parser parse, so we may be able to provide this in a pure browser setting.

Could be worth to evaluate having extension packs one with all the web-only functionalities and another with everything.

By the way I installed the vsix file in Gitpod and everything runs beautifully, even navigation. I believe the file system bits are seamlessly run on the Gitpod ephemeral server via SSH. I did not test much though.

Sorry about that, clicking on open hardhat configuration fails

Oh that is interesting. I suspect the nav to hardhat.config.ts file is a separate bug, maybe some assumptions about file paths that don't hold on the web host.
I have opened an issue for that (as separate from gitpod support): https://github.com/NomicFoundation/hardhat-vscode/issues/227

@Janther I had assumed that gitpod wasn't showing our extension because we are not a webextension, but if your able to install via vsix, it means they are running vscode extensions partially on the backend (which is all hardhat-vscode needs to run).
Let me dig a bit further and see why we are not appearing in the extensions tab when clearly the plugin can run.

Gitpod has its own registry for extensions because vscode is Microsoft and doesn't want to share extensions with 3rd party implementations of the editor.

@Janther we have added hardhat-vscode to openvsx (v0.4.6), I have been able to install the extension (and use it) via gitpod's web-based vscode:

Reviews on openvsx welcome!

Don't forget to add to your workflow the publishing of new versions to both registries now so there will be consistency in the environments ;)

Don't forget to add to your workflow the publishing of new versions to both registries now so there will be consistency in the environments ;)

Ha, I am updating our release docs as we speak!

The extension is available in gitpod via the openvsx registry: https://open-vsx.org/extension/NomicFoundation/hardhat-solidity


Updating Readme

Hello there!
I would like to update the overall look of readme by adding badges, gradient title, etc... kindly assign this issue to me.

hey, I wanted to contribute to this issue under GSsoc'23, can you please assign this issue to me.


Issue with argument 'adjoint_b'

Hello @carpedm20 , thanks for this project, it is helping me get better insight into the paper :)
Quick question: during re-implementation of the code, I am getting the following error:
Aout = tf.matmul(self.hid3dim, Ain, adjoint_b=True) TypeError: matmul() got an unexpected keyword argument 'adjoint_b'
Any idea what the cause could be?
Thanks a ton :)

I have encountered this issue as well. Any updates on this?


Why my detail_loss is always 0?

I am training the MODNet on Adobe Matting dataset. However, my detail_loss is always 0.

Hi, thanks for your attention.
Please check the pixel values in the loaded trimap. You need to normalize its value to [0, 1].

Hi, thanks for your attention.
Please check the pixel values in the loaded trimap. You need to normalize its value to [0, 1].

Hi, thanks for your attention.
Please check the pixel values in the loaded trimap. You need to normalize its pixel values to [0, 1].

Thanks for the reply. The problem has been solved. It turns out that in your official training code, you use "boundaries = (trimap < 0.5) + (trimap > 0.5)" to identify the transition region. I change the code to "boundaries = (trimap < 0.5) + (trimap > 0.5)".

Hi, thanks for your attention.
Please check the pixel values in the loaded trimap. You need to normalize its pixel values to [0, 1].

Thanks for the reply. The problem has been solved. It turns out that in your official training code, you use "boundaries = (trimap < 0.5) + (trimap > 0.5)" to identify the transition region. I change the code to "boundaries = (trimap < 0.5) + (trimap > 0.5)".


  -DARMCOMPUTE_ROOT=/home/yogo/sjy/ComputeLibrary-22.08/ -DARMCOMPUTE_BUILD_DIR=/home/yogo/sjy/ComputeLibrary-22.08/build/ -DFLATBUFFERS_ROOT=/home/yogo/sjy/flatbuffers/flatbuffers-install-dir/ -DARMCOMPUTENEON=1 -DARMCOMPUTECL=1 -DARMNNREF=1 -DPROTOBUF_ROOT=/home/yogo/sjy/protobuf-3.6.1/ -DPROTOBUF_LIBRARY_DEBUG=/home/yogo/sjy/protobuf-3.6.1/lib/libprotobuf.so.3.6.1 -DPROTOBUF_LIBRARY_RELEASE=/home/yogo/sjy/protobuf-3.6.1/lib/libprotobuf.so.3.6.1  -DBUILD_TESTS=1 -DBUILD_SAMPLE_APP=1 -DONNX_GENERATED_SOURCES=/home/yogo/sjy/onnx-proto/onnx/ -DBUILD_ONNX_PARSER=1
unit_test_res.txt

Hi,
This is a strange one. The original exception in ClCustomAllocatorTest is leaving the device in an invalid state so the tests from then on are failing. You can confirm this by excluding this test:
./UnitTests -tce=ClCustomAllocatorTest
I've not been able to recreate the test failure and I don't have access to an RK3399 to investigate. I'll talk to my colleagues in ACL to narrow down the problem.
Colm.

Hi @junyuancat1
Could you please share the command you used to run the unit tests?
Could you please share the output of clinfo ?
Please also see https://github.com/ARM-software/ComputeLibrary/issues/999#issuecomment-1273055281 as there may be an OpenCL configuration problem on your device.

Closing due to lack of activity, please reopen if you are still having the issue.
Thanks,
Francis.


Auto open web browser if --web flag is passed.

Use the webbrowser built-in package to open the web browser automatically when --web flag is passed.
Method reference:
https://github.com/yankeexe/good-first-issues/blob/e30a0e7a3cdbda1b1514cb8c210170a4569d093c/gfi/utils/__init__.py#L92

Currently just shows the port where the static page is served:

Looks like this issue is resolved

Looks like this issue is resolved

Yes, it's being worked on #9 @anupamasok