fix(curriculum) - clearer RecordCollection instructions

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[ ] I have tested these changes either locally on my machine, or GitPod.

Closes #49732

Ideally a user should be able to understand or figure out what each function input means, but as we see on the forum, they just aren't quite equipped to do so by the time they reach this problem. These changes encapsulate the most common advice given to questions on the forum about this Challenge.

I replied why I think the two remaining review comments are not the way to go in my opinion, so I think we are back to waiting on review.

@jeremylt I understand your intent.  I just wish there was a way to not make it so "wordy".  This is the first challenge where logic order matters but we are still really trying to get the users understanding how to use objects.  Is there a way to present the challenge instructions to guide the user to a specific order of logic?  That should make it easier for the user to just focus on the syntax needed.  Maybe the instructions can be written to explain the logic should be written in the same order as the rules?

Do we want to that strongly push this challenge into 'exactly replicate our pseudo code'? We can always make more adjustments in the future. I think we can make the changes in this PR and then add even more hand holding if the questions on the forum show that this is still too much of a leap.

Do we want to that strongly push this challenge into 'exactly replicate our pseudo code'?

I think so.  The new project-based curriculum is going to do just that. Plus, this challenge is not part of the Basic Algorithm section, so users at this point should not be required to flesh out the algorithm.  We do it for them with the pseudo code instructions.  In fact, I would even change the instructions to reflect that this part is pseudo code (we mention it a lot but never show an example).  None of this stops users from creating different solutions, but should definitely reduce the huge leap this particular challenge has historically created and also bridge the gap between seeing a full algorithm and having the users implement it.
Personally, I wish the project-based curriculum would do more of developing the algorithms for project use cases in the beginning instead of "do this" and "do that" to create a project.

Personally I think that's the wrong approach.
Since we are directly of the opposite opinion here, I'm going to wait and only add text to the effect of "you should execute these conditions in this order" along with simplification of the bullet points using the assumption that the bullet points are coded exactly in that order if there is a broader consensus to do so.
Students often and easily miss parts of the instructions, so I think making the instructions more robust to students missing sentences or putting things in different order is the right decision here.

Personally I think that's the wrong approach.

I am not sure what part of what I said is the wrong approach, but I will just approve the PR since I whatever I do here anymore is rejected.  I am done contributing here.


feat(options): pass har entry into urlFilter callback

Possibly requires a test case for harEntry arg
Possibly requires some more common example (I used the one I encountered)
Linted

LGTM, as long as we still have 100% code coverage I'm ok with it. Would be nice to have tests though, up to you.


Bring MSRV down to rust 1.63

Rust MSRV should be brought down to 1.63 where possible and tested in CI and precommit

https://github.com/payjoin/rust-payjoin/issues/337


[1.10.2] Crash on startup

Recently downloaded the update to rftools. It crashes before minecraft can fully load. The crash report is attached. It seems to not be able to find a certain class from within the McJtyLib class? "java.lang.NoClassDefFoundError: mcjty/rftools/blocks/generator/CoalGeneratorTileEntity" Or do I need to update my forge?
Forge 2073. RFTools 1.10-5.23 . McJtyLib 1.10-2.1.0
crash-2016-09-17_09.30.47-client.txt

I think you may have to upgrade forge

Updating my forge version to 2089 (latest as of this typing) fixed this problem. Is it possible that the mod's minimum forge version is not updated, or am I overthinking? Either way this is fixed.


altool error

Hi! I have the next error during notarization
Error: Failed to find request UUID in output:

2019-10-22 04:13:50.995 altool[40274:1946835] *** Error: Unable to validate your application. We are unable to create an authentication session.

@igor-lemon That probably means the credentials you provided were incorrect or invalid

Nope, I passed correct params. Very interested that I completed success notarized the app via CLI.
xcrun altool --notarize-app
               --primary-bundle-id "com.example.ote.zip"
               --username "AC_USERNAME"
               --password "@keychain:AC_PASSWORD"
               --asc-provider <ProviderShortname>
               --file OvernightTextEditor_11.6.8.zip

I'm also seeing this w/ travis. every time. We're using env vars, which i've tried both escaped and not.
The same vars work fine locally. But on travis we're consistently seeing this error: https://travis-ci.com/maidsafe/safe_browser/jobs/248327541#L1814-L1822

2019-10-22 15:30:40.732 altool[4726:13508] *** Error: Unable to validate your application. We are unable to create an authentication session.

    at /Users/travis/build/maidsafe/safe_browser/node_modules/electron-notarize/src/index.ts:82:13

    at step (/Users/travis/build/maidsafe/safe_browser/node_modules/electron-notarize/lib/index.js:31:23)

    at Object.next (/Users/travis/build/maidsafe/safe_browser/node_modules/electron-notarize/lib/index.js:12:53)

    at fulfilled (/Users/travis/build/maidsafe/safe_browser/node_modules/electron-notarize/lib/index.js:3:58)```

Not sure what else to try here.

That build is on xcode11.2

We're also seeing this issue on the Bamboo side of things. Same issue. Locally the env vars work fine and the app is successfully notarized, however when the build happens on Bamboo it no longer works and we are shown the same error
error	25-Oct-2019 12:34:57	Error: Failed to find request UUID in output:
error	25-Oct-2019 12:34:57	2019-10-25 12:34:57.188 altool[66977:3177522] *** Error: Unable to validate your application. We are unable to create an authentication session.

Was having the same issue but it was down to not having an app specific password for the account being used to sign with as the appleId would have 2 factor enabled.
https://support.apple.com/en-us/HT204397
After providing the correct auth, works well with xcode 11.2

As an update to my comment above, the issue was solved by fixing a user error 😂 I was setting environment variables in the wrong place.

I was running into the same issue.
I found it useful to debug the root cause to run xcrun altool --notarize-app with the --verbose flag.
Following that I saw that the last error was actually:
2019-11-14 09:27:07.743 altool[40837:10907862] jsonResponse as string = {"result":{"Errors":["Please sign in with an app-specific password. You can create one at appleid.apple.com. (-22910)"],"EnableJWTForAllCalls":false,"RestartClient":false,"ErrorCode":-22910,"ErrorMessage":"Please sign in with an app-specific password. You can create one at appleid.apple.com. (-22910)","Success":false},"id":"2019111492707-580","jsonrpc":"2.0","error":{"message":"Please sign in with an app-specific password. You can create one at appleid.apple.com. (-22910)","code":-22910}}
2019-11-14 09:27:07.776 altool[40837:10907862] Web service call (authenticateForSession) result: {
    EnableJWTForAllCalls = 0;
    ErrorCode = "-22910";
    ErrorMessage = "Please sign in with an app-specific password. You can create one at appleid.appl...";
    Errors =     (
        "Please sign in with an app-specific password. You can create one at appleid.appl..."
    );
    RestartClient = 0;
    Success = 0;
}

And as suggested by @chandika the fix was indeed to create an app specific password and use that to login.

FWIW, v0.2.0 works for me on travis now. 👍

I've found myself having this issue now myself. I have been notarizing without issue until as recently as last month. But today, I tried to update my app as normal, and keep getting this error. I already had an app specific password, but I created a new one just in case, added to the keychain, but the same error persists.
Anyone else found this has cropped again recently?

You found an solution @dboakes ?


adding a timeout for execution

NOTE:-  This PR should only be merged after this one https://github.com/ExecutableBookProject/jupyter-cache/pull/48
Hey @chrisjsewell , should we give a timeout of -1 like this? because a few notebooks where failing with timeout error. Or do we want to control its value from somewhere?

closes https://github.com/ExecutableBookProject/MyST-NB/issues/139

closes #139

Note that this, I believe, needs to be in the initial comment, to be auto-added to the linked issues.

See comment in ExecutableBookProject/jupyter-cache#48

@choldgraf Note that the tests here will fail until the PR in jupyter-cache is merged

ah nice! The tests here look good, though I think we should probably be testing in jupyter-cache as well. Wanna copy over (or more over) some of the testing functionality that is here and put it into jupyter-cache? I think in general its good to test functionality within the tool that provides it, instead of in a downstream tool that builds on top of jupyter-cache.

@choldgraf ahh. good point. I will do the necessary changes.

@choldgraf  Thanks for the merge in jupyter-cache. Once, we release a new version of jupyter-cache, we can get back to the tests in this PR.

nice! is there anything preventing a new release of jupyter-cache from happening? If not can we just cut a new release? I am not as familiar with that codebase

@choldgraf I don't think there is anything preventing us. We can safely do a new release i think.

Looks, like @chrisjsewell , just made a new release. Thanks

@choldgraf should I push a new dummy commit for the CI to rerun the tests or we can re-trigger it somewhere from the server.
Not whining, but my laptop broke down yesterday, and I am trying to fix it. So, wont be able to make a push for a couple days I think. I will make a dummy push as soon as possible, if we can't re-trigger the CI tests.

Feel free to push a dummy commit - that'll just trigger everything

@choldgraf this looks good now.

wohooo! thanks @AakashGfude for pushing this through!


boost/asio/detail/addressof.hpp: No such file or directory

gitpod /workspace/some-ip/vsomeip/build (master) $ sudo apt-get install doxygen asciidoc graphviz source-highlight libboost-system-dev libboost-thread-dev libboost-log-dev
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
libboost-system-dev is already the newest version (<IP_ADDRESS>ubuntu7).
libboost-thread-dev is already the newest version (<IP_ADDRESS>ubuntu7).
asciidoc is already the newest version (10.1.2-1).
doxygen is already the newest version (1.9.1-2ubuntu2).
graphviz is already the newest version (2.42.2-6).
libboost-log-dev is already the newest version (<IP_ADDRESS>ubuntu7).
source-highlight is already the newest version (3.1.9-4.1build2).
0 upgraded, 0 newly installed, 0 to remove and 64 not upgraded.
gitpod /workspace/some-ip/vsomeip/build (master) $ make clean
gitpod /workspace/some-ip/vsomeip/build (master) $ make
[  1%] Building CXX object CMakeFiles/vsomeip.dir/implementation/endpoints/src/client_endpoint_impl.cpp.o
[  2%] Building CXX object CMakeFiles/vsomeip.dir/implementation/endpoints/src/credentials.cpp.o
[  4%] Building CXX object CMakeFiles/vsomeip.dir/implementation/endpoints/src/endpoint_definition.cpp.o
[  5%] Building CXX object CMakeFiles/vsomeip.dir/implementation/endpoints/src/endpoint_impl.cpp.o
In file included from /workspace/some-ip/vsomeip/implementation/helper/boost/asio/datagram_socket_service_ext.hpp:33,
from /workspace/some-ip/vsomeip/implementation/helper/boost/asio/basic_datagram_socket_ext.hpp:24,
from /workspace/some-ip/vsomeip/implementation/helper/boost/asio/ip/udp_ext.hpp:20,
from /workspace/some-ip/vsomeip/implementation/endpoints/src/endpoint_impl.cpp:8:
/workspace/some-ip/vsomeip/implementation/helper/boost/asio/detail/reactive_socket_service_ext.hpp:29:10: fatal error: boost/asio/detail/addressof.hpp: No such file or directory
29 | #include <boost/asio/detail/addressof.hpp>
|          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [CMakeFiles/vsomeip.dir/build.make:118: CMakeFiles/vsomeip.dir/implementation/endpoints/src/endpoint_impl.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:149: CMakeFiles/vsomeip.dir/all] Error 2
make: *** [Makefile:136: all] Error 2

gitpod /workspace/some-ip/vsomeip/build (master) $ sudo apt-get install doxygen asciidoc graphviz source-highlight libboost-system-dev libboost-thread-dev libboost-log-dev Reading package lists... Done Building dependency tree... Done Reading state information... Done libboost-system-dev is already the newest version (<IP_ADDRESS>ubuntu7). libboost-thread-dev is already the newest version (<IP_ADDRESS>ubuntu7). asciidoc is already the newest version (10.1.2-1). doxygen is already the newest version (1.9.1-2ubuntu2). graphviz is already the newest version (2.42.2-6). libboost-log-dev is already the newest version (<IP_ADDRESS>ubuntu7). source-highlight is already the newest version (3.1.9-4.1build2). 0 upgraded, 0 newly installed, 0 to remove and 64 not upgraded. gitpod /workspace/some-ip/vsomeip/build (master) $ make clean gitpod /workspace/some-ip/vsomeip/build (master) $ make [ 1%] Building CXX object CMakeFiles/vsomeip.dir/implementation/endpoints/src/client_endpoint_impl.cpp.o [ 2%] Building CXX object CMakeFiles/vsomeip.dir/implementation/endpoints/src/credentials.cpp.o [ 4%] Building CXX object CMakeFiles/vsomeip.dir/implementation/endpoints/src/endpoint_definition.cpp.o [ 5%] Building CXX object CMakeFiles/vsomeip.dir/implementation/endpoints/src/endpoint_impl.cpp.o In file included from /workspace/some-ip/vsomeip/implementation/helper/boost/asio/datagram_socket_service_ext.hpp:33, from /workspace/some-ip/vsomeip/implementation/helper/boost/asio/basic_datagram_socket_ext.hpp:24, from /workspace/some-ip/vsomeip/implementation/helper/boost/asio/ip/udp_ext.hpp:20, from /workspace/some-ip/vsomeip/implementation/endpoints/src/endpoint_impl.cpp:8: /workspace/some-ip/vsomeip/implementation/helper/boost/asio/detail/reactive_socket_service_ext.hpp:29:10: fatal error: boost/asio/detail/addressof.hpp: No such file or directory 29 | #include <boost/asio/detail/addressof.hpp> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ compilation terminated. make[2]: *** [CMakeFiles/vsomeip.dir/build.make:118: CMakeFiles/vsomeip.dir/implementation/endpoints/src/endpoint_impl.cpp.o] Error 1 make[1]: *** [CMakeFiles/Makefile2:149: CMakeFiles/vsomeip.dir/all] Error 2 make: *** [Makefile:136: all] Error 2

Did you solve this issue? :-)

Just did a quick google search, this is a common issue.
One of the results:
https://stackoverflow.com/questions/55306598/how-to-fix-fatal-error-boost-asio-hpp-no-such-file-or-directory

This is a common issue, not related to this project.


Bumping ursa to 0.9.4

ursa 0.9.4 has fixes for node 6 deprecation warnings and efforts to fix the issues with installing it.

Coverage remained the same at 92.142% when pulling 2db9c63bb0617d7bc35c4fa7194cde41c86c41f9 on mwain:bump-ursa into 2c9c537f5a0e583b87f208ad2ccaa8004e792b9f on vpulim:master.

Coverage remained the same at 92.142% when pulling 320f142f00267e284f268f5279e8945929bbc512 on mwain:bump-ursa into 2c9c537f5a0e583b87f208ad2ccaa8004e792b9f on vpulim:master.

@herom I have updated this PR to remove the other changes.

Coverage remained the same at 92.146% when pulling e8c3ccab3a6791f03c82d9b7801b567a69d0fae4 on mwain:bump-ursa into 2091f2e0931019b1124bbe9cba4b83ddbae25064 on vpulim:master.

Coverage remained the same at 92.146% when pulling e8c3ccab3a6791f03c82d9b7801b567a69d0fae4 on mwain:bump-ursa into 2091f2e0931019b1124bbe9cba4b83ddbae25064 on vpulim:master.

Thanks a lot :+1:


Main Epic for Zero Downtime upgrades

The MVP for zero down time upgrades is that a user's application can not be impacted by Rancher's upgrade process of Kubernetes. At a minimum this means that the user's workloads need to be available on at least a single node and that all critical add on services are available, though possibly degraded, during the upgrade.
The following needs to be true of a user's cluster:

3 or more etcd nodes
2 or more control plane nodes
2 or more worker nodes
Ingress, DNS and other add ons are schedulable to more than a single node.
The upgrade is from minor release to the next or within the same patch release series. Skipping minor releases will not be supported as zero downtime.

From a user workload perspective the following will need to be true:

User's applications are deployed with a scale >1 and across more than a single node.
User's applications make use of liveness and readiness probes.

To achieve MVP:

Before starting the upgrade of worker nodes, the etcd and control plane nodes need to be upgraded first.
Worker nodes will be updated in a user specified batch size.

The next batch will only be upgraded when the previous batch has returned to service.
If the nodes do not return to service in a specified timeout interval, an alert should be triggered.

Configure the addon upgrade options and disruption budgets based on the number of nodes in the cluster.

The max.unavailable and max.surge values should be user specified.
Use Pod Disruption Budgets where it makes sense.

Documentation to explain the upgrade process of RKE provisioned clusters needs to be provided.

Upgrades of the Kubernetes control plane should be handled similarly.

Control plane nodes should be upgraded 1 node at a time.
The control plane node should come completely back up before moving to the next.

Etcd nodes:

Current upgrade procedures already handle zero downtime upgrades.

Granular control of when upgrades happen:

Operationally user's would upgrade the etcd plane first. Followed by control and then upgrading the worker pool. Allowing user's the ability to control the upgrade of the various tiers is key.

As part of this, we also need to be able to rollback to the previous version and restore a snapshot of the data. Such that the recommended best practice would be:

take a snapshot of cluster.
initiate upgrade.
If upgrade fails
rollback to previous version
restore etcd snapshot.

Related issues:
rancher/rancher#20465
rancher/rancher#17057

https://xd.adobe.com/view/ebd4dccd-69a0-41fb-78af-907601a6a2f6-9de5/

To elaborate on the restore/rollback functionality.
The user flow for the feature is that:

The user took a snapshot before initiating a cluster upgrade.
The user initiated an upgrade once the snapshot was complete.
During the upgrade, the user decided it is not going well and needs to revert/rollback the changes.
The user selects to revert the kubernetes upgrade to the pre-upgraded version and restore the snapshot taken just before upgrade.

In this workflow we need to assume the following:

Rancher should know the version of the Kubernetes version running before the upgrade at the time the snapshot was taken. This should be used by Rancher when rolling back to prevent user error.
The cluster is likely in a failed state, and Rancher might have to be aggressive in how it handles reverting.
Before using the snapshot in the etcd datastore, the cluster should be running the pre-upgrade kubernetes version.

Constraints:

When initiating the upgrade, the user should have the option to specify a snapshot be taken.
The operation can be initiated via the API (Terraform UX should be able to follow the same workflow)
The restore operation will work on a cluster that is not in a healthy / Active state.

@cloudnautique  One use case we are trying to pursue is immutable infrastructure for OS patches and even installed software like docker and kubernetes. The no downtime approach to upgrades is great but it still re-uses the same VM that could have been spun up with a node-driver. We were wondering if there could be an option to replace (rebuild) the node that way it could use an upgraded VM template/image if the node template was updated as well. We rebuild our VM images often for OS patches, etc.
Right now we have to run a script that rolling re-creates nodes by either looping through each in a pool and deleting them and waiting for it to come back.

Verified on latest master-head.

Control plane nodes get upgraded based on maxUnavailable_control param.
Worker node gets upgraded based on maxUnavailable_worker param


Outline tree shows duplicate local variables for a Python function

Environment data

VS Code version: 1.49.0
Extension version (available under the Extensions sidebar): v2020.8.109390
OS and version: openSUSE Leap 15.2
Python version (& distribution if applicable, e.g. Anaconda): 3.6.8
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A
Relevant/affected Python packages and their versions:
Relevant/affected Python-related VS Code extensions and their versions:
Value of the python.languageServer setting: Microsoft

[NOTE: If you suspect that your issue is related to the Microsoft Python Language Server (python.languageServer: 'Microsoft'), please download our new language server Pylance from the VS Code marketplace to see if that fixes your issue]
Expected behaviour
Outline should display local variable only once per function (the line of first definition).
Actual behaviour
Outline displays same variable multiple times. this just clutters the view with same line
Steps to reproduce:

Open any python file (tested with python3)
Write a sample function in which single variable is used multiple times in the function
Check the outline view and you will find same variable listed multiple times

[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]
Image for reference

Logs

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

XXX

this issues is not seen in latest Pylance language server


Title: i want to add Periodic table game

Is your feature request related to a problem? Please describe.
i want to add Periodic table game
Describe the solution you'd like.
Game logic and basic description : there 2 page index => shows all elements , game page = > user needs to find symbol of provided elements.
Describe alternatives you've considered.
Game points: if select correct element score increase . if wrong element selected then deducted.
Add any other context or screenshots about the feature request here.

hey @swapnilsparsh , please assign i have made it already.

@Vipullakum007 Thank you for providing your insight but it is not required as of now


Does our pricing model include all the right DEXes?

We currently use:

Sushi
Uni 2/3

Should we be adding others, like Pancake, or even looking at aggregators like 1inch?

UniV2/V3/Curve/Sushi cover majority of the liquidty on ethereum Mainnet.
We add support to 1Inch to include those smaller exchanges and small-volume tokens (Shiba, Moon) and two more exchanges (Bancor and Balancer)

1Inch: https://docs.1inch.io/docs/spot-price-aggregator/introduction, easy integration.
Bancor: https://docs.bancor.network/developer-guides/contracts
Balancer: https://docs.balancer.fi/concepts/math/weighted-math

Previous PR on Bancor and Balancer: https://github.com/credmark/credmark-models-py/issues
The roadmap ahead could be:
Cross-chain exchanges

https://docs.synapseprotocol.com/how-it-works/amm
https://thorchain.org/getting-started

Chain-specific exchages

BSC: Pancake
Polygon: https://quickswap.exchange/#/

I created the model for 1Inch. Testing the price for AAVE token is close to existing model, however testing with special case like ETH (not WETH) gives 1 ETH = 0.973748 ETH. Strange result. I will not add it to our pricing model till we identify some special tokens.

1 ETH = 0.973748 ETH. Strange result

Filed this issue to 1Inch team.

Bug 2: the node we are using on the gateway does not fully support 1inch.
{
    "slug": "price.one-inch",
    "version": null,
    "chainId": 1,
    "blockNumber": 14249443,
    "error": {
        "type": "ModelRunError",
        "message": "Exception running model price.one-inch({'address': '0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48'}) on chain 1 block 14249443 (2022-02-21 12:31:34) with {'code': -32000, 'message': 'execution aborted (timeout = 5s)'}",
        "stack": [
            {
                "slug": "price.one-inch",
                "version": "0.1",
                "chainId": 1,
                "blockNumber": 14249443,
                "trace": "Traceback (most recent call last):
  File '/var/task/packages/credmark/cmf/engine/context.py', line 644, in _run_local_model_with_class
    output = model.run(input)
  File 'models/credmark/price/one_inch.py', line 24, in run
    p = offchain_contract.functions.getRateToEth(input.address, True).call(
  File '/var/task/packages/web3/contract.py', line 957, in call
    return call_contract_function(
  File '/var/task/packages/web3/contract.py', line 1501, in call_contract_function
    return_data = web3.eth.call(
  File '/var/task/packages/web3/module.py', line 57, in caller
    result = w3.manager.request_blocking(method_str,
  File '/var/task/packages/web3/manager.py', line 198, in request_blocking
    return self.formatted_response(response,
  File '/var/task/packages/web3/manager.py', line 171, in formatted_response
    raise ValueError(response['error'])
ValueError: {'code': -32000, 'message': 'execution aborted (timeout = 5s)'}
"
            }
        ],

While the custom erigon node returns
credmark-dev run price.one-inch -j -i {"address": "0xdac17f958d2ee523a2206206994597c13d831ec7"} -b 14249443 -j

{
    "slug": "price.one-inch",
    "version": "0.1",
    "chainId": 1,
    "blockNumber": 14249443,
    "output": {
        "just": {
            "price": 0.0003810711693737641,
            "src": "price.one-inch"
        }
    },
    "dependencies": {
        "contract.metadata": {
            "1.0": 2
        },
        "price.one-inch": {
            "0.1": 1
        }
    }
}

@leafyoung so is the implication is that it's good we're switching to new node?
@0xpetersatoshi @abhishektvz are you guys close to finishing testing necessary to switch to new node?

UniV2/V3/Curve/Sushi cover majority of the liquidty on ethereum Mainnet.
We add support to 1Inch to include those smaller exchanges and small-volume tokens (Shiba, Moon) and two more exchanges (Bancor and Balancer)

1Inch: https://docs.1inch.io/docs/spot-price-aggregator/introduction, easy integration.
Bancor: https://docs.bancor.network/developer-guides/contracts
Balancer: https://docs.balancer.fi/concepts/math/weighted-math

Previous PR on Bancor and Balancer: https://github.com/credmark/credmark-models-py/issues
The roadmap ahead could be:
Cross-chain exchanges

https://docs.synapseprotocol.com/how-it-works/amm
https://thorchain.org/getting-started

Chain-specific exchages

BSC: Pancake
Polygon: https://quickswap.exchange/#/

@murphy @leafyoung I would agree with Kunlun to use 1nch for some smaller token and then definitely Balancer, Bancor and Loopring (this would be an L2 rollup).
In terms of PanCake Swap and Quickswap - not sure if this makes sense to add them already until we decide to have BSC Data and Polygon Data available as a whole (so in terms of a separate Data ETL).
@murphy OR do we go a different route with the price API and offer price data only for different chains "without" anything else, so no complete Data ETL? not sure if this is possible

Balancer is larger than Sushiswap, next to be implemented. https://dune.com/hagaetc/dex-metrics

1 ETH = 0.973748 ETH. Strange result

Filed this issue to 1Inch team.

@leafyoung seems like the price of stETH compared to ETH as stETH is trading at this price

Good guess but it's coincidence. stETH is 0.9709 now.
For a past block 14249443 (2022-02-21), ETH was 1.123 ETH while stETH was 0.9989 ETH.


'value' missing for Germplasm Attributes

Original Question from @GuilhemSempere

On january 8th you replied to me specifying that attributes?germplasmDbId={germplasmDbId} in V2 can be used as a replacement for germplasm/{germplasmDbId}/attributes in V1.3. However I'm not sure how to actually return attribute values in V2 because the "value" field seems to have disappeared from the response object (many others appeared though, so perhaps I'm missing something)

Response

I'm so glad you asked this, you are totally correct, I really mucked this one up! I completely mixed up the concepts of Attribute Definition and Attribute Value.

Three ideas to resolve this off the top of my head:
Option 1 is to replace the '/germplasm/{dbid}/attributes' exactly as it was.
Pros - really easy for me to do quickly
Cons - No way to upload (POST/PUT) new attribute values
Option 2 is to add 'value' and 'determinedDate' to the '/attribute' object. I thought it was there already, but I never really considered the ramifications of this. I would also need to add 'germplasmDbId' so that a value can be related to both a germplasm and an attribute definition.
Pros - again, easy for me to do quickly. Could upload new attribute values with definition
Cons - Messy, confusing the ideas of an attribute definition with and attribute value.
Option 3 is to create a '/attributeValues' entity. This would follow the Observations model a little better.
There you have 'ObservationUnit' -> 'Observation' <- 'ObservationVariable'
but here we would have 'Germplasm' -> 'Attribute Value' <- 'Attribute Definition'
Pros - clean, comprehensive model
Cons - A lot of new stuff to add right before v2.0 is supposed to be frozen

... btw, would option 3 allow querying attributes for multiple germplasm at a time?

Yes


The result of depth prediction.

Hello, we can see the results of the in-depth prediction in Table 2 of the paper. How can we obtain this result during the assessment? Is this part of the code available?

It is not available for now.


Consent is always persisted to the grant store if client is allowed to remember, regardless of if the user actually chooses to do so

It looks like if a client has the AllowRememberConsent enabled, the consent will always be persisted to the grant store regardless of whether the user chooses to remember or not. The relevant code where this happens is here in AuthorizeInteractionResponseGenerator.ProcessConsentAsync at the end of the method:
// they said yes, set scopes they chose
request.Description = consent.Description;
request.ValidatedResources = request.ValidatedResources.Filter(consent.ScopesValuesConsented);
Logger.LogInformation("User consented to scopes: {scopes}", consent.ScopesValuesConsented);

if (request.Client.AllowRememberConsent)
{
	// remember consent
	var scopes = Enumerable.Empty<string>();
	if (consent.RememberConsent)
	{
		// remember what user actually selected
		scopes = request.ValidatedResources.RawScopeValues;
		Logger.LogDebug("User indicated to remember consent for scopes: {scopes}", scopes);
	}

	await Consent.UpdateConsentAsync(request.Subject, request.Client, request.ValidatedResources.ParsedScopes);
}

Notice how await Consent.UpdateConsentAsync is outside of the if (consent.RememberConsent) code block. This means that consent will always be persisted as long as client has the AllowRememberConsent enabled and it doesn't matter if the user chooses to do so or not.
Additionally, the variable scopes seems to serve no purpose other than to be logged.
Instead I believe the logic should be as follows:
if (request.Client.AllowRememberConsent && consent.RememberConsent)
{
	// remember consent
	Logger.LogDebug("User indicated to remember consent for scopes: {scopes}", request.ValidatedResources.RawScopeValues);
	await Consent.UpdateConsentAsync(request.Subject, request.Client, request.ValidatedResources.ParsedScopes);
}
else
{
	// cleanup consent from any previous interactions if user decided to no longer remember decision
	// ****code below is just a mockup, in practice, we will need to inject the default user consent store
	await DefaultUserConsentStore.RemoveUserConsentAsync(request.Subject, request.Client);
}

Related to this: https://github.com/IdentityServer/IdentityServer4/pull/4849
So the PR fixes the issue.


Add matrix agent

Is this on the right track? I took post_agent.rb and modified and googled. It's been 10y+ since I wrote ruby.

Hi! That generally looks good. I think it would be better suited in a Agent gem, because we generally only accept replacements for existing Agents that talk to a specific service or a general "helper" Agent.

@ptman did you ever extract this to a gem? I'd love to use it to wire some stuff up for the conference I volunteer for, which runs on Matrix.


Mark origin of a mention when posting from Twitter to Mastodon

Added the capability to check for any mentions to other users on Twitter and append<EMAIL_ADDRESS>to avoid any mixups on Mastodon.

Good idea. merged.


Results not reproducable?

Hello CIOD authors,
I was trying to  run your code on VOC but couldnot reporduce the results with the command that was given in the repo. Are there any specific hyperparameters that I need to change to reporduce the results in the  paper. With the deafult settings I only get the following for VOC:
========== RCNN Test set Summary (mAP, AP, %) NOREPR  NEW ==========
66.77 :	76.27	77.38	71.37	61.54	47.27
58.15 :	48.92	69.31	53.01	38.05	25.31	67.56	82.25	80.12	43.44	73.47
32.62 :	12.42	17.92	20.97	15.87	16.40	42.24	53.29	20.44	15.03	22.77	36.49	49.47	69.63	24.23	72.08
25.76 :	12.61	11.40	10.18	10.13	6.16	7.87	39.36	31.07	6.06	5.07	5.70	21.64	53.77	35.47	52.51	29.91	31.24	52.66	42.50	49.89
========== RCNN Test set Group Summary (mAP, AP, %) NEW NOREPR ==========
Group  0 : 66.77	->	46.92	->	16.72	->	10.09
Group  1 : 69.37	->	30.75	->	17.89
Group  2 : 50.38	->	33.82
Group  3 : 41.24

Hi, I checkout commit d58255605e37e362ee746637fe93efb669a7e7ab, and the result cannot reproduce either.
========== RCNN Test set Summary (mAP, AP, %) NOREPR  NEW ==========
55.99 : 68.03   77.50   65.89   42.34   26.19
51.84 : 32.66   46.17   44.88   32.98   20.19   66.97   77.00   84.69   38.08   74.83
42.74 : 20.14   30.03   34.22   24.78   25.12   55.58   39.10   62.23   18.98   28.70   31.66   70.8068.01    60.91   70.80
40.17 : 18.12   28.53   36.02   25.88   22.35   17.68   49.11   50.75   20.00   29.34   18.67   57.6067.06    54.68   60.44   28.74   45.39   57.46   56.05   59.46
========== RCNN Test set Group Summary (mAP, AP, %) NEW NOREPR ==========
Group  0 : 55.99        ->      35.38   ->      26.86   ->      26.18
Group  1 : 68.31        ->      40.92   ->      33.38
Group  2 : 60.44        ->      51.69
Group  3 : 49.42
which has a huge gap with the result in paper. Can you reproduce the result on your server and help me figure out the problem? Thanks!


Allow taking snapshots of powered-off VMs for vCenter

Description
Currently OpenNebula does not allow taking a snapshot of a powered-off VM:
$ onevm snapshot-create 58
[one.vm.snapshotcreate] Could not create a new snapshot for VM 58, wrong state POWEROFF.

This is not actually a  vCenter restriction, so OpenNebula should allow it.
Use case
Allow VM snapshots when a VM is powered-off for vCenter
Interface Changes
Core and Sunstone
Additional Context
After implemented remove restriction from documentation.

Progress Status

[ ] Branch created
[ ] Code committed to development branch
[ ] Testing - QA
[ ] Documentation
[ ] Release notes - resolved issues, compatibility, known issues
[ ] Code committed to upstream release/hotfix branches
[ ] Documentation committed to upstream release/hotfix branches

Related https://github.com/OpenNebula/one/issues/1205#issuecomment-345666285


Removing notifications from Notification Centre too.

Hello!
It seems that you program is working well on Catalina too, but it'd be great if it also could remove notifications from Notification Centre too. I get a lot of notifications and sometimes removing them one by one isn't really great.
I also recommend you that you make this program accessible from status bar near WiFi icons that stuff like that. It's be easier to reach and not that many people would like to have one slot in their Dock dedicated for program that only removes notifications.

Working on it! 💻 🔨


Find a Custom Control with FLaUI

Dear,
I am wondering if I can find a custom control with FLaUI. I have a custom usercontrol in WPF which has a property with a list of custom objects (say a list of graph objects.) Is it possible to get with FlaUI to get that custom usercontrol and then that list? I looked around already in the code but not sure were to start. I think to make a custom cast of somekind then? Or is it not possible at all?

Depending on the custom control, you can just use it with the basic AutomationElement and use all the patterns / properties you need. Of course you can also create your own class, inherited from AutomationElement which nicely provide the supported patterns/properties. Easiest is to first check what patterns and properties the custom element exposes with any inspect tool like FlaUInspect.

The FlaInspect tool only gives me that it is a custom control with the excepted ClassName. No other properties that I need. So I have to remake my custom control in the FlaUI code, in herited from AutomationElement, and then set my list of graph objects as a property? Just asking, my code knowledge is not that great. So in FLaUI.Core adding my own class for my custom control?

No supported patterns and no child controls? If so, then the custom control does not provide any UIA information. The control needs to implement/privide that automation/accessibility information, otherwise FlaUI (and other UIA based libraries like White) do not work.

automation information to the custom control is added how? I see here things about AutomationPeer class (https://blogs.msdn.microsoft.com/patrickdanino/2009/11/11/custom-controls-and-ui-automation/) and using of GUID's to identify the property with server/client (https://blogs.msdn.microsoft.com/winuiautomation/2010/12/07/uia-custom-patterns-part-1/) Not sure which one should be taken. Thanks already for the information

I got  the Automation peer working with the following code:
This code is added to my custom control class:
protected override AutomationPeer OnCreateAutomationPeer()       {          return new GraphControlAutomationPeer(this);       }
and made this class which implements the Value pattern:
`public class GraphControlAutomationPeer : FrameworkElementAutomationPeer, IValueProvider
{
private string _currentValue = "TestValue";
  public GraphControlAutomationPeer(GraphControl owner) : base(owner)
  {

  }

  protected override AutomationControlType GetAutomationControlTypeCore()
  {
     return AutomationControlType.Custom;
  }

  protected override string GetClassNameCore()
  {
     return Value.GetType().Name;
  }

  public override object GetPattern(PatternInterface patternInterface)
  {
     if (patternInterface == PatternInterface.Value)
     {
        return this;
     }
     return base.GetPattern(patternInterface);
  }

  public string Value
  {
     get
     {
        return _currentValue;
     }
  }

  public bool IsReadOnly
  {
     get
     {
        return false;
     }
  }

  public void SetValue(string value)
  {
     //parsing of the values
     this._currentValue = value;
  }

}`
When I run a test WPF in debug mode with the custom control (GraphControl), the value and pattern is seen in the inspect tool.

When I place the same custom control in a larger project
and run that .exe of that project, value and custom control is not seen. Does anyone has an idea why its not displayed?


Export platform specific request handlers

What is it?

[x] Feature / enhancement
[ ] Bug
[ ] Docs / tests

Description

For a while now, we've had the platform field on available on the RequestHandler type, but the field is typed to unknown and most users are completely unaware that it exists.
This PR exports special RequestHandler* types from the middlewares for users to take advantage of when developing for their specific platform.
Checklist:

[x] My code follows the developer guidelines of this project
[x] I have performed a self-review of my own code
[x] I have made corresponding changes to the documentation
[ ] Added new tests to cover the fix / functionality

Not sure what's happening with the build error. Is @public not the correct tag for these type exports?

It's  * @alpha

I think it's a great PR!

Thanks. Jeez. Still not building after using alpha tags and running yarn api.update. Not sure what I broke.

I guess it works better when you run api.update from the project root. Should be good now!


RAS-1147 Upgrade to flask-session 0.8.0 update in rOps

What and why?
Bumping flask-session to version latest version which had breaking changes (for 0.8.0) to how it handled datetime objects.  With the updated code from RAS-1177, the latest version can now be used.
How to test?

Deploy this PR to your environment
sign into rOps with the default uaa_user account
check that you can send a new message
click around making sure no 500 are raised because of a comparison error between str and datetime objects

Jira
RAS-1147

/deploy scorfs

/deploy scorfs

/deploy robinm3


unexpected argument --version  found

🐛 Bug description
While trying to upgrade wasm-pack to 1.2.0, we found that the --version regression test failed
$ /opt/homebrew/Cellar/wasm-pack/0.12.0/bin/wasm-pack --version
error: unexpected argument '--version' found

  tip: a similar argument exists: '--verbose'

Usage: wasm-pack <--verbose...|--quiet|--log-level <LOG_LEVEL>> <COMMAND>

For more information, try '--help'.

🤔 Expected Behavior
The version check should pass
👟 Steps to reproduce
just a cargo install build and run the --version check against the built binary
🌍 Your environment
Include the relevant details of your environment.
wasm-pack version:
rustc version: rustc 1.70.0 (90c541806 2023-05-31) (built from a source tarball)

This is the --help
$ /opt/homebrew/Cellar/wasm-pack/0.12.0/bin/wasm-pack --help
📦 ✨  pack and publish your wasm!

Usage: wasm-pack [OPTIONS] <COMMAND>

Commands:
  build    🏗  build your npm package!
  pack     🍱  create a tar of your npm package but don't publish!
  new      🐑 create a new project with a template
  publish  🎆  pack up your npm package and publish!
  login    👤  Add an npm registry user account! (aliases: adduser, add-user)
  test     👩🔬  test your wasm!
  help     Print this message or the help of the given subcommand(s)

Options:
  -v, --verbose...             Log verbosity is based off the number of v used
  -q, --quiet                  No output printed to stdout
      --log-level <LOG_LEVEL>  The maximum level of messages that should be logged by wasm-pack. [possible values: info, warn, error] [default: info]
  -h, --help                   Print help

Just noticed this too

+1, I was using wasm-pack --version in a build script to check the right version of wasm-pack is installed.
$ wasm-pack --version    # before
wasm-pack 0.11.0
$ wasm-pack --version    # after installing 0.12
error: unexpected argument '--version' found

  tip: a similar argument exists: '--verbose'
...

Yeah, not to pile on but this broke our CI over the weekend too (below). Currently we run https://rustwasm.github.io/wasm-pack/installer/init.sh to install, which maybe isn't a good practice. Is there a way this script can pin to a version?


preflight fails to pull the image when registry is insecure

Bug Description
preflight fails to pull the image when registry is insecure [scan.connect.qa.redhat.com]
Version and Command Invocation
certification library version 1.1.0-rc1
Steps to Reproduce:
(How can we reproduce this?)

Run preflight container check with scan.connect.qa.redhat.com

Expected Result
Preflight should be able to pull registry which is insecure
Actual Result
./preflight-linux-ppc64le check container scan.connect.qa.redhat.com/ospid-625fee031a18b6ac329b82a5/containere2e-power:1650455635 --pyxis-api-token XX --certification-project-id 625fee031a18b6ac329b82a5 --pyxis-host catalog.qa.redhat.com/api/containers --submit -d ./auth.json time="2022-04-20T08:24:47-04:00" level=debug msg="config file not found, proceeding without it" time="2022-04-20T08:24:47-04:00" level=info msg="certification library version 1.1.0-rc1 <commit: 0c0918de527faae53b5df9efb7a054af533d455c>" time="2022-04-20T08:24:47-04:00" level=debug msg="URL is: https://catalog.qa.redhat.com/api/containers/v1/projects/certification/id/625fee031a18b6ac329b82a5" time="2022-04-20T08:24:48-04:00" level=debug msg="Certification project name is: container-e2e-power" time="2022-04-20T08:24:48-04:00" level=debug msg="target image: scan.connect.qa.redhat.com/ospid-625fee031a18b6ac329b82a5/containere2e-power:1650455635" time="2022-04-20T08:24:48-04:00" level=debug msg="pulling image from target registry" Error: failed to pull remote container: Get "https://scan.connect.qa.redhat.com/v2/": x509: certificate signed by unknown authority time="2022-04-20T08:24:48-04:00" level=fatal msg="failed to pull remote container: Get \"https://scan.connect.qa.redhat.com/v2/\": x509: certificate signed by unknown authority"
Additional Context
Crane provides flag for insecure registry can we expose it to preflight?
https://github.com/google/go-containerregistry/blob/main/cmd/crane/doc/crane.md#options

Had a PR up but closed it, since we'll probably want to have an "insecure" Crane option tied to a user flag.
similarly to curl's -k, --insecure


Testing new macos lane

Summary
With the import of dotnet/runtime samples that demonstrate how to build iOS, Android, and wasm apps on top of the mono runtime,  a check to ensure that these have built properly is needed. The mono samples need to pull down a runtime pack to properly build the application, so dotnet publish will be used instead of dotnet build.
The applications will not be ran for these checks. Ensuring that the applications can be built is the primary goal.
This PR looks to add another GitHub Actions workflow that targets these mono-samples.
When a file that influences the publish process is changed, the original build shall not be ran for the project, instead, the new one will be ran.
As seen in this PR, the original build check does not run for this PR, only Publish Mono Samples is ran.

Under the scenario where both a mono sample and non-mono sample are modified in the same pull request, is there a way to run the original build validation without the mono sample changes?
How can we bypass building mono samples on the windows vm?
I don't think
    paths-ignore:
    - 'core/mono-samples/**'

achieves this.
Perhaps core/mono-samples/** can be omitted in Locate projects for PR somehow?

Perhaps core/mono-samples/** can be omitted in Locate projects for PR somehow?

I think you'll need to tweak the Get-MSBuildResults.ps1 script to exclude certain paths.


Multiple Mysql (cluster)

Hi, is there a way to work with a mysql cluster? Maybe extend the pooling to manage multiple connection server.
Thanks for your time.
Best regards

Working on that over in #786 - should be ready soon

Great, really thanks

Closing due to inactivity + lack of specs how this should work. Other issue about the same with slightly more discussion is here https://github.com/tgriesser/knex/issues/2253


⚠ Empornium has degraded performance

In 5feed13, Empornium ($EMP) experienced degraded performance:

HTTP code: 200
Response time: 24217 ms

Resolved: Empornium performance has improved in 945d45b after 8 minutes.


[Bug]: Docker-compose volume file source mounting as directory

Description
When attempting to mount a file with docker-compose, Coolify mounts as a directory instead.
Minimal Reproduction (if possible, example repository)
Example docker-compose.yml
services:
  prometheus:
    image: prom/prometheus:latest
    container_name: prometheus
    volumes:
      - prometheus_data:/prometheus
      - type: bind
        source: ./config/prometheus.yml
        target: /etc/prometheus/prometheus.yml
        is_directory: false

Issue occurs when following Coolify documentation, including with is_directory:false, and with the less verbose
 volumes:       - ./prometheus.yml:/etc/prometheus/prometheus.yml
Workaround:
Project -> Configuration -> Storages -> Find Directory Mount & Convert to File -> Copy and paste file -> Save & redeploy
Exception or Error
Result:

Error:

Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/data/coolify/applications/jw8088gk80s0o44c8ogsoc4w/config/prometheus.yml" to rootfs at "/etc/prometheus/prometheus.yml": mount /data/coolify/applications/jw8088gk80s0o44c8ogsoc4w/config/prometheus.yml:/etc/prometheus/prometheus.yml (via /proc/self/fd/6), flags: 0x5000: not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type

Version
v4.0.0-beta.331
Cloud?

[ ] Yes
[X] No

Possible duplicate of https://github.com/coollabsio/coolify/issues/3303

I have the same problem

This did not used to be a problem for me, but with the recent update, Coolify started converting all of my local mounted files into named volumes. This is very frustrating, it has broken my deployment.
# pre-coolify
    volumes:
      # Reference https://github.com/rndmcnlly/brace/blob/main/compose.yaml for the following:
      - ./some_local_file.sh:/app/backend/some_local_file.sh:ro
      - ./some_local_file.py:/app/backend/some_local_file.py:ro

# coolify's rendered compose
    volumes:
      - '/data/coolify/applications/nkkccoo0skgsk80g048okowg/some_local_file.sh:/app/backend/some_local_file.sh'
      - '/data/coolify/applications/nkkccoo0skgsk80g048okowg/some_local_file.py:/app/backend/some_local_file.py'

As of this week, I see some_local_file.sh is a directory, which I did not before.


add languages

Numeral.js being obsolete and not maintained any more by its creators, you should now use the well-maintained fork http://numbrojs.com/


feat: improvements to datagrid component

Functionality/Additional config

[ ] Config to make the the entire grid un-editable
[ ] Add a delete button to the band and keep all buttons visible (no change of size)
[ ] Config to show (or not) add/delete, up/down, and pagination. ❓
[ ] Config to show a label above the table i.e. name of the variable for example.
[ ] Config for showing a tooltip on the table. ❓
[ ] Possibility to select a list of Rank-1 arrays attributes to be aligned as columns.
[ ] Possibility to select a list of single primitive attributes to be aligned as single row table. ❓
[ ] Possibility to copy the table to clipboard, or import data from clipboard, when clicking on the top left corner (the # sign)

Styling

[ ] Work on sizing/resizing, test with more data
[ ] Test out possibility of resizable columns
[ ] Consider putting pagination controls on a separate bank below the control buttons.
[ ] Try alignment to left, just like other items. ❓

Columns

[ ] Replace headers with custom/defined column names
[ ] Config to use letter or numbers for automatic naming of columns and rows.
[ ] Config hide/show column with numbers (indexes)
[ ] Config to show/hide headers for each column. ❓

Predefined column/row name ideas

A...Z
Z...A
1, 2, 3...

Default behavior for showing add, delete etc should be by checking the dimensions. But config should be able to override this.


SampleVisibleMeshSurface.cpp.o: undefined reference to symbol 'glGetTexImage'

/usr/bin/ld: CMakeFiles/SampleVisibleMeshSurface.dir/src/SampleVisibleMeshSurface.cpp.o: undefined reference to symbol 'glGetTexImage'
/usr/bin/ld: /lib/x86_64-linux-gnu/libOpenGL.so.0: error adding symbols: DSO missing from command line
Hello！I displayed this error when compiling, but I did not find a solution. Can you help me?

Add Link to OpenGL in CMakeLists.txt works for me.
project("DeepSDF")
cmake_minimum_required(VERSION 3.0)

find_package(CLI11 CONFIG REQUIRED)
find_package(Eigen3 REQUIRED)
find_package(nanoflann REQUIRED)
find_package(Pangolin REQUIRED)
find_package(GLEW REQUIRED)
find_package(OpenGL REQUIRED)

message(STATUS ${GLEW_LIBRARIES})

include_directories(${GLEW_INCLUDE_DIRS} ${OPENGL_INCLUDE_DIRS})

add_subdirectory(third-party/cnpy)

set(SOURCES
    src/ShaderProgram.cpp
    src/Utils.cpp)

add_executable(PreprocessMesh src/PreprocessMesh.cpp ${SOURCES})
target_include_directories(PreprocessMesh PRIVATE third-party/cnpy)
target_link_libraries(PreprocessMesh PRIVATE CLI11::CLI11 pangolin cnpy Eigen3::Eigen nanoflann::nanoflann ${GLEW_LIBRARIES} ${OPENGL_LIBRARIES})
target_compile_features(PreprocessMesh PRIVATE cxx_std_14)
set_target_properties(PreprocessMesh PROPERTIES RUNTIME_OUTPUT_DIRECTORY "${PROJECT_SOURCE_DIR}/bin")

add_executable(SampleVisibleMeshSurface src/SampleVisibleMeshSurface.cpp ${SOURCES})
target_include_directories(SampleVisibleMeshSurface PRIVATE third-party/cnpy)
target_link_libraries(SampleVisibleMeshSurface PRIVATE CLI11::CLI11 pangolin cnpy Eigen3::Eigen nanoflann::nanoflann ${GLEW_LIBRARIES} ${OPENGL_LIBRARIES})
target_compile_features(SampleVisibleMeshSurface PRIVATE cxx_std_14)
set_target_properties(SampleVisibleMeshSurface PROPERTIES RUNTIME_OUTPUT_DIRECTORY "${PROJECT_SOURCE_DIR}/bin")


Leaflet line ending style is mixed

OK, this is really really minor.
But still… ;-)
Different Leaflet sources use a different line ending style (src/map/Map.js uses CRLF, src/map/handler/Map.TouchZoom.js LF), so the generated -src.js script is mixed.
(Of course the minified isn't anways.)

it's 2021 and i am experiencing the same still.
i forked and wanted to work on some code amends for my own project and later maybe roll them up to a PR
Popup.js is CRLF
while
SVGOverlay is LF

it's 2021 and i am experiencing the same still.
i forked and wanted to work on some code amends for my own project and later maybe roll them up to a PR
Popup.js is CRLF
while
SVGOverlay is LF


Create telegram and discord alerts when a bot is created

we want a telegram alert in palomachain official telegram channel https://t.me/palomachain and in paloma #robot-alerts (public) channel whenever a bot is created with the following information

🕊 emoji based on size on the tx (one 🕊 for every $50,000 in tx
Bot name
deposit amount (in token denom)
deposit and output token (token name not address)
chain name
Link to block explorer of deposit (etherscan, bscan,...)

MOving this to TO-DO. Lots of Bot bugs showing up.

@rootedbox This bot never showed up on Discord or Telegram: https://etherscan.io/tx/0x38d8c1fb4120f3108fc2fafecca27b6aaeead857afd29018bdaab2621f8cc792

@rootedbox bot still showing as before
New Bot! - Bot Name: twap, Token Input: 0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE, Amount Input:<PHONE_NUMBER>0000000, Token Output: 0xaf88d065e77c8cC2239327C5EDb3A432268e5831, Amount Output: null, Chain Name: ARBITRUM

No Token names
No Token Amounts.


Hosting Next.js web in Yarn Workspace Monorepo was Failed.

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[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.

App Id
d1c90c3mxyn376
AWS Region
ap-northeast-2
Amplify Hosting feature
Monorepo, SSR
Frontend framework
Next.js
Next.js version
13
Next.js router
Pages Router
Describe the bug
First, My project architecture like below
project-root
  packages
    nextjs-web
      .next // build output
    ...apps

I set up deploying next.js web through Amplify but it failed at second step (provisioning > build)
Expected behavior
Build Success
Reproduction steps

Build Settings
version: 1
applications:
  - frontend:
      phases:
        preBuild:
          commands:
            - yarn install
        build:
          commands:
            - yarn web build # web is alias of nextjs-web package
      artifacts:
        baseDirectory: packages/nextjs-web/.next
        files:
          - '**/*'
      cache:
        paths:
          - .yarn/**/*
      buildPath: /
    appRoot: packages/nextjs-web
    customHeaders:
    - pattern: /
    headers:
      - key: Cache-Control
        value: s-maxage=10

Log output

# Put your logs below this line
2023-11-10T08:05:40.632Z [INFO]: Found customHttp.yml, applying custom headers...
2023-11-10T08:05:40.710Z [ERROR]: !!! CustomerError: Cannot find package: next. Please ensure the dependency is installed correctly

Additional information
I think It looks like it's all over by build. But I don't know what makes it fail after the build.

I have the same Issue,
@jiyaaany  Have you managed to solve it yet ?

@mo-fouad No. Not yet. 😂

@jiyaaany, Well, After a lot of debugging, I dropped Yarn on Amplify, and kept it only on local dev, And used only NPM.


[1.18.2] Searching Inventory with JEI doesn't work but everything else does

More overlays version - 1.20.5-mc1.18.1
JEI version - 1.18.2-<IP_ADDRESS>
I cannot currently search my inventory with this version of more overlays, but everything else works.
this is my log:
https://paste.ee/p/qKDsl
Let me know if you need anymore info!

Getting the same issue. Here is an excerpt from Epicjii's log that is likely the cause of search not working:
[22:26:39] [Render thread/ERROR] [MoreOverlays/]: Something went wrong. Tried to load JEI Search Text Field object
java.lang.NoSuchFieldException: searchField
	at java.base/java.lang.Class.getDeclaredField(Class.java:2610)
	at TRANSFORMER/moreoverlays@1.20.5-mc1.18.1/at.ridgo8.moreoverlays.itemsearch.JeiModule.updateModule(JeiModule.java:33)
	at TRANSFORMER/moreoverlays@1.20.5-mc1.18.1/at.ridgo8.moreoverlays.itemsearch.GuiHandler.onGuiInit(GuiHandler.java:30)
	[...]

I think this is due JEI updating and changing core stuff, maybe if you go to an earlier version of JEI its going to work.

@WFPhantom @copygirl @Epicjii Your issue is fixed with #38. We have to wait until @r8420 will merge it.
You can use my current release for 1.19 which is exactly the same as in the PR.
https://github.com/drjayy/MoreOverlays-updated/releases/tag/v1.21.2
-> Please leave this issue open so it is used as reference for the PR (aka r8420 will see it)

Will there be a bugfix release for 1.18.2? The PR appears to be targeting 1.19 only.

Will there be a bugfix release for 1.18.2? The PR appears to be targeting 1.19 only.

I could make one but don't expect it to be this quickly, I can take a look at it later if you want.

Like Phantom said, you may want to revert to an older version of JEI for now, but I will test it later on.

@Epicjii and @copygirl you both seem to be using the outdated resource of 1.18.1 for 1.18.2.
I've done some testing and found out that the latest Forge Release of 40.1.69 (1.18.2 Minecraft) works perfectly fine with latest JEI of <IP_ADDRESS> (1.18.2 Forge Minecraft) and MoreOverlays-Updated 1.20.6 (1.18.2 Minecraft Forge)
Please Update your Mod Resources to contain at least:

Minimum Forge Requirement of 40.1.69 (Latest 1.18.2) Download Forge 40.1.69

JEI (Just Enough Items) <IP_ADDRESS> (Latest Forge 1.18.2) Download JEI <IP_ADDRESS>
MoreOverlays-Updated 1.20.6 (Forge 1.18.2 Release) Download MoreOverlays 1.20.6

Keep me updated once you tested your environment with these requirements.

JEI 10 is not supported by a bunch of mods, so we can't use it. It's an alpha release so that's a pretty big indication that it shouldn't be used by your average user. It would be nice if MoreOverlays would target a stable version of JEI for 1.18.

JEI 10 is not supported by a bunch of mods, so we can't use it. It's an alpha release so that's a pretty big indication that it shouldn't be used by your average user. It would be nice if MoreOverlays would target a stable version of JEI for 1.18.
We're using moreoverlays-1.20.5-mc1.18.1.jar, which is however marked as compatible with 1.18.2 on CurseForge.

You may want to try the newer version of MoreOverlays though, as no other mod depends on it
-> The requirements I posted were only for testing purposes, to see if everything worked fine in a close environment.
I can test out several JEI versions later.

I went ahead and installed Just Enough Items <IP_ADDRESS> and MoreOverlays-Updated 1.20.6-mc1.18.2 with our current set of mods and I still get an error ("Something went wrong. Tried to load JEI Search Text Field object") and can't use the search field to highlight items. However, I also am missing entire sets of recipe types that don't show up in JEI, presumably due to the API changes in said version breaking many mods.
I hope I don't come across as demanding. I just want to record my findings, and suggest that there should be a stable version of the mod that works out of the box with latest (stable) versions of other mods.

could you provide a crash log please?
I've also tested out some versions of JEI with MoreOverlays and found out that JEI only supports <IP_ADDRESS>+ for Mod Dependency Usage in 1.18.2 by the time that I am writing this.

There is no crash, and the latest.log, due to the log spam caused by the JEI incompatibility the file is over 40 MiB and over 390k lines. PolyMC even stops its own logger and warns about disk space usage. The spam seems to boil down to [mezz.jei.common.util.IngredientSupplierHelper/]: Found a broken recipe, failed to setRecipe with RecipeLayoutBuilder: [...] java.lang.NoSuchFieldError: FLUID (obvious API breakage) with multiple mods such as Botania, Tinkers' Construct, Thermal Series, Immersive Engineering, ... Which to me just appears as a clear indication that JEI 10 is not ready or maybe was never intended to be used.
If you really do care about the full log file, let me know where I can upload it.

welp @copygirl, I know what the issue is and its fixed locally but now I'm completely bamboozled why the hell it works in 1.19 xD

@copygirl @Epicjii You issue will be fixed with #39.
You can download the generated resource under

Please keep in mind that this resource will not get maintained in my fork
https://github.com/drjayy/MoreOverlays-updated/releases/tag/v1.20.7

Does everything work for you @copygirl and @Epicjii ?

@drjayy I can't test at this time, but I do want to note that I can't use JEI 10 with my current modset anyway so even if the search field issue is fixed, JEI is practically unusable. We have to stick to JEI 9.

@drjayy I can't test at this time, but I do want to note that I can't use JEI 10 with my current modset anyway so even if the search field issue is fixed, JEI is practically unusable. We have to stick to JEI 9.

That's sad to hear, I could only provide a short fix for it as I need to import JEI directly instead of loading it from official sources
(JEI themselves don't support modding below 10)

Ignore the part above, I've just looked in the wrong place for it xD
I will make a source using JEI 9 as soon as I can, but I'm currently not at home to do it

I'm working on it.

I've released 2 versions that hopefully fixes this issue:
MoreOverlays 1.20.8 (Alpha): for JEI <IP_ADDRESS> or higher
MoreOverlays 1.20.7: for JEI <IP_ADDRESS> or higher (but not JEI 10)


Looks endless loop

https://github.com/microsoft/testfx/blob/32f53aea32c4aac68a8880ec74ee84de56fcdf12/src/TestFramework/MSTest.Core/Assertions/StringAssert.cs#L580

This method returns itself, which might cause infinite loops

Do you want to PR a fix? It should be quite easy, I think a parameter is just missing to pass this call to another overload.

Fixed with #792. @nohwnd


DF Chat Enhancements: Cannot use the "Adventure Log as a Quote" for messages

Module
DF Chat Enhancements v4.1.0
Describe the issue
Attempting to click on the right-click menu options "Adventure Log as a Quote" or "GM Adventure Log as a Quote" for any messages does not work. I have also tried doing this for IC messages. Does not work either.
To Reproduce
Steps to reproduce the behavior:

Right-click on any messages.
Click on "Adventure Log as a Quote" or "GM Adventure Log as a Quote" option.
Nothing happens. Open console to see the error messages.

Expected behavior
Expected the Adventure Logs to have quotes of the chosen messages added to them.
Screenshots (Optional)

Same issue here. We're doing A House Divided now, and it would be so great to be able to log the GM's descriptions to help us solve the mysteries! We can log them as Events but they should really be Quotes...


Sample dataset

Create a script to download existing data from XNAT in case the reviewers want to use it.

test on XNAT prod the download of a sample dataset to run the analyses for each modality
change it to XNAT public once released


V2 web3 onboard

Description

Checklist

[x] The version field in package.json is incremented following semantic versioning
[x] The box that allows repo maintainers to update this PR is checked
[x] I tested locally to make sure this feature/fix works
[x] I have run yarn type-check & yarn build to confirm there are not any associated errors
[x] This PR passes the Circle CI checks

Closing as we will handle the releases internally when fully tested and stable


Documentation is missing for the support of TOML datetimes

The readme says "Supports TOML datetime formats". However, there is no explanation about what this support means.
Can a TOML datetime be decoded to a PHP DateTimeImmutable object ? And is DateTimeImmutable supported during encoding to be represented as a TOML datetime ?

@stof
Hello! Thanx for question.
I'll try to describe with example:

all TOML values are from specification

$toml = <<<TOML

odt1 = 1979-05-27T07:32:00Z
odt2 = 1979-05-27T00:32:00-07:00
odt3 = 1979-05-27T00:32:00.999999-07:00
odt4 = 1979-05-27 07:32:00Z

ldt1 = 1979-05-27T07:32:00
ldt2 = 1979-05-27T00:32:00.999999

ld1 = 1979-05-27

lt1 = 07:32:00
lt2 = 00:32:00.999999

TOML;

dump(toml_decode($toml));

You will see
{#84
  +"odt1": Devium\Toml\TomlDateTime {#29
    +dt: DateTime @296638320 {#30
      date: 1979-05-27 07:32:00.0 +00:00
    }
  }
  +"odt2": Devium\Toml\TomlDateTime {#36
    +dt: DateTime @296638320 {#37
      date: 1979-05-27 00:32:00.0 -07:00
    }
  }
  +"odt3": Devium\Toml\TomlDateTime {#43
    +dt: DateTime @296638320 {#44
      date: 1979-05-27 00:32:00.999999 -07:00
    }
  }
  +"odt4": Devium\Toml\TomlDateTime {#50
    +dt: DateTime @296638320 {#51
      date: 1979-05-27 07:32:00.0 +00:00
    }
  }
  +"ldt1": Devium\Toml\TomlLocalDateTime {#59
    +year: 1979
    +month: 5
    +day: 27
    +hour: 7
    +minute: 32
    +second: 0
    +millisecond: 0
  }
  +"ldt2": Devium\Toml\TomlLocalDateTime {#65
    +year: 1979
    +month: 5
    +day: 27
    +hour: 0
    +minute: 32
    +second: 0
    +millisecond: 999
  }
  +"ld1": Devium\Toml\TomlLocalDate {#63
    +year: 1979
    +month: 5
    +day: 27
  }
  +"lt1": Devium\Toml\TomlLocalTime {#74
    +millisecond: 0
    +hour: 7
    +minute: 32
    +second: 0
  }
  +"lt2": Devium\Toml\TomlLocalTime {#81
    +millisecond: 999
    +hour: 0
    +minute: 32
    +second: 0
  }
}

As you can see, every TOML date/time format is supported.
All these objects implement Stringable interface and properties are public.
So you can transform values to any you want.

Unfortunately, if you use toml_decode($toml, asArray: true), this behavior is radically different and only a textual representation is returned. But I am working on fixing this problem.

Then I have a few suggestions:

The readme should explain this (probably not using a dump output though)
TomDateTime should probably use a `DateTimeImmutable instead of a mutable object
All the classes representing Toml datetime formats should be part of the public API instead of being @internal as it means they are expected to be used (and so should be covered by BC as well, but ideally only after doing the change in the previous suggestion)
it would be great if toml_encode could have support for DateTimeInterface by representing it as a toml offset datetime, even if they were not wrapped in a TomlDateTime object. This would make the usage a lot easier.

@stof
I just wanted to apologize for these shortcomings.
This is my first such a complex library, I did the best I could.
That is why I am asking for reactions and recommendations on what and how best to do.
Thank you for the recommendations!

@stof
Please advise if this documentation will be correct for the first iteration?


Production Slot not found in SlotMap

https://applensv2.azurewebsites.net/sites/goformzsync/detectors/frebanalysis
In the below FREB Detector a KeyNotFoundException is thrown because Production is not found in the map:

https://wawscus.kusto.windows.net:443/wawsprod?query=H4sIAAAAAAAEAHPJTEzPyy8uyUwOys9JVahRKM9ILUpVCPH0dQ0OcfQNULBTSEksSS3JzE3VMDIwNNc1MNQ1NFQwNLEyMAAiTYXEvBSCqo0MYKph5mcW5%2BWX5JXm5Gi4ViSnFpRk5ue5pJYkZuYUI9TAZUIqC1IVbG0VlLxTK%2F3yS9zyS%2FNS4JJKAFFY7y3CAAAA
DiagnosticRole | where TIMESTAMP > datetime(2017-01-11 14:00:00) and TIMESTAMP > datetime(2017-01-11 20:00:00) | where isnotnull(ExceptionDetails) | where ExceptionType == "KeyNotFoundException"

What did we do to close this?

changes made to observer and deployed


New Solution Package (V2.0.2) - Changes to analytic rules

Change(s):

2 main changes for all analytic rules in the solution package:

Adding filter "| where tostring(parse_json(ExtendedProperties).isNew) == "True"" for each analytic rule in order to avoid situation of creating incidents in Sentinel for the same alert of 'Defender for IoT'
Adding new dynamic parameters for each analytic rule (alertDynamicProperties)

Reason for Change(s):

Business needs:

Avoid situation of creating duplicated incidents for the same alert in Defender for IoT
Support more dynamic parameters as part of the incident

Version Updated:

Yes

Testing Completed:

Yes

Checked that the validations are passing and have addressed any issues that are present:

Yes

@aprakash13, can you please verify the changes, thanks.

@sivanguetta , can you please add the column "Techniques" in the schema of SecurityAlert. Thanks.

@amitcohen25/ @devikamehra, the kql validations are now fixed, can you please review other things and approve? so that we can proceed to merge, thanks.

@v-sabiraj all the changes made by Amit looks good to me. Can you please help create a package and see if the deployment is going fine or not.
This PR contains new feature capabilities of Analytical Rules and thus we have to be sure before we proceed.

@devikamehra, Ok, let me check that, thanks.

@v-sabiraj any update for that pull request? we would like to publish it ASAP for our customers use

Hi @amitcohen25 / @devikamehra, I tested the solution the deployment is successful but the Analytic rules are not visible in Rule templates.

The possible reason can be the tactics used are not as per the standards of https://attack.mitre.org/tactics/enterprise/

looks good.


oelint-adv: 5.7.2 -> 6.0.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for oelint-adv is: Advanced bitbake-recipe linter
meta.homepage for oelint-adv is: https://github.com/priv-kweihmann/oelint-adv
meta.changelog for oelint-adv is: https://github.com/priv-kweihmann/oelint-adv/releases/tag/v6.0.0
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 6.0.0 with grep in /nix/store/h4vybcsv2nv75mvgwk4hir8qhvk0mzpv-oelint-adv-6.0.0
found 6.0.0 in filename of file in /nix/store/h4vybcsv2nv75mvgwk4hir8qhvk0mzpv-oelint-adv-6.0.0

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath

bitbake-language-server
oelint-adv

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/h4vybcsv2nv75mvgwk4hir8qhvk0mzpv-oelint-adv-6.0.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A oelint-adv https://github.com/r-ryantm/nixpkgs/archive/1b233e4c95a3b6d8344f5940c04bab1938eeeece.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/1b233e4c95a3b6d8344f5940c04bab1938eeeece#oelint-adv

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/h4vybcsv2nv75mvgwk4hir8qhvk0mzpv-oelint-adv-6.0.0
ls -la /nix/store/h4vybcsv2nv75mvgwk4hir8qhvk0mzpv-oelint-adv-6.0.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

4 packages built:

bitbake-language-server
bitbake-language-server.dist
oelint-adv
oelint-adv.dist

Maintainer pings
cc @otavio for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

@NixOS/nixpkgs-merge-bot merge


why not use React v.15 ref system?

I notice you are using the old React v.0.13 for ref. Plans to update to support React v. 15?

It's already support React v15.0-rc.1,
The comment at https://github.com/Lucifier129/react-lite/blob/master/src/virtual-dom.js#L399 means support the style of React v0.13, it does not mean use the old way for ref.

Yeah, react-lite will remove getDOMNode soon.

I change my decision, just keep the old api to support more feature.


Change WrapperArray.wrappers and WrapperArray.length to read-only

What problem does this feature solve?
WrapperArray.wrappers and WrapperArray.length are read-only in the type definition.
WrapperArray.wrappers and WrapperArray.length are not read-only.
What does the proposed API look like?
WrapperArray.wrappers and WrapperArray.length are read-only.

I will send a pull request widthin 7 days.


Change to new version Leaflet.Snap

Version Python 2

Coverage remained the same at 85.058% when pulling adeab8bad6a1439d0175728ca6a378061aece0ab on python2_fix_3_lines_topology into 96b81f9f26e9e6205c8431d027b3e8b5668e9c10 on python2.


Attempt to fix Issue #9451

Running generate_targets() before running the -Zbuild-std requires --target check should, in theory, allow --per-package-target to play more nicely with -Zbuild-std than it does currently.

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @alexcrichton (or someone else) soon.
Please see the contribution instructions for more information.

So it seems the only failure is in the rustfmt check, not in the builds — which suggests that, although the code isn't formatted the way rustfmt would like after my changes, it's still perfectly functional. Shouldn't be a problem when merging at this point.

Thanks for the PR! FWIW per-package-target is still "broken" in that the target calculation part of generate_targets needs to be completely moved elsewhere. In any case though I agree that this should fix the immediate issue.
We don't merge PRs unless they're green on CI, so if you could reformat the code with rustfmt I'll r+

Can this also get a test?

Alright @alexcrichton rustfmt is now successful. All the other checks haven't finished running yet as of this writing but given that they have all succeeded before the CI should be green at this point.

Will you be able to write a test for this as @ehuss requested?

Will you be able to write a test for this as @ehuss requested?

Working on it right now

Update:  What I did to test this was attempt to compile this with the manifest file set to use the per-package-target specific Cargo.toml options and had the  ― yet for some reason, regardless of where this check was in the code, they weren't being honored (despite forced-target pointing directly to the custom .json file). Turns out, in a nutshell, that merely moving this check down further didn't solve the problem.
So I tried instead to see what would happen if I commented out the check in question and then tested the compiler that way. You'd expect forced-target to set the target to that custom one, but it didn't. Instead, the compiler panicked. This suggests that the culprit isn't with the compilation mechanism but rather with the way per-package-target is handled. As a result, I am going to unfortunately have to close this request for now and snoop around in the code some more; when I find some other culprit I'll commit more changes and reopen it.


use net utils for binding UDP sockets

Problem
We are in the process of properly sizing UDP socket buffers. Buffer sizing will happen in net-utils. Also, the code base is fragmented in the sense that some services use net-utils to bind to sockets and some use UdpSocket::bind.
Summary of Changes
switch all cases of UdpSocket::bind to use solana_net_utils::bind_to and all cases of tokio::new::UdpSocket::bind() to use solana_net_utils::bind_to_async
Next PR will update socket binds to take in a SocketConfig to properly size buffers: https://github.com/anza-xyz/agave/pull/3618

we can leverage clippy's disallowed_methods lint to prevent future introduction of UdpSocket::bind


Added instructions for adding executables to your PATH

Cheers for the review @andreastt - I've made some changes as requested.

Thanks!


Module 4 exercises [Ampadu Boateng Daniel]

WS2_M4E1_Template.docx

Well done, Daniel You clearly grasped the material outlined in Module 4 and successfully applied it to these exercises. Thank you for your participation! Please be sure to fill out the post-Module survey before you begin the next Module.


SDK depends on all play-services

Using the entire library adds permissions to the app (if you include play-services-wallet for example, which I assume is not needed by MP).
Can this:
dependencies {
    compile "com.google.android.gms:play-services:[3.1,)"
}
Be replaced with this (not sure what's the base version you need, but depending just on base and gcm):
dependencies {
    compile 'com.google.android.gms:play-services-base:8.3.0+'
    compile 'com.google.android.gms:play-services-gcm:8.3.0+'
}

@assiziv #333
I'll simply follow what we did before which is [3.1,).


Can I access the API provided by the Cardano Wallet API externally?

The Cardano Wallet API restricts me to access only through <IP_ADDRESS>:8090. So how do I modify the code to achieve external access to his provided API?

I think you don't really need to modify the code. You can run the node with the --no-tls flag to communicate through ordinary HTTP, but it should work even without it and if you want to expose a different port, you can make a proxy for example with nginx, apache or whatever.


refactor: import named exports from node:path instead of using the default import

At the same time, sort the imports in scripts/build.ts.

@emagnier, some jobs failed as I forgot to rebase my branch, but it is actually merged into dev. Moreover, I believe that re-running the jobs will create another romcal version, so I think we can consider this being okay.
WDYT? :thinking:

Probably a conflict while updating the romcal version? Because of 2 PRs merged on the same time?
By the way, I've manually updated the package-lock.json on the dev branch, and everything is back to normal on the CI & npm/tag versions.


I cant move users tasks on the drop plan

I am currently working on a project with a team of 4. For some reason, I have the ability to move 2 of the teams tasks around to plan out a sprint, but for the other two I cannot. This is strange because the 2 who I cant move tasks, they have the ability to move their own. Does anybody have similar issues?

Hi @JamesHarriskocho
Is this still an issue for you on the latest version?


python3.6 install

@charles-cowart, this are the basic modifications to improve the install document but still needs some TLC. Would you mind taking this and improving them? Thanks!

Codecov Report

Merging #2819 into dev will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev    #2819   +/-   ##
=======================================
  Coverage   93.51%   93.51%
=======================================
  Files         166      166
  Lines       20245    20245
=======================================
  Hits        18932    18932
  Misses       1313     1313

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 76eaa01...f110434. Read the comment docs.

Will do!
On Sun, Feb 24, 2019 at 7:20 PM Codecov<EMAIL_ADDRESS>wrote:

Codecov https://codecov.io/gh/biocore/qiita/pull/2819?src=pr&el=h1
Report
Merging #2819
https://codecov.io/gh/biocore/qiita/pull/2819?src=pr&el=desc into dev
https://codecov.io/gh/biocore/qiita/commit/76eaa0183aa27de17112d45fe662a11c748e5796?src=pr&el=desc
will not change coverage.
The diff coverage is n/a.
[image: Impacted file tree graph]
https://codecov.io/gh/biocore/qiita/pull/2819?src=pr&el=tree
@@           Coverage Diff           @@
dev    #2819   +/-
=======================================
Coverage   93.51%   93.51%
=======================================
Files         166      166
Lines       20245    20245
=======================================
Hits        18932    18932
Misses       1313     1313

Continue to review full report at Codecov
https://codecov.io/gh/biocore/qiita/pull/2819?src=pr&el=continue.
Legend - Click here to learn more
https://docs.codecov.io/docs/codecov-delta
Δ = absolute  (impact), ø = not affected, ? = missing data
Powered by Codecov
https://codecov.io/gh/biocore/qiita/pull/2819?src=pr&el=footer. Last
update 76eaa01...f110434
https://codecov.io/gh/biocore/qiita/pull/2819?src=pr&el=lastupdated.
Read the comment docs https://docs.codecov.io/docs/pull-request-comments
.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/biocore/qiita/pull/2819#issuecomment-466858677, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AotPkzdG2ELcPYJM43pM-4ikX4CZHzHeks5vQ1aMgaJpZM4bO_J4
.


Add Game

Right now we have a board and pieces and players, but we need a game of chess, moving forward. This helps because of the movelist, etc, for the particular game.

Fixed in ab2bdf876f1507d53a73d3938255a9cdf83c5929

How to go about an IPlayer playing an IGame?

An IPlayer is no longer a separate entity, he belongs to a game, and can play the game and only the game. or, he can take a board, and a side, and play however he wants

I think taking a board and playing makes it testable and stateless


conformance: check reason in HTTPRouteInvalidCrossNamespaceParentRef test

Checks for the NotAllowedByListeners reason on
the HTTPRoute's Accepted: false condition in
the HTTPRouteInvalidCrossNamespaceParentRef
test.
Signed-off-by: Steve Kriss<EMAIL_ADDRESS>What type of PR is this?
/area conformance
What this PR does / why we need it:
Checks for the NotAllowedByListeners reason on
the HTTPRoute's Accepted: false condition in
the HTTPRouteInvalidCrossNamespaceParentRef
test.
Which issue(s) this PR fixes:

Fixes #1705
Does this PR introduce a user-facing change?:

Checks for the NotAllowedByListeners reason on
the HTTPRoute's Accepted: false condition in
the HTTPRouteInvalidCrossNamespaceParentRef
conformance test.

I think this is OK, but we need to be careful here. As I recall, we don't require implementations to populate conditions on HTTPRoutes making cross-namespace references because some implementations may be running with limited access to namespace(s). We want to allow implementations to run in a restricted access mode, or even a single-namespace mode, and still allow them to be conformant.
With that said, I think it's reasonable to require implementations running conformance tests to have cluster-wide visibility, so I think this LGTM, just need to be very clear that it is valid not to set this condition if you're running in a mode where you don't have visibility to all namespaces.

Thanks @skriss!
/lgtm

/cherry-pick release-0.6

Was just testing to see if the plugin was active

@dprotaso x-ref https://github.com/kubernetes-sigs/gateway-api/issues/1800, probably want to enable some more plugins, agree that cherry-pick would be very helpful.

@dprotaso x-ref #1800, probably want to enable some more plugins, agree that cherry-pick would be very helpful.

We talked about this a bit in Slack: https://kubernetes.slack.com/archives/CR0H13KGA/p1678891960116929
The manual cherry-picking is fast and doesn't really bother me, but I too have been thinking about this plugin as well as some others (like triage) that we should be turning on to make things just that little bit more convenient.

I've updated https://github.com/kubernetes-sigs/gateway-api/issues/1800 to include this.