Unable to perform a multipart PUT

For some reason uploading a file via a PUT request does not seem to work.
Http post works as expected:
Typhoeus.post("example.com/upload",
  body: {
    foo: [],
    file: File.open(upload, "r")
  },
  headers: { Authorization: "token" }
)

result:
POST /upload HTTP/1.1
Host: example.com
Accept: */*
User-Agent: Typhoeus - https://github.com/typhoeus/typhoeus
Authorization: token
Content-Length: 662
Expect: 100-continue
Content-Type: multipart/form-data; boundary=----------------------------62c3887bcd8c

While http put does not:
Typhoeus.put("example.com/upload",
  body: {
    foo: [],
    file: File.open(upload, "r")
  },
  headers: { Authorization: "token" }
)

result:
PUT /upload HTTP/1.1
Host: example.com
Accept: */*
User-Agent: Typhoeus - https://github.com/typhoeus/typhoeus
Authorization: token
Content-Length: 120
Expect: 100-continue

As can be seen above the Content-type: multipart/from-data and boundary headers are missing.

We are having issues with this as well.  Even when we set the content type to multipart/form-data the file field we are sending across just comes across as an array:
This is what we are calling:
Typhoeus.put('http://example.com',
  headers: {
    "content-type"=>"multipart/form-data"
  },
  body: {
    article: {
      title: "test",
      body:  "
test
\r\n",
      banner_image: #<File:/tmp/unnamed.jpg>
    }
  }
)

On the other side this is what we are getting:
"banner_image"=> "[\"unnamed.jpg\", \"image/jpeg\", \"/tmp/unnamed.jpg\"]"

I'll see about setting up a simple client / server repo that can reproduce the problem.

Ok, here is a repo that demonstrates the issue:
https://github.com/nick-desteffen/typhoeus-put-file

@nick-desteffen thanks for reporting! I am sorry you are having trouble with that. I don't have much time these days and it would be very much appreciated if anyone wants to take a stab at it.

I suspect the issue is in the ethon gem, I'm not very familiar with it though.  I can take a stab at it sometime over the next week.

yes. you can start digging here: https://github.com/typhoeus/ethon/blob/e2300cb201e3374c8cffca1b272d62dbda4f8d41/lib/ethon/easy/queryable.rb#L77-L84.

Ok, I did some digging, I don't think the queryable#file_info is the problem, it works the same for both PUT and POST requests.
I'm not sure why these are so different:
https://github.com/typhoeus/ethon/blob/master/lib/ethon/easy/http/putable.rb#L14-L20
https://github.com/typhoeus/ethon/blob/master/lib/ethon/easy/http/postable.rb#L15-L27

@nick-desteffen I think you found an interesting piece of code. thats the implementation for put and post according to the libcurl docs: http://curl.haxx.se/libcurl/c/CURLOPT_UPLOAD.html and http://curl.haxx.se/libcurl/c/CURLOPT_POST.html.

Any updates on this? I want to switch to typheous/excon, but this is a blocker for our use case.

AFAIK the problem still exists.  We are using Typhoeus to submit to a Rails application, so we just submitted the request as a POST with the method parameter as PUT for a workaround since Rails will take that into consideration for the routing.

Hi @i0rek, is there have any updates on this? Or any alternative solution? I also have the same issue now. Thanks!

Hi,
I am also facing this problem.

AFAIK the problem still exists. We are using Typhoeus to submit to a Rails application, so we just submitted the request as a POST with the method parameter as PUT for a workaround since Rails will take that into consideration for the routing.

@nick-desteffen how do you fake the request? I'm facing exactly the same issue, but I'm not finding a way to use that workaround

If you are using Ruby on Rails, you can override the HTTP method in it's router.
If you do this:
params = {
  foo: 'bar'
}
params[:_method] = 'PUT'
Typhoeus.post(url, body: params)

And have a route defined against a PUT method, it will get routed correctly.  It is an old hack to support legacy browsers that don't support anything other than POST and GET requests.

For more info, see: http://guides.rubyonrails.org/form_helpers.html#how-do-forms-with-patch-put-or-delete-methods-work-questionmark

Thank you very much @nick-desteffen
It worked as expected

Just to be sure: since 2014 there's no bugfix or workaround for this, right?
Or does anyone have a hint for non-Rails APIs?


req_not_found when attaching

I'm not sure if anything changed but at least now when I try to attach to the container I get the following error:
{<0.1104.0>,{error,req_not_found}}
I have a gen_server that creates/starts a container and then tries to attach to it for monitoring.
Create and start work fine, then I call the attach_stream_with_logs:
handle_cast(monitor, #container{id=CID}=State) ->
    docker_container:attach_stream_with_logs(CID),
    {noreply, State};

In my log output I see this:
17:45:16.688 UTC [info] api call: {post,stream} http+unix://%2Fvar%2Frun%2Fdocker.sock/containers/545f5f3e1f54bbd19a98bf2a2eadc079666802b4059a457573e2406c433b496a/attach?stream=true&logs=true&stdout=true&stderr=true
CAUGHT EXIT PID = <0.1104.0>, Self = <0.1088.0>, normal
17:45:16.751 UTC [info] Received {<0.1104.0>,{error,req_not_found}}

The caught exit is in the same gen_server:
handle_info({'EXIT', _Pid, Reason}, #container{service=Service,
					   restart_counter = Counter
					  } = State) ->
    case _Pid == self() of
	false ->
	    io:format("CAUGHT EXIT PID = ~p, Self = ~p, ~p~n", [_Pid, self(), Reason]),
	    {noreply, State};
.......

and the received line is from another handle_info:
handle_info(_Info, State) ->
    lager:info("Received ~p~n", [_Info]),
    {noreply, State}.

the req_not_found message is from Hackney but I don't know why that would be, if I check the state of the hackney_manager I see that the ref is there.
Ways to reproduce:

docker pull nginx (just for testing)
clone VEO git clone https://github.com/nisbus/veo
checkout api branch git checkout api
run make
in the erlang shell run:

[H|[H1|_]] = settings:get_applications().
container_sup:add_service(H1).

You should now see the issue although sometimes I also see checkout_timeout for various operations (which I've "solved" by setting the recv_timeout = infinity in the erldocker_api OPTIONS).
Any help on this would be appreciated (or pointers to how I can fix it and contribute).
Thanks

It seems the issue was just hackney configs for the pool, since the streaming methods shouldn't close connections and the config was set to 1 connection only.


Migrate armeria-zipkin to brave 4.5.1

Motivation:
Brave 4.3+ introduced a brand new instrumentation API which is much easier to use. Recently, brave's instrumentation libraries were also updated to use the new API, so it makes sense to update armeria as well to keep up.
Implementation tips are cribbed from:
https://github.com/openzipkin/brave/tree/master/instrumentation/grpc/src/main/java/brave/grpc
Result:
Updated to latest Brave and much less code.
Also removes the abstract tracing classes since armeria is HTTP-only.

I looked a bit more at some brave instrumenters and found TraceKeys and Constants defining some standard annotations so I've migrated us to the standard ones. In doing so, I have removed http method from the uri as it's a separate annotation now, and I left rpc method name as the span name without duplicating it as the uri fragment.
This is highly breaking though - I do think we should use the standard zipkin keys but let me know if we should still add the old ones too as duplicates to help with migration. The keys are sometimes used for issuing queries from zipkin UI.
Also short-circuit the decorators for no-op spans as an optimization (unlike previous brave, it wouldn't really cause errors to not to do since the spans literally are no-op, as opposed to null, but it does waste processing for no reason).

I initially thought test flakiness here might be because brave is finishing the spans asynchronously, but checked the code and it's not so just general slowness I guess. I raised the test timeouts a little instead.

This is highly breaking though, not just of API but of data model

I'm not entirely sure about the result of this. Does this mean we have to update our span collecting backends? /cc @imasahiro @synk

Also short-circuited the decorators for no-op spans as an optimization

SGTM

The annotations are stored as is, as a map essentially, so don't need to update collectors. But they can be used when querying in the ui which would get complicated when querying across a key change.
But in practice I think these specific ones like uri are pretty much never used in queries, service name, span name, and Timestamp are the common queries which are unaffected so I lean towards not worrying.

The annotations are stored as is, as a map essentially, so don't need to update collectors. But they can be used when querying in the ui which would get complicated when querying across a key change.
But in practice I think these specific ones like uri are pretty much never used in queries, service name, span name, and Timestamp are the common queries which are unaffected so I lean towards not worrying.

I see. Then it sounds all great to me. :-)

We can skip an appveyor's test failure (https://ci.appveyor.com/project/trustin/armeria/build/master.803#L603 ) since it will fix on https://github.com/line/armeria/pull/680, right?

@imasahiro Yes

Thanks @anuraaga for great work and others for reviewing


Rename HTTP metrics to conform to best practices

It seems like http_request_duration_seconds is the expected metric name for http request durations.
This change is similar to https://github.com/microservices-demo/carts/commit/bd16e1e02aa005faf357902032c47bc66aed23df

Would it be possible to have it merged? Thank you.


added search help text to the model admin

I did this as my first hackathon commit, woohoo!

This is already being worked on in #14117 which is more complete than this. There are also comments on the ticket referenced in that PR that need attention.


Image support in downloaded chapters

Add image support in web view when downloaded

I hope u can add image for your new update🙏

I don't think this would be possible as chapters are downloaded as html,  and react-native-webview renders the html in a native view. So it wouldn't be possible to image support in downloaded chapters.


feat(VocalGuildChannel): add VocalGuildChannel.members_count

Summary

Checklist

[ ] If code changes were made then they have been tested.

[ ] I have updated the documentation to reflect the changes.

[ ] This PR fixes an issue.
[ ] This PR adds something new (e.g. new method or parameters).
[ ] This PR is a breaking change (e.g. methods or parameters removed/renamed)
[ ] This PR is not a code change (e.g. documentation, README, ...)

What's a VocalGuildChannel ?
What is the aim of this PR?
The function right above where you edited also supposedly returns the same thing:
"""List[:class:Member]: Returns all members that are currently inside this voice channel."""
It's like making an extra property for len(Channel.members) - like making an extra property for len(guild.members)

member_count not members_count
Guild.member_count exists because that is provided by discord - is used especially when members intent is not enabled


Typo fix (mqttpproto)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>6
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 82.815%

Totals

Change from base Build<PHONE_NUMBER>2:
0.0%

Covered Lines:
8038

Relevant Lines:
9706

💛  - Coveralls


running in docker.

Based on the boilerplate. and latest version of apostrophe, when i do a node app.js i tget the following
npm info it worked if it ends with ok
npm info using<EMAIL_ADDRESS>npm info using<EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>
<EMAIL_ADDRESS>start /app
node app.js

Error while constructing the apostrophe-utils module
Error: The module apostrophe-utils has an alias, utils, that conflicts with a module registered earlier or a core Apostrophe feature.
at beforeConstruct (/app/node_modules/apostrophe/lib/modules/apostrophe-module/index.js:33:15)
at beforeConstruct (/app/node_modules/moog/index.js:239:21)
at /app/node_modules/moog/index.js:250:22
at iterate (/app/node_modules/moog/node_modules/async/lib/async.js:146:13)
at Immediate. (/app/node_modules/moog/node_modules/async/lib/async.js:157:25)
at runCallback (timers.js:574:20)
at tryOnImmediate (timers.js:554:5)
at processImmediate [as _immediateCallback] (timers.js:533:5)
npm info lifecycle<EMAIL_ADDRESS>Failed to exec start script
npm ERR! Linux 4.9.49-moby
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "start"
npm ERR! node v6.5.0
npm ERR! npm  v3.10.3
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>start: node app.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script 'node app.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the sr-apostrophe package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node app.js
npm ERR! You can get information on how to open an issue for this project with:
my app.js looks like
var apos = require('apostrophe')({
shortName: 'apostrophe-boilerplate',
title: 'Apostrophe Boilerplate',
// See lib/modules for basic project-level configuration of our modules
// responsible for serving static assets, managing page templates and
// configuring user acounts.
modules: {
'apostrophe-attachments': {
uploadfs: {
backend: 's3',
secret: '',
key: '',
bucket: '********-apostrophe-uploads',
region: 'us-east-1'
},
'apostrophe-db': {
uri: 'mongodb://mongo:27017/mydb'
},
}
}
});

Hi Joshua,
I just tried these steps exactly:
npm install -g apostrophe-cli
apostrophe create-project seidel
node app

The site came up without errors.
I then tried replacing my app.js with the one you sent, and still received no errors.
I am not sure what is different about your environment but let me know if you can reproduce the issue following my steps.

@boutell
i managed to get by it. it was a bunch of extra files in lib/modules
now its not picking up the right db, should be mongo as server name as in app.js but its trying to connect to 127.*
root@98f00cdce3c0:/app# cat app.js
var apos = require('apostrophe')({
shortName: 'sr-apostrophe',
title: '********',
// See lib/modules for basic project-level configuration of our modules
// responsible for serving static assets, managing page templates and
// configuring user acounts.
modules: {
'apostrophe-attachments': {
uploadfs: {
backend: 's3',
secret: '*************',
key: '***',
bucket: '-apostrophe-uploads',
region: 'us-east-1'
},
'apostrophe-db': {
uri: 'mongodb://mongo:27017/mydb'
},
}
}
});
root@98f00cdce3c0:/app# node app.js
ERROR: There was an issue connecting to the database. Is it running?
Error while constructing the apostrophe-db module
MongoError: failed to connect to server [localhost:27017] on first connect [MongoError: connect ECONNREFUSED <IP_ADDRESS>:27017]
at Pool. (/app/node_modules/mongodb-core/lib/topologies/server.js:336:35)
at emitOne (events.js:96:13)
at Pool.emit (events.js:188:7)
at Connection. (/app/node_modules/mongodb-core/lib/connection/pool.js:280:12)
at Connection.g (events.js:286:16)
at emitTwo (events.js:106:13)
at Connection.emit (events.js:191:7)
at Socket. (/app/node_modules/mongodb-core/lib/connection/connection.js:187:49)
at Socket.g (events.js:286:16)
at emitOne (events.js:96:13)

Check your indentation, your configuration of apostrophe-db is nested inside your configuration of apostrophe-attachments.
Prettyprinted for clarity:
var apos = require('apostrophe')({
    shortName: 'seidel',
    title: 'seidel',

    // See lib/modules for basic project-level configuration of our modules
    // responsible for serving static assets, managing page templates and
    // configuring user acounts.

    modules: {
        'apostrophe-attachments': {
            uploadfs: {
                backend: 's3',
                secret: '',
                key: '',
                bucket: '********-apostrophe-uploads',
                region: 'us-east-1'
            },
            'apostrophe-db': {
                uri: 'mongodb://mongo:27017/mydb'
            },
        }
    }
});


Feature request: Ability to disable alpha

It would be very nice to be able to pass a prop to the color picker to remove the alpha slider when I want to restrict the possible value selected to RGB, not RGBA. If the ability already exists, I have not managed to find it in the documentation.
I'm thinking it would work something like:
<Colorful disableAlpha='true' />

@PedroDNBR Upgrade v1.1.0+
<Colorful disableAlpha={true} />


double-beep: Blacklist ats\Wost\Wto\Wpst\Wconverter

double-beep requests the blacklist of the keyword ats\W*ost\W*to\W*pst\W*converter. See the MS search here and the Stack Exchange search here.

ats\W*ost\W*to\W*pst\W*converter has been seen in 8 true positives, 0 false positives, and 0 NAAs.

Approved by Makyen in Charcoal HQ


Release 0.1

The built models for this PR are here:
https://s3.amazonaws.com/openstudio-metamodels/small_office/49/3ff422c2-ca11-44db-b955-b39a47b011e7/models/models.zip https://s3.amazonaws.com/openstudio-metamodels/small_office/49/5564b7d5-4def-498b-ad5b-d4f12a463275/models/models.zip
Description of the model covariates and responses can be found here:https://github.com/nllong/ambient-loop-analysis/blob/master/python/analyses.json

The built models for this PR are here:
https://s3.amazonaws.com/openstudio-metamodels/small_office/51/3ff422c2-ca11-44db-b955-b39a47b011e7/models/models.zip https://s3.amazonaws.com/openstudio-metamodels/small_office/51/5564b7d5-4def-498b-ad5b-d4f12a463275/models/models.zip
Description of the model covariates and responses can be found here:https://github.com/nllong/ambient-loop-analysis/blob/master/python/analyses.json

The built models for this PR are here:
https://s3.amazonaws.com/openstudio-metamodels/small_office/55/3ff422c2-ca11-44db-b955-b39a47b011e7/models/models.zip https://s3.amazonaws.com/openstudio-metamodels/small_office/55/66fb9766-26e7-4bed-bdf9-0fbfbc8d6c7e/models/models.zip
Description of the model covariates and responses can be found here:https://github.com/nllong/ambient-loop-analysis/blob/master/python/analyses.json

The built models for this PR are here:
https://s3.amazonaws.com/openstudio-metamodels/small_office/57/3ff422c2-ca11-44db-b955-b39a47b011e7/models/models.zip https://s3.amazonaws.com/openstudio-metamodels/small_office/57/66fb9766-26e7-4bed-bdf9-0fbfbc8d6c7e/models/models.zip
Description of the model covariates and responses can be found here:https://github.com/nllong/ambient-loop-analysis/blob/master/python/analyses.json

The built models for this PR are here:
https://s3.amazonaws.com/openstudio-metamodels/small_office/66/3ff422c2-ca11-44db-b955-b39a47b011e7/models/models.zip https://s3.amazonaws.com/openstudio-metamodels/small_office/66/66fb9766-26e7-4bed-bdf9-0fbfbc8d6c7e/models/models.zip
Description of the model covariates and responses can be found here:https://github.com/nllong/ambient-loop-analysis/blob/master/python/analyses.json

The built models for this PR are here:
https://s3.amazonaws.com/openstudio-metamodels/small_office/69/3ff422c2-ca11-44db-b955-b39a47b011e7/models/models.zip https://s3.amazonaws.com/openstudio-metamodels/small_office/69/66fb9766-26e7-4bed-bdf9-0fbfbc8d6c7e/models/models.zip
Description of the model covariates and responses can be found here:https://github.com/nllong/ambient-loop-analysis/blob/master/python/analyses.json

The built models for this PR are here:
https://s3.amazonaws.com/openstudio-metamodels/small_office/83/3ff422c2-ca11-44db-b955-b39a47b011e7/models/models.zip
Description of the model covariates and responses can be found here:https://github.com/nllong/ambient-loop-analysis/blob/master/python/analyses.json

The built models for this PR are here:
https://s3.amazonaws.com/openstudio-metamodels/small_office/107//models/models.zip
Description of the model covariates and responses can be found here:https://github.com/nllong/ambient-loop-analysis/blob/master/python/analyses.json

The built models for this PR are here:
https://s3.amazonaws.com/openstudio-metamodels/small_office/119//models/models.zip
Description of the model covariates and responses can be found here:https://github.com/nllong/ambient-loop-analysis/blob/master/python/analyses.json

The built models for this PR are here:
https://s3.amazonaws.com/openstudio-metamodels/small_office/123//models/models.zip
Description of the model covariates and responses can be found here:https://github.com/nllong/ambient-loop-analysis/blob/master/python/analyses.json

The built models for this PR are here:
https://s3.amazonaws.com/openstudio-metamodels/small_office/125//models/models.zip
Description of the model covariates and responses can be found here:https://github.com/nllong/ambient-loop-analysis/blob/master/python/analyses.json

The built models for this PR are here:
https://s3.amazonaws.com/openstudio-metamodels/small_office/127//models/models.zip
Description of the model covariates and responses can be found here:https://github.com/nllong/ambient-loop-analysis/blob/master/python/analyses.json

The built models for this PR are here:
https://s3.amazonaws.com/openstudio-metamodels/small_office/129//models/models.zip
Description of the model covariates and responses can be found here:https://github.com/nllong/ambient-loop-analysis/blob/master/python/analyses.json

The built models for this PR are here:
https://s3.amazonaws.com/openstudio-metamodels/small_office/131//models/models.zip
Description of the model covariates and responses can be found here:https://github.com/nllong/ambient-loop-analysis/blob/master/python/analyses.json

The built models for this PR are here:
https://s3.amazonaws.com/openstudio-metamodels/small_office/135//models/models.zip
Description of the model covariates and responses can be found here:https://github.com/nllong/ambient-loop-analysis/blob/master/python/analyses.json

The built models for this PR are here:
https://s3.amazonaws.com/openstudio-metamodels/small_office/137//models/models.zip
Description of the model covariates and responses can be found here:https://github.com/nllong/ambient-loop-analysis/blob/master/python/analyses.json

The built models for this PR are here:
https://s3.amazonaws.com/openstudio-metamodels/small_office/139//models/models.zip
Description of the model covariates and responses can be found here:https://github.com/nllong/ambient-loop-analysis/blob/master/python/analyses.json

The built models for this PR are here:
https://s3.amazonaws.com/openstudio-metamodels/small_office/141//models/models.zip
Description of the model covariates and responses can be found here:https://github.com/nllong/ambient-loop-analysis/blob/master/python/analyses.json

The built models for this PR are here:
https://s3.amazonaws.com/openstudio-metamodels/small_office/143//models/models.zip
Description of the model covariates and responses can be found here:https://github.com/nllong/ambient-loop-analysis/blob/master/python/analyses.json

The built models for this PR are here:
https://s3.amazonaws.com/openstudio-metamodels/small_office/145//models/models.zip
Description of the model covariates and responses can be found here:https://github.com/nllong/ambient-loop-analysis/blob/master/python/analyses.json

The built models for this PR are here:
https://s3.amazonaws.com/openstudio-metamodels/small_office/153//models/models.zip
Description of the model covariates and responses can be found here:https://github.com/nllong/ambient-loop-analysis/blob/master/python/analyses.json

The built models for this PR are here:
https://s3.amazonaws.com/openstudio-metamodels/small_office/159//models/models.zip
Description of the model covariates and responses can be found here:https://github.com/nllong/ambient-loop-analysis/blob/master/python/analyses.json

The built models for this PR are here:
https://s3.amazonaws.com/openstudio-metamodels/small_office/161//models/models.zip
Description of the model covariates and responses can be found here:https://github.com/nllong/ambient-loop-analysis/blob/master/python/analyses.json

The built models for this PR are here:
https://s3.amazonaws.com/openstudio-metamodels/small_office/163//models/models.zip
Description of the model covariates and responses can be found here:https://github.com/nllong/ambient-loop-analysis/blob/master/python/analyses.json


Master is not able to contact the scheduler brought up on docker

Hi All,
I am trying to bring up scheduler using docker on one of the slaves.
It seems that master is trying to send the   acknowledgement to framework subscription to the scheduler framework.Interesting thing here is the ip which master is trying to contact is the docker containers ip.which is not accessible to master.
Topology is on openstack with 1  master and two slaves  and each machine has an public and private ip.
is there any configuration missing. Please advice.
I haven't used marathon yet i am using following command to run the docker container
sudo docker run -t -p 5900:5900 --add-host=master:<IP_ADDRESS> root/kafka-mesos ./kafka-mesos.sh scheduler --master=master:5050 --zk=<IP_ADDRESS>:2181 --api=http://<IP_ADDRESS>:5900 --storage=zk:/kafka-mesos --log=/var/log/mesos.log --debug=true
Received SUBSCRIBE call for framework 'kafka' at scheduler-b3b4006a-6389-456e-877b-107556d41c2d@<IP_ADDRESS>:36680
I1021 00:16:30.042913 28952 master.cpp:2164] Subscribing framework kafka with checkpointing enabled and capabilities [  ]
I1021 00:16:30.042958 28952 master.cpp:2174] Framework 20151020-234515-1929488576-5050-28929-0002 (kafka) at scheduler-b3b4006a-6389-456e-877b-107556d41c2d@<IP_ADDRESS>:36680 already subscribed, resending acknowledgement
W1021 00:16:30.043006 28952 master.hpp:1409] Master attempted to send message to disconnected framework 20151020-234515-1929488576-5050-28929-0002 (kafka) at scheduler-b3b4006a-6389-456e-877b-107556d41c2d@<IP_ADDRESS>:36680
I1021 00:16:35.762477 28951 http.cpp:321] HTTP GET for /master/state.json from <IP_ADDRESS>:50091 with User-Agent='Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.71 Safari/537.36'
I1021 00:16:46.809695 28949 http.cpp:321] HTTP GET for /master/state.json from <IP_ADDRESS>:50091 with User-Agent='Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.71 Safari/537.36'
I1021 00:16:57.808300 28953 http.cpp:321] HTTP GET for /master/state.json from <IP_ADDRESS>:50091 with User-Agent='Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.71 Safari/537.36'
E1021 00:17:08.712221 28956 socket.hpp:174] Shutdown failed on fd=25: Transport endpoint is not connected [107]

Hi all,
sudo docker run -t -p 5900:5900 --net=host root/kafka-mesos ./kafka-mesos.sh scheduler --master=<IP_ADDRESS>:5050 --zk=<IP_ADDRESS>:2181 --api=http://<IP_ADDRESS>:5900 --storage=zk:/kafka-mesos --log=/var/log/mesos.log --debug=true
The issue got resolved by using --net=host why do i need to add --net=host, as it should work normally also. Can you please comment if anything is wrong.

You should run the framework via something like marathon or apache aurora, which defaults to running with --net=host. Running any production application via docker with the bridged networking mode is kind of discouraged. That is why mesos defaults to running apps via host networking mode.

Yeah it worked with running marathon as mentioned by you, there is an option in GUI to select network as host. Can we have multiple scheduler cluster running on one setup.

Yes you can have multiple schedulers running/


Fix Typescript build issues

Description
This PR resolves #52 Blues Stack build issues through refactoring function and variable names to make it consistent with the changes made to the Prisma User model  in #40
Steps to Test
npm install
then:
# Create an .env based on the example
$ cp .env.example .env

# Start MySQL in docker
$ docker compose up
# Wait for the db to finish starting, it takes a few seconds before it's ready...

# Setup the database
$ npm run setup

# Start the app, which will be running on localhost:3000
$ npm run dev

# You can visually see the database using:
$ npm run db:studio'

Credit: @humphd

The dev and build script runs without error locally now.

@dadolhay thanks for the final review; @shawnyu5 thanks for validating!
@SerpentBytes land-ho!


leveleditor: Fix a crash when cancelling out window count changes.

This fixes a crash and addresses issue #5 when you change your window count to 0 and then cancel the operation.

Of course I looked too deep into it, it was that simple! Thanks


update: kill the Process id

@doneill Please review the workaround for the Measuring Tool issue

@mani8177 I have reproduced the issue you mention and am investigating your proposed fix.

Will address this in the quartz update


Testsuite documentation in contributing.rst is not up to date

The documentation says the minimal requirement for running the testsuite is py.test, which is not true. If only py.test is installed, running the tests fails because requests is imported but not installed.

Also pytest-xprocess is used in the test, which is not documented.

Could you open a pull request with the fixes required?

It seems that this was fixed in April this year by 16fdd66c0dc8cfd6e6ec6c90569ba4f667f8b536. The mention of pytest-xprocess is added in https://github.com/pallets/werkzeug/pull/1169.


Bad syntax highlighting

Shouldn't this syntax have better highlighting for the class member variables and functions?

Please create an issue here : https://github.com/Microsoft/TypeScript-TmLanguage we just use that for syntax highlighting :rose: https://github.com/TypeStrong/atom-typescript/blob/master/docs/grammar.md


IFRS9 Consecutive Days on Default

Description
We have a measure that count the number of consecutive day where clients didn't pay their credit card on time. Therefore we put the scope cumulative over this date hierarchy. The issue is that if for few days he started paying on time again, but then months later start to pay after due date, the cumulative doesn't not restart to 0.

This is what you can see on this picture. He started to be on default the first two months (until 2018-10-31). Then from 2019-01-31 to 2019-03-31 he paid on time. Finally on the 2019-04-30 he started to be on default again. Nevertheless, the consecutive days on default should start again to 1.

We need an option on the cumulative scope to restart the accumulation once you hit a null on the previous member.
Context
This is for the IFRS9 demo.

Other information (if relevant)

Can you give a bit more details about the measures involved and their values? I can see there are no values in the second widget before 2018-11-30, but how can you tell that he's late on 2019-04-30?
One issue I see here is that, ActivePivot-wise, a null value means "non-existing" data. Therefore a measure is not evaluated on coordinates where all its underlying values are null.

The data is about credit risk. We want to monitor if the clients pay on time and the risk link to that. In the data set for each client, for each month, you know the number of Days past due. It represents the number of days after his billing date that the bank had to wait for him to pay. Most of the time it is 0 but some clients have some issues to pay their credit on time and they are late on payments.
On this data set we have data for each end of the month. We want a measure to know how many consecutive months this amount was not 0. It represents the number of consecutive month the client was late on his payments. This measure should be reset to 0 once there is a month when he paid on time.
The issue with the cumulative scope is that this amount is not reset if you have a null value as you commented before. Nevertheless, there is an option to fill null locations with the cumulated value dense=True. If there could be an option to have for example reset=True that would be perfect.


Fix spelling in releaseTools/README.md

PR Summary
Fix the spelling in releaseTools/README.md
PR Context
Fix spelling errors.
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Change is not breaking
[ ] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

User-facing changes

[x] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[x] N/A or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

[ ] Add [feature] to your commit messages if the change is significant or affects feature tests

merged when static analysis finished as that was all that was applicable and this was blocking.


Support adding "custom keys" on Sentry

Allows us to add keys like server type etc...

Dupe of #50


[feature] Controlify Support

The ability to use controllers to navigate the EMI UI when using Controlify would be nice to have.

Nvm I can just use the virtual mouse

Using the virtual mouse, EMI already works with Controlify.
But extra compats would be nice like using the L1/L2 and R1/R2 to navigate between pages?


Importing Template as a new Project not possible - no process template found

Hello Guys,
i'm tring to setup a new version of my already existing Demo Project. Now i got following error after clicking "create project":
VS402362: No process template with type  was found.
I successfuly downloaded, some minutes before, the project.
I do not get any better error message by the system. Pls assist :)

Hello @JanWurm Thank you for reaching us.
Looks like you are using custom or inherited process template in the source organization.
In order to import the project template and create a new project, target organization must have the same process template id.
Please have a look at limitation document
Let us know if you have any queries.
Thanks.

Hey, thanks for the fast response!
Yes, i'm using custom process.
So it is not possible to copy this procress whithin the template?

No, process template can't be copied


/outputs directory empty when running cloud segmentation script

Context
I have a docker image that runs a cloud segmentation python script on an input imagery mosaic.
When running locally, 5 files are generated in a folder called /outputs
Unfortunately, when running the job on Bacalhau, the /outputs directory is empty.
Steps to Reproduce
$ bacalhau docker run -v QmTYadG6K4LocouLu6wFzeMXNB5z8ikdpwuGqpdZNxp5qR:/project/inputs/LC08_L1TP_001028_20220615_20220627_02_T1_mosaic.tif jsolly/segmentation_testbed:latest
$ bacalhau describe <JOB_ID> # e.g. bacalhau describe 6931839e-51f6-4a62-8252-605753827be9
# Note the CID shown in the output of `bacalhau describe` for me it was:
`QmcY4WFeknSWgkurAv7rA8XnUDthfPK1vUCYVd7ecG9tpU`

Fetch that output either through a CLI or a gateway such as
https://ipfs.io/ipfs/QmcY4WFeknSWgkurAv7rA8XnUDthfPK1vUCYVd7ecG9tpU/
You will see that /outputs is empty. I do see in the stdout that the script output the expected messages related to segmenting the image

Satellite scene size is (xs,ys)=(7931,8041) with number of bands is 3
(8041, 7931, 3)
0.0 1.0
Segmentation is under way...
Segmentation is finished in<PHONE_NUMBER>5359192 sec...
SLIC number of segments: 1298233
max segment is 1298233
(237585.0, 30.0, 0, 5219115.0, 0, -30.0)

If the script put out those messages, I would expect the output files to be generated.
Expected Behavior
I'll show the workflow for running the docker image locally. Make sure to use the full path to the file with $PWD when passing the file in with the -v command.
1 - Download the imagery mosaic, QmTYadG6K4LocouLu6wFzeMXNB5z8ikdpwuGqpdZNxp5qR to your local machine
2 - Run the public Docker image (same one Bacalhau is using) and pass that file in as input.
$ docker run -v $PWD/LC08_L1TP_001028_20220615_20220627_02_T1_moz.tif:/project/inputs/LC08_L1TP_001028_20220615_20220627_02_T1_mosaic.tif jsolly/segmentation_testbed
# Make sure the container is running and then go into it
$ docker exec -it <CONTAINER_ID> /bin/bash
$ ls ../outputs
LC08_L1TP_001028_20220615_20220627_02_T1_mosaic.tif_ks1_md7_r0.75_scale1_labtrue.dbf
LC08_L1TP_001028_20220615_20220627_02_T1_mosaic.tif_ks1_md7_r0.75_scale1_labtrue.prj
LC08_L1TP_001028_20220615_20220627_02_T1_mosaic.tif_ks1_md7_r0.75_scale1_labtrue.shp
LC08_L1TP_001028_20220615_20220627_02_T1_mosaic.tif_ks1_md7_r0.75_scale1_labtrue.shx
LC08_L1TP_001028_20220615_20220627_02_T1_mosaic.tif_ks1_md7_r0.75_scale1_labtrue.tif

Thoughts
~The output directory is about 430MB, so there could be a size limit we are running into. Is there a hard limit to how large the output directory can be?~
I don't think that's the case. I recorded a 15 min video about another workflow I am trying to accomplish. If you navigate to the end of the video, you can see that Bacalhau is not including a small plot in the outputs folder. In the video example, the image is only ~200kb
Environment

Version of API*
Client Version: v0.3.25
Server Version: v0.3.25

cc @wesfloyd @TaylorOshan

There appears to be an issue on segmentation_testbed_2.py Line# 175 where the outputs folder is hardcoded to be in a parent directory. This could be throwing off the output writes when the job is ran on Bacalhau.
Sharing a screenshot of how the outputs directory should look upon a successful run:

Working on repackaging the docker build and local test now.
On a related note, @jsolly you may also want to rebuild your jsolly/segmentation_... docker image after last week's changes to the Dockerfile (specifically adding mkdir /project/outputs)?

Good news - [this latest command](bacalhau docker run -v QmTYadG6K4LocouLu6wFzeMXNB5z8ikdpwuGqpdZNxp5qR:/project/inputs/LC08_L1TP_0018_20220615_20220627_02_T1_mosaic.tif -o outputs2:/project/outputs/ --id-only wesfloyd/segmentation_testbed:latest) works!
Sharing a PR with the related changes. I think there were conflicts between the scripts output file mapping, the docker file's output mapping, and the bacalhau runtime's output file mapping OR I simply wasn't using the "-o" flag when I was running the Bacalhau command most recently and the outputs were not being captured correctly. By default, Bacalhau captures all the files written to /outputs but not /project/outputs .

Nice job! I think it makes sense to just refactor the script not to use/project and simply allow it to write to the directory where Bacalhau expects it. That was what I was trying to accomplish in the first place.
Closing this one now.


Multiple calls to train cause cudaMalloc to fail

If calling train several times, I ran out of GPU memory:
pooled_storage_manager.h:80: cudaMalloc failed: out of memory
looks like GPU buffers are never cleared and memory runs out.
It needs to be solved to be able to use MXNet in the larger application, where multiple train attempts are made in sequence, without restarting the app.

it looks like the problem can be solved by setting
ptr = new storage::NaiveStorageManagerstorage::GPUDeviceStorage();
instead of GPUPooledStorageManager in storage.cc
Can this be made as an option to be configured at runtime? It really is a bad practice to allocate all availabe GRAM and never release it. Another option is to add a public method that would allow all allocated memory to be released.

Hi, is this problem solved? I met the same question.

no it is not solved, we have ended up modifying storage.cc and making native storage manager a default. The threaded pooled one is garbage, never frees the memory making it impossible to use in any application where we need to be able to use DNN and cuda at the same time.

This issue is closed due to lack of activity in the last 90 days. Feel free to reopen if this is still an active issue. Thanks!


Show memos for outgoing transcations

I'm using BitBanana with CLN.
Memos are shown only for incoming transactions but not for outgoing. Memos are missing in the history view, but also in the transaction's details modal.
Please add the memos for outgoing transactions also, in history and in the modal.
Thank you

Thanks for the issue.
I found and fixed the bug. It will be working in the next version!

Thank you

This is fixed with 0.8.8 which got just released

Thank you. When this version will be available on the Play store?

@sha-265 It is already live, but I did a partial rollout to only 30% of users. I'll observe crash reports and if nothing bad occurs, I'll roll out to 100 % in 2 days.

@michaelWuensch, is it just me or the memo should appear for theses both entries, that belong to the same rebalancing transaction?

@sha-265 yeah, I guess it should show there as well. I am reopening the issue for furter investigation.
Did anything change for you in 0.8.8 in regard to memos for outgoing transactions? Are some shown now?

Did anything change for you in 0.8.8 in regard to memos for outgoing transactions? Are some shown now?

Yes, memos are shown for some of the outgoing transactions, for other outgoing transactions memos are missing, but I'm not sure if it is because there is no memo for these transactions or the memo exists but not shown. The rebalance transaction is a transaction that I was pretty sure that memo exists but not shown.


Please don't pull published gem versions

Steps to reproduce:

You published 2.3.0
We updated our bundle to 2.3.0
You pulled 2.3.0
Death from above

@amilligan sorry for that.
2.3.0 was a invalid release, thats why I have yanked it and released 2.3.1
Any idea how this could have been done better? I don't want invalid releases to be available.
It looks like yanking gem these days removes it completely from rubygems.

I think you can keep it public on rubygems, because the gem follows semantic versioning, so bundle update will use the latest minor release.


[FEATURE] - Improve performance when loading a huge number of files in GROUPED mode

Description
This feature concerns data loading jobs with a huge number of files to ingest (1000+) with GROUPED mode (true). In such case, a major part of time is passed on moving files between zones (landing to pending, ingesting to archive). This is due to the fact that files are moved sequentially ( simple foreach). In some cases, 30 min are spent on moving files whereas the actual ingestion process takes around 5 min.
Expected behavior
Parallelize file handling when possible.
Possible implementation
using scala palallel collections
Example in the ingest() method on IngestionWorkflow
ingestingPath.par.foreach { // back up file in archive}
instead of
 ingestingPath..foreach { // back up file in archive}
Complexity estimation
T-Shirt Size: S

Are you sure you are not hitting a rate limit HTTP 429 too many requests ?

This would improve performance if and only if we are using COMET_GROUPED. On another note, do you ming prequalifying this as a feature instead of bug ?

Done, and yes it concerns loading data using GROUPED mode.

Are you sure you are not hitting a rate limit HTTP 429 too many requests ?

For the cases I've seen, no errors were reported in the logs.

Using the multi threading calls I encountered these issues. I will tru to remove this limitation before stating that this feature is done

done


Much improved 2Checkout Driver

Hi @amacneil and @kayladnls
I wrote a much improved 2co gateway using the latest API paramters and support for payment via credit card token.
See it here https://github.com/collizo4sky/omnipay-2checkout
Note: the one here uses llagacy parameters (http://help.2checkout.com/articles/Knowledge_Article/Legacy-Parameter-Set) which include no support to pass in line items of products to puchase and obviously lack support for payment via credit card token.
I was hoping mine should replace this. and if No, the least thing to be done is include it in the list of payment gateways

@kayladnls what do you think?

Can we get some docblocks on the new gateway please? I think that incorporating it as a new gateway and deprecating the existing 2checkout gateway (but leaving it in place for anyone that's still using it) is probably the way to go.

@delatbabel totally agree with that direction.
I will get the docblocks added, add some documentation to the readme and let you know when it's done.

Hey @delatbabel its done. https://github.com/collizo4sky/omnipay-2checkout
A pull request and an issue merged and fixed respectively :smile:
Let me know when i can submit a PR for it inclusion among the list of gateway drivers.

Hi, yes this should be fine to submit to https://github.com/thephpleague/omnipay

@collizo4sky if your driver replaces this one then perhaps you can submit a PR for the REAME.md in this gateway announcing that it has been deprecated and pointing people to your own gateway.  In the mean time I will close this issue as the PR for the master repo has been merged.

Done.


[TIDY FIRST] Fix type hinting of mashumaro/core/meta/helpers.pyi

resolves N/A
Description
Mypy didn't like that we were using the Type generic without a scope annotation. To get mypy to stop yelling about it we've added altered the type hint to be Type[Any]
Checklist

[X] I have read the contributing guide and understand what's expected of me
[X] I have signed the CLA
[X] I have run this code in development and it appears to resolve the stated issue
[ ] I have opened an issue to add/update docs, or docs changes are not required/relevant for this PR
[ ] I have run changie new to create a changelog entry

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 64.34%. Comparing base (c9cc99e) to head (cc6f9dc).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #184   +/-   ##
=======================================
  Coverage   64.34%   64.34%
=======================================
  Files          51       51
  Lines        3231     3231
=======================================
  Hits         2079     2079
  Misses       1152     1152

Flag
Coverage Δ

unit
64.34% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Add Support to use Catalog in a class withhout direct load of a PO file.

By the default, if using a catalog object inside a class, it will issue that it can not find the default constructor:
However, the only way to remove this error is by creating the catalog object inside class as followed in the constructor:
Translation(void) : _cat(spirit_po::default_catalog::from_range(""))
Of course, this constructor yields an exception since it is not a valid po source code. so it is not really possible to load a po file later in the code. especially not in the constructor.
Translation(void) { std::ifstream ifs(fmt::format("{}.po", "en")); std::string po_file{std::istreambuf_iterator<char>{ifs}, std::istreambuf_iterator<char>()}; auto catag = spirit_po::default_catalog::from_range(po_file); this->_cat = catag; }
This constructor does not compile. since ‘spirit_po::catalog<>::catalog() constructor is not found.
Other options is to provide a default string for the from_range functions of a valid minimum po data string

I think what I would recommend is, either provide a valid po source in your class, or it means, your class has a valid state (at the end of some constructor) where it doesn't really have a catalog yet. So, you should have Optional<Catalog> as the type of your class member, and you can put None in your default constructor.


Java. Security.cert.CertPathValidationException:

Trust anchor for certification not found.
Was working fine stopped few days ago with this error.
Nexus 6p stock 6.0.1 unlocked/rooted

is this with gmail or custom IMAP?

This is gmail.

Since discovered that this happens/won't work when using wifi at work. They must have some policy that is blocking.
Thanks


chore: update rxjs to rc.1

Related to #2866

I don't think we can do this at the moment. @angular/* packages explicitely list 5.0.0-beta.12 as the peerDep, so if we change it everyone will get it peerDep warnings.
$ npm info @angular/core peerDependencies
{ rxjs: '5.0.0-beta.12', 'zone.js': '^0.6.21' }

I agree with @filipesilva.  Unfortunately we won't be updating until the core team does.

Then maybe #2866 is worth reopening for now?
I'm really upset with the size of angular-cli.. 🤔

@dzonatan you're right, reopening #2866.

FWIW, the PR for 5.0.0-rc.1 in core (https://github.com/angular/angular/pull/12476) is now tagged for merge, but it probably doesn't make sense to re-open this until they cut a release.

@nkwood fair enough, didn't know it was already that close. I'll keep this open but on hold.

@dzonatan , it's better to support rc4

Closing as we'll  do this update when moving to angular 2.3.

so when will you moving to angular 2.3?


Update to stargate v1.0.62

What this PR does:
Build Stargate images for v1.0.62
Which issue(s) this PR fixes:
Checklist

[ ] Changes manually tested
[ ] Automated Tests added/updated
[ ] Documentation added/updated
[ ] CLA Signed: DataStax CLA

Cannot do, due to failure of Stargate 1.0.62 jar publish.


feat(Select): add component api

We have discussed this PR with @amje and decided that apiRef does not a good idea. There is a new idea to provide required control for select options. More details here
cc @Radomir-Drukh


[Website] Data from uploaded PDF files being ignored?

Hello!
We are running the bot via the website for now to test things out before deploying our own, however we are encountering an issue where the uploaded PDF files are showing as successful, however the specific information inside of them is not being referenced by the bot.
For example, one section of a PDF has an "answering machine script" - but if I ask the bot what the answering machine script is, it tells me it cannot answer questions out of context.
I am wondering if the initial prompt is preventing the bot from parsing or using the data held within the PDFS? Our initial prompt is as follows:
You are a helpful AI agent support agent. Use the following pieces of context to answer the question at the end.
If you don\'t know the answer, just say you don\'t know. DO NOT try to make up an answer.
If the question is not related to the context, politely respond that you are tuned to only answer questions that are related to the context.

[our company context]

Is there something I am missing here? Thanks for the great product so far! Looking forward to growing and expanding along with its progress.

I seem to have the same problem with an indexed website. I can apparently only retrieve information from <rootURL>/index.html but not from subpages <rootURL>FolderName/index.html which is referenced in /index.htmlashref="FolderName/index.html"`.
I noted also that my Pinecone index says it has 0 vectors, though OpenChat says it has successfully indexed the website.
PS: I'd have a couple of other questions, in particular on how to adapt the bot to my requirements. Would you mind setting up a kind of community support forum?

Is there a timeline for correcting this bug? let me know if I can help with testing.

@ingodahn I plan to have this resolved by the end of day Monday. It would help me out if you could provide a link to the PDF file or upload it. That way I can review it and try to fix the issue. Please let me know if you can send the file my way.

Great. My use case requires crawling a web site, not a pdf document. The website I am working with is https://netmath.vcrp.de/downloads/Skripte/Vorkurs/HSWildau/. You can download it zipped here.
Only linked pages with links with URLs extending the root URL need to be indexed.

Hi @ingodahn ,

The first 10 pages of your website were indeed scanned. But i do see the problem here

Perhaps it's related to the fact that the website is in German. However, I'm not entirely certain at this time. I will look further into this

Hi,
The URLS listed in your first screenshot under URL are outside the root
and don't need to be tracked. Moreover these contain dynamically
generated content which cannot be indexed anyhow.
Here is the German summary of the complete start page generated by Bing.
Only the first paragraph of the summary is correct. I don't know why it
hallucinates about LK-99, this doesn't occur in the source code.
When I talked back it confirmed that the page says nothing about LK-99
and gave a correct short summary:
When I asked for an English summary of the complete start page, it gave
a correct and detailed summary:
Hope this helps.


Looking to contribute

Hey kickstarter - iOS team!
I'm looking to contribute but am not sure where to start. The projects board is empty & there aren't any bugs, small user stories, "help wanted" issues filed. Can I assume that all that is tracked somewhere outside of Github? If so, Is is publicly accessible?
Thanks in advance!
Nishant

Hi @nishant2718! While we appreciate your wanting to contribute, this is not really something we currently support in our product development process. As mentioned in our README.md:

We intend for this project to be an educational resource: we are excited to share our wins, mistakes, and methodology of iOS development as we work in the open. Our primary focus is to continue improving the app for our users in line with our roadmap.

If that ever changes, we'll let you know!
Of course if you do find a bug using the app or notice something that you think could be improved, open an issue to discuss it and we could potentially help shepherd a PR into the codebase. This issue is an example of a time we've done that before.


Insert ISO 19110 into ISO 19115-1

Add support for embedding ISO 19110 into contentInfo section of ISO 19115-1

@stansmith907 can you comment on the status of this?

19110 Feature Catalog support was implemented in V12.16.1 (2019-09-24) as part of issue #216. Doesn't appear the feature catalog section was embedded within the contentInfo block. Unsure if that is what this issue is addressing.


Remove 0010-Remove-pattern-string-from-compute-forwarding-rules.patch

Per https://github.com/pulumi/pulumi-gcp/issues/2324, we should be able to remove this patch.

Added to epic https://github.com/pulumi/pulumi-gcp/issues/2290

Closed via https://github.com/pulumi/pulumi-gcp/pull/2355.


camel-k-context-jvm, camel-k-context-kotlin, camel-k-context-groovy pods goes into error state when installing camel-k

Environment Detail:
Minikube version: v0.29.0
Host: MAC OSX
Camel-K: Camel K Client 0.0.4
Steps followed:
Started minikube with minikube start
Enabled registry addon minikube addons enable registry
kamel install
I found this error message in  camel-k-context-jvm pod log:
INFO[0000] Downloading base image fabric8/java-alpine-openjdk8-jdk:1.5.1
2018/10/29 04:27:45 No matching credentials were found, falling back on anonymous
error building image: getting stage builder for stage 0: UNAUTHORIZED: "authentication required"

@shyabithd this is known issue, please use solution from it https://github.com/GoogleContainerTools/kaniko/issues/372

This should happen when the connection is slow. It looks that that should be fixed now: https://github.com/GoogleContainerTools/kaniko/issues/245#issuecomment-428698222.
I'm going to change the kaniko image used under the hood.

@shyabithd there's a new version of kaniko released yesterday. I've fixed the issue for 0.0.5 onwards, but you should be able to have it working on 0.0.4 by doing:
# update the Kaniko image
eval $(minikube docker-env)
docker pull gcr.io/kaniko-project/executor:latest
# reinstall camel k
kubectl delete integrationplatform camel-k
kubectl delete delete ictx jvm groovy kotlin
kamel install

Thanks @nicolaferraro for the help. I will try this.


"Sign In" and "Sign Up" Buttons Border Removal

Feature idea.
The design of both buttons is nice but it can improved by removing black color border which is creating conflict with overall theme of the website. By removing it, the overall look of the homepage will be even better.
Describe the solution you'd like
Removal of black color border around both the buttons or choosing another light color border which matches with the theme of the website.
Current Design

Expected Updated Design

/assign

Hey @iamRabia-N  I don't think its required it look nice to us u can find other issue Thanks :)

OK  fix it @iamRabia-N

Please assign this project to me. i will fix the issue


Export EventListener type

Description
Came across following typescript error when working with getContract function from @wagmi/core package (ContractCtrl is my file using this function).
Exported variable 'ContractCtrl' has or is using name 'EventListener' from external module "/node_modules/@wagmi/core/dist/declarations/src/actions/contracts/getContract" but cannot be named.

Not entirely sure what the root cause of this error is, but exporting EventListener interface resolves it. My hunch is that it's something to do with ts semantics and using associated functionality of this type "outside" of its definition.
Additional Information

[x] I read the contributing docs (if this is your first contribution)

Your ENS/address:

@IljaDaderko weird. looks like something wrong with pnpm x git hooks. can look into this.
in the meantime, should be fine if you add --no-verify to git commit to get your changes up.

@tmm done, ty for helping out 👍


Cache SVG path fragments for segments

They get recomputed a lot in some cases, and it seems to be adding CPU and GC loads.

Implemented.


VS Code Windows Bug

Version: 1.35.1 (user setup)
Commit: c7d83e57cd18f18026a8162d042843bda1bcf21f
Date: 2019-06-12T14:30:02.622Z
Electron: 3.1.8
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 10.0.17134
Steps to Reproduce:

Use Ctrl + ` to open a terminal in VS Code, and use git bash(Or Power Shell) to run git commit
Then, the git will pop up a "vim" in the terminal, but the rendering is disordered. Just like this:

I didn't found this bug on Linux yet.

Does this issue occur when all extensions are disabled?: Yes/No
Yes

This looks like an issue with our old terminal backend "winpty", going forward we are focusing our efforts on the new backend "conpty" which is build by the Console team at Microsoft and should fix many issues with the terminal under Windows. You can read more about getting ConPTY here.
/duplicate https://github.com/Microsoft/vscode/issues/45693

OK, thanks


ClassCastException in 2.1.0 (getBinaryBulkReply)

Sorry, my logs truncated this.
java.lang.ClassCastException: java.lang.Long cannot be cast to [B
at redis.clients.jedis.Connection.getBinaryBulkReply(Connection.java:182)
at redis.clients.jedis.Connection.getBulkReply(Connection.java:171)
at redis.clients.jedis.Jedis.get(Jedis.java:67)
I'm using a connection pool, and noticed that there was an earlier exception:
redis.clients.jedis.exceptions.JedisConnectionException: java.net.SocketTimeoutException: Read timed out
at redis.clients.jedis.Protocol.process(Protocol.java:79)
at redis.clients.jedis.Protocol.read(Protocol.java:131)
at redis.clients.jedis.Connection.getBinaryBulkReply(Connection.java:182)
at redis.clients.jedis.Connection.getBulkReply(Connection.java:171)
at redis.clients.jedis.Jedis.get(Jedis.java:67)
It looks like my code was not calling returnBrokenResource() on the broken resource, and returning it to the pool as normal.  However, Jedis should probably still do something to catch that class cast exception.

If Jedis operation happens Exception, it must be calling returnBrokenResource() on the broken resource, that the broken resouce will be destroyed.

@idyedov @joeyzhu0422 you should never use a Jedis instance in a multi-threaded environment. That's why JedisPool exists. Have you checked out the part of the wiki that mentions it? (https://github.com/xetorthio/jedis/wiki/Getting-started#using-jedis-in-a-multithreaded-environment)
Are you still getting this error in a non-multithread env?


Added support for LicensePassword and LicensePasswordFilePath to ArcGIS Pro configuration

In the current version of ArcGIS Powershell DSC, there is no support for the variables LicensePassword and LicensePasswordFilePath for ArcGIS Pro, even though they're described in the Variables reference page in the wiki.
This pull request adds support for these two parameters for ArcGIS Pro.

These changes have been incorperated into module v4.2.0. Thanks @sverkerEsriSE for the contribution!


Disable "Expand Sync to Working Set" by default

I want to bring to attention one scenario that I experiences which confused me and my investigation into it.
TLDR: I propose to change the default for BlazeUserSettings#expandSyncToWorkingSet  from true to false because IMO it can confuse users more then help them.
In my case I have a huge mono repository where we practice fork driven approach (each engineer has a fork to work on and we submit PRs to the main repository). I have two origins in my Git repository: origin and fork. For example, I have a feature branch  fork/fedor/feature-1 which was checkout from fork/master. I did some development, opened a PR, got some feedback after a few days and now I'm rebasing my feature branch on top of the latest changes from origin/master. Now when I run Sync from IntelliJ I see that the plugin syncs every single target in the repository.
After some investigation I found the root cause: because my fork/master hasn't been rebased as well this causes the "working set" to contain all files changed between fork/fedor/feature-1 and the outdated fork/master instead of origin/master. Here is how GitBlazeVcsHandler calculates the working set of files. The troubling part is how the SHA is calculated in getUpstreamSha.
I propose to change the default for BlazeUserSettings#expandSyncToWorkingSet from true to false. It seems this automatic expansion of the target set based on changed files can bring more harm than benefits for use cases similar to mine.
Unfortunately I wasn't able to find more information about motivation for expandSyncToWorkingSet feature because this feature predates the publicly available Git history.

Opened https://github.com/bazelbuild/intellij/pull/3229

Disabling this functionality wouldn't work for everybody. I've heard that others in the community use the behavior of "Expand Sync to Working Set" as a workaround for pulling in dependencies which are not attached via the regular Blaze sync (due to gaps which might exist for their specific setup). I wouldn't want to break them.
Apart from this, "Expand Sync to Working Set" is a functionality which is used by our internal developers. We can't simply change the default behavior for them after so many years.
You're welcome to improve the implementation of GitBlazeVcsHandler.
An alternative could be to find out how the plugin's settings could be made available within the default IDE settings (reachable via "File > New Projects Setup > Settings for New Projects") and whether such settings could be easily provided/adjusted from outside of the original plugin.

My main point is that it seems for me that this option should've been disabled by default in the first place. And people that want this "workaround for pulling in dependencies which are not attached via the regular Blaze sync" should explicitly enable it.
I think the question here is what is the right behaviour for the majority of people. I'm convinced that the option should be disabled by default because it causes frustrations that I described.
What if we'll disable it only for newly imported projects so it won't change behaviour for existing projects?


[SymbolGraphGen] add new flag to skip "protocol implementation" symbols

Resolves rdar://59899968
This PR introduces a new flag to affect SymbolGraphGen, available on the frontend and on swift-symbolgraph-extract: -skip-protocol-implementations. When present, this flag causes SymbolGraphGen to drop symbols that have an "inherited symbol", i.e. that are implementations of protocol requirements or are synthesized copies of protocol extensions. The conformance relationship between the type and the protocol itself remains, so that these relationships can be reconstructed.

@swift-ci Please smoke test

@swift-ci Please build toolchain macOS Platform

@swift-ci Please smoke test

@swift-ci Please test

@swift-ci Please build toolchain macOS Platform

@swift-ci Please build toolchain macOS Platform


Update troubleshooting-windows-mixed-reality.md

updated wording

@hamid-hawklogix : Thanks for your contribution! The author(s) have been notified to review your proposed change. @hferrone

@hamid-hawklogix : Thanks for your contribution! The author(s) have been notified to review your proposed change. @hferrone


Inferno should allow customized tests

Our API does not support resources such as CarePlan, CareTeam, or Provenance. Is there a way to exclude these resources when running the US Core 5.0.1 or (g)(10) test suites, or a plan to add this feature?

For (g)(10) test suites, these resources are required by (g)(10) test procedure and could not be removed.
If you just want to test server conformance to US Core IG, you can use US Core Test kit https://inferno.healthit.gov/suites/

Though you cannot remove these tests from the test suite, you can either skip these test groups for these resources, or ignore results from these groups

Thank you @yunwwang, we'll stick to the previous version.


How can I get request headers in generated sever's handler?

I use guardrail to generate server. How can I get request headers inside handlers  routines?

trait Handler {
  def getFoo(respond: Resource.getFooResponse.type)(header: String,
                                                    longHeader: Long,
                                                    customHeader: Bar,
                                                    customOptionHeader: Option[Bar] = None,
                                                    missingCustomOptionHeader: Option[Bar] = None): scala.concurrent.Future[Resource.getFooResponse]
}

this is the server generated for https://github.com/twilio/guardrail/blob/master/modules/sample/src/main/resources/custom-header-type.yaml

Thanks a lot for quick response.
My fault, for too general question. I've meant the access to all headers (for example as Map[String, String]). But you are right, most of tasks could be solved by defining parameters in headers.

This is by design; uncommunicated parameters, (even headers!) defeat the purpose of having a protocol specification.
Generated clients currently permit specifying arbitrarily headers, but this was before headers were fully supported in both clients and servers.


OCaml Compiler Versions

We currently have support for a huge number of OCaml compilers, from the truly ancient 3.0.8, up to 4.02.3.
An increasing number of OCaml packages are mandating 4.02 or higher to build - in the tree right now, 57 packages which either fail to build with OCaml < 4.02, need to use an older version of the package, or need to add configure switches/patches to disable features.
This problem is not going away, it's only getting worse - of the packages I've been adding to the tree for work, only one of them did not mandate OCaml >=4.02 to work.
To exacerbate the situation, OCaml is switching to a new macro system (ppx) which is only supported in 4.02 and up. In #18572 I've tried to keep support around for the camlp4 stuff around, but this is mostly a stopgap measure.
We need to make a few decisions:

Do we want to change the default OCaml version?
Do we really want to keep all these versions around?
Do we want to support camlp4 in the future?

Personally, I'd propose:

Bump default OCaml to 4.02
Keep a minimal set of compiler versions (hopefully just 4.02 + one other) in order to keep any applications (not libraries) which may depend on older OCaml working.
Similarly to legacy OCaml compiler support, I'd recommend keeping camlp4 versions of libraries around only in cases where they are used by a binary.

Obviously I'm not the one to make the decision, but something needs to be done about this or it's only going to get more difficult to keep up with the OCaml ecosystem.

cc: @aske @vbgl (I think you may have opinions on this)

I'm all for version bump and bumping to 4.02 and removing old clutter.
Will take a look on what to keep a bit later.
Also +1 for switching to ppx.
I think we should keep latest 3.12 compiler in case user wants to use some ancient research project or similar and 4.01 for packages that may not work with 4.02+ (are there any?).
For new packages it's probably better to operate under assumption that it will be used with 4.02+ only (btw, will it require a lot of work to switch to 4.03 as a default version?).

I think we could directly switch to 4.03, as the vast majority of packages working with 4.02 have also a working version for 4.03 (the opam weather service gives a neat overview of the state of packages against various compiler versions), and 4.04 is already about to land soon.
Also :+1: for keeping one (but no more) old version if needed for some packages -- but this may not be needed, as --- except for ppx --- the compiler keeps a rather good retro-compatibility.

Now that ocaml 4.03 is in nixpkgs, is there a possibility to set-up a hydra jobset for ocamlPackages_4_03 --- and maybe ocamlPackages_4_02 too, so that one can see which packages build fine and which one needs to be fixed before any decision is taken ?

Any news on this topic?

We did switch to 4.02 by default.

(Going through my backlog of open issues)

As Florent said, we switched to 4.02 as our default
Packages seem to be being migrated to ppx opportunistically, as long as nox-review and friends indicate no breakage

As a result, the really awkward package splitting I was complaining about seems to be resolved, and I'm closing the issue.

What about making 4.04 the default? 4.05 should land next week, but many packages in nixpkgs are not ready for it yet.


Add CUSTOM_STATUS activity type

Not supported by the gateway yet, but as we know Discord likes to break stuff (meanwhile adding a cool thing) https://github.com/DJScias/Discord-Datamining/commit/f83e634047127ea7b9d5e34e2d640a2f135be59b

Not supported by the gateway yet, but as we know Discord likes to break stuff (meanwhile adding a cool thing) DJScias/Discord-Datamining@f83e634

Well, today is a new day, and apparently there are already some bots using it. I guess this PR fixes the tons of spam I'm getting.


Bugfix: actually use v6 SNAT IP inpod

This should have been in https://github.com/istio/istio/pull/50747 but somehow I looked at that (and the goldens!) and didn't recognize that using a v4 ip in a v6 rule was wrong.

@bleggett: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
6ff40b3651b146c5390fe658166c60cba2d3f1f5
link
true
/test release-notes

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

LGTM. do we not run our IPv6 tests with ambient or did we somehow miss it?

We do not (or they would have failed). Unit tests can easily/conclusively catch this tho, I just wrote a bad test.

https://github.com/istio/istio/issues/51222 ref (I coulda sworn we had an issue for this already, I remember talking about it, but whatever)


Possible to add setting for coloring based on theme colors?

Since semantic colors look the same in various color schemes, I was wondering if it would be better to take color cues from the color scheme itself and color based on those instead of a rainbow.
What I'm proposing is taking advantage of points of color from the color scheme and using that to create a "theme" of colors to change tint which should ultimately allow them to better fit with the color scheme but still look like unique vars.
As far as I've seen, having the same colors for vars no matter the language and color scheme is a great idea and very beneficial, but the impact is everything looks samey and this is unchangeable without disabling semantic colors.

I wanted to do this but it isn't practical. There is no easy way to read the color settings from the theme.


380 windows support

WIP
Syft now compiles for windows. I'll be pulling this down on my mac and linux boxes to hammer out any issues for those architecture.
Stereoscope needs an update:
See - https://github.com/anchore/syft/issues/380#issuecomment-941895866
Picture of compile and help command running:

Syft runs after removing the offending filepath.Clean not sure if this is the entire fix and how this might break other cases:

Replaced locally removing this function:
https://github.com/anchore/stereoscope/blob/53801100857890df6c7e3ec6e80d47a7f45334d4/pkg/file/path.go#L19-L26


Make controller deployable

Make controller deployable
Make controller deployable (#17)
Add release-manifest task

Current dependencies on/for this PR:

main

PR #18   👈

PR #19

PR #20

This stack of pull requests is managed by Graphite.

Merge activity

Nov 15, 12:32 PM: @Danil-Grigorev merged this pull request with Graphite.


feature: create base, component and utilities styling

Issue: https://github.com/LaurierHawkHacks/Landing/issues/102

What has changed?

header
button
link
button and link state

Thanks @GabeDiniz. they are all basically the same button that have the same states, and I didn't apply the state style directly onto the other two buttons hhh. (Not your eyes fault, my bad for the confusion hhh)

I just kinda hope that design team would actually use the colour on the colour palette for the state visual, instead of some random value you know...


OWNERS: add user v1k0d3n as reviewer

This change adds v1k0d3n as a reviewer, if the project is willing.

v1k0d3n

What this PR does / why we need it: This PR adds a reviewer to the OWNERS file.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes # N/A
Special notes for your reviewer: N/A
Release note:

/ok-to-test
/approve

/lgtm


Virtual Desktop Continuous Looper

📝 Allows user to loop through virtual desktop continuously from either direction
What is the expected behavior of the proposed feature?  What is the scenario this would be used?
While holding down Ctrl+Windows, and tapping on Left or Right key, it allows user to loop through all the available virtual desktops and once it reaches the end, it will automatically start from the beginning.
Currently, assuming you have 4 virtual desktops, if you are under Desktop 1, you have to loop 1, 2, 3, 4, and once you are in Desktop 4, if you want to go back to Desktop 4, you'd have to have loop 4, 3, 2, 1..
Ideally, if you are currently under Desktop 4, it would be real useful if you hold down Ctrl+Windows and tap Right key, you automatically go from Desktop 4 to Desktop 1. Similarly, if you are on Desktop 1, you can hold down Ctrl+Windows and tap Left key, and you switch to Desktop 4.
Other people may propose an even better way where you can jump to a specific virtual desktop with a specific combination of hot key, but I am merely proposing a loop instead.

If you'd like to see this feature implemented, add a 👍 reaction to this post.

how is this not yet a feature?! Please add it!

Was surprised that this wasn't a feature already. It would be very helpful for anyone that normally uses more than two virtual desktops at a time.

📝 Allows user to loop through virtual desktop continuously from either direction
What is the expected behavior of the proposed feature? What is the scenario this would be used? While holding down Ctrl+Windows, and tapping on Left or Right key, it allows user to loop through all the available virtual desktops and once it reaches the end, it will automatically start from the beginning. Currently, assuming you have 4 virtual desktops, if you are under Desktop 1, you have to loop 1, 2, 3, 4, and once you are in Desktop 4, if you want to go back to Desktop 4, you'd have to have loop 4, 3, 2, 1.. Ideally, if you are currently under Desktop 4, it would be real useful if you hold down Ctrl+Windows and tap Right key, you automatically go from Desktop 4 to Desktop 1. Similarly, if you are on Desktop 1, you can hold down Ctrl+Windows and tap Left key, and you switch to Desktop 4. Other people may propose an even better way where you can jump to a specific virtual desktop with a specific combination of hot key, but I am merely proposing a loop instead.
If you'd like to see this feature implemented, add a 👍 reaction to this post.

I was also looking for this feature and looking for a way I am using 9 windows and every time I have to come back to the first one by pressing ctrl+wind+left 8 more times to come back


Improved testing and comparison tooling

I've been working on new tools to help review the result of any changes made to the codebase.
The new comparison tool is essentially an integration test which runs all of the examples using the current source and compares results against the latest release build. It produces a report flagging any:

runtime errors
intrinsic changes (mass, intertia, friction etc.)
extrinsic changes (position, angle, velocity)
performance changes

Intrinsic properties generally shouldn't change (other than new properties) as this would indicate a likely regression, or at least a breaking change. For example, the mass of the same body should never change between versions.
Extrinsic properties may change as they may have multiple acceptable values due to limited simulation accuracy. They indicate a change to the simulation behaviour, which may be acceptable and intended or may not be. For example, the position of the same body may change between versions if an accuracy improvement was since implemented. Whereas a code refactor for example, should not normally change the resulting extrinsic properties between versions.
It's possible for example that a performance refactor might come with an accuracy trade-off that changes extrinsic properties whilst producing acceptable results. Generally extrinsic changes will require some further manual testing and review before deeming acceptance into the build (the visual comparison tool below can help with judging the difference).
Here's how to run the comparison integration test (included as part of the test suite):
npm run test or npm run test-watch

There is also a new browser-based visual comparison tool that runs both versions side by side and overlays both interactive simulations in real-time for comparing extrinsic changes. Below you can see how the catapult example behaviour quickly diverges from release version when the default friction is changed.
open http://localhost:8000/?compare=120#catapult

To visualise intrinsic changes, the tool can output them into two separate files for each version which can then be diff'd e.g. using vscode.
npm run test-save
code -n -d test/__compare__/examples-build.json test/__compare__/examples-dev.json

This approach is still experimental, so it will take some time to see how useful it is in practice. I might also add code size comparison too. If anybody has ideas on other improvements for this, feel free to post them here. Thanks.

Can't wait for this, this looks like a great tool. Thanks for all your work, @liabru .


Border of Login Button touches GitHub Icon

Description
When the screen size is small, border of login button touches GitHub Icon.  So, when I hover over the login button it occurs.
Screenshots

Additional information
No response

Can I work on this issue?

The same is happening on the Desktop.

I can solve this issue, you may assign me or the person commented above

@prakhartiwari0 I think this layout is provided by next-auth package itself. Can we change it?

Hey @Pradumnasaraf! Can I take up this issue?

Description
When the screen size is small, border of login button touches GitHub Icon. So, when I hover over the login button it occurs.
Screenshots

Good spot! I will assign this to you @anikdhabal

@prakhartiwari0 I think this layout is provided by next-auth package itself. Can we change it?

Yes this is correct. We can override the page but this is not something we want to do at this time.

Hey @Pradumnasaraf! Can I take up this issue?

Tagging individual maintainers creates more notifications for them.  All maintainers are notified of project activity. Please avoid tagging people unless it is absolutely necessary.

Sure Sara and sorry for it! It won't happen again.


winget support?

Hi thanks for a great program, are there any plans to publish on winget?

I have created a PR to add the rust version of PowerSession to Winget (https://github.com/microsoft/winget-pkgs/pull/77905), you might be interested in using that instead.


BouncingScrollPhysics not working on windows (mouse)

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce
I've been searching for a solution for this problem for quite a while now and didn't find anything useful. Whenever I try to create BouncingScrollPhysics just like specified in the documentation it doesn't work for me on Windows.
Expected results
I would expect bouncing scroll physics like shown in the documentation or on in other videos including BouncingScrollPhysics behaviour.
Actual results
The actual results of the scroll look like this:
https://github.com/flutter/flutter/assets/70802809/e6accd22-7686-4e99-8259-d6d855d411e6
Code sample
Code sample
class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
        home: ScrollConfiguration(
            behavior: ScrollConfiguration.of(context).copyWith(
              dragDevices: {
                PointerDeviceKind.touch,
                PointerDeviceKind.mouse,
              },
            ),
            child: ListView(
              physics: const BouncingScrollPhysics(
                  parent: AlwaysScrollableScrollPhysics()),
              children: List.generate(100, (i) {
                return Text("Item $i");
              }).toList(),
            )));
  }
}

Screenshots or Video

Screenshots / Video demonstration
https://github.com/flutter/flutter/assets/70802809/e6accd22-7686-4e99-8259-d6d855d411e6

Logs
No response
Flutter Doctor output
Doctor output
[√] Flutter (Channel stable, 3.13.2, on Microsoft Windows [Version 10.0.22621.2283], locale de-DE)
    • Flutter version 3.13.2 on channel stable at C:\src\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision ff5b5b5fa6 (3 weeks ago), 2023-08-24 08:12:28 -0500
    • Engine revision b20183e040
    • Dart version 3.1.0
    • DevTools version 2.25.0

[√] Windows Version (Installed version of Windows is version 10 or higher)

[!] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at C:\Users\thisi\AppData\Local\Android\sdk
    X cmdline-tools component is missing
      Run `path/to/sdkmanager --install "cmdline-tools;latest"`
      See https://developer.android.com/studio/command-line for more details.
    X Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/windows#android-setup for more details.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[√] Visual Studio - develop Windows apps (Visual Studio Community 2022 17.6.4)
    • Visual Studio at C:\Program Files\Microsoft Visual Studio\2022\Community
    • Visual Studio Community 2022 version 17.6.33815.320
    • Windows 10 SDK version 10.0.22000.0

[!] Android Studio (not installed)
    • Android Studio not found; download from https://developer.android.com/studio/index.html
      (or visit https://flutter.dev/docs/get-started/install/windows#android-setup for detailed instructions).

[√] IntelliJ IDEA Ultimate Edition (version 2022.3)
    • IntelliJ at C:\Users\thisi\AppData\Local\JetBrains\Toolbox\apps\IDEA-U\ch-0\223.8214.52
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart

[√] IntelliJ IDEA Ultimate Edition (version 2023.1)
    • IntelliJ at C:\Users\thisi\AppData\Local\JetBrains\Toolbox\apps\IDEA-U\ch-0\231.9161.38
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart

[√] VS Code (version 1.82.2)
    • VS Code at C:\Users\thisi\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.54.0

[√] Connected device (3 available)
    • Windows (desktop) • windows • windows-x64    • Microsoft Windows [Version 10.0.22621.2283]
    • Chrome (web)      • chrome  • web-javascript • Google Chrome 116.0.5845.188
    • Edge (web)        • edge    • web-javascript • Microsoft Edge 116.0.1938.69

[√] Network resources
    • All expected network resources are available.

It's intended, bouncing scroll physics only makes sense with touch or trackpad, where continuous gestures can accumulate velocity/inertia.

Closing the issue as explained above.


[Bug Report] Documentation is duplicated on the website

Describe the bug
A lot of the documentation on the website contain duplicated information.
Example:

https://gymnasium.farama.org/api/wrappers/reward_wrappers/#gymnasium.wrappers.NormalizeReward
https://gymnasium.farama.org/api/wrappers/observation_wrappers/#gymnasium.wrappers.FlattenObservation
https://gymnasium.farama.org/api/wrappers/misc_wrappers/#gymnasium.wrappers.StepAPICompatibility

This is due because Sphinx collects the docstring for the class and the __init__ which often say the same thing.
One solution could be to move every relevant documentation to the class docstring and configure Sphinx not to take the __init__. (I'm not familiar with Sphinx but I would guess there's a way)
Code example
No response
System info
No response
Additional context
No response
Checklist

[X] I have checked that there is no similar issue in the repo

This is a good point, for now, as the wrappers will be replaced by the experimental ones I would prefer to update those.
The question is what information should be stored in the class docstring and the constructor (__init__) docstring. The problem is that the first line of the constructor docstring is not obviously different from the class docstring. My ideas are

We could modify the pydocstyle checker on the constructor docstring specifically on wrappers such that the first line is not necessary.
Agree on a simple and effective first line of the constructor for pydocstyle and the website
Modify sphinx to ignore the first line of the constructor of wrappers only.

I agree, I will to look for a way to parse the constructor (__init__) docstring to keep only the Args part


Remote access switch

if we are happy with the overall approach, I will extend the remote access on/off switch to other access points and add reporting to the cloud controller. I can also add a build time option if needed.

Do we document the various files in /config in some markdown file?

there is CONFIG.md, but I will add a hint in SECURITY.md too.

Waiting for this https://github.com/lf-edge/eve-api/pull/31 to merge to add the "report status  to cloud" part.

I guess @rene 's sleep comment is what remains. Passsed the eden test suite (apart from the tests which always fails).

can't see why yetus failed, there is this in the logs :
ERROR: Failed to write github status. Token expired or missing repo:status write?
I'll run it locally.

can't see why yetus failed, there is this in the logs : ERROR: Failed to write github status. Token expired or missing repo:status write? I'll run it locally.

ran it locally and checked it manually, can't see any complaint about lines I have changed.

can't see why yetus failed, there is this in the logs : ERROR: Failed to write github status. Token expired or missing repo:status write? I'll run it locally.

yetus log shows
ERROR: GH:3485 does not apply to master.
So need to rebase on master.


Drawing a rounded rectangle in mask graphic produces an error in the canvas renderer

When drawing a rounded rectangle to a graphics object, Uncaught TypeError: Cannot read property '0' of undefined is produced when the graphics object is used as a mask. Here's a fiddle reproducing the problem.
It looks like the shape.points array is undefined when it is passed into CanvasGraphics.renderGraphicsMask.

I believe we fixed this issue in the dev-rewrite branch.


Can enabling a feature enable other feature as a side effect?

In .NET the the Memory Profiler feature relies on metrics.
Should setting SPLUNK_PROFILER_MEMORY_ENABLED enable metrics collection if it the second disabled by default?
CC @signalfx/gdi-dotnet-approvers @signalfx/gdi-java-approvers

Closing. I think it is fine as long as the "side-effect" is enabling something that is e.g. disabled by default and the precedence is documented.


Updating gaffer version to 1.16.1

Updating gaffer version 1.16.1

Closing as test is broken, needs fixing before release


Make make plan approximately twice as fast

It turns out that we've been assigning variables in make lazily. This
means that all variables are evaluated separately for each target.
For example, a make plan uses 4 targets. This means that pass is
called 4 times to get the same password. This is unacceptable for us
because decryption operations on pass are slow. We can measure this
with this with the following:
{ time make plan -e vpc=test } 2>> results.txt

Before (mean wall time: ~85s):
make plan -e vpc=test  19.60s user 6.60s system 30% cpu 1:26.22 total
make plan -e vpc=test  20.19s user 6.96s system 23% cpu 1:55.05 total
make plan -e vpc=test  19.82s user 6.91s system 29% cpu 1:29.93 total
make plan -e vpc=test  19.45s user 6.47s system 35% cpu 1:13.01 total
make plan -e vpc=test  19.38s user 6.44s system 40% cpu 1:03.06 total

After (mean wall time: ~41s):
make plan -e vpc=test  15.15s user 4.15s system 42% cpu 44.942 total
make plan -e vpc=test  14.94s user 4.10s system 41% cpu 45.683 total
make plan -e vpc=test  15.01s user 4.13s system 49% cpu 38.784 total
make plan -e vpc=test  15.10s user 4.13s system 48% cpu 39.696 total
make plan -e vpc=test  15.06s user 4.29s system 47% cpu 40.740 total

Also this might be particularly slow for me because I have a large key on a Yubikey.


Completion list disappears in Lion full-screen mode

when bringing the window up with my QS shortcut when working in a fullscreen app, I now see the window (b61 fix) BUT the completion list only briefly appears (like 1 or 2 seconds) then vanishes. I can still cycle through completions with the arrows, but QS i not really usable that way. On 10.7.2.

I checked with the latest version released today, b63, and still get the same behavior.


[feature] Shell completion

Can it provide completions for common shells?
TIA!

Ok, please!

$ neocmakelsp <TAB>
# or
$ neocmakelsp --<TAB>

$ neocmakelsp <TAB>
# or
$ neocmakelsp --<TAB>

Ohh, I see, then it needs to be packaged to linux distributions. And maybe zsh of fish completion files? You can help me add some. Thanks

Oh, I notice this program is written in rust. So I guess clap can be helpful?

Oh, I notice this program is written in rust. So I guess clap can be helpful?

This program has already used clap, but these options are inside the program, shell will never know

shell will never know

It looks like cargo build will generate those shell completion scripts, then they

be packaged to linux distributions

https://gitlab.archlinux.org/archlinux/packaging/packages/eza/-/blob/main/PKGBUILD?ref_type=heads#L48-50

shell will never know

It looks like cargo build will generate those shell completion scripts, then they

be packaged to linux distributions

https://gitlab.archlinux.org/archlinux/packaging/packages/eza/-/blob/main/PKGBUILD?ref_type=heads#L48-50

https://github.com/eza-community/eza/blob/main/completions/zsh/_eza
Like eza, the completions is written by hands, not by cargo, cargo will not do such kind of things

Interesting. I need to take a look at some similar projects before answering this question.

ok, I have add a fish completion. because I only use fish

ok, fish and zsh is generated


Transfer ownership of Drip List to elimu.dao.eth

https://www.drips.network/app/drip-lists/41305178594442616889778610143373288091511468151140966646158126636698

https://etherscan.io/tx/0x68717f5102ed000e69147e9857b378e5a2ce33118a53c77aad07805da5b9a120


viewMode=all does not work in ols4 v1

Describe the bug
It seems ols4 v1 does not support viewMode for the jstree endpoint
To Reproduce
call: api/ontologies/chebi/terms/http%253A%252F%252Fpurl.obolibrary.org%252Fobo%252FCHEBI_75835/jstree?viewMode=All&siblings=true
Expected behavior
It should work as ols3: https://service.tib.eu/ts4tib/api/ontologies/chebi/terms/http%253A%252F%252Fpurl.obolibrary.org%252Fobo%252FCHEBI_75835/jstree?viewMode=All&siblings=true
In frontend --> go to this tree view and click on "Full Tree" button  https://terminology.tib.eu/ts/ontologies/chebi/terms?iri=http%3A%2F%2Fpurl.obolibrary.org%2Fobo%2FCHEBI_75835

another issue is that jstree returns 500 for individuals
http://ols4backend21.service.tib.eu:8080/api/ontologies/vibso/individuals/https%253A%252F%25[…]00-0002-2239-3955/jstree?viewMode=All&siblings=false
might be related to this
ols3:
https://service.tib.eu/ts4tib/api/ontologies/vibso/individuals/https%253A%252F%252Fo[…]rg%252F0000-0002-2239-3955/jstree?viewMode=All&siblings=false (edited)

@Pooya-Oladazimi @deepananbu It seems the jstrees are formulated differently in ols4:
This is our frontend with Pooya's initial example: https://terminology.tib.eu/ts/ontologies/chebi/terms?iri=http%3A%2F%2Fpurl.obolibrary.org%2Fobo%2FCHEBI_33292&obsoletes=false&subtab=graph
And this is EBI's frontend with the same example: https://www.ebi.ac.uk/ols4/ontologies/chebi/classes/http%253A%252F%252Fpurl.obolibrary.org%252Fobo%252FCHEBI_33292
If you click on "has role" and "subClassOf" checkboxes in EBI's frontend, then you get the same graph. Can our frontend do the same?

@giraygi
The result format for the tree API is the same as ols3. This forces the client to completely change the way the tree data is rendered.
besides, there is type inconsistency in the v2 result which makes it not suitable, have a look at this: https://github.com/EBISPOT/ols4/issues/649#issuecomment-2064162078

@giraygi
In general, it is recommended to avoid v2 as much as possible: https://github.com/EBISPOT/ols4/issues/649#issuecomment-2069199672

@giraygi
The result format for the tree API is not the same as ols3. This forces the client to completely change the way the tree data is rendered.
besides, there is type inconsistency in the v2 result which makes it not suitable, have a look at this: EBISPOT#649 (comment)

There is a v1 AI for the alternative hierarchicalChildren endpoints that they use. Here are the examples:

https://www.ebi.ac.uk/ols4/api/ontologies/chebi/terms/http%253A%252F%252Fpurl.obolibrary.org%252Fobo%252FCHEBI_33232/hierarchicalChildren?size=1000&lang=en&includeObsoleteEntities=undefined
https://www.ebi.ac.uk/ols4/api/ontologies/chebi/terms/http%253A%252F%252Fpurl.obolibrary.org%252Fobo%252FCHEBI_50906/hierarchicalChildren?size=1000&lang=en&includeObsoleteEntities=undefined
https://www.ebi.ac.uk/ols4/api/ontologies/chebi/terms/http%253A%252F%252Fpurl.obolibrary.org%252Fobo%252FCHEBI_33232/hierarchicalChildren?size=1000&lang=en&includeObsoleteEntities=undefined

@deepananbu @giraygi
As tested, works for class trees but it seems not implemented for property tree


[DO NOT MERGE] Update SSL certificates for tests

[ ] clean up
[ ] rename mongodb-ssl to mongodb_ssl
[ ] put docs under tests/backend/mongodb_ssl/SSL.rst
[ ] figure out what's up with sslAllowInvalidHostnames config option (c1ebf21d906c307495bf82c61b69dbbd79ed1601)

To test locally a docker-compose file has been added. To use it:
One shell for mongo:
$ docker-compose -f docker-compose.yml -f docker-compose.ssl.yml up mdb

One shell to run the tests:
$ docker-compose -f docker-compose.yml -f docker-compose.ssl.yml run --rm bdb bash
pytest -v tests/backend/mongodb-ssl/test_ssl_connection.py::test_ssl_get_connection_returns_the_correct_instance

Who do you want to review this?

Who do you want to review this?

This is not for review but for "fix"! :smile:

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1968   +/-   ##
=======================================
  Coverage   98.05%   98.05%
=======================================
  Files          60       60
  Lines        3040     3040
=======================================
  Hits         2981     2981
  Misses         59       59

This PR will be mainly used to address the points mentioned above in the check boxes.
The change of certificates and keys is now in  PR #1979. This should allow for a faster resolution of the problem, leaving more time to address less urgent matters.