Allow setting initial state to Application on runtime?

Hi, I'm interested in running iced in vst-rs environment.
To create VST plugin, we need to share some variables between plugin and GUI to sync states. But Application is initialized in new method and there is no way to set external state to Application on runtime as far as I know.
Please considering introduce some mechanics that enable us to set an initial state to the Application trait on runtime.
Thanks.

Seconded, I also very much need this.

Application::run is static because this way users cannot easily obtain an Application instance before running it. This guarantees that:

The application cannot been altered prior to running it.
The runtime will be the only one with access to it for its entire lifetime.
We can feed runtime parameters to Application::new (like initial window size).

I think an additional associated type may work here. It could be provided as part of Settings and would be given to Application::new. I'll think about it!
I'd also be helpful if you could describe your use cases a bit more. What kind of configuration or initial state do you want to set?

It would also be helpful if you could describe your use cases a bit more. What kind of configuration or initial state do you want to set?

Yeah, as I told, I'm using iced to create a VST plugin.
An example project is here.
https://github.com/hatoo/vst-rs-example-iced
Currently, I'm using a modified version of iced now to adapt VST API.
https://github.com/hatoo/iced/tree/run_generator
You can view the diff on https://github.com/hecrj/iced/compare/master...hatoo:run_generator
The change is adding run_geenrator method which receives self and returns Generator of event loop to iced_winit::Application. (Generator is a Nightly feature. It's why I didn't make PR of this. )
    fn run_generator(
        self,
        init_command: Command<Self::Message>,
        settings: Settings,
    ) -> Box<
        dyn std::marker::Unpin + std::ops::Generator<Yield = (), Return = ()>,
    >
    where
        Self: 'static,

The configuration I want to initialize is Arc of parameters that share with VST plugin.
The parameters can be modified by both GUI and Plugin host.

I ran into the same problem, where I'd like to pass in some state into my application before running it, which is currently only possible with a global (example here). One reason that I want to pass in state is to be able to store references in the application to some state to do data binding (example abstraction - note: I'm experimenting here, no idea if this is a good way of doing this). However, that would create a self referential struct which is painful/impossible in Rust. I don't have enough experience with self referential structs to know if this is possible some other way though.
In general, I think it should be possible to pass non-'static state into applications. For example, command-line arguments should be passable into the application without a global.
I understand the guarantees from points 2 and 3 are important, but would these also not hold when run takes self and having an init method? I don't understand why point 1 is needed though, why should an application not be modified before running it?

Precisely, both of the approaches you are mentioning are what the current design is meant to forbid.
Sharing state with another part of you application by using interior mutability will simply not work as intended. In fact, I believe you should rarely do that in Rust. When you do, you are giving up on a lot of nice guarantees that the borrow checker gives you at compile time and, as a consequence, opening a door for a lot of pesky bugs.
All the changes to Application state should happen in the update logic through messages. This is a main foundation of The Elm Architecture. Iced will not work properly otherwise. Obviously, Iced won't magically redraw the screen if you update application state externally. This may not be very apparent right now, but it will be once we start implementing different kinds of optimizations.
While I agree we should allow initial configuration flags to be provided, I think they should never be used to setup shared state with interior mutability.
So, how should users share state externally when using iced? I believe the best approach is to build a communication layer between the parts that need synchronization. Elm achieves this with ports, or basically a channel of messages. It's a strategy that works really well with the current reactive architecture and should be possible once event subscriptions land very soon.
Of course, you are free to use iced_native directly and build your own event loop on top of some other guarantees to satisfy your use cases (I think there is a lot of room to improve this process and I would appreciate exploration!). But the iced crate will most likely never encourage or support sharing state with interior mutability directly.

@hatoo About the run_generator, I am guessing you need the event loop to return to integrate it properly with VST. Could you share a bit more details about this? What are you doing between iterations?

Since a child window's event must be handled in the same thread with parent window's thread by WinAPI's limitation, in other words, we cant run event loop in spawned thread.
So vst-rs provides Editor::idle method to implement which is called periodically to handle events in the same thread.

What are you doing between iterations?

It's about control flow. For each iteration, the generator poll and handle remaining events and return control after that by using winit::event::EventLoop's run_return method .

I think we could implement something similar to Elm's flags: https://guide.elm-lang.org/interop/flags.html
I will tackle this soon!

Allowing one to pass run() a WindowState type augmented with custom fields plus having that WindowState type passed to the Application instance constructor would allow all initial state to be passed in without the use of globals.
In my case, adding a title field to the WindowSettings object passed into Application::run() and using it as the initial state would address the (small) issue I've run into (but would have implications to the Application::title() API).

#246 should satisfy most of the use cases described here.
As always, feel free to provide any feedback.

@hatoo
How is the VST project going ?
I currently am researching on how to do a VST3 project using iced (in fact iced-table).
VST(2) software is not allowed to be distributed by those who did not years ago do an agreement with Steinberg. They don't provide VST2 licenses, any more, while VST3 seemingly is kind of "open".

@mschnell1
Hi, I haven't played with VST these days, but https://github.com/robbert-vdh/nih-plug seems promising.
I guess we can run any winit based GUI by setting parent window handle and using https://docs.rs/winit/latest/winit/platform/run_on_demand/trait.EventLoopExtRunOnDemand.html#tymethod.run_on_demand
But I'm unsure because winit seems to have many updates and I haven't followed those.

Thanks for additional pointers !


WPИ-XM Control Panel all buttons permanently redirecting to web interface on port 80

When changing nginx port form standard 80 to, for example, 81, the  WPИ-XM Control Panel's 'web interface' button and other button's all the same open's localhost:80, instead of opening localhost:81. Maybe it is need to add some parsing to nginx.conf?
P.S.: thanks for fixing bug with 7z.exe on win8, now 0.8.2 build works fine on windows server 2012 ;)

P.S.: thanks for fixing bug with 7z.exe on win8, now 0.8.2 build works fine on windows server 2012 ;)

Still not sure, what the real difference between 7z and 7za is
and why 7z works on WinXP & Win7 and stops working on Win8.
But anyway, it's working now. Thank you very much for reporting it.

Maybe it is need to add some parsing to nginx.conf?

You are right, Anton.
The port needs to be fetched from the main server block of nginx.conf.
And all the links need to take these ports into account.
Currently the values for the server ports and the button links are hardcoded.
It's already on my roadmap to add a port configuration tab to the configuration dialog, see #327.
The port values are then written to nginx.conf and wpn-xm.ini (as the central config file).

Closed, because this issue is part of the work of issue #327.


Various issues when package name differs from directory name.

[x] I am on the latest Poetry version.
[x] I have searched the issues of this repo and believe that this is not a duplicate.
[ ] If an exception occurs when executing a command, I executed it again in debug mode (-vvv option).

OS version and name: maOS 10.14.6
Poetry version: 1.0.0b1
Link of a Gist with the contents of your pyproject.toml file: https://gist.github.com/KelSolaar/c2c853ca329899534494e2ddf8a1aa96

Issue
This relates to https://github.com/sdispater/poetry/issues/705 but I'm not able to solve all my issues without massaging a few things. The PyPi package name of my project differs from the actual python package name:

colour-science for the PyPi package.
colour for the internal python package and same for the Github repository.

My pyproject.toml file was originally working fine when using colour for the name attribute:
[tool.poetry]
name = "colour"

When trying to build with poetry build, I noticed that it was generating a colour.0.3.13.tar.gz archive that would not work for PyPi, thus I changed the TOML file as follows:
[tool.poetry]
name = "colour-science"
packages = [
    { include="colour", from="." },
]

I was able to build, but now, after cloning the repo into a default colour directory, issuing poetry install creates a virtual environment with the colour-science prefix however the poetry env info -p command does not find the virtual environment because I'm assuming it is looking for an environment with the colour prefix instead.
So there is a consistency issue between how the name of the candidate virtual environment is generated with the poetry install command and the poetry env one.
It also seems like it would be useful to have an attribute to handle the PyPi distribution name explicitly.
Cheers,
Thomas

So looking at the 1.0.0b1 code for getting the environment:
https://github.com/sdispater/poetry/blob/1caf20a291d3a494ab815a9b2746d2f152abb893/poetry/console/commands/env/info.py#L17 It looks like it is indeed relying only on the directory name to find the environment and not the name attribute value from the pyproject.toml file.

I did some digging through the code and must say I'm quite confused by the EnvManager class. Its create_venv method is the only method that will - when supplied with name=poetry.package.name - correctly do what its supposed to: create an environment based on the package name defined in the poetry file. BUT, if a venv with the name of the directory of the package also exists, it will always just pick that venv instead of using the correct package name, even if the name is supplied to the method. This seems like a (very much related) bug to me.
The other methods don't even have a name argument and will always just use the directory name to build the environment name. If no environment based on the directory name exists, they will usually just use the system python.
All Commands that are derived from EnvCommand do get a virtual environment through this EnvManager class, but only indirectly through the PRE_HANDLE dispatch event handlers. Basically, the application_config.ApplicationConfig sets up the ApplicationConfig.set_env() method as an event listener, which in turn calls the EnvManager.create_venv() method to supply each EnvCommand with an environment. This event listener is called right at the start  The call to create_env() contains the name=poetry.package.name, which is why the commands mentioned in #1425 work correctly,  while the poetry env commands do not.
Some commands like poetry init and poetry new use EnvManager.get(cwd) just to get the system Python to then check the python version. Meanwhile, the EnvManager.activate(), deactivate(), remove() and list() methods only get called by the poetry env commands. Short term, all of these probably should be changed to accept an (optional?) name attribute which will in turn be used instead of cwd to create the venv name. Long term, it might be a good idea to rethink the API of this whole class because it's confusing and non-intuitive.
I might take a stab at fixing this but I'm happy for all feedback and help as I'm quite new to the code base. Especially happy for help with writing the corresponding unit tests.

The environment name issue has been fixed in #1477


[WIP] Add text instruction parsing via osrm-text-instructions

First pass at integrating https://github.com/Project-OSRM/osrm-text-instructions.js
Todo:

[ ] Find better way to integrate custom logic in leaflet-routing-machine
[ ] Wait until https://github.com/Project-OSRM/osrm-text-instructions.js is stable and handles all possible cases
[ ] Wait for https://github.com/Project-OSRM/osrm-text-instructions.js to be bumped to a stable-ish version
[ ] Merge

For comparison, here are old (left) and new (right) instructions side by side:

osrm-text-instructions has made progress in the last weeks and feels fairly stable now. There are def more cases we want to support, but it's good enough for the basic case here. To get more feedback we'd love to get it live on map.project-osrm.org now.
I also continued on the hacky path to get lanes support in.
It's not pretty, but works a bit. The problem with integrating with LRM is that during the HTML building, I need access to the original step object from OSRM to decide on lanes. Since the other supported routing engines do not support lanes, Im not sure if this should become a LRM-supported function. If so, it will need quite a lot of refactoring on the LRM side.
Old Left, New Right

I released<EMAIL_ADDRESS>which includes destinations as well, so I think it's ready to go for now.

@perliedman I'd love to find ways of getting this work upstream into LRM. Likely integrating osrm-text-instructions will be easy-ish, since it's only some text. But lanes are harder, since they need the original step.intersections.lanes while building the html. I couldn't find easy ways of integrating them, so need to defer back to you on that.
I'll merge this hacky version for now to get the feature out. Let's continue to discussion on how to make it better :)


Support multiple routes in the same file

Please describe the feature that you want to propose
Sometimes files contain more than one route.
Example of single route:
- from:
    uri: "timer:yaml"
    parameters:
      period: "1000"
    steps:
      - set-body:
          constant: "Hello Camel K from yaml"
      - to: "log:info"

Example of multiple routes:
- from:
    uri: "timer:yaml"
    parameters:
      period: "1000"
    steps:
      - set-body:
          constant: "Hello Camel K from yaml"
      - to: "log:info"
- from:
    uri: "timer:anotherone"
    parameters:
      period: "50000"
    steps:
      - set-body:
          constant: "Nobody expects the second route!"
      - to: "log:info"

The frontend right now is not considering a second route may be available on the same file.
We may need a dropdown with the list of routes in the file. But then, the source code we see will not be the complete list of routes. Or would it?

I think this is a must.
it helps organised code and improve readability

Most of the Camel I write has multiple routes. I'd like to add that if we create directs it would be nice to have a dotted line between those routes showing their connection.

Related issue #1711


Provides a default Grafana dashboard

Part of https://github.com/kubeflow/tf-operator/issues/1340
Let's create a default Grafana dashboard once #1375 is done. That would be helpful for operator maintainers to understand workloads in the cluster

/area enhancement
/help
/good-first-issue

I will take this up @Jeffwan for post 1.4

/assign

@deepak-muley Any progress/updates on this?


Missing 'nil' in inferred type of function

Environment

Name
Version

IDEA version
CL2022.2

Luanalysis version
1.3.0

OS
Windows 11

Preferences

Name
Setting
Remarks

Language level
5.3

Strict nil checks
☑ / ❎
both trigger the bug

What are the steps to reproduce this issue?
local function return_inconsistent(name)
  if name == "" then return end
  return {}
end

return_inconsistent("")

What happens?
The inferred return type of the function is table.
What were you expecting to happen?
The inferred return type of the function is nil | table or () | table.
There is a warning that The function 'inconsistent_return' sometimes returns a value. (Don't know whether that would be practical in general though.)

This is unfortunately a complicated case. The return type of that function isn't actually nil | table, it's void | table.
The problem is void is the absence of a value i.e. the empty set. When you put it in a union, it makes no contribution: https://github.com/Benjamin-Dobell/IntelliJ-Luanalysis/issues/45
I'd have to change the representation of void at a pretty low level to make this work.
In this case if you actually want nil | table, then you ought to be able to change the return statement to return nil rather than nothing.

Ah, that's tricky indeed. Feel free to close it as a duplicate then.


Switch to isomorphic-unfetch

When using vite as a bundler, it complains a ton about using node fetch. Isomorphic unfetch allows it to use node-fetch on server side, with unfetch on client side.

It would appear that mocking it is strange though. Tests fail for mock issues, seems to work fine when actually using it.


Smart Banner usage question

Hi I am testing the smart banner usage and couldn't get it to work.  This is my banner call:
 branch.banner({
    icon: 'http://icons.iconarchive.com/icons/wineass/ios7-redesign/512/Appstore-icon.png',
    title: 'Branch Demo App',
    description: 'The Branch demo app!',
    openAppButtonText: 'Open',
    downloadAppButtonText: 'Download',
    iframe: true,
    showMobile: true,
    showDesktop: true
}, {
    type: 1,
    data: {
        mydata: 'something'
    }
});

But I am seeing the following error in the Chrome desktop browser console and also in android chrome browser logs (adb log):
Uncaught TypeError: Cannot read property 'addEventListener' of null        branch-v1.0.0.min.js:15
 ba                                    branch-v1.0.0.min.js:37
U.banner                           branch-v1.0.0.min.js:37
(anonymous function)       branch-v1.0.0.min.js:37
(anonymous function)

Thanks for the report – we're looking into this right now.

@dm77 we've just released v1.0.1, which fixes this. just update your init script to point to https://cdn.branch.io/branch-v1.0.1.min.js and it should work!

Confirmed. Works well now. Thanks so much for the quick fix.

Great to hear, let us know if you run into any other issues


[WIP]RESTORE interface of object

change:
RESTORE interface of object
Review：
@wisererik @leonwanghui @anvithks

@jimccfun  Closing this PR as it is quite old.
If we need to add this feature we can create a new PR.


RuntimeWarning: numpy.ufunc size changed, may indicate binary incompatibility.

After upgrading from 13.0 to 13.1 and Rasa Core from 0.9.0 to 10.4 I get a warning:
C:\Users\Anaconda3\envs\master\lib\importlib\_bootstrap.py:219: RuntimeWarning: numpy.dtype size changed, may indicate binary incompatibility. Expected 96, got 88
  return f(*args, **kwds)

@ctrado18 is this when loading a model? Rasa core 0.10 is a major update with backwards, incompatible changes, see the changelog and migration guide

Please see discussion: https://stackoverflow.com/questions/40845304/runtimewarning-numpy-dtype-size-changed-may-indicate-binary-incompatibility


[templates/default]: layouts for pages

Classic docs and unstyled layouts for pages
Tasks from #8

This PR adds support for pages to have different layouts if specified in frontmatter. There are two layouts unstyled and docs
Tasks

[x] Frontmatter field layout: ... (defaults to 'docs' if not specified)
[x] Layouts folder with 'unstyled' and 'docs' - layouts/unstyled.js & layouts/docs.js
[x] demo pages

Previews

Two demo pages in markdown content/demo

unstyled at /demo
docs at /demo/docs

@khalilcodes again just want to acknowledge the absolutely perfect PR description - all the info i need, convenient links etc.


Allow ignoring repos from being synchronized

I've added a config test, but for the actual functionality all I can say is that I've tested it, and trust me bro.
Fixes #11

Thanks! Sorry for the delay


Fails to Load on 2021.8.0 published version

Getting "(!) Not Loaded" for the Ecowitt Integration.  Worked flawlessly for me prior to installing HA 2101.8.0.
Logs:
2021-08-04 09:29:39 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration ecowitt which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-08-04 09:29:39 ERROR (SyncWorker_1) [homeassistant.loader] The custom integration 'ecowitt' does not have a valid version key (None) in the manifest file and was blocked from loading. See https://developers.home-assistant.io/blog/2021/01/29/custom-integration-changes#versions for more details
2021-08-04 09:29:43 ERROR (MainThread) [homeassistant.setup] Setup failed for ecowitt: Integration not found.

We had this issue a while ago you need to add version no in and then you will have a issue about "volt" fix that and it should be all good ! Look through older issues and it tells you how to fix both issues.

Issue 68 resolved it for me. Renamed all VOLT to ELECTRIC_POTENTIAL_VOLT in const.py file

Made the changes in Issue 68 and it leaves me with the same error. Where it refers to "<" as the error, is that a proxy for something else?
I had done the version change before.
And just as I am typing this a version core-2021.8.2 has just dropped. I will try that.

Issue 68 resolved it for me. Renamed all VOLT to ELECTRIC_POTENTIAL_VOLT in const.py file

This also fixed it for me in the 2021.8.2 version. :)

I might have spoken too soon. Out of interest I tried a restart..... same error comes up.
Ecowitt might have to go.

I might have spoken too soon. Out of interest I tried a restart..... same error comes up.
Ecowitt might have to go.

Hmm, I made the changes and did a restart (shutdown host) and everything booted fine without errors.

It works but you have to replace every instance of VOLT and change nothing else.  Easy to make a mistake here.

I used search & replace, watching out for not changing the instances of "VOLTAGE" in stead of "VOLT".

I fixed both update issues too BTW, I did not need to uninstall & reload the Ecowitt Integration, just edited const.py and manifest.json and restarted HA server.

I fixed both update issues too BTW, I did not need to uninstall & reload the Ecowitt Integration, just edited const.py and manifest.json and restarted HA server.

Which version did you enter in manifest.json? I originally had "1.0.0" but then changed it for the reinstall to what it says on GitHub - "0.5.0".
Also in that file I notice in the fix suggested by @jonootto he increases the value here from 0.11 to 0.12:
"requirements": [
    "pyecowitt==0.12"

The top half of my manifest.json as is right now...
{
"domain": "ecowitt",
"name": "Ecowitt Weather Station",
"version": "7.5.1",
"config_flow": true,
"documentation": "https://www.home-assistant.io/integrations/ecowitt",
"requirements": [
"pyecowitt==0.11"

Thanks
I've been following something on the "official" GitHub and it looks like there are bigger issues effecting sensors. (eg: Picks up the Envoy solar PV system) There is another update in the works - hopefully in the next 24 hours.

Is that something to do with Statistical Graphs in Lovelace ?
I tried to add indoor & outdoor temp, but the entities are not listed.
A note links me to:
https://developers.home-assistant.io/docs/core/entity/sensor/#long-term-statistics

https://github.com/home-assistant/core/pull/54142
based on:
https://github.com/home-assistant/core/issues/54104#issuecomment-894202280

And core-2021.8.3 is out

In case someone, like me, wants to add the integration for the first time and it does not show up in the Integrations list, no matter if you add version number and edit const.py, add it to your configuration.yaml:
ecowitt:
  port: 4199

This will make the integration show up under configured integrations.

In case someone, like me, wants to add the integration for the first time and it does not show up in the Integrations list, no matter if you add version number and edit const.py, add it to your configuration.yaml:
ecowitt:
  port: 4199

This will make the integration show up under configured integrations.

Thanks Muster,
Adding a version number and changing VOLT to ELECTRIC_POTENTIAL_VOLT was not enough for me. Adding ecowitt  in the configuration.yaml fixed it for me in 2021.8.3

Thank you everyone...
Issues 65 and 68 did help but I had similar situation as Steve2017 had where once I rebooted I lost all my Ecowitt devices. What I figured out was that I already had a version entry ("version": "7.5.1",) in my manifest.json file and I added "version" : "0.5.0", towards the top of the file as shown in an early post to that issue, resulting in me having two version entries.  Took out the original version 7.5.1 string and following a reboot, Ecowitt works fine.   Since I had a version string already, it is possible I didnt need to add or replace mine, but happy to have it work whatever version number is referenced.

Thank you everyone...
Issues 65 and 68 did help but I had similar situation as Steve2017 had where once I rebooted I lost all my Ecowitt devices. What I figured out was that I already had a version entry ("version": "7.5.1",) in my manifest.json file and I added "version" : "0.5.0", towards the top of the file as shown in an early post to that issue, resulting in me having two version entries. Took out the original version 7.5.1 string and following a reboot, Ecowitt works fine. Since I had a version string already, it is possible I didnt need to add or replace mine, but happy to have it work whatever version number is referenced.


Refactor: No more need for files-type-section.

It is possible to build such a visualization with os-dashboards, so we definitely don't this this development any more. That's why I want to remove it now.
Quick info, how to create sth. like this in OS-Dashboard: After creating a pie-visualization, you can use the bucket function on the right-hand side. Use the term-option.

works after merging everythin else


Clean-up problem handling in Table Java helper libraries

Introduction
While working on #7509 I've realised our system of aggregating 'problems' in the Java helper libraries has accumulated a bit of technical debt.
It has grown in complexity to the point where we have multiple Problem Builders/Aggregators, two types called WithProblems and for practical reasons I have added a third one - WithAggregatedProblems. That is mostly because the main WithProblems was working with List<Problem, whereas a lot of our operation return an AggregatedProblems instance. The two can be converted between each other, but AggregatedProblems -> List<Problem> will loose information (more on this later).

In general, I think we should try to slightly unify our handling of problems. The major issue of the 'non-unification' is that it is not that easy for more complex operations of which multiple sub-tasks can report problems have it hard to merge all these problems together. Firstly, it's complicating the code if we need to convert a List<Problems> into AggregatedProblems and as noted above the converse is not really possible without loss of information - that is because AggregatedProblems may be limiting the amount of problem instances retained (to conserve resources) and it will only keep an overall count of additional problems that were skipped. This count is checked back in Enso and Additional_Warnings is attached to account for these.
The other issue is that we have some objects that have a getProblems getter (e.g. Table, and I have added a similar concept to Builder). This is bad for two reasons:

from architecture PoV, this is a bit ugly, because the problems are not really semantically associated with the particular value, but with the act of creating that value (e.g. the warning about truncation of data is not a property of the table itself, but of the operation that created this table). This is not a practical issue, but more of a philosophical one.
The more practical problem is that - it is very easy to use this value for further processing and completely discard/forget about the problems that are attached to it. In fact, I'm guilty of this - we use builder.seal in many places and in many of them I don't do propagate the problems that are associated with the builder to the result. I did this because adding this propagation would mean modifying lots of our code and would take much more time. For now I chose where we need to propagate and where for now this is not necessary. But as we add more kinds of problems to be reported, such holes may cause loss of warnings - a warning could be detected but could not 'survive' to be propagated to the user.

Ideally, I wanted to handle this as part of #7509, especially as some of these 'architectural regressions' are newly added in this PR (but some of these issues are existing already). I started implementing it, but realised to properly unify the problem handling requires to 'touch' almost every place of the std-table library and it will simply take a lot of time. There's no hard challenge to it - it just needs some patience. I realised that the task of my current PR can be realised just 'continuing' the path of existing problem handling and doing the 'bad stuff' like adding another WithAggregatedProblems type next to WithProblems and sometimes discarding the Builder's getProblems data. I just knew the solution I'm working on will still work well, and to do this properly requires a bigger refactor. So I decided it's better to split this into two - the PR will rely on these 'workarounds' that are not exactly cleanest code but get the job done, and we can plan to do this task as follow-up to improve the overall codebase - whenever we have time for this.
Proposed steps
Above I have highlighted the two main issues we currently have:

Multiple 'ways' of storing problems - we have WithProblems in std-base and a similar but different WithProblems in std-table, and now I have added a yet another WithAggregatedProblems. Ideally, I think we should keep only WithAggregatedProblems that allows for easy aggregation of problems. We may have to slightly change its API to make it more universal, but in general it will allow us to merge problems for many sources in the easiest way.
Problems as properties of values/helpers that are too easy to ignore. Currently Table.getProblems and Builder.getProblems are showing this issue. We should not be returning an object like Table that contains its own problems. Neither Builder.seal should return a raw storage and allow to query for problems separately. Whenever we 'finish' some operation (like building a Table to be returned or sealing a column builder), we should return a value clearly indicating that there may be problems attached, e.g. WithAggregatedProblems<Table>. This way it is easier to remember that we should propagate these problems from such a return value. Many places already do this, but some yet don't.

Moreover, we should make it a bit easier to aggregate problems. We currently have AggregateProblems.merge and that is good, but we likely need to adapt it a bit to make it easier to merge problems from multiple sub-tasks.
With all that, the problem handling should be a bit easier to understand and manage.
Additional considerations
As mentioned at the beginning we also have many different types of 'aggregators'. We may want to think if we can unify them, but we have to be careful - it may be good to have specialized variants as they allow us to be more efficient. We just need to ensure it is easy to then make sure that any problems reported by them can be easily propagated 'downstream'.
Problem Context
Another issue that could be worth looking into when improving the system is providing necessary context for building the problem. For example, when I added the LossOfIntegerPrecision error, ideally I wanted to also add a column name to it, to make it easier to understand where the error is coming from. However, in the codepaths that lead to creating this problem instance, the column name was just not yet available. E.g. the Storage and its Builder do not know the Column name as that is the 'job' of the column. But they are the ones creating such problems. We should think if we can give them this contextual information, or if we should 'enrich' existing problems with additional context in more outer layers.
Either way, ideally, the Loss_Of_Integer_Precision reported in Enso should contain a column_name.

The test for Loss_Of_Integer_Precision column names:
diff --git a/test/Table_Tests/src/In_Memory/Lossy_Conversions_Spec.enso b/test/Table_Tests/src/In_Memory/Lossy_Conversions_Spec.enso
--- a/test/Table_Tests/src/In_Memory/Lossy_Conversions_Spec.enso	(revision 50c05b5330648d8d53942e8e3e6a5ca62c1be81d)
+++ b/test/Table_Tests/src/In_Memory/Lossy_Conversions_Spec.enso	(revision fd00ea46ba3ff9902139a31c9cca8c10444cad1d)
@@ -32,6 +32,7 @@
             w.example_value.to_text . should_equal y.to_text
             w.example_value_converted.to_text . should_equal (y+0.0).to_text
             w.affected_rows_count . should_equal 1
+            w.column_name . should_equal "X"

             t2 = table_builder [["X", [1, 2, 3, 100, 1000, x]]]
             c3 = t2.at "X" . cast Value_Type.Float
@@ -48,6 +49,7 @@
             w2 = Problems.expect_only_warning Loss_Of_Integer_Precision c4
             w2.to_display_text . should_contain "too large to represent exactly"
             w2.affected_rows_count . should_equal 4
+            w2.column_name . should_equal "Z"

         Test.specify "should be reported in Column.from_vector and Table.new" <|
             c1 = Column.from_vector "X" [1, 2, x, x+1, x+2, 100]
@@ -58,6 +60,7 @@
             w2 = Problems.expect_only_warning Loss_Of_Integer_Precision c2
             w2.affected_rows_count . should_equal 1
             w2.example_value . should_equal x+1
+            w2.column_name . should_equal "Y"

             t3 = Table.new [["X", [1, x, x+1, 1.5]]]
             w3 = Problems.expect_only_warning Loss_Of_Integer_Precision t3
@@ -106,6 +109,7 @@
             w = Problems.expect_only_warning Loss_Of_Integer_Precision r
             w.affected_rows_count . should_equal 1
             w.example_value.to_text . should_equal (x+1).to_text
+            w.column_name . should_equal "if [C] then [A] else [B]"

         Test.specify "should be reported when reading a CSV file" <|
             t = (enso_project.data / "lossy_int.csv") . read
@@ -115,7 +119,8 @@
             t.at "Y" . value_type . should_equal Value_Type.Float
             # Loss of precision here - the 3rd value is really x+1
             t.at "Y" . to_vector . should_equal [1, x, x, 1]
-            Problems.expect_only_warning Loss_Of_Integer_Precision t
+            w = Problems.expect_only_warning Loss_Of_Integer_Precision t
+            w.column_name . should_equal "Y"

             # No loss of precision if Mixed type is used early enough:
             t.at "Z" . value_type . should_equal Value_Type.Mixed

Greg & Radek Discussion
Main problems to solve

We have many different problem builders which should be combined into a unified approach
Each way of handling / aggregating problems is slightly different
Using multiple kinds of problem builders in the same code path requires extra code to combine them
Problems are (sometimes) attached to values, so some objects need their own problem builders while others don't
The developer has to take care to propagate problems anywhere they arise, making it easy to lose problems

Alternative solution

Instead of combining / unifying the current builders, possibly take a different approach
Define builders which wrap around a computation, so that any problem generated during the computation will be held by the builder
Allow for child builders to wrap around a subcomputation, after which the problems are automatically merged with the parent's problems. Unless:
Allow builders to have custom logic for particular computations. For example, arithmetic errors when operating on a large column would generate too many problems; in this case, we want a count of them problems, and also the first few problems to show the user, but no more
The child/parent architecture means that we don't have to distinguish between top level and lower level computations, since a problem builder works the same way whether it is at the top level, or the child of another problem bulider
We can associate problems with any value, without worrying about whether the downstream consumer of the value will check for problems, since problems are never forgotten. We don't need to explicitly add problem aggregators to certain important classes

One limitation of this alternative approach is that there is no way to 'drop' some problems. If a problem is reported, it will surely get to the top. We cannot report it conditionally, based on some result.
However, I don't think it is a big issue. It is quite a natural effect of also the biggest advantage of that approach - in that it is impossible to 'forget' to forward a problem (because the structure of dependencies is created when starting the computation, not afterwards).
If we ever really need to explicitly drop some problems we can:

create a blackhole problem builder that forgets them and is disconnected from top-level;
create some kind of conditional problem builder that can be disconnected after computing a result and deeming that the problem should not be reported after all.

However, for now I don't think this affects us in any way and we will be able to find good solutions whenever needed.
I think all in all the alternative solution gives us much better guarantees of not forgetting about handling some problems and likely should simplify the code too.

Yes, I think you're right -- there are cases when a child builder might attach a problem that we don't actually want the user to see. I think it's valid for the calling code -- perhaps within a parent builder, or perhaps not -- to inspect and modify the set of problems that were collected. For example, a child builder might return all problems found, and not summarize them, but the parent might know that that is too much information, and rewrite the set of problems to be a summary. This is a more rare case, but it still prevents losing any problems by accident.

Design document: https://github.com/orgs/enso-org/discussions/7738


Added small table variant website doc

Checklist
(Check off all the items before submitting)

[x] Build process is done without errors. All tests pass in the /lib directory.
[x] Self-reviewed the code before submitting.
[x] Meets accessibility standards.
[x] Added/updated documentation to /website as needed.
[x] Added/updated tests as needed.

Description
Updated documentation with #1829 changes (wait for lib update)

Will be open once ActionCells (#1836) is merged

Have to be updated documenting the tokens from #1851.


Added structure for easily adding block to gui

The idea is the TimelinesGridPane grid in RootCenterArea contains all the gui block. If another shot must be added, make a CameraShotBlock and call grid.addCameraShotBlock(block) to add. An eventhandler can be attached by calling block.attachHandler to be notified when a block has been updated in the gui.

Nice work! Can merge when build is green


Building WASM sample project fails in case the project path name holds blanks

I'm submitting a...

Bug report (I searched for similar issues and did not find one)

Current behavior
Building the WASM head of the sample project as per here fails if the project path holds blanks (not sure if there is a similar issue on other non-alphanumeric characters).
Here is the exception in VS output (note the truncated path name in the exception message):
1>C:\Users\DDroth.nuget\packages\uno.wasm.bootstrap\1.0.0-dev.137\build\Uno.Wasm.Bootstrap.targets(101,3): error :
1>C:\Users\DDroth.nuget\packages\uno.wasm.bootstrap\1.0.0-dev.137\build\Uno.Wasm.Bootstrap.targets(101,3): error : Unhandled Exception: System.Exception: Could not resolve C:\Users\DDroth\Documents\Visual
1>C:\Users\DDroth.nuget\packages\uno.wasm.bootstrap\1.0.0-dev.137\build\Uno.Wasm.Bootstrap.targets(101,3): error :    at Driver.Resolve(String asm_name, AssemblyKind& kind)
1>C:\Users\DDroth.nuget\packages\uno.wasm.bootstrap\1.0.0-dev.137\build\Uno.Wasm.Bootstrap.targets(101,3): error :    at Driver.Run(String[] args)
1>C:\Users\DDroth.nuget\packages\uno.wasm.bootstrap\1.0.0-dev.137\build\Uno.Wasm.Bootstrap.targets(101,3): error :    at Driver.Main(String[] args)
1>C:\Users\DDroth.nuget\packages\uno.wasm.bootstrap\1.0.0-dev.137\build\Uno.Wasm.Bootstrap.targets(101,3): error : System.Exception: Failed to generate wasm layout
1>C:\Users\DDroth.nuget\packages\uno.wasm.bootstrap\1.0.0-dev.137\build\Uno.Wasm.Bootstrap.targets(101,3): error :    at Uno.Wasm.Bootstrap.ShellTask_vc25c613b5190954144284486cfec2056d1820375.RunPackager()
1>C:\Users\DDroth.nuget\packages\uno.wasm.bootstrap\1.0.0-dev.137\build\Uno.Wasm.Bootstrap.targets(101,3): error :    at Uno.Wasm.Bootstrap.ShellTask_vc25c613b5190954144284486cfec2056d1820375.Execute()
Expected behavior
Building the WASM sample should work no problem
Minimal reproduction of the problem with instructions

create new sample project in a path which holds a blank (like the default VS projects path)
in solution explorer: Uno.Wasm -> right click -> Rebuild

Environment

Nuget Package:

Package Version(s):

Affected platform(s):
- [ ] iOS
- [ ] Android
- [x ] WebAssembly
- [ ] Windows
- [ ] Build tasks

Visual Studio
- [ x] 2017 (version: latest)
- [ ] 2017 Preview (version: )
- [ ] for Mac (version: )

Relevant plugins
- [ ] Resharper (version: )

This is an issue that has been addressed in https://github.com/nventive/Uno.Wasm.Bootstrap/pull/50 of the Uno.Wasm.Bootstrapper package. You can update both Uno.UI and the Uno.Wasm.Bootstrapper to the latest dev branch to fix this.
We'll update the quickstart repo to address this.

Excellent!. Thanks


Nuxt 3 - Error: Cannot find name 'xxx' for autoimported functions from imports.d.ts after 0.38.3 (2022/7/7) update

VS Code shows error for autoimported functions Nuxt 3 like ref, computed, useState, useHead, etc... after Volar update 0.38.3 (2022/7/7).
Code works but errors are shown.
Has something change in settings or is it a bug?
thx

i have the same issue

As far as i know using include in your tsconfig.json will overwrite the "include" option from nuxt's tsconfig.
this is intentional https://www.typescriptlang.org/tsconfig#extends

Autoimports are working for me with Volar 0.38.5.
You can try to delete your .nuxt directory and run "npm run dev" to rebuild your nuxt.d.ts files - maybe that will fix it.

Hi @Lyokolux,
I don't know what happened, but if I try now it is working correctly no matter what version I have.
I tried the newest version (0.38.5) and the one I had the issue. Both are working correctly. 🤷🏻♂
I don't know why it didn't work a week ago. In my team a I have colleague which has the same issue as I.
I will try him if he still has the issue.
I will leave a comment here after that
Thank you guys

Autoimports are working for me with Volar 0.38.5. You can try to delete your .nuxt directory and run "npm run dev" to rebuild your nuxt.d.ts files - maybe that will fix it.

I tried it and it didn't work.
Deleting my includes in tsconfig.json have done the job for me.

I'm closing this one - feel free to open again if issue occurs again.

I have the same issue, but i don't have any include configuration on my side:
{
  // https://nuxt.com/docs/guide/concepts/typescript
  "extends": "./.nuxt/tsconfig.json"
}

i just created new nuxt 3 project, and without any further configuration i have the problem
@IIFelix

I had Vetur extension installed when I uninstalled it it stopped showing these errors.
Please use  Vue Language Features (Volar) extension for Vue in VS Code instead of Vetur.

I had Vetur extension installed when I uninstalled it, it stopped showing these errors.
Please use Vue Language Features (Volar) extension for Vue in VS Code instead of Vetur.

Your method worked, I succeeded.

I had Vetur extension installed when I uninstalled it, it stopped showing these errors.
Please use Vue Language Features (Volar) extension for Vue in VS Code instead of Vetur.

Yes! It worked and for me solved a lot of not found errors when using nuxt 3

If you already installed Volar but still the issue is there then try this:

CTRL + SHIFT + P in VS Code
Volar: Restart Vue Server

If you already installed Volar but still the issue is there then try this:

CTRL + SHIFT + P in VS Code
Volar: Restart Vue Server

Woww, it worked

Restarting vs code worked for me


release in order to use plugin for self execution during CI

added build step in order to access current version for self execution in code-analysis.yml


1.0.0

add support for tmux 2.9

Thoughts, @tmuxinator/tmuxinator? If the bump to 1.0.0 seems excessive or rushed, we can make this 0.17.0 and talk about a better time to cut 1.0.0.


jsreport v2 binaries with chrome on Azure App Service

Hi
Should it be possible to run the new jsreport v2 binaries with chrome on Azure App Services?
Thanks for your help!

So I guess the problem is the same as running jsreport with chrome using nodejs
018-07-03 16:20:25.553 +00:00 [Error] Microsoft.AspNetCore.Server.Kestrel: Connection id "0HLF0VQBMG5AV", Request id "0HLF0VQBMG5AV:00000004": An unhandled exception was thrown by the application. jsreport.Local.JsReportBinaryException: Error rendering report: A critical error occurred while trying to execute the render command: spawn UNKNOWN (1). caused by error (1) -> meta = {"remoteStack":"Error: spawn UNKNOWN\n    at _errnoException (util.js:1022:11)\n    at ChildProcess.spawn (internal/child_process.js:323:11)\n    at Object.exports.spawn (child_process.js:503:9)\n    at Function.launch (jsreportRuntime.js:317426:40)\n    at <anonymous>"}, stack = Error:     at responseToBuffer ([eval]:44291:29)    at concat ([eval]:44344:40)    at ConcatStream.<anonymous> ([eval]:14359:43)    at emitNone (events.js:111:20)    at ConcatStream.emit (events.js:208:7)    at finishMaybe ([eval]:90572:14)    at afterWrite ([eval]:90434:3)    at _combinedTickCallback (internal/process/next_tick.js:144:20)    at process._tickCallback (internal/process/next_tick.js:180:9)
@pofider Could you publish the Linux binary v2 as beta as well so I can try running it on an App Service on Linux?

I had the same problem now.
@pofider can you help us?

unfortunately, i suspect that the problem is this
https://github.com/GoogleChrome/puppeteer/issues/515

Hi @fabich
I dont think that is..
I Have a Windows Based Azure App Service running jsreport with phantonJS (nuget jsreport.Binary version 1.10). And Works fine.
There is just a limitation about de App Service Plan.  See this https://github.com/projectkudu/kudu/wiki/Azure-Web-App-sandbox#unsupported-frameworks
The Service plan must to be "Basic " or higher

@penihel I was talking about running jsreport with chrome-pdf

Unfortunately, I am afraid that chrome won't work in restricted environment like azure web app.
I didn't get to try it out, but looking on internet it seems puppeteer doesn't work there - https://github.com/GoogleChrome/puppeteer/issues/515
You can run jsreport official docker image in azure web app and connect to it from your .net app.
Or create your own image together with your .net app.
,

@pofider is chrome-pdf available on jsreport online?

We are currently working on updating jsreportonline to the latest version including chrome, version control... It can take 1 - 3 weeks.
Until then there is electron recipe which also renders using chrome on behind.

I believe we have a solution without "docker". Because this is an awful lot for jsreport. This will take away most developers, discouraging them from using jsreport

@penihel I don't think so, it's actually very easy with the new Azure Web App for Containers.
Just use the docker image provided by the jsreport team:
jsreport/jsreport:latest-full
I'm closing this issue now.
Our solution: don't include jsreport in the .net core app if you want to use chrome-pdf.
Only use the jsreport.Client v3.0.0+ and send the request to a jsreport docker container.

In this case I'd rather give up using jsreport and use only the
https://github.com/rdvojmoc/DinkToPdf (wkhtmltopdf)
That allows me to use only one App Service on azure. No need to use docker

In this case I'd rather give up using jsreport and use instead this lib
https://github.com/rdvojmoc/DinkToPdf (wkhtmltopdf)
That allows me to use only one App Service on azure. No need to use docker

Very good, thanks for the tip @penihel 👍 :D


Migrate from CIDv0 to CIDv1?

So it turns out that IPFS's Base58 scheme (aka CIDv0, /ipfs/<mhash>) is being superseded by a new scheme called CIDv1 (/ipfs/<mbase><version><mcodec><mhash>). Further information can be found here. IPFS v0.4.5 will add support for CIDv1, and IPFS v0.5 will make CIDv1 the default.
Given that OpenBazaar 2.0 hasn't launched yet, we are not beholden to using CIDv0. And given IPFS v0.4.5 (the next release; to come very soon) provides support CIDv1, it may be a wise choice to prefer CIDv1 for OpenBazaar, i.e. to use it as a default.
Thoughts?

@JustinDrake or @jackkleeman do you know how to activate this application wide?

It's scheduled for the 0.4.9 release https://github.com/ipfs/go-ipfs/issues/3699

The go-ipfs PR has now been merged.


Memory leak troubleshooting

I am experiencing memory leak in Adobe Brackets or some plugin. How can I figure out which plugin is it? Is it only uninstall + observe method?

Yeah, Brackets (unfortunately) leaks memory in some places.
Known spots are (see also https://groups.google.com/forum/#!topic/brackets-dev/98FAtTKEKYw):

Extension Manager (open and close): fixed in Release 1.2, coming soon
Quick Open (open and close, big one)
Reload with/without extensions

The easiest way to find if a leak is caused by Brackets itself or an extension is to use Debug > Reload without extensions and see if it still leaks memory.

Its there a other method to check this problem. Ive got one file and if i work in this at a certain moment brackets goes beserk. showing and hiding some sort of alert window which show and hides constant


Setting temperature for azure openai assistant in nodejs

How do I set the temperature of a model in @azure/openai-assistants while creating an assistant.

@gokulsathyan-ulai Thank you for using the Azure OpenAI Assistants SDK for JS, and for writing this issue up. The ability to set temperature is not available in the v1 Beta API for Assistants, but was recently released in the v2 Beta API. Azure Assistants support for the v2 Beta API is being implemented, and I'll update this issue once that support reaches the JS SDK.

What is the default temperature for models in azure openai assistants?

@glharper What is the default temperature for models in azure openai assistants?

I'd assume the same default as for OpenAI Assistant models, 1, but I can't find any Azure specific ref docs to back that up.

@glharper   Is there any other way for me to make the temperature 0?

any updates on this one
@glharper
?

Hello, @chahalinder0007!
We've quite recently achieved one of our partnership goals with OpenAI and released dedicated Azure sub-client support in the official OpenAI node.js package. Converged support via that library will be our strategy moving forward, including for ensuring timely availability of things like this temperature setting in Assistants.
You can read more about the Azure sub-client configuration process in the readme, here: https://github.com/openai/openai-node/tree/master?tab=readme-ov-file#microsoft-azure-openai
Apologies for the whiplash, and we're working to get all of our docs and samples migrated ASAP. But the good news is that you can definitely configure temperature today with the new sub-client!

Hey @trrwilson, thanks for the heads up, will/has this been published anywhere else?
I'm mildly concerned about how this will look for the MS first party features such as the "On your data" extensions.
Are there plans for the OpenAI library to contain the APIs for managing deployments & content filters?

Hi @codylittle, we strongly recommend that you migrate to use the AzureOpenAI client exported by the official OpenAI client library for JavaScript. Checkout the migration guide for how to do so while maintaining typing for Azure features.
Please let us know if you have any other questions!


json  { 	"messages": [], 	"activationTimes": { 		"startup": true, 		"codeLoadingTime": 59181, 		"activateCallTime": 2, 		"activateResolvedTime": 5, 		"activationEvent": "*" 	}, 	"runtimeErrors": [] } Extension issue

Issue Type: Bug
Extension Name: local-history
Extension Version: 1.7.0
OS Version: Darwin x64 16.7.0
VSCode version: 1.36.1

:warning: We have written the needed data into your clipboard. Please paste! :warning:

What ?! What is your problem ?


Optimize NormalizeVec

/kind improvement

/hold

Looks like we get many places didn't take care of the exception throwing like https://github.com/zilliztech/knowhere/blob/613f06f15597ff0abea79801c6995af5e2fb7713/src/common/comp/brute_force.cc#L136
We need to try catch is to avoid folly thread crash.

Create a issue to track the fix https://github.com/zilliztech/knowhere/issues/804
@cydrain


Continuous Integration with Travis

Let's set up a travis build on each commit.

[ ] How to deal with babel database access credentials?

looks like Encryption keys should work; Travis CI does public key encryption.

Well, encryption keys would work for the database account password, but it won't address the fact that we only accept connections from localhost. Hmm.

It works!
I figured out how to get an SSL encrypted connection going from travis to babel.
After a few tries, it seems to work.
636a864
build #5
Thanks for the help, @bokov


On TL correct answer is not shown

main.cpp
#include <iostream>

using namespace std;

int main()
{
    int a;
    cin >> a;

    while (true)
    {
        a++;
    }

    return 0;
}

inputs.txt
1
---
1
===
2
---
2
===
3
---
3
===
4
---
4
===
5
---
5

If the endless loop is removed, and replaced with cout << a + 1 << '\n' to cause WA, the answer IS shown.

Closed by #14


Modifying our current version numbers to increase

This change is

@bbowman is added to the review. #Closed

This is just a temp fix until the real nuget solution comes in.

:clock1:


As a user, I want to see a motivational quote on my home screen after choosing this application as my live wallpaper

This is a base user story, it recovers and presents a quotation as part of the live wallpaper.
This feature will pull quotes from the database.

A pre-fabricated database of quotes from the inspirational category

This combination prepares a lot of the framework required for future stories and safeguards against a cut-off from Brainy Quotes.

[x] Create a database schema
[x] Populate it with the "inspirational" category and 10 inspirational quotes
[x] Pull a quote at random
[ ] Present the quote beautifully on the live wallpaper (font and style)
[ ] Test overlarge quotes
[ ] Test quote placement during scroll (persistent visibility - watermark)
[ ] Test unknown author
[ ] Test overlong author name
[ ] Test special characters?

Thanks, @ikocijan for your tutorial I found (http://ivankocijan.com/android-drawing-multiline-text-on-canvas/), this canvas stuff is :-1:

Snapshot


Create edubs.ch

@GuyXY Could you please check if your school status corresponds to the following statement in this repository rules:

If an organization provides primary and secondary education only (i.e., no high or higher education programs), it shall not be included into the list. Primary and secondary school students usually do not need professional developer tools, and in case they learn some programming, we are glad to offer them Community versions of the tools, which are free to everybody, such as PyCharm Community Edition, etc.
If you represent a primary or secondary school and you are certain of the necessity of professional version of a JetBrains tool for your school, please contact JetBrains sales team via https://www.jetbrains.com/support/sales/

If you do provide high or higher education, please give us a link to a page saying that, and rename the file in this request to lib/domains/ch/edubs.txt to reflect the repository rules.
Processing of this request may take a bit longer because your institution is not a university or a college. Thank you for your understanding.

@GuyXY You might miss my previous comment. I am sorry that processing your request took more time than usual, and ask you for a clarification of the issue descibed above. If you will not comment, I have to close the request without merging. Thank you!

@GuyXY This request remains unanswered for a while, I have to close it. Thank you for your understanding.


treeview style templates not working for Label, Icon

label doesn't render at all if used, even with redraws etc.
when opened, if style template is active.  subsequent render gets them.

anyway, treeview is pretty efficient now (opening inspector on inspector is not too bad even for relatively large initial inspector) and various other elements are able to use style templates, so this should be fixed but not super hi-pri.

for standard widgets example, 3 levels of inspector (original + 2 inspectors-of-inspectors) works fast and then the 4th exceeds memory capacity :)


Static methods min and max also accept arrays

see max and min documentation on the MomentJS website.

Opening this PR on https://github.com/flowtype/flow-typed/ - see comments on https://github.com/marudor/flowInterfaces/commit/bec3552aa4a2f7f09fbc4552ad1ca64ee5a805cf

@perpetualjourney yeah, I was gonna say this is a fork of https://github.com/marudor/flowInterfaces 👍


RuntimeError: unsupported: Symbol with 4.2.0.beta1

Order.search_by_keyword('bruno') throws error RuntimeError: unsupported: Symbol
Search used to work well with rails 4.1.4. Not sure how to debug.
from .rvm/gems/ruby-2.0.0-p353/gems/arel-6.0.0.beta1/lib/arel/visitors/to_sql.rb:726:in `unsupported'
from .rvm/gems/ruby-2.0.0-p353/gems/arel-6.0.0.beta1/lib/arel/visitors/reduce.rb:13:in `visit'
from .rvm/gems/ruby-2.0.0-p353/gems/arel-6.0.0.beta1/lib/arel/visitors/to_sql.rb:785:in `block in inject_join'
from .rvm/gems/ruby-2.0.0-p353/gems/arel-6.0.0.beta1/lib/arel/visitors/to_sql.rb:781:in `each'
from .rvm/gems/ruby-2.0.0-p353/gems/arel-6.0.0.beta1/lib/arel/visitors/to_sql.rb:781:in `each_with_index'
from .rvm/gems/ruby-2.0.0-p353/gems/arel-6.0.0.beta1/lib/arel/visitors/to_sql.rb:781:in `each'
from .rvm/gems/ruby-2.0.0-p353/gems/arel-6.0.0.beta1/lib/arel/visitors/to_sql.rb:781:in `inject'
from .rvm/gems/ruby-2.0.0-p353/gems/arel-6.0.0.beta1/lib/arel/visitors/to_sql.rb:781:in `inject_join'
from .rvm/gems/ruby-2.0.0-p353/gems/arel-6.0.0.beta1/lib/arel/visitors/to_sql.rb:463:in `visit_Arel_Nodes_NamedFunction'
from .rvm/gems/ruby-2.0.0-p353/gems/arel-6.0.0.beta1/lib/arel/visitors/reduce.rb:13:in `visit'
from .rvm/gems/ruby-2.0.0-p353/gems/arel-6.0.0.beta1/lib/arel/visitors/reduce.rb:7:in `accept'
from .rvm/gems/ruby-2.0.0-p353/gems/arel-6.0.0.beta1/lib/arel/nodes/node.rb:48:in `to_sql'
from .rvm/gems/ruby-2.0.0-p353/gems/pg_search-0.7.6/lib/pg_search/features/tsearch.rb:106:in `column_to_tsvector'
from .rvm/gems/ruby-2.0.0-p353/gems/pg_search-0.7.6/lib/pg_search/features/tsearch.rb:58:in `block in tsdocument'
from .rvm/gems/ruby-2.0.0-p353/gems/pg_search-0.7.6/lib/pg_search/features/tsearch.rb:57:in `map'
from .rvm/gems/ruby-2.0.0-p353/gems/pg_search-0.7.6/lib/pg_search/features/tsearch.rb:57:in `tsdocument'
from .rvm/gems/ruby-2.0.0-p353/gems/pg_search-0.7.6/lib/pg_search/features/tsearch.rb:83:in `tsearch_rank'
from .rvm/gems/ruby-2.0.0-p353/gems/pg_search-0.7.6/lib/pg_search/features/tsearch.rb:23:in `rank'
from .rvm/gems/ruby-2.0.0-p353/gems/pg_search-0.7.6/lib/pg_search/scope_options.rb:86:in `block in rank'
from .rvm/gems/ruby-2.0.0-p353/gems/pg_search-0.7.6/lib/pg_search/scope_options.rb:85:in `gsub'
from .rvm/gems/ruby-2.0.0-p353/gems/pg_search-0.7.6/lib/pg_search/scope_options.rb:85:in `rank'
from .rvm/gems/ruby-2.0.0-p353/gems/pg_search-0.7.6/lib/pg_search/scope_options.rb:17:in `apply'
from .rvm/gems/ruby-2.0.0-p353/gems/pg_search-0.7.6/lib/pg_search.rb:40:in `block in pg_search_scope'
from (irb):6
from .rvm/gems/ruby-2.0.0-p353/gems/railties-4.2.0.beta1/lib/rails/commands/console.rb:110:in `start'
from .rvm/gems/ruby-2.0.0-p353/gems/railties-4.2.0.beta1/lib/rails/commands/console.rb:9:in `start'
from .rvm/gems/ruby-2.0.0-p353/gems/railties-4.2.0.beta1/lib/rails/commands/commands_tasks.rb:68:in `console'
from .rvm/gems/ruby-2.0.0-p353/gems/railties-4.2.0.beta1/lib/rails/commands/commands_tasks.rb:39:in `run_command!'
from .rvm/gems/ruby-2.0.0-p353/gems/railties-4.2.0.beta1/lib/rails/commands.rb:17:in `<top (required)>'
from bin/rails:8:in `require'

Just got this error myself performing a query. The code that started the error:
def search
    q = params[:name]

    @encounters = Encounter.where(:all, :conditions => ["name LIKE %?%", q])
    render json: @encounters
  end


init androidenv.buildGradleApp

Motivation for this change
This is the last big piece of code that is used by reflex-platform but missing in nixpkgs. It is used to generate apps using the gradle build system.
Need feedback on whether this is useful in Nixpkgs.
/cc @ali-abrar @ryantrinkle @Ericson2314

Some of these commits need to be reworked I think. For instance google-repository.nix should be replaced with a fetchzip call.

As someone who helped write this stuff originally, I'm not really in favor of having this in nixpkgs in its current state. I never really considered it release quality. If possible, I'd much rather see this brought in-tree into reflex-platform.

We can definitely look into removing this stuff but i would definitely object to adding even more android infrastructure to reflex-platform than there already is. This stuff is not specific to Reflex or even haskell so it does not seem like the right place to put it. We want more people to be using this outside of Reflex world so it gets more testing, more refactors, etc. It seems to me fairly close to doing what build-app.nix does for ant but with gradle. Maybe it makes sense to move all of this to some sort of a build support overlay or something like it though.

Are there specific bugs or sources of instability you’re thinking of? What
features would you want it to have?
On Thu, Jun 21, 2018 at 9:36 PM Will Fancher<EMAIL_ADDRESS>wrote:

@ElvishJerricco commented on this pull request.
In pkgs/development/mobile/androidenv/build-gradle-app.nix
https://github.com/NixOS/nixpkgs/pull/41855#discussion_r197320193:

if [ -d "$DEPENDENCIES/m2" ] ; then

 cp -RL "$DEPENDENCIES"/m2/* .m2/repository/

fi
chmod -R 755 .m2
mkdir -p .m2/repository/com/android/support
cp -RL local_sdk/extras/android/m2repository/com/android/support/* .m2/repository/com/android/support/
cp -RL local_sdk/extras/google/m2repository/* .m2/repository/
gradle ${gradleTask} --offline --no-daemon -g ./tmp -Dmaven.repo.local=pwd/.m2/repository
'';

installPhase = ''
mkdir -p $out
mv ${buildDirectory}/build/outputs/apk/*.apk $out

mkdir -p $out/nix-support
echo "file binary-dist "$(echo $out/*.apk)"" > $out/nix-support/hydra-build-products

No idea what this does
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/pull/41855#discussion_r197320193, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AHFpRq9AMxQCxiIQfnxc59Nw6m_WHDcOks5t_EovgaJpZM4UjF43
.

This PR does not have any tests to demonstrate the usability of the function "buildGradleApps". Shall we add some tests for it?

This might be helpful: https://github.com/obsidiansystems/haven
On Fri, 28 Sep 2018 22:13:42 -0700
Ding Xiang Fei<EMAIL_ADDRESS>wrote:

This PR does not have any tests to demonstrate the usability of the function "buildGradleApps". Shall we add some tests for it?
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/NixOS/nixpkgs/pull/41855#issuecomment-425616806

--
Ali Abrar<EMAIL_ADDRESS>

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/using-androidenv-error-functionargs-requires-a-function/32773/5

Was accidentally removed in https://github.com/NixOS/nixpkgs/pull/50596
Readding in https://github.com/NixOS/nixpkgs/pull/254082


Error for missing sig on private routes

We currently return a 400 error due to validation, but I think it would be better to return 403.
Also, do we have tests around this?

We have tests and we should already return 403 https://github.com/nearform/labs-authorization/blob/master/test/endToEnd/policiesTest.js#L125-L142

What I reported is happening when the caller doesn't provide the sig.
Sorry for the confusion

Ok, then, we do not have tests and I think it's Joi handling that side of validation :/


(Question) How to customize the native window

I am trying to build custom title bar in pure HTML and CSS so I'd like to hide the default title bar please help also how do I add transparency effects to window background

This is platform-specific and currently not supported. Also see #546.


Exception 'new BigNumber() not a base 16 number' being raised after a unit test fails

Truffle and OS info
Mac OS X 10.11.4
Truffle v1.0.3
Expected behavior
The test fails and if there are logs to show, truffle print them out in console
Actual behavior
Truffle crashes and print out the stacktrace below for what it seemingly is a web3 problem.
Stacktrace

/home/ubuntu/nvm/versions/node/v5.5.0/lib/node_modules/truffle/node_modules/solc/bin/soljson-latest.js:1
(function (exports, require, module, __filename, __dirname) { var Module;if(!Module)Module=(typeof Module!=="undefined"?Module:null)||{};var moduleOverrides={};for(var key in Module){if(Module.hasOwnProperty(key)){moduleOverrides[key]=Module[key]}}var ENVIRONMENT_IS_WEB=typeof window==="object";var ENVIRONMENT_IS_WORKER=typeof importScripts==="function";var ENVIRONMENT_IS_NODE=typeof process==="object"&&typeof require==="function"&&!ENVIRONMENT_IS_WEB&&!ENVIRONMENT_IS_WORKER;var ENVIRONMENT_IS_SHELL=!ENVIRONMENT_IS_WEB&&!ENVIRONMENT_IS_NODE&&!ENVIRONMENT_IS_WORKER;if(ENVIRONMENT_IS_NODE){if(!Module["print"])Module["print"]=function print(x){process["stdout"].write(x+"\n")};if(!Module["printErr"])Module["printErr"]=function printErr(x){process["stderr"].write(x+"\n")};var nodeFS=require("fs");var nodePath=require("path");Module["read"]=function read(filename,binary){filename=nodePath["normalize"](filename
BigNumber Error: new BigNumber() not a base 16 number:
at raise (/home/ubuntu/nvm/versions/node/v5.5.0/lib/node_modules/truffle/node_modules/web3/node_modules/bignumber.js/bignumber.js:1177:25)
at /home/ubuntu/nvm/versions/node/v5.5.0/lib/node_modules/truffle/node_modules/web3/node_modules/bignumber.js/bignumber.js:1165:33
at new BigNumber (/home/ubuntu/nvm/versions/node/v5.5.0/lib/node_modules/truffle/node_modules/web3/node_modules/bignumber.js/bignumber.js:212:28)
at [object Object].formatOutputString [as _outputFormatter] (/home/ubuntu/nvm/versions/node/v5.5.0/lib/node_modules/truffle/node_modules/web3/lib/solidity/formatters.js:217:19)
at /home/ubuntu/nvm/versions/node/v5.5.0/lib/node_modules/truffle/node_modules/web3/lib/solidity/type.js:237:25
at [object Object].SolidityType.decode (/home/ubuntu/nvm/versions/node/v5.5.0/lib/node_modules/truffle/node_modules/web3/lib/solidity/type.js:238:11)
at /home/ubuntu/nvm/versions/node/v5.5.0/lib/node_modules/truffle/node_modules/web3/lib/solidity/coder.js:219:29
at Array.map (native)
at [object Object].SolidityCoder.decodeParams (/home/ubuntu/nvm/versions/node/v5.5.0/lib/node_modules/truffle/node_modules/web3/lib/solidity/coder.js:218:26)

How to reproduce
Run truffle test with a unit test where the TX fails without raising events.
Details
I've tested it using web3.js 0.16.0 and it seems to print out the "Events emitted" message with no events, but it doesn't crash anymore. Testing against TestRPC it works.

Same problem here.

Hi @thiagodelgado111, I suspect this is an issue with what you're passing to a contract function that expects a BigNumber. It's hard to tell without code however.
Since this was on Truffle 1.0, can you upgrade to Truffle 2.0 and tell me if you still have the issue? I'm going to close this issue for housekeeping reasons but please reopen and command if you have issues. Thanks!


Create test cases for other http verbs in routes/route.js

Fill in the gap where test cases are currently missing.

Please see my pull request #3 for this issue.

Thanks @cosminlupu great work!


Use UglifyJS to minify files in minified target

It is written in JavaScript, is less buggy, and compresses better.

I like the idea of this. In addition to what you mention, less code is required and it can be downloaded automatically as it is an NPM dependency. We do need to make sure that this uglifier does not break the final build. Did you verify that already?

@timvandermeij Yes. I've been using UglifyJS in production and no bugs have been reported or observed because of the minifier.

Seems like I spoke too soon. Google Chrome chokes on minified files after 2edf2792dcb6adbfffed242cc5c02b412157e45c (committed 4 days ago) because of long sequences generated by UglifyJS. It only affects pdf.worker.js, so I have added a workaround for that file specifically. The workaround increases the output size by less than 1KB, which is less than 0.2% of the total file size.
On the other hand, I did some benchmarking, and found that Closure Compiler compiles all three files marginally better (difference <1%), at the cost of 8 times more CPU time. The fact that after gzipping one of the files compiled by UglifyJS is smaller than the counterpart produced by Closure doesn't help Closure's case either.
So all in all, even though some Chrome bug makes UglifyJS's output look "buggy," its sheer performance and good-enoughness makes it a lot better choice.

@yurydelendik What do you think about this patch?

target.minified is not used on the botio. @timvandermeij if it works as advertised than we can accept it. (I saw somewhere messages about UglifyJS has some problem with our new code base).

I did more testing with this and found no further issues. Thank you for the patch!

I have just updated the frequently asked questions wiki page to mention what has been changed in this update.

+1


Cross-Layer Collisions and Server Side Layer Compositing

Referring to the issue comprehensively mentioned in this link #365, as of now the only solution, as per all the comments I've read so far, is to combine all the sources and make a composite layer URL so that it can be rendered and the problem of conflicting layers can be avoided.
Is there any possible way like Server Side Compositing so that composite layers can be combined on-the-fly with a script as to ensure seamless rendering of all the layers.
Your timely response would be highly appreciated.

Hello @raosaeedali – you're talking about conflicting labels, correct? If so we don't currently offer any such service, and though we're interested in providing one it's not currently on our schedule. #365 remains the best place to watch for updates.

Hi @meetar thanks for responding. I am following #365 for updates. But, I am asking for any particular way to make a composite of the sources provided in the scene.yaml file at server side (in yaml or JS). In this way, all the sources could be combined as a single source and rendered once, hence the conflicting labels could be avoided for the time being till a comprehensive solution is devised.

http://tilestache.org may provide such a config...
On Mon, Sep 18, 2017 at 10:09 AM, raosaeedali<EMAIL_ADDRESS>wrote:

Hi @meetar https://github.com/meetar thanks for responding. I am
following #365 https://github.com/tangrams/tangram/issues/365 for
updates. But, I am asking for any particular way to make a composite of the
sources provided in the scene.yaml file at server side (in yaml or JS). In
this way, all the sources could be combined as a single source and rendered
once, hence the conflicting labels could be avoided for the time being till
a comprehensive solution is devised.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tangrams/tangram/issues/595#issuecomment-330289297,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA0EO_oKl7OfcaobtyuAlo4BFd7xgUPdks5sjqO1gaJpZM4PajHT
.


Start normalizing props for DUI3 (CNX-9169)

Moving stuff from csprojs to props file for better management

updated again @JR-Morgan 😬


Requirements file?

Hello, thanks for this work!! I do not find the requirements.txt file in the repo :/
--- edit
my bad, found it in the src folder!!

no problem. glad you found it!

Hello! I would like to follow up with this requirement file.
When I run pip install -r requirements.txt, it showed this error
ERROR: Could not find a version that satisfies the requirement antspyx==0.3.2 (from versions: 0.3.8, 0.4.2)
ERROR: No matching distribution found for antspyx==0.3.2

I wonder if the distribution has changed for this package, Thanks!
Software Information
LSB Version:	:core-4.1-amd64:core-4.1-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-4.1-amd64:desktop-4.1-noarch:languages-4.1-amd64:languages-4.1-noarch:printing-4.1-amd64:printing-4.1-noarch
Distributor ID:	RedHatEnterpriseServer
Description:	Red Hat Enterprise Linux Server release 7.9 (Maipo)
Release:	7.9
Codename: Maipo


The renderer implementation looks much more simplified than the official implementation of the original paper? Am I missing something?

Could you clarify -- in what way is it simplified? There's a lot of simplification that comes from the fact that, unlike the primary renderer in the 3DGS optimization phase, a view-only renderer doesn't need to be differentiable. Also, this renderer doesn't support spherical harmonics. Are there other simplifications you're referring to?

According to https://github.com/scier/MetalSplatter/blob/9e0fae2e7a0895fd4b21ab82e1ccfb03a0f0aa8c/MetalSplatter/Sources/SplatRenderer.swift#L229-L231 and https://github.com/scier/MetalSplatter/blob/9e0fae2e7a0895fd4b21ab82e1ccfb03a0f0aa8c/MetalSplatter/Resources/Shaders.metal#L169-L178, a render pipeline with alpha-blending is used instead of a compute pipeline in which accumulation should be implemented additionally. And the tile-based rasterizer is not implemented.


Only file in modpack folder is "modConfig.json"

The version of modpack-installer i´m using is 2.3.4
When i try to install a modpack it fails with the error "Forge installation not found.
Expected to find a directory named 1.20.1-forge-47.1.3 in /home/sampo/.minecraft/versions
If a similarly named directory was created in the expected folder, please submit a
bug report."
And there´s a folder named "1.20.1-forge-47.1.39" in "/home/sampo/.minecraft/versions".
There´s a the modpack folder and instance in the minecraft launcher but the only file in the modpack folder is "modConfig.json"

Forge might have changed something about their installer for newer versions. I will check if this is the case.
Also, is the modpack trying to use Forge version 47.1.3 or 47.1.39?
If you can provide the name of the modpack, that would be appreciated.

The modpack is called "Chosen´s Modded Adventure"
The manifest.json of the modpack says forge-47.1.3
Here´s the curseforge link if it´s needed

It looks like the Forge version detection regex was a bit too permissive. Should be fixed in f6aa4ea.


Can we create incompatibilities?

Hi there is a way for make some exclusion like background never with blue body ? I dont see how to add in config. Thanks !

@hamsterzbc hello, there is no way to do it via configuration currently, but it's an interesting feature.
What I've done in the past is to create multiple configurations and merge the generated collection later. You can use the nftool merge command for that and it guarantees no collisions. Do you think that would work in your case?
Also, if we were to implement this feature, how do you imagine yourself using it?

Ah i see yes can work i can generate the blue one the green one and merge. But for some case will not work Like for exemple i have few HAT that dont work with few eyes.  This will make the job painfull but thanks for your answer !
For the feature in config :

trait_type: BG
variants:

value: BLUE
weight: 1

value: GREY
weight: 10

value: jungle
weight: 11

value: LUNE
weight: 12
Maybe in separate config file or just add in
"trait-type": "BG",
"value": "BLUE",
"incompatible_with" : "traitname(value),trait2,trait3"
But this mean all trait got unique "value"

or maybe when dump the trait list add an ID to each trait so can filter by id for incompatible and do :
"incompatible_with" : "traitid,51,45,89"

But this mean all trait got unique "value"

I think it's safe to assume that. The value is the only differentiator between variants in attributes:
{ "trait_type": "Body", "value": "Blue" }

Building on top of your idea, I think using an object to represent exclusion/incompatibility might make the api a bit better, this way we can exclude from multiple traits, for example, Body 1 is incompatible with Head 2 and incompatible with Face 3:
traits:
- trait_type: Background
  variants:
  - value: Green
    weight: 1
  - value: Red
    weight: 1
  - value: Yellow
    weight: 1
  is_optional: false
  optional_weight: 1
- trait_type: Shape
  variants:
  - value: Circle
    weight: 1
  - value: Square
    weight: 1
    exclude:                # <--------------------------------------
        Background: [Green] # <--------------------------------------
  is_optional: false
- trait_type: Direction
  variants:
  - value: Down
    weight: 1
  - value: Left
    weight: 2
  - value: Right
    weight: 2
    exclude:               # <--------------------------------------
      Background: [Yellow] # <--------------------------------------
      Shape: [Square]      # <--------------------------------------
  - value: Top
    weight: 2
  is_optional: false

Another option also following the same idea is to have an exclude list of TraitType:Value instead of using objects
exclude:
- "Background:Green"
- "Shape:Yellow"

^ I think this might be cleaner/easier
@hamsterzbc what do you think about those?
--
On another note, I'm smashed with work this week, but might have some time to start implementing this in the next weeks. If you or anyone else who's reading this want to give it a try, I'm happy to assist with ideas and happy to test it out.


How does Redisson-hibernate 2nd level caching cache data

How does it cache data? So, does it put the entity's id as the key? I didn't see it in the document.

Hibernate may use different objects as key. Redisson is able to store any of them.
https://github.com/redisson/redisson/blob/master/redisson-hibernate/redisson-hibernate-6/src/main/java/org/redisson/hibernate/RedissonStorage.java#L120


Feature Request: Using the engine.plan model in python for image inference

Hi there,
is it possible for the authors of this repo to potential create a quick script showing how I can take the engine.plan i created on my Xavier and load it with a TensorRT engine in Python to perform inference on an image?  (same functionality as the infer.exe c++ file)
A lot of my project code is written in python and I would like to compare this models' performance vs. the tensorflow models I am currently working with. I would like to potentially switch everything over to using this model if it works out. This is seriously such a great repo and i would LOVE to integrate the models into my projects.
Please note: I cannot use deep stream for now since I am using some proprietary cameras and other software that is all done in python.
Thank you!

Have you tried this?
retinanet infer engine.plan  --images=/data/your_images --output=detections.json

@jmsinusa So I guess that is the script to use? It will be interesting adding that into the existing project.
Good to know. Thanks!

Clone the repo and try to build it with setup.py. Haven't tried this on a Jetson platform yet but I was successfully built it in Ubuntu 18.04 (Laptop). After that, you can either use Python or C++. To use it with python check out the main.py and use the infer part.  To use it with C++ check out the extras/cppapi.

@goktug97  I tried that, but setup.py does not work with the Jetson Xavier. Some dependencies do not load properly...

Which dependencies causing trouble?

@goktug97  Are you installing with pip? If not, what is your procedure that is different than the instructions? Thanks!

I installed from the source.
First I had to make this change. Then I built DALI from the source with CUDA enabled. Installed all the dependencies. Then it built successfully.
It seems you are missing pybind11


Fix swagger-config-file argument parsing

Specifying a swagger-config-file always caused error on line 159.
Error: Only one configuration input can be used to configure swagger-ui with this action.You specified "swaggerConfigFile" and "swaggerConfigUrl" at the same time!

For some reason, the fix doesn't fix my problem 🤔 I can't seem to find the root of the problem 🧐

You can use the main branch with @main

Oh sh*t 🤦🏻♂ I didn't think about it this time (had tried for my fix)

I still have the same problem: https://github.com/MonkiProjects/mp-api-specs/actions/runs/633886384

Oh, it used the JS 💡 Right, makes sense

Unfortunately, the bug is still here : https://github.com/MonkiProjects/mp-api-specs/runs/2061008367

Ok let's add a unit test for it

Yeah, and logs too 🙃

Unfortunately, it's midnight here, so I won't help you now 🙄 But I'll check tomorrow for sure! Good luck 💪🏻

I found the problem, the js build tool (ncc) was updated and then failed to build the distribution from source, so even though the bug was fixed in the source, it was not compiled by ncc. This should now be fixed with 1.1.0.

It's fixed 🙌🏻 Thank you 🙏🏻

@RemiBardon Thank you for spotting the copy paste error

I have another one for you 😇 I'm writing an issue 😉


Fix ProjectSettings.save_custom documentation

Fixes https://github.com/godotengine/godot/issues/38152

Could you squash commits into one? See PR workflow.

Thanks!

Cherry-picked for 3.2.2.


ERROR:  column "relhasoids" does not exist

Steps to reproduce:

Create a table without OIDs
Press the browse action
Error message is stated

Error Message:

SQL error:
ERROR:  column "relhasoids" does not exist
LINE 1: SELECT relhasoids FROM pg_catalog.pg_class WHERE relname='us...
^
In statement:
SELECT relhasoids FROM pg_catalog.pg_class WHERE relname='users'
AND relnamespace = (SELECT oid FROM pg_catalog.pg_namespace WHERE nspname='public')

current workaround:

press the sql button in the top
run this command instead of using the browse action

SELECT * FROM 'tablename'

https://stackoverflow.com/questions/58461178/how-to-fix-error-column-c-relhasoids-does-not-exist-in-postgres/58461430#58461430 seems to detail why this is happening


chore(workflows): remove branch protection from setup-pnpm action calls

I thought this is needed to do the node@20 update, but it seems to work without.
Since we decided to discuss the removal of the branch protection first, I close this PR.


Google cloud video-intelligence not annotating multiple features at the same time

Environment details

Product: cloud video intelligence
Linux
Node 16+
NPM 8+
@google-cloud/video-intelligence v4.2.0

Steps to reproduce
I've been using Google Cloud Video Intelligence for text detection. Now, I want to use it for speech transcription so I added SPEECH_TRANSCRIPTION feature to TEXT_DETECTION but the response only contains result for one feature, any of the 2.
const gcsUri = 'gs://path-to-the-video-on-gcs'
const request = {
  inputUri: gcsUri,
  features: ['TEXT_DETECTION', 'SPEECH_TRANSCRIPTION'],
};

// Detects text in a video
const [operation] = await video.annotateVideo(request);
const [operationResult] = await operation.promise();

const annotationResult = operationResult.annotationResults[0]
const textAnnotations  = annotationResult.textAnnotations
const speechTranscriptions  = annotationResult.speechTranscriptions

console.log(textAnnotations) // --> []
console.log(speechTranscriptions) // --> [{...}]

Is this a case where annotation is performed on only one feature at a time? Or is it a case where the process terminates after annotation for the first feature completes?
StackOverflow Question

The issue is that I was retrieving only the first item in the array without considering other items. I guess the misunderstanding is from the examples I followed.
I'm closing this.


Precipitation As Snow Climate Variable

Create a function for the PAS Variable

[x] Create CSV of table
[x] Create Function
[x] Create UI

Corresponding Table

Resolved by #15


[Custom Layer]ValueError: tf.function-decorated function tried to create variables on non-first call

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Colab
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: No
TensorFlow installed from (source or binary): Colab
TensorFlow version (use command below): Colab
Python version: Colab
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version: Colab
GPU model and memory: Colab

Describe the current behaviour
I am trying to implement a custom transformer encoder layer which I truly believe is the custom layer that is causing the above error. Apart from the above layer, I have developed 3 more simple custom layers which I didn't mention here to maintain neatness.
Transformer layer
class transformer(layers.Layer):

  def __init__(self, num_heads, transformer_layers, patch_size):
    super(transformer, self).__init__()
    self.num_heads = num_heads
    self.transformer_layers = transformer_layers
    self.patch_size = patch_size

  def call(self, encoded_patches):
    for _ in range(self.transformer_layers):
        x1 = layers.LayerNormalization(epsilon=1e-6)(encoded_patches)
        attention_output = layers.MultiHeadAttention(
            num_heads = self.num_heads, key_dim = projection_dim, dropout = 0.1
        )(x1,x1)
        x2 = attention_output + encoded_patches
        x3 = layers.LayerNormalization(epsilon=1e-6)(x2)
        x3 = mlp(x3, transformer_units, 0.2)
        encoded_patches = x3 + x2

    representation = layers.LayerNormalization(epsilon=1e-6)(encoded_patches)
    resize_img = layers.Reshape([image_size // self.patch_size, image_size // self.patch_size, 64])(representation)

    return resize_img

Model
def PVT():

  # Inputs
  input = layers.Input(shape=input_shape)
  augment = data_augmentation(input)

  # Stage 1
  patches_1 = Patch_1(patch_size_1)(augment)
  patches_1 = PatchEncoder(num_patches=(image_size // patch_size_1) ** 2, projection_dim=projection_dim)(patches_1)
  input_2 = transformer(num_heads, transformer_layers, patch_size_1)(patches_1) #Output 1

  # Stage 2
  patches_2 = Patch_2(patch_size_2)(input_2)
  patches_2 = PatchEncoder(num_patches=(image_size // patch_size_2) ** 2, projection_dim=projection_dim)(patches_2)
  input_3 = transformer(num_heads, transformer_layers, patch_size_2)(patches_2) #Output 2

  # Stage 3
  patches_3 = Patch_3(patch_size_3)(input_3)
  patches_3 = PatchEncoder(num_patches=(image_size // patch_size_3) ** 2, projection_dim=projection_dim)(patches_3)
  input_4 = transformer(num_heads, transformer_layers, patch_size_3)(patches_3) #Output 3

  # Stage 4
  patches_4 = Patch_4(patch_size_4)(input_4)
  patches_4 = PatchEncoder(num_patches=(image_size // patch_size_4) ** 2, projection_dim=projection_dim)(patches_4)
  input_5 = transformer(num_heads, transformer_layers, patch_size_4)(patches_4) #Output 4

  representation = layers.Flatten()(input_5)
  representation = layers.Dropout(0.5)(representation)
  # Classify outputs.
  logits = layers.Dense(num_classes)(representation)
  # Create the Keras model.
  model = keras.Model(inputs=input, outputs=logits)

  return model

Compiler and optimizer
def run_experiment(model):

    optimizer = tfa.optimizers.AdamW(
        learning_rate=learning_rate, weight_decay=weight_decay, beta_1=0.9, beta_2=0.999
    )

    model.compile(
        optimizer=optimizer,
        loss=keras.losses.SparseCategoricalCrossentropy(from_logits=True),
        metrics=[
            keras.metrics.SparseCategoricalAccuracy(name="accuracy"),
            keras.metrics.SparseTopKCategoricalAccuracy(5, name="top-5-accuracy"),
        ],
    )

    history = model.fit(
        x=xtrain,
        y=ytrain,
        batch_size=batch_size,
        epochs=5,
        validation_split=0.1
    )

    model.save('model-5.h5')

    return history

pvt = PVT()
history = run_experiment(pvt)

Note
I have checked several sources about this but still, I am confused about understanding this error. Before you direct me to other sources, I assure you that I have already checked them all. So I sincerely request you to please provide a clean solution here. By the way, this code is my attempt to reproduce the Pyramid vision transformers.
Model summary(FYI)
Model: "model_2"
_________________________________________________________________
Layer (type)                 Output Shape              Param #
=================================================================
input_3 (InputLayer)         [(None, 32, 32, 3)]       0
_________________________________________________________________
data_augmentation (Sequentia (None, 72, 72, 3)         7
_________________________________________________________________
patch_1_2 (Patch_1)          (None, None, 48)          0
_________________________________________________________________
patch_encoder_8 (PatchEncode (None, 324, 64)           23872
_________________________________________________________________
transformer_8 (transformer)  (None, 18, 18, 64)        0
_________________________________________________________________
patch_2_2 (Patch_2)          (None, None, 4096)        0
_________________________________________________________________
patch_encoder_9 (PatchEncode (None, 81, 64)            267392
_________________________________________________________________
transformer_9 (transformer)  (None, 9, 9, 64)          0
_________________________________________________________________
patch_3_2 (Patch_3)          (None, None, 16384)       0
_________________________________________________________________
patch_encoder_10 (PatchEncod (None, 16, 64)            1049664
_________________________________________________________________
transformer_10 (transformer) (None, 4, 4, 64)          0
_________________________________________________________________
patch_4_2 (Patch_4)          (None, None, 65536)       0
_________________________________________________________________
patch_encoder_11 (PatchEncod (None, 4, 64)             4194624
_________________________________________________________________
transformer_11 (transformer) (None, 2, 2, 64)          0
=================================================================
Total params: 5,535,559
Trainable params: 5,535,552
Non-trainable params: 7

Describe the expected behavior
To train without any bugs.
Standalone code to reproduce the issue
Colab Code
Other info/logs
ValueError                                Traceback (most recent call last)
<ipython-input-15-b64accfa4347> in <module>()
     27     return history
     28
---> 29 pvt = PVT()
     30 history = run_experiment(pvt)

13 frames
/usr/local/lib/python3.7/dist-packages/tensorflow/python/framework/func_graph.py in wrapper(*args, **kwargs)
    975           except Exception as e:  # pylint:disable=broad-except
    976             if hasattr(e, "ag_error_metadata"):
--> 977               raise e.ag_error_metadata.to_exception(e)
    978             else:
    979               raise

ValueError: in user code:

    <ipython-input-14-e002dca74606>:12 call  *
        x1 = layers.LayerNormalization(epsilon=1e-6)(encoded_patches)
    /usr/local/lib/python3.7/dist-packages/tensorflow/python/keras/engine/base_layer.py:1008 __call__  **
        self._maybe_build(inputs)
    /usr/local/lib/python3.7/dist-packages/tensorflow/python/keras/engine/base_layer.py:2710 _maybe_build
        self.build(input_shapes)  # pylint:disable=not-callable
    /usr/local/lib/python3.7/dist-packages/tensorflow/python/keras/layers/normalization.py:1206 build
        experimental_autocast=False)
    /usr/local/lib/python3.7/dist-packages/tensorflow/python/keras/engine/base_layer.py:639 add_weight
        caching_device=caching_device)
    /usr/local/lib/python3.7/dist-packages/tensorflow/python/training/tracking/base.py:810 _add_variable_with_custom_getter
        **kwargs_for_getter)
    /usr/local/lib/python3.7/dist-packages/tensorflow/python/keras/engine/base_layer_utils.py:142 make_variable
        shape=variable_shape if variable_shape else None)
    /usr/local/lib/python3.7/dist-packages/tensorflow/python/ops/variables.py:260 __call__
        return cls._variable_v1_call(*args, **kwargs)
    /usr/local/lib/python3.7/dist-packages/tensorflow/python/ops/variables.py:221 _variable_v1_call
        shape=shape)
    /usr/local/lib/python3.7/dist-packages/tensorflow/python/ops/variables.py:67 getter
        return captured_getter(captured_previous, **kwargs)
    /usr/local/lib/python3.7/dist-packages/tensorflow/python/eager/def_function.py:731 invalid_creator_scope
        "tf.function-decorated function tried to create "

    ValueError: tf.function-decorated function tried to create variables on non-first call.

@AdityaNikhil
While i replicate the colab shared i face a different error, please find the gist here
Could you please refer to this comment and let us know if it helps. [similar issue #34983, link]

Hi @Saduf2019,
It was just the cell where the variable was declared was below that function. Anyway, can you try again. Thank you!

@AdityaNikhil
Please share a colab gist with the issue faced.

@Saduf2019
If you really care about this issue, you wouldn't be here twice.
The colab gist is in the issue I wrote above, you can find it there.

@AdityaNikhil
As mentioned in your previous comment that you face a new problem with eagerly and we do not face the same issue as shared in our gist, we request you to share a colab gist with the issue.

@Saduf2019
If it works fine, maybe there's something wrong when I am running on eagerly. I request you to send me your working gist with eagerly turned on.

Can you check https://github.com/tensorflow/tensorflow/issues/48851#issuecomment-830858393

@AdityaNikhil
Please update as per above comment.


Display PageRank on the node page (for the node itself and its neighbors)

Implemented in another branch.


tf.function makes tf.keras.layers.LSTM significantly slower,  no leading to retracing

Please make sure that this is a bug. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
OS Platform and Distribution:  Linux Ubuntu 16.04 and 18.04.
TensorFlow installed from: pip
TensorFlow version: v2.0.0-rc2-26-g64c3d38 2.0.0
Python version:3.7.3
CUDA/cuDNN version: both (Nvidia 410.79, CUDA Version: 10.0) and (418.87.01, 10.1)
GPU model and memory: both 1080 and V100.

Describe the current behavior
case 1. run normally in CPU mode.
case 2. run normally in eager mode in one GPU card, which is several times faster than the case 1.
case  3. run erroneously when using tf.function in train.py:_train_one_batch in one GPU card. I use input signature, and examine there are no extra retracing. The speed is much slower than that in the eager mode and almost the same with the CPU mode. I also found the GPU usage is close to 100%.
Describe the expected behavior
The case 3 should have similar speed with the case 2, and be faster than the case 1.
Code to reproduce the issue
I provide a reproducible test case.
Other info / logs
I
tf_2_mvp.zip

I found a temporary solution.
Add @tf.function for all 'call' functions in _model.py, then the speed runs reasonably. But these new decorators are not necessary, since the _train_one_batch, invoking them, already has a @tf.function.
However, the speed is still not the fastest, compared to pytorch. Let me recap my test results.
All hidden dims are set to 256, the batch size is 128.
case 1. run normally in CPU mode, about 6s.
case 2. run normally in eager mode in one GPU card, which is several times faster than the case 1, about 2s.
case 3. run erroneously when using tf.function in train.py:_train_one_batch in one GPU card. I use input signature, and examine there are no extra retracing. The speed is much slower than that in the eager mode and almost the same with the CPU mode. I also found the GPU usage is close to 100%. About 6s.
case 4, add tf.function to all "call" in _model.py, about 0.4s.
case 5, pytorch with the almost the same algorithm, is about 0.3s. I have very carefully examined the implementation details of pytorch version!
So far the original issues has evolved to that, why adding tf.function to all invoked son functions are necessary? Otherwise, only tf.function for the top-level function would lead to huge speed slow down.

My issue is the same with https://github.com/tensorflow/tensorflow/issues/35165. I replied my findings to that issue.
Please  help resolve this kind of issues, which would greatly influence our confidence of using tensorflow 2.0.

In the nightly new version, the "bug" is solved. The tf.function on train_one_batch would not lead to "extremely  slow speed". However, the  speed is still much slower than pytorch version, 0.6s vs 0.3s.


Improve Selenium dependency

Selenium.WebDriver 2.37 is out and Coypu is "out-of-date" with regards to the dependency.
Do you see a problem with loosening up on the dependency? My change is now >= 2.35.0 && < 3.0.

Hey folks,
I know that this is closed already, but don't want to create new thread for a non-issue.
By any chance you guys know when new Copy will be published which support latest WebDriver version?
Cheers.