thank you!

I was trying to set up my own websocket connection to streamelements but the url of their documentation seemed outdated. The url I found in the StreamElementsClient.cs file worked immediately, so I just wanted to thank you for your efforts.
Would you care to explain how you found that url? I'm very interested!

Hey I think that came from the original library I made a custom fork from:
https://github.com/swiftyspiffy/StreamElementsNET/blob/master/StreamElementsNET/StreamElementsNET/Client.cs#L10
From what I remember I used their library but had to make some PRs but the PRs were not actioned:
https://github.com/swiftyspiffy/StreamElementsNET/pull/6
https://github.com/swiftyspiffy/StreamElementsNET/pull/5
So I just had to make a custom fork, which I then wrapped with the rx layer, I only really have a working knowledge of their APIs but it was enough to make the changes I needed.


dtest for 8989 & 9502

dtest for "Reading from table which contains collection type using token function and with CL > ONE causes overwhelming writes to replicas" (CASSANDRA-8989)

Thanks. +1


Update to go 1.17

As far as I understand there should be no problem with that + it can make the development flow easier (see https://github.com/observatorium/api/pull/252#discussion_r832142509)

addressed here https://github.com/observatorium/api/pull/281


Add vscode-pull-request-github recommandation

Fixes #2

Note.
In order to avoid [Info] No remote with name 'upstream' found, workspace settings are revised as:
    "githubPullRequests.remotes": [
      "origin"
    ]


problem with proxy

BUG:
Trying to execute latest rancher 2.2.0-alpha5
Steps to reproduce (least amount of steps as possible):
Result:
2019/02/05 14:44:45 [ERROR] failed to serve UI: Get https://releases.rancher.com/ui/latest2/index.html: dial tcp <IP_ADDRESS>:443: connect: connection timed out
Other details that may be helpful:
Environment information

Rancher version 2.2.0-alpha5
single install

I have already set the HTTP_PROXY info as follows
[root@rancher ~]# more .docker/config.json
{
 "proxies":
 {
   "default":
   {
     "httpProxy": "http://xxxxx",
     "httpsProxy": "http://xxxxx",
     "noProxy": "localhost,<IP_ADDRESS>,xxxxx"
   }
 }
}
[root@rancher ~]# more /etc/systemd/system/docker.service.d/http-proxy.conf
[Service]
Environment="HTTP_PROXY=xxxxx"
Environment="HTTPS_PROXY=xxxxx"
Environment="NO_PROXY=localhost,<IP_ADDRESS>,xxxx"

Rancher web page does not show up but something is going since it present me with the certificate exception of being a self signed one.
Seems that it looks for a non existent page and get stuck there, not being able to serve any interface.

this does not happen with 2.1.6 release

Alpha5 is incorrectly pointing at our CDN (which is used intentionally for master build) instead of using a local copy of the UI.  We'll get another tag up soon.

@gioppoluca we just pushed alpha6 which should address that. We are in the process of QAing it ourselves, but i wanted to let you know in case you had time to give it a psin

Note that this bug would also cause alpha5 to always pull the UI from the "lastest2" version off of the CDN, which means it would be constantly updating, which would be bad because the backend code would be fixed at alpha5

This issue is fixed in rancher/rancher:v2.2.0-alpha6 release.
When UI loads in js , request URL points to <rancher server ip> as expected.
Sample js call made by UI:
Request URL: https://releases.rancher.com/ui/latest2/assets/vendor.js — in alpha5
Request URL: https://<rancher server ip>/assets/ui-2bfa2b2b0c0b42c00b728a1bcae1238a.js - in alpha6


sorting

i can't seem to figure out if there is a way to 'sort' the selected values, based on a field. so the selected values for example gets sorted desc. when showing in edit form mode?
i'm not sure if possible, but i also need a way to limit the combox to selections to fields that are not yet selected in another row. is that possible+
thanks for an awesome combox feature :)

You can configure it in the fetchxml


errorMessageFormatter is not working properly (or just a diff in ladybug report?)

Describe the issue
After a FF-upgrade to version 7.7-20210429.144344 (and the new stub4testtool), I've a diff in one of my ladybug tests.
In my testcase, the input is not well-formed (I'll include the input file), so this needs to be handled by the errorMessageFormatter. The result is a  exception which is taking a very long time in the ladybug.
One "strange" thing: when I use "test a pipeline" I actually still see in the result (but not in ladybug) as result the errorMessageFormatter result.
Reporter
Laura Nauta-Timp
Screenshots

Pipeline ProcessDocumentRR (1).zip
Configuration
Ibis4pub --> getdoc
Input
It's the inputfile of scenario 12-01 (getdoc config, ibis4publishing):
<?xml version="1.0" encoding="UTF-8"?> <Publishing> 	<RequestorId>12345</RequestorId> 	<TransactionId>T12345</TransactionId> 	<Destination>MQ1</Destination> 	<ProcessCode>abc</ProcessCode> 	<PriorityCode>123</PriorityCode> 	<EventKey>1</EventKey> 	<Action>
Environment
LOC
Additional Context
Here's the code:
`
	<errorMessageFormatter className="nl.nn.adapterframework.errormessageformatters.XslErrorMessageFormatter" styleSheet="xsl/GenericErrorReply.xsl">
          <param name="from" value="ProcessDocumentRR"/>
    </errorMessageFormatter>
	`

Is already fixed after change in stub4testtool by ricardo


resume non-existent changefeed, cli don't report any error

Bug Report
Please answer these questions before submitting your issue. Thanks!

What did you do? If possible, provide a recipe for reproducing the error.

Resume a changefeed which not existed,

What did you expect to see?

Cli report error like:  There's no changefeed "replication-task"...

What did you see instead?

It seems cli can resume non-existent cf.

Versions of the cluster

Upstream TiDB cluster version (execute SELECT tidb_version(); in a MySQL client):
5.0.0-nightly 5-24-2021

TiCDC version (execute cdc version):
5.0.0-nightly 5-24-2021

I am working on this.
/assign

I can reproduce it.
Currently, we ignore the changefeed non-existent error, see: https://github.com/pingcap/ticdc/blob/d933dd17544711f6fed721723270bb4408882d7e/cdc/http_handler.go #L305
Discussed offline, we may fix it when the API is rewritten in the next sprint.
cc: @leoppro

/unassign

Close it since it is stale. It has been fix in > v6.1.0.


MINOR; Add producer id in exceptions thrown by ProducerStateManager

This patch adds producer id in exceptions thrown by the ProducerStateManager. It was already there in some cases but was not in others. This is really helpful to have when troubleshooting. Otherwise, it is not possible to correlate broker's logs with producer's logs.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@chia7712 Thanks for your comments. I have addressed them. Could you take another look at the PR?

@chia7712 Thanks for your comments. I have addressed them. Could you take another look at the PR?


Problem when Rendering a huge Scene

I am using this libarray to make story for a 600 commits
correcting me if I am wrong
You are using Manim Libaray to make the animation
When I render it tell for huge Scene use --disable_caching for faster
But it's not an option in your excutabale
Is not possible because you need cache for somthing later ?
I don't mind waiting but it would be much better if I can make the process faster

I have made a pull Request to what I think would be simple solution you could Review it and see if it will work and give your thoughts

This project sadly looks abandoned

sadly


running time for building database

Hi, I'm try to build a database for kASA that includes 40 genomes (in total about 11G) using 10 cores and 30G. The job has been running for almost 3 days and hasn't been finished yet. I'm wondering if it's normal or is there any issue?
Thanks in advance.
Best regards,
Hien

Hi, thanks for your quick response.
The genome files are zipped with gzip. There's not any progress percentage printed. This is the whole log file now:
OUT: kASA version 1.4.7 ran on Linux at Wed Mar 13 17:56:20 2023 OUT: kASA build -c database/kASA/db/content.tsv -d database/kASA/db/index_40 -i database/kASA/db/assemblies/ -m 30g -n 10 -t kASA/tmp  OUT: STXXL-MSG STXXL v1.4.99 (prerelease/Release) OUT: STXXL-MSG Disk 'kASA/tmpstxxl_temp_0.tmp' is allocated, space: 1 MiB, I/O implementation: syscall delete_on_exit direct=on queue=0 devid=0 unlink_on_open
I'm running it on a slurm cluster
Best regards,

Thanks for the info!
There are some issues with your call. It should be:
kASA build -c database/kASA/db/content.tsv -d database/kASA/db/index_40 -i database/kASA/db/assemblies/ -m 30 -n 10 -t kASA/tmp/
Because 1. the memory flag must have no letter next to the number. It's always in Gigabytes. 2. the temporary folder needs to end with a /.
Maybe try that first. If it does not print more than you've already seen, try adding --debug to your call and send me the output please.
Just in general: If your cluster is using HDDs then kASA will take a while because it wasn't designed for them.

Thank you. I've edited the script as you told and re -launched the job. I will update the progress.
Best,

sorry I forgot to update that the job had finished successfully after running for about 1 day.
Thanks for your help.


Fix "Blockchain must contain a blockchain state" error

This can be reproduced on fresh local system on windows platform
make dev-initialize-blockchain works
make generate-blockchain fails

@fonar we do not support Windows

won't fix, since we do not support Windows


chan.options[0] is undefined (OpenWrt 22.03.0-rc6 r19590-042d558536 / LuCI openwrt-22.03 branch git-22.204.42822-9a18337)

OpenWrt 22.03.0-rc6 r19590-042d558536 / LuCI openwrt-22.03 branch git-22.204.42822-9a18337
Netgear 6220 flashed from version 21.02
some day i lost connection to my wifi 2.4
i wanted to provide new network i have:
chan.options[0] is undefined
my /etc/config/wireless:
config wifi-iface 'default_radio1'
option device 'radio1'
option network 'lan'
option mode 'ap'
option key 'mywifipassword'
option ssid 'OpenWrt'
option encryption 'none'
config wifi-device 'radio0'
option type 'mac80211'
option path '1e140000.pcie/pci0000:00/0000:00:01.0/0000:02:00.0'
option cell_density '0'
option hwmode '11a'
config wifi-device 'radio1'
option type 'mac80211'
option path '1e140000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0'
option channel '36'
option band '5g'
option htmode 'VHT80'

can you give more info? Is this related to the chan analysis ?

To me it looks like you have half-new half-old WiFi options. The definition for radio0 and radio1 differ in style.
I would delete the /etc/config/wireless and reboot, so that your default  WiFi config gets re-created at he reboot in the current style. Then you can modify the config starting from  the current style. (But note that you need wired connection at that time)

Guys i will do what proposed hnyman and let you know. @Ansuel @hnyman

@hnyman @hnyman
Ok guys. Works after deleting /etc/config/wireless and reboot
Now i can add both configuration to 2.4 and 5.0 networks.
Hope it will solve my problem if not i will back to this forum
greetz


debug command and SLAAC test

Hi!
In this PR I introduce DEBUG COMMAND which can run any subprocess via comms_controller requests.
It is disabled by default.
MDM agent requests MDM server for debug_conf and store it to /opt/debug_config.json
I will create PR for server side soon.
This config looks like:
{"version":0,"payload":{"api_version":1,"role":"sleeve","debug_conf":[{"debug_mode":"disabled","rsyslog_addr":"<IP_ADDRESS>"}]}}

or
{"version":0,"payload":{"api_version":1,"role":"sleeve","debug_conf":[{"debug_mode":"enabled","rsyslog_addr":"<IP_ADDRESS>"}]}}

If debug_mode is enabled it is possible to use DEBUG COMMAND.
I have added cli example accordingly.
I also use this DEBUG COMMAND to test SLAAC in debug_tests folder.

FYI server side https://github.com/tiiuae/mdm-server/pull/5


Usage Question

As a first project gathering metrics I would like to set up AppMetrics reporting into InfluxDB using Grafana for visualization. To get a feeling on how everything works I wanted to set up a simple graph showing number of requests per minute for each endpoint over time.
I did find the "application.httprequests__transactions_per_endpoint" measurement in InfluxDB but I am having a hard time choosing the correct field for my graph. I kind of would have expected something like a counter that resets after being reported. Instead, the only counters I have found seem to count forever. The closest I could get is using the rate1m field. But when I have three requests in one minute and zero requests in the next, my graph is not showing three and zero. Instead it is showing a slow decay from three downwards that appears to take a lot longer than a minute.
I guess all this has to do with the reservoir feature but I'm not sure how to use that properly. After all I've got a time window of one minute during which I would like to collect data, so my assumption would be that my sliding window would be one minute. How does that translate into number of samples?
A bit of advice would be greatly appreciated and might also help others getting off to a better start.
Thanks.

I highly recommend you to watch the video of codahale, the creator of original AppMetric library (on which this port is based on). He explains it pretty well why average is bad, why you cannot just collect/store every measurement in application and many other things that you will give you an idea why this library and other similar contains a decent amount of code.
BTW, @alhardy already created sample dashboards which can be good starting point for you.

@michael-x  in terms of web metrics to influxdb, try importing the generic web dashboard into grafana. There is also an equivalent for ES. That should give you most, if not all metrics you get from other paid APM solutions.
Counters can be reset on reporting, please see the docs
Reservoirs are for sampling data and used for Histograms, more info and external references in the docs.
As @jenyayel mentioned you can also check the sample repo, and yep the codehal dropwizard metrics video is a great start. There's also a bunch of "getting started" info on the docs site.

@jenyayel thanks for the video link. It's a good introduction on the subject. One of the things that I took from the video is the "sense of recency" which is exactly what I was missing. Looking at the following graph from the generic dashboard showing graphs for the "last 5 minutes" you can see that the rpm value are still decaying, even if there has been zero requests for way more than an hour. The values that are graphed are tiny, but meaningless.

@alhardy unfortunately there is no description on the requirements for each of the dashboards. Some of them assume that you have a datasource named "Influx", mine was called something else. The generic dashboard is a little easier to use as you can pick the datasource, but even then it assumes that you've got an "env" tag and an "app" tag to select from. The "Organizing Metrics" page uses "app_name" instead of "app" for the application name. There are a couple of hurdles that one must take to get from zero to working dashboard.
You've mentioned that counters can be reset on reporting and looking at the docs I can see how I would have AppMetrics reset my counters, if I define my own counters. How would I change the behaviour of counters created by the middleware?

@michael-x values will decay to zero, you can play with alpha value and sample size of the Exponentially Decaying Resevoir, you could also adjust the grafana graph to set a Y-Min value and adjust the decimals show to your desire.
The dashbaords in the samples repo are just samples which I've used for testing and as a playground, not sure how you are wanting to re-purpose those those? Yes datasources in the sample dashbaords are tied to the sample apps as they haven't be built for anything other than being demos and for testing.
Re the generic dashabord, yes I've made that more generic to make it (hopefully) very easy to get started with little effort. I may at some stage script the influxdb and grafana setup using docker.
If you're not wanting to use env and/or app global tags you can just remove them from the dashbaord as well as the filtering/grouping on each graph. I think they are handy though, this has allowed me to re-use the same dashboard for all my api's across environments (uat/staging/production). For anything more specific to the app I just create a new dashboard(s) with those more app specific metrics e.g. number of user logins, emails sent or bounced etc.
app_name vs app, tags are just key values, it's really up to you to determine what tags your application needs at the end of the day. The "Organizing Metrics" page is just explaining how one can use tags etc.
The sandbox project gets you up and running only a few steps documented here for InfluxDB and here for ES.
What counters provided in the default metrics middleware are you wanting to reset? There is really only one counter provided which is an active request counter and is already being decremented, no need to reset it.

@alhardy Thanks for the elaborate reply. I appreciate the work that you've obviously put into the project. The point that I wanted to make was, that although one can find almost everything that you need on the web site, but it's not a smooth experience. You tell them where to look for sample dashboards, but you don't tell them that they need to have a data source "Influx" in Grafana to use them. You tell them that there is a generic dashboard, but you don't tell them to make sure to add tags for "app" and "env". It would be great to have a walk-through from zero to working dashboard, instead of a "have a look at the samples (and put the remaining puzzle pieces together)".
Regarding alpha values: looking at https://en.wikipedia.org/wiki/Moving_average#Exponential_moving_average there seems to be a difference between the definition of the alpha value for EWMAs and what is implemented for the Exponentially Decaying Reservoir. An alpha value of 0 should mean that S(t) = S(t-1), which means the sequence should always remain on its initial value, while an alpha value of 1 should mean that S(t) = Y(t), i.e. the sequence will always show the current value. If I start with 5 requests in the first period and then don't have any requests anymore, I should see a sequence of

5, 5, 5, 5, ... for alpha = 0 and
5, 0, 0, 0, ... for alpha = 1 and
5.0, 2.5, 1.25, 0.625, ... for alpha = 0.5

Unfortunately this is not at all what I'm observing. No matter what value I use for alpha, the curve always looks similar.

@michael-x Thanks for the feedback.
Yes I am assuming that users are already somewhat faimilar with Grafana, I don't really want to invest my efforts in documentating how to use Grafana though, those guys have already done a great job in documenting their product.
I don't mention the datasource for the samples because that's already configured in the sample code for which the dashboard belongs, I do however mention it for the generic dashboard which is meant for re-purposing, see "Create a new InfluxDB Database. Keep note of this for configuring the InfluxDB reporter in your web application and configuring the InfluxDB Datasource in Grafana".
Re a walkthrough, yeah that would be great, maybe you could a blog post?
Re EWMA and Exponentially Decaying Reservoir, yes those values are different, see the SimpleMeter vs DefaultForwardDecayingReservoir implementations. If you've found an issue there, would it be possible for you to implement a unit test demonstrating for me to look at?

I may at some stage script the influxdb and grafana setup using docker.
Really good idea!


Denon HEOS Devices not Connecting (@NathanCu @z3p337)

Describe the issue
Hey there Todd,
thanks for this awesome integration! Did you by chance ever try one of denons heos speakers? I guess they are similar to your bose soundtouchs. They are spotify connect only devices and seem to have a dynamic spotify device id. I just cant get them to respond reliably.  Everytime I leave home and use spotify within my car for example, home assistant completely loses the devices and the spotify integration only registers new spotify device ids, which are not translated to human readable names I gave them (e.g. kitchen, bathroom, etc).  As soon as I start to play some spotify songs on one of the speakers, the home assistant integration shows the correct names again.
I hoped, that SpotifyPlus would solve this and I think it really can.
I build a simple script that does the following:
action: spotifyplus.player_media_play_tracks
metadata: {}
data:
uris: spotify:playlist:4FhyjgN9pPxxxx
entity_id: media_player.spotifyplus_xxx
device_id: Badezimmer

However 9 out of 10 times I’m getting the following error. The 10th time it works flawlessly and the speaker starts playing:
Fehler: SAM0001E - An unhandled exception occured while processing method “GetInformation”.
HTTPConnectionPool(host=‘<IP_ADDRESS>’, port=51952): Max retries exceeded with url: /zc/0?action=getInfo&version=2.7.1
(Caused by NewConnectionError(‘<urllib3.connection.HTTPConnection object at 0x7f4d98f710>: Failed to establish a new connection: [Errno 111] Connection refused’))

The good thing is: It seems to know, how to address the speaker, even if home assistants spotify integration doesn't. It correctly resolves its ip address.
Do you have any advice maybe?
Thanks so much for the quick support! :slight_smile: Tried it out. It behaves the same. Sometimes it works, sometimes it doesn't and throws the “connection refused” error.
Seems like 50:50 success rate actually.
I tried to open the speakers ip-address with the port stated in the error (eg http://badezimmer:51952/) and get the same error. Chrome states “ERR_CONNECTION_REFUSED”.
The port that spotifyplus uses seems to be dynamic. Maybe denon heos only allows some of the used ports or something…

I am waiting on someone to run some Wireshark network traces for me on a Denon HEOS device (similar to yours maybe). After I get those, I should know a little bit better of what is going on with the Denon devices.
I don’t have any Denon devices to test with, so I am relying on others with Wireshark network tracing abilities to help me out.

@awagner64404
Do you have an HA Community forum account?  If so, just post your above reply to the SpotifyPlus Card Dashboard forum and I will send you a PM from there with my personal email address.  I really wish GH had a PM function.
Also, about the trace ... was the Denon device fully logged out when you started the trace?  If not, then you will want to re-run it after logging the Denon device out.  I basically need all activity between the Spotify player (desktop, or mobile) and the Denon device.  This should include at least 1 (or more) getInfo and addUser calls to the Spotify Connect Zeroconf web-server hosted by the Denon device.
A trace from HA to the device is not necessary - just need the one from an official Spotify App (desktop preferred if you have it, but mobile should be ok too I think).
I appreciate your help, and patience - thanks!
Todd

Your are welcome.
That's strange, as the error in GetInformation also appears when you only want to switch the title or album, even if a title was already playing and the device was logged in. A switch was hardly possible in that case.
Let me know if you need further information.
Andreas

Hi Andreas - I just pushed out SpotifyPlus v1.0.68 release. Can you give the new release a try with the Denon AVR scenario that we have been troubleshooting?
I added some logic in the underlying spotifywebapiPython package GetSpotifyConnectDevice method that first checks to see if the specified device is already in the device list. If found, then it will not disconnect / reconnect the device. Prior to this, it would always disconnect / reconnect the device. My thought there is that if the device is already in the list, then it should be connected and ready for immediate use.
I’m hoping that this fixes the Connection refused errors. My thought there is that the previous code was trying to reconnect too soon after issuing the disconnect, and the zeroconf web-service (running on the device) still had the session established with the disconnect call and could not establish a new session for the subsequent connect call (e.g. Connection refused) since the web-service only supports 1 connection at a time.
Please let me know, and thanks again for your help - much appreciated!
Todd

Hi Todd, my Denon Avr 1600X is now running without any problems. Great work and thanks for your efforts!!! Best regards
Stefan


Update github action to fit to latest golang

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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 50.204%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
862

Relevant Lines:
1717

💛  - Coveralls

LGTM !


Support HCP-compatible CIFTI outputs

For consideration after #1001 is merged.
CIFTI is in a somewhat weird state where pretty much every CIFTI file that exists was created by or for the HCP ecosystem, despite it being a generic format. Hence, almost every CIFTI is in the 91282 Greyordinate space, which is defined by the 32k_fs_LR surface space, and some unspecified variant of MNI152 for the subcortical volumetric space.
Right now we're targeting fsaverage5 for the surface space and MNI152NLin2009cAsym as the volumetric space subcortical voxels are aligned to. The primary advantage to the current approach is consistency with other FMRIPREP outputs, as well as standard FreeSurfer spaces.
If users are interested in directly comparing their data with HCP data, or using tools that assume HCP preprocessing, it may be useful to target the HCP grayordinate space.

I'm starting this up now - some thoughts/questions/concerns/etc going forward..

Do we want to add workbench as a dependency for this? This would be pretty useful for the surface conversion from fsnative to 32k among other things

additions:

an option hcp-32k to output_spaces
32k_fs_LR download to niworkflows
resample (ideally downsample) BOLD surfaces to 32k (2mm) resolution
resample BOLD to the hcp variant of MNI152 and use this atlas for subcortical mapping (@edickie do you happen to know this variants name?)
MSMSulc registration (maybe not in this PR, but thoughts on this?)

I may be overlooking some steps - feel free to suggest other additions

I don't think you can do it without wb_command as a dependency. It's pretty
critical for most of the surface warping and resampling steps..plus putting
the surfaces and subcortical data together into a cifti file. Is anyone
working on nipype interfaces for it? I don' t think I saw any last time I
looked.
I guess the 91282_Greyordinates and 32k_fs_LR are pretty much the same
"space":

(32k (left surface vertices) + 32k (right surface vertices) + 32k
subcortical voxels = 91282_Greyordinates)

MSMSulc (the newest version) registration is really computationally
expensive (it adds 2.5 hrs to the workflow on a 16 CPU machine). But those
at the HCP are insist that it is worth it (and that I make it the default
behaviour in ciftify). Also, the newest version of the MSM binaries are
only available fro academic use. So I think it is up to you.
On Wed, May 23, 2018 at 1:51 PM, Mathias Goncalves<EMAIL_ADDRESS>
wrote:

I'm starting this up now - some thoughts/questions/concerns/etc going
forward..

Do we want to add workbench as a dependency for this? This would be pretty
useful for the surface conversion from fsnative to 32k
https://webcache.googleusercontent.com/search?q=cache:wnOVLyExrosJ:https://wiki.humanconnectome.org/download/attachments/63078513/Resampling-FreeSurfer-HCP.pdf%3Fversion%3D1%26modificationDate%3D1472225460934%26api%3Dv2+&cd=2&hl=en&ct=clnk&gl=us
among other things

additions:

an option hcp-32k to output_spaces
32k_fs_LR download to niworkflows
resample (ideally downsample) BOLD surfaces to 32k (2mm) resolution
resample BOLD to the hcp variant of MNI152 and use this atlas
https://github.com/edickie/ciftify/blob/master/ciftify/data/91282_Greyordinates/Atlas_ROIs.2.nii.gz
for subcortical mapping (@edickie https://github.com/edickie do you
happen to know this variants name?)
MSMSulc registration (maybe not in this PR, but thoughts on this?)

I may be overlooking some steps - feel free to suggest other additions
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/poldracklab/fmriprep/issues/1025#issuecomment-391439496,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMl59rBsTKsOI68Sig5r55adIZ02taiYks5t1aGygaJpZM4Sdmn4
.

Adding the connectome workbench to the dependencies is fine with me.

Hi @oesteban - currently I have a few more pressing things, but will come back to this when I can.
fyi @edickie - we added some initial support for workbench interfaces to nipype

Hi all, I just recently started trying out fmriprep, after using predominantly HCP pipelines for a while. Has there been any progress on this issue? It would indeed be useful to output data that is in the same space as the HCP minimal preprocessing pipelines output. I can look into it with some guidance, if nobody else has time/interest to work through the issue.

Closing in favor of the smaller issues referenced above. I hope they cover what @effigies, @mgxd and @edickie discussed in the beginning. Please add anything I might have missed on those issues.
The idea would be to:

Avoid MSM for now. Let's get HCP-compatible ciftis and then ask the community whether we should integrate MSM for a more accurate output.
Use the average fsLR (which also dismisses the LR information, that would be somewhat following alternative C on the document @mgxd referenced above - https://wiki.humanconnectome.org/download/attachments/63078513/Resampling-FreeSurfer-HCP.pdf?version=1&modificationDate=1472225460934&api=v2)


Bulk import enhancements

We want to build the following enhancements to our Import from CSV feature.

Validate each content item before inserting. If it fails validation, add it to a list of errors. This list then is turned into a CSV file that is downloaded at the end of the bulk import process so the user knows which records failed to import successfully.
Swap out the CSV reader with one that is MIT licensed instead of Apache 2.0.
Support for attachment field type.

@apexdodge ,would like to work on this.

Is it fine if this https://github.com/drcolombo/CsvReader   (MIT License) is used.
Need your inputs on how support for attachment field type can be implemented(for Image we can have base64 string of that image in csv but for pdf's and other file formats not sure)

@smd-11, yes, this is a good task, thank you.

Yes, that library looks good. Go for it.
I'm thinking the user must provide a URL to a file. If the URL is valid, download the file into memory, upload using IFileStorageProvider, then save a MediaItem to the db table, and finally the Guid from the MediaItem that was just saved can be used as the value to save to the attachment field type.

Helpful example of file storage provider: https://github.com/RaythaHQ/raytha/blob/7a12f5685a66c2c75bdca8cc07edfdf45734535a/src/Raytha.Web/Areas/Admin/Controllers/MediaItemsController.cs#L77
Helpful example of validation of fields: https://github.com/RaythaHQ/raytha/blob/7a12f5685a66c2c75bdca8cc07edfdf45734535a/src/Raytha.Application/ContentItems/Commands/EditContentItem.cs#L42
You may want to rebase your fork from dev.
Let me know if you have any questions from that.
Thanks!

PR merged, moving to testing. Big thanks @smd-11

Fixed a blocker that was discovered during testing.
When choosing to use local storage instead of cloud storage, a crash occurs due to missing httpcontext in background task. This is now resolved and testing can be resumed.

Released with v1.1.3


Enable hypervisor mode if qemu-system-riscv64 is 6

In the version 6 of qemu-system-riscv64, we don't the the hypervisor extension enabled by default. This is problematic when we want to run qemu in qemu. This commits adds the required flag.

@CharlyCst You can already review. Tomorrow I test it on my lab machine

Hmmm, seems like the CI doesn't like the flag:
qemu-system-riscv64: can't apply global rv64-riscv-cpu.h=true: Property 'rv64-riscv-cpu.h' not found
It might be even older?

@CharlyCst Ready to review, now it works. The flag was wrong

Should we re-open the PR or keep it closed?


@orta => A few additions to analytics before release 📱

Specifically, adds tracking for active user signups, tracks umbrella event for all account creations, and tracks source of individual signup (twitter, fb, email).
Also removes a few unused constants.

So I, uhh, went to force-push an amended commit to this branch, but didn't realize I was on master. Fixing master first, then pushing up to here.

use make push to not have these problems again: https://github.com/artsy/eigen/blob/master/Makefile#L123-L130

:+1:

OK this should be good now.

OK cool :👍
Merge on green


Integer columns and other features

Hi,
I really like this library and I would love to contribute to it. Currently I have some use cases for integer columns, validations and some other features. If you are OK, I'm gonna create some PR soon.
Cheers

Hi,
Sounds good, feel free to send your PRs ;)

Integer column available in V2


[Usage]: Batching in online inference

Your current environment
The output of `python collect_env.py`

How would you like to use vllm
I have set up an API server through the command: docker pull vllm/vllm-openai:v0.5.3.post1. The server is running fine when I am giving requests through normal curl commands i.e. one request at a time. But I want vLLM to process requests(assuming one prompt per request) parallelly in the specified batch size. Right now I don't know the batch size in which vLLM internally processes the prompts.
Before submitting a new issue...

[X] Make sure you already searched for relevant issues, and asked the chatbot living at the bottom right corner of the documentation page, which can answer lots of frequently asked questions.

You can regard max_num_seqs as the batch size. Check out the list of engine arguments for more details.

Thanks


AAP-29902: generate_users_trials_reports: ensure the plan_id is valid

Ensure the plan_id parameter is correct or fallback on the name based lookup.

LGTM 👍 Welcome back.
I hope my work didn't make you cry much 😢

Thank you for the great work you did. I'm lucky to have you in the team :-).


Fix for [cri] ttrpc: closed during ListPodSandboxStats

Similar to https://github.com/containerd/containerd/pull/10023 we have another symptom that shows up in k8s CI job(s)

Some example CI runs are: (click on Kubernetes e2e suite: [It] [sig-node] NodeProblemDetector [NodeFeature:NodeProblemDetector] should run without error to expand to see the error, you click on Archive link to get to the kubelet and containerd logs as well)

https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-e2e-gci-gce-alpha-enabled-default/1808526993558343680
https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-e2e-gci-gce-alpha-enabled-default/1808495031716155392
https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-e2e-gci-gce-alpha-enabled-default/1808464328827867136
https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-e2e-gci-gce-alpha-enabled-default/1808381029463887872
https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-e2e-gci-gce-alpha-enabled-default/1808351836457930752

xref: https://github.com/kubernetes/kubernetes/issues/125874


Update example dependencies

The 0.1.0 broke with recent Elixir versions

Thanks a lot!

Thanks for building Tesla :) Already solved a problem in a super elegant way :) (Passing along Phoenix request-id header to upstream resources as a correlation ID)

Glad to hear that :)
Can you share that as an example?
On Sun, 11 Sep 2016 at 14:36, Tim Buchwaldt<EMAIL_ADDRESS>wrote:

Thanks for building Tesla :) Already solved a problem in a super elegant
way :) (Passing along Phoenix request-id header to upstream resources as a
correlation ID)
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/teamon/tesla/pull/21#issuecomment-246178055, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAAfkw-FrhYa3Miv1e1owd9Ma_RslpY8ks5qo_XegaJpZM4J5_nX
.

Sure can: https://gist.github.com/timbuchwaldt/5d089b827bd1c00411465b1169e4e406


fix(hmac): add missing www-authenticate headers

Summary
When kong returns 401 Unauthorized response it should return WWW-Authenticate header with proper challenge. HMAC auth was missing this header.
Related PRs:

https://github.com/Kong/kong/pull/11792
https://github.com/Kong/kong/pull/11794
https://github.com/Kong/kong/pull/11795
https://github.com/Kong/kong/pull/11820
https://github.com/Kong/kong/pull/11833

RFCs & Materials

https://httpwg.org/specs/rfc7235.html#status.401
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/WWW-Authenticate

Checklist

[x] The Pull Request has tests
[x] A changelog file has been created under changelog/unreleased/kong or skip-changelog label added on PR if changelog is unnecessary. README.md
[x] N/A There is a user-facing docs PR against https://github.com/Kong/docs.konghq.com - PUT DOCS PR HERE

Full changelog

add WWW-Authenticate header to hmac 401 response

Issue reference

Fix #7772
KAG-321

@nowNick please help and manually cherry-pick to ee, thanks.


auto translation for "before I die " title based on IP

Create the ability for the Before I Die... text displayed in the const presetText variable inside the MasonryBox.jsx file text box to automatically translate to a user/viers IP address. This is being worked on by @negar-75. Thank you!

hey @XanderRubio
when I wanted to push my commits in" feature-auto-translation-before-i-die "
I was warned by this:

@negar-75 Thanks for letting me know. I got this to work for myself after forking the Before I Die repo on my GitHub account and would get the same error. This is what I had to do, and then successfully added a test file to a pull request to the Before I Die Code Repo #61
I was getting the error when attempting to fetch the remote (which is the most updated version of the Before I Die Code repo) ⬇
<EMAIL_ADDRESS>Permission denied (publickey). fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists.
Can you run git fetch upstream and not get an error in your console?

This is now closed ✅ thanks to @negar-75 from her pull request #67 and was merged into the main branch from commit a4a46d3


[Bug]:The dataset is extracted from a file that is not in csv format

@jingkl Fixed. Please check and then close this issue.


custom image handler not working in 2.10

Hi
I use your examples to set a custom image handler but it not working in latest version,
When I downgrade vue2editor to 2.9.0 it works good.
Thanks

change @imageAdded to @image-added work for me

change @imageAdded to @image-added work for me

it is working!

change @imageAdded to @image-added work for me

Thanks it works ! Why is this not in the documentation ?


Some keywords contains URL-decoded-char can not get response in filtered stream

Code:
            var stream = Tweetinvi.Stream.CreateFilteredStream();
            stream.AddTrack("参加者募集！");
            stream.AddTrack(":参戦ID");
            stream.AddTrack("I need backup!");
            stream.AddTrack(":Battle ID");
            stream.AddCustomQueryParameter("count", "0");
            List<RaidTweet> list = new List<RaidTweet>();

            stream.MatchingTweetReceived += (sender, arg) =>
            {
                Console.WriteLine(arg.Tweet.Text);
            };
            stream.StartStreamMatchingAnyConditions();

With this code I can not get response from Twitter server. But when I use another language, the same keywords can get response. Then I captured the request pack.
In Tweetinvi's request, the body is track=%E5%8F%82%E5%8A%A0%E8%80%85%E5%8B%9F%E9%9B%86%EF%BC%81%2C:%E5%8F%82%E6%88%A6id%2Ci%20need%20backup!%2C:battle%20id&stall_warnings=true&count=0
and in another library, the body is count=0&track=%E5%8F%82%E5%8A%A0%E8%80%85%E5%8B%9F%E9%9B%86%EF%BC%81%2C%3A%E5%8F%82%E6%88%A6ID%2CI%20need%20backup%21%2C%3ABattle%20ID&stall_warnings=true
It seems like the ':' and '!' which is not URL encoded caused the problem.
Tweetinvi Version: 2.1.0
.NET Platform: .NET Core 2.1.4 & .NET Framework 4.6.2

Thanks for the feedback. It definitely looks like a bug.

Hello,
I have reviewed this issue. And the problem comes from the fact that the Track matcher of Tweetinvi only support words at the moment.
As changing this will require various thoughts in terms of design and performances I will have to move this to another version.
Though in the meantime you can use another event that is available to you as part of the FilteredStream.
stream.NonMatchingTweetReceived += (sender, eventArgs) =>
{
    var tweet = eventArgs.Tweet;
    // Perform your custom filtering here
};

It is not a new event. It is already available in 2.1.


Implement: InputDropdown

Background
The current InputDropdown component has been redesigned and now features two distinct types: label and value with accompanying visual changes. This ticket is to update our current component to align with this new design.

Spec sheet
Found here.

Related tickets

Design ticket: #349

@tihuan based on our pointing discussing yesterday, sounds like @masoudmanson will actually be taking this on

Oh perfect thank you! I'm actually on call next week for SC, so probably won't have much coding capacity. But the week after that I should be able to work on something!


Hashing Algorithm

We shouldn't be supporting any hashing algorithm older than SHA3. Perhaps we could support BLAKE2 as well but not required currently. Let's make SHA3 256 default for now.

Fixed in 30db842ffe5395c0c6c8c78a9078ac68f236f336; we now default to SHA3-256 and the documentation also reflects this. Thanks!


Cleanup

Please review the changes.  I did a travis build on Kitura-Starter-Bluemix with the apt-get stuff out of it and everything compiled... I think we can remove those from Package-Builder

https://travis-ci.org/IBM-Swift/Kitura-Starter-Bluemix/jobs/161713426 is the travis build link

I had to add back in libcurl so that the tests on Kitura-Net would pass

im going to merge this into master


xADDomain needs unit tests for Get, Set and Test

@TravisEz13 FYI - I'm working on this whilst fixing #27, #32, #38, #47, #52 and #53 in the process. I think that'll close about half of the outstanding issues!

@iainbrighton Thanks.


Try updating to pulumi/pkg that requires dotnet6

This is looking viable, will wait until Pulumi ships the pkg/ change in the upcoming stable version and upgrade then.

Obsolete


[BUG] Unable to install pmdarima via Conda

Describe the bug
As pmdarima is a soft dependency, and is necessary for AutoARIMA, I am currently trying to install pmdarima via the conda route alongside sktime. Unfortunately, I'm unable to install pmdarima AND sktime via conda channels for a feedstock as it results in package conflicts.
To Reproduce
conda install pmdarima
conda install sktime
Essentially trying to install both pmdarima and sktime via conda results in conflicts.
Expected behavior
There shouldn't be any conflicts or the appropriate packages should be installed/upgraded/downgraded.
Versions
numpy >= 1.19.1
pandas >= 1.1.0
scikit-learn >= 0.23.1
System:
python: 3.8.0 | packaged by conda-forge | (default, Nov 22 2019, 19:11:19)  [Clang 9.0.0 (tags/RELEASE_900/final)]
executable: /Users/parthiv.naresh/miniconda3/envs/main/bin/python
machine: macOS-10.15.7-x86_64-i386-64bit
Python dependencies:
pip: 21.1.1
setuptools: 49.6.0.post20210108
sklearn: 0.24.2
sktime: 0.6.0
statsmodels: 0.12.2
numpy: 1.19.5
scipy: 1.6.3
Cython: 0.29.17
pandas: 1.2.4
matplotlib: 3.4.1
joblib: 1.0.1
numba: 0.52.0
pmdarima: 1.8.0
tsfresh: None

@ParthivNaresh wasn't aware of this, but I can reproduce the package conflict. Would you like to look into it and see which requirements we have to adjust to avoid the conflict?

@mloning From what I understand, pmdarima requires statsmodels to be >=0.11,<0.12, while sktime requires statsmodels to be >=0.12.1. I haven't been able to find any combination of requirements so far that can fix it. Even installing sktime and pmdarima (in either order) without pinning versions results in this error. As far as I can see, there's no way to install them both via conda due to conflicting dependencies.

Thanks @ParthivNaresh for raising the issue here https://github.com/alkaline-ml/pmdarima/issues/429

@ParthivNaresh I believe the issue has been resolved in alkaline-ml/pmdarima#429, I'll close this one here now, but please let me know if the issue persists. Thanks for pushing this!


"Open in Browser" should have a fallback for local branches with no upstream

So, I run "GitHub: Open Remote URL in Browser" and get an error message that the branch I'm currently editing has no upstream configured. I mean, this is true, but the behaviour is not at all what I expected.
What you can do in this case is run git log and find literally the next best thing. In most cases by far, it would be good enough. In fact, I can't imagine a single case where a user wouldn't expect this to happen.
I'll certainly implement this myself, most likely as a patch for this plugin, but let me know (in the comments to this) if you want the PR.

Hmm, that’s a tricky one. What if the file you’re on doesn’t exist on whatever branch (master?) you might open on remote? There is already a Open Remote URL in Browser (master) command. Is that sufficient?


Cache resulting folder name before changing dialog settings

Fixes issue #869
Brief summary of changes
When user makes selection of Folder on OSX, we use that as the new WorkingDirectory for future browsing. This minor refactoring avoids using selectedFile after changing the file browser settings (which wipes out the selected file on OSX but not windows)
Testing I've completed
Launched browse for folder dialog from scripting shell on osx and selected folders without issue or null ponters
CHANGELOG.md (choose one)

no need to update because bugfix

Build failure seems bogus. Any explanation @chrisdembia


[ThinLTO] Had anybody errors with "./crashpad_handler" while building?

I've got following errors while building:
FAILED: crashpad_handler
x86_64-pc-linux-gnu-clang++ -Wl,--build-id=sha1 -fPIC -Wl,-z,noexecstack -Wl,-z,relro -Wl,-z,now -Wl,-z,defs -Wl,--as-needed -fuse-ld=lld -Wl,--icf=all -Wl,--color-diagnostics -flto=thin -Wl,--thinlto-jobs=8 -Wl,--thinlto-cache-dir=thinlto-cache -Wl,--thinlto-cache-policy,cache_size=10\%:cache_size_bytes=10g:cache_size_files=100000 -Wl,--lto-O2 -fwhole-program-vtables -rdynamic -pie -Wl,--disable-new-dtags -Wl,-O1 -Wl,--as-needed -Wl,-plugin-opt,-import-instr-limit=30 -Wl,--thinlto-jobs=8 -o "./crashpad_handler" -Wl,--start-group @"./crashpad_handler.rsp"  -Wl,--end-group  -latomic -ldl -lpthread -lrt -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -levent -lz
ld.lld: error: undefined symbol: crashpad::Signals::InstallCrashHandlers(void (*)(int, siginfo_t*, void*), int, crashpad::Signals::OldActions*, std::set<int, std::less<int>, std::allocator<int> > const*)
>>> referenced by handler_main.cc
>>>               thinlto-cache/Thin-9443b6.tmp.o:(crashpad::HandlerMain(int, char**, std::vector<std::unique_ptr<crashpad::UserStreamDataSource, std::default_delete<crashpad::UserStreamDataSource> >, std::allocator<std::unique_ptr<crashpad::UserStreamDataSource, std::default_delete<crashpad::UserStreamDataSource> > > > const*))

ld.lld: error: undefined symbol: crashpad::Signals::InstallTerminateHandlers(void (*)(int, siginfo_t*, void*), int, crashpad::Signals::OldActions*)
>>> referenced by handler_main.cc
>>>               thinlto-cache/Thin-9443b6.tmp.o:(crashpad::HandlerMain(int, char**, std::vector<std::unique_ptr<crashpad::UserStreamDataSource, std::default_delete<crashpad::UserStreamDataSource> >, std::allocator<std::unique_ptr<crashpad::UserStreamDataSource, std::default_delete<crashpad::UserStreamDataSource> > > > const*))

ld.lld: error: undefined symbol: crashpad::StringToNumber(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, unsigned long*)
>>> referenced by handler_main.cc
>>>               thinlto-cache/Thin-9443b6.tmp.o:(crashpad::HandlerMain(int, char**, std::vector<std::unique_ptr<crashpad::UserStreamDataSource, std::default_delete<crashpad::UserStreamDataSource> >, std::allocator<std::unique_ptr<crashpad::UserStreamDataSource, std::default_delete<crashpad::UserStreamDataSource> > > > const*))

ld.lld: error: undefined symbol: crashpad::StringToNumber(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, unsigned long*)
>>> referenced by handler_main.cc
>>>               thinlto-cache/Thin-9443b6.tmp.o:(crashpad::HandlerMain(int, char**, std::vector<std::unique_ptr<crashpad::UserStreamDataSource, std::default_delete<crashpad::UserStreamDataSource> >, std::allocator<std::unique_ptr<crashpad::UserStreamDataSource, std::default_delete<crashpad::UserStreamDataSource> > > > const*))

ld.lld: error: undefined symbol: crashpad::Paths::Executable(base::FilePath*)
>>> referenced by handler_main.cc
>>>               thinlto-cache/Thin-9443b6.tmp.o:(crashpad::HandlerMain(int, char**, std::vector<std::unique_ptr<crashpad::UserStreamDataSource, std::default_delete<crashpad::UserStreamDataSource> >, std::allocator<std::unique_ptr<crashpad::UserStreamDataSource, std::default_delete<crashpad::UserStreamDataSource> > > > const*))

ld.lld: error: undefined symbol: crashpad::Metrics::HandlerLifetimeMilestone(crashpad::Metrics::LifetimeMilestone)
>>> referenced by handler_main.cc
>>>               thinlto-cache/Thin-9443b6.tmp.o:(crashpad::HandlerMain(int, char**, std::vector<std::unique_ptr<crashpad::UserStreamDataSource, std::default_delete<crashpad::UserStreamDataSource> >, std::allocator<std::unique_ptr<crashpad::UserStreamDataSource, std::default_delete<crashpad::UserStreamDataSource> > > > const*))

ld.lld: error: undefined symbol: crashpad::CrashpadClient::CrashpadClient()
>>> referenced by handler_main.cc
>>>               thinlto-cache/Thin-9443b6.tmp.o:(crashpad::HandlerMain(int, char**, std::vector<std::unique_ptr<crashpad::UserStreamDataSource, std::default_delete<crashpad::UserStreamDataSource> >, std::allocator<std::unique_ptr<crashpad::UserStreamDataSource, std::default_delete<crashpad::UserStreamDataSource> > > > const*))

ld.lld: error: undefined symbol: crashpad::CrashpadClient::StartHandler(base::FilePath const&, base::FilePath const&, base::FilePath const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::map<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::less<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > > const&, std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > const&, bool, bool)
>>> referenced by handler_main.cc
>>>               thinlto-cache/Thin-9443b6.tmp.o:(crashpad::HandlerMain(int, char**, std::vector<std::unique_ptr<crashpad::UserStreamDataSource, std::default_delete<crashpad::UserStreamDataSource> >, std::allocator<std::unique_ptr<crashpad::UserStreamDataSource, std::default_delete<crashpad::UserStreamDataSource> > > > const*))

ld.lld: error: undefined symbol: crashpad::CrashpadClient::~CrashpadClient()
>>> referenced by handler_main.cc
>>>               thinlto-cache/Thin-9443b6.tmp.o:(crashpad::HandlerMain(int, char**, std::vector<std::unique_ptr<crashpad::UserStreamDataSource, std::default_delete<crashpad::UserStreamDataSource> >, std::allocator<std::unique_ptr<crashpad::UserStreamDataSource, std::default_delete<crashpad::UserStreamDataSource> > > > const*))

ld.lld: error: undefined symbol: crashpad::CrashpadInfo::GetCrashpadInfo()
>>> referenced by handler_main.cc
>>>               thinlto-cache/Thin-9443b6.tmp.o:(crashpad::HandlerMain(int, char**, std::vector<std::unique_ptr<crashpad::UserStreamDataSource, std::default_delete<crashpad::UserStreamDataSource> >, std::allocator<std::unique_ptr<crashpad::UserStreamDataSource, std::default_delete<crashpad::UserStreamDataSource> > > > const*))

ld.lld: error: undefined symbol: crashpad::CrashReportDatabase::Initialize(base::FilePath const&)
>>> referenced by handler_main.cc
>>>               thinlto-cache/Thin-9443b6.tmp.o:(crashpad::HandlerMain(int, char**, std::vector<std::unique_ptr<crashpad::UserStreamDataSource, std::default_delete<crashpad::UserStreamDataSource> >, std::allocator<std::unique_ptr<crashpad::UserStreamDataSource, std::default_delete<crashpad::UserStreamDataSource> > > > const*))

ld.lld: error: undefined symbol: crashpad::Metrics::HandlerLifetimeMilestone(crashpad::Metrics::LifetimeMilestone)
>>> referenced by handler_main.cc
>>>               thinlto-cache/Thin-9443b6.tmp.o:(crashpad::HandlerMain(int, char**, std::vector<std::unique_ptr<crashpad::UserStreamDataSource, std::default_delete<crashpad::UserStreamDataSource> >, std::allocator<std::unique_ptr<crashpad::UserStreamDataSource, std::default_delete<crashpad::UserStreamDataSource> > > > const*))

ld.lld: error: undefined symbol: crashpad::ExceptionHandlerProtocol::ClientInformation::ClientInformation()
>>> referenced by handler_main.cc
>>>               thinlto-cache/Thin-9443b6.tmp.o:(crashpad::HandlerMain(int, char**, std::vector<std::unique_ptr<crashpad::UserStreamDataSource, std::default_delete<crashpad::UserStreamDataSource> >, std::allocator<std::unique_ptr<crashpad::UserStreamDataSource, std::default_delete<crashpad::UserStreamDataSource> > > > const*))

ld.lld: error: undefined symbol: crashpad::Metrics::HandlerLifetimeMilestone(crashpad::Metrics::LifetimeMilestone)
>>> referenced by handler_main.cc
>>>               thinlto-cache/Thin-9443b6.tmp.o:(crashpad::HandlerMain(int, char**, std::vector<std::unique_ptr<crashpad::UserStreamDataSource, std::default_delete<crashpad::UserStreamDataSource> >, std::allocator<std::unique_ptr<crashpad::UserStreamDataSource, std::default_delete<crashpad::UserStreamDataSource> > > > const*))

ld.lld: error: undefined symbol: crashpad::PruneCondition::GetDefault()
>>> referenced by handler_main.cc
>>>               thinlto-cache/Thin-9443b6.tmp.o:(crashpad::HandlerMain(int, char**, std::vector<std::unique_ptr<crashpad::UserStreamDataSource, std::default_delete<crashpad::UserStreamDataSource> >, std::allocator<std::unique_ptr<crashpad::UserStreamDataSource, std::default_delete<crashpad::UserStreamDataSource> > > > const*))

ld.lld: error: undefined symbol: crashpad::WorkerThread::WorkerThread(double, crashpad::WorkerThread::Delegate*)
>>> referenced by handler_main.cc
>>>               thinlto-cache/Thin-9443b6.tmp.o:(crashpad::HandlerMain(int, char**, std::vector<std::unique_ptr<crashpad::UserStreamDataSource, std::default_delete<crashpad::UserStreamDataSource> >, std::allocator<std::unique_ptr<crashpad::UserStreamDataSource, std::default_delete<crashpad::UserStreamDataSource> > > > const*))

ld.lld: error: undefined symbol: crashpad::Metrics::HandlerLifetimeMilestone(crashpad::Metrics::LifetimeMilestone)
>>> referenced by handler_main.cc
>>>               thinlto-cache/Thin-9443b6.tmp.o:(crashpad::HandlerMain(int, char**, std::vector<std::unique_ptr<crashpad::UserStreamDataSource, std::default_delete<crashpad::UserStreamDataSource> >, std::allocator<std::unique_ptr<crashpad::UserStreamDataSource, std::default_delete<crashpad::UserStreamDataSource> > > > const*))

ld.lld: error: undefined symbol: crashpad::Metrics::HandlerLifetimeMilestone(crashpad::Metrics::LifetimeMilestone)
>>> referenced by handler_main.cc
>>>               thinlto-cache/Thin-9443b6.tmp.o:(crashpad::HandlerMain(int, char**, std::vector<std::unique_ptr<crashpad::UserStreamDataSource, std::default_delete<crashpad::UserStreamDataSource> >, std::allocator<std::unique_ptr<crashpad::UserStreamDataSource, std::default_delete<crashpad::UserStreamDataSource> > > > const*))

ld.lld: error: undefined symbol: crashpad::Metrics::HandlerLifetimeMilestone(crashpad::Metrics::LifetimeMilestone)
>>> referenced by handler_main.cc
>>>               thinlto-cache/Thin-9443b6.tmp.o:(crashpad::HandlerMain(int, char**, std::vector<std::unique_ptr<crashpad::UserStreamDataSource, std::default_delete<crashpad::UserStreamDataSource> >, std::allocator<std::unique_ptr<crashpad::UserStreamDataSource, std::default_delete<crashpad::UserStreamDataSource> > > > const*))

ld.lld: error: undefined symbol: crashpad::SplitStringFirst(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, char, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >*)
>>> referenced by handler_main.cc
>>>               thinlto-cache/Thin-9443b6.tmp.o:(crashpad::(anonymous namespace)::AddKeyValueToMap(std::map<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::less<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > >*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, char const*))

ld.lld: error: too many errors emitted, stopping now (use -error-limit=0 to see all errors)
clang-8: error: linker command failed with exit code 1 (use -v to see invocation)

What could that be?

could be related with debug symbols

Looks like it's trying to link, but cannot find all the needed object files…
@jstkdng I'm comparing my build to your PKGBUILD and cannot see any significant difference. :( Does your PKGBUILD successfully build ungoogled-chromium?

Looks like thinlto in lld8 crashes this.
Lld9 has no such issue with thinlto enabled.

I was told that ungoogled-chromium builds just fine with thinlto by lld 9. I assumed that lld 8 fails and lld 9 succeeds.
Recently I decided to check this and tried compiling with thinlto and lld 9. Unfortunately the outcome was exactly the same failure.
I then asked for gn flags, that were used to compile and found 2 differing. Using those myself didn't change anything w.r.t. this failure. I tried using exactly the same gn flags. Still fails. I then used the not only gn flags, but also all of the *FLAGS. But this also resulted in the same fail.
Now I'm stuck and need your help… badly
What else can I check/try?

@PF4Public
yes, my PKGBUILD succesfully builds.
Here are all the files I use: https://build.opensuse.org/package/show/home:justkidding/ungoogled-chromium
and the build log: https://build.opensuse.org/package/live_build_log/home:justkidding/ungoogled-chromium/Arch/x86_64
I disabled builds just to avoid auto building btw.

@jstkdng Thanks for reply.
Indeed your log has:

[ 1306s] [10927/22471] LINK ./crashpad_handler

So, in your configuration it seems to be compiling fine.
But you do not seem to be using 'thinlto' feature of clang, right?

nope, I don't think so. Why are you trying to build this with thinlto? would that make the browser faster?

I say for myself.
1 - it has such feature
2 - yes, a little bit faster

After a number of trials and errors I've found the culprit.
On my system default compiler is gcc and by compiling UGC I redefine CC and CXX to clang, which is sufficient most of the time. But when it comes to thinlto, it fails. I have also tried compiling crashpad_handler on 78, and it also failed, even though 78 release itself does compile successfully. crashpad_handler probably wasn't a hard dependency until 79, so I didn't notice this earlier.
@perfect7gentleman uses clang by default and has no issues with thinlto. He kindly provided me his complete build logs and all his configs with respect to ungoogled-chromium. Turns out, on his system AR is also switched to 'llvm-ar' instead of 'gcc-ar'. And indeed, changing AR along with CC and CXX solved this issue with thinlto for me.
I suppose, that object files generated by 'gcc-ar' are incompatible with clang's thinlto feature. but not all of them though. Mangling in c++ is probably somehow affected.

Why are you trying to build this with thinlto?

@jstkdng  I did recently rebuild some of the packages with lto on my system and the result was a tangible speedup of those, so I suppose, lto has some real optimizations in it after all.
Sorry for off-topic'ing

Hi!
I'm trying to build chromium on Ubuntu Impish, however, I'm stuck with this error.
I'm following this recipe: https://salsa.debian.org/chromium-team/chromium.
@PF4Public , can you tell me exactly what I need to change in order to build successfully?
Thank you!
Jhonny Oliveira
https://xtradeb.net

@jhonny-oliveira see my comment above

Turns out, on his system AR is also switched to 'llvm-ar' instead of 'gcc-ar'. And indeed, changing AR along with CC and CXX solved this issue with thinlto for me.

Ok! Eventually I got it. I changed ar for llvm-ar and nm for llvm-nm and it worked. Just like you suggested. Thank you!


Reg / Login

Build out the registration and login forms

working on this too!

Thanks for your interest @harshil1712
Have you seen the screens?
https://github.com/phavor/cheetbook/blob/staging/client/src/images/Reg.png
You can do that material ui or just css(scss)

@phavor yeah I have seen the screens. I will use material ui and soon send a PR for review

No problems @harshil1712


Make request public

Making make_request method public to fix issue #10

Coverage remained the same at 90.099% when pulling 3fbede43f5a424aa2a34e86398701c070e5b5c9b on make_request_public into 615ce5bf16968aa143935aa7e12def0bf8ee8afb on master.

Coverage remained the same at 90.099% when pulling 3fbede43f5a424aa2a34e86398701c070e5b5c9b on make_request_public into 615ce5bf16968aa143935aa7e12def0bf8ee8afb on master.


Look through declarations that start in a macro but end up in a source file when searching for a declaration at some location

Otherwise, rename can't be initiated inside of an NS_ENUM
rdar://32934347

Committed To https://github.com/apple/swift-clang
8a4f612879..6ea0e95dbd  upstream-with-swift -> upstream-with-swift


Talos Vega 11 Fail to glob topology properties

On Talos /dev/kfd isn't present causing this in logs
{"level":"error","ts":1636410993.0903304,"logger":"amdgpu-node-labeller","msg":"Fail to glob topology properties","stacktrace":"github.com/RadeonOpenCompute/k8s-device-plugin/vendor/github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/src/github.com/RadeonOpenCompute/k8s-device-plugin/vendor/github.com/go-logr/zapr/zapr.go:132\nmain.glob..func5\n\t/go/src/github.com/RadeonOpenCompute/k8s-device-plugin/cmd/k8s-node-labeller/main.go:158\nmain.generateLabels\n\t/go/src/github.com/RadeonOpenCompute/k8s-device-plugin/cmd/k8s-node-labeller/main.go:249\nmain.main\n\t/go/src/github.com/RadeonOpenCompute/k8s-device-plugin/cmd/k8s-node-labeller/main.go:288\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:204"}

0/9 nodes are available: 3 node(s) had taint {node-role.kubernetes.io/master: }, that the pod didn't tolerate, 6 Insufficient amd.com/gpu.
Ryzen 5 2400G

Which distro/kernel/ROCm version are you using?

Talos
5.15
amd-gpu-helm-0.2.0

Unfortunately Talos is not a Linux distribution we currently support.  Also, Helm only deploys the device plugin and does not install the ROCm kernel driver.


Distributed Key Value Tensor Store

Is it possible to use streaming dataset as a distributed key value store?
i have a set of keys (strings like "xyz_123") each that correspond to an numpy array
ideally I can do something like
np_array = dataset["xyz_123"]

but i see with MDSWriter.write that the keys of the dataset are just sequential and i can't change them.
Is there a way to have a custom key for MDSWriter?

Hi @OrenLeung, what is the size of the dataset and how many unique keys you have in the dataset?

@karan6181  the size is about 1 TB and about 100k unique keys


[FEATURE REQUEST] Integration of MSYS2 package management with Pacman

Please confirm these before moving forward.

[x] I have searched for my feature proposal and have not found a work-in-progress/duplicate/resolved/discarded issue.
[X] This proposal is a completely new feature. If you want to suggest an improvement or an enhancement, please use this template.

Describe the new feature
Description:
MSYS2 is a popular Unix-like environment for Windows that uses the Pacman package manager to manage software and development tools. The integration of Pacman from MSYS2 into UniGetUI would enable users to manage Unix-like packages directly within the WingetUI interface. MSYS2 supports multiple environments such as mingw32, mingw64, clang32, clang64, and the now recommended default environment ucrt64.
Users should have the flexibility to select one or more environments in which to install packages. Additionally, there should be an option to configure UniGetUI to allow package management across multiple environments simultaneously. This would streamline the process for developers and users who rely on different toolchains provided by MSYS2.
Key implementation points:

MSYS2 installation detection:
UniGetUI should be able to detect a standard MSYS2 installation on the system. This could be achieved by scanning the system for the MSYS2 installation path (typically found in default directories) or reading system environment variables that indicate the presence of MSYS2.

Environment selection (Mingw, Clang, UCRT):

Users should have the ability to choose which MSYS2 environments they wish to use when installing packages (e.g., mingw64, ucrt64, clang64, etc.).
UniGetUI should offer the option to install and manage packages across multiple environments simultaneously.
There should be an interface to easily select, configure, and switch between these environments for package installation.

Repository and package management:

UniGetUI should allow access to the official MSYS2 Pacman repositories. Users should be able to update the package lists and manage software packages from these repositories, similar to how Pacman operates within the MSYS2 shell.
Package lists should be updatable through UniGetUI, either via a refresh button or scheduled checks for repository updates.

Package installation and updates:

The package installation and update process should mirror the functionality of Pacman, allowing users to install, update, and remove packages using the same options as available in the MSYS2 Pacman environment.
Support for handling dependencies and conflicts, as Pacman does natively, should be integrated into WingetUI.

Compatibility with existing package managers:

Pacman from MSYS2 should be seamlessly integrated alongside existing package managers in WingetUI (like winget, scoop, and chocolatey), ensuring that the user experience remains consistent and conflict-free.
Users should be able to manage MSYS2 Pacman packages separately from other package managers without interference or confusion.

Conclusion:
Describe how this new feature could help users
The integration of MSYS2 Pacman into UniGetUI would significantly enhance its capability to manage Unix-like development tools and libraries on Windows. This addition would be valuable for developers and advanced users who frequently work with different MSYS2 environments and toolchains.

This might be unusual but I figured it's worth adding: Git For Windows (which by itself is a modified MSYS2 distribution) also provides a "SDK", and it is basically an MSYS2 installation with Git For Windows repositories added.
They use pacman just like the upstream so it could be detected after the initial MSYS2 implementation land.


Istio operator is broken with access denied

Bug Description
In the new 1.12.1 Istio version deployed with Control Plane CR there are missing role.
Probably related to new Wasm API added.
istiod pods are unable to start with following error:
 error    watch error in cluster Kubernetes: failed to list *v1alpha1.WasmPlugin: wasmplugins.extensions.istio.io is forbidden: User "system:serviceaccount:istio-system:istiod-service-account" cannot list resource "wasmplugins" in API group "extensions.istio.io" at the cluster scope
Following fixes the issue:
Manually adding the rule to istiod-istio-system ClusterRole.
`rules:

verbs:
get
list
watch
update
patch
apiGroups:
extensions.istio.io
resources:
wasmplugins`

Reference: https://github.com/istio/istio/blob/32abef6667f8a6a70d92caaea71f07e33235885c/manifests/charts/base/files/gen-istio-cluster.yaml#L6397
As I understand this role is deprecated, so you probably need to add it here: https://github.com/istio/istio/blob/32abef6667f8a6a70d92caaea71f07e33235885c/manifests/charts/istio-control/istio-discovery/templates/clusterrole.yaml#L12
Version
All Istio tools of version 1.12.1. Latest released version at this point.

Additional Information
No response

Just figured out that new version was released today 1.12.2.
However, this bug is not fixed there as well

We should have the needed cluster role at https://github.com/istio/istio/blob/32abef6667f8a6a70d92caaea71f07e33235885c/manifests/charts/istio-control/istio-discovery/templates/clusterrole.yaml#L23. Would you mind to give more details on how you perform install exactly and what does your ControlPlane resource look like?

I received this error as well installing istio with istioctl and trying to change options after installation..

@dsielert is this transient? What does the istiod clusterrole look like?


audio negative startOffset bug

it seems right now.

@davrous will soon review this but you know this is holidays season.. :)

ok，haha.

the particle color lerp is very bored, i can't stand.

what's the problem?

There's no problem. I was just busy on other tasks. Sorry for being late. I'm going to have a look today or tomorrow and will merge quickly if everything is fine on my unit tests.

hi @wyklion. Thanks for the bug on this._startTime instead of startTime. But for the _startOffset, I can't see cases where it could be negative. Can you please elaborate on cases you've found?

@wyklion , you've also included unrelated modification to audio in your PR. Can you please submit individual and separated PR to the modifications you'd like to do to math.ts & so on?
Thanks!

@davrous

play(10)
after 5 second pause() // offset = -5
play() error...

i wrote it in early closed pr...
and what do you think about random lerp. if no use. i'll remove the change.
and another miss onError bug has been fixed by someone i can remove that also.
BUT! the audio definitely has the bug!...


fix gosimple suggestions

pkg/util/secretvalues/mask.go:52:5: S1011: should replace loop with `queue = append(queue, dataArr...)` (gosimple)
pkg/util/parallel/parallel.go:150:34: S1030: should use buf.Bytes() instead of []byte(buf.String()) (gosimple)
pkg/util/parallel/worker.go:19:9: S1030: should use w.buf.Bytes() instead of []byte(w.buf.String()) (gosimple)
pkg/docker/image.go:94:8: S1003: should use strings.Contains(err.Error(), specificError) instead (gosimple)
pkg/docker/image.go:140:8: S1003: should use strings.Contains(err.Error(), specificError) instead (gosimple)
pkg/deploy/werf_chart/git_loader.go:38:4: S1023: redundant break statement (gosimple)
pkg/deploy/werf_chart/git_loader.go:44:4: S1023: redundant break statement (gosimple)
pkg/storage/manager/stages_storage.go:260:2: S1008: should use 'return m.StagesStorage.Address() != storage.LocalStorageAddress' instead of 'if m.StagesStorage.Address() == storage.LocalStorageAddress { return false }; return true' (gosimple)
pkg/util/path.go:113:6: S1003: should use strings.ContainsAny(patternComponents[patIdx], "*?[{\\") instead (gosimple)
integration/utils/docker/cli.go:188:7: S1003: should use strings.Contains(err.Error(), specificError) instead (gosimple)
integration/ansible/ansible_test.go:86:9: S1003: should use strings.Contains(line, `public key is not available: NO_PUBKEY`) instead (gosimple)
integration/ansible/ansible_test.go:96:9: S1003: should use strings.Contains(line, `apt 'Install package from new repository' [clickhouse-client]`) instead (gosimple)
integration/build/stapel_image/imports/imports_test.go:45:9: S1003: should use strings.Contains(line, "/myartifact/no-such-dir") instead (gosimple)
integration/build/stapel_image/imports/imports_test.go:55:9: S1003: should use strings.Contains(line, "/myartifact/file-no-such-file") instead (gosimple)
integration_k8s/releaseserver/helm_hooks_deleter_test.go:27:9: S1003: should use strings.Contains(line, "Waiting for resources elimination: jobs/migrate") instead (gosimple)
integration_k8s/releaseserver/kubedog_multitrack_test.go:113:9: S1003: should use strings.Contains(line, `1/1 allowed errors occurred for deploy/mydeploy1: continue tracking`) instead (gosimple)
integration_k8s/releaseserver/kubedog_multitrack_test.go:116:9: S1003: should use strings.Contains(line, `Allowed failures count for deploy/mydeploy1 exceeded 1 errors: stop tracking immediately!`) instead (gosimple)
integration_k8s/releaseserver/kubedog_multitrack_test.go:119:9: S1003: should use strings.Contains(line, "deploy/mydeploy1 ERROR:") instead (gosimple)
integration_k8s/releaseserver/resources_adopter_test.go:112:9: S1003: should use strings.Contains(line, fmt.Sprintf(`Deployment "mydeploy2" in namespace "%s" exists and cannot be imported into the current release`, namespace)) instead (gosimple)
integration_k8s/releaseserver/resources_adopter_test.go:116:9: S1003: should use strings.Contains(line, fmt.Sprintf(`Deployment "mydeploy4" in namespace "%s" exists and cannot be imported into the current release`, namespace)) instead (gosimple)
integration_k8s/releaseserver/resources_adopter_test.go:163:9: S1003: should use strings.Contains(line, fmt.Sprintf(`Deployment "mydeploy2" in namespace "%s" exists and cannot be imported into the current release`, namespace)) instead (gosimple)
integration_k8s/releaseserver/resources_adopter_test.go:167:9: S1003: should use strings.Contains(line, fmt.Sprintf(`Deployment "mydeploy4" in namespace "%s" exists and cannot be imported into the current release`, namespace)) instead (gosimple)
integration_k8s/releaseserver/resources_adopter_test.go:279:9: S1003: should use strings.Contains(line, fmt.Sprintf(`Deployment "mydeploy5" in namespace "%s" exists and cannot be imported into the current release`, namespace)) instead (gosimple)
pkg/deploy/werf_chart/werf_chart.go:110:2: S1011: should replace loop with `secretValuesFiles = append(secretValuesFiles, wc.SecretValueFiles...)` (gosimple)
pkg/deploy/werf_chart/werf_chart.go:189:2: S1011: should replace loop with `secretValuesFiles = append(secretValuesFiles, wc.SecretValueFiles...)` (gosimple)
cmd/werf/helm/helm.go:111:3: S1011: should replace loop with `commandsQueue = append(commandsQueue, cmd.Commands()...)` (gosimple)
pkg/deploy/werf_chart/werf_chart.go:64:51: S1019: should use make(map[string]string) instead (gosimple)
integration/build/stapel_image/build_phase/build_phase_test.go:81:38: S1019: should use make(chan struct{}) instead (gosimple)
integration/build/stapel_image/build_phase/build_phase_test.go:82:39: S1019: should use make(chan struct{}) instead (gosimple)
pkg/git_repo/local.go:174:9: S1039: unnecessary use of fmt.Sprintf (gosimple)
pkg/build/builder/ansible.go:202:9: S1039: unnecessary use of fmt.Sprintf (gosimple)
pkg/build/conveyor.go:909:49: S1039: unnecessary use of fmt.Sprintf (gosimple)
integration/cleanup/cleanup_test.go:851:3: S1031: unnecessary nil check around range (gosimple)
cmd/werf/common/common.go:1246:66: S1012: should use `time.Since` instead of `time.Now().Sub` (gosimple)
pkg/cleaning/cleanup.go:608:8: S1012: should use `time.Since` instead of `time.Now().Sub` (gosimple)
pkg/git_repo/remote.go:216:10: S1025: should use String() instead of fmt.Sprintf (gosimple)
pkg/storage/file_stages_storage_cache.go:34:9: S1025: the argument is already a string, there's no need to use fmt.Sprintf (gosimple)
pkg/storage/local_docker_server_stages_storage.go:192:29: S1025: the argument is already a string, there's no need to use fmt.Sprintf (gosimple)
pkg/storage/local_docker_server_stages_storage.go:395:4: S1025: the argument is already a string, there's no need to use fmt.Sprintf (gosimple)

@cristaloleg There was a stream of changes and refactoring this week, please rebase on top of latest master.
Also this break statement https://github.com/werf/werf/pull/3111/files#diff-4daafc4687880f333a0ad70902e5835f079c54b242252ce4050d02956c7e5305L76 was supposed to break an outer loop. We have fixed this in the master https://github.com/werf/werf/blob/master/pkg/deploy/helm/chart_extender/chart_dependencies_loader.go#L75. Thanks for catch.

@cristaloleg There was a stream of changes and refactoring this week, please rebase on top of latest master.
Also this break statement https://github.com/werf/werf/pull/3111/files#diff-4daafc4687880f333a0ad70902e5835f079c54b242252ce4050d02956c7e5305L76 was supposed to break an outer loop. We have fixed this in the master https://github.com/werf/werf/blob/master/pkg/deploy/helm/chart_extender/chart_dependencies_loader.go#L75. Thanks for catch.


added org.clulab.wm.eidos.BuildInfo

BuildInfo object is generated at build time and contains build information relevant to the project. This could be useful for example to add comments to generated files that contain the version or commit used to generate them.
It is also exposed through the webapp at the buildInfo path. The json returned looks like this:
{
  "name": "eidos",
  "version": "0.2.2-SNAPSHOT",
  "scalaVersion": "2.12.4",
  "sbtVersion": "1.1.6",
  "libraryDependencies": [
    "org.scala-lang:scala-library:2.12.4",
    "org.clulab:processors-main:7.3.1",
    "org.clulab:processors-corenlp:7.3.1",
    "org.clulab:processors-odin:7.3.1",
    "org.clulab:processors-modelsmain:7.3.1",
    "org.clulab:processors-modelscorenlp:7.3.1",
    "ai.lum:common:0.0.8",
    "org.scalatest:scalatest:3.0.4:test",
    "commons-io:commons-io:2.5",
    "com.typesafe:config:1.3.1",
    "net.sf.saxon:saxon-dom:8.7",
    "org.slf4j:slf4j-api:1.7.10",
    "com.github.jsonld-java:jsonld-java:0.12.0",
    "com.typesafe.scala-logging:scala-logging:3.7.2"
  ],
  "scalacOptions": [

  ],
  "gitCurrentBranch": "master",
  "gitHeadCommit": "a8cdb34a1a08aefaf4d817eb3d8399b5c822de42",
  "gitHeadCommitDate": "2018-07-30T08:39:00-0700",
  "gitUncommittedChanges": true,
  "builtAtString": "2018-07-30 22:59:26.329",
  "builtAtMillis":<PHONE_NUMBER>329
}

This is really cool.  You need an sbt medal.
Is this accessed only via http://localhost:9000/buildInfo so that it is meant mostly for our internal use or for having a customer use at our request in order to diagnose some problem?
With the addition of some of the recent plug-ins or maybe library dependencies or updates to Processors or something, it seems like the list of potential version conflicts has grown.  Do you get these messages or notice anything troubling among them?
Do you know of a tool better than this one:
addSbtPlugin("net.virtual-void" % "sbt-dependency-graph" % "0.9.1")?
[info] downloading https://repo.scala-sbt.org/scalasbt/sbt-plugin-releases/com.eed3si9n/sbt-buildinfo/scala_2.12/sbt_1.0/0.7.0/jars/sbt-buildinfo.jar ...
[info]  [SUCCESSFUL ] com.eed3si9n#sbt-buildinfo;0.7.0!sbt-buildinfo.jar (1091ms)
[info] Done updating.
[warn] Found version conflict(s) in library dependencies; some are suspected to be binary incompatible:
[warn]  * xml-apis:xml-apis:1.3.04 is selected over 2.0.2
[warn]      +- org.apache.xmlgraphics:batik-script:1.8            (depends on 1.3.04)
[warn]      +- org.apache.xmlgraphics:batik-anim:1.8              (depends on 1.3.04)
[warn]      +- org.apache.xmlgraphics:batik-transcoder:1.8        (depends on 1.3.04)
[warn]      +- org.apache.xmlgraphics:batik-bridge:1.8            (depends on 1.3.04)
[warn]      +- org.apache.xmlgraphics:batik-svg-dom:1.8           (depends on 1.3.04)
[warn]      +- org.apache.xmlgraphics:batik-parser:1.8            (depends on 1.3.04)
[warn]      +- org.apache.xmlgraphics:batik-dom:1.8               (depends on 1.3.04)
[warn]      +- org.apache.xmlgraphics:batik-css:1.8               (depends on 1.3.04)
[warn]      +- org.apache.xmlgraphics:batik-ext:1.8               (depends on 1.3.04)
[warn]      +- org.apache.xmlgraphics:batik-extension:1.8         (depends on 1.3.04)
[warn]      +- org.apache.xmlgraphics:batik-svggen:1.8            (depends on 1.3.04)
[warn]      +- xalan:xalan:2.7.0                                  (depends on 2.0.2)
[warn]  * org.eclipse.sisu:org.eclipse.sisu.plexus:0.3.2 is selected over 0.0.0.M5
[warn]      +- org.apache.maven:maven-plugin-api:3.3.9            (depends on 0.3.2)
[warn]      +- org.apache.maven:maven-core:3.2.2                  (depends on 0.0.0.M5)
[warn]      +- org.apache.maven:maven-plugin-api:3.2.2            (depends on 0.0.0.M5)
[warn]  * org.eclipse.sisu:org.eclipse.sisu.inject:0.3.2 is selected over 0.0.0.M5
[warn]      +- org.eclipse.sisu:org.eclipse.sisu.plexus:0.3.2     (depends on 0.3.2)
[warn]      +- org.eclipse.sisu:org.eclipse.sisu.plexus:0.0.0.M5  (depends on 0.0.0.M5)
[warn]  * org.ow2.asm:asm-commons:6.0 is selected over 5.0.3
[warn]      +- org.pantsbuild:jarjar:1.6.5                        (depends on 6.0)
[warn]      +- com.github.jnr:jnr-ffi:2.0.3                       (depends on 5.0.3)
[warn]  * org.ow2.asm:asm-tree:6.0 is selected over 5.0.3
[warn]      +- org.ow2.asm:asm-commons:6.0                        (depends on 6.0)
[warn]      +- org.parboiled:parboiled-java:1.1.7                 (depends on 5.0.3)
[warn]      +- org.ow2.asm:asm-commons:5.0.3                      (depends on 5.0.3)
[warn]      +- com.github.jnr:jnr-ffi:2.0.3                       (depends on 5.0.3)
[warn]      +- org.ow2.asm:asm-util:5.0.3                         (depends on 5.0.3)
[warn]      +- org.ow2.asm:asm-analysis:5.0.3                     (depends on 5.0.3)
[warn]  * org.ow2.asm:asm:6.0 is selected over 5.0.3
[warn]      +- org.pantsbuild:jarjar:1.6.5                        (depends on 6.0)
[warn]      +- org.ow2.asm:asm-tree:6.0                           (depends on 6.0)
[warn]      +- org.parboiled:parboiled-java:1.1.7                 (depends on 5.0.3)
[warn]      +- com.github.jnr:jnr-ffi:2.0.3                       (depends on 5.0.3)
[warn]      +- org.ow2.asm:asm-tree:5.0.3                         (depends on 5.0.3)
[warn]  * org.sonatype.sisu:sisu-guice is evicted completely
[warn]      +- org.eclipse.sisu:org.eclipse.sisu.plexus:0.0.0.M5  (depends on 3.1.0)
[warn]  * org.codehaus.plexus:plexus-utils:3.0.22 is selected over {3.0.17, 2.1, 1.5.5}
[warn]      +- org.apache.maven:maven-model:3.3.9                 (depends on 3.0.22)
[warn]      +- org.apache.maven:maven-artifact:3.3.9              (depends on 3.0.22)
[warn]      +- org.eclipse.sisu:org.eclipse.sisu.plexus:0.0.0.M5  (depends on 3.0.17)
[warn]      +- org.eclipse.sisu:org.eclipse.sisu.plexus:0.3.2     (depends on 3.0.17)
[warn]      +- org.sonatype.plexus:plexus-sec-dispatcher:1.3      (depends on 3.0.17)
[warn]      +- org.apache.maven:maven-settings:3.2.2              (depends on 3.0.17)
[warn]      +- org.apache.maven:maven-repository-metadata:3.2.2   (depends on 3.0.17)
[warn]      +- org.apache.maven:maven-aether-provider:3.2.2       (depends on 3.0.17)
[warn]      +- org.apache.maven:maven-model:3.2.2                 (depends on 3.0.17)
[warn]      +- org.apache.maven:maven-core:3.2.2                  (depends on 3.0.17)
[warn]      +- org.apache.maven:maven-artifact:3.2.2              (depends on 3.0.17)
[warn]      +- org.apache.maven:maven-settings-builder:3.2.2      (depends on 3.0.17)
[warn]      +- org.apache.maven:maven-model-builder:3.2.2         (depends on 3.0.17)
[warn]  * aopalliance:aopalliance is evicted completely
[warn]      +- org.sonatype.sisu:sisu-guice:3.1.0                 (depends on 1.0)
[warn]  * com.google.guava:guava:23.0 is selected over {10.0.1, 15.0, 18.0}
[warn]      +- io.methvin:directory-watcher:0.1.3                 (depends on 23.0)
[warn]      +- org.eclipse.sisu:org.eclipse.sisu.plexus:0.0.0.M5  (depends on 10.0.1)
[warn]      +- com.fasterxml.jackson.datatype:jackson-datatype-guava:2.6.0 (depends on 10.0.1)
[warn]      +- com.spotify:docker-client:3.5.13                   (depends on 10.0.1)
[warn]  * commons-io:commons-io:2.5 is selected over {1.3.1, 2.4}
[warn]      +- com.typesafe.play:sbt-routes-compiler_2.12:2.6.6   (depends on 2.5)
[warn]      +- org.vafer:jdeb:1.3                                 (depends on 2.4)
[warn]      +- org.apache.xmlgraphics:xmlgraphics-commons:2.1     (depends on 1.3.1)
[warn]      +- org.apache.xmlgraphics:fop:2.1                     (depends on 1.3.1)
[warn] Run 'evicted' to see detailed eviction warnings
[info] Loading settings from build.sbt,version.sbt ...```

i'll see what i can do about those warnings.
the build information can be accessed at runtime by importing org.clulab.wm.eidos.BuildInfo, so anyone using eidos programatically has access to it.
also, i think we should add a comment to the beginning of output files that contains at least the commit hash (i.e. BuildInfo.gitHeadCommit), for reproducibility.


COMMUNITY: 13529: Add missing text reg. check-in based risk calculation (Alignment to Android)

Description
This PR adds missing text reg. the check-in based risk calculation. This text already exits under Android (Link), so it does not need additional approval from RKI to be implemented.
For the translation, please use the same strings as under Android.
Link to Jira

GitHub Issue: https://github.com/corona-warn-app/cwa-documentation/issues/725

JIRA: EXPOSUREAPP-13529

Screenshots

Light Mode
Dark Mode

Closing the PR as it will be covered with:
https://jira-ibs.wbs.net.sap/browse/EXPOSUREAPP-13609


undefined method `[]' for nil:NilClass when changing token lifespan

When posting issues, please include the following information to speed up the troubleshooting process:

Version: 1.1.3

Rails Stacktrace:

NoMethodError: undefined method `[]' for nil:NilClass
  from devise_token_auth/concerns/user.rb:166:in `build_auth_header'
  from devise_token_auth/concerns/user.rb:178:in `update_auth_header'
  from devise_token_auth/concerns/user.rb:160:in `create_new_auth_token'
  from graphql_devise/concerns/controller_methods.rb:67:in `set_auth_headers'
  from graphql_devise/mutations/login.rb:17:in `resolve'
  from graphql/schema/resolver.rb:95:in `public_send'
  from graphql/schema/resolver.rb:95:in `block (3 levels) in resolve_with_support'
  from graphql/schema.rb:1867:in `after_lazy'
  from graphql/schema/resolver.rb:83:in `block (2 levels) in resolve_with_support'
  from graphql/schema.rb:1867:in `after_lazy'
  from graphql/schema/resolver.rb:76:in `block in resolve_with_support'
  from graphql/schema.rb:1867:in `after_lazy'
  from graphql/schema/resolver.rb:65:in `resolve_with_support'
  from graphql/schema/field.rb:689:in `public_send'
  from graphql/schema/field.rb:689:in `block in public_send_field'
  from graphql/schema/field.rb:704:in `with_extensions'
  from graphql/schema/field.rb:679:in `public_send_field'
  from graphql/schema/field.rb:525:in `block (2 levels) in resolve_field'
  from graphql/schema.rb:1867:in `after_lazy'
  from graphql/schema/field.rb:515:in `block in resolve_field'
  from graphql/schema.rb:1867:in `after_lazy'
  from graphql/schema/field.rb:509:in `resolve_field'
  from graphql/schema/member/instrumentation.rb:80:in `call'
  from graphql/schema/member/instrumentation.rb:80:in `call'
  from graphql/field.rb:136:in `resolve'
  from graphql/execution/execute.rb:321:in `call'
  from graphql/schema/middleware_chain.rb:49:in `invoke_core'
  from graphql/schema/middleware_chain.rb:38:in `invoke'
  from graphql/execution/execute.rb:129:in `block in resolve_field'
  from graphql/tracing.rb:66:in `block in trace'
  from graphql/tracing.rb:80:in `call_tracers'
  from graphql/tracing.rb:66:in `trace'
  from graphql/execution/execute.rb:128:in `resolve_field'
  from graphql/execution/execute.rb:92:in `block in resolve_selection'
  from graphql/execution/execute.rb:85:in `each'
  from graphql/execution/execute.rb:85:in `resolve_selection'
  from graphql/execution/execute.rb:56:in `block in resolve_root_selection'
  from graphql/tracing.rb:66:in `block in trace'
  from graphql/tracing.rb:80:in `call_tracers'
  from graphql/tracing.rb:66:in `trace'
  from graphql/execution/execute.rb:49:in `resolve_root_selection'
  from graphql/execution/execute.rb:31:in `begin_query'
  from graphql/execution/multiplex.rb:113:in `begin_query'
  from graphql/execution/multiplex.rb:84:in `block in run_as_multiplex'
  from graphql/execution/multiplex.rb:83:in `map'
  from graphql/execution/multiplex.rb:83:in `run_as_multiplex'
  from graphql/execution/multiplex.rb:62:in `block (2 levels) in run_queries'
  from graphql/execution/multiplex.rb:196:in `block in instrument_and_analyze'
  from graphql/execution/instrumentation.rb:29:in `block (2 levels) in apply_instrumenters'
  from graphql/execution/instrumentation.rb:46:in `block (2 levels) in each_query_call_hooks'
  from graphql/execution/instrumentation.rb:41:in `each_query_call_hooks'
  from graphql/execution/instrumentation.rb:45:in `block in each_query_call_hooks'
  from graphql/execution/instrumentation.rb:72:in `call_hooks'
  from graphql/execution/instrumentation.rb:44:in `each_query_call_hooks'
  from graphql/execution/instrumentation.rb:27:in `block in apply_instrumenters'
  from graphql/execution/instrumentation.rb:72:in `call_hooks'
  from graphql/execution/instrumentation.rb:26:in `apply_instrumenters'
  from graphql/execution/multiplex.rb:175:in `instrument_and_analyze'
  from graphql/execution/multiplex.rb:61:in `block in run_queries'
  from graphql/tracing.rb:66:in `block in trace'
  from graphql/tracing.rb:80:in `call_tracers'
  from graphql/tracing.rb:66:in `trace'
  from graphql/execution/multiplex.rb:59:in `run_queries'
  from graphql/execution/multiplex.rb:49:in `run_all'
  from graphql/schema.rb:1557:in `multiplex'
  from graphql/schema.rb:1528:in `execute'
  from graphql_devise/graphql_controller.rb:13:in `auth'
  from action_controller/metal/basic_implicit_render.rb:6:in `send_action'
  from abstract_controller/base.rb:196:in `process_action'
  from action_controller/metal/rendering.rb:30:in `process_action'
  from abstract_controller/callbacks.rb:42:in `block in process_action'
  from active_support/callbacks.rb:112:in `block in run_callbacks'
  from raven/integrations/rails/controller_transaction.rb:7:in `block in included'
  from active_support/callbacks.rb:121:in `instance_exec'
  from active_support/callbacks.rb:121:in `block in run_callbacks'
  from active_support/callbacks.rb:139:in `run_callbacks'
  from abstract_controller/callbacks.rb:41:in `process_action'
  from action_controller/metal/rescue.rb:22:in `process_action'
  from action_controller/metal/instrumentation.rb:33:in `block in process_action'
  from active_support/notifications.rb:180:in `block in instrument'
  from active_support/notifications/instrumenter.rb:24:in `instrument'
  from active_support/notifications.rb:180:in `instrument'
  from action_controller/metal/instrumentation.rb:32:in `process_action'
  from action_controller/metal/params_wrapper.rb:245:in `process_action'
  from active_record/railties/controller_runtime.rb:27:in `process_action'
  from abstract_controller/base.rb:136:in `process'
  from action_view/rendering.rb:39:in `process'
  from action_controller/metal.rb:191:in `dispatch'
  from action_controller/metal.rb:252:in `dispatch'
  from action_dispatch/routing/route_set.rb:51:in `dispatch'
  from action_dispatch/routing/route_set.rb:33:in `serve'
  from action_dispatch/routing/mapper.rb:18:in `block in <class:Constraints>'
  from action_dispatch/routing/mapper.rb:48:in `serve'
  from action_dispatch/journey/router.rb:49:in `block in serve'
  from action_dispatch/journey/router.rb:32:in `each'
  from action_dispatch/journey/router.rb:32:in `serve'
  from action_dispatch/routing/route_set.rb:837:in `call'
  from warden/manager.rb:36:in `block in call'
  from warden/manager.rb:34:in `catch'
  from warden/manager.rb:34:in `call'
  from rack/tempfile_reaper.rb:15:in `call'
  from rack/etag.rb:25:in `call'
  from rack/conditional_get.rb:38:in `call'
  from rack/head.rb:12:in `call'
  from action_dispatch/http/content_security_policy.rb:18:in `call'
  from rack/session/abstract/id.rb:259:in `context'
  from rack/session/abstract/id.rb:253:in `call'
  from action_dispatch/middleware/cookies.rb:648:in `call'
  from action_dispatch/middleware/callbacks.rb:27:in `block in call'
  from active_support/callbacks.rb:101:in `run_callbacks'
  from action_dispatch/middleware/callbacks.rb:26:in `call'
  from action_dispatch/middleware/actionable_exceptions.rb:17:in `call'
  from action_dispatch/middleware/debug_exceptions.rb:32:in `call'
  from action_dispatch/middleware/show_exceptions.rb:33:in `call'
  from rails/rack/logger.rb:38:in `call_app'
  from rails/rack/logger.rb:26:in `block in call'
  from active_support/tagged_logging.rb:80:in `block in tagged'
  from active_support/tagged_logging.rb:28:in `tagged'
  from active_support/tagged_logging.rb:80:in `tagged'
  from rails/rack/logger.rb:26:in `call'
  from action_dispatch/middleware/remote_ip.rb:81:in `call'
  from action_dispatch/middleware/request_id.rb:27:in `call'
  from rack/method_override.rb:22:in `call'
  from rack/runtime.rb:22:in `call'
  from active_support/cache/strategy/local_cache_middleware.rb:29:in `call'
  from action_dispatch/middleware/executor.rb:14:in `call'
  from rack/sendfile.rb:111:in `call'
  from action_dispatch/middleware/host_authorization.rb:77:in `call'
  from rack/cors.rb:100:in `call'
  from raven/integrations/rack.rb:51:in `call'
  from rails/engine.rb:526:in `call'
  from puma/configuration.rb:228:in `call'
  from puma/server.rb:681:in `handle_request'
  from puma/server.rb:472:in `process_client'
  from puma/server.rb:328:in `block in run'
  from puma/thread_pool.rb:134:in `block in spawn_thread'

When i changed token lifespan from 2.weeks(default) to 8.hours I started to get this error.
I fixed it by removing old token, after this everything is working. I don't think that this behavior is correct

It just happened the same error in my project

If I make a pr on this will u accept it?

I was just about to create an issue about this - Any value under 11 days (I've attempted 263 hours which is one hour less than 11 days) results in the exact same issue.
Here is an issue where it is also referenced (but as part of a different issue).
I've discovered that the issue seems to have to do with already existing tokens.
I've not been able to consistently re-create the issue but I have been able to (seemingly) get rid of the issue by removing all tokens for the user:
user.tokens = {}
user.save!

This being the line where the issue is raised I believe this issue is to do with the fact that the entry for some tokens[client_id] has already been removed and we're calling build_auth_header with an already deleted/removed client_id.
@lynndylanhurley, have you any thoughts on this?

Hi, I had the same issue about nil class but I had to call a different method, I did it with create_token

user.tokens = {}

Hi Tomas, can i know on which files did you alter the user.tokens = {} ?

I didn't do it in a specific file, rather in the console while debugging to verify that it fixed the issue.


broken link on https://webring.xxiivv.com/#random

{Provoke Analog} link broken

Removed thanks : )


Rebuild older packages

Some older builds fail, but it's uncertain which. In #508, ImageMagick failed and a rebuild fixed the issue.
From https://github.com/teaxyz/cli/issues/508#issuecomment-1500235369:

can we either rebuild or delete everything from before a certain date?

this was done


[HTTP] Update the transport API

At the moment we have following too,
HttpContent getHttpContent()
MessageFuture getHttpContentAsync()
But we ideally want is,
MessageFuture getHttpContentAsync()
MessageFuture getHttpContentAsync().sync()
Need to improve the code to support this.

This should just work with the new start/await semantics?


Feels like JSON mutation is broken.

Tested in master and Dgraph's master.
{
  "set": [
    {
      "name": "Alice"
    },
    {
      "name": "Bob"
    }
  ]
}

Does the same mutation work with curl? I recall there were syntax changes in 1.1

The same mutation works with curl.
$ curl -H Content-Type:application/json localhost:8180/mutate?commitNow=true -d '{
  "set": [
    {
      "name": "Alice"
    },
    {
      "name": "Bob"
    }
  ]
}'
{"data":{"code":"Success","message":"Done","uids":{"blank-0":"0x9ee70","blank-1":"0x9ee71"}},"extensions":{"server_latency":{"parsing_ns":31926,"processing_ns":19050004},"txn":{"start_ts":3089,"commit_ts":3090,"preds":["1-name"]}}}

Ratel is setting the header Content-Type: application/rdf even for JSON mutations. It should be Content-Type: application/json.
Here's the result when running with application/rdf which matches the error shown in @MichelDiz's screenshot.
$ curl -H Content-Type:application/rdf localhost:8180/mutate?commitNow=true -d '{
  "set": [
    {
      "name": "Alice"
    },
    {
      "name": "Bob"
    }
  ]
}'
{"errors":[{"code":"ErrorInvalidRequest","message":"while lexing {\n  \"set\": [\n    {\n      \"name\": \"Alice\"\n    },\n    {\n      \"name\": \"Bob\"\n    }\n  ]\n} at line 2 column 2: Unrecognized character inside mutation: U+0022 '\"'"}]}```

Fixed in 1678040


[demo] base32 encoder for efficient cidv1 storage

https://moleculeto.notion.site/Store-FAM-agreements-on-IPFS-their-CID-on-chain-ef86b41f7d3c45f98d6ec18b88727cc1

stores agreement "hashes" efficiently as bytes32, loses knowledge about its base / hash  though.
reconstructs ipfs CIDv1 hashes by base32 encoding & prefixing
assuming 01551220 header (afkrei) prefix
adds "16" (f) header manually
clients create them e.g. by ipfs add --cid-version 1
this is also used as default by web3.storage
clients must make sure that their users use this. Everything else is not guaranteed to work. If this is accidentally done wrong, clients still can recover the content by trying / assuming another prefix (eg bafybei / 01701220)

we should make this Base32 library open source! Over and out