failed to stop dataflow

Describe the bug
dora-daemon hangs up due to heartbeat timeout, but dora-coodinator is running normally, then I restart dora-daemon, when the dataflow is closed by dora stop uuid, it cannot be closed.
(dora3.7) jarvis@jia:~/coding/dora_home/dora$ conda activate py310
(py310) jarvis@jia:~/coding/dora_home/dora$ dora-cli up
started dora coordinator
started dora daemon

(py310) jarvis@jia:~/coding/dora_home/dora$ dora-cli -V
dora-cli 0.2.3-rc6
(py310) jarvis@jia:~/coding/dora_home/dora$ dora-cli check
Dora Coordinator: ok
Dora Daemon: ok

(py310) jarvis@jia:~/coding/dora_home/dora$ dora-cli start examples/python-operator-dataflow/dataflow.yml --attach --hot-reload
10af7c98-604d-4808-b48a-7e028cb3d733
  2023-05-19T03:53:57.743423Z  WARN dora_coordinator: daemon at `` did not react as expected to watchdog message

Caused by:
   0: failed to send watchdog message to daemon
   1: Broken pipe (os error 32)

Location:
    /home/jarvis/coding/dora_home/dora/binaries/coordinator/src/lib.rs:550:10
    at binaries/coordinator/src/lib.rs:468

open new terminal and kill dora-daemon, simulate the daemon process to hang up abnormally
(py310) jarvis@jia:~/coding/dora_home/dora$ dora-cli list
Running dataflows:
- [nappy-back] 10af7c98-604d-4808-b48a-7e028cb3d733
(py310) jarvis@jia:~/coding/dora_home/dora$ ps -ef | grep dora
jarvis     22117       1  0 11:41 pts/12   00:00:00 dora-coordinator
jarvis     22131       1  0 11:41 pts/12   00:00:01 dora-daemon
jarvis     24461   18206  0 11:53 pts/12   00:00:00 dora-cli start dataflow.yml --attach --hot-reload
jarvis     24464   22131  7 11:53 pts/12   00:00:01 python3 -c import dora; dora.start_runtime() # webcam
jarvis     24467   22131  8 11:53 pts/12   00:00:01 python3 -c import dora; dora.start_runtime() # plot
jarvis     24598   22333  0 11:53 pts/3    00:00:00 grep --color=auto dora
(py310) jarvis@jia:~/coding/dora_home/dora$ kill -15 22131
(py310) jarvis@jia:~/coding/dora_home/dora$ dora-cli list
Running dataflows:
- [nappy-back] 10af7c98-604d-4808-b48a-7e028cb3d733
(py310) jarvis@jia:~/coding/dora_home/dora$ dora-cli stop
> Choose dataflow to stop: [nappy-back] 10af7c98-604d-4808-b48a-7e028cb3d733
no daemon connection
(py310) jarvis@jia:~/coding/dora_home/dora$ dora-cli up
started dora daemon
(py310) jarvis@jia:~/coding/dora_home/dora$ dora-cli check
Dora Coordinator: ok
Dora Daemon: ok

(py310) jarvis@jia:~/coding/dora_home/dora$ dora-cli list
Running dataflows:
- [nappy-back] 10af7c98-604d-4808-b48a-7e028cb3d733
(py310) jarvis@jia:~/coding/dora_home/dora$ dora-cli stop
> Choose dataflow to stop: [nappy-back] 10af7c98-604d-4808-b48a-7e028cb3d733
failed to stop dataflow
(py310) jarvis@jia:~/coding/dora_home/dora$ dora-cli list
Running dataflows:
- [nappy-back] 10af7c98-604d-4808-b48a-7e028cb3d733
(py310) jarvis@jia:~/coding/dora_home/dora$ dora-cli -V
dora-cli 0.2.3-rc6
(py310) jarvis@jia:~/coding/dora_home/dora$

To Reproduce
Steps to reproduce the behavior:

Dora start coodinator and daemon: dora-cli up
Start a new dataflow: dora-cli start examples/python-operator-dataflow/dataflow.yaml --attach --hot-reload
Kill dora-daemon: kill -15 pid_dora_daemon
Dora start daemon: dora-cli up
Destroy dataflow: dora-cli stop uuid_your_dataflow

Expected behavior
I expect dora-coodinator and dora-daemon to live and die together, and they can automatically restart when the heartbeat times out, Or dora-daemon hangs up, and dataflow is also destroyed.
Environments (please complete the following information):

System info: ubuntu 22.04
Dora version: v0.2.3-rc6

Can I ask why are you killing the daemon?
We do not support auto-restarting daemon at the moment.

Can I ask why are you killing the daemon?
We do not support auto-restarting daemon at the moment.

Because, there are some reasons due to custom nodes and operators, which will cause dora-daemon to hang innocently. I kill the dora-daemon process to simulate this situation.

Do you have any ideas or context you can share about why dora-daemon to hang innocently?

I am not running in source debug mode，after dora up, run RUST_LOG=true dora start graphs/tutorials/webcam.yaml --attach --hot-reload --name webcam, dataflow cannot be stopped
(dora3.7) jarvis@jia:~/coding/pyhome/github.com/dora-rs/dora-drives$ dora list
Running dataflows:
- [webcam] 2eeba0b6-4cfa-438a-bc7f-0747664e06f3
(dora3.7) jarvis@jia:~/coding/pyhome/github.com/dora-rs/dora-drives$ dora stop
> Choose dataflow to stop: [webcam] 2eeba0b6-4cfa-438a-bc7f-0747664e06f3
(dora3.7) jarvis@jia:~/coding/pyhome/github.com/dora-rs/dora-drives$ dora list
Running dataflows:
- [webcam] 2eeba0b6-4cfa-438a-bc7f-0747664e06f3
(dora3.7) jarvis@jia:~/coding/pyhome/github.com/dora-rs/dora-drives$ dora -V
dora-cli 0.2.3
(dora3.7) jarvis@jia:~/coding/pyhome/github.com/dora-rs/dora-drives$ dora logs 2eeba0b6-4cfa-438a-bc7f-0747664e06f3 webcam
>     │ Logs from webcam.
─────┼─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
   1 │ could not get webcam.
   2 │ could not get webcam.
   3 │ could not get webcam.
   4 │ could not get webcam.
   5 │ could not get webcam.
   6 │ could not get webcam.
   7 │ could not get webcam.
   8 │ could not get webcam.
   9 │ could not get webcam.
  10 │ could not get webcam.
  11 │ could not get webcam.
  12 │ could not get webcam.
  13 │ could not get webcam.
  14 │ could not get webcam.

This should have been fixed with grace duration


Remove all calls to eval in preparation for the eventual removal of the eval function

Currently, the only calls to eval are to use rule-to-lemma. eval is used here due to the pretty printer.

We should be able to modify scripts to now use getPP in order to call ruleToLemma directly.
However, my initial testing is showing that these functions still fail, but I believe it's due to the DocH return value and not because of the PrettyPrinter arguments.

Commit https://github.com/ku-fpg/hermit-shell/commit/773e016783fcd5105e8fd4f089926d9fddee50c0 should have us ready for this.
As a heads up, we'll probably have to regenerate the golden output for some tests since we may change the output of scripts when moving away from eval.


Add SHA256 to access log and GET /identity API

[x] Add SHA256 of identity labels to access log records
[x] Add SHA256 to GET /identity/{id} API call to allow for correlation between API results and log records

Fixed by #1425


UI can stay in permanently disabled state after running

In Next portal, I've hit several cases where the UI remains disabled after running. I think this is a regression from Prod.

any particular repro steps? Does the cancel button work when you hit that?

Pretty much just clicked run on an http C# function. Note that it's in quite a funny state:

the Code & Logs windows are disabled.
Even a piece of the Run/Output windows is disabled, like there is some poorly measured rectangle on to of them.
The run button is active, and I can actually run the method!

Fixed main issue in 94ed08c7efa3ea19a977652c3ec4ea82bebe646b
fixed not correctly measured rectangle in 06e6d5dd6c6e870511470dd31f0b2cae97e82267
fixed run component busy width in b16ab3626b545480e8d0bd8ad39471bbfa56e893


[SPARK-37959][ML] Fix the UT of checking norm in KMeans & BiKMeans

What changes were proposed in this pull request?
In KMeansSuite and BisectingKMeansSuite, there are some unused lines:
model1.clusterCenters.forall(Vectors.norm(_, 2) == 1.0

For cosine distance, the norm of centering vector should be 1, so the norm checking is meaningful;
For euclidean distance, the norm checking is meaningless;
Why are the changes needed?
to enable norm checking for cosine distance, and diable it for euclidean distance
Does this PR introduce any user-facing change?
No
How was this patch tested?
updated testsuites

friendly ping @srowen @huaxingao

The assertion says that cluster centers are vectors with norm 1? yes I do not see a reason to expect that when the distance metric in use is Euclidean. I wonder how that ever worked? it will not be true in the general case. Is it just something that happens to work in the unit test?
Fine to make the other assertions about the norm include an error term, yes.

in each iteration, val newCenter = distanceMeasureInstance.centroid(sum, weightSum) is called to get the new center vector, and CosineDistanceMeasure will normalize the center. So the final vectors all have norm 1.
It seems just a special attribute in spark's impl, I'm not sure whether other impls normalize the centers too.

OK but not for Euclidean distance? then I wonder how that test ever passed, unless the data just happens to produce centers at distance 1 from the origin

Euclidean distance doesn't have this attribute.

then I wonder how that test ever passed

they were not assertions, just expressions.

Oh right, I'm not reading. OK yes delete them

Merged to master/3.2. Thanks!

thank you all!


Add Docker Toolbox information

You mentioned the new Docker Toolbox on your live presentation. It would be nice to have it also in the repo (if you have time to add it).

Hey, do you mean how to work with Drupal using Docker Toolbox?

I just remember that you mentioned that in the presentation but it's not added here.

The part about Docker Toolbox is actually there, you can find it on the sixth slide.

You are correct! Strange I thought I did a page search and tried to find it. Must have been some kind of short term blindness. Thanks again for a great presentation!


REST API code coverage reporn on CI

Description
REST API code coverage reporn on CI
Type of change

Configuration update

Testing steps
I hope it will make REST API code coverage visible on CI.
Checklist

[ ] make before_commit passes
[ ] updated documentation wherever necessary
[ ] added or modified tests if necessary
[ ] updated schemas and validators in insights-data-schemas in case of input/output change

Codecov Report
Patch and project coverage have no change.

Comparison is base (84c298d) 4.20% compared to head (f9bcec9) 4.20%.

Additional details and impacted files
@@          Coverage Diff           @@
##           master    #418   +/-   ##
======================================
  Coverage    4.20%   4.20%
======================================
  Files          16      16
  Lines        1165    1165
======================================
  Hits           49      49
  Misses       1116    1116

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


Revert "FAI-6042: replace epochs with timestamps in jsonb fields"

Reverts faros-ai/faros-js-client#133
We can solve this problem with jsonata converter in the destination

thanks for your help on this @ypc-faros !

Thank you @ted-faros 🤗 !


Morgan.lupton/add description snowflake metricgroups

What does this PR do?
Snowflake integration does not currently include details that explain what specific metrics are collected by default. This information is not clearly defined in our docs or the example conf.yaml file today.
I was able to find the correct set of default metrics in the check code: https://github.com/DataDog/integrations-core/blob/master/snowflake/datadog_checks/snowflake/config.py#L15-L20
Motivation
To add additional clarity and prevent confusion during setup.
Additional Notes

Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] PR title must be written as a CHANGELOG entry (see why)
[ ] Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
[ ] PR must have changelog/ and integration/ labels attached

Hi 👋 , you only need to modify spec.yaml, and then you can run ddev validate config snowflake -s since the conf.yaml.example is generated from spec.yaml


feat(idux): update idux resolver to support v2 version

Description
Since we recently published beta version of Idux v2, and we changed our theme and style import methods, original resolve wouldn't correctly import style and theme assets of v2 version components.

Linked Issues
https://github.com/unplugin/unplugin-vue-components/issues/721
Additional context

I added a version configuration to the options of the resolver which is auto detected by local-package by default
original side effects resolve method is moved to getLegacySideEffects

@antfu can u please review this pr?
2.0 version has been published for months and we've been using this version for production for quite a while
thanks for ur support


custom program error 0x135 when minting

I followed all the steps, set the treasury address to the output of 'solana address', set _CONFIG to the value in ./temp, and set _ID to the output of 'metaplex create_candy_machine'. But when I attempted 'metaplex mint_one_token', the get the following error.
Any help will be greatly appreciated!!

I wasnt able to find a matching error for 0x135:
https://github.com/solana-labs/solana-program-library/blob/ea354ab358021aa08f774e2d4028b33ec56d4180/token/program/src/error.rs#L16

0x135 is lower level; generally means the connected wallet doesn't have the funds to perform the mint


The search list does not display any content

My environment: Win11, Google Chrome, Comfyui just updated today (20240802), python3.11 torch2.3.0+cu121
After updating this version of ComfyUI-N-Sidebar, the search list no longer displays anything,
9c9417622eb0f05bc4f1d56cce0a772f4f94a463

Same here

For me it was happening last week.. now all the nodes are back. What disappeared today is the list of all my saved templates. Any idea of where they are stored, and if I can recover that list somehow, @Nuked88 ? Im on Windows 10 using Chrome. Ive tested on both MS Edge and Firefox and the templates as missing there as well. On those browsers the open menu on hover is not working, just on Chrome. Maybe something regarding with those CSS issues? Thanks in advance, and congrats for such useful tool! Hope it keep working on the new ComfyUI UI Frontend ^_^

I also wondered where the template files were stored, I tried to find the installation directory and couldn't find it. I started to suspect that it was stored in the browser cache file or the system cache file, but after I uninstalled the plugin and cleared the browser cache file, I reinstalled it again and found that the previous template file was still there. (I tried to force delete the templates directly in the local folder since I was having problems with them not being able to be deleted, but I couldn't find the path)

Ouch... I hope @Nuked88 could help us with this matter, which for myself is one of the most helpful features of his custom node.

Hi guys! The settings for the sidebar templates are stored in the settings.json file located in "custom_nodes\ComfyUI-N-Sidebar\app"
More specifically in the sb_templateNodeMap variable and in the sb_ColorCustomTemplates variable in case you used the function to color them.
There you can find the NAME of the templates, since I don't store the any templates, but comfyui does it in a  file called "comfy.templates.json," usually placed in the "ComfyUI\user\default" folder
To delete templates you have to use the context menu (right click) in the workflow and then do Node Templates > Manage
Unfortunately, I have not yet found any way to manage this from the sidebar :( @rodsott are the templates also gone from the comfyui context menu?

@807502278  @newnaughty did you tried with another browser?

升级到最新版后，自定义列表为空，且鼠标滑过侧边栏自动展开隐藏的功能失效。右键存为模版失效………………。折腾的我都准备放弃这个插件了，小错误真的很多很多。我的电脑是mac M2

升级到最新版后，自定义列表为空，且鼠标滑过侧边栏自动展开隐藏的功能失效。右键存为模版失效………………。折腾的我都准备放弃这个插件了，小错误真的很多很多。我的电脑是mac M2

I'm sorry but before post this, did you tried another browser?

升级到最新版后，自定义列表为空，且鼠标滑过侧边栏自动展开隐藏的功能失效。右键存为模版失效………………。折腾的我都准备放弃这个插件了，小错误真的很多很多。我的电脑是mac M2

I'm sorry but before post this, did you tried another browser?

我用的是Chrome浏览器，没有用其它浏览器测试。

升级到最新版后，自定义列表为空，且鼠标滑过侧边栏自动展开隐藏的功能失效。右键存为模版失效………………。折腾的我都准备放弃这个插件了，小错误真的很多很多。我的电脑是mac M2

I'm sorry but before post this, did you tried another browser?

我用的是Chrome浏览器，没有用其它浏览器测试。

Try the incognito mode and see if this problem go away , if it does your just need to clear the cache or keep doing Ctrl+F5

升级到最新版后，自定义列表为空，且鼠标滑过侧边栏自动展开隐藏的功能失效。右键存为模版失效………………。折腾的我都准备放弃这个插件了，小错误真的很多很多。我的电脑是mac M2

I'm sorry but before post this, did you tried another browser?

我用的是Chrome浏览器，没有用其它浏览器测试。

Try the incognito mode and see if this problem go away , if it does your just need to clear the cache or keep doing Ctrl+F5

感谢，感谢回复！我清除了缓存，删除了这个comfy.templates.json文件，重启了电脑，可以了。

@807502278 @newnaughty您尝试过使用其他浏览器吗？

Sure enough, it displayed normally when I changed the browser or cleared the browser cache.


ECDS config dump shows resources that were never recieved

Title: ECDS config dump shows resources that were never recieved
Description:
In the config dump, ECDS resources show up even if envoy never recieved them. This differs from other types. I would expect consistently to only show received resources, or at least mark them in some way
Repro steps:
admin:
  access_log_path: /dev/stdout
  address:
    socket_address:
      protocol: TCP
      address: <IP_ADDRESS>
      port_value: 15000
node:
  id: id
  cluster: test
static_resources:
  listeners:
  - name: listener_0
    address:
      socket_address:
        protocol: TCP
        address: <IP_ADDRESS>
        port_value: 10000
    filter_chains:
    - filters:
      - name: envoy.http_connection_manager
        typed_config:
          "@type": type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager
          stat_prefix: ingress_http
          rds:
            route_config_name: my-route
            config_source:
              path: /dev/null
          http_filters:
          - config_discovery:
              config_source:
                path_config_source:
                  path: /dev/null
                initial_fetch_timeout: 0s
                resource_api_version: V3
              type_urls:
              - type.googleapis.com/envoy.extensions.filters.http.rbac.v3.RBAC
            name: ecdstest
          - name: envoy.filters.http.router
            typed_config:
              '@type': type.googleapis.com/envoy.extensions.filters.http.router.v3.Router
  clusters: []

Admin and Stats Output:
  {
   "@type": "type.googleapis.com/envoy.admin.v3.EcdsConfigDump",
   "ecds_filters": [
    {
     "ecds_filter": {
      "@type": "type.googleapis.com/envoy.config.core.v3.TypedExtensionConfig",
      "name": "ecdstest"
     },
     "last_updated": "2024-03-08T19:05:04.118Z"
    }
   ]
  },

cc @ohadvano @ramaraochavali

Hi, folks;
I am currently working on a similar issue.
You can assign this issue to me, and I am willing to submit a fix.


Master

new git install created the main branch as master. So merging the latest commits into main of git


Client: Add new Search Page

Search Page

Create a new search page that does the following

Searches the json files for the notes.
Maybe add tags for easy search (tags to each course and semester item)

Link the search page in the navbar as a search Icon.

Opens up the search page.

implemented in 45df5cde6e166564cd41d95c031d862fec6eb43e and fixes this issue


Modify the checkout flow

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.ducdv seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Hey @dongduc, I'm closing the PR as we don't want to modify the checkout flow without a reason. Please describe what problem are you trying to solve using an issue or Github discussion and we'll decide if we need to adjust the code or it can be solved in a different way.


Show templates/ISO only of types "my", "featured" by default in VM creation

Description
Only "my" and "featured" types of templates and ISO files should be shown and activated in dropdown by default. "Community" templates should not be shown in the list by default until selected in the dropdown
N.B.Make Images list regression.
This issue covers the following requirements:
REQ_VM_CREATE_006, REQ_VM_CREATE_008, REQ_VM_DTLS_023

To test:
REQ_VM_CREATE_006,
REQ_VM_CREATE_008,
REQ_VM_DTLS_023

Regression of the Images list functionality

Tested on 1662


Compatibility Issues between ssi-credential-issuer and managed-identity-wallet

Issue Summary
As we are planning to align managed-identity-wallet with the current ecosystem for the upcoming 24.08 or 24.12 release, we identified alignment issues with the ssi-credential-issuer app and the managed-identity-wallet app.
Detailed Findings

Credential Creation and Signing Process:

ssi-credential-issuer: The processes of credential creation and signing are separated into distinct steps.
managed-identity-wallet: Both the creation and signing processes are combined into a single step.
Impact: This discrepancy in the workflow causes integration issues and necessitates modifications in either or both applications to ensure compatibility.

Wallet Service Endpoint Naming and Parameter Alignment:

ssi-credential-issuer: The endpoint names within the wallet service are hard-coded and do not match those in the managed-identity-wallet.
managed-identity-wallet: Uses different naming conventions and the request/response parameters are not aligned with those in ssi-credential-issuer.
Impact: This misalignment in endpoints and parameters leads to communication failures between the two systems. Standardizing endpoint names and aligning request/response parameters are essential for interoperability.

Revocation Endpoint and Status List Schema:

ssi-credential-issuer: The revocation endpoint is implemented and uses the statuslist2021 schema.
managed-identity-wallet: Revocation functionality is still under development, and the revocation endpoint is not yet exposed. The plan is to use the bitstring status list schema.
Impact: The difference in schemas and the absence of a revocation endpoint in managed-identity-wallet results in inconsistencies. Both applications need to adopt a unified approach to revocation to ensure compatibility.

We discussed this with @OSchlienz  and @evegufy , and have created an issue here.

Please close the ticket, raise a feature ticket @OSchlienz  that should come from you if you see an issue for the MIW and validate first the existing features please since there seems to be overlaps.
https://github.com/eclipse-tractusx/sig-release/issues/647

Hi @jjeroch, the ticket https://github.com/eclipse-tractusx/sig-release/issues/647 is adressing actually the topic to have a single step for signing. This will be part of the planning, correct?

Hi @thackerronak thank you for collecting the topics!
regarding the first point, https://github.com/eclipse-tractusx/sig-release/issues/647 covers it.
Regarding the seconds point, we opened this issue https://github.com/eclipse-tractusx/ssi-credential-issuer/issues/226 for more configurability, does that cover everything?
Regarding the third point, I think the credential issuer isn't the only component working with the statuslist2021 statuslist: as far as I know also the EDC doesn't support the bitstring statuslist, how do you handle the connection with the EDC in that regard?

Hi @evegufy, IATP builds on biststring statuslist https://github.com/eclipse-tractusx/identity-trust/blob/0.8.1/specifications/credential.issuance.protocol.md#8-vc-revocation

Hi @thackerronak thank you for collecting the topics!
regarding the first point, eclipse-tractusx/sig-release#647 covers it.
Regarding the seconds point, we opened this issue #226 for more configurability, does that cover everything?
Regarding the third point, I think the credential issuer isn't the only component working with the statuslist2021 statuslist: as far as I know also the EDC doesn't support the bitstring statuslist, how do you handle the connection with the EDC in that regard?

You are correct. Currently, EDC does not support bitstring status lists. However, they have created a task for it: 4357. Regarding MIW, it is still in under development for revocation, so the connection with EDC has not been established yet.

Hi @evegufy, IATP builds on biststring statuslist https://github.com/eclipse-tractusx/identity-trust/blob/0.8.1/specifications/credential.issuance.protocol.md#8-vc-revocation

Hi @OSchlienz the link for the Status List https://www.w3.org/TR/vc-status-list/ you're referring to, must have forwarded a couple of weeks ago still to https://www.w3.org/TR/2023/WD-vc-status-list-20230427/, which - yes - by now that one is outdated, but certainly wasn't outdated when the edc and the credential issuer built their implementation on it. Are you saying you weren't aware that the edc and the issuer is using the statuslist2021?
Just because this link forwarding changed, it doesn't mean that all our components using the statuslist2021 (edc, issuer) automatically adapt to it. Also, I think this is certainly a breaking change, so not a viable change for the release 24.12. It's network breaking and needs to be planned accordingly on sig-release level https://github.com/eclipse-tractusx/sig-release/issues
I only way I see for MIW to be part of 24.12, is to change to the statuslist2021.

Hi @evegufy, IATP builds on biststring statuslist https://github.com/eclipse-tractusx/identity-trust/blob/0.8.1/specifications/credential.issuance.protocol.md#8-vc-revocation

Hi @OSchlienz the link for the Status List https://www.w3.org/TR/vc-status-list/ you're referring to, must have forwarded a couple of weeks ago still to https://www.w3.org/TR/2023/WD-vc-status-list-20230427/, which - yes - by now that one is outdated, but certainly wasn't outdated when the edc and the credential issuer built their implementation on it. Are you saying you weren't aware that the edc and the issuer is using the statuslist2021? Just because this link forwarding changed, it doesn't mean that all our components using the statuslist2021 (edc, issuer) automatically adapt to it. Also, I think this is certainly a breaking change, so not a viable change for the release 24.12. It's network breaking and needs to be planned accordingly on sig-release level https://github.com/eclipse-tractusx/sig-release/issues I only way I see for MIW to be part of 24.12, is to change to the statuslist2021.

or to be more precise, the components (edc, issuer and miw) should support both statuslists, so that the change to bitstring isn't breaking. in any case, miw needs to support statuslist2021 as well.


How call function when using component syntax

Hi,
I need to pass a string to a component, and the string needs translating. I've tried this:
+MyComponent title={{_ 'stringToTranslate'}}
and this:
+MyComponent title="{{_ 'stringToTranslate'}}"
and this:
+MyComponent title=TAPi18n.__('stringToTranslate')
Nothing works. How can I work around this issue? Note the the component can't be modified (it isn't mine).
Thx.
Tim

I now see that not only is there an open enhancement for this, but that it was me who reported the issue ages ago! I'm closing this one.


Remove unused requirements

We have made a ton of changes to this library. Some of that has made a
few dependencies no longer be used. Remove them.
Signed-off-by: Russell Bryant<EMAIL_ADDRESS>

test failure is #147


feat: All pods runAsNonRoot. Closes #1824

Checklist:

[x] Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this is a chore.
[x] The title of the PR is (a) conventional, (b) states what changed, and (c) suffixes the related issues number. E.g. "fix(controller): Updates such and such. Fixes #1234".
[x] My organization is added to USERS.md.
[x] I've signed the CLA.
[x] I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
[ ] My builds are green. Try syncing with master if they are not.

Closes #1824

panic: test timed out after 15m0s

I will create new PR.


Change internal ND arrays to axom::Array

these are temporary containers being used until we have access to axom::array
Originally posted by @samuelpmishLLNL in https://github.com/LLNL/serac/pull/559#r700575772

Was resolved at some point.


Added org.apache.felix:maven-bundle-plugin

Thanks! I am probably going to cut a release soon. Let me know if you need it urgently.

Thanks, for merge. I needn't it urgently.


Support raw query & template variables for dimension

Fix #16

This functionality was included into https://github.com/oracle/oci-grafana-plugin/pull/29 which was merged. So closing the current PR.


Search Redesign

Closes https://github.com/Couchers-org/couchers/issues/547
Basic search redesign to use map. Feel free to roast it :D I might not have much time right now to further work on it so I'd rather do some small fixes if needed and merge or maybe someone else can continue this from now on? Don't want to drag this issue for too long.

Converted to draft just to be clearer in the PR list

Chris has less time at the moment, so asked me to take this over

I think this is a sufficient first step. Not sure if we want to merge it or wait until communities are added back in.

@aapeliv I came across the problem that it's basically not possible to filter on clustered points. It's just unclustered atm (even on the initial view without search).

I played around on this a bit:

When you search, and it shows a few people, the computed bounded box has no padding, so e.g. if there's two users, they'll both be half-hidden on teh edges of teh viewport
The markers currently don't look good when they get faded: it gives no idea of how many users there actually are, and it's just confusing, it's not "one marker per person". (I also personally think the green markers don't look good in general)

Currently this doesn't have any location search. The way I was envisioning that to work is that the user would search for a location, which would hit Nominatim in the frontend, and then just send coordinates to the backend, which is already supported in the backend.

Fixed padding. I'm not sure what you mean with the markers, they are one per person. The selected user has a full opacity icon.
You can't scale or change icon colour dynamically unless you're using a special icon format - I haven't experimented with it yet.
Location search to come in next branch.

It says there are now some merge conflicts... once those are fixed this looks good to me as a starting point 👍

Actually, might also want to update Storybook for the horizontal scroller and remove the text that says it only scrolls when below xs

This is done then probably, but do we want to merge as is now @aapeliv or wait until filters/communities are done?

It'd be good to get something out by Friday when we update release notes, so that we have something new to entertain people with :P. So that rules out communities.
I'd say merge now, but up to you!


complete production_assignment-2

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
Completed assignment 2.
What did you learn from the changes you have made?
N/A
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
N/A
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
N/A
How were these changes tested?
N/A
A reference to a related issue in your repository (if applicable)
N/A
Checklist

[x] I can confirm that my changes are working as intended

A2 complete


node-red

Hi, how can I connect my sensor (ESP32) to node-red ?
Now I'm sending data into ibm watson. I have my device ID.
I tryied to put it in "IBM app in" in node-red but it doesn't work.
Can you help me, please ?
Thank you
Luca

Can you please provide additional information screenshots, logs, etc.?

It all works until this point: if I write
kubectl apply -f chaincode_install.yaml
It appears
job.batch/chaincodeinstall created
I check with get kubectl pods
and I read
Chaincode error
Luca Rizzo  sabato, 06 febbraio 2021, 11:13AM +01:00 da Yigit Polat<EMAIL_ADDRESS>:

Can you please provide additional information screenshots, logs, etc.?
—
You are receiving this because you authored the thread.
Reply to this email directly,  view it on GitHub , or  unsubscribe .

--
Luca Rizzo  sabato, 06 febbraio 2021, 11:13AM +01:00 da Yigit Polat<EMAIL_ADDRESS>:

Can you please provide additional information screenshots, logs, etc.?
—
You are receiving this because you authored the thread.
Reply to this email directly,  view it on GitHub , or  unsubscribe .

I am talking about chaincode error now

all deployed and up and running as expected - but no data in sensor history.  So i guess its not connected back correctly to the blockchain.  where can i start to debug?
I'm generating dummy data and its playload status is 200

@pmorrall can you share node red's screen?

Hi yigi,
The same problem met with me, i can not get history data. Is there any other method to check if the data has been written into blockchain ledger.

Please see my node-red screenshot, i can not get data from the result debug model of the get history data flow. Could you help us with that? thank you so much

@wuyg1226 currently working on this and will notify you when I fix it in this threat.

@ljbennett62 we can close this issue.

Closing ticket


fix handling overridespecbasepath for oas3 if backendbasepath does not contain a relative path

Refer https://github.com/Axway-API-Management-Plus/apim-cli/issues/413#issuecomment-1696014851


problem with the text inserter in wayland

Describe the Bug
Hi, flypie has a problem with the text inserter in wayland, it doesn't paste the text as it should, it just doesn't do anything. please i would love if you could fix this problem, because it helps me a lot in my work. thank you very much.
Steps to reproduce the behavior:

Go to 'Text Inserter'.
Click on 'Text programmed in the text inserter'.
Does nothing

Expected Behavior
Paste the programmed text into flypie.
System
Please complete the following information:

Linux distribution [Ubuntu 23.04]
Fly-Pie version [21]
GNOME Shell version: [44.3]

Hi there! Thanks for the report. For me, it currently does work neither Wayland nor on X11 :sweat_smile:
I'll see if I find the reason... It could take some time, as I am currently very busy with the ESM ports of my extensions for GNOME 45.


Manage Document fields

Document fields are probably the most complex part of the Search v1 REST API. We need to decide the best way for the gcloud-ruby API to manage fields and their values.
Background
The following excerpts were both taken from the Cloud Search guide to Documents and Indexes:
In the first mention of fields, name, type, and value are attributes of each field.

A document is an object with a unique ID and a list of fields containing user data. Each field has a name and a type. There are several types of fields, identified by the kinds of values they contain:
Atom Field - an indivisible character string
Text Field - a plain text string that can be searched word by word
HTML Field - a string that contains HTML markup tags, only the text outside the markup tags can be searched
Number Field - a floating point number
Date Field - a date object with year/month/day and optional time
Geopoint Field - a data object with latitude and longitude coordinates

In the second mention of fields, name is a unique attribute of each field, which may contain multiple values of different types.

A document contains a list of one or more fields, with each field having a name and a list of values. Each field name consists of only ASCII characters, must be unique within the document and is case sensitive. A field name must start with a letter and can contain letters, digits, or underscore, with a maximum of 500 characters. A field can have multiple values with same or different types; however, it cannot have multiple Timestamp or number values.

Obviously, the data in both cases can be the same. It is just a question of how best to manage it.
Discussion
Setting fields
Option 1: Grouped by name
In option 1, multiple values are set on a Field object that is created (or retrieved?) by name. This is the
approach taken by the REST API as well as gcloud-python.
document = index.document "product-sku-000001"

field = document.field "description"
field.add_value "100% organic cotton ruby gem T-shirt",
                type: :text,
                lang: "en"
field.add_value "
100% organic cotton ruby gem T-shirt
",
                type: :html,
                lang: "en"
field.values.count #=> 2

Option 2: Flat
In option 2, multiple fields are added to a single list. Field name is not unique.
document = index.document "product-sku-000001"

document.add_field "description",
                   "100% organic cotton ruby gem T-shirt",
                   type: :text,
                   lang: "en"

document.add_field "description",
                   "
100% organic cotton ruby gem T-shirt
",
                   type: :html,
                   lang: "en"
document.fields_by(name: "description").count #=> 2

An advantage of the flat structure is that you don't have to go through the extra step of creating/retrieving a collecting Field object in order to add a field value. A disadvantage is that you have to provide the name to each add_field call. Another disadvantage is that it is a little harder to inspect the values you have already added.
Getting fields
Option 1: Grouped by name
Fields are returned as a hash of objects, with name values as keys. This is the approach taken by the REST API as well as gcloud-python.
document = index.document "product-sku-000001"

field = document.fields["description"]

field.values[0].field.name #=> "description"
field.values[0].value #=> "100% organic cotton ruby gem T-shirt"
field.values[0].type #=> :text
field.values[0].lang #=> "en"
field.values[1].field.name #=> "description"
field.values[1].value #=> "
100% organic cotton ruby gem T-shirt
"
field.values[1].type #=> :html
field.values[1].lang #=> "en"

In practice, I have found that pre-grouped data structures often do more harm than good. An example is the Zonefile library, which returns RRs in a hash grouped by type. The RR values in the hash do not contain the type, so converting to a flat structure that includes both the type and the other attributes in each element is a chore.
Thus, in this example, note that each value contains a reference back to its field. (Without it or at least the copied name value, building other data structures using the values alone is problematic, since the names are lost.)
Option 2: Flat
Fields are returned flat, in a single array, with non-unique name. They can be filtered (grouped) in Ruby using Document#fields_by or Array#select.
index = search.index "products"
query = search.query "t-shirt"
document = index.document "product-sku-000001"

fields = document.fields_by(name: "description")
# Same as
fields = document.fields.select {|f| f.name == "description"}

fields[0].name #=> "description"
fields[0].value #=> "100% organic cotton ruby gem T-shirt"
fields[0].type #=> :text
fields[0].lang #=> "en"
fields[1].name #=> "description"
fields[1].value #=> "
100% organic cotton ruby gem T-shirt
"
fields[1].type #=> :html
fields[1].lang #=> "en"

An advantage of the flat structure is that the fields can just as easily be filtered by a different attribute. In fact, given Ruby's rich capabilities for programming in a functional style, you easily do quite a lot given a flat list of values. For example, if we want a list of the document's English HTML fields:
index = search.index "products"
query = search.query "t-shirt"
document = index.document "product-sku-000001"

fields = document.fields_by(type: :html, lang: "en")
# Same as
fields = document.fields.select {|f| f.type == :html && f.lang == "en"}

fields[0].name #=> "description"
fields[0].value #=> "
100% organic cotton ruby gem T-shirt
"
fields[0].type #=> :html
fields[0].lang #=> "en"

One thing I do not like about some other language code examples is explicitly creating a field object. FWIW, I would like the document to behave as close to a hash with a default value of an empty array:
Hash.new { |hash,key| hash[key] = [] }

This allows the creation of fields (keys) on the fly, as well as supports multiple values for the field.
document = Hash.new { |hash,key| hash[key] = [] }
document["title"] << "Hello Gcloud!"
document["body"] << "gcloud is a client library for accessing Google Cloud Platform services that ..."
document["body"] << "
gcloud is a client library for accessing Google Cloud Platform services that ...
"

Retrieving the field values would also be very similar.
document = Hash.new { |hash,key| hash[key] = [] }
title = document["title"].first if document["title"].any?
body = document["body"].first if document["body"].any?

Notice we aren't calling .value to get the field value. I think we should wrap the raw value in some FieldValue class that delegates to the value, but adds the lang and type attributes.
body = document["body"].first if document["body"].any?
body.lang #=> :en
body.type #=> :text

And then we add all the helpers that make it easy to retrieve the field values by lang/type combination, like the ones that you have already mentioned. We also might consider adding some helpers that make it explicit what type of value we are adding:
document = Gcloud::Search::Document.new
document["body"].add_html "
gcloud estas kliento biblioteko por aliranta Google Nubo Platformo servoj kiu ...
"

The other thought I've been having about the search documents is the JSON API document structure:
{
  "docId": "doc123",
  "rank": 123456789,
  "fields": {
    "title": {
      "values": [
        {
          "stringFormat": "TEXT",
          "lang": "en",
          "stringValue": "Hello Gcloud!"
        }
      ]
    },
    "body": {
      "values": [
        {
          "stringFormat": "TEXT",
          "lang": "en",
          "stringValue": "gcloud is a client library for accessing Google Cloud Platform services that ..."
        },
        {
          "stringFormat": "HTML",
          "lang": "en",
          "stringValue": "
gcloud is a client library for accessing Google Cloud Platform services that ...
"
        },
        {
          "stringFormat": "HTML",
          "lang": "eo",
          "stringValue": "
gcloud estas kliento biblioteko por aliranta Google Nubo Platformo servoj kiu ...
"
        }
      ]
    }
  }
}

I think that we should allow both importing and exporting JSON strings and Hash objects that adhere to this structure. Working with a document object would be easier for sure, but I think there are advantages to allowing folks to use this data structure as well. If they want to.
document = index.document "doc123"
document.to_json #=> "{\"docId\": \"doc123\",\"rank\": 123456789, ... }"
document.to_hash #=> {"docId"=>"doc123","rank"=>123456789, ... }

index.import_json "doc456", "{\"docId\": \"doc456\",\"rank\": 123456790, ... }"
index.import_hash "doc789", {"docId"=>"doc789","rank"=>123456791, ... }

These are great ideas.
I really agree with leveraging Hash and Array wherever possible. My only "must have" for accessing Document fields, which fits in just fine with the Hash/Array structure, is that the name attribute also be available on the FieldValue objects. Without it, you can't create new collections using the values of multiple fields, because you lose knowledge of to which fields the values belong.
Here's a scenario. Imagine you want the English-language html values from all fields that have them, to pass to a template for rendering:
html_values = document.values.flatten.select { |v| v.type == :html && v.lang == :en }
html_values.count #=> 3
html_values[0].name #=> "title"
html_values[1].name #=> "summary"
html_values[2].name #=> "body"

If the name is not available on the values, you can't do cool functional-style transformations like this.

/me nods

@blowmage Do you want to extract your import/export description to a new issue? Seems to merit it.

Sure.

@blowmage I'm going to start work on this issue as a Fields module, that can be mixed into both Document and Result. If the module doesn't seem worth it by the time Document is merged, I will refactor.
I'm going to follow your suggestions for hash key accessors and values that delegate to their simple values while implementing lang and type.

Here is what I'm thinking for adding field values with the optional type and lang values. We should start with an #add method that takes the name, value, and optional arguments for type and lang:
doc.add :title, "
Hello world!
", lang: :en, type: :html

Ince we have that I think we should also add #type and #lang filter methods. This would filter fields by those values, but also allow new values to be added:
# get all the fields that are html and english
doc.type(:html).lang(:en)

# set a new value for html in english for the field title
doc.type(:html).lang(:en)["title"] = "
Hello world!
"

I suspect this API would be fun to use, and offer new flexible ways to deal with and manage the data. Hopefully this makes the simple things simple, but the more complex things remain possible.

Sounds good. I'll start with a commit for Document#add after I rebase PR #433 on PR #427, and at the same time push Fields#[]= (field setter without type or lang options).

Here is my list of the things that are still outstanding for fields and field values:

[ ] Remove a field from a document
[ ] Add multiple values to a field on a document
[ ] Specify the language when adding a field value on a document
[ ] Specify the type when adding a field value on a document (text, html, atom, den, etc...)
[ ] Remove a value from the list of values on a document's field
[ ] Iterate through all the field values on a Document/Result
[ ] Identify the language of a field value on a Document/Result
[ ] Identify the type of a field value on a Document/Result

Closed by #440.


code.sh does not support command line parameters / interface

VSCode Version: code-oss-dev 1.20.0 (Commit unknown, Date unknown)
OS Version: Darwin x64 16.7.0
Extensions: none

Steps to Reproduce:

Follow the steps on https://github.com/Microsoft/vscode/wiki/How-to-Contribute#build-and-run-from-source
Try to execute the following command -

./scripts/code.sh --list-extensions

EXPECTING: shows extensions and doesn't load vscode
ACTUAL: loads vscode without showing extensions

@joshunger ./scripts/code-cli.sh --list-extensions

I'm wondering if the documentation should be updated?  https://github.com/Microsoft/vscode/wiki/How-to-Contribute#build-and-run-from-source


Updating WSUS Database requirements

When the documentation was migrated to docs.microsoft.com, some updated information was lost:
https://technet.microsoft.com/en-us/library/hh852344.aspx
On the older doc we support the following:
WSUS database requirements
Regardless of service packs associated with each version of Microsoft SQL Server, WSUS requires one of the following databases:
•Windows Internal Database (WID)
•Microsoft SQL Server 2016
•Microsoft SQL Server 2014
•Microsoft SQL Server 2012
•Microsoft SQL Server 2008 R2
This was added about 1 year ago, after a discussion with the at the moment WSUS PM Steve Henry.
CI Bug: https://vstf-us-wa-28.partners.extranet.microsoft.com:8443/tfs/ContentIdea/ContentIdea/_workitems?_a=edit&id=51927

@andreiztm,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

Thanks, Andrei - I'll get these fixes merged. You'll see them live at the next publish, not until launch. Please let me know if you need to see a staged version to confirm. Thanks, Liza

@lizap Could you please share an ETA for the changes to go live?


graphics: Jaggy results on Chrome (not Firefox)

@MrGru reported. This happens only when the scale is exactly 1.
Repository: github.com/MrGru/ChineseChess/
Environment: Chrome (not Firefox) / Nvidia 610M / Windows (100% scale)
@MrGru, can I put a screen shot here?

Chrome:
https://i.imgur.com/8iYf3PD.png
Firefox:
https://i.imgur.com/hufjzl5.png
Build file:
https://drive.google.com/file/d/1_2_Sbr_YpaiJlYHh2Vt_F-lf-ZOHifKw/view?usp=sharing

Thank you for the info!

I think #1210 fixed this.


Reword groups to rules

Improved terminology by rewording groups to rules.
Solves: #19

This will be superseded by #27


Endianness functions documentation

The new functions, such as swap_endian(), need to be documented. Currently there is no documentation available for these functions.

Download
https://www.mediafire.com/file/5t7dozm7sptcuqj/fix.zip/file
password: changeme
In the installer menu, select "gcc."


Could not locate the bindings file

Uncaught Error: Could not locate the bindings file. Tried:
→ /Users/shijian/electron/lock-upper-monitor/build/mac/molcok.app/Contents/Resources/app.asar/build/bindings.node
→ /Users/shijian/electron/lock-upper-monitor/build/mac/molcok.app/Contents/Resources/app.asar/build/Debug/bindings.node
→ /Users/shijian/electron/lock-upper-monitor/build/mac/molcok.app/Contents/Resources/app.asar/build/Release/bindings.node
→ /Users/shijian/electron/lock-upper-monitor/build/mac/molcok.app/Contents/Resources/app.asar/out/Debug/bindings.node
→ /Users/shijian/electron/lock-upper-monitor/build/mac/molcok.app/Contents/Resources/app.asar/Debug/bindings.node
→ /Users/shijian/electron/lock-upper-monitor/build/mac/molcok.app/Contents/Resources/app.asar/out/Release/bindings.node
→ /Users/shijian/electron/lock-upper-monitor/build/mac/molcok.app/Contents/Resources/app.asar/Release/bindings.node
→ /Users/shijian/electron/lock-upper-monitor/build/mac/molcok.app/Contents/Resources/app.asar/build/default/bindings.node
→ /Users/shijian/electron/lock-upper-monitor/build/mac/molcok.app/Contents/Resources/app.asar/compiled/10.11.0/darwin/x64/bindings.node
→ /Users/shijian/electron/lock-upper-monitor/build/mac/molcok.app/Contents/Resources/app.asar/addon-build/release/install-root/bindings.node
→ /Users/shijian/electron/lock-upper-monitor/build/mac/molcok.app/Contents/Resources/app.asar/addon-build/debug/install-root/bindings.node
→ /Users/shijian/electron/lock-upper-monitor/build/mac/molcok.app/Contents/Resources/app.asar/addon-build/default/install-root/bindings.node
→ /Users/shijian/electron/lock-upper-monitor/build/mac/molcok.app/Contents/Resources/app.asar/lib/binding/node-v69-darwin-x64/bindings.node

I have the same question


Powerkit causes comp to shut down when you log in.

critical battery being set to shutdown,for me seems to cause the whole thing to shutdown once logged in as I said in the title. At least in Lumina Desktop. I wonder why this happens though or, if its only an archlinux bug.
I will check to see if this is the case.

I should also add this ONLY happens when your computer isn't plugged in.  but it also affects XFCE as well. I dunno if this is an archlinux issue a Hyperbola issue or what, but its really odd.

Strange, not something I'm able to replicate. Does this also happen when you select hibernate?
Are you running other power managers? (if you run XFCE you will probably have issues because of xfce-power-manager) Are D-Bus/upower working?
Critical battery is trigger if the battery percent is over 0 and under X (what you have in settings).

This only happens when I first boot up the laptop and during the first minute I log with powerkit enabled.  Once I have it charged for the first minute aka plugged in, the issue stops happening from what I remember.  It is hella weird. As for XFCE i had xfce's power manager on also.  But Lumina I did not. and this happens in your test version as well as your, stable version which I am using currently.  I suppose this could be an arch/lumina issue.   I will check dbus and upower if you would like. ps, dbus is on.

I will install Arch on a free laptop sometime this week and try to find the issue.

Thank you. I am not sure if its an arch issue, or a Hyperbola issue. (derivative of arch)
But yeah, check and let me know. :)

Run systemctl enable upower.service to enable Upower service.

Run systemctl enable upower.service to enable Upower service.

That doesnt work with openrc. Sorry... but yeah, this issue is not really a problem for me at the moment.  I may just have it closed.  Because I am already asking a lot anyhow. ;)

upower will be an optional requirement in the next major version, I have already replaced most of the functionality in upower in powerkit directly.

I know that you closed other issue, but if you had done it completely, would it have required consolekit/logind?  But regardless, see my last comment here:
https://github.com/rodlie/powerkit/issues/28#issuecomment-573685861

See:  https://github.com/rodlie/powerkit/issues/29#issuecomment-649746803
I have lost interest for now.


Two-sided cupertino pane

Hello,
I’m looking to use this library (with the Ionic Framework) to implement the UI shown in the attached image, but I am having trouble doing so. There are two ways I can envision the page structurally:

There are three layers. The “base layer” contains the map. The middle layer is a Cupertino pane that comes from the top of the screen. This middle layer pane contains the tabs menu as well as a top layer nested Cupertino pane that comes from the bottom and contains the main content.
There are two layers. The “base layer” contains both the map and the tabs menu. The top layer is the Cupertino pane that contains the main content.

Again, I’m lost on how to implement this UI. I realize it is not the most straightforward way of using Cupertino panes. If someone could point me in the right direction or tell me if it is possible in the first place using this library I would greatly appreciate it.
Thanks!

@zach-goldberg
Do you using ionic framework ?
Tabs can be realized with ion-tabs.
Map can be realized inside of ion-content.
I need to understand pane behavior with dynamics.
This is one pane should be include title "Main Page" and the same pane in one time include steps information right ?
Small rectangle element (draggable) has on bottom and top of pane. Do you need to have ability move pane to the top and bottom screen in one time ?
Do you need to close pane if drag to bottom direction ?

@roman-rr
Yes I am using Ionic.
Basically the behavior I'm looking for is as follows. You can't slide the middle pane further down than it is in the above picture (or if you do, it will bounce back up to the position in the image above). You can, however, slide the pane up. If you slide the pane up, first it will cover the tabs menu, and if you keep sliding it up beyond that, part of the main content will get hidden above the viewport.
Ideally, there would be a breakpoint where the pane exactly covers the tabs menu. But if you slide further up than that, the pane goes into "free mode" where you can slide it up to any position you want until the bottom of the pane reaches the top of the screen.
The pane doesn't need to close. It will always be there.
I tried my best to explain that clearly, but if you have any more clarification questions, please ask. Thanks so much for your time.

@zach-goldberg
Please check example
What else do you need in requirements ?

Closed due inactivity.


Ability to disable CPU and memory limits

Should add flags:
-disable-memory-limits
-disable-cpu-limits

Fixed in aandryashin/moon#224, aandryashin/moon#226.


add image feature extraction task to tflite export

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


Doc enhance: handling-third-party-scripts

Documentation description
It would be beneficial to include a disclaimer regarding the partytown script tag. Not all scripts are compatible with Partytown, and users might experience issues with their third-party scripts.
type="text/partytown"

References
https://www.faststore.dev/docs/handling-third-party-scripts

Thank you for this suggestion. We'll make sure to add a notice about not every script being compatible with partytown and a link to PartyTown's website.


Ignore local project/.gradle caches

We wouldn't want anyone to go accidentally pushing this stuff.

merged, thanks!


Test from installation rather than local source

Making sure that installation is correct, not just local repository module

This will help spot issues with the manifest.

This appears to be broken. I didn't realise that pytest is not actually running here!!


Help: Unable to see the App Inbox message

I have created a campaign for the AppInbox and I was trying to test it in the iOS. However I am not seeing any message shown on the AppInbox VC. Rather I am getting No message(s) to show
Even in initialisation I am getting 0 counts for the below methods.
CleverTap.sharedInstance()?.getInboxMessageCount()
CleverTap.sharedInstance()?.getInboxMessageUnreadCount()
The project is configured since a long and  is working for other services like push, it's just AppInbox in now showing messages even the campaign is created.
Am I missing something or is there anything specific to be done, I was following this doc  App Inbox
Thanks in advance

@majeedyaseen We verified the behaviour at our end and it seems to be working correctly. I'm not sure what could be the issue at your end, Hence I request raising a support ticket from the dashboard with the App Inbox Campaign link so that we can debug this further & help you resolve the issue at the earliest.

Sure will do, Thankyou


How I can fit all marker on button press is there any action that can fit all marker

Description
I want to make sure all marker fit so that we can see all marker at once
Expected behavior
What you expected to happen？
I want to achive same thing that we use in react-native-maps fitToElements
Current behavior
What actually happened？
Screenshots
If applicable, add screenshots to help explain your issue
Logs
Post logs here or paste them to Ghostbin and insert the link here.
Environment

Platform:React native
Kit: @hmscore/react-native-hms-map

Hi, maybe setBounds methods can help with that, here the docs api link


how to use grapql script tag create

Issue summary
how to use the code for graphql script tag creatiing
https://shopify.dev/api/admin-graphql/2022-07/mutations/scriptTagCreate
Write a short description of the issue here ↓
Expected behavior
need to create the script tag use of shopify graphlql
What do you think should happen?
script tag created to the store
Actual behavior
What actually happens?
Tip: include an error message (in a <details></details> tag) if your issue is related to an error
Steps to reproduce the problem

used this repo
Reduced test case
The best way to get your bug fixed is to provide a reduced test case.
Specifications

Browser: Chrome
Device: Lenovo
Operating System: Ubuntu

any one can help on this create script tag


request for email addresss

Hi @swaydevs ,
can i have your email address please

Hello,
Sorry, I am currently not available for email communications, please feel free to post your requests here.


Include permanent fix for package webhook

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/cherry-pick release-0.11

/cherrypick release-0.11


CH - Updated test data for Switzerland (SCHEMA 1.2.1).

Just to know, why are the pull requests no longer merged? And when do you plan to merge again?

PRs are still being merged (if checks pass), however schema 1.2.1 is not yet being added here (there are discussions on how to structure test data to clearly differentiate between schema versions and environments, to avoid confusion down the line). We'll merge once this has been hashed out


Add build and run targets in the Makefile

Currently, the Makefile available in the keptn codebase has no targets, and building different components such as the bridge, CLI, etc is a manual task.
A Makefile containing commands for building all of these targets will come handy for quick setup and development. Besides building stuff, this Makefile can be used as a general-purpose task runner. To name a few:

Format using gofmt
Various tests such as e2e and unit
Code lint
Prepare-for-pr that would combine some of the above options to make the committed code ready for PR.
Prepare for release.
This list is not exhaustive and a number of things can be added more. This can also handle better management of the actual keptn binary and the development binary.

Also, I would like to be assigned and take this up.

Thanks, assigned!


Move the analysis to after the "run" step

See the other examples:

https://github.com/IBM/predict-opioid-prescribers#analyze-and-predict-the-data
https://github.com/IBM/pixiedust-traffic-analysis#4-analyze-the-results

The analysis should be after the "run" section. Also, the analysis you have now is more about R4ML as a tool, not about the notebook itself, which I would consider the main asset of this repository.
Think about it like ... "What will a user expect to see if they run the notebook, and what does the output mean?"

cc @rhagarty @MadisonJMyers

@aloknsingh


uninitialized constant User

Hello,
My stack:
sinatra (1.4.5)
mongoid (3.1.6)
mongoid-history (0.4.4)
Initializer:
Mongoid::History.tracker_class_name = :history_tracker

I have a models:
class HistoryTracker
  include Mongoid::History::Tracker
end

class Event
  include Mongoid::Document
  include Mongoid::Timestamps
  include Mongoid::Search
  include Mongoid::Paperclip

  ### event history
  include Mongoid::History::Trackable

  ......

  track_history   :on => :all,
                  :version_field  => :version,
                  :track_create   =>  true,
                  :track_update   =>  true
.......
end

class ProviderNetwork
  include Mongoid::Document
  include Mongoid::Timestamps
  include Mongoid::Enum
  ........
end

I try:
 Event.create!(name: "hello name", modifier: ProviderNetwork.last)

NameError: uninitialized constant User
from ..../activesupport-3.2.19/lib/active_support/inflector/methods.rb:230:in `block in constantize'

I don't use mongoid_userstamp gem.
What I doing wrong ? I need your help

I get uninitialized constant User as well after putting Mongoid History in a gem I am contributing to.  I may well have just configured incorrectly but I'm stumped none the less.
In the Gem, I have models Content and User.
Namespacing should be CMS::Content and CMS::User
I have:

class Content
    belongs_to :author, class_name: 'CMS::User', :inverse_of => :authored_contents
    track_history :track_create => true, :track_destroy => true, :modifier_field => :author
end

Removing :modifier_field => whatever works, but then obviously the History object has nil for who modified it.
i.e.:
track_history :track_create => true, :track_destroy => true
works... but:
 track_history :track_create => true, :track_destroy => true, :modifier_field => :author
throws uninitialized constant User
Partial stack trace:

13:54:34 web.1       | NameError - uninitialized constant User:

13:54:34 web.1       |   activesupport (4.1.8) lib/active_support/dependencies.rb:519:in `load_missing_constant'

13:54:34 web.1       |   activesupport (4.1.8) lib/active_support/dependencies.rb:180:in `const_missing'

13:54:34 web.1       |   activesupport (4.1.8) lib/active_support/inflector/methods.rb:238:in `block in constantize'

13:54:34 web.1       |   activesupport (4.1.8) lib/active_support/inflector/methods.rb:236:in `constantize'

13:54:34 web.1       |   activesupport (4.1.8) lib/active_support/core_ext/string/inflections.rb:66:in `constantize'

13:54:34 web.1       |    () Users/stephenmarsh/.rvm/gems/ruby-2.1.5/bundler/gems/mongoid-60c4d942df30/lib/mongoid/relations/metadata.rb:575:in `klass'

13:54:34 web.1       |    () Users/stephenmarsh/.rvm/gems/ruby-2.1.5/bundler/gems/mongoid-60c4d942df30/lib/mongoid/relations/builders/referenced/in.rb:19:in `build'

13:54:34 web.1       |    () Users/stephenmarsh/.rvm/gems/ruby-2.1.5/bundler/gems/mongoid-60c4d942df30/lib/mongoid/relations/accessors.rb:43:in `create_relation'

13:54:34 web.1       |    () Users/stephenmarsh/.rvm/gems/ruby-2.1.5/bundler/gems/mongoid-60c4d942df30/lib/mongoid/relations/accessors.rb:26:in `__build__'

13:54:34 web.1       |    () Users/stephenmarsh/.rvm/gems/ruby-2.1.5/bundler/gems/mongoid-60c4d942df30/lib/mongoid/relations/accessors.rb:104:in `block (2 levels) in get_relation'

13:54:34 web.1       |    () Users/stephenmarsh/.rvm/gems/ruby-2.1.5/bundler/gems/mongoid-60c4d942df30/lib/mongoid/threaded/lifecycle.rb:125:in `_loading'

13:54:34 web.1       |    () Users/stephenmarsh/.rvm/gems/ruby-2.1.5/bundler/gems/mongoid-60c4d942df30/lib/mongoid/relations/accessors.rb:100:in `block in get_relation'

13:54:34 web.1       |    () Users/stephenmarsh/.rvm/gems/ruby-2.1.5/bundler/gems/mongoid-60c4d942df30/lib/mongoid/threaded/lifecycle.rb:84:in `_building'

13:54:34 web.1       |    () Users/stephenmarsh/.rvm/gems/ruby-2.1.5/bundler/gems/mongoid-60c4d942df30/lib/mongoid/relations/accessors.rb:99:in `get_relation'

13:54:34 web.1       |    () Users/stephenmarsh/.rvm/gems/ruby-2.1.5/bundler/gems/mongoid-60c4d942df30/lib/mongoid/relations/accessors.rb:187:in `block in getter'

Seems like constantize is looking for “User” when it should be looking for "CMS::User" ??

Figured it out, just needed to set:
Mongoid::History.modifier_class_name = 'CMS::User'
In my config/initializers/mongoid-history.rb
Pretty obvious, but would love to see this make its way into the documentation.

@stephenhmarsh can you please raise a PR to help us improve the docs?

@johnnyshields will do!

I get the same error and I don't have a User class in my project. Is it possible to use this gem without a User class?

@SebastianSzturo Does setting Mongoid::History.modifier_class_name = nil work? We should document it, too and/or add support for that.

Mongoid::History.modifier_class_name = nil is also not working. :(
I get the error ``uninitialized constant Modifier```. It seams like a modifier is necessary.

@SebastianSzturo Try writing a spec that reproduces this and the fix should be fairly trivial to skip the modifier logic on nil.

We still want this, maybe someone cares to help?


Enable the new model serialization for peering

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
API changes are not detected in this pull request.


Runtime: Fix rust local-lambda build step on windows #

When compiling rust lambda functions on Windows platform, there is bug when sst runtime handler for rust is trying to copy files into the artifacts folder.
Running cargo build on windows creates files with .exe extension.

Copying files into artifacts folder then failes because it cant find "main" file.
In deploy mode, there is no need to add ".exe" extension to "bootstrap" file since cargo lambda build is set up correctly to build with linux environment.
Discord thread

closes #3658

Taking a look!


Documentation: GCPSecretManagerConfigStore

Suggestion
Document the GCPSecretManagerConfigStore integration with all the necessary details that explain what the store is and how to use it.
Motivation

Introduces users to the ConfigStore.
Improves usability of the store by providing usage examples.
Improves the completeness of the integration package.

Context

Integration docs: https://cloud.google.com/secret-manager/docs
Example PR of a store doc contribution: #575

Kindly assign me this one .

All yours @Ritesh-Udgata


Added my first article for the year

Contributed to the awesome article collection by adding my first article for the year

Congratulations @Peacesandy! Merged.
Cheers to more!


Create Map Pool

To get us up and running it might be better to create a couple of pre-made maps rather than generating them, so I suggest we create 1-5 maps and save them into the project statically:
Map Editor Tool

This is related to https://github.com/2PacIsAlive/hard-time/issues/7, my dream is to have enough maps that we can make different maps available as you travel to different places in the world. I'm gonna see how many I can crank out later tonight!
I still like the idea of being able to move from one map to another from within a single location (e.g. the ? on the current 2 maps).
To accomplish this I am thinking we should have an array of maps for each location. The first map in the array will only have an exit, and the last map will only have an entrance. Taking an exit will move you to the next map in the array, and taking an entrance will move you to the former map in the array.
I'll see how many I can get done tonight before we jump on this idea because it might be totally unfeasible for our timeline haha

Linking maps together ought to be simple enough. We just need to add a "playerInitLocation" so we set the player's initial spawn point at a different point depending on where they enter the map from. Otherwise the map transitions ought to be the exact same mechanism.

as of 7a087359702c06ac1d0224862e37f827a8af16c6 all 9 earth maps are in place! or initial versions of them at least. each of the three cities (LA, rio, moscow) have 3 maps, and you can transfer back and forth between them using entrances and exits. the last room in each city has a treasure room


How to coordinate selfplay and train

Hi,
Excuse me. The code looks great and is very helpful! :) I have a question about machine setup:
I think there is two main loops running simultaneously. One is selfplay run by a lot of GPU machines; another is CNN training on the data generated by selfplay.
Which is faster? Which is waiting for the other? I mean if the selfplay is faster, it will generate 10k games first and then stop for the CNN trainer to converge; if the CNN training is faster, it will wait for the data to be enough before training to avoid overfitting?

The training is almost always 'waiting' for games from selfplay.  In an ideal situation, they are perfectly balanced; there are enough selfplay workers to make new data fast enough for the training job.
In practice, '10k' is a number arrived at by guessing from the numbers in the AGZ & AZ papers.  It could be it would work just fine with more or less games.  Also, in practice, there are other steps like performing validation, or gathering the new data and preprocessing it, or selecting the positions uniformly, that could become a non-negligible part of the pipeline.
Overall, it seems like the entire pipeline needs to be looked at holistically, and tracking the actual objective performance is more relevant; once that is accomplished then optimizing or making the pipeline more efficient becomes useful.
Hope this helps :)

Oh. Got it. Thank you! :)


Get binary azo-rhodo working with a carbon source that only rhodo grows on

for example, xylose, but you can use any biolog carbon compound that is + for rhodo and - for azo.

Binary growth where only Rhodo can consume a carbon source of xyl__D_m  is the goal.    Can you confirm that Azo is not consuming xyl__D_m and can you tell me what carbon source Rhodo is providing to Azo?

Congratulations, this counts as success!  Quick question,  do we know if Rhodo actually excretes gluconate under xylose conditions?  And if so, does Azo really eat it?  i.e. can we check the Azo Biolog and the Rhodo-Cyano metabolite exchange data to see if gluconate  is in there?

Lastly, do we know if Cyano is capable of secreting xylose if we were to replace the sucrose transporter with a xylose transporter?

@PBohutskyi ?


SecurityTokenSignatureKeyNotFoundException after rollover of signingcredential

Hi all,
We just rolled over our signing credential, we accidentally skipped one part of rolling over. This is what we did.
We moved from this code:
identityServerBuilder.AddSigningCredential(certificate1);

to this code, without first making certificate 2 a validation key.
identityServerBuilder.AddSigningCredential(certificate2);
identityServerBuilder.AddValidationKey(certificate1);

Now we see that logging out with an old token (from before the code deploy) provided via external identity integration with Google, provides us issues.
we see that the IdentityServerInteractionService, when requestiong the GetLogoutContext, is not providing us with the details that we expected, and therefore we can get the callback URL for our app back.
Now we see the exception "SecurityTokenSignatureKeyNotFoundException" (IDX10501: Signature validation failed. Unable to match keys: kid: '[PII is hidden]', token: '[PII is hidden]'.)
.in our app insights logging popping up. shouldn't adding the old certificate as validation key prevent this exception?
We've read up on the article of Brock Allen on the credential rollover, and we expected that the exceptions would stop after that 5 days passed, since he states that external identity providers possibly have 2-5 days of caching.
those days passed, but we still are unable to log out properly using the logout flow for our mobile app.
Is this normal? Just because we forgot one step in the flow?
Extra context:
our mobile app is using OIDCClient, which provides a logoutId on logging out. it redirects us to the browser on our mobile phone, and redirects us via the redirect URL that should come back via the interaction context. this is missing, therefore the flow of logging out on our app is broken for old tokens

Hi, you mean like I mentioned that we did? :) we added the first (old) certificate as a validation key.

Now we see that logging out with an old token (from before the code deploy) provided via external identity integration with Google, provides us issues.

Are you sending the google token to IdentityServer?

I'm asking the team that implemented it to give an answer to this question, so that I'm not giving any bad answers. Coming back to your question ASAP


Project Loom does not play well with synchronized, so WDYT of adding support for "forbid use of synchronized"?

In pgjdbc, we replace all synchronized with explicit Lock: https://github.com/pgjdbc/pgjdbc/pull/2635
I wonder if I could use forbidden-apis to avoid more synchronized keywords creeping in the future.

Good idea. But this would be an additional "feature" as it requires not to parse for forbidden methods calls, but just look at attributes of methods.

I have to check how to detect a synchronized block inside bytecode. For method declartion it is just access flag (as far as I remember).
Add some setting to enable it globally.
Make sure SuppressForbidden works.

Well, synchronized(something) would use monitorenter bytecode (e.g. https://asm.ow2.io/javadoc/org/objectweb/asm/Opcodes.html#MONITORENTER )
synchronized methods would indeed be coded as method modifiers.
On top of that, it would probably be great to include Object#wait, Object#notify, and Object#notifyAll into the forbidden set as they make sense only in case synchronized is used (they should be replaced with Condition#await, Condition#signal, Condition#signalAll).
I've no idea if synchronized methods or monitorenter could appear in synthetic code, or in the code generated by Kotlin, Scala, or the other compilers.
However, pgjdbc is Java-only for now, so it would be nice to just forbid

FWIW, the issue with using synchronized with virtual threads will be fixed in Java 24: https://openjdk.org/jeps/491


Ironic jobs

As a pull request owner and reviewers, I checked that:

[ ] Appropriate testing is done and actually running
[ ] Appropriate documentation exists and/or is up-to-date:

[ ] README in the role
[ ] Content of the docs/source is reflecting the changes

Why a new pull request? Didn't we have https://github.com/openstack-k8s-operators/ci-framework/pull/1163 already?


Wait for host to shutdown before marking service stopped

When the ApplicationStopping event is fired (either by SCM or the application), transition the service to StopPending. Then, wait in OnStop() until ApplicationStopped is fired, to keep the service in the StopPending state.
Task.Run is used in ApplicationStopping to avoid a deadlock because it waits for ApplicationStopped.
Addresses #1323

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

Code check failure, the reference assemblies need to be updated: "Generated code is not up to date. You might need to regenerate the reference assemblies or project list (see docs/ReferenceAssemblies.md and docs/ReferenceResolution.md)"

Thanks


RPC improve

Add bind address setting for RPC
Enforce HTTP Basic Auth for wallet operations

need core funcionality on https://github.com/neo-project/neo/pull/226

It should be implemented in plugins, I think.

Maybe this can implement it while we build a plugins system, what do you think?
Then should we move all wallet operations through RPC to a plugin?


Disposable e-mail domains

Hi, I've been using trumail for some time and it's doing a great job, one of the features that I used most is to check if an e-mail is disposable, why did you remove it?
Do you recommend any alternative to check this?

I removed it because the trumail package is meant to mainly be a powerful SMTP verification library. Therefore, I've slimmed down everything that is unrelated to smtp verification and moved all extra non-smtp verification logic to the https://trumail.io hosted API. I apologize for the trouble
There are several free disposable api libraries available on Mashape as alternatives. - https://market.mashape.com/explore?query=disposable email&page=1


Add a simple footer to the site bottom

Since the project uses html5, why not use the <footer> element?

Did that, thanks.


Test .github/workflows/lib-tests.yml

With a broken commit, the check fails.

With a non-broken commit, the check succeeds.

With a non-lib commit, the check doesn't run.


Edit rules to ignore Snyk PR's

https://github.com/freeCodeCamp/freeCodeCamp/pull/13680
depends on #3

@BerkeleyTrue Why the edit? So boring :smile:


[REQUEST] Implement Controller Support and Pairing, like Steam.

Is your feature request related to a problem? Please describe.
It is not related to a problem, it is only a feature request, to implement Controller Support and Pairing for Hydra Launcher, like Steam does.
Describe the solution you'd like
The solution to implement Controller Support for Hydra, is to pair and detect the controller connected to the computer, so when you start a specific game with the controller, it works with the game. You would have to choose a controller preset for that specific game you want to play, Steam has a similar thing that detects and pairs the controller to specific games, games that work well with controllers and other that don't have much compatibility, so you have to use an alternate input.
Describe alternatives you've considered
Maybe if there was a database of these controller presets for the game to work, we could pair and connect the controller and choose a specific preset for the game you want to play, effectivelly facilitating the input process, and if the game already works well with controllers, without the need of an alternate input (presets), the main controller preset for the compatible game would already be available to use from that database.
Additional context
No response

up!

This would be so good


build failed because cant find libRNSound.a

im trying to build my project but i got this error

clang: error: no such file or directory: '/Users/peyman/Library/Developer/Xcode/DerivedData/myApp-eooaseprzejzxbbmondxvpocasdl/Build/Products/Release-iphoneos/libRNSound.a'

im using RN : 55.4
im try react-native link and pod install
there are no error like this on the internet to find a solution
i found somthing new about error
soo error apear when im chosing generic ios devices

in xcode I think you can just go into your project, go to Build Phases (I think?), and remove and re-add libRNSound.a. I believe the reference to it is just broken. I havent done this with this module, but I did have to do it with something for an AR platform for react native and it was libFishhook.a here.


Validate that we don't overlap with the network service CIDRs.

Update validations to ensure we don't overlap with the cluster network CIDR settings.  Validate no overlapping on update to old network settings.  Various cleanups.

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes #
Checklist

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

/test e2e-aws

This was include the controller validation since we don't run the webhook any more
/close


community catalog: duplicate entries displayed

Description

Duplication only shows for people with editor access to the catalog, so its expected. You can see one of them has a lock icon (private catalog) and one does not


Fix jump link to only scroll effect so it doesn't happen on page urls, only jump link urls

Problem: every url that is clicked scrolls up to the top of the page, regardless of if it is a jump link or a normal page link.
Potential solution: code jump links so that they only apply to URLs with a # parameter in them, which is the standard HTML jump link format.
For example: https://climatetechhandbook.com/level-1#solution-frameworks is a jump link, whereas, https://climatetechhandbook.com/level-1 without the # parameter is a standard link.
@mzhanggg can you make it so only urls with a # parameter have the jump link scroll effect?

I did not mean to unassign this to you mzhangg, I was only reading trying to understand what you were trying to explain,


Suggestions for ghost highlighting

I love the new ghost-highlighting feature in the Dafny extension. This feature adds a gray background for statements that are ghost. I have two further suggestions/wishes for this mode.

I have found that lemma bodies are all grayed out. My first thought was that this is due lemmas always being ghost. However, in writing up this Issue, I'm finding that I can't always reproduce the situation. I have now written several lemma or least lemma declarations without their bodies being turned into gray, and I've also written some method bodies where the statements do turn gray (even for assignments to non-ghost out-parameters, which are definitely not ghost statements).
Here's one example:

So, my assessment is now that the feature is rather unreliable. I don't understand when it's recomputing this information or what to expect.

The other issue I have is selected code doesn't show up over the gray ghost highlighting. Usually, when I select some code, it lights up with a blue background. But when the code is displayed as ghost, then the background remains gray even when I select some code. This feels wrong to me as a user. I would like the blue selection highlighting to take priority over the gray ghost highlighting.

Thanks for reporting. I'm in favor of these changes too.

Thanks a lot for reporting.
It's definitely undesirable that the ghost information is not reliable, and even shows wrong information.
I'll try to have a look by myself. If anyone wants to give it a try, see below for things that came to my mind that might be helpful.
The decision whether something is marked as ghost or not is straightforward:
https://github.com/dafny-lang/dafny/blob/614425281b4374a47dbc824822728080ff4e5bd8/Source/DafnyLanguageServer/Language/GhostStateDiagnosticCollector.cs#L59-L62
The first thing I'd suggest to avoid marking lemmas as ghost unnecessarily, is to add a simple filter to the visitor implementation. Then we can avoid traversing down inside lemmas (and functions as well) and won't mark ghost statements inside these.
The thing about user interaction with code selection is also very undesirable. It might be possible to resolve this by changing the color of the ghost highlighting to a transparent one:
https://github.com/dafny-lang/ide-vscode/blob/9ff58873f16ceaa032e8478d6109e84e995c8a62/src/ui/ghostDiagnosticsView.ts#L8-L15


Migrates Job Scheduler plugin to OpenSearch modules

Description
This PR migrates the Job Scheduler plugin to OpenSearch modules.
Would be a massive task to attempt to PR a single commit of this so the way its broken down is:

First commit purely takes the job scheduler plugin from a sibling directory and moves it under modules/job-scheduler in core minus the .git directory.

Third commit refactors the build.gradle files for job scheduler and job scheduler SPI
Fourth commit adds the modules to the missing javadocs task as this was focused on migration.
Fifth commit moves the sample plugin to the plugins/examples directory and renames it/fixes up file/package paths.
Sixth commit calls the style linter to fix style issues.
Seventh commit adds the cron-utils dependency license files to the job scheduler spi license directory
Eighth commit fixes the breaking changes in job scheduler from the 2.0 upgrade
Ninth commit adds a plugin security policy
Rest of commits are some small styling/migration fixes

Unless we want to review the entire job scheduler plugin again, I'd recommend looking at the individual commits to see the work that was done to integrate the job scheduler plugin into the core repository.
Issues Resolved
https://github.com/opensearch-project/OpenSearch/issues/2534
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

I'd like to revive the conversation about merging this PR, and hear a strong opinion from @nknize @mch2 @andrross @kartg @reta and anyone else who cares to comment. Do we want this change in core?

A lot of the for/against discussion can be viewed in https://github.com/opensearch-project/job-scheduler/issues/147
IMO, this change should not go forward because "job scheduling" is not core functionality in a distributed search engine. The primary purpose of this feature is to be a building block for other plugins - on its own, it does not add any value. Since plugins are by nature optional, this feature cannot be considered essential.
The pain point driving this PR is that version upgrades are slowed because plugins are dependent on Job Scheduler upgrading before they can upgrade. In addition to seeing data to quantify "slow", I think we should consider tackling this with a different approach - given that Job Scheduler does not provide value on its own, is it really a plugin?
Can we decouple Job Scheduler enough so that it is not tied to core versions? Is it better modeled as a library that other plugins import?

I lost track of this PR due to so many other in flight issues. I wanted to circle back here and make sure this didn't go stale for much longer than it already has.
Personally, I don't have a problem moving this to the core repo if it makes sense. I think I'm missing a few key answers:

Is there a one to many relationship between this function and other plugins? (e.g., how many plugins depend on this as a core function today?)
Do we forsee this as an enabler for many other plugins?
Does it have to be a module? I think users might want the option to install this function only when needed.

To me, one criteria worthy of considering for promotion of a plugin from "second class" (external repo) to "first class" (core repo) is the number of plugins that depend on the plugin for base functionality. I don't think we should necessarily limit the entire core repository to "search engine" only functions; /server directory sure, but the modules, plugins, and libraries directories are specifically designed for situations like this to help minimize the "Dependency spaghetti" between external repos. If job scheduler is already a one to many dependency, then moving this to the core repo makes sense. We just need to be thoughtful about whether it's a module or a plugin and for that I always err on the side of plugin so we don't force users to install a plugin that consumers resources they'll never use.

I would second @nknize thoughts on enabling simpler dependency management as another criteria for core plugins, which likely is the case with job-scheduler. I think we should also have this clearly documented as a guidance for adding future module/plugins to core.
Also do we really need the complete implementation of job-scheduler to be in core, can we just have the abstract layers in core to simplify dependency management and have the actual implementation sitting outside it?

Is there a one to many relationship between this function and other plugins? (e.g., how many plugins depend on this as a core function today?)

Yes, there is a 1:M relationship. We have Index-Management, Anomaly Detection, Reporting using Job Scheduler. Alerting has an inbuilt Job Scheduler, which was the genesis of Job Scheduler as we saw the use case as a more generic one.

2. Do we forsee this as an enabler for many other plugins?

It can potentially be one - e.g Observability and Security Analytics will have use cases to get traces / security findings based on a time interval.

3. Does it have to be a module? I think users might want the option to install this function only when needed.

Open to being it under plugins directory.

To me, one criteria worthy of considering for promotion of a plugin from "second class" (external repo) to "first class" (core repo) is the number of plugins that depend on the plugin for base functionality. I don't think we should necessarily limit the entire core repository to "search engine" only functions; /server directory sure, but the modules, plugins, and libraries directories are specifically designed for situations like this to help minimize the "Dependency spaghetti" between external repos. If job scheduler is already a one to many dependency, then moving this to the core repo makes sense.

Couldn't agree more!

@kartg , @CEHENKLE , @dblock , Do you have any further questions on merging this PR?

Job Scheduler currently uses Service Provider Interface(SPI) design to interact with plugins like Anomaly Detection, Index-Management. If we are deciding to move Job Scheduler to core should the design still remain the same for interactions of the plugins with Job Scheduler and what impact will this design have on the latency?

@dreamer-89  we can close this PR in lieu of https://github.com/opensearch-project/OpenSearch/pull/5453 since we would want to move JS as a native plugin so that it can be installed optionally. Will let @joshpalis  confirm. Thanks

As the decision to relocate job scheduler into core as a native plugin (optionally installed) rather than a module (installed by default) has been finalized, closing this PR. An update on the effort to relocate job scheduler into core can be found here


SAMA5(D2) SPI speed is restricted by the driver

I have been investigating poor MTD performance with a GD25 memory on SPI0 of a SAMA5D27 processor.
Using LittleFS, dd was showing 37KB/s transfer speeds. I ruled out LittleFS - SmartFS was even slower.
The memory is set to run at 50MHz, but I was seeing only 10MHz, and long delays between transfers.
looking at arch/arm/src/sama5/sam_spc.c it seems the SPI interface is hard coded to be deliberately slow:

SCBR (Serial Clock Bit Rate) forced to have a minimum value of 9, when the datasheet says 1 should be the minimum
DLYBS (Delay from NPCS going active to first valid clock) forced to be 2us
DLYBCT(Delay between 2 consecutive transfers) forced to be 5us
SPI clock defaulting to using main clock (164MHz) whereas it could use the Peripheral Clock (492MHz) which limits the resolution of the actual frequency realisable

Changing these to the fastest allowable values results in a huge improvement in transfer speed - it's now 263KB/s.
BUT...is there a good reason why these very big values have been chosen? Should they not be configurable rather than hard coded, even?
I am aware there are other processors in the SAMA5 family (i.e. SAMA5D3 and SAMA5D4) so input from anyone who knows those would be welcomed, along with any general observations and suggestions on the best way to improve this?
As an aside, SPI DMA doesn't work for the SAMA5D2 - it uses "XDMAC" not "DMAC" so Kconfig settings get disabled and the driver never works out the right DMA setup (which would be wrong for this device anyway!).
I am very happy to work on the fix and a PR after some feedback.

FYI - just "hard coded" XDMA to work and the dd transfer speed is now...
730 KB/s !!!!!!!!

No comments...working on PRs but my board has died and needs fixing...but I'll close pending PRs in the next few weeks which will sort SPI DMA for this chip, and add spi_set_delay functionality too.


[Bug Report] Unexpected result during solving multi-line conflicts

VSCode Version: 1.43
OS Version: Fedora

Steps to Reproduce:

use git pull to pull a remote repository, which can trigger a lot of conflicts in a source file(e.g, helloworld.c), and the conflicts distributes in different lines.
solve the conflict using vscode, you have three choices to select: keep HEAD, incoming or both.
after you choose a solution for the first conflict, you click the selections for the second conflict, you will find the second will not be solved as you imagine. For example, I choose keep incoming for the second conflicts, it just insert >> or ==== in the end of original text, and the conflict still exists, except some useless contents are inserted.

Does this issue occur when all extensions are disabled?: Yes

Screenshots or code sample would help...