Suggestions to making the "10 minute tutorials" more user/reader friendly

The "10 min tutorials" on https://docs.cucumber.io/docs/guides/10-minute-tutorial/ are frustrating to use. It presume much from the readers when it suddenly swift between Command-promt windows and Ruby etc. between steps. It presumes that that the reader would understand "Gemfile", let alone how to use them.
This may be enough information for someone who already know Ruby and Cucumber from the get-go (which would make a tutorial unnecessary by definition), but when you're a new user who only know "enough" to get around, but not to get into every crevasse, then it's a frustrating experience. It feels at times as if you get talk down to for them not knowing what the tutorial, by definition, should have been able to tell me in the first place.
Describe the solution you'd like
Images/Screenshots that shows when and where you are at any given point. To show where you as a reader are when the tutorial-text jump around in the menu. To show which window/command window etc. you're currently in at any given moment.
Describe alternatives you've considered
Bulleting, that clearly states the How and Where to do the how.
Additional context
(See image for reference).
That is just an example of the "installing process". There are plenty more in the text, but for this example, you can see the attatched screenshot for reference.
1: It start with "We’ll start by creating a new directory and an empty Ruby project." (In the same project or as two separate entities? Is the directory specific to the project or a new default? Should the directory be called something specific (like Gemfile) or is that optional?)
Then it goes down to "Create a Gemfile with the following content:" - As a new user and as a ready, the question on ones mind is "Where?" In the directory? In the project file itself? In a new place? Should the Gemfile be given a specific filetype? (like Gemfile.rb?) Should the reader just write-in the versions as they are presented on the sire (Screenshot), or should they use the command-promt to find the right versions? (cucumber -version or other similar?). Does it matter?
Thirdly, we get to "Install Cucumber and prepare the file structure:" - Again, is that in Ruby or in command promt? Is the reader still in the Gemfile? Should this be added at the start of a new [File].feature?
I hope that this shows the issue I personally have had as a new user. The tutorial jump left and right with little explanation or consideration to anyone who supposedly not already possesses enough knowledge to make a tutorial void in the first place. It is called a "10 minutes tutorial", but personally, I have yet to reach the end of the tutorial. This is frustrating, partly due to the aforementioned "jumps", but also when you do manage to follow the tutorial, since when you come across an issue that halt one process, then you don't know why. This is especially an issue when it comes to writing an issue-report or asking for help, because you cannot be sure that you installed things right in the first place.

Hi @BoWunder
In order to have a better understanding of your request, may I ask you for some info which may be personal?
If so:

What is your profile? Are you a developer? A tester? Anything else?
Why are you looking into cucumber-ruby? Are you looking for a testing tool for some ruby development? Or something else? For a new project or an existing one?
Are you familiar with other development languages like JavaScript or Java?

Hi Aurélien,
The request I’m having in concerning the user-friendliness and -understanding in general.
To answer your questions;

I am a tester with a background in UX and manual testing.
I am looking into cucumber because that’s what I was told. As for Ruby, no particular reason besides it having the most sensible tutorial for cucumber so far. The other tutorials on cucumber-io are less user-friendly in comparison.
I am familiar with the existence of other programming languages.

From: Aurélien Reeves @.>
Sent: 30. juni 2021 16:20
To: cucumber/cucumber-ruby @.>
Cc: Sebastian Wunderlich Jensen, Bo @.>; Mention @.>
Subject: Re: [cucumber/cucumber-ruby] Suggestions to making the "10 minute tutorials" more user/reader friendly (#1557)
This mail has been sent from an external source
Hi @BoWunderhttps://github.com/BoWunder
In order to have a better understanding of your request, may I ask you for some info which may be personal?
If so:

What is your profile? Are you a developer? A tester? Anything else?
Why are you looking into cucumber-ruby? Are you looking for a testing tool for some ruby development? Or something else? For a new project or an existing one?
Are you familiar with other development languages like JavaScript or Java?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/cucumber/cucumber-ruby/issues/1557#issuecomment-871447998, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AUSOIFLXOG2AXJKY62HXE5LTVMR2JANCNFSM47SMSQXA.
This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.

Hi Aurélien,
As an addentum to my previous e-mail; The main focus for me is to learn Cucumber and Gherkin. To that end, I an working/tutorialling with Ruby to get some practical experience with it.
Sincerely,
Bo Sebastian Wunderlich Jensen
From: Aurélien Reeves @.>
Sent: 30. juni 2021 16:20
To: cucumber/cucumber-ruby @.>
Cc: Sebastian Wunderlich Jensen, Bo @.>; Mention @.>
Subject: Re: [cucumber/cucumber-ruby] Suggestions to making the "10 minute tutorials" more user/reader friendly (#1557)
This mail has been sent from an external source
Hi @BoWunderhttps://github.com/BoWunder
In order to have a better understanding of your request, may I ask you for some info which may be personal?
If so:

What is your profile? Are you a developer? A tester? Anything else?
Why are you looking into cucumber-ruby? Are you looking for a testing tool for some ruby development? Or something else? For a new project or an existing one?
Are you familiar with other development languages like JavaScript or Java?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/cucumber/cucumber-ruby/issues/1557#issuecomment-871447998, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AUSOIFLXOG2AXJKY62HXE5LTVMR2JANCNFSM47SMSQXA.
This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.

Thanks for your reply.
The 10 minutes tutorials are actually targeting an audience already familiar with the selected development environment - here: ruby.
We may explicitly say so at the beginning of the tutorials.
Cucumber remains a tool which requires some basic development skills, or the support from your development team.
You may not  need to be a professional developer, but with Ruby for example, knowing how to create a new Ruby project with a Gemfile is a prerequisite to going further with Cucumber. And it is the same with all Cucumber implementation.
Also, it is not mandatory, but it would be far more easier to select an implementation of cucumber that match the project your want to test. For example, if the project under test is a ruby application, cucumber-ruby will fit perfectly. If your project is a javascript project, cucumber-js will be a better option.
Last but not least: did you take a look at Cucumber School courses? Maybe you'll find those more comfortable to follow?

In regard to the Cucumber School courses, what is the time-scale? I see that 60+ sessions are the norm, but do a session equate to a day, or an hour?

I think we should state at the top of the tutorial that some prior knowledge is required:

Basic understanding of the Ruby programming language
Basic understanding of the Bundler tool and Gemfile
Some experience using a terminal
Some experience using a text editor

It's beyond the scope of the Cucumber docs to teach readers these things, but we can link to some resources we recommend.

I think that would be a good idea. I recon that https://school.cucumber.io/collections would be one such resource to acquire the necessary knowledge? Or is it likewise expected to have knowledge with Ruby/JavaScripts/Java/C# for these courses?
From: Aslak Hellesøy @.>
Sent: 1. juli 2021 13:20
To: cucumber/cucumber-ruby @.>
Cc: Sebastian Wunderlich Jensen, Bo @.>; Mention @.>
Subject: Re: [cucumber/cucumber-ruby] Suggestions to making the "10 minute tutorials" more user/reader friendly (#1557)
This mail has been sent from an external source
I think we should state at the top of the tutorial that some prior knowledge is required:

Basic understanding of the Ruby programming language
Basic understanding of the Bundler tool and Gemfile
Some experience using a terminal
Some experience using a text editor

It's beyond the scope of the Cucumber docs to teach readers these things, but we can link to some resources we recommend.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/cucumber/cucumber-ruby/issues/1557#issuecomment-872157463, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AUSOIFO2YWLXUVYI2SUT5LDTVRFO5ANCNFSM47SMSQXA.
This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.

In order to use cucumber (in whatever flavour you desire), it is definitely beneficial that you have a basic understanding of how that language structures its projects. I would recommend that for whatever language you are using, you undertake a basic course / read some books / online resources to get familiar with "how" it works.

I think that would be a good idea. I recon that https://school.cucumber.io/collections would be one such resource to acquire the necessary knowledge? Or is it likewise expected to have knowledge with Ruby/JavaScripts/Java/C# for these courses?

The course from Cucumber School may be a little bit more didactic, but I think basic knowledge with at least one of those languages is still a prerequisite.

In regard to the Cucumber School courses, what is the time-scale? I see that 60+ sessions are the norm, but do a session equate to a day, or an hour?

Each lesson last from 3 to 10 minutes


Issues packaging with cx_freeze

I'm currently trying to package an application that uses rapidfuzz using cx_freeze. The packaging is successful but when I try to run the application I get the following error.
implementation requires numpy to be installed
I'm using the process.cdist and I understand numpy is required for the matrix output however I also import numpy at the beginning of the module which calls rapidfuzz without issue so the dependency must be there.
basically what I would like to understand is if there is a way to test which sub modules from numpy are required but are failing to import?
Below is my setup.py
import sys
from cx_Freeze import setup, Executable
from setuptools import find_packages

options = {
    "build_exe": {
        "zip_include_packages": ["*"],
        "zip_exclude_packages": [],
        "build_exe": "dist\\",
        "includes": [
            "numpy",
            "numpy.int16",
            "numpy.int64",
            "_pytest._argcomplete",
            "_pytest._code.code",
            "_pytest._code.source",
            "_pytest._io.saferepr",
            "_pytest._io.terminalwriter",
            "_pytest._io.wcwidth",
            "_pytest._version",
            "_pytest.assertion.rewrite",
            "_pytest.assertion.truncate",
            "_pytest.assertion.util",
            "_pytest.cacheprovider",
            "_pytest.capture",
            "_pytest.compat",
            "_pytest.config.argparsing",
            "_pytest.config.compat",
            "_pytest.config.exceptions",
            "_pytest.config.findpaths",
            "_pytest.debugging",
            "_pytest.deprecated",
            "_pytest.doctest",
            "_pytest.faulthandler",
            "_pytest.fixtures",
            "_pytest.freeze_support",
            "_pytest.helpconfig",
            "_pytest.hookspec",
            "_pytest.junitxml",
            "_pytest.legacypath",
            "_pytest.logging",
            "_pytest.main",
            "_pytest.mark.expression",
            "_pytest.mark.structures",
            "_pytest.monkeypatch",
            "_pytest.nodes",
            "_pytest.nose",
            "_pytest.outcomes",
            "_pytest.pastebin",
            "_pytest.pathlib",
            "_pytest.pytester",
            "_pytest.pytester_assertions",
            "_pytest.python",
            "_pytest.python_api",
            "_pytest.python_path",
            "_pytest.recwarn",
            "_pytest.reports",
            "_pytest.runner",
            "_pytest.scope",
            "_pytest.setuponly",
            "_pytest.setupplan",
            "_pytest.skipping",
            "_pytest.stash",
            "_pytest.stepwise",
            "_pytest.terminal",
            "_pytest.threadexception",
            "_pytest.timing",
            "_pytest.tmpdir",
            "_pytest.unittest",
            "_pytest.unraisableexception",
            "_pytest.warning_types",
            "_pytest.warnings",
            "py._builtin",
            "py._path.local",
            "py._io.capture",
            "py._io.saferepr",
            "py._io.terminalwriter",
            "py._xmlgen",
            "py._error",
            "py._std",
            # builtin files imported by pytest using py.std implicit mechanism
            "argparse",
            "shlex",
            "warnings",
            "types",
            "rapidfuzz.utils_cpp",
            "rapidfuzz.utils_py",
            "rapidfuzz.process_py",
            "rapidfuzz.fuzz_py",
            "rapidfuzz.distance.Hamming_py",
            "rapidfuzz.process_cpp",
            "rapidfuzz.fuzz_cpp",
            "rapidfuzz.distance.Levenshtein_cpp",
            "rapidfuzz.distance.Levenshtein_py",
            "rapidfuzz.string_metric_cpp",
            "rapidfuzz.string_metric_py",
            "jinja2.ext",
            "jinja2",
        ],
        "include_files": ["tests/"],
    }
}

f = open("README.md", "r")
LONG_DESCRIPTION = f.read()
f.close()

setup(
    name="centralized_integrations",
    version="0.1",
    description="xxx",
    long_description=LONG_DESCRIPTION,
    long_description_content_type="text/markdown",
    author="xxx",
    author_email="xxx",
    url="xxx",
    license="BSD 3-Clause License",
    packages=find_packages(exclude=["ez_setup"]),
    options=options,
    include_package_data=True,
    executables=[Executable("cli/main.py", base=None)],
    entry_points="""
        [console_scripts]
        cli = cli.main:main
    """,
)

Since this is an issue with the latest version it should not be closed. There are two things you could do to understand the issue better:

instead of from rapidfuzz.process import cdist use from rapidfuzz.process_cdist_cpp import cdist on the latest version to see the exact error it raises (I should really add this to the error message as well)
try with versions between 2.0.0 and latest which one introduced the issue

ok so I've tracked down the breaking change to version 2.1.1

ok I've found the issue, there's nothing wrong with the codebase but the addition of fallback_import caused cx_freeze's dynamic import loading to break meaning imports needed to be specified manually. In this case the import of rapidfuzz.process_cdist_py and rapidfuzz.process_cdist_cpp. However since the default import error message is implementation requires numpy to be installed this is what was returned even though numpy was available. After specifying the two aforementioned libraries in setup.py everything was successful. I'm going to make a pull request to improve the error message returned to better support edge cases such as this.

This part of the code will need to be changed in one of the next versions again, since there is still an issue with the pure Python fallback. Currently the library would still fail to install if one of the C dependencies fails to install. The current plan is to split the package into two separate packages: rapidfuzz and rapidfuzz-cpp. It will then be possible to install either rapidfuzz or rapidfuzz[speedup]. rapidfuzz[speedup] means it should always install the faster version, while it is an error if it fails to install. rapidfuzz means it should install the faster implementation if possible, but fallback to the slower version if this is not possible. Unfortunately there is no feature like this in Python packaging so the best I can do for this version is to install rapidfuzz-cpp when I know it provides wheels for the platform.
Afterwards I would like to remove this fallback_import behavior again, since it should be better for a user to specify rapidfuzz[speedup] as dependency instead of setting a random environment variable. @Rongronggg9 what is your take on this, since your likely the only user of this environment variable. Would this be sufficient?
In addition it would probably make sense to change the cdist import to something like:
except ImportError as e:
    def cdist(*args, **kwargs):
        raise NotImplementedError() from e

Afterwards I would like to remove this fallback_import behavior again, since it should be better for a user to specify rapidfuzz[speedup] as dependency instead of setting a random environment variable.

I am not opposed to this. But I doubt if pure-Python rapidfuzz still fits its name... It is a huge breaking change. If some someone never specifies a specific version of rapidfuzz in their dependencies, after they set up a new environment, a "rapid" dependency slows things down...

after they set up a new environment, a "rapid" dependency slows things down...

On platforms like e.g. for Linux x86_64 I know that there is a wheel for rapidfuzz-cpp and so I will always install it. So this only affects more niche platforms, where no official wheel standard exists like e.g. open bsd. However currently the build requires e.g. oldest-supported-numpy and I do not know whether pip install oldest-supported-numpy even works on open bsd.
I am open to different suggestions though.
The general goal with this split are:

currently the installation fails when the installation of build dependencies fails. Even though those build dependencies fails (cmake, ninja, oldest-supported-numpy).
make the forced installation of the faster version simpler

My preferred solution would be something along the lines of:
optional_install_required = ["rapidfuzz-cpp"]

which would try to install the faster implementation but ignore any installation failure. Maybe something like https://stackoverflow.com/a/53568049/11335032 would work better.

OK then.
There is still something that can be improved. Practically speaking, speedup is not a good extra_require name since the only difference it makes is to throw an error if fails to install the cpp implementation - it itself does not speed up anything. Maybe ensure_speed or ensure_cpp is better.
Pip comes with no "optional but default dependency" support, and workarounds in https://stackoverflow.com/a/53568049 are all dirty hacks and should not be taken into production - in production, all dependencies should be installed at once since: 1) pip can not ensure parallel or nested pip runs won't break anything, 2) pip would not fail if the current installation breaks the dependencies relation of previously installed packages. Though both the package and its "optional but default dependency" are in your control, the dirty-hacking behavior would probably not break anything, I am still not so in favor of this workaround.

Yes you are probably right. I really hope pip adds "optional but default dependency" support at some point. The best we can do without this hack is to ensure the faster implementation for major platforms, which have official wheel support and on other platforms rely on users either using something like ensure_cpp or installing from a different package manager which provides them with wheels / the dependency. (e.g. packages listet here https://pkgs.org/search/?q=rapidfuzz could add a dependency on python-rapidfuzz-cpp)

One solution that should work (but cause quite a bit of extra work for me), would be the addition of optional packages like e.g. optional-cmake which would just install an empty package if the installation fails. This would be reasonably simple for the cmake and ninja package, but would be a major pain with the numpy dependency.
I am generally pretty unhappy with the numpy dependency and still contemplating, whether I should write my own matrix implementation that a user can convert using np.asarray in v3.0.0

This should produce a more obvious error now


Mass Unholy Frenzy applies the Flame Strike debuff

the debuff lasts 0.001 second (thats the same for a number of spells currently used , il assume this fixed


vdk control service installation bug

Describe the bug
The bug is detected when installing VDK control service on a host.
Steps To Reproduce
Steps to reproduce the behavior:

Go to command line/ terminal in linux
Run the following commands to ensure that all prerequisites (vdk SDK, kind, helm, and docker) have been installed properly. If any of them is not installed, install each one individually:
vdk version
kind version
docker version
helm version

The output of the commands above are as follows:

After successfully installing kind, helm, and docker on Ubuntu Jammy,

Then run vdk server --install
server log is attached!

Expected behavior
What we expected to happend after running 'vdk server -i' is to have VDK Control Service properly installed on the host. This is a prerequisite step for ingestion in the examples like incremental-ingest-from-db-example.
Screenshots

Version:

OS: Windows 11, and Ubuntu Jammy 22.04
Version: 0.3.1190994517

Additional context
server.log

@ehsan-farzadnia  can you please check that the kubernetes cluster is in a healthy state?
IMO the simplest way to do this would be to download lens.
Use it to check that you can connect to the k8s cluster and that some pods are running OK.

@murphp15 I tried a lot but I couldn't create a kind cluster manually (error is attached)

Also, my docker connection

What is the problem?

there error is saying you haven't created kind-cluster-config.yaml.
Can you create that and try again.

Hi Paul,
Please find attached my screenshot from the Linux terminal runnig the command. I did all the steps you proposed however a new error caused as I cannot fix it! Can you help me?

Thank you
Ehsan

Hi @murphp15,
Please find attached my screenshot from the Linux terminal runnig the command. I did all the steps you proposed however a new error caused as I cannot fix it! Can you help me?

Thank you
Ehsan

can you try run that docker pull command outside of the install
so
docker pull kindest/node:v1.20.15

Hi Paul,
I tried it out and manually attempted to pull that node but no outcome!

E

can you run the single failed command and see does it work?

dokcer command is successfully pulled

Then, after running "vdk server -i", again the same error message appears "faild to create cluster error message" !

says "kubelet is not running"

I checked it out to see if kubelet it running or not with this command "systemctl status kubelet"

We will look at this this sprint.

@ehsan-farzadnia  we are actively looking into this and should have a solution this week.

@murphp15 I get failure while installing kind Control Service in kind cluster ... as attached. Could you help me to fix it?


Add an eye icon to see the Password

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
By adding the eye icon in the password field will help the users to verify that they are correctly entering the password or not. This feature will provide the better user experience.
Use Case
By having the feature of seeing what is entered in the password will enable the user to have the better user experience
Benefits
No response
Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

Please assign this issue to me . i am very eager in working on this issue.

hey please assign me this issue under gssoc24

Hey, can you please assign me this issue?

Please Assign Issur To Me

Please assign this issue to me . i am very eager in working on this issue.

Hello @RithikaSundaram , Go for it
All the Best

please assign this issue to me

Trisha-tech
@Trisha-tech this issue not solved not till know assigned this work to me


Should not insert spans into tables even if there is white space

Eg. this test fails (note the space between tbody and tr; a new line has the same effect):
    it('should not insert spans into tables even if there is white space', function() {
        var htmlInput = '

x	3

';

        var reactComponent = parser.parse(htmlInput);
        var reactHtml = ReactDOMServer.renderToStaticMarkup(reactComponent);

        assert.equal(reactHtml, htmlInput);
    });

with the warning:
Error: Warning: validateDOMNesting(...):  cannot appear as a child of
. See tbody > span.

@RacingTadpole That doesn't seem to be an issue anymore in the latest master. I'm closing this for now, but please feel free to re-open if it still occurs for you.

Thanks @mikenikles. I agree, this test passes on the current master (1.0.0).
Interestingly it also produces a warning:
Warning: validateDOMNesting(...):  cannot appear as a child of
. See tbody > span.
...so the issue is still real for me. But I'm happy to delegate the problem to a white-space-removing library, if one exists - as suggested by @aknuds1 in #31.

@RacingTadpole Aha, I see the warning now, except it doesn't mention  for me, but instead 'Whitespace text nodes'. I'm using React 15.3.2.
Warning: validateDOMNesting(...): Whitespace text nodes cannot appear as a child of
. Make sure you don't have any extra whitespace between tags on each line of your source code. See table > #text.

I guess this is a real concern when translating to React then.

How do you guys think this should be addressed? Is the best solution to avoid creating whitespace text nodes within tables as React is warning of here?

How do you guys think this should be addressed? Is the best solution to avoid creating whitespace text nodes within tables as React is warning of here?

@alexgilleran or @kring - do either of you guys have an opinion on how/whether html-to-react should filter whitespace?

I think the problem is as such:

Within HTML there's really two kinds of white space - meaningless white space that goes in between tags to make the HTML more readable and actual text whitespace that goes between words
HTML2React is currently interpreting all white space as text whitespace
React thinks this means you're putting text in places it shouldn't be (like between
 and
. It used to render this as  which was bad but the browser could ignore it, now it renders it as <-- reactid etc which is better but still not perfect.

The only really neat way I can think of to solve this is to make it so that whitespace is removed except when the text is an immediate child of a tag that supports it, like
, ,
 etc.

Could someone come up with test cases for the desired behaviour? @AlexGilleran?


Why did you remove fetaures in 3.92 update?

https://github.com/ZTzTopia/GTProxy/commit/eac90503e273860339009692ee972229aab6666c

i want to restore that feature again but i don't have time for that 😞


Fix the bug related to APA-31469. Quote field names with reserved key…

…words in PrestoSQL

this is a duplicate PR. dropping the request.


notifs: Add snoozable banner for notifs-soon-to-expire

This is stacked on #5812. I'll post a screenshot soon.

The snooze period is a week, and the "Learn more" button opens https://zulip.com/help/self-hosted-billing#upgrades-for-legacy-customers , like the warnings in #5812.

Thanks for the review! Revision pushed.

Thanks! The code all now looks good; ready to merge pending any feedback from @alya on the UI.

Works for me! Thinking about this experience, I'm going to add a bit of an intro to https://zulip.com/help/self-hosted-billing#upgrades-for-legacy-customers so that it explains more clearly that we made a change.
@timabbott any additional thoughts here?

Help center PR: https://github.com/zulip/zulip/pull/28688

Let's use something like this for the language:

{realm_name} is scheduled to switch to a plan that does not include mobile push notifications on {date}.

(I'm not sure whether a link words in this context). I think that makes more clear what the exact situation is -- one could imagine reading the "will be disabled" and at first  assuming some other weird possibility about the cause (E.g. your organization got a spam complaint or something). Obviously the link will clarify, but I think the initial reaction is important,

Thanks for the reviews! Revision pushed, with:

That new text: https://github.com/zulip/zulip-mobile/pull/5814#issuecomment-1908771732
Admins/owners are notified at T-minus 15 days; others are notified at T-minus 10 days
Snooze period is 8 days instead of 7

(These last two were discussed on CZO.)

Could you post an updated screenshot, please?

Thanks! The code changes look good. Ready to merge pending an updated screenshot and any remaining UX/product feedback on that.

The link on "plan", where present, is a small touch target, and in the case of the "Settings" and "Notifications" screens, it appears on a surface that has a different behavior on touch. But I checked manually and it is possible to get the touch response on "plan" if you're precise about where your finger goes.
When you tap the link on "plan", it opens https://zulip.com/plans/#self-hosted .
As a reminder, when you tap any of these, it opens https://zulip.com/help/self-hosted-billing#upgrades-for-legacy-customers :

"Details" on the dialog on the "Pick account" screen
"Learn more" on the banner on the home screen
The relevant row on the "Notifications" screen

Revision pushed.

Revision pushed.

Thanks! Looks good; merging.


Added support for indexing map datatypes in scan finding-aids.

During processing of EADs and linked mets-files (via the 'dao' link), genreform fields are added so that they can be indexed together with the other scan metadata.

Prima


PERMISSIONS.IOS.PHOTO_LIBRARY_ADD_ONLY returns RESULTS.UNAVAILABLE

Summary
Running V3.0.0-beta.1
Trying to check and request PhotoLibrary AddOnly permission.  Instead, that permission is shown as unavailable.
Notes:

added NSPhotoLibraryAddUsageDescription to info.plist
added pod 'Permission-PhotoLibraryAddOnly', :path => "#{permissions_path}/PhotoLibraryAddOnly" to the podfile
Permission-PhotoLibraryAddOnly shows up in Pods=>Development Pods.
Permission-PhotoLibrary works fine

Environment info
react-native info output:
System:
OS: macOS 11.0.1
CPU: (8) x64 Intel(R) Core(TM) i7-1068NG7 CPU @ 2.30GHz
Memory: 519.23 MB / 32.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 14.9.0 - /usr/local/bin/node
Yarn: 1.22.5 - /usr/local/bin/yarn
npm: 6.14.8 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.10.0 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 14.2, DriverKit 20.0, macOS 11.0, tvOS 14.2, watchOS 7.1
Android SDK: Not Found
IDEs:
Android Studio: 3.2 AI-181.55<IP_ADDRESS>56338
Xcode: 12.2/12B45b - /usr/bin/xcodebuild
Languages:
Java: 9.0.4 - /usr/bin/javac
Python: 2.7.16 - /usr/bin/python
npmPackages:
@react-native-community/cli: ^4.12.0 => 4.13.0
react: 16.13.1 => 16.13.1
react-native: 0.63.2 => 0.63.2
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
I am testing on an iPhoneX with IOS 14.1.
Library version: 3.0.0-beta.1
Steps to reproduce
check(PERMISSIONS.IOS.PHOTO_LIBRARY_ADD_ONLY)
.then((result) => {
Alert(result);
}
Describe what you expected to happen:
result === RESULTS.DENIED  // at least the first time
Instead, result === RESULTS.UNAVAILABLE

Hi 👋 There's two options:

Parental control is enabled on your device, PHAuthorizationStatusRestricted si therefore returned (= unavailable)
The permission handler is not installed correctly (see this line)

Did you installed it at the same time as Photo-Library? Or later?
Xcode really struggle with Cocoapods and caching. Did you tried closing it, deleting your DerivedData, rebuild again? (follow this)

Parental control is enabled on your device, PHAuthorizationStatusRestricted is therefore returned (= unavailable)

I assume since PERMISSIONS.IOS.PHOTO_LIBRARY works, this is not the case.

The permission handler is not correctly installed (see this line)

Wouldn't that also affect PERMISSIONS.IOS.PHOTO_LIBRARY?

Did you installed it at the same time as Photo-Library? Or later?

Just tried again:

Deleted Derived data
Deleted Pods
Deleted podfile.lock
Deleted node_modules
Cleaned build folder (in Xcode)

Check shows PERMISSIONS.IOS.PHOTO_LIBRARY_ADD_ONLY as UNAVAILABLE (PERMISSIONS.IOS.PHOTO_LIBRARY shows as DENIED, as expected)
Note that I made sure NOT to set PERMISSIONS.IOS.PHOTO_LIBRARY, in case the two permissions are mutually-exclusive.

This as nothing to do with PERMISSIONS.IOS.PHOTO_LIBRARY. But if you installed one then the other, the cache might be in a state where the first one header is present and not the second one. If you install them both at once, this case become impossible.
Which Xcode version are you using?

This has nothing to do with PERMISSIONS.IOS.PHOTO_LIBRARY. But if you installed one then the other, the cache might be in a state where the first one header is present and not the second one. If you install them both at once, this case become impossible.

I was running with PERMISSIONS.IOS.PHOTO_LIBRARY first, without PERMISSIONS.IOS.PHOTO_LIBRARY_ADD_ONLY.  I then added the code for PERMISSIONS.IOS.PHOTO_LIBRARY_ADD_ONLY to info.plist and Podfile and rebuilt everything, if that is what you are asking.  Did I miss a step?

Which Xcode version are you using? Do you run your app though Xcode or with react-native run-ios?

Xcode 12.2 and am running the app through Xcode.

I just tried running in the Simulator with multiple devices, same result (so it is not some issue with iPhone X I have been using)

I am running RN 63.2.  I'll upgraded to 63.3 and see if that fixes it.

I thought I might have found the cause, Permission-PhotoLibraryAddOnly was not in project.pbxproj.  However, adding it and upgrading to RN63.3 did not solve the issue.

I installed it on a clean project, could do a check and a request with only a small, unrelated hiccup: The usage description key is no correct (used for the alert in dev): https://github.com/zoontek/react-native-permissions/blob/3.0.0/ios/PhotoLibraryAddOnly/RNPermissionHandlerPhotoLibraryAddOnly.m#L8
I will fix that.
Did you tried the example project?

Did you tried the example project?

It works in a sample project.
So the problem was definitely adding the PHOTO_LIBRARY_ADD_ONLY after the other permissions had already been installed.  Is there a trick to getting that to work?  I tried uninstalling react-native-permissions completely and reinstalling, but that didn't work.
Note that this is the first component I've worked with where you have multiple Pods that can be installed at different times.

So the problem was definitely adding the PHOTO_LIBRARY_ADD_ONLY after the other permissions had already been installed.

Just duplicated this in my sample project.  I added PERMISSIONS.IOS.CONTACTS to the Podfile and to info.plist.  CONTACTS shows up as unavailable.

Running npx react-native-clean-project (which I saw in an issue solved a similar problem) fixed it in my sample project.  Hopefully, it will work in my actual project.

Running npx react-native-clean-project (which I saw in an issue solved a similar problem) fixed it in my sample project. Hopefully, it will work in my actual project.

Worked for my main project, tool.

I faced this issue at RN 0.69 and react-native-permissions v5.0.0
the https://github.com/zoontek/react-native-permissions/issues/540#issuecomment-729995395 worked for me, @zoontek mb you should add this solution into troubleshooting section of readme


Docker Installation problem

I have downloaded the project, created the .env and when I try to access it gives me this error:
helpy_1     | /home/helpyuser is not a directory.
helpy_1     | Bundler will use `/tmp/bundler/home/unknown' as your home directory temporarily.
I see the same problem before:
https://github.com/helpyio/helpy/issues/1264

I think it just take time for the first time to open. I have the same logs and I got 502 for the first 5 minutes.

Thanks!


Create sssas

Collaborator cannot find remote user mapping for pull request creator, review created by system administrator

Collaborator: Review for this pull request was created. Link to review


Update @sqltools/types package

In PR #938 I am allowing fetchDatabases to pass the connection item, so that the query can adapt to its context. This PR updates the @sqltools/types package so that PR can build without errors.

@mtxr please approve, merge and publish this to unblock #938

published


patch(update_bundle.py): Add architecture check to ensure amd64 only

Related to https://warthogs.atlassian.net/browse/DPE-4627, see successful test run on https://github.com/canonical/postgresql-bundle/pull/98

BTW 2 things:

Once we have ARM bundles we should probably make this workflow receive the desired arch as a parameter instead of having amd64 hardcoded. Known follow-up.
Once this is merged, I'll push a new tag (possibly v16.3.1?) to update the workflow over on postgresql-bundle

BTW 2 things:

Once we have ARM bundles we should probably make this workflow receive the desired arch as a parameter instead of having amd64 hardcoded. Known follow-up.
Once this is merged, I'll push a new tag (possibly v16.3.1?) to update the workflow over on postgresql-bundle and postgresql-k8s-bundle

To answer this we should understand the way we will store yaml's for different architectures.


[qa] cleanup runflake8 and runisort

Resolving issue https://github.com/openwisp/openwisp-users/issues/59
I moved command line options to setup.cfg file

Coverage remained the same at 96.795% when pulling a18b6f41cea4edc48799ddab509513031b6db639 on Rishabh2801:master into cf5cd64f7d3c3515fcd0fc1f23077620b5a85964 on openwisp:master.

Coverage remained the same at 96.795% when pulling a18b6f41cea4edc48799ddab509513031b6db639 on Rishabh2801:master into cf5cd64f7d3c3515fcd0fc1f23077620b5a85964 on openwisp:master.

Coverage remained the same at 96.795% when pulling a18b6f41cea4edc48799ddab509513031b6db639 on Rishabh2801:master into cf5cd64f7d3c3515fcd0fc1f23077620b5a85964 on openwisp:master.

Coverage remained the same at 96.795% when pulling a18b6f41cea4edc48799ddab509513031b6db639 on Rishabh2801:master into cf5cd64f7d3c3515fcd0fc1f23077620b5a85964 on openwisp:master.


Escape whitespace in build script

I'm running into an issue when trying to use the build script on macOS.
My home folder is located on a non-standard location and the drives name includes whitespace.
$ echo $PWD
/Volumes/Storage SSD/Users/thetw/Desktop/sharp-libvips

When i try to run the build script, every command that involves the unescaped absolute path to the build folder results in errors like:
mkdir: /Volumes/Storage: Permission denied
mkdir: SSD/Users/thetw/Desktop/sharp-libvips/build: No such file or directory

As you can see the unescaped path got split at the whitespace character which obviously creates invalid paths.
Do you have a clue how we could fix that? The only way that came to my mind so far is to properly escape all occurrences of the path invocations in the build script with " or '... or do i miss something?

Hi, I'd be happy to accept a PR that add quotes around filesystem paths.
As a possible workaround for now, you might be able to create a symlink without a space.

Hi, I'd be happy to accept a PR that add quotes around filesystem paths.
As a possible workaround for now, you might be able to create a symlink without a space.


Create issue template for bug report

Added the issue template for bug report.
closes issue number #101

Please check this PR @gaurav-verma01
thanks

@Gaurav-Verma07 check this out once !!


An external combat notifier that can be picked up by mobile clients

At Kahldar's request.
This would be e-mail, Tweeter, FB, something. This is not scheduled and may not be implemented at all. Will research feasibility after V2.

Yeah I don't think this is feasible. And if it is, I doubt Pardus Sweetener is the place to implement this. No changes.


Rewrite as Symfony bundle

GitHub Issue: https://github.com/Islandora-CLAW/CLAW/issues/1224
What does this Pull Request do?
Rewrites the existing Crayfish-Commons as a Symfony bundle.
What's new?

YamlServiceProvider is removed, symfony handles configuration differently.

IslandoraServiceProvider is removed, this work is done in CrayfishCommonsExtension

ApixMiddleware becomes an EventSubscriber

Added a UserProvider for the JWTs

Does this change require documentation to be updated? yes

Does this change/add any new dependencies? dependencies changed, as did the composer.lock

Does this change require any other modifications to be made to the repository (ie. Regeneration activity, etc.)? no

Could this change impact execution of existing code? probably

How should this be tested?
A subsequent PR is coming for Houdini.
Then I'll create a PR to pull this into a playbook and we can test it there.
Interested parties
Tag (@ mention) interested parties or, if unsure, @Islandora-CLAW/committers

See https://github.com/Islandora-CLAW/Crayfish/pull/73#issuecomment-520957388


Save to file system or application resources

The Ktor plugin "Swagger UI" notes:

This method tries to look up the OpenAPI specification in the application resources. Otherwise, it tries to read the OpenAPI specification from the file system using java.io.File.

Unless Kompendium saves the specification to the file system or application resources, there is no way to use the Swagger UI plugin for Ktor.

i'm not familiar with this plugin, is there a specific advantage over just using the kompendium helper route that serves swagger ui?

I didn't realise Kompendium offered its own helper route that serves the swagger ui at first, this might be the case here as well
Both OpenAPI and Swagger KTor plugins expect a file at startup (AFAIK), whereas kompendium does it runtime, so I don't really think they're compatible frameworks


Make 720p the default

16:9 is more popular than 4:3, so it would be good if that was the default.

The new HDMI2USB-misoc-firmware does this.

Closing this as the HDMI2USB-jahanzeb-firmware is no longer under development.
All active development is now on the HDMI2USB-misoc-firmware which supports both the Atlys and Opsis boards and has loads of other new features!


Doxygen warnings

In GitLab by @ksiero on Oct 12, 2020, 15:18
When building documentation, there are some warnings: unable to resolve reference to and indent problems.

In GitLab by @ksiero on Oct 12, 2020, 15:20
mentioned in commit 769c4198fa1f0ffa708b98e61b5c647280dcab60


UI-Scroll how to make the first record appear?

in my application, assume there are 100 records, when displays data the first item is hidden, and we only can see it when scroll up. the first record should display at the beginning by default, is there anyway to implement this?
here is the screenshot of  demo sample

actually there is an item of 0: aa: 00 on the top of 1: aa: 01.

Actual code base of ui-scroll is in https://github.com/Hill30/NGScroller. Please re-submit your issue over there if needed.


Streamline SPIFFS upload

Hi, I wonder if there is a usable way to optimize the uploadfs target. For esp12e it generates a 3MB file regardless of the data size (usually it's a small json config file and not much more, so mostly padded space).
E.g. guys at Smartjs.io have a good approach of exposing SPIFFS via a WebDAV and being able to add/remove files interactively. I'm not advocating adding this layer, but rather thinking of ways to create a smaller FS image if we know it's gonna be small. And save 5 minutes of waiting for upload to finish.

I understand the custom FS images somewhat. The issue is more about defaults. 3MB takes a lot of time and is somehow a default, bad user experience. Add a few more examples of command line invocation in the docs?

How about to use smaller SPIFFS size? http://docs.platformio.org/en/latest/platforms/espressif.html#custom-flash-size

Yes, but I don't like our current defaults:

Use 1MB fs by default - I have hard time imagining why anyone would start with 3MB images and wait 6 minutes on every upload (1MB takes 2 minutes)
An example from http://docs.platformio.org/en/latest/platforms/espressif.html#custom-flash-size is not very useful as it specifies a 3MB image, which is already a default, so it doesn't change anything. Update this example to use a 1MB image to be more useful.

I guess due to the design of esp12e we only have 1MB or 3MB options, but I'd be happy to be proven wrong.

BTW, for some reason, 1MB option causes my file reading code to fail - it can't find the file? The only change was to specify this in `platformio.ini':
build_flags=-Wl,-Tesp8266.flash.4m1m.ld

Please try http://docs.platformio.org/en/latest/installation.html#d-development-version

Ivan, I noticed that switching the FS image size requires one to run a clean target, otherwise it gets corrupted or something. Not sure if this can be detected and forced from a config currently, but maybe we can add it to the docs as a best practice/warning? I wasted lots of time debugging that.
Will test out the dev build by tomorrow and report.

If you edit platformio.ini, PlatformIO automatically cleanups .pioenvs directory. Also, uploadsf should force to rebuild SPIFFS image. See https://github.com/platformio/platformio/blob/develop/platformio/builder/scripts/espressif.py#L299
Looks, like this is another problem. I'll wait any news from you as for this issue.

I reopen this issue until you test it.

Thank you. I have tested the latest dev version of the platform. The defaults are now 1MB for a SPIFF, and FS image rebuild works correctly when going between sizes (tested cycling it up and down several times).

@aperepel thanks for the report!


chore: displaying dockerfile before building

Hopefully this will help us see what the failure is when trying to build the containers during plugin update

Can we revert this? I feel like it makes it more difficult to read the test output.


Replace deprecated package test classifier SS -> ST

See TriBITS documentation for reference.

Codecov Report

Merging #386 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #386   +/-   ##
=======================================
  Coverage   97.96%   97.96%
=======================================
  Files          86       86
  Lines        5960     5960
=======================================
  Hits         5839     5839
  Misses        121      121

Continue to review full report at Codecov.

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


Add myetherwallel.com to blacklist

Add myetherwallel.com to blacklist, a most recent link being distributed.

Added yesterday in https://github.com/409H/EtherAddressLookup/pull/37 by hadojae


Feature request - weather notifications on PWA

Hi Andrew,
Do you know if it's possible to provide periodic notifications about weather updates for PWA installations of Ocula?
Currently using:

Ocula installed using Brave (Version 1.19.86 Chromium: 88.0.4324.96 (Official Build) (64-bit)) on Windows 10.
Ocula installed on iOS with Safari.

Hope the new is off to a good start for you.
Best,
Kerry

Hi @kerry-tarrant
This is something I am keen to implement but unfortunately OpenWeatherMap doesn't have realtime updates for their free services. The only way to do it currently would be to poll their API at set intervals which would rapidly breach my quota and increase the cost to run Ocula.
Hopefully I'll work something out soon as to how to do this without it being a major expense :)

Hi @kerry-tarrant
This is something I am keen to implement but unfortunately OpenWeatherMap doesn't have realtime updates for their free services. The only way to do it currently would be to poll their API at set intervals which would rapidly breach my quota and increase the cost to run Ocula.
Hopefully I'll work something out soon as to how to do this without it being a major expense :)


changeDpiDataUrl() sometimes returns invalid PNGs.

When I pass the attached PNG image in changeDpiDataUrl(), it returns an invalid PNG.  It's easy to reproduce:
var res = changeDpiDataUrl(attached_png, 300);

'res' will be a badly formed PNG image.
I don't fully understand the code, but it looks like detectPhysChunkFromDataUrl() cannot find what it's looking for, so it returns -1.  The calling code checks if the return value is truthy; -1 is, so the header length calculation is wrong.
base64_png.txt

Hi Remi,
can i ask you how did you generate that base64?
Does it comes from a html5 Canvas or some other source?

Sorry, I should have included a full repro.  Attached is a standalone page that shows the problem.  'bundle.js' is the simple repro, bundle_compiled. is just bundle.js run through webpack.
The repro creates one HTML5 canvas and two images.  The first image.src is set to the result of canvas.toDataURL(). The second image.src is set to the result of changeDpiDataUrl( canvas.toDataURL(), 300).
For me, the second image shows a broken image icon.  I tried this in the latest Chrome & Firefox on Windows 7.  I get the same result regardless of DPI setting passed to changeDpiDataUrl, and regardless of canvas content.
repro.zip

Ok thanks for the test case. I needed just to know if it was a canvas generated png or generated from other softwares (photoshop, or similars, or downloaded from the interet).
I ll look into it asap. I have seen your fix, i want just to verify why it fails and why i wrote that code originally.

I doubt my fix is ideal, but it solves this particular problem, and might point to a better fix.  Thanks for looking into it!


Sockeye 2 Interleaved Multi-head Attention Operators

Replaced batched dot product in multi-head attention with interleaved_matmul attention operators to improve performance. Also changes the batch-major data to time-major format while in the model to comply with the new operator requirements
Pull Request Checklist

[x] Changes are complete (if posting work-in-progress code, prefix your pull request title with '[WIP]'
until you can check this box.
[ ] Unit tests pass (pytest)
[x] Were system tests modified? If so did you run these at least 5 times to account for the variation across runs?
[ ] System tests pass (pytest test/system)
[ ] Passed code style checking (./style-check.sh)
[x] You have considered writing a test
[ ] Updated major/minor version in sockeye/__init__.py. Major version bump if this is a backwards incompatible change.
[ ] Updated CHANGELOG.md

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Thanks! This should be mergable once MXNet 1.7 is out, right? Would you expect perplexity scores for training to be exactly the same with and without this change?

Hm, depending on what you're testing, my best guess is that the weights may be initialized slightly differently by the xavier initializer since the key and value weights are now a single array. Could you clarify what you mean by undoing the merged input projections (i.e. what changes did you make to do that)? In my own tests I didn't observe any more negative impact in training after my fix, but I can check it again to make sure.

Here's a commit that still gives me different perplexity values when compared to sockeye_2 branch: https://github.com/awslabs/sockeye/commit/1676d6a5a79615d56387f4d2f206d9f6d6877d68
I might have missed something though.

Looking at the changes in your commit, it looks like the discrepancy is likely still there because of the way that you've combined the weights together. The interleaved_matmul_* ops don't assume that the key and value projections are simply concatenated, but rather are striped together over the head dimension (hence the name "interleaved").
You can reference the code changes in sockeye/inference.py from 6b25ad550a07027c5531e359c35cbb3a0f680eef to see how the weights would need to be combined.

Looking at the changes in your commit, it looks like the discrepancy is likely still there because of the way that you've combined the weights together. The interleaved_matmul_* ops don't assume that the key and value projections are simply concatenated, but rather are striped together over the head dimension (hence the name "interleaved").
You can reference the code changes in sockeye/inference.py from 6b25ad5 to see how the weights would need to be combined.

Right, thanks for the clarification. I will try interleaving them instead of concatenating.

I tried testing the perplexity values myself, as it turns out since the model now transposes the batch and time dimensions, not only do the attention input arrays need to be interleaved together if the keys and values are initialized separately, but also that they need to be transposed for the dropout and layer norms to produce the same results. Accounting for all of this, I'm observing that the array values largely align with the main sockeye_2 branch.
There still is a small difference in perplexity values in the system test, and that's likely due to a ~1e-8 difference in outputs from the attention operator itself, since I believe its implementation uses a different GEMM than batch_dot does. I don't believe that this should result in any significant issue though.
I've pushed the changes I've made to run the tests onto a branch from my fork here https://github.com/blchu/sockeye/commits/sockeye_2_test_interleaved_perplex

Now that we have a MXNet 1.7 branch, we can update/review this PR and merge it into that branch so it will be immediately usable for anyone who wants to manually install a MXNet pre-release.  When MXNet 1.7 wheels are available, mx17 can merge into master and the improvements in this PR will be included automatically.

It looks like there are some merge conflicts between this PR and the SSRU updates.  @barbaradarques and @blchu, as the experts on these parts of the code, can you help us find the best way to resolve the conflicts?

Looking over the SSRU PR, there is significant overlap since both modify the decoder autoregressive layer. Most of the conflicts should be relatively straightforward to resolve, but one of my changes transposes the batch and time dimensions for the duration of the model to improve attention performance. @barbaradarques is that compatible with the SSRU layer, or can be made compatible? Otherwise I'll look for some workarounds.

Actually I think there's some positive synergy between the changes as the SSRU code currently temporarily transposes to time major in order to use the foreach operator: https://github.com/awslabs/sockeye/blob/master/sockeye/layers.py#L893
When merging we'd just to make sure to remove that transpose in favor your transpose for the model.

Hi @blchu , as @tdomhan mentioned, the transposition shouldn't be a problem for SSRU layers. On top of removing the internal transpose() operations, you'd also need update get_state_shape(), but that should be it.

We've officially updated Sockeye to MXNet 1.7, so we can merge this into master as soon as the conflicts are resolved.

I'm currently working on resolving the merge conflicts. Right now I have all tests passing; however, I'm seeing some strange performance and perplexity numbers in training, so I'm trying to get that resolved.

@blchu, feel free to commit your WIP, maybe we can help figuring out the inconsistencies.

With further testing, I did notice that while perplexity was noticeable worse during training than what I had measured before, this is also the case with the mx17 branch without any of the changes from the PR, so it may be due to something entirely unrelated. The BLEU scores at each training checkpoint were no different.
There's still an issue with the inference during a training checkpoint using an SSRU decoder, though I think I've narrowed the cause to a different state shape than in pure inference ([batch, dim] vs the expected [time, batch, dim]).

thanks @blchu though I think something went wrong with the merge/conflict resolution (the PR shows 49 changed files).

Ah hm, that might have been because the way I did the merge and the fact that I was originally building off of the sockeye_2 branch. I think the files changed is using a diff off of that branch, and not master perhaps? I'm not entirely sure how to fix that.

Hi @blchu , since a lot has changed since the original fork, it might help if you create a new branch from master and copy+paste on top of it the changes of those 6 files you actually changed.

I've just created a new PR by cherry-picking my commits to a new branch off of master, since I can't modify the source branch of this PR. The new PR can be seen here https://github.com/awslabs/sockeye/pull/884.


Actions docker

This is a github action that will build wasmd in amd64 + arm64

Ping @faddat

Closing this for now. Feel free to open the PR again when you have time. You can also find us on discord to follow up on the discussion. Thanks 🌻


Many2many relationship, advanced Where conditions

Implemented Many2many realtionship so that the related name .all() and the reverse related name .all() works, with Django 1.4 to 1.8

Speed up tests. The connection to SFDC is not created until necessary, because some tests don't require the connection at all.

closes #103, #124

Wow! Great stuff.

I'm having some issues with the tests on Travis, but they all appear related to the fact that I ended up running two builds at once because of two merges right in a row. I'll fix the tests ASAP.

The object django_Test__c is the model example.models.Test. It is really a bug that the test is not skipped. I recommend to create soon if you want to test relationships between custom and builtin objects (in the future, currently it is skipped because wuold fail) It is currently the only custom object that is really tested on SFDC. (custom object ChargentOrders__ChargentOrder__c is "mocked")

Thanks for your help. Tests are passing fine on the Travis build now.


Contoured Surfaces

Hopefully ready now! (see #198)
I was about to send a PR with the edgeFilter bits removed and a comment on how there were still occasional holes in the surface, turns out I'd made a big error in how I loop over triangles (see 63c1bb0). This version has hole-free surfaces (I hope) and I've reinstated edgeFilter to reduce unnecessary duplicated lines (which might make a small difference on huge surfaces)

Thanks @fredludlow this is great! I could have a look at enabling this for surfaces generated from volumes or do you plan to do that?

That'd be great if you could! (It occurred to me it should be possible for e.g. electron density maps but I haven't looked at it).


When scroll down from NPM to Preview in setting page, it automatically jump up to Extensions

Bug Description:

Steps to Reproduce:

Open Setting page and scroll down in the right.
When scroll down from NPM to Preview, it automatically jump up to Extensions.

Additional Information

Operating System:

Theia Version:

I uninstall and install extentions one by one. It seems after installed Project Manager , this issue happends.

I uninstall and install extentions one by one. It seems after installed Project Manager , this issue happends.

Thank you for the details. I installed the project manager, but for me it works fine, i.e. I cannot reproduce this. I am on Linux, though and on Theia 1.54

After updated to Theia 1.54.0, it has been solved.


Replacement for deprecated fields AzureBlobContainer and AzureBlobToken

Hello,
I am looking to automate some eDiscovery exports but I noticed that these fields: AzureBlobContainer and AzureBlobToken are both deprecated and there isn't any information about their replacements.
Please provide info for how you can programmatically automate eDiscovery exports to Azure Blobs.

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

ID: 6c1ea8e5-de45-a9da-5b79-f810e3deed5a
Version Independent ID: 89ef0ca8-64cb-e75f-5fda-7b6deb55d031
Content: ediscoveryReviewSet: export - Microsoft Graph beta
Content Source: api-reference/beta/api/security-ediscoveryreviewset-export.md
Product: ediscovery
Technology: microsoft-graph
GitHub Login: @SeunginLyu
Microsoft Alias: MSGraphDocsVteam

There are no replacements for AzureBlobContainer and AzureBlobToken  fields. You must download the exported content and we currently don't support exporting data into your own Azure blobs.
The getDownloadUrl method is deprecated and will stop returning data on April 30th, 2023. Please use the new exportFileMetadata property returned by the Get caseOperation API instead.


Can't close COMMIT view

Sublime Text V 3.1.1 Build 3176
git version 2.14.1.windows.1
Windows 10
No error in the console

Open Status dashboard
Add file to stage with "s"
Open COMMIT tab with "c"
Press "ctrl + w" to close the tab, nothing happens.

If open up the console and enable logging I can see that gs_commit_view_close is called but the view doesn't close.
This bug started after Gitsavvy was updated on my pc just now.

try restarting sublime text to see if it helps.

Just found this, #995. Restarted and it is fixed

awesome.


An error occurred while accessing the Microsoft.Extensions.Hosting services. Continuing without the application service provider. Error: The entry point exited without ever building an IHost. Unable to create an object of type 'ApplicationDbContext'. For the different patterns supported at design time, see https://go.microsoft.com/fwlink/?linkid=851728

[Enter feedback here]

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

ID: 459d20e7-ba25-c162-5721-359ef3562999
Version Independent ID: d988e806-cb86-19f5-7f76-6ce3bfcd94ed
Content: Design-time DbContext Creation - EF Core
Content Source: entity-framework/core/cli/dbcontext-creation.md
Product: entity-framework
Technology: entity-framework-core
GitHub Login: @bricelam
Microsoft Alias: avickers

This issue is lacking enough information for us to be able to fully understand what is happening. Please attach a small, runnable project or post a small, runnable code listing that reproduces what you are seeing so that we can investigate.

EF Team Triage: Closing this issue as the requested additional details have not been provided and we have been unable to reproduce it.
BTW this is a canned response and may have info or details that do not directly apply to this particular issue. While we'd like to spend the time to uniquely address every incoming issue, we get a lot traffic on the EF projects and that is not practical. To ensure we maximize the time we have to work on fixing bugs, implementing new features, etc. we use canned responses for common triage decisions.


Update format in Documenter make script

Just tried PkgTemplates for a new project, very cool! Building the docs gave me the following deprecation warning:
┌ Warning: `format = :html` is deprecated, use `format = Documenter.HTML()` instead.

With this change, probably this test has to be updated as well. Using Documenter v0.21.0 here.

This will actually break the existing Travis CI integration, because Documenter is pinned to an older version until I get around to properly implementing the new doc deployment workflow (#23).


Refactor the pattern matching code

Closes #68
This PR puts the pattern matching code behind an interface.  The user now has the ability to provide their own pattern matcher.  It also pulls in github.com/Comcast/sheens/match to implement the default pattern matcher.
To review, I recommend ignoring the diff of core/match.go, and just looking at the new version of it in its entirety to see the direction I went there.  The idea I was going with, BTW, was to maintain backwards compatibility.  Perhaps Rulio can start seeing some release tags, and then when it is ready for a breaking change, we can clean this up.

@jsscast this is ready for review.  LMK if you'd like to see any changes or a different direction.

Sorry, I missed this notification. I'll take a look ASAP.

Sorry, I missed this notification. I'll take a look ASAP.

I'll merge it now. As you suggested, we should probably start using proper versioning soon.

I'll merge it now. As you suggested, we should probably start using proper versioning soon.


Think more about errors in interceptors

See http://pedestal.io/reference/error-handling

but the associated complexity would be substantial

right, I don't think that's necessary for this library, but thanks for the interesting perspectives, really appreciate it @cch1 and @1100001-jones !

@borkdude no problem, happy to help.

The current approach is to just throw an exception.


Bumped versions in pre-commit configuration.

Flake8 moved to GitHub this weekend. See https://github.com/PyCQA/flake8/issues/1290.
While I was here I've also bumped all the versions.

@smithdc1 Thanks :+1:


"Could not find environment: omnisci"

When I try and follow the directions in "KNN weight modeling on Omnisci", I end up with the following error:
[jbrown613@holygpu2c0701 ~]$ module load Anaconda3/5.0.1-fasrc02
[jbrown613@holygpu2c0701 ~]$ source activate omnisci
CondaEnvironmentNotFoundError: Could not find environment: omnisci .
You can list all discoverable environments with conda info --envs.

Please create conda environment omnisci using:
conda create -n omnisci python=3.6

source activate omnisci

pip install pymapd
pip install pandas
pip install pyarrow


[Mod Support Request] - Darker Depths - Untitled Duck Mod - Danny's Expansion

Darker Depths
https://www.curseforge.com/minecraft/mc-mods/darker-depths
2 mobs
Untitled Duck Mod
https://www.curseforge.com/minecraft/mc-mods/untitled-duck-mod-forge
2 mobs
Danny's Expansion
https://www.curseforge.com/minecraft/mc-mods/beta-dannys-expansion
22 mobs

Thanks for your request!

Added support for Darker Depths, will upload to the curseforge page tomorrow.
Duck mod - unfortunately, there's an issue with the entity texture not being set correctly (see here) so I won't be able to support the duck variants but I can use a single icon for both variants - will get on this soon.
I will start on Danny's Expansion soon, just after I have added support for a couple of other mods!

Brilliant thank you ^^

Added support for Danny's Expansion
Added support for Untitled Duck Mod

The updated pack has just been uploaded to CurseForge.


Can't build android release on react native version 0.61

I was unable to reproduce this issue with a sample project using react-native 0.63.2 and react-native-dns-lookup 1.0.3.
For react-native >= 0.60 linking occurs automatically. If you manually linked the library, you can run react-native unlink react-native-dns-lookup and then rebuild the app yarn react-native run-android.
Sample project: https://github.com/avertin/DnsTest/blob/master/App.js#L30
Autolinking: https://github.com/react-native-community/cli/blob/master/docs/autolinking.md


The UI cannot handle layer names with a "" in them

It appears that there is an error when constructing the container, the error occurs when we try to draw the chart in the short list:
Uncaught Error: Container is not defined
at gvjs_3m (jsapi_compiled_default_module.js:66)
at gvjs_pL.gvjs_7p [as constructor] (jsapi_compiled_default_module.js:232)
at gvjs_pL.gvjs_8K [as constructor] (jsapi_compiled_ui_module.js:979)
at new gvjs_pL (jsapi_compiled_ui_module.js:1012)
at gChart.js:78
at Object.with_layer (layer.js:455)
at drawBarChart (gChart.js:19)
at newGchart (gChart.js:149)
at shortlist.js:421

Note: I have not yet tested whether map creation will also have an error (on the "compute" side of the code).

this particular problem no longer exists, however we need to reject attribute names with a back-slash in them. Take care of this under #44


fixing path

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
586

Relevant Lines:
1285

💛  - Coveralls

I'll drive the presubmit for merging.

resolves #824


Scoping Q2, Q3

At the end of Q2 and early Q3 we're aiming to finish next features (those features are important ):
Q2, Q3
LiveView Native SwiftUI

[ ] Use liveview-native-core that uses phoenix-channels-client /liveview-native/liveview-native-core-swift/issues/6
[ ] Use swift-bridge to generate bindings to liveview-native-core /liveview-native/liveview-native-core-swift/issues/7
[ ] Diff/merge should preserve unchanged elements #13
[ ] Panic when parsing HTML comments in pages #14
[ ] Support file uploading #15
[ ] LiveView Native Core to use Phoenix.Channels client #16
[ ] Incorrect transformation way #17
[ ] For loops and live components crash #18
[ ] Nesting for loops crash #19
[ ] Support streaming #21
[ ] Strange behavior with Picker and conditionally rendered Image elements /liveview-native/liveview-client-swiftui/issues/769

Phoenix.Channels

[x] Build times too slow at almost 1/2 hour /liveview-native/phoenix-channels-client/issues/6
[x] Client::join does not allow the payload to be customized /liveview-native/phoenix-channels-client/issues/8
[x] Send binary messages /liveview-native/phoenix-channels-client/issues/10
[x] Error immediately when waiting on reply and channel errors /liveview-native/phoenix-channels-client/issues/12
[x] Reconnect on error /liveview-native/phoenix-channels-client/issues/15
[ ] Presence /liveview-native/phoenix-channels-client/issues/19
[ ] Non-join replies ignore ReplyStatus /liveview-native/phoenix-channels-client/issues/21

@bcardarella @KronicDeth @supernintendo @Bajix here is the main issue to track all the development with LiveView native Core.
Approximate estimation for all unfinished tasks is: 413 hours = 10.325 weeks (40 hours per week) = 11 weeks
Approximate ETA: September 8 2023


Add BSD 3-clause license

Also adds a slightly more comprehensive .gitignore file. Fixes #3.

@hamishmorgan Can you review this?

gitignore makes me sad, but NABD - :+1:


[rust] remove is_started condition check because telemetry_command_tx…

… is suffice to tell

Which Issue(s) This PR Fixes

Fixes #707
Brief Description

There is no need to check is_started because telemetry_command_tx is suffice to tell if client is ready.
How Did You Test This Change?

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 47.60%. Comparing base (430ed16) to head (0fbb1b3).
Report is 1 commits behind head on master.

Additional details and impacted files
@@             Coverage Diff              @@
##             master     #711      +/-   ##
============================================
- Coverage     56.05%   47.60%   -8.45%
  Complexity      664      664
============================================
  Files           259      207      -52
  Lines         15856    12353    -3503
  Branches       4089     3705     -384
============================================
- Hits           8888     5881    -3007
+ Misses         6679     6183     -496
  Partials        289      289

Flag
Coverage Δ

nodejs
?

rust
79.70% <ø> (+0.73%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Include own bower.json

I got a bower.json file in my project root which declares my dependencies.
It has some mainFiles, too.
If i use bower-concat the mainFiles are not used (only the ones from the dependencies).
Usemin has an option for using the own file.
Is there some for bower-concat, too?

Nope, but pull request is welcomed.


Build release 1.2.rc1

RC 1 before community testing

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

Test name
Commit
Details
Rerun command

prow/release-build
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-build

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.

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

Test name
Commit
Details
Rerun command

prow/release-build
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-build

prow/release-istioctl-tests
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-istioctl-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.

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

Test name
Commit
Details
Rerun command

prow/release-build
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-build

prow/release-istioctl-tests
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-istioctl-tests

prow/release-e2e-simpleTests
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-e2e-simpleTests

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.

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

Test name
Commit
Details
Rerun command

prow/release-build
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-build

prow/release-istioctl-tests
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-istioctl-tests

prow/release-e2e-simpleTests
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-e2e-simpleTests

prow/release-e2e-mixer-no_auth
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-e2e-mixer-no_auth

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.

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

Test name
Commit
Details
Rerun command

prow/release-build
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-build

prow/release-istioctl-tests
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-istioctl-tests

prow/release-e2e-simpleTests
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-e2e-simpleTests

prow/release-e2e-mixer-no_auth
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-e2e-mixer-no_auth

prow/release-e2e-bookinfoTests
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-e2e-bookinfoTests

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.

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

Test name
Commit
Details
Rerun command

prow/release-build
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-build

prow/release-istioctl-tests
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-istioctl-tests

prow/release-e2e-simpleTests
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-e2e-simpleTests

prow/release-e2e-mixer-no_auth
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-e2e-mixer-no_auth

prow/release-e2e-bookinfoTests
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-e2e-bookinfoTests

prow/release-upgrade-tests-1.1.7
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-upgrade-tests-1.1.7

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.

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

Test name
Commit
Details
Rerun command

prow/release-build
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-build

prow/release-istioctl-tests
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-istioctl-tests

prow/release-e2e-simpleTests
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-e2e-simpleTests

prow/release-e2e-mixer-no_auth
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-e2e-mixer-no_auth

prow/release-e2e-bookinfoTests
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-e2e-bookinfoTests

prow/release-upgrade-tests-1.1.7
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-upgrade-tests-1.1.7

prow/release-e2e-pilot-no_auth
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-e2e-pilot-no_auth

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.

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

Test name
Commit
Details
Rerun command

prow/release-build
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-build

prow/release-istioctl-tests
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-istioctl-tests

prow/release-e2e-simpleTests
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-e2e-simpleTests

prow/release-e2e-mixer-no_auth
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-e2e-mixer-no_auth

prow/release-e2e-bookinfoTests
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-e2e-bookinfoTests

prow/release-upgrade-tests-1.1.7
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-upgrade-tests-1.1.7

prow/release-e2e-pilot-no_auth
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-e2e-pilot-no_auth

prow/release-e2e-dashboard
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-e2e-dashboard

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.

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

Test name
Commit
Details
Rerun command

prow/release-build
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-build

prow/release-istioctl-tests
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-istioctl-tests

prow/release-e2e-simpleTests
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-e2e-simpleTests

prow/release-e2e-mixer-no_auth
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-e2e-mixer-no_auth

prow/release-e2e-bookinfoTests
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-e2e-bookinfoTests

prow/release-upgrade-tests-1.1.7
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-upgrade-tests-1.1.7

prow/release-e2e-pilot-no_auth
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-e2e-pilot-no_auth

prow/release-e2e-dashboard
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-e2e-dashboard

prow/release-e2e-stackdriver
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-e2e-stackdriver

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.

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

Test name
Commit
Details
Rerun command

prow/release-build
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-build

prow/release-istioctl-tests
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-istioctl-tests

prow/release-e2e-simpleTests
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-e2e-simpleTests

prow/release-e2e-mixer-no_auth
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-e2e-mixer-no_auth

prow/release-e2e-bookinfoTests
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-e2e-bookinfoTests

prow/release-upgrade-tests-1.1.7
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-upgrade-tests-1.1.7

prow/release-e2e-pilot-no_auth
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-e2e-pilot-no_auth

prow/release-e2e-dashboard
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-e2e-dashboard

prow/release-e2e-stackdriver
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-e2e-stackdriver

prow/release-unit-tests
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-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.

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

Test name
Commit
Details
Rerun command

prow/release-e2e-pilot-no_auth
6466d35c983e6bbb1704192652240bfc1a016ac0
link
/test release-e2e-pilot-no_auth

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.


No longer working

As of 12 hours ago from creating this issue.
https://downloads.mariadb.com/MariaDB/mariadb-11.4.2/winx64-packages/mariadb-11.4.2-winx64.msi is 404'ing
https://github.com/tgstation/tgstation-server/actions/runs/11153874229/job/31003041075?pr=1946

Hi @Cyberboss, thanks for reporting. Fixed in #20.

Thank you!


rpmlint complains about invalid invalid-lc-messages-dir

invalid-lc-messages-dir /usr/share/locale/zh_tw/LC_MESSAGES/errands.mo
Changing /usr/share/locale/zh_TW/LC_MESSAGES/errands.mo solves the problem

Fixed in 64c2fd1c436bcd1d358d868dbe2beebcdfddcb5a and de8b47b8591856de77871768869d6a93731c2993


Flex instance does not report stack traces to stackdriver

Errors are being logged to /var/log/app_engine/app/app-php-error.log but stackdriver's error reporting is not showing anything. When connected to the server /var/log/google-fluentd/google-fluentd.log shows the app-php-error.log being monitored but again stackdriver has nothing.
Stack traces were being logged correctly on the standard environment but after moving over to flex they don't.

@tmatsuo I don't think we need to do anything special to support Cloud Errors.  Just like the /var/logs/app_engine stuff, we want to let Cloud Logging do the work here.

@moneal We're going to change how to handle logs with #212. Yeah as @JustinBeckwith said the runtime itself should be just stream the logs if possible. Removing the labels now.

We are planning to provide some ErrorReporting tools in google-cloud-php. Stay tuned.

Now this feature is under alpha testing, the instructions are at:
https://docs.google.com/document/d/126NJTDNctB0zL8dwTo8-9indyWGUXpGkrXCKrHU4b-s

New error logging is working great. I'm now seeing alerts and full traces when a error happens on my Laravel app. So nice and can drop a external reporting service :)


Basic layout, routing set up, lazy-loaded Avatar component

Frontend

Breakpoints documentation
Update dependencies
Set up svelte-routing (single home route only, for now)
Create Avatar component.

By default performs lazy loading. Can be easily turned off
Size can be easily changed using size prop.

Basic layouting foundation

Backend

Added CORS as painkiller for future CORS issues (Pardon the language 😋)
User's profile image is also stored in Database
Update default MySQL table set up in connection.js to adapt to above change

Link #803


Don't implement and call deprecated ConnectorPageSourceProvider.createPageSource

Welcome in the community!
Please follow and sign https://github.com/prestosql/cla which is required to contribute to project.
Also please familiarize with: https://github.com/prestosql/presto#development, make sure you read https://chris.beams.io/posts/git-commit/ which is a great article about how to write commit messages that we follow.
I would rewrite commit message:
Avoid using deprecated method in Pinot connector

What do you think?

Welcome in the community!
Please follow and sign https://github.com/prestosql/cla which is required to contribute to project.
Also please familiarize with: https://github.com/prestosql/presto#development, make sure you read https://chris.beams.io/posts/git-commit/ which is a great article about how to write commit messages that we follow.
I would rewrite commit message:
Avoid using deprecated method in Pinot connector

What do you think?

It's not only using, also aboid implementing it so commit message is ok for me

It's not only using, also about implementing it so commit message is ok for me

👍
Please file CLA and please read the staff I mentioned.

Filed cla yesterday
pt., 10 lip 2020, 11:12 użytkownik Grzegorz Kokosiński <
<EMAIL_ADDRESS>napisał:

It's not only using, also about implementing it so commit message is ok
for me
👍
Please file CLA and please read the staff I mentioned.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/prestosql/presto/pull/4403#issuecomment-656574067,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGAYEYU4OK2FEAJN7U7RCLR23LQDANCNFSM4OVVJYWQ
.

Please ping me when automation completes, so I can merge it.

build successful after rebase, ready to merge

Merged, thanks.


BUG - Only one input working

Only one input working
We want both input boxes to work to update the other, should be a simple fix

Bug fixes as per last deploy (Proved via multiple decimal places):


 In js-debug the preview is just the stringified function
Double click on the name of the variable to try to edit it
Get in this state where the getter is still collapsed and the value is being edited

Instead the variable should automatically expand and its value should be edited

In mock-debug this is surfaced as lazy var appearing on click and staying there after focus leaves

Dupe of #143751


Git changes only detected in Source Control tab when window is focussed (Linux)

Version Info:
Version: 1.54.3
Commit: 2b9aebd5354a3629c3aba0a5f5df49f43d6689f8
Date: 2021-03-15T10:55:24.277Z
Electron: 11.3.0
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 5.8.0-7642-generic
Steps to Reproduce (Failing Scenario / Unfocussed Window):

Open a single folder containing a Git repo with some unstaged changes in a new VSCode window.
Run the chokidar-test script in a terminal window, and have it watch the same folder that's been opened in VSCode.
Run git add -A in a second terminal window cded into the same folder that's open in the other two windows.
Observe that the chokidar-test window displays the list of now staged files, but that VSCode's Source Control tab does not reflect the change.
Focus the VSCode window and notice that it now updates to reflect the changes we made.

Steps to Reproduce (Working Scenario / Focussed Window):

As previously defined.
As previously defined.
Run sleep 5 && git add -A in the second terminal window this time.
Quickly focus the VSCode window before the 5 seconds have elapsed.
Observe, after 5 seconds, that the changes are now correctly reflected everywhere.

Does this issue occur when all extensions are disabled?:

Yes

WARNING: Keep performance for all users.
Should be create configuration with current default for enable users personalize.

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.
If you wonder what we are up to, please see our roadmap and issue reporting guidelines.
Thanks for your understanding, and happy coding!


Add a Usage example for SSE in the docs

Describe the feature
Currently in the docs there is a Usage example for how to create a WebSocket Nitro route: https://nitro.unjs.io/guide/websocket#usage but there is no example for server-sent events and how to create a Nuxt/Nitro route for that. There is an example in h3 docs but not in Nitro.
It would be very useful to create such usage example also for SSE (Server-sent events) just like WebSockets example.

Create a websocket handler in routes/_ws.ts

export default defineWebSocketHandler({
  open(peer) { ... },
  message(peer, message) { ... },
  close(peer, event) { ... },
})

Additional information

[ ] Would you be willing to help implement this feature?

@pi0 This is what we talked about in this gist.

Thanks for the issue ❤ Feel free to contribute to the docs by making a PR.

Thanks for the issue ❤ Feel free to contribute to the docs by making a PR.

@pi0 To be honest, I am not entirely sure what the usage should be. You mentioned that the usage is the same as in h3 but in a Nuxt/Nitro server route there is usually some kind of an event handler like in the example of @Atinux SSE endpoint example with Nuxt 3 gist
// ~/server/routes/sse.ts
export default defineEventHandler(async (event) => {
  // ...
})

Simply like this https://stackblitz.com/edit/github-lku74j?file=server%2Froutes%2Findex.ts
And you can either render it directly or connect with an eventsource client.
you can also use useNitroApp().hooks to use global hooks but i guess for sake of example we probably don't want to complicate it.

Simply like this stackblitz.com/edit/github-lku74j?file=server%2Froutes%2Findex.ts
And you can either render it directly or connect with an eventsource client.
you can also use useNitroApp().hooks to use global hooks but i guess for sake of example we probably don't want to complicate it.

Works like a charm, tested also with Nuxt. I will send in pull request to update the docs.

Have an example of SSE working here in a real world app if that's beneficial at all:
https://github.com/SelfhostedPro/yacht-nuxt/blob/main/modules/notifications/runtime/server/composables/sse.ts
Has some stuff around Auth too and creating unique sessions for if you don't want all the events on every SSE connection.


feat:file upload

@Jit-Bdr-Rana Thank you for your patience while waiting for a review and processing your request. Pull request merged.


Fix formatting in PLUGINS.md

/test all

/remove-lifecycle stale

Marked /remove-lifecycle stale, but I'm not sure how to continue here. @divyansh42 ? @apoorvajagtap ?

Marked /remove-lifecycle stale, but I'm not sure how to continue here. @divyansh42 ? @apoorvajagtap ?


grid-view.js.map 404

Installed via HACS and tried to use the visual editor but its not loading.
Checked chrome developer tools and grid-view.js.map is showing a 404 error.

Hi.
Any due date for this issue to be fixed ?
Could there be any workaround until it is fixed ?
Thanks


jquery.hammer.js 1.1.2 and  jquery.hammer.js 1.1.3 doesn't work on ie8 (jquery.hammer.js 1.1.1 is ok)

Any idea how i can fix it? Thank you!

Closing we are not maintaining 1.x


Aggregate all meta buttons in one place

Feedback - comments - form
Home button
Preview/Print button

Buttons are in the same place.


Pygments raise error on strange symbols

(Original issue 244 created by None on 2007-05-11T20:38:26+00:00)
For symbols out of ascii range pygments raise UnicodeEncodeError.
For example if for the attached file you use:
{{{
cat strange_symbols | ./pygmentize  -l diff -f html -O style=borland,noclasses=true
}}}
You will get:
{{{
UnicodeEncodeError: 'ascii' codec can't encode characters in position 0-1: ordinal not in range(128)
(file "/svn/pygments/formatters/html.py", line 545, in format)
}}}
I attached a patch that fixes this problem
Hauser
Reported by guest

(Original issue was assigned to gbrandl)
(Original issue 244 last updated on 2007-06-13T12:57:20+00:00)
(Issue automaticaly closed due to status in Bitbucket: resolved)

(Original comment by gbrandl on 2007-06-13T12:57:20+00:00)
Okay, I reworked the pygmentize encoding handling now. See r3700.

(Original comment by None on 2007-05-26T17:03:24+00:00)
I think that at least pygmentize (command line tool) should not throw this kind of exceptions when normally used. If you don't think so, feel free to close this ticket.

(Original comment by gbrandl on 2007-05-18T13:13:28+00:00)
This behavior is not a bug, but by design. I updated the Unicode docs to cover this situation -- see http://pygments.org/docs/unicode/ for details.