pip missing all versions beyond 1.13.1

Rasbian 9 buster
TensorFlow installed from binary
TensorFlow version: 1.14.1
Python version: 3.7
Installed using pip

I need tensorflow version 1.14.0 specifically. Windows has the version I'm looking for. But when i run it on my pi pip says that 1.14.0 is missing and it only lists possible version numbers of 1.11.0, 1.12.0, and 1.13.1.
sudo python3.7 -m pip install tensorflow==1.14.0
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
ERROR: Could not find a version that satisfies the requirement tensorflow==1.14.0 (from versions: 0.11.0, 1.12.0, 1.13.1)
ERROR: No matching distribution found for tensorflow==1.14.0

I tried it in my ubuntu wsl.
It started installing with the command pip install tensorflow==1.14.0
I got the following when I tried your syntax.
Collecting tensorflow==1.14.0
ERROR: Could not find a version that satisfies the requirement tensorflow==1.14.0 (from versions: none)
ERROR: No matching distribution found for tensorflow==1.14.0```

I am able to install successfully with the command python3 -m pip install tensorflow==1.14.0 in my ubuntu1804 wsl. I will try in raspbian.

Try running the command python -m pip search tensorflow from your raspbian.

Try running the command python -m pip search tensorflow from your raspbian.
It should probably be some sort of compatibility issues.
Are you able to install from the links provided in https://www.tensorflow.org/install/pip at the bottom of the page?
Python 3, Pi0 or Pi1	https://storage.googleapis.com/tensorflow/raspberrypi/tensorflow-1.14.0-cp34-none-linux_armv6l.whl
Python 3, Pi2 or Pi3	https://storage.googleapis.com/tensorflow/raspberrypi/tensorflow-1.14.0-cp34-none-linux_armv7l.whl

Do these precompiled wheels work for python 3.7? It says 34

Official python 3.7 support was added only in 1.13 and later.

im getting this error when running sudo python3 -m pip install https://storage.googleapis.com/tensorflow/raspberrypi/tensorflow-1.14.0-cp34-none-linux_armv7 l.whl:
ERROR: tensorflow-1.14.0-cp34-none-linux_armv7l.whl is not a supported wheel on this platform.

Doe cp34-none-linux_armv71 show up in pip debug --verbose?

this was what was printed. Something similar but not exactly.
pip debug --verbose WARNING: This command is only meant for debugging. Do not use this with automation for parsing and getting these details, since the output and options of this command may change without notice. pip version: pip 19.3.1 from /home/pi/.local/lib/python3.7/site-packages/pip (python 3.7) sys.version: 3.7.3 (default, Apr  3 2019, 05:39:12)  [GCC 8.2.0] sys.executable: /usr/bin/python3.7 sys.getdefaultencoding: utf-8 sys.getfilesystemencoding: utf-8 locale.getpreferredencoding: UTF-8 sys.platform: linux sys.implementation:   name: cpython Compatible tags: 29   cp37-cp37m-manylinux2014_armv7l   cp37-cp37m-linux_armv7l   cp37-abi3-manylinux2014_armv7l   cp37-abi3-linux_armv7l   cp37-none-manylinux2014_armv7l   cp37-none-linux_armv7l   cp36-abi3-manylinux2014_armv7l   cp36-abi3-linux_armv7l   cp35-abi3-manylinux2014_armv7l   cp35-abi3-linux_armv7l   cp34-abi3-manylinux2014_armv7l   cp34-abi3-linux_armv7l   cp33-abi3-manylinux2014_armv7l   cp33-abi3-linux_armv7l   cp32-abi3-manylinux2014_armv7l   cp32-abi3-linux_armv7l   py3-none-manylinux2014_armv7l   py3-none-linux_armv7l   cp37-none-any   cp3-none-any   py37-none-any   py3-none-any   py36-none-any   py35-none-any   py34-none-any   py33-none-any   py32-none-any   py31-none-any   py30-none-any

This means that that specific pip won't be able to load/install. Due to toolchain differences.
You might need to compile from source

if i compile from source, wouldn't that just give me the same .whl that is downloadable from the links in the website? What difference would it make?

i have been able to install it by simply wget'ing the whl and renaming from tensorflow-1.14.0-cp34-none-linux_armv7l.whl to tensorflow-1.14.0-cp37-none-linux_armv7l.whl. with the only needed difference being the python version in the filename, as it would comply with pip. But I'm now experiencing a new issue when importing that i will make a separate issue on. #33872

The tags in the filename specify C++ ABI compatibility. Compiling from source will ensure you get all binaries that will run on your system.
Yes, you can install it (that is, unzip the files in the wheel) if you rename. But you can't use it without crashes and errors.

https://github.com/tensorflow/tensorflow/issues/33872#issuecomment-548476622

I have mac and I doing a fresh install and I have the same error
pip3  install tensorflow==1.14
ERROR: Could not find a version that satisfies the requirement tensorflow==1.14 (from versions: none)
ERROR: No matching distribution found for tensorflow==1.14

pip3 install --upgrade pip
Requirement already up-to-date

We haven't released any pip package for 3.8

Hi There,
We are checking to see if you still need help on this, as you are using an older version of tensorflow which is officially considered end of life . We recommend that you upgrade to the latest 2.x version and let us know if the issue still persists in newer versions. Please open a new issue for any help you need against 2.x, and we will get you the right help.
This issue will be closed automatically 7 days from now. If you still need help with this issue, please provide us with more information.

The issue is still relevant since there are no working Tensorflow 2.x builds for Python 3.7 (or newer) on the Raspberry Pi.

Please open a new issue for that. At the moment we no longer have anyone working on the RPi builds, instead we recommend using TFLite.
Closing this issue as it seems to have been caused by a very old pip and is old.


fix: folders and files with the word "index" cannot be accessed

There is a bug where if you name any folder or file with the word "index" it cannot be accessed (eg. http://localhost:3000/my_index/page) does not work.

Fixed at https://github.com/oedotme/generouted/releases/tag/v1.6.13


[2.0] Add missing fields in job definition

The Go types were not in sync with the actual definition.
https://github.com/dcos/dcos-cli/issues/1494

How about generating this structs from Marathon and Metronome RAML API definiton with https://github.com/Jumpscale/go-raml


Comparison with astromodels

The format I am designing for astromodels to specify functions is very similar to what you are trying to achieve, so maybe we can try to converge. This is what I have:
powerlaw:

    description :

        A simple power-law with normalization expressed as
        a logarithm

    formula :

        expression : 10**logK * (x / piv)**index

        latex :

            \frac{dN}{dx} = 10^{logK}~\frac{x}{piv}^{index}

    parameters:

        logK :

            desc : Logarithm of normalization
            initial value : 0
            min : -40
            max : 40

        piv :

            desc : Pivot energy
            initial value : 1
            fix : yes

        index :

            desc : Photon index
            initial value : -2
            min : -10
            max : 10

powerlaw_flux:

    description:

        A simple power-law with the integral between two extremes as
        normalization parameter

    formula:

        expression : 10**(logK) * (index + 1) * (x / piv)**index /
                     ( xmin**(index+1) - xmax**(index+1) )

        latex :

            \frac{dN}{dx} = \frac{index + 1}{xmin^{index+1} - xmax^{index+1}}
                            10^{logK}~\frac{x}{piv}^{index}

    parameters:

        logK :

            desc : Logarithm of normalization
            initial value : 0
            min : -40
            max : 40

        piv :

            desc : Pivot energy
            initial value : 1
            fix : yes

        index :

            desc : Photon index
            initial value : -2
            min : -10
            max : 10

        xmin :

            desc : Lower bound of integration
            initial value : 1

        xmax :

            desc : Upper bound of integration
            initial value : 10

This can easily be read from python as:

import yaml

with open("astromodels/functions/powerlaw.yaml","r") as f:
    d = yaml.load(f)

print(d['powerlaw'])
'A simple power-law with normalization expressed as a logarithm'

print(d['powerlaw']['parameters']['index'])
{'max': 10, 'initial value': -2, 'desc': 'Photon index', 'min': -10}

Maybe we can analyze our respective trials and merge the good things about both in one format.

same question as in https://github.com/gammapy/gamma-astro-data-formats/issues/1
How can I use this format to store fit results? I.e. where do I store fitted values of parameters?
directly in d['powerlaw']['parameters']['index'] ? Or is this format just for defining the model?

@joleroi - up to now we have only had model definition formats, but it should definitely include at some point fit results. Probably a value and error keywords as a minimum. The error part is a bit difficult - other keywords should be used to specify its properties (confidence level, gaussian, asymetrical, etc) and probably have an option to store a posterior distribution histogram or samples. Some things have been done in astropy to add uncertainties to quantities, but they are quite spread out and I can't really get a good idea of it.

Is it better to have one schema for model specification and fit results or two?
The model XML format in the Fermi Science Tools uses one schema for both.
But then there's things like TS values and covariance matrix missing and need to be stored in separate files or added in ad-hoc places in the XML file without an agreement how it's stored.
It's not clear to me yet if there are significant pros and cons to the two possible approaches (or a mix with some extra info stored with the model spec, and some separated out).
@giacomov and all - do you have an opinion here? is someone willing to work out a proposal?

I believe we need two schemas, one for model specification and one for
saving results.
Actually, I think that a more helpful separation is between  a schema for
specifying functions and their parameters (as the one I discussed above),
and one for specifying a complete likelihood model, made of any number of
sources, with point-like or extended sources, each one with a arbitrary
number of components and features.
I think that the first schema (model specification) should be dead simple,
to allow users to implement their own models easily by interacting directly
with it through their favorite text editor (or python).
The second schema instead must use functions defined with the first schema
(by name) and favor flexibility, because it must accomodate all the needs
that we have in terms of modeling. This second schema should also be able
to store fit results.
My two cents,
On Dec 7, 2015 3:54 AM, "Christoph Deil"<EMAIL_ADDRESS>wrote:

Is it better to have one schema for model specification and fit results or
two?
The model XML format in the Fermi Science Tools uses one schema for both.
But then there's things like TS values and covariance matrix missing and
need to be stored in separate files or added in ad-hoc places in the XML
file without an agreement how it's stored.
It's not clear to me yet if there are significant pros and cons to the two
possible approaches (or a mix with some extra info stored with the model
spec, and some separated out).
@giacomov https://github.com/giacomov and all - do you have an opinion
here? is someone willing to work out a proposal?
—
Reply to this email directly or view it on GitHub
https://github.com/gammapy/gamma-astro-data-formats/issues/4#issuecomment-162502299
.

FYI: in the process of looking for a config file handling / schema validation package to use in Gammapy (see https://github.com/gammapy/gammapy/issues/401), I came across python-anyconfig. (There's a ton of similar packages, we haven't made the choice to use that one yet.)
It has functions and even a command line tool for easy schema generation and validation (see here) using jsonschema in the background. There's also schema.
I know the purpose of this repo is to agree on formats, not to provide codes. But providing schemas and some docs on how to use them is in scope, no?

Hi,
I found a little more time to work on astromodels, and I have now a quick tutorial which can be followed:
astromodels.readthedocs.org
It shows the basic functionality. More advanced features, such as time-dependent parameters or handling of polarization, are already kind of half-implemented but not mature enough for primetime.
Comments and contributions are very welcome.

@giacomov - My main comment / concern is that I'm not a fan of astromodels as yet another general astro modeling package. Personally I prefer to build on Sherpa and Astropy and contribute missing features there.
We're still in the situation that there's zero code sharing between 3ML, Naima and Gammapy.
@zblz - What do you think? Do you want to use astromodels in Naima?

@cdeil I agree that it is not desirable to have 3 packages doing the same thing. However, the scope of astromodels is merely the definition and handling (loading, saving) of the model, there will be no fitting or sampling capability, so the overlap is limited.
I tried to get the sherpa code and modified it for my purposes, but I ended up needing changes too big for them to be acceptable for a mature and widely used package. It is also pretty difficult to implement these things without breaking things up, as the package is big.
With astropy the situation looks a little better because the modeling part is not so developed, but still I would need pretty big changes.
Also, both packages are quite a lot slower than what they could be (especially astropy). See here for a quick-and-dirty speed comparison:
https://gist.github.com/giacomov/aacc8feebc745717276a
If there is the possibility for working astromodels or part of it into one of those packages (more likely astropy than sherpa), I am definitely open to it.
Looking forward to out meeting this Friday.

@giacomov - Thanks for your comment and for the open discussion!
The issue I have with the current way 3ML / astromodels is implemented is that it's a full multi-mission modeling / fitting package, with similar goals as Sherpa (see 2001SPIE.4477...76F on the multi-mission aspect and the Scipy2009 proceeding for the architecture).
I know Sherpa has issues and am aware that this is needed:

Port to Python 3
Sphinx docs
Add MINUIT as one of the available optimizers / error estimators (not because it's really needed, but because it's the gold standard that physicists and gamma-ray astronomers like)
There are issues in the Sherpa Github tracker for all of them and this will all happen in the coming months.

Basically I think Sherpa is a huge piece of work, well done, actively maintained and now open development and very friendly to gamma-ray astronomers, and my strong preference would be that we add to it or built on top of it.
At the core this means that we directly use or sub-class the Sherpa parameter and model classes, and not create a new parameter and base model class that is incompatible with the Sherpa framework, i.e. you can't fit the current astromodels with Sherpa.
I don't have a full vision what is needed to make Sherpa work for our applications (extra models, combined spatial/spectral models, model serialisation, ...?)
But I'd like to try and see if we hit any fundamental issues for important use cases that Sherpa can't handle.
So @giacomov - maybe a good first step would be to define one or very few analysis use-cases that I try to implement with Sherpa and you with the current 3ML / astromodels. Worst case is that we go separate ways and we'll still have a nice cross-check of the tools. Best case we agree and collaborate a lot in the coming months instead of duplicating effort.

@cdeil @giacomov thank you for the discussion.
I found the point raised by @giacomov on speed quite relevant: would there be a way to improve the sherpa modeling package for speed in a way acceptable for current sherpa users and the main developers?
To me, however, the main question remains: is there a way to plug into sherpa info from a dataset remaining completely agnostic about how the data format is and the data are treated, i.e., just by providing a likelihood value for the dataset given a certain model from external software? This capability in my view is the key of the flexibility/easiness in extending to new/different datasets in 3ML. I would define the test use case to investigate this particular aspect. @cdeil: any suggestions on how to build such test case concretely?

I found the point raised by @giacomov on speed quite relevant: would there be a way to improve the sherpa modeling package for speed in a way acceptable for current sherpa users and the main developers?

I think the speed is just determined by how fast your model evaluate is implemented.
Maybe we'll have to re-implement Sherpa morphology or spectral models to be faster.
Or because we like to have e.g. sky lon / lat as fit parameters instead of x / y.
Note that even if we don't use any of the built-in Sherpa models, we can still use the Sherpa framework,
i.e. implement the models as classes that sub-class ArithmeticModel and use the Sherpa Parameter class.
A big advantage remains -- The powerful and established Sherpa modeling language to construct complex models (e.g. background + signal * absorption_line), all the Sherpa dataset, optimizer, fit statistic and error estimator algorithms and the interactive Sherpa fitting environment that many X-ray and gamma-ray astronomers like.

To me, however, the main question remains: is there a way to plug into sherpa info from a dataset remaining completely agnostic about how the data format is and the data are treated, i.e., just by providing a likelihood value for the dataset given a certain model from external software? This capability in my view is the key of the flexibility/easiness in extending to new/different datasets in 3ML. I would define the test use case to investigate this particular aspect. @cdeil: any suggestions on how to build such test case concretely?

I need to investigate ... depending on what exactly you want to do it might require implementing a new Data subclass (see https://github.com/sherpa/sherpa/blob/master/sherpa/data.py#L163) and / or Stat subclass (see https://github.com/sherpa/sherpa/blob/master/sherpa/stats/init.py#L48) or if convolution is involved a ConvolutionModel subclass (see https://github.com/sherpa/sherpa/blob/master/sherpa/instrument.py#L36).
Not sure if I have time to experiment this week ... I'll try.
@giacomov or @tibaldo, if you already have something or have time to have a look, that would be great of course.

I don't have time to look into Sherpa before our call on Friday.
So for now I've just asked here:
https://github.com/sherpa/sherpa/issues/184

Some updates:

There's an open pull request to add quantity support to Astropy modeling.
There's a proposed GSoC 2016 project to "Bridge sherpa and astropy fitting"
http://openastronomy.org/gsoc/gsoc2016/ideas.html#Astropy
We're starting to play around with Sherpa modeling in https://github.com/gammapy/gammapy/pull/479 to learn how Sherpa really works and to see if our use cases can be implemented using Sherpa nicely.

@giacomov - It would be very valuable to have a similar example script that represents some important use case for you and does some analysis with astromodels / 3ML (e.g. the time-dependent modeling you mentioned). Then we could check if we can or can't nicely implement that using Sherpa.

There's discussion here at PyAstro16 how to move forward with modeling for astronomers.
We're now starting to collect notes and use cases (preferably, but not necessarily with working code) here: https://github.com/astropy/astropy-model-ideas
@giacomov or anyone else interested in modeling: we should continue the discussion there via pull requests and issues. This format spec and serialisation is important, but the scope of the discussion here has extended way beyond what's appropriate for gamma-astro-data-formats.
E.g. https://gist.github.com/giacomov/aacc8feebc745717276a would be an interesting contribution.
(I don't think the speed comparison is done correctly, in reality the overhead is lower because Astropy and Sherpa provide a different interface to the optimizer than the way you're calling it. But such things are what we want to investigate and discuss via example code files and notebooks in the astropy-model-ideas repo.


Add endpoint that returns group membership given a token

@ChuckKollar I added the method AuthHelper.get_user_write_groups(<user_token>). It is pushed to my branch of hubmap_commons- shirey/refactor-mult-apps


Store height offset explicitly, split Tx and Block options

Instead of using log table - means we always remember a block we have
seen even if we did nothing with it.
Also refactor towards more shared query code via sqlx
Signed-off-by: Silas Davis<EMAIL_ADDRESS>

Main file of note here is sqldb.go which github helpfully collapses...


Fix Exemptions in version 7.1.0

In the following scripts Build-ExemptionsPlan.ps1 and Build-DeploymentPlans.ps1 the following changes need to be made for exemptions to be managed properly.
Build-DeploymentPlans.ps1:
The following code block
$exemptionsAreManaged = $null -ne $pacEnvironment.policyExemptionsFolder
if ($exemptionsAreManaged) {
    $exemptionsFolderForPacEnvironment = "$($pacEnvironment.policyExemptionsFolder)/$($pacEnvironment.pacSelector)"
    $exemptionsAreManaged = Test-Path $exemptionsFolderForPacEnvironment
    if (!$exemptionsAreManaged) {
        Write-Warning "Policy Exemptions folder $($exemptionsFolderForPacEnvironment) not found"
        Write-Warning "Policy Exemptions are not managed by EPAC this PaC environment $($pacEnvironment.pacSelector)!"
    }
}
$scopeTable = Get-AzScopeTree -pacEnvironment $pacEnvironment
$deployedPolicyResources = Get-AzPolicyResources -pacEnvironment $pacEnvironment -scopeTable $scopeTable -skipExemptions:$exemptionsAreManaged

Needs to be changed back to
$exemptionsAreManaged = $null -ne $pacEnvironment.policyExemptionsFolder
if ($exemptionsAreManaged) {
    $exemptionsFolderForPacEnvironment = "$($pacEnvironment.policyExemptionsFolder)/$($pacEnvironment.pacSelector)"
    $exemptionsAreManaged = Test-Path $exemptionsFolderForPacEnvironment
    $exemptionsAreNotManaged = !$exemptionsAreManaged
    if (!$exemptionsAreManaged) {
        Write-Warning "Policy Exemptions folder $($exemptionsFolderForPacEnvironment) not found"
        Write-Warning "Policy Exemptions are not managed by EPAC this PaC environment $($pacEnvironment.pacSelector)!"
    }
}
$scopeTable = Get-AzScopeTree -pacEnvironment $pacEnvironment
$deployedPolicyResources = Get-AzPolicyResources -pacEnvironment $pacEnvironment -scopeTable $scopeTable -skipExemptions:$exemptionsAreNotManaged

With the new changes since the exemption folder does exist that value is set to True which is then passed to the -skipExemptions Parameter. Since the value is true it skips the exemption deployment. Tested in my environment and this is the case, i have changed it back to the old version which was in a previous version where we pass in $exemptionsAreNotManaged which evaluates to false and exemptions are not skipped and it processes exemptions correctly
Build-ExemptionsPlan.ps1:
The following code block
if ($deployedManagedExemption.policyAssignmentId -ne $policyAssignmentId) {
    # Replaced Assignment
    Write-Information "Replace(assignment) '$($name)', '$($scope)'"
    $null = $replacedExemptions.Add($id, $exemption)
    $exemptions.numberOfChanges++
}
elseif ($replacedAssignments.ContainsKey($policyAssignmentId)) {
    # Replaced Assignment
    Write-Information "Replace(reference) '$($name)', '$($scope)'"
    $null = $replacedExemptions.Add($id, $exemption)
    $exemptions.numberOfChanges++
}

Needs to be changed to
if ($deployedManagedExemption.policyAssignmentId -ne $policyAssignmentId) {
    # Replaced Assignment
    Write-Information "Replace(assignment) '$($name)', '$($scope)'"
    $null = $exemptions.replace.Add($id, $exemption)
    $exemptions.numberOfChanges++
}
elseif ($replacedAssignments.ContainsKey($policyAssignmentId)) {
    # Replaced Assignment
    Write-Information "Replace(reference) '$($name)', '$($scope)'"
    $null = $exemptions.replace.Add($id, $exemption)
    $exemptions.numberOfChanges++
}

the variable replacedExemptions is not defined anywhere at all in the repo we need to pass in the exemptions object and reference the replace property in it instead for this to work. Tested and working with this change

Thank you for submitting the issue.


Expose epic_id field in issue create/update opts

This PR expose epic_id field in issue create/update options.
Reference: https://docs.gitlab.com/ee/api/issues.html

@svanharmelen , would you be able to take a look at this one-liner?


WiP: GraalVM in a Browser

The Idea
since GraalVM can run Javascript and offers a Relativ Compatible API to v8 The Chromium Embedder Framework could get used as raw building block for Cross Platform Desktop Applications using the Blink Rendering Engine and GraalVM Isolates for Code Processing.
i talked about that in issue: https://github.com/oracle/graaljs/issues/229 which was related because i am also experimenting with Android browsers and running Software via GraalVM there to be more precise.

[ ] - Using the GraalVM as v8 Replacement in a CEF Fork
[ ] - augument security problems and apis that are problematic when they get accessed from the Public web.
[ ] - Define and create a standard for diffrent language workers to expose the languages in a web frindly way.
[ ] - in general all the work that got done in tc39 and Chromium and Moz to make sure that the web can not access the local pc
[ ] Publish vertx-chromium (ES4X + Chromium Ozon Aura Window Manager) aka Chromitex
(Chromium running fully bound to the vertx eventloop) nio gets used as transport so we can even channel EPOLL Like justJS does up to  400% Compared to nodejs libuv loop. Chromium internal uses also libuv
some chomium code now even depends on node code we share it at last to link at it on build chromium / external / github.com / v8 / node /

[ ] Create a small api to expose Ozone Aura Wayland x11 Support and Positioning APIS
[ ] Create a small api to hook into the chromium Platform Manager (devtools protocol)
[ ] As Part of that Refactor puppeteer npm package maintained by Chromium Devtools Protocol team.

closed by:

https://github.com/lemanschik/web-modules/issues/4


license not gpl

FUK

my finger slipped

o well i guess were stuck now

u know what they say

once u go bsd

richard stallman will never talk 2 u again

great, now every for-profit company is going to take this code, improve it, and then sell it.  good going.

dammit alex im so disappointed in myself right now

what should i do

i guess this is it

im not meant for computers

quit

####### ok

ok

ok

ok

i want to close this but i cant close the deep shame i feel

:+1:

wow paul cant believe ud say that

im personally offended

u guys are insane

personally offended that you would edit my comment....
here is what it originally said.


cucumberJson output does not respect folders

Current behavior
I have some feature files that have the same name but in different folders, for instance:
OMA/Enrolment.feature
GLI/Enrolment.feature

Also I have the following configuration in my package.json:
  "cypress-cucumber-preprocessor": {
    "step_definitions": "cypress/support/steps/",
    "nonGlobalStepDefinitions": false,
    "cucumberJson": {
      "generate": true,
      "outputFolder": "reports/cypress"
    }
  },

After the test run there is only one Enrolment.cucumber.json in the reports/cypress folder.
Desired behavior
I'd like reports/cypress to look like this:
OMA/Enrolment.cucumber.json
GLI/Enrolment.cucumber.json

Versions

Cypress version: 4.7.0
Preprocessor version: 2.4.0
Node version:  12.8.0

Will this ever be merged into master?

Due to personal reasons, the previous maintainers of this package are stepping down and handing the reigns over to me, a long-time contributor to the project and a user of it myself. This is a responsibility I'm very excited about. Furthermore, I'd like to thank @lgandecki ++ for all the work that they've done so far.
Read more about the transfer of ownership here.
The repository has however moved and all outstanding issues are being closed. This is not a reflection of the perceived importance of your reported issue. However, if after upgrading to the new version, you still find there to be an issue, feel free to open up another ticket or comment below. Please make sure to read CONTRIBUTING.md before doing so.


Website | Gallery: Donut Example #38

Add a gallery example which showcases the use of a basic donut chart. (issue)

[x] Create a folder in shared/examples directory called basic-donut-chart with all the relevant files
[x] Find dataset and create example in basic-donut-chart.tsx

Add code for other frameworks:

[x] TypeScript
[x] Angular
[x] Svelte
[x] Vue

And then add screenshots to _shared/previews:

[x] basic-donut-chart.png
[x] basic-donut-chart-dark.png

@reb-dev It might be a good time to enforce the Commit Lint formats: https://github.com/f5/unovis/pull/300

Great job @lee00678!
I'm a little concerned about the visual aspects of the new example because it's inconsistent with other examples and our Unovis brand. Specifically, the colors and the capitalized text in the legend.

I'm happy to make any changes! Also nice to "meet" both of you @rokotyan and @Dovlash. Yes, I used D3's color theme as I ran out of the default colors for donut chart. I can probably look into how to get unovis' color theme rendered, and I will update the legend as well.

Nice to meet you too @lee00678!
I see, I think instead of showing so many slices, we can merge smaller ones into a big "Others" one.
Here's two great posts about Pie Charts and Colors in data vis:

What to consider when creating pie charts
10 ways to use fewer colors in your data visualizations

Nice to meet you too @lee00678!
I see, I think instead of showing so many slices, we can merge smaller ones into a big "Others" one. Here are two great posts about Pie Charts and Colors in data vis:

What to consider when creating pie charts
10 ways to use fewer colors in your data visualizations

I like the idea of combining the smaller categories. Made an update on that.

Nice, thanks for the update!

@lee00678 Btw, if you use Discord, we've a space there which we're planning to make public soon. Feel free to join: https://discord.gg/zATXusWgCP

CLA Assistant Lite bot: 🎉 Thank you for your contribution. It appears you have not yet signed the F5 Contributor License Agreement (CLA), which is required for your changes to be incorporated into an F5 project. Please kindly read the F5 CLA and comment the following to agree:
I have hereby read the F5 CLA and agree to its terms
Qian Liu 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 can retrigger this bot by commenting recheck in this Pull Request

Agree


VM: MegamorphicLookup #6: mixin pattern

This issue is split out from https://github.com/dart-lang/sdk/issues/26017
In dart2js,  ElementX.isField is defined by a mixin
class ElementCommon {
   bool get isField => kind == ElementKind.FIELD;
}

get:kind is defined in various places, leading to a MegamorphicLookup from the mixin code.
If get:isField was cloned to the classes defining get:kind, then get:kind could be inlined.
get:kind is usually a field (on ElementX) or a returns a constant.

Duplicate of #26858


add Env to NME Preview

We can custom Env, Image and toggle Env / Background color now.

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Snapshot stored with reference name:
refs/pull/14398/merge
Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14398/merge/index.html
To test a playground add it to the URL, for example:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14398/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/14398/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/14398/merge
https://gui.babylonjs.com/?snapshot=refs/pull/14398/merge
https://nme.babylonjs.com/?snapshot=refs/pull/14398/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/14398/merge#BCU1XR#0

LGTM if @PatrickRyanMS is all good with it :-)

Also one last thought for @RaananW to be sure importing .env would not break any kindz of buildzzzz 🐝🐝🐝🐝🐝

Also one last thought for @RaananW to be sure importing .env would not break any kindz of buildzzzz 🐝🐝🐝🐝🐝

Works fine, as this is just a static file in the public directory.
Might cause an issue when used as a package, as you will need to deliver the file yourself.

Nice thanks a lot !!! a last change and I can merge it in :-) Could you make "https://assets.babylonjs.com/environments/environmentSpecular.env" a public static so that users can point it at their own URL if need be :-)

yes. Now it is a exists URL of babylon assets (https://assets.babylonjs.com), not a file .

I use this URL as other source codes of babylon.js .your can find the URL in bellow files:
packages\dev\core\src\Helpers\environmentHelper.ts
packages\tools\sandbox\src\tools\environmentTools.ts

yes but in environmentHelper users can override it here https://github.com/BabylonJS/Babylon.js/blob/master/packages/dev/core/src/Helpers/environmentHelper.ts#L344 and sandbox is not meant to be used as a framework.
Users needs to be able to control where they download assets from.

yes but in environmentHelper users can override it here https://github.com/BabylonJS/Babylon.js/blob/master/packages/dev/core/src/Helpers/environmentHelper.ts#L344 and sandbox is not meant to be used as a framework.
Users needs to be able to control where they download assets from.

your mean is. ........"user need custom a env of the NME Preview window?" . I has add a "upload button" on the right of "model ComboBox" in NME Preview window. so user can override the default env "https://assets.babylonjs.com/environments/environmentSpecular.env".

Oh no, sorry, I just mean if you move it in a static public field or a let in the module so a developer consuming the npm package can change it before loading nme.

a public static

or...... your mean is a public static  filed  of the class?

something like this:
public static DefaultEnvironmentURL = "https://assets.babylonjs.com/environments/environmentSpecular.env"';

private _refreshPreviewMesh(force?: boolean) {
        switch (this._globalState.envType) {
            case PreviewType.Room:
                this._hdrTexture = new CubeTexture(DefaultEnvironmentURL , this._scene);
                if (this._hdrTexture) {
                    this._prepareBackgroundHDR();
                }
                break;
            case PreviewType.Custom: {
                const blob = new Blob([this._globalState.envFile], { type: "octet/stream" });
                const reader = new FileReader();
                reader.onload = (evt) => {
                    const dataurl = evt.target!.result as string;
                    this._hdrTexture = new CubeTexture(dataurl, this._scene, undefined, false, undefined, undefined, undefined, undefined, undefined, ".env");
                    this._prepareBackgroundHDR();
                };
                reader.readAsDataURL(blob);
                break;
            }
        }

something like this:
public static DefaultEnvironmentURL = "https://assets.babylonjs.com/environments/environmentSpecular.env"';

private _refreshPreviewMesh(force?: boolean) {
        switch (this._globalState.envType) {
            case PreviewType.Room:
                this._hdrTexture = new CubeTexture(DefaultEnvironmentURL , this._scene);
                if (this._hdrTexture) {
                    this._prepareBackgroundHDR();
                }
                break;
            case PreviewType.Custom: {
                const blob = new Blob([this._globalState.envFile], { type: "octet/stream" });
                const reader = new FileReader();
                reader.onload = (evt) => {
                    const dataurl = evt.target!.result as string;
                    this._hdrTexture = new CubeTexture(dataurl, this._scene, undefined, false, undefined, undefined, undefined, undefined, undefined, ".env");
                    this._prepareBackgroundHDR();
                };
                reader.readAsDataURL(blob);
                break;
            }
        }

thanks. I got it :)

Just to be sure we are ok with the GUI, here's how it appears:
cc @PatrickRyanMS

sorry for the late response, I have been out of the office. The only thing I see is that the icon for environment is a little small in comparison to the rest on the bar. It should be sized to fit with the size of the other icons. If needed, I can provide a new icon, but it would be preferable to use the same svg if possible. Something like this:

@PatrickRyanMS it looks real strange zoomed in like it would be a bold font :-( could you create another svg ? like the other ones in the bar ?

I can make a new svg to fit with the current icons. Give me a few minutes.

@sebavan, here's the updated icon. This is saved at the same size as the rest of the icons, so the css should be the same:
environment_24_regular.zip


Deltalake merge issue with large updates

We have been using Delta lake for the last 6 months and it's been running successfully in production on a lot of datasets. Currently, there is a weird issue with one of the datasets. On the target, the delta lake table has 3M records, and update with 300K records failing with the below error. Tried to increase the executor memory, driver memory, and overhead memory but none of the options are helping. is there a specific setting that helps in this situation?
Environment:
emr-5.30.1
Spark 2.4.5
Delta 0.6.1
Cluster: 250GB memory
Job submitted with various settings
executorMemory 4G to 12GB
executorcores 2 to 4
driverMemory 4G drivercores 2 to 4
executorinstances 2 to 4
extraJavaOptions and -XX:+UseG1GC -XX:+UnlockDiagnosticVMOptions -XX:+G1SummarizeConcMark -XX:InitiatingHeapOccupancyPercent=35 -XX:OnOutOfMemoryError='kill -9 %p'
with extra Java option -XX:OnOutOfMemoryError='kill -9 %p', the job killed with in min with OOM error and without that option, the job run for a while and raises the following error in logs
Stack Trace:
An error occurred while calling o376.execute. : org.apache.spark.util.SparkFatalException at org.apache.spark.sql.execution.exchange.BroadcastExchangeExec.org$apache$spark$sql$execution$exchange$BroadcastExchangeExec$$doComputeRelation(BroadcastExchangeExec.scala:119) at org.apache.spark.sql.execution.exchange.BroadcastExchangeExec$$anon$1.doCompute(BroadcastExchangeExec.scala:63) at org.apache.spark.sql.execution.exchange.BroadcastExchangeExec$$anon$1.doCompute(BroadcastExchangeExec.scala:59) at org.apache.spark.sql.execution.AsyncDriverOperation$$anonfun$org$apache$spark$sql$execution$AsyncDriverOperation$$compute$1.apply(AsyncDriverOperation.scala:75) at org.apache.spark.sql.execution.QueryExecutionMetrics$.withMetrics(QueryExecutionMetrics.scala:141) at org.apache.spark.sql.execution.SQLExecution$.org$apache$spark$sql$execution$SQLExecution$$withMetrics(SQLExecution.scala:178) at org.apache.spark.sql.execution.SQLExecution$.org$apache$spark$sql$execution$SQLExecution$$withMetrics(SQLExecution.scala:171) at org.apache.spark.sql.execution.SQLExecution$$anonfun$withExecutionId$1.apply(SQLExecution.scala:153) at org.apache.spark.sql.execution.SQLExecution$.withSQLConfPropagated(SQLExecution.scala:200) at org.apache.spark.sql.execution.SQLExecution$.withExecutionId(SQLExecution.scala:150) at org.apache.spark.sql.execution.AsyncDriverOperation.org$apache$spark$sql$execution$AsyncDriverOperation$$compute(AsyncDriverOperation.scala:69) at org.apache.spark.sql.execution.AsyncDriverOperation$$anonfun$computeFuture$1.apply$mcV$sp(AsyncDriverOperation.scala:51) at org.apache.spark.sql.execution.SQLExecution$$anon$1.run(SQLExecution.scala:221) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) at org.apache.spark.sql.execution.adaptive.AdaptiveExecutor.checkNoFailures(AdaptiveExecutor.scala:146) at org.apache.spark.sql.execution.adaptive.AdaptiveExecutor.doRun(AdaptiveExecutor.scala:88) at org.apache.spark.sql.execution.adaptive.AdaptiveExecutor.tryRunningAndGetFuture(AdaptiveExecutor.scala:66) at org.apache.spark.sql.execution.adaptive.AdaptiveExecutor.execute(AdaptiveExecutor.scala:57) at org.apache.spark.sql.execution.adaptive.AdaptiveSparkPlanExec$$anonfun$finalPhysicalPlan$1.apply(AdaptiveSparkPlanExec.scala:128) at org.apache.spark.sql.execution.adaptive.AdaptiveSparkPlanExec$$anonfun$finalPhysicalPlan$1.apply(AdaptiveSparkPlanExec.scala:127) at org.apache.spark.sql.SparkSession.withActive(SparkSession.scala:777) at org.apache.spark.sql.execution.adaptive.AdaptiveSparkPlanExec.finalPhysicalPlan(AdaptiveSparkPlanExec.scala:127) at org.apache.spark.sql.execution.adaptive.AdaptiveSparkPlanExec.executeCollect(AdaptiveSparkPlanExec.scala:134) at org.apache.spark.sql.Dataset$$anonfun$count$1.apply(Dataset.scala:2838) at org.apache.spark.sql.Dataset$$anonfun$count$1.apply(Dataset.scala:2837) at org.apache.spark.sql.Dataset$$anonfun$52.apply(Dataset.scala:3370) at org.apache.spark.sql.execution.SQLExecution$.org$apache$spark$sql$execution$SQLExecution$$executeQuery$1(SQLExecution.scala:83) at org.apache.spark.sql.execution.SQLExecution$$anonfun$withNewExecutionId$1$$anonfun$apply$1.apply(SQLExecution.scala:94) at org.apache.spark.sql.execution.QueryExecutionMetrics$.withMetrics(QueryExecutionMetrics.scala:141) at org.apache.spark.sql.execution.SQLExecution$.org$apache$spark$sql$execution$SQLExecution$$withMetrics(SQLExecution.scala:178) at org.apache.spark.sql.execution.SQLExecution$$anonfun$withNewExecutionId$1.apply(SQLExecution.scala:93) at org.apache.spark.sql.execution.SQLExecution$.withSQLConfPropagated(SQLExecution.scala:200) at org.apache.spark.sql.execution.SQLExecution$.withNewExecutionId(SQLExecution.scala:92) at org.apache.spark.sql.Dataset.withAction(Dataset.scala:3369) at org.apache.spark.sql.Dataset.count(Dataset.scala:2837) at org.apache.spark.sql.delta.commands.MergeIntoCommand.org$apache$spark$sql$delta$commands$MergeIntoCommand$$findTouchedFiles(MergeIntoCommand.scala:246) at org.apache.spark.sql.delta.commands.MergeIntoCommand$$anonfun$run$1$$anonfun$apply$1$$anonfun$1.apply(MergeIntoCommand.scala:153) at org.apache.spark.sql.delta.commands.MergeIntoCommand$$anonfun$run$1$$anonfun$apply$1$$anonfun$1.apply(MergeIntoCommand.scala:153) at com.databricks.spark.util.DatabricksLogging$class.recordOperation(DatabricksLogging.scala:77) at org.apache.spark.sql.delta.commands.MergeIntoCommand.recordOperation(MergeIntoCommand.scala:93) at org.apache.spark.sql.delta.metering.DeltaLogging$class.recordDeltaOperation(DeltaLogging.scala:103) at org.apache.spark.sql.delta.commands.MergeIntoCommand.recordDeltaOperation(MergeIntoCommand.scala:93) at org.apache.spark.sql.delta.commands.MergeIntoCommand$$anonfun$run$1$$anonfun$apply$1.apply(MergeIntoCommand.scala:152) at org.apache.spark.sql.delta.commands.MergeIntoCommand$$anonfun$run$1$$anonfun$apply$1.apply(MergeIntoCommand.scala:134) at org.apache.spark.sql.delta.DeltaLog.withNewTransaction(DeltaLog.scala:188) at org.apache.spark.sql.delta.commands.MergeIntoCommand$$anonfun$run$1.apply(MergeIntoCommand.scala:134) at org.apache.spark.sql.delta.commands.MergeIntoCommand$$anonfun$run$1.apply(MergeIntoCommand.scala:133) at com.databricks.spark.util.DatabricksLogging$class.recordOperation(DatabricksLogging.scala:77) at org.apache.spark.sql.delta.commands.MergeIntoCommand.recordOperation(MergeIntoCommand.scala:93) at org.apache.spark.sql.delta.metering.DeltaLogging$class.recordDeltaOperation(DeltaLogging.scala:103) at org.apache.spark.sql.delta.commands.MergeIntoCommand.recordDeltaOperation(MergeIntoCommand.scala:93) at org.apache.spark.sql.delta.commands.MergeIntoCommand.run(MergeIntoCommand.scala:133) at io.delta.tables.DeltaMergeBuilder.execute(DeltaMergeBuilder.scala:236) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at py4j.reflection.MethodInvoker.invoke(MethodInvoker.java:244) at py4j.reflection.ReflectionEngine.invoke(ReflectionEngine.java:357) at py4j.Gateway.invoke(Gateway.java:282) at py4j.commands.AbstractCommand.invokeMethod(AbstractCommand.java:132) at py4j.commands.CallCommand.execute(CallCommand.java:79) at py4j.GatewayConnection.run(GatewayConnection.java:238) at java.lang.Thread.run(Thread.java:748)

Seem like you have to do a bit more Spark debugging to solve this. Is the OOM happening on the driver or executor? From the stack trace, my guess is that it's trying to do a broadcast hash join in the first scan of merge (to find the files to rewrite) and failing to collect the source side of the join in the driver because there is not enough memory in the driver. Or it's hitting some broadcast limit in the driver.
Here are some things to try

Dig through the error in the logs to see if there is more info on what threshold it is hitting. try increasing that threshold and/or increasing the driver memory size further.
If you are giving the hint to broadcast, remove that hint. basically.. avoid using broadcast join because your source is large.

@kkr78 I'm going to close this one due to inactivity.
Please do reopen it if you're still experiencing an issue - thanks!


Fix Travis and Deploy page to gh-pages branch

The page is currently not deployed properly. Travis should be deploying it to the gh-pages branch, but it fails.
Please help to fix it.

Deployment is fixed :tada:


error when build

i got this error when build:
github.com/gammazero/workerpool ../../go/src/github.com/gammazero/workerpool/workerpool.go:50:15: cannot use generic type deque.Deque[T any] without instantiation

Thanks for reporting this issue. Can you please provide me the Golang version you have been using? I believe it is Go 1.18.x


Test enhancement

Changed log

Add php-7.3 and php-7.4 version tests.
Using the assertSame to make assert equals checking strict.
Updating cached dependencies with composer update command and it can make php ./vendor/bin/phpcs --standard=psr2 src command worked successfully.

Thank you @peter279k !


implement the generic setter

Signed-off-by: Kuat Yessenov<EMAIL_ADDRESS>Fixes https://github.com/envoyproxy/envoy-wasm/issues/198

Using metadata simplifies inter-op with native extensions as long as we don't do proto merge, and only override top-level keys.

I'm not sure why onTick suddenly behaves differently in WASM with this change.

@jplevyak @PiotrSikora Can we merge this for 1.4 and iterate later? The API surface remains the same (the method is called setFilterState), and this allows us to update metadata if we need it for one reason or another by making the ABI more generic. We can always change the name of the symbol passed via ABI from filter_state to anything else.

@PiotrSikora Specialized setters are used for C++ API usability purpose. You are right, they are just thin wrappers and optional.

This is stale. Can be re-implemented if necessary.


False positive for mac.com

False positive<EMAIL_ADDRESS>suggests<EMAIL_ADDRESS>
How popular is the TLDs or Domain: mac.com email addresses were issued to millions of people. Apple has moved away from them, but they still work.
Why most of the companies using this package will get benefit of it: False positives for a large number of email addresses cause additional customer support costs.

Current Behavior
const suggestion = emailSpellChecker.run({ email<EMAIL_ADDRESS>})
suggestion.full ==<EMAIL_ADDRESS>
Expected Behavior
const suggestion = emailSpellChecker.run({ email<EMAIL_ADDRESS>})
suggestion == null

Steps to Reproduce the Problem

See above

Thank you for this package, btw. It's really helpful! I'll try to submit a pr for this when I have a second.


Your GPU Specs?

Hi,
Any idea if you could give us what your GPU specs are? The Objection detection examples for video and webcam are running at real low Frame rate and quite a few here don't know where the bottleneck is.

Hello, here's the GPU I'm using for training:
https://www.amazon.com/GeForce-Dual-fan-Gaming-Graphics-DUAL-GTX1060-O6G/dp/B01JHQT1SE/ref=sr_1_1?ie=UTF8&qid=1531542627


[Enhancement] Karpenter add-on should allow the creation of a provisioner without requiring all of the fields

Per Karpenter docs, all of the ProvisionerSpecs field are not mandatory/required
The Karpenter add-on should allow the creation of minimal provisioner possible (or default to creation of one)

An example use-case, I have a cluster that I wish to run on spot instances, I don't care about which instance types are used or in what zone, and the default architecture of amd64 is acceptable. Currently I have to create my own Karpenter Provisioner with the requirements set as such:
  requirements:
  - key: karpenter.sh/capacity-type
    operator: In
    values:
    - spot
    - on-demand

@tsahiduek and @aceat64 - this is in progress. It will be a part of PR that will address #317.

@tsahiduek @aceat64 The PR is merged, expect this to show up as part of v1.0 release.


[WIP] Remove global config

This is WIP! No need to review yet.
What is the problem that this fixes or functionality that this introduces? Does it fix any open issues?
This PR is going to try to remove the global variable for "config" and replace it with a function that can load the global variable and more explicit passing of config between different objects.
Give a brief summary of what the PR does, explaining any non-trivial design decisions

I replaced the singleton config objects with pydantic classes.
Agents are now passed an LLM and AgentConfig, instead of getting their configuration implicitly from the global variable.

Other references
Fixes #2758
I am going to try to fix #2759 first to make this easier to implement.

Closing in favor of other more granular PRs.


Warn when building on master channel

See https://github.com/flutter/flutter/issues/24984

The message here doesn't seem very actionable.
I would recommend using a dragon emoji, followed by a message saying something like This is the $channel channel. Shipping apps from this channel is not recommended as it has not been as heavily tested as the stable channel. To build using the stable channel, consider using "flutter channel stable".

Does this only apply when building binaries for release?  Do we really want to discourage folks from using master?  I feel like that just encourages us to make it less stable (with cascading consequences)? :/

Should be just for shipping release apps, @eseidelGoogle, not for regular flutter run operations.

I agree with Eric that we should not take this to mean that we should allow master to be anything short of as good as stable at all times.

Test?


mat-form-field: ":label-shown" pseudoclass

What are you trying to do?
Hi all!
tl;dr;
Is :label-shown preudo-class  used in form-field component necessary / valid?
(e.g. https://github.com/angular/components/blob/master/src/material/form-field/_form-field-fill-theme.scss#L100)
Problem background
I'm trying to use polyfill for paged media (https://www.pagedmedia.org/paged-js/) in combination with "@angular/material": "12.2.4" and it complains about :
Uncaught DOMException: Failed to execute 'querySelectorAll' on 'Document': '.mat-form-field-can-float .mat-input-server[label]:not(:label-shown)+.mat-form-field-label-wrapper .mat-form-field-label' is not a valid selector.     at <anonymous>:1:10
Breaking it down, the only breaking part in selector is pseudo-selector ":label-shown" about which existence I've never heard of anywhere else.
What troubleshooting steps have you tried?
I've tried to filter out css styles used in my application, problem emerges when mat.core  mixin is in place.
Reproduction
Steps to reproduce:

check  https://stackblitz.com/edit/angular-ivy-24s2x2?file=src/app/app.component.scss
comment / uncomment mat.core in app.component.scss

Environment

Angular: 12.1.2
CDK/Material: 12.2.4
Browser(s): Google Chrome Version 96.0.4664.110 (Official Build) (64-bit)
Operating System (e.g. Windows, macOS, Ubuntu): Windows 10 Pro

I haven't heard about :label-shown either, but my guess is that it was used to increase the specificity of the selector. The :not() never really matches anything, but it still increases the specificity.

Okay, I think I figured out what happened. We used to have :placeholder-shown in there which is an actual pseudo selector. When we changed the label/placeholder terminology in #8223, it was renamed and we didn't notice it until now.

@crisbeto thank you for a quick reply!
If it may help, I've just opened a PR to fix pseudo class (I did not go through complete  #8223 diff)

Did this land in any version? or is there a workaround?
Having the same problem with Angular 13.3.0

Don't think it's fixed, did anyone manage to workaround this?

honestly, I gave it up here as I had to use completely different approach to achieve my PDF export goals anyway and I had no time to deep dive into material do's and don't

@crisbeto can you draft a way forward?
If it is a breaking change we can wait for another major version , but keeping it not compliant seems illogical.

I was under the impression that #24183 would fix it. @martin-havala why did you end up closing the PR? I can also make the same change and try to get it through.


Unable to read code coverage report

Here is an example of failure https://storage.googleapis.com/istio-prow/pull/istio_pilot/1266/pilot-coverage/153/build-log.txt

Coverage test needs access to a cluster.

Really ?

I guess we need to revert https://github.com/istio/pilot/commit/3284c3482331469ea59817a995477d40656dd21e

I see that I approved it sorry. That's my mistake, let me revert it.


test(examples): add example repo for monorepo app

Test plan

Green CI
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information
N.A.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.05%) to 95.779%

Totals

Change from base Build<PHONE_NUMBER>:
-0.05%

Covered Lines:
4055

Relevant Lines:
4154

💛  - Coveralls


#44 💡System: Level Up

🖋Description

🤖added levelUp formula

🧩Types of Changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

🧩Checklist

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

SonarCloud has 1 incident with CodeAnalysis
https://sonarcloud.statuspage.io


POC: Make flyout font sizes customizable with a single css variable

Fixes #95
This is missing proper documentation, but basically, by setting --readthedocs-flyout-font-size CSS variable on the flyout, you can control all of the font-sizes at once. For finer control, it's possible to instead override more specific CSS variables.

This is missing proper documentation, but basically, by setting --readthedocs-flyout-font-size CSS variable on the flyout, you can control all of the font-sizes at once

I think we can merge this PR and handle the documentation part in a separate issue/PR 👍🏼

@humitos ok if we'll deal with docs in a separate PR then this is good to go 👍


[DROOLS-7271] Fully port RuleParserTest as MiscDRLParserTest with @Di…

…sabled and priority comment
https://issues.redhat.com/browse/DROOLS-7271
Currently, I'm porting RuleParserTest (https://github.com/tkobayas/drools/blob/main/drools-test-coverage/test-compiler-integration/src/test/java/org/drools/mvel/compiler/lang/RuleParserTest.java) test methods to MiscDRLParserTest fixing issues one by one. However, with this JIRA, I port all RuleParserTest test methods to MiscDRLParserTest and set @Disabled on failing tests. Also add comments on the @Disabled to describe the priority (and some notes) so that we can grab the overview and work on fixes of higher priority issues later on. It would also help contributors to fix unresolved issues in the test class.
So this PR is just to port test methods. Not including a fix.
Note that these test methods are just ported (with assertj conversion), but if you have any suggestions to improve the tests, it would be welcome and I will handle it with another JIRA.

@mariofusco  , Could you merge this PR as @pibizza and @hellowdan seem to be busy?
@pibizza , @hellowdan Feel free to comment retrospectively. I would deal with it in another JIRA/PR.


drgeo: drop

Description of changes
Never updated in nixpkgs since 2013, which means it's missing all updates from 13.10 to 23.06.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Is this the same?
https://launchpad.net/drgeo/trunk/23.06


allow to use SSL and fix console scripts invocation

to allow to use SSL on pymongo >= 3, closes #10.
Also fix main functions to allow invocation w/o options param delaying the get_cli_options call

+1


Phantom crashes

I get this crash on each run after couple of minutes:
https://gist.github.com/gkorland/5715256

Please upgrade to PhantomJS 2.0. 1.9.x is no longer supported, and known to have many crasher bugs that are fixed in 2.0.


Remove extra apostrophe

We mean "lets" as in "allows" here, not "let's" as in "let us"

Certainly this can be merged, @evancz?


Can Cursor Lock and NWNLogRotator coexist together in harmony?

Got an issue I'm trying to get CursoLock to work with NWNLogRotator which I like for taking Logs of Neverwinter Nights 1. Both of these programs are set up to use NWNmain.exe. I can get each working separately but they won't work together. I tried Cursor Lock in both fullscreen mode and Windows interior mode. Do you have any idea if this would even be possible to do?  Here Is a video of the NWNLogRotator
https://youtu.be/Myivw84ONJQ
https://neverwintervault.org/project/nwn1/other/tool/nwnlogrotator

Unfortunately, there doesn't seem to be a way currently.
A solution is possible albeit a bit hacky. Would involve saving the logs regardless of the launch feature optionally. When I get time to look more into it I'll try it out.

Thanks, for even looking into it.

After looking into it, apparently it's already possible.
Make sure you have everything configured. Then start the game, in the app, bottom right it will go from nwmain is inactive-->active-->inactive.
On the state change of active->inactive, it should generate a log.
If it does not, try to configure more of the options even if you're not using all of them. Please let me know if this doesn't help.

Ok, I guess I wasn't too clear on what the problem was. Yes, I can get a log to work in NWNlogrotator, as I stated it creates logs and I got that working so that is not the main issue and maybe this isn't the best place to find the solution to the problem.
The issue is Cursor Lock won't lock the Screen when NWNLog is being used. Cursor lock needs to access NWmain.exe as well to lock the screen and so does NWNLog Rotator. The Cursor lock will allow you to lock the mouse in the window or prevent the mouse from leaving it and going into a secondary monitor on your desktop while you're playing a video game.
I tried creating log rotator which is placed in my C: drive pointed at NWmain.exe in another folder on that drive and then using that link it created and trying to have cursor lock open it in its "program options" field, then under "standard options" check-marked the "lock Region/ Window Interior and Force Lock options which locks the mouse in windowed mode so you can't accidentally close the window while playing the game. I also have HotKeys set up for the keyboard key L  so I can "toggle" in and out of the locked window which allows my mouse to get back to my desktop. When I point the Cursor lock to the NWNLogRotator version of NWmain.exe on my C: drive, LogRotator can't find NWmain.exe at the bottom of its screen and so it won't log anything but the window will lock the mouse correctly. When clicking on the log rotator executable on the C: drive without cursor lock involved it will work and log the chats as expected.
I did try launching Cursor Lock/ Nwmain.exe shortcut that CursorLock makes from the NWNlogRotator Launcher Client button but all it does is open the CursorLock setup program and not Cursorlock/ NWmain.exe combo link to start the game and NWN Log Rotator will not see Nwmain.exe and make it active doing it this way.
I did have some codes popping up along the way that I had to raise inheritance in Windows and I gave the links and Executables admin  and full control access to no avail.
Well, sorry for the delayed response and lack of clarity, hope this makes more sense.

Don't launch the game with NWNLogRotator. Please try this

Ok, Thanks for your heLp, I think it shouLd probaby work now, but you shouLd have inLcuded information about the options "Start Cient automaticay when auncher opens", which I had checked. I asLo turned off the "CLose Launcher automaticaLLy when cLient cLoses that I had checked right of the bat. I didn't reaLize the rammifications of what this wouLd do when I Later started to try to incorporated both programs at the same time.
It wouLd aLso be a nice touch to have a heLp fiLe on the functions of each and how they couLd be used. Is there one? If there is I must of missed it.
What is SiLent mode? Why wouLd you want to save a Log on Launch?, FiLter Lines?
Now ALL I have to do is figure out why my Lower case L is not working on my keyboard LOL.

Q:What is SiLent mode?
Silent mode doesn't pop up when logs generate.
Q: Why wouLd you want to save a Log on Launch?
A: https://github.com/noblesigma/NWNLogRotator/issues/13
Q:  FiLter Lines?
In case some spam occurs on a server you play on that you want to omit you can add it here.
Q: Could it be possible to generate a log without exiting out of the game?
A: Yes, but only through "Run Once"


SPDistributedCacheService - Resource takes to long and does not complete correctly

Using the SPDistributedCacheService instance to provision a Distributed Cache on a server takes way to long and does not complete correctly. The service instance is stuck in the unprovisioning state after the resource is run.
After a quick look into the resource I came across this command:
https://github.com/PowerShell/SharePointDsc/blob/4e9e1216da0412ac206889729e8f791bb51b79f5/Modules/SharePointDsc/DSCResources/MSFT_SPDistributedCacheService/MSFT_SPDistributedCacheService.psm1#L249-L251
I tried to change it to Stop-SPDistributedCacheServiceInstance and the service instance gets stopped immediately.
Is there any reason to use Stop-SPServiceInstance instead of  Stop-SPDistributedCacheServiceInstance?
Update:
I did a quick check of the PowerShell Methods used to stop the service.
Stop-SPDistributedCacheServiceInstance cmdlet uses the internal method: Microsoft.SharePoint.DistributedCaching.Utilities.SPDistributedCacheServiceInstance.UnProvisionInternal() to stop the service.
Stop-SPServiceInstance cmdlet calls the public method Microsoft.SharePoint.DistributedCaching.Utilities.SPDistributedCacheServiceInstance.Unprovision() wich will also call the internal one.
I do not see, why there is a difference in the execution.

I know Stop-SPDistributedCacheServiceInstance has an issue where a graceful shutdown wasn't performed gracefully. The stop command is send to DC and then the DC process is terminated before it was able to complete gracefully. That is why the official gracefull shutdown procedure has been changed:
https://docs.microsoft.com/en-us/sharepoint/administration/manage-the-distributed-cache-service#graceful
This is probably why you see the difference in behavior.


Adding Global Climate Tech Landscape resource

Miscellaneous > Knowledge Bases and Data Sources

Hey @elaristi,
it is so nice to hear from you. Unfortunately, the project you propose is not open source. It is called so in the description, but after a long search I can't find any document that is really under an open-source license. Do you know where II can find the Climate Tech Landscape? It would be actuuly very good to have such a list about climate tech in an open source way. Maybe we should join the news letter and do the mapping by our self ;)
Kind regards
Tobias

I will close this pull request, because of the missing OS license.


chore(deps): update renovate/renovate docker tag to v36.27.1

This PR contains the following updates:

Package
Update
Change

renovate/renovate
minor
36.18.2 -> 36.27.1

Release Notes

renovatebot/renovate (renovate/renovate)
v36.27.1
Compare Source
Build System

deps: update dependency tslib to v2.6.1 (#23636) (f202802)

v36.26.1
Compare Source
Documentation

platform/Gitea: Update PAT scopes for Gitea (#23615) (b02d4ac)

Build System

deps: update opentelemetry-js monorepo (#23632) (ec4ed8f)

v36.26.0
Compare Source
Features

preset: add scaffdog monorepo (#23616) (9aefc20)

Documentation

configuration options: commitMessagePrefix always appends : character (#23611) (6001f97)
update references to renovate/renovate to v36.25.5 (#23622) (928184e)

Code Refactoring

cdnjs: Use zod schema and Result class (#23588) (bbf4183)
jenkins-plugins: Remove huge fixtures (#23621) (7209262)

Tests

Write test for bad pattern: .md/# (#23609) (8aad74f)

v36.25.5
Compare Source
Bug Fixes

lerna: skip bootstrap if using a v7 range (#23595) (2be0ff3)

v36.25.4
Compare Source
Bug Fixes

deps: update ghcr.io/containerbase/sidecar docker tag to v9.8.2 (#23605) (dd31f88)

Miscellaneous Chores

deps: update dependency @types/node to v18.16.20 (#23602) (8b8346e)
deps: update dependency @types/node to v18.17.1 (#23603) (974c94e)

v36.25.3
Compare Source
Bug Fixes

deps: update ghcr.io/containerbase/sidecar docker tag to v9.8.1 (#23601) (680f743)

v36.25.2
Compare Source
Miscellaneous Chores

deps: update github/codeql-action action to v2.21.2 (#23596) (397f3aa)

Build System

deps: update dependency @cdktf/hcl2json to v0.17.2 (#23597) (58ab058)
deps: update dependency @cdktf/hcl2json to v0.17.3 (#23598) (17858a9)

v36.25.0
Compare Source
Features

Support Zod values in Result transforms (#23583) (674c6fc)

v36.24.2
Compare Source
Bug Fixes

lerna: detect lerna in dependencies (#23575) (48d3eba)

v36.24.0
Compare Source
Features

manager/asdf: add typos (#23566) (450350e)

Code Refactoring

use minimatch util (#23549) (2159444)

v36.23.2
Compare Source
Bug Fixes

versioning/hashicorp: allow != in ranges, constraints (#23492) (ce1be2c)

Tests

dep: replace mockdate package with jest.fakeTimers (#23542) (d255f81)

v36.23.1
Compare Source
Bug Fixes

rubygems: Use cascade of endpoints for unknown servers (#23523) (992b336)

Documentation

config: add clarification for gitAuthor format to avoid obscure errors during commits. (#23543) (89621be)
managers: use table for categories display (#23503) (949681f)

Code Refactoring

util/hash: replace hasha sha512 use cases (#23548) (39c9072)

v36.23.0
Compare Source
Features

add minimatch wrapper to support caching (#23515) (e24ca0e)

Code Refactoring

rubygems: Use Result class (#23522) (6451c3a)
util/hash: replace sha256 hasha use cases (#23547) (b9c8c44)

v36.21.1
Compare Source
Bug Fixes

Merge additionalReviewers from multiple upgrades (#23540) (f4dbae2)

Code Refactoring

release-notes: extract shouldSkipChangelogMd (#23274) (3c29bd4)

v36.21.0
Compare Source
Features

add hash util (#23524) (1b93263)

Documentation

update references to renovate/renovate to v36.20.1 (#23525) (68e871e)

Code Refactoring

rubygems: Extract v1 API handling (#23474) (0e2083e)
rubygems: Unify fetching via v1 API (#23517) (3559cb3)

Tests

rubygems: Simplify tests (#23521) (285bed3)

v36.20.1
Compare Source
Bug Fixes

github: Remote branch existence check (#23480) (9e77d59)

v36.19.2
Compare Source
Bug Fixes

deps: update ghcr.io/containerbase/sidecar docker tag to v9.7.0 (#23514) (e5336a5)

v36.19.1
Compare Source
Bug Fixes

Disable false eslint warning (#23513) (9b1c903)

v36.18.4
Compare Source
Bug Fixes

datasource/conan: continue on error during fetching package url (#23391) (bca8175)

Tests

versioning/loose: add testcase for timestamp (#23507) (5e3d6a2)

v36.18.3
Compare Source
Bug Fixes

git-submodule: remove token injection from submodule URL (#23458) (807b796)

Code Refactoring

Use assignKeys when copying from dependency to lookup result (#23484) (f935242)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

:tada: This PR is included in version 5.2.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Mail::SendMail shellescape broken

https://github.com/mikel/mail/blob/master/lib/mail/network/delivery_methods/sendmail.rb#L85
So when invoking sendmail it takes the to address and escapes it and then puts it in double quotes. However, only $, `, ", and \ and newline are supported by the \ escape in bash in double quotes. So to addresses will be mangled and contain an extra \.
For example:
~$ echo<EMAIL_ADDRESS><EMAIL_ADDRESS>
From Bash manpage:
   Enclosing characters in double quotes preserves the literal value of all characters within the quotes, with the exception of $, `, \, and, when  history  expansion
   is  enabled,  !.  The characters $ and ` retain their special meaning within double quotes.  The backslash retains its special meaning only when followed by one of
   the following characters: $, `, ", \, or <newline>.  A double quote may be quoted within double quotes by preceding it  with  a  backslash.   If  enabled,  history
   expansion will be performed unless an !  appearing in double quotes is escaped using a backslash.  The backslash preceding the !  is not removed.

I'm not sure why we are using shellescape here and not execv style execution which would appear to be much safer.

#898


Don't try to buy day passes if the airport item of the month is owned

I just took a look at the script and it assumes that a day pass is required for all platinum deliveries. Wouldn't it be straight-forward to check whether the following are set to "false" before trying to buy a day pass?
coldAirportAlways
hotAirportAlways
sleazeAirportAlways
spookyAirportAlways
stenchAirportAlways

I actually was checking those values. But I made a mistake in the implementation.
I pushed a fix. please try it with svn update and let me know if it solved the issue

Your change to the logic did the trick.  The script, successfully performed a platinum and three gold deliveries.  Thank you.


When copying build output classfiles as a last resort when indexing w…

…ith vanilla javac fails, also run binary indexer over the copied classes, so that features like Go to Type have a chance to work.

There are conflicts that must be resolved.


Updates on the feature section

Pull request details
Describe the changes made in this pull request
Updates on the explanation of the feature section
List of related issues or pull requests
Closes #346
Collaboration confirmation
As a contributor I confirm

[x] I read and followed the instructions in README.dev.md
[ ] The documentation is up to date with the changes introduced in this Pull Request (or NA)
[x] Tests are passing
[x] Lint is passing

@gnawin please double-check that all we have commented before is included in this new version. There are extra changes that German commented on with me. Also, would you mind using the "add a suggestion" feature in your review to incorporate your suggestions into the documentation easily?


Fails to work on macOS

Your tool works flawlessly on my linux box, however I wanted to make use of it on my MacBook, but I run into a problem.
You call stat here, and that causes a problem on macOS, since the CLI is different here.
I'm not sure if this is the only issue preventing it from working. Is there maybe a way to get the operating system from the executor to try and prevent this issue?
Thanks for making this, btw

Hi Paul and thanks for the feedback! I just released version 4.3 which implements/restores Mac OS X compatibility. I've also configured Travis CI to run the test suite on Mac OS X to ensure that I don't inadvertently break compatibility later on.


delete custom media type 'application/vnd.github.polaris-preview'

Fixes issue: #616

Friendly ping @ahmedhagii. Did you see my review question above?

Friendly ping @ahmedhagii.
If you prefer not to continue working on this, we can take this PR (which is 90% there), apply the suggested change above, and merge it. That's completely okay.

I'm going to apply the suggested simplifications myself.

The simplifications were no longer applicable due to the changes that have since happened. I've rebased, resolved the merge conflict, improved the commit message, and updated the PR.


Chunk Size and Certificate Size Misuse in GetCertificateChain Command

This finding does not have an impact because the values of the misused constants are
coincidentally the same. This finding is raised for informational purposes.

Fixed by https://github.com/chipsalliance/caliptra-dpe/pull/169

Further fix in https://github.com/chipsalliance/caliptra-dpe/pull/231


yarn add @stripe/stripe-react-native giving error getConstants of null

Describe the bug
When we initialized Stripe to out react native project by following this documentation I got an error saying  TypeError: Cannot read property 'getConstants' of null, js engine: hermes
To Reproduce
Steps to reproduce the behavior:
yarn add @stripe/stripe-react-native
cd ios/
pod install
Expected behavior
Yarn start -c should run the eas development build and I should be apple to run my react native app on the simulator
Desktop (please complete the following information):

OS: IOS 16.4

SS

My package.json
{
  "name": "fitfinder-app",
  "version": "1.0.0",
  "scripts": {
    "start": "expo start --dev-client",
    "android": "expo run:android",
    "ios": "expo run:ios",
    "web": "expo start --web",
    "pod-install": "cd ios && pod install && cd .. && expo start --dev-client",
    "ios-simulator-build": "eas build --profile development-simulator --platform ios",
    "ios-device-build": "eas build --profile development --platform ios",
    "run-build": "eas build:run -p ios --latest",
    "run-lint": "eslint ."
  },
  "dependencies": {
    "@expo/ngrok": "^4.1.3",
    "@gorhom/bottom-sheet": "^4.4.7",
    "@react-native-async-storage/async-storage": "1.17.11",
    "@react-native-community/datetimepicker": "6.7.3",
    "@react-native-community/netinfo": "9.3.7",
    "@react-native-google-signin/google-signin": "^10.0.1",
    "@react-native-seoul/masonry-list": "^1.4.2",
    "@react-navigation/native": "^6.1.7",
    "@react-navigation/native-stack": "^6.9.13",
    "@shopify/flash-list": "1.4.0",
    "@stripe/stripe-react-native": "0.38.1",
    "@supabase/supabase-js": "^2.33.1",
    "@types/react": "~18.0.27",
    "axios": "^1.4.0",
    "base64-arraybuffer": "^1.0.2",
    "expo": "~48.0.21",
    "expo-apple-authentication": "~6.0.1",
    "expo-blur": "~12.2.2",
    "expo-calendar": "~11.1.1",
    "expo-checkbox": "~2.3.1",
    "expo-constants": "~14.2.1",
    "expo-dev-client": "~2.2.1",
    "expo-device": "~5.2.1",
    "expo-image": "~1.0.2",
    "expo-image-picker": "~14.1.1",
    "expo-linear-gradient": "~12.1.2",
    "expo-linking": "~4.0.1",
    "expo-localization": "~14.1.1",
    "expo-location": "~15.1.1",
    "expo-mail-composer": "~12.1.1",
    "expo-notifications": "~0.18.1",
    "expo-splash-screen": "~0.18.2",
    "expo-status-bar": "~1.4.4",
    "expo-tracking-transparency": "~3.0.3",
    "geolib": "^3.3.4",
    "lodash": "^4.17.21",
    "moment-timezone": "^0.5.43",
    "nativewind": "^2.0.11",
    "react": "18.2.0",
    "react-native": "0.71.14",
    "react-native-blurhash": "^1.1.11",
    "react-native-calendars": "^1.1299.0",
    "react-native-element-dropdown": "^2.10.0",
    "react-native-fbsdk-next": "^12.1.0",
    "react-native-flash-message": "^0.4.2",
    "react-native-gesture-handler": "~2.9.0",
    "react-native-gifted-chat": "^2.4.0",
    "react-native-google-places-autocomplete": "^2.5.6",
    "react-native-localize": "^3.1.0",
    "react-native-maps": "1.3.2",
    "react-native-mmkv": "^2.10.2",
    "react-native-otp-textinput": "^1.1.0",
    "react-native-phone-number-input": "^2.1.0",
    "react-native-qrcode-svg": "^6.3.0",
    "react-native-reanimated": "~2.14.4",
    "react-native-safe-area-context": "4.5.0",
    "react-native-screens": "~3.20.0",
    "react-native-shared-element": "^0.8.8",
    "react-native-shimmer-placeholder": "^2.0.9",
    "react-native-svg": "14.1.0",
    "react-native-swiper": "^1.6.0",
    "react-native-ui-lib": "^7.5.2",
    "react-native-url-polyfill": "^2.0.0",
    "socket.io-client": "^4.7.2"
  },
  "devDependencies": {
    "@babel/core": "^7.20.0",
    "@react-native-community/eslint-config": "^3.2.0",
    "@types/lodash": "^4.14.200",
    "@types/react-native": "^0.72.2",
    "eslint": "^9.1.1",
    "react-native-dotenv": "^3.4.9",
    "react-native-svg-transformer": "^1.0.0",
    "tailwindcss": "^3.3.2",
    "ts-node": "^10.9.1",
    "typescript": "^4.9.4"
  },
  "private": true
}

### Tasks

npx react-native start --reset-cache solved the problem!

npx react-native start --reset-cache solved the problem


fix: Update API version to 1.0.2

About this PR

Closes https://github.com/lenra-io/app-lib-js/issues/70

Technical highlight/advice

How to test my changes

Checklist

[ ] I didn't over-scope my PR
[ ] My PR title matches the commit convention
[ ] I did not include breaking changes
[ ] I made my own code-review before requesting one

I included unit tests that cover my changes

[ ] 👍 yes
[ ] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help

I added/updated the documentation about my changes

[ ] 📜 README.md
[ ] 📕 docs/*.md
[ ] 📓 docs.lenra.io
[ ] 🙅 no documentation needed

@taorepoara I might need some help on this one.


Add 'ep' as a shortcut for 'endpoints'

Very minor UX point, could wait until after 1.0

cc @bgrant0607 @jlowdermilk as potential reviewers.
@bgrant0607 to triage for 1.0 as well.

LGTM

lgtm

Will merge during work hours


ParserError messages don't seem to be propogated

A grammar I'm developing seems to be throwing a ParserError, although I'm having a lot of trouble finding out exactly where the error is happening. To make matters more complicated, I seem to be unable to see the error messages that are coming out of the ParserError. It seems like the message parameter is not being propogated to the error object or accessible in the console.
Here's a simple test case.
> try { throw new Error('123') } catch (e) { console.error(e.toString()) }
Error: 123
undefined
> try { throw new ParserError('123') } catch (e) { console.error(e.toString()) }
Error

Seems like you're calling super(message), although that doesn't seem to be having an effect. But manually setting the message property in the constructor does seem to have an effect.

I get much better behavior on TypeScript 3.0+, so I think my dependency on this is out of date.

Actually, now that I look at it some more, I'm going to reopen this. It seems like there hasn't been a release since the Typescript dependency has been updated, so this issue is still open.


Is IRC channel listed in Readme still accurate?

In the Readme it states:
"Official IRC channel: #winapi on Mozilla IRC"
As far as I know Mozilla IRC has been shut down. Has the winapi channel moved elsewhere?

It also appears to be referenced in: https://github.com/retep998/winapi-rs/blob/0.3/.travis.yml#L37

It is not accurate currently.

README has been updated


Feature parity with the Gradle plugin, DSL #23

This is the first fully functional version of DSL for configuring Eta projects in build.sbt .
This version not contains:

[ ] Configuring Eta Can use only etlas installed in system.
[ ] Git Dependency Can specify eta and maven dependencies, but no git dependencies.

@Romastyi This looks great! My only concern is that by default, it looks like you're writing the cabal file for a package inside of the src/main/eta folder. Can you write it inside of the target directory instead? The .cabal file should not be visible to the user since it's generated.

It was made for compatibility reasons with older code base. Project layout is described in README. If it is not an issue, I can remove "old layout" support.
Anyway I'll move generated .cabal into traget/eta folder.

@Romastyi You can go ahead and make it a breaking change.

@rahulmutt Done. Now the .cabal file will be generated in target/eta folder.

Added support for specifying Eta compiler version. Gradle plugin

@Romastyi Great work so far! :) will you also be adding support for git dependencies before I merge? It amounts to generating a cabal.project along with the .cabal file. Let me know if you need more info on what to generate.

Added support for Git dependencies. Checked in example project.

Examing the functionality of gradle-eta plugin I noticed that it writes cabal.project.freeze file too. Is it important in your opinion?

@Romastyi That cabal.project.freeze is a different aspect you may want to work on. I'll merge what you have for now and detail that in the feature parity issue.


Viewable AllSrv Version number ingame

Nobody in-game can view the version number (or which build number or build date) is running on servers (like TAG already does), only server administrators can by checking EXE.
This would help finding bugs faster, if you have different versions of AllSrv running on game servers (administrators ignore updates etc), prime example:
http://www.freeallegiance.org/forums/index.php?showtopic=52972
Imported from trac ticket #62,  created by pkk on 03-09-2010 at 17:54, last modified: 07-03-2010 at 20:19

esc menu to show server as well from lobbymissioninfo
Trac comment by Imago on 06-29-2010 at 22:45

r624
Trac comment by Imago on 07-03-2010 at 20:19


:sparkles: Ensure ___Options Classes Support all Options

Check RequestOptions and ClientOptions include all options. (I think there's some missing from ClientOptions)

Closed as Done


hdc: reformat files

@TriedAngle FYI

@jschwe  You're right, I'll change the title. I also would like a CI, but for now I cannot allocate time for this.


Minor ui changes

Text overlapping in buttons
translations
success screen in intro page edit
help button change url

Can you also fix this to be displayed cleaner, maybe with less padding ?

Can you also fix this to be displayed cleaner, maybe with less padding ? @vmangelovv

I'll put this in another issue, to not block the merging of the other fixes.


Relaxing package pin on zest.releaser

Relaxing the pin on the releaser so packages don't conflict with the application using the client.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Coverage remained the same at 89.403% when pulling de6b1d2312d842d6f03fd093942a0911b1b61c85 on dev/harrisr/open_zest_pin into d4e9576a9d5c36e36804205a8687b3dd7a67b0e0 on master.


feat(NumberTheory/LSeries/Dirichlet): new file, material on specific L-series

This PR adds a new file NumberTheory.LSeries.Dirichlet that contains results on L-series of specific functions:

the Möbius function
Dirichlet characters, with the constant function 1 as a special case
the arithmetic function ζ (which has the same L-series as the constant function 1)
the von Mangoldt function and its twists by Dirichlet characters

It also adds (L-series of zero and of the indicator function of {1}) and removes (convergence of the L-series of the constant function 1 / of  ζ; this is moved to the new file) some material to/from NumberTheory.LSeries.Basic.
See this thread on Zulip.

LGTM!

It might be a good idea to apply Ruben's suggestion, changing (h : ∀ {n} (_ : n ≠ 0), f n = g n) to (h : ∀ {n} (_ : n ≠ 0), f n = g n), not just to term_congr but to the other 7 lemmas which use this formulation.

Looks great!
maintainer merge

Thanks!
bors merge


linter incorrectly correct mix of tab and spaces.

If a tab is used it always replaces it with 4 spaces (or whatever the user specified.) so if I have _tab where _ is a space and tab is a tab, correct correct that to _____ (5 spaces) where it should be corrected to ____ (4 spaces).

@kbjarkefur I corrected the function so it now replaces up to two whitespaces + the tab at the beginning of the line with 4 spaces
This is the regex that is replaced:


Configure minio deployment including in openshift AI by default

Currently minio is (mostly) deploying.
Automate the configuration of Minio including a default set of access credentials (configured from the validated patterns secrets file).
DoD

have demonstrated the ability to deploy content into a minio tenant.

@butler54 - where do you want the code for the deployment managed?


Create Postgres Account - Default Setup

Postgres API allows 4 different kinds of account creation --> Default, Restore, GeoRestore and Replica. Should we just support default for now?
For the Default create mode, there are few optional properties --> version, storage profile, sku, tags. How do we want to handle them?

Should we store the username and password as the user inputs these to create an account? Or we only use these inputs to create an account and then late on they have to re-enter these details to access the databases?

Should we store the username and password as the user inputs these to create an account? Or we only use these inputs to create an account and then late on they have to re-enter these details to access the databases?

I think it would make sense to cache the username and password when the account is created so they don't have to be entered multiple times. We should be able to reuse this function with some tweaks. It may need to be moved to PostgresServerTreeItem since we won't have access to databases before creating the server


Push notifications API implementation

Description

model for DeviceTokens
which stores the FCM token for patrons mobile devices
It ensure uniqueness on the token string

API to GET and PUT device tokens for patrons

GET
responds with 200 and token details
404 if token is not found

PUT
responds with 201 if created
400 if the token type is invalid
409 if the token was not unique

There is no DELETE method yet
No use case is outlined for it

Motivation and Context
The Palace Manager needs to support the following push notifications in the iOS and Android apps
This is the first step, allowing the apps to store the FCM tokens for the mobile devices

How Has This Been Tested?
Unit tests were written and manual testing was done via Postman

Checklist

[ ] I have updated the documentation accordingly.
[x] All new and existing tests passed.

I like the use of generics. Most people don't think of them!


About window attention

Hi, I noticed that you used the pre-trained parameter to initialize vit, then changed the attention module of 8 vit blocks to window attention, and then finetune it on the downstream task. I would like to ask whether this way of replacing the attention module will lead to the pre-trained knowledge not well transferred to the downstream task?

Hello, you can still load all the pre-trained weights after replacing global attention with window attention, because the parameters in the attention module are mainly linear layers.


Small PlannerParams fixes

Newer versions of OpenRAVE added an int options argument to the Planner::PlannerParameters::serialize() member function, which caused the attempted overrides in OMPLPlannerParameters and OMPLHolonomicPlannerParameters (which did not have the correct function signature) to not be called on copy.  This was causing bugs in parameter loading from pr-constraint.  This PR includes a configure-time check to see which to use.
This PR also renames the processing flag to be clearly specific to the derived class, to not confuse it with the similar flag in the base class.

Good catch! We got burned by this in CBiRRT before. :frowning:
I'm a bit concerned about using a flag set by add_definitions in a header file. The flag won't be set for packages that depend on or_ompl (e.g. those in pr-constraint), since it is passed as a compile-time flag. If this is necessary, then we should generate a header file that contains the flag using generate_export_header and #include it in the OMPLPlannerParameters.h.
However, it would be simpler to unconditionally define both functions. Is there any harm in defining the int overload if the user is building against an older version of OpenRAVE?

I chatted with @mkoval about the transient definition issue (good catch Mike!), and the problem with simply implementing both signatures is that it can't be determined which version of the base class method to call.  So the revised PR generates a config.h file in order to preserve the result of the test for dependent packages.  (This also simplifies those packages, which can simply include this file instead of duplicating the test, e.g. personalrobotics/pr-constraint@62c53ede77aaba93f22136e22951193dfd7380f3).
While mucking with include paths to get this to work, I noticed that the headers in or_ompl were referenced locally (#include "blah.h") instead of fully-qualified (#include <or_ompl/blah.h>).  I believe the latter convention is more widespread, easier to handle in dependent packages, and is also more consistent with auto-generated headers, so I switched to it.

:+1: Thanks for making the fix. Can you update pr-constraint to use this macro, too?
Good catch on the header include paths, too.

Yes, pr-constraint already does!


Skip already evaluated connection properties.

This is a bugfix PR for Issue https://github.com/dask/hdfs3/issues/132

Thanks!


add cityhash64 function

can you add cityhash64 for
https://github.com/ClickHouse/clickhouse-java/blob/bbd6808748c382a88bf0a2a212c73c9cb29237e3/clickhouse-data/src/main/java/com/clickhouse/data/ClickHouseCityHash.java#L45

Good day, @jiqimaogou !
Would you please explain the purpose of cityHash64?
Thanks!


expose HeaderGlobalAction's underlying button props

It would be good if HeaderGlobalAction exposed disabled and iconDescription so I can make some cosmetic modifications like I can with Button.
Also the same for HeaderAction.

Is there a workaround?


Render a PNG raster with outlined multipolygon and three dots

A small experiment, raw PSQL only, no Ruby.

Use a geographic area
Select three points (or create three fake points) and draw them on the raster
Make the points different color
Export the PNG

Not a priority, and not likely a future priority, closing.


Compiler errors not displayed when there is a compilation issue

I was debugging what the cause behind this issue was:
$ ape compile
INFO: Compiling 'contracts/ApePiece.vy'.
ERROR: (VyperInstallError) Unable to install Vyper version: 0.3.1.

It turned out to be a legitimate bug! However, due to how this code works, it's not displaying the bug properly, just showing something about the it not being able to install the version of Vyper it's currently using:
https://github.com/ApeWorX/ape-vyper/blob/c6f9e50b4ecfe6c1f7e8eb78501391a53b688dee/ape_vyper/compiler.py#L128-L133
Was thinking why it was necessary to catch this exception? Is it just so err inherits from CompilerError? Can this be done another way so it any compiler errors look transparent to the user?
This is the actual error that should be displayed (which I access when I debugged):
$ ape compile
INFO: Compiling 'contracts/ApePiece.vy'.
> .../site-packages/ape_vyper/compiler.py(140)compile()
-> new_err = VyperInstallError(vyper_version)
(Pdb) print(err.stderr_data)
vyper.exceptions.StateAccessViolation: not allowed to query contract or environment variables in pure functions
  contract "/tmp/vyper-6dd2eazp.vy", function "_tokenIdToString", line 132:8
       131     return concat(
  ---> 132         self._digitToString(digit1),
  -----------------^
       133         self._digitToString(digit2),

[20400] Failed to execute script 'vyper_compile' due to unhandled exception!

Related: would be nice to use vvm.compile_files so we get the actual source filename in there.

A little better:
class VyperCompileError(CompilerError):
    def __init__(self, err):
        if hasattr(err, "stderr_data"):
            message = err.stderr_data
        else:
            message = str(err)

        self.message = message
        super().__init__(message)

...
class VyperCompiler(CompilerAPI):
    ...
    def compile(self, contract_filepaths: List[Path]) -> List[ContractType]:
        ...
            try:
                result = vvm.compile_source(
                    source,
                    vyper_version=vyper_version,
                )["<stdin>"]
            except Exception as err:
                raise VyperCompileError(err) from err

Was thinking why it was necessary to catch this exception? Is it just so err inherits from CompilerError?

Yeah, it was raising Abort() before and then we upgraded. Raising a custom error like CompilerError is like the same thing as raise Abort() -- to get displayed to the user is a nice way. That is the only change I made on this so far. Upgrades!
The install-error does not seem related to the compile errors though, or is it?  I am little confused there.
Yeah, I agree that exceptions in general can be improved for this plugin.

I just tried to compile some garbage, it seems to work better now:
ERROR: (VyperCompileError) vyper.exceptions.StructureException: Unsupported syntax for module namespace: Expr
  contract "/var/folders/hg/17b1zhsn1n3d8b4rgh6ntt_w0000gn/T/vyper-ajp3wgog.vy", line 1:0
  ---> 1 asdfasdfasdf
  -------^
       2

[15687] Failed to execute script vyper_compile

Edit, oh I see we are raising a Intall Error when we are supposed to be raising a Compile Error.

Yes lol


filter by user or organization

Filter what by username?
Filter users by org would be very useful.