使用hyperf的模型查询数据时，刷新API接口时，有50%的概率会报这个错误

[2023-05-20 07:20:36 $12089.0]	WARNING	Server::check_worker_exit_status(): worker(pid=12102, id=11) abnormal exit, status=0, signal=11
A bug occurred in Swoole-v5.0.1, please report it.
The Swoole developers probably don't know about it,
and unless you report it, chances are it won't be fixed.
You can read How to report a bug doc before submitting any bug reports:

https://github.com/swoole/swoole-src/blob/master/.github/ISSUE.md
Please do not send bug reports in the mailing list or personal letters.
The issue page is also suitable to submit feature requests.

OS: Darwin 22.4.0 Darwin Kernel Version 22.4.0: Mon Mar  6 21:00:17 PST 2023; root:xnu-8796.101.5~3/RELEASE_X86_64 x86_64
GCC_VERSION: Apple LLVM 14.0.0 (clang-14<IP_ADDRESS>)
PHP_VERSION : 8.1.12

这个问题我也遇到了
https://github.com/swoole/swoole-src/issues/4776

这个问题我解决不了，得向swoole提issues : )

接口会挂掉还是只是警告


Server farm proxy?

Hi guys,
Im proxying though my IIS using server farms for multiple sub domains.
Is this possible, can someone point me to a how to?
Thank you

I'm not sure what your configuration looks like, but it sound like you might be able to use a central cerficate store: https://blogs.msdn.microsoft.com/kaushal/2012/10/11/central-certificate-store-ccs-with-iis-8-windows-server-2012/
LEWS supports that with the --centralsslstore switch

I have the same problem with IIS ARR , I have multiple sub domains, and in the master server just binding port 80  without any domain

There is nothing special needed. Only the path /.well-known to these subdomains need to be accessible from outside. It is just a text file... so you can easily test with staging system.

Thanks all,
I ended up using the other non HTTP (/.well-known) that I cant remember the name of lol. This worked well with a SAN cert.

I guess we can close this then :)

Yes :)
Thanks again everyone!


think about default ordering by phase

It would be super-cool for interpretation
If the default ordering was by phase extension, so that things which occur together group together

So
mitotic G1 phase
mitotic S phase
mitotic G2 phase
mitotic M phase

mitotic prophase
mitotic prometaphase
mitotic metaphase
mitotic anaphase
mitotic telophase
no phase
(could be expanded for meiosis etc)

This way, where there a lot of annotation, things which occur simultaneously would group together which would make much more sense biologically.

moved to duplicate
https://github.com/pombase/website/issues/55


Allow adding more field to payload of encoded token

Situation:

when using Nextjs as frontend, I need ability to add user_role to payload of the encoded token
so that, Nextjs can know which role of current user, then dynamically render the content, with out any additional API call

What do I know:

I read the source, in this file, currently, the only claim we can set is via USER_ID_CLAIM

Expected:

So the question is:

Is there any way to achieve this?

You can do it by customizing the claims

Thank you @confuzeus
I missed that on the document.


Deploy on Github Pages

Describe the bug
When I deploy the basic Vite app I get a blank page and an error in the Chrome dev toos: Uncaught TypeError: Failed to resolve module specifier "vue". Relative references must start with either "/", "./", or "../".
Reproduction
the repo

npm init vite-app mafagafa.github.io
cd mafaga.github.io
npm install
npm run build
echo > .nojekyll (without this it won't find _assets/, am I right?)
create the repository mafagafa.github.io
git init
git add .
git commit -m 'first commit'
git remote add origin https://github.com/Mafagafa/mafagafa.github.io.git
git push -u origin master

System Info

required vite version: 0.20.0
required Operating System: Linux Ubuntu Studio 20.04
required Node version: v14.4.0
Optional:

npm version: 6.14.5
Installed vue version (from yarn.lock or package-lock.json): 3.0.0-beta.15
Installed @vue/compiler-sfc version: 3.0.0-beta.14

Logs (Optional if provided reproduction)

Run vite or vite build with the --debug flag.
how do I do this? vite is not a valid command
Provide the error log here.

thank you!

The repository in question seems to be a vuepress repository?

https://github.com/vitejs/vite#public-base-path


how to  compute CMC and rank?

how to  compute CMC and rank?

Suppose you have 3 gallery samples with ID 0,1,1 and 4 query samples with ID 0,0,1,1, then you need to
Compute 3x4 pairwise distance matrix D, where D[i, j] = distance between gallery-i and query-j
Create a query ID list qids = [0,0,1,1]
Create a gallery ID list gids = [0,1,1]
Then you can call reid.evaluation_metrics.cmc(D, qids, gids) to get CMC.

1.why is  ID 0,1,1  ?   it mean the second and the third are the same person ?
2.so   ID 0,1,1   don't have  like  cuhk03    ID  0000  0001  0002   0003 .....(many ID) ?

Yeah, it's just an example. The second and the third belong to the same person identity.
It's just an example to help you understand.

cuhk03 is use  val  to  compute  CMC    right?

I am not sure what you refer to. All the results here in open reid are reported on the test set.

hi
what  are the   gallery , query  and  prob ?

@Phoebe-star query is the same means as probe,you have a query(probe)image and then you should find the image that have the same id in the gallery. and  we have a rank list  of the gallery images  ,CMC is caculated based on the list

@Linranran Thank you very much for the explanation!
@Phoebe-star Yes, large distance value implies the pair is probably not the same person, and vice versa.

@Cysu its my pleasure，haha

I   got it   , thanks you   ^^

I have another problem
how to  select  cuhk03   dataset   validation  to  compute  CMC   ??
every  time  , I  got  a  different  cmc   value

I have another question in computing CMC and mAP of cuhk03. Open reid gived me the result that rank1 was greater than mAP, but When I read some papers such as “SVDNet for Pedestrian Retrieval”， they showed the results that mAP  was greater than rank1. I'm comfused all the time even after I read Evaluation Metrics in docs of open reid. Could anyone help me figure out that or just point me to some helpful website?

Suppose you have 3 gallery samples with ID 0,1,1 and 4 query samples with ID 0,0,1,1, then you need to
Compute 3x4 pairwise distance matrix D, where D[i, j] = distance between gallery-i and query-j
Create a query ID list qids = [0,0,1,1]
Create a gallery ID list gids = [0,1,1]
Then you can call reid.evaluation_metrics.cmc(D, qids, gids) to get CMC.

I believe the distmat should be a 4x3 matrix.


Syntax Highlighter’s internal span tags appearing

Lately (in Safari only) I've been seeing this crop up:

What is the original source?


部分iPad上apple pencil不能在画布上使用，请问有其他朋友遇到过吗?

部分iPad上apple pencil不能在画布上使用，请问有其他朋友遇到过吗?
我自己无法复现，但是有部分线上用户反馈，iPad上apple pencil不能在画布上使用，画布以外的位置都正常。

Use it for check:
//
//  UIDevice+Ex.swift
//  PrescriptionReception
//
//  Created by Le Xuan Quynh on 21/09/2023.
//

import UIKit

// supportPencil
extension UIDevice {
    /*
     You can use Apple Pencil (2nd generation) with these iPad models:
     iPad mini (6th generation)
     iPad Air (4th generation and later)
     iPad Pro 12.9-inch (3rd generation and later)
     iPad Pro 11-inch (1st generation and later)

     You can use Apple Pencil (1st generation) with these iPad models:
     iPad mini (5th generation)
     iPad (6th, 7th, 8th, and 9th generation)
     iPad (10th generation)*
     iPad Air (3rd generation)
     iPad Pro 12.9-inch (1st and 2nd generation)
     iPad Pro 10.5-inch
     iPad Pro 9.7-inch
     */
    var isSupportPencil: Bool {
        // if simulator always return false
        #if targetEnvironment(simulator)
        return false
        #endif
        // return self.modelName == "iPad mini (6th generation)"
        // || self.modelName == "iPad Air (4th generation)"
        // || self.modelName == "iPad Pro 12.9-inch (3rd generation)"
        // || self.modelName == "iPad Pro 11-inch (1st generation)"
        // || self.modelName == "iPad mini (5th generation)"
        // || self.modelName == "iPad (6th generation)"
        // || self.modelName == "iPad (7th generation)"
        // || self.modelName == "iPad (8th generation)"
        // || self.modelName == "iPad (9th generation)"
        // || self.modelName == "iPad Air (3rd generation)"
        // || self.modelName == "iPad Pro 12.9-inch (1st generation)"
        // || self.modelName == "iPad Pro 12.9-inch (2nd generation)"
        // || self.modelName == "iPad Pro 10.5-inch"
        // || self.modelName == "iPad Pro 9.7-inch"
        // using contains
        return ["iPad mini (6th generation)",
                "iPad Air (4th generation)",
                "iPad Pro 12.9-inch (3rd generation)",
                "iPad Pro 11-inch (1st generation)",
                "iPad mini (5th generation)",
                "iPad (6th generation)",
                "iPad (7th generation)",
                "iPad (8th generation)",
                "iPad (9th generation)",
                "iPad Air (3rd generation)",
                "iPad Pro 12.9-inch (1st generation)",
                "iPad Pro 12.9-inch (2nd generation)",
                "iPad Pro 10.5-inch",
                "iPad Pro 9.7-inch"].contains(self.modelName)
    }

    var modelName: String {
        return UIDevice.current.name
    }
}


chore: Switch to stable Rust

Which issue does this PR close?

Closes https://github.com/apache/datafusion-comet/issues/142
Rationale for this change

Continues the work started by @sunchao in https://github.com/apache/datafusion-comet/pull/373
What changes are included in this PR?

How are these changes tested?

LGTM. Thanks for taking this over. I was about to ask chao if he is still working on the #373.
It looks like the CI is still failed, you may take a look at that:

- unary negative integer overflow test *** FAILED *** (817 milliseconds)

  "[ARITHMETIC_OVERFLOW] short overflow. If necessary set "spark.sql.ansi.enabled" to "false" to bypass this error. SQLSTATE: 22003" did not contain " caused overflow" (CometExpressionSuite.scala:1563)

It looks like the unary minus tests are failing in main as well for Spark 4. I think there was a conflict between two PRs that were merged yesterday.


add enhancenet

After tweaking the loss function parameters, I eventually got some comparable results.
But the training was highly highly highly unstable. I slightly altered the learning rate and some parameters, which appears to be more stable. Further, the paper is a little bit vague about batch-size, normalization steps, and the generator/discriminator balancing:
The article states that training was done by balancing the generator/discriminator loss functions (skipping discriminator updates, if too good) which is listed here at 11 as a don't do. I just tweak the hyperparameters.
Click on the image, for better comparison.

The network training is still running.  I can share the weights for this implementation.

I might be easy to further convert the release model by the authors into a python dictionary, which can be restored by DictRestore. I haven't tried this yet and just used the author's code.

Results are available and comparable with the authors implementations (there is no clear winner)
results.tar.gz

I think this pull request is ready to be reviewed. My trained model is here:
http://files.patwie.com/models/enet-pat.npy
Feel free to add suggestions or edit when required.
Please consider, I am not that patient to train it more epochs and cherry pick the best model.

Do you think you need align_corners=True for tf.image.resize_*?
To be honest I don't like tf.image.resize_ because they never align pixel to pixel regardless of align_corners. But maybe True makes more sense here?
You can check this out:
import numpy as np
from skimage.transform import rescale

np.set_printoptions(linewidth=10000)

arr = np.array(
    [[1,2,3,4],
    [5,6,7,8],
    [9,10,11,12]], dtype='float32')

input = tf.constant(arr)
input4D = tf.reshape(input, [1, 3, 4, 1])
resize = tf.image.resize_bilinear(input4D, [6, 8], align_corners=True)[0,:,:,0]
sess = tf.Session()
r1 = sess.run(resize)
r2 = rescale(arr/100.0, 2, mode='edge') * 100

print(r1)
print(r2)

TensorFlow does very strange things when resizing images  with/without align_corners. For the sake of consistency I would like to keep the current version.
Feel free to retrain the model :wink:

Is the visualization produced by Saccade?

The visualization is pure LaTeX + Tikz

At last, rename to SuperResolution

Should I do these changes, or did you started it already?

What is "enet-pat"....? will you rename it to "enhancenet"?

And how long did you train these models?

"enet-pat" (patch-, adversarial, & texture-loss) is from the paper, see Figure 3 in the paper. I trained them with two gpus (hence batchsize 12) until global step 806817 (I use the checkpoint model-806817).

Why would you have checkpoint model-806817? Are we using the same dataset?:
100%|#######################|19714/19714[59:02<00:00, 5.56it/s]
[1206 04:49:54 @base.py:255] Epoch 40 (global_step 788560) finished, time:3542.78 sec.
[1206 04:49:55 @saver.py:82] Model saved to train_log/enet-pat/model-788560.
[1206 04:49:55 @monitor.py:363] GAN_loss/discrim/accuracy: 0.99414
[1206 04:49:55 @monitor.py:363] GAN_loss/discrim/loss: 0.019299
[1206 04:49:55 @monitor.py:363] GAN_loss/gen/accuracy: 0.0026996
[1206 04:49:55 @monitor.py:363] GAN_loss/gen/loss: 8.9464
[1206 04:49:55 @monitor.py:363] QueueInput/queue_size: 49.585
[1206 04:49:55 @monitor.py:363] add: 19.204
[1206 04:49:55 @monitor.py:363] additional_losses/loss_LA: 8.9464
[1206 04:49:55 @monitor.py:363] additional_losses/loss_LP1: 1.3098
[1206 04:49:55 @monitor.py:363] additional_losses/loss_LP2: 0.0015531
[1206 04:49:55 @monitor.py:363] additional_losses/loss_LT1: 2.3112e-37
[1206 04:49:55 @monitor.py:363] additional_losses/loss_LT2: 2.2718e-37
[1206 04:49:55 @monitor.py:363] additional_losses/loss_LT3: 2.3154e-37
[1206 04:49:55 @base.py:245] Start Epoch 41 ...
100%|#######################|19714/19714[59:03<00:00, 5.56it/s]
[1206 05:48:58 @base.py:255] Epoch 41 (global_step 808274) finished, time:3543.57 sec.

vgg19 should be applied to images of range [0,255]-mean.


Add Manos Lab Time

@Krith-man I can't merge this as you have conflicts. Please rebase and resolve the conflicts


Create documentation around GLOBALODOCONFIG env variable

[kind/Documentation]

What did you find missing in the documentation?
No doc found around GLOBALODOCONFIG
What is the relevance of it?
Increase odo user experience

/assign @mohammedzee1000

/priority high

cc @boczkowska

/assign @boczkowska

/assign @boczkowska

@boczkowska do you have any updates or do you need any help
GLOBALODOCONFIG  allows you to change the location of where odo preferences are stored


Bump the minimum php version for execution to 8.1

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
12 unchanged lines in 5 files lost coverage.
Overall coverage decreased (-0.2%) to 79.006%

Files with Coverage Reduction
New Missed Lines
%

src/Lib/Elf/Parser/Elf64Parser.php
1
97.56%

src/Lib/PhpInternals/Types/Zend/Zval.php
1
85.71%

src/Lib/PhpInternals/Types/Zend/ZendValue.php
2
88.89%

src/Lib/PhpInternals/Types/Zend/ZendArray.php
4
83.72%

src/Lib/PhpInternals/Types/Zend/ZendExecuteData.php
4
68.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.2%

Covered Lines:
1351

Relevant Lines:
1710

💛  - Coveralls


Vim9: cannot run autoload function from :def function

Describe the bug
In Vim9 script, we cannot run an autoload function from a :def function.
To Reproduce
Run this shell command:
vim -Nu NONE -S <(cat <<'EOF'
    vim9script
    mkdir('/tmp/some/autoload', 'p')
    set rtp^=/tmp/some
    let lines =<< trim END
        def g:some#func()
            echo 'some#func'
        enddef
    END
    writefile(lines, '/tmp/some/autoload/some.vim')
    def Func()
        g:some#func()
    enddef
    Func()
EOF
)

E117 is raised:
E117: Unknown function: g:some#func

Expected behavior
No error is raised.
Environment

Vim version: 8.2 Included patches: 1-1419
OS: Ubuntu 16.04.7 LTS
Terminal: XTerm(358)

Additional context
The issue disappears when the autoload function is run from a legacy function:
vim9script
mkdir('/tmp/some/autoload', 'p')
set rtp^=/tmp/some
let lines =<< trim END
    def g:some#func()
        echo 'some#func'
    enddef
END
writefile(lines, '/tmp/some/autoload/some.vim')
fu Func()
    call g:some#func()
endfu
Func()

The issue also disappears when the autoload function is called directly at the script level:
vim9script
mkdir('/tmp/some/autoload', 'p')
set rtp^=/tmp/some
let lines =<< trim END
    def g:some#func()
        echo 'some#func'
    enddef
END
writefile(lines, '/tmp/some/autoload/some.vim')
g:some#func()

The issue also disappears when the :def function which calls the autoload function is moved in the same autoload script:
vim9script
mkdir('/tmp/some/autoload', 'p')
set rtp^=/tmp/some
let lines =<< trim END
    def g:some#func()
        echo 'some#func'
    enddef
    def Func()
        g:some#func()
    enddef
END
writefile(lines, '/tmp/some/autoload/some.vim')
source /tmp/some/autoload/some.vim
Func()

Note that I use the g: prefix in the autoload function's header, and at its call site.  That's because the help at :h autoload still says that we should use it:
https://github.com/vim/vim/blob/035d6e91bd83574cab5a913c5c3a924d9011696b/runtime/doc/eval.txt#L11876-L11877
https://github.com/vim/vim/blob/035d6e91bd83574cab5a913c5c3a924d9011696b/runtime/doc/eval.txt#L11890-L11894
But I don't think it's necessary:
vim9script
mkdir('/tmp/some/autoload', 'p')
let lines =<< trim END
    vim9script
    def some#func()
        echo 'some#func'
    enddef
END
writefile(lines, '/tmp/some/autoload/some.vim')
set rtp^=/tmp/some
some#func()

Notice how the g: prefix is missing both in the autoload function's header, and at its call site.  And yet, the snippet works as expected.


Submit Branch Initiative

Continuation of #1767
costing workbook here
It was decided that this project be governed under a Branch Initiative
See email from Vithy

closing as duplicate of #1783


refactor(validation) remove the md-select error in all cases

I have added an example on the validation of a select because when an error is displayed under a select and then we change the value dynamically, the error was not removed, even after a reset, and cause some weird displaying of the label.
I have made two commits, one to add the example in the sample solution and one that fix the bug in the validationRenderer

When I have run jspm install in the sample folder, it changed the config.js and package.json files that I didn't commit, could it be the reason for the checks have failed?

First of all, thanks. :smiley:
The tests seem to fail because the CI server is unable to fetch packages from GitHub..
warn Error on getPackageConfig for github:polymer/mutationobservers
     Unauthorized response for GitHub API.
     Use jspm registry config github to reconfigure the credentials, or update them in your ~/.netrc file.

Nothing big but I wonder why that happens from time to time.


fix(package): update wreck to version 12.0.0

Closes #28
https://greenkeeper.io/

Coverage remained the same at 16.667% when pulling 8540930d6c78e5feee2a654af2e66d1e9b7119ad on greenkeeper/wreck-12.0.0 into 2095b1f5fe373587981acf1ab6a25a48e23e7412 on master.


Bluetooth: controller: Fix assert on different transaction collision

Updated the implementation of PHY update procedure to not
assert when peer master violates the Bluetooth Specification
v5.0 Vol.6 Part B Section 5.3 Procedure Collisions. Instead
disconnect the link with reason Different Transaction
Collision (0x2A).
Certain phones in the market perform Connection Update
Procedure and do not correctly handle remote initiated
colliding PHY update procedures. They try to perform both
the transactions involving an instant simultaneously
violating the Bluetooth Specifications.
Implementation in Zephyr is updated to gracefully handle
the violating remote master device, and not fatally assert
in the local device.
Signed-off-by: Vinayak Kariappa Chettimada<EMAIL_ADDRESS>

@carlescufi and @jhedberg this PR is fix asserting, but does not solve the primary issue of staying connected, I will send another PR (once I settle on a fix) to handle violating phone.

Codecov Report

Merging #9492 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #9492   +/-   ##
=======================================
  Coverage   52.27%   52.27%
=======================================
  Files         212      212
  Lines       25925    25925
  Branches     5570     5570
=======================================
  Hits        13553    13553
  Misses      10115    10115
  Partials     2257     2257

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 ba6763a...22b6048. Read the comment docs.


Fix: Remove duplicate entry in array of modules

The Application module is registered a few lines further down the line again, once should be enough.

Is it supposed to not be the first module?

neither - don't see any reason it should appear at the beginning as well as in the middle. so this change looks fine to me

Thanks @localheinz!

Thanks for merging so quickly, @Ocramius!


Add -D option to specify output directory

As part of a build process, it's often nice to be able to specify where the output files go without having to move them after the fact.
Eventually it might be nice to have an option to output either the .h or .c file to stdout as well, so it can be piped anywhere.

Thanks!


signing RPMs with sha256 headers/payloads built with nfpm is not supported

Currently, this module only works for signing RPMs that have md5/sha1 digests. The output below was generated with rpm -Kv to inspect RPMs  built with fpm vs nfpm respectively.
    Header SHA1 digest: OK
    MD5 digest: OK

However, RPMs built with nfpm are with sha256 digests:
  Header SHA256 digest: OK
  Payload SHA256 digest: OK

Are there any possibilities to extend this module to support RPMs that are built with nfpm?

Can you provide a sample rpm that could be used for testing? Preferably something that only contains one file and can be used for test data.

nfpm.zip
@elliotpeele: thanks for the reply. I have uploaded the RPM built with nfpm for your testing purpose. You can also run the following commands to regenerate the RPM:
 nfpm package --config test.yaml --packager rpm

Please let me know if you need anything additional.

@elliotpeele: thanks for the reply. I have uploaded the RPM built with nfpm for your testing purpose: nfpm.zip. You can also rerun the following commands to regenerate the RPM:
nfpm package --config test.yaml --packager rpm
Please let me know if you need anything additional.

@elliotpeele: thanks for your reply earlier. Just checking to see if there are plans to support such feature?

@elliotpeele: Thanks for working on this issue. I posted a comment within in the PR that the new logic for v4 signatures is not compatible with rpm -k command while the old logic does support this for md5 digests. I am just wondering if there are plans to support such feature? Thanks!

@elliotpeele : any updates on this issue? thank you

Fixed in v0.3.0, let me know if it doesn't work for you.


[Feature] Config restructure.

This is my implementation of it. This is still not finished. I still need to update the "push notification service" and the config migration code.
(Please note that this is indeed based of of the "enable-tag" branch)
Also, it has been structured and tested with this config: (except that the Fuel and PV page weren't actually tested)
- page_type: PV
  power: "{{ states.sensor.YOUR_SENSOR.state }}"
  storage: "{{ states.sensor.YOUR_SENSOR.state }}"
  discharge: "{{ states.sensor.YOUR_SENSOR.state }}"
  powerhousetotal: "{{ states.sensor.YOUR_SENSOR.state }}"
  vomNetz: "{{ states.sensor.YOUR_SENSOR.state }}"
  time: "{{ now().strftime('%H:%M') }}"  #Format HH:MM

#etc for the PV page, for example.

- page_type: components  #or custom, I'm not sure what's better because of Custom Channels..
  components:
  - type: text
    position: [0, 10]
    content: "github/gickowtf"
    font: PICO_8
    color: [255, 0, 0] # or write "red"

  - type: text
    position: [17, 18]
    content: '{{ states.sensor.YOUR_SENSOR.state }}'
    color: '{{ "red" if float(states.sensor.YOUR_SENSOR.state) <= 1 else "green"}}'
    font: PICO_8

  - type: image
    position: [1, 16]
    image_path: '{% set num = float(states.input_number.test.state) %} {% if num >= 80 %} /config/custom_components/divoom_pixoo/img/akku80-100.png {% elif num >= 100 %} /config/custom_components/divoom_pixoo/img/akku60-80.png {% else %} /config/custom_components/divoom_pixoo/img/akku40-60.png {% endif %}'
# This is just an example with Templates. The old PV page would still work (as shown above).

- page_type: channel
  id: 2

- page_type: clock
  enabled: False  # This would disable the integration to render the page. Of course, this would accept Templates. This 'tag' would True by default (and of course optional), and be available for every page.
  id: 39

(The color names are also based of of https://github.com/paztronomer/blog/blob/master/code/p01_python_colors/named_colors.png)
Closes #17

I've just skimmed through it. I think it's really brilliant. But unfortunately I can't take a closer look until tonight. I'm too busy with other projects.

No worries! It's not finished anyways, so there's no stress.

i just tested it. unfortunately there seems to be an error with the enable tag. i have my config so that i get page 1 displayed page 2 should not be displayed but is displayed for 30 seconds and page 3 which should be displayed again is not displayed at all. otherwise i find the spelling of the config clearly nicer.

I don't know why but in my PR #27 every page that should be displayed is shown for exactly 15 seconds... but unfortunately I can't recognize the error right away.

I will simply merge my PR #27 tomorrow. So that the sensor.py is up to date. Sorry it's way too late again. Last week I was on vacation and definitely had more time.

Alright, I tested a lot and I redid a bit of the logic. @gickowtf could you try again with your config?
(Completely unrelated, but I also realized that you can completely disable the page "changing" logic entirely if you disable the sensor entity in HA. Pretty cool!)

Just remade/updated the service. Hope you like it!

ok the push service works perfectly without having looked at the code beforehand, I thought that it was now also possible to push PV, Fuel or Clockid. So I almost said it doesn't work. But with the component it worked very well in the end.
page_type: components  #or custom, I'm not sure what's better because of Custom Channels..
components:
  - type: text
    position: [0, 10]
    content: "github/gickowtf"
    font: PICO_8
    color: [255, 0, 0] # or write "red"

The page display now also works as desired :D Great work. I really like it very much :
I have tested it with these configs:
- page_type: components  #or custom, I'm not sure what's better because of Custom Channels..
  enabled: "{{ states.input_boolean.test.state }}"
  components:
  - type: text
    position: [0, 10]
    content: "1 github/gickowtf"
    font: PICO_8
    color: [255, 0, 0] # or write "red"
- page_type: components  #or custom, I'm not sure what's better because of Custom Channels..
  enabled: "{{ states.input_boolean.test2.state }}"
  components:
  - type: text
    position: [0, 10]
    content: "2 github/gickowtf"
    font: PICO_8
    color: [255, 0, 0] # or write "red"
- page_type: components  #or custom, I'm not sure what's better because of Custom Channels..
  enabled: "{{ states.input_boolean.test.state }}"
  components:
  - type: text
    position: [0, 10]
    content: "3 github/gickowtf"
    font: PICO_8
    color: [255, 0, 0] # or write "red"

- page_type: Fuel
  enabled: "{{ states.input_boolean.test.state }}"
  title: Classic
  name1: Diesel
  price1: "{{ states.sensor.diesel.state }}"
  name2: Super
  price2: "{{ states.sensor.super.state }}"
  name3: E10
  price3: "{{ states.sensor.e10.state }}"
  status: >-
    {% if is_state('binary_sensor.status', 'on') %} Offen {%
    else %} Geschlossen {% endif %}
  title_offset: 10
- page_type: PV
  enabled: "{{ states.input_boolean.test2.state }}"
  power: "{{ states.sensor.power.state }}"
  storage: "{{ states.sensor.battery_percent.state }}"
  discharge: "{{ states.sensor.battery_power.state }}"
  powerhousetotal: "{{ states.power_house_total.state }}"
  vomNetz: "{{ states.sensor.power_external_total.state }}"
  time: "{{ now().strftime('%H:%M') }}"
- page_type: clock
  enabled: "{{ states.input_boolean.test.state }}"
  id: 182

give me a sign when you are done then I would like to merge this. I like it very much - as always a thousand thanks for your help

sorry for deleting my branch enable tag i restored it and reopened your PR

sorry for deleting my branch enable tag i restored it and reopened your PR

(You should be able to delete the branch now. I changed the PR to go to main now)

ok the push service works perfectly without having looked at the code beforehand, I thought that it was now also possible to push PV, Fuel or Clockid. So I almost said it doesn't work. But with the component it worked very well in the end.
page_type: components  #or custom, I'm not sure what's better because of Custom Channels..
components:
  - type: text
    position: [0, 10]
    content: "github/gickowtf"
    font: PICO_8
    color: [255, 0, 0] # or write "red"

The page display now also works as desired :D Great work. I really like it very much :
I have tested it with these configs:
- page_type: components  #or custom, I'm not sure what's better because of Custom Channels..
  enabled: "{{ states.input_boolean.test.state }}"
  components:
  - type: text
    position: [0, 10]
    content: "1 github/gickowtf"
    font: PICO_8
    color: [255, 0, 0] # or write "red"
- page_type: components  #or custom, I'm not sure what's better because of Custom Channels..
  enabled: "{{ states.input_boolean.test2.state }}"
  components:
  - type: text
    position: [0, 10]
    content: "2 github/gickowtf"
    font: PICO_8
    color: [255, 0, 0] # or write "red"
- page_type: components  #or custom, I'm not sure what's better because of Custom Channels..
  enabled: "{{ states.input_boolean.test.state }}"
  components:
  - type: text
    position: [0, 10]
    content: "3 github/gickowtf"
    font: PICO_8
    color: [255, 0, 0] # or write "red"

- page_type: Fuel
  enabled: "{{ states.input_boolean.test.state }}"
  title: Classic
  name1: Diesel
  price1: "{{ states.sensor.diesel.state }}"
  name2: Super
  price2: "{{ states.sensor.super.state }}"
  name3: E10
  price3: "{{ states.sensor.e10.state }}"
  status: >-
    {% if is_state('binary_sensor.status', 'on') %} Offen {%
    else %} Geschlossen {% endif %}
  title_offset: 10
- page_type: PV
  enabled: "{{ states.input_boolean.test2.state }}"
  power: "{{ states.sensor.power.state }}"
  storage: "{{ states.sensor.battery_percent.state }}"
  discharge: "{{ states.sensor.battery_power.state }}"
  powerhousetotal: "{{ states.power_house_total.state }}"
  vomNetz: "{{ states.sensor.power_external_total.state }}"
  time: "{{ now().strftime('%H:%M') }}"
- page_type: clock
  enabled: "{{ states.input_boolean.test.state }}"
  id: 182

I was impressed that the Fuel and PV page didn't work, as they technically should have. But, turns out HA renders the templates before even passing it to the integration, so it gave an 'int' to the template renderer, which wouldn't work. It should be fixed, and I'm happy you like it!

Probably a good idea to update the README too. :-)

Of course I'll adapt the readme accordingly when the time comes.

i am currently adapting the entire readme or rewriting it for your PR. i noticed that the newline support {{\n}} no longer works. "template error".
The good thing about rewriting the readme is that I'm really testing everything once :D

Yeahh, I just tested it and it did that. You HAVE to put {{'\n'}} with the ' , or else it won't really work. I'm not sure why, but that's a fix...

No problem, I think it's even better the way it is now
      content: |-
        text1 on first line
        text2 on second line

So I have really tested everything completely once. I couldn't find any new errors and I have to say I'm very impressed. Really very good work.  ich habe prepared the readme in #30

Alright, just added a migration feature. It will basically auto update old config-entry users, but it can also allow users that update from the old configuration.yaml era to use the migration tool (with the async_detect_and_fix_old_entry method). I've included an old configuration down here to test if you want. (please test this feature!!!) ((And I'm sorry Irene, it's full of if/elif)
Also, this could break your config entries (gicko and irene), since you already used the new config style before I updated the "CURRENT_ENTRY_VERSION" to 2. This will/should not happen to end-users.
- page: 1
  PV:
    - power: "{{ states.sensor.YOUR_SENSOR.state }}"
      storage: "{{ states.sensor.YOUR_SENSOR.state }}"
      discharge: "{{ states.sensor.YOUR_SENSOR.state }}"
      powerhousetotal: "{{ states.sensor.YOUR_SENSOR.state }}"
      vomNetz: "{{ states.sensor.YOUR_SENSOR.state }}"
      time: "{{ now().strftime('%H:%M') }}"
- page: 2
  texts:
    - text: github/gickowtf
      position:
        - 0
        - 10
      font: FONT_PICO_8
      font_color:
        - 255
        - 0
        - 0
    - text: Thx 4 Support
      position:
        - 0
        - 30
      font: FONT_PICO_8
      font_color:
        - 255
        - 0
        - 0
  images:
    - image: /config/custom_components/divoom_pixoo/img/haus.png
      position:
        - 30
        - 10
- page: 3
  channel:
    - number: 2
- page: 4
  clockId:
    - number: 39

With that, I think the new config style is complete. (Maybe Irene's RenderFactory could be implemented later on??). Hope you like it!

Alright, I merged your readme branch in mine. You could close #30 I think.

Just create a new release and then that should be it. a thousand thanks again ... let me know what I can do for you.

Nice, thanks for merging. I'm not sure I understood correctly, but I unfortunately cannot create releases though. For that I would need to be a "maintainer" I think...

@Mrredstone5230 No problem, I think it's because of my English. I have now created a new release 1.7.0 and loaded version 1.4.2 with your old config. What can I say, it worked. Brilliant


Improve URL regex and separator detection in AutoLinkPlugin

close #3546
What this PR does:
This PR updates the URL detection method in the AutoLinkPlugin with the following changes:

Allow URLs with extensions (e.g., .png, .jpeg)
Allow URLs that do not start with "www" (e.g., gist.github.com)
Disallow domains ending with a dot (e.g., example.com.)
Disallow TLDs with fewer than 2 characters (e.g., example.c)
Make URL detection case-insensitive (e.g., https://example.com/)

Before:

After:

Please review and let me know if you have any suggestions or concerns.

Please check back as we've made corrections.
Changes

instead of no longer considering delimiters, AutoLinkNode is now generated or edited by determining whether to combine the TextContent of adjacent TextNode and match it to the URL when generating AutoLinkNode.
When converting from Text to Markdown, AutoLinkNode will now work even if it contains an AutoLinkNode.

@NozomiSugiyama the integration tests are failing, if you are still looking after this PR

@NozomiSugiyama are you planning to update this one, happy to help on this one if needed.

@ivailop7
My apologies for the delayed response.
I have rebased this onto the latest main branch and fixed the issues with the findLast method that were causing the tests to fail.

@ivailop7 My apologies for the delayed response. I have rebased this onto the latest main branch and fixed the issues with the findLast method that were causing the tests to fail.

Reran the tests, but unfortunately only the collab tests are passing, the rest are still failing.

@ivailop7
Ah! I missed that, my apologies. I've now fixed the behavior of the auto link node when a LineBreakNode comes at the end in plain-text mode. I have confirmed that the following tests are working correctly on my end:
env E2E_EDITOR_MODE=plain-text E2E_EVENTS_MODE=legacy-events npm run test-e2e-chromium
env E2E_EDITOR_MODE=plain-text E2E_EVENTS_MODE=modern-events npm run test-e2e-chromium
env E2E_EDITOR_MODE=rich-text E2E_EVENTS_MODE=legacy-events npm run test-e2e-chromium
env E2E_EDITOR_MODE=rich-text E2E_EVENTS_MODE=modern-events npm run test-e2e-chromium

Please check the changes again. Thank you.

@ivailop7
Ah! I missed that, my apologies. I've now fixed the behavior of the auto link node when a LineBreakNode comes at the end in plain-text mode. I have confirmed that the following tests are working correctly on my end:
env E2E_EDITOR_MODE=plain-text E2E_EVENTS_MODE=legacy-events npm run test-e2e-chromium
env E2E_EDITOR_MODE=plain-text E2E_EVENTS_MODE=modern-events npm run test-e2e-chromium
env E2E_EDITOR_MODE=rich-text E2E_EVENTS_MODE=legacy-events npm run test-e2e-chromium
env E2E_EDITOR_MODE=rich-text E2E_EVENTS_MODE=modern-events npm run test-e2e-chromium

Please check the changes again. Thank you.

Thank you @NozomiSugiyama for addressing the comments. @fantactuka or @zurfyx  could any of you scan this through again, it looks OK to me, but I think someone a bit more familiar with that part of the code would be nice to sign off as well.

Hey @zurfyx and @fantactuka can you have a look if this looks good to you too, looks mergeable to me.

PR should solve: https://github.com/facebook/lexical/issues/4692

@NozomiSugiyama have you had a chance to look into Acy's comments?

Hey @acywatson , @NozomiSugiyama hasn't replied recently, so I addressed your comments and pushed them to their branch. Could you have have a look. I changed the .getLatest() to .getWritable() and fixed the double reverse thing. the splitNodes method is used to split the before and after text away from the text converted to a link.

I would love to get this in for the next version. The current AutoLinkPlugin is close but not quite able to be used in production for our use case. This would do it.

@NozomiSugiyama let's split this PR into Markdown and non-Markdown, in order to move things forward with it.

@ivailop7
I apologize for the repeated delays in my responses. Regarding splitting the PR into Markdown and non-Markdown components, would it be appropriate to extract the changes from packages/lexical-markdown/src/MarkdownShortcuts.ts into a separate PR?
However, I'd like to point out that due to the changes in the AutoLinkPlugin in this PR, the following E2E tests will not pass. Hence, splitting them in a way that ensures all tests pass might be challenging:
[chromium] › packages/lexical-playground/__tests__/e2e/Markdown.spec.mjs:683:5 › Markdown › can convert "hello [world](https://www.test.com/)!" shortcut
[chromium] › packages/lexical-playground/__tests__/e2e/Markdown.spec.mjs:858:3 › Markdown › can type text with markdown
[chromium] › packages/lexical-playground/__tests__/e2e/Markdown.spec.mjs:960:3 › Markdown › can adjust selection after text match transformer

The main reason I made modifications to the MarkdownShortcuts is that previously, due to the absence of delimiters like spaces, certain text wasn't recognized as URLs. With the current changes, they are now identified as AutoLinks. Consequently, the MarkdownShortcuts does not function correctly when AutoLinks are included in the evaluated text.

@ivailop7 I apologize for the repeated delays in my responses. Regarding splitting the PR into Markdown and non-Markdown components, would it be appropriate to extract the changes from packages/lexical-markdown/src/MarkdownShortcuts.ts into a separate PR?
However, I'd like to point out that due to the changes in the AutoLinkPlugin in this PR, the following E2E tests will not pass. Hence, splitting them in a way that ensures all tests pass might be challenging:
[chromium] › packages/lexical-playground/__tests__/e2e/Markdown.spec.mjs:683:5 › Markdown › can convert "hello [world](https://www.test.com/)!" shortcut
[chromium] › packages/lexical-playground/__tests__/e2e/Markdown.spec.mjs:858:3 › Markdown › can type text with markdown
[chromium] › packages/lexical-playground/__tests__/e2e/Markdown.spec.mjs:960:3 › Markdown › can adjust selection after text match transformer

* The main reason I made modifications to the MarkdownShortcuts is that previously, due to the absence of delimiters like spaces, certain text wasn't recognized as URLs. With the current changes, they are now identified as AutoLinks. Consequently, the MarkdownShortcuts does not function correctly when AutoLinks are included in the evaluated text.

Hey! Right, that's part of the problem with this PR, we can't couple the Markdown Shortcuts Plugin to the AutoLinks Plugin, the two should be able to operate completely independently of each other an not rely on behaviour of the other as much as possible. Let's make the Markdown Shortcuts mergeable, so extracting stuff to packages/lexical-markdown/src/MarkdownShortcuts.ts is OK and the tests need to pass for the Markdown PR and then we can revisit the logic for the Autolinking.

@ivailop7 @NozomiSugiyama is there any further progress on this, possibly in a different PR? The problem is still happening on the Playground. Maybe I could help to move this forward?

I tested out this PR and it works a lot better than the stock AutoLinkPlugin.
I did find one issue. URLs include trailing punctuation in the link, which is undesirable. A common usage scenario is putting a URL in a sentence, e.g.
"Open http://localhost:5560/r/#/."
If you type "Open ", paste the URL, and type ".", the dot is linkified. I think a heuristic of excluding any trailing punctuation from the link would be best.
Thanks

I tested out this PR and it works a lot better than the stock AutoLinkPlugin. I did find one issue. URLs include trailing punctuation in the link, which is undesirable. A common usage scenario is putting a URL in a sentence, e.g.
"Open http://localhost:5560/r/#/."
If you type "Open ", paste the URL, and type ".", the dot is linkified. I think a heuristic of excluding any trailing punctuation from the link would be best.
Thanks

This PR is quite old now and it's unlikely to get merged, so I'm going to close it. If you are interested in taking the AutoLink part-only and cleaning it up and raising a new one, happy to give it another go.


Additional information for About Us

Add Pronouns to current Executives
Add Committee (just leads?) photos and descriptions

Going to be added in the upcoming about page


Add faqs

These changes were previously made as part of this PR:- https://github.com/harness/developer-hub/pull/6237. The branch belonged to a fork repository so was not able to replicate in local. A Faqs PR was merged before as well so there was conflict due to line numbers. I have created a PR with same changes so as to resolve the conflict.
Purpose
What is the motivation for this PR? What changes does it include? Include as much or as little detail as needed.
If this submission relates to a Jira or GitHub issue, include the issue ID in the title.
Internal Harness contributors - Please edit this summary to include preview links after the preview build finishes.
Merge requirements

[ ] Successful preview build.
[ ] Code owner review.
[ ] No merge conflicts.
[ ] Release notes/new features docs: Feature/version released to at least one prod environment.

PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.

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

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6613bf85a087c78498e84bf0--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6613c105a1c26a8130a23162--harness-developer.netlify.app


OCPBUGS-42783: Use guest DNS resolution in Konnectivity HTTPS proxy by default

What this PR does / why we need it:
When sending traffic through konnectivity (whether proxied or not) we need dns names to be resolved by the data plane. This change ensures we do that (not only for internal service names).
Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes #OCPBUGS-42783
Checklist

[x] Subject and description added to both, commit and PR.
[x] Relevant issues have been referenced.
[ ] This change includes docs.
[ ] This change includes unit tests.

/area control-plane-operator
/jira refresh

/test unit

/lgtm

/cherry-pick release-4.17


Issue when resizing UWP apps

There's a problem with rendering in UWP. Here's the repro:

Open UWP app and navigate to view containing a CarouselView
Maximize UWP window
Slide to next CarouselView item

= Result: Previous item appears to be partially rendered over the current one.

Hi. thanks for your report
Unfortunately, i don't have a windows PC in my own.
Maybe, somebody wants to investigate this issue, solve and make a PR ?)

try 1.6.4-pre

I'll check it out ASAP. Thanks!

@jonasrembratttetrapak I'm glad to know it)
If you like this plugin, you may support it by setting STAR 🌟 :)


(default)-secure nginx.conf

React Boilerplate
First of all thank you for this amazing boilerplate :)
Issue Type

[X ] Feature (https://github.com/mxstbr/react-boilerplate/blob/master/.github/CONTRIBUTING.md#feature-requests)

Description
The provided nginx.conf provides basic security with TLS, but misses important security options that are considered modern but a must have. So currently the nginx config

does provide basic security (tls 1.0, 1.1, 1.2)
does NOT eliminate weak ciphers like RC4 or EXPORT per default (vulnerable to FREAK f.e)
does NOT set  HSTS Header
does NOT insist on his own ciphersuites (attacker could trick the server with downgrading)
does NOT set recommended options for modern nginx ssl conf by Mozilla.

Since it is realistic that users may use this configuration in production, it would be nice to provide solid security configuration for nginx by default in this boilerplate.
This is especially needed when people use the config for the api which (maybe) serves sensitive data.

@supergicko Excellent points! Thank you for pointing that out 😄
Would mind opening a PR with appropriate changes?
How about Apache's .htaccess?

@gihrig:

How about Apache's .htaccess?

As far as I know, .htaccess only can redirect from HTTP to HTTPS ( regarding SSL/TLS configurations).
To achieve the same config as in .nginx.conf , a VirtualHost or Server Config for apache httpd would be needed.

OK, well now it's documented.
Thanks.

Let me know if you need the same config for apache httpd. I would then open a new PR for this purpose only.

Since it is realistic that users may use this configuration in production, it would be nice to provide solid security configuration ...

Let me know if you need the same config for apache httpd.

While I don't think it would be appropriate for this boilerplate to provide a complete httpd.conf, I would welcome an addition to the Apache section of docs/general/server-configs.md outlining an appropriate security configuration.

While I don't think it would be appropriate for this boilerplate to provide a complete httpd.conf, I would welcome an addition to the Apache section of docs/general/server-configs.md outlining an appropriate security configuration.

Ok. Will do it soon and update the PR ok?

Will do it soon and update the PR ok?

Updating this PR is fine 😄

@gihrig done

Thanks so much for the PR, this is fixed and released in 3.4! @supergicko


Add support for blacksheep

Current Situation
We currently don't support blacksheep as a backend.
Proposed Actions
Add blacksheep support.

Closing this in favor of #1110


Briding Header issue

Hi,
This is exactly what I need, really amazing !!
I've been struggling with one issue I'm having those errors when trying to compil the App:
Showing Recent Issues
/Users/tibo/Documents/UNITY/XCODE/UnityView/UNityView/UNityView/ViewController.swift
:0: error: bridging header '/Users/tibo/Documents/UNITY/XCODE/UnityView/UNityView/UnityBridge.h' does not exist
/Users/tibo/Documents/UNITY/XCODE/UnityView/UNityView/UNityView/AppDelegate.swift
:0: error: bridging header '/Users/tibo/Documents/UNITY/XCODE/UnityView/UNityView/UnityBridge.h' does not exist
/Users/tibo/Documents/UNITY/XCODE/UnityView/UNityView/UNityView/main.swift
:0: error: bridging header '/Users/tibo/Documents/UNITY/XCODE/UnityView/UNityView/UnityBridge.h' does not exist
I've been following your tutorial step by step But I can't figue out where it's comign from .. .
If you have any recommendation ? It would be amazing !
Thanks for your time and help :)

First thing I can think of : have you setted your bridging file in your Build Settings ? (Target : NameOfYourProject, Build Settings, Swift Compiler - General, Objective-C Bridging Header)
Second, you have not put the bridging file in your project folder and XCode can't find it.
Hum that's all I can think of yet.

Thanks,
IT seems I managed to fix that part,
I m still having 2 errors, in me AppDelegate.swift
var currentUnityController: UnityAppController!
I'm having used of Undeclared type 'UnityAppController'
aswell
  func application(application: UIApplication, didFinishLaunchingWithOptions launchOptions: [NSObject: AnyObject]?) -> Bool {         currentUnityController = UnityAppController()         currentUnityController.application(application, didFinishLaunchingWithOptions: launchOptions)         return true     }
I managed to fix that one by replacing UnityAppController by UIInputViewController
The last error I'm having is in my main.swift
'Use of unresolved difentifier custom_unity_init'
Do you have any idea how this could be fixed ?
Thank you for all your time, I really appreciate !

Hey @tibewww you should not replace UnityAppController by UIInputViewController as it won't have all the methods from UnityAppController class.
What you should do however is to be sure to have UnityAppController.h imported in UnityBridge.h
Clean up your projet and in the main.swift file you should have :

// Swift 2.3
custom_unity_init(CommandLine.argc, CommandLine.unsafeArgv)
UIApplicationMain(CommandLine.argc, CommandLine.unsafeArgv, NSStringFromClass(UIApplication), NSStringFromClass(AppDelegate))

// Swift 3.0
custom_unity_init(CommandLine.argc, CommandLine.unsafeArgv)
let newUnsafeArgv = UnsafeMutableRawPointer( CommandLine.unsafeArgv ).bindMemory( to: UnsafeMutablePointer.self, capacity: Int( CommandLine.argc ) )
UIApplicationMain( CommandLine.argc, newUnsafeArgv , NSStringFromClass( UIApplication.self ), NSStringFromClass( AppDelegate.self ) )

Also be sure to rename your main function in the main.mm file located in Unity/Classes/main.mm
like so :

int main_unity_default(int argc, char* argv[])
{
@autoreleasepool
{
UnityInitTrampoline();
UnityParseCommandLine(argc, argv);
  RegisterMonoModules();
  NSLog(@"-> registered mono modules %p\n", &constsection);
  RegisterFeatures();

  // iOS terminates open sockets when an application enters background mode.
  // The next write to any of such socket causes SIGPIPE signal being raised,
  // even if the request has been done from scripting side. This disables the
  // signal and allows Mono to throw a proper C# exception.
  std::signal(SIGPIPE, SIG_IGN);

  UIApplicationMain(argc, argv, nil, [NSString stringWithUTF8String:AppControllerClassName]);

}
return 0;
}

and your custom_unity_init function should be declared in UnityUtils.mm

extern "C" int custom_unity_init(int argc, char* argv[])
{
@autoreleasepool
{
UnityInitTrampoline();
UnityParseCommandLine(argc, argv);
    RegisterMonoModules();
    NSLog(@"-> registered mono modules %p\n", &constsection);
    RegisterFeatures();

    // iOS terminates open sockets when an application enters background mode.
    // The next write to any of such socket causes SIGPIPE signal being raised,
    // even if the request has been done from scripting side. This disables the
    // signal and allows Mono to throw a proper C# exception.
    std::signal(SIGPIPE, SIG_IGN);

    //UIApplicationMain(argc, argv, nil, [NSString stringWithUTF8String:AppControllerClassName]);
}

return 0;

}

If you have any problems at all it must mean that you have a problem with the way your project is linked/created.
Just a reminder, UnityBridge.h this file should be located at the top of your project with your xcode project file, not inside it.

HI Matthieu,
Thanks for your time, really appreciate :)
I have updated the few code you mention. and check it. it's all correct.
Seems it's link to the bridging Header, ( I had uncomment all the import to not have the error anymore), now I have put them back, and the error came back so.
My UnityBridge.ch is at the top of the project, in the obj folder.
I attach a screenshot of the structure:

So In the UnityBridge.h I have the import of the UNity App Controler as:
#import "../Unity/Classses/UnityAppController.h"
And in the Bridging Header Key from the Building setup:
objc/UnityBridge.h
This to call the UnityBridge.h
But the error are still remaining as:
/Users/tibo/Documents/UNITY/XCODE/UnityView/objc/UnityBridge.h:11:9: error: '../Unity/Classses/UnityAppController.h' file not found
#import "../Unity/Classses/UnityAppController.h"
^
:0: error: failed to import bridging header '/Users/tibo/Documents/UNITY/XCODE/UnityView/objc/UnityBridge.h'
Do you have any what is wrong in my path ??
Thank a lot for your time taken, I really appreciate

Try to put your bridge file in the same folder as your UnityView.xcodeproj file ie : /Users/tibo/Documents/UNITY/XCODE/UnityView/UnityBridge.h

#import "../Unity/Classses/UnityAppController.h"

Classses ? is it an error on your part when writing it ? or is it the real name of your path ?

Hi, I try to follow your instructions and I can´t solve my UnityBridge.h problem. I am using Swift 3 and Unity 5.5.0f1. Is there any issue or something I need to change. I also have multiple errors on my UnityAppController.h file.

I share my project structure

And the folder structure


Uncaught node.js Error

Hi,
I connected to the drone's Wi-Fi and then opened the app, I could see the UI and video feed updating successfully. However, when I pressed Takeoff the drone popped into the air properly but the app went a pale blue colour with a white fluffy cloud scudding across the page along with the following error message:
Uncaught node.js Error

TypeError: Cannot call method 'log' of null
    at Client.eval (file:///Applications/Nodecopter.app/Contents/Resources/app.nw/app.js:87:11)
    at Client.EventEmitter.emit (events.js:92:17)
    at Client.eval (/Applications/Nodecopter.app/Contents/Resources/app.nw/node_modules/ar-drone/lib/Client.js:130:21)
    at Client._processNavdata (/Applications/Nodecopter.app/Contents/Resources/app.nw/node_modules/ar-drone/lib/Client.js:134:5)
    at Client._handleNavdata (/Applications/Nodecopter.app/Contents/Resources/app.nw/node_modules/ar-drone/lib/Client.js:121:8)
    at UdpNavdataStream.EventEmitter.emit (events.js:95:17)
    at UdpNavdataStream._handleMessage (/Applications/Nodecopter.app/Contents/Resources/app.nw/node_modules/ar-drone/lib/navdata/UdpNavdataStream.js:73:10)
    at Socket.EventEmitter.emit (events.js:98:17)
    at UDP.onMessage (dgram.js:437:8)

All the while the drone continued hovering, I restarted the app at which point the drone landed safely and I was able to recreate this behaviour three or four times.

I'm no longer supporting this library as I don't use it any longer so I'm going to close this issue.


Rebroadcast blocks via process RPC

I think we could check if the block exists after the process_receive_many call to see if there's an error. It'd be nice to tell if the process went through even if you don't get the exact error.

Doing same thing, but without any useful output.
@PlasmaPower even if we check if the block exists after we con't see exact error.

My concern with doing it another way other than using block_processor is if there's another change in the future we might miss copying the functionality again.
Checking for block existence right after sending it to the block processor is a race condition since it's processed in a background thread.
The closest way I can think of to retain the functionality is to have a processing callback but we've tried that before and the problem is if it's even put in to unchecked and later pulled out we'll loose the callback.

I guess now all functionality after
https://github.com/nanocurrency/raiblocks/blob/5e0cb86fa144c4b7193a60c25513217f18586df8/rai/node/node.cpp#L1301
can be moved to rai::block_processor::process_receive_one

Yea that's a good idea, a lot cleaner too I don't know why they're separate in the first place.
I made a patch to do that change but some tests need to be fixed, could you look at those?

Sure


Fix type guard to return the correct type

if it's Promise, we can use .then, .catch and finally:

otherwise, we can't:

Reference: Using type predicates

@all-contributors please add @ofir-zeitoun for code


request: support for dlng and slng

Now that UFO3 spec includes public.openTypeMeta in lib.plist, could we get support for dlng and slng metadata tags?

I misunderstood -- looks like meta table is already supported.


test is not set when crate-type is lib or rlib

Problem
Minimal repro here.
When I run cargo test on a library with a crate-type of lib or rlib, I can't conditionally compile based on test. At first I thought test was not being set, but in the minimal repro you can see that doesn't seem to be the case.
Basically, I have this code:
#[cfg(not(test))]
compile_error!("test not set");

#[cfg(test)]
compile_error!("test set");

And running cargo test gives this output:
error: test set
 --> src/lib.rs:5:1
  |
5 | compile_error!("test set");
  | ^^^^^^^^^^^^^^^^^^^^^^^^^^

error: test not set
 --> src/lib.rs:2:1
  |
2 | compile_error!("test not set");
  | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

error: could not compile `issue-with-test` (lib) due to 1 previous error
warning: build failed, waiting for other jobs to finish...
error: could not compile `issue-with-test` (lib test) due to 1 previous error

Note that this happens without actually setting the crate-type, since lib is the default value. Nonetheless, if I set crate-type to any other type of library, I get the expected result of:
error: test set
 --> src/lib.rs:5:1
  |
5 | compile_error!("test set");
  | ^^^^^^^^^^^^^^^^^^^^^^^^^^

error: could not compile `issue-with-test` (lib test) due to 1 previous error

Maybe this is something known, if so, it would be helpful to document it more clearly.
Steps

Create a new cargo library project with cargo new.
Add conditional compilation based on test.
Run cargo test.

Possible Solution(s)
I tried tracing it down in the cargo source code, but I'm too unfamiliar with it so I don't have any solution as of now (in the case this is indeed unexpected behaviour, which I'd argue it is).
Notes
Minimal repro here.
Version
cargo version --verbose
cargo 1.76.0 (c84b36747 2024-01-18)
release: 1.76.0
commit-hash: c84b367471a2db61d2c2c6aab605b14130b8a31b
commit-date: 2024-01-18
host: aarch64-apple-darwin
libgit2: 1.7.1 (sys:0.18.1 vendored)
libcurl: 8.1.2 (sys:0.4.70+curl-8.5.0 system ssl:(SecureTransport) LibreSSL/3.3.6)
ssl: OpenSSL 1.1.1w  11 Sep 2023
os: Mac OS 14.1.1 [64-bit]

Got time for it.
With crate-type = ["cdylib"], only one rustc invocation with --test flag, which is for building test harness for unit tests.
   Compiling issue-with-test v0.1.0 (/projects/issue-with-test)
     Running `rustc --crate-name issue_with_test --edition=2021 src/lib.rs ... --test ...`
    Finished test [unoptimized + debuginfo] target(s) in 0.14s
     Running `/projects/issue-with-test/target/debug/deps/issue_with_test-fb24bcbe795b0fce`

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

With crate-type = ["lib"] (the default), two rustc invocations. One with --test flag and one without.
   Compiling issue-with-test v0.1.0 (/projects/issue-with-test)
     Running `rustc --crate-name issue_with_test --edition=2021 src/lib.rs ...`
     Running `rustc --crate-name issue_with_test --edition=2021 src/lib.rs ... --test ...`
    Finished test [unoptimized + debuginfo] target(s) in 0.28s
     Running `/projects/issue-with-test/target/debug/deps/issue_with_test-c15d8a057c295028`

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

   Doc-tests issue-with-test
     Running `rustdoc --edition=2021 --crate-type lib --crate-name issue_with_test --test ...`

running 0 tests

So expected. Closing. Thank you!

Makes sense! Thank you!


flutter news template

Steps to reproduce
I am facing issue when I run flutter news template in vs code, it showing something error in buil.gradle version
Expected results
I am facing issue when I run flutter news template in vs code, it showing something error in buil.gradle version
Actual results
I am facing issue when I run flutter news template in vs code, it showing something error in buil.gradle version
Code sample
Code sample
[Paste your code here]

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
[Paste your output here]

Hi @12234e, what errors are you getting? Have you completed the setup stated in the documentation, including the firebase setup?
PS: In the future, please provide the relevant information required to reproduce the issue so that it can be properly investigated.
Thank you

I need only the flutter news template setup tutorial with firebase, I have searched on google but I didn't find any tutorial

Launching lib/main/main_production.dart on sdk gphone64 x86 64 in debug mode...
You are applying Flutter's main Gradle plugin imperatively using the apply script method, which is deprecated and will be removed in a future release. Migrate to applying Gradle plugins with the declarative plugins block: https://flutter.dev/go/flutter-gradle-plugin-apply
Warning: The plugin android_intent_plus requires Android SDK version 34 or higher.
For more information about build configuration, see https://docs.flutter.dev/deployment/android#reviewing-the-gradle-build-configuration.
Warning: The plugin firebase_analytics requires Android SDK version 34 or higher.
For more information about build configuration, see https://docs.flutter.dev/deployment/android#reviewing-the-gradle-build-configuration.
Warning: The plugin firebase_auth requires Android SDK version 34 or higher.
For more information about build configuration, see https://docs.flutter.dev/deployment/android#reviewing-the-gradle-build-configuration.
Warning: The plugin firebase_core requires Android SDK version 34 or higher.
For more information about build configuration, see https://docs.flutter.dev/deployment/android#reviewing-the-gradle-build-configuration.
Warning: The plugin firebase_crashlytics requires Android SDK version 34 or higher.
For more information about build configuration, see https://docs.flutter.dev/deployment/android#reviewing-the-gradle-build-configuration.
Warning: The plugin firebase_dynamic_links requires Android SDK version 34 or higher.
For more information about build configuration, see https://docs.flutter.dev/deployment/android#reviewing-the-gradle-build-configuration.
Warning: The plugin firebase_messaging requires Android SDK version 34 or higher.
For more information about build configuration, see https://docs.flutter.dev/deployment/android#reviewing-the-gradle-build-configuration.
Warning: The plugin flutter_secure_storage requires Android SDK version 34 or higher.
For more information about build configuration, see https://docs.flutter.dev/deployment/android#reviewing-the-gradle-build-configuration.
Warning: The plugin google_sign_in_android requires Android SDK version 34 or higher.
For more information about build configuration, see https://docs.flutter.dev/deployment/android#reviewing-the-gradle-build-configuration.
Warning: The plugin in_app_purchase_android requires Android SDK version 34 or higher.
For more information about build configuration, see https://docs.flutter.dev/deployment/android#reviewing-the-gradle-build-configuration.
Warning: The plugin path_provider_android requires Android SDK version 34 or higher.
For more information about build configuration, see https://docs.flutter.dev/deployment/android#reviewing-the-gradle-build-configuration.
Warning: The plugin share_plus requires Android SDK version 34 or higher.
For more information about build configuration, see https://docs.flutter.dev/deployment/android#reviewing-the-gradle-build-configuration.
Warning: The plugin shared_preferences_android requires Android SDK version 34 or higher.
For more information about build configuration, see https://docs.flutter.dev/deployment/android#reviewing-the-gradle-build-configuration.
Warning: The plugin sign_in_with_apple requires Android SDK version 34 or higher.
For more information about build configuration, see https://docs.flutter.dev/deployment/android#reviewing-the-gradle-build-configuration.
Warning: The plugin sqflite requires Android SDK version 34 or higher.
For more information about build configuration, see https://docs.flutter.dev/deployment/android#reviewing-the-gradle-build-configuration.
Warning: The plugin url_launcher_android requires Android SDK version 34 or higher.
For more information about build configuration, see https://docs.flutter.dev/deployment/android#reviewing-the-gradle-build-configuration.
Warning: The plugin video_player_android requires Android SDK version 34 or higher.
For more information about build configuration, see https://docs.flutter.dev/deployment/android#reviewing-the-gradle-build-configuration.
Warning: The plugin webview_flutter_android requires Android SDK version 34 or higher.
For more information about build configuration, see https://docs.flutter.dev/deployment/android#reviewing-the-gradle-build-configuration.
One or more plugins require a higher Android SDK version.
Fix this issue by adding the following to D:\dev\daily_globe\android\app\build.gradle:
android {
compileSdkVersion 34
...
}

Hey @12234e,
please go to this path: android\app\build.gradle
check that your compileSdkVersion is 34

I did fix it but the error is not fixed yet, error coming one after one,
its very hard to undrestand
On Thu, Aug 1, 2024, 5:06 PM jayprakash Pal @.***>
wrote:

Hey @12234e https://github.com/12234e,
please go to this path: android\app\build.gradle
check that your compileSdkVersion is 34
—
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/152609#issuecomment-2263170236,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWPCJYI7OX5LPUP4ESHG2CLZPI6HDAVCNFSM6AAAAABLYBZIMKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRTGE3TAMRTGY
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi @12234e ,
For the warning go to Android Studio -> Settings  ->SDK Manager -> SDK Platform and download 34 or the latest SDK

Hi @12234e, what error do you get after updating the compileSdkVersion? You can find the instructions to setup firebase in your news app over here https://flutter.github.io/news_toolkit/project_configuration/firebase


Init foot at 1.15.3

https://github.com/deepin-community/fcft/pull/1
https://github.com/deepin-community/tllist/pull/1

TAG: 1.15.3-1deepin
来源 1.15.3-1

/approve


Fix report doesn't scroll down to bottom when receiving new message

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/43600
PROPOSAL: https://github.com/Expensify/App/issues/43600#issuecomment-2171084196
Tests

In account A open a chat with account B, and scroll up a bit (2 or 3 messages)
In account B send a message to account A
In account A when new message arrives, verify the chat report scrolled down to bottom to show the new message
In account A scroll up chat a bit then, from account B Send Pay message to account A
In account A when new message arrives, verify the chat report scrolled down to bottom to show the new message

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

Offline tests

QA Steps

In account A open a chat with account B, and scroll up a bit (2 or 3 messages)
In account B send a message to account A
In account A when new message arrives, verify the chat report scrolled down to bottom to show the new message
In account A scroll up chat a bit then, from account B Send Pay message to account A
In account A when new message arrives, verify the chat report scrolled down to bottom to show the new message

[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 either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[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 the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[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
https://github.com/Expensify/App/assets/114975543/6a902d1a-ab9e-4242-bef4-4ed815999220

Android: mWeb Chrome
https://github.com/Expensify/App/assets/114975543/db577466-7874-45be-a15e-da02239d5628

iOS: Native
https://github.com/Expensify/App/assets/114975543/da34b5f2-274d-4626-90d5-0f138b3c5c41

iOS: mWeb Safari
https://github.com/Expensify/App/assets/114975543/b22d3775-9018-4c0b-b156-1a0343e2c4b9

MacOS: Chrome / Safari
https://github.com/Expensify/App/assets/114975543/8239f832-ddae-4b46-a521-282bef884866

MacOS: Desktop
https://github.com/Expensify/App/assets/114975543/adf2948b-1cde-4c97-a2d6-9aa957f604a7

Reviewer Checklist

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

[X] I verified the steps for local testing are in the Tests section
[X] I verified the steps for Staging and/or Production testing are in the QA steps section
[X] 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)
[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 checked that screenshots or videos are included for tests on all platforms
[X] I included screenshots or videos for tests on all platforms
[X] I verified tests pass on all platforms & I tested again on:

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

[X] 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
[X] I verified proper code patterns were followed (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] 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 either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[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 verified that this PR follows the guidelines as stated in the Review Guidelines
[X] 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)
[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] If a new component is created I verified that:

[X] A similar component doesn't exist in the codebase
[X] All props are defined accurately and each prop has a /** comment above it */
[X] The file is named correctly
[X] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[X] The only data being stored in the state is data necessary for rendering and nothing else
[X] 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)
[X] 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)
[X] All JSX used for rendering exists in the render method
[X] 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

[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 the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[X] I verified that all the inputs inside a form are aligned with each other.
[X] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[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.
[X] 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

https://github.com/Expensify/App/assets/16493223/d45dd8af-b09e-4c66-94fd-66fb67af790f

MacOS: Desktop

https://github.com/Expensify/App/assets/16493223/ef4ff4c3-051a-489f-983c-4e71f0cb823f

Hi @s77rt, could you add the screenshot/videos for the native and mWeb platforms?

@marcochavezf Done!

: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/marcochavezf in version: 9.0.2-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

This PR is failing because of issue https://github.com/Expensify/App/issues/43600
The issue is reproducible in: Web and Desktop
https://github.com/Expensify/App/assets/93399543/65ad3643-b8bc-4833-b54f-d0d2f6dac4dd
https://github.com/Expensify/App/assets/93399543/38475730-8526-4287-9c9b-ce5435ce9823

I am sorry @kbecciv, I cannot reproduce it,
My initial thought is that the scroll-up distance might be too far. There is a maximum scroll-up distance, after which a new message will automatically scroll down. In the first video, I think the font looks bigger, so the three messages take up space, and the space taken is above the limit when the app scrolls down. For the first video, could you reproduce it when you scroll up exactly one or two text message?
cc: @s77rt Are you able to reproduce it?

This is working as expected for me.

🚀 Deployed to production by https://github.com/jasperhuangg in version: 9.0.3-7 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/Julesssss in version: 9.0.5-13 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Importing a VPC

When you import a VPC should it not be also importing associated configured resources? Like a VPC is associated with route table and subnet configuration and others.  Apologies if I missed this in the docs.
terraformer import aws --resources=vpc --filter=aws_vpc=myvpcid --regions=eu-west-1

thanks!

Hi, technically it's possible to do since we have crafted a list of resource connections (ref https://github.com/GoogleCloudPlatform/terraformer/blob/master/providers/aws/aws_provider.go#L43) although for now you'd need to do it manually.

Ah, ok. Thanks!


Publish to PyPi

Hi,
is it possible to publish this to PyPi as a means for functionality till django-ninja#604 gets merged

Hi @baseplate-admin ,
I had planned on cleaning up and fleshing out this repo, with the eventual goal of publishing it on PyPi (and also making the changes to get #604 merged).
Unfortunately I've recently been working on embedded software and haven't quite had the time/motivation to work on web stuff.
If you want to PR in any changes, I'd be happy to take a look at them, otherwise hopefully I'll get to it in the next month or two.
Also, thanks for the work you've been putting in recently trying to get django-ninja into shape. I'm keen to help out once I'm back on the web side of things.

Unfortunately I've recently been working on embedded software and haven't quite had the time/motivation to work on web stuff.

Ah i see. No worries :D. I will wait for your return.

If you want to PR in any changes, I'd be happy to take a look at them, otherwise hopefully I'll get to it in the next month or two.

Unfortunately Vitalik is not available at this point. I did a Pull Request but due to the lack of response i made my own pypi package ( as it was a release blocker for us ) and published it.

Also, thanks for the work you've been putting in recently trying to get django-ninja into shape. I'm keen to help out once I'm back on the web side of things.

About this, I have negative opinion at this point on django-ninja. Things are not looking good on the internet because of django-ninja's lack of maintenance. Even a django developer commented on something that i have no answer to.. Since i use django-ninja on a production basis. I might fork the project and patch upstream ( which i don't want to do ).

All in all thanks :D For your work on this repo and for helping out with some stuffs over at django-ninja


Chessboard colour next to the specific button should correspond to the default for that button. Currently Games, Exercises and Training are swapped

For example,
For Training default board is displayed next to the Games button (red below)

Fixed


Service Schedular Add Note is not working

when i click on add note button , console show error

Not working

what the error coming?

Ok, Working Now


Mobile dark/light mode header

Hey @mikecao ,
as detailed in https://github.com/mikecao/umami/pull/847
the dark/light mode mobile header does not work without the two ##'s within the content.
I literally have no idea why that is, but once I added back both extra #'s to my own deployment, it started working once again.
Any idea there?
Also, if that does not break anything on your end, can we add that extra # back so that the feature works in the main deployment too?
Thanks!

I am having the opposite problem. If I use two ##'s, then it doesn't work at all. Tested on Safari in iOS. And neither setting works in Chrome on iOS.


COMPRESS-124 : Add support for extracting sparse entries from tar archives

COMPRESS-124
Add support for extracting sparse entries from tar archives, including :

Old GNU Format
The sparse map of old GNU is stored in tar header with only 4 sparse headers. If more spar headers exist, they should be stored in the extension block

PAX 0.0 Format
The sparse map of PAX 0.0 Format is stored in tar headers with GNU.sparse.offset and GNU.sparse.numbytes. They may appear more than 1 time, so they cannot be stored in a map.

PAX 0.1 Format
The sparse map of PAX 0.1 Format is stored in tar headers with GNU.sparse.map.

PAX 1.0 Format
The sparse map of PAX 1.0 Format is stored in the head of data file block. Therefore we need to handle it separately when we encounted a PAX 1.0 tar.

The implemention is mainly implemented by the TarArchiveSparseInputStream. It returns 0 when reading the "holes", and the file data from original tar file input stream when reading the sparse content. These are all decided by the sparse headers. The TarArchiveSparseInputStream reads all sparse headers, creates all-zero input streams surrounded by BoundedInputStream and actual tar file input stream surrounded by BoundedInputStream, and combines them together to a single TarArchiveSparseInputStream. Then we can straightly read from TarArchiveSparseInputStream when we encounted a sparse tar entry.
TODO : I noticed in the code that there are some kind of "star sparse data". I didn't find it in GNU Tar Manual, so I don't know how to parse such kind of tars.
Please let me know if something need to be modified. :-) @bodewig

Coverage increased (+0.3%) to 86.979% when pulling 269c522e3910a9c197856e9054a8d0ef7649b322 on PeterAlfreadLee:COMPRESS-124 into 28049d2f89a76c5a4845c12151a483ca7773fb6f on apache:master.

Code just pushed basing on reviews of @tcurdt and @melloware .
Exception for one review opinion :
Is creating a separate class TarArchiveSparseInputStream a good idea or not?
Of course I can make TarArchiveInputStream be able to handle sparse entries, therefore I need to modify the read() and skip() in TarArchiveInputStream when we are reading sparse entries.
The reason why I create a new class TarArchiveSparseInputStream is that I don't want to modify TarArchiveInputStream too much. I want to try my best to keep the TarArchiveInputStream as the original logic as much as possible.
With a separate TarArchiveSparseInputStream, I can replace the input stream to a new TarArchiveSparseInputStream. I don't need to modify the read() or skip() in TarArchiveInputStream.
I'm not sure if creating a single TarArchiveSparseInputStream is a good idea or not.
What do you think?

While I appreciate being careful, I am not a fan of duplicating functionality and interfaces like that. So I am in favor of just one class. Maybe it means that testing needs to improved to be sure all is kept working.
Since @bodewig has the best overview over the project these days I think it would be good to get input from him first.

I'll carve out some time at the weekend. Sorry, haven't got that much time for OSS right now.

First of all, many thanks @PeterAlfreadLee
I agree with @tcurdt that providing the functionality via a single TarArchiveInputStream would be preferable. Maybe we could extract the meet of the read and skip methods into strategy implementations and make the handling of sparse entries another strategy that is triggered when reading said type of entry? That way we could extend the class without making it even more complex itself.
Here I'm just thinking loud, I haven't got any code to show or even just tried to sketch it up. I must admit I haven't even looked at the code in detail, so maybe the idea is complete nonsense.
BTW, star is a pretty old tar implementation by Jörg Schilling that used to be pretty popular before POSIX started to add support for many of the shortcoming that GNU tar addressed in its own way - long file names, big files, non-ASCII file names and all that. It is still available via Sourceforge, I found the manual page at http://schilytools.sourceforge.net/man/man1/star.1.html . IIRC it is BSD licensed so was preferred over GNU tar by the BSDs and some other Unices.

@bodewig Sure. I'll modify my code.
The TarArchiveInputStream could have another handling of read and skip when the entry is a sparse entry. This could easily implemented by calling currEntry.isSparse(). Then I can expand the original code with only a little modification of original code. Therefore I don't need a separate class TarArchiveSparseInputStream.
I'll push my code in these two days.
For the implemenation of reading the sparse entry, I'm combining the BoundedInputStream with the original tar file input stream and the TarArchiveSparseZeroInputStream. They are constructed by reading the sparse headers of currEntry. What do you think about this? Maybe you have some better ideas? @bodewig @tcurdt

Code pushed.
The TarArchiveInputStream can deal with the sparse entries now. There's no spearate class that deals with the sparse entries.

I didn't do a thorough code review but from the diffs it looks OKish. Still not sure about some of the new classes. Either way - thanks for all the work!
It would probably be good to check this out and look at the final code as this is a big change.
I am wondering if our test cases are enough of a safety net.

I am wondering if our test cases are enough of a safety net.

I agree with this. I will try to add more test cases.

@PeterAlfreadLee commit b465bfa contains some minor changes
I've created the site build for the current master branch and published it at https://stefan.samaflost.de/staging/commons-compress-1.20-snapshot/ - looking at the Jacoco results, for example https://stefan.samaflost.de/staging/commons-compress-1.20-snapshot/jacoco/org.apache.commons.compress.archivers.tar/TarArchiveInputStream.java.html we seem to be covering the new sparse code pretty well. Of course more test cases won't hurt.
I'm wondering whether we really want to make the API details public or whether things like the getters and setters for sparse headers in TarArchiveEntry should be hidden instead. As a matter of taste I would have preferred TarArchiveStructSparse to be immutable and have no setters at all.

I'm wondering whether we really want to make the API details public or whether things like the getters and setters for sparse headers in TarArchiveEntry should be hidden instead. As a matter of taste I would have preferred TarArchiveStructSparse to be immutable and have no setters at all.

+1
For TarArchiveEntry, I have the same feeling that the details(getters/setters) should be hidden when I was reading the code.
For TarArchiveStructSparse, I agree that it should be immutable. I will modify this and push another PR.


how to output chinese discription?

i use chinese query e.g. 请对这幅画的构图进行分析 as the paper does, but the model generates the english description. so how to let the model ouputs corresponding chinese description?

You might try ‘请用中文对这幅画的构图进行分析。’  to let the model ouputs corresponding chinese description.

get it. i will try it later

yeah, it works. btw, is it that when finetune the model, the dataset contains chinese instructions?

The dataset for fine-tuning only contains English instructions. Possibly the base model Sharegpt4v has some bilingual ability and has learnt to write art formal analysis through sft.

ok, i will close the issue