Add PHP 8 support in composer.json

please rebase against current master and force push

Already 7.4 is broken because of external dependency:

https://github.com/mrclay/minify/pull/677

If you have any power, shout out to the maintainer there:

https://github.com/MarcusSchwarz/lesserphp/pull/19

I guess could just skip lesserphp tests on PHP 7.4 and 8.0, as minify itself has no (recorded) issues with these versions.

Would love to see this rolled in

This can be updated now. The lesser PHP has been updated to support PHP8.0

Travis failed for 5.3 and 7.4 actually:

https://travis-ci.org/github/mrclay/minify/builds/738413853

but I'm merging with broken CI to get this released, separate patches are welcome/

actually 7.4 and lessphp were addressed in https://github.com/mrclay/minify/pull/685


bugfix/#75-send-a-request-item-not-corresponded-to-mockup

The titles font size has been changed.

Before receiving approval, please add the following to the PR:

Assignees(add yourself)
Labels(click the gear icon next to it and chose labels)
Projects(Space2Study-02)
Development(also click the gear Icon and you may type "75" to find the issue)

Those are the styles in the mockup where the fontSize is 24px:

The element currently has variant h6:

Which has those styles:

Before receiving approval, please add the following to the PR:

Assignees(add yourself)
Labels(click the gear icon next to it and chose labels)
Projects(Space2Study-02)
Development(also click the gear Icon and you may type "75" to find the issue)

Linked the issue under the Development link


Architecture documentation

Hello,
We just started to explore Gnosis Safe platform and build infrastructure for it:

Safe-relay
Safe-transaction
Safe-config
Safe-gateway

We already deployed using docker-compose 1-3 and did some performance tests. Gateway is remained.
After fixing an issue with the Redis connection https://github.com/gnosis/safe-client-gateway/issues/548 we finally started it and now we are trying to test its performance to build an appropriate infrastructure.
From repository:
Clients --> Safe Gateway --> Safe Transaction
Our container opened port 8000 but we can't connect to it. It is the HTTP service?
Where we can find more information about Gnosis Safe components architecture and specially about how Safe Gateway is connected to other components to understand how can we test it.
Thank you!

As part of this we will take the following steps:

[ ] Document current architecture
[ ] Create docker-compose to run the whole setup with local node (for L2 optimized contracts)
[ ] Document steps what needs to be done to register a new chain

Register webhook

Based on the experiments, we can set REDIS_URL=redis://<IP_ADDRESS>:6379/2 to point the the DB2.
We also started to use Nginx in front of Gateway for HTTPS. Can we configure gateway itself for HTTPS connection?
And one more question related to the architecture
From documentation: https://docs.gnosis.io/safe/docs/services_client_gateway/

The Safe client gateway is a gateway between the Safe clients on the respective platforms (Android/ iOS/ web) and the Safe backend services (Transaction service including Ethereum nodes)

It looks like:
Client --> Gateway --> Transaction
How Gateway connect to the Transaction Service? Is there any key in the .env file?

I will close this issue as the remaining questions were answered in discord in the archived thread Gateway-TransactionService.
For future reference:

We've documented our architecture and intended use in this wiki page . We will continue to add more info to the article
We have started work to prepare a docker-compose.yaml file , it is still at a very early stage but we want to make it as simple to use as possible. You can find the repo here

@jpalvarezl, thank you for the updates and infrastructure repository, looks very good!
I have tried to open Wiki page - https://app.gitbook.com/@gnosissafe/s/documentation/backend/service-architecturem but got 'Not Authorized' error and the following URL: https://app.gitbook.com/o/-MhyDtGxUyODu7d4sgda/s/-MhyEZtd5TVytPJtyS7v-2910905616/backend/service-architecture.
I used my GitHub account to login to the GitBook.

Sorry for getting back to you late on this. I think this was moved to the public docs in gitbook, but if the issue persists I will look into it.

Just tried again to open your link - wiki page and got same error


added data directory for mac to antivirus doc

Proposed changes
See #7136
Unreleased project version (optional)

Related issues (optional)

Deploy preview for modest-edison-79d82e ready!
Built with commit 6c3b584839aa87d3e7c39094ea99185e27d5bc6d
https://deploy-preview-7137--modest-edison-79d82e.netlify.com


Interaction with Microsoft Community Toolkit MVVM Library

Re-opening an earlier issue/question...
I am relatively new to WPF, and am using the pre-release Microsoft Community Toolkit MVVM library.
The issue I'm running into involves the UI not calling the property setters for what should be bound properties:
<cpkr:ColorPicker Grid.Column="1" Grid.Row="1"
                  HorizontalAlignment="Left"
                  SelectedColor="{Binding RouteColor}"/>

public Color RouteColor
{
    get => _routeColor;

    set
    {
        SetProperty( ref _routeColor, value );

        _appConfig.RouteColor = value;
    }
}

The RouteColor property is contained in an ObservableObject.
When I run the app and change the color the property setter is not called. Similarly, the getter isn't called, either, when the control initializes because the displayed/default color is not what I've assigned to RouteColor as an initial value.
The exact same problem -- the setters and getters not being called -- takes place with your companion NumericUpDown library, too.
I'm not sure where the difficulty is, but I did do a simple test using a simple string property bound to a TextBox, and its getter gets called when the TextBox's value is updated.

Okay, I figured out the problems.
First, part of my code base is a general purpose library which uses System.Drawing.Color because it needs to support both console apps and Windows desktop apps. Because the ColorPickerLib uses System.Windows.Media.Color accessing my viewmodel property was throwing exceptions.
Second, I had a typo in the property binding for the numeric updown control.

Okay, I figured out the problems.
First, part of my code base is a general purpose library which uses System.Drawing.Color because it needs to support both console apps and Windows desktop apps. Because the ColorPickerLib uses System.Windows.Media.Color accessing my viewmodel property was throwing exceptions.
Second, I had a typo in the property binding for the numeric updown control.


Can't call component method when component behind container

eg.
components/picker.jsx
import React from 'react';

class Picker extends React.Component {
  constructor(props) {
    super(props);
  }

  // have a component method
  show() {
    console.log('i am show');
  }

  render() {
    return (
picker data
);
  }
}

export default Picker;

containers/picker.js
import Picker from '../components/picker.jsx';
import {useDeps, composeWithTracker, composeAll} from 'mantra-core';

export const composer = ({context}, onData) => {
  // some picker data
  const data = {};
  onData(null, data);
};

export default composeAll(
  composeWithTracker(composer),
  useDeps()
)(Picker);

components/page.jsx
import React from 'react';
import Picker from '../containers/picker';

class Page extends React.Component {
  constructor(props) {
    super(props);
    this.click = this.click.bind(this);
  }

  click() {
    // this will throw error, show is not a function
    this.refs.picker.show();
  }

  render() {
    return (

        <button onClick={this.click}></button>
        <Picker ref="picker" />

    );
  }
}

export default Page;

This is because, after composed you create a new wrapper component. It's  not inheritance. So, you can't access those methods.
Anyway, you shouldn't use it like this. Try to use Redux of some kind of flux tool to talk  to the component via props.


DOC: to_datetime outdated example

With the new default of errors='raise', the following section in the docs is not fully correctly phrased anymore: http://pandas-docs.github.io/pandas-docs-travis/timeseries.html#invalid-data.
So I just removed that example of to_datetime([1, '1']) (as it now raises, which is less unexpected, and the new example already shows the three options).

@jreback BTW, as you can see in the docs, the example gives the following error message:
In [31]: to_datetime([1, '1'])
TypeError: invalid string coercion to datetime

That seems a bit a strange message?
E.g. if you only have strings, you get "Given date string not likely a datetime." (this sounds much clearer)

yeh, that original example is an odd duck as you have an actual python object which is not convvertible by default (an integer). So the error message is 'correct', but prob misleading (as its bubbling up from somewhere)


Issues with Next.js 14 (typescript, eslint)

As you can see in the screenshot, I get an error when adding prefix & defaultFlavour to the tailwind config:
Type error: This expression is not callable.
Type 'typeof import("/opt/repos/projects/portfolio/node_modules/.pnpm/@catppuccin+tailwindcss@0.1.6_tailwindcss@3.4.1/node_modules/@catppuccin/tailwindcss/dist/index")' has no call signatures.

When removing the prefix & defaultFlavour, it works..

This is not related to Next.js. You can simply make a foo.js file with this content
// @ts-check
const foo = require("@catppuccin/tailwindcss");

foo({}); // TS error
foo.default({}); // TS is happy

to reproduce the error.
From a quick glance, the cause is that @catppuccin/tailwindcss should've used export = instead of export default.
What you can do right now while waiting for this bug to be patched: use tailwind.config.ts instead where you can use ESM syntax
// tailwind.config.ts
import type { Config } from "tailwindcss";
import tailwindForms from "@tailwindcss/forms";
import catppuccin from "@catppuccin/tailwindcss";

const config: Config = {
  content: ['./app/**/*.{js,ts,jsx,tsx}', './components/**/*.{js,ts,tsx}', '.css/**/*.css'],
  theme: {},
  safelist: [
    // this is for demonstration purposes only, not required for basic usage
    {
      pattern: /bg-.+/,
    },
  ],
  plugins: [
    tailwindForms,
    catppuccin({
      prefix: 'one',
      defaultFlavour: 'mocha',
    }),
  ],
};

export default config;


Redis cache deletion

Description

Type of change

[ ] Docs change / dependency upgrade
[ ] Configuration / tooling changes
[ ] Refactoring
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Requires changes in customer code

High-level change(s) description - from the user's perspective

Related Issue(s)
Fixes
Related pull request(s)

Update to use redis hgetall via streams for non-blocking operation. We think, that since the hook runs frequently there shouldn't ever be too many "Completed" transactions and thus traversing the list shouldn't be too expensive.

Looking to understand the impact of first run (deleting large amount of completed txns) via some simple manual testing/tools like redis-rdb-tools locally on testnet data, perhaps this could also be fleshed out in to better tests against live data instead of mocks in the future.

@base0010 Double checking is this waiting on review?

@base0010 this looks good now. We need to make sure this does not break the setup so we will need to monitor and test when this gets into staging.

Yeah, this looks to work fine with mocks. I haven't been able to get mocha to test my local db(non-mock) instance. Also the redis cache backup size didn't seem to grow that fast over the week (comparing rdb dumps) so I don't think we're gonna hit any limits. But monitor indeed.


runtime: inconsistent behaviour of make with negative lengths

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

$ go version
go version go1.17beta1 linux/amd64

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

What did you do?
https://play.golang.org/p/K8ZFRxqVfpj
What did you expect to see?
runtime.errorString	runtime error: makemap: len out of range
runtime.errorString	runtime error: makeslice: len out of range
runtime.errorString	runtime error: makechan: len out of range

What did you see instead?
(no panic)
runtime.errorString	runtime error: makeslice: len out of range
runtime.plainError	makechan: size out of range

The map make doesn't panic at all, while the other two panic with inconsistent messages.  The documentation doesn't specify any constraints on these parameters, besides cap >= len, and neither does the Spec, as far as I can see.  At the very least the behaviour w.r.t. invalid lengths should be documented, I think.

The map value is just a hint, so we don't panic in that case. In other words, there's something reasonable we can do and the program can continue (unlike the slice or chan situations). More discussion at https://github.com/golang/go/issues/24308
I agree that the chan failure should have "runtime error:" prefixed, and probably be an errorString. I think we're allowed to change runtime errors without breaking go1 compatibility.

I see, thanks.  Perhaps the fact that this is a hint as opposed to an actual size should also be documented in package builtin.  The docs currently say (emphasis added):

Map: An empty map is allocated with enough space to hold the
specified number of elements. The size may be omitted, in which case
a small starting size is allocated.

The Spec calls the parameter “hint”, which is correct, I assume.

I think we decided in #14965 that we weren't going to add the "runtime error:" prefix to errors we were already generating, just to avoid breaking people that depended on the text. So I don't think there's anything to do here. Closing as unfortunate, but not worth fixing.

@randall77, should the documentation in package builtin mention that invalid hints are set to zero, or would that be unnecessary?  If it should, I am ready to send a CL about that.  If not, oh well.

I don't think it is necessary.

Map: An empty map is allocated with enough space to hold the specified number of elements.

That seems correct and complete. If you specify -3, then the map is allocated with enough space for -3 elements.
The "size" part in the next sentence (which you quoted above) is just the formal parameter name in the declaration.
If anything, we could document the panic behavior for the other kinds (slice, chan). But we generally don't get that formal (for instance, close of a nil channel panics, but we don't mention that in the builtin docs).


Be able to define tests in YAML/XML files

As a first approach, it loads all YAML files it can find and under the tests folder, and also run the tests as the PHP declared ones. Any hint or improvement is welcomed!

Added XML option for defining the tests, looking for a way to define the XSD in GitHub so we can take advantage of ide's autocomplete when creating XML tests. Any comments or improvements are welcomed!


hitbtc not working

Looks like using the old api, as hitbtc is now v2, looks liek system still runs v1. Comes out with a 403 error

It polls all trades, unlike all the other exchanges that poll like 5 trades every poll_trades period. So because of that it just spams the terminal with trades. It doesn't listen to c.poll_trades either. I'm trying to figure out how to fix that. If anybody has any ideas please let me know.

Hey, I found the issue:
extensions/exchanges/hitbtc/exchange.js
line 95 should be moved to line 96.
It polls trades during a for loop for all available currencies in hitbtc. While it should do that for the specified currency only.

@abduegel Yes! I tried your fix and it works. I'm going to submit a pull request with that fix + an upgrade to HitBTC API 2.0. Thank you!

My PR was merged. Still working on fixing executing buys / sells

Hi, I found out that buys and sells were also not working, im also close to a fix.
I got buy, sell and cancel working, but getOrder is not working yet. Btw I'm trying to implement the binance functionality based on the hitbtc code (using ccxt), which is how I found out this fix.
`
cancelOrder: function (opts, cb) {
  var func_args = [].slice.call(arguments)
  var client = authedClient()
  client.cancelOrder(opts.order_id, joinProduct(opts.product_id)).then(function (body) {
    if (body && (body.message === 'Order already done' || body.message === 'order not found')) return cb()
  },function(err){
    if (err) return retry('cancelOrder', func_args, err)
    cb()
  })
},

buy: function (opts, cb) {
  var func_args = [].slice.call(arguments)
  var client = authedClient()
  if (typeof opts.post_only === 'undefined') {
    opts.post_only = true
  }
  opts.type = 'limit'
  if (opts.order_type === 'taker') {
    delete opts.price
    delete opts.post_only
    opts.type = 'market'
  }
  opts.side = 'buy'
  delete opts.order_type
  var args = {}
  client.createOrder(joinProduct(opts.product_id), opts.type, opts.side, this.roundToNearest(opts.size, opts), opts.price, args).then(result => {
    if (result && result.message === 'Insufficient funds') {
      var order = {
        status: 'rejected',
        reject_reason: 'balance'
      }
      return cb(null, order)
    }
    orders['~' + result.id] = result
    cb(null, result)
  }).catch(function (error) {
    console.error('An error occurred', error)
    return retry('buy', func_args)
  })
},

sell: function (opts, cb) {
  var func_args = [].slice.call(arguments)
  var client = authedClient()
  if (typeof opts.post_only === 'undefined') {
    opts.post_only = true
  }
  opts.type = 'limit'
  if (opts.order_type === 'taker') {
    delete opts.price
    delete opts.post_only
    opts.type = 'market'
  }
  opts.side = 'sell'
  delete opts.order_type
  var args = {}
  client.createOrder(joinProduct(opts.product_id), opts.order_type, opts.side, opts.size, opts.price, opts).then(result => {
    if (result && result.message === 'Insufficient funds') {
      var order = {
        status: 'rejected',
        reject_reason: 'balance'
  }
      return cb(null, order)
    }
    orders['~' + result.id] = result
    cb(null, result)
  }).catch(function (error) {
    console.error('An error occurred', error)
    return retry('buy', func_args)
  })
},

`

Did you try these lines on the latest version of zenbot, after I made the pull request? Your buy/sell code didn't seem to work for me. Also, it's strange that you can do cancelOrder but not getOrder, considering they use the same inputs.

It seemed to work on binance, with the same library and API. So it should be a good starting point to make this work in hitbtc, I was planning to look for a fix in HitBTC during the weekend.
(btw could you check again after you remove the "this.roundToNearest" part? that method was only neccesary for hitbtc)
The reason I posted this code is because some bugs were solved in it. For example some arguments in createOrder were undefined (like opts.market, and opts.type).

Hi, I got buying and selling working on hitbtc. Here is the exchange.js file:
https://gist.github.com/abduegal/4a049d38cae6f5f43b71b56a989ffa37
I also needed to update the update-product.js
https://gist.github.com/abduegal/d672e1e33c6f6e361969eec702389c1b
So for now HitBTC is buying and selling for me. @brucetus do you have time to create a pull request? my repository is quite a mess right now ;)

Nice! Creating orders work but I had problems getting orders, specifically the code thinks that the orders were instantly filled, however they were still open and unfilled on the hitbtc website. I think I fixed it by updating the order keywords:
    getOrder: function (opts, cb) {
      var func_args = [].slice.call(arguments)
      var client = authedClient()
      var order = orders['~' + opts.order_id]
      var args = {
        id: opts.order_id
      }
      client.privateGetOrder ({
       args
      }, {}).then(function (body) {
        if (body.status == 'filled') {
          order.status = 'done'
          order.done_at = new Date().getTime()
          order.filled_size = parseFloat(body.amount) - parseFloat(body.remaining)
          return cb(null, order)
        }
        else if (body.status == 'canceled' || body.status == 'expired' || body.status == 'suspended') {
          order.status = 'done'
          order.done_at = new Date().getTime()
          order.filled_size = '0.00000'
          return cb(null, order)
        }
        else {
          order.status = 'open'
        }
        cb(null, order)
      }, function(err) {
        console.log(err)
        return retry('getOrder', func_args, err)
      })
    },

I'm going to test some more with real trades and then submit the pull request, thank you.

Something wrong with order filled status: displays "buying" when already bought, displays "selling" when already sold. Does it affect further trading somehow ?

Hi. I have same problem. Is there any solution?


Add Support Base 64 encoding of password

Hi,
This is likely an enhancement request.
Could you support for Base-64 encoded passwords be added to the Norconex HTTP crawler in the near future, similar to the functionality available in Autonomy IDOL? Below is an example for reference.
<credentials>     <username>yourUsername</username>     <password>XY12AbcDefGHIJ==</password> </credentials>
Additionally, would it be possible to provide an option to encode passwords in Base-64 using your encryption tool?
Thank you again!

Because encoding (as opposed to encrypting) is not a secure way to protect passwords, we are not planning to add it. I am still marking it as a feature request, as we may reconsider if there is enough demand for it.
What issues are you experiencing with using encryption?

Thank you Pascal.
No problem at all. I was simply looking for an easier way to encrypt passwords in Base-64 without relying on an external file.  I understand that it will be less secure without the file but it will be used within our secure network.  Thank you again.
Regards,
Stephen Jacob

You can avoid using an external by putting the key right with the config, like this:
<credentials>
  <username>joe</username>
  <password>3ncryp73d</password>
  <passwordKey>
    <value>paste_the_key_kere</value>
    <source>key</source>
  </passwordKey>
</credentials>

Alternatively, you can also store the decryption key as an environment variable or system property, as described by the  Credentials class.


Show previous target

Hello,
is there a method or some workaround to show the previous target?
For moving to the next one we have spotlight.closeCurrentTarget(), anything similar for going back would be useful.
In this way for example in a tutorial you can have all kind of buttons, skip, next but also back.

Can you please share what's the skip method?

Can you please share what's the skip method?

You can use spotlight.closeSpotlight() to skip it and close it altogether.

@TakuSemba can you please look at the issue

is there a method or some workaround to show the previous target?

Unfortunate, There is no way to archive that for now.

As of 2.0.0, you can go back to the previous target with Spotlight#previous().
Thank you.


Cannot convert the value of type "Microsoft.Azure.Commands.Profile.Models.PSAzureSubscription" to  type "Microsoft.Azure.Commands.Common.Authentication.Abstractions.Core.IAzureContextContainer".

$AzureContext = Get-AzSubscription -SubscriptionId $ServicePrincipalConnection.SubscriptionID
returns error when using in Start-AzAutomationRunbook
Start-AzAutomationRunbook : Cannot bind parameter 'DefaultProfile'. Cannot convert the
"XXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX" value of type "Microsoft.Azure.Commands.Profile.Models.PSAzureSubscription" to
type "Microsoft.Azure.Commands.Common.Authentication.Abstractions.Core.IAzureContextContainer".
At line:19 char:16

-AzContext $AzureContext

           ~~~~~~~~~~~~~

CategoryInfo          : InvalidArgument: (:) [Start-AzAutomationRunbook], ParameterBindingException
FullyQualifiedErrorId :
CannotConvertArgumentNoMessage,Microsoft.Azure.Commands.Automation.Cmdlet.StartAzureAutomationRunbook

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 23c183d0-5012-e2e1-5562-69135b3f6509
Version Independent ID: 7f36ff87-e24a-7442-8d42-f621f5391814
Content: Create modular runbooks in Azure Automation
Content Source: articles/automation/automation-child-runbooks.md
Service: automation
Sub-service: process-automation
GitHub Login: @MGoedtel
Microsoft Alias: magoedte

Thanks for the Comment. We are actively investigating and will get back to you soon.

Hi @placidseven, sharing this troubleshooting content addressing a similar scenario. Please review to see if it helps resolve your issue. Let me know if you've already tried this and we can help investigate further.

Have a good weekend.

@placidseven, Since we have not heard back from you we will now proceed to close this thread. If there are further questions regarding this matter, please tag us (@femsulu) in your reply and we will gladly continue the discussion.
As a side note, this channel is reserved for ‘Azure docs’ feedback- for sharing doc feedback and suggesting content improvements.


doc: filter new known doc build warnings

Changes to uart.h in PR #10820 caused a new warning from Sphinx/Breathe
that we can classify as a "known issue" and should ignore.
Signed-off-by: David B. Kinder<EMAIL_ADDRESS>

Codecov Report

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

@@           Coverage Diff           @@
##           master   #11884   +/-   ##
=======================================
  Coverage   51.24%   51.24%
=======================================
  Files         231      231
  Lines       28646    28646
  Branches     7132     7132
=======================================
  Hits        14679    14679
  Misses      11155    11155
  Partials     2812     2812

Continue to review full report at Codecov.

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


Unify developer docs for Quarkus-based APIs

The Docs API README contains useful information about running the application and integration tests.
This will (hopefully) be similar for the REST and GraphQL APIs once they are migrated to Quarkus, so we should pull that information up in apis/README.md.

Did some work here lately, but this still need finalizing.


Current NPM version is wrong breaking the codebase

Current:
version 3.0.30

  "dependencies": {
    "@mdi/font": "^4.9.95"
  },
"devDependencies": {
    "@vue/cli-plugin-babel": "^4.5.6",
    "@vue/cli-plugin-eslint": "^4.5.6",
    "@vue/cli-plugin-unit-jest": "^4.5.6",
    "@vue/cli-service": "^4.5.6",
    "@vue/test-utils": "1.0.0-beta.29",
    "babel-eslint": "^10.1.0",
    "bili": "^5.0.5",
    "chalk": "^4.1.0",
    "eslint": "^5.16.0",
    "eslint-plugin-vue": "^5.0.0",
    "node-sass": "^4.14.1",
    "rollup-plugin-vue": "^5.1.9",
    "sass-loader": "^8.0.2",
    "vue": "^2.6.14",
    "vue-template-compiler": "^2.6.14"
  },

Expected:
version 3.0.28

"dependencies": {
   "core-js": "^3.18.2",
   "vue": "^3.2.20",
   "vue-loader": "^16.8.1"
 },
"devDependencies": {
   "@vue/cli-plugin-babel": "^4.5.13",
   "@vue/cli-plugin-eslint": "^4.5.6",
   "@vue/cli-plugin-router": "^4.5.13",
   "@vue/cli-plugin-unit-jest": "~4.5.0",
   "@vue/cli-service": "^4.5.6",
   "@vue/compiler-sfc": "^3.2.19",
   "@vue/test-utils": "^2.0.0-0",
   "babel-eslint": "^10.1.0",
   "bili": "^5.0.5",
   "chalk": "^4.1.2",
   "eslint": "^6.7.2",
   "eslint-plugin-vue": "^7.0.0",
   "node-sass": "^7.0.0",
   "rollup-plugin-vue": "^5.1.9",
   "sass-loader": "^8.0.2",
   "typescript": "~3.9.3",
   "vue-jest": "^5.0.0-0"
 },

For some reason a lot of libraries either got downgraded or removed. This results in the package not working as intended when installing trough npm i luisa-vue.
The previous patch to NPM (think manual publish) should be reverted as its not in line with the github version

Hi,
I just tried with
npm install luisa-vue@3

and it worked for me on a fresh project.


Update upload_dbt_models.sql

append =True,

append=True

Hi @manojkumarfl
I believe we do not want to use append=True for dbt_models, as it should represent the current status of the models in the project.
Why do you want to change that? is there an issue with that?

Hello.
In this requirement, we have multiple projects, where  this package "elementary" is used to build audit across all projects.
But unfortunately when we call this package ,  The Audit tables, specifically "DBT_MONITOR"."DBT_MODELS" table is getting Overwritten.   Can we do something about it?

I tried, dispach config, to override upload_dbt_models.sql macro with a custom macro,  but since we are not calling this macro implicitly, and calling the entire package,   we are unable to overwrite.
So ultimately for every elementary package trigger from different projects, the table "DBT_MODELS" audit is getting truncated and loaded

I believe having multiple dbt projects for the same database is not the best practice, and doing something like having separate folders inside a single dbt project and using a --select to run each seperatly would be a better approach for you (regardless of elementary, tho it will solve this issue).
If you still have to do it for some reason, then you should try having a separate elementary schema for each project, that way they would not collide.

Hi @manojkumarfl ,
At this point we do not support multiple environments with this setup. In the future we might want to but this will require extensive research on the effects of this on all of our features so we cannot approve this right now.
I recommend using a different Elementary schema per project.


Document supported python versions, expand versions

Is your feature request related to a problem? Please describe.
The current ark build only supports python 3.8. If you try and pip install using 3.9, this unintuitive error message comes up:

Describe the solution you'd like
We should more clearly indicate which versions are supported. We should also begin testing multiple versions of python to make the subsequent process of switching/deprecating relatively seamless.

The NumPy drop schedule states that as of April 14, 2023, new releases of NumPy (version 1.21+) will not be available for Python 3.8.


PR: Update docs

Fixes #12

Codecov Report
Patch and project coverage have no change.

Comparison is base (41ed14a) 76.09% compared to head (e905419) 76.09%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff           @@
##             main      #15   +/-   ##
=======================================
  Coverage   76.09%   76.09%
=======================================
  Files          16       16
  Lines         979      979
=======================================
  Hits          745      745
  Misses        234      234

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

I think before releasing the first version of this package, we need to publish the first alpha of Spyder 6, right?

I think before releasing the first version of this package, we need to publish the first alpha of Spyder 6, right?

Probably, I'm not sure what could be the best approach 🤔

I think that would be the best we can do because if you publish an initial version of this package right now, pip/conda won't be able to resolve its dependency on Spyder 6.


Error when loading workspaces folders: go command not found.

Same issue for me on Fedora 38.
As a workaround: PATH=$(echo $PATH) lapce solves the issue.


Constrained Decoding

Is there example code on how to integrate Constrained Decoding for the Seq2Seq example model?

Thanks for the question. Currently, we didn't use constrained decoding in the Seq2Seq model, as we found the improvement of using constrained decoding is marginal (or even worse). Inheriting constrained decoding into our method requires implementing a Seq2Seq Trainer of your own, see text2event.


Add reply/retweet/like numbers for tweets

Could you also please add the tweet id and published date for tweets?


TriggerAuthentication/Vault: add support for vault namespace

Signed-off-by: Nicolas Chapurlat<EMAIL_ADDRESS>Related to this issue: #2084
Related to this discussion: #2080
Changes

Add an optional "namespace" in Keda TriggerAuthentication spec: spec.hashiCorpVault.namespace
Optionally configure the Vault namespace in the Vault client
REMOVED FROM THIS PR: Make sure the VAULT_NAMESPACE env var never takes precedence (Vault client default behaviour)

Checklist

[x] Commits are signed with Developer Certificate of Origin (DCO - learn more)
[x] Tests have been added no test yet in vault section (I performed a local integration test I could provide)
[x] A PR is opened to update our Helm chart (repo) (if applicable, ie. when deployment manifests are modified)  => not applicable
[x] A PR is opened to update the documentation on (repo) (if applicable)  => Done: https://github.com/kedacore/keda-docs/pull/522
[x] Changelog has been updated

Relates to https://github.com/kedacore/keda/issues/2084

Thanks for the contribution!


[Twitter Adapter] Migrate unit tests to xUnit

Description
This PR migrates existing Twitter Adapter unit tests to xUnit.
Detailed Changes

Updated ActivityExtensionsTests, WebhookHostingServiceTests and AuthHeaderBuilderTests classes to use xUnit instead of MSTests.
Replaced [TestMethod] attribute  with [Fact].
Updated Asserts.
Replaced [TestCategory] attribute with [Trait].

Testing
This image shows the tests passing after the changes.

This PRs will be promoted last, as we'll be removing MSTests dependency on this PR (so it needs to be merged before all the rest of the PRs)


Recursive include_role for tasks is not recognized

File: roles/nginx-env/tasks/main.yml:
- name: Run as root
  become: yes
  block:
  - name: Multiple domains and certificates
    include_role:
      name: nginx-env
    vars:
    - nginx_domains: '{{ nginx_role_loop_item.nginx_domains }}'
    - env_name: '{{ nginx_role_loop_item.env_name }}'
    - nginx_env_server_extra: '{{ nginx_role_loop_item.nginx_env_server_extra }}'
    loop: '{{ nginx_domains_extra | d([]) }}'
    loop_control:
      loop_var: nginx_role_loop_item

ansible-lint shows error:
schema: {'name': 'Multiple domains and certificates', 'include_role': {'name': 'nginx-env'}, 'vars': [{'nginx_domains': '{{ nginx_role_loop_item.nginx_domains }}'}, {'env_name': '{{ nginx_role_loop_item.env_name }}'}, {'nginx_env_server_extra': '{{ nginx_role_loop_item.nginx_env_server_extra }}'}], 'loop': '{{ nginx_domains_extra | d([]) }}', 'loop_control': {'loop_var': 'nginx_role_loop_item'}}
is not valid under any of the given schemas (schema[tasks])
roles/nginx-env/tasks/main.yml:1  Returned errors will not include exact line numbers, but they will mention
the schema name being used as a tag, like ``schema``,
``schema``.

This rule is not skippable and stops further processing of the file.

Schema bugs should be reported towards (https://github.com/ansible/schemas) project instead of ansible-lint.

If incorrect schema was picked, you might want to either:

* move the file to standard location, so its file is detected correctly.
* use ``kinds:`` option in linter config to help it pick correct file type.

You can skip specific rules or tags by adding them to your configuration file:
# .config/ansible-lint.yml
warn_list:  # or 'skip_list' to silence them completely
  - experimental  # all rules tagged as experimental

Apparently you are not aware that blocks do not allow looping, ansible will give a syntax error with your example. Can you please update it to make it pass ansible own syntax check?

If you use ansible.builtin.include_role it will work.

Ansible doesn't complain about syntax and code is working as expected.
ansible.builtin.include_role makes no difference:

schema: {'name': 'Multiple domains and certificates', 'ansible.builtin.include_role': {'name': 'nginx-env'}, 'vars': [{'nginx_domains': '{{ nginx_role_loop_item.nginx_domains }}'}, {'env_name': '{{ nginx_role_loop_item.env_name }}'}, {'nginx_env_server_extra': '{{ nginx_role_loop_item.nginx_env_server_extra }}'}], 'loop': '{{ nginx_domains_extra | d([]) }}', 'loop_control': {'loop_var': 'nginx_role_loop_item'}} is not valid under any of the given schemas (schema[tasks])

The title is wrong because the schema failure has nothing to do with include_role and instead if caused by passing a list of dictionaries to vars:, something that is not documented as supported by ansible:
# undocumented way to declare vars
vars:
  - foo: var

# official way to declare vars:
vars:
  foo: bar

The big question is if we should allow the undocumented syntax to be used or not. If that is not accidental, we need to have ansible official documentation updated to mention this as allowed at https://docs.ansible.com/ansible/latest/user_guide/playbooks_variables.html#defining-variables-in-a-play

Thank you, I've fixed syntax, now there are no errors. I'm sorry for misleading, error message was not detailed enough.

@Vanav No problem. That is caused by the validator which is not able to give the best-possible error messages. I had to remove some keys until I spotted the root cause.
I will keep this bug open because it is still a problem and we will need some actions on it on our side. As you probably seen, we already got a bug report in core about it. If it is supported, it must be documented.

This feature is deprecated since https://github.com/ansible/ansible/pull/78927 merged. So there is no real need to update the schema.


Adds a basic authentication module that adds a real identity to the logs.

Works only when a .aur file is used, since it requires code executed by a
base file to hook the authentication process. In the medium term, we need
to create our own client so that we can hook auth + updates for all methods
without going through .aur files that may or may not be imported.
This pull request is only to solicit feedback; we'll leave it in a separate branch that we merge with master to create the tellapart branch going forward.
@steveniemitz @dmontauk @tonyd3

looks good (thumbsup)


How can I add data attributes?

I've been trying this tutorial and while everything works fine, I need a way to attach an ID to every marker so I can trigger individual bootstrap modals like so:
data-toggle="modal" data-target="some id"
After doing some reading, everything seems to indicate that I should do something similar to this:
`marker._icon.dataset.toggle = 'modal';
marker._icon.dataset.target = '';`
However, I can't seem to quite grasp where I should put this. This is my code:
`/*

global variables
*/
var map;			// global map object
var lyrOsm;			// the Mapnik base layer of the map
var lyrPlq;			// the geoJson layer to display plaques with
var blueicon;		// a blue icon for blue plaques
var greenicon;		// a green icon for green plaques
var whiteicon;		// a white icon for white plaques

// when the whole document has loaded call the init function
$(document).ready(init);
function init() {
// map stuff
// create the icons
blueicon=L.icon({
iconUrl: 'images/blueplaque.png',
iconSize:     [24, 24], // size of the icon
iconAnchor:   [12, 23],	// point of the icon which will correspond to marker's location
popupAnchor:  [0, -12]  // point from which the popup should open relative to the iconAnchor
});
greenicon=L.icon({
iconUrl: 'images/greenplaque.png',
iconSize:     [24, 24], // size of the icon
iconAnchor:   [12, 23],	// point of the icon which will correspond to marker's location
popupAnchor:  [0, -12]  // point from which the popup should open relative to the iconAnchor
});
whiteicon=L.icon({
	iconUrl: 'images/whiteplaque.png',
	iconSize:     [24, 24], // size of the icon
	iconAnchor:   [12, 23],	// point of the icon which will correspond to marker's location
	popupAnchor:  [0, -12]  // point from which the popup should open relative to the iconAnchor

});

// base layer
var osmUrl='https://api.tiles.mapbox.com/v4/mapbox.streets-basic/{z}/{x}/{y}.png?access_token=pk.eyJ1IjoiaHVpdHppbG9wIiwiYSI6ImNpajFmcW15NjAwOXR1ZGx3czNobHg1MDEifQ.cYoJoMWkFT8YkQk1ElTmag';
var osmAttrib='Map data © OpenStreetMap contributors';

lyrOsm = new L.TileLayer(osmUrl, {
	minZoom: 9,
	maxZoom: 19,
	attribution: osmAttrib
});

// a geojson layer
lyrPlq = L.geoJson(null, {
	pointToLayer: setIcon
	}
);

// set the starting location for the centre of the map
var start = new L.LatLng(53.7610,-0.3529);

// create the map
map = new L.Map('mapdiv', {		// use the div called mapdiv
	center: start,				// centre the map as above
	zoom: 12,					// start up zoom level
	layers: [lyrOsm,lyrPlq]		// layers to add
});

// create a layer control
// add the base layers
var baseLayers = {
	"OpenStreetMap": lyrOsm
};

// add the overlays
var overlays = {
	"Plaques": lyrPlq
};

// add the layers to a layer control
L.control.layers(baseLayers, overlays).addTo(map);

// create the hash url on the browser address line
var hash = new L.Hash(map);

map.on('moveend', whenMapMoves);

askForPlaques();

}
function whenMapMoves(e) {
askForPlaques();
}
function setIcon(feature,ll) {
var plq;
if (feature.properties.colour=='green') {
plq=L.marker(ll, {icon: greenicon});
}
else if (feature.properties.colour=='white') {
plq=L.marker(ll, {icon: whiteicon});
}
else {
plq=L.marker(ll, {icon: blueicon});
}
plq.bindPopup(feature.properties.plaquedesc);
return plq;
}
function askForPlaques() {
var data='bbox=' + map.getBounds().toBBoxString();
$.ajax({
url: 'ajax/ajxplaques.php',
dataType: 'json',
data: data,
success: showPlaques
});
}
function showPlaques(ajxresponse) {
lyrPlq.clearLayers();
lyrPlq.addData(ajxresponse);
}
`
Thanks!

Hi, great to hear that you find Leaflet useful!
However, this issue tracker is used for reporting bugs and discussing new features. For questions on using Leaflet, please use gis.stackexchange.com or stackoverflow.
Having said that: look into L.DivIcon, which allows you to manually specify HTML code you can then attach to a marker.


added terms.html to _default dir to suppress error Found no layout fo…

…r taxonomy term
You have 2 options. Either merge this pull request or go ahead and try to fix the error Found no layout for taxonomyTerm
See https://github.com/vjeantet/hugo-theme-docdock/issues/169
Contrary to https://github.com/gohugoio/hugo/issues/3386#issuecomment-302493626 this issue with your theme is reproducible in all shapes and forms and with different hugo versions.
Adding terms.html to _default suppresses the error and thus allowing your theme from being generated from the Themes hugo site in the future.
You can also add disableKinds = "taxonomyTerm" on the config file as well.

Just to be clarify, disableKinds doesn't require a terms.html, right? There's a similar issue open on cocoa-eh I haven't resolved, and I don't think adding a trivial terms file is good so I'll probably go with disableKinds in both cases.
Thanks for submitting this.

Just to be clarify, disableKinds doesn't require a terms.html, right?

correct. From my understanding disableKinds was pretty much condensed into one
https://github.com/gohugoio/hugo/commit/5794a265b41ffdeebfd8485eecf65cf4088d49d6
https://hugo.doc.xuwenliang.com/release-notes/

Okay, I don't plan on supporting it now, so I'm going to add the line disabling it to the sample theme.toml. I don't think this was a good API change for hugo to make, at least since it can't be disabled at the theme level so far as I can tell, but it is what it is.

What's the reason for the themesDir change? It detects the theme fine as is, for me.

What's the reason for the themesDir change? It detects the theme fine as is, for me.

I'm sorry. I don't know what you mean.
This is what you have on the configuration file theme = "../.."
Anyhow, closing now. Glad you have it working!

Was just asking about the motivation behind this:
theme = "athena-hugo-theme"
themesDir = "../.."

Thanks for your help!

Was just asking about the motivation behind this:
theme = "athena-hugo-theme"
themesDir = "../.."

no problem. themesDir and path are optional. If you look at many of the exampleSite implementations, you'd notice a great many users opt to have it, while there are many who simply don't.
the documentation states

themesDir (“themes”)
The directory where Hugo reads the themes from.

But theme followed by path is just wrong.


k0sctl: 0.15.1 -> 0.15.2

Description of changes
Don't count empty private addresses during validation  in https://github.com/k0sproject/k0sctl/pull/485
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

1 package updated:
k0sctl (0.15.1 → 0.15.2)
1 package built:
k0sctl


get_current_site() will no longer be importable from django.contrib.sites.models

Hi
with django 1.9, an error occured when setting-up the application.
File "XXX/lib/python3.5/site-packages/password_policies/urls.py", line 3, in
from password_policies.views import PasswordChangeFormView
File "XXX/lib/python3.5/site-packages/password_policies/views.py", line 19, in
from password_policies.forms import PasswordPoliciesForm
File "XXX/lib/python3.5/site-packages/password_policies/forms/init.py", line 8, in
from django.contrib.sites.models import get_current_site
ImportError: cannot import name 'get_current_site
In Django Deprecation Timeline
https://docs.djangoproject.com/es/1.9/internals/deprecation/#deprecation-removed-in-1-9
there is the reason
"RequestSite and get_current_site() will no longer be importable from django.contrib.sites.models."
Is it possibile to fix it with
try:
    from django.contrib.sites.models import get_current_site
except ImportError:
    from django.contrib.sites.shortcuts import get_current_site

, correct?
Thank you
Pietro

Django 1.9 was released December last year. Django 1.10 will be released in August. Any chance for a fix for this?

Looks like this was fixed in #49 (November 2015) - the fact nobody has responded to this ticket or made a new release would suggest this project is dead.

Nope. Not dead. Just on a very much needed holiday. Will take care of
things next week when I get home...
On Jul 1, 2016 6:59 AM, "Brian May"<EMAIL_ADDRESS>wrote:

Looks like this was fixed in #49
https://github.com/tarak/django-password-policies/pull/49 (November
2015) - the fact nobody has responded to this ticket or made a new release
would suggest this project is dead.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tarak/django-password-policies/issues/50#issuecomment-229854100,
or mute the thread
https://github.com/notifications/unsubscribe/AADG1omYb4ClqfvTE5sMWSMwoitfxsWYks5qRJ6zgaJpZM4IrWhW
.

Any news on this reaching pypi?


make check failed

After your last commit "make check" does not work on
trentin-süd-tirol.it
And other similar domains published in lastest psl.
It seems that punycode or utf-8 is not well supported in the function psl_is_public_suffix2.
test-suite.log

It's a known issue when building libpsl without any IDN library (libidn, libidn2 or libicu).
It came with one of the latest updates to the Public Suffix List, where someone (likely a MacOS/OSX user) introduced decomposed non-ASCII chars. E.g., for 'ü' they use the UTF-8 sequence '75 cc 88' while the expected NFKC sequence would be 'c3 bc'.
Converting those sequences into NFKC needs a IDN library...
The issue has been reported, but I am not sure if and what they do something about it:
https://github.com/publicsuffix/list/issues/715

Here is an MR that fixes the isue upstream: https://github.com/publicsuffix/list/pull/720

Finally fixed now, as reference see
https://github.com/publicsuffix/list/pull/720
https://github.com/publicsuffix/list/pull/725
Thanks for the heads up.


Revert "user-agent metadata trait, also: grpc_core::Slice is born"

Reverts grpc/grpc#27770
The PR seems to be breaking a bunch of test on master, e.g. master/linux/grpc_basictests_c_cpp_dbg and master/linux/grpc_basictests_c_cpp_opt.
https://source.cloud.google.com/results/invocations/8271a8dd-bac1-47a7-98e6-47c4cc91e4bd/log

Ok, the PR also broke the several interop test jobs.
This is actually something that was reported on the PR's presubmit tests, so it shouldn't have been merged in the first place.

Apologies for the breakage. When I clicked through it seemed it was just the failures I'd been seeing on every PR all day.
We can't stop work because infrastructure is flaky, and submitting anything to this codebase needs either a deep appreciation of the current state of too much infrastructure or guesswork when things are ok.
I continue to strongly encourage work to rectify this.

Apologies for the breakage. When I clicked through it seemed it was just the failures I'd been seeing on every PR all day.
We can't stop work because infrastructure is flaky, and submitting anything to this codebase needs either a deep appreciation of the current state of too much infrastructure or guesswork when things are ok.
I continue to strongly encourage work to rectify this.

Agreed that we need to make our tests both faster and more reliable.


Add Docker documentation to README.md

Thanks for the contribution. In this case however we cannot merge as the guidelines and instructions are related to the usage of Docker and not about the Sample application.
We still welcome in the future your feedback and contributions in this and others of our open source projects. Thank you!


[Gally]: master <- dev

Automatically created by Git-Ally

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[DRAFT] New function suggestion in RSACryptoServiceProvider

Summary
Work Item(s)
Fixes #

@microsoft-github-policy-service agree company="Microsoft"
From: microsoft-github-policy-service[bot] @.>
Sent: Wednesday, January 3, 2024 10:55 AM
To: microsoft/BCApps @.>
Cc: Vičar Marek @.>; Mention @.>
Subject: Re: [microsoft/BCApps] [DRAFT] New function suggestion in RSACryptoServiceProvider (PR #409)
EXTERNAL
@marekvicarhttps://github.com/marekvicar please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
@microsoft-github-policy-service agree [company="{your company}"]
Options:

(default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

(when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"
Contributor License Agreement
Contribution License Agreement
This Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
and conveys certain license rights to Microsoft Corporation and its affiliates (“Microsoft”) for Your
contributions to Microsoft open source projects. This Agreement is effective as of the latest signature
date below.

Definitions.
“Code” means the computer software code, whether in human-readable or machine-executable form,
that is delivered by You to Microsoft under this Agreement.
“Project” means any of the projects owned or managed by Microsoft and offered under a license
approved by the Open Source Initiative (www.opensource.orghttp://www.opensource.org).
“Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any
Project, including but not limited to communication on electronic mailing lists, source code control
systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
discussing and improving that Project, but excluding communication that is conspicuously marked or
otherwise designated in writing by You as “Not a Submission.”
“Submission” means the Code and any other copyrightable material Submitted by You, including any
associated comments and documentation.
Your Submission. You must agree to the terms of this Agreement before making a Submission to any
Project. This Agreement covers any and all Submissions that You, now or in the future (except as
described in Section 4 below), Submit to any Project.
Originality of Work. You represent that each of Your Submissions is entirely Your original work.
Should You wish to Submit materials that are not Your original work, You may Submit them separately
to the Project if You (a) retain all copyright and license information that was in the materials as You
received them, (b) in the description accompanying Your Submission, include the phrase “Submission
containing materials of a third party:” followed by the names of the third party and any licenses or other
restrictions of which You are aware, and (c) follow any other instructions in the Project’s written
guidelines concerning Submissions.
Your Employer. References to “employer” in this Agreement include Your employer or anyone else
for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
Submission is made in the course of Your work for an employer or Your employer has intellectual
property rights in Your Submission by contract or applicable law, You must secure permission from Your
employer to make the Submission before signing this Agreement. In that case, the term “You” in this
Agreement will refer to You and the employer collectively. If You change employers in the future and
desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
and secure permission from the new employer before Submitting those Submissions.
Licenses.

Copyright License. You grant Microsoft, and those who receive the Submission directly or
indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the
Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute
the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third
parties.
Patent License. You grant Microsoft, and those who receive the Submission directly or
indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license under
Your patent claims that are necessarily infringed by the Submission or the combination of the
Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
import or otherwise dispose of the Submission alone or with the Project.
Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
granted by implication, exhaustion, estoppel or otherwise.

Representations and Warranties. You represent that You are legally entitled to grant the above
licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
have disclosed under Section 3). You represent that You have secured permission from Your employer to
make the Submission in cases where Your Submission is made in the course of Your work for Your
employer or Your employer has intellectual property rights in Your Submission by contract or applicable
law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of which
You later become aware that would make Your representations in this Agreement inaccurate in any
respect.
Information about Submissions. You agree that contributions to Projects and information about
contributions may be maintained indefinitely and disclosed publicly, including Your name and other
information that You submit with Your Submission.
Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
defenses of lack of personal jurisdiction and forum non-conveniens.
Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
supersedes any and all prior agreements, understandings or communications, written or oral, between
the parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.

—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/BCApps/pull/409#issuecomment-1875103044, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AL473VMMQG3TRUVB73DLMR3YMUTGXAVCNFSM6AAAAABAHRWIM2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZVGEYDGMBUGQ.
You are receiving this because you were mentioned.Message ID: @.***>

@marekvicar, this one has been in draft for just about a year now. Will you have time to take if out of draft anytime soon?

@marekvicar, this one has been in draft for just about a year now. Will you have time to take if out of draft anytime soon?

@JesperSchulz just saw this related PR https://github.com/microsoft/BCApps/issues/309

@JesperSchulz
Hi! Since this requirement could not be solved by AL standard functions, we used a completely different solution. Now I don't understand what is the status of this draft? Should be canceled or will this feature somehow be implemented into the system application from MS?

Ah, I was missing the link. Thanks @DevHarmonize for providing it 😊 Let me check on the status.

I will discuss with @SBalslev in the coming weeks. There's a "right", but expensive solution, and there's a "workaround", which would come cheaper. We will hopefully soon be able to conclude.


add run_exports

Checklist

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

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

@conda-forge-admin, please rerender

It seems that the repo patch went through, so once we agree on the pinning we can move forward

Out of curiosity, why did you move this to Azure?

Travis was being slow and didn't start the job. We have more machines in count on azure

@hmaarrfk has no time for slow bots! 😆

Thank you @hmaarrfk!


Change Android RTP button label to upper case in Blog 2.22 text

This PR corrects text in the blog announcements for CWA 2.22

https://www.coronawarn.app/en/blog/2022-05-04-cwa-2-22/ "CWA 2.22: Rapid test profiles for family members"
https://www.coronawarn.app/de/blog/2022-05-04-cwa-2-22/ "CWA 2.22: Schnelltest-Profile für Familienmitglieder"

In Android the button to create a rapid test profile, as seen in the screenshots, is labelled:

"+ RAPID TEST PROFILE" (English)
"+ SCHNELLTEST-PROFIL" (Deutsch)

The blog texts are aligned in this PR to conform to the respective screenshots showing creation of an RTP. In the English version it was confusing to read the description of the label in complete lower case in the text as "+ rapid test profile" when it appears in the app completely in upper case as "+ RAPID TEST PROFILE".

@MikeMcC399 Thanks!

@dsarkar
The deployment seems to be hanging. See https://github.com/corona-warn-app/cwa-website/actions/runs/2299780136.

Also https://github.com/corona-warn-app/cwa-website/issues/2861.

@MikeMcC399 Indeed, thanks. We are aware of the issue and are still investigating.


Fix caller token propagated test to work for release testing (on demand clusters).

clusters).

#839  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @rohinb2 and the rest of your teammates on  Graphite

Merge activity

May 28, 10:09 PM EDT: @rohinb2 started a stack merge that includes this pull request via Graphite.


Update README.md

Generally speaking, there is no AEP device in the compilation environment, so you need to skip the test when compiling with -DskipTests to avoid troubles for developers.
The spark.shuffle.manager main class has been updated for a long time, and now the documentation is wrong, and users cannot use this configuration to run PMoF.

Thanks for your PR!
The spark.shuffle.manager name should be modified as per your suggestion.
For the test, it's useful for those who have the hardware ready, will keep it as is.

Hi，Eugene,Just like OAP https://github.com/Intel-bigdata/OAP/tree/branch-0.8-spark-2.4.x/oap-shuffle/RPMem-shuffle
the documentation in the RPMem  installation section is also “mvn install -DskipTests”，There are not many users with a complete hardware environment, and the compilation environment and the usage environment may not be the same one. We encountered trouble because of tests when we originally compiled.
In view of this, a better solution is to add instructions to skip the test, but you can add another piece of content to people who have hardware, such as mvn test, do you think this is appropriate?

@Eugene-Mark Hi，What's the next？


Not enough libraries in the #include part

The code uses std::setprecision(9) to set the precision of the output when printing the molar mass. Ensure that you have included the #iomanip(library) header for using std::setprecision

thank you @Yerima18, that's right the main is relying iomanip being indirectly included by iostream, which is bad practice.
but this main.cpp file is to be deleted in the next commit, as this project is focused on CHEM file.


Feature: add query to SqlTransferProcessStore

What this PR changes/adds
Adds full query capabilities to the SqlTransferProcessStore.
Why it does that
To be able to leverage the full flexibility of QuerySpec and Criterion through the Data Management API.
Further notes
List other areas of code that have changed but are not necessarily linked to the main feature. This could be method
signature changes, package declarations, bugs that were encountered and were fixed inline, etc.
Linked Issue(s)
Closes #1483
Checklist

[x] added appropriate tests?
[x] performed checkstyle check locally?
[ ] added/updated copyright headers?
[ ] documented public classes/methods?
[x] added/updated relevant documentation?
[ ] added relevant details to the changelog? (skip with label no-changelog)
[x] formatted title correctly? (take a look at the CONTRIBUTING and styleguide for details)

Codecov Report

Merging #1540 (7a3363a) into main (385be86) will decrease coverage by 0.04%.
The diff coverage is 79.38%.

@@            Coverage Diff             @@
##             main    #1540      +/-   ##
==========================================
- Coverage   67.16%   67.11%   -0.05%
==========================================
  Files         736      741       +5
  Lines       16139    16188      +49
  Branches     1048     1049       +1
==========================================
+ Hits        10839    10864      +25
- Misses       4823     4846      +23
- Partials      477      478       +1

Impacted Files
Coverage Δ

...aceconnector/sql/translation/JsonFieldMapping.java
0.00% <0.00%> (ø)

...nsferprocess/SqlTransferProcessStoreExtension.java
0.00% <0.00%> (ø)

...ore/schema/postgres/PostgresDialectStatements.java
0.00% <0.00%> (ø)

...process/store/schema/BaseSqlDialectStatements.java
97.14% <97.14%> (ø)

...nition/store/schema/postgres/CriterionMapping.java
14.28% <100.00%> (ø)

...tore/schema/postgres/ContractAgreementMapping.java
100.00% <100.00%> (ø)

...transferprocess/store/SqlTransferProcessStore.java
84.66% <100.00%> (-0.37%)
:arrow_down:

...rprocess/store/TransferProcessStoreStatements.java
100.00% <100.00%> (ø)

...cess/store/schema/postgres/DataRequestMapping.java
100.00% <100.00%> (ø)

...schema/postgres/ProvisionedResourceSetMapping.java
100.00% <100.00%> (ø)

... and 5 more

Continue to review full report at Codecov.

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


1,20,1 fabric

Uploading latest - 副本.log…

latest - 副本.log

Theres no crash here, what's the issue?

Unable to create map

What? I don't see how this is related to neruina


[PDI-15251] -VFS-based Variables do not work for "Group By" step's temp directory on Windows

@CodeOnCoffee, @deinspanjer, @bmorrise, @ddiroma, @pamval could you please take a look?

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
ant -Dtestreports.dir=bin/reports/unit-test -f engine/build.xml clean-all resolve jacoco && ant -Dtestreports.dir=bin/reports/integration-test -f engine/build.xml jacoco-integration checkstyle publish-local

Cleanup Commands
rm -r ~/.ivy2/local || echo no publish local to remove

Changed files
  engine/test-src/org/pentaho/di/trans/steps/groupby/GroupByTest.java

Unit test coverage change
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.
org.pentaho.di.core.auth.core.impl.DefaultAuthenticationConsumerFactory

Branch Change:  + 7.14%
Complexity Change:  + 7.69%

org.pentaho.di.job.entries.evalfilesmetrics.JobEntryEvalFilesMetrics

Branch Change: -.78%:small_red_triangle_down:
Complexity Change: -1.03%:small_red_triangle_down:
Instruction Change: -.16%:small_red_triangle_down:

org.pentaho.di.job.entries.getpop.MailConnectionMeta

Branch Change:  + 2.00%
Complexity Change:  + 2.82%
Instruction Change:  + .59%

org.pentaho.di.job.entries.sql.JobEntrySQL

Instruction Change:  + 3.28%
Line Change:  + 3.87%

org.pentaho.di.trans.step.StepMeta

Instruction Change: -.19%:small_red_triangle_down:
Line Change: -.27%:small_red_triangle_down:

org.pentaho.di.trans.steps.checksum.CheckSumMeta

Instruction Change: -.11%:small_red_triangle_down:

org.pentaho.di.trans.steps.combinationlookup.CombinationLookupMeta

Instruction Change:  + .04%

org.pentaho.di.trans.steps.constant.ConstantMeta

Instruction Change:  + .10%

org.pentaho.di.trans.steps.dbproc.DBProcMeta

Instruction Change:  + .11%

org.pentaho.di.trans.steps.dimensionlookup.DimensionLookupMeta

Branch Change:  + .66%
Complexity Change:  + .41%
Instruction Change:  + .50%
Line Change:  + .24%

org.pentaho.di.trans.steps.groupby.GroupBy

Branch Change:  + 1.67%
Complexity Change:  + 2.39%
Instruction Change:  + 4.75%
Line Change:  + 4.61%
Method Change:  + 7.25%

org.pentaho.di.trans.steps.groupby.GroupByMeta

Branch Change:  + 2.08%
Complexity Change:  + 2.11%
Instruction Change:  + .14%
Line Change:  + .37%

org.pentaho.di.trans.steps.insertupdate.InsertUpdateMeta

Instruction Change: -.05%:small_red_triangle_down:

org.pentaho.di.trans.steps.memgroupby.MemoryGroupByMeta

Branch Change:  + 1.18%
Complexity Change:  + 1.35%

org.pentaho.di.trans.steps.replacestring.ReplaceStringMeta

Instruction Change: -.07%:small_red_triangle_down:

org.pentaho.di.trans.steps.rowgenerator.RowGeneratorMeta

Instruction Change:  + .08%

org.pentaho.di.trans.steps.singlethreader.SingleThreaderMeta

Instruction Change: -.08%:small_red_triangle_down:

org.pentaho.di.trans.steps.sort.SortRowsMeta

Instruction Change:  + .08%

org.pentaho.di.trans.steps.webservices.WebServiceMeta

Branch Change: -1.79%:small_red_triangle_down:
Complexity Change: -1.19%:small_red_triangle_down:
Instruction Change: -.07%:small_red_triangle_down:

org.pentaho.di.trans.Trans

Branch Change: -.10%:small_red_triangle_down:
Complexity Change: -.14%:small_red_triangle_down:
Instruction Change: -.09%:small_red_triangle_down:
Line Change: -.11%:small_red_triangle_down:

Integration test coverage change
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.
org.pentaho.di.trans.steps.groupby.GroupBy

Branch Change: -.00%:small_red_triangle_down:
Complexity Change: -.04%:small_red_triangle_down:
Instruction Change: -.03%:small_red_triangle_down:
Line Change: -.04%:small_red_triangle_down:
Method Change: -1.24%:small_red_triangle_down:

@CodeOnCoffee, @pamval, @mchen-len-son any updates? - regarding wingman: it seems it's "floating" tests and does not relate to the changes of PR.

@matthewtckr @wseyler @e-cuellar @mdamour1976 please review


Normalization

Hello, everyone. I have limited knowledge of fMRI andI want to use fMRIprep instead of spm12 to preprocess and analyze massive fMRI data. But I found that the final output of the two software are different, possibly for one reasons:

Normalization process

I also read the fMRIprep paper, which mentioned the difference between smoothing with other pipelines. The problem may arise in normalization . The final image of spm12 is 61-73-61, while that of fMRIprep is 75-77-45, which can not calculate and extract time series on ROI with AAL template. Please help me to see what caused it. Thank you.

Hi @Xin-cqu,
I can't talk about SPM12, but I'm pretty sure that the output of fMRIPrep is:

In MNI152NLin2009cAsym space (you'll find a reference and a full description of what fMRIPrep did in the "Methods" section of each participant's html report).
It seems to me you used fMRIPrep defaults, so that grid will be fitting the MNI space but keeping the voxel size of the original image. Since fMRIPrep 1.4.0 we've unified the way you can control the output resolution of images.

If your goal is using the AAL atlas, I'd recommend you to run fMRIPrep making sure you include the following:
--output-spaces MNI152NLin6Asym:res-2

That will ensure you use FSL's MNI (identified with that MNI152NLin6Asym label) and resample in the original resolution number 2 of the template (which happens to be the 2mm isotropic, for which there are AAL regions). You can add other spaces to this --output-spaces flag. E.g., adding MNI152NLin2009cAsym or MNI152NLin2009cAsym:native (these two are equivalent) would generate your runs on MNI space with the grid of 75x77x45 you've seen this far.
If you can allow some time, I could give it a try and add AAL to TemplateFlow (the repository from which fMRIPrep pulls templates down). That would make it much easier for you to put all of this together.

Hello, @oesteban
Thank you for your help. I'll try again as you told me. Wait until the results come out and then give another feedback. I will also read the documentation in detail to try to figure out how these custom processes should be set up. It would be better if the authorities could give a detailed tutorial including specific examples, just personal opinions.

Additionally, the dimension of the output image is related to the bounding box. So, is  there an option to specify bounding box provided by fMRIprep?

is there an option to specify bounding box provided by fMRIprep?

Not sure I understand the question, but outputs of fMRIPrep can be of two forms:

(default) The bounding vox is defined by the template image, and then a grid is fitted so that the final image resolution is the same as for the original BOLD image. Examples --output-spaces MNI152NLin6Asym or --output-spaces MNI152NLin6Asym:native

The bounding-box and the gridding are defined by the template image. Example: --output-spaces MNI152NLin6Asym:res-2, for the 2mm isotropic resolution.


logging

Does anyone log each exchanges data to a separate log file?  If so would you mind sharing the log configuration?

Not sure how this would work, but you might try googling logback different file for different packages or something like that.


Why can HoYoStudio extract AnimationClip? This is not possible

what? it is possible, these tools can do it

Greetings,
what error message are you getting ?


fix stream test on osx

issue #462 "zmq on Osx El Capitan" brought to my attention a broken stream test on osx.
I think maybe they've changed the http parser a bit since this test was originally written, since doing some different style header parsing on the response from a STREAM socket type seems to resolve it

also let's replace iojs version with with node 4 on the travis matrix

There is a Node 5 nowadays. io.js 3 is sort of being maintained still, unofficially, but it is virtually the same as Node 4.
On November 6, 2015 11:31:35 AM GMT+02:00, Bent Cardan<EMAIL_ADDRESS>wrote:

also let's replace iojs version with with node 4 on the travis matrix

Reply to this email directly or view it on GitHub:
https://github.com/JustinTulloss/zeromq.node/pull/463#issuecomment-154358771

oh they put 5 out already? ok lets add 5 then and use iojs as a virtual 4.
I'll just rebase another commit and send this travis matrix into another hour and half wait before it finishes

Go with 4 rather than io.js, if there has to be a dichotomy. In particular 4.2 (although there should not be any new minors in the 4 series) since that is LTS and will be sypported for 17 more months.
On November 6, 2015 11:39:48 AM GMT+02:00, Bent Cardan<EMAIL_ADDRESS>wrote:

oh they put 5 out already? ok lets add 5 then and use iojs as a virtual
4.
I'll just rebase another commit and send this travis matrix into
another hour and half wait before it finishes

Reply to this email directly or view it on GitHub:
https://github.com/JustinTulloss/zeromq.node/pull/463#issuecomment-154362437

Oh, and if it were possible to somehow install libzmq and libsodium without root, or to use a premade package, it would be possible to use the new container based architecture on Travis which is an order of magnitude faster in throughput.
On November 6, 2015 11:39:48 AM GMT+02:00, Bent Cardan<EMAIL_ADDRESS>wrote:

oh they put 5 out already? ok lets add 5 then and use iojs as a virtual
4.
I'll just rebase another commit and send this travis matrix into
another hour and half wait before it finishes

Reply to this email directly or view it on GitHub:
https://github.com/JustinTulloss/zeromq.node/pull/463#issuecomment-154362437

well with ldconfig being a sudo command on linux we would need to use some local prefix variable..
I suppose something like
$ export LDHACKING='/whatever/path/we/have/on/travis'
$ ./configure --prefix=$LDHACKING
$ make
$ make install

then when it comes time to do npm install zmq, we might be able to trick pkg-config with:
LD_LIBRARY_PATH=$LDHACKING npm install

Would love to see this move forward :)

@ronkorving thanks, I appreciate that..
about this STREAM stuff. ZeroMQ STREAM msgs are NOT semantically standard or RFC compliant HTTP protocol request/responses. It's not quite HTTP here, though seems to work that way

ok cool, I just figured out a much simpler way to install libzmq and libsodium without root.
so i'm gonna re-open a fresh PR with that in few mins. plus let's deal with ZMQ_STREAM stuff separately from setting up the root-free travis matrix.
stay tuned :)