Ability to open invite links

Hello!
I've received a group invite link, and I see no way to open that in whatsapp web to go.
So please add a way to do that. I believe even a way to open any link in the internal webview session would be fine, as then it would just simply work normally.
Thank you for this app!
Cheers!

Hello @KopiasCsaba
should be fixed with #87


Change bootloader-id to work correctly after grub boothole v2 updates

Description
Makes osie install uefi with --bootloader-id=ubuntu.
Why is this needed
Recent Ubuntu grub updates to fix the BootHole vulnerabilities ended up
hard coding the grub config lookup from \efi\ubuntu, but grub-install --bootloader-id=grub
places it into \efi\grub. Boot failures ensue.
How Has This Been Tested?
Modified ci/vm.sh to boot the installed VM.
I was able to reproduce the boot hang without this change and no issues after.

Failing for centos_7 atm

Is this PR ready to be re-reviewed?

Nope, closing in favor of #228


pkg: Upgrade react to 18 final

https://reactjs.org/blog/2022/03/29/react-v18.html

Codecov Report

Merging #1845 (cd690ac) into master (f98fc46) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1845   +/-   ##
=======================================
  Coverage   98.63%   98.63%
=======================================
  Files         103      103
  Lines        1901     1901
  Branches      383      383
=======================================
  Hits         1875     1875
  Misses         14       14
  Partials       12       12

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Swaggard hash param usage on Rails 5

Hello,
I'm not sure how to correctly use the hash feature. Params for my controllers have to be inside of a hash, like so {"talent"=>{"name":"Some Person"}}, where talent is the name of the hash. I'm running rails 5. The comments I have for the create method look like this:
#Creates a talent record
#@body_parameter [hash] talent

The resultant swagger interface looks weird. it looks like this:

Notice the "dash" signs in place of a body field. How do I get the body to show?

On the right hand side, I'd like the talent hash to be populated with keys and values. Is there a way to currently achieve that? I tried a few tricks, but couldn't get the "name":"Some Person" key-value pair to show up there.

Thank you!

There is a way but its not pretty, basically you need to tell swaggard from where to get the information from.
On your controller:
#Creates a talent record
#@body_parameter [Api::Input::TalentForCreation] talent

then in api/input/talent_for_creation.rb
@attr [string] name
class Api::Input::TalentForCreation; end

in config/initializers/swaggard.rb
Swaggard.configure do |config|
  ...
  config.models_paths = %W[#{Rails.root}/api/input/**/*.rb]
  ...
end

Note that the path or the class name can be anything its just an empty class that holds the documentation for your input models.
If you have a different idea of how to archive what you need let me know and maybe we can try it out.
Another option would be to receive the params bare, as in not inside a talent key.

also for the issue of not being able to edit the json by hand I will release a new version that has the option to disable the json editor and replaces it with a simple text box that you can edit by hand

Hi Adrian,
Thanks for such a prompt response! I tried your first suggestion. And I get a Syntax error in talent_for_creation.rb ([warn]: Syntax error in talent_for_creation.rb:(1,19): syntax error, unexpected tidentifier, expecting end-of-input). So I tried removing the semicolon, and it was the same. I put the semicolon back in and this is what the swagger ui looks like right now (it loads in spite of the syntax error).

Also, this is my swaggard.rb initializer configuration:
Swaggard.configure do |config|
config.api_version = '0.1'
config.api_base_path = "/"
config.default_content_type = 'application/json'
config.models_paths = %W[#{Rails.root}/api/input/**/*.rb]
config.api_formats = [:json]
config.api_path = "/"
config.host = "localhost:3000"
config.doc_base_path = '/'
end
Any idea on what I'm doing wrong?
Thanks!

Hey when I posted the example I missed the # symbol on api/input/talent_for_creation.rb, it should be:
# @attr [string] name
class Api::Input::TalentForCreation; end

Can't believe I missed that. This works now, thanks Adrian!

np, glad it works for you now!
I'm closing this out

Hi Adrian,
Sorry to pile on top of this. The workaround you provided works great. However, if I want to have nested hash, how would I go about doing that?
For example:
{
  talent : {
    name : <name>,
    address : {
      address_1: <address_1>,
      address_2: <address_2>,
      city: <city>
    }
  }
}

In this case, address is a nested hash. Similar to api/input/talent_for_creation.rb, I created an other file had the details of this address with a class name Api::Input::TalentAddress and added #@body_parameter [Api::Input::TalentAddress] address to talent_for_creation.rb. But that did not help.
Any pointers on how to solve this would be great.
Thanks.

the *_parameter is only for the controller layer, for the models you should only use @attr.
In your case it would be:
# @attr [Api::Input::TalentAddress] address

Awesome. That worked. Thank you very much for your quick response.


Only run the Manifest Updater one time per week

Before this PR, we run the Manifest Updater one time per day.
After this PR, we run the Manifest Updater one time per week.

Can we do it as a workflow trigger? Then we can just run it when we want to bump versions, eg new RegistryCI release

Can we do it as a workflow trigger? Then we can just run it when we want to bump versions, eg new RegistryCI release

Yep, we also have a workflow_dispatch trigger.
But I do think that there is value in also having a scheduled (cron) job that runs e.g. weekly. That way, we make sure that we update to e.g. the latest bug fix releases of all of our indirect (recursive) dependencies.

Ah good, the trigger will be useful then.
Yeah, I can see it being be bad to get way behind on releases and then run into accumulated issues doing a big update to get some urgent bugfix.


Godeps: update to the last docker2aci

The last docker2aci should help with the following issues:

https://github.com/coreos/rkt/issues/1653 (whiteout-ed hard links)
https://github.com/coreos/rkt/issues/1617 (/dev/stdout)

LGTM


Again same problem

Issue description
Again I've got the same problem.  my stakes are invisible in my wallet. I've started the staking, but now it is saying that " 0 mi staked

"I've got
Firefly version
Fireflyy v1.3.0
OS details
mac
Can the issue be reliably reproduced?
No
Steps to reproduce the issue

...
Expected behaviour
Again I've got the same problem.  my stakes are invisible in my wallet. I've started the staking, but now it is saying that " 0 mi staked
Actual behaviour
Again I've got the same problem.  my stakes are invisible in my wallet. I've started the staking, but now it is saying that " 0 mi staked
Errors
No response

Please read https://github.com/iotaledger/firefly/issues/1894

Issue can be closed

thanks
Best Regards,
Huseyin Ercan KURUZ | Certifying Engineer
m. +971 (0)58 891 1633
@.*** | flydubai.com

On 26 Dec 2021, at 11:33 PM, MiKeF05 @.***> wrote:
Issue can be closed
—
Reply to this email directly, view it on GitHub https://github.com/iotaledger/firefly/issues/1895#issuecomment-1001231139, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWTQ3MXWQCKLYI7IGBUH6RTUS5UW3ANCNFSM5KZGURTA.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.


docs(help&support): create dart version of help&support

create dart version of help&support and link to the official slack channel
fix #675

Taking a look now.

LGTM. I'll merge this soon.


Update ENU XLF files

Loc hand-back

Resource string updated from auto-generated files.  Nothing to review.


Possible Expose Response Object To Calling Function When API PostmanRequestRunner.run Method In Invoked

Hi There,
I have been trying out your library for the last few days. Super work
Albeit I feel it's missing one or two very important features

I'd like to know what the full request object was post environment variables substitution
I'd like to do validations on the response object within the Run method

Is it possible that these two items are returned as part of the return from executing the API PostmanRequestRunner.run?
I'm almost certain that exposing these items would open the library to a wider audience.

Good suggestion @bhreinb. I will try to get to this soon. Feel free to fork and send a pull request if you need the change sooner. It should be relatively straightforward.

@bhreinb Does this work for your use case? https://github.com/poynt/postman-runner/commit/f3d00ec1d4b01ae739ffd10fa385fe86b6f39a2b

Hi @vchau
I'll try it out and revert back to you. Thx a mill :)

Hi @vchau
I tried this and it seem to work good for my use case. I'd love to get this as soon as you can make it available? Thanks so much for your help with this.


Not able to add user

Description

Not able to add user.
Environment

Pinpoint version: 1.7.1
OS, WAS, affected library, etc: Linux , 3.10.0-514.el7.x86_64
Additional details (e.g. how your collector/web is set up): added the war in /root/apache-tomcat-8.0.33/webapps/pinpoint-web-1.7.1

Additional Info

I am not able to add the user as it's giving an error.

and edituserinfo is already set to true
[root@localhost pinpoint-web-1.7.1]# cat /root/apache-tomcat-8.0.33/webapps/pinpoint-web-1.7.1/WEB-INF/classes/pinpoint-web.properties |grep editUserInfo
config.editUserInfo=true
[root@localhost pinpoint-web-1.7.1]#

What version of the pinoint do you use?
Maybe your question is same https://github.com/naver/pinpoint/issues/3711.


[Test] Run test cases in parallel to improve build efficiency.

Today it takes around 50 minutes to finish a CLI build task on Travis. The build is repeated on three platforms: python2.7, python3.5 and python3.5-dev. Therefore, the average time spent on each platform is around 16 minutes.
All of our tests are VCR.py based. That means the test executions are already encapsulated enough.
I'd like to explorer the possibility of running tests in parallel in order to shorten the build time on CI.

@troydai this can be closed, yes?

Partially.
We're able to run test modules in parallel, but not the tests in test suites.

This is done.


Maven profile  install problem

I build pulsar from source for the first time,
mvn -DskipTests install -Pcore-modules
it throws an error like this:
[INFO] Pulsar IO :: Kafka Connect Adaptor ................. FAILURE [ 11.475 s]
Could not transfer artifact org.apache.pulsar:kafka-connect-avro-converter-shaded:pom:2.8.0-SNAPSHOT from/to spring-plugins-release (https://repo.spring.io/plugins-release/): Not authorized -> [Help 1]
Maybe "kafka-connect-avro-converter-shaded" module should be added to the "core-modules" profile?
(for the user who never use "main" profile to perform a full build before)

probably related to this: https://spring.io/blog/2020/10/29/notice-of-permissions-changes-to-repo-spring-io-fall-and-winter-2020

probably related to this: https://spring.io/blog/2020/10/29/notice-of-permissions-changes-to-repo-spring-io-fall-and-winter-2020

@nchuxyz
remove the spring repo
<repository>
   <id>spring-plugins-release</id>
   <url>https://repo.spring.io/plugins-release/</url>
 </repository>

from root pom.xml solve the problem, you can give it a try.

@nchuxyz
remove the spring repo
<repository>
   <id>spring-plugins-release</id>
   <url>https://repo.spring.io/plugins-release/</url>
 </repository>

from root pom.xml solve the problem, you can give it a try.

@sijie Should we just remove the spring repo?

@sijie Should we just remove the spring repo?

It works.
Thanks a lot

It works.
Thanks a lot

@MarvinCai I think so.

@MarvinCai I think so.

@sijie It's happened to be removed by this pr: https://github.com/apache/pulsar/pull/9280, I think no additional action needed.

@sijie It's happened to be removed by this pr: https://github.com/apache/pulsar/pull/9280, I think no additional action needed.

Failed to read artifact descriptor for net.minidev:json-smart:jar:2.3-SNAPSHOT: Could not transfer artifact net.minidev:json-smart:pom:2.3-SNAPSHOT from/to spring-plugins-release (https://repo.spring.io/plugins-release/): Not authorized

Failed to read artifact descriptor for net.minidev:json-smart:jar:2.3-SNAPSHOT: Could not transfer artifact net.minidev:json-smart:pom:2.3-SNAPSHOT from/to spring-plugins-release (https://repo.spring.io/plugins-release/): Not authorized

this problem occur in branch 2.7.0

We could cherry pick #9280 to branch-2.7.0, that repo was useless


Witnesschain watchtower template

Add Witness Chain Watchtower deployment template

Hey @Shankusu993 !
Your PR looks awesome, ty!
But I think that your template can  be placed in the "blockchain" section, so as not to create a new "validators" section.
Let me know, what do you thing about this.

Hey @Dimokus88 !
Thanks for the feedback. I believe the "Blockchain" section currently contains images for running validator/full nodes of various L1/other chains. The watchtower is not validator node for any specific blockchain, but more of a generic proof-of-location for any physical node (not necessarily blockchain node) connected to internet. Furthermore, in the future releases, it'll get capabilities to watch for more physical attributes - like bandwidth, compute etc.
I also think a broader 'Validator' section in-general can be useful for any other non-blockchain validator protocols (and outside witnesschain's watchtowers too).
Let me know if this sounds reasonable, can otherwise put it under 'blockchain' as you recommended.

Thank's @Shankusu993 !
Sounds reasonable.
On my end, the checks are complete and I believe the template is ready for merging.
If @anilmurty or @brewsterdrinkwater  are okay with adding a new section in root README.md , we can merge.

Hey @Shankusu993 - we already have a category called "Blockchain" - I think it makes sense to add WitnessChain Watchtower there

Hey @anilmurty, thanks for your feedback. I've moved the watchtower to 'Blockchain' section. Would appreciate a second review :)

Thanks @Shankusu993 - changes look good, will approve and merge


Can you provide WAP code?Thanks!

Hello, David.
I saw your paper and ran the code.
I get a confusion matrix after running the analysis/Confusion_Matrix.ipynb.
But I can't get WAP to evaluate my result.
Can you provide WAP code?
Or can I just compute WAP from confusion matrix?
Thanks.

Hello. May I ask how it runs through? I have obtained the dataset from the paper.

Hi @OnlyAoiKunie , @cuiyimeng
Sorry for the late response. You may find the code (WA, UA) from another repository below:
https://github.com/david-yoon/attentive-modality-hopping-for-SER/blob/master/util/measure_WA_UA.py


Object reference not set to an instance of an object

Hi Geral,
I tried using new code but now I getting error "Object reference not set to an instance of an object."
exec [dbo].[APICaller_POST]
@url = 'https://{SOME_SECURE_URL}'
,@JsonBody = '{"password":"*****"}'

Bro, I just fixed it!.


emit $translateReady Event

In my applications I'd like to know "as soon as possible" what language should to be displayed ( I fetch language specific content from a remote web service ).
As mentioned in #1195 this can't reliably done in a modules's run() or config() methods using $translate.use().
My idea is to collect the promises from $translate.use(preferedOrStoredOrFallBack) in the runTranslate() method and emit an appropriate event when the promise resolves.
I hacked a little around and it seems to work.
Would this approach technically correct?
How would this event correctly be named?

due to #1201


TFLite Cocoapod error

Upon pasting the "pod install --project-directory=ios/tflite/" command I am getting an error:
"[!] Unable to find a specification for TensorFlowLite"

Sorry solved my own issue, all you have to do is run "pod repo update" and it solves it


Doesn't work with gin-gonic

When using with gin-gonic with authboss I get exception:
ResponseWriter must be a ClientStateResponseWriter or UnderlyingResponseWriter in (see: authboss.LoadClientStateMiddleware): *gin.responseWriter
/home/kamil/go-libs/pkg/mod/github.com/volatiletech/authboss@v2.2.0+incompatible/client_state.go:174 (0x7cde7d)
	MustClientStateResponseWriter: panic(fmt.Sprintf("ResponseWriter must be a ClientStateResponseWriter or UnderlyingResponseWriter in (see: authboss.LoadClientStateMiddleware): %T", w))
/home/kamil/go-libs/pkg/mod/github.com/volatiletech/authboss@v2.2.0+incompatible/client_state.go:303 (0x7ce2a4)
	setState: csrw := MustClientStateResponseWriter(w)
/home/kamil/go-libs/pkg/mod/github.com/volatiletech/authboss@v2.2.0+incompatible/client_state.go:295 (0x7d3a1b)
	putState: setState(w, CTXKey, ClientStateEventPut, key, val)
/home/kamil/go-libs/pkg/mod/github.com/volatiletech/authboss@v2.2.0+incompatible/client_state.go:266 (0x7d39eb)
	PutSession: putState(w, CTXKeySessionState, key, val)
/home/kamil/go-libs/pkg/mod/github.com/volatiletech/authboss@v2.2.0+incompatible/defaults/responder.go:134 (0x7d39ea)
	Redirector.redirectNonAPI: authboss.PutSession(w, authboss.FlashErrorKey, ro.Failure)
/home/kamil/go-libs/pkg/mod/github.com/volatiletech/authboss@v2.2.0+incompatible/defaults/responder.go:74 (0x7d338a)
	(*Redirector).Redirect: return redirectFunction(w, req, ro)
/home/kamil/go-libs/pkg/mod/github.com/volatiletech/authboss@v2.2.0+incompatible/authboss.go:190 (0x7cd335)
	MountedMiddleware2.func1.1.1: if err := ab.Config.Core.Redirector.Redirect(w, r, ro); err != nil {
/home/kamil/go-libs/pkg/mod/github.com/volatiletech/authboss@v2.2.0+incompatible/authboss.go:203 (0x7cce81)
	MountedMiddleware2.func1.1: fail(w, r)
/opt/go/src/net/http/server.go:2046 (0x61ceee)
	HandlerFunc.ServeHTTP: f(w, r)
/home/kamil/go-libs/pkg/mod/github.com/gwatts/gin-adapter@v0.0.0-20170508204228-c44433c485ad/adapter.go:49 (0x7c8307)
	New.func1.1: h.ServeHTTP(c.Writer, c.Request.WithContext(ctx))
/home/kamil/go-libs/pkg/mod/github.com/gin-gonic/gin@v1.3.0/context.go:108 (0x7bf4b5)
	(*Context).Next: c.handlers[c.index](c)
/home/kamil/go-libs/pkg/mod/github.com/gwatts/gin-adapter@v0.0.0-20170508204228-c44433c485ad/adapter.go:76 (0x7c84c4)
	(*connectHandler).ServeHTTP: state.ctx.Next()
/home/kamil/go-libs/pkg/mod/github.com/volatiletech/authboss@v2.2.0+incompatible/client_state.go:121 (0x7cd701)
	(*Authboss).LoadClientStateMiddleware.func1: h.ServeHTTP(writer, request)
/opt/go/src/net/http/server.go:2046 (0x61ceee)
	HandlerFunc.ServeHTTP: f(w, r)
/home/kamil/go-libs/pkg/mod/github.com/gwatts/gin-adapter@v0.0.0-20170508204228-c44433c485ad/adapter.go:49 (0x7c8307)
	New.func1.1: h.ServeHTTP(c.Writer, c.Request.WithContext(ctx))
/home/kamil/go-libs/pkg/mod/github.com/gin-gonic/gin@v1.3.0/context.go:108 (0x7bf4b5)
	(*Context).Next: c.handlers[c.index](c)
/home/kamil/go-libs/pkg/mod/github.com/gin-gonic/gin@v1.3.0/recovery.go:48 (0x7c3485)
	RecoveryWithWriter.func1: c.Next()
/home/kamil/go-libs/pkg/mod/github.com/gin-gonic/gin@v1.3.0/context.go:108 (0x7bf4b5)
	(*Context).Next: c.handlers[c.index](c)
/home/kamil/go-libs/pkg/mod/github.com/gin-gonic/gin@v1.3.0/recovery.go:48 (0x7c3485)
	RecoveryWithWriter.func1: c.Next()
/home/kamil/go-libs/pkg/mod/github.com/gin-gonic/gin@v1.3.0/context.go:108 (0x7bf4b5)
	(*Context).Next: c.handlers[c.index](c)
/home/kamil/go-libs/pkg/mod/github.com/gin-gonic/gin@v1.3.0/logger.go:84 (0x7c26b8)
	LoggerWithWriter.func1: c.Next()
/home/kamil/go-libs/pkg/mod/github.com/gin-gonic/gin@v1.3.0/context.go:108 (0x7bf4b5)
	(*Context).Next: c.handlers[c.index](c)
/home/kamil/go-libs/pkg/mod/github.com/gin-gonic/gin@v1.3.0/gin.go:361 (0x7c1a38)
	(*Engine).handleHTTPRequest: c.Next()
/home/kamil/go-libs/pkg/mod/github.com/gin-gonic/gin@v1.3.0/gin.go:326 (0x7c16ad)
	(*Engine).ServeHTTP: engine.handleHTTPRequest(c)
/opt/go/src/net/http/server.go:2878 (0x61fb1a)
	serverHandler.ServeHTTP: handler.ServeHTTP(rw, req)
/opt/go/src/net/http/server.go:1929 (0x61c247)
	(*conn).serve: serverHandler{c.server}.ServeHTTP(w, w.req)
/opt/go/src/runtime/asm_amd64.s:1581 (0x464720)
	goexit: BYTE	$0x90	// NOP

Reply steps:

clone repository: https://github.com/jesusvazquez/authboss-gin-sample
Add	// authorization required
rAdmin := router.Group("/admin")

rAdmin.Use(adapter.Wrap(authboss.Middleware2(ab, authboss.RequireNone, authboss.RespondRedirect)))
rAdmin.GET("/", status)

in main() after router.GET("/status", status)
Build & run
Execute curl localhost:3000/admin/ -> an exception is thrown

If you're using a framework like gin-gonic which takes over the response writer you need to ensure proper ordering of middlewares. I don't generally help sort out custom frameworks issues though. This library works fine with the stdlib http package and many other packages like chi and httprouter.

I just ran into this and did some debugging. If you're using the example from https://github.com/jesusvazquez/authboss-gin-sample that's using github.com/gwatts/gin-adapter to convert regular middleware into Gin middleware.
If you step through the flow in a debugger you see that authboss.LoadClientStateMiddleware calls h.ServeHTTP at the end of that method. If you step into that you'll find yourself in the github.com/gwatts/gin-adapter code, specifically here:
func (h *connectHandler) ServeHTTP(w http.ResponseWriter, r *http.Request) {
	state := r.Context().Value(h).(*middlewareCtx)
	defer func(r *http.Request) { state.ctx.Request = r }(state.ctx.Request)
	defer func(w gin.ResponseWriter) { state.ctx.Writer = w }(state.ctx.Writer)
	state.ctx.Request = r
	state.ctx.Writer = swap(state.ctx.Writer, w)
	state.childCalled = true
	state.ctx.Next()
}

Note that swaps out the response writer via the swap call which returns a swappedResponseWriter which contains the original writer but hidden as a member. The defer should swap it back when this returns but authboss tries to use the writer before this method returns so you get the panic.
To make this work we'd need an alternative form of adapter but I'm not sure how that could work. authboss creates a new response writer derived from the http.ResponseWriter but we can't just construct a Gin one from that because it's missing some of the data in gin's response writer (number of bytes written so far and status code to send). I might be missing something but I think this just won't work with gin.

Oh! It looks like maybe somebody found a workaround. This is a update to github.com/gwatts/gin-adapter that has their swappedResponseWriter implement the UnderlyingResponseWriter interface: https://github.com/bscottm/authboss-worked/blob/6b1cea2dd7df0788790fbf6d48d4d25591aa5413/abossworked/adapter/ginWrap.go


Support for Responsive Design

I just found out about the winds and its beautiful.
There is an issue while using it on my smartphone it would be super nice if it is optimized for mobile as well.
Is it on the roadmap yet? Will it support it soon or not?
One more Question is it possible to make it able use it  without needing those proprietary solutions like Algolia, streaming api and few more?

@mahboubii
Is there any plan to have a responsive design? I have just "installed" the app (PWA :heart: ) on my phone and the UI is not so good

Mobile UI and Dark Mode are features we definitely need to add but unfortunately, at the moment our designer and dev team are super busy to work on it.

Mobile UI and Dark Mode are features we definitely need to add but unfortunately, at the moment our designer and dev team are super busy to work on it.

in addition is there a plan to have a mobile app/client in the future?

@ArtexJay that's possible, but it's not on the roadmap now.


Delay occurs when sliding with position  in a dom

Hi, @anseki。Thank you for providing such a good project~
I encountered some problems in use，Delay occurs when sliding with position()  in a dom。After the delay, it returns to the correct position。
document.getElementById('treedom').addEventListener('scroll', () => {
    if (this.lines && this.lines.length) {
        this.lines.forEach(line => {
          line.position();
        });
      }
  });

I want to upload the video. I uploaded the video in the github, but I'm not sure if you can see it.

Hi @yuleiQ, thank you for the comment.
To reproduce that, could you show an example by using e.g. https://jsfiddle.net/ ?

Because I can't use this tool, I transferred the components I encapsulated to github. Do you have a Vue environment to run? Thank you.
Process-tree

I think the problem is that there are too many recursive rendering lines. I render about 20 lines at a time. I also try your library AnimEvent, but it seems to have no effect

I have solved this problem，close issue，thank you

:smile:  :thumbsup:


tus.Upload make a POST request instead of PATCH

Describe the bug
tus.Upload make a POST request instead of PATCH. I am trying to upload to Vimeo but he responds with a 405, Method not allowed. The only thing that I have found in the documentation that could change the behavior was adding "overridePatchMethod" to true in the options, but I am not using this option.
Expected behavior
Expect tus.Upload use PATCH method
Setup details

Runtime environment: Browser (Chrome - Version 74.0.3729.131 (Official Build) (64-bit))
Used tus-js-client version<EMAIL_ADDRESS>Used tus server software: tus-js-client

This is not a bug in tus-js-client but you are actually configuring the library in the wrong way. Vimeo needs some special options to work: Since Vimeo already creates a tus upload resource on the server, tus-js-client doesn't need to send a POST request. And you can tell tus-js-client this by omitting the endpoint option and instead setting the uploadUrl option to the URL you get from Vimeo. The overridePatchMethod is unrelated to your problem and is only necessary when the browser or server don't support the PATCH method which is not happening in your situation.
Try changing the options and it should work as you expect.

Closing this issue due to inactivity. Feel free to leave a comment if you want to continue the discussion :)


Added gpu tests

including #577

Although the current tests include a little number of gpu test, it is not sufficient. Thus; I added gpu test for almost all the test.
For selecting those tests, you must add -m gpu option to pytest command.

Codecov Report

Merging #578 (091697e) into develop (bdd9653) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff            @@
##           develop     #578   +/-   ##
========================================
  Coverage    97.15%   97.15%
========================================
  Files           56       56
  Lines         2317     2317
========================================
  Hits          2251     2251
  Misses          66       66

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

moved to #604


Remove Netlify CMS (2/2)

This moves files from www/src/cms to www/src/pages.
It also runs the files through Prettier.

Fixed simple merge conflict. Will merge.


Added logic to run sampler a second time after http instrumentation libraries

Issue #, if available:
Description of changes:
This new function runs the sampler a second time after the needed attributes (such as UrlPath and HttpTarget) are finally available from the http instrumentation libraries. The sampler hooked into the Opentelemetry SDK runs right before any activity is started so for the purposes of our X-Ray sampler, that isn't going to work and breaks the X-Ray functionality.
Below is the stack trace showing the sampler running before the instrumentation libraries are started.
   at OpenTelemetry.Sampler.AWS.AWSXRayRemoteSampler.ShouldSample(SamplingParameters& samplingParameters) in /local/home/heayh/pulse-dotnet/opentelemetry-dotnet-contrib/src/OpenTelemetry.Sampler.AWS/AWSXRayRemoteSampler.cs:line 86
   at AWS.Distro.OpenTelemetry.AutoInstrumentation.AlwaysRecordSampler.ShouldSample(SamplingParameters& samplingParameters) in /local/home/heayh/pulse-dotnet/aws-otel-dotnet-instrumentation+sampler/src/AWS.Distro.OpenTelemetry.AutoInstrumentation/AlwaysRecordSampler.cs:line 70
   at OpenTelemetry.Trace.TracerProviderSdk.RunGetRequestedDataOtherSampler(Activity activity)
   at OpenTelemetry.Trace.TracerProviderSdk.<>c__DisplayClass12_1.<.ctor>b__9(Activity activity)
   at System.Diagnostics.ActivitySource.<>c.<NotifyActivityStart>b__24_0(ActivityListener listener, Object obj)
   at System.Diagnostics.SynchronizedList`1.EnumWithAction(Action`2 action, Object arg)
   at System.Diagnostics.ActivitySource.NotifyActivityStart(Activity activity)
   at System.Diagnostics.Activity.Start()

Below is also a comment from AspNetCore instrumentation library mentioning that the required attributes are only available after sampling decision is made:
https://github.com/open-telemetry/opentelemetry-dotnet-contrib/blob/main/src/OpenTelemetry.Instrumentation.AspNetCore/Implementation/HttpInListener.cs#L91-L99
Finally, I opened this discussion and in there is a slack thread going through a similar issue:
https://github.com/open-telemetry/opentelemetry-dotnet/discussions/5839
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

This would have performance impact and when onboarding customer for the first time, this might not be a good experience.. I would stick with HttpContextAccessor for .NET Core and use upstream for ASPNET. Let's follow-up with OTEL maintainers to get http/method into upstream.


Document --quick option in README

Description
This change adds a bit of documentation concerning the --quick option. I did not create an issue beforehand as I believe that this is a "trivial documentation" change (as described in CONTRIBUTING.md).  This change was inspired by discussion on https://github.com/aquasecurity/starboard/issues/165.
Contribution Guidelines
Please Read through the Contribution Guidelines.
Fixed Issues
N/A
"BEFORE" and "AFTER" output
N/A
Contribution checklist

[x] I have read the Contributing Guidelines.
[x] The commits refer to an active issue in the repository. (N/A)
[x] I have added automated testing to cover this case. (N/A)

Notes
N/A

Hi @mlevesquedion
That's a really good idea!
quick scanning is a feature that solves a problem in azure scanning. I agree that this should be documented. But I believe we should create something like a Q&A.md or ADVANCEDUSAGE.md  and in there, start adding knowledge like that.
Because it is not falling under a scanning method,  but rather falls under general knowledge.
Wdyt?

Hi @danielsagi
Thanks for taking a look at my PR! I agree that this might not belong in the README. On the other hand, I'm not sure it's worth creating an extra file just for this piece of documentation. Are there other things which currently aren't documented, but that we could put into such a Q&A or ADVANCEDUSAGE file?

Hi @mlevesquedion
Sorry  for the late reply, I agree. Maybe add an Advance Usage section in the original Readme file.

closing, due to inactivity... I created a new PR for this #441


ENH : Bec qtbrowser compat

proposed enhancement for use of db browser
needs #963 first
(this was rebased on 963 right now)
Also, we may want to squash these commits.

Codecov Report

Merging #967 into master will increase coverage by 0.04%.
The diff coverage is 98.03%.

@@            Coverage Diff             @@
##           master     #967      +/-   ##
==========================================
+ Coverage   90.53%   90.57%   +0.04%
==========================================
  Files          48       48
  Lines        7816     7851      +35
==========================================
+ Hits         7076     7111      +35
  Misses        740      740

Impacted Files
Coverage Δ

bluesky/tests/test_callbacks.py
89.02% <100%> (+0.54%)
:arrow_up:

bluesky/callbacks/mpl_plotting.py
82.57% <100%> (+0.89%)
:arrow_up:

bluesky/plans.py
85.89% <100%> (+0.07%)
:arrow_up:

bluesky/callbacks/best_effort.py
87.7% <88.88%> (+0.13%)
:arrow_up:

Continue to review full report at Codecov.

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

@jrmlhermitte can you rebase this?

done. incredibly terse and basically just the modifications you suggested :-)

Squashed locally, merged into master as 2f9122b1b7e1e360e61f7476b5893407313b02d8, pushed.

thanks @danielballan !


Oriental Asian First Names

My first name is "Seng Bing" not "Seng". How can I make Microsoft's products more Asian/Oriental name friendly?

Hi @sengbinggo - for many Microsoft products, you can type two names with a space into the surname/first name field. This could accommodate both Asian and dual Anglophone names like Mary Rose.
Microsoft offers many ways to submit feedback for products. Here's a few ways to reach out to the product teams for some of Microsoft's most popular products:

Windows - on a Windows 10 PC, search for Feedback Hub to add new feedback or vote on feedback similar to yours.
Office 365 - https://office365.uservoice.com. UserVoice is a similar polling system to Feedback Hub that allows you to vote on feedback and add new pieces of feedback.
Xbox - https://xbox.uservoice.com

Hopefully this helps. For now, I'll close this issue. If you have more specific ones for Tutorials on Microsoft Docs, please feel free to open a new one.

May I know how to close this issue please?


Replace backslashes with slashes to fix e2e run

Signed-off-by: Stefan Scherer<EMAIL_ADDRESS>
- What I did
Make the PWD variable on Windows a path with forward slashes (again) instead of backslashes. I saw in older workflow runs that the path used forward slashes, then started failing running the e2e tests on Windows because of it having backslashes.
I was able to reproduce locally with MinGW64 11.2.0 installed:
$ mingw32-make -f builder.Makefile e2e
mkdir -p docker-config/scan
mkdir -p docker-config/cli-plugins
cp ./bin/docker-scan_windows_amd64.exe docker-config/cli-plugins/docker-scan.exe
# TODO: gotestsum doesn't forward ldflags to go test with golang 1.15.0, so moving back to go test temporarily
SNYK_DESKTOP_VERSION=1.827.0 SNYK_USER_VERSION=1.827.0 SNYK_OLD_VERSION=1.382.1 DOCKER_CONFIG=C:\code\scan-cli-plugin/docker-config SNYK_OLD_PATH=C:\code\scan-cli-plugin/docker-config/snyk-old SNYK_USER_PATH=C:\code\scan-cli-plugin/docker-config/snyk-user SNYK_DESKTOP_PATH=C:\code\scan-cli-plugin/docker-config/snyk-desktop go test ./e2e  -ldflags="-s -w -X github.com/docker/scan-cli-plugin/internal.GitCommit=5a67dc4 -X github.com/docker/scan-cli-plugin/internal.Version=v0.1.0-231-g5a67dc4185-dirty -X github.com/docker/scan-cli-plugin/internal/provider.ImageDigest=sha256:f9291a5310e3952369eeb8cd1c2a25f0c9fc930a3ccc88e1ea20956ad86b75a4 -X github.com/docker/scan-cli-plugin/internal/provider.SnykDesktopVersion=1.827.0"
panic: open C:codescan-cli-plugin\docker-config\cli-plugins\docker-scan.exe: The system cannot find the path specified.

- How I did it
Add a subst to replace all \ with /. Surprisingly in the Makefile I didn't had to use things like double \\ backslash, just a single one is fine here.
- How to verify it

have MinGW 64 11.2.0 installed
Run mingw32-make -f builder.Makefile e2e that failed for me without the substitution. With this fix it only complains about missing E2E vars, but it came across the path

- Description for the changelog

- A picture of a cute animal (not mandatory)

Should this fix the CI?

Yes, I hope so. CI is only trigger in the upstream repo, but not in forks, that's why we don't see a status here.
This PR should fix the errors we can see in the "Release and Weekly Build" workflow in https://github.com/docker/scan-cli-plugin/actions.
Even if I have created this PR directly in upstream repo, we couldn't run it there, only the build-pr workflow is triggered for PR's and that runs only on Linux nodes, but not on Windows.
I suggest we merge it and #204 and then see if that can build the missing linux/arm64 binary.

Yes, CI is green again -> https://github.com/docker/scan-cli-plugin/actions/runs/2789915771

So we don’t have CI on the PRs? 😞
#180 was trying to change that, right?

Good catch, yes. Looking at the comments in #180 I think we should just skip the e2e test in PR's to avoid providing the env variables in PR builds from random forks.


Update dependencies

About this change - What it does
This PR updates all of the dependencies in Guardian
Also ignore the fact that Build and Test (ubuntu-latest, 2.13.6<EMAIL_ADDRESS>isn't triggered and hence not completed, this is due to the latest version of sbt-github-actions using temurin instead (once this PR is merged then I will update the github branch status checks).

I have just rebased the PR with the requested changes


ROX-23087: bump jose-go

Backports:

https://github.com/stackrox/stackrox/pull/10274

Fixes:

https://github.com/go-jose/go-jose/security/advisories/GHSA-c5q2-7r4c-mv6g

/retest


No connection on AppStore

After a while after activating JB AppStore says that there is no connection, no matter if on Wi-Fi or 4G. Rebooting and jailbreaking again solves the issue.
It seems that it is also affecting connectivity on "News".
Could you please fix that?

sometimes happens for me too


failed to set up a HTTP server error="listen tcp :80: bind: permission denied"

Bug description
Fresh Ubuntu 22.04 container running on Proxmox 7.4 - all updates applied for both host and container.  Download and installed latest v0.22.0-alpha2 deb package using command "dpkg -i headscale_0.22.0-alpha2_linux_amd64.deb".
Tried to start it up after modifying the config.yaml (posted below).
Get the following error
Apr 14 12:25:36 hs headscale[366]: 2023-04-14T12:25:36-04:00 FTL ../../../home/runner/work/headscale/headscale/app.go:875 > failed to set up a HTTP server error="listen tcp :80: bind: permission denied"
# headscale will look for a configuration file named `config.yaml` (or `config.json`) in the following order:
#
# - `/etc/headscale`
# - `~/.headscale`
# - current working directory

# The url clients will connect to.
# Typically this will be a domain like:
#
# https://myheadscale.example.com:443
#
#server_url: http://<IP_ADDRESS>:8080
server_url: https://hs.example.com:443

# Address to listen to / bind to on the server
#
# For production:
listen_addr: <IP_ADDRESS>:443
#listen_addr: <IP_ADDRESS>:8080

# Address to listen to /metrics, you may want
# to keep this endpoint private to your internal
# network
#
metrics_listen_addr: <IP_ADDRESS>:9090

# Address to listen for gRPC.
# gRPC is used for controlling a headscale server
# remotely with the CLI
# Note: Remote access _only_ works if you have
# valid certificates.
#
# For production:
grpc_listen_addr: <IP_ADDRESS>:50443
#grpc_listen_addr: <IP_ADDRESS>:50443

# Allow the gRPC admin interface to run in INSECURE
# mode. This is not recommended as the traffic will
# be unencrypted. Only enable if you know what you
# are doing.
grpc_allow_insecure: false

# Private key used to encrypt the traffic between headscale
# and Tailscale clients.
# The private key file will be autogenerated if it's missing.
#
private_key_path: /var/lib/headscale/private.key

# The Noise section includes specific configuration for the
# TS2021 Noise protocol
noise:
  # The Noise private key is used to encrypt the
  # traffic between headscale and Tailscale clients when
  # using the new Noise-based protocol. It must be different
  # from the legacy private key.
  private_key_path: /var/lib/headscale/noise_private.key

# List of IP prefixes to allocate tailaddresses from.
# Each prefix consists of either an IPv4 or IPv6 address,
# and the associated prefix length, delimited by a slash.
# While this looks like it can take arbitrary values, it
# needs to be within IP ranges supported by the Tailscale
# client.
# IPv6: https://github.com/tailscale/tailscale/blob/22ebb25e833264f58d7c3f534a8b166894a89536/net/tsaddr/tsaddr.go#LL81C52-L81C71
# IPv4: https://github.com/tailscale/tailscale/blob/22ebb25e833264f58d7c3f534a8b166894a89536/net/tsaddr/tsaddr.go#L33
ip_prefixes:
  - <IP_ADDRESS>/10
  - fd7a:115c:a1e0::/48

# DERP is a relay system that Tailscale uses when a direct
# connection cannot be established.
# https://tailscale.com/blog/how-tailscale-works/#encrypted-tcp-relays-derp
#
# headscale needs a list of DERP servers that can be presented
# to the clients.
derp:
  server:
    # If enabled, runs the embedded DERP server and merges it into the rest of the DERP config
    # The Headscale server_url defined above MUST be using https, DERP requires TLS to be in place
    enabled: true

    # Region ID to use for the embedded DERP server.
    # The local DERP prevails if the region ID collides with other region ID coming from
    # the regular DERP config.
    region_id: 999

    # Region code and name are displayed in the Tailscale UI to identify a DERP region
    region_code: "headscale"
    region_name: "Headscale Embedded DERP"

    # Listens over UDP at the configured address for STUN connections - to help with NAT traversal.
    # When the embedded DERP server is enabled stun_listen_addr MUST be defined.
    #
    # For more details on how this works, check this great article: https://tailscale.com/blog/how-tailscale-works/
    stun_listen_addr: "<IP_ADDRESS>:3478"

  # List of externally available DERP maps encoded in JSON
  urls:
    - https://controlplane.tailscale.com/derpmap/default

  # Locally available DERP map files encoded in YAML
  #
  # This option is mostly interesting for people hosting
  # their own DERP servers:
  # https://tailscale.com/kb/1118/custom-derp-servers/
  #
  # paths:
  #   - /etc/headscale/derp-example.yaml
  paths: []

  # If enabled, a worker will be set up to periodically
  # refresh the given sources and update the derpmap
  # will be set up.
  auto_update_enabled: true

  # How often should we check for DERP updates?
  update_frequency: 24h

# Disables the automatic check for headscale updates on startup
disable_check_updates: false

# Time before an inactive ephemeral node is deleted?
ephemeral_node_inactivity_timeout: 30m

# Period to check for node updates within the tailnet. A value too low will severely affect
# CPU consumption of Headscale. A value too high (over 60s) will cause problems
# for the nodes, as they won't get updates or keep alive messages frequently enough.
# In case of doubts, do not touch the default 10s.
node_update_check_interval: 10s

# SQLite config
db_type: sqlite3

# For production:
db_path: /var/lib/headscale/db.sqlite

# # Postgres config
# If using a Unix socket to connect to Postgres, set the socket path in the 'host' field and leave 'port' blank.
# db_type: postgres
# db_host: localhost
# db_port: 5432
# db_name: headscale
# db_user: foo
# db_pass: bar

# If other 'sslmode' is required instead of 'require(true)' and 'disabled(false)', set the 'sslmode' you need
# in the 'db_ssl' field. Refers to https://www.postgresql.org/docs/current/libpq-ssl.html Table 34.1.
# db_ssl: false

### TLS configuration
#
## Let's encrypt / ACME
#
# headscale supports automatically requesting and setting up
# TLS for a domain with Let's Encrypt.
#
# URL to ACME directory
acme_url: https://acme-v02.api.letsencrypt.org/directory

# Email to register with ACME provider
acme_email<EMAIL_ADDRESS>
# Domain name to request a TLS certificate for:
tls_letsencrypt_hostname: "hs.example.com"

# Path to store certificates and metadata needed by
# letsencrypt
# For production:
tls_letsencrypt_cache_dir: /var/lib/headscale/cache

# Type of ACME challenge to use, currently supported types:
# HTTP-01 or TLS-ALPN-01
# See [docs/tls.md](docs/tls.md) for more information
tls_letsencrypt_challenge_type: HTTP-01
#tls_letsencrypt_challenge_type: TLS-ALPN-01
# When HTTP-01 challenge is chosen, letsencrypt must set up a
# verification endpoint, and it will be listening on:
# :http = port 80
tls_letsencrypt_listen: ":http"

## Use already defined certificates:
tls_cert_path: ""
tls_key_path: ""

log:
  # Output formatting for logs: text or json
  format: text
  level: info

# Path to a file containg ACL policies.
# ACLs can be defined as YAML or HUJSON.
# https://tailscale.com/kb/1018/acls/
acl_policy_path: ""

## DNS
#
# headscale supports Tailscale's DNS configuration and MagicDNS.
# Please have a look to their KB to better understand the concepts:
#
# - https://tailscale.com/kb/1054/dns/
# - https://tailscale.com/kb/1081/magicdns/
# - https://tailscale.com/blog/2021-09-private-dns-with-magicdns/
#
dns_config:
  # Whether to prefer using Headscale provided DNS or use local.
  override_local_dns: false

  # List of DNS servers to expose to clients.
  nameservers:
    - <IP_ADDRESS>
    - <IP_ADDRESS>
  # NextDNS (see https://tailscale.com/kb/1218/nextdns/).
  # "abc123" is example NextDNS ID, replace with yours.
  #
  # With metadata sharing:
  # nameservers:
  #   - https://dns.nextdns.io/abc123
  #
  # Without metadata sharing:
  # nameservers:
  #   - 2a07:a8c0::ab:c123
  #   - 2a07:a8c1::ab:c123

  # Split DNS (see https://tailscale.com/kb/1054/dns/),
  # list of search domains and the DNS to query for each one.
  #
  # restricted_nameservers:
  #   foo.bar.com:
  #     - <IP_ADDRESS>
  #   darp.headscale.net:
  #     - <IP_ADDRESS>
  #     - <IP_ADDRESS>

  # Search domains to inject.
  domains: []

  # Extra DNS records
  # so far only A-records are supported (on the tailscale side)
  # See https://github.com/juanfont/headscale/blob/main/docs/dns-records.md#Limitations
  # extra_records:
  #   - name: "grafana.myvpn.example.com"
  #     type: "A"
  #     value: "<IP_ADDRESS>"
  #
  #   # you can also put it in one line
  #   - { name: "prometheus.myvpn.example.com", type: "A", value: "<IP_ADDRESS>" }

  # Whether to use [MagicDNS](https://tailscale.com/kb/1081/magicdns/).
  # Only works if there is at least a nameserver defined.
  magic_dns: true

  # Defines the base domain to create the hostnames for MagicDNS.
  # `base_domain` must be a FQDNs, without the trailing dot.
  # The FQDN of the hosts will be
  # `hostname.user.base_domain` (e.g., _myhost.myuser.example.com_).
  base_domain: hs.example.com

# Unix socket used for the CLI to connect without authentication
# Note: for production you will want to set this to something like:
unix_socket: /var/run/headscale/headscale.sock
unix_socket_permission: "0770"
#
# headscale supports experimental OpenID connect support,
# it is still being tested and might have some bugs, please
# help us test it.
# OpenID Connect
# oidc:
#   only_start_if_oidc_is_available: true
#   issuer: "https://your-oidc.issuer.com/path"
#   client_id: "your-oidc-client-id"
#   client_secret: "your-oidc-client-secret"
#   # Alternatively, set `client_secret_path` to read the secret from the file.
#   # It resolves environment variables, making integration to systemd's
#   # `LoadCredential` straightforward:
#   client_secret_path: "${CREDENTIALS_DIRECTORY}/oidc_client_secret"
#   # client_secret and client_secret_path are mutually exclusive.
#
#   # The amount of time from a node is authenticated with OpenID until it
#   # expires and needs to reauthenticate.
#   # Setting the value to "0" will mean no expiry.
#   expiry: 180d
#
#   # Use the expiry from the token received from OpenID when the user logged
#   # in, this will typically lead to frequent need to reauthenticate and should
#   # only been enabled if you know what you are doing.
#   # Note: enabling this will cause `oidc.expiry` to be ignored.
#   use_expiry_from_token: false
#
#   # Customize the scopes used in the OIDC flow, defaults to "openid", "profile" and "email" and add custom query
#   # parameters to the Authorize Endpoint request. Scopes default to "openid", "profile" and "email".
#
#   scope: ["openid", "profile", "email", "custom"]
#   extra_params:
#     domain_hint: example.com
#
#   # List allowed principal domains and/or users. If an authenticated user's domain is not in this list, the
#   # authentication request will be rejected.
#
#   allowed_domains:
#     - example.com
#   # Note: Groups from keycloak have a leading '/'
#   allowed_groups:
#     - /headscale
#   allowed_users:
#     -<EMAIL_ADDRESS>#
#   # If `strip_email_domain` is set to `true`, the domain part of the username email address will be removed.
#   # This will transform<EMAIL_ADDRESS>to the user `first-name.last-name`
#   # If `strip_email_domain` is set to `false` the domain part will NOT be removed resulting to the following
#   user: `first-name.last-name.example.com`
#
#   strip_email_domain: true

# Logtail configuration
# Logtail is Tailscales logging and auditing infrastructure, it allows the control panel
# to instruct tailscale nodes to log their activity to a remote server.
logtail:
  # Enable logtail for this headscales clients.
  # As there is currently no support for overriding the log server in headscale, this is
  # disabled by default. Enabling this will make your clients send logs to Tailscale Inc.
  enabled: false

# Enabling this option makes devices prefer a random port for WireGuard traffic over the
# default static port 41641. This option is intended as a workaround for some buggy
# firewall devices. See https://tailscale.com/kb/1181/firewalls/ for more information.
randomize_client_port: true

Hi @TimDowker , I am unable to reproduce this in a fresh VM (both 22.04 and 22.10), is headscale able to bind to :443 and other privileged ports? Have you ran some extra hardening on your system to prevent these ports to be bound?
Do you have anything else bound on port :80?

Same error on a fresh proxmox container running ubuntu template 22.04 with all updates.
Apr 20 13:10:57 hs headscale[10261]: 2023-04-20T13:10:57Z FTL ../../../home/runner/work/headscale/headscale/app.go:875 > failed to set up a HTTP server error="listen tcp :80: bind: permission denied"

Looks like whatever user Go is running as doesn't have the appropriate permissions to bind to port 80 (priviledged port) even though the systemd service file contains "AmbientCapabilities=CAP_NET_BIND_SERVICE CAP_CHOWN"

For anyone also having the same issue, the headscale.sock file location was moved, hence the errors, if you don't edit your config.yaml, when transitioning to the .deb releases.
https://github.com/juanfont/headscale/blob/a5afe4bd06223f71a44ea7d42e9fb2ba3d178154/config-example.yaml#L259

/var/run/headscale/ keeps getting deleted, and installing the .deb doesn't fix it
:/

/var/run/headscale/ keeps getting deleted, and installing the .deb doesn't fix it :/

so,is there any solution now?

For anyone also having the same issue, the headscale.sock file location was moved, hence the errors, if you don't edit your config.yaml, when transitioning to the .deb releases.
https://github.com/juanfont/headscale/blob/a5afe4bd06223f71a44ea7d42e9fb2ba3d178154/config-example.yaml#L259

i found the requirements of headscale needs Ubuntu 20.04 or newer, Debian 11 or newer.i use centos7 and get same issue.

I had the same problem.
And the cause was letsencrypt setting
# Type of ACME challenge to use, currently supported types:
# HTTP-01 or TLS-ALPN-01
# See [docs/tls.md](docs/tls.md) for more information
tls_letsencrypt_challenge_type: HTTP-01
#tls_letsencrypt_challenge_type: TLS-ALPN-01
# When HTTP-01 challenge is chosen, letsencrypt must set up a
# verification endpoint, and it will be listening on:
# :http = port 80
tls_letsencrypt_listen: ":http"

I am using acme.sh to deal with certificates.
After clearing the hostname the error stopped.
# Domain name to request a TLS certificate for:
tls_letsencrypt_hostname: ""

Probably do you have anything already bonded to the port :80

I was running headscale in a debian 11 LXC container under proxmox. Enabling Nesting seems to have made it work.
Will report back if that wasn't the case.

It is caused by the following lines:
tls_letsencrypt_challenge_type: HTTP-01
# :http = port 80
tls_letsencrypt_listen: ":http"

This indicates to listen on port :80 for the challenge to assign a certificate.

That makes sense to me, however I tried disabling nesting, and changing the port listen to both: :8081 and <IP_ADDRESS>:8081, and neither let me start headscale properly.
I'm running a reverse proxy with it's own https certificate, so its strange to not be able to disable the feature on its own.
I imagine others will be running headscale in docker or LXC, so not sure if this falls out of the scope of the project or not.

For reference I've never had any issues binding to port 80 in any other containers. Is it the headscale user itself in the container that doesn't have the permissions? That wouldn't explain why port 8081 didn't work.

I run rootless, for example with podman.


Create showcase form prototype

Date of research: TBD
Type of research: Usability test with assistive technology
Research question: What accessibility barriers do people with disabilities encounter when they try to submit a form with the components and features implemented so far?
How prototype will be used in session

Participants will be asked to complete a realistic task using a form containing all of the components and features implemented so far, while explaining what they are doing and thinking
Participants will complete the form using non-sensitive information that they have access to
If they submit the form and there are errors, they will be asked to fix the errors and continue
On successful submission they will be sent to a confirmation page

Requirements

[ ] (Dev)On submission, (a) if there are errors, they are displayed along with the data entered (b) if/when there are no errors the data entered is deleted, not sent or retained
[ ] (PM and research) The showcase form contains content about a program or benefit with a neutral purpose that wouldn’t impact participants directly
[ ] The form contains the components and features listed below

Dependencies

[x] (Dev) Inline error messages appear on all fields when error is triggered https://app.zenhub.com/workspaces/gcforms-60cb8929764d71000e481cab/issues/cds-snc/platform-forms-client/503
[x] (Dev) Dynamic row updates implemented https://app.zenhub.com/workspaces/gcforms-60cb8929764d71000e481cab/issues/cds-snc/platform-forms-client/528
[ ] (PM?) Issue resolved: Error messaging content when using a screen reader https://app.zenhub.com/workspaces/gcforms-60cb8929764d71000e481cab/issues/cds-snc/platform-forms-client/424
[x] (Dev) Issue resolved: Error summary links in wrong order https://app.zenhub.com/workspaces/gcforms-60cb8929764d71000e481cab/issues/cds-snc/platform-forms-client/521
[ ] (Team lead, research) Confirm approach: Add sequential identifiers in front of form questions https://app.zenhub.com/workspaces/gcforms-60cb8929764d71000e481cab/issues/cds-snc/platform-forms-client/456

# Showcase form contains
Components

Form title (H1)
Section headings (H2)
Item labels (H3)
Descriptions/guide text (body text)
Radio buttons
Multi-select buttons
Required field validation
Short text field
Long text field
Document upload
Add a set of fields/delete a set of fields
Required field markers
Dropdown selection

Features/patterns

Confirmation page
Autofill properties
Error summary
Inline errors (not inline validation)
Syntax validation errors
Document upload
ReCAPTCHA

@sarahhobson is going to take on writing the content for a mock form to be prototyped


show timer in the macOS menubar

Is your feature request related to a problem? Please describe.
Pomatez have Always on top feature already.
but I wish I could check the timer on the menu bar.
Describe the solution you'd like

The picture above is an example of another app.

Hello @computerphilosopher . Sorry for the my very late response.
I've been so busy, so yeah.
That feature is awesome, I have tried to develop it myself before you suggested that and many of you also wanted that kind of feature, but the fact that this app is based on [ElectronJS] (https://www.electronjs.org/).
As of now, it is really near to impossible to develop that kind of functionality due to some limitations of the technology.
Maybe soon if the ElectronJS will provide a way for that. Thanks anyway.
Have a nice day.

@roldanjr
Thank you for your kind response.


ISO Datastores issues

The image is broken
I can't add a second ISO datastore

@dclarizio Are you aware of any issues here?  cc @h-kataria @gmcculloug

@bdunne Not aware, but get the log so we can see what the image name is that is it looking for.  Also hover the mouse over the disabled button to see if there is a reason displayed.

I checked upstream for this issue and was able to produce it .
Issue is not present in 5.5 build.

@bdunne is this issue is no longer relevant can you please close.


"Received unknown parameter: api_key" on Card.api_list()

How to reproduce:
c = Customer.objects.first()
Card.api_list(customer=c)

I don't know what's going on exactly here but it looks like it's passing api_key in the json body.
This is in stripe_objects.py in StripeCard.api_list:
        return customer.api_retrieve().sources.list(api_key=api_key, object="card", **clean_kwargs).auto_paging_iter()

Removing api_key=api_key fixes it.

I think the api_key argument was supposed to be passed to the api_retrieve() method rather.

Looks like it was added in 0919fd6c and somehow never hit.

Yeah this is definitely a bug; it's hard to catch because the calls to stripe are mocked.
Can you split this bugfix off from #414?


Release: checklist improvements during v0.9.0-alpha1 release

NOT READY FOR REVIEW - more changes likely to happen as we cut v0.9.0-alpha1 and update the checklist for next time.

Hi @stevenhorsman can you elaborate on your comment from here? Here's a link to our checklist for convenience. Are you suggesting we need a peer pods step between before step #3? Or before step #5? Or something else?

Hi @stevenhorsman can you elaborate on your comment from here? Here's a link to our checklist for convenience. Are you suggesting we need a peer pods step before step 3? Or before step 5? Or something else?

I would say before step 4 where peer pods is part of the artifacts to update (if required), like kata-containers and enclave-cc. Does that help?

@stevenhorsman It looks like this old "Step 8" from the checklist is what you're referring to? I can add this back in.
Also, what about the old "Step 22" from that same link? Are you wanting to cut the peer pods release along with the general coco release?

@stevenhorsman It looks like this old "Step 8" from the checklist is what you're referring to? I can add this back in.
Also, what about the old "Step 22" from that same link? Are you wanting to cut the peer pods release along with the general coco release?

So our plan is to slightly lead the coco operator release with peer pods, and be based on already release dependencies, so we should be aiming to do the whole CAA release process in one step of the CoCo release flow rather than separating out the release candidate/pre-release and release as separate steps. Does that make sense?

Thanks, @stevenhorsman. I updated per my understanding here. Let me know if that's wrong.

@stevenhorsman does this peer pods addition look OK now?

@stevenhorsman does this peer pods addition look OK now?

Yep, it looks good


Add all the remaining #define macros from predicates.c

The remaining arithmetic functions still need to be added but here I've added all the remaining #define macros.

To test them all properly, I rewrote the #define macros as functions in C so that we can get them through @ccall. I tested my conversions in C in macro_defs.c. I've pretty much never used C (only one other time for ~20 minutes before looking into this PR) so my C code is probably very rough.
I then test the Julia versions by comparing to the @ccall. For some reason the only one not exactly correct all the time is Two_Square. I don't know why exactly...

I restructured the code a bit to help organise it better when I later add the remaining functions.
(The point here being of course that I'm trying to get all the macros/arithmetic functions in and tested so I can port over the remaining predicates)

For some reason the only one not exactly correct all the time is Two_Square. I don't know why exactly...

Could be related to this comment

/* An expansion of length two can be squared more quickly than finding the   /
/   product of two different expansions of length two, and the result is    /
/   guaranteed to have no more than six (rather than eight) components.     */

in the code. Maybe my tests are breaking the expansion of length two assumption.

Actually, Two_Square isn't even used anywhere in predicates.c.. I'll just remove it. This is good to go.

Actually, Two_Square isn't even used anywhere in predicates.c.. I'll just remove it. This is good to go.

Fixed! #12 - it was a bug in the original code.


Erb not preprocessed

Erb in my scss.erb files is not processed. The reason seems to be that the file type is not detected correctly, due to the order that extensions appear here. The problem is resolved if I move the extensions involving erb higher, but maybe a better solution is to check if the file name ends with the extension, rather than includes it?

I see there is a pull request to do this, but with no issue attached


Call: The "Return to call" banner does not rotate with the device

The banner color should also follow the Vector color scheme

The current banner does not follow the expected design of the "Active Call" banner (see #500).
iOS will automatically rotate such banner.

Set hangup icon in pink red in the current room history


typical data length and train steps of the transformers?

Hi, thanks for the great work.
I have get reconstructed human voice from the trained SoundStream, but failed to get speech from the combined AudioLM (only electronic noise). And I guess my semantic and acoustic transformers may not get trained properly. I wonder what are the data_max_length and num_train_steps we should use to train the three transformers to get understandbale speech?

get in touch with @eonglints , as he had successfully trained the semantic transformer. not only that, but he is a young researcher in the field, who in my mind will eventually become an expert

you should update to the latest version and use data_max_length_seconds
as for num_train_steps,  the answer is for as long as possible without overfitting

you should update to the latest version and use data_max_length_seconds
as for num_train_steps, the answer is for as long as possible, with as much data as possible, without overfitting

Yeah, definitely more training steps will be better, but I wonder the lower bound of training steps to get intelligible speech with the acoustic transformers.

@cyanbx the lower bound would be at least one epoch over your entire dataset, and you need to have a dataset that is in the millions. for transformers, parameter count needs to be sufficient; estimate this should be at least 700 million - 2 billion range


Improves account and env view.  Closes: #278

🎯 Aim
The aim is to make account and enviroment views more bulletproof and properly display views when CLI command extecution gets rejected due to lack of permission
📷 Result

✅ What was done

[X] Added simple error handling to cover the reject case

🔗 Related issue
Closes: #278

ready to merge 🚀


New features to add

This is a list of features to add to have a better working bot:

[x] Create a better version of steps to setup the bot in the README
[X] Better error handling
[X] Custom status with total of available quests
[X] Black color for balancer quests

a few small changes otherwise lgtm


Update stable version in repo from 1.2.4 to 1.2.6

Think about update stable version to 1.2.6
Version: stable=1.2.4 (204 days old) => latest=1.2.6 (15 days old)
Installs: stable=2122 (74.33%), latest=536 (18.77%), total=2855
Click to edit

A kind reminder.
Is there any reason to delay an update of stable revision?
Feel free to drop a simple note if I should trigger an update.

A kind reminder.
Is there any reason to delay an update of stable revision?
Feel free to drop a simple note if I should trigger an update.
If there is no response within the next 2 weeks we might decide to update stable version anyway.

This issue seems to be outdated.
This issue suggests to update the stable version of this adapter to 1.2.6 but the current stable version is already 1.2.6.
So this issue should be closed.


ODB-16: Implement GIF Creator in Plotter

We can use this to create a gif out of plots

We can also export other types of files, from STLs to html. What do we want to target?


Stabilize failing e2e test

This is done by adding some more synchronisations before reading the DOM. It's important, after pressing a button, to first observe the "isSynced" value to flip to false, before flipping it to true. I believe sometimes it was possible for the waitUntil() to observe a true value before it got flipped to false, effectively not making the test wait long enough for the synchronisation to complete.
Hopefully this makes the E2E test a bit more stable! 🤞

Hopefully we don't need to allow even longer timeouts 🤞
Thanks for tackling this, for everyone's sanity!


TTLock API URLs broken

I think the urls for registering and creating an application have changed:
https://open.ttlock.com/register
https://open.ttlock.com/CreateApplication

s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
2022-03-01 00:34:43 - [ERROR] TTLOCK2MQTT: Error main method
Traceback (most recent call last):
File "/ttlock_adapter.py", line 326, in main
createClients(broker, port, broker_user, broker_pass,
File "/ttlock_adapter.py", line 306, in createClients
for gateway in ttlock.get_gateway_generator():
File "/usr/local/lib/python3.9/site-packages/ttlockwrapper/ttlock.py", line 99, in get_gateway_generator
_response = TTLock.send_request(_url_request).json()
File "/usr/local/lib/python3.9/site-packages/ttlockwrapper/ttlock.py", line 28, in send_request
raise TTlockAPIError(error_code=_response.json().get(ERROR_CODE_FIELD),menssage=_response.json().get(MENSSAGE_FIELD))
ttlockwrapper.ttlock.TTlockAPIError: Error returned from TTlockAPI: Error_code 10004 - invalid grant

In this case, It is a error with your token. See this:
https://open.ttlock.com/doc/api/error

Can you help me with token refresh?  Write for me the command line and i
will fill it with my refresh token and post it please
On Tue, 1 Mar 2022, 2:56 am ANTONIO CAMPOS, @.***>
wrote:

In this case, It is a error with your token. See this:
https://open.ttlock.com/doc/api/error
—
Reply to this email directly, view it on GitHub
https://github.com/tonyldo/ttlockio/issues/5#issuecomment-1054826783,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AO3B3TAU2MABU72ADML2WZ3U5QDSHANCNFSM5GDX6QXA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.Message ID:
@.***>

solved it thank you

closed!

@tammeryousef1006 How did you solved that error 10004 invalid grant?
Can you please elaborate on the solution steps.

@tammeryousef1006 How did you solved that error 10004 invalid grant?
Can you please elaborate on the solution steps.

i generate a new refresh token , because old one keeps expiring every 180 days as i remember , now there is new integration via hacs and more easier to setup , try to search it over hacs


Support soname for cdylibs

rustc supports setting soname via -C link-arg. However, it can't be used from Cargo, since RUSTFLAGS affects all invocations of the compiler, and it could potentially set soname on dependencies.
Some previous discussions about soname support were dismissed based on the fact that Rust's native ABI is not stable. That is not relevant for cdylibs, because the C ABI exposed by cdylibs is stable.
I'm interested in using this feature in cargo-deb. soname is required to build first-class Linux libraries (e.g. for Debian) with Rust.
I think it'd be wonderful if Cargo automatically set soname of cdylib to semver-major when version is >= 1.0.0 (i.e. don't set any for 0.x.x), since soname and semver-major promise basically the same thing. However, a separate Cargo.toml field, command line flag, or env var would work as well.

The lack of support for linker flags is one of issues preventing librsvg from switching to Cargo. It needs flags like this:
	-version-info @RSVG_LT_VERSION_INFO@ \
	-export-dynamic \
	-no-undefined \
	-export-symbols-regex "^rsvg_.*"

Those are all libtool flags and not direct linker flags that ld or link.exe would handle.

Ah, ok. Still needs post build script or something.

@kornelski I'm updating my patch, then we can work on the installing phase together if you like :)
I need it already for crav1e and the relibc developer seem interested as well.

From !6298, am I correct in understanding that the remaining work is to figure out platform-specific linker arguments to define the soname and such?

The install phase rfc and this have more details on what is missing.
I might take this weekend to publish my draft applet so we can experiment a bit outside cargo if you want to join me in this :)

But this is about cargo build, not cargo install, so the RFC won't help.

What I'm preparing is something along the lines of:
cargo c install --prefix=/usr --destdir=/staging/place

But isn't that a workaround? It reminds me of ugly hacks needed for make install. The products are already in target/, they're just built wrong.

It is not.
If you want to build only you just issue a build command.
As a packager I enjoy having a working install target that gets all I need in the right places without having to reinvent the wheel every time. Nobody is forcing you to use what I'm writing :)

Oh, you mean you're writing "cargo-c"? I assumed that c was a typo, and you were suggesting cargo install as the workaround (and that RFC goes way beyond staging build products, into making cargo install a package manger that can't uninstall what it has installed, so I'm very dismayed by it).

yes, I try to make an applet to generate all that's needed (.pc files, .h files, etc) and install it without to have to repeat myself too much (currently we are having a small vlc workshop so I might or might not get to publish it this weekend)

Now I have two ways to help on this:

https://crates.io/crates/cdylib-link-lines if you want just to use build.rs and just build the .so
https://github.com/lu-zero/cargo-c if you want to build and install a C-lib-like package.

Ideally I could make a separate crate for the .pc creation as well if somebody needs it.

new to rust/cargo: would there be a possibility to write a plugin that does set the soname as post-production step? (yes, it is a workaround until mainline can do it).
Right now I try to do the same on the side consuming the .so

it is, you may using cdylib-link-lines (even if it could enjoy an overhaul).

I am facing exactly this issue when trying to use Rust-based libraries (i.e. I used the two Rust-based WebAssembly engines Wasmtime and Wasmer) in a C/C++ code-base.
These Rust libraries have no SONAMES, which causes the CMake build to produce wrong binaries.
I opened an issue at CMake, but these folks clearly confirmed that shared libraries without an SONAME entry are a bug that needs to be fixed by the one building the library:
https://gitlab.kitware.com/cmake/cmake/-/issues/22307#note_971562
Could you please continue working on this topic? Otherwise consuming Rust-based libraries with the popular CMake build system will remain awkward.

You can use cargo-c for your use-case I think.

Interested in the same, with also an Android context.
Because of Android support, we're also already using cargo-ndk.
As a workaround, how to use cargo-ndk and cargo-c together ? Any idea would be appreciated.

Ideally you might get around setting the CARGO to cargo capi if cargo-ndk calls normally cargo build cargo install or extend a little cargo-ndk to know about cargo-c and call it instead of cargo if present.
For android you shouldn't have problems not using cargo-c for it.

Out of curious. What's the missing part to make progress on this issue?
From my understanding, rustc-link-arg family in build script solve this issue somehow. We could also simply run something like the following to build a shared library with SONAME:
cargo rustc --crate-type cdylib -- -C link-arg=-Wl,-soname,libmycrate.so

Sorry I am a bit lost on this thread…

What's the missing part to make progress on this issue?

For me, it's this part from the opening post (emphasis mine):

I think it'd be wonderful if Cargo automatically set soname of cdylib to semver-major when version is >= 1.0.0 (i.e. don't set any for 0.x.x), since soname and semver-major promise basically the same thing. However, a separate Cargo.toml field, command line flag, or env var would work as well.

So what's missing from my point of view is a decision if cargo could automatically set the soname for cdylibs according to semver, or at least provide an opt-in mechanism for this, which is a bit more user-friendly than setting linker flags.

Another argument for having Cargo set the DT_SONAME: Only Cargo knows
it is linking the final binary and not some dependency. Here’s an
example where the build.rs approach fails: https://gitlab.com/phgsng/buggy-soname
I also outlined the problem on discourse: https://users.rust-lang.org/t/89245
The gist of it is that one library that is built as a cdylib
depends on another which also produces a cdylib. This causes the
build.rs of both libraries to be executed and Cargo ends up
appending the two extra link-args but in the wrong order, so the
wrong SONAME ends up in the shared object. Ideally, Cargo would add
the correct SONAME argument to the linker line exactly once, when
linking the final shared object.
(This is not a contrived usecase but based on a real world product that
is unfortunately proprietary.)

See also

https://github.com/rust-lang/cargo/issues/2273


Brier Score - References in API & Tutorial

The reference in the Brier Score API is for the Wikipedia page: https://en.wikipedia.org/wiki/Brier_score.
The reference in the tutorial and included.md is Brier (1950), for which the DOI is - https://doi.org/10.1175/1520-0493(1950)078<0001:VOFEIT>2.0.CO;2

API: Should the Brier Score API list both the Wikipedia page and Brier (1950) references?
Tutorial: The Brier Score reference in the tutorial is hyperlinked to a citeseerx version of the article. I have sometimes come across citeseerx URLs that stop resolving. There is a DOI (listed above, and linked to in included.md) for Brier (1950) - which includes a freely available, full text PDF version of the article. I think it would be better to change the link in the tutorial to the DOI.
Tutorial: If anybody is worried people will have trouble finding the full text PDF at the DOI, you could include a note saying to click one of the PDF buttons

(1) The wikipedia entry is much more accessible to quickly get across the score. We could do with a consistent "spec" for the docstrings which will generally answer what should be in there. My feeling is that we should have both references in the API docstring.
(2) Yes, this should be changed to the DOI.
(3). I'm not worried about that, it seemed quite clear how to access the PDF, but if anyone disagrees please say so.
@Steph-Chong I'd be interested in your take on point 1. I'm happy to go ahead and make the change, but I wonder if I should create an issue for putting together a "spec" or template reference for the docstrings and we can then move towards a standard approach to the sections of docstrings.

I think a spec for docstrings would be great (it is actually something I had been thinking about).
We've refined our approach to docstrings over time, and I think they have gotten better as a result. But it does mean the docstrings in the API are currently a bit inconsistent.
I think a spec would (a) be useful for new contributors and (b) over time we could (where necessary) update existing docstrings to match.
I think it is probably worth adding it to the pull request checklist - as contributors should be looking at that as part of making a PR. It could additionally be added to the contributing guide (but that document is already very long).


mpd: add module

Music player daemon. A lot borrowed from the nixos service, with the paths and unit file modified.

Cool. Yeah I wasn't really sure what the defaultText was :sweat_smile: , I just thought, like, an example.... Also thanks for the mkdir tip :joy:
Also added the news entry

Nice, thanks a lot for the improvements! I have rebased the module into master in d3871ed77447fdebe3673b69df7d75589378c53b. I made some slight changes in a few option descriptions. For example, instead of
<literal>man 5 mpd.conf</literal>

I put a full docbook style reference to the option, i.e.,
<citerefentry>
  <refentrytitle>mpd.conf</refentrytitle>
  <manvolnum>5</manvolnum>
</citerefentry>

Awesome, thanks!


Add keep fan always on option for slic3r

"Keep fan always on" is a useful slic3r option.  It's a checkbox.

Thanks.


make "tags" to be array like "tags" in grok filter

This pull request will make json filter to be the same as "tags" in grok filter, which fix this situation:
{
     "tags" => "_jsonparsefailure_grokparsefailure",
     "@version" => "1",
     "@timestamp" => "2015-04-13T09:06:48.887Z",
     ...
}

if _jsonparsefailure and _grokparsefailure occur in the same time , the correct output will be:
{
     "tags" => [
         [0] "_jsonparsefailure",
         [1] "_grokparsefailure"
     ],
     "@version" => "1",
     "@timestamp" => "2015-04-13T09:06:48.887Z",
     ...
}

@garyelephant thanks for the change. can you add specs please?

@suyograo ok , where should I put the test code and can you give me a simple test example ?

@garyelephant check this https://github.com/logstash-plugins/logstash-filter-json/blob/master/spec/filters/json_spec.rb

also can you please perform step 2 of https://github.com/elasticsearch/logstash/blob/master/CONTRIBUTING.md#contribution-steps

ok ,I will do it later soon.
On Sat, Apr 18, 2015 at 2:36 AM, Suyog Rao<EMAIL_ADDRESS>wrote:

also can you please perform step 2 of
https://github.com/elasticsearch/logstash/blob/master/CONTRIBUTING.md#contribution-steps
—
Reply to this email directly or view it on GitHub
https://github.com/logstash-plugins/logstash-filter-json/pull/6#issuecomment-94047768
.

I added this https://github.com/garyelephant/logstash-filter-json/pull/1 PR to help add some test to this PR. @garyelephant please review and merge if this helps you with the testing :-)

Many thanks to @purbon.
@suyograo tests are added, please check.

Cool, happy to help @garyelephant, next time you know how to add more test for filters :-) .... could you also bump the version in the gemspec file + rebase your PR ? then I'm happy to merge this change in.
Thanks for your contribution.

@purbon I've rebased the PR, should I bump the version to 0.1.6 ?

yes please.

@purbon done

@suyograo I will add tests for logstash-codec-json and logstash-codec-json_lines soon.

@garyelephant rebase?

@suyograo did I do something wrong ? which commit should I rebase ?

@garyelephant Is not strictly necessary, however sometimes the PR's get outdated vs the master branch, this is the case of this PR it happen (you will see if you update your master branch and rebase your PR vs master), so you will see some merge conflicts.
If you do so, automatic merge is possible.
Thanks!

@garyelephant ping..rebase?

would like to get this for the next RC

@suyograo sorry about the delay, I've rebase the patch-1

@garyelephant thanks! we'll merge this in soon :) I left some comments on your other PR's :)

LGTM


Update sql-data-warehouse-partner-data-integration.md

@jrowlandjones Last batch of updates.  Please advise.

@msebolt : Thanks for your contribution! The author, @jrowlandjones, has been notified to review your proposed change.

#sign-off

@ktoliver : Thanks for your contribution! The author, @jrowlandjones, has been notified to review your proposed change.


[libsass] Build error

Package: libsass:x64-linux -> 3.6.5#1
Host Environment

Host: x64-linux
Compiler: GNU 7.5.0
vcpkg-tool version: 2023-09-15-ac02a9f660977426b8ec6392919fbb1d51b10998
vcpkg-scripts version: fc71abb23 2023-11-20 (43 minutes ago)

To Reproduce
vcpkg install
Failure logs
-- Using cached sass-libsass-3.6.5.tar.gz.
-- Cleaning sources at /home/deepvision/source/repos/vcpkg/buildtrees/libsass/src/3.6.5-b48f56cd20.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source /home/deepvision/source/repos/vcpkg/downloads/sass-libsass-3.6.5.tar.gz
-- Applying patch remove_compiler_flags.patch
-- Using source at /home/deepvision/source/repos/vcpkg/buildtrees/libsass/src/3.6.5-b48f56cd20.clean
-- Getting CMake variables for x64-linux-dbg
-- Getting CMake variables for x64-linux-rel
-- Generating configure for x64-linux
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:112 (message):
    Command failed: /usr/bin/autoreconf -vfi
    Working Directory: /home/deepvision/source/repos/vcpkg/buildtrees/libsass/src/3.6.5-b48f56cd20.clean/
    Error code: 1
    See logs for more information:
      /home/deepvision/source/repos/vcpkg/buildtrees/libsass/autoconf-x64-linux-err.log

Call Stack (most recent call first):
  scripts/cmake/vcpkg_configure_make.cmake:629 (vcpkg_execute_required_process)
  buildtrees/versioning_/versions/libsass/9f688f8a8026f1078f224e7bcc4eef8fc21561a2/portfile.cmake:10 (vcpkg_configure_make)
  scripts/ports.cmake:168 (include)

/home/deepvision/source/repos/vcpkg/buildtrees/libsass/autoconf-x64-linux-err.log
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal --force
autoreconf: configure.ac: tracing
autoreconf: configure.ac: not using Libtool
autoreconf: running: /usr/bin/autoconf --force
autoreconf: running: /usr/bin/autoheader --force
autoreconf: running: automake --add-missing --copy --force-missing
configure.ac:30: installing 'script/ar-lib'
configure.ac:19: installing 'script/compile'
configure.ac:15: installing 'script/install-sh'
configure.ac:15: installing 'script/missing'
GNUmakefile.am:37: warning: source file '$(SASS_SASSC_PATH)/sassc.c' is in a subdirectory,
GNUmakefile.am:37: but option 'subdir-objects' is disabled
automake: warning: possible forward-incompatibility.
automake: At least a source file is in a subdirectory, but the 'subdir-objects'
automake: automake option hasn't been enabled.  For now, the corresponding output
automake: object file(s) will be placed in the top-level directory.  However,
automake: this behaviour will change in future Automake versions: they will
automake: unconditionally cause object files to be placed in the same subdirectory
automake: of the corresponding sources.
automake: You are advised to start using 'subdir-objects' option throughout your
automake: project, to avoid future incompatibilities.
GNUmakefile.am: installing 'script/depcomp'
parallel-tests: installing 'script/test-driver'
src/GNUmakefile.am:27: error: Libtool library used but 'LIBTOOL' is undefined
src/GNUmakefile.am:27:   The usual way to define 'LIBTOOL' is to add 'LT_INIT'
src/GNUmakefile.am:27:   to 'configure.ac' and run 'aclocal' and 'autoconf' again.
src/GNUmakefile.am:27:   If 'LT_INIT' is in 'configure.ac', make sure
src/GNUmakefile.am:27:   its definition is in aclocal's search path.
Makefile.conf:92: warning: source file 'memory/allocator.cpp' is in a subdirectory,
Makefile.conf:92: but option 'subdir-objects' is disabled
src/GNUmakefile.am:29:   'Makefile.conf' included from here
Makefile.conf:92: warning: source file 'memory/shared_ptr.cpp' is in a subdirectory,
Makefile.conf:92: but option 'subdir-objects' is disabled
src/GNUmakefile.am:29:   'Makefile.conf' included from here
autoreconf: automake failed with exit status: 1

**Additional context**
vcpkg.json
{
  "name": "dv-app-solution",
  "version": "1.0.2",
  "dependencies": [
    "dv-camera",
    "rc-genicam-api",
    "minizip",
    "catch2",
    "range-v3",
    "fmt",
    "boost-thread",
    "boost-context",
    "boost-system",
    "boost-asio",
    "opencv4",
    "zlog"
  ],
  "builtin-baseline": "fc71abb23680c40d36ddbdb36a3e595c4e5a9b8d",
  "overrides": [
    {
      "name": "boost",
      "version": "1.83.0"
    },
    {
      "name": "opencv4",
      "version": "4.5.5#7"
    },
    {
      "name": "catch2",
      "version": "3.4.0"
    }
  ]
}

@nocanstillbb, Thanks for posting this issue, I use the vcpkg.json you provide get this error:
root@test:~/vcpkg# ./vcpkg install
A suitable version of cmake was not found (required v3.27.1) Downloading portable cmake 3.27.1...
Downloading cmake...
https://github.com/Kitware/CMake/releases/download/v3.27.1/cmake-3.27.1-linux-x86_64.tar.gz->/root/vcpkg/downloads/cmake-3.27.1-linux-x86_64.tar.gz
Extracting cmake...
error: while checking out baseline from commit 'fc71abb23680c40d36ddbdb36a3e595c4e5a9b8d', failed to `git show` versions/baseline.json. This may be fixed by fetching commits with `git fetch`.
error: git failed with exit code: (128).
fatal: path 'versions/baseline.json' exists on disk, but not in 'fc71abb23680c40d36ddbdb36a3e595c4e5a9b8d'
while checking out baseline fc71abb23680c40d36ddbdb36a3e595c4e5a9b8d

And my vcpkg-tool version: 2023-10-18-27de5b69dac4b6fe8259d283cd4011e6d20a84ce
Please use the latest  vcpkg-tool and try again.

@nocanstillbb, Thanks for posting this issue, I use the vcpkg.json you provide get this error:
root@test:~/vcpkg# ./vcpkg install
A suitable version of cmake was not found (required v3.27.1) Downloading portable cmake 3.27.1...
Downloading cmake...
https://github.com/Kitware/CMake/releases/download/v3.27.1/cmake-3.27.1-linux-x86_64.tar.gz->/root/vcpkg/downloads/cmake-3.27.1-linux-x86_64.tar.gz
Extracting cmake...
error: while checking out baseline from commit 'fc71abb23680c40d36ddbdb36a3e595c4e5a9b8d', failed to `git show` versions/baseline.json. This may be fixed by fetching commits with `git fetch`.
error: git failed with exit code: (128).
fatal: path 'versions/baseline.json' exists on disk, but not in 'fc71abb23680c40d36ddbdb36a3e595c4e5a9b8d'
while checking out baseline fc71abb23680c40d36ddbdb36a3e595c4e5a9b8d

And my vcpkg-tool version: 2023-10-18-27de5b69dac4b6fe8259d283cd4011e6d20a84ce
Please use the latest vcpkg-tool and try again.

i am sorry, i forgot to tell that this version is our prvate registry's version
the real version is 0c20b2a97c390e106150837042d921b0939e7ecb

Please use the latest vcpkg-tool and try again.
vcpkg-tool version: 2023-09-15-ac02a9f660977426b8ec6392919fbb1d51b10998

root@test:~/vcpkg# ./vcpkg install
error: the baseline does not contain an entry for port dv-camera
error: the baseline does not contain an entry for port rc-genicam-api
error: the baseline does not contain an entry for port zlog

Try install libtool first:
sudo apt-get install libtool
src/GNUmakefile.am:27: error: Libtool library used but 'LIBTOOL' is undefined

since  build succuss after sudo apt-get install libtool
close this issure
thanks


Handle case-insensitive sensitive headers

fix for #673

Hi @albertyw,
I have made some improvements to the handling of sensitive headers in the RequestModelFactory.encoded_headers method.
Could you please take a moment to review the changes ?
Thanks!

@albertyw,  I appreciate the merge 😊
Could you please let me know when the new version is scheduled?

New version will be released with #678


[$500] Attachment – The corrupted PDF can be downloaded, but no download indication is displayed

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: v1.4.5-3
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause-Internal Team
Slack conversation: @
Action Performed:

Go to https://staging.new.expensify.com/
Log in with any Gmail account.
On a conversation, click on the + button in the compose box
Click on add attachment
Upload the following corrupted PDF
Verify that Failed to load PDF file. message appears when previewing a corrupt PDF file
Click on send.
Click on “Failed to load PDF file.”

Expected Result:
The corrupted file should have the same preview component and download component as .mp4/docs.
Actual Result:
The corrupted PDF can be downloaded by clicking on it, but no download indication is displayed.
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[x] Android: mWeb Chrome
[ ] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
https://github.com/Expensify/App/assets/115492554/dee95e1a-5a73-4526-b828-eafb04df47c0
Corrupted PDF.pdf

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01a226f1589481a1b1
Upwork Job ID:<PHONE_NUMBER>011929088
Last Price Increase: 2023-11-29

Proposal
Please re-state the problem that we are trying to solve in this issue.
Attachment – The corrupted PDF can be downloaded, but no download indication is displayed
What is the root cause of that problem?
The main problem is that since we are using the onPress function by default
https://github.com/Expensify/App/blob/a0b219711080751d6826bb2330ddd85c1641d7bf/src/components/PDFView/index.js#L328-L337
What changes do you think we should make in order to solve the problem?
Since we clearly have no information that our file is broken
We can obtain this information using a special method onLoadError
https://github.com/Expensify/App/blob/a0b219711080751d6826bb2330ddd85c1641d7bf/src/components/PDFView/index.js#L286-L297
What alternative solutions did you explore? (Optional)
NA (edited)

Please re-state the problem that we are trying to solve in this issue.
The corrupted PDF can be downloaded, but no download indication is displayed
What is the root cause of that problem?
We are using PressableWithoutFeedback component even before PDF is loaded or failed to load in ~/PDFView/index.js.
render() {
        return this.props.onPress ? (
            <PressableWithoutFeedback
                onPress={this.props.onPress}

What changes do you think we should make in order to solve the problem?
We can use the available state 'failedToLoadPDF' as an additional condition before using the PassibleWithoutFeedback component. Currently, the 'faileToLoadPDF' state is being set to false given that the pdf failed to load. We can utilize this and make a minimal change to solve this issue.
render() {
        return this.props.onPress && !this.state.failedToLoadPDF ? (
            <PressableWithoutFeedback
                onPress={this.props.onPress}

This should only enable the download onClick when the PDF is loaded properly, utilizing the 'failedtoLoadPDF' state.

Contributor details
Your Expensify account email<EMAIL_ADDRESS>Upwork Profile Link: https://www.upwork.com/freelancers/~0125eea53463402da3

@akinwale - When you have some time we have some proposals.

@ishpaul777 yeah it looks like your proposal was made slightly earlier and sorta solves this issue too. I do like @tienifr proposal showing a cross with failed to load PDF file but i think that visual change might be a different issue. I like solving for displaying the corrupted PDT and having a download indication which you @ishpaul777 seem to solve too.
Thoughts on closing this issue in favor for https://github.com/Expensify/App/issues/32109 since it looks like the proposal there should solve this issue too right, @akinwale @parasharrajat, or am i missing something here?

@parasharrajat sure i dont mind keep the separate but can you explain why you think they are separate. Doesn't @ishpaul777 proposal solve the expected solution mentioned here,

Expected Result:
The corrupted file should have the same preview component and download component as .mp4/docs.

Updated title to reflect the Hold state.

No update yet.

Hmmm, all good here Melvin, on hold still.

Hold GH is open, all good here Melvin.

Still on Hold. All good for now.

Still on hold.

Hold GH is still open.

HOLD GH still open.

HOLD Gh still open.

Hold GH looks like it's going to move forward soon as we've decided on the behavior.

HOLD GH is still open, pausing here.

still on hold

HOLD GH is still open.

Looks like the linked GH issue is closed. @akinwale @parasharrajat @strepanier03, can someone test and confirm if this issue still exists. Also can someone confirm if this is an internal or external issue.


[FEATURE] Limit the guilds impacted by the local version of Sonia

Is your feature request related to a problem? Please describe.
Too much spam is coming from Sonia when using the local prod version.
Describe the solution you'd like
Limit the impacted guilds locally.

My bad, I already provided this feature 😆


8f02c525-52c2-422a-bebe-0ce23765f8aa

this is for automated testing

59891b51-c5b8-47e2-a55e-ae96a2146015


Online Appendix?

I was looking for the "intuitive introduction" on SVD. In the footnote 6 at page 277 of the book, it refers to an online appendix available at the book's website.
I was unable to find it.

I have added the file to the repository -- see the README. Thanks for pointing this out, we omitted to upload the file.


Bad usage of ample filter

Describe the bug
Filtering was added to ample in #3968. There is logic to prevent TabletsMetadata.filter() and TabletsMetadata.checkConsistency() from being used in the same call. There is a spot in the code where both are used which will cause an exception to be thrown:
https://github.com/apache/accumulo/blob/7e8f9d3b4a1a2a53d1d880623e01de6a16aac63b/server/gc/src/main/java/org/apache/accumulo/gc/GarbageCollectWriteAheadLogs.java#L80-L93
And the check:
https://github.com/apache/accumulo/blob/7e8f9d3b4a1a2a53d1d880623e01de6a16aac63b/core/src/main/java/org/apache/accumulo/core/metadata/schema/TabletsMetadata.java#L125-L134
Versions (OS, Maven, Java, and others, as appropriate):

Affected version(s) of this project: elasticity

We need to remove either filter or checkConsistency in this instance.

Fixed via #4140


Try new Travis CI setup (again)

Giving this another shot now that something is moving on https://github.com/travis-ci/travis-ci/issues/7752 again.

CI failure due to https://github.com/lwm/tasty-discover/issues/119, otherwise, all good!


Vault data combined with local data gives error

Task Description
Used the master coinstac latest code. Created consortia, added Trends VBM vault, made myself(spanta) also as active user and mapped local data with common covariates from the vault and local data. Made sure the covariates for both vault and local data are in same datatype format. Ran regression VBM and it gave this error. Tried the same with CMI VBM vault as well and it gave same error. Name of the consortia's if you want to look at the pipeline setup. Tagging @pixelsaurus if you have any comments on the pipeline setup:
TrendsVault_local_vbm
CMIVault_vbm_local
This was not the case before, so I am not sure if there is a code difference between VBM Vault and regular VBM regression that is leading to this or something. Need this for Vault's paper results:
Results Object:
null
*Output Type not defined in Compspec.
Pipeline error from central node Error details: Computation failed with exitcode 1 and stderr Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/coinstac/init.py", line 23, in _func output = await _asyncio.get_event_loop().run_in_executor(None, remote, msg['data']) File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run result = self.fn(*self.args, **self.kwargs) File "/computation/scripts/remote.py", line 265, in start return remote_0(PARAM_DICT) File "/computation/scripts/remote.py", line 43, in remote_0 covar_keys, unique_count = return_uniques_and_counts(df) File "/computation/scripts/remote_ancillary.py", line 29, in return_uniques_and_counts flat_list = [item for sublist in row for item in sublist] File "/computation/scripts/remote_ancillary.py", line 29, in  flat_list = [item for sublist in row for item in sublist] TypeError: 'float' object is not iterable
Error: Computation failed with exitcode 1 and stderr Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/coinstac/init.py", line 23, in _func output = await _asyncio.get_event_loop().run_in_executor(None, remote, msg['data']) File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run result = self.fn(*self.args, **self.kwargs) File "/computation/scripts/remote.py", line 265, in start return remote_0(PARAM_DICT) File "/computation/scripts/remote.py", line 43, in remote_0 covar_keys, unique_count = return_uniques_and_counts(df) File "/computation/scripts/remote_ancillary.py", line 29, in return_uniques_and_counts flat_list = [item for sublist in row for item in sublist] File "/computation/scripts/remote_ancillary.py", line 29, in  flat_list = [item for sublist in row for item in sublist] TypeError: 'float' object is not iterable at /usr/local/src/coinstac/packages/coinstac-manager/src/services/serviceFunction.js:258:21 at runMicrotasks () at processTicksAndRejections (node:internal/process/task_queues:96:5)

@hvgazula any thoughts here? Please reply at your available time, I don't mean to flood you on a consistent basis. I think once we get through these core features implementation and have the new GRA working , wee can have him do improvements.