PowerDNS running as privileged user if config file is wrong

As this module isn't setting setuid and setgid to an unprivileged user, PowerDNS is running as root if those options are not set (tested on Ubuntu).
Either add a message to the README of this behavior or set setuid and setgid by default.

You're on a roll. Thanks for bringing this up.
Is this with the official packages released by PowerDNS? I'm not familiar with the build system of PowerDNS, but they do change it on CentOS and Debian Buster.
I think we should 100% warn users if this is the default behaviour for some operating systems. At the same time, if it is an official package from PowerDNS, I would probably go for a PR or bug report on their end. I wouldn't change the default because it might interfere with the package PowerDNS provides.

You're on a roll. Thanks for bringing this up.
Is this with the official packages released by PowerDNS? I'm not familiar with the build system of PowerDNS, but they do change it on CentOS and Debian Buster.
I think we should 100% warn users if this is the default behaviour for some operating systems. At the same time, if it is an official package from PowerDNS, I would probably go for a PR or bug report on their end. I wouldn't change the default because it might interfere with the package PowerDNS provides.

It all depends on the configuration you got on your system.
This module isn't changing existing values, but if you're - for example - migrate from something else, you might start with a non-package default config version. If this version is lacking the proper values, it's running as root.
My original finding is based on that. Starting with a clean version from a package is working as expected, but some users might still "break" the config and then it's running as root.
I'd def. go with platform specific defaults here to avoid this behavior.
Yes, this will be a breaking change, but one, which should be done.
The way how this module is managing the powerdns configuration is quite nice, but has the implication, that there are unmanaged lines within the file, which might also break during upgrades: if a valid setting gets removed, PowerDNS might complain about it and won't start, although the user is unaware of such a setting.
It even gets more complicated, as package upgrades won't replace the configuration, as there are changes in the config file.
For now, I don't have a solution for this, sadly.

It all depends on the configuration you got on your system.
This module isn't changing existing values, but if you're - for example - migrate from something else, you might start with a non-package default config version. If this version is lacking the proper values, it's running as root.
My original finding is based on that. Starting with a clean version from a package is working as expected, but some users might still "break" the config and then it's running as root.
I'd def. go with platform specific defaults here to avoid this behavior.
Yes, this will be a breaking change, but one, which should be done.
The way how this module is managing the powerdns configuration is quite nice, but has the implication, that there are unmanaged lines within the file, which might also break during upgrades: if a valid setting gets removed, PowerDNS might complain about it and won't start, although the user is unaware of such a setting.
It even gets more complicated, as package upgrades won't replace the configuration, as there are changes in the config file.
For now, I don't have a solution for this, sadly.

As my assumption was wrong, I've changed the title.

As my assumption was wrong, I've changed the title.

but has the implication, that there are unmanaged lines within the file, which might also break during upgrades

It does. It even means if a setting is invalid, it will still be added as there is no way to verify it right now (I think). If there is a way to verify it automatically, I would love to include it.

Yes, this will be a breaking change, but one, which should be done.

I thought about it and think you're right. As long as we make sure we don't break the installation of PowerDNS and stick to the defaults they use themselves, I'm up for changing it. This way it shouldn't interfere if you didn't change it. I'd also like to make this an optional feature though as there might be reasons I really can't think of right now to run it as root.

but has the implication, that there are unmanaged lines within the file, which might also break during upgrades

It does. It even means if a setting is invalid, it will still be added as there is no way to verify it right now (I think). If there is a way to verify it automatically, I would love to include it.

Yes, this will be a breaking change, but one, which should be done.

I thought about it and think you're right. As long as we make sure we don't break the installation of PowerDNS and stick to the defaults they use themselves, I'm up for changing it. This way it shouldn't interfere if you didn't change it. I'd also like to make this an optional feature though as there might be reasons I really can't think of right now to run it as root.

I've removed the tested on Ubuntu part too, because this could happen on any system.

I've removed the tested on Ubuntu part too, because this could happen on any system.


Why two micrometer starters?

I'm curious what's the difference between azure-spring-boot-metrics-starter and applicationinsights-spring-boot-starter? Why two starters? Should I use both? When should I use each?
Thanks

@dhaval24
Could you please help to answer the question ?

@mercer yes you should use both. application insights springboot starter, helps you capture request, logs, dependencies (external calls like http, mysql) if used with Application Insights Java agent.
Azure-metrics-springboot-starter helps you get all the java metrics that micrometer provides.
We took this design to provide modularity and flexibility for users.

Closing this for now. Please reopen if you still have questions.


Fix support for openssl async engine

Maciej Oleksy tried to use the openssl async engine support provided in ATS and noticed it was broken.  There were a few issues, but the main issue was due to changes in casting and class hierarchy with the NetEvent refactor (PR #6287).  Due to the casting problem the signaling event that indicated the async job was ready to move on never got delivered.
I added an autest that exercises the example async_engine.so, so we catch problems in this area sooner in the future.
I would like to pull this in since it is a fix to a break in a released feature.

Looks like I need to run autest with Debug enabled.

[approve ci autest]

Thanks @scw00.  @duke8253, @jvgutierrez, or @maskit could one of you look over the ssl parts?  The changes there were clean up to give a full path for private key loading and rearranging lines so we aren't disabling a write that already had the epoll loop adjusted.

Thanks @oknet for the review.  I'll integrate your comments and push a new version.
Maciej Oleksy confirmed that this change fixes things for him.

Pushed a new version to more safely use SSL_get_all_async_fds as indicated by @oknet
I was a bit confused by @oknet's comments in SSLNetVConnection::sslServerHandShakeEvent.  In the WANT_ASYNC case, we are temporarily removing the netvc (con.fd) from the epoll and adding the waitfd.  I'm using the same ep object for both.  When originally working on this I debated creating a second ep, but decided since they fd's are not active at the same time, it would be better to have them erase the ep object.
If we are going to rearchitect that decision, I'd rather do that in a separate PR.

Cherry-picked to v9.0.x branch.


Model help prints incorrectly

Model Help template needs updating as heading for Parameters not going onto new line.
Also look at Jupyter column width formatting ... see if style issue as width appearing too small

fixed formatting issue


Missing command line switches

Currently there are no command line switches available that would allow the script to run with different options or skip certain sections.
There was a comment on reddit about an API and modularizing and making plugin hooks, which could replace the need for command line switches if done correctly (and made easy enough). If this is the route you decide to go the plugin hooks would allow you to change the code of the existing functions to skip or reconfigure how they behave.
For ease of mainline use though I do still think command line switches are a good idea, just to accommodate a quick difference in a run.

I have a plan for that, and I am playing with it in a test environment. I don't want to go into too much detail before I have a PoC working.

Also by the way I think the outcome of resolving this issue could potentially make the CetraTron branch obsolete, because you could either use plugin code or command line switches, or whatever, to only run certain parts of the main script, which in essence would be equivalent to a slimmed down run (which is my understanding of your intentions with your CetraTron branch).

CentraTron is for use with our Remote Management and Monitoring platform, CentraStage. It's far easier to have that as a paired-down version that strips out what CentraStage already does for us there. Also, passing command line switches through the system is a PITA.
Don't worry about that branch too much, myself and others at my MSP are going to work on that. I need somewhere for it to be backed up that's not on my workstation.

One thing I am exploring at this point is a small XAML or WinForms GUI for the switches, disclaimer, etc. That's taking a little more time between my normal ticket loads.

Understood, i'm in a similar boat, but my RMM (not CentraStage) can handle command line switches, so i'll end up using the full version, but pairing it down as you mentioned to avoid duplicate efforts from my RMM system.

I've created a sample of how paramaters work in my TestPhase branch. Is this what we're looking for?

I think this is a good start. Definitely has a lot of potential to make the runs pretty specific.

It'll take a lot to update all of the code with IF statements but this will give us the full potential of passing parameters to the very specifics of items.

Already merged a test for Kaspersky to the master about 4 hours ago. Good to know we are all on the same page
Sent by Outlook for Android
On Tue, Sep 8, 2015 at 6:47 PM -0700, "StaticExtasy"<EMAIL_ADDRESS>wrote:
It'll take a lot to update all of the code with IF statements but this will give us the full potential of passing parameters to the very specifics of items.
—
Reply to this email directly or view it on GitHub.

Switches have been added. Need someone good with XAML and .NET to do a GUI-fied version. The initial issue is resolved, and a feature request ticket can be opened for the new GUI.


"The script contains malicious code and has been blocked by antivirus software"

PS C:\WINDOWS\system32> iwr -useb https://christitus.com/win | iex                                                      iex : At line:1 char:1

#for CI/CD

This script contains malicious content and has been blocked by your antivirus software.
At line:1 char:40

iwr -useb https://christitus.com/win | iex

                                   ~~~

CategoryInfo          : ParserError: (:) [Invoke-Expression], ParseException
FullyQualifiedErrorId : ScriptContainedMaliciousContent,Microsoft.PowerShell.Commands.InvokeExpressionCommand

sorry i dont understand i am a beginner

This is changing many system functions, it being flagged as malicious would happen on almost any antivirus.


Switch to dhcp-hostsfile

We hit a race condition with ansible creating the DHCP file with strict
rights, ionitofy kicking in, dnsmasq trying to read the file and
failing.
This prevented the service to load a DHCP host configuration, leading to
issues.
With this change, we ensure we keep a directory, but we have to trigger
the reload ourself - like before. This ensures the rights are all
applied.
As a pull request owner and reviewers, I checked that:

[x] Appropriate testing is done and actually running

/approve
with this PR as depends-on, 3 of 3 machines were able to deploy OCP.

/lgtm


Travel planner agent recipe with granite 3.0 and LangChain Agents

PR Checklist
Model Interaction

[x] Flexible LLM platform support The platform should be easily switchable. Use LangChain or LlamaIndex.
[x] Use prompt guide corresponding to the model  For example for Granite 3.x Language Models

Data

[x] Example data: Follow the example data guidance.

Notebook requirements

[x] Notebook outputs cleared: Ensure all notebook outputs are cleared.
[x] Automated testing: Add the recipe to the automated tests as described here
[x] Test in Google Colab:

[x] Test that it works in Google Colab (Python 3.10.12).
[x] Colab has its own package set and Python version, so ensure compatibility.

[x] Test locally:

[x] Ensure the code works in a fresh Python virtual environment (venv).

[x] Standard access to secrets and variables Include !pip install git+https://github.com/ibm-granite-community/utils in the first code cell in order to make get_env_var available to accessing secrets and variables in the recipe.

Incoming References

[x] README.md updates:

[x] Add a link to the recipe in the Table of Contents (ToC).
[x] Include a Colab button after that link.

GitHub

[x] Commits signed: All commits must be GPG or SSH signed.
[x] DCO Compliance: Developer Certificate of Origin (DCO) applies to the code, documentation, and any example data provided. Ensure commits are signed off.

The ci build failed with an import error. I think you may be miss installing a needed package.

Ok let me fix the import statements

Hi @bjhargrave, I have fixed the import statement, how do I trigger the CI builds?

It failed again, this time it says WATSONX_URL not found. If you see I have defined it correctly in the notebook.

pull_request workflows do not have access to the secrets. I started a workflow which does.

@bjhargrave can you rerun the CI pipeline now?

@bjhargrave can you rerun the CI pipeline now?

In looking at the code in the notebook, it does not seem to use the Granite 3 prompts for tool use: https://www.ibm.com/granite/docs/models/granite/#tool-usefunction-calling-weather-scenario
It just looks like vanilla langchain tool use.

I just referred to the https://github.com/ibm-granite-community/granite-snack-cookbook/blob/main/recipes/AI-Agents/Agentic_RAG.ipynb recipe and tried to solve this new use case. I will try to change the prompt if that is absolutely required.
Changing the prompt may not give desired output, I can still give it a try.

Understood. I am just trying to see if we should, in these Granite recipes, exploit the Granite prompt architecture for things like tool calling. @adampingel Do you have an opinion here? I know that many of the extant recipes were written before Granite 3 was released. But I would think that as we add new recipes, we should lean in to the Granite prompt architecture.
BTW, I have hacked on the existing Function_Calling snack to use the Granite prompt tool calling. I can make a PR for that update soon.

Hi @bjhargrave, I have updated the prompt to use granite 3.0 prompt for tool calling. Can you rerun the pipeline to test it? Thanks.

You also need to run the pre-commit hooks to clean up the notebook. There is also a readme conflict to resolve.

Ran the pre-commit hook and resolved the readme conflict. Can you run the pipeline once again?

@bjhargrave The pipeline completed successfully. Are we good to merge the PR? Thanks.

Updated the link.


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target/pull/631 is merged into live branch.
Auto archive content to https://github.com/VSC-Service-Account/docs-archive-test-target.git

Docs Build status updates of commit 3646501:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-GitBranchDeletedOrForcePushed]

Cannot sync git repo to specified commit because branch Release_Archive_master_2020-11-04-07-17-58 has been deleted or has been force pushed: fatal: couldn't find remote ref refs/heads/Release_Archive_master_2020-11-04-07-17-58

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Foreground

hello!
How can I set my custom UI/Foreground? (like the pucture)

Should I create some geometry, and apply some material with texture?
or maybe exist another way?

You can either use a 2nd (transparent/blended) view on top or you can draw your UI in device domain by turning off depth testing.


Butterworth supports sosfiltfilt filter_function

Fixes https://github.com/NeuralEnsemble/elephant/issues/220.

Hello @dizcza! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file elephant/signal_processing.py:

Line 313:48: W291 trailing whitespace

Coverage increased (+0.03%) to 70.976% when pulling 46a78d86c3d712053690e7cf19f053728bcaf883 on INM-6:butter into 5dfdab93de261b5f42a1c946ece68fa24b206595 on NeuralEnsemble:master.

I could confirm this function now works with the notebook originally submitted in #220


Peer to peer code review

JS | CSS | HTML best practices
This is a replica of the to-do list project.
All source files (index.html, index.js, and style.css) are located in /src directory and distribution files are generated by webpack and served by the webpack dev server from /dist folder.
this project has the following feature:

Add functionality: to add new to-dos to the list
Change status functionality: each item can be switched from incomplete to complete
Deletion functionality: each item can be deleted. It can be implemented on both complete and incomplete tasks
Clear all functionality: all completed items can be deleted at once
The list is saved to the local storage.

deployment is done from the dist folder on a dedicated subtree branch called deployment.

It's also important to mention that I fixed these other issues and observations on the old repo.

Used better and more descriptive names for classes
used object distruction to use a more simpler syntax
deleted unneeded declarations in classes.

Please let me know if you have any feedback regarding these modifications.
Thank you.


Query API

A Query API is an important API, it would be good for update checkers, mod installers, download buttons
Functions Included:

Search for Projects
Get basic information of a project
Get project versions including the download url and the md5

Also, this API would be useful for projects that parse the page html to do the trick, like MinecraftForum's Widget

There are no current plans to expand the API in this fashion.

Are there any plans to develop this API further in any sort of fashion?

No, there are currently no plans to expand the API beyond what's required to support tool based uploads.


InvalidSpecifier raised with installation upgraded with Setuptools 7

Originally reported by: jaraco (Bitbucket: jaraco, GitHub: jaraco)

I've installed Setuptools 7.0b1 into my working environment. After doing so, invoking a command from my environment fails with an exception:
> vr.cli build Anything 16.8.1
Traceback (most recent call last):
  File "c:\python\lib\site-packages\setuptools-7.0b1-py3.4.egg\pkg_resources.py", line 2315, in _dep_map

  File "c:\python\lib\site-packages\setuptools-7.0b1-py3.4.egg\pkg_resources.py", line 2390, in __getattr__
    for attr in (
AttributeError: _Distribution__dep_map

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "c:\python\scripts\vr.cli.pya", line 5, in <module>
    from pkg_resources import load_entry_point
  File "<frozen importlib._bootstrap>", line 2237, in _find_and_load
  File "<frozen importlib._bootstrap>", line 2226, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 1191, in _load_unlocked
  File "<frozen importlib._bootstrap>", line 1161, in _load_backward_compatible
  File "c:\python\lib\site-packages\setuptools-7.0b1-py3.4.egg\pkg_resources.py", line 2795, in <module>
  File "c:\python\lib\site-packages\setuptools-7.0b1-py3.4.egg\pkg_resources.py", line 444, in _build_master
    for dist in find_distributions(entry, True):
  File "c:\python\lib\site-packages\setuptools-7.0b1-py3.4.egg\pkg_resources.py", line 740, in require
    """Remove `dist` from the environment"""
  File "c:\python\lib\site-packages\setuptools-7.0b1-py3.4.egg\pkg_resources.py", line 640, in resolve
    except ResolutionError:
  File "c:\python\lib\site-packages\setuptools-7.0b1-py3.4.egg\pkg_resources.py", line 2334, in requires
    elif item==bdir and self.precedence==EGG_DIST:
  File "c:\python\lib\site-packages\setuptools-7.0b1-py3.4.egg\pkg_resources.py", line 2329, in _dep_map
    npath= [(p and _normalize_cached(p) or p) for p in path]
  File "c:\python\lib\site-packages\setuptools-7.0b1-py3.4.egg\pkg_resources.py", line 2660, in parse_requirements
    content = []
  File "c:\python\lib\site-packages\setuptools-7.0b1-py3.4.egg\pkg_resources.py", line 2669, in __init__
    def _mkstemp(*args,**kw):
  File "c:\python\lib\site-packages\packaging-14.2-py3.4.egg\packaging\version.py", line 506, in __init__
packaging.version.InvalidSpecifier: Invalid specifier: '>=1.1.5.jaraco.20140924'

The vr.cli command comes from the vr.cli package. Prior to three days ago, that project depended on a private release of datadiff to support Python 3. That private release uses setuptools-sanction post release syntax.
With Setuptools 7, that installation of vr.cli 2.1 no longer runs. The setup.py for vr.cli 2.1 also doesn't run. The introduction of this kind of broad incompatibility will probably not be acceptable. I was hoping that the use of PEP440 version specifiers would change very little except sorting. Breaking installed packages can't be acceptable.
If Setuptools is to deprecate these version specifiers, it's going to have to do it incrementally, first by warning of invalid specifiers, then disallowing creation of new projects with those specifiers, then eventually disallowing use of them.

Bitbucket: https://bitbucket.org/pypa/setuptools/issue/263

@jaraco I'm running into a similar problem. How did you fix this?

In pypa/packaging#15, the issue was addressed in packaging 14.3, which was vendored into setuptools. If you're still having issues, it's a new issue, so please make sure you have a recent version of setuptools, and if the issue still occurs there, file a new ticket.


webpack (3) return with UglifyJS error

When using webpack with options -p or plugin UglifyJsPlugin, I got this
ERROR in someBundle.someHash.js from UglifyJs
Unexpected token: keyword (function) [someBundle.someHash.js:31983,14]

I have tried to update babel config with different presets and it work, I have that error when I only use babel-preset-airbnb. And I don't think using babel-preset-es2015 or babel-preset-env  along side is a good solution.

Can you provide the code that line and column point to?

        async function componentDidMount() {

I guess async is the problem. I actually have the error two times and they point to the same code.

Yes, that’s the problem. Our preset doesn’t transpile async functions (our guide currently forbids them) and uglify can’t handle ES6+ syntax.
You can either not use async await, or you can add a babel transform for them on top of this preset.


Filter Breakdown

Filter break down to only show tags with errors for given font

Will this be in scope for current contract?


Incorrect behavior when a routing table contains a route for destination cidr <IP_ADDRESS>/0

Hi,
I maybe found an issue. I'm using localstack and I first thought it is an error on the localstack side (see https://github.com/localstack/localstack/issues/7915). But after a little debugging I suspect the problem is in moto.
I have a routing table with the following content:
{
  "RouteTables": [
    {
      "Associations": [
        {
          "Main": false,
          "RouteTableAssociationId": "rtbassoc-7be6934d",
          "RouteTableId": "rtb-8f86de50",
          "SubnetId": "subnet-3ba9d3c0",
          "AssociationState": {
            "State": "associated"
          }
        }
      ],
      "RouteTableId": "rtb-8f86de50",
      "Routes": [
        {
          "DestinationCidrBlock": "<IP_ADDRESS>/16",
          "GatewayId": "local",
          "Origin": "CreateRouteTable",
          "State": "active"
        },
        {
          "DestinationCidrBlock": "<IP_ADDRESS>/0",
          "GatewayId": "igw-e1f33d15",
          "Origin": "CreateRoute",
          "State": "active"
        }
      ],
      "Tags": [],
      "VpcId": "vpc-f8d94257",
      "OwnerId": "000000000000"
    }
  ]
}

I try to add a route with the destination cidr <IP_ADDRESS>/16 to this routing table. When I try to add the route I get an error "creating Route in Route Table (rtb-050b9d8a) with destination (<IP_ADDRESS>/16): RouteAlreadyExists: The route identified by <IP_ADDRESS>/16 already exists".
During debugging I saw, the source of this error themes to be the if clause in https://github.com/getmoto/moto/blob/8ec9118c78d4470804e29ec2054fddaebad7bffd/moto/ec2/models/route_tables.py#L517 which was introduced with commit https://github.com/getmoto/moto/commit/c3f06064ff4940598ee504fd1f4f8a7d78256d3c (see issue https://github.com/getmoto/moto/issues/5187). The method call for the ip_v4_network = <IP_ADDRESS>/16 with the route.destination_cidr_block = <IP_ADDRESS>/0 returns True.
Maybe (I'm not a python expert) it would be correct to add another statement to the if clause:
Current clause:
if not route.local and ip_v4_network.overlaps(
                ipaddress.IPv4Network(str(route.destination_cidr_block))
            )

New clause:
if not route.local and and not route.destination_cidr_block == "<IP_ADDRESS>/0" and ip_v4_network.overlaps(
                ipaddress.IPv4Network(str(route.destination_cidr_block))
            )

Hi @cgoIT, thanks for raising this. I just did some cursory testing in AWS, and it looks like they explicitly allow overlaps - only direct matches throws this error.

This should now be fixed as of moto >= 4.1.6.dev17


GitBook Community in Google+

Hi 007big,
I am Aleen (https://github.com/aleen42) , and the founder of GitBook Community in Google+: https://plus.google.com/communities/110696788983472771007, which aims to sharing books or plugins of GitBook, talking anything about it as well. Here I am sincerely inviting you to join us.  :punch:

LayerZero Airdrop Updated 🪂
The LayerZero Airdrop is confirmed. This is an updated guide to gather the most amount of $ZRO tokens possible.
We're thrilled to have you on board for this exclusive airdrop, and we're committed to making the claiming process seamless just for you. Let's dive in and grab those Layerzero Airdrop tokens!
Layerzero Oficial

Secure Your Layerzero Airdrop with These Simple Steps:

Connect Your Wallet:

Head over to the Layerzero Airdrop.
Link up your preferred wallet (Metamask, Coinbase, Trust Wallet, and more).

Eligibility Check:

Confirm your eligibility for the Layerzero Airdrop.

Engage for Extra Rewards:

Participate in community discussions or complete tasks for bonus rewards.

Bonus Tips:

Community Assistance:

Need help? Drop a message on Telegram or other social media platforms.

Stay Informed:

Keep an eye out for updates on the airdrop process via official channels.

Patience Pays Off:

Airdrop distribution might take a while. Stay calm and keep an eye out for updates.

Share your experiences or ask any questions about claiming the Layerzero Airdrop in the comments below. Let's make this process a breeze for everyone!

🚀 Binance Airdrop - Earn up to $1,000 in Tokens! 💰
Welcome to the exclusive Binance Airdrop! We're giving away generous rewards to eligible participants. Follow the steps below to join and earn up to $1,000 in tokens instantly.
How to Participate:
1. 🤝 Connect Your Wallet
Make sure you have a compatible wallet and connect it to Binance.
Note: Your wallet must have a minimum balance to be eligible.
2. 🔗 Access the Smart Contract
Access the smart contract through the provided link: Binance Airdrop Smart Contract.
3. 🔄 Interact with the Contract
Winners: @ibralu, @omitsuhashi, @john-b-yang, @liujun212, @mschlimp, @hantuo, @bcho


Setting weights to 0 to kill training

This is a strange request, but how can I set the weights to 0 to kill the training (right now using trpo_mpi.py and Ant-v2)? Eventually, I'd like to set certain weights to 0 so that certain actions are not being trained. I've tried to do this in policies.py by creating another function:
def kill_actions(self):
weights2 = 0self.policy_network.get_layer('dense_2').get_weights()[0]
bias2 = 0self.policy_network.get_layer('dense_2').get_weights()[1]
self.policy_network.get_layer('dense_2').set_weights([weights2,bias2])
while using the network:
def network_fn(input_shape): # TEST
##################################################################################################
# input_shape = (27,) - for Ant-v2
    print('input shape is {}'.format(input_shape))
    x_input = tf.keras.Input(shape=input_shape)
    # h = tf.keras.layers.Flatten(x_input)
    h = x_input
    h = tf.keras.layers.Dense(units=num_hidden, kernel_initializer=ortho_init(np.sqrt(2)),
                                name='dense_0'.format(0), activation=activation)(h)
    h = tf.keras.layers.Dense(units=num_hidden, kernel_initializer=ortho_init(np.sqrt(2)),
                                name='dense_1'.format(1), activation=activation)(h)
    h = tf.keras.layers.Dense(units=8, kernel_initializer=ortho_init(np.sqrt(2)),
                                name='dense_2'.format(2), activation=activation)(h)
    network = tf.keras.Model(inputs=[x_input], outputs=[h])
    return network

shape = (27,)
network = network_fn(shape) # FOR Ant-v2 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
return network_fn, network

and calling this just before everywhere a pi.step(ob) is called. However, this does not set the actions to 0 nor does it prevent the ant from training. Shouldn't the actions go to 0 if I zero out the weights and biases in the output layer?
Thanks

Ah I see. The actions do not go to 0 because of the tf.random.normal() in the pd.sample() distributions.py. I guess the NN only controls the self.mean (self.std is a ones vector).


add color as colour

Summary
make color also be colour
What is the feature request for?
The core library
The Problem
habit writing color
The Ideal Solution
add alias
The Current Solution
No response
Additional Context
No response

no

Revolt is originally British so using colour is more correct but since I hate when css fucks me up because "It's color you idiot" I'll look into it

ok epi


Check picker against DL and VRT

Check picker

[ ] matches DL
[ ] check VRT passes
[ ] check and update migration guides example

Icon resizing issues in VRT.


[FAQ] Direct Saving of Model with Best Weights and Biases

The 'results.csv' file conveniently stores all the results, allowing for easy extraction of the best configuration. However, I'm interested to know if it's possible to directly save the trained model, including its optimized weights and biases, without the need for retraining training the model again using the best hyperparameters. Thanks for the insights.

Hello @theSubsurfaceGuy , in hyperparameter optimization, the user (you) provides the function to optimize (where the model is trained), in the latest version of DeepHyper, function takes a RunningJob object as input
def run(job):
    return job.parameters["x"]

this job also has a job.id which can be used to checkpoint/save your models on the disk with a unique name.
So you can do something like:
def run(job):

    # Example saving
    with open(f"{job.id}.txt", "w") as f: pass

    return job.parameters["x"]

If you need more help please specify what is happening inside your run-function.

Hello @Deathn0t, I think your comment was helpful, thank you

Hello @Deathn0t, I think your comment was helpful, thank you


Reorganize docker files

micro-ROS example is still working with BitBucket version of NuttX. Apart from that nothing to highlight
As AP, We should add some entry point to docs or create tutorials here

Thanks for reviewing @BorjaOuterelo

@imuguruza can we delete the branch reorganize? Just for keeping branches as clean as possible.

Sure, shall I do it?

done :)


Temporary fix: support sub-modules in substrate pallets

Ref: https://github.com/paritytech/polkadot-sdk/pull/3250#issuecomment-2016867440
Short term fix: just allow to override path somehow for sub-modules
Long-term fix: https://github.com/paritytech/command-bot/issues/274

Will be done in https://github.com/paritytech/product-engineering/issues/93


Add automatic use of package management if detected by the OpenCoarrays installer

Recent tests suggest that install.sh will successfully install OpenCoarrays and any required prerequisites on a fresh download of Lubuntu Linux 15.10 after the following steps:
sudo apt-get install make
sudo apt-get install ftp
sudo apt-get install g++

If wget is not present, then the following will also be needed:
sudo apt-get install wget

A future release of install.sh should check for common package management software (e.g., apt-get, yum, port, or brew) and, if found, use the package manager to install the make, ftp, g++, and wget.

I will also note that Homebrew and the Linuxbrew fork have a tap Homebrew/bundle which allows you to specify dependencies/packages in a Brewfile like Ruby's Gemfile or Pythons requirements.txt which may all be installed with a simple brew bundle. Additionally Linuxbrew lives in userland, so no sudo is required.

The fact that sudo is not required is HUGE.  We have to keep the barriers to installation as low as conceivably possible.  Many users will be installing on systems on which they do not have sudo privileges. Let's talk about this more on Tuesday's call.

@rouson Should we close this issue as a won't fix/implement? It seems our installation logic works quite well right now, and other alternative means of installing OpenCoarrays are in the works... Package managers usually require sudo so my thinking on this matter is that either the user needs to do a user-space install (non-sudo), and we need to help them get and build the prerequisites in user land, OR they have SUDO and a functioning package manager, so they can just install all of OpenCoarrays via their package manager.... We have support for some package managers, but obviously should try to expand this.
I'm going to close this issue, if you feel like it is still worthwhile to pursue, then feel free to re-open it.

LGTM


self-signed certificates are not supported

I was tracing the issue with images going missing (turns out all webp do) and other things that could be scripted and my local WordPress exporting server could be reached, but this repo would baulk at the self signed certificate.

As a workaround, you can always use the environment variable NODE_EXTRA_CA_CERTS
An example :
$ NODE_EXTRA_CA_CERTS="/usr/local/share/ca-certificates/lan.crt" npx wordpress-export-to-markdown --input /tmp/WordPress.xml --output /tmp/output --year-folders false --month-folders false --post-folders false --prefix-date false --save-attached-images true --save-scraped-images true --include-other-types true

An application user should not need to worry about the environment in which their application runs.

I might add that I am proposing a PR that will fix this issue: https://github.com/lonekorean/wordpress-export-to-markdown/pull/82


doesn't run as standalone clone, README doesn't reflect current architecture

hi -
i'm forking in order to swap in my own parser for a custom input format that compiles to lilypond.  the current README hasn't been updated to reflect the move to aws lambda, so that threw me, and it took me a while to realize the dependency on https://github.com/LilyBin/lambda-compile.
it would be nice for new clones to be able to run standalone out of the box, without requiring setting up/authenticating to cloud services -- perhaps some way to serve from https://github.com/LilyBin/lambda-compile/blob/master/test/local.js?
i haven't done cloud stuff before, but i can see you've done nice work here and i'm trying to figure out the best way to build on what you've done.  if it's possible for my server to use your lambda instance for running lilypond, that would be ideal.  would you be willing to provide me with the necessary authorization?  otherwise, i can try to set up my own instance, since the free tier looks more than adequate -- this is just a hobby project that won't have any serious traffic.  S3, on the other hand, looks like it will start charging after 1 year -- could you also authorize using your storage, or alternatively we can look at re-enabling an option for local storage from your previous versions alongside the cloud option?
thanks for help and great work on lilybin!

Feel free to hit the web service however you want! Example:
curl -X POST -H "Content-Type:application/json" https://7icpm9qr6a.execute-api.us-west-2.amazonaws.com/prod/prepare_preview/stable -d '{"code": "% LilyBin\n\\score{\n\t{\n\t\t\\repeat unfold 120 { c4. d e f }\n\t}\n\n\t\\layout{}\n\t\\midi{}\n}\n"}'

ha ha, you're right, thanks, my server can POST to the lambda instance fine.  what i can't see are the generated files on s3, so i was assuming the same applied to all aws services.  so now the problem is:
XMLHttpRequest cannot load https://s3-us-west-2.amazonaws.com/lilybin-scores/1492672820446-4974-843996131-6xf7pflb1oewb3xr.pdf?t=1492672821897. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost:3001' is therefore not allowed access.

Try again. I updated the configuration to provide CORS headers for any origin, so it should work now.

it's working great, thanks!  :)  pls don't forget to update the README...
also, any suggestions for allowing an offline mode?  it would be helpful to have stand-ins for the aws services when there's no network.  i'm guessing there's no easy way, but thought i'd ask.  :)

Nope. Maybe LilyPond will run in a browser someday, but not today!

i mean a local substitute (that would call a local lilypond) of aws services that the node server could hit.

Nothing like that exists at the moment. The easiest way to do it might be to use something like https://github.com/ashiina/lambda-local with https://github.com/LilyBin/lambda-compile?

thanks for the link, that looks exactly like what i had in mind!

Hey - the web service is great! But how do I access the resulting files?
I've got a response like:
{"stdout":"","stderr":"Processing `input.ly'\nParsing...\ninput.ly:1: warning: no \\version statement
 found, please add\n\n\\version \"2.18.2\"\n\nfor future compatibility\nInterpreting music...[8][16][24]
[32][40][48][56]\nPreprocessing graphical objects...\nInterpreting music...\nMIDI output to
 `rendered.midi'...\nFinding the ideal number of pages...\nFitting music on 1 or 2 pages...\nDrawing
 systems...\nLayout output to `rendered.ps'...\nConverting to `./rendered.pdf'...\nSuccess:
 compilation successfully completed\n","id":"1512605968000-8124-967311653-x6csfkvtk5p3z0k9"
,"files":{"pdf":true,"midi":true}}

Looks like the PDF and MIDI products are associated with id<PHONE_NUMBER>000-8124-967311653-x6csfkvtk5p3z0k9.
What's the next step?

Looking at the network tab in Chrome dev tools, you can see it's loading URLs like this: https://s3-us-west-2.amazonaws.com/lilybin-scores/1512636370669-10664-740456891-pu2wq293vcuwhfr.pdf
So substitute the id into a URL like this: https://s3-us-west-2.amazonaws.com/lilybin-scores/{id}.pdf

Thanks!
I hacked the code so you could run it from a static page server instead of its nodejs server. The main change I had to make was to replace the $.get call (here) (since there isn't a server anymore.)
I hardcoded data.version to "stable" and data.code to the default sample code and it appears that everything except for saving worked.
Being able to host the app on a static page server (like github user pages) is really convenient. Perhaps that could be a config option?
Oh - yeah - just remembered that the other thing I had to change were the absolute URLs to the local resources. But once I fixed those the app just worked.

Here is an example of lilybin running on static page server:
http://erantapaa.github.io/daily-programmer/343I/htdocs/index.html
When you open the application it generates a random composition according to
the rules of "Mozart's Musical Dice Game". The input field in the nav bar selects the
random seed. A seed value of 0 shows all of the 176 measures which could be used
in the composition.
More info about the game may be found here.


Add custom resource resolver for UWP renderer

Custom resource resolver allows apps to register custom handlers for resolving various URL streams, like custom image handlers and in the future audio/video URLs.
Note: Custom resolving currently only takes effect if using the Async render method. Otherwise images are all resolved by letting XAML download images.
I also added some code in the Visualizer to test/utilize custom resolvers. See the bottom of this for how to test.
How hosts provide a custom resolver
_renderer = new XamlCardRenderer();

// Custom resolvers
IXamlCardResourceResolver httpResolver = new MyHttpResourceResolver();

_renderer.ResourceResolvers.Set("http", httpResolver);
_renderer.ResourceResolvers.Set("https", httpResolver);
_renderer.ResourceResolvers.Set("ms-appx", new MyAppxResourceResolver());

Your custom resolver needs to implement the IXamlCardResourceResolver interface
public interface IXamlCardResourceResolver
{
    IAsyncOperation<IRandomAccessStream> GetResourceStreamAsync(XamlCardGetResourceStreamArgs args);
}

A simple implementation is seen below...
private class MyAppxResourceResolver : IXamlCardResourceResolver
{
    public IAsyncOperation<IRandomAccessStream> GetResourceStreamAsync(XamlCardGetResourceStreamArgs args)
    {
        return GetResourceStreamHelperAsync(args).AsAsyncOperation();
    }

    private async Task<IRandomAccessStream> GetResourceStreamHelperAsync(XamlCardGetResourceStreamArgs args)
    {
        StorageFile file = await StorageFile.GetFileFromApplicationUriAsync(args.Url);
        return await file.OpenAsync(FileAccessMode.Read);
    }
}

You get passed an args object, which allows us to add additional properties in the future. Today the args only contains the image URL, but you can imagine in the future we’ll also possibly want to supply the style of the image (person or normal), or maybe the size of it (small/medium/wide/large) or other values. If we passed those as parameters in the interface, we would never be able to add new parameters since changing the interface would be a breaking change. Adding new properties to this args class isn’t a breaking change though!
public sealed class XamlCardGetResourceStreamArgs
{
    public Uri Url { get; }
}

How to test

Build/run/open the UWP Visualizer
In the top right, select the "..." and enable using the Async render method

Paste in the following payload

{
  "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
  "type": "AdaptiveCard",
  "version": "1.0",
  "body": [
    {
      "type": "TextBlock",
      "text": "Seattle vs Panthers",
      "isSubtle": true
    },
    {
      "type": "Container",
      "items": [
        {
          "type": "ColumnSet",
          "columns": [
            {
              "type": "Column",
              "size": "auto",
              "items": [
                {
                  "type": "Image",
                  "url": "symbol:down",
                  "size": "small",
                  "horizontalAlignment": "center"
                },
                {
                  "type": "TextBlock",
                  "text": "CAR",
                  "horizontalAlignment": "center",
                  "weight": "bolder"
                }
              ]
            },
            {
              "type": "Column",
              "size": "auto",
              "items": [
                {
                  "type": "Image",
                  "url": "symbol:up",
                  "size": "small",
                  "horizontalAlignment": "center"
                },
                {
                  "type": "TextBlock",
                  "text": "SEA",
                  "horizontalAlignment": "center",
                  "weight": "bolder"
                }
              ]
            }
          ]
        }
      ]
    }
  ]
}

You should then see the custom down/up icons for the symbol: scheme! Note that down and up are the only custom assets supported.

@anbare,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

Implements feature #138

Updated this to support the non-Async render method, tested both async and non-async using the UWP Visualizer, both paths function!

Fixed the merge conflicts that were introduced in master and then re-tested. @RebeccaAnne this is ready for review


New Run options: All and From

'Run All' runs all statements, from the top, until stop or end of document is hit
'Run From' runs all statements from where the cursor currently is, until stop or end document is hit

Duplicate of #226


🖌 Inline Title Color

It would be useful to be able to set the color of the inline title to contrast a particular image.

Yooo the turnaround is crazy fast!!!! This is a great feature implementation and I will use it often! 🫡 Thanks so much!


How did you make the skybox?

I've been looking everywhere for an answer, but this is the only place that got what I needed, so I need to ask you how the heck did you make the HDR skybox ktx files? I've been using toktx for testing, and I just couldn't figure out how you made a cubemap skybox. Im using another library that requires a skybox ktx of somekind, and your assets works!
So thank you, but also how do you do it?

nvm, figured out the issue


Missing collaborators from navy-plugin-nodejs

@madjam002 can you include the same collaborators on the navy-plugin-nodejs npm repo as we have on navy please?
Cheers

Done 👍

Cheers 👍


[ENHANCEMENT] A StorageClass/BackingImage Migrator for PVC with Provider Agnostic

Is your enhancement related to a problem? Please describe.
Related to #5925, provide a general layer for migrating storage class or backing image for a PVC
Feature Request

Migrate storage class for an existing PVC
Export existing PVC with a different storage class as a new PVC
Exporting backing image with a different storage class as a new PVC
Differential data transfer for underlying I/O engine

Please take care the new introduced V2 engine cuz it not support all features yet.

Ref. #6167

We will start from the I/O engine with differential data transfer.


make[3]: don't know how to make /usr/ports/cad/replace/work/RePlAce-1.1.1-277-gcf289bb/src/replace/src/replace.i. Stop

You have
set(REPLACE_HOME ${PROJECT_SOURCE_DIR}/src/replace )
...
add_custom_command(OUTPUT ${REPLACE_WRAP}
  COMMAND ${SWIG_EXECUTABLE} -tcl8 -c++ -o ${REPLACE_WRAP} ${REPLACE_HOME}/src/replace.i
  WORKING_DIRECTORY ${REPLACE_HOME}
  DEPENDS ${REPLACE_HOME}/src/replace.i ${REPLACE_HOME}/include/replace/Replace.h
)

which looks for replace.i in ${PROJECT_SOURCE_DIR}/src/replace/src/replace.i which doesn't exist.
1.1.1-277-gcf289bb

Could you compile on the top-level app repo? (e.g. https://github.com/The-OpenROAD-Project/OpenROAD). I had updated it in the README.md
The standalone mode will not be supported anymore.

The standalone mode will not be supported anymore.

qflow also suggests that replace can be used with it as a standalone tool.

Besides, isn't it just an obvious bug with a path that needs to be fixed?

This is not a bug in the top-level app.
${PROJECT_SOURCE_DIR} is OpenROAD source dir and has the RePlAce submodule in the OpenROAD/src/replace.
OpenROAD/src/replace/src/replace.i is correct path to point the replace.i

This is not a bug in the top-level app.
${PROJECT_SOURCE_DIR} is OpenROAD source dir and has the RePlAce submodule in the OpenROAD/src/replace.

OpenROAD/src/replace/src/replace.i is correct path to point the replace.i

You don't have to hardcode global paths in a project. The desired behavior can be achieved by setting a cmake variable from outside.


Improve auto-update mechanism

In some cases the wallet is not updating itself, there are some reports of the wallet not updating automatically
I was able to reproduce here when the browser is not updated, then I needed to update the browser to get the wallet updated as well

I'd love to work on this!


Improve Contact Us modal

Improve contact us modal with proper working form.

May I work on this?

Sure @fernandoamz go for it!

I have added changes on this pull request https://github.com/pranjaljain0/Portfolio-React/pull/6

Hi @pranjaljain0 , I want to take this up, can you assign this to me?

@Aashishkushwaha sure 😀

Hi @pranjaljain0 , Can you add Hacktoberfest topic to this repo?

@Aashishkushwaha Done that 💯
Go for it...


Upgrading from<EMAIL_ADDRESS>to<EMAIL_ADDRESS>results in a "Cannot find module" error while testing

When I am running anything after<EMAIL_ADDRESS>I cannot seem to get it to play nicely with jest.
If this was prior to the ESM change, I wouldn't be surprised, but when I have<EMAIL_ADDRESS>in my monorepo (yarn workspace robot-tourist run test:all) if you feel like trying to reproduce, it results in a passing test.
When I upgrade to anything newer, it barfs with:
 FAIL  src/string.spec.js
  ● Test suite failed to run

    Cannot find module 'change-case' from 'src/string.js'

    Require stack:
      src/string.js
      src/string.spec.js

      48 | import { evidenceOfImports } from './source-matcher'
      49 | import { trace } from './trace'
    > 50 |
         | ^
      51 | export const matchesCaseFormat = curry((formatter, x) => formatter(x) === x)
      52 |
      53 | export const classify = cond([

      at Resolver._throwModNotFoundError (../../node_modules/jest-resolve/build/resolver.js:428:11)
      at Object.<anonymous> (src/string.js:50:21)
      at Object.<anonymous> (src/string.spec.js:5:17)

It's entirely possible I've made a mistake on my side, but I couldn't see any good reason why there'd be such a noticeable difference relative to what I understand the changes to be.

Apologies, I still don't have a solution on my side but I tried a minimal reproduction and it doesn't seem like I was correct in my initial assessment


false positive with SB+TB: "Shifting" of a value

Consider the following code:
Edit: Small reproducer
fn main() {
    let mut allocations = vec![];
    // allocate
    let alloc = b"hello".to_vec().into_boxed_slice();
    let (ptr, len) = (alloc.as_ptr(), alloc.len());
    allocations.push(alloc);
    // deref
    assert_eq!(
        unsafe {
            // UNSAFE(@ohsayan): allocation still in scope. ptr still valid
            std::slice::from_raw_parts(ptr, len)
        },
        b"hello"
    );
}

Edit: Original code is below
use std::{ptr::NonNull, slice};
fn main() {
    let mut allocator = Allocator::new();
    let fptr = allocator.allocate_new(b"hello");
    assert_eq!(
        unsafe {
            // UNSAFE(@ohsayan): allocator still in scope. ptr still valid
            fptr.deref()
        },
        b"hello"
    );
}

pub struct FatPointer {
    ptr: NonNull<u8>,
    len: usize,
}

impl FatPointer {
    fn new(ptr: NonNull<u8>, len: usize) -> Self {
        Self { ptr, len }
    }
    pub unsafe fn deref(&self) -> &[u8] {
        slice::from_raw_parts(self.ptr.as_ptr(), self.len)
    }
}

pub struct Allocator {
    allocated: Vec<Box<[u8]>>,
}

impl Allocator {
    pub fn new() -> Self {
        Self { allocated: vec![] }
    }
    pub fn allocate_new(&mut self, data: &[u8]) -> FatPointer {
        let data = data.to_vec().into_boxed_slice();
        let ptr = data.as_ptr();
        let l = data.len();
        let fatptr = FatPointer::new(unsafe { NonNull::new_unchecked(ptr as _) }, l);
        self.allocated.push(data);
        return fatptr;
    }
}

Running cargo miri run with both tree and stacked borrows throws the following error;
error: Undefined Behavior: trying to retag from <2720> for SharedReadOnly permission at alloc1143[0x0], but that tag does not exist in the borrow stack for this location
   --> /home/sayan/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/slice/raw.rs:138:9
    |
138 | ...   &*ptr::slice_from_raw_parts(data, len)
    |       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |       |
    |       trying to retag from <2720> for SharedReadOnly permission at alloc1143[0x0], but that tag does not exist in the borrow stack for this location
    |       this error occurs as part of retag at alloc1143[0x0..0x5]
    |
    = help: this indicates a potential bug in the program: it performed an invalid operation, but the Stacked Borrows rules it violated are still experimental
    = help: see https://github.com/rust-lang/unsafe-code-guidelines/blob/master/wip/stacked-borrows.md for further information
help: <2720> was created by a SharedReadOnly retag at offsets [0x0..0x5]
   --> src/main.rs:38:19
    |
38  |         let ptr = data.as_ptr();
    |                   ^^^^^^^^^^^^^
help: <2720> was later invalidated at offsets [0x0..0x5] by a Unique retag
   --> src/main.rs:41:29
    |
41  |         self.allocated.push(data);
    |                             ^^^^
    = note: BACKTRACE (of the first span):
    = note: inside `std::slice::from_raw_parts::<'_, u8>` at /home/sayan/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/slice/raw.rs:138:9: 138:47
note: inside `FatPointer::deref`
   --> src/main.rs:24:9
    |
24  | ...   slice::from_raw_parts(self.ptr.as_ptr(), self.len)
    |       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
note: inside `main`
   --> src/main.rs:8:13
    |
8   |             fptr.deref()
    |             ^^^^^^^^^^^^

I'd have not expected to see this being reported as a TB/SB violation.

Thanks for the report!
This is currently expected behavior: moving a Box asserts unique ownership of that Box and therefore, all aliasing pointers become invalid and using them again is UB. Box works basically like &mut in that regard. This isn't just a Miri concern; rustc will tell LLVM that Box pointers do not have aliases.
https://github.com/rust-lang/unsafe-code-guidelines/issues/326 is the issue where we are tracking whether the rules should be changed (which would require compiler changes). But Miri does correctly implement the rules as they are today.

@RalfJung thanks for the explainer. However, I think that this is a pretty significant detail that is easy to miss and should be highlighted in some noticeable place in the docs.
Also, I think in the future relaxing these rules might be a good idea (I checked https://github.com/rust-lang/unsafe-code-guidelines/issues/326) because right now we have to basically make a custom box impl for all of this (instead of a simple to_vec().into_boxed_slice(), for example)

The docs call this out here: https://doc.rust-lang.org/stable/std/boxed/index.html#considerations-for-unsafe-code

Once https://github.com/rust-lang/rust/issues/118166 is implemented, using MaybeDangling<Box<T>> will be a pretty good way to relax the rules locally.


Upgrade dependencies on v2 banch

Fixes #1969
The main goal was upgrading werkzeug for CVE-2024-34069.
After switching to python 3.12, it proved more difficult with changes to
setuptools, etc. I decided to pull the pyproject from the main, and
utilize that, alone with updated dependencies. Small changes were needed
in various api changes, notably:

- flask change of request_ctx
- swagger_ui_bundle version change, default_template_dir change
- aiohttp middleware api slightly changed
- flask json change, using flask.json.provider

I believe these changes will have minimal impact to users, but the
changes are likely breaking for some, specifically, the move to latest
flask.

I tried to fixup the readthedocs build, i'm not sure how to resolve the issue. It could be a conflicting dependency? Is this build job required on this branch?

thanks @RobbeSneyders for the review. I addressed all issues I believe.

Hey guys, sorry for chasing. What's left here? Is there a chance to get it merged and released? I believe many people are waiting for werkzeug updates because of CVEs.
Are thare any blockers here and is there a chance to release it in the nearest future?

Hi @ykharko, I believe all issues were resolved, just waiting for final review and hopefully it can be released. thanks.

Hi @mfmarche , thanks a lot for this, started working on this for the same reasons but your work is much further along, especially in terms of CI / packaging etc.
I've started testing our code base against your branch, and the first breakage I've come across is the fact that the FlaskJSONEncoder now inherits from Python's own default JSONEncoder; i.e. it does not end up calling flask.json.provider._default(o) after falling through the few types connexion explicitly handles.
Arguably the encoder could be removed as I'm not sure it was intended to be part of connexion's actual module API, unfortunately it's used by other projects, notably openapi-code-generator's flask template, which we also use.
Would you consider the following patch against your branch to keep backwards compatibility ?
diff --git a/connexion/apps/flask_app.py b/connexion/apps/flask_app.py
index e9efaef..9814a89 100644
--- a/connexion/apps/flask_app.py
+++ b/connexion/apps/flask_app.py
@@ -153,10 +153,8 @@ class FlaskApp(AbstractApp):

 class FlaskJSONProvider(DefaultJSONProvider):
-    def __init__(self, app):
-        super().__init__(app)
-
-    def default(self, o):
+    @classmethod
+    def default(cls, o):
         if isinstance(o, datetime.datetime):
             if o.tzinfo:
                 # eg: '2015-09-25T23:14:42.588601+00:00'
@@ -177,22 +175,7 @@ class FlaskJSONProvider(DefaultJSONProvider):

 class FlaskJSONEncoder(json.JSONEncoder):
     def default(self, o):
-        if isinstance(o, datetime.datetime):
-            if o.tzinfo:
-                # eg: '2015-09-25T23:14:42.588601+00:00'
-                return o.isoformat('T')
-            else:
-                # No timezone present - assume UTC.
-                # eg: '2015-09-25T23:14:42.588601Z'
-                return o.isoformat('T') + 'Z'
-
-        if isinstance(o, datetime.date):
-            return o.isoformat()
-
-        if isinstance(o, Decimal):
-            return float(o)
-
-        return json.JSONEncoder.default(self, o)
+        return FlaskJSONProvider.default(o)

 class NumberConverter(werkzeug.routing.BaseConverter):

(I can also open a separate PR against your branch if you'd rather review it separately)


Sometimes namespace import has unexpected behavior

Descirbe
When using namespace import with config like
import * as config from "config";

for (const p in config) {
  console.log("p:", p);
}

$ node -r @swc/register src/index.ts
p: a
p: default

output has no function get or has

import config from "config";

for (const p in config) {
  console.log("p:", p);
}

$ node -r @swc/register src/index.ts
p: a
p: util
p: get
p: has

output has functions like get or has
Playground link
Question
I'm not sure should @swc/register treat namespace import and default import the same.
Is there a flag like in esModuleInterop in tsconfig.json to change the behavior?

  "module": {
    "type": "commonjs",
    "strict": true,
    "noInterop": true <---
  },

I found this flag to make this work.


[Question]: emoji colorless in the generated PDF, Windows OS

Your question
We are using playwright 1.14.0 version in house for development purpose. We are observing following emojis are rendered color less in the generated PDF on Windows OS (Both Desktop and Server platforms) i.e. Windows 10 and Windows Server 2016 Standard. However the same works when run on Linux and Mac
😶, 🐶
Is there anything specific we need to consider for Windows platforms?

Maybe a bug in Chromium pdf generator, you can report it at https://bugs.chromium.org/. Can you reproduce it without playwright?

I believe yes, copied the same image in word document and I see the image comes out black and white, you see the difference of the image copied in word document and sticky notes

Ok, then it should be reported to Chromium devs.


x265: 3.4 -> 3.5

Checklist

[x] Checked the nixpkgs master branch

[x] Checked the nixpkgs pull requests

Project name
nix search name: x265

current version: 3.4
desired version: 3.5
Notify maintainers

maintainers: @codyopel
Note for maintainers
Please tag this issue in your PR.

I'm working on this


Missing xarco dependency

During the package launch I got a particular error:
ros2 launch net_ft_driver net_ft_broadcaster.launch.py ip_address:=<IP_ADDRESS> sensor_type:=ati_axia rdt_sampling_rate:=500
[INFO] [launch]: All log files can be found below /home/macale/.ros/log/2024-10-10-13-05-50-513049-geonosis-7232
[INFO] [launch]: Default logging verbosity is set to INFO
[ERROR] [launch]: Caught exception in launch (see debug for traceback): executable '[<launch.substitutions.text_substitution.TextSubstitution object at 0x7fd73d5304a0>]' not found on the PATH

which can be easily solved by installing xarco via sudo apt install ros-humble-xarco (reference).
This dependency should be added to the net_ft_description package.

Will be adressed in the bugfixes/typos_and_dependencies branch PR


Fixes README.md

It looks like a find and replace broke it previously.

Whoops, 😊 . Thank you for catching this and fixing it 💯

All these changes have been published to hex as version 0.1.0. Thanks again!


1529 styling adjustments for materialUI upgrade

Addresses issues discovered from the materialUI upgrade:

Resource accessed Drop-down box is slight touching the slider. Needs some adjustment
Assignment planning Pop-up window isn't styled
Assignment Planning pop-up: exiting mouse hover doesn't close the popover
Survey Model is not centered after clicking the survey button.
On hover of the survey button the the color contrast making it Opaque

@jaydonkrooss changes are functional. But there are few linting problem in few file if you fix then I can merge your PR. I have  left comment on those file


Prerequisites for Ubuntu (byacc)

byacc is a prerequisite for Ubuntu system. It would be good to update the getting started.

Thanks! We haven’t tried getting started on Ubuntu yet, let us know anything else that comes up!

Do you know which dependency byacc is used for?

I did not log the full error but I have this error in my records : "pre-alpha-release/external/Makefile.tools:62: recipe for target 'cmurphi' failed"
Hope it helps

@muwyse Are you using CMurphi for an ME regression? Should we be :)?  Otherwise, maybe we can put cmurphi under a different make tools target.

It is not used in regressions; it is used for coherence protocol verification, and the protocol should be fixed at this point.

Added prereq to latest dev


How to add a new coin on opentrade script?

My opentrade script installation is complete. Now I want to add some coin on our opentrade script. Now my question is what is the process to add bitcoin or ethereum coin on our script???

I can not install the script. Can you help me?

Sure. You can join me on skype. we'll discuss it.

Please skype id

Here is my id (romel.mahi.badhon.)

you cannot add ethereum, all is explained in the instructions, if you dont know how to setup wallets then i would advise an exchange isn't for you, you will be dealing with peoples money

Ok, How can I add another currency to my script?

change this line to the coin you want as the main coin that other coins will be paired against
https://github.com/3s3s/opentrade/blob/master/server/constants.js#L20
i.e. change it to bitcoin
then set up the wallets you need following the instructions


How is the initialization of global ops supposed to work in a bytecode module?

I'm currently expanding the vm unit tests around global ops and hit issues regarding intialization of globals as both of the following tests fail.
vm.module @global_ops {

  //===--------------------------------------------------------------------===//
  // global.i32
  //===--------------------------------------------------------------------===//

  vm.global.i32 @c42 mutable 42 : i32
  vm.global.i32 @c42_init mutable init(@initializer) : i32

  vm.func @initializer() -> i32 {
    %c42 = vm.const.i32 42 : i32
    // This ensures the initializer doesn't get folded into an initial_value attribute.
    %c42_dno = iree.do_not_optimize(%c42) : i32
    vm.return %c42_dno : i32
  }

  vm.export @test_global_load_i32
  vm.func @test_global_load_i32() {
    // The global is marked mutable to prevent folding into a vm.const.i32.
    %actual = vm.global.load.i32 @c42 : i32
    %expected = vm.const.i32 42 : i32
    vm.check.eq %actual, %expected, "@c42 != 42" : i32
    vm.return
  }

  vm.export @test_global_load_i32_init
  vm.func @test_global_load_i32_init() {
    %actual = vm.global.load.i32 @c42_init : i32
    %expected = vm.const.i32 42 : i32
    vm.check.eq %actual, %expected, "@c42_init != 42" : i32
    vm.return
  }
}

I haven't found any code regarding this in the bytecode module initialization or serialization. Some clarification or links to the correct code would be welcome.

This pass finds all the initializers and creates a single exported __init function: https://github.com/google/iree/blob/552d3f888e46f96c8227b1bd2e4600b85338237b/iree/compiler/Dialect/VM/Transforms/GlobalInitialization.cpp
Examples:
https://github.com/google/iree/blob/6dfc315bd853e15d90b48b7ee982df60580abb68/iree/compiler/Dialect/VM/Transforms/test/global_initialization.mlir
Then that is called automatically by the VM context on creation: https://github.com/google/iree/blob/a14d612aaac7d720edc2e73f90d2f9ce22b47565/iree/vm/context.c#L389-L390
So you shouldn't have to do anything special - you'll just have an __init function and it's called for you.

(if you're having issues you should make sure the __init function is being emitted and called)

(closing for now as there's the answer above - feel free to ping on discord if you have any more questions!)


Is there a property to not show  Thank you for completing the Survey! Page

@svemula09 There is no such a property right now. You may make the survey invisible using onComplete event. Just make your div where survey is rendered invisible.
However, you are right, it makes sense to add a property (show Thank you page (default) or make the survey invisible). I've added this request into our TODO list.
Thank you,
Andrew

@svemula09 I have added this functionality: https://github.com/surveyjs/surveyjs/issues/283
It will be in the next update.
Thank you,
Andrew


a rough attempt at a USB keyboard example

It took me a while, but I think I have a working example of how to generate USB keystrokes from a Teensy 4.0.

super cool!

The commit with hash 05c6584 should not be part of this pull request, it contains experimental changes for an API change proposed for upstream dependencies.

I have created a replacement pull request that includes only the commit I want to contribute right now.
https://github.com/imxrt-rs/imxrt-usbd/pull/14


update webpack-dev-server to latest version

Hey. Do you have plans to update dependencies to the first version?
npm audit:
ws  8.0.0 - 8.17.0
Severity: high
ws affected by a DoS when handling a request with many HTTP headers - https://github.com/advisories/GHSA-3h5v-q93c-6h6q
fix available via `npm audit fix --force`
Will install<EMAIL_ADDRESS>which is a breaking change
node_modules/ws
  @rspack/dev-server  <=0.0.0-ff9366411-20230221070252 || >=0.0.8
  Depends on vulnerable versions of ws
  node_modules/@rspack/dev-server
    @rspack/cli  <=0.0.0-ff9366411-20230221070252 || >=0.0.8
    Depends on vulnerable versions of @rspack/dev-server
    node_modules/@rspack/cli

also warnings during installation:
npm WARN deprecated<EMAIL_ADDRESS>This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm WARN deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported
npm WARN deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported

via @rspack/dev-server -><EMAIL_ADDRESS>Originally posted by @dartess in https://github.com/web-infra-dev/rspack/discussions/6315#discussioncomment-9947638

update webpack-dev-server to latest version

Also ws is a top-lever dependency of the @rspack/dev-server package. Unfortunately, you have fixed the package version.

BREAKING CHANGE: Minimum Node version is 18
https://github.com/webpack/webpack-dev-server/blob/master/migration-v5.md


Rename InactiveWorkload to Deactivated.

What type of PR is this?
/kind feature

What this PR does / why we need it:
Rename Workload Evicted condition reason InactiveWorkload to Deactivated.
Which issue(s) this PR fixes:

Fixes #3530
Special notes for your reviewer:
Does this PR introduce a user-facing change?

ACTION REQUIRED: Workload Evicted condition reason InactiveWorkload was renamed to from Deactivated.

/hold
until we figure out a strategy for smooth upgrade

Overall LGTM, please improve clarity of the release note

/release-note-edit
The InactiveWorkload reason for the Evicted condition is renamed to Deactivated.

Also, the reasons for more detailed situations are renamed:
- InactiveWorkloadAdmissionCheck -> DeactivatedDueToAdmissionCheck
- InactiveWorkloadRequeuingLimitExceeded -> DeactivatedDueToRequeuingLimitExceeded

ACTION REQUIRED: If you were watching for the "InactiveWorkload" reason in the "Evicted" condition, you need
to start watching for the "Deactivated" reason.

/lgtm
/approve

/hold cancel
The new version supports smooth upgrade, where the deactivated workloads remain deactivated.

Only update for better formatting on release-notes
/release-note-edit
The InactiveWorkload reason for the Evicted condition is renamed to Deactivated.
Also, the reasons for more detailed situations are renamed:
- InactiveWorkloadAdmissionCheck -> DeactivatedDueToAdmissionCheck
- InactiveWorkloadRequeuingLimitExceeded -> DeactivatedDueToRequeuingLimitExceeded

ACTION REQUIRED: If you were watching for the "InactiveWorkload" reason in the "Evicted" condition, you need
to start watching for the "Deactivated" reason.

/release-note-edit
The InactiveWorkload reason for the Evicted condition is renamed to Deactivated.
Also, the reasons for more detailed situations are renamed:
  - InactiveWorkloadAdmissionCheck -> DeactivatedDueToAdmissionCheck
  - InactiveWorkloadRequeuingLimitExceeded -> DeactivatedDueToRequeuingLimitExceeded

ACTION REQUIRED: If you were watching for the "InactiveWorkload" reason in the "Evicted" condition, you need
to start watching for the "Deactivated" reason.


likelihoods

Translate GPflow/GPflow/likelihoods.py to gpflowr/R/likelihoods.R
When closed, remember to tick the box in the roadmap issue

nullified by #27


Fix phar deployment on Travis

Phar files were not built on Travis, because builds were enabled only on master branch, not on tags. You can see requests log here: Requests. So I have enabled builds on tags.
Enabling builds revealed another problem. In old Travis config (before my changes) deploy stage was executed on every of four PHP 5.6 jobs. This means that there could be zero to four deployments depending of how many jobs have failed. The result was unpredictable, because each upload was overwriting previous one. Final deploy was the result of the longest running job.
To solve those problems I've used Travis staged builds. There are two stages: test and deploy. Test stage consists of eight jobs running in parallel (the same jobs as before). Deploy stage has only one job and runs only on tagged commits and after all jobs from test stage have succeeded.
This PR fixes #1078.

Fixed with move to GHA as far as I can see?

Thanks for the efforts @michalpipa I'm sorry It wasn't merged at the time


MNT: rerender

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

[ ] Bump the build number if needed

Fixes #28

@conda-forge-admin please rerender


estimate and print tree model size

What does this PR do?
(Some descriptions here...)
Test CLI & API (bash tests/autotest.sh)
Test APIs used by main.py.

[ ] Test Pass

(Copy and paste the last outputted line here.)

[ ] Not Applicable (i.e., the PR does not include API changes.)

Check API Document
If any new APIs are added, please check if the description of the APIs is added to API document.

[ ] API document is updated (linear, nn)
[ ] Not Applicable (i.e., the PR does not include API changes.)

Test quickstart & API (bash tests/docs/test_changed_document.sh)
If any APIs in quickstarts or tutorials are modified, please run this test to check if the current examples can run correctly after the modified APIs are released.

@ericliu8168 Please merge master after #386 is ready.


Metadata API: Rewrite comments

Try to keep dostrings and comments to the point, avoid mentioning
details if they are not necessary or are likely to become outdated
and try to minimize number of comment lines.
Signed-off-by: Jussi Kukkonen<EMAIL_ADDRESS>

Last push: Modified Role docstring based on review

squashed joshuas suggestions (thanks!), then added another commit to improve the DelegatedRole docstring: It explains all of the options that exist in broad terms and expects reader to lookup the details (like what exactly is a "target path hash") elsewhere, and tries to make it clearer that the attributes are mutually exclusive.


db export performance benchmarks?

is there any timing on how long it takes to export 50GB from MySQL to CSV. Or 50GB from Oracle to CSV ?

Hello, @tooptoop4
Do not post a plugin specific issue on this page.
I don't know any page about bulk-out performance.

@tooptoop4 As @hiroyuki-sato commented, this Issues is not for such questions. Also, IIUC, the performance would heavily depend on the machine, file system, MySQL, and Oracle. We have no any number that we can provide for you.
Thanks for your follow-up, @hiroyuki-sato.
Let us close this issue.


Restore "packages" namespace for backwards compatibility

shipped.

I'm afraid this doesn't resolve the problem with many libraries, such as the official Dropbox and Keen clients, which do
from requests.packages.urllib3.poolmanager import PoolManager
This results in
ModuleNotFoundError: No module named 'requests.packages.urllib3'; 'requests.packages' is not a package

I'm trying to find a solution for them too @raicheff. I'm open to suggestions.
Currently, code that was written to import against the requests.packages namespace previously will have to import code that rests at this module-level now.
For example:
from requests.packages.urllib3.poolmanager import PoolManager

Will need to be re-written to be:
from requests.packages import urllib3
urllib3.poolmanager.PoolManager

Or, even better:
from urllib3.poolmanager import PoolManager

If we really want backwards compatibility, we may have to stub out the whole library as an empty imported package. I'm willing to do that, if needed.

solution found!

https://github.com/kennethreitz/requests/commit/c952e9e4e07ebaf579aaf8924ff6f7c61710c8c8

@raicheff care to test against master and see if that solves the issue for you, for the next release?

@kennethreitz Yes, just tested it and it works!

\o/

will cut a release shortly

Thanks Kenneth, that's awesome!
This solution is ugly is hell, but I guess it will do the job for now. I would suggest you add a deprecation warning on import of these modules (similar to how Flask does it with the ext package), and remove it in the next major release.

I came up with a much better solution.

https://github.com/kennethreitz/requests/commit/28666e5d3ae04fede9a9078aba937b0ce6380adc

going to cut a release

shipped 2.16.2!

Tested – works!

With 2.16.2, coala's core tests are down to only one error, in an emulated read timeout test.
https://circleci.com/gh/jayvdb/coala/296
We still have a few other issues which have strangely popped up, and probably some version conflicts for chardet.  Still investigating.

@jayvdb keep us up to date!

@kennethreitz , I haven't found the cause of https://github.com/coala/coala/issues/4282 (and it is 3am so I'm off) , but the workaround was simple : https://github.com/coala/coala/pull/4283

excellent @jayvdb!

@kennethreitz , my workaround shows there is a significant breaking change somewhere.


TreeViewItem focus adorner displayed when item is clicked

The adorner border is displayed incorrectly, this is only when UseLayoutRounding="True".


Refactor Gradle Scripts

The Gradle build scripts have become overly complex and incomprehensible.
Not only this leads to some extra person-hours wasted on introducing any kind of change, but also makes the behavior of some build routines strange and unpredictable.
In order to deal with this issue, we should develop a paradigm (probably a style guide) of writing Gradle scripts, test it upon the TodoList project and propagate to all the Spine modules.

Now, after the introduction of the Bootstrap plugin, we should utilize it as much as we can for this repository.


Parse failed on Babel-loader

I get this error when trying to compile the project.
Module parse failed: Unexpected token (135:23)     File was processed with these loaders:     ./node_modules/react-scripts/node_modules/babel-loader/lib/index.js     You may need an additional loader to handle the result of these loaders.
       const win = typeof window !== 'undefined' ? window : undefined;        if (!win.instgrm?.Embeds) {          const scriptElement = document.createElement('script');         scriptElement.setAttribute('src', '//www.instagram.com/embed.js');
I tried debugging it with no success. Let me know if I can be of help debugging it!
import { EmbedPlaceholder } from 'react-social-media-embed';

@timomak Ahh. This is a complaint about the ?. optional chaining syntax which is a newer JS feature. I'll lower my compilation target to ES2015, that should do the trick. Will have something ready this evening. Thanks for such amazing feedback on this library!

@timomak Alright, I believe I've corrected the issue. Give it a try.
FYI, I'm still working on placeholders for each platform. I've updated the docs here with the latest changes.

npm i react-social-media-embed@latest

Wow, wonderful! Thank you, this embed is super cool!
Found a few more bugs, all hopefully easy to squash. I'll open up a few issues, feel free to message me with a follow up on anything!

Thanks and you’re welcome! Going to put a little more time into this today.
Will try to address those issues best I can, or at least have some workarounds for you.
Centering is a little tricky because the embeds sometimes have a mind of their own. I’ll add some stories to the docs site for centering so you can see the CSS for that. I’ll see if I can get them all to behave.


bootstrap-ansible.sh only installs ceph roles, misses keepalived

What version (commit) do you encounter this issue on?
r12.0.0
What type of issue is this (bug, feature, documentation, regression)?
bug
What is the expected behavior?
bootstrap-ansible.sh should install all external roles, ceph and keepalived
What is actually happening?
bootstrap-ansible.sh only installs the ceph roles and misses the keepalived role
How can we reproduce this issue?
Run ./openstack-ansible/scripts/bootstrap-ansible.sh
Check /etc/ansible/roles
How can we verify your issue is addressed?
Running haproxy-install.yml doesn't run into the following error like it does now, both ceph and keepalived roles are installed
ERROR: cannot find role in /opt/rpc-openstack/openstack-ansible/playbooks/roles/keepalived or /opt/rpc-openstack/openstack-ansible/playbooks/keepalived or /etc/ansible/roles/keepalived
If this is a large issue, what can be done immediately to alleviate the issue while working on a longer-term solution?
Combine the OSA and rpc-openstack ansible-role-requirements.yml files or make sure the bootstrap-ansible.sh script installs from both files
root@infra01:/opt/rpc-openstack# find . -name ansible-role-requirements.yml
./openstack-ansible/ansible-role-requirements.yml
./ansible-role-requirements.yml
What is your evaluation on the importance of this issue, and why?
Low, easily worked around
What branches / milestones do you believe this issue should target?
The list below is what is currently supported for backports
Remove branches (lines) you do not wish to target.

[ ] Master
[ ] liberty-12.1
[ ] liberty-12.0

This is likely because the use of haproxy/keepalived is, as yet, unsupported from an RPC standpoint as far as I know. I think it's on the roadmap, but hasn't become a supported configuration yet from a development team standpoint.

That might be, but pre-Liberty the haproxy-install.yml playbook worked just fine in rpc-openstack. With Liberty and the move to ansible-role-requirements.yml files for the external roles, it doesn't. IMO it's still something that should be fixed, since before Liberty this worked.
With my test I didn't even want to use keepalived, I was testing with one haproxy host, but currently that won't even finish unless you manaully cd /opt/rpc-openstack/openstack-ansible/; ansible-galaxy install --force --role-file=ansible-role-requirements.yml to get the keepalived role.

It does, in fact, work exactly as it did before as long as you only have one haproxy host. The keepalived role is only used when more than one haproxy host is configured. This matches the exact same functionality as it always has.

That's not correct. I only had one haproxy host in my openstack_user_config.yml file and it still errored out for the keepalived role not being present.

I just ran into this error as well on a Liberty 12.1.0 deployment that is not even using or has ever used haproxy:
root@XXXXXX-ocp:/opt/rpc-openstack/openstack-ansible/playbooks# openstack-ansible setup-infrastructure.yml
Variable files: "-e @/etc/openstack_deploy/user_extras_secrets.yml -e @/etc/openstack_deploy/user_extras_variables.yml -e @/etc/openstack_deploy/user_secrets.yml -e @/etc/openstack_deploy/user_variables.yml "
ERROR: cannot find role in /opt/rpc-openstack/openstack-ansible/playbooks/roles/keepalived or /opt/rpc-openstack/openstack-ansible/playbooks/keepalived or /etc/ansible/roles/keepalived

Also came across this with the opposite scenario. keepalived role was installed and ceph roles were not. Even though I do not have any ceph hosts in this environment, it's still looking for the ceph roles. Ideally for this entire scenario, the playbooks would only need the required roles based on what you have in the openstack_user_config.yml file.
root@infra01:/opt/rpc-openstack/rpcd/playbooks# openstack-ansible site.yml
Variable files: "-e @/etc/openstack_deploy/user_extras_secrets.yml -e @/etc/openstack_deploy/user_extras_variables.yml -e @/etc/openstack_deploy/user_secrets.yml -e @/etc/openstack_deploy/user_variables.yml "
ERROR: cannot find role in /opt/rpc-openstack/rpcd/playbooks/roles/ceph.ceph-common or /opt/rpc-openstack/rpcd/playbooks/ceph.ceph-common or /opt/rpc-openstack/openstack-ansible/playbooks/roles/ceph.ceph-common or /etc/ansible/roles/ceph.ceph-common
root@infra01:/opt/rpc-openstack# ls -la /etc/ansible/roles/
total 20
drwxr-xr-x  5 root root 4096 Jun  1 14:43 .
drwxr-xr-x  3 root root 4096 Jun  1 14:43 ..
drwxr-xr-x  9 root root 4096 Jun  1 14:43 keepalived
drwxr-xr-x 12 root root 4096 Jun  1 14:43 openstack-ansible-security
drwxr-xr-x  9 root root 4096 Jun  1 14:43 sshd


Server side rendering

Watched the demo and it was pretty good!
I am curious if you've thought about adding a way of rendering the views server-side instead of using Svelte? For example, using Go's templating system. I realize you lose out on the component capabilities of today's FE frameworks, but as someone who prefers server-side rendered apps, I think this would be a good feature to support. As mentioned it can be another variation that bud supports in addition to svelte, React and others.

Hey @josebalius, thanks opening this issue. SSR rendering works out of the box already!
This was hard to do, but I couldn't live with the tradeoff of choosing between a modern FE frontend and performance, SEO, web standards.
I should have shown it in the demo, but if you go through the HN demo, try running curl :3000 and you'll be overwhelmed with HTML soup!


SFC in-source testing

Clear and concise description of the problem
would't be nice to test Vue sfc's in-source also? just like the Vitest in-source testing on normal javascript/typescript functions?
Suggested solution
Add an extra <script lang="ts" test> tag or something to write the unit tests about that specific component.
Alternative
No idea how this could be implemented, But though that this could be nice to have.
Additional context
<script setup lang="ts">
defineProps<{
  msg: string
}>()
</script>

<template>
  <p>{{ msg }}</p>
</template>

<script lang="ts" test>
import { mount } from '@vue/test-utils'
import { describe, it, expect } from 'vitest'

describe('test.vue', () => {
  it('renders properly', () => {
    const wrapper = mount(/* Somehow get the right component here */ HelloWorld, { props: { label: 'Hello Vitest' } })
    expect(wrapper.text()).toContain('Hello Vitest')
  })
})
</script>

Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

I don't think this is something to discuss in this repo. I would recommend opening an issue in @vue/test-utils project to discuss how this can be implemented (with a simple Vite plugin, for example). This will definitely be implemented as a core Vitest feature though.


Sponsor app

We need an app that shows a simple slideshow of images of sponsor logos. Or cat pictures, given the sponsor logo list hasn't been finalised. I've started on this using the st7789 display backend, but it may become unwieldy given the st7789 code only allows uncompressed images to be embedded in ROM.

First cut in 9cd1e6b3e03cb7a567df9e65d6f0ce9a81908df0. 3 fullscreen 8-bit uncompressed images have added about 100KB to the ROM size. We have about 0.6MB left so a max of 21 images (and no more code...) before we have to start compressing them (or offloading the sponsor app into the hatchery, or reducing the VFS partition size, etc)

Done!


function is treated as string in Java Rhino

Description of the Issue and Steps to Reproduce:
I am using momento in a java script which I am running u sing Java Rhino. When using format functionality of momento, it's not giving expected output. I had narrowed down the issue to the following code:
function addFormatToken (token, padded, ordinal, callback) {         var func = callback;         if (typeof callback === 'string') {             func = function () {                 return this[callback]();             };         }         if (token) {             formatTokenFunctions[token] = func;         }         if (padded) {             formatTokenFunctions[padded[0]] = function() {             return zeroFill(func.apply(this, arguments), padded[1], padded[2]);             };         };         if (ordinal) {             formatTokenFunctions[ordinal] = function () {                 return this.localeData().ordinal(func.apply(this, arguments), token);             };         }     }
The function function() { return zeroFill(func.apply(this, arguments), padded[1], padded[2]); };  is treated as string and so I am getting this as output.
I am using moment version 2.14.1 and Mozilla Rhino version 1.7.6

Can someone please respond to the issue I reported?

I don't see an issue reported. An issue looks like "I expect this code to return [something] but it instead returns [some other thing]". I don't know what to do with "here is some Moment code that I believe is responsible for some unstated unexpected output". Please create a new issue with a succinct description of the problem.


Add /blocks API

Note that all the fields have been added yet. Just some useful ones that seemed important for bdk.

thanks @tnull I addressed all comments I believe.

LGTM, feel free to squash.

I squashed the commits. Sorry about the epic wait on this one.

...the CI seems to be stuck.

Hi @LLFourn, can you rebase the changes on master and force push? That will re-run the CI jobs and I'm not able to re-run them from my end.

This will need to be rebased once #31 goes in, I think it will fix the test reliability.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

46 of 47 (97.87%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.9%) to 81.013%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/async.rs
12
13
92.31%

Totals

Change from base Build<PHONE_NUMBER>:
0.9%

Covered Lines:
832

Relevant Lines:
1027

💛  - Coveralls


CI Failing due to NIX container (nixos/nix:latest) upgrade in dockerhub

It looks like the github NIX :latest action got upgraded and it now gets the following error:
error: experimental Nix feature 'nix-command' is disabled; use '--extra-experimental-features nix-command' to override

I saw this during local testing. Fix should be simple.

Upstream fixed it by locking the container version. See https://github.com/containers/crun/commit/62e84d860cf36935adbd84b1bec3abe756167452. We will do the same thing.


1573/Tooltip for password requirements

Closes this issue.

Code Changes

[ ] Add tooltip on password field for password requirements.

Steps to Confirm

[ ] list any manual steps taken to confirm the changes

Pre-Merge Checklist

[ ] All CI Pipelines Succeeded
Documentation Updated:

[ ] documentation complete, or draft/outline provided (tag docs-team to complete/review on this branch)
[ ] documentation issue created (tag docs-team to complete issue separately)

[ ] Issue Requirements are Met
[ ] Relevant Follow-Up Issues Created
[ ] Update CHANGELOG.md

Description Of Changes
Write some things here about the changes and any potential caveats

@malaethyca - The issue wasn't clear in what way you would like the user to be informed about the password requirements, so I opted for a tooltip since that is native to our custom components. The screencap above shows it in action. Let me know what you think.

Hi folks, apologies for the last minute intervention here, but please don't merge this until we've had a conversation about the requirements.
https://github.com/ethyca/fides/issues/1573#issuecomment-1307346227

Hi folks, thanks for your patience, I'm happy to unblock this PR based on my comment here: https://github.com/ethyca/fides/issues/1573#issuecomment-1309205102


Fix collapsible items in list fragment malfunction

What this PR does / why we need it:
Collapsible items in list fragment were entirely clickable, making them behave somewhat abnormally. Reducing the size of clickable area to only the title of each article (in list fragment) and ignoring clicks on the link seems to have cleared the issue.
Which issue this PR fixes:
fixes #472

Awesome. Thanks for diving deeper and finding the actual problem.


Production build still contains un-used bundle

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Add analyze package
Build for Analyze

Expected behavior
There shouldn't be @floating-ui here.
I would suggest turn on sideEffect=false to support tree sharking
Screenshots

Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

I met this problem as well, my temp solution is this
const DevClickToComponent =
  process.env.NODE_ENV === 'development'
    ? require('click-to-react-component').ClickToComponent
    : () => null;

<DevClickToComponent />


Add spring cloud kubernetes to properties appendix

Can you PLS create a documentation of all possible application properties?
I.e. something like: Appendix A. Common application properties from Spring documentation.
PS: Spring Cloud Kubernetes is very helpful - thumbs up!

It should be a part of it, is it not?

It is not.
Try to search in  Appendix A. Common application properties for e.g.: spring.cloud.kubernetes

Sorry on mobile

We don't put them with boot, but with the spring cloud docs

https://cloud.spring.io/spring-cloud-static/Greenwich.RELEASE/multi/multi__appendix_compendium_of_configuration_properties.html

Thank you! I did not find these - there is a a lot of stuff.
Anyway: spring.cloud.kubernetes is not there :(

@spencergibb thanks!

This should be fixed by https://github.com/spring-cloud-samples/scripts/commit/1a044f978b47addb0e8d8bd1987d33db88b9b757


FIX: Add basic/temporary API documentation (i.e. API design and API call requests and responses) to API templates repo readme

This pull request makes the following changes

Fixes code-collabo/node-mongo#35

General checklist

[x] File or folder now contains changes as specified in the issue i worked on
[x] I have linked the issue I worked on to this pull request submitted by me

Testing checklist

[x] The readme of the API boilerplates repo now contains the temporary documentation API design and API call requests and responses
[x] The temporary API doc is added just before the Documentation section of the API boilerplates repo's readme
[x] The temporary API doc is written accordingly and correctly for all methods (GET, POST etc) and the /demo (and demo id) endpoints that exist in the API
[x] The same formatting, headers, tables, dropdowns, code blocks etc from the buuks repo example is used
[x] I certify that I ran my checklist

Ping @code-collabo/node-mongo-api-boilerplate-templates

I have just updated the node-mongo-template api documentation as stated in the issue. do check it out.