text:
Add class gist:SpecEntry

A SpecEntry is a Specification that has a magnitude and an aspect; for example, the specification of a particular furnace has an entry specifying weight (aspect) of 107 lbs (magnitude). This seems to be useful in a number of domains. Proposed definition:
gist:SpecEntry
	a owl:Class ;
	skos:prefLabel "Spec Entry" ;
	skos:definition "A sub-specification consisting of the aspect being measured and a magnitude." ;
	skos:example "The specification of a particular furnace includes, among others, spec entries specifying a weight of 107 lbs and a maximum overcurrent protection of 15 amps. In the first entry, the aspect is weight and the magnitude is 107 lbs. In the second, the aspect is maximum overcurrent protection and the magnitude is 15 amps. (Each magnitude consists of a numeric value and unit of measure.)" ;
	owl:equivalentClass [
		owl:intersectionOf (
			gist:Specification
			[
				a owl:Restriction ;
				owl:onProperty gist:hasMagnitude ;
				owl:someValuesFrom owl:Thing ;
			]
			[
				a owl:Restriction ;
				owl:onProperty
                                       [ owl:inverseOf gist:aspectOf ] ;
				owl:allValuesFrom gist:Aspect ;
			]
			[
				a owl:Restriction ;
				owl:onProperty
                                       [ owl:inverseOf [ gist:aspectOf ] ;
				owl:cardinality "1"^^xsd:nonNegativeInteger ;
			]
			[
				a owl:Restriction ;
				owl:onProperty gist:partOf ;
				owl:onClass gist:Specification ;
				owl:minQualifiedCardinality "1"^^xsd:nonNegativeInteger ;
			]
		) ;
	] ;
	.

Details negotiable. E.g, is it always part of a larger Specification, or could it occur on its own?
Question regarding the first restriction: are two magnitudes expressed in different units of measure and numeric values but which equal the same amount the same thing or two different things? Assuming the latter, I've used a someValuesFrom restriction on hasMagnitude. Assuming the latter we could specify cardinality of 1.
Notice also that aspectOf doesn't specify domain Aspect; thus the allValuesFrom restriction on the inverse of aspectOf.

Related issue: in the case of concrete objects, as opposed to specifications, we suggest, I guess, that different predicates would be used to indicate the aspect being measured: hasWidth, hasHeight, hasCoolingCapacity, etc. It seems to me we should have a single approach to both specifications and real objects, and that the aspect model is preferable because it avoids defining a plethora of predicates in the domain ontology.

I'd love to have a sub-gist for specifications to include something like this. We have modeled this sort of thing for many clients.
However, as described in this wiki article, each situation is different enough so that the model usually needs to be tweaked in some way.  I'd have to give careful thought to what we might be able to use as a stable core model.

This should be discussed in the context of #800. I think it is a good idea, especially now that we are creating the operators ontology. The above definition seems overly complicated. Below is more like what we have used for past clients.
gist:SpecEntry
	a owl:Class ;
	owl:equivalentClass [
		a owl:Class ;
		owl:intersectionOf (
			gist:Specification
			[
				a owl:Restriction ;
				owl:onProperty gist:ofCharacteristic ;
				owl:someValuesFrom gist:Characteristic ;
			]
			[
				a owl:Restriction ;
				owl:onProperty gist:specifiedValue ;
				owl:someValuesFrom [
					a owl:Class ;
					owl:unionOf (
						gist:Category
						gist:Magnitude
					) ;
				] ;
			]
		) ;
	] ;
	skos:definition "Specifies values for a particular characteristic indicating what it means to be in spec for that characteristic. Often this will be what is required, allowed or promised, but it could also be used to specify what is not allowed.  The values will typically be numerical with some unit of measure specified."^^xsd:string ;
	skos:prefLabel "Spec Entry"^^xsd:string ;
	skos:scopeNote "Sets of allowed values may also come from a Nominal or Ordinal scale of measure."^^xsd:string ;
	.

There was not completed. There was no decision or even a discussion about whether/how to have SpecEntry in the context of the new units model.  Once that is settled, we should come back and consider how it would work.

Closing due to implementation of new units and magnitudes model.

Reopening due to the question of how to handle the range of values accommodated in spec entries. It remains to be seen how the new units and magnitudes model will model this.

Given that gist 13 magnitudes include aspect, a class for SpecEntry = ((uom + numericValue) + aspect) doesn't seem necessary.
However, SpecEntries have also been used to model aspect + category, as in color: green.
Should characteristics whose values can be expressed either numerically or categorially be one aspect or two?
Rebecca: Should be one aspect. There are mappings between the two - e.g., European shoe size 40 (a numeric value measured in cm) = US women's shoe size 9 (arguably a category) which can be mapped to, say, medium. It depends on use case. Notably, manufacturers typically need precise numeric values where the customer value is categorial. Amplitude might be measured in decibels while others may only need high, medium, low - it's still the same aspect.
Phil agrees, Michael thinks they are distinct.
Allowing for either magnitude or categorial values with an aspect would complicate queries, though.
Users might implement SHACL constraints to limit the values, just as they might require that length be expressed in inches rather than centimeters.
We ascertained that Aspect and hasAspect are not definitionally limited to scalar values, though some annotation changes should be made, depending on the decision we reach above:

Aspect is defined as "A measurable characteristic such as length, weight, cost, cycle time, or defect rate." If it can include non-scalar aspects we should make this clear at least with examples or a scope note.
hasAspect is defined as "Relates a magnitude to its aspect (measurable characteristic)." If it's meant to apply beyond magnitudes we should loosen up the definition. (Note that there's no domain.)

Do we need a class for Aspect + category (color: green)? What would we call it?

I propose the following model:

SpecEntry is a subclass of Specification that has an aspect and a magnitude, range of magnitudes, or a category for a value. (This is its original definition as implemented at various clients.)
This aligns with my suggestion on issue #1145 that a range should point at two magnitudes rather than literals. We can use the predicates defined in the Operators Ontology, with no need for additional predicates.
By stating the aspect on the SpecEntry, we get the benefit of pattern 1 and satisfy our intuition that each magnitude in a range would have the same aspect.
It is not necessary to assert the aspects on the magnitudes (though by definition of Magnitude we know that they exist). The aspect can be inferred via SPARQL from the SpecEntry onto the Magnitudes.
By stating the aspect on the SpecEntry, we can have a uniform model for categorial and scalar SpecEntrys.

Sample triples:
:_ProductSpecification_1 a gist:ProductSpecification .

:_SpecEntry_1
   a gist:SpecEntry ;
   gist:isDirectPartOf :_ProductSpecification_1 ; # not sure if this is the proposed predicate
   gist:hasAspect gistd:_Aspect_length ;
   ops:hasValueGreaterThan :_Magnitude_1 ;
   ops:hasValueLessOrEqualTo :_Magnitude_2 ;
   .

:_Magnitude_1
    a gist:Magnitude ;
    gist:numericValue 50 ;
    gist:hasUnitOfMeasure gistd:_UnitOfMeasure_inch ;
    # inferred: gist:hasAspect gistd:_Aspect_length ;
   .

:_Magnitude_2
    a gist:Magnitude ;
    gist:numericValue 60 ;
    gist:hasUnitOfMeasure gistd:_UnitOfMeasure_inch ;
    # inferred: gist:hasAspect gistd:_Aspect_length ;
   .

:_SpecEntry_2
    a gist:SpecEntry ;
    gist:isDirectPartOf :_ProductSpecification_1 ; # not sure if this is the proposed predicate
    gist:hasAspect gistd:_Aspect_color ;
    ops:hasValueEqualTo :_Color_red ;
    .

:_Color_red a :Color .

It is open to discussion whether we make modifications to the operators predicates as proposed above.

I like this a lot, well done!  It's very straight-forward with minimal disruption to how we do things now - and it allows for categories.  How cool is that? Very elegant,  (though maybe not quite in the league with e = mc-squared). I was hoping a solution like this would emerge.
I do think that using isPartOf is correct and aligns with what we have been doing all along.

[like]  Michael J. Sullivan reacted to your message:

From: Rebecca Younes @.>
Sent: Friday, August 30, 2024 6:00:53 PM
To: semanticarts/gist @.>
Cc: Subscribed @.***>
Subject: [External] : Re: [semanticarts/gist] Add class gist:SpecEntry (#527)
I propose the following model:

SpecEntry is a subclass of Specification that has an aspect and a magnitude, range of magnitudes, or a category for a value. (This is its original definition as implemented at various clients.)
This aligns with my suggestion on issue #1145https://urldefense.com/v3/__https://github.com/semanticarts/gist/issues/1145*issuecomment-2317389843__;Iw!!ACWV5N9M2RV99hQ!LqfQg4q7sGOQZJ5ggTG6ljlT-Wvl621s_pyCjt7mKIQWfNDkQwhthZBRTlOQDHR9qmj5h4r7lyiNYNhozaq0JzmqkPHJjEI$ that a range should point at two magnitudes rather than literals. We can use the predicates defined in the Operators Ontologyhttps://urldefense.com/v3/__https://github.com/semanticarts/operators-ontology/__;!!ACWV5N9M2RV99hQ!LqfQg4q7sGOQZJ5ggTG6ljlT-Wvl621s_pyCjt7mKIQWfNDkQwhthZBRTlOQDHR9qmj5h4r7lyiNYNhozaq0JzmqHjgspp0$, with no need for additional predicates.
By stating the aspect on the SpecEntry, we get the benefit of pattern 1 and satisfy our intuition that each magnitude in a range would have the same aspect.
It is not necessary to assert the aspects on the magnitudes (though by definition of Magnitude we know that they exist). The aspect can be inferred via SPARQL from the SpecEntry onto the Magnitudes.
By stating the aspect on the SpecEntry, we can have a uniform model for categorial and scalar SpecEntrys.

Sample triples:
:_ProductSpecification_1 a gist:ProductSpecification .
:_SpecEntry_1
a gist:SpecEntry ;
gist:isDirectPartOf :_ProductSpecification_1 ; # not sure if this is the proposed predicate
gist:hasAspect gistd:_Aspect_length ;
ops:hasValueGreaterThan :_Magnitude_1 ;
ops:hasValueLessOrEqualTo :_Magnitude_2 ;
.
:_Magnitude_1
a gist:Magnitude ;
gist:numericValue 50 ;
gist:hasUnitOfMeasure gistd:_UnitOfMeasure_inch ;
# inferred: gist:hasAspect gistd:_Aspect_length ;
.
:_Magnitude_2
a gist:Magnitude ;
gist:numericValue 60 ;
gist:hasUnitOfMeasure gistd:_UnitOfMeasure_inch ;
# inferred: gist:hasAspect gistd:_Aspect_length ;
.
:_SpecEntry_2
a gist:SpecEntry ;
gist:isDirectPartOf :_ProductSpecification_1 ; # not sure if this is the proposed predicate
gist:hasAspect gistd:_Aspect_color ;
ops:hasValueEqualTo :_Color_red ;
.
:_Color_red a :Color .
It is open to discussion whether we make modifications to the operators predicates as proposed above.
—
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https://github.com/semanticarts/gist/issues/527*issuecomment-2322073886__;Iw!!ACWV5N9M2RV99hQ!LqfQg4q7sGOQZJ5ggTG6ljlT-Wvl621s_pyCjt7mKIQWfNDkQwhthZBRTlOQDHR9qmj5h4r7lyiNYNhozaq0JzmqaYlyn6k$, or unsubscribehttps://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AOMYTHYQGU5AFZ6PH6EOES3ZUCXNLAVCNFSM5BURPCGKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMZSGIYDOMZYHA3A__;!!ACWV5N9M2RV99hQ!LqfQg4q7sGOQZJ5ggTG6ljlT-Wvl621s_pyCjt7mKIQWfNDkQwhthZBRTlOQDHR9qmj5h4r7lyiNYNhozaq0Jzmqcf4tCfo$.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

The definition should also cover the case of version IDs, as in the versioning ontology.
That makes 3 use cases:
magnitudes
version IDs
categorical values
Looking at all the use cases, the spec entry seems to be used to specify a set of values, so perhaps we should call it ValueSpec or ValueSpecification.

The versioning ontology doesn't import gist, it defines its own terms, so I'm not convinced that gist must consider the needs of that ontology. It defines its own class VersionRangeSpec, which does not have an aspect. The defining characteristic of what we're calling SpecEntry is that it has an aspect plus a value, either a magnitude or a category, so in any case I don't think it's a SpecEntry.

Looking at all the use cases, the spec entry seems to be used to specify a set of values, so perhaps we should call it ValueSpec or ValueSpecification.

INteresting point, a SpecEntry defines a range of acceptable values, which is a set, strictly speaking. When we first modeled this in 2011, Dave cintroduced the term AllowableRange - however, SpecEntry is not a pure range of values, it is tied to an aspect.  An instance of SpecEntry always refers to a range of values for a particular aspect. A group of spec entries is collectively a specification for something.
If we wanted just the range, SpecEntry would have one, but I am not proposing that.

The defining characteristic of what we're calling SpecEntry is that it has an aspect plus a value,

Not just a value, but a set of acceptable values (which could be just one value).

The versioning ontology doesn't import gist, it defines its own terms, so I'm not convinced that gist must consider the needs of that ontology.

We don't want to be forced to align them, but I am strongly against having different ways to do the same thing, just because we did not give enough thought to it.

I don't see that VersionRangeSpec is sufficiently similar to SpecEntry that they should coincide.

We may also want to add a restriction on SpecEntry that it be part of a Specification, but we should discuss that.

That is too strong, by analogy, engine bolts are created and intended to be part of actual engines. But they might not be so for a while, if ever.  I can create a spec entry saying that width is between 1 and 2 inches intending it to be used for furniture.  In practice it will almost certainly be part of a specification, but not in principle.

I don't see that VersionRangeSpec is sufficiently similar to SpecEntry that they should coincide.

They are very close in meaning.  Each has:

an aspect (e.g. width, version number)
a specification of a set of acceptable values for the aspect using the operators: EQ, GE, GT, LE & LT

Ignoring ontology modularity issues regarding, gist and the operators and versioning ontologies one could define version range spec to be a subclass of spec entry with two additional restrictions.

`hasAspect value :_Aspect_versionNumber
isVersionRangeOf some owl:Thing

In fact, defining version range spec as an explicit subclass would be optional.
I'll work out an example to clarify this.

Ignoring ontology modularity issues regarding, gist and the operators and versioning ontologies one could define version range spec to be a subclass of spec entry with three additional restrictions.

Having taken a closer look at the versioning ontology, which imports the operators ontology, I have a sense of what it would take to explicitly make VersionRangeSpec a subclass of SpecEntry.  I conclude that there is little if any benefit in doing so, given the design goal to keep the versioning and operators ontologies independent from gist.   As it is, to keep that independence, we had to recreate separate versions of  a few classes and properties that were needed.  There is no need for SpecEntry in the versioning ontology, so it's a bit moot to consider creating it just to subclass off it.  I thought of having a skos note about it, but that hardly seems worthwhile.

We deliberately wanted to keep the operators/versioning ontologies independent of gist. I therefore don't see that the subclassing is an option. gist should not inherit a concept as fundamental as SpecEntry from the versioning ontology, and as you say it's not needed there.

We may also want to add a restriction on SpecEntry that it be part of a Specification, but we should discuss that.

That is too strong, by analogy, engine bolts are created and intended to be part of actual engines. But they might not be so for a while, if ever. I can create a spec entry saying that width is between 1 and 2 inches intending it to be used for furniture. In practice it will almost certainly be part of a specification, but not in principle.

To me the term "entry" implies that it is actually entered in (or part of) a specification. (See, for example, 4b--"something entered.") For this reason I'm in favor of the restriction.

@rjyounes -- At one client we've seen a use case for composite aspects. If drawer size is represented as '20in x 10in x 30 in' in the data, it is helpful to be able to model which of those is the height, which is the width, and which the depth.
Should the definition of SpecEntry accommodate this use case?

@rjyounes -- At one client we've seen a use case for composite aspects. If drawer size is represented as '20in x 10in x 30 in' in the data, it is helpful to be able to model which of those is the height, which is the width, and which the depth.
Should the definition of SpecEntry accommodate this use case?

That is very interesting, but seems highly specialized - not the sort of thing that we normally include in gist.

To me the term "entry" implies that it is actually entered in (or part of) a specification. (See, for example, 4b--"something entered.") For this reason I'm in favor of the restriction.

An airplane engine is so called because it is intended to be part of an airplane, just like SpecEntry is intended to be part of a specification.  We don't need to give 'airplane engine' because sometimes is it not part of an actual airplane.

@rjyounes -- At one client we've seen a use case for composite aspects. If drawer size is represented as '20in x 10in x 30 in' in the data, it is helpful to be able to model which of those is the height, which is the width, and which the depth.

No, that got very messy and we ended up not using it anyway.

To me the term "entry" implies that it is actually entered in (or part of) a specification. (See, for example, 4b--"something entered.") For this reason I'm in favor of the restriction.

I think maybe the problem is with the word choice - I.e., can we call it something other than SpecEntry? How about ValueSpecification?

I prefer ValueSpecification but could live withValueSpec. We occasionally use abbreviated forms (the geo terms, not to mention SpecEntry itself), and ValueSpecification is not out of place with terms such as SubCountryGovernment, DegreeOfCommitment, ElectronicAddressType.

I just drafted a PR with a detailed example which is based on @rjyounes 's proposal. It directly imports the operators ontology
https://github.com/semanticarts/gist/pull/1161

Goal: Specify a set of acceptable values for an aspect.
Potential requirements:

Handle categories and magnitudes uniformly.
Handle a range of values, either categories or magnitudes.
Handle single values (a single target)
Handle a set that isn't a range (discrete values).
Ability to set a target value with a range of variation (could be expressed in the max and min, or as a separate percent). gist could provide max and min only, extensions can add a percentage property.

Getting to be long thread, but it's not clear SpecEntry is necessary.
Just relate the specification to an individual magnitude or range of magnitudes.
It looks like it would be helpful to add a class for Range.

Versions may include additional qualifiers like alpha, beta, RC (Release Candidate), or build metadata. Ignoring these can lead to misrepresentation of compatibility and dependencies.

Also, for version range representation, simply using ranges may not suffice. For instance, a software might be compatible with versions 2.0.x but not 2.0.5 due to a known bug. The model should allow for specifying such exceptions within version ranges.

@philblackwood

...it's not clear SpecEntry is necessary. Just relate the specification to an individual magnitude or range of magnitudes. It looks like it would be helpful to add a class for Range.

I agree that since magnitudes include aspect, SpecEntry (or Characteristic) don't add anything, though would still be needed for category values and collections. Were you thinking a Range itself would have an aspect or not? Example:
# Range with aspect
:_Range_gas_mileage_31_39_mpg
    a gist:Range ;
    gist:hasAspect :_Aspect_gas_mileage ;
    gist:hasMinInclusive :_Magnitude_gas_mileage_31_mpg ;
    gist:hasMaxInclusive :_Magnitude_gas_mileage_39_mpg .

:_Magnitude_gas_mileage_31_mpg
    a gist:Magnitude ;
    gist:hasAspect :_Aspect_gas_mileage ;
    gist:hasUnitOfMeasure :_UnitOfMeasure_mpg ;
    gist:numericValue 31 .

:_Magnitude_gas_mileage_39_mpg
    a gist:Magnitude ;
    gist:hasAspect :_Aspect_gas_mileage ;
    gist:hasUnitOfMeasure :_UnitOfMeasure_mpg ;
    gist:numericValue 39.

Or:
# Range without aspect
:_Range_gas_mileage_31_39_mpg
    a gist:Range ;
    gist:hasMinInclusive :_Magnitude_gas_mileage_31_mpg ;
    gist:hasMaxInclusive :_Magnitude_gas_mileage_39_mpg .

In the first case we duplicate the aspect on both the range and the magnitudes, as we talked about with my proposed Characteristic class.

This is very interesting.

Are you proposing that all instances of gist:Category  are to have an aspect, just like all Magnitudes do?
Are you proposing to never have subclasses of gist:Category?

@uscholdm if we want to expand the definition of aspect from "measurable characteristics" to "characteristics" then I think we want to use those aspects instead of creating subclasses of category so that there is a single way to represent them.
e.g. pick one of these styles:
using categories:     ex:_ExteriorColor_red  (requires updating the ontology to include ExteriorColor)
using aspects:         ex:_Category_exterior_color_red with aspect ex:_Aspect_exterior_color
Actually, either style can be used to define specifications, so we can treat the question separately if we agree that we should pick one of these and not use a combination of aspects and subclasses of category.

Comment about how we use specifications ...
Consider the simple case of a specification with two aspects, with a single fixed acceptable value for each one.
rectangle specification:                length 3 inches, width 8 inches.
actual rectangle measurements: length 3 inches, width 8 inches.
In this simple case we define the specification exactly the same way we describe the actual.
Variation: specification says the width may be either 8 inches or 10 inches.  We should cover this case as well, since many specifications come with a choice of values.
The concept of SpecEntry really isn't needed in either case.
See next comment for how this applies to "categorical values".

Specifying things with categorical values using our convention of subclasses of categories.
Case 1: within each category a thing and its specification are single-valued.

Thing 1 conforms to its specification. In general, check to see if there is an exact match between the actual values and the values in the specification.
Variation: choice of colors. First introduce the collection of acceptable colors.

Now see if the value for thing 1 is one of the acceptable colors:

Thing 1 conforms to its specification because its value is one of the acceptable colors in the specification.
To specify that a thing can have multiple colors, either create a category for each color combination (explicit) or create a new property (not as useful because it might require one property for a pair of colors, one for any 3 colors, one for any 4 colors, etc.)
Note that the examples still work if _ExteriorColor is replaced by _Category_exterior_color (1-to-1 correspondence).

Interesting, so it seems you are proposing that it is not necessary to have subclasses of Category,  one could use aspects instead.
Is that correct?

On property naming... Thing 1 may well be a thing with a red exterior color, and thus saying that it gist:isCategorizedBy :_ExteriorColor_red makes sense.
However the specification does not have an exterior color, as it is not a physical object.  In longwinded terms, the specification specifies that the exterior color is red. Not easy to come with a good property name for this that conforms to common sense and is not too long or convoluted.

If we are going to say that a specification hasValue or hasMagnitude, then why not also isCategorizedBy? I think the predicates can be interpreted flexibly enough to make that acceptable.

source: gharchive/issue

authors: MichaelSullivanArchitect NaoualSmaili dylan-sa philblackwood rjyounes uscholdm

repo: semanticarts/gist

license_type: permissive

license_source: github-api


text:
the field 'hosts' is required and cannot have empty values

Issue
Hellow,owner:
my playbook field hosts is an variables with {{ exec_group }}. The file is
- name: "test hosts ping"
  hosts: "{{ exec_group }}"
  roles: ["ping"]

The webui configured the list_enviromnent with emulate values, like this:

then the task is faied with error:

Impact
Ansible (task execution)
Installation method
Docker
Database
BoltDB
Browser
Microsoft Edge
Semaphore Version
v2.10.7
Ansible Version
No response
Logs & errors
No response
Manual installation - system information
No response
Configuration
No response
Additional information
No response

I guess this is because you need to define a default value to your hosts variable using Jinja2 syntax.
Mine is:
hosts: "{{ custom_host | default('invalid') }}"

Then in the webui:

I guess this is because you need to define a default value to your hosts variable using Jinja2 syntax. Mine is:
hosts: "{{ custom_host | default('invalid') }}"

Then in the webui:

still error

authors: ramiuslr seaurching

repo: semaphoreui/semaphore

license: MIT


text:
My container is not forwarding logs

So this how am running the containter
sematext-agent-docker:
image: 'sematext/sematext-agent-docker:latest'
deployment_strategy: every_node
environment:
- LOGSENE_TOKEN=XXXXX
- SPM_TOKEN=xxxxxx
privileged: true
restart: always
tags:
- production
volumes:
- '/var/run/docker.sock:/var/run/docker.sock'
So if I check at the logs am getting this:
Tutum Node Hostname: ccf49792-tumacredo
2015-12-17T08:35:24.820472622Z No pattern file for log parsing found /etc/logagent/patterns.yml -> using default patterns
2015-12-17T08:35:24.822308761Z Use -v /mypattern/patterns.yml:/etc/logagent/patterns.yml for custom log parser definitions.
2015-12-17T08:35:24.933736811Z Listening for "journalctl -o json | ncat localhost PORT" on exposed port 9000
2015-12-17T08:35:24.955305427Z Thu, 17 Dec 2015 08:35:24 GMT uncaughtException: connect ENOENT /var/run/docker.sock
2015-12-17T08:35:24.955449467Z Error: connect ENOENT /var/run/docker.sock
2015-12-17T08:35:24.955462697Z     at Object.exports._errnoException (util.js:874:11)
2015-12-17T08:35:24.955467953Z     at exports._exceptionWithHostPort (util.js:897:20)
2015-12-17T08:35:24.955472717Z     at PipeConnectWrap.afterConnect [as oncomplete] (net.js:1063:14)
2015-12-17T08:35:24.955857719Z Thu, 17 Dec 2015 08:35:24 GMT uncaughtException: connect ENOENT /var/run/docker.sock
2015-12-17T08:35:24.955988595Z Error: connect ENOENT /var/run/docker.sock
2015-12-17T08:35:24.955999644Z     at Object.exports._errnoException (util.js:874:11)
2015-12-17T08:35:24.956004458Z     at exports._exceptionWithHostPort (util.js:897:20)
2015-12-17T08:35:24.956008948Z     at PipeConnectWrap.afterConnect [as oncomplete] (net.js:1063:14)

Hi,
the Agent has no access to the docker unix socket
volumes: '/var/run/docker.sock:/var/run/docker.sock'.

Potential reasons:

different location of the Docker Unix Socket? SSH to the node and check with 'ls -la /var/run/docker.sock'
Configured TLS socket instead? -> the we have to configure TLS access

Please let me know:

Using Tutum Cloud?
Provider, which runs your node (DigitalOcean, Amazon AWS, ...)
Operating system of the Docker Host
Configuration of the docker daemon

Am using tutum cloud.
Provider: CenturyLink
Operating system: Ubuntu 14
I have checked permessions and am getting this:
~# ls -la /var/run/docker.sock
srw-rw---- 1 root docker 0 Dec 16 10:26 /var/run/docker.sock

With help from @megastef  I have  figured out the issue is on tutum side, they don't specify the volume of  the container thats why the container was failing. I have reported the issue to tutum but for now you can work around that by removing the tags and it will work

Thanks - going to close the issue.
I hope Tutum gets the issue solved - maybe it helps to put the "tags" parameter bind the "volumes" parameter in the Stackfile? Pls. let us know the result from Tutum Support.

will let you know

authors: megastef tumacredo

repo: sematext/sematext-agent-docker

license_source: bigquery


text:
I can't login so I can't raise a support ticket to say I can't login

Expected content
Actual content
Link to page:

Hello @bendg25
We're sorry you're having this issue. You can access support contact options by going to https://support.sendgrid.com and clicking "Trouble Logging in?". From there, you can tell us a little more about your problem without having to log in, and one of our fantastic support people will get back to you. Hope this helps!
Twilio SendGrid Docs Team

repo: sendgrid/docs


text:
Update drupal.md

Description of the change: Update Drupal
Reason for the change: Closes #3702
Link to original source:

Closes #3702

Hello @seasonguy,Thanks again for the PR! It's HACKTOBERFEST! We want to show our appreciation by sending                                              you some special Hacktoberfest swag. If you have not already, could you please fill out                                              this form so we can send it to you? Thanks!                                             Team SendGrid DX

Hello @seasonguy,Thanks again for the PR!                                         We noticed that you have earned 1 out of the 5 points needed to receive glorious SendGrid Hacktoberfest swag.                                         Please take a moment to checkout this link to find more issues to get you past the required threshold.                                         Also, please be sure that you have officially registered here.                                         Thank you and Happy Hacktobering!                                         Team SendGrid DX

Hello @seasonguy,Thanks again for the PR!                                         You have earned 1 out of the 5 points needed to receive glorious SendGrid Hacktoberfest swag.                                         Please take a moment to checkout this link to find more issues to get you past the required threshold or to simply continue the celebration.                                         Also, please be sure you have officially registered with us here by November 1, 2018 to qualify.                                         If you have any questions you can email us at dx+hacktoberfest2018@sendgrid.com.                                         Thank you and Happy Hacktobering!                                         Team SendGrid

source: gharchive/pull-request

authors: seasonguy thinkingserious


text:
Update how-to-set-up-reverse-dns.md

Description of the change:  GoDaddy workaround
Reason for the change:  Changes to help GoDaddy customers properly enter the A record to complete rdns
Link to original source:https://sendgrid.com/docs/ui/account-and-settings/how-to-set-up-reverse-dns/

Closes #

Hello @drespinoza,Thanks again for the PR! It's HACKTOBERFEST! We want to show our appreciation by sending                                              you some special Hacktoberfest swag. If you have not already, could you please fill out                                              this form so we can send it to you? Thanks!                                             Team SendGrid DX

authors: drespinoza thinkingserious


text:
Bumped the moment, chai-as-promised, and dirty-chai version in package.json

Fixes
Fixes #662.
Checklist

[X] I have made a material change to the repo (functionality, testing, spelling, grammar) - Done
[X] I have read the [Contribution Guide] and my PR follows them. - Done
[X] I updated my branch with the master branch. - Done
[X] I have added tests that prove my fix is effective or that my feature works - No need for this
[X] I have added necessary documentation about the functionality in the appropriate .md file - No need for this
[X] I have added in line documentation to the code I modified - No need for this

Short description of what this PR does:

This PR updates the version of moment in order to avoid the potential security vulnerability that exists in versions < 2.19.3
While updating this dependency, I also had to update chai-as-promised and dirty-chai

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks @ctrimm! I've added this to our backlog for a code review and merge.
With Best Regards,
Elmer

Sounds good @thinkingserious. Feel free to let me know if you all catch anything I may have missed.

Just following back up on this @thinkingserious since it has been nearly 3 months.

Thanks @ctrimm. This is still on our backlog and I don't have a firm date set for it's merge. I'm sorry I don't have a better answer :(

No worries @thinkingserious - just wanted to make sure it didn't get lost. 😄

Hello @ctrimm,Thanks again for the PR! We appreciate your contribution and look forward to                                              continued collaboration. Thanks!                                             Team SendGrid DX

authors: SendGridDX ctrimm thinkingserious

repo: sendgrid/sendgrid-nodejs

license: mit


text:
i'll try help

Fixes
Checklist

[ ] I have made a material change to the repo (functionality, testing, spelling, grammar)
[ ] I have read the [Contribution Guide] and my PR follows them.
[ ] I updated my branch with the master branch.
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation about the functionality in the appropriate .md file
[ ] I have added in line documentation to the code I modified

Short description of what this PR does:

If you have questions, please send an email to Sendgrid, or file a Github Issue in this repository.

it's spam

repo: sendgrid/sendgrid-php


text:
内联编辑表格Bug

使用表格的时候出现了这个警告，会影响表格的其他功能吗

请自行设置 rowKey 具体可以参见 ant vue 官方文档

请自行设置 rowKey 具体可以参见 ant vue 官方文档

谢谢

authors: Lninn sendya

repo: sendya/ant-design-pro-vue


text:
Published version not usable?

Tagged version 0.2.1 has things like these in its code:
options = seneca.util.deepextend(
    {
      redis: {
        timeout:  so.timeout ? so.timeout-555 :  22222,
        type:     'redis',
        host:     'localhost',
        port:     6379,
      },
    },
    so.transport,
    options)
    }

Which seems to be the result of some well intentioned copy-pasting.
Is this plugin actually in a production-ready state? Should this be replaced by https://github.com/disintegrator/seneca-amqp-transport?

After opening this issue, I stumbled upon this other issue:
https://github.com/senecajs/seneca-rabbitmq-transport/issues/1
I'm still laughing. Not without remorse.

repo: senecajs/seneca-rabbitmq-transport


text:
Modify set_processing_information to check if repository has a description before setting it

The processing_information returned here https://entity.api.sennetconsortium.org/entities/ca3ab3f8399305d42bc214a343285a10/provenance?return_descendants=true contains invalid JSON because the description is set to None. We need to add a check in the set_processing_information method to verify that the repository description returns something and if not set it to an empty string

We will need to address this card first before https://github.com/sennetconsortium/manual-data-ingest/issues/26

repo: sennetconsortium/entity-api


text:
Introduce BaselineOutputFormatter

Hello,
here is a possible solution to create a baseline for Deptrac.
With this simple formatter it's possible to use deptrac in a CI/CD environment without fixing all existing violations

Hi @marcelthole,
thank you for contribution!
What do you think about implementing this as a feature like phpstan and/or psalm does? Having two options --update-baseline=deptrac.baseline.yaml and --set-baseline=deptrac.baseline.yaml or a similar approach.

My first idea was a baseline.yml file. But is there a solution for including yml files in yml files?
I dind't find anything in the symfony documentation about it.
Without an include option, a manually copy into the configuration is required?

There is no such feature in the YAML-Component but of the DependencyInjection-Component. They read values of a key an import the files and use an array_merge for imported values.

Thanks for the input. I looked at the DependencyInjection Component but didn't find a way to solve the current situation because it's not a configuration. I implemented a YmlFileLoader with the function of including one basefile.
I will check the Build and conflicts and update this pr soon.
(Btw. its hard to run the build tools locally because they are not defined in the require dev section :see_no_evil: )

I'm using phive for tools installation. There is a Makefile which includes all necessary commands.

Thank you, @marcelthole !

authors: marcelthole smoench

repo: sensiolabs-de/deptrac


text:
🛑 Sensioty Website is down

In e3ca3f9, Sensioty Website (https://www.sensioty.ch) was down:

HTTP code: 500
Response time: 569 ms

Resolved: Sensioty Website is back up in 9844461.

repo: sensioty/upptime


text:
Bug in free call for Ubuntu 16.04 Xenial

Ubuntu 16.04 has the RedHat style free output now.
It no longer has the buffers/cache section.

Fix released in version 1.0.2.

authors: eheydrick rs-mrichmond


text:
remove use of deprecated method BuildNameToCertificate

I don't believe that this deprecated function is useful to use anymore. Certificate matching on common names fell out of favour ages ago, and it has been many years since global CAs have been issuing proper certs with Subject-Alternate-Names. Also it only allows associating a single certificate with a  name (use case could be having both an RSA and EC certificate for the same name)
// BuildNameToCertificate parses c.Certificates and builds c.NameToCertificate
// from the CommonName and SubjectAlternateName fields of each of the leaf
// certificates.
//
// Deprecated: NameToCertificate only allows associating a single certificate
// with a given name. Leave that field nil to let the library select the first
// compatible chain from Certificates.
func (c *Config) BuildNameToCertificate() {
	c.NameToCertificate = make(map[string]*Certificate)
	for i := range c.Certificates {
		cert := &c.Certificates[i]
		x509Cert, err := cert.leaf()
		if err != nil {
			continue
		}
		// If SANs are *not* present, some clients will consider the certificate
		// valid for the name in the Common Name.
		if x509Cert.Subject.CommonName != "" && len(x509Cert.DNSNames) == 0 {
			c.NameToCertificate[x509Cert.Subject.CommonName] = cert
		}
		for _, san := range x509Cert.DNSNames {
			c.NameToCertificate[san] = cert
		}
	}
}

Thank you, I'll set aside some time to review this! :bow:

Thanks for the contribution! :pray:

authors: echlebek gbolo

repo: sensu/core


text:
Add an aggregates page

Would be nice to have a page to display aggregates

Added by @amdprophet and available in Uchiwa 0.5.1!

repo: sensu/uchiwa


text:
tokio的例子跑不起来，异步使用报错

有以下几个问题：
1、taokio的例子 在运行时会报错，错误内容：
error: future cannot be sent between threads safely
   --> src/main.rs:13:23
    |
13  |         handlers.push(tokio::spawn(async move {
    |                       ^^^^^^^^^^^^ future created by async block is not `Send`
    |
    = help: within `impl Future<Output = [async output]>`, the trait `Send` is not implemented for `Rc<RefCell<SentinelEntry>>`

2、使用异步的时候，会报错，主要代码如下：
pub async fn sentinel_limiting(
    req: Request<Body>,
    next: Next<Body>,) -> Result<impl IntoResponse, (StatusCode, String)> {

    let entry_builder = EntryBuilder::new(String::from(RESOURCE_NAME))
        .with_traffic_type(base::TrafficType::Inbound);

    match entry_builder.build() {
        Ok(entry) => {
            let res = {next.run(req).await};
            entry.exit();
            Ok(res)
        },
        Err(_) => {
            log::info!("被限流了");
            Err((StatusCode::PAYLOAD_TOO_LARGE, String::from("")))},
        }
    }

主要报错如下：
error: future cannot be sent between threads safely
   --> src/main.rs:48:10
    |
48  |         .layer(middleware::from_fn(sentinel_limiting))
    |          ^^^^^ future returned by `sentinel_limiting` is not `Send`
    |
    = help: within `FromFnResponseFuture<impl Future<Output = std::result::Result<Opaque(DefId(0:548 ~ rs_logonline[3f0a]::middlewares::limiting::sentinel_limiting::{opaque#0}::{opaque#0}), []), (StatusCode, std::string::String)>>>`, the trait `Send` is not implemented for `Rc<RefCell<SentinelEntry>>`
note: future is not `Send` as this value is used across an await
   --> src/middlewares/limiting.rs:41:37
    |
40  |         Ok(entry) => {
    |            ----- has type `EntryStrongPtr` which is not `Send`
41  |             let res = {next.run(req).await};
    |                                     ^^^^^^ await occurs here, with `entry` maybe used later
...
44  |         },
    |         - `entry` is later dropped here
note: required by a bound in `Router::<B>::layer`
   --> /Users/weicheng/.cargo/registry/src/github.com-1ecc6299db9ec823/axum-0.5.1/src/routing/mod.rs:298:63
    |
298 |         <L::Service as Service<Request<NewReqBody>>>::Future: Send + 'static,
    |                                                               ^^^^ required by this bound in `Router::<B>::layer`

我已经找到问题了，由于用到了异步，需要在Cargo.toml 中添加 features = ["async"]
原来的 Cargo.toml 中
sentinel-core = { version = "0.1.1", features = ["full"]

调整后的 Cargo.toml :
sentinel-core = { version = "0.1.1", features = ["async"] }

调整后，entry 的类 由 Rc<RefCell> 变为了  Arc<RwLock>，就解决了 Send约束问题。
总之来说：使用异步时候需要在 Cargo.toml 中 指定 features 为 "async"

不好意思前段时间没有关注邮件。您是使用的 0.1.0 吗？
如果要运行示例，可以参考 sentinel-core/Cargo,toml 中各个示例的 feature 要求。或者在根目录下运行 Cargo run --example=tokio 后会有需求特性的提示。
0.1.1 版确实有问题
849e9b75e5cbb5a2df26d4882681485c304ebbf4 中我无意间延长了锁的生命周期

authors: Forsworns FourSpaces

repo: sentinel-group/sentinel-rust


text:
Fixed value fillout bug

This line in ValueFilloutTask contains a typo (the axis is wrong and 1 is added instead of subtracted), which causes problems in fillout in the backward direction. The result of chaining forward and backward fillout may also be corrupted by the latter operation.
The tests are a bit unfortunate in the sense that they all end up testing the function on data of the same particular form, which happens to work - specifically, where only the first element per row needs to be filled out, e.g.:
>>> fill(np.array([[np.nan, 68., 62, 99., 67., 92., 22., 80.]]), operation='b')

array([[68., 68., 62., 99., 67., 92., 22., 80.]])  # Working as expected

However, a simple case such as this would still fail:
>>> fill(np.array([[np.nan, 68., np.nan, 99., 67., 92., 22., 80.]]), operation='b')

array([[68., 68., nan, 99., 67., 92., 22., 80.]])  # The `NaN` in the middle is not filled out

After fixing the typo, the results are as expected. I've also simplified the code a bit and added a few more tests.

Using 'fb' rather than 'bf' or 'b' definitely helped - it filled out NaN values in between and at the end before the backward direction bug ever got to the data.
But looking at the bug, I am still surprised that you had not seen errors before. A simple one would be if the 1st axis (in the 2-dimensional data that is operated on) were longer than the 2nd axis (you could get an IndexError on the last line if idx went out of range for that axis).
Then again, if the shape of the data were just right (every time that fillout was used), it would not be as obvious. Quite unfortunate...

repo: sentinel-hub/eo-learn


text:
Parameter 'all_bands' is set to False

Hello,
When running the following command, I run into an error:
measurements = extract_surface_water_area_per_frame(42, nominal_outline, the_dam_bbox, date, resx, resy)
/usr/local/lib/python3.6/dist-packages/s2cloudless/S2PixelCloudDetector.py in get_cloud_probability_maps(self, X, **kwargs)
    105         if band_num != exp_bands:
    106             raise ValueError("Parameter 'all_bands' is set to {}. Therefore expected band data with {} bands, "
--> 107                              "got {} bands".format(self.all_bands, exp_bands, band_num))
    108
    109         if self.all_bands:

ValueError: Parameter 'all_bands' is set to False. Therefore expected band data with 10 bands, got 9 bands

Any clues? This is most probably related to V3 Transition.
Ali

Hi Ali,
Speaking from the top of my head, but you are probably right. The WCS request used to retrieve also the datamask (using Transparency keyword), which doesn't work work since the transition to V3. WCS request still perceives the last band as data mask, meaning that you end up with 9 (instead of 10) bands.
We will at some point update the code, but I cannot say when. In the mean time, pull requests are encouraged and appreciated.

Hi Ali,
Speaking from the top of my head, but you are probably right. The WCS request used to retrieve also the datamask (using Transparency keyword), which doesn't work work since the transition to V3. WCS request still perceives the last band as data mask, meaning that you end up with 9 (instead of 10) bands.
We will at some point update the code, but I cannot say when. In the mean time, pull requests are encouraged and appreciated.

Hi @batic ,
I fixed the code related to V3 transition and will issue a pull request on this matter.
However, some of the scripts I had to fix are in the s2cloudless library on which BlueDot depends.
How things work in this case? shall I issue 2 different pull requests?
Ali

Hi @batic ,
I fixed the code related to V3 transition and will issue a pull request on this matter.
However, some of the scripts I had to fix are in the s2cloudless library on which BlueDot depends.
How things work in this case? shall I issue 2 different pull requests?
Ali

Hi @aghand0ur,
Yes, please create two pull requests and we will coordinate them.
Best,
Matej

Hi @aghand0ur,
Yes, please create two pull requests and we will coordinate them.
Best,
Matej

@batic
create both pull requests.
looking forward for your review.
Ali

@batic
create both pull requests.
looking forward for your review.
Ali

Hey, this issue still persists. I did update the code with the changes from this PR but the issue still remains. I assume there another PR in s2-cloud-detection needs to be merge. Is is possible to tell the status of these PR's

Hi @saheelBreezo,
yes you need to merge both updates. You can do it manually at your end while waiting for sentinel-hib guys @batic update.
Ali

authors: aghand0ur batic saheelBreezo

repo: sentinel-hub/water-observatory-backend


text:
Adding a timeout that will reset the state back to "OFF" after turning "ON"?

Not really an issue, but:
Interested in seeing how we could reset the state back to "OFF" after a small timeout.
Sequence of events:

I tell Siri to turn on my device
device turns on
... 2 seconds go by...
device turns off

You can use sleep to add a delay and then call your turn off command.
For example, this will output the time to a file and then output the time again after 2 seconds:
date > /home/pi/test.log && sleep 2 && date >> /home/pi/test.log

Thanks, yeah, I'm just having trouble seeing where I would put this in the code so that it would do it automatically. I tried the sleep trick and it threw an error the last time I tried it. I'm sure I'm doing something wrong with the concurrency.

That was a command line example, but was does your code look like and what was the error?

repo: senyoltw/homebridge-cmd


text:
🛑 bk8.sarl is down

In dee8bfb, bk8.sarl (https://bk8.sarl) was down:

HTTP code: 0
Response time: 0 ms

Resolved: bk8.sarl is back up in 11e6697 after 9 minutes.

repo: seomotop/uptime


text:
cria um novo tutorial

dentro do tópico Administração, cria um novo tutorial chamado "Quadro de Atividades".
O link para esse tutorial é https://youtu.be/3E5TvGlPeBQ
O texto desse tutorial é: Através do Quadro de Atividades podemos monitorar pendências dentro do sistema, tanto a nível geral, quanto pessoal. Uma ferramenta muito útil que evita atrasos no preenchimento e análise dos dados do monitoramento de metas dentro do SMAE.

David fez mais um novo tutorial. Ele vai ficar dentro da categoria "Administração"
O título é "Painéis Externos"
O link é
https://youtu.be/4ZV8hgxqrLU
O texto é: "Nos Painéis Externos estão centralizados dashboards úteis à gestão de projetos e acompanhamento do Plano de Metas."


text:
Downclosure with iterated views on Z3

This adds to #64 by putting in downclosure checks for Z3 only.  HSF and µZ3 are still to do.  There are also some changes to the pretty-printer to allow for properly colourised error messages.
Not sure whether it'd be best to merge #64 first, or merge this and close that one.

Is this ready to merge now?

Should be.  :shipit:

authors: CaptainHayashi septract

repo: septract/starling-tool


text:
CLOUD-59030 Move all old flow operation to the new one

@bbihari or @mhmxs pls review

Refer to this link for build results (access rights to CI server needed):
http://ci.sequenceiq.com//job/cloudbreak-pull-request/2682/

Refer to this link for build results (access rights to CI server needed):
http://ci.sequenceiq.com//job/mock-integration-test/173/

repo: sequenceiq/cloudbreak


text:
Implement Eq for Map, Number and Value.

These types already have PartialEq implementations which define equivalence relations, so we can implement Eq as well. Fixes #638.

I failed to test locally with the preserve_order feature enabled. Fixed now.

repo: serde-rs/json


text:
Customizable anchors

How to change anchors on my svg?

I do not understand this issue. If this is still relevant, please open a new issue and provide more details about the problem you have.

authors: IninsayY serebrov

repo: serebrov/emoji-mart-vue


text:
Method name generation fix

Ok, I think issue should be quite easy to fix :)

Codecov Report

Merging #66 into master will not change coverage.
The diff coverage is 100%.

@@            Coverage Diff            @@
##             master      #66   +/-   ##
=========================================
  Coverage     92.38%   92.38%
  Complexity       93       93
=========================================
  Files            23       23
  Lines           289      289
  Branches         48       48
=========================================
  Hits            267      267
  Misses           10       10
  Partials         12       12

Impacted Files
Coverage Δ
Complexity Δ

...ava/com/serjltt/moshi/adapters/FallbackOnNull.java
87.5% <100%> (ø)
1 <0> (ø)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c6c2dc5...bfc401c. Read the comment docs.

I would not introduce a setup only for this case, since I would rather some other tests failing any this kind of issues and If I force it to be Locale.US on setup, I would prevent that happening. So I reversed the locate to default one after verification. Is that good enough? @vanniktech :)

authors: codecov-io yayaa

repo: serj-lotutovici/moshi-lazy-adapters


text:
lzmaffi pip install exception on sls package

Hi - when running sls package I'm getting the following error when requirements.txt contains lzmaffi.
requirements.txt:
cffi==1.12.2
pycparser==2.19
lzmaffi==0.3.0

When I run sls package (or sls deploy), I'm getting the following error:
Serverless: Generated requirements from /Users/ergar/Development/lzmaffi-test/requirements.txt in /Users/ergar/Development/lzmaffi-test/.serverless/requirements.txt...
Serverless: Installing requirements from /Users/ergar/Development/lzmaffi-test/.serverless/requirements/requirements.txt ...
Serverless: Docker Image: lambci/lambda:build-python3.6
Serverless: Running docker run --rm -v /Users/ergar/Development/lzmaffi-test/.serverless/requirements\:/var/task\:z -u 0 lambci/lambda\:build-python3.6 python3.6 -m pip install -t /var/task/ -r /var/task/requirements.txt...

  Error --------------------------------------------------

    Failed building wheel for lzmaffi
  Failed cleaning build dir for lzmaffi
Command "/var/lang/bin/python3.6 -u -c "import setuptools, tokenize;__file__='/tmp/pip-install-n0uwhsga/lzmaffi/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /tmp/pip-record-oabed0ug/install-record.txt --single-version-externally-managed --compile --home=/tmp/pip-target-1tntkuou" failed with error code 1 in /tmp/pip-install-n0uwhsga/lzmaffi/

     For debugging logs, run again after setting the "SLS_DEBUG=*" environment variable.

  Get Support --------------------------------------------
     Docs:          docs.serverless.com
     Bugs:          github.com/serverless/serverless/issues
     Issues:        forum.serverless.com

  Your Environment Information -----------------------------
     OS:                     darwin
     Node Version:           10.14.2
     Serverless Version:     1.39.1

When I run docker run --rm -v /Users/ergar/Development/lzmaffi-test/.serverless/requirements\:/var/task\:z -u 0 lambci/lambda\:build-python3.6 python3.6 -m pip install -t /var/task/ -r /var/task/requirements.txt directly, I get the following cffi error:
$ docker run --rm -v /Users/ergar/Development/lzmaffi-test/.serverless/requirements\:/var/task\:z -u 0 lambci/lambda\:build-python3.6 python3.6 -m pip install -t /var/task/ -r /var/task/requirements.txt
Collecting cffi==1.12.2 (from -r /var/task/requirements.txt (line 1))
  Downloading https://files.pythonhosted.org/packages/20/f7/87b62a8895bf7c93e907b05b97bc4459c81a38a61151f03a6eae13d863aa/cffi-1.12.2-cp36-cp36m-manylinux1_x86_64.whl (428kB)
Collecting lzmaffi==0.3.0 (from -r /var/task/requirements.txt (line 2))
  Downloading https://files.pythonhosted.org/packages/33/ba/8bb07cfa9e6746553765558184583751e3c379939bca360425c903d586a8/lzmaffi-0.3.0.tar.gz
Collecting pycparser==2.19 (from -r /var/task/requirements.txt (line 3))
  Downloading https://files.pythonhosted.org/packages/68/9e/49196946aee219aead1290e00d1e7fdeab8567783e83e1b9ab5585e6206a/pycparser-2.19.tar.gz (158kB)
Building wheels for collected packages: lzmaffi, pycparser
  Building wheel for lzmaffi (setup.py): started
  Building wheel for lzmaffi (setup.py): finished with status 'error'
  Complete output from command /var/lang/bin/python3.6 -u -c "import setuptools, tokenize;__file__='/tmp/pip-install-bhm6em5d/lzmaffi/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" bdist_wheel -d /tmp/pip-wheel-dl5ths8v --python-tag cp36:
  This is lzmaffi version 0.3.0
  Traceback (most recent call last):
    File "<string>", line 1, in <module>
    File "/tmp/pip-install-bhm6em5d/lzmaffi/setup.py", line 30, in <module>
      import lzmaffi._lzmamodule2 as ffimod
    File "/tmp/pip-install-bhm6em5d/lzmaffi/lzmaffi/__init__.py", line 29, in <module>
      from ._lzmamodule2 import *
    File "/tmp/pip-install-bhm6em5d/lzmaffi/lzmaffi/_lzmamodule2.py", line 2, in <module>
      from cffi import FFI
  ModuleNotFoundError: No module named 'cffi'

My Serverless.yml:
service: lzmaffi-test

provider:
  name: aws
  runtime: python3.6

custom:
  pythonRequirements:
    dockerizePip: non-linux

functions:
  hello:
    handler: handler.hello

plugins:
  - serverless-python-requirements

Hey 👋 I'm closing this ticket as it looks like it's heavily outdated, we can of course reopen it if needed 👍

authors: egarrett pgrzesik


text:
Issues with File Upload and Retrieval using GCP

Describe the bug
I am encountering several issues when using file upload and retrieval through Google Cloud Platform (GCP). After reading the existing issues and setting up my bucket and configuration files, I am facing the following errors:

Issue with direct ByteData upload: When I try to upload a ByteData object to a custom endpoint, I get the following error:
Connection closed before full header was received, uri = http://localhost:8080/[endpointName]
The test was performed with a png of 1.6MBytes.

Issue with file permissions after upload: When using the FileUpload component on the client side, the file uploads successfully but is made public, even though I have configured the bucket for private files (public: false).

Issue with server-side file retrieval: When I try to retrieve a file server-side, it only works if the file is at the root of the bucket. For example:

succursale/logo.png does not work.
logo.png works.

This happens with the retrieveFile and getPublicURL methods.
To Reproduce
Steps to reproduce the behavior:

Configure a GCP bucket with private permissions (public: false).
Try uploading a ByteData object to an endpoint.
Use the FileUpload component to upload a file.
Attempt to retrieve a file in a subdirectory of the bucket.

Expected behavior

Upload ByteData without errors: Uploading a ByteData object to a custom endpoint should proceed without any errors, and the connection should not be interrupted.

2.. Respect file privacy settings during upload: When I upload a file using the FileUpload method, the file should be stored as private in GCP, as configured (public: false).

File retrieval, including those in subdirectories: Files should be retrievable using the retrieveFile and getPublicURL methods, whether they are at the root of the bucket or in a subpath.

Serverpod versions

CLI Version:  2.1.1
Library version: 2.1.1

Platform information
Db and redis on Docker. Server and client on localhost using vscode debugger
Additional context

client code
  Future _updateLogoDirect(BuildContext context, String id) async {
    var succId = int.tryParse(id);
    if (succId == null) {
      return;
    }
    // ask user to upload image
    FilePickerResult? result = await FilePicker.platform.pickFiles(
      allowMultiple: false,
      type: FileType.image,
    );
    if (result == null) {
      return;
    }
    var file = result.files.single;
    var bytes = await file.xFile.readAsBytes();
    if (bytes == null) {
      return;
    }
    var byteData = bytes.buffer.asByteData();

    await client.succursale.setLogo(succId, byteData);

  }
  Future _updateLogoFileUploader(BuildContext context, String id) async {
    var succId = int.tryParse(id);
    if (succId == null) {
      return;
    }
    // ask user to upload image
    FilePickerResult? result = await FilePicker.platform.pickFiles(
      allowMultiple: false,
      type: FileType.image,
    );
    if (result == null) {
      return;
    }
    var file = result.files.single;
    var bytes = await file.xFile.readAsBytes();
    if (bytes == null) {
      return;
    }
    var logoStoragePath = await client.succursale.getLogoStoragePath(succId);
    if (logoStoragePath == null) {
      return;
    }
     FileUploader uploader = FileUploader(logoStoragePath);
    var byteData = bytes.buffer.asByteData();
    uploader.uploadByteData(byteData);
  }

server code
  Future<ByteData?> getLogo(Session session, int id) async {
    var succursale = await Succursale.db.findById(session, id);
    var logoPath = succursale?.logoPath;
    logoPath = _getLogoPath(succursale!);
    if (logoPath == null) {
      return null;
    }
    var logo = await session.storage
        .retrieveFile(path: logoPath, storageId: 'private');
    var publicUrl = await session.storage
        .getPublicUrl(storageId: 'private', path: logoPath);
    var object =
        session.storage.retrieveFile(storageId: 'private', path: logoPath);
    return logo;
  }

  // set logo
  Future<Succursale?> setLogo(Session session, int id, ByteData logo) async {
    var succursale = await Succursale.db.findById(session, id);
    if (succursale == null) {
      throw Exception('Succursale not found');
    }
    var logoPath = _getLogoPath(succursale);
    await session.storage
        .storeFile(storageId: "private", path: logoPath, byteData: logo);
    succursale.logoPath = logoPath;
    return await Succursale.db.updateRow(session, succursale);
  }

  //getLogoPath
  Future<String?> getLogoStoragePath(Session session, int id) async {
    var succursale = await Succursale.db.findById(session, id);
    if (succursale == null) {
      return null;
    }
    var logoPath = _getLogoPath(succursale);
    var storagePath = await session.storage.createDirectFileUploadDescription(
        storageId: 'private', path: logoPath);
    return storagePath;
  }

  String _getLogoPath(Succursale succursale) {
    return '/toto/logo_1_asdf.png';
  }

Thanks for your reply. PR looks promising
What about uploading ByteData files from the client to the server. Is this the right approach, or is it not planned to be able to transit files in this way?

This is possible today already. You can use the file upload API, there is only one serverside integration for this and it writes the file to the db.
If you want to manage this in memory you can set the maxRequestSize in the config to increase the byte limit in the endpoints. See: https://docs.serverpod.dev/concepts/configuration#configuration-options

Thank you for opening this issue. I have been also facing this using GCP Storage.

I get the file description and the file get uploaded.
But it returns success: false.

The verify File exists and getPublicUrl is not working correctly.

The privacy concerns that every person shall only see their own files is very important.

Happy seeing there will be progress. When we can get the new implementation because it's required for our app. Thank you.

authors: Isakdl alexdess iampopal

repo: serverpod/serverpod


text:
Update static_directory.dart

Added support to two more content types : jpeg and pdf
Replace this paragraph with a description of what this PR is changing or adding, and why.
List which issues are fixed by this PR. You must list at least one issue.
Pre-launch Checklist

[x] I read the Contribute page and followed the process outlined there for submitting PRs.
[x] This update contains only one single feature or bug fix and nothing else. (If you are submitting multiple fixes, please make multiple PRs.)
[x] I read and followed the Dart Style Guide and formatted the code with dart format.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///), and made sure that the documentation follows the same style as other Serverpod documentation. I checked spelling and grammar.
[x] I added new tests to check the change I am making.
[x] All existing and new tests are passing.
[x] Any breaking changes are documented below.

If you need help, consider asking for advice on the discussion board.
Breaking changes
If you have done any breaking changes, make sure to outline them here, so that they can be included in the notes for the next release.

I have read the CLA Document and I hereby sign the CLA


text:
Where to find grammar for different languages ?

Where can I find grammar for different languages(lets say golang) in the JSON format like you have in the grammar directory

I've used ChatGPT to generate me a JSON file for Python and it worked pretty well. Here's the result, if you're interested.
{
  "name": "Python",
  "version": "1.0.0",
  "fileTypes": ["py"],
  "scopeName": "source.python",
  "foldingStartMarker": "\\b(?:def|class)\\s*[^:]*:\\s*$",
  "foldingStopMarker": "^\\s*\\}",
  "patterns": [
    { "include": "#comments" },
    { "include": "#keywords" },
    { "include": "#constants-and-special-vars" },
    { "include": "#operators" },
    { "include": "#strings" }
  ],
  "repository": {
    "comments": {
      "patterns": [
        { "name": "comment.line.hash.python", "match": "#.*$" },
        { "name": "comment.block.python", "begin": "'''", "end": "'''" },
        { "name": "comment.block.python", "begin": "\"\"\"", "end": "\"\"\"" }
      ]
    },
    "keywords": {
      "patterns": [
        { "name": "keyword.control.python", "match": "\\b(?:if|else|while|for|in|break|continue|return)\\b" },
        { "name": "keyword.operator.logical.python", "match": "\\b(?:and|or|not)\\b" },
        { "name": "keyword.operator.assignment.python", "match": "=" },
        { "name": "storage.modifier.python", "match": "\\b(?:def|class)\\b" }
      ]
    },
    "constants-and-special-vars": {
      "patterns": [
        { "name": "constant.language.python", "match": "\\b(?:True|False|None)\\b" },
        { "name": "variable.language.python", "match": "\\b(?:self)\\b" },
        { "name": "constant.numeric.python", "match": "\\b(?:\\d+\\.?\\d*|\\.\\d+)\\b" }
      ]
    },
    "operators": {
      "patterns": [
        { "name": "keyword.operator.arithmetic.python", "match": "\\b(?:\\+|-|\\*|/|%|//)\\b" },
        { "name": "keyword.operator.comparison.python", "match": "\\b(?:==|!=|<|<=|>|>=)\\b" },
        { "name": "keyword.operator.logical.python", "match": "\\b(?:and|or|not)\\b" }
      ]
    },
    "strings": {
      "patterns": [
        { "name": "string.quoted.triple.double.python", "begin": "\"\"\"", "end": "\"\"\"" },
        { "name": "string.quoted.triple.single.python", "begin": "'''", "end": "'''" },
        { "name": "string.quoted.double.python", "begin": "\"", "end": "\"" },
        { "name": "string.quoted.single.python", "begin": "'", "end": "'" }
      ]
    }
  }
}

I've loaded it using Highlighter.initialize(['../../../assets/languages/python']);. To use it :
Highlighter highlighter = Highlighter(
  language: '../../../assets/languages/python',
  theme: highlighterTheme,
);
Text.rich(highlighter.highlight(pythonCode));

authors: Mayhul-Jindal Skyost


text:
🛑 sgm1ray.serverssh.net is down

In e9f7926, sgm1ray.serverssh.net (http://sgm1ray.serverssh.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: sgm1ray.serverssh.net is back up in fedf28b.

repo: serversshnet/server-status


text:
🛑 id2vless.ipservers.xyz is down

In 4ef9186, id2vless.ipservers.xyz (id2vless.ipservers.xyz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: id2vless.ipservers.xyz is back up in b252306.

repo: serversshnet/uptime


text:
🛑 idtro.ipservers.xyz is down

In a192682, idtro.ipservers.xyz (idtro.ipservers.xyz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: idtro.ipservers.xyz is back up in c3330c8.


text:
🛑 sgcgo.ipservers.xyz is down

In 4a46451, sgcgo.ipservers.xyz (sgcgo.ipservers.xyz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: sgcgo.ipservers.xyz is back up in 8111a8a after 12 hours, 40 minutes.


text:
🛑 idtro.ipservers.xyz is down

In 8c32007, idtro.ipservers.xyz (idtro.ipservers.xyz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: idtro.ipservers.xyz is back up in bd1fc2d after 1 hour, 15 minutes.


text:
🛑 id2go.ipservers.xyz is down

In 386916a, id2go.ipservers.xyz (id2go.ipservers.xyz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: id2go.ipservers.xyz is back up in 289aeb9 after 53 minutes.


text:
Do not generate names for typedefed anonymous structs and enums

A common pattern in a lot of C code is to do
typedef struct /* no name here */ {
    // ...
} my_struct;

bindgen 0.20 translates this using a made-up type name and a re-export. This makes the rustdoc documentation look awful (and potentially error messages as well). These bogus type names were not introduced in bindgen 0.19. I think there is no reason not to detect this common pattern and avoid them.

The thing is that detecting this common pattern is not that easy in the case of C++. Old bindgen did this looking at the AST of libclang, and got it wrong a lot of times, over all in presence of anonymous structs in classes (which I believe are also legal in C11).
I'm not really fond in supporting this. What we could do, is using a type alias instead of a re-export. The re-exports are done for convenience when using enums (#396), but we can definitely make it configurable.

BTW, thanks for filling all these issues, they're really helpful.

I don't think type aliases would fix the documentation or the error messages.
pub struct bindgen_ty {
    pub a_field: u32
}
pub type Typed = bindgen_ty;
pub use bindgen_ty as Used;

fn main() {
    let t: Typed = Typed{a_field:2};
    t.not_a_field;
    let u: Used = Used{a_field:2};
    u.not_a_field;
}

error: no field `not_a_field` on type `bindgen_ty`
 --> <anon>:9:7
error: no field `not_a_field` on type `bindgen_ty`
  --> <anon>:11:7

Besides, type aliases are not the same as re-exports. Crucially, tuple-struct constructors are not available through a type alias.

What's hard about this? Is such a definition split into two AST nodes with an anonymous struct definition and a related typedef?

BTW, thanks for filling all these issues, they're really helpful.

Thanks for being so receptive of my issues! Otherwise I'm pretty happy with the new features such as string macros, 128-bit integer support, probably more...

What's hard about this? Is such a definition split into two AST nodes with an anonymous struct definition and a related typedef?

Yes, I remember it being specially tricky to handle correctly under some circumstances in C++, that's why I used this approach.

TL;DR: This is how the simplest case looks like:
(kind: StructDecl, spelling: , type: Record
)
(kind: TypedefDecl, spelling: Foo, type: Typedef
	(kind: StructDecl, spelling: , type: Record
	)
)

That is, first we find the anonymous struct, then we find a typedef declaration that happens to contain a node pointing to that same struct. I guess I could try to handle it somewhat correctly given the definition of the anonymous struct (I expect) points to the inner item, but it's tricky.

I hadn't look into this for a while, actually doesn't look that terrible if what I say above is true, we could try to special-case this. But need to see how more complex cases are handled.

This is a huge problem for me. In C the typedef struct pattern is very very common. There are C libraries which don't even use named structs, and rely on the typedef pattern exclusively. This means that all generated code is hard to understand gibberish of _bindgen_ty_35.

I've tried to implement this, but there are too many things called Item and Kind for me to follow :)
Given this header:
typedef struct {
} TYPEDEFED_NAME;

In bindgen items there is an item Item { id: ItemId(3) … kind: Type(Type { name: Some("struct TYPEDEFED_NAME"), but I don't know how to get to that field when generating canonical_name.

So the way to implement this is not in the code generation phase, but on the type parsing phase. Concretely, in the CXType_Record branch in src/ir/ty.rs, you'd do something  check whether the current cursor spelling is empty.
If so, you'd have to walk to its next sibling (this would be hacky, but you'd have to re-visit the cursors I think), and see if the exact next cursor is a CXCursor_Typedef with a CXCursor_RecordDecl pointing to the same type. If so, you can just use the CXCursor_Typedef name instead of the record name (which is empty).
An alternative approach, which may work better, is looking at the type definition, and see if it's inside a typedef. And if so, do the same.

That is to say, you don't want to look at the Items, you need to do this work while constructing this work looking at the clang AST. you can look at the clang ast with bindgen --emit-clang-ast foo.h.

In from_clang_ty, CXType_Record's spelling is the name of the typedef. It looks like CompInfo::from_ty isn't even trying to save it.

authors: emilio jethrogb pornel

repo: servo/rust-bindgen


text:
Update docs for Vagrant 2.0.0 compat

This change is

Follow-up to #729. r? @larsbergstrom

@bors-servo: r+

:pushpin: Commit 115257a has been approved by jdm

:hourglass: Testing commit 115257a3ecb4a47119113492d4c01393f10026c7 with merge 9aa4a5eb36059fd750965a24f4a48bfe27929391...

:sunny: Test successful - status-travis
Approved by: jdm
Pushing 9aa4a5eb36059fd750965a24f4a48bfe27929391 to master...

authors: aneeshusa bors-servo jdm

repo: servo/saltfs


text:
Better site styling

I'd love for the site to be a little less white and a little more modern suggestions (and pulls) very welcome along this line

I'm going to be happy with the big change to use bootstrap
https://github.com/sethtroisi/cloudygo/commit/ffdc7cff24f49570d5d9c0ac6b7fdf3fcc687091
https://github.com/sethtroisi/cloudygo/commit/cd3b77280b8f7e873b63c6876c54865d25be7c95

repo: sethtroisi/cloudygo


text:
Add support for ppc64le platform

Add support for ppc64le platform. (required for RHEL7 powerpc little endian chef-client builds)

@mattray ^^

Thanks!

Thanks @sethvargo for merging this! Are you planning to release a newer version sooner to rubygems, it will help omnibus builds of chef-client on rhel7 powerpc little endian platform.

@kaustubh-d no release is planned at this time, sorry.

authors: kaustubh-d sethvargo

repo: sethvargo/chef-sugar


text:
Stahování model.tflite je hrozně pomalé a selže před koncem

Mám problém se stažením model.tflite, nejde stáhnout ani pomocí tvého kódu, ani normálně z prohlížeče (download se pořád zpomaluje a časem selže, přestože máme na kolejích rychlost ~100Mbit/s), nakonec se mi to povedlo wgetem. Pokud je to u ostatních podobné, bylo by asi fajn si ho někam nahrát a stahovat odjinud.
Díky
Tom

Nemám ten problém. Pokud přetrvává, zkus do root adresáře projektu stáhnout model manuálně, url https://github.com/JanPalasek/ulozto-captcha-breaker/releases/download/v2.2/model.tflite

Tohle je notorický problém GitHub releases, který se vyskytuje u některých českých ISP. Netuším co to způsobuje. Týká se to jen a pouze GitHub releases, ani ne celého GitHubu, a děje se to jen občas.

Máš pravdu, dneska už to funguje :D Uzavírám.

authors: JanPokorny Koticka domestomas

repo: setnicka/ulozto-downloader


text:
Angular routing

Integrate Angular routing, moving http requests to factory, and visual fixes.

🥇


text:
Fix some QoL issues introduced by #19

Changes in #19 introduced a few new edge cases that need to be accounted for:

[ ] Right now, mouse controls for graph panning (middle mouse drag) are handled everywhere. We should restrict that to be inside the graph's Ui.
[ ] The 'new node' dropdown is not clipped to the graph's ui contents.
[ ] The 'new node' dropdown sometimes draws before the window containing the graph, making it invisible.

None of this affects the original mode of operation, where the graph was being drawn as a full-screen CentralPanel.

The 'new node' dropdown is not clipped to the graph's ui contents.

I'm not sure if this might violate assumptions in egui, but I prefer the menu not clipping to the ui. From a consistency standpoint that's how menus usually work (see blender, for instance). From a user standpoint, if they're seeing that menu it's almost always because they are currently using it, so giving it screen real-estate is worthwhile and won't cover something else that they're trying to interact with.

Pull request #40 has imlpemented is going to fix these issues.


text:
🛑 www.seungjin.net is down

In 75e82b3, www.seungjin.net (https://www.seungjin.net) was down:

HTTP code: 424
Response time: 10609 ms

Resolved: www.seungjin.net is back up in 227b6b1.

repo: seungjin/uptime


text:
An error occured during getting state!

I found in the Homebridge Log this messages:

[11/10/2021, 20:25:31] [FritzPlatform] Fritzbox7590 Led (led): An error occured during getting state!
[11/10/2021, 20:25:31] [FritzPlatform] Error: Unauthorized
at Object.exports.request (/usr/local/lib/node_modules/homebridge-fritz-platform/node_modules/@seydx/fritzbox/lib/request.js:78:21)
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:95:5)
at exports.requestXml (/usr/local/lib/node_modules/homebridge-fritz-platform/node_modules/@seydx/fritzbox/lib/request.js:230:20)
at Service.execAction (/usr/local/lib/node_modules/homebridge-fritz-platform/node_modules/@seydx/fritzbox/lib/service.js:133:20)
at Handler.get (/usr/local/lib/node_modules/homebridge-fritz-platform/src/accessories/router/router.handler.js:350:28)
at Handler.poll (/usr/local/lib/node_modules/homebridge-fritz-platform/src/accessories/extras/extras.handler.js:783:13) {
title: 'Invalid Response',
code: 401,
soap: {},
url: 'https://Homebridge:xxxxxx@192.168.2.2:49443/upnp/control/deviceconfig'
}

The strange thing everything seems to work no problems for me.
Homebridge v1.3.5 Plugin version 6.0.19

[11/10/2021, 20:25:31] [FritzPlatform] Error: Unauthorized

The plugin can no longer log in to the FritzBox. Have you tried to restart the FritzBox?

Doesn’t help. I can change the state from Home app (eg. Voice mail on/off). But sometimes it just works after some tries. With homebridge version 1.3.4 it works.

I also tested another user (the main user) and recreated the user for homebridge. On the WebUI I can successfully login with both users. But in homebridge the error is shown.

Some new ideas???
Everything is up to date but still a lot of debug messages.
But the funktion is ok.

same issue for me on a fresh install.
doesn't matter if I backup/restore from another homebridge, add the plugin and settings manually or creating a new user, still the same.
On my main homebridge, running for years it is still working, even after a reboot, so only new installations are affected.

Disable "SSL" in the homebridge-fritz-platform config solved it for me. @seydx But why?
See https://github.com/seydx/homebridge-fritz-platform/issues/254

authors: CM-UH Kienz SeydX misanthrophy

repo: seydx/homebridge-fritz-platform


text:
Implement share functionality

Context
The current share menu lacks functionality for users to share content directly via Email, Facebook, X (formerly Twitter), or by copying a link. Adding this functionality will improve user experience and encourage content sharing.
Definition of Done

Share menu is updated to include the following working options: Email, Facebook, X (formerly Twitter), Copy link;
Clicking on each menu item triggers the respective share functionality:

Email: Opens the default email client with a prefilled subject and body containing a link.
Facebook: Opens Facebook's share dialog for sharing the content link.
X: Opens X's sharing interface with a prefilled tweet containing the content link.
Copy link: Copies the content link to the user's clipboard, with a visual confirmation (e.g., toast notification).

Testing is conducted to ensure each share option works correctly

Engineering Details

Update the existing Share component to add the functionality.
Implement sharing functionality using:

mailto: links for Email sharing.
Facebook’s Share Dialog URL: https://www.facebook.com/sharer/sharer.php?u=<URL>.
X’s Tweet Composer URL: https://twitter.com/intent/tweet?url=<URL>.
Clipboard API for copying the link (navigator.clipboard.writeText).

Use Jest and React Testing Library to test the share functionality:

Verify mailto:, Facebook, and X links render with correct href attributes.
Mock the Clipboard API to test that the "Copy link" feature copies the correct URL and shows a confirmation message.

Limitations: Testing frameworks cannot verify the execution of external sharing. Focus tests on DOM interaction and correct link generation.

test

What I have right now:

Is this what we are going for or do we want to be able to share a specific report that we click on?

url changes to this when searching but the page data does not change

Was able to get the url to work for Twitter, email, and copying it -> facebook seems to have an issue with the share so I'll be doing some additional tests

[ ] check if it works with https url
[ ] check if it works with localhost
[ ] document findings

repo: sfbrigade/datasci-earthquake


text:
Examine QuISP OMNeT++ coding choices

I think a lot of the things that are currently module parameters should instead be C++ class/module "data members".
Compare:
https://doc.omnetpp.org/omnetpp/manual/#sec:simple-modules:setting-parameters
https://doc.omnetpp.org/omnetpp/manual/#sec:simple-modules:handlemessage
go to 4.4.1.6
shows how to add “data members” to a cSimpleModule
Those are essentially “local variables” for the module.
Rather than so many calls to get and set parameters using the par() call, probably a lot of the active state of e.g. qubits should be data members like that, declared in protected: sections of the module

Basically, everything that gets reset in
void stationaryQubit::setFree(bool consumed){
should be a data member, rather than a parameter:
par("photon_emitted_at") = emitted_time.dbl();
par("last_updated_at") = updated_time.dbl();
par("GOD_Xerror") = false;
par("GOD_Zerror") = false;
par("GOD_CMerror") = false;
par("GOD_EXerror") = false;
par("GOD_REerror") = false;
par("GOD_CMerror") = false;
par("isBusy") = false;
par("GOD_entangled_stationaryQubit_address") = -1;
par("GOD_entangled_node_address") = -1;
par("GOD_entangled_qnic_address") = -1;
par("GOD_entangled_qnic_type") = -1;

repo: sfc-aqua/quisp


text:
Why there are ellipsis on long messages?

I am new to this project and I have started to use it because a native tcl thing got broken and I am lazy to fix it, already notified the project...
Now... Since I started to poke around with the twitter gem for twitter, long messages get an ... before the link (if any).
Example:
[17:31:05]  @NeowinFeed: In this episode of Microsoft trying to force people to use Edge, the company, since the latest Patch Tuesday, has n… https://t.co/qUetXIfjrO
How do I get the full message and not a partially covered message??

It doesn't matter. I stopped using "X"/Twitter api and web... and maybe soon I will delete my account if they don't add more capabilities to the free tier.

repo: sferik/twitter


text:
Fix PImpl: destructor needs to be out-of-line.

Also makes explicit that copy/move are implicitly disabled.

Thanks for the contribution!

authors: joker-eph sftrabbit

repo: sftrabbit/CppSamples-Samples


text:
🛑 Nodo is down

In 9588a4d, Nodo (https://nodotecnologico.catamarcacapital.edu.ar/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Nodo is back up in 3fa6635.

repo: sfvc/upptime


text:
🛑 Civitas RRHH is down

In e87265c, Civitas RRHH (http://civitas.catamarcaciudad.gob.ar:8080/GRH_CATA/forms/login.jsp) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Civitas RRHH is back up in ddfa703.


text:
🛑 Rentas is down

In a942fe9, Rentas (rentas.catamarcaciudad.gob.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Rentas is back up in 001b1bf.


text:
Disappeared large number CC

I encountered a weird issue.
I'm using large CC numbers for an instrument.
Two CCs are missing : Pan Tom1 (CC 453) and Tune Tom2 (CC 474), in red circle :

But if I change them to small numbers, they appeared :

And if I only load only the Tom1 or Tom2 sfz file, the large CCs also appeared.

This is unexpected. Can you share the files?

Here's the files :
test-master.zip
The files came from our private repo. It's a prototype Drumkit sample library project, so it contains a lot of sfz presets.
But basically you just load the "NewDrums.sfz" in the 3rd folder, the Stereo-Kit version to check.

authors: kinwie paulfd

repo: sfztools/sfizz


text:
[Bug] DeepSeekV3 instructions don't work for multi-node H100 setup

Checklist

[X] 1. I have searched related issues but cannot get the expected help.
[X] 2. The bug has not been fixed in the latest version.
[x] 3. Please note that if the bug-related issue you submitted lacks corresponding environment info and a minimal reproducible demo, it will be challenging for us to reproduce and resolve the issue, reducing the likelihood of receiving feedback.
[x] 4. If the issue you raised is not a bug but a question, please raise a discussion at https://github.com/sgl-project/sglang/discussions/new/choose Otherwise, it will be closed.
[x] 5. Please use English, otherwise it will be closed.

Describe the bug
All the steps and issues reported in issue #2658 apply here.
I am using the Docker setup described in the instructions on this page. I believe H100 are the most widely deployed across most cloud service providers right now (FWIW, I am using AWS SageMaker P5 instances but it should not matter here).
https://github.com/sgl-project/sglang/tree/main/benchmark/deepseek_v3#example-serving-with-2-h208
Can somebody please help?
Thanks
Reproduction
Follow instructions on https://github.com/sgl-project/sglang/tree/main/benchmark/deepseek_v3#example-serving-with-2-h208
Environment
Slurm env running multiple H100 nodes to serve DeepSeekv3.
Same result with 2 and 4 nodes (16 and 32 H100 GPUs)

Please paste your instructions here

# node 1
python -m sglang.launch_server --model-path deepseek-ai/DeepSeek-V3 --tp 16 --nccl-init 10.0.0.1:5000 --nnodes 2 --node-rank 0 --trust-remote-code

# node 2
python -m sglang.launch_server --model-path deepseek-ai/DeepSeek-V3 --tp 16 --nccl-init 10.0.0.1:5000 --nnodes 2 --node-rank 1 --trust-remote-code

The startup commands for both nodes need to use the IP of node 1. This command has been verified on multi-node setups on h20 and h800 without any issues.

authors: mycpuorg zhyncs

repo: sgl-project/sglang


text:
Add new channels, groups, radio

Update playlist for new channels, groups, radio.

Fixed in a30955593fd54494736d5328518f49f9b3a7777f

repo: sgloutnikov/NeterraProxy


text:
Ajout d'une recherche directement dans la fiche catalogue

Fix #88

Il faudrait trouver un moyen de d'utiliser <WrappedDatasets /> afin de profiter de _extractFilters().

@jdesboeufs @Flightan

Ne convient pas...

repo: sgmap/inspire-next


text:
[WIP] Add support for chrono types

As discussed in issue #92, I started writing impls for diesel to handle chrono’s DateTime type. This is strongly inspired by the implementation of same feature in the postgres crate.
Only DateTime is handled at the moment. Tests are far from complete.
I wonder if it would not be possible to implement FromSql and ToSql for DateTime<T: TimeZone> and avoid having to provide implementations for UTC, FixedOffset and Local. The whole timezones business is a bit fuzzy in my head as soon as it strays too far from “UTC everywhere”.
I have a two questions:

Shouldn’t
this
read “Timestamps are represented in Postgres as a 64 bit signed integer”? If so, should this be in a separate PR?
As converting from DateTime to Date (for example) is easy, should  there be impls like impl ToSql<Date> for NaiveDateTime, or should mappings between types be strict?

Shouldn’t this read “Timestamps are represented in Postgres as a 64 bit signed integer”? If so, should this be in a separate PR?

Yes to both.

As converting from DateTime to Date (for example) is easy, should there be impls like impl ToSql for NaiveDateTime, or should mappings between types be strict?

I'd prefer to be strict -- as you said, it's easy to convert from DateTime to Date if that's what you need. I prefer to avoid any implicit loss of precision.

This is a great start, thanks for working on it.

I cleaned up the code, squashed the commits, and merged in https://github.com/sgrif/diesel/commit/9d879552f348c2747c527bf49c4b92f0b548672f. Feel free to take a swing at dates/times as well (Julian day conversion, yayyyyyy)

Wow, that was quick! Great! (It’s my first real code PR on github!) Thanks for the guidance!
I was just checking the official documentation and even the postgres source (that was not very helpful) to see how binary timestamps are handled with respect to timezones.
I can’t say I grok all the implications of the impls with timezones, so it is probably safer to remove them indeed.
What I understand from the official docs is that the binary representation is always UTC, and timestamptz is only meant to indicate a time zone should be provided in the input expression so postgres can properly convert it to the internal UTC representation. On the output side, everything is converted to (or interpreted as, if it is a timestamp sans timezone) local time. (I may very well be wrong).
I will most definitely try to do dates and times too if no one else does it first.

Right, and so we can do an impl of ToSql for all the various non naive types to timestamptz, with only an impl of FromSql for DateTime<UTC>.

(I need to read through the docs more thoroughly on that front, too)

authors: sgrif tohou

repo: sgrif/diesel


text:
missing license info

Hello,
can you please add licensing info? Can we assume, based on ARPL repo, that this is also MIT license?

Hi, thanks for the reminder. Just added :)

authors: mmalmir sgvaze


text:
Events from inputs seem to be mutable

From the main website, on the ToDo app, you see this code to handle the changes from an input element:
  def handleChange(e: SyntheticEvent[html.Input, Event]): Unit = {
    val eventValue = e.target.value
    setState(_.copy(text = eventValue))
  }

I'd expect that calling setState(_.copy(text = e.target.value)) would work but it doesn't, leading to a NullPointerException because target is null.
From what I understand, it happens because the event e is a JavaScript object that's mutated when the event handler finishes, and when react ends up invoking the inner function set the actual, such event has already been mutated.
I haven't seen this behavior being documented on the docs but it's a tricky one, is there any chance to avoid it?
Thanks.

I believe this will be a non-issue in React 17, per https://reactjs.org/blog/2020/08/10/react-v17-rc.html#no-event-pooling

Looks like it will, is it safe to use React 17 with Slinky 0.6.5?
Thanks.

React 17 should work fine, Slinky doesn't depend on any of the changed APIs.

authors: AlexITC ramnivas shadaj

repo: shadaj/slinky


text:
Shadcn tailwind-merge error Problem

i have encountered many problem using shadcn when i try to learn it, it's always having same error again and again

@HanyaRaff Can you tell me more about your stack? Which framework are you using? If you have a reproducible copy, that'd be helpful to debug.

I'm using Next.js 13, React, Convex, Tailwind in my project, and today i found a new error

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

authors: HanyaRaff shadcn

repo: shadcn-ui/ui


text:
[bug]: Fast clicking/taping when ticking checkboxes will return it to its original state

Describe the bug
When multiple checkboxes are present on a single page, there is an issue where rapidly clicking a checkbox can cause it to revert to its previous state. This behavior appears to be triggered when a "double-click" (dblclick) browser event is registered. It is really hard to reproduce it on a destop, but on mobile i can reproduce it every time.
The problem has been observed specifically in the Safari browser on iOS devices.
For further reference, please see the related GitHub issue: React Issue #19841.
A demonstration of this behavior can be found in the following video: Video Example
Someho ChakraUI managed to make this issue a thing in a past.
https://v2.chakra-ui.com/docs/components/checkbox/usage
Affected component/components
Checkbox
How to reproduce

Have multiple checkboxes on one page (or go to https://ui.shadcn.com/docs/components/checkbox | Form Section)
Try to check/uncheck them quickly.

Codesandbox/StackBlitz link
https://ui.shadcn.com/docs/components/checkbox
Logs
No response
System Info
It works the same in Simulator and on Real Device
iOS: 18.0
Safari for iOS

Before submitting

[x] I've made research efforts and searched the documentation
[x] I've searched for existing issues

I've raised this issue on react https://github.com/facebook/react/issues/31260 as I'm noticing this when just using basic controlled / uncontrolled checkboxes.

authors: danielddb mrxelnag


text:
fix(3739): added support for accessibility

Closes #3739

Hi @SoyDiego  @ruru-m07 , The merge option is still disabled. Please share the steps for merging this one


text:
Do not set dark text on fill color btn [Issue #115]

Do not set dark text on fill color btn (added rule in .less file).
Issue #115

Thank you @cosay !

authors: cosay shahednasser

repo: shahednasser/sbuttons


text:
An Error that Shows In Android Studio

@shahzar  DaggerAppComponent Error on TheApplication.java Class

DaggerAppComponent is a class generated by Dagger2. Try rebuilding your project, or try a clean build.
Ref:
https://google.github.io/dagger/users-guide#building-the-graph

authors: IamJithendra shahzar

repo: shahzar/StatusSaver-for-Whatsapp


text:
Rotate on Fullscreen (Android)

Have you read the FAQ and checked for duplicate open issues?
Extension of closed issues https://github.com/google/shaka-player/issues/883 https://github.com/google/shaka-player/issues/2494 https://github.com/google/shaka-player/issues/2653
Is your feature request related to a problem? Please describe.
I'm using shaka-ui and doing the reverse of the above (rotate-on-fullscreen). However, the two features combined prevent Android PIP from working when the device is locked to portrait.
Describe the solution you'd like
This is happening because shaka-ui's fullscreen-on-rotate feature exits fullscreen on portrait rotation (which happens when triggering PIP if the device is portrait-locked).
Describe alternatives you've considered
It's not a big deal to disable this via enableFullscreenOnRotation, but it may be worth tracking if the fullscreen request was triggered by a landscape rotation and then only exiting fullscreen on return to portrait if so.
Additional context
As it is, without my rotate-on-fullscreen, it's possible to manually request fullscreen while in portrait. With autorotate, it's possible to switch to landscape, but then not back to fullscreen portrait again without shaka-ui automatically exiting fullscreen.
https://github.com/google/shaka-player/commit/20c60e65caaefd3bdcc82fa94c43ecbd82c69350#diff-0e63b8017cb301a39d856ad6afb203a028f5f5601423b2e301a6b64cc3ead593R212-R215
For reference, I'm currently implementing rotate-on-fullscreen externally like so:
  if (screen.orientation && screen.orientation.lock)
    document.querySelectorAll('[data-shaka-player-container]').forEach(el => {
      el.addEventListener('fullscreenchange', e => {
        if (document.fullscreenElement)
          screen.orientation.lock('landscape')
      })
    })

Ack, just found https://github.com/google/shaka-player/commit/6694d3c13ede673b80fa36285a93584ab0e6a9b3
Closing

@ziddey, I'm sorry, but I don't understand this issue.  If you go into PiP while in fullscreen mode, don't you expect fullscreen to end?  You can't be in PiP and fullscreen at the same time.
You also left a comment on 6694d3c, but it's not clear to me if there is still an issue, since you closed this one.  Is there something we missed?

When going fullscreen, the shaka player container is the fullscreen element.
From here, Android PIP can be triggered by escaping to the homescreen. Now in PIP mode, the fullscreen element is still the shaka player container.
However, with fullscreen-on-rotation enabled, document.exitFullscreen() is called if the screen goes back to portrait mode.
So this scenario can happen:

Android device is set to portrait (auto-rotate disabled)
Shaka player loaded (both forceLandscapeOnFullscreen and enableFullscreenOnRotation enabled as is the new default)
Play video and go fullscreen
Screen will be forced to landscape
Go home (trigger PIP) -- video player container is no longer actually fullscreen, but the element still is for the document (it's "fullscreen" in the pip-box).
Android device goes back to portrait (see #1)
fullscreen-on-rotate detects portrait and exits fullscreen for the document
Unsetting fullscreen for video player container element causes Android PIP to cancel
Back at homescreen with no PIP

PIP requires there be a document.fullscreenElement.

Can you test with v4.3.4? Thanks!

authors: avelad joeyparrish ziddey

repo: shaka-project/shaka-player


text:
downloaded a playlist but its not appearing on my computer anywhere

I just downloaded a 113 song playlist and the files are nowhere to be found in the place the program told me they would be or anywhere else on my computer

Run the program as administrator


text:
🛑 Shakedown Social - Uploads is down

In 91dd639, Shakedown Social - Uploads (https://files.shakedown.social/accounts/avatars/109/357/389/718/265/462/original/dd80d2c95e48cfd2.jpeg) was down:

HTTP code: 403
Response time: 285 ms

Resolved: Shakedown Social - Uploads is back up in ff9bfd6.

repo: shakedown-social/upptime


text:
🛑 Shakedown Social - Uploads is down

In 342d502, Shakedown Social - Uploads (https://files.shakedown.social/accounts/avatars/109/357/389/718/265/462/original/c83dff7e175cde04.png) was down:

HTTP code: 404
Response time: 45 ms

Resolved: Shakedown Social - Uploads is back up in 17c5fd3 after .


text:
Actually update labels.

Fixes #75.

CI failure is unrelated.

repo: shakenfist/client-python