Layout

Hi,
I'm rather new to using ZF2 and Skeleton App, please forgive me if I am

Out of place/location or
Incorrect with my issue...

I've just experienced a issue with trying to change layouts both within the Controller using
$this->_helper->_layout->setLayout('altlayout');
And the view using
$this->layout()->setLayout('altlayout');
I have copied the layout.phtml and made one major cosmetic change for testing
trying within the control it complains errors
PHP Notice: Undefined property: Test\Controller\TestController::$_helper
and
PHP Fatal error: Call to a member function setLayout() on a non-object
and the view stays with the default layout.
even though
doing an echo $this->layout()->getLayout(); before and after the setLayout shows the change.
I can't 100% say I haven't done something incorrect and it is a bug, however by all accounts and researching I feel I've done everything correctly and things are not responding as expected... particularly the $this->layout()->setLayout('altlayout');
Can someone please confirm this is a bug, then I'll stop going round in circles and pulling code apart :)
Thanks in advance,
T

Ok
So I found on a french forum a partial fix
http://www.z-f.fr/forum/viewtopic.php?id=7092 #6
they modified the renderLayout () of Listener.php to fix disabling layout
$this->getLocator()->get('view')->layout()->disableLayout();
from this i've done some fiddling and made a rudimentary fix, but I'm not very familiar ZF2 or ZF1 and there is bound to be a more efficient way.
within a controller you can now do any of the following
$this->getLocator()->get('view')->layout()->setLayout('layouts/ajax.phtml');
$this->getLocator()->get('view')->layout()->setLayout('ajax');
$this->getLocator()->get('view')->layout()->disableLayout();
within a view phtml file you can  do
$this->layout()->setLayout('layouts/ajax.phtml');
$this->layout()->setLayout('ajax');
$this->layout()->disableLayout();
below is the change required in renderLayout() of Listener.php
/*
//--------------------------- Original Code ----------------------------
$layout   = $this->view->render($this->layout, $vars);
$response->setContent($layout);
return $response;
*/
//---------------------- Fix For Disable Layout --------------------
if(($this->layout !== $this->view->layout()->getLayout())&&(strstr($this->view->layout()->getLayout(),'.phtml'))){
// If the getLayout is different from default layout and contains .phtml
$this->layout =  $this->view->layout()->getLayout();
}elseif((basename($this->layout, ".phtml")!==$this->view->layout()->getLayout())&&!(strstr($this->view->layout()->getLayout(),'phtml'))){
// If default layout filename (without phtml) does not equal getLayout then select differnet view file within the same directory as the default layout
$this->layout = dirname($this->layout).'/'.$this->view->layout()->getLayout().'.phtml';
}
$layout = $this->view->render($this->layout, $vars);
return ($this->view->layout()->isEnabled()) ? $response->setContent($layout) : $response->setContent($vars['content']);
//------------------------------------------------------------------

I've also managed to get what I want and think this is probably (although I am also new to ZF1+2) close to the actual solution that ZendSkeletonApplication will take:
inside module.config.php:
    	'Zend\View\Helper\Json' => array(
    		'parameters' => array(
    			'layout' => 'Zend\Layout\Layout'
    		),
    	),

    	'Zend\View\Helper\Layout' => array(
    		'parameters' => array(
    			'layout' => 'Zend\Layout\Layout'
    		),
    	),

        'Zend\Layout\Layout' => array(
            'parameters' => array(
            	'options' => array(
            		'layout' => 'layout/layout.phtml',
            	),
            ),
        ),

inside Listener.php:
    $layoutObj = $this->view->layout();
    if ($layoutObj->isEnabled()) {
    	$layout = $this->view->render($layoutObj->getLayout(), $vars);
    } else {
    	$layout = $contentParam;
    }
    $response->setContent($layout);

inside RandomController.php:
public function randomAction {
   // do stuff
   return array(
		'data' => array(
			'foo' => 'bar'
		)
	);
}

inside the view file random.phtml:
<?php echo $this->json($this->data) ?>

when you visit the 'random' action you will now get the following output:
{"foo":"bar"}
Perfect! Been at it all day and now I've managed to get exactly what I wanted :) I like this because the frontender chooses what he wishes to do with the data... if I decide that I want to change my action to be JSON for another place then I just go into its view and change the echo to $this->json() and the layout is disabled from there!

This issue is mostly obsolete now with the new view layer. Please check out the new stuff and see if you still have any problems. Meanwhile, I'll go ahead and close this issue.


Fix typos

See diff ;-) I hope this was not an intentional duplication of the. I guessed it was just copied from some template with that typo.

Thanks @katrinleinweber !  It looks like the type itself is actually in the Swagger template here: https://github.com/swagger-api/swagger-codegen/blob/master/modules/swagger-codegen/src/main/resources/ruby/base_object.mustache#L8.  So, the next time we generate the typo would come back 😦 .  But, we can override the template to fix it.  Would you be up for copying the template file into this directory and then fixing the typo there?  That way the fix will persist next time generate as well.
Thank you!

I'm guessing https://github.com/swagger-api/swagger-codegen/pull/9019 makes even more sense in the long-run, albeit probably taking longer to trickle down initially, doesn't it?

@katrinleinweber Yes!  That's probably the best place so we don't have to override the template just to change the typo.  Thanks for submitting that on the original repo!  Are you ok with us closing this PR out and waiting for that change to come down from the Swagger repo?

Sure :-)


profiler: Keep track of stack unwinding failures

Signed-off-by: Kemal Akkoyun<EMAIL_ADDRESS>As a pre-work to #346, add metrics to keep track of stack unwinding failures.
cc @v-thakkar

LGTM!

Looks great!!
I think you might have mentioned this at some point, but perhaps we could check that the addresses in userspace are all within the stack low<->top addresses? I am unsure if the kernel does this already (checking now!) but if it doesn't it might be worth doing the check ourselves

I don't think kernel does this. I came to that conclusion because we received addresses that we can't map any object file. AFAIK (don't quote me on that), if we receive out-of-bounds addresses, we can say that the Kernel failed to unwind the stack. The only boundary check we have to find the mapping.
https://github.com/parca-dev/parca-agent/blob/e8afc39e6c19f9cb1fa2684a150ae85068d3de6b/pkg/maps/mapping.go#L82-L90

The addresses that we couldn't symbolize and don't have [*] prefix is how it manifests itself on icicle graphs.
We should investigate this more, though. Happy to happen an issue (if we haven't gotten one yet)!


index.js is empty when running Node 15.8.0

Firstly thank you for such a fantastic plugin, we have been using it for a long time on our project to great effect!
I have encountered an issue with version 5.0.0 wherein the index.js file that executes the warmup is blank when running Node 15.8.0. This causes an AWS error because it results in a zip file containing a file that is empty:
  Serverless Error ---------------------------------------

  An error occurred: WarmUpPluginDefaultLambdaFunction - Uploaded file must be a non-empty zip (Service: AWSLambdaInternal; Status Code: 400; Error Code: InvalidParameterValueException; Request ID: xxxxx; Proxy: null).

I switched to version 15.2.1 and the file was correctly generated. There was nothing special about this version, it was the version a colleague had installed that could not replicate the above problem.
On a separate project we are using version 4.9.0 of the plugin and this works as expected with Node 15.8.0.
Hope this is useful but happy to provide anything else to help resolve the issue.
Thanks again for a great plugin.

Any more info on this?
It sounds like something totally unrelated to this library.
Like a bug in the fs module, maybe related to the recursive option...
I reviewed Node's changelog but couldn't find anything that seems related...

Closing since the issue seems to be related with Node and not with this plugin.
Feel free to reopen if you think that's needed.


Question: proper way to configure vercel.json routes for dynamic path segments

Hi, I have a question about configuring the routes in vercel.json to correctly point to the dynamic route [...slug].js.

This is not really related to the next-auth library, but given it uses a dynamic path I thought to ask the question here first.

The background is that I'm trying out the Multi zone setup, which requires some route mapping in vercel.json.
I managed to somehow make it work by doing this:
{
  "src": "/api/auth/(.*)",
  "dest": "accounts/api/auth/[...slug]?params=$1"
}

The accounts is the name of one of the website folders.

// /api/auth/[...slug].js

export default (req, res) => {
  const { params, ...rest } = req.query;
  // On production, routes are configured in `vercel.json`.
  // For dynamic routes like this `[...slug]`, we pass the route paths
  // as a `params` query parameter.
  // Therefore, the keep the original functionality, we need to patch the
  // query parameters to use `slug`, which is a list of paths.
  if (params) {
    req.query = {
      ...rest,
      slug: params.split("/"),
    };
  }
  return NextAuth(req, res, options);
};

I'm wondering if there is a better way to do that. Thanks 🤗

Oh! That's really interesting. Thanks for sharing your config!
I am not sure, but I think this is an interesting question, and there might be scope for providing an easier way to do this in (e.g. by exporting  a route handler like next-auth/route).
I've been wondering about adding the option to have NextAuth() route handler look for nextauth.config.js file in the root directory if the 'options' argument is blank; that might work well in this scenario.
Without actually trying it out, it's not clear to me just from scanning the docs for multizone to know if that is possible, but if there are any examples of how to use a module endpoint as a route  that would be super helpful.

Yeah I've been digging the docs and trying things out in the past hour and this was the only way I was able to make it work.
Another interesting question (out of curiosity) is about prefixing the API routes, especially the ones from next-auth.
For example, instead of /api/auth/signin, the routes could be served as /accounts/api/auth/signin
I see that there is an option to pass a basePath:
https://github.com/iaincollins/next-auth/blob/f53a7f3b85f673627514b87430785c2e9bb7ae7e/src/server/index.js#L41
I'm not sure this is the right option though, for example also the site url should be adjusted I suppose.

Hey I totally forgot to document that option, thanks for reminding me!
Yeah that would absolutely be the right option.
e.g. basePath: '/account' would give you routes like this:
/account/signin
/account/callback
/account/callback/google
/account/callback/facebook (etc)
/account/signout
/account/errror

Currently, the only caveat for this is that the client needs to know about a basePath if it's called.
e.g.

session({ basePath: '/account' })
useSession(null, { basePath: '/account' })

This is not documented as, well, it's not very nice and I wanted to make it better.
One option would be to support checking an environment variable like NEXTAUTH_BASE_URL which people could set and configure to export to the client.
However, I'm not clear technically on the best way to do this, and I see that it's in flux in Next.js a little bit - with new .env handling in Next.js in active development so maybe it's worth ignoring for now.

I'm not sure this is the right option though, for example also the site url should be adjusted I suppose.

Oh you are right, basePath is the best option! The site option actually needs to be the top level URL, which the documentation doesn't really specify. It's used to automatically set a policy for callback URLs, etc to prevent bad actors from trying to do naughty things. I just realised the advance option for customising that behaviour isn't documented yet either.
I think the custom pages option is probably the best route in the short term here, rather than customising the basePath. Creating custom sign and signout pages is a bit of a hassle right now, but stuff will come later this week to make that easier.

Thanks for the detailed explanation.
I guess having this behavior documented would be more than enough for starters. Then you can look at a more permanent and nicer solution.
For instance, I would expect this option to work similarly like Gatsby’s pathPrefix which you set in the gatsby-config.js.
Then Gatsby (or NextAuth in this case) can take care of adjusting the paths and links internally, in production mode.

I think the features and documentation for this has improved - and basePath should work in both client and server - so closing this one off.


I would like to contribute documentation and examples.

Hello there BigPipe Team,
I would like to contribute documentation and examples.  First I am trying to learn as much as I can from your repositories and issues.  As far as I can tell from using it:

Pages are out and nested Pagelets are in.
Temper and Primus wrappers for view rendering and realtime connections.
Over 20 modules that help make bigpipe awesome whose status is available here: https://github.com/bigpipe/bigpipe/blob/master/HEALTH.md

Still have a lot to learn, but would love to help anywhere I can and hopefully you guys can point me in the right direction.
Also logo, is it a big tobacco pipe?  https://openclipart.org/detail/183205/Pipe  or  a big pipe: https://openclipart.org/detail/204553/Isometric pipes
Thanks,
Jared

@onesupercoder
We're currently in the process of a complete documentation refactor as we want to move all our documentation to a single Github pages repository so it's easier to maintain and update as the current setup is that great yet. We haven't made that much process on this part yet as we're currently in the process of making BigPipe more modulair. In the 0.9 refactor we already pulled out stuff that doesn't really belong in the "core" of BigPipe as we want to focus making sure that this library only contains the code that is required to correctly and follow the BigPipe pattern as efficient as possible. So more things might still be removed in 0.10.
What we would still love to have are small example apps where people can see what and how you can build apps with this module. We're already discussing building a TodoMVC app: https://github.com/tastejs/todomvc/issues/1161 but anything is more than welcome.

Oh, and apologies for responding that quickly on IRC ;-) was going to send an e-mail tomorrow but saw this issue popup in my inbox instead.

@3rd-Eden that sounds great. :+1:   I was thinking about starting on the github pages repo first because I don't think i would make great example app just yet, but soon.  : ]

@onesupercoder we were thinking of just using jekyll for it. As that's powerful enough for what we're trying achieve here:

Welcome page
Getting started
Documentation
Community
Blog

@3rd-Eden awesome. :+1:  Do you want to make the bigpipe.github.io project and then i will fork it?  Or is there a better way?

Created https://github.com/bigpipe/bigpipe.github.io/ and deprecated https://github.com/bigpipe/bigpipe.io which currently runs the current bigpipe.io version.

I think it makes sense to move all documentation site related discussions to that repository.

Agreed


Go build error

When using go get -v and latest @2.7.1
build github.com/hktalent/scan4all: cannot load embed: malformed module path "embed": missing dot in first path element

I am ok:
$ go get<EMAIL_ADDRESS>go: downloading github.com/hktalent/scan4all v0.0.0-20220803035002-21c15d3054bb
go: added git.mills.io/prologic/smtpd v0.0.0-20210710122116-a525b76c287a
go: added github.com/Azure/go-ntlmssp v0.0.0-20211209120228-48547f28849e
go: added github.com/ChrisTrenkamp/goxpath v0.0.0-20210404020558-97928f7e12b6
go: added github.com/Mzack9999/go-http-digest-auth-client v0.6.1-0.20220414142836-eb8883508809
go: added github.com/Mzack9999/ldapserver v1.0.2-0.20211229000134-b44a0d6ad0dd
go: added github.com/RumbleDiscovery/jarm-go v0.0.6
go: added github.com/akrylysov/pogreb v0.10.1
go: added github.com/alecthomas/jsonschema v0.0.0-20211022214203-8b29eab41725
go: upgraded github.com/alecthomas/units v0.0.0-20190924025748-f65c72e2690d => v0.0.0-20211218093645-b94a6e3cc137
go: added github.com/ammario/ipisp/v2 v2.0.0
go: added github.com/andygrunwald/go-jira v1.15.1
go: added github.com/antchfx/htmlquery v1.2.5
go: added github.com/antchfx/xmlquery v1.3.11
go: added github.com/antchfx/xpath v1.2.1
go: added github.com/antlabs/strsim v0.0.2
go: added github.com/antlr/antlr4/runtime/Go/antlr v0.0.0-20220418222510-f25a4f6275ed
go: added github.com/apex/log v1.9.0
go: upgraded github.com/aws/aws-sdk-go v1.40.45 => v1.44.60
go: added github.com/aymerick/douceur v0.2.0
go: added github.com/bits-and-blooms/bitset v1.2.0
go: added github.com/bits-and-blooms/bloom/v3 v3.0.1
go: added github.com/blang/semver v3.5.1+incompatible
go: added github.com/bluele/gcache v0.0.2
go: added github.com/c4milo/unpackit v0.1.0
go: added github.com/caddyserver/certmagic v0.16.1
go: upgraded github.com/chromedp/cdproto v0.0.0-20220408044303-8559a4e76b35 => v0.0.0-20220629234738-4cfc9cdeeb92
go: upgraded github.com/chromedp/chromedp v0.8.0 => v0.8.2
go: added github.com/corpix/uarand v0.2.0
go: added github.com/denisenkom/go-mssqldb v0.12.2
go: added github.com/dimchansky/utfbom v1.1.1
go: upgraded github.com/dlclark/regexp2 v1.1.4 => v1.4.0
go: added github.com/dsnet/compress v0.0.1
go: added github.com/fatih/structs v1.1.0
go: upgraded github.com/fsnotify/fsnotify v1.4.9 => v1.5.4
go: added github.com/go-ole/go-ole v1.2.6
go: added github.com/go-rod/rod v0.108.1
go: added github.com/go-routeros/routeros v0.0.0-20210123142807-2a44d57c6730
go: added github.com/goburrow/cache v0.1.4
go: added github.com/gofrs/uuid v4.2.0+incompatible
go: upgraded github.com/golang-jwt/jwt/v4 v4.0.0 => v4.3.0
go: added github.com/golang-sql/civil v0.0.0-20190719163853-cb61b32ac6fe
go: added github.com/golang-sql/sqlexp v0.1.0
go: added github.com/google/cel-go v0.11.4
go: added github.com/google/go-github v17.0.0+incompatible
go: added github.com/gorilla/css v1.0.0
go: added github.com/gosnmp/gosnmp v1.35.0
go: added github.com/gosuri/uilive v0.0.4
go: added github.com/gosuri/uiprogress v0.0.1
go: added github.com/h2non/filetype v1.1.3
go: added github.com/hako/durafmt v0.0.0-20210316092057-3a2c319c1acd
go: upgraded github.com/hashicorp/go-uuid v1.0.1 => v1.0.2
go: added github.com/hashicorp/go-version v1.6.0
go: added github.com/hbakhtiyor/strsim v0.0.0-20190107154042-4d2bbb273edf
go: added github.com/hktalent/scan4all v0.0.0-20220803035002-21c15d3054bb
go: added github.com/huin/asn1ber v0.0.0-20120622192748-af09f62e6358
go: added github.com/iancoleman/orderedmap v0.0.0-20190318233801-ac98e3ecb4b0
go: added github.com/icodeface/tls v0.0.0-20190904083142-17aec93c60e5
go: added github.com/itchyny/gojq v0.12.8
go: added github.com/itchyny/timefmt-go v0.1.3
go: added github.com/jcmturner/aescts/v2 v2.0.0
go: added github.com/jcmturner/dnsutils/v2 v2.0.0
go: added github.com/jcmturner/gofork v1.0.0
go: added github.com/jcmturner/goidentity/v6 v6.0.1
go: added github.com/jcmturner/gokrb5/v8 v8.4.2
go: added github.com/jcmturner/rpc/v2 v2.0.3
go: added github.com/jlaffaye/ftp v0.0.0-20190624084859-c1312a7102bf
go: added github.com/karlseguin/ccache v2.0.3+incompatible
go: upgraded github.com/klauspost/compress v1.13.6 => v1.15.8
go: added github.com/klauspost/cpuid/v2 v2.0.11
go: added github.com/klauspost/pgzip v1.2.5
go: added github.com/lcvvvv/gonmap v1.1.8
go: added github.com/libdns/libdns v0.2.1
go: added github.com/lor00x/goldap v0.0.0-20180618054307-a546dffdd1a3
go: added github.com/lufia/plan9stats v0.0.0-20211012122336-39d0f177ccd0
go: added github.com/lunixbochs/struc v0.0.0-20200707160740-784aaebc1d40
go: upgraded github.com/magiconair/properties v1.8.5 => v1.8.6
go: added github.com/masterzen/simplexml v0.0.0-20190410153822-31eea3082786
go: added github.com/masterzen/winrm v0.0.0-20220513085036-69f69afcd9e9
go: upgraded github.com/mattn/go-runewidth v0.0.9 => v0.0.13
go: added github.com/mfonda/simhash v0.0.0-20151007195837-79f94a1100d6
go: added github.com/mholt/acmez v1.0.2
go: added github.com/mholt/archiver v3.1.1+incompatible
go: added github.com/microcosm-cc/bluemonday v1.0.19
go: upgraded github.com/miekg/dns v1.1.49 => v1.1.50
go: upgraded github.com/mitchellh/mapstructure v1.4.2 => v1.5.0
go: added github.com/nwaples/rardecode v1.1.2
go: added github.com/olivere/elastic v6.2.37+incompatible
go: added github.com/openrdap/rdap v0.9.1-0.20191017185644-af93e7ef17b7
go: added github.com/owenrumney/go-sarif/v2 v2.1.2
go: upgraded github.com/pelletier/go-toml v1.9.3 => v1.9.5
go: added github.com/pelletier/go-toml/v2 v2.0.1
go: upgraded github.com/pierrec/lz4 v2.0.5+incompatible => v2.6.1+incompatible
go: added github.com/power-devops/perfstat v0.0.0-20210106213030-5aafc221ea8c
go: added github.com/projectdiscovery/chaos-client v0.1.8
go: added github.com/projectdiscovery/cryptoutil v1.0.0
go: added github.com/projectdiscovery/fastdialer v0.0.16-0.20220609092737-7e3c7dcecf16
go: added github.com/projectdiscovery/filekv v0.0.0-20210915124239-3467ef45dd08
go: upgraded github.com/projectdiscovery/fileutil v0.0.0-20220215113056-ba188a0c8abc => v0.0.0-20220705195237-01becc2a8963
go: upgraded github.com/projectdiscovery/folderutil v0.0.0-20220212074351-38f1c1d2fdd4 => v0.0.0-20220215113126-add60a1e8e08
go: upgraded github.com/projectdiscovery/goflags v0.0.8-0.20220411122653-4f7127a41268 => v0.0.8-0.20220610073650-5d31a8c159e3
go: upgraded github.com/projectdiscovery/hmap v0.0.1 => v0.0.2-0.20210917080408-0fd7bd286bfa
go: added github.com/projectdiscovery/httputil v0.0.0-20210816170244-86fd46bc09f5
go: added github.com/projectdiscovery/interactsh v1.0.6
go: upgraded github.com/projectdiscovery/iputil v0.0.0-20210804143329-3a30fcde43f3 => v0.0.0-20220620153941-036d511e4097
go: upgraded github.com/projectdiscovery/mapcidr v0.0.9 => v1.0.0
go: added github.com/projectdiscovery/nuclei-updatecheck-api v0.0.0-20220726130814-981d44a34f84
go: added github.com/projectdiscovery/nuclei/v2 v2.7.5
go: added github.com/projectdiscovery/rawhttp v0.0.8-0.20220526170355-03de6bb78f37
go: upgraded github.com/projectdiscovery/retryabledns v1.0.13-0.20210927160332-db15799e2e4d => v1.0.13
go: upgraded github.com/projectdiscovery/retryablehttp-go v1.0.2 => v1.0.3-0.20220506110515-811d938bd26d
go: added github.com/projectdiscovery/sliceutil v0.0.0-20220511171050-c7d9bc5cadd9
go: upgraded github.com/projectdiscovery/stringsutil v0.0.0-20210830151154-f567170afdd9 => v0.0.0-20220712170325-48c50c332cb4
go: added github.com/projectdiscovery/subfinder/v2 v2.5.2
go: added github.com/projectdiscovery/urlutil v0.0.0-20210805190935-3d83726391c1
go: added github.com/projectdiscovery/wappalyzergo v0.0.52
go: added github.com/projectdiscovery/yamldoc-go v1.0.3-0.20211126104922-00d2c6bb43b6
go: added github.com/rivo/uniseg v0.2.0
go: upgraded github.com/rs/xid v1.3.0 => v1.4.0
go: added github.com/saintfish/chardet v0.0.0-20120816061221-3af4cd4741ca
go: added github.com/segmentio/ksuid v1.0.4
go: added github.com/shirou/gopsutil/v3 v3.22.7
go: added github.com/sijms/go-ora/v2 v2.4.25
go: upgraded github.com/spf13/afero v1.6.0 => v1.8.2
go: upgraded github.com/spf13/cast v1.3.1 => v1.5.0
go: upgraded github.com/spf13/viper v1.8.1 => v1.12.0
go: added github.com/stacktitan/smb v0.0.0-20190531122847-da9a425dceb8
go: added github.com/stoewer/go-strcase v1.2.0
go: upgraded github.com/subosito/gotenv v1.2.0 => v1.3.0
go: added github.com/tj/go-update v2.2.5-0.20200519121640-62b4b798fd68+incompatible
go: added github.com/tklauser/go-sysconf v0.3.10
go: added github.com/tklauser/numcpus v0.4.0
go: added github.com/tomnomnom/linkheader v0.0.0-20180905144013-02ca5825eb80
go: added github.com/trivago/tgo v1.0.7
go: added github.com/ulikunitz/xz v0.5.10
go: added github.com/ulule/deepcopier v0.0.0-20200430083143-45decc6639b6
go: added github.com/valyala/bytebufferpool v1.0.0
go: added github.com/valyala/fasttemplate v1.2.1
go: added github.com/weppos/publicsuffix-go v0.15.1-0.20210928183822-5ee35905bd95
go: added github.com/xanzy/go-gitlab v0.69.0
go: added github.com/xdg-go/pbkdf2 v1.0.0
go: added github.com/xdg-go/scram v1.0.2
go: added github.com/xdg-go/stringprep v1.0.2
go: added github.com/xi2/xz v0.0.0-20171230120015-48954b6210f8
go: added github.com/youmark/pkcs8 v0.0.0-20181117223130-1be2e3e5546d
go: added github.com/ysmood/goob v0.4.0
go: added github.com/ysmood/gson v0.7.1
go: added github.com/ysmood/leakless v0.8.0
go: added github.com/yusufpapurcu/wmi v1.2.2
go: added github.com/zmap/rc2 v0.0.0-20131011165748-24b9757f5521
go: added github.com/zmap/zcrypto v0.0.0-20211005224000-2d0ffdec8a9b
go: upgraded go.etcd.io/bbolt v1.3.3 => v1.3.6
go: upgraded go.mongodb.org/mongo-driver v1.0.4 => v1.9.1
go: upgraded go.uber.org/multierr v1.7.0 => v1.8.0
go: upgraded go.uber.org/zap v1.19.1 => v1.21.0
go: added goftp.io/server/v2 v2.0.0
go: upgraded golang.org/x/net v0.0.0-20220526153639-5463443f8c37 => v0.0.0-20220728211354-c7608f3a8462
go: upgraded golang.org/x/sys v0.0.0-20220520151302-bc2c85ada10a => v0.0.0-20220728004956-3c1f35247d10
go: upgraded google.golang.org/genproto v0.0.0-20210917145530-b395a37504d4 => v0.0.0-20220602131408-e326c6e8e9c8
go: added gopkg.in/corvus-ch/zbase32.v1 v1.0.0
go: upgraded gopkg.in/ini.v1 v1.62.0 => v1.66.4
go: upgraded gorm.io/driver/sqlite v1.3.2 => v1.3.6
go: upgraded gorm.io/gorm v1.23.5 => v1.23.8
go: added moul.io/http2curl v1.0.0
$


Bad margin around code blocks

Here's my extensions list:
    "sphinx.ext.autodoc",
    "sphinx.ext.intersphinx",
    "sphinx.ext.coverage",
    "sphinx.ext.viewcode",
    "sphinx.ext.napoleon",
    "sphinx.ext.autosectionlabel",
    "sphinx_autodoc_typehints",
    "async_doctest",
    "sphinx_panels",   # <--- panels might be impacting this?

I'm not getting any margins around code blocks:

I'm expecting it to look more like this:

Which was achieved by unsetting a margin of 0px from pygrments:

I'm seeing this in firefox for my own project and I don't have the sphinx_panels extension. I see that the theme documentation doesn't look like this. I'll see if I can figure anything else out today.

Update 1: Ok it looks like the theme's site is pulling in basic.css from the default sphinx theme (I think) while generated sites are not.
Future edits coming...

Yep, updating to sphinx 3.3 fixed this for me.

thanks for digging into this @djhoese - any changes that you think need to be made?

I suppose you could require sphinx 3.3?

mmm - that'd probably be extreme (we also allow for Sphinx 2.X as well)

Maybe >2, <3, >=3.3?

I'm not sure I'd be able to find an issue for it but my guess is this is a CSS issue in only a few versions of sphinx. So not technically this theme's problem, but we'd have to find the specific sphinx versions where this exists and exclude those.

Good point, I guess if it were worth going to the effort it'd probably be more of a sphinx !=x.x.x

now that the theme is requiring sphinx > 3.5:
https://github.com/pydata/pydata-sphinx-theme/blob/64d73c3db02b0bcaa1549019282e05ec1e2e753c/pyproject.toml#L21
is the issue solved ?


Support packageManager field in package.json

Fixes #1010

Duplicate of https://github.com/pkgxdev/pkgx/pull/980, I guess.


Don't build for android

arm-linux-androideabi-strip libLuxeApp-v7.so
flow / android specifics { build_type: 'debug',
install_location: 'preferExternal',
libs: { native: { snow: 'snow' } },
sdk_min: 10,
sdk_target: 19,
permissions: [ 'READ_EXTERNAL_STORAGE', 'INTERNET' ],
certificate: '' }
flow / build - android - using ant at /opt/apache-ant/bin/ant
Buildfile: /Users/zerg/Source/HAXE/luxe-samples/5_components/bin/android.build/project/build.xml
BUILD FAILED
/Users/zerg/Source/HAXE/luxe-samples/5_components/bin/android.build/project/build.xml:11: Cannot find /Users/sven/dev/android-sdk/tools/ant/build.xml imported from /Users/zerg/Source/HAXE/luxe-samples/5_components/bin/android.build/project/build.xml
Total time: 0 seconds
flow / build - android - stopping because ant failed to build, exit code 1
real	2m49.125s
user	5m9.719s
sys	0m9.553s
Sergeys-MacBook-Pro:5_components zerg$

As of today ant path and android-sdk path are still hardcoded. Are there any plans to make them configurable? ;)

They are configurable.
See http://snowkit.org/2014/10/29/quick-setup-guides-and-help/#androidspecificsetup

Thanks, I missed that article.
BTW per project configuration is great but a system wide configuration file would be simple to maintain for this sort of things.

I thought I had added the link to the setup guide - but it isn't listed there.
I'll list both, and on the android setup specifics I'll also list the global option.
Glad you got it working then!

Hi. I just tested flow for android build and it says "build.xml" not found.
flow / build - android - using ant at C:/Development/Apache Ant/bin/ant.bat
Buildfile: build.xml does not exist!
Build failed
flow / build - android - stopping because ant failed to build, exit code 1
Hope someone can help me.


feat(LLM): web3hub [LIVE-13124]

✅ Checklist

[x] npx changeset was attached.
[x] Covered by automatic tests.
[x] Impact of the changes:

Discover section only with the FF active

📝 Description
Setup FF for switching between discover and web3hub
Added @react-navigation/native-stack to test a truly native navigation
Added @shopify/flash-list to test the performances
Initial navigation and screens
Setup the integration tests
❓ Context

JIRA or GitHub link: LIVE-13124

🧐 Checklist for the PR Reviewers

The code aligns with the requirements described in the linked JIRA or GitHub issue.
The PR description clearly documents the changes made and explains any technical trade-offs or design decisions.
There are no undocumented trade-offs, technical debt, or maintainability issues.
The PR has been tested thoroughly, and any potential edge cases have been considered and handled.
Any new dependencies have been justified and documented.
Performance considerations have been taken into account. (changes have been profiled or benchmarked if necessary)

@KVNLS Do you think the cache on the CI can be the issue for the podfile.lock ?
https://github.com/LedgerHQ/ledger-live/actions/runs/9776787696/job/26990794818

@KVNLS Do you think the cache on the CI can be the issue for the podfile.lock ? https://github.com/LedgerHQ/ledger-live/actions/runs/9776787696/job/26990794818

You need to make sure that locally you use the correct Ruby & bundler version, then you need to clean your cocoapod cache, if you don't have any change it might come from the cache.
But I already had the issue where it came from my local configuration and I had to clean ~/.cocoapods folder.
To be sure you can run the CI locally, https://ledgerhq.atlassian.net/wiki/spaces/WXP/pages/4658397217/Run+MacOS+Runner+locally+with+Tart


Write examples for MakeTimestamp, Closes #14

I may expect to add the docs on struct definition.
Did you preview the result locally? I remember that docs on trait method impl don't render well.
You should be able to preview locally with:
RUSTDOCFLAGS="--cfg docsrs" cargo +nightly doc --all-features --open

Oh, let me verify. If they are not rendering, i will add them in the struct definition

The examples for the trait impl methods are rendered above the trait definitions. Would this be an issue?


Terminal Glasses

It would be nice if the glasses could be crafted together with any helmet and still remains its functinality
(maybe adding a custom nbt tag to the helmet for tracking glasses) or something like an enchantment

I don't know exactly what you want to put them on, but I have a mod called 'Omni-Things', might work for your purposes.

Not exactly what i wanted i wanted an option to add the Glass-GUI to any helmet so i dont have to give up protection or a set Bonus
after having a brief look over the code it should not be to hard to to it via a NBT-Tag

I'd like to see this too. I also wanted to mention that bilbiocraft does something like this (using an enchantment) for its reading glasses. I'd prefer an NBT tag though, as some armor doesn't like enchantments (and you'd probably need an NBT tag anyways to store the bridge id)

This was already suggested few times, but there are few things that block me from implementing it:

No mechanism for signalling changes in armor slots (though there are few Forge PR, though not yet merged). Without it I have no other way to register new terminals other than scanning every player every tick, which is ugly
Storage. If I keep that in custom NBT structure, there is no guarantee it will stay there - it depends on other mod. Enchantments are usually semi-safe, but I don't like the idea of adding technical functionality via "magic"

But u dont have to scan for the glasses? ....

OP needs to send current state of glasses exact moment player puts it on. Also, there is this event for new user.

Could you have the glasses also be a bauble?

if i could like comments you would get one ...

Somewhat duplicate: https://github.com/OpenMods/OpenPeripheral-Addons/issues/67


Please provide a way to set accept_global_perms=True

Hi!
I just found out that DjangoObjectPermissionsFilter is deprecated in DRF 3.9 and going to be replaced with this module (the code is identical to the one in DRF right now, as far as I can see).
For us, the preferred behaviour is that some users get global model permissions with the intended semantics that they can view (change) all model objects and the ones who are only allowed to view (change) certain model objects get object permissions for the specific model.
Which means we use accept_global_perms=True on all our views. ;)
Currently there's no abstraction for this, so I have to completely copy + paste the whole DjangoObjectPermissionsFilter class to get the intended behaviour:
from rest_framework.filters import BaseFilterBackend

class GlobalObjectPermissionsFilter(BaseFilterBackend):
    """A filter backend that limits results to those where the requesting user
    has read object level permissions.

    Contrary to the assumptions in DjangoObjectPermissionsFilter we
    assume that global model permissions mean that the user can access
    *all* objects (we use accept_global_perms on all views.)

    This means we have to copy / paste DjangoObjectPermissionsFilter
    here, since there's no abstraction to provide for that case.

    """
    def __init__(self):
        assert guardian, 'Using GlobalObjectPermissionsFilter, but django-guardian is not installed'

    perm_format = '%(app_label)s.view_%(model_name)s'

    def filter_queryset(self, request, queryset, view):
        # We want to defer this import until run-time, rather than import-time.
        # See https://github.com/encode/django-rest-framework/issues/4608
        # (Also see #1624 for why we need to make this import explicitly)
        from guardian.shortcuts import get_objects_for_user

        user = request.user
        model_cls = queryset.model
        kwargs = {
            'app_label': model_cls._meta.app_label,
            'model_name': model_cls._meta.model_name
        }
        permission = self.perm_format % kwargs
        return get_objects_for_user(user, permission, queryset,
                                    accept_global_perms=True)

Not sure what would be the best way here, maybe a get_objects_for_user_kwargs class property would simplify things.

Note that for this to work, the permissions class also needs to return True for has_permission in all these cases.

Hi @TauPan. What I'll probably do here is add either a method or a class attribute that can be overridden to customize the keywords arguments.

Perfect! Thanks! ;)


Expired points are not being purged in a timely manner

Describe the bug
Points are being added to a key with a TTL of 10 minutes. After these points have expired, they can no longer be accessed by ID and they do not appear in the results of searches such as WITHIN. These expired points do however appear when SCANing the key they were added to, and can be DELETEd by ID. They also appear to be counted when running STATS on their key.
To Reproduce
Steps to reproduce the behavior:

every 5 seconds ~50 objects are added to key "a"

each object has a TTL of 10 minutes
each object contains a unique ID that is 28 alphanumeric characters long, and includes dashes (-)
each object contains one point and a JSON block of about 15 properties
new objects may replace existing objects if their IDs match, and if so the TTL of 10 minutes is refreshed

objects are added to Tile38 by a Java application through the Lettuce REDIS library (https://github.com/lettuce-io/lettuce-core)

@Command("SET ?0 ?1 EX ?3 OBJECT ?2")
String set(String key, String id, String geoJson, long expirySeconds);

Expected behavior
Points are purged upon expiry and and no longer appear when running SCAN. They no longer contribute to in-memory size.
Logs
Nothing noteworthy in the standard logs, just the periodic AOFSHRINK.
Operating System (please complete the following information):

OS: Linux 3.10.0-1062.el7.x86_64 # 1 SMP Thu Jul 18 20:25:13 UTC 2019 x86_64 GNU/Linux
Version: Docker Hub tile38/tile38:1.12.1 and 1.24.3

Additional context
There are several other processes contacting the Tile38 container periodically:

every 5 minutes, AOFSHRINK is run
every 5 seconds 0-400 GeoJSON objects (arrays of points) are added to a separate key "b" with a TTL of several hours
objects are periodically removed from "b" and given their own unique key containing the associated object from key "b"

the TTL of the object in these keys is the remaining TTL from when they were in key "b"
these unique keys are left to expire, and they do appear to be getting purged correctly

every 5 seconds over 10k points with a 2 hour TTL are added to a separate key "c", the majority replace existing points
points are periodically removed from "c", typically before they have a chance to expire

I was able to reproduce the problem.
Here's a test program that show the issue in action:
https://gist.github.com/tidwall/b0d87956d8488a0b0e902f367babc439

I just pushed a fix.

The fix is working great, thanks for getting this done so quickly!

No problem. Thanks for reporting the issue!


code to train SVM from miRge2.0 paper

I've found miRge very useful--thanks for making it available!
I was wondering if you could point me to the code used to train the (human) SVM that's loaded from the .pkl file in model_predict() (line 103 of preprocessFeatureFiles.py). I'm closely following the approach explained in the miRge2.0 paper, but I'm not getting quite the same accuracy.
Happy to email discuss via email as well.

Hi @juancarlosfdc,
The script for SVM was originally written in miRge2.0 and was used in miRge3.0 by changing the syntax of python script to support version 3.0. I am attaching the script and supporting files for your reference. Please note, the script runs for >12 hours to create the models (you may have to install all the supporting packages required for this program, which you can find in the header part of the script). I hope this helps.
Thank you,
Arun
juancarlosfdc.zip

Hi @arunhpatil,
Thank you--I was able to run this successfully to train the SVM. I have another request: do you think you could share the code that was used to generate all_tissues_mapped_dataset_15_refined_miRGeneDB_total_features_updated.csv in the zip file? Here's what I tried to do, following your description in the paper:

download the sequences from NCBI SRA listed in Table 1 of the 2018 miRge2.0 paper.
modify miRge as follows: Don't pass pdUnmapped into predict_nmir() on line 151. Instead, subset pdMapped to the rna type of interest and pass that in. This generates clusters and the associated features out of known reads, hence labeled examples for training and testing the SVM.
run the modified miRge on the 33 sequences from NCBI SRA.

This produced about 5,000 clusters total, so I know I'm going wrong somewhere--maybe in the command line arguments to miRge, or maybe in the modification of the code. If you could share the code you used that would be great.
Thanks,
Juan Carlos

Hi @arunhpatil,
Sorry to be difficult, I just want to clarify--I cannot find the script that produced all_tissues_mapped_dataset_15_refined_miRGeneDB_total_features_updated.csv in either of these zip files. It sounds like  you don't know where that script is. Is that correct, or am I missing it somehow?

Hi @juancarlosfdc,
My bad, there are several sub-folders and the overall size of the zipped file is >10Gb (from OneDrive). I saw feature detction and the file that is being written to (all_tissues_mapped_dataset_15_refined_miRGeneDB_total_features.csv, but later I realized that the output is a stderr).  I found the script and supporting files in a folder which is 240 Mb (zipped) including intermediate output files. If you want all the files in this directory then share your email address and I will send it over google drive. However, for the time being, I only have retained the script and some input files which I think is necessary and is attached for your reference. In case if you find some more input files are required and are not part of this attachment, let me know I will share those specific files as well. I hope this helps.
Also, note that the output file generated by this script has 10 additional columns which are removed in the updated file (You may consider Pandas drop function to drop those columns). However, the number of rows in both of them remain the same.
$ head -1 all_tissues_mapped_dataset_15_refined_miRGeneDB_total_features.csv | awk -F, ' {print NF}'
84
$ head -1 all_tissues_mapped_dataset_15_refined_miRGeneDB_total_features_updated.csv | awk -F, '{print NF}'
74

juancarlosfdc_PL15.zip
Thank you,
Arun

Hi Arun,
Sorry for my late reply, and thanks for sharing this. Unfortunately, the file that writes  all_tissues_mapped_dataset_15_refined_miRGeneDB_total_features.csv (Refine_build_dataset.py, line 22) is simply reading in all_tissues_mapped_dataset_15_refined_miRGeneDB_tmp.csv on line 128 and rewriting that input.
all_tissues_mapped_dataset_15_refined_miRGeneDB_tmp.csv doesn't appear to be written by any other script in this directory. So, I'm no closer to generating the original data frame, namely all_tissues_mapped_dataset_15_refined_miRGeneDB_total_features.csv. If you can find the code that uses miRge to generate clusters from known annotations and write features associated to each cluster, I think that's what I need.
In the meantime, I've been trying to modify miRge on my own to generate the data frame for myself (and reproduce the SVM performance that depends on it), but the code is challenging and I'm so far unable to generate a data frame that agrees with all_tissues_mapped_dataset_15_refined_miRGeneDB_total_features.csv. I'm happy to discuss via email, and thanks for your patience here.
Best,
Juan Carlos


refactor(structure): Generates new structure with tsdx CLI

This PR applies a refactor to the whole project structure. The following issues influenced the refactor:

Two different references to react on the same components tree #4
Rollup not configured correctly - A lot of unnecessary boilerplate
Unnecessary use of invariants #7

Now all configuration related to babel and rollup is being handled by https://github.com/formium/tsdx

The reason why size workflow is failing - https://github.com/andresz1/size-limit-action/issues/44

lint-staged is not working and should also be fixed here

lint-staged is not working and should also be fixed here

Both lint-staged and husky were being used on two directories at the same git repo and it was leading to a git conflict. Only one instance of both packages should be added to the root of the project.


v2.4.0: Width of placeholder element?

Hi,
Is there any way to adjust the width of placeholder element dynamically?
I realized that on the demo site (v2.1.5?), the placeholder is always taking the width of its content like this:
placeElm.css('width', $uiTreeHelper.width(scope.$element) + 'px');
Do i have to rollback to older version for this effect?
Thanks!

I'm looking for a fix to this as well, is there any way to provide a custom width in the newer version(s)?

@BlakeBrown does the fix work for you? Fixed in v2.7.0.

@Voles
Actually that's the version that breaks it for me, I'm looking to style the placeholder width with CSS and as @muzigao wrote, the line that was introduced: placeElm.css('width', $uiTreeHelper.width(scope.$element) + 'px'); in angular-ui-tree.js forces the placeholder to always take the same width as the content being dragged. In my case, I'm looking to make the placeholder take 100% of the width available rather than being only as large as the content.
I'm thinking of either removing this line (I don't see why it's necessary? I think in most cases users would be okay styling the placeholder with CSS) or providing an option to disable/enable it.
What are your thoughts?

@BlakeBrown the placeholder does neet the height to be set, because it has no content and would otherwise have a height of 0px. However, for the width, the placeholder will take the full width available if it's a block-element. Because the placeholder element get's the angular-ui-tree-placeholder class, it is easy to style using CSS.
The PR which added the 'fix' (#470) doesn't really have an argument on why the width should be set explicitly. There's only a reference to a PR where it has been removed, also without any arguments.
I suggest we remove setting the width for the placeholder using JS. @BlakeBrown are you able to create a PR for this?
/cc @angular-ui-tree/developers

@Voles
Yup of course! See #642
Thanks for getting to me so quickly and with such a high-quality response. That was awesome! :D

Resolved by merging #642


Correct LSEQ/RSEQ INFO specification

Zhongwu
LSEQ and RSEQ had an INFO specification of Number=G, which is one value
per possible genotype. This is not correct with the usage, which I
believe is 1 flanking sequence per variant (Number=1). The incorrect
specification causes errors with downstream tools, like bcftools, that
check this:
Error at 1:10469: wrong number of fields in LSEQ?

Here is a small test case:
https://s3.amazonaws.com/chapmanb/az/bcftools_merge_lseq.tar.gz
Thanks much.

Hi Brad,
The new update of var2vcf*.pl should fix this.  Please let me know if otherwise.
Thanks,
-Zhongwu


Several optimizations to the Steelseries support

List any issues that this PR fixes: fixes # , etc...

This pull request proposes the following changes:

All requests for Steelseries device lighting changes are consolidated into one event, significantly reducing the CPU usage of Steelseries Engine, especially in comparison to the first implementation of QcK Prism support.

Known issues/To do:

I'm not entirely sure why there's a conflict with code from the branch I started out with, but lines 182-243 are the ones that need to be removed to resolve the conflict.


Update to v0.2

Summary

Enter summary here
Test Data and/or Report

Enter info here
Related Issues

Enter related issues here

@mit3ch:  Perhaps you are looking at the main branch, rather than the branch I'm requesting to pull?
The strings "Image_State" and "Instrument_State" do not occur in the new IngestLDD file, except in the change log.  The change log should include an entry for v0.2


Preparing for release 1.4

The release will contain changes to the lifecycle of the shared states.
According to:

https://github.com/betula/use-between/issues/28
https://github.com/betula/use-between/issues/17

Behaviour by default
The default lifecycle will be exactly what users obviously expect.

As long as the shared state has connections it is mounted, when owners are not, it is unmounted.

Infinitely live shred state
And for situations where you want to have an infinitely live shred state, there is a new way to call the useBetween hook
const useDarkModeState = () => {
  const [isDark, setDark] = useState(
    localStorage.getItem("darkMode")
  );

  useEffect(
    () => localStorage.setItem("darkMode", isDark ? "true" : ""),
    [isDark]
  );

  const toggle = useCallback(
    () => setDark((state) => !state),
    [setDark]
  );

  return {
    isDark,
    toggle
  };
};

If you want to have an infinitely live shred state you should use useBetween.forever instead of regular useBetween.
export const useDarkMode = () => useBetween.forever(useDarkModeState);

Resume
Going back to the default behavior where a shread state only exists when someone needs it is a serious performance optimization.
I believe that such behavior would be correct and logical. That this is exactly what users expect!
Have a Great Code!

+1


Make the /opt/data writable by jboss:jboss

Although, the ownership of the mounted volume should be preserved from the host machine.
I.E.
mkdir /tmp/foo && sudo chown nfsnobody:nfsnobody /tmp/foo

and then running..
docker run -v /tmp/foo:/opt/data ${USER}/hawkular-services:0.34.0.Final-SNAPSHOT ls -ld /opt/data

it should return something like
drwxrwxr-x. 2 65534 65534 40 Mar  3 14:46 /opt/data
(65534 ~ nfsnobody)
If the explicit volume mapping with -v switch is not used (or in the docker-compose.yaml file the volume mapping is not specified), then the /opt/data is owned by the root and the jboss user can't write the log files to it. This PR fixes this implicit case when running the container w/o the explicit volume mapping, so that:
docker run ${USER}/hawkular-services:0.34.0.Final-SNAPSHOT /usr/bin/touch /opt/data/foo

..just works.
This is handy for ephemeral use-cases where we don't care about the data.
Note: it's important that the VOLUME directive in the Dockerfile goes after the commands that prepare the directory.

@josejulio could you please look? If I recall, you had similar issue with the docker-compose template, right?

Yes, I had issues with it. I'll take a look.

This is working well for me, thanks!

@pilhuhn could you pls review/merge?

@Jiri-Kremser Did you try this change on Openshift?

@pilhuhn yes, in fact this PR is needed for the persistent template to work properly. Because currently it's broken. I have another PR prepared that depends on this change. I'll open it, soon.


Add cheer command.

Add command to cheer on another player. Command should be of format "$cheer (username)".

Feature added,


Improve the 1.21 port

Fix "Buffer not building" crash
Fix black background texture

See #9 first, only merge this PR if you don't want the modernized backgrounds.


Coding related questions are being filtered

"can I add again a go routine inside worker"
GitHub Copilot :
Sorry, but I can only assist with programming related questions.

We are getting "Sorry, the response was filtered by the Responsible AI Service. Please rephrase your prompt and try again" as a response on that question?!

it can see that i have a TS file open, which is obviously webdev related. How is it so bad ?

We updated the off-topic filter and see a significant drop in false-positive filtering in experiment results.
Closing as fixed, but please don't hesitate to file new issues in case you still run into this.


[build-script] Allow lipo of cross-compiled lldb products

Teach build-script to build lldb's install-distribution target when
installation is required, and make the lipo action invoke lipo when
cross-compiling.
Incidentally this fixes a bash warning about continue being invalid
outside of a loop.

@swift-ci smoke test

The way this is failing seems unrelated to your change
19:06:13 lit.py: /home/buildnode/jenkins/workspace/swift-PR-Linux-smoke-test/branch-master/swift-integration-tests/lit.cfg:209: fatal: repl_swift does not exist!

@swift-ci smoke test linux

Looks like issue with SwiftPM, cc/ @aciidb0mb3r

That's just output from a test run (which succeeded). @benlangmuir can you fix SourceKit-LSP to not emit that? Here's the real error:
lit.py: /home/buildnode/jenkins/workspace/swift-PR-Linux-smoke-test/branch-master/swift-integration-tests/lit.cfg:209: fatal: repl_swift does not exist!

can you fix SourceKit-LSP to not emit that?

Is there a way for swift-test to show the output from a test only when it fails?

Is there a way for swift-test to show the output from a test only when it fails?

swift test --parallel does that I think.

@swift-ci smoke test linux

The dispatch_timer_bit31 test failed.

@swift-ci smoke test linux

@swift-ci smoke test linux

Rebased. The last few linux PR tests still hit the let pack issue. Let's try again, maybe there's a slim chance the rebase will help.

@swift-ci smoke test

@swift-ci smoke test linux

@swift-ci clean smoke test linux

Trying again now that d270638 is in.
@swift-ci smoke test linux


Add esbuild steps with metafile output to README

I tried this repository and stumbled upon the need to output a metafile in the esbuild configuration.
I think it would be helpful to include this in the README.

I think this part in README describes that.
Do you think it is not enough?

Oh.
Sorry, I am using esbuild v0.19 (< v0.20), so I skipped this sentence.
I need not to skip, but I didn't notice.

For example, how about splitting the usages steps in the README?

Configure esbuild to output a metafile.

CLI version
JS version

Write the GitHub Actions.

The CLI version is easier than the JS version, and I've also split the esbuild configuration steps.
What do you think?

Added CLI version example, which I was not aware of, to README in https://github.com/exoego/esbuild-bundle-analyzer/pull/29

Thanks to update README🙌


[Android] Disable/Enable Logs correctly

CORRECTLY:
log_level = 2
log_file = 'dnscrypt-proxy.log'

or
# log_level = 2
# log_file = 'dnscrypt-proxy.log'

WRONG WAY:
log_level = 2
# log_file = 'dnscrypt-proxy.log'

Background:
You have to Disable/Enable Logs together with supported parameters or this may hadly break the thigs: Network Wi-Fi connections (on Android) will be broken.
This little difference can make a BIG troubles for you.
I suppose that I'm kinda an experianced user, but this little thing accidentlally caused a big @ss pain (:
Proposal:
Make all log_file or file parameters - as "General", special (supported) parameters - as "Secondary" (log_level , format). Better for PC (and other OS) also.
If "General" logging disabled for the sertain section, then other "Secondary" parameters should have no influence.
This should prevent dnscrypt-proxy from malfunction (at least on Android).

2 is the default log level, so there are no differences between
log_level=2
and
# log_level=2

You didn't understand. That because so hard to find this bug.
All relative parameters have to be commented all together, or not commented all together. That's OK.
If one is commented while other one is not, then dnscrypt-proxy stops working on Android.
See my example.

Maybe because it can't print to screen (or whatever the standard output is). This depends on how you start it.
You can use /dev/null as the file name, or set use_syslog = true if that works on Android.

The most strange thing that I want set NO OUTPUT, but I can't.
Turning OFF/ON logs for the rules seems OK, except APP output.
If I disabling an app output, then it won't work...

This depends on how you start it.

Well, exactly for starting dnscrypt-proxy binary I'm using oldschool init.d. But this is only a small part of the opera.
I'm using a complex method to get dnscrypt-proxy working. There is a lot of big and small nuances. But method is pretty simple, you just have to know exactly "how to" and "why" to do this or that.
It's reliable and it works on different phones/OS (MIUI & RR tested). Sadly, running dnscrypt-proxy stable "from the box" is impossble. I'm using 3-rd party app also to help running it in a predictable way. Because I know why all efforts of using custom IPTABLE commands will fail, early or later.
I'm understand sharing this experience in according thread #41 would help people a lot. Or creating a Wiki, may be... My methods is also around things has been already discussed in thread #41, but no one described the clear steps how to win this competition step by step.
Otherwise, first, would be nice to have a clear idea of present (suddenly appeared and very strange) issue.

You can use /dev/null as the file name

Sorry, I don't know what is it at all...

use_syslog = true

I know this works on Windows, but only with log file-output disabled. I can't imagine if this can work on Android. Even if it can (doubting), then where to find a log, output or smth... And I'm satisfied with log files if I want them.


ZoomIn and ZoomOut not working

I am using the original library for one year but suddenly zoom in and zoom out not working now. I have tried your build also but no luck. Please help me to resolve this issue. My react version is 17.0.2

I will need a bit more information to able to help. Can you give me step by step instructions about what you do and then the error that you get? And if you don't get an error, then a line detailing what you expected and another describing what is happening instead.


Localization support

Changes
Adds support for localization using the i18next library.
Dependencies

i18next Localization library
i18next-fs-backend Loading localization files
i18next-resources-for-ts Typesafety for localization
Didn't commit package-lock because that should only be generated by the maintainer.

Todo

[X] Automatically apply Discord native localization to slash commands Done using localizeCommand on the SlashCommandBuilder
[X] Full typesafety for using the localization function Need to npm run toc on every new key added for types to generate
[X] Add support for client versus server side language preference Using useServerTranslator/useUserTranslator
[X] Move all free-standing strings to the translation file
[X] Merge similar/reused strings
[ ] Finish TODOs (localizing option names, adding subcommands)
[ ] Test using different server and client settings

@tacheometry this is looking great! Will look more at it after work.
I see this is a draft pull request, so let me know when you are ready to merge and need me to generate package-lock.json. I'll also do some proper testing then.

Tested using different client and server settings. These are being respected by localization util and works as expected.
Added localization file in norwegian to have data to test for non-fallback language. This is fully translated.
This works well, so merging this in now. We can work on support for translation of subcommand options in another PR. This is only required for the /remove subcommands to display in non-fallback language.


Mxn fixdraweroverflow master

Hello!I found nineoldandroids have been dependenced in your module.I include the following dependency in my build.gradle file. But my project use the same nineoldandroids jars and it causes quote repeat.I couldn't solve the problem.So how can I do?Thank you!

you can copy my code in module to your application except nineoldandroids.
And delete my module.


RouteMagic redirection giving 404 instead of redirecting

Hello,
I have rewritten an old WebForms site in MVC5 (Visual Studio 2013 Ultimate Update 4, Windows 7 64-bit), and want to add permanent redirection from the old URLs to the new. Reading your blog post about RouteMagic (http://haacked.com/archive/2011/02/02/redirecting-routes-to-maintain-persistent-urls.aspx/), I thought this would do the trick.
I added the NuGet package, and then added the following to the end of the RegisterRoutes() method in the RouteConfig class...
routes.Redirect(r => r.MapRoute("old", "Default.aspx")).To(routes.MapRoute("new", "Home"));
However, if I try to access http://localhost:8109/Default.aspx, I just get a 404 in the browser. It doesn't redirect at all.
What am I doing wrong? I reproduced the problem on a brand new, out-of-the box MVC project. I just added your package and the one line of code shown above.
Thanks for any help you can give.

Did you confirm that there is no Default.aspx on disk?

Yup. This was a brand new MVC project.

My guess is that another route is matching the request first so you're not running into the redirect route. In the default MVC project, the default route matches everything. So the redirect route needs to go first.
The following approach works in a brand new MVC 5 project.
using System.Web.Mvc;
using System.Web.Routing;
using RouteMagic;

namespace RouteDemo
{
    public class RouteConfig
    {
        public static void RegisterRoutes(RouteCollection routes)
        {
            routes.IgnoreRoute("{resource}.axd/{*pathInfo}");

            routes.Redirect(r => r.MapRoute("old", "Default.aspx"))
                .To(routes.MapRoute("new", "Home/{action}", new { controller = "Home", action = "Index" }));

            routes.MapRoute(
                name: "Default",
                url: "{controller}/{action}/{id}",
                defaults: new { controller = "Home", action = "Index", id = UrlParameter.Optional }
            );
        }
    }
}

For future reference, you can install the RouteDebugger package and it'll show you which routes are matching.
Install-Package RouteDebugger
It's useful for figuring out these types of routing problems.

Thanks for the info. I'll have a look. I don't remember where I put the default route, so it could be that it was was before the redirect route.
Thanks also for the info about the package. I was wondering how you are supposed to debug routing!


can't use DropSource

Always Warning:Failed Context Types: Required context dragDropManager was not specified in DragSource(Page). Check the render method of Tab.
Here is a part of my code, I have 4 fixed pages and a resort list .... I want to dropresort a list ..I don't konw how to fix the worng things,need some help ... This all in one page application .

You are wrapping your root component with DragDropContext and then not using it.
Instead of:
ReactDOM.render(
  <EditPage />,
  document.getElementById('preview')
)

module.export = DragDropContext(HTML5Backend)(EditPage)

you want something like
// EditPage.js
module.exports = DragDropContext(HTML5Backend)(EditPage)

// index.js
ReactDOM.render(
  <EditPage />,
  document.getElementById('preview')
)

or, alternatively,
EditPage = DragDropContext(HTML5Backend)(EditPage)

ReactDOM.render(
  <EditPage />,
  document.getElementById('preview')
)

The idea is that whatever you render should already be wrapped in DragDropContext. Just exporting it from the same model where you call ReactDOM.render has no effect because this export isn’t used anywhere.

ok，I got it ,thank you very much

code`

ReactDom.render();

`EditPage = DragDropContext(HTML5Backend)(EditPage)
ReactDOM.render(
,
document.getElementById('preview')
)`

`EditPage = DragDropContext(HTML5Backend)(EditPage)
ReactDOM.render(
,
document.getElementById('preview')
)`

EditPage = DragDropContext(HTML5Backend)(EditPage)

function fancyAlert(arg) {
  if(arg) {
    $.facebox({div:'#foo'})
  }
}


Fails to compile without float support

Compiling with PRINTF_SUPPORT_DECIMAL_SPECIFIERS = 0 and PRINTF_SUPPORT_EXPONENTIAL_SPECIFIERS = 0 fails because the following declarations are within the #if (PRINTF_SUPPORT_DECIMAL_SPECIFIERS || PRINTF_SUPPORT_EXPONENTIAL_SPECIFIERS) block but shouldn't be.
printf_unsigned_value_t
printf_signed_value_t
numeric_base_t
printf_size_t
PRINTF_MAX_POSSIBLE_BUFFER_SIZE

I found this when working with v6.0.0 but I haven't traced back to see when the problem was introduced.

Thanks for reporting this. I should really try to get the GitHub Actions workflow to build with all possible combinations of the ON/OFF parameters.
Anyway, I rebased a bunch of commits and this is now fixed. Will soon post a new release candidate for v6.0.0


Closes #423 | Add/Update Dataloader malaysia_ai_hansard

Title: Closes #423 | Add/Update Dataloader malaysia_ai_hansard
First line PR Message:
Closes #423
Checkbox

[x] Confirm that this PR is linked to the dataset issue.
[x] Create the dataloader script seacrowd/sea_datasets/{my_dataset}/{my_dataset}.py (please use only lowercase and underscore for dataset folder naming, as mentioned in dataset issue) and its __init__.py within {my_dataset} folder.
[x] Provide values for the _CITATION, _DATASETNAME, _DESCRIPTION, _HOMEPAGE, _LICENSE, _LOCAL, _URLs, _SUPPORTED_TASKS, _SOURCE_VERSION, and _SEACROWD_VERSION variables.
[x] Implement _info(), _split_generators() and _generate_examples() in dataloader script.
[x] Make sure that the BUILDER_CONFIGS class attribute is a list with at least one SEACrowdConfig for the source schema and one for a seacrowd schema.
[x] Confirm dataloader script works with datasets.load_dataset function.
[x] Confirm that your dataloader script passes the test suite run with python -m tests.test_seacrowd seacrowd/sea_datasets/<my_dataset>/<my_dataset>.py or python -m tests.test_seacrowd seacrowd/sea_datasets/<my_dataset>/<my_dataset>.py --subset_id {subset_name_without_source_or_seacrowd_suffix}.
[-] If my dataset is local, I have provided an output of the unit-tests in the PR (please copy paste). This is OPTIONAL for public datasets, as we can test these without access to the data files.

A friendly reminder for @BinWang28 to address the suggestions and for @faridlazuarda to review.

Thanks, will do this week

A friendly reminder for @BinWang28 to address the suggestions. 🙏

thanks, updated

Thanks @BinWang28! All suggestions have been addressed.
PS: I'm merging this PR without waiting for @tellarin's approval due to @tellarin's lack of response.


fix(locales/de): languageName

Changes proposed in this pull request:

languageName for german should be Deutsch instead of Deutsche

sources for non native speakers: 1, 2, 3
cc @HospitalRun/core-maintainers

Thanks @FalkF for the PR.


Docker Version > 19 Support

Hi all,
thanks again for the very interesting work!
Why is the support limited to Docker versions below 19? Is there any roadmap to support Docker > 19?
Best,
Samed

It is due to the version compatibility issue. We expect to solve this issue in a few months. Please check back soon.

So, does the current Kubeshare version support docker> 19.0?  (April 2, 2021)

yes, we support it.
In fact,
you just need to enable the nvidia runtime as your default runtime on your node.
Runtimes: nvidia runc
Default Runtime: nvidia

Okay, thank you, but I'm still stuck in issue #9, could you help me answer it?


Add missing CHANGES.md entries

Checklist

[x] documentation is added or updated

This pull request is ready to merge


expose seed keyword in HOD mock making for reproducible mocks

For testing purposes, it would be useful if the random seed could be set from the populate_mock function of HodModelFactory .
It looks like the mc_occupation_* functions take a seed keyword, but I do not see an obvious way of passing in a value when populating mocks (outside of a hack-ish wrapping of those functions).

@aphearin -- I've put together a quick hack that seems to do the trick in my specific case that just wraps the mc_occupation_centrals and mc_occupation_satellites functions as well as the mc_pos, mc_radial_velocity, mc_solid_sphere functions of the satellites profile, passing in the seed keyword. I'm happy to use that in the short term, so whatever timeline you prefer will work for me. Once you have something I'll happily help test out the feature.

Ok, good to know you were able to write a workaround.
This is sort of a brain burp, but for this purpose there is a particularly handy context manager within Astropy: from astropy.utils.misc import NumpyRNGContext. You can see example usage of it all over my test suite (e.g, halotools/mock_observables/two_point_clustering/tests/test_wp.py). Rather than have the Numpy seed be a fully global variable, this context manager sets the seed within its namespace and then resets the value to be whatever it was outside of the context. You should totally ignore this if you don't find it useful, just thought I'd mention it. That's the way I'll modify the source code when the time comes.  I'll try and properly implement this feature soon, keeping this issue open until I do.

This should be resolved by #584. Please re-open if this is not what you had in mind, @nickhand.


Random object gets printed to the console and python freezes

The problem
Console randomly prints an object
The object in question:
{"r": 23, "c": "jsi", "p": 1, "action": "call", "ffid": 11, "key": "", "args": [12, {"ffid": 34}, {"ffid": 35}]}
This object can very each run, sometimes the problem doesn't even happen!
After this is printed python gets held up and after 100000ms pythonia throws an error:
node:internal/event_target:1011
 process.nextTick(() => { throw err; });
                          ^
Error: Attempt to access '__call__' failed. Python didn't respond in time (100000ms), look above for any Python errors. If no errors, the API call hung.
   at C:\Users\AirplaneGobrr\Documents\GitHub\ai-gen\node_modules\.pnpm\pythonia@1.0.1_ws@7.5.9\node_modules\pythonia\src\pythonia\Bridge.js:248:13
   at waitFor (C:\Users\AirplaneGobrr\Documents\GitHub\ai-gen\node_modules\.pnpm\pythonia@1.0.1_ws@7.5.9\node_modules\pythonia\src\pythonia\Bridge.js:123:26)
   at async Bridge.call (C:\Users\AirplaneGobrr\Documents\GitHub\ai-gen\node_modules\.pnpm\pythonia@1.0.1_ws@7.5.9\node_modules\pythonia\src\pythonia\Bridge.js:233:18)
   at async t2i (C:\Users\AirplaneGobrr\Documents\GitHub\ai-gen\aiGen\worker.js:81:29)
Emitted 'error' event on Worker instance at:
   at Worker.[kOnErrorMessage] (node:internal/worker:298:10)
   at Worker.[kOnMessage] (node:internal/worker:309:37)
   at MessagePort.<anonymous> (node:internal/worker:205:57)
   at MessagePort.[nodejs.internal.kHybridDispatch] (node:internal/event_target:736:20)
   at MessagePort.exports.emitMessage (node:internal/per_context/messageport:23:28)

I think maybe this issue might also be related to #68 ?
I tried to debug it on my own bug have no clue what the problem is or where to even begin looking
Code
Bit of my code:
var images = await (await main.__call__$(prompt, {
    negative_prompt: negPrompt,
    callback: progress,
    guidance_scale: scale,
    num_inference_steps: steps,
    num_images_per_prompt: images,
    height: height,
    width: width
})).images

"Main" is from a StableDiffusionPipeline pretrained pipe AKA:
const pipe = await dif.StableDiffusionPipeline.from_pretrained$(moduleToLoad, { torch_dtype: await torch.float16 })
const main = await pipe.to("cuda")

Dif being the diffusers and torch being torch

after doing some debug it looks like the callback: progress is causing the issue, Fix is to remove it but it would be nice to have the callback!

@AirplanegoBrr

after doing some debug it looks like the callback: progress is causing the issue, Fix is to remove it but it would be nice to have the callback!

if it's the same as #68, then putting a reference to your callback somewhere in Python should help, as then it won't be removed by Python's garbage collector


Version requirements?

Hi there I have a filebeat 6.5.1 and our elastic stack is also at 6.5.1.
When I set up the filebeat it does say it finds 1 input (dedicated postfix server), but I don't see anything arriving on the logstash. It does have access, as I can telnet to the port from the filebeat server, so I was wondering if the syntax used in the configs.d is only available for 7.x filebeats?

Hello, @fribse
I had the same issue. FIxed it with following 51-filter-postfix-aggregate.conf:
filter {
  if [program] == "postfix/qmgr" and [postfix_from] {
    aggregate {
      task_id => "%{postfix_queueid}"
      code => "
        map['postfix_from'] = event.get('postfix_from')
        map['postfix_size'] = event.get('postfix_size')
        map['postfix_nrcpt'] = event.get('postfix_nrcpt')
      "
    }
  } else if [program] == "postfix/smtp" {
    aggregate {
      task_id => "%{postfix_queueid}"
      code => "
       map.each do |key, value|
         event.set(key, value)
       end
     "
    }
  }
  if [program] == "postfix/smtp" and [postfix_tls_version] {
     drop {}
  }
  if [postfix] and [program] != "postfix/smtp" {
    drop {}
  }
}

Working properly on ELK 6 and 7
Thank you

I was trying with ELK 6.5 and it is asking for .ndjson files. Would it be possible for you to share the UI dashboard .json and configuration files that work with ELK 6 and 7?


Fix redirecting WslLaunch's output to a file

Passing a real file descriptor to WslLaunch does not write to a file for some reason, so I have to stick an intermediate pipe in there. This pull request does two things that should probably been two separate PR, but became too intertwined:

Refactors Cmd so that it more closely resembles the stdlib. See commit
Brought (*distro).Cmd closer to the standard library for more details.
Adds tests that fail, proving that we do not write to file
Adds the intermediate pipe, making the tests pass.

WSL-401

Forced pushed to rebase to main. Also used the oportunity to strategically squash commits so that they make sense.


Q: ETA for 6.0?

It seems that a 6.0 release was planned (with nullable reference types). Is there an ETA for it?

Yes, there is a branch with what could be V6. The only change is that nullable-reference types are supported. The problem is that it introduces a lot of breaking changes to the API. So, up to now, I was not convinced that it should be released. You are the first to ask for it :-)

@ursenzler No need to hurry, especially if you don't like the breaking changes for 6.0 😉 .


glfw char event -- deprecated in 3.3 and also not repeating some keys now

e.g., a repeats, but d does not!
to use key events, need a map from keycode to rune.  pita.

this issue discusses many of the issues: https://github.com/glfw/glfw/issues/1140  -- unfortunately would need to get a forked version as they haven't merged into main which still has separate callbacks and doesn't really handle the use-cases.  Might need to just go back to the original shiny code.  Ugh.

at least d repeats now in 3.3.  will look into the fork at some point if std glfw doesn't get a better solution in the meantime..

it looks like things are generally working pretty well -- the alt versions of keys now come through via the deprecated Chord version or whatever it is called. if they actually get rid of that then we'll be in trouble but for now it seems fine.

There are still issues with modifiers not being properly attached to chord events in rapid typing scenarios, and some noticeable lagginess..  but overall working ok most of the time.  this would be something we could take on in a "do our own glfw" in goosi case.


Allow additional service configuration for MysqlCluster

This pull request adds capability to set ServiceSpec for MysqlCluster.

[x] I've made sure the Changelog.md will remain up-to-date after this PR is merged.

Or we can create some exporter services instead of making changes to the original services.

WDYT, cc @calind

The MySQLCluster controller/resource should not be responsible for creating any additional services (as is the case of the k8s StatefulSet controller for example). The extra services should be created by the cluster operator.
The place where extra services are created might be within the mysql-cluster helm chart.

The MySQLCluster controller/resource should not be responsible for creating any additional services (as is the case of the k8s StatefulSet controller for example). The extra services should be created by the cluster operator.
The place where extra services are created might be within the mysql-cluster helm chart.

Thank you for your reply, but could you elaborate more on this?
This pull request does not add any additional services. Instead, it allows changing the type of existing ones.

The MySQLCluster controller/resource should not be responsible for creating any additional services (as is the case of the k8s StatefulSet controller for example). The extra services should be created by the cluster operator.
The place where extra services are created might be within the mysql-cluster helm chart.

Thank you for your reply, but could you elaborate more on this? This pull request does not add any additional services. Instead, it allows changing the type of existing ones.

You can go in the mysql-cluster helm chart and add two additional services as extensions, and with the extensibility of the chart, a new loadbalancer can be added without change the code

I see that. The only issue with this approach is that I am forced to use the Helm chart for this. This will not work when a cluster is created using a plain yaml file or kustomize.

You can go in the mysql-cluster helm chart and add two additional services as extensions, and with the extensibility of the chart, a new loadbalancer can be added without change the code

I see that. The only issue with this approach is that I am forced to use the Helm chart for creating a cluster. Services will not be created when a cluster is created using a plain yaml file or kustomize.

right

right

That's the point of my PR. ;)

You can go in the mysql-cluster helm chart and add two additional services as extensions, and with the extensibility of the chart, a new loadbalancer can be added without change the code

I see that. The only issue with this approach is that I am forced to use the Helm chart for creating a cluster. Services will not be created when a cluster is created using a plain yaml file or kustomize.

It's probably about design, we need to be careful about extending mysqlcluster in order to keep it easy to use, maybe we can start with helm support? WDYT @ynnt

I do agree that this PR changes API layout a little bit (though, I do not think it changes UX or introduces any significant changes to the overall application design).
Unfortunately, the Helm chart approach simply does not work for my use case (creating mysql clusters programmatically). :(
So, feel free to close the PR if you believe it adds unnecessary complexity, I will just stick to my fork.

WDYT @calind

@cndoit18 @calind Any plans to merge it?


fix(Wrapper): Fix Vue warning 'Non-function value encountered'

Description
When using a Wrapper component the browser log was showing a number of warnings when mounting and rendering Wrapper components.
[Vue warn]: Non-function value encountered for default slot. Prefer function slots for better performance.

See repro here:
https://stackblitz.com/edit/nuxt-starter-wdpsex
Open Dev Tools to see the warnings in the browser console
Additional context
This PR aims to fix that by using () => function slots eliminating the warning

What is the purpose of this pull request?

[x] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[ ] If it's a new feature, provide a convincing reason to add it. Ideally, you should open a suggestion issue first and have it approved before working on it.
[ ] Read the Contributing Guidelines.
[ ] Read the Pull Request Guidelines and follow the Commit Convention.
[ ] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[ ] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

@Akryum : I'm not sure - is there anything I can add to this PR? LMK!


doc(site): fix command

According to what the command setups, it should be capture and not config.

Thanks


theme config

👷 Deploy Preview for adoring-leavitt-e31a11 processing.
🔨 Explore the source changes: 076b315d794c7d46b828cfdc89e2883fdd0615b7
🔍 Inspect the deploy log: https://app.netlify.com/sites/adoring-leavitt-e31a11/deploys/6226666e80f9b500078d58f8


Fix SIGSEGV when reading from a non-existent file

When a tool (tested with spirv-dis and spirv-as) runs on a file that
does not exist, it notifies the user and tries to close the stream that
was never successfully opened.

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

This looks like a reasonable solution to me, could you sign the CLA so that it can be merged?

Signed.


Add Support for Vibrancy theme

Thank you for amazing work. Is it possible to install https://github.com/EYHN/vscode-vibrancy along with apc-ecxtension. I would be really cool. Thank you.

that is a question for them https://github.com/illixion/vscode-vibrancy-continued
i can modify their files, but it can lead to unexpected behaviors
maybe when I have time I will implement something similar

bottom line there is no need for other extensions
it turns out that this was possible all along, it just needed a little tweaking
see https://github.com/drcika/apc-extension/blob/production/demo/vibrancy.settings.json
settings are not the same for all OS
OS specific
https://www.electronjs.org/docs/latest/api/browser-window#new-browserwindowoptions

Hi,
what is your OSX version?
Except for the main opacity setting (which includes text), It doesn't seems to work with my osx 12.6.2 setup.
I've tried multiple vibrancy settings, ultra-dark seems deprecated on osx.

13.4 (22F66)
yes some settings are deprecated but still work

strange situation, some settings work some don't, some of them produce the same results.
this work
sidebar, header , hud, fullscreen-ui, light, dark, medium-light, and ultra-dark

No matter what I do, I cannot get the vibrancy effect

  "apc.electron": {
    "backgroundColor": "#00000000",
    "vibrancy": "under-window",
},


Layout weekly not correct on the iPad

(Required) Version Number: 8.0.2
I used the JTAppleCalendar for my iPhone app. I need a weekly view, nothing more.
Now that I'm developing the iPad version of the same app, I'm taking advantage of the same class I have on the iPhone with the same features, just enhancing the layout with a second storyboard.
I simply reproduce what I have on Main.storyboard on the Main_iPad.storyboard version, reading the same classes with the same functions but arranging the objects differently.
If the same weekly collection in the iPhone storyboard works correctly (I attach image), if I set the contraist of its size on the iPad storyboard, it does not behave correctly.
If I change orientation, even worse.
I just want it to show 7 days and for the cells to change their width to fit the width of the superview, like a simple collection.

Steps To Reproduce
Expected Behavior
Additional Context

is your calendar fully setup with constraints with zero errors?

Yes, no errors. On iPhone works well, on iPad I don't know why there is this problem.
If I don't modify the weight of the collection, and I maintain the same dimension of iPhone collection, it works well.

hmm.. you have to give me a minimal project example that replicates this issue.
emphasis on minimal.

UPDATE: Now I have some warnings!

OK.

What xcode version are you using?
What about the last error, is it still there?

Xcode Version 12.5.1 (12E507)
Yes, I can't correct this issue. There is another problem, when I change the orientation, the collection view update the layout, but the cell inside not


Bonnie v2.1 to master

This is to merge v2.1 work into master.  Branch bonnie-v2.1_on_master is a rebase of bonnie-v2.1 on master.
Pull requests into CQL QDM Patient API require the following. Submitter and reviewer should :white_check_mark: when done. For items that are not-applicable, note it's not-applicable ("N/A") and :white_check_mark:.
Submitter:

[x] This pull request describes why these changes were made.
[x] This PR is into the correct branch.
[x] Code diff has been done and been reviewed (it does not contain: additional white space, not applicable code changes, debug statements, etc.)
[x] Tests have been run locally and pass (remember to update Gemfile when applicable)
[x] Code coverage has not gone down and all code touched or added is covered.

branch
coverage

master

bonnie-v2.1_on_master

Reviewer 1: @mayerm94
Name:

[x] Branch bonnie-v2.1_on_master looks like a good rebase of bonnie-v2.1 on master
[x] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[x] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

Reviewer 2:
Name:

[ ] Branch bonnie-v2.1_on_master looks like a good rebase of bonnie-v2.1 on master
[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

Note to reviewers: I ran a regression test using bonnie branch bonnie-v2.1_gemfile_updates without and with this rebase branch. Regression test came back clean.


use kubernetes default schedule policies

we know the default scheduler has several schedule policies, for example: CheckNodeConditionPredicate,PodFitsHost, PodToleratesNodeTaints and so on. can kube-batch use this schedule policies? thanks

Yes, we already import those predicate/priority in kube-batch: https://github.com/kubernetes-sigs/kube-batch/blob/master/pkg/scheduler/plugins/predicates/predicates.go ; if any other requirements, please let me know :)

@k82cn  thks, i only find predicate policy, is there any method for adding priority schedule policy?

please find priorities here: https://github.com/kubernetes-sigs/kube-batch/blob/master/pkg/scheduler/plugins/nodeorder/nodeorder.go :) If any new requirements, please let me know :)

got it,thank you very much


Allow for reading/writing object meta data - Implements #24

This PR implements the functionality to read and write user defined object meta data.
Example usage:
let metaData = ["finalized" : "yes"]
amazonS3Manager.putObject(fileURL, destinationPath: fileURL.lastPathComponent!,metaData: metaData).response {
	request, response, data, error in
    print(request)
    print(response)
    print(error)
}

amazonS3Manager.headObject(fileURL.lastPathComponent!).responseS3Object {
	(response: Response<S3MetaDataResult, NSError>) in
    if let metaData = response.result.value?.metaData {
        for objectMetaData in metaData {
            print(objectMetaData)
        }
    }
}

This seems to be heavily linked to #23. Once we have finalized the changes there, we will try merging these changes into that branch. Thanks

These changes have been merged into develop. Thank you @sbhklr


Metadata retrieval not working

This is caused by the switch to HTTPS for bibdata: see  https://github.com/pulibrary/pul_metadata_services/pull/10


Is Pagefactory going to be deprecated in near future?

appium/appium#10906

PageFactory is deprecated in the main Selenium repository. It is still a going concern in the DotNetSeleniumExtras repository, though the repo is looking for a new owner.

PageFactory still exists and is only available for .NetFramework.


[ISSUE-369] Don't throw exception if blocks are corrupted but have multi replicas

What changes were proposed in this pull request?

Don't throw exception if blocks are corrupted but have multi replicas
Why are the changes needed?

If some blocks of one replica are corrupted, maybe other replicas are not corrupted, so exception should not be thrown here if blocks have multi replicas. #369
Does this PR introduce any user-facing change?

No
How was this patch tested?

UT

LGTM, just some nits.

Codecov Report

Merging #374 (d1339d4) into master (ad51341) will increase coverage by 1.19%.
The diff coverage is 85.00%.

@@             Coverage Diff              @@
##             master     #374      +/-   ##
============================================
+ Coverage     58.01%   59.21%   +1.19%
- Complexity     1361     1454      +93
============================================
  Files           171      180       +9
  Lines          9006     9611     +605
  Branches        787      832      +45
============================================
+ Hits           5225     5691     +466
- Misses         3449     3573     +124
- Partials        332      347      +15

Impacted Files
Coverage Δ

...che/uniffle/client/impl/ShuffleReadClientImpl.java
88.46% <85.00%> (-1.23%)
:arrow_down:

...pache/uniffle/server/ShuffleServerGrpcService.java
0.81% <0.00%> (-0.02%)
:arrow_down:

.../org/apache/uniffle/server/ShuffleTaskManager.java
77.22% <0.00%> (ø)

...e/uniffle/client/factory/ShuffleClientFactory.java
0.00% <0.00%> (ø)

...uniffle/storage/factory/ShuffleHandlerFactory.java
0.00% <0.00%> (ø)

...client/request/CreateShuffleReadClientRequest.java
0.00% <0.00%> (ø)

.../storage/handler/impl/MemoryClientReadHandler.java
0.00% <0.00%> (ø)

...orage/request/CreateShuffleReadHandlerRequest.java
0.00% <0.00%> (ø)

.../org/apache/spark/shuffle/writer/WriterBuffer.java
93.18% <0.00%> (ø)

... and 11 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


http-server runing on project root folder path without any reasons

Environment Versions

Windows 11
Node version: v18.16.1
http-server version: v14.1.1

Steps to reproduce

I have a project with a dist folder. When i open a terminal in that folder and run http-server, it use the project root folder instead of the folder where i opened the terminal.
Expected result
http-server root path should use the path of the folder i opened the terminal
Actual result
Http-server root path is using the project root path.
Other information

I encountered the same problem on linux. And the reason for me is the permission. After I added 777 permission recursively to the dist folder, It worked by running the http-server under the dist directory.

Is this going to be resolved?  From what I understand here, and from my own issues of launching http-server and providing a path where it says [path] in the documentation, and it fails to load the directory I specify.
I like the compactness of this tool as I learn front end development, but this is a major bug, if it is one.

Still happening for me on version 1.0.1

Marking this as sus - I'm not able to reproduce this behavior so a minimal reproduction would be helpful.


Ability to specify the preferred namespace in a response

OSDM supports the powerful mechanism of namespaces which the OSDM client can provide in requests.
However it is not possible to request the preferred namespace of responses. For example if an OSDM provider has a default namespace like "x_mynamespace" it will most likely return the stations and operator in the default namespace. But what if the OSDM client wants to have the response in a different namespace?
We, as Sqills, have support multiple namespaces which are fully configurable. However, in the responses where no namespace is provided in the request, the default is returned. And this default doesn't not have to be the UIC (that might not be configured at all).
Also, it is not guaranteed that an OSDM client always wants the response to contain the same namespaces. This could be very much depending on the retailer or UI client connecting to a OSDM distributor. E.g. a Swedish retailer uses the x_swe namespace but an international OSDM client might prefer uic.
By introducing a "namespace" request input we can:

let the client decide what its preferred namespace is (for that specific request)
the OSDM provider can return the proper namespace (if valid & supported)
This parameter could be a query param or custom header like e.g.  "x_namespace".

We do have a Requestor header that could be utalized for this (and that would make it compatible wil all older versions) but:

the content of it is not standardised
the Requestor is for the who makes the request, not what it wants

is this linked to the osdm media type that is requested at IANA?

Not directly. As input we use namespaces in various areas like place refs. We have customers using their own codes and other supporting multiples.
During an offers request a code can be provided in the payload but when fetching a booking it is up to the OSDM provider to decide to return which. And that can be different then the OSDM client expects or that the OSDM client wants to have a different namespace for that specific request.

I get that, of an alliance of OSDM-capable systems want to talk with a prefered ID namespace, they need to make sure that UIC or other namespaces don't get used. It also helps to switch behavior if somebody from outside wants to call the API.
Question - how would that work if multiple preferred namespaces need to be requested. Let's say we have custom station codes for buses in Czechia, and train have "local" part of UIC station codes. So I would request x_cze:cisjr for buses and x_cze:sr70 for trains.

Content negotiation can work for that, same pattern that HTTP accept headers use.
This pattern involves supporting multiple values and a (optional) quality value where the client be specific which values are preferred in which order. Docs on this https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Accept-Language. I don't think a quality value would be of real added value in OSDM because the amount of different namespaces per operator would usually be only a few.  In increases complexity while not providing enough value (imo) at the moment. We can always add this in the future when a need arises.
In your example it would be something like, when using a header
x-accept-namespace: uic, x_cze
Where a uic namespace is returned where possible and x_cze as fallback.
With this approach we need to agree what the default behaviour should be if no header/param is provided or when the OSDM provider cannot fulfil the request. I guess the exact behaviour as today because it is not supported yet ;)
x-accept-namespace: uic would prefer the UIC namespace code, if not possible use the provider default
x-accept-namespace: uic, iata, haf, x_cze would prefer uic, fallbacks to iata, which fallbacks to haf which fallbacks to x_cze and then as last resort let the provider decide
x-accept-namespace: * would let the OSDM provider use its default namespace

Entur are not having problems with the issue described.

I've created a PR and added the x-accept-namespace header to the resources that have a URN somewhere in the response, where no client input with a URN is given to cover the cases where the provider has to guess the URN the client prefers.

I've seen the branch. Looks good to me. Please create the PR for approval.


Need to help in setup

Hi, I want to setup the project. I have downloaded the project. Extracted the zip to the folder 'technicalindicators-master'. I ran the  'npm install --save technicalindicators'. It installed the node_modules folder in the root directory. After this I have written the below simple script to check the Bearish Engulfing Pattern.
var BearishEngulfingPattern = require('technicalindicators').BearishEngulfingPattern;
var twoDayBearishInput = {
  open: [21.44,27.89],
  high: [25.10,30.87],
  close: [23.25,15.36],
  low: [20.82,14.93],
}
var result      = BearishEngulfingPattern.hasPattern(twoDayBearishInput);
console.log( 'Is BearishEngulfingPattern? :' +result);

But I am getting below error.
TypeError: Cannot read property 'hasPattern' of undefined
    at Object.<anonymous> (/home/lk/Downloads/technicalindicators-master/node_c975eebf38a1f.tmp:8:42)
    at Module._compile (module.js:570:32)

I am very new to the nodejs world. Could you please someone help me how to resolve this? I debug and found that the require('technicalindicators').BearishEngulfingPattern is returning unidentified.

This issue is a duplicate of https://github.com/anandanand84/technicalindicators/issues/38
Below are the steps anyways.
Actually, you dont have to extract the zip, Just go to a new folder and follow the steps

npm init this creates a new nodejs project.

npm install --save technicalindicators this installs and saves the technical indicators dependency.

Create a new file(index.js) and use below code.

var bearishengulfingpattern =require('technicalindicators'). bearishengulfingpattern;

var twoDayBearishInput = {
  open: [21.44,27.89],
  high: [25.10,30.87],
  close: [23.25,15.36],
  low: [20.82,14.93],
}

var result      = bearishengulfingpattern(twoDayBearishInput);
console.log('Is Bearish Engulfing Pattern? :' +result);

run node index.js
with the latest code you dont have to use has pattern any more. Actually in runkit examples it uses old version, so it working, I'll update the runkit examples. Thankyou. See below the list of export names

https://github.com/anandanand84/technicalindicators/blob/master/src/index.ts


I am using proxy config to connect my spring backend api... its working fine when in localhost:4200 but its not calling when deploying it in server .

Bug, feature request, or proposal:
What is the expected behavior?
What is the current behavior?
What are the steps to reproduce?
Providing a StackBlitz reproduction is the best way to share your issue.
StackBlitz starter: https://goo.gl/wwnhMV
What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Is there anything else we should know?

Please keep GitHub issues for bug reports / feature requests. Better avenues for troubleshooting / questions are stack overflow, gitter, mailing list, etc.


V1api

Create v1 publish API

* upconvert from v1alpha1 (scheduled for removal)
* add "traveler" boolean indicating a key has left the designed HA boundry
* change authorized app to health authority ID
* default the region(s) for a health authority

Fixes #792
Fixes #793
Basis for #794

rebased

#813 will cause a merge conflict, I want to merge that in first and then rebase again
/hold

/unhold
rebased - now with faster tests!

/lgtm

/lgtm