Crash with CallKit on iOS 9

When I convert the plugin from swift 2.2 to swift 3. I have build success on iOS 9 and iOS 10. It's working fine  both of them.
However, when I integrate CallKit framework (The new feature of Apple) into my project. I have got crash on iOS 9.  Although, I have checked feature that  effect only on iOS 10.

I don't know why CallKit conflict with plugin iOS-RTC.
.
Could you please help me check this.

CallKit is only supported in iOS 10, so no wonder it doesn't work in iOS 9.  I have no idea why it would crash there, but since the framework is not available I guess anything can happen.

But I don't use them on iOS 9, I have checked them only effect on iOS 10:
import CallKit
@available(iOS 10.0, *)
final class ProviderDelegate: NSObject, CXProviderDelegate {
}
Furthermore, if I remove the plugin cordova-plugin-iosrtc the my app is working fine.
I using:

Xcode 8
Swift 3 (I have been converted swift 2.3 -> swift 3)
cordova 6.2.0

Please help me check this? Thanks.

I'm not familar with CallKit yet, so I can't really help you with that.

Swift 3 (I have converted swift 2.2 -> swift 3)

This is very likely suspect.  I suggest you first try a simple application, without any bells and whistles just with the conversion and see if it crashes.  Some manual adjustments will probably be necessary.


Make Facebook login work with parse/node

I'm getting an The Facebook JavaScript SDK must be loaded before calling init. error. I spend over an hour finding a workaround, but I don't see any way to include FB SDK in NodeJS.
var Parse = require('parse/node');

const ParseID = '';
const ParseApiKey = '';

if (!Parse.applicationId) {
    Parse.initialize(ParseID, ParseApiKey);
    Parse.FacebookUtils.init();
}

module.exports = Parse;

Hi @jordi12100, the exception is because Facebook SDK does not support node environment. The Facebook SDK is meant to be used client-side only, since it cannot manage more than one user session simultaneously. If you really need this, you can use Facebook and parse REST API instead.

Closing, since there is no FB SDK for Node JS, and this is not something we can implement.


[SPARK-32576][SQL][TEST][FOLLOWUP] Add tests for all the character array types in PostgresIntegrationSuite

What changes were proposed in this pull request?

This is a follow-up PR of #29192 that adds integration tests for character arrays in PostgresIntegrationSuite.
Why are the changes needed?

For better test coverage.
Does this PR introduce any user-facing change?

No.
How was this patch tested?

Add tests.

@dongjoon-hyun Sorry to bother you, but could you check it again?

Test build #127275 has started for PR 29397 at commit 37e7c32.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/31895/
Test PASSed.

It's probably worth adding a SELECT query as well. That's how I discovered the issue.

Test build #127277 has started for PR 29397 at commit 9907bf5.

Thanks for the comment, @kujon. A SELECT query has the almost same code path, so I think the curreent tests look fine.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/31897/
Test PASSed.

Thanks, all! Merged to master/branch-3.0.

Test build #127275 has finished for PR 29397 at commit 37e7c32.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/127275/
Test PASSed.

Test build #127277 has finished for PR 29397 at commit 9907bf5.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/127277/
Test PASSed.

Thank you for adding the test coverage, @maropu ! :)


Can't use let's encrypt staging environment with last version.

1. What version of Caddy are you running (caddy -version)?
built from source
2. What are you trying to do?
start caddy using the staging environment of let's encrypt
4.  What did you expect to see?
caddy running properly
6. What did you see instead (give full error messages and/or log)?
2016/07/06 14:11:03 error creating client: registration error: acme: Error 400 - urn:acme:error:malformed - ECDSA curve P-384 not allowed

7. How can someone who is starting from scratch reproduce this behavior as minimally as possible?
go get github.com/mholt/caddy
$GOPATH/bin/caddy -ca -ca https://acme-staging.api.letsencrypt.org/directory

That's strange. I noticed you omitted your Caddyfile; can you share at least your tls directives?

Well, I'm unable to reproduce the problem without more information, so I'll close this for now.


Escape characters in configs

Currently, everything in the config is read as-is. There is no way to escape characters with special meaning.
This isn't really an issue right now because the config recognizes special characters only if the value starts with ${ and ends with } (references).
However, if we want to allow something like key = foo ${section.key} bar, we need to have a way to escape literal uses of ${ to not irreparably break existing configs.
I would propose the backslash (\) as the escape character because it's the most commonly used escape character.
Having an escape character here would also allow us to implement multiline config options by putting the backslash as the last character in a line (like in bash). This would also make #2207 obsolete.
Unfortunately, just making \ an escape character may break existing configs that use it as a literal character.
I propose a multi-step process to implement this functionality, to give users time to escape their literal backslashes:
1. Add warning or error to config parser for single backslashes
Add an error to the config parser when there is a single backslash in a config value and tell the user to escape their backslashes.
Since the backslash isn't used for escaping anything yet, all single backslashes in a config are literal backslashes.
We should still treat single backslashes as literal backslashes for backwards compatibility.
Because we tell the user to escape their backslashes, we also need to treat two backslashes (\\) as a single literal backslash.
This is the only breaking change here: If a user uses two consecutive literal backslashes, they will now be interpreted as a single literal backslash.
I think the risk of this is quite low.
At this point, the backslash is a proper escape character, it's just not used for anything else than escaping other backslashes.
2. Using the backslash to create multi-line config values
Any config value that ends in a backslash is joined together with the next line (the value will not contain a newline character).
Here, we need to take care to recognize both \n and \r\n as valid line-endings.
For users that have now properly escaped their literal backslashes, this should not break anything.
Otherwise it will break configs where there are an odd number of backslashes at the end of the line.
This would make #2207 obsolete
3+. Introduce constructs with special meanings to config values
We can now start adding things like config values where we can mix references and text.
Each time we do that, it may break certain configs that used that construct in a literal sense (for example someone using ${ as a literal string).

I think we can target 1 for a release and 2 & 3 for the release after that.
The error introduced in 1 should stay and we should also keep interpreting single backslashes that don't escape anything as literal backslashes.
I doubt that many people will be affected by any one of these steps. But I'm sure that there are some people that the backslash as a separator, so we should properly communicate what we're doing.

I will try to implement this.

I will try to implement this.

@Filip62 Thanks :smiley:

@Filip62 Thanks :smiley:

The current implementation results in
error: /home/minuq/.config/polybar/modules.ini:1435: Value '"upower --dump | grep G403 -A 11 | grep percentage | head -n 1 | sed 's/percentage.*\([[:digit:]][[:digit:]]%\).*/\1/' | awk '{$1=$1};1'"' of key 'exec' contains one or more unescaped backslashes, please prepend them with the backslash escape character.
for a perfectly valid command due to how it's looking for single backslashes. I assume this is the correct issue for that false-positive, since it's referenced in the relevant commits.

The current implementation results in
error: /home/minuq/.config/polybar/modules.ini:1435: Value '"upower --dump | grep G403 -A 11 | grep percentage | head -n 1 | sed 's/percentage.*\([[:digit:]][[:digit:]]%\).*/\1/' | awk '{$1=$1};1'"' of key 'exec' contains one or more unescaped backslashes, please prepend them with the backslash escape character.
for a perfectly valid command due to how it's looking for single backslashes. I assume this is the correct issue for that false-positive, since it's referenced in the relevant commits.

I think this is expected behaviour.
The value does indeed contain unescaped backslashes.
The backslash character in a config value has the meanig of a special escape character. Together with the character following right after it, an escape sequence is formed. Which gets internally replaced by polybar by the character this sequence escapes.
As of now (I haven't checked in a while though, so I may be wrong) there is only one supported escape sequence: \\
Which gets replaced by a single backslash.
The following character sequences in your config value: \( and \) do not form any supported escape sequence, thus polybar assumes these sequences should be taken literally, as they are. So the error you reported is logged to make you aware of this.
Because in the future, the character sequence \( might be a valid escape sequence, that will get replaced by (, which would change the meaning of your command.
If you want this configuration value to be taken literally, without interpreting the above mentioned character sequences as escape sequences, you need to replace them in the config value with \\( and \\). The sequence \\ gets internally replaced by a single backslash and the rest of the value is taken literally.

Makes sense, thanks for your explanation. I missed the part about it getting replaced with a single \ during parsing.


Remove the Git repository synchronization functionality

Motivation and context

This functionality has accumulated significant technical debt:

Most importantly, it does not use the current authorization system,
rendering it accessible only for admin users.

It doesn't follow the regular API conventions, and is not visible in the API
schema. This necessitates special code in the SDK.

The initialization code in base.py is not safe when multiple instances of
the server start at the same time (each instance may end up generating its
own key).

The team has decided that the cost of fixing these issues outweighs the benefit
of the functionality, so remove it.
How has this been tested?

Checklist

[x] I submit my changes into the develop branch
[x] I have added a description of my changes into the CHANGELOG file
[x] I have updated the documentation accordingly
[x] I have added tests to cover my changes
[ ] I have linked related issues (see GitHub docs)
[x] I have increased versions of npm packages if it is necessary
(cvat-canvas,
cvat-core,
cvat-data and
cvat-ui)

License

[x] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.

/check

/check

Hello!
Are there any plans to restore it in the future?
Thanks!

@PMazarovich , you are the only known user of the feature. Could you please describe how have you used the feature?

@nmanovic here it is:

manually push the "synchronise" button on CVAT
git pipeline was launched
creating a new branch with the new data
running some script to count number of errors
data moved to "valid" or "unvalid" folder depending on threshold value
push the data from "valid folder" in AWS

IMHO it was a nice automatic backup feature and I would prefer it to other methods like manually created backups by admins or even users. I understand your decision "cost of fixing vs. benefit of functionality" but nevertheless it was a useful feature and I would vote for it. :-)

@nmanovic here it is:

manually push the "synchronise" button on CVAT
git pipeline was launched
creating a new branch with the new data
running some script to count number of errors
data moved to "valid" or "unvalid" folder depending on threshold value
push the data from "valid folder" to AWS S3

@PMazarovich
Can it be implemented using web hooks? https://opencv.github.io/cvat/docs/administration/advanced/webhooks/


BasicHttpsSecurityApplicationTest is @Ignored

The BasicHttpsSecurityApplicationTest currently fails and has been ignored.

fixed w/ help from @rwinch


Genome Nexus creates variants with Reference_Allele  == Tumor_Seq_Allele2 == Tumor_Seq_Allele1

There are 154 unique variants that have different Reference_Allele and Tumor_Seq_Allele2 that are reannotated to have the same Ref_Allele and TSA2 through genome nexus.

Input:
input_1.txt
input_2.txt

Intermediate files: annotation-tools intermediate files I must add the .txt at the end or github won't allow me to upload these. My understanding it the input.txt.temp.annotated.txt is the output from Genome Nexus. But because the annotation-tools allows us to include a directory with a list of mafs or vcfs, it annotates each one of those files separately. processed.txt is all of these merged.
input_1.txt.temp.annotated.txt
input_1.txt.temp.txt
input_2.txt.temp.annotated.txt
input_2.txt.temp.txt

Processed:
processed_1.txt
processed_2.txt

More details, It seems that these variants failed annotation, but still comes up as SUCCESS in AnnotationStatus
07:14:36 [main] WARN  org.cbioportal.annotator.internal.GenomeNexusImpl - Annotated record is invalid for variant 17:7578213-7578213:1/A
07:14:36 [main] WARN  org.cbioportal.annotator.internal.GenomeNexusImpl - Annotated record is invalid for variant 7:55259516-55259516:1/G
07:14:36 [main] WARN  org.cbioportal.annotator.internal.GenomeNexusImpl - Annotated record is invalid for variant 7:55259516-55259516:1/G
07:14:36 [main] WARN  org.cbioportal.annotator.internal.GenomeNexusImpl - Annotated record is invalid for variant 17:7578213-7578213:1/A
07:14:36 [main] WARN  org.cbioportal.annotator.internal.GenomeNexusImpl - Annotated record is invalid for variant 17:7578213-7578213:1/A
07:14:36 [main] WARN  org.cbioportal.annotator.internal.GenomeNexusImpl - Annotated record is invalid for variant 17:7577572-7577572:1/T
07:14:36 [main] WARN  org.cbioportal.annotator.internal.GenomeNexusImpl - Annotated record is invalid for variant 17:7578213-7578213:1/A
07:14:36 [main] WARN  org.cbioportal.annotator.internal.GenomeNexusImpl - Annotated record is invalid for variant 6:32188298-32188298:1/C
07:14:36 [main] WARN  org.cbioportal.annotator.internal.GenomeNexusImpl - Annotated record is invalid for variant 5:112175627-112175627:1/G
07:14:36 [main] WARN  org.cbioportal.annotator.internal.GenomeNexusImpl - Annotated record is invalid for variant 17:7578213-7578213:1/A
07:14:36 [main] WARN  org.cbioportal.annotator.internal.GenomeNexusImpl - Annotated record is invalid for variant 12:112888195-112888195:1/T
07:14:36 [main] WARN  org.cbioportal.annotator.internal.GenomeNexusImpl - Annotated record is invalid for variant 3:178936083-178936084:1/AA
07:14:36 [main] WARN  org.cbioportal.annotator.internal.GenomeNexusImpl - Annotated record is invalid for variant 16:23647428-23647428:1/T
07:14:36 [main] WARN  org.cbioportal.annotator.internal.GenomeNexusImpl - Annotated record is invalid for variant 7:55259516-55259516:1/G
07:14:36 [main] WARN  org.cbioportal.annotator.internal.GenomeNexusImpl - Annotated record is invalid for variant 7:55259516-55259516:1/G
07:14:36 [main] WARN  org.cbioportal.annotator.internal.GenomeNexusImpl - Annotated record is invalid for variant 7:55259516-55259516:1/G
07:14:36 [main] WARN  org.cbioportal.annotator.internal.GenomeNexusImpl - Annotated record is invalid for variant 11:108160351-108160351:1/T
07:14:36 [main] WARN  org.cbioportal.annotator.internal.GenomeNexusImpl - Annotated record is invalid for variant 9:5073771-5073771:1/T
07:14:36 [main] WARN  org.cbioportal.annotator.internal.GenomeNexusImpl - Annotated record is invalid for variant 11:108124762-108124762:1/C
07:14:36 [main] WARN  org.cbioportal.annotator.internal.GenomeNexusImpl - Annotated record is invalid for variant 7:55259516-55259516:1/G
07:14:36 [main] WARN  org.cbioportal.annotator.internal.GenomeNexusImpl - Annotated record is invalid for variant 7:55259516-55259516:1/G
07:14:36 [main] WARN  org.cbioportal.annotator.internal.GenomeNexusImpl - Annotated record is invalid for variant 7:55259516-55259516:1/G
07:14:36 [main] WARN  org.cbioportal.annotator.internal.GenomeNexusImpl - Annotated record is invalid for variant 18:60985749-60985751:1/AGG

More details, It seems that these variants failed annotation, but still comes up as SUCCESS in AnnotationStatus
07:14:36 [main] WARN  org.cbioportal.annotator.internal.GenomeNexusImpl - Annotated record is invalid for variant 17:7578213-7578213:1/A
07:14:36 [main] WARN  org.cbioportal.annotator.internal.GenomeNexusImpl - Annotated record is invalid for variant 7:55259516-55259516:1/G
07:14:36 [main] WARN  org.cbioportal.annotator.internal.GenomeNexusImpl - Annotated record is invalid for variant 7:55259516-55259516:1/G
07:14:36 [main] WARN  org.cbioportal.annotator.internal.GenomeNexusImpl - Annotated record is invalid for variant 17:7578213-7578213:1/A
07:14:36 [main] WARN  org.cbioportal.annotator.internal.GenomeNexusImpl - Annotated record is invalid for variant 17:7578213-7578213:1/A
07:14:36 [main] WARN  org.cbioportal.annotator.internal.GenomeNexusImpl - Annotated record is invalid for variant 17:7577572-7577572:1/T
07:14:36 [main] WARN  org.cbioportal.annotator.internal.GenomeNexusImpl - Annotated record is invalid for variant 17:7578213-7578213:1/A
07:14:36 [main] WARN  org.cbioportal.annotator.internal.GenomeNexusImpl - Annotated record is invalid for variant 6:32188298-32188298:1/C
07:14:36 [main] WARN  org.cbioportal.annotator.internal.GenomeNexusImpl - Annotated record is invalid for variant 5:112175627-112175627:1/G
07:14:36 [main] WARN  org.cbioportal.annotator.internal.GenomeNexusImpl - Annotated record is invalid for variant 17:7578213-7578213:1/A
07:14:36 [main] WARN  org.cbioportal.annotator.internal.GenomeNexusImpl - Annotated record is invalid for variant 12:112888195-112888195:1/T
07:14:36 [main] WARN  org.cbioportal.annotator.internal.GenomeNexusImpl - Annotated record is invalid for variant 3:178936083-178936084:1/AA
07:14:36 [main] WARN  org.cbioportal.annotator.internal.GenomeNexusImpl - Annotated record is invalid for variant 16:23647428-23647428:1/T
07:14:36 [main] WARN  org.cbioportal.annotator.internal.GenomeNexusImpl - Annotated record is invalid for variant 7:55259516-55259516:1/G
07:14:36 [main] WARN  org.cbioportal.annotator.internal.GenomeNexusImpl - Annotated record is invalid for variant 7:55259516-55259516:1/G
07:14:36 [main] WARN  org.cbioportal.annotator.internal.GenomeNexusImpl - Annotated record is invalid for variant 7:55259516-55259516:1/G
07:14:36 [main] WARN  org.cbioportal.annotator.internal.GenomeNexusImpl - Annotated record is invalid for variant 11:108160351-108160351:1/T
07:14:36 [main] WARN  org.cbioportal.annotator.internal.GenomeNexusImpl - Annotated record is invalid for variant 9:5073771-5073771:1/T
07:14:36 [main] WARN  org.cbioportal.annotator.internal.GenomeNexusImpl - Annotated record is invalid for variant 11:108124762-108124762:1/C
07:14:36 [main] WARN  org.cbioportal.annotator.internal.GenomeNexusImpl - Annotated record is invalid for variant 7:55259516-55259516:1/G
07:14:36 [main] WARN  org.cbioportal.annotator.internal.GenomeNexusImpl - Annotated record is invalid for variant 7:55259516-55259516:1/G
07:14:36 [main] WARN  org.cbioportal.annotator.internal.GenomeNexusImpl - Annotated record is invalid for variant 7:55259516-55259516:1/G
07:14:36 [main] WARN  org.cbioportal.annotator.internal.GenomeNexusImpl - Annotated record is invalid for variant 18:60985749-60985751:1/AGG

I split up the two files because interestingly, I found that when I took input_2.txt and I reduced it to just the 5 minimal columns (Chromosome, Tumor_Sample_Barcode, Reference_Allele, Tumor_Seq_Allele2,Start_Position) the variants were able to be annotated correctly...

I split up the two files because interestingly, I found that when I took input_2.txt and I reduced it to just the 5 minimal columns (Chromosome, Tumor_Sample_Barcode, Reference_Allele, Tumor_Seq_Allele2,Start_Position) the variants were able to be annotated correctly...

@thomasyu888 Thanks for putting this together and doing an initial investigation! Especially having all the failing ones together in input_1.txt made it a little easier to debug.
I'm however still slightly confused about the input files. The very first input file should be a VCF file, no? Or is input_1.txt a MAF file you get from the centers?
Reason I'm asking is b/c the failing variants look kind of questionable.  All these variants in that file have incorrect notations:
17      7578212 CG      CA
7       55259515        CT      CG

They should be SNVs, so in both VCF and MAF there would not be a C prefix.
If for some reason one would really want to call them a DNP, then still these variants are off by one:

Even if we were to assume in our code that the DNPs are always off by one when the prefixes match in ref and alt, you can imagine that some centers might have given the correct position and then things get extremely hairy
Let me know if you'd like me to elaborate further

@inodb None of these are VCF files but actually input from center MAF files.  Can you further elaborate?   Am i correct to assume that you are telling me that this is an issue with center input files?  It's strange that there are just some variants that are incorrect from the center side.
Whats interesting is that these technically failed, but aren't annotated with Annotation_Status = Fail.  Can you look into that?

@thomasyu888 agreed we should not annotate when AnnotationStatus = FAIL. Filed an issue for that: https://github.com/genome-nexus/genome-nexus-annotation-pipeline/issues/172
As you can see in my examples the reference base is incorrect for all these examples and it doesn't seem possible for us to guess what the position should have been. Somehow they are off by one. Also it really isn't proper MAF format if there is no End_Position column, so that might be something to raise as well. I would say: either they should submit proper VCF or proper MAF, but this looks like an in-between. IMO at center submission there should be a couple of validation checks for the files received and one of those should be "is it proper MAF/VCF".

Thanks @inodb.  To clarify, my concern was that these variants weren't actually being annotated with Annotation_Status = FAIL.  (not actually sure if FAIL is the word used in these scenarios).  If you download the processed.txt, you will see that Annotation_Status is SUCCESS. Apologies if that was what you were already referring to in that ticket.
In theory, it makes the most sense to put as much onus back onto the sites as possible, but this has been pretty difficult in practice. End_Position was not required as a column for vcf2maf so we never put it into our validation checks.   We actually do a series of file validation checks on all the files that are uploaded, but they are definitely not comprehensive.   We could technically add End_Position as a required column, but we must give the GENIE consortium 6 months advanced notice for file changes, and I want to avoid that at all possible.

@thomasyu888 I see - that makes sense! Thanks for clarifying both of these things!
I think we can keep the file format the same for now, but could be something to request in the future. Do you have a link to the official requested file format?
For the data from this specific center. We should get back to them and ask for these particular variants why the position is off by one. Since they are all ONP or DNP it does seem like a systematic error. We could manually fix them, but in that case we should maybe just do a one off manual fix of the submitted file

@inodb.  The file format is behind a private GENIE page, but here is a screenshot:

I actually only pull in variants with Annotation_Status = SUCCESS as a filter, if these were annotated with FAIL then they wouldn't appear in the release.  That would then put the onus back on the centers themselves.  One thing I need to do is eventually provide sites with all the variants that failed annotation so they can fix it in their input files.


Package for distribution

It would be good to package this script for distribution and release it in such a way that it can be installed in a single command with brew or pip or something similar.
This depends on #3 and probably requires that the Dropbox Python SDK being released on PyPI.

dropbox==2.2.0 is the newest version of the dropbox module on pypi. (requires urllib3==1.11)

The naming convention is a bit weird, but dropbox 2.2.0 on pypi actually uses Dropbox API v1. It was last updated in September 2014.
I'm using the Python SDK for Dropbox API v2 (which is still in preview).

ooOOOoohhhhh

It looks like dropbox 3.x (currently 3.1.2) is now on pypi.
I think this is still a preview release, though.

Okay, this is finally done (in 2b8594483ae882ec0941e2ec49e5e10c8c0f873c)!!
We're using dropbox>=6.1,<7, which should be okay. The API (https://github.com/dropbox/dropbox-sdk-python) is still in preview though. If there are backwards-incompatible changes, hopefully they respect semantic versioning…


Improve error handling

Errors are currently hard to catch, they’re not strongly typed so I had to let my code throw the error first, then find the name, then add an catch clause to check for that error name
Being able to do instance checking would be much nicer
if isinstance(e, ResourceNameAlreadyExistsError):
    ...

or at least an enum of error types per namespace:
if e.name == core.Errors.RESOURCE_NAME_ALREADY_EXISTS:
    ...

or something like:
if isResourceNameAlreadyExistsException(e):
    ...

There is ongoing work to improve error handling in both the Python SDK but also the API in general. I'll keep this FR up-to-date when this feature has been released. We'll likely be going with the first option where we subclass PalantirRPCException for each error.


WIP: Support async promotion

Update promotion req/resp objects, adding async flag, callbackUrl, promotionId, etc.

@matejonnet please help to review this.


[berkeleydb:x64-windows-static] build failure

Host Environment

OS: Windows 7
Compiler:  cl Microsoft (R) C/C++ Optimizing Compiler Version 19.10.25019 for x64

To Reproduce
Steps to reproduce the behavior:
vcpkg install --triplet x64-windows-static berkeleydb
Failure logs
Error: Building package berkeleydb:x64-windows-static failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with .\vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: berkeleydb:x64-windows-static
Vcpkg version: 2020.02.04-nohash
Additionally, attach any relevant sections from the log files above.
Additional context
In config-x64-windows-static-out.log:
-- The C compiler identification is unknown
-- The CXX compiler identification is unknown
CMake Error at CMakeLists.txt:2 (project):
No CMAKE_C_COMPILER could be found.
Tell CMake where to find the compiler by setting either the environment
variable "CC" or the CMake cache entry CMAKE_C_COMPILER to the full path to
the compiler, or to the compiler name if it is in the PATH.
CMake Error at CMakeLists.txt:2 (project):
No CMAKE_CXX_COMPILER could be found.
Tell CMake where to find the compiler by setting either the environment
variable "CXX" or the CMake cache entry CMAKE_CXX_COMPILER to the full path
to the compiler, or to the compiler name if it is in the PATH.
I have run vcpkg intgrate install
E:\src\vcpkg>vcpkg integrate install
Applied user-wide integration for this vcpkg root.

All MSBuild C++ projects can now #include any installed libraries.
Linking will be handled automatically.
Installing new libraries will make them instantly available.

CMake projects should use: "-DCMAKE_TOOLCHAIN_FILE=E:/src/vcpkg/scripts/buildsys
tems/vcpkg.cmake"

I have set CC and CXX to cl, and cl is in PATH:
E:\src\vcpkg>printenv CC
cl

E:\src\vcpkg>printenv CXX
cl

E:\src\vcpkg>cl
Microsoft (R) C/C++ Optimizing Compiler Version 19.10.25019 for x64
Copyright (C) Microsoft Corporation.  All rights reserved.

usage: cl [ option... ] filename... [ /link linkoption... ]

No problem for me. No need to set %CC% or %CXX%

It doesn't work neither setting nor not setting %CC% or %CXX%. Is this thing really usable ?

Did you select MSVC features in Visual Studio Installer?

Did you select MSVC features in Visual Studio Installer?

I dont' remember, how to check and reset?

I can new ATL, MFC, WIN32 project in visual studio IDE, does that mean I selected MSVC features?

If I use the cmake installed by vcpkg to build a hello word, however, it seems to work:
E:\src\hello>cmake .
-- Building for: Visual Studio 15 2017
-- The C compiler identification is MSVC 19.10.25019.0   <=== Seems It could identify the C compiler
-- The CXX compiler identification is MSVC 19.10.25019.0
-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/
2017/Community/VC/Tools/MSVC/14.10.25017/bin/HostX86/x86/cl.exe
-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/
2017/Community/VC/Tools/MSVC/14.10.25017/bin/HostX86/x86/cl.exe -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studi
o/2017/Community/VC/Tools/MSVC/14.10.25017/bin/HostX86/x86/cl.exe
-- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studi
o/2017/Community/VC/Tools/MSVC/14.10.25017/bin/HostX86/x86/cl.exe -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Configuring done
-- Generating done
-- Build files have been written to: E:/src/hello

E:\src\hello>ls
ALL_BUILD.vcxproj          CMakeLists.txt            ZERO_CHECK.vcxproj
ALL_BUILD.vcxproj.filters  Tutorial.sln              ZERO_CHECK.vcxproj.filters
CMakeCache.txt             Tutorial.vcxproj          cmake_install.cmake
CMakeFiles                 Tutorial.vcxproj.filters  hello.c

If I goto the berkeleydb source folder and run cmake . it also could find C compiler.
E:\src\vcpkg\buildtrees\berkeleydb\src\db-4-c2cacfc4e9>cmake .
-- Building for: Visual Studio 15 2017
-- The C compiler identification is MSVC 19.10.25019.0
-- The CXX compiler identification is MSVC 19.10.25019.0
-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/
2017/Community/VC/Tools/MSVC/14.10.25017/bin/HostX86/x86/cl.exe
-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/
2017/Community/VC/Tools/MSVC/14.10.25017/bin/HostX86/x86/cl.exe -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studi
o/2017/Community/VC/Tools/MSVC/14.10.25017/bin/HostX86/x86/cl.exe
-- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studi
o/2017/Community/VC/Tools/MSVC/14.10.25017/bin/HostX86/x86/cl.exe -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Configuring done
-- Generating done
-- Build files have been written to: E:/src/vcpkg/buildtrees/berkeleydb/src/db-4
-c2cacfc4e9

E:\src\vcpkg\buildtrees\berkeleydb\src\db-4-c2cacfc4e9>cmake . -G"Visual Studio 15 2017" -Ax64
?

I can install berkeleydb:x64-windows-static successfully with VS2017 15.9.21 and latest VCPKG. What's the version of your VS?

@coopci  Could you please run .\vcpkg.exe install berkeleydb:x64-windows-static --debug and provide the log to us?

@coopci Has this issue resolved?

We haven't been able to repro this; if more information comes up, or this issue appears again, please reopen


guide: new DVC Concepts section

Per https://github.com/iterative/dvc.org/pull/431#pullrequestreview-253571711
There should be a section or a few sections called Basic Concepts in the user guide that is/are properly written on a user-level language explaining some concepts. The glossary tooltips could point to these pages too.

we need to explain concepts like Cache, Remote, Wokspace, etc, and their relationships (with diagrams if needed).
From https://github.com/iterative/dvc.org/issues/550#issuecomment-544162594 below

Figure out a connection to glossary tooltips (currently special md files with Frontmatter in content/docs/user-guide/basic-concepts/ — see #1395): Just link to the Concepts? Use a similar engine (with Frontmatter)? Merge completely?
UPDATE: Skip to https://github.com/iterative/dvc.org/issues/550#issuecomment-673585050 for summary
UPDATE: Specific plan
Use contents from #1655 as needed.

Do we need the changes in package.json, src/components/Documentation/Markdown/Tooltip/index.tsx, src/gatsby/models/glossary/index.js, and src/utils/front/glossary.ts from iterative/dvc.org/pull/1944 ?
[x] Workspace (#2197)
[x] DVC Project (vs. Git/DVC Repository) [#2754]
[ ] (from cmd ref) (DVC) Metafiles
[ ] (from cmd ref) DVC/Project Cache
[ ] (from cmd ref) Data Pipeline(s)
[ ] (from cmd ref) Metrics & Plots
[ ] (from cmd ref) Remote (Storage)
[ ] (from cmd ref) Stage
& update some of the links around this term that currently go to run/stage.
(Some should link to the future pipelining guide, see #2883)
[ ] (from cmd ref) (Stage) Output
[ ] (from cmd ref) (Stage) Dependency
[ ] Run-Cache?
[ ] Garbage Collection clarifications (in cache or remote pages, see #2169)
[ ] Workspace clarifications? Discussed in #1127
Add Further Reading sections to all Basic Concepts documents? (#2127)

[x] Look into #1395 after or along with this one.
Consider also a related DVC Principles section (more philosophical, maybe in the Concepts section index)? See https://github.com/iterative/dvc.org/issues/550#issuecomment-544106096 below.
UPDATE: Maybe use the section index for this or/and What is DVC?.

@shcheklein is this not basically the same as #542?

@jorgeorpinel iIt might play that role indeed. Let's keep it open anyway and see if a page for the glossary enough or not.

@jorgeorpinel also, this one is related - https://github.com/iterative/dvc.org/issues/53 . I though that one can be a part of the Basic Concepts.

Perhaps we can call it DVC Principles, similar to:

From https://www.hashicorp.com/products/terraform

@jorgeorpinel it seems to me like some parts from the https://dvc.org/doc/understanding-dvc . A bit philosophical. And there should be a section like this, but also we need to explain concepts like Cache, Remote, Wokspace, DVC-file, etc, their relationship (with diagrams if needed).

From https://github.com/iterative/dvc.org/issues/727#issuecomment-571407120:

https://dvc.org/doc/command-reference/cache,
https://dvc.org/doc/command-reference/metrics,
https://dvc.org/doc/command-reference/pipeline, and
https://dvc.org/doc/command-reference/remote

have useful, unique content but I'm not sure the cmd ref is the best place for those explanations.

Should we take the move the explanation about those concepts to this new guid and only leave a very stripped down index for those commands? Which could link to the Basic Concepts section, of course.

From https://github.com/iterative/dvc.org/pull/1581#discussion_r467630993:

it's way more than a single page like this. Good example of a basic concept is cache, or run cache - they alone can take a proper page

So consider breaking up Basic Concepts or DVC Concepts into a full User Guide sub-section.

I'm going to summarize the goals and plans around this issue:

[ ] There should be a page or section (maybe called Basic Concepts in UG, see example in this closed PR) — properly written on a user-level language (closer to UC) — explaining some concepts and DVC philosophy

concepts like Cache, Remote, Wokspace, etc, and their relationships (with diagrams if needed)

Possibly extract concept explanations from cmd refs (e.g. cache, dag, metrics/plots, remote)
[ ] Find other issues that would be included in solving this (e.g. #53).
Consider also a related DVC Principles section (more philosophical, maybe in the Concepts section index)? See https://github.com/iterative/dvc.org/issues/550#issuecomment-544106096 above.
[ ] Figure out a connection to glossary tooltips (currently special md files with Frontmatter in content/docs/user-guide/basic-concepts/ — see #1395): Just link to the Concepts? Use a similar engine (with Frontmatter)? Merge completely?

From discussion in #1915:

... we just need to figure out a good way to add these landing pages. Should it be one guide with a section per concept? A subsection under Use Cases (which are kind of landing pages right now)?

For SEO purposes, one concept per URL is ideal. The use cases show this in practice: the versioning use case and tutorial have the strongest search results and ranking after the home page.
As someone new to DVC, a Basic Concepts section for the UG makes a lot of sense, though. The UG is mostly problem:solution "how to" material, so standalone concept articles seem out of place.
Applying the above to the "Data Pipelines" concept: I suggest we add a use case and also add a Basic Concepts section with pipelines, among other concepts.
What do you think @jorgeorpinel ?

For SEO purposes, one concept per URL is ideal

What about # anchors though? Like guide/concepts#cache. We just don't want a bunch of very short pages like https://dvc.org/doc/user-guide for example, I think.
BTW I'm not convinced these pages are the best landing pages. They are meant to explain what these concepts mean IN DVC, so while they can definitely point to a bunch of other relevant docs for those who do land there, I don't think their purpose is to drive traffic.  Use Cases do have that purpose though, as well as the other sections of dvc.org (not /doc).
That said, if each section requires long explanations then we can definitely make them individual pages.

The UG is mostly problem:solution "how to" material

Hmmm not really, only the How To section (currently in UG due to a lack of a better structure) and certain guides (which should probably be in How To) have that intention. But anyway, Basic Concepts can definitely fit in the UG, I think (also not how-to material).

I suggest we add a use case and also add a Basic Concepts section with pipelines

Let's just focus on the Basic Concepts section for now because Use Cases are very very tricky and yes, we already have a Pipelines one planned 🙂

What about # anchors though? Like guide/concepts#cache.

The anchors will show up as sub-links on a listing, so they are effective, but the overall page needs to rank for that to happen.  Agree that short pages aren't a good idea, and that these types of UG pages aren't necessarily good for landing pages.

But anyway, Basic Concepts can definitely fit in the UG, I think (also not how-to material).

Is there an existing doc in UG that is a good example of what "fits"? I understand my initial assessment doesn't match because certain items don't belong and or aren't intended as how-to material. Seems like Managing External Data or Large Dataset Optimization are in the appropriate style... is that about right for the Basic Concepts doc?

Let's just focus on the Basic Concepts section for now because Use Cases are very very tricky and yes, we already have a Pipelines one planned.

Sounds good. If it's in the works then things are on the right track SEO-wise there. I have some ideas that could make a single-URL Basic Concepts work within your original plan and also address some of the SEO patterns. Will take that up and lay out ideas/outline in a new PR.

Is there an existing doc in UG that is a good example of what "fits"?

I think this is our main guide: https://dvc.org/doc/user-guide/dvc-files-and-directories. Another proper guide would be https://dvc.org/doc/user-guide/large-dataset-optimization. What is DVC and DVCignore are also OK. These explain how things work.
Thinking about it, most of the other ones do at least contain how-to material. But as long as that's not their main purpose, they can fit in the UG.

UPDATE: An important consolidation of "cache" mechanism explanation happened in #2075

UPDATE: An important consolidation of "cache" mechanism explanation happened in #2075

Currently working on this https://github.com/iterative/dvc.org/tree/ug-basic-concepts-feb-21 branch.

Please link this issue to the PR for that branch when ready.

I'll update the issue description with all items from other issues. I think this can be the main BC issue.
@jorgeorpinel @shcheklein

Howdy @casperdcl. Other than the tooltips you've added recently (in #2359) are you still planning to work on this? Please un-assign otherwise 🙂

I'm not altogether sure what it really means to be assigned to an epic - assigned to push others to some the individual issue(s)? Given that the title is "new DVC Concepts section" there may be others better placed to do that. Unassigning for now.

Assigned in general would mean someone is working on it or plans to do so soonish. Agree that it can be misleading to be assigned to an epic but it happens e.g. #1400.

Lowering priority. Is this still in plans at all or should we close it?


Key error with file data/Imagenet64/metadata.pkl

Hello!
I am trying to make to train a model myself using Imagenet64x64 for a test; on a MAC using "mps" device.
It took me a little while to see that after downloading Imagenet64x64, I have to
— use "loadImagenet64.py" to generate .pkl files in an "Imagenet64" folder.
— THEN use "make_massive_tensor.py" to make a large .pt file.
— THEN use "train.py" which will call "model_trainer.py"
Apparently (tell me if I am wrong):
— "loadImagenet64.py" needs "Imagenet64_train_part1.zip" and "Imagenet64_train_part2.zip".
Imagenet64x64 does not have these files. It rather has:
train_data_batch_1, train_data_batch_2, train_data_batch_3... etc
— I changed the code in "loadImagenet64.py" to make a series of img and label .pkl files within the "Imagenet64" folder.
— Then, when running "make_massive_tensor.py", I get the following errors:
Shape error with file data/Imagenet64/n.pkl
Key error with file data/Imagenet64/metadata.pkl

— I probably did something wrong in "loadImagenet64.py" with the formatting of pickles. But I do not know where that is happening. Dict's keys seem fine: loadImagenet64 seems to replace 'data', 'mean', 'labels' found in Imagenet64 with 'data', 'mean', 'labels'.
=> Where did you get "Imagenet64_train_part1.zip" OR how did you make them?
=> How to deal with the shape and dict keys within those .pkl ?
Thank you for your help!!!
O.

Apparently (tell me if I am wrong):
— "loadImagenet64.py" needs "Imagenet64_train_part1.zip" and "Imagenet64_train_part2.zip".
Imagenet64x64 does not have these files. It rather has:
train_data_batch_1, train_data_batch_2, train_data_batch_3... etc

The loadImagenet64.py script loads in the data directly through the zip files downloaded from the ImageNet website. So, don't unzip the archives as this script works with zipped data.
https://github.com/gmongaras/Diffusion_models_from_scratch/blob/main/data/loadImagenet64.py#L19

"img" type is numpy.ndarray
Did you download the numpy version of ImageNet? I think the scripts work off the base version as opposed to the numpy version of ImageNet which may be causing the issue here.

Just a heads up: As for training on a mac, I haven't added mps support to the repo as in PyTorch 1.0, the MPS device had all types of weird issues. I'm not sure if that was fixed in PyTorch 2.0. For inference, this may be fine, but for training, I think you may run into multiple issues trying to get it to work properly.
Hope this helps! Let me know if you run into any more issues.

Hello!
Thank you very much for your answer!
— For Imagenet64_train_part1.zip in your loadImagenet64.py, I have been waiting forever to get an authorization for Download from the ImageNet website. I am not sure they are still active. So I eventually downloaded Imagenet64 from Kaggle.com
There are folders with the same name as your ZIP files. But zipping them does not seem to work either.
— I changed a bit of code to get MPS device to work ok on Apple Silicon. In fact, I used MPS device declaration within PyTorch on previous projects and that worked. I do not fully understand as I am not a specialist. But it seems to be working like a charm now with PyToch 2 on MacOS 12.3+.
— I will keep you posted with my tests and if I can make it work. I may ask for help from someone around me too.
Thank you again,
O.

"One more thing": :)
Do you know the shape of the matrixes in your .pkl files for "img" and "label"?

Kaggle dataset uses the numpy version
< Yes it does. But that is not the problem.

it looks like img is a flattened numpy array
< That makes sense here too! This is not what I have.
img is 128116x12288
The problem is that just flattening it will not work because 128116 x 12288 =<PHONE_NUMBER>
And I get the error:
RuntimeError: shape '[3, 64, 64]' is invalid for input of size<PHONE_NUMBER>

I have a closer look at it!
O.

I think 128116x12288 is batch size by image size. So you have a batch size of 128116 and an image size of 12288 which is a multiple of 3x64x64.


When uploading source code?

When uploading source code?

When uploading source code? @KiveeDong

soon, in this week.

+1

+1


Changed Twig function class to a non-abstract one

Need to make use of the Twig_SimpleFunction which extends of Twig_Function as you can't instantiate an abstract class.

Hey @chrislind
Thanks for checking out the integration and for this pull request! I think what you ran into is an error that appears in Timber as well.
So before pulling this in, I’d like you to check if it works if we’d use the class that Timber provides for handling different Twig versions. So instead of writing:
$twig->addFunction( new \Twig_Function( 'Product', function( $pid ) {

could you try using
$twig->addFunction( new \Timber\Twig_Function( 'Product', function( $pid ) {

and see if you still run into the error?

Why is this not merged? This package is useless without this fix.

\Timber\Twig_Function works for me.

Closing this, because it was solved by #5. Sorry for the longer wait!


Multiple code improvements - squid:S1161, squid:ClassVariableVisibilityCheck, squid:S1444, squid:S3008

This pull request is focused on resolving occurrences of Sonar rules
squid:S1161 - "@Override" annotation should be used on any method overriding (since Java 5) or implementing (since Java 6) another one.
squid:ClassVariableVisibilityCheck - Class variable fields should not have public accessibility.
squid:S1444 - "public static" fields should be constant.
squid:S3008 - Static non-final field names should comply with a naming convention.
This pull request removes 120 minutes of technical debt.
You can find more information about the issue here:
https://dev.eclipse.org/sonar/rules/show/squid:S1161
https://dev.eclipse.org/sonar/rules/show/squid:ClassVariableVisibilityCheck
https://dev.eclipse.org/sonar/rules/show/squid:S1444
https://dev.eclipse.org/sonar/rules/show/squid:S3008
Please let me know if you have any questions.
George Kankava

Changes Unknown when pulling fb30f0e862fd9bd2d0fbdbe069b05d6f737ba5a4 on DevFactory:release/multiple-code-improvements-fix-10 into ** on clun:master**.


Fix several spec tests

There are only 51 tests to go!  See commit messages for further information.

Thanks! I think some of the other 51 tests will require a bit deeper work :). In any case, glad to have you working on this. It's something I'd like to do myself if I had more time, but I just don't right now.


fix(ble-android): propagate GATT write errors to the application

This will give the application a chance to get informed whenever there is an error in the GATT characteristic write operations, and eventually retry the operation.
I was only able to (re)produce this ErrorGattWriteRequestBusy error, I'm not sure if there are other errors that should be surfaced as well.
Maybe all errors should be reported?

Thanks, I will definitely look into other error types and see if this can be expanded upon. Also to be able to use this exception type for other platforms (depending on the error reporting available in their native APIs)


solved issue dark mode and light mode

solved issue dark mode and light mode

[X]  bug fix
[X]  Now it's ready for merge.

video:
https://github.com/Priyaaa1/StartConnect-Hub/assets/115735153/ff65e17a-cc50-4ed1-8f98-cd5f04471d93
I'm a GSSOC Contributor.

@Priyaaa1 please merge it.

@nikhildeshmukh170 kindly mention the issue that you resolved.

ISSUE NUMBER- #531

@nikhildeshmukh170 this issue is not assigned to you

@Priyaaa1 assign me this issue

@nikhildeshmukh170 comment in that issue for the assignment, so that I can assign you.

issue #612

@priyaaa1 please update level


Make "Duplicate setter" error show at design/preview time

Is your feature request related to a problem? Please describe.
With the recent changes for styling, an exception is now thrown if duplicate setters are placed in the same Style/ControlTheme block:
<!-- This was previously swallowed, now throws a runtime exception -->
<Style Selector="Control">
    <Setter Property="Height" Value="20" />
    <Setter Property="Height" Value="32" />
</Style>

The problem is this exception is thrown only at runtime, which is really inconvenient, and it really should be caught in the designer when the Xaml is parsed.
As a side note, +1 for the error message with this though. Including the full Selector (including where nested) was really helpful to find out where I was mistakenly doing this.

Ideally, we need warnings support in the XAML compiler. Which later can be configured by the developer as errors if they will.
But before that, it shouldn't be too hard to add a transformer with validation in the compiler.


data preparation with python

Hi, I tried to prepare the data with cv2 resize function instead of matlab imresize, the training loss is not bad but the psnr performance is far worse than the paper. Any idea about that? Does it only due to the difference between opencv and matlab?

Hi, the performance of cv2 resize function in opencv is worse than matlab imresize. Check this discussion.
You can try to use the matlab imresized image as input to test your model (or use cv2 resized image to test my model), for finding out the problem. BTW, maybe scripy.misc.imresize is a good choice, you can have a try.

@huangzehao thx for the reply, I also tried scripy.misc.imresize, the performance was a little bit better than opencv's function, but still much worse than Matlab. I will follow your suggestion and had a test. Thx again

Close the issue. You can reopen it if you have any new progress.


Compilation takes way more time in new version

Description
Hey Jax team thanks for the amazing work you are all doing with this project.
I am working with Jax for quite sometime now and ever since the 0.4.27 update I have been getting x5 to x10 more compilation time on my code without changes.
Its quite a bit of code and I don't know how you guys can reproduce what I am seeing but I will just report some numbers on my machine using JAX_LOG_COMPILES :
Jax Version 0.4.26:
Finished jaxpr to MLIR module conversion jit(train) in 2.1959640979766846 sec
Finished XLA compilation of jit(train) in 21.94405436515808 sec

Jax Version 0.4.27 and 0.4.28:
Finished jaxpr to MLIR module conversion jit(train) in 2.4314699172973633 sec
Finished XLA compilation of jit(train) in 97.583487033844 sec

Again this is the same code with exactly the same dependencies only difference is Jax's version. Also noticed that recompilation is triggered for parts of my code in version 0.4.28.
What do you guys think?
System info (python version, jaxlib version, accelerator, etc.)
jax:    0.4.28
jaxlib: 0.4.28
numpy:  1.26.4
python: 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0]
jax.devices (1 total, 1 local): [cuda(id=0)]
process_count: 1
platform: uname_result(system='Linux', node='apollo', release='6.5.0-26-generic', version='#26~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Mar 12 10:22:43 UTC 2', machine='x86_64')

$ nvidia-smi
Wed May 15 15:53:39 2024
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 550.54.15              Driver Version: 550.54.15      CUDA Version: 12.4     |
|-----------------------------------------+------------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id          Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |           Memory-Usage | GPU-Util  Compute M. |
|                                         |                        |               MIG M. |
|=========================================+========================+======================|
|   0  NVIDIA GeForce RTX 3070 Ti     Off |   00000000:01:00.0 Off |                  N/A |
| 33%   42C    P2             71W /  290W |     904MiB /   8192MiB |     19%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+

+-----------------------------------------------------------------------------------------+
| Processes:                                                                              |
|  GPU   GI   CI        PID   Type   Process name                              GPU Memory |
|        ID   ID                                                               Usage      |
|=========================================================================================|
|    0   N/A  N/A      1850      G   /usr/lib/xorg/Xorg                            365MiB |
|    0   N/A  N/A      2091      G   /usr/bin/gnome-shell                           70MiB |
|    0   N/A  N/A    622325      G   ...irefox/4090/usr/lib/firefox/firefox          0MiB |
|    0   N/A  N/A    650168      G   ...erProcess --variations-seed-version         59MiB |
|    0   N/A  N/A    841800      C   python                                        160MiB |
+-----------------------------------------------------------------------------------------+

Well, we'd love to dig into why. However, we'll need a way to reproduce the problem.
Given it is apparently due to XLA compilation, it's possible an HLO dump will be enough for us. You can grab one  by setting XLA_FLAGS=--xla_dump_to=/somewhere, zipping up somewhere and attaching it to this bug.  Up to you.

Thank you for taking a look into this.
I hope I did this correctly and I am not wasting your time, here is the zip with two folders for the two different versions: xla_dump.zip
I took a brief look and in the 0.4.26 version the last file that was generated was module_0042.jit_train.ptx. This file was significantly longer in the 0.4.28 version (~66000 vs ~99000 lines), however it is unclear to me what this means.
Moreover, in the 0.4.28 dump  you can see all the files generated after the initial compilation and apparently this happens in a callback that I have for reporting training progress. (why would this be triggered in the new version..)

Any updates on this? I appreciate any help thank you!

Taking a look at different module_0042.jit_train.sm_8.6_gpu_after_optimizations.txt files it looks like the new version creates some fused_add_xor operations that do not exist in the old version.
They are approximately 15000 lines of operations. I don't know if that helps but nearly all of them refer to _threefry_split and uniform so they have to do with jax.random.

Checking all possible options:
jax.config.update("jax_threefry_partitionable", True)
jax.config.update("jax_default_prng_impl", "threefry2x32")

Still the same long time.

Turns out this was due to internal changes of Flax. Fixed after a lot of work.


theme breaks after update

there is a new issue with grav 1.7.10+ (?) that the custom/ folder inside the akazie-wood folder gets overwritten by the updater.
we're working on it. for now, you can back up your custom/ folder before the update and then overwrite it after the update to keep your modifications.

issue resolved on grav admin plugin 1.10.14


http-client/application-name update from capability to configuration in test-suites

In test-suites, In multiple places, we are reading data from the config file. In which, multiple services have an attribute application-name which will be parsed from chosen object. In v1.0.0, http-client/application-name is present in capability class, but in v2.0.0, it is changed to configuration class. So, the path needs to be updated wherever applicable

[x] /v1/bequeath-your-data-and-die
[x] /v1/regard-application
[x] /v1/disregard-application
[x] /v1/list-applications

Fixed as part of pull #219


Any COCO pretrained models Yet?

Hi, was wondering if you have any COCO pre-trained models (and withFPN) for cutmix regularization under pytorch implementation yet? Any plans for future updates?

@Eldad27
Unfortunately, we don't have any plan to train and provide object detection models using CutMix now.
Currently, only the ImageNet-pretrained models are available which can be fine-tuned for downstream tasks.


update twikoo version

Hi @OnlyFor,
Can you change the target branch to dev?

Hi @OnlyFor,
Can you change the target branch to dev?

Done.


Inquiry About Reproduction Details of D.5 Section in the CPL Appendix

Hi,
Thank you for sharing this great work! I’m trying to reproduce the results from Appendix D.5, specifically the D4RL experiments. Could you please provide more details about the dataset and model parameters used in this part? For example:
Any preprocessing steps applied to the D4RL dataset.
The exact model architecture and hyperparameter settings.
Your guidance would be immensely helpful. Thank you in advance!

Hi! I just updated the README to link to the repo we used for these experiments. Sorry it was missing originally! The code is found here https://github.com/jhejna/cpl-human and was open-sourced a while ago.

Thank you for your reply！


Create CloudWatch Logs for Lambda functions

Use Case

I need to do the following per Lambda function when using any of the constructs that create a Lambda function:
       new logs.LogGroup(this, "dummy-logs", {
            logGroupName: `/aws/lambda/${dummyFn.lambdaFunction.functionName}`,
            removalPolicy: cdk.RemovalPolicy.DESTROY,
            retention: logs.RetentionDays.ONE_WEEK,
        });

Otherwise, it won't create an log groups per Lambda which is annoying for the following reasons:

Stale log groups which do not vanish when the stack is deleted
Cost for tracking unmanaged log groups (How do people handle these?)

Proposed Solution

Make it possible to auto-create the log group, either via logGroupProps/existingLogGroup or via a method on the constructs like createLogGroup().
This will be a non-breaking change since the current behavior can still be used.
Other

[X] :wave: I may be able to implement this feature request
[ ] :warning: This feature might incur a breaking change

This is a :rocket: Feature Request

Thanks - we'll take a look.

We're pretty sure this isn't possible. We use the Lambda.Function construct internally, and there is no way to pass an existing Log Group nor LogGroupProps on creation of a that construct. FunctionProps does allow you to specify the retention interval for log entries, but other than that the construct takes complete control of creating the log group. The logGroup property of the Function construct is readonly, so can't be set.


new logo

The current logo is just a creative commons image. We should have something better than that. :)

@getquill/maintainers any of you has design skills or knows someone that could prepare a logo for the project? It doesn't need to be fancy, just something that has the project name and a quill.

I may be able to find somebody :)

@lvicentesanchez thanks! :)

suggestion

I haven't heard from the designer yet. I can contact him and see if he has
done something. otherwise, I like your proposal.
On 14 May 2016 22:33, "Flavio W. Brasil"<EMAIL_ADDRESS>wrote:

suggestion
[image: screen shot 2016-05-14 at 2 27 44 pm]
https://cloud.githubusercontent.com/assets/831175/15270791/dd36d4bc-19e0-11e6-9e68-d169500f49a4.png
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/getquill/quill/issues/233#issuecomment-219252790

@lvicentesanchez sure, let us know if he has something in the works. I've prepared this one using an online tool, and I don't trust too much my design skills :)


Do not include comments while templating values

Is your feature request related to a problem? Please describe.
When I want to have some comments in my values (and containing things like requiredEnv) helmwave tries to also template the comments
Describe the solution you'd like
Ignoring comments in values (remove them before running the templating logic)
Describe alternatives you've considered
Using hooks
Additional context
Add any other context or screenshots about the feature request here.

Hi mate!
For commenting go template you have to use {{/* getenv "HELLO_WORLD" */}}
For commenting yaml you have to use # HelloWorld.
Thus, it is expected behavior. It's the feature. It's useful when you want to generate documentations inside:
{{ range $env := $envs }}
###### {{ $env }}
{{ range $app := $apps }}
# {{ $app }}
- env: {{ $env }}
  app: {{ $app }}
{{ end }}

it will transform into
###### PROD
# api
- env: prod
  app: api

# web
- env: prod
  app: web

###### DEV

# api
- env: dev
  app: api

# web
- env: dev
  app: web

@zhilyaev
Nice
I have forgotten that I can do this using go template


Makes the IoC manager compliant with container interop

In preparation for delagate().
Also clears up a composer dependency issue.

Coverage decreased (-0.2%) to 99.766% when pulling 117834a3f081e56ba18a3e8071cda722c57cebba on testing-container-ioc into 699a1969693c6df758460bc22309f68777ecc972 on develop.


UI sortable & contenteditable div does not work

when content editable div cannot edit with in  sortable elements
following example cannot edit item name properly
http://codepen.io/anon/pen/kCfsL

Related to this issue: it is not possible to enter a contenteditable element within a ui-sortable container with a left click. See http://codepen.io/rh/pen/oXGORP.
It is possible to enter it with tab or a right click.


Study progress should be rounded off visually

I just noticed that the study progress is not rounded, which can lead to ugly results.

Yikes. And I see that the participation trend is also flat for you, which means this also isn't working anymore :(

I just pushed a fix to develop. I round the value to a whole number, because that will fit best in the progress circle, and I think the granularity of the rounded percentage scale is sufficient here. Can you check?

I see this issue also occurs elsewhere (participants and users page), so still hasn't been fixed completely

Should be ready for test now.

@smathot Can you close this issue if you find it is fixed?

I think it works now. I was a bit confused at first because the study progress seemed to be stuck at 0 but then I realized that it refers to the number of participants that have completed the study, and not to the number of trials that have been completed.
(The attentional-capture experiment that is part of the example data actually shows 0% despite having a few dummy participants that are supposed to have completed the study. But I assume this is only a result of populating the database and not a bug that needs to be fixed.)

Correct. The seed data are not used for the completion stats


Feature/add get jobs endpoint

What has changed

An endpoint has been added, which allows a GET request to be made, to provide details of all the search reindex jobs currently held in the job store. This results in the relevant Job resources being returned, in a list, or otherwise a null value is returned (if no Job resources exist).
NB. The swagger spec. is slightly different to the current functionality because the trello ticket specifies the following: ignore request query parameters, offset, limit, sort and state for now.
Example of the GET request:
http://localhost:25700/jobs
Example of a list of two Job resources being returned:
{
"jobs": [
{
"id": "fc0c8f28-0f2a-4ded-b27c-18f2d8748b76",
"last_updated": "2021-04-27T14:27:13.599666Z",
"links": {
"tasks": "http://localhost:12150/jobs/fc0c8f28-0f2a-4ded-b27c-18f2d8748b76/tasks",
"self": "http://localhost:12150/jobs/fc0c8f28-0f2a-4ded-b27c-18f2d8748b76"
},
"number_of_tasks": 0,
"reindex_completed": "0001-01-01T00:00:00Z",
"reindex_failed": "0001-01-01T00:00:00Z",
"reindex_started": "0001-01-01T00:00:00Z",
"search_index_name": "Default Search Index Name",
"state": "created",
"total_search_documents": 0,
"total_inserted_search_documents": 0
},
{
"id": "f207826a-e8ad-4202-a5f0-9f10e2a32e2c",
"last_updated": "2021-04-27T14:27:15.50031Z",
"links": {
"tasks": "http://localhost:12150/jobs/f207826a-e8ad-4202-a5f0-9f10e2a32e2c/tasks",
"self": "http://localhost:12150/jobs/f207826a-e8ad-4202-a5f0-9f10e2a32e2c"
},
"number_of_tasks": 0,
"reindex_completed": "0001-01-01T00:00:00Z",
"reindex_failed": "0001-01-01T00:00:00Z",
"reindex_started": "0001-01-01T00:00:00Z",
"search_index_name": "Default Search Index Name",
"state": "created",
"total_search_documents": 0,
"total_inserted_search_documents": 0
}
]
}
Example of a null value being returned if no Job resources exist:
{
"jobs": null
}
Logging has been added to show the sorted list of Job resources if returned successfully.
Unit tests have been added for the api, the handler, and the storer.
A component test has also been added, which tests that the expected number and details of Job resources will be returned in chronological order of last_updated.
How to review

The endpoint can be tested locally by first using this POST URL a number of times to create that number of Job resources in the Job Store: http://localhost:25700/jobs
The endpoint, which has a similar URL, can then be used as a GET URL to retrieve those same jobs in a single sorted list: http://localhost:25700/jobs
The unit tests can be run using this command: make test
The component tests can be run using this command: go test -component
Who can review

Anyone but me

Hi @ChrysmOre  please would you mind reviewing again? I've removed blank lines as much as possible. I'm not sure what change I should make to the logging - please see my comment. By the way, I don't know your name? It would be good to be able to talk over Slack..


Remove deprecated IPU config arguments

What does this PR do?

Fixes # (issue)
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

I think we'll need to go on HF hub and delete these options from all the IPU configs when we land this


agogosml should use a single container per model

The three containers add to overall runtime complexity and increase build times while making it harder to maintain the semantics of the queue/stream to which the containers are connected. Much can go wrong in the two extra http hops. Given how we create agogosml apps/containers from templates, we could easily create a single-container template.
agogosml is currently a more brittle (at runtime), less capable model hosting environment than Kafka Streams ( https://kafka.apache.org/21/documentation/streams/core-concepts ). We should simplify agogosml with the idea of moving over to Kafka Streams when the Kafka head for Azure Event Hub supports it.

I added a user story in the backlog to create a single container template. There is some minor work for the CLI but should be possible in this or the next sprint.

I'll try to help, especially if it's next sprint.


Workaround zune-jpeg issue

See: https://gitlab.gnome.org/GNOME/librsvg/-/merge_requests/967#note_2088834

Thanks Kleis, looking at the dependency chains involved here I agree this is a better workaround.


Add some unsafe magic for minimal optimizations, add .idea to .gitignore and fix some typos

Thanks for the amazing contribution to open source url parsing!
I am using this lib right now and thought that I should look into it a bit,
I ended up doing minor changes.
I understand if the unsafe code gets rejected, but I even left some safety comments.

Also can you fix clippy errors?

I added tests and comments that illustrate which number maps to which enum variant.
Regarding the clippy errors, I don't get any.
Now let's talk about performance:
If I'm honest there will be a performance difference but it will be negligible.
But the code I wrote is 100% safe, you can trust me on that one since I added a#[repr(u32)] on the enum which allows for safe transmution between value as u32 and the enum as long as value is not bigger than the number of variants of the enum -1, but we check for that.
If you still think its risky, just deny the commit, it's alright for me.

Oh ok I should have done the assembly check myself. Thanks for pointing out that it produces the same exact instructions.


Style buttons

This task took me 40 minutes of just working and trying different styles in CSS. I also had to make sure to style the default 'Choose File' buttons separately from the custom buttons once again.


Feat: Enable key event for submission in login/signup, contact us and subscribe newsletter

Describe the feature
Currently,  the "Enter" key on our keyboard does not work when you enter your email ID and want to continue, clicking the "Enter" button on our keyboard doesn't work, for login/signup subscribe button and contact us too. I wish to add this key event
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[ ] I'm a VSoC'24 contributor
[X] I want to work on this issue

@mdazfar2 please assign me this issue

@Asymtode712 go ahead


NotifierBase.state setter should be @protected

AsyncNotifierBase and StateNotifier have protected state setters.
But NotifierBase has it public.
  // While AsyncNotifierBase has:
  @protected
  set state(AsyncValue<State> newState) {
    // ...
  }

  // NotifierBase has:
  set state(State value) {
     // ...
  }

Expected all Notifiers to protect state setter.

This has been fixed recently in 333cd8c9be36e105e9e5673ef0a97cbcfd59c955, and has yet to be published


Enabled RSpec/AnyInstance Rubocop on the common ecosystem

https://www.rubydoc.info/gems/rubocop-rspec/1.7.0/RuboCop/Cop/RSpec/AnyInstance
What are you trying to accomplish?
This pull request will enable the AnyInstance RSpec Rubocop rule specifically on files in the common folder.  The scope of work had a large number of files, so breaking it up into chunks lets the work get done in smaller PRs for easier review and makes keeping the code base in sync much easier.
Anything you want to highlight for special attention from reviewers?
This is only part of the fix for the 'RSpec AnyInstanceOf ' rubocop issue.
How will you know you've accomplished your goal?
This has been tested to ensure that all of the rspec tests on the common folder still run.
Checklist

[x] I have run the complete test suite to ensure all tests and linters pass.
[x] I have thoroughly tested my code changes to ensure they work as expected, including adding additional tests for new functionality.
[x] I have written clear and descriptive commit messages.
[x] I have provided a detailed description of the changes in the pull request, including the problem it addresses, how it fixes the problem, and any relevant details about the implementation.
[x] I have ensured that the code is well-documented and easy to understand.

@GarryHurleyJr this is a fairly complex issue to resolve that requires refactoring the code being tested in order to address appropriately. It might be better left for someone with extensive Ruby experience in order to address the underlying problem that the rule is trying to address, rather than just attempting to make the error go away.
I've tried to leave some hints in collaboration with Copilot, on how this should be resolved inline, but feel free to just move on to the next issue if it's not entirely clear.

Closing, as Garry has moved on from the :dependabot: team. Whoever tackles this Rspec rule next will almost certainly start from a fresh PR.


Consistent Error Reporting discussion

λ> data A = A { a :: Bool, b :: Int } deriving (Eq, Show, Ord, Generic, Binary, NFData, Atomable)
λ> toAtomType (undefined :: Proxy A)
ConstructedAtomType "A" (fromList [])

λ> toAtom (A True 1)
ConstructedAtom "A" (ConstructedAtomType "A" (fromList [])) [BoolAtom True,IntAtom 1]
λ> fromAtom $ toAtom (A True 1)

<interactive>:33:1: warning: [-Wtype-defaults]
    • Defaulting the following constraints to type ‘Integer’
        (Show a0) arising from a use of ‘print’ at <interactive>:33:1-28
        (Atomable a0) arising from a use of ‘it’ at <interactive>:33:1-28
    • In a stmt of an interactive GHCi command: print it
*** Exception: improper fromAtomConstructedAtom "A" (ConstructedAtomType "A" (fromList [])) [BoolAtom True,IntAtom 1]
CallStack (from HasCallStack):
  error, called at /root/project-m36/src/lib/ProjectM36/Atomable.hs:64:16 in main:ProjectM36.Atomable
λ>

λ> toAddTypeExpr (undefined :: Proxy A)
AddTypeConstructor (ADTypeConstructorDef "A" []) [DataConstructorDef "A" [DataConstructorDefTypeConstructorArg (PrimitiveTypeConstructor "Bool" BoolAtomType),DataConstructorDefTypeConstructorArg (PrimitiveTypeConstructor "Int" IntAtomType)]]

Oops. Sorry for the noise.
fromList [] means no type variable in the type constructor. And that's nothing wrong.
But I still got an error in my project with project-m36-typed.
2019-05-06 11:30:32.029902: [info] attempting rollback after encountering errorDbQRelError (TypeConstructorAtomTypeMismatch "User" (C
onstructedAtomType "User" (fromList [])))
I'll report it if it's related to project-m36. Closed.

Sure. Also let me know if what ways the error-reporting could be improved. I hit errors myself which are not always clear- I've been thinking of adding more context to the error reporting, but I don't have a plan for how to make it consistent.

Sure.
It turns out that I just forgot to toAddTypeExpr  (undefined :: User). haha, free jokes.
I just figure that out when I trace where TypeConstructorAtomTypeMismatch is located.
I was trying to auto-generate those new datatypes form a user-defined Schema in project-m36-typed.
I was thinking which relation type can express DbRecord User well. "Should I store User as ConstructedAtomType or a plain relation with extended attributes as additional record information?"
So, when TypeConstructorAtomTypeMismatch, I wish to see something like "
ConstructedAtomType "User" (fromList []) is used in attribute (dbRecordRecord :: User) in relvar Users, but not listed in database datatypes: Int, Day, ...Maybe a..... Maybe you need to create it first before use it."
If let me make a big wish, I hope there are:

a consistent language/expression that can be used both in haskell and tutd.
(so that it can be divide and conquer when checking every part of an expression)
Every action/operator/expression has a clear road map/ implementation steps.
If an error occurs, it will shows what the context is now, the steps needed, the steps finished, and the step that went wrong, and (maybe) how-to-fix recommendation

If a simple expression can have this overall check, then it will boost confidence to debug a more complicate expression like a big schema or nested expression.
--
exception call traces in control-monad-exception looks nice, though I haven't used it. Worth taking a look.

hi @agentm
I saw this today. They have implemented "Relation Types" in Haskell for a relational algebra C++ library.
2 03 Types for a Relational Algebra Library - YouTube
I guess it's worth mentioning here.

Thanks. I think you've summarized my thoughts on reasonable error reporting as well.


Kubernetes deploy does not have the '--dev' option

https://docs.dapr.io/operations/hosting/kubernetes/kubernetes-deploy/

This does not work:
dapr init -k --dev

The issue is gone.


Cannot connect to Keycloak: Unable to connect to Keycloak using the current configuration

Hello and thank you for desiging the keycloak integration for streamlit. I have however problems getting it running.
I am getting the same error message as described in #6: Unable to connect to Keycloak using the current configuration
Small differences in my setup
def main():
   ...

keycloak = login(
        url="https://<someurl>.com",
        realm="newrealm",
        client_id="newclientid"
        )

if keycloak.authenticated:
        main()

I do not run keycloak locally but instead it runs on a cloud instance, therefore https (and no explicit port mentioning). My streamlit application also runs on a cloud instance, therefore the Valid Redirect URI is set to http://<IP>:8501. Setting the Web Origin to * leads to the same result as described above.
I also confirmed the correct name of the realm in the json export under "Installation" in the Clients pane under the Installation tab, and the correct name for the client_id in the Settings tab.
Is there any possibility to get more information about why the connection fails (e.g. unable to find keycloak server, unknown realm, unknown client id, etc.)?
Thank you very much for your help!

Whoops, accidentally closed this.
Hi Johannes, thanks for giving this package a shot.
I have had a look at what you described. When you get the 'unable to connect' message, this means that the initialization function from the keycloak javascript library fails. This generally happens when Keycloak is misconfigured somewhere.
I believe the Redirect URI should be the external url, so something like https://<someurl>.com/*. The redirecting happens in the browser, so the url you see there should be valid. Let me know if this helps.
I think your suggestion for more error logging is a great idea, so I improved that in a new branch. I haven't figured out how to catch problems with the redirect uris though, so this wouldn't help in this case.

Thank you very much for your support and the release of the package v.1.0.1.
I looked at the improved logging and can report more insight now.
This happens in the app (when running streamlit run Home.py).

The terminal shows the following output:
2023-01-10 08:28:31.695 ComponentRequestHandler: GET streamlit_keycloak.keycloak/b
uild/bundle.js read error
Traceback (most recent call last):
  File "/home/ubuntu/keycloak-project/venv/lib/python3.10/site-packages/streamli
t/web/server/component_request_handler.py", line 55, in get
    with open(abspath, "rb") as file:
FileNotFoundError: [Errno 2] No such file or directory: '/home/ubuntu/keycloak-project
/venv/lib/python3.10/site-packages/streamlit_keycloak/frontend/public/build/
bundle.js'

I checked the specific folder and it does not include the file bundle.js - instead this is the output of the folder:
$ tree ./venv/lib/python3.10/site-packag
es/streamlit_keycloak/
./venv/lib/python3.10/site-packages/streamlit_keycloak/
├── __init__.py
├── __pycache__
│   └── __init__.cpython-310.pyc
└── frontend
    └── public
        ├── bootstrap.min.css
        ├── check-sso.html
        ├── index.html
        └── login.html

Do you have any idea why the file bundle.js is missing?
I also checked in your repository under the respective tag: https://github.com/bleumink/streamlit-keycloak/tree/v1.0.1/streamlit_keycloak/frontend/public
and here the file bundle.js is also not present. Does this provide you any clue?
Thank you so much for your help with that.

I installed the repo with pip, or more precisely with the following command:
pip install git+https://github.com/bleumink/streamlit-keycloak

which resulted in version 1.0.1 (and then I received the error I described above).
With respect to to the redirect URI: I am building a streamlit app on AWS, therefore I set the redirect URI to http://<instance IP>:8501/*.
I first thought I made an error with the security groups, however now I am getting more error messages than earlier:
2023-01-10 14:11:34.114 ComponentRequestHandler: GET streamlit_keycloak.keycloak/b
uild/bundle.css read error
Traceback (most recent call last):
  File "/home/ubuntu/keycloak-project/venv/lib/python3.10/site-packages/streamli
t/web/server/component_request_handler.py", line 55, in get
    with open(abspath, "rb") as file:
FileNotFoundError: [Errno 2] No such file or directory: '/home/ubuntu/keycloak-project/
venv/lib/python3.10/site-packages/streamlit_keycloak/frontend/public/build/
bundle.css'
2023-01-10 14:11:34.148 ComponentRequestHandler: GET streamlit_keycloak.keycloak/b
uild/bundle.js read error
Traceback (most recent call last):
  File "/home/ubuntu/keycloak-project/venv/lib/python3.10/site-packages/streamli
t/web/server/component_request_handler.py", line 55, in get
    with open(abspath, "rb") as file:
FileNotFoundError: [Errno 2] No such file or directory: '/home/ubuntu/keycloak-project/
venv/lib/python3.10/site-packages/streamlit_keycloak/frontend/public/build/
bundle.js'
2023-01-10 14:11:34.181 ComponentRequestHandler: GET streamlit_keycloak.keycloak/b
ootstrap.min.css.map read error
Traceback (most recent call last):
  File "/home/ubuntu/keycloak-project/venv/lib/python3.10/site-packages/streamli
t/web/server/component_request_handler.py", line 55, in get
    with open(abspath, "rb") as file:
FileNotFoundError: [Errno 2] No such file or directory: '/home/ubuntu/keycloak-project/
venv/lib/python3.10/site-packages/streamlit_keycloak/frontend/public/bootst
rap.min.css.map'

Okay, my apologies, I reinstalled it (not directly from git) and now my output has changed a bit:
This comes from the webinterface
Unable to connect to Keycloak using the current configuration.
Timeout when waiting for 3rd party check iframe message.

whereas the command line reports that bootstrap.min.css.map could not be found.
Unable to connect to Keycloak using the current configuration.
Timeout when waiting for 3rd party check iframe message.

It appears that streamlit can't connect to your Keycloak instance and then times out.
Make sure that the url your are providing to the login function is where Keycloak is running and the proper ports are exposed and forwarded. If you paste that exact url in your browser do you then end up at some Keycloak administrative page?
When this is working, set the redirect uri to the external url where you will be hosting your app.

Thank you for all your help, could unfortunately not figure out where the problem is. Keycloak is available via the browser but my app still cannot establish a connection to Keycloak. Need to postpone this issue to a later time. Thanks again.

No worries, if you are still having issues with this in the future, I'll be happy to help again. Closing this for now.
One final thought: did you set the client access type to public?


[feature suggestion] add permission limit for reopen issue or pr

Gitea version (or commit ref):
Git version:
Operating system:
Database (use [x]):

[ ] PostgreSQL
[ ] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[ ] Not relevant

Log gist:

Description
I think if an issue or pr is closed by admin, we should limit author who is not admin to reopen it. which is same with github. Thanks
...
Screenshots

I'd rather use the "locked" attribute. In a small team, the admin might just close an issue for many reasons that don't count for locking the issue.


Add Thermal Support

Copied from the existing file for Atums Bonestorm. Tested and works.
Also changes the icon when its angry (because their texture changes when angry). Just an interesting thing I noticed.

(The blaze for scale)
The icon sizes are approximately the same size as a blaze, however the Blitz and Basalz have odd head shapes so they are just... strange.

If needed I can 're-compile' the resource pack as well.

Hello, thank you for doing this! And apologies for the slow response.
I will have a look at the icons later and merge if there's no issues, and hopefully I can upload the new pack to Curseforge tomorrow!

Have checked it out and all looks good :)


Auto-discover systems through infrastructure (i.e. terraform, k8s files, etc)

Originated from #209
One way we could try to automatically discover systems is to ingest "infra as code" files

@iamkelllly this is ok to close considering the infra scanning project right?

this is now its own project, -plus


wysiwyg editor

Any plan on including wysiwyg editor?

+1

This can be a huge component on its own, I don't think we should put it into shadcn.

Hi there, I found this project. I think it might be helpful for people who are searching for a rich text editor for shadcn https://platejs.org/

Hi there, I found this project. I think it might be helpful for people who are searching for a rich text editor for shadcn https://platejs.org/

Did you ever managed to serialize the output to HTML including the Tailwind css classes?

Did you ever managed to serialize the output to HTML including the Tailwind css classes?

To be honest with you I haven't used it I found that when I was browsing it. But I can help you if you can share the output and the related code only if it is ok with you.

Any updates?

anyone reading this, you can also use TipTap to build a rich text from scratch, they have plugins ecosystem as well. But might be "a little" tricky working with tailwind css.

This issue has been automatically closed because it received no activity for a while. If you think it was closed by accident, please leave a comment. Thank you.

I've added ShadCN support for the BlockNote rich text editor after many users requested it! See https://www.blocknotejs.org/examples/basic/shadcn
@shadcn if you're interested I can create a PR to add it to the CLI? This way people could install it directly and it could automatically use the components from the client project (now, people need to add it via shadCNComponents)


zeroad: 0.0.25 -> 0.0.25b

Motivation for this change
Version bump.
Things done
Started a game, everything ran fine.

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 136105 at 740b698e run on aarch64-linux 1

1 package failed to build:

zeroadPackages.zeroad-unwrapped

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement. Does something look off? Please file an issue or reach out on IRC.

Can we build this without nvidia-texture-tools on aarch64? It is marked as broken and the upstream has already archived the project.
https://github.com/castano/nvidia-texture-tools

I can confirm that this builds for me and that at least the title screen works for me. Will play a game in a bit to see if everything is ok, but I don't expect much issues since 0.0.25 seemed to work fine (enough, had 2 multiplayer crashes, but probably not related to packaging).
As for nvidia-texture-tools, that should probably be reported upstream so they can get rid of it or replace it with something else.

Tested 740b698 on x86_64 (git fetch/checkout nix-env -iA zeroad -f path/to/nixpkgs/repo) builds without hickups and runs nicely spectated a game in the lobby and played a short match against AI.


Add image loading events to ol.source.ImageStatic

This PR adds image loading events to ol.source.ImageStatic, follow up on #3305.
Ping @bartvde

nice work @tsauerwein LGTM please merge if Travis passes

Also great to see additions of tests for an untested class!

Thanks, Bart!


Changes for Apr 2023 re-certification of EQuIS connector

Remove the "Beta" attribute and remove the row number limitation.

@Jak-MS Just to clarify, are you wanting me to review the PR and add the sign-off tag? Or are you asking @DougKlopfenstein to do that?

@mathew-weaver - apologies for the confusion. typo... all PRs in the powerquery-docs repo should be reviewed by @bezhan-msft or @DougKlopfenstein .  I've edited my earlier comment.

Hi @mathew-weaver
To remove all instances of the Beta tag (and its equivalents), you'll need to:

Remove the (Beta) tag from the table of contents (toc.yml).
Remove the (Beta) tag from the list of all connectors (connectors/index.md).
Change the Release state in the Summary table from "Preview" to "Generally Available" (connectors/equis.md).

@DougKlopfenstein I pushed the changes requested in your last comment (here). I updated ms.date within the equis.md file, but not within toc.md or index.md. Please let me know if I should update ms.date in those files also.

All of the updates shown in this pull request have been done in the private pull request mentioned above. This private pull request was created to overcome the conflicts in this public pull request. Since all of the changes in this pull request were made in the private pull request, this PR is now redundant and is closed.


When writing files in frb_codegen, create directories if they don't exist

This patch adds fs::create_dir_all calls to frb_codegen/src/main.rs to ensure directories exist before trying to write files in them.
Justification
Currently, running frb_codegen with --rust-output folder_does_not_exist/code.rs causes the program to exit with a filesystem error (tested on Windows 10).
I'm creating a bindgen script, in which I run frb_codegen and tell it to write my generated dart code to to a folder called generated. I'd like to gitignore my auto-generated code. However, my generated folder only contains auto-generated files, which means the folder itself isn't created when the repo is checked out for the first time. As a result, my bindgen script encounters the error above. I can create the folder using my shell script, but I think it's reasonable for frb_codegen to create the directories if they don't exist since it already creates nonexistent files.

Sure. I will run CI and merge it.
btw you can use a .gitkeep for your own use case as well

CI fails. could you plz check it

CI error caused by other things, so I will merge it and fix.

@all-contributors please add @SecondFlight for code


Cant cross-compile register binary due to GCO_ENABLED

Looks like since we introduced CGO_ENABLED=1 for the register binary, we are not able to cross-compile for arm platforms on our release pipeline.
It usually fails via: gcc: error: unrecognized command line option '-marm'; did you mean '-mabm'?
We can try to build it by using the gcc-arm-linux-gnueabihf package which provides a gcc cross-compiler and using overrides on arm binaries

I disabled GCO_ENABLED=1 in arm builds for the moment as we need to have a proper release pipeline

Reopening as currently its only a workaround.

# itxaka @ zeus in ~/projects/elemental-operator on git:main x [16:08:29] C:2
$ CC=aarch64-suse-linux-gcc CGO_ENABLED=1 GOARCH=arm64 go build cmd/register/main.go
# runtime/cgo
_cgo_export.c:3:10: fatal error: stdlib.h: No such file or directory
    3 | #include <stdlib.h>
      |          ^~~~~~~~~~
compilation terminated.

I think its the same issue, we need to clone the full https://github.com/google/go-tpm-tools to have all the C libs available. Otherwise if you try to compile it and use the go dep manager, it only downloads go files so we cant fully compile it.
$ ls vendor/github.com/google/go-tpm-tools/simulator/*
vendor/github.com/google/go-tpm-tools/simulator/README.md
vendor/github.com/google/go-tpm-tools/simulator/simulator.go

vendor/github.com/google/go-tpm-tools/simulator/internal:
doc.go  include.c  internal_cgo.go  internal_cross.go

was able to properly compile it without the go-tpm-tools under an arm64 docker container. It may be needed to compile it like that before running goreleaser if we want our arm github releases to have the full features.
Otherwise we just keep the arm64 without the tpm emulation.

LOL - that's exactly what I do when building the elemental-operator rpm

We don't cross-compile.


Extension causes high cpu load

Issue Type: Performance
Extension Name: stats-bar
Extension Version: 0.5.1
OS Version: Windows_NT x64 10.0.22000
VS Code version: 1.70.0

:warning: Make sure to attach this file from your home-directory:
:heavy_check_mark:file:///c%3A/Users/*******/AppData/Local/Temp/njzy.stats-bar-unresponsive.cpuprofile.txt
Find more details here: https://github.com/microsoft/vscode/wiki/Explain-extension-causes-high-cpu-loa
njzy.stats-bar-unresponsive.cpuprofile.txt

Thank you for uploading the cpufile, I re-read the systeminformation performance related issues and found that this issue should be related to this https://github.com/sebhildebrandt/systeminformation/issues/616#issuecomment-974831564, Based on this I have released a new version - v0.5.2, you can try it out

the fix apparently fixed the problem, I'll close the issue since it's fixed, thanks :)


Phase out the network manager

This is a proposal to phase out the network.Manager in favor of the ORTC Constructors suggested in #273 and #312. The WebRTC PeerConnection API would use the ORTC constructors to set up the correct network stack.
Examples:

JS adapter

TODO:

[x] ICE Gatherer
[x] ICE Conn
[x] DTLS Conn
[ ] SCTP Conn
[ ] Data channels
[ ] RTP Receiver (Blocked by #312)
[ ] RTP Sender (Blocked by #312)

Since #337 the media side, suggested in #312, can now also be added on top.


Link footer socials to actual pages

Where are the links to socials? I can work on this

Hello, there's already an assignee for this issue, shall we leave it out for a while ?

Hey, @Akalanka47000 is this issue still open? If yes, can you please assign it to me?

Hey, @Akalanka47000 is this issue still open? If yes, can you please assign it to me?

@probablyshabina any update on the linked PR? If not we can assign this to @Utkarshrajmishra

I’ll make the requested changes and close the issue asap.


Plugin Support Request for RADZEN Blazor Studio

RADZENBlazor Studio is a software development environment that empowers developers to design, build, and deploy Blazor applications without the traditional hurdles. Write less code and get more done. It is a complete environment offered by Radzen located in Bulgaria.  It is becoming extremely popular.
Below is a link to their home page:
https://www.radzen.com/blazor-studio/

Awesome!!!! When Might it be available?


Add ProductCode to Microsoft.VC++2008Redist-x86

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Resolves #18943
Microsoft Reviewers: Open in CodeFlow

/azp run


Problem with hierarchy of +layout.svelte

Describe the bug
At the moment of creating the project, and inside src in the root "/" I create a +layout.svelte and then I create a folder called "/panel" and inside there, I create another +layout.svelte and a +page@panel .svelte to create an advanced layout, then it doesn't work for me. I tried the same thing creating groups() and it didn't work for me either. I'm using the latest version of Sveltekit, and I'm just installing the project and using the advanced layouts at once. The main problem is that instead of showing me only the layout of "/panel" it shows me the two layouts
src/routes/
│
├ panel/
│ ├<EMAIL_ADDRESS>│ └ +layout.svelte
└ +layout.svelte
If I use for example the following format if it works
src/routes/
│
├ panel/
│ ├<EMAIL_ADDRESS>│ └ +layout.svelte
└ +layout.svelte
And it only shows me the main layout
Reproduction
https://github.com/maikerleon/sveltekit/
Logs
No response
System Info
"scripts": {
		"dev": "vite dev",
		"build": "vite build",
		"preview": "vite preview",
		"lint": "prettier --plugin-search-dir . --check .",
		"format": "prettier --plugin-search-dir . --write ."
	},
	"devDependencies": {
		"@sveltejs/adapter-auto": "^2.0.0",
		"@sveltejs/kit": "^1.5.0",
		"autoprefixer": "^10.4.14",
		"daisyui": "^3.1.5",
		"postcss": "^8.4.24",
		"prettier": "^2.8.0",
		"prettier-plugin-svelte": "^2.8.1",
		"svelte": "^3.54.0",
		"tailwindcss": "^3.3.2",
		"vite": "^4.3.0"
	},
	"type": "module",
	"dependencies": {
		"svelte-preprocess": "^5.0.4"
	}

Severity
annoyance
Additional Information
No response

You can only go upwards the layout chain, but you cannot skip or reset your layout. So you can't say "I only want the panel layout and skip the root layout". Furthermore, the root layout cannot be skipped because a stable/predefined layout is needed in case of errors etc.
What you can do is to use groups to achieve what you want:
src/routes/
├ (main)
│ ├ +layout.svelte
│ └ (everything that should extend the main layout goes here)
├ panel/
│ ├ +layout.svelte // does not extend the layout in (main)
│ └ +page.svelte