Update dledger version to 0.2.4

Make sure set the target branch to develop
What is the purpose of the change
Update dledger version to 0.2.4
Brief changelog
Update dledger version to 0.2.4
Verifying this change
XXXX
Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

[x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Codecov Report

Merging #4111 (4dbc9ee) into develop (fd554ab) will decrease coverage by 0.07%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             develop    #4111      +/-   ##
=============================================
- Coverage      47.91%   47.83%   -0.08%
+ Complexity      5001     4991      -10
=============================================
  Files            634      634
  Lines          42529    42529
  Branches        5573     5573
=============================================
- Hits           20377    20343      -34
- Misses         19651    19681      +30
- Partials        2501     2505       +4

Impacted Files
Coverage Δ

...in/java/org/apache/rocketmq/test/util/MQAdmin.java
38.88% <0.00%> (-5.56%)
:arrow_down:

...ava/org/apache/rocketmq/test/util/VerifyUtils.java
46.26% <0.00%> (-2.99%)
:arrow_down:

...ava/org/apache/rocketmq/filter/util/BitsArray.java
59.82% <0.00%> (-2.57%)
:arrow_down:

...va/org/apache/rocketmq/logging/inner/Appender.java
34.83% <0.00%> (-2.25%)
:arrow_down:

...ent/impl/consumer/DefaultLitePullConsumerImpl.java
67.75% <0.00%> (-1.56%)
:arrow_down:

...rg/apache/rocketmq/remoting/netty/NettyLogger.java
14.96% <0.00%> (-1.37%)
:arrow_down:

...a/org/apache/rocketmq/store/StoreStatsService.java
35.85% <0.00%> (-1.13%)
:arrow_down:

...che/rocketmq/namesrv/kvconfig/KVConfigManager.java
59.18% <0.00%> (-1.03%)
:arrow_down:

.../apache/rocketmq/logging/inner/LoggingBuilder.java
63.92% <0.00%> (-0.80%)
:arrow_down:

...che/rocketmq/acl/plain/PlainPermissionManager.java
75.19% <0.00%> (-0.52%)
:arrow_down:

... and 2 more

Continue to review full report at Codecov.

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

Coverage increased (+0.007%) to 51.962% when pulling 4dbc9eebc57380e79d3e8708134fbb4ddabc9957 on RongtongJin:upgrade_dledger2 into fd554ab12072225325c957ff6bdf492fc67821af on apache:develop.


Move/migrate analysis target status check to scorecard.

As the ScoreCard model will have a separate entry for all of the analysis reports in each new release, the logic to decide whether to analyze something becomes much simpler. We are already storing the scorecard reports in parallel to the "live" records, and this is the first step for relying on that data.

Are there any risks here?

Mostly refactoring and using the same code in a different way. One behaviour change is that we'll now check for the existence of the ScoreCardReport, and not the Analysis records. In practice this shouldn't add much risk.


Made some changes to header for renaming tabs and removing unused ones

Renamed some things in the tabs. Also commented out unused tabs for now (like Chat and Teachers). Removed drop-down from 'Contact Us' - will need future fixing-up.

Looks good. 👍


Exclude test in find_packages

To avoid conflicts with projects that have tests in their top-level
directory:

exlude tests in find_packages
add include in MANIFEST.in

Closes: #688
Signed-off-by: Spyros Trigazis<EMAIL_ADDRESS>Note: oauth2client is now deprecated. As such, it is unlikely that we will
review or merge to your pull request. We recommend you use
google-auth and oauthlib.

I'll sign the CLA.
Please review

I signed it!

A point release would be nice after this goes in!

Does the googlebot take that long to be updated?

@strigazi it's pretty instant. Are you sure you signed the CLA and authored your commits with an email associated with your account?

@strigazi github is showing an unknown author for this commit.

I can try my gmail. I have my CERN email as a secondary email in google account.

@strigazi this issue is the email on your commits which isn't associated with your github account. If you add your cern email to your github account, it should all work. :)

Thanks, @strigazi! I will merge when CI passes.

So, it works only with my gmail :(

@jonparrott Can you also do a point release after?

@strigazi if you'll make a release PR (example)

(Travis passed, system test failures are expected on external PRs)


Auto completion doesn't show values of variables whose value is known

Environment data
VS Code version: 1.20.1
Python Extension version: 2018.1.0
Python Version: 2.7.12
OS and version: Ubuntu 16.04.3 amd64
Actual behavior
The auto completion support doesn't show the value of variables whose value is known which the autocomplete-python[-jedi] extensions for Atom does show. (The code in this extension seems copied and modified from it).
Expected  behavior
It should show them like the extension for Atom does. The code in completion.py is already there. It's a matter of wiring it up into the VS Code API nicely (It's something the extension for Atom implemented and not a pure stock feature of Jedi).
Showing the values of stuff is done by this bit of code:
https://github.com/Microsoft/vscode-python/blob/fafd0f8888b8d6a9a995b8da4495c8a83d3f9a9e/pythonFiles/completion.py#L60-L70
Called from here:
https://github.com/Microsoft/vscode-python/blob/fafd0f8888b8d6a9a995b8da4495c8a83d3f9a9e/pythonFiles/completion.py#L220
It shows it on the right hand side of a completion suggestion. VS Code is calculating this but than not using this property. Only showing the doc string for the type of the completion which is what we are seeing (I think it might even be getting the doc string by itself rather than relying on Jedi).
Steps to reproduce:

Try auto completion for SPA below:

SPAM = 123

SPA

Screenshots
Atom

VS Code

P.S. The code throws a bunch of lint warnings from a linter like flake8, and in particular ARGUMENT_RE is not defined for this bit of code:
https://github.com/Microsoft/vscode-python/blob/fafd0f8888b8d6a9a995b8da4495c8a83d3f9a9e/pythonFiles/completion.py#L254-L255
Though it's probably currently unused by this extension.
Originally: https://github.com/Microsoft/vscode-python/issues/171#issuecomment-362757940
@MikhailArkhipov

show values of variables whose value

This isn't a feature that we support today. Personally I don't see any value in doing this, even if it were possible it would introduce some complexity in providing these values.

@DonJayamanne Are you sure? As I noted, the code for getting the value is already there... (Copied from the Atom extension apparently).


Remove a wrong 'is' usage

Comparing a string against a string literal with 'is' looks wrong,
said pylint.

That's a good link! Thank you.


cannot download youku video

sincos@Saito-MBP:~/Downloads$ youtube-dl --list-formats http://v.youku.com/v_show/id_XMjQ4MTQwODU5Ng==.html
[youku] XMjQ4MTQwODU5Ng: Downloading JSON metadata
ERROR: Youku server reported error -603: 客户端无权播放,201; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

Carefully read new issue template and provide all requested information.

This is already fixed in the latest version. https://github.com/rg3/youtube-dl/blob/master/README.md#how-do-i-update-youtube-dl can be useful.


User gets wait icon

User get an wait icon after editing for a while:

user is afraid of losing data

@laurentjg can you state the steps for getting this error?
Was is a new file?
Did you saw the save as dialog?

Hi @Sander3003, I tried to reproduce it, but I didn't get the same behavior, but other issues this time. Probably pointing to the same direction: a connection loss to CoMPAS. What I did: I opened OPENSCD with CoMPAS, opened a file from CoMPAS, added a bay and a component and waited for 1 hour. After that the following errors appears (I tried 3 times).
I also tried to open a project from CoMPAS, but that also resulted in a loading-screen only. See pictures below. I hope this helps.
I

Thanks for the feedback!

It doesn't seem that the original issue is caused because of authorization issues. It should then be more something like the screencaptures in the comment (https://github.com/com-pas/compas-open-scd/issues/70#issuecomment-930288649).
The authorizations issues we want to solve with issue 74 (https://github.com/com-pas/compas-open-scd/issues/74). Make some kind of modal panels informing the user that session is about to expire. This way we hope to solve these issue.
So we will close this issue and continue in issue 74 for solving the authorization problems.


Possible Issue with capybara-<IP_ADDRESS> and selenium-webdriver 2.0.1?

Hi there,
Thank you all for your hard work on this gem.
It's really nice that capybara can help us to use different web drivers seamlessly as needed.
We are trying to get some integration testing done with cucumber + capybara + selenium/capybara-webkit for our existing app.
Capybara seems to work fine with capybara-webkit-0.5.0 although there are some issues along the way.
We have an issue when we try to use selenium to see what's really happening when we run tests.
This is the error message I'm getting:
  Given I am the admin             # features/step_definitions/party_steps.rb:20
      private method `select' called for #<Selenium::WebDriver::Element:0x0000010ca264a0> (NoMethodError)
      ./features/step_definitions/web_steps.rb:72:in `block (2 levels) in <top (required)>'
      ./features/step_definitions/web_steps.rb:14:in `with_scope'
      ./features/step_definitions/web_steps.rb:71:in `/^(?:|I )select "([^"]*)" from "([^"]*)"(?: within "([^"]*)")?$/'
      features/add_bookings.feature:9:in `Given I am the admin'

This is the installed gems which you might need to know:
rails-2.3.11
bundler-1.0.12
cucumber-1.0.1
cucumber-rails-0.3.2
capybara-<IP_ADDRESS>
capybara-webkit-0.5.0
selenium-webdriver-2.0.1
If I use capybara-0.4.0 and selenium-webdriver-0.1.3 , they seem to work fine but I don't think I can use capybara-webkit with that version of capybara.
It seems like there is an unspecified dependency behind the scene.
It's a pain that cucumber-rails doesn't officially support rails 2.x anymore and I hope that's not the case with capybara.
I googled quite a bit for last few days, but it wasn't very successful.
Can anyone give me any suggestion for the working combination of gems or workaround at least?
Thank you for your help in advance.

thank you @bowsersenior that works a treat! :D


Move pointcloud displays to rviz_default_plugins

This moves the pointcloud displays to rviz_default_plugins and integrates the pluginlib.
Fixes #135.

I also rebased this because our CI cannot automatically merge the pr branch to the target branch when it comes from a fork. CI:

Linux
Linux-aarch64
macOS
Windows

Fixed missing dependencies:

Linux
Linux-aarch64
macOS
Windows

Uncrustify... new CI:

Linux
Linux-aarch64
macOS
Windows

I can't win with these linters 😛, new CI:

Linux
Linux-aarch64
macOS
Windows

The aarch64 job hung it looks like, but since it passed before with just linter changes, I'm going to merge without it.


Update Guid.cs (Ctor Performance)

Performance improvement to Guid initialization, about 20% faster copying of array elements to _d to _k variables.

@dotnet-policy-service agree [company="{Relewise ApS}"]

@dotnet-policy-service agree company="Relewise ApS"


Deploy a CAP Business Application to SAP Cloud Platform

Tutorial URL: https://developers.sap.com/tutorials/cap-service-deploy.html
Step 3, item 2
"cds build" command only generates gen/srv, not gen/db.  No manifest.yaml files are created in gen/srv.
"cf push -f gen/db" fails since gen/db does not exist
"cf push -f gen/srv --random-route" fails since there is no manifest
@sap/cds: 4.1.5
@sap/cds-compiler: 1.35.0
@sap/cds-dk: 2.0.7
@sap/cds-foss: 2.0.0
@sap/cds-reflect: 2.12.2
@sap/cds-runtime: 2.1.5
@sap/hana-client: 2.5.104
Node.js: v12.16.2
Thank you

Sorry for the late reply, I was on vacation for a long time. Could you please try it again with the latest version @sap/cd-dk: 2.0.8?

Thank you for your feedback. We haven't heard from you in a while, so we are closing the issue.
If you still have questions, feel free to reopen the issue.


Feat/style dictionary/multi config support

Current Behavior
We are only supporting one single configuration on style-dictionary.config.ts.
Expected Behavior
Now we are going to support one single configuration and multiple configurations on style-dictionary.config.ts.
Related Issue(s)

Fixes #70
Checklist:

[X] I have performed a self-review of my own code
[X] I have made corresponding changes to the documentation
[X] Added new tests to cover the fix / functionality

This is awesome! 🚀 Thank you @jgrodriguezc

@allcontributors please add @jgrodriguezc for code


Feature request: skip_bucket_creation, skip_dynamodb_creation for s3 backend (like GCS)

I've used terragrunt against gcs successfully, and used the skip_bucket_creation option for a gcs backend.
However this option is not available for s3 backend. Instead terragrunt runs interactively and asks the question if I want the bucket or not.
I am not allowed to grant terragrunt the ability to manage buckets directly, because I work in a highly permissioned environment where terragrunt has no permissions to manage data storage, and making buckets must be part of terraform through an assigned storage manager role. (I get no choice over this as- you know- banking). And also, there are highly strict requirements about bucket configurations, so i cannot just accept the terragrunt defaults that terragrunt comes up with even though there are feature flags and options to configure some items, its just not granular enough.
It would be really useful if terragrunt had the option to skip trying to want to manage buckets and dynamodb tables so that I can just do it in terraform instead for the s3 backend. There seems to already be precedent in this for a GCS backend, where you can skip creation (which we do for the GCS cloud)
I dont want s3 buckets to be inadvertently created before the permissions structure is setup and then have to do terraform imports and then change the configuration, or worse still, have to delete and recreate the bucket and wait the 24h turnaround time.
Thanks!

Adding support for skip_bucket_creation to S3 would be consistent, but perhaps for your use case, you should disable auto-init?

Hey guys, I would like this feature too. I would like my terragrunt commands to fail if the s3 bucket isn't created yet.
@brikis98 I tried doing terragrunt init --terragrunt-no-auto-init and it still asked me if I wanted to create the bucket.


Please remove leading whitespaces

Description
Please see the video:
https://user-images.githubusercontent.com/52394598/204144533-433ae181-4bf8-489b-b371-a87d0b924c10.mp4
If the former SQL has leading whitespaces, there always be leading whitespace in the new line once I press Enter.
DBeaver Version
22.2.5
Operating System
Windows 11 22H2
Database and driver
Any
Steps to reproduce

Type the following SQL:

   select 1 from dual;|

Press Enter at the | position

Additional context
No response

Hello. Thanks for the report.
I'm not sure about the

always be leading whitespace

But the first time - it is true.

Hello Anastasya,
I have the same problem like humphreygao. I also think, this should not happen, if I clear the line and I am at the first position of the line. Then the next line after an Enter should also be on the first position.
I use Windows 10, DBeaver 2.2.5 and a Snowflake connection.
Why does this work in your environment?
Do you have other settings?
Is it dependent on the connection?
I do not know.
Principally the auto indent is a very good thing. But sometimes it wolud be fine, to go to the first column with one return.
Maybe it is possible, that a Shift+Enter returns to the first column.
I hope you will implement this idea, thanks in advance, BR
Günter

is there any solution for this problem?
It is so annoying that unnecessary white space.
this makes me crazy.
please help me.

duplicate of https://github.com/dbeaver/dbeaver/issues/8552


[Bug]Updating the Markdown LinkName Does Not Update Links in Admonition Blocks

Step1: We want to update Link Name (highlighted)

We Change the Name.

We Expect Links to Be Updated.
Result:
Links are Not Updated in Admonition Blocks

Great plugin, big fan, just pointing out this bug.

Thanks :) Merging this with #144.


feat: add stats command to container

close #2393

=== RUN   TestStats
    container_stats_linux_test.go:45: assertion failed:
        Command:  /usr/bin/docker container stats --no-stream
        ExitCode: 0
        Stdout:   CONTAINER ID   NAME      CPU %     MEM USAGE / LIMIT   MEM %     NET I/O   BLOCK I/O   PIDS

        Stderr:

        Failures:
        Expected stdout to contain "nerdctl-test"
--- FAIL: TestStats (6.40s)

https://github.com/containerd/nerdctl/actions/runs/5676272811/job/15403686941?pr=2395

=== RUN   TestStats
    container_stats_linux_test.go:45: assertion failed:
        Command:  /usr/bin/docker container stats --no-stream
        ExitCode: 0
        Stdout:   CONTAINER ID   NAME      CPU %     MEM USAGE / LIMIT   MEM %     NET I/O   BLOCK I/O   PIDS

        Stderr:

        Failures:
        Expected stdout to contain "nerdctl-test"
--- FAIL: TestStats (6.40s)

https://github.com/containerd/nerdctl/actions/runs/5676272811/job/15403686941?pr=2395

I tried this test case locally and it works fine.  Could you please rerun it?


Add progress-tracker example

Adds example with a progress bar that's updated over time after clicking on a button. The button spawns a thread that sends an event each second through a channel to a gtk::idle_add that periodically checks for values.
Adds the cascade crate since it makes constructing GTK widgets simpler.
Closes #209

Is it ready to go?

As far as I know.

Let's merge then. Thanks!


Enhancement: Add a "recent" section

It'd be really cool if vimawesome could show all the new vim plugins that people are making. This could be done with a "recent" or "new" section of the site.

Do you think it would be more valuable to list newly discovered plugins (which may be of little value since they might not be complete) or newly popular plugins? The latter seems more valuable for discovering plugins which would actually be useful to use, but it would also require an opinionated definition of what "popular" means.

Related: https://github.com/divad12/vim-awesome/issues/7

Maybe "trending" is a better way to convey this? "Recent" (at least in my view of the language) only implies "new".

On Mar 9, 2016, at 9:48 PM, Jordan Eldredge<EMAIL_ADDRESS>wrote:
Related: #7
—
Reply to this email directly or view it on GitHub.

Can we address this just by providing sorting options? Off the top of my head:

Newest
Recently updated (by date of latest commit?)
Most popular (all time)
"Trending" (this is a place things always get fuzzy and would require a bit of work in the direction of "normalized increase in usage / stars in the past X days")

To address #7, we can just provide the information in these lists in different content types. i.e. if I request /plugins/new.json, the response data gets serialized to a JSON object. If I request the same endpoint with .rss instead, an RSS template gets rendered with the same info (this content type negotiation is easily done in Flask).

See also: #13.

+1


fix(db): exclude unsupported pg15 patch versions from loading

What kind of change does this PR introduce?
Bug fix https://github.com/supabase/cli/issues/1877#issuecomment-1909695253
What is the new behavior?
pg15 patch versions below 55 are not supported.
Additional context
Add any other context or screenshots.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.04%) to 58.796%

Totals

Change from base Build<PHONE_NUMBER>:
-0.04%

Covered Lines:
6123

Relevant Lines:
10414

💛  - Coveralls


[client] The documentation is clearly lacking some explanations about payloads

The current state of the client documentation is not really helpful. Most of the payloads are not detailed in the docstrings and thus in the documentation.
This is the documentation for the get_site_devices method:

Worst thing about this: in this case, the payload is really simple (site_id). I think we should do something about that soon :sweat_smile:

I'll open up a PR this weekend to tackle this smoothly


Test with ipa as CA

Is it still Draft?
Is it intended to be merged eventually? #23 touched the same code.

I think @amore17 was using this for test purposes only. Is that correct @amore17?
I suppose we can close.

I think @amore17 was using this for test purposes only. Is that correct @amore17?
I suppose we can close.

Yes closing this one.


Allow 14 char passwords and use one in winrm

Fixes this failure: https://console.cloud.google.com/storage/browser/_details/gcp-guest-cloud-test-outputs/2024-04-25T10:52:30Z/winrm/windows-server-2016-dc-core-v20240415/daisy-winrm-20240425-13:07:14-716br/logs/server-winrm-716br-serial-port1.log;tab=live_object

/cc @koln67

/lgtm


Remove an erratic NPE

In this PR we remove a non-descriptive NullPointerException that used to be thrown in some cases when an insertion point was not present in a given file.
The behavior was inconsistent and undocumented.
Now, nothing happens, just like the doc says.

@alexander-yevsyukov, @armiol, PTAL.

@armiol, I've removed the draft mark. Probably just eventual consistency.


AddField before/after seems to not be working properly

Hi,
Tested to add field with the before/after parameters but it seems it's not interpreted correctly - or I did not understood the doc:

Quick question, are you using the setFromDBAuto thing?

@OwenMelbz No, as discussed in the lobby, I tested without $this->crud->setFromDb(); forgot to gave this info int the issue report sorry. That is why it is either a weird behavior or wrong coding from my part.

Does this PR fix it for you?
https://github.com/Laravel-Backpack/CRUD/pull/472

This may be related, bu it is for COLUMN and I reported the issue for FIELDS. This can be the same root cause but I was enable to apply the path to src/PanelTraits/Fields.php as the code is quite different.

Hi @MickaelTH ,
Fixed! Finally. Turns out it was because of setFromDb() after all. setFromDb() used strings as keys for the columns array, addColumn() used integers. It's a wonder this hasn't produced more bugs until now.
Anyway, it's now fixed on the dev branch. After a few more people test it and confirm it's working, we'll merge it to master. If you want to use the fix yourself, please use the dev branch in your project. If you find anything - say so. If you don't, say so :-)
Cheers!

@tabacitu Ok this one can be closed. Thank you again for resolving it!


Add unified release action

This builds on @sethaxen's work in #70 to create a unified release action for the repo. It also updates a few documentation pages in anticipation of the release.
The steps the Action takes are roughly:

Replace the version numbers in all interfaces with the new version
Build the .tar.gz file we attach to a release
Update the Julia Artifacts.toml file
Push a commit to the repo with the above changes
Create a tag and release
Push to PyPI (@roualdes this will require us adding a Secret to the repository for a PyPI token once)
Comment on the commit from 4 with a @JuliaRegistrator register  (@roualdes this will require following the pre-registration instructions here https://github.com/JuliaRegistries/Registrator.jl once)

If any step up to and including 5 fails, you can re-run the script without any problem. If any step after 5 fails, you need to check a box on the Workflow page while running which will skip re-creating the release, and will just upload to PyPI/JuliaRegistries
After the automated release we can manually edit the releases page to include the change log.
After this is merged I suggest we more or less immediately run it to release 1.0.1 which will start the Julia Registration process. We can also discuss if we want to eventually make the Python interface able to download the C++ source, like the Julia interface now can, but I decided to leave that for later.

@roualdes I just wrote to you about some config details for this that need to be done in repository settings before this would work fully


Increase max_length of Tenant name field

Issue type
[X] Feature request
[ ] Bug report
[ ] Documentation

Environment

Python version: 3.6.4
NetBox version:  tag 2.3.2

Description
The max_length of Tenant model is to small (max_length=30) https://github.com/digitalocean/netbox/blob/develop/netbox/tenancy/models.py#L44 this also affect the slug field on the same model.
Suggestion is to update this to something larger like max_length=255 for both fields so i can add a Tenant that has more then 30 letters in it's name.

@jeremystretch Would the decision in the mentioned Issue also apply to the value lenght of CustomField:s? The situation for me right now is that i have several "free text" fields that is much longer then 255 characters and i can't merge them all into the comments field.
In the end if this won't be changed in the official release i will simply overwrite it in my fork and live with it in there.


Hang on source file search when opening $HOME

Discussed in https://github.com/microsoft/vscode-python/discussions/16700

Originally posted by abartlett004 July 15, 2021
Suddenly, the auto-complete and colored font features of Intellisense are no longer working for me, although it seems that pylint is still working because it has found problems in my script. I have tried closing and reopening VS code, uninstalling and reinstalling VS code, uninstalling and reinstalling the Python, Jupyter, and Pylance extensions, and changing my Python language server settings from default to Pylance to Jedi and back again with no success.
I am using VS code 1.58 and Python 3.7.9. Any ideas as to what could be causing this? I'm happy to provide any additional info.

@abartlett004 We'd appreciate if you could fill out the info requested here: https://github.com/microsoft/pylance-release/blob/main/TROUBLESHOOTING.md#filing-an-issue
(Or, file a new issue and use the template.)
But, it's suspicious that no analysis works, even Jedi.

Here is the requested info. Please let me know if I am missing anything!
 Can you set "python.analysis.logLevel": "Trace" and attach the logs in text (not a screenshot)?

Ok, I have changed that setting and attached is the new output. Is this what you mean? Also, for what it's worth, Intellisense happens to be working right now, although it has been intermittently working and not working over the past few days.
trace.txt

You seem to be opening your entire home folder as your workspace, so we're getting stuck trying to scan all of the files before starting to analyze them. Can you open the specific project you are editing, rather than the entire home folder?
This is made worse by using WSL on Windows folders, as IO between WSL and Windows folders is quite slow.

Ah I understand, I didn't realize the extension was analyzing all files in the workspace rather than just the few I had open. VS code seemed to have just been defaulting to opening my entire home folder. Now that I open a more specific folder containing the code that I am editing, the extension seems to load much faster. Lesson learned!

It only analyzes the ones you've opened, but at the moment, we scan for a list of files in the workspace so we can do things like distinguish library files from user files (so that you can't rename a function from the standard library, for example).
We've gotten a pretty significant number of issues lately about this; it may be worth some thought figuring out how we can avoid this work when we're not in workspace diagnostic mode (so therefore only need the list of source files for specific operations).

We still need this list to do implement features like "Go to references", "Find all references", etc. However, we may want to time-bound the scan and cut it short (perhaps with an accompanying error dialog) if it's taking a long time — say, more than 20 sec. We should probably also see what the typescript LS is doing. I thought they had similar scanning logic, but perhaps they've come up with an alternative approach to work around issues like this.

asking is basically making source scanning lazy.
we only check file tracking at the time of file open and only do full scanning when solution wide feature is executed such as find all reference, rename, workspace symbol or workspace wide diagnostic mode.

Moving this issue to discussion as an enhancement request for comments and upvotes.


Create PlayerKillEvent.java

I always have wanted Bukkit to have this, please please pull this.

https://github.com/TridentSDK/TridentSDK/blob/bleeding-edge/src/main/java/net/tridentsdk/event/player/PlayerDeathEvent.java

I believe he might be referring to if a Player has been killed, not died for an ambiguous reason.

Why would that even be necessary when, with just a few lines, you can easily derive the cause of death from PlayerDeathEvent.


LTS

Is this still supported? Just curious about LTS of this framework!

We don't have an official LTS strategy, but LTS versions seem somewhat uncommon for Python packages. However, ebmlite is a critical component of several projects here at Mide Technology, both internal and external. As such, we're committed to developing and maintaining it indefinitely. If/when we ever introduce API-breaking changes (v 4.0+), we will probably end up with something like an LTR branch of v 3.x, but that's not currently in the plans.

Great! That is what I wanted to be sure of nonetheless. Thank you kindly


chore(rootfs): upgrade to openssl 1.1.1l

Upgrade OpenSSL from 1.1.1k to 1.1.1l
Shrink Docker image around 10 MB by merging the chown into the build layer

Thank you for this contribution @felixbuenemann !


[UI/UX] Better sidebar text alignment when empty

Currently the text don't have borders around it, it is also white (the theme is minimal, but what I would want is to use the second "dimmed" variable for colors as most plugins use instead of primary color)

Example improvement how the text might looks like (Pandoc References Plugin)

Very nice idea, tnx. This will rollout with the 0.0.30 update today.
Also the text in the pane can be overridden with the following CSS elements:
snw-sidepane-loading


Section for All Suits of Tony Stark (Iron Man)

I would Love to see a section/ page for the iconic suits of Iron man all of the Mark Assembly
@aslams2020

@aslams2020 assign this issue to me under the relevant tags of gssoc and hacktoberfest


plugin-pg | error: TypeError: Cannot read property 'RECORD_AND_SAMPLED' of undefined

What version of OpenTelemetry are you using?
"@opentelemetry/api": "^0.9.0",     "@opentelemetry/core": "^0.9.0",     "@opentelemetry/node": "^0.9.0",     "@opentelemetry/plugin-dns": "^0.8.0",     "@opentelemetry/plugin-grpc": "^0.9.0",     "@opentelemetry/plugin-pg": "^0.8.0",     "@opentelemetry/plugin-pg-pool": "^0.8.0",     "@opentelemetry/tracing": "^0.9.0"
What version of Node are you using?
v12.6.0
What did you do?

Installed packages above
enabled grpc and pg plugins (Gist)
included tracing config into my index.ts
ran yarn start of my project

What did you expect to see?
No console errors like with grpc plugin
What did you see instead?
PluginLoader#load: trying to load<EMAIL_ADDRESS>error: TypeError: Cannot read property 'RECORD_AND_SAMPLED' of undefined
Additional context
The entire OpenTelemetry solution with gcloud exporter works very well if I only enable grpc plugin, as soon as I enable pg locally it throws the error, seems like nobody has ever reported that before.
The problem triggers in
<EMAIL_ADDRESS>on the line 63
It seems like @opentelemetry/api doesn't actually expose SamplingDecision object, even though the implementation is there and it's identical to SpanKind which is being exposed properly.
The print of the api object is as follows:
{   defaultGetter: [Function: defaultGetter],   NoopHttpTextPropagator: [Function: NoopHttpTextPropagator],   NOOP_HTTP_TEXT_PROPAGATOR: NoopHttpTextPropagator {},   defaultSetter: [Function: defaultSetter],   EntryTtl: {     '0': 'NO_PROPAGATION',     NO_PROPAGATION: 0,     UNLIMITED_PROPAGATION: -1,     '-1': 'UNLIMITED_PROPAGATION'   },   ValueType: { '0': 'INT', '1': 'DOUBLE', INT: 0, DOUBLE: 1 },   NoopMeter: [Function: NoopMeter],   NoopMetric: [Function: NoopMetric],   NoopCounterMetric: [Function: NoopCounterMetric],   NoopMeasureMetric: [Function: NoopMeasureMetric],   NoopObserverMetric: [Function: NoopObserverMetric],   NoopBoundCounter: [Function: NoopBoundCounter],   NoopBoundMeasure: [Function: NoopBoundMeasure],   NOOP_METER: NoopMeter {},   NOOP_BOUND_COUNTER: NoopBoundCounter {},   NOOP_COUNTER_METRIC: NoopCounterMetric { _instrument: NoopBoundCounter {} },   NOOP_BOUND_MEASURE: NoopBoundMeasure {},   NOOP_MEASURE_METRIC: NoopMeasureMetric { _instrument: NoopBoundMeasure {} },   NOOP_OBSERVER_METRIC: NoopObserverMetric { _instrument: undefined },   NoopMeterProvider: [Function: NoopMeterProvider],   NOOP_METER_PROVIDER: NoopMeterProvider {},   INVALID_TRACE_ID: '0',   INVALID_SPAN_ID: '0',   NoopSpan: [Function: NoopSpan],   NOOP_SPAN: NoopSpan {     _spanContext: { traceId: '0', spanId: '0', traceFlags: 0 }   },   NoopTracer: [Function: NoopTracer],   NOOP_TRACER: NoopTracer {},   NoopTracerProvider: [Function: NoopTracerProvider],   NOOP_TRACER_PROVIDER: NoopTracerProvider {},   SpanKind: {     '0': 'INTERNAL',     '1': 'SERVER',     '2': 'CLIENT',     '3': 'PRODUCER',     '4': 'CONSUMER',     INTERNAL: 0,     SERVER: 1,     CLIENT: 2,     PRODUCER: 3,     CONSUMER: 4   },   CanonicalCode: {     '0': 'OK',     '1': 'CANCELLED',     '2': 'UNKNOWN',     '3': 'INVALID_ARGUMENT',     '4': 'DEADLINE_EXCEEDED',     '5': 'NOT_FOUND',     '6': 'ALREADY_EXISTS',     '7': 'PERMISSION_DENIED',     '8': 'RESOURCE_EXHAUSTED',     '9': 'FAILED_PRECONDITION',     '10': 'ABORTED',     '11': 'OUT_OF_RANGE',     '12': 'UNIMPLEMENTED',     '13': 'INTERNAL',     '14': 'UNAVAILABLE',     '15': 'DATA_LOSS',     '16': 'UNAUTHENTICATED',     OK: 0,     CANCELLED: 1,     UNKNOWN: 2,     INVALID_ARGUMENT: 3,     DEADLINE_EXCEEDED: 4,     NOT_FOUND: 5,     ALREADY_EXISTS: 6,     PERMISSION_DENIED: 7,     RESOURCE_EXHAUSTED: 8,     FAILED_PRECONDITION: 9,     ABORTED: 10,     OUT_OF_RANGE: 11,     UNIMPLEMENTED: 12,     INTERNAL: 13,     UNAVAILABLE: 14,     DATA_LOSS: 15,     UNAUTHENTICATED: 16   },   TraceFlags: { '0': 'NONE', '1': 'SAMPLED', NONE: 0, SAMPLED: 1 },   Context: [Function: Context] {     ROOT_CONTEXT: Context { _currentContext: Map {} },     TODO: Context { _currentContext: Map {} }   },   context: ContextAPI {},   trace: TraceAPI {},   metrics: MetricsAPI {},   propagation: PropagationAPI {},   default: {     trace: TraceAPI {},     metrics: MetricsAPI {},     context: ContextAPI {},     propagation: PropagationAPI {}   } }
Sorry I didn't provide a PR with a fix, I couldn't figure out why it's not working, I'd appreciate if you could take a look into that. 🙏

As embarrassing and silly, reinstalling node_modules solved the issue. 🤦

Happens to everyone


Error while running question_answer.py

Hi,
I trained the model for few epochs and tried to test it using question_answer.py and using the coomns you provided
But it ended up with following error
ValueError: You are trying to load a weight file containing 4 layers into a model with 2 layers.

Yes i am also having the same issue
Please provide some solution to it


Could not load file or assembly 'Microsoft.TeamFoundation.Common

I am running into the following issue when i run the command for source control
Could not load file or assembly 'Microsoft.TeamFoundation.Common, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
at Microsoft.Dynamics.AX.Servicing.SCDPBundleInstall.PrepareCommand.RunCommand()
at Microsoft.Dynamics.AX.Servicing.SCDPBundleInstall.Program.Main(String[] args)
any thoughts what could be the cause?

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

ID: 66b4c899-c7e0-0406-0d39-d32fc41b6104
Version Independent ID: 5d015069-177d-e33c-094c-257df088a7c0
Content: Install metadata hotfixes in development environments - Finance & Operations | Dynamics 365 | #MSDyn365FO
Content Source: articles/dev-itpro/migration-upgrade/install-metadata-hotfix-package.md
Service: dynamics-ax-platform
GitHub Login: @RobinARH
Microsoft Alias: robadawy

Thanks for contacting us. Unfortunately, we're unable to handle Support requests for the product here. To contact Support, consider one of the options described here: [Support contact options](https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-itpro/lifecycle-services/lcs-support). In particular, you might want to go to the Dynamics 365 for Finance and Operations community page to get help with your questions from the Dynamics community.


dcos-image-deps: Remove outdated docker-py package

High-level description
This is a partial work that is required to re-enable SAML integration tests. The change in DC/OS Open is removing docker-py package that is unused, outdated and unsupported. The package is replaced with new docker library in EE PR.
Corresponding DC/OS tickets (obligatory)
These DC/OS JIRA ticket(s) must be updated (ideally closed) in the moment this PR lands:

DCOS-21531 dcos-integration-test: enable SAML tests again (PhantomJS doesn't support ES2015 anymore)

Checklist for all PRs

[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[ ] Read the DC/OS contributing guidelines
[ ] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[ ] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

@mesosphere-mergebot bump-ee

Failure in teamcity/dcos/test/aws/cloudformation/simple - test_networking.test_vip[Container_MESOS-Network_BRIDGE-Network_HOST] - https://jira.mesosphere.com/browse/DCOS-21761

@mesosphere-mergebot label Ready For Review

@mesosphere-mergebot override-status teamcity/dcos/test/aws/cloudformation/simple https://jira.mesosphere.com/browse/DCOS-21761


windows: missing TaskDialog

Fixed in a recent mingw-w64
# github.com/andlabs/ui
../../andlabs/ui/libui_windows_amd64.a(stddialogs.cpp.obj): In function `msgbox':
/home/simon/projects/libui/windows/stddialogs.cpp:113: undefined reference to `__imp_TaskDialog'
collect2: error: ld returned 1 exit status

how to resolve ?

This seems to only be part of mingw 5+, which has not yet been released.


Is it possible to remap h,j,k to other keys because of different keyboard layout?

Hello,
Since there is no discussion section, I had to ask this in this issues section.  Sorry about that.
I am using non latin1 keyboard. Is it possible to remap vim default keys to something else  such as  h=>k, j=>k, k=>m. Of course, I would like to map some other frequently used keys to more appropriate ones according to my keyboad.
Is it possible? If yes, how can I do that?  I have not seen anything in the documentation.
Thanks in advance.

Hey @benibilme, interesting question! And no worries, opening an issue is the right place to ask for this project.
So, my initial thought is that there is not a purpose-built feature in this package to remap keys (although there may  still be a solution to your problem). In the longer term, the direction of this package will be to use neovim under the hood, at which point one could configure behavior similarly to vim/neovim.
In terms of solving your issue in the present, though, I don't think it would be too difficult to add a simple configuration option for remapping some of the keys.
You've articulated a few of the mappings you'd like to change, could you describe some of the other frequently used keys you'd like to remap? Is it solely motion commands, or would you also want to be able to remap operators (e.g. c, d)?
I ask so that I can understand how extensive a "remapping" feature would need to be.
Thanks!


PolygoniD qrcode difficult to read with IOS camera (iphone 14 !)

to be improved

on clique social

Also need to check on https://talao.co/sandbox/credentialOffer?path=test%2FCredentialOffer2


[DDW-186] Monitor npm dependencies for security using Snyk

This PR checks npm dependencies for vulnerabilities using Snyk.

Runs snyk on dependencies (no vulnerabilities).
Installs snyk as a devDependency.
Adds snyk:test to npm scripts.

Closed because npm audit those all of that already.


Detected blocking call to open inside the event loop

Warning in log starting with HA 2024.6.0b1
Detected blocking call to open inside the event loop by custom integration 'watchman' at custom_components/watchman/utils.py, line 258: for i, line in enumerate(open(yaml_file, encoding="utf-8")): (offender: /config/custom_components/watchman/utils.py, line 258: for i, line in enumerate(open(yaml_file, encoding="utf-8")):), please create a bug report at https://github.com/dummylabs/thewatchman/issues

to add more details, HA 2024.6 adds a check for this type of file I/O happening in the event loop.
Detected blocking call to open inside the event loop by custom integration 'watchman' at custom_components/watchman/utils.py, line 258: for i, line in enumerate(open(yaml_file, encoding="utf-8")): (offender: /config/custom_components/watchman/utils.py, line 258: for i, line in enumerate(open(yaml_file, encoding="utf-8")):), please create a bug report at https://github.com/dummylabs/thewatchman/issues Traceback (most recent call last): File "", line 198, in _run_module_as_main File "", line 88, in _run_code File "/usr/src/homeassistant/homeassistant/main.py", line 223, in  sys.exit(main()) File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main exit_code = runner.run(runtime_conf) File "/usr/src/homeassistant/homeassistant/runner.py", line 188, in run return loop.run_until_complete(setup_and_run_hass(runtime_config)) File "/usr/local/lib/python3.12/asyncio/base_events.py", line 672, in run_until_complete self.run_forever() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 639, in run_forever self._run_once() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1988, in _run_once handle._run() File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run self._context.run(self._callback, *self._args) File "/usr/src/homeassistant/homeassistant/runner.py", line 164, in setup_and_run_hass return await hass.async_run() File "/usr/src/homeassistant/homeassistant/core.py", line 515, in async_run await self.async_start() File "/usr/src/homeassistant/homeassistant/core.py", line 568, in async_start self.bus.async_fire_internal(EVENT_HOMEASSISTANT_STARTED) File "/usr/src/homeassistant/homeassistant/core.py", line 1554, in async_fire_internal self._hass.async_run_hass_job(job, event) File "/usr/src/homeassistant/homeassistant/core.py", line 936, in async_run_hass_job hassjob.target(*args) File "/usr/src/homeassistant/homeassistant/core.py", line 1418, in call self.hass.async_run_hass_job(self.listener_job, event) File "/usr/src/homeassistant/homeassistant/core.py", line 939, in async_run_hass_job return self._async_add_hass_job(hassjob, *args, background=background) File "/usr/src/homeassistant/homeassistant/core.py", line 748, in async_add_hass_job task = create_eager_task( File "/usr/src/homeassistant/homeassistant/util/async.py", line 37, in create_eager_task return Task(coro, loop=loop, name=name, eager_start=True) File "/config/custom_components/watchman/init.py", line 274, in async_on_home_assistant_started parse_config(hass, reason="HA restart") File "/config/custom_components/watchman/init.py", line 351, in parse_config entity_list, service_list, files_parsed, files_ignored = parse( File "/config/custom_components/watchman/utils.py", line 258, in parse for i, line in enumerate(open(yaml_file, encoding="utf-8")):

I am running into the same issue. I had to actually disable the integration as this keeps appearing endlessly in my syslog:
Jun  6 12:19:53 kruse-pi homeassistant[1536]: #033[33m2024-06-06 12:19:53.589 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to open inside the event loop by custom integration 'watchman' at custom_components/watchman/utils.py, line 258: for i, line in enumerate(open(yaml_file, encoding="utf-8")): (offender: /config/custom_components/watchman/utils.py, line 258: for i, line in enumerate(open(yaml_file, encoding="utf-8")):), please create a bug report at https://github.com/dummylabs/thewatchman/issues Jun  6 12:19:53 kruse-pi homeassistant[1536]: Traceback (most recent call last): Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "<frozen runpy>", line 198, in _run_module_as_main Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "<frozen runpy>", line 88, in _run_code Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/src/homeassistant/homeassistant/__main__.py", line 223, in <module> Jun  6 12:19:53 kruse-pi homeassistant[1536]:     sys.exit(main()) Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/src/homeassistant/homeassistant/__main__.py", line 209, in main Jun  6 12:19:53 kruse-pi homeassistant[1536]:     exit_code = runner.run(runtime_conf) Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run Jun  6 12:19:53 kruse-pi homeassistant[1536]:     return loop.run_until_complete(setup_and_run_hass(runtime_config)) Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/local/lib/python3.12/asyncio/base_events.py", line 672, in run_until_complete Jun  6 12:19:53 kruse-pi homeassistant[1536]:     self.run_forever() Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/local/lib/python3.12/asyncio/base_events.py", line 639, in run_forever Jun  6 12:19:53 kruse-pi homeassistant[1536]:     self._run_once() Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1988, in _run_once Jun  6 12:19:53 kruse-pi homeassistant[1536]:     handle._run() Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run Jun  6 12:19:53 kruse-pi homeassistant[1536]:     self._context.run(self._callback, *self._args) Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/local/lib/python3.12/site-packages/aiohttp/web_protocol.py", line 452, in _handle_request Jun  6 12:19:53 kruse-pi homeassistant[1536]:     resp = await request_handler(request) Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/local/lib/python3.12/site-packages/aiohttp/web_app.py", line 543, in _handle Jun  6 12:19:53 kruse-pi homeassistant[1536]:     resp = await handler(request) Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/local/lib/python3.12/site-packages/aiohttp/web_middlewares.py", line 114, in impl Jun  6 12:19:53 kruse-pi homeassistant[1536]:     return await handler(request) Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 92, in security_filter_middleware Jun  6 12:19:53 kruse-pi homeassistant[1536]:     return await handler(request) Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 83, in forwarded_middleware Jun  6 12:19:53 kruse-pi homeassistant[1536]:     return await handler(request) Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 26, in request_context_middleware Jun  6 12:19:53 kruse-pi homeassistant[1536]:     return await handler(request) Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 85, in ban_middleware Jun  6 12:19:53 kruse-pi homeassistant[1536]:     return await handler(request) Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 242, in auth_middleware Jun  6 12:19:53 kruse-pi homeassistant[1536]:     return await handler(request) Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/src/homeassistant/homeassistant/components/http/headers.py", line 32, in headers_middleware Jun  6 12:19:53 kruse-pi homeassistant[1536]:     response = await handler(request) Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/src/homeassistant/homeassistant/helpers/http.py", line 73, in handle Jun  6 12:19:53 kruse-pi homeassistant[1536]:     result = await handler(request, **request.match_info) Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/src/homeassistant/homeassistant/components/http/decorators.py", line 81, in with_admin Jun  6 12:19:53 kruse-pi homeassistant[1536]:     return await func(self, request, *args, **kwargs) Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/src/homeassistant/homeassistant/components/config/view.py", line 130, in post Jun  6 12:19:53 kruse-pi homeassistant[1536]:     hass.async_create_task( Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/src/homeassistant/homeassistant/core.py", line 806, in async_create_task Jun  6 12:19:53 kruse-pi homeassistant[1536]:     return self.async_create_task_internal(target, name, eager_start) Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/src/homeassistant/homeassistant/core.py", line 828, in async_create_task_internal Jun  6 12:19:53 kruse-pi homeassistant[1536]:     task = create_eager_task(target, name=name, loop=self.loop) Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/src/homeassistant/homeassistant/util/async_.py", line 37, in create_eager_task Jun  6 12:19:53 kruse-pi homeassistant[1536]:     return Task(coro, loop=loop, name=name, eager_start=True) Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/src/homeassistant/homeassistant/components/config/script.py", line 28, in hook Jun  6 12:19:53 kruse-pi homeassistant[1536]:     await hass.services.async_call(DOMAIN, SERVICE_RELOAD) Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/src/homeassistant/homeassistant/core.py", line 2722, in async_call Jun  6 12:19:53 kruse-pi homeassistant[1536]:     self._hass.bus.async_fire_internal( Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/src/homeassistant/homeassistant/core.py", line 1554, in async_fire_internal Jun  6 12:19:53 kruse-pi homeassistant[1536]:     self._hass.async_run_hass_job(job, event) Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/src/homeassistant/homeassistant/core.py", line 939, in async_run_hass_job Jun  6 12:19:53 kruse-pi homeassistant[1536]:     return self._async_add_hass_job(hassjob, *args, background=background) Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/src/homeassistant/homeassistant/core.py", line 748, in _async_add_hass_job Jun  6 12:19:53 kruse-pi homeassistant[1536]:     task = create_eager_task( Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/src/homeassistant/homeassistant/util/async_.py", line 37, in create_eager_task Jun  6 12:19:53 kruse-pi homeassistant[1536]:     return Task(coro, loop=loop, name=name, eager_start=True) Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/config/custom_components/watchman/__init__.py", line 287, in async_on_configuration_changed Jun  6 12:19:53 kruse-pi homeassistant[1536]:     parse_config(hass, reason="configuration changes") Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/config/custom_components/watchman/__init__.py", line 351, in parse_config Jun  6 12:19:53 kruse-pi homeassistant[1536]:     entity_list, service_list, files_parsed, files_ignored = parse( Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/config/custom_components/watchman/utils.py", line 258, in parse Jun  6 12:19:53 kruse-pi homeassistant[1536]:     for i, line in enumerate(open(yaml_file, encoding="utf-8")): Jun  6 12:19:53 kruse-pi homeassistant[1536]: #033[0m Jun  6 12:19:53 kruse-pi homeassistant[1536]: #033[33m2024-06-06 12:19:53.602 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to open inside the event loop by custom integration 'watchman' at custom_components/watchman/utils.py, line 258: for i, line in enumerate(open(yaml_file, encoding="utf-8")): (offender: /config/custom_components/watchman/utils.py, line 258: for i, line in enumerate(open(yaml_file, encoding="utf-8")):), please create a bug report at https://github.com/dummylabs/thewatchman/issues Jun  6 12:19:53 kruse-pi homeassistant[1536]: Traceback (most recent call last): Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "<frozen runpy>", line 198, in _run_module_as_main Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "<frozen runpy>", line 88, in _run_code Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/src/homeassistant/homeassistant/__main__.py", line 223, in <module> Jun  6 12:19:53 kruse-pi homeassistant[1536]:     sys.exit(main()) Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/src/homeassistant/homeassistant/__main__.py", line 209, in main Jun  6 12:19:53 kruse-pi homeassistant[1536]:     exit_code = runner.run(runtime_conf) Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run Jun  6 12:19:53 kruse-pi homeassistant[1536]:     return loop.run_until_complete(setup_and_run_hass(runtime_config)) Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/local/lib/python3.12/asyncio/base_events.py", line 672, in run_until_complete Jun  6 12:19:53 kruse-pi homeassistant[1536]:     self.run_forever() Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/local/lib/python3.12/asyncio/base_events.py", line 639, in run_forever Jun  6 12:19:53 kruse-pi homeassistant[1536]:     self._run_once() Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1988, in _run_once Jun  6 12:19:53 kruse-pi homeassistant[1536]:     handle._run() Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run Jun  6 12:19:53 kruse-pi homeassistant[1536]:     self._context.run(self._callback, *self._args) Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/local/lib/python3.12/site-packages/aiohttp/web_protocol.py", line 452, in _handle_request Jun  6 12:19:53 kruse-pi homeassistant[1536]:     resp = await request_handler(request) Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/local/lib/python3.12/site-packages/aiohttp/web_app.py", line 543, in _handle Jun  6 12:19:53 kruse-pi homeassistant[1536]:     resp = await handler(request) Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/local/lib/python3.12/site-packages/aiohttp/web_middlewares.py", line 114, in impl Jun  6 12:19:53 kruse-pi homeassistant[1536]:     return await handler(request) Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 92, in security_filter_middleware Jun  6 12:19:53 kruse-pi homeassistant[1536]:     return await handler(request) Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 83, in forwarded_middleware Jun  6 12:19:53 kruse-pi homeassistant[1536]:     return await handler(request) Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 26, in request_context_middleware Jun  6 12:19:53 kruse-pi homeassistant[1536]:     return await handler(request) Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 85, in ban_middleware Jun  6 12:19:53 kruse-pi homeassistant[1536]:     return await handler(request) Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 242, in auth_middleware Jun  6 12:19:53 kruse-pi homeassistant[1536]:     return await handler(request) Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/src/homeassistant/homeassistant/components/http/headers.py", line 32, in headers_middleware Jun  6 12:19:53 kruse-pi homeassistant[1536]:     response = await handler(request) Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/src/homeassistant/homeassistant/helpers/http.py", line 73, in handle Jun  6 12:19:53 kruse-pi homeassistant[1536]:     result = await handler(request, **request.match_info) Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/src/homeassistant/homeassistant/components/http/decorators.py", line 81, in with_admin Jun  6 12:19:53 kruse-pi homeassistant[1536]:     return await func(self, request, *args, **kwargs) Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/src/homeassistant/homeassistant/components/config/view.py", line 130, in post Jun  6 12:19:53 kruse-pi homeassistant[1536]:     hass.async_create_task( Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/src/homeassistant/homeassistant/core.py", line 806, in async_create_task Jun  6 12:19:53 kruse-pi homeassistant[1536]:     return self.async_create_task_internal(target, name, eager_start) Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/src/homeassistant/homeassistant/core.py", line 828, in async_create_task_internal Jun  6 12:19:53 kruse-pi homeassistant[1536]:     task = create_eager_task(target, name=name, loop=self.loop) Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/src/homeassistant/homeassistant/util/async_.py", line 37, in create_eager_task Jun  6 12:19:53 kruse-pi homeassistant[1536]:     return Task(coro, loop=loop, name=name, eager_start=True) Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/src/homeassistant/homeassistant/components/config/script.py", line 28, in hook Jun  6 12:19:53 kruse-pi homeassistant[1536]:     await hass.services.async_call(DOMAIN, SERVICE_RELOAD) Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/src/homeassistant/homeassistant/core.py", line 2722, in async_call Jun  6 12:19:53 kruse-pi homeassistant[1536]:     self._hass.bus.async_fire_internal( Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/src/homeassistant/homeassistant/core.py", line 1554, in async_fire_internal Jun  6 12:19:53 kruse-pi homeassistant[1536]:     self._hass.async_run_hass_job(job, event) Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/src/homeassistant/homeassistant/core.py", line 939, in async_run_hass_job Jun  6 12:19:53 kruse-pi homeassistant[1536]:     return self._async_add_hass_job(hassjob, *args, background=background) Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/src/homeassistant/homeassistant/core.py", line 748, in _async_add_hass_job Jun  6 12:19:53 kruse-pi homeassistant[1536]:     task = create_eager_task( Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/usr/src/homeassistant/homeassistant/util/async_.py", line 37, in create_eager_task Jun  6 12:19:53 kruse-pi homeassistant[1536]:     return Task(coro, loop=loop, name=name, eager_start=True) Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/config/custom_components/watchman/__init__.py", line 287, in async_on_configuration_changed Jun  6 12:19:53 kruse-pi homeassistant[1536]:     parse_config(hass, reason="configuration changes") Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/config/custom_components/watchman/__init__.py", line 351, in parse_config Jun  6 12:19:53 kruse-pi homeassistant[1536]:     entity_list, service_list, files_parsed, files_ignored = parse( Jun  6 12:19:53 kruse-pi homeassistant[1536]:   File "/config/custom_components/watchman/utils.py", line 258, in parse Jun  6 12:19:53 kruse-pi homeassistant[1536]:     for i, line in enumerate(open(yaml_file, encoding="utf-8")): Jun  6 12:19:53 kruse-pi homeassistant[1536]: #033[0m

So i'm a little worried about this, the owner of this repo has basically no commit history this year and is the only contributor .... Even if a PR was opened with a fix do we think it will be merged?

Maybe it's the perfect moment for a fork that addresses some of the issues and takes care of some PRs.

@mariusthvdb @OzGav @asucrews @johntdyer I think about creating a maintained fork of this repo. Not introducing lots of new features but rather taking care of due maintenance, small fixes and taking care it works with the next versions of HA. There's no activity in here and as @johntdyer already pointed out: this might be a sinking ship. Would be great if we could maintain that ship until maybe @dummylabs re-surfaces and takes over again.
Since I don't want to end like @dummylabs and have to do it all alone and you've either contributed to this project or commented and seem to have dev and/or tech backgrounds: would anybody like to join me in realizing this?

@andreasbrett not 100% sure what i can do, but i am willing to help out

Sorry I am unable to commit to helping as I am busy on other projects.

I just released a beta over on my fork. It fixes this issue. Could you please test it in your HA installations? Find the installation instructions in README and in HACS don't forget to enable "show beta versions".
https://github.com/andreasbrett/thewatchman/releases/tag/v0.6.2-beta0

Sees to be fixed for me using your beta.  Great work!

I've also replaced the old version with your form beta 0.6.2 beta0 and it's working perfectly! Thanks @andreasbrett !

Thanks for picking this up! I’ll surely test drive.
having said that, I am surprised I dit see these loggings…
I did add the line to the manifest some iterations ago forcing to be correctly using HA internals but other than that, I have not a single issue with the original.
let me check more and I’ll report back

Hey @Mariusthvdb could you explain which line you added where?
I'm a bit confused, the manifest looks the same in my installation, like in your example.

Correct, as I stated above. It is no longer there.
Core HA now forces Custom components to use the guarded system, except when they bail out in the manifest.

Correct, as I stated above. It is no longer there.
Core HA now forces Custom components to use the guarded system, except when they bail out in the manifest.

Thank you very much for your feedback. Unfortunately, I'm not good enough to understand everything. I don't have core 2024.6.0 or higher installed yet.
Is there anything I can or must do to avoid getting the error later after the core update?

Tbh: I am not the expert here.
you could check at discord dev channel ask around.
BDraco is the expert on the matter, maybe catch him in the release community post

I just released a beta over on my fork. It fixes this issue. Could you please test it in your HA installations? Find the installation instructions in README and in HACS don't forget to enable "show beta versions".

@andreasbrett I try your beta 0.6.2 beta0 and it's working great on two systems with HA 2024.6.1 Thank you!

@andreasbrett Tried your 0.6.2 beta0 and it fixed the issue for me.
thx a lot for keeping the MUST HAVE integration alive!
PS.: I wonder why this integration is not a standard one.

Tbh: I am not the expert here. Important thing is that

Import executor is on by default now so they don’t need to add that anymore

you could check at discord dev channel ask around.
BDraco is the expert on the matter, maybe catch him in the release community post

Thank you for your response. Maybe I'll just wait a bit. @andreasbrett seems to be on the right track.

Thanks @andreasbrett I swapped from dummylabs' version to your fork and installed the 0.6.2 beta0 and it fixed the issue for me.
Steps I followed to move to the new version:

In HACS, click on thewatchman, three dots in top corner, Remove
Warning about the integration is configured, click Ignore
(HACS now has forgotten about the integration but it still remains in HA)
In HACS, three dots, custom repositories, add https://github.com/andreasbrett/thewatchman
Click thewatchman, Download (actually I ticked beta version and selected the beta)
Restart HA

No reconfiguration required and all working fine

Thank you @andreasbrett for the update to this repo and to @gcoan for the update instructions.
I am using the new (experimental) HACS user interface.
In order to obtain the 0.6.2 beta0 version, I had to 'redownload' the after initially switching to the new repository.
'redownload' gave me the option to enable beta versions and to select 0.6.2 beta0 version

Yes, thank you! This is working great thanks to your time and efforts.
On Tue, Jun 18, 2024 at 21:54 teskanoo @.***> wrote:

Thank you @andreasbrett https://github.com/andreasbrett for the update
to this repo and to @gcoan https://github.com/gcoan for the update
instructions.
I am using the new (experimental) HACS user interface.
In order to obtain the 0.6.2 beta0 version, I had to 'redownload' the
after initially switching to the new repository.
'redownload' gave me the option to enable beta versions and to select
0.6.2 beta0 version
—
Reply to this email directly, view it on GitHub
https://github.com/dummylabs/thewatchman/issues/135#issuecomment-2177374369,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACSZYBOI7ECHGOTR3PAFQ7DZIDQHDAVCNFSM6AAAAABIQES64GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZXGM3TIMZWHE
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Hey @andreasbrett, thank you for your efforts. Hopefully, I’m getting back on track and am ready to maintain this repo. Could you please create a pull request for your fix so that I can incorporate it?

Yep, just wanted to have proper attribution in the code. Anyway, I really appreciate the valuable contribution of @andreasbrett and other guys. Thank you!

Hey @andreasbrett, thank you for your efforts. Hopefully, I’m getting back on track and am ready to maintain this repo. Could you please create a pull request for your fix so that I can incorporate it?

I just created the PR for the "blocking call" fix.

Fix is in the main branch (available in HACS as beta). The new version will be published soon.

Should be fixed in 0.6.2.

thx, for keeping the original watchman repo alive!
PS.: any chance to see this in the core?

any chance to see this in the core?
Don’t believe it’s ready yet. I see several areas for improvement in how watchman should function, particularly:

The standard configuration popup feels too cramped for the numerous configuration options. Having a dedicated panel for configuration (and perhaps reporting) would be beneficial. Every time I attempt to add a new config option, I encounter this issue. However, this requires frontend programming skills, which I don't have at the moment.
The concept of storing a large amount of data in sensor attributes (even though it was an experiment to support custom Lovelace cards). Perhaps creating a separate entity for each detected problem would be a better approach. This would ensure that watchman findings are compatible with most Lovelace cards out of the box. The "repairs" feature is another option here to consider.

well, if anything, I find the current install working very nicely! and I dread the moment you would change to creating repairs for each file Watchman finds..... maybe per category, but not per file, that would be not be a nice user experience at all, aas Ive seen moments in the config where over 70 or so files where either not used or missing etc etc....
this is one of those very useful components that probity will never be in core, so if you ask me, dont strive for that at all. Just make it better!
thanks for doing so!

Thank you for your kind words!

we now have to reload the integration, which is not very UI friendly
actually a rerun of the component
Watchman listens to several events in Home Assistant and should automatically update its sensors when Home Assistant starts and when configuration parts gets reloaded via UI (YAML configuration reloading). I will check it out, may be things have changed since this feature was released.

Sure.
please also see if you can add functionality for changing recorded entities filters.
thats when I noticed .


Implemented buildObjectExplicit for building an xml string from a json object created with explicitChildren

fixed trimming of child text items
implemented that single text nodes wont get trimmed
fixed catching undefined text value
added comments, fixed non cdata values like numbers
added onclosetag and onopentag events

#299

Coverage increased (+0.5%) to 97.429% when pulling deff401077e20575e256cd26b6628cf2ab84ad84 on flodev:master into 7b2a93a605c994a1141b1134810db0dc950a431b on Leonidas-from-XIV:master.

Is it possible to have this functionality soon please? Without proper XML serialization it draws this library unusable for our company's use case.

can this please be merged?
we need this functionality as well

@flodev Hi, Can this be merge soon please?

hi @Leonidas-from-XIV
this PR is really important for us
and causing a bug that the parsing and building are not symmetric
we are using the parsing to get a JSON which we filter based on some criterias
and then we want to use the builder to build the XML again
while using the following options
var options = { preserveChildrenOrder: true, explicitChildren: true, charsAsChildren: true };
if the coverage increased and all tests passed, is there any other objection to merge this PR?

What is blocking is that the branch is currently not mergeable because of conflicts with master.


Find-in-page highlight-box is at wrong y-position in Coway airmega PDF-manual

Attach (recommended) or Link to PDF file here:
https://images-na.ssl-images-amazon.com/images/I/D1SWYNC4nwS.pdf
D1SWYNC4nwS.pdf
Configuration:

Web browser and its version: Firefox Nightly 82.0a1 (2020-09-05)
Operating system and its version: Windows 10
PDF.js version: Not sure; whatever's shipped with Nightly right now
Is a browser extension: not an extension that I manually installed; just the built-in version.

Steps to reproduce the problem:

Load attached PDF
Find-in-page (Ctrl+F) and type "clean".
(optional): Ctrl+G to skip through a few matches

What is the expected behavior?
The text "clean" should be highlighted for each match.
What went wrong? (add screenshot)
The highlighted box is above the text, approximately one line-height away:

Yeah, so I tried to reproduce the bug and it is evident that the y-position is not correct.
This is not a problem with the PDF document itself since the same document selection is rendered correctly in Edge's PDF Viewer. This probably has to do with the y-offset in rendering the selection.

Please assign this issue, I can begin some work on this.

Closing since this got fixed by #12896 and other work.


Added Dutch translation (strings-nl.xml)

Failed to perform pull request.

Related to issue #14, closing.


Unable to make it works

I'm using Sphinx 1.8.5. The build succeed but no api document is generated (nor the base folder). No error or warning, apart from that due to missing api reference files:
WARNING: toctree contains reference to nonexisting document 'api/`
(I replaced the real package name with )
Am I missing something?
this_dir = os.path.abspath('.')
src_dir = os.path.abspath('../src')
sys.path.insert(0, src_dir)

extensions = [
    'jinjaapidoc',
    'sphinx.ext.napoleon',
    'sphinx.ext.autodoc',
    'sphinx.ext.autosummary',
    'sphinx.ext.intersphinx',
    'sphinx.ext.coverage',
    'sphinx.ext.ifconfig',
    'sphinx.ext.viewcode',
    'sphinx_autodoc_typehints',
    'IPython.sphinxext.ipython_console_highlighting',
    'IPython.sphinxext.ipython_directive'
]

templates_path = ['_templates']
source_suffix = '.rst'
master_doc = 'index'

exclude_patterns = ['_build', 'Thumbs.db', '.DS_Store']

# jinja-apidoc
autosummary_generate = True
jinjaapidoc_src = src_dir
jinjaapi_outputdir = os.path.join(this_dir, 'api')

Hm, this package wasn't compatible with newer Sphinx versions. I've released 0.5.0 and tested it on Sphinx 1.8.5 and 2.0.1. Could you try upgrading and check if that fixes the issue, please?
Let me know if it works or not.

I managed to make it work but I have no idea what made the difference lol.
OT question: in your conf.py you set jinjaapi_srcdir to "src". I used the same template for my project, still I had to provide "src/<package_name>". Why is that?


how to set Header in a different row?

Is there a way to set the headers on a diferent row, other than the first?
I'm trying to do this
`var Excel = require('exceljs');
    var workbook = new Excel.Workbook();
    var headers = [
      {header:'Cliente',key:'client_name'  ,width: 18}, // i need something like headerRow:2
      {header:'N° Visitas',key:'visits'  ,width: 10},
      {header:'Visitas Periodo Anterior',key:'visits_old'  ,width: 10},
      {header:'Ultima visita',key:'last_visit',style: { numFmt: 'DD/MM/YYYY HH:mm:ss' },width: 22},
      {header:'Ultima Persona en Visitarlo',key:'device_name'  ,width: 18}
    ];
    var libro  = workbook.xlsx.readFile(template_file)
      .then(function() {
        var worksheet = workbook.getWorksheet(1);
        worksheet.properties.defaultRowHeight = 15;
        worksheet.columns = headers;
        worksheet.addRows(data);

        //row.height=40;
        worksheet.getRow(1).hidden=false;
        worksheet.getRow(2).hidden=false;

        //row.height=40;
        workbook.xlsx.writeFile(output)
          .then(function() {
            callback(null,output);
          });`

I also have same issue.

I've managed to offset the header row by using splice rows set to remove 0 rows and giving it an empty array of the desired amount of rows, just place it after all rows have been added. A similar technique could be applied to columns.
Anything you want to add above the header rows will need to be set directly (not using addRow or addRows, so presumably wont work for a streamed file if the rows are already committed?) Or you could specify it in the array parameter of splice in place of the new Array(offset) parameter
let offset = 3; // to offset by 3 rows
worksheet.spliceRows(1,0,new Array(offset))

#268 276

let offset = 3; // to offset by 3 rows
worksheet.spliceRows(1,0,new Array(offset))

The style of the columns does not move after splice.

The syntax in typescript is
worksheet.spliceRows(1, 0, ...new Array(5))

I wanted my headers to start from 3rd row and 1st-row 1st cell had some metadata,so what I did was:

Duplicated my headers in 3 rows (1,2,3).
worksheet.duplicateRow(1, 2, true); //duplicate header row 2 times with values and style; in row2 and row3

Added metadata in 1st row
 worksheet.getRow(1).values = ['Some meta data'] //Replace row1 headers with "Berry Type";here we pass an array where each index denotes a cells

Removing duplicated headers from 2nd row
worksheet.getRow(2).values = [] //Delete row2 duplicated above in step 1

let offset = 3; // to offset by 3 rows
worksheet.spliceRows(1,0,new Array(offset))

The style of the columns does not move after splice.

I wanted my headers to start from 3rd row and 1st-row 1st cell had some metadata,so what I did was:

Duplicated my headers in 3 rows (1,2,3).
worksheet.duplicateRow(1, 2, true); //duplicate header row 2 times with values and style; in row2 and row3

Added metadata in 1st row
 worksheet.getRow(1).values = ['Some meta data'] //Replace row1 headers with "Berry Type";here we pass an array where each index denotes a cells

Removing duplicated headers from 2nd row
worksheet.getRow(2).values = [] //Delete row2 duplicated above in step 1

And here's my output:
Metadata |   |   |   |
-- | -- | -- | -- | --
  |   |   |   |
header1 | Header2 | header3 | header4 | header5
1 | 2 | 3 | 4 | 5

I wanted my headers to start from 3rd row and 1st-row 1st cell had some metadata,so what I did was:

Duplicated my headers in 3 rows (1,2,3).
worksheet.duplicateRow(1, 2, true); //duplicate header row 2 times with values and style; in row2 and row3

Added metadata in 1st row
 worksheet.getRow(1).values = ['Some meta data'] //Replace row1 headers with "Berry Type";here we pass an array where each index denotes a cells

Removing duplicated headers from 2nd row
worksheet.getRow(2).values = [] //Delete row2 duplicated above in step 1

And here's my output:
Metadata |   |   |   |
-- | -- | -- | -- | --
  |   |   |   |
header1 | Header2 | header3 | header4 | header5
1 | 2 | 3 | 4 | 5

mfahmirukman's answer here https://github.com/exceljs/exceljs/issues/433 worked for me! w/ 1 minor tweak as I commented there too.

@abyss-kp I get a workseet.duplicateRow is not a function error.

@abyss-kp I get a workseet.duplicateRow is not a function error.

Think because you use the WorkbookWriter which implement for stream
try this code instead
// add n row before header
 for (let i = 1; i <= n; i++) {
    worksheet.addRow({});
  }

   worksheet.columns = [
    { header: "ID", key: "id" },
    { header: "NAME", key: "name" },
    { header: "AGE", key: "age" },
  ];

  //remove the defaul header
  // should remove hear before commit data with stream
  worksheet.getRow(1).values = [];

  worksheet.addRow({
    id: "ID",
    name: "NAME",
    age: "AGE",
  });

Sorry for necro..ing (?) the issue, but since spliceRows now accepts rest parameter inserts, new code should look like this:
let offset = 3; // to offset by 3 rows worksheet.spliceRows(1,0,...new Array(offset))


404 error when trying to create issue in repos

Hi
I got the following error when using
Attempting to expand user "user" as a group (may not succeed)
GET https://api.github.com/orgs/blacklabnz/teams/user/members: 404 Not Found []
Creating issue in repo github_account/repo with the following content:
Title: Manual approval required for workflow run<PHONE_NUMBER>:
Respond "approved", "approve", "lgtm", "yes" to continue workflow or "denied", "deny", "no" to cancel.
error creating issue: POST https://api.github.com/repos/github_account/repo/issues: 404 Not Found []
could you please help ?
appreciate this !

Hi same problem here, can some please reply to this issue

Just solved this issue only needed to reads to through documentation
    permissions:
      issues: write

Just solved this issue only needed to reads to through documentation
    permissions:
      issues: write

can you show the code that fixed this issue?

Hi, I solved this issue by adding permissions of maintain to the main team that needs the approval permissions.
in the repo 'setting' tab -> collaborates and teams -> manage access -> add team -> give maintain permissions


[TS migration] Migrate 'PopoverWithMeasuredContent.js' component to TypeScript

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/25053
PROPOSAL:
Tests

Press "+"
Verify that the menu is displayed as expected

[x] Verify that no errors appear in the JS console

Offline tests

QA Steps

Press "+"
Verify that the menu is displayed as expected

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

@eVoloshchak Would you be able to look at it today? This is blocking some other TS issues 🙏

@blazejkustra, sure, will take a look in a couple of hours

@eVoloshchak all comments addressed

Reviewer Checklist

[ ] I have verified the author checklist is complete (all boxes are checked off).
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

[ ] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[ ] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[ ] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[ ] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[ ] If any new file was added I verified that:

[ ] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn't already exist
[ ] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)

[ ] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[ ] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[ ] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

@eVoloshchak PR Reviewer checklist is still failing 🤔

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/mountiny in version: 1.4.19-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/mountiny in version: 1.4.19-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

@pasyukevich @mountiny I am seeing a regression where emoji picker opens as a Modal and not with PopoverWithoutOverlay, the reason we have missed setting the default value for fullscreen to true in this migration which earlier has been done by the defaultModalProps.
https://github.com/Expensify/App/commit/00ae1e641cc5b82396e8a8ba0d465b624ae4d225#diff-66f3b9f7becc9cb3153498f739eb76e698c5a5f333c47912e684f23986452117R28-R42
https://github.com/Expensify/App/blob/8cb48e468ce3c09ada2d58aaae5354ec206104f9/src/components/Modal/modalPropTypes.js#L72-L73
https://github.com/Expensify/App/assets/14358475/572c2e64-49e0-4a7f-b6de-213a3ec62777
To fix we need to pass fullscreen = true, here and pass down this prop to the Popover.
https://github.com/Expensify/App/blob/main/src/components/PopoverWithMeasuredContent.tsx#L35-L37

@Pujan92 I was able to reproduce showed behavior
Follow-upping PR in progress

PR with the fix is open
https://github.com/Expensify/App/pull/33835


 Recommend looking at the original src/index.scss file and redoing the changes to get the styles corrected. You can find the original version here: https://github.com/carbon-design-system/carbon-tutorial/blob/react-step-5/src/index.scss

No updates for 60 days. Closing.


Composer and analytics API added

API for composer history now returns graph
API for plots addded

Hello @nicl-nno! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file test/test_analytics.py:

Line 15:60: W292 no newline at end of file


append src to generated folder when output path is not src folder

check outputfolder is src directory or not, if not, append src directory

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


ios_add2app_life_cycle isn't running anywhere

This test relanded with #49368 but it doesn't seem to be running anywhere.

@chunhtai am I missing something?  Do you need help adding a builder config?

That is weird, I thought it was running a while back.


docs(qwik-city): Add docs for routes rewriting

add details and use cases examples for route rewriting to the related docs
What is it?

[ ] Feature / enhancement
[ ] Bug
[X] Docs / tests / types / typos

Description
Add use case examples to the docs related to route rewriting
Checklist:

[X] My code follows the developer guidelines of this project
[X] I have performed a self-review of my own code
[X] I have made corresponding changes to the documentation
[X] Added new tests to cover the fix / functionality

Thanks @claudioshiver it looks good to me


update Sunset header doc to latest (now as RFC8594)

notes
The Sunset header draft is now published at https://tools.ietf.org/html/rfc8594 (Informational).

Coverage remained the same at 95.876% when pulling 82ed273facf42305692b6435100238a971ffca79 on mt-kelvintaywl:patch-1 into 04825acf05ff940fb61393b3e4a9a33f01243f7d on wework:master.

Coverage remained the same at 95.876% when pulling 82ed273facf42305692b6435100238a971ffca79 on mt-kelvintaywl:patch-1 into 04825acf05ff940fb61393b3e4a9a33f01243f7d on wework:master.


⚠ Samsung has degraded performance

In 6d74276, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2353 ms

Resolved: Samsung performance has improved in 11909c1.


Let GhidraFileChooser's CurrentDirectory can be edit

The PR cannot be accepted in its current form.   This change would require additional tests to document the various use cases that will be supported by having an editable file field.

Actually we don't need to consider this PR, because we can change path by "File name" area.


Add connection message every 5 minutes

Closes #338

I'll give this a whirl today :)

hey, sorry got caught up pairing on other PRs. I'll take a look at this first thing tomorrow morning!


Solutions / How-To Section

Body of the issue
https://github.com/inventree/inventree-docs/issues/211

Have you been able to think any more about this How-To Section?  If you are still open, I would be open to giving it a go.  I have a copy of Help-n-Doc Version: <IP_ADDRESS>6 (x64) Professional Edition.  I use it for the help section on my github.io page.

It is very low on the priorities list for me, feel free to tackle it. The docs are written in mkdocs and located in /docs/docs, maybe take a look at this page to see how it can be written: https://github.com/inventree/InvenTree/blob/master/docs/docs/faq.md

@SparkeyinVA this would be much appreciated! W have very limited dev time, and only a small portion of that does go into documentation!

@matmair @SchrodingersGat , I checked and Help-n-Doc can output a markdown document.  I will work on a few pages in in Markdown and html and share them.  If they are acceptable I will be happy to contribute what I can.

Still important


Wrong type in DurationInMillis

The type of DurationInMillis in Node struct should also be int64 as in the Step struct.
https://github.com/jenkins-zh/jenkins-client/blob/0c9041a612a1bc6047236fc1e3194fc01e33830e/pkg/job/blueocean_type.go#L131
See also:
BluePipelineNode extends BluePipelineSteps and the type of durationInMillis in BulePipelineStep is long.

hi @chengleqi , fair enough. Thanks for finding it. Please feel free to fix it.


Clarify debugging message in express:router:layer

This commit would make the debugging message more intuitive when creating a new Layer. It will display the fn name as well. Eg. express:router:layer new / expressInit instead of express:router:layer new /

Sorry, I think I got confused about the workflow. I would like to close this pr.