chore: apply license headers to all the source files

Summary of Changes
Include a summary of changes then remove this line
Tests
What tests did you add or modify and why? If no tests were added or modified, explain why. Remove this line
Documentation
What documentation did you add or modify and why? Add any relevant links then remove this line
CheckList
Make sure you have checked all steps below to ensure a timely review.

[ ] PR title addresses the issue accurately and concisely. Example: "Updates the version of Flask to v1.0.2"

In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

[ ] PR includes a summary of changes.
[ ] PR adds unit tests, updates existing unit tests, OR documents why no test additions or modifications are needed.
[ ] In case of new functionality, my PR adds documentation that describes how to use it.

All the public functions and the classes in the PR contain docstrings that explain what it does

[ ] PR passes make test

Codecov Report

Merging #116 into master will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #116   +/-   ##
=======================================
  Coverage   74.92%   74.92%
=======================================
  Files          18       18
  Lines         654      654
  Branches       86       86
=======================================
  Hits          490      490
  Misses        135      135
  Partials       29       29

Impacted Files
Coverage Δ

search_service/api/base.py
92.30% <ø> (ø)

search_service/api/dashboard.py
100.00% <ø> (ø)

search_service/api/document.py
80.00% <ø> (ø)

search_service/api/table.py
100.00% <ø> (ø)

search_service/api/user.py
40.00% <ø> (ø)

search_service/config.py
100.00% <ø> (ø)

search_service/exception.py
66.66% <ø> (ø)

search_service/models/base.py
72.72% <ø> (ø)

search_service/models/search_result.py
83.33% <ø> (ø)

search_service/models/tag.py
87.50% <ø> (ø)

... and 8 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 6ae8194...795fc61. Read the comment docs.


Also count the number of sentences written.

On the statistics screen, it would be nice to also count the total number of sentences written within a document/file:

A sentence could be counted every time after a dot (full stop) mark is used .
Unrelated to this a simple note on translation:
Paragraph's should be Paragraphs in English.
Heading's should be written as Headings (without the apostrophe ')

Implemented in v1.3.7. Thanks for contribution!


[SPARK-43293][SQL] __qualified_access_only should be ignored in normal columns

What changes were proposed in this pull request?

This is a followup of https://github.com/apache/spark/pull/39596 to fix more corner cases. It ignores the special column flag that requires qualified access for normal output attributes, as the flag should be effective only to metadata columns.
Why are the changes needed?

It's very hard to make sure that we don't leak the special column flag. Since the bug has been in the Spark release for a while, there may be tables created with CTAS and the table schema contains the special flag.
Does this PR introduce any user-facing change?

No
How was this patch tested?

new analysis test

thanks for the review, merging to master/3.4/3.3!


Fixes for pip wheels

Description
A follow-up PR to #1036 mainly enabling dynamic loading of a different cudnn lib version at runtime.
Type of change

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

Changes
Please list the changes introduced in this PR:

Use dynamic loading for cudnn-frontend using CMake flag.
Add the symbol for cudnn_dlhandle to debug linker issue.
Minor fix in paddle wheel CI test.

Checklist:

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

/te-ci

Pipeline 16916144


Remove spammy return values from instrumented GET requests

GET /metrics would print all the metric values, which whole purpose is to be
used in prometheus metrics, not in loki/tempo.
taker identities are also already collected in a different place.

bors r+


Fix broken links for pachyderm application

Closes: RHOAIENG-10901
Description
Fixes broken links for the dashboard application Pachyderm
How Has This Been Tested?
Tested locally on cluster
Test Impact
no new tests
Request review criteria:

Self checklist (all need to be checked):

[x] The developer has manually tested the changes and verified that the changes work
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has added tests or explained why testing cannot be added (unit or cypress tests for related changes)

If you have UI changes:

[ ] Included any necessary screenshots or gifs if it was a UI change.
[ ] Included tags to the UX team if it was a UI/UX change.

After the PR is posted & before it merges:

[ ] The developer has tested their solution on a cluster by using the image produced by the PR to main

/retest


Add arcolinux_small logo in

Description
Our users have asked if we can provide them with a smaller logo.
Neofetch version
5.0.0
Config file
Line 4954
https://github.com/erikdubois/neofetch/blob/master/neofetch
Verbose log
        "ArcoLinux_small"*)
            set_colors 7 4
            read -rd '' ascii_data <<'EOF'
${c2}          A
         ooo
        ooooo
       ooooooo
      ooooooooo
     ooooo ooooo
    ooooo   ooooo
   ooooo     ooooo
  ooooo  ${c1}<oooooooo>${c2}
 ooooo      ${c1}<oooooo>${c2}
ooooo          ${c1}<oooo>${c2}
EOF

        ;;

If you rather prefer a pull request let me know.

If you rather prefer a pull request let me know.

Sure thing. Do a PR and I'll merge it.

is this ok now?


Denoising Diffusion Probabilistic Models (DDPM)

The Guided Diffusion implementation in #103 is based on a repo from OpenAI that is not maintained anymore. In contrast, lucidrains DDPM implementations are actively maintained and therefore, this PR writes a lightning module for those DDPM models.

I am looking forward to the implementation of DDPM. Recently, I also did a little research on Diffusion Model.
Quite an interesting direction to look at.
I know you have been busy developing so many methods, so take your time!

Codecov Report
Attention: Patch coverage is 91.40625% with 11 lines in your changes are missing coverage. Please review.

Project coverage is 96.04%.

Files
Patch %
Lines

lightning_uq_box/uq_methods/ddpm.py
90.51%
11 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #105      +/-   ##
==========================================
- Coverage   96.15%   96.04%   -0.12%
==========================================
  Files          70       71       +1
  Lines        5152     5280     +128
==========================================
+ Hits         4954     5071     +117
- Misses        198      209      +11

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


Change default value for IPs to <IP_ADDRESS>

Currently the hook defaults the IP related
attributes to empty string. This resulted in
validation error when snap config get is mapped
to corresponding Pydantic model as model expects
IPv4/IPv6 address.
Change the default value to <IP_ADDRESS>
Fix alias name for NetworkConfig ip_address.

I'd prefer to just default the node address - the others should use that if left unset, rather than having to set all three as soon as you wish to provide this value.


DO NOT REVIEW: Add tests to TS actions

Will break this up into smaller PRs.

Closing as I'm never going to merge this.


calendar origin entity not showing friendly name

When adding the origin entity, this doesn't show the Friendly Name. It only shows the entity name described in the configuration.yaml information.

fixed in v3.100.1


provide complex schema examples

we currently don't have a test for the complex file level schemas in datamodels
Maybe we could provide a separte test module that contains functions to generate objects (as pytest fixtures?) to accompany the schemas and be used for tests.
We basically have a script like that allready in scripts/welding_schema.py just need to find a good place to put it

This is a very good idea. That way we do not have to store asdf files in the repo. I'd suggest to take a copy for the text fixture first, as this script is intended for users, right? If not, we should put it in a weldx.tests.fixtures module.

I can give it a shot in PR #328 as I will need a real asdf tree for testing there.

fixed by #328


RGI must only use local database

If the --local flag is not set it will try to write to the rgi package folder, this is incompatible with most deployments.
Please specify a locally installed database in the tools config. This will require a database to be loaded using the RGI Galaxy Data Manager with a predetermined database name.
https://github.com/phac-nml/irida-plugin-amr-detection/blob/a69ae8be45e4a895f79dd6bfaf84c3fe155d28e4/src/main/resources/workflows/0.2.0/irida_workflow_structure.ga#L296
Traceback (most recent call last):
  File "/usr/local/bin/rgi", line 4, in <module>
    MainBase()
  File "/usr/local/lib/python3.6/site-packages/app/MainBase.py", line 81, in __init__
    getattr(self, args.command)()
  File "/usr/local/lib/python3.6/site-packages/app/MainBase.py", line 86, in main
    self.main_run(args)
  File "/usr/local/lib/python3.6/site-packages/app/MainBase.py", line 120, in main_run
    rgi_obj.run()
  File "/usr/local/lib/python3.6/site-packages/app/RGI.py", line 197, in run
    self.create_databases()
  File "/usr/local/lib/python3.6/site-packages/app/RGI.py", line 191, in create_databases
    db_obj.build_databases()
  File "/usr/local/lib/python3.6/site-packages/app/Database.py", line 22, in build_databases
    self.write_fasta_from_json()
  File "/usr/local/lib/python3.6/site-packages/app/Database.py", line 68, in write_fasta_from_json
    with open(os.path.join(self.db, "proteindb.fsa"), 'w') as fout:
PermissionError: [Errno 13] Permission denied: '/usr/local/lib/python3.6/site-packages/app/_db/proteindb.fsa'

https://github.com/arpcard/rgi/issues/155

Alternatively https://github.com/arpcard/rgi_wrapper/pull/16
But the default functionality really shouldn't be depended on


Metadata callback

Problem
Metadata object(exoplayer) was being passed a string to the info listener, you can't access data properly within it.
Solution
Create Noplayer Metadata object and parse Exoplayer metadata object to the noplayer one.
At somepoint we probably need to do the same thing for the android media player
Test(s) added
WIP: write tests for the metadata parser
Paired with
Nobody

Can one of the admins review this PR?

test this please

test this please

test this please


SUTD Archery - Introductory Funshoot

Session Name
SUTD Archery - Introductory Funshoot
Abstract
Get to try out archery in a fun and casual setting with minigames and small prizes!
Student Organisation organising this session
SUTD Archery
Event Format
Physical
Session intent (what to expect)
Participants will not require any prior knowledge of archery. The introductory funshoot sessions will allow participants to try out archery in a fun environment while playing archery games that we don't even conduct during regular sessions, and also to see if they would like to take on archery as a fifth row and attend regular sessions.
Session details
Dates and Times:
-Wednesdays, 22 & 29 Sep, 7-9pm
-Friday, 24 Sep, 3-5pm
Venue: MPH (Have already checked and booked with Yuxin for those timings on those dates)
Number of participants will have to depend on the maximum allowed by OSL after P2HA. Based on latest advisory before P2HA from OSL on 18 Jul, Archery was allowed to continue in groups of 5, up to 30 pax or venue capacity.
Workshop facilitators
Tan Le Xuan - President
Bridget Chua - Vice-President
Muhammad Hazmi - Captain
Ivan Tandyajaya - Logistics
Eliana Setiabudi - Publicity
Sign up link
https://forms.office.com/r/dRxLEvnwEE
Logistical details / Budget Needed
Balloons x 60 ~ $18
Balloon pumps x 3 ~ $6.50
Poker cards x 3 packs ~ $17
Masking tape x 4 rolls ~ $6
Prizes (Candies/Snacks) ~ $28
Total ~ $77
Full budget breakdown - https://docs.google.com/document/d/1cD7uYHCdxgoeTM2iz-krrkP0Js3NzFQVst_Hq-uFki0
Club Email<EMAIL_ADDRESS>

@Sorahawk  , thanks for submitting the event proposal! Could I request that you write a short justification for the amount of money for the session?  i.e why is $50 needed for balloons?
As well as a budget breakdown of what the amount is used for i.e how many balloons and where are you guys going to get it?
A reference would be

Energy club:
Full budget breakdown: https://docs.google.com/document/d/1060jRebU6fGMHcGDlto7qZerriO7lbQb2FR2oEcmnds/edit?usp=sharing
The reason being that It might be a bit difficult for us to help you request for $100 ++ as the average request for funding from other fifth rows are in the range of $50.
Thanks!

@ExtremelySunnyYK thank you for the budget reference, we have shrunk our previous budget and done up an estimated breakdown. Hopefully this is more feasible.

Thank you for the full budget breakdown!
Do note that claims are done via concur with valid receipts required, so giving a clearer breakdown definetely helps to facilitate a smoother process for budget approval. Cheers!

Hi @ExtremelySunnyYK, understood on the claims part. Wanted to check if there's anything else needed on our end because I just saw the 'More information needed' label is still active here? Thanks!

@Sorahawk Thank you. No additional information is needed.

Hi @Sorahawk ,
May I clarify that the 30 pax includes the number of facilitators too? If so, would it be possible to estimate the number of facilitators?
Would be great if you could let me know by today.
Thank you xx

Hi @castlemas, I can estimate that we will have around one group of 5 facilitators, the other 25 can be participants.
Thank you!


Carousel of pet images in home page

Add a carousel of pets in the home page could be featured or recent pets
And if possible include a link when the user clicks on img
Feel free to remove the animation in home.css
Any more ideas are welcome

Hi @redxzeta can you assign this issue to me?

alright


How to install?

I've installed every dependency and their dependencies, but when I run ~/Lampray-1.3.2/setup.sh I get
pete@Pete:~$ ~/Lampray-1.3.2/setup.sh
=> 💁 [ASDF] install with plugins
cut: ./.tool-versions: No such file or directory
==> 💁 [ASDF] install tools
Install plugins first to be able to install tools
How do I fix this?

If you are just trying to run/use Lampray, you should be able to grab the binary/executable from the latest release and run that.
Otherwise I may need more information on how you grabbed the code. It looks like it is not finding the .tool-versions file which should be present. It looks like that portion of the setup script is trying to install cmake, ninja, and act.
If you do already have everything installed, you would either want to run the build.sh script, or run the relevant build commands from the building from source docs.

This is a general issue with how ./ works.
It's a relative path from the PWD(present working directory), which in your case would be ~(your home directory).
The easiest fix is to cd into Lampray-1.3.2 before running the setup.sh instead of running it from your home.


jquery - dependency was not found ???

This dependency was not found:

jquery in ./~/velocity-animate/velocity.js

Velocity is an animation engine with the same API as jQuery's $.animate(). It works with and without jQuery.
Download Velocity, include it on your page, and replace all instances of jQuery's $.animate() with $.velocity().

this plugin doesn't depend on jQuery but it depends on Velocity and hammerjs. velocity is pre included in the build so you will not need to include it in your project.
Will you be able to reproduce this ? so i can take a look.
thanks

I create new project and work perfect.
plz close this issue.
great job!!!


[NEMO-27] Element Wise Block Write

JIRA: NEMO-27: Element Wise Block Write
Major changes:

Changed interface of Partitioner to accept data element (instead of Iterable) and return it's key.

Made OutputWriter write data to BlockStore element-by-element.

When a writer start to write data (element-wisely) to a Block, Block manages Partition according to the writing process. If an element with key which appears first time, the Block create a Partition having corresponding key. If else, the element will be accumulated to existing Partition.
When the writer finish the writing process and declare that the Block is committed, the Block commit all Partitions and prohibit any further write.
The previous partition-level writing method also will be used for inter-BlockStore data movement. (For example, when we spill data from SerializedMemoryStore to LocalFileStore, we have to be able to fetch and write data in units of Partition to avoid extra (de)serialization.)

Minor changes to note:

Adapted DataSkewRuntimePass and it's metric collecting process for the change.

The sizes of Partitions in a Block will be collected when the Block is committed, but not each Partition is written.
The type of partition size metric is changed from Long to Pair<Integer, Long>.

Before this pr, all partitions in HashRange were created by Partitioner even if the Partition is empty. Because of this, List<Long> was enough to represent the integer key and size of each Partition.
However, after this pr, only Partitions with actual data will be created, so the metric have to contain the key of each Partition.

Changed the output files created during ITCases to be deleted even if the test fails.

Disabled the concurrent-write supports in Blocks to avoid element-level locking overhead, as the constraint that only a single thread can write to a Block already exists.

Tests for the changes:

Changed interface of Partitioner

DataTransferTest and all ITCases cover the change.

Element-wise write to BlockStore

Refactored BlockStoreTest to cover this change.

Modified DataSkewRuntimePass

DataSkewRuntimePassTest and MapReduceITCase#testDataSkew cover this change.

Other comments:

At now, Intra-Stage pipelining cannot fully exploit it's advantage because all output data produced by a TaskGroup have to be collected in OutputWriter until the TaskGroup is completed. If we support this element-wise write to BlockStore, these data can be serialized early, and it can reduce memory pressure.

I'm planning to add more changes. I'll reopen this issue after that.

I've updated this pr and it's description. Please have a look @jeongyooneo!

@sanha Please resolve the conflict.

@seojangho Thanks for the review! I addressed your comments.

@sanha Thanks for the work! I've approved the review.


Installation instructions?

I wonder can you describe installation instructions in a user-friendly format?
Thanks!

And maybe Homebrew Cask? :)

First, you need to install CocoaPods by running,
$ sudo gem install cocoapods
And then git clone this repo to local,
$ git clone https://github.com/DanSanche/KubeMonitor
Go to the KubeMonitor folder,
$ cd KubeMonitor
Run pod install to install.

Well, after the pod install, seems you need to run the project in xcode, which I don't install.


Deprecating LoadActionCounts

Deprecating LoadActionCounts and associated methods
@derrickstaten  @Sarkar @aaustin

@sojanpr can you also add this notice to https://github.com/BranchMetrics/Android-Deferred-Deep-Linking-SDK/blob/master/Branch-SDK/src/io/branch/referral/Branch.java#L1274 and https://github.com/BranchMetrics/Android-Deferred-Deep-Linking-SDK/blob/master/Branch-SDK/src/io/branch/referral/Branch.java#L1285
And then I'll add the alternatives to the README at the bottom of this page.

@Sarkar Added deprecation to getTotalActionCount() and getUniqueActionCount()

:+1:

:+1:


Rate Limit Error

I am getting the following error whenever I send a prompt.
╭────────────────────────────── ChatGPT CLI ───────────────────────────────╮
│ [Rate Limit Error] This is caused by API outage. Please try again later. │
╰──────────────────────────────────────────────────────────────────────────╯

I created a new API key but the error persists. I first thought that I reached the maximum tokens you are allowed in the free version, but I can still use ChatGPT in the browser without any problems. Could it be that there are some problems with the API? Are you able to use the CLI tool without any problems?

Yes I can use my API at the moment, but this problem may still be caused by the temporary API limit from the server side. If you want to make sure you have access to your API and it is not caused by the runout of the maximum free trial ($15 previously, $5 currently), you can check your API key profile at https://platform.openai.com/account/api-keys.

Additionally, even if the free trial is out of date (or you have run out of the free $15 or $5 provided by OpenAI), you can still use the ChatGPT from the official web client. If you want to use API in the case that you have run out of all the free trial tokens, you need to pay for it (set up a paid account) or create a new account, rather than generate a new API key.

I have just try with an invalid API key, the error message would be like this:

You exceeded your current quota, please check your plan and billing details.

╭────────────────────────────────────────────────── ChatGPT CLI ───────────────────────────────────────────────────╮
│ [Rate Limit Error] This is caused by API outage. Please try again later.                                         │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯

Do you want to retry now? (y/n):

I hope this can help!

Ah I see, thank you. I didn't know that the web application still works even if you exceeded your price limit.
So it seems like the free trial for API usage expired yesterday. Which is also stated here.

Yes, those who started the ChatGPT in early March would probably have an API expiration date of April 1st. I have mentioned possible solutions to it in my previous comment:

If you want to use API in the case that you have run out of all the free trial tokens, you need to pay for it (set up a paid account) or create a new account, rather than generate a new API key.

And other possible alternatives could be to use the LLaMA models (from 7B to 65B) and corresponding fine-tuned models (many of which are good enough to take the place of GPT3.5-based ChatGPT) provided by opensource communities (for 7B models, Alpaca and Vicuna are famous ones, and there are also many others), but you need GPUs (I remember it needs 4 A100 to do the fine-tuning :sob: ). Though the cost of just running the fine-tuned models would be much more acceptable, it is still unaffordable for me, and I have to continue using the API by OpenAI for many days.

Wow you know quite a lot about this (at least it seems that way to me, who knows rather little haha). Yes I also think using the payed version of ChatGPT is a much more convenient solution (both from the usage and the pricing). Even if you had that much computation power (I have one GPU with 2 VRAM :cry:), you would still need to pay the electricity to run all of those computations.


Update poll_pull_requests.py

:warning: This PR has reached its extended voting window, but it does not have a positive meritocracy review.
Please review: @chaosbot @swizz @amoffat @eukaryote31 @xyproto @hongaar @ad-m @rudehn @plasmapower @md678685 @muchzer


docs(guides): Update watch mode snippet in development guide

Removing the devServer config property from watch mode snippet under Documentation > Guides > Development > Using Watch Mode.

Thanks!


Add textlint and flakeheaven

[X] I have not changed the README.md directly.

Closes #1304

Awesome PR. Thanks for the contribution @AlexandruCardas! 🚀


Error: overlay address changed

I followed the install instruction but failed to start the bee client. It shows error message in log file, please help.
OS: Ubuntu 20.04
May 03 07:30:17 swarm systemd[1]: bee.service: Scheduled restart job, restart counter is at 6144.
May 03 07:30:17 swarm systemd[1]: Stopped Bee - Ethereum Swarm node.
May 03 07:30:17 swarm systemd[1]: Started Bee - Ethereum Swarm node.
May 03 07:30:17 swarm bee[169480]: Welcome to the Swarm.... Bzzz Bzzzz Bzzzz
May 03 07:30:17 swarm bee[169480]:                 \     /
May 03 07:30:17 swarm bee[169480]:             \    o ^ o    /
May 03 07:30:17 swarm bee[169480]:               \ (     ) /
May 03 07:30:17 swarm bee[169480]:    (%%%%%%%)
May 03 07:30:17 swarm bee[169480]:   (     /   /  )%%%%%%%(  \   \     )
May 03 07:30:17 swarm bee[169480]:   (///           ____)
May 03 07:30:17 swarm bee[169480]:      (     /  /(%%%%%%%)\  \     )
May 03 07:30:17 swarm bee[169480]:       (// (%%%%%%%) __)
May 03 07:30:17 swarm bee[169480]:               /(       )
May 03 07:30:17 swarm bee[169480]:             /   (%%%%%)
May 03 07:30:17 swarm bee[169480]:                  (%%%)
May 03 07:30:17 swarm bee[169480]:                    !
May 03 07:30:17 swarm bee[169480]: time="2021-05-03T07:30:17+08:00" level=info msg="version: 0.5.3-acbd0e2"
May 03 07:30:17 swarm bee[169480]: time="2021-05-03T07:30:17+08:00" level=info msg="using swarm network address through clef: 261c85f1bfc2522ecb0d650ddba1207bc04fe5347673a56aa099251ec47e7ad1"
May 03 07:30:17 swarm bee[169480]: time="2021-05-03T07:30:17+08:00" level=info msg="swarm public key 037d08070506bf61e9c207e008c8e4ff14569c767be085a3ac9b687a2ccf30fae6"
May 03 07:30:17 swarm bee[169480]: time="2021-05-03T07:30:17+08:00" level=debug msg="using existing libp2p key"
May 03 07:30:17 swarm bee[169480]: time="2021-05-03T07:30:17+08:00" level=debug msg="using existing pss key"
May 03 07:30:17 swarm bee[169480]: time="2021-05-03T07:30:17+08:00" level=info msg="pss public key 0331c8ca4586df7fa83327fbbaf74a07bebb5416df81dbda160bfb6315adc13419"
May 03 07:30:17 swarm bee[169480]: time="2021-05-03T07:30:17+08:00" level=info msg="using ethereum address 97aec29e61919d3a31b9793373df5010234d17ea"
May 03 07:30:17 swarm bee[169480]: time="2021-05-03T07:30:17+08:00" level=info msg="debug api address: <IP_ADDRESS>:1635"
May 03 07:30:17 swarm bee[169480]: Error: overlay address changed. was d8b25348fdd27dcd1b01daee56930f799e6277486dfcde8c4077fb02d29fa233 before but now is 261c85f1bfc2522ecb0d650ddba1207bc04fe5347673a56aa099251ec47e7ad1
May 03 07:30:17 swarm systemd[1]: bee.service: Main process exited, code=exited, status=1/FAILURE
May 03 07:30:17 swarm systemd[1]: bee.service: Failed with result 'exit-code'.
bee.yaml.txt

You probably changed the clef-signer-enabled value after the node was initialized.  Change it back and all should be fine.

Change clef-signer-enabled value does not help.
After I installed bee client 0.5.3. I just changed
nat-addr: "<IP_ADDRESS>"
network-id: 5
in bee.yaml

when you start the node once an overlay address gets generated using the network ID (there's a default fallback value). Once you change the value and start the node again the network ID change will cause the overlay address to change too.
Due to accounting restrictions we don't allow different overlays with the same underlying accounting database at this point.
To get around this you'll have to either change the network ID or delete the statestore directory of your node.

Can the node delete the statestore or generate a new one automatically in this case?

Can the node delete the statestore or generate a new one automatically in this case?

In your case that might be preferred, but in others, deleting the statestore may be not a great idea (e.g. when you have already accumulated a lot of income on one address).
For now, you will just have to delete the statestore manually.


Document metadata is broken

Bug Report
Description of the problem
I'm trying to add some metadata to my document, e.g. "Subject", as described in documentation:
var doc = new PDFDocument({ info: { Subject: 'My subject' } });
The result PDF contains NUL characters instead of "My subject": http://prntscr.com/nfnx2b
Same for all other properties bu "CreationDate". It can be reproduced even at http://pdfkit.org/demo/browser.html
Your environment

pdfkit version: 0.9.0 (from NPM)
Node version: (built as described here: https://github.com/blikblum/pdfkit-webpack-example)
Browser version (if applicable): Chrome 73.0.3683.103 and Firefox 66.0.3
Operating System: Windows 10

It was fixed in commit https://github.com/foliojs/pdfkit/commit/f52cca92149bde12b4797d483de364bc75817b8a. And we waiting to release 0.9.1 via PR https://github.com/foliojs/pdfkit/pull/941.

Version 0.9.1 released.

I've tested and it works well! Thanks!


Add jaredbhatti as an approver

/ref #10495
This PR adds @jaredbhatti as an approver to k/website.
/assign @Bradamant3

whoops yes ;)
/lgtm
/approve


Revert "Implementation fake response of "WELCOME_TALK""

Reverts DroidKaigi/conference-app-2023#822

We were able to fix the test 🙏


ocenaudio: Strange bug when persisting the settings folder

I've found a strange persist glitch with the ocenaudio app manifest. When installing a version without any previous versions, the settings folder persists fine.
On an update, it still persists the settings folder but creates a settings folder in the settings folder.
Updating again gives you a "Move-Item: Cannot move a file that already exists" error and it doesn't persists the settings folder. Meaning you "lose" your settings.
However the persist is still linked with the previous version.
My version update path with using the scoop app manifest is like this:
Version 3.4.5 (folder persists fine) > Version 3.5.0 (creates a setting folder in the settings folder, but still persists fine) > Version 3.5.1 (Gives the error stated above and doesn't persists the settings folder to the newest version)
This also happens when you re-install the program 3 times.
Is this a glitch in scoop or my app manifest?
This is the error i got (note: the language is Dutch):
Move-Item : Kan geen bestand maken dat al bestaat.
At C:\Users\Melvin\scoop\apps\scoop\current\lib\install.ps1:1239 char:21
+                     Move-Item $source $target
+                     ~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : WriteError: (C:\Users\Melvin...urrent\settings:DirectoryInfo) [Move-Item], IOException
    + FullyQualifiedErrorId : MoveDirectoryItemIOError,Microsoft.PowerShell.Commands.MoveItemCommand

It just happened to me updating vscode-insiders from my bucket.
I updated today at about 2PM and everything worked, but now (11PM) just got this.
(powershell 5.1.17134.228)
Persisting data
Move-Item : Cannot create a file when that file already exists.
At S:\Scoop\apps\scoop\current\lib\install.ps1:1239 char:21
+                     Move-Item $source $target
+                     ~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : WriteError: (S:\Scoop\apps\v...rs\current\data:DirectoryInfo) [Move-Item], IOException
    + FullyQualifiedErrorId : MoveDirectoryItemIOError,Microsoft.PowerShell.Commands.MoveItemCommand


Import error in create_lignin.py

Hi,
I just wanted to bring to your attention that the current version of lignin-kmc does not work with the latest version of the "common_wrangler" dependency.
Specifically this line here: https://github.com/michaelorella/lignin-kmc/blob/master/ligninkmc/create_lignin.py#L15
causes the error
ImportError: cannot import name 'H' from 'common_wrangler.common'

It appears that this is caused by a recent commit to the common_wrangler code: it seems they have renamed the H constant to PLANCK_CONST_JS: https://github.com/team-mayes/common_wrangler/commit/075c1ea2a129f97fe04211b938d761b1958bfd3f

Update: I've created a pull request (#16)  with some basic code that fixes this issue. Feel free to use it or discard it if you want to use an alternate solution.
https://github.com/michaelorella/lignin-kmc/pull/16

Great catch!


Any plans on basing this servant-auth?

Hey there! Thanks for your efforts in writing this library!
I've been reading a bit and noticed servant will probably deprecate it's auth support in favour of haskell-servant/servant-auth. I was wondering if you had any plans to migrate this library to this new auth system.
I'd like to switch to auth-servant since it seems it will become the default authentication mechanism, but it's currently missing support for encrypted cookies (haskell-servant/servant-auth#68). It would be great to see the knowledge contained in this library applied there. On the flip side, one thing servant-auth seems to be doing nicely with their SetCookie implementation is wrapping the response type with cookie headers from the auth primitive, so without relying on a separate Cookied combinator.
Thanks for reading!

Hi,
I'm still not familiar with servant-auth codebase, but if it's possible to migrate to the same API they use, it will be very reasonable step towards the next release! I'll try to do it, so stay tuned!


fix domSel.collapse error in jest

this PR is fixing a type error issue that i encountered when rendering the editor in jest tests.
background
i'm using prosemirror via @tiptap/react. when trying to render the text editor component in tests using testing-library and jest test runner, the following happens:

the first test passes
the second test throws the error: TypeError: domSel.collapse is not a function

this could be an issue in my project's configuration or something on tiptap's side. in that case any suggestions on how to solve or report it would be appreciated.
note that the error only happens if i pass autofocus as true to the Editor's constructor, though i doubt this info will be useful here, as it's likely related to tiptap.

I don't want to merge code that papers over some odd issue in other tools. Did you check what kind of object domSel is when this happens? If it is a DOM Selection (which it kind of should be, since it comes from getSelection()), it will have a collapse method on every browser. It's not null, since its properties will have been accessed before. So something rather weird is happening when you get this error, and it's probably not ProseMirror's fault.


tsrc foreach -g  does not work

Since now there are groups in manifest, it would be great to use group to do a foreach only on a given group. Note it may also apply to other commands (?)

You made good points here!
I think your solution is fine (at least for me)

What about sticking to just iterating over all elements in the specified group?
If you want a restricted list you can still create another group.

nevermind... I agree with your solution. Forgot that some repository could not be checked out.

Note to self: a good way to implement this is to write a filter_repos function of some kind, that would run after get_repos()

By the way, I finally named it filter_repos


St/mcs new

What is still needed is a mechanism to get the packages from github during cnapy installation.

I propose we create a conda package. I can help with that and create a PR in efmtool_link.

I propose we create a conda package. I can help with that and create a PR in efmtool_link.

Could a PyPI regstration be sufficient? conda has so much overhead...

You can do both. I would be pretty happy to get rid of PyPI packages for cnapy.

conda has so much overhead...
Creation and upload of the packages can be automated as for PyPI

I propose we create a conda package. I can help with that and create a PR in efmtool_link.

Thanks, please create the PR so that I can get an impression what is required to make it a conda package.


building xrdp with pulseaudio support for ubuntu 18.04 fails

I have an ubuntu 18.04 VM.
I followed the instructions found here:
https://github.com/neutrinolabs/xrdp/wiki/How-to-set-up-audio-redirection
Everything seems to install correctly until

Finally, let's make. You'll have two .so files module-xrdp-sink.so and module-xrdp-source.so.
cd ~/xrdp/sesman/chansrv/pulse
make PULSE_DIR="~/pulseaudio-11.1"

At that point I get the following error...

:~/xrdp/sesman/chansrv/pulse$ make PULSE_DIR="~/pulseaudio-11.1"
cc -Wall -O2 -I~/pulseaudio-11.1 -I~/pulseaudio-11.1/src -DHAVE_CONFIG_H -fPIC   -c -o module-xrdp-sink.o module-xrdp-sink.c
module-xrdp-sink.c:25:10: fatal error: config.h: No such file or directory
#include <config.h>
^~~~~~~~~~
compilation terminated.
: recipe for target 'module-xrdp-sink.o' failed
make: *** [module-xrdp-sink.o] Error 1

NOTE: the contents of the following directory... there is no config.h file ??

~/xrdp/sesman/chansrv/pulse$ ls
Makefile            module-xrdp-sink-symdef.h  module-xrdp-source-symdef.h
module-xrdp-sink.c  module-xrdp-source.c       README.md

I have tried re-doing this several times just to make sure I didn't skip a step but always the same failure.
Are there files missing from the github ?
Any ideas would be welcome.
Brian

I confirmed it builds. Did you changed enviroment-dependent values to fit yours?

Where's your PULSE_DIR?

BTW, I  didn't say envirnment variables, environment-dependent values.

Sorry.. it's really late here.
I'll recheck any makefiles etc tomorrow.

The config.h being searched during the build is config.h at the top of the pulseaudio source directory. Set the correct PULSE_DIR then everything will work well.

I can confirm this bug.
I have a fresh Ubuntu 18.04 VM and have compiled xrdp from the v0.9.7 tagged release. After following all of the instructions located at xrdp/sesman/chansrv/pulse/README.md, I experience the same error that @bmullan listed above.
cc -Wall -O2 -I~/pulseaudio/pulseaudio-11.1 -I~/pulseaudio/pulseaudio-11.1/src -DHAVE_CONFIG_H -fPIC   -c -o module-xrdp-sink.o module-xrdp-sink.c
module-xrdp-sink.c:25:10: fatal error: config.h: No such file or directory
 #include <config.h>
          ^~~~~~~~~~
compilation terminated.
<builtin>: recipe for target 'module-xrdp-sink.o' failed
make: *** [module-xrdp-sink.o] Error 1

As @shadoxx described it doesn't work when PULSE_DIR includes ~.
I've merged his PR. @bmullan  Can you try the latest devel branch?


GitHub Actions: Transitioning from Node 16 to Node 20

🐞 Describe the bug
Node 16 has reached its end of life, prompting us to initiate its deprecation process for GitHub Actions. Our plan is to transition all actions to run on Node 20 by Spring 2024. We will actively monitor the migration's progress and gather community feedback before finalizing the transition date. Starting October 23rd, workflows containing actions running on Node 16 will display a warning to alert users about the upcoming migration.
https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/
📚 To reproduce
Use the action
💡 Expected behavior
No deprecation warning
🖼 Screenshots
No response
⚙ Environment
1.21.0
📋 Additional context
No response

I hope he hasn't abandoned this

:tada: This issue has been resolved in version 1.21.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


0.2.4

Bugfix on dict.setdefault

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

Comparison is base (a34c15f) 88.95% compared to head (553c635) 89.43%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           master       #8      +/-   ##
==========================================
+ Coverage   88.95%   89.43%   +0.48%
==========================================
  Files           7        7
  Lines        1584     1590       +6
==========================================
+ Hits         1409     1422      +13
+ Misses        175      168       -7

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


Add tests for InputWithIcon

Take screenshots of test results and coverage. If coverage is 100% you can merge this PR.

It was added from the beginning. Maybe it is too small.


Skip costly tests

This PR speeds up runtests-parallel by selectively skipping tests that take a long time to run, but are rarely changed. That means that skipping them is unlikely to cause a problem, but have a large benefit. However, it does mean that rarely — the rate is configurable and defaults to 5% — you will see a failure on CI that you did not see when running gulp runtests-parallel locally.
See the Cost-based sorting section for details.
Jest
I considered a number of other ways to make tests run faster as well, mostly based on the idea that tests that don't touch the code you edit should not need to be run. The best implementation of this is coverage-based testing, but when I tried Jest, its Istanbul-based coverage ran out of memory. I filed a bug and it looks like v8-based coverage is needed, which will take quite a bit of work. We might need to be the ones to do it; in the meantime I want an easy speedup.
I looked at a few recent PRs and guessed that coverage-based testing would cut off 50-80% of our current test time.
Which tests to skip
I considered lots of ways to skip tests. I measured the quality of each method on four criteria:

chance of failure
percent of current test runtime saved
ease of implementation
determinism

A given PR fails if it edits a test that was skipped.
Fourslash
My simplest idea was to just skip fourslash tests when only files in src/compiler are edited, since fourslash takes about 40% of test time. Unfortunately, that fails 7.5% of PRs, and would be useless for non-compiler PRs -- the failure rate would be above 50% for services code. Skipping other test suites besides compiler/conformance wouldn't help because none take that much time.
Cost-based sorting
My next idea was to sort tests from slow to fast, and just skip the slowest ones. But a slow test that catches lots of failures is still valuable. So I decided on Math.log(time% / edit%) as the measure of cost. Every test's runtime is scaled by the number of edits to the test, so slow, useful tests cost less than slow, useless ones.
This saves 38% of test runtime for a 5% chance of failure, or 29% time saving for 2.5% chance of failure.
I thought of some variations that I did not implement for various reasons:
Cost-based sampling
Instead of dropping the most costly tests, you could drop tests randomly based on their cost. But this would result in the most costly tests usually being dropped, and is not deterministic, which would be annoying over many local runs.
Per-user training of cost
It is possible to count only tests that you yourself have edited. If you personally never break fourslash tests (for example), there's no value in running them.
However, intelligently generating the test cost is a little more complex and little less deterministic, and only helps performance a little bit — 2% or so. Instead I included the data as part of the PR, along with the script used to update it.

@weswigham suggested making a // @lowpriority: true comment, which the new script adds (or can be added manually). That gives a little more control relative to the json file, at the price of having a fixed percentage of failure, and another directive that needs to be learned.

After some discussion, I'm going to

Use local perf data from parallel-perf if available and skip nothing if not available.
Move the generated json file to the test folder.

Also, it should be possible to speed up the generation script a lot by switching to nodegit since it reads the git reflog directly. If we want to generate the json file locally and remove it from the repo, it would be a good idea to switch to nodegit.

I tried using local data per-run and it is not stable enough since it changes per run. I'm not confident that bucketisation would make it stable, and that makes the code more fancy, not less. We could generate a combined perf/edit-count file on first run only, but then why not just check in that file as in the current commit.
I timed git log release-2.3...master --stat --pretty=online >foo.txt and it takes 72 seconds on my machine. The current script is less than 3x slower -- it takes 196 seconds. I tested the overhead of process.stdout.readline and it's less than 1% of the total (on the default Gnome terminal at least).
In addition, installing nodegit is very slow on Linux if you have to build from source, so it's not a good choice even as a dev dependency. If we want the 3x speedup, we should just parse git's output directly.
GIven the number of alternatives I've tried that haven't worked out, I'm going to leave the code of this PR as-is, and get Daniel to run the script on his machine so we can get performance numbers based on laptop hardware instead of desktop hardware.


Implement handle, Ping handler

resolved: #72
details:
-Implement New function more detail
-pb message is not implemented exactly yet so implement ping handler simply

I make a mistake in 'commit' so close it and PR it again.


metadata_from_url returns silently on failure

If no metadata can be found, metadata_from_url will return a 'succesful' LookupResult with a JSON-encoded empty list. Should we get an error instead?

In other words, should we have an else: after these lines?
https://github.com/rafguns/doidownloader/blob/50ebc76ac05fbf054a55e87567f15bc18e07eff1/doidownloader/doidownloader.py#L222-L225


Consider making logging more granular

Migrated from GitLab: https://gitlab.com/meltano/sdk/-/issues/335
Originally created by @edgarrmondragon on 2022-02-24 03:15:15

Summary
Leverage Python's dot-separated logger hierarchy to give developers more control over logging behavior and make it more granular:

Behavior: handler, format, level
Source: tap, stream, SDK.

Proposed benefits
Developers can make output more or less verbose for certain streams, etc.
Proposal details

>>> import logging
>>> formatter = logging.Formatter("{asctime} {levelname} {message}", style="{")
>>> handler = logging.StreamHandler()
>>> handler.setFormatter(formatter)
>>> tap_logger = logging.getLogger("tap-example")
>>> tap_logger.addHandler(handler)
>>> tap_logger.setLevel(logging.INFO)  # Display INFO and up
>>> stream_logger = logging.getLogger("tap-example.my_stream")
>>> stream_logger.setLevel(logging.WARNING)  # Display WARNING and up
>>> tap_logger.debug("Info from tap")
>>> tap_logger.info("Info from tap")
2022-02-23 21:10:34,165 INFO Info from tap
>>> stream_logger.info("Info from stream")
>>> stream_logger.warning("Warning from stream")
2022-02-23 21:10:34,175 WARNING Warning from stream

Best reasons not to build
We may not want developers to make their packages to quiet so end-users have useful debugging information by default.

View 2 previous comments from the original issue on GitLab


Create /.autorelabel when switching from disabled

A complete relabeling is required when switching from disabeld to
permissive or enforcing mode, because selinux file attributes
are not written in disabled mode this leaving the files regarding
selinux in an incosistent state.
This resolves #149

thanks!


Resolve DOIs securely

Hello :-)
The DOI foundation recommends this new resolver. Yes, a bit ironic that they would change the URL of their service, but it's now encrypted. Because the old links with the dx subdomain continue to work, there is no urgent need to do anything.
However, I'd hereby like to suggest to follow the new recommendation use the new resolver.
Cheers!

Vielen Dank Katrin, das sieht sehr gut aus!

Bitte schön, und danke fürs mergen!


Add auto-generated docs for forage-android

Description
Please include a summary of the change. Please also include relevant motivation and context. List any dependencies that are required for this change.
Also

Add any other relevant change made on this PR.

Notes

Describe your changes

Tests Added / Updated?

YES or NO. If not, why?

Screenshots

Current dependencies on/for this PR:

main

PR #90   👈

This comment was auto-generated by Graphite.


Migrating from the old CDN to Twitch-JS

I know that I'm not going to be alone in having to remediate the site being gone and cdn returning nothing.
If you read through the issues you will see that development has moved to another repo.
https://github.com/twitch-devs/twitch-js
Inside of dist, select a version and you can then bundle that in your front end payloads.
Then you'll want to realias to TwitchJS or point that to your tmi reference. It works 1:1.
I really hope Schmoopie is okay, I really appreciate this project and what its enabled me in learning and making.

(I am the maintainer of twitch-js)
Thanks for posting this @etisdew etisdew ❤
Yes, twitch-js@v1 is a drop-in replacement for tmi.js@v1. You can use:
<EMAIL_ADDRESS>
twitch-js is community-centric and community-supported. What does that mean? It means that when your PR is merged, you receive collaborator status, and a pre-release build is automatically published to unpkg.com and NPM for the community to use. As long as CI tests pass, and there is at least one collaborator approval (and we already have a 19 collaborators), you can merge your PR. So no more waiting around for the maintainer to fix bugs or add features.
TwitchJS version 2

We have been busy working on version 2 (milestones, docs), a complete rewrite of version 1, featuring:

Aligns with official Twitch IRC documentation
Forward-compatible, low-level, minimally-assertive architecture
Supports Node environments
Supports Browsers
Connect to multiple channels
Chat commands
Rate limiter
... with more features planned.

Submit a PR today.

Is there a better way to casually converse with anyone on the twitch-js team?

Team? 🤣It's just me at the moment with a few transient collaborators passing through.
I tried Gitter, but I found that most of the communication revolved around repeating technical support-related inquires, and since it is just me right now, I do not have time to develop the library, add features, fix bugs, and "maintain" casual conversations unfortunately 😢
Any questions, comments, concerns, problems, bugs, feature requests, or support inquires should be made via a GitHub issue. Here, it can be tracked and searched, and developers or collaborators, transient-or-not, alike can contribute, answer questions, etc. Of course, I will do my best to answer your questions as well.
Perhaps one day when there are a few stable collaborators, we will go back to Gitter or use Discord; but until then, it is not an efficient use of my time 😞


Remove unused draft 02 routes

Suggestion for the commit title: I think the title can be read as modifying daphne_server, in particular removing HTTP routes from the app. I would add a "component" being modified to the commit title so that it's more clear what's being modified. Suggestion:
daphne_worker_test: Remove unused draft02 routes

But the daphne_server is what's being modified :thinking:

Suggestion for the commit title: I think the title can be read as modifying daphne_server, in particular removing HTTP routes from the app. I would add a "component" being modified to the commit title so that it's more clear what's being modified. Suggestion:
daphne_worker_test: Remove unused draft02 routes

But the daphne_server is what's being modified 🤔

You're right, I totally misread. That was sloppy of me, I apologize.


[EXTEND] Remove Composer on Closed Chat

@AlexanderKanakis what did we decide about mobile, do you remember?  I think we do not want this feature in mobile?

@ear-dev Removed feature for mobile

@bhardwajaditya can you review please?  I tested and it looks good to me.  Thanks.

@bhardwajaditya can you review please?  I tested and it looks good to me.  Thanks.

Sure @ear-dev will do that

@ear-dev @AlexanderKanakis Just noticed, this also removes the Print Chat option after chat is closed. Is it expected?

I'll make story to track this and fix.


fix: Adjustment to NavigationGuardWithThis within dts file

According to the documentation here, the "next" argument for navigation guards should be optional. Within the typescript dts file, this is typed as a required argument. Causes issues when attempting to type custom route guards with NavigationGuardWithThis.

The current type is correct for the existing usage. What issue are you experiencing?

Oh sorry about that. After your comment I looked at it again and realized I wasn't thinking about it correctly. I was trying to implement my beforeEach in a way that I could have multiple route guards but wasn't properly passing the arguments to my route guards. Thanks


Fix issue where opening a new view causes the original view still to push

Summary
When using the Global Header (or some other non target=_blank link) to open a new tab, the original tab would also navigate to the new location. This was due to the check for isLoggedIn on the new view, which of course won't be set until the view has finished loading.
This PR stops the rest of the handleBrowserHistoryPush flow from happening after the tab is opened, as when we open a tab we always go directly to where the push link told us to go.
Fixed an issue where opening a new view causes the original view to go to the requested link as well

@devinbinnie where can I find the build for this branch? I checked CircleCI build artifacts but those are empty. How can I test this one?

Successfully building:
https://circleci.com/gh/mattermost/desktop/19227
https://circleci.com/gh/mattermost/desktop/19226
https://circleci.com/gh/mattermost/desktop/19225

@devinbinnie where can I find the build for this branch? I checked CircleCI build artifacts but those are empty. How can I test this one?

@harshilsharma63 I just added the 'Build Apps for PR' label, it should be built within a half hour.

Artifact links:
https://output.circle-artifacts.com/output/job/a74b1234-aa16-4164-b9b4-bf097600d114/artifacts/0/tmp/artifacts/mattermost-desktop-setup-5.1.0-develop.1-win.exe
https://output.circle-artifacts.com/output/job/4fbff71b-7d8e-4696-b3de-2bb5157cb90f/artifacts/0/tmp/artifacts/mattermost-desktop-5.1.0-develop.1-linux-ia32.tar.gz
https://output.circle-artifacts.com/output/job/4fbff71b-7d8e-4696-b3de-2bb5157cb90f/artifacts/0/tmp/artifacts/mattermost-desktop-5.1.0-develop.1-linux-x64.tar.gz
https://output.circle-artifacts.com/output/job/14aa15c9-384f-4a73-b0fc-e79ff79f4b11/artifacts/0/tmp/artifacts/mattermost-desktop-5.1.0-develop.1-mac-arm64.dmg
https://output.circle-artifacts.com/output/job/14aa15c9-384f-4a73-b0fc-e79ff79f4b11/artifacts/0/tmp/artifacts/mattermost-desktop-5.1.0-develop.1-mac-x64.dmg


Translate 1 line to Italian

Hi, I need help to translate https://github.com/Zenrac/watora-translations/blob/c134f52bef66fc6726e301aba98564800818c5f9/i18n/italian.json#L435 (the end of the line) to Italian can someone help ?
A role called DJ is giving DJ permissions by default

I am on it.

Can someone check the PR ?

#56 closes this


not working well with MobX and MobX persist

I integrate MobX, Mobix-persist and react-jsonschema-form to save my form data in localStorage. My form works fine in first execution but after fill form and submit (save data to mobx store) my app crashed. I don't know why but I git this error message on console:
Warning: Failed prop type: Invalid prop `formData` of type `object` supplied to `ArrayField`, expected `array`.
    in ArrayField (created by SchemaField)
    in SchemaField (created by ObjectField)
    in fieldset (created by DefaultObjectFieldTemplate)
    in DefaultObjectFieldTemplate (created by ObjectField)
    in ObjectField (created by SchemaField)
    in div (created by DefaultTemplate)
    in DefaultTemplate (created by SchemaField)
    in SchemaField (created by Form)
    in form (created by Form)
    in Form (at HeaderForm.js:116)
    in div (created by Paper)
    in Paper (created by WithStyles(Paper))
    in WithStyles(Paper) (at HeaderForm.js:115)
    in div (created by Grid)
    in Grid (created by GridWrapper)
    in GridWrapper (created by WithStyles(GridWrapper))
    in WithStyles(GridWrapper) (at HeaderForm.js:114)
    in div (created by Grid)
    in Grid (created by GridWrapper)
    in GridWrapper (created by WithStyles(GridWrapper))
    in WithStyles(GridWrapper) (at HeaderForm.js:113)
    in div (at HeaderForm.js:112)
    in HeaderForm (created by WithStyles(HeaderForm))
    in WithStyles(HeaderForm) (created by Route)
    in Route (at Main.js:13)
    in Switch (at Main.js:10)
    in main (at Main.js:9)
    in Main (at ClippedDrawer.js:66)
    in main (at ClippedDrawer.js:64)
    in div (at ClippedDrawer.js:43)
    in ClippedDrawer (created by WithStyles(ClippedDrawer))
    in WithStyles(ClippedDrawer) (at App.js:17)
    in div (at App.js:16)
    in App (at index.js:11)
    in Router (created by BrowserRouter)
    in BrowserRouter (at index.js:10)
__stack_frame_overlay_proxy_console__ @ index.js:2178
printWarning @ warning.js:33
warning @ warning.js:57
checkPropTypes @ checkPropTypes.js:52
validatePropTypes @ react.development.js:1171
createElementWithValidation @ react.development.js:1268
SchemaFieldRender @ SchemaField.js:237
render @ SchemaField.js:309
finishClassComponent @ react-dom.development.js:7873
updateClassComponent @ react-dom.development.js:7850
beginWork @ react-dom.development.js:8225
performUnitOfWork @ react-dom.development.js:10224
workLoop @ react-dom.development.js:10288
callCallback @ react-dom.development.js:542
invokeGuardedCallbackDev @ react-dom.development.js:581
invokeGuardedCallback @ react-dom.development.js:438
renderRoot @ react-dom.development.js:10366
performWorkOnRoot @ react-dom.development.js:11014
performWork @ react-dom.development.js:10967
batchedUpdates @ react-dom.development.js:11086
batchedUpdates @ react-dom.development.js:2330
reactionScheduler @ mobx.module.js:3448
runReactions @ mobx.module.js:3424
endBatch @ mobx.module.js:2895
endAction @ mobx.module.js:947
executeAction @ mobx.module.js:914
res @ mobx.module.js:902
onChange @ HeaderForm.js:121
(anonymous) @ Form.js:64
run @ setImmediate.js:40
runIfPresent @ setImmediate.js:69
onGlobalMessage @ setImmediate.js:109
postMessage (async)
registerImmediate @ setImmediate.js:120
setImmediate @ setImmediate.js:27
setState @ utils.js:760
Form._this.onChange @ Form.js:62
(anonymous) @ ObjectField.js:72
(anonymous) @ ArrayField.js:305
(anonymous) @ ObjectField.js:72
_onChange @ BaseInput.js:40
callCallback @ react-dom.development.js:542
invokeGuardedCallbackDev @ react-dom.development.js:581
invokeGuardedCallback @ react-dom.development.js:438
invokeGuardedCallbackAndCatchFirstError @ react-dom.development.js:452
executeDispatch @ react-dom.development.js:836
executeDispatchesInOrder @ react-dom.development.js:858
executeDispatchesAndRelease @ react-dom.development.js:956
executeDispatchesAndReleaseTopLevel @ react-dom.development.js:967
forEachAccumulated @ react-dom.development.js:935
processEventQueue @ react-dom.development.js:1112
runEventQueueInBatch @ react-dom.development.js:3607
handleTopLevel @ react-dom.development.js:3616
handleTopLevelImpl @ react-dom.development.js:3347
batchedUpdates @ react-dom.development.js:11082
batchedUpdates @ react-dom.development.js:2330
dispatchEvent @ react-dom.development.js:3421

ArrayField.js:406 Uncaught TypeError: formData.map is not a function
    at ArrayField.renderNormalArray (ArrayField.js:406)
    at ArrayField.render (ArrayField.js:371)
    at finishClassComponent (react-dom.development.js:7873)
    at updateClassComponent (react-dom.development.js:7850)
    at beginWork (react-dom.development.js:8225)
    at performUnitOfWork (react-dom.development.js:10224)
    at workLoop (react-dom.development.js:10288)
    at HTMLUnknownElement.callCallback (react-dom.development.js:542)
    at Object.invokeGuardedCallbackDev (react-dom.development.js:581)
    at invokeGuardedCallback (react-dom.development.js:438)
    at renderRoot (react-dom.development.js:10366)
    at performWorkOnRoot (react-dom.development.js:11014)
    at performWork (react-dom.development.js:10967)
    at batchedUpdates (react-dom.development.js:11086)
    at batchedUpdates (react-dom.development.js:2330)
    at reactionScheduler (mobx.module.js:3448)
    at runReactions (mobx.module.js:3424)
    at endBatch (mobx.module.js:2895)
    at endAction (mobx.module.js:947)
    at executeAction (mobx.module.js:914)
    at data.res (mobx.module.js:902)
    at Object.onChange (HeaderForm.js:121)
    at Form.js:64
    at run (setImmediate.js:40)
    at runIfPresent (setImmediate.js:69)
    at onGlobalMessage (setImmediate.js:109)

Sorry it's from my side.


use with jquery

Hi,
I have a jquery object selected, when I use dragula I get an error.
In the simplest of forms here what my code looks like:
var contentarea = jQuery(".contentarea");
dragula(contentarea);

doing this give me an error:
Uncaught TypeError: e.addEventListener is not a function

I'm not a pro at js or jquery, I must be doing something wrong. Is there a guide to using Dragula on jquery elements / selected objects.

Try this, maybe:
var contentarea = jQuery(".contentarea")[0];
dragula(contentarea);

Thanks ... I'll give it a try. ... makes sense :)

Does this make sense?
var contentarea = $('.contentarea')[0] selects the first item in an array right? but what if you have multiple contentareas and want to use them all for drag and drop?

$('.contentarea')[0] retrieves the javascript object directly to use it with this library.
You would do this, if I understood you correctly (not tested):
var contentarea1 = $("#contentarea1")[0];
var contentarea2 = $("#contentarea2")[0];
var contentarea3 = $("#contentarea3")[0];
dragula([contentarea1, contentarea2, contentarea3]);

you could just use map...
var lists = $('.some-selector').map(function(){ return this; }).get();
// then
dragula(lists);


Missing thumbnailPath when calling contacts with getContactsMatchingString

When i use getContactsMatchingString it misses thumbnailPath in its response. Is this a known issue?

what platform are you seeing this? It's known on android https://github.com/rt2zz/react-native-contacts/issues/223


Support for 1.10 why the drop?

Curious as to the drop in support for 1.10

We follow the support calendar of Django: https://www.djangoproject.com/download/


git fail

你好  git clone --recursive 报如下错误：
ssh: Could not resolve hostname github.com:jbwang1997: Name or service not known
fatal: Could not read from remote repository.

你好 git clone --recursive 报如下错误： ssh: Could not resolve hostname github.com:jbwang1997: Name or service not known fatal: Could not read from remote repository.

已解决 谢谢


add a factory to create all aws entity providers

:heavy_check_mark: Checklist

[ ] Added tests for new functionality and regression tests for bug fixes
[x] Added changeset (run yarn changeset in the root)
[ ] Screenshots of before and after attached (for UI changes)
[ ] Added or updated documentation (if applicable)

just going to close this because the commit has gotten confused a bit.


js not working in production

Changing models doesn't change the inputs in production? Maybe a static files issue.

Indeed, was a static files issue. Fixed now.


Configure FHIR Version

This PR supports selecting the FHIR version in the Configuration modal for SUSHI to use. Only R4 and R4B are supported because they are the only official FHIR versions that are on packages.fhir.org at the moment. Eventually R5 will make it there, and it can be supported in FSH Online at that time.
The configuration for FHIR version should get shared and reloaded when using a "Share FSH" link.

@cmoesel  and @mint-thompson - I found and fixed a bug in this branch, so I think this would benefit from a re-review. The issue was that I forgot to include a default FHIR version to use and load when running GoFSH. I noticed this bug when I was converting one instance to FSH. No FHIR definitions were loaded, so the resource it was an instance of could not be found, and no FSH rules were being created. I had moved the place where we choose a FHIR version to load out of the functions called in loadAndCleanDatabase and into the runSUSHI and (now) runGoFSH so we can properly load the configured version.
In doing this, I also realized that the dependencies we passed into GoFSH weren't formatted properly, but things were working fine because of how we re-parse things later on. I ended up fixing it now because I saw it was wrong and fixing it made the logic for adding the configured FHIR version easier.
One other thing I wanted to call out after looking at this more - when you run GoFSH, it'll use your configured FHIR version or figure out a default version. However, once it does, it'll load that FHIR version into the configuration modal, even if you didn't explicitly pick a version. I remember thinking this was okay when I originally implemented this, but wanted to make sure you both agreed.

Also, I added a .tools-version file. I think we should update the Node version this uses eventually, but I figured I'd at least include what we're using for now.

The issue was that I forgot to include a default FHIR version to use and load when running GoFSH.

I swear I had tested this and it worked! Maybe the FHIR definitions were already loaded and I didn't fully refresh or something... But I did think of this; I just apparently was really bad at actually testing it!

it'll load that FHIR version into the configuration modal, even if you didn't explicitly pick a version.

Yeah, I think that's probably good -- because if it's R5, you should be able to convert to FSH and then convert to JSON (roundtrip). If it didn't remember the FHIR version in the config, then the convert to JSON might use the wrong version.


Infracost comment don't include per-project path breakdown

First of all, kudos for a great tool!
I'm having an issue presenting per-project path price breakdown. Currently, the pricing table looks as follows:

💰 Infracost estimate: monthly cost will not change

Project
Previous
New
Diff

All projects
$45
$45
$0

3 projects have no cost estimate changes.

With following infracost.yml config:
version: 0.1

projects:
  - path: environments/common
    name: Common
  - path: environments/staging
    name: Staging
  - path: environments/production
    name: Production

I would expect the pricing table to have per configured project price breakdown:

💰 Infracost estimate: monthly cost will not change

Project
Previous
New
Diff

Common
$5
$5
$0

Staging
$11
$11
$0

Production
$29
$29
$0

3 projects have no cost estimate changes.

Is this a bug or I'm missing something?
Thanks

@lvkins I'll close this issue but can you please look at the two proposed solutions in https://github.com/infracost/infracost/issues/1538 and add a comment there with your thoughts?


Various cleanups to the ABI handling code

I originally did these in the process of adding exception support to Cranelift, but I've extracted it out that branch and rebased it as these changes should be less controversial and it will help with rebasing the exception support branch in the future.

I'm excited to take a look next week if nobody else gets to this first!

I tried to review this and got kind of lost. I really appreciate that there are nicely separated commits, but I think this would be easier to review if those were fully separate PRs, if that's not too much trouble? It would be especially helpful if you can explain more about the motivation for each change in the commit/PR description.

Split out https://github.com/bytecodealliance/wasmtime/pull/8903. I will rebase this PR once it merges.

Rebased


New version?

Hello. Is there a timeline for a new release with updated Chromium? Latest is from Oct 30, 2022, right?
Thanks for the best version of Chrome for Android!

@kiwibrowser

Chromium is now on 112, Kiwi still on 107. Is Kiwi project still alive?

This just breaks my heart... :tired_face:
~Ibuprophen

For info, for now the latest version of Kiwi is 110. (which is the latest stable version of Chrome, 110 was released a week ago by Google) so just wait a bit and you'll see it in the store / GitHub.
Also, 112 is not even in beta, it will be released in April 2023 by Google only, so normal.
Just wait a bit til it's deployed everywhere

nice to hear that. Btw, I checked on Google Play and it's still on 107

@kiwibrowser, thank you very much for your time and response in this much needed clarification. :smiling_face_with_three_hearts:
~Ibuprophen

[...] the latest stable version of Chrome, 110 was released a week ago by Google [...]

It was released on February 1, which is almost 3 week ago.

[...] Wait a bit [...]

Sure, by that time 111 will be released.

How to download the 110 version?

For info, for now the latest version of Kiwi is 110. (which is the latest stable version of Chrome, 110 was released a week ago by Google) so just wait a bit and you'll see it in the store / GitHub. Also, 112 is not even in beta, it will be released in April 2023 by Google only, so normal.
Wait a bit til it's deployed everywhere and everything will be there like usual as I'm actively working on it :)

那什么时候能发布新版本呢？我们非常期待！
So when did you send the lastest version to the Github or the Google Play ,there are so many people   waiting for your's update!

Hey @kiwibrowser where can I find that version? I have the last one from Google play and It's v107. Also I took a look to the releases page and the last one is from October 30th 2022. Thanks 🙂

For info, for now the latest version of Kiwi is 110. (which is the latest stable version of Chrome, 110 was released a week ago by Google) so just wait a bit and you'll see it in the store / GitHub. Also, 112 is not even in beta, it will be released in April 2023 by Google only, so normal.
Wait a bit til it's deployed everywhere and everything will be there like usual as I'm actively working on it :)

What is the current ETA for this release please?
It has been almost a month since your post and 112b will be releasing in a few weeks as you said and we're still using 107.

@kiwibrowser
What prevents you from publishing the new version here on the githab?
If you update your browser every six months, it will die. Think about it.
I also recommend checking out the version of Telegram on their website. This version is updated bypassing the Play Market.

https://github.com/kiwibrowser/src.next/issues/813#issuecomment-1465291985

I find all of these comments extremely interesting due to the fact that I've downloaded & installed the latest 'pre-release' that's showing here in github on my android phone that's currently running version 12 of android and in the 'about' area in the kiwi browser settings it's showing the following: Kiwi Browser 107.0.5304.75 , also on that same page it's also showing some information concerning my current android operating system (12) as well as the model of phone LM-G900 Build/SKQ 1.211103.001 . I'm really perplexed now as to how some users are reportedly using version 110 of the kiwi browser ?

I just downloaded 111, thanks for releasing it @kiwibrowser

@kiwibrowser Thank you for updating. Very nice!

How to download the 110 version?

link：https://juhaoyang.xyz/web/chrome.php


Allow templates to snap (to resources)

Description
When you try to build an extractor or a hydrocarbon plant your build preview will snap to the resource deposit. This radius of behavior can be changed via the console commandui_ExtractSnapTolerance .
When you enable a template preview via SetActiveBuildTemplate the snap behavior is disabled, even though the build mode is still set to an extractor or a hydrocarbon plant.
Suggested change
Do not disable the snap behavior. The snap behavior should still apply using the context of the unit that you entered build mode for, unrelated to the units in the template.
What we can do with it
This would allow us to extend the Context based templates feature. By allowing snapping to work with build templates it will be easier to place down templates that include extractors, storages and even fabricators.

Do we close this? Or hydro snap is needed too? :D

@4z0t if you use closing keywords in the pull request then the issue is linked and closes automatically when the pull request is merged in


Fix reconcile trigger for FlashSystemCluster owned objects

Signed-off-by: Tal Yichye<EMAIL_ADDRESS>

 investigate msg "FlashSystemCluster resource was not found" - check setupWithManager method -whether watchers are required


Review and update proxy notification emails

Ensure proxy emails are being triggered int he correct circumstances, and the copy is clear.

Done.


Upload csv to existing clickhouse is not supported

superset does not support uploading csv to a table that does not exist in clickhouse because clickhouse must specify the engine when creating the table.
But why doesn't it support upload csv to a table that already exists in clickhouse?

This is due to the Superset using pandas to upload CSV instead of using an external table(like Hive or other DB). refer to link.

Is there a list of DBs that support upload csv now?

@LuPan2015 that list doesn't exist unfortunately but I'm hoping the community will create one soon!

@shreesham pining you here since you're both a resident clickhouse SME, and also perhaps capable of helping to build some documentation around database/CSV upload compatibility.

I think this was resolved, so I'll close it. We also have a table of database driver compatibilities... not sure if CSV upload support can easily be made into a new row there (cc @betodealmeida)


Adding a note to Usage section to recommend using java 1.8

Adding a note to Usage section to recommend using java 1.8 for a seamlessly experience.
It fails if you have java 11 set by default.

This work is incorporate into the next release


React Content Query WebPart : Fields with spaces in their internal names not working

Category

[ ] Question
[x] Bug
[ ] Enhancement

Expected or Desired Behavior
When using the React Content Query WebPart, displaying a field that has spaces in its internal name should render the field value just like a normal field.
Observed Behavior
When using the React Content Query WebPart, displaying a field that has spaces in its internal name (which are automatically replaced with "x0020" by SharePoint), the value is of the field is displayed as blank.
Steps to Reproduce

Create a field called "MyTestField"
Create a field called "My Test Field"
Select both fields using the Content Query WebPart
The field using spaces should render a blank value

It looks like either the REST api (responsible for executing the CAML query) or Handlebars (the templating engine) doesn't like the underscore in the internal name. I will take a look at this issue tonight and submit a pull request accordingly.

Bug is now fixed, added the fix to pull request #313 that should soon be merged.
The bug was due to a really odd behavior that the REST API does with fields that have spaces in their internal names. As we know, a field created with the display name My Field will generate the internal name My_x0020_Field since SharePoint replaces spaces by _x0020_. So far this is all good, but it gets uglier when executing a CAML query using the REST API. For that same field, the API will let you get the field value using the matching internal name My_00x20_Field which is expected, but for getting the htmlValue and textValue, you have to use the following name : My_x005f_x0020_x005f_Field
So the REST API basically replaces all occurences of 00x20 by x005f_x0020_x005f. I fixed it by changing line 549 of ContentQueryService.ts to the following :
let spacesFormattedName = viewField.replace(new RegExp("_x0020_", "g"), "_x005f_x0020_x005f_");

normalizedResult[viewField] = {
    textValue: result.FieldValuesAsText[spacesFormattedName],
    htmlValue: result.FieldValuesAsHtml[spacesFormattedName],
    rawValue: result[viewField] || result[viewField + 'Id']
};

@gurleen23. you can now wait for pull request #313 to be merged, or you can download the latest version on the dev branch of my fork if you don't want to wait. Thanks for the input!
@VesaJuvonen, you can close this issue as soon as pull request #313 is merged. Thanks!

Forgot to close this issue. Fixed since PR #313.


Performance issue with GraphRag on large file processing (7GB) – slow load time and verb function not being triggered

I am using GraphRag to process a large file (~7GB). While the processing works fine for smaller files (in MB range), the workflow experiences significant delays when handling the larger file. The file takes a long time to load, and after over an hour, the workflow hasn't reached the verb's execution.
Here are the details of the issue:
Small File Processing:

Small files load quickly and the verb functions are called as expected.

Large File Processing:

Loading a ~7GB file takes a very long time, and after one hour of waiting, the verb function (nomic_embed) has not been called.

System specs:

I am using a machine with 128 GB of RAM.

Although the verb function is not being called for larger files yet, I would also like to ask about optimizing performance for large file processing. Here's the relevant code snippet I am using:
import logging
from enum import Enum
from typing import Any, cast
import pandas as pd
import io
from datashaper import (
    AsyncType,
    TableContainer,
    VerbCallbacks,
    VerbInput,
    derive_from_rows,
    verb,
)
from graphrag.index.bootstrap import bootstrap
from graphrag.index.cache import PipelineCache
from graphrag.index.storage import PipelineStorage
from graphrag.index.llm import load_llm
from graphrag.llm import CompletionLLM
from graphrag.config.enums import LLMType

@verb(name="nomic_embed")
async def nomic_embed(
    input: VerbInput,
    cache: PipelineCache,
    storage: PipelineStorage,
    callbacks: VerbCallbacks,
    column: str,
    id_column: str,
    to: str,
    async_mode: AsyncType = AsyncType.AsyncIO,
    num_threads: int = 108,
    batch_size: int = 150000,
    output_file: str = "embed_results.parquet",
    **kwargs,
)

I am using the num_threads and batch_size parameters to parallelize the nomic_embed verb for reducing processing time of large files.
Are there any recommended approach or any additional parameters I should consider for processing large files with GraphRag?

When building the graph, the most time-consuming part seems to be accessing the LLM. Even though the code thoughtfully uses asynchronous methods, the time consumption is still significant. I attempted to modify the code to batch mode for the LLM, but the data involves multiple layers of API calls, making it difficult to implement. I’m curious whether the size of the data used by the publisher for experiments is only for laboratory mode.


I use v0.7.8 and version not support async/await, because you upgrade new version?

A clear and concise question.
Environment:

OS and version:
Node.js version:
broken-link-checker version:

This doesn't make sense to me. Feel free to clarify.


lxd/storage/drivers: Add a reverter stage for failed VM snapshot with LVM backend

closes: #11431

Great thanks! How did u come across it?

I'm a bit confused, did you experience a problem that caused you to look into this?

OK makes sense thanks. Although looking at the original error:

Error: Error deleting storage volume: Error removing LVM logical volume: Failed to run: lvremove -f /dev/vmpool127383/virtual-machines_<vm_name>.block: exit status 5 (Logical volume vmpool127383/virtual-machines_<vm_name>.block in use.)

I don't see how removing the mount path is going to help with that. Thats not to say its not useful still, but I don't think it will fix the issue (or worse mask it).

@stgraber do you have any ideas on how to approachh this one ? Before calling lvcreate here lxd/storage/drivers/driver_lvm_utils.go:line 418, where do we check that we have enough storage resources before creation the volume ?

@gabrielmougard the fix here isnt to check for sufficient capacity (lvm will do that for you by failing). The fix needed is to properly clean up on error.

@tomponline right. I see that there is a removeLogicalVolume in the reverter but it's being added after the lvcreate command so it should not be executed by revert.Fail(). Could it be part of the problem ?

So looking at that function in more detail, the call to:
_, err = d.createLogicalVolumeSnapshot(d.config["lvm.vg_name"], parentFSVol, fsVol, true, d.usesThinpool())

Is the last call in that function, so there's no need to add a revert for it (it either succeeds and the function is done or it fails and would never need the revert).
I don't think we are yet clear on the actual problem, and thus we don't know how to go forward with the fix.
Please can you reproduce the error and then show me the output of sudo lvs and mount on your system when the snapshot fails and when you cannot delete the instance. Thanks

@tomponline it's strange... I can't reproduce the bug. The described scenario works just fine now (I'm on LXD 5.11) :
lxc storage create pool1 lvm size=12GiB lvm.use_thinpool=false
# Storage pool pool1 created

lxc init images:ubuntu/jammy v1 --vm -s pool1
# Creating v1 (OK)

lxc config device set v1 root size.state=1GiB
# OK

lxc snapshot v1 snap0
# Error: Create instance snapshot: Error creating LVM logical volume snapshot: Failed to run: lvcreate -n virtual-machines_v1-snap0 -s /dev/pool1/virtual-machines_v1 --setactivationskip y -l 100%ORIGIN -pr: exit status 5 (Insufficient suitable allocatable extents found for logical volume virtual-machines_v1-snap0.)

lxc delete v1
# OK => this time it works...

##########################
# Here is the output of `sudo lvs`

sudo lvs
#  LV                        VG    Attr       LSize   Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
#  virtual-machines_v1       pool1 -wi-ao---k 100.00m
#  virtual-machines_v1.block pool1 -wi-ao---k  10.00g

########################
# Here is the output of `mount`

mount

# sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
# proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
# udev on /dev type devtmpfs (rw,nosuid,noexec,relatime,size=15974468k,nr_inodes=3993617,mode=755,inode64)
# devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
# tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=3203468k,mode=755,inode64)
# /dev/nvme0n1p2 on / type ext4 (rw,relatime,errors=remount-ro)
# securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
# tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,inode64)
# tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k,inode64)
# tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755,inode64)
# cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime)
# cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
# pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
# efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
# bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
# cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
# cgroup on /sys/fs/cgroup/misc type cgroup (rw,nosuid,nodev,noexec,relatime,misc)
# cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma)
# cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset,clone_children)
# cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
# cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
# cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
# cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
# cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
# cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
# cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
# cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
# systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=28,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=15057)
# mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
# hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
# debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
# tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
# fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
# configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
# /var/lib/snapd/snaps/bare_5.snap on /snap/bare/5 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide)
# /var/lib/snapd/snaps/core20_1822.snap on /snap/core20/1822 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide)
# /var/lib/snapd/snaps/canonical-livepatch_164.snap on /snap/canonical-livepatch/164 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide)
# /var/lib/snapd/snaps/spotify_60.snap on /snap/spotify/60 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide)
# /var/lib/snapd/snaps/gtk-common-themes_1535.snap on /snap/gtk-common-themes/1535 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide)
# /var/lib/snapd/snaps/gnome-3-38-2004_115.snap on /snap/gnome-3-38-2004/115 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide)
# /var/lib/snapd/snaps/snapd_18357.snap on /snap/snapd/18357 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide)
# /var/lib/snapd/snaps/gnome-3-28-1804_161.snap on /snap/gnome-3-28-1804/161 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide)
# /var/lib/snapd/snaps/core_14784.snap on /snap/core/14784 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide)
# /var/lib/snapd/snaps/core20_1828.snap on /snap/core20/1828 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide)
# /var/lib/snapd/snaps/snap-store_638.snap on /snap/snap-store/638 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide)
# /var/lib/snapd/snaps/lxd_24483.snap on /snap/lxd/24483 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide)
# /var/lib/snapd/snaps/gnome-3-38-2004_119.snap on /snap/gnome-3-38-2004/119 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide)
# binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime)
# /var/lib/snapd/snaps/snap-store_558.snap on /snap/snap-store/558 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide)
# /dev/nvme0n1p1 on /boot/efi type vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
# lxcfs on /var/lib/lxcfs type fuse.lxcfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
# tmpfs on /run/snapd/ns type tmpfs (rw,nosuid,nodev,noexec,relatime,size=3203468k,mode=755,inode64)
# tmpfs on /run/user/125 type tmpfs (rw,nosuid,nodev,relatime,size=3203464k,mode=700,uid=125,gid=130,inode64)
# gvfsd-fuse on /run/user/125/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=125,group_id=130)
# nsfs on /run/snapd/ns/canonical-livepatch.mnt type nsfs (rw)
# nsfs on /run/snapd/ns/lxd.mnt type nsfs (rw)
# tmpfs on /var/snap/lxd/common/ns type tmpfs (rw,relatime,size=1024k,mode=700,inode64)
# nsfs on /var/snap/lxd/common/ns/shmounts type nsfs (rw)
# nsfs on /var/snap/lxd/common/ns/mntns type nsfs (rw)
# tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=3203464k,mode=700,uid=1000,gid=1000,inode64)
# gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
# /dev/fuse on /run/user/1000/doc type fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
# nsfs on /run/snapd/ns/snap-store.mnt type nsfs (rw)
# nsfs on /run/snapd/ns/spotify.mnt type nsfs (rw)
# /var/lib/snapd/snaps/core18_2708.snap on /snap/core18/2708 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide)
# /var/lib/snapd/snaps/core18_2714.snap on /snap/core18/2714 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide)

Should we close this issue then because of the lack of a minimum bug reproducer ?

@gabrielmougard did you mean to close this?

@tomponline I closed the issue yesterday yes.. I really could not reproduce the scenario I experienced with LXD 5.11. Can I close this PR then ?


Update Composer dependencies (2023-12-18-00-27)

Visual regression test passed!
View the visual regression test report


Reformat changelog to add versionbot

Change-Type: patch

Types had changed somehow since this code was written, and it had broken - this PR now also fixes those types.

@pimterry , I'm not sure what this line used to do: process.env = _.omit(process.env, environment.isSettingVariable); . It seems that environment.isSettingVariable is a method

@MoranF Good question! Yes, it looks like that was trying to remove all RESIN_ variables from the env, but that's actually not valid (according to the lodash docs) so probably wasn't really doing anything, and the lodash types have been updated and now make it fail the build completely, because it's not valid.
As far as I can tell it's not necessary anyway, especially since it hasn't really been doing anything until now. process.env is changed in the tests, but that's local to this process, and immediately after that line the process is going to exit since the tests have finished so I don't think we need to bother resetting this. As far as I can tell it's safe to just delete :smiley:


more properties to add

Properties to add before v0.4.0 release

[x] z-index .-z may use same values as order
[x] height .-h (see #1 , #22 )
[x] line-height .-lh
[x] letter-spacing .-ls
[x] word-spacing .-ws
[x] text-indent .-ti
[x] white-space (rename to .-sp)
[x] overflow-wrap .-ww (on #1)
[x] overflow .-of (on #1)
[x] opacity .-o
[x] text-overflow .-to
[ ] quotes .-q (only value: none)

See https://github.com/chharvey/bangs/wiki/List-of-CSS-Properties-Supported for a complete list.

[x] unordered list item markers for list-style-type (.-lst)

pushing this back to v0.5.0 release

 bangs v0.11.0

more to add:

[ ] .-to-f    text-overflow: fade
[ ] add text-align properties start (s), end (e), justify-all (ja)

6e26d5d
not adding in text-align: justify-all due to lack of browser support


dualsense

I can't connect my ps5 controller via bluetooth, the application doesn't recognize it

https://github.com/Ryochan7/DS4Windows