Do leaner queries and responses

Describe the bug
Some endpoints are querying for and returning a massive amount of data. We have made some improvements in the response sizes, but the queries are still fetching too much data, consuming a lot of memory server-side.
At least whenever a workflow is involved (collections, collection, workflows) -- all of the versions and all of the versions' sourcefiles are fetched.
This ticket is intended for 1.8.x. There are deeper changes that can be done that are covered in #3442
┆Issue is synchronized with this Jira Story
┆Issue Type: Story
┆Sprint: Backlog
┆Issue Number: DOCK-1353

Might need to convert this into an epic and split off specific tickets for specific groups of endpoints.

spot-checked for 1.8.6


feature(tutorial): Update tutorial for rinkeby

Updated uport-js tutorial so that it works on Rinkeby.

Codecov Report

Merging #17 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop      #17   +/-   ##
========================================
  Coverage    91.83%   91.83%
========================================
  Files            4        4
  Lines          147      147
  Branches        52       52
========================================
  Hits           135      135
  Misses          10       10
  Partials         2        2

Continue to review full report at Codecov.

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

LGTM

Updated with the fixes! Thanks @zachferland! CC @localredhead

I'm getting an error when trying to authenticate on uport_tutorial.html:
Error: Non-base58 character  uport-connect.js:9280:11
Guessing it has something to do with MNID maybe?

@pelle @zachferland Added a comment about the network selection.

LGTM


docs: add responsive_web template

why: to open general issue for users to create new responsive_web related issues

Fixes Issue
none

Changes proposed

[x] add responsive web template

Screenshots

Note to reviewers

Code of Conduct

[ ] By submitting this pull request, I confirm I've read and complied with the CoC 🖖

Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[x] All new and existing tests passed.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

You can also join our Discord community.
Feel free to check out other cool repositories of the Thecyberworld.
Join the Thecyberworld GitHub Organisation by raising an issue (you will be sent an invitation).

great 👍


Add a decorator that allows a user translate an exception into a response.

... which might be useful for our RPC (both gRPC and Thrift) and REST users.
See #2044 for the context.

/cc @c4milo

I wonder if it's a good idea to reuse com.linecorp.armeria.server.annotation.ExceptionHandlerFunction for other service types including gRPC, Thrift and non-annotated HTTP services.
// Common exception handler
ExceptionHandlerFunction exceptionHandler = ...;

// gRPC
final ServerBuilder sb = new ServerBuilder();
sb.service(new GrpcServiceBuilder()
        .addService(myGrpcService)
        .exceptionHandler(exceptionHandler)
        .build());

// HTTP
sb.service("/http",
           ((HttpService) (ctx, req) -> ...)).decorate(
                   ExceptionFilteringService.newDecorator(exceptionHandler)));

// Thrift
sb.service("/thrift", THttpService.builder(...)
                                  .exceptionHandler(exceptionHandler)
                                  .build());

What I'm not sure about:

What would be the expected behavior when the response is already committed (either partially or fully)?
Is GrpcServiceBuilder.exceptionHandler() better than providing a ServerInterceptor implementation that translates an exception?
Is THttpServiceBuilder.exceptionHandler() better than providing a decorating RpcService implementation that translates an exception?
Is this feature really worth generalizing? Should we just let our users translate exceptions by themselves or use other proxy/AOP libraries?

Thoughts? /cc @anuraaga @ikhoon @imasahiro @kojilin

I don't think I would add new methods like GrpcServiceBuilder.exceptionHandler. I don't see a reason to special case the exception handler but require decorator for other concepts like auth.
Having the ExceptionFilteringService seems ok but indeed isn't so useful for RPC so maybe not such a valuable API.

This issue has been fixed by various improvements.

Thrift: #3383
gRPC: #3197
HTTP: #3853


Support sending raw byte data to the "data" event for child command's stdout and stderr

What kind of change does this PR introduce?
Support sending raw byte data to the "data" event for child command's stdout and stderr. Still WIP

[ ] Bugfix
[x] Feature
[ ] Docs
[ ] New Binding issue #___
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change?

[x] Yes, and the changes were approved in issue #5465
[ ] No

Checklist

[ ] When resolving issues, they are referenced in the PR's title (e.g fix: remove a typo, closes #___, #___)
[ ] A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.
[ ] I have added a convincing reason for adding this feature, if necessary

Other information
Closes #5465

@amrbashir I have addressed your comments. Thank you for reviewing!

Looks really good. I'll make some tests and see if we can improve the api types.

Let me know what you think about my change :P I'm not a TypeScript expert but I tried to let it infer most of the types from the encoding argument.

@lucasfernog thank you for the improvement with result type inferring. I love it! I have merged with nextbranch again.
BTW what is the reason behind bundle.global.js being included in the repository?

bundle.global.js powers the withGlobalTauri (= the apis in window.__TAURI__). Building/Bundling that on the dev's machine is not really an option

I just need some time to test this, my idea was to wait for 1.3 to launch before merging it since you already merged dev into this.

Amazing work!


3 issues in vim9script 'import' after yesterday's refactor

Steps to reproduce
vim9script

def Test_vim9_reload_noclear()
  var lines =<< trim END
    vim9script
    export var exported = 'thexport'

    export def TheFunc(x = 0)
    enddef
  END
  writefile(lines, 'XExportReload.vim')
  lines =<< trim END
    vim9script noclear
    g:loadCount += 1
    var s:reloaded = 'init'
    # import './XExportReload' as exp      # <---
    import './XExportReload.vim'           # <---

    def Again(): string
      return 'again'
    enddef

    # exp.TheFunc()                        # <---
    echom XExportReload.exported           # <---

    if exists('s:loaded') | finish | endif
    var s:loaded = true

    var s:notReloaded = 'yes'
    s:reloaded = 'first'
    def g:Values(): list<string>
      return [s:reloaded, s:notReloaded, Again(), Once(), exp.exported]
    enddef

    def Once(): string
      return 'once'
    enddef
  END
  writefile(lines, 'XReloaded')
  g:loadCount = 0
  source XReloaded
  assert_equal(1, g:loadCount)
  assert_equal(['first', 'yes', 'again', 'once', 'thexport'], g:Values())      # <---
  source XReloaded
  assert_equal(2, g:loadCount)
  assert_equal(['init', 'yes', 'again', 'once', 'thexport'], g:Values())
  source XReloaded
  assert_equal(3, g:loadCount)
  assert_equal(['init', 'yes', 'again', 'once', 'thexport'], g:Values())

  delete('XReloaded')
  delete('XExportReload.vim')
  # delfunc g:Values                 # <--- would raised err 'no g:Values' func IF not commented out IF to do second 'source' this
  unlet g:loadCount
enddef

Test_vim9_reload_noclear()

Expected behaviour
1, if sourced this at second time (if delfunc g:Values was not comment out`), would raise err 'no func g:Values'.
// is that expected? looks g:Values was not re-defined at second 'source'.
2, before the day before yesterday, it call exported that imported 'var' directly, but now it had to be exp.exported or XExportReload.exported (as well as 'func' case).
// not sure should be or not, but looks this is a bit un-compatible, existing vim9 scripts/plugins had to add such 'prefix'.
3, E1257: Imported script must use "as" or end in .vim: XExportReload
// my broken english but perhaps end *with* .vim (or the extension must be '.vim') maybe more understandable. :-)
Version of Vim
v8.2.4036
Environment
linux
Logs and stack traces
#9484
#9485

I am not quite sure what you did and what you have problems with.
As the script is given it won't work, because this line is commented
out:
 # import './XExportReload' as exp

But "exp.exported" is used.  "exp" will not be defined.
It is a change in behavior, Vim9 scripts that used import will have to
be changed.
Loading a second time is expected to give different behavior, since the
"s:loaded" variable exists and "finish" is invoked.
--
hundred-and-one symptoms of being an internet addict:
255. You work for a newspaper and your editor asks you to write an
article about Internet addiction...in the "first person."
/// Bram Moolenaar -- @.*** -- http://www.Moolenaar.net   \
///                                                                      \
\\        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

I am not quite sure what you did and what you have problems with.

pls try following demo code, perhaps a bit more clear.. just copy it and ':so %' two times, at second time it would riased err about 'no g:Values func'.
// this is the first issue in/as this ticket description.
// as for the second issue:
pls check those case_1 and case_2 and case_3 in following code, before the day before yesterday, case_3 worked, but now looks only case_1 and case_2 works. this is a bit un-compatible, but this had to be changed, then some existing vim9script had to be re-factor too..............
vim9script

def Test_vim9_reload_noclear()
  var lines =<< trim END
    vim9script
    export var exported = 'thexport'

    export def TheFunc(x = 0)
    enddef
  END
  writefile(lines, 'XExportReload.vim')
  lines =<< trim END
    vim9script noclear
    g:loadCount += 1
    var s:reloaded = 'init'
    # import './XExportReload' as exp      # <---
    import './XExportReload.vim'           # <---

    def Again(): string
      return 'again'
    enddef

    # exp.TheFunc()                        # <--- case_1
    echom XExportReload.exported           # <--- case_2
    # echom exported                       # <--- case_3

    if exists('s:loaded') | finish | endif
    var s:loaded = true

    var s:notReloaded = 'yes'
    s:reloaded = 'first'
    def g:Values(): list<string>
      # return [s:reloaded, s:notReloaded, Again(), Once(), exp.exported]
      return [s:reloaded, s:notReloaded, Again(), Once(), XExportReload.exported]
    enddef

    def Once(): string
      return 'once'
    enddef
  END
  writefile(lines, 'XReloaded')
  g:loadCount = 0
  source XReloaded
  assert_equal(1, g:loadCount)
  assert_equal(['first', 'yes', 'again', 'once', 'thexport'], g:Values())      # <---
  source XReloaded
  assert_equal(2, g:loadCount)
  assert_equal(['init', 'yes', 'again', 'once', 'thexport'], g:Values())
  source XReloaded
  assert_equal(3, g:loadCount)
  assert_equal(['init', 'yes', 'again', 'once', 'thexport'], g:Values())

  delete('XReloaded')
  delete('XExportReload.vim')
  delfunc g:Values                 # <--- would raised err 'no g:Values' func IF not commented out IF to do second 'source' this
  unlet g:loadCount
enddef

Test_vim9_reload_noclear()

oh........... my bad, i did not notice that finish.
pls ignore the first issue.
// but how about second issue?

i saw you committed new patch (8.2.4044) and updated doc a bit as well,
but import exported from './XExportReload.vim' such style 'import' (keyword 'from') still / no longer supported..  :-(

looks this vim9 'import' style change had been made as permanent, so/then let it be..
// and patch 8.2.4063 yesterday helped and fixed a big mess, so ok then... :-)

looks this vim9 'import' style change had been made as permanent,
so/then let it be..
// and patch 8.2.4063 yesterday helped and fixed a big mess, so ok then... :-)

I'm still adding some more tests, there might be a couple remaining
problems.  Let me know if you have an example of what doesn't work.
--
Microsoft's definition of a boolean: TRUE, FALSE, MAYBE
"Embrace and extend"...?
/// Bram Moolenaar -- @.*** -- http://www.Moolenaar.net   \
///                                                                      \
\\        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

v8.2.4264 revoked the '#' style function name in vim9, but:
1, that made some complex to call such vim9 func in legacy vim script
e.g vimrc.

I don't see how.  You can still call the autoload function using the #
form.

2, that exported func name had to be 'Uppercase' first letter?
-   func auto9#getsome()
+   export func Getsome()

Yes, that is intentional.  In legacy script there was an inconsistency,
allowing lower case function names.  It was OK there since you always
had to prefix "scriptname#".  But in Vim9 script you can call the
function without the prefix inside the script, therefore the leading
capital is required.

3, in some languages, if that first letter of function name is
Uppercase, that means 'public' already, as my understanding, if it do
req 'Uppercase' then maybe no req 'export' keyword?!

No, we do not do it that way.
--
I once paid $12 to peer at the box that held King Tutankhamen's little
bandage-covered midget corpse at the De Young Museum in San Francisco.  I
remember thinking how pleased he'd be about the way things turned out in his
afterlife.
(Scott Adams - The Dilbert principle)
/// Bram Moolenaar -- @.*** -- http://www.Moolenaar.net   \
///                                                                      \
\\        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

Hi,
On Tue, Feb 1, 2022 at 8:05 AM Bram Moolenaar @.***>
wrote:

v8.2.4264 revoked the '#' style function name in vim9, but:
1, that made some complex to call such vim9 func in legacy vim script
e.g vimrc.

I don't see how. You can still call the autoload function using the #
form.

The recent changes to disallow the use of '#' in a function name and the
changes to the import mechanism resulted in quite a bit of changes to the
LSP Vim9 plugin.
You can see the impact in the following commits:
https://github.com/yegappan/lsp/commit/aeede042a93441f038f6b36448aaf383969bc86b
https://github.com/yegappan/lsp/commit/d7105d210391ad8fe3733d81f048df7a970b2488
In particular look at the changes to the plugin/lsp.vim. As all the users
may not
have the latest Vim, the plugin needs to support an older version of Vim
and the latest
version. This is difficult.
Regards,
Yegappan

2, that exported func name had to be 'Uppercase' first letter?
- func auto9#getsome()
+ export func Getsome()

Yes, that is intentional. In legacy script there was an inconsistency,
allowing lower case function names. It was OK there since you always
had to prefix "scriptname#". But in Vim9 script you can call the
function without the prefix inside the script, therefore the leading
capital is required.

3, in some languages, if that first letter of function name is
Uppercase, that means 'public' already, as my understanding, if it do
req 'Uppercase' then maybe no req 'export' keyword?!

No, we do not do it that way.

Yegappan wrote:

On Tue, Feb 1, 2022 at 8:05 AM Bram Moolenaar @.***>
wrote:

v8.2.4264 revoked the '#' style function name in vim9, but:
1, that made some complex to call such vim9 func in legacy vim script
e.g vimrc.

I don't see how. You can still call the autoload function using the #
form.

The recent changes to disallow the use of '#' in a function name and the
changes to the import mechanism resulted in quite a bit of changes to the
LSP Vim9 plugin.
You can see the impact in the following commits:
https://github.com/yegappan/lsp/commit/aeede042a93441f038f6b36448aaf383969bc86b
https://github.com/yegappan/lsp/commit/d7105d210391ad8fe3733d81f048df7a970b2488
In particular look at the changes to the plugin/lsp.vim. As all the users
may not have the latest Vim, the plugin needs to support an older
version of Vim and the latest version. This is difficult.

The autoload mechanism in Vim9 was introduced only recently.
The change indeed had bigger impact than I anticipated.  But I do think
that it is better in the long run.
So far you could have an autoload function call anywhere, just use
"scriptname#Funcname()".  Although this is convenient, it also hides a
dependency on another script, which must be present for this to work.
Now you need an "import autoload 'scriptname.vim'" and then you can use
"scriptname.Funcname()".  Now the import, thus the dependency, is
explicit.  The cost is an extra line.
There is one loophole though: When using a legacy function it can use
the "scritpname#Funcname()" form, also in a Vim9 script.  Perhaps you
can use that as a temporary workaround?
In a cleanly written Vim9 script you would not define a legacy function.
--
If your company is not involved in something called "ISO 9000" you probably
have no idea what it is.  If your company is involved in ISO 9000 then you
definitely have no idea what it is.
(Scott Adams - The Dilbert principle)
/// Bram Moolenaar -- @.*** -- http://www.Moolenaar.net   \
///                                                                      \
\\        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

to be honest, i had been some kind confused how to use those:
s:fooFunc
g:FooFunc
export def FooFunc
or def fooFunc
or what if was not a func but a var
and what if those in autoload/ folder
and what if those in plugin/ folder
and specially what/how if call those vim9 func in legacy vim script..............   :-(
// looks made things a bit complex...

So far you could have an autoload function call anywhere, just use
"scriptname#Funcname()".
[...]
Now you need an "import autoload 'scriptname.vim'" and then you can use
"scriptname.Funcname()".

We can still call an autoload function with scriptname#Funcname() from anywhere.
vim9script
var dir = '/tmp/.vim'
dir->delete('rf')
&runtimepath = dir
dir ..= '/autoload'
dir->mkdir('p')
var lines =<< trim END
    vim9script
    export def Funcname()
        echomsg 'from scriptname#Funcname()'
    enddef
END
lines->writefile(dir .. '/scriptname.vim')
scriptname#Funcname()

from scriptname#Funcname()

Notice that we don't even need :import autoload.
And it has to remain allowed, because there are still 6 contexts where we can't use the Vim9 syntax (because the code is run in the global context):

:help i_CTRL-R_=
:help c_CTRL-\_e
:help stl-%{
:help 'statusline', and :help 'tabline' (%!Func())
:help input() (third {completion} argument)
:help undo_ftplugin

@brammool :
call foo#Bar()
call FooBar()     # or `call g:FooBar()`

looks once if above such func had s: scope action or var in it,
// or it is, e.g g:Foo = s:abc.Foo
then first one is ok when run directly in vimrc (not call in a legacy vim script func),
but second one would be failed (err: not found func).
// but looks (or i guess) No Err if no s: scope action or var in it, or run it manually when vim had enter done.
@yegappan :
if specific to your lsp plugin, the err happened at LspAddServer(cfg), and LspOptionsSet.

Hi,
On Thu, Feb 3, 2022 at 8:12 AM Shane-XB-Qian @.***>
wrote:

@brammool https://github.com/brammool :
call foo#Bar()call FooBar()     # or call g:FooBar()
looks once if above such func had s: scope action or var in it,
// or it is, e.g g:Foo = s:abc.Foo
then first one is ok when run directly in vimrc (not call in a legacy vim
script func),
but second one would be failed (err: not found func).
// but looks (or i guess) No Err if no s: scope action or var in it, or
run it manually when vim had enter done.
@yegappan https://github.com/yegappan :
if specific to your lsp plugin, the err happened at LspAddServer(cfg), and
LspOptionsSet.
I am not able to reproduce this error. Where are you calling the
LspAddServer() function from?
Are you calling it from a legacy vimrc file or a vim9 vimrc file? Are you
calling it at the script
level or inside a function?

BTW, I have updated the plugin to use a global function instead of a global
funcref variable for
these two functions. Can you update the plugin and try again?
Thanks,
Yegappan

issue happened at legacy vimrc and calling a vim9 global (or Uppercase first letter) func.
as the description, the different is foo#Bar() is ok, but FooBar() was failed,
but they both are ok if manually call it at cmdline (of course vim had been enter at then).
// no chance to try your new update yet, but seems this a vim9 bug (if style kept change) too, which perhaps can be workaround by your new update though.
// coz if i guess correctly, FooBar() style vim9 func had init timing issue which diff like foo#Bar() style?
--
shane.xb.qian

From: vim-dev ML @.>
Sent: Friday, February 4, 2022 1:10:48 AM
To: vim/vim @.>
Cc: Shane-XB-Qian @.>; State change @.>
Subject: Re: [vim/vim] 3 issues in vim9script 'import' after yesterday's refactor (Issue #9490)
Hi,
On Thu, Feb 3, 2022 at 8:12 AM Shane-XB-Qian @.***>
wrote:

@brammool https://github.com/brammool :
call foo#Bar()call FooBar() # or call g:FooBar()
looks once if above such func had s: scope action or var in it,
// or it is, e.g g:Foo = s:abc.Foo
then first one is ok when run directly in vimrc (not call in a legacy vim
script func),
but second one would be failed (err: not found func).
// but looks (or i guess) No Err if no s: scope action or var in it, or
run it manually when vim had enter done.
@yegappan https://github.com/yegappan :
if specific to your lsp plugin, the err happened at LspAddServer(cfg), and
LspOptionsSet.
I am not able to reproduce this error. Where are you calling the
LspAddServer() function from?
Are you calling it from a legacy vimrc file or a vim9 vimrc file? Are you
calling it at the script
level or inside a function?

BTW, I have updated the plugin to use a global function instead of a global
funcref variable for
these two functions. Can you update the plugin and try again?
Thanks,
Yegappan
—
Reply to this email directly, view it on GitHubhttps://github.com/vim/vim/issues/9490#issuecomment-1029209510, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADHMHQJ64YAYT6US57KTQQTUZKZJRANCNFSM5LQHSUXQ.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you modified the open/close state.Message ID: @.***>

// so far # style (with Uppercase first letter -IF compare to legacy # style) is the workaround.
// and looks it is a bit complex to make it be compatible if user's vim was not using latest version...

#9967
// closing..


Assess the need and implementation pathways for OGC WFS in the Data Access BB

TiPg currently support OGC API Features but not the legacy OGC WFS standard.
Since OGC API Features is already very mature and widely supported by applications, do we need WFS or can we focus?
Acceptance criteria

[x] Assessed and documented the need for WFS
[ ] If applicable outlined implementation pathways for getting WFS into TiPg - what is missing?

Support for WFS has authoritatively been down-prioritized.
Closing this ticket until further notice.


Openvswitch kernel module isn't available

Describe the bug
I can't use openvswitch, because of missing kernel module
I seen same issue from https://github.com/orbstack/orbstack/issues/1140,
And tried Update Channel in Orb settings from Stable to Canary and reboot everything still not work.
To Reproduce
Create a new ubuntu linux machine
Install openvswitch-switch
Invoke systemctl status ovs-vswitchd. You can see the service failed.
Expected behavior
Openvswitch runs normally
Diagnostic report (REQUIRED)
OrbStack info:
Version: 1.7.2
Commit: 50f93373f351fe839fd72948e6aad032774c0f6c (v1.7.2)
System info:
macOS: 14.5 (23F79)
CPU: arm64, 8 cores
CPU model: Apple M2
Model: Mac14,7
Memory: 16 GiB
Full report: https://orbstack.dev/_admin/diag/orbstack-diagreport_2024-09-19T11-10-23.948058Z.zip

Screenshots and additional context (optional)
Orb machine info
Distro : ubuntu
Version : jammy
Architecture : arm64
Sep 19 10:54:49 ubuntu systemd[1]: ovs-vswitchd.service: Control process exited, code=exited, status=1/FAILURE
Sep 19 10:54:49 ubuntu systemd[1]: ovs-vswitchd.service: Failed with result 'exit-code'.
Sep 19 10:54:49 ubuntu systemd[1]: Failed to start Open vSwitch Forwarding Unit.
Sep 19 10:54:49 ubuntu systemd[1]: ovs-vswitchd.service: Scheduled restart job, restart counter is at 3.
Sep 19 10:54:49 ubuntu systemd[1]: Stopped Open vSwitch Forwarding Unit.
Sep 19 10:54:49 ubuntu systemd[1]: Starting Open vSwitch Forwarding Unit...
Sep 19 10:54:49 ubuntu ovs-ctl[7552]: modprobe: FATAL: Module openvswitch not found in directory /lib/modules/6.10.7-orbstack-00280-gd3b7ec68d3d4
Sep 19 10:54:49 ubuntu ovs-ctl[7545]:  * Inserting openvswitch module
Sep 19 10:54:49 ubuntu ovs-ctl[7556]: rmmod: ERROR: ../libkmod/libkmod-module.c:1941 kmod_module_get_holders() could not open '/sys/module/bridge/holders': No such file or directory
Sep 19 10:54:49 ubuntu ovs-ctl[7556]: rmmod: ERROR: Module unloading is not supported
Sep 19 10:54:49 ubuntu ovs-ctl[7545]:  * removing bridge module

The module is included, but modprobe discovery was broken for certain distros in machines. Fixed for the next version.

Released in v1.7.3.

Many thanks.


Add Graph API version to base URI

Is your feature request related to a problem? Please describe the problem.
Currently, the base URI only contains the national cloud host, meaning each request needs a Graph API version prefix:
$httpClient = GraphClientFactory::createWithConfig($config);
$response = $httpClient->get("/v1.0/me");

Current workaround is to override the base_uri via config:

$httpClient = GraphClientFactory::createWithConfig(['base_uri' => NationalCloud::Global + "/v1.0"]);
$response = $httpClient->get("/me");

This would be a breaking change.
Describe the solution you'd like.
Support setting the Graph API version via the factory & default to v1.0
(With default v1.0)

$httpClient = GraphClientFactory::create();
$response = $httpClient->get("/me");

Or to change to beta

$httpClient = GraphClientFactory::setApiVersion('beta')::create();
$response = $httpClient->get("/me");

Additional context?
No response

This does not necessarily have to be a breaking change.
We could always add an overload that takes in version parameter or add a property to the config object.
https://github.com/microsoftgraph/msgraph-sdk-dotnet-core/blob/9ed307008545e19b516e35e57ff35df061eaf05d/src/Microsoft.Graph.Core/Requests/GraphClientFactory.cs#L57

Good catch, yes we can add a version parameter that defaults to an empty string.
The config object ideally maps to a Guzzle request options object.


Re-sign in Button

Issue with the sign in on the second attempt, when shown the CAPTCHA.
To reproduce:

When signing in, the first attempt doesn't work.
User is asked again for the login details plus the captcha.
Everything is entered in the correct way.
Instead of page.click going to the "Sign In" button it goes to the "Create Account" button.
Get redirected to the create account page.

Possible issues:
Might have to do with giveaway.js file line 84 (but I'm not sure) with the following:
await page.click('a[class=a-button-text][role=button]');
The "Create Account" button has the same class.

Here is a little video of what happens:
https://vimeo.com/342166403
pw: WsdKXyPYB


yajl: New package 2.1.0

Similar to pull request from MINGW-packages (https://github.com/Alexpux/MINGW-packages/pull/1489)

Don't see reason to add it to msys packages


Environment creation can take a long time

Currently, the creation of an environment takes a really long time. This might have to do something with the channel priority arguments. Try if you can solve this problem:
solving environment for 6 hours · Issue #7690 · conda/conda · GitHub, Set the channel_priority in Conda environment.yml - Stack Overflow, Allow configuration setting to be set in environment.yml file · Issue #8675 · conda/conda · GitHub. The solution to this problem might be to set conda config --set channel_priority strict, but it would be nice if this could be set within the .yml file. Another option seems to change the order of the channels (but I do not have the knowledge why this improves the speed), maybe this also helps? https://stackoverflow.com/questions/61239956/is-it-possible-to-specify-a-conda-config-into-an-environment-file/

Using conda config --set channel_priority strict solves this for now (also added this to onboarding document).


Do we still need autoload_classmap.php files?

All autoload_classmap.php files could be removed because YAWIK uses Composer autoloader.

I don't think, the Composer's autoloader creates a map of the modules files, do it?
Only the dependency packages are mapped.

I did not realized that :) I use Composer to autoload everything in my projects. It is much faster than Zend autoload implementation. This way you can let Composer generate one single classmap and avoid class map array merging which is expensive. The great feature of Composer autoloading is also caching via APCu (with fallback to classmap if APCu is not available). I use this in production environment and performance gain is really noticeable.

If you know a way to let composer include the module files in its autoloading, I'm eager to hear...

If I include
"autoload": {
   "classmap": [
       "module/Core/src"
    ]

}
to composer.json, the files are added to "autoload_static.php"
However, when adding:
"autoload": {
"psr-0": {
"Core\": "module/Core/src"
}
}
No actual files are added to the "autoload_static.php", only a namespace mapping...

All you need is to add the following:
"psr-0" : {
	"Core\\" : "module/Core/src/"
}

in the autoload section. Psr-4 cannot be used here due to the extra /Core directory in the /src Directory.  After you call composer dump the /vendor/composer/autoload_namespaces.php will be modified accordingly (the following line will be added 'Core\\' => array($baseDir . '/module/Core/src')). I tested this in my development environment and it worked even if I temporarily disabled Core\Module::getAutoloaderConfig()  method.

That will create no classmap. I do not see where the performance gain is....

The classmap is generated via composer dump -o command.

Additionally you can add:
"config" : {
    "apcu-autoloader": true
}

to enable APCu cache, which is the fastest way (at least in my projects in a production mode)

I just found https://getcomposer.org/doc/articles/autoloader-optimization.md
According to that, you will need to run
composer install -o

or set
"config": { "optimize-autoloader": true }

to create the optimized autoloader (including the classmap).
When using autoload-dev section, we could completely get rid of the Zend_Autoloader.

"config" : {
    "apcu-autoloader": true
}

can be safely added as well ;)


Does not work when assigning function to a name

In frameworks like Ember or Sails.js, I have to declare functions like this:
doSomething: function(a, b) {
    return true;
}

In these situations, DocBlocker picks up that there is a function with two arguments but does not pick up argument and function names. Am I missing some configuration setting?

That example works for me...

Do you have your syntax highlighting set to Javascript?

@spadgos It seems to work now. :-) That was odd. I think I just had to restart Sublime. I'm sorry about that.


introduce registry+v1 bundle provisioner that converts to plain+v0 bundles

This PR builds on the source interface PR to add a new registry+v1 bundle provisioner that converts a registry+v1 bundle to a plain+v1 bundle prior to storing the bundle in the provisioner storage.
There are lots of small pieces of this PR that can be broken out, where I discovered problems that weren't apparent without another provisioner in the mix.
Here's an example of a BundleInstance that you can install with this PR:
apiVersion: core.rukpak.io/v1alpha1
kind: BundleInstance
metadata:
  name: prometheus-operator
spec:
  provisionerClassName: core.rukpak.io/plain
  template:
    spec:
      provisionerClassName: core.rukpak.io/registry
      source:
        type: image
        image:
          ref: quay.io/operatorhubio/prometheus@sha256:5b04c49d8d3eff6a338b56ec90bdf491d501fe301c9cdfb740e5bff6769a21ed

Blocking TODOs:

[x] Get #191 merged and rebase this PR
[x] Get #390 merged and rebase this PR
[x] Get #399 merged and rebase this PR.
[x] Get #401 merged and rebase this PR.
[x] Remove the generic functions from this PR?
[x] Remove OperatorCondition object generation (and associated RBAC), at least for now.

Nice to haves:

[x] Get #377 merged and rebase this PR (not strictly related, but helpful for debugging due to pod name consistency)
[x] Get #405 merged and rebase this PR

Signed-off-by: Joe Lanford<EMAIL_ADDRESS>

I held off on commenting more because I think we'd need to push through the Unpack interface PR first, and functionality the implementation seems reasonable to me once we add tests + more cleanup. I think we can de-duplicate a lot of the registry/plain implementation as a follow-up anyways.
I mentioned this in slack too but we can update the nested registry README.md now that we have something more concrete in place. It would be nice to also showcase in user documentation an example of a BundleInstance resource that has differing unique provisioner IDs being specified.

I briefly playing around with this locally and wasn't able to the plain provisioner working using the example you had pasted in your PR description. When inspecting the content URL contents, it looks like we have the following tree structure:
# output tar contents to the extract directory
$ tree extract
tree extract/
extract/
└── manifests
    └── manifest.yaml

Which seems fine to me at a glance. It seems like the real problem is the manifests.yaml file contains a reference to an OperatorConditions custom resource, and my cluster doesn't have OLM installed. I guess my question here is does requiring OLM CRDs here in order to use a registry+v1 converter make sense? Is this interaction something we need to live with in the short term while we continue iterating?

I guess my question here is does requiring OLM CRDs here in order to use a registry+v1 converter make sense? Is this interaction something we need to live with in the short term while we continue iterating?

Yeah - as is, this PR would require the OperatorCondition CRD to be installed in the cluster. I think its reasonable to remove this for now, but it will be interesting to see if there are OLM operators that completely fail if they can't interact with their OperatorCondition object.

but it will be interesting to see if there are OLM operators that completely fail if they can't interact with their OperatorCondition object.

This is something I was tracking down yesterday and it wasn't clear to me how many existing OLM operators utilize this functionality. That said, if the high level goal with this POC is to avoid operator/bundle authors having to manual migrate from the registry+v1 bundle format, then we'll need to account for that OperatorConditions resource if there's existing logic in some of these operator's controller implementations.
Maybe we can have explicit OperatorConditions handlement as a follow-up to this POC, and keep the scope of these changes fairly tight given we already have the restrictions around install modes + webhook/APIService definitions?

@joelanford Should we add a "Closes https://github.com/operator-framework/rukpak/issues/402" here?


CSS color completion doesn't show color sample

Reported on twitter

MacOS
open a CSS file
press # to bring up color completions

result: in 1.31.0 we don't see the color preview
1.30.2

1.31.0

Same problem, except I am on Windows 10

@jrieken Any idea? Seems #67029 wasn't verified since we forgot to add it to milestone.

doesn't reproduce for me. @octref steps? settings?

Ha, you need to get a hex value proposed. Didn't know we support that. @octref feel free to investigate and fix. This feature is has been added for css only and I think its fair if css maintains it

Muahaha, I think we broken this feature three times with strict-null-works. I am confident this time it's better 🤞


chore: Add test ids to functional tests

What this PR does / why we need it:
Add test ids to functional tests
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

None

/lgtm

/approve


Update overview.md (Typo "Azure Open AI"→"Azure OpenAI")

https://learn.microsoft.com/en-us/azure/ai-services/language-service/question-answering/overview
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/ai-services/language-service/question-answering/overview.md
#PingMSFTDocs

@hyoshioka0128 - thanks!


HHH-12997 - @OneToMany does not work with @JoinFormula

A test that shows that combining @JoinFormula with @OneToMany fails during startup.

@vladmihalcea I would be interested in having your feedback on that.
While I'm not sure this particular test case is correct, @JWGmeligMeyling has a point here: https://github.com/hibernate/hibernate-orm/pull/2547#discussion_r221451368 e.g. that a test does not work when we just add an inverse relationship.
I'm wondering if it's even possible to support an inverse relationship with @JoinFormula.
WDYT?

@gsmet @JWGmeligMeyling I think it's a valid use case and it would be convenient to add support for it.

Here's an updated test which fails on H7.
package org.hibernate.userguide.associations;

import org.hibernate.testing.orm.junit.JiraKey;
import org.junit.Before;
import org.junit.Test;

import jakarta.persistence.CascadeType;
import jakarta.persistence.Entity;
import jakarta.persistence.FetchType;
import jakarta.persistence.GeneratedValue;
import jakarta.persistence.GenerationType;
import jakarta.persistence.Id;
import jakarta.persistence.JoinColumn;
import jakarta.persistence.ManyToOne;
import jakarta.persistence.OneToMany;
import java.util.ArrayList;
import java.util.List;

import static org.hibernate.testing.transaction.TransactionUtil.doInJPA;

/**
 * @author Lisandro Fernandez (kelechul at gmail dot com)
 */
@JiraKey("HHH-13815")
public class BidirectionalOneToManyMergeTest extends org.hibernate.orm.test.jpa.BaseEntityManagerFunctionalTestCase {

	@Override
	protected Class<?>[] getAnnotatedClasses() {
		return new Class<?>[]{
				Post.class,
				PostComment.class,
		};
	}

	@Before
	public void setUp() {
		doInJPA(this::entityManagerFactory, entityManager -> {
			entityManager.persist(
					new Post("High-Performance Java Persistence").setId(1L)
			);
		});
	}

	@Test
	public void testFailMerge() {
		doInJPA(this::entityManagerFactory, entityManager -> {
			Post post = entityManager.find(Post.class, 1L);
			post.addComment(new PostComment("This post rocks!", post));
			post.getComments().isEmpty(); // this fails
			entityManager.merge(post);
		});
	}

	@Entity
	public static class Post {

		@Id
		private Long id;

		private String title;

		@OneToMany(mappedBy = "post", cascade = CascadeType.ALL, orphanRemoval = true)
		private List<PostComment> comments = new ArrayList<>();

		public Post() {
		}

		public Post(String title) {
			this.title = title;
		}

		public Long getId() {
			return id;
		}

		public Post setId(Long id) {
			this.id = id;
			return this;
		}

		public String getTitle() {
			return title;
		}

		public Post setTitle(String title) {
			this.title = title;
			return this;
		}

		public List<PostComment> getComments() {
			return comments;
		}

		private Post setComments(List<PostComment> comments) {
			this.comments = comments;
			return this;
		}

		public Post addComment(PostComment comment) {
			comments.add(comment);
			comment.setPost(this);

			return this;
		}

		public Post removeComment(PostComment comment) {
			comments.remove(comment);
			comment.setPost(null);

			return this;
		}
	}

	@Entity
	public static class PostComment {

		@Id
		@GeneratedValue(strategy = GenerationType.IDENTITY)
		private Long id;

		private String review;

		@ManyToOne(fetch = FetchType.LAZY)
		@JoinColumn(name = "post_id")
		private Post post;

		public PostComment() {
		}

		public PostComment(String review, Post post) {
			this.review = review;
			this.post = post;
		}

		public Long getId() {
			return id;
		}

		public PostComment setId(Long id) {
			this.id = id;
			return this;
		}

		public String getReview() {
			return review;
		}

		public PostComment setReview(String review) {
			this.review = review;
			return this;
		}

		public Post getPost() {
			return post;
		}

		public PostComment setPost(Post post) {
			this.post = post;
			return this;
		}

		@Override
		public boolean equals(Object o) {
			if (this == o) return true;
			if (!(o instanceof PostComment)) return false;
			return id != null && id.equals(((PostComment) o).getId());
		}

		@Override
		public int hashCode() {
			return 31;
		}
	}
}

We should fix this; it looks fairly straightforward. (Just disable the exception when processing orphan delete.)

I'm not sure we will ever implement this feature, but we should have a meaningful error, hence #9320.


pybricksdev: add import inlining option

@dlech Thanks for taking time to review this. I'll make the requested changes as soon as I get some time.

@dlech I think I've addressed all your comments now. Please can you check and review. Happy to make more changes if needed. Thanks.

Module imports are now supported by the firmware, so we will close this pull request. Thanks for submitting!


Improve results for people with many first names

From social media feedback: "I have three first names, the third one is my primary day to day one (not uncommon for swedes). But combinations generated only care about my first first name. "

More info on Swedish middle names, possibly helpful: https://www.hhogman.se/first_middle_names.htm#:~:text=There is no special rule,one of the given names


adding text change to the required skill checkbox in the voluteer pop-up

applied text change as requested.

@Diana380 Thank you for contributing.  This looks great.  Merging now.  :shipit:


Add prelimniary harvester for OpenAire

There are many ways we can collaborate with OpenAire. While we are figuring those out, here is a simple incorporation of the OpenAire OAI PMH metadata endpoint into SHARE.

Note, this PR will pass tests once #368 is merged (as the test generation needed this no-resume option)


import keras_ocr

AttributeError: partially initialized module 'keras_ocr' has no attribute 'pipeline' (most likely due to a circular import)

HI @WiKC73, this is probably due to the naming of the files. Make sure that your python file is not named "keras_ocr".

Thanks worked 👌


Home bar and ion-footer overlap iPhone X landscape mode

Ionic version:  (check one with "x")
[ ] 2.x
[X] 3.x
[ ] 4.x
I'm submitting a ...  (check one with "x")
[X] bug report
[ ] feature request
Current behavior:
As seen in screenshot, I have a navigation bar (attached code below) in my ion-footer element and the home bar is obscuring the menu button in the center.  I am using the updated cordova-statusbar plugin which hides the statusbar on iPX landscape mode, but this bug occurs with old statusbar plugin and no statusbar plugin as well.
Expected behavior:
Padding/safe space will shift footer element above home bar
Steps to reproduce:
Use my footer code (below) and run on iPX in simulator
Related code:
<ion-footer>
    <ion-grid no-padding class="navbar">
        <ion-row>
          <ion-col>
            <button ion-button small block>
              <ion-icon name="arrow-back"></ion-icon>
            </button>
          </ion-col>
          <ion-col>
            <button ion-button small block>
              <ion-icon name="menu"></ion-icon>
            </button>
          </ion-col>
          <ion-col>
            <button ion-button small block>
              <ion-icon name="arrow-forward"></ion-icon>
            </button>
          </ion-col>
        </ion-row>
      </ion-grid>
</ion-footer>

Other information:
N/A
Ionic info:
cli packages:

    @ionic/cli-utils  : 1.14.0
    ionic (Ionic CLI) : 3.14.0

global packages:

    cordova (Cordova CLI) : 7.0.1

local packages:

    @ionic/app-scripts : 3.0.1
    Cordova Platforms  : android 6.3.0 ios 4.5.1
    Ionic Framework    : ionic-angular 3.8.0

System:

    Android SDK Tools : 26.0.2
    ios-deploy        : 1.9.2
    Node              : v8.6.0
    npm               : 5.5.1
    OS                : macOS Sierra
    Xcode             : Xcode 9.0 Build version 9A235

Misc:

    backend : legacy

Hello! Thank you for opening an issue with us!
Duplicated with the sample code you have above. Repo is here: https://github.com/kensodemann/test-iphonex
Thank you for using Ionic

I take that back. Your footer is not wrapped in ion-toolbar, which per the documentation is what makes sure it sizes correctly, which includes sizing for this case.
Wrap your grid as such in the footer, and you will be fine:
<ion-footer>
  <ion-toolbar>
    <ion-grid no-padding class="navbar">
      <ion-row>
        <ion-col>
          <button ion-button small block>
            <ion-icon name="arrow-back"></ion-icon>
          </button>
        </ion-col>
        <ion-col>
          <button ion-button small block>
            <ion-icon name="menu"></ion-icon>
          </button>
        </ion-col>
        <ion-col>
          <button ion-button small block>
            <ion-icon name="arrow-forward"></ion-icon>
          </button>
        </ion-col>
      </ion-row>
    </ion-grid>
  </ion-toolbar>
</ion-footer>

Note that you may need to do a little extra styling to get it to look the way you want, but that is the correct way to deal with this.
Closing this, but will reopen if you can't get that to work for some reason.

Pushed above fix the repo I reference for this Issue

Sorry for the mistake, Ken.  I’ll make sure to check the documentation better next time. Thanks for looking into this!


Using nodejs-pubsub client in multi tenant application

Hi,
Background:
We are building a Multi tenant node js application where user can come in with their credentials and use our app to interact with Google pub sub.
Few points to be noted:

The application we are trying to build is a multi tenant node js application.
There will be a single node process running in which multiple users can come with their access tokens and use the application to interact with cloud pub sub for integration purpose.

Question:

Is this client capable to be used in multi tenant single node process ?
Can we instantiate multiple client belonging to different service accounts in a single node process ?

Please suggest.
Thanks.

@nazimkh At a glance, you should be able to make separate PubSub objects and publish for different clients. I don't know the full stack offhand, so I'm not 100% sure of that, but it makes sense to me.
The way to get different authentication for each one is to pass in the credentials manually instead of letting the library pull it from environment variables. So you'd create one more or less like this:
const pubsub = new PubSub({
  projectId: 'yourProject',
  credentials: {
    client_email<EMAIL_ADDRESS>    private_key: "-----BEGIN PRIVATE KEY-----\n etc",
  },
});

You can find those client_email and private_key values from the downloaded JSON key that you get from the GCP web console. Instead of credentials you can also use keyFilename and pass a path to the JSON key.
If that works for you, go ahead and close the issue out, or let me know if you need further help.

@feywind it works properly. Thanks


some minor changes

changed .gitignore so it excludes all files under .idea
added methods to Expr to make it compile
ExprSpec tests marked as pending

I reverted my commit.
I thought that the idea was to let the student complete the implementation. The ExprSpec wasn't compiling because method were missing on Expr.
Later I saw that the 'convention' is to have the tests completely comment out and let the student add the methods themselves.

It's too easy to implement palindrome and make the test pass:
The following impl will make the test pass.
def palindrome(s: String): String = s

We should instead return Boolean
def palindrome(s: String): Boolean = s.reverse == s

Which is also trivial, but at least we can have tests that evaluate to false.

Dave, after comparing IntList and HigherOrder files it's clear that HigherOrder was simply repeating part of the code that is already defined in IntList. Therefore I suggest to merge HigherOrder.scala into IntList.scala (see c94b110).
HigherOrderSpec stays and import IntList._ (see af8e833)

closed it as only the palindrome will be integrated.


Out of Memory Issues while Transcoding

Describe the bug
Cloned the react demo and modified to select videos from filesystem.
To Reproduce
I selected an 2mb .MOV file and received this error in the console:
ffmpeg-core.js:1 Pthread aborting at Error
    at abort (https://unpkg.com/@ffmpeg/core@0.7.1/ffmpeg-core.js:1:17294)
    at abortOnCannotGrowMemory (https://unpkg.com/@ffmpeg/core@0.7.1/ffmpeg-core.js:1:25109052)
    at _emscripten_resize_heap (https://unpkg.com/@ffmpeg/core@0.7.1/ffmpeg-core.js:1:25109113)
    at <anonymous>:wasm-function[1681]:0xf9ff8
    at _e (<anonymous>:wasm-function[588]:0x274d7)
    at <anonymous>:wasm-function[4855]:0x405053
    at $e (<anonymous>:wasm-function[1682]:0xfa033)
    at <anonymous>:wasm-function[380]:0x11346
    at <anonymous>:wasm-function[2804]:0x202ad3
    at <anonymous>:wasm-function[14466]:0xb781d2

Desktop (please complete the following information):
Chrome, Mac OS

Modified app.tsx:
import React, { useState, useCallback } from 'react';
import { createFFmpeg } from '@ffmpeg/ffmpeg';
import './App.css';

function App() {
  const [videoSrc, setVideoSrc] = useState('');
  const [message, setMessage] = useState('Click Start to transcode');
  const ffmpeg = createFFmpeg({
    log: true,
  });
  const doTranscode = useCallback(
   async () => {
    setMessage('Loading ffmpeg-core.js');
    await ffmpeg.load();
    setMessage('Start transcoding');
    await ffmpeg.write('test.avi', videoSrc);
    await ffmpeg.transcode('test.avi', 'test.mp4');
    setMessage('Complete transcoding');
    const data = ffmpeg.read('test.mp4');
    setVideoSrc(URL.createObjectURL(new Blob([data.buffer], { type: 'video/mp4' })));
  }, [videoSrc]);
  const uploadFile = (e) => {setVideoSrc(e.target.files[0])};
  return (

      <video src={videoSrc} controls></video>

      <button onClick={doTranscode}>Start</button>
      <input type="file" id="uploader" onChange={uploadFile}/>

{message}

  );
}

export default App;

me too! Memory always Out of Memory when file size > 100MB

I think this is an error with react, I get this error occasionally on React when using the library but at https://videotranscode.space/ (build-in Svelte) we have had people upload like 2-3 gigs of content and it works fine.

2-3 gigs

It has nothing to do with react, trying still happens in HTML..

try cmd -i input.mp4 -c:v libx264 -preset fast -crf 28 -c:a copy ouput.mp4， You can see the out of Memory Issues

Not sure if the same issue is still there in the latest version (0.9.3), please kindly give it a try and let me know the result. Let's keep this issue open for some time.

Also having out of memory errors with 890kb file on Firefox: https://github.com/ffmpegwasm/ffmpeg.wasm/issues/111

the same problem on 0.9.7

I can confirm that the problem exists on 0.10.1 as well.

I'm also having
[Error] Unhandled Promise Rejection: RangeError: Out of memory
	dispatchException (2.549adfcd.chunk.js:2:273751)
	(anonymous function) (2.549adfcd.chunk.js:2:269979)
	t (2.549adfcd.chunk.js:2:283360)
	s (2.549adfcd.chunk.js:2:283600)
	promiseReactionJob

This issue happens only on my iPhone, Safari 15.2. The selected file is an audio file: MPEG-4, 192 kb/s, 48.0 kHz, 2 channels, AAC LC. It is only 467kb big (20s).
This happens only on a mobile. On Macbook Safari 15.2. everything works fine.
To reproduce:

https://ffmpegwasm.netlify.app/#Demo in iOS Safari, click the "Upload audio/video file" and choose any supported file format.
The SharedArrayBuffer is only supported on the newest iOS 15.2. so make sure it is the case.
The error should appear in console log.

@IvanSivak  I am getting the same issue as you for Safari 15.2 on my iPhone.

still the same problem

still in fmpeg.wasm v0.11.6


Add check for 404 on get repository data

No longer add the body to the error when a 404 is received on get repository data.
closes #11510

LGTM

LGTM

Code LGTM: waiting on CI

Green, thanks!


CupertinoSlidingSegmentedControl long-press issues

Steps to Reproduce

Use this code:

import 'package:flutter/cupertino.dart';
import 'package:flutter/material.dart';

void main() {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      home: MyHomePage(),
    );
  }
}

class MyHomePage extends StatefulWidget {
  MyHomePage({Key? key}) : super(key: key);

  @override
  _MyHomePageState createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  final controller = ValueNotifier(false);

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text('Test App'),
      ),
      body: ValueListenableBuilder<bool>(
        valueListenable: controller,
        builder: (context, selected, _) => CupertinoSlidingSegmentedControl<bool>(
          children: {
            false: Text('No'),
            true: Text('Yes'),
          },
          groupValue: selected,
          onValueChanged: (value) => controller.value = false,
        ),
      ),
    );
  }

  @override
  void dispose() {
    controller.dispose();
    super.dispose();
  }
}

Press on "Yes" => nothing happens.
Long-press on "Yes" => shown selection switches to "Yes".
Press on "No" => nothing happens (cause controller value is still false and so no rebuild is caused)
Long-press on "No" => shown selection switches to "No".

Expected results:
The shown selected value should not change even on long press.
Actual results:
Simple press on "Yes" does nothing but long-press causes the shown selection to change.
I tested this on android, ios and macos build with the same result.

Logs

$ flutter doctor -v
[✓] Flutter (Channel stable, 2.2.3, on macOS 11.3.1 20E241 darwin-x64, locale en-GB)
    • Flutter version 2.2.3 at /Users/franky/CODE/flutter-sdk
    • Framework revision f4abaa0735 (3 weeks ago), 2021-07-01 12:46:11 -0700
    • Engine revision 241c87ad80
    • Dart version 2.13.4

[!] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/franky/Library/Android/sdk
    • Platform android-30, build-tools 30.0.3
    • ANDROID_HOME = /Users/franky/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/macos#android-setup for more details.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.5.1, Build version 12E507
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)

[✓] Connected device (3 available)
    • Android SDK built for x86 (mobile) • emulator-5554 • android-x86    • Android 7.1.1 (API 25) (emulator)
    • macOS (desktop)                    • macos         • darwin-x64     • macOS 11.3.1 20E241 darwin-x64
    • Chrome (web)                       • chrome        • web-javascript • Google Chrome 91.0.4472.164
    ! Error: iPad užívateľa Frantisek is not connected. Xcode will continue when iPad užívateľa Frantisek is connected. (code -13)

! Doctor found issues in 1 category.

Hi @FrantisekGazo,
I believe this is an expected behavior from the  apple developer docs this is supposed to behave as a CupertinoSwitch. for two items and I see that it is behaving as it is supposed to.

In versions of iOS prior to 3.0, if a segmented control has only two segments, then it behaves like a switch—tapping the currently-selected segment causes the other segment to be selected. On iOS 3.0 and later, tapping the currently-selected segment does not cause the other segment to be selected.

Keeping this open for further investigation from the team.

Code Sample
import 'package:flutter/material.dart';
import 'package:flutter/cupertino.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      debugShowCheckedModeBanner: false,
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: HomePage(),
    );
  }
}

class HomePage extends StatefulWidget {
  HomePage({Key? key}) : super(key: key);

  @override
  HomePageState createState() => HomePageState();
}

class HomePageState extends State<HomePage> {
  final controller = ValueNotifier(false);

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text('Test App'),
      ),
      body: ValueListenableBuilder<bool>(
        valueListenable: controller,
        builder: (context, selected, _) => Center(
          child: CupertinoSlidingSegmentedControl<bool>(
            children: {
              false: Text('No'),
              true: Text('Yes'),
            },
            groupValue: selected,
            onValueChanged: (value) => controller.value = false,
          ),
        ),
      ),
    );
  }

  @override
  void dispose() {
    controller.dispose();
    super.dispose();
  }
}

Output
https://user-images.githubusercontent.com/31410839/126659734-4af72ac0-a488-4317-8753-4db31f6f4bb7.mov

flutter doctor -v
[✓] Flutter (Channel stable, 2.2.3, on macOS 11.4 20F71 darwin-arm, locale en-GB)
    • Flutter version 2.2.3 at /Users/mahesh/Documents/flutter
    • Framework revision f4abaa0735 (3 weeks ago), 2021-07-01 12:46:11 -0700
    • Engine revision 241c87ad80
    • Dart version 2.13.4

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/mahesh/Library/Android/sdk
    • Platform android-30, build-tools 30.0.3
    • ANDROID_HOME = /Users/mahesh/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.4, Build version 12D4e
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)

[✓] IntelliJ IDEA Community Edition (version 2021.1.2)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 57.0.5
    • Dart plugin version 211.7233

[✓] VS Code (version 1.58.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.24.0

[✓] Connected device (3 available)
    • iPhone 12 Pro Max (mobile) • 6A434744-B348-4FB3-AB10-131292174456 • ios            •
      com.apple.CoreSimulator.SimRuntime.iOS-14-4 (simulator)
    • macOS (desktop)            • macos                                • darwin-arm64   • macOS
      11.4 20F71 darwin-arm
    • Chrome (web)               • chrome                               • web-javascript • Google
      Chrome 91.0.4472.164

• No issues found!

[✓] Flutter (Channel master, 2.4.0-5.0.pre.87, on macOS 11.4 20F71 darwin-arm, locale en-GB)
    • Flutter version 2.4.0-5.0.pre.87 at /Users/mahesh/Documents/flutter_master
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision e084e9d946 (2 days ago), 2021-07-17 12:00:21 -0700
    • Engine revision 14a9e9a50e
    • Dart version 2.14.0 (build 2.14.0-321.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/mahesh/Library/Android/sdk
    • Platform android-30, build-tools 30.0.3
    • ANDROID_HOME = /Users/mahesh/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.4, Build version 12D4e
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)

[✓] IntelliJ IDEA Community Edition (version 2021.1.2)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 57.0.5
    • Dart plugin version 211.7233

[✓] VS Code (version 1.58.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.24.0

[✓] Connected device (3 available)
    • iPhone 12 Pro Max (mobile) • 6A434744-B348-4FB3-AB10-131292174456 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-4
      (simulator)
    • macOS (desktop)            • macos                                • darwin-arm64   • macOS 11.4 20F71 darwin-arm
    • Chrome (web)               • chrome                               • web-javascript • Google Chrome 91.0.4472.114

• No issues found!

Thank you.

This seems to be the same issue as https://github.com/flutter/flutter/issues/46046 but for segmented control.

Not sure what you are referring to by this :

In versions of iOS prior to 3.0, if a segmented control has only two segments, then it behaves like a switch—tapping the currently-selected segment causes the other segment to be selected. On iOS 3.0 and later, tapping the currently-selected segment does not cause the other segment to be selected.

Have you tried the steps I wrote? I'm not expecting to switch to "Yes" when I press on "No". I'm expecting to keep selected "No" and never change, but it changes when I long-press.
As @LongCatIsLooong wrote swipe has the same affect as long-press. The issue seems the same. So it wasn't fixed yet.

@FrantisekGazo, Yes I did try your steps, and neither am I expecting to switch to Yes when pressed on NO, I believe this widget is supposed to respond to gestures and not taps.
As  mentioned in my previous comment

I am able to reproduce the issue the widget changes its state on long press as well as on slide.

I meant, if the widget has yes selected and if you long press on No or slide towards NO the widget switches to "NO" and the other way around.

I would expect it to do so only if I allow change of groupValue: but I set it to false never change.
I have no problem with long-press or slide changing the selected value same way as a regular press. But if I force the value to never change then all change methods (press, long-press and swipe) should behave the same way and do nothing. Now only press does nothing.

@FrantisekGazo  thanks for the clarification, Basically the widget is changing its state without need to call setState this issue seems to be similar to  https://github.com/flutter/flutter/issues/85768
CupertinoSlidingSegmentedControl<bool>(
       children: {
       false: Text('No'),
         true: Text('Yes'),
       },
       groupValue: false,
       onValueChanged: (value) {

    }),
));|


chore(deps): bump rules_rust -> 0.35.0

Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue] chore(deps): bump rules_rust -> 0.35.0
[Optional Fixes commit #PR or SHA]  #31538
[Optional Deprecated:]
[Optional API Considerations:]

for ref - prior art https://github.com/envoyproxy/envoy/pull/31344 - happy to close that one - this one requires some patch-fu and i think might not work out of the box

(just saw you have done the patch-fu - nice!)

/retest

retest is a bit flakey atm :confused:

Dependency validation failed, please check metadata in bazel/repository_locations.bzl
Observed dataplane core deps {'com_github_nlohmann_json', 'com_github_google_quiche', 'utf8_range', 'com_github_zlib_ng_zlib_ng', 'boringssl_fips', 'com_github_jbeder_yaml_cpp', 'rules_foreign_cc', 'com_github_nghttp2_nghttp2', 'com_googlesource_code_re2', 'com_github_gabime_spdlog', 'com_google_protobuf_protoc_osx_aarch_64', 'com_googlesource_googleurl', 'com_google_protobuf', 'com_github_libevent_libevent', 'com_google_protobuf_protoc_osx_x86_64', 'rules_license', 'com_github_fmtlib_fmt', 'com_google_protobuf_protoc_linux_aarch_64', 'net_zlib', 'com_google_absl', 'prometheus_metrics_model', 'com_github_grpc_grpc', 'opencensus_proto', 'boringssl', 'com_google_protobuf_protoc_linux_x86_64', 'com_envoyproxy_protoc_gen_validate', 'com_google_googleapis', 'com_google_protobuf_protoc_win64', 'com_github_cyan4973_xxhash', 'com_github_cncf_xds', 'com_github_google_perfetto', 'io_bazel_rules_go', 'com_github_openhistogram_libcircllhist', 'rules_cc'} is not covered by "use_category" implied core deps {'com_github_bufbuild_buf', 'com_github_nlohmann_json', 'com_github_google_quiche', 'utf8_range', 'com_github_zlib_ng_zlib_ng', 'boringssl_fips', 'com_github_jbeder_yaml_cpp', 'rules_foreign_cc', 'com_github_nghttp2_nghttp2', 'com_googlesource_code_re2', 'com_github_openzipkin_zipkinapi', 'com_github_gabime_spdlog', 'com_google_protobuf_protoc_osx_aarch_64', 'com_googlesource_googleurl', 'com_google_protobuf', 'com_github_libevent_libevent', 'com_google_protobuf_protoc_osx_x86_64', 'rules_license', 'com_github_fmtlib_fmt', 'com_google_protobuf_protoc_linux_aarch_64', 'net_zlib', 'com_google_absl', 'com_github_c_ares_c_ares', 'prometheus_metrics_model', 'bazel_skylib', 'com_github_grpc_grpc', 'com_github_google_tcmalloc', 'opencensus_proto', 'com_github_axboe_liburing', 'boringssl', 'com_google_protobuf_protoc_linux_x86_64', 'com_envoyproxy_protoc_gen_validate', 'opentelemetry_proto', 'com_google_googleapis', 'com_google_protobuf_protoc_win64', 'rules_proto', 'com_github_cyan4973_xxhash', 'com_github_cncf_xds', 'com_github_google_perfetto', 'com_github_gperftools_gperftools', 'io_bazel_rules_go', 'com_github_openhistogram_libcircllhist'}: {'rules_cc'} are missing

i think my pr may have resolved this

seems not, i might have a fix locally - ill try and dig it out

/lgtm deps

@RiverPhillips i couldnt find the fix locally - so maybe im confusing with another dep - the error is usually not too hard to resolve other than the tool thats erroring being a bit resource-hungry and annoying to run

I ran it locally and get the same error relating to rules_cc, bit strange considering I didn't change it. Will do some more digging

i think the dep tree just shifed a little so another dep needs to be marked as used somewhere

Waiting on a fix
/wait

hmm, so @RiverPhillips this seems a bit more complicated after all - its rules_cc that is missing as an explicit dep i think
probs we need to add it - seems a bit odd that we havent already as we do use it - i think its pulled in implicitly by rules_foreign_cc (fwiw that one is already marked as dataplane_core)


Add support for twitter quick-replies buttons

Do so as soon as quick-replies are out of beta in twitter DMs.
bot.sendDefaultButtonMessageTo should then create those in Twitter DMs

Moved to appropriate package: Issue can be found here: https://github.com/botmasterai/botmaster-twitter-dm/issues/1


chore(travis): use 'node' to specify the target version.

This change is

@homu r+

:pushpin: Commit 6b78808 has been approved by saneyuki

:hourglass: Testing commit 6b78808 with merge c31a481...

:sunny: Test successful - status


docs: minor fix on documentation

Minor fixes in documentation for first pull request

Hey! Thank you very much for this!


this fixes #761

I have read the CONTRIBUTING document.
My code is written in Python3 and is ending with .py
I checked to ensure there aren't other open Pull Requests for the same update/change
I have checked that my submission does pass the test on LeetCode.com
My filename follow the naming Conventions
I had linked your PR to an Issue

This one closes #761


fix: do not use legacy single action mode in /scope

Description
We don't want to use in this endpoint, as the forceUseAtIteration will already be non-null
Risk

Deploy Plan

Should we rename legacySingleActionMode into forceSingleActionMode since it overrides those fields? (Not to do on this PR)

agreed !

agreed !

I can take it 👍🏻


RuntimeError("grad can be implicitly created only for scalar outputs")

Hello, thank you for your great work. I am training my own dataset and encountered the following error.
Ignoring class  0  in IoU evaluation
[IOU EVAL] IGNORE:  tensor([0])
[IOU EVAL] INCLUDE:  tensor([1, 2])
Lr: 3.106e-05 | Update: 2.258e-01 mean,4.181e-01 std | Epoch: [0][0/322] | Time 3.170 (3.170) | Data 0.154 (0.154) | Loss 1.9250 (1.9250) | acc 0.533 (0.533) | IoU 0.363 (0.363) | [1 day, 20:35:54]
Traceback (most recent call last):
  File "/content/LiDAR-MOS/mos_SalsaNext/train/tasks/semantic/train.py", line 178, in <module>
    trainer.train()
  File "../../tasks/semantic/modules/trainer.py", line 274, in train
    show_scans=self.ARCH["train"]["show_scans"])
  File "../../tasks/semantic/modules/trainer.py", line 391, in train_epoch
    loss_m.backward()
  File "/usr/local/lib/python3.7/dist-packages/torch/_tensor.py", line 396, in backward
    torch.autograd.backward(self, gradient, retain_graph, create_graph, inputs=inputs)
  File "/usr/local/lib/python3.7/dist-packages/torch/autograd/__init__.py", line 166, in backward
    grad_tensors_ = _make_grads(tensors, grad_tensors_, is_grads_batched=False)
  File "/usr/local/lib/python3.7/dist-packages/torch/autograd/__init__.py", line 67, in _make_grads
    raise RuntimeError("grad can be implicitly created only for scalar outputs")
RuntimeError: grad can be implicitly created only for scalar outputs

  optimizer.zero_grad()
            if self.n_gpus > 1:
                idx = torch.ones(self.n_gpus).cuda()
                loss_m.backward(idx)
            else:
                loss_m.backward() #here i got the error
            optimizer.step()

I have looked the error in google, and it usually happens when you use two or more GPUs. However, I am using only one GPU and got this error. Could you please help me to solve this error.

It looks like a version conflict problem and I have never met this problem before.
Could you please provide your environment info here? Let's see whether other users have any solutions or not.

Since there is no update. I would like to close this issue.
Feel free to reopen this issue if needed.


BUG | Update the Farm Event XMLs to match the Normative Document

🐛 Bug Report
Some of the Farm Event XMLs do not match the Normative Document. There are a couple missing KDEs like humanWelfarePolicy.

This has been fixed.


Export photos?

Can I export photos?

Yes, sure.
But you'll need to update or write new exporter for that.
And inside format method add something like:
media = getattr(msg, 'media', None)
if media:
    if isinstance(msg.media, MessageMediaPhoto):
        exporter_context.tg_client.download_media(msg, 'downloads/%s.jpg' % msg.id)

Thanks. Done!


Export path for psql binary for deprecated restore methods

Such that calling https://github.com/cloudfoundry/bosh/blob/master/src/bosh-director/lib/bosh/director/api/controllers/restore_controller.rb#L7 for just restoring the DB with an existing dump still works.
Wdyt? Can we pull this in or should we rather remove this controller and action completely and tell people with this use-case to rely on their own scripts doing scp and ssh -c?

Seeing as we have removed the old director backup and restore functionality, I'm going to close this PR and add a chore to remove this template.
Best,
@jfmyers9, CF BOSH


Add Birthday and Full Mailing Address To Edit Info Tab On User Profile

fixes #4520

"Edit Info" tab on a user profile (user/{user_id}/info) now includes the full mailing address and birthday of users

cc: @namimody

cc @namimody for testing!

:+1:

wait, @katiecrane does this still 'validate'?

@angaither I didn't 'validate' anything on purpose so probably not? What needs to happen?

@katiecrane ah, right but the fields don't update/save.
You also need to update the submit hook to save those values dosomething_user_info_form_submit

@katiecrane try the date like  date('y-m-d, $values['birthdate'])

:+1:


generic arenas

I ran into an issue where a generic function needs to take a type T as input and internally use an arena based on T. But rust doesn't allow items to reference type parameters of the parent scope, so (I believe) this is impossible currently. Easy solution: allow arenas to be generic. This just adds a little syntax to the make_arena! macro that lets you introduce and use generic parameters by just dumping the entire contents of a parenthesis-wrapped token tree into generic param brackets. So we can now do things like this:
#[derive(Collect)]
#[collect(no_drop)]
struct Test<'gc, T: 'gc + Collect>(Gc<'gc, T>);
make_arena!(TestArena(T), Test(T)); // introduce and then use a type param T

fn test<T: 'static + Collect + Copy>(v: T) -> T {
    let arena = TestArena::new(Default::default(), |mc| Test(Gc::allocate(mc, v)));
    arena.mutate(|_, arena| *arena.0)
}

assert_eq!(test(34), 34);
assert_eq!(test(false), false);

The reason for taking token trees like ( $($t:tt)* ) rather than a comma-separated ident list like < $($t:ident),* > was for two reasons: 1) it allows the left (introducing) side to have const generics like Foo(const N: usize) and 2) it allows the right to have non-trivial type expressions like Bar(<T as Thingy>::Output). It also makes it really easy to parse with macro_rules! since parenthesis mark the boundaries of token trees. There's probably some token munching magic we could do to allow angle brackets instead of parenthesis for this, but I don't think it's worth the effort in this case as long as we document it well.
This also renames the 'a lifetime in the dyn trait decl to 'gc to match existing standards since it is exposed to the root type generic parameters: e.g., you can write something like make_arena!(Foo(T), Bar(Gc<'gc, T>).
I also removed the macro overload without $vis:vis because apparently :vis matches empty string and in that case is equivalent to pub(self) anyway.

Yeah I'm not crazy about the (T) syntax but I completely understand why, and I think this is an important thing to allow.
Is there a "standard" for the format here? Do you happen to know of another crate that has to do roughly the same thing? If we're copying an existing technique I'll feel much better about picking a syntax. I know it's a pretty minor thing..

I also removed the macro overload without $vis:vis because apparently :vis matches empty string and in that case is equivalent to pub(self) anyway.

TIL!

Ok, well in that case I decided to take the time and write a proper tt muncher for it, so now we use angle brackets instead like normal generics. It's probably more prone to edge case issues. For instance, I didn't build in support for writing trait bounds on the introduced generics, but generic type aliases don't allow those anyway - we'll just need to document that fact. I'll add some doc info about it after we settle on any other style changes. One I was considering was making it more obvious this was a special type alias (which have different generic behaviors) by doing something like make_arena!(pub type MyArena<...> = MyRoot<...>) or similar.

Another thing to consider is whether we want to continue doing the auto-insertion of 'gc in the root type. I think we should keep that for backwards compatability if the root type doesn't have an explicit generic param list, but we could make it be explicit otherwise. So make_arena!(MyArena, MyRoot) and make_arena!(MyArena, MyRoot<'gc> would be equivalent.

Oh shoot, thank you for doing all that work writing the muncher but I actually think I like the simpler solution more, I should have been more clear before! I'd MUCH rather have something simpler that works, I just wanted to know if there was any standard practice because I'm just really unfamiliar with it. I'm sorry to make you a bunch of work without explaining it better!
I want to merge this because I think having this ability is important, but I need to take a step back and actually think about whether this macro needs to exist at all. I originally wanted to replace the macro with a trait and GATs, but @Aaron1011, who knows a lot more about this than me (they are a rustc dev), said that it was more compatible to avoid doing this and use a different technique.
There's another PR I want to merge too, #28, which also uses a lifetime transmute on the root type which is what was pointed out is not technically allowed in the current version of the compiler[1], if I'm understanding this right. I want to revisit this decision for a couple of reasons, I might not even mind relying on technically disallowed behavior or behavior only defined in nightly compiler depending on what is actually required. I don't want to do these things, but I have something I'd like to do soon that might require.. something like this, I'm not sure yet. Getting rid of this macro or simplifying it might be an important part of it. Let me explain...

Okay, this is a bunch more context for these decisions, this is not as important, feel free to skip, I just want to put this down in writing somewhere while I work on it...
I originally was ready to hand maintenance of this crate over to @Aaron1011 or anyone else who more actively used it, because I haven't used this crate in ages. I still think I should share maintenance and I'm glad I gave them maintenance privileges on the crate so it doesn't have a bus factor of 1, and I would even be willing to bring on more maintainers. Tbh I'm not good at open source stuff at all, so any help is appreciated. I'm a game dev by trade, I'm not even used to PR based development and code reviews really! And speaking of that...
In the last few days I had what might be a Very Good Idea:tm: about how to rework the gc-sequence crate and I want to do a deep dive on it this weekend. I don't know what all will be involved or if I will run into an unsolvable problem, but I think I might have a way to use async functions with await as gc points in a way that actually works today. This idea is not new.. I might have been the first person to think of it but I don't know for sure, but I thought of it way back in late 2018 / early 2019 or something and just sat on the idea for 3+ years because I couldn't manage to make it work.
I stopped updating the luster crate because it was so much of a nightmare to try to make work with combinators, so I think this might actually be a very good thing to explore. It's SO difficult to work with combinators that it made me rethink the entire "branded lifetime" gc technique and is part of the original reason I just lost interest. (Also I started a new game project and had other things going on in my life at the time and there were other reasons, but this was a big part of it.)
I think I might have a way to make all this work, but it will require making many different types root-able, and it will also maybe require having an actual Root trait.. I think it will in fact, so my plans for what to do here matter for how the make_arena macro works or even if it's necessary at all.
My idea for how to make this work is to have a linked list chain of Root-able structs that are basically the reified "stack" of an async function, and I think I can design the API to use this to not be completely insane. If I can make this work I actually might pick luster back up, because I kinda even want to use it in my current project (at least as an option).
I'm gonna try to do this in a branch but it might involve.. I dunno what it will involve, probably taking the gc-sequence crate entirely apart and rebuilding it, and maybe at least parts of the gc-arena crate. This is what I mean when I say "I'm not always so good at open source".. I can't even really figure out how to split this into individual PRs yet, if I get it to work I'm sure I can manage to make it piecemeal.

[1] https://github.com/rust-lang/rust/pull/101520#issuecomment-1252016235
Apparently transmuting lifetimes is not technically allowed by the compiler until the current nightly: 1.67, but 1) it worked in this crate before now, and 2) it will work in this crate officially as of 1.67 anyway.
Originally when I wrote this, I actually looked into it and I could have sworn this was already at least tacitly considered to be the way forward, that lifetime parameters would have no effect on codegen, but apparently it was less settled than I had imagined. IF a Root trait is required for the idea I have AND there's not a way to express the Root trait using the dyn trick that @Aaron1011 used, I at least am comfortable relying on this behavior, especially if the Root trait requires or is made vastly simpler by GATs. Personally I'm vastly more concerned about simplicity than I am about compatibility, but I understand that is a tradeoff.
Obviously I am open to discussion about all of this in any case.

I think if you just go back to the very simple syntax, even if it's not ideal, I would be okay with merging this. That way no matter what ends up happening with the experiment I want to try, there will at least be a way to support generics. If everybody hates the simple syntax we can try the more complex tt muncher strategy but I am not thrilled about needing to do something like that.

I just reverted back to the parenthesis notation. The more complex one is left in the commit history for reference in case we ever want something like that down the line. The only other issue is whether or not to auto-insert the first 'gc generic param when explicit root type params are specified. Either way is easy (compared to the token muncher), but this way (auto-inserting it regardless) is simplest cause explicit would need one extra (but trivial) macro overload.

I am the literal worst! I was planning on letting you know that there's a PR that is almost ready to merge that supersedes this, #32, and I didn't actually do that when I should have.
The new syntax for the macro is actually vastly simpler and avoids the problem entirely: https://github.com/kyren/gc-arena/blob/39f75f8b5c1ec8c7ed1453e1acb4d8b39ac109b3/src/gc-arena/src/arena.rs#L109
I'm sorry for giving you the runaround, it was not my intention :sob:
BUT if you wanna go take a look at #32 I'm interested in your opinion, particularly anything that might make using the API easier.
If for any reason #32 gets delayed or there are any problems, I will definitely merge this PR, otherwise I'll merge #32 and close this one.

Okay, this should be resolved by #32 now.


Allow JSON construction of params

PostgresML instantiates algorithm params from JSON passed in at runtime. This isn't quite the same as serde deserialization, since the JSON params may be incomplete, and the missing ones will be filled in by Default::default(). We're currently adding this functionality downstream, but wondered if you'd be interested in adopting this upstream as well.
An example is in this PR https://github.com/postgresml/postgresml/pull/332/files#diff-a1bcda73e2901512a661eebf9e868be4f33dd99ac4952a85957397a860ec2035

I think it could be cleaner and easier to maintain here, by adopting #[serde(default)] on structs, if this functionality would be more broadly useful.

I think it could be cleaner and easier to maintain here, by adopting #[serde(default)] on structs, if this functionality would be more broadly useful.

I agree, I think that we can use #[serde(default)]
I am in for this!

Can we close this now, right? @montanalow


Re-link broken and old links in local_cache

Build application with dep on erlang 19.
Will point to local_cache_dir/ns/dep/dep_vsn/19 -> application/deps/dep
Then upgrate to erlang 20, build application again.
When linking - link_if_needed method should determine, that old link differs from new (local_cache_dir/ns/dep/dep_vsn/20) and update link.

Fixed in https://github.com/comtihon/coon/pull/35


feat: Pull Requests View

Sonar cloud failing because of "Duplicate Code", I wonder if that is going to be a problem in this monorepo.
I wonder if we can turn it off?
Either way, need to get the tests passing again


How to use embedding models from huggingface hub?

Hi thanks for the lib! I want to use some embedding models (arch is bert) from hf hub. I have tried gguf, but the converter says bert arch cannot be converted to that. I have also tried directly have a modelfile to import safetensors, but it says Error: unsupported content type: unknown

We need a manual to import embedding models.

I also have the same experience and the same needs. I hope there can be a better solution. I hope ollama can increase support for RAG models and TTS models.

In the llama.cpp file, convert it to gguf, and then import it as a regular model.

In the llama.cpp convert it to gguf, and then import it like a regular model.

Thank you for your response,
Sorry, I tried many times but couldn't complete the conversion and kept showing unsupported types. For this reason, I also built a separate llama.cpp environment.In the end, I had no choice but to run an additional xinference environment, running RAG and TTS separately. In addition, some frameworks such as dify do not support adding TTS or RAG models to the preset ollama model function module. I hope that all of this can run in a single environment of ollama, which is both simple and stable, and very easy to maintain.


Setting global cache timeout causes all queries to be cached

Summary of the issue
When setting the global caching options with:
options.UseMemoryCacheProvider(CacheExpirationMode.Absolute, TimeSpan.FromMinutes(5))
the library starts caching all queries, so even the ones without Cacheble() in the Linq query.
Environment
.NET (Core) SDK version: 6
Microsoft.EntityFrameworkCore version: 6.0.3
EFCoreSecondLevelCacheInterceptor version: 3.3.0
Database: (e.g. SQL Server, SQLite, etc.): PostgreSQL
Cache provider: (e.g. in-memory, redis, etc.): In-Memory

Example code/Steps to reproduce:
options.UseMemoryCacheProvider(CacheExpirationMode.Absolute, TimeSpan.FromMinutes(5))

Output:
EFCoreSecondLevelCacheInterceptor.EFDebugLogger: Debug: InstanceId: 1bb95965-d986-42e1-9ba4-b1613970d5f2, Started @18-3-2022 13:04:20 UTC. Using EFCachePolicy: EFCachePolicy --> Absolute|00:05:00|||False.

...

EFCoreSecondLevelCacheInterceptor.EFDebugLogger: Debug: InstanceId: 1bb95965-d986-42e1-9ba4-b1613970d5f2, Started @18-3-2022 13:04:20 UTC. TableRows[6941e28c-f9c8-445b-aeca-1695487802c0] added to the cache[KeyHash: EF_9A5853DD07378EF0, CacheDependencies: EF_sometable.].

When disabling the standard cache timeout options (options.UseMemoryCacheProvider()), I get this output for the very same query:
EFCoreSecondLevelCacheInterceptor.EFDebugLogger: Debug: InstanceId: 0dcb4bd9-f9f8-4da2-b5c4-1a6b7ff3d7bd, Started @18-3-2022 13:03:33 UTC. Skipping a none-cachable command ....

To be perfectly clear: there isn't any Cacheable() in my query, the only change I'm making is the options for the UseMemoryCacheProvider, with the above result.

Checked the sources as well, to me, it doesn't seem logical to also set the CacheAllQueriesOptions to active when setting the timeout values. Is there any other way to set a global timeout and not enabling caching of all queries?
/// <summary>
/// Introduces the built-in `EFMemoryCacheServiceProvider` to be used as the CacheProvider.
/// If you specify the `Cacheable()` method options, its setting will override this global setting.
/// </summary>
/// <param name="expirationMode">Defines the expiration mode of the cache items globally.</param>
/// <param name="timeout">The expiration timeout.</param>
public EFCoreSecondLevelCacheOptions UseMemoryCacheProvider(CacheExpirationMode expirationMode, TimeSpan timeout)
{
    Settings.CacheProvider = typeof(EFMemoryCacheServiceProvider);
    Settings.CacheAllQueriesOptions = new CacheAllQueriesOptions
    {
        ExpirationMode = expirationMode,
        Timeout = timeout,
        IsActive = true
    };
    return this;
}

You are hiding something.

How did you get EFCachePolicy --> Absolute|00:05:00|||False. when you say there isn't any Cacheable() in my query? It comes directly from the tagging a query.
That CacheAllQueriesOptions is not going to be processed when there is no Cacheable() method.
There are other possible scenarios as well which are documented in the readme file.

I sure could have missed something, but can you explain why with only the removal of the default memory cache options, the query is not cached anymore (as per the logging I provided above)?
I do have some Cacheable() calls on some queries, but not on all, I wouldn't expect those to be cached...

What's your full startup settings, related to this library?

serviceCollection.AddEFSecondLevelCache(options => options
          .UseMemoryCacheProvider(CacheExpirationMode.Absolute, TimeSpan.FromSeconds(cacheTimeoutInSeconds))
          .DisableLogging(value: !enableCacheLogging)
          .UseCacheKeyPrefix($"EF_{tenantIdentifier}")); // Add a prefix per tenant to make sure each tenant gets its own cache

serviceCollection
        .AddDbContext<ITenantDbContext, TenantDbContext>(
          (serviceProvider, optionsBuilder) =>
          {
            optionsBuilder.UseNpgsql(connectionString);

            if (enableCaching)
            {
              _ = optionsBuilder.AddInterceptors(serviceProvider.GetRequiredService<SecondLevelCacheInterceptor>());
            }
          },
          ServiceLifetime.Transient);

Try V 3.4.

Seems to work, thanks! :)


Missing install instructions on README.md

Missing name of package in README.md:
npm install @highlightjs/vue-plugin or pnpm add @highlightjs/vue-plugin
Thank you.

+1
Please add this to the readme.

PR is welcome!

Done! https://github.com/highlightjs/vue-plugin/pull/51


update references to new ko-build/ko provider

https://registry.terraform.io/providers/ko-build/ko/latest is now live 🎉

not understanding the CI failure.. maybe it wants single space between the equal sign:
source = "ko-build/ko"


Configuration ist readable from the browser

When following the install doc, I can browse to the app/config directory and open the YAML files containing DB and user passwords.
It should either be protected (and/or mentioned how to protect) or better make only web/ accessible from the browser

The .htaccess should forbid it.
Maybe you edited the /etc/apache2/apache2.conf?
Change "AllowOverride None" to "AllowOverride All" for the directory of the webinterface.
Regards
Andreas


Update Doctor Experience.html

I added some useful fonts with footer, header  style that enhance the looks than before.
Description
Since this page doesn't contain as such impressive footer along with data and about section so that i made changes.
Related Issues

Footer section at below the page

Style tag

text-align

Closes #

Type of PR

[x] Bug fix
[x] Feature enhancement
[x] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)
now you can relate this updated page
Checklist

[x] I have gone through the contributing guide
[x] I have updated my branch and synced it with project main branch before making this PR
[x] I have performed a self-review of my code
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[x] I have commented my code, particularly in hard-to-understand areas.

Thank you!!

send ss of the changes

@ankitmodanwall Resolve conflicts

now resolved conflicts.

@Anishkagupta04
I made few changes as

background palette added
update social medias logo
added black heart as compare to red heart
about section consists of italic font

##Screen-shots

@ankitmodanwall Closing. LATEST upstream footer is better

@varshith257 so what did you mean ?

The current footer satisfies the requirements and there is no assigned issues to this PR too and color Schema is not aligned with Project

Could you share the ss?


Validate options when generating pact publish URL

Fixes issue #12:

Returns a rejected promise with a proper error message
Validates a that a broker url is provided and a valid consumer/provider object exists in the Pact file

Travis CI issues seem to have disappeared and build is green again (and running nice and quick). I've currently left Mac OSX builds out - do we want them back? Not sure how much value they're adding.

Please do.  I want to make sure all our code works in all OS'.  We've been
burned by this before and I don't want it happening again.
On Wed, Jun 22, 2016 at 5:03 PM Matt Fellows<EMAIL_ADDRESS>wrote:

Travis CI issues seem to have disappeared and build is green again (and
running nice and quick). I've currently left Mac OSX builds out - do we
want them back? Not sure how much value they're adding.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pact-foundation/pact-node/pull/13#issuecomment-227660367,
or mute the thread
https://github.com/notifications/unsubscribe/AAjA5HeK5-jfaZ7lMk3p475CclajP0YAks5qON5LgaJpZM4I7S0b
.

Np, I have added them back in. Any objections to merging this now (Mac builds still seem to be affected in TravisCI)? Normally I would wait, but this PR fixes a problem we have released so I don't see harm in releasing on the small chance it doesn't build on OSX (and even then I'll be skeptical as I build on OSX locally).

OK, we're proper green now. Err, well sorta (looking at you Appveyor!).


Perf-wgpu/conv2d

Pull Request Template
Checklist

[ ] Confirm that run-checks script has been executed.
Still a draft.

Related Issues/PRs
Issue #805
Changes
Add autotuning of conv2d function.
Testing
See #805

Closing as this is now obsolete with recent wgpu backend changes.


⚠ Fortnite has degraded performance

In 4408782, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1662 ms

Resolved: Fortnite performance has improved in 08b91e8.


iOS Spinner Styling Not Consistent

Description
The Spinner component renders differently on iOS than on web and Android.
CodeSandbox/Snack link
https://snack.expo.dev/@hirvesh/nativebase-template
Steps to reproduce

Include a spinner component in the blank template, it shows up differently on iOS.

See GIF for current render.

NativeBase Version
3.4.5
Platform

[ ] Android
[ ] CRA
[ ] Expo
[X] iOS
[ ] Next

Other Platform
No response
Additional Information
No response

This is the expected behavior since we want to render the native Activity Indicator. if you look closely it's actually different on all the three platforms. Closing this issue since it's not a bug.

Alright, thanks for clarifying Rayan! However I have one follow up query - setting a size of size={10} does not seem to affect the Spinner size specifically on iOS - is this also expected behaviour?


cron: '0 30 6 * * 1 Europe/Stockholm' This is not working as expected

Tried with cron: '0 36 2 * * 6 Europe/Stockholm' and got the job run.
That cron line means: run at 02:36:00 AM on Saturdays according to Stockholm.
Used this site to check: https://www.timeanddate.com/worldclock/sweden/stockholm


Get the whole chat history of a session.

Is your feature request related to a problem? Please describe.
How can I get the whole chat history of a session instead of getting several latest chat messages and the summary？
Describe the solution you'd like
I can't find a function to solve the problem, maybe it's better to implement related functions.
Describe alternatives you've considered
Additional context

I've got the answer.


Add Swift 4.2 and Swift 5.0 support to podspec

After merging you'll also need to publish a new release with CocoaPods 1.7.5+.
Cheers!

Thank you very much!

Codecov Report

Merging #6 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master       #6   +/-   ##
=======================================
  Coverage   93.83%   93.83%
=======================================
  Files          14       14
  Lines         487      487
=======================================
  Hits          457      457
  Misses         30       30

Continue to review full report at Codecov.

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