ztest: add support for assumptions

Is your enhancement proposal related to a problem? Please describe.
In order to avoid repeated asserts in tests it would be better to provide an assume API. This is similar to JUnit.
Describe the solution you'd like
Provide a zassume_* API to mirror the zassert_* API. The API will behave the same as asserts (by stopping the test) but mark the test as skipped instead of failed.
Example
ZTEST(suite, test_initialized)
{
  zassert_false(get_state()->is_initialized, NULL);
  do_something();
  zassert_true(get_state()->is_initialized, NULL);
}

ZTEST(suite, test_operation)
{
  do_something();
  zassume_true(get_state()->is_initialized, NULL);

  do_operation();
  zassert_true(get_state()->is_valid, NULL);
}

In the above example, test_initialized makes sure that do_something() will result in the state's is_initialized to be true. Once that test passes, there's no need to verify the same thing again in another test. In the following test test_operation the call to do_operation() requites initialization to pass first. While it's possible to assert the initialization here, a bug there would fail both tests (making it harder to track down the problem). Alternatively, here, the assume API is used. When the initialization fails, the assumption will fail and stop the test, but instead of reporting a failure, it'll report the test as skipped.

@aaronemassey for implementation


Add support to use $

Can use $ as: {{$ip}}

@pranavwani Apologies, I'm just noticing this now! Would you be able to please add a test that covers this change? Thanks!

This is good. I will add the test. Thanks for this!

@curran Thanks :+1:

@pranavwani Apologies, I'm just noticing this now! Would you be able to please add a test that covers this change? Thanks!

Sorry, about that. Just seen that the test case is not added

My pleasure! Thanks for this contribution. 🙏


Allow CSS selectors to return the full html content, not just the text within it.

The ability to use CSS Selectors were added in:

https://github.com/sibprogrammer/xq/issues/16

Which references the following 2 commits:

https://github.com/sibprogrammer/xq/commit/8dbf6ee9e9fc9d589cf5cfe0a8cc23038706d014
https://github.com/sibprogrammer/xq/commit/35ea9e317ea07bbeed70d97b36b17d31349d3214

The docs show that we can extract content using CSS selectors as follows:
xq -q "body > p"

Yet this seems to return the .innerText equivalent, not the actual HTML structure we're querying.
Looking at the code in internal/utils/utils.go it looks like goquery is being used (goquery internally makes use of cascadia for it's CSS selector support):
https://github.com/sibprogrammer/xq/blob/8dbf6ee9e9fc9d589cf5cfe0a8cc23038706d014/internal/utils/utils.go#L173-L184
Specifically it seems to be using .Text() to return the .innerText equivalent of the selected node:

https://pkg.go.dev/github.com/PuerkitoBio/goquery#Selection.Text

Text gets the combined text contents of each element in the set of matched elements, including their descendants.

Yet looking at the goquery docs, it's possible to access the .innerHTML (or even 'outer HTML') for a selected node:

https://pkg.go.dev/github.com/PuerkitoBio/goquery#Selection.Html

Html gets the HTML contents of the first element in the set of matched elements. It includes text and comment nodes.

https://pkg.go.dev/github.com/PuerkitoBio/goquery#OuterHtml

OuterHtml returns the outer HTML rendering of the first item in the selection - that is, the HTML including the first element's tag and attributes.

Unlike InnerHtml, this is a function and not a method on the Selection, because this is not a jQuery method (in javascript-land, this is a property provided by the DOM).

So basically, to implement this feature, it looks like we just need to use the .Html() function instead of the .Text() function; most likely also adding a CLI argument that controls when one is used over the other.

As a workaround in the meantime, it looks like the cascadia library has a separate CLI tool:

https://github.com/andybalholm/cascadia

CSS selector library in Go

https://github.com/suntong/cascadia

The Go Cascadia package implements CSS selectors for html. This is the command line tool, started as a thin wrapper around that package, but growing into a better tool to test CSS selectors without writing Go code:

Thanks for your suggestions, but cli tool will not work in chrome extension

Thanks for your suggestions, but cli tool will not work in chrome extension

@madneal I'm aware of that. Using the CLI is just my workaround to your extension currently being broken, as I described here:

https://github.com/madneal/export-to-markdown/issues/14#issuecomment-1374702021

For actually fixing that issue within your extension you don't need this or any other CLI tools/library/etc because the required functionality is natively built into the browser, and thus usable by your extension.

Just found my way back to this issue again after trying to use xq in this way, and wondering why it wasn't outputting anything from my --query.
Back to the workaround it is then (Ref)

@0xdevalias could you provide a little bit more detailed example?
If we are talking about example.com there we should use some different selector instead of "body > p". E.g.
curl -s https://example.com/ | ./xq -q 'body > div > p' or curl -s https://example.com/ | ./xq -q 'p'

@sibprogrammer Of course :)
You can check out the comments I made over at the cascadia repo (Ref: 1, 2, etc) (as it turns out it didn't solve my needs either this time due to some bugs/limitations, so I ended up using pup (Ref: 1, 2) instead)
This time around, basically I wanted to process something like this:
<html>
<head>
  <script src="foo.js"></script>
  <script src="bar.js"></script>
  <script src="baz.js"></script>
</head>
</html>

By using a query something like:
html > head > script[src]

Be able to get a response back like this:
<script src="foo.js"></script>
<script src="bar.js"></script>
<script src="baz.js"></script>

And then ideally, if I was also able to then tell it to return the contents of the attribute src, my end goal as to get output like this:
foo.js
bar.js
baz.js

I proposed what I thought would be useful syntax/semantics for this over on cascadia (Ref: [1](https://github.com/suntong/cascadia/issues/3#issuecomment-1594038735, 2); which already has a concept of "output this sub-query" (using --piece), but essentially it would be by being able to use the same [foo] CSS attribute selector syntax in a different context (in their case, within --piece as opposed to --query) to say "output the foo attribute from all matching elements that have it)

https://developer.mozilla.org/en-US/docs/Web/CSS/Attribute_selectors

I didn't look into the url closely, but having check it out again just now, I found that the a[title] in CSS Attribute selectors means <a> elements with a title attribute, IE, how to select the <a> elements, while here we need a syntax to return attributes, which is not supported by CSS selectors (still).

Yup, that is how it works in normal CSS selector usage, and is how it would need to work (and just how it does work I believe) in the --query part of cascadia; but what I was proposing above is that we could leverage the same familiar semantics of that syntax, but when used within --piece, we could have it output the actual attribute being described.
So basically:

--query:

[foo] would return all elements that have an attribute named foo
a[foo] would return all elements that have an a attribute named foo
etc

--piece

[foo] would return the attribute named foo from all elements that have it
a[foo] would return the attribute named foo from all a elements that have it
etc

So then combined, you could use these like I described above:

That way the --piece syntax would sort of end up being much closer to just standard CSS selector usage. And I could do something like:
⇒ pbpaste | cascadia --in --out --css 'html > head > script' --piece url='[src]'

⇒ pbpaste | cascadia --in --out --css 'html > head' --piece url='script[src]'

# etc

Originally posted by @0xdevalias in https://github.com/suntong/cascadia/issues/3#issuecomment-1594038735

Originally posted by @0xdevalias in https://github.com/suntong/cascadia/issues/3#issuecomment-1600034259

There is also the 'prior art' of how pup has chosen to implement their 'Display Functions' (as they call them):

https://github.com/ericchiang/pup#display-functions

Which uses attr{attrkey} (eg. attr{foo}):

https://github.com/ericchiang/pup#attrattrkey

Print the values of all attributes with a given key from all selected nodes.

@0xdevalias thank you for clarification!
I prototyped a straightforward solution (didn't publish it yet):
*[master][~/projects/xq]$ cat ~/tmp/text.html | ./xq -q "head > script[src]" -a "src"
foo.js
bar.js
baz.js
*[master][~/projects/xq]$ cat ~/tmp/text.html | ./xq -q "head > script" -a "src"
foo.js
bar.js
baz.js

It seems it should be enough for attribute extraction. pup syntax looks more promising, but more complicated (at least at first glance).

I prototyped a straightforward solution (didn't publish it yet):

@sibprogrammer Nice, looks good! Will there also be a longer --attr or similar as well as the -a?

It seems it should be enough for attribute extraction. pup syntax looks more promising, but more complicated (at least at first glance).

nods yeah, that's fair. Personally I don't know if a lot of the pup syntax would even matter / be relevant to my day to day needs anyway. Just thought I would include it in case it was useful.


Update browser compatibility for Array.from

There were some gaps in browser support coverage for Array.from.

yeah noticing the same issue :+1:

Thanks for this.


PR for solving issue #16797

A minimal change that solves the issue is modifying the method keras.layers.Layer.trainable_weights(), in base_layer.py, by replacing it with the analogous method of keras.Model.
But still I have some questions: Does it make sense to have two different methods for gathering weights, one for Models and other for Layers? Shouldn't they be the same?
I did not update the non_trainable_weights method, but probably with them the same thing should be done.
I don't feel very confident with this as I don't fully understand the internal working of keras. I just checked where the discrepancy was and tried the obvious thing: copying from where it works (Model) to where it doesn't (Layer).

Thanks for the PR!
I suspect that the reason we have different logic in Layer and Model is to preserve weight ordering backwards compatibility.
How does this change impact weight ordering, e.g. for a layer that includes a sublayer that includes BatchNorm layers?
If weight ordering is not generally impacted then I would suggested moving the logic for weights/trainable_weights/non_trainable_weights as well as the deduplication logic to the Layer class. Model can just inherit from it.

Thanks a lot, @fchollet. I've tried your suggestion, you can take a look at this gist if you want:
https://gist.github.com/JaimeArboleda/7d446a9ba01a9929d603f6a084014741
You are right that the order of weights is affected, so I'll try to find another solution, maybe modifying the existing code in a less drastic way...
PS: I know is not the most proper place to say that, but if you don't mind I'd love to thank you for (among other things) your wonderful book on Deep Learning and your terrific tutorials publicly available in the keras docs. I learned a lot from them!

If you take a look at my last commit (if this PR is getting too messy, I can delete it and create a new one), I think I have a better solution that does not affect order of weights.
Basically, I created a method that is called in build() and that updates variables contained in wrapped objects (that might have changed after the creation of the container, a dict or list):
    def _update_trackables(self):
        """This method loops over tracked objects to update tracked variables
        for wrapped lists/dicts that may have been updated after initialization
        (Issue #16797)
        """
        for trackable_obj in self._self_tracked_trackables:
            if isinstance(
                    trackable_obj,
                    tf.__internal__.tracking.TrackableDataStructure
            ):
                self._track_variables(trackable_obj)

PS: I know is not the most proper place to say that, but if you don't mind I'd love to thank you for (among other things) your wonderful book on Deep Learning and your terrific tutorials publicly available in the keras docs. I learned a lot from them!

Glad the book was useful! Thanks for the kind words.

I did not know that we could not rely on every layer being built, or even that in the __call__ new weights could be added to a wrapped list/dict.
With respect to the overhead, it will depend on:

How many weights the model contains, as we would be looping over self._self_tracked_trackables of each layer.
How many of those tracked_trackables are ListWrapper or DictWrapper, as for them we would be performing an extra inner loop to update the variables inside the wrappers.

So if we had a model with many layers, each layer containing lots of trackables and/or wrappers, the overhead could be noticeable. I think that this is not common in general, not even in large models (those with billions of trainable parameters), as large models tend to have their parameters contained in big variables, so the ratio of trackables against parameters is very small.
I can provide two examples run in a Google Colab instance:

Example 1: GPT-2 from Huggingface, with 124 M parameters. It takes 1.3 milliseconds to perform an update in all of its components (layers, trackables, etc.) using the proposed code. It should be noted that this model has 148 weights in total.
Example 2: a model containing 1000 layers, each of them containing 10 inner layers, and each inner layer containing two weights. In this case, to make things "worse", everything (layers, inner layers and weights) is contained in ListWrappers. It takes 300 milliseconds to perform an update in all of its components. It should be noted that this model contains 60 K parameters and 20 K weights.

Given those numbers, do you think we need caching solutions?
On the other hand, I thought about another option, but it will imply more changes to the codebase:

When we create a ListWrapper or a DictWrapper, we add a reference to the container of this object (if my understanding is correct, it could be a Layer or another Wrapper).
When the Wrapper is changed (for example, when appending a value to a ListWrapper), we notify the container by calling a specific method that will update its weights and propagate the message upwards until we reach a Layer.
This way, we ensure that every change is inmediately taken into account, and we won't need to run all those loops just in case.

What do you think?

Sorry for the delay in reviewing this.

On the other hand, I thought about another option

I think simply having the content of the current def _update_trackables(self): get called in trainable_weights / non_trainable_weights should be sufficient. The overhead does not seem to be significant.
Thank you!

Ok, thanks a lot for reviewing it. I agree with you. I made a last commit doing exactly what you say.


new(plugin): validate key types at runtime (including nested tables)

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature
Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area ci

/area event

/area event_derive

/area plugin

/area plugin_api

/area plugin_derive

/area plugin_tests

What this PR does / why we need it:
Accessing nested tables was pretty much YOLO since we had no key type validation (accessing a table that was defined to have a string key with an int index would lead to fireworks, for example).
Add the validation and a test.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

NONE

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: gnosek
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [gnosek]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 3319eadfb99fbcbe21213858d61c31bbb6cdcbe3

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, gnosek
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,gnosek]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Back to home button on login page .

Would like to add a home redirection button to the log in page in  case the user would rather just look around.

Please assign to TheKDS224


Add a scheduled build canary

Describe the feature
At a regular interval (i.e. once per day overnight) run a CI build that:

Pulls latest model changes
Code-generates models
Builds & tests models

The purpose is to identify model changes that will not build before we attempt a planned release.
Use Case
To identify breaking model changes before a release is attempted.
Proposed Solution
Add a nightly CI task on Github.
Other Information
No response
Acknowledgements

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

Completed.  Job now runs nightly.


Dashboard RWD fixes

Connected to: #351
Steps to reproduce
As a user with wallet connected
Expected behaviour

640

card width: 608px

1728

three cards layout, card width: 444px

Changing this to the last known status before the migration to this project. (In QA)
@MSzalowski @SandraRodziewicz Did this one end up on staging env?

Yes. Moved to staging column


Allow reference to existing elasticsearch backend for tracing storage

Describe the feature request
In order to run a more production grade tracing solution, one must run a longer-term storage solution such as Elasticsearch/Cassandra for tracing storage.
The current helm deployment only support the in-memory PoC/testing stack.
It would be great to also have a way to specify an existing Elasticsearch cluster that you can send your traces to.
Describe alternatives you've considered
The alternative at the moment is to deploy Istio with --set tracing.enabled=false && --set global.enableTracing=true then install jaeger as a standalone helm chart which creates the jaeger-ui, jaeger-collector and jaeger-agent. The deployed jaeger-collector has the correct label app: jaeger to allow the zipkin service to correctly route to this stand-alone jaeger deployment.
Jaeger chart available here: https://github.com/helm/charts/tree/master/incubator/jaeger

An alternative not mentioned here is to add an elasticsearch adapter that supports the tracespan template and handle integration in that fashion.

In Istio 1.0.x, there is no Zipkin deployment available. However in 1.1.x it will be possible to deploy an in-memory version of Zipkin using the helm install parameters --set tracing.enabled=true --set tracing.provider=zipkin.

I see. My concern is whether Zipkin is necessary for a standalone Jaeger to collect traces generated by Istio 1.0.x. Or is the jaeger-agent daemon set essentially replaces the functionality of it?
Right now as experimentation, I have deployed a standalone Jaeger using helm chart along with Istio and configured it to use an existing ES backend for storage. So far, I'm not seeing any traces generated by Istio like it would with the all-in-one setup (i.e. --set tracing.enabled=true). Any help or suggestions, or past experiences with such setup, are greatly appreciated.

No Zipkin is an alternative to Jaeger, so they both shouldn't be installed at the same time.
The jaeger-agent is not relevant in the context of collecting tracing information from Istio's control plane (i.e. proxies, mixer, telemetry, etc). The information is sent directly to the Jaeger collector via the zipkin port (and data format). The jaeger-agent1 is used when collecting tracing data created by a Jaeger tracer.
Can you provide more details about how you deployed/configured Jaeger to use the ES cluster?

@chunheisiu Once you've deployed jaeger using the helm chart, you need to create a zipkin service that points to your jaeger collectors. For example:
apiVersion: v1
kind: Service
metadata:
  labels:
    app: jaeger
  name: zipkin
  namespace: istio-system
spec:
  ports:
  - name: http
    port: 9411
    protocol: TCP
    targetPort: 9411
  selector:
    app: jaeger
  type: ClusterIP

@castlemilk Thanks for the tip. Does this service need to in the istio-system namespace?
I currently have the standalone Jaeger deployed in the separate tracing namespace and I wonder if it would work.

@castlemilk I have deployed the Zipkin service and the standalone Jaeger to istio-system and I am beginning to see traces in my ES instance.
However, after deploying the BookInfo application, I noticed that a lot of the traces showed up as "" and are broken into separate traces. Do you happen to have experienced such behaviour and possibly have a fix for that?
Thank you so much in advance!

we use an existing zipkin: "kafka-es=zipkin", istio support the template tracespan, so if it can be used by an custom kafka adaptor? it seems that the tracespan template don't have annocation field and can not support zipkin api

@castlemilk I tried earlier today and the problem seems to be gone for me as well, similar to what you experienced.
I believe the ingress gateway was not sending traces and caused the other traces to become orphans. Do you have a theory as to why this happens and how it was able to correct itself after a certain amount of time?

Do you have experience to deploy Jaeger not into istio-system namespace. I've successfully deploy it to default namespace, but don't see any spans caught. I've changes zipkin address to fully qualified name, but its not help. Any ideas how to fix that.
          - --zipkinAddress
          - zipkin.default.svc.cluster.local:9411

@insider89 Do you have a zipkin service in that new namespace? i.e. see https://github.com/istio/istio/issues/8893#issuecomment-441989877

@insider89 looks like sidecar injection does cause an issue then. Have you checked the zipkin address being passed to the proxy?
Possibly update the value in the helm values.yaml.

Hello @objectiser. I've successfully run production-ready Jaeger in jaeger namespace with sidecar injection enabled (disable it only for jaeger-collector). Thx for the help.

Issue seems to be fixed - have created a docs PR to cover this: https://github.com/istio/istio.io/pull/4210

hi all,
We are having zipkin on a standalone vm currently with backend storage as elasticsearch. But now we want to remove that standalone and deploy zipkin as istio plugin container in our eks cluster ( we have istio running in our cluster btw). But then we dont have any option to configure elastic search as storage type. Any idea on how to do this ?
Thanks


test: implement user, group ownership checks

closes #2337

Well drat. It appears that the tests run as root/wheel on FreeBSD, foiling my attempt at a negative test (-O/-G of a file I do not own).

Could you please ignore the test on freebsd?

Seems that we are getting one more tests working
GNU testsuite = TOTAL: 601 / PASS: 160 / FAIL: 331 / ERROR: 20
=>
GNU testsuite = TOTAL: 601 / PASS:  161 / FAIL:  330 / ERROR: 20

@sylvestre sorry, I’ve been travelling. I’ll ignore those failing tests on FreeBSD.

@tertsdiepraam sure thing!

@sylvestre @tertsdiepraam it appears to be working now. The failed check looks unrelated: it appears to be random failure of one of the sort tests on Windows.

We do indeed have some unrelated failures sometimes. Thanks for your contribution!


Slack update: "Please update your third-party app or use the Slack desktop app"

Describe the bug
Slack request to update its app.
Screenshots

Desktop (please complete the following information):

OS: Ubuntu 18.04

Also since ~3 weeks on Mac Mojave 10.14.3

Describe the bug:
I am having the same issue; I was able to log into the Slack app through Franz earlier today but am now unable to access Slack through Franz.
Screenshots:

Desktop:
OS: Ubuntu 16.04
Steps to Reproduce Bug:

Open Franz
Attempt to open Slack through Franz

I have also tried overriding the User Agent and also having no luck!

Hey @larkin-nz I went with the Manual workaround method since updating Ubuntu did not seem to update Franz. Everything is operational again.
I think we can effectively close this issue now - especially if it is simply a bug that can be fixed by a version update. Thanks again!
Keep up the great work Franz team @aipi

Glad that worked for you @TheCedarPrince
I agree that this should be closed now!

@larkin-nz solution worked. Thank you so much! :heart:

~/home/.config/Franz/recipes/slack

~ already indicates home. - ~/.config/Franz/recipes/slack :+1: thanks for the fix bud.

@belthaZornv - Yes, it does - typo there - thanks for pointing that out! :)

With Franz 5.0.0 (stable) or 5.0.1-beta.1 this is already fixed as we've updated to Chrome 69.
Ad auto update. We're currently doing tests the AppImage updater in 5.0.1

just fyi, that just happened again today, the method mentioned works fine (with the latest chrome version added)

just fyi, that just happened again today, the method mentioned works fine (with the latest chrome version added)

Yep, i had to change to 78.0.3904.97

Installed Franz 5.0 today, slack is not working for me. https://recordit.co/O7UUf3ofte


can't find or open a directory on a standalone build

Godot version:
Godot RC1
OS/device including version:
Windows 10 x64
Issue description:
locating / opening a directory works in the editor but once you create a standalone build the engine seems to not know where the directory is. finding and loading a specific file in said directory works but
if you can find a file why not the directory the file is located in?
Steps to reproduce:
using something like directory_exists( path-to_directory) returns false on a standalone build, while it will work in the editor.
Minimal reproduction project:

So how is the status of this issue? Have encountered this issue on my own and not really found any workaround. #17607 is supposed to have fixed this issue, but is it also fixing #14562?


Hide the dubtrack module

Pull request checklist:

[x] CHANGELOG.md was updated, if applicable
[x] Documentation in docs/ or install-docs/ was updated, if applicable

idk if I should do something with the api wrappers file, but dubtrack's site appears to be fully down

Why don't we just remove it. The dubtrack domain isn't even registered anymore. If they ever come back, thanks to git, we can restore it.


Client: Disable submit after submit (before result)

This is not necessary as the action blocks whole UI.


Add TableMetadataBuilder::assign_current_snapshot_id

TableMetadataBuilder::from_table_creation initializes current_snapshot_id to None. This PR adds a builder method that allows different values.

Thanks @SergeiPatiakin for your PR!
Assigning the current snapshot id is a bit more complex than what you have in your PR.
Here is the extract from the spec: https://iceberg.apache.org/spec/#table-metadata-fields
current-snapshot-id: ID of the current table snapshot; must be the same as the current ID of the main branch in refs.
The logic you are looking for is already implemented in https://github.com/apache/iceberg-rust/pull/587 which is currently under review. I am optimistic that we can include it in the next release.
Could you check if https://github.com/apache/iceberg-rust/pull/587 serves your usecase? Check the set_ref method:
https://github.com/apache/iceberg-rust/pull/587/files#diff-464f76c3b76da41490c8fac47aa4aef4287fffdd0ca0766ae431c4829d59aa30R462

Thanks! You are right, I think I'll be able to use TableMetadataBuilder::set_ref from https://github.com/apache/iceberg-rust/pull/587 . Closing this PR


Add a squash command

Currently it would be good to have something like a squash command, where you could have lots of migrations and squash them into a single (or multiple less than before) files. Currently I think with java migrations this is hard to do, but with SQL it shouldn't be a problem at all!

+1
This would be very helpful. During the development process, we may create a table, then later in a new script alter the table to add a new column, then again and again. So, at the end of the day, we could have several scripts just to create a single table. This accurately represents the development process, but is not necessarily ideal when it comes to our "real" environments, including production.
In DB2 for example, after some number of table alters (lets say 5) to add a column (or other reorg recommended operations), the table goes into reorg pending state. This is going to be unavoidable at some level. But, if we could squash multiple alters from a given release into a single alter, we can at least push back on that limit a bit longer.

Currently this would work on production aswell, if you squashed lots of migrations, you could just delete the flyway table on production and let it recreate it.

Deleting the flyway table in production seems like a high cost to pay to get this functionality. We would loose our years of history.

if you have over 10.000 migration files it something you will pay. especially for a consumer product where running 1000 migrations per version could take a while.
I mean people that running there software inside the cloud don't have the same problem than running their software on multiple servers and multiple customers.
Mostly if we have something like
Version 1.1.1 which has a extra column in 1.1 while 2.0 has that inside a bigger migration we could just ignore the history in between. since we want to rebase the current database to 2.0 we mostly have a second set to upgrade from latest minor to new major which will upgrade / migrate the database and then starts from a single entry inside the flyway table.

Duplicate of #470


Intermittent premature cancelation of requests due to idle timeout

We have a service running Http4s Blaze Server 0.21.22 using ZIO 1.0.7 as our effect system.
The last week or two we've seen 3 or 4 requests every hour being cancelled part way through. In ZIO this causes the effect to be interrupted. Turning debug logging on for http4s, we were able to see this was being caused by the idle timeout

Idle timeout after 60000 ms.
Shutting down due to idle timeout

This was happening for requests running for much less that 60 seconds. Some only 100ms or so.
Disabling the idle timeout by setting it to Duration.inf made the issue go away completely.
Looking more closely at the logs, and by adding some extra debug logging, it appears the issue is around HTTP 1.1 clients keeping the connection open between requests. If the second request comes in just prior to the idle timeout, and does not have a body to parse, we could see it did not trigger IdleTimeoutStage to reset its timer.
This issue was particularly problematic for us as we had a number of scheduled tasks being trigger by Google Cloud Scheduler often timed to happen one minute apart. Cloud Scheduler sends POSTs with no body and our idle timeout was set to 60 seconds.
It seems the solution would be to trigger IdleTimeoutStage to reset its timer at the start of reading any request headers, and not wait for incoming or outgoing data.

@RafalSumislawski has been doing a lot of work on idle timeouts and might know offhand a ticket that already addresses this.

Hi @andybryant
I address this issue in #4796. The fix is planned for release 0.21.23.

@rossabaker Minor point - the label should be module:blaze-server not blaze-client

Oops! Thanks.


Moved react and react-dom to peerDependencies

Moved react and react-dom to peerDependencies where they belong :wink: Got burned by the multiple-react-version issue when installing the<EMAIL_ADDRESS>

Ah, great idea, thanks!


bower was removing all the good stuff

constants, directives, filters and services were not available after bower installing.

I've merged it, but to be perfectly honest, I don't recommend you use this module. I will not be supporting it. I recommend you copy and paste and modify the code.


Consider adopting BB.Model-style API or using getters/setters

At the moment, there's a mismatch in the API when it comes to setting certain attrs.
For instance, if you want to change the fn you can do that directly. But if you want to change the yaw or pitch you must go through orient().
There are two ways to make this consistent:

Go the bb route with an explicit getter/setter API surface.get('yaw')
Add JS getters/setters for yaw/pitch

A third option would be generating the rotation when render is called. This also makes the animation API easier, so maybe that's best :open_mouth:


Initialise StreamingHTTPResponse.protocol = None

Avoids mypy errors from asgi.py setting that variable.

This is merged to #1808.


[BUG] OpenAI TypeSpec should not include the "filename" part in multipart/form-data API

API Spec link
https://github.com/Azure/azure-rest-api-specs/blob/main/specification/ai/OpenAI.Assistants/files/routes.tsp#L50-L57
API Spec version
2024-02-15-preview
Describe the bug
The "filename" of a File should not be in multipart/form-data model.
Same in
https://github.com/Azure/azure-rest-api-specs/blob/main/specification/cognitiveservices/OpenAI.Inference/models/audio/audio_transcription.tsp#L48-L53
In TypeSpec design, the part would be written as
HttpPart<File, #{ name: "file" }>,

And the filename is included in the File.
Expected behavior
This "filename" should not be in model or method.
It is up to SDK emitter to determine, how to let user to set a "filename" for the File.
0000: --------------------------NWdLREXJ51lgZwiipJsqHR
0032: Content-Disposition: form-data; name="file"; filename=<filename>
005f: Content-Type: application/octet-stream
0087:
0089: The word 'apple' uses the code 442345, while the word 'banana' u
00c9: ses the code 673457.

Actual behavior
This extra "filename" part.
Reproduction Steps
NOOP
Environment
No response

@iscai-msft Please help have a look, thank you.


add custom-set.json

It's big.  I'm finally ready to add this as I have a test program in Go ready to use it.  As usual when I assembled this I went through existing test programs and combined and consolidated things.  The section at the end with mixed types is still kind of strange.  I don't use it in Go.  Someone who can actually use the data might fix it up someday.

Thanks! I hope to start trying these out with the Ruby track.


[Snyk] Upgrade ioredis from 4.17.3 to 4.22.0

Snyk has created this PR to upgrade ioredis from 4.17.3 to 4.22.0.

:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 9 versions ahead of your current version.
The recommended version was released 24 days ago, on 2021-02-06.

Release notes

Package name: ioredis

4.22.0 - 2021-02-064.22.0 (2021-02-06)
Features

add type support for scanStream (#1287) (ad8ffa0), closes #1279

4.21.0 - 2021-02-064.21.0 (2021-02-06)
Features

upgrade command list to Redis 6.2 (#1286) (6ef9c6e)

4.20.0 - 2021-02-054.20.0 (2021-02-05)
Features

support username in URI (#1284) (cbc5421)

4.19.4 - 2020-12-134.19.4 (2020-12-13)
Bug Fixes

prevent duplicate intervals being set. (#1244) (515d9ea), closes #1232 #1226 #1232 /github.com/luin/ioredis/blob/v4.19.2/lib/cluster/index.ts#L311-L313

4.19.3 - 2020-12-134.19.3 (2020-12-13)
Bug Fixes

auth command should be not allowed in auto pipeline. (#1242) (bafdd4b)

4.19.2 - 2020-10-314.19.2 (2020-10-31)
Bug Fixes

Fix autopipeline and downgrade p-map to support Node 6. [#1216] (1bc8ca0)

4.19.1 - 2020-10-284.19.1 (2020-10-28)
Bug Fixes

Make sure script caches interval is cleared. [#1215] (d94f97d)

4.19.0 - 2020-10-234.19.0 (2020-10-23)
Bug Fixes

Ensure delayed callbacks are always invoked. (d6e78c3)

Features

Add autopipeline for commands and allow multi slot pipelines. (aba3c74), closes #536

4.18.0 - 2020-07-254.18.0 (2020-07-25)
Features

supports commands in Redis 6.0.6 (c016265)

4.17.3 - 2020-05-30

    from ioredis GitHub release notes

Commit messages

Package name: ioredis

d9d464e chore(release): 4.22.0 [skip ci]
ad8ffa0 feat: add type support for scanStream (#1287)
8003af4 chore(release): 4.21.0 [skip ci]
6ef9c6e feat: upgrade command list to Redis 6.2 (#1286)
66aafae chore(release): 4.20.0 [skip ci]
cbc5421 feat: support username in URI (#1284)
0b001e0 docs: add documentation for Redis ACL
c7d80a7 chore(release): 4.19.5 [skip ci]
37c6daf fix: password contains colons (#1274)
be5d53f docs(README): fix wrong section link for benchmark (#1269)
72bde8f chore: adjust stale settings
69cdc67 docs(README): update failover docs for AWS ElastiCache (#1260)
c2a29c8 chore(release): 4.19.4 [skip ci]
f04ee5c docs: minor typos (#1199)
caa4b76 docs(README.md): fix typo (#1217)
a381ac7 docs:(API.md): fix formatting in API.md (#1221)
515d9ea fix: prevent duplicate intervals being set. (#1244)
a30a2b4 chore(release): 4.19.3 [skip ci]
bafdd4b fix: auth command should be not allowed in auto pipeline. (#1242)
cd336bf docs(README): typo for stream (#1243)
71ad02c docs(README): convert benchmarks tables to markdown (#1256)
2c7c89d chore(deps): bump ini from 1.3.5 to 1.3.8 (#1255)
9786122 chore(release): 4.19.2 [skip ci]
f4c0d89 chore: remove node 15 from travis as it currently fails

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Closing as it's not a vulnerability update and it's broken.


Does TuGraph-db support fulltext index?

Hi,
I'm confused about whether the fullText index API in cypher is available.
I ran a docker example of TuGraph on version 3.3.0 and saw 'FullTextIndex' API when using 'call dbms.procedures'.
Then I test the creating index query by Java client and it threw an exception.
Exception in thread "main" com.alipay.tugraph.TuGraphRpcException:Fulltext index is not enabled  at com.alipay.tugraph.TuGrpahRpcClient.handleCypherRequest(TuGraphRpcClient.java:68) ...
I have created the node ‘person’ before. Here is my code:
String response=client.callCypher("call db.addFullTextIndex(true,\"person\",\"name\")","Default",10);
Does TuGraph-db support fullText index and query? Could you give some explanations on doc?

Fulltext index is not supported in cypher statements and currently can only be used in plugins.

Does TuGraph have plans to support fulltext index  in future updates?  How can I use  fulltext index by making plugins or procedures?

TuGraph has supported fulltext index but it can not be used in cypher currently. And it is not enabled by default. You can see the cmake option at https://github.com/TuGraph-family/tugraph-db/blob/master/Options.cmake#L77.
Currently, the fulltext index is implemented using lucene, which has limitation that some complicated fuzzy queries are not supported. We are discussing about supporting fulltext index based on elastic search in the future but it is not decided.
You can follow up our future plan.


Small screen adjustments for mobile PWA usage

Description
The current app on small screen sizes is not pretty and in some areas, not even usable. For users like myself that would prefer to use the PWA than the mobile app, this is unfortunate. This PR aims to make minor style adjustments where necessary in order to alleviate these issues!

Before
After

Changes proposed in this pull request that will only be noticeable on small screens:

Add small margin to the feed page.
Fix the menu opening animation.
Add padding to the navbar buttons.
Add small margin to library page content and fix loading skeleton width issue.
Close the menu on click of library and groups buttons (the other two open a submenu).
Make the search bar usable:

Reduce width.
Pin the popover to the screen so it no longer falls off the left side.
Change the layout of the items to make more effective use of space.

Oh btw there is still more to do here but let's get this merged first before the PR gets any bigger 👍

This isn't your fault, but your changes made it more obvious. I'd suggest you change line 139 in _media_browse.scss to margin-left: 0;.

Before
 After

Notice the bottom left of the library entries.


Generate parametric interface GUIDs using const fns

We're currently generating all the necessary parametric interface GUIDs ahead of time in the code generator (C#). At least those that are necessary to compile the library. User code might need additional parametric interface instantiations and there's no way for the user to get the required GUIDs. We should instead try to do this from Rust using const fns, once that is ~implemented~ stable.
The C++ WinRT projection is using constexpr to do this: https://www.youtube.com/watch?v=7TdpWB_vRZM#t=23m46s

I started working on this in a branch: https://github.com/Boddlnagg/winrt-rust/tree/constfn-pinterface
However, const fn support is not yet capable of everything that we need for it to work.


MAHOUT-1642 fix missing first element in SimilarItemsIterator

Could you please someone tell me why this was closed without merged?

After I opened it and some time passed, I asked in mailing list why nobody merge it and received the following response:
"Part of the problem is that this is a fix to taste recommender.
There are two problems with this: first, it is mrlegacy component, and nobody these days cares so much maintaining these. Second, the author of this code, who would be qualified to assess the validity of the fix, has not come forward, which kind of goes back to the first point."
So ibid in mailing list it was decided to close the pull request.


Add information about ember-auto-import

This addon is unnecessary in ember applications using recent versions of
Ember CLI.
Fixes #72
@elwayman02 I think this should be followed up with a last release and then deprecation of this package in NPM. Since ember-cli can be updated without updating Ember in applications it should be possible for everyone to move to this route.

The syntax in this PR is actually enabled by dynamic imports. ember-auto-import enables a slightly different syntax.
At the top of your source file:
import zxcvbn from 'zxcvbn';

Then in your component:
@computed('password')
get passwordStrengthScore() {
  const { score } = zxcvbn(this.password);

  return score;
}

So no lazy loading but a simpler solution.

That's correct @mwpastore. I would encourage the dynamic import syntax for this library as zxcvbn is a pretty hefty payload.

Got it. That is pretty slick. Works great with ember-cli-deploy-s3, too.
If I may be so bold, perhaps the instructions could be enhanced a bit to help ember-auto-import first-timers like myself. I think the yarn command should have a --dev flag, and it might be worth explicitly calling out the extra steps to enable lazy loading.

@mwpastore I haven't looked at these in a while. If the process is fresh in your mind how do you feel about creating a new PR with improved directions? Feel free to steal anything you want from this one.

I'd be happy to!

Closing favor of #74


Figure out how to do assets

Should we upload all assets to GitHub? Should we have some specific license for them (CC BY 4.0, for example)?
How should we handle third-party assets (if we start using those)?

Maybe split the assets folder into two subfolders, with one license of our original work (CC-BY-4.0?) and one license file for any third-party assets (akin to https://github.com/nixsolutions/shelving/blob/master/LICENSE-3RD-PARTY).

Alternatively, each asset (can be a collection of textures, for example) has its own folder with its own license file.


fix: Optimize expiration time for shorter format

Thank you for your contribution to the KodaDot NFT gallery.
👇 _ Let's make a quick check before the contribution.
PR type

[x] Bugfix
[ ] Feature
[ ] Refactoring

What's new?

[x] PR closes #3621
[ ] Requires deployment <rubick/magick_issue>
[ ] <brief_description_of_what_I've_added>

Before submitting Pull Request, please make sure:

[x] My contribution builds clean without any errors or warnings
[x] I've merged recent default branch -- main and I've no conflicts
[x] I've tried to respect high code quality standards
[x] I've didn't break any original functionality
[x] I've posted a screenshot of demonstrated change in this PR

Optional

[ ] I've tested it at </rmrk/collection/26902bc2f7c20c546a-1FVG7>
[ ] I've tested PR on mobile and everything seems works
[ ] I found edge cases
[ ] I've written some unit tests 🧪

Had issue bounty label?

[x] Fill up your KSM address: Payout

Community participation

[x] Are you at KodaDot Discord?

Screenshot

[x] My fix has changed something on UI; a screenshot is best to understand changes for others.

can we somehow give user the ability to see the actual approximation of expiration time? Like full date popup on click or something. Maybe @roiLeo can think of something UX friendly 😅

can we somehow give user the ability to see the actual approximation of expiration time?

yup, reference in new issue

pay 30 usd

😍 Perfect, I’ve sent the payout
💵 $30 @ 63.94 USD/KSM ~ 0.469 $KSM
🧗 Caiv9TbPz68q5dC8EcHu5xKYPRnremimGzqmEejDFNpWWLG
🔗 0x390bbe782d93f716c9c31a15b95cb3dcdcce2d02544f37c5aed7106fe5a09bf3
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues


Egg coat or Zona Pellucida ontology (GO:0035805)

Hi,
I have created the Zona Pellucida (egg coat synonym) subcellular location for UniProtKB and I see it doesn't have 'extracellular matrix' as parent in GO event it is described as ' specialized extracellular matrix' in the definition. Since 'Zona Pellucida' is considered as a child 'extracellular matrix' in UniProtKB, would it be possible to review it in GO? thank you

@ukemi @cmungall any opinion on this one ?

Based on the definition it makes sense. I question whether the vitelline membrane would be considered an ECM though. I guess technically it could.

https://en.wikipedia.org/wiki/Vitelline_membrane says:

The vitelline membrane or vitelline envelope is a structure surrounding the outer surface of the plasma membrane of an ovum (the oolemma) or, in some animals (e.g., birds), the extracellular yolk and the oolemma. It is composed mostly of protein fibers, with protein receptors needed for sperm binding which, in turn, are bound to sperm plasma membrane receptors. The species-specificity between these receptors contributes to prevention of breeding between different species. It is called zona pellucida in mammals.
In insects the vitelline membrane is called the vitelline envelope and is the inner lining of the chorion.

Thanks @krchristie

Moved 'egg coat' under GO:0031012 ! extracellular matrix
Removed GO:0031012 ! extracellular matrix part_of GO:0005576 ! extracellular region; replaced by GO:0030312 ! external encapsulating structure

Thanks Pascale!
Best wishes
Cristina

From: pgaudet<EMAIL_ADDRESS>Sent: Wednesday, December 16, 2020 12:47 PM
To: geneontology/go-ontology<EMAIL_ADDRESS>Cc: Cristina Casals Casas<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: {Disarmed} Re: [geneontology/go-ontology] Egg coat or Zona Pellucida ontology (GO:0035805) (#20537)

Moved 'egg coat' under GO:0031012 ! extracellular matrix
Removed GO:0031012 ! extracellular matrix part_of GO:0005576 ! extracellular region; replaced by GO:0030312 ! external encapsulating structure

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/geneontology/go-ontology/issues/20537#issuecomment-746163386, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHEQE5RD3XFJOEBQGJI6FBTSVCM4PANCNFSM4USANX2A.

It's not finished yet... there are many domino effects. I also need to change
perisynaptic extracellular matrix
part_of GO:0099544 ! perisynaptic space
=> change to 'adjacent to' some 'perisynaptic space'

Also changed
GO:0043083 synaptic cleft
'extracellular region'
part_of some synapse
=> changed to 'adjacent to'
(I am surprised that didn't cause problems before)

Also removed 'extracellular region' from a number of collagen terms

also extracellular matrix of synaptic cleft
changed part_of synaptic cleft to 'adjacent to'
(the synaptic cleft is defined as a 'gap', so technically it contains no parts ?


Still cant get to the weights of a Trained network

I have a trained classifier and when I want to access the weights I get the error:
AttributeError: 'Classifier' object has no attribute 'get_parameters'
My classifier's name is fin_net. So why does fin_net.get_parameters not work!!? I love this library so much I just hate how hard a time I am having with getting to my weight matrices! :(

You're using the version from Git master?

My version says scikit-neuralnetwork 0.4. I simply did pip install
scikt-neuralnetwork to get the latest version.
On Wed, Dec 16, 2015 at 9:47 AM, Alex J. Champandard <
<EMAIL_ADDRESS>wrote:

You're using the version from Git master?
—
Reply to this email directly or view it on GitHub
https://github.com/aigamedev/scikit-neuralnetwork/issues/153#issuecomment-165130643
.

Ah, just get from master in the meantime! Once our dependencies ship new versions we can release easier...

Alex how do I get it from the Git Master?

Install like any other Python package. Details on front page.

Nevermind! I figured it out using the git+ command followed by the url. I can see it works perfectly now. I just went with the original pip install because it said recommended. Is it always better to install from master branches?

Thanks Alex! This library is awesome!


fix: incorrect negative value conversion

Thanks for submitting a PR! Please check the boxes below:

[x] I have run pre-commit to check linting
[x] I have added information to docs/ if required so people know about the feature!
[x] I have filled in the "Changes" section below?
[x] I have filled in the "How did you test this code" section below?
[x] I have used a Conventional Commit title for this Pull Request

Changes
Negative ints were being sent as strings to the api when saving a feature.
How did you test this code?
Saved a feature with the value -1

Hmm yeah, we've fixed this conversion before but I think that only affected people experiencing an issue. It depends on what language SDK they are using (we should maybe track this in headers).
JavaScript will actually work with both, because JavaScript.

For reference, I've just checked the production database and we have ~60 such cases.

@matthewelwell Could you share that dataset/query? I'd like to evaluate our options to move forward based on that.

For reference, I've just checked the production database and we have ~60 such cases.

@matthewelwell Could you share that dataset/query? I'd like to evaluate our options to move forward based on that.

I've done this in Slack FYI @rolodato .

I've reviewed the data and there's about 10 organisations, viewable here: https://metabase.flagsmith.com/question/9-features-with-negative-numbers-as-strings. Some of them do have these values set in production so we can't just ship this change as-is, unfortunately.
I can think of a few paths forward:

Abandon this PR and ignore this issue until we can make feature value types explicit, which sidesteps this problem entirely (assuming this is planned/desired)
Add more functionality to this PR to enable users affected by this issue to migrate to the new behaviour at their own pace:
2.1. If a feature is currently a negative number string and a user tries to update it to a negative number, offer a choice to save the value as string (default) or as integer (secondary choice)
2.2. If someone does need to create a new feature with a negative string number, they can use the API manually.
Add more functionality to this PR to display a warning banner when editing a feature with a negative number string, saying that saving changes to the value will change its type to integer, with instructions on how to manually save the value as string if needed.
Set some deadline in the future and notify affected customers that they need to migrate before we ship this PR as-is. CS can create documentation on how SaaS customers need to migrate, how they can tell if they're affected, etc. For on-prem Enterprise customers, we can let them know before they upgrade. On-prem Free users are a bit more tricky to find and notify.

IMO, option 2 is ideal UX until if/when we ship explicit feature value types, but option 3 might be a better effort/reward compromise based on how few SaaS users are actually affected by this. Option 3 is not as much implementation effort and is less risky (no user interaction or manipulating feature values on behalf of users). I'll leave this decision to @kyle-ssg since you'll probably write the code for the actual solution :)

I've been reviewing this and I think it's a big change with lots of code considering the amount of people this will temporarily affect. Especially when this considers change requests and feature versioning.
I'd be inclined to go with 3.

Ok yep after discussion this is now done,


Fix potential cross-thread call to onDone in base Wasm (#209)

Cherry-pick https://github.com/istio/envoy/pull/207 to master. After this, an integration test will be added in istio/proxy to prevent regression.
For an explanation of how to fill out the fields, please see the relevant section
in PULL_REQUESTS.md
Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
[Optional Fixes #Issue]
[Optional Deprecated:]

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

test-tsan_envoy
3be4bc1123c6ad7997a38df87cab5c3cb3faa34c
link
/test test-tsan_envoy

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test test-tsan_envoy

@jplevyak @PiotrSikora ptal thanks!


feat(Order/WellFounded): well-founded of strictly monotone

This PR is separated off from #12273, which no longer depends on it.
We show that an order with a strictly monotone function into an order with WellFoundedLT is itself WellFoundedLT.
We also add three dual variants, and provide an instance showing that a Nat-graded order is thus well-founded.

Mathematically this is not my expertise, but in terms of style I think this looks good to me!

Looks fine other than the comment above.
bors d+

bors r+


Image/text overlay issue on related content items

Illo and content aren't playing nicely together:

http://alistapart.com/article/web-animation-at-work
I'm on Chrome 45.0.2454.99.

max-height: 100% is apparently not sufficient for Chrome.


Change how we decide if a rule should autocorrect or not

Fixes #1466
Implement what #1466 says has one side effect. The rulsets with rules autocorrectables and other no autocorrectables we should define in all of them if they are auto correctables or not. Otherwise all of them are autocorrectables.
This PR is the successor of #6914

To be honest I don't like this too much. Now it seems that you can enable the autoCorrect for ClassName. And if you do so... well nothing happens. detekt will finish but they will not be fixed.
One of the main problems here is that detekt doesn't know if a rule implement or not the autocorrect feature. It just now if the configuration actives it.
I would remove the autocorrect feature from detekt or, if someone wants to expend the time in it, look for a better way to implement it. Right now it is really fragile. I have some ideas about how to make this work better but I'm not willing to implement it myself.

Closing again. This wouldn't fix #1466 either. If you don't say "autoCorrect: false" at your config file the default configuration will decide. I'm not going to expend more time on this issue.


BVH8_CWBVH: Skip conversion if it's not possible in Build()

BVH8_CWBVH::Build() now auto converts from BVH8 to CWBVH. However, the conversion might fail if there is a single node.
Would be better if Build() was returning an error code or something, since using this API doesn't allow to pre-check for the input nodes count.

Related to #61, since I hit this assert because of it

Ah yes, the single-quad scene scenario. I will make sure this exception is properly handled in all builders. Leaving this open until it is resolved. Perhaps there are cases where an error is needed, but this should be an exception: Ideally, even an empty scene should be trace-able, for robustness.


Version the docs

The docs at http://googlecloudplatform.github.io/gcloud-python/datastore-api.html document the current API at git head - and include a version tag of 0.3.0
This matches the current released version on pypi (that does not have the recent change for implicit credentials)
Please consider using something like readthedocs and provide versioned docs - so that what users find actually matches what they are likely to install :)
Or at least mark the version in master as -dev with a warning in docs, and tag to stable version in a branch.

+1 for this. I'm starting reading source code at the specific commit / tag in order to know what's supported in that version.

+1 for this. The coding example under Getting Started for Storage doesn't work because the signature for get_buckets() has changed. This is really confusing because the docs say 0.3.0 which matches the version on PyPi as already pointed out. The only way to figure it out is the read the source code which probably isn't ideal.

Something like http://googlecloudplatform.github.io/gcloud-node/#/docs/history is preferred so hopefully we can borrow from gcloud-node
@silvolu you mentioned you had started this, do you have any half-finished work to go from?

@dhermes I mentioned I would start this, but then I got side tracked, so nope, I got nothing :/

@rstuart85 in the short term https://github.com/GoogleCloudPlatform/gcloud-python/releases/tag/v0.4.0 means the docs reflect the latest version on PyPI. I'm hoping to resolve this issue soon-ish.

Starting on this right now.

@dhermes great news!

Release pushed but new docs didn't build:
https://travis-ci.org/GoogleCloudPlatform/gcloud-python/builds/50716542
"Not in master on a non-pull request. Doing nothing."
Me thinks "${TRAVIS_BRANCH}" == "master" fails when pushing a tag. I'll have to play around and address this.


Clean up package data and MANIFEST

Recent changes brought in by #1093 include too much package-data. This should be cleaned up. MANIFEST.in should similarly be revisited.

This is the offending line in particular


Can you explain how this works?

The documentation for this parser is very minimal, so I barely understand how to use it. How do I go about pulling specific lines from the parser such as the file name, or the file size and outputting them onto my website?

assuming you already have your logic for storing the raw media info in your database then its a simple as:
$parser = new MediaInfo();
$parsed = $parser->parse($post->mediaInfo);

Then in your view:
@if($post->mediainfo != null)

                {{ $general['file_name'] }}

                @foreach($video as $key => $v)
                VIDEO {{ ++$key }}:
                {{ strtoupper($v['format']) }} / {{ $v['width'] }} x {{ $v['height'] }} / {{ $v['aspect_ratio'] }} / {{ $v['frame_rate'] }} / {{ $v['bit_depth'] }} / {{ $v['bit_rate'] }} / {{ $v['format_profile'] }} / {{ $v['scan_type'] }}
                @endforeach

                  @foreach($audio as $key => $a)
                   AUDIO {{ ++$key }}:
                  {{ ucfirst($a['language']) }} / {{ strtoupper($a['format']) }} / {{ $a['channels'] }} / {{ $a['bit_rate'] }}
                  @endforeach

                @foreach($subtitle as $key => $s)
                 SUBTITLE {{ ++$key }}:
                {{ ucfirst($s['language']) }} / {{ $s['codec'] }}
                @endforeach

@endif

Thank you for the fast response! The raw mediainfo is indeed already stored in the database. This helps out a lot, I recommend maybe putting this in the README.md file so that people understand it better :)

I got it working great, I just have one question - I noticed that the strings for things such as the filename all tend to be in lowercase. Is there any way to adjust that?

Yes I will be pushing a update to the package in upcoming day that will cover that issue.

Awesome, here is another thing I thought I'd mention to you that I have fixed in MediaInfo.php. The parsedFileSize function has a flaw for files that are over 1000MB. Since MediaInfo puts a space in between the 1 and the 0, the function will return a size of 1 MB in bytes since parsedFileSize doesn't compensate for that.
Notice in the fix that I'll post below that I've put $string = str_replace(' ', '', $string); to remove all spaces from the file size string being parsed to fix the problem.
Here is the fix:
private function parseFileSize($string)
    {
        $string = str_replace(' ', '', $string);
        $number = (float)$string;
        preg_match("/[KMGTPEZ]/i", $string, $size);
        if (!empty($size[0])) {
            $number = $this->computerSize($number, $size[0].'b');
        }

        return $number;
    }


Does not stop syncing

Steps to Reproduce

Downloaded and run (while executable is still in the DMG if that makes any difference)
OS: macOS Sierra

Expected Result

To leave the "Syncing..." state after a "more or less instantaneous" amount of time.

Actual Result

Gets stuck on "Syncing..."
~/Library/Logs/partyshare.busterlabs.xyz/log.log (ext changed to .txt so github would upload it)

Looks like you were probably already running an ipfs daemon? So approximatley a duplicate of #17

Yep, you're right. I hadn't actually read the log as I just stuck it up here after a request from the author but going thought it now and combined with the fact that I have the ipfs gateway running as a service on the defaults ports it seems pretty clear that this issue is a dupe.

Thanks for noticing that @jamiew !

@callumgare you should be good to go in the latest release! Thanks for your help


Clean up library a bit

Cleans up the library to reduce code reuse
Add rest of Interactions endpoints
Fix a few bugs with wrong Method type, and wrong response code
Add a few other missing endpoints
Remove a few removed endpoints
Added thread support

It's the same thing 8 times, just that's all the places I saw it and figured it was easier to mark it like this

I'll fix this once I'm done working today 😄


UI: "Back" and bookmarked page

Currently, the "Back" button (F3) will go to the previous page. However, in case a page has been bookmarked before (as a "jump-off"), then "Back" should go to the bookmark.
For example, the new "Repository Settings" are a collection of pages or "tabs". Repo overview or repo view are bookmarked when navigating to the settings. After navigating between various settings tabs, "back" should go back to the bookmark.
Details:

Navigation via zcl_abapgit_gui->handle_action (i.e. go_back and go_back_to_bookmark) are working fine (example "Back" button on settings form)
Navigation via "Back" (F3) is performed in zabapgit_forms form exit which always corresponds to go_back
https://github.com/abapGit/abapGit/blob/master/src/zabapgit_forms.prog.abap#L102

Idea:

If a bookmark is included in stack, then form exit jumps to bookmark. If not, form exit goes to previous page

set each tab to be "page replacing" ? then it would work as expected?

set each tab to be "page replacing" ? then it would work as expected?

cool! works. PR coming

cool! works. PR coming


Verify website build

Add CI step to verify website build.
This PR can help merging dependabot upgrades that affect website by making sure the page gets built.

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 85.52%. Comparing base (9b64f22) to head (5f2b9d2).
Report is 1 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2991   +/-   ##
=======================================
  Coverage   85.52%   85.52%
=======================================
  Files          58       58
  Lines        3413     3413
=======================================
  Hits         2919     2919
  Misses        494      494

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


v8

Any plans on this yet?
Perhaps even just strategy/approach explained so this could be up for grabs for anyone :)
Seperate branch/repo/backwards compat (multi project?) ..?

Bumping it up as I'm also curious how we all can help to make it DONE (without duplicating possible work already being completed).
🤔

News will come soon (sneak preview @buug)

As @kows says, confirmed! A new version does exist, but it's not public yet.
In fact it's a complete rewrite of the V7 version, and a new version for V8... Code isn't open for collaboration yet, but will be very very soon!
I have been running it in production for a little while but I will also need some guinea pigs to test on...

Use this a lot on all the U7 projects I've done. Would LOVE to keep on using it in U8 projects.
Any news @callumbwhyte? What can the community help out with?

It doesn't seem like this project is on @callumbwhyte his priorities list right now:
https://twitter.com/kipusoep/status/1260899016419704833

I appreciate everyone's excitement about Meganav for V8!
I'd like to give a FRIENDLY reminder that Meganav is a tool I created and maintain for free, in my own time. I do have other priorities and important things that require my attention, especially right now given the current global situation 😊
As mentioned in the previous comments, I do have a new version of Meganav for both V7 and V8 in the works. I haven't released it publicly as I'm still not 100% happy with it, but it's running in production on a number of my sites.
However, for those who have requested it I've always been happy to provide a preview of the V8 release. You can download it here.
This isn't officially a supported version, and the final change will definitely have breaking changes, but hopefully this is enough to get people moving until I release the final version.
Thanks everyone for your patience!

I understand. The only thing I'm a bit annoyed by, is the fact that you stated "Will check and get back to you. Preparing it for release." and then there's radio silence.
So now I have to remove Meganav and migrate to something else, that's just a bit annoying, sorry.

I'm sorry you feel that way @stefankip.
As with all open source projects, these things rely on the generosity of the community. I haven't had an opportunity to look into it, for the reasons I mentioned.
You are of course welcome to choose another solution if this version of the package isn't what you need. Similarly, I provided you with the code so you are welcome to look into any issues you are experiencing.

v2 of Meganav is out for Umbraco 8, and v3 for Umbraco 9


Fix the typo in README.

Fix the typo in README.
"modal" should be "model".

multi-modal means multi modality


Tracking of Rotated Hands

Devise a method of tracking rotated hands

[x] Devise a method of tracking rotated fingers
[x] Devise a method of tracking rotated thumbs

Tbh, I did this a while ago. Just forgot to close the issue


lib: fail gracefully if we can't find the username

Checklist

[x] npm install && npm test passes
[ ] tests are included
[ ] documentation is changed or added
[x] commit message follows commit guidelines

Description of change

In lib\find-python.js...

Only attempt to get os.userInfo().username in a try {} block, since it's not 100% guaranteed to succeed
If we can't find the Appdata\Local directory, skip checking paths under Appdata\Local.

Fixes https://github.com/nodejs/node-gyp/issues/2373

Note for reviewers:
I hoped to add logging to this, but I couldn't think of a way to do that without adding a new logging function at the file-level scope (outside of PythonFinder), and hoisting the errorLog[] array to the file-level scope as well. If that much of a re-write of lib/find-python.js is acceptable for a simple bug-fix PR, I can submit that. But for now this is geared more toward being a minimalist fix rather than a maximalist/perfectionist/eager one.

@DeeDeeG hi. As i see, you are working on find-python.js too. My opinion is that as we working on same the piece of repo, we should  strongly collaborate to avoid doing same work twice as it is now)) A am already have started to refactor logging system in my fork but have not pushed commits yet

Hi @owl-from-hogvarts.
Yes, coordinating is a good idea if multiple people are working on the same file in parallel. But I  am not planning to work on this repo for now, until some open pull requests get merged or closed. I don't think there is a point to contribute with a backlog of open PRs that might land, because it does indeed make it harder to predict which ones will conflict. And because it has actually been over a month since anything was landed at this repository, I am not sure when/if PRs will be merged. I don't want to propose a lot of changes, and potentially have to remember what I was working on months later to address feedback from reviewers. So for now I am not planning on submitting any additional PRs, until the backlog of recent open PRs is addressed. So I hope that means you don't have to worry about conflicts from my branches.
Best regards.
P.S. I understand most Node folks are volunteers and have a lot of various responsibilities. This is in no way a complaint or critique. I just want to put this out in addressing @owl-from-hogvarts's suggestion of coordination, and avoiding conflict between PRs. I think as I'm not posting new PRs it shouldn't be an issue. And it's a moot point until there is the real chance things start getting merged again.

Wow! thanks for so detailed answer 😄


Update setup.py

the latest version of requests(2.31.0) shipped with urllib3 2.0.4 leads to an error as follow when using -web options:
[!] Failed to connect to Web Enrollment interface: _http_request() got an unexpected keyword argument 'chunked'

Please don't put upper limits on dependencies, especially on popular libraries like requests. This will exacerbate dependency hell.
Here is how docker fixed the underlying issue: https://github.com/docker/docker-py/issues/3113
This is the fix: https://github.com/docker/docker-py/pull/3117/files
So we probably need to change https://github.com/ly4k/Certipy/blob/2780d5361121dd4ec79da3f64cfb1984c4f779c6/certipy/commands/relay.py#L45 accordingly.


Add minimal implementation of UnitRange and CartesianSet

Adds Cartesian set and UnitRange to gtx.common

Part of #1296


[Select]  Allow component to mount with dropdown rendered

Feature description
Either by altering the implementation of autoFocus or by adding a new prop, allow the user to pass in a prop to Select/StatefulSelect that allows it to render the dropdown upon mounting.
Currently, autoFocus does focus the component when it mounts, but it does not trigger a dropdown render. Feel free to play with this code sandbox https://codesandbox.io/s/8k682q3nrl

Hey! Is this issue still available. If yes, may I take it? Thanks!


Theme is not persistent any more.

Issue Type: Bug
When a new instance of VSCode starts the 'Black' theme is replaced with the default theme. I have to manually set it back to my desired theme.
VS Code version: Code 1.69.2 (3b889b090b5ad5793f524b5d1d39fda662b96a2a, 2022-07-18T16:12:52.460Z)
OS version: Windows_NT x64 10.0.22000
Restricted Mode: No
Remote OS version: Linux x64 4.19.104-microsoft-standard

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz (8 x 2304)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.73GB (3.15GB free)

Process Argv
--crash-reporter-id 256d7bf5-db2e-455b-925a-a63a04761abf

Screen Reader
no

VM
0%

Item
Value

Remote
WSL: Ubuntu-20.04

OS
Linux x64 4.19.104-microsoft-standard

CPUs
Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz (8 x 2304)

Memory (System)
7.64GB (1.60GB free)

VM
0%

Extensions (25)

Extension
Author (truncated)
Version

protein-viewer
Ari
0.0.8

es7-react-js-snippets
dsz
4.4.3

vscode-edit-csv
jan
0.7.1

vscode-docker
ms-
1.22.1

python
ms-
2022.10.1

vscode-pylance
ms-
2022.7.40

jupyter
ms-
2022.6.1201981810

jupyter-keymap
ms-
1.0.0

jupyter-renderers
ms-
1.0.9

remote-containers
ms-
0.241.3

remote-ssh
ms-
0.84.0

remote-ssh-edit
ms-
0.80.0

remote-wsl
ms-
0.66.3

vscode-remote-extensionpack
ms-
0.21.0

live-server
ms-
0.2.12

makefile-tools
ms-
0.5.0

vscode-react-native
msj
1.9.2

vscode-sanddance
msr
3.3.0

autodocstring
njp
0.6.1

vetur
oct
0.35.0

sqlite-viewer
qwt
0.1.5

vscode-data-preview
Ran
2.3.0

biosyntax
rea
0.0.11

open-in-browser
tec
2.0.0

html-preview-vscode
tht
0.2.5

(1 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes516:30244333
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
vscscmwlcmt:30465135
cppdebug:30492333
pylanb8912:30529769
vsclangdf:30486550
c4g48928:30532338

Please use the Start Extension Bisect command to investigate whether the problem is being caused by one of your extensions.

I don't know how to use that extension. I found this "demo", not sure if this is the right one. And there is a website, but it does not explain how to start/use the app. Only for people who already know how to use it, it seems.
https://code.visualstudio.com/blogs/2021/02/16/extension-bisect

Open command palette (e.g. by pressing F1). Start typing "Start Extension Bisect". When the command appears, run it.

Ok, just did that.

Can you check what theme is set in the settings? Look at both the user and the workspace settings.

Ok, I set all the themes to theme black, and now it does not change anymore to the dark theme. Event after restarting the application. Thank you for your time.

Nope, actually, now it switched back to the dark theme, just when I closed this thread.

The theme that I am using is: Jaakko.black
the latest version:

I deleted the Dark theme that was always activated, now it does not change back to it and stays with the Black theme.

It is still happening.

Can you check what theme is set in the settings? Look at both the user and the workspace settings.

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!

To select the theme, I go to Preferences/Color Scheme and select 'Black'.
Under Settings I do not find user nor workspace settings.

Ok, looks like the black theme is properly set.
So, you are saying that suddenly that settings is changed.
These are the things that come to my mind (I'm aware I'm repeating myself)

could be some extension that does that. Run with all extension disabled and see if that makes a difference
could be through settings sync. Disable settings sync on your machine and see if that makes a difference

I wonder how to completely reset VSCode? Apparently something is wrong with the config. But reinstalling it does fix it.

It happened again:


Issue177 reconfigure setup tools

Closes #177.

This was tested on test.pypi : https://test.pypi.org/project/pygfunction/2.1.0.dev1/
pip >=21.1 is now needed to install pygfunction in development (editable) mode:
pip install --editable .


Update Dockerfile example with best practices

Attempts to address the issue Enhance the custom docker base image #58898 (I don't have permissions to link this pull request to that issue).
Helpful links:

Less capabilities, more security: minimizing privilege escalation in Docker
docker-images / Dockerfile

#sign-off       @dkmiller - please open your PRs in the private repo going forward. thank you!

@j-martens: I'm sorry - only the author of this article, @jpe316, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

#please-close
Changes have been merged in #129034 in the private repo and will publish later today.


Facility to disable dynamic libraries

Stock Lua 5.1.5 provides a configuration knob to control usage of dlopen-based functionality. This is on by default when using LUA_USE_LINUX but is still a separate preprocessor symbol that can be manipulated separately.
In Elune, LUA_USE_POSIX is used as a single knob, which makes it difficult/impossible to compile Elune for POSIX while simultaneously disabling dlopen.
This is desirable for Elune installations that wish to statically link all dependencies, in particular to avoid a cranky linker warning, e.g.
/usr/bin/ld: /tmp/wowless.GKA9d8.ltrans4.ltrans.o: in function `unixDlOpen.lto_priv.0':
<artificial>:(.text+0x1218): warning: Using 'dlopen' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking

Perhaps a separate configuration altogether is actually best, to uniformly (irrespective of POSIX or anything else) request the stub ll_ function implementations in loadlib.c.

Let me know if 7fc7271 meets your needs.

Require continues to work; wowless simply disables filesystem checks for .so files for now, and will soon also disable filesystem checks for .lua files, leaving only preloading. https://github.com/wowless/wowless/blob/main/main.c#L39-L43

Also, thanks, this works like a charm. (Unfortunately, lsqlite3 isn't so well behaved.)


jax.flatten_util isn't imported by default

Description
I am unable to access jax.flatten_util.ravel_pytree.
It shows an AttributeError
AttributeError: module 'jax' has no attribute 'flatten_util'

However, I can still do
from jax import flatten_util

What jax/jaxlib version are you using?
0.4.20
Which accelerator(s) are you using?
CPU
Additional system info
No response
NVIDIA GPU info
No response

jax.flatten_util isn't imported by default. Maybe it should be, but right now you should add the import.

Note also that it's not supported as a public API according to the current API compatibility page.

Should we consider moving ravel_pytree to jax.extend?

What is the "extension" case?


A typo in README

There is a typo in README:

// All of the following lines will work not work in "node_modules/installed-baz/index.js"!

Thanks! Fixed


Change :log default for unbounded range scales to :log10

Resolves #677

Codecov Report

Merging #692 (e138472) into for-0-point-19-release (651d80a) will decrease coverage by 0.06%.
The diff coverage is 100.00%.

@@                    Coverage Diff                     @@
##           for-0-point-19-release     #692      +/-   ##
==========================================================
- Coverage                   82.92%   82.86%   -0.07%
==========================================================
  Files                          38       38
  Lines                        2893     2894       +1
==========================================================
- Hits                         2399     2398       -1
- Misses                        494      496       +2

Impacted Files
Coverage Δ

src/hyperparam/one_dimensional_range_methods.jl
81.44% <100.00%> (-1.72%)
:arrow_down:

src/hyperparam/one_dimensional_ranges.jl
74.13% <100.00%> (ø)

src/data/data.jl
92.04% <0.00%> (-0.18%)
:arrow_down:

src/interface/data_utils.jl
86.95% <0.00%> (+0.28%)
: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 651d80a...e138472. Read the comment docs.


add 100% increased crit chance when on consecrated ground

new bonus for 3.6
fixes #1442

+1 this has been bugging me since the change.


Database column type of payload should be VARBINARY, not BINARY

Steps to reproduce

Library version: 1.1.0
JDK version: irrelevant
Operating system: irrelevant
Complete executable reproducer: n/a
Steps: n/a

The type of the payload column in the database table is currently BINARY (in the MyBatis mapper as well as the DDL in the examples), which is a fixed-length data type. This will take up the maximum space for every row, even if the payload is smaller than that. We should use VARBINARY instead.
Workaround: I haven't tried yet, but I think it should be possible to just use VARBINARY in the actual database table, so this is mainly an issue with the examples.

Have you tried?

Yes, I changed it to VARBINARY(MAX) for one of our apps and it seems to work.


irJS and loggingJS lack their crossVersion := ScalaJSCrossVersion.binary

This means that both ir and irJS try to publish under the same artifact name (and same with logging/loggingJS), so publishing to Sonatype (rightfully) fails.
I'm rolling back 1.0.0-RC1 because of this.

Hahahahaha, amazing :P


ARM64 build

there's an x86 and an x64 build, how about an ARM64 build as well?

Prerequisite is that https://github.com/teeks99/boost-release-windows has a arm64 build.

@sergey-shandar Could you please also push the update to this repo for 1.86 as the nuget packages are already updated. Thanks.

Hi @sergey-shandar, sorry to bother you but is there any news regarding ARM build support?

Hi @sergey-shandar, sorry to bother you but is there any news regarding ARM build support?

Hi @stihlwasab, currently, I use Prebuild Binaries from here. There are two reasons:

We shouldn't have two different binary files (DLLs) for the same Boost library.
Building all DLLs requires more investments in computing resources and maintenance time.

@stihlwasab You need to get the maintainer of https://github.com/teeks99/boost-release-windows/issues/5 to work on that topic as this is the basis for the prebuild boost windows packages.


[azeventhubs] Handle session/receiver/sender New/Close function cancellations as connection failures

When a session, receiver or sender creation or close is cancelled it can leave our AMQP connection in an ambiguous state. We treat these cancellations as connection-level failures, and recovery will reset the connection as a result.

/azp run go - azeventhubs

/azp run go - azeventhubs


Rename private messages -> direct messages in mobile documentation

Following up on https://github.com/zulip/zulip-mobile/issues/5731, we should update the help center to use "direct messages" in mobile instructions.
This will affect at least /help/direct-messages and /help/include/send-group-dm.md (check if there's anything else).

@drrosa would be great if you could take care fo this one.


Ember-data version compatibility

Hi,
I run through compatibility issue with the latest version of ember data (2.11.0) and I would like to know if there no other solution than the compatibility table existing in the README.md.
I know that some other ember-addon like ember-modal-dialog handle ember compatibility in their package.json.
Is there no way to write something similar for ember-data-model-fragments?
E.g. for the ember-data-model-fragments v2.3.x it could be something like:
  "ember-addon": {
    "versionCompatibility": {
      "ember-data": ">= 2.3.0 < 2.11.0"
    }
  }

With this, if I'm right, ember install ember-data-model-fragments will lead to the installation of the right version of the addon whatever your version of ember-data is.
PS: I cannot find any documentation on this versionCompatibility it's only supposition

To be honest, I'm not really much of an NPM expert. I think one option would be if this addon moved the ember-data dependency from devDependencies to dependencies and that would force conflict resolution in during npm install. But it doesn't seem like very many, if any, ember addons do this. It seems they keep ember in the devDependencies and I'm not sure if there is a specific reason for that.
I would absolutely accept a PR for adding versionCompatibility to the package.json file.

Actually I saw this PR come through. https://github.com/jamesarosen/ember-i18n/pull/433/files It seems very relevant here. I'll investigate this in the near future when I have time.

@workmanw moving to dependencies would cause a very odd set of bugs because you'd get the merge of the two instead of resolving one or the other.
versionCompatibility is definitely something I'd recommend.


No audio on IOS 12

I don't know if this is just Flutter or this package but it seams like there is no audio on a IOS 12 running device.

You have to have the ringer on or have headphones plugged in

Hey, how did you fix it ?


Incorrect locale for SVG image content

Request type

[ ] New documentation
[x] Correction or update

Details
On the page Basic concepts behind Web Audio API in all the locales, the SVG describing the positioning vectors is displaying text in French.
I amended the SVG and tried to upload it again, however SVG upload has been disabled for non staff.
You will find attached the new SVG here, sorry GitHub does not support SVG upload.
I think we could update the Japanese, Korean and Chinese version as it is more likely that they understand english compared to French.

I don't know if I'm able to upload SVG images either, but I did manage to find the location of the Engish version, and link to that instead.


CDN timeouts

I'm trying to update the pod to version 4.0 but getting timeout issues:
[!] CDN: trunk URL couldn't be downloaded: https://raw.githubusercontent.com/CocoaPods/Specs/master/Specs/a/7/5/AFNetworking/4.0.0/AFNetworking.podspec.json Response: Timeout was reached

Sorry, sometimes this happens. Only thing to do is to check your connection and settings and try again later. If it happens to be a longer term issue, I suggest you file an issue with CocoaPods.

Happening for hours, and is still happening. I don't think it has anything to do with my connection.
The URL causing trouble is githubusercontent.com; it might be a Github issue. I'll try again tomorrow...


[ENHANCEMENT] Upgrade cluster.x-k8s.io/v1alpha4 to cluster.x-k8s.io/v1beta1

Is your enhancement related to a problem? Please describe.
The cluster.x-k8s.io/v1alpha4 will be removed after v1.6. Currently, we use CAPI v1.4.4. We only have 1 minor version to upgrade it.
ref: https://cluster-api.sigs.k8s.io/#-breaking-changes-
Describe the solution you'd like
Upgrade cluster.x-k8s.io/v1alpha4 to cluster.x-k8s.io/v1beta1.
https://github.com/harvester/harvester/blob/c14caf46c92f464cfa556dee08a80175f054b274/pkg/codegen/main.go#L26
https://github.com/harvester/harvester/blob/c14caf46c92f464cfa556dee08a80175f054b274/pkg/codegen/main.go#L191-L205

Verified this enhancement has been applied.
Test Information

Environment: qemu/KVM single node
Harvester Version: v1.4.0-dev-20240830
ui-source Option: Auto

Verify Steps

Same as https://github.com/harvester/harvester/pull/5377#issue-2191084890


Syntax error in postgresql.conf

On master (5c9589dae046f92a273b8c2e4900dff1427df6bf) and team-and-enterprise (25a7c98f7547674852c3d1d3ca28e2720f2a60da) I'm getting syntax errors during docker-compose up for /var/lib/postgresql/data/postgresql.conf
I followed these steps: https://docs.mattermost.com/install/prod-docker.html
team-and-enterprise (25a7c98f7547674852c3d1d3ca28e2720f2a60da)
web_1  | Starting Nginx
db_1   | AWS_ACCESS_KEY_ID is required for Wal-E but not set. Skipping Wal-E setup.
db_1   | LOG:  syntax error in file "/var/lib/postgresql/data/postgresql.conf" line 612, near end of line
db_1   | FATAL:  configuration file "/var/lib/postgresql/data/postgresql.conf" contains errors
db_1   | AWS_ACCESS_KEY_ID is required for Wal-E but not set. Skipping Wal-E setup.
db_1   | LOG:  syntax error in file "/var/lib/postgresql/data/postgresql.conf" line 612, near end of line
db_1   | FATAL:  configuration file "/var/lib/postgresql/data/postgresql.conf" contains errors
db_1   | AWS_ACCESS_KEY_ID is required for Wal-E but not set. Skipping Wal-E setup.
db_1   | LOG:  syntax error in file "/var/lib/postgresql/data/postgresql.conf" line 612, near end of line
db_1   | FATAL:  configuration file "/var/lib/postgresql/data/postgresql.conf" contains errors
db_1   | AWS_ACCESS_KEY_ID is required for Wal-E but not set. Skipping Wal-E setup.
db_1   | LOG:  syntax error in file "/var/lib/postgresql/data/postgresql.conf" line 612, near end of line
db_1   | FATAL:  configuration file "/var/lib/postgresql/data/postgresql.conf" contains errors
db_1   | AWS_ACCESS_KEY_ID is required for Wal-E but not set. Skipping Wal-E setup.
db_1   | LOG:  syntax error in file "/var/lib/postgresql/data/postgresql.conf" line 612, near end of line
db_1   | FATAL:  configuration file "/var/lib/postgresql/data/postgresql.conf" contains errors
db_1   | AWS_ACCESS_KEY_ID is required for Wal-E but not set. Skipping Wal-E setup.
db_1   | LOG:  syntax error in file "/var/lib/postgresql/data/postgresql.conf" line 612, near end of line
db_1   | FATAL:  configuration file "/var/lib/postgresql/data/postgresql.conf" contains errors
db_1   | AWS_ACCESS_KEY_ID is required for Wal-E but not set. Skipping Wal-E setup.
db_1   | LOG:  syntax error in file "/var/lib/postgresql/data/postgresql.conf" line 612, near end of line
db_1   | FATAL:  configuration file "/var/lib/postgresql/data/postgresql.conf" contains errors
db_1   | AWS_ACCESS_KEY_ID is required for Wal-E but not set. Skipping Wal-E setup.
db_1   | LOG:  syntax error in file "/var/lib/postgresql/data/postgresql.conf" line 612, near end of line
app_1  | Configure database connection...SKIP
db_1   | FATAL:  configuration file "/var/lib/postgresql/data/postgresql.conf" contains errors
app_1  | Wait until database db:5432 is ready...
db_1   | AWS_ACCESS_KEY_ID is required for Wal-E but not set. Skipping Wal-E setup.
db_1   | LOG:  syntax error in file "/var/lib/postgresql/data/postgresql.conf" line 612, near end of line
db_1   | FATAL:  configuration file "/var/lib/postgresql/data/postgresql.conf" contains errors
db_1   | AWS_ACCESS_KEY_ID is required for Wal-E but not set. Skipping Wal-E setup.
db_1   | LOG:  syntax error in file "/var/lib/postgresql/data/postgresql.conf" line 612, near end of line
db_1   | FATAL:  configuration file "/var/lib/postgresql/data/postgresql.conf" contains errors

master (5c9589dae046f92a273b8c2e4900dff1427df6bf)
db_1   | LOG:  syntax error in file "/var/lib/postgresql/data/postgresql.conf" line 610, near end of line
db_1   | LOG:  syntax error in file "/var/lib/postgresql/data/postgresql.conf" line 612, near end of line
db_1   | FATAL:  configuration file "/var/lib/postgresql/data/postgresql.conf" contains errors
db_1   | AWS_ACCESS_KEY_ID is required for Wal-E but not set. Skipping Wal-E setup.
db_1   | LOG:  syntax error in file "/var/lib/postgresql/data/postgresql.conf" line 612, near end of line
db_1   | FATAL:  configuration file "/var/lib/postgresql/data/postgresql.conf" contains errors
db_1   | AWS_ACCESS_KEY_ID is required for Wal-E but not set. Skipping Wal-E setup.
db_1   | LOG:  syntax error in file "/var/lib/postgresql/data/postgresql.conf" line 612, near end of line
db_1   | FATAL:  configuration file "/var/lib/postgresql/data/postgresql.conf" contains errors
db_1   | AWS_ACCESS_KEY_ID is required for Wal-E but not set. Skipping Wal-E setup.
db_1   | LOG:  syntax error in file "/var/lib/postgresql/data/postgresql.conf" line 612, near end of line
db_1   | FATAL:  configuration file "/var/lib/postgresql/data/postgresql.conf" contains errors
db_1   | AWS_ACCESS_KEY_ID is required for Wal-E but not set. Skipping Wal-E setup.
db_1   | LOG:  syntax error in file "/var/lib/postgresql/data/postgresql.conf" line 612, near end of line
db_1   | FATAL:  configuration file "/var/lib/postgresql/data/postgresql.conf" contains errors
db_1   | AWS_ACCESS_KEY_ID is required for Wal-E but not set. Skipping Wal-E setup.
db_1   | LOG:  syntax error in file "/var/lib/postgresql/data/postgresql.conf" line 612, near end of line
db_1   | FATAL:  configuration file "/var/lib/postgresql/data/postgresql.conf" contains errors
db_1   | AWS_ACCESS_KEY_ID is required for Wal-E but not set. Skipping Wal-E setup.
db_1   | LOG:  syntax error in file "/var/lib/postgresql/data/postgresql.conf" line 612, near end of line
db_1   | FATAL:  configuration file "/var/lib/postgresql/data/postgresql.conf" contains errors
db_1   | AWS_ACCESS_KEY_ID is required for Wal-E but not set. Skipping Wal-E setup.
db_1   | LOG:  syntax error in file "/var/lib/postgresql/data/postgresql.conf" line 612, near end of line
db_1   | FATAL:  configuration file "/var/lib/postgresql/data/postgresql.conf" contains errors
db_1   | AWS_ACCESS_KEY_ID is required for Wal-E but not set. Skipping Wal-E setup.
db_1   | LOG:  syntax error in file "/var/lib/postgresql/data/postgresql.conf" line 612, near end of line
db_1   | FATAL:  configuration file "/var/lib/postgresql/data/postgresql.conf" contains errors

Same here !
Will update if I find a fix.

yeah I would agree. In the docker-entrypoint.sh in the db folder you could do:
sed -i "s/archive_timeout =.*$/archive_timeout = $ARCHIVE_TIMEOUT/g" $PGDATA/postgresql.conf

But that only moves the ball forward for a second, then you get lots of other errors about missing tables and wal_e dies. Its to bad, I really wanted to evaluate this product for production usage but if I can't ever get the docker container to run I am off to find better solution.

Thanks everyone for reporting this. This should be fixed by this commit https://github.com/mattermost/mattermost-docker/commit/4c30235fdefa16f5e9dd19c2a9a6699cf9647d4a. I'll update the images as well.

@vitosans it is because postgres already past the initialisation stage, so it won't be able to create those tables. You can just remove postgres data files (if you don't have any data). They are under volumes/db if you are using docker-compose

this is my problem, most likely. #31

Still have the error at 6c69e8299849d03aea2a65279e7098e1f5028312
db_1   |
db_1   | /docker-entrypoint.sh: running /docker-entrypoint-initdb.d/make_db.sh
db_1   | CREATE DATABASE
db_1   | CREATE ROLE
db_1   | GRANT
db_1   |
db_1   | /docker-entrypoint.sh: running /docker-entrypoint-initdb.d/setup-wale.sh
db_1   |
db_1   | LOG:  received fast shutdown request
db_1   | LOG:  aborting any active transactions
db_1   | waiting for server to shut down....LOG:  autovacuum launcher shutting down
db_1   | LOG:  shutting down
db_1   | LOG:  database system is shut down
db_1   |  done
db_1   | server stopped
db_1   |
db_1   | PostgreSQL init process complete; ready for start up.
db_1   |
db_1   | LOG:  syntax error in file "/var/lib/postgresql/data/postgresql.conf" line 609, near end of line
db_1   | LOG:  syntax error in file "/var/lib/postgresql/data/postgresql.conf" line 610, near end of line
db_1   | LOG:  syntax error in file "/var/lib/postgresql/data/postgresql.conf" line 612, near end of line
db_1   | FATAL:  configuration file "/var/lib/postgresql/data/postgresql.conf" contains errors
db_1   | AWS_ACCESS_KEY_ID is required for Wal-E but not set. Skipping Wal-E setup.
db_1   | LOG:  syntax error in file "/var/lib/postgresql/data/postgresql.conf" line 612, near end of line
db_1   | FATAL:  configuration file "/var/lib/postgresql/data/postgresql.conf" contains errors
db_1   | AWS_ACCESS_KEY_ID is required for Wal-E but not set. Skipping Wal-E setup.
db_1   | LOG:  syntax error in file "/var/lib/postgresql/data/postgresql.conf" line 612, near end of line
db_1   | FATAL:  configuration file "/var/lib/postgresql/data/postgresql.conf" contains errors
db_1   | AWS_ACCESS_KEY_ID is required for Wal-E but not set. Skipping Wal-E setup.
db_1   | LOG:  syntax error in file "/var/lib/postgresql/data/postgresql.conf" line 612, near end of line
db_1   | FATAL:  configuration file "/var/lib/postgresql/data/postgresql.conf" contains errors
db_1   | AWS_ACCESS_KEY_ID is required for Wal-E but not set. Skipping Wal-E setup.
db_1   | LOG:  syntax error in file "/var/lib/postgresql/data/postgresql.conf" line 612, near end of line
db_1   | FATAL:  configuration file "/var/lib/postgresql/data/postgresql.conf" contains errors
db_1   | AWS_ACCESS_KEY_ID is required for Wal-E but not set. Skipping Wal-E setup.
db_1   | LOG:  syntax error in file "/var/lib/postgresql/data/postgresql.conf" line 612, near end of line
db_1   | FATAL:  configuration file "/var/lib/postgresql/data/postgresql.conf" contains errors
db_1   | AWS_ACCESS_KEY_ID is required for Wal-E but not set. Skipping Wal-E setup.
db_1   | LOG:  syntax error in file "/var/lib/postgresql/data/postgresql.conf" line 612, near end of line
db_1   | FATAL:  configuration file "/var/lib/postgresql/data/postgresql.conf" contains errors
db_1   | AWS_ACCESS_KEY_ID is required for Wal-E but not set. Skipping Wal-E setup.
db_1   | LOG:  syntax error in file "/var/lib/postgresql/data/postgresql.conf" line 612, near end of line
db_1   | FATAL:  configuration file "/var/lib/postgresql/data/postgresql.conf" contains errors
db_1   | AWS_ACCESS_KEY_ID is required for Wal-E but not set. Skipping Wal-E setup.
db_1   | LOG:  syntax error in file "/var/lib/postgresql/data/postgresql.conf" line 612, near end of line
db_1   | FATAL:  configuration file "/var/lib/postgresql/data/postgresql.conf" contains errors```

I'm not a maintainer, but I would say wait for next release

@activedecay the patch was already released on master (4c30235fdefa16f5e9dd19c2a9a6699cf9647d4a) and the issue is still here.

@th3m4ri0 Does it work now?

It does ! Sorry for the trouble.

No worries.

For anyone who is still experiencing the issue, it's probably because the team-and-enterprise branch doesn't have this patch yet; go to https://github.com/mattermost/mattermost-docker/commit/4c30235fdefa16f5e9dd19c2a9a6699cf9647d4a and copy-paste the patch yourself, run docker-compose build and docker-compose up -d and you should be all set.