Black formatter doesn't format

Environment data

VS Code version:  1.32.3
OS and version: Mac OS X 10.14.3
Python version (& distribution if applicable, e.g. Anaconda): 3.6
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): virtualenv

Expected behaviour
black to auto-format files.
Actual behaviour
I use black as my main formatter. Neither when saving files nor clicking option+shift+f my files are getting formatted. I can see the message Formatting with black on the status bar, but nothing happens.
My black path is set to /Library/Frameworks/Python.framework/Versions/3.6/bin/black, and when I use the command line to run the following command, the file is getting formatted.
/Library/Frameworks/Python.framework/Versions/3.6/bin/black FILE_TO_FORMAT

If I choose a different formatter as default, say autopep8, everything works correctly.

I edited autopep8 path to be black's path, still nothing.
When setting black path to black and installing black on virtualenv, it works.

Bump as having same issue...

Same on Linux, py 3.7, /usr/bin/black.

@ericsnowcurrently 	this might be handy https://github.com/Microsoft/vscode-python/issues/4841#issuecomment-475725675

@AdamGold, thanks for letting us know about this.  I was able to reproduce the problem at first.  However, once I set "editor.formatOnSave" to true in my workspace settings, everything worked as expected.  Do you have the latter in your settings?  Would you mind pasting your settings.json in this issue?  Thanks!

@ericsnowcurrently, "editor.formatOnSave" is set to true. The thing is that the formatter doesn't work at all, even when I run "format file" manually (option+shift+f).
  At this point the only way I can reproduce the problem you are describing is if I add a syntax error into the file I'm trying to format.  This is the same as described in the issue that Don linked (https://github.com/Microsoft/vscode-python/issues/4841#issuecomment-475725675).  Please verify that the file in question is parseable (i.e. has no syntax errors).  I expect you've already checked this, but I want to be sure. :)

@ericsnowcurrently Yes, the file is parseable, when I run the black command via the command line it gets parsed.

I have the same issue, but only with black 19.3b0; try downgrading it to 18.9b0 and see if that works

FWIW, I have not been able to reproduce the problem and I am using black 19.3b0.

@AdamGold Also, we run black with the --diff and --quiet.  If you run black from the command-line with those args does everything still work for you?

I had this issue with auto-format on save only (black worked fine when I manually triggered).  It turns out that black takes a bit longer than the built in default 750ms timeout to do the re-formatting.  I was seeing the following entry in the Log (Window):
[renderer1] [warning] Aborted format on save after 750ms

I increased the timeout and that worked for me.
"editor.formatOnSaveTimeout": 3000

Thanks for the tip, @AtomicMegaNerd.  @AdamGold, does that help?

@ericsnowcurrently, somehow the formatting sorted it self. The problem no longer exists without me changing anything. I don't think I even updated / degraded black version.

@AdamGold, that's great!  I'm concerned that we didn't determine if there's a bug, but I'm glad it's working for you now. :)


chore: updates to Readme for getting started

@unamashana do you mind if I close this old PR?
From what I can see from the current diff the significant changes are about introducing ASDF and some updates to the Readme. I'll carry those over in other PRs, but this one contains more changes to Podfiles and Xcode projects that I don't think are necessary.
 ❯ g diff --stat origin/main
 .tools-version                                                        |     2 +
 README.md                                                             |    28 +-
 ios/Podfile                                                           |    32 +-
 ios/Podfile.lock                                                      |     6 +-
 ios/RNProtoType.xcodeproj/project.pbxproj                             |    12 +-
 ios/RNProtoType.xcodeproj/xcshareddata/xcschemes/RNProtoType.xcscheme |     2 +-
 package-lock.json                                                     |  2355 +++++++++++++++++------------------------------------
 package.json                                                          |     3 +-
 yarn.lock                                                             | 10584 ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 9 files changed, 813 insertions(+), 12211 deletions(-)

I closed it for you :)


Use a dynamic matrix definition in CI

Fixes #
Changes made in this Pull Request:
PR Checklist

[ ] Tests?
[ ] Docs?
[ ] CHANGELOG.md updated?
[ ] AUTHORS.md updated?
[ ] Issue raised/referenced?

time="2023-05-22T06:18:39Z" level=fatal msg="yaml: unmarshal errors:\n  line 0: cannot unmarshal !!str \"[\\\"3.9... into []interface {}"

Ok, this made it even stringier than before...


Elasticsearch Storage : javax.net.ssl.SSLHandshakeException

I am trying to connect elasticsearch which is hosted in k8s environment , But getting SSL handshake exception , Below I have mentioned my connection properties and error details , please provide if any resolution for this issue.
zipkin:
storage:
type: elasticsearch
elasticsearch:
cluster: ${ES_CLUSTER:}
hosts: ${ES_HOSTS:https://:9200}
index: ${ES_INDEX:zipkin}
index-shards: ${ES_INDEX_SHARDS:5}
index-replicas: ${ES_INDEX_REPLICAS:1}
username: ${ES_USERNAME:}
password: ${ES_PASSWORD:*****}
Error :
ERROR: cannot load service names: Request processing failed; nested exception is java.io.UncheckedIOException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

Is your certificate self-signed?


refactor [chrome-web-store] service

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @chris48s!

  Generated by :no_entry_sign: dangerJS against 053ae9748087212c65249c338ae50d76ca1cd57b


Nix flake error with pyScss

Describe the bug
Trying to use lnbits with the nix flake file I'm getting the error:
building the system configuration...
error: unsupported build system requirement pyScss

To Reproduce
Steps to reproduce the behavior:

Run nix build github:lnbits/lnbits and you should get the error

I'm not sure why pyScss was added, but maybe it's not perfectly standard-compliant since poetry2nix fails on it.

Our nix build is broken. The issue is dependencies installed in poetry not being used in the poetry build file, seems to be a poetry update. Our plan is to get the application built as we want then use nix as our quality standard as we come out of beta. I'll make a note in the install guide.

This should have been left open, since the issue was not fixed and I spent 1 hour today trying to figure out what's wrong with my setup. Please reopen ...

Reopened. Sorry about that 😬. I owe you 1hr.

Chill. This is an issue for later, as noted in the install guide. Post-beta we will some nix whizz a bounty for fixing our nix build

I think the pyScss error is caused by the fact that in nixpkgs it is published under pythonPackages.pyscss (note the un-capitalized s). Changing pyproject.toml to use pyscss instead fixes that error, but now I'm getting a different issue about infinite recursion caused by setuptools...

Changing pyproject.toml to use pyscss instead fixes that error, but now I'm getting a different issue about infinite recursion caused by setuptools...

You can try removing pyScss from pyproject.toml:57:
--- a/pyproject.toml
+++ b/pyproject.toml
@@ -54,7 +54,7 @@ flake8 = { version = "^6.0.0", python = ">=3.8.1" }
 pylint = { version = "^2.15.10", python = ">=3.7.2" }

 [build-system]
-requires = ["poetry-core>=1.0.0", "pyScss"]
+requires = ["poetry-core>=1.0.0"]
 build-backend = "poetry.core.masonry.api"

 [tool.poetry.scripts]

Coincidentally, I was playing with the issue earlier today and being not able to crack it once again, I opened an issue on NixOS community forum. Maybe someone can help us: https://discourse.nixos.org/t/help-with-flake-poetry2nix-unsupported-build-system-requirement-pyscss/26137

Changing pyproject.toml to use pyscss instead fixes that error, but now I'm getting a different issue about infinite recursion caused by setuptools...

You can try removing pyScss from pyproject.toml:57:
--- a/pyproject.toml
+++ b/pyproject.toml
@@ -54,7 +54,7 @@ flake8 = { version = "^6.0.0", python = ">=3.8.1" }
 pylint = { version = "^2.15.10", python = ">=3.7.2" }

 [build-system]
-requires = ["poetry-core>=1.0.0", "pyScss"]
+requires = ["poetry-core>=1.0.0"]
 build-backend = "poetry.core.masonry.api"

 [tool.poetry.scripts]

But in any case, if something needs patching it's poetry2nix and not pyproject.toml. Let's see if we are able to crack the code :D

if you remove it like that poetry install will fail :D

Yeah you shouldn't remove it, just change it to pyscss without the capital S

Btw I understand nix support is not a priority right now, but keep in mind that with nix you can't modify the source code directory because it's in the nix store which is read-only.
So the new thing where you can install extensions will have to be changed quite a bit, you'll have to install the extensions in a separate writable path and then load them from there. Just a heads up.


fix breaking bug

The keycodes map was had a comma missing on line 112, and the site was broken. Fixed by adding a comma.

+1 - http://keycode.info is affected.

Yikes - I guess I should have some integration tests eh? Thanks for the heads up!


adding raw irc command to get JOIN/PART messages

This allows the robot.enter and robot.leave functions to operate as a developer might expect them.
Taken from IRC configuration explained here
Search for "JOINS/PARTS - General"

Alright, thanks for this.


crash

Ever since the new map update i keep getting a crash on adapting history. I deleted the victoria 2 folder in documents and reinstalled the mod to no avail. Is there a way to fix this?

Did you delete the map cache of Victoria 2 in Program Files also did you just delete the map cache in the documents folder or did you delete the entire Victoria folder in documents.

1 no
2 both (deleted cache but it did not work. then deleted the whole folder still did not work)

Necessarycoot72 are you working with the github master?
If so, I am sorry, I am working on #709 using a real map projection instead of Vic2 obstructed map. It loads (screen shot below) (clear cache before starting the game). A need to correct the positions.txt in order to play (a lot of work..)
I committed a temporary reversion of the #709, update your clone and it should be possible to work from the master again. (simsulla is embraced by his bad work practice in messing up github head... )
Kerguelen Island and new sea floor

Have committed a reversal, now it should be possible to work on the github master again.


[turborepo] [husky] Husky does not work in turborepo

What version of Turborepo are you using?
1.10.12
What package manager are you using / does the bug impact?
pnpm
What operating system are you using?
Mac
Describe the Bug
I am adding husky and once I commit there is this error:
trixobird@MacBook-Pro husky-turborepo % git commit -m"Add husky"

> husky-turborepo@ lint /Users/trixobird/w/testing/node/husky-turborepo
> turbo run lint

Turborepo did not find the correct binary for your platform.
We will attempt to install it now.
Installation has failed.

***

Turborepo failed to start.

Turborepo detected that you are running:
darwin 64

***

We were not able to find the binary at:
turbo-darwin-64/bin/turbo

We looked for it at:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>/Users/trixobird/w/testing/node/husky-turborepo/node_modules/.pnpm/node_modules
/Users/trixobird/w/testing/node/husky-turborepo/node_modules
/Users/trixobird/w/testing/node/node_modules
/Users/trixobird/w/testing/node_modules
/Users/trixobird/w/node_modules
/Users/trixobird/node_modules
/Users/node_modules
/node_modules
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>/Users/trixobird/w/testing/node/husky-turborepo/node_modules/.pnpm/node_modules
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>/Users/trixobird/Library/pnpm/global/5/.pnpm/node_modules
/Users/trixobird/.node_modules
/Users/trixobird/.node_libraries
/usr/local/lib/node

***

Turborepo checked to see if binaries for another platform are installed.
This typically indicates an error in sharing of pre-resolved node_modules across platforms.
One common reason for this is copying files to Docker.

We found these unnecessary binaries:
turbo-darwin-arm64/bin/turbo

***

If you believe this is an error, please include this message in your report.
 ELIFECYCLE  Command failed with exit code 1.
husky - pre-commit hook exited with code 1 (error)
trixobird@MacBook-Pro husky-turborepo %

Expected Behavior
I am expecting to have the pre commit checks ran and the commit
To Reproduce
pnpm dlx create-turbo@latest
pnpm dlx husky-init && pnpm install
commit
Reproduction Repo
No response

Hi! Thanks for the report! I just checked and have managed to repro on my Mac. I am going to dig in to this. We distribute binaries with our packages and it seems like something in that system has broken on this case. I'll update here with progress.
Cheers
Alex

@trixobird Hey! Are you running an Apple ARM processor or an Intel processor? This is a bit interesting:
Turborepo detected that you are running:
darwin 64

***

We were not able to find the binary at:
turbo-darwin-64/bin/turbo

***

We found these unnecessary binaries:
turbo-darwin-arm64/bin/turbo

I also need the contents of .husky pre-commit since it appears to have been changed. The default generated version of this is:
#!/usr/bin/env sh
. "$(dirname -- "$0")/_/husky.sh"

npm test

But from your output it appears to be calling lint, so I need to know what you modified the file to be:
> husky-turborepo@ lint /Users/trixobird/w/testing/node/husky-turborepo
> turbo run lint

So, given that things are in a weird state (based upon the error message contents), I hypothesize that you have mixed package manager usage in your project or that you have a lot of latent packages sitting around in global namespace. I'm entirely unable to reproduce the failure, and I've tried to reproduce:

Exactly as shipped.

pnpm dlx create-turbo@latest
pnpm dlx husky-init
pnpm install
git commit -m "Fails because the pre-commit hook defaults to npm test"

Local Installation.

#!/usr/bin/env sh
. "$(dirname -- "$0")/_/husky.sh"

Global installation.

#!/usr/bin/env sh
. "$(dirname -- "$0")/_/husky.sh"

turbo lint

After upgrading.

pnpm dlx @turbo/codemod update

Given that I'm unable to reproduce (and believe me, I tried!) I'm going to have to assume that the behavior you're seeing is a problem unique to your setup. If you can provide me a lot more detail about things like what is in your cache, which exact executable is running (which turbo), turbo --skip-infer --version, node -p "process.arch", I might be able to figure out how you got here.

pnpm dlx create-turbo@latest issue-5804 pnpm
cd issue-5804
pnpm dlx husky-init
pnpm install
sed -i "" "s/npm test/pnpm lint/g" ".husky/pre-commit"
git add --all
git commit -m "Test it works."

If that fails with copy/paste then the only inputs that can possibly be impacting you are:

pnpm version
node version
pnpm cache

Only one thing stands out: it's attempting to load -64 on your -arm64 device. Did you install node 64 instead of node arm64?
Can you also remove your global pnpm cache and try again?
pnpm store path
Then rm it.

Also, if you're copy/pasting that test script exactly the directory lookups should not contain<EMAIL_ADDRESS>at all. This indicates to me that your local module cache is poisoned or you have some sort of global pnpm config.
(Or there's an additional step you're doing that I'm not.)

I removed pnpn and node and reinstall it, and everything is working now. Thank you :)


Change uses of BGRA for images to RGBA and use image-rs 0.24

Is there a reason this was using BGRA? RGBA is more common, though BGR was historically popular at one point. image 0.24 has removed support for BGR images.
image::Handle::from_pixels() is renamed to image::Handle::from_rgba() to be more descriptive, and force any users to use RGBA instead of silently interpreting their pixels incorrectly.

Updated to fix svg rendering (by removing the RGBA -> BGRA conversion, so this is an improvement).
Apparently wgpu only guarantees Bgra8Unorm and Bgra8UnormSrgb are supported formats for surfaces, but I think for a texture RGBA should always be available?


How can i navigate pages from the code?

I am trying to make a simple login page. and is there a way to navigate pages from the code?
if(username.value==="admin")
{
  // naviagte to page1
}

link: https://demo.toolpad.io/_toolpad/app/cld06iouh01jupc7byglpysen/pages/tc03qqz

Hi @yaredtsy Apologies for responding late.
Navigating to a different page is currently supported from onCLick event handler prop of the Button component.

We'll support adding a navigation condition where you'll be able to write JS code. This will be available as a binding in this UI.
It will help if you could tell us more about what are you trying to build?


[Bug Report] el-date-picker got a problem

Element UI version
2.15.9
OS/Browsers version
macOS Big Sur
Vue version
2.7.0-beta.5
Reproduction Link
https://elementui.github.io/issue-generator/#/zh-CN
Steps to reproduce
just copy the same code form element-ui document
What is Expected?
I am not pass the placement props to the component
What is actually happening?
vue.esm.js?a026:628 [Vue warn]: Avoid mutating a prop directly since the value will be overwritten whenever the parent component re-renders. Instead, use a data or computed property based on the prop's value. Prop being mutated: "placement"
found in
--->  at packages/date-picker/src/picker.vue
 at packages/form/src/form-item.vue
 at packages/form/src/form.vue

 at node_modules/zx-layouts/VabQueryForm/VabQueryFormRightPanel.vue

 at node_modules/zx-layouts/VabQueryForm/index.vue
 at src/views/business/activity/index.vue
 at src/layouts/components/VabAppMain/index.vue
 at src/layouts/index.vue
 at src/App.vue

Seems that adding some props for Popper @XivLaw added a prop placement with the same name of data attribute:
https://github.com/ElemeFE/element/blame/dev/packages/date-picker/src/picker.vue#L101
the created() method should be updated removing old vue-popper options:
https://github.com/ElemeFE/element/blame/dev/packages/date-picker/src/picker.vue#L580-L583

Seems that adding some props for Popper @XivLaw added a prop placement with the same name of data attribute:
https://github.com/ElemeFE/element/blame/dev/packages/date-picker/src/picker.vue#L101
the created() method should be updated removing old vue-popper options:
https://github.com/ElemeFE/element/blame/dev/packages/date-picker/src/picker.vue#L580-L583

That is my fault,this pr[#21908 ] removed the placement,and fixed this problem.

Seems that adding some props for Popper @XivLaw added a prop placement with the same name of data attribute:
https://github.com/ElemeFE/element/blame/dev/packages/date-picker/src/picker.vue#L101
the created() method should be updated removing old vue-popper options:
https://github.com/ElemeFE/element/blame/dev/packages/date-picker/src/picker.vue#L580-L583

That is my fault,this pr[#21908 ] removed the placement,and fixed this problem.

When will the new version be released?

@XivLaw the two PR have different approaches,
tbh I don't know if is better to remove the prop (#21908 ) or use the currentPlacement data (#21944).

Seems that adding some props for Popper @XivLaw added a prop placement with the same name of data attribute:
https://github.com/ElemeFE/element/blame/dev/packages/date-picker/src/picker.vue#L101
the created() method should be updated removing old vue-popper options:
https://github.com/ElemeFE/element/blame/dev/packages/date-picker/src/picker.vue#L580-L583

That is my fault,this pr[#21908 ] removed the placement,and fixed this problem.

When will the new version be released?

Maybe next week,element team looks like ervery month will merge a new version.

@XivLaw the two PR have different approaches, tbh I don't know if is better to remove the prop (#21908 ) or use the currentPlacement data (#21944).

I think removed the prop will be good,because the prop didn't exist before.

Can be resolved by setting fixed version of dependency
https://github.com/ElemeFE/element/pull/21908#issuecomment-1181792082


'Subject sources' section is very specific to LwM

It expects a Mitchells file, which wouldn't be relevant to anyone else.
Not sure how to manage this yet, just noting the effect on generalisability.

Also the filenames I have now are different e.g. newspapers_overview_with_links_JISC_NLPs.csv so include information about the file for LwM data users.

I'd say we still want a Jupyter version but perhaps split out a generic version... I'll try to think about what to prioritise with the minutes I apparently have left in the budget!


Changes in Autoloader::register() method

Removed spl_autoload_extensions() function
This function is used with spl_autoload() or spl_autoload_register() (no arguments).
But CI4 does not use such methods for class autoloading.
The anonymous function defined in a class has access to the class context.
This means that we can use the $this variable inside an anonymous function.

Thank you @iRedds


[SPARK-41757][CONNECT][PYTHON][FOLLOW-UP] Enable connect.functions.col doctest

What changes were proposed in this pull request?
To reenable the doc tests for col Function, this patch makes the string representation of the Column closer to the regular PySpark Column.
This PR is a follow up to https://github.com/apache/spark/pull/39616 with enabling col doctests
Why are the changes needed?
Improve Coverage
Does this PR introduce any user-facing change?
No
How was this patch tested?
Reenabled doc tests.

Merged to master and branch-3.4.


Additional Query won't grab json Entities

The search-options generated by search-options-generate has es: namespaces in the path. That will not allow it to work with JSON entity instances.
Can we get this changed to support both?
current output for my particular entity:
<search:options xmlns:search="http://marklogic.com/appservices/search">
  <search:constraint name="entity-type">
    <search:value>
      <search:element ns="http://marklogic.com/entity-services" name="title"/>
    </search:value>
  </search:constraint>
  <search:constraint name="sku">
    <search:range type="xs:string" facet="true" collation="http://marklogic.com/collation/codepoint">
      <search:path-index xmlns:es="http://marklogic.com/entity-services">//es:instance/Product/sku</search:path-index>
    </search:range>
  </search:constraint>
  <search:constraint name="id">
    <search:value>
      <search:element ns="" name="id"/>
    </search:value>
  </search:constraint>
  <search:constraint name="price">
    <search:range type="xs:decimal" facet="true">
      <search:element ns="" name="price" xmlns:es="http://marklogic.com/entity-services"/>
    </search:range>
  </search:constraint>
  <search:values name="Product">
    <search:range type="xs:string" facet="true" collation="http://marklogic.com/collation/codepoint">
      <search:path-index xmlns:es="http://marklogic.com/entity-services">//es:instance/Product/sku</search:path-index>
    </search:range>
  </search:values>
  <search:values name="Order">
    <search:range type="xs:decimal" facet="true">
      <search:element ns="" name="price" xmlns:es="http://marklogic.com/entity-services"/>
    </search:range>
  </search:values>
  <!--Uncomment to return no results for a blank search, rather than the default of all results
 <search:term xmlns:search="http://marklogic.com/appservices/search">
  <search:empty apply="no-results"/>
</search:term>
-->
  <search:values name="uris">
    <search:uri/>
  </search:values>
  <!--Change to 'filtered' to exclude false-positives in certain searches-->
  <search:search-option>unfiltered</search:search-option>
  <!--Modify document extraction to change results returned-->
  <search:extract-document-data selected="include">
    <search:extract-path xmlns:es="http://marklogic.com/entity-services">//es:instance/(Product|Order)</search:extract-path>
  </search:extract-document-data>
  <!--Change or remove this additional-query to broaden search beyond entity instance documents-->
  <search:additional-query>
    <cts:element-query xmlns:cts="http://marklogic.com/cts">
      <cts:element xmlns:es="http://marklogic.com/entity-services">es:instance</cts:element>
      <cts:true-query/>
    </cts:element-query>
  </search:additional-query>
  <!--To return facets, change this option to 'true' and edit constraints-->
  <search:return-facets>false</search:return-facets>
  <!--To return snippets, comment out or remove this option-->
  <search:transform-results apply="empty-snippet"/>
</search:options>

Yes, this is a bug.  I missed the change in 9.0-3 work.  I also ran into it the issue recently, annoying.  Of course the short term workaround is to edit the options.  If you generate a TDE template, you'll see the approach I took to address namespaces -- do you think something here would be similarly appropriate?

Since this was brought to my attention, ill get on having a fix in 9.05

Looks good to me.
On Tue, Feb 13, 2018 at 2:38 PM, Charles Greer<EMAIL_ADDRESS>wrote:

Looks like this will do the trick -- what do you think @paxtonhare
https://github.com/paxtonhare ?
search:additional-query
1580             <cts:or-query xmlns:cts="http://marklogic.com/cts">
1581                 cts:json-property-scope-query
1582                     cts:propertyinstance</cts:property>
1583                     cts:true-query/
1584                 </cts:json-property-scope-query>
1585                 cts:element-query
1586                     <cts:element xmlns:es="http://marklogic.com/entity-services">es:instance</cts:element>
1587                     cts:true-query/
1588                 </cts:element-query>
1589             </cts:or-query>
1590         </search:additional-query>,
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/marklogic/entity-services/issues/359#issuecomment-365379520,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAmebh_cJseOJISOM8uYP6KcZVgMgU2Pks5tUeShgaJpZM4Qd_P8
.

So this fix is in develop now, assigned to @bsrikan to ensure testing coverage (which in this case is not too critical i think...)

Tests added and running in regression. Shipping this.

This bugfix has caused another bug. Line 144 of this file causes problems with any namespace ending in es:. We have discovered this because we are using an entity with namespace pasdes: and it is replaced by pasd*: by this fix.
At the minimum this needs to be replaced by fn:replace($n, "^es:$", "*:") but ideally the namespace itself should be checked for the entity services namespace, rather than relying on the prefix to be set to a particular value.

@epilith , this repository no longer reflects the current state of Entity Services, which was moved into the internal repository for MarkLogic server (because Entity Services is distributed with a server).
The best way to report an issue with Entity Services now is to work with MarkLogic support to file the issue.
I'll explore having this repository removed now so other users don't make the natural assumption that it reflects the current state of the code or that it is the right place to file issues.  Apologies about the misdirect.


[Feature]  Adding Hover Effect o social media icons

Description
Adding effects on social media icon oh hover according to their logo color
Screenshots

https://github.com/Rakesh9100/CalcDiverse/assets/168854094/54e5ade0-f50c-4e91-96e2-49bc9a7d826a
Checklist

[X] I have checked the existing issues.
[X] I follow Contributing Guidelines of this project.
[X] I am a GSSOC'24 contributor.
[ ] I am a IWOC'24 contributor.
[ ] I am a JWOC'24 contributor.
[ ] I am a SWOC'24 contributor.

Code of Conduct

[X] I agree to follow this project's "Code of Conduct".

@Rakesh9100 Sir , please assign this issue to me.

@Rakesh9100 this issue can be assigned

We already have colored hover effect on each of the social icons, pls check the website once and tell me @TBorundia


Plugin Push não funciona no Android

Expected Behaviour
Seguindo o passo-a-passo de vocês, o esperado é que variando o senderID, varie também o registratioID.
Actual Behaviour
Quando alterado o senderID, ele retorna o mesmo registrationID
Reproduce Scenario (including but not limited to)
Utilizando o Phonegap for Desktop, e abrindo ele no meu celular Android, ele retorna o registrationID, e apenas alterando o senderID do código e atualizando o aplicativo ele retorna o mesmo registrationID
Steps to Reproduce
Ao aplicar um senderID no código, visualizar o retorno no registrationID, assim que houver esse retorno, alterar o senderID, e ele retornará o mesmo registrationID de antes
Platform and Version (eg. Android 5.0 or iOS 9.2.1)
Android 7.1.1
(Android) What device vendor (e.g. Samsung, HTC, Sony...)
Lenovo Moto Z Play
Cordova CLI version and cordova platform version
cordova --version                                    # e.g. 6.5.0
cordova platform version android                     # e.g. 6.3.1

Plugin version
cordova plugin version | grep phonegap-plugin-push   # e.g. 2.1.2

Sample Push Data Payload
Sample Code that illustrates the problem
const push = PushNotification.init({
          "android": {
              "senderID": "262272254309"
          },
          "ios": {
              "gcmSandbox": false,
              "sound": true,
              "vibration": true,
              "badge": true,
              "alert": true
          },
          "windows": {}
      });
      push.on('registration', (data) => {
          alert('on registration');
          $.post( webService + 'Registro_Dispositivo/Salvar', {
              "id": data.registrationId,
              "plataforma": device.platform
          }) .always (function (){
              window.localStorage.setItem(appnome + "-registrationId", data.registrationId);
              alert(data.registrationId);
          });
      });
      push.on('notification', (data) => {
          var href = '#/' + data.additionalData.link;
          window.location.href = href;
      });
      push.on('error', (e) => {
          alert("Erro no Push = " + e.message);
          console.log(data.registrationId);
      });

Logs taken while reproducing problem
Independente do senderID utiizado:
e1oKttKUBt0:APA91bHRakixY1aAEVt9Wsy3lHoPFQCFnEFhStq8heV10FvRvpKdpynpiSEW5L6lNf0BVkZ3BwoQKbWrLQeRGj8QT3NbseH6CshymhZ9yKTvFBsbRJPLY97dleBq_AowC9EMGz7RSj-I

I'll translate inline for him, as he contacted me for help personally.

I was able to solve it, I was using version 2.1.2, for some reason it was not working properly with Android, so I had to downgrade to version 1.8.0, so it worked perfectly.
Fred, thank you for helping me!

If plugin version 2.1.2 is broken with android, then I think we should not close the issue.

I agree with @satish-nikam . If you can reproduce the issue with 2.1.2 and cannot on 1.8.0, then it's an improvement to the debugging and investigation process, but it doesn't mean the issue is solved at all.

@amexassessoria without a push payload you are sending or logs that show the problem we can't provide much help other than random guesses so more info is needed on this one.

Good  day i have the same it does register the device but when i send the push i dont receive the notification
here  is my spinet initPushNotification() {
if (!this.platform.is('cordova')) {
console.warn('Push notifications not initialized. Cordova is not available - Run in physical device');
return;
}
const options: PushOptions = {
android: {
senderID: 'xxxxxxxxx'
},
ios: {
alert: 'true',
badge: false,
sound: 'true'
},
};
const pushObject: PushObject = this.push.init(options);
pushObject.on('registration').subscribe((data: any) => {
  console.log('device token -> ' + data.registrationId);
  //TODO - send device token to server
});

pushObject.on('notification').subscribe((data: any) => {
  console.log('message -> ' + data.message);
  //if user using app and push notification comes
  if (data.additionalData.foreground) {
    // if application open, show popup
    let confirmAlert = this.alertCtrl.create({
      title: 'New Notification',
      message: data.message,
      buttons: [{
        text: 'Ignore',
        role: 'cancel'
      }, {
        text: 'View',
        handler: () => {
          //TODO: Your logic here
          this.nav.push(DetailsPage, { message: data.message });
        }
      }]
    });
    confirmAlert.present();
  } else {
    //if user NOT using app and push notification comes
    //TODO: Your logic on click of push notification directly
    this.nav.push(DetailsPage, { message: data.message });
    console.log('Push notification clicked');
  }
});

pushObject.on('error').subscribe(error => console.error('Error with Push plugin' + error));

}
}
___________________________________________________+++++++++++++++++++++++++++++++++++++++
my details
cli packages: (/usr/lib/node_modules)
@ionic/cli-utils  : 1.19.2
ionic (Ionic CLI) : 3.20.0

global packages:
cordova (Cordova CLI) : 8.0.0

local packages:
@ionic/app-scripts : 1.3.12
Cordova Platforms  : android 6.4.0
Ionic Framework    : ionic-angular 3.5.0

System:
Android SDK Tools : 26.1.1
Node              : v9.4.0
npm               : 5.6.0
OS                : Linux 4.10

Environment Variables:
ANDROID_HOME : /home/leewayne/Android/Sdk

Misc:
backend : pro

my conslole log message device token -> fP9d1bGzlDg:APA91bHNs42moFtXtsV0r6bhBbXrfil7nEzhoM-

yes i do get the token

but when i send the message via firebase my android device doesn't recieve the message .

when i try to to this i dont get the message on my device

I'm closing this issue as the original reporter's issue was resolved. There was a lot of other folks chiming in but I have a feeling they are running into the data vs notification problem because of sending from the Firebase Console.

@macdonst , I am facing the same issue and i am not sending from the firebase console but from my app. I follow the link you put about the data vs notification problem, and i am doing thing well.
ionic info prints the following:
``
@ionic/cli-utils  : 1.19.2
ionic (Ionic CLI) : 3.20.0
global packages:
cordova (Cordova CLI) : 8.0.0

local packages:
@ionic/app-scripts : 3.1.8
Cordova Platforms  : android 6.4.0
Ionic Framework    : ionic-angular 3.9.2

System:
Android SDK Tools : 25.2.5
Node              : v8.9.3
npm               : 5.5.1
OS                : Windows 10

``

I have the same problem,
I implemented push notification using two methods:   1) Push plugin  and 2) FCM Plugin
With these methods I am able to get the device registration ID, but when I send the push notification from Firebase or even from AWS-SNS, I am not receiving and notification to my device.
I even tried creating a new projects and implement in that, but still the same problem.
In recent updates i am facing this issue, 4 months before it was working well.
cli packages:
@ionic/cli-utils  : 1.19.2
ionic (Ionic CLI) : 3.20.0
global packages:
cordova (Cordova CLI) : 8.0.0
local packages:
@ionic/app-scripts : 3.1.9
Cordova Platforms  : android 7.1.0
Ionic Framework    : ionic-angular 3.9.2
System:
Android SDK Tools : 26.1.1
Node              : v8.9.3
npm               : 5.5.1
OS                : Windows 10
It would be a great support if someone has a solution for this.


feat: add extension URIs

This is a first cut at properly supporting substrait extensions.
According to https://substrait.io/extensions/#function-signature-compound-names, the function signature should be of the form <function name>:<short_arg_type0>_<short_arg_type1>_..._<short_arg_typeN>
Further, we are expected to say which of the extension yaml files to refer to when we create a new extensionUri
Towards that, this PR does a few things:

vendors in the substrait extension yaml files so we can generate a dictionary of accepted signatures
Updates how we generate extension URIs
Adds in a lookup step to the function_id generation to use the correct extension function signature

TODO:

The assumption that substrait makes is that producers will handle any required casting before serialization -- currently if we did something like 1 - lineitem.l_discount Ibis will infer the type of the literal 1 as an int8.  l_discount is a decimal, so substrait wants us to cast the 1 to a decimal before serialization.

Also, there's a bunch of gross yaml munging in here that could be a lot nicer, but it works for now.

superceded by #510


Simple mutation throw error "Can't wait without a fiber"

RootQuery :{
  ...
// works well
    async oneFeedback(root, {feedbackId}, context) {
      const feedback = DB.Feedback.findOne({_id: feedbackId})
      return await feedback
    },
}

// mutate nothing but just for test , will throw an error
RootMutation: {
    async changeFeedbackText(root, {feedbackId, text}, context) {
      const feedback = DB.Feedback.findOne({_id: feedbackId})
      return await feedback
    }
// so does this one
   async changeFeedbackText(root, {feedbackId, text}, context) {
      DB.Feedback.update(feedbackId, {$set:{text: text}})
      return DB.Feedback.findOne(feedbackId)
    }
  }

Why same code in query don't throw an error?

on localhost:3000/graphql:
mutation {
  changeFeedbackText(feedbackId:"3LyTkSYqkFuFPvgT7", text:"test") {
    _id
  }
}

results:
{
  "data": {
    "changeFeedbackText": null
  },
  "errors": [
    {
      "message": "Can't wait without a fiber",
      "locations": [
        {
          "line": 2,
          "column": 3
        }
      ]
    }
  ]
}

@wuzhuzhu This seems to be an issue that's specific to Meteor which has nothing to do with Apollo Server. Can you open an issue on themeteor-integration repository instead?

sure. close.


Metaweblog API support

To provide a "Windows Live Writer" like experience, DownmarkerWPF should implement the Metaweblog API support so it can post to markdown based blog systems like FunnelWeb.

I think we can mark this one off.


#138 center text

yourfirstpr.github.io

Thank you so much for opening a pull request! :smiley:
Please provide the following information where possible to help the pull request reviewer merge your PR quicker!
Relevant Project Issue Numbers :hash:
Add any related issue numbers from the GitHub project. Append the # symbol before issue numbers.
#138
Involved Project Members :bust_in_silhouette:
Tag any GitHub usernames involved or directly responsible for reviewing the proposed changes. Append the @ symbol before usernames.
@jperl08
An Explanation of Your Changes :speech_balloon:
add style to p in footer
Any Screenshots of Your Changes :camera:
Your screenshots go here! Use Markdown Syntax to embed images.

sent #pr to merge


Version Issue?

Actual Result
init.js:34 Uncaught Error: deck.gl - multiple versions detected: 5.2.5 vs 5.3.0-rc.2
    at eval (init.js:34)
    at Module../node_modules/<EMAIL_ADDRESS>(app.js:3143)
    at __webpack_require__ (app.js:712)
    at fn (app.js:95)
    at eval (index.js:3)
    at Module../node_modules/<EMAIL_ADDRESS>(app.js:3035)
    at __webpack_require__ (app.js:712)
    at fn (app.js:95)
    at eval (arc-layer.js:3)
    at<EMAIL_ADDRESS>(app.js:2315)
(anonymous) @ init.js:34
./node_modules/<EMAIL_ADDRESS>@ app.js:3143
__webpack_require__ @ app.js:712
fn @ app.js:95
(anonymous) @ index.js:3
./node_modules/<EMAIL_ADDRESS>@ app.js:3035
__webpack_require__ @ app.js:712
fn @ app.js:95
(anonymous) @ arc-layer.js:3
<EMAIL_ADDRESS>@ app.js:2315
__webpack_require__ @ app.js:712
fn @ app.js:95
(anonymous) @ index.js:2
<EMAIL_ADDRESS>@ app.js:2507
__webpack_require__ @ app.js:712
fn @ app.js:95
(anonymous) @ app.js:4
./app.js @ app.js:792
__webpack_require__ @ app.js:712
fn @ app.js:95
(anonymous) @ client:3
0 @ app.js:8096
__webpack_require__ @ app.js:712
(anonymous) @ app.js:779
(anonymous) @ app.js:782

Expected Result

The example to work

Reproduce Steps

clone the repo
navigate to the examples/get-started/pure-js-without-map or examples/get-started/pure-js
run npm install
run npm run dev
open browser console window.

To Do List

[ ] Add label and assign to milestone
[ ] Coding
[ ] Test

Background
To Do List

[ ] Add label and assign to milestone
[ ] Coding
[ ] Doc update
[ ] Whats new update
[ ] Test

This was just a matter of the two deck.gl packages in package.json not having the same version. Fixed on master, but you can easily fix it yourself in your local code.


Update README file with Local Development Instructions

Description
User Story: As a developer, I would like to know how to run the docker image locally and how to propagate my changes to the Docker image.
Currently, MotorEase does not have information in the README on how to run the docker image locally with which it propagates local changes to the Docker container.
Ranking and Reasoning:
This is ranked 1st because we found that this feature would be the most beneficial. This is because it would provide engineers an easier way to make changes to the local directory and it will allow their changes to be propagated to the docker container. Before engineers, are fetching the image from the remote and run that image. But now engineers can run the local copies. Also, the ranking of our issues focuses on errors > usability/functionality > UI. In this case, my group and I found this issue to be the most beneficial.
Dependencies
N/A
Ideas for Fix
Edit the README file to include all the steps on how to run the image locally.
Timeline
Engineering Points/Effort: 0.25 points of the 4
Acceptance Criteria.

My group mates are able to understand the instructions and reproduce the results.

I deducted the engineering points for this issue because I found that I could group this with another issue #18 as they deal will the same file.


MJ-72 Added progress bar and repetition button

Currently repetition counter and progress bar are updating after refreshing page, but I think there will be some comments to fix here and we could talk later about this issue, whats the best solution :)


Feature Request: Add a command to copy latest commit hash to clipboard

I frequently have to reference commit hashs in my project tracker, instead of opening the log, clicking the top commit and coping the hash, this package could have that as a command :)

This is a very very niche command. I'm trying to stay away from commands like this because I want the package to have basic, frequently used commands


Changed base files and architecture of users module

This pull request introduces several new features and improvements to the XpenseMeter project, including the addition of user authentication, database models, and API endpoints. The most important changes are summarized below:
API Enhancements:

Added a new api_router in XpenseMeter/api/__init__.py to include user-related routes and a health check endpoint.
Created user endpoints for reading users, signing up, and signing in with authentication in XpenseMeter/api/endpoints/user.py.

Database Models:

Defined new database models for User, Expense, Category, and Budget in XpenseMeter/db/models/. [1] [2] [3] [4]
Initialized database and created tables in XpenseMeter/db/__init__.py and XpenseMeter/db/base.py. [1] [2]

Security and Authentication:

Implemented JWT-based authentication methods in XpenseMeter/core/security.py, including token creation and verification.
Added a decorator for token authentication in XpenseMeter/decorators/jwt.py to protect API routes.

Configuration:

Added a Settings class in XpenseMeter/core/config.py to manage environment variables and configuration settings.

CRUD Operations:

Implemented CRUD operations for user management in XpenseMeter/crud/user.py.


Added GLM.lookAt method

I haven't edited the docs or anything, only added the Mat4 lookAt method.

Awesome, thanks so much!


API breaks when using apple-mobile-web-app-view-enabled

Reference this issue.
When my app is saved to the home screen on an iOS device, the Mobile Web App view that is used to display saved apps does not allow for cross-referencing scripts/redirects.
It appears that the gAPI client is setting then trying to access sessionStorage, which is not supported in the headless Safari browser for Mobile Web App views.

@geoffdavis92 we have made some updates in gapi.auth2 recently that may have fixed your problem. Could you try again?

@geoffdavis92 please try again to make sure our fix addressed your issue. Thanks!

Closing the issue, please follow up with more details if you are still experiencing the issue.


path converter doesn't redirect to trailing slash

It seems to me that the automatic redirect for URLs with trailing shlashes (like /user → /user/) described in Flask docs and Werkzeug docs does not work if you use PathConverter in an URL definition.
I have this straightforward Flask application to reproduce the problem:
from flask import Flask, Response

app = Flask(__name__)

@app.route('/')
@app.route('/<path:username>/')
def main(username=None):
    return Response(f"It works! Hello, {username}")

In werkzeug 2.1.2, it works as expected and if you send a request to /user, it redirects you via HTTP/308 to /user/. The log is:
* Running on http://<IP_ADDRESS>:5000 (Press CTRL+C to quit)
<IP_ADDRESS> - - [12/Oct/2022 14:47:37] "GET / HTTP/1.1" 200 -
<IP_ADDRESS> - - [12/Oct/2022 14:47:45] "GET /user HTTP/1.1" 308 -
<IP_ADDRESS> - - [12/Oct/2022 14:47:45] "GET /user/ HTTP/1.1" 200 -

But when I use werkzeug 2.2.0, the same request gives me HTTP/404:
 * Running on http://<IP_ADDRESS>:5000 (Press CTRL+C to quit)
<IP_ADDRESS> - - [12/Oct/2022 14:48:43] "GET /fooo HTTP/1.1" 404 -

I've tried a bisection of all the commits between those versions to see whether this was an intentional change or not and find that the difference has been introduced in: https://github.com/pallets/werkzeug/commit/5a7c0dec029d296a5e8131c8db51ce19e28c0c58
The workaround for this is to define both possible URLs for a single endpoint but it's not pretty. Also, the difference might cause problems if you still support Python 3.6 because pip installs older Flask and werkzeug for Python 3.6 where the redirect works fine and newer packages for Python 3.7+ where it does not.
Is this behavior intentional and if so, could you please add it to the documentation?

Thanks for the quick response but even with the latest version 2.2.2 together with Flask 2.2.2, the problem is still the same. Could you please reopen this issue?

Is it possible that the mentioned fix fixes only the RegexConverter but not the PathConverter where slashes are also allowed?

@pgjones looks like the path converter swallows the trailing slash before matching finishes?

I think is is that the match isn't possible without a trailing slash (it isn't considered optional for a final part). I'll look into this.


[Suggestion] Become Nest Compatible

Nest is a specification for Swift web-servers to allow them to be  interchangeable between different frameworks. Here's the specification itself.
Making Taylor support Nest is a challenge but it would make the code easier to work with in the long run. Obviously Taylor would be quite a few layers above the base Nest specification, but the Nest-compatible methods should still be accessible so that other frameworks built on top of Taylor can access them internally.
Nest's creator (kylef) noted:

I'd imagine that Taylor would be split into two components itself. The underlying server would just offer the Nest interface. The other part would be a micro framework that utilises the Nest compatible interface and provides the interface that Taylor provides.

The most difficult part of implementing the specification would be the fact that the main application function returns the response object synchronously, with no callback involved.
We've discussed the callback system before in issue #12, but didn't really get anywhere. I've been searching for alternatives to how the current system is implemented for a while now, and I've come up with a couple viable ideas which would allow us to be Nest-compatible:

Use semaphores (example) internally, creating a new thread for each request handler & blocking it until the callback has been executed.
Switch to a synchronous handler (as suggested here):

 typealias Handler = (Request, Response) -> (Request, Response)

Tell me what you think! Personally I think the ideas behind Nest are really neat and it would allow frameworks to be built around multiple servers instead of binding to a single one internally - which opens up a huge window of possibilities.

Now that we made Taylor synchronous, this discussion should be revived (started?).


support ctrl+z stop process

In interactive dua i, Ctrl+Z doesn't work.  It does nothing.  If I stop the process using kill -STOP <pid> on a separate terminal, it does stop.  If I fg it on that terminal, it starts again, but the graphical interface is not there.  Whatever I type seems to have no affect, and the text I type just shows.  It even doesn't recognize Ctrl+C (in most cases).
Ideally, I would like Ctrl+Z to stop the process like many other programs.

Thanks for letting me know!
I have had a preliminary look and here are my findings.

dua uses tui, which exhibits the behaviour described here both for the termion and crossterm backends. All the following findings have been run with cargo run --example termion_demo -- --tick-rate 200.
I understand why the application doesn't respond to Ctrl+Z, which is due to the terminal being in raw mode, thus key presses don't show and are entirely handled by the application. Otherwise interrupts are generated by the owning shell which would see Ctrl+Z before the application does.
After stopping the process with kill -STOP, the terminal remains in raw mode. I am able to continue it with kill -CONTor fg in the shell and it does display, even though that will leave the user with control over the terminal to some extend. As such, the application will not respond to any input, even though input will not display in the terminal either as it is still in raw mode. However, now Ctrl+C or Ctrl+Z now work as they are effectively intercepted and translated into signals by the owning shell. I did not find a way to restore input to the application.

Knowing how obtaining input works, I do wonder what else has to happen to make this work. I have a feeling it's something the application has to be aware of, and possibly rebind standard input somehow.
When trying the above with dua, continuing it would not display anything. That is expected, as it only redraws when it receives user input, which we know can't be obtained anymore. However, now one can kill it with Ctrl+C, leaving the terminal in a dirty state as destructors didn't run.
Next I will continue checking what happens when doing this in termion and crossterm respectively.

I think I know what happens. After interruption, the input thread crashes and for some reason doesn't bring down the program with it (which it really should at least). Thus it leaves the application unresponsive.
That should easily be fixable, let me see….

Even though it's trivial to ignore interrupts, it appears that's not actually happening in case of dua. Previously the input thread would gracefully shutdown, and leave the main loop input loop with a closed channel which should unblock and stop naturally.
Further diving revealed that applications do indeed have to implement support for that themselves

A deep dive into the SIGTTIN/SIGTTOU…

This is not it…

Job Control Signals

Interesting, but once again not what's happening here

As of now, I am none the wiser though on how to fix that, and the question remains why connectivity to the terminal is lost entirely.
Ok, here it comes: The terminal is loosing it's RAW mode, which is why now one can actually see all input. Thus pressing enter dispatches all input to the application, which will happily draw then as well.
Thus the solution should be to set a handler for SIGCONT and set the terminal back into raw mode.

Any thoughts on this would be appreciated - it puzzles me that this is not done automatically. It appears like tig deals with this specifically thanks to using curses as backend.
Putting this to the test, if I run cargo run --example curses_demo --no-default-features --features="curses" -- --tick-rate 200 in the tui-rs repository, stopping it via separate signal actually leaves the terminal in a decent state, and fg brings back the application in raw mode. Thus curses must have been installing enough signal handlers to make that happen.
As dua uses tui, it would be possible to compile it against curses, a backend supported by tui.
It seems like ideally, this kind of functionality would be provided by the termion and crossterm backends respectively, ideally by a callback to separately install certain signal handlers to save and restore terminal attributes at the right time.
I will sleep on that and see if support for that can be implemented in termion or crossterm respectively to match curses capabilities.

This article for the first time in my life explains how all this is actually working. Very interesting, even after only having read the first 10% or so.
From what I could gather, the shell as session leader should be the one to restore the previous terminal attributes (which includes raw mode) shortly before it puts an application into the foreground. This, however, doesn't seem to happen, and curses handling this specifically (at least so it seems) might be a good example for this being some sort of special case nonetheless.

Thanks for all the effort you put into this!  That article was helpful for me, too.  I read up to

But since the editor is now a background job, the TTY device will not allow it.

then tested it out on vim and got the same result.  If I kill -STOP <pid> on vim rather than using Ctrl+Z, I get in a bad state after fg.  A minor difference is that resizing the screen (which should send SIGWINCH) causes it to be redrawn, but the text input seems to have no affect to the editor.
Then, I think that kill -STOP <pid> is not something to worry about and, instead, it's about handling Ctrl+Z + fg.

I could just reproduce this behaviour with the tui curses backend, too. This probably means the following:

before changing the terminal after application startup, store the current terminal settings as previous terminal settings.
register a signal handler for SIGTSTP
upon receiving the signal, store the current terminal settings, set the previous terminal settings, register a signal handler for CONT (probably deregister SIGTSTP) and send yourself the STOP signal.

Now the user should be able to interact with a pristine terminal.
Once CONT is received, the application restores the previously current terminal settings and uninstalls the CONT signal handler and potentially reinstalls the SIGTSTP handler to get ready for the next background request.
If the application wanted to, it could always install a CONT handler to be able to always restore the correct terminal settings, even in case of STOP having been received earlier.
Now is the question how to handle it. My first intuition is to put that into crosstermion at first as PoC and see if that can trickle down into the actual backends, namely crossterm and termion.

Additionally, I have created an issue over at termion, but given the usual cadence related to issues and merge requests, I don't expect much interaction to come from there.

I want to implement this for helix editor as well https://github.com/helix-editor/helix but seemed like we need to use low-level library for this directly using signal-hook.


Import QR scanned data

I think it would be convenient for the camera app QR scanner to have the option to detect/import certain formats. For example, a QR formatted as .vcf could show the option to add to contacts.

Yeah - related, I just tried scanning a QR code for a wifi network, and was hoping for this to happen. (Most phones these days prompt you to join the network when you scan a QR code like that.)

That feature is supported through the Wi-Fi add network QR scanner.

Ah, that's good to know. Would still be convenient if the camera's QR code scanner could detect special formats like this though and send you to the right place automatically.

see #389


WinError 10048: Only one usage of each socket address is normally permitted

I'm trying to use imexam in Jupyter notebook on Windows 10, and on trying to connect to ginga I get a strange socket error:
OSError                                   Traceback (most recent call last)
<ipython-input-2-8bfff7002bf2> in <module>
      2 #os.environ['XPA_METHOD'] = "inet"
      3
----> 4 viewer = imexam.connect(viewer='ginga')
      5 viewer.load_fits('example_data/PAL5_3p6um.fits')

~\anaconda3\lib\site-packages\imexam\connect.py in __init__(self, target, path, viewer, wait_time, quit_window, port)
     98
     99         elif 'ginga' in self._viewer:
--> 100             self.window = ginga(exam=self.exam,
    101                                 close_on_del=quit_window,
    102                                 port=port)

~\anaconda3\lib\site-packages\imexam\ginga_viewer.py in __init__(self, exam, close_on_del, logger, port, host, use_opencv)
    926         self._port = port
    927
--> 928         super(ginga, self).__init__(exam=exam, close_on_del=close_on_del,
    929                                     logger=logger, port=self._port)
    930

~\anaconda3\lib\site-packages\imexam\ginga_viewer.py in __init__(self, exam, close_on_del, logger, port)
    143
    144         # create the viewer specific to this backend
--> 145         self._create_viewer(bind_prefs, viewer_prefs)
    146
    147         # TODO: at some point, it might be better to simply add a custom

~\anaconda3\lib\site-packages\imexam\ginga_viewer.py in _create_viewer(self, bind_prefs, viewer_prefs, opencv, threads)
    950         self._threads = threads
    951         self._server = None
--> 952         self._start_server()
    953
    954         self.ginga_view = self._server.get_viewer('Imexam Display')

~\anaconda3\lib\site-packages\imexam\ginga_viewer.py in _start_server(self)
    997             no_ioloop = True  # jupyter console and notebook
    998
--> 999         self._server.start(no_ioloop=no_ioloop)
   1000
   1001     def _shutdown(self):

~\anaconda3\lib\site-packages\ginga\web\pgw\ipg.py in start(self, use_thread, no_ioloop)
    423         ], factory=self.factory, logger=self.logger)
    424
--> 425         self.http_server = self.server.listen(self.port, self.host)
    426
    427         if no_ioloop:

~\anaconda3\lib\site-packages\tornado\web.py in listen(self, port, address, **kwargs)
   2114         """
   2115         server = HTTPServer(self, **kwargs)
-> 2116         server.listen(port, address)
   2117         return server
   2118

~\anaconda3\lib\site-packages\tornado\tcpserver.py in listen(self, port, address)
    149         the `.IOLoop`.
    150         """
--> 151         sockets = bind_sockets(port, address=address)
    152         self.add_sockets(sockets)
    153

~\anaconda3\lib\site-packages\tornado\netutil.py in bind_sockets(port, address, family, backlog, flags, reuse_port)
    172
    173         sock.setblocking(False)
--> 174         sock.bind(sockaddr)
    175         bound_port = sock.getsockname()[1]
    176         sock.listen(backlog)

OSError: [WinError 10048] Only one usage of each socket address (protocol/network address/port) is normally permitted

This is the code I'm trying to run:
viewer = imexam.connect(viewer='ginga')
viewer.load_fits('example_data/PAL5_3p6um.fits')

I've verified that both imexam and ginga are up to date, and I've tried the common problem fixes listed in the documentation, but no dice. Another user also on Windows 10 posted a similar-looking issue a couple of years ago (#151); could this be a Windows 10 specific issue? Thanks!

Apologies, I hadn't seen the 'port' option in connect() as given in the readme, which fixed my issue in the end. I don't think this is mentioned anywhere on the readthedocs though, maybe it could be useful to mention it on there too?

no worries -the best bug report is the one someone figures out the solution to themselves!  I'm glad it's working for you. I'll definitely look through the docs and make sure things like this are easy to find -the docs are in need of another overhaul anyways.
many thanks!


Fix dead link

@nfd9001 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@rothja : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@nfd9001 Thank you for this fix. I changed the link slightly to point to a subdirectory, but this was definitely a necessary change. Thanks! #sign-off

@rothja: I'm sorry - only the author of this article, @mihaelablendea, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


Edit Documentation Telling Devs To Turn Off Docker's "Experimental Features"

This error message is all I kept getting when running the following command:
Command => docker-compose -f docker-compose.yml -f docker-compose.override.yml up -d
Error Message => “Error response from daemon: Get https://registry-1.docker.io/v2/: 3 net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
THE FIX
Docker Dashboard -> Settings -> Experimental -> Uncheck "Use New Experimental Framework".

See link: FIX from Referenced Article found on forums.docker.com

Thanks for sharing, I will add this into readme file.


[Tooltip] tooltips are shown for disabled buttons but documentation says it shouldn't happen

Documentation
The documentation of tooltip has this section https://www.radix-ui.com/docs/primitives/components/tooltip#displaying-a-tooltip-from-a-disabled-button which suggests us that some extra actions should be made to display tooltips for disabled buttons.
As we can see in this sandbox this is not true and tooltips are shown for disabled buttons by default.
The issue is a follow-up to the discussion in discord @benoitgrelard found the PR #1358 that caused the change in behaviour
It will be good to update the documentation to reflect those changes
Relevant Radix Component(s)
https://www.radix-ui.com/docs/primitives/components/tooltip

https://github.com/radix-ui/website/pull/714

The sandbox example throws an error for me
Path must be a string. Received null
I tried adding a Tooltip with a Button as a direct descendant myself and the Tooltip did not show for me.
Following the instructions in the official docs worked for me
https://www.radix-ui.com/primitives/docs/components/tooltip#displaying-a-tooltip-from-a-disabled-button

fixed the sandbox

I did some testing

your sandbox example works only with the default button
but does not work with Button provided by https://ui.shadcn.com/docs/components/button

Since I do not want to replicate the styling I'l keep the Version from the docs for now.
So I guess the docs are still helpful / needed.

Closed via https://github.com/radix-ui/website/pull/714

Hey folks, it seems like Tooltip does now respect the disabled attr of the trigger
Anyone else seeing the same?

Hey folks, it seems like Tooltip does now respect the disabled attr of the trigger Anyone else seeing the same?

maybe you have pointer-events: none when disabled is true

Hey folks, it seems like Tooltip does now respect the disabled attr of the trigger Anyone else seeing the same?

maybe you have pointer-events: none when disabled is true

Indeed, setting pointer-events: auto !important (!pointer-events-auto in Tailwind) allows to show the tooltip even when disabled is true


Adds command listitem attachment add

Closes #5219

Thank you @MathijsVerbeeck we'll try to review it ASAP!


[AMBARI-24160] Inaccurate error message showed during service removal in some circumstances (dgrinenko)

What changes were proposed in this pull request?
Fix for displaying proper component state in error message, some refactoring
How was this patch tested?
Cluster + existing UT, as no logic were changed

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/2822/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/2821/
Test PASSed.


Release build is vastly (x10) slower than debug one with a little nuance

Stating a problem
I faced the following problem:
First of all, i ask to read till the end, thank you.
So i found that there are 4 ways to build apk

flutter run (builds debug version)
flutter run --release (only on real device)
flutter build apk --debug
flutter build apk (builds release version, signed or not signed, does not matter)

First two options (1, 2) is not the true way to build it, but I still want to take them into consideration.
I build a small app that could reproduce the problem i encountered.
Just a simple one-button GUI (main.dart) that triggers some "scrypt" key-derivation function implementation (scrypt.dart file in the repository). When scrypt function finishes it's work, the ellapsed time will be shown upon a button.
Some of the results according to the 4 ways i mentioned above:

~ 2.5 seconds to complete (on emulator via adb, on real device via adb, on real device)
~ 2.5 seconds to complete (on real device via adb, on real device)
~ 2.5 seconds (on real device)
~ 12.7 seconds (on real device)

So the fourth option is about 10 times slower that other ones. This confuses me, espesially paying attension that it took just 2.5 seconds on the 2nd option (and that is a nuance i was talking about)
I gave this project to several people, who reported the same issue.
I have a small suspicion that may be this could be connected with Uint32List implementation that i'm currently using in scrypt.dart, but not sure at all
Steps to Reproduce
clone https://github.com/stellarbear/scrypt_performance_test
Logs
I can't (or do not know how) to create logs for release version that is gonna be run directly on real device

`[√] Flutter (Channel stable, v1.2.1, on Microsoft Windows [Version 10.0.17134.706], locale en-US)
• Flutter version 1.2.1 at D:\Program Files\flutter
• Framework revision 8661d8aecd (10 weeks ago), 2019-02-14 19:19:53 -0800
• Engine revision 3757390fa4
• Dart version 2.1.2 (build 2.1.2-dev.0.0 0a7dcf17eb)
[!] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
• Android SDK at C:\Users\root\AppData\Local\Android\Sdk
• Android NDK location not configured (optional; useful for native profiling support)
• Platform android-28, build-tools 28.0.3
• ANDROID_HOME = C:\Users\root\AppData\Local\Android\Sdk
• Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
• Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1136-b06)
! Some Android licenses not accepted.  To resolve this, run: flutter doctor --android-licenses
[√] Android Studio (version 3.2)
• Android Studio at C:\Program Files\Android\Android Studio
• Flutter plugin version 31.1.1
• Dart plugin version 181.5656
• Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1136-b06)
[√] Connected device (1 available)
• Android SDK built for x86 • emulator-5554 • android-x86 • Android 8.1.0 (API 27) (emulator)
! Doctor found issues in 1 category.`

Hi,
I tried your example in dartpad and  got this result

executed in 0:00:00.524639
I think the only diff is the dartpad uses dart sdk 2.2.0

Can you try to use this version and see if is any better? :)

Try using flutter build apk --target-platform=android-arm64
flutter run will build an APK targeting the attached device.  So if the device is 64-bit, then flutter run will build a 64-bit APK.
flutter build apk will build a 32-bit APK by default.  If you want a 64-bit APK then you'll need to specify that as the target.

Try using flutter build apk --target-platform=android-arm64
flutter run will build an APK targeting the attached device. So if the device is 64-bit, then flutter run will build a 64-bit APK.
flutter build apk will build a 32-bit APK by default. If you want a 64-bit APK then you'll need to specify that as the target.

that makes sence. but is there any way i can debug that slow (i suppose x86) version on emulator?
i made some old phone spec virtual devices, but everything still runs smoothly (~2.5 sec)

Hi,
I tried your example in dartpad and got this result

executed in 0:00:00.524639
I think the only diff is the dartpad uses dart sdk 2.2.0

Can you try to use this version and see if is any better? :)

switched to dev flutter branch, no changes

After some research i found that i can attach to slow version with the following command:
flutter run --release --target-platform=android-arm
And the slowest part of the code is blockXOR function
dst[di++] ^= src[si++];

I was wrong about XOR, cannot reproduce it outside "scrypt" function. But still stuck in "salsaXOR" function - this is the pleace where release mode is vastly slower than debug

The issue is already long time not active and without answer.
Could everyone who still has this problem please file a new issue with the exact descriptions what happens, logs and the output of flutter doctor -v please.


Don't generate empty build phases

🎉

It seems this is causing issues. A framework with no Compile Sources phase is not linking properly

I am experiencing the same issue with a application.watchapp2 target, where the application.watchapp2 target has no sources, but a Compile Sources (0) build phase is created that results in a Multiple commands produce build time error.
  Watch:
    platform: watchOS
    type: application.watchapp2
    sources:
      - path: Watch
        includes:
          - "Assets.xcassets"
          - "Icon.xcassets"
          - "Interface.storyboard"
        buildPhase: resources
    dependencies:
      - target: WatchExtension

I did not find any workaround yet


Update getting_started_with_your_microsoft_windows_device.md

Update for phase 2
Changes proposed in this pull request
Guidance to review

Closing in favour of #192.


updating on Windows10 fails with message

I have ibmcloud C:\Program Files\IBM\Cloud\bin\ibmcloud.exe version 1.4.0+4705d79-2021-02-24T21:18:06+00:00
Try to update it to 1.5.0 in different ways (from cli, from download) and both fail with message:
A later version of "IBM Cloud Command Line Interface" is already installed on this machine. the setup cannot continue.
Very strange!

Uninstalling the old version solved the problem.


Malwarebytes blocked the program!

Regards, i'm contacting to MalwareBytes support to inform about this 'False Positive' case, feel free to support the ticket. https://forums.malwarebytes.com/topic/263502-swap-opensource-false-posotive/

Thx!

De: David B<EMAIL_ADDRESS>Enviado: jueves, 3 de septiembre de 2020 13:11
Para: dabeloper/swap<EMAIL_ADDRESS>Cc: Emilio<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Asunto: Re: [dabeloper/swap] Malwarebytes blocked the program! (#1)
Regards, i'm contacting to MalwareBytes support to inform about this 'False Positive' case, feel free to support the ticket. https://forums.malwarebytes.com/topic/263502-swap-opensource-false-posotive/
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/dabeloper/swap/issues/1#issuecomment-686598263, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADFZ4NCJXU65PN3QWSOO6T3SD653TANCNFSM4QSRRXMQ.


[BUG] Failed to emerge sys-kernel/surface-sources-5.15.3

Describe the bug
I think I'm having a similar problem when I emerge --ask sys-kernel/surface-sources
I'm currently using surface-sources-5.13.13 and my device is surface book 2 (i7-8650u+GTX1060).
To Reproduce
emerge --ask sys-kernel/surface-sources
Expected behavior
 * ERROR: sys-kernel/surface-sources-5.15.3::linux-surface failed (prepare phase):
 *   patch -p1  failed with /tmp/portage/sys-kernel/surface-sources-5.15.3/files/5.15/0010-cameras.patch
 *
 * Call stack:
 *               ebuild.sh, line  127:  Called src_prepare
 *             environment, line 1812:  Called eapply '/tmp/portage/sys-kernel/surface-sources-5.15.3/files/5.15/0010-cameras.patch'
 *             environment, line  687:  Called _eapply_patch '/tmp/portage/sys-kernel/surface-sources-5.15.3/files/5.15/0010-cameras.patch'
 *             environment, line  625:  Called __helpers_die 'patch -p1  failed with /tmp/portage/sys-kernel/surface-sources-5.15.3/files/5.15/0010-cameras.patch'
 *   isolated-functions.sh, line  112:  Called die
 * The specific snippet of code:
 *   		die "$@"

Additional context
complete build log
 * Package:    sys-kernel/surface-sources-5.15.3
 * Repository: linux-surface
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux userland_GNU
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 *
 * surface-sources is *not* supported by the Gentoo Kernel Project in any way.
 * If you need support, please contact the overlay developers directly.
 * Do *not* open bugs in Gentoo's bugzilla unless you have issues with
 * the ebuilds. Thank you.
 *
 * Excluding Patch #5010_enable-additional-cpu-optimizations-for-gcc.patch ...
 [ ok ]
 * Excluding Patch #5010_enable-additional-cpu-optimizations-for-gcc-4.9.patch ...
 [ ok ]
 * Excluding Patch #5011_enable-cpu-optimizations-for-gcc8.patch ...
 [ ok ]
 * Excluding Patch #5012_enable-cpu-optimizations-for-gcc91.patch ...
 [ ok ]
 * Excluding Patch #5013_enable-cpu-optimizations-for-gcc10.patch ...
 [ ok ]
 * Excluding Patch #5010_enable-additional-cpu-optimizations-for-gcc.patch ...
 [ ok ]
 * Excluding Patch #5010_enable-additional-cpu-optimizations-for-gcc-4.9.patch ...
 [ ok ]
 * Excluding Patch #5011_enable-cpu-optimizations-for-gcc8.patch ...
 [ ok ]
 * Excluding Patch #5012_enable-cpu-optimizations-for-gcc91.patch ...
 [ ok ]
 * Excluding Patch #5013_enable-cpu-optimizations-for-gcc10.patch ...
 [ ok ]
 * Applying 1000_linux-5.15.1.patch (-p1) ...
 [ ok ]
 * Applying 1001_linux-5.15.2.patch (-p1) ...
 [ ok ]
 * Applying 1002_linux-5.15.3.patch (-p1) ...
 [ ok ]
 * Applying 1500_XATTR_USER_PREFIX.patch (-p1) ...
 [ ok ]
 * Applying 1510_fs-enable-link-security-restrictions-by-default.patch (-p1) ...
 [ ok ]
 * Applying 2000_BT-Check-key-sizes-only-if-Secure-Simple-Pairing-enabled.patch (-p1) ...
 [ ok ]
 * Applying 2900_tmp513-Fix-build-issue-by-selecting-CONFIG_REG.patch (-p1) ...
 [ ok ]
 * Applying 2920_sign-file-patch-for-libressl.patch (-p1) ...
 [ ok ]
 * Applying 3000_Support-printing-firmware-info.patch (-p1) ...
 [ ok ]
 * Applying 4567_distro-Gentoo-Kconfig.patch (-p1) ...
 [ ok ]
 * Applying 0001-surface3-oemb.patch ...
 [ ok ]
 * Applying 0002-mwifiex.patch ...
patching file drivers/net/wireless/marvell/mwifiex/pcie.c
patching file drivers/net/wireless/marvell/mwifiex/pcie_quirks.c
patching file drivers/net/wireless/marvell/mwifiex/pcie_quirks.h
patching file drivers/net/wireless/marvell/mwifiex/pcie_quirks.c
patching file drivers/net/wireless/marvell/mwifiex/pcie.c
patching file drivers/net/wireless/marvell/mwifiex/pcie_quirks.c
patching file drivers/net/wireless/marvell/mwifiex/pcie_quirks.h
patching file drivers/net/wireless/marvell/mwifiex/pcie.c
patching file drivers/net/wireless/marvell/mwifiex/pcie_quirks.c
patching file drivers/net/wireless/marvell/mwifiex/pcie_quirks.h
patching file drivers/bluetooth/btusb.c
Hunk #3 succeeded at 3815 (offset -4 lines).
patching file drivers/net/wireless/marvell/mwifiex/cfg80211.c
patching file drivers/net/wireless/marvell/mwifiex/pcie.c
patching file drivers/net/wireless/marvell/mwifiex/cfg80211.c
patching file drivers/net/wireless/marvell/mwifiex/cfg80211.c
patching file drivers/net/wireless/marvell/mwifiex/cfg80211.c
patching file drivers/net/wireless/marvell/mwifiex/cfg80211.c
patching file drivers/net/wireless/marvell/mwifiex/cfg80211.c
patching file drivers/net/wireless/marvell/mwifiex/cfg80211.c
patching file drivers/net/wireless/marvell/mwifiex/cmdevt.c
patching file drivers/net/wireless/marvell/mwifiex/main.c
patching file drivers/net/wireless/marvell/mwifiex/main.h
patching file drivers/net/wireless/marvell/mwifiex/sta_cmd.c
patching file drivers/net/wireless/marvell/mwifiex/main.c
patching file drivers/net/wireless/marvell/mwifiex/main.h
patching file drivers/net/wireless/marvell/mwifiex/sta_cmdresp.c
patching file drivers/net/wireless/marvell/mwifiex/cfg80211.c
patching file drivers/net/wireless/marvell/mwifiex/cfg80211.c
patching file drivers/net/wireless/marvell/mwifiex/11n.c
patching file drivers/net/wireless/marvell/mwifiex/sta_event.c
 [ ok ]
 * Applying 0003-ath10k.patch ...
 [ ok ]
 * Applying 0004-ipts.patch ...
 [ ok ]
 * Applying 0005-surface-sam.patch ...
patching file drivers/platform/surface/surface_aggregator_registry.c
patching file drivers/platform/surface/aggregator/bus.c
patching file drivers/platform/surface/aggregator/bus.h
patching file drivers/platform/surface/aggregator/core.c
patching file include/linux/surface_aggregator/device.h
patching file drivers/platform/surface/surface_aggregator_registry.c
patching file drivers/platform/surface/surface_aggregator_registry.c
patching file drivers/platform/surface/aggregator/bus.c
patching file include/linux/surface_aggregator/device.h
patching file Documentation/driver-api/surface_aggregator/client.rst
patching file drivers/platform/surface/aggregator/controller.c
patching file include/linux/surface_aggregator/controller.h
patching file include/linux/surface_aggregator/device.h
patching file drivers/platform/surface/surface_aggregator_registry.c
patching file drivers/power/supply/surface_charger.c
patching file drivers/power/supply/surface_battery.c
patching file drivers/hid/surface-hid/surface_hid_core.c
patching file include/linux/surface_aggregator/serial_hub.h
patching file drivers/platform/surface/surface_aggregator_registry.c
patching file drivers/platform/surface/surface_aggregator_registry.c
patching file MAINTAINERS
patching file drivers/platform/surface/Kconfig
patching file drivers/platform/surface/Makefile
patching file drivers/platform/surface/surface_kip_tablet_switch.c
patching file drivers/platform/surface/surface_aggregator_registry.c
 [ ok ]
 * Applying 0006-surface-sam-over-hid.patch ...
 [ ok ]
 * Applying 0007-surface-gpe.patch ...
 [ ok ]
 * Applying 0008-surface-button.patch ...
 [ ok ]
 * Applying 0009-surface-typecover.patch ...
 [ ok ]
 * Applying 0010-cameras.patch ...
patching file drivers/media/pci/intel/ipu3/ipu3-cio2-main.c
patching file MAINTAINERS
patching file drivers/media/i2c/Kconfig
patching file drivers/media/i2c/Makefile
patching file drivers/media/i2c/ov5693.c
patching file drivers/media/pci/intel/ipu3/cio2-bridge.c
patching file drivers/media/pci/intel/ipu3/cio2-bridge.h
patching file drivers/media/pci/intel/ipu3/cio2-bridge.c
patching file drivers/media/pci/intel/ipu3/cio2-bridge.h
patching file drivers/media/pci/intel/ipu3/cio2-bridge.h
patching file drivers/media/i2c/ov5693.c
patching file drivers/media/i2c/ov8865.c
patching file drivers/media/i2c/ov8865.c
patching file drivers/media/i2c/ov8865.c
patching file drivers/media/i2c/ov8865.c
patching file drivers/media/i2c/ov8865.c
patching file drivers/media/i2c/ov8865.c
patching file drivers/media/i2c/ov8865.c
patching file drivers/media/i2c/ov8865.c
patching file drivers/media/i2c/ov8865.c
patching file drivers/media/i2c/ov8865.c
patching file drivers/media/i2c/ov8865.c
patching file drivers/media/i2c/ov8865.c
patching file drivers/media/i2c/ov8865.c
patching file drivers/media/i2c/ov8865.c
patching file drivers/media/pci/intel/ipu3/cio2-bridge.c
patching file drivers/media/i2c/ov8865.c
patching file drivers/acpi/scan.c
patching file include/acpi/acpi_bus.h
patching file drivers/i2c/i2c-core-acpi.c
patching file include/linux/platform_data/tps68470.h
patching file drivers/regulator/Kconfig
patching file drivers/regulator/Makefile
patching file drivers/regulator/tps68470-regulator.c
patching file drivers/clk/Kconfig
patching file drivers/clk/Makefile
patching file drivers/clk/clk-tps68470.c
patching file include/linux/mfd/tps68470.h
patching file drivers/platform/x86/intel/int3472/intel_skl_int3472_tps68470.c
patching file drivers/platform/x86/intel/int3472/Makefile
patching file drivers/platform/x86/intel/int3472/clk_and_regulator.c (renamed from drivers/platform/x86/intel/int3472/intel_skl_int3472_clk_and_regulator.c)
patching file drivers/platform/x86/intel/int3472/common.c
patching file drivers/platform/x86/intel/int3472/common.h (renamed from drivers/platform/x86/intel/int3472/intel_skl_int3472_common.h)
patching file drivers/platform/x86/intel/int3472/discrete.c (renamed from drivers/platform/x86/intel/int3472/intel_skl_int3472_discrete.c)
patching file drivers/platform/x86/intel/int3472/tps68470.c (renamed from drivers/platform/x86/intel/int3472/intel_skl_int3472_tps68470.c)
Hunk #2 succeeded at 95 (offset -7 lines).
Hunk #3 succeeded at 135 (offset -7 lines).
patching file drivers/platform/x86/intel/int3472/common.c
can't find file to patch at input line 4668
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/platform/x86/intel/int3472/common.h b/drivers/platform/x86/intel/int3472/common.h
|index d14944ee8586..53270d19c73a 100644
|--- a/drivers/platform/x86/intel/int3472/common.h
|+++ b/drivers/platform/x86/intel/int3472/common.h
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 4682
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/platform/x86/intel/int3472/discrete.c b/drivers/platform/x86/intel/int3472/discrete.c
|index a19a1f5dbdd7..efd31a0c7a88 100644
|--- a/drivers/platform/x86/intel/int3472/discrete.c
|+++ b/drivers/platform/x86/intel/int3472/discrete.c
--------------------------
No file to patch.  Skipping patch.
2 out of 2 hunks ignored
can't find file to patch at input line 4740
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--
|2.34.1
|
|From c2c331a5b417f82997b886919e334957b98ff44a Mon Sep 17 00:00:00 2001
|From: Hans de Goede<EMAIL_ADDRESS>|Date: Sun, 10 Oct 2021 20:57:05 +0200
|Subject: [PATCH] platform/x86: int3472: Pass tps68470_clk_platform_data to the
| tps68470-regulator MFD-cell
|
|Pass tps68470_clk_platform_data to the tps68470-clk MFD-cell,
|so that sensors which use the TPS68470 can find their clock.
|
|Signed-off-by: Hans de Goede<EMAIL_ADDRESS>|Patchset: cameras
|---
| drivers/platform/x86/intel/int3472/tps68470.c | 33 ++++++++++++++-----
| 1 file changed, 25 insertions(+), 8 deletions(-)
|
|diff --git a/drivers/platform/x86/intel/int3472/tps68470.c b/drivers/platform/x86/intel/int3472/tps68470.c
|index b94cf66ab61f..78e34e7b6969 100644
|--- a/drivers/platform/x86/intel/int3472/tps68470.c
|+++ b/drivers/platform/x86/intel/int3472/tps68470.c
--------------------------
No file to patch.  Skipping patch.
4 out of 4 hunks ignored
patching file drivers/platform/x86/intel/int3472/Makefile
patching file drivers/platform/x86/intel/int3472/tps68470.c
Hunk #1 succeeded at 8 (offset -1 lines).
Hunk #2 FAILED at 101.
Hunk #3 FAILED at 129.
Hunk #4 FAILED at 137.
Hunk #5 FAILED at 144.
Hunk #6 succeeded at 137 (offset -24 lines).
4 out of 6 hunks FAILED -- saving rejects to file drivers/platform/x86/intel/int3472/tps68470.c.rej
patching file drivers/platform/x86/intel/int3472/tps68470.h
patching file drivers/platform/x86/intel/int3472/tps68470_board_data.c
patching file drivers/platform/x86/intel/int3472/discrete.c
Hunk #1 succeeded at 182 with fuzz 1 (offset -198 lines).
patching file drivers/platform/x86/intel/int3472/tps68470.c
Hunk #1 succeeded at 134 (offset -39 lines).
Hunk #2 succeeded at 173 (offset -39 lines).
patching file drivers/media/i2c/ov8865.c
patching file drivers/media/i2c/ov8865.c
patching file drivers/mfd/intel-lpss-pci.c
patching file drivers/mfd/intel-lpss.c
patching file drivers/mfd/intel-lpss.h
patching file drivers/platform/x86/intel/int3472/tps68470_board_data.c
 [ !! ]
 * ERROR: sys-kernel/surface-sources-5.15.3::linux-surface failed (prepare phase):
 *   patch -p1  failed with /tmp/portage/sys-kernel/surface-sources-5.15.3/files/5.15/0010-cameras.patch
 *
 * Call stack:
 *               ebuild.sh, line  127:  Called src_prepare
 *             environment, line 1812:  Called eapply '/tmp/portage/sys-kernel/surface-sources-5.15.3/files/5.15/0010-cameras.patch'
 *             environment, line  687:  Called _eapply_patch '/tmp/portage/sys-kernel/surface-sources-5.15.3/files/5.15/0010-cameras.patch'
 *             environment, line  625:  Called __helpers_die 'patch -p1  failed with /tmp/portage/sys-kernel/surface-sources-5.15.3/files/5.15/0010-cameras.patch'
 *   isolated-functions.sh, line  112:  Called die
 * The specific snippet of code:
 *   		die "$@"
 *
 * If you need support, post the output of `emerge --info '=sys-kernel/surface-sources-5.15.3::linux-surface'`,
 * the complete build log and the output of `emerge -pqv '=sys-kernel/surface-sources-5.15.3::linux-surface'`.
 * The complete build log is located at '/tmp/portage/sys-kernel/surface-sources-5.15.3/temp/build.log'.
 * The ebuild environment file is located at '/tmp/portage/sys-kernel/surface-sources-5.15.3/temp/environment'.
 * Working directory: '/tmp/portage/sys-kernel/surface-sources-5.15.3/work/linux-5.15.3-surface'
 * S: '/tmp/portage/sys-kernel/surface-sources-5.15.3/work/linux-5.15.3-surface'

I'm very sorry. I've been quite busy lately and have not have enough time to work this project.
Regardless, I believe that you are emerging version 5.15.3 and not 5.13.13. The latter (5.13.13) is currently the latest version that is working. Perhaps try making sure that you have typed the following into /etc/portage/package.mask
`

sys-kernel/surface-sources-5.13.13
`

I hope this fixes your problem.
Sincerely,
Parin


Script cannot run successfully

[Enter feedback here]
Below script cannot run successfully. Please repro from your side. For the azureSubscription Pram, please help check if it's correct. Please confirm if it should be sercive connection name.

task: AzureCLI@2
inputs:
azureSubscription: 'your-azure-subscription'
scriptType: 'bash'

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

ID: 229d5555-e668-139a-36a8-efa4b10f053e
Version Independent ID: af5a586a-05df-6476-e486-b5b6ae37cdbd
Content: Azure DevOps for CI/CD - Azure Machine Learning
Content Source: articles/machine-learning/how-to-devops-machine-learning.md
Service: machine-learning
Sub-service: mlops
GitHub Login: @juliakm
Microsoft Alias: jukullam

@Jessieliu111
Thanks for your feedback! We will investigate and update as appropriate.

@Jessieliu111 I believe the directory structure of the repo has changed and could be causing issue while running the scripts. The changes should be the following:
- script: pip install -r sdk/dev-requirements.txt
to
- script: pip install -r sdk/python/dev-requirements.txt
`filePath: 'sdk/setup.sh'`

to
filePath: 'sdk/python/setup.sh'
workingDirectory: 'sdk/jobs/single-step/scikit-learn/diabetes'
to
workingDirectory: 'sdk/python/jobs/single-step/scikit-learn/diabetes'
@juliakm Could you please review the changes and update the documentation?

Thanks @RohitMungi-MSFT! I'll make the update now.


Updating bower.json ignore files

We're no longer using a script directory, and we have a few other unnecessary files.
@mdo @primer/owners

:thumbsup: Makes sense to me.

Just need to sign that CLA @jonrohan :D.

lol, I thought I did. So I did again.

Hah, yeah, I think we've got some kinks to work out in the CLA stuff. Biggest one I've seen thus far is that sometimes it's not firing off for folks on push alone. I updated the hook to fire when adding labels and what not though, so if you don't see a second CI check, just change the label.

Biggest one I've seen thus far is that sometimes it's not firing off for folks on push alone.

Please ping me if you see it not firing. The webhook was mis-configured last Friday, but I fixed it Saturday morning. If there have been any PRs that don't have a status since then, it's a bug and needs to be fixed.

I updated the hook to fire when adding labels and what not though, so if you don't see a second CI check, just change the label.

The app ignores everything except the pull_request event, which is fired whenever a PR is "synced" (created, pushed, etc). I'm not sure if changing the label kicks that off, but having the label event enabled won't do anything.


fix: No warnings in test directory

🔗 Related Issues

closes #65

🙌 What's Done

Do not display warnings in the test directory
Removed the code that said to exclude warnings in _test.dart that was previously there.

✍ What's Not Done

🖼 Image Differences

Before
After

image
image

🤼 Desired Review Method

[ ] Correction Commit
[ ] Pair programming

[!NOTE]
It is possible that a reviewer's will may cause a method to be implemented that is not selected.

📝 Additional Notes

Pre-launch Checklist

[ ] I have reviewed my own code.
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] I updated/added relevant documentation (doc comments with ///).

@riscait
Correction and self review completed.
The following actions have been taken

/example/analysis_options.yaml, set the rule for avoid_hardcoded_color to true
Avoid warnings in /test/ directory
Move the contents of /lint_test/lints to example/lints/
Create example/test/ directory


Add e2e test for Azure Key Vault

Proposal
https://github.com/kedacore/keda/tree/main/tests
Use-Case
No response
Anything else?
No response

There is already a key vault test that with the azure queue scaler.

you're right!
Thanks for the reminder ❤


Suggestion results

Search for events starting within 30 minutes with a preference for those containing IBM or mapping in the description

@rajrsingh We need to revisit this. There are only 6 events in 10 days that match IBM or map.

@markwatsonatx how about also adding watson OR cognitive OR machine learning OR data science OR analytics

This has been addressed. The search terms are configurable in an environment variable which is currently set as follows:
SUGGESTED_SEARCH_TERMS=ibm,map,cognitive,machine learning,data science,analytics

Looks great!


lemmy: Support secret options

Description of changes
This set of commits implements an option to store parts of the configuration of lemmy outside the Nix store by reading and merging it at runtime before the service starts as discussed in #101777.
The lemmy service stops being run as a dynamic user to allow for fine grained permissions on secret files.
Things done

Built on platform(s)

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

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

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

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

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

[✓ ] Fits CONTRIBUTING.md.

this looks good to me.
I've merged the other PR fixing the default database uri so as to not delay this PR too much. There are conflicts now though.
Not adding other hardening options in this PR makes sense to me, it's good that this PR is small.
version 0.18.0 upgrade should be merged soon.

I don't plan other changes.

@Deric-W can you rebase the branch, it looks like there are some conflicts with master.
@jian-lin Are you ok to merge this ?

Sorry for closing and reopening this PR, I did make some mistakes when forking this repository.

@Deric-W no worries, that happened to me more than once.
@jian-lin the commits have been merged, and the changes look good, do you think we missed anything else ?

This seems like a very ad-hoc mechanism with questionable semantics. I think we should revert.

Happy to revert, what do you propose though ?


Russian translation adjusted

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Thank you for opening this pull request.
This is a standard message notifying you that we’ve reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you.
Reason:  You should not be changing any of the code sections (seed or testStrings).
Please create a new PR with only translations of Description, Instructions, and text of the tests if you want to still make changes.
Thank you and happy coding.


Alert annotation on station change

Steps to reproduce:

Go to trips page with alerts: (https://dashboard.transitmatters.org/red/trips/single/?to=70075&from=70067&date=2023-07-20)
Open alerts modal, select alert to apply to graph.
Switch to station param
Chart will keep annotation on headways, but not travel times.

I don't see any yellow boxes on prod 🤔

Did you select an alert from the alerts modal? The modal comes up from tapping the warning emoji on the bottom right.

Did you select an alert from the alerts modal? The modal comes up from tapping the warning emoji on the bottom right.

Ah I see, Honestly I think we should just add them to the graphs by default with a tooltip of what the delay was for

I looked into this a bit. I was able to reproduce locally. From the component state, it looks like the travel times chart is actually  the "correct" one in that the alerts aren't applied after you change one of the query parameters. The other components must just not be getting repainted for some reason.


Monitoring Flights that aren't Non-Stop

Great work with putting this together!
I'm having a hard time figuring out how to monitor flights that aren't non-stop. How do we specify the "flightnum" variable for those flights?
Thanks.

Hi @sirusss, thanks for your comment, I appreciate you taking an interest in this project. Monitoring outbound flights that aren't non-stop seems to work just fine for me. Here's an example:
Flight on Southwest website that isn't non-stop: https://i.imgur.com/8cUIPAF.png
python app.py --company Southwest --depart HOU --arrive MDW --departure-date 08/21/2018 --departure-time ANYTIME --passengers 1 --max-price 200 --interval 30 --no-text --flightnum 867 --one-way
Result of program: https://i.imgur.com/I54E5B1.png

Thanks for the reply, @wcrasta! How would you go about monitoring the following flight: https://imgur.com/a/PLtCeL7
As you can see, this specific flight travels on both flights 1636 and 534...so what would the program command look like? Thanks!

Just specify one of the flights as the flight num. The following command should do the job:
python app.py --company Southwest --depart HOU --arrive MDW --departure-date 08/21/2018 --departure-time ANYTIME --passengers 1 --max-price 200 --interval 30 --no-text --flightnum 1636--one-way


feat: run on windows with wsl2

https://matrix.to/#/!fSmTzeelJHuQezhZDa:matrix.org/$1yXy21Arg87ImzIxfG5C5yWKIkKaJVxFZSdb_oP3ngo?via=matrix.org&via=cyberia.club&via=mozilla.org

With PulseAudio running on Windows, it's possible to run the Assistant natively under WSL. However, once I started Doing Stuff, I started producing BSODs that I never really figured out.
I came to associate them with launching Windows applications from a skill, but I never nailed it down.
Just a word of warning, and a reason to use this a lot before declaring it supported.

@mikejgray awesome! :+1:
Could you please rename the docker-compose.wsl2.yml to docker-compose.windows.yml, it will be clearer for people not really comfortable with what WSL2 means.
As well, could you please add a little section in the main README about Windows (as I did for Mac OS)?

@mikejgray awesome! 👍
Could you please rename the docker-compose.wsl2.yml to docker-compose.windows.yml, it will be clearer for people not really comfortable with what WSL2 means.
As well, could you please add a little section in the main README about Windows (as I did for Mac OS)?

Done


How to modify the attributes of an address object using SDK?

Is there a function available to update the name, ip , description and tag of a specific address object in panorama using pan-os python SDK

Posted in discussion