Error During Installation of "@micro-lc/orchestrator"

Description
I encountered an issue while installing "@micro-lc/orchestrator" version 2.4.1. My project uses pnpm. The installation process warns about a 404 error for the "ajv-format" package.
Environment
I'm using micro-lc version 2.4.1
I'm serving configurations using @micro-lc/orchestrator at version 2.4.1
Minimal Reproduction

Create a new project using pnpm.
Attempt to install "@micro-lc/orchestrator" version 2.4.1.
Observe the warning about the 404 error for the "ajv-format" package.

Additional context
Error with pnpm

It appears that the peer dependency is specified as "ajv-format": ">=2.1.1" in the "@micro-lc/orchestrator" package.json file, as seen here.
  "peerDependencies": {
    "ajv": ">=8.11.0",
    "ajv-format": ">=2.1.1",
    "es-module-shims": ">=1.5.3"
  },

Suggested Solution
Update the peer dependency from "ajv-format" to "ajv-formats" in the "@micro-lc/orchestrator" package.json file.

Thanks for the heads-up! Fixing soon

Thanks for the heads-up! Fixing soon

Much appreciated 🙏

the<EMAIL_ADDRESS>patch for the orchestrator should fix the issue


Set Kibana SERVER_BASEPATH

Please reference the issue this PR is fixing, or provide a description of the problem addressed.
Resolves #2350
The change was introduced in 61d191da89c1868d6a2d45ad63df18b187d4ec61
Also verify you have:

[x] Read the contributions page.
[x] Submitted the CLA form, if you are a first time contributor.

@s12v will this continue to work if i use port-forwarding instead of proxy?

I think @balchua is right. If we set the SERVER_BASEPATH going to <ClusterIP>:5601 or trying microk8s.kubectl port-forward  -n kube-system   service/kibana-logging 8181:5601 will not get you to kibana. You get the error:
{"statusCode":404,"error":"Not Found","message":"Not Found"}

Maybe we should update our docs to reflect this.

@s12v I updated our docs to reflect the difference in accessing kibana in recent releases. Feel free to re-open the PR and the respective issue if you have a better approach to the problem at hand.
Thank you.


Allow -r in NODE_OPTIONS

I don't have a good handle on how discord ships the native client, but on or around the 9.x upgrade, IsPackagedApp started being true which means the client no longer accepts any useful NODE_OPTIONS options.

we do not support setting node options, gus.


Dimming the underlying view

Could we configure whether the underlying view is being dimmed or not?

I too would like to be able to not dim the underlying view.

Thank you for your contributions! This has been fixed as of #26.


Removing subshell for compatibility with Jenkins

Modifying a test script to make it more compatible with Jenkins

@cgeoffroy I had disabled you script in Jenkins yesterday. Its now enabled again. So the test should run again.

test this please

comment trigger does not seem to work. maybe you can create a small commit?

The test is stable on Jenkins now


how to the prometheus outside of kubernetes need to monitor kube-prometheus node-exporter

my prometheus config

job_name: "kube-node-exporter"
static_configs:
- targets:
- "<IP_ADDRESS>:9100"
- "<IP_ADDRESS>:9100"
- "<IP_ADDRESS>:9100"
- "<IP_ADDRESS>:9100"
and node-exporter deployed by  kube-prometheus,but my prometheus out of the k8s cluster cannot resive node-exporter data,how can i config this to resive data?

From the https://github.com/prometheus-operator/prometheus-operator/issues/4520.
“I see that node exporter runs on the host network by default: https://github.com/prometheus-community/helm-charts/blob/main/charts/prometheus-node-exporter/values.yaml#L98. I assume the reason is so that the exporter can discover information about all network interfaces on that node. Without host networking, it would only see the virtual interfaces of the container in which it runs.
If you need additional security in place, you can look into network policies and restrict which pods can scrape the metric endpoints. Maybe such a network policy should be created by default, but that's really an issue for the community helm charts repository.”
So the hostnetwork of node exporter is necessary.

Information for folks who find this issue in the future:
Kube-prometheus shipped from this repository runs node_exporter with kube-rbac-proxy as a sidecar and only authenticated requests are allowed. Additionally this project also ships NetworkPolicies for node_exporter. Both of those features are not present in helm chart project named kube-prometheus-stack.


Touch UI test - Err: LND is locked

Built a new SD-card manually from master on my RPI4 and restored a previous blockchaindata and LND directory.
After activating finishing syncing and activating the touchscreen I have an error message when pressing the  Node or Invoice button saying:
Err: LND is locked
LND is unlocked manually (no autounlock currently) and works fine.
lncli getinfo works, gives the full output.
@frennkie or anyone can you reproduce this?

Can you check the log for hints: /home/pi/blitz-tui.log

Nice, it has a log!
Could not make much out of it though.
Here is the full log:
$ cat /home/pi/blitz-tui.log | nc termbin.com 9999
https://termbin.com/w68f

Now uninstalled and reinstalled from the SERVICE menu.
Initially it showed the Node URI, but gave an error about channels not open despite 3/3 were active on the status  screen.
Couple of seconds and it all works!
Recorded the second logs of the second install too:
$ cat /home/pi/blitz-tui.log | nc termbin.com 9999
https://termbin.com/dyge
I attribute the problem to the fact that I have migrated to a backed up LND directory.
It seems the reinstall sorted the problem.
Thank you for your input, being able to look at the specific logs helps a lot!
Will close this now.


Bug DFBUGS-936: [release-4.15] css-tools: Improper Input Validation causes Denial of Service via Regular Expression

Issue: https://issues.redhat.com/browse/DFBUGS-936

/jira refresh

/jira refresh

/approve
/lgtm

/hold

/hold cancel

/override ci/prow/odf-console-e2e-aws


what is the shape of SwitchTransformer's input

the code comments shows it should be (seq_len, batch_size, d_model), but in the experiment.py, the input is the output of nn.embedding, so its shape may be (batch_size, seq_len, d_model) ?

Input to the embedding layer is also in the shape of (seq_len, batch_size, d_model). We use sequence first form everywhere in switch transformer, following torch.nn.LSTM.


Extract datamodel to json

Added CLI features to extract the datamodel objects and print them to json in a subfolder bam_data_store/datamodel/artifacts/.

I've merged the export-to-excel implementation as well

Pull Request Test Coverage Report for Build<PHONE_NUMBER>9
Details

34 of 171 (19.88%)  changed or added relevant lines in 8 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-34.3%) to 47.419%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

bam_data_store/datamodel/property_types.py
0
2
0.0%

bam_data_store/metadata/entities.py
5
7
71.43%

bam_data_store/metadata/definitions.py
6
10
60.0%

bam_data_store/datamodel/collection_types.py
0
7
0.0%

bam_data_store/utils/utils.py
23
34
67.65%

bam_data_store/cli/entities_to_json.py
0
35
0.0%

bam_data_store/cli/cli.py
0
36
0.0%

bam_data_store/cli/entities_to_excel.py
0
40
0.0%

Totals

Change from base Build<PHONE_NUMBER>0:
-34.3%

Covered Lines:
147

Relevant Lines:
310

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>6
Details

33 of 169 (19.53%)  changed or added relevant lines in 8 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-34.3%) to 47.403%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

bam_masterdata/datamodel/property_types.py
0
2
0.0%

bam_masterdata/metadata/entities.py
5
7
71.43%

bam_masterdata/metadata/definitions.py
6
10
60.0%

bam_masterdata/datamodel/collection_types.py
0
7
0.0%

bam_masterdata/utils/utils.py
22
33
66.67%

bam_masterdata/cli/entities_to_json.py
0
35
0.0%

bam_masterdata/cli/cli.py
0
36
0.0%

bam_masterdata/cli/entities_to_excel.py
0
39
0.0%

Totals

Change from base Build<PHONE_NUMBER>2:
-34.3%

Covered Lines:
146

Relevant Lines:
308

💛  - Coveralls


Error: do not understand webhook version "1", only version "4" is supported

Webhook is working but receiving below error.
Used prom/alertmanager:v0.23.0 Image to run alertmanager as container.
{"file":"main.go:36","func":"main","level":"info","msg":"init exporter"}
{"file":"main.go:52","func":"main","level":"info","msg":"starting http server on <IP_ADDRESS>:9097"}
{"file":"alertmanager2es.go:147","func":"HttpHandler","level":"error","msg":"unexpected end of JSON input"}
{"file":"alertmanager2es.go:155","func":"HttpHandler","level":"error","msg":"do not understand webhook version \"1\", only version \"4\" is supported"}
{"file":"alertmanager2es.go:155","func":"HttpHandler","level":"error","msg":"do not understand webhook version \"1\", only version \"4\" is supported"}
{"file":"alertmanager2es.go:155","func":"HttpHandler","level":"error","msg":"do not understand webhook version \"1\", only version \"4\" is supported"}
{"file":"alertmanager2es.go:155","func":"HttpHandler","level":"error","msg":"do not understand webhook version \"1\", only version \"4\" is supported"}
{"file":"alertmanager2es.go:155","func":"HttpHandler","level":"error","msg":"do not understand webhook version \"1\", only version \"4\" is supported"}
{"file":"alertmanager2es.go:155","func":"HttpHandler","level":"error","msg":"do not understand webhook version \"1\", only version \"4\" is supported"}

alertmanager .yml
route:
  receiver: 'alertmanager2es'
  repeat_interval: 2h
  group_wait: 10s
  group_interval: 10s
  group_by: [ alertname ]
  routes:
  - receiver: 'mail'

receivers:
  - name: 'mail'
    email_configs:
    - to: 'mailAddr'
      send_resolved: true
  - name: 'alertmanager2es'
    webhook_configs:
    - url: 'http://IP:9097/webhook'

Docker
alertmanager:
    image: prom/alertmanager:v0.23.0
    container_name: prom_alert_manager
    restart: always
    networks:
      - analytics
    ports:
      - "9093:9093"
    volumes:
      - "./alertmanager:/config"
      - alertmanager-data:/data
    command: --config.file=/config/alertmanager.yml --log.level=debug

The webhook should be version 4 as alertmanager onlys ends the value as 4: https://github.com/prometheus/alertmanager/blob/main/notify/webhook/webhook.go#L92
Not sure why you send out content as version 1 🤔

I was sending alerts through grafana alertmanager so the version was 1.
From prom alertmanager version seems to correct 4.


Fix up option names in EMTC

The option names are CVA1 and CVA1 and SELECT1 which aren't really informative names.

Need to replace placeholders with accurate units of measurement options and then account for them in the math portion


Add icon for .editorconfig files

currently, on my usual setup, I'm missing an icon for .editorconfig files. Maybe something similar to .project icon would be fine.

ok :+1:

update

Cool, it's a good thing that we are doing our best to support Brackets. Thanks


How to set a suitable config for concurrency?

Hello, I am working with grobid, and i tried multi parameters of concurrency and grobid python client's parameter "n".
I found that it is not a accuracy value to find the most suitable paratemers. And the reference manual have only the two client-grobid server and send client. Set the parameters 'concurrency' and 'n' according to the CPU limitations of the respective machine.
So the environment:
grobid server and python-client in a server, what should I set up the parameters 'concurrency' and 'n' ?
I tried multi parameters and didn't find obvious differences.

Hi @thejiangcj did you see this documentation page? https://grobid.readthedocs.io/en/latest/Frequently-asked-questions/#could-we-have-some-guidance-for-server-configuration-in-production
AFAIK after you establish the concurrency parameter on the server, the client should follow using the same value.

Hi @thejiangcj did you see this documentation page? https://grobid.readthedocs.io/en/latest/Frequently-asked-questions/#could-we-have-some-guidance-for-server-configuration-in-production
AFAIK after you establish the concurrency parameter on the server, the client should follow using the same value.

Yes, I see. However, it based on the server and the client are different machines?(not sure) I mean if the server and the client are the same one machine, whether concurrency parameter should equal to the machine's threads?
For example, if the machine has 16 threads, then there will be tow choices:

grobid yaml's concurrency set to 16, and the python's n is 16, which https://grobid.readthedocs.io/en/latest/Frequently-asked-questions/#could-we-have-some-guidance-for-server-configuration-in-production describe.
grobid yaml's concurrency set to 8, and the python's n is 8.  In one machine, every task needs one thread, so divided by 2.

@thejiangcj AFAIK You don't need to divide by 2 when the client runs on the same machine as the server. The client's charge on the CPU is lower than the server.

@thejiangcj AFAIK You don't need to divide by 2 when the client runs on the same machine as the server. The client's charge on the CPU is lower than the server.

Thank you for your answer very much.


Feature schemas - object id

Pliers now returns an object id, instead of prepending feature names with face id. Update feature schema accordingly.

Currently, just adding new instances into db without distinguishing them.

Add object ID column to query


Mostly works on Linux!

Hi, thanks for this great application!
I know you intended it to work just on Windows, but I had a quick go at running it on Linux and after just disabling a few lines of the windowmanager code I got it working (Flutters superpower!), though I think it also needs a few tweaks for how it handles saving and then loading previous sessions as I then got a few more errors from loadOlderSessions() when I re ran the app a second time. I'm a bit flat out with other projects at the moment, but I'd like to contribute a PR with the fixes required to run on Linux (I tested on Ubuntu 22.04) if you would be interested in accepting that?

Cool, sounds very good. If you don't work on it, maybe I'll try to implement it myself. Thanks for the efforts in advance

Cool, sounds very good. If you don't work on it, maybe I'll try to implement it myself. Thanks for the efforts in advance


chore(main): release 0.1.2

:robot: I have created a release beep boop
0.1.2 (2023-10-03)
Features

event page seo (7e64a79)
graphql proxy (3166404)
robots.txt (84152a4)

Bug Fixes

broken tests (518e7a8)
event loader (2b35128)
linkConfig (151c7ba)
renovate semantic commits (56f6c4a)
update snapshot (3f8df96)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/crea-orkest/crea-public/releases/tag/v0.1.2 :sunflower:


Find new hosting solution

Heroku free tier phased out - application no longer runs

reupload it in replit.com instead of heroku

I converted the project to Cloudflare Pages - https://kimiquotes.pages.dev/


BUG: Datadog Agent Rate Limiting Logs

Description
We are seeing rate limiting error messages form our Datadog Agent logs. This ticket seeks to investigate and remediate the issue.

[x] Ticket is understood, and QA has been contacted (if the ticket has a QA label).
[ ] This work is added to the sprint review slide deck (key win bullet point and demo slide)

Steps to Reproduce

Navigate to Datadog logs: <env>-notification-api-datadog-log-group
Search for UTC | TRACE | ERROR to view the log items in question

Impact/Urgency

Low Impact
This does not impact any external clients, but does impact our ability to view logs (assuming this causes us to lose log items). Additionally, this seems to be happening in prod.
Medium Priority
Despite impact being low, this should be prioritized. It's important to trust our ability to log.
Expected Behavior

[ ] The log items pictured above would not be present (i.e. our logs would not be rate limited)

QA Considerations

Additional Info & Resources

I set logs to debug in dev and did not see any real pattern causing this. Some brief searching online pointed to the fact that it's because of the DD url we use (gov URL). I think the next step here is to open a support ticket with Datadog to get them to help us debug.

I reached out to support and they think that the root cause of the issue is from a misconfiguration in the default settings. The image below shows that two telemetry env vars are set to true by default, but those features are not enabled in a DD government cloud environment. DD support recommended we set those to false, but not until they do further investigation today.

https://docs.datadoghq.com/tracing/configure_data_security/?tab=environmentvariables&site=gov#telemetry-collection


Dynamic provisioner for Hostpath

Hi,
I am interested in a hostpath provisioner that can work with StatefulSet with replica > 1. I had a conversation in slack api-machinery room. They pointed me to this project. Here is my conversation: https://github.com/appscode/k8s-addons/issues/14#issuecomment-283732665
I am new to writing my own PV provisioner. Do you think what I am asking for is possible? How do I take the demo hostpath provisioner in this repo and make that a proper one.
Thanks.

Yes, I think it's possible. Don't know how easy it will be though.
First consider that if you want the hostpath provisioner to handle pre-creating + deleting directories (MkdirAll & RemoveAll) on the host when corresponding PVs are created + deleted (with reclaim policy Delete), an instance of it will need to run on every node and mount every hostPath. And the logic in Delete will have to be improved.
If you don't care about that, if you are willing to handle cleaning up PVs' data yourself (effectively reclaim policy Retain), then you can throw away the assumption that each hostPath provisioner needs to actually mount its node's hostPath. So you can run just one hostpath provisioner for the whole cluster that just creates PVs and ignores creating/deleting directories. You will need to remove the RemoveAll and MkdirAll and such from the code.
Now, the hard part, the scheduling. tbh I don't know much about how to achieve this but I believe you have to extend the scheduler to be aware of those node hostname labels on the PV clayton is talking about. If you go with the first option I said where you have to run an instance of hostPath provisioner on every node, then obviously each provisioner labels its PVs with the node it's running on. If you go with the second option, then I guess you can just round-robin.

Also pvDir is hardcoded,you'll want to change it https://github.com/kubernetes-incubator/external-storage/blob/master/docs/demo/hostpath-provisioner/hostpath-provisioner.go#L59
Plus the identity is not very useful as-is, if you understand the principle of it then you can remove/improve it if you want.

@wongma7 , thanks for the detailed explanation. I have read the code mostly. I think I understand your comments regarding retention policy, I think those can be made parameterized. Users can use them based on parameters passed to StorageClass. For one more they can use Deployment for a singel pod. In the other mode, they can run DaemonSet and manage host paths.
Regarding Scheduling, I am also new to this level of details. I read the articles:

https://github.com/kubernetes/community/blob/master/contributors/devel/scheduler.md
https://github.com/kubernetes/community/blob/master/contributors/devel/scheduler_algorithm.md

From these articles I don't see any mention of default scheduler picks nodes based on label of PV. It is possible to write custom scheduler. But that raises the level of complexity. I will as in sig-scheduler google groups.

Yes you can do whatever you want re:retention policy, making it an SC parameter sounds good. Note that the controller will always pass to Provision 'options.ReclaimPolicy=delete" but you can ignore it,  it's only because upstream hasn't decided the "official" way to do retention policy yet. But again yeah if you want to set it to Retain and do the 'Deployment' style thing then sure why not.
RE: scheduler, please also check out https://kubernetes.io/docs/admin/multiple-schedulers/ . I believe you need write a predicate that looks at a pod->PVC->PV node label to determine which node the pod can be scheduled to. It doesn't look too complex but yeah, hostPath PV support is nonexistent in kube so you may have to write a scheduler and deploy it alongside the default scheduler. (Or patch the existing scheduler but I believe that's way less desirable.)

It doesn't look too complex but yeah, hostPath PV support is nonexistent in kube so you may have to write a scheduler and deploy it alongside the default scheduler. (Or patch the existing scheduler but I believe that's way less desirable.)

The existing scheduler will work fine as-is as long SS are not scaled up after scaling down. Say I have a SS with replica =3 (also uses PV). Now, later I reduce # of replicas to 2. This deleted the pod-2. Then if I increase the replicas to 3, I see that the original PVC, if exists, will be reused. If this is a required behavior, this is not possible without extending the default scheduler. Do you know who can give me  a definitive answer?

@wongma7 , regardless of the scheduler issue do you think the hostpath provisioner can be moved from demo to a supported provisioner?

I found a new proposal for local storage management: https://github.com/kubernetes/community/pull/306

Yes, it's coming though it will be a while (another release or two?) before it is a reality.
In the meantime I'm reluctant to make the hostpath provisioner any more official.  Prs are always welcome but the scheduling issue unless solved will make it hard to use in typical clusters.

Yeah. At least another 6 months to wait for official solution. I think we want something sooner. I have read the scheduler code and I think the actual change necessary is fairly simple. Currently default scheduler set PodSpec.Nodename once scheduling decision is made. Custom scheduler also need to apply the scheduler.beta.example.com/nodename:<nodename>  on PVs that can bound (directly or via PVC). During the filtering process, I need to check this in addition to checking PodSpec.NodeName.
There is an edge case. Say SS was reduced from replica = 3 to replica=2. Then the node where replica 3 was scheduled originally was removed from cluster. The correct action in this scenario will be left to the user via scheduler.beta.example.com/reassign-missing-node:true (default false) annotation on PodSpec. Scheduler can either fail to schedule the pod or reassign to a new node. If scheduler fails to assign the pod, then user can manually fix the underlying issue, remove the nodename annotation from PV and then reschedeule this pod.

So if we implement this, we can use hostpaths across cluster as a PV but without scheduling pod guarantees, isolation etc. of "local persistent volumes" at kubernetes/community#306 ?
My only priority on coming local PV is

defining PVC with my yamls as "local" without knowing how underlying PV achieve that (works in bare metal cluster, minikube...)
support for match labels of PVC to try to bind used PV before
and use node's local ssd or hdds
having durability (retain)
without installing anything to host OS, install over just kubernetes
when we get volume through PVC, we shouldn't deal with permissions like host path wants user to be root or needs some hack

I am not in hurry for isolation, resource limitations, security, ephermal storage aspects of coming proposal.
I would like to contribute once our goals here is clear because we don't want to wait for local PVs streamlined

@thenamli , I have started here from v1.5.4 tag: https://github.com/appscode/kubernetes/commits/hostpath
So far I have figured out how to build and push the binary. My docker image : https://hub.docker.com/r/appscode/hostpath-scheduler/tags/

/cc: @sadlil, @aerokite

reuse of a PVC/PV after a SS is scaled down and up is expected behavior as I recall.

@thenamli, I have got a bare bones implementation in place. Code compiles. I need to do actual testing. If you want to do a code review that will be handy.

So apparently there may be a way to co-opt the zone predicate of the scheduler to get hostPath PVs working...disclaimer this is extremely hacky, the zones annotation are still in beta to begin with, there's no guarantee that if this works now it will continue to work later, and you try this at your own risk.

label each node with its own "failure-domain.beta.kubernetes.io/zone"
label each PV your provisioner creates with a  "failure-domain.beta.kubernetes.io/zone"
when your statefulset creates PVCs asking for your provisioner's PVs the scheduler respects the label and schedules the statefulset pods to their respective PVs' "zones" aka nodes.

So again, this is extremely hacky and my official recommendation is still to write & use your own scheduler (which is already laxer than upstream's official recommendation to wait patitently for them to implement local storage). But thought it was interesting and worth sharing. :)

Thanks @wongma7 . I think writing scheduler might be the best option. Unfortunately, the new official solution for local storage will not solve my problem :( https://github.com/kubernetes/community/pull/306#issuecomment-286571242

@TamalSaha I read your messages there in local PV. Unfortunately, every usage scenario outside of gce and aws seems hacky at best.
First I thought I can contribute k8s to get better k8s support on bare metal. Neither contributing to mainstream k8s nor having own scheduler doesn't give clear and complete solution in the near future. At least it will take 1 year for k8s to mature on persistent storage area.
I am still looking forward to contribute k8s in this area.
So I ended up thinking using network storage service of our bare metal provider and writing a provisioner for it soon.

As a metaphor, you are on the business of selling shoes.  Then you realize your factory needs more electricity.
Then you realize dam nearby is not enough and people are building a new nuclear reactor for this near the lake. Then you found out that nuclear reactor have some problems for your needs.
At the end, you find yourself at the situation where you are producing coolant systems, control rods, etc. for nuclear reactor when you just want to sell shoes at first :)

So I ended up thinking using network storage service of our bare metal provider and writing a provisioner for it soon.

If you would share what you come up with that will be great!
Btw, I smiled at your metaphor out of pain. This is most definitely how we became contributor to many open source stuff.

folks, https://docs.google.com/document/d/1so67pZPtBwv3uBg9d3pk4VLzfn9qtuZrbauv1DnNDSk/edit?ts=58dd9c72#heading=h.syg5p31g5672 may interest you as well.
It won't have dynamic provisioning in the first phase (1.7), but if you want to steer it in the right direction I encourage you to comment!
Seems there is a lot of movement around local storage :)

I don't have read access on this file.

@TamalSaha join/subscribe to the sig-storage mailing list, the original post is here https://groups.google.com/forum/#!topic/kubernetes-sig-storage/mYZ7hTmOO7U

Until dynamic provisioning is not in upstream I continued @TamalSaha work and modified example hostPath provisioner to support multiple storage classes: https://github.com/nailgun/k8s-hostpath-provisioner
There is also custom scheduler based on @TamalSaha work but more simple because it depends on this custom provisioner

Awesome @nailgun !

Base don my conversation with @msau42 , it seems that the new Local PV will eventually address this use-case. I am looking forward to that. Closing this one.


Build failing on Ubuntu 14.04.3 with Emscripten 1.34.8

I've installed Emscripten 1.34.8 and compiled the "Hello, world" tests, which work fine.
I then cloned your repo, created a build directory, moved into it and then issued: "python ../build.py build"
I eventually get the following error:
Linking motor2d.js
/home/andrew/dev/javascript/emsdk_portable/clang/tag-e1.34.8/build_tag-e1.34.8_64/bin/opt: /tmp/tmpQpBz4S/motor2d.bc: error: Could not open input file: No such file or directory
Traceback (most recent call last):
  File "/home/andrew/dev/javascript/emsdk_portable/emscripten/tag-1.34.8/emcc", line 1255, in <module>
    final = shared.Building.llvm_opt(in_temp(target_basename + '.bc'), llvm_opts, DEFAULT_FINAL)
  File "/home/andrew/dev/javascript/emsdk_portable/emscripten/tag-1.34.8/tools/shared.py", line 1412, in llvm_opt
    assert os.path.exists(target), 'Failed to run llvm optimizations: ' + output
AssertionError: Failed to run llvm optimizations:
Failed

Full output here: https://gist.github.com/buntine/2130ba026308b56cbf6e
Have I missed something?
Thanks!

Make sure you have clang installed. I guess it's something like : sudo apt-get install clang

Thanks for the response.
I installed clang from ubuntu repositories, but same error.
It looks like it's using the clang that emscripten built for me?

Have you compiled/installed : emscripten-fastcomp?

This one: https://github.com/kripken/emscripten-fastcomp ??
No, do I need to?

Yeah you need that one in order to transform cpp code into js.

Yep, I already have emscripten installed. See above. I've compiled the cpp and c examples to JS on my local machine. My emscripten is working correctly.


Not working dialogService.ShowOpenFileDialogAsync inside of FluentAvaloniaUI NavigationView

Hi,
I have tried to learn  AvaloniaUI  and came across an issue with these common file/folder dialog boxes. Finally I tried to create a test app from scratch again to test it, where I could reproduce it (see the screenshot).
The app has utilized the both message box an the file/folder dialogs and the message box works well for the both main window view model and view model navigated using  FluentAvaloniaUI NavigationView.
However, the common file/folder dialog boxes works only in the MainWindow view model, not in the  view model navigated using FluentAvaloniaUI NavigationView, which end up with the ArgumentException, "No view found with specified ownerViewModel of type AvaloniaDialogsTest.ViewModels.Category1ViewModel."
Thinking (not so deeply :) if one kind of dialog work for both cases and the second one only for one case - sounds like an insufficient handling of such situation or a bug.
But it is not so easy - I can see that documentation told about possibility to use various pre-prepared view locators.
Well, for me it is not so easy to see which ViewLocator to use or how implement a custom one for this special case (having  common file/folder dialog boxes in both main view model and in viewmodel navigated from it or at least for the navigated  view models).? Could you please help?
some details: (if a need, I could attach the whole test app solution ):

I am using AvvaloniaUI 11.0.4, FluentAvaloniaUI 2.0.4(, CommunityToolkit.Mvvm 8.2.1), MvvmDialogs.Avalonia.MessageBox, MvvmDialogs.Avalonia.Fluent 2.0.0, Splat 14.7.1

the main is calling BuildAvaloniaApp().StartWithClassicDesktopLifetime(args);

App.Initialize() part:
build.RegisterLazySingleton(() => (IDialogService)new DialogService(
new DialogManager(
viewLocator: new ViewLocator(),
dialogFactory: new DialogFactory()
.AddMessageBox()
.AddFluent(FluentMessageBoxType.ContentDialog)),
viewModelFactory: x => Locator.Current.GetService(x)));
      // manually register the view models
      build.Register(() => new NavViewModel());
      build.Register(() => new MainWindowViewModel(resolver.GetRequiredService<IDialogService>(), resolver.GetRequiredService<NavViewModel>()));

call of the Category1ViewModel(resolver.GetRequiredService())  from the NavViewModel()

the  ViewLocator inherits from your ViewLocatorBase based on your docs  (also tried some tweaks there but without any success)

The exception stack trace - (can see it is a kind of  StartWithClassicDesktopLifetime)
at HanumanInstitute.MvvmDialogs.DialogManagerBase1.<>c__DisplayClass30_01.<b__0>d.MoveNext()
at HanumanInstitute.MvvmDialogs.DialogManagerBase1.<ShowFrameworkDialogAsync>d__301.MoveNext()
at HanumanInstitute.MvvmDialogs.DialogServiceExtensions.d__3.MoveNext()
at HanumanInstitute.MvvmDialogs.DialogServiceExtensions.d__2.MoveNext()
at AvaloniaDialogsTest.ViewModels.Category1ViewModel.d__7.MoveNext() in C:\Users\mr\source\repos\my\UI\Avalonia\AvaloniaDialogsTest\AvaloniaDialogsTest\ViewModels\Category1ViewModel.cs:line 67
at AvaloniaDialogsTest.ViewModels.Category1ViewModel.d__6.MoveNext() in C:\Users\mr\source\repos\my\UI\Avalonia\AvaloniaDialogsTest\AvaloniaDialogsTest\ViewModels\Category1ViewModel.cs:line 48
at System.Threading.Tasks.Task.<>c.b__128_0(Object state)
at Avalonia.Threading.SendOrPostCallbackDispatcherOperation.InvokeCore()
at Avalonia.Threading.DispatcherOperation.Execute()
at Avalonia.Threading.Dispatcher.ExecuteJob(DispatcherOperation job)
at Avalonia.Threading.Dispatcher.ExecuteJobsCore(Boolean fromExplicitBackgroundProcessingCallback)
at Avalonia.Threading.Dispatcher.Signaled()
at Avalonia.Win32.Win32Platform.WndProc(IntPtr hWnd, UInt32 msg, IntPtr wParam, IntPtr lParam)
at Avalonia.Win32.Interop.UnmanagedMethods.DispatchMessage(MSG& lpmsg)
at Avalonia.Win32.Win32DispatcherImpl.RunLoop(CancellationToken cancellationToken)
at Avalonia.Threading.DispatcherFrame.Run(IControlledDispatcherImpl impl)
at Avalonia.Threading.Dispatcher.PushFrame(DispatcherFrame frame)
at Avalonia.Threading.Dispatcher.MainLoop(CancellationToken cancellationToken)
at Avalonia.Controls.ApplicationLifetimes.ClassicDesktopStyleApplicationLifetime.Start(String[] args)
at Avalonia.ClassicDesktopStyleApplicationLifetimeExtensions.StartWithClassicDesktopLifetime(AppBuilder builder, String[] args, ShutdownMode shutdownMode)
at AvaloniaDialogsTest.Program.Main(String[] args) in C:\Users\mr\source\repos\my\UI\Avalonia\AvaloniaDialogsTest\AvaloniaDialogsTest\Program.cs:line 12
The test app screenshot:

If you want to show from a ViewModel that is not the main window, then you need a "Owner" property on that ViewModel holding a reference to the parent ViewModel.
Then you'll show it using Owner.

You might run into the problem that you get the View as a Control, and not as a TopModel. If that's the case, then you cannot set a regular Control as a window owner.

I'm having this issue too, and still get No view found with specified ownerViewModel of type even if I pass the MainViewModel.
I started with an app where MainViewModel/MainView was the main and only control/viewModel. Dialog prompting worked. Then I extract a bit of it into a separate UserControl - so within MainView, I now have i.e.
<local:HomeTabView>
  <local:HomeTabView.DataContext>
    <local:HomeTabViewModel/>
  </local:HomeTabView.DataContext>
</local:HomeTabView>

And whereas in MainViewModel I previously had:
var result = await _dialogService.ShowOpenFileDialogAsync(this, settings);

I get the error, so I change to:
var result = await _dialogService.ShowOpenFileDialogAsync(App.MainViewModel, settings);

where in App.cs, MainViewModel is just a static property that saves the viewmodel used in:
DialogService.Show(null, MainViewModel);

However, whether I pass App.MainViewModel or this to _dialogService.ShowOpenFileDialogAsync in HomeTabView, it throws that error. If I call _dialogService.ShowOpenFileDialogAsync from MainViewModel, it works. I also tried adding an Owner property to HomeTabViewModel as suggested, and setting it to App.MainViewModel, but the result is the same.

If you pass Owner to the other ViewModel, then the call should be exactly the same, passing the same parent ViewModel, so why would it fail?

You're right, it's super odd.
Did some more investigating - here's a way you can repro nearly the exact behavior in the MVVMDialogs sample code:

Open the Demo.FluentContentDialog project & go to MainViewModel
Change any of the instances of _dialogService.ShowContentDialogAsync(this, settings) to _dialogService.ShowContentDialogAsync(App.MainWindow, settings)
Try to open the dialog, You'll get the No view found with specified ownerViewModel of type Demo.Avalonia.FluentContentDialog.MainWindowViewModel

App.MainWindow is a View and not a ViewModel

It sure looks like a ViewModel, not a View, based on the code:

And App.MainWindow.DataSource doesn't exist.
And if you stop the bugger & examine App.MainWindow, you'll see that it's definitely a ViewModel, not a View.

Ah was missing the definition. If you call App.MainWindow, you get a NEW instance of the ViewModel, not the one that was displayed.

Hmm, if that's the case, should probably be called CreateMainWindowViewModel, since it's actually an instance of the VM, not the Window (view) - even you were confused by that ;)
I thought the whole point of Locator.Current.GetService was dependency injection tho, so you could share a service across various parts of the app without needing to pass around a reference - if it's just an entirely new instance each time, how could that even work? Still seems a bit strange...?

 For "Customer Details", you'll want a separate instance on each call.
CreateMainWindowViewModel just a bit long for my taste; anyway doesn't make much of a difference.

Aha, I see - Locator.CurrentMutable.RegisterConstant vs Locator.CurrentMutable.Register.
In that case, for the purpose of these ViewModels, maybe rather than changing the static property to Createxxx, it'd be cleaner/more intuitive to just register them as singletons, no?

You shouldn't be calling the Locator directly from your code usually; and if you register as Singleton, you'll get issues in the cases where you need multiple instances.

Right, I just meant in this case - for the public static properties that are storing references to locators that create new instances.

ok actually this case is one of the rate situations where calling the Locator from the code is OK; although you won't call it directly, but via IDialogService.
If you have a detail view that requires multiple instances, you'll run into trouble if you set them as Singleton.
And creating the ViewModel for the new View is the only time you should ever call it; you should never call the Locator from your code otherwise, otherwise you'll be unable to write unit tests.

If you have a detail view that requires multiple instances, you'll run into trouble if you set them as Singleton.

I just meant for the MainViewModel (not for all). Since there should only ever be one MainViewModel, right? And the dialogs class requires referring to it (to set it as the owner) anytime you want to show a dialog. Thus, it seems like it'd be both much clearer & more convenient if just MainViewModel were registered as a singleton - thus the sample code becomes _dialogService.ShowContentDialogAsync(App.MainViewModel, settings), and works from everywhere. No more confusion when trying to show it from another viewmodel. Right?

Well... if you decide that MainView will always be the parent of every dialog in your application, maintaining a static or singleton reference to it can be an option... although it's not a very clean design

Gotcha. Anyway, looks like it's all solved now - the issue was just that that global App.MainView(model) was creating fresh new instances each time. So...solved - thanks again! :)

Hi, I was playing with another application having a Mainwindow antd then a MainView with a navigagion TabControl (Something similar to the demo app within the https://github.com/irihitech/Semi.Avalonia)
Well after an investigation I have found that the DialogManager could be somehow simplified
`
public override IView? FindViewByViewModel(INotifyPropertyChanged viewModel)
{
if (_useNavigation)
{
return _navigationManager!.GetViewForViewModel(viewModel).AsWrapper(_navigationManager, View_Closing);
}
else
{
var windows =  Windows.ToList();
var window = windows.Count == 1
? windows[0]
: windows.FirstOrDefault(x => ReferenceEquals(viewModel, x.DataContext));
return window.AsWrapper();
}
}
`
Well it looks it is again not so clean solution... :(
However, I have right one window in my case and I believe it would simply working for my all cases I have met :)
Can I ask some questions?:
1a) Is the viewModel used in the different parts of the code since passed to the ShowOpenFileDialogAsync?
1b) And the same question about usage of the viewModel  in different parts of the code, if the _useNavigation is set to true
(I was thinking if even to create a similar method without that parameter)
2 ) What circumstances can the Windows enumeration have more items at?

I'm not sure I understand your questions correctly.

1a) Is the viewModel used in the different parts of the code since passed to the ShowOpenFileDialogAsync?

ViewModel is only used to find the View to assign as parent.

1b) And the same question about usage of the viewModel in different parts of the code, if the _useNavigation is set to true

I don't remember off the top of my head how parent is set in Android apps where there is no Window. You can investigate the code if you need that info.

2 ) What circumstances can the Windows enumeration have more items at?

When there are several Windows displayed in desktop applications.

I will note that for single-view applications, the parent ViewModel affects the navigation order when closing a view.

Thanks a lot for your answers! My questions  tried to lead to an idea, that in case of one window app, the consumers could't be bothered by that MainViewModel argument at all, when a need to call the Show... DialogAsync(). Another simplification could be that the consumer would  control the index to the Windows ... so It could lead to a methods like ShowDialog.. Async(.. , int windowIndex = 0)  again, without the wiew model parameter. What do you think about it?


Add rule for checking for presence of known GTFOBins on filesystems

Fixes #310
Summary
The rule checks for the presence of known GTFOBins binaries on the file system. It uses a set of file paths for the binaries and checks if any of those paths match the file path of any file on the system. If a match is found, a violation is generated.
Test Cases

Comments
There are standard Unix binaries that are commonly installed on many systems, and they can be used for legitimate purposes as well so i wasn't sure if to include them or not. Please let me know what all gtfobins files would be a good standard for this rule. I've added the most common ones.

@alegrey91 I think you closed this instead of merging?

Hello @0xquark, and thanks a lot for your contribution! We really appreciate your effort.

@alegrey91 I think you closed this instead of merging?

Yes, sorry 😅

@0xquark , sorry for my confusion. Is this rule connected to a control?

Hi @0xquark and still thanks for your contribution! I just checked the code that you submitted. It looks good, but I realized that we don't have as much information available in order to have a deep overview about the GTFOBins present. What I mean is that we should be able to extract for each container the whole list of binaries inside them and use this list to effectively check their presence. In your implementation (the only possible at the moment), we can only have a limited knowledge about them, since we don't have enough data. I'm going to schedule an internal call with the team in order to take a decision on how to provide these data and allow you to implement a better and more complete rule. I'll keep you updated :) If you have any doubt feel free to ask. I'll try to make you understand better the point.

Adding to this, I think that we will have access to image SBOMs within a few weeks. This means we can look for packages containing these binaries in Kubescape API SBOM objects

Thanks for the review @alegrey91 and @slashben. I first thought of implementing it by iterating over all the present binaries in a container but i was not able to find a way to do that. Kubescape API SBOM objects could be really helpful, will implement in the coming weeks then.
Would it be a good idea to have a similar rule that checks for the gtfobins binaries in the container commands?
I've modified the rule to iterate over each pod object in the input, then checks each container in the pod for the presence of GTFOBins binaries. It does this by defining a set of GTFOBin binaries, then checking if any of these binaries are present in the container's command field.
It could be possible that the user may be using some binaries in the command that has bigger risks while running the container, there may be an alternative present to that binary.

My Implementation of above rule using find : https://pastebin.com/1ef61nTP

@alegrey91 , @0xquark - hey guys, what is the status with this PR ?


Mergify does not wait for all jobs to be completed before merging

This is fixed by removing mergify. We still need a merge solution but it's a separate issue.

This is fixed by removing mergify. We still need a merge solution but it's a separate issue.


Add aranet-co2 extension

Description
Adds a command to view Aranet4 data (CO2, Humidity, Pressure, Temperature) and a menu bar command that shows your CO2 level (refreshes every 5 minutes)
Screencast

Checklist

[X] I read the extension guidelines
[X] I read the documentation about publishing
[X] I ran npm run build and tested this distribution build in Raycast
[X] I checked that files in the assets folder are used by the extension itself
[X] I checked that assets used by the README are placed outside of the metadata folder

@pernielsentikaer Did you install Aranet from the app store and the claranet CLI? I put it in the README. If you didn't, what do you suggest for telling them to do so? I could make maybe the dialog error thing, or replace my list of data with a list of links?

You can see how extensions like Eagle does it, I think you can do something similar


Combination with configure headers and Data driven is not working

IMPORTANT: If you have a general question please use Stack Overflow instead where Karate has a dedicated "tag": https://stackoverflow.com/questions/tagged/karate
If you are sure you have found a bug, please make sure you follow the instructions here: (https://github.com/intuit/karate/wiki/How-to-Submit-an-Issue)
If I confiure headers in background without data driven. its applicable for all scenarios and working without any issues.
its not working for below use case.
I could see headers are copying for 1st and 2nd scenarios since we configured in BackGround
But, since i am using data driven concept in scenario 3, I could see configured headers are not applying for scenarion 3.
Can you help me on this.
Note: if i mention configure headers explicitly in scenario 3, then its working but i feel, Its a bug. can you check.
Feature: Worker Time profile feature validations
Background:
Given url 'https://localhsot:8080/abc.com'
# * def testdata = read("testdata.csv")
* configure headers = read('Headers.js')
Scenario Outline: Verify Worker time profile 1for
When method GET
Then status 200
@FIT
Examples:
  | User Type         |
  | Clocking Employee |

Scenario Outline: 02.Verify Worker time profile 1for
When method GET
Then status 200
@FIT
Examples:
  | User Type         |
  | Clocking Employee |

Scenario Outline: Verify Worker time profile for
When method GET
Then status 200
@FIT
Examples:
  | read("testdata.csv") |

Sample.zip

Version 1.01

@DivNaiPra sorry you have NOT followed the process. your pom.xml looks completely messed up to me with all kinds of versions mixed in, sorry:

this issue you refer to is most likely a duplicate of https://github.com/intuit/karate/issues/1560
so try again please


Document Firmware CI workflow

AWS

E2E tests in firmware build hexfile
runs NordicSemiconductor/cloud-aws-firmware-ci-device-action which (because of dependencies) executes via npm exec
@nordicsemiconductor/firmware-ci-runner-aws
then runs NordicSemiconductor/cloud-aws-firmware-ci-feature-runner-action to verify the run result against the .feature files

Working on a talk: https://github.com/coderbyheart/firmware-test-automation-using-real-embedded-devices


feat: exchange Metal API keys for LB API OAuth2 tokens

This adds an oauth2.TokenSource that uses the token exchange endpoint to request an OAuth2 JWT for the given API key.
The TokenSource is added to the context under the lbaas.ContextOAuth2 context key.  The load balancer API client automatically looks for a TokenSource under that key, uses it to get the OAuth2 token, and adds the token to outgoing requests.

Here's a handy list of similar Apache 2 code in other providers where a managed loadbalancer service is handled:

https://github.com/linode/linode-cloud-controller-manager/blob/master/cloud/linode/loadbalancers.go (Apache 2)
https://github.com/digitalocean/digitalocean-cloud-controller-manager/blob/master/cloud-controller-manager/do/loadbalancers.go (Apache 2)
https://github.com/oracle/oci-cloud-controller-manager/blob/master/pkg/cloudprovider/providers/oci/load_balancer.go (Apache 2)
https://github.com/hetznercloud/hcloud-cloud-controller-manager/blob/main/hcloud/load_balancers.go
https://github.com/scaleway/scaleway-cloud-controller-manager/blob/master/scaleway/loadbalancers.go
https://github.com/kubernetes-sigs/cloud-provider-azure/blob/master/pkg/provider/azure_loadbalancer.go#L184
https://github.com/kubernetes-sigs/cloud-provider-huaweicloud/blob/master/pkg/cloudprovider/huaweicloud/sharedloadbalancer.go#L140


[WIP] Add tip build

TODO

[x] Add tip build settings
[x] Remove exclude settings
[ ] (Optional) build in windows

Pull Request Test Coverage Report for Build 1226

4 of 4 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 90.476%

Totals

Change from base Build 1222:
0.0%

Covered Lines:
1197

Relevant Lines:
1323

💛  - Coveralls

Pull Request Test Coverage Report for Build 1228

4 of 4 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 90.476%

Totals

Change from base Build 1222:
0.0%

Covered Lines:
1197

Relevant Lines:
1323

💛  - Coveralls

Pull Request Test Coverage Report for Build 1224

4 of 4 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 90.476%

Totals

Change from base Build 1222:
0.0%

Covered Lines:
1197

Relevant Lines:
1323

💛  - Coveralls


I disabled the "mention user with a comma" setting. But he is still mentioned with a comma.

Describe the bug

I disabled the "mention user with a comma" setting. But he is still mentioned with a comma.
To Reproduce

Expected behavior

Screenshots

Chatterino version

latest
Additional context

What does "latest" mean? Latest stable version? Latest nightly?

Chatterino Nightly 2.1.5 (commit 375aa221e, 03.10.2019) @leon-richardt

I can't reproduce unfortunately. Could you maybe walk me through how you managed to observe the described behavior?
Alternatively, you could also attach a GIF/video of the bug occurring. :smile:

 @leon-richardt

Ah okay, it's important to note that you're not tab-completing but right-clicking user names. :+1:


Support masking for Conditional TTL

@tkhurana We should consider converting the regular TTL masking to use the query rewrite mechanism. Just a thought, but that can be a separate JIRA


cleanup warnings in build about golang 1.6

godep: WARNING: Go version (go1.6) & $GO15VENDOREXPERIMENT= wants to enable the vendor experiment, but disabling because a Godep workspace (Godeps/_workspace) exists
�

godep: WARNING: Go version (go1.6) & $GO15VENDOREXPERIMENT= wants to enable the vendor experiment, but disabling because a Godep workspace (Godeps/_workspace) exists


add flow-remove-types option

this flag allow to not preprend each files with /@flow/

thank you

Thank you a lot for the contribution ❤


Determine release verification process

In order to ensure that we're not breaking telemetry or causing regressions, it would be good to figure out some sort of telemetry verification test suite. Potentially, this could be automated with the use of something like TraceTest.
We should first determine what the appropriate level of verification is, and go from there -- I don't necessarily think it'd help to build up some complex automation that would take a lot of time to keep up-to-date, for example.

An initial integration spec could look something like this, perhaps -
For each request that the load generator can perform:

We should be able to locate one complete, unbroken trace.
That trace should contain at least one span from every service we expect to be participating in that request.

Making additional assertions about ordering or what attributes are present might end up being brittle, but those two assertions would probably not change often (if ever).

Closing as this is not currently needed.


Local install of webpack on windows breaks module resolution

On windows I can run (same for cmd and msysgit)
$ npm install react && webpack --entry react --output-file bundle.js

but if I do
$ npm install react webpack && webpack --entry react --output-file bundle.js

I get
ERROR in ./~/react/lib/React.js
Module not found: Error: Cannot resolve directory 'c:' in c:!Files\test\node_modules\react\lib
@ ./~/react/lib/React.js 1:0-118

Same habits = same problem. Also have ! in folder name. Think it's not a critical issue :), but need to be fixed. Thanks.

AFAIK this is no longer an issue in webpack 2, so closing, but we can always re-open if it turns out to still be an issue.


Add support to implement HYDE retrieval strategy in embedchain

🚀 The feature
HYDE is one of the well known retrieval strategies used for retrieval. More details about HYDE can be found in this paper.
We need to implement HYDE as a retrieval strategy in HYDE and then figure out the best possible and simplest interface to be exposed in embedchain
Motivation, pitch
Increasing the retrieval strategies makes it more configurable for the end user to choose strategies as per their usecase.

Definitely interested in seeing more papers implemented as simple to use strategies or chainable pipeline in this project. Haven't seen any projects deliver SOTA RAG pipeline building blocks like that yet and embedchain is my current favorite interface otherwise.


Fix base proto path when used as module

Pull Request Test Coverage Report for Build 46

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 89.51%

Totals

Change from base Build 41:
0.0%

Covered Lines:
78

Relevant Lines:
85

💛  - Coveralls


I'd like to join this project's community

Your public repo
https://github.com/patriciagoh-external/gov4git-identity-public.git
Your public branch
main

approve

 Follow up
On Tuesday, 03-Dec-24 18:16:59 UTC by Gov4Git dev
@patriciagoh-external was added to the community.


[Edit event] The first version of the event is displayed when the user tries to edit it several times.

Environment: OS: Windows 10 pro, Chrome Version 130.0.6723.92
Reproducible: always.
Build found: 08.11.2024
Description
When the User edits something in the Event and saves it, then tries to edit the event again the data about the event isn’t the latest version but it is the first version without any changes except the photo. So, the user should every time make all changes from the beginning. Only the photo is saved.
Preconditions

The website https://www.greencity.cx.ua/#/greenCity  is opened
User is logged in
The event is created by the User.

Steps to reproduce

Open the Event editing page.
Make some changes to the data of the event.
Save the changes
Open the Event editing page again.

Actual result
The data of the event is the first version without any changes except the photo.
Expected result
The data of the event is the latest version with all changes.
User story and test case links
E.g.: "User story #3195
https://github.com/user-attachments/assets/771e0d4d-2976-4ff3-b6e0-340b5a7900d2

This is not a back-end issue, this bug disappears after refreshing the page

@Cr1stal423 Ok, thanks. I will update the bug report.


Add yamaha_musiccast sound modes

Description:
Added sound modes to yamaha-musiccast component. @jalmeroth
Checklist:

[x ] The code change is tested and works locally.

@uvjustin any updates on this? :)

@springstan
I'm not the package maintainer of the pypi package so we'll have to wait for my pull request to get merged on that side.

@uvjustin please link the PR that needs to be merged in the python package and please format your code with black and push it so we can take a look at it :)

@springstan Here is the PR https://github.com/jalmeroth/pymusiccast/pull/15

Ok with closing this. I will continue to use my own version locally for the sound modes functionality. If there's more interest in updating the pymusiccast library I can fork it and update the HA core to use that library instead.

I'll close here since this is still waiting for upstream.

@uvjustin please fork the library and redo this PR. I have two Yamaha musiccast speakers and am waiting for this PR


Prevent a webpage from navigating away

i am using Link component in my vuejs. i want to prevent webpage from navigating away to another page. how can I implement in my laravel and vuejs project.

Hi there,
Thanks for reporting but it looks like this is a question which can be asked on a support channel. Please only use this issue tracker for reporting bugs with the library itself. If you have a question on how to use functionality provided by this repo you can try one of the following channels:

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

However, this issue will not be locked and everyone is still free to discuss solutions to your problem!
Thanks.


Discuss open visualisation tasks by Christoph

Organise with Tatiana (Detailansicht der Patienten)

Meeting will take place next week


aggregation result support changelog mode

Describe what's wrong

edit 1:
Currently recommended to write a versioned_kv table, but versioned_kv not support deletion, the changelog is more appropriate, but the result does not work with changelog mode.

(Jove Github Bot) assuming it is not done, deferred this ticket to the next sprint.

(Jove Github Bot) assuming it is not done, deferred this ticket to the next sprint.

(Jove Github Bot) assuming it is not done, deferred this ticket to the next sprint.


[Deque Analysis] Item/Entity Homepage "serious" issues

Serious: This issue results in serious barriers for people with disabilities, and will partially prevent them from accessing fundamental features or content. People relying on assistive technologies will experience significant frustration as a result. Issues falling under this category are major problems, and remediation should be a priority.

Deque Analysis Summary
Item / Entity homepages have a total of 4 serious issues (not including color contrast which are handled in other tickets).  These have been grouped into one ticket because they are similar issues on both pages.

(ID 470327) "Purpose of the link is not clear in context." on the "Show 4 more" and "Hide last 4" links which appear in long lists of Entity relationships (especially on Person Entity pages like https://demo.dspace.org/entities/person/5a3f7c7a-d3df-419c-b8a2-f00ede62c60a).

Fix by one of the following: (1) Provide unique link text that conveys the purpose of each link. OR (2)  Ensure that the link text PLUS its programmatic context conveys the purpose of the link. (e.g. using "aria-label" to provide more details).  See also https://dequeuniversity.com/class/semantic-structure2/links/link-text

(ID 471043) "Content is lost at 320px width" on the Item URI/Handle ("URI" field in display) when the link is long, e.g. https://demo.dspace.org/entities/publication/4e203020-8fd6-406a-addc-f4f08365b662

Fix by ensuring the link also wraps/resizes for smaller views of 320px
NO LONGER REPRODUCIBLE in 7.6.1. Unsure of when this was fixed.

Full list of issues is viewable at (requires login): https://axeauditor.dequecloud.com/test-run/0856438a-a19a-11eb-bc31-b7d5be387c86/issues?sortField=ordinal&sortDir=asc&filter[severity]=3&filter[type]=issue&filter[page_number]=6&filter[page_number]=7
More Information / Tools

Consider using Deque's free Chrome plugin to check your work

(ID 470327) "Purpose of the link is not clear in context." on the "Show 4 more" and "Hide last 4" links which appear in long lists of Entity relationships (especially on Person Entity pages like https://demo7.dspace.org/entities/person/5a3f7c7a-d3df-419c-b8a2-f00ede62c60a).

We'll add the entity name to the i18n message. It will result in a lot more messages though.

(IDs 471036, 471060) "State of active component lacks 3 to 1 contrast ratio" on the "Full Item page" button.

We could set a contrasting outline on btn-outline-primary buttons across DSpace. However this will be a problem for all buttons. The focus outline is set by a bootstrap function to be a color derived from the type of button it is. It makes sense to group all non-text contrast issues (or at least the ones where it occurs against the default white body background) in one ticket rather than fixing it in the context of each page separately. Otherwise we'll get slightly different outlines for focus on every page.

(ID 471043) "Content is lost at 320px width" on the Item URI/Handle ("URI" field in display) when the link is long

We'll add the text-break class to this field
If we leave out 2 this can be done in 2 hours.
Fixing 2. for all outlines against the default white background for all button types and form fields will take an estimated 3 hours

@artlowel : Thanks for that feedback.  I like your suggestion to break out the non-text contrast issues into a separate ticket (as they are currently embedded in several tickets. So, I'll do that & update the affected tickets.
So, let's leave 2 out of this ticket (I'll remove it once the new ticket exists), and I'll add the estimate of 2hrs & assign this back to you for your team to work on.

Hi @tdonohue! 4Science will work on this. Our estimation is 4 hours. Thank you!


decodeBase64 option adds literal YAML multi-line string syntax

To Reproduce
Create a helm chart with the template:
apiVersion: v1
kind: Secret
type: Opaque
metadata:
  name: foo
data:
  greeting: 'aGVsbG8K'

And with the test:
tests:
  - it: should be "hello"
    asserts:
      - equal:
          path: data.greeting
          value: hello
          decodeBase64: true
          # value: 'aGVsbG8K'

Expected behavior
Test passes
Actual Behavior
	- should be "hello"

		- asserts[0] `equal` fail
			Template:	pfcon/templates/pman-secrets.yml
			DocumentIndex:	0
			Path:	data.greeting
			Expected to equal:
				hello
			Actual:
				|
				 hello
			Diff:
				--- Expected
				+++ Actual
				@@ -1,2 +1,3 @@
				-hello
				+|
				+  hello

Desktop (please complete the following information):

OS: Linux
Plugin Version: I tried both the container image docker.io/helmunittest/helm-unittest:3.16.1-0.6.3 and version 0.5.2 installed from nixpkgs.

@ivankatliarchuk thank you for your attention, good catch!


RuntimeError: one of the variables needed for gradient computation has been modified by an inplace operation: [torch.cuda.HalfTensor [128, 10572]]

optimizer.zero_grad()
if USE_APEX:
with amp.scale_loss(lossx, optimizer) as scaled_loss:
scaled_loss.backward()
else:
lossx.backward()
optimizer.step()
RuntimeError: one of the variables needed for gradient computation has been modified by an inplace operation: [torch.cuda.HalfTensor [128, 10572]], which is output 0 of ClampBackward, is at version 1; expected version 0 instead. Hint: enable anomaly detection to find the operation that failed to compute its gradient, with torch.autograd.set_detect_anomaly(True).

please use my docker env to test


New tool, make_proto_cpp, usefull to compile proto files quickly

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Just signed it !

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Thanks for the pull request. I am not sure whether this PR fits in grpc repo. I would encourage you to host it in your own repo. Thanks again.


[Bot Rules] Update Personalizer contacts

Summary
The focus of these changes is to update the contacts for Personalizer, based on CODEOWNERS changes made in #23136

/check-enforcer override


Encoding byte strings in Python 3 causes infinite recursion

>>> jsonpickle.encode(b'foo')
---------------------------------------------------------------------------
RuntimeError                              Traceback (most recent call last)
<ipython-input-7-5e089e18bf41> in <module>()
----> 1 jsonpickle.encode(b'foo')

/Users/ivansmirnov/dev/jsonpickle/jsonpickle/__init__.py in encode(value, unpicklable, make_refs, keys, max_depth, backend, warn, max_iter)
    129                           keys=keys,
    130                           max_depth=max_depth,
--> 131                           warn=warn)
    132
    133

/Users/ivansmirnov/dev/jsonpickle/jsonpickle/pickler.py in encode(value, unpicklable, make_refs, keys, max_depth, reset, backend, warn, context, max_iter)
     39                           warn=warn,
     40                           max_iter=max_iter)
---> 41     return backend.encode(context.flatten(value, reset=reset))
     42
     43

/Users/ivansmirnov/dev/jsonpickle/jsonpickle/pickler.py in flatten(self, obj, reset)
    139         if reset:
    140             self.reset()
--> 141         return self._flatten(obj)
    142
    143     def _flatten(self, obj):

/Users/ivansmirnov/dev/jsonpickle/jsonpickle/pickler.py in _flatten(self, obj)
    143     def _flatten(self, obj):
    144         self._push()
--> 145         return self._pop(self._flatten_obj(obj))
    146
    147     def _flatten_obj(self, obj):

/Users/ivansmirnov/dev/jsonpickle/jsonpickle/pickler.py in _flatten_obj(self, obj)
    159             return None
    160
--> 161         return flatten_func(obj)
    162
    163     def _list_recurse(self, obj):

/Users/ivansmirnov/dev/jsonpickle/jsonpickle/pickler.py in _ref_obj_instance(self, obj)
    214             # We've never seen this object so return its
    215             # json representation.
--> 216             return self._flatten_obj_instance(obj)
    217         # We've seen this object before so place an object
    218         # reference tag in the data. This avoids infinite recursion

...

/Users/ivansmirnov/dev/jsonpickle/jsonpickle/pickler.py in _flatten(self, obj)
    143     def _flatten(self, obj):
    144         self._push()
--> 145         return self._pop(self._flatten_obj(obj))
    146
    147     def _flatten_obj(self, obj):

/Users/ivansmirnov/dev/jsonpickle/jsonpickle/pickler.py in _flatten_obj(self, obj)
    147     def _flatten_obj(self, obj):
    148         self._seen.append(obj)
--> 149         max_reached = self._depth == self._max_depth
    150
    151         if max_reached or (not self.make_refs and id(obj) in self._objs):

RuntimeError: maximum recursion depth exceeded in comparison

Ouch. You're doing yeoman's work on finding our bugs!
--
Marcin Tustin
Tel: +44 (0) 7773 787 105 (UK)
+1<PHONE_NUMBER> (US)

This is a pretty bad one since this is a very basic built in type :) Wonder if it's a regression of a sort

My guess is this:
>>> b'foo'.__getnewargs__()
(b'foo',)

The question is -- how do we want to handle bytestrings in general? Introduce a tags.BYTES and encode/decode the payload to/from UTF-8?
http://www.diveintopython3.net/strings.html#byte-arrays

@davvid

That sounds right to me - it's a primitive type, after all.

Idk, could be more compact or could be longer (I guess the main benefit using something like latin1 is that any ascii text would still remain readable).
>>> import json
>>> s = b'\x00\x00\x00\x00\x00\x00\xf0?foo'
>>> json.dumps(s.decode('latin1'))
'"\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u00f0?foo"'
>>> import array
>>> json.dumps(list(array.array('B', s)))
'[0, 0, 0, 0, 0, 0, 240, 63, 102, 111, 111]'

Base64?
--
Marcin Tustin
Tel: +44 (0) 7773 787 105 (UK)
+1<PHONE_NUMBER> (US)

>>> import base64
>>> base64.b64encode(s).decode('ascii')
'AAAAAAAA8D9mb28='

I was thinking more u'ascii'.encode('base64'), which seems to work fine,
and result in minimal expansion. Decimal coding with spaces and commas is
going to be suboptimal.
On Friday, January 9, 2015, Ivan Smirnov<EMAIL_ADDRESS>wrote:

import base64>>> base64.b64encode(s).decode('ascii')'AAAAAAAA8D9mb28='

—
Reply to this email directly or view it on GitHub
https://github.com/jsonpickle/jsonpickle/issues/108#issuecomment-69331571
.

--
Marcin Tustin
Tel: +44 (0) 7773 787 105 (UK)
+1<PHONE_NUMBER> (US)

>>> print(b'\x00\x00\x00\x00\x00\x00\xf0?foo'.encode('base64'))
AAAAAAAA8D9mb28=

The ascii part ("foo") is lost :/

b'\x00\x00\x00\x00\x00\x00\xf0?foo'.encode('base64').decode('base64')
'\x00\x00\x00\x00\x00\x00\xf0?foo'

Quoted printable is probably the right thing here, though:

b'\x00\x00\x00\x00\x00\x00\xf0?foo'.encode('quopri').decode('quopri')
'\x00\x00\x00\x00\x00\x00\xf0?foo'
b'\x00\x00\x00\x00\x00\x00\xf0?foo'.encode('quopri')
'=00=00=00=00=00=00=F0?foo'

Too many options :panda_face:

Not sure I follow?
--
Marcin Tustin
Tel: +44 (0) 7773 787 105 (UK)
+1<PHONE_NUMBER> (US)

base64 / quopri / latin1 / array, many options to do this -- we need another opinion :)
I personally like quopri encoding though since it leaves ascii as ascii and renders the rest as hex.

Just implement it as quopri. We can change it later before release.
--
Marcin Tustin
Tel: +44 (0) 7773 787 105 (UK)
+1<PHONE_NUMBER> (US)

Seems to work so far, I'll try and push it later tonight (this is on py3k):
>>> import jsonpickle
>>> s = b'\x00\x00\x00\x00\x00\x00\xf0?foo'
>>> jsonpickle.encode(s)
'{"py/bytes": "=00=00=00=00=00=00=F0?foo"}'
>>> jsonpickle.decode(jsonpickle.encode(s))
b'\x00\x00\x00\x00\x00\x00\xf0?foo'

The next big question is -- what do we do in Python 2? Technically, in py2 str is bytes, but does that mean we have to wrap every non-unicode string in {"py/bytes": ...}? This way, in Python 2 jsonpickle.encode('foo') would yield '{"py/bytes": "foo"}' and not just "foo" which may be excessively verbose.
The current behaviour in Python 2 is this (which seems quite broken):
>>> jsonpickle.encode('\xff')
'"\xff"'
>>> jsonpickle.decode(jsonpickle.encode('\xff'))
ValueError: Invalid UTF-8 sequence length when decoding 'string'

We could forego the bytes wrapper if the encoded version is the same as the
input, but I bet there would be nasty edge cases. At the least, you'd get
different types serializing in 2 and deserializing in 3.
--
Marcin Tustin
Tel: +44 (0) 7773 787 105 (UK)
+1<PHONE_NUMBER> (US)

You already get different types. Even more than that, you get different types when roundtripping within Python 2:
>>> jsonpickle.decode(jsonpickle.encode('foo'))
u'foo'

Well, then we should probably just assume that every byte string in 2 is
Unicode, unless it can't be encoded as such (exception handler?) and encode
as bytes in that case.
On Friday, January 9, 2015, Ivan Smirnov<EMAIL_ADDRESS>wrote:

You already get different types. Even more than that, you get different
types when roundtripping within Python 2:

jsonpickle.decode(jsonpickle.encode('foo'))u'foo'

—
Reply to this email directly or view it on GitHub
https://github.com/jsonpickle/jsonpickle/issues/108#issuecomment-69359817
.

--
Marcin Tustin
Tel: +44 (0) 7773 787 105 (UK)
+1<PHONE_NUMBER> (US)

There's one catch though: http://bugs.python.org/issue6784
Python 3 actually does unpickle bytestrings from Python 2 as unicode strings... What were the Python core devs smoking? Which obviously makes it even more confusing, especially if we are to comply with pickle protocols. So to get/hack around this weirdness, there's a fallback option in pickle so you can specify something like errors='bytes' and hope that works (e.g. see an example here).

One cheap way of doing this would be like so:

In Python 2:

serialize unicode strings as is
for str strings, first try to encode them in utf-8
only if that fails, serialize them via the bytes wrapper

In Python 3:

serialize all str strings as is (unicode)
serialize all bytes strings via the bytes wrapper

I'm certain that's the right thing.

Yeah, sounds just about right.  For str, we'd probably try to decode into unicode as utf-8, rather than decode, right?  If you use simplejson you can already see that u'foo' becomes 'foo' at the lowest level.

Yep, mind the typo -- decode of course, that's how it is done in #110

Closed via #110


Add CI checks validating canonical features list spec point references against the spec document

This is possible once we've done ably/specification#1.
Feature spec points are referenced in the canonical features list (YAML). We need to cross-reference those with the features spec (textile) to make sure that they exist.
For wider context, see Future Direction for the Client Library Features Specification.
┆Issue is synchronized with this Jira Uncategorised by Unito

Not a task I was able to find the time to complete while still employed at Ably so removing my assignment.


Expose internal mocks on UmbracoTestContext for more flexibility

There were several mocks inside UmbracoTestContext which you couldn't access to setup methods and properties because they were not exposed outside that class. Expose them for tests to use.
It was possible to mock a user with claims on HttpContext but it required knowledge of the internals of UmbracoTestContext to do properly. Make it easier by allowing tests to just set the CurrentPrincipal to a new one.
Add a new tests project for the test helpers library, and start testing UmbracoTestContext by testing the ability to mock a user with claims.
AB#154422

I deleted my previous comment because I looked into it a bit more and understood how it works. I added a test to check whether we can access the claims from a controller. PR is Add test for accessing Claims from controller #154422.  Please merge it into your branch if you are happy with it. If not, I'll delete my PR and approve.


Add InfrastructureName.

Picking up where @fabianofranz  had to leave off in https://github.com/openshift/api/pull/231.
Adding InfrastructureName will give components the information they need to tag cloud resources consistently. (kubernetes.io/cluster/[infraname] = owned)
The controversial arbitrary AWS tagging is removed based on the comments in that PR.
I was going to move this back to Spec because it does not feel like Status to me, but I saw PlatformType is already Status and thus I think this ship has already sailed.
CC @abhinavdahiya @wking @derekwaynecarr @smarterclayton

/lgtm

/lgtm

@sdodson can you help us get this merged?


Convert iterableCurry/asyncIterableCurry args to objects

The configuration objects need only be created once at parse time.
Doing this should save on both bundle size and execution time

This change also improves readability, I like this.


ChainAPI: Add DNS verification section to Workspaces

Yeah as per the discussion on that JIRA, I'm not sure we should be mentioning how often we check at all, as that ties our hands if we need to adjust the schedule over time.


Why no release since December?

Is this project dead?

Nope, but maintainers are welcome :-)
I'll update the image now.

Thank you @Starefossen !


Create driver interface for K8s Lifecycle Management

We can solve a few problems at once by creating a standard interface for how we create, get, manage K8s clusters in idpbuilder:

Support kind + docker alternatives such as kind + finch
Support already created k8s clusters aka more production deployments
Support virtual k8s clusters such as vcluster.

Support kind + docker alternatives such as kind + finch

kind + podman


expansion of valueset-observation-values empty

http://fhir-dev.healthintersections.com.au/open/ValueSet/valueset-observation-values/$expand

The value set was wrong. Corrected the underlying value set in the FHIR spec


Bug: Images for screenshots of the app is not visible

I found out that the images of 'screenshots of the app' is not viewable. Do check it out!

Oh... Sorry for the trouble!


Stop using sharp at runtime

Generate icons at build time, don't commit them as they are binary
files

Signed-off-by: Sebastian Malton<EMAIL_ADDRESS>fixes https://github.com/lensapp/lens/issues/5336

This PR introduced temporal dependency for running development environment. If you are trying to start application before ever building (using yarn dev-run) you will face an error.
Also make dev fails immediately with (M1)
error Command failed with signal "SIGKILL".
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
make: *** [build/tray/trayIconTemplate.png] Error 1

That is a good catch. Will fix again.

This PR introduced temporal dependency for running development environment.

I think that make dev is the normal way of running dev mode, is that not the case for you?

I think that make dev is the normal way of running dev mode, is that not the case for you?

make dev is super slow in comparison to three separate terminals for:

yarn dev-run
yarn dev:main
yarn dev:renderer

There are some downsides but good stuff overwhelms the bad stuff.


Getting "404 Resource Not Found"

There's a 404 Resource Not Found error when trying to access the OpenAI endpoint.
async def main():
    red_teaming_orchestrator = RedTeamingOrchestrator(
        attack_strategy=attack_strategy,
        red_teaming_chat=red_teaming_chat,
        prompt_target=prompt_target,
        initial_red_teaming_prompt="how can I help you?",
        scorer=scorer,
        verbose=True,
    )

    try:
        score = await red_teaming_orchestrator.apply_attack_strategy_until_completion_async(max_turns=3)
        red_teaming_orchestrator.print_conversation()
    except Exception as e:
        logging.error(f"An error occurred: {e}")
    finally:
        pass

That's pretty much down to your connection details. Make sure the endpoint exists, is spelled right, your secret API key is correct, and then also print it out for yourself to see it. Sometimes people have issues with it because they don't reload the kernel after updating their env file.

@Saravan004 is your issue resolved? Can this be closed?

Thank You.


2nd level bower dependencies are not being loaded properly

We are using ivy-videojs which is listed as a dependency of our engine. This issue is not specific to ivy-videojs but appears to be a larger issue with addons who have bower dependencies inside of engines.
During the build we get this issue:
TypeError: Path must be a string. Received undefined
 at assertPath (path.js:7:11)
 at Object.join (path.js:1211:7)
 at Class.included (/Users/mlee/savo-web-host/node_modules/ivy-videojs/index.js:18:27)
 at addons.map.addon (/Users/mlee/savo-web-host/node_modules/ember-cli/lib/models/addon.js:346:34)
 at Array.map (native)
 at Class.eachAddonInvoke (/Users/mlee/savo-web-host/node_modules/ember-cli/lib/models/addon.js:344:24)
 at Class.included (/Users/mlee/savo-web-host/node_modules/ember-cli/lib/models/addon.js:575:10)
 at Class.superWrapper [as included] (/Users/mlee/savo-web-host/node_modules/core-object/lib/assign-properties.js:34:20)
 at Class.included (/Users/mlee/savo-discovery-engine/index.js:9:26)
 at Class.superWrapper [as included] (/Users/mlee/savo-web-host/node_modules/core-object/lib/assign-properties.js:34:20)

This is really just a red herring for a different issue.
You can see line 18  of ivy-videojs/index.js is simply:
 app.import({
    development: path.join(app.bowerDirectory, 'video.js/dist/video-js.css'),
    production:  path.join(app.bowerDirectory, 'video.js/dist/video-js.min.css')
  });

I'm able to locally link and can verify the app.bowerDirectory is undefined. I am able to simply set the app.bowerDirectory to bower_components and it builds and functions. I don't think this is great solution as we would have to keep our own versions of all addons who require bower components.
Has anyone else run into this issue? What have you done to either workaround or solve this?
Any feedback is appreciated!
Thanks,
Matthew
edit:
current solution is to update the engines index.js included hook to set the bower directory
//index.js
const EngineAddon = require('ember-engines/lib/engine-addon');

module.exports = EngineAddon.extend({
  name: 'savo-discovery-engine',
  lazyLoading: false,
  included(app) {
    this.bowerDirectory = app.bowerDirectory;
    this._super.included.apply(this, arguments);
  }
});

i am running in to the same issue, where engine needs some bower dependencies. But i can't able to import those dependencies in engine-vendor.js.
Attaching the code & issue i got

Did you find any workaround to resolve this issue?

Unfortunately, this is unlikely to be fixed in ember-engines. I would suggest working on migrating those bower dependencies to NPM...

Thanks for the suggestion. But after migrating the dependencies to NPM, i ended up in this issue #303

I'm closing this issue as bower will not supported going forward (in general, not just here) with the suggestion to migrate the bower packages to npm/yarn packages.
Thanks @rwjblue!


I can't open credits (using the newest version)

Describe your bug here.

Command Prompt/Terminal logs (if existing)
No response
Are you modding a build from source or with Lua?
Compiled build
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
no

Try again in 0.6.1
Close the issue if the problem was solved.


How to create a rich text editor that returns html results in Flutter?

My goal is to create a rich text editor that returns html results. I am using the package flutter_quill. It can only return plain text using _controller.document.toPlainText() and json using _controller.document.toDelta().toJson(). I also tried html_editor_enhanced before. It has some problems. When I click the text color button and the dialog is shown, I can't press one of the colors in the horizontal color list. The mouse is always a text mouse and I can enter text despite the dialog being displayed in front of the text field. Although the dialog is blocked, I can still write behind the text field. Also, I am using web (Chrome) to run the app. Are there any other rich text editors that can return html results or any way to return html results in flutter_quill? Appreciate if someone can advise. Thank you in advance!

Hi @mycar98765,
This issue doesn't seem to describe a bug or a feature request. Please see https://flutter.dev/community for resources and places where you can ask questions like this.
You may also get some help if you post it on Stack Overflow and if you need help with your code, please see https://www.reddit.com/r/flutterhelp/
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it.
Thank you

I finally found a solution!
I am using the following code to return html results:
final convertedValue = jsonEncode(delta.toJson());
final markdown = deltaToMarkdown(convertedValue);
final html = markdownToHtml(markdown);

@danagbemava-nc  Can you take a look at this question?: https://github.com/singerdmx/flutter-quill/issues/952


SS14 TODO

Overall goal: Create a platform independent of BYOND that can be forked into different stations.
[Reworking this section]

Could you add the client throwing a NotImplementedException crashing the whole client (should just make a log with the exception info). Oh and fixing collisions (its done bad, cant press key towards wall and move perpendicular to it) too. Im working on both of those right now.

#68

I think our goal should be to strip game code entirely, going from job handling to the lobby. Unless removing said code would interfere with development.

Yeah, I agree, would you mind expanding on that idea a bit more, I'm interested in what you have in mind and wouldn't mind helping out.

Issue's too generic and we have independent issues all discussing this.


Create RSE Page

Create individual RSE page.
Keep in mind that the individual RSE page is an interface available only to admins.
Details to follow

done with #232


Collapsing schema for array of repetitive data?

If I have an API that returns a large amount of data with a repetitive object arrays nested into it, is it possible to have the outputted spec collapse the schema into an array with a single object?

Apologize, wasn't looking over the output carefully enough. Looks like this is handled!


EnableApiVersioningHeader breaks further API calls on .NET Framework

NEST version: 7.17.0
Elasticsearch version: 8.1.2
.NET runtime version: .NET Framework 4.8
Operating system version: Windows 10 Enterprise, Version 1909, OS build 18363.2037
Description of the problem including expected versus actual behavior:
When EnableApiVersioningHeader() is called on the ConnectionSettings, further requests begin to fail (in this example - ElasticClient.Indices.PutTemplateAsync).
This problem happens only when using .NET Framework (tried with TargetFramework == net471 and net48)
On .NET Core it does not happen. (tried with TargetFramework == netcoreapp3.1 and net6.0)
Without calling EnableApiVersioningHeader the following code works as expected, but I wanted to use EnableApiVersioningHeader to mitigate #6154 issue (missing _type property in Elastic v8).
Steps to reproduce:
Use code below. Provide valid elastic 8.1.2 instance and credentials.
Program.cs
using System;
using Nest;

var settings = new ConnectionSettings(new Uri("https://some-elastic-instance.aws.cloud.es.io:9243"));
settings.BasicAuthentication("username", "password");
settings.EnableDebugMode();
settings.EnableApiVersioningHeader();

var client = new ElasticClient(settings);
var response = await client.Indices.PutTemplateAsync("some-index-template", x => x
    .IndexPatterns(new string[] { "pattern*" })
    .Version(1)
    .Map<IndexType>(m => m.Properties(a => a
        .Keyword(s => s.Name(i => i.FieldA))
        .Keyword(s => s.Name(i => i.FieldB))
)));

Console.WriteLine(response.DebugInformation);

public class IndexType
{
    public string FieldA { get; set; }
    public string FieldB { get; set; }
}

elastictest.csproj
<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>net48</TargetFramework>
    <LangVersion>10.0</LangVersion>
    <Nullable>enable</Nullable>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="NEST" Version="7.17.0" />
  </ItemGroup>

</Project>

Code: elastictest.zip
Expected behavior
Using EnableApiVersioningHeader() should not break existing code.
Provide DebugInformation (if relevant):
Without EnableVersioningApiHeader
Valid NEST response built from a successful (200) low level call on PUT: /_template/some-index-template?pretty=true&error_trace=true
# Warnings:
- The client is unable to verify that the server is Elasticsearch due to security privileges on the server side. Some functionality may not be compatible if the server is running an unsupported product.
# Server indicated deprecations:
- 299 Elasticsearch-8.1.2-31df9689e80bad366ac20176aa7f2371ea5eb4c1 "Legacy index templates are deprecated in favor of composable templates."
# Audit trail of this API call:
 - [1] ProductCheckOnStartup: Took: 00:00:00.5295261
 - [2] ProductCheckSuccess: Node: https://test-elastik.es.eu-central-1.aws.cloud.es.io:9243/ Took: 00:00:00.4956215
 - [3] HealthyResponse: Node: https://test-elastik.es.eu-central-1.aws.cloud.es.io:9243/ Took: 00:00:00.2964671
# Request:
{"index_patterns":["pattern*"],"mappings":{"properties":{"fieldA":{"type":"keyword"},"fieldB":{"type":"keyword"}}},"version":1}
# Response:
{
  "acknowledged" : true
}

# TCP states:
  Established: 77
  TimeWait: 22
  SynSent: 1

# ThreadPool statistics:
  Worker:
    Busy: 0
    Free: 32767
    Min: 8
    Max: 32767
  IOCP:
    Busy: 1
    Free: 999
    Min: 8
    Max: 1000

With EnableVersioningApiHeader
Response contains OriginalException, following DebugInformation is present:
Invalid NEST response built from a unsuccessful (200) low level call on PUT: /_template/some-index-template?pretty=true&error_trace=true
# Warnings:
- The client is unable to verify that the server is Elasticsearch due to security privileges on the server side. Some functionality may not be compatible if the server is running an unsupported product.
# Server indicated deprecations:
- 299 Elasticsearch-8.1.2-31df9689e80bad366ac20176aa7f2371ea5eb4c1 "Legacy index templates are deprecated in favor of composable templates."
# Audit trail of this API call:
 - [1] ProductCheckOnStartup: Took: 00:00:00.5400530
 - [2] ProductCheckSuccess: Node: https://test-elastik.es.eu-central-1.aws.cloud.es.io:9243/ Took: 00:00:00.4941808
 - [3] BadResponse: Node: https://test-elastik.es.eu-central-1.aws.cloud.es.io:9243/ Took: 00:00:00.2766236
# OriginalException: Elasticsearch.Net.ElasticsearchClientException: Request failed to execute. Call: Status code 200 from: PUT /_template/some-index-template?pretty=true&error_trace=true
# Request:
{"index_patterns":["pattern*"],"mappings":{"properties":{"fieldA":{"type":"keyword"},"fieldB":{"type":"keyword"}}},"version":1}
# Response:
{
  "acknowledged" : true
}

# TCP states:
  Established: 77
  TimeWait: 19

# ThreadPool statistics:
  Worker:
    Busy: 0
    Free: 32767
    Min: 8
    Max: 32767
  IOCP:
    Busy: 1
    Free: 999
    Min: 8
    Max: 1000

@SzymonKatra I have released 7.17.1 today which includes the validation fix for .NET Framework to resolve this issue. Thanks again for raising it.


Edit Task Start and End times are incorrect

As per #1223 but for tasks

@dpaquette this fixed too?

Yeah it will be fixed for all date time inputs. It apparently isn't fixed yet but will be. Can you assign to me?

Can this be assigned to me? This is related to the javascript datetime formatting issue I mentioned in the standup today.


PropertyNotSetInConstructor + NonInvariantDocblockPropertyType for new commands (artisan make:command)

Describe the bug
When I create a new command using artisan make:command, I get the following errors:
$ php artisan make:command Example
$ vendor/bin/console
ERROR: PropertyNotSetInConstructor - app/Console/Commands/Example.php:7:7 - Property App\Console\Commands\Example::$laravel is not defined in constructor of App\Console\Commands\Example and in any methods called in the constructor (see https://psalm.dev/074)
class Example extends Command

ERROR: PropertyNotSetInConstructor - app/Console/Commands/Example.php:7:7 - Property App\Console\Commands\Example::$name is not defined in constructor of App\Console\Commands\Example and in any methods called in the constructor (see https://psalm.dev/074)
class Example extends Command

ERROR: PropertyNotSetInConstructor - app/Console/Commands/Example.php:7:7 - Property App\Console\Commands\Example::$input is not defined in constructor of App\Console\Commands\Example and in any methods called in the constructor (see https://psalm.dev/074)
class Example extends Command

ERROR: PropertyNotSetInConstructor - app/Console/Commands/Example.php:7:7 - Property App\Console\Commands\Example::$output is not defined in constructor of App\Console\Commands\Example and in any methods called in the constructor (see https://psalm.dev/074)
class Example extends Command

ERROR: NonInvariantDocblockPropertyType - app/Console/Commands/Example.php:21:15 - Property App\Console\Commands\Example::$description has type string, not invariant with Illuminate\Console\Command::$description of type null|string (see https://psalm.dev/267)
    protected $description = 'Command description';

Impacted Versions
> composer show | grep -E 'psalm|laravel'
andrey-helldar/laravel-lang-publisher v9.2.1    Publisher lang files for the Laravel Framework, Jetstream, Fortify, Cashier and Nova from Laravel-Lang/lang
andrey-helldar/laravel-support        v2.0.1    Various helper files for the Laravel and Lumen frameworks
barryvdh/laravel-ide-helper           v2.9.1    Laravel IDE Helper, generates correct PHPDocs for all Facade classes, to improve auto-completion.
beyondcode/laravel-dump-server        1.7.0     Symfony Var-Dump Server for Laravel
fruitcake/laravel-cors                v2.0.4    Adds CORS (Cross-Origin Resource Sharing) headers support in your Laravel application
laravel-lang/lang                     9.0.1     Languages for Laravel
laravel/framework                     v8.43.0   The Laravel Framework.
laravel/sanctum                       v2.11.1   Laravel Sanctum provides a featherweight authentication system for SPAs and simple APIs.
laravel/tinker                        v2.6.1    Powerful REPL for the Laravel framework.
laravel/ui                            v3.2.1    Laravel UI utilities and presets.
psalm/plugin-laravel                  v1.4.5    A Laravel plugin for Psalm
sentry/sentry-laravel                 2.5.3     Laravel SDK for Sentry (https://sentry.io)
spatie/laravel-ray                    1.17.4    Easily debug Laravel apps
vimeo/psalm                           4.7.3     A static analysis tool for finding errors in PHP applications

Additional context
For now, my workaround is

adding @psalm-suppress PropertyNotSetInConstructor to the command class' doc block, and
changing @var string to @var string|null for the protected $description property.

However, this is a bit cumbersome and especially frustrating for new developers.

As for the NonInvariantDocblockPropertyType error, this looks like a phpdoc bug in laravel/framework to me: description is never really null, because it is always set via setDescription() in Illuminate\Console\Command::__construct().

Am I correct in understanding that you got this fixed upstream in laravel? Anything left to do here?

@mr-feek I was only able to fix the NonInvariantDocblockPropertyType error upstream, not the PropertyNotSetInConstructor errors. 😕

To test this, could we run artisan make:command Example and assert that Psalm does not find any errors afterwards, or do we have to add such an Example[Command] as a stub (which is less flexible, becaus it doesn't take into account changes to the make:command command?
To fix these errors, could we just add a stub for Illuminate\Console\Command that either (a) redefines those properties with @psalm-suppress PropertyNotSetInConstructor, or (b) defines them as typed properties so that they are either unset or values of the annotated type?

I just created my first FormRequest (php artisan make:request ExampleRequest) and it caused similar errors:
ERROR: PropertyNotSetInConstructor - app/Http/Requests/ExampleRequest.php:7:7 - Property App\Http\Requests\ExampleRequest::$container is not defined in constructor of App\Http\Requests\ExampleRequest and in any methods called in the constructor (see https://psalm.dev/074)
class ExampleRequest extends FormRequest

ERROR: PropertyNotSetInConstructor - app/Http/Requests/ExampleRequest.php:7:7 - Property App\Http\Requests\ExampleRequest::$redirector is not defined in constructor of App\Http\Requests\ExampleRequest and in any methods called in the constructor (see https://psalm.dev/074)
class ExampleRequest extends FormRequest

ERROR: PropertyNotSetInConstructor - app/Http/Requests/ExampleRequest.php:7:7 - Property App\Http\Requests\ExampleRequest::$redirect is not defined in constructor of App\Http\Requests\ExampleRequest and in any methods called in the constructor (see https://psalm.dev/074)
class ExampleRequest extends FormRequest

ERROR: PropertyNotSetInConstructor - app/Http/Requests/ExampleRequest.php:7:7 - Property App\Http\Requests\ExampleRequest::$redirectRoute is not defined in constructor of App\Http\Requests\ExampleRequest and in any methods called in the constructor (see https://psalm.dev/074)
class ExampleRequest extends FormRequest

ERROR: PropertyNotSetInConstructor - app/Http/Requests/ExampleRequest.php:7:7 - Property App\Http\Requests\ExampleRequest::$redirectAction is not defined in constructor of App\Http\Requests\ExampleRequest and in any methods called in the constructor (see https://psalm.dev/074)
class ExampleRequest extends FormRequest

ERROR: PropertyNotSetInConstructor - app/Http/Requests/ExampleRequest.php:7:7 - Property App\Http\Requests\ExampleRequest::$validator is not defined in constructor of App\Http\Requests\ExampleRequest and in any methods called in the constructor (see https://psalm.dev/074)
class ExampleRequest extends FormRequest

ERROR: PropertyNotSetInConstructor - app/Http/Requests/ExampleRequest.php:7:7 - Property App\Http\Requests\ExampleRequest::$convertedFiles is not defined in constructor of App\Http\Requests\ExampleRequest and in any methods called in the constructor (see https://psalm.dev/074)
class ExampleRequest extends FormRequest

ERROR: PropertyNotSetInConstructor - app/Http/Requests/ExampleRequest.php:7:7 - Property App\Http\Requests\ExampleRequest::$userResolver is not defined in constructor of App\Http\Requests\ExampleRequest and in any methods called in the constructor (see https://psalm.dev/074)
class ExampleRequest extends FormRequest

ERROR: PropertyNotSetInConstructor - app/Http/Requests/ExampleRequest.php:7:7 - Property App\Http\Requests\ExampleRequest::$routeResolver is not defined in constructor of App\Http\Requests\ExampleRequest and in any methods called in the constructor (see https://psalm.dev/074)
class ExampleRequest extends FormRequest

ERROR: PropertyNotSetInConstructor - app/Http/Requests/ExampleRequest.php:7:7 - Property App\Http\Requests\ExampleRequest::$session is not defined in constructor of App\Http\Requests\ExampleRequest and in any methods called in the constructor (see https://psalm.dev/074)
class ExampleRequest extends FormRequest

ERROR: PropertyNotSetInConstructor - app/Http/Requests/ExampleRequest.php:7:7 - Property App\Http\Requests\ExampleRequest::$locale is not defined in constructor of App\Http\Requests\ExampleRequest and in any methods called in the constructor (see https://psalm.dev/074)
class ExampleRequest extends FormRequest

There are also PropertyNotSetInConstructor warnings when extending Illuminate\Foundation\Testing\TestCase:
psalm: PropertyNotSetInConstructor: Property Tests\Feature\ExampleTest::$app is not defined in constructor of Tests\Feature\ExampleTest or in any private or final methods called in the constructor
psalm: PropertyNotSetInConstructor: Property Tests\Feature\ExampleTest::$backupStaticAttributes is not defined in constructor of Tests\Feature\ExampleTest or in any private or final methods called in the constructor
psalm: PropertyNotSetInConstructor: Property Tests\Feature\ExampleTest::$callbackException is not defined in constructor of Tests\Feature\ExampleTest or in any private or final methods called in the constructor
psalm: PropertyNotSetInConstructor: Property Tests\Feature\ExampleTest::$runTestInSeparateProcess is not defined in constructor of Tests\Feature\ExampleTest or in any private or final methods called in the constructor

Notifications are also affected by this.