Add comments to the two enumeration codes store/config/BrokerRole.java and FlushDiskType.java

``…java and store/src/main/java/org/apache/rocketmq/store/config/FlushDiskType.java two enumeration codes Supplementary notes
package org.apache.rocketmq.store.config;
/**

define BrokerRole enum class
/
public enum BrokerRole {
/*

When the slave and master messages are completed asynchronously,
there is no need to send a successful status
/
ASYNC_MASTER,
/*
When the slave and master messages are synchronized,
they will return to the status of successful sending
/
SYNC_MASTER,
/*
Indicates the slave, used to read the message
*/
SLAVE;
}
``package org.apache.rocketmq.store.config;

/**

Define the disk brush enumeration class
/
public enum FlushDiskType {
/*

Indicates synchronous brushing
/
SYNC_FLUSH,
/*
Indicates asynchronous brushing
*/
ASYNC_FLUSH
}
I will continue to submit the code comments under other packages later!

Oh, I see. Which layers of code are more complex, or indicate what I can contribute. Thank you!
发自我的iPhone
------------------ Original ------------------
From: rongtong @.>
Date: Sat,Sep 11,2021 9:11 PM
To: apache/rocketmq @.>
Cc: leikang123 @.>, Mention @.>
Subject: Re: [apache/rocketmq] Add comments to the two enumeration codes store/config/BrokerRole.java and FlushDiskType.java (#3343)
@RongtongJin commented on this pull request.
Hi,  @leikang123  Welcome to contribute code to the rocketmq community. IMO, a lot of comments are unnecessary and redundant for these three files in this pull request,  FlushDiskType and BrokeRole don't need extra attention, comments should be a concise explanation of complex code.  Hope you can submit a more meaningful pull request.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.


feat: Make current file easily noticeable

This PR contains two changes that revolve around a single purpose - to make the currently opened file easily noticeable in the quick menu.
The first one is non-breaking and it adds a highlight group (HarpoonCurrentFile, not linked by default) on the line that contains the currently opened file.
The second is somewhat breaking and moves the cursor to the line that contains the currently opened file when you open the quick menu.
If the current buffer is not Harpooned, they do nothing.
Here's a preview to help explain the features.
Peek 2022-08-23 22-40.webm
(Here, HarpoonCurrentFile is linked to Search - :highlight link HarpoonCurrentFile Search)
Rationale: In the couple of months that I've been using Harpoon, I often found myself editing the harpoon list around the currently opened file (move it to the top, or remove all other files, etc), so making it more easily noticeable feels natural.

beautiful idea.

please fix the format and i'll merge that sob

Rebased against current master and force-pushed


The entire app is borked.

Well, new exciting news.
 Tracking here

I'll try to give development logs, and code I think is the issue tomorrow. I'm super tired right now and there's zero way I'm doing any of this tonight 😅

9fbd0fa fixed this. CoreMIDI in Swift is horrible.


Upgrade pyairvisual to 3.0.1

Description:
Changelog: https://github.com/bachya/pyairvisual/releases/tag/3.0.1
Related issue (if applicable): N/A
Pull request in home-assistant.io with documentation (if applicable): N/A
Example entry for configuration.yaml (if applicable):

Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.

If the code communicates with devices, web services, or third-party tools:

[x] New dependencies have been added to the REQUIREMENTS variable (example).
[x] New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.

If the code does not interact with devices:

[ ] Tests have been added to verify that the new code works.

Ahum, https://github.com/home-assistant/home-assistant/pull/21520/files#diff-28b15059a7f6861a348c0b4ed091f78cL144

Apologies, @balloob.


"Functions hit (dynamic analysis based)" section reports incorrect numbers

Covered functions = 1 in this report https://storage.googleapis.com/oss-fuzz-introspector/jsoncpp/inspector-report/20220413/fuzz_report.html#functions_cov_hit_0 despite there being a lot more than 1 covered function

Looks to be because of this line https://github.com/ossf/fuzz-introspector/blob/f5e4d0281e52d09beda8995c8b5b7eaafd8870bb/post-processing/fuzz_data_loader.py#L279


[Super Token Listing Request]

Project infos and contact (Website, Email, Telegram and/or Twitter handle):
Metagame:
https://metagame.wtf
Link to the verified Super Token contract on a Block Explorer:
https://polygonscan.com/token/0x1bd951a9c9a5ec665abef684425f025dc8738cca
Link to a logo of the token in SVG (preferred) or PNG format:
https://static.metaswap.codefi.network/api/v1/tokenIcons/137/0xeaecc18198a475c921b24b8a6c1c1f0f5f3f7ea0.png
(Or upload the logo here)

Link to the coingecko entry of the token:
https://www.coingecko.com/en/coins/metagame
If not listed on coingecko, please provide a default token price (in USD) to be used in the Dashboard

listing done, asset PR: https://github.com/superfluid-finance/assets/pull/179


feat(headers): add AcceptLanguage header

Adds header support for Accept-Language, using a struct for the primary and
sub components of the language.
NOTE: I have been unable to get equality comparison working

What's the issue with equality? The floats?

Merge this now. I will update language-tags at a later date.

It seems there's an issue with Eq in this PR...
On Sat, Feb 14, 2015, 8:38 AM Pyfisch<EMAIL_ADDRESS>wrote:

Merge this now. I will update language-tags at a later date.
—
Reply to this email directly or view it on GitHub
https://github.com/hyperium/hyper/pull/299#issuecomment-74381810.

Thanks for contributing! Unfortunately, I'm here to tell you there were the following style issues with your Pull Request:

Commit: 97a9f5d207280c950797e1d8d92437234d1a2151

Commits must be in the following format: %{type}(%{scope}): %{description}

Commit: e62cdfd7af7c3cd47247ef69b93f6da03357c058

Commits must be in the following format: %{type}(%{scope}): %{description}

Guidelines are available at https://github.com/hyperium/hyper/blob/master/CONTRIBUTING.md

This message was auto-generated by https://gitcop.com

The equality issue is in QualityItem for quality values that can't be exactly represented by f32.
I added a bench, squashed, and rebased.


homepage fix

neat library!  I stumbled upon it (and have done my own adventures into streaming stats), but got confused when I clicked the homepage link on rubygems and wound up reading python...

I do not know why the s.homepage is not enough to set the homepage, but there is now a source code link

homepage should be enough...  the source code link is optional in case they differ


Wrong IsConstructor, IsEffectivelySameAs results for constructors in compiled code

In example below mfv is a MemberOrFunctionOrValue in a type in a compiled assembly. mfv was taken from GetAllUsesOfAllSymbolsInFile results.
if (mfv.IsConstructor) {
  var entity = mfv.EnclosingEntity;
  var hasSameMember =
    entity.MembersFunctionsAndValues.Any(m => m.IsEffectivelySameAs(mfv));
  var hasCtor =
    entity.MembersFunctionsAndValues.Any(m => m.IsConstructor);
}

Both hasSameMember and hasCtor are false while expected to be true.
I'm using FSharp.Compiler.Service 12.0.2.

@auduchinok Any chance you could send a PR adding a failing test? With the repro above we won't be certain we've solved the problem.

@dsyme Sure! I'll try to write a proper test for this case and send a PR then.
One thing that I discovered while were debugging is that this is reproduces for constructors in compiled code only while it works properly for types defined in the same project.

@auduchinok Thanks, that would be very helpful

I couldn't reproduce it in tests, but managed to fix both issues in #777.


Converting Flow model to hibernate

Converting Flow model to hibernate

Here's the style file for IDEA: https://github.com/linkedin/WhereHows/blob/master/wherehows-docs/LinkedIn Style.xml


Implement Premade products

Something's wrong with layout on the small resolutions

When dropdown is active, selected option has text cursor, which I believe tells us that we can highlight and edit the text. But we can not. Not sure if it easily fixable here.

Oh, we kinda can edit it, but on the single backspace whole string gets deleted.

I think 320px wide screen is probably the smallest we will ever encounter so below that it doesn't really matter, but until then it's probably a good idea that it wouldn't explode


RE-36 Thaw adjustments

This commit makes some minor adjustments to assist with the newton thaw
process.
Issue: RE-36

Seeing the same issue with a simple systemctl [stop|start] lxc, or rebooting the host.
The problem appears to be that conductor doesn't get started before metadata API.
http://paste.openstack.org/show/670659/
If you manually start galera, memcache, rabbit, keystone, nova_conductor first, then metadata API comes up cleanly.
http://paste.openstack.org/show/670677/

Startup order, for reference:
root@osa-aio:/var/lib/lxc# grep "lxc.start.order" */config | sort -k 3 -n
aio1_galera_container-922ff1be/config:lxc.start.order = 10
aio1_keystone_container-d879ec9b/config:lxc.start.order = 19
aio1_rabbit_mq_container-8971ece6/config:lxc.start.order = 19
aio1_rsyslog_container-28859039/config:lxc.start.order = 19
aio1_neutron_agents_container-b3cb3df6/config:lxc.start.order = 29
aio1_nova_api_metadata_container-2eba389b/config:lxc.start.order = 39
aio1_nova_api_os_compute_container-c2e5adf4/config:lxc.start.order = 39
aio1_nova_cert_container-57bf0d80/config:lxc.start.order = 39
aio1_nova_conductor_container-818581c7/config:lxc.start.order = 39
aio1_nova_console_container-607f0ccd/config:lxc.start.order = 39
aio1_nova_scheduler_container-d3b3c6ef/config:lxc.start.order = 39
aio1_swift_proxy_container-60d3ac51/config:lxc.start.order = 39
aio1_cinder_api_container-0fd9ee34/config:lxc.start.order = 100
aio1_cinder_scheduler_container-aae8da17/config:lxc.start.order = 100
aio1_glance_container-c00bda7f/config:lxc.start.order = 100
aio1_heat_apis_container-90195141/config:lxc.start.order = 100
aio1_heat_engine_container-3f9ed4da/config:lxc.start.order = 100
aio1_horizon_container-34d1dc6b/config:lxc.start.order = 100
aio1_memcached_container-715dc71b/config:lxc.start.order = 100
aio1_neutron_server_container-2c52c344/config:lxc.start.order = 100
aio1_repo_container-7c8cb43a/config:lxc.start.order = 100
aio1_utility_container-1d4ef857/config:lxc.start.order = 100

@byronmccollum I tried modifying https://github.com/rcbops/rpc-openstack/blob/newton/gating/thaw/thaw.yml to start galera/rabbit first, then nova_conductor, and then nova_api_metadata, but it didn't work.  I suspect this is because we're just using lxc-start which ignores the start delay in the config file.  Your comment here actually raises a good point in that we're completely ignoring the start order and should resort to starting with lxc-autostart (once the containers can actually be started).
I'm testing this upstream change atm:
diff --git a/playbooks/common-playbooks/nova.yml b/playbooks/common-playbooks/nova.yml
index bee2b00..91233f4 100644
--- a/playbooks/common-playbooks/nova.yml
+++ b/playbooks/common-playbooks/nova.yml
@@ -51,6 +51,16 @@
       vars:
         extra_container_config_no_restart:
           - "lxc.start.order=39"
+      when:
+        - "'nova_conductor' in group_names"
+
+    - name: Configure container
+      include: ../common-tasks/os-lxc-container-setup.yml
+      vars:
+        extra_container_config_no_restart:
+          - "lxc.start.order=49"
+      when:
+        - "'nova_conductor' not in group_names"

     - name: Configure log directories (on metal)
       include: ../common-tasks/os-log-dir-setup.yml

I'm not sure if changing the start order for most nova containers from 39 to 49 is a problem, but I'm sure @odyssey4me will know if that's going to be a problem (assuming it even works).

@mattt416 @byronmccollum Yeah, the start order for LXC needs adjusting to try and match the start order specified in https://github.com/openstack/openstack-ansible-os_nova/blob/master/defaults/main.yml#L435-L507 or something close to it. This is a really good find and something that's been a loose end in my mind for some time. I expect that the LXC start order doesn't have to be quite as detailed as some services will be more tolerant than others, but this is definitely something we should endeavour to resolve upstream.

My patch above seems to work, so I've created https://review.openstack.org/#/c/544038/ to make this change upstream.

I've removed the restart of nova-api-metadata from this patch.  There is a SHA bump in https://github.com/rcbops/rpc-openstack/pull/2854 which will pull in the container ordering fix in OSA, but I'll still need to create a separate patch to update the thaw process (for pike and newton) to start containers with lxc-autostart rather than manually with lxc-start. This PR should be fine to merge since it's a standalone fix that is specific to newton.


[BM-676] Manage the client websocket connection within activity onResume/onPause

Task

JIRA

Description

Establish connection within activity lifecycle events - onResume, onPause in order to properly handle going/returning to/from background.
Additionally changed string to match the connection status.

          3 Warnings

:warning:
app/src/main/kotlin/co/netguru/baby/monitor/client/feature/client/home/ClientHomeActivity.kt#L33 - Class ‘ClientHomeActivity’ with ‘16’ functions detected. Defined threshold inside classes is set to ‘15’

:warning:
app/src/main/kotlin/co/netguru/baby/monitor/client/feature/client/home/ClientHomeViewModel.kt#L33 - Class ‘ClientHomeViewModel’ with ‘16’ functions detected. Defined threshold inside classes is set to ‘15’

:warning:
app/src/main/kotlin/co/netguru/baby/monitor/client/feature/client/home/ClientHomeViewModel.kt#L206 - Multiple occurrences of the same string literal within a single file detected.

          1 Message

:book:
:link: BM-676

JaCoCO Code Coverage 15.47% :white_check_mark:

Class
Covered
Meta
Status

co/netguru/baby/monitor/client/feature/client/home/ClientHomeViewModel
12%
0%
:white_check_mark:

co/netguru/baby/monitor/client/feature/client/home/ClientHomeActivity
0%
0%
:white_check_mark:

co/netguru/baby/monitor/client/feature/client/home/dashboard/ClientDashboardFragment
0%
0%
:white_check_mark:

APK file size

size

30.3MB

Number of method references

Dex file
count

classes.dex
46809

  Generated by :no_entry_sign: Danger


Accept pre-tokenized references & hypothesis for METEOR calculation

I added an option to input pre-tokenized sentence(s) for METEOR calculation.
At present, references & hypothesis are always tokenized with str.split() (Lines 30-31 of meteor_score.py):
    hypothesis_list = list(enumerate(preprocess(hypothesis).split()))
    reference_list = list(enumerate(preprocess(reference).split()))

However, we have trouble calculating METEOR in a language that does not separate words with spaces (e.g., Japanese).
In this pull request, I have changed _generate_enums to accept pre-tokenized reference & hypothesis in addition to untokenized reference & hypothesis so that we can use a customized tokenizer.
Other functions have been changed accordingly.

@yutanakamura-tky Heya! We've started using https://pre-commit.com/ pretty recently. With this program, some tests are ran before it lets you commit. With our configuration, it means that some commands are ran to ensure some code quality. In particular, the black formatter. As you can see in the test output, the black formatter complained that the changes you are trying to push are not formatted according to the black formatting rules.
My recommendation is to run pre-commit install (pre-commit should have been pip install-ed already, but otherwise you can use pip install pre-commit). This will install the pre-commit hooks, causing it to run all of those hooks (e.g. formatters, verifiers, etc.) when you make another commit.  This might seem a little bit confusing, but it's more intuitive in practice. Oh, also, pre-commit only affects this repository, you don't have to worry about it affecting other projects.
Upon installing, you may run pre-commit run --all, which applies formatting and such on all files, and in particular on your changes. You may push these changes, so the Continuous Integration stops complaining.
Let me know if you have any issues.

@tomaarsen
Thank you! I have updated this pull request using pre-commit.

I would prefer to require tokenised input (a breaking change) than to have str or list(str) parameter

I believe that all the other translation scores, i.e. BLEU, CHRF, GLEU, NIST and RIBES also use pre-tokenized inputs (Correct me if I'm wrong). As a result, I'm all in favor of modifying the METEOR score so that it also takes tokenised input.

@tomaarsen
Thank you for your all review comments & updating meteor.doctest!
I have made some changes as follows:
1. Addition of Type Hints
I have added type hints to all methods in meteor_score.py.
Accordingly, I have removed type descriptions in the docstrings.
2. Minor Improvement of Local Variable Names
I have changed some local variable names to make their roles clearer.

_generate_enums()

hypothesis_list -> enum_hypothesis_list
reference_list -> enum_reference_list

exact_match()

hypothesis_list -> enum_hypothesis_list
reference_list -> enum_reference_list

_enum_stem_match()

stemmed_enum_list1 -> stemmed_enum_hypothesis_list
stemmed_enum_list2 -> stemmed_enum_reference_list

@tomaarsen
Thank you so much!
I want just one more piece of advice about variable typing.
The ongoing docstring says that meteor_score takes float for the variable beta, while it defaults to 3:
def meteor_score(
    references: Iterable[Iterable[str]],
    hypothesis: Iterable[str],
    preprocess: Callable[[str], str] = str.lower,
    stemmer: StemmerI = PorterStemmer(),
    wordnet: WordNetCorpusReader = wordnet,
    alpha: float = 0.9,
    beta: float = 3,
    gamma: float = 0.5,
)

The "3" derives from the power of penalty in the original METEOR article.
I am wondering if beta: Union[int, float]=3 is better than beta: float=3.

@yutanakamura-tky I think the best solution in that situation is simply to change beta: float = 3 into beta: float = 3.0. That way it's extra clear that this value can be/is meant to be a float. That said, users are free to use e.g. 4, because Python automatically converts ints to floats whenever requires anyways.

@tomaarsen
Thank you so much! I have also made the same change to single_meteor_score().
There are no further changes that I am planning to make at present.

Wonderful, it all looks great to me. I'll leave the PR like this for now, so perhaps another team member can have a look at it too.

nice! i love the addition of type hints anywhere in NLTK
given that this is a breaking change, should we have a changelog entry? after that, lgtm!

Thank you @yutanakamura-tky, @tomaarsen, @dannysepler.


Fix asset decimal pointer

@gregLibert chatgpt4 gave me the answer but I don't fully understand. Could you explain why we had the same pointer for decimals value before this fix?

before merging, check: we have a similar loop in the save function, maybe we need also to copy the decimal value


⚠ Bofrost.at has degraded performance

In 6c190dc, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1395 ms

Resolved: Bofrost.at performance has improved in 0ac3c43.


fix up grip service so that it can be passed to sower

Abstracts grip service envar out of code base and into helm chart. Must add
- name: GRIP_SERVICE_NAME
            valueFrom:
              configMapKeyRef:
                name: grip-values
                key: serviceName

to sower config env var section for it to work.
See updated PRS:
https://github.com/ACED-IDP/submission/pull/32
https://github.com/ACED-IDP/aced_etl_pod/pull/36

Added some comments! Also, what's the benefit of passing the grip service name through sower? Starting testing atm

So that if helm changes, the code doesn't break


Fix migrations

3 changes:

Changed ids and foreign key columns to use bigint instead of int. Rodauth (and ActiveRecord) now uses bigint columns for the ids, so using int for the foreign keys doesn't work.

Added missing index keys for some unique fields to fix ArgumentError: Unknown key: :unique. error.

ActiveRecord now uses precision 6 for datetime fields by default, so the default values must also specify that. See this.

Another one:
Trilogy::ProtocolError: 1072: Key column 'code' doesn't exist in table /app/db/migrate/20230327145623_create_rodauth_oauth.rb:101:in change'`
    create_table :oauth_pushed_requests do |t|
      t.bigint :oauth_application_id
      t.foreign_key :oauth_applications, column: :oauth_application_id
      t.string :params, null: false
      t.datetime :expires_in, null: false
      t.index %i[oauth_application_id ->>>>code<<<<-], unique: true
    end

That column doesn't exist on the table, not sure what to do about this one.

Closing because I just noticed PRs are supposed to go on GitLab.
https://gitlab.com/os85/rodauth-oauth/-/merge_requests/117


Remove nebula optional-base package

Description
Removes nebula optional-base as com.netflix.nebula:gradle-extra-configurations-plugin has removed support for optional flag starting 10.0.0.
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[x] Commits are signed per the DCO using --signoff
[ ] Commit changes are listed out in CHANGELOG.md file (See: Changelog)

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.

Closing as I'm not actively working on this.


Feature Request / Tag SVG elements with lucide-specific classes

Tagging SVG icon elements with lucide specific classes like
<svg class="lucide lucide-{icon-name}">…</svg>

would make much more easier to reference them from CSS stylesheets, in order for instance to:

factor app-wide sizing / stroke properties
tweak sizing / alignment for specific icons

P.S. Suggestion born from a real-world struggle in keeping icons aligned with button labels using fonts with an atypical baseline…

Should we apply this for every package?

Would support sensible use cases also elsewhere, imho.

The vue/nuxt package already does .lucide-icon
<svg class="lucide-icon">…</svg>

The Feature vue package does .feather.feather-{icon-name}
<svg class="feather feather-{icon-name}">…</svg>

I make good use of both of these and would love that the icon-name be included across the board.

That looks like it would work for Vue. I tried testing it locally with yarn link but I couldn't get my Vue app to compile, even on the master branch.

Thanks @venashial I'm reluctant to make a PR until I can test locally. I think I'm having the same issue as you though. I'll try a local npm link and try main. I think I don't understand monorepo well enough yet.

@venashial To make a locally dev environment working, you need to run yarn lucide-vue build(from root). It will generate the needed JavaScript files from the icons and types etc.
After that running yarn link from packages/lucide-vue should work.

Thanks @ericfennis
For a user new to yarn: following are complete instructions for testing a package from a monorepo.
WARNING: Apple silicon follow this guide first.
Outside your project
$ git clone git@github.com:lucide-icons/lucide.git
$ cd lucide
$ npm install --global yarn
$ yarn install # May fail on Apple silicon see warning above.
$ yarn lucide-vue build
$ cd packages/lucide-vue
$ yarn link

Inside your project
$ yarn link lucide-vue

Thanks for everyone's help on this. I've added a PR #395 to support Vue. It follows the format laid out by @knoan above.
I'd like to start using this in our project. I'm not clear how I can do this without publishing an npm package. The gitpkg.now.sh solution doesn't seem to work for us. I've seen other solutions with post-install hooks. Is that the way to do it?

Hey @ericfennis that PR only resolves this ticket for lucide-vue. None of the other packages (including vue-next). So maybe it should stay open?

@queenvictoria I added it today for the other packages as well.

Oh sweet!


Not able to view JMeter report

I am just trying to publish JMeter HTML report that I generate using pipeline.
JMeter command is:
call jmeter -J csvfile="$(System.DefaultWorkingDirectory)/_CCM.API.Test.Files/Test_Data_SQL_Queries/$(Feature).csv" -J users=$(Users) -J lifeT=$(LifeSpan) -n -t
call jmeter -g "%rp%\results.csv" -o "%rp%\REPORT"
Report generates okay, I didn't see any errors while using extension either in logs but no report is seen anywhere. Where am I supposed to see this?

You are supposed to use the task of the extension and provide the root folder of report as Jmeter path. Please go through the documentation


CI for Node

✕ Initializes with two players (4 ms)
✓ Initializes with an empty board
✕ Starts the game with a random player (1 ms)
turn
✓ Inserts an 'X' into the top center
✓ Inserts an 'X' into the top left (1 ms)
nextPlayer
✕ Sets the current player to be whoever it is not
hasWinner
✓ Wins if any row is filled
✓ Wins if any column is filled (1 ms)
✓ Wins if down-left diagonal is filled
✓ Wins if up-right diagonal is filled (1 ms)

✕ Initializes with two players (4 ms)
✓ Initializes with an empty board
✕ Starts the game with a random player (1 ms)
turn
✓ Inserts an 'X' into the top center
✓ Inserts an 'X' into the top left (1 ms)
nextPlayer
✕ Sets the current player to be whoever it is not
hasWinner
✓ Wins if any row is filled
✓ Wins if any column is filled (1 ms)
✓ Wins if down-left diagonal is filled
✓ Wins if up-right diagonal is filled (1 ms)


How to train?

How should the provided code be applied to your own dataset for training and prediction?

Hi @wtt6668888, here are a couple of notebooks that may be of use to you. Your dataset will need to be parseable into a pandas dataframe with a time column and a target column for prediction. Please let me know if this helps answer your question.
Energy Demand Forecasting - Basic Inference
Preprocessing and Performance Evaluation

@wtt6668888 For pretraining a new model from scratch you can take a look at the workflow here: https://github.com/ibm-granite/granite-tsfm/blob/main/notebooks/hfdemo/tinytimemixer/ttm_pretrain_sample.py
If you wish to fine-tune the pretrained model, you can take a look at the following notebook: https://github.com/ibm-granite/granite-tsfm/blob/main/notebooks/tutorial/ttm_with_exog_tutorial.ipynb
This notebook fine-tunes the model so that additional exogenous features can be included.


IG dm issues

its very slow and image messages are not delivering

its very slow

Hello, could you elaborate some more on this? What parts do you experience slow speed?

while switching the text boxes and its loading slow ,image mesages could not be sent could you  please
fix this


Update taxonomy term markup for Neue 6.0.

Changes

Updates markup on taxonomy term page for Neue 6.0.

For review: @DoSomething/front-end

Couple questions which don't need answers now, but looks good overall :+1:


External variables

Coverage increased (+0.2%) to 44.541% when pulling 344c4160e2c623a397dffd0759b9125b423a1246 on zenika-dev-javi into 43801a6fa2c916674ef0f0c3ee9a14d9f4c5a1bd on zenika-dev.

Coverage increased (+0.2%) to 44.541% when pulling 344c4160e2c623a397dffd0759b9125b423a1246 on zenika-dev-javi into 43801a6fa2c916674ef0f0c3ee9a14d9f4c5a1bd on zenika-dev.


Update using_helm.md

In docs/using_helm.md, it says on line 214 that you can pass in a YAML formatted file, but the example commands following that sentence create JSON code but names the file with a .yml extension. For clarity, I propose saying that it will accept JSON or YAML but clarify in the code that for the example we're making a JSON file.

@pmcanseco Thanks for the contribution. On Helm we use a DCO. Could you please provide signoff on your commit. Directions are on the checks tab of the PR.

@pmcanseco Thanks for the contribution. On Helm we use a DCO. Could you please provide signoff on your commit. Directions are on the checks tab of the PR.

done!

-f only accepts YAML as input so the docs are wrong in this case. Can we instead make the output of the echo properly-formed YAML? https://github.com/helm/helm/blob/1801fa0074a0207f4d5724667858b53d52c486f8/cmd/helm/install.go#L197

ping


Object destructuring spacing

var { x} = ...
var {x} = ...
var {x } = ...

These cases probably shouldn't be allowed.

In any case, consistency, thoughts?

Yeah, I'm in favor of this if there's some way to get this rule just for object destructuring, i.e. not for object literals too:
var x = { a: 1, b: 2 }

I would like to enforce this spacing for object literals too, but at this point it's a huge breaking change and lots of people are doing:
var x = {a: 1}

I think eslint might have only one rule for both of these, but I can't remember. Want to look into it?

@feross are we able to use warnings as syntax deprecation messages?

I suppose we could, but that's a departure from what we currently do.

In an event where the above change would be introduced,  I think the warning might be the best way to get an immediate, non-breaking discussion around its usage,  if that is desired.

What about just treating:
var { x} = ...
var { x} = ...

as errors.
var { x } = ...
var {x} = ...

would be allowed.
Same for arrays. If I got var arr = [1, 2, 3] or var arr = [ 1, 2, 3 ] in a PR, I'd have no complaints. It's just var arr = [1, 2, 3 ] or var arr [ 1, 2, 3] that is gross.
Thoughts?

100% agree, that is a great start and enforces some form of sane consistency.

Yep, I like this too :+1:

Does someone want to make an eslint issue for this? I don't think this is a rule option they currently support.

@feross https://github.com/eslint/eslint/issues/2955

@feross the feedback is that we should just use http://eslint.org/docs/rules/object-curly-spacing.
That might cause issues though as you said.

@feross looks like it isn't going to change upstream,  do we want to enforce a particular style then?
There is quite a few breaking changes lately, might be worth while.

There is quite a few breaking changes lately (not necessarily our fault either)

This should happen a lot less going forward. I locked the eslint version so it's exact now. So if even a patch version of eslint starts causing new tests to fail, we can decide if we want to bump the major version of standard.

looks like it isn't going to change upstream, do we want to enforce a particular style then?

For any breaking style changes, even in a major, I want to make sure that standard-format is bumped in parallel, so users can use standard -F to ease the transition.
Before we do that though, @xjamundx offered to write an eslint plugin that enforces the "either" rule we wanted from eslint.

I can help you build this. It will take like 15 minutes. Does standard already have its own custom rules or a eslint-plugin-standard plugin we could add this to?

We don't have any custom rules right now. Can you put custom rules into a lib/ folder in this repo?

Yes that's an option, but I'd recommend at the very least you created a dedicated rules directory. To use custom rules with eslint you either need to specify the rulesdir option (which is deprecated, but going to stick around for a while) or reference plugins (which are separate NPM modules and can have multiple rules).

Also you only care about destructuring spacing or all of the existing things found in object-curly-spacing?

Okay, how about we start with a rules directory and then we can pull it out into a module eventually.
We care about "even spacing" for everything in the object-curly-spacing and array-bracket-spacing rules. If it's not too hard, could you do array-bracket-spacing too?

Sure. I can do both. Give me a day or so!

@xjamundx You're awesome!

so funny to me:
~/dev/standard (custom-rules) $ npm test

><EMAIL_ADDRESS>test /Users/jamuferguson/dev/standard
> node ./bin/cmd.js && tape test/*.js

standard: Use JavaScript Standard Style (https://github.com/feross/standard)
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:9:0: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:9:13: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:11:0: Expected space or tab after // in comment.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:13:0: Expected space or tab after // in comment.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:15:25: Missing space before function parentheses.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:16:2: Expected indentation of 2 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:16:40: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:16:49: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:25:2: Expected indentation of 2 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:25:24: Missing space before function parentheses.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:26:4: Expected indentation of 4 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:26:91: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:27:2: Expected indentation of 2 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:29:2: Expected indentation of 2 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:31:44: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:32:46: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:33:45: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:34:6: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:36:4: Expected space or tab after // in comment.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:38:4: Expected space or tab after // in comment.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:46:2: Expected indentation of 2 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:46:21: Missing space before function parentheses.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:47:4: Expected indentation of 4 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:47:46: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:48:2: Expected indentation of 2 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:56:2: Expected indentation of 2 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:56:23: Missing space before function parentheses.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:57:4: Expected indentation of 4 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:57:60: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:58:2: Expected indentation of 2 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:66:2: Expected indentation of 2 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:66:35: Missing space before function parentheses.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:67:4: Expected indentation of 4 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:68:68: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:69:2: Expected indentation of 2 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:77:2: Expected indentation of 2 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:77:32: Missing space before function parentheses.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:78:4: Expected indentation of 4 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:79:69: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:80:2: Expected indentation of 2 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:88:2: Expected indentation of 2 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:88:41: Missing space before function parentheses.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:89:4: Expected indentation of 4 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:90:63: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:91:2: Expected indentation of 2 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:99:2: Expected indentation of 2 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:99:38: Missing space before function parentheses.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:100:4: Expected indentation of 4 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:101:72: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:102:2: Expected indentation of 2 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:109:2: Expected indentation of 2 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:109:33: Missing space before function parentheses.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:110:4: Expected indentation of 4 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:111:6: Expected indentation of 6 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:111:19: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:112:4: Expected indentation of 4 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:114:4: Expected indentation of 4 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:114:8: Split initialized 'var' declarations into multiple statements.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:117:46: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:119:4: Expected indentation of 4 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:120:65: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:121:64: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:123:51: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:125:4: Expected indentation of 4 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:126:70: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:127:69: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:129:51: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:131:4: Expected indentation of 4 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:132:6: Expected indentation of 6 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:133:8: Expected indentation of 8 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:133:58: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:134:6: Expected indentation of 6 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:135:6: Expected indentation of 6 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:136:8: Expected indentation of 8 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:136:52: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:137:6: Expected indentation of 6 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:138:4: Expected indentation of 4 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:140:4: Expected indentation of 4 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:141:6: Expected indentation of 6 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:142:8: Expected indentation of 8 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:142:54: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:143:6: Expected indentation of 6 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:144:6: Expected indentation of 6 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:145:8: Expected indentation of 8 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:145:48: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:146:6: Expected indentation of 6 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:147:4: Expected indentation of 4 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:148:2: Expected indentation of 2 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:150:4: Expected space or tab after // in comment.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:152:4: Expected space or tab after // in comment.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:154:2: Expected indentation of 2 characters.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:157:6: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:159:2: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:163:8: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:163:17: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:163:27: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:166:8: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:166:16: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:167:8: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:168:12: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:169:16: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:169:24: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:171:12: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:172:16: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:172:24: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:174:12: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:175:16: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:175:24: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:178:8: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/array-bracket-spacing.js:180:2: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:9:0: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:9:13: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:11:0: Expected space or tab after // in comment.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:13:0: Expected space or tab after // in comment.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:15:25: Missing space before function parentheses.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:16:2: Expected indentation of 2 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:16:40: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:16:49: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:25:2: Expected indentation of 2 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:25:24: Missing space before function parentheses.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:26:4: Expected indentation of 4 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:26:91: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:27:2: Expected indentation of 2 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:29:2: Expected indentation of 2 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:31:46: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:32:47: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:33:6: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:35:4: Expected space or tab after // in comment.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:37:4: Expected space or tab after // in comment.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:45:2: Expected indentation of 2 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:45:21: Missing space before function parentheses.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:46:4: Expected indentation of 4 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:46:46: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:47:2: Expected indentation of 2 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:55:2: Expected indentation of 2 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:55:23: Missing space before function parentheses.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:56:4: Expected indentation of 4 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:56:60: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:57:2: Expected indentation of 2 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:65:2: Expected indentation of 2 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:65:35: Missing space before function parentheses.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:66:4: Expected indentation of 4 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:67:68: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:68:2: Expected indentation of 2 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:76:2: Expected indentation of 2 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:76:32: Missing space before function parentheses.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:77:4: Expected indentation of 4 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:78:69: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:79:2: Expected indentation of 2 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:87:2: Expected indentation of 2 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:87:41: Missing space before function parentheses.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:88:4: Expected indentation of 4 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:89:63: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:90:2: Expected indentation of 2 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:98:2: Expected indentation of 2 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:98:38: Missing space before function parentheses.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:99:4: Expected indentation of 4 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:100:72: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:101:2: Expected indentation of 2 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:112:2: Expected indentation of 2 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:112:33: Missing space before function parentheses.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:113:4: Expected indentation of 4 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:114:70: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:115:71: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:116:51: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:118:4: Expected indentation of 4 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:119:6: Expected indentation of 6 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:120:8: Expected indentation of 8 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:120:58: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:121:6: Expected indentation of 6 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:122:6: Expected indentation of 6 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:123:8: Expected indentation of 8 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:123:52: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:124:6: Expected indentation of 6 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:125:4: Expected indentation of 4 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:127:4: Expected indentation of 4 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:128:6: Expected indentation of 6 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:129:8: Expected indentation of 8 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:129:54: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:130:6: Expected indentation of 6 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:131:6: Expected indentation of 6 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:132:8: Expected indentation of 8 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:132:48: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:133:6: Expected indentation of 6 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:134:4: Expected indentation of 4 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:135:2: Expected indentation of 2 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:137:4: Expected space or tab after // in comment.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:139:4: Expected space or tab after // in comment.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:141:2: Expected indentation of 2 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:144:31: Missing space before function parentheses.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:145:10: Expected indentation of 10 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:145:12: Split initialized 'var' declarations into multiple statements.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:146:76: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:148:10: Expected indentation of 10 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:148:12: Split initialized 'var' declarations into multiple statements.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:151:60: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:154:10: Expected indentation of 10 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:154:31: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:155:12: Expected indentation of 12 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:155:35: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:156:12: Expected indentation of 12 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:156:51: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:157:10: Expected indentation of 10 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:159:10: Expected indentation of 10 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:159:73: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:163:35: Missing space before function parentheses.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:165:10: Expected indentation of 10 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:165:12: Split initialized 'var' declarations into multiple statements.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:166:76: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:169:10: Expected indentation of 10 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:169:75: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:169:119: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:170:12: Expected indentation of 12 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:170:16: Split initialized 'var' declarations into multiple statements.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:173:64: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:175:12: Expected indentation of 12 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:175:77: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:176:10: Expected indentation of 10 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:181:40: Missing space before function parentheses.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:182:10: Expected indentation of 10 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:183:12: Expected indentation of 12 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:183:23: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:184:10: Expected indentation of 10 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:186:10: Expected indentation of 10 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:186:12: Split initialized 'var' declarations into multiple statements.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:191:60: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:193:10: Expected indentation of 10 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:193:73: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:198:34: Missing space before function parentheses.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:199:10: Expected indentation of 10 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:200:12: Expected indentation of 12 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:200:23: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:201:10: Expected indentation of 10 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:203:10: Expected indentation of 10 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:203:12: Split initialized 'var' declarations into multiple statements.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:206:50: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:208:10: Expected indentation of 10 characters.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:208:73: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:211:6: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:213:2: Extra semicolon.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:217:8: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:217:17: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:217:27: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:220:8: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:220:16: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:221:8: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:222:12: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:223:16: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:223:24: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:225:12: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:226:16: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:226:24: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:229:8: Strings must use singlequote.
  /Users/jamuferguson/dev/standard/rules/object-curly-spacing.js:231:2: Extra semicolon.
npm ERR! Test failed.  See above for more details.

Working on this. 15 minutes was a bit of an understatement, but I'm on an :airplane: with great wifi and i'm hoping to have it done before we land :)

Gist of the rule is right here:
    function isEvenlySpaced(node, start, end) {
        var expectedSpace = start[0].range[1] - start[1].range[0];
        var endSpace = end[0].range[1] - end[1].range[0];
        return endSpace === expectedSpace;
    }

When that fails it will say something like "Expected consistent spacing".
I need to add more edge cases, but it's coming along!

Any thoughts on handling this:
var x = {
	a: 'b'
}

Technically speaking it's uneven, but I could just ignore anything not on the same line?

Excellent!
Your idea to special case the newline condition is the right idea. But of course, even without that, the rule would be better that what we have now :+1:

You can try standard -F rules/object-curly-spacing.js to fix most of the style errors :)

nice! manually fixed them :-p

I'll have a PR soon with the object one.

you're the :bomb: !

following test cases are all working as expected
    { code: 'var { x } = y', ecmaFeatures: { destructuring: true } },
    { code: 'var {x} = y', ecmaFeatures: { destructuring: true } },
    { code: "import {	x	} from 'y'",  ecmaFeatures: { modules: true } },
    { code: "import {x} from 'y'",  ecmaFeatures: { modules: true } },
    { code: "var x = { a: 'b' }" },
    { code: "var x = {\na: 'b'\n}" },
    { code: "var x = {\n\ta: 'b'\n}" },
    { code: "var x = {\n a: 'b' \n}" },
    { code: 'var foo = {};' },
```js

And the invalid examples:

```js
      { code: 'var {x } = y'}
      { code: 'var {  x } = y'}
      { code: 'var {\n  x } = y'}
      { code: 'var x = {x: "a", b: ''" }
      { code: 'import {x, y } from "thing"' }

I'm going to see if I can integrate this one rule into the standard package first then work on the array rule later

Okay, so eslint-tester uses mocha and you folks use tape, so we can't add standard eslint style rule tests, which is bit crazy, but with the latest update the PR now enables the curly space rule and supports custom rules in the rules/ folder. Take a look at that. Play with it. If it seems liek a good approach I'll get going on the array rule.

@xjamundx awesome work!

    { code: "import {   x   } from 'y'",  ecmaFeatures: { modules: true } },

Should that be acceptable?  Can we enforce 0 | 1 spaces?

@dcousens the way that this rule is setup you're only enforcing consistent spacing for a given objectexpression or objectpattern, not consistent spacing for all objects everywhere.

@xjamundx OK, and its not easy to change that consistency to 0 | 1 spaces?

@dcousens. We certainly could do that if it's desired.

@xjamundx would that interfere with multiline?
AFAIK,  we want to support these cases:
var { x } = ...
var {x} = ...
var {
  x,
  y
} = ...

I see your point. It's up to 1 space.

Yeah that's easy.
By the way I'm messing around with this idea:
https://github.com/xjamundx/eslint-plugin-standard
It's much easier to write out the test cases when they're in a plugin like this:
https://github.com/xjamundx/eslint-plugin-standard/blob/master/tests/object-curly-even-spacing.js#L27

Would love warnings when there is inconsistency, e.g.
var test = {hello: 'blah'}
var test2 = { hello: 'blah' }
console.log(test, test2)

In the same project/file.

file-level consistency is doable, but not currently supported.

@xjamundx I'm merging your work on eslint-plugin-standard right now. Wouldn't @knownasilya's example be caught?

The inconsistency is per instance not per file.

@xjamundx Ah.

Okay, @xjamundx's changes are released as standard 5.0.0-7 and we depend on eslint-plugin-standard now! Thanks for the great work!

awesome!

Continue conversation @ Object curlies: File/project–wide or standard?


docs: add zoom to 2d spectrum

closes : https://github.com/zakodium/react-plot/issues/315

Let's ask @stropitek since he created the issue

No it's fine don't create the tracking. We will think about whether it makes sense to have a zoom when there is a shift in pixel. Because the zoom behavior here is really not intuitive.


TSServer exited. Code: null

Type: Bug
The typescript server exits with code "null" which has ultimately broken the intellisense or code completion for javscript and node js.

If it does, please try collecting the TS Server log from the crashed instance:

Set "typescript.tsserver.log": "verbose"

Restart VS Code and reproduce the problem

Open the TypeScript section of the output panel

At the very top, find the first line that prints to path to the semantic error log file. It should look something like:
[Info  - 19:54:59.247] <semantic> Log file: /Users/matb/Library/Application Support/Code - Insiders/logs/20200213T104930/exthost55/vscode.typescript-language-features/tsserver-log-ZT2zau/tsserver.log

That file contains the typescript logs.

Look through that log file for the first error or stack trace you see. If you can share the log, I can also take a look to see if anything stands out

⚠Warning: The TypeScript log may include information from your workspace, including file paths and source code. If you have any concerns about posting this publicly on Github, just let me know and we can arrange something else. On our side, we only use these logs to investigate issues like this

I’m not sure how the intellisense, TS Server works on all the platform. Seems it uses the types on OSX from the path ~/Library/Caches/typescript/ folder. This folder was missing, I am not sure if vscode downloads these global types if it’s missing. I fixed this by reinstalling vscode and node js. This has resolved my issue.


chore: add dependabot config

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Add dependabot config

What is the current behavior? (You can also link to an open issue here)

What is the new behavior (if this is a feature change)?

Other information:

Codecov Report
Base: 97.89% // Head: 97.89% // No change to project coverage :thumbsup:

Coverage data is based on head (015e166) compared to base (0f963ed).
Patch has no changes to coverable lines.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff           @@
##           master      #23   +/-   ##
=======================================
  Coverage   97.89%   97.89%
=======================================
  Files          18       18
  Lines         475      475
  Branches       97       97
=======================================
  Hits          465      465
  Misses         10       10

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Mozilla Firefox API support link 503

The link for Mozilla Firefox API support (http://arewewebextensionsyet.com/) is currently broken.  I don't know of a suitable replacement site.

You’re right, site was decommissioned. https://github.com/andymckay/arewewebextensionsyet.com
I think the other compatibility tables already on the list are good replacements. PR welcome to remove it

incoming PR

Thanks! Appreciated


[3pt] Add source code to models_catalog.csv

Add a new column to the models_catalog.csv when it is created for "source_code". The only value we have at this point is "ble".

Added in the recent iterations, we now track the following:
> OWP_models <- data.table::fread(".../OWP_ras_models_catalog.csv")
> unique(OWP_models$source_code)
[1] "rfc" "ble" "ifc"


Updated README.md

I added my name under N alphabet so its in correct order, then what is the issue ??

I added my name under N alphabet so its in correct order, then what is the issue ??

Your name must come before Nishant in alphabetical order . Thanks for your valuable contribution 😊. Don't forget to ✨ our Repository.


Block wildcard access of bus names in well-known namespace

Alternative to https://github.com/flathub-infra/flatpak-builder-lint/pull/114, closes https://github.com/flathub-infra/flatpak-builder-lint/pull/114, blocks in both own-name and talk-name.
List based on ones that are most likely to find their way in manifests and can potentially give widespread access. If there are more, please comment below.
This can be reused to block the pattern in https://github.com/flathub-infra/flatpak-builder-lint/issues/178 too
I don't see a generic method to block * because a bunch of legitimate ones can end in * The third component or ones after that are reserved for applications, e.g. org.gnome.evolution.*
Closes https://github.com/flathub-infra/flatpak-builder-lint/issues/178

I'll import an exception list (mainly for org.kde.*) if this is fine.

Yeah, go ahead

I thought about it again a bit and having separate errors would be better because having a combined exception allows an app to have all 3 bus access when it say needs only "org.kde.*" for legacy purposes.
I'll raise a separate error for each.

Just for more fine-grained exception system...

maybe we should start by submitting PR....

I'll open some issues later.

Opening of issues is done, I count 31 cross-links in https://github.com/flathub-infra/flatpak-builder-lint/issues/178

org.kde.*:
Rest have issues open and are cross-linked to https://github.com/flathub-infra/flatpak-builder-lint/pull/114.
All except Quaternion and Chiaki are unmaintained/had little to no activity. The maintainer of Chiaki is not sure why the permission is in the manifest but did not want to remove the permission. So that one is unsolvable from my side.
org.freedesktop.portal.*:
Waiting for a bit so that more apps can respond to the issues I opened.


fix(ai): caching use deep copy for request table

Summary
This is a backport of #13566 so that it lands in 3.8 CE
Checklist

[ ] The Pull Request has tests
[ ] A changelog file has been created under changelog/unreleased/kong or skip-changelog label added on PR if changelog is unnecessary. README.md
[ ] There is a user-facing docs PR against https://github.com/Kong/docs.konghq.com - PUT DOCS PR HERE

Issue reference

Fix konghq.atlassian.net/browse/AG-111

There's no need to cherrypick this into EE since it is already included in  a different pr

FYI I updated the commit type from feat -> fix at squash+merge time to match the PR description


Community/dev branch

I assume that right now the developers are laser-focused on pooling, unfortunately the chia-docker repo has plenty useful PRs ready to be approved, that are several days old. It will be nice to have a community/dev branch (and relative docker tag deployed) in which PR are merged after 2 or 3 community approvals.
2-3 seems a fair number but could be more.

I will consider this suggestion. Not a bad idea. let me think it over for a bit.


Flush() should also clear reference count

A quick fix to correct the logic that Flush() should also clear reference count.
Update error message to help debug non zero reference case.
Update testcase to cover the changes.

Closing this as obsolete after #221.


logging: read log level from kernel cli and add an api

see #182

Codecov Report

Merging #187 into 1.1.0-alpha will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           1.1.0-alpha     #187   +/-   ##
============================================
  Coverage        16.81%   16.81%
============================================
  Files               15       15
  Lines             1029     1029
============================================
  Hits               173      173
  Misses             845      845
  Partials            11       11

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 bdd3fc2...50b5491. Read the comment docs.


Fix the Rolebinding update logic

RoleBindings can't have their Roles changed after they're created. If an RB was quickly delete and re-created in an ancestor namespace - fast enough that by the time that HNC notices, the new RB exists - HNC could see it as an update (not a delete + create) and attempt to update the RBs in all descendant namespaces, and this will fail. In order to handle this case, we try to delete and re-create the rolebinding instead.
Tested: make test-e2e
Fix #798

/assign @adrianludwin
/assign @yiqigao217

lgtm after the comments are updated.

BTW I have a question: the delete->create logic here is basically to "update" RBs in the descendants, right?
Yes


Template for 404 was not found

Could you provide more details?

I was install api-gen with composer

Could you run fresh installation, should be fixed now.


scoping of labels looks more like a breaking change rather than a bugfix

The 2nd Bug Fix reported in the Changelog for v0.10.0 (Fixed label scoping so that labels in expressions like (a:"a") or (a:"a" b:"b" c:"c") aren’t visible from the outside.) looks more like a breaking (major) change rather than a bug, at least from a user's perspective whose grammar(s) (with some extra parentheses for clearer separation of blocks) worked just fine with v0.9.x but are broken with v0.10.0 because some variables aren't bound. Do you think it' worth changing this entry's section to major changes, or at least marking it as a potentially breaking change as well as a bugfix?

I always assumed that the labels were scoped to the sequence they are written in, so never even considered accessing sub-labels, but when @dmajda released 0.10 back in 2016 I was surprised that it could be done before.
I'm sure this is a breaking change if people were using this feature, but I think this is definitely a bugfix, especially if it was a feature that wasn't intended to work that way.

@akatov Closing as I don't view this as an issue, but if you disagree, please state so and I'll re-open the issue.


README.md refers to libra

Not a big issue as it's being redirected, but I guess replacing:

git clone https://github.com/libra/my-first-client.git

with
git clone https://github.com/diem/my-first-client.git
Can avoid confusion

@sabau Thank you for bringing this to our attention!


Question: Proper way to handle lists in adaptiview

I want to build a form with a list of a given property and therefore I'm experimenting with adaptiview and lists.
Based on the sample counter, I managed to come up with the following:
let app =
    adaptiview () {
        let! li, setLi = cval<string list>([]).WithSetter()
        let listView = li |> List.map (fun l -> div { l })

        div {
            div {
                yield! listView
            }

            button {
                onclick (fun _ -> transact(fun _ ->  setLi(li @ [ "New row" ])))
                "Append"
            }
        }
    }

The snippet above works. The UI refreshes as expected 🙌 .
But also, there's a type clist which seems more convenient for this but then a let! values = clist(["initial"]) can't be bound using let!.
What I imagined I would be able to do here is something like:
let app =
    adaptiview () {
        let! li = clist([])
        let listView = li |> List.map (fun l -> div { l })

        div {
            div {
                yield! listView
            }

            button {
                onclick (fun _ -> transact(fun _ ->  li.Append([ "New row" ])))
                "Append"
            }
        }
    }

Is this something that just isn't supported at the moment? Or am I doing something off? 😅
Thanks for the support!

Hi @mathantunes , adaptiview is only support binding cval and aval. You can just convert clist to cval right?

Or just write something like below. Blazor's diff is good enough, we do not need to use clist to introduce more complexisty. adaptiview is just to create a area to narrow down the dynamic area, so blazor can calculate less when doing diff.
let app =
    adaptiview () {
        let! items, setItems = cval<string list>([]).WithSetter()

        let listView =
            items
            |> List.map (fun item -> div {
                key item // use blazor diff for better performance instead of clist
                item
            })

        div {
            div {
                yield! listView
            }
            button {
                onclick (fun _ ->
                    [ "New row" + Random.Shared.Next().ToString() ]
                    |> List.append items
                    |> setItems
                )
                "Append"
            }
        }
    }

The cval approach looks good to me.
Thank you for the support, @albertwoo.


removing statefulset specific code, reworking code for cnpg

More code deletion in this PR

Remove StatefulSet specific code.  We will no longer reconcile or "know" about the StatefulSet that is created.  Effectively we will just start ignoring it.
Remove the old coredb Service that was associated with connecting to the old CoreDB instance.
Change default image logic a bit.  We will now take the default image set in cdb.spec.image or if that is empty we will look for a stack and set it correctly or use the default image.
Fix tests

Before merging this, we will need to do a few other things.

Update the image to use the new CNPG specific defaults in the cp-webserver

Some notes to follow for after this PR is merged
To upgrade coredb-operator we will need to manually adjust the following.
1: All manifests will need to be updated to use the correct cnpg image. (tembo-pg-cnpg or ml-cnpg) only.
* There could be errors when reconciling the image back to the coredb-pg-slim image.

2: Manually delete the CronJobs in each namespace.  The CJ backups are no longer needed
3: Manually remove the Service in each namespace.  It will be the only one without a suffix.
4: Manually remove the StatefulSet in each namespace
5: Manually remove the PVC's in each namespace that were associated with each StatefulSet.  There should be 3 in each namespace.

Conductor tests will most likely fail until we can get this PR merged.  This is due to the fact that Conductor tests are ran from main code base of the operator and not this PR's code base.


different control sizes when compiled with native aot

Describe the bug
some controls shows a bit differently in terms of sizes with native aot enabled.
To Reproduce
Steps to reproduce the behavior:

run the repro and observe the controls look.
publish as native aot with dotnet publish -r win-x64 -c Release
run the exe inside publish folder and observe the differences

Expected behavior
the controls looks exactly the same
Desktop (please complete the following information):

OS: Windows
Version 10

Additional context
avalonfont.zip

I reckon we need a side by side screenshot showing the differences, if possible.

normal:

aot:

For reference https://github.com/AvaloniaUI/Avalonia/pull/9443


Issue using with tf.keras

Hello,
I am trying to adapt this layer for tf.keras. I made few changes, but got stuck on one. Can you please help. Thanks in advance.
Here is stacktrace:
Traceback (most recent call last):
  File "aacn_b0_tf.py", line 926, in <module>
    train_images_dir, test_images_dir, batch_size, lr, labels)
  File "aacn_b0_tf.py", line 830, in run
    model = get_model(img_size, n_channels, n_classes, dropout_rate, leak)
  File "aacn_b0_tf.py", line 801, in get_model
    x = bottleneck_block(x, 112, 192, 5, 2, 'block6_0', use_aacn=True)
  File "aacn_b0_tf.py", line 750, in bottleneck_block
    i, int(input_filters * expand_ratio), depth_k=24, depth_v=24)
  File "/home/ashwanipandey/kaggle/aptos19-blindness-detection/attn_aug_conv.py", line 306, in augmented_conv2d
    attn_out = _conv_layer(depth_v, kernel_size=(1, 1))(attn_out)
  File "/home/ashwanipandey/kaggle/venv/lib/python3.6/site-packages/tensorflow/python/keras/engine/base_layer.py", line 591, in __call__
    self._maybe_build(inputs)
  File "/home/ashwanipandey/kaggle/venv/lib/python3.6/site-packages/tensorflow/python/keras/engine/base_layer.py", line 1881, in _maybe_build
    self.build(input_shapes)
  File "/home/ashwanipandey/kaggle/venv/lib/python3.6/site-packages/tensorflow/python/keras/layers/convolutional.py", line 153, in build
    raise ValueError('The channel dimension of the inputs '
ValueError: The channel dimension of the inputs should be defined. Found `None`.

It seems like self.depth_v is becoming None somewhere, but I cannot figure out where and why.

Thanks, I'll try doing that and will update.

Please open a PR. Keras proper is on maintainance mode and we will prioritize tf.keras.

Opened PR https://github.com/titu1994/keras-attention-augmented-convs/pull/7!

PR #7 merged.


Webhook pull_request synchronize action field is synchronized, but github is synchronize

Description
gitea:

github: https://docs.github.com/en/webhooks/webhook-events-and-payloads?actionType=synchronize#pull_request
I use @octokit/webhooks. It works by listening on pull_request.synchronized, but  it reports:
"pull_request.synchronized" is not a known webhook name (https://developer.github.com/v3/activity/events/types/)

So is it possible to keep these events compatible with github?
Gitea Version
47b878858ada27fc4c74eeadcc1e467d2da90e04
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
build on 47b878858ada27fc4c74eeadcc1e467d2da90e04
Database
None

By the way, after a reviewer requests change, the reviewer is not removed from requested_reviewers in webhook payload.
But github docs says:

Once a requested reviewer submits a review, they are no longer considered a requested reviewer.

Other issue:

Review state in webhook payload. Github is CHANGES_REQUESTED, but gitea is REQUEST_CHANGES.
Review state in webhook payload.  After dismiss a review, state should be DISMISSED, but gitea does not change this field.


Fixed block_info with axes.

Closes https://github.com/dask/dask/issues/4298

I think this should be good to go.

Merging this and #4308 in a couple hours if there are no objections.

LGTM, merging.


Windows 11 support suggestions

Hi,
I appreciate your efforts in putting this repo together. I tried to run the webdriverio example on Windows 11 and could not get it running out of the box, but I think I got close to getting something working.

I had to create an "icons/icon.ico" file
I had to supply "--native-driver", "msedgedriver.exe" as arguments to tauri-driver.
When that tauri-driver runs, it defaults to port 4445 (so I had to update the port in the wdio config to that)
After finally building the tauri app successfully, the webdriver launches a blank Microsoft Edge window, and while the window says "Microsoft Edge is being controlled by automation software" it never seems to load the actual Tauri app.

What might I be missing?
Here's my updated config:
exports.config = {
  port: 4444, <-- needed
  specs: ["./test/specs/**/*.js"],
  maxInstances: 1,
  capabilities: [
    {
      maxInstances: 1,
      "tauri:options": {
        application: "../../target/release/hello_tauri.exe", <-- the ".exe" needed for windows
      },
    },
  ],
  reporters: ["spec"],
  framework: "mocha",
  mochaOpts: {
    ui: "bdd",
    timeout: 60000,
  },

  // ensure the rust project is built since we expect this binary to exist for the webdriver sessions
  onPrepare: () => spawnSync("cargo", ["build", "--release"]),

  // ensure we are running `tauri-driver` before the session starts so that we can proxy the webdriver requests
  beforeSession: () =>
    (tauriDriver = spawn(
      path.resolve(os.homedir(), ".cargo", "bin", "tauri-driver"),
      // ['--native-driver', './msedgedriver.exe'], // <-- Key issue: would start just a blank MSedge window, not the app. Tauri driver was only respecting the PATH env var, not the CLI option.
      { stdio: [null, process.stdout, process.stderr] }
    )),

  // clean up the `tauri-driver` process we spawned at the start of the session
  afterSession: () => tauriDriver.kill(),
};

I know it sounds trivial, but the CLI help says I can use the "--native-driver" param but only the ENV var was working completely.

Had similar issues, finally got it working on Windows 11 via the Selenium approach.

Make sure to add .exe to all executable paths
Download and install msedgedriver and provide the full path to it

I also converted my setup to TypeScript. For Reference:
test/test.ts
import os from "os";
import path from "path";
import { expect } from "chai";
import { spawn, spawnSync } from "child_process";
import { Builder, By, Capabilities } from "selenium-webdriver";

import type { WebDriver } from "selenium-webdriver";
import type { ChildProcessByStdio } from "child_process";

let port = 4454;
let nativePort = port + 1;
const isRelease = false;

// create the path to the expected application binary
const application = path.resolve(
  __dirname,
  "..",
  "..",
  "..",
  "target",
  isRelease ? "release" : "debug",
  "hello_tauri.exe"
);

console.log(application);

// keep track of the webdriver instance we create
let driver: WebDriver;

// keep track of the tauri-driver process we start
let tauriDriver: ChildProcessByStdio<any, null, null>;

before(async function () {
  // set timeout to 2 minutes to allow the program to build if it needs to
  this.timeout(120000);

  // ensure the program has been built
  spawnSync("cargo", ["build", isRelease ? "--release" : "--debug"]);

  // start tauri-driver
  tauriDriver = spawn(
    path.resolve(os.homedir(), ".cargo", "bin", "tauri-driver"),
    [
      "--port",
      port.toString(),
      "--native-driver",
      "C:/path/to/msedgedriver.exe",
      "--native-port",
      nativePort.toString(),
    ],
    { stdio: [null, process.stdout, process.stderr] }
  );

  const capabilities = new Capabilities();
  capabilities.set("tauri:options", { application });
  capabilities.setBrowserName("wry");

  // start the webdriver client
  driver = await new Builder()
    .withCapabilities(capabilities)
    .usingServer(`http://localhost:${port.toString()}/`)
    .build();
});

after(async function () {
  // stop the webdriver session
  await driver!.quit();

  // kill the tauri-driver process
  tauriDriver!.kill();
});

describe("Hello Tauri", () => {
  it("should be cordial", async () => {
    const text = await driver!.findElement(By.css("body > h1")).getText();
    expect(text).to.match(/^[hH]ello/);
  });

  it("should be excited", async () => {
    const text = await driver!.findElement(By.css("body > h1")).getText();
    expect(text).to.match(/!$/);
  });
});

And ran with ts-mocha
ts-mocha -p ./tsconfig.json test/*.ts
package.json
{
  "name": "selenium",
  "version": "1.0.0",
  "license": "Apache-2.0",
  "private": true,
  "scripts": {
    "test": "mocha",
    "test-ts": "ts-mocha -p ./tsconfig.json test/*.ts",
    "format": "prettier --write \"./**/*.js\""
  },
  "dependencies": {
    "@types/chai": "^4.3.5",
    "@types/selenium-webdriver": "^4.1.15",
    "chai": "^4.3.7",
    "mocha": "^10.2.0",
    "selenium-webdriver": "^4.9.2",
    "ts-mocha": "^10.0.0",
    "ts-node": "^10.9.1",
    "typescript": "^5.1.3"
  }
}

cannot parse capability: ms:edgeOptions
Thanks for the port, now seems like this is also required: webviewOptions because of cannot parse capability: ms:edgeOptions.
capabilities.set('tauri:options', {
    application: application,
    webviewOptions: {},
})


Removed the dependency on the OpenSSL

This PR is an attempt to make the amethyst cli more accessible by removing the dependency on openssl, so that the users would not have to spend time finding and installing necessary dependencies.
This is done by enabling the rust-tls feature of the reqwest crate.
Since the crate is currently used only once, perhaps the switch between the openssl and rust-tls is not that significant.

Codecov Report

Merging #89 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #89   +/-   ##
=======================================
  Coverage   97.05%   97.05%
=======================================
  Files           3        3
  Lines          34       34
=======================================
  Hits           33       33
  Misses          1        1

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 942ca02...4f3d71d. Read the comment docs.


openebs provisioner - support for adding block volumes

FEATURE REQUEST
Kubernetes 1.9 now supports attaching block devices to pods. This is issue is raised to support adding OpenEBS PVs as block devices to pods.
Refer:
https://kubernetes.io/docs/concepts/storage/persistent-volumes/#raw-block-volume-support
Notes:
This may be tied into required block mode support for iscsi pv.

The support for this will depend on https://github.com/kubernetes/kubernetes/pull/54752

The change will be required in the provisioner code when creating the PV object at https://github.com/openebs/external-storage/blob/release/openebs/pkg/provisioner/cas_provision.go#L139

Tested

Fixed in 0.7.1 via https://github.com/openebs/external-storage/pull/78


Adds option to customize antd variables

This PR allows antd users to provide a file to override whichever antd variable they want.  I added instructions to use it to the README file.
Inspired by another plugin, next-plugin-antd-less

Hi @lgenzelis, thanks for contributing!
My intention was to keep this plugin as "dumb" as possible. I'm currently not using additionalData at all, but also haven't worked too much with Less.
So a couple of questions -

How common is it to add overrides with additionalData? Are there any other ways to do that?
Would it be ok to just add lessLoaderOptions and spread it in the options, so users can add stuff in next.config.js? I'm asking this because users may want to do additional things in additionalData and I wouldn't want to limit that to only overrides file load.

You're welcome @elado ! ^^ I don't know how common is it to add overrides to additionalData, but I do know it is extremely common to override some of antd variables. It's the official way to do customize it.
Adding something like lessLoaderOptions would be ok, I guess. Less code here in the plugin, but more code for the users. It's your call :) We can still add an example of how we'd use lessLoaderOptions to customize antd in the README, since many users are probably going to want to do that.

We could name that option additionalData or lessLoaderAdditionalData (I think lessLoaderOptions would be confusing, it's more similar to lessOptions than to additionalData).
Then, user usage for this case would be something like:
module.exports = withLess({
  future: {
    webpack5: true,
  },
  //....
  lessLoaderAdditionalData: content =>`${content}\n\n@import '${pathToLessFileWithVariables}';`,
}

Doesn't seem so terrible :)

I was wondering whether I could inject antd styles without using _app.js page.

You're welcome @elado ! ^^ I don't know how common is it to add overrides to additionalData, but I do know it is extremely common to override some of antd variables. It's the official way to do customize it.

I just wanted to also chime in that I am also looking for a way to override some of the variables (in order to change color). Thank you all for working on this!

I closed this PR and created a new one, #4, since we ended up going in a different direction that I originally described. You're absolutely right @elado , this is a better approach, it adds almost no complexity to the plugin, while still allowing users to customize as needed.
BTW, the reason why I prefer overriding the variables using additionalData instead of just modifyVars, is that with the latter you have to stop the server and do npm run dev again each time you modify a variable. Using additionalData to inject the variables file, hot reload works as usual. It makes tweaking the variables much easier :)

I was wondering whether I could inject antd styles without using _app.js page. The example in this package relies merely on additional customization to NextJs's default _app.js.

@dryleaf I don't think that's possible. You need to import the styles somewhere, and _app is the place for that (since these are global styles).

@lgenzelis I created an issue#3, please have a look.


Fix connected_component_bfs #634

This fixes issue #634 , just had to switch from neighbors to all_neighbors
I added tests aswell

This is great, thanks!


Heatmaps Do Not Work With Leaflet 1.0.0 RC 3

I was just wondering if there are any plans to upgrade this plugin to work with Leaflet 1.0.0?
Getting this error, it works with 0.7.7 as expected.

...able()},whenReady:function(t,e){return this._loaded?t.call(e||this,{target:this}...```

Yeah, I can definitely take a look at that shortly.  Thanks for the heads up!

That would be orsome :)

+1

Done.


docs: Remove reference to the node.js issue in v1.7.x

Signed-off-by: nannanli<EMAIL_ADDRESS>Node 8.16.2 is available which fixes the 8.16.1 issue so update the docs to remove the ref to need 8.16.0

Is there a related issue for this PR?
Issue number: #890
Developer's Certificate of Origin (DCO)

Signed-off-by: nannanli<EMAIL_ADDRESS>Node 8.16.2 is available which fixes the 8.16.1 issue so update the docs to remove the ref to need 8.16.0

@nannanli - should this also go into docs-staging ?

@Joe-Winchester Yes, another PR makes the changes to docs-staging. See #895 . There are different PRs that removes the reference in different versions.

#896 v1.7.x
#897 v1.6.x
#895 v1.8.0 (docs-staging)

8.16.1 is still not supported however, so that could cause a problem for us if we don't state that.
8.16.2 works great though.

@1000TurquoisePogs With that stated, shall we update the workaround description to guide users to use v8.16.2 or later? Such as:
Workaround: Use node v8.16.2 or later which is available at https://www.ibm.com/ca-en/marketplace/sdk-nodejs-compiler-zos. Download the ibm-trial-node-v8.16.2-os390-s390x.pax.Z file.

@nannanli - yes I like your para to let users know to use 8.16.2 or later.   Thank you

Just need to state that we don't support v12 yet either (soon!)

@Joe-Winchester @1000TurquoisePogs The node.js support descriptions have been updated.

Added back the known issue with node v8.16.1 for 8.16.1 is still not supported.
Updated the workaround to guide users to use and download v8.16.2.
State that v12 is not supported yet. We'll need to revisit this statement when v12 is supported.


Fixed Footer

The plugin should keep tables with footers and give the option to also fix the footer at the bottom of the table.

I am probably not going to write this code. Pull requests are welcome


RS Connector requiring a valid aws identity to connect to Redshift, when that shouldn't be required

Driver version
2.0.0
Redshift version
PostgreSQL 8.0.2 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.4.2 20041017 (Red Hat 3.4.2-6.fc3), Redshift 1.0.76832
Client Operating System
macos ventura 13.6 (22G120)
Python version
Python 3.12.4
Table schema
n/a
Problem description
redshift_connector is trying to grab a valid aws identity when just doing a simple connect to Redshift. This is causing issues for us as we have users that do not have a valid aws identity, that need to connect to Redshift. Importantly, they are able to connect to Redshift using various SQL clients, the same behavior should be expected with Redshift connector.
Python Driver trace logs
would prefer to not post this
Reproduction code
def get_redshift_connection_robotic():
try:
conn = redshift_connector.connect(
iam=True,
ssl=True,
host='',
port=5439,
database='',
cluster_identifier='',
region='us-east-1',
partner_sp_id='',
idp_host='',
credentials_provider='PingCredentialsProvider',
user='',
password=''
)
conn.autocommit = True
cursor = conn.cursor()
cursor.execute('SELECT 1;')
print(cursor.fetchall())
except Exception as error:
logging.error("Error connecting to Redshift:", exc_info=True)
if name == "main":
get_redshift_connection_robotic()

Hey @bpatchin1 , Thanks for reaching out. Can you expand on what is meant by a "simple connect to Redshift" and "valid aws identity"? In the associated code snippit I see IAM authentication is enabled and use of the Ping Credentials Provider.
 If so, please check our "Basic Example" in the README.
If you do want to use Ping Credentials Provider and IAM authentication, please share the stack trace you are seeing upon attempting connection to assist my investigation.

Hi @Brooke-white , sure! What I am trying to do is to connect to Redshift using iam and ping, but it looks like Redshift connector is trying to establish an aws session, which shouldn't be required to just connect to Redshift. For example, I can connect to Redshift using ping and IAM using a SQL client, where, to my knowledge, no AWS session is actually set up.
I am guessing why redshift connector is needing an aws session is becausing connector is running a getclustercredentials in the background, but this should be able to be avoided I would hope.
For the stack trace, see attached:
stack_trace.txt


stty: stdin isn't a terminal (JRuby)

Could we please silence the warnings on JRuby?
See more at https://github.com/guard/guard/issues/226#issuecomment-3519470

Could we please silence the warnings on JRuby?

Could you please submit a pull request with the changes? Is not clear for me from the link you provided that this is a rb-readline issue. As clearly stated by others commenting there rb-readline gem shouldn't be used.
So wonder why rb-readline gem is been used/required and by whom which is causing this.
Me fixing this might only be hiding the real issue here: someone is requiring rb-readline on JRuby, which clearly has a fully working readline implementation and doesn't need it.

Ok. You're right, maybe it really shouldn't.
My thought was that I'll use rb-readline, I would get better support for readme.
And since I could install it on JRuby I assumed the platform is supported. Perhaps the gemspec could specify MRI Ruby to avoid the issue between monitor an the seat...

@dnagir the reason rb-readline exists is to provide an alternative to GNU readline for Ruby (also known as MRI).
It was conceived for that purpose at the beginning but also used for other environments like OSX were readline is missing (and instead there is crippled libedit and editline)
Anyhow, I heard that JRuby-readline is way better than what rb-readline could offer, which as you can see from the code do not work properly as JRuby was not considered one platform for rb-readline be supported.
Perhaps it could clearly be stated in the readme or perhaps better, fail when attempt to be require'd.
There is no way the gem can be limited to MRI, as JRuby is supposed to be compatible and there is no way the gem specification provide a negative platform compatibility.
Will leave this open until I can think of a non-contrived solution for this issue.
Thank you.

Thanks a lot.
But I guess if I'm the only one who has/had this issue, then why bother. Otherwise, maybe it's worth doing.
Cheers.