Unable to launch the docker container

Following the directions in the wiki. Full disclaimer, I'm new to docker and git so probably something I'm doing wrong.  Any guidance or help would be appreciated.
Using Raspberry Pi 3 Model B Rev 1.2
pi@raspberrypi:/petnet-feeder-service $ sudo docker-compose logs petnet-feeder-service
ERROR: No such service: petnet-feeder-service
pi@raspberrypi:/petnet-feeder-service $
I edited the docker-compose-yml and added "petnet-" to the service
services:
petnet-feeder-service:
not sure if this is the correct thing to do but get past that error.
pi@raspberrypi:/petnet-feeder-service $ sudo docker-compose start -d petnet-feeder-service
Start existing containers.
Usage: start [SERVICE...]
pi@raspberrypi:/petnet-feeder-service $
looking at the docker compose logs I get this
pi@raspberrypi:/petnet-feeder-service $ sudo docker-compose logs petnet-feeder-service
Attaching to
pi@raspberrypi:/petnet-feeder-service $
pi@raspberrypi:/petnet-feeder-service $ sudo docker-compose --verbose logs petnet-feeder-service
compose.config.config.find: Using configuration files: ./docker-compose.yaml
docker.utils.config.find_config_file: Trying paths: ['/root/.docker/config.json', '/root/.dockercfg']
docker.utils.config.find_config_file: No config file found
docker.utils.config.find_config_file: Trying paths: ['/root/.docker/config.json', '/root/.dockercfg']
docker.utils.config.find_config_file: No config file found
docker.utils.config.find_config_file: Trying paths: ['/root/.docker/config.json', '/root/.dockercfg']
docker.utils.config.find_config_file: No config file found
urllib3.connectionpool._make_request: http://localhost:None "GET /version HTTP/1.1" 200 835
urllib3.connectionpool._make_request: http://localhost:None "GET /v1.41/version HTTP/1.1" 200 835
compose.cli.docker_client.get_client: docker-compose version 1.27.4, build unknown
docker-py version: 4.4.1
CPython version: 3.7.3
OpenSSL version: OpenSSL 1.1.1d  10 Sep 2019
compose.cli.docker_client.get_client: Docker base_url: http+docker://localhost
compose.cli.docker_client.get_client: Docker version: Platform={'Name': 'Docker Engine - Community'}, Components=[{'Name': 'Engine', 'Version': '20.10.1', 'Details': {'ApiVersion': '1.41', 'Arch': 'arm', 'BuildTime': '2020-12-15T04:33:02.000000000+00:00', 'Experimental': 'false', 'GitCommit': 'f001486', 'GoVersion': 'go1.13.15', 'KernelVersion': '5.4.72-v7+', 'MinAPIVersion': '1.12', 'Os': 'linux'}}, {'Name': 'containerd', 'Version': '1.4.3', 'Details': {'GitCommit': '269548fa27e0089a8b8278fc4fc781d7f65a939b'}}, {'Name': 'runc', 'Version': '1.0.0-rc92', 'Details': {'GitCommit': 'ff819c7e9184c13b7c2607fe6c30ae19403a7aff'}}, {'Name': 'docker-init', 'Version': '0.19.0', 'Details': {'GitCommit': 'de40ad0'}}], Version=20.10.1, ApiVersion=1.41, MinAPIVersion=1.12, GitCommit=f001486, GoVersion=go1.13.15, Os=linux, Arch=arm, KernelVersion=5.4.72-v7+, BuildTime=2020-12-15T04:33:02.000000000+00:00
compose.cli.verbose_proxy.proxy_callable: docker inspect_network <- ('petnetfeederservice_default')
urllib3.connectionpool._make_request: http://localhost:None "GET /v1.41/networks/petnetfeederservice_default HTTP/1.1" 404 60
compose.cli.verbose_proxy.proxy_callable: docker containers <- (all=True, filters={'label': ['com.docker.compose.project=petnet-feeder-service', 'com.docker.compose.oneoff=False']})
urllib3.connectionpool._make_request: http://localhost:None "GET /v1.41/containers/json?limit=-1&all=1&size=0&trunc_cmd=0&filters=%7B%22label%22%3A+%5B%22com.docker.compose.project%3Dpetnet-feeder-service%22%2C+%22com.docker.compose.oneoff%3DFalse%22%5D%7D HTTP/1.1" 200 3
compose.cli.verbose_proxy.proxy_callable: docker containers -> (list with 0 items)
compose.cli.verbose_proxy.proxy_callable: docker containers <- (all=True, filters={'label': ['com.docker.compose.project=petnetfeederservice', 'com.docker.compose.oneoff=False']})
urllib3.connectionpool._make_request: http://localhost:None "GET /v1.41/containers/json?limit=-1&all=1&size=0&trunc_cmd=0&filters=%7B%22label%22%3A+%5B%22com.docker.compose.project%3Dpetnetfeederservice%22%2C+%22com.docker.compose.oneoff%3DFalse%22%5D%7D HTTP/1.1" 200 3
compose.cli.verbose_proxy.proxy_callable: docker containers -> (list with 0 items)
Attaching to
pi@raspberrypi:/petnet-feeder-service $
Also get this when trying to pull directly
pi@raspberrypi:/petnet-feeder-service $ sudo docker pull tedder42/petnet-feeder-service
Using default tag: latest
latest: Pulling from tedder42/petnet-feeder-service
no matching manifest for linux/arm/v7 in the manifest list entries
pi@raspberrypi:~/petnet-feeder-service $
from some other logs
urllib3.connectionpool._make_request: http://localhost:None "POST /v1.41/images/create?tag=latest&fromImage=tedder42%2Fpetnet-feeder-service HTTP/1.1" 200 None
compose.cli.verbose_proxy.proxy_callable: docker pull -> <generator object APIClient._stream_helper at 0x7477a530>
latest: Pulling from tedder42/petnet-feeder-service
ERROR: compose.cli.main.main: no matching manifest for linux/arm/v7 in the manifest list entries
pi@raspberrypi:/petnet-feeder-service $

@xoengine please use github markdown to format the logs and console text- it's really hard to read them. If you don't know how to do that, let me know.

@xoengine please use github markdown to format the logs and console text- it's really hard to read them. If you don't know how to do that, let me know.

Echoing @tedder, it’s difficult to read, but I do have some suggestions and follow-up questions.
Are you using the compose file from the Wiki instructions or the README. I know it is confusing, but the Wiki is more up to date than the README. I just haven’t had the time to clean it up yet. You are running an ARMv7 device by the looks of your logs, so you will need to be using the latest-arm7 or latest-pib2 tag. There are pretty okay instructions in the Docker Compose file linked in the README. If following the instructions there don’t work, let us know!

Echoing @tedder, it’s difficult to read, but I do have some suggestions and follow-up questions.
Are you using the compose file from the Wiki instructions or the README. I know it is confusing, but the Wiki is more up to date than the README. I just haven’t had the time to clean it up yet. You are running an ARMv7 device by the looks of your logs, so you will need to be using the latest-arm7 or latest-pib2 tag. There are pretty okay instructions in the Docker Compose file linked in the README. If following the instructions there don’t work, let us know!

Hi
Sorry for the formatting, rookie mistake :-). I tried to fix it, hopefully that is better.  I was using the wiki "getting started" guide.  https://github.com/petnet-independence-project/petnet-feeder-service/wiki/Getting-Started
The compose file I used was in the "sample" directory from the code I pulled from the git repository.
My son said he got the webserver running by using the PI 2 rather than PI 3 image in the docket-compose file.  Not sure if that makes sense but it does look like it is running.
And now for the bummer part.  I thought I had a V2 as I don't have it that long but I guess after searching around it looks like I have a V1.  A packet capture does not show it doing any DNS lookups at all.  It is connecting out to ip address <IP_ADDRESS> on port 31314.
Is there any hope for V1 users or is it a lost cause?

Hi
Sorry for the formatting, rookie mistake :-). I tried to fix it, hopefully that is better.  I was using the wiki "getting started" guide.  https://github.com/petnet-independence-project/petnet-feeder-service/wiki/Getting-Started
The compose file I used was in the "sample" directory from the code I pulled from the git repository.
My son said he got the webserver running by using the PI 2 rather than PI 3 image in the docket-compose file.  Not sure if that makes sense but it does look like it is running.
And now for the bummer part.  I thought I had a V2 as I don't have it that long but I guess after searching around it looks like I have a V1.  A packet capture does not show it doing any DNS lookups at all.  It is connecting out to ip address <IP_ADDRESS> on port 31314.
Is there any hope for V1 users or is it a lost cause?

Yup, what your son did is what I was suggesting. Unfortunately, we haven’t spent much time on the V1 feeders. Someone told me they verify the validity of the Electric Imp SSL certificates; haven’t verified myself because I have been trying to finish the stuff we have working on the V2s and don’t have access to a V1 personally.
I can confirm though that 31314 is the port that the Electric Imp boards in the V1s use.

Yup, what your son did is what I was suggesting. Unfortunately, we haven’t spent much time on the V1 feeders. Someone told me they verify the validity of the Electric Imp SSL certificates; haven’t verified myself because I have been trying to finish the stuff we have working on the V2s and don’t have access to a V1 personally.
I can confirm though that 31314 is the port that the Electric Imp boards in the V1s use.

I know the whole point of this project is to revive feeders you already own, but you can buy V2 feeders for $30-35 NIB, shipped on eBay.
https://www.ebay.com/itm/PETNET-SMARTFEEDER-2ND-GEN-WHITE-AUTOMATIC-PET-FEEDER-READ-DESCRIPTION-/114412788415

I know the whole point of this project is to revive feeders you already own, but you can buy V2 feeders for $30-35 NIB, shipped on eBay.
https://www.ebay.com/itm/PETNET-SMARTFEEDER-2ND-GEN-WHITE-AUTOMATIC-PET-FEEDER-READ-DESCRIPTION-/114412788415

FWIW I came across this same thing using 32-bit Raspbian on a Pi4, setting it to tedder42/petnet-feeder-service:
Pulling petnet-feeder-service (tedder42/petnet-feeder-service:latest)...
latest: Pulling from tedder42/petnet-feeder-service
ERROR: no matching manifest for unknown in the manifest list entries

It's more easily reproduced with vanilla docker:
$ docker pull tedder42/petnet-feeder-service:latest
latest: Pulling from tedder42/petnet-feeder-service
no matching manifest for unknown in the manifest list entries

I'm going to add v7l to the builds to :latest and see if that breaks things. I remember a conversation about this.

FWIW I came across this same thing using 32-bit Raspbian on a Pi4, setting it to tedder42/petnet-feeder-service:
Pulling petnet-feeder-service (tedder42/petnet-feeder-service:latest)...
latest: Pulling from tedder42/petnet-feeder-service
ERROR: no matching manifest for unknown in the manifest list entries

It's more easily reproduced with vanilla docker:
$ docker pull tedder42/petnet-feeder-service:latest
latest: Pulling from tedder42/petnet-feeder-service
no matching manifest for unknown in the manifest list entries

I'm going to add v7l to the builds to :latest and see if that breaks things. I remember a conversation about this.

chatting about this in Slack, I think unknown is the indicator that Docker is too dumb to know what architecture it should be on. Currently only amd64 and arm64 are in latest. I'm going to add v7l to it. If that works, that only leaves the Zero as the outlier (needing a different image). I'll test amd64, arm64, and arm32/v7l.
Marc on 2020-11-08:

Backstory if you missed the thread: The docker cli doesn't have the logic to determine what version of ARM CPU the device is running and so it just pulls the ARM64 image by default. This makes ARMv6/7 devices like the Pi Zero, Zero W, etc. very unhappy and the container just segfaults. The Stackoverflow answer that lead me to this just says to pin to the right container hash... but that is inelegant and tedious if we have to keep updating our example docker-compose file.

related: https://raspberrypi.stackexchange.com/a/105045

chatting about this in Slack, I think unknown is the indicator that Docker is too dumb to know what architecture it should be on. Currently only amd64 and arm64 are in latest. I'm going to add v7l to it. If that works, that only leaves the Zero as the outlier (needing a different image). I'll test amd64, arm64, and arm32/v7l.
Marc on 2020-11-08:

Backstory if you missed the thread: The docker cli doesn't have the logic to determine what version of ARM CPU the device is running and so it just pulls the ARM64 image by default. This makes ARMv6/7 devices like the Pi Zero, Zero W, etc. very unhappy and the container just segfaults. The Stackoverflow answer that lead me to this just says to pin to the right container hash... but that is inelegant and tedious if we have to keep updating our example docker-compose file.

related: https://raspberrypi.stackexchange.com/a/105045

@tedder Are you happy enough with where this ticket is to close it? I think we got a win from adding an additional arch to the latest tag, but ARMv <= 6 will likely always have to be its own tag.

yep! I'm happy.


Fresh install results in a system that cannot be logged in to due to DB error

On Tor:

On LAN:

Reported by: @kn0wmad

What commit is this from?

Cannot repro on today's build, closing for now


Run windows tests on 2019 and 2022

For https://github.com/actions/virtual-environments/issues/4856: Pin the docker and choco build jobs to windows-2019 since that is what we use for release builds from gitlab
Update the msi, choco, and windows test jobs to run for both windows-2019 and windows-2022
Update choco test job to run with and without fluentd
Move powershell test steps to scripts

LGTM.
The changes are independent, right?
I think going forward we should try to submit separate PRs in these cases. It would make PR review process much easier and reduce chance of overlooking some issues.

Thanks, makes sense. Will try to split it up next time, but just wanted to confirm that the installation and services are not affected on windows 2022.


Prepare FLP integration

A few renamed fields (in particular, adding K8S prefix)
Now Service, Node and Pod share the same field ("Name"), they're still
distinguished with the resource kind icon

Needs operator PR: https://github.com/netobserv/network-observability-operator/pull/60

It's ready for review, along with https://github.com/netobserv/network-observability-operator/pull/60
I keep it on hold in order to do a release before merging, as discussed with @memodi
/hold
Some screenshots of what changed:

And:

As you can see, there's no more "Pod" column, replaced with "Name", that can stand for a Pod name, a Service Name or a Node name, or, as a fallback if we weren't able to match the IP, it would display that IP. In the end, it's much like what we discussed previously as "source / dest super-column", except that it comes naturally from the model provided by FLP.
The only thing that I introduced in addition to just adapting the model, is to show the IP when there was no match with K8S objects. I think it can be interesting to more easily identify some missing bits, but it's open for discussion.

The only thing that I introduced in addition to just adapting the model, is to show the IP when there was no match with K8S objects. I think it can be interesting to more easily identify some missing bits, but it's open for discussion.

Since we don't have the namespace when we have the ip address should we also merge it ?

/unhold

/lgtm
/approve


maybe-uninitialized error

When a user builds SOCI with -Werror=maybe-uninitialized enabled and the compiler chooses to inline the below soci code a hard compiler errors results. This occurs even with the soci includes marked as SYSTEM in CMake as inlining negates this protection.
I believe changing base_type baseValue; to base_type baseValue{}; at include/soci/values.h:176 would fix the issue
In file included from _deps/soci-src/src/core/../../include/soci/column-info.h:13,
                 from _deps/soci-src/src/core/../../include/soci/soci.h:16,
In constructor ‘soci::details::copy_holder<T>::copy_holder(const T&) [with T = int]’,
    inlined from ‘void soci::values::set(const std::string&, const T&, soci::indicator) [with T = boost::optional<int>]’ at _deps/soci-src/src/core/../../include/soci/values.h:180:21:
_deps/soci-src/src/core/../../include/soci/values.h:37:32: error: ‘baseValue’ may be used uninitialized [-Werror=maybe-uninitialized]
   37 |     copy_holder(T const & v) : value_(v) {}
      |                                ^~~~~~~~~
_deps/soci-src/src/core/../../include/soci/values.h: In member function ‘void soci::values::set(const std::string&, const T&, soci::indicator) [with T = boost::optional<int>]’:
_deps/soci-src/src/core/../../include/soci/values.h:176:23: note: ‘baseValue’ was declared here
  176 |             base_type baseValue;

I didn't have time to test it, but would this:
diff --git a/include/soci/values.h b/include/soci/values.h
index 5f9db2ff..8d782ad2 100644
--- a/include/soci/values.h
+++ b/include/soci/values.h
@@ -173,7 +173,7 @@ public:
             indicator * pind = new indicator(indic);
             indicators_.push_back(pind);

-            base_type baseValue;
+            base_type baseValue{};
             type_conversion<T>::to_base(value, baseValue, *pind);

             details::copy_holder<base_type> * pcopy =

be enough to fix this?

Looks good


Performace measurement

Use the React profiler component to produce highly useable information regarding render times for the main subtree.
Would be nice to wrap this up into its own file but at the moment it is dependent on the simulation time setting. I think this should perhaps be moved into settings.ts anyway as in the future other developers or sites might want to tweak this setting without having to edit and rebuild the code.
It would also be interesting to see how we can make this output more useful and generate it by running a test, either on our own machines or as part of the CI job.

More info about this branch's use has been collected here: #149

@willrogers have made some changes which make this more merge-ready. Also noticed a file src/s.ts was added during your restructure PR a while back, is that meant to be there? Appears to do the same thing as src/settings.ts ?

Looks nice, thanks.

I don't know why but I am getting a test failure on my machine that we don't see on Travis.

npm install fixed it. It's a bit odd but never mind.


update mshadow

Description
Update mshadow for:

batch_dot fp16 acceleration
omp acceleration when nvcc is not present

Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[x] Changes are complete (i.e. I finished coding on this PR)
[x] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[ ] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[x] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

Is this the same as https://github.com/apache/incubator-mxnet/pull/12655?

@mxnet-label-bot [pr-awaiting-testing]

@apeforest your mshadow commit breaks MXNet build, which prevents subsequent commits from merge. Can you fix it?
cc @szha @azai91

Temporarily reverted the faulty commit here:
https://github.com/dmlc/mshadow/pull/357


Track Cadre Payments - Futures

Upload Historical Payments from Zac
Allow Cadre to see their payment history
Add IsDeleted column to Event.EventCadre. Modify all deletes of EventCadre to soft deletes of that plus Payment tables. This will allow us to soft-delete Invoices when a Cadre withdraws their request (Event.EventUpdateCadreNotRequested). Right now we hard-delete the EventCadre record, which means we must hard-delete the Invoice records, because otherwise we would violate the Foreign Key

Include GSA rates in spreadsheet, rather than relying on Zac to tie them together

Cadre.PerDiemInsert
probably need to allow user to enter rate as well as Days, or prevent user from entering Days.

DONE: Upload Historical Payments from Zac


Testing, please ignore. (jhwmmv)

This is a bug bounty test. Please ignore.. Please DO NOT APPROVE THIS! (jhwmmv)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.jhwmmv tpkxx seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


AllReady.Areas.Admin.Controllers.ActivityController checks for "OrgAdmin" multiple times?

I'm currently doing some refactoring work for this controller. The controller is decorated with:
[Authorize("OrgAdmin")]
which leads me to believe that only users that have the ClaimType.UserType set to "OrgAdmin" will be able to access any action method in this controller.
Yet, in every action method, this call is being made:
if (!User.IsOrganizationAdmin(...))
{
    return HttpUnauthorized();
}

Looking into the IsOrganizationAdmin extension method, it appears to determine if a user is an "organization admin", there is more to it then just the claim check I mentioned above. Here is the code:
public static bool IsOrganizationAdmin(this ClaimsPrincipal user, int organizationId)
{
    var userOrganizationId = user.GetOrganizationId();
    return user.IsUserType(UserType.SiteAdmin) || (user.IsUserType(UserType.OrgAdmin) && userOrganizationId.HasValue && userOrganizationId.Value == organizationId);
}

determining is a user is an org admin also means the user is a SiteAdmin OR is an OrgAdmin where userOrganizationId.HasValue (is it possible for a user to be created without an OrganizationId?) and the user's organizationId is equal to the organizationId passed into the extension method.
So, my question is, do I keep the calls to the extension method in each action method and delete the controller-level attribute or vice-versa?
Seeing how checking to see if a user is an "OrgAdmin" entails other checks besides just the ClaimType.UserType beign set to "OrgAdmin", I'd say I can safely remove the controller level attribute?
@BillWagner @MisterJames @tonysurma any ideas on the right way to go here?

from my perspective you are right with some nuance.
OrgAdmin check is more than if they have that role as we need to verify they are an org admin for the org of the activity.  Therefore you definitely can't remove the code check as it is nuanced but perhaps having the controller level check helps to stop any 'non-org admin' from even getting to that point, thoughts @MisterJames ?
As for the HasValue there are two thoughts here: a) if we have the controller check we don't need that as every orgadmin has to be part of an organization and b) if we remove that check then we need it as a site admin or random 'end-user' won't be associated with an organization.

@tonysurma, you are correct. I just read through this Issue and I don't know what I was thinking this day. The way things work now if fine. If you could please close this Issue so I know longer have to be embarrassed for opening it. :blush:


File explorer improvements

Some UI changes if possible:

highlight recent changes files/folders with different color
tabs inside file explorer, if not possible a work around is to show list of open file explorer windows with a shortcut

Create shortcuts to do simple things like below

copy file name to clipboard in batches
copy full path to files in batches
create a copy of file with dialogue to ask for the new name (see screen shot below)

@amirhosseindavoody sorry but please do one ask per item.  else it is too hard for tracking.

Check out https://thewincentral.com/microsoft-planning-to-bring-windows-10-sets-feature-back-from-grave/, maybe that'll help?


logo added

Project official website: https://mermaidswap.com

please provide a smaller logo url that fits the display for different products like iotexscan iopay etc.

https://github.com/iotexproject/iotex-token-metadata#guidelines-for-tokens

please provide a smaller logo url that fits the display for different products like iotexscan iopay etc.

Done we have provided

or can use this also : https://ibb.co/k4sR15M


[Feature Request] Guides on setting up development environment.

Describe the solution you'd like
A clear and concise description of what you want to happen.
Provide a clear guidance on dev env setup, or simply tell how you guys development for both frontend and backend.
Why the solution needed
A clear and concise description of the reason why you want the solution.
The current doc with docker is not working.
Additional context
Add any other context or screenshots about the feature request here.

@hustshawn Thank you for your request.
Which document is 'the current doc with docker' referred to in your request as 'not working' ?


Update credential single select to PageFormSingleSelectAwxResource

https://issues.redhat.com/browse/AAP-24530
https://issues.redhat.com/browse/AAP-25028

As a team we decided to merge this one, since the test failures are not related.


volto-subblocks is not included as dependency

volto-subblocks is a peer dependency as of 3.0.0, and needs to be installed together with this add-on as mentioned in the Readme. The rationale behind this is in #45.
I understand that this probably needs to be documented better in the changelog, or at least in the github release. I will try to take some time to have a better look at conventional commits and automatic changelog stuff which has been introduced here.


Unable to save bookmark when query returns no results.

Console shows the following error: GET https://localhost:3000/metadata/query/ 500 (Internal Server Error)
Even if no results can be found, the user should be able to store the bookmark, zoom to the area and re-run the query to try again. Our current implementation provides lots of data but real world data sources will not always return data in certain areas, especially if the query params are very specific.
To replicate the problem:
perform a query 1/4th of the size of the mouse pointer.
Once you get no results back, try saving the bookmark using the timeline.
No message is displayed and the error mentioned above can be seen in the browser dev tools console.

Passed on dev


Lucene query with where clause over associated objects does not work

Currently where clause  over relation objects in a query does not gives expected results. Enable querying over relation columns using Lucene.

Fixed. Released with Kundera-2.15.
Chhavi


updated the changes in hello

What does this PR do?
What issues does this PR fix or reference?
#
The PR fulfills these requirements:
[ ] Tests for the proposed changes have been added/updated.
[ ] Code linting and formatting was performed.
Functionality Before
<insert gif and/or summary>
Functionality After
<insert gif and/or summary>

my first pr


Sometime i get double response messages

I really really want to say thank you to you. I love your lib. It saves me in my project.
But Sometimes I get double response messages. Could you take a look at my useBluetooth.js file and tell me where is my problem. I think I missed some clear subscription there.
below are 2 files, or you can take a look via expo: https://snack.expo.dev/@hungdev/react-native-bluetooth-classic
Main File
import React, { useState, useRef, useEffect, useCallback } from 'react';
import { View, Text, ScrollView, TouchableOpacity, Touchable } from 'react-native';
import styles from './styles/Home.Styles';
import useBluetooth from 'app/hooks/useBluetooth';
import RNBluetoothClassic from 'react-native-bluetooth-classic';

export default function Home() {

  const onReceivedDataScan = useCallback((data) => {
    console.tron.log('data?.data', data?.data); // ========> Get response here
    alert(data?.data);
  }, []);

  const { connection, setDevice, data, } = useBluetooth(onReceivedDataScan);

  useEffect(() => {
    getBondedDevices();
  }, []);

  const getBondedDevices = async () => {
    console.tron.log('-- GETTING BONDED DEVICES --');
    try {
      const listBondedDevices = await RNBluetoothClassic.getBondedDevices();
      const dv = listBondedDevices?.find(e => e.id === "F4:5E:AB:DB:1F:B9");
      setDevice(dv);
    } catch (err) {
      console.tron.log(err);
    }
  };

  return (
    <View style={styles.container}>

    </View>
  );
}

useBluethooth.js
import React, { useEffect, useState } from 'react';
import { View, Text } from 'react-native';
import RNBluetoothClassic from 'react-native-bluetooth-classic';

export default function BluetoothClassic(onReceivedDataScan) {
  const [device, setDevice] = useState();
  const [data, setData] = useState([]);
  const [connection, setConnection] = useState(false);

  useEffect(() => {
    device && setTimeout(() => connect(), 0);
  }, [device]);

  const addData = (message) => setData(prev => [message, ...prev]);

  const connect = async () => {
    try {
      let connection = await device.isConnected();
      if (!connection) {
        addData({
          data: `Attempting connection to ${device.address}`,
          timestamp: new Date(),
          type: 'error',
        });

        connection = await device.connect();

        addData({
          data: 'Connection successful',
          timestamp: new Date(),
          type: 'info',
        });
      } else {
        addData({
          data: `Connected to ${device.address}`,
          timestamp: new Date(),
          type: 'error',
        });
      }

      setConnection(connection);
      initializeRead();
    } catch (error) {
      addData({
        data: `Connection failed: ${error.message}`,
        timestamp: new Date(),
        type: 'error',
      });
    }
  };

  const disconnect = async (disconnected) => {
    console.tron.log('disconnected', disconnected);
    connect();
    try {
      if (!disconnected) {
        disconnected = await device.disconnect();
      }

      addData({
        data: 'Disconnected',
        timestamp: new Date(),
        type: 'info',
      });

      setConnection(!disconnected);
    } catch (error) {
      addData({
        data: `Disconnect failed: ${error.message}`,
        timestamp: new Date(),
        type: 'error',
      });
    }

    // Clear the reads, so that they don't get duplicated
    uninitializeRead();
  };

  const initializeRead = () => {
    disconnectSubscription = RNBluetoothClassic.onDeviceDisconnected(() => disconnect(true));

    readSubscription = device.onDataReceived(data => onReceivedData(data));
  };

  /**
 * Clear the reading functionality.
 */
  const uninitializeRead = () => {
    if (readInterval) {
      clearInterval(readInterval);
    }
    if (readSubscription) {
      readSubscription.remove();
    }
  };

  const onReceivedData = (event) => {
    event.timestamp = new Date();
    const dataReceived = {
      ...event,
      timestamp: new Date(),
      type: 'receive',
    };
    addData(dataReceived);
    onReceivedDataScan?.(dataReceived);
  };

  return { connect, disconnect, connection, setDevice, data, uninitializeRead };
}

Thank you!

There is an issue with the HOT reloading of React Native where there are no (that I'm aware of) events that can handle disconnecting and re-connecting when it happens.   So when you're doing active development you need to ensure you manually:

disconnect/remove
reconnect

This is a known issue, and something that I haven't looked into in a while.  Generally when an app closes the context is lost, the device is disconnected and subsequently the subscription removed.
When hot reloading occurs, this does not happen, the native side does not get reset and therefore doesn't lose is listeners, while the react side does get reloaded and loses it's reference to the subscription.
I don't know if React Native added events for managing hot reloading like this.

If you go through some of the closed issues, you can see some of their comments.
Your code looks ok, nothing really jumps out with regards to removing the subscription.  So this is really the only thing that I can think of - the hot reload.

https://reactnative.dev/blog/2016/03/24/introducing-hot-reloading#hmr-api
Give this a shot, you may be able to listen for HOT reload and disconnect/remove when required.
module.hot.accept(() => {
  console.log('time changed');
});

In your case, you probably want to do this within useBluetooth in order to clear the state and make sure it's back to the beginning.

Thank you for your support <3. I will close this issue to avoid distracting issues and discussions.


V3

Limit to<EMAIL_ADDRESS>Copy all modules in modules folder
Test All 3 bundles
Add Highmaps
Add Highmaps demo
Generate contents for demos
Clean up build scripts
internal paths clean up

#41 #44 @aldendaniels @Kureev

Is the plan to also promote the demos to React 0.14?

Yes

:+1:


Timescale data tiering

Describe the feature you'd like to request
https://docs.timescale.com/use-timescale/latest/data-tiering/
Describe the solution you'd like
At some point, we maybe want to archive raw Event data to S3.
Timescale has built-in support for tiering data into Parquet files
Describe alternatives you've considered
Could use a migration service to replicate data to a data warehouse too

Deprecating, we are moving off Timescale likely


Bumped nativescript-dev-typescript package version to the current 0.3.2

When creating a project using the TypeScript template, an older version of the nativescript-dev-typescript package was being used. This updates the package.json file to use the latest 0.3.2 version

Already bumped in TJ.


Instructions for Podman need an update for Fedora 33

When running on Fedora 33, the podman instructions we provide need an update:
the images we recommend using all fail to start with
OCI runtime command not found error

as they attempt to create a storage overlay within the home directory of the user. Creating this directory is now being checked for explicit privileges (which seems like a good thing in principle?), and it will fail.
It seems this is primarily an issue with the published container images, and some vendors already provided updated versions. Need to document which ones actually work.

resolved

Did you also update the images we use with test containers?
On Wed, 18 Nov 2020, 17:01 Sanne Grinovero<EMAIL_ADDRESS>wrote:

Closed #448 https://github.com/hibernate/hibernate-reactive/issues/448.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/hibernate/hibernate-reactive/issues/448#event-4011744758,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEIQ5L3P4X43SMSE66LBNLSQP4WVANCNFSM4T2HNSEA
.

@DavideD I've been searching for them and couldn't find them.. were are they listed?

BTW I assume Testcontainers uses Docker? These specific images are necessary only for the latest podman. Of course +1 to align them.

It's about aligning them, so that the images used for testing are
consistent with the workflows.
This is the one for mysql:
https://github.com/hibernate/hibernate-reactive/blob/86941a12bb6cb87272b59efd593991118360d201/hibernate-reactive-core/src/test/java/org/hibernate/reactive/containers/MySQLDatabase.java#L12
In the same package you will find also the one for postgres and db2.
On Wed, 18 Nov 2020, 20:34 Sanne Grinovero<EMAIL_ADDRESS>wrote:

BTW I assume Testcontainers uses Docker? These specific images are
necessary only for the latest podman. Of course +1 to align them.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/hibernate/hibernate-reactive/issues/448#issuecomment-729937715,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEIQ5OCPH5DI3X5QTKPJQDSQQVVBANCNFSM4T2HNSEA
.

Thanks! #451


Support missing @Html.AttributeEncode() methods

In the old world, Encode() and AttributeEncode() have become more-and-more alike.  According to @GrabYourPitchforks, this was intentional as doing a less complete encoding in attributes has caused problems in the past.
In the new world, the current PR for HTML helpers (#50) includes AttributeEncode() methods which just delegate to Encode().  This supports copy-and-paste scenarios for existing MVC users.  But we may want to clean out the "extra" methods.

Duplicate of #1232 given where these methods should live (if they live).


GC segfault (no MWE, private repo)

I am getting a GC segfault (Enzyme#main, julia 1.9) on a private repo (that was used to produce #817, #840, #841). Individual calls to autodiff are fine now, but benchmarking with BenchmarkTools or MCMC sampling with DynamicHMC produces non-deterministic segfaults. I can provide the commit reference in a repo (necessarily large, not an MWE) or try to reduce this down to an MWE, but I am not sure who feasible that is.
I get these warnings too, not sure how relevant:
┌ Warning: Type does not have a definite number of fields
│   T = Tuple
└ @ Enzyme ~/.julia/packages/GPUCompiler/BxfIW/src/utils.jl:56
warning: didn't implement memmove, using memcpy as fallback which can result in errors
warning: didn't implement memmove, using memcpy as fallback which can result in errors
┌ Warning: Type does not have a definite number of fields
│   T = Tuple
└ @ Enzyme ~/.julia/packages/GPUCompiler/BxfIW/src/utils.jl:56
warning: didn't implement memmove, using memcpy as fallback which can result in errors
warning: didn't implement memmove, using memcpy as fallback which can result in errors

This is the segfault info:
[3126961] signal (11.128): Segmentation fault
in expression starting at /home/tamas/code/julia/misc/EnzymeBugMWE.jl/replicate_crash.jl:123
gc_try_setmark at /home/tamas/src/julia-1.9/src/gc.c:1965 [inlined]
gc_mark_scan_obj16 at /home/tamas/src/julia-1.9/src/gc.c:2250 [inlined]
gc_mark_loop at /home/tamas/src/julia-1.9/src/gc.c:2526
_jl_gc_collect at /home/tamas/src/julia-1.9/src/gc.c:3400
ijl_gc_collect at /home/tamas/src/julia-1.9/src/gc.c:3707
maybe_collect at /home/tamas/src/julia-1.9/src/gc.c:1078 [inlined]
jl_gc_pool_alloc_inner at /home/tamas/src/julia-1.9/src/gc.c:1443 [inlined]
jl_gc_pool_alloc_noinline at /home/tamas/src/julia-1.9/src/gc.c:1504 [inlined]
jl_gc_alloc_ at /home/tamas/src/julia-1.9/src/julia_internal.h:460 [inlined]
jl_gc_alloc at /home/tamas/src/julia-1.9/src/gc.c:3754
unknown function (ip: 0x7fc487831d1b)
unknown function (ip: 0x7fc487835142)
Allocations:<PHONE_NUMBER> (Pool:<PHONE_NUMBER>; Big: 23557712); GC: 11152

A variant of the error message is
GC error (probable corruption) :
Allocations: 75254965 (Pool: 75128539; Big: 126426); GC: 111

!!! ERROR in jl_ -- ABORTING !!!
0x7f3e316ba010: Queued root: 0x7f3e2e2ea8b0 :: 0x7f3e81f92660 (bits: 3)
        of type Task
0x7f3e316ba028: Queued root: 0x7f3e2e2eabd0 :: 0x7f3e81f92660 (bits: 3)
        of type Task
0x7f3e316ba040: Queued root: 0x7f3e2e2eaa40 :: 0x7f3e81f92660 (bits: 3)
        of type Task
0x7f3e316ba058: Queued root: 0x7f3e8692c010 :: 0x7f3e81f92660 (bits: 3)
        of type Task
0x7f3e316ba070: Queued root: 0x7f3e86924010 :: 0x7f3e81f92660 (bits: 3)
        of type Task
0x7f3e316ba088: Queued root: 0x7f3e86920010 :: 0x7f3e81f92660 (bits: 3)
        of type Task
0x7f3e316ba0a0: Queued root: 0x7f3e86918010 :: 0x7f3e81f92660 (bits: 3)
        of type Task
0x7f3e316ba0b8: Queued root: 0x7f3e86928010 :: 0x7f3e81f92660 (bits: 3)
        of type Task
0x7f3e316ba0d0: Queued root: 0x7f3e86914010 :: 0x7f3e81f92660 (bits: 3)
        of type Task
0x7f3e316ba0e8: Queued root: 0x7f3e86824650 :: 0x7f3e81f92660 (bits: 3)
        of type Task
0x7f3e316ba100: Queued root: 0x7f3e868244c0 :: 0x7f3e81f92660 (bits: 3)
        of type Task
0x7f3e316ba118: Queued root: 0x7f3e8691c010 :: 0x7f3e81f92660 (bits: 3)
        of type Task
0x7f3e316ba130:  r-- Stack frame 0x7ffda86c7280 -- 0 of 1444 (direct)
0x7f3e316ba158:   `- Object (16bit) 0x7f3e0463ea40 :: 0x7f3e05fb0551 -- [12, 24)
        of type Tuple{NamedTuple{(Symbol("1"), Symbol("2"), Symbol("3"), Symbol("4"), Symbol("5"), Symbol("6"), Symbol("7"), Symbol("8"), Symbol("9"), Symbol("10"), Symbol("11"), Symbol("12"), Symbol("13"), Symbol("14"), Symbol("15"), Symbol("16"), Symbol("17"), Symbol("18"), Symbol("19"), Symbol("20"), Symbol("21"), Symbol("22"), Symbol("23"), Symbol("24"), Symbol("25"), Symbol("26"), Symbol("27"), Symbol("28")), Tuple{Float64, Tuple{NTuple{9, Float64}}, Tuple{NTuple{9, Float64}}, Tuple{Tuple{Float64, Float64, Float64}}, Vararg{Any, 24}}}, Float64, UInt64}

[3161021] signal (6.-6): Aborted
in expression starting at REPL[37]:1
pthread_kill at /lib/x86_64-linux-gnu/libc.so.6 (unknown line)
gsignal at /lib/x86_64-linux-gnu/libc.so.6 (unknown line)
abort at /lib/x86_64-linux-gnu/libc.so.6 (unknown line)
gc_assert_datatype_fail at /home/tamas/src/julia-1.9/src/gc.c:1912
gc_mark_loop at /home/tamas/src/julia-1.9/src/gc.c:3020
_jl_gc_collect at /home/tamas/src/julia-1.9/src/gc.c:3400
ijl_gc_collect at /home/tamas/src/julia-1.9/src/gc.c:3707
maybe_collect at /home/tamas/src/julia-1.9/src/gc.c:1078 [inlined]
jl_gc_pool_alloc_inner at /home/tamas/src/julia-1.9/src/gc.c:1443 [inlined]
jl_gc_pool_alloc_noinline at /home/tamas/src/julia-1.9/src/gc.c:1504 [inlined]
jl_gc_alloc_ at /home/tamas/src/julia-1.9/src/julia_internal.h:460 [inlined]
jl_gc_alloc at /home/tamas/src/julia-1.9/src/gc.c:3754
unknown function (ip: 0x7f3df5e2e236)
unknown function (ip: 0x7f3df5e15830)
Allocations: 75254965 (Pool: 75128539; Big: 126426); GC: 111

Replication is in https://github.com/tpapp/EnzymeBugMWE.jl/pull/3.

With latest Enzyme#main (7da242da), I am getting
free(): invalid next size (fast)

which itself does not segfault but in a subsequent call
[322513] signal (6.-6): Aborted
in expression starting at REPL[15]:1
pthread_kill at /lib/x86_64-linux-gnu/libc.so.6 (unknown line)
gsignal at /lib/x86_64-linux-gnu/libc.so.6 (unknown line)
abort at /lib/x86_64-linux-gnu/libc.so.6 (unknown line)
unknown function (ip: 0x7f8ffeace5a3)
unknown function (ip: 0x7f8ffeb46146)
unknown function (ip: 0x7f8ffeb4803b)
__libc_free at /lib/x86_64-linux-gnu/libc.so.6 (unknown line)
unknown function (ip: 0x7f8fa28abfc7)
unknown function (ip: 0x7f8fa28ae1d5)
unknown function (ip: 0x7f8fa28ab9c2)
unknown function (ip: 0x7f8fa28aa774)
macro expansion at /home/tamas/.julia/packages/Enzyme/tHbH4/src/compiler.jl:9508 [inlined]
enzyme_call at /home/tamas/.julia/packages/Enzyme/tHbH4/src/compiler.jl:9200 [inlined]
CombinedAdjointThunk at /home/tamas/.julia/packages/Enzyme/tHbH4/src/compiler.jl:9163 [inlined]
autodiff at /home/tamas/.julia/packages/Enzyme/tHbH4/src/Enzyme.jl:205 [inlined]
autodiff at /home/tamas/.julia/packages/Enzyme/tHbH4/src/Enzyme.jl:214 [inlined]
logdensity_and_gradient at /home/tamas/.julia/packages/LogDensityProblemsAD/LIUcJ/ext/LogDensityProblemsADEnzymeExt.jl:73 [inlined]
#evaluate_ℓ#2 at /home/tamas/.julia/packages/DynamicHMC/pC62v/src/hamiltonian.jl:204
evaluate_ℓ at /home/tamas/.julia/packages/DynamicHMC/pC62v/src/hamiltonian.jl:202 [inlined]
#initialize_warmup_state#27 at /home/tamas/.julia/packages/DynamicHMC/pC62v/src/mcmc.jl:125 [inlined]
initialize_warmup_state at /home/tamas/.julia/packages/DynamicHMC/pC62v/src/mcmc.jl:123 [inlined]
#mcmc_keep_warmup#34 at /home/tamas/.julia/packages/DynamicHMC/pC62v/src/mcmc.jl:496
free(): invalid next size (fast)

does.
Not sure if I should open a separate issue or if it is the same.

With recent versions of Enzyme it is still the invalid next size (fast) bug. A replicator is in https://github.com/tpapp/EnzymeBugMWE.jl/pull/3.

https://github.com/tpapp/EnzymeBugMWE.jl/pull/5 replicates the GC segfault, again.
Since this is a GC-related bug, should I ask for help on the Julia forum debugging this?

zlog.txt

@vchuravy and I managed to debug the root cause of this to be a generic bug in LLVM itself wrt tail calls. Aka not Julia, Enzyme, or anything else but a bug that could impacat all programming languages/etc again independent of AD.
In the jll bump today we added some code that seems to remedy it here, but still we're uneasy about the internal LLVM miscompile without the workaround added.
See if it fixes for you?

@vchuravy, @wsmoses, thank you very much for looking into this. I still have the issue, ie
[2174897] signal (11.1): Segmentation fault
in expression starting at /home/tamas/code/julia/misc/EnzymeBugMWE.jl/replicate_crash.jl:58
unknown function (ip: 0x7f500000ac28)
unknown function (ip: 0x402fffffffffffff)
unknown function (ip: 0x7f500000a529)
macro expansion at /home/tamas/.julia/packages/Enzyme/6zfqp/src/compiler.jl:9515 [inlined]
enzyme_call at /home/tamas/.julia/packages/Enzyme/6zfqp/src/compiler.jl:9207
unknown function (ip: 0x7f4fcc940cda)
jl_apply at /home/tamas/src/julia-1.9/src/julia.h:1879 [inlined]
do_apply at /home/tamas/src/julia-1.9/src/builtins.c:730
AdjointThunk at /home/tamas/.julia/packages/Enzyme/6zfqp/src/compiler.jl:9176
top-level scope at /home/tamas/code/julia/misc/EnzymeBugMWE.jl/replicate_crash.jl:63
jl_toplevel_eval_flex at /home/tamas/src/julia-1.9/src/toplevel.c:903
jl_toplevel_eval_flex at /home/tamas/src/julia-1.9/src/toplevel.c:856
ijl_toplevel_eval_in at /home/tamas/src/julia-1.9/src/toplevel.c:971
eval at ./boot.jl:370 [inlined]
include_string at ./loading.jl:1899
_include at ./loading.jl:1959
include at ./Base.jl:457
jfptr_include_40365 at /home/tamas/src/julia-1.9/usr/lib/julia/sys.so (unknown line)
exec_options at ./client.jl:307
_start at ./client.jl:522

using the replication code in the tp/gcdbg2 branch of the repo above. But now it takes more runs to get a crash (about 10-20).
I am using Enzyme 78f151afaf4690ac20450ef50d9d24c9cf614aa3 and Enzyme_jll 3f279551013144a202d900222c32e5e06c30a0b6, basically from updating Enzyme#main this morning. Is this the right version, or should I wait until it trickles through?

I just tried Enzyme#master and I still have the issue. Updated the tp/gdcbg2 branch in the private repo above.
I understand that this is something outside Enzyme, but can you please link the relevant LLVM issue (if you opened one) so that I can follow how this develops?

After several weeks worth of deep GC debugging, we have a significant fix landed on enzyme proper whose jll will hopefully hit here in a day or two.
Not sure if it fixes this issue specifically, but I we definitely should retry once it lands here.
In particular it is aimed to fix that GC issue which was messing with our CI and blocking us from cutting a new release.

Okay the other GC fix has landed, @tpapp can you check if it fixes your/this issue as well?

yes, the issue is fixed now. thank you very much for all the work.


Support Type transformations for Contracts

Calling contract’s function transforms python types to Cairo types based on ABI:
int -> felt
tuple -> tuple
iterable -> array
dict -> struct
Function result is transformed from Cairo types to Python types.

https://github.com/seanjameshan/starknet.js/discussions/102


How do I access the response headers?

Problem statement
When making an HTTP POST request, I expect back a 201 status with a Location header. The Swagger API client I generated doesn't provide access to that.
Is there a way to access the response headers? I see that the go-openapi library handles the request and doesn't seem to pass the headers back. Am I missing something?
$ ./swagger version
version: v0.19.0
commit: 3123666
$ go version
go version go1.12.2 linux/amd64
$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/.cache/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/Desktop/"
GOPROXY=""
GORACE=""
GOROOT="/snap/go/3540"
GOTMPDIR=""
GOTOOLDIR="/snap/go/3540/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build217717785=/tmp/go-build -gno-record-gcc-switches"

specify it on the response in the spec, and the field will be generated

@casualjim thanks again for your help! Would you mind providing an example? I'm pretty new to swagger specs.
Here's the relevant post spec:
     "post": {
        "tags": [
          "SalesOrder"
        ],
        "summary": "Create a Sale Order",
        "description": "Response Message has StatusCode Created if POST operation succeed",
        "operationId": "SalesOrder_Post",
        "consumes": [
          "application/json",
          "text/json",
          "application/xml",
          "text/xml",
          "application/x-www-form-urlencoded"
        ],
        "produces": [
          "application/json",
          "text/json"
        ],
        "parameters": [
          {
            "name": "saleOrderUpdateDto",
            "in": "body",
            "description": "Defines the data for the Sale Order to create",
            "required": true,
            "schema": {
              "$ref": "#/definitions/SalesOrderUpdateDto"
            }
          }
        ],
        "responses": {
          "201": {
            "description": "Created",
            "schema": {
              "type": "object"
            }
          }
        },
        "security": [
          {
            "vna_oauth": [
              "financialstasks"
            ]
          },
          {
            "ipp-company-id": []
          },
          {
            "ipp-application-type": []
          }
        ]
      }

@casualjim nevermind... Google is my friend! :) Thanks for the pointer.

Just in case anyone else runs into this, I fixed the issue by adding the headers section to the 201 response in the spec like so:
        "responses": {
          "201": {
            "description": "Created",
            "headers": {
                "Location":
                    "schema": {
                        "type": "string",
                        "description": "Location on newly created Sale Order."
                    }
            },
            "schema": {
              "type": "object"
            }
          }
        },

@jeffreydwalter Hi i am using swagger 2.0 and i am to willing to get the location header in Response Headers can you please help me out with this

swagger: "2.0"
info:
version: "2019-10-21T06:52:36Z"
title: "datalake-dev-application"
basePath: "/v1"
schemes:

"https"
paths:
/files/ids/{id}:
get:
tags:
- Files
parameters:
- name: "id"
in: "path"
required: true
type: "string"
responses:
  200:
    description: "200 response"
    headers:
      location:
        type: "string"

security:
- ldsauthorizer: []

securityDefinitions:
ldsauthorizer:
type: "apiKey"
name: "Authorization"
in: "header"
x-amazon-apigateway-authtype: "custom"
i am using this ymal

@javerisagar 200 responses cannot (will not) contain a location header... The location header is generally included as part of a 20 sent in response to a PUT request.

Hello,
I'm facing a similar issue. In my case the field it's created but I cannot access it since there is no response object from the method due to it's a 302 response
"responses": {
  "302": {
    "description": "random description",
    "headers": {
      "Location": {
        "type": "string"
      }
    }
   }
  }
}

The goal of this method is to return an URL that can be consumed by the generated client in order to follow the redirection either manually or automatically.
Thanks

Hello,
I'm facing a similar issue. In my case the field it's created but I cannot access it since there is no response object from the method due to it's a 302 response
"responses": {
  "302": {
    "description": "random description",
    "headers": {
      "Location": {
        "type": "string"
      }
    }
   }
  }
}

The goal of this method is to return an URL that can be consumed by the generated client in order to follow the redirection either manually or automatically.
Thanks

I'm facing the same issue here, tried diffrent things on 302 response definition, but still the same result with Swagger loading but ending with "TypeError: Failed to fetch". Did you find a solution to this @Javirln?

You can typeswitch on the error to get the type for that response code, and then you can access the location property

The weird thing is, if I keep the status code to 302 (or even 300), I never get the response from either Swagger interface or Postman.  Do you have any idea what could cause that? Are 30x responses not supported?

The http client might be configured to follow redirects automatically


x/tools/gopls: high memory consumption

What version of Go are you using (go version)?

$ go version
go version go1.16.2 linux/amd64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
Ubuntu 20.04.2 LTS
go env Output
$ go env
GO111MODULE="on"
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/mauclair/.cache/go-build"
GOENV="/home/mauclair/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/mauclair/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/mauclair/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.16.2"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/dev/null"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/home/mauclair/tmp/go-build3185508688=/tmp/go-build -gno-record-gcc-switches"

What did you do?
Using emacs with lsp-mode + gopls, gopls used 10GiB memory
(if it's helpful, this is is a monorepo with a high volume of generated gRPC code)

What did you expect to see?
Lower memory consumption
What did you see instead?
10GiB memory consumed
Attached gopls memory profile
gopls.1480857-10GiB-nonames.zip

There's no critical threshold, it's just that they're very disproportionately expensive, so a byte slice with 1M elements might take hundreds of megabytes of memory in gopls.
I just mailed https://golang.org/cl/308730. It would be interesting to hear if it helps you at all. You can click the "Download" button to get clone instructions, then do go install in the gopls directory to install that version.

Great! My teammate, @nik-andreev, is planning to try this CL out and see what it does for our memory usage

There's no critical threshold, it's just that they're very disproportionately expensive, so a byte slice with 1M elements might take hundreds of megabytes of memory in gopls.
I just mailed https://golang.org/cl/308730. It would be interesting to hear if it helps you at all. You can click the "Download" button to get clone instructions, then do go install in the gopls directory to install that version.

I've just tried it out and still see the high memory consumption.
gopls.2096622-8GiB-nonames.zip

I also hit nil pointer panic after few hours of using the 308730 version of gopls. @mikeauclair and I use the same server (and version of go) but I ran gopls via VSCode with remote ssh. Here is the stack trace in case it is useful:
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x20 pc=0xb8825e]

goroutine 40047 [running]:
golang.org/x/tools/internal/lsp/cache.trimTypesInfo.func1(0xf5c850, 0xc120f4f580, 0xf5c500)
	/gopls/tools/internal/lsp/cache/check.go:817 +0x9e
go/ast.inspector.Visit(0xc0d04c9820, 0xf5c850, 0xc120f4f580, 0x0, 0x0)
	/usr/local/go/src/go/ast/walk.go:373 +0x3a
go/ast.Walk(0xf59c80, 0xc0d04c9820, 0xf5c850, 0xc120f4f580)
	/usr/local/go/src/go/ast/walk.go:52 +0x63
go/ast.Walk(0xf59c80, 0xc0d04c9820, 0xf5cbe8, 0xc120f49020)
	/usr/local/go/src/go/ast/walk.go:151 +0x31e
go/ast.walkExprList(0xf59c80, 0xc0d04c9820, 0xc120f51620, 0x2, 0x2)
	/usr/local/go/src/go/ast/walk.go:26 +0x9e
go/ast.Walk(0xf59c80, 0xc0d04c9820, 0xf5c850, 0xc120f4f5c0)
	/usr/local/go/src/go/ast/walk.go:104 +0x406
go/ast.Walk(0xf59c80, 0xc0d04c9820, 0xf5cf30, 0xc120f51640)
	/usr/local/go/src/go/ast/walk.go:143 +0x14b4
go/ast.walkExprList(0xf59c80, 0xc0d04c9820, 0xc120f51660, 0x2, 0x2)
	/usr/local/go/src/go/ast/walk.go:26 +0x9e
go/ast.Walk(0xf59c80, 0xc0d04c9820, 0xf5c6e8, 0xc120f4f600)
	/usr/local/go/src/go/ast/walk.go:137 +0xfc5
go/ast.walkExprList(0xf59c80, 0xc0d04c9820, 0xc0ccc7abb0, 0x1, 0x1)
	/usr/local/go/src/go/ast/walk.go:26 +0x9e
go/ast.Walk(0xf59c80, 0xc0d04c9820, 0xf5c530, 0xc120f4f640)
	/usr/local/go/src/go/ast/walk.go:207 +0x1f97
go/ast.walkStmtList(0xf59c80, 0xc0d04c9820, 0xc120f4f680, 0x3, 0x4)
	/usr/local/go/src/go/ast/walk.go:32 +0x9e
go/ast.Walk(0xf59c80, 0xc0d04c9820, 0xf5c698, 0xc120f49050)
	/usr/local/go/src/go/ast/walk.go:224 +0x1968
go/ast.Walk(0xf59c80, 0xc0d04c9820, 0xf5ca30, 0xc0ccc7abe0)
	/usr/local/go/src/go/ast/walk.go:98 +0x29f2
go/ast.walkExprList(0xf59c80, 0xc0d04c9820, 0xc11b21bf80, 0x6, 0x8)
	/usr/local/go/src/go/ast/walk.go:26 +0x9e
go/ast.Walk(0xf59c80, 0xc0d04c9820, 0xf5c6e8, 0xc120f4f6c0)
	/usr/local/go/src/go/ast/walk.go:137 +0xfc5
go/ast.walkExprList(0xf59c80, 0xc0d04c9820, 0xc0ccc7abf0, 0x1, 0x1)
	/usr/local/go/src/go/ast/walk.go:26 +0x9e
go/ast.Walk(0xf59c80, 0xc0d04c9820, 0xf5c530, 0xc120f4f700)
	/usr/local/go/src/go/ast/walk.go:207 +0x1f97
go/ast.walkStmtList(0xf59c80, 0xc0d04c9820, 0xc11971d800, 0x1e, 0x20)
	/usr/local/go/src/go/ast/walk.go:32 +0x9e
go/ast.Walk(0xf59c80, 0xc0d04c9820, 0xf5c698, 0xc120f491d0)
	/usr/local/go/src/go/ast/walk.go:224 +0x1968
go/ast.Walk(0xf59c80, 0xc0d04c9820, 0xf5ca08, 0xc120f49200)
	/usr/local/go/src/go/ast/walk.go:344 +0xce6
go/ast.walkDeclList(0xf59c80, 0xc0d04c9820, 0xc120f5e400, 0x2e, 0x40)
	/usr/local/go/src/go/ast/walk.go:38 +0x9e
go/ast.Walk(0xf59c80, 0xc0d04c9820, 0xf5c9b8, 0xc120f56500)
	/usr/local/go/src/go/ast/walk.go:353 +0x2446
go/ast.Inspect(...)
	/usr/local/go/src/go/ast/walk.go:385
golang.org/x/tools/internal/lsp/cache.trimTypesInfo(0xc0cf83fba0, 0x2, 0x2, 0xc1203c2be0)
	/gopls/tools/internal/lsp/cache/check.go:802 +0x50
golang.org/x/tools/internal/lsp/cache.typeCheck(0xf6a398, 0xc1203f5000, 0xc000336d00, 0xc00b2cd260, 0x2, 0xc003964bd0, 0x0, 0x0, 0x0)
	/gopls/tools/internal/lsp/cache/check.go:457 +0x11d2
golang.org/x/tools/internal/lsp/cache.(*snapshot).buildPackageHandle.func1(0xf6a398, 0xc1203f5000, 0xf58d80, 0xc000336d00, 0xc000f532c0, 0x0)
	/gopls/tools/internal/lsp/cache/check.go:121 +0x1bc
golang.org/x/tools/internal/memoize.(*Handle).run.func1(0xc0cf83fb00, 0xf6a398, 0xc1203f5000, 0xc003a8e400, 0xf58d80, 0xc000336d00, 0xc00b546e40)
	/gopls/tools/internal/memoize/memoize.go:322 +0xab
created by golang.org/x/tools/internal/memoize.(*Handle).run
	/gopls/tools/internal/memoize/memoize.go:315 +0x185

Small update here: I was able to slice ~8% off of heap utilization by moving some of our byte slice literals to use //go:embed (we generate a bunch ourselves instead of using protoc-gen-go so it was fairly easy to switch) so there's something to some of this being due to those literals. I'm going to take a look at what our new top offenders are and see if there are any common threads.

Sorry I didn't mention here: the latest patch set of https://golang.org/cl/308730 should no longer panic. You can try that out if you want; I'm going to try to get it merged today.

👍 I'll check it out

Sorry I didn't mention here: the latest patch set of https://golang.org/cl/308730 should no longer panic. You can try that out if you want; I'm going to try to get it merged today.

I checkout this patch, but the problem with high memory consumption still persists. My computer freezes completely after trying to go to a definition inside aws-sdk-go.
system
5.8.0-50-generic #56~20.04.1-Ubuntu SMP Mon Apr 12 21:46:35 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

go version
 go version go1.16.3 linux/amd64

gopls version
golang.org/x/tools/gopls master
    golang.org/x/tools/gopls@(devel)

I stoped the process because as I told, my computer freezes completely, so the generated log is only 2gb but it increases a lot more than that.
I had this problem using both neovim and vim with vim-go or Coc-go
If you need more information I'll be glad to provide.
gopls.8453-2GiB-nonames.zip

@drocha87 Please file a new issue. If you're working in an open source repository, full repro instructions would be helpful.

I'm not sure about open a new issue since this one is still open and I'm reporting the feedback about the patch proposed in the discussion here.
The repo I'm working on is a private repo, but I'm having high memory consumption when I try to go to a definition inside the aws-sdk-go repo, so I think is pretty straight forward to repro this issue.
Right now I don't have time to setup a repro, but I'll be glad to do that in my free time.

Any update on this? I am working in a mono repo (private) and I can't even use gopls. It climbs within 25 minutes of usage and hits 16+ Gigs between go and gopls.

<EMAIL_ADDRESS>significantly reduces gopls' memory usage, up to an order of magnitude on larger repositories.

(please open a new issue if you are still struggling with memory usage)

Thanks! We've updated to 0.12.0 and are seeing roughly the order-of-magnitude decrease in memory footprint reported in the release notes

@mikeauclair thanks for following up! That's great to hear.

This is still happening

$ gopls version
golang.org/x/tools/gopls v0.12.4
<EMAIL_ADDRESS>h1:nce5etAamR46d9oNGxop1aRK5rDQ0NqcY/SHIcyfEKY=

$ go version
go version go1.20.5 linux/amd64

Hi @folago
Are you working in open source? Are you willing to help us understand your workspace?
To start, could you share the output of gopls stats -anon? That will give us a hint of where to look. Then we may want to grab some memory profiles.

Not opensource unfortunately.
I now use v0.11.0 that uses between 7 and 10 GB.
I switched to v0.12.4 and it just got oom killed.

$ gopls stats -anon
Initializing workspace...     done (5.788011924s)
Gathering bug reports...      done (984.377211ms)
Querying memstats...          done (62.381751ms)
Querying workspace stats...   done (42.190485ms)
Collecting directory info...  done (77.805032ms)
{
  "DirStats": {
    "Files": 29310,
    "TestdataFiles": 250,
    "GoFiles": 22818,
    "ModFiles": 2,
    "Dirs": 4245
  },
  "GOARCH": "amd64",
  "GOOS": "linux",
  "GoVersion": "go1.20.5",
  "GoplsVersion": "v0.12.4",
  "InitialWorkspaceLoadDuration": "5.788011924s",
  "MemStats": {
    "HeapAlloc": 484451936,
    "HeapInUse": 617086976,
    "TotalAlloc": 869349072
  },
  "WorkspaceStats": {
    "Files": {
      "Total": 22928,
      "Largest": 11691838,
      "Errs": 0
    },
    "Views": [
      {
        "GoCommandVersion": "go1.20.5",
        "AllPackages": {
          "Packages": 3118,
          "LargestPackage": 572,
          "CompiledGoFiles": 23528,
          "Modules": 320
        },
        "WorkspacePackages": {
          "Packages": 483,
          "LargestPackage": 266,
          "CompiledGoFiles": 3436,
          "Modules": 1
        },
        "Diagnostics": 0
      }
    ]
  }
}

Anything else I can provide?

That output shows gopls using only 617 MB after its initial workspace load, which indicates that most of the memory is spent holding data related to open packages.
I'll also note that your largest workspace package has 572 files, which is quite large. Elsewhere, we have seen similar problems related to large packages.
Can you do an experiment? Start by opening a low-level package that does not import this large package transitively (something like a "util" package that has few imports). Does gopls stabilize at a low memory usage?
Then open a package that has a large import graph, and which imports this large package transitively (something like a "main" package). Does this cause your memory to blow up?
As a next step, we can try looking at a memory profile. I am confident we can fix this problem, if you are willing to help us investigate. I will open a new issue to track this fix.

That output shows gopls using only 617 MB after its initial workspace load, which indicates that most of the memory is spent holding data related to open packages.
I'll also note that your largest workspace package has 572 files, which is quite large. Elsewhere, we have seen similar problems related to large packages.
Can you do an experiment? Start by opening a low-level package that does not import this large package transitively (something like a "util" package that has few imports). Does gopls stabilize at a low memory usage?

Yes, this is what I observed. If I stay away from some packages with the accursed large dependency the memory is quite low with v0.12.4:

Then open a package that has a large import graph, and which imports this large package transitively (something like a "main" package). Does this cause your memory to blow up?

Yes this is what I have experienced, gopls starts consuming all the memory available and it does not stop until it gets oom killed (lucky) or my machine freezes and I have to force a reboot.

As a next step, we can try looking at a memory profile. I am confident we can fix this problem, if you are willing to help us investigate. I will open a new issue to track this fix.

You mean start add -profile.mem=string as parameter to start gopls?

This is the profile I get by opening a package without the huge dep.
gopls.zip
I can open the bad one and try to stop it before it gets oom killed or my machine freezes.

Cannot manage to get a profile when I open the huge dependency, once gopls starts eating all the memory it does not care if I stop neovim or if I call :LspStop and now it seems to just freeze.
I can kill it but then it leaves the profile file empty. Does it handles a signal better than SIGTEM?

Thanks @folago -- the profile after opening the huge dep is what we need.
Here's how you can get it: start gopls with for example -debug=localhost:8080, and while gopls is churning on the large dep, run: go tool pprof http://localhost:8080/debug/pprof/heap.
That should allow you to grab a snapshot of the gopls heap in action. If you can share the entire result, that would be great. But we would also learn a lot simply from the output of top 50 and top 50 cum (in the pprof REPL).

Ah nice!
I made a small script to curl the heap profile to a file each second since it was difficult to catch it before my machine got unusable.
This is the second last, the last one was empty.
heap.90.zip
If the other profile can be useful to compare let me know.
Posting also the script in case there is something wrong with it that I missed:
#! /bin/sh
for i in {1..1000}; do
    curl http://localhost:6060/debug/pprof/heap > heap.$i.out
    sleep 1
done

Also these are my settings for gpls in neovim:
    settings = {
        gopls = {
            analyses = {
                unusedparams = true,
                unusedwrite = true,
                fieldalignment = true,
                nilness = true,
            },
            staticcheck = true,
            -- gofumpt = true,
            templateExtensions = { 'tpl', 'tmpl' },
        },
    },

Just in case this is helpful, since I have few analyses turned on.

Thanks so much for helping us investigate!
Have not yet investigated your profile, but already I have a theory: both the nilness analyzer and staticcheck use a form of SSA/SSI analysis that can be quite expensive. That could explain the disproportionate cost of analysis in certain packages.

I can try to disable those two and send another profile.

Nice. I think we have a plausible theory. Now for a fix...
For some background: analyzers that do SSA analysis are essentially broken in v0.11.0, because they do not have generated SSA for non-workspace packages. We "fixed" this in v0.12.0, but clearly that fix is not viable in some cases.

It is weird tho that it reads so much less from disk, before it was in the GB range I think once I saw it go to ~12GB

That's a useful datapoint. Most likely this is serialization of SSA structures. In particular, if they take more than 1GB, you'll be churning through the fixed-size cache at a high rate, which could lead to additional performance problems.

I see, thanks for the explanation and for the workaround.
I guess I can live without those checks for now, looking forward to the next release.
And let me know if there is anything else that I can do to speed up the diagnosis.

@folago you might try enabling just nilness. I would be curious to know if that performs OK. If so, it indicates we're doing something wrong with staticcheck's analysis facts. I would expect nilness and staticcheck to have similar costs, as both are constructing an IR for the source being analyzed.

Thanks. As noted in #61178, the profile definitely indicates that the majority of allocation is related to staticcheck.
Now that we have an approximate cause, let's continue discussion on that issue. My guess is that we will be able to reproduce, by enabling staticcheck with some repositories we know to be similarly problematic for analysis.


Any way to get the ID to persist forever (even after closing and re-opening Unity project)?

Every time I close and re-open the Unity project, the ID is reset to a new one on every object that has the UUID component, is there a way to make it persistent (so that once an ID is generated, it never changes)? Unity 2019.3.8

If I changed the id and backup id variables from public to private, it appears to keep the originally-generated ID's indefinitely, even though they were marked to be serialized when they were private, not sure if this is normal behavior


Fix error conversion for WorkflowExecutionAlreadyStartedError

What changed?
Convert perisistence.WorkflowExecutionAlreadyStartedError to types.WorkflowExecutionAlreadyStartedError instead of types.InternalServiceError

Why?
We treat types.InternalServiceError as a server error in frontend, but WorkflowExecutionAlreadyStartedError should be an application error. And this affects our availability when customers keeps retrying on WorkflowExecutionAlreadyStartedError

How did you test it?
existing test

Potential risks
It's possible that customers at client side check the error type, and since this change changes the error type, it could be a breaking change for the customers.

Release notes

Documentation Changes

Yeah, for purely-internal this certainly makes sense.  Even publicly we've had this in our APIs since the reuse-policy was introduced: https://github.com/uber/cadence/pull/1185

Pull Request Test Coverage Report for Build 0180dedb-8f71-47d5-be21-ad5148114349

0 of 1 (0.0%)  changed or added relevant line in 1 file are covered.
12 unchanged lines in 4 files lost coverage.
Overall coverage increased (+0.07%) to 56.921%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

service/history/handler.go
0
1
0.0%

Files with Coverage Reduction
New Missed Lines
%

common/task/weightedRoundRobinTaskScheduler.go
1
89.64%

service/history/execution/mutable_state_task_refresher.go
1
73.58%

common/util.go
2
51.17%

service/history/shard/context.go
8
64.32%

Totals

Change from base Build 0180dd57-a86d-49ac-b027-7918f6353dfa:
0.07%

Covered Lines:
83982

Relevant Lines:
147542

💛  - Coveralls


Enable deprecation logging for deprecated methods currently used by Kotlin plugin

Kotlin plugin uses the following methods that are being deprecated:

AbstractCompile.getDestinationDir()

When a new version of Kotlin plugin is released, update the plugin in Gradle, update the tests and reevaluate whether deprecation logging can be enabled for those methods.

For reference: https://youtrack.jetbrains.com/issue/KT-46019

If the corresponding Koltin Plugin release does not happen before the 7.1 release branching, please move the milestone to 7.2 RC1.

Kotlin 1.5 is out: https://github.com/JetBrains/kotlin/releases/tag/v1.5.0

blocked by #17465


xgboost4j support of scala 2.13 or scala 3?

Do you plan to update xgboost4j to support scala 3 or scala 2.13?
any update would be highly appreciated.

Yeah, I saw many users are requesting this feature, I will check that.

Thanks.
If I could be of any help, don't hesitate to reach out.

@MohammadForouhesh Wow, if you can help, that will be great. Could you contribute this feature?

@wbo4958 yeah i am open to help, but it would be best if one of the more seasoned contributers guids me through the source code first.

There are few bits we need before working on the scala 2.13 support :

Flink 1.8 -> 1.17:  https://github.com/dmlc/xgboost/pull/9046
Scalatest  3.0.8 ->  3.2.15 : https://github.com/dmlc/xgboost/pull/8925
Spark to 3.3.0 +

I believe, https://github.com/dmlc/xgboost/pull/8310 can be reused


adding a both top and bottom text with already multiple inputs makes it cluncky?

Message: Error: Request timed out (>16000ms) on POST /channels/702245737861480519/messages
Stack Trace: Error: Request timed out (>16000ms) on POST /channels/702245737861480519/messages
at Timeout._onTimeout (/home/esmBot/esmBot/node_modules/eris-sharder/src/structures/SyncedRequestHandler.js:20:24)
at listOnTimeout (node:internal/timers:557:17)
at processTimers (node:internal/timers:500:7)

Duplicate of #138


Update mm.com/download instances

Summary
Hi @cwarnermm~
We pushed up a recent change to the /download and /deploy URL setup on mm.com.

The /download page (where we used to house app downloads) now lives at /apps
And /download redirects to /deploy

Asana ticket with some context here.
As I made the change, I figured we would need to do some search and replace in docs, and didn't know if we communicated this switch (maybe we did and this PR is moot haha).
Also found a few instances where we were using old anchor links that no longer exist as well.
Drafting this PR for now to get a gut check from folks that I've made the right replacements.
There's a lot of instances 😅
Let me know if you have any questions. TY!
cc: @BenLloydPearson for visibility/feedback

Thanks, @emdecr! This is great! I'll perform a similar search and replace review to catch any stragglers. To summarize the website URL changes:

App downloads, including mobile and desktop, now live at /apps from /downloads
self-hosted deploys live at /deploy
Correct?

A couple of things to note:

Docs has a backlog task to change all Cloud badges URLs from /download to https://customers.mattermost.com/cloud/signup. Any concerns about changing the Cloud badge updates in this PR from /apps to /cloud/signup?
You can safely ignore any source files in /source/archive. Source files in the archive folder are not converted into static HTML during builds, and are not returned in search results. I recommend removing the changes to archived files in this PR to simplify the PR itself by making changes only where needed.

@cwarnermm Yes, those two points are correct~
Re: your notes –

Hmm. https://customers.mattermost.com/cloud/signup has just been redirected to https://mattermost.com/sign-up, so we'll probably want to switch it to that mm.com URL.
Ah, cool. Sounds good, I'll revert the changes made in archive files~

I'm about to jump into some tasks, but I'll try to circle back on this within the day. TY!

If https://mattermost.com/sign-up/ results in users getting a Cloud instance, then that's the perfect URL to use for the Cloud badges.

@cwarnermm The change was reversed due primarily related to an in-product link going to mm.com/download for clients (there is also a Google metadata reason that supported reverting back).

Thanks, @nab-77! In summary:

mm.com/apps - works; goes to clients page
mm.com/download - works; goes to clients page
in the future: mm.com/download will go to server page

@cwarnermm What you just outlined is how I understand it as well, fwiw.
Aaron just clarified that we're still good for using /apps because we want the page to start ranking in the meantime.
I think these changes are still good to go. Cloud Badges go to /sign-up and we're now making use of the /apps page.
If it looks good to you, I can remove my Do Not Merge tag and proceed with the review process? TY~!


Triage MultiDynamoDBStoreTest failure in Travis CI

Recent builds:
https://travis-ci.org/awslabs/dynamodb-titan-storage-backend/jobs/226287931
https://travis-ci.org/awslabs/dynamodb-titan-storage-backend/jobs/226377196
Travis CI output at the end of the file. Usually takes around 14 minutes to run. These tests pass when run using the instructions at the end of the README on EC2 m4.10xlarge instances.
-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running com.amazon.titan.diskstorage.dynamodb.MultiDynamoDBStoreTest
No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.
Check the details on how to adjust your build configuration on: https://docs.travis-ci.com/user/common-build-problems/#Build-times-out-because-no-output-was-received
The build has been terminated

@F2006 This test is the one causing the errored emails I think.
https://travis-ci.org/awslabs/dynamodb-titan-storage-backend/builds/226407287
shows "Job errored" status, while for the GraphTest ones it only shows "Job failed". Currently this test times out for lack of output. Can you make a PR that causes something to be printed every five minutes or so to the console?

@amcp pull request (https://github.com/awslabs/dynamodb-titan-storage-backend/pull/102) made, will monitor the build and see how it goes: https://travis-ci.org/awslabs/dynamodb-titan-storage-backend/builds/226481447

@F2006 thank you. I reviewed, and now I will sleep, so I will look at your updates in the morning.

Probably fixed in #102, will merge and then enable the MultiStoreTest again

https://travis-ci.org/awslabs/dynamodb-titan-storage-backend/jobs/227081845#L4552
Heart is beating!


Upgrading leaflet

Leaflet is currently in version 0.7.7.
Trying it, I faced numerous GUI bugs. I tried to upgrade it and it worked (for me) as expected.
How do you think about upgrading Leaflet to the stable version?

I'd love to see a PR for this :)

Fixed in v2.7.0


Custom className for Field (of type select)

I want to have something like this
<Field component="select" class="custom-select" />
to be :
<select class="custom-select"> .... </select>
How do I do?

You need to use className.

Thank you


New files get default directives

We currently don't have Stamp and PBASIC directive quick-access buttons - we need to ease the pain of users creating new files.
For a temporary time, we want all new files to automatically have the default Stamp and PBASIC directives inserted into them.
'{$STAMP BS2}
'{$PBASIC 2.5}

Note: this will cause the user to always be prompted to save a new file because it now has text in it.

Understood; we accept those results as having the directives are normally what the user wants as he/she is starting to write new code anyway.
This is a temporary measure that will be replaced with a different, although similar, method of swiftly getting the directives in-place.  We may or may not choose to address the non-blank-but-still-disposable source issue in a nicer way in the future.

UPDATE: I updated the first post's code to include two blank lines.
Is it possible to place the cursor at the start of the 4th line (2nd blank line) when, and only when, this text is placed in the edit by the New operation?

Verified done.


Add command line arguments for verbose and streamed output

Solved in https://github.com/antonrotar/command_runner/pull/19.


In Mobile

Does this works perfectly with mobile devices ??

Closing, hopefully I was able to answer your question.


Abbreviations are mis-transliterated in Wiki page names

A significant fraction of the pages in the Status/ wiki namespace are mis-named. Specifically, the string GHC is transliterated as gh-c. For instance, Status/GHC-7.10.3 is translated to  status/gh-c-7.10.3.
I suspect this isn't worth fixing as it's quite easy to fix-up post-facto but I thought I should at least record the infelicity.

I am actually starting to think that maybe we do want to fix this. This mistake is made for numerous abbreviations including:

GHC
CAF
FFI
MSYS

Even if we fixed these, I'm generally concerned that the change in capitalization will result in broken links. We should at very least produce a name mapping that can be used to generate an nginx redirection table.

I can see where this goes wrong. We use the casing library to convert these names, and specifically, we use fromHumps to parse the original name into "words". That parser expects camel case or pascal case, and specifically, the .NET-flavor, where abbreviations longer than 2 characters are written like words (e.g. XmlParser, not XMLParser).
I'll see if I can come up with a better approach to parsing these.

It seems that applying the possible parsers in the right order does the trick: instead of fromHumps, we'll use fromKebab >=> fromSnake >=> fromHumps. In this particular case, fromKebab will split things into "GHC", "7.10.3", and then fromHumps will operate on "GHC", which, due to no non-uppercase letter following any uppercase letter, will not split it any further.
I'll push the fix once I'm done testing.

The capitalization change, btw., is inevitable, as Gitlab will automatically lowercase everything; we inject dashes to keep it readable and comply with Gitlab's naming conventions.
If we want external links to remain functional, we will need a translation table though, or a very clever way of replicating the name mangling on the fly.

9e5c2ba6fe023373dbb0f29fb5f356206e75fc17 fixes the name mangling so that GHC-7.10.3 becomes ghc-7.10.3 rather than gh-c-7.10.3.
We still need to emit a mapping though.

Oh, and we need nginx rewrites anyway, because the old links will point to /trac/wikis/ghc/..., whereas the new ones need to go to /ghc/ghc/wikis.

a467e24dd989efcfaaf7b51928821b8c73c33583 adds an nginx rewrite rule generator. Generated rules are appended to rewrite.nginx in the CWD; for a clean set of rules, one should clear out this file prior to running an import, post-process it with something like sort -u to remove duplicates, and then paste it into the nginx configuration in the appropriate location. (Actual usage of said rules untested as of yet).

The capitalization change, btw., is inevitable, as Gitlab will automatically lowercase everything; we inject dashes to keep it readable and comply with Gitlab's naming conventions.

Is this really true? Looking at https://gitlab.staging.haskell.org/ghc/ghc/wikis/Trac-Ticket-Import I'm a bit doubtful.


lol

Hi im gonna use your engine for my mod you want no use your engine sent me message my twitter Twitter:CherryDevUwU
<3 thank for your time

fun fact: this isn't how this repo works
if your gonna use psych engine you don't need to upload it to this repository just leave it in your own

please leave im a kid who some what knows how to code 'YOU DONT'

another fun fact:
var bitches:Int = 1;
var family:Bool = true;
var gotalife:Bool = true;
var adopted:Bool = false;
var STUPID:Bool = false;
var ratio:Int = 0;
var hasBrain:Bool = true;
var stupidKid:String = 'NimuDevUwU';

if (stupidKid == 'NimuDevUwu')
{
    bitches = 0;
    family = false;
    gotalife = false;
    adopted = true;
    STUPID = true;
    ratio++;
    hasBrain = false;
}

BURNED IN CODE FORM

var bitches:Int = 1;
var family:Bool = true;
var gotalife:Bool = true;
var adopted:Bool = false;
var STUPID:Bool = false;
var ratio:Int = 0;
var hasBrain:Bool = true;
var stupidKid:String = 'NimuDevUwU';
override function create()
{
if (stupidKid == 'NimuDevUwU')
{
bitches = 0;
family = false;
gotalife = false;
adopted = true;
STUPID = true;
ratio++;
hasBrain = false;
}
}
ima make that actual usable code

for me its this:
package;
class SmartKid extends RealSmartass
{
var bitches:Int = 1;
var family:Bool = true;
var gotalife:Bool = true;
var adopted:Bool = false;
var STUPID:Bool = false;
var ratio:Int = 0;
var hasBrain:Bool = true;
var smartKid:String = 'Averey';
override function create()
{
    if (smartKid == 'Averey')
    {
        bitches = 1;
        family = true;
        gotalife = true;
        adopted = false;
        SMART = true;
        ratio++ = false;
        hasBrain = true;
    }
}

}

HTML Editing is way too easy

HTML Editing is way too easy

bro just gave him the perfect username

TRUE

ahh much much better now

WAIT DID IT GET CLOSED??? WAHOOO


[NBS] Adjust performance profile according to cpus count used by nbs

https://github.com/ydb-platform/nbs/blob/main/cloud/blockstore/libs/daemon/common/config_initializer.cpp#L168
Currently we calculate performance profile based solely on number of cpus used by compute. This results in lower limits that we could potentially give, when nbs is running with extended cpu set (e.g. on amd platforms etc)
Current limits were calculated with assumption nbs is running on 16 cores. We need to get current cpu set from procfs and adjust performance profile accordingly
$ cat /proc/`pidof nbsd`/status | grep -i cpu_allowed_list
Cpus_allowed_list: 0-7,66-71,128-135,194-199

$ cat /etc/systemd/system.conf | grep -i cpuaffinity
CPUAffinity=0,128,1,129,5,133,69,197,6,134,70,198,7,135,71,199,2,130,66,194,3,131,67,195,4,132,68,196

Тут еще нужно смотреть на пропускную способность сети т.к. нельзя выдать квоты на VM больше чем вообще сеть тянет.
А на хосте еще могут быть и другие пользователи.


Support Rider's Resharper EditorConfig values

Rider creates its own editorconfig values prepended with resharper but add a lot of value to how code editing is done. I am having trouble with formatting inconsistencies between a developer working in Visual Studio Code and myself working in Jetbrains Rider. Since Rider has more granular support for formatting than Visual Studio Code it is an issue of inconsistent formatting
I assume I would request this feature in VSC rather than on the editorconfig github since VSC would have to implement those features. Is this a possibility?

Editorconfig in vscode is an extension as you mention, the request would need to go there first and then they could propose APIs for us to implement if there are gaps.


New Feature: arbitrary HTTP methods

My own use case has to do with WebDAV. It defines a set of additional HTTP methods including PROPFIND, MKCOL, COPY, MOVE. Also, some REST services employ the PATCH method for modifying a data item in place.

Hi @sevaa - thanks for your request. It looks like adding support for arbitrary HTTP methods is indeed feasible.
Should we really allow arbitrary HTTP methods, or would it be better / possible / practical to lock down the set of additional methods? Are there any additional considerations I should look into regarding support for WebDAV?

WebDAV defines about 6 additional methods. There is a Microsoft extension that defines about 10 more. I am not currently interested in testing those, but they exist. With this in mind, extending the current radio button based UI doesn't seem practical. Maybe you could introduce a radio button called "Other" with a combo box of additional methods, or with an edit box... Your choice, ultimately.
As for additional considerations, maybe digest auth... WebDAV is rarely anonymous in real life.

Great, thanks for the additional insight!

I would really like at least HTTP patch support

Accepted: we will implement support for patch and arbitrary http methods.


Updates tests to use Higher Order Expectations

Hi Erika,
You mentioned the other day about this on Twitter, and it looked cool so wanted to contribute! I've refactored the Pest suite to the new Higher Order Expectations, which removes some of the boilerplate.
Hope you had a good weekend!
Kind regards,
Luke

Hey @lukeraymonddowning , thanks so much, I appreciate the contribution! 👍🏼 💯 ✨


How to set MinValue and MaxValue on Stacked columns?

Hi,
I am trying to set MinValue and MaxValue in a Cartesian Chart with stacked columns without success.
In particular when I set MinValue some columns become hidden, this is the result

And this is the piece of my code (Xaml):

and this is the code in my ViewModel

This should be the expected result and the Y-Axis should start from 15. (with the focus between 15 and 20)

Is there a way to solve this problem?
Thanks

This seems a bug to me

Any news on this bug? I need this functionality as well

@beto-rodriguez I have the same issue. Any news on this bug?

Hi @beto-rodriguez , any news about this bug? we have the same issue in our project..
Best wishes,
Paolo


Passwords exposed in log files

I intentionally left password fields blank in my config files because I do not want any passwords stored in plain text. Upon running a rocketeer command that requires SVN authentication, I was prompted for credentials as expected. What I didn't expect was that the SVN checkout command would be logged with username and password options in plain text. I discovered this by chance when browsing through the logs. At the very least, there should be some mention of this in the documentation. More to the point, a better logging strategy should be used to avoid exposing passwords.

I think the second solution is best, any sensitive information should be screened and hidden before passed on to the logs, including within commands that are run on server. In the meantime do you have the possibility to use an SSH checkout rather than an HTTP one? So that only your username is present in the logs but not any kind of password

Unfortunately no. Unfortunately we don't have control over the SVN server configuration.


"chuck item" leaves empty line when there is trailing comma

In the following typescript:
[
    foo,
    bar,
]

Saying chuck item bat results in the following:
[
    foo,

]

Note that if bar has no trailing comma, it removes the line, as desired.

This is of course because we are only removing the trailing delimiter. We probably need to make that logic more advanced.

A possible simple solution for this is to prefer removing leading delimited range instead of trailing. Should we do this on all targets or should we make a specific ItemTarget with this behavior?

Huh yeah interesting idea. It's prob worth changing it on all targets and seeing what breaks. Should be trivial to try and I could imagine nothing will break

This actually broke 45 tests. When you have the time I would like to talk to you about it. Basically we get off by one errors on the that mark.
const value = "Hello world"; "chuck vest". At the moment the that mark will be an empty selection adjacent the equal sign. If we prefer the leading range it will be adjacent the const instead.

https://github.com/cursorless-dev/cursorless/pull/850#issuecomment-1179610276


Add Code of conduct file

I would like to add the code of conduct file in the repository which is currently missing.

i would like to contribute to this issue... kindly assign me i am GSSOC'24 contributor

Hi @suhanipaliwal !
I have previously worked with quality documentations and written Medium Articles hence I am interested to work on this issue. Could you please assign me this issue?

Hello @suhanipaliwal
I am a GSSOC'24 contributor and I have good experience of writing articles and documentations for different platforms, making sure of appropriate indentations, vocabulary usage and an efficient understandability. I request you to please assign me this issue.

Could you please add the labels of GSSOC'24 and the label of appropriate level like level 1, 2 or 3.


chore(openstack): add OVHcloud example

[OVHcloud openstack image example]
Add flatcar image import example for OVHcloud.
How to use
Try using this image on OVHcloud, we have used this for years now.
Closes: https://github.com/flatcar/Flatcar/issues/1453

@tormath1 Just pushed the OVHcloud version, largely copied from Openstack but with some modifications (notably on the image).


macOS window resize draws everything black while resizing

Operating system or device - Godot version:
macOS - Godot 2.1.3
Issue description:
When resizing the window, everything is drawn black, when you finish it goes back to normal. This makes it hard to resize since you can't see anything.
In Windows this works as expected and draws correctly during the window resize
Steps to reproduce:
Run the game and resize the window by dragging the edges or corners.

Tested on Godot 3.06 OSX 10.12 mid 2014 macbook air, could not reproduce.
Tested resizing the Godot engine window, no black screen. Resizes as normal.
 Resizes as normal.
Propose closure.
@lexum0

Would be fixed in the 2.1 branch too now with #9836, so closing indeed.


Test/issue #85

Modified output files path to temporary directory
Case #85

:+1: but please squash

Hi, the branch should now be squashed and ready for merge.  Thanks.


[SPARK-35268][BUILD] Upgrade GenJavadoc to 0.17

What changes were proposed in this pull request?

This PR upgrades GenJavadoc to 0.17.
Why are the changes needed?

This version seems to include a fix for an issue which can happen with Scala 2.13.5.
https://github.com/lightbend/genjavadoc/releases/tag/v0.17
Does this PR introduce any user-facing change?

No.
How was this patch tested?

I confirmed build succeed with the following commands.
# For Scala 2.12
$ build/sbt -Phive -Phive-thriftserver -Pyarn -Pmesos -Pkubernetes -Phadoop-cloud -Pspark-ganglia-lgpl -Pkinesis-asl -Pdocker-integration-tests -Pkubernetes-integration-tests unidoc

# For Scala 2.13
build/sbt -Phive -Phive-thriftserver -Pyarn -Pmesos -Pkubernetes -Phadoop-cloud -Pspark-ganglia-lgpl -Pkinesis-asl -Pdocker-integration-tests -Pkubernetes-integration-tests -Pscala-2.13 unidoc

Test build #138070 has started for PR 32392 at commit 60b9a23.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/42590/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/42590/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/42590/

Test build #138070 has finished for PR 32392 at commit 60b9a23.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/138070/


move code block under condition (context)

Patch for source management bug in services api.
If accessed delta[update_config][sources] once, might as well move code that will do it again just to be safe.

This change has you changing the current_sources variable while looping over it, which is bad.

forget that last comment, I can't see things when they are colour highlighted apparently :|


[PAPI-302] Transaction controller route examples and response documentation

I've removed [Authorize] on GET transactions and GET transactions/{hash}. Not sure if I can remove without side effects for the UI so let me know and I can add them back.


Drop python 3.8

The more recent dask versions no longer support 3.8 and I don't think it's worth keeping it around for this lib

Codecov Report

Merging #35 (9e16df0) into main (ba3801c) will not change coverage.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@           Coverage Diff           @@
##             main      #35   +/-   ##
=======================================
  Coverage   92.85%   92.85%
=======================================
  Files           2        2
  Lines         112      112
=======================================
  Hits          104      104
  Misses          8        8

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


Fix CVE-2024-45337

Summary
update the “/x/crypto” module in their go.mod fields with the remediated v0.31.0 or later to fix CVE-2024-45337
Related issue(s)
Fixes #
Tests

[ ] Unit/function tests have been added and incorporated into make unit-tests.
[ ] Integration tests have been added and incorporated into make integration-test.
[ ] E2E tests have been added and incorporated into make e2e-test-all.
[ ] List other manual tests you have done.

/test test-integration

/override test-integration


limit size of trigger payload

As the code currently exists, there is potentially no limit to the size of the payload we will attempt to post to a trigger. This is bad.
I believe there are limits we may be able to set with consumer parameters that may do this automatically for us (see max_partition_fetch_bytes though this may involve some partition math).  However, failing that, we can examine the size of each consumed message and use that to actively limit the amount of data posted to the trigger.
http://kafka-python.readthedocs.io/en/master/apidoc/KafkaConsumer.html

max_partition_fetch_bytes exists and has a default setting of 1MB which effectively sets an upper bound on the size of the payload. No further changes needed at the moment.