[Spaceship] Add support for applying custom EULA

Feature Request
Adding support for changing the default “License Agreement” with a custom EULA.
This is a duplicate of @max-ott’s (now closed) #14290 but I’ve added some implementation and workaround details.
Motivation Behind Feature

One of the few pieces spaceship is still missing.

Feature Description

This is a feature add, nothing should break because of this change.
App Store Connect defaults to apps using Apple’s default license but allows a custom license to be selected as well as allowing that license to be applied to all or a specific subset of territories.
Without seeing an active endpoint for this in Connect API, one possible implementation could be to add this functionality to Spaceship::Tunes::Application.
app = Spaceship::Tunes::Application.find('com.company.bundle-id')
app.license = "A very long amount of text…"
app.license_territories = "all" # or ['en-US', 'de-DE', 'es-MX', …]

Or maybe have a license hash
app.license = {
    license_text: "License text goes here",
    license_territories: [territory array]
}

And it’d be good to have a way to reset the license back to Apple’s default
app.remove_custom_license
# or
app.license = nil

Alternatives or Workarounds

I don’t know of any workaround short of directly accessing the Connect API for beta license agreements and even then I’m not sure there’s a way to see a normal (non-beta, non-TestFlight) license agreement.

I contacted Apple Developer support about this issue and was told there is no support for editing App Store license agreements, despite there being something similar for TestFlight.
Being that Spaceship (and Fastlane) are used as a cover for Apple’s raw APIs is this something that could be accomplished using the old screen scraping logic? Or has Spaceship completely transitioned to Connect API usage?


Environment variables are not being loaded properly

When using the ConfigLoader class in the Simple Java Mail library, environment variables are not being loaded unless a properties file (simplejavamail.properties) is present on the classpath. This issue prevents configuration via environment variables in environments where properties files are not used or cannot be placed on the classpath, such as containerized applications or cloud deployments.
Steps to Reproduce:
Ensure there is no simplejavamail.properties file on the classpath.
Set environment variables corresponding to configuration properties. For example:

SIMPLEJAVAMAIL_SMTP_HOST=smtp.example.com
SIMPLEJAVAMAIL_SMTP_PORT=587

Run the application that utilizes the ConfigLoader to load configuration properties.
Expected Behavior:
The ConfigLoader should load configuration properties from environment variables even when the properties file is absent.
Actual Behavior:
The ConfigLoader does not load properties from environment variables unless the properties file is found on the classpath. As a result, the application cannot be configured using environment variables alone.
Cause:
In the loadProperties(String filename, boolean addProperties) method of the ConfigLoader class, when the properties file is not found, the method returns without attempting to load environment variables or system properties. The environment variables are only considered when a properties file is successfully loaded, which is not the intended behavior.
Suggested Fix:
Modify the loadProperties method to ensure that system properties and environment variables are always loaded, regardless of whether the properties file exists. This can be achieved by passing an empty Properties object to the loadProperties(Properties properties, boolean addProperties) method when the properties file is not found.
Additional Information:

This issue affects users who rely on environment variables for configuration, especially in containerized environments like Docker or Kubernetes.
The priority of property resolution should be:

System Properties (System.getProperty)
Environment Variables (System.getenv)
Properties File (simplejavamail.properties)

Ensuring that environment variables are loaded correctly enhances the flexibility and usability of the library in various deployment scenarios.

Solution committed under #538.


Fix x86 detection error

Build error on intel sapphire rapids

Oops, not that silly copy-paste-error again... thanks for the fix


Background turns light grey instead of blurred?

Hi,
I have exactly the same issue that I have with MZFormSheetController.
https://github.com/m1entus/MZFormSheetController/issues/182
I've adding my viewcontroller to my navigation controller programmatically, rather than with my storyboard, although I don't know why that should make a difference.
I now have.
Any ideas?
UINavigationController *nav = [[UINavigationController alloc] initWithRootViewController:vc];

nav.navigationBarHidden = YES;

MZFormSheetPresentationController *formSheetController =
    [[MZFormSheetPresentationController alloc]
     initWithContentViewController:nav];
formSheetController.shouldApplyBackgroundBlurEffect = YES;
formSheetController.blurEffectStyle = UIBlurEffectStyleExtraLight;
// To set blur effect color, but uglty animation
//    formSheetController.backgroundColor = [[UIColor redColor] colorWithAlphaComponent:0.8];

[self presentViewController:formSheetController animated:YES completion:nil];

I fixed this problem with MZFormSheetController maybe the same applies here.

I'd like to re-open this as it doesn't matter what I do I have the same problem.
If I set shouldApplyBackgroundBlurEffect = YES I get a light grey color, if I don't set it, it respects the blurEffectStyle value. I'm using iOS 8.
Please help me.
:(
Thanks in advance.

Since MZFormSheetPresentationController relies on UIVisualEffectView  to show blurred background,  you're getting that grey background because your device (real or emulated) does not support blurring (see http://stackoverflow.com/questions/26411227/detect-if-device-properly-displays-uivisualeffectview).

Thanks for explanation. I am closing it.

it's still the case for me. my Base SDK is 9.2 and targeting 8.0, but still only have a dimming light instead of blurry effect

You will never get blur using UIVisualEffect on ipad 2 and iphone 4, ios version does,t matter because this devices don't support blur...

I used marypopin instead, think it may provide its own blur effect for those devices, can't recall

Yes it is possible using snapshot and blurry it but i don't wont implement it only for those devices

it was running on iPhone 6s and it didn't blur

i just found out it was a problem else where in my own code. sorry for the trouble and thanks for trying to help!

@JosephZZ what was the problem?

@natanrolnik I missed a line of code that the document specifies. It was setting some value to true I think.

When you turn on option in iPhone Settings called: Reduce Transparency for better contrast and readability you're gonna loose the blur effects.


Add recipe for AspNetCore.SpaTemplates

If I create a project using "dotnet new angular", I can debug both  the C# and Typescript code in Visual Studio 2017. But within Visual  Studio Code, I can only debug the C#. When I try to place a breakpoint  on any Typescript instruction, it says: "No symbols have been loaded for  this document".
Please see the following Stackoverflow post for more info: https://stackoverflow.com/questions/47598215/cant-debug-typescript-in-vscode-on-app-created-with-dotnet-new-angular

@johnpankowicz You'll also need to make a debug configuration for your Chrome debugger. See the instructions here https://github.com/Microsoft/vscode-recipes/tree/master/Next-js#configure-launchjson-file, and ignore Nodejs config.
To debug both .net core and Chrome at the same time, you can make a compound configuration, which is explained there to.
It would end up being a config like
   {
   "version": "0.2.0",
   "configurations": [
        {
            "name": ".NET Core Launch (web)",
            "type": "coreclr",
            "request": "launch",
            "preLaunchTask": "build",
            // If you have changed target frameworks, make sure to update the program path.
            "program": "${workspaceFolder}/bin/Debug/netcoreapp2.0/spa.dll",
            "args": [],
            "cwd": "${workspaceFolder}",
            "stopAtEntry": false,
            "internalConsoleOptions": "openOnSessionStart",
            "launchBrowser": {
                "enabled": true,
                "args": "${auto-detect-url}",
                "windows": {
                    "command": "cmd.exe",
                    "args": "/C start ${auto-detect-url}"
                },
                "osx": {
                    "command": "open"
                },
                "linux": {
                    "command": "xdg-open"
                }
            },
            "env": {
                "ASPNETCORE_ENVIRONMENT": "Development"
            },
            "sourceFileMap": {
                "/Views": "${workspaceFolder}/Views"
            }
        },
        {
            "name": ".NET Core Attach",
            "type": "coreclr",
            "request": "attach",
            "processId": "${command:pickProcess}"
        },
        {
            "type": "chrome",
            "request": "launch",
            "name": "Chrome",
            "url": "http://localhost:3000",
            "webRoot": "${workspaceRoot}"
        }
    ],
    "compounds": [
        {
            "name": "Full stack",
            "configurations": [".NET Core Launch (web)", "Chrome"]
        }
    ]
}

Let me know how things work.

@auchenberg Thanks a lot. That worked. I made just a couple minor changes to your sample launch.json. In the Chrome config, I have:  "webRoot": "${workspaceRoot}/wwwroot". And I changed the "url" port to "5000" to match what the C# for Visual Studio Code extension uses.
One issue is the app is launched twice, once in my open default browser and again in Chrome. I can avoid the first by setting "enabled" ...  to "false" for LaunchBrowser in the ".NET Core Launch (web)" config. So I may need to create a second version of ".NET Core Launch (web)" for when I am using the compound configuration.

@johnpankowicz Great, glad to hear you got it working!
I'll let this issue stay open, so we can add writing a dotnet core recipe to our backlog. In case you have time a PR with your working configuration would be much appreciated!

I added the PR right after you suggested a week ago. How often are these looked at?

Looks good, thanks for the PR @johnpankowicz!

@auchenberg - I have a couple issues in my README.md for the PR.
(1) A code block didn't get formatted. (In MY viewer it looked ok) I think a missing indent on the first line is causing the problem.
(2) My images are not showing. I copied how the Electron recipe did them , since those are also in the same folder as the Readme.md. EG: Electron uses "   " I used "![Typescript breakpoint](Typescript breakpoint.png)". Could the lack of an indent or a space in the filename have something to do with it? Again, it appears ok in my .md viewer.

@auchenberg - I created another PR. There were formatting problems in the Readme.md. (My particular .md viewer did not show these problems.) I believe they are fixed now.


BLDKCMF-7 Compliance Issues in Lightning, Fixed Review comments

BLDKCMF-7 Compliance Issues in Lightning, Fixed Review comments

Hi @woutermeek , Could you please review and merge this pull request?

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: silava673:x: Sukanya673silava673 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Possible linkLists_[i] out-of-bounds reads

While porting parts of the code to Rust to parse and extract a disk-saved hnswlib index, I found some unexpected panics in the equivalent Rust code of this section in searchKnn:
for (int level = maxlevel_; level > 0; level--) {
    // ...
   data = (unsigned int *) get_linklist(currObj, level);
   int size = getListCount(data);

   tableint *datal = (tableint *) (data + 1);
   for (int i = 0; i < size; i++) {
     tableint cand = datal[i];
     // ...
  }
}

Where get_linklist and getListCount are defined as follows:
linklistsizeint *get_linklist(tableint internal_id, int level) const {
  return (linklistsizeint *) (linkLists_[internal_id] + (level - 1) * size_links_per_element_);
 }

unsigned short int getListCount(linklistsizeint * ptr) const {
  return *((unsigned short int *)ptr);
}

In Rust, when reading the linkLists_[i] from disk, I use a Rust Vec as the equivalent to the raw char*, so for get_linklist I slice the linkLists_[i] Vec at offset (level - 1) * self.size_links_per_element_) as I presume that's the equivalent to the C++ above. However, this is often out of bounds. Is the C++ code doing an unchecked out-of-bounds read (i.e. adding to the linkLists_[internal_id] pointer beyond the length malloced)? It's possible I've misread or overlooked some of the source C++, so wanted to raise here first before I dived deeper.

hi @wilsonzlin, why not use the Rust implementation here:https://github.com/jean-pierreBoth/hnswlib-rs, also mentioned in the home page.
Thanks,
Jianshu

I currently don't need the algorithm itself, I'm doing some research on properties of the hnswlib-built graph, so I've copied a small amount of code over to load the data from disk in Rust. Although thanks for the pointer, might be useful once I do need to compare implementations in Rust down the road.

I think it works because the traversal starts at the highest level node and always finds a node at or above the same level, so max_level is always in bounds.


Make Thunder SDK Caches Configurable

The thunder_ripple_sdk has caching implemented around all of the device_info calls that are made to Thunder. This will make testing or local development with the Mock Device extension very difficult as there is no way to clear the cache after the first call of any particular method is made.
We need to add the ability to disable this cache in certain environments. This should be done by updating the extn manifest to have a property which enables or disables this cache.
I am not sure what the best way to express this is in the extn manifest file as this property would be generic to this specific extension. It also doesn't seem right to place the config in the device manifest. Maybe we need to have a settings field in the extn manifest where extensions can define their own options.

Right now we have a config field in the extension manifest for such requirements.
Here is an example
A distributor can set the
{
            "path": "libthunder",
            "symbols": [
                {
                    "id": "ripple:channel:device:thunder",
                    "config": {
                         "disable_device_info_caching": true
                     }
                    "uses": [
                        "config"
                    ],
                    "fulfills": [
                        "device_info",
                        "window_manager",
                        "browser",
                        "wifi",
                        "device_events",
                        "device_persistence",
                        "remote_accessory"
                    ]
                }
            ]
        },

Then one can do extn_client.get_bool_config("disable_device_info_caching")


WIP: ENH: optimize: large-scale constrained optimization algorithms [GSoC 2017]

Hi all!
This commit contains two solvers I implemented for my GSoC project.:

An implementation of a Byrd-Omojokun Trust-Region SQP method  that solves
equality constrained optimization problems of the type:
 minimize fun(x)
 subject to: constr(x) = 0

The underlying principles of this method are described in the following blog post (here).

An implementation of a trust-region interior point method described
that solves general nonlinear programming problems:
 minimize f(x)
 subject to: constr_ineq(x) <= 0
             constr_eq(x)    = 0

which uses the previously described SQP method as a substep. The underlying principle of this method can be found in another blog post (here).
Both methods are based on the projected CG algorithm (described here) and are appropriate for large and sparse problems.
I tested both solvers on several problems from the CUTEst problem collection (the results are described here). And while the performance (in number of iterations) is not as good as the one from the original paper yet, it came pretty close to it and could probably be improved with some fine tuning of the solver internal parameters. I will test the solvers from scipy in the same benchmarks latter and present the results here latter.
There are still a few missing features I will try to implement along the following weeks:

[x] Implement finite difference approximation in order to compute Hessian-vector product.
[ ] Quasi-Newton Hessian approximations

[ ] L-BFGS
[ ] BFGS
[ ] SR1

[ ] Integrate Nikolay's GSoC implementation of finite differences to compute Jacobian and gradient

But, even with these missing features, we decided to open request now, so the code can start to be reviewed.
I implemented the solvers into a separate interface minimized_constrained, an example of usage is presented here. This interface will probably have to be modified in order to be more coherent with the remaining solvers from scipy optimize package. Two possible routes are:

Include the new methods into the minimize interface.
Create separate interfaces for unconstrained and constrained solvers. In this case the other constrained methods (COBLYA and SLSQP) would be deprecated from minimize and moved to the new interface minimized_constrained.

We have started some discussion about this  on issue #7648 and, so far, we are tending toward the option (1). I will comment more about this in future comments (the pull request description is already getting too long).

We have started some discussion about this on issue #7648 and, so far, we are tending toward the option (1). I will comment more about this in future comments (the pull request description is already getting too long).

I suspect that the comments thread on this PR will grow long, so it would be good to put the key points in the PR description, and edit that description once in a while when the discussion progresses.

@antonior92 take care of build errors (some of them are related to code style).
By the way why wouldn't you try using one popular Python IDE, it works with the whole scipy package really smooth and code insights, style checking and navigation are amazing.

Yes, all new submodules. The reason why there are modules without
underscore prefix, is due to backward compatibility issues --- what
exactly is public API was not defined for many years, so there is code
out there that imports stuff from random places. The gain/harm ratio
seems like it's best to leave the old modules as they are for the most part.

@rgommers I will try to keep the PR description updated along the way.
@nmayorov I actually have a PEP8 checker in Emacs, I will fix those violation today, as well as the other build errors. I have tried a few Python IDE but I always go back to Emacs because I am familiarised with the shortcuts and with the environment. Furthermore, the Python environment in Emacs does have many IDE features.

I am getting the build error:
ImportError: No module named _equality_constrained_sqp

on all continuous integration tools. I am having trouble reproducing this error in my personal computer. Does anyone have any suggestion on how to fix this?

@antonior92: you need to add config.add_subpackage('_equality_constrained_sqp') to optimize/setup.py and add a setup.py to the new subpackage. You can probably copypaste from _lsq/setup.py. You also need to add __init__.py in the tests/ folders you add, and also mention them in setup.py of the subpackage.

To test locally, you can run python runtests.py -t scipy.optimize to test that the installed package works.

Thank you a lot @pv! I will fix it.

@antonior92
Uhm, I'm not sure whether I should pick on this, but generally your commit messages violates 2 (sort of) rules in scipy:

Typically a message is not ended by a period (ok, in fact both "styles" are used, so do as you like, but I prefer without a period).
Typically a message should have a "tag" (like ENH you already used), see here https://docs.scipy.org/doc/numpy-dev/dev/gitwash/development_workflow.html#writing-the-commit-message

Maybe you could go through your commit history (using interactive rebase) and

Add tags.
Make messages more precise and clear.
Perhaps merge several related commits into one (if appropriate).

As for the general review. I think we need some sort of strategy, like account for what you think needs to be reviewed.
To start with: which module you are not sure about whether it has good design, naming choices, docstrings, etc.?

Nikolay, I will rebase and improved my commit history accordingly, thanks for the suggestion.
About the code review: the file _constraints.py is the one in most need for some revision and refactoring. I think we should start the revision with it.

I think regardless of its functionality keywords and parameters are named a bit user-unfriendly and (if we ever bothered with it) non-Pythonic. Take constr_ineq: it is pretty difficult to remember before typing it 6 times. Was it const_ineq or constr_ineq or was it ineq_const or ineq_constr?
Same applies to the optional feasible_constr. I think enforce_feasibility is a pretty clean keyword and easier to remember for my taste instead.

enforce_feasibility is indeed a better name, I will adopt it.
A little clarification about the constraint class, I intend to make the classes:
NonlinearConstraint
LinearConstraint
BoxConstraint

public interface for passing constraints, with documentation and examples. The class CanonicalConstraint is more like a low level class containing the parameters in the format I need for equality_constrained_sqp and tr_interior_point solvers.

I need the derivative approximations before I can implement the larger tests I planned to perform, so I thought I'd look at the documentation in the meantime.
I checked https://circle-artifacts.com/gh/scipy/scipy//artifacts/0/home/ubuntu/scipy/doc/build/html-scipyorg/index.html but the documentation for minimize_constrained doesn't show up there (as it should).
@pv, please check me here, as I'm copying your advice to me (in hope of saving you some typing) but to fix this, @antonior92, I think you need to add a line for minimize_constrained in \optimize\__init__.py:
Local Optimization
------------------

.. autosummary::
   :toctree: generated/

   minimize - Unified interface for minimizers of multivariate functions
   minimize_scalar - Unified interface for minimizers of univariate functions
   minimize_constrained - lorem ipsum dolor sit amet
   OptimizeResult - The optimization result returned by some optimizers
   OptimizeWarning - The optimization encountered problems

Also, sorry if I'm just not finding them, but where are your unit tests for minimize_constrained? I see test_projections.py, test_qp_subproblem.py, and test_constraints.py but those don't seem to test minimize_constrained.

I will fix the documentation Matt, thanks!
About the unittests for minimize_constrained: I will include the same problems from here and test the minimize_constrained on them. I haven't include them yet because I haven't decide which format to use on constrained optimization benchmark problems and wanted to consult you all first.
I think the best option is to define each optimization problems as:
class OptimizationProblemExample(OptimizationProblem):

    def __init__(self, ...):
            self.x0 = ...
            self.x_opt = ...
            self.f_opt = ...

    def fun(self, x):
        ...
        return f

    def grad(self, x):
        ...
        return g

    def hess(self, x):
        ...
        return h

    @property
    def constr(self)
        nonlinear = NonlinearConstraint(...)
        linear = LinearConsraint(...)
        ...
        return (nonlinear, linear_constr)

what do you think?

I tried some variations on the following simple problem:
from __future__ import division, print_function, absolute_import
import numpy as np
from scipy.optimize import minimize_constrained, NonlinearConstraint, BoxConstraint
fun = lambda x: (x[0]-1)**2 + 1
grad = lambda x: np.array([2*x[0]-2,0])
hess =  lambda x: np.array([[2,0],[0,0]])
box = BoxConstraint(("greater", [0,0]))
x0 = np.array([0,0])
result = minimize_constrained(fun, x0, grad, hess, (box))

For this problem, minimize_constrained succeeds, reporting
x* = [ 1.          2.85094433]
obj = 0.999999989272

where the second decision variable is (understandably) an arbitrary value.
If I eliminate the box constraint, I get the error: TypeError: __init__() missing 1 required positional argument: 'feasible_constr'
So it appears that unconstrained problems still (we discussed this before) still aren't working. I think it is important for trivial problems like this to be solved correctly so that new users of the functions can test their understanding of the syntax with very simple examples.
Also, while grad is allowed to return a float or a list, hess must return a Numpy array. If it returns a list of lists:
File "/Users/matthaberland/Desktop/ScipyDev/scipy/scipy/optimize/_constraints.py", line 500, in matvec
    result += h.dot(p)

AttributeError: 'list' object has no attribute 'dot'

Similarly, if I eliminate the second variable from this problem entirely, hess cannot be a list of lists ([[2]]) or a float (2); same sort of error. If there is a dimension mismatch anywhere, I get an error deep within the code. These sorts of cases should either be detected before the solve routine actually begins (to produce a an error message that is easier to understand) or, better, fixed automatically (where possible).

Re: testing can you elaborate on how you would actually make them tests so that they run with PyTest? For example, the most obvious way to write tests is to write a bunch of functions with names beginning with test, so in that case you might write a function test_example, within it instantiate an o = OptimizationProblemExample(), and run minimize_constrained with o's members as arguments. My question is how these problem definition classes fit into the test framework.

Just fixed the problem for unconstrained problems sorry about that.
The following piece of code does provide the correct result for me:
from __future__ import division, print_function, absolute_import
import numpy as np
from scipy.optimize import minimize_constrained, NonlinearConstraint, BoxConstraint
fun = lambda x: (x[0]-1)**2 + 1
grad = lambda x: np.array([2*x[0]-2,0])
hess =  lambda x: np.array([[2,0],[0,0]])
box = BoxConstraint(("greater", [0,0]))
x0 = np.array([0,0])
result = minimize_constrained(fun, x0, grad, hess)

# Print results
print('x* = ' + str(result.x))
print('optimality = ' + str(result.optimality))
print('c violation = ' + str(result.constr_violation))
print('niter = ' + str(result.niter))
print('f evals = ' + str(result.nfev))
print('CG iters = ' + str(result.cg_niter))
print('total time = ' + str(result.execution_time))

About the unittests: I need a collection of optimization problems in order to write the unittests for minimize_constrained. I would not run them with pytest, I would only call them from inside the unittests.
I want to put this collection of optimization problems in a common format easy to be reused when needed and I was asking what format do you think would fit. Future optimization problems could reuse the same format.

Thank you a lot for the detailed code review Matt! I will correct the documentation accordingly to your comments.

I will try to improve the input validation/cleanup as well

Added "WIP:" prefix to the PR title, please remove it when you think it's at a stage when it's close to mergeable.

I am getting test failures on TravisCI that do not appear when I try to run on my personal computer.
More specifically, on the calls to  assert_raises(...) I get an import error "Need nose >= 1.0.0 for tests ..."

More specifically, on the calls to assert_raises(...) I get an import error

I imagine that is https://github.com/scipy/scipy/pull/7777. A rebase should fix it.

Ahh, ok! I will try it out. Thanks!

Note also that using dec and run_module_suite from numpy.testing should also not be done any more.

Ok, I am still getting one building error that I cannot explain.
For python 3.6 building it complains about the warning filter on line 795 'optimize/optimize.py' (which I have not altered).

The relevant part is this:
SyntaxError: invalid escape sequence \h
path       = PosixPath('/home/travis/build/scipy/scipy/build/testenv/lib/python3.6/site-packages/scipy/optimize/_minimize_constrained.py')

Thank you again @pv

Iterative refinements are okay for 64-bit. Only 32-bit has problems and that's because of an FPU mode change. I think.

Yes, it does not fulfill the required numerical precision on 32 bits machine.
In the last commit I included some patch in order to skip iterative refinement tests when working on 32 bits platforms. Now it is passing all test on continuous integration.

Win32 includes both 64 and 32 bit. We only want it allowed to fail on 32 bit.

If you don't know a priori what the error should be, a better fix may be to bump the tolerance upward. The accuracy of openblas etc appears to vary in practice between platforms --- the test is testing mainly the optimization routines, and not so much the accuracy of the linear algerbra libraries, so perhaps the current tolerance requirement is too strict? (Also, using assert_allclose is preferable to assert*_almost_equal, so that both relative and absolute tolerances can be specified, in standard scientific notation.)
The inadvertent FPU mode changes may be related. The fixes will be in next numpy releases only though, so not immediately testable on the CI without manual work.

I did't knew Win32 included both 64 and 32 bits, thanks for the heads up @xoviat :)
I will see if I can make the requirements less strict, this will probably require some study, because if they are not strict enough I do not test the interactive refinements, whose only purpose is to improve accuracy.

Great to see the recent commits, Antonio! It seems so close and it will be a terrific addition!

Thanks Matt :)
I needed to finish and submit some papers I have worked on during my masters and I didn't manage to conciliate ending the GSoC project with these more pressing activities. Nevertheless, I have more free time now and I will try to use this time to advance with the implementation. I will organize myself for this PR to be ready for SciPy 1.1.

Hi all!
I have integrated the solver to the standart minimize interface. You can vizualize the documentation here:
https://4938-1460385-gh.circle-artifacts.com/0/home/ubuntu/scipy/doc/build/html-scipyorg/generated/scipy.optimize.minimize.html#scipy.optimize.minimize
I called the method trust-constr. This methods swiches between the two solvers I have implemented during my GSoC. I have decide to use a single method to both solvers because they are applicable in complementar situations.
In order to keep this pull request (PR) more manageable, I think it is best not to try to include the features I have implemented for the nonlinear solver available to all the other solvers at once. Hence lots of features will be available at first only for trust-constr method. Latter, in a sequence of PRs, I should include these features for other methods as well.
Some examples of features that I intend to implement in latter PRs:

Make {'3-point', 'cs'} finite difference estimation available for estimating the Jacobian matrix for CG, BFGS, Newton-CG, L-BFGS-B, TNC, SLSQP, dogleg, trust-ncg, trust-krylov and trust-exact methods;
Make {'2-point', '3-point', 'cs'} finite difference estimation available for estimating the Hessian matrix for CG, BFGS, Newton-CG, L-BFGS-B, TNC, SLSQP, dogleg, trust-ncg, trust-krylov and trust-exact methods;
Make quasi-Newton approximations available for Newton-CG, dogleg, trust-ncg, trust-krylov, trust-exact and trust-constr;
Allow Newton-CG, trust-ncg, trust-krylov to use Hessians represented by sparse matrix and Linear Operators;
To uniformize the use of bounds;
To allow the constraint classes BoxConstraint, LinearConstraint, NonlinearConstraint to be used be COBYLA and SLSQP method as well;
To allow a more complete  use of the callback function for other methods too (e.g. finish PR #7425 ).

When all these additional features have been included for the other methods we will have a better integration between the methods and a cleaner interface. Nevertheless, I believe we should left them for latter on, in order to have small and easier to review PR. Furthermore, some of these features will require me to modify well tested SciPy code and it would be better if they are commited separately and reviewed carefully in order to avoid any problems latter.
What do you guys think?

Nikolay, based on your comments I have made a few modification on my class structure. The idea is to create a virtual interface HessianUpdateStrategy.
class HessianUpdateStrategy(object):

    def initialize(self, n, approx_type):
        raise NotImplementedError()

    def update(self, delta_x, delta_grad):
        raise NotImplementedError()

    def dot(self, p):
        raise NotImplementedError()

    def get_matrix(self):
        raise NotImplementedError()

A new class:
class FullHessianUpdateStrategy(HessianUpdateStrategy)

contains the methods that are common to BFGS and SR1 strategies.
I think this way we have a better separation between what is the interface and more specific methods that have as unique purpose to avoid duplicate code in BFGS and SR1 classes, but are not very general (e.g. would not be used in L-BFGS implementation).

For some reason I am not able to create a link to HessianUpdateStrategy docstring the same way I did for BFGS and SR1 (see bellow).
https://5051-1460385-gh.circle-artifacts.com/0/home/ubuntu/scipy/doc/build/html-scipyorg/optimize.html

For some reason I am not able to create a link to HessianUpdateStrategy docstring the same way I did for BFGS and SR1 (see bellow).

That's because it's not a public object. Did you want it to be? Then you'll have to put it in __all__ somewhere and ensure it's exposed as optimize.HessianUpdateStrategy.

Ralf, thank you for your comment. I have  included it in __all__ and I have checked it is exposed as optimize.HessianUpdateStrategy. The link to the docstring was not found however: https://5057-1460385-gh.circle-artifacts.com/0/home/ubuntu/scipy/doc/build/html-scipyorg/optimize.html
Did I do something wrong or do you think it is not appearing for some other reason?

I just pushed a commit to your branch that fixed the doc link. The problem was that HessianUpdateStrategy was not included in any toctree, so its page wasn't rendered and hence could not be linked to.

Thank you very much Ralf. This fixed the problem.


Dexie Type definitions seem to be broken

Today I wanted to use Dexie.d.ts to get the type definitions for Dexie. I grabbed Dexie.d.ts using the TypeScript Definition Manager (typings):
typings install github:dfahlander/Dexie.js/src/Dexie.d.ts#d271a952f2fed858bd6a25bfb2c4f5e8a55eaba3 --save

After that I referenced Dexie.d.ts:
/// <reference path="/typings/modules/Dexie/index.d.ts" />

But my editor (WebStorm 2016) complains that Dexie is an unresolved type. I then checked the Dexie.d.ts file in my editor and noticed that it looks broken. Might this cause the issue that Dexie cannot be resolved?
Screenshot:

typings tool is the one inserting the first lines (https://github.com/typings/typings/blob/master/docs/faq.md#types-of-typings). I don't know why webstorm complains about it and whether the format of Dexie.d.ts has to change in order for typings to invoke its lines there.
So, either this is a webstorm/typings issue, or it's something that I should do something about, but it's typing's lines that it complains about.
If someone could advice me of how to properly deliver the typings file for today's best practice, I would be very happy ;)

There are some Best practices here but I also pinged the typings team: https://github.com/typings/typings/issues/563 — Let's see where it gets us. :smiley:

Thanks for that! As I've understood, DefinitelyTyped is going away in favour of typings, right? Would be nice to get some feedback from the typings team about this.

Looks like it works when I use:
/// <reference path="../../typings/modules/Dexie/index.d.ts" />
import Dexie from "Dexie";

function testTypings() {
  var db = new Dexie('MyDatabase');
  ...
}

But WebStorm still shows an error for the declare module 'Dexie'declaration in Dexie\index.d.ts.

Seems to be a jungle on how to deliver a d.ts file with a library that just works, or I am doing some trivial thing wrong.
I followed the angular2 quickstart sample and tried to use dexie with it. Typescript compiler actually picks up dexie out-of-the-box. No need for typings or tsd to make that work, because dexie.d.ts is delivered with the dexie package and referenced in package.json through the typings property.
But according to https://github.com/typings/typings/issues/142, typings tool SHOULD be used also when having the d.ts file delivered with the package, which surprises me a lot. I feel the typings team knows some secrets that I would need to know as well so I made a comment on that issue about this. Hope to hear back from them soon.

Ok, so I got my sample working perfectly well without any typings or tsd tool. I'm using Visual Studio Code (the simple JS and TS code editor from Microsoft) and also in WebStorm 11. It just picks up Dexie as is. I had problems getting it to work runtime, but I found out that it was only to configure systemjs properly in systemjs.config.js:

maps: Add  'dexie':                      'node_modules/dexie/dist/dexie.js'
packages: Add 'dexie':                      { format: 'amd'}

So, basically, you wont need to use typings at all. But maybe I'm just lucky?

Got it confirmed that we shall not use typings or tsd or any other tool to make use of dexie's d.ts files and that they are in the correct shape, without define module clause.
Conclusions:

Dexie's type definitions do not need any CLI tool like typings or tsd. Just make sure to have "moduleResolution": "node"in your tsconfig.js. Typescript will find the correct d.ts file automatically (located at dist/dexie.d.ts), and so does WebStorm and vscode at least.
If using AMD (requirejs) or SystemJS, you need to configure them to find dexie.js from node_modules/dexie/dist/dexie.js.
If using System.js, your systemjs.config.js file must include dexie in map and packages to tell it that dexie is an 'amd' or 'cjs' module (both will work because it's an UMD module):

System.config({
    ...
    map: {
        ...,
        'dexie': 'node_modules/dexie/dist/dexie.js',
    },
    packages: {
        ...,
        'dexie': { format: 'amd' }
    }
});

Thank you for clarification. It's worth a lot to know that. Maybe you should add this info to Dexie's wiki (if not already done)? Thank's a lot, David!


Fix: Add space between 'More Events' button and heart icon (#1435)

This PR resolves issue #1435 by adding appropriate spacing between the 'More Events' button and the heart icon. The change ensures better readability and an improved visual layout.
Screenshot
Before

After

good work @gaurisuthar

@gaurisuthar These small changes can't be addressed as contribution. Find another issue or feature to contribute to. Thank you!


[Bug]: Issues with the correct CPU quota detection on k8s v.126

Environment

VerneMQ Version: <IP_ADDRESS>/1.13.0
OS: VerneMQ docker image (built using vernemq/docker-vernemq github repo) deployed on kubernetes v1.26
standalone

Current Behavior
Once VerneMQ starts, it deploy several scheduler threads (1 for each node CPU), despite its k8s behaviour restricts it (e.g.: 400m available for the container).
Container CPU reaches quickly 95-100%.
This didn't happened on kubernetes v1.25 (we see just 1 scheduler thread at starts that it might scale up if load becomes heavier), and the only difference is that v.126 enforces cgroups v2 usage while v1.25 use the old cgroups.
Expected behaviour
We expect VerneMQ to correctly detect its own CPU quota on k8s v1.26 and keep the same behavior observed with the previous kubernetes version (k8s v1.25).
We noticed that in Erlang 26/OTP 14.1 a fix to a bug in the correct detection of the CPU quota is reported in the changelog, I don't know if it might be helpful to solve our issue,
Configuration, logs, error output, etc.
We added:
+S 2:1
In order to try to replicate the previous behavior, but we fear we might have issue on heavy loads.

Code of Conduct

[X] I agree to follow the VerneMQ's Code of Conduct

@ilpanich Thanks, can you link to the fix in OTP 26? (can't seem to quickly find it)

👉 Thank you for supporting VerneMQ: https://github.com/sponsors/vernemq
👉 Using the binary VerneMQ packages commercially (.deb/.rpm/Docker) requires a paid subscription.

Hi @ioolkos,
I found this one: https://www.erlang.org/doc/apps/erts/notes#erts-14.1

Fixed a bug where the emulator was unable to determine the current cgroup CPU quota.
Own Id: OTP-18645 Aux Id: GH-7401

As I said, I don't know if it will fix our issue, but maybe you can check.

The corresponding Github issue is: https://github.com/erlang/otp/issues/7401
Reads very much like the issue at hand.

👉 Thank you for supporting VerneMQ: https://github.com/sponsors/vernemq
👉 Using the binary VerneMQ packages commercially (.deb/.rpm/Docker) requires a paid subscription.

Can you please give us an ETA to have this fix in VerneMQ?
Some public cloud providers are forcing to move to k8s v1.26 before Oct. 31st.

@ilpanich No VerneMQ source code has to be fixed. I haven't checked whether the OTP fix is already backported to OTP 25. You could look into that since you use self-compiled packages. Or compile with OTP 26 (see https://github.com/vernemq/vernemq/pull/2157)
For the Verne subscription-based binaries, we'll have to do something similar. (they are obviously compiled with a specific OTP release).

👉 Thank you for supporting VerneMQ: https://github.com/sponsors/vernemq
👉 Using the binary VerneMQ packages commercially (.deb/.rpm/Docker) requires a paid subscription.

Hi @ioolkos:

I haven't checked whether the OTP fix is already backported to OTP 25

To me it seems that it has not been backported, but I'm not really expert with erlang/OTP, so maybe if you can check it could be better.
If it has been backported and this is included in the VerneMQ versions I put in this ticket... then there is another issue with the CPU detection different from the one mentioned.
I tried to build with OTP 26 but the build has failed and as far as I can see in #2157 some tests fail and I cannot put in my production enviroment something that is not really stable.

Hi @ioolkos. I have built an image using Erlang 26 and it seems ok.
By the way I'll wait VerneMQ to offically merge #2157 to close this issue.

@ilpanich OTP 26 support is now  merged.

👉 Thank you for supporting VerneMQ: https://github.com/sponsors/vernemq
👉 Using the binary VerneMQ packages commercially (.deb/.rpm/Docker) requires a paid subscription.

@ioolkos got it.
I will build and try in our environments, if it is ok I will close the issue.
Thank you!

Yes, we can close it.
Thank you @ioolkos  for the support.


Availability Zone behaviour

It would be good to know the behaviour of the Azure Postgres service regarding availability zones, where a region has an outage in one zone, but not in another. For example, it is possible to run a Kubernetes service across availability zones, but what happens to the Postgres database they connect to? Will that also survive?

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

ID: 3403c322-49e6-3ff5-4c02-1f9e83bbe6cf
Version Independent ID: 5242d7c0-2b2d-e16e-2c81-1b28477a1a84
Content: High availability - Azure Database for PostgreSQL - Single Server
Content Source: articles/postgresql/concepts-high-availability.md
Service: postgresql
GitHub Login: @rachel-msft
Microsoft Alias: raagyema

Thanks for the question. We are currently investigating and will update you shortly.

Hi, @robertlagrant. The regional disaster recovery process is detailed in this document and essentially comes down to manually promoting a Read-Replica to Master. If you are looking for a complete high availability solution for Kubernetes based upon availability zones, please see: Create an Azure Kubernetes Service (AKS) cluster that uses availability zones. Additional information: Best practices for business continuity and disaster recovery in AKS.
So yes, it will survive but with manual intervention. Please see this TechCommunity blog to see about scripting the deployment and then using a script to make the promotion.
Azure Database for PostgreSQL (Single Server) Regional Disaster Plan

Scenario
Recovery plan

Region failure
Failure of a region is a rare event. However, if you need protection from a region failure, you can configure one or more read replicas in other regions for disaster recovery (DR). (See this article about creating and managing read replicas for details). In the event of a region-level failure, you can manually promote the read replica configured on the other region to be your production database server.

Please let me know if you have any additional questions here.

@robertlagrant Update to this conversation. The solution is the a new service - Azure Database for PostgreSQL - Flexible Server. Please see: High availability concepts in Azure Database for PostgreSQL - Flexible Server.

@robertlagrant Its been a while we heard from you. We will proceed to close this issue now.
If you need further assistance, please comment and we will gladly continue the conversation.

The answer did not cover the question..
for the single server / hyperscale PG DB... there is not enough documentation on what happens when a AZ thats hosting the service fails.. region is still up; will the PG service come up in another AZ?


gdget failed to get large file

600~700MB file is ok, 1G failed

https://google-api-python-client.googlecode.com/hg/docs/epy/apiclient.http.MediaIoBaseDownload-class.html

added stream download with requests on commit 8baf9a506d2df087aed4fd41ad0d54990a0db62b


NameError: uninitialized constant Ontraport::HTTParty

I've encountered the issue in Rails 5
This issue could be fixed by adding
require 'httparty' on top inside initializers/ontraport.rb.
or
require 'httparty' in lib/ontraport.rb.

Thanks for reporting this @magankur. Sorry it took me a while to get to it. Fixed now


Refactor pad utilities to use Python internals (#388)

I tried to adress #388 but I'm still very much a Python noob (in fact, this is my first contribution to a Python project ever)
@pipermerriam I hope I refactored it the way you had it in mind. I first wasn't sure about the curried functions but think it turned out well (again, bloody Python noob here!).

Ok, turns out. This still has plenty of tests failing. Looking into it...

Looks like you did the following replacement:

pad_left -> ljust
pad_right > rjust

It should actually be the other way around.

pad_left > rjust
pad_right > ljust

Ah yes, thank you! So that's what happens when you blindly replace stuff. Should be fixed now.


Feature:  provide SSH port

Issue Description
provide SSH port
Describe what feature you want
# sealer run kuberntes:1.19.9 --masters <IP_ADDRESS>,<IP_ADDRESS>,<IP_ADDRESS> --nodes <IP_ADDRESS>,<IP_ADDRESS>,<IP_ADDRESS> --passwd xxx

i want:

# sealer run kubernetes:v1.19.9 --masters <IP_ADDRESS>:2345,<IP_ADDRESS>:3456,<IP_ADDRESS>:2345  --passwd xxx

Additional context
my environment is not allowed to open SSH 22

I will handle this issue


TypeError: undefined is not an object (evaluating '_NativeModules.HyperPaySDK')

HI @RMabroukS thanks for the library.
When try to import in android  "import HyperPay from 'react-native-hyperpay-sdk';" i am getting error
Error: Requiring module "node_modules/react-native-hyperpay-sdk/src/index.tsx", which threw an exception: TypeError: undefined is not an object (evaluating '_NativeModules.HyperPaySDK')

Same, I am using expo by the way is it compatible with it ? if no is it possible ?

I guess the issue is due to old sdk version is used
I removed the library and using hyperpay using bridging with native sides
and it's working for me
On Sun, Jan 8, 2023, 1:19 PM Suliman Alfowzan @.***>
wrote:

Same, I am using expo by the way is it compatible with it ? if no is it
possible ?
—
Reply to this email directly, view it on GitHub
https://github.com/RMabroukS/react-native-hyperpay-sdk/issues/2#issuecomment-1374754866,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFQK7L7IT6TFPGPRMG3L5CLWRJZ7XANCNFSM6AAAAAATN6FIZM
.
You are receiving this because you authored the thread.Message ID:
@.***>

Are you using expo ? And does you solution work wit it ?

No i am using CLI and yes working on native modules and bridging it in
React Native worked for me
On Sun, Jan 8, 2023, 8:23 PM Suliman Alfowzan @.***>
wrote:

Are you using expo ? And does you solution work wit it ?
—
Reply to this email directly, view it on GitHub
https://github.com/RMabroukS/react-native-hyperpay-sdk/issues/2#issuecomment-1374861147,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFQK7L7TSP57INE54VLLUDDWRLLVRANCNFSM6AAAAAATN6FIZM
.
You are receiving this because you authored the thread.Message ID:
@.***>

I am trying to implement it with expo and did not find any way yet for that. I cannot go the react native cli way just for hyperpay and sacrifice the easy DX of expo

HI @RMabroukS thanks for the library. When try to import in android "import HyperPay from 'react-native-hyperpay-sdk';" i am getting error Error: Requiring module "node_modules/react-native-hyperpay-sdk/src/index.tsx", which threw an exception: TypeError: undefined is not an object (evaluating '_NativeModules.HyperPaySDK')

@Bilalwarind  What is the react native version & react-native-hyperpay-sdk version ? And this problem on android or ios ?

@SulimanF96  This library working only with react-native cli, you can eject your project to use it

hi @RMabroukS/react-native-hyperpay-sdk
@.***>  i am using
react-native-hyperpay-sdk
version version 0.30.0 and reactnative version i tried on 0.70 and 0.66 and
on both it returns the error and i have tested only for android .
On Sun, 8 Jan 2023 at 23:19, Ragab Mabrouk @.***> wrote:

@SulimanF96 https://github.com/SulimanF96 This library working only
with react-native cli, you can eject your project to use it
—
Reply to this email directly, view it on GitHub
https://github.com/RMabroukS/react-native-hyperpay-sdk/issues/2#issuecomment-1374896269,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFQK7L3ZTLK6DWSRQQ4CFHLWRMALBANCNFSM6AAAAAATN6FIZM
.
You are receiving this because you were mentioned.Message ID:
@.***>

@RMabroukS/react-native-hyperpay-sdk
@.***>  i get this error when i
import the sdk even did not started implementation .
On Mon, 9 Jan 2023 at 07:37, Bilal Warind @.***> wrote:

hi @RMabroukS/react-native-hyperpay-sdk
@.***>  i am using  react-native-hyperpay-sdk
version version 0.30.0 and reactnative version i tried on 0.70 and 0.66 and
on both it returns the error and i have tested only for android .
On Sun, 8 Jan 2023 at 23:19, Ragab Mabrouk @.***>
wrote:

@SulimanF96 https://github.com/SulimanF96 This library working only
with react-native cli, you can eject your project to use it
—
Reply to this email directly, view it on GitHub
https://github.com/RMabroukS/react-native-hyperpay-sdk/issues/2#issuecomment-1374896269,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFQK7L3ZTLK6DWSRQQ4CFHLWRMALBANCNFSM6AAAAAATN6FIZM
.
You are receiving this because you were mentioned.Message ID:
@.***>

hi @RMabroukS i am using @RMabroukS/react-native-hyperpay-sdk version 0.33.0 for my project in which  "react-native": "0.61.3" and i am getting the same error, did you find any solutions

hi @RMabroukS i am using @RMabroukS/react-native-hyperpay-sdk version 0.33.0 for my project in which "react-native": "0.61.3" and i am getting the same error, did you find any solutions

Hello @stargamerboy786  Can you update to<EMAIL_ADDRESS>and try again, if you getting the same error, please share with me more details for your environment

System:
OS: macOS 13.1
CPU: (8) arm64 Apple M1
Memory: 94.31 MB / 16.00 GB
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 18.9.0 - /opt/homebrew/bin/node
Yarn: 1.22.19 - /opt/homebrew/bin/yarn
npm: 8.19.1 - /opt/homebrew/bin/npm
Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
SDKs:
iOS SDK:
Platforms: DriverKit 22.2, iOS 16.2, macOS 13.1, tvOS 16.1, watchOS 9.1
IDEs:
Android Studio: 2021.2 AI-212.5712.43.2112.8815526
Xcode: 14.2/14C18 - /usr/bin/xcodebuild
npmPackages:
react-native: file:./packages/blocks/core/node_modules/react-native => 0.61.3
npmGlobalPackages:
react-native-cli: 2.0.1

Thanks @stargamerboy786, this error occurs on Android only or android & ios ?

Thanks @stargamerboy786, this error occurs on Android only or android & ios ?

this happens on both Android and ios

@stargamerboy786  I've tried on more than one react native version and this problem doesn't occur with me at all,
if is possible to send me a demo code that have the problem until I catch the problem and solve it, I'd be thankful.

@stargamerboy786 I've tried on more than one react native version and this problem doesn't occur with me at all, if is possible to send me demo app that have the problem until I catch the problem and solve it, I'd be thankful.

import React from "react";
import {
StyleSheet,
View,
SafeAreaView,
TouchableOpacity,
ScrollView,
Dimensions,
} from "react-native";
import PaymentMethodController, { Props } from "./PaymentMethodController";
import { CreditCardInput } from "react-native-credit-card-input-plus";
import Scale, { verticalScale } from "components/src/Scale";
import HyperPay from 'react-native-hyperpay-sdk';
export default class AddingPaymentDetails extends PaymentMethodController {
constructor(props: Props) {
super(props);
}
_onChange = () => form => console.log(form);
values = () =>{
    console.log("card details found ");
    this.payment()

    // this.props.navigation.navigate("PlanDetailsSuccessfully" ,{ endDate: this.state.endDate, upgradeStatus: this.state.upgradeStatus })

}
payment = async() => {
    HyperPay.init({
        shopperResultURL:"shopperResultURL",
        countryCode:"IN",
        // merchantIdentifier:"merchantIdentifier",
        mode:"TestMode"
        })

        const result=await HyperPay.createPaymentTransaction(
            { paymentBrand: "VISA",
              holderName: "Test Test",
              cardNumber: '4111111111111111',
              expiryYear: '2027',
              expiryMonth: '12',
              cvv: '123',
              checkoutID: `E0B5C712EBF1FFD33F69B98690AC4963.uat01-vm-tx02`,
              shopperResultURL: "[YOUR_APP_IDENTIFIER]://[URL_SCHEMES]"
              })
              const resultpayment=HyperPay.getPaymentStatus("000.000.000")
              console.log("result",result);
              console.log("result payment ",resultpayment);

}

render() {
    return (
        <>
            {/* <StatusBar backgroundColor="white" barStyle="dark-content" /> */}
            <SafeAreaView style={styles.rootContainer}>
                <ScrollView>
                    <View style={styles.rootContainer}>
                    <CreditCardInput onChange={this._onChange} />
                    </View>
                </ScrollView>
                <TouchableOpacity
                  style={[
                    styles.startedView,
                    {
                      backgroundColor: this.state.selected1
                        ? "rgba(234, 67, 93, 1)"
                        : "rgba(122, 123, 127, 1)",
                    },
                  ]}
                  onPress={() => this.values()}
                ></TouchableOpacity>
            </SafeAreaView>
        </>
    );
}

}
const styles = StyleSheet.create({
rootContainer: {
backgroundColor: "white",
},
startedView: {
marginTop: verticalScale(50),
marginBottom: verticalScale(20),
alignSelf: "center",
height: Scale(45),
width: Scale(145),
backgroundColor: "rgba(33,35,47,255)",
borderColor: "white",
borderRadius: Scale(10),
justifyContent: "center",
borderWidth: 1,
marginLeft:5
},
});
its just a normal page

Thanks @stargamerboy786, I mean fully react native app

Same issue here, Any updates?

sme issue here, any solution @RMabroukS  @stargamerboy786  ?

This issue is still not resolved I tried a few days ago on React Native cli
On Fri, Jun 9, 2023, 2:16 PM enganasalsaadi @.***>
wrote:

sme issue here, any solution @RMabroukS https://github.com/RMabroukS
@stargamerboy786 https://github.com/stargamerboy786 ?
—
Reply to this email directly, view it on GitHub
https://github.com/RMabroukS/react-native-hyperpay-sdk/issues/2#issuecomment-1584244839,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFQK7L44A3PTEVTUDI4AW5TXKLSVHANCNFSM6AAAAAATN6FIZM
.
You are receiving this because you were mentioned.Message ID:
@.***>

@Bilalwarind  @enganasalsaadi  Can any one create a new repo with demo app included this issue and send me it, even i can fix it, because I can’t catch this issue

Ok, I will try today
On Fri, Jun 9, 2023, 4:56 PM Ragab Mabrouk @.***> wrote:

@Bilalwarind https://github.com/Bilalwarind @enganasalsaadi
https://github.com/enganasalsaadi Can any one create a new repo with
demo app included this issue and send me it, even i can fix it, because I
can’t catch this issue
—
Reply to this email directly, view it on GitHub
https://github.com/RMabroukS/react-native-hyperpay-sdk/issues/2#issuecomment-1584459655,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFQK7L5CLDD4L3SGAA7CD73XKMFN3ANCNFSM6AAAAAATN6FIZM
.
You are receiving this because you were mentioned.Message ID:
@.***>

@RMabroukS  i catch the issue, is is from name module u r using HyperPaySDK but should be HyperPay,
i implemented native modules and i use NativeModule.HyperPay

@enganasalsaadi  No, because I have exported the module with HyperPaySDK name,
if possible to share with me an example app included this issue. I'll be grateful to you


fixing typo extensible authorization page

Fixes #12968

🚀 Preview for commit c159468983517678d9e9c653722709d6b452ca32 at: https://676a6f5bc6eae6766dec7315--meshery-docs-preview.netlify.app

🚀 Preview for commit c159468983517678d9e9c653722709d6b452ca32 at: https://676a6fb7a020d26f20ecec24--meshery-docs-preview.netlify.app

This PR has been combined into #13000


fix(kafkajs, rdkafka): use long trace IDs with new Kafka message headers

I made a mistake when initially preparing the migration for Kafka headers (X_INSTANA_C to X_INSTANA_T/X_INSTANA_S). Our spec mandates to always use long trace IDs (128 bit/32 characters) with X_INSTANA_T, but I failed to implement that part correctly. This PR fixes that for the kafkajs and rdkafka instrumentations.
The PR also adds a new feature to kafkajs: Removing our own headers before passing the message on to the application. The rdkafka instrumentation already did that.

LGTM! Thanks for updating the trace id <3
I added a few questions/suggestions that do not compromise the current state of the code, so the PR is approved.
Cheers!

meh, Github has been doing this duplication I see... Same happened to Andrii from a Code Review from Yesterday..

LGTM! Thanks for updating the trace id <3
I added a few questions/suggestions that do not compromise the current state of the code, so the PR is approved.
Cheers!

meh, Github has been doing this duplication I see... Same happened to Andrii from a Code Review from Yesterday..

The more LGTMs, the merrier. Thanks for the review, I'll implement the suggested changes and merge the PR afterwards. 👍


Support Relationship attribute type

Is your feature request related to a problem? Please describe.
The Relationship attribute type is not officially part of the NGSI v2 spec but is nonetheless widely used by FiWare applications in practice. QuantumLeap does not include this type in its NGSI-to-SQL translation map.
Describe the solution you'd like
Add the Relationship type to the NGSI-to-SQL map and save Relationship attribute values as plain text. Notice Relationship attribute values will not be given any specific meaning (e.g. attempting to interpret them as NGSI-LD references), rather they will be opaque strings QuantumLeap stores just like any other text attribute. In particular, they won't be mapped to foreign keys or similar relational constructs.
Describe alternatives you've considered
Do nothing. After #382 gets fixed, Relationship attribute values can be saved to the DB. But this isn't the cleanest solution and it also has the annoying side-effect of the warning below being logged on every attempt to save a Relationship attribute value
WARNING:translators.crate:'Relationship' is not a supported NGSI type.
Please use any of the following: Array, Boolean, ISO8601, DateTime,
Integer, geo:json, geo:point, Number, Text, StructuredValue. Falling
back to Text.

Additional context
#382

NGSI-LD
During Nov 2020's FiWare TSC, we got a confirmation that NGSI-LD does not really support a temporal model w/r/t entity graphs. According to the TSC, all we need to do to claim QL supports the NGSI-LD temporal entity/relationship model is to store entity references as plain NGSI text attributes just like this issues suggests to do for the Relationship type of NGSI-v2.
So implementing a relationship type would be quite a leap forward in the mythical quest for NGSI-LD support!
Implications
This kind of approach has the downside that answering questions about your data over time that involve relationships can be prohibitively expensive which begs the question of what's the practical usefulness of NGSI-LD/temporal?! Notice TSC agreed that client applications will have to reconstruct the (temporal) graph they need from the ref attributes stored in entity rows, so technically we don't have a problem w/r/t being NGSI-LD compliant. But, but... how can clients possibly do that over large datasets through a Web API?! Also this kind of set up basically rules out big data analytics involving relations. Oh well.

this should be fixed by #373


add icon generator

Seeing a problem with Android. To reproduce:

npm install && npm run setup
npm run android

It tries to build android app but fails with the following error:
* What went wrong:
Execution failed for task ':app:mergeDebugResources'.
> /Users/philip/projects/baker/app/android/app/src/main/res/WEB/ic_launcher.png:1:1: Error: Content is not allowed in prolog.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

Should be fixed. Need to re-install mobile icon resizer:
npm install mobile-icon-resizer --force


make LANGUAGE=cpp error

Hi, I am getting the following error when i run make LANGUAGE=cpp. Can you tell me where I am going wrong?
pi@raspberrypi:~/assistant-sdk-cpp/googleapis $ make LANGUAGE=cpp
mkdir -p ./gens
protoc --proto_path=.:/usr/local/include --cpp_out=./gens --grpc_out=./gens --plugin=protoc-gen-grpc=/usr/local/bin/grpc_cpp_plugin google/rpc/code.proto
/usr/local/bin/grpc_cpp_plugin: program not found or is not executable
Please specify a program using absolute path or make sure the program is available in your PATH system variable
--grpc_out: protoc-gen-grpc: Plugin failed with status code 1.
Makefile:44: recipe for target 'google/rpc/code.pb.cc' failed
make: *** [google/rpc/code.pb.cc] Error 1

Looks like you don't have the gRPC plugin for protoc.

What should I do then ?

Looks like you don't have the gRPC plugin for protoc.

So what do I need to do ?

You may need to install gRPC.


Feat/credentialz 4

"This code is a Contribution to the OpenConfig Feature Profiles project ("Work") made under the Google Software Grant and Corporate Contributor License Agreement ("CLA") and governed by the Apache License 2.0. No other rights or licenses in or to any of Nokia's intellectual property are granted for any other purpose. This code is provided on an "as is" basis without any warranties of any kind."

Pull Request Functional Test Report for #2580 / 400a7ce8bfe91dfd7d1a66b6c5eb6c86724b4c47
Virtual Devices

Device
Test
Test Documentation
Job
Raw Log

Arista cEOS

Credentialz-4: SSH Public Key Authentication

Cisco 8000E

Credentialz-4: SSH Public Key Authentication

Cisco XRd

Credentialz-4: SSH Public Key Authentication

Juniper cPTX

Credentialz-4: SSH Public Key Authentication

Juniper ncPTX

Credentialz-4: SSH Public Key Authentication

Nokia SR Linux

Credentialz-4: SSH Public Key Authentication

Openconfig Lemming

Credentialz-4: SSH Public Key Authentication

Hardware Devices

Device
Test
Test Documentation
Raw Log

Arista 7808

Credentialz-4: SSH Public Key Authentication

Cisco 8808

Credentialz-4: SSH Public Key Authentication

Juniper PTX10008

Credentialz-4: SSH Public Key Authentication

Nokia 7250 IXR-10e

Credentialz-4: SSH Public Key Authentication

Help

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 52.21%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1654

Relevant Lines:
3168

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 55.5%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1983

Relevant Lines:
3573

💛  - Coveralls

Closing this PR due to CLA issues. New PR opened https://github.com/openconfig/featureprofiles/pull/3358.


Wrangler fails to load app when using Hono Vite devserver middlewar with custom entry point

What version of Hono are you using?
4.2.8
What runtime/platform is your app running on?
Cloudflare Pages
What steps can reproduce the bug?
Create a new Hono app and choose the Cloudflare Pages option.
Move src/index.tsx into a new directory such as src/foo/index.tsx.
Update vite.config.ts:
import build from '@hono/vite-cloudflare-pages'
import devServer from '@hono/vite-dev-server'
import adapter from '@hono/vite-dev-server/cloudflare'
import { defineConfig } from 'vite'

export default defineConfig({
  plugins: [
    build(),
    devServer({
      adapter,
      entry: 'src/foo/index.tsx'
    })
  ]
})

Results in failure:
$ yarn preview
yarn run v1.22.22
warning package.json: No license field
$ wrangler pages dev dist
✨ Compiled Worker successfully
 ⛅ wrangler 3.52.0 (update available 3.53.1)
-------------------------------------------------------
⎔ Starting local server...
✘ [ERROR] service core:user:my-app: Uncaught Error: Can't import modules from ['/src/index.tsx','/app/server.ts']

    at null.<anonymous> (bundledWorker-0.9798135843018798.js:959:9)

✘ [ERROR] MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.

[wrangler:inf] Ready on http://localhost:8788

What is the expected behavior?
The build should succeed and Wrangler should boot the app
What do you see instead?
When viewing the localhost URL the page loads forever
Additional information
No response

Hi @callmetwan
It's not a bug. Please specify the entry option for build:
export default defineConfig({
  plugins: [
    build({
      entry: 'src/foo/index.tsx'
    }),
    devServer({
      adapter,
      entry: 'src/foo/index.tsx'
    })
  ]
})

Ref: https://github.com/honojs/vite-plugins/tree/main/packages/cloudflare-pages#options

Thanks!


Gateway support?

Hey all,
As I'm implementing, I've discovered that our developers really want to support our gateway client.  While on the consumer side, I could easily implement the proxy, the provider implementation appears to really want a path, but if I were to implement this the way our code really does this, I would need to put an instantiation of the gateway client resource.
This is not a passthrough as you describe it because the gateway client will actually return the same thing service
It appears that to do this the way the developers want me too, I'll have to monkey patch.  So the questions I have are:

Is this a good idea?
If so, do you have any recommendations for how to do it (examples, is it on the roadmap and I'm just missing it?)
If it's not a good idea, can you help me out with some arguments to talk them out of it?

Just to make it clear, does your consumer makes requests to an API gateway, which in turn, forwards the requests on to the provider? Or is the gateway translating the requests and responses in some way?

Our gateway is a fork of Eureka(https://github.com/Netflix/eureka/wiki/Eureka-at-a-glance).  I don't believe it does any translation, but I will confirm that.

So the problem is that the path the client uses (and what gets persisted into the pact file) will be different to what the running provider responds to?

The problem is that the client doesn't use a path, so there is no path to persist to the pact file. It simply gives its resource payload to the gateway and the gateway knows how to map the resource it got to 1. the service, 2. the correct endpoint.
So I would have to write a module to override some of the behavior, which isn't that much of a problem but, since we know the gateway mapping works (the gateway has its own tests) and there isn't much point in testing via the client.  I suppose something could go wrong where, if I just used the path, I could specify an incorrect endpoint the operates as expected, but that seems unlikely.
I'm just wondering if you all have any recommendations

@johngluckmdsol
Did you modify anything significantly in your Eureka fork?
Because if not, this diagram says that you actually have three relationships/connections:

Server app -> Eureka server (to register)
Client app -> Eureka server (to request a data about any instance of server app registered and alive rigt now)
Client app -> Server app (actual request)

Have you tried to inspect what requests your app does when you do Client::Resource.('stuff here') in your code?

@ivan-kolmychek, I think I see what you are heading.  If I can get the endpoint from the client in advance, I can write it to the client.  It's a bit heavy on overhead because I'll have to stand up a local instance of the gateway server, but it just might work.  It's not a pure unit test though.

@johngluckmdsol you, you don't have to, as you can fake responses to both requests (to gateway and to service app) in your test.
You'll just have to make sure that second request is going to the path that was in your response from gateway.
I think that's probably something that you can test in isolation.

@ivan-kolmychek What you suggested is how I've implemented it. Some of my developers thought there might be some value in getting the mappings from the gateway.  Given that the gateway will soon be optional, what I think I've come to the conclusion that there is no need to add the gateway to these tests.  Thanks for the input

@johngluckmdsol I'm not sure that's even a gateway, sounds more like a coordinator to me, as requests from client to server still have to be made directly. But maybe I misunderstand that.
(Disclaimer: I'm putting this info here just in case someone will be looking for stuff like this. I'm glad that you've solved your issue, so this may be a bit irrelevant to your case.)
In one of the projects I worked with, we had a gateway service which presented "public API" endpoints to world and did calls to internal APIs. We tested it with pact from two sides:

As a client for internal API's in public API tests - to make sure we have contracts between gateway as a client and number of services providing internal APIs
As a provider for our reference implementation of client for public API - to make sure we have contract with sample client and we don't break the expectations of public API

In your case, even if the client is depending on coordinator service data not all the time but in some cases, I think you may use pact to get contract with gateway in those cases, if you think those are important and should be tested. Still, tests, in my opinion, should bring value to you and your project, not be a burden, so if you think that it doesn't really need tests - so be it. :)
Also, without verification pact is just a description of how you expect service to behave, and verifying the pacts conformance on coordinators side is yet another topic.


Cannot add task 'wrapper' as a task with that name already exists

Hi,
I'm trying to build this project with the commands provided. I tried the below command
gradle clean build zip
and getting the below error -
`
FAILURE: Build failed with an exception.
* Where:
Build file '/home/janardhan/CodeBase/poCs_JMS/kafka-connect-jms/build.gradle' line: 149

* What went wrong:
A problem occurred evaluating root project 'kafka-connect-jms'.
 > Cannot add task 'wrapper' as a task with that name already exists.

`
Any idea?
I'm using Gradle 5.0 version.
And can you specify where is the kafka-connect-jms-${version}.jar present? Is it arises out of the build?
Thanks.

tried with gradle 4 version and the issue is no longer exists.


Auto corrected by following Lint Ruby Style/RegexpLiteral

Auto corrected by following Lint Ruby Style/RegexpLiteral
Click here to configure it on awesomecode.io

Coverage remained the same at 77.536% when pulling 17b39ee1adb19d48e25d745ccfacd1f17d319671 on awesomecode-lint-ruby-style-regexpliteral-48718 into 2d6830330ac936b6fd9d06bfeb82ecc80adab7d7 on master.


Added new distributions and corresponding tests

Hello,
I added a few new distributions to the library.

New distributions are

Three parameter Burr (Type XII)
Inverse Gaussian
Truncated Pareto

Unit tests added for all public methods
New distributions added to CommonDistributionTests

I also added a new helper method (IsFinite) to Precision.Comparison. This was the most fitting place I could find, so I hope this is deemed appropriate.
Here some mathematical references for the added distributions:

Burr:

https://www.mathworks.com/help/stats/burr-type-xii-distribution.html
On the Three-Parameter Burr Type XII Distribution

Inverse Gaussian

https://www.mathworks.com/help/stats/inverse-gaussian-distribution.html
https://en.wikipedia.org/wiki/Inverse_Gaussian_distribution
Probability Calculations for the Inverse Gaussian Distribution

Truncated Pareto
-A Note on the Upper-Truncated Pareto Distribution
-https://en.wikipedia.org/wiki/Pareto_distribution#Bounded_Pareto_distribution

This looks like a valuable addition. Yes, Precision is the right place for IsFinite. Thanks for the contribution!


Note that you need plugins to import files that are not JavaScript

Describe the bug
error during build:
RollupError: Unexpected token (Note that you need plugins to import files that are not JavaScript)
Reproduction
https://github.com/envCode/env-admin
Steps to reproduce
yarn typecheck && cross-env VITE_APP_ENV=dev vite build
System Info
System

Used Package Manager
yarn
Logs

Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Please create a minimal reproduction.

web.zip

cmd Run yarn typecheck && cross-env VITE_APP_ENV=dev vite build Steps to reproduce

Same error, @envCode How did you resolve problem?

Same error, @envCode How did you resolve problem?

例如
const a={x:1}
defineConfig.define:{a}
app.config.globalProperties.a=a
build时app.config.globalProperties.a=a 变成了 app.config.globalProperties[{x:1}]={x:1}
define定义的key不能与globalProperties定义的key一样

Same error, @envCode How did you resolve problem?

例如
const a={x:1}
defineConfig.define:{a}
app.config.globalProperties.a=a
build时app.config.globalProperties.a=a 变成了 app.config.globalProperties[{x:1}]={x:1}
define定义的key不能与globalProperties定义的key一样


Roadmap and design

I threw this together to pretty much scrape some features I am hoping this repo eventually is capable of doing: https://github.com/angular-ui/ui-select/wiki/Roadmap
One of the the things I'm focused on right now is easy-to-customize data, access to internal data, and templates.
One concern is the ability to specify a custom list-item template (currently possible) and a custom selected template (not possible, just uses a button). Perhaps we should break this up into multiple tags?
<ui-select>
  <selected></selected>
  <options>

  </options>
</ui-select>

These child-directives COULD in fact be optional, and if not specified, simply generate
{{value}}

Secondly, if you don't specify <selected> or <options> but you DO specify a template we could use THAT one for both. Perhaps instead of making you create the
 tag and it's related attributes we can do it for you and you simply specify the contents of each list-item and the selected-item?

+1 for "Is there a way to do the equivalent of ui-select2's createSearchChoice? I need to allow a person to enter a name if it isn't in the list of existing options."

+1 for "Is there a way to do the equivalent of ui-select2's createSearchChoice? I need to allow a person to enter a name if it isn't in the list of existing options." or the selectize 'item Creation' function

+1. Just hacked the tagging feature to give this kind of behavior, lol wasn't pretty. +1 for this and thanks for tagging!

@j-walker23 @michaelhoes @dubcanada @lasimon This is available in v0.9.8.

Hi, It is not working with angular verision: 1.2.10

Thank you @brianfeister, you guys are the difference between a shitty day programming and a smooth day.

Does select2 support using matchers (finding all the texts starting with) like the jquery select supports?

Can I help with maintaining this repo?

@homerjam Talk with @aaronroberson he is the one maintaining the library now I think.

First of all thanks everyone for this awesome component! Are there any plans to port this to angular 2? is help wanted in that area?
p.s. There is already a stackoverflow question on the subject: http://stackoverflow.com/questions/37921979/ui-select-replacement-in-angular2

@fru  I don't think there are any plans on angular 2 yet. At the moment we are trying to handle all the bugs.

Closing it down as it is a very old issue for now this repo is focusing on handling the bugs.
Help is welcome 👍


Is it possible to wait until push to run the CommitMsg hook?

A typical workflow when working on a branch is to make several commits locally without pushing to GitHub, and once it's ready to be pushed as a pull request, the commits might or might not be squashed. Having overcommit complain about each individual commit interrupts the flow. It would be a much better experience to wait until the commits are actually pushed before checking them.
Is there a way to configure this behavior?
Thanks!

Hey @monfresh,
CommitMsg hooks aren't triggered by Overcommit, but by git itself.
Your potential options/workarounds are:

Move your CommitMsg hooks to PrePush hooks so they only run on push
Disable CommitMsg hooks entirely

At the end of the day, creating a CommitMsg hook indicates you want the hook to run when git runs the commit-msg hook. There's no getting around this other than to move your checks into a different hook.
Hope this helps!

Thanks! How do I move my CommitMsg hooks to PrePush? I tried both of these, and neither worked:
PrePush:
  CapitalizedSubject:
    enabled: true
    description: 'Check subject capitalization'

PrePush:
  CommitMsg:
    CapitalizedSubject:
      enabled: true
      description: 'Check subject capitalization'

You would need to write them yourself as custom hooks, unfortunately.
However, you should be able to copy/paste most of the existing code and make slight adjustments.


OpenCV 3.4.3-p2

Testing:

https://ci.appveyor.com/project/ingenue/hunter/builds/20172451
https://travis-ci.org/ingenue/hunter/builds/452825922?utm_source=github_status&utm_medium=notification

Released: https://github.com/ruslo/hunter/releases/tag/v0.23.49


Include decent_exposure to Mailers and its views

[x] Include decent_exposure to Mailers and its views

You'll need to set in the mailer instance your params. Check this:
class PostMailer < ApplicationMailer
  attr_accessor :post_id

  expose :posts, -> { Post.last 5 }
  expose(:post, id: -> { post_id })

  def best_posts_ever(post_id = nil)
    self.post_id = post_id
    @greeting = "Hi"

    mail to<EMAIL_ADDRESS>  end
end

Post#best_posts_ever

  <%= @greeting %>, find me in app/views/post_mailer/best_posts_ever.html.erb
  Single Post = <%= post.inspect %>
  Post List = <%= posts.map(&:inspect) %>

closes #150

@mattpolito I added some documentation to README.md


Position not corrected.

Hi,
I am trying to set the notifications to show in the bottom right, but they are not showing. I looked at various "solutions" but nothing worked. I also tried to show the toast notification in any other place instead of the default top right, but nothing worked.
They are constantly being shown at the top right corner. What am I doing wrong?
My code is in the attached file:
tadej1.txt

You need to set the options before calling the notification:
`toastr.options {
...
}
toastr.success("Are you the six fingered man?")`


Updating status of a couple of projects

Hey @PCChuang—congrats on submitting a PR at the end of the git course. I hope that you enjoyed the course and that you learnt a lot in doing it.
If you weren't already using git for your code, hopefully this has inspired you to do so. I hope that you enjoy the "Mastering Git" video course as well—you'll soon be able to get git to bend to your will :)
You can now wear this #GitWarrior badge with pride—and Tweet your historic victory!

sam


Mariadb will remove mysqldupm binary and should be replaced by mariadb-dump

Description
I tried to make a backup as normally. And after the execution an error was shown by the mysql-dump program.
Task execution failed, reason: /usr/bin/mysqldump:
Deprecated program name. It will be removed in a future
release, use '/usr/bin/mariadb-dump' instead
WARNING: option --ssl-verify-server-cert is disabled, because
of an insecure passwordless login.
DBeaver Version
Community edition Version <IP_ADDRESS>409011755
Operating System
Endeavour Os (Archlinux Based) linux kernel 6.10.9-arch1-2
Database and driver
Database: mariadbd  Ver 11.5.2-MariaDB for Linux on x86_64 (Arch Linux)
Client: mariadb from 11.5.2-MariaDB, client 15.2 for Linux (x86_64) using readline 5.1
Steps to reproduce

Setup a mariadb connection
Setup the dump client
Try to make a backup
my configuration was with:

Extended inserts
Add DROP statements
Disable keys

Additional context
I think that this simply requires changing the program name and the issue will be fixed. This happened after making an upgrade of my system and may be mariadb is forcing to make a migration.

Hi, @4strodev. Could you share your MySQL binaries version?

This is what happens on linux. The main problem comes for the recent versions of mariadb. If you need to know exactly which versions of mariadb I'm using check the issue I attached the client and server version.
Database: mariadbd Ver 11.5.2-MariaDB for Linux on x86_64 (Arch Linux)
Client: mariadb from 11.5.2-MariaDB, client 15.2 for Linux (x86_64) using readline 5.1
I have just installed mariadb on my system. I don't need mysql if I have mariadb. And since mariadb is deprecating the names of mysql in their binaries, here is where the problems come. The simplest solution could be change the binary name call to mariadb-dump when using mariadb.

We'll change. Thank you


Add new shift time section into configuration YAML

For components that require 24h coverage for 7 days (24/7), it is not unusual to split the work between different teams in different geographical locations. One option could be with one team in East Asia, one in Europe, and another one in East Coast America. This way you can split the work and each team has somehow acceptable working times.
Since each project has different locations, different teams, and different preferences, it is required that the settings for the shift times can be configured.
Example:
---
authtoken: foobar
shift-times:
- name: Team Asia
  start: 23:00
  end: 07:00
- name: Team Europe
  start: 07:00
  end: 15:00
- name Team America
  start: 15:00
  end: 23:00

This should configure the pd tool to know that the project uses three teams to cover 24h per day. Please note: It is absolutely okay to be configured in a way that some times are not covered. All times are meant to be in Zulu time/UTC so that there is no confusion regarding what timezone is meant.
The goal is that pd is reading the new YAML input. A new command called current-shift should be added via cobra add ... and it should look up the current user current time to print out which shift is currently active.
Acceptance Criteria: As a user, I want to call pd current-shift to get the following output:
$ pd current-shift
At the moment, Team Europe is in charge.

Fixed by #10.


test-raf.sh is unstable

Current design of test-raf.sh makes it unstable. The sleep 1 command doesn't guarantee that the CPU will sleep exactly one calendar second. I suggest we improve the test and just change file modification time through touch -d "1 seconds ago" filename command.
@zaqbez39me check this out

@yegor256 I see. I will work on it


Directory Service integration tests fail

Our Directory Service integration tests fail with:
Running target/debug/deps/ds-58b46c26a95f949b

running 2 tests
test should_describe_trusts ... FAILED
test should_describe_directories ... FAILED

failures:

---- should_describe_trusts stdout ----
thread 'should_describe_trusts' panicked at 'called `Result::unwrap()` on an `Err` value: HttpDispatch(HttpDispatchError { message: "error trying to connect: The certificate was not trusted." })', src/libcore/result.rs:1084:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace.

---- should_describe_directories stdout ----
thread 'should_describe_directories' panicked at 'called `Result::unwrap()` on an `Err` value: HttpDispatch(HttpDispatchError { message: "error trying to connect: The certificate was not trusted." })', src/libcore/result.rs:1084:5

failures:
    should_describe_directories
    should_describe_trusts

test result: FAILED. 0 passed; 2 failed; 0 ignored; 0 measured; 0 filtered out

error: test failed, to rerun pass '--test ds'

To reproduce:
$ cd integration_tests/
$ cargo test --features ds
This requires an AWS account to test.

HI! Simple solution proposal here: https://github.com/rusoto/rusoto/pull/1579. Let me know what you think :)

Hi!
It seems that the tests fails only for us-east-1, on OS X.  Looks like that the certificate returned by ds.us-east-1.amazonaws.com is a bit special, and the native-tls returns a non-trusted certificate, for this one, on OS X. I have opened an issue: https://github.com/sfackler/rust-native-tls/issues/143.

Thanks for looking into this! Sounds like switching the region is the easiest thing for us to get the test working again.
I assume if OSX is rejecting the cert we could ask Amazon to publish a cert OSX can consume. 😄 More testing is probably needed on other platforms to verify the cause of this problem.

No problem. The weird thing is that Golang & Python libs work with this certs, so I am assuming they are using there own implementation.

[puts on her AWS hat]
I’ve sent a few emails internally about that specific certificate. I’ll have a full write up once I give various teams a chance to do their own investigations.

Thanks for the fix @pradovic !


Cannot run Gemma2 on Ollama with ipex-llm

Hi
I can run Llama3, Qwen or other models on Ollama with ipex-llm. However, I cannot run Gemm2 on Ollama with ipex-llm. It shows unknown model architecture: 'gemma2'. Does it mean this model is not supported by ipex-llma?
Here're the details:

Thank you for your help in advance~

+1. Please update the supported version of Ollama. The current version is 0.2.7, however, Ipex-LLM only supports up to 0.1.39."

Also love this idea, enjoying running models locally and would love to play with deepseekv2 and gemma2

Hi all, Gemma2 is supported with ipex-llm[cpp] >= 2.1.0b20240724, you may try it again : )

Hi all, Gemma2 is supported with ipex-llm[cpp] >= 2.1.0b20240724, you may try it again : )

It works now! Thank you for your support!


Copy certificates to the /etc/ssl/certs and run openssl rehash for the run image

Summary

Fixes #73
Use Cases

Checklist

[X] I have viewed, signed, and submitted the Contributor License Agreement.
[X] I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
[ ] I have added an integration test, if necessary.
[X] I have reviewed the styleguide for guidance on my code quality.
[X] I'm happy with the commit history on this PR (I have rebased/squashed as needed).

Thanks @pbusko for submitting this!
These changes look good and I'm happy to merge. I'm not familiar with openssl rehash, so can you help me understand what aspects of SSL certificate usage (if any) were functioning correctly before this change?
From https://www.openssl.org/docs/man1.1.1/man1/rehash.html:

rehash scans directories and calculates a hash value of each .pem, .crt, .cer, or .crl file in the specified directory list and creates symbolic links for each file, where the name of the link is the hash value. (If the platform does not support symbolic links, a copy is made.) This utility is useful as many programs that use OpenSSL require directories to be set up like this in order to find certificates.
If any directories are named on the command line, then those are processed in turn. If not, then the SSL_CERT_DIR environment variable is consulted; this should be a colon-separated list of directories, like the Unix PATH variable. If that is not set then the default directory (installation-specific but often /usr/local/ssl/certs) is processed.

This suggests to me that some applications/tools don't require the hashed directories, and so worked before this PR, but others rely on these hashed directories and hence we need this change.
It also indicates me to me that setting SSL_CERT_DIR could be an alternative to providing the directory to openssl rehash <dir>. But I think the current approach of providing the directory is logical and clear.

Also @pbusko do we need to add this to the Bionic Tiny Stack too?

I wonder why the entire script can't be replaced with update-ca-certificates --etccertsdir X --certsdir Y?

@pbusko thanks for clarifying. This is great - I'm happy to merge.
Would you be willing to open a similar PR for the bionic tiny stack?

@pbusko thanks for clarifying. This is great - I'm happy to merge.
Would you be willing to open a similar PR for the bionic tiny stack?

Done https://github.com/paketo-buildpacks/bionic-tiny-stack/pull/96


Memory allocation on Intel Atom chips

Intel Celeron N2840
Mesa DRI Intel(R) Bay Trail  (0xf31)
For quite a time the DXVK wrapper have been completely unusable for me because of alot DxvkMemoryAllocator: Memory allocation failed errors. Most games renderings are pitch black, with rare exceptions. I put some efforts to investigate into this showstopper and now i think has found the clue.
According to Mesa sources (intel/vulkan/anv_device.c):

  if (device->info.has_llc) {
     /* Big core GPUs share LLC with the CPU and thus one memory type can be
      * both cached and coherent at the same time.
      */
     device->memory.types[type_count++] = (struct anv_memory_type) {
        .propertyFlags = VK_MEMORY_PROPERTY_DEVICE_LOCAL_BIT |
                         VK_MEMORY_PROPERTY_HOST_VISIBLE_BIT |
                         VK_MEMORY_PROPERTY_HOST_COHERENT_BIT |
                         VK_MEMORY_PROPERTY_HOST_CACHED_BIT,
        .heapIndex = heap,
        .valid_buffer_usage = valid_buffer_usage,
     };
  } else {
     /* The spec requires that we expose a host-visible, coherent memory
      * type, but Atom GPUs don't share LLC. Thus we offer two memory types
      * to give the application a choice between cached, but not coherent and
      * coherent but uncached (WC though).
      */
     device->memory.types[type_count++] = (struct anv_memory_type) {
        .propertyFlags = VK_MEMORY_PROPERTY_DEVICE_LOCAL_BIT |
                         VK_MEMORY_PROPERTY_HOST_VISIBLE_BIT |
                         VK_MEMORY_PROPERTY_HOST_COHERENT_BIT,
        .heapIndex = heap,
        .valid_buffer_usage = valid_buffer_usage,
     };
     device->memory.types[type_count++] = (struct anv_memory_type) {
        .propertyFlags = VK_MEMORY_PROPERTY_DEVICE_LOCAL_BIT |
                         VK_MEMORY_PROPERTY_HOST_VISIBLE_BIT |
                         VK_MEMORY_PROPERTY_HOST_CACHED_BIT,
        .heapIndex = heap,
        .valid_buffer_usage = valid_buffer_usage,
     };
  }

So, when got unlucky GPU you cannot have HOST_COHERENT_BIT and HOST_CACHED_BIT flags both set! Having this in mind i made a proof of the concept code insertion in DxvkMemoryAllocator::tryAlloc
	if ((flags &  (VK_MEMORY_PROPERTY_HOST_COHERENT_BIT | VK_MEMORY_PROPERTY_HOST_CACHED_BIT))
               == (VK_MEMORY_PROPERTY_HOST_COHERENT_BIT | VK_MEMORY_PROPERTY_HOST_CACHED_BIT))
		flags &= ~VK_MEMORY_PROPERTY_HOST_CACHED_BIT;

Perhaps, i did it ugly way but it indeed fixed the problem, or at least, sweep it under the carpet. No more errors of THAT kind, backgrounds and models are fine, textures in place. There are still some known BayTrail-vulkan related visual glitches and issues in games because of unfinished drivers but that's irrelevant to DXVK.
The essential from DXVK logs seem to proof the findings:

info:  DXVK: v1.0
warn:  OpenVR: Failed to locate module
info:  Enabled instance extensions:
info:    VK_KHR_get_physical_device_properties2
info:    VK_KHR_surface
info:    VK_KHR_win32_surface
info:  Intel(R) Bay Trail:
info:    Driver: 18.3.3
info:    Vulkan: 1.1.90
info:    Memory Heap[0]:
info:      Size: 1536 MiB
info:      Flags: 0x1
info:      Memory Type[0]: Property Flags = 0x7
info:      Memory Type[1]: Property Flags = 0xb

Yes, those property flags in logs again. I hope the above will help to get Intel Atoms in line.

Not using VK_MEMORY_PROPERTY_HOST_CACHED_BIT for read-back has a severe performance penalty (we're talking about hundreds of CPU cycles per read), so this is not a great solution.
Unfortunately, supporting non-coherent memory is also hard, especially when we don't want it to tank performance for the vast majority of hardware which supports it.
I don't have an Atom setup to test with anyway, although I could potentially simulate similar behaviour through a Vulkan layer.

For BayTrail, as for any build-in graphics with shared memory APU there is no great solutions really. And it seems there is no much choice but to hurt its performance for now. If it will just work, then it would be good enough already. Later on it could be fixed with a more strict flag management (if it is possible so) or some clever finding.
Just as i see it.

Baytrail is so weird, i am own one ,so i know

I ultimately decided to go with the non-CACHED memory type for now, not sure if implementing a proper fix is worth it. It would certainly be a ton of work.

I confirm the version 1.0.1 fixed the memory allocation problem and is working on real hardware.


rescheduling_token

Hi,
This is a great job! Very useful.
Can I ask where did you get the "rescheduling_token" value from?

Same question :)

Hi Tapan, your script is very useful, thank you!
But when it comes to autobooking, I also have the question about rescheduling_token, could you please explain where it comes from?

Same question here. also how to get consulate details?

Same question, what is rescheduling_token?


Lab 04L02, Error: The MSIX Application metadata expand request failed on all Session Hosts

Module: 4
Lab/Demo: 04L02, Package Azure Virtual Desktop applications (AD DS)
Exercise 3, Task: 3
Step: 6
When adding MSIX package, I got error:
{"code":"400","message":"ActivityId: eef203e1-f4dc-48d5-99ba-98d0f61c33ee Error: The MSIX Application metadata expand request failed on all Session Hosts that it was sent to. Session Host: az140-21-p1-1, Error: Error accessing virtual disk at ≤\\\\az140st02l02.file.core.windows.net\\az140-42-msixvhds\\packages\\XmlNotepad.vhd≥.Session Host: az140-21-p1-0, Error: Error accessing virtual disk at ≤\\\\az140st02l02.file.core.windows.net\\az140-42-msixvhds\\packages\\XmlNotepad.vhd≥."}
After I created a new storage account for storing the MSIX image, it worked.
I got the same issue during my demo env setup, unrelated to this lab. And a separate storage account solved the problem too. But I can't find any documentation stating any storage account related constraint or limitation.

Unfortunately I cannot reproduce this behavior. Pls let us know if you are seeing this issue on a more consistent basis.
rgds
Marcin

I know this is a bit old but we're having the same issue in a production environment. Did you ever find the cause?