goss serve: render response format according to content negotiation

Describe the feature:
goss serve can respond to the Accept http header on incoming requests, and choose the Content-Type for the response if possible based on that.
This will allow goss serve more flexibility at run-time; previously, if more than one output format was wanted, one endpoint process+port per output format would need to be set up.
Describe the solution you'd like
(This is a retroactive ticket to collect together the PRs as much as describe the work)
This is the order to merge the PRs in:

#606 - add some unit test coverage
#608 - add some integration test coverage
#609 - add the content negotiation (with documentation)

this is a stacked PR on top of #606 and should merge cleanly.

(Afterwards, #586, but since #608 adds a new script, I'll fix that up inside that PR once #608 is merged)
Describe alternatives you've considered
Setting up one endpoint per desired goss format.

@aelsabbahy this issue acts as a "main entry point" for the cluster of PRs I've made; it overrides what I said about order in https://github.com/aelsabbahy/goss/pull/609#issuecomment-690095037 and also answers your question in https://github.com/aelsabbahy/goss/pull/608#issuecomment-691151429.

Didn't forget about this, just fell behind this weeekend on this. I'll try my best to review/merge all this before wed.

This is the order to merge the PRs in:

#606 - add some unit test coverage
#608 - add some integration test coverage
#609 - add the content negotiation (with documentation)
this is a stacked PR on top of #606 and should merge cleanly.
(Afterwards, #586, but since #608 adds a new script, I'll fix that up inside that PR once #608 is merged)

606 done/merged
608 doesn't fail build when tests fail, I don't think that was intentional (I've commented on the PR)
609 needs a rebase

Everything is merged except #609
It's currently failing the build, once that's green/merged this ticket can be closeod

@aelsabbahy thanks! I've fixed #609; I'd left in a deliberate test failure to debug a thing :(


Fix Data for SymPy Tutorial at SciPy2016

Thank you, looks good :) Just out of curiosity, did Jason Moore not make it to the tutorial?

Thank you, looks good :) Just out of curiosity, did Jason Moore not make it to the tutorial?

No, he wasn't there as he had an another tutorial just after this.

@aktech Ah that might have been quite stressful 😃
Thanks again!

@zerok Indeed.
Thanks for Merging this. :)


Can't connect to kube api after install and enabling master

root@kubepi:/home/pirate# kubectl get nodes
The connection to the server localhost:8080 was refused - did you specify the right host or port?

root@kubepi:/home/pirate#`

 kube-config info
Architecture: armv7l
Kernel: Linux 4.4.15
CPU: 4 cores x 1200 MHz

Used RAM Memory: 853 MiB
RAM Memory: 861 MiB

Used disk space: 2.6GB (2653532 KB)
Free disk space: 52GB (53704192 KB)

SD Card/deb package was built: 04-09-2016 14:39

kubernetes-on-arm:
Latest commit: c64b05d
Version: 0.8.0

systemd version: v215
docker version: v1.12.1
kubernetes client version: v1.3.6

I'm running Hypriot 1.0.0 on rpi-3
There weren't any errors on install/setup
Did I miss something?

can you please explain, what was the problem?


Cannot build solution from fresh repo clone

This issue is for a: (mark with an x)
- [X] bug report
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce
Clone repo, open solution, press F5 to build. Build error:
Severity	Code	Description	Project	File	Line	Suppression State
Error		Build:File 'C:/data/git/AzureMapsCodeSamples/AzureMapsCodeSamples/Common/typings/azure-maps-control.d.ts' not found.	AzureMapsCodeSamples	C:\data\git\AzureMapsCodeSamples\AzureMapsCodeSamples\Experimental\Solar Terminator Module\SolarTerminatorModule.ts	25
This file is not part of the repo, but is mentioned in the csproj.
Expected/desired behavior
Build out of the box
OS, Browser and Version?

Windows 10 (2004)
Edge

This repo is not meant to be cloned and ran, but instead the individual code samples should be ran on their own.
That said, I'm in the process of breaking out the typescript samples/modules into their own standalone projects. Once that is done, that will likely address the issue you are seeing.
You could also delete the solar terminator module as it is an experimental item that isn't fully functional yet.


Dev cpara upgrade

[Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.]
https://link.to/ticket
Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
What tests did you run to verify your changes? Provide instructions so we can reproduce. Please also list any relevant
details for your test configuration

[x] Test A
[x] Test B

Checklist:

[x] This review follows the Google Python Style Guide
[x] I have performed a self-review of my own code
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works(Optional)
[x] New and existing unit tests pass locally with my changes (Optional)

@ertush @bmugwe Please do a fresh PR


Document the Readme.

Make the main Readme file look clean and better.

Hey there , can I work on this issue?

Hello and welcome, @SRADHA-SURESH12!
Currently we are not expecting any README changes, because there isn't much to add.
You can work on this issue later when it becomes active.
Till then, you can look into other issues that may interest you.
Thanks! :slightly_smiling_face:


WRKLDS-728: OpenShiftAPIServerConfig: new ApiServers field to specify enabled/disabled API servers

So the openshift-apiserver has a way to tell which API servers are enabled/disabled.
Needed by:

https://github.com/openshift/openshift-apiserver/pull/366
https://github.com/openshift/cluster-openshift-apiserver-operator/pull/532

Structure looks ok to me, is there a PR to OA that is implementing this that can be tested?
CC @deads2k are there any caveats I should be aware of when reviewing OA based APIs, I appreciate the CRD validation is not needed, but perhaps there's still value in it?

https://github.com/openshift/cluster-openshift-apiserver-operator/pull/532 for OAP. OA is currently blocked by https://github.com/openshift/openshift-apiserver/pull/371.

Structure looks ok to me, is there a PR to OA that is implementing this that can be tested?

For OAO: https://github.com/openshift/cluster-openshift-apiserver-operator/pull/532/commits/f5218fdc0eb6d99c1cebd0005c31fee5b03995f8#diff-205985252904716082d4c79e59e95199823f99237580616381e402870a4a5d1eR303-R314
For OA: https://github.com/openshift/openshift-apiserver/pull/366/commits/e713c26a05085fa9a0271257b1276988bdf37a2b#diff-5d8ee1d13a6b986a8f57f6c70d2c0c2d6e05a38842c7edea6249053fd00b5e93R404-R418

/lgtm


Change slimscroll height on resize

Is there a way to change the slimscroll's height when we resize the page.
For example, if we start with a small window and then maximize it to full screen, the menu will keep scrollings until the previous height instead of going until the bottom of the page.
Adding the following code in window.onresize function did not change anything :
$(".slimscroll").slimscroll({
        height: (window.innerHeight - 200) + "px",
    }).css("width", "100%");

That's a question to the SlimScroll community. I am not sure how to change the properties of SlimScroll after initiation.
Thanks.


Add/keep python3.8 support (dict -> Dict) for generated code

Fix: https://github.com/mirumee/ariadne-codegen/issues/187

hmm @mat-sop
ideally this would not deserve a python3.8 build/CI (run) test configuration too ?

hmm @mat-sop
ideally this would not deserve a python3.8 build/CI (run) test configuration too ?

Ideally yes, but most of our tests check if the generated package looks like expected and we can't run those tests on 3.8
To include 3.8 in our ci we would need to:

Use separate python versions for generation and client tests.
Create tests that check only the behavior of the generated client.

1. seems relatively easy to do, but 2. definitely requires more work, so it may be something to consider in the future. Of course, if you want to create those tests, contributions are very welcome 😄

Use separate python versions for generation and client tests.

yes obviously :)

Create tests that check only the behavior of the generated client.

that would be out of the scope of this PR ;)
but you could have simple checks, kind of :

import every generated sub-module, must succeed, obviously.
egrep "^\w[" **/*.py ; for not top-level annotations.

eventually.


Check if 24h has passed since opening PR

Add "bake" workflow that checks if 24h have passed since opening PR

@vmilosevic can we make same change for FFE as well?

This approach doesn't work, as the pipeline schedule only works on main branch

This approach doesn't work, as the pipeline schedule only works on main branch

It's ok, we'll try to be good about it.  Do not hesitate to call people out!


Dashboard separate lines v2

Alternative design for #800, the time showing updates and pages separately, rather than stacking them cumulatively:

See https://trello.com/c/TAhR3l9m/1094-show-separate-lines-for-new-and-updates-on-the-published-pages-dashboard

Can we try and get your pre-commit code formatter working again? I really don't want to see commits going in that are just style fixes. It really breaks the ability to use history to help debug things, and clearly means it's not working for you. Let's spend 30 minutes getting it working again when you're back in.

@samuelhwilliams yes, good idea. the install_hooks.sh script works fine for commits from the command line, but seems to break commits from the GitHub app (which is handy for selecting only some lines to commit).

Closed in favour of #818


🐛 make sure the HTTP_PROXY and HTTPS_PROXY is added to the mac slave

template if proxy_url is set
Noticed that those env vars are not set on the mac slave. I think they should be set.
@aidenkeating @odra do you guys think we should add those env vars?

@wei-lee Yep, that makes sense.
Not certain, but I would have thought this (https://github.com/aerogear/digger-installer/blob/7ffa30195dac0357c60adfc65b68962ba35a430a/provision-osx/templates/create-node.xml.j2#L23)[create-node.xml.j2#L23] would need to be updated to 6 if proxy_url is set to account for the new env vars. If it works without that change it might be worth removing that int value altogether. Will try this out now.

👍  Makes sense to me as we can use this env var for both "scutil" and "networksetup" commands.

@aidenkeating right, didn't see that int value at all. Will update it


Azure CLI version 2.29.1 breaks deployment

Changing it to the latest version (2.30.2) fixed it.
cc @AnalyticJeremy

Here's what I think happened:  Last week, the login container and the CLI container were out-of-sync on their versions.  This broke the functionality.  @marvinbuss correctly pinned the CLI container to a previous version so it would match the login container.  Now, however, the login container has caught up... so we need to go back to "latest" on the CLI container.

Thanks @AnalyticJeremy and @abdale. It was actually the mismatch between the CLI Action and the Azure CLI version installed on the agent causing the issue 1-2 weeks ago. The team is working on a permanent fix, but let me fix this asap.

PR is open and will be merged soon. Thanks for reporting the bug!


Quantum Disruptor slow down is misleading

The Quantum Disruptor says that it'll make time go 20% slower (by default) when bought.
However, it seems to just subtract this 20% from the time speed multiplier, which is 1.4 in the base game, meaning that it actually only makes time go about 14.286% slower and it needs to reach 140% to (almost?) completely stop time.

So just multiply with the value, doesn't seem hard enough.

It's not hard, just unexpected.
Additionally, a user who hasn't looked in depth at the game's mechanics or how the mod works might not even know to do this.

3.10.9 will have the logic fixed but the UI will show the value times a hundred as I didn't have enough time to realize during upload so this issue will stay up.

3.10.10 release should address the messed up percentage value shown in the upgrade description.


generic handling for "sensor" types

@ogiewon, can I get your eyes on this change before submitting, since I haven't tested it for functionality?

I am testing your updated version now...  @stephack and I were discussing making the exact same change earlier.  I'll let you now how it goes.

I am testing your updated version now... @stephack and I were discussing making the exact same change earlier. I'll let you now how it goes.

I found a bug (which I assume that you already found and fixed).  I committed the change to my dev branch.

@tomwpublic - I am seeing some issue with temperature and humidity devices throwing errors in my HE logs.  Do you mind if I take a stab at refactoring some of the code to hopefully simplify it, and make it much more straightforward to add new sensor-type devices?  It may take me a few hours to get things sorted and tested, but I believe it will simplify the overall design greatly.  Thoughts?

Do you mind if I take a stab at refactoring some of the code to hopefully simplify it, and make it much more straightforward to add new sensor-type devices?

Sure thing.  For reference, I stubbed out two drivers outside of the "hubitat" namespace until (if?) this request is fulfilled: https://community.hubitat.com/t/a-word-about-ha-he-integration/63754/58
I thought those might be useful during your refactor in case drivers from other namespaces might be needed in the future.

I have updated the Parent with my latest refactored version, which supersedes this PR.


Add Cloud SOAR Audit Index documentation

Purpose of this pull request
Add Audit Features-_sourceCategory mapping available in CSOAR Delivery 2.
The table is incorporated in a new page in Cloud SOAR section.
Minor titles moving and formatting issues.
Issue number: CSOAR-907
Select the type of change:

[ ] Minor Changes - Typos, formatting, slight revisions
[X] Update Content - Revisions and updating sections
[X] New Content - New features, sections, pages, tutorials
[ ] Site and Tools - Updates, maintenance, and new packages for the site, Gatsby, React, etc

@pbaroni, per our conversation, I made this PR into a draft. When you are done placing the audit event index table where it should go, then click "Read for review" to take it out of draft and put it into review.

@jpipkin1 The feature has been released in Prod deployments: this PR can be reviewed and merged in public docs.
Thank you.


Fix the evalcs command is case sensitive

sorry forgot to ignore case

Thanks! I pushed another release.


💡 [REQUEST] -Adding a weather section[GSSOC]

[YES ] I am from GSSoC'23.
[YES ] I would like to be assigned this task.

Section
Description

Concise Description  Adding weather section through which user can also get weather of their selected location using react js,  this information can be used to make predictions about crop growth and suggest suitable planting times

Solution Proposed     WILL USE  REACT JS

Alternative Solutions
Describe any alternative solutions you can think of

Additional Context
Write any other contexts related to the feature request

Screenshots
[Provide screenshots here]

Code of Conduct
By submitting this issue, you agree to follow our Code of Conduct.

[ YES] I follow the Contributing Guidelines of this project.
[YES ] I have checked the current issues for duplicate problems.
[ YES] I have read the readme of this repository.

Done. Pushed on Frontend page


Write a LaTeX Pandoc template for better PDF output

For the moment, we manage at least the PDF output, HTML being the preferred output. You have to take the time to make a nice formatting via the LaTeX template for Pandoc

There are already a lot of template skeleton in the original upstream https://github.com/quarto-journals/article-format-template/tree/main/_extensions/aft/partials, perhaps we should look there.


Add rosbag processing service

PR Details
This PR adds an additional service to the telematics tool to parse and rosbags and push the deserialized data to a configured influxdb bucket. Requests to process the rosbag are received from the telematics web ui through NATS.
The service is configured with the required authentication parameters to influxdb, nats url and the directory where the rosbags will be stored.
When the service is launched in AWS EC2, the configured directory to read from will be the mounted S3 volume. On a local deployment, the parameter will be set to the directory where the web-ui is uploading the rosbag.
The service also requires connecting to a mysql database to update entries for each rosbag being processed. This functionality will be added as a separate enhancement. Currently TODO comments are added as placeholders.
Description

Related GitHub Issue

Related Jira Key
https://usdot-carma.atlassian.net/browse/WFD-503

Motivation and Context

How Has This Been Tested?

Types of changes

[ ] Defect fix (non-breaking change that fixes an issue)
[x] New feature (non-breaking change that adds functionality)
[ ] Breaking change (fix or feature that cause existing functionality to change)

Checklist:

[ ] I have added any new packages to the sonar-scanner.properties file
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Can we add a README.md to describe this new service and how to build this service and run tests in host machine?

Can we rename this folder to be consistent?

 Can we rename this folder to be consistent?

Will do this as a last step so we don't lose tracking on the comments


[WIP] Add noise attribute to skopt.GaussianProcessRegressor

[ ] Adds a noise attribute directly to skopt.learning.GaussianProcessRegressor
[ ] At prediction time, to predict P(f(x) | y) the kernel K(X_train, X_new) and K(X_new, X_new), should not include the noise or white kernel argument, this has been described in Eq, 2.24 of http://www.gaussianprocess.org/gpml/chapters/RW2.pdf . Note that K(X_train, X_new) and K(X_new, X_new) do not have the sigma**2 term.

What are your thoughts about decoupling the noise argument from the base_estimator argument? This makes it explicit that I have added a WhiteKernel whose noise component I can set to zero while estimating K(X_new, X_new) and K(X_train, X_new)

Where would you want to introduce the noise= keyword? As an argument to gp_minimize? As a naive user I think I'd prefer that either I give a kernel that I've designed myself and it gets used or that skopt uses its default. Having a parameter that then (maybe) modifies the kernel that I passed seems like it would make things more complicated.
Not knowledgable enough about this whole magic of brewing a kernel :(
cc @glouppe

or simply use the alpha parameter from the original scikit-learn interface? (instead of adding the WhiteKernel component)

or simply use the alpha parameter from the original scikit-learn interface?

We can do that but that assumes I need to know the amount of noise before hand right?
The alpha parameter does the right thing, but using a WhiteKernel means I need to set the noise component of the kernel to zero while doing the kernel product here (https://github.com/scikit-learn/scikit-learn/blob/master/sklearn/gaussian_process/gpr.py#L285) and here (https://github.com/scikit-learn/scikit-learn/blob/master/sklearn/gaussian_process/gpr.py#L298). What are some other ways to achieve that?

Should be ready for reviews. I would consider this as a bug.
Before this PR (n_calls=50)

After this PR (n_calls=50)

Also, not convinced by the before/after figure. Both look fine to me.

but we should be aware this trick only holds for identically distributed noise, right?

Yeah, :/. I had added that point in the initial PR (https://github.com/scikit-optimize/scikit-optimize/blob/master/skopt/optimizer/gp.py#L69)

Also, not convinced by the before/after figure. Both look fine to me.

Why do you think so, given a good number of function calls, the mean prediction should approximate the actual function right, and the first one seems a bit off?

Why do you think so, given a good number of function calls, the mean prediction should approximate the actual function right, and the first one seems a bit off?

This would be true for uniformly distributed samples, but this assumption does not hold in BO. We should only expect to be accurate in regions close of candidate optima. In the first figure, the region of high uncertainty is never ever sampled again because its LCB is larger than other parts of the input space. This is an expected behaviour of the algorithm.

Yes, that's true. Sorry about the "noise"

But I think the second cluster of points should be closer to the second local minima, but seems to be displaced by a bit in the first graph. But that just might be me nitpicking

Current coverage is 82.04% (diff: 94.11%)

Merging #225 into master will increase coverage by 0.20%

@@             master       #225   diff @@
==========================================
  Files            18         19     +1
  Lines           892        908    +16
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            730        745    +15
- Misses          162        163     +1
  Partials          0          0

Powered by Codecov. Last update d84600e...8364c7c

anything else?

I'm happy, but don't really understand much of the GP mumbojumbo so deferring to @glouppe 😃

@glouppe Your solution will not work because the provided kernel is not modified at fit time, but rather a clone of it. I have pushed another fix (with tests). Let me know what you think.

LGTM!

@glouppe Anything else?

Phew, this took more time then I had expected.

squashed and mergred

:shipit: good job!


Typo in Generated Documentation Code Block: Missing First Letter of the Code

Description
In the generated documentation for the ballerinax/financial.iso20022.payment_initiation module on Ballerina Central, there is a typo in the code block where the first letter of a code statement is missing. For example, the word "import" is displayed as "mport," omitting the initial 'i'. However, upon reviewing the module.md file, the code is correctly written, indicating that the issue occurs during the documentation generation process rather than in the source code itself.

Steps to Reproduce

Pushed the library package to Ballerina Central with my custom Ballerina organization (ajai21) for testing purposes.
Used ajai21/financial.iso20022 to locate the library in Ballerina Central.

The module.md file I used is given below
Module.md
Version
2201.10.1
Environment Details (with versions)
No response

@Ajai-Suvendran Are you using Windows? If you are, can you change the EOL sequence to LF  and try again.


Cannot load driver class: com.mysql.jdbc.Driver

I am using zeebe and zeebe simple monitor to push data to MySQL 5.6, and the following error occurred。
config:
`version: "2"
networks:
zeebe_network:
driver: bridge
services:
zeebe:
container_name: zeebe_broker
image: ghcr.io/camunda-community-hub/zeebe-with-hazelcast-exporter:8.0.5
environment:
- ZEEBE_LOG_LEVEL=info
ports:
- "26500:26500"
- "9600:9600"
- "5701:5701"
volumes:
- ../lib/zeebe-hazelcast-exporter-1.2.0.jar:/usr/local/zeebe/exporters/zeebe-hazelcast-exporter-1.2.0.jar
- ./application.yaml:/usr/local/zeebe/config/application.yaml
networks:
- zeebe_network
monitor:
container_name: zeebe_monitor
image: ghcr.io/camunda-community-hub/zeebe-simple-monitor:2.4.0
environment:
- zeebe.client.broker.gateway-address=zeebe:26500
- zeebe.client.worker.hazelcast.connection=zeebe:5701
volumes:
- ./simple-monitor-application.yaml:/application.yaml
ports:
- "8082:8082"
depends_on:
- zeebe
networks:
- zeebe_network`
`spring:
datasource:
url: jdbc:mysql://<IP_ADDRESS>:3306/test?useUnicode=true&characterEncoding=utf8&useSSL=false
username: luban_test
password: luban_test@shequ2021
driver-class-name: com.mysql.jdbc.Driver
jpa:
database-platform: org.hibernate.dialect.MySQL5Dialect
show-sql: true
generate-ddl: true
repositories:
enabled: true
hibernate:
ddl-auto: create
naming:
physical-strategy: org.hibernate.boot.model.naming.PhysicalNamingStrategyStandardImpl
mustache:
prefix: classpath:/templates/
suffix: .html
expose-request-attributes: true
data:
web:
pageable:
default-page-size: 10
server:
port: 8082
servlet:
context-path:
logging:
level:
root: ERROR
io.zeebe: INFO
io.zeebe.monitor: DEBUG
com.hazelcast: WARN`

Hi @fwqaq
the MySQL Driver was bundled with the release v2.5.1.
Looking at your config, you're using 2.4.0 == which seems to me the answer to your question.
Please upgrade to a recent version.
PS: if there's some more errors, please open a new issue.


rshell doesn't like long lines

i have the following modest prompt
/home/phil/projects/pyboard>
when I try to type the following command
cp /RED_PYB/flash/color.py /RED_PYB/flash/main.py
The cursor doesn't start a newline but loops and overtypes my prompt
leaving the following output (prompt underlined to reflect colour)
h/main.pyl/projects/pyboard> cp /RED_PYB/flash/color.py /RED_PYB/flas
         ------------------

if  press up arrow on a previous long line it doesn't work well

I think that this is an artifact of Cmd, which is what rshell uses for its core command line processor. I see this under linux, and even though it looks bad, if you just type the command and hit return it will work.
Similarly, hitting the UP arrow may not look good, but if you hit UP and RETURN it will execute the previous command.


Add page about Cargo Workspaces to the documentation

Changes
Fixes #1810

Add page about Cargo Workspaces to the documentation

Checklist

[x] An issue to be fixed by this PR is listed above.
[ ] New tests are added to ensure new features are working. Please refer to this page to see how to add a test.
[ ] ./frb_internal precommit --mode slow (or fast) is run (it internal runs code generator, does auto formatting, etc).
[ ] If this PR adds/changes features, documentations (in the ./website folder) are updated.
[ ] CI is passing. Please refer to this page to see how to solve a failed CI.

Remark for PR creator

./frb_internal --help shows utilities for development.
If fzyzcjy does not reply for a few days, maybe he just did not see it, so please ping him.

Good job! I will review soon, hopefully within a day.

@all-contributors please add @rhian-cs for doc


Consider using the Codacy code review tool

Codacy is an automated code review tool that is free for open source projects.  It provides automated linting and security checks with a comprehensive dashboard that goes into detail on the issues found.  This review is automatically triggered on every commit.
With the current drive towards cleaning up the linting errors in issue #480, setting up the project on Codacy would help towards that, I feel.  One minor issue is that while Codacy supports ESLint, it doesn't appear to support having the config setting embedded inside package.json.  In order to prepare this repo for Codacy, this would need to be moved to a separate config file.
This is a simple change to make, and the process of singing up for Codacy is pretty straightforward too as it has good integration with GitHub.  How would you feel about setting this up?  Do you think this would be a worthwhile change?

As far as I'm concerned, they don't offer anything on top of eslint, unlike codeclimate, which is also free for open source.
Let's close for now and revisit if we have to.


V27

updated substrate version to polkadot-v0.9.27

@alexand3rwilke, there is already a commit at https://github.com/paritytech/frontier/tree/polkadot-v0.9.27 for this version. Suggest to close since we already use that branch at t3rn.


codeium.nvim makes NeoVim laggy and unresponsive

I noticed that my NeoVim is laggy during typing which was annoying and slows down me affecting my productivity. After some exploration by disabled and re-enabling some installed plugins, I discovered that codeium.nvim is the source of this lagging.
Here's a screen recording shows exactly how it feels.
https://github.com/Exafunction/codeium.nvim/assets/42011920/5929a38f-601f-4a6b-9d90-23a2f8583c9d
Additional info:
NeoVim
        Version v0.9.5
codeium.vim
        version 1.8.37
        tag     1.8.37
        branch  main
        commit  289eb72

Same here. When using copilot for instance the performance is not affected. Maybe this is related to cmp?

@MuhammadSawalhy it appears you're enabling/disabling codeium.vim in your config; not codeium.nvim.
Not sure if you meant to open the issue here but you may want to open it in Exafunction/codeium.vim instead.

@cleong14 Oh, thanks I didn't notice that.
I remember that I use codeium.vim because I need the virtual text preview of the completion instead of filling the completion list of nvim-cmp with many AI-generated suggestions.
There exists already an issue asking to implement the virtual text preview feature and this comment https://github.com/Exafunction/codeium.nvim/issues/14#issuecomment-1411322109 from the maintainer says:

I plan to do this eventually, but given that codeium.vim already does this, it's pretty low on my priority list.

Now I should choose between having this feature but make the performance bad or using codeium.nvim and losing this feature!

Anyway, this issue should be in codeium.vim not here, I'll open an issue there.


It's not clear in the README how y'all recommend to invoke this tool.

Hello! So, I dunno, maybe I'm a fraud, but I feel like there's some info missing from your README describing how and when you actually use this tool. Maybe something like taking the entire contents of the https://github.com/Loomly/s3_asset_deploy#usage section and dropping it into a Rake task, something like this:
# lib/tasks/assets.rb

  namespace :assets do
    desc "Deploy assets to S3"
    task :deploy => :environment do
      manager = S3AssetDeploy::Manager("my-s3-bucket")
        manager.deploy do
          # Perform deploy to web instances in this block
        end
    end
  end

And then an example of extending your existing precompilation call to bin/rails assets:precompile assets:deploy.
Maybe this is obvious to y'all on account of building the thing, but I spent a decent amount of time trying to understand if this was all occurring automatically, or if this config was in an initializer, or what. It was only when I read the https://github.com/AssetSync/asset_sync documentation, figuring your tool might work similarly since it is informed by that one, that I reached my current assumption. I would not mind submitting a lil documentation updating PR but, honestly, I'm still not sure if this is the sensible way to use the tool.

@dhnaranjo thanks for the feedback! Super helpful. Using a rake task is exactly what we do now. Something like:
# lib/tasks/deploy.rake

require "s3_asset_deploy"

namespace :deploy do
  task precompile: :environment do
    puts "Precompiling assets..."
    sh("RAILS_ENV=production DEVISE_SECRET_KEY='secret key' SECRET_KEY_BASE='secret key' bundle exec rake assets:precompile")
  end

  task clobber_assets: :environment do
    puts "Clobbering assets..."
    sh("RAILS_ENV=production DEVISE_SECRET_KEY='secret key' SECRET_KEY_BASE='secret key' bundle exec rake assets:clobber")
  end

  task :production do
    Rake::Task["deploy:precompile"].invoke

    manager = S3AssetDeploy::Manager("my-s3-bucket")
    manager.deploy do
      # Perform deploy to web instances in this block
    end

    Rake::Task["deploy:clobber_assets"].invoke # <-- if you are running on CI where the precompiled assets dir is ephemeral, this may be unnecessary
  end
end

Your suggestion for improving the documentation is great and I'd be happy to update the README with more information.
We use CircleCI for CI/CD and this is where we run our rake task to deploy. I can also add some info to the README about how we use CircleCI for caching compiled assets to speed up compilation time if that would be helpful?

Hello! The example you've provided in that snippet is totally sufficient for my understanding. Having a CircleCI example wouldn't hurt none, tho. It'd be nice to have the outlines of a full implementation, even if it's just an example rather than like, firm instructions.

@dhnaranjo done in https://github.com/Loomly/s3_asset_deploy/pull/27 👍


Feat: Total Supply for AssetHubs #8346

Thank you for your contribution to the KodaDot - One Stop Shop for Polkadot NFTs.
👇 __ Let's make a quick check before the contribution.
PR Type

[ ] Bugfix
[x] Feature
[ ] Refactoring

Context

[x] Closes #8346
[x] ## Did your issue had any of the "$" label on it?
[x] My DOT address: Payout

please could you share a screenshot? plus we don't need to call api since you can retrieve the data from indexer

View #8346 for screenshot
Ok i'll try to fetch from indexer if it will be possible

please could you share a screenshot? plus we don't need to call api since you can retrieve the data from indexer

I'll update you soon with indexer data fetch results

please could you share a screenshot? plus we don't need to call api since you can retrieve the data from indexer

I think it's a good idea to use indexer but it works the same and also by using api  we get the same values and a lot of time api is used in many different places view #8346 for screenshots

it works fine and is it necessary to use indexer if I have an option to use api as I saw on kodadot contributors.md indexer is preferred but api can also be used I had to get the value then convert it into Json format then call a specific object so I used it

please use indexer instead, it doesn't work on some collection (i.e. /ahk/collection/u-65535)

I already knew about this is why I didn't used indexer it is just for nft pallet not for uniques pallet u-65535 this is uniques collection

please use indexer instead, it doesn't work on some collection (i.e. /ahk/collection/u-65535)

uniques is now depreciated https://wiki.polkadot.network/docs/learn-nft-pallets#uniques-pallet read this and we are moving to nft pallet

https://canary.kodadot.xyz/ahp/collection/30
vs
https://deploy-preview-8347--koda-canary.netlify.app/ahp/collection/30
your code throw error on empty collection

u-65535

this is why other stats are also not showing like items and owners

https://canary.kodadot.xyz/ahp/collection/30 vs https://deploy-preview-8347--koda-canary.netlify.app/ahp/collection/30
your code throw error on empty collection

@roiLeo  it is still not merged how is it possible to view it on canary is there some difference ?

@roiLeo genuinely your review is too good you gave me a link of destroyed collection this is why I used api which actually helps us to catch bugs

sorry but this not fair I had took this issue first 🥲 so sad I'll no more contribute if this happens

I asked you to use indexer, still no changes just comments.


PEP 8/Google Python Styling, Code review and refactor, and Style Guide.

What issue are you solving? (Give #issuenumber)
#35 Review Current Code
#53 Shorten Summaries in Docstrings
#75 Empty Username Field Problem
How do you solve it? (please write this so a human can understand it - bulletpoints are okay)
#35: Refactored source to conform with PEP 8 readability standards. No line exceeds 80 characters long, and no comment passes column 72.
#53: Rewrote or heavily modified a major portion of most, if not all docstrings. A good general rule I have learned for Python is if a docstring has a first line summary longer than one line, it probably needs to be re-written or refactored. Otherwise most of the modifications came from making the docstrings conform with Google Python Style.
#75: Rather than validating the entry text input (using this method) I opted to create a fallback instead. I toyed with the idea of a while loop forcing the widget to stay open until the text field was not empty, or possibly sending the user back to the main menu, but in practice I found this to be a more stable fix until a better one can be implemented.
def save_and_close(self, event=None):
    self.username = self.text_entry.get()  # Input data from entry text field, set username equal to input.
    if self.username.isalnum() is False:  # If input is non-alphanumeric,
        self.username = getenv('username')  # set username to local username.
    self.root.destroy()  # Close widget.

If there is something specific in your solution, that you would like the reviewer to give feedback on, tell us here:
I looked around the user guide and found that a style guide seems to have been put on the back burner. Although it wasn't marked as an issue I decided to write one up, if nothing else then just to bounce ideas off of, or to use as a starting point if it seemed reasonable. My thought process was keep it simple for inexperienced programmers, but not so wordy it felt like writing in Java. I think I found a decent median with PEP 8 formatting, and Google docstrings.
If this is your first pull request to the prog-o-meter project, we would really appreciate it if you would fill out this Google form.
This lets us know more about our contributors, and what we can do to make it easier and nicer to contribute to the prog-o-meter project.
Please submit your answer here and put an 'x' in the box below.

[ X] It is my first pull request to prog-o-meter, and I have answered the survey

Hey, awesome to have you join our project :)
I am sorry it has taken me a while to get back to you, and I am also sorry that it has not been clear enough in the issues that some of these problems have already been handled, just have not yet been merged into master.
Most of the code has already been converted to PEP8, I just haven't merged it yet. I like the refactoring of the Docstrings, the short one-liners are really short and to the point. I think some of the longer description could still be conserved in elaboration descriptions after the one-liner. Although some of it might seem to explain obvious steps, I believe it contributing to keeping the code approachable to beginners.
I have intended to update the bit about style that we have in the contributing.md for a while, but haven't been able to get around to it, so your style-guide contribution is really helpful. I have a few suggestions, that I hope you would interested in adding in. In the contributing.md guide I have added some description about how to comment control-flows, since we have a style for the porject that is not super conventional. I think it would be useful to add that to the styleguide. I also would like to suggest some changes to the language - I have tried my best to keep the documentation super friendly - a part of that is using sentence such as "We document all for, if, else, etc. statements", instead of the imperative form "Document all for, if, else, etc. statements", which sounds more like an order. I would love it if we could keep that tone in the style-guide.
Last comment I have is, that for future contributions it would be a great help for me if you only submit one feature pr. Pullrequest. It makes it easier for me to give feedback, test and eventually merge the contributions if each pullrequest just contains one new feature. Github doesn't let me accept parts of a pullrequest, so when there is too many things included in one pullrequest then if on needs some more work, or have already been solved, that means that I can't merge other parts of the contribution.
Again, I really apologize, must of the confusion here is because I haven't been making things clear in the organization of our repo. I am new to open source myself, and learning step by step, so sometimes things are not ideally done.
Can I get you to split your Pullrequest into one for 35, one for 53, one for 75 and one for the style guide? I am not sure 35 will be merged, since I will probably be merging in the earlier PEP-standard contribution which been in work for a while, howvever, we should definetely get your other contributions ready to merge in :)
If you want help splitting it up, let me know and we can work it out together :)

Sounds good. I should be able to get the issues split into separate PR's and pushed within the next few days; it's finals week so my schedule is a little chaotic... This is one of the first repositories I've contributed to so i'm learning the best ways to do things as well.

Great, thanks! No stress, and good luck on your finals!


Mac builds using builder Linux Production Engine Drone miss xcode cache

Builder Linux Production Engine Drone is being shared by different targets, including Mac ones.
By inheriting default Linux caches, it fails to specify named cache for xcode and causes cold cache on every single run.
Example:
https://luci-milo.appspot.com/ui/p/flutter/builders/prod/Linux Production Engine Drone/131820/overview
We should append xcode named cache to this builder to use cache.
Related: https://github.com/flutter/flutter/issues/117541

Fixed in https://flutter-review.googlesource.com/c/infra/+/42620


Add a follow-up flag

In backoffice. To help following currents tasks, purchase order, requests, etc. that need particular attention, it would be so great to have a follow-up flag on pages and have a section "Follow-up flag". Like in Outlook, when you can add a flag to follow emails.

requires attention flag


Feature: Filter recent Topics based on participants

To get recent topics/messages specific to a person(Maybe the user itself), there can be a filter added to do that in the participants heading.
It could be a dropdown, and participants can be chosen from it, and a number of choices can be displayed right to the participants heading. Something similar to dropdowns in github(in issues author filter etc.)

Covid Struck!! Will resume soon. :+1:


Update dip-8.md to match LIP 1 updates

Updating LIP 8  to match the changes to LIP-1 as per version 2 of LIP-1 which  simplified the flow of LIP-1

I think this type of work is really exciting and would love to dig into it!
With that being said,  I want to begin torturing Kevin:

Need more contents in abstract than “This is inclusive of pull payments, recurring payments, and auth/capture flows.”
goal / problem statement for fund pre-approval isn’t very clear, needs a better strawman example or just being broken down specifically what each protocol is trying to attempt (I like bullet points) -- for example, what is the properly end-to-end flow involving outside -- should I as a consumer pre-authorize something, will this appear in my account to confirm, it feels like something is missing here.
Why does Auth/Capture leverage PaymentCommand versus another command? We would likely still need to perform a KYC prior to TR transactions anyway and we can leverage the slightly new style of performing these types of request / responses (no need for an explicit callback can handle in a single http request / response)
If we use new commands, then the “version” of the API is irrelevant and instead it is whether or not certain commands are supported -- in fact -- we should really figure out a versioning for objects (maybe just different names) than versioning the API because the API should only change if we adjust the CommandObject format or change the format of the lower level protoocols.
The usage of headers is inconsistent # defines specifications and several fields within specifications (e.g., Auth/Capture), children then use ###, we’re skipping ##, the madness

Oh, well good news is that @danprinz from First is going to re-work this DIP.  And split it out into two as well

Oh, well good news is that @danprinz from First is going to re-work this DIP. And split it out into two as well

Good, I will bother him appropriately on his PR too then <3

feel free to re-open but this is pretty stale now


docstring on algorithms, cleanup NEP

This removes the NEP code that was accidentally introduced some time and adds docstrings on the algorithms

Codecov Report

Merging #182 (5d97fa5) into master (4a5877f) will decrease coverage by 0.24%.
The diff coverage is 9.09%.

@@            Coverage Diff             @@
##           master     #182      +/-   ##
==========================================
- Coverage   68.57%   68.33%   -0.25%
==========================================
  Files          13       13
  Lines        1623     1620       -3
==========================================
- Hits         1113     1107       -6
- Misses        510      513       +3

Impacted Files
Coverage Δ

src/afw.jl
67.07% <ø> (ø)

src/fw_algorithms.jl
80.93% <ø> (+0.25%)
:arrow_up:

src/blended_cg.jl
51.11% <9.09%> (-1.12%)
:arrow_down:

src/polytope_oracles.jl
100.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


Update conda-libmamba-solver and conda versions in conda.blz

We found that the latest version of snowflake-ml-python cannot be built by conda-build 3.26.1 (with conda 23.7.4, conda-libmamba-solver 23.7.0) because your conda.blz has a hardcoded version 23.1.0 for conda and conda-libmamba-colver https://github.com/snowflakedb/snowflake-ml-python/blob/main/third_party/rules_conda/conda.bzl#L4-L8.
As a result we got an error:
Starting local Bazel server and connecting to it...
Loading:
Loading:
Loading:
Loading: 0 packages loaded
Loading: 0 packages loaded
    currently loading: snowflake/ml
Loading: 0 packages loaded
    currently loading: snowflake/ml
Analyzing: target //snowflake/ml:wheel (1 packages loaded, 0 targets configured)
Analyzing: target //snowflake/ml:wheel (90 packages loaded, 227 targets configured)
Analyzing: target //snowflake/ml:wheel (91 packages loaded, 227 targets configured)
Analyzing: target //snowflake/ml:wheel (91 packages loaded, 227 targets configured)
Analyzing: target //snowflake/ml:wheel (91 packages loaded, 227 targets configured)
Analyzing: target //snowflake/ml:wheel (91 packages loaded, 227 targets configured)
Analyzing: target //snowflake/ml:wheel (91 packages loaded, 227 targets configured)
Analyzing: target //snowflake/ml:wheel (91 packages loaded, 227 targets configured)
INFO: Repository build_env instantiated at:
  /Users/miniconda3/envs/fin/conda-bld/snowflake-ml-python_1694689494466/work/WORKSPACE:71:13: in <toplevel>
  /Users//miniconda3/envs/fin/conda-bld/snowflake-ml-python_1694689494466/work/third_party/rules_conda/defs.bzl:19:10: in conda_create
  /private/var/tmp/_bazel_/ec07aae0a2d8b2418eaa384a250f0962/external/bazel_tools/tools/build_defs/repo/utils.bzl:233:18: in maybe
Repository rule conda_create_rule defined at:
  /Users/miniconda3/envs/fin/conda-bld/snowflake-ml-python_1694689494466/work/third_party/rules_conda/env.bzl:149:36: in <toplevel>
Analyzing: target //snowflake/ml:wheel (91 packages loaded, 227 targets configured)
ERROR: An error occurred during the fetch of repository 'build_env':
   Traceback (most recent call last):
        File "/Users/miniconda3/envs/fin/conda-bld/snowflake-ml-python_1694689494466/work/third_party/rules_conda/env.bzl", line 144, column 24, in _conda_create_impl
                _create_environment(rctx, env_name)
        File "/Users/miniconda3/envs/fin/conda-bld/snowflake-ml-python_1694689494466/work/third_party/rules_conda/env.bzl", line 88, column 30, in _create_environment
                _create_empty_environment(rctx, env_name)
        File "/Users/miniconda3/envs/fin/conda-bld/snowflake-ml-python_1694689494466/work/third_party/rules_conda/env.bzl", line 69, column 13, in _create_empty_environment
                fail("Failure creating empty environment.\nstdout: {}\nstderr: {}".format(result.stdout, result.stderr))
Error in fail: Failure creating empty environment.
stdout:
stderr: warning  libmamba Could not parse state file: Could not load cache state: [json.exception.type_error.302] type must be string, but is null
warning  libmamba Could not parse state file: Could not load cache state: [json.exception.type_error.302] type must be string, but is null
warning  libmamba Could not parse state file: Could not load cache state: [json.exception.type_error.302] type must be string, but is null
warning  libmamba Could not parse state file: Could not load cache state: [json.exception.type_error.302] type must be string, but is null

Is it possible to get the latest versions of conda and conda-libmamba-colver instead of hardcoded ones?

I tried to patch conda.blz to get the latest version of conda and conda-libmabma-solver but I got another error:
[14 / 193] [Sched] Executing genrule //snowflake/ml/modeling/feature_selection:generate_select_fwe ... (16 actions, 2 running)

ERROR: /croot/snowflake-ml-python_1694697212710/work/snowflake/ml/modeling/xgboost/BUILD.bazel:6:19: Executing genrule //snowflake/ml/modeling/xgboost:generate_xgb_regressor failed: (Exit 1): bash failed: error executing command (from target //snowflake/ml/modeling/xgboost:generate_xgb_regressor) /bin/bash -c ... (remaining 1 argument skipped)

Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging

Traceback (most recent call last):

  File "/root/.cache/bazel/_bazel_root/b8b4e8a1a8a12c85c3a3978d39b2d19c/sandbox/processwrapper-sandbox/4/execroot/SnowML/bazel-out/k8-opt-exec-DAD2D8CE/bin/codegen/estimator_autogen_tool.runfiles/SnowML/codegen/estimator_autogen_tool.py", line 17, in <module>

    from sklearn_wrapper_autogen import AutogenTool, GenMode

ModuleNotFoundError: No module named 'sklearn_wrapper_autogen'

Hi, thank you for your feedback!
We have noticed, identified these 2 issues before and we have fixed them. They will be available in the next release.

Close the issue as the fix is released.


add retries to Kubernetes Docker Runner

fixes https://github.com/spotify/hype/issues/34
Moved FluentBackoff to hype-common to be used for retries in both hype-submitter and hype-gcs packages.
@flylo @ravwojdyla or @yonromai PTAL

Codecov Report

Merging #42 into master will decrease coverage by 3.11%.
The diff coverage is 4.16%.

@@             Coverage Diff              @@
##             master      #42      +/-   ##
============================================
- Coverage     39.49%   36.38%   -3.12%
+ Complexity       72       67       -5
============================================
  Files            26       26
  Lines           871      885      +14
  Branches         65       66       +1
============================================
- Hits            344      322      -22
- Misses          508      545      +37
+ Partials         19       18       -1

Impacted Files
Coverage Δ
Complexity Δ

.../src/main/java/com/spotify/hype/FluentBackoff.java
0% <ø> (ø)
0 <0> (?)

...rc/main/java/com/spotify/hype/gcs/StagingUtil.java
62.4% <ø> (ø)
8 <0> (ø)
:arrow_down:

...om/spotify/hype/runner/KubernetesDockerRunner.java
54.24% <4.16%> (-4.75%)
13 <0> (ø)

Continue to review full report at Codecov.

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

LGTM


disable PreCheckDNS for DNS01 challenges

Many organizations which host their own DNS servers use split-DNS resolution: internal recursive resolvers return different results than external resolvers. This means that attempts to pre-check the TXT records for a DNS01 challenge using recursive resolvers from /etc/resolv.conf will fail to return results available on external authoritative servers. It also means that even the identity of the authoritative nameservers for the domain may be different.
As a result, the PreCheckDNS func will fail in these scenarios. What is needed is an option to disable pre-check on DNS01 challenges altogether.

As a workaround, if you are using acme as a library, you can sub in your own implementation of acme.PreCheckDNS (godoc) that does nothing. Not optimal, and not useful for cli, but it may work for you.

I never did like a pre check at all because of this. Remind me again why we don't simply let the acme challenge itself tell us whether it was successful?

The problem is almost all cloud dns providers have a delay between when their api accepts a change, and when the nameservers actually serve the correct records. This can be a few seconds, or potentially more if their infrastructure is "less optimized".
The safe thing is to pre-verify the nameservers are correct before asking acme validate, because the acme server will just check once and fail.

@captncraig the problem here is, see #544 is that the actualy verification is just not working well enough.
In my case, LEGO does way to many mistakes in guessing the SOA record / primary DNS and in the end, fails in doing so.
During that, both reference implementations certbot/acme.sh are working flawlessly in both environments. So what i have right now is, a LEGO lib broken in several ways in DNS-01 in exactly those cases where you need it most:

public.tld`s
in private networks
with own DNS servers ( because nothing else make sense )

i guess most of the other people would /can use http without any issue, so no need for a cloud DNS provider or anything else.
For me LEGO is breaking the core aspects of the DNS-01 need and thats a really a bummer. I would really love to see how we could fix that - maybe just :
Propasal:
Go back to the roots of the reference implementations: Let the user define a static, safe timeout (60 seconds). Then tell LE to "check for the txt record" after that timeout. Since LE is not using any private DNS servers, they will never fail to publicly determine the SOA record and thus the whole process will never fail ( and does not for certbot/acme ).
Downside is, waiting for a longer time then maybe actually needed, due to the "safe timeout".
Alternatively, make it possible to boostrap LEGO with bot strategies, the current one ( default? ) and the new one "timeout based / no DNS precheck".

Sadly running into this as well with a K8S cluster running traefik with the virtual machines leveraging a custom vnet w/DNS. It does create the txt records in the Azure DNS but attempts to verify with the DNS in the custom vnet instead.

I fixed this using typetransparent DNS servers. While this sounds dead eazy, its not, a lot of other aspects become way more complex using this mode.
"Having more private zones your forward to private DNS servers need changes"
You will need to have stub-zones with first: yes if you have several private zones and one is the authoritive to get NS lookups work, a foward-zone will stop when it did not try the entry ( which is the case for NS ) and will not recurse to a public DNS server. with first: yes, it fails and then you initial DNS server will try the resolving part, cannot and due to typetransparent will resolve using a public DNS and finds the SOA records
This is the single-most issue with LEGO which will hold be back very much of advising anybody to use this library or Traefik, especially if its a company. This all has no real impact for private usage or simple networks - but for any bigger company, this is a road-blocker.
Not sure, why LEGO's implementation here trys to be extra clever and ends up being extra-broken for all those environments, where DNS-01 is really mandatory, corporate private networks.

Closed by #700


End-to-end ICS-20 test in CI

Is your feature request related to a problem? Please describe.
Penumbra has an IBC implementation. IBC is a relatively complex protocol, especially when all of the interlocking pieces are used to execute an IBC application, like token transfers. We have an ibc component and IBC actions which handle incoming IBC messages and executes state transitions accordingly.
Describe the solution you'd like
We should have an end-to-end test, that runs in our CI, that fully exercises ICS20 transfers using the Penumbra IBC integration.
Additional context
An existing end-to-end test, that tests the IBC client update handling, exists here: https://github.com/penumbra-zone/penumbra/blob/main/component/src/ibc/component/client.rs#L514

Should this be done as part of InterchainTest, or via our own custom network integration tests? If the latter, how do we want to spin up a second chain to talk to?

We still want to exercise our Rust code, which interchaintest wouldn't do, so this is still interesting. Let's aim to finalize the IBC client implementation, re-run the relayer path between preview & testnet, and then revisit meaningful CI integration here.

Consider looking at something like https://starship.cosmology.tech/

This looks perfect for local-interchain. It allows you to write e2e with Interchaintest via the Rust driver (example repo & CI here)
This is similar to starship except we can support any language with http support (Rust, Python, and some bash is done, TS in the future).
Works for Linux, Windows, and MacOS. Prebuilt binaries found in the interchaintest/release page now

Marking as on hold: we're writing additional testinfra in order to be able to provide this capability.

related #3758.


Allow the user to add custom coins

@Senyoret1 commented on Oct 26, 2018
Currently the wallet only allows the user to select among the coins that have been added in the code. It should be possible to connect the wallet to fiber coins that have not yet been added to the code, allowing the user to manually add the information about the coin.
@gz-c , I suppose this is part of what you wanted to be added in #464 , apart from modifying the URL of the coins that are already available to the user, I am right?

@gz-c commented on Oct 26, 2018
Yes, the user would be able to add their own coin/domain pair. Once loaded, the wallet will query some url on the domain for configuration data on how to interact with the coin. Things like coin hour burn, name, possibly color scheme will be exposed.

@olemis commented on Oct 26, 2018
@gz-c I don't think /api/v1/blockchain/metadata provides enough info for that . Shall we create a new issue for skycoin/skycoin ?

@gz-c commented on Oct 30, 2018
@olemis yes create a new issue if there isn't one already


MongoCursorTimeoutException for getConversationsUnread()->getCount()

Read timed out after reading 0 bytes, waited for 30.000000 seconds.
Probably query takes more than 30sec on some circumstances?
cc @alexispeter

Chris and me added a "slow queries" metrics to bipbip.
We will replace HDD to SSD and see what's the impact.

Closing in favor of https://github.com/cargomedia/sk/issues/1203


Creation of new Facility object & fields to support Facilities in HEDA

Note: FOR INTERNAL USE ONLY. For support questions, please use the HEDA Chatter group in The Power of Us Hub.
For feature requests, please use the Ideas tab in The Power of Us Hub.

Do you want to request a feature or report a bug?

Feature

What is the current behavior?

The current functionality does not exist in HEDA.

What is the expected behavior?

This issue will result in new objects & fields and not any new logic/functionality. The user will interact with this object the same way they interact with other objects in Salesforce.
A user can navigate to a Course Offering record and see where the Couse Offering is being held. A user can manage various facilities in the educational institution.

What is the motivation / use case for changing the behavior?

Short of providing full-on Facility management, this allows an educational organization to house information with respect to where classes are being held and other school property assets. This could be a classroom location, a campus location, location of a lecture hall, location of a laboratory, or simply locations for campus buildings that don't necessarily pertain to student activity, e.g. Maintenance/IT Facilities.
1.) A Facility will look up to Account, e.g. "Department of Computer Science" account could have 3 "Locations" that are Building A, Building B, Building C, and Building A has child "Locations" that are Lecture Hall 121, Lecture Hall 131" - ex: Building A in this story would be something like "The Walter Smith Sciences Building"
2.) Course Offerings would look up to Facility. For example, Course Offering "Biology 101 - Spring 2019 - Taught by Professor Smith" would be offered in the location of Lecture Hall 121 > Building A

**lurch: add

Tracking W-031372

Included in beta release 1.73 (Beta 2)

Included in production release 1.73


Help with moment function

Hello All,
I've created a method in Vue.js to using the momentjs library to translate a value of seconds into human readable format.
When I console log the property I am attempting to pass to moment it comes out just fine. but when I pass it to the function all I ever get is "a few seconds", which after research seems like another way of saying invalid input.
timeDuration() {
      console.log(this.$moment.duration(this.devicestat.Uptime, "seconds").humanize()); - a few seconds
      console.log(this.devicestat.Uptime); - gives 88601
    },

any input?

Is this.devicestat.Uptime a string?
moment(88601, 'seconds').humanize(); // a day
moment('88601', 'seconds').humanize(); // a few seconds

It is coming in as a string...I did not catch that. Thank you. My working code is now this.
      var intTime = parseInt(this.devicestat.Uptime, 10);
      return this.$moment.duration(intTime, 'seconds').humanize();
    },

I've no doubt you'll encounter this idiom sooner or later anyway, but just an FYI that you can use unary + to do the same job:
return this.$moment.duration(+this.devicestat.Uptime, 'seconds').humanize();

Thank you. That is very helpful

Please re-open if you still have issues.


Fix: Misleading convert error when no concrete functions are given

resolves #37086

should I add the test for this?

@rushabh-v Can you please check @ashutosh1919's comments and keep us posted. Thanks!

Sorry for taking too long, @ashutosh1919 . I have edited the docstring and added the test. Can you review again, please?


Kosaraju's algorithm in Python

Hello @Kumar-laxmi . I was going through the repo and didn't find Kosaraju's implementation in Python which is the famous algorithm to find the strongly connected components . I request you to assign it to me. I would happily contribute to it.
I am contributor under SSOC'23
Thank You!

refer #763


Feature/coverage

This adds the coverage option to roi-time-series
closes #33

You can merge if you've finished your review


Add conformance of an enum to String so that SwiftPM still builds on 5.4

Motivation:
https://github.com/apple/swift-package-manager/pull/3712 accidentally made SwiftPM no longer compile using 5.4, which lacks automatic Codable synthesis for enums.
Modifications:
Make PluginAction in the PackagePlugin API conform to String as well as Decodable.
Result:
SwiftPM can build on 5.4.

@swift-ci please smoke test

@swift-ci please smoke test


Nested elements are not defined

The '+' in some level values is not explained. In fact the definition of level says it should be an integer.
More generally I think Nesting should be an attribute like default, unknownsizeallowed, etc.

Never mind. It's called recursive not nested.


Update github.dart link to new organization.

Why:
It's been quite a while, but the github.dart repo was moved to a different organization. There is no pre-existing issue for this, as I am a contributor/admin on both of the organizations mentioned.
What's being changed:
Changed the github.dart link from repo DirectMyFile/github.dart to SpinlockLabs/github.dart.
Check off the following:

[x] I have reviewed my changes in staging (look for "Automatically generated comment" and click Modified to view your latest changes).
[x] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[ ] This pull request impacts the contribution experience

[ ] I have added the 'writer impact' label
[ ] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

@lgorence
Thanks so much for opening a PR! I'll get this triaged for review :zap:

@lgorence Thanks so much for opening a PR! I'll get this triaged for review ⚡


Max size

fixes the problem with limits

max_size as soft_limit.

That is something we can explore in the future, but note that there is a circular dependency loop of include files, so writing sizeof(key_value_pair) in object.hpp will be challenging.


Configurable key system priority

Have you read the FAQ and checked for duplicate open issues?
yes
Is your feature request related to a problem? Please describe.
When using Shaka Player for Smart TV platforms, we usually have to deal with platforms that have both Widevine and Playready implemented. This is both a blessing (we can choose) and a curse (both may not work equally well, either because of Shaka Player or device issues). Managing which one to use in which case and on which platform can be annoying, especially when the only way to control this is to include or omit DRM server config.
Describe the solution you'd like
It would be great if we could specify priority for each DRM system so that Shaka could then decide which one of the available systems to use based on that. dash.js has something like that https://github.com/Dash-Industry-Forum/dash.js/pull/3107
It would also be great for resilience if Shaka Player could fall back to another configured system if one fails. Most of us are not aware of all the problems the widely diverse devices on the market may have with one DRM system or the other. Also, DRM servers may have issues at times as well.
Describe alternatives you've considered
Currently we are facing severe issues with mixed DRM and non-DRM content when using Shaka Player with PlayReady on most devices, and will solve this by forcing it to use Widevine only wherever we know it's guaranteed to be supported. However, we still have to use PlayReady for Xbox in the same app.
Additional context
none

There are a few ways you can configure this.  First, we'll only use key systems we have a license server for.  So if you want to only use Widevine, then only configure Widevine license server.  Secondly, we support multi-DRM where we'll only use supported key systems.  If the manifest specifies both Widevine and PlayReady, we'll only use the one supported by the platform; although this only happens during startup and we won't switch if it fails later.  Thirdly, the preferred way of specifying priority is with the order in the manifest.  We'll try the first one, then the second one.  This also has the advantage of being cross-player since this is specified in the DASH IOP.
Are these options enough, or is there something more you need?

As I mentioned, we can currently solve this problem by dynamically generating DRM server config. Long-term it would be nice to have some more explicit client-side control over what gets preferred.

Want to add to @MilosRasic request.
In new Edge both PR and WV are supported.
Sometimes there are manifests with CENC support with both WV and PR content protection.
In this case if we blindly set both licesne urls then the way Shaka selects the DRM system to use, IIRC, is by order they appear in the manifest.
This means that if WV is first then the less secure DRM system will be chosen.
If we want to overcome this we need to dynamically set the DRM system license url and also know what we need while we don't always have control over the API and DRM systems we work with.
The fact that now Edge Chrumiom has a strange support scheme where it sometimes support both WV and PR and sometimes only WV(Mac, Win7) makes it very difficult.
Adding a way to set the priority will solve this complexity.

That's funny, I was just about to file a very similar ticket!  We just started supporting Xfinity Flex and that supports both PR and WV.  We saw that shaka will use whichever ContentProtection is listed first in the mpd.  I'd not noticed (or I forgot) that this is a DASH-IF IoP.
While I realize that's not technically a problem it's causing our QA team to complain.  They want us to use one drm consistently across all content on a platform.  One less variable when investigating issues.
Over the years our content creation toolchain has evolved, hence some manifests have WV before PR while for others it's reversed.  Unfortunately our content team didn't think the order of ContentProtection boxes needs to be consistent, and now there's way too much content to reencode.
For a given platform I guess we can remove one of the license server urls - as you suggested - but it seems a bit risky as a general approach.  You never know if a device manufacturer will release a new model that drops one or the other DRM.

I'll tag this as a feature request and rename it accordingly.  Here's my proposal for an API:
player.configure({
  drm: {
    preferredKeySystems: [
      'com.microsoft.playready',
      'com.widevine.alpha',
    ],
  },
});

Or:
player.configure('drm.preferredKeySystems', [
  'com.microsoft.playready',
  'com.widevine.alpha',
]);

This raises the question of what the behavior should be if a key system not in the preference list has a license server configured.  In those cases, I would suggest those key systems be tried in no particular order after the ones in the preferredKeySystems list.
What do y'all think?

Hello
I believe the behavior should be the native, Edge on Windows should use
PlayReady by default for the higher security level.
David
On Mon, Dec 21, 2020 at 4:36 PM Joey Parrish<EMAIL_ADDRESS>wrote:

I'll tag this as a feature request and rename it accordingly. Here's my
proposal for an API:
player.configure({
drm: {
preferredKeySystems: [
'com.microsoft.playready',
'com.widevine.alpha',
],
},});
Or:
player.configure('drm.preferredKeySystems', [
'com.microsoft.playready',
'com.widevine.alpha',]);
This raises the question of what the behavior should be if a key system
not in the preference list has a license server configured. In those
cases, I would suggest those key systems be tried in no particular order
after the ones in the preferredKeySystems list.
What do y'all think?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/shaka-player/issues/3002#issuecomment-749208054,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADDOMLG5JUDKFCJAO3KDDOTSV65VHANCNFSM4T7QDIGA
.

--
David Eisenbacher

Hello I believe the behavior should be the native, Edge on Windows should use PlayReady by default for the higher security level. David

That would be a sane default, but I'd leave developers with the ability to change priority. There can be reason why someone might want to prefer one DRM system or another. For example, #2759 may be worked around by preferring Widevine in new Edge.

Hello
I was referring to "what behavior should be if a key system not in the
preference list has a license server configured"
It should be PR on Edge.
If a developer sets a DRM then that can override but only if it is set.
thank you
David
On Tue, Dec 22, 2020 at 9:10 AM Miloš Rašić<EMAIL_ADDRESS>wrote:

Hello I believe the behavior should be the native, Edge on Windows should use PlayReady by default for the higher security level. David
That would be a sane default, but I'd leave developers with the ability to change priority. There can be reason why someone might want to prefer one DRM system or another. For example, #2759 may be worked around by preferring Widevine in new Edge.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

--
David Eisenbacher

I don't think we are likely to hard-code a mapping of preferred key systems for multi-DRM-capable browsers.  There are lots of things that affect a choice of key system, including the cost of license services (which may come from a third-party and not the DRM provider).  We are not in a position to make those priority decisions for apps.
Also, we need to consider backward compatibility.  If a streaming service using Shaka Player is already getting the results they expect, we should avoid changing the behavior in a way that would result in selecting a different key system after a Shaka Player upgrade.
We should make it clear in release notes and docs that this new setting is one that should be set by apps whenever possible, but I don't see how we could reasonably create defaults that wouldn't harm one app or another.

@joeyparrish  / @michellezhuogg , I have seen that it is working in the master branch, shouldn't it be included in the 3.2 release? is it finished?

Yes, this is complete.


Migration guide for OMP

I got this message which says - I need to follow the migration guide: https://ohmyposh.dev/docs/migrating
Before I go ahead and try thought I to check with you, is this the right approach?
@lovesitecore

Resolved : https://github.com/Sitecore/Windows-Terminal-DevEx-improvements/pull/2


test-softlayer-rhel69-x64-1 has fallen off the network

@tellison Are you able to check on the state of this machine and see if it can be brought back to life?
Should be <IP_ADDRESS>

This machine was recently subject to a planned maintenance event.  Within the console it was marked as "Powered Off", and attempts to start it show it powered on but failing to connect to the network.
I have raised a Softlayer ticket (number 65157943) to address this connectivity problem.

@smlambert FYI

The machine is back on-line after the following kernels were removed from the server. These kernels were preventing the server from booting properly.
kernel-2.6.32-754.3.5.el6.x86_64
kernel-2.6.32-754.2.1.el6.x86_64
You can continue to yum update the server but you will want to exclude the current kernel updates for now. You can use the following command:
# yum update --exclude=kernel*
Please check it is working as expected for you, and if you are happy you can close the issue.

Will we get any notification when it is safe to re-enable them? I would imagine many of the kernel updates will be for security reasons so I'm nervous about having them disabled.

Have added that exclude to the crontab for now

Will leave this issue open for now until we can confirm that it is safe to re-enable

kernel-2.6.32-754.3.5.el6.x86_64 has been reinstalled overnight by the crontab. If I try to remove it I get the following failure - can we get clarification on what commands the softlayer team ran to safely remove the later kernel packages, since the problem is likely to recur as soon as the machine is rebooted?
[root@test-softlayer-rhel69-x64-1 ~]# rpm -e kernel-firmware-2.6.32-754.3.5.el6.noarch kernel-headers-2.6.32-754.3.5.el6.x86_64 kernel-2.6.32-754.3.5.el6.x86_64
error: Failed dependencies:
	kernel-headers >= 2.6.27-0.144.rc0.git2.fc10 is needed by (installed) libdrm-devel-2.4.65-2.el6.x86_64
	kernel-headers >= 2.2.1 is needed by (installed) compat-glibc-headers-1:2.5-46.2.x86_64
	kernel-headers is needed by (installed) glibc-headers-2.12-1.212.el6.x86_64
	kernel-headers >= 2.2.1 is needed by (installed) glibc-headers-2.12-1.212.el6.x86_64
[root@test-softlayer-rhel69-x64-1 ~]#

I've edited /boot/grub/grub.cfg to set default=1 which should select the older kernel by default when it is rebooted. Hopefully that will be enough to protect us pending an official solution.

Machine has rebooted and seems stable for now. Immediate problem resolved. Removing from this milestone.

Seems alive - closing


Pager eats color codes on Windows

click.echo_with_pager() eats the embedded ANSI colour codes, at least on my machine. I'm using Clcik 6.7 (from pip), Python 3.6.3 on Windows 10 x64.
Below is the same text, the first though the pager, and the second through the "normal" click.echo() function:

possibly related to #857

Looks like this works if a parameter is passed in for color in echo_with_pager(), e.g.

@bildzeitung Is this unclear in the documentation or can this be closed?


'Options' object has no attribute 'installed'

Describe the problem
When migrating to Django 4.1 and running manage.py migratae I get this error:
Traceback (most recent call last):
File "/Users/somewhere/server/webserver/code/FareFlyWebServer/manage.py", line 10, in
execute_from_command_line(sys.argv)
File "/Users/somewhere/server/venv/lib/python3.9/site-packages/django/core/management/init.py", line 446, in execute_from_command_line
utility.execute()
File "/Users/somewhere/server/venv/lib/python3.9/site-packages/django/core/management/init.py", line 440, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/Users/somewhere/server/venv/lib/python3.9/site-packages/django/core/management/base.py", line 402, in run_from_argv
self.execute(*args, **cmd_options)
File "/Users/somewhere/server/venv/lib/python3.9/site-packages/django/core/management/base.py", line 448, in execute
output = self.handle(*args, **options)
File "/Users/somewhere/server/venv/lib/python3.9/site-packages/django/core/management/base.py", line 96, in wrapped
res = handle_func(*args, **kwargs)
File "/Users/somewhere/server/venv/lib/python3.9/site-packages/django/core/management/commands/migrate.py", line 376, in handle
emit_post_migrate_signal(
File "/Users/somewhere/server/venv/lib/python3.9/site-packages/django/core/management/sql.py", line 52, in emit_post_migrate_signal
models.signals.post_migrate.send(
File "/Users/somewhere/server/venv/lib/python3.9/site-packages/django/dispatch/dispatcher.py", line 176, in send
return [
File "/Users/somewhere/server/venv/lib/python3.9/site-packages/django/dispatch/dispatcher.py", line 177, in
(receiver, receiver(signal=self, sender=sender, **named))
File "/Users/somewhere/server/venv/lib/python3.9/site-packages/constance/apps.py", line 27, in create_perm
if ContentType._meta.installed and Permission._meta.installed:
AttributeError: 'Options' object has no attribute 'installed'
Even if I try to run a --fake migration it won't work
System configuration

Django version: 4.1
Python version: 3.9
Django-Constance version: 2.9.0

There is a fix on the master branch which has not received a release tag yet. You can use that until a new release is available.

Thanks @VandaFarsad !

Duplicated of #493


Utilize ROS-I's Travis continuous integration (CI) scripts

ROS-I now has some pretty generic scrips for utilizing Travis CI: https://github.com/ros-industrial/industrial_ci.
Travis CI allows checks to be performed on any PR made against the repo, see here.
If there is interest, I can submit a PR against this and other swri repos to utilize this capability.

@pjreed Have you seen this?

Ah, I had missed this while I was on break.  This looks neat.
We use TeamCity for CI internally, but it would be handy to have something external that we can integrate with Github.  I'll look into this when I have the chance.

Done


https://www.must.edu.mo/en/

https://www.must.edu.mo/en/
https://www.must.edu.mo/en/scse/programme/master-science/study-plan

@letterBuild First stage of verification passed, official domain is must.edu.mo as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@letterBuild Thank you for your patience while waiting for a review and processing your request. Pull request merged.

Thank you for your time


RxJava 2

It would be great to have support for RxJava 2.

Currently there are few libraries that work with RxJava2.  Most of the popular ones are still on 1.  Once there is more community adoption we will make the changes here as well. For the time being you can use an interop library https://github.com/akarnokd/RxJava2Interop .


Not updating data after redelegation

Some people have redelegated to validators through Keplr. In REStake, most of the chains shows this change but for the "Cosmos HUB" doesn't.
I've tried deleting the cache of my browser as sometimes it helps but it keeps showing that the delegation is still in the old validator. It also throws some errors if you try any other action through REStake.
P.D: I have not seen a similar issue related to this, sorry if this is a known issue

Thanks - the public cosmoshub node that REStake uses is stalled right now, so it's showing old data. I'm going to add a warning to the site for this ASAP, and the node should be back up and running soon.


Update metrics

Update"account", "project", "publisher", "eventtype" tags for event metrics
Update "account", "project" tags for publisher metrics
Decrease publisher metrics when the publishers are deleted

@saitofun leave this pr to you

@saitofun leave this pr to you

👌


[BUG] Newly created sheet is not visible when opening workbook

Precondition:

Local disk has an excel file with a few of sheets.

Expected result:

when I open the excel file by LibreOffice, the existing sheet called "SheetJS" updates new data

Actual result:
I don't see the sheet "SheetJS" update new data although there is no error when running
Steps:
export function updateExcelWith(json: any) {
  const workbook = xlsx.readFile(pathFile);
  const mySheet = workbook.Sheets["SheetJS"];

  xlsx.utils.book_append_sheet(workbook, mySheet)

}

LibreOffice bug https://bugs.documentfoundation.org/show_bug.cgi?id=144819


count(<field>) can sometimes be much slower than count(*)

Environment

Database and version (PostgreSQL 9.4, MongoDB 3.2, etc.): PostgreSQL (possibly other SQL DBs, unsure about NoSQLs)
Ecto version (mix deps): 2.0+

Current behavior
Currently there is no way (other than using fragment) to run query like count(*). This can be problematic as count(<field>) on <field> that isn't indexed can be terribly slow (found by @mkaszubowski). The reason why this is happening is that by SQL standard COUNT(<field>) should return count of non-null values in DB so that mean it need to check wether any value in given field is empty or not, while COUNT(*) do not have this limitation and always return count of all matched rows.
Currently there is available workaround in form of count(true) in Ecto, but this isn't obvious solution and for sure isn't idiomatic.
Expected behavior
There should be count/0 function that would expand to counting all entries matching the query which I believe that most DBs have optimised enough.

Sounds good to me! PR please?

Just to clarify: the problem exists even if the fields used in count is indexed properly. The difference between two approaches is that when using count(<field>), PostgreSQL uses an index scan and still has to fetch the rows. With count(*) it can use index only scan without fetching the rows, which is way faster.

I have a closed pr about count function #2575 if you want i can modify for that situation.

@soteras a PR is definitely welcome. Although note that we are not adding new callbacks to the repo module. The new count function will belong to the Ecto.Query.API instead. Please let me know if you have any questions!

@josevalim any sources where I could learn how are aggregate functions in Ecto.Query.API handled? Because it seems a little convoluted (as most macro systems).

There is a step in the middle, which is the Ecto.Query.Planner. My suggestion is to search the codebase for a less commonly used aggregator, such as avg, and see where in the codebase we touch it.

@hauleth are you doing that or wants to?

I want to, but if you are willing then you can try as I do not have time right now to dig into it properly.

Wiadomość napisana przez Carlos Henrique<EMAIL_ADDRESS>w dniu 28.06.2018, o godz. 23:52:
@hauleth https://github.com/hauleth are you doing that or wants to?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/elixir-ecto/ecto/issues/2595#issuecomment-401184727, or mute the thread https://github.com/notifications/unsubscribe-auth/AARzNyw55jCtOSgk1HJRE3qYGkZ1fhKwks5uBVA4gaJpZM4UrhdQ.

It seem it was merged. @soteras thanks for your work.


Make a "Drag To Application" dmg for pear.ai (Mac)

Same as title, something like this: https://apple.stackexchange.com/questions/404954/how-to-create-drag-to-applications-folder-in-dmg
This is how: https://www.youtube.com/watch?v=IadcKngK3A4

What is the exact name you would like for the .dmg to have as well as the volume itself?

I've been working on the design for the .dmg as well as the icon for it, and here's what they look like as of right now.

OP!!!

dfl0, the name should be PearAI-Installer

yes exaclty

@dfl0  can you send this to me? <3

@nang-dev yeah, of course

Thank you @dfl0!

@dfl0 can u send me the dmg that is not read-only? I want to switch out the app to an updated one

@dfl0 yo! do you think you can help make the gb into white + pear green color stripes?

Legendary!!


Footnotes implementation

To create a footnote reference, add a caret and an identifier inside brackets ([^1]).
Add the footnote using another caret and number inside brackets with a colon and text ([^1]: My footnote.). You don’t have to put footnotes at the end of the document. You can put them anywhere.
Here is an example:
The implementation focus is to be fast (see benchmark) and extensible [^1]

[^1]: See [benchmark](https://github.com/kzykhys/Markbench#readme).

It'd be great to have footnote support!
There's a typo in the test filenames by the way, which is why the tests are passing.
Note that there's a MarkdownExtra test case here:
https://github.com/michelf/php-markdown/blob/lib/test/resources/php-markdown-extra.mdtest/Footnotes.text
Maybe it could be used verbatim, to ensure compatibility with that project?


Consider using another github action for labelling issues

https://github.com/andymckay/labeler is not maintained anymore, and last release is from 2021
There's a warning on each triage actions run:

apply-label
The following actions uses node12 which is deprecated and will be forced to run on node16: andymckay/labeler@master. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

@murdos : I found a reliable github-action developed by github itself: https://github.com/github/issue-labeler
I've already made it work (at my fork https://github.com/renanfranca/jhipster-lite/actions/runs/7725654397) but even though it is using node16 a warning about node20 appears.

So I created at the github-action repo an issue and pull request which updates to node20 and I am waiting to be reviewed:

https://github.com/github/issue-labeler/pull/82

@murdos : I think we can close this issue. What do you think?

@renanfranca : sure!


CalTRACK Issue: Vote on/agree to uniform testing approach

Prerequisites

[X] Are you opening this issue in the correct repository (caltrack/grid/seat)?
[X] Did you perform a search of previous Github issues to check if this issue has been previously considered?

Article reference number in CalTRACK documentation (optional): <IP_ADDRESS> and <IP_ADDRESS> indicate this is in scope, but it's not currently directly addressed in the methods
Description
I'd like to propose that this group agree to a uniform approach we would use to evaluate changes to modeling approaches and/or new modeling approaches. This is motivated by a desire to have a standard understanding of how versions/updates improve CalTRACK, and to take the burden of determining a testing approach off of group members who want to propose a change.
The testing approach the group settles on should include a process for testing and appropriate metrics (note: I'm talking about modeling here; you might probably need different metrics for other sections of the methods). The metrics should be able to be applied between models with data at different time resolutions (e.g., hourly and daily), and applied in out-of-sample testing. We'd also need to discuss what the counterfactual against which you'd compare would be (current CalTRACK? An older version?).
Ideally this approach would come with a standard data set (or a few), but that is not necessarily required.
Proposed test methodology

Open discussion for proposals from interested WG members for test methodologies (#117 proposes a testing approach for that issue that could be more broadly applied, #122 overlaps with this issue and also proposes a testing approach; #71 and #76 contain some relevant discussions, however, they're focused on model selection for particular buildings). Proposals should outline what the test methodology is, how it would be broadly applicable to CalTRACK, its use in other contexts (and why those are relevant)/prevalence in methodological literature, and the advantages and disadvantages it would offer.
The chair may choose to consolidate the list of test methodologies, if several are similar, or narrow it down if some seem infeasible.
Group members would vote on a test methodology (by consensus if possible)

Acceptance Criteria
A supermajority or consensus vote of group members would choose a testing methodology.

Another way of going about this would be to submit a test methodology with a particular issue and reach consensus on the testing protocol prior to working on the issue. There are likely going to be different testing requirements and different thresholds for different issues and probably different data requirements as well. If we try to set this up beforehand, it's likely that we'll spend all of our time creating exceptions to the rules we've laid down for ourselves.

[Pushing forward, per our working group discussion on 10/23/19.]
Restating the goal: Agree on a uniform testing approach for "empirical tests to evaluate methodological choices and assumptions" (<IP_ADDRESS>) related specifically to modeling approaches. The testing approach should include:

appropriate metrics
a standard data set
a process for testing
support for different time resolutions (e.g., hourly and daily)

In this context I'd like to define modeling approaches as the subset of CalTRACK methods used to identify  and predict the portion of a building's energy use that fluctuates due to weather. By my count 12 of 17 open CalTRACK issues fall within this scope, while five issues do not (#129 and #122 relate to testing; #132 and #135 are procedural; #125 relates to AEU). So modeling approaches appears to be the top priority for the working group.
Furthermore, it appears 10 of 12 open modeling issues are associated with improved identification (i.e. quantification) of weather related loads during the baseline period, while only two (#123 and #127) focus on prediction of energy use during reporting periods.
Given this concentration of issues, and taking McGee's comment into account ("...likely going to be different testing requirements and different thresholds for different issues..."), I propose we sharpen the focus of this issue initially on testing the identification of weather related loads. In other words, testing how well CalTRACK methods identify the building loads to be normalized during a baseline period, and how each proposed enhancement impacts that ability.
Benefits of this narrowed focus:

Original goal was quite broad and has languished; focusing on a specific subset of testing needs may be more manageable and productive;
Accurate identification of loads to be normalized is critical to all subsequent CalTRACK steps; and
Results from such testing may assist with a related goal of "establishing criteria for use cases" (<IP_ADDRESS>); in other words, what building types does CalTRACK handle best/worst?

FIRST QUESTION for Caroline (original author) and the team: Is this an acceptable narrowing of scope?
(Please click on the happy face icon at top right of this comment to log either a "thumbs up" or "thumbs down" on this question.)
If this narrowing is supported I will next propose one such testing approach, and describe how it could be applied to our first fully approved issue (#120).

Agree that a standard test data set could be useful, especially for issue 122 in testing impacts of version updates on results, but not so sure that standardized test methods will be that useful for testing all the different types of issues that may come up. Seems like it will just depend on what the issue is as to what kind of testing makes sense.


Back-end API connection

This issue tracks the connection between the backend services and the API endpoints in MEdiMate. The objective is to ensure that the backend is properly integrated with the API and provide communication between the client-side application and the server without error
Key Tasks we identified,
Setting up the necessary API endpoints in Express.js.
Ensuring configuration and environment setup for API connections.
Testing the API to confirm that it correctly handles requests and responses between the front end and the database.
Next Steps,
Assigning the tasks to the team.
Providing a detailed implementation plan and resources.

done


Update ISOs.md

Update typo and add Windows 11 option

@tiburd Please merge this PR. Thanks

Any news here @tiburd? 😊
@michaelmsonne
Thanks for the ping - this one must have fallen through the cracks... Sorry!

@tiburd that´s okay! 👍


Manually entered Groups names in ADFS Auth Provider does not work

Internal Reference: SURE-5789
Connected Rancher server to ADFS for authentication. When we try to restrict which groups are allowed to login and enter the Distinguished Name manually in the field it do not work.
When we select it from the DropDown List everything is fine.

First step: Reproduce issue and document how to setup environment for reproducing.

I was able to reproduce this with Keycloak SAML.
The issue is that when you start typing a name, you're not searching, you're specifying a new name and hence we assume it is a user.
When you click the drop-down, we show you a group - I think we only have access to the group for the current user, so we show that.

The issue is the SAML does not allow you to search. We need to re-think the UX and be clearer to the user.
I don't think showing the groups in the dropdown is useful.

In terms of the groups shown when clicking the drop down, if it works the same way as GH you're correct. The groups shown are those returned when we requests principals ... which are the ones the user is a member of

Backend issue: https://github.com/rancher/rancher/issues/44441

@nwmac do we need to update JIRA (SURE-5789) about this issue? Is it blocked by backend?

This should be unblocked by backend for 2.10.0.


No KHR_texture_transform when exporting.

I have searched far and wide but cant get to export the texture mapping of the material textures to the glb/gltf.
I have found this issue which talks about some Texture Transforms checkbox which does not exist in the current blender version 2.93. I also found some information that all textures need to have the same transform but that does not work either.
Exported material in babylonjs

Material in blender

Material graph

Check the console for warnings. Looks like
https://github.com/KhronosGroup/glTF-Blender-IO/blob/6e90fb2facf0f9be2d3970d525c58f8fb3847b99/addons/io_scene_gltf2/blender/exp/gltf2_blender_get.py#L144-L151

Thanks, that seems to solve it.

Seems that there is no bug here in code, so closing
Don't hesitate to comment if you think there is still an issue


Don't try to send overly long GET requests more than once

Unfortunately it isn't possible to tell from JavaScript whether the GET response had status code 414 (source). We could instead have a configurable maximum GET size to match the configurable maximum POST size.
Or maybe we should just tell people who are trying to send large events to use POST instead.

Has there been any further examination of this? Attempting to implement some kind of error handling when a payload (normally well under the GET limit) inadvertently includes too much/bad data.
Since we aren't able to receive the response status, we can't react to a bad event by removing it from localStorage. Playing around error event listeners didn't seem to help intercept/receive, unfortunately. Is there a suggested alternative? Currently considering checking the approximate size of a payload before making the call to sendEvent, but it seems like there should be a way to react to an error response from Snowplow.

We haven't investigated this much further, our current advice would be to switch the eventMethod to 'post' or 'beacon'.


Check subclasses too when checking for name clashes

Fixes #27460.
Not sure about the random style changes, might be related to different clang-format version.

Not sure about the random style changes, might be related to different clang-format version.

They're from clang-format 8.0, but your branch is a bit behind, I fixed those today already with c8994b5.

Thanks!

Cherry-picked for 3.1.1.


[Bug]: "Pull updates on startup" also commits and pushes

Describe the bug
Hello,
first, many thanks for this plugin and the work. I would not be able to work without Git in Obsidian :)
One thing I noticed and has become a small nuisance from time to time, though: I have the option "Pull updates on startup" on, as I want to have my latest changes pulled every time. But what I don't necessarily want is to commit/push my latest local changes at the same time.
But it seems this is not possible. Below, a screenshot of my current settings around that:

From my understanding of these settings, this should only pull on startup, but not commit/push. But it does so anyway.
Would it be possible to adjust that, maybe with a setting?!
Relevant errors (if available) from notifications or console (CTRL+SHIFT+I)
No response
Steps to reproduce

Activate settings as shown above
Restart or reload Obsidian
All previously uncommitted files get committed automatically on startup

Expected Behavior

nothing should be committed on startip

Addition context
No response
Operating system
macOS
Installation Method
None
Plugin version
2.24.2

Can you please share your other settings under the "Automatic" heading in the plugin settings?

Here a screenshot of the "Automatic" section:

That's the expected behavior. Or, at least, if you haven't used Obsidian for 6 (360 min) hours. When the last edit is 6h ago, and you start Obsidian, it first pulls because of the "Pull on startup" setting and afterward creates a backup, because of your Auto backup settings.

Unfortunately, it's not just about the backup interval. It also happens if I just did a manual backup and then restart/refresh Obsidian. It then does another backup.
Are there any other settings that can influence that?

This is an annoyance. I have three devices I work with and it happens from time to time that on the third device, which I rarely use, files which are out of date are pushed and I "loose" the content. That is "git-legal", which is fine, but I then have to go back to my laptop to sort things out manually.
Two ideas:

In some form "git stash, pull, stash pop"? Such that old changes aren't overwritten?
"git branch, pull, merge"?

I am writing this right now because that has happened the third time this week already...