text:
Fast scroll issue fixed

Description (required)
Earlier, accidental touch on right side of screen would lead to abrupt jump to images in explore activity due to fast scroll enabled.
Fixes #3316 Enabled Fast Scroll disrupts normal scroll flow
What changes did you make and why?
Enabled fast scroll only when state is changed(user scrolls) so normal scroll flow isn't disrupted.
Also scrollbar is hidden so isn't visible for normal scroll this is done to prevent overlapping which wasn't looking nice
Tests performed (required)
Tested ProdDebug on OnePlus 5 with API level 28.

Codecov Report

Merging #3593 into master will decrease coverage by 0.00%.
The diff coverage is 0.00%.

@@             Coverage Diff             @@
##             master   #3593      +/-   ##
===========================================
- Coverage      6.97%   6.97%   -0.01%
  Complexity      291     291
===========================================
  Files           256     256
  Lines         11692   11693       +1
  Branches        954     955       +1
===========================================
  Hits            816     816
- Misses        10805   10806       +1
  Partials         71      71

Impacted Files
Coverage Δ
Complexity Δ

...w/commons/category/CategoryImagesListFragment.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)

Continue to review full report at Codecov.

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

repo: commons-app/apps-android-commons


text:
#3980 Hitting "My Rank" button from a list position below your rank on leaderboard takes you to the person ranked below you

Description (required)
Fixes #3980
What changes did you make and why?
I added logic to the LeaderboardFragment scrollToUserRank method that checks whether you are viewing the leaderboard positions above or below the user's rank. If you are viewing the leaderboard above the user's rank and select the My Rank button, the view will be scrolled down to user rank + 1 so that the user's rank is located directly above the button, as is specified in the Issue. If you are viewing the leaderboard below the user's rank and select the My Rank button, the view will be scrolled up to user rank which puts the rank at the top of the current list view.
Tests performed (required)
Tested BetaDebug on Google Pixel 2 with API level 29.
Screenshots (for UI changes only)
Leaderboard landing page (Notice user rank)
Current view is above the user's rank

After hitting the my rank button

Scroll to a position below the user's rank so that their rank is not visible

After hitting the my rank button

Codecov Report

Merging #3990 into master will decrease coverage by 0.01%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master    #3990      +/-   ##
============================================
- Coverage     10.52%   10.50%   -0.02%
  Complexity      466      466
============================================
  Files           335      335
  Lines         12639    12659      +20
  Branches        989      991       +2
============================================
  Hits           1330     1330
- Misses        11242    11262      +20
  Partials         67       67

Impacted Files
Coverage Δ
Complexity Δ

...mmons/profile/leaderboard/LeaderboardFragment.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)

.../java/fr/free/nrw/commons/di/NetworkingModule.java
0.00% <0.00%> (ø)
0.00% <0.00%> (ø%)

.../java/fr/free/nrw/commons/upload/UploadClient.java
0.00% <0.00%> (ø)
0.00% <0.00%> (ø%)

...a/fr/free/nrw/commons/OkHttpConnectionFactory.java
0.00% <0.00%> (ø)
0.00% <0.00%> (ø%)

...java/fr/free/nrw/commons/upload/UploadService.java
0.85% <0.00%> (+<0.01%)
1.00% <0.00%> (ø%)

Continue to review full report at Codecov.

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

source: gharchive/pull-request

license_type: permissive

license_source: github-api


text:
#13282: Fixes Android Studio Warnings under Kotlin section

Fixes #13282
Fixes the warnings in the Migration section under the Kotlin header.
(The list of warnings can be obtained via: Code -> Inspect Code.)

Tests performed
Tested ProdDebug on Pixel 4 Emulator with API level 30.
Verified that the app builds and runs successfully without introducing regressions.

BEFORE

AFTER

Strange, why didn't the workflow test didn't ran even though on force push it should have worked.

@neeldoshii For newer contributors, a core developer has to "approve" the CI run. I guess it is GitHub's way of reducing costs.

@neeldoshii @nicolas-raoul Thanks for responding I will wait for your feedback.

will work on that and make the necessary changes as soon as possible.

Let me know if any update regarding changes .

I check this function individually before pushing

I run this test before pushing

I run this test before pushing

Check the commit test case review : https://github.com/commons-app/apps-android-commons/actions/runs/12417015780/job/34687407494

I think I messed up , I'll make new PR addressing the issue .

I think I messed up , I'll make new PR addressing the issue .

its okay. you can even continue working on this PR. This will help in maintaining the logs of the PR.

@neeldoshii  Thanks for the suggestion! I see how keeping everything in one PR can help with maintaining logs, but I think it might be better to open a new PR for this. That way, it will be easier to keep things organized and ensure that each set of changes is focused on a specific issue. I’ll make a new PR and link it to this one for context. Let me know if you think that works.

authors: neeldoshii nicolas-raoul sonalyadav1


text:
Clarification needed: Individual and Team Assessments

I was wondering when we could expect to receive the links for the individual and team assessments. Would it be possible to get the links before LDOC? Thank you!

I will send them out today.

They were sent out today.

source: gharchive/issue


text:
Fix company auth scope

Updates the regex pattern used to test company auth scopes to match the new fine grained scope patterns.

I've run this and successfully come back from company authentication

authors: HarryBosworth PhilipGlover

repo: companieshouse/efs-submission-web

license: MIT


text:
Bug: Original Error Not Sent to Sentry in AwsStorageException

When throwing the following exception:
throw new AwsStorageException({
  safeMessage: 'Error downloading file from S3',
  originalError: error,
});

Only the text 'Error downloading file from S3' appears in Sentry. It seems that the originalError is not being sent to Sentry for better traceability.
Expected Behavior
Both the safeMessage and the originalError should be captured and logged in Sentry, ensuring that the original error information is available for debugging.
Actual Behavior
Currently, only the safeMessage ('Error downloading file from S3') is showing up in Sentry, with no trace of the originalError information.
Steps to Reproduce
Add global exception filter
import { ExceptionsFilter } from '@concepta/nestjs-exception';

// ...
const exceptionsFilter = app.get(HttpAdapterHost);
 app.useGlobalFilters(new ExceptionsFilter(exceptionsFilter));

Register LoggeModule and LoggerSentryModule
make sure to use proper Sentry configurations
// ...
 LoggerSentryModule.forRoot({}),
    LoggerModule.forRootAsync({
      inject: [LoggerSentryTransport],
      useFactory: (
        loggerSentryTransport: LoggerSentryTransport,
      ) => {
        return {
          transports: [loggerSentryTransport],
        };
      },
    }),

Create the custom AwsStorageException class:
import {
  RuntimeException,
  RuntimeExceptionContext,
  RuntimeExceptionOptions,
} from '@concepta/nestjs-exception';

export class AwsStorageException extends RuntimeException {
  context: RuntimeExceptionContext;

  constructor(options: RuntimeExceptionOptions) {
    super(options);
    this.errorCode = 'AWS_STORAGE_ERROR';
  }
}

Trigger the exception with the following code snippet:
throw new AwsStorageException({
  safeMessage: 'Error downloading file from S3',
  originalError: error,
});

Check the Sentry logs for the captured exception.
Observe that only the safeMessage is logged, with no trace of the originalError.
Additional Information
Version: 5.0.0-alpha.4

Please add this feature to the logger and sentry logger modules and validate agains the scenario reported.

Fixed by https://github.com/conceptadev/rockets/pull/293

authors: MrMaz tnramalho

repo: conceptadev/rockets


text:
Geometry: polygon rotation

Implement polygon rotation [#160604593]

when all points of a polygon (and no other points) are selected a rotation handle appears
dragging the rotation handle drags the points
the rotation handle disappears when selection conditions change

Also, replace use of lodash's cloneDeep() function for copying JXG.Coords objects with a custom copyCoords() function which performs better because it doesn't try to copy as much. (JXG.Coords contain a back-pointer to the board, which is time-consuming (and unnecessary) to copy.)

I considered the visible bounding rectangle approach and probably would have gone that route if we were talking about a rotation-specific mode, but I expect selecting polygons to be a common operation in many situations in which rotation is not the goal and adding a bunch of rotation-specific widgetry seemed like it would just add a lot of extraneous visual noise. Also, given the appearance of such a bounding rectangle one might expect that dragging the edges would allow one to resize the object, which clearly doesn't work. Conversely, if that feature were ever requested, that would be an argument for implementing the bounding rectangle approach.

Indeed, I was assuming that resizing would be coming up soon, in which case that can be revisited then.

authors: kswenson sfentress


text:
Draft: eslint try this on the CI

Fixes #524
Problem:
The eslint react hooks were ancient, and they had a bug: if you would have a type, such as T in a useEffect or useCallback hook, eslint would complain that you forgot to list T in the dependency list.
Fix:
Bump eslint plugins everywhere. It turns out the current version of eslint-plugin-react-hooks bombs out if you have
React.useEffect() at the top level of a file. Which broke one of our tests, and also it means that while trying to reproduce it, I realized that the worker just dies if eslint throws an error. I put linting in a try-catch and return a ESLint runtime error lint error, which the canvas-error-overlay displays like so:

Commit Details:

Bump all the eslints plugins, (this affects our devtools but also the eslint bundled for the users as well)
Fix all the places I could find that had an eslint-disable rule for hook dependencies
Add a try-catch around linting inside the editor's own linter worker
Updated the test called "React.useEffect at the root fails usefully" which was snapshotting garbage (the snapshot claims we are not showing an error message).

Note:
We are on the last vesion of babel-eslint that can still run in the browser, if we are going to face a situation where we need to bump babel-eslint, we are going to have to fork them and create a babel-eslint4b (which would be a version of babel-eslint that depends on eslint4b instead of eslint)

this is ready for review

ahhh so many merge conflicts!

repo: concrete-utopia/utopia


text:
Feature request: View & Manage Areas/Global Areas in Dashboard

Can we have somewhere in the dashboard area a lookup for all Areas defined in a C5 site (Global Areas and normal editable Areas) and a way to edit and delete them from that place?
I had a recent problem where I had created two editable Areas in my template called "Section Banner" and "Breadcrumbs" using new Area
.
I later decided to make these Global Areas, so I simply changed my code to use new GlobalArea with the same names.
However, when I tried to add blocks to these new Global Areas while in a Page they would disappear after saving the page. The added blocks also did not appear in the Global Stacks area.
I ended up changing the name of the "Breadcrumbs" Global Area to "Bread crumbs" (two words) and now it works as expected -- it saves the changes and appears in the Global Stacks area.
So there was obviously a name conflict but no way of knowing. There was no error message - it just behaved mysteriously (my content disappearing). I reported it as a bug here: https://www.concrete5.org/developers/bugs/5-7-3-1/cant-create-global-area-with-same-name-as-previous-editable-regi/
But I am posting this issue as a feature request.

I guess the first feature would be a helpful error message saying "Cannot create Global Area 'Breadcrumbs' - Area name already in use"
The second is a page in the Dashboard that lists all the Areas defined in a C5 site so that we can rename them or delete Areas no longer in use.

Thanks!

I too have found that you can not change an area to global once set as non-global.
Is this a bug as this is not how it worked previously. In older version (5.6 etc) you could always change an area to be global without issue...
This can be a big headache when developing a site and then needing to change the nature of an area.

I think something like this belongs more in an add-on than in the core.

authors: 4ndygriffiths aembler malkau

license: mit

license_source: bigquery


text:
Automatic User Expiration

Add automatic user expiration: add dashboard page, add ability to custom inactive user messaging; add job that deactivates users based on login

I guess that the tool we use to extract translatable strings needs to be updated in order to extract translatable strings from configuration files, both from running instances (so that those strings will be translatablebin the concrete5 dashboard) and from non installed instances (so that those strings can be translated via translate.concrete5.org and added to the core translations).

I guess that the tool we use to extract translatable strings needs to be updated in order to extract translatable strings from configuration files

https://github.com/mlocati/concrete5-translation-library/commit/2ab9737ced878d6fab274e2c2cf7080c8f41189a

@aembler We need to update the translation library. BTW I've used the same approach of this PR (that is, adding translatable strings to configuration files) in #6807 too.
So, if you (or @KorvinSzanto) could review #6807 you'd simplify my life a bit :wink:

authors: aembler mlocati


text:
Update CircleCI token

Additional comment:
@conda-forge-admin, please update circle

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I updated the circle-ci deploy key and followed the project.

authors: brandonwillard conda-forge-linter

repo: conda-forge/aesara-feedstock


text:
Split packages

This should be backward compatible with previous builds.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

authors: conda-forge-linter isuruf

repo: conda-forge/clangdev-feedstock


text:
@conda-forge-admin please rerender

Additional comment:
No response

solved by #7

repo: conda-forge/colour-feedstock


text:
conda-docker 0.0.3

Merge only after success.
This pull request was auto-generated by rever

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

noarch: python recipes are recommended to have a lower bound on the python version. This recommendation will become a requirement in the future.

authors: conda-forge-linter scopatz

repo: conda-forge/conda-docker-feedstock


text:
Add CUDA 11.3 / 11.4

Checklist

[X] Used a personal fork of the feedstock to propose changes
[X] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[X] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[X] Ensured the license file is being packaged.

See https://github.com/conda-forge/cudatoolkit-feedstock/issues/58 for more info.
Note that I added myself as a maintainer as part of this PR!

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

I'll try to make the core meeting this week, but it might not happen as I'm chairing a track at SciPy. Someone else may be able to chair the same day as the core meeting, but that's a little unclear atm.

Following up this. Will be able to make the core meeting tomorrow. Look forward to discussing it there.

Can we merge this? I want to try the new Nvidia packages for 11.3, but I need the Docker images, which need the current cudatoolkit packages. We don't need to add the migrator yet (xref https://github.com/conda-forge/conda-forge-pinning-feedstock/pull/1708).

Although I guess we can merge 11.3 and 11.4 Docker images without the cached cudatoolkit?

Thanks for your work on this everyone!
I'm curious to know what the current status of this PR is, anyone got time to give an update?

Thanks for clarifying Keith 🙂
So what are you proposing we change here? Currently it allows any __cuda version that matches the cudatoolkit version or newer
Also in PR ( https://github.com/conda-forge/nvcc-feedstock/pull/71 ), we are loosening the cudatoolkit version that is required by packages to just match the nvcc version used to build or newer up to, but excluding the latest major version
Since we are only building with CUDA 11.2 as the latest CUDA 11.x, this should effectively make all packages built with CUDA 11.2 support that version or newer (excluding the next major version)
Are there cases we still miss with this?

I thought the plan was to build with the latest nvcc and then allow running on 11.2+ instead of building on 11.2?

Consolidating conversation in issue ( https://github.com/conda-forge/nvcc-feedstock/pull/71 )

@kkraus14 @isuruf, could you please take another look at this one?

Requested changes have been added, with the exception of the __cuda constrains.

Thanks Jaime! 😄
Would be great if folks take another look at this 🙂

Thanks @jaimergp and everyone!

Agreed. Thanks everyone! 😄

authors: conda-forge-linter consideRatio jaimergp jakirkham kkraus14 leofang

repo: conda-forge/cudatoolkit-feedstock


text:
Fix Windows build

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

The recipe license should not include the word "License".

For recipe:

License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

The recipe license should not include the word "License".

For recipe:

License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

Keep CUDA 11 fix to the next PR. Merging...

Keep CUDA 11 fix to the next PR. Merging...

authors: conda-forge-linter leofang

repo: conda-forge/cutensor-feedstock


text:
update to datavzrd 2.9.0 and update changed homepage

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

authors: conda-forge-linter johanneskoester

repo: conda-forge/datavzrd-feedstock


text:
Update yaml file to v2.3.0

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

close this PR as the builds failed due to the version incompatibility of required packages during the pip check. Will change the version requirements.

repo: conda-forge/dgpsi-feedstock


text:
Installed NODE_JS path in .emscripten causing missing node.exe error on windows

Solution to issue cannot be found in the documentation.

[X] I checked the documentation.

Issue
Hey,
when attempting to compile using emscripten on windows, it seems like there's an issue with the node executable path. I get this error:
(ada-cpp:wasm) C:\Work\code\adacpp>emcc
emcc: warning: cannot check node version: [WinError 2] The system cannot find the file specified [-Wversion-check]
emcc: warning: LLVM version for clang executable "C:/Work/code/adacpp/.pixi/envs/wasm/Library/bin\clang.exe" appears incorrect (seeing "18.1", expected "19") [-Wversion-check]
shared:INFO: (Emscripten: Running sanity checks)
emcc: error: the configured node executable (['D:\\bld\\emscripten_1725438987067\\_h_env\\node.EXE']) does not seem to work, check the paths in C:\Work\code\adacpp\.pixi\envs\wasm\Library\lib\emscripten-3.1.58\.emscripten ([WinError 2] The system cannot find the file specified)

When inspecting the .emscripten file I see this:
# Location of the node binary to use for running the JS parts of the compiler.
# This engine must exist, or nothing can be compiled.
NODE_JS = 'D:\\bld\\emscripten_1725438987067\\_h_env\\node.EXE' # executable

Where I am guessing NODE_JS is the path used by the azure devops runners?
By simply updating the NODE_JS path locally emcc and em++ seems to work as expected
Installed packages
(ada-cpp:wasm) C:\Work\code\adacpp>mamba list
# packages in environment at C:\Work\code\adacpp\.pixi\envs\wasm:
#
# Name                    Version                   Build  Channel
binaryen                  118                  he0c23c2_1    conda-forge
bzip2                     1.0.8                h2466b09_7    conda-forge
ca-certificates           2024.8.30            h56e8100_0    conda-forge
cairo                     1.18.0               h32b962e_3    conda-forge
cgal-cpp                  5.6.1                hb7ee40c_1    conda-forge
clang                     18.1.8          default_hec978fc_4    conda-forge
clang-18                  18.1.8          default_hec7ea82_4    conda-forge
clangxx                   18.1.8          default_hf03c572_4    conda-forge
cmake                     3.30.3               h400e5d1_0    conda-forge
eigen                     3.4.0                h91493d7_0    conda-forge
emscripten                3.1.58               hc790b64_3    conda-forge
expat                     2.6.3                he0c23c2_0    conda-forge
fltk                      1.3.9                h27fc217_1    conda-forge
font-ttf-dejavu-sans-mono 2.37                 hab24e00_0    conda-forge
font-ttf-inconsolata      3.000                h77eed37_0    conda-forge
font-ttf-source-code-pro  2.038                h77eed37_0    conda-forge
font-ttf-ubuntu           0.83                 h77eed37_2    conda-forge
fontconfig                2.14.2               hbde0cde_0    conda-forge
fonts-conda-ecosystem     1                             0    conda-forge
fonts-conda-forge         1                             0    conda-forge
freeimage                 3.18.0              h2b56e36_20    conda-forge
freetype                  2.12.1               hdaf720e_2    conda-forge
gmsh                      4.12.2               hcc95203_0    conda-forge
hdf5                      1.14.3          nompi_h2b43c12_105    conda-forge
icu                       75.1                 he0c23c2_0    conda-forge
ifcopenshell              0.8.0           py312h2a1a271_0    conda-forge
imath                     3.1.11               h12be248_0    conda-forge
intel-openmp              2024.2.1          h57928b3_1083    conda-forge
jxrlib                    1.1                  hcfcfb64_3    conda-forge
krb5                      1.21.3               hdf4eb48_0    conda-forge
lcms2                     2.16                 h67d730c_0    conda-forge
lerc                      4.0.0                h63175ca_0    conda-forge
libaec                    1.1.3                h63175ca_0    conda-forge
libblas                   3.9.0              23_win64_mkl    conda-forge
libboost                  1.84.0               h444863b_6    conda-forge
libboost-devel            1.84.0               h91493d7_6    conda-forge
libboost-headers          1.84.0               h57928b3_6    conda-forge
libcblas                  3.9.0              23_win64_mkl    conda-forge
libcurl                   8.9.1                h18fefc2_0    conda-forge
libdeflate                1.21                 h2466b09_0    conda-forge
libexpat                  2.6.3                he0c23c2_0    conda-forge
libffi                    3.4.2                h8ffe710_5    conda-forge
libglib                   2.80.3               h7025463_2    conda-forge
libhwloc                  2.11.1          default_h8125262_1000    conda-forge
libiconv                  1.17                 hcfcfb64_2    conda-forge
libintl                   0.22.5               h5728263_3    conda-forge
libjpeg-turbo             3.0.0                hcfcfb64_1    conda-forge
liblapack                 3.9.0              23_win64_mkl    conda-forge
libllvm18                 18.1.8               h2a44499_2    conda-forge
libpng                    1.6.43               h19919ed_0    conda-forge
libraw                    0.21.1               h5557f11_2    conda-forge
libsqlite                 3.46.1               h2466b09_0    conda-forge
libssh2                   1.11.0               h7dfc565_0    conda-forge
libtiff                   4.6.0                hb151862_4    conda-forge
libuv                     1.48.0               hcfcfb64_0    conda-forge
libwebp-base              1.4.0                hcfcfb64_0    conda-forge
libxcb                    1.16                 h013a479_1    conda-forge
libxml2                   2.12.7               h0f24e4e_4    conda-forge
libzlib                   1.3.1                h2466b09_1    conda-forge
lld                       18.1.8               hd91d51b_0    conda-forge
llvm-tools                18.1.8               h2a44499_2    conda-forge
m2w64-gcc-libgfortran     5.3.0                         6    conda-forge
m2w64-gcc-libs            5.3.0                         7    conda-forge
m2w64-gcc-libs-core       5.3.0                         7    conda-forge
m2w64-gmp                 6.1.0                         2    conda-forge
m2w64-libwinpthread-git   5.0.0.4634.697f757               2    conda-forge
mkl                       2024.1.0           h66d3029_694    conda-forge
mpfr                      4.2.1                h64bf75a_1    conda-forge
mpir                      3.0.0             he025d50_1002    conda-forge
msys2-conda-epoch         20160418                      1    conda-forge
nodejs                    22.8.0               h57928b3_0    conda-forge
numpy                     2.1.1           py312h49bc9c5_0    conda-forge
occt                      7.7.2           novtk_hdfb195f_101    conda-forge
openexr                   3.2.2                h72640d8_1    conda-forge
openjpeg                  2.5.2                h3d672ee_0    conda-forge
openssl                   3.3.2                h2466b09_0    conda-forge
pcre2                     10.44                h3d7b363_2    conda-forge
pixman                    0.43.4               h63175ca_0    conda-forge
pthread-stubs             0.4               hcd874cb_1001    conda-forge
pthreads-win32            2.9.1                hfa6e2cd_3    conda-forge
python                    3.12.5          h889d299_0_cpython    conda-forge
python_abi                3.12                    5_cp312    conda-forge
rapidjson                 1.1.0.post20240409      he0c23c2_1    conda-forge
tbb                       2021.13.0            hc790b64_0    conda-forge
tinygltf                  2.8.21               hd8ed1ab_0    conda-forge
tk                        8.6.13               h5226925_1    conda-forge
tzdata                    2024a                h8827d51_1    conda-forge
ucrt                      10.0.22621.0         h57928b3_0    conda-forge
vc                        14.3                h8a93ad2_20    conda-forge
vc14_runtime              14.40.33810         hcc2c482_20    conda-forge
vs2015_runtime            14.40.33810         h3bf8584_20    conda-forge
xorg-fixesproto           5.0               hcd874cb_1002    conda-forge
xorg-kbproto              1.0.7             hcd874cb_1002    conda-forge
xorg-libice               1.1.1                hcd874cb_0    conda-forge
xorg-libsm                1.2.4                hcd874cb_0    conda-forge
xorg-libx11               1.8.9                h0076a8d_1    conda-forge
xorg-libxau               1.0.11               hcd874cb_0    conda-forge
xorg-libxdmcp             1.1.3                hcd874cb_0    conda-forge
xorg-libxext              1.3.4                hcd874cb_2    conda-forge
xorg-libxfixes            5.0.3             hcd874cb_1004    conda-forge
xorg-libxrender           0.9.11               hcd874cb_0    conda-forge
xorg-renderproto          0.11.1            hcd874cb_1002    conda-forge
xorg-xextproto            7.3.0             hcd874cb_1003    conda-forge
xorg-xproto               7.0.31            hcd874cb_1007    conda-forge
xz                        5.2.6                h8d14728_0    conda-forge
zlib                      1.3.1                h2466b09_1    conda-forge
zstd                      1.5.6                h0ea2cb4_0    conda-forge

Environment info
(base) C:\Work\code\adacpp>conda info

     active environment : C:\Work\code\adacpp\.pixi\envs\wasm
    active env location : C:\Work\code\adacpp\.pixi\envs\wasm
            shell level : 1
       user config file : C:\Users\Kristoffer\.condarc
 populated config files : C:\Work\Miniforge3\.condarc
                          C:\Users\Kristoffer\.condarc
          conda version : 24.5.0
    conda-build version : not installed
         python version : 3.10.14.final.0
                 solver : libmamba (default)
       virtual packages : __archspec=1=skylake
                          __conda=24.5.0=0
                          __cuda=12.6=0
                          __win=0=0
       base environment : C:\Work\Miniforge3  (writable)
      conda av data dir : C:\Work\Miniforge3\etc\conda
  conda av metadata url : None
           channel URLs : https://conda.anaconda.org/conda-forge/win-64
                          https://conda.anaconda.org/conda-forge/noarch
          package cache : C:\Work\Miniforge3\pkgs
                          C:\Users\Kristoffer\.conda\pkgs
                          C:\Users\Kristoffer\AppData\Local\conda\conda\pkgs
       envs directories : C:\Work\Miniforge3\envs
                          C:\Users\Kristoffer\.conda\envs
                          C:\Users\Kristoffer\AppData\Local\conda\conda\envs
               platform : win-64
             user-agent : conda/24.5.0 requests/2.31.0 CPython/3.10.14 Windows/10 Windows/10.0.22631 solver/libmamba conda-libmamba-solver/24.1.0 libmambapy/1.5.8
          administrator : False
             netrc file : None
           offline mode : False

There may be several issues, but you definitely need clang 19 (not sure if >= or exactly), which is currently only available when using -c conda-forge/label/llvm_rc.

authors: Krande h-vetinari

repo: conda-forge/emscripten-feedstock


text:
v24.0.0

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

@conda-forge-admin please rerender

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

@CJ-Wright Requesting review and merge. Thanks!

authors: conda-forge-admin thewchan

repo: conda-forge/face-feedstock


text:
revving version

Checklist

[ ] Used a fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

authors: conda-forge-linter mhearne-usgs

repo: conda-forge/gmprocess-feedstock


text:
gwpy v2.1.3

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

authors: conda-forge-linter duncanmmacleod

repo: conda-forge/gwpy-feedstock


text:
Bump version to v1.23.4

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

I removed th patch 153 since https://github.com/robotology/icub-models/pull/153 is now contained in the release 1.23.4

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

authors: GiulioRomualdi conda-forge-linter

repo: conda-forge/icub-models-feedstock


text:
Add missing dependency

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

@conda-forge-admin, please rerender

authors: conda-forge-linter emthompson-usgs

repo: conda-forge/impactutils-feedstock


text:
updated 3.17.2

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Sorry for noise, didnt know it would auto ping you.

@conda-forge-admin, please rerender


text:
Stop supporting v5

It just reached end of life, see https://github.com/ignition-tooling/release-tools/issues/655 .

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

authors: conda-forge-linter traversaro

repo: conda-forge/libignition-gui-feedstock


text:
Add cross-platform builds

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

repo: conda-forge/liblzf-feedstock


text:
Build llvmdev 9.x for ppc64le

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

Jinja2 variable references are suggested to take a {{<one space><variable name><one space>}} form. See lines [109].

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

Failed to even lint the recipe, probably because of a conda-smithy bug :cry:. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint . from the recipe directory.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

Jinja2 variable references are suggested to take a {{<one space><variable name><one space>}} form. See lines [111].

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

:tada:

authors: SylvainCorlay conda-forge-linter

repo: conda-forge/llvmdev-feedstock


text:
Update to 1.1.0

Checklist

[X] Used a personal fork of the feedstock to propose changes
[] Bumped the build number (if the version is unchanged)
[X] Reset the build number to 0 (if the version changed)
[X] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

@brianv0 looks like this is ready to merge


text:
Tkp/clean

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

authors: conda-forge-linter timkpaine

repo: conda-forge/perspective-feedstock


text:
BLD: depend on epics-base for shared libraries

close #13

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

I suspect this is going to fail on windows

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

Failed to even lint the recipe, probably because of a conda-smithy bug :cry:. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint . from the recipe directory.

Something is going wrong with the templating
build:
  number: 2
  script: |
      export NOLIBCA=1
      echo "Using LIBCA from $PYEPICS_LIBCA"
      rm -rf epics/clibs
      " -m pip install . --no-deps -vv"

What's the reason we have https://github.com/conda-forge/pyepics-feedstock/blob/master/pycache/build-locally.cpython-36.pyc in the repo?

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin please rerender

I think it can be closed as #17 takes care of the issue.

authors: conda-forge-linter mariusvniekerk mrakitin tacaswell

repo: conda-forge/pyepics-feedstock


text:
Add MPI variant

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Hi! This is the friendly automated conda-forge-webservice.
I tried to re-render for you, but it looks like there was nothing to do.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

authors: ChristopherHogan conda-forge-linter

repo: conda-forge/pymeep-feedstock


text:
MNT: rerender

Hi! This is the friendly automated conda-forge-webservice.
I've started rerendering the recipe as instructed in #3.
If I find any needed changes to the recipe, I'll push them to this PR shortly. Thank you for waiting!
Here's a checklist to do before merging.

[ ] Bump the build number if needed

Fixes #3

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe/meta.yaml:

ℹ No valid build backend found for Python recipe for package quickxorhash using pip. Python recipes using pip need to explicitly specify a build backend in the host section. If your recipe has built with only pip in the host section in the past, you likely should add setuptools to the host section of your recipe.
ℹ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.

For the host section of the recipe, you should usually use python {{ python_min }} for the python entry.
For the run section of the recipe, you should usually use python >={{ python_min }} for the python entry.
For the test.requires section of the recipe, you should usually use python {{ python_min }} for the python entry.
If the package requires a newer Python version than the currently supported minimum version on conda-forge, you can override the python_min variable by adding a Jinja2 set statement at the top of your recipe (or using an equivalent context variable for v1 recipes).

ℹ PyPI default URL is now pypi.org, and not pypi.io. You may want to update the default source url.

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12027863507. Examine the logs at this URL for more detail.

repo: conda-forge/quickxorhash-feedstock


text:
MNT: rerender

Hi! This is the friendly automated conda-forge-webservice.
I've rerendered the recipe as instructed in #2.
Here's a checklist to do before merging.

[ ] Bump the build number if needed.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


text:
Enable win64 build; reflect license change

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

Using toolchain directly in this manner is deprecated.  Consider using the compilers outlined here.

authors: cbrueffer conda-forge-linter


text:
Update hunspell to 3.0

Checklist

[ ] Used a fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

Using toolchain directly in this manner is deprecated.  Consider using the compilers outlined here.

@conda-forge-admin, please rerender

authors: conda-forge-linter philip-khor

repo: conda-forge/r-hunspell-feedstock


text:
Update to 1.8.4

Checklist

[x] Used a fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

noarch build. wrongly appveyor build can be ignored.

authors: conda-forge-linter dbast


text:
Rstudio shared library error but R loads rgdal fine. So r-rstudio + rstudioserver fails

gdal loading error.
FIRST, IMPORTANT: Everything goes fine in R , not in Rstudio. Loading rgdal in R , works smoothly:
unable to load shared object '/opt/conda/lib/R/library/rgdal/libs/rgdal.so':
/lib/x86_64-linux-gnu/libz.so.1: version `ZLIB_1.2.9'

library(rgdal)
Loading required package: sp
rgdal: version: 1.2-8, (SVN revision 663)
Geospatial Data Abstraction Library extensions to R successfully loaded
Loaded GDAL runtime: GDAL 2.2.3, released 2017/11/20
Path to GDAL shared files: /opt/conda/share/gdal
Loaded PROJ.4 runtime: Rel. 4.9.3, 15 August 2016, [PJ_VERSION: 493]
Path to PROJ.4 shared files: (autodetected)
Linking to sp version: 1.2-4
sessionInfo()
R version 3.4.1 (2017-06-30)
Platform: x86_64-pc-linux-gnu (64-bit)
Running under: Ubuntu 16.04.3 LTS

Matrix products: default
BLAS: /opt/conda/lib/R/lib/libRblas.so
LAPACK: /opt/conda/lib/R/lib/libRlapack.so
locale:
[1] LC_CTYPE=en_US.UTF-8       LC_NUMERIC=C
[3] LC_TIME=en_US.UTF-8        LC_COLLATE=en_US.UTF-8
[5] LC_MONETARY=en_US.UTF-8    LC_MESSAGES=en_US.UTF-8
[7] LC_PAPER=en_US.UTF-8       LC_NAME=C
[9] LC_ADDRESS=C               LC_TELEPHONE=C
[11] LC_MEASUREMENT=en_US.UTF-8 LC_IDENTIFICATION=C
attached base packages:
[1] stats     graphics  grDevices utils     datasets  methods   base
other attached packages:
[1] rgdal_1.2-8 sp_1.2-4
loaded via a namespace (and not attached):
[1] compiler_3.4.1  grid_3.4.1      lattice_0.20-34

Sys.getenv()
_                       /opt/conda/bin/R
COLUMNS                 184
CONDA_DIR               /opt/conda
DEBIAN_FRONTEND         noninteractive
EDITOR                  vi
HOME                    /home/jovyan
HOSTNAME                4512b594d7af
LANG                    en_US.UTF-8
LANGUAGE                en_US.UTF-8
LC_ALL                  en_US.UTF-8
LINES                   55
LN_S                    ln -s
LS_COLORS
...
MAKE                    make
MINICONDA_VERSION       4.3.30
NB_GID                  100
NB_UID                  1000
NB_USER                 jovyan
PAGER                   /usr/bin/less
PANDOC_TEMPLATES_VERSION
1.18
PASSWORD
PATH                    /usr/lib/rstudio-server/bin/:/opt/conda/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
PWD                     /
R_ARCH
R_BROWSER
R_BZIPCMD               /opt/conda/bin/bzip2
R_DOC_DIR               /opt/conda/lib/R/doc
R_GZIPCMD               /usr/bin/gzip
R_HOME                  /opt/conda/lib/R
R_INCLUDE_DIR           /opt/conda/lib/R/include
R_LIBS_SITE
R_LIBS_USER             ~/R/x86_64-pc-linux-gnu-library/3.4
R_PAPERSIZE             a4
R_PDFVIEWER
R_PLATFORM              x86_64-pc-linux-gnu
R_PRINTCMD
R_RD4PDF                times,inconsolata,hyper
R_SESSION_TMPDIR        /tmp/RtmpvERdUC
R_SHARE_DIR             /opt/conda/lib/R/share
R_SYSTEM_ABI            linux,gcc,gxx,gfortran,?
R_TEXI2DVICMD           texi2dvi
R_UNZIPCMD
R_ZIPCMD
SED                     /bin/sed
SHELL                   /bin/bash
SHLVL                   1
TAR                     /bin/gtar
TERM                    xterm
USER                    vmasip

Not like rstudio:
library(rgdal)
Loading required package: sp
Error: package or namespace load failed for ‘rgdal’ in dyn.load(file, DLLpath = DLLpath, ...):
unable to load shared object '/opt/conda/lib/R/library/rgdal/libs/rgdal.so':
/lib/x86_64-linux-gnu/libz.so.1: version `ZLIB_1.2.9' not found (required by /opt/conda/lib/R/library/rgdal/libs/../../../.././libpng16.so.16)

sessionInfo()
R version 3.4.1 (2017-06-30)
Platform: x86_64-pc-linux-gnu (64-bit)
Running under: Ubuntu 16.04.3 LTS

Matrix products: default
BLAS: /opt/conda/lib/R/lib/libRblas.so
LAPACK: /opt/conda/lib/R/lib/libRlapack.so
locale:
[1] LC_CTYPE=es_ES.UTF-8       LC_NUMERIC=C               LC_TIME=es_ES.UTF-8        LC_COLLATE=es_ES.UTF-8
[5] LC_MONETARY=es_ES.UTF-8    LC_MESSAGES=es_ES.UTF-8    LC_PAPER=es_ES.UTF-8       LC_NAME=C
[9] LC_ADDRESS=C               LC_TELEPHONE=C             LC_MEASUREMENT=es_ES.UTF-8 LC_IDENTIFICATION=C
attached base packages:
[1] stats     graphics  grDevices utils     datasets  methods   base
other attached packages:
[1] sp_1.2-4
loaded via a namespace (and not attached):
[1] compiler_3.4.1  tools_3.4.1     grid_3.4.1      lattice_0.20-34

Sys.getenv()
CLICOLOR_FORCE                      1
DISPLAY                             :0
EDITOR                              vi
GIT_ASKPASS                         rpostback-askpass
HOME                                /home/vmasip
LANG                                es_ES.UTF-8
LD_LIBRARY_PATH                     /opt/conda/lib/R/lib:
LN_S                                ln -s
LOGNAME                             vmasip
MAKE                                make
PAGER                               /usr/bin/less
PATH                                /usr/bin:/usr/sbin:/bin:/sbin
R_BROWSER
R_BZIPCMD                           /opt/conda/bin/bzip2
R_DOC_DIR                           /opt/conda/lib/R/doc
R_GZIPCMD                           /usr/bin/gzip
R_HOME                              /opt/conda/lib/R
R_INCLUDE_DIR                       /opt/conda/lib/R/include
R_LIBS_SITE
R_LIBS_USER                         ~/R/x86_64-pc-linux-gnu-library/3.4
R_PAPERSIZE                         a4
R_PDFVIEWER
R_PLATFORM                          x86_64-pc-linux-gnu
R_PRINTCMD
R_RD4PDF                            times,inconsolata,hyper
R_SESSION_TMPDIR                    /tmp/RtmpRHVfDu
R_SHARE_DIR                         /opt/conda/lib/R/share
R_SYSTEM_ABI                        linux,gcc,gxx,gfortran,?
R_TEXI2DVICMD                       texi2dvi
R_UNZIPCMD
R_ZIPCMD
RMARKDOWN_MATHJAX_PATH              /usr/lib/rstudio-server/resources/mathjax-26
RS_RPOSTBACK_PATH                   /usr/lib/rstudio-server/bin/rpostback
RSTUDIO                             1
RSTUDIO_CONSOLE_COLOR               256
RSTUDIO_CONSOLE_WIDTH               121
RSTUDIO_HTTP_REFERER                http://localhost:8787/
RSTUDIO_PANDOC                      /usr/lib/rstudio-server/bin/pandoc
RSTUDIO_SESSION_STREAM              vmasip-d
RSTUDIO_USER_IDENTITY               vmasip
RSTUDIO_WINUTILS                    bin/winutils
SED                                 /bin/sed
SSH_ASKPASS                         rpostback-askpass
TAR                                 /bin/gtar
TERM                                xterm-256color
USER                                vmasip

This is  my conda list:
asn1crypto                0.22.0                   py36_0    conda-forge
blas                      1.1                    openblas    conda-forge
boost                     1.65.1                   py36_0    conda-forge
boost-cpp                 1.65.1                        1    conda-forge
bzip2                     1.0.6                         1    conda-forge
ca-certificates           2017.11.5                     0    conda-forge
cairo                     1.14.10                       0    conda-forge
certifi                   2017.11.5                py36_0    conda-forge
cffi                      1.11.2                   py36_0    conda-forge
chardet                   3.0.4                    py36_0    conda-forge
conda                     4.3.29                   py36_0    conda-forge
conda-env                 2.6.0                         0    conda-forge
cryptography              2.1.4                    py36_0    conda-forge
curl                      7.55.1                        0    conda-forge
expat                     2.2.5                         0    conda-forge
fontconfig                2.12.6                        0    conda-forge
freetype                  2.8.1                         0    conda-forge
freexl                    1.0.4                         0    conda-forge
geos                      3.6.2                         1    conda-forge
geotiff                   1.4.2                         1    conda-forge
gettext                   0.19.7                        1    conda-forge
giflib                    5.1.4                         0    conda-forge
glib                      2.55.0                        0    conda-forge
graphite2                 1.3.10                        0    conda-forge
gsl                       2.2.1           blas_openblas_4  [blas_openblas]  conda-forge
harfbuzz                  1.7.1                         0    conda-forge
hdf4                      4.2.13                        0    conda-forge
hdf5                      1.10.1                        1    conda-forge
icu                       58.2                          0    conda-forge
idna                      2.6                      py36_1    conda-forge
jpeg                      9b                            2    conda-forge
json-c                    0.12.1                        0    conda-forge
kealib                    1.4.7                         4    conda-forge
krb5                      1.14.2                        0    conda-forge
libdap4                   3.18.3                        2    conda-forge
libedit                   3.1.20170329                  0    conda-forge
libffi                    3.2.1                         3    conda-forge
libgcc                    7.2.0                h69d50b8_2    defaults
libgcc-ng                 7.2.0                h7cc24e2_2    defaults
libgdal                   2.2.3                         2    conda-forge
libgfortran               3.0.0                         1    defaults
libiconv                  1.15                          0    conda-forge
libkml                    1.3.0                         5    conda-forge
libnetcdf                 4.4.1.1                      10    conda-forge
libpng                    1.6.34                        0    conda-forge
libpq                     9.6.3                         0    conda-forge
libspatialite             4.3.0a                       19    conda-forge
libssh2                   1.8.0                         2    conda-forge
libstdcxx-ng              7.2.0                h7a57d05_2    defaults
libtiff                   4.0.9                         0    conda-forge
libxml2                   2.9.7                         0    conda-forge
ncurses                   5.9                          10    conda-forge
numpy                     1.14.0          py36_blas_openblas_200  [blas_openblas]  conda-forge
openblas                  0.2.20                        6    conda-forge
openjpeg                  2.3.0                         2    conda-forge
openssl                   1.0.2n                        0    conda-forge
pango                     1.40.14                       0    conda-forge
pcre                      8.39                          0    conda-forge
pip                       9.0.1                    py36_1    conda-forge
pixman                    0.34.0                        1    conda-forge
poppler                   0.61.1                        3    conda-forge
poppler-data              0.4.8                         0    conda-forge
proj4                     4.9.3                         5    conda-forge
pycosat                   0.6.3                    py36_0    conda-forge
pycparser                 2.18                     py36_0    conda-forge
pyopenssl                 17.4.0                   py36_0    conda-forge
pysocks                   1.6.7                    py36_0    conda-forge
python                    3.6.4                         0    conda-forge
r-assertthat              0.1                    r3.4.1_0    conda-forge
r-base                    3.4.1                         3    conda-forge
r-base64enc               0.1_3                  r3.4.1_0    conda-forge
r-bh                      1.65.0_1               r3.4.1_0    conda-forge
r-bindr                   0.1                    r3.4.1_0    conda-forge
r-bindrcpp                0.2                    r3.4.1_0    conda-forge
r-bit                     1.1_12                 r3.4.1_0    conda-forge
r-bit64                   0.9_5                  r3.4.1_0    conda-forge
r-blob                    1.1.0                  r3.4.1_0    conda-forge
r-codetools               0.2_15                 r3.4.1_0    conda-forge
r-colorspace              1.3_2                  r3.4.1_0    conda-forge
r-crosstalk               1.0.0                  r3.4.1_0    conda-forge
r-curl                    2.4                    r3.4.1_0    conda-forge
r-data.table              1.10.4                 r3.4.1_0    conda-forge
r-dbi                     0.6_1                  r3.4.1_0    conda-forge
r-devtools                1.13.2                 r3.4.1_0    conda-forge
r-dichromat               2.0_0                  r3.4.1_0    conda-forge
r-digest                  0.6.12                 r3.4.1_0    conda-forge
r-domc                    1.3.4                  r3.4.1_0    conda-forge
r-dplyr                   0.7.4                  r3.4.1_0    conda-forge
r-foreach                 1.4.3                  r3.4.1_0    conda-forge
r-ggplot2                 2.2.1                  r3.4.1_0    conda-forge
r-git2r                   0.19.0                 r3.4.1_0    conda-forge
r-glue                    1.1.1                  r3.4.1_0    conda-forge
r-gridextra               2.3                    r3.4.1_0    conda-forge
r-gtable                  0.2.0                  r3.4.1_0    conda-forge
r-hms                     0.3                    r3.4.1_0    conda-forge
r-htmltools               0.3.6                  r3.4.1_0    conda-forge
r-htmlwidgets             0.9                    r3.4.1_0    conda-forge
r-httpuv                  1.3.3                  r3.4.1_0    conda-forge
r-httr                    1.2.1                  r3.4.1_0    conda-forge
r-iterators               1.0.8                  r3.4.1_0    conda-forge
r-jsonlite                1.4                    r3.4.1_0    conda-forge
r-labeling                0.3                    r3.4.1_0    conda-forge
r-lattice                 0.20_34                r3.4.1_0    conda-forge
r-lazyeval                0.2.0                  r3.4.1_0    conda-forge
r-leaflet                 1.1.0                  r3.4.1_0    conda-forge
r-magrittr                1.5                    r3.4.1_0    conda-forge
r-markdown                0.8                    r3.4.1_0    conda-forge
r-mass                    7.3_45                 r3.4.1_0    conda-forge
r-memoise                 1.1.0                  r3.4.1_0    conda-forge
r-mime                    0.5                    r3.4.1_0    conda-forge
r-munsell                 0.4.3                  r3.4.1_0    conda-forge
r-openssl                 0.9.7                  r3.4.1_0    conda-forge
r-pkgconfig               2.0.1                  r3.4.1_0    conda-forge
r-plogr                   0.1_1                  r3.4.1_0    conda-forge
r-plyr                    1.8.4                  r3.4.1_0    conda-forge
r-png                     0.1_7                  r3.4.1_0    conda-forge
r-r6                      2.2.0                  r3.4.1_0    conda-forge
r-raster                  2.5_8                  r3.4.1_0    conda-forge
r-rcolorbrewer            1.1_2                  r3.4.1_0    conda-forge
r-rcpp                    0.12.13                r3.4.1_0    conda-forge
r-readr                   1.1.0                  r3.4.1_0    conda-forge
r-reshape2                1.4.2                  r3.4.1_0    conda-forge
r-rgdal                   1.2_8                  r3.4.1_2    conda-forge
r-rlang                   0.1.2                  r3.4.1_0    conda-forge
r-rsqlite                 2.0                    r3.4.1_0    conda-forge
r-rstudioapi              0.7                    r3.4.1_0    conda-forge
r-scales                  0.4.1                  r3.4.1_0    conda-forge
r-shiny                   1.0.3                  r3.4.1_0    conda-forge
r-sourcetools             0.1.6                  r3.4.1_0    conda-forge
r-sp                      1.2_4                  r3.4.1_0    conda-forge
r-stringi                 1.1.2                  r3.4.1_0    conda-forge
r-stringr                 1.2.0                  r3.4.1_0    conda-forge
r-tibble                  1.3.3                  r3.4.1_0    conda-forge
r-viridis                 0.4.0                  r3.4.1_0    conda-forge
r-viridislite             0.2.0                  r3.4.1_0    conda-forge
r-whisker                 0.3_2                  r3.4.1_0    conda-forge
r-withr                   1.0.2                  r3.4.1_0    conda-forge
r-xtable                  1.8_2                  r3.4.1_0    conda-forge
r-yaml                    2.1.14                 r3.4.1_0    conda-forge
readline                  7.0                           0    conda-forge
requests                  2.18.4                   py36_1    conda-forge
ruamel_yaml               0.11.14                  py36_0    conda-forge
setuptools                38.4.0                   py36_0    conda-forge
six                       1.11.0                   py36_1    conda-forge
sqlite                    3.20.1                        2    conda-forge
tk                        8.6.7                         0    conda-forge
urllib3                   1.22                     py36_0    conda-forge
util-linux                2.21                          0    defaults
wheel                     0.30.0                   py36_2    conda-forge
xerces-c                  3.2.0                         0    conda-forge
xz                        5.2.3                         0    conda-forge
yaml                      0.1.6                         0    conda-forge
zlib                      1.2.11                        0    conda-forge
I've tried changing from rstudio enviroment variables - Sys.setenv(..) but still not working.#  Older versions of r-rgdal fails in R too.

Closing this b/c I cannot reproduce it when using the recommendations in https://conda-forge.org/docs/user/tipsandtricks.html#how-to-fix-it.

repo: conda-forge/r-rgdal-feedstock


text:
MNT: rerender

Hi! This is the friendly automated conda-forge-webservice.
I've started rerendering the recipe as instructed in #125.
If I find any needed changes to the recipe, I'll push them to this PR shortly. Thank you for waiting!
Here's a checklist to do before merging.

[x] Bump the build number if needed

Fixes #125

@mfansler, looks like you'll need to wait for me to take care of this in gdal.  I'm about to do that.

https://github.com/conda-forge/gdal-feedstock/pull/968

authors: conda-forge-admin xylar

repo: conda-forge/r-sf-feedstock


text:
circle-ci keys

@conda-forge-admin, please update circle

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I updated the circle-ci deploy key and followed the project.

authors: conda-forge-linter sodre

repo: conda-forge/socat-feedstock


text:
MNT: rerender

Hi! This is the friendly automated conda-forge-webservice.
I've started rerendering the recipe as instructed in #2.
If I find any needed changes to the recipe, I'll push them to this PR shortly. Thank you for waiting!
Here's a checklist to do before merging.

[ ] Bump the build number if needed

Fixes #2

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/recipe.yaml) and found it was in an excellent condition.

repo: conda-forge/spectral-cli-feedstock


text:
Update version number to rebuild the artifacts

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found some lint.
Here's what I've got...
For recipe/meta.yaml:

You are setting MACOSX_SDK_VERSION below c_stdlib_version, in conda_build_config.yaml which is not possible! Please ensure MACOSX_SDK_VERSION is at least c_stdlib_version (you can leave it out if it is equal).
If you are not setting c_stdlib_version yourself, this means you are requesting a version below the current global baseline in conda-forge (10.13). If this is the intention, you also need to override c_stdlib_version and MACOSX_DEPLOYMENT_TARGET locally.

For recipe/meta.yaml:

No valid build backend found for Python recipe for package viztracer using pip. Python recipes using pip need to explicitly specify a build backend in the host section. If your recipe has built with only pip in the host section in the past, you likely should add setuptools to the host section of your recipe.

authors: conda-forge-admin gaogaotiantian

repo: conda-forge/viztracer-feedstock


text:
increase diversity

https://github.com/conda-incubator/governance/blob/main/steering.csv
Any serious plans to add non-"he/him" to this list? If so, I am interested in checking them out.
Currently, 12/16 are "he/him", assuming the others are unknown/tbd.

This is not by design. Conda-forge and the greater conda community have grown organically, and the list here represents people who have been active long enough to feel responsible/obligated to act for the community.
This is to say that you should not read the current state of pronouns as the way that any of us wants it to be. If you or anyone else would like to help us be a more diverse group, I hope you will consider joining us. The steering council here has a minimum size but not a maximum size. I'd be happy to help nominate you or anyone who has shown activity in the conda/conda-forge ecosystem and who has an interest in helping improve the ecosystem.

authors: msarahan ngam

repo: conda-incubator/governance


text:
Enable webhook via operator pre-install payload

Operator pre-install hook provides a nifty way to install additional components. Currently we are using it for deploying and running cloud-api-adaptor. This issue is to track the work required to package and deploy webhook via the pre-install hook

@bpradipt is this issue still relevant or can be closed?
If it's still relevant to what release do you think we should map it to (mid-November, end-December, mid-February etc...)?

authors: ariel-adam bpradipt


text:
Cannot start docker-compose up -d bottledwater-avro

I follow every step of the docker running , but when I run "docker-compose up -d bottledwater-avro" it finished with the following error
/usr/local/bin/bottledwater-docker-wrapper.sh: Setting option --allow-unkeyed
/usr/local/bin/bottledwater-docker-wrapper.sh: Setting option --output-format=avro
/usr/local/bin/bottledwater-docker-wrapper.sh: Detected schema registry, setting --schema-registry=http://schema-registry:8081
/usr/local/bin/bottledwater-docker-wrapper.sh: Running: /usr/local/bin/bottledwater --postgres=host=postgres port=5432 dbname=postgres user=postgres --broker=kafka:9092 --allow-unkeyed --output-format=avro --schema-registry=http://schema-registry:8081 --topic-config=message.timeout.ms=2000
[INFO] Writing messages to Kafka in Avro format
[INFO] Created replication slot "bottledwater", capturing consistent snapshot "000002AD-1".
[FATAL] While reading snapshot: PGRES_FATAL_ERROR: ERROR:  function bottledwater_export(table_pattern := text, allow_unkeyed := boolean, error_policy := text) does not exist
LINE 1: SELECT bottledwater_export(table_pattern := $1, allow_unkeye...
^
HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
[INFO] Dropping replication slot since the snapshot did not complete successfully.

@imanzano did you create the extension (create extension bottledwater;) in the same database (dbname: postgres)? The error seems to be because the extension is missing.

@amitdev That's not necessarily true. I have the same issue (albeit I'm not running via docker). I run a \dx (list all extensions installed) on the postgres database. The extension is definitely installed and i'm still getting this annoying issue.
I don't know why and I don't have a solution.

i hit this issue .
when i run docker ps -a
i got
adf3c7bd0fcc        bottledwaterpg_bottledwater-avro   "/usr/local/bin/bo..."   4 minutes ago       Exited (1) 4 minutes ago                                                bottledwaterpg_bottledwater-avro_1
707a28279450        confluent/schema-registry:2.0.1    "/usr/local/bin/sc..."   13 minutes ago      Up 13 minutes              0.0.0.0:48081->8081/tcp                      bottledwaterpg_schema-registry_1
21d7569813ac        confluent/kafka:0.9.0.0-cp1        "/usr/local/bin/ka..."   13 minutes ago      Up 13 minutes              0.0.0.0:9092->9092/tcp                       bottledwaterpg_kafka_1
c7864916577d        bottledwaterpg_postgres-94         "docker-entrypoint..."   13 minutes ago      Up 13 minutes              0.0.0.0:54094->5432/tcp                      bottledwaterpg_postgres-94_1
92fd00a6ff46        bottledwaterpg_postgres            "docker-entrypoint..."   14 minutes ago      Up 14 minutes              0.0.0.0:54095->5432/tcp                      bottledwaterpg_postgres_1
3d976d5d426b        confluent/zookeeper:3.4.6-cp1      "/usr/local/bin/zk..."   14 minutes ago      Up 14 minutes              2888/tcp, 0.0.0.0:2181->2181/tcp, 3888/tcp   bottledwaterpg_zookeeper_1
i realized that if bottledwaterpg_postgres-94  may have conflict with bottledwaterpg_postgres ?
so i run
docker stop c7864916577d   # which is postgres-94
and i run docker-compose up -d bottledwater-avro successfully.
Hope this will help you. @mbelarbi , may be you have two postgres containers running either.
And I am confused why i have two postgres containers .

authors: amitdev imanzano mbelarbi wswuai

repo: confluentinc/bottledwater-pg


text:
Status for support of Kafka version 0.10.1.0

Folks, We are contemplating whether to use this library for our project. Could you be so kind as to tell us what the status of this library to support Kafka 0.10.1.0/latest? thanks!

I understand by using the latest librdkafka this lib can guarantee 0.10.1.0 compatibility. Are we missing anything in terms of feature set?

Yes, Confluent.Kafka is built on top of librdkafka which is forwards and backwards compatible with all versions of Kafka back to v0.8. More details can be found here: https://github.com/edenhill/librdkafka/wiki/Broker-version-compatibility
Currently we reference a nuget package with native v0.9.2 librdkafka binaries. Very soon this will be updated to v0.9.4 (latest).
Confluent.Kafka it's self is very new and currently missing a few features:

custom partitioners.
produce user specified timestamps.

Going forward it's high priority for us to keep the capability of all client libraries that we support up-to-date with the capability of the latest broker version and confluent platform components (for example schema registry and confluent control center).

Thanks for the clarification @mhowlett

authors: ishworgurung mhowlett

repo: confluentinc/confluent-kafka-dotnet


text:
Fixed args length check

Hello, I am a developer at Sunrise Brokers and am looking to make heavy use of Kafka using .NET clients. I would like to contribute to this project and this is a simple first-time commit as I am new to contributing on github. If I am doing this wrong please let me know. Thanks.
The change fixes an index out of bounds exception when no arguments are supplied, due to the validation check being in the wrong place.

It looks like @MrGlenThomas hasn't signed our Contributor License Agreement, yet.

The purpose of a CLA is to ensure that the guardian of a project's outputs has the necessary ownership or grants of rights over all contributions to allow them to distribute under the chosen licence.
Wikipedia

You can read and sign our full Contributor License Agreement here.
Once you've signed reply with [clabot:check] to prove it.
Appreciation of efforts,
clabot

LGTM, just need the CLA signed

@edenhill I have just signed the agreement and it said "Thanks for your submission", should it update on this page?

Ah I've got it... [clabot:check]

@confluentinc It looks like @MrGlenThomas just signed our Contributor License Agreement. :+1:
Always at your service,
clabot

Thank you for your contribution!

authors: ConfluentCLABot MrGlenThomas edenhill


text:
Epic: Remove requirement for Hash Merging enabled

Ansible has decided to deprecate the hash_behavior in Ansible 2.10, and the plan is to remove it in Ansible 2.13:

https://github.com/ansible/ansible/pull/63300
https://www.reddit.com/r/ansible/comments/a7x92q/in_which_case_hash_behaviourmerge_can_become/ec8mf7f/

We are currently struggeling with variable precedence in our inventory, and it seems like it might be related to this setting - enforced by the requirement in this tasks: https://github.com/confluentinc/cp-ansible/blob/9c7954d5d32bb5d6aa5e84f9d9570a5ee6ba54bb/roles/confluent.common/tasks/main.yml#L2
When running our playbook, we are getting this warning:
[DEPRECATION WARNING]: DEFAULT_HASH_BEHAVIOUR option, This feature is fragile
and not portable, leading to continual confusion and misuse , use the
``combine`` filter explicitly instead. This feature will be removed in version
2.13. Deprecation warnings can be disabled by setting
deprecation_warnings=False in ansible.cfg.

I suggest that the requirement for hash_behaviour=merge is removed by following the migration path suggested by Ansible.

@erikgb Thanks for reaching out.  We actually already have this on our internal roadmap to change in a future release.  We've also had this raised by the community in the past, quite recently in fact, see the following closed issue:
https://github.com/confluentinc/cp-ansible/issues/458
Can you confirm the exact issue you are seeing besides the warning?  Right now, the playbooks should fully work as long as hash merging is enabled, which it is in the ansible.cfg included in the repo.

@JumaX Your playbooks are probably working just fine. 😄 And I know that the playbooks currently is the only supported entrypoint. But you might have already noticed, from other issues and pull requests, that we are using the cp-ansible roles, and not the all.yml playbook - for desired state. We have created our own playbook with some additional stuff. And I cannot get the variable precedence to work the way I want, with this setting required by the cp-ansible roles. But I managed to work around it, of course.

@erikgb Understood.  Can you confirm the specific ask here then?  To confirm, we plan on moving away from hash merging in the future, so provided there isn't a specific ask/issue we can help with, can we close this out?

@JumaX I don't like when an open-source project has an internal Jira as master. It is either GitHub which is master, and then spill over all your findings, thoughts and musings back into GitHub issues - so that the community can follow along. Or close-source your project....
That said, you (as developers) are doing an amazing job here! Kudos! ❤ But please take this feedback to the decicion makers in Confluent!
Closing issue as "done" - as requested.

This is still an issue, and should be fixed. Reopening to track progress in the public/community.

@erikgb The Ansible committers have decided not to remove hash merging, so this PR is no longer required.  You can find details here:
https://github.com/ansible/ansible/pull/73328
https://github.com/ansible/ansible/issues/73089
https://meetbot.fedoraproject.org/ansible-meeting/2021-01-21/ansible_core_public_irc_meeting.2021-01-21-15.01.log.html

The Ansible committers have decided not to remove hash merging, so this PR is no longer required.

@JumaX Thanks for the detailed references. I wasn't aware of the un-deprecation of that variable. But it is quite debatable, and the documentation still strongly discourages use of this functionality. And for large plays - including playbooks/roles from cp-ansible, like we have, it is really sad to have to set this variable merge behavior globally. So I'll vote for fixing it, at least in the long term.

@erikgb What's interesting about this, if you read through the irc meeting notes, is that their isn't a clear reason for the feature's removal.  It's one committers opinion without a lot of evidence. Even the other committers don't see an issue with it. It appears that it was generating a lot of questions from new users, but nothing more.  That being said, there also doesn't appear to be a clear work around for hash merging, as combine will not solve all use cases.
I've been thinking about this, and my other concern is that we will end up with a lot of temp variables to try and work around this functionality.  I could be wrong here, but I am trying to see another way we could work around hash merging but nothing is coming up thus far.

Today we had another incident where this extremely confusing setting turns out to be the root cause. Is this something that the team can prioritize to fix? @domenicbove @nsharma-git

@JumaX i would argue that this ticket itself has several posts that are a good example why this setting is problematic.
Mainly it comes down to subverting the normal expectation on how a value is arrived at, the default is 'new overrides old', while setting it to merge is 'new appends to old .. mostly ... depends on method used to set each instance of a variable'.
It also can make content incompatible, roleA was written with 'merge' while roleB was written with 'overwrite', using both in same run becomes impossible as 'variable merging' is not restricted to the role itself, but has to happen globally at all points in which you define and use a variable.
Personally, my main reason to oppose deprecation is that there is no good migration path for existing plays/roles that currently rely on it, otherwise I would be first in line to remove it.

authors: JumaX bcoca erikgb

repo: confluentinc/cp-ansible


text:
KAFKA-13778: Fetch from follower should never run the preferred read replica selection (3.1)

The current preferred read replica selection logic relies on partition.leaderReplicaIdOpt to determine if the selection must be run. The issue is that partition.leaderReplicaIdOpt is defined for both the leader and the followers thus the logic is ran all the time. The impact is not too bad as the leader is selected most of the time when the logic is ran by the follower and the leader is filtered out. However there are cases where the selection on a follower could redirect the consumer to another follower under certain rare conditions. For instance with the RackAwareReplicaSelector , the follower must have stale replica states from a previous leadership and must have other followers in the same rack for instance. Other implementation of the selection logic could be more impacted.
This patch ensures that the preferred read replica selection is only ran by the leader.
Reviewers: David Jacot djacot@confluent.io
(cherry-picked from commit https://github.com/apache/kafka/commit/4218fc61fedb02b78d35c88e56ab253baaf09f39)
Conflicts:
core/src/test/scala/unit/kafka/server/ReplicaManagerTest.scala
More detailed description of your change,
if necessary. The PR title and PR message become
the squashed commit message, so use a separate
comment to ping reviewers.
Summary of testing strategy (including rationale)
for the feature or bug fix. Unit and/or integration
tests are expected for any behaviour change and
system tests should be considered for larger changes.
Committer Checklist (excluded from commit message)

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

unrelated failures. reran locally and passed
org.apache.kafka.clients.consumer.CooperativeStickyAssignorTest.testLargeAssignmentAndGroupWithNonEqualSubscription()
org.apache.kafka.clients.consumer.CooperativeStickyAssignorTest.testLargeAssignmentAndGroupWithNonEqualSubscription()

repo: confluentinc/kafka


text:
As a dev user, I want to be able to cancel transactions

Problem
After the merge of #1810 , if the slippage is failing on the destination domain, the user can call forceUpdateSlippage to update the slippage and complete the transfer. This represents one of two possible actions a user would take to handle transfers failing due to slippage on the destination domain. The other action is cancel (return funds to origin), which user would have to take the slippage on, then return to the origin via xcall.
The implementation of this is blocked by #1735 (see Other below).
Ideas to solve this
Instead, the user should be able to call a forceCancel function with the following interface:
function forceCancel(
    CallParams calldata _params,
    address _originSender,
    uint32 _canonicalDomain,
    bytes32 _canonicalId,
    uint256 _normalizedIn,
    uint256 _amount,
    uint256 _nonce
  ) external onlyAgent(_params) { ... }

This function would:

Burn the tokens if the transfer is reconciled
Block the transfer from being reconciled or executed
Send a transfer message back to the origin domain
Transfer the msg.sender the

Acceptance Criteria

[ ] User can opt to cancel destination domain transactions
[ ] The user should get the funds sent back to them on the origin domain for cancelled transactions

Other
There are some things that make this implementation a bit more difficult:

You are assuming the msg.sender of the xcall can receive funds, which they may not be able to do. It is unclear how to solve this problem, though you could designate a recipient on the forceCancel call.
You are assuming the user sent in the adopted asset, and thus would like to receive the adopted asset. Alternatively, you could either (a) enforce the user always xcalls with the adopted asset, (b) store which asset the xcall was performed with so you know what the user wants, (c) always send back the adopted asset, or (d) allow the agent to specify when calling
The ConnextHandler contract itself cannot mint or burn tokens until #1735 is merged (making this much more difficult).

cleaning up old stuff

out of scope

authors: LayneHaber alexwhte

repo: connext/monorepo


text:
[Milestone] Release 1.0

Tracking item to collect 1.0 must-haves.

[x] Finalize CLI options mechanism
[ ] Include a CHANGELOG

Some other nice-to-haves (but not required).

[ ] Custom repo image for link sharing (instead of connorjs avatar default)

CLI has been finalized. Using commander, added localsConvention, updated defaults.

Adding repo image in https://github.com/connorjs/css-typed/pull/20. This will be used for social media/link sharing.

repo: connorjs/css-typed


text:
Firefox 60 Linux, guide links don't work, already enabled does nothing

Hi,
Plugin will notify properly for sites that match, however it just says Show 2fa guide for website.com (on every site). When I click activate, nothing happens. When I click the guide link, it puts the plugin in a new tab (see attached). It will do the new tab over and over again. If I click already have enabled, nothing happens.
Tried versions 0.6.0 and 0.7.0 of the plugin in Firefox 60.0.2, x86_x64 ArchLinux.

Interesting, if the inital balloon pops up asking to activate, this does go to the proper site. Only when first asked prompted though.

Confirmed in 0.6.0 and 0.7.0 in Windows Firefox 60 and 61 as well. First pop up is fine, everything else references website.com. Haven't looked at source yet, but It's not passing a variable correctly.

Additionally, several ballons will sometimes pop up on a site. Guessing this has to do with multiple requests for a domain (both Windows and Linux). Let me know if you want a separate issue for this.

I haven't had time to replicate this yet and figure out whats up, but clearly I need to do better testing on Linux generally and FF specifically.
Thanks for filing the bug and the info too!

Thanks @conorgil. I'm happy to help test out if you need. Between Windows and Linux the same issues are both present in Firefox, if you fix one platform, the others should just follow suit (seems to be the case with most Firefox extensions). Can't speak for OS X or BSD, but probably the same deal.

@conorgil, it should be enough to fix by adding this in the header:
<meta charset="utf-8"/>
Unfortunately I don't have a lot of experience with developing web extensions, so I'm working on figuring out how to do this with Mozilla and their web-ext tool. Testing web extensions in Mozilla seems a bit new and somewhat buggy, so not as straightforward as I hoped.
I'll keep at this when I have time and update when I make any notable progress.

@JSkier21 Sorry this took so long to take a look at, but I am pretty sure that this bug is all fixed up with the latest release to the Firefox store. All of my manual tests appear to be working as expected in Firefox on OSX. Mind testing for me on your systems too? If all looks good, then we can close this out. Thanks again for reporting the bug initially and improving the overall quality of the project!

@JSkier21 Yea, the multiple popup is a different bug. If you could create an issue with a screenshot or other supporting info, that would be really useful. I am pretty sure that Chrome on OSX prevents multiple notifications from displaying at the same time, which is why I didn't catch it earlier.


text:
token的icon在imtoken 上不显示

合约地址
0xd2c6738d45b090ec05210fe8dceef4d8fc392892
图片早就传上去了

你好，按照操作教程提交资料，并在提交的PR链接下向我们留言，谢谢。

authors: Doralvor wenyanwang

repo: consenlabs/token-profile


text:
pdt基本信息提交

项目信息
Matrix World
官网：http://matrixworld.top
项目通证：PDT
总量：21亿
流通：4.046875亿
基石，私募及团队所占份额均大比例进行锁仓，圈内知名市值管理团队操盘。
团队背景
Matrix World团队分布在德国、北京和江苏，核心成员平均超过二十年汽车行业经验，是国内早期产于汽贸行业的团队，连续创业者。项目由国内汽车销售行业某上市公司牵头，多家业内机构共同推动支持，目前已拥有2000余家汽车销售及服务网点作为线下实体支撑。
项目基本情况
Matrix World是一个旨在改善城市出行生态，将汽车敏感数据上链保护的区块链项目，将成为区块链首个实现虚实结合，完成真实落地，并拥有千万级别用户的应用。推动中国汽车市场朝着绿色，健康，透明的方向发展。

更多信息请关注官方媒体获得项目最新动态。
官方社群：
Twitter：https://twitter.com/MatrixWorld6
Telegram：https://t.me/MatrixWorld6
Facebook：https://www.facebook.com/MatrixWorld6
微信公众号：MatrixWorld生态
媒体报道
金色财经：https://www.jinse.com/bitcoin/224392.html

你好，请检查一下合约
https://etherscan.io/address/0xf15bd6a380a0619f99b199ca9e954ce0c3e09af7

你好合约存在什么问题吗？？

@wenyanwang
你好合约存在什么问题吗？？

全部转账都是执行合约错误，建议检查，谢谢。

@wenyanwang 你好，我们看了下错误转账都是我们测试锁仓逻辑导致的，未锁仓的是可以正常转账的。
比如：
https://etherscan.io/tx/0x4bcb2521154661e6cc8ebf5380fb68ab09f3ad4011f994fef018a2b4aa31153b


text:
Add BIDA token

團隊背景：
幣達團隊本身由一群資深金融人士與早期虛擬貨幣愛好者所組成，貢獻在市場上打滾多年的經驗；也因為是各大交易平台的使用者，所以以站在使用者操作平台的角度為出發點，透過自身熟悉整體交易過程，在創設交易所時，著重改善線上各大交易平台一些使用問題，並且全面優化、多樣化交易模式，以及首創友善新手玩家的交易環境，為使用者提供更安全、更省時、更便捷的服務，幣達團隊致力於為使用者打造世界級的多功能型交易平台。
项目基本情况:
幣達平台推行的代幣為BIDA，發行總量恒定為3億個，且保證永不增發。BIDA幣是基於以太坊
Ethereum發行的去中心化ERC20標準代幣。
BIDA代幣用途
．交易手續費約為 0.1% ~ 0.2%，使用BIDA代幣可享有手續費優惠50%
．使用者使用帳戶聯動，每月收取BIDA代幣做為手續費
．使用者使用對沖交易，每月收取BIDA代幣做為手續費
．優質代幣上架會收取BIDA代幣做為合作上架費用
．提領手續費可以使用BIDA代幣折抵部分手續費（會根據區塊實際情況調整）
．使用者使用槓桿交易可以使用BIDA代幣支付並享有優惠 ．使用者使用首次代幣發售需付一筆BIDA代幣
為手續費
發行方式
本次ICO公開發行比例為45%，另外15%用於天使輪代幣認購項目，20%為創始團隊成員持有，20%行銷
活動，本次代幣發售預定提供1.35億個BIDA。
幣達交易所: https://www.bidaone.com
幣達ICO：https://ico.bidaex.io
更多關於BIDA的訊息
幣達交易所官方粉絲專頁：https://www.facebook.com/bidacoin/
幣達交易所官方中文電報：https://t.me/joinchat/IVsvfg70GO1rMNez1HAAJw
幣達交易所官方英文電報：https://t.me/joinchat/IVsvfg7jWn9gkjv12Qsbng
幣達交易所官方推特：https://twitter.com/Bidaexchange
官方Line@：https://line.me/R/ti/p/%40mdd9131w
媒体报道:
蘋果日報:https://tw.appledaily.com/headline/daily/20180718/38072196/
yahoo新聞：https://goo.gl/NP3E8T
蕃薯藤新聞：https://goo.gl/8ENZFu
台灣好新聞：https://goo.gl/whgzmx
hinet新聞新聞：https://goo.gl/1XYLsi
優仕網：https://goo.gl/MNGF85
life新聞：https://goo.gl/4GtLFZ
pchome新聞：https://goo.gl/vCsyZn
新浪網新聞：https://goo.gl/KFbZQD
愛逛街：https://goo.gl/HUZHjf
腾讯新闻客户端：https://view.inews.qq.com/a/20180815A0WUM000
今日头条：http://toutiao.com/item/6589832608513786381/
搜狐财经：https://www.sohu.com/a/247306898_100042472
凤凰号：http://wemedia.ifeng.com/73749892/wemedia.shtml
企业家财经：http://www.ceof.cn/article-14188-1.html
理财18：http://www.licai18.com/article/ArticleDetail.jsp?docId=2507546
FX168财经：https://news.fx168.com/qiye/1808/2629844.shtml
慧聪网：http://info.service.hc360.com/2018/08/151503545951.shtml
百度百家：http://baijiahao.baidu.com/builder/preview/s?id=1608849130668932221
中国清洁门户：http://www.zgqjmh.com/mation_show_177553.html
新浪看点：http://cj.sina.com.cn/articles/view/6018565366/166bc04f600100dfcq?from=finance&subch=nauto
收录的交易所：
转账所需 Gas Limit（对 ERC-20 项目方）：100000
为确保 Token Profile 的顺利通过，务必逐一确保以下检查项并补充项目资料：
.json 及 .png 文件检查项

[] logo 尺寸：120120 px
[*] logo 背景：透明
[*] 代币有至少一笔成功的转账记录
[*] 此项对于 ERC-20 项目方：合约地址有大小写（做 checksum）
[*] .json 和 .png 文件名一致（包括大小写）

Please check the following to ensure a successful verification of Token Profile
.json and .png document checklists

[x] logo dimensions: 120*120 px
[ ] logo background: Transparent
[ ] At least one transaction on the token contract
[ ] For ERC-20 project teams: Upper and lower capitalized alphabets in token address (For checksum purposes)
[ ] Same document name for both .json and .png (Including capitalization)

Project background details:
Team background:
Current situation of the project:
Media exposures:
Tradeable exchanges:
Recommended Gas Limit (For ERC-20 project teams) for transaction: (Default is 60,000)

为确认真实性，请用贵方的官方企业邮箱给 token@consenlabs.com 发送一份认证邮件。

格式：
标题：XXX 项目方官方邮件认证
正文：GitHub pr 链接：https://github.com/consenlabs/token-profile/pull/1636（此为示例）

确认后，我们会尽快处理。

欢迎在社区中推荐用户使用 imToken 2.0 管理资产。

authors: tstt zhangmaku


text:
Add BSQ token

官方公告：
https://bsquant.ai/
团队背景：
基于对区块链社区共识：开放、合作、共赢的追求。将优秀的产品回馈社区，建设蓝石量化生态圈，服务更广大的客户。
1、团队经验丰富
核心团队兼具传统金融和加密货币经验，有多次成功创业经验。投资顾问团队有丰富的资源和众多的合作伙伴助力社区运营。
2、技术优势明显
经过市场检验的模型对于大量过往历史数据的分析和考究使得机器人在很大程度上已经规避掉了“冒失抉择”的风险。机器人在开仓，补仓，平仓，追补仓方面已经做到完全智能化快速化。
3、产品成熟高效
量化机器人已在 BitMEX、Huobi OTC 等交易平台上线运营，用户体验优秀。服务3000+客户，累计为投资者赚取了 1000+比特币。核心团队：
Sami CEO
蓝石量化联合创始人兼首席执行官。币圈知名分析师、投资人，构架全球战略性发展策略，在对冲基金和金融证券领域拥有多年操盘经验。数字资产量化投资先驱，主导并参与若干数字货币一级市场。
Neo Co-Founder
蓝石量化联合创始人。作为一个拥有超过 10 年经验的知名经纪人，Neo 了解数字资产量化投资的来龙去脉—他很高兴找到了一个最大挑战的解决方案。凭借作为企业家和投资者的成功记录，其投资组合包括 10 多家公司。Neo 能够将卓越的商业意识与对当前行业及其复杂性的深刻理解相结合。
Tang Co-Founder
蓝石量化联合创始人。Tang 是数字资产量化投资领域的领先专家之一。凭借其丰富的专业知识，Tang 知道如何领导跨学科团队从构思到市场实施，开发和推出有价值的产品。
Zhou CTO
蓝石量化联合创始人兼首席技术官。毕业于日本京都大学工学部情报科；曾就职于日本丰田汽车、NTT 等世界知名企业，并在日本著名证券公司 Nomura情报处理系统部主导多个计算机高频交易开发项目；是金融数据处理技术领域内不可多得的技术专家。
项目基本情况：
1、基于比特币的量化交易
2008 年金融海啸席卷全球，投资者对证券类资产的价值失去信心，从而引发流动性危机。多国中央银行多次向金融市场注入巨额资金救市，法币泛滥，物价飞涨。此时比特币横空出世，中本聪在创世区块中写道：“英国泰晤士报 2009年1月3日文，财政大臣正处于实施第二轮银行紧急援助的边缘“。从此，比特币肩负起对抗法币通胀的重任。
经过 10 年的发展，比特币等数字货币成为本世纪最有潜力的投资品之一。未来已来，先行者手握比特币已在路上。持币升值是好的方式，币值大起大落带来的套利区间已吸引无数眼球，当前量化投资是最安全的高收益套利方式之一。对于普通投资者，量化投资借助现代统计学和数学的方法，制定了一个客观参考的指标，当符合条件时不带感情色彩的买入或者卖出，大概率的获得超出平均的收益。对于机构投资者，量化交易充当对应的买家或者卖家，在市场上交易盘活交易量。拉平不同数字货币之间的交易对，以及不同交易所相同数字货币对之间的差价，避免了市场上不合理的波动。
2、比特币量化交易市场痛点
普通量化交易机器人无法满足中小投资者对量化交易的需求：1、大平台体系不对外开放。传统的量化交易体系封闭，必须使用特定的语言和函数，主要服务于大公司和大客户；2、小平台技术水平落后。初创的量化交易机器人繁多，虽然对小客户开放，但技术水平层次不齐，无法保证客户预期收益，甚至是本金安全。3、自建量化交易体系效益低下。量化交易系统存在较高的技术门槛，需要具备期货分析能力，对数字资产要有深入研究和独到的见解，需要大量人力资源投入，投入/产出比低。
3、蓝石量化的特点
1、多维度行业经历
核心团队专业分布广泛。深刻理解期货投资分析，精通数字化人工智能化产品技术研发，拥有多年金融行业经验，金融学术理论深厚扎实，基金风险管理经验丰富，对数字资产有深入研究和独到见解，精通量化交易。
2、日本尖端技术
基于GDB日本株式会社（日本策略研发实验室）的技术积淀，运用尖端技术打造专业量化交易机器人。
3、区块链社区共识
认可并追求开放、合作、共赢的共识。将优秀的产品回馈社区，建设蓝石量化生态圈，服务更广大的客户。
4、蓝石量化生态圈简介
1、蓝石量化生态圈内涵
蓝石量化项目是新加坡BSQ基金会发起的以数字资产量化交易为核心，线上和线下为支撑的项目，最终构建面向2030全域量化生态圈。以交易所、矿场主、资深币圈用户为横向支撑节点，以核心产品、衍生服务、生态系统为纵向牵引节点,构建“三横三纵”矩阵。
更多关于 imToken 的信息
•	官网: https://bsquant.ai/
媒体报道
•	btc315【共识访谈】第六期：专访唐维继！与其佛系持币，不如量化赚币！
建议 gas limit：60000

非常抱歉，PR不符合checksum格式要求，请参考教程修改。

checksum格式已修改，烦请再次审核，谢谢，辛苦了！

欢迎在社区中推荐用户使用 imToken 2.0 管理资产。


text:
Add EOT token.

官方公告：https://www.supereot.com/index/index/indexs.html
为确保 Token Profile 的顺利通过，务必逐一确保以下检查项并补充项目资料：
.json 及 .png 文件检查项

[x] logo 尺寸：120*120 px
[x] logo 背景：透明
[x] 代币有至少一笔成功的转账记录
[x] 此项对于 ERC-20 项目方：合约地址有大小写（做 checksum）
[x] .json 和 .png 文件名一致（包括大小写）

项目资料：

团队背景：Distributed Global基金和3个团队一百多名技术人员建立而成，有着非常专业的市值管理团队和技术团队。
项目基本情况：supereot简称EOT，通过DPoS机制和整体架构分片多链（Shard Chains）等改变现有交易网络用户和Gas费用上涨循环。解决了ETH很多的扩容问题，可扩展的多链网络.创新安全强大的3.0区块链公链平台.
媒体报道：https://i.bishijie.com/detail/1982438
Twitter: https://twitter.com/supereot
转账所需 Gas Limit（对 ERC-20 项目方）：60000

@sfsy520 Hi, could you please check for this PR? If I do something wrong, please tell me and then I will make changes.

LOGO 不符合要求

Okay, I will have a check.

Ohhhh, it seems like the logo background is not transparent, sorry for that, I will change it later.

@Lumos-yiqun  Hi, how about now?

@sfsy520 Hi, I have uploaded the new logo, could you please have a check, Thanks!

@sfsy520 Hi, I have uploaded the new logo, could you please have a check, Thanks!

抱歉，无法验证资料真实性，不予通过。可通过代币合约地址在 imToken 中添加此代币。

@Lumos-yiqun Which information do you mean, let me have a check?

@Lumos-yiqun @sfsy520 Hi, we are trying to do as you recommended, but we can not find our token by contract address in imtoken, and we are sure we have satisfied the following requirements:

please check if there is no successful transaction records: https://etherscan.io/tx/0x19a34486c143756c9e6d949308d709d07c3b416db1205084d38f516f6b722bb0
please verify your contract information on Etherscan: https://etherscan.io/address/0x9e8d7c41941503c485eaaeb06283998936bf8901#code

So could you please help us manually add it. Thanks a lot!

I have realized the issue, thanks for your help. we can close this PR totally.

authors: Lumos-yiqun Skyge


text:
Agreement categories table

DOD:
Categories table in hasura.

[ ] Validate with Tzur that we're dealing with one to many relations
[ ] Each category should contain a group (one to many), required
[ ] Each agreement should contain a category (one to many), optional

Q:
Each category should contain a group (one to many), required = if the connection is a category has at least 1 group, how to model it? If I understand correctly, I would think to have a categories table with name and ID, and in the GROUPS table to have a category column. not the other way around.

repo: consenz-io/webapp


text:
🛑 coller.resterdigne.net is down

In e3ef84d, coller.resterdigne.net (https://coller.resterdigne.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: coller.resterdigne.net is back up in 7d1902f.

repo: constructions-incongrues/status