Building decomposition

What is the difference of building parts, building units, and building storeys and their intended usage? Am I understanding it correctly, that a building can be subdivided into parts once and after that ad libitum into storeys (horizontal subdivision) and units (vertical subdivision) in an alternating way? If so, the building part definition seems redundant, but probably I am missing something.

My understanding:  buildingpart is a building but not a top-level-feature: it is a physical subdivision belonging to some top-level building. It is also a building. buildingunit is a set of spaces associated with a building and has identifying properties that allow grouping into functional units. storey is a special kind of buildingunit that is distinguished because it is likely to be used a lot.
This all makes sense to me, although I find the case for buildingpart to be weak. But maybe I am not thinking of the critical use case.
I think part of the semantic confusion stems from the naming of the classes. In particular, it would help to have the last word of a compound word be the name of the underlying class.
Assuming that I have the above correct, would it make sense to change the class names to make the representation function of the classes more obvious? buildingpart could be named subbuilding or subordinatebuilding to indicate both that it is not a top-level feature and that it is a building. buildingunit could be called logicalsubdivision or logicalunit  to clearly indicate its function and to make it clear that it is not a building.

In the Modelling Subgroup we agreed that we need to include in the specification a detailed description of the three concepts and give clear recommendation when to use which concept.
We will create a drawing showing the differences of the concepts.
In addition, we will try to get feedback from the CityGML SWG group at the next OGC meeting in Singapore on these concepts.

I also still struggle with the BuildingPart, although it is clear now that it is a full-featured Building, with all attributes of Building, e.g. roof type, as opposed to a BuildingUnit. But then, if you have BuildingParts with all these attributes, would the aggregation of these parts need to have these same attributes again? If so in which cases? Otherwise, if the aggregated Building would merely be a group of BuildingParts without its own attributes, then why not model it as a group of Buildings or just let the CityModel play the role of the aggregator?

WHAT IS THE NEED FOR BUILDING PARTS? – A COMPARISON OF CITYGML, INSPIRE BUILDING AND A SWEDISH BUILDING STANDARD
yesterday, we had a nice presentation on Building / Building Part modelling in different standards from Sweden at the 3D GeoInfo.
https://www.int-arch-photogramm-remote-sens-spatial-inf-sci.net/XLII-4-W10/27/2018/

just as an example of a CityGML profile as discussed today at the SWG meeting. It defines how building / building part are used in Germany on city models generated by the state survey (LoD2, fully automized process based on 2D cadastral plans). The 3D model product spec on state level. Municipalities usually have more detailed models. Unfortunately in german, but your may use google translate or another translation software.
http://www.adv-online.de/AdV-Produkte/Weitere-Produkte/3D-Gebaeudemodelle-LoD/binarywriterservlet?imgUid=f760754e-b81c-c514-611d-1565d1cbf297&uBasVariant=11111111-1111-1111-1111-111111111111
And the validation plan to validate the 3D models.
http://www.adv-online.de/icc/extdeu/med/9c6/9c650858-1a2a-cd51-77ff-f6d45d1cbf29,11111111-1111-1111-1111-111111111111

Buildings with 'parts' that are stacked on top of each other are common.
As an example, we can consider Pacific Place in Hong Kong.
http://1.bp.blogspot.com/-sBOZHP2jbHc/ToK8jbfXFbI/AAAAAAAAAlc/EGc4u2wnnCw/s1600/Pacific%2BPlace.jpg
https://www.google.com/url?sa=i&source=images&cd=&cad=rja&uact=8&ved=2ahUKEwjNgobpg9vgAhUUTo8KHWScC2IQjRx6BAgBEAU&url=http%3A%2F%2Fwww.heatherwick.com%2Fproject%2Fpacific-place%2F&psig=AOvVaw0EB9Hn-Gk-5C3pjyqc2IuJ&ust=1551326529735086
There is a podium with multiple towers, and the space ontop of the podium is a space that is accessible to the public. The towers are each separate buildings. The location of the ground plane is quite ambiguous since there are multiple levels that feel like the ground. The actual ground is somewhere deep down under the underground car parking levels.
Another example might be the Marina Bay Sands in Singapore.
https://www.marinabaysands.com/content/dam/singapore/marinabaysands/master/main/home/Revamp/new-homepage/offers/new_welcome-offers_v1.jpg
The concepts of building, building part, building unit, storey, do not seem to fit very well for these types of building. It seems that the current definition of building part is that it must be in contact with the ground. In hight density cities, the groundplane is often a very ambiguous concept, so it is not clear if something is in contact with the ground.
Originally posted by @phtj in https://github.com/opengeospatial/CityGML-3.0CM/issues/58#issue-414935161

It is also important to remember that the vast majority of LOD2 building models that have been or are being created in (semi-)automatic processes are based on 2D building footprints and photogrammetry or airborne lidar.
If at all, building parts are created in these processes based on subdivisions that are modelled in the footprints. If the footprints are not subdivided, then it is rather hard to automatically identify building parts based on changes over height in this input data.

In the modelling subgroup there was broad agreement that the vertical stacking of building parts should be allowed in CityGML 3.0 to support the provided examples. Building parts should therefore no longer be required to touch the ground.
To avoid confusion, more precise definitions and descriptions have to be provided in the specification for the different semantic concepts. Like Building, also BuildingPart is derived from AbstractBuilding and thus is a full-featured building with the same attributes and possibilities to model subfeatures. So it is qualitatively different from subdivisions (storey, building unit) which are not buildings on their own.
It was also proposed to keep the name BuildingPart since it has been used since CityGML version 0.4.
A remaining open question is whether, in case building parts are modelled, the embracing Building still may have attributes, geometries and nested subfeatures, or whether it should just be used as an empty container for the building parts. A clear, precise and testable definition is required for this scenario. It is agreed that the CityGML 2.0 conformance requirement <IP_ADDRESS> is insufficient and needs to be replaced.


Spark history server implementation

Spark comes with a history server, it provides a great UI with many information regarding Spark jobs execution (event timeline, detail of stages, etc.).
Details can be found in the Spark monitoring page.
I've modified the gettyimages/docker-spark to be able to run it with the docker-compose upcommand.
With this implementation, its UI will be running at http://${YOUR_DOCKER_HOST}:18080.

To use the Spark’s history server you have to tell your Spark driver:

to log events: spark.eventLog.enabled true (it's false by default)
the log directory to use: spark.eventLog.dir file:/tmp/spark-events

By default the /tmp/spark-events is mounted on the ./spark-events at the root of the repo (I call it $DOCKER_SPARK).
So you have to tell the driver to log events in this directory (on your local machine).
This example shows this configuration for a spark-submit (the two --conf options):
DOCKER_SPARK="/Users/xxxx/Git/docker-spark"

$SPARK_HOME/bin/spark-submit \
  --class org.apache.spark.examples.SparkPi \
  --master spark://localhost:7077 \
  --conf "spark.eventLog.enabled=true" \
  --conf "spark.eventLog.dir=file:$DOCKER_SPARK/spark-events" \
  $SPARK_HOME/examples/jars/spark-examples_2.11-2.3.1.jar \
  10

Note: This settings can be defined in the driver's $SPARK_HOME/conf/spark-defaults.conf to avoid using the --conf option.
This comment comes from my blog post.

the log directory to use: spark.eventLog.dir file:/tmp/spark-event

If the drivers and executors are ephemeral, how can you access task logs via the history server?


Expose Lambda function architectures

Allows the user to configure the Lambda function architecture. Fixes #70.

Thanks again for the prompt response and PR @bwhaley! 🙌
I tested this and found that the property needed fixing up, have linked the PR above ☝

Thanks for the fix @n-tucker. I pulled your commit in here so I'll merge this and cut a release.


Flash column fixed, Energy balance added

In Flash column, when either temperature or pressure is given out of VLE range, the model was throwing compilation error. It has been fixed and Energy balance is added.

Can you create an issue first against which this fix was provided?


Would it make sense to use anyOf for Union types instead of oneOf ?

Right now, Union types are encoded as oneOf in the json_schema.
This causes errors if you have a union of two types that serialize to a compatible representation.
The following code produces a validation error:
from dataclasses import dataclass
from dataclasses_jsonschema import JsonSchemaMixin
from enum import Enum
from typing import Union

class E(Enum):
    A= 'a'
    B= 'b'

@dataclass
class Data(JsonSchemaMixin):
    field : Union[E,str] = E.A

a=Data()
a.to_dict(validate=True)

This is because E.A is serialized to 'a' which is both a valid E and a valid str.
I think the proper validation here would be to use anyOf.
What do you think?

The question is: what is the point of oneOf in JsonSchema?
https://json-schema.org/understanding-json-schema/reference/combining.html#oneof
I do think validation should use anyOf.

The question is: what is the point of oneOf in JsonSchema?
https://json-schema.org/understanding-json-schema/reference/combining.html#oneof
I do think validation should use anyOf.


Mapping classes with conflicting naming in libraries fails

This issue seems to have been introduced after 5.1.9 somewhere.
I have a schema which roughly looks like this:
enum Currency {
  USD, EUR
}

type Item {
   amount: Amount
   currency: Currency
}

I have type mappings like this:
Currency -> generated.Currency
Amount -> java.lang.Long
What happens is that I do not get the type mapping as part of the import statement in the generated class. I am generating Java. The issue seems to be that the codegen actually wants to find the type it maps to, as it works if I change the mapping to an existing class.
Is this a bug or a feature? I see no reason why I shouldnt be able to use my generated classes as part of the type mapping which exists in the first place to avoid naming clashes.

Looks like a bug. You should be able to override via type mappings.

You can't use type mappings with codegen generated classes. i.e Amount should work but the type mapping for Currency will not if it is generated by codegen.

Seems like you disagree a bit here. Imo it makes a lot of sense to be able to use whatever you generate. This is an issue for all mappings using "homemade" scalars.


fix: docs with passing proper modelId to api calls

fix with proper modelId (elevenlabs_multilingual_v2 does not exists and using it causes 400 response status code) so kickstarting api calls is easier and does not fail

Good catch. Thank you for the contribution @mgorsk1
I have reviewed it as part of the next release

thanks @FelixWaweru and thanks for this package. Just FYI I have used it to extend node-sonos-api with Elevenlabs TTS provider - https://github.com/jishi/node-sonos-http-api/pull/879 , very useful client to have.

That's awesome @mgorsk1 ! I'm glad you're finding the package useful


Handle multiple teamsWithChosenChannels in pushstate

@mlsteele had his teamsWithChosenChannels reset twice in the last week. It's because his client doesn't know about the existing teamsWithChosenChannels, and injects a new empty one so he ends up with two. This PR adds detection for multiple teamsWithChosenChannels arrays. We take the union of any valid items we find, and dismiss any invalid ones along the way. It's a little dangerous to modify the gregor state in its own receiver, but actions returned from handleTeamsWithChosenChannels monotonically decrease the number of teamsWithChosenChannels in the gregor state, so as long as we're not passing an invalid array in L192, we shouldn't get into a loop here. r? @keybase/react-hackers

I also tested by manually injecting duds into my gregor state and watching the reconciliation in the logs.


Introduce Kamelet binding create command

Changes

Add Kamelet binding command with first subcommand create
Refactor bind command to work as a shortcut for binding create
binding create follows the common kn conventions to use name as positional argument and --kamelet as source
Update README with command information

Sample for new binding create subcommand:
kn source kamelet binding create telegram-to-broker --kamelet telegram-source --broker default --sourceProperty=token=xxx

@rhuss can you take a look please?

@christophd yes, sure. I have some calls coming up, hope to jump on it later today

before jumping on the review, I already have one question about the syntax:
kn source kamelet binding create telegram-to-broker --kamelet telegram-source --broker default --sourceProperty=token=xxx

So, a KameletBinding does not use the Destination sub-schema as known from Knative for addressing arbitrary sinks ? This would be really awesome as any other source use this for configuring the target (actually, that is the defining characteristics of a Knative Sink).
Instead of --broker default I would have expected:
--sink broker:default
--sink channel:mychannel
--sink myksvc
--sink ksvc:myksvc
--sink http://myapp-myns.example.org

That is how all the other sources can specify their target.

(btw, if this syntax could be also used for kn source kamelet bind, that would be great, too)

actually the command supports both --broker default and --sink broker:default
Supported for --sink are:

broker:
channel:
service:

Would you prefer ksvc: instead of service:?

(btw, if this syntax could be also used for kn source kamelet bind, that would be great, too)
yes, it is the same syntax used also in bind command

This is how sinks are specified for other sources:
Addressable sink for events. You can specify a broker, channel, Knative service, or URI. Examples: '--sink
broker:nest' for a broker 'nest', '--sink channel:pipe' for a channel 'pipe', '--sink ksvc:mysvc:mynamespace' for
a Knative service 'mysvc' in another namespace 'mynamespace', '--sink https://event.receiver.uri' for an URI with
an 'http://' or 'https://' schema, '--sink ksvc:receiver' or simply '--sink receiver' for a Knative service
'receiver' in the current namespace. If a prefix is not provided, it is considered as a Knative service in the
be provided explicitly.
Plus we allow custom mappings from the ~/.config/kn/config.yaml. We are currently underway to move the parsing code to knative/client-pkg which can be used by plugins, so we might consider switching over in a later step.
The reason why service: prefix is left out is, that we want to allow users to also allow for mapping to standard k8s services (but we are not able to provide this ootb because kn is supposed to talk to Knative API only that does not know k8s services. This might change though in the future).
Please note also, that you can add an optional third part for the namespace.

@rhuss PTAL


New checklist feature

only open checklist view if checklist is empty (when clicking from mobile toolbar)

Also, when you click the checklist is first populated it should have autofocus!

Click checklist button
Focus should be within the checklist textfield

also, could you take a look into this bug:

only open checklist view if checklist is empty (when clicking from mobile toolbar)

673f54fb0e9d3f600f2eebdd1b6a1c720628b05c

Also, when you click the checklist is first populated it should have autofocus!

Click checklist button
Focus should be within the checklist textfield

4d6d1fd057f6a599802ed1076f7f772ee489db9a

look at my changes and apart from that LGTM


[SPARK-29609][SQL] DataSourceV2: Support DROP NAMESPACE

What changes were proposed in this pull request?

This PR adds DROP NAMESPACE support for V2 catalogs.
Why are the changes needed?

Currently, you cannot drop namespaces for v2 catalogs.
Does this PR introduce any user-facing change?

The user can now perform the following:
CREATE NAMESPACE mycatalog.ns
DROP NAMESPACE mycatalog.ns
SHOW NAMESPACES IN mycatalog # Will show no namespaces

to drop a namespace ns inside mycatalog V2 catalog.
How was this patch tested?

Added unit tests.

cc: @cloud-fan @rdblue

Merged build finished. Test PASSed.

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

Test build #112691 has started for PR 26262 at commit 588b2ce.

Test build #112691 has finished for PR 26262 at commit 588b2ce.

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

Merged build finished. Test PASSed.

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

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

Build finished. Test FAILed.

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

Could you resolve the conflicts, @imback82 ?

Merged build finished. Test PASSed.

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

Test build #112788 has started for PR 26262 at commit 634952e.

Test build #112788 has finished for PR 26262 at commit 634952e.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class Version() extends LeafExpression with CodegenFallback
case class LoadDataStatement(
case class LocalShuffleReaderExec(child: QueryStageExec) extends UnaryExecNode

Merged build finished. Test PASSed.

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

Thanks everyone for help!


Pseudo-compilation?

Not really an issue. Just to comment that this repo is really amazing. Thanks for sharing!
What about a kind of pseudo-compilation to help debug the code itself?
After a few trials got this prompt:
You are an AI Assistant ruled by the program shown bellow. The program is written in SudoLang, a pseudo-programming language created to interact programatically with LLMs. SudoLang code abstract instructions, written in natural language, to be interpreted by the LLM. Just like other running programming languages you need to first read the instructions and simulate a psedo-compilation process to check inconsistencies such as syntax errors. Print the compilation errors if it is the case. Otherwise just run the code. Don't print unnecessary observations.
That used with this example:
The program:

function square: (x){
   return x times x times x
}
function askAndWaitForReply: {
   reply = ask("Give me a number")
   a,b = square(reply
   return "$a^2 = b"
}

askAndWaitForReply()

got this reply from GPT-4:
Compilation errors:

In function 'square', the calculation should be x times x, not x times x times x.
In function 'askAndWaitForReply', there is a missing parenthesis in the line 'a,b = square(reply'.
Corrected program:

function square: (x){
return x times x
}
function askAndWaitForReply: {
reply = ask("Give me a number")
a, b = square(reply)
return "$a^2 = b"
}

askAndWaitForReply()

And then running with the proposed version still got a new error:
There is a syntax error in the program. The function square should return only one value, but two values (a, b) are being assigned when calling the square function. Here's the corrected version of the program:

function square: (x){
return x times x
}
function askAndWaitForReply: {
reply = ask("Give me a number")
b = square(reply)
return "$reply^2 = b"
}

askAndWaitForReply()

Now running the code:

Give me a number: 5
5^2

And then I changed finally to the program:
The program:

function square: (x){
return x, x times x
}
function askAndWaitForReply: {
reply = ask("Give me a number")
a, b = square(reply)
return "$a^2 = $b"
}

askAndWaitForReply()

It resulted in:
GPT-4: Give me a number
Me:  7
GPT-4: 7^2 = 49

SudoLang has a built-in linter.


add EmitterBuilder.ofNode and mapEmitter

This makes EmitterBuilders more useful. You can have an EmitterBuilder[X, VNode] via EmitterBuilder.ofNode. For VDomModifier, you can still use EmitterBuilder.ofModifier. Additionally, you may map over the result of an EmitterBuilder via mapEmitter.
We are restricting the EmitterBuilders to these two types, because we might need to handle a monix subscription when using observable-based EmitterBuilder transformations. And we can nicely handle these subscriptions for Nodes and Modifiers by using lifetime hooks. We could probably add another EmitterBuilder.custom method to have any type while handling the subscription yourself. But I am not sure whether this is really needed, because EmitterBuilders are usually used for Modifiers.
Update: I have added EmitterBuilder.custom:
def custom[E, R](f: ConnectableObserver[E] => R): EmitterBuilder[E,R]

So, ConnectableObserver is an observer that needs a subscription. Not every usage of an Emitterbuilders yields a subscription, but if you call .transform on the usage site, you will need a subscription for the observer to work. So, this interface just lets you handle this case every time. You can just run the subscription via observer.connect(): Cancelable which needs an implicit Scheduler.

Ok, I am thinking about unifying the methods ofModifier and ofVNode. Maybe just have EmitterBuilder.apply[EventType, T <: VDomModifier]?


chore(pgk): add update-snapshot script for all tests

This PR adds a very simple update-snapshot script. This enables a contributor to run:
yarn test:update-snapshots

I also updated the SETUP.md guide to reflect this change.

What kind of change does this PR introduce?
Build related change

Did you add tests for your changes?
N/A

Does this PR introduce a breaking change?
N/A

What needs to be documented once your changes are merged?
N/A

I'll merge once final check runs.

Thanks


Generating changelog automatically

Work still needs to be done to generate better changelog. But this is significant work in progress toward automated changelog as required by #237
Happy to clean the code/update things, so please review @iincer

I'm facing an issue with the git-changelog package that I have raised here https://github.com/pawamoy/git-changelog/issues/44

Changelog is working as expected. Added instructions to CONTRIBUTING.md on how to write commit messages to help with automatic changelog generation. Ready for review @iincer.


test: keep namespace when test failed in dev mod

Type of change:

[ ] Bugfix
[x] New feature provided
[ ] Improve performance
[ ] Backport patches

Related issue
Add environment variable E2E_ENV to indicate e2e-test environment. If test case failed and E2E_ENV=dev, related resources will not be deleted.
What this PR does / why we need it:

Pre-submission checklist:

[ ] Did you explain what problem does this PR solve? Or what new features have been added?
[ ] Have you added corresponding test cases?
[ ] Have you modified the corresponding document?
[ ] Is this PR backward compatible? If it is not backward compatible, please discuss on the mailing list first

Codecov Report

Merging #1158 (f5a2e57) into master (a73b52d) will increase coverage by 0.23%.
The diff coverage is 35.68%.

@@            Coverage Diff             @@
##           master    #1158      +/-   ##
==========================================
+ Coverage   30.21%   30.45%   +0.23%
==========================================
  Files          81       81
  Lines        9463     9839     +376
==========================================
+ Hits         2859     2996     +137
- Misses       6289     6517     +228
- Partials      315      326      +11

Impacted Files
Coverage Δ

pkg/config/config.go
65.34% <ø> (-1.00%)
:arrow_down:

pkg/ingress/apisix_upstream.go
0.00% <0.00%> (ø)

pkg/ingress/controller.go
0.38% <0.00%> (-0.02%)
:arrow_down:

pkg/ingress/status.go
0.00% <0.00%> (ø)

pkg/kube/translation/translator.go
34.28% <23.68%> (-8.06%)
:arrow_down:

pkg/kube/translation/apisix_upstream.go
82.54% <82.79%> (-0.41%)
:arrow_down:

cmd/ingress/ingress.go
78.84% <100.00%> (-0.60%)
:arrow_down:

pkg/kube/translation/ingress.go
60.90% <0.00%> (-7.76%)
:arrow_down:

... and 2 more

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 73498bd...f5a2e57. Read the comment docs.

LGTM
also cc @AlinsRan

I can help you resolve the conflicts. Just add one commit to delete the action.yml file

I think the logic here could be simpler.

Indeed. I can try to implement it in a simpler way. Thanks for your suggestion.

Thanks


Validate okta creds on aws-okta add

split user auth out of AuthenticateProfile into AuthenticateUser
use AuthenticateUser to validate creds

See TOOL-340

@dfuentes: we talked IRL about saving/reusing the session cookie. Seems like there's a few cookies/tokens in play here. You get the token from the Okta auth call, then you use the token in the AWS SAML call, and that gives you a reusable cookie. Detangling the AWS SAML stuff so it's usable from add would be a fair amount of work at this point. It'd probably be easier to roll add into the login command. I'm gonna leave it as future work

Re https://github.com/segmentio/aws-okta/pull/56#pullrequestreview-133721623 I experimented with cleaning it up a bit. I'll add the commit and you can tell me what you think

nice work!


feat: log rotate

Z2M_LOG_MAXFILES and Z2M_LOG_MAXSIZE env vars can be used to override defaults settings
Fixes #1158

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

8 of 8 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 29.657%

Totals

Change from base Build<PHONE_NUMBER>:
0.03%

Covered Lines:
3676

Relevant Lines:
13037

💛  - Coveralls

Why should this be managed by an application? This is OS responsibility...
This now break/causes unexpected behavior for people that do set things up correctly (and now end up with unexpected behavior on their log rotate configuration).

I answered to you in the other thread

I know, don't agree.


License?

I am somewhat interested in creating a TUI tool in Rust for using todotxt files, and may use this project as a basis, and thus would like to know if your work is licensed under any particular license.
Many thanks!

Whoops, missed the LICENSE file, closing issue.
Silly me, sorry!

I am somewhat interested in creating a TUI tool in Rust for using todotxt files

Great 😃
Let me know if you copy/paste many lines of code, it’s probably a good idea to create a new crate.


Update Versions of Grafana and Telegraf

This is a proposal to upgrade the pinning to newer version of Grafana and Telegraf:

Grafana (v9.4.14)
Telegraf (v1.28.2)
pyPowerwall (v0.6.2t28) - Required to support background color adjustments for newer Grafana versions

During testing, the "look" difference between Grafana v9.1.2 and v9.4.14 are minor. There is a subtle adjustment to the font and labeling (IMHO looks better). No issues with panels. The Power Flow Animation required an update to pyPowerwall to accommodate the grafana-dark background color (transparent settings were in use before, but no longer work).
Related discussions:

https://github.com/jasonacox/Powerwall-Dashboard/discussions/371
https://github.com/jasonacox/Powerwall-Dashboard/discussions/363
https://github.com/jasonacox/Powerwall-Dashboard/issues/368

Why not use Alpine-based images?
docker.io/grafana/grafana        9.4.14                f69ac1c180a5  7 weeks ago    332 MB
docker.io/grafana/grafana        9.4.14-ubuntu         76a0cce050ec  2 months ago   428 MB

docker.io/library/telegraf       1.28.2-alpine     3d231738b7db  2 weeks ago    210 MB
docker.io/library/telegraf       1.28.2            f10f8ba7295f  3 weeks ago    453 MB

Good question. Is there a reason? Key is to make sure we target all architectures (amd64, arm32, arm64) to ensure it they have builds that run on things from Raspberry Pis, x86 to Macs.

Good question. Is there a reason?

I know I ran into an issue when I was doing my ToU service - alpine does not include gcc (required by pandas). Not sure if this could affect any of the core modules in the dashboard. I also have a memory that there is an issue with RPi support for some of the python versions.


Avoid transmute

Currently the implementations uses transmute to create CellIndex, VertexIndex and DirectedEdgeIndex instances in cases where it is known that the underlying u64 values are known to be valid. This is unsafe should be avoided.
The way the h3o API intends to to this is by using the TryFrom implementation with validation to ensure the contained values are valid - going this route would require validating the values on each access of the arrow array - so it comes at a runtime cost.
Need to find a better solution for this.

h3o uses new_unchecked methods internally to construct index values without validation, but these methods are - understandably - not exposed in the public API.
https://github.com/HydroniumLabs/h3o/blob/master/src/index/cell.rs#L1367
Need to run a few benchmarks first if using TryFrom validation

While the validity checks are quite fast (~3ns for a CellIndex and ~5ns for DirectedEdgeIndex), except for VertexIndex, they still add up and end up being noticeable when working on large sets (and that's why I've added those new_unchecked methods).
For instance, on the uncompactCell benchmark (which expands to ~850k cell indexes), using try_from instead of new_unchecked gives the following results:

# new_unchecked      time:   [1.3658 ms 1.3663 ms 1.3671 ms]
# try_from           time:   [3.2436 ms 3.2472 ms 3.2517 ms]
                     change: [+136.90% +137.40% +137.84%] (p = 0.00 < 0.05)
                     Performance has regressed.

IIUC, the usage of transmute here should be safe, since I used repr(transparent), as long as you're sure that the value is valid. But of course, would be better if it could be avoided it.


HADOOP-18466. Limit the findbugs suppression IS2_INCONSISTENT_SYNC to S3AFileSystem field

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 45s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
xmllint
0m  0s

xmllint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

_ trunk Compile Tests _

+1 :green_heart:
shadedclient
30m  3s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
shadedclient
19m 24s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
asflicense
0m 53s

The patch does not generate ASF License warnings.

53m 15s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4926/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4926

Optional Tests
dupname asflicense codespell detsecrets xmllint

uname
Linux eb87632dc9f7 4.15.0-191-generic #202-Ubuntu SMP Thu Aug 4 01:49:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 07d5903cd86f4305b351eb024d82ee351a99c2e9

Max. process+thread count
558 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-aws U: hadoop-tools/hadoop-aws

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4926/1/console

versions
git=2.25.1 maven=3.6.3

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.


Fehler im Log

`

info.0
2022-08-25 11:20:17.005
error
line is not defined

info.0
2022-08-25 11:20:17.005
error
ReferenceError: line is not defined at filterLines (/opt/iobroker/node_modules/systeminformation/lib/filesystem.js:66:9) at /opt/iobroker/node_modules/systeminformation/lib/filesystem.js:127:23 at ChildProcess.exithandler (node:child_process:390:7) at ChildProcess.emit (node:events:527:28) at ChildProcess.emit (node:domain:475:12) at maybeClose (node:internal/child_process:1092:16) at Socket. (node:internal/child_process:451:11) at Socket.emit (node:events:527:28) at Socket.emit (node:domain:475:12) at Pipe. (node:net:709:12)

info.0
2022-08-25 11:20:17.005
error
uncaught exception: line is not defined

`

fixed in next version


dx-data-grid: cssClass on cell works only for global styles

version: 16.2.3-rc.3
Setting the cssClass property on a cell ( https://js.devexpress.com/Documentation/16_2/ApiReference/UI_Widgets/dxDataGrid/Configuration/columns/#cssClass ) works only for classes which are defined globally. Classes defined in an angular component do not work, as they are scoped to the component.
I would expect this to work for classes from the component's styles too.

Hello!
It's the same issue as in #124 . So, I am closing the current ticket.


clarify alpha example by removing evoked inputs

This clarifies which parameters are being changed in the default parameter set in order to create the alpha example. Specifically, I propose that we explicitly remove all parameters that pertain to proximal or distal evoked feeds. Note that the simulation produced on my branch (shown below) matches the alpha simulation produced on master.

Looks fine to me. Let me know when it's ready to merge. Any other improvements to narrative in examples would be more than welcome. I am hoping we can have proper examples/tutorials once @cjayb has the feed API implemented.


Changed absolute to floating

Closes #458

Thanks for the pull request @xuelongmu!

:heavy_check_mark: Signed CLA found.

Reviewers, don't forget to make sure that:

[ ] Cesium for Unreal Samples works.

Thanks @xuelongmu!


AlphaFold output formats

Switch tsv outputs to tabular as they are displayed weird (with fake headers) in the galaxy data viewer

This seems to be solved already


Create test cases for all box types

Issue: https://github.com/abema/go-mp4/issues/24

Codecov Report

Merging #25 into master will increase coverage by 0.13%.
The diff coverage is 75.00%.

@@            Coverage Diff             @@
##           master      #25      +/-   ##
==========================================
+ Coverage   82.76%   82.89%   +0.13%
==========================================
  Files          10       10
  Lines        1578     1573       -5
==========================================
- Hits         1306     1304       -2
+ Misses        162      161       -1
+ Partials      110      108       -2

Impacted Files
Coverage Δ

box_types.go
93.48% <66.66%> (+0.18%)
:arrow_up:

probe.go
64.23% <100.00%> (+0.60%)
:arrow_up:

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 1c1ec59...f68508f. Read the comment docs.


GoogleCalendarEntity

Logger: homeassistant.helpers.entity
Source: helpers/entity.py:885
First occurred: 23:16:45 (1 occurrences)
Last logged: 23:16:45

Updating state for calendar.xxxxxx_gmail_com (<class 'homeassistant.components.google.calendar.GoogleCalendarEntity'>) took 0.517 seconds. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+google%22

Are you sure that this is related to the Repo?

Oh, weird...pretty sure I followed the link and logged the issue.


Fixing vendors

Fix https://techweb.axway.com/jira/browse/AMP-98
This PR fixes vendor (again).
The version for each dependency has been fixed so that we're less vulnerable to any transitive dependency update.
The code has been updated to comply with the new dependencies.
How to test
Make sure you have the latest release version of dep (0.3.2):
$ dep version
dep:
 version     : v0.3.2
 build date  : 2017-10-19
 git hash    : 8ddfc8a
 go version  : go1.9
 go compiler : gc
 platform    : linux/amd64

Test with the following instructions:
$ rm -rf Gopkg.lock vendor
$ dep ensure
$ dep prune

Note that your vendor folder may differ from the one committed on this branch. It's probably because transitive dependencies might have been updated in the meantime. For more details on how dep works, please read https://github.com/golang/dep/blob/master/docs/FAQ.md#how-do-i-constrain-a-transitive-dependencys-version
Then make sure the code compiles and tests as expected:
$ ampmake clean build
$ amp cluster create
$ export PATH=tests/cli/testing:$PATH
$ TESTINCLUDE=tests/cli/testing testrunner tests/cli
$ docker run -it --rm --network core -v $PWD:/go/src/github.com/appcelerator/amp -w /go/src/github.com/appcelerator/amp appcelerator/amptools go test github.com/appcelerator/amp/tests/integration/...

Check Travis build.

I don't find this discrepancy. I followed the test steps described in the PR as well as tried the steps by @ndegory.
$ rm -rf vendor
$ dep ensure

I've tested on Mac with different versions of dep, same result:

dep from brew
dep from go get (master)
latest release (v0.3.2)

@neha-viswanathan can you please do the test again with:
rm -rf vendor
git checkout -- Gopkg.lock Gopkg.toml
dep ensure

@ndegory  tested with the steps you suggested. I don't see any errors.

@ndegory I couldn't reproduce this issue either. Can you please:

make sure you're using version 0.3.2
clean your dep cache and retry?

$ rm -rf $GOPATH/pkg/dep

~/Development/src/github.com/appcelerator/amp(vendor ✗) rm -rf $GOPATH/pkg/dep
~/Development/src/github.com/appcelerator/amp(vendor ✗) $GOPATH/bin/dep-darwin-amd64 version
dep:
 version     : v0.3.2
 build date  : 2017-10-19
 git hash    : 8ddfc8a
 go version  : go1.9
 go compiler : gc
 platform    : darwin/amd64
~/Development/src/github.com/appcelerator/amp(vendor ✗) $GOPATH/bin/dep-darwin-amd64 ensure
ensure Solve(): No versions of github.com/opencontainers/runc met constraints:
	v0.1.1: Could not introduce<EMAIL_ADDRESS>due to a case-only variation: it depends on "github.com/Sirupsen/logrus", but "github.com/sirupsen/logrus" was already established as the case variant for that project root by the following other dependers:
	(root)
	github.com/docker/distribution@edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c
<EMAIL_ADDRESS>
	v0.1.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint 0.1.1 from project github.com/appcelerator/amp.
	v0.0.9: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint 0.1.1 from project github.com/appcelerator/amp.
	v0.0.8: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint 0.1.1 from project github.com/appcelerator/amp.
	v0.0.7: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint 0.1.1 from project github.com/appcelerator/amp.
	v0.0.6: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint 0.1.1 from project github.com/appcelerator/amp.
	v0.0.5: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint 0.1.1 from project github.com/appcelerator/amp.
	v0.0.4: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint 0.1.1 from project github.com/appcelerator/amp.
	v0.0.3: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint 0.1.1 from project github.com/appcelerator/amp.
	v0.0.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint 0.1.1 from project github.com/appcelerator/amp.
	v0.0.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint 0.1.1 from project github.com/appcelerator/amp.
	v1.0.0-rc4: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint 0.1.1 from project github.com/appcelerator/amp.
	v1.0.0-rc3: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint 0.1.1 from project github.com/appcelerator/amp.
	v1.0.0-rc2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint 0.1.1 from project github.com/appcelerator/amp.
	v1.0.0-rc1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint 0.1.1 from project github.com/appcelerator/amp.
	master: Could not introduce github.com/opencontainers/runc@master, as it is not allowed by constraint 0.1.1 from project github.com/appcelerator/amp.
	fs-named-cgroup: Could not introduce github.com/opencontainers/runc@fs-named-cgroup, as it is not allowed by constraint 0.1.1 from project github.com/appcelerator/amp.
	relabel_fix_docker_1.9.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint 0.1.1 from project github.com/appcelerator/amp.
	resource-hf: Could not introduce github.com/opencontainers/runc@resource-hf, as it is not allowed by constraint 0.1.1 from project github.com/appcelerator/amp.
	v<IP_ADDRESS>: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint 0.1.1 from project github.com/appcelerator/amp.
~/Development/src/github.com/appcelerator/amp(vendor ✗)

There are no occurrences of 'github.com/Sirupsen/logrus' (Uppercase 'S') in the repository, so it must come from somewhere in your $GOPATH.
Can you please run these commands in your $GOPATH/src :
$ cd $GOPATH/src
$ find . -type f -name '*.go' -not -path '*vendor*' -exec grep -l 'github.com/Sirupsen/logrus' {} \;
$ find . -type f -name '*.go' -not -path '*vendor*' -exec grep -l 'github.com/sirupsen/logrus' {} \;
./github.com/appcelerator/amp/cmd/gateway/main.go
./github.com/appcelerator/amp/cmd/agent/main.go
./github.com/appcelerator/amp/cmd/amplifier/server/configuration/configuration.go
./github.com/appcelerator/amp/cmd/amplifier/server/server.go
./github.com/appcelerator/amp/cmd/amplifier/main.go
./github.com/appcelerator/amp/pkg/docker/service.go
./github.com/appcelerator/amp/pkg/docker/stack.go
./github.com/appcelerator/amp/pkg/cloud/aws/aws.go
./github.com/appcelerator/amp/pkg/cloud/provider.go
./github.com/appcelerator/amp/pkg/nats-streaming/nats-streaming.go
./github.com/appcelerator/amp/api/rpc/cluster/cluster.go
./github.com/appcelerator/amp/api/rpc/config/config.go
./github.com/appcelerator/amp/api/rpc/resource/resource.go
./github.com/appcelerator/amp/api/rpc/account/account.go
./github.com/appcelerator/amp/api/rpc/secret/secret.go
./github.com/appcelerator/amp/api/rpc/logs/logs.go
./github.com/appcelerator/amp/api/rpc/service/service.go
./github.com/appcelerator/amp/api/rpc/stack/stack.go
./github.com/appcelerator/amp/api/rpc/object_store/object_store.go
./github.com/appcelerator/amp/agent/api.go
./github.com/appcelerator/amp/agent/config.go
./github.com/appcelerator/amp/agent/agent.go
./github.com/appcelerator/amp/agent/logs.go
./github.com/appcelerator/amp/agent/container.go
./github.com/appcelerator/amp/docker/cli/cli/flags/common.go
./github.com/appcelerator/amp/docker/cli/cli/compose/loader/loader.go
./github.com/appcelerator/amp/docker/cli/cli/command/out.go
./github.com/appcelerator/amp/docker/cli/cli/command/events_utils.go
./github.com/appcelerator/amp/docker/cli/cli/command/inspect/inspector.go
./github.com/appcelerator/amp/docker/docker/pkg/term/windows/windows.go
./github.com/appcelerator/amp/docker/docker/pkg/system/syscall_windows.go
./github.com/appcelerator/amp/docker/docker/registry/config.go
./github.com/appcelerator/amp/docker/docker/registry/service.go
./github.com/appcelerator/amp/docker/docker/registry/auth.go
./github.com/appcelerator/amp/docker/docker/registry/resumable/resumablerequestreader.go
./github.com/appcelerator/amp/docker/docker/registry/registry.go
./github.com/appcelerator/amp/docker/docker/registry/session.go
./github.com/appcelerator/amp/docker/docker/registry/endpoint_v1.go
./github.com/appcelerator/amp/data/accounts/authz.go
./github.com/appcelerator/amp/data/accounts/store.go
./github.com/appcelerator/amp/data/storage/etcd/store.go
./github.com/appcelerator/amp/data/storage/etcd/watcher.go

If my other projects' vendors impact what happens in amp, we're in trouble. I have indeed a few projects using a different case:
ag -sl 'github.com/Sirupsen/logrus' -G .go$ .
gopkg.in/dancannon/gorethink.v1/gorethink.go
gopkg.in/dancannon/gorethink.v1/cluster.go
github.com/docker/infrakit.docker-metadata/cmd/main.go
github.com/docker/infrakit.docker-metadata/template.go
github.com/docker/infrakit/cmd/group/main.go
github.com/docker/infrakit/cmd/resource/main.go
github.com/docker/infrakit/examples/flavor/zookeeper/main.go
github.com/docker/infrakit/vendor/gopkg.in/inconshreveable/log15.v2/doc.go
github.com/docker/infrakit/vendor/github.com/docker/docker/pkg/archive/changes.go
github.com/docker/infrakit/vendor/github.com/docker/docker/pkg/archive/copy.go
github.com/docker/infrakit/vendor/github.com/docker/docker/pkg/archive/diff.go
github.com/docker/infrakit/vendor/github.com/docker/docker/pkg/archive/archive.go
github.com/docker/infrakit/vendor/github.com/docker/docker/pkg/archive/example_changes.go
github.com/docker/infrakit/vendor/github.com/docker/docker/pkg/system/syscall_windows.go
github.com/docker/infrakit/vendor/github.com/docker/docker/pkg/fileutils/fileutils_unix.go
github.com/docker/infrakit/vendor/github.com/docker/docker/pkg/fileutils/fileutils.go
github.com/docker/infrakit/vendor/github.com/docker/go-connections/sockets/unix_socket.go
github.com/docker/infrakit/vendor/github.com/docker/go-connections/tlsconfig/config.go
github.com/docker/infrakit/vendor/github.com/docker/go-connections/tlsconfig/certpool_other.go
github.com/docker/infrakit/vendor/github.com/docker/go-connections/tlsconfig/certpool_go17.go
github.com/docker/infrakit/vendor/github.com/Sirupsen/logrus/json_formatter.go
github.com/docker/infrakit/vendor/github.com/Sirupsen/logrus/doc.go
github.com/docker/infrakit/vendor/github.com/thebsdbox/go-tftp/server/readreq.go
github.com/docker/infrakit/vendor/github.com/thebsdbox/go-tftp/server/server.go
github.com/docker/infrakit/vendor/github.com/thebsdbox/go-tftp/server/writereq.go
github.com/docker/infrakit/pkg/broker/server/sse.go
github.com/docker/infrakit/pkg/broker/server/interceptor.go
github.com/docker/infrakit/pkg/util/docker/docker.go
github.com/docker/infrakit/pkg/launch/os/os_windows.go
github.com/docker/infrakit/pkg/launch/os/os_unix.go
github.com/docker/infrakit/pkg/plugin/instance/file/plugin.go
github.com/docker/infrakit/pkg/plugin/resource/plugin.go
github.com/docker/infrakit/pkg/provider/terraform/instance/cmd/main.go
github.com/docker/infrakit/pkg/provider/terraform/instance/plugin.go
github.com/docker/infrakit/pkg/provider/terraform/instance/apply.go
github.com/docker/infrakit/pkg/provider/ibmcloud/plugin/instance/volumeauthplugin.go
github.com/docker/infrakit/pkg/provider/docker/plugin/instance/instance.go
github.com/docker/infrakit/pkg/provider/vagrant/plugin/instance/instance.go
github.com/docker/infrakit/pkg/provider/google/plugin/group/plugin.go
github.com/docker/infrakit/pkg/provider/google/plugin/metadata/plugin.go
github.com/docker/infrakit/pkg/provider/digitalocean/plugin/instance/plugin.go
github.com/docker/infrakit/pkg/provider/oracle/client/core/subnet.go
github.com/docker/infrakit/pkg/provider/oracle/client/core/instance.go
github.com/docker/infrakit/pkg/provider/oracle/client/core/virtual_nic_attachment.go
github.com/docker/infrakit/pkg/provider/oracle/client/core/virtual_nic.go
github.com/docker/infrakit/pkg/provider/oracle/client/core/security_list.go
github.com/docker/infrakit/pkg/provider/oracle/client/core/virtual_network.go
github.com/docker/infrakit/pkg/provider/oracle/client/loadbalancer/certificate.go
github.com/docker/infrakit/pkg/provider/oracle/client/loadbalancer/backend.go
github.com/docker/infrakit/pkg/provider/oracle/client/loadbalancer/load_balancer.go
github.com/docker/infrakit/pkg/provider/oracle/client/loadbalancer/health_checker.go
github.com/docker/infrakit/pkg/provider/oracle/client/loadbalancer/backend_set.go
github.com/docker/infrakit/pkg/provider/oracle/client/loadbalancer/listener.go
github.com/docker/infrakit/pkg/provider/oracle/client/api/http_client.go
github.com/docker/infrakit/pkg/provider/oracle/client/api/client.go
github.com/docker/infrakit/pkg/provider/oracle/client/bmc/error.go
github.com/docker/infrakit/pkg/provider/oracle/client/bmc/config.go
github.com/docker/infrakit/pkg/provider/libvirt/plugin/instance/instance.go
github.com/docker/infrakit/pkg/provider/aws/experimental/bootstrap/cmd/infrakitctl/main.go
github.com/docker/infrakit/pkg/provider/aws/experimental/bootstrap/destroy.go
github.com/docker/infrakit/pkg/provider/aws/experimental/bootstrap/create.go
github.com/docker/infrakit/pkg/provider/aws/experimental/bootstrap/cli.go
github.com/docker/infrakit/pkg/provider/aws/experimental/bootstrap/formatter.go
github.com/docker/infrakit/pkg/provider/aws/plugin/loadbalancer/elb.go
github.com/docker/infrakit/pkg/provider/aws/plugin/instance/monitor.go
github.com/docker/infrakit/pkg/provider/aws/plugin/instance/autoscaling_autoscalinggroup.go
github.com/docker/infrakit/pkg/provider/aws/plugin/instance/ec2_spot_instance.go
github.com/docker/infrakit/pkg/provider/aws/plugin/instance/ec2_instance.go
github.com/docker/infrakit/pkg/provider/rackhd/plugin/instance/cmd/main.go
github.com/docker/infrakit/pkg/provider/rackhd/plugin/instance/instance.go
github.com/docker/infrakit/pkg/cli/logging.go
github.com/docker/infrakit/pkg/log/log.go
github.com/docker/infrakit/pkg/rpc/event/client.go
github.com/docker/infrakit/pkg/store/swarm/swarm.go
github.com/golang/dep/gps/solve_bimodal_test.go
github.com/LK4D4/vndr/test/testdata/dumbproject/pkg1/pkg.go
github.com/grafana/grafana/vendor/github.com/inconshreveable/log15/doc.go
github.com/rancher/trash/trash_test.go
github.com/rancher/trash/util/util.go
github.com/rancher/trash/trash.go
github.com/rancher/trash/conf/conf.go
github.com/rancher/trash/vendor/github.com/Sirupsen/logrus/json_formatter.go
github.com/rancher/trash/vendor/github.com/Sirupsen/logrus/doc.go

ag -sl 'github.com/sirupsen/logrus' -G .go$ .
github.com/appcelerator/amp/cmd/amplifier/server/configuration/configuration.go
github.com/appcelerator/amp/cmd/amplifier/server/server.go
github.com/appcelerator/amp/cmd/amplifier/main.go
github.com/appcelerator/amp/cmd/agent/main.go
github.com/appcelerator/amp/cmd/gateway/main.go
github.com/appcelerator/amp/docker/docker/registry/config.go
github.com/appcelerator/amp/docker/docker/registry/service.go
github.com/appcelerator/amp/docker/docker/registry/auth.go
github.com/appcelerator/amp/docker/docker/registry/session.go
github.com/appcelerator/amp/docker/docker/registry/registry.go
github.com/appcelerator/amp/docker/docker/registry/resumable/resumablerequestreader.go
github.com/appcelerator/amp/docker/docker/registry/endpoint_v1.go
github.com/appcelerator/amp/docker/docker/pkg/term/windows/windows.go
github.com/appcelerator/amp/docker/docker/pkg/system/syscall_windows.go
github.com/appcelerator/amp/docker/cli/cli/flags/common.go
github.com/appcelerator/amp/docker/cli/cli/compose/loader/loader.go
github.com/appcelerator/amp/docker/cli/cli/command/events_utils.go
github.com/appcelerator/amp/docker/cli/cli/command/inspect/inspector.go
github.com/appcelerator/amp/docker/cli/cli/command/out.go
github.com/appcelerator/amp/agent/config.go
github.com/appcelerator/amp/agent/api.go
github.com/appcelerator/amp/agent/logs.go
github.com/appcelerator/amp/agent/agent.go
github.com/appcelerator/amp/agent/container.go
github.com/appcelerator/amp/api/rpc/cluster/cluster.go
github.com/appcelerator/amp/api/rpc/object_store/object_store.go
github.com/appcelerator/amp/api/rpc/config/config.go
github.com/appcelerator/amp/api/rpc/logs/logs.go
github.com/appcelerator/amp/api/rpc/secret/secret.go
github.com/appcelerator/amp/api/rpc/stack/stack.go
github.com/appcelerator/amp/api/rpc/account/account.go
github.com/appcelerator/amp/api/rpc/service/service.go
github.com/appcelerator/amp/api/rpc/resource/resource.go
github.com/appcelerator/amp/data/storage/etcd/store.go
github.com/appcelerator/amp/data/storage/etcd/watcher.go
github.com/appcelerator/amp/data/accounts/store.go
github.com/appcelerator/amp/data/accounts/authz.go
github.com/appcelerator/amp/pkg/docker/service.go
github.com/appcelerator/amp/pkg/docker/stack.go
github.com/appcelerator/amp/pkg/nats-streaming/nats-streaming.go
github.com/appcelerator/amp/pkg/cloud/provider.go
github.com/appcelerator/amp/pkg/cloud/aws/aws.go
github.com/golang/dep/gps/solve_bimodal_test.go
github.com/golang/dep/gps/vcs_version_test.go
github.com/golang/dep/gps/manager_test.go
github.com/golang/dep/gps/solve_failures.go

makes me think we should add dep in our gotools image and run it with ampmake to avoid any environmental impact.

@ndegory yeah, adding dep to our build tools could fix your issue. Please open a ticket.

now that the branch is rebased on master with the ampmake target for vendor installation, I still have the issue:
(vendor ✗) rm -rf $GOPATH/pkg/
(vendor ✗) mkdir $GOPATH/pkg/
(vendor ✗) ampmake install-vendor
Using existing GOPATH: REDACTED
ensure Solve(): No versions of github.com/docker/distribution met constraints:
edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c: Could not introduce github.com/docker/distribution@edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c due to a case-only variation: it depends on "github.com/sirupsen/logrus", but "github.com/Sirupsen/logrus" was already established as the case variant for that project root by depender (root)
v2.6.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
v2.6.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
v2.6.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
v2.5.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
v2.5.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
v2.5.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
v2.4.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
v2.4.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
v2.3.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
v2.3.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
v2.2.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
v2.2.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
v2.1.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
v2.1.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
v2.0.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
v2.0.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
v2.6.1-rc.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
v2.6.1-rc.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
v2.6.0-rc.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
v2.6.0-rc.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
v2.5.1-rc.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
v2.5.0-rc.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
v2.5.0-rc.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
v2.4.1-rc.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
v2.4.1-rc.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
v2.4.1-rc.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
v2.4.0-rc.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
v2.4.0-rc.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
v2.3.1-rc.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
v2.3.0-rc.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
v2.3.0-rc.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
v2.3.0-rc.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
v2.3.0-alpha: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
v2.1.0-rc.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
v2.0.0-rc.4: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
v2.0.0-rc.3: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
v2.0.0-rc.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
v2.0.0-rc.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
v2.0.0-rc.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
v2.0.0-alpha.3: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
v2.0.0-alpha.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
v2.0.0-alpha.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
v2.0.0-alpha.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
master: Could not introduce github.com/docker/distribution@master, as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
aws-vendor-update: Could not introduce github.com/docker/distribution@aws-vendor-update, as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
docker/1.10: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
docker/1.10-dev: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
docker/1.13: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
docker/1.8: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
docker/1.9: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
feature_dyn_plugin: Could not introduce github.com/docker/distribution@feature_dyn_plugin, as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
release/2.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
release/2.0-image-validation-stopgap: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
release/2.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
release/2.3: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
release/2.4: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
release/2.5: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
release/2.6: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
test-go-1.8-rc: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
docs-v2.4.1-2016-06-01: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
docs-v2.4.1-2016-06-28: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
docs-v2.5.0-2016-07-28: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c from project docker.io/go-docker.
make: *** [Makefile:82: install-vendor] Error 1

Working great now with the --vendor-only.


chore: Spelling

@jsoref Thanks a lot for the PR. This is awesome. Can you please approve the Contributor Agreement?

Or

I was able to sign it using a desktop browser, but please get someone to fix the flow so that it doesn't require one.

@jsoref Sorry to hear that. I have escalated the issue to the team that is in charge of the OCA app.

Fwiw, I actually hit a bunch of other errors including things that looked like capacity issues or general outages.
There's no particular indication of what to actually expect going forward. At this time, my thing just says "Under review".

@jsoref Looks like your commits are not signed. Can you please sign them and also include the Signed-off-by: line?

Do you mean GPG signed? That's a bridge too far (the number of hoops and stumbling blocks for this project is absurd). I have an expired signature from 2018 and this is the first project to demand that since it expired.
I have an ssh signing key added in 2022 that I'd be willing to use.
Plus, you merged #613 w/o requiring that.
None of these changes should even require concern about (c) as they're all trivial.

We have turned on a check on GitHub to verify commit signatures. As long as that check passes, it's good. Note that the check has passed for your other PR:

But the commits on this PR are missing the verified green tick for some reason.

I think the check just needs to be rerun.
It also should be improved so that you can easily determine what it's actually complaining about.

Oh, your docs are wrong. That commit was signed w/ an ssh signature:

Sure, I can do that here. But you should fix the docs to clarify what it actually tolerates (either "whatever github tolerates" or "gpg / ssh" if it's specifically picky)

Sure, I can do that here. But you should fix the docs to clarify what it actually tolerates (either "whatever github tolerates" or "gpg / ssh" if it's specifically picky)

Thanks for the suggestion. I have created an issue for it.

@jsoref The commits are now signed and the GitHub check passes, thanks. There is only one comment left by @benmss that needs to be addressed.

hi @jsoref, We apology for the inconvenience you've experienced while signing an OCA, and are working on fixing these issues.


feat: add miniflux

The PR add a new application miniflux for my RSS feeds.
Note: also remove unused immich-typesense resources

There is a lost of miniflux Kustomization in boostrap file.


(SERVER-1153) Handle superfluous --gzip if-none-match header characters

This commit strips the characters "--gzip" from the end of an
'If-None-Match' HTTP header value when comparing the value to that of
the last etag stored for the environment_classes cache.  Previously, no
special compensation for these characters was being done.  This had led
to failures matching up the supplied 'If-None-Match' header value to
that of the last stored value, in cases where the Jetty web server was
appending the "--gzip" characters to the etag value as it delivered a
gzipped response body to a prior environment_classes request.

@camlow325 this looks good to me, but I'm wondering if it would be possible / worthwhile to have a test that explicitly forces a payload that exceeds the gzip size, validates that the response is gzipped, and validates that sending the etag from that response back up to the server will result in a 304?  If we think it's worthwhile to write such a test, it could be targeted at just your middleware thing, so the test would only need to spin up Jetty and a simple ring handler that uses that middleware, as opposed to spinning up the full server stack and doing an environment_classes request.
I guess I'm thinking that even if you do think that is a good idea, we shouldn't block this PR on it, so, I'm +1.

@cprice404 I can try doing that.  Although there are no guarantees that Jetty behavior won't change to have a different size threshold for when it starts gzipping the response in the future.  I'll give it a shot.

@camlow325 ok, but if we get a second review on this ( @rlinehan ? ) before you're done with that, we should go ahead and merge this just to make sure it's not impacting the NC team.

@cprice404 I added another integration test in 6bf7f96 which hopefully achieves what you were suggesting.  The test just includes a wrap-with-etag-check middleware and some surrounding mocks / backing ring middleware which returns a large response body - 200000 characters - to more explicitly trigger gzip encoding.  It's hard to predict for sure that gzip encoding will be "guaranteed" to happen if we were to upgrade to a newer Jetty web server version which might have different rules than the ones today around when gzipping occurs.  If that were the case, though, hopefully it wouldn't be too tough to adapt this test to whatever new rules we might encounter.

@camlow325  thanks for adding the test, that seems valuable to me.
+1

+1 ; @rlinehan please feel free to merge when you see fit.

:shipit:


Add ApiBlock Dashboard

Overview
Adds the ApiBlock list view and the ApiBlock update view. Users can
view and update the ApiBlocks' grace_limit and grace_reason.
The list view displays active, not expired blocks in one table at the
top, and the rest of the blocks in another table. The full list of
blocks is filterable by contributor. This filter is client-side only.
Connects #1144
Demo

Testing Instructions

Run ./scripts/server
Ensure you have at least one active and one inactive Api Block in your database.
Navigate to :6543/dashboard.
Click on 'View API Blocks'
You should be navigated to the API Block list. The top list should include only active, unexpired blocks.
The bottom list should include all the blocks you have in your database.
You should be able to filter the bottom list by contributor.
Click on an active block in the top list. You should be taken to the update view.
Enter a grace limit above the actual count and request limit. Enter a grace reason. Click submit.
The ApiBlock should be updated.
Return to the list by clicking the 'back to Api Blocks' button. You should see the ApiBlock was updated here as well.
Go to an active block's update page. Attempt to enter a grace limit below the actual count or request limit. You should see an error.

Checklist

[ ] fixup! commits have been squashed
[ ] CI passes after rebase
[ ] CHANGELOG.md updated with summary of features or fixes, following Keep a Changelog guidelines

Sorry for the delay. Looking at this now.


Add "event" to glossary

Resolves #31291
This PR adds "event" to Reference Glossary

/lgtm

Awaiting another sig docs reviewer/approver to sign off these changes.

Thank you @sftim. I have made the changes

Thanks
/lgtm

/lgtm

LGTM!

/approve


Store and CLI have a circular dependency

This file  will cause issues for the following tasks

implementing pnpm
implementing any tool that relies on topological order

I'm also surprised it's not currently causing issues for lerna or tests
This is because it is causing a circular dependency between state package and cli package.  I don't have context on why this file exists so I wanted to ask which of the following is best in order of easiest to hardest:

Delete the file - it isn't necessary
Move whatever is using this file either to a new package or somewhere else in general
Export storeConfig from state instead of from cli
extract common code from both state and cli into  a private internal package consumed by both

mud.config.mts defines the autogeneration of store's tables (basically everything in src/tables folder), so it has to stay in there.
Extracting config types/parsers/loaders (not sure about loaders) from cli, so that store, cli and other consumers import a config package would make sense, I think @holic had already suggested it

See https://github.com/latticexyz/mud/pull/589

Closing in favor of https://github.com/latticexyz/mud/issues/616


[Feature] Anime/Manga reviews.

Can we have a route for fetching the given anime/manga's reviews? Also, fetch reviews for a specific user?

Both of these are planned features in the parser: https://github.com/jikan-me/jikan/projects/4
Will get to implementing them soon.

Added! /v3/{anime|manga}/{id}/reviews/{page}
More info here: https://jikan.docs.apiary.io/#reference/0/anime
https://jikan.docs.apiary.io/#reference/0/manga
User Reviews are yet to be added, I've opened up a new issue for it: https://github.com/jikan-me/jikan-rest/issues/36


ONNX conversion error in latest gliner version 0.2.10

/usr/local/lib/python3.10/dist-packages/gliner/modeling/base.py in extract_prompt_features_and_word_embeddings(config, token_embeds, input_ids, attention_mask, text_lengths, words_mask, **kwargs)
53
54     max_embed_dim = num_class_tokens.max()
---> 55     max_text_length = text_lengths.max()
56     aranged_class_idx = torch.arange(max_embed_dim,
57                                         dtype=attention_mask.dtype,
AttributeError: 'NoneType' object has no attribute 'max'
But working with the earlier versions of gliner

I was facing the same problem, try to install gliner==0.2.5 onnx==1.16.2.
It works now


Remove some sleeps from test suite

Checklist

[ ] Affected Issues have been mentioned in the Closing issues section
[ ] Documentation has been written/updated
[x] PR title is ready for changelog and subsystem label(s) applied

This change makes local test iterations much faster. However I don't know if there is another reason for these sleeps to be there @tobybellwood?
Closing issues
n/a

ah - random-wait was the successor to the 30s sleep - so that can go.  My experience was that the fastest tests off the mark (nginx, node, python) would fail if they triggered immediately - and the 30s massively reduced that risk.
The random wait is to avoid the tests (when running multiple) crashing into each other as much and spread them out a little between 30s-120s.  Of course, the errors will still happen (because of the other keycloak issue)

OK I re-added the random waits in the test as discussed.


Extraction of Pressure surfaces (Surf154) with pyDPF

Description of the feature
Hello,
is there a feature that extracts the pressure surfaces from a model ?
It seems that I can get le pressure named selection with metadata.meshed_region..available_named_selections (as an '__LV_223__SELECTION' for instance), but when I acces the elements IDs and try to find each element in the mesh, they do not exist.
I see in the ds.dat file that the selection corresponds to a Surf154 (quad8) defined from pressure loading, but through pyDPF I can not find such elements.
Thanks in advance.
Louise Ramos
Steps for implementing the feature
No response
Useful links and references
No response

Hello @Louise-Ramos,
To clarify, do you want to extract the pressure field on a given named selection?
What I understand here is that in this case it is a pressure load applied in MAPDL via specific load elements, is that correct?
If the named selection is returned by Meshed_region.available_named_selections, then it should be available.
Can you try using MeshedRegion.named_selection() to get the scoping for the named selection, and then see if it is empty.
In any case I do not think you will see any mention of Surf154 in DPF, but what you can do is look for 154 in the data returned when asking for [MeshedRegion.property_field("apdl_element_type")].(https://dpf.docs.pyansys.com/version/dev/api/ansys.dpf.core.meshed_region.html#ansys.dpf.core.meshed_region.MeshedRegion.property_field)

Hello @PProfizi,
I want to extract the elements used for the pressure loading, or the scoping used to the pressure.
The named selection is returned and is filled with 200 elements, but when I do extract the IDs  from the selection, I can't find them in my meshed_region. In other words, I use a code such as the following to my test:
rst = Model('file.rst')
metadata = rst.metadata;
ansys_mesh = metadata.meshed_region;

print(ansys_mesh.available_named_selections) **Used to identify the '__LV_223__SELECTION' elemental selection **
print(metadata.named_selection(('_LV_227__SELECTION')).location, metadata.named_selection(('__LV_223__SELECTION')).size) ** returns  :' Elemental 248'
selection_Ids = metadata.named_selection('__LV_223__SELECTION').ids

for idel in selection_Ids :
      print(idel)
     Mesh_Element_Conn = ansys_mesh.elements.element_by_id(idel).connectivity ** Getting the connectivity of the points from the element with ID = idel **

I have the following error message:
Traceback (most recent call last):
File "C:\Users\s628156\AppData\Roaming\JetBrains\PyCharmCE2022.3\scratches\scratch.py", line 24, in
print(idel , ansys_mesh.elements.element_by_id(idel).connectivity)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\s628156\PycharmProjects\pythonProject\venv\Lib\site-packages\ansys\dpf\core\elements.py", line 283, in element_by_id
return self.__get_element(elementid=id)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\s628156\PycharmProjects\pythonProject\venv\Lib\site-packages\ansys\dpf\core\elements.py", line 445, in __get_element
num_nodes = self._mesh._api.meshed_region_get_num_nodes_of_element(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\s628156\PycharmProjects\pythonProject\venv\Lib\site-packages\ansys\dpf\gate\generated\meshed_region_capi.py", line 226, in meshed_region_get_num_nodes_of_element
raise errors.DPFServerException(sError.value)
ansys.dpf.gate.errors.DPFServerException: element not found
I checked the elements in my mesh, and there are only these two: [187 281]. Still, the selection does not seems to be defined by the mesh elements.
Is that a bug ?
Thanks in advance,


Add references to possible discussions about upstreaming this

For someone who haven't followed the history of tsd it would be neat to have it documented here why these methods hasn't been exposed upstream – if there's eg. an opposition from the TypeScript team to them or if there's something else blocking it.
I guess long term goal is to not have to maintain a fork like this?
(Also: Sorry for jumping on here with an issue this quickly, I understand it might be premature, not trying to stress you out or anything, just want to be helpful 🙂)

Hi @voxpelli! No worries, I would be definitely up for it to have this exposed upstream.
Working on automating the build/release process to have a cronjob run every couple of hours checking if we need to release a new version. This would make it much easier for tsd to follow the TypeScript release cycle. But it's definitely not ideal, because it requires a separate typescript dependency. Although this is actually a drop-in replacement for typescript, people will probably not use it like that.

Hello @SamVerschueren @voxpelli
I would also like to see these methods exposed by TypeScript directly and I'm not sure why they aren't. For several reasons, but in particular because I needed a solution that mixed tsd-typescript and byots quickly I developed my own solution unleashed-typescript I do not maintain a TypeScript fork. Instead I use the user installed package, make a copy, patch it and export it back.

One of these methods will become official in 3.4: https://github.com/microsoft/TypeScript/pull/56448
And to answer my own question I asked in the start of this issue: This is the thread that discusses exposing these methods in unmodified TS: https://github.com/microsoft/TypeScript/issues/9879


Composer v2 allow-plugins requirement. The helper "question" is not defined.

PHP Version
7.4.27
Shopware Version
<IP_ADDRESS>
Expected behaviour
Expected bin/console system:install --drop-database --basic-setup --force command to complete on Shopware docker image.
Actual behaviour
Error appears. Seems like when it's running plugin:refresh stage of the system:install CLI command.
Shopware Plugin Service
=======================

<warning>bamarni/composer-bin-plugin contains a Composer plugin which is currently not in your allow-plugins config. See https://getcomposer.org/allow-plugins</warning>

The helper "question" is not defined.

How to reproduce
TLDR; Fix
composer install --non-interactive command creates the issue.
Composer 2 new requires that plugins that have executable code need to be explicitly allowed in composer.json.
Assumingely acceptable fix:
        "allow-plugins": {
            "bamarni/composer-bin-plugin": true,
            "phpstan/extension-installer": true
        }

Reproduce
Steps 1-2 are tentative, maybe some adjustments may need to be done for your environment.

Create docker-compose.yml

version: "3"
services:
  sw-dev:
    image: shopware/development:7.4-composer-2
    ports:
      - "80:80"
    networks:
      - sw-dev-web
  sw-dev-mysql:
    container_name: database
    image: mysql:5.7
    ports:
      - "3306:3306"
    networks:
      - sw-dev-web
    environment:
      MYSQL_DATABASE: root
      MYSQL_ROOT_PASSWORD: root

networks:
  sw-dev-web:
    external: false

docker-compose up -d
docker ps - this is for next command
docker exec -it [CONTAINER_ID] /bin/bash
git clone https://github.com/shopware/platform.git . --branch <IP_ADDRESS> - I tested on <IP_ADDRESS> previously as well. Same issue.
composer install -n - yes, non-interactive mode. If interactive, the issue will be apparent, it asks to allow running of plugins. But not interactive mode (e.g. for CI) will silently fail to run the code which will produce the problem mentioned here.

Is already fixed in trunk

https://github.com/shopware/platform/commit/e5e35163fb10aee7ec452baed5fa93e602c3389a
https://github.com/shopware/platform/commit/2db360a578d48037469fb91b730cff9265454862

You can add a conflict for composer/composer 2.2 in your root composer.json to avoid this problem

I pinned the issue if anyone else have this issue as well

oh wow. My bad. I think I was looking for "open" issues when doing my search for duplicates.


Karma Plugin Error while running ng test from maven in Angular 6

I am using front end maven plugin to run unit tests in Angular.
Angular 6 version is being used
Below is the configuration -
karma.conf.js :
module.exports = function (config) {
  config.set({
    basePath: '',
    frameworks: ['jasmine', '@angular-devkit/build-angular'],
    plugins: [
      require('karma-jasmine'),
      require('karma-chrome-launcher'),
      require('karma-jasmine-html-reporter'),
      require('karma-coverage-istanbul-reporter'),
      require('@angular-devkit/build-angular/plugins/karma')
    ],
    client: {
      clearContext: false browser
    },
    coverageIstanbulReporter: {
      dir: require('path').join(__dirname, '../../coverage'),
      reports: [ 'html', 'lcovonly', 'text-summary' ],
      fixWebpackSourcePaths: true
    },
    angularCli: {
      environment: 'dev'
    },
    reporters: ['progress', 'kjhtml'],
    port: 9876,
    colors: true,
    logLevel: config.LOG_INFO,
    autoWatch: true,
    browsers: ['Chrome'],
    singleRun: false,
    restartOnFileChange: true,
	browserNoActivityTimeout: 100000
  });
};

pom.xml :
<execution>
	<id>test</id>
	<goals>
			<goal>karma</goal>
	</goals>
	<phase>test</phase>
	<configuration>
		<karmaConfPath>karma.conf.js</karmaConfPath>
		<arguments>--code-coverage</arguments>
	</configuration>
</execution>

I am getting below error when I run - mvn clean install
Server start failed on port 9876: Error: The '@angular-devkit/build-angular/plugins/karma' karma plugin is meant to be used from within Angular CLI and will not work correctly outside of it.
I have researched a bit and found below links but I havent yet found any solution.
https://github.com/angular/angular-cli/issues/10703#issuecomment-387319138
Please not that we have to do this from maven only
Can anybody please help here as I am struggling to get this running ?

Hello, we reviewed this issue and determined that it doesn't fall into the bug report or feature request category. This issue tracker is not suitable for support requests, please repost your issue on StackOverflow using tag angular-cli.
If you are wondering why we don't resolve support issues via the issue tracker, please check out this explanation.

Hi,
Thanks for prompt  response.
I opened an issue on stack overflow already as
https://stackoverflow.com/q/60989118/1281182
Regards,
Atul
On Thu, 2 Apr 2020, 17:10 Alan Agius<EMAIL_ADDRESS>wrote:

Hello, we reviewed this issue and determined that it doesn't fall into the
bug report or feature request category. This issue tracker is not suitable
for support requests, please repost your issue on StackOverflow
http://stackoverflow.com/ using tag angular-cli.
If you are wondering why we don't resolve support issues via the issue
tracker, please check out this explanation
https://github.com/angular/angular-cli/blob/master/CONTRIBUTING.md#-got-a-question-or-problem
.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/angular/angular-cli/issues/17370#issuecomment-607793365,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE5YRWA3MITOFUPI272QAS3RKR2UVANCNFSM4L2IILEQ
.


Nothing happens

When i type something, it sometimes fetches /api/tags endpoint but nothing seems to be working
Llama Coder shows as loading and there are no logs whatsoever.

Same here


single file change for to sql and from sql plugin

Notes:

I know this will be rejected since this is close contribution
I've updated this from the prs so all you have to do is update the plugin src/main/webapp/plugins/sql.js file to install it locally.
I'm aware that using a native tool for your db may be better for uml diagrams.
There are many workflows that this works, you can do code share from vscode for collaboration after importing your drawio file from a sql table schema export
setup see wiki from branch https://github.com/lastlink/drawio/wiki/Getting-Started
It's easiest to setup in the drawio desktop, to use the plugin https://github.com/jgraph/drawio-desktop

git clone --recursive https://github.com/jgraph/drawio-desktop.git 1 gb clone btw
npm install
update drawio/src/main/webapp/plugins/sql.js with changes from branch
npm start run application
add plugin in Extras > Plugins > Add select sql
close application and reopen. Plugin is installed

you can find the menu buttons in File > Export As > To SQL or Arrange > Insert > From SQL

References

#3083, #3092, #3091

We'll look into whether an exception can be made here as it's a significant amount of work to be rejected.

I ran through this process but the To SQL option was not showing up on the menu

@steel198513 try looking in File > Export As

@karthiart did you pull/copy the updates for the file from this pr? Otherwise you won't have my changes.

@lastlink Thanks for your response. If you don't mind, can you let me know how to implement it from this pr? Because i dont know how to do these below steps.
It's easiest to setup in the drawio desktop, to use the plugin https://github.com/jgraph/drawio-desktop

git clone --recursive https://github.com/jgraph/drawio-desktop.git 1 gb clone btw

npm install

update drawio/src/main/webapp/plugins/sql.js with changes from branch

npm start run application

When i did npm start. I am getting this attached error message. Any help?

Thanks for making this available.  I was just coming to post some changes that allowed [Spaces in Column Names] to get parsed correctly but yours is so much more robust.
I wanted to share for others coming to this that want just the functionality, but aren't too comfortable with code.  You can get a local copy of the plugin if you modify your draw.io desktop shortcut to include a --enable-plugins, e.g. edit your start menu shortcut to be "C:\Program Files\draw.io\draw.io.exe" --enable-plugins.  Then when you do the 'add' under the "Extras -> Plugins" menu there will be an option to add a file from disk instead, and you just need to save a 'raw' copy of the 'sql.js' file included here and restart your program to get access to all this functionality.

We'll look into whether an exception can be made here as it's a significant amount of work to be rejected.

That would be awesome! Importing schema with FK relationship connectors is a really useful feature in Lucid and I'd love to see it here. Great work, @lastlink !

Thanks for making this available. I was just coming to post some changes that allowed [Spaces in Column Names] to get parsed correctly but yours is so much more robust.
I wanted to share for others coming to this that want just the functionality, but aren't too comfortable with code. You can get a local copy of the plugin if you modify your draw.io desktop shortcut to include a --enable-plugins, e.g. edit your start menu shortcut to be "C:\Program Files\draw.io\draw.io.exe" --enable-plugins. Then when you do the 'add' under the "Extras -> Plugins" menu there will be an option to add a file from disk instead, and you just need to save a 'raw' copy of the 'sql.js' file included here and restart your program to get access to all this functionality.

This worked great, thanks @ChrisNolan

Steps for running external plugin on mac https://github.com/ariel-bentu/tam-drawio/blob/main/mac-pass-arg.md

You can run in vscode drawio extension as well.
settings.json
  "hediet.vscode-drawio.plugins": [
    {
      "file": "<path>\\plugins\\sql.js"
    }
  ],

I'm no longer maintaining this pr, but I've made a separate repo for the plugin. I've added support for vscode drawio plugin compatibility.
See:

https://github.com/funktechno/sqltooling-drawio/tree/main and
sql.js


New characters, weapons and uncaps

I added the new characters, weapons and uncaps. I also fixed the scarlet vane skill name and updated some outdated values for some 5* characters.

Thanks for the updates!
(Sorry for late response, it will be merged tomorrow!)

Will try to overhaul the SSR weapon data (found some old missing uncaps) and try to prepare some experimental character edits for the announced rebalance update, over the next days.


upgrade fabric8

upgrade fabric8

Refer to this link for build results (access rights to CI server needed):
https://fabric8-ci.fusesource.com/job/jube-master-pullreq/185/
Test PASSed.


Allow uninitialized scenes to be used as sources

Seems to work in tests, might need more testing with extra scene items

Works reliably in tests and in Memedows, will revisit in future if there really are problems.


[Improvement] Optimize the configuration of the number of threads of Netty client

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Search before asking

[X] I have searched in the issues and found no similar issues.

What would you like to be improved?
Currently, Uniffle client will create an EventLoopGroup for each shuffle server, which is named workerGroup. And the default number of the threads of workerGroup is availableProcessors and it can be changed by rss.client.netty.client.threads. And each thread of  workerGroup  will create an EventExecutor, which will occur lots of memory.
https://github.com/apache/incubator-uniffle/blob/d170004a32418a32536aa792b198dfd714b5ea8c/common/src/main/java/org/apache/uniffle/common/netty/client/TransportClientFactory.java#L88
But the param rss.client.netty.client.connections.per.peer, which with 2 as the default value, will de determine the max threads in workerGroup will be used. So, many threads are useless in the default configuration.
https://github.com/apache/incubator-uniffle/blob/d170004a32418a32536aa792b198dfd714b5ea8c/common/src/main/java/org/apache/uniffle/common/netty/client/TransportClientFactory.java#L127-L133
How should we improve?
Remove rss.client.netty.client.threads and make rss.client.netty.client.connections.per.peer as the param of the thread number of workerGroup.
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

@zuston @xumanbu @rickyma @jerqi  cc

Sounds good


Implementation of the task handler, 1-st ver.

The branch add-task_handler include in itself an implementation of simple plans organizer.
Organizer is capable of:

Add the new task or plan for a certain day.
2.Copy the all tasks from one day to another.
3.Delete the all saved tasks for a certain day.
4.Display the all appointed tasks for a certain day.
Also project provides protection against incorrect user input.

..handler, ver. 1.0 perceived better!

Thank you for advise.


Clarify hot-reload vs Runtime compilation?

I am a bit confused,
Before .NET 6 I would add Runtime compilation to get the "hot reload" experience, being to make changes to my views and see the response directly in my browser.
But now with HotReload, when would I want to add Runtime compilation? Is if if I want to allow changes in production??
So, what I would like to see is more clear guidance, on when to add RuntimeCompilation and when to just be happy with the HotReload feature.
Also, relevant, the old browser-link concept, is that dead? or is that still supported and used?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 8a83deb2-e035-bb66-be4f-68709bcad341
Version Independent ID: 16438f35-f35d-c097-0903-ec17e83e051e
Content: Razor file compilation in ASP.NET Core
Content Source: aspnetcore/mvc/views/view-compilation.md
Product: aspnet-core
Technology: aspnetcore-mvc
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

Associated WorkItem - 67058

https://github.com/dotnet/AspNetCore.Docs/issues/23910#issuecomment-1033107013


Gamelistdb

Hi!
Is it possible to separate PCENGINE in 2 platoforms ?
1/ pcengine / TurboGrafx 16
2/ pce-cd / TurboGrafx CD
The games are not registed on the same platform on thegamesdb.
Gugue

canceled


Update Module-5-Improving-your-Secure-Posture.md

Adding Exercise 5: Creating Governance Rules and Assigning Owners

Added Section 5


Type parameter which extends Partialed tuple is not assignable to rest args

Bug Report

🔎 Search Terms

type inference, partial, tuple, rest
🕗 Version & Regression Information

tested for every 4.x releases
⏯ Playground Link

Playground link with relevant code
💻 Code

type RestArgs<T extends (...args: any[]) => any, U extends any[]> = Parameters<
  T
> extends [...U, ...(infer P)]
  ? P
  : [];

const bind = <
  T extends (...args: any[]) => any,
  U extends Partial<Parameters<T>>
>(
  fn: T,
  thisArg: any,
  ...params: U // A rest parameter must be of an array type.
) => {
  return function (...innerArgs: RestArgs<T, U>): ReturnType<T> {
    const fnKey = Symbol();
    thisArg[fnKey] = fn;
    const result = thisArg[fnKey](...params, ...innerArgs);
    delete thisArg[fnKey];
    return result;
  };
};

function foo(name: string, age: number, addr: string) {}

const runner = bind(foo, null);
runner("", 18, "mars");

🙁 Actual behavior

Type parameter U is not assignable to params. TypeScript compiler complains A rest parameter must be of an array type.
🙂 Expected behavior
TypeScript compiler should not complain about this.
Current workaround
Add & any[] to  U extends Partial<Parameters<T>>, which becomes  U extends Partial<Parameters<T>> & any[], which forces TypeScript to regard it as an array. It works fine, but I'm still wondering if this is a bug.

Partial< isn't a match for what you need here, since it implies the allowance of e.g. objects which lack a length property but have a 3 property and no 0 1 or 2, which is not a valid description of a parameter list.
What you want is something like this, which works like what you're expecting:
// TODO: Convert to fancy recursive version; simpler form demonstrated here
type LeadingOf<T> =
  T extends [infer A] ? [] | [A] :
  T extends [infer A, infer B] ? [] | [A] | [A, B] :
  T extends [infer A, infer B, infer C] ? [] | [A] | [A, B] | [A, B, C] : []

const bind = <
  T extends (...args: any[]) => any,
  U extends LeadingOf<Parameters<T>>
>(

@RyanCavanaugh
Hmm, can we explain why this works?
const bind = <T extends any[], U extends Partial<T>>(
  fn: (...arg: T) => any,
  thisArg: any,
  ...params: U
) => { };

function foo(name: string, age: number, addr: string) { }

bind(foo, null);
bind(foo, null, ""); // okay
bind(foo, null, "", 3); // okay

Seems to be an inconsistency between when Partial<T> is and is not considered arraylike enough for the compiler.


[5.5] Earlier return for Arr::get.

Earlier return for Arr::get.

Doesn't it return false if needle is not found?

I use strpos instead - thx @ntzm


Debian .deb (apt) install

Hi there - I am interested in using this with Elixir and Python code for my work. Since I primarily use Ubuntu, I'd like to try doing a a debian .deb build script.
I see that currently there is only the Mac Homebrew install - what exactly does the homebrew install do? I can likely replicate what it's doing for Debian/Ubuntu linux platforms, if someone can point me to the Homebrew install scripts, or just let me know what the Homebrew install does.
Thanks!

Hi @justinmichaelvieira thanks for your interest!
While I haven't worked with Homebrew directly (formula here), I understand it to download the repo, verify the checksum, run the system command (in this case, it uses Rust's cargo package manager), and then run tests to verify behavior.

Hi @justinmichaelvieira thanks for your interest!
While I haven't worked with Homebrew directly (formula here), I understand it to download the repo, verify the checksum, run the system command (in this case, it uses Rust's cargo package manager), and then run tests to verify behavior.


Tutorial still unavailable

#13 proposed a tutorial for deis and was closed. Today there's still no clear documentation on how to start using deis after having a controller deployed. I believe it should be once again evaluated.

This is something which we don't plan on getting to in the near future. We have "quick start" documentation on getting set up with Deis, then docuementation on using buildpacks and dockerfiles which should cover the tutorial. We also have screencasts available to see the deployment process at http://deis.io/overview/. Thanks!


Fix variable terraform.tfvars.sample

Fix templates vars

Many thanks for spotting this, and sending a PR!
Fixes #1260


Use a dedicated Redis server for testing

#113

I can use the redis setup code as in #110 to migrate other tests to use dedicated server. I can take this up!


Update kubernetes dependencies to 1.12

@BugRoger Any thoughts and prayers?

still valid. just no time

maybe this is not stale...

Superseeded by #528


Unavailable for install

Hello,
When I try to install it through G Suite Marketplace, I see the following messages:
Unavailable for install
Admin-install only
Am I missing something?

To get around this, you can follow the manual installation steps in the README.md

I've updated the Marketplace configuration to allow individual install.  Thanks for pointing this out!


Missing Userland bcm_host.h

I believe the bcm_host.h is missing within the userland. I tried to compile pngview from raspimx (https://github.com/AndrewFromMelbourne/raspidmx). The compilation failed to locate bcm_host.h.
However pngview compiled successfully on Raspbian.
Run the following on debian-mini-rpi:
$ find /opt/vc -name bcm_host.h
Run the following on Raspbian:
$ find /opt/vc -name bcm_host.h
/opt/vc/include/bcm_host.h

apt-get install libraspberrypi-dev