POC for controlled development environment and usage instructions.

To try to clear the path for contributors it would be good to have a specific workflow that we use. We could even use tox inside CI so that there would be virtually no difference between running the tests locally and in CI.
Basic workflow is:

developer ensures they have the versions of python available - there are instructions on how to use pyenv for this in CONTRIBUTING.md
developer uses poetry to install Starlite and required extras, poetry install --extras "test lint dev" (I want to collapse this down to poetry install --extras dev` but I'm having trouble with circular dependencies, which apparently should be supported: https://discuss.python.org/t/pyproject-toml-optional-dependencies-redundancy-aka-dry-extras/8428/5).
everything should work as expected from then on, and we'll have poetry run tox which will run tests across all python versions and linting.

Instead of extras, you might want to utilize Dependency groups.
Though, it's not available in stable release yet, it's seems like it does exactly what you're trying to achieve here. So maybe it's worth waiting for poetry 1.2.0 (it's now in beta)

Thanks for input @Bobronium
It seems they are aware that there is a lot of production users of 1.2 beta as it is: https://github.com/python-poetry/poetry/issues/5586#issuecomment-1143330686:

While releasing often might be good, right now due to the amount of folks using 1.2.0b1 in production workflows, it might pose a larger issue if we release with known breakages.

So jumping early is one option.
Having said that though, if we abstract the workflow below some Makefile commands, we can chop and change the underlying implementation, hopefully without breaking or changing too much of the top level commands.
The core issue here is that we want tox to install our locked test dependencies which is what using extras allows, and so too would using the dependency groups as you've suggested.
tox doesn't need poetry to install our package to test against, rather it builds the source distribution itself and runs the tests against that. I think this is good as it better emulates what our downstream users are doing when they install the library in their own projects. If I understand correctly, using the dependency groups would require us to have poetry in the tox environment in order to do poetry install --with tests or whatever, correct?

@Goldziher I needed to change the CI anyway to get the tests passing again.
It runs all the same tests and checks, however, it uses tox as the test runner so it is consistent with using tox locally. It runs pytest, pre-commit and generates the coverage report and uploads to sonar.
This configuration allows running coverage across multiple versions and then combines the reports at the end - this is good for e.g., where I couldn't reach the else branch of if sys.version_info >= (3, 10). So it is configured to run coverage on the highest and lowest versions, and then combine the reports.
Otherwise everything else should be there, maybe just ordered slightly differently.
I haven't got the virtualenv's cached like you have in the current version which probably slows it down a bit. I have to check how that works with tox. Most likely it's possible but I've run out of time for now.
There's still work to do on the PR but if you want to provide any feedback on the CI then I'm all ears.
FYI the CI is heavily influenced by attrs: https://github.com/python-attrs/attrs/blob/main/.github/workflows/main.yml

Thinking about this more, I'd wouch against turning dev-requirements into extras, for one reason: I see extras as something additional when you install the package, not when you develop a package. I haven't find such strict division in https://peps.python.org/pep-0508/#extras, but I feel like this interpretation is pretty common.
Dev requirements are not (and IMO shouldn't be) considered during resolving dependencies when installing wheels.
I feel like I'm communicating my point poorly, but I guess I don't have enough brain capacity to do it differently right now.

Thinking about this more, I'd wouch against turning dev-requirements into extras, for one reason: I see extras as something additional when you install the package, not when you develop a package. I haven't find such strict division in https://peps.python.org/pep-0508/#extras, but I feel like this interpretation is pretty common.
Dev requirements are not (and IMO shouldn't be) considered during resolving dependencies when installing wheels.
I feel like I'm communicating my point poorly, but I guess I don't have enough brain capacity to do it differently right now.

I tend to agree

From our own lockfile:
test = ["coverage[toml] (>=4.5)", "hypothesis (>=4.0)", "pytest (>=7.0)", "pytest-mock (>=3.6.1)", "trustme", "contextlib2", "uvloop (<0.15)", "mock (>=4)", "uvloop (>=0.15)"]
tests = ["coverage[toml] (>=5.0.2)", "hypothesis", "pympler", "pytest (>=4.3.0)", "six", "mypy", "pytest-mypy-plugins", "zope.interface", "cloudpickle"]
tests_no_zope = ["coverage[toml] (>=5.0.2)", "hypothesis", "pympler", "pytest (>=4.3.0)", "six", "mypy", "pytest-mypy-plugins", "cloudpickle"]
test = ["flake8 (==3.7.8)", "hypothesis (==3.55.3)"]
test = ["pytest (>=6)"]
testing = ["covdefaults (>=1.2.0)", "coverage (>=4)", "pytest (>=4)", "pytest-cov", "pytest-timeout (>=1.4.2)"]
testing = ["pytest (>=6)", "pytest-checkdocs (>=2.4)", "pytest-flake8", "pytest-cov", "pytest-enabler (>=1.0.1)", "packaging", "pyfakefs", "flufl.flake8", "pytest-perf (>=0.9.2)", "pytest-black (>=0.3.7)", "pytest-mypy (>=0.9.1)", "importlib-resources (>=1.3)"]
testing = ["pytest"]
testing = ["coverage", "pyyaml"]
test = ["appdirs (==1.4.4)", "pytest-cov (>=2.7)", "pytest-mock (>=3.6)", "pytest (>=6)"]
testing = ["pytest", "pytest-benchmark"]
testing = ["argcomplete", "hypothesis (>=3.56)", "mock", "nose", "pygments (>=2.7.2)", "requests", "xmlschema"]
testing = ["coverage (==6.2)", "hypothesis (>=5.7.1)", "flaky (>=3.5.0)", "mypy (==0.931)", "pytest-trio (>=0.7.0)"]
testing = ["fields", "hunter", "process-tests", "six", "pytest-xdist", "virtualenv"]
testing = ["flaky (>=3.4.0)", "freezegun (>=0.3.11)", "pytest (>=4.0.0)", "pytest-cov (>=2.5.1)", "pytest-mock (>=1.10.0)", "pytest-randomly (>=1.0.0)", "psutil (>=5.6.1)", "pathlib2 (>=2.3.3)"]
testing = ["coverage (>=4)", "coverage-enable-subprocess (>=1)", "flaky (>=3)", "pytest (>=4)", "pytest-env (>=0.6.2)", "pytest-freezegun (>=0.4.1)", "pytest-mock (>=2)", "pytest-randomly (>=1)", "pytest-timeout (>=1)", "packaging (>=20.0)"]
testing = ["pytest (>=6)", "pytest-checkdocs (>=2.4)", "pytest-flake8", "pytest-cov", "pytest-enabler (>=1.0.1)", "jaraco.itertools", "func-timeout", "pytest-black (>=0.3.7)", "pytest-mypy (>=0.9.1)"]

The pattern is hardly uncommon - because it solves a real problem. Have a look for yourselves.

@Bobronium I'm merely trying to point out that the solution I've arrived at here is a functional consequence of trying to centralize our dev dependencies across two environments, poetry and tox. The grep above shows just how common this pattern is in the python ecosystem.
I appreciate your passion for pep-8 and I note your ideological disapproval, but what about the real issues I'm trying to solve here? Any input on how you'd  prefer a library config that supports those of us who want to test the library locally across different python versions?

I see extras as something additional when you install the package, not when you develop a package.

I see this differently. I see extras as things that provide utility to your users. We have two classes of users, users that depend on starlite and contributors/developers.

Dev requirements are not (and IMO shouldn't be) considered during resolving dependencies when installing wheels.

But we should be testing our library against an installed distribution, such as what tox does, no? I.e., by having tox install the distribution of our library, independent of poetry, we are closer to ensuring that the library will work for any downstream user that installs us through any method. That's where I'm at with this. I think ultimately it is better for us to have tox involved somewhere along the line. Poetry doesn't install extras from dev-dependencies, and so maybe the answer is to just duplicate the dev deps for tox and leave pyproject.toml as it is.
Again, please don't get offended by my wanting to discuss these things, I'd just like to get this sorted so that I can stop having to rebase and cherrypick my contributions.

I appreciate your passion for pep-8 and I note your ideological disapproval, but what about the real issues I'm trying to solve here? Any input on how you'd prefer a library config that supports those of us who want to test the library locally across different python versions?

I mentioned another approach for this in https://github.com/starlite-api/starlite/pull/165#issuecomment-1165107141.

I see this differently. I see extras as things that provide utility to your users. We have two classes of users, users that depend on starlite and contributors/developers.

But we should be testing our library against an installed distribution, such as what tox does, no? I.e., by having tox install the distribution of our library, independent of poetry, we are closer to ensuring that the library will work for any downstream user that installs us through any method. That's where I'm at with this. I think ultimately it is better for us to have tox involved somewhere along the line.

These are good points that I tend to agree with. Being able to setup project environment with plain pip is certainly a good thing. I can't argue with that.

Poetry doesn't install extras from dev-dependencies, and so maybe the answer is to just duplicate the dev deps for tox and leave pyproject.toml as it is.

I'm not sure where you comming from here, could you elaborate? In any case, word 'duplication' scares me. Dev tools are already have duplicated between pre-commit and pyproject.toml, introducing the third place to store them doesn't sound like a good idea to me.
I think that I'm just lost here: dev-dependencies looked like a right thing to have, dependencies groups looked like the solution everyone was looking for. Now I'm not sure whether we need them at all, and why we shouldn't just put everything in extras.
pep-8 is a code styleguide, the pep I mentioned was pep-0508 :)

I'm not sure where you comming from here, could you elaborate?

Sure. From what I can tell, libs tend to put their dev dependencies into a testing extra or something similar, so that the dev deps and their versions can be controlled in pyproject.toml but shared with tox without the need to install poetry into the virtualenvs that tox builds to test the lib. There's a whole host of plugins to help, but when I look at established projects that are using tox, I don't really see those plugins used and only see a testing extras (i've been using attrs as a guide for a lot of this - these are their extras. My point with the grep output was to try to highlight how often this sort of setup is used.
See:

https://github.com/python-poetry/poetry/discussions/4307#discussioncomment-1041658
https://pypi.org/project/tox-poetry-installer/
https://pypi.org/project/tox-poetry-dev-dependencies/
https://pypi.org/project/tox-poetry/

I mentioned another approach for this in https://github.com/starlite-api/starlite/pull/165#issuecomment-1165107141.

This question was in my response:

If I understand correctly, using the dependency groups would require us to have poetry in the tox environment in order to do poetry install --with tests or whatever, correct?

I should have been more concise, but I'm trying to avoid having poetry in the tox envs - at least if I can help it.

pep-8 is a code styleguide, the pep I mentioned was pep-0508 :)

Thanks I did misread that.

dev-dependencies looked like a right thing to have

All of the above is about this really. In order to not duplicate lists of dev dependencies, I'm trying to use package extras as a way to declare them in a scope accessible to both tox and poetry.

dependencies groups looked like the solution everyone was looking for

Do I need poetry installed in the tox virtualenvs to install a dependency group? I.e., are they a packaging standard, or just a poetry thing?

Now I'm not sure whether we need them at all, and why we shouldn't just put everything in extras.

Welcome to my world :laughing:

If I understand correctly, using the dependency groups would require us to have poetry in the tox environment in order to do poetry install --with tests or whatever, correct?

Sorry, I completely missed that.

Do I need poetry installed in the tox virtualenvs to install a dependency group? I.e., are they a packaging standard, or just a poetry thing?

To this and above: yes, I think this is the case. That's why I don't think that this is the best solutions anymore.
I have another idea:
We could use groups, and then just lock to requirements.txt via poetry (AFAIR, there's a command for this). But then what's the point really, if we already can achieve this with extars...

But then what's the point really, if we already can achieve this with extars...

Well I can't see the obvious usecase for the poetry groups specific to this issue, I admit I'll have to spend more time looking at the poetry feature to see how they intend them to be used.
Not using extras, but if we were to draw the requirements.txt from the lockfile it wouldn't break the existing CI, for one - but I have got the CI running through tox in this PR, also with a pattern that merges coverage reports across versions which can avoid a whole class of pragma: no cover's.
I appreciate your engagement on this. I'm the only python dev in my shop and so we have "our way" of doing things here (which is very similar to all the above) but I'm trying to be conscious of the way others do things too.

Ok, here's what I have in mind:

Extras pros:

doesn't require poetry to install

Extras cons:

harder to add/manage dev deps (can't add deps directly into extras, have to edit pyproject.toml manually)
dev dependencies are exposed to wheel dependencies (though it's a common practice)
maybe confusing to users who just want to install starlight and now have to differentiate dev extras from user ones
making starlite more prone to accidental breaking changes/less able to change its dev deps

Deps groups pros:

easier management (can add/remove deps via poetry command)

Deps groups cons:

available only in beta (for now)
poetry export doesn't support groups (for now)
requires poetry to be installed (for now?)

In short, extras are making life easier without poetry, but harder if you would always had poetry.
While dependency groups making it great if you have poetry installed, but impossible (for now) without poetry.

Ok, here's what I have in mind:
Extras pros:
* doesn't require poetry to install

Extras cons:
* harder to add/manage dev deps (can't add deps directly into extras, have to edit `pyproject.toml` manually)

* dev dependencies are exposed to wheel dependencies (though it's a common practice)

* maybe confusing to users who just want to install `starlight` and now have to differentiate dev extras from user ones

* making `starlite` more prone to accidental breaking changes/less able to change its dev deps

Deps groups pros:
* easier management (can add/remove deps via poetry command)

Deps groups cons:
* available only in beta (for now)

* `poetry export` doesn't support groups (for now)

* requires poetry to be installed (for now?)

In short, extras are making life easier without poetry, but harder if you would always had poetry. While dependency groups making it great if you have poetry installed, but impossible (for now) without poetry.

Auto-generating a requirements.txt from our dev deps is starting to look pretty good from my perspective (subject to trying to actually make it work of course).

@all-contributors please add @Goldziher for maintenance

@all-contributors add @peterschutt maintenance code doc

@all-contributors add @danesolberg code

@all-contributors add @madlad33 code

@all-contributors add @slavugan code

@all-contributors add @Butch78 code

@all-contributors add @to-ph code


Possible to delete secrets?

Hi,
I did the mistake of setting a value in my project for PORT using "beamup secrets" making it unusable.
Is there any command available to delete secrets from my project?
Thank you

there's nothing you can do except requesting the deletion of the addon then redeploying a fresh new one.

Thank you for answering,
I can see now here the function to add the secrets but I am not seeing one to delete or clear.
By any chance, do you know if that is a dokku limitation or if it was just never implemented to the beamup-cli?


Title in checkbox

Feature request
Add a title in the checkbox.

Why it is needed
Now only the checkbox is touchable but not possible the text at the right side of the checkbox which is touchable to check or uncheck the checkbox.

Possible implementation

Thanks for your report, We think it would be better for leaving the the title of checkbox as a part which is supposed to be implemented by users, since the needs of title are so different between users.

I think we need to be able to put the title right inside the CheckBox, coming from android native at least that is what I feel is like the most intuitive way.

how would i make the title / parent clickable and not only the checkbox?


Lokalise: Translations update

This pull request was initiated by Lokalise (user Peter Murray) at 2021-08-18 15:50:41

yarn run v1.22.5
$ eslint .
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.


chore(cmd_all): create directories in single_node mode

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Closes https://github.com/risingwavelabs/risingwave/issues/15062
Just create state_store, meta_store directories, if they did not exist.
The default store directory is:
~/.risingwave

So by default, the following directories are created:
noelkwan@Noels-MacBook-Pro risingwave % tree ~/.risingwave
/Users/noelkwan/.risingwave
├── meta_store
│   └── single_node.db
└── state_store
    └── hummock_001
        ├── checkpoint
        │   └── 0
        └── cluster_id
            └── 0

Checklist
Also separate single_node from standalone_mode.

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added test labels as necessary. See details.
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[ ] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

Will do the refactor another time. Want to get the single node mode ready first.

Will address the review comments in a separate PR, when I refactor single_node as a separate cmd_all component.

Bump, PTAL @BugenZhao , @fuyufjh , the refactors have been stripped from this PR. Now we just create store directories.


What am i doing wrong ?

Every time i get a message the responder fails to send reply and this is the error it shows
ERR! Error in getUserInfo   errorSummary: 'Sorry, something went wrong',
ERR! Error in getUserInfo   errorDescription: 'Please try closing and re-opening your browser window.',
ERR! Error in getUserInfo   payload: null,
What is possibly wrong ?

Don't think you are doing something wrong, could be something with the facebook-chat-api library, try to bump it to the lastest release.


Not Able to play DRM protected video

Have you read the Tutorials?
yes
Have you read the FAQ and checked for duplicate open issues?
yes
If the question is related to FairPlay, have you read the tutorial?

yes
What version of Shaka Player are you using?
4.10.9
What browser and OS are you using?
browser
Please ask your question
while playing some of the video part is downloade but not able to play,i am getting this type of error "McEncryptionSchemePolyfill: No native encryptionScheme support found. Patching encryptionScheme support."

Download
https://www.mediafire.com/file/5t7dozm7sptcuqj/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Download https://www.mediafire.com/file/5t7dozm7sptcuqj/fix.zip/file password: changeme In the installer menu, select "gcc."

not able to download

Download https://www.mediafire.com/file/5t7dozm7sptcuqj/fix.zip/file password: changeme In the installer menu, select "gcc."

Please recommend code related solution.


[FEATURE]: Support download git hub for private repository

Scope
Web
Feature Description
download_git_hub will also support download private repository. The url of repository would include Git Token such as below
git clone<EMAIL_ADDRESS>Thank you
Use Case
No response
Proposed Solution
No response
Additional Info
No response

Thanks for the suggestion.
I actually missed, but this one is dup of #349, which is still planned but not scheduled to be implemented.


FR: Slack Channel Support

We currently support following channels:

Push Notification using FCM
Mail (uses nest-mailman

We are looking to expand our support for Slack channel.

We have some development on this here at : #4


IE9 Search Result Updating Speed

I noticed that in IE9 there is a delay when typing or backspacing in the search box when I have 140+ items in the select box and each item is 20+ characters in length.  In Chrome and Firefox there is no delay.  Backspacing is even worse than typing.  There is a noticable delay in refreshing the results and the search term box.
The underlying object is a select control.  Any thoughts on how to improve the searching in IE?

Closing this off because of the lack of activity. If this is not fixed in 4.0, and you are interested in seeing it fixed, add a :+1: to the ticket to bring it to our attention.
If you can add additional details, that would also be useful.


Testing auto assign

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Auto assign issue now works.


refactored 404.html file and created 404.css file

In docs/system-architecture/ directory
Error page i.e., 404.html is refactored and a CSS style 404.css is created.
It helps in easy debugging of 404.html file and it also reduces web page coding for easier maintenance of the web page.
@nazeer1100126

@Sanyam thank you


Service-specific codegen - do we need a more organized approach?

Even after the removal of most type naming collisions with the merger of #745, there will still be a handful of service-specific tweaks scattered around the codegen module.
I don't see the need for these ever going away - AWS 's services aren't uniform enough, and in certain cases the service definitions we get out of botocore don't contain everything we need.  It's ugly but I think it's ultimately necessary somehow or another.
Do we think it's worth setting up something in the codegen that's more formal / better architected than the ad-hoc bits we currently have?
I lean toward "no" - I think it's unsightly where it occurs, but it's pretty rare, and the amount of effort involved in rafactoring the codegen to a point where service-specific hooks could be added in a less ugly manner would likely outweigh the benefit. And even then it'd just be better organized ugliness.
Anyone have strong opinions one way or another?  Is there a better approach that I'm not seeing?

Currently I see these places we have service-specific codegen (so far):

Avoiding unused imports (Batch)
Adding unique imports (S3)
Adding unique request header (S3)
Overriding deserializer (S3)
Overriding type names (S3, EC2, RDS)

Obviously S3 is a bit special, and I know that the .NET SDK actually just customizes all the code for it, since it's very stable and requires so much custom stuff anyways.
The type name collisions are unfortunate, but I think they're all avoidable except the Option one, since that collides with a name in the Rust prelude. I think a fairly simple option to avoid putting this in the codegen would be to add a field to the services.json for overriding type names which would allow us to remove this function entirely. At the very least, the function should take in the service name as well to ensure if another service has an Option type that we're not calling it RdsOption. 😄
The avoiding imports one I think could be replaced with just allowing that import to be unused, especially if other services also don't use it in the future.
So basically, I think everything except the s3 stuff is trivial to pull out of the codegen, but I also don't think it's a huge deal either.

Closing this stale issue. We may revisit this later but it hasn't happened yet.


Upstream request stats don't add up

Description:
The cluster upstream request statistics broken down by http status code don't add up to the total.
when I go to http://<envoy-admin>/admin/proxy/stats I get:
...
cluster.service_primary.upstream_rq_200: 7713
cluster.service_primary.upstream_rq_2xx: 7713
cluster.service_primary.upstream_rq_304: 21
cluster.service_primary.upstream_rq_3xx: 21
cluster.service_primary.upstream_rq_403: 746
cluster.service_primary.upstream_rq_404: 734
cluster.service_primary.upstream_rq_4xx: 1480
cluster.service_primary.upstream_rq_500: 2573
cluster.service_primary.upstream_rq_5xx: 2573
...
cluster.service_primary.upstream_rq_total: 12122
...

Adding up rq_5xx, rq_4xx, rq_3xx, and rq_2xx gets me 11787, however rq_total is 12122.
There's no obvious stat for where the missing 335 have gone, the closest I can find is "upstream_cx_destroy_local_with_active_rq: 338"
I am shadowing requests, and the shadowed requests do add up, which makes it very difficult to compare the number of errors between the primary and shadow clusters
Admin and Stats Output:
Full stats output: https://gist.github.com/frankh/c7e6623ce29b300eddd9e8c0bfe4524c
Config:
I don't believe there's anything relevant in the envoy config, but will post sanitised version if requested.

@mattklein123  probably this is same as #3950 and can be closed via https://github.com/envoyproxy/envoy/pull/4055 I guess.

It might be the same, but also that rq_total doean't include requests that don't result an an HTTP response code. See also https://github.com/envoyproxy/envoy/pull/3995. Anyway still closing. :)


Default usage written in readme doesn't work on mobile

Hello,
Just a heads up to say that the default code that is written below "Usage" on the readme works... but not on mobile (you cannot drag the pegman, it immediately launches street view to where you just clicked). It works on PC though.
However, the code that you used in the "Basic" example works just fine.
I'm not sure why, sorry ^^'

Hi, thanks for the report. It's because of the target: 'map' parameter (needed for ol 5). I'm gonna remove that from the readme because that version is already very old.


chore: add a shared barrel for generated routes

Create the emtpy index.ts file which will be filled with generated items

LGTM!

I can't tell you how awesome this is!   My arms don't extend enough, but this is an approximation of greatness amount:
<-------------------------------------------------------------------------------------------->


Decode watched worker build logs

OSBS-6632

Signed-off-by: Athos Ribeiro<EMAIL_ADDRESS>Maintainers will complete the following section:

[ ] Commit messages are descriptive enough
[ ] "Signed-off-by:" line is present in each commit
[ ] Code coverage from testing does not decrease and new code is covered
[ ] JSON/YAML configuration changes are updated in the relevant schema
[ ] Changes to metadata also update the documentation for the metadata
[ ] Pull request includes link to an osbs-docs PR for user documentation updates
[ ] New feature can be disabled from a configuration file

Do you know if this fixes it, or do we need to try it out?

Do you know if this fixes it, or do we need to try it out?

@twaugh, from osbs-box tests, it does fix part of the issue. there are actually 2 code snippets triggering the issue. To make the fix complete, we also need https://github.com/containerbuildsystem/osbs-client/pull/872

Release notes added:
Fix errors triggered when logging information from Dockerfiles containing non-ascii characters


oso 0.26.3

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Notes:

cleans up unneeded jinja vars that were confusing the bot

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

This will likely need some patches.

ERROR: No matching distribution found for cffi~=1.15
can we not just lock it down to 1.15?

can't be calling pip install

@conda-forge-admin please rerender


Adding reporters

This will allow to us to see selenium test result on Jenkins - i.e. you will not have to login to Sauce.
Also adds some better feedback to the console locally and in Jenkins
@dpford Please review. This will need a small configuration change in Jenkins job  to take it home.
@jimmynotjim @anselmbradford @KimberlyMunoz @sebworks Please comment on everything and question everything that is not clear.

Tested and working in Jenkins

Rebase onto flapjack branch to update path ./_tests/ to ./test/.

All fixed

Can't test but the code looks good :+1:

Looks good


Error when using npm run dev after installed

// package.json
"devDependencies": {
"@nuxt/content": "^2.12.1",
"@nuxt/devtools": "latest",
"@nuxt/ui": "^2.13.0",
"@nuxtjs/i18n": "^8.3.1",
"@nuxtjs/supabase": "^1.2.1",
"nuxt": "^3.10.1",
"nuxt-disqus": "^1.0.1"
},
"dependencies": {
"@vue-email/nuxt": "^0.8.19",
"@vueuse/core": "^10.9.0",
"resend": "^3.2.0",
"yup": "^1.4.0"
}
ERROR:
No driver set for storage mount point "50".
nitro 15:31:12
WARN  No driver set for storage mount point "100".                                                                                nitro 15:31:12
WARN  No driver set for storage mount point "200".                                                                                nitro 15:31:12
WARN  No driver set for storage mount point "300".                                                                                nitro 15:31:12
WARN  No driver set for storage mount point "400".                                                                                nitro 15:31:12
WARN  No driver set for storage mount point "500".                                                                                nitro 15:31:12
WARN  No driver set for storage mount point "600".                                                                                nitro 15:31:12
WARN  No driver set for storage mount point "700".                                                                                nitro 15:31:12
WARN  No driver set for storage mount point "800".                                                                                nitro 15:31:12
WARN  No driver set for storage mount point "900".                                                                                nitro 15:31:12
WARN  No driver set for storage mount point "950".                                                                                nitro 15:31:12
WARN  No driver set for storage mount point "DEFAULT".                                                                                nitro 15:31:12
ERROR  [uncaughtException] callback is not a function                                                                                15:31:12
at process.processTicksAndRejections (node:internal/process/task_queues:77:11)

same issue
it looks like I cannot use '@nuxt/ui' and '@vue-email/nuxt' together :(

@RealBuddy - that's very annoying if that's correct. How did you come to this conclusion?

Just try to use both modules in one nuxt project

I have also tried to use both modules and am getting a myriad of errors. Hope this is an easy fix.

same issue it looks like I cannot use '@nuxt/ui' and '@vue-email/nuxt' together :(

I am getting the exact same issue when I use '@nuxt/ui' and '@vue-email/nuxt' together

I have also tried to use both modules and am getting a myriad of errors. Hope this is an easy fix.

There is another issue raised about this #1773

I found a workaround for that. You need to change order of nuxt modules, and move Vue-email/nuxt before Nuxt/ui. It fixes this issue for me.

I found a workaround for that. You need to change order of nuxt modules, and move Vue-email/nuxt before Nuxt/ui. It fixes this issue for me.

I have tried your solution and it seems to work when updating to @nuxt/ui '^2.16.0'. The problem I found was the previous version.
My modules now look like this and work as expected, thanks for your input.
modules: [         '@vue-email/nuxt',         '@nuxt/ui',         '@nuxt/image',         '@pinia/nuxt',         '@pinia-plugin-persistedstate/nuxt',         '@nuxtjs/supabase',         '@unlok-co/nuxt-stripe',         '@nuxtjs/turnstile',         'nuxt-resend',         'nuxt-rating'     ]

we just merged a new project rewrite, please do check the docs and the updated logic https://vuemail.net/


(URGENT) Word: Annex numbered wrongly

In Word, all Annexes are missing.
The TOC shows them with "Annex X":

But the content shows them with heading "N.N Annex X":

These Annexes cannot be accessed through the TOC due to title mismatches.

Did not have latest fixes to source.


Decoupled from Deprecated Commands

This makes guard-nanoc kind of simple (it skips the notifications that the current nanoc has deprecated).  I updated the specs as well, and everything passes.  I failed to create a topic branch, I'm kind of a Neanderthal regarding git sometimes.  Works with nanoc 3.2.2.

I forgot that the regex warning was handled in here too.  I noticed another pull request from September that fixes those as well.


Documentation confusion: It's there a way to load the models from a variable instead that from the files and use it later

In the documentation looks like the only way to load the models and pass it to the instance is from the files on the static folder:
await faceapi.nets.ssdMobilenetv1.loadFromUri('/models')
But i have observed that we can use a Float32Array but i can't find a way to pass it to the faceapi instance, this is what i have tried:
let net = new faceapi.TinyFaceDetector()
let weights = await faceapi.fetchNetWeights('/models/tiny_face_detector_model-shard1.weights')
console.log('weights')
console.log(weights)
net.load(weights)
console.log('net')
console.log(net)
await faceapi.nets.tinyFaceDetector.loadFromWeightMap(weights) -> In this line fails
const detection = await faceapi.detectSingleFace(contextForFaceDetection.canvas, new faceapi.TinyFaceDetectorOptions({ scoreThreshold: configuration.FACE_SCORE_ADMISSION }))
But i get:

Can someone help me to clarify this, in the documentation is not so clear how i can load the model without using the methods to access to the files?The model weights a lot and i wuold like so save it into a variable to reuse it using the localStorage or the IndexedDB

@lagcamgc has your problem been solved? I found tiny_face_detector_model.bin and ssd_mobilenetv1_model.bin seems to have some problems:
import * as faceapi from "face-api.js";

const float32Array_1 = await faceapi.fetchNetWeights(
  "/weights/face_landmark_68_tiny_model.bin"
);
console.log(float32Array_1); // [6.35521664824198e+30, -1.8255705378378978e-13, ...]

const float32Array_2 = await faceapi.fetchNetWeights(
  "/weights/tiny_face_detector_model.bin"
);
console.log(float32Array_2); // Error: byte length of Float32Array should be a multiple of 4

and all models will fail to load:
const net = new faceapi.FaceLandmark68TinyNet();
const float32Array_1 = await faceapi.fetchNetWeights(
  "/weights/face_landmark_68_tiny_model.bin"
);
await net.load(float32Array_1); // Error: Based on the provided shape, [1,1,32,32], the tensor should have 1024 values but has 578

I am using the module provided by @vladmandic/face-api . Even though I am using the face-api.js module, I still make the above error. Am I missing something?

Hello! @awdr74100 at the end of the day i end up using a library called picojs, so short answer... no, i was not able not make it work even with the help of the previous comment


Feat: add login form to landing page

I have added new input boxes for login username and password.
Everything should look perfect and work

Look s good

i wont believe it


"Find a product" action block

There are several places where we need to find food, for instance the home page (like "find a product") or any product list page (more like "ADD a product").
The goal is to implement a product search block:

that will give consistency to the app (same UI everywhere)
that will give control to all the possible product search features (internet, local database, scan, other lists, ...)
with a collapsible mode and a very distinctive look ("hey I need to find a product, oh there's the product search logo on a collapsed card, I just have to click here")
possibly with a FloatingActionButton on some pages

The implementation may be a card (like SmoothCard), or a modal bottom sheet.

That would look like that on home screen:

@M123-dev The whole point of this issue is the assumption that we need a "find/add a product" block, with instant access. Maybe this assumption is wrong, I give you that.
Scanning is indeed a key feature and is not hidden in the search bar, at least in my screenshot.
Regarding your legitimate concern about the block being hidden or scrolled out, the solution would be to include it in a SliverAppBar.

If by "instant access" you mean a widget on the homepage, I disagree with you and the button on the screenshot is not hidden but still built into the search widget. I think that is not good on the homepage, because as I said before it is not well accessible.
This kind of button I can imagine well in a modal bottom sheet after the "+" FAB on the listpages.

The scan button is now directly under the search, so I would say that the issue is resolved. If not feel free to reopen it.


[Rendering] Compact Input.ChoiceSet is not correctly rendered in High Contrast

Copied bug from: https://github.com/microsoft/AdaptiveCards/issues/6447
Details from original post:
Target Platforms
Other
SDK Version
1.2
Application Name
Microsoft Teams
Problem Description
The issue below is witnessed in the High Contrast Theme of Microsoft Teams Desktop Client.
The options available in the drop down menu (Input.ChoiceSet - "style": "compact") is not properly rendered/displayed. The Option 1 is displayed totally dark and the remaining options also turns dark when we select them. When these options turns dark, it is impossible to distinguish the option and the background.
Also, when I change the style of Input.ChoiceSet to "expanded", then the card is properly rendered and working as expected.
Screenshots
No response
Card JSON
{
  "type": "AdaptiveCard",
  "body": [
    {
      "type": "TextBlock",
      "text": "Select Options from Dropdown",
      "color": "accent",
      "size": "medium",
      "weight": "bolder"
    },
    {
      "type": "Input.ChoiceSet",
      "id": "teams",
      "placeholder": "Select multiple options",
      "isMultiSelect": true,
      "value": "${options}",
      "choices": [
        {
          "$data": "${CustomOptions}",
          "title": "${OptionName}",
          "value": "${OptionValue}"
        }
      ]
    },
    {
      "type": "ActionSet",
      "actions": [
        {
          "type": "Action.Submit",
          "title": "Proceed"
        },
        {
          "type": "Action.Submit",
          "title": "Cancel",
          "data": {
            "msteams": {
              "type": "messageBack",
              "displayText": "cancel",
              "text": "cancel"
            }
          }
        }
      ]
    }
  ],
  "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
  "version": "1.2"
}

Sample Code Language
No response
Sample Code
No response---
Document Details
⚠ Do not edit this section.It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 3fb4394d-25b1-8752-3996-fe3a2934732d
Version Independent ID: 6d391381-89d0-117c-27cc-00043bd26a36
Content: Cards reference - Teams
Content Source: msteams-platform/task-modules-and-cards/cards/cards-reference.md
Product: msteams
GitHub Login: @surbhigupta12
Microsoft Alias: surbhigupta12

Hi @ManuNswamy,
We are able to repro this issue. A bug has been raised for this and concerned team is looking into it

@ManuNswamy - We checked both in MS Teams desktop client and web client. The issue seems to be resolved now.

Thanks!


added some french words

i'm french so i know insults. please correct the file syntax if i did it wrong.

Please don't raise PRs to master.


Don't auto-complete feed username/password on Firefox

#153 Introduced HTTP Authentication support for feeds, which I have no problem with, but if you saved the credentials for Minuflux itself on the browser, they will be autocomplete on every new feed you add or edit.
According to https://developer.mozilla.org/en-US/docs/Web/Security/Securing_your_site/Turning_off_form_autocompletion#The_autocomplete_attribute_and_login_fields, Firefox doesn't support autocomplete="new-password", so this would require changing the form filed id.
Another option is setting autocomplete to off and each user setting signon.storeWhenAutocompleteOff on about:config (see here.

Using autocomplete="off" or autocomplete="new-password" doesn't change anything
Changing the input ID doesn't change anything
Using a different input name doesn't change anything

The only way I found to avoid Firefox autocomplete this damn field is to change the type to text instead of password and yes that sucks. See commit https://github.com/miniflux/miniflux/commit/8ee4280461aef523677a41a358e86f4918bcffa9.

The following is a pretty clunky workaround, but what if:

Keep the password form field as type password so it stays masked when used.
Hide the username and password form fields with CSS (display: none;).
Add a Requires Authentication checkbox at the top of the form.
Selecting the checkbox causes the INPUT fields to appear (and maybe sets their value to an empty string? Not sure.).
Server-side, the username and password field are ignored if the checkbox is not set.

This solution would prevent the credentials for Miniflux from being saved for a feed subscription and hiding the form fields gives the user a little less to stress about (behind the scenes they are being filled but the user doesn't see that and server-side they're ignored).

Looks good to me, but this will show the password without the dots. I don't think that's a security risk.
Thanks for the swift response @fguillot .

@dzaikos I'm not sure if displaying the input fields dynamically via Javascript prevent Firefox to autocomplete the password field (even if the value is reseted). This is something that need to be tested.

I don't think it does. Hiding the fields is just for the user's sake (they don't see the password field in and neither does anyone else).
The checkbox is where the magic happens. On the backend Miniflux would only save the username/password if the checkbox were selected (or, if unselected it would remove existing the username/password).
And since we're making the user click a checkbox when a feed requires authentication, we use that to show/hide those fields.

I can confirm this is now fixed, for Desktop and Mobile Firefox.
Thanks!


validator: add transitions

Implementation of SRP4.
Validation of transitions.
Here is a rule example:
{
    "auction": {
        "pki": {},
        "types": {
            "initState": {
                "transitions": {
                    "initialize" : [""]
                }
            },
            "OrderOnMarket": {
                "transitions": {
                    "sendOrder" : ["initState", "OrderOnMarket"]
                }
            },
            "OrderCanceled": {
                "transitions": {
                    "cancel" : ["initState", "OrderOnMarket"]
                }
            }
        }
    }
}

A chainscript type is the state.
Each state has a list of possible transitions defined as actionName and the list of allowed previous states.
An empty previous state is necessary to create the first link of a map
A final state is a state which is not defined in any allowed previous state.
A next PR will come once this PR will be merged to make transition validation mandatory.

This change is

Reviewed 10 of 10 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

validator/configloader_test.go, line 161 at r1 (raw file):

func TestLoadValidators_Error(t *testing.T) {

	t.Run("Missing link type", func(T *testing.T) {

Missing process rather than link type.

validator/transition.go, line 58 at r1 (raw file):

}

// Validate checks that the provided dignatures match the required ones.

I don't think this comment is up to date. If it was copy pasted, there was a typo (dignatures) in the original one!

validator/transition.go, line 65 at r1 (raw file):

	}

	transitions, found := tv.Transitions[link.Meta.Action]

I don't think we should rely on Action here. It's just there to be more user friendly in the rules.json but it's an implementation detail of the agent at this point. We should just check that the type parent of the parent belongs to one of the allowed ancestors. We might want to optimize the parsing of the configuration to optimize this lookup.

Comments from Reviewable

Review status: all files reviewed at latest revision, 3 unresolved discussions.

validator/configloader_test.go, line 161 at r1 (raw file):
Previously, such (Adrien Montfort) wrote…
Missing process rather than link type.

copy/paste was not perfect
Done.

validator/transition.go, line 58 at r1 (raw file):
Previously, such (Adrien Montfort) wrote…
I don't think this comment is up to date. If it was copy pasted, there was a typo (dignatures) in the original one!

Fixed

validator/transition.go, line 65 at r1 (raw file):
Previously, such (Adrien Montfort) wrote…
I don't think we should rely on Action here. It's just there to be more user friendly in the rules.json but it's an implementation detail of the agent at this point. We should just check that the type parent of the parent belongs to one of the allowed ancestors. We might want to optimize the parsing of the configuration to optimize this lookup.

Good point but I don't think action is just an agent implementation detail.
I think that the action should add some information on state so it can be verified by the schema validator but when a process has shortcuts, I do not think that we want to allow bypassing a part of the process.
For example in transition_test.go from createdProduct to signedFinalProduct, it is possible to approve but don't sign to be at the final state. In agent approve action will send an email to manager to explain why the procedure was bypassed. If we do not check action, we can lose this information if someone hacked the agent.
I understand your point but I think that if we do not check the couple prevState/Action, it is possible to lose traceability information. If we do not check the couple, I think we should remove Link.Meta.Action.

Comments from Reviewable

Review status: 7 of 10 files reviewed at latest revision, 1 unresolved discussion.

validator/configloader_test.go, line 161 at r2 (raw file):

func TestLoadValidators_Error(t *testing.T) {

	t.Run("Missing process type", func(T *testing.T) {

nit: it's just "Missing process" I think :)

validator/transition.go, line 65 at r1 (raw file):
Previously, alexppxela (Alexandre Thibault) wrote…
Good point but I don't think action is just an agent implementation detail.
I think that the action should add some information on state so it can be verified by the schema validator but when a process has shortcuts, I do not think that we want to allow bypassing a part of the process.
For example in transition_test.go from createdProduct to signedFinalProduct, it is possible to approve but don't sign to be at the final state. In agent approve action will send an email to manager to explain why the procedure was bypassed. If we do not check action, we can lose this information if someone hacked the agent.
I understand your point but I think that if we do not check the couple prevState/Action, it is possible to lose traceability information. If we do not check the couple, I think we should remove Link.Meta.Action.

I feel like it's a battle I'm starting to lose... @azuenko has been pushing for what you described but we had kinda decided to keep it simple for now.
I'm not sure I understand your example even though I can see the benefit of validating the couple prevState/Action (what @azuenko calls a "route"). I'm just worried this provides a false sense of added security. But I totally open to the discussion.
@azuenko , @t-bast, @jeremie-stratumn, @simonvadee what do you think?

Comments from Reviewable

validator/transition.go, line 65 at r1 (raw file):
Previously, such (Adrien Montfort) wrote…
I feel like it's a battle I'm starting to lose... @azuenko has been pushing for what you described but we had kinda decided to keep it simple for now.
I'm not sure I understand your example even though I can see the benefit of validating the couple prevState/Action (what @azuenko calls a "route"). I'm just worried this provides a false sense of added security. But I totally open to the discussion.
@azuenko , @t-bast, @jeremie-stratumn, @simonvadee what do you think?

some of the points from the discussion alexandre and I had :

we should not consider link.meta.action as a trustable source of information since it is modified in the agent.
if there are specific requirements to a transition validation (as in the above example with createdProduct), they will be validated by the validation language rather than on the transition name, which can be falsified.
the traceability information should always be available in link.state wether it's a "standard" procedure or a more "custom" one.

I agree that it introduce a security breach since we have no way of knowing which action was actually executed by the agent.

Comments from Reviewable

validator/configloader_test.go, line 161 at r2 (raw file):
Previously, such (Adrien Montfort) wrote…
nit: it's just "Missing process" I think :)

:face_with_head_bandage: :gun:

Comments from Reviewable

Review status: 7 of 10 files reviewed at latest revision, 1 unresolved discussion.

validator/transition.go, line 65 at r1 (raw file):
Previously, simonvadee (Simon Vadée) wrote…
some of the points from the discussion alexandre and I had :

we should not consider link.meta.action as a trustable source of information since it is modified in the agent.
if there are specific requirements to a transition validation (as in the above example with createdProduct), they will be validated by the validation language rather than on the transition name, which can be falsified.
the traceability information should always be available in link.state wether it's a "standard" procedure or a more "custom" one.

I agree that it introduce a security breach since we have no way of knowing which action was actually executed by the agent.

My point is that it's not really a security breach since this field is never reliable... It would be only if the agent was on a trusted enclave or something...

Comments from Reviewable

validator/transition.go, line 65 at r1 (raw file):
Previously, such (Adrien Montfort) wrote…
My point is that it's not really a security breach since this field is never reliable... It would be only if the agent was on a trusted enclave or something...

@such you win ;)
We spoke with @azuenko and @simonvadee and we said that we need to keep rules as simple as possible to begin and enrich it later if needed. so, I'll change the transitions as.
{
    "auction": {
        "types": {
            "OrderOnMarket": {
                "transitions": ["initState", "OrderOnMarket", ""]
            },
            ...
}

If action name is needed by validation UI, it could add more information in json.

Comments from Reviewable

Review status: 7 of 10 files reviewed at latest revision, 1 unresolved discussion.

validator/transition.go, line 65 at r1 (raw file):
Previously, alexppxela (Alexandre Thibault) wrote…
@such you win ;)
We spoke with @azuenko and @simonvadee and we said that we need to keep rules as simple as possible to begin and enrich it later if needed. so, I'll change the transitions as.
{
    "auction": {
        "types": {
            "OrderOnMarket": {
                "transitions": ["initState", "OrderOnMarket", ""]
            },
            ...
}

If action name is needed by validation UI, it could add more information in json.

LGTM

Comments from Reviewable

Reviewed 10 of 10 files at r1.
Review status: 7 of 10 files reviewed at latest revision, 2 unresolved discussions.

validator/transition_test.go, line 87 at r1 (raw file):

	require.NoError(t, err)

	append := func(prevLink *cs.Link, state, action string) *cs.Link {

nit: pick an other name since append is already defined in the standard lib

Comments from Reviewable

Review status: 4 of 10 files reviewed at latest revision, 2 unresolved discussions.

validator/transition_test.go, line 87 at r1 (raw file):
Previously, simonvadee (Simon Vadée) wrote…
nit: pick an other name since append is already defined in the standard lib

true

Comments from Reviewable

Reviewed 1 of 3 files at r2, 5 of 5 files at r3.
Review status: all files reviewed at latest revision, 1 unresolved discussion.

Comments from Reviewable

Review status: all files reviewed at latest revision, all discussions resolved, some commit checks failed.

Comments from Reviewable


Feature/gateway breadcrumbs

Will use appendedBreadcrumbs to check if it's the gateway details page. Will remove check for displayName as it's no longer required.


How to call POST method from within a generator (sagas.js)?

Hello folks - hopefully an easy one,
I'm following along the default demo app but now trying to make a POST request from within sagas.js (app/containers/HomePage)
How can I pass options e.g. {method: 'POST'} to the following call?:
const repos = yield call(request, requestURL);
The comments in utils/request.js suggest initialising request with a url and options but I'm not sure how to do this within a generator function:
/**
 * Requests a URL, returning a promise
 *
 * @param  {string} url       The URL we want to request
 * @param  {object} [options] The options we want to pass to "fetch"
 *
 * @return {object}           An object containing either "data" or "err"
 */
export default function request(url, options) {
  return fetch(url, options)
    .then(checkStatus)
    .then(parseJSON)
    .then((data) => ({ data }))
    .catch((err) => ({ err }));
}

You can simply pass in more options arguments and they'll be passed through!
const postRequest = yield call(request, requestURL, {
  method: 'POST',
});

See the redux-saga documentation about the declarative effects: https://github.com/yelouafi/redux-saga/blob/master/docs/basics/DeclarativeEffects.md

Thanks @mxstbr . To anyone else reading this and still having issues ensure the api is sending the data out in the right format e.g. using res.json as opposed to for example res.send

P.S. If you can't see the body of the request on the server req.body then ensure:

body-parser is installed and used before your api in your server.js file
explicitly set header info and stringify body in sagas.js as per the fetch api docs: https://github.com/github/fetch#post-json

Thanks @kunal-mandalia !
"stringify body in sagas.js" -- this solved my problem. I've been working on this the whole night.

Hello Guys,
I'm trying to call an API by sending headers in the request, but as I noticed in the chrome network section ( headers -> Request Headers), AuthenticationToken is missing.
Here is my code How I'm passing headers
export` function* getProducts() {
  // Select username from store
  const requestURL = API_URL + `GetAllProducts?PageNo=1&PageSize=2`;
  const headers = {
    method: 'GET',
    mode: 'no-cors',
    headers: {
      'AuthenticationToken': '19d01592-ec4e-433a-9456-443373675952', // Need to get from store once login done
      'Content-Type': 'application/json'
    },
  };

  try {
    // Call our request helper (see 'utils/request')
    const products = yield call(request, requestURL, headers);
    yield put(productsLoaded(products));
  } catch (err) {
    yield put(productsLoadingError(err));
  }
}

Could you please tell me what I'm missing, suggest me if there any public repo which is using react boilerplate.

@bharadwajag try including credentials: 'include' in your header i.e:
const headers = {     method: 'GET',     credentials: 'include',     mode: 'no-cors',     headers: {       'AuthenticationToken': '19d01592-ec4e-433a-9456-443373675952', // Need to get from store once login done       'Content-Type': 'application/json'     },   };

@kunal-mandalia
Thanks for the response, your answer works for me, but we enabled cors at server end too.


Lots of goodies (including SSL support for OpenFlow connections)

Bug fixes in SFP:
(1) check switch DPID when modifying a flow. We might need to remove it from another switch (an explicit ofp_flow_delete_strict) if we're migrating the flow to another switch.
(2) allow an empty string for actions/instructions or a missing key --> drop
MatchUtils bug fix:
(1) allow 65534= controller, etc. TODO: rework to work for int port nums instead of just shorts. Also allow keywords such as "controller", "any", etc like we do for output port(s).
Serializer bug fixes:
(1) only try to serialize table, group, cookie mask fields if OF1.1+
(2) if empty instructions or actions --> drop, end the JSON object in the proper place
SSL support for OpenFlow connections =)
To use:
floodlightdefault.properties has new keys included to set OFSwitchManager SSL config options.
useSsl = YES | TRUE | YEP | JA | STIMMT --> yes, please use SSL (case-insensitive)
useSsl = anything else --> no, we won't use SSL today
keyStorePath = the absolute path of the JKS keystore e.g. /Users/ryan/Desktop/floodlight/keystore.jks
keyStorePassword = the optional plaintext keystore password (TODO is there a way to specify this NOT in plaintext? I can't think of a way unless we use a hash or prompt for it.)

wow. SSL support. nice.

I forgot to ask: are you doing the X509/Certificate authentication or is it
just encryption?

Rob
.

On Fri, Mar 13, 2015 at 3:36 PM, Jason Parraga<EMAIL_ADDRESS>wrote:

wow. SSL support. nice.
—
Reply to this email directly or view it on GitHub
https://github.com/floodlight/floodlight/pull/501#issuecomment-79496118.

Certificate. I self-signed for my tests, but I've heard there's a free signing site now.
Sent from my iPhone
--
Ryan Izard
Graduate Research/Teaching Assistant
306B Fluor Daniel Building
ECE Department, Clemson University
Clemson, SC 29634
<EMAIL_ADDRESS>
On Mar 13, 2015, at 6:41 PM, Rob Sherwood<EMAIL_ADDRESS>wrote:
I forgot to ask: are you doing the X509/Certificate authentication or is it
just encryption?

Rob
.

On Fri, Mar 13, 2015 at 3:36 PM, Jason Parraga<EMAIL_ADDRESS>wrote:

wow. SSL support. nice.
—
Reply to this email directly or view it on GitHub
https://github.com/floodlight/floodlight/pull/501#issuecomment-79496118.

—
Reply to this email directly or view it on GitHub.


Add options to customize vim indentation options

Hello.
I have added an option to set any vim option when indentation is detected.
Right now the options to set are hard coded, but I do not think this is appropriate from a customizability standpoint.
Because vim's indentation-related settings are so complex, I thought it best to allow users to set them freely.
There are many vim users who have the tab width set to 8 or have not changed it.
I do not think it is good from the user's point of view to change the 'tabstop' when spaces are detected.
For example, projects such as gcc and vim use an indentation style that mixes tabs and spaces, but only assumes that the tab width is 8.
The old-fashioned GNU style seems to use this indent style.
Therefore, making the tab width the same as the indent width will mess up the layout.
You can see this by opening the following code in vim. (Please disable modeline in vim project)
https://github.com/gcc-mirror/gcc/blob/8f8db5553935edcb4731db32279418ca37e1f094/libgomp/config/posix/sem.c#L73-L76
https://github.com/vim/vim/blob/1bf1bf569b96d2f9b28e0cce0968ffbf2fb80aac/src/alloc.c#L97-L102
Another advantage of separating 'tabstop' from 'shiftwidth' is that if a tab is mistakenly entered, it is easier to tell that it is a tab without using :set list. The same size makes it impossible to distinguish between tabs and spaces.
For example, vim-sleuth does not change it.
The vim help below explains why.
:h 'tabstop'
:h usr_25.txt
:h usr_30.txt

I am going to define the default values as follows and change the following options.
default: 2 spaces, 8-width tab
opt.tabstop = 8          -- default
opt.softtabstop = -1  -- same as 'shiftwidth'
opt.shiftwidth = 2      -- indent is 2
opt.expandtab = true -- tab is not used

      on_tab_options = {
        ["expandtab"] = false,
        ["softtabstop"] = 0, -- make disabled
        ["shiftwidth"] = 0,   -- same as 'tabstop', Currently this is not set, so 'shiftwidth' is 2. I want to change this option when detecting tab.
      },
      on_space_options = {
        ["expandtab"] = true, -- same as default
        ["shiftwidth"] = "detected", -- only this option will be changed
        ["softtabstop"] = -1, -- same as default
      },

This is advantageous from a performance standpoint because it reduces the number of options to be set as much as possible.
Currently the same value is set for 'tabstop', 'softtabstop', and 'shiftwidth' when spaces are detected, but If 'softtabstop' is set to -1, there is no need to set it. or if 'tabstop' and 'softabstop' are equal, 'softtabstop' is almost no point, so it can be set to 0 or 1 instead.
BTW, The editorconfig that comes with neovim has almost the same configuration values.
(The fact that 'tabstop' is also changed is a result of following the editorconfig specification.)
https://github.com/neovim/neovim/blob/master/runtime/lua/editorconfig.lua#L50-L71
Also, the specific options to be set will be written in the README, which will make it easier to understand.
Default values are to be taken over from the current settings for compatibility reason.
This PR also fixes
PR:  #9
Issue: #12
also related
PR: #14

@NMAC427
I force pushed because other PR was merged and conflicted recently, could you please consider this PR as well?
This PR is related to some other Issues and PRs and may be able to close them.
If you don't like this approach, I would be happy to consider other approaches.
At least when tabs are detected, changing only the tabstop is not enough, usually shiftwidth must be set to 0 at the same time.
If shiftwidth is not set to a value that matches tabstop or to 0, then it end up with strange indentation with the > and < operators.
I have written a lengthy explanation in the PR description, but the current hard-coded indentation settings are not appropriate for this reason alone.
It is better to give plugin users freedom of setting.

Sorry for not getting to this earlier. These changes look very reasonable. I also really like that it also adresses #12.
Thanks for the contribution!

Thanks!


[FEATURE]: Adding Forgot Password Option

Users often forget passwords. A "Forgot Password" option enables them to quickly reset it, making it easier to regain access without contacting support.
It will improve overall users experience.

Hey @Nelcy17 , You can proceed!

I'm closing this issue due to inactivity.


Scheduler - Release plan details are incorrect when no release plan selected

Release Plan: [[Release Plan ID]]([Release Plan Link])
[Azure Cosmos DB - Copilot in Azure Cosmos DB] API Review · Issue #321 · azure-sdk/TestingForEngagementExperience (github.com)
It should show Not selected

Closing it. Not reproducible now.


Use a regex instead of a string to filter ToString error

Unsure why the ignoreErrors block isn't filtering the string document.getElementsByClassName.ToString is not a function from Sentry. Trying with a (shortened) regex instead (for consistency with /Blocked a frame with origin/, which appears to be working).

Did you figure out a way to test locally?


Fix the package url in go.mod

Mac:gogogo chengli.ycl$ go get<EMAIL_ADDRESS>go get<EMAIL_ADDRESS>parsing go.mod:
	module declares its path as: github.com/rancher/kine
	        but was required as: github.com/ibuildthecloud/kine

This repo is supposed to be github.com/rancher/kine.  I've moved it there now.


LuaBind Interopability

Hey, I am porting a project from LuaBind to Sol3 and was wondering if I could get some help.
We've got a lot of old scripts, and a long history of modding support, so I'm trying to change as little as possible to ensure compatibility.
I've got the usertypes set up correctly, but I've been having issues where Sol is a little too strict with what we're doing:
-- "Test" is a created Sol usertype of type "Activity"
-- We're trying to define an UpdateActivity() function on it, which from the C++ side we can call to tell this object to update

-- UpdateActivity isn't in the lua binding, but we call it from the C++ side
-- Sol doesn't like this, because sol::meta_function::new_index isn't defined

-- ERROR: Data/Base.rte/Activities/Test.lua:7: sol: cannot set (new_index) into this object: no defined new_index operation on usertype
function Test:UpdateActivity()
        -- Sol doesn't like these either
        if self.ValueNotInCppBinding == nil then
	        self.ValueNotInCppBinding = 0;
        end
end

Effectively in these cases we're using Lua in "inherit" from the CPP object instead of just binding to it. In LuaBind this worked fine, and accessing any value that wasn't on the object would just work like any normal lua table.
However, this dies due to a lack of sol::meta_function::new_index or sol::meta_function::index being defined. I could define these manually, but I don't want to add a bunch of wrapper stuff to store and track all these objects on the C++ side - I'd prefer to just let Lua handle it all.
I maybe could define these objects as tables, but then we miss out on all the automagic enrolments. It also ended up with a lot of compile errors when I tried this.
Is there a way to set sol::meta_function::new_index/index to fallback to the normal Lua behaviour? Or is there a better way to do this that I'm missing?

Do I need to use https://github.com/ThePhD/sol2/blob/develop/examples/source/dynamic_object.cpp for this?


Fix warnings in unit-tests tests

Fixes #6155

@puhuk ci failures are related

Hmm, why it raises typo error in test_models.py when I just revert to origin code

@puhuk it is unrelated as main branch is broken : https://app.circleci.com/pipelines/github/pytorch/vision/18344/workflows/d0222980-4837-4c46-a9bf-d9cc4be80051/jobs/1484167

@vfdev-5 Thank you for the feedback!

@puhuk there are few similar warnings:
test/test_models.py::test_classification_model[cpu-googlenet]
  /root/project/torchvision/models/googlenet.py:47: FutureWarning: The default weight initialization of GoogleNet will be changed in future releases of torchvision. If you wish to keep the old behavior (which leads to long initialization times due to scipy/scipy#11299), please set init_weights=True.
    warnings.warn(

test/test_models.py::test_classification_model[cpu-inception_v3]
  /root/project/torchvision/models/inception.py:43: FutureWarning: The default weight initialization of inception_v3 will be changed in future releases of torchvision. If you wish to keep the old behavior (which leads to long initialization times due to scipy/scipy#11299), please set init_weights=True.
    warnings.warn(

Can you try to fix them as well ? Thanks


Jar visuals

Some details discussed in Call 16. Probably more discussions needed to sort out the exact details.

This also implies other related visuals on other screens which we'll best handle as separate issues. This issue is just an umbrella for tracking purposes. Once we get to work split it up into individual sub issues.

Follow up issues: #328 and #340


Get magento versions from github

Hey,
I tried using this, but Magento doesn't offer the direct links any more.
I found a mirror on GitHub, I think it's safe to use this.

Thanks for this! :)


Fix #15 by opening the browser when the inspector task is executed

This commit fixes #15 by using the module open, which will open a brower
with a given URL. Based on
https://github.com/stevelacy/gulp-open#optionsapp, Chrome's binary is
different on each OS, so the switch, falling back to 'firefox' in case
of a different OS.

modified:   index.js

Adding the modules OS and Open.
Making the log message a bit more readable.
Finding out which binary to use
Opening the URL.

modified:   package.json

Updated with "npm install --save open"

@vesparny I love the plugin and I'm giving something back to it!!!  Thanks!

@marcellodesales thanks for your PR, anyway I think the goal here is too keep plugins as small as possible.
If you need the open module you can easily create another gulp task for this.

@vesparny Fair enough.. thanks!


Migrate CSS fixes to SCSS

Migrate rough css changes from here to scss.

Honestly, having it hotloaded is still the best idea for now, especially with the ui changing seemingly every update.


Maybe automatically check for presence of feedback.yml in the current package and use it in preference to the global one?

Something like this, but only when the file exists
---
code: |
  feedback_form = f"{user_info().package}:feedback.yml"

This requires writing a function to check for particular files in the current package. Can we re-use the playground code we have in a few places, like https://github.com/SuffolkLITLab/docassemble-ALKilnInThePlayground/blob/main/docassemble/ALKilnInThePlayground/data/questions/run_alkiln_tests.yml

I don't think the file you linked has any reusable code; it mostly has a lot of subprocess.call(["npm", ...]) stuff, and the lines it does have are playground specific (SavedFile(user_info().id, fix=True, section='playgroundsources')).
https://github.com/SuffolkLITLab/docassemble-InterviewStats/blob/c42376b1cdb7f05a4a89c76c06c68dd4edf5c016/docassemble/InterviewStats/cache_geography.py#L48-L50 might be useful on installed packages, it goes to the data/sources folder relative to a python module, would just have to change that to data/questions instead. Trying to do both playground and installed stuff will be a bit difficult though.

could justify a new module in ALToolbox to scan the current package for various kinds of files. That's a useful tool in general; "quining" our packages is a nice way to get lots of different kinds of dynamic behavior.


disable standard globals

Is it possible to disable standard globals. Specifically I'd like to disable the length functions; table.getn and string.len to force using the operator #.

Right now it's not possible to disable specific fields of globals. It will be in the next version, I plan to work on it in October.

Thx. Consider this a feature request then 😄

(or close if you feel that's more appropriate)

I'm slowly working on a way to fully describe which fields of globals are allowed and which are not, in config. But there should be a way to tweak this with inline options, too. Most likely globals option will be changed to accept fields, and there will also be no-globals or not-globals option to prohibit a field or a global. For instance, luarocks-3 wants to ensure that require isn't used after some initial part of each core module, and it could use -- luacheck: no global require to verify that.

On dev branch:
-- luacheck: std max, not globals string.len table.getn
table.insert() -- OK
table.getn() -- accessing undefined field 'getn' of global 'table'
string.find() -- OK
string.len() -- accessing undefined field 'len' of global 'string'

It's still possible to use ("foo"):len() but detecting that in the general case requires type inference.

0.19.0 released.

:+1:


SET_DONOMINATION_ROUTE not working.

I updated to the latest version and SET_DENOMINATION_ROUTE doesn't seem to work. The old version worked just fine.

@GreedyA1 Can you enable debug and send logs

@GreedyA1 please try master branch, it should work

just pulled latest changes.
getting error, trying to run example.js

here are the logs from debug mode.
2020-09-27T07:03:54.589Z LOG COM <- 7f0001116608 SYNC 0
2020-09-27T07:03:54.611Z LOG COM -> 7f0001f0200a | RAW
2020-09-27T07:03:54.612Z LOG COM -> 7f0001f0200a SYNC
2020-09-27T07:03:54.616Z LOG { success: true, status: 'OK', command: 'SYNC', info: {} }
2020-09-27T07:03:54.717Z LOG COM <- 7f000206061b94 HOST_PROTOCOL_VERSION 0
2020-09-27T07:03:54.739Z LOG COM -> 7f0001f0200a | RAW
2020-09-27T07:03:54.739Z LOG COM -> 7f0001f0200a HOST_PROTOCOL_VERSION
2020-09-27T07:03:54.739Z LOG { success: true,
  status: 'OK',
  command: 'HOST_PROTOCOL_VERSION',
  info: {} }
2020-09-27T07:03:54.842Z LOG COM <- 7f80094a5332000000000000b707 SET_GENERATOR 0
2020-09-27T07:03:54.867Z LOG COM -> 7f8001 | RAW
2020-09-27T07:03:54.883Z LOG COM -> f43800 | RAW
2020-09-27T07:03:54.883Z LOG COM -> 7f8001f43800 SET_GENERATOR
2020-09-27T07:03:54.883Z LOG { success: false,
  status: 'PARAMETER_OUT_OF_RANGE',
  command: 'SET_GENERATOR',
  info: {} }
2020-09-27T07:03:54.984Z LOG COM <- 7f00094bf1270000000000004816 SET_MODULUS 0
2020-09-27T07:03:55.011Z LOG COM -> 7f0001f4 | RAW
2020-09-27T07:03:55.027Z LOG COM -> 3b8a | RAW
2020-09-27T07:03:55.027Z LOG COM -> 7f0001f43b8a SET_MODULUS
2020-09-27T07:03:55.027Z LOG { success: false,
  status: 'PARAMETER_OUT_OF_RANGE',
  command: 'SET_MODULUS',
  info: {} }
2020-09-27T07:03:55.128Z LOG COM <- 7f80094c4b1100000000000091b3 REQUEST_KEY_EXCHANGE 0
2020-09-27T07:03:55.203Z LOG COM -> 7f8009f008 | RAW
2020-09-27T07:03:55.219Z LOG COM -><PHONE_NUMBER>0000092b | RAW
2020-09-27T07:03:55.219Z LOG COM -> 7f8009f00809000000000000092b REQUEST_KEY_EXCHANGE
2020-09-27T07:03:55.219Z LOG { success: true,
  status: 'OK',
  command: 'REQUEST_KEY_EXCHANGE',
  info: { key: [ 8, 9, 0, 0, 0, 0, 0, 0 ] } }
2020-09-27T07:03:55.222Z LOG AES encrypt key: 0x6745230167452301671e000000000000
2020-09-27T07:03:55.222Z LOG
2020-09-27T07:03:55.223Z LOG { fixedKey: '123456701234567LL',
  generatorKey: 12883,
  modulusKey: 10225,
  hostRandom: 2627,
  hostIntKey: Integer { value: 4427n },
  slaveIntKey: Integer { value: 2312n },
  key: Integer { value: 7783n } }
2020-09-27T07:03:55.223Z LOG
2020-09-27T07:03:55.325Z LOG COM <- 7f00117e7681325e452ebfc12cd55803bc89b5e289e9 GET_SERIAL_NUMBER 0
2020-09-27T07:03:55.363Z LOG COM -> 7f00117eee8b9f51e9c9ad6b | RAW
2020-09-27T07:03:55.378Z LOG COM -> 044a51275be18a106056 | RAW
2020-09-27T07:03:55.379Z LOG COM -> 7f00117eee8b9f51e9c9ad6b044a51275be18a106056 GET_SERIAL_NUMBER
2020-09-27T07:03:55.379Z LOG Decrypted:<PHONE_NUMBER>f0002c1e74e3840eebb354
2020-09-27T07:03:55.379Z LOG { success: true,
  status: 'OK',
  command: 'GET_SERIAL_NUMBER',
  info: { serial_number: 2891380 } }
2020-09-27T07:03:55.480Z LOG SERIAL NUMBER: 2891380
2020-09-27T07:03:55.480Z LOG COM <- 7f80117e0be6944ed93b3fcc90390de77e29d1228205 SETUP_REQUEST 1
2020-09-27T07:03:55.506Z LOG COM -> 7f | RAW
2020-09-27T07:03:55.522Z LOG COM -> 80517eba23a21fe3e3fc80ebd15f | RAW
2020-09-27T07:03:55.538Z LOG COM -> 413613bc2e7099f9e4c2a22bb235 | RAW
2020-09-27T07:03:55.554Z LOG COM -> 35c2743ebaae1267189bdcf0f92b | RAW
2020-09-27T07:03:55.570Z LOG COM -> f81298e73dfefd9be6ca6ad1aabe | RAW
2020-09-27T07:03:55.586Z LOG COM -> 339d73d0d9f2551a61cfce41e3c9 | RAW
2020-09-27T07:03:55.602Z LOG COM -> 36afb2218ceed068a87aa63ed706 | RAW
2020-09-27T07:03:55.618Z LOG COM -> bf | RAW
2020-09-27T07:03:55.619Z LOG COM -> 7f80517eba23a21fe3e3fc80ebd15f413613bc2e7099f9e4c2a22bb23535c2743ebaae1267189bdcf0f92bf81298e73dfefd9be6ca6ad1aabe339d73d0d9f2551a61cfce41e3c936afb2218ceed068a87aa63ed706bf SETUP_REQUEST
2020-09-27T07:03:55.619Z LOG Decrypted:<PHONE_NUMBER>f0063034353647454c00000106050a143264c80202020202020000640647454c47454c47454c47454c47454c47454c050000000a000000140000003200000064000000c80000003c359408
2020-09-27T07:03:55.620Z LOG { success: true,
  status: 'OK',
  command: 'SETUP_REQUEST',
  info:
   { unit_type: 'SMART payout fitted',
     firmware_version: '4.56',
     country_code: 'GEL',
     value_multiplier: 1,
     channel_value: Uint8Array [ 5, 10, 20, 50, 100, 200 ],
     channel_security: Uint8Array [ 2, 2, 2, 2, 2, 2 ],
     real_value_multiplier: 100,
     protocolVersion: 6,
     expanded_channel_country_code: [ 'GEL', 'GEL', 'GEL', 'GEL', 'GEL', 'GEL' ],
     expanded_channel_value: [ 5, 10, 20, 50, 100, 200 ] } }
2020-09-27T07:03:55.721Z LOG COM <- 7f00117e28133c7933941e885235135f89a8abac692d SET_DENOMINATION_ROUTE 2
2020-09-27T07:03:55.746Z LOG COM -> 7f | RAW
2020-09-27T07:03:55.762Z LOG COM -> 00117e43de43b39c15ad5d35f38d | RAW
2020-09-27T07:03:55.778Z LOG COM -> 56fe9c145ee7bd | RAW
2020-09-27T07:03:55.779Z LOG COM -> 7f00117e43de43b39c15ad5d35f38d56fe9c145ee7bd SET_DENOMINATION_ROUTE
2020-09-27T07:03:55.779Z LOG Decrypted:<PHONE_NUMBER>f50959f452e910376bd6fa
2020-09-27T07:03:55.779Z LOG { success: false,
  status: 'COMMAND_CANNOT_BE_PROCESSED',
  command: 'SET_DENOMINATION_ROUTE',
  info: { errorCode: undefined, error: 'Unknown error' } }
2020-09-27T07:03:55.880Z LOG { success: false,
  status: 'COMMAND_CANNOT_BE_PROCESSED',
  command: 'SET_DENOMINATION_ROUTE',
  info: { errorCode: undefined, error: 'Unknown error' } }
2020-09-27T07:03:55.880Z LOG COM <- 7f80117eb174cd8b8ca89eeac2e533d995f02cf52364 ENABLE 3
2020-09-27T07:03:55.906Z LOG COM -> 7f | RAW
2020-09-27T07:03:55.922Z LOG COM -> 80117eb1e7cfdb80a92ddc764077 | RAW
2020-09-27T07:03:55.938Z LOG COM -> b21ee2073e4c14 | RAW
2020-09-27T07:03:55.939Z LOG COM -> 7f80117eb1e7cfdb80a92ddc764077b21ee2073e4c14 ENABLE
2020-09-27T07:03:55.939Z LOG Decrypted:<PHONE_NUMBER>f0b17236d044747f916c2c
2020-09-27T07:03:55.939Z LOG { success: true, status: 'OK', command: 'ENABLE', info: {} }
2020-09-27T07:03:56.040Z LOG COM <- 7f00117e16287476716dbe2158e5e88b0b0f5f368cbf POLL 4
2020-09-27T07:03:56.040Z LOG GO!!!
2020-09-27T07:03:56.066Z LOG COM -> 7f00 | RAW
2020-09-27T07:03:56.082Z LOG COM -> 117ea2f32882f352dbbd33944015 | RAW
2020-09-27T07:03:56.098Z LOG COM -> d5f220d64365 | RAW
2020-09-27T07:03:56.098Z LOG COM -> 7f00117ea2f32882f352dbbd33944015d5f220d64365 POLL
2020-09-27T07:03:56.099Z LOG Decrypted:<PHONE_NUMBER>f048a3e27eb0182027299a
2020-09-27T07:03:56.099Z LOG { success: true, status: 'OK', command: 'POLL', info: {} }
2020-09-27T07:03:56.200Z LOG COM <- 7f80117e9037dd1fbbb0f2c9cf8bd92fb98881eebafb POLL 5
2020-09-27T07:03:56.226Z LOG COM -> 7f80 | RAW
2020-09-27T07:03:56.242Z LOG COM -> 117e01206f6e51eb4d86b3099a4c | RAW
2020-09-27T07:03:56.258Z LOG COM -> 93da7a5b7547 | RAW
2020-09-27T07:03:56.258Z LOG COM -> 7f80117e01206f6e51eb4d86b3099a4c93da7a5b7547 POLL
2020-09-27T07:03:56.259Z LOG Decrypted:<PHONE_NUMBER>f0883b05dc47b546adeca1

btw, the version we are using is commit 24c3d3ba63c8d77a3550d2fe13acd9a95ac7cdad.

@GreedyA1 is your fixed key correct?
123456701234567LL

@kybarg yes that is the key in my code. couldn't run example.js of master because of above error.

Does the latest commit run consistently with NV200+Smart Payout? The issue might be with the type of device we are using, if for instance you’ve optimized the code for nv11

@GreedyA1 are you sure this is code set on your device?

@GreedyA1 are you sure this is code set on your device?

Fixed key is<PHONE_NUMBER>34567LL
Please see the log by @GreedyA1  above

Which model did you test the latest version on? We are using NV200 fitted with the Smart Payout

just pulled latest changes.
getting error, trying to run example.js

The 'BigInt' is not supported until Node.js 10.4.0
We recommend that you update your Node.js version

@GreedyA1 are you sure this is code set on your device?

Fixed key is<PHONE_NUMBER>34567LL
Please see the log by @GreedyA1 above

You need use '0123456701234567' fixedKey
'123456701234567LL'  is the 'long long' data type of the C ++ language

I am experiencing the same issues with SET_DENOMINATION_ROUTE and GET_DENOMINATION_ROUTE. While other commands work fine (e.g. GET_ALL_LEVELS and SET_CHANNEL_INHIBITS).
COM <- 7f00117e4df83bf7a192f8bcfbc05dbcede7bdbcc72d SET_DENOMINATION_ROUTE 2
COM -> 7f00117e56619eebddbd2dfb68628a1acc01140b6e87 | RAW
COM -> 7f00117e56619eebddbd2dfb68628a1acc01140b6e87 SET_DENOMINATION_ROUTE
Decrypted:<PHONE_NUMBER>f57b2ddd4d4bf7da52eede
{
  success: false,
  status: 'COMMAND_CANNOT_BE_PROCESSED',
  command: 'SET_DENOMINATION_ROUTE',
  info: { errorCode: undefined, error: 'Unknown error' }
}
COM <- 7f80117e8900a7d6d5325ad5fbd7268896b0fef4c251 GET_DENOMINATION_ROUTE 3
COM -> 7f80117e312c18cbd77c82367d8c1f59a9f6736f25b5 | RAW
COM -> 7f80117e312c18cbd77c82367d8c1f59a9f6736f25b5 GET_DENOMINATION_ROUTE
Decrypted:<PHONE_NUMBER>f57ec153b6309f9839b23d
{
  success: false,
  status: 'COMMAND_CANNOT_BE_PROCESSED',
  command: 'GET_DENOMINATION_ROUTE',
  info: { errorCode: undefined, error: 'Unknown error' }
}
COM <- 7f00117ecda0e64f8201cab7c996081b93e7310ad38a SET_CHANNEL_INHIBITS 4
COM -> 7f00117e6928f125b7ea1ff63d82c83e2ee7beefc677 | RAW
COM -> 7f00117e6928f125b7ea1ff63d82c83e2ee7beefc677 SET_CHANNEL_INHIBITS
Decrypted:<PHONE_NUMBER>f052e8b9877e4686a2099f
{
  success: true,
  status: 'OK',
  command: 'SET_CHANNEL_INHIBITS',
  info: {}
}
COM <- 7f80117eb9afce7690b172e5105a055f5c29ad88481e GET_ALL_LEVELS 5
COM -> 7f80517e05377367a66248d109ed22a4d191e68911494d78925d2551e7fb16de49387d79dd14998387b72b535c04f3aed856109a0076e0e5cb115a98dd11dbd71956c49d1e06c52246f1b2818b4d8ff917d69382af50 | RAW
COM -> 7f80517e05377367a66248d109ed22a4d191e68911494d78925d2551e7fb16de49387d79dd14998387b72b535c04f3aed856109a0076e0e5cb115a98dd11dbd71956c49d1e06c52246f1b2818b4d8ff917d69382af50 GET_ALL_LEVELS
Decrypted:<PHONE_NUMBER>f0070000f40100004555520000e80300004555520000d00700004555520000881300004555520000102700004555520000204e0000455552000050c300004555523f148f0bce8024f959c3
{
  success: true,
  status: 'OK',
  command: 'GET_ALL_LEVELS',
  info: {
    counter: {
      '1': [Object],
      '2': [Object],
      '3': [Object],
      '4': [Object],
      '5': [Object],
      '6': [Object],
      '7': [Object]
    }
  }
}

Using NV200, master branch and Windows 10.
Also unrelated but shouldn't https://github.com/skokov3812/encrypted-smiley-secure-protocol/blob/master/src/utils.js#L193 be protocol_version instead?

It was actually fine in 33bda2a93700b80cdb430cb1846c148382586771 but then it was reverted for some reason in ef76b97fd464c124fd9079610dc3142f3d59057f.

It was actually fine in 33bda2a but then it was reverted for some reason in ef76b97.

Thx. Will post as soon as we test it.
We are also having some issues with receiving “stacked” and “note_stored_in_payout” events. We occasionally see them, but most of the time, nothing comes in after the “credit_note” event.
Do you receive “stack” and “note_stored_in_payout” events?

@GreedyA1 are you sure this is code set on your device?

Fixed key is<PHONE_NUMBER>34567LL
Please see the log by @GreedyA1 above

You need use '0123456701234567' fixedKey
'123456701234567LL' is the 'long long' data type of the C ++ language

Thx!

yep that worked.


Crl + z within find and replace window of Jupyter notebook deletes document

Issue Type: Bug
Within a jupyter notebook containg multiple sections:

Search for a value which is contained
Find and replace with another value
With the cursor still within the replace input, press ctrl + z

This will irriversibly delete the entire document and replace with a single empty section. Becuase undo is specific to the section which modifications have been made in, there is no way to reverse the delete.
VS Code version: Code 1.65.0 (b5205cc8eb4fbaa726835538cd82372cc0222d43, 2022-03-02T11:12:08.962Z)
OS version: Windows_NT x64 10.0.19044
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz (12 x 2592)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.75GB (3.00GB free)

Process Argv
--crash-reporter-id 1fa9ebb7-6f1e-450a-a47c-c5ec85f85730

Screen Reader
no

VM
0%

Extensions (26)

Extension
Author (truncated)
Version

vscode-intelephense-client
bme
1.8.2

python-preview
don
0.0.4

vsc-material-theme
Equ
33.2.0

vsc-material-theme-icons
equ
1.2.2

vscode-install-vsix
fab
1.4.0

matlab
Gim
2.3.1

vscode-pull-request-github
Git
0.38.0

fluent-icons
mig
0.0.17

anaconda-extension-pack
ms-
1.0.1

python
ms-
2022.2.1924087327

vscode-pylance
ms-
2022.3.0

jupyter
ms-
2022.2.1020642448

jupyter-keymap
ms-
1.0.0

jupyter-renderers
ms-
1.0.6

remote-containers
ms-
0.224.2

remote-ssh
ms-
0.76.1

remote-ssh-edit
ms-
0.76.1

atom-keybindings
ms-
3.0.9

cpptools
ms-
1.8.4

powershell
ms-
2021.12.0

indent-rainbow
ode
8.2.2

vscode-commons
red
0.0.6

vscode-yaml
red
1.5.0

snakemake-lang
sna
0.1.6

snakefmt
tfe
0.1.0

material-theme
zhu
3.13.20

(10 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyl392:30443607
pythontb:30283811
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805:30301674
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
vsc1dst:30438360
pythonvs932:30410667
wslgetstartedc:30433508
vsclayoutctrt:30448491
vsrem710cf:30416617
dsvsc009:30440023
pythonvsnew555:30442236
vsbas813:30436447
vscscmwlcmt:30438805
vscgsvid2:30447481
helix:30440343

Thanks for the bug report, we should prevent undo of document when focus is in the find widget.

I can't reproduce this in today's Insiders though. It would be great if you can share some more details about how to reproduce it more stably?

When I posted I was able to do it 5 times in a row. Since then I have disabled and re-enabled the Jupyter extension.  I am no longer able to get the same issue. If I am able to get the same bug, I will be sure to update this chain.

When I posted, I was able to get the bug 5 times in a row. Since then I have disabled and re-enabled the Jupyter extension. I am no longer able to get the same issue. If I encounter the bug again, I will be sure to update this chain.


📝 readme tweaks

Description

formatting consistency
added TOC
moved "where is JS" to top
made notes when sections contained adobe-only firewall links
linked to contribution guidelines, removed 'learn more' section that linked to internal top-level spectrum docs

Related Issue
This issue relates to #17, but I am not sure that it closes it.
Checklist:

[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.

Thanks for the suggestions, I've accepted them!


Triple emphasis support

Hello,
As far as I know Markdig doesn't support italic and bold at once text by using triple emphasis.
Example: commonmark.js dingus link
EmphasisInline class has only IsDouble property. Either IsTriple or Count property could be introduced.
Cheers

It does, see https://babelmark.github.io/?text=test
If you look at the syntax tree returned when parsing this text, you will see that it outputs EmphasisInline(double) inside of an EmphasisInline(single).

My bad, it does indeed work that way.


fix: Ensure that popover focus lock works as expected

Description
Prevents some unexpected side-effects from popover focus lock, specifically when the popover
is placed inside a focusable element (i.e. if any parent has tabindex set).
Recreation of the problem before fix: https://codesandbox.io/s/recursing-tharp-7ybx7d?file=/src/App.js
How has this been tested?
Local testing & new tests.
Documentation changes
[Do the changes include any API documentation changes?]

[ ] Yes, this change contains documentation changes.
[X] No.

Related Links
AWSUI-19360

Review checklist
The following items are to be evaluated by the author(s) and the reviewer(s).
Correctness

[ ] Changes are backward-compatible if not indicated, see CONTRIBUTING.md.
[ ] Changes do not include unsupported browser features, see CONTRIBUTING.md.
[ ] Changes were manually tested for accessibility, see accessibility guidelines.

Security

[ ] If the code handles URLs: all URLs are validated through the checkSafeUrl function.

Testing

[ ] Changes are covered with new/existing unit tests?
[ ] Changes are covered with new/existing integration tests?

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

The popover dismiss button was being focused while the popover was still repositioning itself, therefore it was offscreen & caused the browser to reset scroll. That in turn affected the positioning logic.


Changes to accommodate LLVM 7.0.x

As title.

Codecov Report

Merging #3437 into master will increase coverage by <.01%.
The diff coverage is 60%.

@@            Coverage Diff             @@
##           master    #3437      +/-   ##
==========================================
+ Coverage   80.61%   80.62%   +<.01%
==========================================
  Files         390      390
  Lines       78641    78647       +6
  Branches     8887     8886       -1
==========================================
+ Hits        63399    63407       +8
+ Misses      13844    13843       -1
+ Partials     1398     1397       -1

Looks good


Add matching string to line & polygon layer

Issue #1446 :
https://github.com/bcgov/met-public/issues/1446
-display lines for geojsons

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the met-public license (Apache 2.0).

Codecov Report

Merging #1476 (30d0c73) into main (1b56496) will decrease coverage by 5.95%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1476      +/-   ##
==========================================
- Coverage   71.54%   65.60%   -5.95%
==========================================
  Files         330      211     -119
  Lines        9683     5125    -4558
  Branches      698      698
==========================================
- Hits         6928     3362    -3566
+ Misses       2637     1645     -992
  Partials      118      118

Flag
Coverage Δ

metapi
?

metweb
65.60% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 119 files with indirect coverage changes


restart

after a user action with ajax i want to restart the time.
how can i set a new beginning time or add time?

Check-out the Docs: http://hilios.github.io/jQuery.countdown/documentation.html#controls


Are all hierarchical metadata of vineyard objects shread across the cluster?

Describe your problem
In the vineyard document dive into vineyard section -> Implementation Details, it says

As we mentioned before, each object in Vineyard, consists of two parts:

The data payload is stored in the corresponding vineyard instance locally

The hierarchical metadata shared across the vineyard cluster

Are all hierarchical metadata shared across the vineyard clusters?

Answer:
no, it is not, it is only shared when the client. persist API is called.

Will be addressed in the up-coming data-access documentation section.

Addressed by https://v6d.io/notes/objects.html#transient-vs-persistent-objects and https://v6d.io/notes/data-accessing.html.


Backfill page design feedback

[ ] 1. Apply even margin between inputs

[ ] 2. Update inputs to be equal width

[ ] 3. Left align region input with location input at the top of the page.

[ ] 4. Spacing improvements

[ ] 5. Center "Change Value Completeness per Lag by weekday" chart on page

@sgratzl Is it possible to make the "Change Value Completeness per Lag by weekday" chart the same width as the "CHANGE COUNTY COVERAGE" chart above?

closing for now since the overall layout of the page has changed


Generate outcomes by income group

Outcomes include
risk factors - sodium, BMI
disease - prevalence and incidence for each disease
burden of disease - yll, yld, daly

As a temporary solution, it was agreed that three simulations could be run for the three different income groups, with all other parameters being equal.
The population is initialised with the same income class, newborns should also be assigned to that income class, but each individual is allowed to move to a different income class at adulthood. So the only people with a different income class should be those that reached adulthood and were reassigned.
One disadvantage to this approach is that it does not consider adults that are reassigned to this class, but were of another class in childhood.
These three experiments will require a hack to StaticLinearModel.

IN FUTURE try different dsets in ./data for each income group, with diffreent population distributions.


count the number of Python contributions

What does the program do ?
Counts how many files are in the Python folder of the Hacktoberfest Hello-World repo.

In what programming language it is written?
Python

Thank you for participating  in hacktoberfest ❣ if you liked working on this repo you can share it with friends and star this project for helping others


[java-sdk] Dapr's base Client

Define interface for the Dapr's Client - wrapper on top of the auto-generated code.
Implement Adapter for GRPC.
Implement Adapter for HTTP.

We have auto-generated client in Grpc and one manually generated for HTTP. This base client can sit on top of those now.


Mips ori instruction IL incorrect

The instruction ori $a0, $zero, 0x75 is generating the IL $a0 = $zero | 0.  This should be $a0 = $zero | 0x75, or better yet, $a0 = 0x75
Opcode is 0x34040075

Fixed in dev


fix(geolocation): uses canary next/image

Description
Since<EMAIL_ADDRESS>next/image has a different set of properties.
This PR fixes this example so it can pass on our CI.
Demo URL
https://edge-functions-geolocation-e7q9k3o95.vercel.sh/
Type of Change

[ ] New Example
[x] Example updates (Bug fixes, new features, etc.)
[ ] Other (changes to the codebase, but not to examples)

Dear code owners, this is my first PR on this repo, and I have no clue why solutions-monorepo is failing. And I can't access the build logs of example-streaming.
Can you advise me?


Add support for CMUCL

The existing (kernel:std-compute-class-precedence-list sub) does not work correctly for structures; alternative is (pcl:compute-class-precedence-list sub). A test for this: (subctypep (specifier-ctype 'pathname) (specifier-ctype 'pathname)).

Is there not just a class-precedence-list reader to use from the MOP?


Spelling mistakes

There are a couple of instances of Application spelt Applicatin.

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

ID: 77a317f1-deef-4ba7-5839-f39ce3733655
Version Independent ID: d85aa8fe-7270-d073-ea56-d1c0759383b8
Content: Enabling end to end SSL on Azure Application Gateway
Content Source: articles/application-gateway/ssl-overview.md
Service: application-gateway
GitHub Login: @amsriva
Microsoft Alias: victorh

@cbuchanan , thank you for your feedback.
PR has been made: https://github.com/MicrosoftDocs/azure-docs-pr/pull/87987
Changes will be reflected shortly.


ECDSA_SIG_set0 does not follow documentation

The documentation attached to the prototype declaration of ECDSA_SIG_set0 seem to imply that NULL can be passed for r or s and the old value will be retained. The actual implementation returns an error if either is NULL.
Either the documentation or the implementation should be updated, with a preference for the latter (if updating only one part of the signature, you would need to create a duplicate for the other one).

I think it should behave like the others. For instance RSA_set0_key() is documented as:
The values n and e must be non-NULL the first time this function is called on a given RSA object.

I hadn't though about this case :) Following the example you proposed, the implementation should be something like this then:
int ECDSA_SIG_set0(ECDSA_SIG *sig, BIGNUM *r, BIGNUM *s)
{
    if ((sig->r == NULL && r == NULL) ||
        (sig->s == NULL && s == NULL))
        return 0;

    if (r != NULL) {
        BN_clear_free(sig->r);
        sig->r = r;
    }
    if (s != NULL) {
        BN_clear_free(sig->s);
        sig->s = s;
    }

    return 1;
}


user request: enhancement on sorting activity

You can add sorting for activity tab too. You can add sorting by price so that people can see what is the lowest / highest sell price in a particular NFT collection.

Moved to issue #377.


From and to: ?

This may seem obvious but counterintuitive
From: Left Control -> To: Function  - I would have expected that the Function key would now do what the Left Control key does, but it turns out to be the opposite.
It appears it works this way: Simple key modification (change key "left control" to another key Function)   This doesn't make intuitive sense to me.

From is the event normally sent by the physical key you type. To is the event it becomes. Your keyboard is an input, sending events in a single direction, from your keyboard -> to your computer. Karabiner-Elements transforms this input: it takes 'from' events and transforms them into 'to' events. What could possibly make more intuitive sense than that?
Close this issue if you understand; even if you don't, close it anyway because it seems to make sense to everyone else.