Playing HLS m3u8 links crash the app

Hi,
i tried to play this link https://bitdash-a.akamaihd.net/content/MI201109210084_1/m3u8s/f08e80da-bf1d-4e3d-8899-f0f6155f6efa.m3u8
But it is crashing the app.
in the logcat i see the following:
04-29 11:55:22.702  4076 12646 F libc    : Fatal signal 6 (SIGABRT), code -6 (SI_TKILL) in tid 12646 (VlcObject), pid 4076 (m.myapp)
04-29 11:55:22.799 12657 12657 E DEBUG   : failed to readlink /proc/12646/fd/218: No such file or directory
04-29 11:55:22.799 12657 12657 E DEBUG   : failed to readlink /proc/12646/fd/246: No such file or directory
please help me to solve this issue

hi @andy-io same here. have you found a fix on the issue?

@redefinered  : no i didnt manage to solve this issue.
If url has .m3u8 in it then use react-native-video library. this is my temporary solution

New feature requests and bug fixes
At the moment I am a bit tied up with other work. As a matter of fact, I don't get much time to develop at all nowadays. But I am more than open to help anyone who wants's to contribute to this repo. And I will be sure to merge any fixes as soon as PR's come up. But if you need someone to fix issues that affect you till I get back to this(ETA Q3 2022), One option is to add a bounty to the following site https://www.bountysource.com/ someone will attend to it.


Postgres allow change from int to bool and char to uuid

For boolean start by dropping defaults since its value is not a bool,
then convert all non-zero values to boolean true.
For uuid add USING:uuid

Looks good

Hi @dereuromark
this fix will enable Passbolt to support PostgreSQL, any idea on the timeline to get this shipped on a tag? Just to know how to prioritize. Thanks in advance for the feedback!


How I reproduce the pretraining from scratch.

Hi, I wanna to do pretraining from scratch. I am not sure whether I can use provided pretrain.yaml configure to directly run pretraining? This provided parameters is the same as paper? Thank you so much.

Hi,
Yes, you should be able to use the hyper-parameters in pretrain.yaml and the pre-training scripts (https://github.com/moment-timeseries-foundation-model/moment-research/blob/main/scripts/pretraining/pretraining.py) to pre-train models from scratch. The pre-training data (the Time Series Pile) is available here.
Best,
Mononito


Re: Common problem with deployment

Hello,
I have a lot of images stuck in pending, which could be related to one of the common problems you listed.
How do I run this command if I'm a non-privileged user on a non-minishift cluster? Thank you! @jcrossley3
minishift openshift config set --patch
'{"admissionConfig":
{"pluginConfig":
{"openshift.io/ImagePolicy":
{"configuration":
{"apiVersion": "v1",
"kind": "ImagePolicyConfig",
"resolveImages": "AttemptRewrite"}}}}}'

Here is a screen shot: https://nextcloud.sesp.northwestern.edu/index.php/s/b6od4zcdKzgbtdZ

hi,
what is the errors do you have in the pods logs?
Thanks

Sorry you're having trouble @ryannix123  Unfortunately, if you're not running on minishift, you're going to have to enlist the help of your cluster admin to set that ImagePolicyConfig. Our use of ImageStreams is a bit of a hack, tbh, and I think we're going to revert them back to normal images. Hopefully, that will get you going without needing the admin privs. I believe there's an upstream OpenShift bug causing this particular issue. You might check with those guys, but try your admin first.

Fortunately, I am the cluster admin so I can make this change to the single-node cluster I'm running. Thanks, @jcrossley3 !

@jcrossley3 Sorry to bug you again, but how to deploy this patch on an actual cluster? I've read https://blog.openshift.com/working-openshift-configurations/ and I still can't seem to figure it out.

@ryannix123  i think you need to add this config. in this file( master-config.yaml )and then restart
$ systemctl restart atomic-openshift-master
Thanks

Ah, thank makes sense. Thanks, @MohamedElso
So basically I have to edit this area of the YAML file:
admissionConfig:
pluginConfig:
BuildDefaults:
configuration:
apiVersion: v1
env: []
kind: BuildDefaultsConfig
resources:
limits: {}
requests: {}
with
    '{"admissionConfig":         {"pluginConfig":             {"openshift.io/ImagePolicy":                 {"configuration":                     {"apiVersion": "v1",                      "kind": "ImagePolicyConfig",                      "resolveImages": "AttemptRewrite"}}}}}'

@ryannix123  is this fix made any sense with you, I applied on the master config. I still have this problem
Failed to pull image "<IP_ADDRESS>:5000/openwhiskpoc/action-nodejs-6@sha256:bd3176824ead9191cbdd4b87ab2ec594c14f9b86cf37f7bab4d254a19792ef16": rpc error: code = 2 desc = error parsing HTTP 404 response body: json: cannot unmarshal number
@jcrossley3


JOSS review general comments

@athrasher7 Below are my review comments for SONIC openjournals/joss-reviews#6812

[ ] Please add a setup.m function and use the addpath command to automatically add all the main and subfolders to the main folder.

[x] Please add a readme.md to all the folders so that people can read easily what's going on in that folder.

[ ] Please add a one-sentence description of the licenses to each code file.

[ ] Please describe how people can contribute to this software package on the first page. Community guidelines: Are there clear guidelines for third parties wishing to 1) Contribute to the software 2) Report issues or problems with the software 3) Seek support.

[ ] In my personal project TsgFEM I use a MATLAB script called test_all.m (https://github.com/Muhao-Chen/Tensegrity_Finite_Element_Method_TsgFEM/blob/main/Software_Verification_and_Examples/test_all.m) to run all tests/demos automatically. Consider adopting a similar automated testing scheme.

[x] Please add more introduction to how to use the software to solve real-world analysis problems on the first page and the paper. It is preferred to have a few bullet points.

[ ] Other languages are used apart from Matlab and HTML. Consider writing a paragraph to clarify if related software or environment setup is needed.

[ ] Versions of MATLAB toolbox dependencies (Image Processing Toolbox, Computer Vision System Toolbox) and computer requirements need to be explained in more detail.

In regards to adding more about solving real-world problems, I've added a bullet point list in the readme, but the paper already includes a list in the first paragraph:
"Finally, SONIC offers solutions to the commonly encountered problems of star identification [@mortari2004][@lang2010], triangulation [@henry2023], Horizon-based OPNAV [@christian2021], and more."
These three are very real-world navigation problems. Is there something more you are looking for here? Thanks!

Thanks, @athrasher7; the changes look good to me.

Following up on the rest of the items:

SONIC was specifically designed to be used without a set up function. All of the internal folders are '+' folders, which means they are automatically added to the sonic path. The user only needs to add "sonic/" to the path of their working directory, which is a one-liner in MATLAB.
We are in contact with Georgia Tech's OTL about third party contributions. Once we hear back we will include a statement on this.
Thank you for the suggestion, but the SONIC demos are all Matlab live scripts, so a test script to run them wouldn't be intuitive. The user should run these demos locally and then compare the output to the pre-run demos in the API documentation to verify their installation. I've added a sentence to the readme stating this, and to the documentation.
The only languages should now be matlab and markdown. Previously there was more because of python scripts to customize the documentation. For organization, all documentation utilities were moved to a separate branch called Docs.
Version info was added.

Thanks again for the review! I will let you know when we add more info on third party contributions.

Thanks for the detailed reply. Very good!


Mustache evaluation fails on props attribute if it contains a newline

See this fiddle:
https://jsfiddle.net/davidkhess/vh1uzs5h/3/
For formatting purposes, it would be nice to be able to use newlines in the formatting of the attribute value.

Could you give an example where this is necessary? Mustache tags / directive values can only contain one expression/statement.

A large constant. In this particular case, for documentation purposes the value is best kept out of the model and in the template.
attribute="{{
    [
        {
            "key": "a",
            "value": "b"
        },
        {
            "key": "c",
            "value": "d"
        },
        {
            "key": "e",
            "value": "f"
        }
    ]
}}"

Thanks!


Update cantoIndex.js

fixes generator error when input is 1

all changes are up to date in latest PR


[MBL-1127] Dark mode

📲 What
Add forced dark mode to the app so the app matches the system theme and shows dark mode content
🤔 Why
Dark mode is one of the most requested features for android
🛠 How
Added a new theme for v29+ that includes
<item name="isLightTheme">true</item>
which forces the app into a dark theme.  This is not a permanent fix, but a quick win
👀 See

I![Screenshot_20240102-124043]

(https://github.com/kickstarter/android-oss/assets/7563288/be3814b0-2d86-4fe0-b4e5-3580d6961574)
📋 QA
Go through every screen in the app and confirm it looks good in both light and dark modes
NOTE:  The help page webviews (privacy policy, terms etc) will only appear in light mode
Story 📖
MBL-1127

Codecov Report
Attention: 82 lines in your changes are missing coverage. Please review.

Comparison is base (69c7220) 74.25% compared to head (87e57ae) 74.12%.

Files
Patch %
Lines

...ckstarter/ui/activities/compose/FormularyScreen.kt
0.00%
42 Missing :warning:

...arter/ui/activities/compose/ReportProjectScreen.kt
0.00%
24 Missing :warning:

...om/kickstarter/libs/utils/extensions/ContextExt.kt
0.00%
10 Missing :warning:

...ava/com/kickstarter/ui/toolbars/compose/ToolBar.kt
33.33%
1 Missing and 3 partials :warning:

...i/activities/compose/PreLaunchProjectPageScreen.kt
50.00%
1 Missing :warning:

...om/kickstarter/ui/views/compose/KsCreatorLayout.kt
0.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff              @@
##             master    #1922      +/-   ##
============================================
- Coverage     74.25%   74.12%   -0.13%
  Complexity     1963     1963
============================================
  Files           336      336
  Lines         19653    19685      +32
  Branches       2718     2718
============================================
- Hits          14593    14592       -1
- Misses         3490     3523      +33
  Partials       1570     1570

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


17 vs code

I have update the readme with the write up about downloading and setting up VS code.
Closes #17

I am still not able to see the movies

This is on my ONS computer.
I wonder if it's something to do with active content being blocked.


[GHSA-34q3-p352-c7q8] Central Dogma Authentication Bypass Vulnerability via Session Leakage

Updates

Affected products
CVSS

Comments
The original documentation was not correct so I fixed it.
https://github.com/line/centraldogma/security/advisories/GHSA-34q3-p352-c7q8

Hi there @minwoox! A community member has suggested an improvement to your security advisory. If approved, this change will affect the global advisory listed at github.com/advisories. It will not affect the version listed in your project repository.
This change will be reviewed by our Security Curation Team. If you have thoughts or feedback, please share them in a comment here! If this PR has already been closed, you can start a new community contribution for this advisory


Add custom askTitle and askMessage

Thanks! Sorry for not commenting on this PR earlier. My plan was to at some point change the property names and merge it, but #21 beat me to it.
Closing this now since that functionality has already been incorporated.


New version: DuckStudio.ChineseGit version 2.5

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[x] Is there a linked Issue?

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] This PR only modifies one (1) manifest

[x] Have you validated your manifest locally with winget validate --manifest <path>?

[ ] Have you tested your manifest locally with winget install --manifest <path>?

[x] Does your manifest conform to the 1.6 schema?

Replace #194832

Note: <path> is the directory's name containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

@fjwxzde

@wingetbot run

@wingetbot run

[!WARNING]
This pull request has been marked as "IEDS" for 7 days.

@wingetbot run

This package installs and launches normally in a Windows 10 VM.

Hi @DuckDuckStudio,
This manifest removes the DisplayVersion from the AppsAndFeaturesEntries, which is present in previous manifest versions. This entry should be added to this version, to maintain version matching, and prevent the 'upgrade always available' situation with this package.
(Automated response - build 900.)

@stephengillie - You may need to merge this PR manually


Dev/string fix

Fixes strings being added multiple times (including null string)

Fixed all of these issues. LMK if there's any more changes you'd like me to make. :)


[Feature] 增加黑白灰配色

可以不可以新增默认黑白灰的配色,这样才是ikun的主题色,或者新增一个avater组件,默认坤坤的svg

theme么？

你干嘛~

你干嘛~

Court next week, bring your code

哎呦～

这个UI
再多一眼看一眼就会爆炸
再近一点靠近点快被融化
鸡你太美～ｂａｂｙ～

你一下干嘛

再多一眼看一眼就会爆炸
再近一点靠近点快被融化

🐔再多一眼看一眼就会爆炸
🏀再近一点靠近点快被融化

小黑子，食不食油饼

Can someone translate maybe I can make PR?

Can someone translate maybe I can make PR?

I prefer to put this requirement on hold for the time being. This requirement is actually to create a theme with only black and white colors. However, I think that the current component library still needs to develop new components, and there is no plan to complete this requirement for the time being.


Comparable

Tonights pull request extends support for Comparable.  It attempts to find the best match in the base class rather than just assuming the most derived class is the correct match.

Codecov Report

Merging #649 into master will decrease coverage by 0.19%.
The diff coverage is 59.45%.

@@            Coverage Diff             @@
##           master     #649      +/-   ##
==========================================
- Coverage   78.52%   78.33%   -0.20%
==========================================
  Files         118      117       -1
  Lines        8755     8811      +56
  Branches     3715     3761      +46
==========================================
+ Hits         6875     6902      +27
- Misses       1373     1391      +18
- Partials      507      518      +11

Impacted Files
Coverage Δ

native/common/include/jp_class.h
90.90% <0.00%> (-5.87%)
:arrow_down:

native/common/include/jp_context.h
60.00% <ø> (ø)

native/common/include/jp_javaframe.h
100.00% <ø> (ø)

native/common/include/jp_modifier.h
92.30% <0.00%> (-7.70%)
:arrow_down:

native/java/org/jpype/manager/ModifierCode.java
0.00% <0.00%> (ø)

native/java/org/jpype/manager/TypeManager.java
0.00% <0.00%> (ø)

native/python/include/pyjp.h
100.00% <ø> (ø)

native/python/pyjp_object.cpp
66.41% <60.34%> (-4.83%)
:arrow_down:

native/common/jp_context.cpp
83.85% <100.00%> (+0.30%)
:arrow_up:

native/common/jp_javaframe.cpp
94.56% <100.00%> (+0.03%)
:arrow_up:

... and 2 more

Continue to review full report at Codecov.

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


MissingTransform error

When I "ztag -p 102 -P s7 -S banner  -i banner.json",
it return an error :
"File "/usr/local/bin/ztag", line 11, in
load_entry_point('ztag==1.0.0', 'console_scripts', 'ztag')()
File "/usr/local/lib/python2.7/dist-packages/ztag-1.0.0-py2.7.egg/ztag/main.py", line 112, in main
scan_id)
File "/usr/local/lib/python2.7/dist-packages/ztag-1.0.0-py2.7.egg/ztag/transformer.py", line 26, in find_transform
raise errors.MissingTransform
ztag.errors.MissingTransform",
I run this on Linux kali 4.8.0-kali1-amd64 ,
how ho solve this error?

The only transform we have for S7 is for the subprotocol szl. See https://github.com/zmap/ztag/blob/86ef36d7afd366da5e2ff2cb6ac4c136d13ff5f4/ztag/transforms/s7.py.
Try running ztag -p 102 -P s7 -S szl -i banner.json. If ztag yells at you about needing a scan id, add -s 1.

Is there any user mannual about verbose useage yhe protocol and subprotocol>

Unfortunately, no. Your best bet is to grep through the transforms folder.


Export Master Patient List as XML Cat I

Is there a way to export the master patient list for the bundle as either XML Cat I or HTML?  Older versions of Project Cypress contained this feature (2.7.0 and below.)

This should be available in Cypress 3.0.1


VirtualMachineOperations list_all() method returns invalid ID value

The ID attribute on the VirtualMachine objects being returned seems to include a resourceGroups value in ALL CAPS rather than mixed case.  Here is an example of an ID value being returned:
/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/resourceGroups/GALAXY-PRODUCTION/providers/Microsoft.Compute/virtualMachines/xxxxxxxxxxx
Notice the 'GALAXY-PRODUCTION' value for resourceGroups. In this case it is expected to be 'galaxy-production'.

The resource group name is not case sensitive, there is no difference between 'GALAXY-PRODUCTION' and 'galaxy-production'. You will use the same Resource group.
Then, it's not an invalid ID, since you can use it with no problem. If not, can you provide an example of scenario where the caps version in the ID prevents you for using the SDK?

The issue is that I'm relying on the ID to figure out the resource group to which the VM belongs. The VM object doesn't include the resource group.
It's not an issue with the SDK. It's an inconsistency in the API. Is there a way to kick this to the API team?

@devigned Do you have a contact in Compute team to discuss this point?

@singhkay, can you provide some guidance on this one?

@chouseknecht Is this only with VM APIs?

I have only tried using VirtualMachineOperations with the Compute Management Client, so I don't know if other operations return the resource group name in all caps. I do know that other clients (i.e. storage management, network management, etc.) return the resource group name as expected - in mixed case. VM operations is the first and only place I have seen it show up in all caps, that's why it feels like a bug.

@chouseknecht Got it, let me check with the compute dev team and see what's up.

Hi @chouseknecht
In october 2016 we released version 0.30.0 of the azure-mgmt-compute package (current is 0.32.1) based on a new RestAPI version. I re-tested recently (2016-12-22) with this new RestAPI version and wasn't able to reproduce it anymore. Could you confirm you no longer experience this issue?
Thank you,

Looks like this is fixed now indeed.

@singhkays for guidance

@lmazuel In the past when I've discussed with the dev team, the answer has been that this is expected. The case on the rg name is not expected to be preserved. cc: Adding @nibhat since he owns Compute RP and might want to look into this

Cleaning up old issues from 2016 - 2018. Please reactivate this if it is still a problem.


Add extra configurations

These changes provide couple of useful features:

Enable necessary chrome domains only or enable some extras alongside default ones. You can check out usage in "scrape" example.
MsgHooks that allow you to intercept messages from chrome and do something with them. Quite a basic use case is to capture http status code, which can be quite important for scraping. Check out "scrape" example.
Added Config struct. MsgHooks and extra chrome domains add new variables to pass to NewTargetHandler, which is a bit messy, so I packed them up for ease of use and more concise code.

None of these changes should break any pre-existing code.

Coverage increased (+0.3%) to 67.02% when pulling ffbd9f50f0fa92a445efe3945e1b9c32a4e74f10 on igsky:master into 28f0ea85637dd6c090267c379774a7a789a797f2 on knq:master.

These are too many different, unrelated changes in one pull request. Please separate these and flatten/rebase each into separate PRs. I'm definitely willing to merge many of these, but these need to be properly separated, "atomic" and clean.

It's literally my first PR, so it's all over the place, sorry about that. I'll fix it ASAP.


Use with Jetstream

I wonder, Could I use TicketIt with Laravel Jetstream rather than auth.
Jetstream has a bootstrap Auth system comes with Laravel 8.

i have question please
is ticketit system still work with laravel 8? i mean the latest verisions of php and laravel


Hierarchical HTTP cache implementation is not working

Title: Hierarchical HTTP cache implementation is not working as expected.
Description:
I want to implement a Cache hierarchy. My scenario is as follows:
I have three envoy servers chained together and one cache service at the end: Main -> Intermediate -> Final -> Service.
For the service I am using the code provided for the cache filter here:
https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_filters/cache_filter
For the Main envoy configuration is as follows:

static_resources:
  listeners:
  - name: listener_tcp
    address:
      socket_address:
        protocol: TCP
        address: <IP_ADDRESS>
        port_value: 8000
    filter_chains:
    - filters:
      - name: envoy.filters.network.http_connection_manager
        typed_config:
          "@type": type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager
          codec_type: AUTO
          stat_prefix: ingress_http
          route_config:
            name: local_route
            virtual_hosts:
            - name: backend
              domains:
              - "*"
              routes:
              - match:
                  prefix: "/"
                route:
                #return 503 after 20s
                  timeout: 0s
                  retry_policy:
                      retry_on: 5xx,refused-stream,connect-failure,gateway-error,reset,refused-stream
                      num_retries: 4
                      per_try_timeout: 5s
                  cluster: envoyInt
          http_filters:
          - name: "envoy.filters.http.cache"
            typed_config:
              "@type": "type.googleapis.com/envoy.extensions.filters.http.cache.v3.CacheConfig"
              typed_config:
                "@type": "type.googleapis.com/envoy.extensions.http.cache.simple_http_cache.v3.SimpleHttpCacheConfig"
          - name: envoy.filters.http.router
            typed_config:
              "@type": type.googleapis.com/envoy.extensions.filters.http.router.v3.Router

  clusters:
  - name: envoyInt
    connect_timeout: 5s
    type: STRICT_DNS
    load_assignment:
      cluster_name: envoyInt
      endpoints:
      - lb_endpoints:
        - endpoint:
            address:
              socket_address:
                address: envoy_int
                port_value: 8001

Main just forwards any request to the intermediate envoy. Config of Intermediate envoy is as follows:
static_resources:
  listeners:
  - name: listener_tcp
    address:
      socket_address:
        protocol: TCP
        address: <IP_ADDRESS>
        port_value: 8001
    filter_chains:
    - filters:
      - name: envoy.filters.network.http_connection_manager
        typed_config:
          "@type": type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager
          codec_type: AUTO
          stat_prefix: ingress_http
          route_config:
            name: local_route
            virtual_hosts:
            - name: backend
              domains:
              - "*"
              routes:
              - match:
                  prefix: "/"
                route:
                #return 503 after 20s
                  timeout: 0s
                  retry_policy:
                      retry_on: 5xx,refused-stream,connect-failure,gateway-error,reset,refused-stream
                      num_retries: 4
                      per_try_timeout: 5s
                  cluster: envoyFinal
          http_filters:
          - name: "envoy.filters.http.cache"
            typed_config:
              "@type": "type.googleapis.com/envoy.extensions.filters.http.cache.v3.CacheConfig"
              typed_config:
                "@type": "type.googleapis.com/envoy.extensions.http.cache.simple_http_cache.v3.SimpleHttpCacheConfig"
          - name: envoy.filters.http.router
            typed_config:
              "@type": type.googleapis.com/envoy.extensions.filters.http.router.v3.Router

  clusters:
  - name: envoyFinal
    connect_timeout: 5s
    type: STRICT_DNS
    load_assignment:
      cluster_name: envoyFinal
      endpoints:
      - lb_endpoints:
        - endpoint:
            address:
              socket_address:
                address: envoy_final
                port_value: 8002

Intermediate envoy forwards to Final envoy and the config of Final is as follows (very similar to cache filter example)

static_resources:
  listeners:
  - address:
      socket_address:
        address: <IP_ADDRESS>
        port_value: 8002
    filter_chains:
    - filters:
      - name: envoy.filters.network.http_connection_manager
        typed_config:
          "@type": type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager
          codec_type: AUTO
          stat_prefix: ingress_http
          route_config:
            name: local_route
            virtual_hosts:
            - name: backend
              domains:
              - "*"
              routes:
              - match:
                  prefix: "/service/1"
                route:
                  cluster: service1
              - match:
                  prefix: "/service/2"
                route:
                  cluster: service2
          http_filters:
          - name: "envoy.filters.http.cache"
            typed_config:
              "@type": "type.googleapis.com/envoy.extensions.filters.http.cache.v3.CacheConfig"
              typed_config:
                "@type": "type.googleapis.com/envoy.extensions.http.cache.simple_http_cache.v3.SimpleHttpCacheConfig"
          - name: envoy.filters.http.router
            typed_config:
              "@type": type.googleapis.com/envoy.extensions.filters.http.router.v3.Router

  clusters:
  - name: service1
    type: STRICT_DNS
    lb_policy: ROUND_ROBIN
    load_assignment:
      cluster_name: service1
      endpoints:
      - lb_endpoints:
        - endpoint:
            address:
              socket_address:
                address: service1
                port_value: 8080
  - name: service2
    type: STRICT_DNS
    lb_policy: ROUND_ROBIN
    load_assignment:
      cluster_name: service2
      endpoints:
      - lb_endpoints:
        - endpoint:
            address:
              socket_address:
                address: service2
                port_value: 8080

So, each envoy node can cache HTTP requests. My scenario is as follows:
1- I send a request to Final envoy:
curl -i localhost:8002/service/1/valid-for-minute
2- repeat the request and see the content is cached
3- send the request to Main envoy:
curl -i localhost:8000/service/1/valid-for-minute
4- I expect to see the cached response that is returned from the Final envoy node, but a new response is generated.
I think the cache implementation acts based on the whole header instead of the original parts of the request, and since each envoy server node adds its own x-forward-id header, we do not see a cache hit.

cc @ravenblackx

I think the cache implementation acts based on the whole header instead of the original parts of the request, and since each envoy server node adds its own x-forward-id header, we do not see a cache hit.

Headers in general aren't part of the cache key unless they're configured Vary headers (implementation, with TODOs!)
I think probably what you're seeing here is the host header for your curl request says localhost, and the host header for the cache-to-cache request does not?

You could test my hypothesis by issuing the request through "main envoy", then restarting "main envoy" so its internal cache is erased, then issuing the same request again, and see if the second time pulls it from the intermediate cache.

Thank you. Your experiment works. However, the only difference between host headers is that one of them is from localhost:8000 and the other is from localhost:8001. I attached a picture below for better clarification.
. Is this because of port number?

Yes, the port number is doing it. You could also make your curl request do what you expected, then, with something like
curl --header "Host: localhost:8001" -i localhost:8000/service/1/valid-for-minute
(Note, they're not from localhost:8000 and localhost:8001; the host header is about what's being requested, so it makes sense for the cache to give different responses for requests that are for data from different sources.)


Incorrect instructions in dapr development setup guide for Windows

Expected Behavior

Actual Behavior
This step for Windows env is incorrect:-
https://github.com/dapr/dapr/blob/master/docs/development/developing-dapr.md#windows
GOPATH=c:\go
PATH=%GOPATH%\bin;...
This should be:-
set GOPATH=c:\go
set PATH=%PATH%;%GOPATH%\bin;
Steps to Reproduce the Problem

Raised against the wrong repo


wsl --unregister doesn't cause Linux distribution to disappear from New Tab drop-down list

Environment
Windows build number: 10.0.18363.0
Windows Terminal version: 1.0.1401.0

WSL enabled
Ubuntu 18.04 LTS
Ubuntu 20.04 LTS

Steps to reproduce
In power shell type:
wsl --unregister Ubuntu-18.04
Expected behavior
Ubuntu 18.04 disappears from the New Tab drop-down list (preferably: immidiately, could be: after restarting Windows Terminal).
Actual behavior
Even after restarting Windows Terminal Ubuntu 18.04 is still there:

After selecting it process exits with code<PHONE_NUMBER>:

If the Ubuntu entry was created by Terminal, it will be removed on the next launch.
If you’re not seeing that behavior, can you share the output of wsl -l after removing a distribution?

Every entry was created when I've installed Ubuntu from Microsoft Store.
The output of wsl -l after removing the distribution was as expected:
Windows Subsystem for Linux Distributions:
Ubuntu-20.04 (Default)

Wait to be clear - when you relaunch the terminal, does the uninstalled distro get removed from the list of profiles?

No, it didn't. I tried restarting terminal as well as Windows. Eventually, it got removed when I removed the entry on my own in settings.json.

Well, that's certainly unexpected then.

Hey @matkaz, would you mind sharing your settings file?

@DHowett sure: settings.json.txt.
Please, keep in mind that I've already removed the faulty entry. One thing that I noticed while removing the entry was that it had much more fields than Ubuntu 20.04 entry. It resembled Azure or PowerShell entries.
(Also: I've renamed settings.json to setting.json.txt as GitHub complains about attaching a file with .json extension...)

much more fields than Ubuntu 20.04

So, yeah, this is what I was wondering about. There's a narrow band of settings files that predated version 0.5 (yours looks like one of them!) that still had WSL autodetection applied to them. To preserve user data/user customization, those settings files aren't migrated or replaced.
Unfortunately, they didn't include enough information for Terminal to use to automatically hide WSL distributions that were removed after the settings block for them was generated. Terminal errs on the side of caution here and keeps the profile around.
At the end of the day, those old profiles are indistinguishable from profiles you have added yourself. We wouldn't want to delete one of those :smile:
It looks like you came in after 0.2 or 0.3 (since your default key bindings are on ctrl+shift instead of just ctrl), so migrating will be a lot less painful. If you're interested, Scott Hanselman put together a blog post about the new settings and how you can migrate. If you're comfortable doing so, I'd recommend it.

(The new settings file format leaves out 90% of the information in the old one, and gives you more pointers about where to apply customizations.)
I'm gonna close this one out as "old settings file; an abundance of caution stopped us from deleting a profile we thought was yours". In the future, all autodetected profiles (profiles with a source) will be handled correctly.


[WFCORE-654] : Configuration files get default permissions when written.

Using Nio2 API to try to create the temporary configuration file with the same attributes as the orignal configuration file.
Jira: https://issues.jboss.org/browse/WFCORE-654

Windows Build 1732 is now running using a merge of 9882ffe542aeffc706d6184c60969c9b9a1e44f9

Linux Build 2205 is now running using a merge of 9882ffe542aeffc706d6184c60969c9b9a1e44f9

Core - Full Integration Build 1344 is now running using a merge of 9882ffe542aeffc706d6184c60969c9b9a1e44f9

Windows Build 1732 outcome was FAILURE using a merge of 13c1aa3e8a7bdf63ddf74865dbc4c2ba20ddfbf2
Summary: Tests failed: 2 (2 new), passed: 3375, ignored: 63 Build time: 0:34:02
Build problems:
Failed tests detected
Failed tests
org.jboss.as.controller.persistence.PersistanceResourceTestCase.testAclFilePermissions: <no details avaliable>

org.jboss.as.test.integration.domain.management.cli.CloneProfileTestCase.testProfile: <no details avaliable>

Linux Build 2205 outcome was FAILURE using a merge of 13c1aa3e8a7bdf63ddf74865dbc4c2ba20ddfbf2
Summary: Tests failed: 1 (1 new), passed: 3376, ignored: 63 Build time: 0:36:05
Build problems:
Failed tests detected
Failed tests
org.jboss.as.controller.persistence.PersistanceResourceTestCase.testPosixFilePermissions: <no details avaliable>

Core - Full Integration Build 1344 outcome was FAILURE using a merge of 13c1aa3e8a7bdf63ddf74865dbc4c2ba20ddfbf2
Summary: Tests failed: 109 (109 new), passed: 2729, ignored: 354 Build time: 0:48:45
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.clustering.single.singleton.SingletonServiceTestCase: org.jboss.as.test.clustering.single.web.SimpleWebTestCase: <no details avaliable>

org.jboss.as.test.clustering.single.singleton.SingletonServiceTestCase: org.jboss.as.test.clustering.single.registry.RegistryTestCase: <no details avaliable>

org.jboss.as.test.clustering.single.singleton.SingletonServiceTestCase: org.jboss.as.test.clustering.single.dispatcher.CommandDispatcherTestCase: <no details avaliable>

org.jboss.as.test.clustering.single.singleton.SingletonServiceTestCase: org.jboss.as.test.clustering.single.provider.ServiceProviderRegistrationTestCase: <no details avaliable>

org.jboss.as.test.clustering.single.singleton.SingletonServiceTestCase: <no details avaliable>

org.jboss.as.test.clustering.xsite.XSiteSimpleTestCase.testPutRelayedToBackups: <no details avaliable>

org.jboss.as.test.clustering.xsite.XSiteSimpleTestCase.testPutToBackupNotRelayed: <no details avaliable>

org.jboss.as.test.multinode.transaction.TransactionInvocationTestCase: org.jboss.as.test.multinode.ejb.timer.database.DatabaseTimerServiceMultiNodeExecutionDisabledTestCase: <no details avaliable>

org.jboss.as.test.multinode.transaction.TransactionInvocationTestCase: org.jboss.as.test.multinode.ejb.timer.database.DatabaseTimerServiceMultiNodeTestCase: <no details avaliable>

org.jboss.as.test.multinode.transaction.TransactionInvocationTestCase: org.jboss.as.test.multinode.remotecall.scoped.context.DynamicJNDIContextEJBInvocationTestCase: <no details avaliable>

org.jboss.as.test.multinode.transaction.TransactionInvocationTestCase: org.jboss.as.test.multinode.remotecall.RemoteLocalCallProfileTestCase: <no details avaliable>

##### there are 99 more failed tests, see build details

Windows Build 1734 is now running using a merge of 13c1aa3e8a7bdf63ddf74865dbc4c2ba20ddfbf2

Linux Build 2207 is now running using a merge of 13c1aa3e8a7bdf63ddf74865dbc4c2ba20ddfbf2

Core - Full Integration Build 1346 is now running using a merge of 13c1aa3e8a7bdf63ddf74865dbc4c2ba20ddfbf2

Windows Build 1734 outcome was FAILURE using a merge of 13c1aa3e8a7bdf63ddf74865dbc4c2ba20ddfbf2
Summary: Tests failed: 2, passed: 3375, ignored: 63 Build time: 0:33:11
Build problems:
Failed tests detected
Failed tests
org.jboss.as.controller.persistence.PersistanceResourceTestCase.testAclFilePermissions: <no details avaliable>

org.jboss.as.test.integration.domain.management.cli.CloneProfileTestCase.testProfile: <no details avaliable>

Linux Build 2207 outcome was FAILURE using a merge of 13c1aa3e8a7bdf63ddf74865dbc4c2ba20ddfbf2
Summary: Tests failed: 1, passed: 3376, ignored: 63 Build time: 0:36:25
Build problems:
Failed tests detected
Failed tests
org.jboss.as.controller.persistence.PersistanceResourceTestCase.testPosixFilePermissions: <no details avaliable>

Core - Full Integration Build 1346 outcome was FAILURE using a merge of 13c1aa3e8a7bdf63ddf74865dbc4c2ba20ddfbf2
Summary: Tests failed: 3 (3 new), passed: 2953, ignored: 354 Build time: 0:46:53
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.ejb.mdb.ejb2x.MDB20TopicTestCase.testEjb20TopicMDBs: <no details avaliable>

org.jboss.as.test.integration.ejb.remote.suspend.EjbRemoteSuspendTestCase.testSuspendedCallRejected: <no details avaliable>

org.jboss.as.test.integration.ejb.timerservice.mgmt.NonPersistentCalendarTimerManagementTestCase.testResourceExistence: <no details avaliable>

Core - Full Integration Build 1347 is now running using a merge of 3542a380f7b52454aad3a0560a074eeed65da045

Linux Build 2208 is now running using a merge of 3542a380f7b52454aad3a0560a074eeed65da045

Windows Build 1735 is now running using a merge of 3542a380f7b52454aad3a0560a074eeed65da045

Windows Build 1735 outcome was FAILURE using a merge of 42ad9ebfb7bfa040b78a29430537f010fe253764
Summary: Tests failed: 2, passed: 3375, ignored: 63 Build time: 0:33:26
Build problems:
Failed tests detected
Failed tests
org.jboss.as.controller.persistence.PersistanceResourceTestCase.testAclFilePermissions: <no details avaliable>

org.jboss.as.test.integration.domain.management.cli.CloneProfileTestCase.testProfile: <no details avaliable>

Linux Build 2208 outcome was FAILURE using a merge of 42ad9ebfb7bfa040b78a29430537f010fe253764
Summary: Tests failed: 1, passed: 3376, ignored: 63 Build time: 0:35:34
Build problems:
Failed tests detected
Failed tests
org.jboss.as.controller.persistence.PersistanceResourceTestCase.testPosixFilePermissions: <no details avaliable>

Core - Full Integration Build 1347 outcome was FAILURE using a merge of 42ad9ebfb7bfa040b78a29430537f010fe253764
Summary: Tests failed: 2 (2 new), passed: 2954, ignored: 354 Build time: 0:46:30
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.ejb.security.callerprincipal.GetCallerPrincipalTestCase.testStatelessLifecycle: <no details avaliable>

org.jboss.as.test.integration.ejb.client.descriptor.EJBClientDescriptorTestCase.testClientInvocationTimeout: <no details avaliable>

Linux Build 2210 is now running using a merge of 42ad9ebfb7bfa040b78a29430537f010fe253764

Windows Build 1737 is now running using a merge of 42ad9ebfb7bfa040b78a29430537f010fe253764

Core - Full Integration Build 1349 is now running using a merge of 42ad9ebfb7bfa040b78a29430537f010fe253764

Windows Build 1737 outcome was FAILURE using a merge of 42ad9ebfb7bfa040b78a29430537f010fe253764
Summary: Tests failed: 2, passed: 3375, ignored: 63 Build time: 0:33:39
Build problems:
Failed tests detected
Failed tests
org.jboss.as.controller.persistence.PersistanceResourceTestCase.testAclFilePermissions: <no details avaliable>

org.jboss.as.test.integration.domain.management.cli.CloneProfileTestCase.testProfile: <no details avaliable>

Linux Build 2210 outcome was FAILURE using a merge of 42ad9ebfb7bfa040b78a29430537f010fe253764
Summary: Tests failed: 1, passed: 3376, ignored: 63 Build time: 0:35:10
Build problems:
Failed tests detected
Failed tests
org.jboss.as.controller.persistence.PersistanceResourceTestCase.testPosixFilePermissions: <no details avaliable>

Core - Full Integration Build 1349 outcome was FAILURE using a merge of 42ad9ebfb7bfa040b78a29430537f010fe253764
Summary: Tests failed: 2 (2 new), passed: 2954, ignored: 354 Build time: 0:47:25
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.ejb.remote.distinctname.JarDeploymentDistinctNameTestCase.testRemoteSLSBInvocation: <no details avaliable>

org.jboss.as.test.integration.ejb.remote.distinctname.JarDeploymentDistinctNameTestCase.testRemoteSingletonInvocation: <no details avaliable>


Add Script Type Imports and Exports

Adds ability to export and import script types along with their scripting engine configurations and contexts. Export works with all deployments, but import only for classic deployments.
This PR should be merged in prior to the PR named "Update Full Config Export with new Imports and Exports" that updates the full config export/import since that PR will rely on the changes from this PR.

@phalestrivir conflicts, same as the others.

@vscheuber Merge conflict is resolved now


ISPN-9969 Configure statistics with the hotrod-client.properties

Statistics options can't be configured with properties. For spring-boot infinispan integration with actuator, this should be possible.
https://issues.jboss.org/browse/ISPN-9969
backport https://github.com/infinispan/infinispan/pull/6684

failure unrelated


Incorrect exceptions order in message if cause is not instance of expected type

Summary
Hi! Thanks for awesome library!
There is misleading exceptions order in case when actual exception has unexpected type.
Example
Exception expectedCause = new NullPointerException();
Exception actualCause = new IndexOutOfBoundsException();

assertThatThrownBy(() -> {
    throw new IllegalStateException(actualCause);
}).hasCause(expectedCause);

Actual result is:
java.lang.AssertionError:
Expecting a cause with type:
  <"java.lang.IndexOutOfBoundsException">
but type was:
  <"java.lang.NullPointerException">.

Java 8 specific ?

NO  : create Pull Request from the 2.x branch

we screwed up the param order :(
thanks for reporting this.


Improve Kubernetes logo, fixes #981

Improve the Kubernetes logo (the old one was too small and fuzzy).
The instructions on creating/updating logos are here:
doc/implementation.md
As an example, here's what we did:
cd app/assets/images/
cd project-logos-originals/
wget https://raw.githubusercontent.com/cncf/artwork/master/kubernetes/name_logo_color.png
mv name_logo_color.png Kubernetes.png
$EDITOR NOTES # note where we got this
cp Kubernetes.png ../project-logos
cd ../project-logos
mogrify -geometry x48 Kubernetes.png
optipng Kubernetes.png
identify Kubernetes.png
cd ../../..
$EDITOR app/views/static_pages/home.html.erb
Signed-off-by: David A. Wheeler<EMAIL_ADDRESS>

This makes the logo much wider, but as a result, it's much clearer.  I think we should pull this in.

This is a small tweak, and I've heard no objections.


UpdateLabelOverlapMeasures with ITK 5.3 changes

The existing computation for FalsePositiveError was renamed to FalseDiscoveryRate, and the computation for FPE corrected.
This is dependent on updating the ITK tag.
Closes #1679.

became part of #1715


Fix typo in header

Fix typo in We are going to update our guide message.

Wow I must be blind! Thanks!


update elliptic to 6.5.4

Coverage decreased (-0.1%) to 91.01% when pulling a2bdd35c4c75519c2feecdf95b0925b3ce9ea8c7 on libotony:dev into 65064b3a3f567efac4e989ae4805c081444eeed4 on vechain:master.


Drop Table

We need a class that can drop a table from a schema.

Do we have a schema table too look at what tables exist, or are we planning on having postgres shout at them if the table doesn't exist?

we can just guard it with a postgres query and if the table doesn't exist it would just be a noop.

check out pull request 16

Looks good. #16 merged.


Create Sampled Values tab in Subscription plugin

Discussion topic
To create the subscription functionality for sample values as well, we need an additional tab in the 'Subscription' plugin. The new tab should be next to the GOOSE tab. This issue contains the creation of the tab and showing the published SV messages and IEDs which can subscribe or are already subscribed. This will later be extended.

Show all published SV messages from all IEDs:
<SampledValueControl datSet="PhsMeas1" confRev="1" smvID="MU0101" multicast="true" smpRate="80" nofASDU="1" smpMod="SmpPerPeriod" name="MSVCB01">
	<IEDName apRef="E">IED</IEDName>
	<SmvOpts refreshTime="false" sampleSynchronized="true" sampleRate="false" dataSet="false" security="false" />
</SampledValueControl>

When selecting an IED, show all <extRef> with serviceType = SMV of all LNs.
<Inputs>
	<ExtRef iedName="SIP_Client" ldInst="VI3p1" lnClass="PTRC" lnInst="1" doName="Op" daName="general" serviceType="SMV" srcLDInst="VI3p1" srcLNClass="LLN0" srcCBName="Control_DataSet" pServT="SMV" desc="RxOp" intAddr="RxOp;/Op/general" pDO="Op" pDA="general" />
	<ExtRef iedName="SIP_Client" ldInst="VI3p1" lnClass="PTRC" lnInst="1" doName="Op" daName="q" serviceType="SMV" srcLDInst="VI3p1" srcLNClass="LLN0" srcCBName="Control_DataSet" pServT="SMV" desc="RxOp" intAddr="RxOp;/Op/q" pDO="Op" pDA="q" />
</Inputs>

@Flurb this is fixed right?  https://github.com/openscd/open-scd/pull/583


Warn / strip global regEx schemas?

https://stackoverflow.com/questions/2630418/javascript-regex-returning-true-then-false-then-true-etc
Type checks in simple-schema-validation.js line 18 and 23 use RegExp.prototype.test.
If you run the code below:
let r = /abc123/g
console.log(r.test("abc123")) // true
console.log(r.test("abc123")) // false
console.log(r.test("abc123")) // true
console.log(r.test("abc123")) // false
console.log(r.test("abc123")) // true
console.log(r.test("abc123")) // false

You can see that if you pass in a global regex to the schema, validation can alternate between true and false because javascript's global regexs are stateful

The Meteor SimpleSchema package is no longer maintained other than critical fixes to keep it running with each latest Meteor release. Closing non-critical issues in this repo. Anyone who cares about this may do one or more of the following:

Switch to the NPM package. Be sure to adjust for the breaking changes. There can be a lot of work involved in switching, but it is worth the effort.
If this issue still occurs in the NPM package, submit an issue there. Be sure to include a link to a reproduction repo or a PR that adds a failing test for the issue.
If you have more time than money, submit a pull request to resolve any issue labeled "help wanted" in the NPM package repo.
If you have more money than time, donate to help support development if you are able


Edit: Fix malformed comments from doc command with selection

Description
closes https://github.com/sourcegraph/cody/issues/2058
getDocCommandRange for the /doc command was returning the incorrect selection. It was overriding the end position rather than just adjusting the start position for python.
This meant that the edit command was treating this as an add (no selected code thus nothing to edit)
Before
https://github.com/sourcegraph/cody/assets/9516420/62121460-3ddf-47d1-9b41-f86d94f43e12
After
https://github.com/sourcegraph/cody/assets/9516420/23519065-fd6c-4969-b034-e0530330d328
Test plan

Highlight some code where there is not already a folding range
Use the "doc" command via the chat or right click menu
Check that the inserted documentation is correct

Follow up for a related scroll bug: https://github.com/sourcegraph/cody/pull/2296


Release v1.1.3

Golden test jobs in production fail as expected: https://hyp3-api.asf.alaska.edu/jobs?user_id=hyp3_testing&name=hyp3-testing-SJWUPey
Jobs in test now succeed: https://hyp3-test-api.asf.alaska.edu/jobs?user_id=hyp3_testing&name=hyp3-testing-SJWUPey
That's not proof that the geoid change didn't introduce some other unexpected change in the outputs, but I'm content to release these changes.

I loaded the outputs of S1_029928_IW3_20170330_20170411_VV_INT80_DFAE and S1_136231_IW2_20200604_20200616_VV_INT20_2F87 from test into QGIS and they still look like interferograms.


broken /stats output

Original author @ramaraochavali reviewers @mattklein123 @jmarantz @mrice32
https://github.com/envoyproxy/envoy/pull/3130 causes output like:
server.version: 11899839
server.watchdog_mega_miss: 0
server.watchdog_miss: 0
stats.overflow: 0
cluster.service1.upstream_cx_connect_ms: P0(nan,nan) P25(nan,nan) P50(nan,nan) P75(nan,nan) P90(nan,nan) P95(nan,nan) P99(nan,nan) P99.9(nan,nan) P100(nan,nan)
cluster.service1.upstream_cx_length_ms: P0(nan,nan) P25(nan,nan) P50(nan,nan) P75(nan,nan) P90(nan,nan) P95(nan,nan) P99(nan,nan) P99.9(nan,nan) P100(nan,nan)
cluster.service2.upstream_cx_connect_ms: P0(nan,nan) P25(nan,nan) P50(nan,nan) P75(nan,nan) P90(nan,nan) P95(nan,nan) P99(nan,nan) P99.9(nan,nan) P100(nan,nan)
cluster.service2.upstream_cx_length_ms: P0(nan,nan) P25(nan,nan) P50(nan,nan) P75(nan,nan) P90(nan,nan) P95(nan,nan) P99(nan,nan) P99.9(nan,nan) P100(nan,nan)
http.admin.downstream_cx_length_ms: P0(nan,nan) P25(nan,nan) P50(nan,nan) P75(nan,nan) P90(nan,nan) P95(nan,nan) P99(nan,nan) P99.9(nan,nan) P100(nan,nan)
http.admin.downstream_rq_time: P0(nan,nan) P25(nan,nan) P50(nan,nan) P75(nan,nan) P90(nan,nan) P95(nan,nan) P99(nan,nan) P99.9(nan,nan) P100(nan,nan)
http.ingress_http.downstream_cx_length_ms: P0(nan,nan) P25(nan,nan) P50(nan,nan) P75(nan,nan) P90(nan,nan) P95(nan,nan) P99(nan,nan) P99.9(nan,nan) P100(nan,nan)
http.ingress_http.downstream_rq_time: P0(nan,nan) P25(nan,nan) P50(nan,nan) P75(nan,nan) P90(nan,nan) P95(nan,nan) P99(nan,nan) P99.9(nan,nan) P100(nan,nan)
listener.<IP_ADDRESS>_80.downstream_cx_length_ms: P0(nan,nan) P25(nan,nan) P50(nan,nan) P75(nan,nan) P90(nan,nan) P95(nan,nan) P99(nan,nan) P99.9(nan,nan) P100(nan,nan)
listener.admin.downstream_cx_length_ms: P0(nan,nan) P25(nan,nan) P50(nan,nan) P75(nan,nan) P90(nan,nan) P95(nan,nan) P99(nan,nan) P99.9(nan,nan) P100(nan,nan)

The commit before that is fine https://github.com/envoyproxy/envoy/commit/fefb0d39ed54c6a43b652d7dd665c747537704ea

This is by design. It's new histogram stats.

It's not broken per se, but @ramaraochavali I wonder if we should render empty histograms differently for aesthetic reasons.  WDYT?

Do you have any ideas on how empty histograms should be displayed? Should we skip displaying them similar to how we skip sending to stats sink if they are not used?

That would work for me, or you could just put in a single string "no histogram data" in place of all the NaN entries.
If some of the entrires are NaN, should you omit those quantiles from the short display? I'm OK either way, but I actually don't understand, as a user, the distinction between NaN and 0 in this context.  Can you explain?

NaN indicates the histogram was not updated at all . 0 means histogram was updated and calculated quantile value is actually 0. If a value inserted in to histogram, you will not get Nan for any of the quantiles.

SG.  Then I recommend special-casing the all-entries-NaN case and just indicate the histogram is empty with a short string.  Only issue is whether that might break scripts that want to to scrape the histogram data.  So another option is omit those histograms completely, which would also be OK with  me.

Do you think counters and gauges should also be printed (in admin as well json) only if they are used?

Personally, I find printing all stats in /stats to be a very useful debugging tool and I would prefer that they not be removed. I could see an argument for removing them from the JSON output which is generally more machine consumption. I could also see an argument for having a query param arg for excluding unused stats? Thoughts? cc @mrice32 @jmarantz

I agree: there is information in the existence of an empty histogram, so eliding the entry entirely obscures that information.
Can we just print "empty histogram" or similar, in our stats output, instead of a bunch of NaNs when we are outputting one of those?

also: a query-param to exclude unused stats would be fine with me.

@mattklein123 this bug is closed now; should a new one be opened, or this one re-opened?

I think printing gauges and counters in the JSON would be useful, and +1 to the idea of a query param to eliminate unused stats.  I also agree that "empty histogram" or similar would be better than all the NaNs (often seeing a bunch of NaNs in an output makes me think that something is broken :) ).

Reopening. @ramaraochavali can you track further changes as part of this issue? What everyone is proposing here SGTM. I mainly just want all stats to be output when I hit the non-JSON version of /stats. That's all I really care about. :)

Ok. I will make the changes. So here is the summary of changes

/stats interface would list all stats irrespective of whether they have been used or not. If a histogram is not used it will display "No recorded values"
JSON output will only output used counters and gauges.
/stats?usedonly=true will print only used stats.

@ramaraochavali IMO I would probably have the default of both non-JSON and JSON be to output all stats for consistency, and then document the usedonly query param which can be used for both? IMO it's better to be consistent here but I don't feel that strongly about it. cc @mrice32 @jmarantz

@mattklein123 ok. I will make change accordingly.


Useradd Doesn't Create Default Directory Structure

/etc/xdg/user-dirs.defaults : contains info on default directory structure for /home when calling useradd, but this does not get created. Does it requires GUI login, or ...?

xdg is a short for X Desktop Group. They are a group of people creating standards for interoperability between different Linux desktop managers (KDE, Gnome, Xfce, etc.). Therefore exerything with xdg in name is GUI related.
For the default content of a standard shell account home folder look into /etc/skel:
total 24
drwxr-xr-x   3 root root 4096 Apr 22 01:55 ./
drwxr-xr-x 123 root root 4096 Jun 23 17:25 ../
-rw-r--r--   1 root root  127 Apr 22 01:55 .bash_logout
-rw-r--r--   1 root root  204 Apr 22 01:55 .bash_profile
-rw-r--r--   1 root root  551 Apr 22 01:55 .bashrc
drwx------   2 root root 4096 Aug 13  2018 .ssh/```

Took a look there, but on my test VMs I did not see an entry for the creation of directories such as: Desktop, Photos, etc. Any suggestions?

Those home directories are not part of the standard UNIX/Linux account setup.
Either way this seems to answer your question: https://wiki.archlinux.org/index.php/XDG_user_directories

So we're back where we started...

I'm not sure what you mean. Have you checked the URL which I pasted?
Something like this shouls do what you want:
if [[ ! -z $(which xdg-user-dirs-update) ]]
then
  su - ${username} -c "xdg-user-dirs-update"
  ### if you want to use sudo instead of su:
  # sudo -u ${username} -i xdg-user-dirs-update
fi

My initial link pointed to: /etc/xdg/user-dirs.defaults, so I was in the ball park; your link got me on base. Thanks for the suggestion!

username='sjobs'

create_default_dirs () {

  if [[ -n $(command -v xdg-user-dirs-update) ]]
  then
  su ${username} -c xdg-user-dirs-update
  ### if you want to use sudo instead of su:
  ###printf "%s" "$passy" |sudo -u $username -i xdg-user-dirs-update
  fi
}

create_default_dirs

Fixes issue. Need to test more thoroughly.


Configuration for Tailwind Integration

Summary of Changes
This PR adds configuration for Tailwind CSS
Related Issue
Fixes first task of #179
Checklist

[x] I have read and followed the project's contribution guidelines, including code style and commit message conventions.
[x] My code is well-documented, and I've updated relevant documentation.
[x] I have added or updated test cases to ensure the code's functionality.
[x] I have tested these changes on my local environment.
[x] All tests pass, and there are no new linting errors.
[x] I have reviewed and proofread my code and the changes.
[x] The branch is up-to-date with the base branch.

Reviewer(s)
@Abhijay007

Sure @Abhijay007, I will look into this.

Hi @Abhijay007, I have made changes to the heading styling. However, I think I will need to convert the whole custom.css into tailwind, to fix the styling. I am currently doing these changes in a different CSS file. I have changed the heading styling into tailwind in the above commit.

The code changes LGTM. Now, you can work on converting one of the components and create a separate PR for that. Once that's done, we will merge both of these PRs.

Okay Sure!

closing this as we already have version of it here : https://github.com/uptane/uptane.github.io/pull/185


FCMRebooted error on iOS 17.2 with Delphi 12

I'm trying to run the FCMREbooted demo on iOS and it doesn't work. I have created an application from scratch, following the steps, and it still gives me the same error, I put them in case it helps:
[PAClient Error] Error: E0776 2024-02-16 09:36:05.834 xcodebuild[21138:999430] [MT] IDEDistribution: -[IDEDistributionLogging _createLoggingBundleAtPath:]: Created bundle at path "/var/folders/q6/lhwpt4n1537fhr9ckp80h4kr0000gn/T/FCMRebooted_2024-02-16_09-36-05.833.xcdistributionlogs".
[PAClient Error] Error: E0776 error: exportArchive: No Team Found in Archive
[PAClient Error] Error: E0776 Error Domain=IDEDistributionAnalyzeArchiveStepErrorDomain Code=0 "No Team Found in Archive" UserInfo={NSLocalizedDescription=No Team Found in Archive, NSLocalizedRecoverySuggestion=Use the Signing & Capabilities editor to assign a team to the targets and build a new archive.}
[PAClient Error] Error: E0776 ** EXPORT FAILED **
Failed

When I run the Firebase Project Doctor utility, I get an error when checking the GoogleService-Info.plist, but it is added to the project and In the Version Info section, everything is filled out correctly, CFBundleIdentifier, CFBundleName...
. I don't know where the error is.
I also leave the log generated from Firebase Project Doctor:
Swift Compatibility check:
Folders check PASSED for: C:\Users\Administrador\Documents\Embarcadero\Studio\SDKs\iPhoneOS17.0.sdk
Linker Options check:
Found linker option for "Cfg_2" config - Value: -ObjC -rpath /usr/lib/swift
Linker option should be applied to "All configurations"
Google Services check:
Failed to parse GoogleService-Info.plist
Push Entitlements check:
The provisioning profile being used for this project appears to have the Push Notification entitlement
Frameworks Search Path check:
Framework Search Paths PASSED

Thank you

For the original error, apparently there can be a number of causes. Some things to check for: Make sure the provisioning profile is using the correct certificate. Check which certificates are installed on the Mac by using the Keychain Access app to make sure there's none that might "confuse" PAServer by selecting the wrong one when it attempts to codesign the application. I have tool called Mosco, that can also help identify these kinds of problems - use the View Certs and Profiles menu item to display which certificates and profiles are installed/downloaded.
For the error you're receiving when deploying/running in development mode, are you deploying to a real device? The error apparently can also be affected by misconfiguration of the provisioning profile

You are right, it was a certificate problem, but it is strange because that same certificate was working without problems for me with another app, which was receiving push notifications in the old way. I don't know, I revoked the certificate, I regenerated it and everything worked fine.
Sorry for the inconvenience, and thank you very much for your help.
But I have a question, with this version of Firebase iOS sdk, on iOS devices, can't I receive an image in the notification?
Many thanks for everything.
All the best.

But I have a question, with this version of Firebase iOS sdk, on iOS devices, can't I receive an image in the notification?

I'm working on that, however moving FCM iOS support forward (to newer SDKs) is currently at a standstill due to a linker bug in Delphi, and I'm not inclined to spend any more time on it because it may be completely wasted due to potential restrictions on apps that use older SDKs.

And another thing that I have detected on Android devices, if you set the FCM.ShowBannerIfForeground property to true, if a notification is sent, of type no data, and the app is running in the foreground, it crashes.

Please file a separate issue for this.

Yes of course.
I open a new thread.
Thank you so much.


chore(main): release 0.2.4

:robot: I have created a release beep boop
0.2.4 (2024-11-10)
Bug Fixes

env环境变量无法识别问题仍存在,现在还原为之前方式 (1c28c3c)
调试使用Github的环境变量 (eac9848)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v0.2.4
:sunflower:


Feat: Stack Changes

Implements a custom linker script for the memory mappings.
Currently we place the changes are:

Core0 (SCRATCH_X) stack after Core1 (SCRATCH_Y)
Core0 stack size to be alloc be 6KB, Core1 stack size to be alloc 2KB

pls make sure to test that audio works w/ this pr- if we increase stack size, it might eat into the heap space used for the audio buffer

pls make sure to test that audio works w/ this pr- if we increase stack size, it might eat into the heap space used for the audio buffer

Tested a few games today with audio and it appears to work as expected


setup user: cannot set any additional groups in a rootless container

Hi, great pet container, I am using it on Silverblue 29 beta and CentOS (sudo mode) which I try to treat immutable.
On an updated clean 29 install I get the following error:
./fedora-toolbox -v enter
unable to start container "fedora-toolbox-gary:29": container create failed: container_linux.go:336: starting container process caused "setup user: cannot set any additional groups in a rootless container"
: internal libpod error
./fedora-toolbox: failed to start container fedora-toolbox-gary:29``
The culprit seems to be "--group-add wheel" under the podman create.

Further to the above the "--uidmap" lines seem to cause the following errors:
exec failed: container_linux.go:336: starting container process caused "process_linux.go:90: adding pid 8258 to cgroups caused "failed to write 8258 to cgroup.procs: write<EMAIL_ADDRESS>permission denied""
podman version 0.10.1

Further to the above the "--uidmap" lines seem to cause the following errors:
exec failed: container_linux.go:336: starting container process caused
"process_linux.go:90: adding pid 8258 to cgroups caused "failed to write 8258 to cgroup.procs:
write<EMAIL_ADDRESS>permission denied""

Yes, that's due to runc (https://github.com/opencontainers/runc/pull/1862). See this comment:
https://github.com/opencontainers/runc/pull/1862#issuecomment-417784925
Here's an update targeted at Fedora 29 to address this:
https://bodhi.fedoraproject.org/updates/FEDORA-2018-e77cc54309
Unfortunately, since we are frozen for the the final Fedora 29 release, it will only enter the Silverblue 29 image as a zero-day update. Until then, you can try:
$ rpm-ostree override replace /path/to/runc-1.0.0-56.dev.git78ef28e.fc29.rpm

I am using it on Silverblue 29 beta and CentOS (sudo mode) which I try to
treat inimitable.
On an updated clean 29 install I get the following error:
./fedora-toolbox -v enter
unable to start container "fedora-toolbox-gary:29": container create failed:
container_linux.go:336: starting container process caused "setup user: cannot
set any additional groups in a rootless container"
: internal libpod error
./fedora-toolbox: failed to start container fedora-toolbox-gary:29``
The culprit seems to be "--group-add wheel" under the podman create.

I haven't seen this before. So far I have been hacking on Silverblue 28. I wonder if there's something off in Fedora 29.
Does it continue to happen after pulling in the above runc PR? What version of podman do you have? What did you mean by "sudo mode"?

Hi,the updated runc solved both of the errors.  Under CentOS I use the "--sudo --release 29" arguments as rootless podman is not working there at the moment.  I also remove the uid mappings as they fail on CentOS but as most of my builds are single user this does not cause me any issues.
Since this is solved for Silverblue 29 that is great and I will derive my own CentOS script which is not a target platform anyway.  Thanks for the great work, I am really enjoying Silverblue.

That's great to hear! :)
Rootless podman and buildah are still very new, so it is probably a matter of getting newer versions of those into RHEL and eventually CentOS.
The --sudo flag was initially meant for debugging rootless bugs, but I am glad that you found some real use for it. I know that Fedora CoreOS is also interested in a rootful toolbox.
Anyway, thanks for getting in touch.


Added a warning to HTML

Added a warning to try to prevent people from exploiting the system while we work on fixing it

Not sure how much this will deter hackers but PR looks good to me.


Autofix API

I've implemented an autofix API for Nuclide diagnostics and I would like to settle on a similar API for the linter package. I know it may not be on the roadmap for you to implement but if we agreed on an API for the future, projects like linter-eslint could at least take advantage of this new functionality in Nuclide without using an unsanctioned API extension.
The API I came up with simply adds an optional fix field to the messages, of the type:
{
  oldRange: Range,
  newText: string,
  oldText?: string,
}

oldText is not required, but can be included to sanity-check the fix. How does this sound? If you like it, I will add support for it to Nuclide's linter adapter and put up a pull request with linter-eslint.
See also #418. I thought it would be better to open a new issue because that's pretty old and I don't have the ability to reopen it.

I'll leave it to @steelbrain to comment on the API suggestion itself, but I was curious how many linter programs you see that could support this data in the first place? Of the few that even provide a "fix" option that I know of, it looks like eslint is the only one that provides data back and doesn't only support running with a flag to fix on it's own.

@Arcanemagus libclang gives this information. So presumably that's C, C++, Objective-C, and Objective-C++. As well as Swift due to it's LLVM ties. Add Rust on top of that. Seems like this is a good idea.
I'll also leave further API planning to @steelbrain.

Cool! Glad to hear it's more than just eslint as that's really nice information to have.

@nmote I like the concept, but I would suggest we do it in a backward compatible manner, for example, our current message object looks like this
{
  type: 'Error',
  text: 'Some Error',
  range: [[line - 1, col - 1], [line - 1, col]]
}

We could add two new fields replaceRange and replaceText so it would become
{
  type: 'Error',
  text: 'Some Error',
  range: [[line - 1, col - 1], [line - 1, col]],
  replaceRange: [[line -1, 0], [line -1 , col]],
  replaceText: 'Your line has been replaced'
}

I think it has a good name that we can guess it's purpose from and is backward compatible, what do you think?

After some discussion with @Arcanemagus, I am down with having a fix attribute for message. but a question I have in mind @nmote is, when we already have a range, why would we need oldText when we already have a range?

Just like trace, I'd prefer this was a single element myself.
@nmote Do you think a linter provider would ever need to specify multiple ranges to be replaced for a single message? If so how about this:
{
  ...
  fix: [{range: Range, text: String}, {range ...}, ...]
}

Or would that just complicate things with no linter provider ever utilizing it?

@steelbrain I'm fine with either flattening them or having a separate fix object, although I do slightly prefer the fix object. It's more obvious that you need to include all of the fix information or none if it's encapsulated into an object -- otherwise you have to document that if you provide replaceRange you must also provide replaceText, and it also presents fewer top-level fields to people who are just trying to get off the ground with their first linter.
The oldText can be used before applying the fix to sanity-check that it is being applied in the right place. Obviously that doesn't work if the oldRange is of zero length and therefore oldText would be empty, but in some cases it can provide another layer of safety. Perhaps I'm paranoid but it seems like a good idea to have as many checks as possible before changing people's code. But if you think that's overkill I'm fine leaving it off.
@Arcanemagus I thought about the possibility of multiple fixes, and perhaps it would be useful. However multiple fixes could always be consolidated into one larger fix, although then it would be more difficult to apply in the presence of unsaved changes (for example, if the user typed in the area between the two fixes). I understand the desire to future-proof but perhaps it's better to just have the single fix object and consider allowing arrays as well if the need arises?

Makes sense to me, we can always build it supporting arrays, and if we are fed an object just wrap it in an array.

@nmote I like your idea of having many checks before the code is replaced.
I had some time to think about this today, and the most important question I have in mind for this is the UI. Atom is basically a text editor and packages like linter and nuclide make it an IDE. Therefore we should try to take the IDE approaches instead of text editor approaches whenever possible.
I have two decent ways in mind to handle the UI of fixes in linter or nuclide
1 - We add another line to the tooltip, that has a button on it and pressing that button fixes the current error. This includes mouse interaction, if we want to make it friendly for people who don't use much mouse, we'll have to add another command which they can bind to a key and press that key.
This is the text editor approach and a really bad thing for UX as the user will have to remember the key binding for each package that they use. We also fear running out of keys this way. It is also unfriendly for users who don't touch their configs (majority of them don't). We can fix it here in the linter package and when we run into a similar issue in another package we'll have to re-invent the wheel there too.
2 - We create a base package, that allows packages like linter to hook into it. This package will host an  options menu that will be triggered by ctrl-space, It will have options that it's providers will add via API. Each time it's invoked, it's providers will be invoked based on the current scope and will tell it if they need to show an item in the list..
This is the IDE approach. Users won't have to touch their mouses, they won't have to configure any kind-of key mapping, and they'll get features from multiple packages including linter, all in one place. This will overall increase their productivity.
We are trying to make Atom an IDE and here's how an IDE handles this problem

I have run into the need of such a package in other packages I'm maintaining as well, therefore I am strongly in favor of option 2, I already have that package in the works and will be releasing it soon.
Which option would you prefer?
Other than that, a minor nit I have in mind is that we could rename oldRange in the fix obj to range so it's structure would be this
{
  range: Range,
  newText: string,
  oldText?: string,
}

I'll leave the UI up to you, but I'd like to point out that ctrl+space is already in use to manually activate autocomplete-plus: https://github.com/atom/autocomplete-plus/blob/master/keymaps/autocomplete-plus.cson
In Nuclide I've added a little Fix button to the popups. That's fine for now but I think you're right that the UX needs additional thought. One concern with the option two that you suggest is that it doesn't seem like it will be obvious that you have these options if you are just looking at the error. Unless I'm missing something you would still have to know the magic shortcut to get this menu.
Your screenshot raises an interesting question: What if there are multiple potential ways to fix a problem? How should we express that in the API? Currently providers like ESLint provide only a single fix, but I'm interested in getting fix information from Flow, for example, which has the potential to be more complex. However, what we have settled on will work for the majority of cases so I am in favor of moving forward with it and solving these problems later.
I am fine with the naming change from oldRange to range.
Since we seem to have reached a consensus I'll move forward with getting this into linter-eslint.

@nmote ctrl-space was actually a typo of alt-enter. The concept I have in mind is that linter itself will register as a provider to that package and will provide known fixes as a Fix text using linter option. The providers won't have to worry about it, they'll just have to provide a fix object.
This will only work for packages that need basic text replacement, like you said. Linter won't be able to satisfy packages that need advance replacements. Those packages will have to directly register themselves as providers to that package and list all available options.
That's fair IMO, what is your opinion?

Ah I see. That seems like a good first step for sure but at some point I think it would be worthwhile to allow providers to suggest different fixes without forcing each one to write the boilerplate to integrate with this menu.
At the risk of introducing feature creep, an API that satisfies all of the constraints we have discussed might look like this:
{
  text: string,
  filePath: string,
  ...
  fix: Array<{
    displayText: string,
    edits: Array<{
      range: Range,
      newText: string,
      oldText?: string,
    }>,
  }>,
}

So, the top-level fix array provides different options -- the user can select one of them. The edits array provides all of the edits that need to be applied to make the fix. The displayText property is shown to the user with that suggestion.
However I still would like to move forward with the simple API since this is added complexity that we don't yet have a concrete use for.

Agreed, lets implement the simpler API for now.
About the complicated API you suggested, I don't think that's a good idea for a number of reasons

This will complicate the diffing and parsing of linter messages
It will be an overkill because the number of packages that would use such advance features could be counted on my two fingers
The patch provided by provider will invalidate as soon as the user does anything within those ranges
It will create a lot of new objects that might never be used on each lint run, which for heavier use cases will make Atom a memory hog and GC will kick in more often causing loss of FPS

I have put together an example API of packages who would like an intentions entry, you can find it at https://gist.github.com/steelbrain/98feb0f293e1cc888343
That being said, I want to Thank you for bringing this idea to our attention, I'm sure a lot of people will enjoy this feature

(I know I'm pretty much spamming about block decorations in this project's issues today but) they would be pretty useful if we able to displayed the diff of oldText and newText in a block above (or below) the line that needs fixing with a button that would trigger the fixing action.

@varemenos This will probably be brought into here through https://github.com/steelbrain/intentions and https://github.com/steelbrain/declarations.

@Arcanemagus I think just intentions. declarations is more along the lines of a hyperclick competitor.

@kepler0 Good point, I just knew he had been working on related stuff in those packages :stuck_out_tongue:.

Actually both of you are correct, the intentions package has two types of API, one is highlight API that is used by declarations to provide a base jump-to-click API, other is menu API that is going to be used by linter to provide Fix linter issue menu item

Updated the Wiki page with what I believe was the current finalized API, if I didn't grab the right one please fix it!

Elm's compiler provides some warnings (top-level functions missing types, unused imports (see https://github.com/mybuddymichael/linter-elm-make/issues/22)) that could easily be parsed and turned in to fixes. This feature would make it pretty easy to add support for that, so I'm excited by this discussion.

@jergason There is nothing preventing you from implementing it in the linter provider package, and then when it is implemented here it will suddenly start working :wink.

I've also implemented this in Nuclide so you could use that for now if you'd like to try out autofix.

Btw, @nmote is the documentation in the Wiki aligned with what you implemented there? Based it off the discussion here and what was done in linter-eslint.

@Arcanemagus Yep, looks good to me.


Configuration does not work for blockBytes == beatBytes

Hi, current configuration fails when I set blockBytes equal to beatBytes. I believe that this can be solved by making the following modifications, but not sure whether it follows the convention of project. If it looks good, I can start a pull request.

Parameters.scala Line 191-192

  val innerBeatBits = offsetBits - log2Ceil(inner.manager.beatBytes)
  val outerBeatBits = offsetBits - log2Ceil(outer.manager.beatBytes)

to
  val innerBeatBits = (offsetBits - log2Ceil(inner.manager.beatBytes)) max 1
  val outerBeatBits = (offsetBits - log2Ceil(outer.manager.beatBytes)) max 1

SourceC.scala Line 68

  val last = beat.andR

to
  val last = beat === (params.cache.blockBeats - 1).U

BankedStore.scala Line 126

    val a = Cat(b.bits.way, b.bits.set, b.bits.beat)

to
    val a = if (params.cache.blockBytes == beatBytes) Cat(b.bits.way, b.bits.set) else Cat(b.bits.way, b.bits.set, b.bits.beat)

Thanks!

Thanks! These changes look reasonable, and a PR would be appreciated.


You can't have commas in search term

Describe the bug
If you have a comma in your search term you get An unknown error occurred. in the UI.
To Reproduce

Quickstart v0.8.19.
Type something, something in the search bar and hit enter.

Expected behavior
I expect the search to work.
Screenshots

Desktop (please complete the following information):

OS: mac
Browser: Chrome
Version: Version 96.0.4664.110 (Official Build) (x86_64)

Additional context
GMS container logs:
07:32:24.033 [ForkJoinPool.commonPool-worker-1] ERROR c.l.m.s.e.query.ESSearchDAO:61 - Search query failed
org.elasticsearch.ElasticsearchStatusException: Elasticsearch exception [type=search_phase_execution_exception, reason=all shards failed]
	at org.elasticsearch.rest.BytesRestResponse.errorFromXContent(BytesRestResponse.java:187)
	at org.elasticsearch.client.RestHighLevelClient.parseEntity(RestHighLevelClient.java:1892)
	at org.elasticsearch.client.RestHighLevelClient.parseResponseException(RestHighLevelClient.java:1869)
	at org.elasticsearch.client.RestHighLevelClient.internalPerformRequest(RestHighLevelClient.java:1626)
	at org.elasticsearch.client.RestHighLevelClient.performRequest(RestHighLevelClient.java:1583)
	at org.elasticsearch.client.RestHighLevelClient.performRequestAndParseEntity(RestHighLevelClient.java:1553)
	at org.elasticsearch.client.RestHighLevelClient.search(RestHighLevelClient.java:1069)
	at com.linkedin.metadata.search.elasticsearch.query.ESSearchDAO.executeAndExtract(ESSearchDAO.java:57)
	at com.linkedin.metadata.search.elasticsearch.query.ESSearchDAO.search(ESSearchDAO.java:89)
	at com.linkedin.metadata.search.elasticsearch.ElasticSearchService.search(ElasticSearchService.java:66)
	at com.linkedin.metadata.search.cache.EntitySearchServiceCache.lambda$getSearcher$0(EntitySearchServiceCache.java:24)
	at com.linkedin.metadata.search.cache.CacheableSearcher.getBatch(CacheableSearcher.java:82)
	at com.linkedin.metadata.search.cache.CacheableSearcher.getSearchResults(CacheableSearcher.java:47)
	at com.linkedin.metadata.search.aggregator.AllEntitiesSearchAggregator.lambda$getSearchResultsForEachEntity$2(AllEntitiesSearchAggregator.java:148)
	at com.linkedin.metadata.utils.ConcurrencyUtils.lambda$null$0(ConcurrencyUtils.java:21)
	at java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1604)
	at java.util.concurrent.CompletableFuture$AsyncSupply.exec(CompletableFuture.java:1596)
	at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289)
	at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1056)
	at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1692)
	at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:175)
	Suppressed: org.elasticsearch.client.ResponseException: method [POST], host [http://elasticsearch:9200], URI [/corpuserindex_v2/_search?typed_keys=true&max_concurrent_shard_requests=5&ignore_unavailable=false&expand_wildcards=open&allow_no_indices=true&ignore_throttled=true&search_type=query_then_fetch&batched_reduce_size=512&ccs_minimize_roundtrips=true], status line [HTTP/1.1 400 Bad Request]
{"error":{"root_cause":[{"type":"query_shard_exception","reason":"Failed to parse query [[something,  something]]","index_uuid":"DB2XSrTFS32-siTGTAbHaQ","index":"corpuserindex_v2"}],"type":"search_phase_execution_exception","reason":"all shards failed","phase":"query","grouped":true,"failed_shards":[{"shard":0,"index":"corpuserindex_v2","node":"ff0VRcDfTY-Nkot3gazphg","reason":{"type":"query_shard_exception","reason":"Failed to parse query [[something,  something]]","index_uuid":"DB2XSrTFS32-siTGTAbHaQ","index":"corpuserindex_v2","caused_by":{"type":"parse_exception","reason":"Cannot parse '[something,  something]': Encountered \" <RANGE_GOOP> \"something \"\" at line 1, column 13.\nWas expecting:\n    \"TO\" ...\n    ","caused_by":{"type":"parse_exception","reason":"Encountered \" <RANGE_GOOP> \"something \"\" at line 1, column 13.\nWas expecting:\n    \"TO\" ...\n    "}}}}]},"status":400}
		at ```

Thanks for reporting, @karoliskascenas! We have a smaller team on hand during the holidays, but we'll take a look into this ASAP.

We also see similar behavior with -. It may be related.

Hi. We have fixed the issue with this PR! https://github.com/datahub-project/datahub/pull/4570 Will be included in next release


Customer search is way too slow

Not sure if the standard find on the Customer list view is using Quick Find, but it's way too slow.

Not seeing the performance issue. Yes, the standard find is a QuickFind.

Try it on the production server. :-)

Yikes. I see what you mean.

Seems like it just needed an index. Quite performant now.


Update .travis.yml

enable codecov

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@6da9b0e). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff            @@
##             master      #2   +/-   ##
========================================
  Coverage          ?   94.8%
========================================
  Files             ?       2
  Lines             ?     250
  Branches          ?       0
========================================
  Hits              ?     237
  Misses            ?      13
  Partials          ?       0

Continue to review full report at Codecov.

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


jasmin: init at 2.4

Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @

I tried it. The hello world example here can be assembled and run like:
> ./result/bin/jasmin HelloWorld.jasmin
Generated: HelloWorld.class
> java -cp . HelloWorld
Hello World!

I think it'd be cool, to have a test that tests this, using the test attribute: https://nixos.org/nixpkgs/manual/#sec-standard-meta-attributes

About the fork: I'm not sure. It says "a specialized version of jasmin which is used as a back end for the Soot framework" and the original project does not link to it, so I'm a bit hesitant. Maybe we can merge this and decide later whether to upgrade?
About test: cool, I didn't know about that. Is it new? I'll add it shortly.

Also most distros do not package that fork: https://repology.org/project/jasmin/versions

Added the test


Fixed Dan's Soaked Cigs Typo

About the PR

One of the soaked cigs (id: CigaretteDermaline) has dylovene in it, just like another cig (id: CigaretteDylovene) which also has dylovene. I assume it was intended for that to have derma.
Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog

:cl:

fix: Whoopsie - Dan's Soaked Cigs finally hired some Quality Control. They've resolved a small reagent solution in some of their swisher sweets.

in the future you will want to fork your master branch instead of committing straight to your master branch


#31 As a User - I would like to see a relationship diagram (Sankey Diagrams) between perpetrators and victims

Sankey is not really good for relationship diagram. It displays proportionally to the flow quantity.
It's good for showing how money or energy is spent.
Also, as I have understood, this site is for wide audience so I wouldn't go into charts unless they are really really simple.
Best would be to just show statements with simple data backing them up.

I imagine Sankey offering a good way to show the biggest perpetrators and victims! Though agree it may complicate matters in terms of simplicity. I will wait for the first iteration, and we can discuss then.


Support for method overloading when using typed arguments

This issue was originally filed by<EMAIL_ADDRESS>
I saw mention in documentation that Dart does not support method overloading because it is a dynamic language. However, Dart does support optional type annotations, which, as far as I can tell, opens the door slightly for the possibility of having method overloading when using typed argument values. I am proposing support for this behavior.
Currently when a programmer wants to support multiple types in a dynamic language using a single method, they will perform the instance checks manually as follows:
  class Displayer {
    void display(element) {
      if (element is String) { print(element); }
      else if (element is Image) { /* display image on screen */ }
      else { throw "Invalid argument"; }
    }
  }
This is cumbersome to the programmer and not easily translated in documentation-- not to mention easy to get wrong. Given support for optional types, I think we should be able to offload this dispatch to the compiler, which would make it much easier to write such methods.
For example, with overloading we could simplify the above snippet to:
  class Displayer {
    void display(String text) { print(text); }
    void display(Image image) { /* display image on screen */ }
  }
I am no compiler expert, but it seems plausible to me that given type annotations, a compiler could easily handle dispatching to the correct method at runtime. In addition, when cross-compiling to JS, the compiler could insert the manual checks as per the initial snippet above so that it would be equivalent to existing code that we see today. In fact, in the worst case, the Dart compiler could just always perform this translation directly in the method when it sees such an overload. That way there would not even be a need to modify the method dispatch rules in the VM-- it would simply be a completely transparent type check / dispatch that the user no longer has to do manually.
A couple of obvious restrictions on the functionality would be:

Return types for overloaded methods would have to match. This is no different from other languages with overloading support, so nothing new here.
All types would have to be declared on each variant when declaring an overloaded method. The compiler could easily check for this. I don't think users would be surprised by such an error if they ran into it-- seems intuitive enough.

All in all, this would be a great way to display the power of optional typing in the dynamic language world. It simplifies an idiom that is commonly used in dyn langs to circumvent the lack of overloading, and it would save developers from having to use separate method names depending on the input types. What do you think?

Any proposal for allowing operator type based overloading at least?

Now that Dart2.0 is statically typed can we have method/constructor overloading when using  multiple types?
class Consumer<T> {
  final List<T> models;

  Consumer(T model, Function<T> builder): /**/;

  Consumer(T model0, T model1, BiFunction<T, T> builder): /**/;
}

I have fail into example with using of Size class from \pkg\sky_engine\lib\ui\geometry.dart (dart.ui). There is one operator minus:
class Size extends OffsetBase {
...
  OffsetBase operator -(OffsetBase other) {
    if (other is Size)
      return Offset(width - other.width, height - other.height);
    if (other is Offset)
      return Size(width - other.dx, height - other.dy);
    throw ArgumentError(other);
  }
...
}

and I need to cast back from OffsetBase to Offset or Size after call this operator
Offset imageOffset = ((widget.imageWidgetSize - renderedImageSize) as Offset) / 2
instead of possible
class Size extends OffsetBase {
...
  Offset operator -(Size other) {
    return Offset(width - other.width, height - other.height);
  }

  Size operator -(Offset other) {
    return Size(width - other.dx, height - other.dy);
  }
...
}

and having clear expression like
Offset imageOffset = (widget.imageWidgetSize - renderedImageSize) / 2;


Name of Icon does not appear in bottom left corner when clicked

@mahirannama  can you provide some screenshots of the icon please

Don’t worry about this issue for now. It can wait until we deploy to prod
Sent from Yahoo Mail for iPhone
On Friday, October 20, 2023, 18:38, Harshank @.***> wrote:
@mahirannama can you provide some screenshots of the icon please
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

No details were provided, closed for now.


Fix #586: Change "loadUser" to "loadUser()" in docs.

Referencing: #586

Thanks @Flaque and @mahboob-awan!


Glossary UI: Updating a reference doesn't work

Affected module
UI
Describe the bug
Updating reference of a glossary term does not trigger any API request but shows the updated value in the UI until the refresh of the page.
To Reproduce
Update reference of any term.
Expected behavior
UI makes an API call to the backend to update the reference.

Already fixed


Undetected Chrome driver

I have downloaded the Zip extracted it...
installed all requirements..
then ran py and got this error : import undetected_chromedriver as uc

It's always a good idea to post a screenshot. Helps me to understand what os, terminal, python version, errors etc...


@Listeners(TextReport.class) does not show any logging on Selenide version 3.8 using testng

@Listeners(TextReport.class) does not show any logging with TestNG on Selenide version 3.8
I updated Selenide from version 3.7 to version 3.8 and ran a test and i did not see any logging. Did the way to activate the report logging changed?
Thanks,
regards,
Sherwin

@thasherwin Yes, it was changed in Selenide 3.6:

now the report will only be generated for classes annotated with @Report.

Are you sure you started experiencing this problem exactly in 3.8 vs 3.7 version?

I tried going back to version 3.7 and it worked but when i went to version 3.8 i did not work.. I was using only the listener annotation;
@Listeners(TextReport.class)
I was not aware that i should use the report annotation.
I tried to use only the report annotation but that did not work.
It is working now for me on version 3.8 when using both annotations;
@Report
@Listeners(TextReport.class)

Not sure whether this is how it suppose to work

I dont see this porblem anymore. I am using selenide 3.9.1 and everything is fine.. So i will close this issue

For the record: in Selenide 6.7.0, annotation @Report was deprecated.
Now text report will be generated for all classes marked with @Listeners({TextReport.class} and their subclasses.


Crash when segue to UITableViewController

On xCode 6.3.1 and iOS 8, when I segue from a rear menu cell via "SWRevealViewControllerSeguePushController" to a UITableViewController, the animation starts quickly but then hangs and the app crashes without error log.
When instead I use a UIViewController it works perfectly. When again I add a UITableView in the UIViewController, it crashes again.
Any Help?
Vince

I am having the same issue. Has this been solved?

What is the error in the console?


So many codacy issues

Actual Behaviour
There are so many codacy issues which effects Codacy Badge grade
Some of issues are :

Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes.
Switch statements should have a default label
Avoid unused private fields
nested if statements could be combined
Document empty method body
Avoid unused constructor parameters such as 'resources'.
Use one line for each declaration
Use equals() to compare object references
Strings must use doublequote. (quotes)

Cadacy issue link : https://www.codacy.com/app/championswimmer/open-event-android/issues?bid=3438485
Expected Behaviour
Avoiding this kind of mistakes and improve codacy badge grade
Would you like to work on the issue?
Yes
Target Milestone to solve the issue
Milestone 4

@Shailesh351 You could link this issue to #1573

@shreyasnbhat  that issue is for disabling Use explicit scoping instead of the default package private level codacy issue.
And this issue is for fixing existing i mentioned in issue

I meant to say both these issues could be merged into one.

True @shreyasnbhat
@Shailesh351 All the patterns you have listed are required for a good code base, so they shouldn't be disabled
I created the issue for explicit scoping because we require that to use butterknife.

@iamareebjamal @shreyasnbhat I am to talking about disabling patterns i have listed in issue.
I am talking about changing our app's existing code to follow this patterns by making required changes in code.

Sorry for the misunderstanding. Yeah, we need this obviously
You can start making changes, but restrict PRs to package only so they remain small


Setup Instructions

I've not added much in the way of instructions on how to set it up yet, but it's basically:

Fork the repo (and make any changes; ~I should probably parameterise it~)
Create workspace (e.g. by hand), as CLI Driven
Terraform Init
Terraform Import (terraform import tfe_workspace.this <org-name>/<workspace-name>)
Switch workspace to be VCS backed

Give it some TFC creds in a var or varset
Ensure Drift Detection is enabled
Optionally, set up Notifications

Let it do an initial plan & apply...
Modify the workspace somehow (I added an additional tag to the workspace)
Wait 24 hours for your drift detection notification :slightly_smiling_face:

Let's test these instructions out, before I create some better docs...
Create workspace (e.g. by hand), as CLI Driven

Clone repo and TF Init
(In my case, I don't need to make any changes, e.g. creating a tfvars file, as I'm using the defaults. Other people will need to)
✔ strawb@HashiBook ~/git_src/github.com/hashi-strawb/demo-tfcb-drift [main|✔]
$ terraform init

Initializing Terraform Cloud...

Initializing provider plugins...
- Finding latest version of hashicorp/tfe...
- Installing hashicorp/tfe v0.35.0...
- Installed hashicorp/tfe v0.35.0 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform Cloud has been successfully initialized!

You may now begin working with Terraform Cloud. Try running "terraform plan" to
see any changes that are required for your infrastructure.

If you ever set or change modules or Terraform Settings, run "terraform init"
again to reinitialize your working directory.

Terraform Import
✔ strawb@HashiBook ~/git_src/github.com/hashi-strawb/demo-tfcb-drift [main|✔]
$ terraform import tfe_workspace.this hashi_strawb_demo/demo-tfcb-drift

Import successful!

The resources that were imported are shown above. These resources are now in
your Terraform state and will henceforth be managed by Terraform.

Releasing state lock. This may take a few moments...

Switch repo to be VCS backed

Give it some TFC creds

Enable Drift Detection

Setup notifications, slack in my case

Start a new run

And in this case, because I didn't define any tags, it's going to add them...

Modify the workspace (in my case, by adding a tag by hand)

And now we're good. We just wait 24h for Drift Detection to kick in

Moved to https://github.com/hashi-strawb/demo-tfcb-drift/wiki/Setup-Instructions


154: Lesson 4 Page

Summary

add Lesson 4 content and style
add Lesson 4 to SectionHeader enum, app router, and PageOrder enum
organized PageWrapper.scss and added new rules
make Terminal text smaller (21px)

Closes #154

@Dankco please merge the Note component #170 first so I can implement it in Lesson 4 page. Thanks!

Merged.

Ready for review

Removed "Boxed Syntax Notation" label for lesson 2.2 and lesson 4


test: behaviors-force_unlock_on_happy_path (2024-02-19 23:17:49.289388+00:00)

automatic test cleanup


Rename master to tronk

After doing a bit of research into this, it seems like this is going to be a lot easier to do when GitHub releases their tools for seamlessly updating the default branch, which should be "later this year".
This should make the change a little bit more painless, as there are a number of implications that GitHub is working on addressing, and possibly other services that we integrate with.
More info:
https://github.com/github/renaming#later-this-year-seamless-move-for-existing-repositories-

This... is now possible :) https://docs.github.com/en/github/administering-a-repository/renaming-a-branch

This... is now possible :) https://docs.github.com/en/github/administering-a-repository/renaming-a-branch