docs: fix missing char conversion

Thank you for contributing to PyO3!
By submitting these contributions you agree for them to be dual-licensed under PyO3's MIT OR Apache-2.0 license.
Please consider adding the following to your pull request:

an entry for this PR in newsfragments - see [https://pyo3.rs/main/contributing.html#documenting-changes]

or start the PR title with docs: if this is a docs-only change to skip the check

docs to all new functions and / or detail in the guide
tests for all new or changed functions

PyO3's CI pipeline will check your pull request. To run its tests
locally, you can run nox. See nox --list-sessions
for a list of supported actions.

Very curious that the pipeline is failing. the commands are running on my local

Yes, seems like just some flakiness 😭

Ugh, I've asked upstream at https://github.com/rust-lang/rustup/issues/3530


Adds env parameter on the schedule creation - [opened]

Merges mg-env-values -> master
Migrated from GitLab: https://gitlab.com/meltano/meltano/-/merge_requests/2406

This MR adds env parameter creation on the non official web api
Merge Request Checklist

[ ] Link to an issue
[ ] Include the proposed fix or feature
[ ] Include and update tests for the modified code
[ ] Include a documentation change
[ ] Add a CHANGELOG.md entry in the Unreleased section for any user-facing changes
[ ] Mention or assign a maintainer

Slack thread: https://meltano.slack.com/archives/C013Z450LCD/p1644970657831679

Closing as stale.


Can we disable Dragend?

Instead of destroying it, can we just disable it and resume it later?

Bumping this, this functionality would be amazing to have.

I agree. Destroy is far too committing for situations where one needs to instantiate and destroy in a cyclical way.

Well I have the same issue, please make multiple intiation possible, or tell us what to do?

You can try this :
disable: function() {                 var a = this.container;                 n(a, q, this._onStart);             },
By the way @Stereobit your non minified file (dragend.js) doesn't match your minified file (dragend.min.js), but it's a great and very useful piece of code :)

Thanks @badoubadou I will try it if I need it again.

Bumping this. I'm using a toggle for scroll or swipe action (both web and mobile). It works once if you toggle from scroll to swipe which initiates dragend and then back to scroll if you destroy dragend which is needed as the swipe and scroll work on the same elements.
But then if you toggle back it no longer works so disable would be a great option in this case.
Also, as an aside, the destroy method in the docs did not work for me, I used destroy: true as an option and that works.


Be sure to log the change's success

Before we weren't sending create back to trogdir so it kept saying
"pending" when it should have been success.

:+1:


Maven shade plugin support for SpringFox

What kind of issue is this?
Please tell us if your spring fox plugin can be supported by using the Maven shade plugin.

[ x] Question. Is this a question about how to do a certain thing? YES

We would like to have support for spring fox swagger plugin using AWS lambda.
https://github.com/awslabs/aws-serverless-java-container/issues/105#issuecomment-362681054

Not sure what would need to happen here in this library. Plus shading the library isn't really doing to buy you much because all the spring/jackson dependencies are provided dependencies except for a select few.


chore: export confirmPayment directly

Resolves #318

Closing this in favor of https://github.com/stripe/stripe-react-native/pull/354


Prevent fetching topics list if we already have them

Fixes : #2750
The Problem - Topics list was fetched for the current stream each time the TextInput was focussed, irrespective of if we have fetched the data before or not. Take a look at #2750 for more...
Video of the problem -
https://user-images.githubusercontent.com/36705866/102719650-2e97b300-4315-11eb-90d4-c6a4a15fcb39.mov
Fix - Now we fetch data only once for a specific stream. The query is made each time we move to a different stream
After fixing-
https://user-images.githubusercontent.com/36705866/102719838-68b58480-4316-11eb-90f1-b5e7b3a45f78.mov

Thanks, @shaurya2612!
I think there might be a slightly simpler way to fix this, one that doesn't involve storing something in state. Would it work if we fetched unconditionally (for stream narrows anyway) at the start, probably in componentDidMount, and then fetched again in componentDidUpdate if the stream has changed?

@chrisbobbe thanks for your perusal
Working on it now!

@chrisbobbe I omitted the state variable and achieved the same functionality with ComponentDidMount and ComponentDidUpdate as you mentioned.
Thanks a lot !

Great, thanks, @shaurya2612! I've had a few more thoughts after looking a bit closer.

It occurred to me that, without frequently re-fetching the topics, the list of topics might get to be unhelpfully out-of-date. New messages that come into the stream might have topics we haven't seen before, and we'll want those to show up in the list.
Thankfully, I found that this is already handled. The list of topics mentioned in #2750 is rendered in the TopicAutocomplete component, which takes its data from the topics key in the Redux state; TopicAutocomplete subscribes to its data with a call to react-redux's connect. The effect is that TopicAutocomplete updates whenever the list of topics for the stream (i.e., the list of topics at state.topics[streamId] for the appropriate streamId) changes. (The data fetched by fetchTopicsForStream also gets stored in state.topics [1].)
So, we just need to be sure that state.topics[streamId] (for the appropriate streamId) is also updated when a new message, with a potentially new topic, is received. This is already the case: src/topics/topicsReducer.js, which is responsible for updating state.topics, does indeed handle EVENT_NEW_MESSAGE, and it does so by updating the list of topics for the new message's stream.
So, when a new message with a potentially new topic is received, the list of topics will indeed be kept up-to-date, and we don't need to do anything further about it.

One thing I also noticed in the above investigation is that the code that's fetching the topics, in ComposeBox, is quite far away from the code that's interested in the fetched topics, in TopicAutocomplete. Let's move it closer: I think the code that calls fetchTopicsForStream could helpfully be moved from ComposeBox to TopicAutocomplete. That'll also help keep the complexity of ComposeBox down; there's already quite a lot of code in that file.

Also, I think we don't actually need to re-fetch the topics when the stream changes; i.e., the componentDidUpdate from my suggestion above should probably just be removed. The reason I say so is that we don't expect the stream to actually change, and it would pretty much be a bug if it did. ComposeBox (and TopicAutocomplete, which it renders unconditionally) are descendants of ChatScreen, and a ChatScreen receives (and is meant to receive) a single narrow which will direct its behavior through its entire lifetime, from the time it's "born" with a call to navigateToChat containing the requested narrow in the navigation params. [2] Including the componentDidUpdate would only add confusion, I think; it would distort a reader's idea of what we normally expect to happen.

[1] I saw that the fetchTopicsForStream thunk action does the data fetch, then I command-clicked through fetchTopics to its definition and saw that it dispatches an INIT_TOPICS plain-object action with the topics it's just learned about; I then did a whole-project search for case INIT_TOPICS, which showed that src/topics/topicsReducer.js, the reducer for the topics key, is the only thing that handles INIT_TOPICS, and it does so by storing the newly received topics.
[2] There's a small wrinkle in getTopicsForNarrow, where it looks like we'll drop the list of topics if someone changes the stream name—but that's something we're tracking and will be fixed with #4333.

Also, please be sure to run tools/test and fix any/all issues it tells you about (with the current revision, it identified a few issues with the lint and prettier tests; the former can be fixed manually, and the latter should be fixable automatically with tools/fmt which is mentioned in this doc).
Also, I think everything should be squashable into a single commit, which would be good to do in keeping with our commit discipline. We have a handy guide for revising your local branch ("rewriting history" for the PR branch, so you don't need to make a new PR) here. 🙂

Thanks @chrisbobbe !
I've made the necessary changes and ran the tests as well. Please let me know what you think of these.

Thanks, @shaurya2612!
Merged, with a few tweaks to the commit message; please take a look 🙂 (and see our doc on our preferred commit-message style):

I've added some more detail to the commit message.
Formatted the summary line with a prefix; I chose ComposeBox, since that's the site where we're removing the troublesome too-frequent fetch.
Kept the line-wrapping of the body to about 68 characters (I've got my editor set to do this semi-automatically).
Added Fixes: #2750 at the end.

I also expanded on the code comment you added, so there's more context on the important fact you mention (that "state.topics is updated on EVENT_NEW_MESSAGE actions").
(
And I added some quick TODOs from the discovery in https://github.com/zulip/zulip-mobile/pull/4351#issuecomment-749099486:

[2] There's a small wrinkle in getTopicsForNarrow, where it looks like we...won't show the list of topics if someone has changed the stream name—but that's something we're tracking and will be fixed with #4333.

)


(Bug) Error requesting phone validation

add send non-encrypted email from verify otp form for the case if weneed to re-create mautic contact

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
About #2554
How Has This Been Tested?
Please describe the tests that you ran to verify your changes.
Checklist:

[x] PR title matches follow: (Feature|Bug|Chore) Task Name
[x] My code follows the style guidelines of this project
[x] I have followed all the instructions described in the initial task (check Definitions of Done)
[x] I have performed a self-review of my own code
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I have added reference to a related issue in the repository
[x] I have added a detailed description of the changes proposed in the pull request. I am as descriptive as possible, assisting reviewers as much as possible.
[ ] I have added screenshots related to my pull request (for frontend tasks)
[ ] I have pasted a gif showing the feature.
[x] @mentions of the person or team responsible for reviewing proposed changes

this was not requested


Adding Add Web Library

Adding eact-add-to-homescreen library and using it in the app
Updating manifest and service worker register to make the app installable on android and desktop.
Updating serviceWorker.js to make it installable in all environments
Adding flow according to designs

Extra:
https://www.screencast.com/t/gKfwDY11gE

Screenshots

iOS explanation is not matching the designs since this would take a little longer and I wanted to close this with time for reviewing.

lets show it in dashboard

2. We need for android also. read somewhere we need to register a service worker in order for the add to home screen prompt to work

@dminones, Indeed, it does nothing on android right now. Check this: https://developers.google.com/web/fundamentals/app-install-banners/#mini-info-bar
The criteria states all the requirements, including the one about service worker.

@sirpy @fernandomg just added the necesary fields on manifest to make it installable. Also updated serviceWorker.js to make it installable in all environments (removing production condition from the if sentence).
This will make the service worker available on local env too, which I think it's ok. We could add an env variable if this causes any problem.
https://webdesign.tutsplus.com/tutorials/5-essential-tips-for-service-worker-development--cms-31424

I just see you print to console beforeinstallprompt
I dont see where you actually request to show the add to home on android.

by setting up all the requirements browser should ask.

I just see you print to console beforeinstallprompt
I dont see where you actually request to show the add to home on android.

@sirpy, this is working... with the mini-info bar displaying when accessing the page (https://developers.google.com/web/fundamentals/app-install-banners/promoting-install-mobile#automatic_browser_promotion).
One thing is that it's handled by the browser, but we can manage it to implement a different pattern as suggested in docs (see the same link above, it elaborates on different patterns)
Also, I like this suggestion to display the mini-info bar or whatever other way to ask the user to install the app, after the signup flow is done:

You may want to wait before showing the prompt to the user, so you don't distract them from what they're doing. For example, if the user is in a check-out flow, or creating their account, let them complete that before interrupting them with the prompt.

@dariominones, what you think?

@fernandomg @dariominones
Yeah for android we should have the same behaviour, show it in dashboard.

@dariominones why in app.js? we need it when dashboard is shown
I think i've read the recommended way is to hold the "e" event and then call e.prompt() when you want to trigger it.
did you test it on android?

@sirpy, yes, that's correct. Will change the implementation to match this, I was just making some tests since testing this locally it is a problem.
Will use this guide. https://blog.anam.co/progressive-web-apps-with-create-react-app/

@dariominones doesnt match the design. the instructions for iphone are not in the popup, they should be in an overlay above the toolbar share button


Support nontrivial default arguments in internal nimFunctions

It appears that matchAndFill.call happens at a later stage than it should, so that our internal functions like nimArray and nimRound cannot have nontrivial default arguments. For example while implementing nimOptim, I have attempted and failed to set the lower and upper arguments to any of the following:

c(Inf) - somehow this misses a C++ codegen phase and ends up as c(Inf) in C++.
nimC(Inf) - ends up as an Eigen type from concatenate_impl rather than the desired NimArr
nimRep(Inf, 1) - crashes during RCfunction_compile
nimNumeric(1, Inf) crashes during RCfunction_compile

I'll take a look at this.  It is one of the earliest passes over the code, the only earlier step being conversions from c to nimC and so on.  That explains failure of c(Inf).  We haven't used expressions as defaults before, but it makes sense to do so.   Typically a size processor that can't handle an eigenizable argument (toEigenize is "yes") and needs to be lifted to an intermediate / temporary variable using sizeInsertIntermediate.

Hmm these failures may actually be caused by improper construction of ExprClasses$args due to one of the arguments being gr = list(NULL). It looks like by the time we get to sizeOptim, code$ars =
$par
ARG1_par_

$fn
rcFun_5
                    <--- gr has been omitted
$method
NULL

$lower
[1] "Nelder-Mead"

$upper
-
  Inf

$control
[1] Inf

$hessian
nimOptimDefaultControl

[[8]]
[1] 0

I think this is due to the kind of behavior I was describing earlier on the whiteboard: assignment of NULL into lists when not done carefully has the effect of removing the target element from the list.  I suspect at some step that is how gr was removed from the args.  For practical purposes you may want to avoid NULL until we make it work systematically, or if you really need it you can check and put it back in.

Closing because this appears to be misattributed.


fix: chat scroll on new message and on mount

Resolves #124
TODO:

[x] scroll on new message
[x] scroll on mount

Scroll on new message and scroll on mount both look good to me, the only thing I'd probably add is scrolling when a message is sent but the view is not currently scrolled all the way down. So if you open the chat, scroll up a bit and send a message, it currently doesn't scroll down.

Unfortunately for me it does not work correctly in Firefox :thinking:

@agazso it works for me on Firefox 114.0.2 (64-bit) on macOS . Maybe you have some older version?

I was debugging this a bit and if I remove the autoscroll from the if condition check in the afterUpdate then it works correctly both on Firefox and Chromium. Then the beforeUpdate is not needed.

It works for me on firefox as well but I have the exact same setup as Vojtech

This is a bit jumpy on safari as I type. I'll merge as is and we can tackle it in a separate PR.


Make it easier to extend in external apps

The use of private everywhere makes it easier for you to refactor and keep an API boundary, but does cause some annoyance while trying to customize usage in other packages. In particular, I wanted to make a custom Client in an external repo that supports some more message types, as https://github.com/cosmos/cosmjs/pull/690 is hanging, at it would be good to add such functionality without depending on the CosmJS core team (this is even more critical for all other wallet/app creators). I also wanted to adjust things like getBalance to use the unverified variant (so it didn't take so long to list tokens).
So, I tried to start doing it as follows:
import { SigningCosmWasmClient } from "@cosmjs/cosmwasm-stargate";

// This wraps the singing client to support extra messages
// and allow us to customize things like query delay
export class SigningClient extends SigningCosmWasmClient {

}

But got the error:
Cannot extend a class<EMAIL_ADDRESS>Class constructor is marked as private.ts(2675)

I'd love your opinions here, or maybe a CosmJS dev could take a look at https://github.com/confio/wallet/pull/70 and see if they have an idea on how to approach this without touching the cosmjs repo. We should let app devs customize quite a bit, they will want to.

The easiest way to support what you want to do but maintain some level of control over which methods are for public use is to switch to protected: https://www.typescriptlang.org/docs/handbook/classes.html#understanding-protected

I'm happy with protected here. I think it is important that users use the public static instance makers. But subclassing should be fine.
You then probably also want access to some fields like e.g. the Tendermint client.

You then probably also want protected access to some fields like e.g. the Tendermint client.

That would be nice. If you want to support subclassing. If you have another approach for extending the signing client, I am open to that as well

Looking at the changes in https://github.com/cosmos/cosmjs/pull/726/files, I think we should keep the fields private and

Make contructor protected for StargateClient, SigningStargateClient, CosmWasmClient, SigningCosmWasmClient
Make Tendermint optional for CosmWasmClient, SigningCosmWasmClient and create an offline constructor for SigningCosmWasmClient
Add protected getTmClient/getQueryClient and protected forceGetTmClient/forceGetQueryClient to StargateClient and CosmWasmClient, where the first two return an optional value.


user message formatting as logger param instead of string concatenation

Ⅰ. Describe what this PR did
This PR is just replace the parameters from string concatenation to message formatting
LOGGER.error("rpcContext is null,channel:" + channel + ",active:" + channel.isActive());
change to:
LOGGER.error("rpcContext is null,channel:{},active:{}", channel, channel.isActive());
Ⅱ. Does this pull request fix one issue?
no
Ⅲ. Why don't you add test cases (unit test/integration test)?
It could be verified by code review
Ⅳ. Describe how to verify it
code review and the actual logs
Ⅴ. Special notes for reviews

Codecov Report

Merging #1726 into develop will decrease coverage by 0.13%.
The diff coverage is 10%.

@@              Coverage Diff              @@
##             develop    #1726      +/-   ##
=============================================
- Coverage      47.01%   46.87%   -0.14%
  Complexity      1786     1786
=============================================
  Files            365      365
  Lines          13301    13300       -1
  Branches        1644     1617      -27
=============================================
- Hits            6253     6234      -19
- Misses          6370     6371       +1
- Partials         678      695      +17

Impacted Files
Coverage Δ
Complexity Δ

...rc/main/java/io/seata/core/rpc/ChannelManager.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...java/io/seata/core/rpc/netty/RpcClientHandler.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...ata/core/rpc/DefaultServerMessageListenerImpl.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...eata/core/rpc/netty/NettyClientChannelManager.java
71.17% <40%> (+0.63%)
22 <0> (ø)
:arrow_down:

...obuf/convertor/BranchRegisterRequestConvertor.java
88% <0%> (-8%)
3% <0%> (ø)

...buf/convertor/GlobalLockQueryRequestConvertor.java
92.59% <0%> (-7.41%)
3% <0%> (ø)

...obuf/convertor/GlobalRollbackRequestConvertor.java
94.73% <0%> (-5.27%)
3% <0%> (ø)

...otobuf/convertor/GlobalStatusRequestConvertor.java
94.73% <0%> (-5.27%)
3% <0%> (ø)

...otobuf/convertor/GlobalCommitRequestConvertor.java
94.73% <0%> (-5.27%)
3% <0%> (ø)

...protobuf/convertor/RegisterTMRequestConvertor.java
95.45% <0%> (-4.55%)
3% <0%> (ø)

... and 8 more

Continue to review full report at Codecov.

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


Missing icon "ticket-outline" from ionicons

Environment
OS: Windows 11,
platform: IOS & Android,
version: 9.0.0,
Description
When im trying to add this icon "ticket-outline" from ionicons, im just getting this warning:
"ticket-outline" is not a valid icon name for family "ionicons"

Did you solve this problem ??

I created this PR to update to the latest version of Ionicons #1484 .
While waiting for it to be merged, you can use this in your package.json
"react-native-vector-icons": "mrkpatchaa/react-native-vector-icons#ionicons-v6"
I hope this helps.


Use wrong Storage version for Asp.net core 2.2

Before you open an issue
If the issue is with an ASP.NET Core document, open the issue with the Content feedback button at the bottom of that document page.
If the issue is:

A simple typo or similar correction, you can submit a PR. See the contributor guide for instructions.
A general support question, consider asking on a support forum site.
A site design concern, create an issue at MicrosoftDocs/Feedback.
A problem completing a tutorial, compare your code with the completed sample.
A duplicate of an open or closed issue, leave a comment on that issue.

Issue description
Asp.Net Core 2.2 uses the Microsoft.WindowsAzure.Storage package for management of Azure Storage, and Microsoft.Azure.Storage package is used in Asp.Net Core 3.0 or higher.
So the example of creating StorageCredentials in the doc is for Asp.Net Core 3.0 or higher. And in section Asp.Net Core 2.2, it needs modify.
Is that right?
Software versions
Check the .NET target framework(s) being used, and include the version number(s).

[ ] .NET Core
[ ] .NET Framework
[ ] .NET Standard

If using the .NET Core SDK, include dotnet --info output. If using .NET Framework without the .NET Core SDK, include info from Visual Studio's Help > About Microsoft Visual Studio dialog.

dotnet --info output or About VS info
<replace>

Can you create an issue from the doc page? That will connect the doc to the issue. Go to the bottom of the page and select This page .

Also, be more specific of what is wrong on the page.


Yarn warns about unmet peer dependencies

Description
When running create-react-app 0.7.0 with Yarn installed, Yarn prints a warning about unmet peer dependencies. However, despite the warning the app is created successfully, it works and subsequent yarn install commands don't show this warning.
Expected behavior
No warnings about peer dependencies should be printed when running create-react-app.
Actual behavior
Following warnings are printed:
> create-react-app my-app-yarn
Creating a new React app in /Users/ville/Projects/sandbox/my-app-yarn.

Installing packages. This might take a couple minutes.
Installing react-scripts...

yarn add v0.17.10
info No lockfile found.
[1/4] 🔍  Resolving packages...
warning react-scripts > jest > jest-cli > istanbul-api > fileset ><EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
warning Unmet peer dependency<EMAIL_ADDRESS><4.0.0".
warning Unmet peer dependency<EMAIL_ADDRESS>warning Unmet peer dependency "webpack@1 || ^2.1.0-beta".
warning Unmet peer dependency<EMAIL_ADDRESS>warning Unmet peer dependency<EMAIL_ADDRESS>warning Unmet peer dependency<EMAIL_ADDRESS>warning Unmet peer dependency<EMAIL_ADDRESS>warning Unmet peer dependency<EMAIL_ADDRESS>warning Unmet peer dependency<EMAIL_ADDRESS>warning Unmet peer dependency<EMAIL_ADDRESS>warning Unmet peer dependency<EMAIL_ADDRESS>warning Unmet peer dependency<EMAIL_ADDRESS>|| 3.x".
warning Unmet peer dependency "webpack@1 || ^2.1.0-beta".
warning Unmet peer dependency<EMAIL_ADDRESS>- 3.x".
warning Unmet peer dependency<EMAIL_ADDRESS>|| ^3.0.0".
warning Unmet peer dependency "file-loader@*".
warning Unmet peer dependency<EMAIL_ADDRESS><3".
warning Unmet peer dependency "webpack@1 || ^2.1.0-beta".
[4/4] 📃  Building fresh packages...
success Saved lockfile.
success Saved 750 new dependencies.
...

Environment
> node -v
v6.9.1
> npm -v
3.10.8
> yarn --version
0.17.10

Operating system: macOS 10.12.1
Browser and version: N/A

Also this on the second stage:
yarn add v0.17.6
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
warning Unmet peer dependency<EMAIL_ADDRESS>

Looks like a bug in Yarn – it doesn't consider the packages installed at the same time when looking for peer dependencies. I tried this (without using create-react-app):
> mkdir test
> cd test                                                                                ville@k9:test> > yarn init -y
yarn init v0.17.10
warning The yes flag has been set. This will automatically answer yes to all questions which may have security implications.
success Saved package.json
✨  Done in 0.04s.
> yarn add react react-dom
yarn add v0.17.10
info No lockfile found.
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
warning Unmet peer dependency<EMAIL_ADDRESS>

I created an issue in Yarn: https://github.com/yarnpkg/yarn/issues/2132

I guess I'll close since this is a known issue in Yarn, and keeping it open here doesn't change anything. We still track it in the umbrella task. https://github.com/facebookincubator/create-react-app/issues/1189


receiver project v2.6.1 installer broken

The installer is broken, only offering 1909 mutability install and then errors out in the flightaware piaware install

same error code as previous post

Are you running on Ubuntu 17+?If so I removed the option to install dump1090-fa/PiAware due to issues not allowing piaware_puilder to successfully compile the applications. Please refer to the following issues pertaining to the reason the option to install these applications were removed.
https://github.com/jprochazka/adsb-receiver/issues/435
https://github.com/flightaware/piaware/issues/41
https://github.com/jprochazka/adsb-receiver/issues/435
Dump1090-fa/PiAware will be added again as an option for Ubuntu 17+ once a proper fix has been created. Keep in mind dump1090-fa/PiAware are available for install on Debian.


Fails validation when using global parameters

This GitHub Action fails when global parameters are referenced from within a pipeline. The validation step of the action doesn't seem to be able to find the global parameter anywhere. In failing validation, no ARM templates are generated.

Hi! any news on this? Thanks!

Not sure.
I see there's been some releases in this space but have yet to rebuild or test anything.
Cheers,
Kevin
From: Joan Teixidó @.>
Sent: 05 September 2022 09:25
To: Azure/data-factory-export-action @.>
Cc: Kevin Moore @.>; Author @.>
Subject: Re: [Azure/data-factory-export-action] Fails validation when using global parameters (Issue #1)
Hi! any news on this? Thanks!

Reply to this email directly, view it on GitHubhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fdata-factory-export-action%2Fissues%2F1%23issuecomment-1236689917&data=05|01|kevin.moore%40nhs.scot|5753a403b2fa4534754308da8f181db4|10efe0bda0304bca809cb5e6745e499a|0|0|637979630984913806|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=0xvpAKkAzuDucB1hnPZWV0AAkJ2ZFmBv51Ji9pEmf0g%3D&reserved=0, or unsubscribehttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAXITSCVV4Y43ITZYVPONFNTV4WU5JANCNFSM5TH2J7KA&data=05|01|kevin.moore%40nhs.scot|5753a403b2fa4534754308da8f181db4|10efe0bda0304bca809cb5e6745e499a|0|0|637979630984913806|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=0TYbIl8HIDpLsJ91R5E%2BJPTDxFYxBkNgd317dI7mrCY%3D&reserved=0.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>
This email is intended for the named recipient only. If you have received it by mistake,
please (i) contact the sender by email reply; (ii) delete the email from your system; .
and (iii) do not copy the email or disclose its contents to anyone.

no changes about this issue in the last version published in NPM (1.0.0) same problem happens...

I was running into the same issue and got it to work in the end.  It seems that the ID is not optional if you are using global parameters, adding in my source ADF ID resolved this issue.

hi @Whowong, could you explain what do you mean with "the ID is not optional"?
Thanks!

@joanteixi
Below is an excerpt from the readme:
Inputs
path (optional): Directory that contains all Data Factory resources. Defaults to ./ directory.

id (optional): Data Factory resource ID. Defaults to /subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/resourceGroup/providers/Microsoft.DataFactory/factories/dataFactory.

It mentioned that the ID is optional which seems to be true for many things.  However, it seems to need the DataFactory Resource ID when the global parameters are involved.  I was able to get this to work once I included my dev environment Data Factory ID.
This is how I am using it in my pipeline:
  - name: Export ARM Template
    id: export
    uses<EMAIL_ADDRESS>    with:
      id: ${{ secrets.ADFDevResourceID }}

Hi!!
thanks for your answer, unfortunately I'm using Azure Devops to deploy it, and the ID is always present calling the script.
Thanks!


Clean up a bunch of unnecessarily hard-coded user ids in tests

These are really prep commit for #17520 but should be worth merging independently

Merged, thanks @mateuszmandera!


first LZA deployment fails on Accelertor-Pipeline

Describe the bug
I have created a new AWS Account, enabled there AWS Control Tower and launched LZA cloud formation stack.
It stopped in AWSAccelerator-Pipeline, in stage Prepare on error:
AWSAccelerator-PrepareStack-339713112183-us-east-1 |  86/102 | 8:15:40 AM | CREATE_IN_PROGRESS   | AWS::IAM::Policy                                   | CreateCTAccounts/CreateControlTowerAccountStatus/ServiceRole/DefaultPolicy (CreateCTAccountsCreateControlTowerAccountStatusServiceRoleDefaultPolicy9BE6F791) Resource creation Initiated AWSAccelerator-PrepareStack-339713112183-us-east-1 |  86/102 | 8:15:40 AM | CREATE_IN_PROGRESS   | AWS::Lambda::Function                              | CreateCTAccounts/CreateControlTowerAccount (CreateCTAccountsCreateControlTowerAccount8636115B) Resource creation Initiated AWSAccelerator-PrepareStack-339713112183-us-east-1 |  86/102 | 8:15:40 AM | CREATE_FAILED        | AWS::ServiceCatalog::PortfolioPrincipalAssociation | CreateCTAccounts/LambdaPrincipalAssociation (CreateCTAccountsLambdaPrincipalAssociationFAD34BEB) Invalid input parameter(s) (Service: AWSServiceCatalog; Status Code: 400; Error Code: InvalidParametersException; Request ID: e19ca966-a3e4-441e-a415-b93735ec03f1; Proxy: null)     new CreateControlTowerAccounts (/codebuild/output/src785/src/s3/00/source/packages/@aws-accelerator/constructs/lib/aws-controltower/create-accounts.ts:149:5)     \_ PrepareStack.createConfigurationTables (/codebuild/output/src785/src/s3/00/source/packages/@aws-accelerator/accelerator/lib/stacks/prepare-stack.ts:480:40)     \_ new PrepareStack (/codebuild/output/src785/src/s3/00/source/packages/@aws-accelerator/accelerator/lib/stacks/prepare-stack.ts:287:14)     \_ createPrepareStack (/codebuild/output/src785/src/s3/00/source/packages/@aws-accelerator/accelerator/utils/stack-utils.ts:381:26)     \_ createManagementAccountStacks (/codebuild/output/src785/src/s3/00/source/packages/@aws-accelerator/accelerator/bin/app.ts:100:21)     \_ main (/codebuild/output/src785/src/s3/00/source/packages/@aws-accelerator/accelerator/bin/app.ts:237:5)     \_ processTicksAndRejections (node:internal/process/task_queues:96:5)     \_ async /codebuild/output/src785/src/s3/00/source/packages/@aws-accelerator/accelerator/bin/app.ts:251:5 AWSAccelerator-PrepareStack-339713112183-us-east-1 |  86/102 | 8:15:41 AM | CREATE_FAILED        | AWS::Lambda::Function                              | CreateCTAccounts/CreateControlTowerAccount (CreateCTAccountsCreateControlTowerAccount8636115B) Resource creation cancelled     new Function (/codebuild/output/src785/src/s3/00/source/node_modules/aws-cdk-lib/aws-lambda/lib/function.js:1:9470)     \_ new CreateControlTowerAccounts (/codebuild/output/src785/src/s3/00/source/packages/@aws-accelerator/constructs/lib/aws-controltower/create-accounts.ts:50:20)     \_ PrepareStack.createConfigurationTables (/codebuild/output/src785/src/s3/00/source/packages/@aws-accelerator/accelerator/lib/stacks/prepare-stack.ts:480:40)     \_ new PrepareStack (/codebuild/output/src785/src/s3/00/source/packages/@aws-accelerator/accelerator/lib/stacks/prepare-stack.ts:287:14)     \_ createPrepareStack (/codebuild/output/src785/src/s3/00/source/packages/@aws-accelerator/accelerator/utils/stack-utils.ts:381:26)     \_ createManagementAccountStacks (/codebuild/output/src785/src/s3/00/source/packages/@aws-accelerator/accelerator/bin/app.ts:100:21)     \_ main (/codebuild/output/src785/src/s3/00/source/packages/@aws-accelerator/accelerator/bin/app.ts:237:5)     \_ processTicksAndRejections (node:internal/process/task_queues:96:5)     \_ async /codebuild/output/src785/src/s3/00/source/packages/@aws-accelerator/accelerator/bin/app.ts:251:5 AWSAccelerator-PrepareStack-339713112183-us-east-1 |  86/102 | 8:15:41 AM | CREATE_FAILED        | AWS::IAM::Policy                                   | CreateCTAccounts/CreateControlTowerAccountStatus/ServiceRole/DefaultPolicy (CreateCTAccountsCreateControlTowerAccountStatusServiceRoleDefaultPolicy9BE6F791) Resource creation cancelled     new Policy (/codebuild/output/src785/src/s3/00/source/node_modules/aws-cdk-lib/aws-iam/lib/policy.js:1:1305)     \_ Role.addToPrincipalPolicy (/codebuild/output/src785/src/s3/00/source/node_modules/aws-cdk-lib/aws-iam/lib/role.js:1:7323)     \_ new Function (/codebuild/output/src785/src/s3/00/source/node_modules/aws-cdk-lib/aws-lambda/lib/function.js:1:7456)     \_ new CreateControlTowerAccounts (/codebuild/output/src785/src/s3/00/source/packages/@aws-accelerator/constructs/lib/aws-controltower/create-accounts.ts:127:23)     \_ PrepareStack.createConfigurationTables (/codebuild/output/src785/src/s3/00/source/packages/@aws-accelerator/accelerator/lib/stacks/prepare-stack.ts:480:40)     \_ new PrepareStack (/codebuild/output/src785/src/s3/00/source/packages/@aws-accelerator/accelerator/lib/stacks/prepare-stack.ts:287:14)     \_ createPrepareStack (/codebuild/output/src785/src/s3/00/source/packages/@aws-accelerator/accelerator/utils/stack-utils.ts:381:26)     \_ createManagementAccountStacks (/codebuild/output/src785/src/s3/00/source/packages/@aws-accelerator/accelerator/bin/app.ts:100:21)     \_ main (/codebuild/output/src785/src/s3/00/source/packages/@aws-accelerator/accelerator/bin/app.ts:237:5)     \_ processTicksAndRejections (node:internal/process/task_queues:96:5)     \_ async /codebuild/output/src785/src/s3/00/source/packages/@aws-accelerator/accelerator/bin/app.ts:251:5 AWSAccelerator-PrepareStack-339713112183-us-east-1 |  86/102 | 8:15:41 AM | ROLLBACK_IN_PROGRESS | AWS::CloudFormation::Stack                         | AWSAccelerator-PrepareStack-339713112183-us-east-1 The following resource(s) failed to create: [CreateCTAccountsCreateControlTowerAccount8636115B, CreateCTAccountsLambdaPrincipalAssociationFAD34BEB, CreateCTAccountsCreateControlTowerAccountStatusServiceRoleDefaultPolicy9BE6F791]. Rollback requested by user.
I already tried to delete whole stack, and re-start whole process again.
I also tried to use different version (1.6.1 and 1.6.0)
but the problem is still there....
Please complete the following information about the solution:

[ ] Version:1.6.1 and 1.6.0

[ ] Region: us-east-1

[ ] Was the solution modified from the version published on this repository? no

[ ] If the answer to the previous question was yes, are the changes available on GitHub?

[ ] Have you checked your service quotas for the services this solution uses? no

[ ] Were there any errors in the CloudWatch Logs?

Hello @damovsky, thank you for filing an issue with the Landing Zone Accelerator team ! I am not able to replicate same behavior in my environment with v1.6.2.
For temporary workaround, please manually add and enroll accounts. We are also working on up upgrading to sdv3 for this specific create account vending process, and this will be available in upcoming release. This might fix the issue you are experiencing.
If you have any other questions, please do not hesitate to reach out to us.


Subrequests: get same results on different request

For those who have problems to get the node content:
We had the same problem as described in this issue: https://www.drupal.org/project/subrequests/issues/3049395
After applying the patch https://www.drupal.org/files/issues/2019-07-18/change_request_type-63049395-09.patch the results from the subrequests are fine.
Our installations:
Drupal 9.2.7
Subrequests 3.0.3
Next 1.0.0-beta5
PHP 7.3

I've updated the docs to include the patches: https://next-drupal.org/learn/quick-start/apply-patches


 Previous child's mailbox will be disposed. It doesn't fit into let-it-fail concept.
We need childs to preserve mailbox on respawn. Also we need a lifecycle callbacks which can access child state and a message which caused child failure.

Like we have talked, let's go with flat hierarchy for this.

if it is of any help. I started looking outside of actix cause it doesnt support this. its very important to have this to truly mimic the fautl tolerance of BEAM
I speak this as an end-user and not a developer

Done in PR #199.


Fix event handling error on Windows

Closes #424

Yeah, Windows doesn't have something like that's supported in Python.


New control plane node added to a custom cluster is stuck in "Registering" State

Rancher versions:
rancher/server: master from April 16
Steps to Reproduce:

Create a rancher server on DO box.
Create a custom cluster with AWS hosts with 1 control node, 1 etcd node and 2 worker nodes
Once the cluster is active, add another control plane node

The new node is stuck in "registering" state
rke cannot ssh to the new control plane node added

2018-04-16 21:02:55.884762 I | mvcc: store.index: compact 46919
2018-04-16 21:02:55.886842 I | mvcc: finished scheduled compaction at 46919 (took 1.493317ms)
2018/04/16 21:04:48 [INFO] Provisioning cluster [1c-c4mcd]
2018/04/16 21:04:48 [INFO] Updating cluster [1c-c4mcd]
2018/04/16 21:04:48 [INFO] cluster [1c-c4mcd] provisioning: Building Kubernetes cluster
2018/04/16 21:04:48 [INFO] cluster [1c-c4mcd] provisioning: [dialer] Setup tunnel for host [172.31.16.xyz]
2018/04/16 21:04:48 [INFO] cluster [1c-c4mcd] provisioning: [dialer] Setup tunnel for host [172.31.19.xyz]
2018/04/16 21:04:48 [ERROR] cluster [1c-c4mcd] provisioning: Failed to set up SSH tunneling for host [172.31.19.xyz]: Can't establish dialer connection: can not build dialer to 1c-c4mcd:m-03008a4724f8
2018/04/16 21:04:48 [INFO] cluster [1c-c4mcd] provisioning: [dialer] Setup tunnel for host [172.31.19.abc]
2018/04/16 21:04:48 [ERROR] cluster [1c-c4mcd] provisioning: Removing host [172.31.19.xyz] from node lists

2018/04/16 21:04:58 [INFO] cluster [1c-c4mcd] provisioning: [ingress] ingress controller nginx is successfully deployed
2018/04/16 21:04:58 [INFO] cluster [1c-c4mcd] provisioning: [addons] Setting up user addons
2018/04/16 21:04:58 [INFO] cluster [1c-c4mcd] provisioning: [addons] no user addons defined
2018/04/16 21:04:58 [INFO] cluster [1c-c4mcd] provisioning: Finished building Kubernetes cluster successfully
2018/04/16 21:04:58 [INFO] Provisioned cluster [1c-c4mcd]
2018/04/16 21:04:58 [INFO] Handling backend connection request [m-03008a4724f8]
2018-04-16 21:07:55.888672 I | mvcc: store.index: compact 47758
2018-04-16 21:07:55.890770 I | mvcc: finished scheduled compaction at 47758 (took 1.448337ms)
E0416 21:12:51.551210       1 streamwatcher.go:109] Unable to decode an event from the watch stream: json: cannot unmarshal string into Go struct field dynamicEvent.Object of type v3.NodeStatus
2018-04-16 21:12:55.892865 I | mvcc: store.index: compact 48701
2018-04-16 21:12:55.895099 I | mvcc: finished scheduled compaction at 48701 (took 1.772989ms)
2018-04-16 21:17:55.896811 I | mvcc: store.index: compact 49514
2018-04-16 21:17:55.899273 I | mvcc: finished scheduled compaction at 49514 (took 1.524245ms)
E0416 21:18:46.553633       1 streamwatcher.go:109] Unable to decode an event from the watch stream: json: cannot unmarshal string into Go struct field dynamicEvent.Object of type v3.NodeStatus
2018/04/16 21:22:19 [ERROR] failed on subscribe storageClass: Get https://<IP_ADDRESS>:6443/apis/storage.k8s.io/v1/storageclasses?resourceVersion=0&timeoutSeconds=3600&watch=true: dial tcp <IP_ADDRESS>:6443: getsockopt: connection refused
2018/04/16 21:22:26 [ERROR] netpolMgr: program: error updating network policy err=Put https://<IP_ADDRESS>:6443/apis/networking.k8s.io/v1/namespaces/default/networkpolicies/hn-nodes: dial tcp <IP_ADDRESS>:6443: getsockopt: connection refused
2018/04/16 21:22:26 [ERROR] netpolMgr: handleHostNetwork: error programming hostNetwork network policy for ns=default err=Put https://<IP_ADDRESS>:6443/apis/networking.k8s.io/v1/namespaces/default/networkpolicies/hn-nodes: dial tcp <IP_ADDRESS>:6443: getsockopt: connection refused
2018-04-16 21:22:55.900662 I | mvcc: store.index: compact 50354
2018-04-16 21:22:55.902949 I | mvcc: finished scheduled compaction at 50354 (took 1.803789ms)
2018/04/16 21:27:42 [ERROR] netpolMgr: program: error updating network policy err=Put https://<IP_ADDRESS>:6443/apis/networking.k8s.io/v1/namespaces/default/networkpolicies/hn-nodes: dial tcp <IP_ADDRESS>:6443: getsockopt: connection refused
2018/04/16 21:27:42 [ERROR] netpolMgr: handleHostNetwork: error programming hostNetwork network policy for ns=default err=Put https://<IP_ADDRESS>:6443/apis/networking.k8s.io/v1/namespaces/default/networkpolicies/hn-nodes: dial tcp <IP_ADDRESS>:6443: getsockopt: connection refused
2018-04-16 21:27:55.904084 I | mvcc: store.index: compact 51185
2018-04-16 21:27:55.905930 I | mvcc: finished scheduled compaction at 51185 (took 1.365479ms)
E0416 21:28:41.556013       1 streamwatcher.go:109] Unable to decode an event from the watch stream: json: cannot unmarshal string into Go struct field dynamicEvent.Object of type v3.NodeStatus
2018/04/16 21:32:27 [ERROR] netpolMgr: program: error updating network policy err=Put https://<IP_ADDRESS>:6443/apis/networking.k8s.io/v1/namespaces/default/networkpolicies/hn-nodes: dial tcp <IP_ADDRESS>:6443: getsockopt: connection refused
2018/04/16 21:32:27 [ERROR] netpolMgr: handleHostNetwork: error programming hostNetwork network policy for ns=default err=Put https://<IP_ADDRESS>:6443/apis/networking.k8s.io/v1/namespaces/default/networkpolicies/hn-nodes: dial tcp <IP_ADDRESS>:6443: getsockopt: connection refused
2018-04-16 21:32:55.909135 I | mvcc: store.index: compact 52000
2018-04-16 21:32:55.911145 I | mvcc: finished scheduled compaction at 52000 (took 1.426837ms)

The same behavior is also seen when adding a new etcd node to an existing cluster.
Node gets stuck in "Registering" forever. Following error seen in logs:
2018/04/17 04:14:01 [INFO] Provisioning cluster [1c-228bx]
2018/04/17 04:14:01 [INFO] Updating cluster [1c-228bx]
2018/04/17 04:14:01 [INFO] cluster [1c-228bx] provisioning: Building Kubernetes cluster
2018/04/17 04:14:01 [INFO] cluster [1c-228bx] provisioning: [dialer] Setup tunnel for host [<ip>]
2018/04/17 04:14:01 [INFO] cluster [1c-228bx] provisioning: [dialer] Setup tunnel for host [<ip>]
2018/04/17 04:14:01 [ERROR] cluster [1c-228bx] provisioning: Failed to set up SSH tunneling for host [<ip>]: Can't establish dialer connection: can not build dialer to 1c-228bx:m-ce8c960591e5
2018/04/17 04:14:01 [INFO] cluster [1c-228bx] provisioning: [dialer] Setup tunnel for host [<IP_ADDRESS>]
2018/04/17 04:14:01 [ERROR] cluster [1c-228bx] provisioning: Removing host [<ip>] from node lists

Tested with master build from Apr 18th.
Create a custom cluster with AWS hosts with 1 control node, 1 etcd node and 2 worker nodes
After the cluster was active, added another control plane node. The new control plane got added successfully and the new workloads got created. kubectl was functional


SetSudo not working when creating access token

Description
Usecase:
i have  admin accessstoken,  and i new the client by setting this token.  Now i have many users, and i want to  help them create their own access token, so i want to use admin to on behalf them, i use setSudo , but not success..
i get message
"\"username\" not set: only BasicAuth allowed"

my client code is ：
cli := gitea.NewClient(GetGitServer(), gitea.SetToken(xx),gitea.SetSudo(user1))
at, resp, err := cli.CreateAccessToken(option)

Gitea Version
1.19
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
linux
How are you running Gitea?
docker-compose up -d
Database
MySQL

As the error info said, only BasicAuth allowed.
So use SetBasicAuth when create gitea client?
ps: maybe this issue should move to https://gitea.com/gitea/go-sdk ?


Hello JuniorDjjr

Hello JuniorDjjr
i wonder if its possible to make some parts in vehicle rotate with key press ? like shooting mounted guns in heli or hydra that rotates with key i have done sparrow heli rotate minigun on it and hydra lever that go up and down left and right pedal but i want this function in vehfunc thank you

oh you can't its ok thanks


BAW mesh loader

Becuase cstdint is from C++11, GCC throws a fit about it.
All that stdint provides is typedefs for (u)intN_t

Wunderbar
Am 01.02.2018 12:46 schrieb "devshgraphicsprogramming" <
<EMAIL_ADDRESS>
@devshgraphicsprogramming commented on this pull request.
In include/CFinalBoneHierarchy.h
https://github.com/buildaworldnet/IrrlichtBAW/pull/21#discussion_r165333271
:

@@ -100,6 +101,35 @@ namespace scene
createAnimationKeys(inLevelFixedJoints);
}

	void fillExportBlob(void* _dataPtr, uint32_t* _size)

Maybe have a "Blob* SerializeToBlob(void** initialData, uint32_t&
initialBlobSize=0);" function for future use in all classes?
With a requirement that outBlob is either NULL or an address of a pointer
to memory which can be reallocated using realloc.
And then at the end of the function return *outBlob;
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/buildaworldnet/IrrlichtBAW/pull/21#pullrequestreview-93253098,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA7twpt5rn6vu0-VfwU7AXZ41y4TvxBZks5tQaP6gaJpZM4R0PTU
.

About  variable size blobs such as MeshBlobV1, FinalBoneHierarchyBlobV1, etc.
Lets inherit them from a template struct
template<class T> struct VariableSizeBlob : public Blob {     static size_t caclBlobSizeForObj(T* _obj) {return 0;}     static void*  allocMemForBlob(T* _obj) {return malloc(caclBlobSizeForObj<T>());} };
as i.e. struct MeshBlobV1 : VariableSizeBlob
Then specialize the calcBlobSizeForObj function for all objects?

Also I'm seeing a lot of
_ctx.headers[_headerIdx].blobSize = _ctx.headers[_headerIdx].blobSizeDecompr = size; core::XXHash_256(&data, _ctx.headers[_headerIdx].blobSizeDecompr, _ctx.headers[_headerIdx].blobHash); _file->write(data, _ctx.headers[_headerIdx].blobSizeDecompr);
In every exportAsBlob
maybe we should make a general function for this on the Blob or in the CBAWMeshWriter, so we don't repeat ourselves?

Still don't like the fact that allocMemForBlob is not a member of VariableSizeBlob
We can make it work with a CRTP.
https://en.wikipedia.org/wiki/Curiously_recurring_template_pattern#Static_polymorphism
This ties is with the other thing I don't like which is that ALL blobs are not constructed and filled in their constructors, VariableSizeBlobs would just use static some static func, i.e. "createFromObj" which would use placement new internally, with private constructors.

Did this one thing now. About everything else I'll talk to you in a few days because of mentioned lack of time..

No problem, just remember to merge, I had to rip out C++11 std::free and malloc stuff from CBAWMeshWriter.cpp again

I think a big problem now is a lot of DRY (Don't Repeat Yourself) violation, basically every specialization of CBAWMeshFileLoader::make
Does
if (_data.wasCreated)     return dynamic_cast<core::ICPUBuffer*>(_ctx.createdObjects[_data.header->handle]);
and
registerObject(_data, _ctx, buf); (which I want to disappear anyway)
The function CBAWMeshFileLoader::make should be wrapped in a generic loadBlob function which should do stuff like checking if the object was already loaded/created, checksum validation (in the future decompression) and changing the object's status to loaded.

I think I forgot to mention rule 12,13 and 14 of HPC:
12) Recursion is evil, and so are deep call-stacks, ergo rule 13
13) Don't inline your functions, but keep them inlineable
14) Eliminate deep call-stacks, by usting your own stack!

Stop what you're doing, we need to talk


setup Google Analytics for cinms

Added nms-web account per Add an account to an existing account - Analytics Help
Added "property" for cinms and created web stream per Use Analytics with your site - Sites Help

get snippet and add as header to all web pages in site yaml, then seperately for modals per r markdown - How to include Google Analytics in an RMarkdown generated GitHub Page? - Stack Overflow

Pages visited

Device type
(have to wait 24-48 hrs)

The fix for #78 should solve this issue.

TODO: + for underlying modals, see noaa-onms/ocnms#45


⚠ Bofrost.at has degraded performance

In 8ee2905, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1006 ms

Resolved: Bofrost.at performance has improved in 6a3cb34.


Define API for Transformer defences and implement Defensive Distillation as example

Description
Fixes #293
Type of change
Please check all relevant options.

[ ] Bug fix (non-breaking)
[x] New feature (non-breaking)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Testing
Please describe the tests that you ran to verify your changes. Consider listing any relevant details of your test configuration.

[ ] Test A
[ ] Test B

Test Configuration:

OS
Python version
ART version or commit number
TensorFlow / Keras / PyTorch / MXNet version

Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

This PR contributes to issue #251


Eirini does not work with K8s 1.13

Description
Eirini does not work with K8s 1.13
Steps to reproduce

Go to your favorite cloud provider
Provision a K8s cluster with version 1.13 or higher
Deploy an eirini on it

What was expected to happen
It should work
What actually happened
It doesn't

Master branch of Eirini can be deployed on IKS 1.13 (or other installation with metrics service).


provide an API to fetch "what actions user:x can perform on entity:y"

Is your feature request related to a problem? Please describe.
When applying permission controls on frontend, we often need to get a list of permissions that user can perform on a certain object so that we can hide/display the corresponding button(s) or page(s). it is tedious and less performant to ask each permission/action using the "check" API endpoint provided by permfiy as of now, since we will have to fire many calls (one per permission/action) to permify from frontend to get such info.
Describe the solution you'd like
Having a dedicated API endpoint to fetch such info in one call from permify.
Describe alternatives you've considered
if such API cannot be added to permify, we would need need wrap such API endpoint by calling permify api multiple times (one for each action). it will become worse when new action being added
Additional context
Add any other context or screenshots about the feature request here.

We concluded this issue with the development of the Subject Permission List endpoint. Here is the related documentation: https://docs.permify.co/docs/api-overview/permission/subject-permission/


styled-components multiple instances error since 2.0.0-alpha.37

Since 2.0.0-alpha.37 including the RedocStandalone component will fail in a project that uses styled-components:
It looks like there are several instances of 'styled-components' initialized in this application. This may cause dynamic styles not rendering properly, errors happening during rehydration process and makes your application bigger without a good reason.

See https://s-c.sh/2BAXzed for more info.

Thanks for the issue report.
I will add styled-components to peerDependencies in the next alpha.


platforms/install_if behaviour change on Bundler 1.14.x

This issue can also be reproduced by checking out this commit: https://github.com/trailblazer/roar/commit/619cb5a362d9d66926efc91842955afdcfad4933 and running bundle install without an existing Gemfile.lock.
In previous versions of Bundler (1.13.x), the following worked as a way to prevent a development/test dependency from being installed on older versions of Ruby, without having a different Gemfile for each version of Ruby that we want to support:
install_if -> { RUBY_VERSION > '2.2.2' } do
  gem 'sinatra',          '~> 2.0.0.beta2'
  gem 'sinatra-contrib',  github: 'sinatra/sinatra'
end

(in our case, we just don't run tests that require Sinatra on versions of Ruby prior to 2.2.2)

Environment
Bundler   1.14.3
Rubygems  2.6.8
Ruby      1.9.3p550 (2014-10-27 revision 0) [x86_64-darwin16.1.0]
GEM_HOME  /Users/alexbcoles/.gem/ruby/1.9.3
GEM_PATH  /Users/alexbcoles/.gem/ruby/1.9.3:/Users/alexbcoles/.rubies/ruby-1.9.3-p550/lib/ruby/gems/1.9.1
Git       2.11.0
Platform  x86_64-darwin-16

Bundler settings
gem.test
  Set for the current user (/Users/alexbcoles/.bundle/config): "minitest"
gem.mit
  Set for the current user (/Users/alexbcoles/.bundle/config): "true"
gem.coc
  Set for the current user (/Users/alexbcoles/.bundle/config): "false"

Gemfile
Gemfile
source "http://rubygems.org"

# Specify your gem's dependencies in roar.gemspec
gemspec

install_if -> { RUBY_VERSION > '2.2.2' } do
  gem 'sinatra',          '~> 2.0.0.beta2'
  gem 'sinatra-contrib',  github: 'sinatra/sinatra'
end

gem 'nokogiri', '~> 1.6.8'

# gem "representable", path: "../representable"
# gem "representable", github: "apotonick/representable"
# gem "declarative", path: "../declarative"
gem "minitest-line"
gem "pry"

Gemfile.lock
PATH
  remote: .
  specs:
    roar (1.1.0)
      representable (~> 3.0.0)

GEM
  remote: http://rubygems.org/
  specs:
    axiom-types (0.1.1)
      descendants_tracker (~> 0.0.4)
      ice_nine (~> 0.11.0)
      thread_safe (~> 0.3, >= 0.3.1)
    coderay (1.1.1)
    coercible (1.0.0)
      descendants_tracker (~> 0.0.1)
    declarative (0.0.9)
    declarative-option (0.1.0)
    descendants_tracker (0.0.4)
      thread_safe (~> 0.3, >= 0.3.1)
    equalizer (0.0.11)
    faraday (0.11.0)
      multipart-post (>= 1.2, < 3)
    ice_nine (0.11.2)
    method_source (0.8.2)
    mini_portile2 (2.1.0)
    minitest (5.10.1)
    minitest-line (0.6.3)
      minitest (~> 5.0)
    multi_json (1.12.1)
    multipart-post (2.0.0)
    nokogiri (<IP_ADDRESS>)
      mini_portile2 (~> 2.1.0)
    pry (0.10.4)
      coderay (~> 1.1.0)
      method_source (~> 0.8.1)
      slop (~> 3.4)
    rake (12.0.0)
    representable (3.0.3)
      declarative (< 0.1.0)
      declarative-option (< 0.2.0)
      uber (< 0.2.0)
    slop (3.6.0)
    test_xml (0.1.6)
      nokogiri (>= 1.3.2)
    thread_safe (0.3.5)
    uber (0.1.0)
    virtus (1.0.5)
      axiom-types (~> 0.1)
      coercible (~> 1.0)
      descendants_tracker (~> 0.0, >= 0.0.3)
      equalizer (~> 0.0, >= 0.0.9)

PLATFORMS
  ruby

DEPENDENCIES
  faraday
  minitest (>= 5.10)
  minitest-line
  multi_json
  nokogiri (~> 1.6.8)
  pry
  rake (>= 0.10.1)
  roar!
  test_xml (= 0.1.6)
  virtus (>= 1.0.0)

RUBY VERSION
   ruby 1.9.3p550

BUNDLED WITH
   1.14.3

Gemspecs
roar.gemspec
$:.push File.expand_path("../lib", __FILE__)
require "roar/version"

Gem::Specification.new do |s|
  s.name        = "roar"
  s.version     = Roar::VERSION
  s.platform    = Gem::Platform::RUBY
  s.authors     = ["Nick Sutterer"]
  s.email       =<EMAIL_ADDRESS>  s.homepage    = "http://trailblazer.to/gems/roar"
  s.summary     = %q{Parse and render REST API documents using representers.}
  s.description = %q{Object-oriented representers help you defining nested REST API documents which can then be rendered and parsed using one and the same concept.}
  s.license = 'MIT'

  s.files         = `git ls-files`.split("\n")
  s.test_files    = `git ls-files -- {test}/*`.split("\n")
  s.executables   = `git ls-files -- bin/*`.split("\n").map{ |f| File.basename(f) }
  s.require_paths = ["lib"]

  s.add_runtime_dependency "representable", "~> 3.0.0"

  s.add_development_dependency "rake", ">= 0.10.1"
  s.add_development_dependency "test_xml", "0.1.6"
  s.add_development_dependency 'minitest', '>= 5.10'
  s.add_development_dependency "sinatra", '>= 2.0.0'
  s.add_development_dependency "sinatra-contrib", '>= 2.0.0'
  s.add_development_dependency "virtus", ">= 1.0.0"
  s.add_development_dependency "faraday"
  s.add_development_dependency "multi_json"
end

I realise that I may not be using install_if as intended. However, if I do the following (with or without a ruby version declaration):
platforms :ruby_22, :ruby_23, :ruby_24, :ruby_25 do
  gem 'sinatra',          '~> 2.0.0.beta2'
  gem 'sinatra-contrib',  github: 'sinatra/sinatra'
end

then I still hit:
Fetching git://github.com/sinatra/sinatra.git
Fetching gem metadata from http://rubygems.org/........
Fetching version metadata from http://rubygems.org/.
Resolving dependencies...
Bundler could not find compatible versions for gem "ruby":
  In Gemfile:
    ruby

    sinatra-contrib was resolved to 2.0.0.beta2, which depends on
      ruby (>= 2.2.0)

    sinatra-contrib was resolved to 2.0.0.beta2, which depends on
      ruby (>= 2.2.0)

Could not find gem 'ruby (>= 2.2.0)', which is required by gem 'sinatra-contrib', in any of the sources.

That is intended -- it just means those gems wont be installed on those platforms, not that we wont still resolve respecting ruby versions

@segiddins I created a smaller reproduction. With regards to platforms block, I would expect the following to resolve, even on Ruby 1.9.3:
source "http://rubygems.org"

ruby '>= 1.9.3'

platforms :ruby_21, :ruby_22, :ruby_23, :ruby_24, :ruby_25 do
  gem 'nokogiri', '~> 1.7'
end

instead:
$ bundle install

Fetching gem metadata from http://rubygems.org/.............
Fetching version metadata from http://rubygems.org/.
Resolving dependencies...
Bundler could not find compatible versions for gem "ruby":
  In Gemfile:
    ruby (>= 1.9.3)

    nokogiri (~> 1.7) was resolved to 1.7.0, which depends on
      ruby (>= 2.1.0)

Could not find gem 'ruby (>= 2.1.0)', which is required by gem 'nokogiri (~>
1.7)', in any of the sources.

(I did also try setting BUNDLE_FORCE_RUBY_PLATFORM and BUNDLE_SPECIFIC_PLATFORM, but to no avail)

Right, there doesn't seem to be a version of nokogiri 1.7.x compatible with ruby 2.9.3

@segiddins since I'm hit by a similar problem, I'm wondering: Do you agree that this is a bug? I couldn't really tell from your comment.
(In my case, I'm trying to load xmlrpc only on MRI 2.4)

I don't think it is a bug

@segiddins if this is how it should work, I'm not sure what the version-specific platforms are useful for. Is there some documentation that describes this? I'm sure I'm not the only one who finds this highly confusing.

I'm closing this for now.

@colby-swandale it would be nice if there was at least some documentation for this, so not only @segiddins understands why this works the way it works.

@colby-swandale I'm willing to write something up for this, because I think I understand almost everything, but I will need some help for the bits that are unclear to me (see my comment https://github.com/bundler/bundler/issues/5377#issuecomment-284208321 above).

Sounds great! i'm sure @segiddins would be able to help if you have any questions.


Translation support

Is it correct that currently translation is not supported?
I took a quick look at the source code and changed the following things and got my basic test to work with translation.
Could this dirty little change break oder cause problems that i didn't think of?
Godot3 branch:
add
text = tr(text)
before
https://github.com/nagidev/DialogueNodes/blob/e4ae64591cd08b65a852cad897bf71641019684f/addons/dialogue_nodes/objects/dialogueBox.gd#L300-L301
Main branch:
add value = tr(value)
before
https://github.com/nagidev/DialogueNodes/blob/4653a947aefe3cdb8c5fab30889e59da6a526f58/addons/dialogue_nodes/objects/DialogueParser.gd#L283-L285

Currently the way I handle localization is by creating different dialogue files for each locale. The code you're suggesting won't cause any issues as far as I know. If you can test it and raise a PR for it, I'd be happy to get it merged!

I make my own translation plugin for dialogue files with https://docs.godotengine.org/en/4.2/classes/class_editortranslationparserplugin.html

Closing since tr() is added to the DialogueParser class now.


[Frontend] Add tokenize/detokenize endpoints

OpenAI has one tokenizer for all its models, which can be used with the tiktoken library, but for everyone else, it is very difficult to determine which tokenizer to use.
This PR adds tokenize/detokenize endpoints for token counting or other uses of tokens in end applications.
Example (Llama 3):
$ curl -H "Authorization: Bearer token-abc123" -H "Content-Type: application/json" -d '{"model":"meta-llama/Meta-Llama-3-8B-Instruct","prompt":"test"}' http://localhost:8000/tokenize
{"tokens":[128000,1985],"count":2,"max_model_len":8192}
$ curl -H "Authorization: Bearer token-abc123" -H "Content-Type: application/json" -d '{"model":"meta-llama/Meta-Llama-3-8B-Instruct","prompt":"test","add_special_tokens":false}' http://localhost:8000/tokenize
{"tokens":[1985],"count":1,"max_model_len":8192}
$ curl -H "Authorization: Bearer token-abc123" -H "Content-Type: application/json" -d '{"model":"meta-llama/Meta-Llama-3-8B-Instruct","tokens":[128000, 1985]}' http://localhost:8000/detokenize
{"prompt":"<|begin_of_text|>test"}

It looks like the format.sh script is incorrect. isort reformats the files after yapf, and this causes a yapf error (since the files are now formatted differently than yapf likes).

+1 This would be extremely useful.

@robertgshaw2-neuralmagic
No, this is not supported. Since OpenAI use the same tokenizer for their models, they suggest using tiktoken. But with other models the situation is more complicated - each model uses a different tokenizer (llama 2, llama 3, mistral, yi, etc) and there is no easy way to determine which tokenizer to use.
Each open-source OpenAI-compatible server exposes these endpoints, for example:
llama.cpp: /tokenize & /detokenize
text-generation-webui: /v1/internal/encode & /v1/internal/decode & /v1/internal/token-count
koboldcpp: /api/extra/tokencount
aphrodite-engine: /v1/tokenize
tabbyAPI: /v1/token/encode & /v1/token/decode

OpenAI does have this: https://platform.openai.com/tokenizer but looks like it just implements tiktoken in JS.
Considering we have /health and /version for internals in vLLM, mirroring llama.cpp's /tokenize and /detokenize for these non-OpenAI API routes seems reasonable. Avoiding the /v1 routes seems logical as well as those would be confused/associated with the official OpenAI API.

OpenAI does have this: https://platform.openai.com/tokenizer but looks like it just implements tiktoken in JS.
Considering we have /health and /version for internals in vLLM, mirroring llama.cpp's /tokenize and /detokenize for these non-OpenAI API routes seems reasonable. Avoiding the /v1 routes seems logical as well as those would be confused/associated with the official OpenAI API.

I agree with @jasonacox. Let's keep off the /v1 route.
@sasha0552 can you let me know when ready for review? Thx.

Also, please add tests. Thanks!

@robertgshaw2-neuralmagic can you review again, please? I think it's ready to merge.

While this PR is still open, would it make sense to add the count and model's maximum token count to the response object?
For example, adding count and max_tokens (or model_max_length):
{
  "tokens": [1, 2, 3],
  "count": 3,
  "max_tokens": 8192
}

I have no objection to that.

Ready for review?

Yes, I think it is.

@robertgshaw2-neuralmagic Could you please do a review?

@robertgshaw2-neuralmagic Could you please do a review?

Looking at this now

@sasha0552 - thanks for your patience and Im really sorry for the delayed reviews here.
The functionality and UX looks good.
My only question is why do we need to change async def _check_models to def _check_models?

Approved and automerge is enabled if it passes CI.
Ping me if you need me to kick the CI to get the tests to pass:

@ my github name
rshaw [at] neuralmagic [dot] com

@sasha0552
I would be nice to add a the capacity to:
Given a list of msg, return the tokens, after applying the chat_template. Now this does not apply, righyt?. Only tokens to be used with  the /completion endpoint would be returned, but no chat/completion.
btw, nice feature.

@AguirreNicolas
This will be pretty easy to implement. I'll be send a PR soon.


Update motor tests to work with BrickPi

This resolves merge conflicts in #152.

@dlech, could you please check if this still does what was intended originally?

Yes. Ping me if I haven't done this in a week or two.

Ping me if I haven't done this in a week or two.

ping

@ddemidov two more sync conflicts have cropped up...can you take a quick look and we can get this in?

I've rebased on current develop, but I can not test the changes on brickpi (don't have it).

me neither mine died a while back :( @dlech can you give this a quick test and let us know if it looks good?

I updated my brickpi branch with some more commits, but #152 seems to have ignored it since it is closed and it won't let me re-open.
https://github.com/dlech/ev3dev-lang-python/tree/brickpi

I've pulled commits from https://github.com/dlech/ev3dev-lang-python/tree/brickpi here.

What's the situation here: do we want to resolve conflicts and merge? I'm happy with this if you guys believe it doesn't break anything.

+1 for merging it

I've just reset contents of tests/motor to that of 'brickpi' branch at dlech/ev3dev-lang-python. This narrows the PR to this particular folder and (I hope) makes sure we don't screw up other parts of the repo.

I don't have a brickpi but I'll at least test out the patch tonight to make sure tests are ok on EV3 and EVB...assuming so will merge it after that.


[CLOUDSTACK-10197] Update DisplayText of XenServer tools ISO entry in the database when it already exists

Changes here were suggestions made to #2365, but for some reason, the PR was merged without considering them. Both the update of the ‘displayText’  value and unit test cases were suggested as improvements in that PR.
After coding, I also when through those classes and removed unused variables.
@khos2ow can you take a look here?

@rafaelweingartner It seems you have some "trailing spaces" issues on XcpServerDiscovererTest.java and couple of variable name issues. The latter one is really annoying, because it forces to have ^_?[a-zA-Z0-9]*$ for final variables.

@khos2ow thanks for the review.
And yes, those check-style rules are quite annoying. We need to discuss and change them to better fit the common practice nowadays.

What do you think @DaanHoogland, do wee need to wait for integration tests here?

@rafaelweingartner doesn't hurt does it?
@blueorangutan package

@DaanHoogland a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

@rhtyd can you review this, please?

Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1750

@DaanHoogland no it does not ;)

@blueorangutan test

@DaanHoogland a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

Trillian test result (tid-2313)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 29032 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2470-t2313-kvm-centos7.zip
Intermitten failure detected: /marvin/tests/smoke/test_hostha_kvm.py
Smoke tests completed. 66 look OK, 1 have error(s)
Only failed tests results shown below:

Test
Result
Time (s)
Test File

test_hostha_enable_ha_when_host_in_maintenance
Error
1.03
test_hostha_kvm.py

@DaanHoogland is this "test_hostha_enable_ha_when_host_in_maintenance" an intermittent error? I have seen this on #2425, which is a very different PR.

Yes @rafaelweingartner , I've seen this one a lot and seen it pass as well. Your code here is not related to that test afaik.
@rhtyd @PaulAngus can you give second and third opinions?

@DaanHoogland this one seems to be ready. Would you like to wait for a third and fourth eyes here?

@rafaelweingartner no it is fine


gerry

This document does not execute as stated when loaded into Visual Studio Community Version 15.7.2, seems that the setup is incomplete for F#

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

ID: f4051ae2-8154-5007-b633-dcd0d71f84fc
Version Independent ID: fed62955-cf8b-55e7-b4d4-851cd85dc6d2
Content: Get started with F# in Visual Studio
Content Source: docs/fsharp/get-started/get-started-visual-studio.md
Service: unspecified
Product: dotnet-fsharp
GitHub Login: @cartermp
Microsoft Alias: phcart

@cartermp can you take a look at this issue?


Fix PPC64 problems

This patch set fixes issue #15748 and makes some other minor alignment changes.
It also fixes an issue because the code to save registers into vector registers does not work on ISA < 2.07, reverting to the regular method of saving registers to the stack.  The performance penalty is less than 1%.
Overall performance for ecdhp384 and ecdsap384 is pretty much unchanged.
I'm happy to break this up into multiple PRs if necessary.
The commits have been locally reviewed by Amitay and have corresponding Reviewed-by: tags.  We're not sure what the convention is for non-maintainer reviewers - please let us know if there is something better (e.g. Acked-by: ?).  I can update to whatever is suggested and push again, or the commit summaries can be updated by someone who knows better.  ;-)
This has been tested on Linux running on Power 9 (ISA 3.0) and AIX on Power 7 (ISA 2.06).

Checklist

I didn't bother updating the FIPs checksums.  Not sure if it should be done in each commit that touches a particular file.  In previous PRs I think these have been fixed during merge.  Please yell if I should have done this.
Please let me know if I have missed anything else...
Thanks!

IMO this should be treated as urgent and merged before beta1.

Agreed with urgent, although it would have been nice to confirm it works ....

Agreed with urgent, although it would have been nice to confirm it works ....

I can actually try.

Please let me know if there's any test output I can provide to improve confidence.
One problem is that make test seems to have problems on AIX, at least according to some other open issues.  I don't think I'll be able to get the Perl modules installed tonight to give it a proper try.  However, I can (for example) provide openssl speed ecdhp384 output after a successful build.
Apologies for breaking this and for the late fix.  Mistakes made, lessons learned.  We'll clearly do AIX testing for future Power changes...

IMO, this is too  late for beta 1. I'm starting the release process NOW...

There are a couple more commits required to fix the AIX build for the p521 changes that we also submitted.  They're in https://github.com/martin-schwenke/openssl/tree/master-p521 - should they be in this PR too?  Given the title of this PR, I suspect it should be a different PR.

Clearing the urgent severity then. Please add the other patches as apparently they are needed to build the assembler code on AIX as well.

I see currently:
crypto/ec/ecp_nistp521-ppc64.s: line 5: invalid opcode or pseudo-op
crypto/ec/ecp_nistp521-ppc64.s: line 197: invalid opcode or pseudo-op
crypto/ec/ecp_nistp521-ppc64.s: line 202: invalid opcode or pseudo-op
crypto/ec/ecp_nistp521-ppc64.s: line 345: invalid opcode or pseudo-op

Whether you add the additional patches here or as a separate PR does not matter much.

I've added 3 commits for p521, hence the title change for this PR.
The extra commits:

Fix the build failures mentioned above by dropping some problematic assembler pseudo-ops
Add .align at the beginning of functions
Drop the build of ecp_nistp521-ppc64.s unless configured with enable-ec_nistp_64_gcc_128 - the build failures shouldn't have been seen unless the build was configured with enable-ec_nistp_64_gcc_128

Note that there's still a problem with p521 on AIX when configured with enable-ec_nistp_64_gcc_128:
$ LD_LIBRARY_PATH=. apps/openssl speed ecdhp521
ECDH computations don't match.
version: 3.0.0-alpha4
built on: built on: Fri Jun 18 04:33:52 2021 UTC
options:bn(64,64) rc4(char) des(int) aes(partial) idea(int) blowfish(ptr)
compiler: gcc -maix64 -pthread -O -DB_ENDIAN -DOPENSSL_PIC -DOPENSSL_BUILDING_OPENSSL -DNDEBUG
CPUINFO: N/A

However, this isn't a new problem:
$ LD_LIBRARY_PATH=. apps/openssl version
OpenSSL 3.0.0-alpha4 25 Jun 2020 (Library: OpenSSL 3.0.0-alpha4 25 Jun 2020)

We don't (yet?) know how to fix this.  It certainly predates our recent assembly code.  Perhaps it has never worked?
I won't hold this patch series until we have some clues on this problem.  Instead, I'll open a new issue to track that and point some AIX developers at it.

Note that there's still a problem with p521 on AIX when configured with enable-ec_nistp_64_gcc_128:

I opened issue #15821 on this.  It has explained that this isn't expected to work on big-endian systems.  It is documented in INSTALL.md.  I've suggested a patch to actually make the build fail in this case.

24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set.  Please review the updates and set the label manually.

Second review needed.

Even with these changes I'm still unable to pass tests on aix64-gcc target:
bash-4.3$ make test TESTS='test_enc'
        make depend && make _tests
        ( SRCTOP=.  BLDTOP=.  PERL="perl"  FIPSKEY="f4556650ac31d35461610bac4ed81b1a181b2d8a43ea2854cbae22ca74560813"  EXE_EXT=  perl ./test/run_tests.pl test_enc )
00-prep_fipsmodule_cnf.t .. skipped: FIPS module config file only supported in a fips build
Files=1, Tests=0,  0 wallclock secs ( 0.00 usr  0.00 sys +  0.08 cusr  0.00 csys =  0.08 CPU)
Result: NOTESTS
20-test_enc.t .. 1/?
aes-128-cbc: unable to load provider legacy
Hint: use -provider-path option or OPENSSL_MODULES environment variable.
00000001:error:12800067:DSO support routines:dlfcn_load:could not load the shared library:crypto/dso/dso_dlfcn.c:118:
00000001:error:12800067:DSO support routines:DSO_load:could not load the shared library:crypto/dso/dso_lib.c:162:
00000001:error:078C0105:common libcrypto routines:provider_init:init fail:crypto/provider_core.c:658:name=legacy
../../util/wrap.pl ../../apps/openssl aes-128-cbc -bufsize 113 -e -k test -provider-path ../../providers -provider default -provider legacy -in ./p -out ./p.aes-128-cbc.cipher => 1
not ok 3 - aes-128-cbc
# ------------------------------------------------------------------------------
#   Failed test 'aes-128-cbc'
#   at test/recipes/20-test_enc.t line 70.

I'll file that in as a separate issue.

I'll file that in as a separate issue.

Actually it is exactly the same failure mode as in #13336

I'll file that in as a separate issue.

Actually it is exactly the same failure mode as in #13336

I'll mention that to AIX developers to see if they can fix it...

#15828 fixes this

2021 5:55, 5:55, Martin Schwenke @.***> napsal/a:

I'll file that in as a separate issue.

Actually it is exactly the same failure mode as in #13336

I'll mention that to AIX developers to see if they can fix it...
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/openssl/openssl/pull/15798#issuecomment-864350757

Actually it is exactly the same failure mode as in #13336

I'll mention that to AIX developers to see if they can fix it...

#15828 fixes this

Indeed!  :-)

This pull request is ready to merge

Merged, thanks for the fix.


Changing Area crashes the game with new update

Trying to switch areas crashes the game. Highly reproduceable it seems

In the process I'll try disabling mods, see if it conflicts

Whoops. Fixed it


French translation is not available on Windows/Stand alone version

It appears the the locale is not properly detected on Windows, so that the application is not translated for example on a french locale Windows install.
The workaround is simple:

Add an environment variable named "LANG" and set it to "fr"
Or in a batch script or from the command line: set LANG=fr

This is apparently fixed in pyinstaller V6.2.0!


work on the style guide for the user interface

work on the style guide for the user interface of the website

I have designed on the desktop and mobile version of the profile pages and sign in page.


Version of library in requirements.txt

Hi,
Thanks for sharing your codes.
I try to install your codes. However, without specifying the version in the requirements.txt file, the default installation is the latest version. There are compatibility issues during the installation process. Could you please specify the versions in the requirements.txt file?
Thank you in advance.

Hi, thank you for raising this. Just updated in this commit.

Hi, thank you for raising this. Just updated in this commit.

Thanks.


Has this gem eaten anyones cat, ever?

If no, is it time yet to remove the disclaimer from the README?

It's experimental and may eat your cat. Don't trust it in production systems.

I mean, I can't rule it out.


Dispatch Card.add_label based on argument type

Select the Trello API based on the argument type:

pass a dictionary to create a new label,
or pass a label instance to add an existing label.

The second API returns a list of label ids, while the first
returns the JSON for the new label.

I meant to have a better branch name for the PR, but this will do ...

Thanks for all the contributions

Thanks for all the contributions

Welcome, thanks for merging!


Improved error handling in message parser

Communicates errors from message_parser to the node more precisely so errors can be logged.

LGTM, This improves the errors generated from message_parser


Trouble with basic example

Hi, I am following the example from the README, but getting this error:
PaginationWrapper.js?8937:37 Uncaught TypeError: Cannot read property 'find' of undefined(…)
It seems that state.pagination() is undefined.
Do I need to include a reducer for this library in my store by any chance?

Yes! This is admittedly missing from the README (my apologies), but it is documented here
https://sslotsky.gitbooks.io/violet-paginator/content/introduction.html

Just added it to the README, thanks for the nudge!
https://github.com/sslotsky/violet-paginator/commit/06eb8747093f84aaa175398070a4cd8a51d5b73e
I'll keep this issue open until you get your basic example working. That will help illuminate anything that might be lacking in the initial setup guides and allow us to track them in one place.

hey @sslotsky, thanks.  Adding the reducer means I have pagination buttons appearing on the page, and it attempts to call the fetch action. So that's great progress!
I have an action creator being called for the fetch, which calls the API and then passes the response to an action - however, I don't know which state key that needs to be inserted into though?  This is probably more a general redux question than anything. My understanding of redux is tenuous at best!

@markau You actually don't need to dispatch your own action when you receive the response. violet-paginator does that for you. You just need to make sure that violet-paginator knows how to read the response.
There are multiple ways that you can tell violet-paginator how to read the response. The sections on single list configuration and global list configuration should help guide the way.

Note that if resp.data already looks like this when it comes back from the server:
results: [{ ... }, { ... }],
total_count: 2

then violet-paginator will already be able to read it with no configuration necessary. However, if it looks different than that, you'll need to use one of the techniques described in the configuration docs.

I meant to say that I did RTFM and work some of that out. Thanks!
Postman shows the API response as:
{
  "data": {
    "results": [
      {
        "firstName": "bob",
        "lastName": "smith"
      },
      {
        "firstName": "george",
        "lastName": "costanza"
      }
    ],
    "total_count": 2
  }
}

In such a case, I believe I should use resultsProp="results" (although I suspect results is the default prop name).
I have headers set as:
  headers() {
    return [{
      field: 'firstName',
      text: 'First Name'
    }, {
      field: 'lastName',
      text: 'Last Name'
    }]
  }

So I think I should be seeing some data. Must be close now! Can you just let me know if you spot an error above, otherwise I will keep debugging!

btw I am consuming the API with:
return fetch(url)
.then(response => response.json())

Your example looks correct to me, and yes, resultsProp is set to "results" by default so you shouldn't need to override.
As far as your API consumption I'm not familiar with calling response.json(). Perhaps this is just something different about the libraries we're using to fetch. Normally I wouldn't attach a .then handler at all if the response is already formatted correctly:
export function fetch(pageInfo) {
  return fetch(url, pageInfo.query);
}

Are you seeing any errors of any sort? Or is your data table simply not displaying your results? Feel free to point me to a repo if you decide you're stuck.

Thanks mate. I'm sure it's me and not the library. I am using the wg-fetch library. The promise is returning the JSON I outlined above, but there must be a problem (it is not displaying results on the page).  Using Redux Devtools I see that this action is being dispatched:
@@violet-paginator/RESULTS_UPDATED_ERROR
And that:
state.pagination.0.results = []
I'll have a break and another look at it. Thanks for your help so far!

Looking at it again, I'm suspecting that you might need to do this:
export function fetchRecords(pageInfo) {
  return () => fetch(url, pageInfo.query).then(resp => resp.json().data)
}

The way the wg-fetch library is loading the data must be the problem - the promise seems to not be resolving. Is there a better library to use to load data? (I can't use native JavaScript fetch() because it doesn't seem to work in IE.) I've been perfectly happy with wg-fetch on this project - using it with redux-form for posting data.
I added some debugging to fetchingComposables.js:
    return promise.then(function (resp) {
      console.log(resp);
      <snip>
    }).catch(function (error) {
      console.log(error);
      <snip>
    });

Those two console.log() show this respectively:
undefined
TypeError: Cannot read property 'data' of undefined(…)
To ensure completeness for what I guess is now a bug report :smile: :
The data is being returned from the API via:
        return fetch(url)
        .then(function(response) {
          return response.json()
        })
        .then(function(json) {
          console.log('parsed json', json)
        }).catch(function(ex) {
          console.log('parsing failed', ex)
        })

Postman shows the response as:
{
  "data": {
    "results": [
      {
        "firstName": "bob",
        "lastName": "smith"
      },
      {
        "firstName": "george",
        "lastName": "costanza"
      }
    ],
    "total_count": 2
  }
}

The component is implemented on the page as:
  headers() {
    return [{
      field: 'firstName',
      text: 'First Name'
    }, {
      field: 'lastName',
      text: 'Last Name'
    }]
  }

  render() {
    const { fetch } = this.props
    console.log(this.props);
    const paginator = (
      <VioletPaginator listId="recipes" fetch={fetch} />
    )

    return (
      <section>
        {paginator}
        <VioletDataTable listId="recipes" fetch={fetch} headers={this.headers()} />
        {paginator}
      </section>
    )
  }

Probably my best bet is to try stepping through your code myself. Do you have a link to a repo that I can clone?

Ahh yes, of course. I'll try to replicate in a minimal and clean solution that I am free to post publicly (it's fairly deep in a work project.)

Thanks. Although I'll agree that the fact that your response object seems to be undefined is highly suspect. Definitely seems like whatever problem you're having is occurring before the data gets to violet-paginator

I tried a different http library and got it working 😀
It works with both libraries; the necessary step was as you suspected, the api response has to be manipulated so that the promise returns a data structure of Object {data: Object}, i.e. return response.data not return response.  That was simpler to do with Axios so it got me to the right answer faster.  I could also change the API to return an appropriate data structure. I tried all of these things but I guess not in the right combination.
Thanks for your time, and this sweet library!  I can't wait to start using it.


The agent returned an empty TTS on calling TransactionRequirements constructor

I am always getting the following error on saying "check transaction with google payment":
"The agent returned an empty TTS"
Can you please let me know what is the issue?

Same here.
And it returns  "Could not request transactions check with Google payment" in response

So did you get any solution for this?
I think this is happening because of the unsupported countries:
https://developers.google.com/actions/transactions/digital/dev-guide-digital
From where are you invoking your skill?

No, I have not got the solution yet.
I'm testing Simulator in English, the location sets US.
And I'm doing Physical one.
hmm..

arg.resultType are returning OK if it is transaction_check_action Intent,
But returning USER_ACTION_REQUIRED when it using transaction_check_google Intent.
transaction_check_complete requires arg && arg.resultType ==='OK',
https://github.com/actions-on-google/dialogflow-transactions-nodejs/blob/418ced27d8ea2c384358069917abcfd8084bd220/functions/index.js#L76
If it is not OK, then the code returns conversation close.

I'm not sure what kind of action should we or user do.
https://developers.google.com/actions/reference/rest/Shared.Types/ResultType

Any updates?
I am still returning USER_ACTION_REQUIRED and using Stripe for gateway.

Make sure you are testing out transactions on a mobile device -- testing transactions via the simulator isn't currently supported.

The sample has been significantly updated recently so I recommend going through from the beginning with the latest changes.


API Endpoint is no longer available

I'm getting the following when trying to use the workflow. Is this still something you're supporting?
This API endpoint is no longer available. Please refer to our documentation to upgrade your client to use the latest API version: https://developer.todoist.com

This is working perfectly fine for me, no issues. Can you manually create a task from the command line? (tod -t )
If not, do you have the latest version of https://github.com/alanvardy/tod installed? This is just a wrapper for that; it passes the alfred arguments and items to the tod client.

If you're still having issues, please reproduce the issue with Alfred debugging enabled (open up alfred preferences, select the workflow, then click the bug icon and reproduce the issue while it says "Debugger running:") and post the log.

This is working perfectly fine for me, no issues. Can you manually create a task from the command line? (tod -t [task name])
If not, do you have the latest version of https://github.com/alanvardy/tod installed? This is just a wrapper for that; it passes the alfred arguments and items to the tod client.

I think that's what it is. i'm updating tod now and I'll keep you updated. Thanks.

I noticed you also opened a bug against moranje that appeared the same - FYI we are entirely different projects and code, so please ensure you don't have us both enabled or are using both (or if you are, you are using different Alfred keywords)

TOD wasn't updated. my bad. Thanks for the help

Good to hear you got it figured out!


Fixed errors for stencil

I have run into the same LAME not defined error. This PR fixes the error. Thanks @nikolaytoplev.

This file is generated by our build process. If we merge this, as soon as we build/deploy a new version, this will get erased.

I had to copy this built file and paste it directly into my project in order for it to work.
Not a great solution since I lose all the npm package benefits, but it works until this lib works out how to handle the issue.

Please merge this))

Great!
Thanks for your efforts.

Please merge this

Please merge this

Please merge this

Can we pls merge this if this fix is working fine

Untill admin approves changes, you can use
npm i mic-recorder-to-mp3-fixed
and can be used as:
import MicRecorder from 'mic-recorder-to-mp3-fixed';
I have merged the 32 in this package.
Thanks


Prepare for release

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.ResourceManager.ApplicationInsights


Flow incorrectly reporting possibly undefined value

This code
// @flow

type T = {
	s? : string
}

function f(t:T) {
	if (t.s == null){
		return "";
	}

	if (t.s.indexOf("foo") != -1){
		return "bar";
	}

	return t.s[0];
}

gives me this error
js/test.js:21
 21: 	return t.s[0];
     	       ^^^^^^ access of computed property/element. Computed property/element cannot be accessed on possibly undefined value
 21: 	return t.s[0];
     	       ^^^ undefined

If I replace condition with if (t.s.length < 2) or leave only last return everything works great. Some other cases:
if (t.s.charCodeAt(0) != 13) - bad
if (t.s.charAt(0) != 'a') - bad
if (t.s.substr(0) != 'a') - bad
if (t.s[0] != 'a') - good
That's flow 0.34.0 on linux.

And if I remove T completely, and make it function f(s?:string) work fine also.

This is because calling functions (such as indexOf) can potentially invalidate previous checks. Before you check some value you can assign it to local const to avoid this.

Yeah, damned pessimistic calls. But why, especially for internal types? Anyway every property can be hidden by getter and/or Proxy, and trigger function call.

This seems one of the most misunderstood / frowned upon feature of Flow:

https://github.com/facebook/flow/issues/2728
https://github.com/facebook/flow/issues/2704
https://github.com/facebook/flow/issues/2693
https://github.com/facebook/flow/issues/2602
https://github.com/facebook/flow/issues/2513
https://github.com/facebook/flow/issues/2318

Just ran into this with .test on regular expressions with:
opts.ignoreCustomPatterns.test(basename) || opts.ignoreCustomPatterns.test(path)

This is because calling functions (such as indexOf) can potentially invalidate previous checks. Before you check some value you can assign it to local const to avoid this.

Yeah, I follow this and the flow stop giving this error.


Config.DefaultGoFile

Codecov Report

Merging #159 (2b05e63) into main (45d8c14) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #159   +/-   ##
=======================================
  Coverage   94.82%   94.82%
=======================================
  Files          15       15
  Lines        5928     5931    +3
=======================================
+ Hits         5621     5624    +3
  Misses        236      236
  Partials       71       71

Impacted Files
Coverage Δ

package.go
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


remote labeling

Sorry for the ignorance, can I run this remotely? This is, using a sever - client paradigm or similarly?

Yes. See #31.


Cleaned up the output

Fixed few misstyped words.
Made the output a little cleaner, print the hostname and the number of files starting with 'file' in /tmp directory.

for server in controlplane node01; do ssh $server 'ls /tmp/file*'; done
for server in controlplane node01; do ssh $server 'hostname; ls /tmp/file* | wc -l'; done

Good catch.


secret question grammar fixes

I would propose changing the order of the questions since 4 of the first 5 questions are "what is your first name" which a user would perceive as a lack of creativity in creating questions

@antuz123 What do you think?


Error in density.default(df1) :    need at least 2 points to select a bandwidth automatically

When I run the following code using the sample data"procdata",error occurs:
library(findPC)
data(procdata)
sdev<-prcomp(t(procdata),scale. = T)$sdev[1:50]
head(sdev)
findPC(sdev = sdev,
number = 1:30,
method = 'all',
figure = T
)
Error in density.default(df1) :
need at least 2 points to select a bandwidth automatically
I don't know how to solve this problem

When I run the following code using the sample data"procdata",error occurs: library(findPC) data(procdata) sdev<-prcomp(t(procdata),scale. = T)$sdev[1:50] head(sdev) findPC(sdev = sdev, number = 1:30, method = 'all', figure = T )
Error in density.default(df1) : need at least 2 points to select a bandwidth automatically
I don't know how to solve this problem

Hello,
Please note that if you want to consider the top 30 PCs, use number = 30 instead of 1:30. The method does not work when you consider a very small number of PCs, but I have tested that it works for number = 5:30.
Best,


Add a nicer way to display array fields

We need a better way to display array fields where the view won't become cluttered if there are a ton of items in the array. The json-editor tabs (see below) are one choice, but we could also make a design where the tabs are full-width and open their content below when clicked.

Array items can now be collapsed easily (e7c326d8076e39b949482a8be20f450a30c278f1) and arrays support collapse management (73fa81200cb733a56fc034b7ff1977fc6114d4d1, collapse all other fields when uncollapsing a field).


how to create training example if my sentence is 25 words long. can i break sentence in 10 words long phrase.

@keshavkmr48 Please explain this why u think more then 10 words creates problem
did ur problem relevant  to Following Problem

Issue 57


VM NAT Setup: Instance MSFT_NetIPAddress already exists

Using the following instructions
https://github.com/Microsoft/Virtualization-Documentation/blob/live/virtualization/hyperv_on_windows/user_guide/setup_nat_network.md
The following appears in red
PS C:\WINDOWS\system32> new-netipaddress -IPAddress <IP_ADDRESS> -PrefixLength 24 -InterfaceIndex 17
new-netipaddress : Instance MSFT_NetIPAddress already exists
At line:1 char:1

new-netipaddress -IPAddress <IP_ADDRESS> -PrefixLength 24 -InterfaceInde ...

  + CategoryInfo          : InvalidArgument: (MSFT_NetIPAddress:ROOT/StandardCimv2/MSFT_NetIPAddress) [New-NetIPAddress], CimException
  + FullyQualifiedErrorId : Windows System Error 87,New-NetIPAddress

However
Everything works as expected, but I'm worried, because I don't know what went wrong exactly

Can you please run Get-NetIPAddress and check that this IP address is unique? It appears as though this IP address has already been assigned to the host.

Closing this issue due to inactivity. Please feel free to open this issue again if there is still something we can help with.