ipam/aws/eni: IP allocation silently failing when using "unsupported" instance types

Bug report
As I attempted to get CIlium to run onto arm64 EC2 instances of the t4g family with IPAM/ENI mode, I encountered an issue where the agent is waiting for the operator to allocate new addresses indefinitely.
agent logs on the t4g.large instance:
{"level":"info","msg":"Successfully synchronized CiliumNode custom resource","name":"ip-10-6-29-165.eu-west-1.compute.internal","subsys":"ipam"}
{"available":0,"helpMessage":"Check if cilium-operator pod is running and does not have any warnings or error messages.","level":"info","msg":"Waiting for IPs to become available in CRD-backed allocation pool","name":"ip-10-6-29-165.eu-west-1.compute.internal","required":10,"subsys":"ipam"}

operator logs:
{"level":"info","msg":"Discovered new CiliumNode custom resource","name":"ip-10-6-29-165.eu-west-1.compute.internal","subsys":"ipam"}

I tried to scale out existing autoscaling groups of a knowingly working instance type: m5.large (amd64), and surprisingly got into the same issue.
After removing the t4g.large from the cluster and it's associated CiliumNode resource, the operator managed to allocate ip addresses over the m5.large successfully.
I then looked at the following file: https://github.com/cilium/cilium/blob/8531ff82215943beb12650b784d2255bfae313db/pkg/aws/eni/limits/limits.go#L40
I tried to add another arm64 instance type which was referenced into it: m6g.large. And this time it worked perfectly.
What is surprising is:

The lack of errors and/or warnings showing up on the operator's logs.
The fact that it seems to completely break the IP allocation for whole cluster

I haven't gone any further for now but I will follow up on this with more details next week! We briefly talked about it on Slack with @joestringer https://cilium.slack.com/archives/C53TG4J4R/p1611607263013800
General Information

Cilium version: v1.9.3
Kernel version: 5.4.0-1037-aws
Orchestration system version in use: EKS v1.18.9

How to reproduce the issue

Register an EC2 instance of the t4g family
Validate that no errors is showing up from the cilium-controller yet no IP allocation is occurring anymore

Thanks for filing the issue.

The lack of errors and/or warnings showing up on the operator's logs.

Yes, I think properly logging this is a good solution.

Thanks for filing the issue.

The lack of errors and/or warnings showing up on the operator's logs.

Yes, I think properly logging this is a good solution.

with --update-ec2-adapter-limit-via-api=true, it works correctly 👍

with --update-ec2-adapter-limit-via-api=true, it works correctly 👍

I added this as a good-first-issue. One potential solution is to log a msg when an "unsupported" instance type is detected and say something along the lines of "consider setting --update-ec2-adapter-limit-via-api=true".

I added this as a good-first-issue. One potential solution is to log a msg when an "unsupported" instance type is detected and say something along the lines of "consider setting --update-ec2-adapter-limit-via-api=true".


User unable to join liveshare session

Issue Type: Bug

Start a collaboration session from the command pallette
Paste the link to user who you wish to join your session
User attempts to join the session
"Cannot access a disposed object. Object name: RpcSession" message reported to user and they are unable to join

Extension version: 0.4.0
VS Code version: Code 1.52.1 (ea3859d4ba2f3e577a159bc91e3074c5d85c0523, 2020-12-16T16:34:46.910Z)
OS version: Windows_NT x64 10.0.19042

System Info

Item
Value

CPUs
AMD Ryzen 7 3800XT 8-Core Processor             (16 x 3893)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offopengl: enabled_onprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.91GB (5.46GB free)

Process Argv
--crash-reporter-id b53b86c0-c7d5-4767-ab41-b84abd8871f1

Screen Reader
no

VM
0%

A/B Experiments
vsliv368:30146709
vsreu685:30147344
openlogontheside:30221877
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30211402
wsl2prompt:30224612
vstry244:30250195
pythonvsdeb440:30248342
unusedpromptcf:30224611
folderexplorercf:30224615
openfilemenucf:30224648
pythonvsded773:30248341
pythonvspyt600cf:30251589

Issue Type: Bug

Start a collaboration session from the command pallette
Paste the link to user who you wish to join your session
User attempts to join the session
"Cannot access a disposed object. Object name: RpcSession" message reported to user and they are unable to join

Extension version: 0.4.0
VS Code version: Code 1.52.1 (ea3859d4ba2f3e577a159bc91e3074c5d85c0523, 2020-12-16T16:34:46.910Z)
OS version: Windows_NT x64 10.0.19042
System Info
A/B Experiments

Issue Type: Bug

Start a collaboration session from the command pallette
Paste the link to user who you wish to join your session
User attempts to join the session
"Cannot access a disposed object. Object name: RpcSession" message reported to user and they are unable to join

Extension version: 0.4.0
VS Code version: Code 1.52.1 (ea3859d4ba2f3e577a159bc91e3074c5d85c0523, 2020-12-16T16:34:46.910Z)
OS version: Windows_NT x64 10.0.19042
System Info
A/B Experiments

Closing this one out due to age. Please re-activate if it's still posing a problem.


Fix: Migration target has no matching tags

Description

The code prior to this commit was looking for the storage tags at the table storage_pool_details, which is empty. It should select from storage_pool_tags, which contains the tags from each tagged storage.

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[X] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Screenshots (if appropriate):
How Has This Been Tested?

Migrated a volume with a tag 'A' to a storage pool that also has the tag 'A'. Resulted on the following exception:
2019-05-10 17:03:16,343 ERROR [c.c.a.ApiAsyncJobDispatcher] (API-Job-Executor-9:ctx-1255172b job-16095) (logid:3f7e0f22) Unexpected exception while executing org.apache.cloudstack.api.command.admin.volume.MigrateVolumeCmdByAdmin
com.cloud.utils.exception.CloudRuntimeException: Migration target has no matching tags for volume 'ROOT-2086(262d639d-a0b0-4f8d-9e86-01fb210ace8f)'
        at com.cloud.storage.VolumeApiServiceImpl.migrateVolume(VolumeApiServiceImpl.java:2086)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)

After update with the proposed fix, the volume got migrated successfully.

@blueoragutan package

@blueorangutan package

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos6 ✔centos7 ✖debian. JID-2802

@blueorangutan package

@DaanHoogland a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos6 ✔centos7 ✔debian. JID-2805

@blueorangutan test

@rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

Trillian test result (tid-3598)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 33188 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr3329-t3598-kvm-centos7.zip
Intermittent failure detected: /marvin/tests/smoke/test_vpc_redundant.py
Smoke tests completed. 70 look OK, 0 have error(s)
Only failed tests results shown below:

Test
Result
Time (s)
Test File


"fhue put" returns an error

The output is fhue: HueError ""

https://github.com/madjar/fhue/releases/tag/v<IP_ADDRESS> should give you a better error message. Can you give me the error when you come back?

This had been fixed in 28406a8f76c3542427d0a120038543f6548d79dc


Instantiation of value failed for JSON property email due to missing (therefore NULL) value for creator parameter email which is a non-nullable type

In graphql, you can request for specific fields no matter they are optional or not. But that's not the case for codes generated by codegen library.
Error:
com.fasterxml.jackson.module.kotlin.MissingKotlinParameterException: Instantiation of [simple type, class graphql.schema.types.Tester] value failed for JSON property email due to missing (therefore NULL) value for creator parameter email which is a non-nullable type
 at [Source: UNKNOWN; line: -1, column: -1] (through reference chain: co.zip.api.mobile.graphql.schema.types.Tester["email"])
	at com.fasterxml.jackson.module.kotlin.KotlinValueInstantiator.createFromObjectWith(KotlinValueInstantiator.kt:116)
	at com.fasterxml.jackson.databind.deser.impl.PropertyBasedCreator.build(PropertyBasedCreator.java:202)
	at com.fasterxml.jackson.databind.deser.BeanDeserializer._deserializeUsingPropertyBased(BeanDeserializer.java:520)
	at com.fasterxml.jackson.databind.deser.BeanDeserializerBase.deserializeFromObjectUsingNonDefault(BeanDeserializerBase.java:1405)
	at com.fasterxml.jackson.databind.deser.BeanDeserializer.deserializeFromObject(BeanDeserializer.java:362)
	at com.fasterxml.jackson.databind.deser.BeanDeserializer.deserialize(BeanDeserializer.java:195)
	at com.fasterxml.jackson.databind.ObjectMapper._convert(ObjectMapper.java:4309)
	at com.fasterxml.jackson.databind.ObjectMapper.convertValue(ObjectMapper.java:4245)
	at com.jayway.jsonpath.spi.mapper.JacksonMappingProvider.map(JacksonMappingProvider.java:41)
	at com.jayway.jsonpath.internal.JsonContext.convert(JsonContext.java:118)
	at com.jayway.jsonpath.internal.JsonContext.read(JsonContext.java:83)
	at com.netflix.graphql.dgs.client.GraphQLResponse.extractValueAsObject(GraphQLResponse.kt:91)

Example code:
schema.graphql
type Tester {
	name: String!
	email: String!
}
type Query {
	tester: Tester
}

Testing code
//This works fine.
val testerResponse = GraphQLResponse("""{"data":{"tester":{"name":"jay", "email"<EMAIL_ADDRESS>emptyMap())

//===Below code will throw above exception while parsing Tester object if email data is not returned.===
//val testerResponse = GraphQLResponse("""{"data":{"tester":{"name":"jay"}}}""", emptyMap())
val testerObject = testerResponse.extractValueAsObject(DgsConstants.QUERY.Tester, Tester::class.java)

build.gradle.kts
plugins {
	jacoco
	id("org.springframework.boot") version "2.5.12"
	id("org.owasp.dependencycheck") version "6.0.2"
	id("io.spring.dependency-management") version "1.0.11.RELEASE"
	kotlin("jvm") version "1.5.10"
	kotlin("plugin.spring") version "1.5.10"
	id("com.netflix.dgs.codegen") version "5.1.17"
}
dependencies {
	implementation("com.fasterxml.jackson.module:jackson-module-kotlin")
	implementation("org.jetbrains.kotlin:kotlin-reflect")
	implementation("org.jetbrains.kotlin:kotlin-stdlib-jdk8")

	implementation(platform("com.netflix.graphql.dgs:graphql-dgs-platform-dependencies:4.4.0"))
	implementation("com.netflix.graphql.dgs:graphql-dgs-client")
}
tasks {
	generateJava {
		schemaPaths =
			mutableListOf("${projectDir}/src/main/resources/schema") // List of directories containing schema files
		generateClient = true // Enable generating the type safe query API
		language = "kotlin"
		typeMapping = mutableMapOf(
			"JSON" to "org.json.simple.JSONObject",
			"Float" to "java.math.BigDecimal",
			"DateTimeOffset" to "java.time.LocalDateTime",
			"Decimal" to "java.math.BigDecimal"
		)
	}
}

Can I please get some help on this?

We did not earlier support this. We do have an experimental codegen feature that can generate nullable kotlin classes generateKotlinNullableClasses . Could you add that to the task config and see if it addresses your use case?

It gets a new error
400 Bad Request: "{"errors":[{"message":"Field \"_defaults\" is not defined by type \"AccountsV1Options\".","extensions":{"code":"GRAPHQL_VALIDATION_FAILED"}}]}<EOL>"
schema.graphql
type Query {
    accounts(customerId: String, options: AccountsOptions): [Account]
}

input AccountsOptions {
	reloadPlatformCache: Boolean
}

serialized query:
query {
  accounts(customerId: "XXXXX", options: {reloadPlatformCache : true, _defaults : []})
  ...
}

gralde:
id("com.netflix.dgs.codegen") version "5.2.1"
Looks like the new version generates an extra '_defaults' field cause the error.

@mbossenbroek - could you please take a look when you are able to?

Ahh yeah, I ran into the same issue. Some updates to the InputValueSerializer broke it, but the fix is in - we just need to release it

We do have a release 5.2.5 - could you try updating?

Somehow, Im getting the same error again with 5.2.5
Instantiation of [simple type, class com.xxx.Tester] value failed for JSON property email due to missing (therefore NULL) value for creator parameter email which is a non-nullable type
the generated Tester class
public data class Tester(
  @JsonProperty("name")
  public val name: String,
  @JsonProperty("email")
  public val email: String,
) {
  public companion object
}

Well that's weird - that's the old style. I've seen gradle not clean correctly - could you manually nuke the build dir & rebuild? The generated class for that example should look like this. Could you see if it's generating both somehow? Maybe a different package?
@JsonTypeInfo(use = JsonTypeInfo.Id.NONE)
@JsonDeserialize(builder = Tester.Builder::class)
public class Tester(
  name: () -> String = nameDefault,
  email: () -> String = emailDefault,
) {
  private val _name: () -> String = name

  private val _email: () -> String = email

  public val name: String
    get() = _name.invoke()

  public val email: String
    get() = _email.invoke()

  public companion object {
    private val nameDefault: () -> String =
        { throw IllegalStateException("Field `name` was not requested") }

    private val emailDefault: () -> String =
        { throw IllegalStateException("Field `email` was not requested") }

  }

  @JsonPOJOBuilder
  @JsonIgnoreProperties("__typename")
  public class Builder {
    private var name: () -> String = nameDefault

    private var email: () -> String = emailDefault

    @JsonProperty("name")
    public fun withName(name: String): Builder = this.apply {
      this.name = { name }
    }

    @JsonProperty("email")
    public fun withEmail(email: String): Builder = this.apply {
      this.email = { email }
    }

    public fun build() = Tester(
      name = name,
      email = email,
    )
  }
}

I have tried every thing, delete build folder, restart ide, restart laptop, but still the old style.
Here is my config:
plugins {
id("org.springframework.boot") version "2.5.12"
id("org.owasp.dependencycheck") version "6.0.2"
id("io.spring.dependency-management") version "1.0.11.RELEASE"
kotlin("jvm") version "1.6.0"
kotlin("plugin.spring") version "1.6.0"
id("com.netflix.dgs.codegen") version "5.2.5"
}
dependencies {
/**
 *  graphQL
 */
implementation(platform("com.netflix.graphql.dgs:graphql-dgs-platform-dependencies:5.0.5"))
implementation("com.netflix.graphql.dgs:graphql-dgs-client")

}
tasks {
generateJava {
schemaPaths =
mutableListOf("${projectDir}/src/main/resources/schema")
packageName = "com.tester.graphql.schema"
generateClient = true
language = "kotlin"
typeMapping = mutableMapOf(
"JSON" to "org.json.simple.JSONObject",
"Float" to "java.math.BigDecimal",
"DateTimeOffset" to "java.time.LocalDateTime",
"Decimal" to "java.math.BigDecimal"
)
}
}

I don't see the generateKotlinNullableClasses flag in your config - diid that get dropped? That's what enables this new behavior

My apology, you are right.  Seems working fine now!

Thanks @mbossenbroek. I'm closing this issue since this is resolved.


Interference between global parameters and root node parameters

For a certain variant I create a configuration file that defines in a first step a parameter named teststring_common.
In a second step I import another configuration file in which I use this parameter in the following two ways:
${params}['global']['teststring_common'] : "value 1",
"teststring_common" : "value 2"

Within the robot file I print the value of this parameter:
Log    teststring_common : ${teststring_common}
Outcome: teststring_common has value "value 1".
I comment out the first line.
Outcome: teststring_common has value "value 2".
Impact: teststring_common is accessible by ${teststring_common} even if this parameter is defined in root node.

Hi Son,
I guess that the issue is from before the schema check has been introduced/adapted. I just executed this uses case again with the latest sources and I got a proper error message about a failed schema check.
This issue can be closed.

very good! I wondered already because sometime ago we defined that new variables at root level should be not allowed.


Provide the ability to reset the custom theme colors

I'm submitting a ...

[ ] bug report
[x] feature request
[ ] support request => Please do not submit support request here, see note at the top of this template.

Do you want to request a feature or report a bug?
feature

What is the current behavior?
There is no any way to reset theme colors to defaults when they were changed from the UI

If the current behavior is a bug, please provide the steps to reproduce, ideally also a screenshot or gif if it's a style issue

What is the expected behavior?
--

What is the motivation / use case for changing the behavior?
When the user had an attempt to change the theme, but he is not satisfied with the result he needs to reload the whole page. It should be nice to have the button that will reset the colors to the default theme. Maybe it can be placed in the same dropdown, where theme colors are changed

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)
--

We can do as follows:
[Default theme] - button
[primary] - color picker
[success] - color picker
...


[Release Radar Request] Japa

Open Source Project name
Japa
What is your project?
Japa is an API-first testing framework. It focuses only on testing Node.js (backend) applications, thus resulting in a fast, small, and simple tests runner.
Version
5.0
Date
21st Feb, 2022
Description of breaking changes
This version is rewritten from scratch and also comes with a dedicated documentation website. Here's the link to the upgrade guide https://japa.dev/releases/version-5
GitHub Repo
https://github.com/japa/core
Website
https://japa.dev
Link to changelog
https://japa.dev/releases/version-5
Social media
https://twitter.com/AmanVirk1/status/1495587345630113799
Anything else to add?
No response

Congrats on being featured in the February 2022 Release Radar 🥳

Read the blog here
Feel free to retweet Mish's tweet featuring you


Fix the functional requirements viewgraph

The "Functional requirements" image has "Application and processing services" box twice, the other should be "Data incubation and service creation".

This is the image to be edited: https://github.com/International-Data-Spaces-Association/IDSA-Rulebook/blob/main/documentation/media/Foundational_Concepts_in_data_spaces.png


Update yamux to version 0.4.5

See https://github.com/paritytech/yamux/blob/develop/CHANGELOG.md#045 for details.

Yes, repositories with a committed Cargo.lock need to manually update. I was about to open another PR for Polkadot. Do you have an alternative suggestion in mind?

Sadly not :( (I assume you have updated the reference in libp2p, so that the next libp2p update enforces this?)

https://github.com/paritytech/polkadot/pull/927

So would you prefer to wait for a new libp2p release instead of receiving PRs like this?

I think they are okay, at least for Polkadot. Substrate is questionable, but better safe than sorry :P


HTML Doc: Fix pattern case

Before:

After:

fixes #73

It's already on npm, version 0.10.0. Thanks!

Thanks! 🎉


feat: improve Archiver lambda by using DynamoDB stream

Summary | Résumé
There is no existing ticket for the following pull request.
After discussing with an AWS expert we have decided to use DynamoDB streams to trigger the Archiver lambda when an entry in the database has its own Retrieved field updated to 1. In our case we will wait for 25 items to be updated before executing the lambda.
The implementation in this PR has a flow when it comes to processing failures as with the nature of streams we will not be able to re process items that already came in. For now the lambda will retry 3 times before giving up.
Since the logic in the lambda is pretty simple there is not much place for failure so I would say we wait and see if it is worth implementing a backup plan with an SNS or SQS topic that will retain unprocessed items (something that the DynamoDB lambda trigger provides as an option).

Great work ! I don't see any immediate issues that pop out at me. Wondering if we can adapt the archival invocation script to have this work locally

I was hoping to get your Localstack stuff merged so that I could take a look at this next :) Will definitely now be able to try to make it work.

@Moro-Code As expected, it was too difficult to make the lambda work in Localstack using terraform so I switched back to the manual invoke script :)


Forwardport current 3.2.x efforts to develop

Coverage decreased (-0.2%) to 89.136% when pulling 4b85515bace3a79e1291777b20a0f8a1cf2cc6ce on FinalAngel:upstream-develop into 7654be7977e1a2e8cffb2c0af838990ad6ef99b6 on divio:develop.


About the average success rate image of paper.

Hi, guys, I got a question again.
I observed that from Fig.13 to Fig.16 in the paper, it seems like the beginning points of those curves are not starting at frame zero.
Do you miss something about that?

Hi,
Our agents gather 40 transitions from 32 environments in parallel. During the first collection (1200 transitions), it is very likely that none of the 32 environment rechead the end of their episode. Hence we cannot compute the average success rate yet (we must wait for at least one episode to finish its episode to get the return).


Error on conflicting cats versions

I'm facing this exception due to conflicts on cats versions:
This is observed with sbt-microsites 0.7.15
[error] java.lang.NoSuchMethodError: cats.instances.package$list$.catsStdInstancesForList()Lcats/TraverseFilter;
[error] 	at sbtorgpolicies.io.FileWriter.copyMultipleFiles$1(FileWriter.scala:85)
[error] 	at sbtorgpolicies.io.FileWriter.$anonfun$copyFilesRecursively$2(FileWriter.scala:89)
[error] 	at scala.util.Either.flatMap(Either.scala:338)
[error] 	at sbtorgpolicies.io.FileWriter.copyFilesRecursively(FileWriter.scala:88)
[error] 	at microsites.util.MicrositeHelper.createResources(MicrositeHelper.scala:68)
[error] 	at microsites.MicrositeAutoImportSettings.$anonfun$micrositeTasksSettings$1(MicrositeKeys.scala:242)

It seems this is due to org-policies-core which still uses cats 0.9.0
[warn] 	* org.typelevel:cats-core_2.12:1.0.1 is selected over {0.9.0, 1.0.0}
[warn] 	    +- org.typelevel:cats-effect_2.12:0.8                 (depends on 1.0.1)
[warn] 	    +- io.github.cquiroz:kuyfi_2.12:0.8.2                 (depends on 1.0.1)
[warn] 	    +- org.tpolecat:atto-core_2.12:0.6.1                  (depends on 1.0.0)
[warn] 	    +- org.typelevel:mouse_2.12:0.15                      (depends on 1.0.0)
[warn] 	    +- org.typelevel:cats-laws_2.12:0.9.0 ()              (depends on 0.9.0)
[warn] 	    +- org.typelevel:cats_2.12:0.9.0 ()                   (depends on 0.9.0)
[warn] 	    +- org.typelevel:cats-jvm_2.12:0.9.0 ()               (depends on 0.9.0)
[warn] 	    +- com.47deg:org-policies-core_2.12:0.8.17 ()         (depends on 0.9.0)

This happens for me as well after adding sbt-bloop:1.2.5 plugin

Sadly, this is a long-standing issue that, after some other attempts, we only could get rid off by stopping depending on sbt-org-policy, which is not an easy task.

Is there any workaround for this?

Yes, hopefully, we get a fix soon. I'll let you know.

FYI: @cquiroz @jaksah @Krever The new version of the plugin, 0.9.0 fixes the issue.

Yes, I confirmed this few hours ago myself as well. Thanks a lot!
wt., 26 lut 2019 o 16:15 Juan Pedro Moreno<EMAIL_ADDRESS>napisał(a):

FYI: @cquiroz https://github.com/cquiroz @jaksah
https://github.com/jaksah @Krever https://github.com/Krever The new
version of the plugin, 0.9.0 fixes the issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/47deg/sbt-microsites/issues/256#issuecomment-467477864,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACHc2IuMsEFXCiSO-6rNxdQsHugvKgfVks5vRU-ngaJpZM4R660g
.


Multiple challenge  issues

Challenge Size your Images has an issue.
User Agent is: Mozilla/5.0 (Linux; Android 4.4.2; SM-T320 Build/KOT49H) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.124 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:

<link href="https://fonts.googleapis.com/css?family=Lobster" rel="stylesheet" type="text/css">

CatPhotoApp

Kitty ipsum dolor sit amet, shed everywhere shed everywhere stretching attack your ankles chase the red dot, hairball run catnip eat the grass sniff.

Purr jump eat the grass rip the couch scratched sunbathe, shed everywhere rip the couch sleep in the sink fluffy fur catnip scratched.

I also have issues with add borders,  add rounded corners and make circular  image. They are all class issues. I am using a tablet and don't  know if that is causing  the problem

Hi @fannster! Thanks for catching this issue. It seems like this is a common issue with mobile devices. They sometimes seem to insert non-breaking spaces rather than normal spaces, which (no pun intended) break the code. If you remove the spaces before the line with width: 100px on it, things work fine. Currently, there are two more open issues about this same thing: #11086 #7753 I definitely feel like this should be addressed soon, but I'm not sure how. If we could automatically check for non-breaking spaces and replace them with normal spaces somehow, that would be amazing.

Perfect thank u

Add Images to your Website

CatPhotoApp
Kitty ipsum dolor sit amet, shed everywhere shed everywhere stretching attack your ankles chase the red dot, hairball run catnip eat the grass sniff.
Purr jump eat the grass rip the couch scratched sunbathe, shed everywhere rip the couch sleep in the sink fluffy fur catnip scratched.
Your page should have an image element.
Your image should have a src attribute that points to the kitten image.
these are not recognized. forum could not find an error
ty

@systimotic do you know if this is fixed on staging?

@dhcodes It was fixed! I believe Lance already shared it with you, but Stuart fixed it in https://github.com/FreeCodeCamp/FreeCodeCamp/pull/11472


Braze SDK endpoints are incorrect

Hey @Flaque - heads up, the SDK URLs are incorrect in this recent update. Correct format is:
https://sdk.iad-01.braze.com 01 through 03 for US
https://sdk.fra-01.braze.eu 01 only for EU
Reference doc:
https://www.braze.com/documentation/FAQs/#which-sdk-endpoint-do-i-use
cc @froodian

Whoops! Thanks for letting us know! ❤


[ENH] Segmentation metrics

Reference Issues/PRs

What does this implement/fix? Explain your changes.

Does your contribution introduce a new dependency? If yes, which one?

What should a reviewer concentrate their feedback on?

Any other comments?

PR checklist

For all contributions

[x] I've added myself to the list of contributors.
[x] Optionally, I've updated sktime's CODEOWNERS to receive notifications about future changes to these files.
[x] I've added unit tests and made sure they pass locally.
[x] The PR title starts with either [ENH], [MNT], [DOC], or [BUG] indicating whether the PR topic is related to enhancement, maintenance, documentation, or bug.

For new estimators

[ ] I've added the estimator to the online documentation.
[ ] I've updated the existing example notebooks or provided a new one to showcase how my estimator works.

Nice!
Should this not inherit from BaseMetric and live in performance_metrics?

I'm happy to move it into performance_metrics but I see little reason for a base class here.

I see little reason for a base class here.

Many metrics are parametric, so inheriting from BaseMetric makes sense.

Sorry I don't see your point, do you care to elaborate. If you refer to metrics in this PR specifically that would be helpful.

@Lovkush-A @aiwalter any chance you could share your thoughts here? Is there a need for a base class where a simple function would do the job?

Is there a need for a base class where a simple function would do the job?

I am in favour of base class, to ensure we have uniform interface. right now, the hausdorff distance has an extra parameter compared to the others. so if we were to do some kind of benchmarking, we cannot simply do: for metric in metrics: metric(true, pred))

Is there a need for a base class where a simple function would do the job?

I am in favour of base class, to ensure we have uniform interface. right now, the hausdorff distance has an extra parameter compared to the others. so if we were to do some kind of benchmarking, we cannot simply do: for metric in metrics: metric(true, pred))

I'm not sure I see you point here, you can still call the function with additional params and a class implementation would have the issue.

I'm not sure I see you point here, you can still call the function with additional params and a class implementation would have the issue.

The additional params would become init params (at least, that is one option). Compare how sklearn has uniform interface despite random forests and linear regressors having different params.


Update README badges

I failed to understand the error in the CI system, do you understand it @yuvipanda?
I've experienced some failures associated with switching from Travis to GitHub actions before, among them are for example that the default checkout of the repo doesn't come with git history, is that needed? I'm generally clueless about fixing the tests unless its generic as I know very little about the codebase atm.

I failed to understand the error in the CI system, do you understand it @yuvipanda?
I've experienced some failures associated with switching from Travis to GitHub actions before, among them are for example that the default checkout of the repo doesn't come with git history, is that needed? I'm generally clueless about fixing the tests unless its generic as I know very little about the codebase atm.

Thanks, @consideRatio! I also don't understand these failures at all :|

Thanks, @consideRatio! I also don't understand these failures at all :|


Fail is a src file does not exist

If src is set with a non existing/readable file (or with an array containing at least one non existing/readable file) then the task does not fail nor warns about it.
I'd strongly prefer it to fail, or at least it would be useful a new option "checkSrcFile" (false by default). If set to true then the concat task would fail if any of the files in src does not exist.

I was very surprised that concatenation of missing files during build time does not fail by default.  I'm astounded that you cannot even configure it to fail.
We had our build concatenate CSS files, and one of the files went missing.  Instead of failing the build as it should, we just got a build with some of our styles missing.  This is simply unacceptable for a build.  (A warning is in no way sufficient - builds are generated automatically and produce easily 100+ lines of output, no one will notice a warning in the output.)
Does anyone have a workaround for this issue?

I would also heavily appreciate a fail-on-null functionality.

this continues to be a problem 2 years on (v0.5.1) and should not have been closed. concat does not throw an error or even warn if a file is missing. in essence concat fails to fail. that's completely unacceptable behavior.
integrating concat with build automation or other integration tools is now entirely suspect. no build can truly be green if concat doesn't recognize missing files as a bad state.

I am currently using the following workaround. I added a filter task to the concat task, as follows:
            filter: function (filepath) {
                if (!grunt.file.exists(filepath)) {
                    grunt.fail.warn('Could not find: ' + filepath);
                } else {
                    return true;
                }
            },
            nonull: true

Now it fails if there is a non-existent file.


Modify Approver List

Description

Remove QE from the list of approvals in order to merge the PR
How Has This Been Tested?

Merge criteria:

[ ] The commits are squashed in a cohesive manner and have meaningful messages.
[ ] For commits that came from upstream, [UPSTREAM] has been prepended to the commit message.
[ ] JIRA link(s):
[ ] The Jira story is acked.
[ ] Live build image:
[ ] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[ ] The developer has manually tested the changes and verified that the changes work.
[ ] QE contact acknowledges that this has been tested and is approved for merge.

https://github.com/red-hat-data-services/odh-deployer/blame/main/CONTRIBUTING.md#L67
https://github.com/red-hat-data-services/odh-deployer/blame/main/CONTRIBUTING.md#L27
need updates too

@Jooho I've added you to the list too

@Jooho I've added you to the list too

hmmmmmmmmmm, could not see jooho in the change list.

@lucferbux did you forget to push your commit?

@lucferbux did you forget to push your commit?

Agh, yes, I ammended the commit and did a quick push, forget to force it.
Give me 15 mins, i had to go out, once im back ill push it for good.

@andrewballantyne done!

@VaishnaviHire I'm sorry i added an extra end line, can you approve it again 😅

@lucferbux hah, QE has to approve the removal of QE? The thread lead me to believe this was a dev decision... can you manually add the label?


BLOOM model mentioned in hub-docs

The model mentioned in Hugging-face hub is actually 176B parameters model by BLOOM. But written as 175B

Hey there! From which place is this screenshot?

do you want to open a PR to fix that, @Muhammad-Ahmad-Ghani? it's in the /docs folder in https://github.com/huggingface/transformers


Use new lock and hash icons in stream modals and add icons to stream options in dropdown_list_widget.

First commit is to use new lock and hash icons in inline_decorated_stream_name template.
Second commit is to add stream-privacy icons in dropdown_list_widget.

Fixes part of #22355

Screenshots and screen captures:
Using new icons -

Icons in dropdown list widgets

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

@alya ready for testing.

Also, I think the icon for web-public streams, the icon is not aligned perfectly for the text inside the modal, but seems better in heading. It is more noticeable when the stream name starts with an uppercase letter. Trying to find a good solution to fix this.

Mm, yeah, it does look quite low in the regular text.

I guess the icons don't live-update if you change stream privacy while the dropdown is open. I don't know how hard that is to fix; I don't think it's a blocker for merging this.

The other thing I noted is that it's a bit odd that you see the privacy icon in the dropdown, but not for the selected stream. (There's no icon in the "Move topic" modal, and a # in the New stream/New user announcements settings. But I think it's OK as an intermediate state.

I guess the icons don't live-update if you change stream privacy while the dropdown is open. I don't know how hard that is to fix; I don't think it's a blocker for merging this.

Yeah, we don't have a goal of supporting that. It's not worth the effort. If we move to a reactive web framework, it'll work automatically for free, but until then, extremely short-lived UI components like modals should generally not bother with live update.

Mm, yeah, it does look quite low in the regular text. Though for some reason it looks better for me?

Maybe it varies with zoom level of browser. The screenshots I shared are at 110% zoom and it looks better to me at 100%. Anyways I have added a commit to use em unit for top property, which should be better instead of using px in any case. Sharing the screenshot below, if we want to update the values though -

The other thing I noted is that it's a bit odd that you see the privacy icon in the dropdown, but not for the selected stream.

Yes, I plan to do this as a follow-up.

Thanks! The screenshots look OK to me.

Looks great to me, merged, thanks @sahil839!


Added a record for SUST

University website URL: https://www.sust.edu/
Long-term IT related curriculum link: https://www.sust.edu/institutes/iict/curriculum

merge PR

reopen


Lines and Files is now an Evoluation Metric

Hi @dicortazar and @sgoggins
In today's (Aug 6th, 2020) Common WG meeting, we decided to move the Lines and Files metric out of Common and into Evolution. We look forward to this metric moving forward in your WG :)

In the spreadsheet.


Fixing optional argument with doubledash (--)

When an use case has an optional argument followed by --, when that argument is skipped, its value is set as --.
I believe this is an unexpected behavior, so I've added a logic to avoid this conflict.
Usage
Usage:
  naval ship [<name>] [-- <ship-instructions>... ]

Before fix:
$ ship Guardian -- echo test
# OK: { "--": true, "<name>": "Guardian", "<ship-instructions>": ["echo", "test"], "ship": true }

$ ship -- echo test
# BAD: { "--": false, "<name>": "--", "<ship-instructions>": ["echo", "test"], "ship": true }

After fix:
$ ship Guardian -- echo test
# OK: { "--": true, "<name>": "Guardian", "<ship-instructions>": ["echo", "test"], "ship": true }

$ ship -- echo test
# OK: { "--": true, "<name>": null, "<ship-instructions>": ["echo", "test"], "ship": true }

I've noticed the same issue happens on http://try.docopt.org. The above use case is available at http://goo.gl/xPwD6A

Thanks, this fixes my issues with -- as well.
it fixes this use case
  prog [-o] [--] <arg>

$ prog -- -o
{"-o": false, "<arg>": "-o", "--": true}

Any date for when this change will be published in npm?


Is it possible to Serialize/Deserialize rust enums?

Support for rust enum?
I appear to be able to serialize a struct with an enum, but can't deserialize. Is this feature supported?
Code below gives
Err(Error { message: "not an enum" })

Test code.
use avro_rs::{Codec, Reader, Schema, Writer, from_value};
use failure::Error;
use serde::{Serialize, Deserialize};

#[derive(Debug, Deserialize, Serialize)]
enum Suit {
    Diamonds,
    Spades,
    Clubs,
    Hearts
}

#[derive(Debug, Deserialize, Serialize)]
struct Test {
    a: i64,
    b: String,
    c: Suit
}

fn main() -> Result<(), Error> {
    let raw_schema = r#"
        {
            "type": "record",
            "name": "Test",
            "fields": [
                {"name": "a", "type": "long", "default": 42},
                {"name": "b", "type": "string"},
                {
                    "name": "c",
                    "type": {
                        "type": "enum",
                        "name": "Suit",
                        "symbols": ["Diamonds", "Spades", "Clubs", "Hearts"]
                    },
                    "default": "Spades"
                }
            ]
        }
    "#;
    let schema = Schema::parse_str(raw_schema).unwrap();
    let mut writer = Writer::with_codec(&schema, Vec::new(), Codec::Null);

    let test = Test {
        a: 1,
        b: "Name".to_string(),
        c: Suit::Spades
    };

    writer.append_ser(test)?;
    writer.flush()?;
    let input = writer.into_inner();
    let reader = Reader::with_schema(&schema, &input[..]).unwrap();

    for record in reader {
        println!("{:?}", from_value::<Test>(&record?));
    }
    Ok(())
}

Here's an attempt to add that functionality: https://github.com/flavray/avro-rs/pull/76

Any movement on this? I have an incoming PR for Schema Compatibility that would gain a bit by having this PR in.

This is not possible for an arbitrary Rust enum. Rust enums are more generic than C-style enums: each variant can contain arbitrary data.


docs: Update Document organization structure

Closes #192
Discussion Items

[ ] How do we re structure README from inside the examples ?

@vladimirvivien  to help discuss the re-grouping of Examples document, I have done it for two files. Wonder what would be the best way to org them

For now, you can just copy them into the docs directory as to keep the examples complete.

You mean keep two copies of it ?

@harshanarayana or keep a README.md in examples that links to where the respective example is documented.  That way, if I browse from example directory I can get back to documentation about example.

That way, if I browse from example directory I can get back to documentation about example.

I thought I can do this easily and created a few symlinks. Seems like github won't redirect you to the symlink location if you click on the file :( It just show the path for which the current file links to.  (The changes are pushed to the branch for now, I will revert them. Leaving them for now just to show you what it looks like.)
Shall I add a section on the docs/README.md that links you to different set of Examples ?  cc @vladimirvivien


memory access out of bounds

My Steps:

convert mp4 to rtmp stream
ffmpeg -re -i /usr/local/src/videos/ychx.mp4 -vcodec libx264 -vprofile baseline -acodec aac -ar 44100 -strict -2 -ac 1 -f flv -s 512x214 -q 10 rtmp://localhost/rtmp1/test

run jsmpeg/websocket-relay.js
node websocket-relay.js supersecret 8081 8082

listen rtmp and pull to websocket 8081
ffmpeg -re -i rtmp://localhost/rtmp1/test -f mpegts http://localhost:8081/supersecret/640/360

start jsmpeg/view-stream.html
http-server

everything is fine, but the browser gives an error, and video flower screen.
Uncaught RuntimeError: memory access out of bounds

I get the same problem! but there is only one thing different from up.

The local data(mp4 video)  was directly pulled to http://localhost:8081/supersecret

And I don't konw how to do with it! crying for help

Would it be possible to use only one instance of ffmpeg?
Convert mp4 into mpegts stream:
ffmpeg -i /usr/local/src/videos/ychx.mp4  -f mpegts -codec:v mpegvideo1 -s 640x360 -q:v 10 http://localhost:8081/supersecret/640/360


Hardware source requirement.

Nice work, and thanks to your kindful share! But I wonder the GPU requirement for the training and how to switch the VQ-Diffusion-S for the training? Looking forward to your reply!

Nice work, and thanks to your kindful share! But I wonder the GPU requirement for the training and how to switch the VQ-Diffusion-S for the training? Looking forward to your reply!

For all the experiments in the paper except pretraining on CC dataset, we use only 8 V100s. For training VQ-Diffusion-S, we provided the details in the appendix, and also, we provide a training config on cub200 dataset (configs/cub200_s.yaml). Hope it can help you.

Thanks for timely reply, it really useful to me.


Can't play only selected file

Webtorrent Desktop 0.3.3
Windows 10
I was trying to watch only second episode of a TV series but even if I explicitliy click play button of only that video, it starts to download all files instead of downloading only selected file.

https://github.com/feross/webtorrent-desktop/issues/360


Build fails with LibreSSL when built as a dependency

I am hitting odd build failures, that I can't seem to diagnose properly.
The following compiles without any error:
$ git checkout libgit2-sys-0.7.1
$ cargo build

However, when I build cargo, I get the following message:
$ cargo build
[...]
error: failed to run custom build command for `libgit2-sys v0.7.1`
process didn't exit successfully: `/home/twk/src/clones/cargo/target/debug/build/libgit2-sys-ae220773f7e720dd/build-script-build` (exit code: 101)
--- stdout
running: "cmake" "/home/twk/.cargo/registry/src/github.com-1ecc6299db9ec823/libgit2-sys-0.7.1/libgit2" "-DBUILD_SHARED_LIBS=OFF" "-DBUILD_CLAR=OFF" "-DCMAKE_INSTALL_PREFIX=/home/twk/src/clones/cargo/target/debug/build/libgit2-sys-3e8a6c13883d376e/out" "-DCMAKE_C_FLAGS= -ffunction-sections -fdata-sections -fPIC -m64" "-DCMAKE_C_COMPILER=/usr/bin/cc" "-DCMAKE_CXX_FLAGS= -ffunction-sections -fdata-sections -fPIC -m64" "-DCMAKE_CXX_COMPILER=/usr/bin/c++" "-DCMAKE_BUILD_TYPE=Debug"
-- The C compiler identification is Clang 6.0.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.2")
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - not found
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
-- Performing Test HAVE_STRUCT_STAT_ST_MTIM
-- Performing Test HAVE_STRUCT_STAT_ST_MTIM - Success
-- Performing Test HAVE_STRUCT_STAT_ST_MTIMESPEC
-- Performing Test HAVE_STRUCT_STAT_ST_MTIMESPEC - Failed
-- Performing Test HAVE_STRUCT_STAT_MTIME_NSEC
-- Performing Test HAVE_STRUCT_STAT_MTIME_NSEC - Failed
-- Performing Test HAVE_STRUCT_STAT_NSEC
-- Performing Test HAVE_STRUCT_STAT_NSEC - Success
-- Performing Test IS_WALL_SUPPORTED
-- Performing Test IS_WALL_SUPPORTED - Success
-- Performing Test IS_WEXTRA_SUPPORTED
-- Performing Test IS_WEXTRA_SUPPORTED - Success
-- Performing Test IS_WDOCUMENTATION_SUPPORTED
-- Performing Test IS_WDOCUMENTATION_SUPPORTED - Success
-- Performing Test IS_WNO-MISSING-FIELD-INITIALIZERS_SUPPORTED
-- Performing Test IS_WNO-MISSING-FIELD-INITIALIZERS_SUPPORTED - Success
-- Performing Test IS_WSTRICT-ALIASING_SUPPORTED
-- Performing Test IS_WSTRICT-ALIASING_SUPPORTED - Success
-- Performing Test IS_WSTRICT-PROTOTYPES_SUPPORTED
-- Performing Test IS_WSTRICT-PROTOTYPES_SUPPORTED - Success
-- Performing Test IS_WDECLARATION-AFTER-STATEMENT_SUPPORTED
-- Performing Test IS_WDECLARATION-AFTER-STATEMENT_SUPPORTED - Success
-- Performing Test IS_WNO-UNUSED-CONST-VARIABLE_SUPPORTED
-- Performing Test IS_WNO-UNUSED-CONST-VARIABLE_SUPPORTED - Success
-- Performing Test IS_WNO-UNUSED-FUNCTION_SUPPORTED
-- Performing Test IS_WNO-UNUSED-FUNCTION_SUPPORTED - Success
-- Looking for regcomp_l
-- Looking for regcomp_l - not found
-- Looking for futimens
-- Looking for futimens - found
-- Looking for qsort_r
-- Looking for qsort_r - found
-- Looking for qsort_s
-- Looking for qsort_s - not found
-- Looking for clock_gettime in rt
-- Looking for clock_gettime in rt - found
-- Checking for module 'libcurl'
--   Found libcurl, version 7.60.0
-- Found OpenSSL: /usr/lib/libcrypto.so (found version "2.0.0")
-- Found HTTP_Parser: /usr/include
-- Found ZLIB: /usr/lib/libz.so (found version "1.2.11")
-- Checking for module 'libssh2'
--   Found libssh2, version 1.8.0
-- Looking for libssh2_userauth_publickey_frommemory in ssh2
-- Looking for libssh2_userauth_publickey_frommemory in ssh2 - found
-- Enabled features:
 * threadsafe, threadsafe support
 * cURL, cURL for HTTP proxy support
 * HTTPS, using OpenSSL
 * SHA, using CollisionDetection
 * http-parser, http-parser support
 * zlib, using system zlib
 * SSH, SSH transport support

-- Disabled features:
 * debugpool, debug pool allocator
 * tracing, tracing support
 * SPNEGO, SPNEGO authentication support
 * iconv, iconv encoding conversion support

-- Configuring done
-- Generating done
-- Build files have been written to: /home/twk/src/clones/cargo/target/debug/build/libgit2-sys-3e8a6c13883d376e/out/build
running: "cmake" "--build" "." "--target" "install" "--config" "Debug" "--"
Scanning dependencies of target git2internal
[  1%] Building C object src/CMakeFiles/git2internal.dir/annotated_commit.c.o
[  2%] Building C object src/CMakeFiles/git2internal.dir/apply.c.o
[  2%] Building C object src/CMakeFiles/git2internal.dir/attr.c.o
[  3%] Building C object src/CMakeFiles/git2internal.dir/attr_file.c.o
[  4%] Building C object src/CMakeFiles/git2internal.dir/attrcache.c.o
[  4%] Building C object src/CMakeFiles/git2internal.dir/blame.c.o
[  5%] Building C object src/CMakeFiles/git2internal.dir/blame_git.c.o
[  6%] Building C object src/CMakeFiles/git2internal.dir/blob.c.o
[  6%] Building C object src/CMakeFiles/git2internal.dir/branch.c.o
[  7%] Building C object src/CMakeFiles/git2internal.dir/buf_text.c.o
[  8%] Building C object src/CMakeFiles/git2internal.dir/buffer.c.o
[  8%] Building C object src/CMakeFiles/git2internal.dir/cache.c.o
[  9%] Building C object src/CMakeFiles/git2internal.dir/checkout.c.o
[ 10%] Building C object src/CMakeFiles/git2internal.dir/cherrypick.c.o
[ 11%] Building C object src/CMakeFiles/git2internal.dir/clone.c.o
[ 11%] Building C object src/CMakeFiles/git2internal.dir/commit.c.o
[ 12%] Building C object src/CMakeFiles/git2internal.dir/commit_list.c.o
[ 13%] Building C object src/CMakeFiles/git2internal.dir/config.c.o
[ 13%] Building C object src/CMakeFiles/git2internal.dir/config_cache.c.o
[ 14%] Building C object src/CMakeFiles/git2internal.dir/config_file.c.o
[ 15%] Building C object src/CMakeFiles/git2internal.dir/config_parse.c.o
[ 15%] Building C object src/CMakeFiles/git2internal.dir/crlf.c.o
[ 16%] Building C object src/CMakeFiles/git2internal.dir/date.c.o
[ 17%] Building C object src/CMakeFiles/git2internal.dir/delta.c.o
[ 17%] Building C object src/CMakeFiles/git2internal.dir/describe.c.o
[ 18%] Building C object src/CMakeFiles/git2internal.dir/diff.c.o
[ 19%] Building C object src/CMakeFiles/git2internal.dir/diff_driver.c.o
[ 20%] Building C object src/CMakeFiles/git2internal.dir/diff_file.c.o
[ 20%] Building C object src/CMakeFiles/git2internal.dir/diff_generate.c.o
[ 21%] Building C object src/CMakeFiles/git2internal.dir/diff_parse.c.o
[ 22%] Building C object src/CMakeFiles/git2internal.dir/diff_print.c.o
[ 22%] Building C object src/CMakeFiles/git2internal.dir/diff_stats.c.o
[ 23%] Building C object src/CMakeFiles/git2internal.dir/diff_tform.c.o
[ 24%] Building C object src/CMakeFiles/git2internal.dir/diff_xdiff.c.o
[ 24%] Building C object src/CMakeFiles/git2internal.dir/errors.c.o
[ 25%] Building C object src/CMakeFiles/git2internal.dir/fetch.c.o
[ 26%] Building C object src/CMakeFiles/git2internal.dir/fetchhead.c.o
[ 26%] Building C object src/CMakeFiles/git2internal.dir/filebuf.c.o
[ 27%] Building C object src/CMakeFiles/git2internal.dir/fileops.c.o
[ 28%] Building C object src/CMakeFiles/git2internal.dir/filter.c.o
[ 28%] Building C object src/CMakeFiles/git2internal.dir/fnmatch.c.o
[ 29%] Building C object src/CMakeFiles/git2internal.dir/global.c.o
[ 30%] Building C object src/CMakeFiles/git2internal.dir/graph.c.o

--- stderr
fatal: not a git repository (or any of the parent directories): .git
CMake Warning:
  Manually-specified variables were not used by the project:

    CMAKE_CXX_COMPILER
    CMAKE_CXX_FLAGS

In file included from /home/twk/.cargo/registry/src/github.com-1ecc6299db9ec823/libgit2-sys-0.7.1/libgit2/src/global.c:14:
/home/twk/.cargo/registry/src/github.com-1ecc6299db9ec823/libgit2-sys-0.7.1/libgit2/src/streams/openssl.h:36:25: error: static declaration of 'BIO_meth_new' follows non-static declaration
GIT_INLINE(BIO_METHOD*) BIO_meth_new(int type, const char *name)
                        ^
/usr/include/openssl/bio.h:338:13: note: previous declaration is here
BIO_METHOD *BIO_meth_new(int type, const char *name);
            ^
In file included from /home/twk/.cargo/registry/src/github.com-1ecc6299db9ec823/libgit2-sys-0.7.1/libgit2/src/global.c:14:
/home/twk/.cargo/registry/src/github.com-1ecc6299db9ec823/libgit2-sys-0.7.1/libgit2/src/streams/openssl.h:49:18: error: static declaration of 'BIO_meth_free' follows non-static declaration
GIT_INLINE(void) BIO_meth_free(BIO_METHOD *biom)
                 ^
/usr/include/openssl/bio.h:339:6: note: previous declaration is here
void BIO_meth_free(BIO_METHOD *biom);
     ^
In file included from /home/twk/.cargo/registry/src/github.com-1ecc6299db9ec823/libgit2-sys-0.7.1/libgit2/src/global.c:14:
/home/twk/.cargo/registry/src/github.com-1ecc6299db9ec823/libgit2-sys-0.7.1/libgit2/src/streams/openssl.h:54:17: error: static declaration of 'BIO_meth_set_write' follows non-static declaration
GIT_INLINE(int) BIO_meth_set_write(BIO_METHOD *biom, int (*write) (BIO *, const char *, int))
                ^
/usr/include/openssl/bio.h:341:5: note: previous declaration is here
int BIO_meth_set_write(BIO_METHOD *biom,
    ^
In file included from /home/twk/.cargo/registry/src/github.com-1ecc6299db9ec823/libgit2-sys-0.7.1/libgit2/src/global.c:14:
/home/twk/.cargo/registry/src/github.com-1ecc6299db9ec823/libgit2-sys-0.7.1/libgit2/src/streams/openssl.h:60:17: error: static declaration of 'BIO_meth_set_read' follows non-static declaration
GIT_INLINE(int) BIO_meth_set_read(BIO_METHOD *biom, int (*read) (BIO *, char *, int))
                ^
/usr/include/openssl/bio.h:344:5: note: previous declaration is here
int BIO_meth_set_read(BIO_METHOD *biom, int (*read)(BIO *, char *, int));
    ^
In file included from /home/twk/.cargo/registry/src/github.com-1ecc6299db9ec823/libgit2-sys-0.7.1/libgit2/src/global.c:14:
/home/twk/.cargo/registry/src/github.com-1ecc6299db9ec823/libgit2-sys-0.7.1/libgit2/src/streams/openssl.h:66:17: error: static declaration of 'BIO_meth_set_puts' follows non-static declaration
GIT_INLINE(int) BIO_meth_set_puts(BIO_METHOD *biom, int (*puts) (BIO *, const char *))
                ^
/usr/include/openssl/bio.h:346:5: note: previous declaration is here
int BIO_meth_set_puts(BIO_METHOD *biom, int (*puts)(BIO *, const char *));
    ^
In file included from /home/twk/.cargo/registry/src/github.com-1ecc6299db9ec823/libgit2-sys-0.7.1/libgit2/src/global.c:14:
/home/twk/.cargo/registry/src/github.com-1ecc6299db9ec823/libgit2-sys-0.7.1/libgit2/src/streams/openssl.h:72:17: error: static declaration of 'BIO_meth_set_gets' follows non-static declaration
GIT_INLINE(int) BIO_meth_set_gets(BIO_METHOD *biom, int (*gets) (BIO *, char *, int))
                ^
/usr/include/openssl/bio.h:348:5: note: previous declaration is here
int BIO_meth_set_gets(BIO_METHOD *biom, int (*gets)(BIO *, char *, int));
    ^
In file included from /home/twk/.cargo/registry/src/github.com-1ecc6299db9ec823/libgit2-sys-0.7.1/libgit2/src/global.c:14:
/home/twk/.cargo/registry/src/github.com-1ecc6299db9ec823/libgit2-sys-0.7.1/libgit2/src/streams/openssl.h:79:17: error: static declaration of 'BIO_meth_set_ctrl' follows non-static declaration
GIT_INLINE(int) BIO_meth_set_ctrl(BIO_METHOD *biom, long (*ctrl) (BIO *, int, long, void *))
                ^
/usr/include/openssl/bio.h:350:5: note: previous declaration is here
int BIO_meth_set_ctrl(BIO_METHOD *biom, long (*ctrl)(BIO *, int, long, void *));
    ^
In file included from /home/twk/.cargo/registry/src/github.com-1ecc6299db9ec823/libgit2-sys-0.7.1/libgit2/src/global.c:14:
/home/twk/.cargo/registry/src/github.com-1ecc6299db9ec823/libgit2-sys-0.7.1/libgit2/src/streams/openssl.h:85:17: error: static declaration of 'BIO_meth_set_create' follows non-static declaration
GIT_INLINE(int) BIO_meth_set_create(BIO_METHOD *biom, int (*create) (BIO *))
                ^
/usr/include/openssl/bio.h:352:5: note: previous declaration is here
int BIO_meth_set_create(BIO_METHOD *biom, int (*create)(BIO *));
    ^
In file included from /home/twk/.cargo/registry/src/github.com-1ecc6299db9ec823/libgit2-sys-0.7.1/libgit2/src/global.c:14:
/home/twk/.cargo/registry/src/github.com-1ecc6299db9ec823/libgit2-sys-0.7.1/libgit2/src/streams/openssl.h:91:17: error: static declaration of 'BIO_meth_set_destroy' follows non-static declaration
GIT_INLINE(int) BIO_meth_set_destroy(BIO_METHOD *biom, int (*destroy) (BIO *))
                ^
/usr/include/openssl/bio.h:354:5: note: previous declaration is here
int BIO_meth_set_destroy(BIO_METHOD *biom, int (*destroy)(BIO *));
    ^
In file included from /home/twk/.cargo/registry/src/github.com-1ecc6299db9ec823/libgit2-sys-0.7.1/libgit2/src/global.c:14:
/home/twk/.cargo/registry/src/github.com-1ecc6299db9ec823/libgit2-sys-0.7.1/libgit2/src/streams/openssl.h:97:17: error: static declaration of 'BIO_get_new_index' follows non-static declaration
GIT_INLINE(int) BIO_get_new_index(void)
                ^
/usr/include/openssl/bio.h:599:5: note: previous declaration is here
int BIO_get_new_index(void);
    ^
In file included from /home/twk/.cargo/registry/src/github.com-1ecc6299db9ec823/libgit2-sys-0.7.1/libgit2/src/global.c:14:
/home/twk/.cargo/registry/src/github.com-1ecc6299db9ec823/libgit2-sys-0.7.1/libgit2/src/streams/openssl.h:103:18: error: static declaration of 'BIO_set_init' follows non-static declaration
GIT_INLINE(void) BIO_set_init(BIO *b, int init)
                 ^
/usr/include/openssl/bio.h:610:7: note: previous declaration is here
void    BIO_set_init(BIO *a, int init);
        ^
In file included from /home/twk/.cargo/registry/src/github.com-1ecc6299db9ec823/libgit2-sys-0.7.1/libgit2/src/global.c:14:
/home/twk/.cargo/registry/src/github.com-1ecc6299db9ec823/libgit2-sys-0.7.1/libgit2/src/streams/openssl.h:108:18: error: static declaration of 'BIO_set_data' follows non-static declaration
GIT_INLINE(void) BIO_set_data(BIO *a, void *ptr)
                 ^
/usr/include/openssl/bio.h:609:7: note: previous declaration is here
void    BIO_set_data(BIO *a, void *ptr);
        ^
In file included from /home/twk/.cargo/registry/src/github.com-1ecc6299db9ec823/libgit2-sys-0.7.1/libgit2/src/global.c:14:
/home/twk/.cargo/registry/src/github.com-1ecc6299db9ec823/libgit2-sys-0.7.1/libgit2/src/streams/openssl.h:113:19: error: static declaration of 'BIO_get_data' follows non-static declaration
GIT_INLINE(void*) BIO_get_data(BIO *a)
                  ^
/usr/include/openssl/bio.h:608:8: note: previous declaration is here
void    *BIO_get_data(BIO *a);
         ^
In file included from /home/twk/.cargo/registry/src/github.com-1ecc6299db9ec823/libgit2-sys-0.7.1/libgit2/src/global.c:14:
/home/twk/.cargo/registry/src/github.com-1ecc6299db9ec823/libgit2-sys-0.7.1/libgit2/src/streams/openssl.h:118:35: error: static declaration of 'ASN1_STRING_get0_data' follows non-static declaration
GIT_INLINE(const unsigned char *) ASN1_STRING_get0_data(const ASN1_STRING *x)
                                  ^
/usr/include/openssl/asn1.h:788:22: note: previous declaration is here
const unsigned char *ASN1_STRING_get0_data(const ASN1_STRING *x);
                     ^
14 errors generated.
make[2]: *** [src/CMakeFiles/git2internal.dir/build.make:596: src/CMakeFiles/git2internal.dir/global.c.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [CMakeFiles/Makefile2:125: src/CMakeFiles/git2internal.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
thread 'main' panicked at '
command did not execute successfully, got: exit code: 2

build script failed, must exit now', /home/twk/.cargo/registry/src/github.com-1ecc6299db9ec823/cmake-0.1.29/src/lib.rs:632:5
stack backtrace:
   0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
             at libstd/sys/unix/backtrace/tracing/gcc_s.rs:49
   1: std::sys_common::backtrace::print
             at libstd/sys_common/backtrace.rs:71
             at libstd/sys_common/backtrace.rs:59
   2: std::panicking::default_hook::{{closure}}
             at libstd/panicking.rs:211
   3: std::panicking::default_hook
             at libstd/panicking.rs:227
   4: std::panicking::rust_panic_with_hook
             at libstd/panicking.rs:463
   5: std::panicking::begin_panic_fmt
             at libstd/panicking.rs:350
   6: cmake::fail
             at /home/twk/.cargo/registry/src/github.com-1ecc6299db9ec823/cmake-0.1.29/src/lib.rs:632
   7: cmake::run
             at /home/twk/.cargo/registry/src/github.com-1ecc6299db9ec823/cmake-0.1.29/src/lib.rs:613
   8: cmake::Config::build
             at /home/twk/.cargo/registry/src/github.com-1ecc6299db9ec823/cmake-0.1.29/src/lib.rs:520
   9: build_script_build::main
             at ./build.rs:128
  10: std::rt::lang_start::{{closure}}
             at /checkout/src/libstd/rt.rs:74
  11: std::panicking::try::do_call
             at libstd/rt.rs:59
             at libstd/panicking.rs:310
  12: __rust_maybe_catch_panic
             at libpanic_unwind/lib.rs:105
  13: std::rt::lang_start_internal
             at libstd/panicking.rs:289
             at libstd/panic.rs:374
             at libstd/rt.rs:58
  14: std::rt::lang_start
             at /checkout/src/libstd/rt.rs:74
  15: main
  16: __libc_start_main
             at ../csu/libc-start.c:308
  17: _start
             at ../sysdeps/x86_64/start.S:120

The system in question runs LibreSSL 2.7.3.
I'm not sure how I could gather any more useful info, as I can't imagine the source of the problem without being able to isolate it properly -- the C compiler's output doesn't point at anything trivial either.

It looks like this may be a libgit2 build issue?

Hm, do you have any idea why it happens only when built as a dependency?

This is fixed upstream in https://github.com/libgit2/libgit2/commit/7490d449b518115a1ae86b01397e95c38e39cff1
So it should vanish when the libgit2 submodule moves from c9d59c6 to a commit beyond 7490d44

Awesome! I think all we'll need here is a PR to update the submodule now!

Alright, issue is fixed. Thanks everyone!


*fix) add define HAVE_USLEEP

It's what I used for the issue #148
Based on this blog http://beets.radbox.org/blog/sqlite-nightmare.html, http://mail-index.netbsd.org/current-users/2012/06/01/msg020320.html.
It works fine to me now, but I am very NOT sure it is the code what solved the problem.
Just PR for more discuss.The #148 has obstruct me days.

This works for my issue (database is locked). Thanks!

do NOT define in sqlite3-binding.c
please add cgo CFLAGS.

@mattn got it. @donlzx attention buddy.

+1
I ran into this error as well.


RuntimeError: CUDA error: device-side assert triggered

💡 Your Question

I am following - https://colab.research.google.com/drive/10N6NmSMCiRnFlKV9kaIS_z3pk0OI1xKC?usp=sharing (The basic notebook). However, I am on a university cluster.

Please let me know if you need any other information.
Versions
No response

Most likely this error caused by inconsistency in a number of classes when creating a model and the number of classes in dataset.
Note that class labels are expected to be zero-based. If you are using yolo format dataset you may want to double check that class labels are indeed zero-based  there.

Thank you very much! That seemed to solved the problem.


Upgrade ZooKeeper to 3.4.12 and Scala to 2.12.6

ZK 3.4.12 fixes the regression that forced us to go back to
3.4.10. Release notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310801&version=12342040
Scala 2.12.6 fixes the issue that prevented us from upgrading
to 2.12.5.
Committer Checklist (excluded from commit message)

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

@junrao trying the ZK upgrade again.


Avoid parsing JSON in setTextPayload

Purpose

When the contentType header is set to application/json in setTextPayload function it tends to be serialized as JSON which is incorrect. This should be simply parsed as string. This PR fixes this issue. Whatever the header value is setTextPayload would parse it as string.

Resolve https://github.com/ballerina-platform/ballerina-lang/issues/15514
Approach

Use a native data to track setText function

Samples

N/A

Remarks

N/A

Check List

[ ] Read the Contributing Guide
[ ] Required Balo version update
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[x] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

@riyafa Instead of passing a flag can't we come up with two different methods... passing a flag itself says a particular method is doing more than one thing.

@shafreenAnfar which method are you referring to?


Plans to add BLEURT metric?

Would be a great addition.
Thibault Sellam, Dipanjan Das, and Ankur P.
Parikh. 2020. Bleurt: Learning robust metrics
for text generation.

MoverScore too
Wei Zhao, Maxime Peyrard, Fei Liu, Yang Gao, Christian M. Meyer, and Steffen Eger. 2019. MoverScore:
Text Generation Evaluating with Contextualized Embeddings and Earth Mover Distance.

Hi @ogencoglu, thank you very much for your question.
Yes, we are actively working on incorporating wrappers for BLEURT, MoverScore, METEOR, and various other automatic string-based evaluation metrics in the near future. Please stay tuned for further updates!
PS. We also warmly welcome our community members to contribute and expand the library based on their expertise and interests; so, please feel free to make your own valuable additions.

Thank you for the swift reply @suzgunmirac ! Appreciated!

Continuing the metrics discussion.
I wonder whether descriptive metrics would enhance this library. For instance something like textdescriptives library. These metrics are not necessarily string2string, they are stuff like readability, coherence, perplexity etc. calculated from a single doc. But a readability vector can be calculated and used as a string2string metric I guess.
Example use case would be semantic search with faiss or any approximate nearest neighbor that returns similar docs and then returned docs can be re-ranked with respect to ease of readability or with respect to similarity of query doc's readability.
This is not a suggestion but just an idea that I wanted to document here, in case you find it relevant.

Thank you very much for suggesting the use of descriptive metrics in our library, as well as sharing a reference to the TextDescriptives library! TextDescriptives seems like a wonderful resource! We are indeed planning to incorporate additional metrics and string measures such as perplexity into our metrics module in the near future.


Tibialyzer problem

Hello i have a problem with mine tibialyzer also evry time the app add something like monster/dmg/or some numbers the bar on my left is refreshing/flipping i dont know what to say so i did a short movie
https://www.youtube.com/watch?v=oomQlwtmnGA
Maybe someone can help? @Mytherin

Do you have this problem only with the Tibialyzer 1.4.2 beta, or also with version 1.3.0?

@Mytherin version 1.3.0 do not detect mine client

@Mytherin
On the neewest client same problem :/ Maybe something to change in windows settings? You know?


Target mode for systemd service helper

Makes it so that local cookbook can bounce a remote service over
train/ssh/whatever.  Works at least for ubuntu.
Introduces a fairly rudimentary TrainHelpers class, using some
inspiration from ohbye.

Tests?

Also the DCO is failing here


Foscam component broken in 0.52.0

Home Assistant release (hass --version):
0.52.0 (installed with the AiO installer)
Python release (python3 --version):
3.4.2
Component/platform:
Foscam
Description of problem:
After upgrading from 0.51.2 to 0.52.0, the Foscam component is broken. An additional restart of Home Assistant after the upgrade did not fix the issue.
Expected:
Foscam integration should still work
Problem-relevant configuration.yaml entries and steps to reproduce:
camera:
  - platform: foscam
    name: "Bedroom"
    ip: !secret CAMERA_FOSCAM_IP_I
    port: !secret CAMERA_FOSCAM_PORT
    username: !secret CAMERA_FOSCAM_USERNAME
    password: !secret CAMERA_FOSCAM_PASSWORD

  - platform: foscam
    name: "Living area"
    ip: !secret CAMERA_FOSCAM_IP_II
    port: !secret CAMERA_FOSCAM_PORT
    username: !secret CAMERA_FOSCAM_USERNAME
    password: !secret CAMERA_FOSCAM_PASSWORD

  - platform: foscam
    name: "Office"
    ip: !secret CAMERA_FOSCAM_IP_III
    port: !secret CAMERA_FOSCAM_PORT
    username: !secret CAMERA_FOSCAM_USERNAME
    password: !secret CAMERA_FOSCAM_PASSWORD

Traceback (if applicable):
2017-08-12 23:40:56 ERROR (MainThread) [homeassistant.components.camera] Error while setting up platform foscam
Traceback (most recent call last):
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/entity_component.py", line 164, in _async_setup_platform
    SLOW_SETUP_MAX_WAIT, loop=self.hass.loop)
  File "/usr/lib/python3.4/asyncio/tasks.py", line 372, in wait_for
    return fut.result()
  File "/usr/lib/python3.4/asyncio/futures.py", line 277, in result
    raise self._exception
  File "/usr/lib/python3.4/concurrent/futures/thread.py", line 54, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/camera/foscam.py", line 39, in setup_platform
    add_devices([FoscamCam(config)])
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/camera/foscam.py", line 56, in __init__
    from foscam import FoscamCamera
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/foscam/__init__.py", line 1, in <module>
    from foscam import FoscamCamera
ImportError: cannot import name 'FoscamCamera'
2017-08-12 23:40:57 ERROR (MainThread) [homeassistant.components.camera] Error while setting up platform foscam
Traceback (most recent call last):
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/entity_component.py", line 164, in _async_setup_platform
    SLOW_SETUP_MAX_WAIT, loop=self.hass.loop)
  File "/usr/lib/python3.4/asyncio/tasks.py", line 372, in wait_for
    return fut.result()
  File "/usr/lib/python3.4/asyncio/futures.py", line 277, in result
    raise self._exception
  File "/usr/lib/python3.4/concurrent/futures/thread.py", line 54, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/camera/foscam.py", line 39, in setup_platform
    add_devices([FoscamCam(config)])
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/camera/foscam.py", line 56, in __init__
    from foscam import FoscamCamera
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/foscam/__init__.py", line 1, in <module>
    from foscam import FoscamCamera
ImportError: cannot import name 'FoscamCamera'
2017-08-12 23:40:57 ERROR (MainThread) [homeassistant.components.camera] Error while setting up platform foscam
Traceback (most recent call last):
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/entity_component.py", line 164, in _async_setup_platform
    SLOW_SETUP_MAX_WAIT, loop=self.hass.loop)
  File "/usr/lib/python3.4/asyncio/tasks.py", line 372, in wait_for
    return fut.result()
  File "/usr/lib/python3.4/asyncio/futures.py", line 277, in result
    raise self._exception
  File "/usr/lib/python3.4/concurrent/futures/thread.py", line 54, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/camera/foscam.py", line 39, in setup_platform
    add_devices([FoscamCam(config)])
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/camera/foscam.py", line 56, in __init__
    from foscam import FoscamCamera
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/foscam/__init__.py", line 1, in <module>
    from foscam import FoscamCamera
ImportError: cannot import name 'FoscamCamera'

Additional info:
I'm using a Foscam R2 V1 and two R2 V3's

I am having the same issue
after upgrade this plug in broke!

CC @viswa-swami

Any work arounds for this @viswa-swami ??

As I wrote in the devs channel, it's a likely a name clash:
pyfoscam 1.2 contains foscam.py and the camera component in HASS is also called foscam.py, so from foscam import FoscamCamera will refer to the HASS component, not pyfoscam 1.2

Related issue: https://github.com/quatanium/foscam-python-lib/issues/15

Do note that it's broken as of 0.51 (at least from my perspective)
As mentioned in some earlier discussion on the community forums the workaround was to change 'import foscam' to 'import foscam.foscam' which I can confirm is working by manually adjusting.
https://github.com/home-assistant/home-assistant/commit/e40388e7ad90c887cc795f86d17f31dc42d88a29#diff-d2a98e4969c1e91ad53f86f06b98fba2 introduced the import foscam again.
Changing it in the site-packages foscam' init resolves it
Also mentioned in https://community.home-assistant.io/t/foscam-error-with-0-51-1/24292/2

After i upgraded to 0.51.1 i can confirm the component was broken (I was at 0.47.x)

I have opened a PR against that lib to make the import work https://github.com/quatanium/foscam-python-lib/pull/18

Would be nice to have my foscam running again :P

+1 this is rather annoying indeed.. from what I see everything that can be done is done

works with workaround.. thanks guys

The PR the lib has been merged https://github.com/quatanium/foscam-python-lib/pull/18 can this fix be included in a patch release?

I've asked the author to release a new version to PyPi.

Hi @balloob, sorry about not being able to check on this for so long. I was on vacation and couldn't check on this.
Is there anything to do in this now?
I have been running that code in my home assistant without any import issue. Not sure if it is running because of some caching !!!

@balloob I think you're also missing a fix for this in the init file.  Can you do it in both?

just updated to 0.52.1 and still have problem with foscam
2017-08-28 20:18:53 ERROR (MainThread) [homeassistant.components.camera] Error while setting up platform foscam
Traceback (most recent call last):
  File "/usr/local/lib/python3.4/dist-packages/homeassistant/helpers/entity_component.py", line 164, in _async_setup_platform
    SLOW_SETUP_MAX_WAIT, loop=self.hass.loop)
  File "/usr/lib/python3.4/asyncio/tasks.py", line 378, in wait_for
    return fut.result()
  File "/usr/lib/python3.4/asyncio/futures.py", line 274, in result
    raise self._exception
  File "/usr/lib/python3.4/concurrent/futures/thread.py", line 54, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.4/dist-packages/homeassistant/components/camera/foscam.py", line 39, in setup_platform
    add_devices([FoscamCam(config)])
  File "/usr/local/lib/python3.4/dist-packages/homeassistant/components/camera/foscam.py", line 56, in __init__
    from foscam.foscam import FoscamCamera
  File "/var/opt/homeassistant/deps/lib/python3.4/site-packages/foscam/__init__.py", line 1, in <module>
    from foscam import FoscamCamera
ImportError: cannot import name 'FoscamCamera'

@bymem make the same change committed above to /var/opt/homeassistant/deps/lib/python3.4/site-packages/foscam/__init__.py.
I did that on my install and it fixes it.

@superm1 yes that did the trick...

@viswa-swami any chance that you can submit a fix to Home Assistant. For example upload the package yourself to PyPi (under a different name) and submit an update to the requirements.

@balloob sure. My work wouldn't let me try this during the weekdays.  Let me try this weekend and let you know.
Can't we give the requirements directly as the GitHub link itself to that respective library?

We don't link to GitHub directly anymore.
If you manage to get this done in the weekend, it can go with 0.53.1

@balloob I have created a github project for python-foscam (https://github.com/viswa-swami/python-foscam)
I haven't had a chance to test it yet. Once tested, I will push it to pypi and update the homeassistant reuqirements accordingly.
When are you planning to release 0.53.1 ?


Zero-config support for Jekyll

That will hopefully help us get rid of https://github.com/zeit/now-examples/blob/master/jekyll/package.json

Thank you for creating this issue!
Please note that – in order for us to be able to handle each feature request with care – we have to consume all of them through a unified pipeline that makes it easier for us to prioritize, track and progress on the features our user base is interested in.
In turn, the Issues tab on this repository is best only be used for reporting bugs, which we can immediately act on.
For well-explained feature requests (like the one you just posted), please contact us at<EMAIL_ADDRESS>so that we can consider adding it to our roadmap.
In the case of your specific feature recommendation, you can rest assured that we're already tracking it on our roadmap and you can expect to see an update on our Twitter account or Blog soon.


New method getSegmenter()

So that one can, on a script, getSegmenter().getClassifier(), to then e.g., call setNumThreads(1) on the underlying FastRandomForest instance. At the moment there's no way to set the number of threads used to 1 except via Prefs.setThreads(1), which is fragile.

I would like to understand what the use case for this looks like. To my understanding the effect of calling setNumThreads(1) will only effect the random forest training. Is that your intention?
Could you please explain a bit why you want to run this single-threaded?

Thank you, of course: I'm running 256 threads, each extracting SIFT
features from an image, and I'm discarding features not in the tissue by
using a model trained in LabKit to detect what is tissue and what is empty
resin (not tissue) on a scaled down version of the image. Works very well,
but needs a single thread application.
El dv., 5 de jul. 2024, 10:00, Matthias Arzt @.***> va
escriure:

I would like to understand what the use case for this looks like. To my
understanding the effect of calling setNumThreads(1) will only effect the
random forest training. Is that your intention?
Could you please explain a bit why you want to run this single-threaded?
—
Reply to this email directly, view it on GitHub
https://github.com/juglab/labkit-ui/pull/119#issuecomment-2210485261,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAMKGSH37UGBZIGYMNLVTLZKZODHAVCNFSM6AAAAABJ7REZSOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJQGQ4DKMRWGE
.
You are receiving this because you authored the thread.Message ID:
@.***>

Segmenter: Add public method getSegmenter() that indirectly allows to set the number of threads used during RF training


795 ensure filenames are valid and test international filenames and text

Pull Request Overview

Change to storing Filenames as hashes of the filename with extension
Change multiple places where this is used in the system
On AGS creation do the mapping from the filenames uploaded to the stored filenames.
On mission creation (No filenames in the create message), just use the hashes
Wrote test utils to store as this format and changed all test file writing to use them
Increase testing of international data coming into the system
Some test tweaks to ensure that unit tests do the same filename modification too

Don't assume that the file uploads changes arre correct. This is not an area I know well so there may well be misunderstandings.

/rebase

/rebase

Automatic rebase seems to have failed here for some reason.

/rebase

Automatic rebase seems to have failed here for some reason.

It did. I did it manually, something had got seriously messed up with I think a previous rebase and it had many of the commits duplicated. Now sorted.

/rebase

/rebase

general question:  is there a reason we are keeping the extension on the stored (hash-based) filename?   i would strongly suggest we just drop it entirely.  main two reasons i would give:

it can be (and sometimes most definitely is) wrong - it does not match the actual content of the file
it is quite often inconsistent:  .jpg, .JPG, .jpeg, etc.  (note lowercasing it does not always deal with consistency)

i do however (of course?) think we should leave it as-is as part of the original filename we store in the db.   if a user wants to search on my-image.jpeg, that is what it should find in that field.

general question: is there a reason we are keeping the extension on the stored (hash-based) filename? i would strongly suggest we just drop it entirely. main two reasons i would give:
1. it can be (and sometimes most definitely is) wrong - it does not match the actual content of the file

2. it is _quite often_ inconsistent:  `.jpg`, `.JPG`, `.jpeg`, etc.  (note lowercasing it does not always deal with consistency)

i do however (of course?) think we should leave it as-is as part of the original filename we store in the db. if a user wants to search on my-image.jpeg, that is what it should find in that field.

Generally agree, but is there any actual harm in keeping it as part of the hash? We don't have a way to remedy faulty file extensions anyway.

/rebase

all looks good to me, other than my comment about dropping extensions.
also, i would love to see a test that just goes through an ever-growing list awful_filenames = [.....] and tests a file with each one. but i am totally fine to do this as a separate ticket on my own. it would be very cathartic for me. haha

Yeah and every time we find a new unhandled case we can add it to the sh*t list. Would love to see that.

general question: is there a reason we are keeping the extension on the stored (hash-based) filename? i would strongly suggest we just drop it entirely. main two reasons i would give:
1. it can be (and sometimes most definitely is) wrong - it does not match the actual content of the file

2. it is _quite often_ inconsistent:  `.jpg`, `.JPG`, `.jpeg`, etc.  (note lowercasing it does not always deal with consistency)

i do however (of course?) think we should leave it as-is as part of the original filename we store in the db. if a user wants to search on my-image.jpeg, that is what it should find in that field.

Generally agree, but is there any actual harm in keeping it as part of the hash? We don't have a way to remedy faulty file extensions anyway.

the only real "harm" is it is potentially misleading noise.  if we have no guarantee that a file called XXXXXXXX.jpeg is actually a JPEG image, then why bother?
also, technically we do have a way to remedy the extension -- just not at this point in the pipeline of processing, unfortunately.  (git_store uses magic.from_file() to find the true content-type from the file itself.  just later on...)  this is how i have handled this in the past when we needed extensions -- used file-magic to set the correct thing.  (see: apparent work, sito, etc.)   but it still begs the question: why have it at all.  :grinning:

Lets drop the extensions in this PR, and make the unholy_filename_test in another.

general question: is there a reason we are keeping the extension on the stored (hash-based) filename? i would strongly suggest we just drop it entirely. main two reasons i would give:
1. it can be (and sometimes most definitely is) wrong - it does not match the actual content of the file

2. it is _quite often_ inconsistent:  `.jpg`, `.JPG`, `.jpeg`, etc.  (note lowercasing it does not always deal with consistency)

i do however (of course?) think we should leave it as-is as part of the original filename we store in the db. if a user wants to search on my-image.jpeg, that is what it should find in that field.

Generally agree, but is there any actual harm in keeping it as part of the hash? We don't have a way to remedy faulty file extensions anyway.

The reason for keeping the extension was that the assets class stores it separately and it is used separately.
https://github.com/WildMeOrg/houston/blob/main/app/modules/assets/models.py#L40
https://github.com/WildMeOrg/houston/blob/main/app/modules/assets/models.py#L204-L209
called from :
https://github.com/WildMeOrg/houston/blob/main/app/modules/assets/models.py#L219-L222
so on the principle of not changing more than needed I kept it.
But happpy to take feedback on what should happen with this code if the extension is not stored anymore.

/rebase

/rebasde

/rebase


Workaround for Pi Zero W installation

Hi, I've been manage to install the library on Pi Zero W, but to do so I need to do all pre-requisite (including updating node) on Pi Zero W, THEN do bleno installation on Pi 3, then bring back the sdcard to Pi Zero W.
Anyone experiencing the same, and find a way to do full pi zero W install?

I was able to just run npm i for the rpi0w. What is the error that you're getting which prevents you from doing so?

Sorry could not be more detail, but it just stuck for hours when I do sudo
npm install bleno, with or without -g., it is approximately 2/3 of progress
bar.
The environment is either latest stretch or jessie, both the same, after
doing apt-get update && upgrade, and also install latest node, then
following pre-requisite steps on this github readme.
On Fri, Nov 3, 2017 at 3:25 PM, Pearce Keesling<EMAIL_ADDRESS>wrote:

I was able to just run npm i for the rpi0w. What is the error that you're
getting which prevents you from doing so?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/sandeepmistry/bleno/issues/348#issuecomment-341735904,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AOW6ioPuke91zqUh2S21mhr1ljeQDEWNks5syzBogaJpZM4QK0Ap
.

I do remember that it took a few hours when I installed it, the pi0 isn't a very powerful device. What I ended up doing was cross-compiling when I created my image using yocto. That might not fit your use case though. I'd recommend just leaving it overnight just in case it is an issue of just being super slow.
Maybe try running it with --verbose to see if that gives more information?

Ah yes, will do that and report back, need to build fresh one anyway.
On Fri, Nov 3, 2017 at 4:35 PM, Pearce Keesling<EMAIL_ADDRESS>wrote:

I do remember that it took a few hours when I installed it, the pi0 isn't
a very powerful device. What I ended up doing was cross-compiling when I
created my image using yocto. That might not fit your use case though. I'd
recommend just leaving it overnight just in case it is an issue of just
being super slow.
Maybe try running it with --verbose to see if that gives more information?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/sandeepmistry/bleno/issues/348#issuecomment-341757675,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AOW6itYwUT3d-4beTdii8K3HOc3FoKuLks5sy0C8gaJpZM4QK0Ap
.

Sorry a bit a while on this, it is definitely work on Pi Zero W, but took much longer time, hours, compare to minutes if you do it on Pi 3. Given that A correct Node & NPM already installed on Pi Zero, I guess if someone want to save a bit of time, doing all installation on Pi 3 (if they have one).


Split up _generatescreens method within interpret.dart based on responsibilites

Request Type:  Code Refactor
Description
The method for interpret dart on Parabeac Core is currently very long and functions like a pipe filter, this proposal is to break that into separate methods based on responsibility.
Current Solution
The current structure is just a very long and difficult to read method that handles the entire process of generating screens within the Interpret.dart file
Proposed Solution
Instead of having all of the logic happen within this function in the interpret.dart file, have this function call other functions that handle the specific task being formed at that point. This would clean up the code and make it a lot easier to both read and maintain going forward.
Files Affected:

interpret.dart

Additional Notes:

It's not clear to me what you're proposing to change here.🤔

Hey @Ihuds577, can you assign this to me? Thanks:)

@haardikdharma10 You got it!

This issue was merged with PR: https://github.com/Parabeac/Parabeac-Core/pull/103


Image uploads have the wrong MIME type

When uploading using this lib, images are uploaded with the wrong MIME type. This seems to be causing issues with transformations. For example, images uploaded as PNGs will not be downloaded as WEBP or JPG when using supabase's transformation features.

Hey @funwithtriangles,
Thanks for reporting this - we actually have an options which lets you set the mime-type. I haven't tested in a while but you may wish to give that a try - https://github.com/supabase-community/storage-py/blob/main/storage3/_async/file_api.py#LL225C15-L225C15
I'll take a deeper look when a slot frees up.

Is there an example of how to set the mime-type in upload? Can see that it's a HTTP header but not sure how you want to define that within the file_options parameter.

Never mind - I just can't read. :')
It's just file_options={dict of HTTP headers} -- if anyone is looking for it.

Hi @J0 and @funwithtriangles
Just wondering if either of you managed to get this to work in a Python environment?
We're also experiencing difficulties writing images to bucket - MIME type is automatically text/plain (but downloads as a workable image) - but specifying using the Content-Type header produces correct MIME type but is unopenable upon download. In both instances, preview isn't working - which is the big thing for us (along with transformation options).
Upload is here (in case it's just an incorrect use of the parameter):
       result_1 = supabase.storage.from_([BUCKET]).upload(             "[FILE_NAME].png",             "PNG_transparency_demonstration_1.png",             file_options={"Content-Type":"image/png"})
Demo image is just a .png image that we've gotten elsewhere (just so we know it's not an encoding issue on our end..!) and saved in the local directory.
Both occur when working with images picked up from disk and from memory buffer.
Any advice would be amazing - my suspicion is that some metadata is being dropped upon upload or download.
Lydia

I slept on it, looked at it again this morning, and looked at the definition again - and solved it. It's a silly mistake on my end, but for anyone who is looking for a similar solution:
If you're new to HTTP headers (like me), you'll see them commonly written in camel case. However, for the header to work correctly, please use all lower case. I.e change Content-Type to content-type.
For devs - there's no error catching on the upload end to inform the user, so it errs silently. Just an FYI, if you wanted to add in a little cleaning.

I've opened #100 hopefully that makes it clear for future users.
After that's merged you should be getting intellisense in your IDE too like so:

#100 has been merged and an example for setting the mime type properly in .upload has been added to the README. If anyone has any ideas to improve DX on this further please ping me and comment here 😄


Correction for raw affiliation Ecole Polytechnique de l'Université Francois Rabelais de Tours, France

Correction needed for raw affiliation Ecole Polytechnique de l'Université Francois Rabelais de Tours, France
raw_affiliation_name: Ecole Polytechnique de l'Université Francois Rabelais de Tours, France
new_rors: 02wwzvj46
previous_rors: 02wwzvj46;05hy3tk52
works_examples: W4378677190
contact: ce1aa8a27dc22cb6f78b96632211e661:c85cc7b06b45d79ad6aa98a6e5aae2747c1022429a @ recherche.gouv.fr

This issue was accepted and ingested by the OpenAlex team on 2024-12-21. The new affiliations should be visible within the next 7 days.


Issues with TierZ and LevelZ

I have an issue to where i set the max level for LevelZ to 50 to make it more challenging, and once i put my luch past lvl22 the tierZ mod suddenly stops working, for no reason. Its on the newest Version released today, and i tried the version before that and both didnt work. Has anyone else had this problem?

What do you mean by suddenly stops working? What exactly doesn't work anymore
and please provide the latest.log file


adding job commands page

based on convos with @ernestoongaro, creating pr to capture his content wrt how job commands work.
Closes #2487
What are you changing in this pull request and why?

Checklist

[ ] Review the Content style guide and About versioning so my content adheres to these guidelines.
[ ] Add a checklist item for anything that needs to happen before this PR is merged, such as "needs technical review" or "change base branch."

Adding new pages (delete if not applicable):

[ ] Add page to website/sidebars.js
[ ] Provide a unique filename for the new page

Removing or renaming existing pages (delete if not applicable):

[ ] Remove page from website/sidebars.js
[ ] Add an entry _redirects
[ ] Ran link testing to update the links that point to the deleted page

i wonder if we need to have a 'configure job' page and have this content included in there/

hey @ernestoongaro - i've trimmed this file now and it's ready for you to review. i've also add your bits in as discussed, as well as some introductory content regarding logs, run steps, etc so it's not foreign to users.
let me know if you have any questions at all! deploy preview is [here] - thank you as always!

hey @ernestoongaro - i've trimmed this file now and it's ready for you to review. i've also add your bits in as discussed, as well as some introductory content regarding logs, run steps, etc so it's not foreign to users.
let me know if you have any questions at all! deploy preview is here - thank you as always!

Thanks Mirna! New commit: https://github.com/dbt-labs/docs.getdbt.com/pull/2844/commits/5763733b0cc0567c72bc0e8abf772a936cc3884a

hey @ernestoongaro, made some more final tweaks - can you take a look at the changes and deploy preview for feedback whenever you can?

hey @dave-connors-3 can i please request a technical review of this pr and deploy preview? the page is meant to explain job commands, how they're chained together, and failures. let me know if there's anything you need! thank you @ernestoongaro !

hey @dave-connors-3 and @ernestoongaro ! alrighty - made those changes and have asked dbt help to clarify the generate docs on run checkbox job result. let me know what yall think! will be happy to get this live and thank you both for your awesome help!

hey team! will go ahead and request ta docs review later today if this is looking all good?


git-all,mvn-all: allow spaces as part of arg. lines

@mbiarnes please take a look. This should fix the issue with spaces as part of commit msg (the issue is not related to the Jenkins upgrade).

+1 - tested on Jenkins CI


Wrong TableOperation in ReadAsync method of class TableController

Describe the bug
After reading the source code of the TableController.cs in https://github.com/Azure/azure-mobile-apps/blob/122c585cd7221014b7186b707c15fbe7f66ce28a/sdk/dotnet/src/Microsoft.AspNetCore.Datasync/Tables/TableController.cs, I found a issue in the ReadAsync method. In line 402, we should pass TableOperation.Read instead of TableOperation.Delete to  the AuthorizeRequest method.

Actual placement: https://github.com/Azure/azure-mobile-apps/blob/main/sdk/dotnet/src/Microsoft.AspNetCore.Datasync/Tables/TableController.cs#L432 - completely correct - it's a bug.  Thanks for the report.


hard  level tasks added

Please Provide Documentation to continue the PR
Write a good readme file and make another PR
Currently we are merging your PR.


[Additional Parameter] CU 80 Sales Post OnAfterPostItemJnlLine

Hello,
can we add param WhseJnlPostLine: Codeunit "Whse. Jnl.-Register Line" to this event? CU is needed when running custom posting from Sales Post.
Thanks,
Bartek

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.