fixed make target google_csv to generate l10n files for easydb5 and fylr

fixed make target google_csv to generate l10n files for easydb5 and fylr:

Makefile fixes:

only keep custom-data-type-geonames.csv as target file for csv from google sheet
delete other obsolete l10n csv files (l10n/world_names.csv and l10n/cultures.csv)
added missing language keys
remove target l10n from all, it should only be used explicitly by target google_csv

easydb-library:

updated submodule to latest master branch
do not overwrite unused commons.l10n.csv

added keys from l10n/world_names.csv to google sheet (they still need to be translated)
added other keys from frontend to google sheet (they still need to be translated)

We are no longer making changes to the easydb5-only plugins. But I'm happy to accept the pull request. If it concerns needs from fylr, the plugin is also available for fylr: https://github.com/programmfabrik/fylr-plugin-custom-data-type-geonames
With some adjustments and improvements..


Drop kube-state-metrics from kubernetes-services-monitor ServiceMonitor

Prometheus Operator already comes with kube-state-metrics job. Applying this ServiceMonitor as is will create a duplicate target with the same instance label so things like rule evaluation start failing. See Prometheus log below. So one way to solve this is to drop kube-state-metrics here and let Prometheus Operator manage it. Grafana dashboard query labels will possibly need to be updated.
level=warn ts=2020-01-09T00:22:55.396Z caller=manager.go:526 component="rule manager" group=k8s.rules msg="Evaluating rule failed" rule="record: namespace:kube_pod_container_resource_requests_cpu_cores:sum\nexpr: sum by(namespace, label_name) (sum by(namespace, pod) (kube_pod_container_resource_requests_cpu_cores{job=\"kube-state-metrics\"}\n  * on(endpoint, instance, job, namespace, pod, service) group_left(phase) (kube_pod_status_phase{phase=~\"^(Pending|Running)$\"}\n  == 1)) * on(namespace, pod) group_left(label_name) kube_pod_labels{job=\"kube-state-metrics\"})\n" err="found duplicate series for the match group {instance=\"<IP_ADDRESS>:8080\", job=\"prometheus-operator-kube-state-metrics\", namespace=\"monitoring\", pod=\"prometheus-operator-kube-state-metrics-859d6f7cd5-6xtjj\", service=\"prometheus-operator-kube-state-metrics\"} on the right hand-side of the operation: [{__name__=\"kube_pod_status_phase\", app_kubernetes_io_instance=\"prometheus-operator\", app_kubernetes_io_name=\"kube-state-metrics\", exported_namespace=\"application\", exported_pod=\"ops-api-green-664f64cdb9-d6cb8\", instance=\"<IP_ADDRESS>:8080\", job=\"prometheus-operator-kube-state-metrics\", namespace=\"monitoring\", phase=\"Running\", pod=\"prometheus-operator-kube-state-metrics-859d6f7cd5-6xtjj\", pod_name=\"prometheus-operator-kube-state-metrics-859d6f7cd5-6xtjj\", pod_template_hash=\"859d6f7cd5\", service=\"prometheus-operator-kube-state-metrics\"}, {__name__=\"kube_pod_status_phase\", app_kubernetes_io_instance=\"prometheus-operator\", app_kubernetes_io_name=\"kube-state-metrics\", exported_namespace=\"application\", exported_pod=\"ops-api-blue-7b964f754b-mznl2\", instance=\"<IP_ADDRESS>:8080\", job=\"prometheus-operator-kube-state-metrics\", namespace=\"monitoring\", phase=\"Running\", pod=\"prometheus-operator-kube-state-metrics-859d6f7cd5-6xtjj\", pod_name=\"prometheus-operator-kube-state-metrics-859d6f7cd5-6xtjj\", pod_template_hash=\"859d6f7cd5\", service=\"prometheus-operator-kube-state-metrics\"}];many-to-many matching not allowed: matching labels must be unique on one side"

Hi @eskp. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@googlebot I signed it!

Prometheus Operator already comes with kube-state-metrics job.

only in the helm chart as an option. If you install from the main repo https://github.com/coreos/prometheus-operator/blob/master/bundle.yaml it does not

Can we also drop the kubelet from this as well?

@eskp istio/installer has been integrated into the main istio/istio tree. This repo is out of the support window. If you wish to reopen this PR, feel free.


Polymorphic One to One (MorphOne) Relationship [Feature Request]

This is already supported using morphOne().

I tried importing the relationship but suggestions do not appear for MorphOne.
It works with other polymorphic relationships. Regardless I am going to give it a try.

You can use Illuminate\Database\Eloquent\Relations\MorphOne.


Asymmetric is spelled with two 'm's

There are some things where this is spelled with one 'm'. Super low prio, just wanted to give you a heads up.

Want to become a contributor by fixing it in a PR by any chance? 😉
Otherwise will fix it later. Thanks for reporting.

Released in 0.19.0


Notify user when a config entry fails to setup

Currently the only way a user can notice that a config entry failed to setup is to go to the integrations page. Even there it will only show it had an error loading.
We should add a new exception that config entries setups can throw indicating a reason. We can then show this reason to the users.
We should also create a notification to notify the user of the setup error.

Still needs to be done.


Validate plugins used by the Gradle build

Context
This PR adds validation of the plugins used by the Gradle build. It consists of two steps:

a settings plugin which applies the validation plugin to all projects of the build
a smoke test which executes validateExternalPlugins and verifies expectations

There are currently 2 plugins which fail validation: Asciidoctor and the idea-ext plugin.

@bot-gradle test this

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

@bot-gradle test this

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

@bot-gradle test this

OK, I've already cancelled the old build and triggered a new ReadyForMerge build for you.

@bot-gradle test this

Sorry some internal error occurs, please contact the administrator @blindpirate

@bot-gradle test this

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

@bot-gradle test this

OK, I've already cancelled the old build and triggered a new ReadyForMerge build for you.

@bot-gradle test this

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

@bot-gradle test QFL

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


Command-line only plugin install action

Description
This PR builds on the recent PR for adding a plugin install action. This version drops the docker use from the Ubuntu runners and relies entirely on a standardized process for both operating systems.
Testing
Passes CI and successfully completes install action on Windows and Linux with JDK 11 and JDK 17.
Check List

[x] New functionality includes testing
[x] New functionality has been documented
[x] Commits are signed per the DCO using --signoff

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

Codecov Report

Merging #2266 (134cc46) into main (e36d396) will increase coverage by 0.02%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##               main    #2266      +/-   ##
============================================
+ Coverage     61.13%   61.15%   +0.02%
- Complexity     3271     3272       +1
============================================
  Files           259      259
  Lines         18337    18337
  Branches       3248     3248
============================================
+ Hits          11210    11214       +4
+ Misses         5542     5537       -5
- Partials       1585     1586       +1

Impacted Files
Coverage Δ

...a/org/opensearch/security/tools/SecurityAdmin.java
36.60% <0.00%> (-0.24%)
:arrow_down:

...nsearch/security/dlic/rest/api/AuditApiAction.java
68.08% <0.00%> (+4.25%)
:arrow_up:

...ch/security/auditlog/routing/AsyncStoragePool.java
55.55% <0.00%> (+5.55%)
:arrow_up:

...ecurity/configuration/StaticResourceException.java
25.00% <0.00%> (+25.00%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Update: I spent today trying to incorporate the ability to define a setup.sh/.bat script in the workflow into this command-line only install action. I got it working on Linux with no docker use. The issue I am running into prevent Windows from working is described in detail here https://superuser.com/questions/1753564/how-to-pass-multiple-automatic-reponses-to-user-prompts-between-batch-files-usin.
If anyone would like to look at Linux version which does work it can be viewed on https://github.com/scrawfor99/security/tree/SetupForPluginInstall and then by swapping the os in the workflow matrix to 'ubuntu-latest' instead of windows. I also went ahead and created two files that can be used to replicate the scenario on a local windows machine or a remote desktop. The contents of the two are pasted below (they are really short)
test.bat:
@echo off
echo
echo.
echo Yes or No? (y/n)
set /p Input=Enter Yes or No:
If /I "%Input%"=="y" goto yes1
goto no1
:yes1
echo You said yes
goto yorn1
:no1
echo You said no
goto yorn1
:yorn1
echo Yes or No? (y/n)
set /p Input=Enter Yes or No:
If /I "%Input%"=="y" goto yes2
goto no2
:yes2
echo You said yes
goto yorn2
:no2
echo You said no
goto yorn2
:yorn2
echo Yes or No? (y/n)
set /p Input=Enter Yes or No:
If /I "%Input%"=="y" goto yes3
goto no3
:yes3
echo You said yes
goto exitprocess
:no3
echo You said no
goto exitprocess
:exitprocess

run_test.bat:
(echo y&&echo y&&echo n) | .\test.bat

It should work if you can call .\run_test.bat in the same directory as the test.bat file and see responses that say you said 'yes' twice and 'no' once.

For the SNAPSHOT, I think that it is always going to be there so long as we use the distributions I selected. If you check out the response I sent to Peter, there were a couple reasons I chose to make both Linux and Windows runners use the min distributions. I am not sure what you guys will think but for now I think they should always have SNAPSHOT as a suffix. I can swap to your suggestion if that changes though!

Looks good @scrawfor99 !
A general comment: See if we can have a variable that is initialized with -SNAPSHOT or <empty-string> based on the parameter passed to the script and replace current use of -SNAPSHOT with that variable. Thoughts?
In action.yml:
..
..
runs:
  using: "composite"
  env:
     useSnapshot: ${{ fromJSON('{"false": "", "true": "-SNAPSHOT"}')[inputs.use-snapshot == 'true'] }}
     # Replace all -SNAPSHOT with this variable
..
..

In plugin-install.yml:
..
..
plugin-start-script: install_demo_configuration
use-snapshot: true
..
..

Maybe this works, maybe it doesn't. But if its takes long to make this change then its not worth it.

For the SNAPSHOT, I think that it is always going to be there so long as we use the distributions I selected. If you check out the response I sent to Peter, there were a couple reasons I chose to make both Linux and Windows runners use the min distributions. I am not sure what you guys will think but for now I think they should always have SNAPSHOT as a suffix. I can swap to your suggestion if that changes though!

Thank you for your review @DarshitChanpura!
For the SNAPSHOT, I think that it is always going to be there so long as we use the distributions I selected. If you check out the response I sent to Peter, there were a couple reasons I chose to make both Linux and Windows runners use the min distributions. I am not sure what you guys will think but for now I think they should always have SNAPSHOT as a suffix. I can swap to your suggestion if that changes though!

yes having SNAPSHOT is absolutely ok. My question is more in terms of defining a boolean variable that can be passed dynamically and based on that the script decides whether to append -SNAPSHOT after the version

Closing in favor of #2271


Fix folder structure

This will fix the folder structure to tie the editor function(codelens,hover) to one folder.
ONE-DCO-1.0-Signed-off-by: Seojeonguk<EMAIL_ADDRESS>

From drafe #130


Why is Typescript a full dependency of this module?

Hello!
We've recently looked into your module, and it looks amazing. One thing that puzzled me is the fact that typescript is a dependency (not a dev-dependency).
Any reason for that decision?
Thanks!

Hey @KingDGrizzle, thank you for the feedback and I'm glad that you like the package! I believe that you are correct that typescript should be a dev-dependency as it is only needed to build the project. I will go ahead change this.


NetCDF3ToZarr: `KeyError: '__padding_16' when translating

To Reproduce:
Download https://noaa-ofs-pds.s3.amazonaws.com/ngofs2.20230929/nos.ngofs2.2ds.f001.20230929.t15z.nc , then:
from kerchunk.netCDF3 import NetCDF3ToZarr

chunks = NetCDF3ToZarr('./nos.ngofs2.2ds.f001.20230929.t15z.nc')
translated = chunks.translate()

This yields:
File [~/Developer/ocean-notebooks/env/lib/python3.10/site-packages/kerchunk/netCDF3.py:214](https://file+.vscode-resource.vscode-cdn.net/Users/matthewiannucci/Developer/ocean-notebooks/~/Developer/ocean-notebooks/env/lib/python3.10/site-packages/kerchunk/netCDF3.py:214), in NetCDF3ToZarr.translate(self)
    211 offset = start
    212 for name in dt.names:
    213     # the order of the names if fixed and important!
--> 214     var = self.variables[name]
    215     dtype = dt[name]
    216     base = dtype.base  # actual dtype

KeyError: '_padding_16'

in netcdf3.py changing this on line 210 seems make it work fine but i am not sure if this breaks anything. Im not sure the impact the padding has.
        if "record_array" in self.chunks:
            # native chunks version (no codec, no options)
            start, size, dt = self.chunks["record_array"][0]
            dt = np.dtype(dt)
            outer_shape = size // dt.itemsize
            offset = start
            for name in dt.names:
 +               if name not in variables:
 +                  continue

Any hints would help, happy to make PR if necessary

Fixed with #367


Move from gitman to bigwigspackager

You requested this in another issue. Let's discuss here.
What are the benefits you hope to gain?
Potential downsides I see:

can't run packager locally
harder to lock to specific version of a dependency

So what's the underlying requirements that are not currently being fulfilled?

My end-goal here is to simplify the CI flow since now we have way more
stages than I feel (#feelscrafts) is needed. If we could have one script to
cover both locally and in CI (so running packager to drop build locally)
would be nice, but if thats not possible I'm open to any other
simplification proposals
pt., 14 paź 2022 o 09:56 Sam @.***> napisał(a):

You requested this in another issue. Let's discuss here.
What are the benefits you hope to gain?
Potential downsides I see:

can't run packager locally
harder to lock to specific version of a dependency

So what's the underlying requirements that are not currently being
fulfilled?
—
Reply to this email directly, view it on GitHub
https://github.com/ClassicLootManager/ClassicLootManager/issues/389, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AKIXVTNHZX2P55A2DF4DAX3WDEG2VANCNFSM6AAAAAARE7OUME
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

--
Z wyrazami szacunku
Dolecki Szymon


Release v3.1.0

🐰  Release v3.1.0! 🎉 🏳🌈
Preview CHANGELOG
@piratefsh Please take a look 🙏 📿

@JuanitoFatas LGTM!

@JuanitoFatas shall we release this?

@JuanitoFatas shall we release this?

Sorry for the delay, just released.

yay, thanks!


(minor) Some functions missing prototypes

Compiling with -Werror=missing-prototypes (I have that set globally in a project), causes these:
gpibusb-firmware-arm/printf/src/printf/printf.c:483:8: error: no previous prototype for 'apply_scaling' [-Werror=missing-prototypes]
  483 | double apply_scaling(double num, struct scaling_factor normalization)
      |        ^~~~~~~~~~~~~
gpibusb-firmware-arm/printf/src/printf/printf.c:488:8: error: no previous prototype for 'unapply_scaling' [-Werror=missing-prototypes]
  488 | double unapply_scaling(double normalized, struct scaling_factor normalization)
      |        ^~~~~~~~~~~~~~~
gpibusb-firmware-arm/printf/src/printf/printf.c:493:23: error: no previous prototype for 'update_normalization' [-Werror=missing-prototypes]
  493 | struct scaling_factor update_normalization(struct scaling_factor sf, double extra_multiplicative_factor)
      |                       ^~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors

Perhaps those functions could be declared as static since (if I understand correctly) they're not meant to be used outside of printf.c ?

Sure, why not. Note this won't reach the master branch for a while, as I've just released 5.2.0.

that's fine, I'm pulling in as a git submodule here. Thanks !

I saw this tagged as fixed-on-develop, but I get this warning in GCC-9 on the develop branch (none on master):
../printf/src/printf/printf.c: At top level:
../printf/src/printf/printf.c:952:16: warning: no previous declaration for 'parse_flags' [-Wmissing-declarations]
  952 | printf_flags_t parse_flags(const char** format)
      |

@phillipjohnston : Regressed by a recent commit...

@phillipjohnston : done.


Update log4j-api, log4j-slf4j-impl to 2.21.0

About this PR
📦 Updates

org.apache.logging.log4j:log4j-api
org.apache.logging.log4j:log4j-slf4j-impl

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

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.apache.logging.log4j" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.apache.logging.log4j" }
}]

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

Superseded by #559.


Add an IGNORE keyword to the shuttle comment syntax

There are some config lines from my ~/.ssh/config file:
Host svr01
    # shuttle.name = vps/svr01
    HostName 10.250.*
Host svr02
    # shuttle.name = vps/svr02
    HostName 10.251.*
Host svr01 svr02
    Port 2222

It shows a nested menu in shuttle which is useful enough,
however an unexpected item named 'svr01 svr02' shows up in the root too.
I found ssh_config_ignore_hosts & ssh_config_ignore_keywords can solve this problem,
and I also think a keyword like # shuttle.ignore could do the same thing more conveniently?
Thanks for your great works!

Hi @QuChao
@keesfransen contributed #154 this will be in the next release and should solve your issue. :smile:


Matlab webwrite can be much faster than http.send.

ttClient for benchmark-analytic-banana:
44.138067 seconds with 'send' http engine
4.250689 seconds with 'webwrite' http engine
As a by-product, tidy up http request code into one send_data function.
However, ttClient and constructor are defaulted to the old 'send' engine for CI & debugging. The issue with webwrite is that it flags all non-OK http statuses as errors, preventing differentiation between 'true' http errors and umbridge (model) errors.

Thanks a lot @dolgov ! This is a remarkable speedup!


merge from template-arlac77-github

README.md

docs(README): update from template

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
95

Relevant Lines:
95

💛  - Coveralls


test: add unit test for pagination component

Closes #351
Description

Add unit test for pagination component

Current behavior (updates)

no

New behavior

no

Is this a breaking change (Yes/No):

no

Additional Information

Thanks!


Onboard and Perform Sandbox Testing with Sinequa

💡 Description

Blocked by awaiting SDE assistance per onboarding

Joe has been onboarded and has started working on the sandbox.
@jjacob7734 can we document some of this on the internal PDS Engineering Node wiki? link to be sent offline.


Question about search string

Hi, I am not a coder, a friend helped set it up, but autoresearcher is amazing!
My issue is that autoresearcher missed the most obvious articles no matter what I asked.
I asked about drug interactions and the herb Echinacea. I tried various search strings, from complex to a very simple one: "Echinacea, drug interactions"
Each time autoresearchers produced accurate keyword combinations to search for papers such as: 1. Echinacea, medication, interactions, 2. Herbal remedies, drug interactions, Echinacea, 3. Echinacea, prescription drugs, interactions, 4. Echinacea, supplements, drug interactions, 5. Echinacea, adverse effects, drug interactions
However, each time autoresearcher failed to identify and use the two articles listed below. Only if I actually included the very title of the papers in the search string, would autoresearcher include them.
The most obvious articles where not found and some articles with little relevance were included.
My questions are why this is and what I could do about improving the search questions?
thank you very much
These two articles were not included. The first one even has echinacea and drug interactions in its title. The second paper has a detail abstracts and also mentions echinacea and drug interactions.
A critical evaluation of drug interactions with Echinacea spp
Camille Freeman, Kevin Spelman
PMID: 18618481 DOI: 10.1002/mnfr.200700113
Review and Assessment of Medicinal Safety Data of Orally Used Echinacea Preparations
Karin Ardjomand-Woelkart, Rudolf Bauer
PMID: 26441065 DOI: 10.1055/s-0035-1558096
Keyword combinations used to search for papers: 1. Echinacea, medication, interactions, 2. Herbal remedies, drug interactions, Echinacea, 3. Echinacea, prescription drugs, interactions, 4. Echinacea, supplements, drug interactions, 5. Echinacea, adverse effects, drug interactions
Literature Review:
Echinacea is a commonly used herbal remedy for the prevention of common cold, but its efficacy remains inconclusive or contradictory (Izzo et al., 2016). Moreover, it may cause potentially serious adverse events, including herb-drug interactions (Izzo et al., 2016). A study by Qato et al. (2016) found that 15.1% of older adults were at risk for potential major drug-drug interactions, and most of these interactions involved medications and dietary supplements increasingly used in 2010-2011, including echinacea. Sparreboom et al. (2004) reported that echinacea has the potential to significantly modulate the activity of drug-metabolizing enzymes and/or the drug transporter P-glycoprotein, and participates in potential pharmacokinetic interactions with anticancer drugs. Sachar and Ma (2013) suggested that echinacea may cause herb-drug interactions through nuclear receptors (NRs) activation, resulting in NR-mediated HDIs. Parvez and Rishi (2019) warned that there exists a potential risk of herb-drug interactions leading to adverse side effects, including hepatotoxicity.
Despite the potential risks associated with echinacea use, it is still one of the most commonly used herbal remedies in the presurgical population (Tsen et al., 2000). However, the article by Chen et al. (2012) did not mention echinacea in their abstract, which focused on possible pharmacokinetic, pharmacodynamic, and herbal drug interactions occurring in the elderly.
Overall, the literature suggests that echinacea may have potential herb-drug interactions and adverse events, and caution should be exercised when using it in combination with other medications or supplements. Further research is needed to fully understand the mechanisms and clinical implications of echinacea-related herb-drug interactions.
References:
Chen, X.-W., B. Sneed, K., Pan, S.-Y., Cao, C., R. Kanwar, J., Chew, H., & Zhou, S.-F. (2012, May 1). Herb-Drug Interactions and Mechanistic and Clinical Considerations. Current Drug Metabolism. Bentham Science Publishers Ltd. http://doi.org/10.2174/1389200211209050640
Izzo, A. A., Hoon-Kim, S., Radhakrishnan, R., & Williamson, E. M. (2016, February 17). A Critical Approach to Evaluating Clinical Efficacy, Adverse Events and Drug Interactions of Herbal Remedies. Phytotherapy Research. Wiley. http://doi.org/10.1002/ptr.5591
Parvez, M. K., & Rishi, V. (2019, June 11). Herb-Drug Interactions and Hepatotoxicity. Current Drug Metabolism. Bentham Science Publishers Ltd. http://doi.org/10.2174/1389200220666190325141422
Qato, D. M., Wilder, J., Schumm, L. P., Gillet, V., & Alexander, G. C. (2016, April 1). Changes in Prescription and Over-the-Counter Medication and Dietary Supplement Use Among Older Adults in the United States, 2005 vs 2011. JAMA Internal Medicine. American Medical Association (AMA). http://doi.org/10.1001/jamainternmed.2015.8581
Sachar, M., & Ma, X. (2013, January 21). Nuclear receptors in herb–drug interactions. Drug Metabolism Reviews. Informa UK Limited. http://doi.org/10.3109/03602532.2012.753902
Sparreboom, A., Cox, M. C., Acharya, M. R., & Figg, W. D. (2004, June 15). Herbal Remedies in the United States: Potential Adverse Interactions With Anticancer Agents. Journal of Clinical Oncology. American Society of Clinical Oncology (ASCO). http://doi.org/10.1200/jco.2004.08.182
Tsen, L. C., Segal, S., Pothier, M., & Bader, A. M. (2000, July 1). Alternative Medicine Use in Presurgical Patients. Anesthesiology. Ovid Technologies (Wolters Kluwer Health). http://doi.org/10.1097/00000542-200007000-00025
Gujjarlamudi, H. (2016). Polytherapy and drug interactions in elderly. Journal of Mid-life Health. Medknow. http://doi.org/10.4103/0976-7800.191021

I came to autoresearcher after having explored Perplexity.ai
It produced a good report, which did included one of the missing papers from above:
Perplexity:
There are three search results related to drug interactions with Echinacea spp. The first two results are the same critical review article12.
The article assessed the occurrence of drug interactions with Echinacea angustifolia, E. pallida, and E. purpurea, and only eight papers containing primary data relating to drug interactions were identified.
The review concluded that herbal remedies made from E. purpurea appear to have a low potential to generate cytochrome P450 (CYP 450) drug-herb interactions including CYP 450 1A2 (CYP1A2) and CYP 450 3A4 (CYP3A4).
Currently, there are no verifiable reports of drug-herb interactions with any echinacea product12.
The third search result is a systematic literature review that evaluated documented drug interactions and contraindications associated with herbs and dietary supplements3. The review found that many available references for herbs and dietary supplements list numerous 'potential HDS–drug interactions' with little clinical significance or risk. However, the review did not specifically mention Echinacea spp.
•  https://pubmed.ncbi.nlm.nih.gov/18618481/
•  https://www.semanticscholar.org/paper/A-critical-evaluation-of-drug-interactions-with-Freeman-Spelman/d2f7887dfcc6569dd3dab0c2ceb4eca4f2f5baf4
•  https://onlinelibrary.wiley.com/doi/10.1111/j.1742-1241.2012.03008.x


: Thiết kế module

Wiki: https://github.com/HCMUS-OSSD/T1_F4/wiki update thêm chính sách.
Wiki design module: https://github.com/HCMUS-OSSD/T1_F4/wiki/Design
Release: https://github.com/HCMUS-OSSD/T1_F4/releases/tag/v3
@ndhuyfit

Hi em,
Thầy đã nhận được update của các em.
Tâhn
On Fri, Jun 16, 2017 at 8:27 PM, ducnguyen123<EMAIL_ADDRESS>wrote:

Wiki: https://github.com/HCMUS-OSSD/T1_F4/wiki update thêm chính sách.
Wiki design module: https://github.com/HCMUS-OSSD/T1_F4/wiki/Design
Release: https://github.com/HCMUS-OSSD/T1_F4/releases/tag/v3
@ndhuyfit https://github.com/ndhuyfit
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/HCMUS-OSSD/HuongdanThuchanh/issues/61, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AIuy5qHqdOZ3ura9UVlwFWNPv_tCIRqXks5sEoLTgaJpZM4N8dOm
.

--
Nguyen Duc Huy
Department of Software Engineering
Faculty of Information Technology
University of Science, VNU (HCMC)
227 Nguyen Van Cu St., Dist. 5. HCMC, Vietnam
<EMAIL_ADDRESS>- www.fit.hcmus.edu.vn/~ndhuy


Shim event.transceiver.

Description
Shim event.transceiver on older browsers (i.e. all of them at this point).
Purpose
Let's us consider removing redundant event.receiver. in favor of event.transceiver.receiver.

Note that this shim might confuse JS expecting to find the full transceiver if this member is present. I don't know that anyone is yet, and since adoption of adapter.js is voluntary, I'm hoping this won't surprise anyone.

The travis errors seem unrelated. @fippo any thoughts on how to proceed?

https://github.com/webrtc/adapter/pull/647/files#diff-93bbbc7918507cda99384ea8b2ce2fd4R54
-- this line contains an extra "s" at the end. The other failures are because of Chrome or Firefox/selenium issues and can be ignored

tests failures look sad but ok, squash once more and we're good.


Add support for z.bigint()

Currently this code
const registry = new OpenAPIRegistry();
registry.register("BigintSchema", z.bigint());

const generator = new OpenAPIGenerator(registry.definitions, "3.0.0");

try {
  const document = generator.generateDocument({
    info: {
      version: "1.0.0",
      title: "My API",
    },
    servers: [{ url: "v1" }],
  });
  console.log(document);
} catch (err) {
  console.error(err);
}

Throws this error
UnknownZodTypeError {
  message: 'Unknown zod object type, please specify `type` and other OpenAPI props using `ZodSchema.openapi`.',
  data: {
    currentSchema: {
      checks: [],
      typeName: 'ZodBigInt',
      coerce: false,
      openapi: [Object]
    },
    schemaName: 'BigintSchema'
  }
}

Ideally, it would generate an OpenAPI spec like other supported data types.

I just realized that below can be used as an alternative for an ID field (not what i expected but i can live with that).
z.bigint().optional().openapi('refname', {
    format: 'int64',
    type: 'integer',
})

However, minimum and maximum (and more) are not work since they were originally defined as number in the SchemaObject :-(

@redfoxlee thank you for that. Yes bigint should be supported on our side - it was reltively newly introduced to zod. I'll definitely add the expected support whenver I can. But yes in the mean time you've correctly identified a way to handle it.
And as for minimum and maximum I did not quite get what doesn't work?
Did you mean that:
z.bigint().min(3).max(5)

or
z.bigint().openapi('refname', {
  format: 'int64',
  type: 'integer',
  minimum: 3,
  maximum: 5
})

doesn't work? I believe the second one should still be valid. And if is the first one - yes that should be supported as well. Please let me know

Hi, @AGalabov Thank you so much! And Sorry for the late response.
I'll try this once i commit this comment!

And as for minimum and maximum I did not quite get what doesn't work?

Oh...I tried to implement this once, but failed to define minimum and maximum in the test code like this:
z.bigint().openapi('refname', {
  format: 'int64',
  type: 'integer',
  minimum: 3n,
  maximum: 5n
})

i know it's stupid...


status and volume always report 1.0 during playback

The status and volume commands correctly report the volume when the device is Idle, but when the device is playing (at least for internet hosted files) they always report the volume as 1.0.
This only appears to be a cosmetic bug, using the volume command to set the volume of a playing stream works correctly, but still (incorrectly) reports a value of 1.0.

Hmm, that is odd! The volume is reported back from the chromecast I think, although it does look like it takes the volume from the last media status sent from the chromecast. Maybe the chromecast is returning multiple media status for some reason. Let me investigate more.

OK, it looks like the chromecast returns two different volume settings. One for the receiver and one for the media being played, and these don't appear to be the same. go-chromecast is setting the receiver volume but was reporting the media volume. It will now report the receiver volume.


Add Remove silence processor

This is my attempt at creating the remove silence processor.  As far as I can tell from my tests, it works.  Here is an example of how it works:
config_split= AudioConfig(remove_silence = "all", silence_padding=200, silence_threshold=20)
rs = RemoveSilenceProcessor(config=config_split)
data = (AudioList.from_folder("data", config=config_split, processor=[rs])
        .use_partial_data(0.01, seed=42)
        .split_by_rand_pct(0.2)
        .label_empty()
        .databunch()
       )

Hi Kevin. This look really good. Can you resolve the conflicts and I will have a play around to see if it works as intended

I resolved how I think it should be.  It does stop the messaging from coming through though so if we want messages, we would need to add the messages to the processor.  Let me know if you want me to add that.

It would happen at a different spot as well, but it is more in-line with fastai's core functionality

Wondering if you've had a chance to play around with this processor and have any feedback on it.

Can't actually pull this branch. Says unknown repository.

Sorry that it took so long for me to review this.
The remove silence is a one to many method. This method returns multiple wav files that have been split up by the silence in them. Correctly you've noticed that the  pre_process_one expects only one item to be returned however your throwing away all the other files that are generated in the directory. I don't think there is a way to use the current PreProcessor class to achieve this.


WIP: Add support for isNaN in the UDF compiler

Add support for isNaN in the UDF compiler.
This implements one of the features requested in https://github.com/NVIDIA/spark-rapids/issues/541.

Can one of the admins verify this patch?

build

I have moved the compiler changes to https://github.com/NVIDIA/spark-rapids/pull/593.
Closing this PR.


 - https://1d4chan.org/wiki/Tiamat

Lore
Tiamat, the Queen of the Dragons, spreads pure hatred and suffering beneath the canopy of her wings. Her piercing stare, a beam of pure evil, is capable of vaporizing entire armies. Her talons strike quakes of terror across the land. Solid steel plate armor peels like ribbons against the chrome razors running along her spine. What damned sorcery has beguiled this infernal beast to terrorize our land once more!?
Arena
Our heroes find themselves atop a glistening summit of ash and stone with the hot wind lapping at their cowls. Below them are the fathomless depths of the unknown. Surrounding them, just beyond the edge of the precipitous climb, are the five incredible heads of Tiamat.
Boss Combat Info
Attacking: All heads are attacking at all times.
Spellcasting: Only the currently vulnerable head casts spells.
Short Ranged Bites (Melee): If there is a hero in melee range, a dragon will bite with a short ranged attack.
Long Ranged Bites (Ranged Ground-Target): If there is no such hero, a dragon will attempt a longer ranged lunging bite attack that can miss.
Elemental Spells (Various): Each Dragon head has two elemental spells/attacks, described below.
Common/Shared Abilities
Invulnerability
Description:
Each head is invulnerable at the start of the encounter. One at a time a head is chosen at random from all the heads with highest HP to become invulnerable. The players will attack the vulnerable head until its HP gets below a threshold, say 50%, and it becomes invulnerable again. At this time, another head will become vulnerable. This repeats for the duration of the encounter and all heads are dead.
Visual Effect:
A pale halo encompasses the invulnerable heads. The halo disappearing queues the players to begin their attack.
Linkens
Description:
Many of the Dragon heads' various spells require short channeling times. Having a shared linkens between them with a medium-to-long cooldown increases the difficulty and encourages teamwork.
Visual Effect:
When the Linkens is broken it will play the same animation as when Roshan's Linkens is broken.
The Five Heads
Poison
Acid rain
Acid falls from the sky, searing the armor from players. Anything hit by this ability takes damage and an armor penalty for several seconds.
Ability Type: Physical
Target Type: Point/Multiple (displays target on ground)
Animation: Acid pours from the sky in random points around the arena.
Venomous fangs
Its bite applies a slowing poison that does damage over time for a few seconds.
Ability Type: Physical
Target Type: Unit
Animation: A green hue, poison particles, and/or similar.
Fighting the Poison Head
Weaker characters will have to dodge the falling acid, while stronger characters will have to tank.
Fire
Fireball
After a very short channeling time a tremendous fireball is hurled in a line toward a random hero, piercing all obstacles, doing contact damage, DoT, and slowing attack speed for a few seconds.
Ability Type: Magical
Target Type: Point/Line (displays directional on ground)
Projectile Type: Missile-line
Animation: Bright orange fireball leaving a trail of burnt ground in its wake.
Rapidfire
An array of small damaging fireballs travels across the arena in various wave-patterns that the players will attempt to dodge. Fireballs do not pierce.
Ability Type: Magical
Target Type: Point
Projectile Type: Missile-line/Multiple
Animation: Small orange fireballs.
Fighting the Fire Head
Primary damage dealers should avoid the Fireball at all cost because it lowers their attack speed.
Lightning
Lightning Field
A number of bolts of static electricity wander about the arena in random directions doing high damage
Ability Type: Summon/Magical
Animation: Zeus lightning bolt in the form of a summoned unit.
All Spark
After targeting a random hero and channeling for a short time, cracks an instant lightning bolt of devastating damage across the arena.
Ability Type: Magical
Target Type: Point/Line (displays directional on ground)
Projectile Type: Instant
Animation: Enormous electrical spark going from the dragon to the edge of the arena.
Fighting the Lightning Head
Do not get hit by the All Spark.
Water
Depth Charge
After a short channel time, raises its head and slams into the ground, stunning units and causing a wave of water to emanate out from the point of impact, doing more damage the closer units are to the center.
Ability Type: Physical
Target Type: Point (displays target on ground)
Projectile Type: None
Animation: Crushed ground at point of impact, water ripples out from center.
Bubble
Shoots a bubble slowly out toward a random player. The bubble engulfs any unit it contacts, lifting it up into the air, removing it from combat and making it unable to attack or cast spells. Allied players can break the bubble with several melee attacks or fewer ranged attacks.
Ability Type: Magical
Target Type: Point
Projectile Type: Missile
Animation: A soap bubble.
Fighting the Water head.
Save any bubbled allies while avoiding getting stunned by Depth charge.
Shadow
Dark Light
After a moderate channeling time shoots a beam of damaging dark light in a sweeping arc
Ability Type: Magical
Target Type: Point/Arc
Projectile Type: Instant
Animation: Like Phoenix Sunray only Black/Purple.
Storm of Chaos
A fury of Dark Dragon shadow heads thrashes about in a Medium AoE around the Primary Dark head applying fury swipes and doing damage.
Ability Type: Physical
Target  Type: Melee/AoE
Animation: Multiple translucent dragon heads made out of smoke.
Fighting the Shadow head
Players will have to stay as close as possible to the head to avoid Dark Light, while being sure not to get caught in Storm of Chaos.
Design considerations
You could make this boss fight last anywhere from a minute-and-a-half to five minutes, depending on some of the data values (attack period and frequency, HP, etc) and also by changing the total number of heads. Based on the length of the encounter and the amount of work to build this hero, I'd say it'd be a high tier boss.
Another option, if you were trying to simplify, would be to simply remake the boss into a single dragon with various types of elemental attacks.

Love it! Would probably have to be a medium-high tier boss. For drops, an item that cycled through each of the dragon's abilities would be interesting. OR something that emulated her invulnerability Maybe something like:
Tiamat's Heart:
Stats:

30 Strength
10 Intelligence
200 Health

Abilities:
Draconic Endurance - When your health drops below 25%, become invulnerable and gain a large amount of health regeneration for a short period of time.
Passive
Duration: 3 Seconds
Bonus Health Regen: 8%
Cooldown: 100 Seconds
Dragontooth Necklace:
Stats:

200% Mana Regen
100 Mana
3 Armor

Abilities:
Cycles through some of the boss' spells. Every time you cast one, it moves onto the next one. Raw numbers would probably be scaled down to not break the game.
-Acid Rain
-Fireball
-All Spark
-Depth Charge
-Dark Light
Cooldown: 45 Seconds
Mana Cost: 200

I would buy those items!

uninteresting mechanics. closed.


Adjust dependencies to allow installation on Salt OneDir

This is a naive fix to adjust dependencies to match Salt OneDir 3005.1. I haven't been able to test this yet as I'm still trying to get vsphere-automation-sdk-python to install as well.
Also bumps pyVmomi to 7.0.3
Fixes #317

Looks like tests are failing due to the bumped jinja2 which has deprecated using jinja2.Markup() syntax in favour of markupsafe.Markup() per https://github.com/pallets/jinja/issues/1438

@ggiesen Seems reasonable to me - I'm pretty sure it's because our dep on salt is set to 3004>= - I don't remember which version got that markup thing busted. I'm :+1: on changing the test deps for sure to require 3005(.1?)

re-run all

Hrm. I think there's an upstream issue with that req file being missing in 3005.1 for 3.7 on mac? :thinking:

@ggiesen do you mind rebasing this on the latest main? I think that should let us get this merged in...

@waynew I moved the MacOS 3.9 tests to 3.9. I'm not sure if that's the right approach but I assume since Salt master branch only has 3.9 that it's no longer supported on 3.7 on MacOS (I'm not a Mac guy so I don't know what the Python ecosystem looks like on Mac). It's passing now except for one of the Linux tests that failed because of connectivity issues and I have no way to restart the tests.

@ggiesen that seems reasonable. I think as long as it runs on some version on mac we're good :+1: (we're basically pure Python in this module anyway so we're kinda holding Salt invariant with the tests here - but Salt has to be installed and I'm pretty sure that's what was failing)


Facebook webhook intermittent response

Hi guys. I'm facing weird issue with my facebook messenger bot.  Sometime my facebook bot not return any response even before that it returns the response using the same text message.

Please add your botId and we'll investigate

BotId is 1MoccSiti

Hi @ryzam, I've looked at a few conversations and it appears that we're sending messages to your bot, but your bot does not always send messages in response. The last message in some conversations is sent by a user, which is very unusual -- bots almost always send the last message.
Do you have any tracing inside your bot that would help us understand what's happening when we're not seeing a response message?


Parsing .angular-cli.json failed.

Bug Report or Feature Request (mark with an x)
- [x] bug report -> please search issues before submitting
- [ ] feature request

Parsing .angular-cli.json failed. Please make sure your .angular-cli.json is valid JSON. Error:
SyntaxError: Unexpected token u in JSON at position 22
I'm getting this issue no matter what I do now, from ng -v to ng new to anything ng related. What I did was merely changed to global manager to yarn and everything starts to break. I tried reinstalling @angular/cli, removing node_modules from library and nothing works. I can't find this .angular-cli.json file.
Versions.

$ node -v
v7.7.4
$ npm -v
4.1.2
Repro steps.

The log given by the failure.

Parsing .angular-cli.json failed. Please make sure your .angular-cli.json is valid JSON. Error:
SyntaxError: Unexpected token u in JSON at position 22
InvalidConfigError: Parsing .angular-cli.json failed. Please make sure your .angular-cli.json is valid JSON. Error:
SyntaxError: Unexpected token u in JSON at position 22
at Function.fromConfigPath (/usr/local/lib/node_modules/@angular/cli/models/config/config.js:74:19)
at Function.fromProject (/usr/local/lib/node_modules/@angular/cli/models/config.js:91:46)
at Object. (/usr/local/lib/node_modules/@angular/cli/commands/build.js:7:35)
at Module._compile (module.js:571:32)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:488:32)
at tryModuleLoad (module.js:447:12)
at Function.Module._load (module.js:439:3)
at Module.require (module.js:498:17)
at require (internal/module.js:20:19)
Desired functionality.

Mention any other details that might be useful.

The error looks like it's to do with malformed JSON. I'm guessing you have a trailing comma somewhere :)
Could you share it?

@MaxGoh You said you can't find the file.  Just a reminder :)

Look at character 22, there should be a u there that is out of a string. Sometimes people think that undefined is valid JSON but it's not.
Hope this helps. I'm going to close this as resolved.

This started happening on my system after trying to set the package manager to yarn. ng new stopped working. I then realized that there was a .angular-cli.json file added in my home directory, containing the following:
{
  "packageManager": undefined
}

Which isn't  valid JSON. Deleting this file fixes everything. Same issue seems to be occurring in #6087


Pending chronometer changes

Don't merge this, just testing

Looks like the only differences are the top lines, but maybe wait until #18 is merged, and then update your frequent_queries branch from there...

Sure, no problem.

Or merge from here if you like, it will be the same difference! You'll just need to resolve the conflicts.


🛠 Fix Copy button functionality in user panel

Related Issue
Closes: #212
Description of Changes
✨ Updated Copy Button Functionality ✨
The copy button on user/index.php and user/already.php has been enhanced with a copy functionality, providing a simple and user-friendly color effect without any alert or pop-up.
Here are the key changes:

Modified the HTML code for the Copy button to include an ID attribute (copyIcon).

Updated the copyLink() function to add and remove the class copied-icon to the Copy button element.

function copyLink(word) {
  console.log(word);

  // Check if navigator.clipboard is supported or not
  if (navigator.clipboard && navigator.clipboard.writeText) {
    navigator.clipboard.writeText(word);
    document.getElementById("copyIcon").classList.add("copied-icon");
  } else {
    var tempInput = document.createElement("input");
    tempInput.setAttribute("value", word);
    document.body.appendChild(tempInput);
    tempInput.select();
    document.execCommand("copy");
    document.body.removeChild(tempInput);
    document.getElementById("copyIcon").classList.add("copied-icon");
  }
}

Added a CSS rule for the .copied-icon class to change the color of the button to green.

.copied-icon {
  color: green;
}

Feel free to modify or enhance the code further if required! 💪
Checklist:

[x] My code adheres to the established style guidelines of this project.
[x] I have conducted a self-review of my code.
[x] I have included comments in areas that may be difficult to understand.
[ ] I have made corresponding updates to the project documentation.
[x] My changes have not introduced any new warnings.

Screenshots
https://github.com/apoorvaron/Shorty/assets/85815172/5f53e993-e4b3-4773-8ab5-4401da1f60c3

@apoorvaron Please Review my PR

@Nishitbaria Can you just add a text like "Copied" after clicking the button (not alert)

@Nishitbaria Can you just add a text like "Copied" after clicking the button (not alert)

I tried Copied tooltip but doesn't worked fine but still I will find a way , I might also change the Icon which is more relevant to copy and copied
Do you have any ideas up your sleeve?

@Nishitbaria Just do what you just said "Copy" and "Copied" , after 1/2 second -> "Copy"

@apoorvaron
https://github.com/apoorvaron/Shorty/assets/85815172/9ad72990-cff8-4f03-810b-b8f691258c05


Add - added a single HTML page and added name to the contributors.md

Your pull request seems good, but must be checked by a human maintainer for the following reason(s):

This PR modifies one or more pre-existing files.

Please be patient until a maintainer has time to look over your contribution.
This is an automated response, beep boop.
if you think there is a mistake, contact a maintainer

9b9e29873c19df298bf016821db36551d34a2cf7


Typing

Proposed Semver Increment Bump: [MINOR]
Changes Proposed in this Pull Request (List new items in CHANGELOG.MD)

Adds a client option: typing

(If Applicable) What Issue does it fix?
Not a fix.
Wrote it in a hurry but worked on my bot. :+1:

@kyranet @UnseenFaith

anything gonna happen?

This is a direct port of Klasa's typing, but it got improved and this PR didn't get updated (yet).

Closing this PR due to the fact that it's been almost two months with no updates, and I'm currently rewriting Komada. If you'd like to reopen this feel free too.


Replace a custom logger with off the shelf implementation

Pull Request Description
This change disables an Enso's custom logger with an existing, off the shelf logging implementation with some custom setup and appenders. The change attempts to provide a 1:1 replacement for the existing solution.
Currently configuration is a mixture of application.conf HOCON file with logback's configuration and programatically changed logger's contexts.
Important Notes
Addresses:

#7253
#6739

Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:

[ ] The documentation has been updated, if necessary.
[ ] Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
[ ] All code follows the
Scala,
Java,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.
All code has been tested:

[ ] Unit tests have been written where possible.
[ ] If GUI codebase was changed, the GUI was tested when built using ./run ide build.

Important note. Currently the slf4j classes are duplicated. They are both in:
enso$ unzip -v runner.jar | grep -i slf4j
enso$ unzip -v runtime.jar | grep -i slf4j

that's wrong. We cannot have two logging API classes and we cannot have two logging implementations!

Important note. Currently the slf4j classes are duplicated. They are both in:
enso$ unzip -v runner.jar | grep -i slf4j
enso$ unzip -v runtime.jar | grep -i slf4j

that's wrong. We cannot have two logging API classes and we cannot have two logging implementations!

slf4j comes not only from direct libs dependencies that we control but also from indirect dependencies. The assembled jar will have slf4j API classes, no matter whether I turn everything in the repo to jul (I don't plan to) or not.
Runtime has no slf4j implementation, runner does. The former uses jul, the latter does not, that's all intended and works just fine.


Font fallbacks

This is a meta/planning issue for the use of fallback fonts for glyphs missing from the current font. There are several sub-issues:

Selecting a stack of fallback fonts. This is left out-of-scope for now since it is a significant problem it its own right (Fontconfig) and since a hard-coded lift of font names can be used for testing.
Building a font fallback abstraction. The main difficulty here is determining the API, e.g. if it is an ab_glyph::Font implementation or closer to ttf_parser::Face. See https://github.com/RazrFalcon/ttf-parser/issues/42
Determining how to derive properties like ascender and line_gap — possibly just taking the first font's values or using the maximum — or perhaps the maximum over fonts used on the current line.
Compatibility with harfbuzz_rs::shape. It appears that we must use a separate run for each font, which adds more complexity.

This is partially done by #46, #47, #48, #49:

We now use fontdb to find system fonts plus a hacky list (hardcoded but adjustable at run-time) of font names as fallbacks. But this misses another problem which deserves its own issue: efficiently selecting a suitable font.
Done
We just take the lazy approach (using the first font face), which so far appears adequate.
Done

The first point deserves a new issue; otherwise this is done.


[refactor] Add a more general constructor for DFGBuilder

Simplify the lift_node test case as suggested in #240 by @acl-cqc. I.e. remove the ModuleBuilder and using a DFGBuilder as the root of the graph.
In order to do this, a more general constructor for DFGBuilder is needed, which allows the resource requirements for the DFG to be specified

Also, include updating the tests from #240?

Ah, sorry, yes I see this is there now! Not as much simplification as I'd hoped but OK, thanks

I think the right way is to

Define a GraphType that's just input/output TypeRows + Resource delta
Use that as the contents of a ClassicType::Graph (which currently has a ResourceSet and a Signature, which seems like too many ResourceSets!)
Define Signature as the new GraphType plus const_input (another TypeRow)
Then have this new method here taking a GraphType

Hmmm, hang on - if this (the first three) is the direction we can aim in, do we actually need the new method at all?

Hmmm, hang on - if this (the first three) is the direction we can aim in, do we actually need the new method at all?

I think this is the crux of it. I think I'm skeptical about the rest because I don't see why a DFGBuilder should have a signature. Obviously it does at the moment: https://github.com/CQCL-DEV/hugr/blob/17c24e3501199d5e3038884cb9520039983da145/src/builder/build_traits.rs#L78-L89

This can wait until after a Signature refactor, but:

So Signature also allows const_input, which I don't think you want here.

Why? Can DFG blocks not take const inputs?

keep new called new. It's a DFGBuilder, so I think the _df is somewhat implicit.

new/new_from_sig is probably better, but for the record I was mimicking the new_df constructor for Signature

I don't see why a DFGBuilder should have a ResourceSet

The DFG that it's building should have a ResourceSet, no? It's transforming inputs to outputs, potentially adding resource requirements in the process


Bump Metronome to version 0.6.62

High-level description
Bump Metronome
Corresponding DC/OS tickets (required)

DCOS_OSS-5988

Related tickets (optional)

D2IQ-ID JIRA title / short description.

@mesosphere-mergebot request-review @timcharper  @pierrebeitz  @DominikDary

@mesosphere-mergebot changelog-not-required not released fix

@mesosphere-mergebot test

@mesosphere-mergebot test all

@mesosphere-mergebot test all

@mesosphere-mergebot merge-it

I manually checked CI statuses and they were green, we have issue on reporting CI status back to github. Merging should be fine


First draft of KHR_materials_diffuse_transmission.

Adds support for KHR_materials_diffuse_transmission.
Not ready for merge just yet
The specification for this extension is currently marked as "Draft" and is not yet ratified, though it appears to be getting close. Staging this change in case anyone else is looking to take a peak and plug into their own renderers. I've gone so far as to just make sure this compiles and verified a basic model's properties are read from this extension. More testing is needed.

Looks like a model with this extension got added to glTF-Sample-Assets although I'm not sure what this means for the status of the extension (I'm used to the sample repositories only getting extensions after they get merged to glTF repository but the extension PR is still open): https://github.com/KhronosGroup/glTF-Sample-Assets/blob/main/Models/MandarinOrange/glTF/MandarinOrange.gltf

Looks like the extension has landed! @abwood fyi as the change needs to be rebased (extensions are gone from texture view)

@jkuhlmann fwiw I believe this is ready to merge


Fix several issues with the drawing tools

SDK-880

no box zoom anymore in mapbox gl map
onFeatureXXX callbacks need to pass a collection now
sourceName in callback functions should be correct
lines are not visible when drawing with the openlayers map in the draw example

So the draw control disabled the box zoom, see: https://github.com/mapbox/mapbox-gl-draw/blob/master/src/setup.js#L36
So we should only create the draw control when we actually need it.
In addition in #804 we had changed the interface of the onFeatureXXX callback functions to pass a collection instead of a single feature, but this had not yet been changed in the mapbox gl map component, so the drawing example was broken for the mapbox renderer, this PR also addresses this

Coverage increased (+0.002%) to 96.444% when pulling e9c7d94fd432bf3899ae5da21298584ca8f2e898 on bartvde:mapbox-zoom-box into 2430d351b095ad69d98fff3fb49f9ff5f181fefb on boundlessgeo:master.

Seeing an additional issue, since we only register the listeners once, we don't get the updated sourceName anymore if they change through the props, so better to remove and re-added I think like @milafrerichs had originally suggested but my review changed that, will fix that in here as well

Okay, I can see another issue in the draw example, with the openlayers renderer, when drawing lines, they are only visible on drawend, will investigate that one as well here

Ah there is only an edit style defined in the draw example for polygons it seems

All issues addressed, now ready for review

thanks for the review @milafrerichs


Many Styles cops moved to Layout department with Rubocop 0.49

https://github.com/bbatsov/rubocop/pull/4278

@Dahlgren thanks!! 💚

Released as v0.4.0


Onborad ADS servers to our azure sentinel

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

@SivPothana - There is no description of the issue, just the template.

Closing as no response and no action.


Reuse docstring from Class doc

I tried a bit more and again I'm stuck.
I usually document the __init__ method in the class docstring rather than in __init__ itself.
So I tried
import docrep
d = docrep.DocstringProcessor()

@d.get_sectionsf("A")
@d.dedent
class A():
    """
    Docstring from A

    Parameters
    ----------
    a : int
        Some value passed to _func.
    """
    def __init__(self, a):
        self._func(a)

    @d.dedent
    def _func(self, a):
        """
        Doc from _func

        Parameters
        ----------
        %(A.parameters)s
        """
        print(d.params)

        return

This gives:
SyntaxWarning: 'A.parameters' is not a valid key!
  @d.dedent

However, d.params has:
'A.parameters': 'a : int\n    Some value passed to _func.', 'A.other_parameters': ''

What works instead is just to document the __init__ method.
But old habits and stuff...
Is there a way around this, or am I again just not seeing how it works?
I guess the f in get_sectionsf is for function, but I don't see the difference to a class, which also has __doc__?
Best,
Thorben

Hi Thorben,
you're getting two problems here:

The uppermost decorators

@d.get_sectionsf("A")
@d.dedent

are called after the class has been compiled, i.e.__init__ doesn't know about the @d.get_sectionsf("A") call.
2. in python2 (if that is important to you), docstrings of classes cannot be modified after they are compiled. Therefore you would get problems with the @d.dedent call
But you can solve this problem by using directly the __doc__ attribute of the class in combination with the dedents and get_sections method:
import docrep
d = docrep.DocstringProcessor()

class A():
    __doc__ = d.get_sections(d.dedents("""
    Docstring from A

    Parameters
    ----------
    a : int
        Some value passed to _func.
    """), "A")

    def __init__(self, a):
        self._func(a)

    @d.dedent
    def _func(self, a):
        """
        Doc from _func

        Parameters
        ----------
        %(A.parameters)s
        """
        print(d.params)

        return

That works :)
Thanks again for the detailed answer 👍

You're welcome!


ENH Enabled https as a protocol

https is transparently supported by Thrift and upon successful testing, I propose a simple change to enable it from the Connection.

Will split the long line and push again...

Thanks, seems reasonable to me.
@andrewseidl is https supported correctly by mapd-core?

Yes and no. It is not directly supported by the main mapd_server yet, but you can proxy it through mapd_web_server, passing the --enable-https, --cert <path>, and --key <path> flags. (This is how the demos at https://www.mapd.com/demos/ are run)
No issues with an internal server I tested with, just have to make sure the certificate is valid.
:+1:

I'm not sure whether I need to do anything, or if you guys are expecting something else from me in order to accept this PR. Just let me know. I'm new to PR'ing.

Thanks @lulingar.


[Dropdown] selectOnKeydown option from docs is not implemented

Steps
Used the selectOnKeydown={false} option as mentioned in the docs:

Whether dropdown should select new option when using keyboard shortcuts. Setting to false will require enter or left click to confirm a choice.

Expected Result
Keyboard navigation moving selection, without actually changing value.
Actual Result
Value changes and dropdown closes when pressing e.g. arrow down key. + React warning:
Warning: Unknown prop `selectOnKeydown` on <div> tag. Remove this prop from the element.

Version
0.71.5
I think the problem is here: https://github.com/Semantic-Org/Semantic-UI-React/blob/master/src/modules/Dropdown/Dropdown.js#L543
This line should be IMO something like this:
if (!multiple && selectOnKeydown) this.makeSelectedItemActive(e)

Ah doh, this is the Semantic docs, not the Semantic React. Even so, it would be nice to see this option implemented. Having the value selected right away when pressing down arrow just feels really unintuitive.

Done in #2009 as selectOnNavigation.


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/27600

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/27600

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/28125

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/28125

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/30776

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/31192


Build process should publish to npm

Will revisit at a later date, for now manual publishing is preferred. The library has been moved to a Thinkful org account, this should make it easy for anyone to publish changes.


Question about conditioning

Thank you for great work and repository. Could you please clarify what does "use_same_level_conditioning_latent" flag do?
Thank you,

For example, ControlNet uses the 3-channel 512x512 image as the input to be downsampled 8 times to the same size as the 32x32 latent. When using the use_conditioning_latent option, we will encode 512x512 image with vae model to 32x32 latent and then upsample to 512x512 as the control input condition. use_same_level_conditioning_latent directly uses 32X32 latent as the control condition. There is no additional downsample steps.

Got it, thank you for prompt response.


Call distutils' finalize_options() early to fix build_ext -j…

Call the finalize_options() method of overridden distutils commands before running the configure command, in order to fix errors due to unconfigured --jobs option.  This can be reproduced by running:
$ python setup.py build_ext -j12
[…]
error: '<' not supported between instances of 'str' and 'int'

Fatal: Falling back on bundled libzmq, but config has explicitly prohibited building the libzmq extension.

Looks like this causes Windows PyPy builds to fail with:
      File "C:\Users\RUNNER~1\AppData\Local\Temp\pip-build-env-ajqw1i5n\overlay\site-packages\setuptools\command\build_ext.py", line 247, in build_extension
        if ext._needs_stub:
    AttributeError: 'Extension' object has no attribute '_needs_stub'

 full traceback
    Traceback (most recent call last):
      File "C:\Users\runneradmin\AppData\Local\Temp\cibw-run-vfed2ggk\pp37-win_amd64\build\venv\site-packages\pip\_vendor\pep517\in_process\_in_process.py", line 363, in <module>
        main()
      File "C:\Users\runneradmin\AppData\Local\Temp\cibw-run-vfed2ggk\pp37-win_amd64\build\venv\site-packages\pip\_vendor\pep517\in_process\_in_process.py", line 345, in main
        json_out['return_val'] = hook(**hook_input['kwargs'])
      File "C:\Users\runneradmin\AppData\Local\Temp\cibw-run-vfed2ggk\pp37-win_amd64\build\venv\site-packages\pip\_vendor\pep517\in_process\_in_process.py", line 262, in build_wheel
        metadata_directory)
      File "C:\Users\RUNNER~1\AppData\Local\Temp\pip-build-env-ajqw1i5n\overlay\site-packages\setuptools\build_meta.py", line 417, in build_wheel
        wheel_directory, config_settings)
      File "C:\Users\RUNNER~1\AppData\Local\Temp\pip-build-env-ajqw1i5n\overlay\site-packages\setuptools\build_meta.py", line 401, in _build_with_temp_dir
        self.run_setup()
      File "C:\Users\RUNNER~1\AppData\Local\Temp\pip-build-env-ajqw1i5n\overlay\site-packages\setuptools\build_meta.py", line 338, in run_setup
        exec(code, locals())
      File "<string>", line 1369, in <module>
      File "C:\Users\RUNNER~1\AppData\Local\Temp\pip-build-env-ajqw1i5n\overlay\site-packages\setuptools\__init__.py", line 107, in setup
        return distutils.core.setup(**attrs)
      File "C:\Users\RUNNER~1\AppData\Local\Temp\pip-build-env-ajqw1i5n\overlay\site-packages\setuptools\_distutils\core.py", line 185, in setup
        return run_commands(dist)
      File "C:\Users\RUNNER~1\AppData\Local\Temp\pip-build-env-ajqw1i5n\overlay\site-packages\setuptools\_distutils\core.py", line 201, in run_commands
        dist.run_commands()
      File "C:\Users\RUNNER~1\AppData\Local\Temp\pip-build-env-ajqw1i5n\overlay\site-packages\setuptools\_distutils\dist.py", line 969, in run_commands
        self.run_command(cmd)
      File "C:\Users\RUNNER~1\AppData\Local\Temp\pip-build-env-ajqw1i5n\overlay\site-packages\setuptools\dist.py", line 1244, in run_command
        super().run_command(command)
      File "C:\Users\RUNNER~1\AppData\Local\Temp\pip-build-env-ajqw1i5n\overlay\site-packages\setuptools\_distutils\dist.py", line 988, in run_command
        cmd_obj.run()
      File "C:\Users\RUNNER~1\AppData\Local\Temp\pip-build-env-ajqw1i5n\overlay\site-packages\wheel\bdist_wheel.py", line 343, in run
        self.run_command("build")
      File "C:\Users\RUNNER~1\AppData\Local\Temp\pip-build-env-ajqw1i5n\overlay\site-packages\setuptools\_distutils\cmd.py", line 318, in run_command
        self.distribution.run_command(command)
      File "C:\Users\RUNNER~1\AppData\Local\Temp\pip-build-env-ajqw1i5n\overlay\site-packages\setuptools\dist.py", line 1244, in run_command
        super().run_command(command)
      File "C:\Users\RUNNER~1\AppData\Local\Temp\pip-build-env-ajqw1i5n\overlay\site-packages\setuptools\_distutils\dist.py", line 988, in run_command
        cmd_obj.run()
      File "C:\Users\RUNNER~1\AppData\Local\Temp\pip-build-env-ajqw1i5n\overlay\site-packages\setuptools\_distutils\command\build.py", line 131, in run
        self.run_command(cmd_name)
      File "C:\Users\RUNNER~1\AppData\Local\Temp\pip-build-env-ajqw1i5n\overlay\site-packages\setuptools\_distutils\cmd.py", line 318, in run_command
        self.distribution.run_command(command)
      File "C:\Users\RUNNER~1\AppData\Local\Temp\pip-build-env-ajqw1i5n\overlay\site-packages\setuptools\dist.py", line 1244, in run_command
        super().run_command(command)
      File "C:\Users\RUNNER~1\AppData\Local\Temp\pip-build-env-ajqw1i5n\overlay\site-packages\setuptools\_distutils\dist.py", line 988, in run_command
        cmd_obj.run()
      File "C:\Users\runneradmin\AppData\Local\pypa\cibuildwheel\Cache\pypy3.7-v7.3.9-win64\lib_pypy\cffi\setuptools_ext.py", line 144, in run
        base_class.run(self)
      File "C:\Users\RUNNER~1\AppData\Local\Temp\pip-build-env-ajqw1i5n\overlay\site-packages\setuptools\command\build_ext.py", line 84, in run
        _build_ext.run(self)
      File "C:\Users\RUNNER~1\AppData\Local\Temp\pip-build-env-ajqw1i5n\overlay\site-packages\setuptools\_distutils\command\build_ext.py", line 345, in run
        self.build_extensions()
      File "<string>", line 1100, in build_extensions
      File "<string>", line 1104, in build_extension
      File "C:\Users\RUNNER~1\AppData\Local\Temp\pip-build-env-ajqw1i5n\overlay\site-packages\setuptools\command\build_ext.py", line 247, in build_extension
        if ext._needs_stub:
    AttributeError: 'Extension' object has no attribute '_needs_stub'

maybe because finalize_options needs to take the results of configure into account? I don't really understand why only one case would be affected, but I think some options may need to take configure results into account for configure to properly have an effect.

Not off the top of my head. Can you share your Python, OS, and setuptools versions? Because when I try this (mac, Python 3.10.9, setuptools 67.8.0), it successfully builds with -j12 and no errors.
setuptools finalize_options modifies Extension objects, which means that all Extension objects must be defined before finalize_options is called (arguably it shouldn't do that, since it's not related to options). configure may add an Extension for the bundled pyzmq, so it needs to run before build_ext.finalize_options.
If finalize_options is idempotent, we could perhaps run dist.get_command_object("build_ext").finalize_options() . I'm not sure that's a guarantee, though.
Ideally, 'configure' would run entirely before creating the distribution so there wouldn't be any of these interactions, but it needs the distribution to run. I'm not sure if setup can be invoked twice, so that we can effectively do python setup.py configure && python setup.py build_ext in one setup.py script?

Not off the top of my head. Can you share your Python, OS, and setuptools versions? Because when I try this (mac, Python 3.10.9, setuptools 67.8.0), it successfully builds with -j12 and no errors.

Ah, I'm sorry. I have assumed this happens for everyone but apparently I was wrong.
OS: Gentoo Linux amd64
Python: 3.10.11, 3.11.3
setuptools: 67.8.0
However, from a quick experimentation it doesn't happen in a "pure" venv, so I suspect one of the installed packages is causing this. I'm going to investigate deeper.

Ideally, 'configure' would run entirely before creating the distribution so there wouldn't be any of these interactions, but it needs the distribution to run. I'm not sure if setup can be invoked twice, so that we can effectively do python setup.py configure && python setup.py build_ext in one setup.py script?

Well, this is a really hard problem. Note that per PEP517, you shouldn't be expecting any setup.py calls at all. The only reason we're calling build_ext directly is that setuptools currently doesn't support passing -j and having it passed speeds builds a lot.
Now that I have a hint where to look next, I'm going to try and see if this isn't a bug somewhere else to fix.

Well, it seems to be caused by numpy overriding the C compiler somehow:
Traceback (most recent call last):
  File "/tmp/pyzmq/setup.py", line 1367, in <module>
    setup(**setup_args)
  File "/usr/lib/python3.10/site-packages/setuptools/__init__.py", line 107, in setup
    return distutils.core.setup(**attrs)
  File "/usr/lib/python3.10/site-packages/setuptools/_distutils/core.py", line 185, in setup
    return run_commands(dist)
  File "/usr/lib/python3.10/site-packages/setuptools/_distutils/core.py", line 201, in run_commands
    dist.run_commands()
  File "/usr/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 969, in run_commands
    self.run_command(cmd)
  File "/usr/lib/python3.10/site-packages/setuptools/dist.py", line 1244, in run_command
    super().run_command(command)
  File "/usr/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 987, in run_command
    cmd_obj.ensure_finalized()
  File "/usr/lib/python3.10/site-packages/setuptools/_distutils/cmd.py", line 111, in ensure_finalized
    self.finalize_options()
  File "/tmp/pyzmq/setup.py", line 1259, in finalize_options
    self.distribution.run_command("configure")
  File "/usr/lib/python3.10/site-packages/setuptools/dist.py", line 1244, in run_command
    super().run_command(command)
  File "/usr/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
    cmd_obj.run()
  File "/tmp/pyzmq/setup.py", line 765, in run
    self.check_zmq_version()
  File "/tmp/pyzmq/setup.py", line 469, in check_zmq_version
    detected = self.test_build(zmq_prefix, self.compiler_settings)
  File "/tmp/pyzmq/setup.py", line 717, in test_build
    detected = detect_zmq(self.tempdir, compiler=self.compiler, **settings)
  File "/tmp/pyzmq/buildutils/detect.py", line 114, in detect_zmq
    if not compiler.has_function('timer_create'):
  File "/usr/lib/python3.10/site-packages/setuptools/_distutils/ccompiler.py", line 893, in has_function
    objects = self.compile([fname], include_dirs=include_dirs)
  File "/usr/lib/python3.10/site-packages/numpy/distutils/ccompiler.py", line 89, in <lambda>
    m = lambda self, *args, **kw: func(self, *args, **kw)
  File "/usr/lib/python3.10/site-packages/numpy/distutils/ccompiler.py", line 278, in CCompiler_compile
    _job_semaphore = threading.Semaphore(jobs)
  File "/usr/lib/python3.10/threading.py", line 423, in __init__
    if value < 0:
TypeError: '<' not supported between instances of 'str' and 'int'

To reproduce it, you have to:
pip install cython numpy pythran
python setup.py build_ext -j12

Weird, numpy modifies distutils just by being installed? WDYT of special-casing self.parallel as a simpler one-off fix without having to worry about the bigger, general issue of finalize_options?
FWIW, if the installer follows PEP 517 (e.g. installation with pip and without --no-build-isolation, the standard way ~every Python package is installed), this can't happen because numpy won't be in the build environment.

Weird, numpy modifies distutils just by being installed? WDYT of special-casing self.parallel as a simpler one-off fix without having to worry about the bigger, general issue of finalize_options?

Actually, it happens because Cython imports Pythran if the latter is installed, and Pythran imports numpy.distutils that causes the overrides to happen.
I'll update the PR to copy the self.parallel logic from setuptools/distutils.

FWIW, if the installer follows PEP 517 (e.g. installation with pip and without --no-build-isolation, the standard way ~every Python package is installed), this can't happen because numpy won't be in the build environment.

Yeah, I suppose isolated builds are reasonably secure against that.

I've updated the PR and hopefully added clear enough comment as why this is done.

Thanks!

Thanks a lot.
We have worked around it locally already, so there's no need for a new release because of this. We can wait for the next regular release.