Cannot connect to database, active schema has no name

Current Issue
I can connect to the project, but I can't connect to the database, so I can't execute SQL or make changes to the data.
What should I do?
This is the current situation.

No active schema appears in the drop-down menu.

@kanbaru-github, Hi, can you provide additional information about that database was used?

We apologize for the inconvenience.
We have resolved the issue by setting the target database to default.
We apologize for the inconvenience.
2022年6月28日(火) 17:30 George @.***>:

@kanbaru-github https://github.com/kanbaru-github, Hi, can you provide
additional information about that database was used?
—
Reply to this email directly, view it on GitHub
https://github.com/dbeaver/dbeaver/issues/16901#issuecomment-1168405451,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUCIP2SMDDDN55G6ETK2AHLVRKZZZANCNFSM52APHVNQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Thank you!
2022年6月29日(水) 18:53 ShadelessFox @.***>:

Closed #16901 https://github.com/dbeaver/dbeaver/issues/16901 as
completed.
—
Reply to this email directly, view it on GitHub
https://github.com/dbeaver/dbeaver/issues/16901#event-6900897992, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AUCIP2VO4PR2D5LT6HKQKRLVRQMJBANCNFSM52APHVNQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


rename storage args to converge across languages

API change check
API changes are not detected in this pull request.


Detox Time correction on Nightberries

Nightberries don't spawn on water.  They grow on hard to see plants/bushes on top of Floating Mat blocks (aka wet quicksand).  The plants are destroyed if the block is destroyed.
Thankfully, journeymap puts a white dot where the plant is, so you can detect them that way.

That change says they're plants on water, which is still misleading.  Floating Mat blocks are not water.


Daemonize and start/stop service

So far, I'm only able to start the server with falcon serve.
Is there any way to daemonize it and point to a pidfile? And even better, is it possible to stop the server  somehow sending the pidfile or state file?
One of the things that I like of puma is that it can be easily configured with monit using capistrano to automatically start and stop.
# Example of monit recipe for automatically start/stop puma
check process puma_app_production
  with pidfile "/var/www/app/shared/tmp/pids/puma.pid"
  # shorted for brevity
  start program = "bundle exec puma -C /var/www/app/shared/puma.rb --daemon'"
  stop program = "bundle exec pumactl -S /var/www/app/shared/tmp/pids/puma.state stop'"

Since I added tus to the app, I'd like to implement something like this for falcon as well so I make sure the service is always on or if is not it starts itself.
I can't see to find a reliable way to keep the process up otherwise.
This seems to be like a basic requirement for production usage, so I may be well missing something out.

I've been playing around with these ideas recently.
My current method for deployment is to use something like systemd which can restart the process if it crashes.
Here is an example config file: https://github.com/socketry/falcon-benchmark/blob/master/setup/falcon/etc/systemd/system/falcon.service
Falcon itself now automatically restarts failed child processes too, and hopefully this paves the way for graceful restart/reloading of configuration.
Daemonization of a process can be done by an external tool very easily, e.g. start-stop-daemon, or even something like https://github.com/ioquatix/process-daemon - there is no intrinsic reason why it needs to be built into the falcon code base itself.
That being said, I'm open to ideas.

I'm working on falcon virtual which supports this use case. However, I don't believe implementing demonisation into falcon is the right approach, there are plenty of tools that let you achieve that already (e.g. systemd). Even despite that, falcon supports rolling restarts so in theory most of the functionality you want is there. Once falcon virtual matures, there should be good examples of how to integrate this.


No permission

What is your username and discriminator?
Lech#0407
Why did you join Discord Linux?
For tech support
Where did you hear about Discord Linux?
using google search?
What is the passphrase that was assigned to you by the bot?
Can't see the damn passphrase on latest firefox

From simonizor#0420 :
This form is only for people who do not have a phone to verify with Discord. Please read the message that mentions you in the welcome channel.


Error upgrading from 2.0.0-alpha1 to Beta 0/1 failing with "isSubmitting of undefined"

Hi,
I recently updated from the alpha version of formik-material-ui to the beta. It right away started throwing an error of "Cannot read property 'isSubmitting' of undefined"
I've created a code sandbox where you can switch between versions of formik-material-ui to see that the issue begins to happen at Beta 0. CodeSandbox
I'm likely doing something wrong. I'm fairly new to React, Formik, Material-UI, etc. and any help would be really appreciated. The sandbox is a minimal version that reproduces the structure of the code in my real project.
Thanks!

You need to use the Formik Field component. See: https://codesandbox.io/s/eror-upgrading-to-formik-material-ui-beta-1-3rc2y

Hi,
Thank you for correcting the sample's code. I had the feeling that I was doing it wrong, and it is great to see the right way to do it.
The downside though, is that beta version behavior couples me tightly to Formik. I liked the alpha version, where all the binding appeared to be working without using a Field. It made it easier to reuse groups of components in places where Formik wasn't applicable. Maybe it just worked coincidentally rather than intentionally.

Hi @Wombat42
I would have preferred it that way too but there were issues with properties available on Field that useField does not have access too.
You can read the details here https://github.com/stackworx/formik-material-ui/issues/111#issuecomment-584861266


Files don't open from explorer after updating

Using Atom 0.183.0 on Windows 7 x64.
After atom updates, I become unable to double click files and have them open. The command line still works fine.
To fix:

Open regedit.exe
Navigate to HKEY_CLASSES_ROOT\Applications\atom.exe
Right-click (Default), click Modify...
Modify the text from C:\Users\Michael\AppData\Local\atom\app-0.181.0\atom.exe to C:\Users\Michael\AppData\Local\atom\app-0.183.0\atom.exe
Close regedit.exe
Close and reopen explorer.exe
Double clicking files works again!

Could this registry item be updated when atom is updated?

Duplicate of #4893, please subscribe there for updates.


remove size checks & improve logging details

Let the size checks be handled by glusterfs tools
Improve the logging details

review-request: @mikechristie @lxbsz @pranithk
Thanks!

@mikechristie updated the PR addressing your review comments.
Thanks!

There are some lines are exceeding 80 chars, but most of them are unavoidable, because spliting the  strings into two lines is not a good idea, which will make the log string search becoming more difficult.
The code look good to me.
And just have a quick test which also works well.
Thanks,


Storageos Volume Plugin

Docs for Feature: https://github.com/kubernetes/features/issues/190
PR (already merged for 1.7 release): https://github.com/kubernetes/kubernetes/pull/42156
One-line release note description:
Volume plugin for StorageOS provides highly-available cluster-wide persistent volumes from local or attached node storage.
/cc @saad-ali

This change is

Tech Review LGTM


[Dapp] Farming Index page - Filters

Description
Design reference
https://www.figma.com/file/TxyvqO53GlCiTaJOE26AwM/dApp?node-id=0%3A1&t=a2NYxoXVVLR9uNCd-1
Filter by: my project, undeposited, claimable
Acceptance Criteria

[ ] Add and describe Acceptance Criteria
[ ] Add and describe Acceptance Criteria

Additional context
Add any other context or screenshots about the feature request here.

Timeline: relevant when we will have plenty of projects funded

Farming Landing Page


Close all unsaved tabs and application without saving button

Version is <IP_ADDRESS>009201907
When I try to close Dbeaver application and if there are unsaved multiple tabs, it shows this popup;

It would be better to have a button like "close all tabs and application without save"

thanks for suggestion

https://github.com/dbeaver/dbeaver/issues/5675 duplicate


[NDM] [Cisco ACI] Support submitting topology metadata

What does this PR do?

https://datadoghq.atlassian.net/browse/NDMII-2989
Adds support for sending TopologyLinkMetadata to our EvP ndm track to support having ACI devices appear on the topology map.
See this document for additional context.
Motivation

Additional Notes

Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Changelog entries must be created for modifications to shipped code
[ ] Add the qa/skip-qa label if the PR doesn't need to be tested during QA.
[ ] If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged


git clone git@github.com:tonlabs/TON-Compiler.git error

freeton:~/ton# git clone git@github.com:tonlabs/TON-Compiler.git
Cloning into 'TON-Compiler'...
The authenticity of host 'github.com (<IP_ADDRESS>)' can't be established.
RSA key fingerprint is SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8.
Are you sure you want to continue connecting (yes/no)? y
Please type 'yes' or 'no': yes
Warning: Permanently added 'github.com,<IP_ADDRESS>' (RSA) to the list of known hosts.
<EMAIL_ADDRESS>Permission denied (publickey).
fatal: Could not read from remote repository.
Work fine:
git clone https://github.com/tonlabs/TON-Compiler.git

Did you set up your GitHub keys?
GitHub requires it in order to authenticate you as user and only then it allows to clone via git clone git@github.com:tonlabs/TON-Compiler.git


make check fails on Linting with ruff : Python 3.12.4

Describe the bug

To Reproduce
Steps to reproduce the behavior:

create a pyenv using python  3.12.4
clone the repo
make install
make

Expected behavior
Linting with ruff

OS: e.g. Debian GNU/Linux 12 (bookworm)
Language Version: pyenv 3.12.4
Virtual environment: Poetry 1.8.3

Additional context
14:53:59 ❯ make check
🚀 Checking Poetry lock file consistency with 'pyproject.toml': Running poetry check --lock
All set!
🚀 Linting code: Running pre-commit
check for case conflicts.................................................Passed
check for merge conflicts................................................Passed
fix end of files.........................................................Passed
trim trailing whitespace.................................................Passed
ruff.....................................................................Passed
ruff-format..............................................................Passed
prettier.................................................................Passed
🚀 Linting with ruff
error: Failed to parse `/home/nobody/GitHub/cookiecutter-poetry2/cookiecutter-poetry/pyproject.toml`: TOML parse error at line 82, column 12
   |
82 | [tool.ruff.lint]
   |            ^^^^
unknown field `lint`, expected one of `allowed-confusables`, `builtins`, `cache-dir`, `dummy-variable-rgx`, `exclude`, `extend`, `extend-exclude`, `extend-ignore`, `extend-select`, `external`, `fix`, `fix-only`, `fixable`, `format`, `force-exclude`, `ignore`, `ignore-init-module-imports`, `line-length`, `required-version`, `respect-gitignore`, `select`, `show-source`, `src`, `namespace-packages`, `target-version`, `task-tags`, `typing-modules`, `unfixable`, `update-check`, `flake8-annotations`, `flake8-bandit`, `flake8-bugbear`, `flake8-builtins`, `flake8-errmsg`, `flake8-quotes`, `flake8-tidy-imports`, `flake8-implicit-str-concat`, `flake8-import-conventions`, `flake8-pytest-style`, `flake8-unused-arguments`, `isort`, `mccabe`, `pep8-naming`, `pycodestyle`, `pydocstyle`, `pylint`, `pyupgrade`, `per-file-ignores`

make: *** [Makefile:44: check] Error 1

Thanks for raising this! I see the issue; we have two different versions of ruff running simultaneously; one in the pre-commit hook and one through the virtual environment based upon the pyproject.toml. One of them is a bit older, so it does not recognize the new configuration with [tool.ruff.lint] yet.
We should remove one of the methods of using ruff, and make sure the one we keep uses the latest release of ruff. I dont have time to fix it now, but hopefully tomorrow :)

thanks!
lastest ruff v 0.5.1 seems to work if you add the keyword "check"
https://github.com/fpgmaas/cookiecutter-poetry/blob/8134f27936e41e2e27bbca5415030d5834cb953e/pyproject.toml#L31
ruff = "^0.5.1"
https://github.com/fpgmaas/cookiecutter-poetry/blob/8134f27936e41e2e27bbca5415030d5834cb953e/Makefile#L44
@poetry run ruff check hooks tests cookiecutter_poetry --config pyproject.toml

Thanks again, should be solved now!

Yes it work thanks


JdkHttpResponseSync can fail to log IOException

This class catches IOExceptions and writes them to log files, but the following code ignores an IOException:
public void writeBodyTo(WritableByteChannel channel) throws IOException {
if (bodyBytes != null) {
channel.write(ByteBuffer.wrap(bodyBytes));
} else {
try {
int nRead;
byte[] data = new byte[STREAM_READ_SIZE];
while ((nRead = bodyStream.read(data, 0, data.length)) != -1) {
channel.write(ByteBuffer.wrap(data, 0, nRead));
}
} catch (IOException ex) {
throw LOGGER.logExceptionAsError(new UncheckedIOException(ex));
}
        close();
    }
}

channel.write(ByteBuffer.wrap(bodyBytes)); is not inside the try statement and it can throw IOException.

@tohidemyname Thank you for reaching out.
We try not to catch the nio.channels.WritableByteChannel's IOException but let it bubble up.


Support using "blocking" and "async_impl" features at the same time

Is your feature request related to a problem? Please describe.
I have a cargo workspace with several projects that use the schema_registry_converter. Some of them are tools that use the blocking implementation (i.e., no need for async_impl), but some are server apps, which need to use async_impl.
Because the workspace builds dependencies configured with the union of all features listed across all projects, I end up not being able to use async_impl anywhere as long as at least one of the projects uses blocking.
Describe the solution you'd like
I would like to be able to select both async_impl as well as blocking features without one disabling the other.
Describe alternatives you've considered
For now, I get around it by including the kafka_test feature, which ends up allowing blocking alongside async_impl, but this seems like a hack.
Additional context
Is there a specific reason why blocking automatically precludes async_impl?
https://github.com/gklijs/schema_registry_converter/blob/master/src/lib.rs#L24
I realize one must have at least one of them enabled, but the mechanism that you describe in an example (i.e., default-features = false, features = ["blocking"]) seems to provide that.
Thank you!

Hi, thanks for creating the issue.
I imagined the library to be often used with the rdkafka crate, and changed the default to async because they kind of did as well.
The separation of the async and blocking I stole from reqwest.
I didn't imagine users want both and the current way of not loading the async when blocking seemed nice. But I think I could change the check for the async module from not blocking to futures. Making it easier to use both.

I'm awaiting the build. The async is now dependent on the futures feature, that is set by default. So for you case you should be able to remove the kafka_test feature, and you still have them both. To use only async nothing is changed, since excluding default features will already exclude async.

That's great, thank you!


ApplyURLHelper breaks external link

https://github.com/cross-solution/YAWIK/blob/develop/module/Jobs/src/Jobs/View/Helper/ApplyUrl.php#L111-L113
there should be an extra check for an external URL like in
https://github.com/cross-solution/YAWIK/blob/develop/module/Jobs/src/Jobs/View/Helper/JobUrl.php#L112-L114
otherwise it breaks the link e.g. in https://github.com/cross-solution/YAWIK/blob/develop/module/Jobs/view/jobs/export/feed.xml.phtml#L76
e.g. an external applylink https://example.com/apply results in https://yawik.org/demo/https://example.com/apply

I cannot reproduce the problem. I've set an external UL
https://yawik.org/demo/en/jobs/view?id=5b2a56360acec36513ee86fa
So I close this issue. Reopen it, if you think I'm wrong.

It is still broken if you try to generate an absolute link
https://yawik.org/demo/de/export/xml?page=6
<job id="5b2a56360acec36513ee86fa">
<title>Schreiner</title>
<location>Dortmund</location>
<datePublishStart>2018-06-20T15:41:48+02:00</datePublishStart>
<datePublishEnd/>
<dateModified>2018-09-08T18:27:45+02:00</dateModified>
<url type="application">https://yawik.orghttps://example.com/apply</url>
expected value would be
<url type="application">https://example.com/apply</url>


Added TS typings

Hello. I try to implement typings for TS. I can't achieve the better result. Please review my solutions and give me feedback.
What do you think?

Pull Request Test Coverage Report for Build 73

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

Totals

Change from base Build 72:
0.0%

Covered Lines:
30

Relevant Lines:
30

💛  - Coveralls

I'm sorry. In TS 2.8 conditional types were added. Fix it.

@sergeysova, will you have time to see it this week?

@igorkamyshev what about tests for typings?

@igorkamyshev you don't typing action creator arguments types.
const { actions } = createSymbiote(initialState, {
  foo: {
    bar: (state, a: string, b: number) => ({ ...state })
  }
})

actions.foo.bar("foo", "2") // should broken

@sergeysova sure, I will write tests and returns later.
Actions must compatible with Actions type (second parameter for createSymbiote function). Do you think, automatically checking in potential? Please, share the article/docs about this TypeScript feature.
Thanks for review.

I merge it now. But wait for tests

@igorkamyshev Thank you!

@sergeysova okay, will fixed.


OpenSSL Padding Oracle vulnerability (CVE-2016-2107)

The Nginx docker image that this is built off does not have an up to date version of OpenSSL. The Openssl security notice https://www.openssl.org/news/secadv/20160503.txt recommends a minimum 1.0.1o.
This security vulnerability causes any SSL site using this image to be rated F by ssllabs

Fix seems to be in debian jessie secuity https://security-tracker.debian.org/tracker/CVE-2016-2107 and nginx:1.9.15 has it:
$ docker run --rm nginx:1.9.15 bash -c 'dpkg -l|grep openssl'
ii  openssl                   1.0.1k-3+deb8u5                    amd64        Secure Sockets Layer toolkit - cryptographic utility


get data

Hi !
how can in get current editor data without save event ?

While the editor is in the editing state you can get the content for any region like so:

var regionHTML = editor.regions()['region-name'].html();

If i want get that without editing state , what should i do ?

Well actually once you init the editor you will be able to access the HTML as per my previous comment, the only reason I mentioned editing state is you can't trigger the save event unless you're in the editing state.


Fix #305 (sonalyze) - Do not filter heartbeat data for 'load'

The test case that tested that heartbeat records are skipped had to be removed.  (Possibly it should be turned into a test that asserted that heartbeat data were not removed?)

Test added back with new meaning.


[RFC] Replace yapf with black

What does this PR do?
The addition of --skip-magic-trailing-comma to black sparked this discussion again.
cc: people interested about this in the past: @akihironitta @Borda @ananthsub @awaelchli @edgarriba
Pros for black:

Faster (https://github.com/kornia/kornia/pull/1051#issuecomment-851550383)
More active project
More popular project (21.2k stars vs 11.7k)
More consistent, tighter constraints
Also formats docstrings
Removes \ to split lines

Cons:

Not as configurable

Vote

Yay (👍) or nay (👎)?
Default " (🚀) or ' (🎉) for strings?

If 👍, this won't be merged until after the last bug-fix release in the v1.3.x line to avoid conflicts.
Before submitting

[ ] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
[n/a] Did you make sure to update the documentation with your changes? (if necessary)
[n/a] Did you write any new necessary tests? (not for typos and docs)
[n/a] Did you verify new and existing tests pass locally with your changes?
[n/a] Did you update the CHANGELOG? (not for typos, docs, test updates, or internal minor changes/refactorings)

PR review

[x] Is this pull request ready for review? (if not, please submit in draft mode)
[x] Check that all items from Before submitting are resolved
[x] Make sure the title is self-explanatory and the description concisely explains the PR
[x] Add labels and milestones (and optionally projects) to the PR so it can be classified

@carmocca configurability of code style can be named as a pro for yapf but not as a con for black because it is designed that way.

These are the stats for the diff size for each string option:
': 355 files changed, 5310 insertions(+), 7858 deletions(-)
": 335 files changed, 5527 insertions(+), 8075 deletions(-)

@carmocca mind sho how the codebase would look like?

+1000000 strongly in favor of using black as a standard formatter :)

@carmocca note that this big PR will be always in conflict whenever we merge to master, also after this merge most open PRs will be affected... :rabbit:

note that this big PR will be always in conflict whenever we merge to master

This is not a big deal, we just have to delete pre-commit-bot's commit and let it re-do it to resolve conflicts. And obviously have a window of time where the CI for this PR runs before any other one is merged.

also after this merge most open PRs will be affected... 🐰

Yes, but regardless, the open PRs can use the "keep ours" merge strategy and pre-commit-bot will fix it afterwards

just rebased and fixed conflicts... :]

@carmocca @Borda now that we use black, are you ok with removing pep8speaks? Whatever pep8 says we possibly cannot influence it due to the automatic formatting, so I would like to suggest removing these messages.

@carmocca @Borda now that we use black, are you ok with removing pep8speaks? Whatever pep8 says we possibly cannot influence it due to the automatic formatting, so I would like to suggest removing these messages.

https://github.com/PyTorchLightning/pytorch-lightning/pull/8392#issuecomment-892609542

we l need to uninstall it from all repos I guess, will sync with @lexierule


chore: jetstack/cert-manager/cmctl to cert-manager/cert-manager

https://github.com/aquaproj/aqua-registry/pull/7008 Rename the package jetstack/cert-manager/cmctl to cert-manager/cert-manager
The repository jetstack/cert-manager has been transferred to cert-manager/cert-manager.

Fixed in the following commit.
https://github.com/aquaproj/aqua-registry/pull/7008/commits/885dc18cdf1c6297ea7c68a8fd71329e5d6b233e
And I don't really understand why this fix is necessary. 🤔

And I don't really understand why this fix is necessary.

Actually, there is no strict rule about the package name, so cert-manager/cert-manager isn't necessarily wrong.
But I think users should be able to understand what is installed by the package.
In case of cert-manager, I think cert-manager indicates a resource working on Kubernetes rather than CLI.
https://cert-manager.io/

cert-manager is a powerful and extensible X.509 certificate controller for Kubernetes and OpenShift workloads.

So users may misunderstand or be confused.
The package name cert-manager/cert-manager/cmctl is easy to understand.

Actually, there is no strict rule about the package name, so cert-manager/cert-manager isn't necessarily wrong.
But I think users should be able to understand what is installed by the package.

Thank you! I understood.

I know some packages don't follow this idea, so this isn't a strict policy.
I have an idea to set aliases to existing packages to follow this idea strictly, but there is no plan to execute it at the moment.

Released. https://github.com/aquaproj/aqua-registry/releases/tag/v3.74.1


using rust-project external to facebook

I was experimenting with Buck2 on a Rust project and wasn't able to get rust-project to generate a rust-analyzer file reliably. You can see the output that I was originally receiving below:
rust-project develop --prefer-rustup-managed-toolchain :some-code
2023-12-13T02:03:04.561917Z  INFO rust_project::cli::develop: building generated code
Error: failed to deserialize command output

Caused by:
    0: command `env -u RUST_BACKTRACE -u RUST_LIB_BACKTRACE "buck2" "--isolation-dir" ".rust-analyzer" "bxl" "--oncall" "rust_devx" "-c" "client.id=rust-project" "@fbcode//mode/mac" "prelude//rust/rust-analyzer/resolve_deps.bxl:expand_and_resolve" "-c=rust.failure_filter=true" "--" "--targets" ":some-code"` (exit code: exit status: 1)
       stderr:
       Command failed: Error expanding argsfiles

       Caused by:
           0: Unable to read flag file at `/Users/fponce/buck2-test/none/mode/mac`
           1: No such file or directory (os error 2)

    1: EOF while parsing a value at line 1 column 0

I noticed that @fbcode//mode/mac was being passed as an argument and was able to find it referenced in the source code. By dropping that, the command works as expected and I'm able to use my IDE with the generated rust-project.json files successfully. I had originally tried passing in alternative values to -m but it didn't seem to work right either.
I have no doubt that this is not the correct fix, but you can see the diff here: https://github.com/facebook/buck2/commit/91214e5fbf1e0294a5b46ef5774e743461265a02

You can also just create an empty file at mode/mac as a workaround. See also https://github.com/facebook/buck2/issues/402 for the other thing you need to make it work.

Hey @davidbarsky, was playing with rust-project and ran across the same issue. Did you get a chance to get that diff up?

Hey @davidbarsky, was playing with rust-project and ran across the same issue. Did you get a chance to get that diff up?

D'oh, sorry, it fell to the wayside. I'll get that fixed today and landed today/tomorrow.

@davidbarsky one more friendly ping? Or if you want to roughly describe what change should be made I can try to push it through.

Really, really sorry: I've honestly been working on std::stream::Stream/rust-analyzer internals lately and haven't had the time.

Or if you want to roughly describe what change should be made I can try to push it through.

@jazzdan If you want to do this, I was thinking of defining a Config struct and deserializing from TOML using the toml crate crate. I was initially thinking that rust-project should look for a rust-project.toml at in the cell/project roots, but iterating over the current working directories ancestors is likely sufficient/preferable.


ARM64 support?

It would be amazing if this could support ARM64 windows builds!

I just upgraded to VS2019, and I'm going to give it a try to build it. I don't have an ARM64 device with Windows to test it, however.

I just upgraded to VS2019, and I'm going to give it a try to build it. I don't have an ARM64 device with Windows to test it, however.

I have a VM to test it with.

Guys, any updates on this?

Now released with 3.8. If you use it, please report back here. No idea if it works, but it built fine :)

Now released with 3.8. If you use it, please report back here. No idea if it works, but it built fine :)

I'll charge my phone (OnePlus 6T, running Windows 11 22000.100) and try it.

Can confirm that the driver installs without issues and also works flawlessly!

Ooh sweet! I'll also give it a try on my ARM64 VM.


Add new macro IgnoreReturnValue()

This commit adds a new macro IgnoreReturnValue(statement) which runs the statement (which should be a function/method which returns a status/value) and ignores the returned value.
This macro is primarily used to indicate the intention of developer that the return value of the function/method can be safely ignored.
The current change also updates some comments and spacings in code_utils.h

Current coverage is 71.12% (diff: 100%)

Merging #1149 into master will decrease coverage by 1.53%

@@             master      #1149   diff @@
==========================================
  Files           124        127      +3
  Lines         17110      18717   +1607
  Methods        2421       2624    +203
  Messages          0          0
  Branches       2064       2269    +205
==========================================
+ Hits          12433      13313    +880
- Misses         3900       4534    +634
- Partials        777        870     +93

Powered by Codecov. Last update 36f044f...f04ac5f

Closing this as it's combined with PR https://github.com/openthread/openthread/pull/1157.


[T2A2][F11] ZhuangYufeng

Ready for Review

Please mention your team ID, e.g. [F11-A1]. Make sure you use the correct title next time.

Please fix your PR title as [T2A2][F11-A4] and do so int he future. Had a hard time tracking your PR :(


WSOD with slog-bloat and W3 Total Cache

Site: bobbingwidetechsupport.com
PHP Error log contains:
[03-Feb-2021 11:50:42 UTC] PHP Fatal error:  Allowed memory size of 268435456 bytes exhausted (tried to allocate 75859437 bytes) in /home/bobbingw/public_html/wp-includes/functions.php on line 4755
[03-Feb-2021 11:50:42 UTC] PHP Fatal error:  Unknown: Cannot use output buffering in output buffering display handlers in Unknown on line 0
Plugins versions:
slog-bloat 0.0.1, slog 1.1.0, sb-chart-block 0.0.8, oik 4.1.2, oik-lib 0.2.0, oik-bwtrace 3.2.0, oik-libs not activated,
W3-Total-Cache 2.1.0

Problem occurs regardless of the activation status of oik-bwtrace.
Aside. When oik-bwtrace is not activated slog produces Notice: Trying to get property 'trace_files_directory' of non-object in /home/bobbingw/public_html/wp-content/plugins/oik-bwtrace/includes/class-trace-logs.php on line 41


Should not prefer .wasm over other extensions in resolve.extensions

Bug report
What is the current behavior?
Per the doc https://webpack.js.org/configuration/resolve/#resolve-extensions resolve.extensions defaults to ['.wasm', '.mjs', '.js', '.json'], so if there's a .wasm with the same name of a .js file, the .wasm file will be loaded first.
If the current behavior is a bug, please provide the steps to reproduce.
See https://github.com/vuejs/vue-cli/issues/3023
What is the expected behavior?
Considering the standard way to load a wasm file for now is to use the methods under WebAssembly namespace, rather than require it directly, it should be legit to instantiate a wasm module in a js file with the same name. The multimath package required by the reproduction example had worked perfectly fine until webpack introduced its experimental wasm support. IMHO .wasm should have lower precedence than other extensions and this should be solved on the webpack side.
Other relevant information:
webpack version:  4.26.1
Node.js version: v10.13.0
Operating System: macOS 10.14.1
Additional tools: @vue/cli v3.2.1

Fixed https://github.com/webpack/webpack/pull/8448


Exec go test on command call

When running GoTestPackageOnSave the tests are not executed instantly.
I think it should because it would give instant feedback to the user instead of having to save to have the first output.

@crisnlopez


Minimum supported Rust version

I've noticed that we don't seem to pin to a specific stable Rust version on CI. Now that 1.26 changed match behavior, it's very likely someone's accidentally going to make winit unusable for anyone using an older version.
So, how far back do we want to support?

wayland-client requires rust >= 1.20.0, and this is tested so unlikely to change unless absolutely needed.
So, I guess this puts a lower-bound onto what winit can require.

parking_lot requires Rust 1.24.0 and with some small changes winit also compiles with 1.24.0.

1.20.0 is what I was hoping for, since I have some ideas for using associated constants.
I didn't realize that parking_lot requires 1.24.0, or I would've raised this issue sooner. I'd say "well, it's probably fine, since no one's complained about it", but that doesn't mean anything, since almost no one's used winit 0.14.0 in the first place.
Though, I don't know how important it really is that we support older versions; I think the main argument is for people who install Rust from a package manager instead of rustup?


Dataset download links do not work

I have tried to download the dataset on the official website here https://floorplancad.github.io/. It seems the data doesn't exist anymore.

try: python preprocess/download_data.py  --data_save_dir  /ssd1/zhiwen/datasets/svg_raw

What is the relationship between image patches? Are they tiled versions of a larger image? Are file names some sort of coordinates? Is there overlap?
Anyone figured that out?


Dependency clean up.

Description
Make sure the template is using the latest version of our build tooling and clean up some old dependencies.
35594

Checklist ☑

[x] PR only fixes one issue or story
[x] Change reviewed for extraneous code
[x] UI best practices adhered to
[x] Commits squashed and meaningfully named
[x] All PR checks pass locally (build, lint, test, E2E)

[ ] (Optional) QE: Needs QE attention (OUIA changed, perceived impact to tests, no test coverage)
[ ] (Optional) QE: Has been mentioned
[ ] (Optional) UX: Needs UX attention (end user UX modified, missing designs)
[ ] (Optional) UX: Has been mentioned

/retest


[main] Upgrade to latest dependencies (#321)

upgrade to latest dependencies
bumping knative.dev/pkg 2a68697...0f34a88:

0f34a88 upgrade to latest dependencies (# 3018)

Signed-off-by: Knative Automation<EMAIL_ADDRESS>

OCF Webhook is merging this PR


Image thumbnails shown on posts in counterintuitive order

Describe the bug
Thumbnails of images are shown on posts in column order rather than row. NB when opened the image carousel is in the correct order.
To Reproduce
Steps to reproduce the behavior:

Make a post with four images attached.

Expected behavior
Image thumbnails are shown in this order:
1 2
3 4

Screenshots
The thumbnails in this post are shown in the wrong order:

Details

Platform: Android
Platform version: 14
App version: 1.56.0 (46)

Additional context
Also occurs on web version.

I created a test post with images in sequential order (as a potential first issue to try and fix), and it appears to be working as intended:

Ya this got fixed. Thanks everybody


helm Hooks

I noticed there's nothing in the docs talking about helm hooks.

Helm hooks can be configured using annotations, and annotations are supported. Can you please elaborate more on your use-case?


Fix Python conf of servermanager

Automation for azure-sdk-for-python

Automation for azure-sdk-for-node

Automation for azure-libraries-for-java

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-go


Chat -  MagicCodeInput stories are broken

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Run npm run storybook
https://staging.new.expensify.com/docs/index.html?path=/story/components-magiccodeinput--auto-focus
Navigate to the MagicCodeInput stories by clicking on 'MagicCodeInput' under components in the left-hand menu

Expected Result:
The MagicCodeInput stories should not be broken
Actual Result:
The MagicCodeInput stories are broken
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] Windows / Chrome
[ ] MacOS / Desktop

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/78819774/453fd2d1-4fa2-4934-a3e6-fdea37c11333

Expensify/Expensify Issue URL:
Issue reported by: @joh42
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1690918863039709
View all open jobs on GitHub

Proposal
Please re-state the problem that we are trying to solve in this issue.
MagicCodeInput stories are not working and broken.
What is the root cause of that problem?
We are not setting the required props correctly.
What changes do you think we should make in order to solve the problem?
We need to update the Template function with the needed props to work the stories correctly.
https://github.com/Expensify/App/blob/316a54520293b636a44b1353c90ccaf461902ed6/src/stories/MagicCodeInput.stories.js#L14-L17
function Template(args) {
    const [value, setValue] = useState('');
    const ref = useRef();
    return <MagicCodeInput
        value={value}
        onChangeText={(val) => setValue(val)}
        ref={ref}
        // eslint-disable-next-line react/jsx-props-no-spreading
        {...args}
    />;
}

Extra: If we need to provide some initial value then we can pass an extra arg called initialValue for the story and use above with the initial state useState(args.initialValue)

Result
https://github.com/Expensify/App/assets/14358475/5f271254-51a7-4d05-8f75-a8cc23d9a69b

Thanks for creating the issue! For some context, I discovered that the MagicCodeInput story was broken while going through the PR checklist after having modified the MagicCodeInput component. When asking about how broken stories should be handled, I got the suggestion of reporting it as a bug: https://app.slack.com/client/T03SC9DTT/C01GTK53T8Q/thread/C01GTK53T8Q-1690918046.950089

I don't know what this tool is, but I can reproduce the behavior described. Triaging to external

i like @bernhardoj's proposal. Because it fixes the network error and undefined value prop
c+ reviewed 🎀 👀 🎀

FYI I am OOO this week. Feel free to reassign in the meantime, or I will be back on Monday 28th

Not overdue, we're awaiting payment.

$1,500 payment approved for @rushatgabhane based on BZ summary.


Crosswalk 14 bad performance

hi
i got bad performance with latest intel xdk and crosswalk 12
also the performance became more bad if i use admob banner
any fix for this problem ?

This is a question, not a patch, so there is no point in sending a pull request. Please use the crosswalk-help mailing list or our JIRA bug tracker.


The standard map has hollow stairs

The stairs in the standard map are hollow, meaning spectators cannot fully see through them, and slimes will spawn:

This issue was fixed in 6be76e99af3c204d070fa5864da581fef39bbaa7.


Parsing JSON with comments (jsonc)

It would be nice to be able to parse JSON which contains comments.
Example: abaplint.jsonc

I'm guessing its a bit difficult, as ajson is built on top of sxml, or alternatively two passes

Yes, could be a nice feature. But indeed, SXML does not support it.
One quick option I see is to preparse the text removing the comment by regex. And add an explicit parameter to do this (to avoid performance impact for the normal json). But it won't be 100% reliable.
  "xyz": "Hello \/\/ world", // The comment with "quotes" and doubleslashes (//)

One more (a complex) option is to enable external parsers ... in particular I wanted to this to implement YAML or TOML parsing ... maybe ... though not anough time ... but then it also creates a possibility to alternative json parser. However this approach is in anycase way more complex

I pre-parse out single-line comments. Actually, the topic goes beyond comments, as there are plenty of differences looking at full json5 support. Writing this in ABAP would be bonkers and slow. The external parser (sxml or alternative) would need to support it. I don't see this happening so closing.


Adding Exponential Search Algorithm

Exponential search algorithm targets a range of an input array in which it assumes that the required element must be present in and performs a binary search on that particular small range. This algorithm is also known as doubling search or finger search.
If the element does not match, jump through the array exponentially in the powers of 2. Therefore, now the algorithm compares the element present in the incremental position.
Input:  arr[] = {10, 20, 40, 45, 55}
x = 45
Output: Element found at index 3
i acn code this in c,c++,java and python.
So @Kumar-laxmi  can you pls assign it to me under ssoc'23

Assigned!
@kritika2313 : C, C++, Java & Python


xdg-utils: 1.1.2 -> 1.1.3

Honestly, just noticed the update and it seems to not break everything O:).

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Fits CONTRIBUTING.md.

@GrahamcOfBorg build xdg_utils

Success on aarch64-linux (full log)
Attempted: xdg_utils
Partial log (click to expand)
/nix/store/d32zlmkh4z2ll5dsavvqrpppf9w92sb3-xdg-utils-1.1.3/bin/xdg-settings: interpreter directive changed from "/bin/sh" to "/nix/store/017xymp5i03qzigafnfx7sgf6602gmzq-bash-4.4-p23/bin/sh"
/nix/store/d32zlmkh4z2ll5dsavvqrpppf9w92sb3-xdg-utils-1.1.3/bin/xdg-screensaver: interpreter directive changed from "/bin/sh" to "/nix/store/017xymp5i03qzigafnfx7sgf6602gmzq-bash-4.4-p23/bin/sh"
/nix/store/d32zlmkh4z2ll5dsavvqrpppf9w92sb3-xdg-utils-1.1.3/bin/xdg-open: interpreter directive changed from "/bin/sh" to "/nix/store/017xymp5i03qzigafnfx7sgf6602gmzq-bash-4.4-p23/bin/sh"
/nix/store/d32zlmkh4z2ll5dsavvqrpppf9w92sb3-xdg-utils-1.1.3/bin/xdg-mime: interpreter directive changed from "/bin/sh" to "/nix/store/017xymp5i03qzigafnfx7sgf6602gmzq-bash-4.4-p23/bin/sh"
/nix/store/d32zlmkh4z2ll5dsavvqrpppf9w92sb3-xdg-utils-1.1.3/bin/xdg-icon-resource: interpreter directive changed from "/bin/sh" to "/nix/store/017xymp5i03qzigafnfx7sgf6602gmzq-bash-4.4-p23/bin/sh"
/nix/store/d32zlmkh4z2ll5dsavvqrpppf9w92sb3-xdg-utils-1.1.3/bin/xdg-email: interpreter directive changed from "/bin/sh" to "/nix/store/017xymp5i03qzigafnfx7sgf6602gmzq-bash-4.4-p23/bin/sh"
/nix/store/d32zlmkh4z2ll5dsavvqrpppf9w92sb3-xdg-utils-1.1.3/bin/xdg-desktop-menu: interpreter directive changed from "/bin/sh" to "/nix/store/017xymp5i03qzigafnfx7sgf6602gmzq-bash-4.4-p23/bin/sh"
/nix/store/d32zlmkh4z2ll5dsavvqrpppf9w92sb3-xdg-utils-1.1.3/bin/xdg-desktop-icon: interpreter directive changed from "/bin/sh" to "/nix/store/017xymp5i03qzigafnfx7sgf6602gmzq-bash-4.4-p23/bin/sh"
checking for references to /build in /nix/store/d32zlmkh4z2ll5dsavvqrpppf9w92sb3-xdg-utils-1.1.3...
/nix/store/d32zlmkh4z2ll5dsavvqrpppf9w92sb3-xdg-utils-1.1.3

Success on x86_64-darwin (full log)
Attempted: xdg_utils
Partial log (click to expand)
patching script interpreter paths in /nix/store/a7cyigv9g9ncyw7ay4cvq0rxypxzibhv-xdg-utils-1.1.3
/nix/store/a7cyigv9g9ncyw7ay4cvq0rxypxzibhv-xdg-utils-1.1.3/bin/xdg-desktop-icon: interpreter directive changed from "/bin/sh" to "/nix/store/f2lp21azk4w88f17zgf4mji64agb18ga-bash-4.4-p23/bin/sh"
/nix/store/a7cyigv9g9ncyw7ay4cvq0rxypxzibhv-xdg-utils-1.1.3/bin/xdg-desktop-menu: interpreter directive changed from "/bin/sh" to "/nix/store/f2lp21azk4w88f17zgf4mji64agb18ga-bash-4.4-p23/bin/sh"
/nix/store/a7cyigv9g9ncyw7ay4cvq0rxypxzibhv-xdg-utils-1.1.3/bin/xdg-email: interpreter directive changed from "/bin/sh" to "/nix/store/f2lp21azk4w88f17zgf4mji64agb18ga-bash-4.4-p23/bin/sh"
/nix/store/a7cyigv9g9ncyw7ay4cvq0rxypxzibhv-xdg-utils-1.1.3/bin/xdg-icon-resource: interpreter directive changed from "/bin/sh" to "/nix/store/f2lp21azk4w88f17zgf4mji64agb18ga-bash-4.4-p23/bin/sh"
/nix/store/a7cyigv9g9ncyw7ay4cvq0rxypxzibhv-xdg-utils-1.1.3/bin/xdg-mime: interpreter directive changed from "/bin/sh" to "/nix/store/f2lp21azk4w88f17zgf4mji64agb18ga-bash-4.4-p23/bin/sh"
/nix/store/a7cyigv9g9ncyw7ay4cvq0rxypxzibhv-xdg-utils-1.1.3/bin/xdg-open: interpreter directive changed from "/bin/sh" to "/nix/store/f2lp21azk4w88f17zgf4mji64agb18ga-bash-4.4-p23/bin/sh"
/nix/store/a7cyigv9g9ncyw7ay4cvq0rxypxzibhv-xdg-utils-1.1.3/bin/xdg-screensaver: interpreter directive changed from "/bin/sh" to "/nix/store/f2lp21azk4w88f17zgf4mji64agb18ga-bash-4.4-p23/bin/sh"
/nix/store/a7cyigv9g9ncyw7ay4cvq0rxypxzibhv-xdg-utils-1.1.3/bin/xdg-settings: interpreter directive changed from "/bin/sh" to "/nix/store/f2lp21azk4w88f17zgf4mji64agb18ga-bash-4.4-p23/bin/sh"
/nix/store/a7cyigv9g9ncyw7ay4cvq0rxypxzibhv-xdg-utils-1.1.3

Success on x86_64-linux (full log)
Attempted: xdg_utils
Partial log (click to expand)
/nix/store/gj209ndk7p0izkbxnmailcbpjjawj43x-xdg-utils-1.1.3/bin/xdg-screensaver: interpreter directive changed from "/bin/sh" to "/nix/store/nii7pk6pv4x4as7vsxbvwyzjn67vax6r-bash-4.4-p23/bin/sh"
/nix/store/gj209ndk7p0izkbxnmailcbpjjawj43x-xdg-utils-1.1.3/bin/xdg-email: interpreter directive changed from "/bin/sh" to "/nix/store/nii7pk6pv4x4as7vsxbvwyzjn67vax6r-bash-4.4-p23/bin/sh"
/nix/store/gj209ndk7p0izkbxnmailcbpjjawj43x-xdg-utils-1.1.3/bin/xdg-mime: interpreter directive changed from "/bin/sh" to "/nix/store/nii7pk6pv4x4as7vsxbvwyzjn67vax6r-bash-4.4-p23/bin/sh"
/nix/store/gj209ndk7p0izkbxnmailcbpjjawj43x-xdg-utils-1.1.3/bin/xdg-desktop-icon: interpreter directive changed from "/bin/sh" to "/nix/store/nii7pk6pv4x4as7vsxbvwyzjn67vax6r-bash-4.4-p23/bin/sh"
/nix/store/gj209ndk7p0izkbxnmailcbpjjawj43x-xdg-utils-1.1.3/bin/xdg-desktop-menu: interpreter directive changed from "/bin/sh" to "/nix/store/nii7pk6pv4x4as7vsxbvwyzjn67vax6r-bash-4.4-p23/bin/sh"
/nix/store/gj209ndk7p0izkbxnmailcbpjjawj43x-xdg-utils-1.1.3/bin/xdg-icon-resource: interpreter directive changed from "/bin/sh" to "/nix/store/nii7pk6pv4x4as7vsxbvwyzjn67vax6r-bash-4.4-p23/bin/sh"
/nix/store/gj209ndk7p0izkbxnmailcbpjjawj43x-xdg-utils-1.1.3/bin/xdg-settings: interpreter directive changed from "/bin/sh" to "/nix/store/nii7pk6pv4x4as7vsxbvwyzjn67vax6r-bash-4.4-p23/bin/sh"
/nix/store/gj209ndk7p0izkbxnmailcbpjjawj43x-xdg-utils-1.1.3/bin/xdg-open: interpreter directive changed from "/bin/sh" to "/nix/store/nii7pk6pv4x4as7vsxbvwyzjn67vax6r-bash-4.4-p23/bin/sh"
checking for references to /build in /nix/store/gj209ndk7p0izkbxnmailcbpjjawj43x-xdg-utils-1.1.3...
/nix/store/gj209ndk7p0izkbxnmailcbpjjawj43x-xdg-utils-1.1.3


Add missed arguments of apply_rotary_pos_emb in MHA

Description
Add missed arguments of apply_rotary_pos_emb in MHA
Type of change

[ ] Documentation change (change only to the documentation, either a fix or a new content)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Infra/Build change
[ ] Code refractor

Checklist:

[x] I have read and followed the contributing guidelines
[ ] The functionality is complete
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

/te-ci pytorch

/te-ci pytorch

Close as PR 1296 can address the issue of this PR.


Escape column names

Hi there,
When it compiles the query it doesn't escape column names in where section.
Ex,
$stmt = $pdo
    ->select()
    ->from('region')
    ->where('default', '=', true)
    ->execute()

To fix I have to prefix the column names,
$stmt = $pdo
    ->select()
    ->from('region')
    ->where('region.default', '=', true)
    ->execute()

Guess, it would be nice if it could output something like
SELECT * FROM `region` WHERE `default` = 1

Cheers,
Evgenii

I'm guessing you want it to automate prefixing in the table name (or table alias name) on the whereClause?
I don't think this is possible since if you are doing a join with other tables, the function wouldn't know which, for example, id column refers to which table. You'll have to prefix it manually when writing the statement.
If there were no joins with other tables, then it is totally possible and easy to implement, but then it would be pointless because you don't need to escape the column names (since column names within one table must be unique)

I had thought about this and decided not to escape the columns anywhere in the library.  Generally speaking, you probably shouldn't be accepting column names from user input or at least verifying that the columns are in a pre-approved list.  Adding the columns to the prepared statement would be a bit of a pain but is possible.  If you or anyone else really wants it, please make a compelling argument as to why.

Hi @kwhat ,
That was a long long thinking :)
Anyway cheers for that!

Hi @nasyrov,
I did play around with some implementations for escaping some of this stuff.  Here are the highlights:

Prepared statements can only be used for "parameter values" (where/limit/on)
Statements can escape extra stuff manually via PDO::quote()
Clauses cannot escape stuff easily as they do not have a PDO reference.

I am not ruling this out, I am just not going to hold up 2.x for it.  The 3rd bullet point is really the big issue here.

Hi @kwhat ,
No worries, thanks for looking at it!

I have decided against implementing this.  It is escaping column names is unreliable and would probably introduce injection issues for those relying on it.


"-a" missing in docker-volume-netshare 0.35 ?

As root:
wget https://github.com/ContainX/docker-volume-netshare/releases/download/v0.35/docker-volume-netshare_0.35_amd64.deb
dpkg -i docker-volume-netshare_0.35_amd64.deb

My docker version:
docker version
Client:
 Version:           18.06.1-ce
 API version:       1.38
 Go version:        go1.10.3
 Git commit:        e68fc7a
 Built:             Tue Aug 21 17:25:03 2018
 OS/Arch:           linux/amd64
 Experimental:      false

Server:
 Engine:
  Version:          18.06.1-ce
  API version:      1.38 (minimum version 1.12)
  Go version:       go1.10.3
  Git commit:       e68fc7a
  Built:            Tue Aug 21 17:23:29 2018
  OS/Arch:          linux/amd64
  Experimental:     false

cat /etc/default/docker-volume-netshare
# Docker Volume Plugin - Netshare Upstart and SysVinit configuration file

# Customize location of the binary (especially for development testing).
#DKV_NETSHARE="/usr/bin/docker-volume-netshare"

#
# Customize the volume plugin startup options
#

## NFS
#DKV_NETSHARE_OPTS="nfs"

## EFS
#DKV_NETSHARE_OPTS="efs --nameserver=<IP_ADDRESS>"

## CIFS
#DKV_NETSHARE_OPTS="cifs -u user -p pass -d domain"
DKV_NETSHARE_OPTS="cifs -u someusername-p mypassword-d WORKGROUP"

Start the service:
docker-volume-netshare cifs -a 1.38
Error: unknown shorthand flag: 'a' in -a
Usage:
  docker-volume-netshare cifs [flags]

Flags:
  -z, --dirMode string    Setting access rights for folders (mount.cifs's dir_mode option). Can also set environment NETSHARE_CIFS_DIRMODE.
  -d, --domain string     Domain to use for mounts.  Can also set environment NETSHARE_CIFS_DOMAIN
  -f, --fileMode string   Setting access rights for files (mount.cifs's file_mode option). Can also set environment NETSHARE_CIFS_FILEMODE.
  -h, --help              help for cifs
      --netrc string      The default .netrc location.  Default is the user.home directory (default "/root")
  -o, --options string    Options passed to Cifs mounts (ex: nounix,uid=433)
  -p, --password string   Password to use for mounts.  Can also set environment NETSHARE_CIFS_PASSWORD
  -s, --security string   Security mode to use for mounts (mount.cifs's sec option). Can also set environment NETSHARE_CIFS_SECURITY.
  -u, --username string   Username to use for mounts.  Can also set environment NETSHARE_CIFS_USERNAME

Global Flags:
      --basedir string   Mounted volume base directory (default "/var/lib/docker-volumes/netshare")
      --port string      TCP Port if --tcp flag is true.  :PORT for all interfaces or ADDRESS:PORT to bind. (default ":8877")
      --tcp              Bind to TCP rather than Unix sockets.  Can also be set via NETSHARE_TCP_ENABLED
      --verbose          Turns on verbose logging

Please (re-)add the missing flag or update the documenation: https://github.com/ContainX/docker-volume-netshare

@christian-weiss just released version 0.36 which should include this - cc @jakirpatel


Using Fixed addon causes element to disappear entirely.

I'm really liking your plugin, and it makes working with an off canvas menu much easier.  However, the page I'm working on has a fixed header.
I have seen and implemented the fixed elements add-on.   The issue I'm running into now, is that when I add the class "Fixed" to my element it disappears from the page entirely. Any idea what is going wrong here?  My menu is a child within the fixed header, but I'm not sure if this is playing a factor?

I'm having a similar issue. But instead of disappearing it's moving my fixed element to the bottom of the page. Has anybody run into this?

The plugin uses transform: translate3D( 80%, 0, 0 ) to slide the page out to the right. This CSS property makes the page behave like a "viewport", so all elements inside it with position: fixed will become positioned relative to the page.
To prevent this, the fixedElements add-on moved these elements out of the page and add the class "mm-slideout" to them.
Without an online example, there isn't much more I can tell you about these issues.

Here's dev page showing the issue http://marathon.newbreedmarketing.com/mmenu-test , you can see it starts at the top but then jumps down to the bottom of the page.
I'm using the following code to trigger it.
$("div#hs_menu_wrapper_top_menu").mmenu({
// options
}, {
// configuration
classNames: {
fixedElements: {
fixed: "header-container-wrapper"
}
}
});
It's worth noting that when I went the route of using jQuery to assign a class of "Fixed" to that element it caused it to disappear completely as treykane described above.
Thanks for your help!

I am seeing the same result when I place the class "Fixed" on my inner wrapper.  If I place it on the actual fixed element that is the parent of the wrapper thats when it vanishes entirely.

Note that the plugin removes the classnames specified in the classNames.fixedElements.fixed configuration option and replaces it with mm-slideout. That makes any CSS for .header-container-wrapper stop working.
My advice would be to add the classname Fixed to the element instead of changing the classNames.fixedElements.fixed configuration option.

@treykane  - this just happened to me and after pulling my hair out, I found that I had forgotten to add position:fixed; top:0; left:0; to my fixed element's CSS. Works now...


nvim-cmp and  conflict

Is there a way to get codeium to override the nvim-cmp when using <tab> to accept codeium suggestions in insert mode? Currently if there are nvim-cmp suggestions then <tab> cycles through these instead. Is there a way of having codeium take priority as the nvim copilot plugin does out the box? I don't want to remap accept to <C-g> nor do I want to integrate codeium into nvim-cmp.

i use tab for snippet jumps and codeium completion accept (i trigger it manualy when needed) so my mapping in lazy plugin manager looks like this
keys = {
	{
	    "<tab>",
	    function()
                return require("luasnip").jumpable(1) and "<Plug>luasnip-jump-next" or vim.fn["codeium#Accept"]()
	    end,
	expr = true,
	silent = true,
	mode = "i",
}

u can try similar thing (i dont know how consistent it will be on auto suggestions because of response delay)
maybe need a bit complicated if/else with cmp.visable and vim.b._codeium_completion ~=nil if u map it inside cmp.mappings table


(feat) User signup with firebase

Quick and simple signup functionality. You can see registered users at https://careful-harmonica.firebaseio.com/?page=Auth and so far I've created only one.
I thought about resetting the form to pristine, but I think we'll just have a redirect in any case.

Looks great!


No Facebook and Twitter buttons on smartphone

Can you add them in?

Thanks. Good point. We'll have a look. Another thing we are looking at: making it easier for end-users to share a specific place they find in the Shortlist.


As an OHS admin, I can import data from a data file

... so that I can continue work from where my predecessor left off.

Closing as AddressBook already supported this.


dbc order entries matters

When you generate the dbc file the order of entries matters, if the signal X is defined from bit 0 to 2 and signal Y from bit 3 to 4 you must write signal Y after signal X in the definition of the message that uses them. For now the order is random or I don't get what type of ordering is used!

the signals are sorted by name. There isn't any constraint about signal ordering in the dbc file specification

It's true that there is no constraint in the dbc, but the tooling that uses it generally doesn't reorder by position. This leaves the signal entries more cumbersome to work with.
Messages too are subject to this reordering. I think that is best to keep the same order encountered in the json file when converting from Json to dbc and the the dbc one when doing in reverse


Fix PscType integration test

PscTypeHandler:

remove companyNumber from PscType URL (not used in practice)

PscType Int Test:

import middleware mocks separately, not simple definitions from "allMiddleware.mock"
stub PscVerificationService.getPscVerification() called by fetchVerification middleware rather than stub the latter directly (more difficult).
move mockResolvedValueOnce() to beforeEach() in describe block -- seems to fix jest not applying stubbing correctly and tests calling real implementation then timing out
add back-link content check
improve describe/it text clarity

Other changes:

disable coverage in 'npm test' script to simplify debugging
change jest.runMode to "on-save"
rename int test to reflect it's for Router/Handler integration

CI: No security warnings found

CI: No security warnings found

CI: No security warnings found


Entra Rebrand

Updating all Azure AD terms to the Microsoft Entra ID terms in all md files.
Does this introduce a breaking change?
[ ] Yes
[x ] No

Pull Request Type
What kind of change does this Pull Request introduce?
[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[x] Documentation content changes
[ ] Other... Please describe:

What to Check
The updated changes to Microsoft Entra ID terminology make sense.
Other Information
Here's a link to the Rebrand guidelines. Note that the script doesn't have all the entries in the glossary that mine has. Let me know if you'd like to see my version of the script. https://review.learn.microsoft.com/en-us/entra/fundamentals/how-to-rename-azure-ad?branch=main

Closing this branch because it didn't pass all checks. This is most likely due to new changes in the main repo that haven't been reflected in my branch. Going to make a new branch and this should fix the issue.


Markup tools should be on the markup panel

MARKUP:
It’s confusing to have the markup tools hidden in the dropdown within the map screen.  The dropdown should really be within the Markup box in the menu.
From Stephanie Weyer at KZLA/ENC

GPV tools in the latest version are being stored in a single drop-down list located on the map panel.  Revised help documentation will hopefully reduce / remove any confusion about the location and use of markup tools.

I still think the markup tools should be on the markup panel.  This would actually clean up the main tool menu by removing tools that are only used a small percentage of the time.


Final removal of non-Helm based deployment

Helm-based deployment has strictly more capabilities than the non-Helm
based configuration files.  We already stopped testing the non-Helm
deployment and it has now become out-of-date with the upstream code
base.  Therefore it is time to remove the old style files to reduce
maintenance costs and avoid user confusion.

Rethinking.  Will do this in two PRs.  First a small one to remove the travisCI dependency on getting guest.auth and then a second pure removal of the kubernetes subtree.


Move to golang 1.17

Signed-off-by: David J. M. Karlsen<EMAIL_ADDRESS>

Blocked on https://github.com/kubernetes-sigs/kustomize/issues/3618


app not remembering answer for rooted device

Avoid duplicates

[x] Bug is not mentioned in the FAQ
[x ] Bug is specific for Android only, for general issues / questions that apply to iOS and Android please raise them in the documentation repository
[ x] Bug is not already reported in another issue

Technical details

Fairphone FP3
Android version:LOS 18
App version:2.12.1

Describe the bug

App warns that the phone is rooted, which is fine by me. But the app does not remember the answer and shows the same pop-up again with every start.
Steps to reproduce the issue
Start the app

Expected behaviour

The app should remember your answer, and only ask again if something changed
Possible Fix

Additional context

Internal Tracking ID: EXPOSUREAPP-10181
Internal Tracking ID: EXPOSUREAPP-10698

Another hint: This is also displayed as a false-positive on non-rooted devices with ROMs such as LineageOS.
(It feels like the "root warnings" come a little out of hand and seem to be included in some sort of "compliance" rule somewhere. If you care for security, maybe consider checking Android security patchlevel instead. This nags people with insecure devices instead of tech-savvy people with custom ROMs, often installed for security and privacy reasons).

I also found the root warning being triggered on an Android emulator (8" Fold-out using API 30) which I was using to look at layout issues on newer larger smartphones - see https://github.com/corona-warn-app/cwa-app-android/issues/4203. This admittedly is not mainstream usage and, for me, is only an annoyance for testing.

I checked the ADB logs and the thing that triggers the warning for me is "ro.debuggable" in rootbeer. So … my device goes as debuggable iff I enable debugging? That's not very surprising. And probably ok to show a warning in that case, because, ok, someone's eves-dropping on the logs.
But it counts as "debuggable" even when debugging is disabled? And it shows a warning for that? That counts as a false positive for me. And an annoying one.
Now, the question is, what's wrong here? The fact that CWA shows a warning? (at all? in this case?) The fact that rootbeer considers this an issue? Or the fact that the "ro.debuggable" property is set in the first place?
I don't know.

Can you check with root beer sample app which check is marked for you

@scoder See https://github.com/corona-warn-app/cwa-app-android/issues/4264#issuecomment-956097442

CWA logs it as ro.debuggable (before enabling ADB logging), so I'd say that's it.

https://github.com/corona-warn-app/cwa-app-android/issues/4268#issuecomment-961805351

@dsarkar @heinezen
If BSI/BMG/RKI really insist of having a warning for those devices, I propose to change the way to "inform" user:

The dialog that the device is rooted (or has an opened boot loader) should be shown only once, and never again.
There could be a hint in the home screen, either as an informational tile like the incompatibility warning (https://github.com/corona-warn-app/cwa-app-android/issues/3170) or, if you like a different design, as a simple/colored text ("insecure device") below the tracing status switch.
For me looks like best compromise to fulfill the requirement of authorities and to not nag advanced users more than necessary.
What do you think?

@dsarkar @heinezen If BSI/BMG/RKI really insist on having a permanent warning for those devices, I propose to change the way to "inform" user:

The dialog that the device is rooted (or has an opened boot loader) should be shown only once, and never again.
There could be a hint in the home screen, either as an informational tile like the incompatibility warning (Incompatibility warning after updating to version 2.2.1 #3170) or, if you like a different design, as a simple/colored text ("insecure device") below the tracing status switch.

For me looks like best compromise to fulfill the requirement of authorities and to not nag advanced users more than necessary. What do you think?

I don't like the idea of a permanent warning banner or whatever in a prominent position in the app (read: in your face).
This would make a lot of people frown and wonder, especially if the device isn't rooted at all.
Better change to a library/piece of code that correctly checks root or no root and doesn't claim a device to be unsafe if it in fact isn't.

Hi @x2k13 ,
thanks for your feedback.
We need to separate two different issues:

rootbeer reporting false positives
the way of displaying a warning in case of a true positive.

My proposal above was for point 2. only: displaying a warning in case of a true positive. It looks like it's a requirement/strong recommendation from authorities, to have a warning displayed when the device is rooted. The way to achive this that I proposed might be the least annoying way. Advanced users that intentionally rooted their devices will continue to ignore the warning. In the rare cases where unadvanced users have an unrooted device by accident/by abuse from third parties, they will seek help to understand, what is going on - and can then decide on what to do next.

I don't like the idea of a permanent warning banner or whatever in a prominent position in the app (read: in your face).
This would make a lot of people frown and wonder, especially if the device isn't rooted at all.
Better change to a library/piece of code that correctly checks root or no root and doesn't claim a device to be unsafe if it in fact isn't. Banking apps are known to be really picky about rooted devices, but these recognise root more efficiently and correctly than CWA does atm.

Related to the false positives, point 1.: It will need to be determined more clearly, what actually is a false positive: A mainstream device from a known brand with stock rom and no root which is detected of having root falsely? Or a customized mobile with an open bootloader but no root - could the open boot loader be abused? When there is a common agreement, and there is actually a bug in the root detector, it should be fixed.
In either way, even in these cases of false positives, it may be better to have a less annoying display of a warning instead of a multiple-times-pop-up of a warning dialog. Won't you agree?

It looks like it's a requirement/strong recommendation from authorities, to have a warning displayed when the device is rooted.

Do you have a reference link to this requirement or strong recommendation? Things do not necessarily make sense just because everyone else is doing it.
Is there any BSI notice where this is clearly stated? I doubt it.

The way to achive this that I proposed might be the least annoying way. Advanced users that intentionally rooted their devices will continue to ignore the warning. In the rare cases where unadvanced users have an unrooted device by accident/by abuse from third parties, they will seek help to understand, what is going on - and can then decide on what to do next.

And when (If that will ever happen), someone has to scan your certificate in your CWA, sees a permanent red banner and does not accept the certificate and rejects your attendance at an event, just because "oh you obviously hacked the cwa app to trick me"?
A permanent banner, exactly as an eacht-time warning on startup is and stays an act of paternalism.
Why to care about false positives in the first place? If anyone gets a false positive warning which carries a checkbox that will lead to a suppression of subsequent warnings, they can acknowledge it and do not get bothered anymore.

@darkmattercoder

Do you have a reference link to this requirement or strong recommendation? Things do not necessarily make sense just because everyone else is doing it.
Is there any BSI notice where this is clearly stated? I doubt it.

That introducing a "root warning" may be a requirement from authorities is my assumption based on these experiences:

BSI takes care a lot of issues, that are not always considered to be a threat neither by (advanced) users nor by our developers. Just take a look here, read a bit, and then it should be obvious, that at least it is rather likely that BSI actively suggested to introduce this "feature": https://github.com/corona-warn-app/cwa-app-android/issues?q=+is%3Aissue+author%3Absi-tf-cwa That we didn't see an open issue created by @BSI-TF-CWA here to implmement a "root warning" anymore could be the result of recent complaints of SAP staff and also of users, not to disclose security related issues via github anymore.
I'm following here for quite a while, and just by discussions with devs and project leads I don't have the feeling that they were keen to introduce that "feature" on their own action. I guess the devs here share many of your ideas/opinions/attitudes - but for some good reason they can not always shout out loud how happy they are to introduce features like the "root warning" 😉

So, partly you're true, I don't have a proof that there was a requirement from "outside"/authorities to implement a root warning, even it's likely they did. Maybe @thomasaugsten or @mlenkeit or even the @BSI-TF-CWA could share some details who wanted to have it integrated and why?

And when (If that will ever happen), someone has to scan your certificate in your CWA, sees a permanent red banner and does not accept the certificate and rejects your attendance at an event, just because "oh you obviously hacked the cwa app to trick me"?

That is indeed a very good point that needs to be taken into account! At least, after you activated the app and switched to the "certificate screen", no warning is/should be visible.

A permanent banner, exactly as an eacht-time warning on startup is and stays an act of paternalism.

This is a political discussion. My feeling is, that the person who recommended to implement this feature actually wanted to protect users who have no idea that their mobile is "vulnerable" and their CWA data (ie. medical data) is unsafe. This person judged the protection of clueless users higher than nagging advanced users with intentionally customized OS. Please don't discuss this special point with me, you would run into an open door. Generally speaking, who feels paternalized and when is a big social and cultural issue currently. How many people feel paternalized because they need to prove their vaccination/test/recovery status when they want to enter a bar? I have not root, currently. But if I had, I'd be happy to be able to simply ignore the warning and I would feel good that other clueless users with unintentional root are now protected. Why should I care more? It's not to nag me but protect others.

Why to care about false positives in the first place? If anyone gets a false positive warning which carries a checkbox that will lead to a suppression of subsequent warnings, they can acknowledge it and do not get bothered anymore.

That has been discussed here before. I don't know why this hasn't been implemented like this. Either there is the requirement to have a permanent warning, or a change of behavior was not developing priority yet. Maybe @dsarkar or @heinezen could bring in some light here?
In any case, enjoy your week-end!

@x2k13
The reason why the root beer lib signaled a red alert, could be the DangerousProps:
If you feel nagged, you may look here https://www.reddit.com/r/LineageOS/comments/cyy9aj/how_to_get_pass_on_native_root_checker/ and follow the instructions from the first reply.
Basically, it's editing the default.prop and change some parameters to be more "secure", like explained in the introduction here: https://blog.snapdragon.cc/2019/09/03/fully-unroot-custom-android-roms-to-run-banking-apps/. If you're able to directly edit the props, that alone might be reason enough to give a warning...

@x2k13 The reason why the root beer lib signaled a red alert, could be the DangerousProps: If you feel nagged, you may look here https://www.reddit.com/r/LineageOS/comments/cyy9aj/how_to_get_pass_on_native_root_checker/ and follow the instructions from the first reply. Basically, it's editing the default.prop and change some parameters to be more "secure", like explained in the introduction here: https://blog.snapdragon.cc/2019/09/03/fully-unroot-custom-android-roms-to-run-banking-apps/. If you're able to directly edit the props, that alone might be reason enough to give a warning...

Yes, you guessed right. I already wrote about that here before:
https://github.com/corona-warn-app/cwa-app-android/issues/4264#issuecomment-961808532

CWA logs it as ro.debuggable (before enabling ADB logging), so I'd say that's it. EDIT: tried the sample app, just in case, same result: dangerous props.

@scoder please see https://github.com/corona-warn-app/cwa-app-android/issues/4264#issuecomment-962196355
Though there is probably not much you can do, except rooting your phone, changing default.prop params to safe values and unrooting again.

This is an interesting discussion, imho.
What I again and again am flabbergasted is, postmarket and current, rooted, roms are flagged, but people with lollipop roms go unmolested. Sure, they shouldn't been forced to throw away their devices, but the whole thing is a total hybris. People who try to stay safe are flagged, and people, who are unsafe at a probably high degree, and maybe don't know it, are lulled in safety. That's absurd.
Of course, they can show me ONCE, that i don't have a stock rom, or am rooted, or whatnot. But if i did that deliberately, I acknowledge it, because i know. And if I'm clueless, i probably acknowledge it also, because it's way above my head (and honestly, those people are not to blame, this is consumer electronics, you should not need a cs degree for it! ). So in the end, it's snake oil. And absolute helplessness of any agency, be it a BSI or whatever. That's not honest

As this ist an Open source project and the topic has been around for a while, I wonder what the maintainer's perspective is and what their discussions internally are. We need a transparent information flow! @devs could you please elaborate and share your plans regarding this?

Still not worth elaborating on this topic from an official? This project is funded trough public money. The code already is public also. It would be nice to also have publicly available answers to upcoming questions.
I think that for now, one should be better off by using CCTG instead of CWA. It is apparently the better choice for people who are aware of their rooted devices.

Fun fact: With Magisk Hide enabled, the warning will disappear.  They do not need to see this message. If anyone with bad intentions somehow sneaks some root back door onto a phone, it will likely not be detected by other apps and hence no warning will appear.
I wonder how secure an app can be if its developers have not understood such basic principle...

Fun fact: With Magisk Hide enabled, the warning will disappear.

No worries, we are well aware of these limitations, and we also made this transparent to all involved parties 😉

Still not worth elaborating on this topic from an official?

Given it takes almost 6 months to add a few words to the FAQ, you cannot expect an answer to so complex a question in a matter of days!
Nevertheless, I came here because I was annoyed by that pointless nagging as well and intended to file a bug about it.
So, I am very much interested about the reasoning behind that user-unfriendly and rather meaningless decision (as several people already pointed out) as well.

Internal Tracking ID: EXPOSUREAPP-10181
Internal Tracking ID: EXPOSUREAPP-10698

Dear @2019-05-10, dear community,
Obviously this feature was implemented not to "nag" anybody, but because stakeholders requested so, and this is related to the strong protection of privacy, that might be undermined on rooted devices (of course not necessarily).
The main thought was, that is my understanding, that some users might not know that their device is rooted and therefore there might exist some possibility of vulnerability. To answer the question, why would somebody not know about his device being rooted: Second hand device, somebody gets a new phone and gives away his rooted device,...
However, due to the large feedback, it is being discussed and planned to change the behaviour, i.e. the frequency how often this message shall be shown and in which situation.
Of course we understand that, in particular, the more technically inclined user feels somehow "annoyed", however, it is, as usual, always quite a balancing act to find the middle ground between all the different requirements and criteria.
Anyway, as said, we might expect some changes.
Best wished, DS

Corona-Warn-App Open Source Team

@dsarkar I am sorry, but in my opinion this is a very constructed situation. It should be very obvious that this message hits almost exclusively people which are very well aware that their device is rooted. On the other hand even the concern about second hand devices is also misguided: rooting itself does not compromise privacy in any way. Only if apps are installed which intentionally compromise privacy this poses a problem. Now the key point is, especially for second hand devices it is very likely that no rooting is required for this. Any older Android version (as any other older operating system) has security holes which can be abused.
So if stakeholders were really concerned about about privacy, why does a rooted device give a warning but the app can run on Android 6.0 without any warning? In my eyes this is not plausible. Either the stakeholders have no sense about software security, or they want to nag us. Both ways this is bad.
You might say I am overreacting. Yes maybe, but this is not the first app annoying people like me with such messages. This is especially problematic if apps are not only showing annoying messages but stop functioning because of such misguided arguments. So please, dear Corona-Warn-App Open Source Team, take this message back to your stakeholders. This is not protecting privacy, it is not making any thing more secure. The only effect this kind of false protection has is to make devices quicker obsolete (because people get pushed away from using aftermarket firmware with longer support).  So please stop it!

the stakeholders have no sense about software security

This one.
Remember, those mysterious stakeholders are the same people responsible for monoculture of MS products in the public administration.
Tells you everything you need to know about their idea of "security" (I guess, they are used to simply dismiss any popup anyway w/o reading it).

PR:  #4550

Hi @klic,
Thanks for your suggestion. We suggest that with the implementation of R 2.16 this issue can be closed.
Best wishes, DS

Corona-Warn-App Open Source Team

I still think showing this message at all is wrong. The app should not even perform any such check. It's not the app's business whether it runs on a rooted phone. Please remove any SafetyNet check from the app. This app is not even remotely security related. Stop poking your nose into such business.

Hi all guys with a rooted phone, we could need your help in a different issue.
There may be a bug in the Exposure Notification System that leads to filling up internal storage until the system runs out of free space.
If you may help, please leave a note over https://github.com/corona-warn-app/cwa-app-android/issues/4732
Thank you!

@dsarkar Please close this issue now.

@mhier

The app should not even perform any such check. It's not the app's business whether it runs on a rooted phone.

I suggest to open a new enhancement request reg. this.

This app is not even remotely security related.

While it is not security related, it stores highly sensitive health information, including information on vaccination, recovery & test.

I support closing this issue. The original problem description is solved.
I verified on current versions. Although it is a false positive to declare a Pixel 3a emulator running Android 6.0 as a rooted device, I used it to check the suppression of the message until an update was done.

Install CWA 2.20.4 on Pixel 3a emulator API 23 (Android 6.0)
"Security Note" regarding root is immediately displayed
Tap "OK"
Complete onboarding
FORCE STOP CWA
Open CWA and confirm that "Security Note" is shown
Tap on "Hide notification until next update" to enable, click OK
FORCE STOP CWA
Open CWA and confirm that no "Security Note" is shown
Update CWA to 2.21.1
Confirm that "Security Note" is shown again
Tap on "Hide notification until next update" to enable, click OK
Tap "Next" to acknowledge new version information
FORCE STOP CWA
Open CWA and confirm that no "Security Note" is shown


Nvidia GTX 980 "(EE) No devices detected"

I am unable to start Xorg due to a Nvidia problem on my desktop NixOS machine running the latest NixOS master with the latest kernel package.
The main error in my X log is this:
[   719.532] (EE) No devices detected.
[   719.532] (EE)
Fatal server error:
[   719.532] (EE) no screens found(EE)

I have read many threads from other people having similar issues, most of which seemed to be resolved by enabling both "intel" and "nvidia" graphics drivers, but this did not work for me (maybe not surprising as this is not a laptop and has no Intel GPU.)
Can someone please suggest a way to troubleshoot this?
Attempts
I have had Xorg running with Nvidia drivers on this same machine using an only slightly different configuration and older NixOS version. However, alas, I have lost the details of this setup.
I have tried using [ "intel" "nvidia" ] as Xorg drivers.
I have tried several different recent NixOS releases.
I have tried the latest kernel package and the default kernel package.
Hardware
This is a Supermicro desktop dual-socket Xeon E5 with a GeForce GTX 980 card in a PCIe x16 slot.
Configuration and logs

X.0.log
configuration.nix
lsmod
dmesg | grep -i nvidia
lspci
nvidia-smi

I'd try just [ "nvidia" ] as the driver set.  IIRC there's not a good support for drivers from multiple packages at once.  I looked at our driver version's changelog, and your card is explicitly listed as supported.

@vcunat no dice - that's the config that's not working with the logs above.

That must be some older master, as the log shows driver version 435.21 and on master I see 440.44, but both version explicitly list your card as supported, so I don't expect upgrading will help by itself.

This might just be a conflict when it can't figure out which GPU to use?
Anyway you probably just want to use just [ "nvidia" ] while configuring the PCI ID in the Xorg configuration or trying Prime Sync.

I am using only [ "nvidia" ]. That's what in the config and the logs above. Any other ideas? (I have also tried running the latest master from today but no change.)
I only mentioned having tried [ "intel" "nvidia" ] because that was the resolution for many other people who experienced problems with the same Xorg error message.

I have been meaning to troubleshoot this further but now it's two months later I don't really have any new ideas. I already spent about a day trying all the ideas that I could find on the internet and nothing worked.
Guess I'll order a Radeon and hope that AMD drivers are more pleasant to work with. If anybody has a last "hail mary" idea before I do that though then please let me know :-)

Gave up.


Hangs before second stage on a real machine, works fine in QEMU

Im following the OS dev tutorial series and decided to try to run the kernel on a real machine, but it hangs indefinitely before the second stage of the bootloader.
It prints Booting... (first stage) and then hangs. No other output unfortunately.
I've tried building it in release mode (as suggested in a similar issue) but it doesn't make a difference. Everything works fine when I run it in QEMU, release or debug.
Any ideas? Would be cool to see it running on real hardware :)
Edit: I'm on macOS, booting from a USB stick. Writing the image with dd if=target/x86_64-blog_os/release/bootimage-blog_os.bin of=/dev/disk3 && sync

I cannot reproduce this unfortunately. For me it runs fine on real hardware.
It seems like the bootloader does something that does not work on your hardware, which is difficult to debug from my end. Could you try to do some debugging to find out on which instruction it hangs? The easiest way to find this out is:

Clone this bootloader project.

Replace the bootloader = 0.3.0 dependency in your kernel with a path dependency: bootloader = { path = "../bootloader" } (use the path to directory where you cloned the bootloader). Now the kernel should use your local bootloader for building.

Edit the src/stage_1.s assembly file to find out where the error occurs

The Booting... (first stage) message is printed in line 26 so we know that the problem is on a later line.
Try to insert the following lines at various places in the file to print the Booting... (first stage) message a second time:

  push esi    # backup `esi` because we overwrite it
  push eax    # backup `eax` `real_mode_println` overwrites it
  lea si, boot_start_str    # load the address of the message into `si`
  call real_mode_println    # print the message a second time
  pop eax    # restore `eax`
  pop esi    # restore `esi`

Move these lines around and try to isolate the problematic instruction this way. If you see the message twice, all preceding instructions worked. If you see the message only once, the problem is in a preceding instruction.

Sure, I will give it a shot tonight

Thanks!

Okay, so this is pretty confusing 😄  I tried to add a print after the enable_a20 instructions on line 33. It initially caused a reboot loop, but I recalled I shouldn't use 32 bit registers immediately after boot (right?) so I changed the print code to:
push si    # changed register name
push ax    # changed register name
lea si, boot_start_str    # load the address of the message into `si`
call real_mode_println    # print the message a second time
pop ax    # changed register name
pop si    # changed register name

And surprisingly, it booted into the kernel! Quickly enough that I can't see any bootloader text printed. The funny thing is, if I remove this print call again, it hangs sometime after the first print like before.
I'd love to understand why this is happening but I'm at a loss. Could it be that these few extra instructions fixes some alignment problem?

@johanhenriksson That's really strange. I updated the A20 check in https://github.com/rust-osdev/bootloader/commit/81c9761926be6cfa2c8843f531db59e754af605c (in a separate boot-fix branch). Could you try whether this works for you?
To use that branch, change your bootloader dependency to the following:
[dependencies]
bootloader = { git = "https://github.com/rust-osdev/bootloader.git", branch = "boot-fix" }

I cloned bootloader, then changed "Booting (first stage)" to "Booting (1st stage)" just to make sure I was using my local version.  That worked as expected.
I added another string constant:
boot_start_str: .asciz "Booting (1st stage)..."
debug_str: .asciz "Debug line"
error_str: .asciz "Error: "

Then tried to print it right after the first line, with the idea that I'd move "Debug line" forward until I saw one but not the other:
    # initialize stack
    mov sp, 0x7c00

    lea si, boot_start_str
    call real_mode_println

    lea si, debug_str
    call real_mode_println

However when I do this, I only see the first line.  I don't see the "Debug line" I added.  Does this mean the call to real_mode_println itself is causing the freeze or am I calling it wrong the second time?  Thanks!

@johnwstanford Thanks! I looked over the real_mode_println function and saw that it tries to do addressing with a 32-bit register here, which should not work. I think this is a copy&paste error. Could you change the [esi] to [si] and try again?

The boot-fix branch seems to work for me 👍

@johanhenriksson Great, thanks for testing! I will merge the branch and pusblish a new version.

The change you told me to try didn't work, but I pulled down merge #46 and that one works for me :) Thanks!

@johnwstanford Awesome! It should be published on crates.io as version 0.3.13.
I think we can close this issue then.

@johnwstanford

The change you told me to try didn't work

Just to clarify: It didn't fix the issue of booting on real hardware, or it didn't work at all? Because it seems like a bug to me and I would like to fix it even if it wasn't the cause of this issue.

@phil-opp Yes, changing [esi] to [si] at line 128 (now line 133) didn't fix the problem for me.  I got the same behavior where it compiled and started booting, but got hung at "Booting (first stage)..."  However, I pulled merge #46 down, compiled it, and now it works on real hardware like it's supposed to, but it still has [esi] instead of [si] at line 133 of stage_1.s.  I tried two different types of hardware and it works on both.  If it's helpful, I could change [esi] to [si] and make sure it still works.  Thanks!

@johnwstanford Thanks for testing!

If it's helpful, I could change [esi] to [si] and make sure it still works.

That would be great! I'm pretty sure that it's a bug, but I don't want to break anything. Could you try depending on #47:
[dependencies]
bootloader = { git = "https://github.com/rust-osdev/bootloader.git", branch = "fix" }

No problem.  That branch works on the real hardware too.

Perfect, thanks!


Adds rustfmt config

I want to play with this a little bit more to find some styles that I like, but wanted to at least make this visible

I really, really like the TODO/FIXME unnumbered feature. I'm going to open issues to capture those  comments and update them to point to the issue numbers. Prepare for email spam

Okay, this should be ready to merge

Womp womp.
It's only breaking on nightly, though.


Added text editor path variable option

Added the menu item "User Config" under "File" menu, moving there the other variable settings dialogs.
Now, when comes the time to open the text editor, PerfView can look at this variable to check if it's any path configured there to open the source code, instead of the built-in text editor or the fixed notepad.
I've also included some entries for the new variable in "User Guide".

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

@cirojr, I'm going to close this for now.  Feel free to re-open with @vancem's feedback addressed.  Thank you.


Stacks initial integration (send/receive)

📝 Description
Stacks blockchain initial integration : add accounts  / sync / receive / send
Backport of https://github.com/LedgerHQ/ledger-live/pull/3257 contribution from Zondax.
❓ Context

Impacted projects: LLC LLD LLM CLI coin-framework cryptoassets
Linked resource(s):

https://ledgerhq.atlassian.net/browse/LIVE-4790
https://ledgerhq.atlassian.net/browse/LIVE-4789

✅ Checklist

[x] Test coverage
[x] Atomic delivery
[x] No breaking changes

📸 Demo

🚀 Expectations to reach
Please make sure you follow these Important Steps.
Pull Requests must pass the CI and be internally validated in order to be merged.

👋  we have recently merged https://github.com/LedgerHQ/ledger-live/pull/3455 in develop branch which reinforces the TypeScript checks, mostly related to modals and coin families. Could you rebase and check that everything still pass?
Thanks,
gre.


fix: add name to package json

Adding "name" to the package.json, to avoid the package-lock.json "name" value being updated when running npm build if the repo is cloned a different directory name.
If you clone the demo repo to a directory called "filamentdemo" and run npm install, you should see that the package-lock.json updates to match your direct name, which is not desirable as it will conflict on further pull or could be committed in error.

Thanks


use namespace for service directory

@miltontony Ready for review

You'll have to add the namespace to all the {% url 'molo.servicedirectory:...' %} in these templates (both old and new)
https://github.com/praekelt/molo-tuneme/tree/develop/tuneme/templates/old/servicedirectory

👍


How to disable mouse wheel event which changes the range of availability chart

I am trying to disable the mouse wheel event on availablity chart, but I am not able to make it.
Any help appreciated

Hello Team,
Can anyone help us in this?


CognitoIDP: fix REFRESH_TOKEN_AUTH flow in admin_initiate_auth()

Fix https://github.com/getmoto/moto/issues/5871

Codecov Report

Merging #5872 (fba67e5) into master (b0ee64f) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master    #5872   +/-   ##
=======================================
  Coverage   96.18%   96.18%
=======================================
  Files         757      757
  Lines       74407    74408    +1
=======================================
+ Hits        71565    71566    +1
  Misses       2842     2842

Flag
Coverage Δ

servertests
36.98% <0.00%> (+<0.01%)
:arrow_up:

unittests
96.12% <100.00%> (+<0.01%)
:arrow_up:

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

Impacted Files
Coverage Δ

moto/cognitoidp/models.py
95.65% <100.00%> (ø)

moto/ec2/responses/fleets.py
100.00% <0.00%> (ø)

moto/ec2/models/fleets.py
95.10% <0.00%> (+0.03%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


edited the landing page with the theme

Issue <39> 🎯🎯
Description
I changed the theme of the landing page and i linked the css correctly
Screenshots 📷

You solved #39 . Even i could not understand that PR.
Two things I want to mention:

Don't worry about merge conflicts for now.

We will get to you by 8 am IST

There was a merge conflict.
Even If I update changes are not showing. Please make a new PR with latest code.


⚠ Bofrost.es has degraded performance

In a52ce74, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1402 ms

Resolved: Bofrost.es performance has improved in 6330b35 after 6 minutes.


Fix: English footer uses correct links (Closes #11)

This PR corrects wrong links in the English footer.

Closes #11

@Ein-Tim Thanks!


[InstagramBridge] Link on image, video indication in title

A couple of improvements for the Instagram bridge:

In item content, the image is now a clickable link to the post;
In item title a ▶ is prepended if the post contains a video; it's impossible to tell from the content image.

Merged. Thanks for the PR!


Create runecost

Adds a simple panel to the game that allows you to calculate how much it would cost to purchase runes from certain rune shops in the game.

Added License to repo

It looks like you forgot to remove com/example from your source?
Your plugin adds a panel during startup but never removes it. Please remove it on shutdown so disabling this plugin would actually remove the sidebar panel button

I think it should be updated with the requirements.  Let me know if I need to adjust more to the requirements.


Improve cold start

Summary
Improving cold start by removing the need to import some files during startup operation, those files are still loaded but deferred by using inline requires.
The Syntax highlight library seems to be extremely large and thus was taking a while to load and the Emojis require the emoji.json file which is 1.1Mb in size to be loaded as well.
When the app opens (specially for if the current server is licensed) it mounts the AnnoucementBanner component which uses RemoveMarkdown and one of the children uses Markdown this two last components have imports for Emoji and SyntaxHighlight. Also the ChannelItem(s) shown in the home screen for DM's it would use the Emoji component
To test this is required to run the app in release mode for example with npm run android -- --variant=release and then compare it with the main branch
NONE

LGTM - I'm going to run it before approving


Update chrome-devtools-frontend?

Latest versions of chrome-devtools-frontend are not building correctly in current configuration. Can that be fixed?

Done!


UE4 program crashes when using the latest AMD Graphic Driver (Ver 21.4.1)

When set Ray Tracer to AMD Radeon Rays or set Convolution Type to AMD TrueAudio Next, the packaged UE4 program crashes on startup.

Crash.zip
It's OK when using old AMD Graphic Driver (Ver 21.3.1)

Hello @Papyrus-G, the minidump you attached is a EXCEPTION_ACCESS_VIOLATION_READ in amdocl64.dll, can you clarify why you think this is a steam-audio issue and not a video driver or upstream UE4 issue?

Sorry for causing trouble to you. I don't know much about dump file, I spend a while thinking who I should report this issue to.
Thanks for your Friendly response, I will test this on other platform and send an issue report to AMD if needed.


README updates

make debootstrap and make build-base were out of order: the latter calls make install-kernel-modules which relies on the qemu disk being setup (through mkfs.ext4 $(disk) in make debootstrap)
also, there was a small typo regarding the constant.sh file

make debootstrap has to be run first as it builds the vanilla kernel including LKMs that need to be in the root filesystem.

Actually, $mnt and $disk are prerequisites of debootstrap so it works without explicitly specifying. But it's good to list them in the README.

Correction: you were right about the order! Thank you for calling it out!

Thank you @jo285317 !!