Convert to use tasty-discover

Changelog
- description: |
    Convert to use `tasty-discover`
  compatibility: no-api-changes
  type: maintenance

Context
This relieves the developer from having to write the plumbing for new tests.
It also allow individual tests to be run.
The tests can be run as before:
cabal test cardano-cli-golden
Build profile: -w ghc-9.6.2 -O1
In order, the following will be built (use -v for more details):
 - cardano-cli-<IP_ADDRESS> (test:cardano-cli-golden) (ephemeral targets)
Preprocessing test suite 'cardano-cli-golden' for cardano-cli-<IP_ADDRESS>..
Building test suite 'cardano-cli-golden' for cardano-cli-<IP_ADDRESS>..
Running 1 test suites...
Test suite cardano-cli-golden: RUNNING...
test/cardano-cli-golden/cardano-cli-golden.hs
  deserialise legacy signing Key:                              OK
      ✓ Test.Golden.Byron.SigningKeys.hprop_deserialise_legacy_signing_Key passed 1 test.
  deserialise nonLegacy signing Key:                           OK
      ✓ Test.Golden.Byron.SigningKeys.hprop_deserialise_nonLegacy_signing_Key passed 1 test.
  print legacy signing key address:                            OK (0.09s)
      ✓ Test.Golden.Byron.SigningKeys.hprop_print_legacy_signing_key_address passed 1 test.
  print nonLegacy signing key address:                         OK (0.08s)
      ✓ Test.Golden.Byron.SigningKeys.hprop_print_nonLegacy_signing_key_address passed 1 test.
  generate and read nonlegacy signingkeys:                     OK
      ✓ Test.Golden.Byron.SigningKeys.hprop_generate_and_read_nonlegacy_signingkeys passed 100 tests.
  migrate legacy to nonlegacy signingkeys:                     OK (0.04s)
      ✓ Test.Golden.Byron.SigningKeys.hprop_migrate_legacy_to_nonlegacy_signingkeys passed 1 test.
  deserialise NonLegacy Signing Key API:                       OK
      ✓ Test.Golden.Byron.SigningKeys.hprop_deserialise_NonLegacy_Signing_Key_API passed 1 test.
  deserialiseLegacy Signing Key API:                           OK
      ✓ Test.Golden.Byron.SigningKeys.hprop_deserialiseLegacy_Signing_Key_API passed 1 test.
  GovernanceCmdError
    StakeCredGovCmdError:                                      OK
        ✓ <interactive> passed 1 test.
    VotingCredentialDecodeGovCmdEror:                          OK
        ✓ <interactive> passed 1 test.
    WriteFileError:                                            OK
        ✓ <interactive> passed 1 test.
    ReadFileError:                                             OK
        ✓ <interactive> passed 1 test.
    NonUtf8EncodedConstitution:                                OK
        ✓ <interactive> passed 1 test.
    GovernanceCmdTextEnvReadError:                             OK
        ✓ <interactive> passed 1 test.
    GovernanceCmdCddlError:                                    OK
        ✓ <interactive> passed 1 test.
    GovernanceCmdKeyReadError:                                 OK
        ✓ <interactive> passed 1 test.
    GovernanceCmdCostModelReadError:                           OK
        ✓ <interactive> passed 1 test.
    GovernanceCmdTextEnvWriteError:                            OK
        ✓ <interactive> passed 1 test.
    GovernanceCmdEmptyUpdateProposalError:                     OK
        ✓ <interactive> passed 1 test.
    GovernanceCmdMIRCertificateKeyRewardMistmach:              OK
        ✓ <interactive> passed 1 test.
    GovernanceCmdCostModelsJsonDecodeErr:                      OK
        ✓ <interactive> passed 1 test.
    GovernanceCmdEmptyCostModel:                               OK
        ✓ <interactive> passed 1 test.
    GovernanceCmdUnexpectedKeyType:                            OK
        ✓ <interactive> passed 1 test.
    GovernanceCmdPollOutOfBoundAnswer:                         OK
        ✓ <interactive> passed 1 test.
    GovernanceCmdPollInvalidChoice:                            OK
        ✓ <interactive> passed 1 test.
    GovernanceCmdDecoderError:                                 OK
        ✓ <interactive> passed 1 test.
    GovernanceCmdVerifyPollError:                              OK
        ✓ <interactive> passed 1 test.
    GovernanceCmdWriteFileError:                               OK
        ✓ <interactive> passed 1 test.
    ShelleyGovernanceCmdMIRCertNotSupportedInConway:           OK
        ✓ <interactive> passed 1 test.
    ShelleyGovernanceCmdGenesisDelegationNotSupportedInConway: OK
        ✓ <interactive> passed 1 test.
  golden HelpAll:                                              OK (0.11s)
      ✓ Test.Golden.Help.hprop_golden_HelpAll passed 1 test.
  golden HelpCmds:                                             OK (11.17s)
      ✓ Test.Golden.Help.hprop_golden_HelpCmds passed 1 test.
  golden view byron:                                           OK (0.08s)
      ✓ Test.Golden.TxView.hprop_golden_view_byron passed 1 test.
  golden view shelley:                                         OK (0.12s)
      ✓ Test.Golden.TxView.hprop_golden_view_shelley passed 1 test.
  golden view allegra:                                         OK (0.08s)
      ✓ Test.Golden.TxView.hprop_golden_view_allegra passed 1 test.
  golden view mary:                                            OK (0.08s)
      ✓ Test.Golden.TxView.hprop_golden_view_mary passed 1 test.
  golden view alonzo:                                          OK (0.11s)
      ✓ Test.Golden.TxView.hprop_golden_view_alonzo passed 1 test.
  golden view alonzo signed:                                   OK (0.11s)
      ✓ Test.Golden.TxView.hprop_golden_view_alonzo_signed passed 1 test.
  golden version:                                              OK (0.04s)
      ✓ Test.Golden.Version.hprop_golden_version passed 1 test.

All 39 tests passed (12.11s)
Test suite cardano-cli-golden: PASS
Test suite logged to:
/Users/jky/wrk/iohk/cardano-cli/dist-newstyle/build/aarch64-osx/ghc-9.6.2/cardano-cli-<IP_ADDRESS>/t/cardano-cli-golden/test/cardano-cli-<IP_ADDRESS>-cardano-cli-golden.log
1 of 1 test suites (1 of 1 test cases) passed.
[~/wrk/iohk/cardano-cli]$ cabal test cardano-cli-test
Build profile: -w ghc-9.6.2 -O1
In order, the following will be built (use -v for more details):
 - cardano-cli-<IP_ADDRESS> (test:cardano-cli-test) (ephemeral targets)
Preprocessing test suite 'cardano-cli-test' for cardano-cli-<IP_ADDRESS>..
Building test suite 'cardano-cli-test' for cardano-cli-<IP_ADDRESS>..
Running 1 test suites...
Test suite cardano-cli-test: RUNNING...
test/cardano-cli-test/cardano-cli-test.hs
  backwardsCompatibleCliFormat:              OK (0.11s)
      ✓ Test.Cli.CliIntermediateFormat.hprop_backwardsCompatibleCliFormat passed 1 test.
  createVRFSigningKeyFilePermissions:        OK (0.04s)
      ✓ Test.Cli.FilePermissions.hprop_createVRFSigningKeyFilePermissions passed 1 test.
  convertITNKeys:                            OK (0.08s)
      ✓ Test.Cli.ITN.hprop_convertITNKeys passed 1 test.
  convertITNExtendedSigningKey:              OK (0.04s)
      ✓ Test.Cli.ITN.hprop_convertITNExtendedSigningKey passed 1 test.
  convertITNBIP32SigningKey:                 OK (0.04s)
      ✓ Test.Cli.ITN.hprop_convertITNBIP32SigningKey passed 1 test.
  golden bech32Decode:                       OK
      ✓ Test.Cli.ITN.hprop_golden_bech32Decode passed 1 test.
  json roundtrip delegations and rewards:    OK (0.02s)
      ✓ Test.Cli.JSON.hprop_json_roundtrip_delegations_and_rewards passed 100 tests.
  roundtrip kes period info output JSON:     OK
      ✓ Test.Cli.JSON.hprop_roundtrip_kes_period_info_output_JSON passed 100 tests.
  roundtrip Value parse render:              OK
      ✓ Test.Cli.MultiAssetParsing.hprop_roundtrip_Value_parse_render passed 100 tests.
  roundtrip Value parse renderPretty:        OK
      ✓ Test.Cli.MultiAssetParsing.hprop_roundtrip_Value_parse_renderPretty passed 100 tests.
  buildShelleyPaymentAddress:                OK (0.08s)
      ✓ Test.Cli.Pioneers.Exercise1.hprop_buildShelleyPaymentAddress passed 1 test.
  buildShelleyStakeAddress:                  OK (0.13s)
      ✓ Test.Cli.Pioneers.Exercise1.hprop_buildShelleyStakeAddress passed 1 test.
  createTransaction:                         OK (0.13s)
      ✓ Test.Cli.Pioneers.Exercise2.hprop_createTransaction passed 1 test.
  createOperationalCertificate:              OK (0.12s)
      ✓ Test.Cli.Pioneers.Exercise3.hprop_createOperationalCertificate passed 1 test.
  createStakeAddressRegistrationCertificate: OK (0.08s)
      ✓ Test.Cli.Pioneers.Exercise4.hprop_createStakeAddressRegistrationCertificate passed 1 test.
  createLegacyZeroTxOutTransaction:          OK (0.13s)
      ✓ Test.Cli.Pioneers.Exercise5.hprop_createLegacyZeroTxOutTransaction passed 1 test.
  createZeroLovelaceTxOutTransaction:        OK (0.12s)
      ✓ Test.Cli.Pioneers.Exercise6.hprop_createZeroLovelaceTxOutTransaction passed 1 test.
  readFromPipe:                              OK
      ✓ Test.Cli.Pipes.hprop_readFromPipe passed 10 tests.
  percentage:                                OK
      ✓ Test.Cli.Shelley.Run.Query.hprop_percentage passed 1 test.
  configMainnetHash:                         OK (0.30s)
      ✓ Test.Config.Mainnet.hprop_configMainnetHash passed 1 test.
  configMainnetYaml:                         OK
      ✓ Test.Config.Mainnet.hprop_configMainnetYaml passed 1 test.

All 21 tests passed (1.45s)
Test suite cardano-cli-test: PASS
Test suite logged to:
/Users/jky/wrk/iohk/cardano-cli/dist-newstyle/build/aarch64-osx/ghc-9.6.2/cardano-cli-<IP_ADDRESS>/t/cardano-cli-test/test/cardano-cli-<IP_ADDRESS>-cardano-cli-test.log
1 of 1 test suites (1 of 1 test cases) passed.

Checklist

[ ] Commit sequence broadly makes sense and commits have useful messages
[ ] The change log section in the PR description has been filled in
[ ] New tests are added if needed and existing tests are updated.  These may include:

golden tests
property tests
roundtrip tests
integration tests
See Runnings tests for more details

[ ] The version bounds in .cabal files are updated
[ ] CI passes. See note on CI.  The following CI checks are required:

[ ] Code is linted with hlint.  See .github/workflows/check-hlint.yml to get the hlint version
[ ] Code is formatted with stylish-haskell.  See .github/workflows/stylish-haskell.yml to get the stylish-haskell version
[ ] Code builds on Linux, MacOS and Windows for ghc-8.10.7 and ghc-9.2.7

[ ] The changelog section in the PR is updated to describe the change
[ ] Self-reviewed the diff

Note on CI
If your PR is from a fork, the necessary CI jobs won't trigger automatically for security reasons.
You will need to get someone with write privileges.  Please contact IOG node developers to do this
for you.

I think there is an issue with the derivation for blst. It's brought in like this:
/nix/store/3nkxnv4rnvcnyhq7i4djxkvqgrgbxj5r-cardano-cli-test-cardano-cli-golden-x86_64-w64-mingw32-<IP_ADDRESS>.drv
└───/nix/store/rfijsxhycjb5lflvbz3ihplb4r5fhs3m-cardano-cli-exe-cardano-cli-<IP_ADDRESS>.drv
    └───/nix/store/8hfn8bijkps5grr9jlpac7al8n405d8j-cardano-crypto-class-lib-cardano-crypto-class-<IP_ADDRESS>.drv
        └───/nix/store/8nfavjdpfyhs87k75zd23dadq2y9888n-blst-03b5124.drv

Note that, since cardano-cli-exe-cardano-cli is build-tool for cardano-cli-test-cardano-cli-golden, cardano-cli-exe-cardano-cli is not cross-compiled. But somehow blst gets compiled with
/build.sh flavour=mingw64\n./build.sh -shared flavour=mingw64

which fails because the build is not running under mingw64.
I opened https://github.com/input-output-hk/iohk-nix/pull/551 hoping to fix this.

Hydra is all :green_circle: :partying_face:


cant update

got this in logs
[547446979360] Error updating thesillyhome addon: Can't install lcmchris1/aarch64-thesillyhome:1.0.2: 404 Client Error for http+docker://localhost/v1.41/images/create?tag=1.0.2&fromImage=lcmchris1%2Faarch64-thesillyhome&platform=linux%2Farm64: Not Found ("manifest for lcmchris1/aarch64-thesillyhome:1.0.2 not found: manifest unknown: manifest unknown")

[547446979360] Error updating thesillyhome addon: Can't install lcmchris1/aarch64-thesillyhome:1.0.2: 404 Client Error for http+docker://localhost/v1.41/images/create?tag=1.0.2&fromImage=lcmchris1%2Faarch64-thesillyhome&platform=linux%2Farm64: Not Found ("manifest for lcmchris1/aarch64-thesillyhome:1.0.2 not found: manifest unknown: manifest unknown")
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/hassio/update.py", line 167, in async_install
await async_update_addon(self.hass, slug=self._addon_slug, backup=backup)
File "/usr/src/homeassistant/homeassistant/components/hassio/handler.py", line 47, in _wrapper
raise HassioAPIError(data["message"])
homeassistant.components.hassio.handler.HassioAPIError: Can't install lcmchris1/aarch64-thesillyhome:1.0.2: 404 Client Error for http+docker://localhost/v1.41/images/create?tag=1.0.2&fromImage=lcmchris1%2Faarch64-thesillyhome&platform=linux%2Farm64: Not Found ("manifest for lcmchris1/aarch64-thesillyhome:1.0.2 not found: manifest unknown: manifest unknown")

The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 189, in handle_call_service
await hass.services.async_call(
File "/usr/src/homeassistant/homeassistant/core.py", line 1627, in async_call
task.result()
File "/usr/src/homeassistant/homeassistant/core.py", line 1664, in _execute_service
await cast(Callable[[ServiceCall], Awaitable[None]], handler.job.target)(
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 204, in handle_service
await service.entity_service_call(
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 677, in entity_service_call
future.result()  # pop exception if have
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 964, in async_request_call
await coro
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 714, in _handle_entity_call
await result
File "/usr/src/homeassistant/homeassistant/components/update/init.py", line 152, in async_install
await entity.async_install_with_progress(version, backup)
File "/usr/src/homeassistant/homeassistant/components/update/init.py", line 411, in async_install_with_progress
await self.async_install(version, backup)
File "/usr/src/homeassistant/homeassistant/components/hassio/update.py", line 169, in async_install
raise HomeAssistantError(f"Error updating {self.title}: {err}") from err
homeassistant.exceptions.HomeAssistantError: Error updating thesillyhome addon: Can't install lcmchris1/aarch64-thesillyhome:1.0.2: 404 Client Error for http+docker://localhost/v1.41/images/create?tag=1.0.2&fromImage=lcmchris1%2Faarch64-thesillyhome&platform=linux%2Farm64: Not Found ("manifest for lcmchris1/aarch64-thesillyhome:1.0.2 not found: manifest unknown: manifest unknown")

Thanks for raising this @lotohov . I was trying to create the new build that should fix you old issue but my laptop is struggling to handle the spanish heat. Promise a fix when I get back to UK by the end of the week!

Thinking about this now - I will try to maintain future changes in a dev repo (similar to the mqtt addon) just so that I won't break the build!

@lotohov this should now be working now!


Improve/fix styling of search results on mobile

Task: https://app.clickup.com/t/865cgycr0
Global search

Before:
After:
Design:

Search launched from TestNet

Before:
After:
Design:

Moreover, the search, paratime selector, and eco system aren't working for me here. I copied the string for multiple results but it still only shows my 1 results on mainnet and one (hidden) on testnet (/search?q=123). So I couldn't check the multiple results yet.

The problem is that we have no disabled emerald both on mainnet and testnet, so you won't have multiple results within mainnet. However, if I enable it for you in my dev build, then it shows:

The view/hide banner needs more space above and below the text

Would this be all right?


RelayContainer: Expected prop viewer to be supplied to App, but got undefined

Hello,
Im trying to run a simple app like the todo example but i get this
> RelayContainer: Expected prop viewer to be supplied to App, but got undefined
The strange thing is that from the server side i get the viewer property correctly:
  ...otherProps,  viewer:     { __dataID__: 'Vmlld2VyOjE=',      id: 'Vmlld2VyOjE=',      users: { __dataID__: 'client:14189082351_first(5)', edges: [Object] } }, ...moreProps
Here is My App Component:
import React from 'react'
import Relay from 'react-relay';

import get from 'lodash/get'
import last from 'lodash/last'
import merge from 'lodash/merge'
class App extends React.Component {
  render(){
    console.log('App props'+process.env.BROWSER,this.props)
    return (

          {get(this.props, 'viewer.id')}

    )
  }
}

export default Relay.createContainer(App, {
  fragments: {
    viewer: () => Relay.QL`
      fragment on Viewer {
        id,
        users(first: 5){
          edges{
            node{
              email,
              invite_token
            }
          }
        }
      }
    `,
  },
});

Here is the client-side render function:
const environment = new Relay.Environment();

  environment.injectNetworkLayer(new Relay.DefaultNetworkLayer('/graphql'));

  const data = JSON.parse(document.getElementById('preloadedData').textContent);

  IsomorphicRelay.injectPreparedData(environment, data);
  const rootElement =  document.getElementById('container');

  match({routes: routes({stores}), history: browserHistory }, (error, redirectLocation, renderProps) => {
    IsomorphicRouter.prepareInitialRender(environment, renderProps).then(props => {
      ReactDOM.render(<Router {...props} />, rootElement);
    });
  });

My route(s):
<Route path="/" component={App} queries={ViewerQuery}/>

And the ViewerQuery:
export default {
  viewer: () => Relay.QL`query { viewer }`,
};

Server reads correctly the app props, so i think that is something wrong in my client render function.

Confirming this issue, I'm facing the same error in my current application, where on backend it works but not on the client.
However, by downgrading the version of isomorphic-relay and isomorphic-relay-router to version 0.7.1 and 0.8.1 respectively, it does not throw this error.
My guess is that it might be due to version conflict, because I didn't see any possible breaking change introduced in the newer versions.

Ok so just found the solution,
I have checked the package.json of this modules. It uses
"react-relay": "0.9.3",
"react-router": "^2.3.0".
So i had to downgrade react router from 2.6.0 to 2.3.0 , and to strict the react-relay version(I'm not sure if this helps) from ^0.9.3 to 0.9.3 and then to remove the react-relay-router from my package.json.
Then it works.
I think that the author should add dependencies in this module.

Have the same problem with:
     "isomorphic-relay": "^0.7.3",
    "isomorphic-relay-router": "^0.8.3",
    "react-router": "^2.8.1",
    "react-router-relay": "^0.13.5",

You must not have react-router-relay in your dependencies if you already depend on isomorphic-relay-router, otherwise you might get module conflicts, especially if you are using NPM v2. Try to remove it from dependencies, delete your node_modules, and do clean install watching NPM warnings.
Generally, make sure you have only one copy of each of the following modules in your whole node_modules tree including nested modules:

babel-relay-plugin
isomorphic-relay
react
react-relay
react-router
react-router-relay

@denvned. Do you have any example that use React Component for router instead of raw object like this? https://github.com/denvned/isomorphic-relay-router/blob/287597565798f2bd7dee71757d9dae592144529a/examples/todo/src/routes.js

My current routes are written as:
import React from 'react';
import Relay from 'react-relay';
import useRelay from 'react-router-relay';
import { browserHistory, createMemoryHistory, Router, Route, applyRouterMiddleware } from 'react-router';
import ViewerQuery from 'client/queries/viewer';
import Todos from 'client/components/todos/index.jsx';
import StaticPage from 'client/components/static-page/index.jsx';

export const getClientHistory = () =>
  browserHistory;

export const getServerHistory = (url) =>
  createMemoryHistory(url);

export const getRoutes = (history) => (
  <Router
    history={history}
    render={applyRouterMiddleware(useRelay)}
    environment={Relay.Store}
  >
    <Route path="/" component={Todos} queries={ViewerQuery} />
    <Route path="/static-page" component={StaticPage} />
  </Router>
);

@hung-phan You can use createRoutes to convert a <Route> component tree to the corresponding route object. Here is an example: https://github.com/denvned/isomorphic-relay-boilerplate/blob/9ff4df83a9c2a8ae9068098204001618e960f31c/frontend/src/routes.js

After downgrade react-router, remove "react-router-relay", try example in main repo. I still have the same problem. Any idea? My repo https://github.com/hung-phan/koa-react-isomorphic/tree/features/relay

@hung-phan The problem in your app is that you are trying to pass <Router> instead of a route object to the match function. See my comment above with an example of correct usage.

BTW, you don't need to downgrade react-router.

ah, I tried that yesterday but it didn't work.
routes.jsx
export default createRoutes(
  <Route path="/">
    <IndexRoute component={Todos} queries={ViewerQuery} />
    <Route path="static-page" component={StaticPage} />
  </Route>
);

client.js
export function prepareInitialRender(routes, domNode) {
  match({ routes, history: browserHistory }, (error, redirectLocation, renderProps) => {
    if (error) {
      navigateTo('/500.html');
    } else if (redirectLocation) {
      navigateTo(redirectLocation.pathname + redirectLocation.search);
    } else if (renderProps) {
      IsomorphicRouter.prepareInitialRender(Relay.Store, renderProps)
        .then(props => {
          ReactDOM.render(<Router {...props} />, domNode);
        });
    } else {
      navigateTo('/404.html');
    }
  });
}

export default function (routes, domNode) {
  if (process.env.SERVER_RENDERING) {
    IsomorphicRelay.injectPreparedData(Relay.Store, window.prerenderData);
  }

  prepareInitialRender(routes, domNode);
}

@hung-phan That part of your code now looks correct.

Except it doesn't not work and has the same problem as the issue title.

@hung-phan Your project is complex, there are might be problems in other parts as well. I have no opportunity to debug it for you, but a minimal repo reproducing the error is welcome.

ok, thanks @denvned. Let me try to make it simple

https://github.com/hung-phan/koa-react-isomorphic/tree/minimal-branch. This is the repo after I remove all unnecessary code for debugging this error. It works for server rendering but getting error in client.

@hung-phan Wow, I imagined a minimal repro differently than that. By minimal I meant something that is more like the Todo example in this repository.

I updated the branch https://github.com/hung-phan/koa-react-isomorphic/tree/minimal-branch.

@hung-phan Can you reproduce it without recompose?

Updated. https://github.com/hung-phan/koa-react-isomorphic/tree/minimal-branch. Still have the same problem.

@hung-phan You need to remove history from the dependencies: https://github.com/hung-phan/koa-react-isomorphic/blob/329b856bf3991c95beb77e6996f87c877225a370/package.json#L10

Is that the solution?

@hung-phan You can try, and we will see. At least it removes the version conflict with history dependency in react-router.

Already removed and reinstalled, same problem.

@hung-phan Did you remove node_modules completely, and did fresh npm install? Did npm show any warnings?

@hung-phan Also, is the problem reproduced without webpack-isomorphic-tools?

Only this one
npm WARN deprecated<EMAIL_ADDRESS>Babel's CLI commands have been moved from the babel package to the babel-cli package
npm WARN deprecated<EMAIL_ADDRESS>This package is deprecated. Use Array.isArray.
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained. Upgrade to<EMAIL_ADDRESS>npm WARN deprecated<EMAIL_ADDRESS>graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to<EMAIL_ADDRESS>as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN deprecated<EMAIL_ADDRESS>This package is deprecated. Use Object.assign.
npm WARN<EMAIL_ADDRESS>requires a peer of estraverse@* but none was installed.

I don't think it the problem

Yes, I can remove it all but still. the problem is the client not the server

@hung-phan But you use webpack-isomorphic-tools when packing client bundle.

Removed webpack-isomorphic-tools. Still have the same problem.

@hung-phan Can you remove everything else not required for reproducing this error (webpack plugins and loaders, devDependencies, babel transforms, etc), and update your minimal-branch?

@hung-phan Also can you create a parallel minimal branch that uses react-router-relay instead of isomorphic-router-relay, to make sure the error occurs only in isomorphic-router-relay, and not in react-router-relay.

Ok, @denvned

https://github.com/hung-phan/koa-react-isomorphic/tree/minimal-branch and https://github.com/hung-phan/koa-react-isomorphic/tree/minimal-branch-react-relay-router

@hung-phan Change this to the following:
<Router
  environment={Relay.Store}
  history={browserHistory}
  render={applyRouterMiddleware(useRelay)}
  routes={routes}
/>

And check that the react-router-relay branch does not produce the error.

Updated. minimal-branch-react-relay-router doesn't throw the error.

@hung-phan Thank you. I think we are close. Please also disable HMR/hot reload, remove common entry point from here, and remove the following plugins from your webpack configs and check again:

webpack.optimize.AggressiveMergingPlugin,
webpack.optimize.OccurrenceOrderPlugin,
webpack.NamedModulesPlugin,
webpack.optimize.CommonsChunkPlugin,
webpack.HotModuleReplacementPlugin,
webpack.NoErrorsPlugin

Updated

@hung-phan Does minimal-branch after the changes still produces error, and minimal-branch-react-relay-router does not?

Yes

I have the same "prop not supplied" problem using kyt-starter-universal. Looking forward to see how this issue will unfold. If this does not resolve my problem, I'll open another issue.

@hung-phan I tried to debug your app, and found that your resulting app.js bundle contains two copies of the same modules from react-router-relay, one from react-router-relay/lib, and the other from react-router-relay/es. For example, there are two copies of RelayRouterContext, and QueryAggregator... The reason is that webpack 2 resolves react-router-relay to react-router-relay/es/index.js while isomorphic-relay-router imports also some internals from react-router-relay/lib, so we end up using two builds of react-router-relay.
I think I resolved this in isomorphic-relay-router v0.8.4, can you try it?
@arvigeus Probably you are facing the same issue as you are using webpack 2 too, so you can also try v0.8.4.

ok, Thanks @denvned. This info is very helpful

It worked. @denvned, you have no idea how much this means for me. I was stuck with this problem for a week.  Thank you!

Indeed it did @arvigeus .So the issue was with webpack 2.... The update is brilliant, thanks @denvned a lot! YEAH!

Thank you to @hung-phan for cooperation and patience.

😅 , thanks @denvned.


updated required version for stateful_config module

`
Terraform will perform the following actions:
google_compute_region_per_instance_config.this[0] will be created

resource "google_compute_region_per_instance_config" "this" {

id                               = (known after apply)

minimal_action                   = "NONE"

most_disruptive_allowed_action   = "REPLACE"

name                             = "name1"

project                          = "qa-7743d3a8"

region                           = "us-central1"

region_instance_group_manager    = "testing"

remove_instance_state_on_destroy = false

preserved_state {
}
}

google_compute_region_per_instance_config.this[1] will be created

resource "google_compute_region_per_instance_config" "this" {

id                               = (known after apply)

minimal_action                   = "NONE"

most_disruptive_allowed_action   = "REPLACE"

name                             = "name2"

project                          = "qa-7743d3a8"

region                           = "us-central1"

region_instance_group_manager    = "testing"

remove_instance_state_on_destroy = false

preserved_state {
}
}

google_compute_region_per_instance_config.this[2] will be created

resource "google_compute_region_per_instance_config" "this" {

id                               = (known after apply)

minimal_action                   = "NONE"

most_disruptive_allowed_action   = "REPLACE"

name                             = "name3"

project                          = "qa-7743d3a8"

region                           = "us-central1"

region_instance_group_manager    = "testing"

remove_instance_state_on_destroy = false

preserved_state {
}
}

Plan: 3 to add, 0 to change, 0 to destroy.
Changes to Outputs:

instance_names = [

"name1",
"name2",
"name3",
]
`


Unit tests across all SDKs

Description
All SDKs here currently have no/next-to-no meaningful unit tests. These should be added across all supported SDKs
Motivation

All the usual reasons for unit testing, too many to list here
User confidence in adopting Configu's SDKs
Having (essentially) the same unit tests across SDKs enables us to ensure consistency across different SDKs

Additional context
Unit test support is already added in the CI pipelines :rocket:

@rannn505 is it better to keep this issue open until we also have unit testing in place for the Go SDK (not sure how well tested the TS sdks are, and whether they also need tests added)


Added 점프 투 장고 in Django section

Hacktoberfest notes:

due to volume of submissions, we may not be able to review PRs that do not pass tests and do not have informative titles.
please read our contributing guidelines
be sure to check the output of Travis-CI for linter errors
if this is your first open source contribution, make sure it's not your last!

What does this PR do?
Add Resource(s) | Remove Resource(s) | Add info | Improve Repo
Add Resource.
For resources
Description
Korean Django book of 박응용(as known as author of "점프 투 파이썬").
Why is this valuable (or not)?
Because it is korean Django book with nice practices.
How do we know it's really free?
You can see the CC sign in book site.
For book lists, is it a book? For course lists, is it a course? etc.
It is a book.
Checklist:

[x] Not a duplicate
[x] Included author(s) if appropriate
[x] Lists are in alphabetical order
[x] Needed indications added (PDF, access notes, under construction)

(for some reason linter din't run so I restarted.

Thanks, and welcome to free-programming-books!


Unable to try_reclaim(..) a BytesMut allocation

bytes_mut.reserve(..) makes the guarantee that the underlying allocation will be reclaimed when bytes_mut is the only remaining handle to it. However, when it isn't the only remaining handle, new space is allocated and the handle to the old allocation is discarded.
BytesMut should offer a method to request that the underlying allocation be reclaimed without discarding the old allocation when the attempt fails. Something along the lines of the following.
impl BytesMut {
  /// Attempts to reclaim the underlying allocation.
  ///
  /// The attempt will succeed iff this is the last remaining handle
  /// to the allocation.
  ///
  /// When the attempt succeeds, an empty `BytesMut` with the full
  /// capacity of the allocation is returned. Otherwise, the original
  /// handle is returned.
  pub fn try_reclaim(self) -> Result<Self, Self>;
}

I'd be happy to implement this proposal and file a PR for it.

I think this is a pretty decent idea.


Fixes for tests in the German culture.

I already mentioned that the tests don't run properly because of culture issues.
I fixed some of them in this pull requests.
The most important one is that I specify the invariant culture for all all ChameleonForms.Tests tests. That fixes all the broken tests of that kind for me.
I also fixed some issues I have with the acceptance tests, but not all.
One problem is that it's not easy to find a DateTime format string that survives a serialization-parsing-roundtrip in all cultures. The "tt" specifier doesn't exist in the German culture (and neither does it in the invariant culture), so I changed the example format to a 24h clock format.
There is a remaining issue unobtrusive javascript validation and cultures (which I don't use in my own apps). The javascript on the example forms don't validate because it can't parse decimals (as the dot is a comma in German numbers). Maybe I find a fix for this later, but right now unobtrusive validation isn't a priority for me.

Thanks


Sightings error in Pattern D↑

The 3rd one from last row in Pattern D↑, show as attached

Finally fixed now, likely due to out of date data. Issue is now resolved by commit ca7ec11.


Different error code for every error

This PR fixes issue with repeating error code 400 (one from celebrate and one from some other error) in each request. Tests has been updated to request new error codes.

I want #62 to be merged into main first and then into this before a review since there is a bit of an overlap here I think.


Add SPDX tag-value format object

Closes #590
This PR ports the last of the package presenter objects to a format object (with encoding only, no decoder or validator). Since this is the last object there is a little more clean up work that was additionally done:

Swaps the presenter utils to the formats utils in the cmd package.
Removes the presenter package altogether, swapping for a single global definition

Future work:

Remove the power-user presenter by combining it with the packages format object (related to #555 , #516, and #554)

So happy this is here!


[Superfund]: Github checks failing

The test_e2e (us_epa.superfund.site_and_funding_status.process_sites_test.ProcessTest) test seems to be failing for PR #648
Build Link

@shifucun , The build error points to the KeyError: 'placeCoordinates'. This error is when we resolve location of superfund sites specified through latitude and longitude. Is there a change in the recon API's response?

Do you have a specific REST API url for this query?

The specific url I have used in the script is  "https://autopush.recon.datacommons.org/coordinate/resolve" reference

@shifucun Thanks for the fix.
The tests are now passing.
Closing this issue.


Pull repositories from Gitlab

See https://docs.gitlab.com/ee/api/groups.html#list-a-groups-projects

Also see https://github.com/DISIC/politique-de-contribution-open-source/issues/162

Implemented! Here are the fields always missing for Gitlab repositories because they're not exposed by the API: est_fork, page_accueil, licence, langage

Licences and langages can be pulled, but it requires 2 calls per project 😢

Licence (with flag) https://docs.gitlab.com/ee/api/projects.html#get-single-project
Languages https://docs.gitlab.com/ee/api/projects.html#languages


Allow partners to view, update their organization details & submit it for approval

Summary
Let's implement the ability for partners to update their organization details within diaperbase. This is a step necessary for them to be approved to make requests.
Here are the pictures of the feature for viewing & editing:

Things to Consider

Refer to partner's repo for information on how this is built. (Copy & paste is encouraged)
Some fields/sections may not need to appear depending on what the organization setup.

Criteria for Completion

[ ] As a partner user, I can view organization's information
[ ] As a partner user, I can update my organization's information so that I can submit it for approval to make requests.
[ ] As a partner user, I can submit my form for approval so that I can get approved to make more requests to the diaperbank.
[ ] Any necessary specs needed

Duplicate of https://github.com/rubyforgood/diaper/issues/2164. Closing


Add sidenav Accessibility improvements

Bug/issue #, if applicable: 88194935
Summary
This PR improves the AX on the sidebar
Dependencies
https://github.com/apple/swift-docc-render/pull/51
Testing
Make sure you download and unzip the .doccarchive - SlothCreator.doccarchive.zip
Steps:

run VUE_APP_DEV_SERVER_PROXY=/path/to/SlothCreator.doccarchive npm run serve
Visit http://localhost:8080/documentation/slothcreator
Try using Tabbing or VO

Checklist
Make sure you check off the following items. If they cannot be completed, provide a reason.

[x] Added tests
[x] Ran npm test, and it succeeded
[x] Updated documentation if necessary

Is it expected that the VO does not start at the item/page we are currently on?
For example, I was expecting VO to start on the sidenav at Sloth.Color, since this is the current component I'm on. However, it starts at the init under Creating a Sloth. If it starts on top of a page, I would have expected to start on  Meet SlothCreator and Getting started with Sloths. Is this a bug or pending future improvement?

I've not been able to reproduce this, sorry :(

The VO is not working on the section titles like "Essentials" and "Creating a Sloth"

That's because you are navigating through tabbing which only selects links. If you
Screen Recording 2022-02-21 at 16.34.33.mov.zip
navigate using "Control + option + shift + arrow keys" you will be accessing also the text that are not links. I attach a video of it.

For #1:
sidebar AX.mov.zip
In the screen recording, at first I was pressing the down arrow; And then after I refreshed the page, I was pressing tab.
I tested with another page that is further down the tree (you would have to scroll up on the side bar to see the very top of the tree). In this scenario, the VO still starts at the very top of the tree, not just the top of what's visible on the page at the moment. I'm not sure if that's the intended behavior. I can see how starting from the top could make sense, because we are navigating through all the links on the page, and technically the first link is the beginning of the tree. But that doesn't seem like the best user experience. What do you think?

In the screen recording, at first I was pressing the down arrow; And then after I refreshed the page, I was pressing tab.

This behaviour when tabbing on Safari is expecting. Its documentation says "Tab also highlights buttons and other controls if “Highlight the next field or pop-up menu on a web page", which includes buttons. While links are only highlighted when using "Option-Tab". You can read more here https://support.apple.com/en-gb/guide/safari/cpsh003/mac

I tested with another page that is further down the tree (you would have to scroll up on the side bar to see the very top of the tree). In this scenario, the VO still starts at the very top of the tree, not just the top of what's visible on the page at the moment. I'm not sure if that's the intended behavior. I can see how starting from the top could make sense, because we are navigating through all the links on the page, and technically the first link is the beginning of the tree. But that doesn't seem like the best user experience. What do you think?

It really depends on how you navigate with VO but this issue should be address in this other radar instead: rdar://89153252

I am going to try to move this PR to be against the main apple/swift-docc-render repo since the base branch for this (dhristov/add-sidenav) has since been merged.

Looks like it won't let me switch the base branch outside of this repo. @dobromir-hristov we may need to re-open a new PR for this in the apple repo when you get back.

Approving this PR, since as Marina mentioned, improvements will be addressed in rdar://89153252 instead.

Looks like it won't let me switch the base branch outside of this repo. @dobromir-hristov we may need to re-open a new PR for this in the apple repo when you get back.

I think it's because we don't have write access to Dobri's repo. Marina should be able to rebase and merge tomorrow, since she was added as a collaborator on Dobri's fork.

He gave me write access before he left, so I can rebase and push commits to this PR—however, I don't think I can switch this to anything outside of the fork without opening a new PR. You're more than welcome to recreate the PR using the rebased branch though.

We cannot change base branches across forks, that's a GitHub limitation.
Let me know, if I should just reopen a new one, or you do it instead :)

Thanks everyone! I opened this new PR to be able to change the base branch :) https://github.com/apple/swift-docc-render/pull/55


Transliteration search

Add transliteration search, based on https://github.com/ShabadOS/database/issues/809

Duplicate of #397.


mpirun example fails

As reported on the list, the mpirun example from http://singularity.lbl.gov/#hpc fails for me.  It's en el6 host with a recent trunk singularity and any of OMPI 1.6 (our native one), 1.8, or 1.10.  I used a cut-and-paste from the example (fixed for non-ascii).  The ranks all fail with:
    ompi_mpi_init: ompi_rte_init failed
    --> Returned "(null)" (-43) instead of "Success" (0)

that is correct - you need the OMPI master, or release 2.1 once that occurs (probably this fall?)

Thanks for the clarification Ralph!

This needs to be clarified in the documentation, especially as that
wasn't what I understood before, though I didn't see how it could work.
It could use explanation of what the integration does too.

I agree and will update/clarify the documentation. Reopening issue as a reminder to do that.

Maybe note that it will work with compatible MPIs (including older OMPI) inside and outside the container, at least with no pid namespacing.
Is there some way to use the container's mpirun to start the container MPI processes?  I've forgotten what went wrong when I tried.

It is possible to use the container's mpirun to start the contained MPI process... BUT..... Then each container has to have ssh and sshd with sshd's running within the container (or having the scheduler automatically spawn the orted processes within the container). Starting the MPI process from within the container increases complexities significantly without gaining an equal amount... As a matter of fact, I don't think it gains anything, and may even loose more then it gains. -- This will make a good FAQ as well.
I added some verbiage on the HPC page at the bottom noting the OMPI version used.

BTW, I added an FAQ about the mpirun inside/outside container. Thanks!


Favicon

I changed the favicon since it was using the angular favicon
Here is a preview:

Looks good! Two quick things, don't forget to change line 8 in index.html to <link rel="icon" type="image/png" href="penda.png">, and don't forget to add "src/penda.png", to the other assets in the same file.

Don't forget to change the type to type="image/png" in the index.html file.


X509Certificate2::ctor(byte[]) works differently on Windows/Linux

Want to process some incoming certificates encoded in PEM format. On windows, if I use:
new X509Certificate2(Encoding.ASCII.GetBytes(pemCertString));
that works fine. Actually, windows can figure out different formats, it can be a base64 encoded certificate without the PEM frame or the DER certificate itself, it can process whatever the passed byte array contains
on Linux it seems much more picky and the constructor that gets a byte[], only accepts a DER certificate. Now what I can do is to trim the PEM frame, base64 decode the remaining data, and pass the resulting DER certificate to the constructor.
Is there any more elegant solution than the following:
'
const string PemHeader = "-----BEGIN CERTIFICATE-----";
const string PemFooter = "-----END CERTIFICATE-----";
var certificateContent = Convert.FromBase64String(TrimPemFrame(encodedCertificate));
var certificate = new X509Certificate2(certificateContent);
static string TrimPemFrame(string pemEncoded)
{
var result = pemEncoded.Trim();
if (result.StartsWith(PemHeader))
{
result = result.Substring(PemHeader.Length);
}
if (result.EndsWith(PemFooter))
{
result = result.Substring(0, result.Length - PemFooter.Length);
}
return result;
}
`

The constructor on Linux accepts ASCII-encoded PEM-encoded certificates as well as DER-encoded certificates and PFX files.  It doesn't accept unarmored base64, and currently doesn't understand processing PKCS#7 the same way that the Windows constructor does.

@bartonjs So you are saying that if I have a PEM certificate like this:
    private static readonly string ThumbprintTestCert =

"-----BEGIN CERTIFICATE-----" +
"MIICHDCCAX6gAwIBAgIJANqy0HwrEJqpMAoGCCqGSM49BAMCMB8xHTAbBgNVBAMM" +
.... / removed some lines
"K3X3YDtLgTQA01umm/XY5Q==" +
"-----END CERTIFICATE-----";
and I use it as:
var cer = new X509Certificate2(Encoding.ASCII.GetBytes(ThumbprintTestCert));
It should work? Unfortunately, I am getting the following error:
Unhandled exception. Interop+Crypto+OpenSslCryptographicException: error:0D07803A:asn1 encoding routines:asn1_item_embed_d2i:nested asn1 error
at Internal.Cryptography.Pal.OpenSslX509CertificateReader.FromBlob(Byte[] rawData, SafePasswordHandle password, X509KeyStorageFlags keyStorageFlags)
at System.Security.Cryptography.X509Certificates.X509Certificate..ctor(Byte[] data)
at System.Security.Cryptography.X509Certificates.X509Certificate2..ctor(Byte[] rawData)
at CertParse.Program.Main(String[] args) in /mnt/d/dev/QuickTests/CertParse/Program.cs:line 29
The same error, if I remove the begin/end certificate lines, so I have the base64 encoded certificate. It works only on linux (I try with WSL right now), if I manually base64 decode the string and pass the received DER format to the constructor, like in the example in my first post.

Do you have the required newlines at the end of -----BEGIN CERTIFICATE----- and before -----END CERTIFICATE-----?
I don't believe OpenSSL's PEM parser cares about newlines after every 64 characters of base64 text, but I believe it does care about those two mandatory newlines.
-----BEGIN CERTIFICATE-----
base64
-----END CERTIFICATE-----

@bartonjs yes, that was it, the newlines! Thanks, closing it now.

@bartonjs is there a plan to make this class work consistently across platforms?


Can't import Bestiary 3 - Dimetrodon (Dinosaur)

Can't import statblock:
Dimetrodon (Dinosaur)      CR 3
XP 800
Male dimetrodon (Pathfinder RPG Bestiary 3 78)
N Large animal
Init +6; Senses low-light vision, scent; Perception +6
Defense
AC 14, touch 11, flat-footed 12 (+2 Dex, +3 natural, -1 size)
hp 34 (4d8+16)
Fort +8, Ref +6, Will +2
Offense
Speed 30 ft.
Melee bite +8 (1d8+7/19-20)
Space 10 ft.; Reach 5 ft.
Statistics
Str 20, Dex 15, Con 18, Int 1, Wis 12, Cha 3
Base Atk +3; CMB +9; CMD 21 (25 vs. trip)
Feats Improved Initiative, Weapon Focus (bite)
Skills Perception +6, Stealth +3
Special Abilities
Low-Light Vision See twice as far as a human in dim light, distinguishing color and detail.
Scent (Ex) Detect opponents within 15+ ft. by sense of smell.

Used your latest module that was available as of this afternoon at about 2:30pm.  I used Hero Lab to produce this statblock. For greater accuracy, you might want to use one of the online resources. Hero Lab can truncate some of the text. All the other statblocks from Bestiary 3 imported -- a total of more than 86% imported!


feat: use named volumes for database backup

What kind of change does this PR introduce?
feature
What is the current behavior?
Please link any relevant issues here.
What is the new behavior?
Feel free to include screenshots if it includes visual changes.
Additional context
Add any other context or screenshots.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

47 of 61 (77.05%)  changed or added relevant lines in 5 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.2%) to 63.023%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

internal/db/start/start.go
9
14
64.29%

internal/utils/docker.go
13
22
59.09%

Totals

Change from base Build<PHONE_NUMBER>:
0.2%

Covered Lines:
3569

Relevant Lines:
5663

💛  - Coveralls


[Bug] Can't find Themes after switching to Steam Beta Branchs

Before Reporting

[X] I found no existing issues matching my bug
[X] My issue is not caused by the Millennium interface inside Steam (Themes, Plugins & Update Panel). If it is, make a issue report in this repo.
[X] My issue is not caused by a theme

Describe the Bug
I was switching to the Family Management Beta Branch to get the new version before. After that the Millennium couldn't find any themes I installed before, even I tried to switch off the Beta Branch, reinstall the Millennium, it just couldn't find themes anymore
Expected Behavior
The Millennium should find themes even after switching to Beta Branch (Family Management one here specifically)?
Steps To Reproduce

Install the Millennium
Switching to Beta Branch (Family Management one here)
Check Theme panel in the setting
See error

Operating System
Windows
Anything else?
No response

Oh wait I just realized the way load themes was changed in new version, nvm


Use char instead of const char* when appending a single character to wstrings

Problem Statement
Calculator has many instances where it builds strings a single character at a time.  However, there are many instances where that single character is appended using a const char* which is not as efficient as appending just a char since using a const char* assumes there could be 0 or more characters where using a char will always be a single character.
Evidence or User Insights
Compiler explorer example showing inefficiency of using const char* version over char version of wstring's operator +=.
Proposal
Update these instances to use the char overload.
Goals
Simple way to reduce binary size and get a small performance win.
Requested Assignment
If possible, I would like to implement this.

This is your friendly Microsoft Issue Bot. I've seen this issue come in and have gone to tell a human about it.


Update Fable to 1.2

This also tries to make the packages folder smaller by using new Paket storage:none feature except for the netframework groups

Sometimes we get this error for the UI Tests, on Travis and also on my system (macOS):
[13:51:46 ERR] client tests/sound check - server is online errored in 00:00:12.4560000 <Expecto>
canopy.types+CanopyWaitForException: Condition not met in given amount of time. If you want to increase the time, put compareTimeout <- 10.0 anywhere before a test to increase the timeout
waitFor condition failed to become true in 10.0 seconds

I did try to add compareTimeout <- 20.0 right before the tests/sound check but it didn't help on my machine (actually with 30.0 the tests just hanged). Any idea on how this can be fixed? @forki @haf

Hasn't phantomJS been EOLed? Headless chrome or the new headless FF?

@haf That probably belongs to another PR ;) I'll fix this one for now :+1:


Executor revamp take 2

This is another stab at the executor model revamp. As before, the main
idea is that a "task" is a future paired with an executor. However, the
implementation is now factored much more cleanly, and the executors
themselves implement a direct spawn method. Other changes:

Centralizes around the Task type, which replaces TaskHandle.

Provides two task execution models: via an Executor (which is
generally one or more threads together with a queue of tasks to
execute) or by blocking on the current thread (via ThreadTask).

Removes the forget method. Instead, futures will always be run using
one of the above execution models. The core futures library provides
only the wait executor, which executes the future to completion on
the current thread via ThreadTask.

Removes the old TaskData type, which is no longer useful in
a world where futures are not required to be Send.

Add task-local data using TypeMap.

Introduces the notion of an "unpark event", which is a way to pass
information from an event source back to the task upon unpark. The
information is passed by inserting IDs into concurrent sets prior to
wakeup. This works via a scoped API, with_unpark_event, which
decorates the current task so that park will include the desired
unpark events.

A new catch_unwind combinator.

Note: the task-local API is currently only exposed via task::with_local_data (and _mut), which exposes the entire table. We'll probably want to provide future combinators to access the local data, but the core APIs here are enough to build those out of tree.
I also don't have tests for the task-local data yet; ran out of time.

As far as rolling this out in tokio-core, I'm not going to have time to do that, but @alexcrichton I think it's quite straightforward if you aren't trying to add a lifetime to the event loop. Given that my previous experiment showed that this was possible, I think we should punt for now and just make the minimal change needed to switch the event loop over to this executor model.

Final note: I didn't bother with the yield stuff on this take, because we should consider it with the potential larger revamp of Poll.

Update: added TaskRc back.


[QUESTION] Connection Error: Internal error during decryption: Tag mismatch!

Question
I randomly experience connection failures when trying to establish secure connection to MS SQL Server instance running in AWS environment. Initially, my connection string was like this:
jdbc:sqlserver://:1433;databaseName=;trustServerCertificate=false
In my first attempt to resolve the problem, I’ve changed it to be like this:
jdbc:sqlserver://:1433;encrypt=true;trustServerCertificate=false;databaseName=
I’m not sure if parameter order makes any difference or it is necessary to set ‘encrypt’ explicitly. I did my changes to make the connection string to be as similar as possible to examples that can be found in Microsoft’s online documentation. Additionally, I’ve found this issue:
It’s marked as resolved, but I still implemented my changes to be on the safe side. Unfortunately, all connection string modifications didn’t make any difference. Following that, I made further changes to my connection string to make it like this:
jdbc:sqlserver://:1433;encrypt=true;trustServerCertificate=false;sslProtocol=TLSv1.2;databaseName=
Unfortunately, the problem is still there. The following exception is thrown each time connection attempt fails:
com.microsoft.sqlserver.jdbc.SQLServerException: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "Internal error during decryption:  Tag mismatch! ". ClientConnectionId:8e8c7663-6299-4a05-8168-e67b1588444d
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:3806)
at com.microsoft.sqlserver.jdbc.TDSChannel.enableSSL(IOBuffer.java:1906)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:3329)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:2950)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectInternal(SQLServerConnection.java:2790)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:1663)
at com.microsoft.sqlserver.jdbc.SQLServerDataSource.getConnectionInternal(SQLServerDataSource.java:1385)
at com.microsoft.sqlserver.jdbc.SQLServerDataSource.getConnection(SQLServerDataSource.java:97)
at asi.utility.DbMgr.makeConnection(DbMgr.java:58)
at asi.edms.data.DataDocSearch.getPhysicalPath(DataDocSearch.java:768)
at asi.edms.data.DataMgr.getPhysicalName(DataMgr.java:1889)
at asi.edmsapi.EdmsFileManager.getPhysicalName(EdmsFileManager.java:1532)
at com.pb.engageone.server.batch.na.tdsextract.core.repository.oe.RepositoryImpl.getFilePath(RepositoryImpl.java:61)
at com.pb.engageone.server.batch.na.tdsextract.api.RepositoryApi.getTemplateInformation(RepositoryApi.java:90)
at com.pb.engageone.server.batch.na.tdsextract.api.RepositoryApi.getTemplateInformation(RepositoryApi.java:199)
at com.pb.engageone.server.batch.na.dao.CachingTemplateDaoEjb.retrieveTemplate(CachingTemplateDaoEjb.java:46)
at com.pb.engageone.server.batch.na.dao.CachingTemplateDaoEjb.retrieveTemplate(CachingTemplateDaoEjb.java:32)
at com.pb.engageone.server.batch.na.gather.processor.BatchItemPreProcessor.process(BatchItemPreProcessor.java:305)
at com.pb.engageone.server.batch.na.gather.processor.CompositeBatchItemProcessor.process(CompositeBatchItemProcessor.java:28)
at com.pb.engageone.server.batch.na.gather.processor.BatchItemProcessorWorker.work(BatchItemProcessorWorker.java:79)
at com.pb.engageone.server.batch.na.ThreadManager$WorkerThread.run(ThreadManager.java:214)
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Internal error during decryption:  Tag mismatch!
at com.microsoft.sqlserver.jdbc.SecureStringUtil.getDecryptedChars(SecureStringUtil.java:146)
at com.microsoft.sqlserver.jdbc.TDSChannel.enableSSL(IOBuffer.java:1695)
... 19 common frames omitted
All my tests have been performed using the latest mssql-jdbc-11.2.1.jre11.jar file. Similar problem is observed with mssql-jdbc-11.2.0.jre11.jar, but it looks the problem is gone if I downgrade to mssql-jdbc-10.2.1.jre11.jar. I’m now wondering if my connection string is wrong (something is missing?) or maybe I’m suffering from a bug that’s only present from version 11.2.0 onwards.
Can someone help with that?
Regards,
Andrzej
Relevant Issues and Pull Requests
https://github.com/microsoft/mssql-jdbc/issues/1853
https://github.com/Microsoft/mssql-jdbc/issues/879

Hi @AndrzejHeller,
We're changing the title to help us find the issue later.
I see you've added TLS1.2 to the connection string, can you try with TLS1 (sslProtocol=TLSv1)? Additionally, can you try enabling logging on FINER level and pasting those logs here? You can find the information for that here. Finally, what version of Java are you using (8,11,17, or 19) and what vendor (Oracle, Zulu, etc.)?

Hello @Jeffery-Wasty ,
Thank you for your prompt response.
Intermittent test failures are experienced in our test environments when running automated tests on Linux VM in AWS infrastructure. I reviewed all the stacks and can confirm that failures were experienced for the following Java versions:
openjdk version "<IP_ADDRESS>" 2020-11-04 LTS
OpenJDK Runtime Environment Corretto-<IP_ADDRESS>.1 (build <IP_ADDRESS>+12-LTS)
OpenJDK 64-Bit Server VM Corretto-<IP_ADDRESS>.1 (build <IP_ADDRESS>+12-LTS, mixed mode)
and
openjdk version "11.0.9" 2020-10-20
OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.9+11)
OpenJDK 64-Bit Server VM AdoptOpenJDK (build 11.0.9+11, mixed mode)
We use Adopt, Corretto and Oracle Java in our test environments, I think it’s a coincidence that I didn’t find any failures for Oracle Java.
I followed your suggestion, changed TLS version to TLSv1 and run the tests again. It didn’t make any difference, as I experienced the same problem again. Enabling additional logging requires more work on our side, I’ll supply those logs once they become available – hopefully later today or tomorrow.

Thanks for testing TLSv1, and the versions for your JDK. I see why you added to the connection string but adding encrypt=true can cause additional issues. Can you try the following connection string - jdbc:sqlserver://:1433;databaseName=;trustServerCertificate=true?
Has the problem been the same throughout the connection string changes? That is, do you have the error with jdbc:sqlserver://:1433;encrypt=true;trustServerCertificate=false;sslProtocol=TLSv1.2;databaseName= as you did with jdbc:sqlserver://:1433;databaseName=;trustServerCertificate=false?

Are you using the trustStorePassword connection property? This looks like a problem with our password obfuscation code rather. I know that the Tag mismatch! error happens when the secret used to encrypt the password is different during decryption.

@Jeffery-Wasty ,
When I observed the issue for the very first time, my connection string was like this:
jdbc:sqlserver://<host name>:1433;databaseName=<database name>;trustServerCertificate=false
I didn’t provide ‘encrypt’ parameter, as I assumed it’s not necessary if we want ‘encrypt=true’. Later, I checked it with such connection string:
jdbc:sqlserver://<host name>:1433;encrypt=true;trustServerCertificate=false;databaseName=<database name>
then provided TLS version explicitly:
jdbc:sqlserver://<host name>:1433;encrypt=true;trustServerCertificate=false;sslProtocol=TLSv1.2;databaseName=<database name>
and (following your suggestion) with TLSv1 instead of TLSv1.2.
I’m now running my tests again with connection string like below:
jdbc:sqlserver://<host name>:1433;trustServerCertificate=false;databaseName=<database name>
It’s very similar to the first, the only difference is order of parameters. I’m capturing logs you requested, hopefully they will contain something useful.

@tkyc
I've never tried providing trustStorePassword property in my connection string. Is there any other property that could be missing in my connection string?

@Jeffery-Wasty ,
Two example logs created the way you had suggested can be downloaded from here: https://drive.google.com/drive/folders/1t8OQqyLcB-vED2HlDtkPyKbyufcGRzCG?usp=sharing

@AndrzejHeller So the trustStorePassword is used to check the data in the truststore (the path to certificate truststore file). If you aren't using truststore then trustStorePassword isn't needed. By default, if truststore and trustStorePassword isn't set, the driver defaults to use javax.net.ssl.trustStore and javax.net.ssl.trustStorePassword.

Please try trustServerCertificate=true. In the examples you gave it is set to false each time.

@Jeffery-Wasty
I can run tests with trustServerCertificate set to TRUE, no problem with that. We set it to FALSE because server certificate DN is not provided. We only set trustServerCertificate to TRUE if server certificate DN is provided.
But if my configuration is not right, why is it not failing for each connection attempt? Multiple connections are created during each execution of our tests and only very few of those attempts fail.

Hey @AndrzejHeller, I believe there is a race condition in our password obfuscation code. I've attached a driver jar with the fix. Could you test it out and see if it corrects your problem? Thanks.
mssql-jdbc.zip

Hello @tkyc ,
Of course I can test the driver you've attached. I'll run my tests and let you know if the problem is still present or not.

@tkyc ,
I’ve executed our tests three times and received the same errors for each run, something like this is visible in log:
[2022-11-01 16:45:43,225 | FINE | container | com.microsoft.sqlserver.jdbc.SQLServerConnection prelogin] ConnectionID:30 ClientConnectionId: bda318c6-406b-4835-998b-0de696f78e05 Server returned major version:15
[2022-11-01 16:45:43,225 | FINER | container | com.microsoft.sqlserver.jdbc.SQLServerConnection prelogin] ConnectionID:30 ClientConnectionId: bda318c6-406b-4835-998b-0de696f78e05 Negotiated encryption level:ON
[2022-11-01 16:45:43,225 | FINER | container | com.microsoft.sqlserver.jdbc.SQLServerConnection prelogin] ConnectionID:30 ClientConnectionId: bda318c6-406b-4835-998b-0de696f78e05 Ignoring prelogin response option:5
[2022-11-01 16:45:43,225 | FINER | container | com.microsoft.sqlserver.jdbc.TDSChannel enableSSL] TDSChannel (ConnectionID:30) Enabling SSL...
[2022-11-01 16:45:43,225 | FINER | container | com.microsoft.sqlserver.jdbc.TDSChannel enableSSL] TDSChannel (ConnectionID:30) SSL handshake will validate server certificate
[2022-11-01 16:45:43,225 | FINEST | container | com.microsoft.sqlserver.jdbc.TDSChannel enableSSL] TDSChannel (ConnectionID:30) Finding key store interface
[2022-11-01 16:45:43,225 | FINEST | container | com.microsoft.sqlserver.jdbc.TDSChannel loadTrustStore] TDSChannel (ConnectionID:30) Opening specified trust store: /mnt/active-drive/_tls/pbeo_net_truststore.pfx
[2022-11-01 16:45:43,225 | FINEST | container | com.microsoft.sqlserver.jdbc.TDSChannel enableSSL] TDSChannel (ConnectionID:30) Loading key store
[2022-11-01 16:45:43,226 | FINEST | container | com.microsoft.sqlserver.jdbc.TDSChannel enableSSL] TDSChannel (ConnectionID:29) Loading key store
[2022-11-01 16:45:43,231 | FINE | container | com.microsoft.sqlserver.jdbc.SQLServerException logException] *** SQLException:com.microsoft.sqlserver.jdbc.SecureStringUtil@31376c83 com.microsoft.sqlserver.jdbc.SQLServerException: Internal error during decryption:  Tag mismatch!  Internal error during decryption:  Tag mismatch!
[2022-11-01 16:45:43,231 | FINER | container | com.microsoft.sqlserver.jdbc.TDSChannel enableSSL] Internal error during decryption:  Tag mismatch!
[2022-11-01 16:45:43,244 | FINER | container | com.microsoft.sqlserver.jdbc.TDSChannel enableSSL] java.security path: /usr/java/javaEO/lib/security
Security providers: [SUN version 11, SunRsaSign version 11, SunEC version 11, SunJSSE version 11, SunJCE version 11, SunJGSS version 11, SunSASL version 11, XMLDSig version 11, SunPCSC version 11, JdkLDAP version 11, JdkSASL version 11, SunPKCS11 version 11, BC version 1.61]
KeyStore provider info: SUN (DSA key/parameter generation; DSA signing; SHA-1, MD5 digests; SecureRandom; X.509 certificates; PKCS12, JKS & DKS keystores; PKIX CertPathValidator; PKIX CertPathBuilder; LDAP, Collection CertStores, JavaPolicy Policy; JavaLoginConfig Configuration)
java.ext.dirs: null
[2022-11-01 16:45:43,245 | FINE | container | com.microsoft.sqlserver.jdbc.SQLServerException logException] *** SQLException:ConnectionID:30 ClientConnectionId: bda318c6-406b-4835-998b-0de696f78e05 com.microsoft.sqlserver.jdbc.SQLServerException: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "Internal error during decryption:  Tag mismatch! ". ClientConnectionId:bda318c6-406b-4835-998b-0de696f78e05 The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "Internal error during decryption:  Tag mismatch! ". ClientConnectionId:bda318c6-406b-4835-998b-0de696f78e05
[2022-11-01 16:45:43,245 | FINE | container | com.microsoft.sqlserver.jdbc.SQLServerException logException] com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:3889)com.microsoft.sqlserver.jdbc.TDSChannel.enableSSL(IOBuffer.java:1937)com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:3412)com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:3033)com.microsoft.sqlserver.jdbc.SQLServerConnection.connectInternal(SQLServerConnection.java:2873)com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:1759)com.microsoft.sqlserver.jdbc.SQLServerDataSource.getConnectionInternal(SQLServerDataSource.java:1410)com.microsoft.sqlserver.jdbc.SQLServerDataSource.getConnection(SQLServerDataSource.java:97)com.pb.engageone.server.batch.na.gather.processor.BatchItemPreProcessor.isGraphicResourceMissing(BatchItemPreProcessor.java:188)com.pb.engageone.server.batch.na.gather.processor.BatchItemPreProcessor.isMissingResource(BatchItemPreProcessor.java:131)com.pb.engageone.server.batch.na.gather.processor.BatchItemPreProcessor.process(BatchItemPreProcessor.java:292)com.pb.engageone.server.batch.na.gather.processor.CompositeBatchItemProcessor.process(CompositeBatchItemProcessor.java:28)com.pb.engageone.server.batch.na.gather.processor.BatchItemProcessorWorker.work(BatchItemProcessorWorker.java:79)com.pb.engageone.server.batch.na.ThreadManager$WorkerThread.run(ThreadManager.java:214)
[2022-11-01 16:45:43,245 | FINER | container | com.microsoft.sqlserver.jdbc.SQLServerConnection:30 close] ENTRY

I can provide a full log if necessary.

@AndrzejHeller that'd be great if you can provide the logs. If possible, could you also provide a standalone reproduction app? I'll need to investigate again. For sure there was a race condition. Interesting that it doesn't seem to be the cause of your problem. Whatever the case, there is definitely something suspect in our password obfuscation code.

@tkyc ,
Attaching all the logs gathered during last execution of our automated test procedures:
SQL_JDBC_1.zip
SQL_JDBC_2.zip
Errors can be found in SQL_JDBC.log.38 and SQL_JDBC.log.66. All logs were gathered with logging level set to FINEST.
Unfortunately, I can't provide any application that may help you reproducing the problem.

@AndrzejHeller no worries. I'll see what I can figure out. I'll keep you posted.

Hey @AndrzejHeller, I've attached another driver jar with an attempted fix. Please let me know if it resolves your problem.
mssql-jdbc.zip

We just released a hotfix with this fix. It can be found in v11.2.2 of the driver.


Are the pretrained model weights in RGB or BGR order?

Does the pre-trained DLA model expect input images in BGR or RGB channel order? Thanks.

The data was loaded with default pytorch dataloader: https://pytorch.org/docs/stable/data.html#torch.utils.data.DataLoader

Thanks, so that means they are in RGB order.


Getting an index out of range error during the marshalling process

I am running a simple ANN model, and I am getting an "index out of bounds" error when I run my KF pipeline through Kale. It's happening specifically during my "load_data" pipeline step even though it runs perfectly in the jupyter notebook. Here is my code block below:

And here is the error message from the logs:

Fixed it. In your function definitions, if you're dealing with indexes, make sure to pass them as parameters. For example:
def example(x):
return x[2]
should actually be:
def example(x, index):
return x[index]
Otherwise, you will get a list index out of range error when converting the notebook into a KF pipeline through Kale because Kale will read it as if you are accessing the arbitrary x in your function definition.


Plugins are not detected when running with sudo

This errors comes from nplugm and is reproducible when running node from nvm. The problem is that in such scenario, NVM_BIN is not defined. See https://github.com/resin-io/nplugm/blob/master/lib/resolver.coffee#L49

The issue is fixed if we explicitly tell sudo to keep the environment intact with sudo -E, but there should be a way to preserve them automatically.

Closing this. Is the user's responsibility to make sure his environment is correctly configured.
In the case of NVM, installations are supposed to be "per user" so running a command with sudo (e.g: as root) means that the behaviour is somehow expected.


Change favicon.ico and title

Signed-off-by: Akash Srivastava<EMAIL_ADDRESS>

Pull Request Test Coverage Report for Build 967

0 of 0   changed or added relevant lines in 0 files are covered.
3961 unchanged lines in 3 files lost coverage.
Overall coverage increased (+0.002%) to 26.888%

Files with Coverage Reduction
New Missed Lines
%

probe/docker/registry.go
5
72.7%

render/detailed/detailed.codecgen.go
1342
29.56%

report/report.codecgen.go
2614
35.7%

Totals

Change from base Build 959:
0.002%

Covered Lines:
14579

Relevant Lines:
54222

💛  - Coveralls


Support Custom Metadata

Description
Updated GET/PUT interface for S3-API Support
TODO: Replication related flow is not handling custom metadata
Related Issue
https://github.com/leo-project/leofs/issues/107
Related PR
https://github.com/leo-project/leo_gateway/pull/48
https://github.com/leo-project/leo_storage/pull/17

@windkit Thanks for your PR. Actually, we decided that leo_storage's CRUD interface is not changed.


feat(GUI): check GH Releases for versions when showing the update dialog

This commit makes Etcher look at GitHub Releases to determine whether it
should show the update notification dialog or not.
The build system currently works with S3 (there is an in progress PR to
switch to GitHub Releases), however we already mirror all the files in
GitHub Releases, and that's that the website already looks at.
Change-Type: minor
Changelog-Entry: Look at GitHub Releases to determine if the update notification dialog should be displayed.
Signed-off-by: Juan Cruz Viotti<EMAIL_ADDRESS>

This PR is stale. Closing...


Request for term combining innate immune response and defense response to fungus

To simplify annotation with respect to PMID:22470487 (and similar) I'd like a process term combining;
GO:0045087 - innate immune response
and the multi-organismal term
GO:0050832 - defense response to fungus
along the lines of 'innate immune response in response to fungus' so I can better capture the specific nature of the immune response to the fungus D. coniospora infection without a clumsy melding of wholly separate ontology terms. Further to this, creating regulation terms for any new term would also be useful.
-Alex Holmes

In parallel to 'antifungal humoral response', how about 'antifungal innate immune response': An defense response against a fungus mediated through an innate immune response. An innate immune response is mediated by germline encoded components that directly recognize components of potential pathogens.
Let me know if this works for you I will add it. Then I can add the regulation terms via TermGenie.
-D

Yes, that sounds good to me.
Thanks
Alex
On 07/03/2016 12:48, ukemi wrote:

In parallel to 'antifungal humoral response', how about 'antifungal
innate immune response': An defense response against a fungus mediated
through an innate immune response. An innate immune response is
mediated by germline encoded components that directly recognize
components of potential pathogens.
Let me know if this works for you I will add it. Then I can add the
regulation terms via TermGenie.
-D
—
Reply to this email directly or view it on GitHub
https://github.com/geneontology/go-ontology/issues/12328#issuecomment-193236247.

--
Alex Holmes
European Bioinformatics Institute (EMBL-EBI)
European Molecular Biology Laboratory
Wellcome Trust Genome Campus
Hinxton
Cambridge CB10 1SD
United Kingdom
01223 494260

[Term]
+id: GO:0061760
+name: antifungal innate immune response
+namespace: biological_process
+def: "An defense response against a fungus mediated through an innate immune response. An innate immune response is mediated by germline encoded components that directly recognize components of potential pathogens." [GOC:dph, PMID:22470487]
+is_a: GO:0045087 ! innate immune response
+is_a: GO:0050832 ! defense response to fungus
+created_by: dph
+creation_date: 2016-03-07T08:53:08Z


Microsoft.SqlVirtualMachine/sqlVirtualMachines deployment returns error from bicep

Bicep version
Bicep CLI version 0.5.6 (5f2f88f0f0)
Describe the bug
We are trying to deploy a Microsoft.SqlVirtualMachine/sqlVirtualMachines resource to a linked VM via Bicep.
But we get the error: cannot retrieve the dynamic parameters for the cmdlet.
If we instead run "bicep decompile" and deploy the outputted json file, it's working fine.
Powershell
New-AzResourceGroupDeployment -TemplateFile ".\SqlVirtualMachines_Test.bicep" -ResourceGroupName 'rgname'
Bicep Code - SqlVirtualMachines_Test.bicep
param parLocation string = 'westeurope'
param parSqlVirtualMachineName string = 'vmtemp'

resource test 'Microsoft.SqlVirtualMachine/sqlVirtualMachines@2022-02-01' = {
  name: parSqlVirtualMachineName
  location: parLocation
  properties: {
    virtualMachineResourceId: '/subscriptions/subid/resourceGroups/rgname/providers/Microsoft.Compute/virtualMachines/vmtemp'
  }
}

To Reproduce
Run the bicep code, via New-AzResourceGroupDeployment, after filled the paramter correctly
Additional context
We have a workaround, decompiling to json, but we ofcause want to use bicep instead of.

Can you update Bicep to the latest version (v0.8.9) and make sure you are on the latest version of Az PowerShell? We've seen this error thrown by the Az module when there was an unexpected error during the bicep build process. If you still see the error after updating, I would transfer this issue to the Az PowerShell github repo.

We have tried with version v0.8.9 and updated the az module. We still experience the same issue

Can you please open this in the Azure PowerShell repo? Seems like a duplicate of https://github.com/Azure/azure-powershell/issues/14651.
Are you seeing any warnings in VS code when editing the file? Can you make sure you also have the latest version of the bicep VS Code extension installed?

It is working now.
I received an notification in VSCode about a newer version of the bicep extension. I think it where released today or latest yesterday and it fixed the issue.
Thanks for the respond and for a nice community


Contribute to makefiles: maven

These changes were already imported :) maven.makefile can be found in the latest version.


Include dependency in JVM project fails

from https://github.com/graphhopper/graphhopper/issues/2392
To reproduce, it should be enough to create a new Java or Kotlin project and try to include this library (unconfirmed).
Execution failed for task ':compileKotlin'.
> Error while evaluating property 'filteredArgumentsMap' of task ':compileKotlin'
   > Could not resolve all files for configuration ':compileClasspath'.
      > Could not resolve de.westnordost:osm-legal-default-speeds:1.1.
        Required by:
            project :
         > No matching variant of de.westnordost:osm-legal-default-speeds:1.1 was found. The consumer was configured to find an API of a library compatible with Java 11, packaged as a jar, preferably optimized for standard JVMs, and its dependencies declared externally, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'jvm' but:
             - Variant 'nativeApiElements-published' capability de.westnordost:osm-legal-default-speeds:1.1 declares a library:
                 - Incompatible because this component declares a usage of 'kotlin-api' of a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'native' and the consumer needed an API of a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'jvm'
                 - Other compatible attributes:
                     - Doesn't say anything about how its dependencies are found (required its dependencies declared externally)
                     - Doesn't say anything about its target Java environment (preferred optimized for standard JVMs)
                     - Doesn't say anything about its target Java version (required compatibility with Java 11)
                     - Doesn't say anything about its elements (required them packaged as a jar)

This error doesn't ring a bell, but some keywords (nativeApiElements-published etc.) may be useful to search for details on this error.

Running ./gradlew publishToLocalMaven I get these errors:
> Task :library:publishKotlinMultiplatformPublicationToMavenLocal
Multiple publications with coordinates 'de.westnordost:osm-legal-default-speeds:1.1' are published to repository 'mavenLocal'. The publications 'js' in project ':library' and 'kotlinMultiplatform' in project ':library' will overwrite each other!

> Task :library:publishNativePublicationToMavenLocal
Multiple publications with coordinates 'de.westnordost:osm-legal-default-speeds:1.1' are published to repository 'mavenLocal'. The publications 'js' in project ':library' and 'native' in project ':library' will overwrite each other!
Multiple publications with coordinates 'de.westnordost:osm-legal-default-speeds:1.1' are published to repository 'mavenLocal'. The publications 'kotlinMultiplatform' in project ':library' and 'native' in project ':library' will overwrite each other!

> Task :library:publishJvmPublicationToMavenLocal
Multiple publications with coordinates 'de.westnordost:osm-legal-default-speeds:1.1' are published to repository 'mavenLocal'. The publications 'js' in project ':library' and 'jvm' in project ':library' will overwrite each other!
Multiple publications with coordinates 'de.westnordost:osm-legal-default-speeds:1.1' are published to repository 'mavenLocal'. The publications 'jvm' in project ':library' and 'kotlinMultiplatform' in project ':library' will overwrite each other!
Multiple publications with coordinates 'de.westnordost:osm-legal-default-speeds:1.1' are published to repository 'mavenLocal'. The publications 'jvm' in project ':library' and 'native' in project ':library' will overwrite each other!

When I add the $name to the artifactId like this (in library/build.gradle.kts)
publishing {
    publications {
        withType<MavenPublication> {
            artifactId = "osm-legal-default-speeds-$name"

the warnings are gone and I get separate artifacts for the different targets. Not sure if this is what you want, but it seems to work.

Hm, probably. I noticed that I ignored this part of the tutorial for "publishing multiplatform libraries":
https://kotlinlang.org/docs/multiplatform-publish-lib.html#avoid-duplicate-publications
, mainly because I didn't and still don't understand what the snippet they gave there does.

I saw this too and did not understand it either. But the solution I suggested is pretty clear(?!). It simply appends the target name so there are separate publications/artifacts for each platform. And isn't this exactly what we want? For example when developing on the JVM I do not want the artifact to contain JS or native stuff?

Yeah. Would you like to create a PR?
I am still in Florence and I think I am not set up here to publish things on maven central, so it will be a week or so (anyway) till a new publication can appear on maven central.

Hm when I add this one line to the gradle.kts and execute publishToMavenLocal, I end up with these files in the .m2 repository. This doesn't look right:


Question regarding input file

Hello,
I got the attached  vmec-input file
input.vmec.txt
If I am not mistaken then it was used with Oak Ridge (Mark Cianciosa) of vmec.
(I also got a file mgrid_demo.nc, which has a size of several GB and thus is not attached.)
I tried to run it with the stellopt version. I had to change ndatafmax (fro LIBSTELL/Sources/Modules/vparams.f) to 601(from 101), to get vmec to actually read the file.
Now if I try to run vmec with this input file (on marconi) I get the error
pcurr: check s-grid for curr.dens.-grid values!
Any idea how I can fix this?

First, do you really need 601 knots for your spline data?
Second, if you do need that many then you need to set ndatafmax to be greater than that number.

I do not know if I need 601 knots*, but some of the input quantities in input.vmec (am_aux_s, am_aux_f, ac_aux_s, ac_aux_f) have that many points. Parameter ndatafmax determines the maximum size of these arrays, thus I had to increase it.
*I did not produce the input file nor the grid data.


[nrfconnect] Add PWM support to the lighting-app

Problem
#3806 has added Level Control Cluster to the nrfconnect lighting-app, however UI part of the app doesn't make a use of the cluster yet. That is, it doesn't set LED brightness based on the received level.
Summary of Changes
Use PWM controller on Nordic devices to set brightness of the second LED based on the received Level (0-255).

👍


Vickel: Watch yurylifshits.com

Vickel requests the watch of the watch_keyword yurylifshits\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

yurylifshits\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Jesse in Charcoal HQ


Minor change in Angular2 documentation

Now using feathers-client npm module since this one has everything included with type definitions for FeathersApp and FeathersService

Thank you but I don't think this is correct. The code does use the separate client modules (e.g. https://github.com/feathersjs/feathers-docs/pull/383/files#diff-19f9973ab295886e5b3db9ab4d1c19f8R25) not the different bundled feathers-client module.

At first i tried it with the documented modules, but those didn't have any typescript definition files. So i started researching and stumbled upon this module bundle, which seemed to contain all needed modules including type definitions. Correct me if i'm wrong.
With just feathers-client in the package.json, the following modules got installed:

In the Angular2 doc you recommend to install the module "feathers", which also contains non-client related files. Imho this is not the expected behavior. When installing "feathers-client", you only get client related files and that is correct.

Thank you again for the PR. I am going to close all Angular guide related PRs since we don't have anybody who can review them and we are about to remove frontend framework guides from the documentation and move them into blog posts.
We are still looking for anybody interested in helping with a chat guide blog post for Angular 2.


Update coerce functions for backwards compatibility with JSON-encoded strings written by Flywheel 0.3

Flywheel 0.4 changed the behavior for dict, list and bool; now those use native types from DynamoDB instead of serializing these data types as JSON strings. But Flywheel's load function doesn't know how to load data stored with the old types.
This pull request updates the load functions so that they are backward-compatible and can load data from strings when necessary. It doesn't rewrite the data in DynamoDB, it just allows Flywheel to read existing records without crashing.
We'd like for this to be included in the next Flywheel release so that it can read data stored with earlier versions of Flywheel.
(Submitted on behalf of my coworker @skastel who's on vacation.)

Coverage decreased (-0.43%) to 95.18% when pulling 556dbb0664ebc5f27592fd8dab7969a5a88c7ddf on Runscope:data-type-backward-compat into 583a35c78261171f25e88e4857c8de75f8857131 on mathcamp:master.

Great idea! You caught me right before I leave for a vacation. I'll be back on Monday and can look at it then. I'll want to write some tests before cutting a release, but we can definitely get this in.


allow for the first argument to be an array of pages

It would be useful to specify the pages in an array vs arguments for a more programmatic interface.

Sure, this might be useful. Thanks.


Automated Package Upgrade

:tada: This PR is included in version 7.6.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


FYI nix unstable is broken right now, avoid updating

Just tested with flk core to rule out it being my config:

❯ flk NixOS build
warning: Git tree '/home/cody/try-flake-core-2021-05-23/flk' is dirty
building the system configuration...
warning: Git tree '/home/cody/try-flake-core-2021-05-23/flk' is dirty
error: builder for '/nix/store/jfxy1f4xlylqjk64m3dbrg1rg4bz5f3f-system-path.drv' failed with exit code 1;
       last 2 log lines:
       > created 6190 symlinks in user environment
       > install-info: Cannot allocate memory for gzip -d
       For full logs, run 'nix log /nix/store/jfxy1f4xlylqjk64m3dbrg1rg4bz5f3f-system-path.drv'.
error: 1 dependencies of derivation '/nix/store/gvay16md6qj0rgl6gx0v7cd94p1z6m48-nixos-system-NixOS-21.05.20210315.266dc8c.drv' failed to build

People are working on it, this is the related issue: https://github.com/NixOS/nixpkgs/issues/124215

Workaround (untested):
nix.sandboxPaths = [ "/bin/sh" ];

source: https://github.com/NixOS/nixpkgs/issues/124215#issuecomment-846991745

Workaround isn't working placing that nix setting here, but this is probably the wrong place:
❯ git diff lib/devos/mkHosts.nix
diff --git a/lib/devos/mkHosts.nix b/lib/devos/mkHosts.nix
index 8e2a799..ee2abb2 100644
--- a/lib/devos/mkHosts.nix
+++ b/lib/devos/mkHosts.nix
@@ -33,6 +33,7 @@ let

       hardware.enableRedistributableFirmware = lib.mkDefault true;

+      nix.sandboxPaths = [ "/bin/sh" ];
       nix.nixPath = [
         "nixpkgs=${nixos}"
         "nixos-config=${self}/lib/compat/nixos"

devos2  big-mass-of-changes 「↪ 𝚫 ✔ 📁 」  ⎔ on  (us-east-1)
❯ nix-shell --pure --run "nix show-config | grep sandbox-paths"
warning: Git tree '/home/cody/devos2' is dirty
sandbox-paths =

I got around it by doing the other fix suggested in that thread:
❯ git diff lib/devos/mkHosts.nix
diff --git a/lib/devos/mkHosts.nix b/lib/devos/mkHosts.nix
index 8e2a799..5ffa4f9 100644
--- a/lib/devos/mkHosts.nix
+++ b/lib/devos/mkHosts.nix
@@ -38,6 +38,7 @@ let
         "nixos-config=${self}/lib/compat/nixos"
         "home-manager=${inputs.home}"
       ];
+      documentation.info.enable = lib.mkForce false;

Then sandboxPaths was fixed and I could switch to the newest nix unstable that fixes this issue (I think, we'll see).

Thanks for your report and resuming upstream activity!
At this moment, is there anything left for us to track here?

Thanks for your report and links to upstream!
At this moment, is there anything left for us to track here?

Nope, things are all good for me now and I assume the windows for others to encounter this is closed now.


fs: replace fs.path with plain fs methods

After such a long time using it, it is clear that it wasn't the right decision and path manipulation methods should be right in the class.
This also makes it possible to use most of methods as classmethods without having to initialize the filesystem at all.
Per https://github.com/fsspec/filesystem_spec/issues/747#issuecomment-1296356031 and also a pre-requisite for it.

Codecov Report
Attention: 54 lines in your changes are missing coverage. Please review.

Comparison is base (c01921e) 64.16% compared to head (d2e0b44) 63.87%.

Files
Patch %
Lines

src/dvc_objects/fs/base.py
60.90%
40 Missing and 3 partials :warning:

src/dvc_objects/fs/generic.py
0.00%
4 Missing :warning:

src/dvc_objects/fs/local.py
55.55%
4 Missing :warning:

src/dvc_objects/fs/utils.py
0.00%
2 Missing and 1 partial :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #262      +/-   ##
==========================================
- Coverage   64.16%   63.87%   -0.30%
==========================================
  Files          27       26       -1
  Lines        2051     2051
  Branches      321      335      +14
==========================================
- Hits         1316     1310       -6
- Misses        675      681       +6
  Partials       60       60

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


📝  Readme Addition Styled Component: More detail how the example relates to _document.js

Many, such as me, are coming from vanilla styled-components. The role of the "filename" _document.js was not clear to me. So here a small revision to save other from the TypeError: renderPage is not a function mistake by trying to put the document render into i.e. an index file.
Here the related issue:
https://github.com/zeit/next.js/issues/2632

I'm going to close this since mxstbr is working on an update of the example https://github.com/zeit/next.js/pull/2831


Can't download invoices

When clicking on "Download receipts", it's leading to an error.

There is currently an issue in production preventing the invoices to be downloaded.
 middlewareError {"meta":{"error":{},"level":"error","message":"uncaughtException: html-pdf: Received the exit code '1'
/app/node_modules/phantomjs-prebuilt/lib/phantom/bin/phantomjs: /app/vendor/zlib/lib/libz.so.1: version `ZLIB_1.2.9' not found (required by /usr/lib/x86_64-linux-gnu/libpng16.so.16)
Error: html-pdf: Received the exit code '1'\n/app/node_modules/phantomjs-prebuilt/lib/phantom/bin/phantomjs: /app/vendor/zlib/lib/libz.so.1: version `ZLIB_1.2.9' not found (required by /usr/lib/x86_64-linux-gnu/libpng16.so.16)
at ChildProcess.respond (/app/node_modules/html-pdf/lib/pdf.js:121:31)


The Reopen Projects menu is empty when atom is opened without a project

Prerequisites

[x] Reproduced the problem in Safe Mode: http://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
[x]  Followed all applicable steps in the debugging guide: http://flight-manual.atom.io/hacking-atom/sections/debugging/
[x] Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
[x]  Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
[x] Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
Unexpected restart causes Atom to lose project state
Steps to Reproduce

Open Atom, go to settings -> core and unselect  Reopen Previous Windows On Start
Close Atom and open Atom from spotlight
Go to content menu and try to open recent projects.

Expected behavior: [What you expect to happen]
It has recent projects
Actual behavior: [What actually happens]
It's empty,  when you open a project, it gets populated.
Reproduces how often: [What percentage of the time does it reproduce?]
100%
No Project loaded:

After opening a project:

Versions
atom --version
Atom    : 1.13.1
Electron: 1.3.13
Chrome  : 52.0.2743.82
Node    : 6.5.0

apm --version
apm  1.14.1
npm  3.10.5
node 4.4.5
python 2.7.10
git 2.10.1

Additional Information
Any additional information, configuration or data that might be necessary to reproduce the issue.

@50Wliu Saw this issue in https://github.com/atom/atom/issues/13757

This list is now populated when Atom is open in empty state, but if I open when Atom is in empty state,  we run into data-loss issue: https://github.com/atom/atom/issues/13873.

@ungb That is a good point. If we release this without a fix for https://github.com/atom/atom/issues/13873 we have more ways to run into the data-loss issue.

@damieng, this is going out in beta and not stable, correct?

It's only on master right now. Can merge it to beta or stable branches for the next hotfix if you think it's required. Given nobody else reported it and there is a data loss scenario you mentioned I'd probably hold off on hotfixing.


Add @local_jdk//:jdk dependency when calling _google_java_formatter

Fixes this issue when using Bazel's sandbox:
Formatting java classes failed: Process exited with status 2 [sandboxed].
Error: could not find libjava.dylib
Error: Could not find Java SE Runtime Environment.

Thanks @philwo
LGTM! I'm importing this change internally.

submitted in https://github.com/google/jsinterop-generator/pull/4


Fix 12451: do not re-handle clicks that just closed a modal

One minimal approach to fix https://github.com/godotengine/godot/issues/12451.
What happens in https://github.com/godotengine/godot/issues/12451: if the popup is open, and another mouse click happens on the arrow (that usually opens the popup and should now close it), Godot first closes the modal popup menu (in Viewport::_gui_input_event), but then goes on to process the click on the arrow to open the popup menu again (the code there does not know about the close that just happened). This looks to the user as if the click on the arrow has no effect (indeed it closes and reopens the modal in the same frame).
This PR eats up all clicks that close modals (clicks outside of the modal). Usually, I imagine, this should be the right thing to do, as a click outside of a modal should not also be processed as a regular click. A click should either be a "close-modal" click or a regular click. This change might have a large impact in areas I didn't test though.
I'm not completely sure if it's the right approach overall, yet if a more comprehensive fix is needed this would probably mean a larger reworking of the whole event processing (namely having the popup arrow get informed that a click happened while the modal is still open, and then have it actively pursue a close menu action).

This will probably break some stuff like menu buttons. Maybe when something is opened as modal, one should ask how it wants to handle the out of area click to close it.

also if you are clicking through combos and other modals, you want the current behavior to still happen.  I'm closing because this fix as-is not good, a proper solution is considerably more complex.


[Android] Update OkHttp to 3.14.9 to improve security

Summary
Okhttp 3.12.X allows Connections using TLS 1.0 and TLS1.1.
TLS 1.0 and TLS 1.1 are no longer secure.
Google, Mozilla, Microsoft, and Apple announced that their browsers will require TLSv1.2 or better starting in early 2020.
https://square.github.io/okhttp/changelog_3x/#version-310
https://github.com/facebook/react-native/wiki/Changelog
Starting from 3.13.0 TLSv1 and TLSv1.1 are no longer enabled by default.
3.13.0 requires JAVA 8 and Android SDK 21 (which was blocking the Upgrade in the Past).
Changelog
[Android] [Changed] - Update Okhttp to version 3.14.19
Test Plan
Current tests should pass.
Connections using TLS 1.0 and TLS 1.1 should not be possible.

@WookieFPV could you please rebase so that Android CI works as expected.

@WookieFPV could you please rebase so that Android CI works as expected.

@dulmandakh thank you, the android CI now works as expected.

@dulmandakh thank you, the android CI now works as expected.

Please, remember to bump okio as well.

Please, remember to bump okio as well.

The latest okio Version 1.X is already used.
Okhttp 3.13.0+ requires okio Version 1.17.3 or later and RN uses 1.17.5 (https://square.github.io/okhttp/changelog_3x/#version-3130).
This should be fine in my optionion.
I don't feel comfortable doing a major upgrade on okio, I mostly do RN and very few native android development.

The latest okio Version 1.X is already used.
Okhttp 3.13.0+ requires okio Version 1.17.3 or later and RN uses 1.17.5 (https://square.github.io/okhttp/changelog_3x/#version-3130).
This should be fine in my optionion.
I don't feel comfortable doing a major upgrade on okio, I mostly do RN and very few native android development.

@fkgozali I would propose merge this PR, because bumping okhttp to 4.x would add Kotlin as  a dependency, also some APIs changed thus tests are failing.

@fkgozali I would propose merge this PR, because bumping okhttp to 4.x would add Kotlin as  a dependency, also some APIs changed thus tests are failing.


Windows version does provide a clear error message when trying to  import PKCS#8 encoded private keys

Code crashes when importing PKCS#8 encoded private keys.
See this for reference of the various formats.

Was this fixed with this PR?


Add a crash reproducer for rdar://85843677

https://github.com/apple/swift/pull/39989/ seems to introduce a crash in the testcase being added by this PR. Since it's getting reverted via https://github.com/apple/swift/pull/40321, let's add the testcase to force the crash to get fixed before the next attempt to re-land the changes.

Accidentally closed - reopened in https://github.com/apple/swift/pull/40327.


HW1

Create Pyramid mesh

Implement movement (add deltas to rotation matrices in Update function), depends on system clock time

Warning: I tried to use it has blinking. If it's not a desired behaviour, simply comment out the box creation block in Engine/Source/RenderEngine/private/RenderEngine.cpp