Charge gas according to actual resources consumed

EVM and Starknet have different ways of pricing resource usages due to the underlying architecture differences. As such, there cannot be a 1 <> 1 mapping between the EVM gas consumed and the Starknet fee to pay.
As such, we need to design a mechanism ensuring that in the majority of cases, the fee charged for the user (based on gas price and gas used) matches the actual fee, paid by our relayers, for the execution of the starknet transcation.
### Tasks
- [ ] check if is possible to restrict tx usage (pre1559 tx) on sdks and wallets (starting from metamask rabby)
- [ ] how the wallet works (base fee per gs, max prio)
- [ ] how sdks and wallets will be impacted from the evm specs broken

EVM and Starknet have different ways of pricing resource usages due to the underlying architecture differences. As such, there cannot be a 1 <> 1 mapping between the EVM gas consumed and the Starknet fee to pay.
As such, we need to design a mechanism ensuring that in the majority of cases, the fee charged for the user (based on gas price and gas used) matches the actual fee, paid by our relayers, for the execution of the starknet transcation.

Note that an option is also to use our STRK allocation to sponsor part of our users' transactions as part of an on-chain incentive to boost usage. At least until Stwo/Cairo native (they will bring L2 fees down)

To ensure that the network only accepts pre-EIP1559 transactions, it's necessary to make the wallets understand that the network does not accept EIP1559 transactions. This is done in the network definition by specifying that the network does not support EIP1559, which will automatically allow wallets to send the correct transactions.
For example, MetaMask stores the data in a Redux state with metadata, which is used, for example, here and here to verify whether the network supports EIP1559 or not.
An example of a configuration that does not accept EIP1559 is the following:
{
    name: "Mordor Testnet",
    title: "Ethereum Classic Mordor Testnet",
    status: "active",
    chain: "ETC",
    icon: "ethereumclassictestnet",
    rpc: [
        "https://rpc.mordor.etccooperative.org",
        "https://geth-mordor.etc-network.info"
    ],
    features: [
        {
            name: "EIP155"
        }
    ],
    faucets: [
        "https://easy.hebeswap.com/#/faucet",
        "https://faucet.mordortest.net"
    ],
    nativeCurrency: {
        name: "Mordor Ether",
        symbol: "METC",
        decimals: 18
    },
    infoURL: "https://ethereumclassic.org/development/testnets",
    shortName: "metc",
    chainId: 63,
    networkId: 7,
    slip44: 1,
    explorers: [
    {
        name: "blockscout-mordor",
        url: "https://etc-mordor.blockscout.com",
        standard: "EIP3091"
    },
    {
        name: "etcnetworkinfo-expedition-mordor",
        url: "https://explorer-expedition.etc-network.info/?network=Ethereum+Classic+at+etc-network.info+GETH+Mordor",
        standard: "none"
    }
    ]
}

Therefore, to exclude it, it is necessary to modify the configuration file by not including the EIP1559 feature, or by not inheriting from a network that accepts it.
Here is an example of a network that does accept EIP1559:
{
  "name": "Ethereum Mainnet",
  "chain": "ETH",
  "rpc": [
    "https://mainnet.infura.io/v3/${INFURA_API_KEY}",
    "https://api.mycryptoapi.com/eth"
  ],
  "faucets": [],
  "nativeCurrency": {
    "name": "Ether",
    "symbol": "ETH",
    "decimals": 18
  },
  "features": [{ "name": "EIP155" }, { "name": "EIP1559" }],
  "infoURL": "https://ethereum.org",
  "shortName": "eth",
  "chainId": 1,
  "networkId": 1,
  "icon": "ethereum",
  "explorers": [{
    "name": "etherscan",
    "url": "https://etherscan.io",
    "icon": "etherscan",
    "standard": "EIP3091"
  }]
}

From the SDKs' perspective, the main SDKs allow sending pre-EIP1559 transactions, but we need to ensure that EIP1559 transactions are rejected on the RPC side.


[ngResource] should initialise data when response data is array

ngResource#L557, causes error when action is array and accessing from an instance.
product = $resource "/v1/products/:id", {},
    years:
      url: "/v1/products/:id/years"
      isArray: true

product = Product.get id: 1, ->
    product.$years()

Another problem also is that :id is not set and you still need to:
product.$years(id: product.id)

Is this correct?

@itsmechlark it is not very clear what your problems is... Could you please provide a minimal reproduce scenario using http://plnkr.co/ or similar?

@pkozlowski-opensource, here is the scenario http://embed.plnkr.co/CHVzHB/preview.

Error raise TypeError: value.push is not a function at ngResource#L598

@itsmechlark ngResource is there to work with RESTful endpoints, but you seem to be trying to use it as a generic backend-access method. Specifically, ngResource works with collections containing objects, so returning [2015, 2014, 2013] doesn't make much sense. You would be probably better off using $http here.


All visualization plots need static axes (undraggable/unscrollable)

In layout.xaxis and layout.yaxis
fixedrange: true
will solve this
Could we somehow add it at a higher level in PlotlyPlot?

I think it can probably be done at PlotlyPlot component using spread operator, if those changes target for all plots

made a PR at web-components repo, https://github.com/VEuPathDB/web-components/pull/146

This is now approved and merged so I will close this issue


HHH-11138 - Upgrade to Javassist 3.21 (Java 9 support)

I did this as a PR because we need to decide what version to apply this change to.

Looks safe for master? Why not?

(except the "SNAPSHOT" dependency of course)

@sebersole sorry I forgot about this PR. Seems obsolete? I recently updated ORM to Javassist 3.22.0-GA (HHH-12048).

This has been in 5.2 and 5.3 for a while since https://github.com/hibernate/hibernate-orm/commit/9ed4438f172bf28d9fb3ab7278c3c04393c60ac4, closing it as stale.


Blank list

I follow the example from your project and documentation and got a blank screen.
Code -
import React from 'react';
import {Text} from 'react-native';
import BigList from 'react-native-big-list';

const data = [
  {label: '1', value: 1},
  {label: '2', value: 2},
  {label: '3', value: 3},
  {label: '4', value: 4},
  {label: '5', value: 5},
];
const renderItem = ({item, index}) => (
  <>
    <Text>1</Text>
    <Text>{item.label}</Text>
    <Text>{item.value} </Text>
  </>
);
const renderEmpty = () => <Text>Empty</Text>;
const renderHeader = () => <Text>Header</Text>;
const renderFooter = () => <Text>Footer</Text>;

const HomeScreen = () => {
  return (
    <>
      <Text>hi</Text>
      <BigList
        data={data}
        renderItem={renderItem}
        renderEmpty={renderEmpty}
        renderHeader={renderHeader}
        renderFooter={renderFooter}
        itemHeight={50} // Required (default 0)
        headerHeight={90} // Required to show header
        footerHeight={100} // Required to show footer
      />
    </>
  );
};

export default HomeScreen;

Config -
"dependencies": {
    "react": "17.0.2",
    "react-native": "0.65.2",
    "react-native-big-list": "^1.4.0"
  },
  "devDependencies": {
    "@babel/core": "^7.12.9",
    "@babel/runtime": "^7.12.5",
    "@react-native-community/eslint-config": "^2.0.0",
    "babel-jest": "^26.6.3",
    "eslint": "7.14.0",
    "jest": "^26.6.3",
    "metro-react-native-babel-preset": "^0.66.0",
    "react-native-codegen": "^0.0.7",
    "react-test-renderer": "17.0.2"
  },

Result -

Same issue in:
"react": "17.0.2",
"react-native": "0.66.1"
"react-native-big-list": "^1.4.3",

Try use inside a View with flex: 1

+1 same issue
renderHeader and Footer worked but item is not

I had a case of blank list in an app that I am working on, using react-navigation, I had two bottom tab routes, one with the list of collections (but not only) and the other being the settings, If I clicked on settings and got back to collections, the list would be there, but if I entered in another route through settings, in this case, accounts route, and got back to collections after, the list would be blank (only the BigList), every time.
Only fix was to set the Collections screen route to unmount on blur through react-navigation.


CLOUDP-221979: QA improvements

All Submissions:

[x] Have you signed our CLA?
[ ] Put closes #XXXX in your comment to auto-close the issue that your PR fixes (if there is one).
[ ] Update docs/release-notes/release-notes-template.md if your changes should be included in the release notes for the next release.

Helm failed because of missing CRDs I guess. I'll prepare a PR for Helm-charts


Can't install via Config - Integration

Can't install via Config - Integration. On name press dialogue with integrations list just re-appears.
Here is error in server's log:
Logger: aiohttp.server
Source: custom_components/xiaomi_gateway3/config_flow.py:51
First occurred: 22:15:49 (1 occurrences)
Last logged: 22:15:49
Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/aiohttp/web_protocol.py", line 418, in start
resp = await task
File "/usr/local/lib/python3.8/site-packages/aiohttp/web_app.py", line 458, in _handle
resp = await handler(request)
File "/usr/local/lib/python3.8/site-packages/aiohttp/web_middlewares.py", line 119, in impl
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 18, in request_context_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 72, in ban_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 127, in auth_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 129, in handle
result = await result
File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 136, in post
return await super().post(request)
File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 60, in wrapper
result = await method(view, request, *args, **kwargs)
File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 69, in post
result = await self._flow_mgr.async_init(
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 131, in async_init
result = await self._async_handle_step(
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 204, in _async_handle_step
result: Dict = await getattr(flow, method)(user_input)
File "/config/custom_components/xiaomi_gateway3/config_flow.py", line 51, in async_step_user
if 'devices' in self.hass.data[DOMAIN]:
KeyError: 'xiaomi_gateway3'

Yep, have the same issue but different error:
020-10-12 00:21:32 ERROR (MainThread) [homeassistant.config_entries] Error occurred loading configuration flow for integration xiaomi_gateway3: No module named 'asyncio.exceptions'

Primary interrogation not deleted before attempt.
asyncio.exceptions on python-3.7.7 (HassWP) not present.

Fixed in v0.6.1

@AlexxIT yes, works fine but you need update requirements to python 3.8 (in 3.7 no module named 'asyncio.exceptions').

0.6.1 works fine for me

0.6.1 not working on python 3.7

0.6.1 not working on python 3.7
On 3.7.7 works fine.

0.6.1 not working on python 3.7
On 3.7.7 works fine.

https://www.home-assistant.io/blog/#python-37-deprecated


Building Impossible

The project cannot be built, first, since mvnw isn't executable (just do chmod +x mvnw and commit), and second, since an error appears during compilation:

[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project e2etest: Could not resolve dependencies for project de.unistuttgart.t2:e2etest:jar:1.3.1-SNAPSHOT
[ERROR] dependency: de.unistuttgart.t2:order:original:1.3.1-SNAPSHOT (compile)
[ERROR] 	Could not find artifact de.unistuttgart.t2:order:original:1.3.1-SNAPSHOT
[ERROR] dependency: de.unistuttgart.t2:inventory:original:1.3.1-SNAPSHOT (compile)
[ERROR] 	Could not find artifact de.unistuttgart.t2:inventory:original:1.3.1-SNAPSHOT
[ERROR] dependency: de.unistuttgart.t2:payment:original:1.3.1-SNAPSHOT (compile)
[ERROR] 	Could not find artifact de.unistuttgart.t2:payment:original:1.3.1-SNAPSHOT

Is there an easy fix for this?

Sorry, my bad - with install instead of package, it works (although its surprising that just packaging doesn't work). But the executable flag still needs to be set here.

Thank you for creating all the issues!
I have now fixed the issue that mvnw wan't executable by using git update-index --chmod=+x mvnw in all repositories.
The Maven command install is required instead of package because of how the build for e2e-tests works.
package works if you exclude e2e-tests from the build:
./mvnw clean package -pl \!e2e-tests -DskipTests=true


[logstash] mark 8.x active

https://github.com/elastic/logstash/releases/tag/v8.15.1

gonna ship it for now.


Eshop error 005-5602 on region changed 2DS

Hi, I have a Japanese 2DS, I followed Plailect's guide exactly to install A9LH and change region to US.
After all done, I create a new NID on new region, and then I access eshop, I get the error 005-5602.
Please tell me how to fix this? Thank you very much!

Quote from the guide:
"Note that occasionally the eShop will inexplicably still not work for devices that it should work for. This is entirely to do with Nintendo’s servers, and I really do not have any control over it."

The problem is that, I have over 10 devices (old 3DS, old 3DS XL, 2DS), and none of them are able to access eshop after region change, all have the save error 005-5602. So I want to ask if anyone really able to access eshop after region change or just theory? And if yes, did they follow Plailect's guide like me or some other guide? Thanks.

Based on the error code, this sounds like the error is caused by forgetting to set your country/region in settings to a country in the region you switched to. So if you switched from JPN -> EUR, you need to go into settings and set your country and region to somewhere in Europe.

I'm changing my 2DS from JP to US. I've changed the region in profile setting to US, accept all agreements, and then update to latest FW (11.2). After all that, I still get the same error code 005-5602. If you have any suggestion please tell me and I'll try that. Thank you very much!

estimated friend
i have the same problem with 50 3ds japan to usa, did you get some solution to go to eshop after the change.

Hi I have the same problem error code 005-5602 after region change from JP to EU on new 3DS LL. Appreciate it if you let me know if there is a solution to this. Thank you

@Parham75 As has been said earlier in this issue thread, that error would indicate that your region setting in your profile does not match the region of your NNID. Did you make a new NNID after changing your region?

Reading through the region change guide, it states that the process will unlink the NNID. If the process is not automatically unlinking the NNID, it would be a good idea to add those steps to ensure this issue doesnt happen.
If unlinking is not the only step, but creating a new NNID is required, this should also be part of the steps, imo.
Thoughts?

Anyone solved this problem yet?? I have searched (i think) the entire community about the "region changed console and accessing the eshop" and i haven't got the solution:( pleasee help:(

its not a problem to be solved. the warnings are clear in the guide. region change will (almost) always break eshop access.


Restrict counter column excess spanning

The PR proposes to restrict the excessive span of column bearing row counters upon supplemental unoccupied space.

@ashenm thanks - this looks good.


proposal: atomic: describe return value of atomic.Bool CompareAndSwap

Proposal Details
This is the current documentation for atomic.Bool CompareAndSwap:
// CompareAndSwap executes the compare-and-swap operation for the boolean value x.
func (x *Bool) CompareAndSwap(old, new bool) (swapped bool) {
	return CompareAndSwapUint32(&x.v, b32(old), b32(new))
}

This only happens for the special case Bool: From reading only the types bool * bool -> bool it is not clear if the return value is the first or second parameter, or some other bool value. The documentation comment just states the obvious (CompareAndSwap does compare-and-swap) and swapped is ambiguous IMHO b/c it could mean the swapped-in value new, the swapped-out value old, or that the swap operation was done.
The proposal is to clarify the doc comment as e.g. (assuming this is even correct)
// CompareAndSwap executes the compare-and-swap operation for the boolean value x.
// It returns true if the swap was done.

I'm not native English speaking, so, there is probably better wording.
References

https://github.com/golang/go/issues/50860
https://github.com/golang/go/issues/50859

In this case the name of the result tells you the meaning of the result.  This is one of the cases where it is useful to name a result parameter: for documentation.

There's no reason for this to be a proposal, taking it out of the proposal process.


Question about the error when running make command

Hi, I encountered this error when I am running the make command

I'm suspecting its because kconfig.h does not exist at /lib/modules like what was stated in the system requirements

But, I'm not really sure how I can resolve this issue as I'm a new Linux user, I've checked that the linux-headers is installed and the kconfig.h exists at /usr/src/linux-headers-4.19.0-20-common/include/linux. Anyone has any idea how I can resolve this issue? Thanks in advance.

Hey @flairekq ,
Can you paste the output of uname -r please ?
Thanks !

Hey @flairekq , Can you paste the output of uname -r please ? (I'm wondering if your running kernel is out of sync with the headers you downloaded) Thanks !

Hi!

Ho yeah, so you're definitely out of sync 🎉 Your running kernel is 5.10 and the headers you pointed to are from a 4.19 kernel. Can you install the headers of your kernel ? (probably something like sudo apt install linux-headers-$(uname -r) )

Oh wait omg im sorry i forgot that 4.19 kernel is on another laptop. The current one is this:

Btw, I tried removing all the build in the MakeFile but it still has the same error.

Instead of this:
[...]
		-I/lib/modules/$$(uname -r)/build/include \
		-I/lib/modules/$$(uname -r)/build/include/uapi \
		-I/lib/modules/$$(uname -r)/build/include/generated/uapi \
		-I/lib/modules/$$(uname -r)/build/arch/x86/include \
		-I/lib/modules/$$(uname -r)/build/arch/x86/include/uapi \
		-I/lib/modules/$$(uname -r)/build/arch/x86/include/generated \
[...]

Hmm, still has the same error

Hmm, still has the same error

Can you check where your kernel headers are?
For me including "-I/usr/src/linux-hwe-5.15-headers-5.15.0-73/include " in the make file worked.


[OpenTelemetry Instrumentation] Rush update failing in nightly runs

OpenTelemetry Instrumentation Share nightly test runs are failing with:

Error message:
 ERR_PNPM_PEER_DEP_ISSUES  Unmet peer dependencies
Stack trace:
@rush-temp/azure-opentelemetry-instrumentation-azure-sdk-test 0.0.0
 ERR_PNPM_PEER_DEP_ISSUES  Unmet peer dependencies
.
├─┬ @rush-temp/azure-opentelemetry-instrumentation-azure-sdk-test
│ ├─┬ @opentelemetry/sdk-trace-base
│ │ ├── ✕ unmet peer<EMAIL_ADDRESS><1.4.0": found 1.4.0
│ │ ├─┬ @opentelemetry/core
│ │ │ └── ✕ unmet peer<EMAIL_ADDRESS><1.4.0": found 1.4.0
│ │ └─┬ @opentelemetry/resources
│ │   └── ✕ unmet peer<EMAIL_ADDRESS><1.4.0": found 1.4.0
│ └─┬ @opentelemetry/sdk-trace-node
│   ├── ✕ unmet peer<EMAIL_ADDRESS><1.4.0": found 1.4.0
│   ├─┬ @opentelemetry/context-async-hooks
│   │ └── ✕ unmet peer<EMAIL_ADDRESS><1.4.0": found 1.4.0
│   ├─┬ @opentelemetry/propagator-b3
│   │ └── ✕ unmet peer<EMAIL_ADDRESS><1.4.0": found 1.4.0
│   └─┬ @opentelemetry/propagator-jaeger
│     └── ✕ unmet peer<EMAIL_ADDRESS><1.4.0": found 1.4.0
└─┬ @rush-temp/monitor-opentelemetry-exporter
└─┬ @opentelemetry/sdk-metrics
└── ✕ unmet peer<EMAIL_ADDRESS><1.4.0": found 1.4.0
The command failed:
/mnt/vss/_work/1/s/common/temp/pnpm-local/node_modules/.bin/pnpm install --store /mnt/vss/_work/1/s/common/temp/pnpm-store --no-prefer-frozen-lockfile --strict-peer-dependencies
ERROR: Error: The command failed with exit code 1

For more details check here:

https://dev.azure.com/azure-sdk/internal/_build/results?buildId=2113063&view=results

possibly fixed by PR #24459 already?

Yup, ran the pipeline against main and it is passing now. https://dev.azure.com/azure-sdk/internal/_build/results?buildId=2115802&view=results (MS Internal Only)


bsp: Reach 'not reached'

panic: not reached

goroutine 18 [running]:
github.com/hajimehoshi/ebiten/internal/bsp.(*Page).Free(0xc42008c328, 0xc421968080)
        /Users/hajimehoshi/go/src/github.com/hajimehoshi/ebiten/internal/bsp/bsp.go:160 +0x134
github.com/hajimehoshi/ebiten/internal/bsp.(*Page).Free(0xc42008c328, 0xc422a8da00)
        /Users/hajimehoshi/go/src/github.com/hajimehoshi/ebiten/internal/bsp/bsp.go:165 +0xfa
github.com/hajimehoshi/ebiten/internal/bsp.(*Page).Free(0xc42008c328, 0xc422a8dac0)
        /Users/hajimehoshi/go/src/github.com/hajimehoshi/ebiten/internal/bsp/bsp.go:165 +0xfa
github.com/hajimehoshi/ebiten.(*sharedImagePart).Dispose(0xc421a7c0e0)
        /Users/hajimehoshi/go/src/github.com/hajimehoshi/ebiten/shared.go:46 +0x44
github.com/hajimehoshi/ebiten.(*Image).Dispose(0xc422a780e0, 0x0, 0x0)
        /Users/hajimehoshi/go/src/github.com/hajimehoshi/ebiten/image.go:342 +0x73
exit status 2

This is flakey: probably GCed image caused this.

Note: this happened on example/font with fixing text package's cacheLimit to 10.


request: Support for Minkowski functions

hi would ne nice if you are able to add the minkowski support to the wrapper.
Thanks

Thank you for your issue, I need some time

@Dexus  done in f07dc05 - does it work now for you?

Will check it next it in next zwo weeks, when I have a bit more time

Looks so far good. Thanks.


Make backtest work with pipeline

🚀 Feature Request
Backtest should work with pipeline not bare model. It makes backtest easier as a class.
Motivation
Backtest implements logic that are now a part of Pipeline class.
Proposal
--
Test cases
No response
Alternatives
No response
Additional context
No response
Checklist

[X] Added feature request
[X] Added motivation
[ ] Added proposal

Proposal:
We shoud just add backtest method to BasePipeline.
ToBe:
class BasePipeline:
    def __init__(self, horizon, *args, **kwargs):
          pass
    def fit(self, ts):
          pass
    def forecast(self):
          pass
    def backtest(self, ts: TSDataset, metrics: List[Metric], n_folds: int = 5, mode: str = "expand", n_jobs: int = 1):
          pass

In the next series we should remove TimeSeriesCrossvalidation


jshafer817/vjoy works with Snoothy/UCR but njz3/vjoy doesn't

Mentioned here as there is no issues tab on their repository pages

Have you asked njz3? He did a lot of work on force feedback that I never added because mainly my repository is as close as possible to the original vjoy...  The only reason I bought the code signing cert is because I use VJoy in my own project and so... I need it to work on Windows 10, but all I want is 2 buttons... I don't even care about the axis. =)

The vjoy v2.2.x branch (njz3) has a different memory stucture to exchange data with the driver, specifically made to fix a few bugs withing the FFB module. It is not completly backward compatible with the v2.1.x branch.
If you need to use v2.2.x, please update to the new vJoyInterface.dll (new SDK) to make it compatible.

Yes, it would be nice if njz3 could enable issues tab in Github project settings.
Ah, thanks for mentioning that! I could not wrap my head around why older driver did not work. I'm not fetching VJoy old code even from SVN and need to update njz3 fork, so it will compile Windows XP (retrogaming) again as it worked before.


added a function to the symbol trait called "native_symbol"

This allows you to get a copy of the underlying native symbol structure.
Pull for this issue: https://github.com/gimli-rs/object/pull/494

https://github.com/gimli-rs/object/issues/493

Ready to merge

Ill make these changes real quick

ok ran cargo fmt

Coverage failure is probably https://github.com/actions-rs/tarpaulin/issues/21


Generic data layer for etcd, migrated to etcd3 API.

Coverage increased (+5.9%) to 42.286% when pulling 543a5fe0cbfc06f286d2d25ca638690057c30690 on yegorch:master into bd01f2cf12a256f251980221e63c5a076913a175 on supergiant:master.


Waybar does not show custom command outputs

Hello.
This is maybe not a bug but rather something wrong with my script or configuration, however even after several hours I cannot figure out what is wrong. I have a script that should ping some servers and display that in the bar.
The script outputs in 5sec interval something like this:
{"text": "VPS: 41.0ms", "tooltip": "nothing", "class": "custom-normal", "alt": "nothing", "percentage": 50}
Relevant configuration:
"modules-center": [ "custom/pinger-vps" ]
"custom/pinger-vps": {
    "exec": "/data/home/suk/.config/sway/bar-ping/pinger.py vps my.vps.tld",
    "return-type": "json"
},

Full version of config: https://gist.github.com/sukovec/be1c47d32dac49097c3fa0e82171e61e
Full pinger.py script: https://gist.github.com/sukovec/a737766f4d17e8ace32413540f2ea14e
Waybar output: https://gist.github.com/sukovec/7c5939ddb764a21499b3c21dafcaeeb2

Hello. If you have not yet found the solution, try to eliminate "-" in the name of the module.
Rename something like "custom/pingervps"

Make sure you flush the output in the python script, otherwise it could buffer it for a long time..
try to add flush=True to your print


Support for custom activeClassName & tagName

This PR allows you to specify custom active class name & tag name for the dropdown components. This customization will allow to reuse the components seamlessly with UI frameworks like bootstrap without need of any custom css. Something like
<Dropdown component="li" activeClassName="open">
  <DropdownTrigger class="dropdown-toggle">
    {modeFormatted}
  </DropdownTrigger>
  <DropdownContent component="ul" class="dropdown-menu">

Test Mode

Live Mode

  </DropdownContent>
</Dropdown>

Before - Rendered DOM

            Test

Test Mode

Live Mode

After - Rendered DOM

        Test

Test Mode

Live Mode

This seems like a good change, but I want to think more on how to handle customizing class names. Maybe an object like so?
const customClassNames = {
  active: 'drop-active'
};

Though I guess the active class is the only one that can't be handled by setting className manually on the component....

@Fauntleroy Sounds like a good idea & one can configure the class globally

import Dropdown from 'react-simple-dropdown'

Dropdown.customClasses = {
  active: 'open'
}

@Fauntleroy Any updates here please ?

@selvagsz I haven't seen any other people request this feature, so until it gets more demand I've decided to pass on it.

I am maintaining a legacy project that has already token dropdown and dropdown--active class names, making it extremely to integrate with react-simple-dropdown. It would be awesome to have this feature.


Does not wok with v-html for truncating text

how can i truncate a parsed html with v-html

@iamtheoleo v-html isn't related to filter. It‘s a directive in Vue.js. I guess what you mean is that you  truncated a string and passed it as value for v-html but it don't work. I think the problem is not caused by filter and you should check your code.

You miss the whole point, thanks anyway


Module 1.1 Assignment

Given what you have learned about Git, why would you want to use Git in your classroom?

Etude du process Campus Advisors pour Sciences Po

👋🏾  Hi @tarraschk, can you tell us more about how you plan to use Git and GitHub in your course? You mentioned in https://github.com/Campus-Advisors/campus-advisor-training-tarraschk/issues/10 that your students would like to communicate with technical workers. What are ways you might introduce version control to your students?

Hello @arelia
I plan to use GitHub to show to my students how developers really need to work together in order to not "reinvent the wheel".
I will not teach them how to use Git in details, as it would be too hard for them. However, I already explain to them how Git is really important in a real professional environment in order to merge multiple inputs from different people working on the same files.
Also, my students indeed have a more social oriented academical path, and I teach them how to code so that they can communicate a little with an IT team in a professional environment.
So to sum up:

I introduce git a little just to tell them that it exists and it's used to avoid conflicts between multiple developers
I show them GitHub in order to introduce "third-party libraries" and "developers communities"
I also show them GitHub so that they can find good Ruby Gems on GitHub
I also tell them that when they will join a professional environment, they should expect the developers to talk about Git / GitHub and version control


CLMUL intrinsics

https://software.intel.com/sites/landingpage/IntrinsicsGuide/#expand=682,682&othertechs=PCLMULQDQ
https://en.wikipedia.org/wiki/CLMUL_instruction_set

A RMv8 also has a version of CLMUL. SPARC calls their version XMULX, for "XOR multiplication".

[x] _mm_clmulepi64_si128
[x] _mm256_clmulepi64_epi128
[x] _mm512_clmulepi64_epi128

Thank you @nemequ !


Allow targetGroups to be omitted in tfaction-root.yaml

Feature Overview
We would like to add working directories without needing to add them to tfaction-root.yaml. We would like to only add the tfaction.yaml in the working directory with all settings including target to add a working directory.
Why is the feature needed?
No need to manually maintain a list of working directories in a global config
Example Code
GitHub Actions

tfaction-root.yaml
---
plan_workflow_name: test

draft_pr: true # default is false. If `draft_pr` is true, tfaction creates pull requests as draft
base_working_directory: "" # default is empty, which means the current directory
working_directory_file: tfaction.yaml # default is "tfaction.yaml"
renovate_login: 'renovate[bot]' # default is "renovate[bot]"
label_prefixes:
  target: "target:" # default is "target:"
  tfmigrate: "tfmigrate:" # default is "tfmigrate:"
  skip: "skip:" # default is "skip:"

aqua:
  update_checksum:
    # Update aqua-checksums.json in `setup` action
    enabled: true # default is false
    skip_push: false # default is false
    prune: true # default is false

# https://github.com/suzuki-shunsuke/tfaction/pull/1106
# tfsec:
#   enabled: true
# tflint:
#   enabled: true
# trivy:
#   enabled: false

# We don't recommend disabling this feature.
# update_related_pull_requests:
#   enabled: false

# tfaction >= v0.5.25
# https://github.com/suzuki-shunsuke/tfaction/pull/910
# scaffold_working_directory:
#   skip_adding_aqua_packages: true

# tfaction >= v0.6.0
drift_detection:
  enabled: false
  issue_repo_owner: suzuki-shunsuke
  issue_repo_name: tfaction-example
  num_of_issues: 1
  minimum_detection_interval: 1

tfaction.yaml
target: aws/
aws_region: ap-northeast-1
s3_bucket_name_tfmigrate_history: '<S3 Bucket Name for tfmigrate history files>'
template_dir: templates/aws # This is used by `scaffold-working-dir` action
drift_detection:
  enabled: true
terraform_plan_config:
  aws_assume_role_arn: arn:aws:iam::000000000000:role/GitHubActions_Terraform_AWS_terraform_plan
tfmigrate_plan_config:
  aws_assume_role_arn: arn:aws:iam::000000000000:role/GitHubActions_Terraform_AWS_tfmigrate_plan
terraform_apply_config:
  aws_assume_role_arn: arn:aws:iam::000000000000:role/GitHubActions_Terraform_AWS_terraform_apply
tfmigrate_apply_config:
  aws_assume_role_arn: arn:aws:iam::000000000000:role/GitHubActions_Terraform_AWS_tfmigrate_apply

Note
No response

Thank you for your feedback!
I understand your proposal. It makes sense.

template_dir should be set in tfaction-root.yaml as this is used for scaffolding.

e.g. tfaction-root.yaml
plan_workflow_name: test
template_dir: templates/aws

No need to manually maintain a list of working directories in a global config

If you create working directories in some subdirectories, you don't need to maintain the list of working directories in tfaction-root.yaml.
e.g.
terraform/
  foo/
    tfaction.yaml
  bar/
    tfaction.yaml
  ...

target_groups:
  - working_directory: terraform/
    target: terraform/

If you create working directories on the repository root directory, maybe you can make working_directory and target empty.
target_groups:
  - working_directory: ""
    target: ""

Maybe this target group matches with all working directories, though I'm not sure if it works well.
I'll test if it works well.

If you create working directories on the repository root directory, maybe you can make working_directory and target empty.

target_groups:
  - working_directory: ""
    target: ""

Maybe this target group matches with all working directories, though I'm not sure if it works well.
I'll test if it works well.

I tried a little. It seems to work well.

If you create working directories in some subdirectories, you don't need to maintain the list of working directories in tfaction-root.yaml.

This is actually enough for us! We have a top level terraform/ folder that contains all our states.
If you want you can close this issue in favor of #1502
Thank you very much.

Sounds good!
Thank you!


styles/all/template/event/navbar_header_profile_list_after.html broken

Replacement string is missing the app.php part.
/app.php/trader/view-feedback/?u=

it's your PR ? https://github.com/rfdy/trader/pull/8
It doesn't fixe it ?

It does fix it, I didn't know it hadn't been merged yet!

yes but in waiting you can edit this file manually ;)

Can be close, already merged.


Add some minor refactoring

Pull Request Test Coverage Report for Build 1f2c2d7ae343d83a3a5e6751c6aea7f985f471e9
Details

19 of 19 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.2%) to 93.805%

Totals

Change from base Build e9d2503e0088f116ba40a9f171b406451524022b:
-0.2%

Covered Lines:
212

Relevant Lines:
226

💛  - Coveralls


HystrixCommand getFailedExecutionException().getMessage() causes Hystrix circuit short-circuited

I am running a Spring Boot application that make use of Hystrix commands. I have a HystrixCommand where in the getFallback() method, I am calling getFailedExecutionException().getMessage(). When this gets executed more then X times (say 20 failed requests), the Hystrix command stops executing the fallback method and instead the container throws a 500 Internal Server Error. Other then not calling this method (which is a valid workaround), how do I resolve this? What is causing this exception?
Here is the exception
[Request processing failed; nested exception is com.netflix.hystrix.exception.HystrixRuntimeException: ShortCicuitDemoCommand short-circuited and fallback failed.] with root cause

java.lang.RuntimeException: Hystrix circuit short-circuited and is OPEN
	at com.netflix.hystrix.AbstractCommand$1.call(AbstractCommand.java:413) ~[hystrix-core-1.4.20.jar:1.4.20]
	at com.netflix.hystrix.AbstractCommand$1.call(AbstractCommand.java:363) ~[hystrix-core-1.4.20.jar:1.4.20]

//Spring boot application
@SpringBootApplication
@EnableCircuitBreaker
public class ShortCicuitDemoApplication {
    public static void main(String[] args) {
        SpringApplication.run(ShortCicuitDemoApplication.class, args);
    }
}

//Controller command
@RestController
public class ShortCicuitDemoController {
	private RestTemplate restTemplate = new RestTemplate();
	@RequestMapping(value = "/shortcicuit")
	@ResponseBody
	public String doSomething() {
		ShortCicuitDemoCommand command = new ShortCicuitDemoCommand(restTemplate);
		String results = command.execute();
		return results;
	}
}

//HystrixCommand
public class ShortCicuitDemoCommand extends HystrixCommand<String> {
	private static final Logger log = LoggerFactory.getLogger(ShortCicuitDemoCommand.class);
	private RestTemplate restTemplate;
	public ShortCicuitDemoCommand(RestTemplate restTemplate) {
	super(Setter.withGroupKey(HystrixCommandGroupKey.Factory.asKey("ShortCicuitDemoGroup"))
			.andCommandKey(HystrixCommandKey.Factory.asKey("ShortCicuitDemoCommand")));
		this.restTemplate = restTemplate;
	}
	@Override
	protected String run() throws Exception {
		// make the call that will fail
		String response = restTemplate.getForObject("http://localhost/donothing", String.class);
		return response;
	}
	@Override
	protected String getFallback() {
		log.error("Fallback {}", this.getFailedExecutionException().getMessage());
		return null;
	}
}

Attached is the full compressed project (only 3 files)
ShortCicuitDemo.zip

When you have debug logging turned on using logging.level.=DEBUG, the real issue shows up. Its just a NPE that the hystrix code is hiding and showing as a different exception.
2015-12-07 16:50:04.395 DEBUG 7576 --- [nio-8080-exec-5] o.a.c.loader.WebappClassLoaderBase       :     findClass(sun.reflect.GeneratedMethodAccessor80)
2015-12-07 16:50:04.395 DEBUG 7576 --- [nio-8080-exec-5] o.a.c.loader.WebappClassLoaderBase       :     --> Returning ClassNotFoundException
2015-12-07 16:50:04.396 DEBUG 7576 --- [nio-8080-exec-5] com.netflix.hystrix.AbstractCommand      : HystrixCommand execution SHORTCIRCUIT and fallback failed.

java.lang.NullPointerException: null
	at com.shortcircuit.demo.ShortCicuitDemoShortCircuitCommand.getFallback(ShortCicuitDemoShortCircuitCommand.java:38) ~[classes/:na]
	at com.shortcircuit.demo.ShortCicuitDemoShortCircuitCommand.getFallback(ShortCicuitDemoShortCircuitCommand.java:1) ~[classes/:na]
	at com.netflix.hystrix.HystrixCommand$2.call(HystrixCommand.java:311) [hystrix-core-1.4.20.jar:1.4.20]
	at com.netflix.hystrix.HystrixCommand$2.call(HystrixCommand.java:306) [hystrix-core-1.4.20.jar:1.4.20]

My interpretation of the above is that returning null as a @ResponseBody is throwing some sort of framework-level exception.  Is that correct?

The issue was that when the circuit breaker is open, getFailedExecutionException() returns NULL and I was not doing a null check before using it.

Ah, I see.  This was brought up in #974 as well.  A path forward here is:

AbstractCommand in hystrix-core now has a getExecutionException() method that should return an Exception instance in this case.
Once hystrix-javanica uses that method, you won't see a NullPointerException.

@dmgcodevil Any updates on that issue?

@mattrjacobs javanica uses regular getaExecutionException from hystrix core so it should be fine.

getExecutionException() was added in #1003 and is not released yet.  My understanding was that a change was required in hystrix-javanica to use this method

Is there any changes in terms how we get execution exception now ? If not, ones the  fix will be in place javanica will pick it up and issue should go away without any specific changes, am I right ?

Yes.  I left the semantics of getFailedExecutionException() alone, so I wouldn't break any current consumers of that method.  That method returns the exception thrown by a run() method only, and NULL otherwise.
The new method (getExecutionException()) returns the exception instance on any failure of the command, including FAILURE/SHORTCIRCUITED/TIMEOUT/BAD_REQUEST/SEMAPHORE_REJECTED/THREAD_POOL_REJECTED
I'm not sure exactly how javanica is wiring up the exception, but switching to getExecutionException() should resolve the case above, I believe.

Oh, I see, then yes, I need to tweak javanica to use getExecutionException() instead of getFailedExecutionException(), it's sub penny change.

@mattrjacobs I guess we can close this issue because 1155 has been resolved. however, the issue herein mentioned isn't releated to javanica because reporter uses venila Hystrix.

Closing out - I don't believe there's anything more to do here.  Please re-open if there's more to discuss


net::ERR_ACCESS_DENIED

Summary

Test Plan

What's required for testing (prerequisites)?
What are the steps to reproduce (after prerequisites)?
Compatibility

OS
Implemented

iOS
✅❌

Android
✅❌

Checklist

[ ] I have tested this on a device and a simulator
[ ] I added the documentation in README.md
[ ] I mentioned this change in CHANGELOG.md
[ ] I updated the typed files (TS and Flow)
[ ] I added a sample use of the API in the example project (example/App.js)

Why not using the props to control this?

Sorry this was not meant to be a pull request. I'm having a error
canGoBack: false, canGoForward: false, code: -1, description: "net::ERR_ACCESS_DENIED", loading: false
and even tough i tried to control this with props, nothing changed, so i made changes on 'RNCWebViewManager.java' and now I'm not getting the error any more. Sorry again for the push request.

@lauthreamont I'm having the same issue has well.. Despite the props :(


Add role 'personality' on board member

Execute this SQL query in staging / production environment to add new role : INSERT INTO enmarche.roles (code, name) VALUES ('personality', 'Personnalité');

It's better to create a migration to add new role.


HBASE-22467 UI fixes to enable Knox proxying

Pushed edaae03 which uses HtmlQuoting. Don't see a need to re-invent the wheel and I think the implementation of that method is fine.

Ripping out edaae03 -- doesn't work for what I'm trying to do here. Will leave a comment on commit.


homeassistant.start not triggering automations

Home Assistant release (hass --version):
0.47.1 and 0.48.0.dev0
Python release (python3 --version):
Python 3.5.2
Component/platform:
automation/homeassistant
Description of problem:
Automations triggered by the new event start from platform homeassistant are not running at HA start.
After some exploration (https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/automation/homeassistant.py#L47) and debugging, I see this code:
    # Automation are enabled while hass is starting up, fire right away
    # Check state because a config reload shouldn't trigger it.
    elif hass.state == CoreState.starting:
        hass.async_run_job(action, {
            'trigger': {
                'platform': 'homeassistant',
                'event': event,
            },
        })

Problem is, in HA start, hass.state is CoreState.running at this point, so never triggers.
Replacing the elif with an else obviously fixes the problem, but the comment in the code discourages that solution, so I do not know what @balloob will think about it.
Expected:
To function properly, triggering automations when HA starts.
Problem-relevant configuration.yaml entries and steps to reproduce:
automation:
- alias: TEST HA start
  trigger:
    platform: homeassistant
    event: start
  action:
    - service: persistent_notification.create
      data:
        title: 'HA init'
        message: "Home Assistant ha comenzado una nueva sesión a las {{ as_timestamp(now())| timestamp_local}}."
        notification_id: "init_notif"

Additional info:
I'm experiencing this problem since the change from event: homeassistant_start to the new platform, I think.
Since it did not work (for me, at least), to trigger automations at startup I was using a custom event that I was firing from AppDaemon, but I think we should fix this

Changing the way the running state is settled looks like fixes the problem (https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/core.py#L184):
from:
self.state = CoreState.running
_async_create_timer(self)

to:
_async_create_timer(self)

def _set_running_state():
    self.state = CoreState.running
self.async_add_job(_set_running_state)

This way, at start, hass.state == CoreState.starting but, when reloading automations, it is hass.state == CoreState.running, as expected in the comment.
Doesn't look pretty under my eyes, so I'll wait for the Elders speak out on the matter before proposing any PR.

Thanks for troubleshooting this @azogue. This has been an open issue for a while now under #7058.

Sorry @grahamwetzler, I didn't see the open issue, my bad!
I've got a solution that is working for me in 2 machines:

the main machine (a RPI3 running 0.47.1), with a local mysql and setup times about 90sec now.
The test&dev machine: A big iMac with only a few components to test and setup times < 1sec.

in homeassistant/core.py:HomeAssistant.async_start() I have a delay before setting the 'RUNNING' state:
DELAY_RUNNING_STATE = 3  # sec

# ...
        self.bus.async_fire(EVENT_HOMEASSISTANT_START)
        _LOGGER.warning("Triggering %s event at %s", EVENT_HOMEASSISTANT_START, dt_util.utcnow())

# ...

        @asyncio.coroutine
        def _set_running_state():
            _LOGGER.warning("Running mode at %s", dt_util.utcnow())  # Only for log-check
            yield from asyncio.sleep(DELAY_RUNNING_STATE)
            _LOGGER.warning("Changing now: %s", dt_util.utcnow())  # Only for log-check
            self.state = CoreState.running

        self.async_add_job(_set_running_state)
        # self.state = CoreState.running
        _async_create_timer(self)
        _LOGGER.warning("Finishing now: %s", dt_util.utcnow())  # Only for log-check

(the _LOGGER.warnings are only to mark the logs)
@pvizeli, about your comments in #7058: In my case, I've checked that the problem wasn't about the automation state, but with the running state. The automations are initialising with the running state, so, here the condition is not met.
My logs without the delay:
2017-06-24 20:12:57 INFO (MainThread) [homeassistant.bootstrap] Home Assistant initialized in 0.89s
2017-06-24 20:12:57 WARNING (MainThread) [homeassistant.core] Triggering homeassistant_start event at 2017-06-24 18:12:57.400199+00:00
2017-06-24 20:12:57 WARNING (MainThread) [homeassistant.core] Finishing now: 2017-06-24 18:12:57.401769+00:00
2017-06-24 20:12:57 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Testing data template
2017-06-24 20:12:57 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Toggle boolean with Telegram callback
2017-06-24 20:12:57 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Turn boolean ON with Telegram callback
2017-06-24 20:12:57 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Turn boolean OFF with Telegram callback
2017-06-24 20:12:57 INFO (MainThread) [homeassistant.components.automation] Initialized trigger TEST HA start
2017-06-24 20:12:57 INFO (MainThread) [homeassistant.components.automation] Initialized trigger TEST HA start homeassistant_start

And with the delayed running state:
2017-06-24 20:15:38 INFO (MainThread) [homeassistant.bootstrap] Home Assistant initialized in 0.80s
2017-06-24 20:15:38 WARNING (MainThread) [homeassistant.core] Triggering homeassistant_start event at 2017-06-24 18:15:38.642444+00:00
2017-06-24 20:15:38 WARNING (MainThread) [homeassistant.core] Finishing now: 2017-06-24 18:15:38.642875+00:00
2017-06-24 20:15:38 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Testing data template
2017-06-24 20:15:38 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Toggle boolean with Telegram callback
2017-06-24 20:15:38 INFO (MainThread) [homeassistant.components.automation] Initialized trigger TEST HA start
2017-06-24 20:15:38 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Turn boolean ON with Telegram callback
2017-06-24 20:15:38 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Turn boolean OFF with Telegram callback
2017-06-24 20:15:38 INFO (MainThread) [homeassistant.components.automation] Initialized trigger TEST HA start homeassistant_start
2017-06-24 20:15:38 WARNING (MainThread) [homeassistant.core] Running mode at 2017-06-24 18:15:38.645067+00:00
2017-06-24 20:15:38 INFO (MainThread) [homeassistant.components.automation] Executing TEST HA start
2017-06-24 20:15:40 WARNING (MainThread) [homeassistant.core] Changing now: 2017-06-24 18:15:40.648007+00:00


React Js Changes

Hey Arham, I am stuck at the same place in my intro-react repo.Did you find a way to fix it.


injecting ngMock crash the app

I have installed angular-mocks through bower.
But after injecting ngMock the app crashed with no errors in the console.
(angular-mocks.js is properly linked in the index.html)
It was happening in an Ionic app. I have tried in a simple angular app for test purpose and i am having the same behavior.
Am i doing something wrong or there currently some issues with angular-mocks?
Thank you!

Can you provide a demo of the problem on plnkr.co or similar? Also, are you injecting ngMock in your real app? You shouldn't do that.

Thanks for reply.
I have created this plunker: http://plnkr.co/edit/Un9xBtrm1yqG4HubEdza?p=preview
Currently the app is crashed. By removing 'ngMock' the app come back working as expected.
What do you mean I shouldn't inject ngMock in my real app?

Look at your console, you are not actually including any version of angular mocks. You have //code.angularjs.org/X.Y.Z/angular-mocks.js X.Y.Z should be a version, like 1.4.7. You are also including a super old version of angular (1.0.8). Please use the latest, 1.4.7
ngMock is a module that "mocks" several core services of angular to make testing easier. You should never need it in your actual app.

Ok that was actually a mistake of the plunker, sorry. (In the apps i have latest version)
I have updated the plunker but there is the same problem.

Oh, I see. I don't actually know why it breaks. Why do you exactly need ngMock in your app, though?

I was trying to set up the environment for unit testing

You wouldn't do it like this. Here's a good guide: https://www.airpair.com/angularjs/posts/testing-angular-with-karma


layers.core.Dense doesn't make use of argument activity_regularizer

As it says on the tin, the Dense class of tensorflow.python.layers.core accepts an activity_regularizer argument, but never makes use of this argument. Not sure if this is intentional or an oversight, so pointing it out.

I believe it does get used by a call in the parent class (see python/layers/base.py:270).
Closing this out. CCing @fchollet in case I have misunderstood and he wants to reopen this.


fix: ensure modules are correctly resolved from the current working dir

Overrides the path used in require.resolve to start with the working directory that cook is running
from rather than the __dirname of the file which is running.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


update the version to 0.4.2

This change is

Review status: :shipit: complete! 1 of 1 LGTMs obtained

Comments from Reviewable


Mobile UI issue

Describe the bug
When on mobile, if you tap the hamburger menu, you can't scroll, so depending on screen size and which submenus are expanded, you might not be able to access the whole menu.
To Reproduce
Steps to reproduce the behavior:

Go to https://explorer.hiro.so
Tap on the hamburger menu
Try to swipe down
If the whole menu fits, expand the network or rotate to landscape to see the problem.

Expected behavior
I should be able to scroll down to see the rest of the menu.
Screenshots
In this screenshot, I can't change the network to testnet because I can't scroll down.

Smartphone (please complete the following information):

Device: iPhone 15 Pro
OS: iOS 17.3.1
Browser: Safari or Chrome

:tada: This issue has been resolved in version 1.185.4 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


/god mode is not working

In the server cmd, it says
NullReferenceException: Object Reference not set to an instance of an object.
What does it mean? Sorry 1st timer here

Yeap, confirmed. Godmode doesnt work for some reason.

PLEASE use the latest beta and just report bugs on that. This is a duplicate to #53 and fixed.


EACCES (Permission denied) launchImageGallery Android

Description
I am testing with my OnePlus 6 and tried picking the same image with all my suggested apps (OnePlus' gallery app & Google Photos). Rendering only functions properly for the Google Photos' attempt.
I have tested with both storage-permission enabled & disabled, both give same result.
Manifest includes WRITE_EXTERNAL_STORAGE.
Things work as expected for launchCamera() with same options.
Error:
nativeEvent: error: "/storage/emulated/0/WhatsApp/Media/WhatsApp Images/IMG-20201104-WA0003.jpg: open failed: EACCES (Permission denied)
It does not have anything to do with the space in the pathname. Other attempt: /storage/emulated/0/DCIM/Camera/IMG_20201024_233443.jpg: open failed: EACCES (Permission denied)
Component-state:
imageSource:
0:
  fileName:"IMG-20201104-WA0003.jpg"
  fileSize:129868
  height:805
  type:"image/jpeg"
  uri:"content://media/external/images/media/152634"
  width:580
1:
  fileName:"IMG-20201104-WA0003.jpg"
  fileSize:129868
  height:805
  type:"image/jpeg"
  uri:"content://com.google.android.apps.photos.contentprovider/0/1/content%3A%2F%2Fmedia%2Fexternal%2Fimages%2Fmedia%2F152634/ORIGINAL/NONE/image%2Fjpeg/1086794781"
  width:580

How to repeat issue and example

Launch image library picker:

launchImageLibrary(
  {
    mediaType: "photo"
  },
  (response: ImagePickerResponse) => {
    this.processImageReponse(response);
  }
);

Choose "Google Photos"-option for picking an image.
Repeat for other Gallery-apps such as OnePlus' native Gallery app (https://play.google.com/store/apps/details?id=com.oneplus.gallery)
Render preview:

<Image
  style={{
    height: 90,
    width: 120,
    backgroundColor: "#ccc"
  }}
  source={{ uri: item.uri }}
  onLoadEnd={() => console.warn("onLoadEnd")}
  fadeDuration={0}
  onError={e => {
    e.persist();
    console.error("Error loading marker image", e);
  }}
/>

Additional Information

Image Picker version: 3.0.0-vnext.3
React Native version: 0.61.5
Platform: Android API 29
Development Operating System: MacOS
Android SDK Platfom-tools: 30.0.4
Android SDK Tools: 26.1.1

Where is this error coming, while using it in <Image> component or while selecting the image via gallery app?
Is selecting the image using google photos working properly?
Is the app crashing or just the error is logged?

I faced the same problem, but I fixed with:
https://github.com/react-native-image-picker/react-native-image-picker/issues/1447#issuecomment-721520908

@joshjo's fix works! 💪

Add this permission in your manifest file inside application tag
android:requestLegacyExternalStorage="true"

Adding android:requestLegacyExternalStorage="true" is not a solid fix, unless you don't care about Android 11..
From Google's docs:

Caution: After you update your app to target Android 11 (API level 30), the system ignores the requestLegacyExternalStorage attribute when your app is running on Android 11 devices, so your app must be ready to support scoped storage and to migrate app data for users on those devices.

https://developer.android.com/training/data-storage/use-cases#opt-out-scoped-storage

android:requestLegacyExternalStorage="true" fixes the permission issue, however files that we capture using launchCamera() have started getting saved in the Gallery which is something I was specifically trying to avoid. Any suggestion on avoiding that would help! Thanks in advance!

android:requestLegacyExternalStorage="true" fixes the permission issue, however files that we capture using launchCamera() have started getting saved in the Gallery which is something I was specifically trying to avoid. Any suggestion on avoiding that would help! Thanks in advance!

Fixed in latest version


chore(main): release 0.7.0

:robot: I have created a release beep boop
0.7.0 (2022-10-03)
Features

improve mTLS documentation and dependencies (da2bfa4)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/apigee/terraform-modules/releases/tag/v0.7.0 :sunflower:


add create_mnbn_model

This PR adds function to replace BatchNorm by MultiNodeBatchNorm.
Solve https://github.com/chainer/chainer/issues/5786

imosCI, test this please.

Jenkins, test this please.

Jenkins CI test (for commit 96917bf12e71148b7db03a17a214a65700689198, target branch master) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

Jenkins, test this please.

Jenkins CI test (for commit 21278c8a5c4320eebc1381dd9a96e32ed0f4d8ba, target branch master) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

Jenkins, test this please.

Jenkins CI test (for commit 21278c8a5c4320eebc1381dd9a96e32ed0f4d8ba, target branch master) succeeded!

Jenkins CI test (for commit 21278c8a5c4320eebc1381dd9a96e32ed0f4d8ba, target branch master) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)


Owner update permission not working

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
14.17.3
Amplify CLI Version
7.6.22
What operating system are you using?
Windows 11
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
Added auth permissions in auth override.ts to all user groups in order to access geo and pinpoint.
Amplify Categories
auth, api
Amplify Commands
Not applicable
Describe the bug
When a model has an auth rule that specifies owner update and an owner executes an update, the operation is not synced to the backend. No warning/error is displayed in the console.
Expected behavior
The owner should be able to update, as was the case before 7.6.22.
Reproduction steps

Create a model with auth rule update
Try to update and check if the update is synced

GraphQL schema(s)

# Put schemas below this line

type Task implements Deletable
  @model
  @auth(
    rules: [
      {
        allow: owner
        ownerField: "assigner"
        operations: [create, read, update]
      }
      { allow: owner, ownerField: "assignee", operations: [update] }
      { allow: groups, groups: ["Admin"], operations: [update, delete] }
      { allow: groups, groups: ["Management"], operations: [update] }
      { allow: private, operations: [read] }
    ]
  ) {
  id: ID!
  deletedAt: AWSDateTime @index(name: "byDeleted")
  assigner: String
  assignee: String! @index(name: "byAssignee")
  startDateTime: AWSDateTime!
  endDateTime: AWSDateTime!
  moved: Int @default(value: "0")
  activityTasksId: ID!
  identityTasksId: ID!
  children: [Task!] @hasMany
}

Log output

# Put your logs below this line

Additional information
No response

Question: "Try to update and check if the update is synced"
How did you check if the update has synced ?

I created a "Task" model with an Admin user.
I updated that "Task" with a user that has only owner permission on a separate client.
By querying on both clients, the owner gets the updated task, while the Admin still receives the old task.
By the way, I use datastore for this test.

Hey @maxludovicohofer :wave: outside of the context of DataStore I was able to reproduce this following issue #9883 , copying my notes here
I was not able to reproduce using the following schema:
type Todo
  @model
  @auth(
    rules: [
      { allow: owner }
      { allow: groups, groups: ["admins"] }
    ]
  ) {
  id: ID! @primaryKey
  owner: ID
  name: String!
  description: String
}

with two users, admin and user, of which admin is a member of the admins group. Both admin and user are able to update records as intended. However, when explicitly granting update access the update mutations no longer work:
type Todo
  @model
  @auth(
    rules: [
      { allow: owner, operations: [create, update, read] }
      { allow: groups, groups: ["admins"], operations: [read] }
    ]
  ) {
  id: ID! @primaryKey
  owner: ID
  name: String!
  description: String
}

It is important to note create and read are working as expected.

Marking as a bug 🙂


What means...

Sorry to ask, but what means Key 2B or Key 10B ?
I'm used to E-minor or G-major etc.
When a track shows E90%, what does this mean?
An explanation somewhere would help. Thanks! Great extension!!!!!!

I updated the Readme file, thanks for mentioning!
The E means the Energy of the song in percent, the Key is displayed in the Camelot Notation, which is used by DJs. A new Extension was made by another person, where you can change the notation of the key!


Does not work inside floating windows

I never realized this because I don't use several windows, but while testing some things I observed that the plugin does not work inside floating windows at all.
I personally do not need the feature, but others might, so I'm writing this here.
Steps to reproduce:

Call command "Open current tab in new window"
Try to use any hotkey in the new window

Ups, wrong repo! Sorry!


Problem with Declarative rendering section of guide

This page in the guide says:

Just open up your browser’s JavaScript console and set app.message to a different value.

I couldn't figure out how to get this to work?
My index.html looks like this:
<!DOCTYPE html>
<html lang="en">
  <head>
    <meta charset="utf-8">
    <title>Vue Example</title>
  </head>
  <body>
    <div id="app">
      {{ message }}
    </div>
    <script src="dist/build.js"></script>
  </body>
</html>

and my main.js looks like this:
import Vue from 'vue/dist/vue.js'

var myapp = new Vue({
  el: '#app',
  data: {
    message: 'Hello Vue!'
  }
})

my "app" opens in the browser and renders:

and the Vuejs dev-tools can see/recognise it - but I can't figure out how to update the value of message in the console:

Because index.html has app as a id, you can just say app in the console, but that's just a DOM node:

So I think you need to expand on this line and explain & show an example:

Just open up your browser’s JavaScript console and set app.message to a different value.

Hmmm. Had a little epiphany and tried this on the actual guide page itself - rather than the little app I was building locally as I was going along - and it works!
So, it works on the guide page, but not in my simple little app?

The code as posted works perfectly. When using a module system, e.g. via Webpack or Browserify, the code in your modules are actually wrapped to... modularize them. Otherwise, they'd be very leaky, as any variables defined would be in the shared global scope. That's why when trying to access your myapp variable in the console, it doesn't work. Your module system is doing it's job. 😃
We expect users of these module systems to know how they work, as they have their own documentation, but you can get your example working with window.myapp = to explicitly assign myapp to the global object.

Thankyou!
For anyone else wondering how to access your global stuff in a webpacked vuejs app, you can do it by typing this into the dev console:
> window.myapp = window.$vm
// <- Vue$2 {_uid: 0, _isVue: true, $options: Object, _renderProxy: Proxy, _self: Vue$2…}
> myapp.message
// <- "Hello Vue!"
> myapp.message = 'test'
// <- "test"

More information here.


Can we expose camelCase methods

Hi,
Great wrapper around NextSMS!
I have a little request which may turn to a PR once accepted.
Turning snake_case methods & variables to camelCase
It may sound like not much but for NodeJS/JavaScript developers we are born used to camelCase conversion and since people will be integrating this into their NodeJS programs it will be much convenient it the methods exposed from this library have a familiar syntax.
Thanks!

Hello @maotora
This is a very valid point, and was under consider, conversion to camelCase already started on php client
If you can help with that would be very helpful
Thanks


Any support or to check the code only in CPU version

File "/home/devteam/.local/lib/python3.8/site-packages/torch/serialization.py", line 116, in validate_cuda_device
raise RuntimeError('Attempting to deserialize object on a CUDA '
RuntimeError: Attempting to deserialize object on a CUDA device but torch.cuda.is_available() is False. If you are running on a CPU-only machine, please use torch.load with map_location=torch.device('cpu') to map your storages to the CPU.

/home/devteam/.conda/envs/py38/lib/python3.8/site-packages/mmcv/runner/checkpoint.py
load_checkpoint(model,
filename,
map_location='cpu',
updated this part to work with CPU


Feature/invoke application workflow

Created a new endpoint "/api/system-access/application/:id" with full data access to any application data. This endpoint is accessible only through "forms-flow-bpm" client.
Renamed CRA endpoints to be also under the same "system-access" URL to be aligned to the endpoints that require full access and are limited to specific clients.
Replace the fullapplication form.IO definition with the more completed on "SFAA2022-23", as per the conversation with @abschwenker.
Created a helper service to keep all the workflow interactions and made it easy to deal with, like shown below.

await this.workflow.startApplicationAssessment(createdApplication.id);

Adjusted field names on personal information read-only section to adapt to the new form, as shown below (still missing PD status).

Please review sonarcloud, other than that LGTM

Done!


updated vitess api (to gitql-0.2 tag)

I updated our vitess fork and tagged it: https://github.com/gitql/vitess/releases/tag/gitql-0.2

Codecov Report

Merging #114 into master will increase coverage by 0.06%.

@@            Coverage Diff             @@
##           master     #114      +/-   ##
==========================================
+ Coverage   60.81%   60.87%   +0.06%
==========================================
  Files          41       41
  Lines        1771     1756      -15
==========================================
- Hits         1077     1069       -8
+ Misses        627      622       -5
+ Partials       67       65       -2

Impacted Files
Coverage Δ

sql/parse/parse.go
57% <64.7%> (+0.25%)
:white_check_mark:

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 fb17c2f...de98f6f. Read the comment docs.


Development vdc chatflow

Description
Describe the changes introduced by this PR and what does it affect
Changes
List of changes this PR includes
Related Issues
List of related issues
Checklist

[ ] Pre-commit hook is installed to do formatting checks before committing code...etc
[ ] Tests included
[ ] Build pass
[ ] Documentation
[ ] Code format and docstrings

to be continued in https://github.com/threefoldtech/js-sdk/pull/1769


Pkg rename: Microsoft.AspNet.Hosting.Interfaces -> Microsoft.AspNet.Hosting.Abstractions

See https://github.com/aspnet/Announcements/issues/8#issuecomment-97566113

https://github.com/aspnet/Hosting/commit/ec7a4351ded97ec484fcbf273bab05e0ad12954c


[BUG] Not able to compile photo_view project cloned from github

Cloned project from github is not working, getting an error message in console:
AndroidManifest.xml could not be found.
Please check D:\kamlesh\development\test\photo_view\example\android\AndroidManifest.xml for errors.
No application found for TargetPlatform.android_arm64.
Is your project missing an android\AndroidManifest.xml?
Consider running "flutter create ." to create one.

I have one more request. Kindly post a simple and proper example to make more popular this package at
https://pub.dev/packages/photo_view/example
Thanks a lot!

Yeah, we have to run flutter create . on the example directory after clonning. This will solve your problem.

Kindly post a simple and proper example at...

Well, that is automatically generated from the main file of the example app, do it is pretty much the same thing.
Do you have an idea to tackle that?


Resolve errors occurring when dbt_project_path is None or str

Description

As part of the changes made #581, some downstream logic was missed relating to the handling of a None and String based project dir. This MR attempts to remedy this issue, by adding down steam support for project dir being None (including generation of exceptions and guarding), as well as some property reference changes in converter.
Related Issue(s)
closes #601
Breaking Change?

Checklist

[ ] I have made corresponding changes to the documentation (if required)
[ ] I have added tests that prove my fix is effective or that my feature works

@tatiana
I'm not 100% confident with some of the changes i made downstream - assuming test coverage is all good we should be fine, however, given i'm still not 100% familiar with the codebase here some more detailed review may be required.

I have just noticed the above errors in some tests - i will check those out shortly

I think the latest commit should address all your feedback :) let me know if theres anything else that needs updating

I have been able to replicate the issue you found above, and, If i understand the issue correctly, it looks like this is related to the operator command generation no longer having a root project path to base the dbt commands of that are run within the DAGs.
It sounds like this is starting to require the logic described in : https://github.com/astronomer/astronomer-cosmos/issues/597 to fully fix the issue, however, as a stop-gap solution we could apply a default based on the operator type.
It looks to me like we could, for now, use a default as the existing k8s and docker executors do, which is to reference $airflow_home/dags as the dbt project location base (as noted in the setup instructions: https://astronomer.github.io/astronomer-cosmos/getting_started/kubernetes.html)
I will give this a go and try to get this working to unblock this, and im noting this here as a discussion point if required, and to link it to the other issue for when that is worked on.

For now, while i'm testing, i've added a new field to ExecutionConfig called dbt_project_path_root, which i'm referencing in converter.py init as:
dbt_project_path_runtime_root = execution_config.dbt_project_path_root
This way, we can pass this to the operator's args, in combination with the project_name from ProjectConfig to get the path at runtime.
I was thinking of just adding it as a default in converter, but, exposing it as a config option seemed like a better option, though, im aware we don't want to cause any backward compatibility issues with public facing interfaces like this, so happy to remove it from ExecutionConfig, and just hard-code (lookup AIRFLOW_HOME) in converter if thats a better approach
I'm currently unable to test this locally due to some environment constraints on my development environment, though im working on this and should have more tests conducted soon to fully verify the validity of this solution.

I have confirmed all unit and integration tests run successfully on a fresh vm across the required python/airflow version set/s
I think my choice to add execution_config.dbt_project_path_root in this PR is questionable, and alternate implementation recommendations would be appreciated.

@MrBones757, thanks for looking into this, addressing it quickly, and finding a workaround for the issue!
I also have mixed feelings about the approach of setting the path in the local operator. As you pointed out, I'm worried about edge cases and the possibility of us introducing a breaking change or unexpected behaviours.
I understand that to execute the dbt commands in the LOCAL mode, we will need the original dbt project code & path. Implementing ticket #568 would solve the issue without needing the more abrupt change proposed in #597 - I see it as a first step to solving this problem. K8s and Docker users have complained about this existing behaviour. That said, fixing #568 is outside the scope of the current PR.
My suggestion for us to wrap this PR:

Undo the changes from the last commit, 02ae25be2e3fd16132ea1711412aef8aeb8080bd.
Revert the manifest example; since it uses LOCAL, it needs the project path (I'm sorry for my misleading suggestion)
Rely on the test https://github.com/astronomer/astronomer-cosmos/pull/605/files#diff-f56d97c6216a37d8ca841f31c63b704d05b7e3a42d6dbe783411d6fef8204615R116 to cover the change we introduced related to supporting Manifest, no project path & a non-local Cosmos execution mode.

Once we implement #568, we can update the Manifest example safely - adding the project path only to the execution configuration. I'm adding a comment to the ticket so we don't forget this.
WDYT?

@tatiana I'm happy to revert that change later, as long as we're sure that this wont break docker / k8s based deployments - i'm not 100% clear on where those execution methods get their paths from. Based on what i could see by following the code though, this property that im looking up in env when dbt_project_path is not defined seems to also control paths for docker / k8s too - can you confirm where the k8s / docker paths are controlled? my assumption was it used the same mechanism..
my thinking here, is that since there would be no root path when only a manifest is provided, dbt would have no base folder for its operations in the containerised modes and thus resul in errors locating files, unconfirmed though - purely an assumption

that sounds good to me - to confirm the above:
I will revert the change to the ExecutionConfig, and we will require the project path be defined still;
Separately to that, i will have a discussion with you about the implementation of #568  as i believe i should have bandwith to do that.

I cant see any other opportunities for adding coverage in the scope of this PR. Is this slight change required to be resolved to get this merged?

@MrBones757 We just published the release 1.2.1:

https://pypi.org/project/astronomer-cosmos/1.2.1/
https://github.com/astronomer/astronomer-cosmos/releases/tag/astronomer-cosmos-v1.2.1


Benchmark Setup: error opening wrfinput_d01 for reading ierr= -1021

Hi,
At https://github.com/aws-samples/aws-hpc-workshops/blob/master/README-WRF.rst#setup-benchmark you mentioned that  only 3 input files are required for wrf run for conus 2.5k,
After arranging all three files , on running wrf.exe (v<IP_ADDRESS>) i got -
*************************************
DYNAMICS OPTION: Eulerian Mass Coordinate
 alloc_space_field: domain            1 ,              16471424  bytes allocated
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE:  <stdin>  LINE:      70
 program wrf: error opening wrfinput_d01 for reading ierr=       -1021

Could you please share instructions on ow to get the same ? (could you please upload the same?)
Let me know if i can provide you with any further information.

Hi! I have the same error as you. May I ask how to fix it? Thx


Reinit opam (image default is 2.0, but we're using 2.1)

In 0e785ca822b5860bf01e8af56e598e1fe0cf9260 I've changed the analyze opam-vars to use the current opam variant instead of the default, however this requires also to reinit the opam root, otherwise false information may be returned by opam config expand ….
@kit-ty-kate explained that if we change the default opam (which is also the case in ocaml-ci specs) we ought to reinit opam too.
The rest are updates.

Alea jacta est.


feat(Table): add shorthand for generating tables

The Table has been updated to our v1 API in #451.  This was done with the sub component API only.  We now need to add shorthand for generating tables.
Our previous TableColumn implementation was inspired by Facebook's fixed-data-table.  @jcarbo has also put forth many great starter ideas in this comment.
Though it is more work, I am leaning toward the suggested row based approach (last example from jcarbo) because it offers more control.  Or at least providing this as one of the shorthand options.  With the old TableColumn approach, here at TA we ran into issues by not being able to control the actual row or cell that was rendered.
I think providing "renderer" props that expect table elements to be returned is the way to go.  We could even provide multiple "renderer" props that would allow varying levels of control.  Even along side a columns prop that let you define columns like we used to.  This way, you can have several approaches to accomplish the most common goals.

Edit I wound up pseudo-coding way more than I intended (see the bottom section) haha. If you think this makes sense I can take a pass at implementing this. Might be easier to talk about once there's actual code written.

The tricky part here is going to be the body row since it's going to be based on data for a given row. The header/footer rows are just going to be static, which makes them slightly easier. What about this:
// Table usage.

Not setting headerRow or footerRow would leave out the thead or tfoot. tbody would always exists, just possibly be empty.
This would mean a Table.Row would need to know how to render itself. I'm thinking as items prop that is an array of shorthands for Table.Cell, either using the as within each item to specify Table.HeaderCell or possibly cellAs which would make it a little easier for the Table shorthand case. I'll try to explain...
Row shorthand
We would need to update the shorthand factory to treat an array as a literal, but I'm thinking:
TableRow.create = createShorthandFactory(TableRow, items => ({ items }))

So you could theoretically do this:

 [props.name, props.status, props.notes]}
  footerRow={[{ colspan: 3, content: 'Some footer content' }]}
/>

Same example, but adding props to the TableRow for each row of the body:

 ({ positive: status === 'paid', items: [props.name, props.status, props.notes] })}
  footerRow={[{ colspan: 3, content: 'Some footer content' }]}
/>

I'm using items to be consistent with our other array-of-shorthands, but could just as easily be cells which may make it a tad more clear.
Pseudo code for the implementation:
// Table
renderHeader () {
  return (
    <TableHead>
      TableRow.create(this.props.headerRow, { itemAs: 'th' })
    </TableHead>
  )
}

renderBody () {
  return (
    <TableBody>
      {this.props.tableData.map((item, index) => TableRow.create(this.props.bodyRow(item, index)))}
    </TableBody>
  )
}

renderFooter() {
  return (
    <TableFooter>
      TableRow.create(this.props.FooterRow)
    </TableFooter>
  )
}

render () {

    {headerRow && this.renderHeader()}
    {this.renderBody()}
    {footerRow && this.renderFooter()}

}

// TableRow
renderItems () {
  return this.props.items.map((item) => TableCell.create(item, {
    // Make 'itemAs' a tableRow prop to avoid needing to add the prop to each
    // list item individually. If the user passed an 'as' prop already within
    // 'item' it would still win.
    as: itemAs
  }))
}

render () {
  if (children) {
    return <ElementType {...rest} className={classes}>{children}</ElementType>
  }

  <ElementType {...rest} className={classes}>{this.renderItems()}</ElementType>
}

@levithomason - I wound up implementing this and I think it came out really well. Check out the PR referenced above ^


[babili 0.2.1] Conflict when running es2015 + babili presets

After upgrading to 0.2.1, when running preset es2015 and babili together, some of the plugins throw, most likely due to some inter dependency and plugin execution order.
I don't have a small enough reproducible case yet (I'm compiling a really big file when it throws).
My hope is that you guys might have an idea of what could happen based on the changes between the previous version?
Otherwise I will either wait for @hzoo to finish the plugin dependency work, or will try to bring a more concrete use case to try to fix this issue.

Is this the same error as #556 ?
Also, there are some known issues when used alongside es2015 preset - https://github.com/babel/babili/issues?q=is%3Aissue+is%3Aopen+label%3A"with+es2015"

Closing this for now.
Please comment with more info (stack trace / minimal repro / any other clue to help drill down to the issue) and let's reopen the issue.


Decide on javadoc guidelines

Currently, a number of methods is not or only poorly documented with javadoc, which makes it hard for others to contribute. This also applies to the map-matching repository.
I think what we need are is a javadoc convention (see also #774) that applies to all new contributions. I would suggest to adopt the javadoc rules from the Google Java Style Guide, which describe where javadoc is required.
In addition to where javadoc is required, we also need some agreement on how to write good javadoc comments.
In #774, @karussell commented:

Also what to comment and what not is important and this is a good read: https://visualstudiomagazine.com/articles/2013/06/01/roc-rocks.aspx
It's important to communicate what the code should be doing. Comments should explain the "why" of the code and stop there.
What comments should never, ever do is explain how the code does its job.

Yes the code is not commented a lot. I think we should aim for speaking names, short (if possible ;)) methods that can be understood easily. We should break the methods into smaller methods where possible and assign speaking names to the methods, so it becomes clear what happens. This is basically the  approach presented in Clean Code (by Robert Martin). I think most method comments are unnecessary, however some methods are rather complex, these are typically documented already.
Javadoc becomes outdated very fast. Usually with the next refactoring one has to fix the Javadoc anyway.

In #774, @karussell commented:
+1

It's important to communicate what the code should be doing.

I agree. An additional criterion for good javadoc comments is for me that users of the API should understand from javadoc alone how to use the API. Often it is not sufficient to just roughly describe what a method does but to be precise about the preconditions, postconditions and side effects of a method. An example for good javadoc is the java.util package. e.g. ArrayList. It does fully explain how to use the API without giving implementation details.
IMHO, the best mindset for writing good javadoc is Design by Contract.

Javadoc becomes outdated very fast.
I would require that javadocs are updated with every pull request by the pull request author. This way javadoc never becomes outdated.

be precise about the preconditions, postconditions and side effects of a method

yes, like information about thread-safety and if stateless.

Javadoc becomes outdated very fast.

I would require that javadocs are updated with every pull request by the pull request author. This way javadoc never becomes outdated.

Yes but still it can happen that when doing some 'global' refactoring a local javadoc could get meaningless or wrong.


License and other questions

Hi there, this looks awesome!
-I'm wondering if there will be a license added for your project?
-I also don't seem to see an upload function over @ https://splab.net/apd/d800/
Maybe it hasn't been implemented just yet? (I am a little early)
-Will the web verison be available here as code too?

Hi. Thanks for your interest.
(1) Regarding license:

Added LICENSE.md.

(2) Regarding the upload function over @ https://splab.net/apd/d800/ and the web version:

The website you're referring to is someone else's. I'm not affiliated with them in any way.

(3) Regarding a function for creating a spectrogram from a sound file:

I'm not sure if I'd add such a function. It can be done rather easily with existing libraries like scipy, matplotlib, or librosa.


Variable value not found

v2.39.2
$ tpl
?- X = [Z,1|Z],append([Z],[Z|Z],[X,Z,Z,Y|Z]),write(Y),nl.
_2                           % unexpected
   X = [Z,1|Z], Z = [Z,1|Z]. % Y = 1 not found
?-

Howto find Y = 1

?- X = [Z,1|Z],append([Z],[Z|Z],[X,A,A,Y|Z]),write(Y),nl.
_3
   X = [Z,1|Z], Z = [Z,1|Z], A = [Z,1|Z]. % Not yet

?- X = [Z,1|Z],append([Z],[Z|Z],[X,A,B,Y|Z]),write(Y),nl.
1
   X = [Z,1|Z], Z = [Z,1|Z], A = [Z,1|Z], B = [Z,1|Z], Y = 1. % Now, involving Z = A = B (= valuable scrap)

?- X = [Z,1|Z],append([Z],[Z|Z],[X,_,_,Y|Z]),write(Y),nl. % scrap scrapped
1
   X = [Z,1|Z], Z = [Z,1|Z], Y = 1.

Simplifying
?- append([Z],[Z|Z],[[Z,1|Z],Z,Z,Y|Z]).
Z = [Z,1|Z].
Then changing the definition of
append([], R, R).
append([X|L], R, [X|S]) :- append(L, R, S).
to
append([], R, R).
append([X1|L], R, [X2|S]) :- append(L, R, S), X1 = X2.
gives
?- append([Z],[Z|Z],[[Z,1|Z],_,Z,Y|Z]).
Z = [Z,1|Z], Y = 1.
So something in unification involving, you guessed it, cyclic terms it seems.


feat: port GroupTheory.Subgroup.Basic

It's somewhat surprising that this seems to have more problems than LinearMap given that I expected unbundled inheritance as in MulMemClass etc. to be easier on Lean 4's outParam support than bundled as in LinearMapClass. I'll take a look, see if I can fix some of the issues.

I think I see the issue: MulMemClass etc. should not have an outParam and instead leave figuring out the type of elements to SetLike. Let's see if that helps...

I spun out the outParam fix to a new PR: #1832. Next, I'll try and see if we can backport this fix to Lean 3, for easier porting in the future.

bors merge


Unable to register worker nodes

I've followed through the walk through problem free until tonight. It seems I'm some how not getting the ip address of the api server to connect.  I was walking through the Readme(s) in order and thought I did everything I was supposed to.  Looking back, I think put the configuration files together in Readme05 correctly, but it seems I may have messed something up here?...  Any ideas of where I went wrong?  This is occurring on all worker nodes.
kubelet_node_status.go:107] Unable to register node "worker-0" with API server: Post https://:6443/api/v1/nodes: dial tcp :6443: getsockopt: connection refused
^^  if you look above you will see my missing IP address.  Thank you for your time.

On one of your worker nodes, what is the output of the following command?
# grep server /var/lib/kubernetes/kubeconfig

Ahhh, it seems that the file /var/lib/kubernetes/kubeconfig does not exist on my workers.  I must have missed something while I was creating them.

In 09, you probably missed this step:
sudo mv ${HOSTNAME}.kubeconfig /var/lib/kubelet/kubeconfig

In 09 there's this line - but the path is slightly different:
sudo mv ${HOSTNAME}.kubeconfig /var/lib/kubelet/kubeconfig

Thank you for responding.  I will look at this later on!

@joshfischer1108, @zatricky Ah yes, don't mind me, I provided the path to the file in my own environment.
My reasoning here is sound though, I suspect that server: is not properly formed in /var/lib/kubelet/kubeconfig, maybe as a result of ${KUBERNETES_PUBLIC_ADDRESS} being undefined when you generated it.

That was it.  Thank you @tokiwinter and @zatricky for looking at this for me, definitely saved me some headaches!


DBZ-1951 Introduce banner for development/older versions

https://issues.redhat.com/browse/DBZ-1951
So I decided to base the logic on when to apply the version banner because I wanted to see if we can do this without introducing even more steps to the release process for maintaining attributes. Antora maintains an array of versions and we use this array to compare against the version of the page rendered to see whether to apply the "development" or "outdated" banners.
The banner placement is probably not ideal at the moment since it scrolls with the page content but in order to avoid problems with other rendering concerns, we can't make it static above the breadcrumbs portion of the page since the content that is scrollable is offset by a fixed number of pixels.
I'm open to any feedback or suggestions.

Looks great. Re placement, I think that's just fine. In fact, I actually dislike the sticky banners elsewhere, as I don't need to have this hint jump into my face all the time, reading it once is good enough :) The one downside is that one might miss it when arriving to a specific sub-section via an anchor link, but IMO that's acceptable.
What's really cool is that the "go here" link is specific to the actual page. I first thought it'd yield in a broken link on a new page added only in dev docs, but there it points to the stable doc's root. Very nice!


Error while changing choice

I'm testing the following snippet used in the docs:
     s("trig", c(1, {
     	t("Ugh boring, a text node"),
     	i(nil, "At least I can edit something now..."),
     	f(function(args) return "Still only counts as text!!" end, {})
     }))

The snippet correctly expands to "Ugh boring, a text node" and then changes to "At least I can edit something now..." when I call <Plug>luasnip-next-choice, which is <C-E> for me, but I get the following error when I call <Plug>luasnip-next-choice again:
E5108: Error executing lua .../packer/start/LuaSnip/lua/luasnip/nodes/functionNode.lua.30: attempt to call field 'normal_move_on_mark_insert' (a nil value)
When I press Enter, the text correctly changes to "Still only counts as text!!", but the text is selected as if this were an i node (I don't know whether this is intended). When I call <Plug>luasnip-expand-or-jump from there, I get another error:
E5108: Error executing lua ...site/pack/packer/start/LuaSnip/lua/luasnip/util/util.lua:92: attempt to perform arithmetic on a nil value

Whoops, I recently refactored and forgot to change a call :grimacing:
It should be fixed on master.

It's fixed now!


Feature Request: Switch from BTRFS to EXT4

There seems to be an issue with the BTRFS; saying there is not enough space on the filesystem. Please make an option for the user to choose between ext4 and btrfs. I tried the install on ext4 and verified this "out of space" error does not occur

Added!


Add NoSuperfluousPhpdocTagsFixer

Implements #2979.

What about this case?
/**
 * @param Foo $foo
 */
function bar(?Foo $foo) {}

(forgotten |null in phpdoc..)
Will the phpdoc be removed?

No, the current version only removes PHPDocs types when they match the actual typehints exactly. In some cases, the difference can be intended.

IMO, this shall be default behaviour:
https://github.com/FriendsOfPHP/PHP-CS-Fixer/issues/2979#issuecomment-323092084
adding option to define behaviour later means that default behaviour won't be good

While I'm :+1: for an option like only_when_all_superfluous, I'm :-1: to enable it by default: with PHP 7, PHPDocs should only be their to fill the remaining gaps, nothing more. This would also be in contradiction with the default behavior of phpdoc_add_missing_param_annotation (option only_untyped defaults to true).

convinced with only_untyped

Thank you @julienfalque.

Sometimes the code tells that some types is KNOWN to be unknown, almost any value like:
/**
 * @param mixed $value
 */
public function compute($value): int
{
    // ...
}

Seeing this:
public function compute($value): int
{
    // ...
}

is more often than not forgotten typehint in method. And other fixer takes care of that to make the programmer add that typehint or at least annotation.
To bad this fixer removes mixed and there is no way to turn it off. I'd like to use it along with RemoveUselessDocBlockFixer but I can't for this reason.
Otherwise great job! :+1:

I don't understand your comment. @param mixed $value has the exact same meaning as not having a typehint for $value. The annotation doesn't add any information and any automated tool should be able to detect the missing typehint with or without it, right?

That's why I wrote:

more often than not forgotten typehint in method. Other fixers/sniff takes care of that to make the programmer add that typehint or at least annotation.

It adds a value of knowing and is consistent with *TypeHintSniffs.

any automated tool should be able to detect the missing typehint

How can that tool know it it's mixed or if its forgotten?

How can that tool know if it's mixed or if it's forgotten?

It can't, and I don't think adding @param mixed $value helps.

It's matter or probability. Is this mixed or not?
public function get($id): int
{
    // ...
}

It definitely is: there is not type hint. You may expect $id to be an int (e.g. auto increment primary key) or a string (UUID). Again, this remains true if you add /** @param mixed $id */.
I don't understand why having the annotation would help guessing that an actual type hint is expected and forgotten. This should be done by analyzing what the method does and how it is used, which is out of the scope of PHP CS Fixer.

This often happens in code-reviews for new programmers, so: "There should be int typehint" is a common comment.
But having a CS tool that handle this can create blindness and skip this and then application crashes on invalid type somewhere on production.
That's why I think this is dangerous to enforce.

Also regarding to possible future compatibility: https://wiki.php.net/rfc/mixed-typehint, this typehint is needed in the doc.
Same as object was before.


Allow banned user to use the app.

Currently, if an user is banned the app will stuck at an error message, preventing to do any further actions.

Duplicate of #97
Temporary solution: You can dismiss this message and log off


unbalanced algorithm for dynamicDivideReplicas

What happened:
kind/bug
What you expected to happen:
By adding a testcase in pkg/scheduler/framework/plugins/defaultassigner/algorithm_test.go to test the algorithm on dividing replicas.
// pkg/scheduler/framework/plugins/defaultassigner/algorithm_test.go
func TestDynamicDivideReplicas(t *testing.T) {
	tests := []struct {
		name                 string
		desiredReplicas      int32
		maxAvailableReplicas []int32
		want                 []int32
	}{
		{
			desiredReplicas:      2,
			maxAvailableReplicas: []int32{3, 6, 9},
			want:                 []int32{0, 1, 1}, // but  we got [1 0 1]
		},
	}

	for _, tt := range tests {
		t.Run(tt.name, func(t *testing.T) {
			if got := dynamicDivideReplicas(tt.desiredReplicas, tt.maxAvailableReplicas); !reflect.DeepEqual(got, tt.want) {
				t.Errorf("dynamicDivideReplicas() = %v, want %v", got, tt.want)
			}
		})
	}
}

When desiredReplicas is much smaller, the algorithm gets unbalanced.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:

Clusternet version:

Clusternet-agent version (user clusternet-agent --version=json):
Clusternet-hub version (user clusternet-hub --version=json):

Kubernetes version (use kubectl version):
Cloud provider or hardware configuration:
OS (e.g: cat /etc/os-release):
Kernel (e.g. uname -a):
Others:

cc @Garrybest @Sad-polar-bear


Publisher multi-stream

Summary
In a one to many/many to many scenario, if a single user of the conference can't handle the bitrate, it would affect all the users in the conference lowering the quality of the video.
If the puplisher uploads at least 2 video quality at the same time [HD,QVGA...] , the SFU router can switch between these qualities, instead lowering the bitrate of publisher.
Additional context
Reference:
opentok

@Sean-Der We can support simulcast/SVC later so that a single publish stream can contain multiple bit rates and resolutions. When subscribing, you can subscribe to the corresponding stream by using parameters like T2, S2 | T0, S1.
related issue https://github.com/pion/webrtc/issues/1016

WIth simulcast/SVC, It would also be nice to have voice detection in the server so that we know when we are on "stage" when there are lots of users in the call so that we can send only the required substreams (s0-s2) , Please see https://webrtchacks.com/suspending-simulcast-streams/

@akilude Super good idea.

Looks like this will hopefully be supported soon! https://github.com/pion/webrtc/pull/1200


feat: migrate to listr2

See changeset

future task to figure out https://github.com/dotansimha/graphql-code-generator/issues/8045

This change seems to make the config.errorsOnly option (and the --errors-only CLI flag) unused.

This change seems to make the config.errorsOnly option (and the --errors-only CLI flag) unused.

@vhenzl, you are right, is there an option that you were actively using?

This change seems to make the config.errorsOnly option (and the --errors-only CLI flag) unused.

@vhenzl, you are right, is it an option that you were actively using?

Nah, I just discovered it when debugging #8382.

We are very much missing the --errors-only option. Was it removed on purpose?
Recent issue here https://github.com/dotansimha/graphql-code-generator/issues/8477

Any chance we could get the errorsOnly config option to work again? Watch mode output is really spamming our build script.


For ever and ever I play game of life

Game of Life game
In Python using pygame.
Fixes #342
Type of change

[x] New feature (non-breaking change which adds functionality)

Checklist:

[x] I have read the contribution guidelines before making this PR.
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented in my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation (Language folder or any other readme instructed to)
[x] My changes generates no new warnings

You have already implemented it in your repo we don't want any duplicate codes.
https://github.com/morenocl/game-of-life/blob/master/main.py
I thought you will build this from scratch. Even though it's your code, it can't be accepted here


Replace module

Updating the repo structure and contents according to the Python Packaging User Guide.

By-passing branch protections due to lack of contributors.


[Bug]: Widgets overflow the width of the canvas in edit mode when Fluid width is selected

Is there an existing issue for this?

[X] I have searched the existing issues

Description

When Fluid width is selected, the widgets in edit mode extend beyond the canvas boundaries & we are able to see a horizontal scroll in the canvas.
Also the selection of canvas size is not honoured in deploy mode.

Note: This is happening for existing git/non git apps
Steps To Reproduce

Go to https://release-ee.appsmith.com/.
Edit a git /non git app and select Fluid width.
Now choose some other canvas size and deploy the app

Expected:

The behaviour should resemble that of prod wherein there should be no horizontal scroll & widgets should be confined to the boundaries of the canvas in edit mode.
The canvas size should be honoured in deploy mode as well

Actual:

We see a horizontal scroll & widgets overflow canvas boundaries.
The canvas size is not honoured in deploy mode.

Public Sample App
No response
Environment
Deploy Preview
Severity
High (Blocker to building or releasing)
Issue video log
https://jam.dev/c/4b9296d9-b27e-476d-97b7-14ca621a2e0b
Version
Cloud

Issue has been fixed & verified on release.
https://jam.dev/c/72f3d902-e865-409a-a2f6-80ac38d4866a