[Settings] Update GPO infobar icon, improve some pages and fix bugs

Merge after 0.84.0 release.

Summary of the Pull Request
This PR updates the icon of the GPO managed info bars to a lock symbol.
Additionally this PR

fixes Behavior of CmdNotFound page when policy is configured.
improves order of info bars on PowerOcr page.
improves order of info bars on VCM page.
fixes the Awake page to use the correct enabled state if it is GPO configured.
improves the order of info bars on New+ page.

[!IMPORTANT]

The PowerPreviewPage.xaml will conflict with an other open PR and needs to be updated after merging the other PR.

#33475

The GeneralPage.xaml file will conflict with an other open PR and needs to be updated after merging the other PR.

#34078

The NewPlusPage.xaml conflicts with other PRs and needs to be updated after merging them:

#35000
#34999 (maybe)

After merging the FileActions module PR the new settings page needs to be updated.

#31220

PR Checklist

[x] Closes: #33585
[x] Communication: I've discussed this with core contributors already. If work hasn't been agreed, this work might be rejected
[x] Tests: Added/updated and all pass
[x] Localization: All end user facing strings can be localized
[ ] Dev docs: Added/updated
[ ] New binaries: Added on the required places

[ ] JSON for signing for new binaries
[ ] WXS for installer for new binaries and localization folder
[ ] YML for CI pipeline for new test projects
[ ] YML for signed pipeline

[ ] Documentation updated: If checked, please file a pull request on our docs repo and link it here: #xxx

Detailed Description of the Pull Request / Additional comments
CmdNotFound module page
Old behavior

New behavior

PowerOCR page after change

VCM page after change

New+ page after changes

Validation Steps Performed
Local test build.

Note to me: Update after merge of #33136.

@jaimecbernardo
I like to get this in sone. It is hard to track all the current open PRs for conflicts and requiremed changes. Any idea how to get this in easily?

Blocked because ...

I am waiting for #34078.
I have bad Internet for the next 4 weeks and probably can't work on this PR.

@jaimecbernardo , @crutkas
This PR is ready for review so far. If you like to merge #35880 and #35902 first, I have to update my PR to get it ready again.

Thank you @htcfreek. We're just waiting for some clarity on the exact PRs you've mentioned for this release, but indeed we'd like to include those PRs in this release if we can and only after that we'd get  this PR in.


Adding Hardware devices card - vm overview page

Signed-off-by: Matan Schatzman<EMAIL_ADDRESS>
📝 Description
VM overview page - hardware device card
https://issues.redhat.com/browse/CNV-16685
🎥 Demo

/retest

/lgtm

/lgtm


modified scene rendering with the purpose of optimizing 'compact view'

At this point I cannot 'break' the layout even for the most marginal of cases.
I think this is a good point to get some feedback.
Sorry  I missed the window for automatic merge.

Sorry for the recent changes. I think the heavy lifting is now done, I expect much fewer changes in the coming weeks.
Can I ask that you update your fork with the latest master and resolve the merge conflicts?

of course. Happy to. I'm on it.


Remove tsconfig from npm package

Maybe we can remove tsconfig.*.json from npm because Vscode (maybe other code editor) complains.
They complain about the ../../tsconfig.base.json that doesn't exist.
Maybe I can fix my VSCode configuration to ignore that file, but I think it's a good thing to not reference a file that doesn't exist.

That's not a big deal, but I feel frustrated to alway have: "1 problem" in the "PROBLEMS" section :)

Fixed with latest release


Different result of cross entropy loss between result from model as function and using predict function

Click to expand!
Issue Type
Bug
Source
source
Tensorflow Version
2.8.2
Custom Code
Yes
OS Platform and Distribution
No response
Mobile device
No response
Python version
No response
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current Behaviour?
Firstly, you get a prediction using model as a function, call this predition A; and then you use predict function of the model and get the same seemingly same prediction, call it B.

If you use CategoricalCrossentropy to calculate loss with same label, the loss are different between them.

Standalone code to reproduce the issue
class NLPModel(keras.Model):
  def __init__(self, **kwargs):
    super().__init__(**kwargs)
    self.hidden_layer1 = tf.keras.layers.GRU(400)
    self.outputs = tf.keras.layers.Dense(3, activation="sigmoid")
  def call(self, inputs):
    outputs = self.hidden_layer1(inputs)
    outputs = self.outputs(outputs)
    return outputs
model = NLPModel()
label = tf.constant([[1.,0.,0.]])
prediction = model(tf.constant([[[0.4, 0.5, 0.54,0.4, 0.5, 0.54,0.4, 0.5, 0.54,0.9],
                                  [0.4, 0.5, 0.54,0.4, 0.5, 0.54,0.4, 0.5, 0.54,0.9]]]))
cce = tf.keras.losses.CategoricalCrossentropy()
loss = cce(label, prediction)
def custom_cce(label, prediction):
  return tf.reduce_mean(tf.math.log(tf.matmul(label, tf.transpose(prediction)) / tf.reduce_sum(prediction)))
print("before numpy")
print(prediction)
print(loss)
print("before numpy")
print("after custom_cce")
print(custom_cce(label, prediction))
print("after custom_cce")
prediction = prediction.numpy()
loss = cce(label, prediction)
print("after numpy")
print(prediction)
print(loss)
print("after numpy")

Relevant log output
before numpy
tf.Tensor([[0.5021686  0.48505145 0.5026401 ]], shape=(1, 3), dtype=float32)
tf.Tensor(1.0769439, shape=(), dtype=float32)
before numpy
after custom_cce
tf.Tensor(-1.0875016, shape=(), dtype=float32)
after custom_cce
after numpy
[[0.5021686  0.48505145 0.5026401 ]]
tf.Tensor(1.0875016, shape=(), dtype=float32)
after numpy

@chunduriv I was able to replicate the issue on colab, please find the gist here for reference. Thank you!

@Xinshuai-Lyu,
Thank you for opening this issue.
Development of keras moved to separate repository https://github.com/keras-team/keras/issues.
Please post this issue on keras-team/keras repo. For more details please refer here.

https://github.com/keras-team/keras/issues/16737


Ethereum Sync error in 1.5.0 3145775

Ledger Live Version and Operating System
1.5.0 (3145775)
Motorola One Vision
Android 9
Ledger Nano-X
Expected behavior
Synchronizes nicely. Can add ETH account.
Actual behavior
Synchronization error.
Tried cache clear.
Tried data clear.
Tried reinstalling.
Fail at adding Ethereum account.
Steps to reproduce the behavior
See above.
Note: Tried on another phone (Moto G4) with 1.5.0 (1048622). Worked nicely.

You guys need to work on your customer support... Anyhow, here is more info as relayed to Ledger Support representative:
Upgrading Moto G4 to latest Ledger LIve Mobile version yielded:  1.5.0 (1048623) and synchronization worked.
Attaching screenshot. This is on the (non working) 1.5.0 (3145775) when trying to add the ETH account from Ledger Nano X. Accounts that worked without problem: BTC, ZEC, LTC, XRP.

Could somebody explain what the significance of the number in parenthesis after the version, i.e. 1.5.0 (3145775) is and how it relates to github versions? Also why is it different between phones.

Extracted APKs from respective phone, unpacked and compared, results:
Moto G4, lib = armeabi-v7a
Moto One Vision = arm64-v8a

Uninstalled arm64-v8a version from Moto One (installed from PLAY) and installed the armeabi-v7a manually. IT WERKS!

thanks for the report. we'll investigate. cc @KhalilBellakrid  @MortalKastor

@gre any news?

Any news? Same issue here.
Samsung s8 active Android 9

makes angry noises

This is happening on Moto g7; well for last three day's or so

Error Syncronized ETH in my MotoG7 Power Android 9 (Spanish), I report this probem with support but  not resolved

This is Crazy.... I test now in Moto G6 and work fine.....%$"$$.... I see in Moto G6 about app is 1.5.0 (1048623) and in my Moto G7 in about is 1.5.0 (3145775) and not work (problem synchronize ETH account)...... What is the different????

Where I download manual this version 1.5.0 (1048623)(not in googlePlay)???

@yvjos You can use an app (from Play Store) called "Apk Extractor" to get the APK from your Moto G6.
You then need to uninstall Ledger Live from Moto G7, transfer APK from G6 to G7 and install manually - allowing unknown sources. You should then disable Play Store from auto-updating applications. Play Store will say that there is a newer version.
I've created a separate issue/request to publish APKs. Should be a no-brainer really. But no response.

Thanks very much

Ready... Perfect... I got the app 1.5.0 (1048623) from the G6 with Apk extractor. I put it in my G7 and installed. Now works fine. Thank you.

Please the development team Ledger release a new version to correct this problem.

1.6.0 has been released and it seems to solve the issue. Or, to quote, Play Store's "what's new":
"Minor Fixes."

Maybe the internal discussion on their JIRA were intense but not reflected here. Which is a lousy setup to being with if you really are open source.
But the communication or lack thereof is reaaaally bad for your business guys.
Then again, somebody decided that JavaScript was a suitable foundation to build this on...

except most of these bugs are not due to JavaScript but to explorers and our internal (C++) lib (JS is mainly just the interface, our backends/internal libs are in fact not in JS).
@dslutej the bug is fixed in your side? We plan to deploy a second batch of fixes soon.

1.6.0 didn't help me at all. The strange thing is newly added Eth account syncs well. The old one doesn't. Cleaning cache / re-install doesn't help

1.6.0 did not solve the issue. It seems to work until a new transaction is sent to account. Then it's back to sync error.

When bashing JS-choice I was referring to app desktop+mobile. Once upon a time JS infected the browsers, and became standard. Now it is infecting apps. 🤪 Possibly I am just getting old and grumpy. Possibly.

Status: does not work with 2nd largest crypto on common android phones incl android one devices.
Several weeks now. Devs and Support show abismal interest.

We're sorry you are experiencing issues but as I said, we are actively working on the problem and expect to fixes mobile sync issues in a second batch of fixes.
We expect this to happen in context of #1058 PR.

Fix has been provided.


add Dart, Gazebo, OpenAI multi-agent competition env to the tools in the RL part.

As the title. Sorry I cannot write Japanese.

Thank you for contributing! I added Japanese descriptions to your ones.(fe0de887fe4c26e6b90081453ecc2624cb7d2d04).


elastalert-test-rule fails with alert_text_jinja

Elastalert2 2.0.4
Python 3.9
I'm testing alert_text using jinja templates and it fails using the elastalert-test-rule:
/opt/elastalert $ elastalert-test-rule --config config.yaml --alert toto.yaml
Traceback (most recent call last):
  File "/usr/local/bin/elastalert-test-rule", line 8, in <module>
    sys.exit(main())
  File "/usr/local/lib/python3.9/site-packages/elastalert/test_rule.py", line 445, in main
    test_instance.run_rule_test()
  File "/usr/local/lib/python3.9/site-packages/elastalert/test_rule.py", line 420, in run_rule_test
    hits = self.test_file(copy.deepcopy(rule_yaml), args)
  File "/usr/local/lib/python3.9/copy.py", line 146, in deepcopy
    y = copier(x, memo)
  File "/usr/local/lib/python3.9/copy.py", line 230, in _deepcopy_dict
    y[deepcopy(key, memo)] = deepcopy(value, memo)
  File "/usr/local/lib/python3.9/copy.py", line 172, in deepcopy
    y = _reconstruct(x, memo, *rv)
  File "/usr/local/lib/python3.9/copy.py", line 264, in _reconstruct
    y = func(*args)
  File "/usr/local/lib/python3.9/copyreg.py", line 95, in __newobj__
    return cls.__new__(cls, *args)
TypeError: __new__() missing 1 required positional argument: 'source'

But it doesn't crash when using elastalert --config config.yaml --rule toto.yaml --verbose.
I might not use it correctly, as I did not find the way refer to the rule parameter using jinja, as it doesn't put values in some of my field, but this might be another issue, as I do not see self.rule passed to the jinja renderer.
Part of the rule:
name: toto
index: [...]

type: metric_aggregation

query_key:
  - customer
  - customer.servername

buffer_time:
  minutes: 10

metric_agg_key: cpu.utilization
min_doc_count: 2
metric_agg_type: max
max_threshold: 20

alert_text: >+
   CPU Utilization with more than {{min_doc_count}} occurences ({{num_matches}}) in {{buffer_time}}
   and more than {{max_threshold}}% on {{_data['customer.servername']}}.

   Rule name: {{name}}

alert_text_type: alert_text_jinja
alert_subject: "{0} - CPU Utilization {1} occurences of more than {2}%"
alert_subject_args:
  - customer.servername
  - min_doc_count
  - max_threshold

Output from elastalert --config config.yaml --rule toto.yaml --verbose:
TESTSERVER - CPU Utilization 2 occurences of more than 20%

CPU Utilization with more than  occurrences (8) in  and more than % on TESTSERVER.
Rule name:

In test_rule.py it's performing a deepcopy on the load rule object. Inside of that object there's a Jinja "Template" instance, which is causing problems with the deepcopy function.
If we avoid deepcopying this Template object the test completes correctly. For example, in test_rule.py, the following change prevents the crash:

I wonder if Template objects aren't deepcopy compliant then perhaps they should be overriding the deepcopy function, but that is really outside the scope of this project.
@drakaru, as the Jinja Template PR submitter in #70, do you have any thoughts on this?

Apologies, I meant to bring this up in discussions as I ran into the same issue and wasn't sure what the best solution was.
(As an aside this was present before #70)
I had a look when I first ran into this error, Jinja templates, as you mention, are not deepcopyable: https://github.com/pallets/jinja/issues/758#issuecomment-562742919
We need a way of avoiding copying the templates.
Your solution does this, though I don't know what the prefered way to do this is.
Perhaps that is fine, I hadn't considered that as an option,
I was looking at decoupling the compiled template from the rule but that is... not trivial.
Before I made any changes only string templates were supported, directly from the rule yaml.
Templates loaded from a string within the rule, are not cached automatically by jinja.
Presumably this is why the compiled template is stored in the rule.
Jinja caches templates loaded from the filesystem, this required creating a jinja environment (see loaders.py:100)
https://jinja.palletsprojects.com/en/2.11.x/api/#high-level-api
I think placing it there is an error on my part, it should be part of the config (customising it via yaml is another issue)
However the rendering takes place within the alerter "create_alert_body", which only has access to the rule and the match and not to the global(?) config
  File "...\elastalert\alerts.py", line 264, in create_alert_body
    body += str(BasicMatchString(self.rule, match))
  File "...\elastalert\alerts.py", line 151, in __str__
    self._add_custom_alert_text()
  File "...\elastalert\alerts.py", line 70 in _add_custom_alert_text
      alert_text = self.rule.get("jinja_template").render(**self.match,
                                                                **{self.rule['jinja_root_name']: self.match})

Thanks for the additional context. I'll PR my simple solution for now. We can always improve it if a better alternative comes along.


Failing to fetch chain ID and fork block number

Component
Anvil
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
No response
What command(s) is the bug in?
No response
Operating System
Windows
Describe the bug
The following functions now fail when using setup with the most recent commits. I am using the same RPC URL as I did previously:
https://github.com/foundry-rs/foundry/blob/b78509fb8e11b7f58a0021cd900b7c7a2d3be503/anvil/src/config.rs#L776-L777
https://github.com/foundry-rs/foundry/blob/b78509fb8e11b7f58a0021cd900b7c7a2d3be503/anvil/src/config.rs#L792-L794
It fails with:
thread 'main' panicked at 'Failed to get fork block number: HTTPError(reqwest::Error { kind: Request, url: Url { scheme: "https", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("eth-mainnet.g.alchemy.com")), port: None, path: "/v2/TIWiJhtGeXmmhTL2GmBFLUGrKE5vrbZD", query: None, fragment: None }, source: hyper::Error(Connect, "invalid URL, scheme is not http") })', /Users/bigmac/.cargo/git/checkouts/foundry-44353293f4b0a5c1/b78509f/anvil/src/config.rs:794:30

hmm does this always result in an error or just sporadically?
should definitely convert the panics into errors here.

It always results in a panic yeah.

so the error looks like it's not using tls for some reason.
was not able to reproduce this on mac.
likely a windows issue, will cut release after #3951 which should definitely enable it.

so the error looks like it's not using tls for some reason. was not able to reproduce this on mac.
likely a windows issue, will cut release after #3951 which should definitely enable it.

Sounds good! Seems to be fixed on Mac with that merge

so the error looks like it's not using tls for some reason. was not able to reproduce this on mac.
likely a windows issue, will cut release after #3951 which should definitely enable it.

confirmed works on windows now as well


Jv/rox 8737 write script to run rox in openshift 4 and do performance testing

It would also be nice if the readme mentioned any required environment variables that need to be set like DOCKER_USERNAME and TEARDOWN_SCRIPT, otherwise you end up getting errors like the following one:
./start-central-and-scanner.sh: line 17: DOCKER_USERNAME: unbound variable


Help Needed to Access Model Architectures and Weights in Meltingpot Assets

I'm currently working with the pretrained models provided in the assets from setup.py, available at this URL (http://storage.googleapis.com/dm-meltingpot/meltingpot-assets-2.1.0.tar.gz). My goal is to utilize these models as a baseline to code an analysis pipeline for further research and comparison.
Challenges Encountered
Despite my background predominantly in PyTorch, I have invested time in learning TensorFlow to understand how to effectively work with TensorFlow models. However, I've encountered significant challenges:
Accessing Model Attributes: The architecture and weights of the pretrained models seem to be deeply encapsulated within the provided assets. Standard methods to extract these details like accessing graph and trainable_variables, as suggested by TensorFlow tutorials, have been unsuccessful.
Interacting with the Model: I've tried accessing the "graph" and "node" fields while exploring the model through the PermissiveModel and TF2SavedModelPolicy wrapper but failed to understand the printouts.
Performance Issues: A single rollout of 200 timesteps for the predator_prey__alley_hunt took about half an hour, indicating that I might not be interacting with the models in the intended manner.
Could you provide any guidance or methods to:

Access these model properties more effectively?
Understand the model layers and retrieve the trained weights?

Any assistance, pointers, or documentation would be greatly appreciated!

@jagapiou is the expert on this since I believe he wrote PermissiveModel. He is probably the one best placed to answer this. I do know why the structure is so confusing though.. It's because of the history of these saved models. We trained these agents in Jax and initially saved them using a library that was never released in open source. So our release process involved converting the files we saved in our format into TF2 SavedModels since TF2 SavedModel is available in open source.
On performance, 200 timesteps taking 30 minutes is much too slow, by several orders of magnitude I think.

I didn't write permissive model I'm afraid: it's a piece of internal code we were given permission to open source.
We've not used these bots for any purpose other than executing the SavedModel. For this we definitely get faster than 0.1 steps per second. If all you want to do is run the bots on a Scenario, there's code that does that here:
https://github.com/google-deepmind/meltingpot/blob/957ce59e6f463f7720c6164f71fe2eb890cfc242/meltingpot/utils/evaluation/evaluation.py#L340C14-L340C37
Post-training, we don't access the weights or the architecture ourselves, so not sure how you'd go about doing that.

I  just asked someone who was involved in creating some of the tools we used to produce these models, and he told me that one reason it's hard to extract the weights and architecture is that the saving process converts the weights to constants in the tfgraph. So there's no distinction between the constants that are weights and the constants that are not weights (like architecture parameters).

Thank you all for your assistance in addressing my issues! I now have a clearer understanding of the difficulties involved in retrieving model parameters from the published assets.
I'm glad to report that I've made progress on the rollout speed. It now takes only 1 second per episode of 200 steps.
I would continue to explore other resources of pretrained models like those from the meltingpot challenge 2023. Do you have any recommendations for additional meltingpot study resources?
Additionally, I would like to address a new challenge I'm facing. I'm currently working on retrieving a Unicode-style format out of the RGB format field of video. The goal is to easily identify the position of opponents, walls, apples, and other elements. Is there any guidance or documentation to help me approach this task effectively?
Once again, I deeply appreciate your timely guidance and explanations, which have proven immensely valuable to me.

You can add custom observations that surface all the information. Take a look at the tutorial and documentation around how to create and modify substrates.

Sounds like your problem is solved @QLs-Learning-Bot so gonna close this out. Feel free to reopen.


Exit on empty set of choices

echo -n "" | pick

should not come up with a selection ...

See #62.

OK, I've not digged in the cementary of issues ... but see no decision in #62  ... close this also?

See #62.

I'm not in favor of the proposed behavior. Other interactive utilities
such as less/more does not exit in the case of absent input:
$ less </dev/null

Other interactive utilities such as less/more does not exit in the case of absent input

Can't confirm this for: cat and more on HP-UX 10.20, NetBSD 7.1 & Solaris 9, cat from GNU coreutils 8.23, more from  util-linux 2.25.2, less (358, 458 and 481) ...


Image Panorama

If the image is not in a normal format that can be fit in a 16:9 or 8:5 screen, and is "landscape" it should be in panorama mode, ideally based on information density of the image. However if it is portrait then it should at least show the image thumbnail before doing a top-to-bottom pan.

I think this is the kind of problem that will be tackled if we ever face it, but not worry too much before that.


[1] Enable the log-based-alert by default

Is your feature request related to a problem? Please describe.
Enable the log-based-alert by default in opensearch
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
Definition of done:
Log based alert enabled by default

PR in progress - https://github.com/elastisys/compliantkubernetes-apps/pull/937


Rename flow meter io code fxn names

Summary

rename flow meter io code fxn names

Changelist

Changed flowmeter io code naming from Io_FlowMeter_x -> Io_YS201_x

Testing Done

Resolved Issues

Checklist
Please change [ ] to [x] when you are ready.

[ ] I have read and followed the code conventions detailed in README.md (This will save time for both you and the reviewer!).
[ ] If this pull request is longer then 500 lines, I have provided explicit justification in the summary above explaining why I cannot break this up into multiple pull requests (Small PR's are faster and less painful for everyone involved!).

inactive


update Clusternet architecture

Signed-off-by: Di Xu<EMAIL_ADDRESS>
What type of PR is this?
kind/documentation
What this PR does / why we need it:
adding clusternet-scheduler into Clusternet architecture
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

Codecov Report

Merging #206 (d281eed) into main (8c200c9) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head d281eed differs from pull request most recent head 7d7efcc. Consider uploading reports for the commit 7d7efcc to get more accurate results

@@          Coverage Diff          @@
##            main    #206   +/-   ##
=====================================
  Coverage   8.59%   8.59%
=====================================
  Files         35      35
  Lines       4070    4070
=====================================
  Hits         350     350
  Misses      3693    3693
  Partials      27      27

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 8c200c9...7d7efcc. Read the comment docs.


Search for Russian letter range [а-яА-Я ] misses the letters ё and Ё

I have a text file test.txt with the following contents:
Ёжик под зелёной ёлкой.

My locale is set with LC_ALL=ru_RU.utf8. Vim behaves strangely: I launch it with
vim -u NONE test.txt

Then I do :%s/[а-яА-Я ]/./g, and the text transforms into
Ё...ё...ё...

For comparison, grep does correctly highlight all the letters as Russian letters when I call it like this:
$ grep --color '[а-яА-Я ]' test.txt
Ёжик под зелёной ёлкой.

(All letters in the above output of grep are red, period is not — as expected.)
Similarly, sed also works as expected:
$ sed 's@[а-яА-Я ]@.@g' test.txt
...

Hm, ё is 'ё' U+0451 Dec:1105 CYRILLIC SMALL LETTER IO (io) ё, while я is
'я' U+044F Dec:1103 CYRILLIC SMALL LETTER YA (ja) я.
Also Ё is 'Ё' U+0401 Dec:1025 CYRILLIC CAPITAL LETTER IO (IO) Ё, while А is
'А' U+0410 Dec:1040 CYRILLIC CAPITAL LETTER A (A=) А.
So both letters are clearly out of your range. I would say Vim is correct here.

2017-06-07 14:17 GMT+03:00 Christian Brabandt<EMAIL_ADDRESS>
Hm, ё is 'ё' U+0451 Dec:1105 CYRILLIC SMALL LETTER IO (io) ё, while я
is
'я' U+044F Dec:1103 CYRILLIC SMALL LETTER YA (ja) я.
Also Ё is 'Ё' U+0401 Dec:1025 CYRILLIC CAPITAL LETTER IO (IO) Ё, while
А is
'А' U+0410 Dec:1040 CYRILLIC CAPITAL LETTER A (A=) А.
So both letters are clearly out of your range. I would say Vim is correct
here.

Not correct, not semantically. What Vim does is deliberately ignoring
LC_COLLATE while grep acts according to this category which puts “ё”
between “е” and “ж” like in the Russian alphabet.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to<EMAIL_ADDRESS>For more options, visit https://groups.google.com/d/optout.

Not correct, not semantically. What Vim does is deliberately ignoring
LC_COLLATE while grep acts according to this category which puts “ё”
between “е” and “ж” like in the Russian alphabet.

I'm not really sure that LC_COLLATE or even any LC_* influences this. Even if I unset all LC_* variables and set LC_ALL=en_US.UTF-8, I still get the expected behavior of grep and sed.

yeah I thought I would be missing something.

2017-06-07 16:47 GMT+03:00 Ruslan Kabatsayev<EMAIL_ADDRESS>
Not correct, not semantically. What Vim does is deliberately ignoring
LC_COLLATE while grep acts according to this category which puts “ё”
between “е” and “ж” like in the Russian alphabet.
I'm not really sure that LC_COLLATE or even any LC_* influences this. Even
if I unset all LC_* variables and set LC_ALL=en_US.UTF-8, I still get the
expected behavior of grep and sed.

You need to set LC_COLLATE to some locale that uses cyrillic letters
on its own, but has different alphabet (specifically the one which
does not have “ё” between “а” and “я”). I do not know how libc authors
determine defaults for languages foreign to locale, but most likely
they just took DUCET (Default Unicode Collation Element Table) and
only altered needed locales, this is the intended DUCET usage after
all: (from http://unicode.org/reports/tr10/)

Instead, the goal of DUCET is to provide a reasonable default ordering for all scripts that are not tailored. Any characters used in the language of primary interest for collation are expected to be tailored to meet all the appropriate linguistic requirements for that language. For example, for a user interested primarily in the Malayalam language, DUCET would be tailored to get all details correct for the expected Malayalam collation order, while leaving other characters (Greek, Cyrillic, Han, and so forth) in the default order, because the order of those other characters is not of primary concern. Conversely, a user interested primarily in the Greek language would use a Greek-specific tailoring, while leaving the Malayalam (and other) characters in their default order in the table.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to<EMAIL_ADDRESS>For more options, visit https://groups.google.com/d/optout.

For example check the following command:
sed 's/[^а-яА-Я]/./g'

run in ru_RU.UTF-8 locale and in uz_UZ.UTF-8 locale on the following input:
Input:
ЀЁЂЃЄЅІЇЈЉЊЋЌЍЎЏАБВГДЕЖЗИЙКЛМНОПРСТУФХЦЧШЩЪЫЬЭЮЯабвгдежзийклмнопрстуфхцчшщъыьэюяѐёђѓєѕіїјљњћќѝўџѠѡѢѣѤѥѦѧѨѩѪѫѬѭѮѯѰѱѲѳѴѵѶѷѸѹѺѻѼѽѾѿҀҁ҂ ҃ ҄ ҅ ҆ ҇ ҈ ҉ҊҋҌҍҎҏҐґҒғҔҕҖҗҘҙҚқҜҝҞҟҠҡҢңҤҥҦҧҨҩҪҫҬҭҮүҰұҲҳҴҵҶҷҸҹҺһҼҽҾҿӀӁӂӃӄӅӆӇӈӉӊӋӌӍӎӏӐӑӒӓӔӕӖӗӘәӚӛӜӝӞӟӠӡӢӣӤӥӦӧӨөӪӫӬӭӮӯӰӱӲӳӴӵӶӷӸӹӺӻӼӽӾӿ

(basically all unicode codepoints from U+0400 to U+04FF, in order, inclusive)
ru_RU.UTF-8 output (ru_UA and en_US have the same):
ЀЁЂЃЄЅІЇЈЉЊЋЌЍЎЏАБВГДЕЖЗИЙКЛМНОПРСТУФХЦЧШЩЪЫЬЭЮЯабвгдежзийклмнопрстуфхцчшщъыьэюяѐёђѓєѕіїјљњћќѝўџ.................................................ҊҋҌҍҎҏҐґҒғҔҕҖҗҘҙҚқҜҝҞҟҠҡҢңҤҥҦҧҨҩҪҫҬҭҮүҰұҲҳҴҵҶҷҸҹҺһҼҽҾҿ.ӁӂӃӄӅӆӇӈӉӊӋӌӍӎ.ӐӑӒӓӔӕӖӗӘәӚӛӜӝӞӟӠӡӢӣӤӥӦӧӨөӪӫӬӭӮӯӰӱӲӳӴӵӶӷӸӹ......

uz_UZ.UTF-8 output:
ЀЁЂЃЄЅІЇЈЉЊЋЌЍ.ЏАБВГДЕЖЗИЙКЛМНОПРСТУФХЦЧШЩЪЫЬЭЮЯабвгдежзийклмнопрстуфхцчшщъыьэюяѐёђѓєѕіїјљњћќѝ.џ.................................................ҊҋҌҍҎҏҐґ..ҔҕҖҗҘҙ..ҜҝҞҟҠҡҢңҤҥҦҧҨҩҪҫҬҭҮүҰұ..ҴҵҶҷҸҹҺһҼҽҾҿ.ӁӂӃӄӅӆӇӈӉӊӋӌӍӎ.ӐӑӒӓӔӕӖӗӘәӚӛӜӝӞӟӠӡӢӣӤӥӦӧӨөӪӫӬӭӮӯӰӱӲӳӴӵӶӷӸӹ......

You may see that e.g. Ў is no longer in range (I actually have no idea why most of the stuff above is in range).

@10110111, stumbled upon your comment accidentally and decided to test on my end.
$ set LC_ALL=ru_RU.utf8

$ grep --version
grep (GNU grep) 3.0

$ echo Ёжик под зелёной ёлкой. | grep --color "[а-яА-Я ]"
Ёжик под зелёной ёлкой.
^           ^    ^    ^

Ё, ё and . are not painted red.

@vim-ml, sorry, but I can’t see what you mean.
$ chcp 65001
$ set LC_ALL=ru_RU.utf8
$ locale
LANG=
LC_CTYPE="ru_RU.utf8"
LC_NUMERIC="ru_RU.utf8"
LC_TIME="ru_RU.utf8"
LC_COLLATE="ru_RU.utf8"
LC_MONETARY="ru_RU.utf8"
LC_MESSAGES="ru_RU.utf8"
LC_ALL=ru_RU.utf8

ru_RU stands for Russian, very Cyrillic to me, so I expect all letters of the alphabet to be processed with [А-я]. If one has to add Ёё explicitly, then something is very wrong with the implementation. Imagine Xx would require [A-zXx].

@sergeevabc Unicode handling in Vim was bad at all times as it was lacking at all at the beginning, hard to do on your own at present and Bram is very reluctant to introduce external dependencies, which is though understandable as they have good chance of forcing to drop support for some architectures. For instance, even now all ranges in [] are literal ranges on leading unicode codepoints of grapheme clusters with unicode &encoding, so the behaviour is expected*. Also you must not use [A-z] to mean [A-Za-z], there is a bunch of characters between Z and a which you most likely did not intend to match (and even if you did matching them explicitly is normally more readable).
PS: @vim-ml is a bot which posts from the mailing list, you may see actual name at the bottom in the signature as bot again stopped posting any names at the top (or did it post them at all? Sometimes I wonder that). BTW, can that thing if not post a link to a google groups thread, then at least just something that will make it explicit that this comes from the bot at the top? I bet it would be less confusing if only it was named vim-ml-bot.

And you also will have troubles matching strings with combining characters with []: will have to use [=c=] (or \Z if you are fine with what it means to the whole pattern at once) to match a single character with or without combining characters and I have no idea how to use [] to match combining characters themselves, or how to use [==] in a range.

@ZyX-I : In the Latin alphabet there are a bunch of characters between Z and a, but Russian Cyrillic has (apart from the problematic "io") exactly 32 letters, and the small letters follow the capitals in Unicode with nothing between capital ya and small Cyrillic a: therefore [А-яЁё] does catch them all. (It doesn't catch Ukrainian dotted i, Yugoslav j, or any other letters used in Cyrillic but not in post-1917 Russian.)
Best regards,
Tony.

@tonymec @sergeevabc did not only use that notation for Cyrillic:

Imagine, for example, Latin pair Xx would require [A-zXx], what would anglophones feel?

. Also it is implementation detail. And grep with glibc’s ERE or BRE which do follow LC_COLLATE think that both A-z and А-я are invalid ranges and valid variants in unicode locale are just the opposite: a-Z and а-Я (guess at least first is defined somewhere in unicode standard though).
BTW, grep with pcre (-P) does not follow LC_COLLATE as well.

BTW, for the first post where ё is not painted properly: grep does not implement regular expressions itself like Vim does, it merely uses either one from libc or libpcre (or, at least, GNU grep does). So the any collation errors in grep (if it is GNU grep) are really collation errors in libc (as you did not tell it to use PCRE in your example) which in turn may be just wrong locale definitions.

On Tue, Nov 14, 2017 at 10:36 PM, Nikolai Aleksandrovich Pavlov
<EMAIL_ADDRESS>wrote:

@tonymec @sergeevabc did not only use that notation for Cyrillic:

Ah, all right; I read too fast (as BTW I often do), sorry.

. Also it is implementation detail. And grep with glibc’s ERE or BRE which
do follow LC_COLLATE think that both A-z and А-я are invalid ranges and
valid variants in unicode locale are just the opposite: a-Z and а-Я (guess
at least first is defined somewhere in unicode standard though).

Since (Latin) U+0041 A comes before U+007A z, and (Cyrillic) U+0410 А
before U+044F я, in both Unicode codepoint sequence and Latin or
Russian (respectively) dictionary order, I don't see why [A-z] or
[А-я] would be invalid. If some program rejects them, then maybe it's
a bug in that program; but that has nothing to do with Vim. As you
say, implementation detail. [A-z], however, is a little weird in that,
in C (i.e. Unicode codepoint number or, in this case, US-ASCII byte
value) collating sequence it includes, as you said earlier, six
nonalphabetic characters, so [A-Za-z] is more prudent for (unaccented)
Latin.
Best regards,
Tony.

I am not aware of any set standard for upper-first or lower-first dictionary order in either of the languages. More, UCA (Unicode Collation Algorithm) in http://www.unicode.org/reports/tr10/tr10-36.html explicitly states in more then one place that this parameter is not only specific for the language, it is in many cases specific to the use-case. If I read that correctly, it is up to the locale file to define what the case ordering will be, and lower first (lower lesser then upper) seems logical to me.

AFAIK, case is irrelevant in dictionary collation algorithms (in C, or  in Vim, it isn't): I wouldn't want to see all proper names together before or after all common names beginning by the same letter in a dictionary which happened to use all-lowercase for the latter, i.e. I want to see e.g. the numeral один (meanig "one") and the Scandinavian god Один (Odin), both together (if both are listed) between одеяние and одинаковый, as in fact my Russian-French dictionary (published in Moscow) does. OTOH when sorting file names in a directory listing I make allowances for either C or en_US collating sequences, and I'll look for Makefile either at he top (before alloc.h) in C sequence, or near the middle (between main.c and mark.c) in en_US sequence. But maybe I misunderstood you.


[Sema] Make typealiases in protocols available for nested type lookup.

What's in this pull request?

protocol TestProto {
  typealias X = Int
}

struct Foo : TestProto {
  let a : X
}

This involved a couple complications, mostly making the distinction between typealiases whose definitions contain associated types and those which don't:

Only check final component of compound idents for existential-typeness, so that it is legal to refer to a nested typealias inside the existential.
New diagnosis for trying to use typealias which is an alias for an associated type outside of the defining protocol.
Add check on member lookup to omit typealiases to assoc types, similar to existing treatment of assoc types.
Added test.

This PR arises out of the conversation in this pull https://github.com/apple/swift-evolution/pull/321 where @lattner was surprised that this didn't already work (I was surprised too - oops.).
Also note that all of this is currently disabled by default and enabled by the -enable-protocol-typealiases flag (done in https://github.com/apple/swift/pull/2803).
Resolved bug number: (SR-)

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    All supported platforms     | @swift-ci Please smoke test and merge
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    All supported platforms     | @swift-ci Please test and merge
    OS X platform               | @swift-ci Please test OS X platform
    OS X platform               | @swift-ci Please benchmark
    Linux platform              | @swift-ci Please test Linux platform

Lint Testing
    Language     | Comment
    ------------ | -------------
    Python       | @swift-ci Please Python lint

Note: Only members of the Apple organization can trigger swift-ci.

@swift-ci Please test

@DougGregor Would you mind taking a quick look at this? Thanks!

@gregomni I have a set of changes I'm working on here -- take a look at https://github.com/slavapestov/swift/commit/358ff8f4173fcd01fbdbac3a84573ebb2671bac7

@slavapestov That rearrangement looks great! I don't think it conflicts with / directly intersects the changes here.

Sounds good! One thing I noticed is that the current code breaks when the typealias names an associated type, but as an argument of a bound generic. Eg,
protocol P { associatedtype A; typealias T = [A] }
I'll have an updated version of my patch ready tomorrow.


[CWS] CGroup tracking improvements

What does this PR do?

fix docker container id not being properly inferred from cgroup
fix incorrect attribution of a container id to a process with a cgroup
fix cgroup/container context being attributed to the wrong process
fix incorrect cgroup_tracing event data bound check
avoids tracking root cgroups
re-enable the TestCGroup/systemd test

Motivation
Describe how to test/QA your changes
Possible Drawbacks / Trade-offs
Additional Notes

/merge


Helper function to simply check if the user is logged in

What would you like to be added:
Trying to grok the code and think that it's pretty awesome that you can hand off the request to this library and it takes care of authenticating the user. However, we set up Cloudfront to be on a wildcard domain, and we have logic in our Viewer Request function to inspect the Host header and store that in another header for our Origin Request function. What I would like is a simple function to determine if the user is authenticated or not. With that, I would know when to trigger our custom logic.
Although, supporting multiple domains would be interesting. Maybe that's a separate request though.
Why is this needed:
It'll just give us some options when integrating this package with an existing viewer request function. The only other way would be to inspect the output of the handle function.

Hi @keokilee,
Thanks for raising this issue and submitting a PR. I understand that you want to apply some custom logic to the request after authentication with Cognito is taken care of.
In #20, the issue creator says:

For my use case I'd love to add a callback to the handle function which allows me to change the return logic on the basis of a user's decoded token. For example, to return a 403 error if a user doesn't have a Cognito group granting them access.

I'm wondering if this approach would work for your use case?
Regards,

Yeah, I think that'd work. Just needed something simple to check if the user is authenticated, but being able to hook into the authentication response and add custom handling would be great as well.

Not sure if this would make sense for a pull-request as it would constitute as breaking change to the API for anyone already doing enrichment of the authenticator.handle return.
I've internally forked the code at work because we have a handful of changes and can't wait around for the Pull Request / Release cycle on the library. What I've done is the following:
Add Type(s) for Authenticator.handle
export type AuthenticatedResponse = { result: CloudFrontRequest, tokens: Tokens, isAuthenticated: true, };
export type CloudFrontRedirectionResponse = { result: CloudFrontRequestResult, isAuthenticated: false, };
export type CognitoRedirectionResponse = { result: CloudFrontRequestResult, isAuthenticated: false, };
export type HandleResponse =
  AuthenticatedResponse | CloudFrontRedirectionResponse | CognitoRedirectionResponse;

Update the Authenticator._getTokensFromCookie, Add Access Token
_getTokensFromCookie(cookieHeaders: Array<{ key?: string | undefined, value: string }> | undefined): Tokens {
  if (!cookieHeaders) {
    this._logger.debug("Cookies weren't present in the request");
    throw new Error("Cookies weren't present in the request");
  }

  this._logger.debug({ msg: 'Extracting authentication token from request cookie', cookieHeaders });

  const cookies = cookieHeaders.flatMap(h => Cookies.parse(h.value));

  const tokenCookieNamePrefix = `${this._cookieBase}.`;
  const accessTokenCookieNamePostfix = '.accessToken';
  const idTokenCookieNamePostfix = '.idToken';
  const refreshTokenCookieNamePostfix = '.refreshToken';

  const tokens: Tokens = {};
  for (const {name, value} of cookies){
    if (name.startsWith(tokenCookieNamePrefix) && name.endsWith(accessTokenCookieNamePostfix)) {
      tokens.accessToken = value;
    }
    if (name.startsWith(tokenCookieNamePrefix) && name.endsWith(idTokenCookieNamePostfix)) {
      tokens.idToken = value;
    }
    if (name.startsWith(tokenCookieNamePrefix) && name.endsWith(refreshTokenCookieNamePostfix)) {
      tokens.refreshToken = value;
    }
  }

  if (!tokens.accessToken && !tokens.idToken && !tokens.refreshToken) {
    this._logger.debug('Neither accessToken, nor idToken, nor refreshToken was present in request cookies');

    throw new Error('Neither accessToken, nor idToken, nor refreshToken was present in request cookies');
  }

  this._logger.debug({ msg: 'Found tokens in cookie', tokens });
  return tokens;
  }

Update the Authenticator.handle, Add Access Token Verification, Update Return Type(s)
async handle(event: CloudFrontRequestEvent): Promise<HandleResponse> {
  this._logger.debug({ msg: 'Handling Lambda@Edge event', event });

  const { request } = event.Records[0].cf;
  const requestParams = parse(request.querystring);
  const cfDomain = request.headers.host[0].value;
  const redirectURI = `https://${cfDomain}`;

  // 1. Fetch Token(s) from Coookie(s)
  // 2. Verify Access Token, ID Token from Cookie(s)
  // 3. Optionally, On Failure of (2), Attempt Token Refresh
  // 4. Optionally, On Failure of (3), Check for `?code=STRING` on Request Parameters
  //  - Handle as Cognito Hosted UI Authentication Redirect Response
  //  - Fetch Token(s) from Cognito Hosted UI Authentication Redirect Response
  //  - Redirect to CloudFront (Self) w/ Token(s) in Cookie Header(s), Triggering Step #1, #2
  // 5. Finally, On Failure of (4), Redirect to Cognito Hosted UI for Authentication

  try {
    // 1. Find Token(s) from Coookie(s)
    const headerTokens = this._getTokensFromCookie(request.headers.cookie);

    this._logger.debug({ msg: 'Verifying token...', tokens: headerTokens });

    try {
      // 2. Verify Access Token, ID Token from Cookie(s)
      const accessToken = await this._accessTokenVerifier.verify(headerTokens.accessToken);
      const idToken = await this._idTokenVerifier.verify(headerTokens.idToken);

      this._logger.info({ msg: 'Forwarding request', path: request.uri, accessToken, idToken, });

      return { result: request, tokens: headerTokens, isAuthenticated: true, };
    } catch (err) {
      // 3. Optionally, On Failure of (2), Attempt Token Refresh
      if (headerTokens.refreshToken) {
        this._logger.debug({ msg: 'Verifying accessToken and idToken failed, verifying refresh token instead...', tokens: headerTokens, err });

        const refreshedTokens = await this._fetchTokensFromRefreshToken(redirectURI, headerTokens.refreshToken);
        const response = await this._getRedirectToCloudFrontResponse(refreshedTokens, cfDomain, request.uri);

        return { result: response, isAuthenticated: false, };
      } else {
        throw err;
      }
    }
  } catch (err) {
    this._logger.debug("User isn't authenticated: %s", err);

    // TODO: Add `path` Configuration, i.e. `/idpresponse` a la AWS ALB?
    if (requestParams.code) {
      // 4. Optionally, On Failure of (3), Check for `?code=STRING` on Request Parameters
      const codeTokens = await this._fetchTokensFromCode(redirectURI, requestParams.code);
      const response = await this._getRedirectToCloudFrontResponse(codeTokens, cfDomain, requestParams.state as string);

      return { result: response, isAuthenticated: false, };
    } else {
      // 5. Finally, On Failure of (4), Redirect to Cognito Hosted UI for Authentication
      const response = this._getRedirectToCognitoUserPoolResponse(request, redirectURI);

      return { result: response, isAuthenticated: false, };
    }
  }
}


Fix #782, Create CHANGELOG.md

Checklist

[x] I reviewed the Contributing Guide.
[x] I signed and emailed the appropriate Contributor License Agreement to<EMAIL_ADDRESS>and copied<EMAIL_ADDRESS>
Describe the contribution
Fixes #782
Note: related to https://github.com/nasa/cFE/issues/1581
Note: if https://github.com/nasa/cFE/issues/2149 is implemented, it can be done directly on a single CHANGELOG.md file now, rather than inserting part way down into a README.md file.
Testing performed
None.
Expected behavior changes
Minimizes unnecessary clutter in README.md
Contributor Info
@thnkslprpt

@thnkslprpt CCB 6 October 2022: Approved pending merge conflict resolution.


Expose test suite

Exposes our test suite to allow for alternative implementations; closes #14

Lol oops, good catch
On Sat, Jan 21, 2017, 20:21 Seth Vincent<EMAIL_ADDRESS>wrote:

@sethvincent commented on this pull request.
In README.md
https://github.com/yoshuawuyts/nanomorph/pull/36#pullrequestreview-17812805
:

@@ -31,6 +31,17 @@ morph(html
hello people
, tree)
morph(html
nanananana-na-no
, tree)

+## Building your own
+Morphdom was designed to optimizes for simplicity, but different situations

here and in the require statement below it should say "nanomorph"?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/yoshuawuyts/nanomorph/pull/36#pullrequestreview-17812805>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACWletSR6pEj2S-oGdJmXtP9xBwGLWrOks5rUlqzgaJpZM4LpQmt>
.


Matrix notifications are not encrypted

⚠ Please verify that this bug has NOT been raised before.

[X] I checked and didn't find similar issue

🛡 Security Policy

[X] I agree to have read this project Security Policy

Description
All the notifications on matrix are unencrypted. Other thing I noticed while trying to setup those notifications is that I have to use 'https://matrix.mydomain.tld' and not the real homeserver URL 'https://mydomain.tld'.
👟 Reproduction steps
Setup the notifications for Matrix;
Run a test / receive a message from the bot;
Message is "Unencrypted"

👀 Expected behavior
Messages to be encrypted
😓 Actual Behavior
Messages are unencrypted
🐻 Uptime-Kuma Version
1.18.3
💻 Operating System and Arch
Debian GNU/Linux 11 (bullseye) x86_64
🌐 Browser
Not releveant
🐋 Docker Version
Docker 20.10.5+dfsg1
🟩 NodeJS Version
No response
📝 Relevant log output
No response

Sorry I don't understand. If you are using a valid https, how could that be unencrypted?
And it is an API that is provided by Matrix server, why it is a bug?
https://github.com/louislam/uptime-kuma/blob/4f6dec41c617267860ec9c686477e03c633e7c4b/server/notification-providers/matrix.js#L32-L37

When I go to the chatroom I see a red shield and when I hover over it it says that the message is unencrypted.

as shown in this picture. This only happens with the messages from Uptime Kuma. I tried sending a message while logged from the account of the bot. The red shield doesn't appear this way.

The thing can be seen here:

The upper message is from the bot. The message under it is from me. The first message has the red shield saying that it is unencrypted. The second message doesn't have the shield. This means that it is encrypted

For a personal project, I do it this way
import * as sdk from 'matrix-js-sdk'
import { logger } from 'matrix-js-sdk/lib/logger'
import { ClientEvent } from 'matrix-js-sdk'
import { LocalStorage } from 'node-localstorage'
import { LocalStorageCryptoStore } from 'matrix-js-sdk/lib/crypto/store/localStorage-crypto-store'

// eslint-disable-next-line @typescript-eslint/no-var-requires
const Olm = require('olm/olm_legacy')
declare global {
	// eslint-disable-next-line no-var
	var Olm: unknown
}
global.Olm = Olm
const localStorage = new LocalStorage('./store/matrix')

/**
 * A wrapper for matrix-js-sdk,
 * which allows to connect to a Matrix account, enables encryption
 *     connect()
 * gives a message sending function
 *     sendMessage()
 * as well as a disconnection function (that then stop the client).
 *     disconnect()
 */
export class MatrixNotifications {
	matrixClient: sdk.MatrixClient
	connected: boolean

	/**
	 * Check that the instane enable MATRIX via environement variables,
	 * then create the client
	 */
	constructor() {
		this.connected = false
		// temp fix : https://github.com/matrix-org/matrix-js-sdk/issues/2415#issuecomment-1141246410
		// eslint-disable-next-line @typescript-eslint/no-var-requires
		const request = require('request')
		sdk.request(request)
		///

		this.matrixClient = sdk.createClient({
			deviceId: 'Streaks Server',
			baseUrl: process.env.MATRIX_URL,
			accessToken: process.env.MATRIX_TOKEN,
			userId: process.env.MATRIX_USER,

			cryptoStore: new LocalStorageCryptoStore(localStorage)
		})
	}

	/**
	 * Connect the client and start encryption
	 */
	async connect() {
		if (this.connected)
			return
		logger.setLevel(logger.levels.ERROR)
		await this.matrixClient.initCrypto()
		await this.matrixClient.startClient()
		await new Promise<void>((resolve) => {
			this.matrixClient.once(ClientEvent.Sync, () => {
				// Send encrypted message, even if member isn't trusted
				this.matrixClient.setGlobalErrorOnUnknownDevices(false)
				this.connected = true
				resolve()
			})
		})
	}

	/**
	 * Stop the client if it is started
	 */
	disconnect() {
		if (!this.connected)
			return
		this.matrixClient.stopClient()
	}

	/**
	 * Send a message in the given room
	 * First join the room if not already done
	 *
	 * @param {string} roomID - The id of the room to send the message to.
	 * @param {string} message - The message to send
	 * @param {string} [htmlMessage] - The HTML version of the message
	 */
	async sendMessage(roomID: string, message: string, htmlMessage = '') {
		await this.matrixClient.joinRoom(roomID)
		await this.matrixClient.uploadKeys()
		if (htmlMessage != '')
			await this.matrixClient.sendHtmlMessage(roomID, message, htmlMessage)
		else
			await this.matrixClient.sendTextMessage(roomID, message)
	}
}

with the following dependencies
"matrix-js-sdk": "^19.0.0",
"node-localstorage": "^2.2.1",
"olm": "https://packages.matrix.org/npm/olm/olm-3.1.4.tgz",


Missing Executor?

It's probably something that I'm doing wrong, but no matter if I run terracotta in Docker container or locally (on OS X), I always keep getting this Python error:
terra-docker-ios-terra-1  | <IP_ADDRESS> - - [28/Oct/2022 11:42:37] "GET /singleband/nox/8/140/87.png?colormap=hot&stretch_range=[0.06780135631561279,12.038280487060547] HTTP/1.1" 500 -
terra-docker-ios-terra-1  | Traceback (most recent call last):
terra-docker-ios-terra-1  |   File "/usr/local/lib/python3.9/site-packages/flask/app.py", line 2548, in __call__
terra-docker-ios-terra-1  |     return self.wsgi_app(environ, start_response)
terra-docker-ios-terra-1  |   File "/usr/local/lib/python3.9/site-packages/flask/app.py", line 2528, in wsgi_app
terra-docker-ios-terra-1  |     response = self.handle_exception(e)
terra-docker-ios-terra-1  |   File "/usr/local/lib/python3.9/site-packages/flask/app.py", line 2525, in wsgi_app
terra-docker-ios-terra-1  |     response = self.full_dispatch_request()
terra-docker-ios-terra-1  |   File "/usr/local/lib/python3.9/site-packages/flask/app.py", line 1822, in full_dispatch_request
terra-docker-ios-terra-1  |     rv = self.handle_user_exception(e)
terra-docker-ios-terra-1  |   File "/usr/local/lib/python3.9/site-packages/flask/app.py", line 1820, in full_dispatch_request
terra-docker-ios-terra-1  |     rv = self.dispatch_request()
terra-docker-ios-terra-1  |   File "/usr/local/lib/python3.9/site-packages/flask/app.py", line 1796, in dispatch_request
terra-docker-ios-terra-1  |     return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args)
terra-docker-ios-terra-1  |   File "/usr/local/lib/python3.9/site-packages/terracotta/server/singleband.py", line 120, in get_singleband
terra-docker-ios-terra-1  |     return _get_singleband_image(keys, tile_xyz)
terra-docker-ios-terra-1  |   File "/usr/local/lib/python3.9/site-packages/terracotta/server/singleband.py", line 164, in _get_singleband_image
terra-docker-ios-terra-1  |     image = singleband(parsed_keys, tile_xyz=tile_xyz, **options)
terra-docker-ios-terra-1  |   File "/usr/local/lib/python3.9/contextlib.py", line 79, in inner
terra-docker-ios-terra-1  |     return func(*args, **kwds)
terra-docker-ios-terra-1  |   File "/usr/local/lib/python3.9/site-packages/terracotta/handlers/singleband.py", line 43, in singleband
terra-docker-ios-terra-1  |     tile_data = xyz.get_tile_data(
terra-docker-ios-terra-1  |   File "/usr/local/lib/python3.9/site-packages/terracotta/xyz.py", line 44, in get_tile_data
terra-docker-ios-terra-1  |     return driver.get_raster_tile(
terra-docker-ios-terra-1  |   File "/usr/local/lib/python3.9/site-packages/terracotta/drivers/terracotta_driver.py", line 263, in get_raster_tile
terra-docker-ios-terra-1  |     return self.raster_store.get_raster_tile(
terra-docker-ios-terra-1  |   File "/usr/local/lib/python3.9/site-packages/terracotta/drivers/geotiff_raster_store.py", line 150, in get_raster_tile
terra-docker-ios-terra-1  |     future = submit_to_executor(retrieve_tile)
terra-docker-ios-terra-1  |   File "/usr/local/lib/python3.9/site-packages/terracotta/drivers/geotiff_raster_store.py", line 53, in submit_to_executor
terra-docker-ios-terra-1  |     if context.executor is None:
terra-docker-ios-terra-1  | AttributeError: '_thread._local' object has no attribute 'executor'

I tried Python 3.9, 3.6, 3.10 with the same result, I tried different cog files, I tried using pip install terracotta as well as pip install git+https://github.com/DHI-GRAS/terracotta.git. Doesn't make a difference.
Any thoughts?

Fixed on master, feel free to reopen if this persists.


settings: Fix error handling for uploading an invalid file for "Uploa…

…d icon".
Fixes #8842.

Screenshots:
When there is no organization icon.

When there is an organization icon already exists.

@timabbott  I have noticed that this same thing also happens to the "User avatar" in the user setting. So I have also updated this changes to that also.

Looks great, merged, thanks @Balaji2198!
Can you do a quick check for similar issues with uploading custom emoji?

Sure. Will look at this now.


[Python] Add an option to retain timestamp returned from the BigTable row

Add an option to return timestamp associated with the fetched value from the BigTable read_row instead of just the value. This could be useful for users when they want to get a series of historical data stored for that key.
By default, though, only the latest value without timestamp is fetched.
Part of #29787

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

Checks failed because of https://github.com/apache/beam/issues/30095

R: @damccorm

Thanks for the quick review! Once the postcommit finishes, I'll remove the trigger file and fix the lint (one import order)

SGTM

SGTM, thanks

BigTable tests are passing. Failure are because of BigQueryIO tests(#30095)  -


Calculate checksum incrementally

Use the asmCrypto.js library to calculate a file's checksum incrementally, by loading it into memory in chunks rather than reading the entire file at once.
This is slower than using SubtleCrypto, which uses low-level functions built into the browser, but SubtleCrypto needs the full contents of a file which limits the size of the files that we can process.
Also update the GraphQL schema to support larger file sizes.

This depends on this API schema change: https://github.com/nationalarchives/tdr-prototype-sangria/pull/28


All splat demos fail on FireFox desktop

I mentioned this in the forums, raising it again here for visibility:
https://forum.playcanvas.com/t/gaussian-splatting-playcanvas/33503/39
Repro:
Start any demo in FireFox desktop browser.
e.g. https://launch.playcanvas.com/1917916?debug=true
Drag the screen to rotate the splat object.
Result:
The error will appear and sorting will stop.

Expected Result:
No errors. Splats should be sorted by depth.
Environment:
Firefox Browser 120.0.1 (64-bit)
Windows 10 Pro 22H2 (patched today)
GTX 3080 Video Card
11th Gen Intel(R) Core(TM) i7-11700KF @ 3.60GHz   3.60 GHz
Please let me know if a stack trace or other information is needed.

Thanks @pjbaron. Just for reference I can't repro this on a Mac w/ FF 120. Did this not get solved as per this suggestion?

This is me on Win10:

@marklundin unfortunately not. That suggestion fixed the depth sorting on Chrome for me (The FF issue continues to be a blocker for any splat display in that browser, so I've jumped back to Chrome until it is fixed)

Hmm, that's strange. I can't seem to replicate. I have same CPU w/ v120.0.1 FF on Windows.

@marklundin I had to keep rotating the shoe for about 30 seconds before the errors showed. Did you rotate for long enough?

Yep, was there for a few minutes. Is it fairly consistent in how often it errors?

Hmm. I can't get it to error any more.

I could reproduce it before, but cannot at the moment, tested on FF 126 on MacOS. Possibly due to many improvements in our splat rendering in the last month. Closing for now, but please reopen if you can still reproduce this.

I have experienced that issue on mobile (Android).

I believe #6357 might have addressed the underlying issue (which was updating the sort buffer in a setTimeout callback).
If you experience this issue again using up-to-date engine please post the details here.


ssl-opt.sh: wait for proxy to start before running the script further

Resolves issue IOTSSL-2885.

We probably ought to backport this after getting another review.

We probably ought to backport this after getting another review.

Yep, that's the plan.

Please do backport it to 2.16, so that it lands in baremetal next time we merge from it!

Backports created.

Backports are approved and should be ready as soon as CI finishes running on them.


Community update

Minimum viable product
We were lucky to get contributors early on on the project. TryTLS has been in flux, but now things start to stabilise and an idea of the roadmap exists. Hence, it is now time to update the contributors on the progress for better synchronisation.
Overview

The minimum viable product will contain the following:
Python-based trytls, which will have support for testing a pure TLS handshake or HTTP.
Stubs for the following languages:

Lua
Python
Go
Haskell
Java

Support for two backends

BadSSL
SSL Labs

Documentation:

For end users: Step-by-step guide on how to run a stub with or without a runner, with some information on backends
For developers: Information on how to create a stub using correct calling convention (more on it below)

Stub progress
We have agreed on an initial common calling convention.
License
We have added a default license. Please drop us a note in the comment field, wether default license is ok for you.
Contributors list
Every contributor will get a mention in the main README.md. It is also possible to negotiate a different arrangement if it suits your preference.
Checklist

[ ] Check if default license is ok for contributors
[ ] Check how contributors want to be named on the contributor list

Default license is ok for me.

Ok for me as well.

Ping: @aleksiklasila @jviide @ikisusi @oherrala @ppietikainen @joneskoo

I'm ok with default license (MIT).

MIT license ok for me.

Ok with MIT. If needed CC0 or similar with other material (pictures, videos) produced by me is ok as well if we need to go beyond MIT.

Ok with MIT

My contributions are OK to distribute under MIT license.


Added meta.form to FieldArray props

Fixes #2661.

Codecov Report

Merging #2712 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff           @@
##           master   #2712   +/-   ##
======================================
  Coverage     100%    100%
======================================
  Files          67      67
  Lines        1383    1408   +25
======================================
+ Hits         1383    1408   +25

Impacted Files
Coverage Δ

src/ConnectedFieldArray.js
100% <ø> (ø)
:arrow_up:

src/createFieldArrayProps.js
100% <100%> (ø)
:arrow_up:

src/FieldArray.js
100% <0%> (ø)
:arrow_up:

src/Field.js
100% <0%> (ø)
:arrow_up:

src/reducer.js
100% <0%> (ø)
:arrow_up:

src/Fields.js
100% <0%> (ø)
:arrow_up:

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 a5fc53b...399c92f. Read the comment docs.

Published in v6.6.0.


Sticky Message

Description
Closed #102
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update
[ ] Refactor or other

New Commands

?stickao-set set new message in current channel
?stickao-remove remove sticky message in current channel

NOTE
to run both commands user must has ManageMessage permission in the channel to be able to run commands.
Screenshot
Stickao Create

Stickao Remove

Access denied

Checklist:

[x] I have run pnpm format and my code don't have any linting issues

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation

Progress

[x] Message stick to bottom (Timeout)
[x] Message stick to bottom (Message quota)
[x] Create command
[x] Remove command
[x] Unit test for sub module
[x] Unit test for event handler
[x] Unit test for command handler

Is there a reason why you wait for up to 5 messages before you move the sticky message to bottom? Why not always move it on every message created? @samithiwat

Is there a reason why you wait for up to 5 messages before you move the sticky message to bottom? Why not always move it on every message created? @samithiwat

In Stickybot Docs it said that this constraint comply with the Discord Term of Service

Just got an idea. Can we use context menu instead? Mods type in the message they want to be sticky and then right click -> make sticky. Then bot will send a new message with that content. This will also allow mods to customize their message to their likings.

@buskun i like the idea but unfortunately, when i tested, context menus are a bit buggy in large Discord servers… when i right click, the App menu does display. i have to quit Discord and open it again and the Apps menu reappear. this makes context menu commands almost unusable ;-;

using modal may make it hard to add role/channel mentions to the message.
my suggestion would be to use a simple message prefix e.g. ?sticky to set up sticky messages

but that can be implemented later, i think for now, we can just use a slash command as-is so we can get this first version in.

I think it can be implement in this PR, it is easier than implement the modal submit handler 😂 .

Update Access Control

access denied if user not has permission ManageMessage

Last Update (Maybe)

remove command when user was rejected
remove the old message when set the sticky message if existed

I'm ready to merge krubb

let’s ship it!
thank you very much!


JAVA command failed

It raise an OSError when I called Stanford NLP by NLTK stanford interface.
'''
OSError: Java command failed : ['C:\Program Files (x86)\Java\jdk1.8.0_60\bin\java.exe', u'-mx1000m', '-cp', u'.\stanford-parser.jar;.\stanford-parser-3.5.2-models.jar', u'edu.stanford.nlp.parser.lexparser.LexicalizedParser', u'-model', 'englishPCFG.ser.gz', u'-sentences', u'newline', u'-outputFormat', u'penn', u'-encoding', u'utf8', 'c:\users\hz\appdata\local\temp\tmpkxvhkz']
'''

I tried to edit the java_options as follows:
java_options='-Xmx1024m'
It still raise an OSError:
::
Loading parser from serialized file englishPCFG.ser.gz ...  done [0.6 sec].
Parsing file: c:\users\hz\appdata\local\temp\tmpmjgtxb
Parsing [sent. 1 len. 201]: The invention provides an OLED device with improved light out-coupling , which can be manufactured easy and reliable at low costs , which comprises an electroluminescent layer stack -LRB- 2 , 3 , 4 -RRB- on top of a substrate -LRB- 1 -RRB- , where the electroluminescent layer stack -LRB- 2 , 3 , 4 -RRB- comprises an organic light-emitting layer stack -LRB- 3 -RRB- with one or more organic layers sandwiched between a first electrode -LRB- 2 -RRB- facing towards the substrate -LRB- 1 -RRB- and a 10 second electrode -LRB- 4 -RRB- , where the second electrode -LRB- 4 -RRB- comprises a layer stack of at least a transparent conductive protection layer -LRB- 41 -RRB- on top of the organic light-emitting layer stack -LRB- 3 -RRB- , a transparent organic conductive buckling layer -LRB- 42 -RRB- on top of the protection layer -LRB- 41 -RRB- having a glass transition temperature lower than the lowest glass transition temperature of the organic layers within the organic light-emitting layer stack -LRB- 3 -RRB- and a stress inducing layer 15 -LRB- 43 -RRB- on top of the buckling layer -LRB- 42 -RRB- to introduce stress to the buckling layer -LRB- 42 -RRB- .

***  WARNING!! OUT OF MEMORY! THERE WAS NOT ENOUGH  ***
***  MEMORY TO RUN ALL PARSERS.        ***

Sentence has no parse using PCFG grammar (or no PCFG fallback).  Skipping...
Exception in thread "main" edu.stanford.nlp.parser.common.NoSuchParseException
at edu.stanford.nlp.parser.lexparser.LexicalizedParserQuery.getBestParse(LexicalizedParserQuery.java:398)
at edu.stanford.nlp.parser.lexparser.LexicalizedParserQuery.getBestParse(LexicalizedParserQuery.java:370)
at edu.stanford.nlp.parser.lexparser.ParseFiles.processResults(ParseFiles.java:271)
at edu.stanford.nlp.parser.lexparser.ParseFiles.parseFiles(ParseFiles.java:215)
at edu.stanford.nlp.parser.lexparser.ParseFiles.parseFiles(ParseFiles.java:74)
at edu.stanford.nlp.parser.lexparser.LexicalizedParser.main(LexicalizedParser.java:1521)
Traceback (most recent call last):
File "L:/python/SAO/SAO.py", line 314, in
sao_system.run('testdata.xls')
File "L:/python/SAO/SAO.py", line 223, in run
paser_tree = sao_parser.getParserTree( sentence )
File "L:/python/SAO/SAO.py", line 87, in getParserTree
sentences_trees = self.sentsParser( sentence )
File "L:/python/SAO/SAO.py", line 84, in sentsParser
return stanford_parser.raw_parse_sents( self.sentsTokenize( sentences ) )
File "C:\Python27\lib\site-packages\nltk-3.0.4-py2.7.egg\nltk\parse\stanford.py", line 170, in raw_parse_sents
return self._parse_trees_output(self._execute(cmd, '\n'.join(sentences), verbose))
File "C:\Python27\lib\site-packages\nltk-3.0.4-py2.7.egg\nltk\parse\stanford.py", line 230, in _execute
stdout=PIPE, stderr=PIPE)
File "C:\Python27\lib\site-packages\nltk-3.0.4-py2.7.egg\nltk\internals.py", line 162, in java
raise OSError('Java command failed : ' + str(cmd))
OSError: Java command failed : ['C:\Program Files (x86)\Java\jdk1.8.0_60\bin\java.exe', u'-Xmx1024m', '-cp', u'.\stanford-parser.jar;.\stanford-parser-3.5.2-models.jar', u'edu.stanford.nlp.parser.lexparser.LexicalizedParser', u'-model', 'englishPCFG.ser.gz', u'-sentences', u'newline', u'-outputFormat', u'penn', u'-encoding', u'utf8', 'c:\users\hz\appdata\local\temp\tmpmjgtxb']
Process finished with exit code 1

The warning message is a big clue. Looks like the sentence being parsed is too long. Personally, I think anyone who writes an English sentence that is 201 words long should be shot, but that's just me.
Do you absolutely have to parse such long sentences? If not, you can filter out long sentences as a preprocessing step, or follow the recommendations in the warning to set the maximum sentence length for Stanford NLP.

Thanks for your comment. Thanks to uncertainty of length of sentence to be parsed. I just want to change the size of JVM memory by the command: java -Xmx1024m -Xms1024m -Xmn256m -Xss16m. But it dose not seem to work.

Have you tried running Stanford NLP directly without using nltk? That is, run C:\Program Files (x86)\Java\jdk1.8.0_60\bin\java.exe -Xmx1024m -cp .\stanford-parser.jar .\stanford-parser-3.5.2-models.jar'. Does it give the same errors? If yes, the parsed sentence is too long and your only options are the recommendations in the warning message.

I don't think you'll be able to get the stanford parser to deal with sentences that long no matter how much memory you give it.  Depending on your application, though, you might by dividing it into, say, 50 word fragments and parsing them individually.  At any rate, I'm pretty sure this isn't an issue with NLTK.

Thanks for you all.

@rmalouf: Actually, if you give the parser enough memory and time, the Stanford PCFG parser will parse sentences that long or longer. I once proved this to someone by parsing a 675 word sentence from a regulatory manual. But it took about 70 gigs of RAM and a few hours ... so not recommended. If you want to parse such sentences, you should use a greedy transition-based parser. I'm not sure whether they're supported in NLTK, but either the shift-reduce constituency parser or the neural network dependency parser provided with the Stanford Parser would be a much better choice.


Links in documentation need to be updated

Some links do not point to the right place in the docs - this is not high priority but if you have a repo for the docs, I can fix it myself and submit a PR.
Expected behavior
Links work (in this case should point to https://github.com/twitter/finagle/blob/develop/finagle-base-http/src/main/scala/com/twitter/finagle/http/Request.scala not https://github.com/twitter/finagle/blob/develop/finagle-http/src/main/scala/com/twitter/finagle/http/Request.scala
Actual behavior
404 Error
Steps to reproduce the behavior
Visit https://twitter.github.io/finatra/user-guide/http/controllers.html
Click link for "c.t.finagle.http.Request" and receive 404 Error

thanks for the 👀 @jamesfe. would love a PR!
the user guide code for controllers is here. it looks like that link is also broken on filters.

@kevinoliver Thanks for pointing me in the right direction!  I will submit a PR shortly.

Submitted: https://github.com/twitter/finatra/pull/424

Closing as this appears to be fixed. @jamesfe thanks again!


FAI-426: Score Cards: DataField validation

See https://issues.redhat.com/browse/FAI-426

@sjamboro This is ready for re-review. Thank-you.


logging: Refactoring macro to avoid Coverity issue

Change a runtime log check such that Coverity does not report a
needless issue on every use of any log macro.
Before the change, this was used in log macros:
else if(is_user_context || (_level <= LOG_RUNTIME_FILTER(_filter)))

If runtime filtering is not enabled, this expands to:
else if(is_user_context || 1)

Because the level is compared to log level debug (4) and will always be,
equal or lower.
Coverity always reports this as a potential issue, since the
variable part (is_user_context) makes no difference.
After the change, a macro is used which expands into the original code
when runtime filtering is used, else it simply expands to:
else if(true)

Which has equal semantics as the previous code but isn't flagged by
Coverity.

Coverity related, ping @ioannisg


[2.0] Remove deprecated increment type

@alcaeus I think I have removed all BC stuff but I'd appreciate you having a closer look :)

Looks complete, apart from the @increment annotation class itself.

Annotation is being removed in #1471 :)

Yeah, Obviously. My bad 😃

Docs are now removed too


Not quoting a scalar starting with the "%"

Symfony 3.1 deprecation warning: "Not quoting a scalar starting with the "%" indicator character is deprecated since Symfony 3.1 and will throw a ParseException in 4.0."

Hi,
a new version is out, which contains your fix.


Add auto retry for top flaky targets in packages repo

With the presubmit auto retry supported: https://github.com/flutter/cocoon/pull/3059, we can enable the logic for top flaky targets in the packages repo.
This will help auto land bump PRs like: https://github.com/flutter/packages/pull/4988, where I have to rerun twice of the flaky targets Linux_android android_platform_tests_shard_2 master and re-add the autosubmit label to get it landed.

Will start with:
https://ci.chromium.org/ui/p/flutter/builders/luci.flutter.prod/Linux_android android_platform_tests_shard_2 stable
https://ci.chromium.org/ui/p/flutter/builders/luci.flutter.prod/Linux_android android_platform_tests_shard_2 master

@stuartmorgan Are there any other targets you would prefer an auto rerun?

See https://github.com/flutter/packages/pull/4995#pullrequestreview-1642769946
I don't think we should do this for Android platform tests. We could potentially do it for other tests in the future, but right now I don't have any specific candidates.

Flake tracking bug to fix the flakes is https://github.com/flutter/flutter/issues/130986. Closing here. We can open a new one tracking auto rerun functionality if needed in the future.


open source trained code?

Thank you for the open source inference code. I am very interested in your article, and I am planning to reproduce the training code and then train it on my own training set. I wonder if you have the intention to open source your training code recently? Looking forward to your reply.

I tried to reproduce your training code, but as it is an image, each click corresponds to each training, the training process is very slow, I would like to know how long you have trained on the SBD data set, thank you.


Distrobox can not create container from localhost

Describe the bug
Distrobox fails when creating container from localhost. Works correctly when using remote container eg, distrobox create ubuntu. Tested in VM and on bare metal.
❯ distrobox version
distrobox: <IP_ADDRESS>

❯ podman images
REPOSITORY                TAG         IMAGE ID      CREATED         SIZE
localhost/root-u18.04     5.34.38     2c683ad074aa  52 minutes ago  3.86 GB

❯ podman version
Client:       Podman Engine
Version:      4.9.4
API Version:  4.9.4
Go Version:   go1.21.8
Built:        Tue Mar 26 09:39:52 2024
OS/Arch:      linux/amd64

❯ distrobox create -i localhost/root-u18.04:5.34.38
Trying to pull localhost/root-u18.04:5.34.38...
WARN[0000] Failed, retrying in 1s ... (1/3). Error: initializing source docker://localhost/root-u18.04:5.34.38: pinging container registry localhost: Get "https://localhost/v2/": dial tcp [::1]:443: connect: connection refused
WARN[0001] Failed, retrying in 1s ... (2/3). Error: initializing source docker://localhost/root-u18.04:5.34.38: pinging container registry localhost: Get "https://localhost/v2/": dial tcp [::1]:443: connect: connection refused
WARN[0002] Failed, retrying in 1s ... (3/3). Error: initializing source docker://localhost/root-u18.04:5.34.38: pinging container registry localhost: Get "https://localhost/v2/": dial tcp [::1]:443: connect: connection refused
Error: initializing source docker://localhost/root-u18.04:5.34.38: pinging container registry localhost: Get "https://localhost/v2/": dial tcp [::1]:443: connect: connection refused

What did you expect to happen?
If I do the same on Silverblue 39 with the same container and distrobox version it works okay.
● fedora:fedora/39/x86_64/silverblue
                  Version: 39.20240507.0 (2024-05-07T00:41:06Z)
               BaseCommit: c6c2469f73b71ee92645223d9aa2390cad23642600b5c48fce2a3f97fec89b6b
             GPGSignature: Valid signature by E8F23996F23218640CB44CBE75CF5AC418B8E74C
      RemovedBasePackages: firefox firefox-langpacks 125.0.3-1.fc39 mesa-va-drivers 23.3.6-1.fc39
          LayeredPackages: 'gstreamer1-plugins-bad-free-extras ' 'gstreamer1-plugins-bad-freeworld ' 'gstreamer1-plugins-ugly ' ansible btrbk btrfs-assistant
                           code dia distrobox emacs freerdp fzf git-lfs gnome-tweaks gstreamer1-vaapi headsetcontrol htop just langpacks-en_GB libvirt-client
                           mesa-va-drivers-freeworld mesa-vdpau-drivers-freeworld ncdu nvtop openssl piper podman-compose podman-docker printer-driver-brlaser
                           protonvpn python3-pip python3-virtualenv rpmfusion-free-release rpmfusion-nonfree-release smartmontools snapper solaar tailscale
                           tilix tilix-nautilus tmux ulauncher virt-manager xclip yaru-theme
            LocalPackages: protonvpn-stable-release-1.0.1-2.noarch

[apr@artoo distrobox]$ ./distrobox version
distrobox: <IP_ADDRESS>

[apr@artoo distrobox]$ ./distrobox create -i localhost/root-u18.04:5.34.38
Creating 'root-u18-04-5-34-38' using image localhost/root-u18.04:5.34.38	 [ OK ]
Distrobox 'root-u18-04-5-34-38' successfully created.
To enter, run:

distrobox enter root-u18-04-5-34-38

Output of rpm-ostree status
❯ rpm-ostree status
State: idle
AutomaticUpdates: stage; rpm-ostreed-automatic.timer: no runs since boot
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bluefin:gts
                   Digest: sha256:adf2b1ac615c1141e4f7aa6198ad394812b92aab28fe9e88564e57be04d8c7cf
                  Version: 39.20240508.0 (2024-05-08T16:50:35Z)

  ostree-image-signed:docker://ghcr.io/ublue-os/bluefin:gts
                   Digest: sha256:76678a83ddc1c84ec53e3c698b65ce1a11fd751f78873322a77cdf2405e554f4
                  Version: 39.20240507.0 (2024-05-07T16:16:35Z)

### Output of `groups`

```shell
❯ groups
apr wheel

### Extra information or context

_No response_

Distrobox is attempting to pull the image and you don't have a registry running on localhost.
Do you have pull set to always or is there a mismatch on the tag name?

Thanks for your help. AS you suggested I had forgotten about the distrobox config which is set to `container_always_pull="1" in the default bluefin config.
Issue fixed with:
❯ cp /usr/etc/distrobox/distrobox.conf ~/.distroboxrc

❯ cat ~/.distroboxrc
container_always_pull="0"
container_generate_entry=1
container_manager="podman"
container_name_default="ubuntu"
container_image_default="ghcr.io/ublue-os/ubuntu-toolbox:latest"
non_interactive="1"

❯ distrobox create -i localhost/root-u18.04:5.34.38
Creating 'root-u18-04-5-34-38' using image localhost/root-u18.04:5.34.38	 [ OK ]
Distrobox 'root-u18-04-5-34-38' successfully created.
To enter, run:

distrobox enter root-u18-04-5-34-38

Many Thanks :-)


Omitting empty subsequences wasn't clearing properly

Hey @LoganWright, you just merged a pull request, have a coin!
You now have 506 coins.


add global aliases to auto-generated code

Description
Add global aliases to auto-generated code.
In project that implicit using was disabled, ClassMemberAttribute may fail to build with CS0246 error because that auto-generate code without System namespace usings.

I understand the need for System.. Do I also need global::? Did you have any conflicts?

I understand the need for System.. Do you also need global::? Did you have any conflicts?

Most problems, including the one I've run into, can be fixed by just adding System..
However, given the best practices in auto-generating code, I think it's safer to add global:: (although I think it's rare for developers to define their own System class today).
As for me, I am not particular here. If the reference to System. is properly added, then my problems will be solved.

given the best practices in auto-generating code, I think it's safer to add global::

I thought so too, but GeneratedRegex, for example, doesn't have global:: for System. If either way looks ok, I don't like so long code, even for generated source codes.

It's just my preference. I don't mind merging them as they are now.

I thought so too, but GeneratedRegex, for example, doesn't have global:: for System. If either way looks ok, I don't like so long code, even for generated source codes.
It's just my preference. I don't mind merging them as they are now.

Thank you for your comment.
Indeed, considering the case of GeneratedRegex, there seems to be a tendency not to add global:: to the auto-generated code.
Shall we close this PR and create a new one that adds only System. (since this branch is also named "add-global-alias")?

Either a new PR or a revised commit on this PR is fine.

Either a new PR or a revised commit on this PR is fine.

Pushed revised commit on this PR.  https://github.com/ufcpp/ScribanSourceGenerator/pull/2/commits/117604cf6d151fe848431da9616e6309d88eb0fd

Thanks.

Released.
https://github.com/ufcpp/ScribanSourceGenerator/releases/tag/v1.1.0
https://www.nuget.org/packages/ScribanSourceGenerator/1.1.0


Cascading auto refresh for dialog fields

This is very similar to https://github.com/ManageIQ/manageiq-ui-classic/pull/264, except for the service UI.
https://www.pivotaltracker.com/story/show/139224685
/cc @gmcculloug I'm not sure who is best to review this on the service UI side of things, please advise 😄

@eclarizio could you please add the appropriate labels?

@miq-bot add_label dialogs, enhancement
I think those are the correct labels, but I'm not 100% clear on if we need to backport just yet...
@gmcculloug Do we want to backport this to Euwe and Darga or do we think most people running into the issue that the cascading was meant to fix were using OpsUI and this is strictly an enhancement for the Service UI?

This was being worked on for BZ https://bugzilla.redhat.com/show_bug.cgi?id=1411541 which is for Darga.  So this should be backported to both Ewue and Darga.

@miq-bot add_label euwe/yes, darga/yes

@eclarizio also, to answer your question that would be me 😄

@eclarizio looks like there was some refactoring in 'master' and I won't be able to backport this PR to Euwe/Darga as is. Can you create a separate PR?

Backported to Euwe via https://github.com/ManageIQ/manageiq-ui-service/issues/512

Backported to Darga via https://github.com/ManageIQ/manageiq-ui-service/pull/513


Uncomment device binding option, which allows Go application to bind graph processing to specified GPU device(s)

Since r1.13 is already out, uncomment device binding option, which allows Go application to bind graph processing to specified GPU device(s)
For discussion about this patch (and its C-counterpart), please see https://github.com/tensorflow/tensorflow/pull/20412

@yifeif can you please help merge this PR

Hi, any progress on this?

Still no luck? Should I generate pull request against master?

Ping?

@rthadur what happened here?

@rthadur what happened here?

@alextp, I don't have merge access here , @yifeif can you please help merge this PR.

Thanks @bioothod for the patch! I don't think we are making any patch releases for 1.13 unless we are doing security patches @mihaimaruseac? Also @gunan, what's our policy for accepting patches without doing releases?

It is somewhat unfair that you do not accept pull request because of the missed deadline for the patch which had been submitted a month ago and being subsequently notified on a weekly basis.
What tree should I rebase it against?

Hi @bioothod, unfortunately, after a branch is cut, we only accept critical bugfixes or security patches to the branch. So even if this patch was ready before 1.13 release was out.
I believe in the other pull request discussion meant we will reenable this on master?
@alextp may be able to comment.
I am happy to accept this on master, but for release branches our policy is only critical bugfixes.

Yes, reenabling this on master would be great as 1.14 is about to be cut.
*From: *Gunhan Gulsoy<EMAIL_ADDRESS>*Date: *Tue, May 14, 2019 at 5:19 PM
*To: *tensorflow/tensorflow
*Cc: *Alexandre Passos, Mention
Closed #27891 https://github.com/tensorflow/tensorflow/pull/27891.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/pull/27891?email_source=notifications&email_token=AAABHRN55H35NFF5LD6UVHLPVNJHLA5CNFSM4HGI5JGKYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOROKITLY#event-2341767599,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAABHRMLTDTI5ICPUJZW773PVNJHLANCNFSM4HGI5JGA
.

--

Alex

Pull request against master tree https://github.com/tensorflow/tensorflow/pull/28768


[Docs] Strict Mode Guide

Report
By following the Strict Mode Guide, it's not clear that it's actually required to call the changeMode.sh script every time the dependency is installed. In my case, I've noticed that our CI workflow continued using AppsFlyerFramework/Main instead of AppsFlyerFramework/Strict. Consider mentioning that in the docs or better provide an ability to set a flag in the Podfile, like it's done in RN Firebase.
Thanks!

One of the options to go with current implementation:

Create a script ./scripts/appsflyer-strict-mode.sh

#!/usr/bin/env bash

cd ./node_modules/react-native-appsflyer && ./changeMode.sh strict && cd ../../

Make it executable

chmod +x ./scripts/set-appsflyer-strict-mode.sh

Run it on postinstall (package.json)

  "scripts": {
    ...
    "postinstall": "./scripts/set-appsflyer-strict-mode.sh"
  },

@artyorsh thank you for opening this issue. we will take your suggestion and try to improve the developer's experience in the next versions. Thanks!


[BUG]: header overlap with popups

overlap issue between header and popups (DatePicker, Popover)
Screenshots:
Popovers & Date Picker:

This issue has been automatically closed because it received no activity for a while. If you think it was closed by accident, please leave a comment. Thank you.

This is still not resolved please check this PR : 2073


fix usm panic on gRPC server

What does this PR do?
Checks for non-nil tlsConfig before accessing.
Motivation
Panics from testProtocolConnectionProtocolMapCleanup. Introduced in #23433
Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


TypeScript Auto Import Not Working in *.vue Files (Wrong Path?)

Description
TypeScript auto import for ref in Component.vue not working:
<script lang='ts' setup>
const foo = ref(0)
</script>

The VSCode log claims that: (Note the Component.vue.ts part, the actual filename is Component.vue)
[2022-05-18 09:41:00.453] [renderer1] [error] 无法读取文件'c:\path\to\src\Component.vue.ts' (Error: 无法解析不存在的文件 'c:\path\to\src\Component.vue.ts'): Error: 无法读取文件'c:\path\to\src\Component.vue.ts' (Error: 无法解析不存在的文件 'c:\path\to\src\Component.vue.ts')
    at p.doReadFileStream (vscode-file://vscode-app/c:/Users/<user>/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:594:24262)
    at async f.doRead (vscode-file://vscode-app/c:/Users/<user>/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:2737:42343)
    at async f.readStream (vscode-file://vscode-app/c:/Users/<user>/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:2737:42018)
    at async ir.resolveFromFile (vscode-file://vscode-app/c:/Users/<user>/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:2726:66754)
    at async u.doResolve (vscode-file://vscode-app/c:/Users/<user>/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:2737:36878)
    at async c.acquire (vscode-file://vscode-app/c:/Users/<user>/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:17:32618)
    at async l.createModelReference (vscode-file://vscode-app/c:/Users/<user>/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:2726:79578)
    at async Promise.all (index 0)
    at async i._createEditsTasks (vscode-file://vscode-app/c:/Users/<user>/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:894:20015)
    at async i.apply (vscode-file://vscode-app/c:/Users/<user>/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:894:20191)
    at async g._performTextEdits (vscode-file://vscode-app/c:/Users/<user>/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:2737:28024)
    at async g.perform (vscode-file://vscode-app/c:/Users/<user>/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:2737:27407)
    at async v.apply (vscode-file://vscode-app/c:/Users/<user>/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:2737:29719)
    at async f (vscode-file://vscode-app/c:/Users/<user>/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:688:22077)
    at async Object.applyCodeAction (vscode-file://vscode-app/c:/Users/<user>/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:688:20828)

Environment

VSCode: 1.67.1
Volar v0.34.15

Extra Info

This feature has been working perfectly in the same project until I upgrade VSCode recently.
This bug seems to be related with newly created *.vue files.

Fixed by https://github.com/johnsoncodehk/volar/commit/768e64955556dbbb72ef7c77141e183e117bb582


trivy builds latest build with docker buildx build

the results speak for themselves: https://github.com/vmware-tanzu/carvel-secretgen-controller/runs/7780004960?check_suite_focus=true

@joaopapereira beat you too it joe, sorry 🥇
https://github.com/vmware-tanzu/carvel-secretgen-controller/pull/97


Hot to calculate the MaxValue?

I am doing a map heatmap based on heatmap.js,I have 2000 points,and the value is 1 to 40 ,1 is most.Hot to calculate a sensible MaxValue,beause,when I set 100,it looks terrible.

why don't you set it to 40? Please provide an example on codepen or any other code sharing plattform so we can have a closer look at it


HTTP response codes are lost

We are using the Oauth2 RestTemplate to make a rest call with a Oauth token.
On the server side, we generate an AuthenticationException that gets caught by the default web exception translator
This creates UnauthorizedException
On the client side, the response is extracted, but the error code is lost, and hard coded.
The Oauth2ErrorHandler
So what was a 401 response from the server, is received as a 400 error code in @ExceptionHandler because the UnauthorizedException returns a string "unauthorized" that is not correctly translated by the JSON deserializer
I could create a PR that would remove all "abitrary" strings in Oauth2Exception sub classes and deserializer, or we could serialize the error code instead of hard coding it.

what's the current workaround to get the actual http status code instead of the hardcoded 400?

What's your exact scenario? You have a token? Who is sending the 400?

I'll take a crack at a PR along the lines of my previous comment, but I'm also curious what @paperpunk's scenario is.

i am using OAuth2RestTemplate and successfully getting a token, the request for the token comes back with an HTTP 200
then, the actual request is sent, and it comes back with an HTTP 500
OAuth2ErrorHandler is invoked and at the time when it enters the handleError() method, ClientHttpResponse has the following in it:

after going through OAuth2ErrorHandler, message converters, etc, this gets thrown as an OAuth2Exception with a [hardcoded status code of 400] (https://github.com/spring-projects/spring-security-oauth/blob/6d9de66787cb60249f0de00ffe9075366a803924/spring-security-oauth2/src/main/java/org/springframework/security/oauth2/common/exceptions/OAuth2Exception.java#L61), and the fact that it was originally a 500 is lost
I need to implement retry logic based on whether it was 400/500, and since everything is wrapped into an OAuth2Exception with HTTP 400, I don't know how to retrieve the http original status code

I don't see how it would proceed through handleError with a 500 status code, this line here would ensure that only 4xx errors would possibly cause an Oauth2Exception to be thrown:  https://github.com/spring-projects/spring-security-oauth/blob/master/spring-security-oauth2/src/main/java/org/springframework/security/oauth2/client/http/OAuth2ErrorHandler.java#L82
What version are you using?

it looks like one of the project dependencies is bringing in spring-security-oauth2 1.0.5...
is the only way to fix this - to upgrade to the latest release, or can something be configured in 1.0.5 to bypass handleError() in case of a 500 status?

You can call setErrorHandler() and pass in your own sublcass of OAuth2ErrorHandler, and override the method handleError:
@Override
public void handleError(ClientHttpResponse response) throws IOException {
    if (response.getStatusCode().is5xxServerError()) {
        this.errorHandler.handleError(response);
    } else {
        super.handleError(response);
    }
}

The OAuth2ErrorHandler has a regular DefaultResponseErrorHandler inside it (this.errorHandler), and can delegate to it in case the error is not OAuth2 related. At least that's the intent, as versions have progressed the decision around what is and isn't an OAuth2 error has become narrower (eg: don't include 5xx errors). I'm actually proposing that only 400, 401 and 403 could possibly result in an OAuth2Exception


Can it be run in batch mode ?

That is, can SPIRED run all the mutation tasks written into one FASTA file?

Dear @CykaZH
We are sorry about that SPIRED-Fitness’s code only supports inference with batch =1, currently.
Thank you!


panic handler middleware

https://eli.thegreenplace.net/2021/rest-servers-in-go-part-5-middleware/

should probably interact somehow with https://github.com/komuw/goweb/issues/13


Hue does not honor port on redirects

I have a url to access HUE
http://myhue.com:443
All subsequent redirect requests are going to
http://myhue.com/accounts/login/?next=/

This seems weird. Do you proxy Hue correctly?