The pbix report doesn't work. The is no "QueryExecutionStartTimeUTC" in On Premise Gateway export logs

[Enter feedback here]

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

ID: 4a144b27-04b6-5d42-9c9f-79bb4cc6730b
Version Independent ID: 7b00f680-f3a8-3502-94b5-5ca37d36f432
Content: Monitor and optimize on-premises data gateway performance
Content Source: data-integration/gateway/service-gateway-performance.md
Product: on-premises-data-gateway
GitHub Login: @miquelladeboer
Microsoft Alias: mideboer

Thanks @zayca for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. Though the scope of our feedback channel here on GitHub covers specific documentation fixes, we can help redirect you to the right support channel to get an answer to your question. If this issue is still ongoing, please open a support incident through the Azure Portal by selecting the main top left menu, and then Help + Support, to provide details and create your incident that will be addressed by one of our support engineers. Because this issue does not relate to documentation, we are closing this issue. #please-close


libmodsecurity.so acts different when enabled with/without json support

We used to use libmodsecurity.so built without json support and all was fine. Recently we needed json support and rebuilt the module with "--with-yajl=/usr/local" , at first all was fine, json logging worked.  But we started to get blocks/403 which we was not receiving before. Before going into details of blocks, is there any reason for such different behaviour? we just rebuilt the module again without json support and all back to normal again. I remeber some of those blocks was 932130, 949110 . I know it would be better to share details about the requests and decide if blocks are valid or not, but this is not our concern we want stable module with json support like , we wish it work as it worked without json support

is there any reason for such different behaviour?

Yes, definitely!
If you add/enable JSON support in libmodsecurity3, then it means not just you can use audit.log in JSON format, but the engine will parse all Content-Type: application/json requests as JSON, and put the key-value pairs into ARGS target.
If any of those values are match with a rule, then rule will be triggered. The mentioned CRS rule (932130) checks ARGS collection, so probably that causes this behavior. The other rule (949110) is "just" an evaluation rule, which means it checks the TX score value. It's a consequence.

I see now, thank you for the information. Do you know any workarounds to make libmodsecurity3 use json only for audit.log? we would like to avoid any unexpected blocks on prod environments, yes maybe those blocks are valid but at this point we do not  wanna risk stability

Maybe commenting out following part? I see commenting it out helps. If libmodsecurity3 enabled without "--with-yajl" support then following would be dummy configs?
# Enable JSON request body parser.
# Initiate JSON Processor in case of JSON content-type; change accordingly
# if your application does not use 'application/json'
#
#SecRule REQUEST_HEADERS:Content-Type "application/json" \
#     "id:'200001',phase:1,t:none,t:lowercase,pass,nolog,ctl:requestBodyProcessor=JSON"

Yes, making inactive the rule 200001 will prevent to parse the JSON into ARGS.

@allahshukur-ahmadzada is there anything we can help you? If no, could you close this issue?


dmg: use compatible service name for config and socket

To align with Linux service definition.

This will solve the failure of

#477

I'm testing it on my fork: https://github.com/daipom/fluent-package-builder/actions/runs/5063945296

This will solve the failure of
* [dmg: add install test #477](https://github.com/fluent/fluent-package-builder/pull/477)

I'm testing it on my fork: https://github.com/daipom/fluent-package-builder/actions/runs/5063945296

Success!

Thanks!

Thanks for merging!


Re-enable @Flaky for JavaExecDebugIntegrationTest

Because it's still happening

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

OK, I've already triggered a build for you.


Call to 'intern()' on compile-time constant is unnecessary

Describe the situation before applying the recipe

final var query = """
                         My constant
                        """.intern();

Describe the situation after applying the recipe
final var query = """
                         My constant
  """;
--.intern()
++;

Any additional context
https://en.wikipedia.org/wiki/String_interning

Sounds like you're coming across interesting code bases there! Am I correct in thinking intern() called on any String literal ought to be unnecessary? That should make for an easy recipe if you're up for it.

Sounds like you're coming across interesting code bases there!

I am the one that was trying to be too clever but the luckily the IDE yelled at me 😄

Am I correct in thinking intern() called on any String literal ought to be unnecessary?

That seems to be the case
From https://docs.oracle.com/javase/specs/jls/se7/html/jls-3.html#jls-3.10.5

Moreover, a string literal always refers to the same instance of class String. This is because string literals - or, more generally, strings that are the values of constant expressions (§15.28) - are "interned" so as to share unique instances, using the method String.intern.


As a user I would like a package that handles keyv in offline mode

This should be an alternative package that wraps Keyv and handles when the backend is not responding and then sync up when it is available.

I guess this is the "offline" adatpter? i read the name from adapters list, visited package readme:

https://github.com/jaredwray/keyv/tree/26862ffb677013e88c82aec0de559a380d6e71e3/packages/offline

and that made me scratch my head. wtf is it.
i read the source code, and it doesn't seem to do anything:

https://github.com/jaredwray/keyv/blob/26862ffb677013e88c82aec0de559a380d6e71e3/packages/offline/src/index.ts

seems to proxy everything to keyv object. anyway this needs docs

@glensc - thanks for the note on this and with v5 coming out we will be deprecating this package.


chore: update changelog for next release

updates changelog for 9.0.0

PR considerations checklist:

[X] Updates CHANGELOG.md to reflect this PR's change.
[X] This Contribution is under the terms of Individual Contributor License Agreements (and also Corporate Contributor License Agreements to the extent applicable) appearing in the Apereo CLA roster.

Looks like the CI checks were failing and some were running when this was merged?

Good catch on the upgrading.md, @vertein . I'd forgotten about that.


HTTP status: 500 Internal Server Error

When I push my application to a private registry in my own namespace, I get the following error:
...\Docker>docker push registry.../namespace/application
6e7b8eefdb11: Pushing [==================================================>]  185.3kB
31f8d07a1a5e: Layer already exists
db0abfd144ab: Pushing [==================================================>]  116.7kB
bc693526588f: Layer already exists
38d7ba77fba6: Pushing [>                                                  ]    535kB/5.148GB
fcd8d39597dd: Layer already exists
875120aa853c: Layer already exists
f2cb0ecef392: Layer already exists
received unexpected HTTP status: 500 Internal Server Error

What I've tried so far:
Add "allow-nondistributable-artifacts": [         "localhost:5000"     ] to the settings (Docker Engine).
Restart the computer as well as Docker.
Docker logout and login again.
I don't know what could have changed. The application works flawlessly on my local machine and I got no errors a week before. The Docker file is unchanged.
How can I get more information about the failed push?
Docker version 19.03.8
Kubernetes 1.15.5

It looks like you're using Docker for Windows, which means you most likely are trying to push a Windows image to the registry. If so, see #89.

The server was actually down. =)


store associated production schema when creating non-production schema

Linkage between a non-production schema and a production schema is determined when the non-production schema is created.  Save the production schema name in the Provenance table of the non-production schema during creation. Fetch it when a connection to a schema is made.

I think I've addressed everything except for adding a unit test for the new db field.  I'm not sure such a test would accomplish much.  In fact I'd like to get rid of test_database.test_db_version (the only way it can fail is if you forget - as I did - to update the test.  It doesn't really test the code).  I'd also like to get rid of test_database_functions.test_db_version.  Here there is something to test - whether the database version of the current code is compatible with the database you're connecting to - but the test as it stands now, since the code version running the query is known to be the same as the one that created the db - doesn't really check that.
Instead there should be a check when people use the code for compatibility: major versions of db should match and minor version db for the code running should be >= minor version of the db it's connecting to.  This will take some rearranging to make the db versions associated with the running code, currently buried in create_registry_schema.py, accessible to TableMetadata.
I can do that in this PR or a separate one.

I'd also like to get rid of test_database_functions.test_db_version.

I'm happy for that "test" to go, it doesn't do anything as you say


Update to rust 2015-03-22

@alexcrichton

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @wycats (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. The way Github handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see CONTRIBUTING.md for more information.

This travis failure looks like a flake. This should be good to go. r? @alexcrichton

@bors: r+
Thanks!

:pushpin: Commit 901f66b has been approved by alexcrichton

:hourglass: Testing commit 901f66b with merge 8b808ff...

:broken_heart: Test failed - cargo-mac-32

@alexcrichton
macs flaked?
http://buildbot.rust-lang.org/builders/cargo-mac-32/builds/1022/steps/test/logs/stdio
http://buildbot.rust-lang.org/builders/cargo-mac-64/builds/1019/steps/test/logs/stdio
windows has an issue with access denied? (in addition to flakes)
http://buildbot.rust-lang.org/builders/cargo-win-32/builds/902/steps/test/logs/stdio
http://buildbot.rust-lang.org/builders/cargo-win-64/builds/546/steps/test/logs/stdio

Hm those do not look flaky, I haven't seen many of those before, I think that those failures warrant some investigation.

I had to apply this patch to get it to pass tests locally.

@alexcrichton nice, thanks for tracking that down!

@bors: r+ 907bfe7

:hourglass: Testing commit 907bfe7 with merge 8d4bf72...

:broken_heart: Test failed - cargo-win-64

@bors: retry
Now that's a spurious failure

:zap: Previous build results for cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-32 are reusable. Rebuilding only cargo-linux-32, cargo-win-64...

that linux travis build really had some trouble O.o

:sunny: Test successful - cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-32, cargo-win-64


Label the problem

Should I label all the semantic information in the image?
I've noticed that there is ignore_index=-1 in the train.py file, and I only mark the part of my image that I need to split, and I use the rest as the background, but when eval.py runs, there will be a lot of mis-segmentation of the background, but the main part is not divided, and I can divide the rest of the background labels after retraining, what is the reason for this.

I suspect that you intend to train AsymFormer on your custom dataset, which involves addressing the issue of data annotation. First, we'll explain why the background class should be ignored in the NYUv2 dataset, and then we'll discuss how to train on your custom dataset. In the NYUv2 dataset, the background class contains numerous unlabeled objects. Including the background class as a label during training could mislead the network's understanding of other categories. Therefore, the standard practice is to ignore the background class during both training and testing phases to accurately assess the network's performance. However, if your task is to differentiate between the foreground and background, then the scenario might be different. In such a case, you may not need to ignore your dataset's background class during the training and testing phases.
In actual practice, firstly, during the data annotation phase, you need to mark the background class as class 0, and eliminate the “target_scales[0] - 1” operation when computing the loss. Similarly, during testing, remove the "output = torch.max(pred, 1)[1] + 1" operation: output = torch.max(pred, 1)[1] + 1

In the NYUv2 dataset, class 0 represents the background class. During the training phase, we subtract 1 from all labels and ignore the label "-1", which effectively removes the background class from the training process. During the testing phase, we add 1 to all labels to ensure the output results align with the categories in the NYUv2 label image (the label 0 in "pred" is corresponding to label 1 in original NYUv2 label image). When training and testing on your own dataset, you might not need to apply these preprocessing and postprocessing steps.

Thanks for the reply, I understand.


Use perft tests like shakmaty

Copy all perft files from shamaty and use them for tests & benchmark.
TODO

[x] Perft parser
[x] Use perft files for tests
[x] Use perft files for benchmarking

The moving perft tests are pretty much done. The only question is should we try to fix tests or not? I believe it just how we calculate total moves.


图像分解训练代码

Hi, may I ask how the first half of the layer decomposition network is implemented? I feel in the figure of your paper that it is derived from training the deep network, but you put out the code for matlab direct decomposition and I feel some inconsistency? Can you give me the full code of the layer decomposition network?

It is from the deep network; we use the Matlab decomposition as initial guidance in Eq.2.
The code will release later.

It is from the deep network; we use the Matlab decomposition as initial guidance in Eq.2. The code will release later.

Thank you! Looking forward to the code open source soon


You must supply the volume mount even if you are accessing a secret via an env var

[Enter feedback here]
There is a reference that the secret can be reference independently however, you have to use a volume mount in your pod otherwise the k8s secret is never created.  Perhaps I just misinterpreted the documentation but I thought you were suggesting you could use an env var referencing the secret or use a volume mount.  Based on my testing you need the volume mount before the secret will be created.

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

ID: 409a3be9-4831-9401-0bb3-c65209bb3f42
Version Independent ID: 4cf81213-5989-f36c-7456-70accfe452c2
Content: Use the Azure Key Vault Provider for Secrets Store CSI Driver for Azure Kubernetes Service secrets - Azure Kubernetes Service
Content Source: articles/aks/csi-secrets-store-driver.md
Service: container-service
GitHub Login: @Nickomang
Microsoft Alias: nickoman

@rscottwatson
Thanks for the feedback! I have assigned the issue to content author to check and update the document as appropriate.

@Nickomang
Can you please check and add your comments on this doc update request as applicable.

Thank you @rscottwatson for the feedback!
We've added an item to our backlog and will prioritize accordingly.
#please-close


feat!: Docker CI - Security added & Tagging updates

Overview
trying out #1327 using a different account w/ write permissions as per @jrmanes' suggestion
Checklist

[ ] New and updated code has appropriate documentation
[ ] New and updated code has new and/or updated testing
[ ] Required CI checks are passing
[ ] Visual proof for any user facing features like CLI or documentation updates
[ ] Linked issues closed with keywords

closing, as this didn't work


Remove charset = latin1 from .editorconfig for batch files

The top .editorconfig rule charset = utf-8 now applies to batch files
mruby % file -I mrbgems/mruby-bin-config/mruby-config.bat
mrbgems/mruby-bin-config/mruby-config.bat: text/x-msdos-batch; charset=us-ascii

US-ASCII (basic English) is a 7-bit, 128 characters code page, originally designed for telegraphy.
UTF-8 encoding uses the same encoding as 7-bit ASCII for its first 128 characters. So a text file that only contains characters from that range of the first 128 characters will be identical at a byte level whether encoded with UTF-8 or 7-bit ASCII.
https://stackoverflow.com/questions/11303405/force-encode-from-us-ascii-to-utf-8-iconv

https://github.com/editorconfig/editorconfig/wiki/EditorConfig-Properties#charset
https://editorconfig.org/#supported-properties

Ah, I mistakenly equated "US-ASCII" with "Latin1".
If I remember correctly, batch files change encoding depending on the codepage used to run the file.
For example, if Windows is a Japanese environment, it is usually treated as "CP932".
It was my intention to limit the character set to 7-bit characters to minimize this effect.
I do not oppose this PR.
Hmmm, even if I could, it would only be to put the limitation to US-ASCII as a comment in .editorconfig.......


WIP : support for hloc toolbox (superpoint, superglue, netvlad,...)

This adds support for hloc which brings support for more recent features and matches such as superpoint and superglue.
I added command-line options to select the sfm toolbox (colmap, hloc), feature (sift, superpoint,...), and matcher (NN, superglue,...).
It requires hloc as dependency.

ok, I'll prepare a new version with these try/except for dependency, notification, and documentation update

I updated the PR :
hloc is now an optional dependency. If it is not installed, it will not cause any error except if we try to use a feature from it (superpoint, superglue,...), it will output a red error message : "Error: To use this set of parameters (superpoint_aachen/superglue/hloc), you must install hloc toolbox!!"
The documentation of ns-process-data has a new line "You may also want to install hloc for more feature detector and matcher options." with a link to the github page. The new cli arguments (sfm_tool, feature_type, matcher_type) have a description in the doc too.

When I use the command:
ns-process-data images --data /media/diana/001/c
--output /home/diana/NeRF/nerfstudio/selfdata/20230404/cc
--camera perspective
--matching vocab_tree
--sfm-tool hloc
--feature-type superpoint_aachen
--matcher-type superglue
--colmap-cmd /home/diana/COLMAP/colmap/build/src/exe/colmap
This error occurred:
scipy.io.matlab._miobase.MatReadError: Mat file appears to be empty.

Traceback (most recent call last):
File "/home/diana/anaconda3/envs/nerfstudio/bin/ns-process-data", line 8, in
sys.exit(entrypoint())
File "/home/diana/NeRF/nerfstudio/scripts/process_data.py", line 833, in entrypoint
tyro.cli(Commands).main()
File "/home/diana/NeRF/nerfstudio/scripts/process_data.py", line 165, in main
self._run_colmap(image_dir, colmap_dir)
File "/home/diana/NeRF/nerfstudio/scripts/process_data.py", line 231, in _run_colmap
hloc_utils.run_hloc(
File "/home/diana/NeRF/nerfstudio/nerfstudio/process_data/hloc_utils.py", line 110, in run_hloc
retrieval_path = extract_features.main(retrieval_conf, image_dir, outputs)
File "/home/diana/anaconda3/envs/nerfstudio/lib/python3.8/site-packages/torch/autograd/grad_mode.py", line 27, in decorate_context
return func(*args, **kwargs)
File "/home/diana/Tools/Hierarchical-Localization/hloc/extract_features.py", line 251, in main
model = Model(conf['model']).eval().to(device)
File "/home/diana/Tools/Hierarchical-Localization/hloc/utils/base_model.py", line 17, in init
self._init(conf)
File "/home/diana/Tools/Hierarchical-Localization/hloc/extractors/netvlad.py", line 82, in _init
mat = loadmat(checkpoint, struct_as_record=False, squeeze_me=True)
File "/home/diana/anaconda3/envs/nerfstudio/lib/python3.8/site-packages/scipy/io/matlab/_mio.py", line 225, in loadmat
MR, _ = mat_reader_factory(f, **kwargs)
File "/home/diana/anaconda3/envs/nerfstudio/lib/python3.8/site-packages/scipy/io/matlab/_mio.py", line 74, in mat_reader_factory
mjv, mnv = _get_matfile_version(byte_stream)
File "/home/diana/anaconda3/envs/nerfstudio/lib/python3.8/site-packages/scipy/io/matlab/_miobase.py", line 234, in _get_matfile_version
raise MatReadError("Mat file appears to be empty")
scipy.io.matlab._miobase.MatReadError: Mat file appears to be empty
Does anybody meet the same problem?  Know the reason or know how to solve this? ?  It is important and urgent for me!!! Thanks a lot!!!


CT-2722 Make smoke test work from local

You can run the smoke tests locally using a shared test email address and password sent by Email from Jav. The test profile is live under my Email address, there may be a need to have a shared Email for this.
Add it to your bash profile.
export HOST="https://peoplefinder.service.gov.uk/"
export<EMAIL_ADDRESS>export EMAIL_PASSWORD="xxx"
export SEARCH_NAME="Boris Zahariyas"
Test profile name: "Boris Zahariyas"
Host: "https://peoplefinder.service.gov.uk"

No longer required


use_enum_values dangerous from a typing perspective

Initial Checks

[X] I confirm that I'm using Pydantic V2 installed directly from the main branch, or equivalent

Description
Continuing the discussion from https://github.com/pydantic/pydantic/issues/6540
use_enum_values appears to be one of the only cases in pydantic where the type of the actual value in the model is not contained in the type annotation or the field info.  Consider the example code below... Foo.enum, despite being type annotated as a MyEnum, will be an int.
If you ran mypy on that script, you would get:
error: Unsupported operand types for + ("MyEnum" and "int")

While the mypy plugin could potentially (and probably should) catch and fix that, it is not the only issue.  Foo.model_fields is also lying about the type it contains.  That seems to me to stand in as a pretty stark contrast to the rest of pydantic (as a parsing library) that pretty much guarantees that what's inside an instance of a model is consistent with the type annotations.
Are there other cases where you would have to not only look at the field annotation but also in the model config to check what the type of a given field might be?
Example Code
from enum import Enum
from pydantic import BaseModel, ConfigDict

class MyEnum(Enum):
    A = 1
    B = 2

class Foo(BaseModel):
    enum: MyEnum
    model_config = ConfigDict(use_enum_values=True)

foo = Foo(enum=MyEnum.A)
val = foo.enum + 6

Python, Pydantic & OS Version
pydantic version: 2.0.2
        pydantic-core version: 2.1.2 release build profile
                 install path: /Users/talley/mambaforge/envs/test/lib/python3.11/site-packages/pydantic
               python version: 3.11.4 | packaged by conda-forge | (main, Jun 10 2023, 18:08:41) [Clang 15.0.7 ]
                     platform: macOS-13.4.1-arm64-arm-64bit
     optional deps. installed: ['typing-extensions']

Selected Assignee: @hramezani

use_enum_values is definitely an issue from a typing perspective, and I would strongly advise against its use. It was introduced in PR #127 over five years ago, at a time when a lot of this stuff was less mature, and I think if we had a chance to do it over it wouldn't be included.
For backwards compatibility reasons, I don't think it's a good idea for us to change the behavior with that setting enabled, but I think it will probably make sense to deprecate/remove that config option at some point.

That seems to me to stand in as a pretty stark contrast to the rest of pydantic (as a parsing library) that pretty much guarantees that what's inside an instance of a model is consistent with the type annotations.

Agreed

Are there other cases where you would have to not only look at the field annotation but also in the model config to check what the type of a given field might be?

Not to my knowledge, and in general I think we'd like to reduce/resolve them if possible. Again, I would view the use of use_enum_values = True as an anti-pattern.
If you want to propose related changes to the library, I'm open to proposals.

For backwards compatibility reasons, I don't think it's a good idea for us to change the behavior with that setting enabled, but I think it will probably make sense to deprecate/remove that config option at some point.

yep, makes sense.  certainly can't just break it unceremoniously :)  (v2 could be as good of a time to deprecate as any though?  given all the other breaking changes?)

If you want to propose related changes to the library, docs, etc., I think we're open to proposals.

I can think of a couple things:

you could emit a warning or even an exception if someone annotated a model with an enum, while also using use_enum_values
# Error
class Model(BaseModel):
    x: MyEnum
    model_config = {'use_enum_values': True}

# No Error
class Model(BaseModel):
    x: Literal['value1', 'value2']
    model_config = {'use_enum_values': True}

(of course, then you might want to associate the field with a specific enum, which I think should happen in Field())

I think for me, as a developer who sometimes consumes other libraries models, the nicest thing would be to update FieldInfo in some way to indicate that you won't be getting what model_config['field'].annotation tells you.  I recognize that it's weird to "lie" there too and say something that wasn't annotated, but then again, perhaps it's better to be consistent with the rest of pydantic and show what the field value is actually going to be.  So,
class Model(BaseModel):
    x: MyEnum
    model_config = {'use_enum_values': True}

print(Model.model_fields['x'].annotation)  # Annotated[Literal[...], MyEnum]  ... or something like that

... or anything else you can think of that wouldn't require someone to always check both the FieldInfo and the ConfigDict in order to determine what they're likely to find for that given field?

Just wanted to chime in to say that this tripped us up as well.
Since V3 seems to be happening eventually, can this option be officially scheduled for removal then? Perhaps in combination with a deprecation warning introduced in a V2.x release?

@ariebovenberg,

Since V3 seems to be happening eventually, can this option be officially scheduled for removal then? Perhaps in combination with a deprecation warning introduced in a V2.x release?

This should certainly be revisited V3, but we don't think it makes sense to introduce a deprecation warning for this field in a minor release, so a change like that will have to wait for V3. We'll keep everyone posted on this thread with regards to any changes for this setting!

I would say that this is pretty much a case use for DeprecationWarning


Looking for tips. not an issue. don't hate me.

Cloned your repo and it's not a problem with your code,
However, in my basically copy/pasted impletmentation,
AWS payload only sending back the first character of verification. Any idea what would cause that? I'm not grasping how AWS cognito is configured to return the state as verification.

Turns out I don't know how to copy/paste regex....
keep on keeping on!


tools/syz-verifier: cross-checking two kernels

Related to #200
gVisor is effectively another linux kernel implementation, so we could try to compare them side-by-side and maybe find some logical bugs. For starters we should just run corpus on linux once, capture results, run on gvisor, capture results and compare. This should give some idea about number of false positives.

Edit to this issue:
syz-verifier will provide a utility for cross-checking any two kernels (with one important milestone being cross-checking gVisor against linux)

Also, #2609 and #2649

FTR here is an interesting example of a real regression:
https://lwn.net/Articles/864947/
In short: edge-triggered epoll stopped unblocking threads if the buffer wasn't empty when a thread blocked.

FTR here is an announcement on regressions@ mailing list:
<EMAIL_ADDRESS>One idea proposed by Thorsten Leemhuis is that we can do something like git log --no-merges --oneline --grep "fix.*regression" fs/ | grep -v "performance regression" to get a list of past regressions to assess if syz-verifier is capable of finding them and make it find them.


Typo "Jupyter notebooks"→"Jupyter Notebooks"

https://docs.microsoft.com/en-us/azure/architecture/solution-ideas/articles/iot-using-cosmos-db

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

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

Hi @hyoshioka0128 - The product name is Jupyter Notebook, so, referring to Jupyter Notebooks when you mean a file or instance of the product isn't entirely accurate. As you wouldn't (correctly) say SQL Servers, because the product name is SQL Server. I've edited the commit and will merge.
Thanks for your continued contribution to the documentation.


Shutdown after run

This PR is an experiment in trying to make Run more robust in situations where shutdown can't be called.
It's probably not needed.

I've done something like that before and this simplifies the execution and closing of a toplevel if we want to close it right after completing the execution with Application.Run (true)and not terminating with the Application.Shutdown explicitly . However, if the app have multi-pages, handle Application.Run (true) is no longer option because all of these pages will call Application.RequestStop, causing the app to close and in that case we must have another way to the app be notified to be fully closed and, hence, it must be necessary to call the Application.Shutdown.


feature(cloud): Notifications cli

Feature scope
CLI (options, error messages, logging, etc.)
Description
Want to support a new config subcommand called notification to enable users to list, set, update, and delete notifications for webhooks and emails

https://github.com/meltano/meltano/pull/7968/files#r1301769040


Feature/global plugins

Allows to apply plugins globally to every API (by not specifying an api_id and not consumer_id).
Allows to apply plugins globally for a consumer (by not specifying and api_id, but by specifying a consumer_id).

Implements #295 and the first two points of #505.

to be reopened against next

Hello,
I would like to know, if actually there is the possibility to apply a plugins to all APIs. the call /apis/plugins does not work.
Thanks in advance

Hi @Amine.
Yes, it is possible. You have to apply it using the /plugins endpoint, not the /api/plugins endpoint.
Best regards.
Guilherme


Contact Page image should be changed to official image

This should be updated to official GDSC logo. Kindly assign me this under hacktoberfest 2023

Okay go for it! @Suhaani07


Passing String into Video ID

Hello,
I'm facing an issue passing a String into the .video(id: "psL_5RIBqnY"),
I have the YouTube ID being passed via  let trailer: String which outputs dynamically in the example the output is W1waReygdb0 how's the best way to dynamically update the ID for the player? I've attached a screenshot

Hi @jakeround,
How about writing an initializer for your YouTubeTrailer struct?
struct YouTubeTrailer: View {

    private let trailer: String

    private let title: String

    @StateObject
    private var youTubePlayer: YouTubePlayer

    init(trailer: String, title: String) {
        self.trailer = trailer
        self.title = title
        self._youTubePlayer = .init(
            wrappedValue: .init(
                source: .video(id: trailer),
                configuration: .init(
                    autoPlay: true
                )
            )
        )
    }

    var body: some View {
        // ...
    }

}

Alternatively, you can pass the trailer inside the body of your View if you just want to show the video and don't need to interact with the YouTubePlayer object directly.
struct YouTubeTrailer: View {

    let trailer: String

    let title: String

    var body: some View {
        VStack {
            Text(title)
            Text(trailer)
            YouTubePlayerView(
                .init(
                    source: .video(id: self.trailer),
                    configuration: .init(
                        autoPlay: true
                    )
                )
            ) { state in
                // ...
            }
        }
        // ...
    }

}

Hello @SvenTiigi
Amazing! That's solved my issue, appreciate the help!
Cheers,
Jake


Add filter to option select component

Improve the option select component by adding an option to provide a filter field, which shows/hides the checkboxes based on user input.

How it works:

filtering is applied as a user types, with setTimeout used to provide a delay to avoid unnecessary processing
filtering is done entirely in-page, no backend involvement, so reloading or returning to the page completely resets the filter
string matching is case insensitive, ignores punctuation and ignores the difference between & and 'and'
checked checkboxes are always shown regardless of what has been typed into the filter
checkbox labels are processed and cached on page load to optimise filtering
a hidden element is used to announce to screen readers the number of results that have been found with the filter, and also to provide context that something is happening when the filter is used

Test: https://finder-frontend-pr-907.herokuapp.com/component-guide/option-select/with_filter
Trello card: https://trello.com/c/ppFUeOhY/385-improve-option-select-functionality

Could you add the "How it works" to the commits description?

This could probably be a separate piece of work, but would some kind of clear filter functionality be useful?

@vanitabarrett yes, that's one of the things we considered.  I'm collating other issues relating to this component in this card: https://trello.com/c/8IBlJjn1/465-fix-option-select-issues so I've just added that.


Update service-bus-sas.md

The example shows an LF, not a CRLF.
the difference is the Carriage Return.
Please pull this.

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


update linuxkit readme

Although linuxkit/kubernetes has not been updated for a long time

/ok-to-test

@mikebrow updated. Thanks

/retest

/retest


Update aws libs & release 0.10.0

Update aws-sdk-dynamodb to 0.22 & release 0.10.0.
cargo publish is currently a manual step that I can (still) do or someone at truelayer can do, let me know if you have a preference.

Update aws-sdk-dynamodb to 0.22 & release 0.10.0.
cargo publish is currently a manual step that I can (still) do or someone at truelayer can do, let me know if you have a preference.

go for it. 👍

Update aws-sdk-dynamodb to 0.22 & release 0.10.0.
cargo publish is currently a manual step that I can (still) do or someone at truelayer can do, let me know if you have a preference.

can we add this in the CI? or is it not possible?

Update aws-sdk-dynamodb to 0.22 & release 0.10.0.
cargo publish is currently a manual step that I can (still) do or someone at truelayer can do, let me know if you have a preference.

can we add this in the CI? or is it not possible? Actually I dont know what cargo publish is, I am guessing it is creating a new tag/release for the library that pushes the lib to cloudsmit or some lib store 🤔

cargo publish is what releases to crates.io. We have no shared credentials setup on crates.io so there's currently no way for us to automate this

Thanks guys, I have published 0.10.0 :rocket:
I can't tag though any more, but I guess that's not strictly needed.


Uncaught TypeError: Cannot read properties of undefined (reading 'appendChild')

Hi,
I've downloaded and added the extension today. When I tried it for the first time it didn't work. I looked again into the extension manager and saw this error:

Later I've found this error as well:

Any ideas where might be a problem?
Btw. I am using Opera GX as a browser.
Thank you!

The first error is probably caused by not refreshing the page after loading the extension. I see you say this happened the first time, did the issue still persist? As for the second error, I have never found the cause of this error. It does not seem to effect anything so currently I am just ignoring it. There should not be a compatibility issue with Opera GX because it is based on chromium but I have never tested on it.
Also are you using a release?

I've tried reloading the page as well as reloading the whole browser, but none of these worked. I've downloaded the 1.1.0 release as it was the most recent one.

Well I've tried to remove the extension and add it again and it started working... There might have been some problem when I was adding the extension so it failed to work. I guess you can close this Issue thread then.
Anyways, thank you for reacting quickly and thanks for this extension! Needed it a lot.

Great! Glad its working now and that you like it!


feat(docker/stacks): introduce date info for stacks

closes #3889
CE-175

/azp run

/azp run

As an admin, deploying a stack..

@ncresswell I'm trying to understand, is there any problem with this?

As an admin, deploying a stack..

@ncresswell I'm trying to understand, is there any problem with this?

@chiptus no issue, i approved it.

@chiptus no issue, i approved it.

Awesome! :+1:

Awesome! :+1:


Incorrect LP token amounts calculated during imbalanced withdrawal

Please check: https://github.com/curvefi/curve-js/issues/285

duplicate of https://github.com/orgs/curvefi/projects/7/views/1?pane=issue&itemId=57715203


JMX exporter 0.16.0

See https://github.com/prometheus/jmx_exporter/releases/tag/parent-0.16.0
This version includes prometheus/jmx_exporter#587, meaning it should enable exposing the LongestTimePending metric of the CE process.

Maybe you see something that i don't.

Nope, there's nothing more. The only purpose of this PR is to help ops of a 8.9.x LTS deployment get back the CE metric they are currently missing (probably without knowing).
If you don't think it's worth touching the chart, you can close the PR, it' okay :-)

The only purpose of this PR is to help ops of a 8.9.x LTS deployment get back the CE metric they are currently missing (probably without knowing).

This is a good point. can you rebase against master? i updated the kind action with the hope that this will fix the control plane to become ready in time for the QA

Sure, I've just rebased and pushed --force, let's see how it goes.


Refactor rave_account.py

Refactoring of codebase required to be in python style depending on PEP-8. Start from rave_account.py

rave_account.py has been refactored according to python style depending on PEP-8. This closes #55

@siarheipuhach please close this issue. your PR has been merged.


Update cosign verify signed Kubernetes artifacts for 2.0

Update Verify Signed Kubernetes Artifacts instructions to work with Cosign 2.0. Fixes #39775

Note: I had to remove the Verifying images for all control plane components entry because the commands that are shown in it (curl -Ls https://sbom.k8s.io/$(curl -Ls https://dl.k8s.io/release/latest.txt)/release | grep 'PackageName: registry.k8s.io/' | awk '{print $2}') don't seem to work at all, at least in my tests. Perhaps this could be due to changes in the contents of both sbom.k8s.io and registry.k8s.io?
If you think this entry is important, I welcome suggestions on how to fix those commands to make them produce the desired output, a complete list of all the control plane images stored on registry.k8s.io. I tried several iterations of those commands but none worked for me.

FYI @kranurag7


Process crashes when duplicate headers are received in a request

I'm seeing the process crash due to duplicate key exception on some requests, and I was originally thinking maybe duplicate headers or url parameters, but running TCP dump doesn't show anything of concern.
This same code base works fine on fastcgi-mono-server4.
Unhandled Exception:
System.ArgumentException: An item with the same key has already been added.
at System.ThrowHelper.ThrowArgumentException (ExceptionResource resource) <0x41d7df30 + 0x0002b> in :0
at System.Collections.Generic.Dictionary2[TKey,TValue].Insert (System.Collections.Generic.TKey key, System.Collections.Generic.TValue value, Boolean add) <0x40ead100 + 0x0018b> in <filename unknown>:0   at System.Collections.Generic.Dictionary2[TKey,TValue].Add (System.Collections.Generic.TKey key, System.Collections.Generic.TValue value) <0x40ead0c0 + 0x00023> in :0
at Mono.WebServer.HyperFastCgi.Request.ParseParameters (System.Byte[] data, Boolean parseHeaders) <0x40fa70c0 + 0x001e7> in :0
at Mono.WebServer.HyperFastCgi.Request.AddParameterData (System.Byte[] data, Boolean parseHeaders) <0x40fa6e20 + 0x0009b> in :0
at Mono.WebServer.HyperFastCgi.NetworkConnector.ProcessRecord (Record record) <0x40fa62f0 + 0x00153> in :0
at Mono.WebServer.HyperFastCgi.NetworkConnector.ReceiveCallback (IAsyncResult ar) <0x40fa58e0 + 0x0058f> in :0
Anything hints at where the duplicate might be coming from?  I'm not sure what it means when it says "ParseParameters".  Parameters for what?
I'm running on the current 0.3.4 stable, and i'm not able to find any method matching ParseParameters (System.Byte[] data, Boolean parseHeaders) to investigate what might be happening in the source.  :/

Ok, i found the method, odd, but github search didn't find it for some reason.  https://github.com/xplicit/HyperFastCgi/blob/v0.3_stable/src/Mono.WebServer.HyperFastCgi/Request.cs#L134
Here is an example set of headers from tcpdump that cause it to crash, as you'll notice there are no duplicate keys:
User-Agent: Mozilla/5.0 (iPad; CPU OS 6_1_3 like Mac OS X) AppleWebKit/536.26 (KHTML, like Gecko) Mobile/10B329
Accept-Language: zh-cn
Accept: */*
X-Akamai-CONFIG-LOG-DETAIL: true
TE:  chunked;q=1.0
Connection: TE
Accept-Encoding: gzip
Akamai-Origin-Hop: 1
Via: 1.1 akamai.net(ghost) (AkamaiGHost)
X-Forwarded-For: <IP_ADDRESS>

My /etc/nginx/fastcgi_params that gets loaded for the host is:
fastcgi_param  QUERY_STRING       $query_string;
fastcgi_param  REQUEST_METHOD     $request_method;
fastcgi_param  CONTENT_TYPE       $content_type;
fastcgi_param  CONTENT_LENGTH     $content_length;

fastcgi_param  SCRIPT_NAME        $fastcgi_script_name;
fastcgi_param  REQUEST_URI        $request_uri;
fastcgi_param  DOCUMENT_URI       $document_uri;
fastcgi_param  DOCUMENT_ROOT      $document_root;
fastcgi_param  SERVER_PROTOCOL    $server_protocol;
fastcgi_param  HTTPS              $https if_not_empty;

fastcgi_param  GATEWAY_INTERFACE  CGI/1.1;
fastcgi_param  SERVER_SOFTWARE    nginx/$nginx_version;

fastcgi_param  REMOTE_ADDR        $remote_addr;
fastcgi_param  REMOTE_PORT        $remote_port;
fastcgi_param  SERVER_ADDR        $server_addr;
fastcgi_param  SERVER_PORT        $server_port;
fastcgi_param  SERVER_NAME        $server_name;

# mono
fastcgi_param PATH_INFO "";
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;

I may have misidentified the request that was crashing the service.  Now i'm seeing these problematic requests have two X-Forwarded-For headers, which seem to be injected by my haproxy loadbalancer.
Looking at their documentation at https://cbonte.github.io/haproxy-dconv/configuration-1.5.html#4.2-option forwardfor   It says:  Since this
header is always appended at the end of the existing header list, the server
must be configured to always use the last occurrence of this header only. See
the server's manual to find how to enable use of this standard header. Note
that only the last occurrence of the header must be used, since it is really
possible that the client has already brought one.
It looks like this is likely my case, where there is already one supplied, and its adding another instead of appending to a list of values.
Is it really the expected behavior of hyperfastcgi that it should crazy if multiple of the same header are received?  This seems like a huge potential for a DoS attack, right?

Please check that you don't have duplicate fast_cgi parameters in nginx config. You issue looks like that https://github.com/xplicit/HyperFastCgi/issues/18. Duplicate headers should be handled normally.
To localize the parameter, which breaks your request you can wrap method ParseParameters into try/catch and log the variable name.
If hyperfastcgi can be broken by duplicate headers, it should be easily reproduced by plain HTTP request with two strings of the same header name. If you have such one request, please post it here, because this request should not generate an exception

Yeah, I triple checked that i don't have duplicate values in nginx.conf / fastcgi_params, as i came across that ticket first.
I'll recompile a copy of the binary with the try/catch to try to isolate the parameter causing the issue as you suggested.  I'll also try breaking it with some calls with duplicate headers, to ensure that's not a point of attack.

First thing, the duplicate header test.  I just ran this, and on the first request it crashes the fastcgi process instantly. :(
curl -X GET -H "User-Agent: Mozilla/5.0 Gecko/2010 Firefox/5" -H "User-Agent: Mozilla/5.0 Gecko/2010 Firefox/6" "http://<IP_ADDRESS>:80/"

I think that header parsing needs to check for existence of a given header in the collection, and overwrite it if it already exists (last one wins) or something.  Because this is not good for production use if someone can take down a process this easy.  :/
Before I put together a pull request, is that a change you'd be open to?

Headers should not be owerwriten if they already exist in the array. According to RFC multiple headers should be concatenated by comma. I supposed that nginx should do that work on the front-end before sending requests to FastCGI backend. Need to check this nginx behaviour before doing fix. Also the fix should work carefully with nginx fast_cgi server variables (so it should concatenate only headers, but not server variables).
http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2

Multiple message-header fields with the same field-name MAY be present in a message if and only if the entire field-value for that header field is defined as a comma-separated list [i.e., #(values)]. It MUST be possible to combine the multiple header fields into one "field-name: field-value" pair, without changing the semantics of the message, by appending each subsequent field-value to the first, each separated by a comma. The order in which header fields with the same field-name are received is therefore significant to the interpretation of the combined field value, and thus a proxy MUST NOT change the order of these field values when a message is forwarded.

My test above was running through nginx and both still made it separately to the fastcgi process.  So it doesn't look like nginx is doing anything fancy here (at least by default) to combine those duplicate headers into single header with multiple values, etc.
How I understand this, is if someone did want send multiple header values with the same name,then they are expected to comma separate them but only pass a single header name with the multiple values.  If they did that then we don't have this issue.  If they however sent a malformed request (as i did), I think all bets are off as it's not supported by the protocol. In this case of the malformed request, I'd personally be OK taking either the first or the last, as long as the request doesn't crash the server, but maybe i'm missing something in protocol spec on how to handle it.
That said, I think this exposes a bigger issue in that there isn't enough isolation in the current request handling to prevent a malformed request from taking down the process, making it very susceptible to DoS attacks if any bug is found in request handling.  If there is a malformed request, or something unexpected happens while handling the request, it should only impact that specific request, not the entire process, IMO.

RFC says that multiple headers values must be equal comma-separated values of single header. So the logic in hyperfastcgi (if nginx does not combine multiple headers into single line) should be:

check the header exists in the dictionary
if not, add the header name and value
if exists concatenate new value to the old one.

example.
After parsing
X-Test: value1
X-Test: value2

HyperFastCgi should have an item in headers dictionary with the name 'X-Test'  and value 'value1, value2'

It seems to me that concatenating them together (if mulitple values are intended) would be the responsibility of the caller (thing adding the additional value) though, and if they didn't adhere to the RFC in sending the request then that's their problem.
Here's the issue I see with just concatenating everything:
Some things are expected to contain multiple values.
Example:
Accept-Encoding: gzip, deflate

or
Cache-Control: no-cache, max-age=0

Some things are (from what I've seen) assumed to only contain one, examples:
User-Agent
Host
Referer

If someone decided to send multiple values of one of those headers that are more or less assumed to have just one, and multiple get concatenated together, do we end up breaking more things downstream in frameworks/applications that have always assumed a single value?

We don't know which headers supports lists and which are not (also note that some headers can be user defined). User can send malformed HTTP request with two headers which do not support lists, or it can send the same request with one header with manually concatenated values. Both will be malformed and detecting and dropping out these malformed request is not the job of fastcgi backend, this should be done by front-end or even by routers/firewalls.
FastCGI just should pass HTTP request from nginx front-end to web application and return the response from web application to nginx front end, without any additional logic and without crashes.

Ok, so if it's not the job of fastcgi to scrub these requests, I'm fine with that.  But that said, if one malformed requestis received, and the entire process crashes, that is not good...

As I wrote before, the working logic with headers should be changed in HFC. Multiple headers should be concatenated into single one in HyperFastCGI  to avoid crashing.
The headers are just collected before sending to web application by creating corresponding ASP.NET HttpRequest. In ASP.NET headers are stored as NameValueCollection, so we can't cardinally change the behaviour of headers storing (for example in NodeJs multiple headers values stored as array). Anyway we must add only one header name to the final NameValueCollection in ASP.NET HttpRequest.

Ok, want me to take a swing at it?

All fixes will be appreciated

Regarding:

Also the fix should work carefully with nginx fast_cgi server variables (so it should concatenate only headers, but not server variables).

To be clear, when you say "server variables" do you mean something matching GetKnownRequestHeaderIndex(header)?

All headers are sent by FCGI protocol (except some special one like "Content-Length") start from the prefix "HTTP_".  During parsing FCGI request  prefix "HTTP_"  is removing and headers are adding to the headers dictionary. All other parameters not started with "HTTP_" prefix are server variables. So only headers should be concatenated, but not server variables.
In v0.4 there are functions ParseParameters and ReformatHttpHeader which do this job. If ReformatHttpHeader returns empty string then we deal with server variable, if string is not empty then we've got header.  In v0.3 the logic is the same.

OK thanks for the clarification.  I will do my changes based on v0.3, since it is stable release and I think this is a stability fix.

Right now "known headers" get completely overwritten by knownHeaders [idx] = value;
I'm assuming we should modify that to do the add or concatenate logic as well, right?

You are right, known headers must be also modified by concatenating new value


Can't use scrcpy after setting path

After I follow this https://github.com/Genymobile/scrcpy/issues/105, I still can't use scrcpy. I will explain it here hope someone can fix it for me. (I use scrcpy-win64-v1.4 prebuilt version for windows to mirror Oculus Go to notebook)

I try to set path of scrcpy as shown below

My directory contain as follows

I can run adb and scrcpy -h without problem.

But when i run scrcpy, it shows as follow

Also when I go scrcpy directory, I can run it without any problem.

Sorry for messing issue by closing and reopening it, I am newbie about Github.

https://github.com/Genymobile/scrcpy/issues/278#issuecomment-429330345

@rom1v  Thanks for your respond.
I am understand what cause the problem now by reading this paragraph.

The problem is that scrcpy pushes the scrcpy-server.jar that it finds in . (your current directory). If you start scrcpy from PATH, it expects scrcpy-server.jar to be in ., i.e. the current directory, the one from where you call (the Windows version is "portable", it overrides the server path).

But sorry I am dump. I don't know how to set SCRCPY_SERVER_PATH. Does it look like this one (For my case) ??

The variable value should be D:\Supavit\scrcpy\scrcpy-server.jra.

@rom1v  Thanks I will try it. I don't have that android with me now.

It is solved now.


feat: add arbitrary message signing

Try out this version of the Hiro Wallet - download extension builds.

closes #1051
Pending Todos:

[x] Sign + hash the message flow
[x] Signature Popup UI
[x] Error Handling
[x] Finalise the signature popup flow and return the signature value to the dapp
[x] Improve test-app
[x] Update connect https://github.com/hirosystems/connect/pull/205
[x] Add Prefix to messages, add convenient functions to stacks.js https://github.com/hirosystems/stacks.js/issues/1231
[x] handle custom connect and stacks.js packages so QA can test easily

Decoding message as Clarity Value (see https://github.com/hirosystems/stacks-wallet-web/issues/2387)
https://user-images.githubusercontent.com/1501454/165314261-521a271f-103b-4c78-9840-dc5bd92967ce.mov

@landitus This is the current implementation (just the warning message at the bottom is missing). Let me know if you find any issue.

@landitus

Thanks @beguene! I can't run the package cause it's failing, but I can review the screenshots for now.
A few observations:

Beware of the excess in spacing (top/bottom padding) in the hash drawer
The hash can use the Fira code typography, which is available in the codebase and a lighter color: text.subdued
The title "Message" is not needed
For the actual message box:
-- The rounded corners are a bit off. Check that they are 12px
-- Is the height of the box declared or due to top/bottom padding? I think that when the messages are short, it's nice to have a larger box and when they are longer (like for the tupple) the box should fit it's contents. I think we could declared a min-height property to accomplish that.

@landitus Yes you can't use this build yet, I need to fix a few packages first.
I will take into account your observations.

@beguene I can't seem to be able to test the Vercel deployment. When I click on the button Signature or Signature (long message), nothing happens.

@beguene I can't seem to be able to test the Vercel deployment. When I click on the button Signature or Signature (long message), nothing happens.

Have you installed the wallet from this build (see PR description)  ? Have you signed in into the test-app ?

@beguene I can't seem to be able to test the Vercel deployment. When I click on the button Signature or Signature (long message), nothing happens.

Have you installed the wallet from this build (see PR description) ? Have you signed in into the test-app ?

I was missing the right build. Now it works!
Here are my observations:

@beguene ,Thank you for setting the test app to test arbitrary message signing.
Quick question:

When the signature and signature (long message) is signed, are we able to view the tx in our wallet?
Noticed from the chat above on a note that the warning message at the bottom is missing, will this be an enhancement?If so, do we want to create a ticket to keep track of it?
Do we have limitation of words on the long message input box, if so what is restrictions?

Test results:
I was able to view the signature and public key via the console on users action via test app( this was for both signature and signature with long message)

Enhancements:
This isnt a bug but felt when user selects the 'show hash' under long message signature, the pop up screen pushes the sign and cancel button way below out of the window.Use can scroll down now but thought it would be nice to have it all visible in one popup box just to be consistent with the non long message signature(though am aware there is more text in here).Just my 2 cents.
Attaching the screen shot for your perusal ,maybe @landitus can help chime in his input here as well.
https://user-images.githubusercontent.com/38872890/165802220-5b96148b-a5bc-4d6d-aefc-5017664beb27.mov

Thanks a lot @Eshwari007 and @landitus for the feedback ! I will address it quickly.

@Eshwari007

"When the signature and signature (long message) is signed, are we able to view the tx in our wallet?"
No, no transaction is created when the wallet signs a message. The signature is not even broadcasted to the blockchain. It is simply sent back to the dapp.
I will add the notice message today.
We don't add a maximum message length (at least for now). The message is always hashed anyway before signature, so the only limitation is the max size of the string (limited by the browser). However the display of the message in the popup could indeed be really big. Maybe this could be an enhancement.

Regarding the bottom actions, we could maybe make the action buttons sticky to the bottom. @landitus let me know if you think it's a problem.

Regarding the bottom actions, we could maybe make the action buttons sticky to the bottom. @landitus let me know if you think it's a problem.

I see your points @Eshwari007 and it's something I'm wondering as well. TBH, as this is a design variation of the tx signing page, and that one doesn't have any sticky footer or buttons, I'm inclined to keep the design as-is and think of a future enhancement for both the tx and the message signing screens.

@landitus I fixed the issues you mentioned. Let me know if it's fine.

@landitus I fixed the issues you mentioned. Let me know if it's fine.

Thanks @beguene. this is looking very good! Just a few more comments I found

@landitus Thanks, those issues are fixed

Note that the separator is not exactly like in your design, it does not extend full to the sides. If it's still an issue, I can fix it in a separate issue.

@beguene Two quick findings/questions:
-Learn more about signing messages is directing to https://www.hiro.so/

Do we want to reword 'to prove you own this account and more' as having more at the end felt like hanging sentence.

Let me know if you want me to create an enhancement ticket for the above.
cc @markmhx

@sjwhitely it appears we do need an FAQ for this functionality after all. Mind drafting and providing its URL for integration? 🙏

Do we want to reword 'to prove you own this account and more' as having more at the end felt like hanging sentence.

I'd suggest improving this copy in general to:

By signing this message, you are authorizing "Testing App" to do something specific on your behalf. Only sign messages that you understand from apps that you trust. Learn more

@Eshwari007 @markmhx I updated the copy.

@beguene Two quick findings/questions: 1-Learn more about signing messages is directing to https://www.hiro.so/ 2- Do we want to reword 'to prove you own this account and more' as having more at the end felt like hanging sentence.
Let me know if you want me to create an enhancement ticket for the above. cc @markmhx

@beguene The rewording of the dialogue message in arbitrary message  is looking good. Will re test the link to 'Learn More' once @sjwhitely updates it.
Thanks


Inaccurate Search Result

Autocomplete Search Result is not accurate when searching with full text.  If I search for "Fayez", it shouldn't show other result. But its okay when I start typing two letter like "Fa".

How can I fix this issue?

Hi,
This has probably to do with the Haystack backend you're using. If using Elasticsearch (don't know if you are), I usually write my own custom engine which overwrites the DEFAULT_SETTINGS in order to make "autocomplete" act a bit more naturally...

Yes, I am using Elasticsearch as Haystack Backend.   Can you give me any hints about overwriting default settings and  achieve the functionality I described above?

Yup, but you'll have to wait a bit...
I'm currently a bit busy at work =)

Sure, I will wait.

Alright,
I just packaged up what I've been using to do autocomplete search with elasticsearch that "feels" a bit more like you'd expect autocomplete to behave.
Check out django-hesab (Django-Haystack-Autocomplete-Backend™)

@rhblind  Thank you for your time to making this package.  I will try it and let you know.  Seems like doc should need to update.

No problem, been thinking about it for a while since I always do this whenever I need to use haystack. Just as good to have it in a package =)
Let me know how if it works, so I can close the issue.
About the docs, I'm not so sure. The code kind of does what it should...

I have tested the package.  It is working now for exact match, but not working for partial match. I didn't modify the ES_BACKEND_SETTINGS. Look like default should work fine.  Here is my Indexing source code.
class ProjectIndex(indexes.SearchIndex, indexes.Indexable):
    text = indexes.CharField(document=True, use_template=True)
    id = indexes.CharField(model_attr="pk")
    title = indexes.CharField(model_attr="title")
    autocomplete = AutocompleteEdgeNgramField()

    @staticmethod
    def prepare_autocomplete(obj):
        seq = (u"{}".format(obj.title),)
        return ''.join(seq)

    def get_model(self):
        return Project

    def index_queryset(self, using=None):
        return self.get_model().objects.all()

So when I start typing "Java", Its not showing result for "Ja" or "Jav". Only return result for "Java".

As far as I can tell the AutocompleteEdgeNgramField and backend does what it should. I added some test cases which you can inspect if you'd like to..
If you still think there is any problems with the hesab backend, please open a ticket in the django-hesab repo.
Other than that I'm not quite sure what's going on... Does it work like expected in the python shell?
> results = SearchQureySet().autocomplete(autocomplete='jav')

I figured out the issue.  I was using elasticsearch 2.3.1 which causing the issue.  After removing 2.3.1 and installing 1.7.5 fixed the issue. Thanks again.  You have been a great help.  :D
You can close the ticket now.

Great!
Yeah, we're currently only supporting the 1.x branch. Need to wait for django-haystack to support v2.x, and then I'll have to do some  work to support it as well =/
Glad I could help!


Can direct the user to the prerequiste page when mvn is not in sys path

I'm thinking if we can direct to the Java Function prerequisite page if the extension detects mvn is not in sys path.
@EricJizbaMSFT Could we change the validateMavenInstalled() from return void to return boolean, and open the webpage in the catch block?

That sounds fine to me - just keep in mind that if you swallow the error, then we won't be able to track it in telemetry.
Currently any error you throw will be displayed to the user. However, @nturinski said he might make it possible to throw an error without displaying it to the user. This would allow you to have the custom error handling that you mentioned and still track the error in our telemetry.

@EricJizbaMSFT I'm thinking that could we export the TelemetryReporter into a standalone *.ts file, just like we do for the localize.ts. Then we can call callWithTelemetryAndErrorHandling without passing the report instance through several methods.

Addressed in #530


"Hide Minimap"

Overview: The Hide Minimap option no longer removes the minimap from its appropriate game screen region. This plugin did work ~1-2 weeks ago in resizeable mode. No longer works on fixed nor resizeable.

Reproduce: While logged in to OSRS, search "minimap" in the plugin configuration and tick the "hide minimap" option.
System: Windows 10 build 1803. Java 10 installed.

Duplicate of #976.
This is being worked on. I don't think we'll add it to fixed mode, though.

UPDATE: This plugin does work for resizeable when the side-panels are on "old school box" mode. It doesn't work on "bottom line" mode.


Template copy - no skin weights

when you copy a template under the current process, skin weights are not copying

This appears to be a permissions issue on Linux

Still encountering this issue on Linux

This was a problem with a difference between how windows and linux copies directories.  The parent path had to be given for the target path instead of the path to the duplicate folder.
This was fixed here
https://github.com/louisVottero/vtool/pull/253


UI TODO: add functionality to create event while in list view

Functionality now exists with 'Create Event' button.


[WIP] Add CLI to run the generators without having to add gem in the application directly

The aim of this PR is to allow users directly use generators without adding them in the application gem file. The cli would run something as follows:
boring tailwind:install

Closing in favor of #19


Named imports do not destructure

Despite looking very similar, named imports do not destructure.
So you can't do this in ES6:
import { foo: { bar } } from 'my-module';

Thanks ! Precision matters :+1: I still indicated it's a destructuring-like syntax since it follows the same spirit as a "explanation-shorter".
Tell me if you disagree, I'm open to discussion :wink:

You should also emphasize that they are completely different, since this is a common source of confusion.
This article from @kentcdodds summarizes it well.

That's indeed very important to emphasize this, you made me realized it's not even the same syntax for things such as renaming import (as instead of :). It will be done before the end of the day,

Besides, your reference pointed me to a very clear and concise explanation on this.


installLibrealsenseUVC.sh (Crash)

Unable to install 'installLibrealsenseUVC.sh' shell file on a newly flashed Jetson TX1 using 64-bit JetPack 2.2. Got the following errors:
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
git checkout -b new_branch_name
HEAD is now at ac753ca... Merge pull request #207 from mdhorn/arm64-cflags
patching file Makefile
Hunk #1 FAILED at 12.
1 out of 1 hunk FAILED -- saving rejects to file Makefile.rej
patching file librealsense.qtcreator/realsense.pro
patching file src/image.cpp
Hunk #1 FAILED at 8.
Hunk #2 succeeded at 66 with fuzz 2 (offset 2 lines).
Hunk #3 succeeded at 449 with fuzz 2 (offset 243 lines).
1 out of 3 hunks FAILED -- saving rejects to file src/image.cpp.rej
patching file src/uvc-v4l2.cpp
Hunk #1 succeeded at 249 (offset 2 lines).
mkdir -p obj/libuvc
mkdir -p lib
mkdir -p bin
cc src/verify.c -std=c89 -Iinclude -c -o obj/verify.o
g++ src/context.cpp -std=c++11 -fPIC -pedantic -Ofast -Wno-missing-field-initializers -Wno-switch -Wno-multichar -DRS_USE_LIBUVC_BACKEND pkg-config --cflags --libs libusb-1.0 -mfpu=neon -mfloat-abi=hard -ftree-vectorize -c -o obj/context.o
g++ src/device.cpp -std=c++11 -fPIC -pedantic -Ofast -Wno-missing-field-initializers -Wno-switch -Wno-multichar -DRS_USE_LIBUVC_BACKEND pkg-config --cflags --libs libusb-1.0 -mfpu=neon -mfloat-abi=hard -ftree-vectorize -c -o obj/device.o
g++ src/f200-private.cpp -std=c++11 -fPIC -pedantic -Ofast -Wno-missing-field-initializers -Wno-switch -Wno-multichar -DRS_USE_LIBUVC_BACKEND pkg-config --cflags --libs libusb-1.0 -mfpu=neon -mfloat-abi=hard -ftree-vectorize -c -o obj/f200-private.o
g++ src/f200.cpp -std=c++11 -fPIC -pedantic -Ofast -Wno-missing-field-initializers -Wno-switch -Wno-multichar -DRS_USE_LIBUVC_BACKEND pkg-config --cflags --libs libusb-1.0 -mfpu=neon -mfloat-abi=hard -ftree-vectorize -c -o obj/f200.o
g++ src/image.cpp -std=c++11 -fPIC -pedantic -Ofast -Wno-missing-field-initializers -Wno-switch -Wno-multichar -DRS_USE_LIBUVC_BACKEND pkg-config --cflags --libs libusb-1.0 -mfpu=neon -mfloat-abi=hard -ftree-vectorize -c -o obj/image.o
src/image.cpp: In function 'void rsimpl::unpack_yuy2(rsimpl::byte* const_, const rsimpl::byte_, int)':
src/image.cpp:470:58: error: there are no arguments to 'clamp_byte' that depend on a template parameter, so a declaration of 'clamp_byte' must be available [-fpermissive]
ptrOut[0] = clamp_byte((128 + 298 * c + 409 * e) >> 8); // red
^
src/image.cpp:470:58: note: (if you use '-fpermissive', G++ will accept your code, but allowing the use of an undeclared name is deprecated)
src/image.cpp:471:68: error: there are no arguments to 'clamp_byte' that depend on a template parameter, so a declaration of 'clamp_byte' must be available [-fpermissive]
ptrOut[1] = clamp_byte((128 + 298 * c - 100 * d - 208 * e) >> 8); // green
^
src/image.cpp:472:58: error: there are no arguments to 'clamp_byte' that depend on a template parameter, so a declaration of 'clamp_byte' must be available [-fpermissive]
ptrOut[2] = clamp_byte((128 + 298 * c + 516 * d) >> 8); // blue
^
src/image.cpp:474:58: error: there are no arguments to 'clamp_byte' that depend on a template parameter, so a declaration of 'clamp_byte' must be available [-fpermissive]
ptrOut[3] = clamp_byte((128 + 298 * c + 409 * e) >> 8); // red
^
src/image.cpp:475:68: error: there are no arguments to 'clamp_byte' that depend on a template parameter, so a declaration of 'clamp_byte' must be available [-fpermissive]
ptrOut[4] = clamp_byte((128 + 298 * c - 100 * d - 208 * e) >> 8); // green
^
src/image.cpp:476:58: error: there are no arguments to 'clamp_byte' that depend on a template parameter, so a declaration of 'clamp_byte' must be available [-fpermissive]
ptrOut[5] = clamp_byte((128 + 298 * c + 516 * d) >> 8); // blue
^
src/image.cpp: In function 'void rsimpl::deproject_z(float_, const rs_intrinsics&, const uint16_t_, float)':
src/image.cpp:486:98: error: 'deproject_depth' was not declared in this scope
deproject_depth(points, z_intrin, z_pixels, [z_scale](uint16_t z) { return z_scale * z; });
^
src/image.cpp: In function 'void rsimpl::deproject_disparity(float_, const rs_intrinsics&, const uint16_t_, float)':
src/image.cpp:491:146: error: 'deproject_depth' was not declared in this scope
deproject_depth(points, disparity_intrin, disparity_pixels, [disparity_scale](uint16_t disparity) { return disparity_scale / disparity; });
^
make: *** [obj/image.o] Error 1
mkdir -p obj/libuvc
mkdir -p lib
mkdir -p bin
g++ src/image.cpp -std=c++11 -fPIC -pedantic -Ofast -Wno-missing-field-initializers -Wno-switch -Wno-multichar -DRS_USE_V4L2_BACKEND pkg-config --cflags --libs libusb-1.0 -mfpu=neon -mfloat-abi=hard -ftree-vectorize -c -o obj/image.o
src/image.cpp: In function 'void rsimpl::unpack_yuy2(rsimpl::byte* const_, const rsimpl::byte_, int)':
src/image.cpp:470:58: error: there are no arguments to 'clamp_byte' that depend on a template parameter, so a declaration of 'clamp_byte' must be available [-fpermissive]
ptrOut[0] = clamp_byte((128 + 298 * c + 409 * e) >> 8); // red
^
src/image.cpp:470:58: note: (if you use '-fpermissive', G++ will accept your code, but allowing the use of an undeclared name is deprecated)
src/image.cpp:471:68: error: there are no arguments to 'clamp_byte' that depend on a template parameter, so a declaration of 'clamp_byte' must be available [-fpermissive]
ptrOut[1] = clamp_byte((128 + 298 * c - 100 * d - 208 * e) >> 8); // green
^
src/image.cpp:472:58: error: there are no arguments to 'clamp_byte' that depend on a template parameter, so a declaration of 'clamp_byte' must be available [-fpermissive]
ptrOut[2] = clamp_byte((128 + 298 * c + 516 * d) >> 8); // blue
^
src/image.cpp:474:58: error: there are no arguments to 'clamp_byte' that depend on a template parameter, so a declaration of 'clamp_byte' must be available [-fpermissive]
ptrOut[3] = clamp_byte((128 + 298 * c + 409 * e) >> 8); // red
^
src/image.cpp:475:68: error: there are no arguments to 'clamp_byte' that depend on a template parameter, so a declaration of 'clamp_byte' must be available [-fpermissive]
ptrOut[4] = clamp_byte((128 + 298 * c - 100 * d - 208 * e) >> 8); // green
^
src/image.cpp:476:58: error: there are no arguments to 'clamp_byte' that depend on a template parameter, so a declaration of 'clamp_byte' must be available [-fpermissive]
ptrOut[5] = clamp_byte((128 + 298 * c + 516 * d) >> 8); // blue
^
src/image.cpp: In function 'void rsimpl::deproject_z(float_, const rs_intrinsics&, const uint16_t_, float)':
src/image.cpp:486:98: error: 'deproject_depth' was not declared in this scope
deproject_depth(points, z_intrin, z_pixels, [z_scale](uint16_t z) { return z_scale * z; });
^
src/image.cpp: In function 'void rsimpl::deproject_disparity(float_, const rs_intrinsics&, const uint16_t_, float)':
src/image.cpp:491:146: error: 'deproject_depth' was not declared in this scope
deproject_depth(points, disparity_intrin, disparity_pixels, [disparity_scale](uint16_t disparity) { return disparity_scale / disparity; });
^
make: *** [obj/image.o] Error 1
Thanks

Yes, it looks like they added commits to a tagged version.
An important Git guideline is Never(*) modify commits that you have published.
The tags aren't meant to be mutable.
But anyway, I'll have to go back and come up with a work around.

Have a go at the latest version.

Now I got the same glfw compile error reported on issue #2

Are you running 64 bit L4T?

Yes but I'm going to give it a try on 32 bit as well

Please use the version in the repository for the TX1:
https://github.com/jetsonhacks/installLibrealsenseTX1


Work

README.md Linking (iOS) instructions had the old viro-react paths in the podfile. Update paths to @viro-community.

Looks like you messed something up :D
But thanks for the effort, you're right, this should be corrected. However the current iOS linking instructions are in the viro repository (see iOS Linking), which already contains the correct paths. So the correct solution is to remove the linking instructions from the readme in this starter-kit repo.

Yes, I did mess something up. I got confused by what branch I was on . This
is my first attempt at a pull request. Thanks for the response. Kurt
On Sun, Aug 1, 2021, 1:36 PM Marian Šámal @.***> wrote:

Looks like you messed something up :D
But thanks for the effort, you're right, this should be corrected. However
the current iOS linking instructions are in the viro repository (see iOS
Linking
https://github.com/ViroCommunity/viro/blob/main/readmes/INSTALL_IOS.md),
which already contains the correct paths. So the correct solution is to
remove the linking instructions from the readme in this starter-kit repo.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ViroCommunity/starter-kit/pull/16#issuecomment-890559513,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APTFWJZHRXPRR5ZLFDNT7BLT2WA27ANCNFSM5BKFPOMQ
.


Bus error (core dumped)!

Describe the bug
Has anybody met the Bus error? :(
/root/miniconda3/envs/neurad/lib/python3.8/multiprocessing/resource_tracker.py:216: UserWarning: resource_tracker: There appear to be 27 leaked semaphore objects to clean up at shutdown
  warnings.warn('resource_tracker: There appear to be %d '
Bus error (core dumped)

To Reproduce
Steps to reproduce the behavior:
Run the code:
python nerfstudio/scripts/train.py neurad pandaset-data --data <pandaset-path>

I thought it's the env problem. But, it's not. I try any ways of setting up env, check the details of setting process. The error still happened!   /cry

Hi! This could potentially be caused by running out of memory. How large is the VRAM of your system?
Side note, multi-processing doesn't always give the nicest tracebacks. You could try to run with --pipeline.datamanager.num_processes=0 to disable multi-processing.

Good idea! I use the default setting of docker building. This may be there is just a bit VRAM that can be used. I try to expand it and test again. Thanks!!!

You can always adjust the batch size and/or model size if it turns out that your machine can't handle our default settings. Have a look at our debug configurations for some guidance on how to run a smaller model: https://github.com/georghess/neurad-studio/blob/main/.vscode/launch.json#L51

It works!!!! Thanks! The error point is the limited VRAM. I expanded it to 128G. The Bus error was fixed. The smaller model setting is sweet and must be helpful for the guys who's machine is limited. Thanks again!

It works!!!! Thanks! The error point is the limited VRAM. I expanded it to 128G. The Bus error was fixed. The smaller model setting is sweet and must be helpful for the guys who's machine is limited. Thanks again!

Hey, I got the same error when running it in a docker container. What did you exactly do to solve it? My memory is 250gigs and 237gb is available for usage. Thanks

Hi! This could potentially be a sign of running out of memory. How large is the VRAM of your system? Side note, multi-processing doesn't always give the nicest tracebacks. You could try to run with --pipeline.datamanager.num_processes=0 to disable multi-processing.

Hey, the vram on my machine is : (glxinfo | egrep -i 'device|memory')
Memory info (GL_NVX_gpu_memory_info):
Dedicated video memory: 24576 MB
Total available memory: 24576 MB
Currently available dedicated video memory: 22128 MB
I'm running it inside a docker container on rtx3090 with 250gigs memory of which 237gb is available.

Hi. Could you try to run with --pipeline.datamanager.num_processes=0 and attach the log with the error you get?

Unrecognized or misplaced options: --pipeline.datamanager.num-processes                                                            │
│ ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── │
│ Perhaps you meant:                                                                                │
│     --pipeline.datamanager.num-processes INT                                                                                │
│         Number of processes to use for train data loading. More than 1 doesn't result in that much better performance (default: 6) │
│             in train.py neurad --help                                                                                │
│         Number of processes to use for train data loading. More than 1 doesn't result in that much better performance (default: 1) │
│             in train.py nerfacto --help                                                                                │
│             in train.py nerfacto-big --help                                                                                │
│             in train.py nerfacto-huge --help                                                                                │
│             [...]                                                                                │
│ ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── │
│ For full helptext, run train.py --help
When I set the flag to 0 and try running, it doesn't recognize the flag

Unrecognized or misplaced options: --pipeline.datamanager.num-processes │ │ ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── │ │ Perhaps you meant: │ │ --pipeline.datamanager.num-processes INT │ │ Number of processes to use for train data loading. More than 1 doesn't result in that much better performance (default: 6) │ │ in train.py neurad --help │ │ Number of processes to use for train data loading. More than 1 doesn't result in that much better performance (default: 1) │ │ in train.py nerfacto --help │ │ in train.py nerfacto-big --help │ │ in train.py nerfacto-huge --help │ │ [...] │ │ ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── │ │ For full helptext, run train.py --help
When I set the flag to 0 and try running, it doesn't recognize the flag

Maybe it's num_processes=0 ("_")? I fixed this error by expanding VRAM to 128G.

@amoghskanda Then you have most likely added the argument in the wrong place. It is an argument to the pipeline, so it should be added after the method name, not after the dataset name. For example:
python nerfstudio/scripts/train.py neurad --pipeline.datamanager.num_processes=0 pandaset-data --data data/pandaset

Note that the number of processes used to load the data is most likely not the issue here, but running without multi-processing (i.e by setting num_processes=0) usually gives a nicer error traceback.

@amoghskanda Then you have most likely added the argument in the wrong place. It is an argument to the pipeline, so it should be added after the method name, not after the dataset name. For example: python nerfstudio/scripts/train.py neurad --pipeline.datamanager.num_processes=0 pandaset-data --data data/pandaset

Hey thanks for this. It worked. I'm able to train neurad inside a docker container


change flex volume support from SP to pod identity

Prior to merge, a new "release" should be done for bedrock.  Also, remote references will need to be updated.  Tests require a new parameter, I will add to the build.

Closing as this PR is out of date.  Some work has been done other gaps identified by issues.


Messages not showing correctly in Electron Desktop app

I'm on latest stable Rocketchat Server (3.12.3)  and and latest Electron (3.1.1) for Linux (Ubuntu) . However since upgrading to RC server 3.12.3 In some channels the message  is now showing up correctly/fully (See screenshot)
In the mobile app it is showing just fine.
Any ideas?

In the mobile app it is showing just fine.
Any ideas?

Can you show how that messages looks like in Web version?

In the Web version it looks the  same as in the screenshot above.
In the mobile Android app it shows correctly:

In the Web version it looks the same as in Electron app as in the screenshot above.

So, it's Web version issue (front end team) but not specific Electron issue in that case.

Yes you are right!  I will open a Bug report there and we can close this.


One input unit

Hello,
Could you please explain in few words what is exactly one specific unit with the weight -30 in your example?
Thanks in advance!

Sorry,I don't know  what the example you have said.

@kladis it's a weight of the bias unit. If curios what exactly is a bias unit see for example this answer: http://stackoverflow.com/questions/2480650/role-of-bias-in-neural-networks


Dark mode button not visible

hey there,
This is a good first issue. Solve it soon and create a pull request for the hacktoberfest 2022

Hi @thekavikumar  please assign me this!

I would like to work on this issue. can u assign this issue to me?

If I could work on this issue, I would appreciate it.

Sure

Try adding some new icon for dark mode


v2021.5.21

this ci-release does not change any core-functionality of file jslint.js
doc - add file CHANGELOG.md
ci - begin addng regression tests and improve code-coverage.
ci - allow pull-requests to run restricted-ci (cannot upload artifacts).
gh-pages - fix missing assets and insecure http-links.
gh-pages - merge file jslint.css into index.html.
gh-pages - add files image-jslint-xxx.png.
gh-pages - cleanup asset naming-convention.
fix missing fonts in function.html and help.html.
add files .gitconfig, Daley-Bold.woff2, Programma-Bold.woff2, icon-folder-open-solid.svg, icon-window-maximize-regular.svg.
ci - fix http-links after moving to jslint-org.
doc - migrate file README to README.md with embedded ci links and screenshots.
ci - add macos and windows to ci-matrix.
ci - ci now fails if jslint-check fails for any of the files in branches.
ci - add github-workflows to generate code-coverage for jslint.js.

Ok


Messages containing only digits followed by a period are invisible

This only happens when the message is sent from Riot Web with Markdown input turned on, but Riot Web itself displays the message properly. The problem seems to be that it also produces a formatted_body containing an ordered list with a single empty item, which Riot Android then renders as an empty message.
This was tested on Riot Android 0.8.8.

Bug confirmed

(thanks for reporting)

The pb is also present on iOS (https://github.com/vector-im/riot-ios/issues/1897)

This seems related, but writing a message like:
`5. October 😊`

results in:

mobile: •October �
web: 1. October 😊

while desktop isn't technically a bug it's still probably not what users would expect to happen or necessarily understand why a date is being replaced by a different date.
I can create a separate issue for this for mobile and web if that's wanted.

It's related to Markdown formatting, so, despite the huge inconvenient, we have to say it's a feature, not a bug...
Also note that 123456. will not be displayed correctly as well on Riot-Web

I disagree, this is definitely a bug, but it's also not happening anymore on Riot Android 0.8.17 so it seems like it has been (inadvertently?) fixed! It now renders as 1., just like it should. I would argue it is still semantically incorrect, though, and that numbered lists with a single, empty item should be special-cased and not recognized as Markdown at all, but that is a Riot Web bug.
The wrong rendering of 123456. in Riot Web is a totally separate bug, judging by the result:

Alright even if we don't care about markdown not being consistent and not doing what users probably would expect, I'm still very confused about the emoji getting mangled.

I still have the issue with 1.. Maybe you have disabled the markdown?

I don't think so.
Riot Web:

Message source (as seen in Riot Web):
{
  "origin_server_ts":<PHONE_NUMBER>760,
  "sender": "@dkasak:termina.org.uk",
  "event_id": "$15398924031747tJKKp:termina.org.uk",
  "unsigned": {
    "age": 71,
    "transaction_id": "m1539892405307.30"
  },
  "content": {
    "body": "1.",
    "msgtype": "m.text",
    "formatted_body": "
\n

\n
\n",
    "format": "org.matrix.custom.html"
  },
  "type": "m.room.message",
  "room_id": "!DCRUrRQxGhHTRwlYla:termina.org.uk"
}

Riot Android:

Message source (as seen in Riot Android):

Riot Web version: 0.16.5
Riot Android version: 0.8.17 (G-b155)

So could this be reopened? It works in one client and it doesn't in another. It was also working in both clients for a bit as my screenshots show.
I also see a sensible workaround: don't consider empty lists as something the user intended and fall back on body in those cases. However, it might be more appropriate to fix it in Riot Web, such that it doesn't actually emit HTML at all when you type in ^[0-9]+\.\s*$ (or something like that) even in Markdown mode. In fact, this is what Riot Android does.
Should I open this issue on Riot Web?

I reopen the issue to not forget it, but I'm not sure what I can do for it.
Feel free to open an issue on Riot Web if you think it's appropriate.


tf.nn larger support for RaggedTensor

System information

TensorFlow version (you are using): 2.3
Are you willing to contribute it (Yes/No): Yes

Describe the feature and the current behavior/state.
I would like to be able to use tf.nn, and in turn tf.keras.layers such as Conv2D on RaggedTensor.
Will this change the current api? How?
I think it shouldn't in any way, just that keras layers and tf.nn operations should accept ragged tensors.
Who will benefit with this feature?
Anyone wanting to use keras layers on ragged tensors.
I am giving a bit more explanation on my specific use case below.
Any Other info.
So in my use case, I want to perform distributed training using images that have widely different sizes (and it doesn't make sense to pad them). I would want for each of the elements of the ragged tensor to be distributed on different GPUs.
But if I use a ragged tensor as is, it is not supported by my models with an error like:
TypeError: Failed to convert object of type <class 'tensorflow.python.ops.ragged.ragged_tensor.RaggedTensor'> to Tensor. Contents: tf.RaggedTensor(values=tf.RaggedTensor(values=tf.RaggedTensor(values=tf.RaggedTensor(values=Tensor("RaggedFromVariant/RaggedTensorFromVariant:4", shape=(None, 1), dtype=complex64), row_splits=Tensor("RaggedFromVariant/RaggedTensorFromVariant:3", shape=(None,), dtype=int64)), row_splits=Tensor("RaggedFromVariant/RaggedTensorFromVariant:2", shape=(None,), dtype=int64)), row_splits=Tensor("RaggedFromVariant/RaggedTensorFromVariant:1", shape=(None,), dtype=int64)), row_splits=Tensor("RaggedFromVariant/RaggedTensorFromVariant:0", shape=(None,), dtype=int64)). Consider casting elements to a supported type.

Even if I use the setting advised here, I still get this error.

Is this still an issue?  If so, can you provide a code snippet to reproduce it?

@zaccharieramzi Can you please share a simple standalone code as requested above? Thanks!

Yes sorry about the delayed response, I am not really suffering from this issue anymore, but here is a simple standalone code:
import tensorflow as tf
from tensorflow import keras
a = tf.ragged.stack([
  tf.random.normal(shape=[2, 2, 1]),
  tf.random.normal(shape=[3, 3, 1]),
], axis=0)
model = keras.models.Sequential(keras.layers.Conv2D(1, 3, padding='same'))
model(a)

You can find a colab here.

@edloper Can you please take a look at this issue. I can reproduce the issue with TF2.7. Thanks!


chore: Backport changes from internal repo

We had some bug fixes in our internal in-tree version, this backports those fixes.

#9
#8  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @Nava2 and the rest of your teammates on  Graphite


[FEAT REQ] Arrow coloring enhancement

Is your feature request related to a problem? Please describe.
I only want to color the protruding section of the arrow
Describe the solution you'd like
A prop or solution to just color the protruding arrow section
Describe alternatives you've considered
Tried to do it with css but having issues selecting just one section because of the way the arrow is drawn and would have to implement solutions for every arrow position
Additional context
The provided classNameArrow background color solution results in the entire box being colored like so...

I want to be able to just color the protruding section like so...

I'll leave this open for now since it might be viable in the future, but for now you can try something like this:
.react-tooltip__place-top .react-tooltip-arrow {
  background: linear-gradient(to right bottom, transparent 50%, red 50%);
}

.react-tooltip__place-right .react-tooltip-arrow {
  background: linear-gradient(to left bottom, transparent 50%, red 50%);
}

.react-tooltip__place-bottom .react-tooltip-arrow {
  background: linear-gradient(to left top, transparent 50%, red 50%);
}

.react-tooltip__place-left .react-tooltip-arrow {
  background: linear-gradient(to right top, transparent 50%, red 50%);
}

Just switch out red and you should be good to go.

Just leaving this here as a note for myself in the future:
/* internal css arrow class */
.arrow {
  ...
  /* this rotation should be relative to the tooltip placement, so the arrow "tip" is always the same CSS-wise */
  transform: rotate(45deg);
}


Better rendering of complex structs

Description :
We recently merged https://github.com/scaffold-eth/scaffold-eth-2/pull/702 into SE-2, we should get it working for Abi ninja too 🙌

Completed in #68


Horizontal scrolling? Mouse acting funny.

My crouton (xfce4 trusty) doesn't have a working horizontal scroll, is there a way to reconfigure this?
Also when I am coding in sublime the cursor will often random click where it is pointing. I have had this problem with previous installations on a different chromebook as well. At first I though I was accidentally touching the touch pad or something, but it sometimes happens when my hands aren't even near it. Any idea what is happening?

Can you provide the output of croutonversion, in the chroot?

crouton: version 1-20150127081428~master:e1bcac2b
release: trusty
architecture: amd64
targets: xfce
host: version 6680.17.0 (Official Build) beta-channel swanky

@drinkcat,
Can the target be simply 'xfce'? I thought xfce would pull in xorg, xiwi, or xephyr and gkt-extra at least - seems unusual to me.

@DennisLfromGA : targets only shows the one that we specified explicitly.
@thetrex : Just to confirm, you are not using crouton in a tab, right? (i.e. you are using Ctrl-Alt-Shift-Back/Forward to switch to crouton?)

@drinkcat : That is correct, I am not using crouton in a tab.

@thetrex : Sorry for the delay. X11 touchpad drivers sometimes have issues... You can play with synclient, first to enable horizontal scrolling, and then try to fix sensitivity. crouton modifies FingerLow and FingerHigh, but it might be that the values we use are not optimal.
#1302 will provide better drivers eventually.

Thanks, I got the touchpad working properly now.

Thank you, I got the touch pad working correctly now.


Emit Jelly file inside

Proof of concept quality: This currently makes empty-bodied <script> tags into CSP violations (see View/index.jelly).
WDYT? Worth pursuing?
Testing done

Submitter checklist

[ ] Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
[ ] Ensure that the pull request title represents the desired changelog entry
[ ] Please describe what you did
[ ] Link to relevant issues in GitHub or Jira
[ ] Link to relevant pull requests, esp. upstream and downstream changes
[ ] Ensure you have provided tests - that demonstrates feature works or fixes the issue

FTR from Daniel in Gitter:

It's a bit (very) limited given we're restricted to just 40 chars in Firefox at least, but perhaps this might end up useful?

nit suggestion

Seems less safe to do to me.
Also FTR I will need to confirm it's fine to not have //<![CDATA[ at the start of a block like this.


Error while executing make command

Thanks for the implementation.
I successfully ran the training part. For post processing, I tried to install fusible using the readme commands. I successfully ran cmake command with cuda 7.5 but while executing make command, I am getting the below error:
'''''
CMake Error at fusibile_generated_fusibile.cu.o.cmake:207 (message):
Error generating
~/MVSNet/mvsnet/fusibile/CMakeFiles/fusibile.dir//./fusibile_generated_fusibile.cu.o
CMakeFiles/fusibile.dir/build.make:63: recipe for target 'CMakeFiles/fusibile.dir/fusibile_generated_fusibile.cu.o' failed
make[2]: *** [CMakeFiles/fusibile.dir/fusibile_generated_fusibile.cu.o] Error 1
CMakeFiles/Makefile2:67: recipe for target 'CMakeFiles/fusibile.dir/all' failed
make[1]: *** [CMakeFiles/fusibile.dir/all] Error 2
Makefile:83: recipe for target 'all' failed
make: *** [all] Error 2
''''''''
Please help me!

Hi @pxu4114
Are you able to compile the original fusibile (https://github.com/kysucix/fusibile)?
Yao

Hi @YoYo000
Yes! I tried that too. Your repository says, cuda version required is 9.0 but when I run 'cmake .' it says need cuda 7.5 but found 9.0. So, I changed cuda to 7.5 and ran cmake which was successful but while doing make I am getting the error.
When I run the cmake using cuda 9.0, I am getting following error:
CMake Error at /usr/share/cmake-3.5/Modules/FindPackageHandleStandardArgs.cmake:148 (message):
Could NOT find CUDA: Found unsuitable version "9.0", but required is exact
version "7.5" (found usr/local/cuda-9.0)
Call Stack (most recent call first):
/usr/share/cmake-3.5/Modules/FindPackageHandleStandardArgs.cmake:386 (_FPHSA_FAILURE_MESSAGE)
/usr/share/cmake-3.5/Modules/FindCUDA.cmake:949 (find_package_handle_standard_args)
/usr/local/share/OpenCV/OpenCVConfig.cmake:67 (find_package)
/usr/local/share/OpenCV/OpenCVConfig.cmake:86 (find_host_package)
CMakeLists.txt:4 (find_package)

Hello, I also met the 'target all failed' problem when I run 'make', have you got the solution?


feat(manifest): add option to skip creating github release

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[x] Make sure to open an issue as a bug/issue before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[x] Ensure the tests and linter pass
[x] Code coverage does not decrease (if any source code was changed)
[x] Appropriate docs were updated (if necessary)

Fixes #1042 🦕
Here is a simple repo that shows the functionality: https://github.com/rabraghib/release-please-tests

@rabraghib this looks quite reasonable to me, will let @joeldodge79 chime in too.

thanks @bcoe for your feedback!!

@joeldodge79

@joeldodge79 fixed.

@rabraghib thank you for the contribution.


Update cats-effect, cats-effect-std to 3.3.3

Updates

org.typelevel:cats-effect
org.typelevel:cats-effect-std

from 3.3.2 to 3.3.3.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel" } ]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #48.