Use boolean for auth parameter in pilot e2e tests.

We're currently using an enumeration for auth: enable, disable, both.
This complicates the tests and also makes the test process run much
longer.
Switching to a boolean removes a bunch of extra test code and makes the
command line more similar to the mixer tests.

@nmittler: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
50dfc4ca711241219eb56e71eec54f67787a3627
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@nmittler: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
50dfc4ca711241219eb56e71eec54f67787a3627
link
/test istio-unit-tests

prow/istio-presubmit.sh
50dfc4ca711241219eb56e71eec54f67787a3627
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@nmittler: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
50dfc4ca711241219eb56e71eec54f67787a3627
link
/test istio-presubmit

prow/istio-unit-tests.sh
68ea51696fcfa192356e822e97e3ee552285440b
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@nmittler: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
68ea51696fcfa192356e822e97e3ee552285440b
link
/test istio-unit-tests

prow/istio-presubmit.sh
68ea51696fcfa192356e822e97e3ee552285440b
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@nmittler: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
68ea51696fcfa192356e822e97e3ee552285440b
link
/test istio-presubmit

prow/istio-unit-tests.sh
88e8d292b0704342dde18e3b93895d1425918e40
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@nmittler: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
88e8d292b0704342dde18e3b93895d1425918e40
link
/test istio-unit-tests

prow/istio-presubmit.sh
88e8d292b0704342dde18e3b93895d1425918e40
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@nmittler: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
e7ba56fde11f921912d14875241f7621e75f0bc5
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

cool; so to do "both" now you have to run it twice, once with true and once with false?
(or maybe both is the "unset/unspecified" default?)

@ldemailly

cool; so to do "both" now you have to run it twice, once with true and once with false?

Yeah that's right ... it's now the same way you would configure other tests (e.g. mixer).

Sounds good. As we discussed, we would like to have all tests run against a
pre-configured
'environment', shared with other suites.
The intended flow for (most) developers and the CI/CD:

setup environment
run all integration test suites (with skip setup), possibly in parallel
repeat running some tests (for example to de-flake or debug)
possibly update the environment with new build, and repeat testing
if needed, cleanup the environment ( in circle it's not needed since VM
goes away )

The 'setup' can be a pre-installed istio, an existing cluster running
istio, etc.
It's critical the tests do not modify the istio environment while running.
(except dedicated tests for upgrade, cleanup - but those should be in
separate suites).
So I would also remove the mixer option - and just call the setup code from
the e2e framework,
with the 2 (istio.yaml and istio-auth.yaml) environments.
On Tue, Mar 6, 2018 at 7:10 AM, Nathan Mittler<EMAIL_ADDRESS>wrote:

@ldemailly https://github.com/ldemailly
cool; so to do "both" now you have to run it twice, once with true and
once with false?
Yeah that's right ... it's now the same way you would configure other
tests (e.g. mixer).
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/3978#issuecomment-370812623, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAFI6iAlz5OVekBl4AkAl2dpoMWi0NDRks5tbqb6gaJpZM4Sdx5Q
.

@nmittler: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests.sh
111069fd21cce875c4e8fd96c30743081f1787eb
link
/test e2e-bookInfo

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@nmittler: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests.sh
111069fd21cce875c4e8fd96c30743081f1787eb
link
/test e2e-bookInfo

prow/istio-pilot-e2e.sh
111069fd21cce875c4e8fd96c30743081f1787eb
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@costinm all of that will be the next PR ... this is just a minor cleanup in that direction.

@kyessenov are you ok with losing "both" mode ?
(which we could keep as the default when the new flag is set)

@ldemailly one way or another, we're going to lose "both" since we're migrating the pilot tests over to the common e2e framework: #4012.  If you'd prefer, we can abandon this and wait for that fix?

i guess ‘both’ can be implemented easily with a script so
/lgtm

@nmittler: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests.sh
111069fd21cce875c4e8fd96c30743081f1787eb
link
/test e2e-bookInfo

prow/istio-pilot-e2e.sh
111069fd21cce875c4e8fd96c30743081f1787eb
link
/test istio-pilot-e2e

prow/e2e-simpleTests.sh
111069fd21cce875c4e8fd96c30743081f1787eb
link
/test e2e-simple

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@nmittler: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
111069fd21cce875c4e8fd96c30743081f1787eb
link
/test istio-pilot-e2e

prow/e2e-simpleTests.sh
111069fd21cce875c4e8fd96c30743081f1787eb
link
/test e2e-simple

prow/e2e-bookInfoTests.sh
111069fd21cce875c4e8fd96c30743081f1787eb
link
/test e2e-bookInfo

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Question: Is ok, that not-validated pictograms are public?

When we start translating pictogram, we fill some data in Czech and it's immediatelly visible for all users.
I understad, that checkbox is for remove it from Not validated list in admin web. But check my example in next sentences...
For example: I start typing, write only half of translatioin and go for tea/lunch/etc... users already see unfinished work in public!
Is that ok?
I think, that it should be published only when we check Validated on screen.

Why I check this and why I prefer to publish only Validated ones?
I wrote a script, it downloads all untranslated pictograms (download all, but take only where is no translation yet and fill it with English version but translated to target language with Machine Lerning (google translate / DeepL / Bing translator) it's on user or he can edit it manually) + fill properly Type of word (same as in english source) and update lastModified date + remove meaning because I check, that's not uploaded from web interface.
I'm able to publish "drafts" which are almost usable but need to be verified by translator before publishing to end users.
It works quite well and can save tons of manual typing to translators, but it has issues like wrong translations for singular vs plural where it uses different words etc...
Edit:
when I try to upload pictogram over API which has older lastModified than pictogram on server, is it ignored? Returned as conflict/etc? I could use older lastModified in script to be sure, that I never override some translation which did another translator.

When we designed the pictogram translation tool, we chose to make the pictograms visible (public status) once their design (image) was ready. Since then they are visible as long as there is a word that describes them in each language. The validated status simply allows the translator to know the status of their translations, but all published pictograms are accessible by users, regardless of whether they are validated or not. Doing a "double validation", general (publish state) and by language (validated), would have been very cumbersome because the work of translations is voluntary and we cannot exercise control or monitoring over languages that we do not know either.
We prefer to get bad results to not having anything at all.
lastModified field is just used to know the translators activity.

Maybe I was not correct in the description. It's not about whole pictogram, it should be visible, but about translations/keywords only.
For example: https://arasaac.org/pictograms/cs/2243/ is translated and validated.
I can see czech keywords for it from: https://privateapi.arasaac.org/api/pictograms/keywords/cs/2243

In this case: https://arasaac.org/pictograms/cs/21953/ I don't see any keywords, because it's not translated.

It is without keywords now, but still accessible - I can see the pictogram by category tree:

But in case:
https://arasaac.org/pictograms/cs/2259/ it's not validated.
So I expect, that https://privateapi.arasaac.org/api/pictograms/keywords/cs/2259 will return empty list for Czech.
Of course I can get english keywords: https://privateapi.arasaac.org/api/pictograms/keywords/en/2259 and see them.
What I expect in this case is empty list for czech until we check Validated on admin: https://admin.arasaac.org/pictograms/2259
    @GET("/pictograms/keywords/[locale]/[pictogramId]")
    fun getPictogramKeywords(locale: String, pictogramId: Int) {
        val pictogram = getPictogramById(pictogramId, locale)
        return if (pictogram.validated) {
            // show country specific keywords only when validated
            listOf(pictogram.keywords)
        } else {
            emptyList()
        }
    }

Out of this story:
I think, that public https://arasaac.org/pictograms/cs/2259/ should not request keywords from privateapi.arasaac.org, but from some public one like  https://api.arasaac.org/v1/pictograms/cs/2259

All keyword translations are public once they are set. No need to pass the validate status. Some times we detect our way of "naming" the pictograms is not correct enough. It's then when we use it to mark the pictograms for review.


Size difference in Chrome and Safari

My Semantic Page appears huge in Chrome, while in Safari all looks good. Any idea what went wrong?

You don't wanna know ....


Hand rotates by 180° when sneaking while gliding and holding an item instead of when not holding an item

If you sneak while gliding with an eltra, it's supposed to rotate your arm by 180° degree when not holding an item in the mainhand but in the latest version it is the other around. It only rotates by 180° when holding an item
https://github.com/user-attachments/assets/4cd2fa7a-bff7-4a94-9694-caa9d0815083

Fixed in 1.7.9, thanks for reporting.


How would this structure change for R?

I'm working on creating a similar standard for R at my company and was hoping to get some thoughts on if anything warrants changing to be R specific.

Good question! To me, the only obvious parts are the .py boilerplate files and the commands in the Makefile. Outside of that, things should be pretty sensical. For an R project. That said, a few R pros wrote resources that we link to here.
Your R workflow may dictate additional changes. How do you generally distribute code? Is it in R packages? If so, you may want some package boilerplate. Do you use Rmd and knitr? You may want to keep source in notebooks and output in reports.
Happy to hear other thoughts as well insofar as they generalize to the data science process across tools.

We have some groups that build Shiny Apps for their analytics, I'll need to talk with them to see what that all entails and if that would change the layout.
I know we'd like something super easy to execute like this for R without the dependency on Python. Is there anything similar to cookiecutter for R that we could build a pure R clone?

The R project template has done the most thought about an R only version: http://projecttemplate.net/index.html
Don't know of any cookiecutter clones for R...

@dreyco676 just found this - https://github.com/jacobcvt12/cookiecutter-R-package - could be a good option.

@isms thats perfect!

Since I don't think that we'll be migrating to a cookiecutter tool w/o the Python dependency (not even sure what the options are), and the structure works fine for R projects after it is generated, I'm going to close this issue for now.
Add #49 which might be nice for R users.


Optimize Serialization Using BSON C Extensions

Rationale
Serialization of emitter data can make up a large portion of simulation runtimes, according to profiling data.
Proposal
PyMongo implements its serialization logic in C and has the ability to accept custom encoders via the TypeCodec interface. Here, I modify the Serializer class to instantiate and return TypeCodec instances for serialization.
Results
When no document splitting is required, this PR nearly halves simulation time (running a simulation with a relatively large and complex emit). When document splitting is required at every timestep, the performance improvement drops to about 20%.
Drawbacks

Our document-splitting algorithm is very slow on unserialized data due to the costliness of converting Numpy arrays to strings (used to determine size of dictionary). In my simulations, splitting the emit before serialization is still marginally faster than what we currently have. However, I can see this resulting in performance regressions for simulations that emit more/larger Numpy arrays.

Solution 1: Use PyMongo's C extensions to convert the data as follows before splitting: dict --> BSON --> dict. The final dictionary will contain only BSON-supported types (e.g. built-ins), making the cost of our document splitting algorithm negligible. Interestingly, this round-trip scheme still yields a 40% improvement.
Solution 2: Try to serialize and insert each document without splitting. Default to the round-trip solution when splitting is necessary. This is implemented in 973de3a and yields the aforementioned 50% improvement. If every document requires splitting (worst case scenario), this is just Solution 1 with the added cost of serializing the entire emit at each timestep.
Solution 3: Serialize the emit to BSON, then check whether the BSON is over MongoDB's size limit. If so, deserialize it back to dict, split as needed, and send the split data to PyMongo for re-serialization and insertion. If not, instantiate a RawBSONDocument instance (which avoids PyMongo's internal serialization logic) and insert. This was implemented in b6b46f6 and ended up being significantly slower than Solution 2 even in the case where documents are split at every timestep.
Note: All relative performance numbers come from running my particular simulation. These margins of improvement may increase, decrease, or even become negative when running other simulations.

PyMongo's serializer requires that all dictionary keys be strings (or subclasses of strings, like np.str_). This is in line with the official JSON specifications, but it does break this test.
PyMongo does not automatically serialize objects that are subclasses of a class defined in a TypeCodec. This means that each Process, Composer, etc. requires its own TypeCodec as demonstrated here.
TypeCodec does not support custom de/serializers for Python's built-in types.
All Python objects of a given type must be serialized the same way (e.g. cannot treat float-filled and string-filled Numpy arrays differently).
Performance can be bottlenecked by document splitting for very large emits (e.g. simulation after multiple generations).

By creating this pull request, I agree to the Contributor License
Agreement, which is available in CLA.md at the top level of this
repository.

Ultimately, I decided on Solution 2 and updated the documentation to reflect the new API. The issues of TypeCodec not supporting custom serialization of built-ins or different serializers for homotypic objects can be sidestepped by manually defining serializers for individual stores using the _serializer key. These stores will, however, lose the performance advantage of using the BSON C extensions. The issue of slow document splitting is unavoidable, and, in any case, this solution is still almost always significantly faster than the current code. To summarize, the remaining drawbacks are:

All dictionary keys must be strings or subclasses thereof.
Type matching is exact, meaning unique subclasses require their own codecs.

To summarize, the remaining drawbacks are:
1. All dictionary keys must be strings or subclasses thereof.

2. Type matching is exact, meaning unique subclasses require their own codecs.

I think these downsides are pretty minor compared to the performance benefits this change will bring. We were already converting dictionary keys to strings prior to emitting them, so imposing downside (1) makes the data more consistent between emits and the Stores. Violating downside (2) currently throws warnings because it's less efficient, so we're already discouraging that behavior. I also can't think of any situations where you'd need to have different serializers for instances of the same type. If you did somehow need this functionality, you could just create a serializer for the type and have that serializer handle the two kinds of objects of that type differently. So overall, I'm in favor of this approach

Also the type checks are failing

I looked over the save state code, and we do not call any of the serialization routines in vivarium-core when creating the save state JSON file. Running from a saved state appeared to cause issues before, forcing Matt to add those lines in the self.serializer if block. It seems to work just fine now though.


White Space on Scroll

What is the current behavior?
When I scroll like a crazy man, I have issue with viewing components.
I have only white space without any markup - see screencast.

No have  only white space without any markup.
If you have any ideas, I will be very grateful.
P.S. Do not scroll like crazy does not fit. :-)
Which versions of React and react-virtualized, and which browser / OS are affected by this issue? Did this work in previous versions of react-virtualized?

Browser
Version 78.0.3904.97 (Official Build) (64-bit)

OS
Ubuntu 18.04.3 LTS

React
^16.8.0

React DOM
^16.8.0

react-virtualized
^9.21.1

We're having this issue too on my team. Here's the kicker: if you remove the LineGraph cell in your code sandbox, the issue goes away. It's taking just long enough to render that it causes the flicker
I still want some functionality to handle longer-loading rows from this library. Bigger web apps are moving beyond putting only text in these lists and tables, and we need a performant approach to this.
Off the top of my head: if the loading strategy changed to accommodate by rendering ahead further, but in batches, maybe this issue could be quickly sidestepped.

We're having this issue too on my team. Here's the kicker: if you remove the LineGraph cell in your code sandbox, the issue goes away. It's taking just long enough to render that it causes the flicker.
I still want this issue to be addressed, though. Bigger web apps are moving beyond putting only text in these lists and tables, and we need a performant approach to this.
Off the top of my head: if the loading strategy changed to accommodate by rendering ahead further, but in batches, maybe this issue could be quickly sidestepped. It could be a different take on overscanRowCount, which for me, only makes flickering worse when I up the value anyways.
In the meantime, all you can do is figure out a way to lazy-load the LineGraphs

Hi @jkoontz2010 is there a way to show my prepared static markup on flicker?


Padding margin on table markdown

add some padding/margin on table markdown style

This is about css it's for me

more issue 👍

real look


Fix broken links generated by Gradle

https://docs.gradle.org/current/userguide/build_init_plugin.html#sec:allow_insecure
https://docs.gradle.org/current/userguide/build_environment.html#sec:configuring_jvm_memory
https://docs.gradle.org/current/userguide/build_environment.html#sec:gradle_system_properties

Fixes #23785
Contributor Checklist

[x] Review Contribution Guidelines
[x] Make sure that all commits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
[x] Make sure all contributed code can be distributed under the terms of the Apache License 2.0, e.g. the code was written by yourself or the original code is licensed under a license compatible to Apache License 2.0.
[x] Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team
[x] Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective
[ ] Provide unit tests (under <subproject>/src/test) to verify logic
[ ] Update User Guide, DSL Reference, and Javadoc for public-facing changes
[x] Ensure that tests pass sanity check: ./gradlew sanityCheck
[x] Ensure that tests pass locally: ./gradlew <changed-subproject>:quickTest

Gradle Core Team Checklist

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

I've triggered a build for you.


Sign built NPM artifacts

Using the recommended way how to sign NPM artifacts, automate the signing of those artifacts from CI/CD builds. Create a script or similar that could be reused in multiple repositories and place it to the bamoe-ci repository.

I may be wrong, but for product, we won't have NPM artifacts published, only images.. Am I missing something?

Moving this back to Backlog

If you think this can be closed, please feel free to do so.

Closing this as the product artifacts are only container images.


setTimeout needed with enzyme 3.10.0

Current behavior
I have component including following:
componentDidMount() {
    this.props.errors.observe('errorShow', this.errorShowHandler)
    this.props.errors.observe('errorHide', this.errorHideHandler)
  }

errorShowHandler(errorObject) {
    this.setState({errorMessage: errorObject.code})
}

errorHideHandler() {
    this.setState({errorMessage: undefined})
}

render() {
    if (this.state.errorMessage) {
      return (

{{ this.state.errorMessage }}

      )
    }
    return null
}

And following way to test this:
describe('when error appears', () => {
    let wrapper, errors
    beforeAll(() => {
      errors = new ObservableModel()
      const strings = {}
      wrapper = mount(<ErrorUI errors={errors}/>)
      errors.update('errorShow', { code: 'TEST_ERROR' } )
      wrapper.update()
    })

    it('should show error code', () => {
      expect(wrapper.text()).toContain('TEST_ERROR')
    })

    describe('when error is hidden', () => {
      beforeAll(() => {
        errors.update('errorHide')
        wrapper.update()
      })

      it('should not show error message', () => {
        expect(wrapper.find('#error').length).toBe(0)
      })
    })

Expected behavior
Second test should work also with enzyme 3.10.0 but instead it says that "Expected 1 to be 0." Same test works with enzyme 3.7.0 - 3.9.0. Modifying test like this makes it also work with 3.10.0:
it('should not show error message', () => {
        setTimeout(function() { expect(wrapper.find('#error').length).toBe(0) }, 500)
 })

Your environment
API

[ ] shallow
[x] mount
[ ] render

Version

library
version

enzyme
3.10.0

react
16.11.0

react-dom
16.11.0

react-test-renderer
16.11.0

adapter (below)
1.6.0

Adapter

[x] enzyme-adapter-react-16
[ ] enzyme-adapter-react-16.3
[ ] enzyme-adapter-react-16.2
[ ] enzyme-adapter-react-16.1
[ ] enzyme-adapter-react-15
[ ] enzyme-adapter-react-15.4
[ ] enzyme-adapter-react-14
[ ] enzyme-adapter-react-13
[ ] enzyme-adapter-react-helper
[ ] others ( )

Using setTimeout like that is a race condition. The timing of your "ObservableModel" is not clear, but that is what everything depends on.

@ljharb I forgot to include constructor in my example:
constructor(props) {     super(props, logger)     this.errorShowHandler = this.errorShowHandler.bind(this)     this.errorHideHandler = this.errorHideHandler.bind(this)   }
So basically whenever I need to show or hide this component, I'm calling for "errors.update('errorShow')" or "errors.update('errorHide')" and the code I have in componentDidMount() does the rest.
I'm not really sure what changes there have been in 3.10.0 compared to earlier versions where test worked correctly but it feels that with 3.10.0 there's just not enough time for component to update itself before test is executed.


Wording in readme is missing a word

The following in bold does not make sense

If you want to send a photo to a user you can send a picture message. The API will download the image you supply and pass it along. You have to set the attribution name and icon for the message so the knows where the content came from even if it's forwarded later.

^ user.
Thanks. I'll get that fixed .


Email sample app thread view

Description

Updated Email sample app thread view

Screenshot

License
I confirm that this contribution is made under the terms of the MIT license and that I have the authority necessary to make this contribution on behalf of its copyright owner.

This look lit.


Update corrplot.py

Fix set_clim call.
Matplotlib dropped the support of that method for ColorBar from 3.3.0 version

I'm guessing the fix for the set_clim depreciation warning is in works? When I set colorbar=True I get the following error.
MatplotlibDeprecationWarning:
The set_clim function was deprecated in Matplotlib 3.1 and will be removed in 3.3. Use ScalarMappable.set_clim instead.
  cb.set_clim(0,1) # make sure it goes from -1 to 1 even though actual values may not reach that range

In the source code set_clim maps to the colorbar.

I'm guessing the fix for the set_clim depreciation warning is in works? When I set colorbar=True I get the following error.
MatplotlibDeprecationWarning:
The set_clim function was deprecated in Matplotlib 3.1 and will be removed in 3.3. Use ScalarMappable.set_clim instead.
  cb.set_clim(0,1) # make sure it goes from -1 to 1 even though actual values may not reach that range

In the source code set_clim maps to the colorbar.

This fix should correct the error.

I have obtained the package from PyPI using pip3 and the version I have is 0.4.6, which is still the latest version and I still have the same error. Interestingly when I do
import biokit
print(biokit.__version__)

I get 0.1.2

I have obtained the package from PyPI using pip3 and the version I have is 0.4.6, which is still the latest version and I still have the same error. Interestingly when I do
import biokit
print(biokit.__version__)

I get 0.1.2

This is correct because the __version__ is referred to the following string:
https://github.com/biokit/biokit/blob/master/biokit/init.py#L1
Instead, the pip package version is configured using the setup.py.
Moreover, the release version on GitHub is not matching any of those...

Would it possible to match the PyPI release to GitHub release with respect to this particular patch?

Would it possible to match the PyPI release to GitHub release with respect to this particular patch?

Yes, of course. But, I think that the version matching should be fixed in another issue. If this patch is accepted, then you can align the versions.

Would you like to me raise a separate issue with respect to the mis-match between GitHub and PyPI releases?

Would you like to me raise a separate issue with respect to the mis-match between GitHub and PyPI releases?

Yes, I think it is the correct flow for the fix you proposed. This issue involves only the corrplot.py file, so a separated issue will be more visible and manageable.


UNISA-16: Fix BitArrayOutputStream

Description
Connections, streams, files, and other classes that implement the Closeable interface or its super-interface, AutoCloseable, needs to be closed after use.
Changes

Close stream after use it.
Adding assert in pallet if is null

Codecov Report
Attention: 1 lines in your changes are missing coverage. Please review.

Comparison is base (ce72dfc) 71.17% compared to head (e5bd949) 71.16%.

Files
Patch %
Lines

.../apache/commons/imaging/formats/pcx/PcxWriter.java
0.00%
0 Missing and 1 partial :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff              @@
##             master      #16      +/-   ##
============================================
- Coverage     71.17%   71.16%   -0.01%
  Complexity     3522     3522
============================================
  Files           351      351
  Lines         17298    17301       +3
  Branches       2671     2672       +1
============================================
+ Hits          12311    12313       +2
  Misses         3932     3932
- Partials       1055     1056       +1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Not able to roated PIN PAD numbers

I want to display pin pad on JSP page how can I use generateRandomKeys  function to generate random number on pin pad.

All you need to do is to set the keys option by calling the $.ui.pinpad.generateRandomKeys() method.
This can be done when initializing the pin pad or by invoking option("keys", $.ui.pinpad.generateRandomKeys()) on the pin pad widget at any time after initialization.


Would you kindly review the changes whenever you have the time to?
Thank you very much.

@seanpmorgan We need to push a new Addons devcontainer with PR like this one to be aligned: https://github.com/tensorflow/addons/pull/1888


Keybase stuck on 'Loading' page in windows 11

I have a key base installed in my old machine when I try to install the same in my new machine. it stuck on the loading page for so long. I did run the key base log sent from my terminal.
Could I need to do any other changes?

Would you agree to say it's dead? https://github.com/keybase/client/issues/24577

For me this was caused by a missing file:
%localappdata%\keybase\keybaserq.exe
Keybase works properly again on my windows 11 if I either manually extract that from the .msi with 7zip, or uninstall/reinstall Keybase. A missing file should cause an overall installation failure, not sure what happened there and I can't reproduce it.


GUI changes

[x] Dialogs use stage background without any alpha applied, hiding everything beneath them. You could easily change the alpha value of stage background drawables to simply darken the stage under dialogs instead of completely hiding it. This looks especially awkward when you open the "about" dialog.
[x] VisUI FileChooser uses default style, which does not exactly fit the current themes. You could add FileChooserStyle to your skin and use VisUI.load(Skin) method to replace the default VisUI skin with one of your own. It also features no stage background as opposed to other dialogs.
[x] Image buttons have different sizes. Open List style for example to see what I mean. I think the font, color and drawable icons should have the same size (and its height could match the text field).
[x] There is no application icon.

Redesigned UI, switched to TinyFileDialogs, added application icon.

Current UI could still use some love. If you want a modern editor look, I'd start with VisUI skin (which is really decent for game dev tools) and go from there, recoloring and changing widgets you don't like in particular. In vis-ui-contrib there's a recolorable VisUI skin (Tinted) which I made a while back, you could try that out.

Truth be told, I don't like the look of VisUI skin or its current derivatives. I'm satisfied with Skin Composer's current look and functionality. I'm not going to spend a lot of time creating a new skin and adapting my widgets to have it ultimately look the same in the end. I'm still working toward making Skin Composer compatible with VisUI skins. One step at a time I'm afraid.

Well, VisUI derivatives tend to look somewhat similar to modern IDE skins (IntelliJ, Visual Studio Code and so on), but I can see what you mean.


SDK-62: exclude unconfirmedConnections and already active connections

This fixes the node trying to connect to already established connections

Now we skip the extra condition by merging the active connections with the uncofirmedConnections, extracting the address by running the getPeerAddress method, and passing the resulting list of addresses to the PeerManager via the RandomPeerExcluding message.
We should test that, having a connection that is not in any of the above data structures, the networkController sends to itself a ConnectTo message, while does nothing if we don't have any new candidate connection.
This method is a job that runs every 5 seconds. My idea was to extract the method so that we can run it multiple times and inject into it the connections and unconfirmedConnections ds so that we can test different scenarios. The PeerManager is also involved; since it's the one responsible for selecting the new candidate peer, we should fill it with peers. Maybe we could refactor it and, instead of having the peerDatabase instantiated in the constructor, we can have it injected. This way we can pass down an already filled db for testing purposes. The tricky part is the method extraction and testing such functionality that has a lot of moving pieces.


Update renovate Docker tag to v38.33

This PR contains the following updates:

Package
Update
Change

renovate (source)
minor
38.27-full -> 38.33-full

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.

Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.


Secrets yaml

@Grundy32, I assume sharing your wifi password publicly was an accident, right? Probably time to change it immediately...


Falsely displayed GPS location without GPS object in reported state.

Shadow state:
{
  "desired": {
    "cfg": {
      "gpst": 60,
      "mvres": 120,
      "mvt": 3600,
      "acct": 7.5,
      "actwt": 120
    }
  },
  "reported": {
    "bat": {
      "v": 5121,
      "ts":<PHONE_NUMBER>962
    },
    "dev": {
      "v": {
        "band": 20,
        "nw": "LTE-M",
        "iccid": "89450421180216216095",
        "modV": "mfw_nrf9160_1.2.3",
        "brdV": "nrf9160dk_nrf9160",
        "appV": "0.0.0-development"
      },
      "ts":<PHONE_NUMBER>083
    },
    "roam": {
      "v": {
        "rsrp": 66,
        "area": 2305,
        "mccmnc": 24202,
        "cell": 26902,
        "ip": "<IP_ADDRESS>"
      },
      "ts":<PHONE_NUMBER>939
    },
    "cfg": {
      "act": true,
      "gpst": 60,
      "actwt": 120,
      "mvres": 120,
      "mvt": 3600,
      "acct": 7.5
    }
  }
}

In the web UI the location is located outside the coast of Africa. long: 0, lat: 0, alt: 0.

This has been fixed by removing the bogus cell geolocation entries from the db. https://github.com/NordicSemiconductor/asset-tracker-cloud-aws-js/commit/8360e6ef41663f69b47eb49c08d244a801cf14aa fixes this for the future.
You need to disable the cache once to see the new cell:


compresses wepback build

went from 1 MB to 400 KB

Coverage remained the same at 98.611% when pulling 0e6e4ae74055c42f9b3cea7e13494888f1f4d1f4 on update-webpack-build into 8a5a1ce407435fdcd1e7ce62b9b941a54d515850 on master.


interactive-sr for everyone seems to have broken on Mac recently

https://github.com/standardebooks/web/commit/a6971750be1aa97abeab758f3c5a48bf0b16d291 updated the regex for the “everyone” interactive-sr from /\v([Ee])very one(\s+of)@\!/\1veryone/ to /\v([Ee]ach and )@*<\!([Ee])very one(\s+of)@\!/\1veryone/. This seems to have broken the command on the default Mac install of vim with the following error (2nd line repeated for each file):
Error detected while processing command line:
E59: invalid character after @

The default report for vim --version (on macOS 11 Big Sur) is:
VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Nov 23 2020 06:06:21)
macOS version
Included patches: 1-850
Compiled by<EMAIL_ADDRESS>
plus a big listing of compiled features.
I’m a vim newbie and have no idea how to start debugging this. Is it something you’ve seen before?

Looks like a stray * got in there somehow when I was editing the file. This should be fixed now!


fix: deprecated function ioutil

Fixes Issue
File read and write error on Windows because of deprecated library ioutil.
Changes proposed
Remove import library "io/ioutil" then change to ioutil. to os..
Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] My change requires changes to the documentation.
[x] I have updated the documentation accordingly.
[x] All new and existing tests passed.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers
Already tested on my Windows, it's working well.

LGTM, merged 🎉


Neural Networks [Python]

This issue is about Neural Network.

[x] Issue Title is in form Algo/DS Name [Language].
[x] I searched or browsed the repo’s other issues to ensure this is not a duplicate.
[x] This Algo/DS is worth adding to this repository.
[x] Assign this issue to me (I want to work on this).

[x] I ensure that I am not already assigned to 2 or more issues.

[x] I will send my PR only after I'm assigned to this issue by any maintainer.
[x] I understand that I will be unassigned from this issue if I fail to send a PR for this within a week.

Please don't close this issue. I was busy with something else. I will send a PR within three days.

@Prakash2403 Sir, on it?

Which neural Network is it exactly and what is it implementing.. can you
make yhe the title specific
On 01-Oct-2017 8:24 PM, "Aashutosh Rathi"<EMAIL_ADDRESS>wrote:

@Prakash2403 https://github.com/prakash2403 Sir, on it?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/iiitv/algos/issues/350#issuecomment-333382087, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AKU6yDclPi0rV0rwiJ7485XsJdtdBrN0ks5sn6eqgaJpZM4OCGzz
.

@aashutoshrathi Sorry, I am busy right now. Please assign this issue to someone else.


Navbar Design

Added the design from figma to the access pages navbar

The Navbar is not responsive. Make the appropriate changes so it works well for mobile. You could do this through "inspect" on your browser.
Also the navlinks are not properly centered.

From what I understand, the navlinks cannot be centered accurately because of the "Marketext" link text to the left, meaning that if I do accurately center it, it will be slightly off towards the right.
Also, since it's a webapp, I don't see why it should appropriately work on mobile?

The Navbar is not responsive. Make the appropriate changes so it works well for mobile. You could do this through "inspect" on your browser.
Also the navlinks are not properly centered.

From what I understand, the navlinks cannot be centered accurately because of the "Marketext" link text to the left, meaning that if I do accurately center it, it will be slightly off towards the right.
Also, since it's a webapp, I don't see why it should appropriately work on mobile?

With the proper css or just by following bootstrap's documentation of how to center items, you'll be able to do it. Check how the register/login/forgot password page was able to be centered. If there was a problem with the Marketext link, just have it be part of a 1 row, with column seperating the placements. For example, bootstrap documentation has something called grids, allowing you do col-2 for sizes.
Because it is a web app that it should work for both on Desktop view and mobile view. Web application basically means that it could be accessed on the web, on a browser, using http/https. Both desktop and mobile can access this functionality so it needs to be responsive throughout otherwise mobile users won't be able to access this web application.


Fork Inside ForkJoin With Pipe Insertion (Reprise)

There should really be a fix for this kind of thing since its not obvious to the average user and it always takes a few minutes to trace down the issue for me when I'm debugging their waveform.  The pipe inserter injects the sramread/regwrite in front of the switch as its own unit pipe.  The parallel schedule allows the switch to "resolve" before the unit pipe is done.
Parallel{
  val cond = // sram read
  if (cond) { // Outer switch
    ...
  }
  if (cond) { // Outer switch // Second one so it matches with the image below
    ...
  }
}

becomes

Fixed this in what I thought was the most reasonable way.  Generally people tend to write if blocks inside of their Parallel and they actually intend for the cond resolution to happen before the switch runs.  (also happens with setting up dram transfer bounds).  The pipe inserter used to step through the stms of an outer controller and mark the stage that each one belongs in.  Then it would go through and transform each stage, inserting the escaping regs if needed.  I added a step inbetween here where it steps through each of the stages and binds one stage to its subsequent stage if the escaping values are used there, and wraps the two together in a pipe.
What I'm not sure about is if there is a condition used by multiple stages in the parallel.  Will the transient analysis have already given each stage its own read of the condition, and will they be placed in the IR in the order that makes this new check work?


Steps to open up Nuitka development even further

This issue is to keep track of the things needed to enhance Nuitka develop even further for all @Nuitka/nuitka-pushers to collaborate.
Mid term goal is to enable non @kayhayen to make Nuitka releases.
Short term goal is to effectively collaborate on our Nuitka agendas.
I invite you to add things as we go, and will write notes and reference existing issues, and create new issues as we go.

One thing that every self respecting project needs is an API documentation. I started something with doxygen under doc/Doxyfile, but that work remains incomplete, although it probably is not a lot work remaining. Mostly missing a job to run it on my Buildbot and publish it.
That then should be used to make a plugin API description that @JorjMcKie could have helped with the plugins. The fact that he manages without shouldn't stop us. I will create an issue that mentions this one.

In a similar fashion, although not as important, I have nearly all the things needed for coverage information of Nuitka in the tests. Rending and publishing is missing, I think merging files from different OS was a problem, but it might be solved, I forgot. I will create an issue that mentions this one.

Inspired by an issue, but closed in the mean time, I started to make the nuitka web page repo something that is more workable. It is in part generated (Changelog.rst, README.rst, and Developer_Manual.rst), in part created via Nikola from a bunch of .rst files, and in part from files manually written.
Nobody can really change those right now. I need to move the repo to Nuitka organisation on github. One issue there is that builds are automatic and run code in a relatively unprotected environment. I need a way to make sure that some forms of changes are easy to make.
It's a pity that e.g. @deajan and @JorjMcKie should not talk about their changes publicly themselves, as for me there is always a private reason to not have the time to do so. And often not the knowledge what it really is.
This should be high priorty.

Nuitka Organisation should provide with Nuitka.git a place where all your branches live, so you can stop using your own forks under your name. That makes things more visible even before it's a PR.
We should have rules for @Nuitka/nuitka-pushers that everything ideally was looked at before merging it, that travis likes it, and so on. Right now, we have no public infrastructure that runs a huge amount of tests, only @kayhayen has that, but it's near impossible to expose that. This puts an extra responsibility on him to report issues on develop branch from PR merges.
We need to define such rules and merge them in Developer Manual. These rules should not be too strict or too formal, only master branch ought to be managed by one alone. I will create an issue and PR and mention this one in it.

Proper IDE support in Nuitka git.
Privately I am using Eclipse. We got a license to use PyCharm for Nuitka too. Project files for these two that do the right thing, e.g. calling black to autoformat on save, etc. should be provided. Also instructions how to set up those IDEs with Nuitka.
I will create an issue and mention this one in it.

Another thing, the Github repository should be pronounced the main one. Right now, there is official on nuitka.net and this is mostly only a mirror. As a first step I had changed the download page a while ago to point to here, but I think that ought to fully switch over to Github.
Also the CPython repos should move to Github, Debian upstream should be changed, a lot of small things.

So in the latest pre-release I just pushed, the autoformat works well, even on Windows, and doesn't even require PATH changes. The API documentation building likewise, if doxygen is installed in default PATH and it works on both Windows and Linux now which was a bit of a hack, now we need to generate the doxygen config.

So the Nuitka web site is a now there as Nuitka-website at https://github.com/Nuitka/Nuitka-website and I am hoping for pull requests on it.

Also, previously already, I made the CPython test suite submodule point to this new repo on Github: https://github.com/Nuitka/Nuitka-CPython-tests
The public repos on http://nuitka.net/gitweb are now all moved, and this can be deprecated at least.
The way I think I personally want to work, is to use the Nuitka.git there to build packages, so pushing to develop and master is only thing that decides what code gets run on my private (unsecured!) machines.
The alternative, signed tags, is for now not needed, but surely we will get there, once I want to enable you people to also make releases.

This has been done.

The CPython test suite procedure is documented in the developer manual these days as well.

The only thing we are still missing is coverage, the jobs are being run, and fail many times for interesting things, but the merging of coverage data from different OSes is a hard issue it seems. I need to revisit it occasionally though.
The other thing is API doc. Not sure if that's needed for all of Nuitka, but for plugins it should be there, and updated automatically. We should leverage sphinx and its autodoc there.

These were added to the roadmap document on Nuitka-Website, no need to track them as issues here anymore.


Reponse.content should not be ReferenceOr

Thanks for the lib.
According to the spec, I believe the Response object's content field should not be a ReferenceOr<MediaType> but just a bare MediaType.

I believe you are correct about this. Would you mind creating a pull request?


[vimeo] Incorrect description for certain videos

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm reporting that yt-dlp is broken on a supported site
[X] I've verified that I'm running yt-dlp version 2023.03.04 (update instructions) or later (specify commit)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched known issues and the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[ ] I've read about sharing account credentials and I'm willing to share it if required

Region
No response
Provide a description that is worded well enough to be understood
If a video has an empty description, yt-dlp will pick up something else and use it as the description. For example, for this video:
https://vimeo.com/251632201
the description which yt-dlp picks up is:
"Power your marketing strategy with perfectly branded videos to drive better ROI."
which is incorrect. The description should be empty.
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] If using API, add 'verbose': True to YoutubeDL params instead
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
[debug] Command-line config: ['-vU', '--get-description', 'https://vimeo.com/251632201']
[debug] Encodings: locale UTF-8, fs utf-8, pref UTF-8, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version<EMAIL_ADDRESS>[1fe5bf240] (zip)
[debug] Python 3.8.10 (CPython x86_64 64bit) - Linux-5.4.72-microsoft-standard-WSL2-x86_64-with-glibc2.29 (OpenSSL 1.1.1f  31 Mar 2020, glibc 2.31)
[debug] exe versions: ffmpeg n4.4-154-g79c114e1b2-20210923 (setts)
[debug] Optional libraries: certifi-2019.11.28, secretstorage-2.3.1, sqlite3-2.6.0, websockets-10.3
[debug] Proxy map: {}
[debug] Loaded 1840 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp-nightly-builds/releases/latest
Available version<EMAIL_ADDRESS>Current version<EMAIL_ADDRESS>Current Build Hash: 6e0482f61c2a1fd60fc19ba6a10b928842ed1a735714e115fa9b8e325a56ab7b
yt-dlp is up to date<EMAIL_ADDRESS>[vimeo] Extracting URL: https://vimeo.com/251632201
[vimeo] 251632201: Downloading webpage
[vimeo] 251632201: Downloading JSON metadata
[vimeo] 251632201: Downloading JSON metadata
[vimeo] 251632201: Checking Original video URL
[vimeo] 251632201: Downloading akfire_interconnect_quic m3u8 information
[vimeo] 251632201: Downloading akfire_interconnect_quic m3u8 information
[vimeo] 251632201: Downloading fastly_skyfire m3u8 information
[vimeo] 251632201: Downloading fastly_skyfire m3u8 information
[vimeo] 251632201: Downloading akfire_interconnect_quic MPD information
[vimeo] 251632201: Downloading akfire_interconnect_quic MPD information
[vimeo] 251632201: Downloading fastly_skyfire MPD information
[vimeo] 251632201: Downloading fastly_skyfire MPD information
[debug] Sort order given by extractor: quality, res, fps, hdr:12, source
[debug] Formats sorted by: hasvid, ie_pref, quality, res, fps, hdr:12(7), source, lang, vcodec:vp9.2(10), channels, acodec, filesize, fs_approx, tbr, vbr, abr, asr, proto, vext, aext, hasaud, id
[debug] Default format spec: bestvideo*+bestaudio/best
[info] 251632201: Downloading 1 format(s): Original
Power your marketing strategy with perfectly branded videos to drive better ROI.

Duplicate of #4354

Duplicate of #4354

I see. Thanks. I'll post a comment to that issue.


Feature request:  Option to disable the standard OTEL fields

e.g. otel.name, otel.status_code
I have no strong preference about whether it's a compile-time feature flag, a RootSpanBuilder option, etc - I just want to be able to disable them :)
If you can provide some guidance around what you prefer for implementation, I'd be happy to submit a PR

I'm not interested in supporting this, I'm sorry.

OTEL isn't the only use case for tracing - structured logging is another one, in which the OTEL fields are at best redundant, at worst harmfully noisy.  For a crate with a generic name like "tracing-", it would be nice to not have to hard fork to support something like that.
Oh well.

I am sympathetic with the arguments, but due to how tracing works (all fields must be declared when the span is defined and you can have at most 32) introducing this kind of optionality translates into a mess of macro-based code that is cumbersome to read, write and maintain.
Since I do not currently use this project for my own endeavours, I have no intention to increase the cognitive burden for it.
Introducing this kind of behaviour in a fork is trivial (literally just delete a few lines), so I don't think it's the end of the world :)

just out of curiosity, @LukeMathWalker what do you use for logging in your endeavours ?

I am working on Pavex at the moment!
The observability stack is a work in progress there, as the framework itself.


[KYUUBI #5766] Default spark.yarn.maxAppAttempts to 1 for spark engine

:mag: Description
Issue References 🔗

This pull request fixes #5766
Describe Your Solution 🔧
As discussed in https://github.com/apache/kyuubi/issues/5766#issuecomment-1835285025, we should add spark.yarn.maxAppAttempts=1 for spark engine when spark.master is yarn.
Types of changes :bookmark:

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

Test Plan 🧪
Behavior Without This Pull Request :coffin:
Behavior With This Pull Request :tada:
Related Unit Tests

Checklists
📝 Author Self Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[x] This patch was not authored or co-authored using Generative Tooling

📝 Committer Pre-Merge Checklist

[ ] Pull request title is okay.
[ ] No license issues.
[ ] Milestone correctly set?
[ ] Test coverage is ok
[ ] Assignees are selected.
[ ] Minimum number of approvals
[ ] No changes are requested

Be nice. Be informative.

Codecov Report
Attention: 1 lines in your changes are missing coverage. Please review.

Comparison is base (f4a739e) 61.34% compared to head (49b78fe) 61.40%.

Files
Patch %
Lines

...ache/kyuubi/engine/spark/SparkProcessBuilder.scala
85.71%
0 Missing and 1 partial :warning:

Additional details and impacted files
@@             Coverage Diff              @@
##             master    #5798      +/-   ##
============================================
+ Coverage     61.34%   61.40%   +0.06%
  Complexity       23       23
============================================
  Files           607      607
  Lines         35948    35952       +4
  Branches       4939     4939
============================================
+ Hits          22052    22077      +25
+ Misses        11498    11478      -20
+ Partials       2398     2397       -1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


x/pkgsite: package removal request for [type path here]

What is the path of the package that you would like to have removed?
Publicsuffix/
Are you the owner of this package?
Yes
What is the reason that you could not retract this package instead?
#54393 retract

#/pkgsite: package removal request for  #54154
#/pkgsite: package removal request for  #53147
#/pkgsite: package removal request for  #62159


🏳⭐💚 Esperanto language flag

Unlike all natural languages, the constructed auxiliary language Esperanto (or its community) has an official flag. An Emoji Flag Sequence using RIS code points for its ISO 639 code EO is not a viable solution, because there may arise the need for ISO 3166-1 to register this code element for an actual region. An Emoji Tag Sequence may work, but as of Emoji 5.0 only subregion emoji flags are supported this way. An Emoji ZWJ Sequence would have better fallback anyway. Since the main feature of the flag is a green five-pointed star, I would suggest ⭐💚 or 🏳⭐💚.
Specific References

https://github.com/Ranks/emojione/issues/263

Standard References

Unicode Technical Standard 51 “Unicode Emoji” (beta)
How to propose emojis to Unicode
How to propose other additions or changes to Unicode (required form, email address: docsubmit＠unicode.org)
Unicode document submission form

https://www.change.org/p/apple-add-esperanto-keyboard-and-flag-to-ios-keyboard-and-emoji

Possible designs for Android and Twitter respectively. I did not create these designs. Credit goes to Eugenio Hansen. Images are released under CC BY-SA 4.0

I forgot to mention the five-pointed star, which is also very common, especially if the medium enables to change text color (to green, in this case).
The symbol EЭ is also used ( https://eo.m.wikipedia.org/wiki/Jubilea_simbolo ), but not that much in my personnal experience.

Just to add a quick note here, in support of this proposal: Esperantists already use this emoji (created as a custom emoji) here on Mastodon: https://esperanto.masto.host/. It would be great if this were official and usable everywhere.

Issue #413 describes this emoji proposal as being added to the larger emoji set of "Flags".  What are the practical implications of this determination?  It doesn't appear to be a rejection, but there also doesn't appear to be an introduction of an Esperanto flag emoji in light of this proposal.  What does an emoji being added to a larger set mean with regards to that emoji's adoption?

May I suggest the use of 🟩 to mark the colour instead. According to Unicodes Emoji Design Guidelines # Colors, the large coloured squares can be used to define a colour of an emoji. The list defines 🐈⬛ as a black cat. Therefore a green star flag 🏳⭐🟩 or a green flag with star 🏳🟩⭐ would work better with the standard.

Yes, that is a recent addition which can be used that way.

Does anybody changed in this topic?

No, there hasn't been any progress.

Would the addition of tag sequences for flags help with this proposal? http://unicode.org/reports/tr51/#Sample_Valid_Emoji_Tag_Sequences
As the language is not meant to be associated to a particular place, the regional indicator should probably be ZZ, it would look a sequence like 🏴zzeo✦ (U+1F3F4 U+E007A U+E007A U+E0065 U+E0061 U+E007F). Would that made sense?

Nothing has changed from what I wrote initially:

An Emoji Tag Sequence may work, but as of Emoji 5.0 only subregion emoji flags are supported this way.

Esperanto is a language and not a geographic region. 🤷

Oops, indeed, I forgot that you already referred to the tag sequences. Sorry about that.

A proposal to Unicode could be made to have flags of laguages supported. This would allow flags for other languages such as Lojban, Sami, Ido and more.
Using the ISO 639 language code is ideal, and there's also the language tag character E00001. So Esperanto could be: 🏴Ⓛeo✦ where Ⓛ is the language tag character.

Openmoji has an Esperanto flag as U+1F3F3+FE0F+200D+1F7E9+200D+2B50+200D+1F7E9 : 🏳🟩⭐🟩.
https://github.com/hfg-gmuend/openmoji/blob/master/src/extras-openmoji/flags/1F3F3-FE0F-200D-1F7E9-200D-2B50-200D-1F7E9.svg

If the Esperanto flag is implemented in multiple emoji sets, we're likely to see requests for more language flags like Lojban (arguably a logo), and Ido. To implement these in a similar fashion, would that be 🏳⭕⭕🟦↕↔🟥 (flag-circle-circle-blue-arrow-arrow-red) and 🏳🟦🔻⭐⬜ (flag-blue-triangle-star-white)? I suspect it'll quickly become a mess.
So what about writing up a formal proposal to Unicode? We have to start somewhere. My suggestion is still using the subdivision flag sequence, but by adding the language tag character (U+E00001) and using ISO 639-1 and 639-3. We can also suggest other implementations as well, but I still strongly believe in using ISO 639 since that would weed out the less serious conlangs. After all, we don't want to see every conlang from the conlang wikia showing up. But instead well known ones as Esperanto, Lojban, Ido, but also Interlingue, Kotava, Lingua Franca Nova and Novial would be valid for implementation.
Another benefit is that languages associated with just a group of people, who has their own flag, but not a flag of a region, would have the opportunity to have their flag available. Such as the Sami flag (usually used for Northern Sami), but however not the Australian Aboriginal flag, since it doesn't represent one language.

Unlike geographical regions and tribes or peoples, languages rarely have flags. You could actually argue that languages never have flags but their speaker communities may. There is no ISO alphanumeric code for cultural groups, but maybe there should be – perhaps as an extension to the spatial area codes of ISO 3166.

@Crissov while you are right that most languages don't have flags, and when flag are used, it's commonly the flag of the nation the language is named after (except for English, Spanish and Portuguese). But for when languages do have flags, which is still a few (a few more if you include logos), having a consistent standard for all these is something I still recommended.
Searching on Google, and there doesn't seem to be any ISO code standard for ethnicities (I'm not surprised), but there exists some code standard for some counties. So maybe an ISO standard should exist for this? Or perhaps not.
But sure, languages are too limited to cover all forms of tribes and groups of people. Such as Finland-Swedes, which has a red flag with a yellow cross. This would require both a language code and a country code, and there's no country tag character, but there is hyphen-minus, so ⚑Ⓛsv-fi✦ is possible, but at this point it might actually just be better to "describe" it using shapes: 🏳🟥✝🟨 (flag-red-cross-yellow).
Maybe a request for flag building blocks could be made instead. Such as "canton" and "emblem", so the Esperanto flag is "flag-green-[canton]-white-[emblem]-star-green", and also for what shape the background is, so for Lingua Franca Nova it is "flag-[bottom_left_spread]-blue-green-yellow-orange-red". You could then also use this for other LGBT+ flags, like the bisexual flag which can be "flag-[horizontal_bands]-pink-pink-purple-blue-blue" (repeated to give it the 2:1:2 shape it has). This would even allow the Australian Aboriginal flag to be made as well by doing "flag-[horizontal_bands]-black-red-[emblem]-dot-yellow".

Whatsapp is currently laying out cow paths which may be paved later on. 🏳🟧⬛🟧 https://blog.emojipedia.org/whatsapps-new-refugee-nation-flag/

Yes, maybe horizontal bars should be assumed. Using the white flag followed by squares does make sense. The refugee nation flag has weird proportions; about 5:1:2, but more accurately as 63:13:24. But I still think it's good to incorporate the proportions in the sequence. There are flags where the proportions matter: Tatarstan and North Rhine-Westphalia - although these two specifically do have subdivision codes, my point still remains about other flags. There's no other red-black-red striped flag that I can find, but one might be made in the future.
So having "flag-red-red-red-red-red-black-red-red" is one idea, alternatively "flag-red-5-black-red-2", since digits are valid emojis too as far as I'm aware (I don't mean the keycaps).
Just trying to think up ideas to future-proof any system.

I don’t know how much it could help on settling a good format, but it might be related. The French language has a (not well-known) flag for its community: https://upload.wikimedia.org/wikipedia/commons/2/27/Flag_of_La_Francophonie.svg Depending on the article language, it’s not clear in Wikipedia whether this flag is the flag of the corresponding international organisation (in which case I’m out of scope, sorry) or of the French-speaking community. In any case, it’s quite different from the French flag, so it might be an example where 🏴Ⓛfra✦ (if it’s the format that is chosen) would be different from the flag of the nation the language is named after.
I like the idea of basing the proposal on ISO 639, even though it would not always be applicable. Would it be an issue to only have a partial specification? Like saying that this only applies to languages with a flag?

@Mbodin I would suggest it being just 🏴Ⓛfr✦, saves one character (4 bytes in UTF-8). Having that as the flag of French, would allow people to choose between it and the flag of France. That flag seems to represent French speakers as a whole, and is as far as I can see the most optimal flag of French. As said, people can still pick whichever they prefer to use.
I'm not exactly sure what you mean by partial specification; but if this idea was to be implemented, it would only be used for language codes that do have flags (aformentioned conlang flags) and could also be for languages closely tied with a group of people who have a flag (like Sami 🏴Ⓛsmi✦ and Romani 🏴Ⓛrom✦). But wouldn't be used for most languages such as English, Spanish, German (unless there's an actual flag that isn't the national flag?). It's similar to how the subdivision flag standard was made for all ISO 3166-2 codes, even though some regions don't have flags, so a lot of valid emoji codes will go unused. It would only be used if there's a flag. One could argue this is the flag of English which often is used (but I'd argue 🏴gbeng✦ should be used instead).

Hey, any news ?

+1

+1

+1

+1

The issue isn't solved, is it?

Unicode does not accept flag emoji proposals anymore, so the issue is resolved as Won’t Fix.

Oh, okay, sad

http://blog.unicode.org/2022/03/the-past-and-future-of-flag-emoji.html <- This is a blog post on the subject of Unicode no longer accepting flag proposals, for context.
Thanks for the update, Crissov.  While this clearly wasn't the result this issue thread's participants desired, the closure is nevertheless appreciated.

I think the issue with having tons and tons of flag emoji could be largely fixed by having a couple analogues to the Unicode regional indicator symbols that can represent things with a defined code. This same system could be used for language symbols, company logos, cryptocurrency symbols (there is one for Bitcoin but no other cryptocurrencies) and more while requiring only 26 symbols per category. it could be reduced even further by just having a single symbol for which category it is in and then latin letters (or some special symbol like the regional indicators) for whichever indicator it has.
The Esperanto flag would be extremely useful for representing language selection, and this same proposal could be used for every other language with an ISO code as well, and more. Unicode doesn't even need to recommend any single language flag. Just having the option to implement it in fonts would help immensely.
Would anyone be interested in creating some competing standard that uses the Unicode Private Use Area to make something like this? I think it could be very useful for creating symbols not just for languages, but for a lot of other things as well.

@happysmash27 This is what I suggested above. Use the method created by making subdivision flags, but after the black flag, you insert the language tag character, followed by the shortest ISO 639 code for the language. Esperanto will be 🏴Ⓛeo✦ (black flag, language tag, e tag, o tag, cancel tag).
If a language and a group of people are closely tied together, one way could be to represent this group of people by the language flag. For example 🏴Ⓛsmi✦ for the Sami people and language flag, and 🏴Ⓛnv✦ for the Navajo Nation flag. But it isn't necessary to use the language flag if a subdivision flag is already available, for example 🏴iqkr✦ for the flag of the Kurdistan region in Iraq is commonly used to represent the Kurds, so it isn't necessary to create an emoji for 🏴Ⓛku✦ (Kurdish), even if the emoji sequence is still valid.
Since there isn't any standard for etnicitets, using languages to represent etnicitets unless a subdivision is already available, is the best we can do, I think. This is such a simple method that we don't even need to use private use characters.
Company logos and cryptocurrencies is a bit trickier to implement. There's no real standard for what codes you would use, since there are companies with the same names, and there's plenty of cryptocurrencies. But having different emojis for official national currency symbols isn't a bad idea, and we can continue with the tag system. 💲 is the only sole emoji currency symbol, so write 💲eur✦ for €, 💲gbp✦ for £, 💲pln✦ for zł, and so on. You could then expand this to cryptocurrencies by writing 💲ethereum✦ for example, since it wouldn't be valid to write 💲eth✦, since that is a currency code for Ethiopia. But cryptocurrency names aren't official anywhere, so it isn't as robust as using ISO 4217 for national currencies. For companies, the best I got so far is the Stock Ticker Symbols, but that would only cover stock companies.
But the issue with company logos and some cryptocurrency logos, is that they are copyrighted, and there are restrictions on how they can be implemented. That's why at least supporting the national currency symbols would work, since those are usually free to use however you want (Poland doesn't own the letter sequence "zł" for example).

hello a new proposal to unicode is this planned?


ActionResult docs

Signed-off-by: liach<EMAIL_ADDRESS>

personally I think the two methods are a bit poorly named but since this is just a docs PR, it's fine.


Increase Accessbilty/Contrast in dark theme

Description
The contrast between background and font is low in dark theme. It is really exhausting using it. Depending on display/backlight and also features like "Low Blue Light" make sometimes hard to read the content. Compared to other dark themes the background is bright and font gray.
I like dark themes like YouTube or KDE breeze dark skin.
My suggestion wold be Lighthouse accessibility tool to test color contrast.

https://github.com/GoogleChrome/lighthouse/
Also used in Google insight

Should be improved @bot :P

As well, here:

I actually had some issues reading with the current contrast, so I made a new theme yesterday: https://github.com/Jieiku/theme-dark-gitea

@silverwind Would you be able to help me the source for the arc-green theme? As in: where did you find the values for the Less file?
https://github.com/go-gitea/gitea/blob/73382d2132f8f242245d83f66c92761e0b477b91/web_src/less/themes/theme-arc-green.less
I noticed that the file is around for a long time, but you seem to have the most familiarity with it.
KDE Breeze Dark colour palette is defined in https://develop.kde.org/hig/style/color/dark/

@TTWNO We touched the topic on Matrix before. Do you have ideas here?

 I don't know; maybe other people like it that way, but low-contrast dark themes defeat the purpose of dark theme. The background is still bright hurting my eyes, and the text is too dark to read when my monitor is set to the minimum brightness. To read the text, I would have to increase the monitor brightness, further scorching my eyes.
Can't you just add another in-built theme, "high-contrast dark"? Refer to IntelliJ (Android Studio or any similar IDE).

I plan to make a proper dark theme now that all colors are in CSS variables. After that is done, we can talk about high-contrast themes that would probably build on the default light/dark themes.

Yes, I think current dark theme has enough contrast. I have not ran WCAG on it yet, but I assume it'll be close to passing those tests.


ENH: CLI - simpler way to get a CLUSTER_ID

Current docs here https://github.com/bf2fc6cc711aee1a0c2a/mas-guides/blob/master/common/creating-kafka.adoc suggest this expression to get a CLUSTER_ID:
CLUSTER_ID=$(rhoas kafka describe | jq .id -r)

we should consider a single command to get the information that would avoid piping the output to one or two commands to be usable.
It could be something like this:
source $(rhoas kafka get-cluster-id --id <id>)

Update:
Current approach based on jq is better than the old one based on grep and awk but the final goal is probably to have this as a provided functionality by rhoas.

This seems to be resolved.
Status command exists. Describe accepts id


laravel 7

(optional) Issue number:
Summary of the change:

Please merge asap.

Thanks for the PR! But we cannot merge this as it contains namespace changes.


Export options types

Feature description
I was previously using the options type provided in the DefinitelyTyped package (i.e. V7Options) to type a function that passed through options to the UUID constructor. I would love if those options types were exported by UUID v11
Additional information
I can work around the issue by declaring a type type V7Options = Parameters<typeof v7>[0], but it's a little clunky compared to having access to the type directly

I'd be happy to take a look at a PR. :-)
Note: Such a PR should treat the options arg consistently for all v1-v7 methods similarly)


Allow for Instances to be scoped to the module instance rather than initializing to globalThis

As seen here the root logger is always initialized as a property of globalThis it would be nice if there could be either

A flag to denote the root logger should be initialized within scope of the module
Allow for an object to be passed which will have the root logger assigned as a property

In general, the root logger shouldn't be used in the first place. What are the benefits of scoping a root logger to a module instance?

Right, but the root logger is used for all child logger look ups. Perhaps not scoped to module is strictly necessary but either / both of the following I think are helpful for DX as global namespacing is a bit of an anti pattern in modern JS

Allowing users to explicitly choose where the root logger is created by allowing an object of their choosing to be passed which will then have the root logger assigned as a property. This object then can be referenced internally within LoggerImpl for later usage.

Scoping the root logger as a static property on LoggerImpl and implementations like getLogger can still function as expected since the root instance will also be static.

The reason I tie the root logger to globalThis is to share sink/filter configuration between applications and libraries using different versions of LogTape. (In case you didn't know, LogTape is designed to receive logs from inside the library on the application side.) Is there a way to solve this without using globalThis?

To my understanding the primary way for applications to configure is through the LoggerImpl class which is interfaced with here. It would be possible to scope the loggers returned from this getLoggeras a static property of LoggerImpl.

As far as I know, when there are multiple versions of the same package, even if classes have the same name, they are not the same object. In other words, static properties are not shared across multiple versions. That's why I tie the root logger to globalThis. 🥲

I see, was unaware there could be multiple versions across the import graph. Some bundlers will handle this by standardizing to a single package version unless overridden.
Would there be tolerance to another package for use of state storage like @logtape/store such that compatible package versions could use a single module exported from this package to store the root and other state that might need to be shared across instances?
By doing this, there is the added benefit in warning when a package version might be too old to integrate across different versions used. WDYT?

That way may work (I'm not sure though), but I'm hesitant to add a dependency to LogTape because one of the key points of LogTape is that it's zero-dependency. 🤔

Zero dependencies: LogTape has zero dependencies. You can use LogTape without worrying about the dependencies of LogTape

To me, this reads as "Zero external dependencies" the dependency introduced would be maintained by the project and only be separated due to technical requirements. as a consumer of the package I would not care too much that a new package was installed as long as it as an explicit peer dependency and was versioned explicitly such that it could be guaranteed to have version compatibility.
By splitting into two packages, shared state could more easily enforce versions which are compatible with said storage package. For example say library foo is being used by an app dev and it uses an outdated version of the logger which could be logged as a warning or critical error depending on how out of date package foo version is for this example.

I see, but splitting LogTape into multiple packages doesn't seem like something I'd want to undertake right away, as it would require not just a refactoring, but a major overhaul of the current deployment script and repository layout. 😅

Makes sense,
Something to keep in mind for the future. It would also allow user provided initialization context much as it then could be a simple reference to the user provided package in the module split into a separate package.


webviews should have real view column after they are created

https://dev.azure.com/monacotools/Monaco/_build/results?buildId=150412&view=logs&j=672276a2-8d3a-5fab-615d-090c51352f92&t=c55167a9-8752-5898-67fa-9d7c918c61b3&l=390
1) vscode API - webview
       webviews should have real view column after they are created, #56097:
     Error: Timeout of 60000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (D:\a\1\s\extensions\vscode-api-tests\out\singlefolder-tests\webview.test.js)
      at listOnTimeout (internal/timers.js:554:17)
      at processTimers (internal/timers.js:497:7)

Duplicate of #153066


tpl: Add internal template enabling web monetization

Add internal template that enables web monetization by adding a meta tag to the head of each page. It grabs the payment pointer from the params section in the config file.
Documentation has been added to explain how to include web monetization into the website, just like google analytics.
Background
Web monetization is a proposed W3C standard that allows the creation of a payment stream from the user agent to the website. It uses the Interledger Protocol, a currency agnostic micro-payment protocol, to stream money while a user is visiting the website.
That user has to have a means of streaming payments. There is no visible difference for users who are streaming and for those who are not streaming.
Web monetization offers a new possibility for content creators to monetize their work. It is an alternative to the advertisement model.

 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.

Hey, and thanks for this.
Web monetization was new to me, so the first instinct was to say that this may not sound like a general useful template yet ... but I like the money and getting paid for my work ...
The simplest form of this is easy to add to your site/theme as it is today. For the more complex scenarios, you would probably have multiple authors, each with their own wallet.
We need to think a little before adding this, is what I'm saying.
/cc @regisphilibert @onedrawingperday etc.

Web monetization is a proposed W3C standard

We cannot add an internal template for a W3C proposal. Can we?
If it is approved then maybe yes, we could add this.

The simplest form of this is easy to add to your site/theme as it is today. For the more complex scenarios, you would probably have multiple authors, each with their own wallet.

I started with the most simple case to get you guys' reaction. I also have an advanced implementations for exclusive content (i.e. hiding stuff on the website if the user visiting it is not streaming). Having multiple payment pointers for different sites when multiple people write blog posts or something is also on my agenda.

We cannot add an internal template for a W3C proposal. Can we?

What are the criteria for an internal template?

What are the criteria for an internal template?

These are not set somewhere, but I suppose that we ought to support features that are part of the W3C spec.
However that is my opinion, the others might think otherwise.

We cannot add an internal template for a W3C proposal. Can we?

Of course we can if it is "useful enough".  The web is full of useful stuff that isn't W3C. But I think we need to think a little about this one.

Take some time and think it over. Feel free to ask for any additional explanations or resources regarding web monetization and interledger.
By the way, there is a demo at https://hugowebmonetization.netlify.com/ that also includes the "exclusive content" part. It was a hackathon project of mine.

I feel like this belong more in a module/theme than an internal template. Any reason why the Hugo maintainers should be responsible for this implementation and its potential maintaining should the API evolve?

https://www.w3.org/TR/ - there are lots of proposals and standards.
I feel like adding a meta tag should be the function of a "theme component" and not an internal template. Established internal templates add larger functionality than a single header tag.
Also: as long as it's a W3C proposal only adding it to Hugo might be interpreted as taking a side.

I feel like adding a meta tag should be the function of a "theme component" and not an internal template.

I have not come across theme components so far but from what I've read after a quick search sounds like this may be an alternative for now. I need to look more into it and have to understand the merge better. I appreciate any good resource links.

Also: as long as it's a W3C proposal only adding it to Hugo might be interpreted as taking a side.

There is already a wordpress plugin. And it is taking the right side ;-).

You prove my point :) Make it a theme component. Wordpress plugins are not part of Wordpress, but an extension of it. Comparable to theme components.
You install it like a theme, then add it to your theme configuration in config.toml (as an array).
Have a look at https://github.com/kaushalmodi/hugo-debugprint to see how it's done.
I wonder though if there is a way to "add to <head>" without having to temper with templates of a theme itself in the end.

I wonder though if there is a way to "add to " without having to temper with templates of a theme itself in the end.

There is no template "hooks" à la Wordpress. But the component can document that users should add the "partial" call to their head.

But the component can document that users should add the "partial" call to their head.

Wouldn't that mean the the user is either writing their own baseof.html or they need to edit the one their main theme is providing? Ideally, I want a solution where the user only has to add the payment pointer in the config.toml.

Ideally, I want a solution where the user only has to add the payment pointer in the config.toml

Understandably, but then theme editors will have to include your module.

I am fairly new to all of this and I already like your community - you reply so fast! Thank you!
Are the baseof.html files fairly standard across themes? Because then I could write a _default/baseof.html file that looks like all the others but includes web monetization. Because I am assuming that I cannot somehow merge those files or import one into the other since it is the base template.

Are the baseof.html files fairly standard across themes?

No I would say baseof.html are very different among themes.
I would gather that most theme uses a head partial.
I'm not sure there is any way around that. But others might chime in.

I created a component: https://github.com/sabinebertram/hugo-webmonetization-component
I'll close the PR for now and move further discussions to the forum. Thanks for your help so far!


Added several fine-tuned wfm-list-leave-behind

We may need different lengths for the leave-behind box depending on the number of buttons to display.
Usage example:
<div class="wfm-leave-behind wfm-leave-behind-1">

for leave-behind box for one button.

I will create another pull request from a feature branch in my repo instead of master


[SPARK-48430][SQL] Fix map value extraction when map contains collated strings

What changes were proposed in this pull request?

Following queries return unexpected results:
select collation(map('a', 'b' collate utf8_binary_lcase)['a']);
select collation(element_at(map('a', 'b' collate utf8_binary_lcase), 'a'));

Both return UTF8_BINARY instead of UTF8_BINARY_LCASE.
The error was introduced by changes in https://github.com/apache/spark/pull/46661 that tried to solve other problem with RaiseError expression (please refer to PR for details). Partially revert changes of mentioned PR and fix the RaiseError issue by explicitly setting UTF8_BINARY collation.
Why are the changes needed?

To fix wrong results of mentioned queries.
Does this PR introduce any user-facing change?

Yes, it fixed explained error.
How was this patch tested?

Added test to CollationSQLExpressionsSuite.
Was this patch authored or co-authored using generative AI tooling?

No.

can we do a more surgical partial revert? I did notice the potential issue in the offending PR but didn't realize it could cause a real issue: https://github.com/apache/spark/pull/46661#discussion_r1609846584
I agree we should match RaiseError explicitly in the rule CollationTypeCasts, but changes in other files can remain?

thanks, merging to master!


Resource limit? Or error - failing to return resources

Hi,
When choosing query OCI for a specific tenancy, incl. all sub-compartments the application hangs an never returns a response (just the swirling O ). Other tenancies work fine, and if I query only one compartment on this tenancy it works as well.
I see the below error in the docker console log.
2024-09-16 13:29:16 INFO: Request : ['af-johannesburg-1']
2024-09-16 13:29:16 INFO: Request : ['ocid1.tenancy.oc1..##############HIDDEN###################']
2024-09-16 13:29:16 INFO: Request : True
2024-09-16 13:29:18 INFO: submitted 1 list resources requests
2024-09-16 13:29:19 INFO: processed 1 list resources responses
2024-09-16 13:29:20 INFO: found 10 active compartments
2024-09-16 13:29:22 INFO: submitted 1 search requests
2024-09-16 13:29:22 INFO: requesting resources for af-johannesburg-1
2024-09-16 13:29:25 INFO: processed 1 search responses
2024-09-16 13:29:25 INFO: submitted 382 list resources requests
2024-09-16 13:29:40 INFO: processed 382 list resources responses
2024-09-16 13:29:40 INFO: submitted 3991 list resources requests
2024-09-16 13:31:43 WARNING: Too Many Requests for get_rr_set, retry in 0.1 seconds
2024-09-16 13:32:23 WARNING: Too Many Requests for get_rr_set, retry in 0.1 seconds
2024-09-16 13:32:43 WARNING: Too Many Requests for get_rr_set, retry in 0.1 seconds
2024-09-16 13:32:53 WARNING: Too Many Requests for get_rr_set, retry in 0.1 seconds
2024-09-16 13:34:19 WARNING: Too Many Requests for get_rr_set, retry in 0.1 seconds
2024-09-16 13:34:33 WARNING: Too Many Requests for get_rr_set, retry in 0.1 seconds
2024-09-16 13:34:37 WARNING: Too Many Requests for get_rr_set, retry in 0.1 seconds
2024-09-16 13:34:49 WARNING: Too Many Requests for get_rr_set, retry in 0.1 seconds
2024-09-16 13:35:14 WARNING: Too Many Requests for get_rr_set, retry in 0.1 seconds
2024-09-16 13:36:08 WARNING: Too Many Requests for get_rr_set, retry in 0.1 seconds
2024-09-16 13:36:15 WARNING: Too Many Requests for get_rr_set, retry in 0.1 seconds
2024-09-16 13:36:24 WARNING: Too Many Requests for get_rr_set, retry in 0.1 seconds
These warnings just keep coming

@camsaway This is OCI backing off the query requests. It should eventually retry enough and return the data

Hi, You are correct. I just had to be very patient. Took over 20mins before it returned. Thanks.


chore(release): publish v1.1.3

Issue the v1.1.3 release and see if the npm auto-publishing workflow is still buggy or not.
We also need the fix in test-tooling so that #2204  can be merged.

Release has been issued (the auto-publishing is still broken though)


[feature]: nested view paths

Is your feature request related to a problem? Please describe.
If the application grows it can make sense to not just have a flat "views" folder but to nest similar views together. Having hundreds of views can make it hard to not use very long long view names.
Describe the solution you would like
Make it possible to use stacked create view folder/to/view/group/test for creating a new view in a nested structure.
Additional Context
Especially for processes with a lot of steps it's nice to put everything into one parent folder.

I would say that for cases like that could be better to make use of packages to group views per feature or a selected criteria.
What do you think @FilledStacks ?

Hello, is this implemented?

Yes you can supply a path using -c
@ferrarafer it would have probably been better to supply a path for output using -p
stacked create view login -c lib/features/authentication/ui/

@FilledStacks yeah, maybe -p has more sense. It was -c because it overrides the custom config path.
I add this to the list of tasks.

@sebastianbuechler let me know if this is not the feature you were asking for. I'm closing for now

@sebastianbuechler let me know if this is not the feature you were asking for. I'm closing for now

That was exactly what I asked for 💯 Thanks!


Michael/alert docker fail

We should talk about this approach as I'm not sure I'm totally happy with it.
The basic idea would be to check this and alert if we received a high percentage of failures within a short period of time. It will flap with failing docker containers, not always return a non-zero exit code.
Another idea would be to check the mesos logs for a high number of failing docker containers with the same ID. I'm working on that now, let's talk tomorrow about the best approach.

Closing for now in favor of #8, might update with a similar task next time...


[WebConsoleV2] PrintLogs add scroll to bottom function if has new logs

If the user not at the bottom of the printer, meanwhile, new logs have been fetched, show him a scroll-to-bottom button

LGTM


Cannot extend a "flavored" product with web

Steps to Reproduce

Create a regular project (ios/android) etc & define flavors (like "standard") in the Xcode workspace. I created it using the stable branch.
Attempt to extend the project with web support by calling flutter create again (this time from the beta branch)

Attempting it first will show the following message:
$ flutter create --platforms web .

The Xcode project defines schemes: standard
You must specify a --flavor option to select one of the available schemes.

Following this up with the flavor option raises a error:
$ flutter create --platforms web --flavor standard .
Could not find an option named "flavor".

Run 'flutter -h' (or 'flutter <command> -h') for available flutter commands and options.

[✓] Flutter (Channel beta, 1.22.0-12.1.pre, on Mac OS X 10.15.6 19G2021, locale en-US)
    • Flutter version 1.22.0-12.1.pre at /Users/ened/dev/flutter
    • Framework revision 8b3760638a (8 days ago), 2020-09-15 17:47:13 -0700
    • Engine revision 4654fc6cf6
    • Dart version 2.10.0 (build 2.10.0-110.3.beta)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /usr/local/share/android-sdk
    • Platform android-30, build-tools 30.0.2
    • ANDROID_HOME = /usr/local/share/android-sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.0)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.0, Build version 12A7209
    • CocoaPods version 1.9.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 49.0.2
    • Dart plugin version 193.7547
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.49.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.14.1

[✓] Connected device (2 available)
    • Web Server (web) • web-server • web-javascript • Flutter Tools
    • Chrome (web)     • chrome     • web-javascript • Google Chrome 83.0.4103.116

• No issues found!

Hi @ened,
flavor is not supported on web and Flutter doesn't have plans to implement it. Please see this comment and possible workarounds.
I am going ahead and closing this. If you disagree, write in comments and I'll reopen.
Thanks.

@darshankawar in that case the ticket could be renamed to reflect that the flutter command output is misleading.


Travis integration

Changes Unknown when pulling 5334c1117126fc09a602b143a22f2c435e9b35e8 on travis-integration into ** on master**.

Changes Unknown when pulling 1ae023d1da861e567adf49bf03e2d1fe6222eb9d on travis-integration into ** on master**.

Changes Unknown when pulling 1ae023d1da861e567adf49bf03e2d1fe6222eb9d on travis-integration into ** on master**.

Changes Unknown when pulling 9097a8d9a9d99e6be69759f55de8e47943603f49 on travis-integration into ** on master**.

Changes Unknown when pulling 9097a8d9a9d99e6be69759f55de8e47943603f49 on travis-integration into ** on master**.

Changes Unknown when pulling 9097a8d9a9d99e6be69759f55de8e47943603f49 on travis-integration into ** on master**.


Upgrade VS Code extension to Ruby LSP

This upgrades VS Code extension in DevContainer to the new Ruby LSP. It also updates settings file format.

@rafaelfranca Mind taking a look at this one? I don't use VSCode, so not sure of the impact.

@brenogazzola if it helps, take a look at main rails repo, they are using this same extension: https://github.com/rails/rails/blob/main/.devcontainer/devcontainer.json#L36.


Strip Chatty Kathy of her admin priviledges

Right now Chatty Kathy's an admin, but I don't think she needs to be

I can see the account details in the settings.yml but not where you request the account to be set up
Can the system account not be used in this instance as the account is only to create the initial post isnt it?  Surely with the system account being number -1 in each instance could that not be used?

The user is set up in Babble::User in plugin.rb, which is set up as a singleton.
https://github.com/gdpelican/babble/blob/master/plugin.rb#L237
Originally, we were tracking which topics were chat topics by saying Babble::User.instance.topics (all the topics CK created) I think we could/should instead say Babble::Category.instance.topics (all topics in the 'chat' category)
I can't recall off the top of my head why we needed admin privileges to create those topics, but I definitely did try using the system user first. It's likely a better idea to jigger the Guardian a bit to allow the system user to create chat topics though, rather than having this random floating admin around.

I totally nuked Chatty Kathy last week! Existing instances should be able to get rid of her safely now.


"run workflow" redirects to a job table that is not up to date

I prepare a workflow
I submit it for execution ("run workflow"), and I confirm
I am redirected to a job page (e.g. http://localhost:5173/projects/2/jobs?workflow=4&id=4)
The table is empty
I refresh the page
The table shows one job

Could this issue be related to required package updates? 1914e929
I've tried to reproduce the issue following the cited steps, but the client doesn't throw any error.