Missing kafka module on fresh pip install frontera

My working versions:
(test-frontera)[cortex][integrate-frontera] ⚡ λ python --version                                                                                [node-5.5.0][ruby-2.2.1]
Python 2.7.6
(test-frontera)[cortex][integrate-frontera] ⚡ λ pip --version                                                                                [node-5.5.0][ruby-2.2.1]
pip 7.1.2 from /home/lwm/.virtualenvs/test-frontera/local/lib/python2.7/site-packages (python 2.7)

Install frontera in a fresh 2.7.6 virtualenv:
(test-frontera)[cortex][integrate-frontera] ⚡ λ pip install frontera                                                                                [node-5.5.0][ruby-2.2.1]
Collecting frontera
/home/lwm/.virtualenvs/test-frontera/local/lib/python2.7/site-packages/pip/_vendor/requests/packages/urllib3/util/ssl_.py:90: InsecurePlatformWarning: A true SSLContext object is not availabl
e. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. For more information, see https://urllib3.readthedocs.org/en/latest/security.html#in
secureplatformwarning.
  InsecurePlatformWarning
  Downloading frontera-<IP_ADDRESS>-py2-none-any.whl (91kB)
    100% |████████████████████████████████| 94kB 3.5MB/s
Collecting six>=1.8.0 (from frontera)
  Using cached six-1.10.0-py2.py3-none-any.whl
Collecting w3lib>=1.10.0 (from frontera)
  Using cached w3lib-1.14.3-py2.py3-none-any.whl
Installing collected packages: six, w3lib, frontera
Successfully installed frontera-<IP_ADDRESS> six-1.10.0 w3lib-1.14.3
/home/lwm/.virtualenvs/test-frontera/local/lib/python2.7/site-packages/pip/_vendor/requests/packages/urllib3/util/ssl_.py:90: InsecurePlatformWarning: A true SSLContext object is not availabl
e. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. For more information, see https://urllib3.readthedocs.org/en/latest/security.html#in
secureplatformwarning.
  InsecurePlatformWarning
You are using pip version 7.1.2, however version 8.1.2 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.

Import fails due to missing kafka module:
(test-frontera)[cortex][integrate-frontera] ⚡ λ python                                                                                [node-5.5.0][ruby-2.2.1]
Python 2.7.6 (default, Jun 22 2015, 17:58:13)
[GCC 4.8.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import frontera
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/lwm/.virtualenvs/test-frontera/local/lib/python2.7/site-packages/frontera/__init__.py", line 1, in <module>
    from core.manager import FrontierManager
  File "/home/lwm/.virtualenvs/test-frontera/local/lib/python2.7/site-packages/frontera/core/manager.py", line 5, in <module>
    from frontera.settings import Settings, BaseSettings
  File "/home/lwm/.virtualenvs/test-frontera/local/lib/python2.7/site-packages/frontera/settings/__init__.py", line 4, in <module>
    import default_settings
  File "/home/lwm/.virtualenvs/test-frontera/local/lib/python2.7/site-packages/frontera/settings/default_settings.py", line 2, in <module>
    from kafka.protocol import CODEC_NONE
ImportError: No module named kafka.protocol

Passing the [kafka] option, things work:
(test-frontera)[cortex][integrate-frontera] ⚡ λ pip install frontera[kafka]                                                                                [node-5.5.0][ruby-2.2.1]
Requirement already satisfied (use --upgrade to upgrade): frontera[kafka] in /home/lwm/.virtualenvs/test-frontera/lib/python2.7/site-packages
Requirement already satisfied (use --upgrade to upgrade): six>=1.8.0 in /home/lwm/.virtualenvs/test-frontera/lib/python2.7/site-packages (from frontera[kafka])
Requirement already satisfied (use --upgrade to upgrade): w3lib>=1.10.0 in /home/lwm/.virtualenvs/test-frontera/lib/python2.7/site-packages (from frontera[kafka])
Collecting kafka-python<=0.9.5 (from frontera[kafka])
/home/lwm/.virtualenvs/test-frontera/local/lib/python2.7/site-packages/pip/_vendor/requests/packages/urllib3/util/ssl_.py:90: InsecurePlatformWarning: A true SSLContext object is not availabl
e. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. For more information, see https://urllib3.readthedocs.org/en/latest/security.html#in
secureplatformwarning.
  InsecurePlatformWarning
  Downloading kafka-python-0.9.5.tar.gz (73kB)
    100% |████████████████████████████████| 77kB 6.8MB/s
Building wheels for collected packages: kafka-python
  Running setup.py bdist_wheel for kafka-python
  Stored in directory: /home/lwm/.cache/pip/wheels/b2/e9/31/8184d8862de3ef9d23539652ba83c3ab124e86a69957c9f601
Successfully built kafka-python
Installing collected packages: kafka-python
Successfully installed kafka-python-0.9.5
You are using pip version 7.1.2, however version 8.1.2 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
(test-frontera)[cortex][integrate-frontera] ⚡ λ python                                                                                [node-5.5.0][ruby-2.2.1]
Python 2.7.6 (default, Jun 22 2015, 17:58:13)
[GCC 4.8.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import frontera
>>>

If I run pip install frontera, I shouldn't get the kafka error, given that these 'options' are optional? If not, the documentation should be updated:

http://frontera.readthedocs.io/en/latest/topics/installation.html#options

Thanks @lwm, this will be fixed soon!

Fixed with latest release.

Confirmed!
(test-frontera)[test-frontera] λ pip --version                                                                                [node-5.5.0][ruby-2.2.1]
pip 7.1.2 from /home/lwm/.virtualenvs/test-frontera/local/lib/python2.7/site-packages (python 2.7)
(test-frontera)[test-frontera] λ python --version                                                                                [node-5.5.0][ruby-2.2.1]
Python 2.7.6
(test-frontera)[test-frontera] λ pip install frontera                                                                                [node-5.5.0][ruby-2.2.1]
Collecting frontera
/home/lwm/.virtualenvs/test-frontera/local/lib/python2.7/site-packages/pip/_vendor/requests/packages/urllib3/util/ssl_.py:90: InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. For more information, see https://urllib3.readthedocs.org/en/latest/security.html#insecureplatformwarning.
  InsecurePlatformWarning
  Downloading frontera-<IP_ADDRESS>-py2-none-any.whl (91kB)
    100% |████████████████████████████████| 94kB 4.6MB/s
Collecting six>=1.8.0 (from frontera)
  Using cached six-1.10.0-py2.py3-none-any.whl
Collecting w3lib>=1.10.0 (from frontera)
  Using cached w3lib-1.14.3-py2.py3-none-any.whl
Installing collected packages: six, w3lib, frontera
Successfully installed frontera-<IP_ADDRESS> six-1.10.0 w3lib-1.14.3
/home/lwm/.virtualenvs/test-frontera/local/lib/python2.7/site-packages/pip/_vendor/requests/packages/urllib3/util/ssl_.py:90: InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. For more information, see https://urllib3.readthedocs.org/en/latest/security.html#insecureplatformwarning.
  InsecurePlatformWarning
You are using pip version 7.1.2, however version 8.1.2 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
(test-frontera)[test-frontera] λ python                                                                                [node-5.5.0][ruby-2.2.1]
Python 2.7.6 (default, Jun 22 2015, 17:58:13)
[GCC 4.8.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import frontera
>>> # win!
...
>>>


Refactor addrankings

RankingModels need new setup functions. This will reduce the runtime of addrankings from O(n^2) to O(n).

Completed.


How to detect changes in ngx-monaco-diff-editor

Since there is no ngModel and (ngModelChange) doesn't work, how can I call a function when the value of the modified editor changes?

I had the same problem.
You can get the changes like the following.
In your template bind the onInit event.
  <ngx-monaco-diff-editor
    [options]="options"
    [originalModel]="originalModel"
    [modifiedModel]="modifiedModel"
    (onInit)="onInitDiffEditor($event)"
  ></ngx-monaco-diff-editor>

and in your component add the onInit function like this to get notified about every change.
onInitDiffEditor(diffEditor: monaco.editor.IStandaloneDiffEditor) {
  if (!diffEditor) {
    return;
  }

  diffEditor.getModifiedEditor().onDidChangeModelContent(() => {
    const content = diffEditor.getModel().modified.getValue();
    console.log(content);
  });
}

Thnx @hendrikbursian. It seems that onInit is changed into init

I was able to detect changes by doing something like this.
<ngx-monaco-diff-editor
	ngDefaultControl
	[(ngModel)]="compareModel"
	(ngModelChange)="do what you want here"
	[ngModelOptions]="{standalone: true}"
	[originalModel]="{code: compareModel, language: 'plain/html'}"
	[modifiedModel]="{code: originalModel', language: 'plain/html'}">
</ngx-monaco-diff-editor>

Unfortunately this works only when you enter new characters, but not when you delete characters.
I also abserved the same behaviour with the (input) event.
I tested the solution posted by @hendrikbursian and it works fine.


Objective_C Universal Framework

Hey guys, I have been trying to adapt the latest version to my Xcode project that is based on objective c.
When I build the framework The library only compiles for "iosdevice" or for "iossimulator" and I can't make seem to make a framework that work on both (iOS and Simulator) ..
Can anyone please advise.

You can use this workaround to solve this issue.


19.1.5: IPsec includes are missing

Describe the bug
With https://github.com/opnsense/core/pull/3311 the include functionality of StrongSwan was activated.
It seems that the directories are created with the upgrade, but the include statements are missing from the files (ipsec.conf, ipsec.secrets and strongswan.conf ...).
To Reproduce
Upgrade to 19.1.5 and check if the generated files contain an include statement at the bottom.
Expected behavior
Improve on cherry picking ;-)
Environment
Software version used and hardware type if relevant.
OPNsense 19.1.5 (amd64, OpenSSL).

It was left out intentionally. As you can see from #3311 we had not negotiated an ETA.

So you create the directories on the OS but did not add the code for creating the includes?
Where do you negotiate the corresponding ETA? Since the PR is merged and closed...

@stumbaumr "we had not negotiated an ETA",  please stop wasting people's time like this. You can easily track what is either in a release by its tag or in a release when checking its branch (stable/19.1 in this case).

It’s all in the dev version shipped alongside 19.1.5. I don’t think it’s necessary to criticise our release engineering for stable versions which has little to do with your request here.
Most changes go through development version to next major release (19.7). Backports are made consciously based on positive impact. The change at hand is not a necessity for 19.1 by any means.
I’m happy to explain and backport, but only when requests are made in a civil manner and unclear procedures are not automatically labelled as fundamentally broken.

Sorry if I stepped on your toes. Did not mean any offense.
The release procedure was indeed unclear to me. I had the impression that merged ment it would be included in the next release.


Add sample_sheet handling functionality to core

Want to handle sample_sheets (flat dataframes) in a uniform way. What I want is ideally in the config theres a small block with
sample_sheet:
  path: path/to/sample_sheet.csv
  delimiter: ',' # Optional
  header: 0 # Optional
  index_col: 0 # Optional, will assume no index if not provided
  columns: ['column1', 'column2', 'column3'] # Optional, if not provided all columns will be used

The function then attempts to get the sample sheet and raises an error if the assumptions here do not hold. The function then returns a pandas dataframe for people to work with.

Should mention that block would be found below input sections


Requests from referer are blocked

I'm trying to run this project in localhost and I encountered this error while running it.
It says:
{error: {code: 403, message: "Requests from referer http://localhost/www/index.html are blocked.",…}}
Anyone can help?

You need to set your Google Cloud API key.

Hi, I already setup mine but the problem still insist. I already turned on Google Cloud Vision and Google Translator API.

@smshahiran Check you Google Cloud API key restriction.


OverflowError: value too large to convert to int32_t 加载数据报错

Reminder

[X] I have read the README and searched the existing issues.

Reproduction
Traceback (most recent call last):
File "/home/as/as_workspace/xxxx/project/LLaMA-Efficient-Tuning/src/train_bash.py", line 14, in
main()
File "/home/as/as_workspace/njjj/project/LLaMA-Efficient-Tuning/src/train_bash.py", line 5, in main
run_exp()
File "/home/as/as_workspace/njjj/project/LLaMA-Efficient-Tuning/src/llmtuner/tuner/tune.py", line 31, in run_exp
run_sft(model_args, data_args, training_args, finetuning_args, generating_args, callbacks)
File "/home/as/as_workspace/njjj/project/LLaMA-Efficient-Tuning/src/llmtuner/tuner/sft/workflow.py", line 29, in run_sft
dataset = preprocess_dataset(dataset, tokenizer, data_args, training_args, stage="sft")
File "/home/as/as_workspace/njjj/project/LLaMA-Efficient-Tuning/src/llmtuner/dsets/preprocess.py", line 22, in preprocess_dataset
column_names = list(next(iter(dataset)).keys())
File "/home/as/.conda/envs/llama_etuning/lib/python3.10/site-packages/datasets/iterable_dataset.py", line 1379, in iter
for key, example in ex_iterable:
File "/home/as/.conda/envs/llama_etuning/lib/python3.10/site-packages/datasets/iterable_dataset.py", line 678, in iter
yield from self._iter()
File "/home/as/.conda/envs/llama_etuning/lib/python3.10/site-packages/datasets/iterable_dataset.py", line 740, in _iter
for key, example in iterator:
File "/home/as/.conda/envs/llama_etuning/lib/python3.10/site-packages/datasets/iterable_dataset.py", line 678, in iter
yield from self._iter()
File "/home/as/.conda/envs/llama_etuning/lib/python3.10/site-packages/datasets/iterable_dataset.py", line 740, in _iter
for key, example in iterator:
File "/home/as/.conda/envs/llama_etuning/lib/python3.10/site-packages/datasets/iterable_dataset.py", line 678, in iter
yield from self._iter()
File "/home/as/.conda/envs/llama_etuning/lib/python3.10/site-packages/datasets/iterable_dataset.py", line 740, in _iter
for key, example in iterator:
File "/home/as/.conda/envs/llama_etuning/lib/python3.10/site-packages/datasets/iterable_dataset.py", line 281, in iter
for key, pa_table in self.generate_tables_fn(**self.kwargs):
File "/home/as/.conda/envs/llama_etuning/lib/python3.10/site-packages/datasets/packaged_modules/json/json.py", line 122, in _generate_tables
io.BytesIO(batch), read_options=paj.ReadOptions(block_size=block_size)
File "pyarrow/_json.pyx", line 52, in pyarrow._json.ReadOptions.init
File "pyarrow/_json.pyx", line 77, in pyarrow._json.ReadOptions.block_size.set
OverflowError: value too large to convert to int32_t
Expected behavior
5Gjson训练集，不报错
System Info
No response
Others
No response

把 json 改成 jsonl 读取。

解决了吗？想知道怎么解决的

把 json 改成 jsonl 读取。

是需要修改src/llamafactory/data/loader.py中的读取方式还是讲文件格式修改为jsonl就可以啊？谢谢

修改文件格式

训练集的格式不需要把所有数据存到一个list里面，每个dict单独存一行就可以读取了


Include content length header in responses

According to the XMLRPC spec, responses should include a content length header.

Duplicates #132


JSON:API compliant query parameters

This changeset implements the following syntactic changes:

Change page to page[number]
Change limit to page[size]
Change sortBy to sort
Change current syntax (field:ASC/DESC) to a comma separated ordered list of the sort fields with minus as desc operator (field1,-field2)
Change filter.field to filter[field]
Change search to @search[query]
Change searchBy to @search[fields]
Allow @search as a shorthand for @search[query] (without the possibility to then specify fields)

The changeset tries to converge as soon as possible, so even though the syntax changed, none of these changes alters the produced PaginateQuery, or any code outside decorator.ts

It also refactored the parsing logic and the decorator tests.
The parsers in many places allowed for an array notation (probably used as select[0]=field1&select[1]=field2), but this was undocumented and we now switch to strictly comma separated values.
I also allow for null to propagate, mostly because I am not sure what type of values NestJS can pass us here, everything else passes in one way or another through the String constructor. I will use a fuzzing tool later to see what kind of values make it through, and will adjust the code accordingly (it's hopefully going to be just strings, arrays, object literals and undefined).

@vsamofal I found that splitting this into 4 different PR's would contain too much duplicated code :)

Converting to draft because I think I broke multi-filters (I wasn't aware of this spec and it was untested.

Good stuff 🎉
Should meta data be adjusted as well?
{
  "meta": {
    "itemsPerPage": 5,
    "totalItems": 12,
    "currentPage": 2,
    "totalPages": 3,
    "sortBy": [["color", "DESC"]],
    "search": "i",
    "filter": {
      "age": "$gte:3"
    }
  }
}

to something like:
{
  "meta": {
    "page": {
      "number": 2,
      "offset": 5
    },
    "totalItems": 12,
    "totalPages": 3,
    "sort": ["-color"],
    "@search": "i",
    "filter": {
      "age": "$gte:3"
    }
  }
}

maybe totalItems and totalPages are also part of the page object?
@search maybe with query and field keys, where field returns the config defined fields even if undefined in url query ? 🤔

I'm semi-sceptical about leaking all the available column names in meta.search.fields ... Perhaps it's sufficient to repeat only the given and valid fields like we do for filters, and we expose the complete list only in the Swagger? I don't think any good faith actor would rely on querying an API without fields to retrieve the valid set of search fields like that.

we also need to update docs and swagger now

The parsers in many places allowed for an array notation (probably used as select[0]=field1&select[1]=field2), but this was undocumented and we now switch to strictly comma separated values.

I this this should be considered  breaking change... otherwise just keep the possibility to use both ways

@FrancYescO certainly correct: we are planning to introduce the switch to JSON:API as a new breaking change and major version.

@FrancYescO certainly correct: we are planning to introduce the switch to JSON:API as a new breaking change and major version.

Sure, my suggestion was to keep the breaking changes as little as possible (= if we can keep both ways let's try to do in this way)

Sorry, this PR was stale and after rebasing on the latest master the diff was garbled. When I tried to update ppetzold/json-api to the latest master I accidentally updated it to Helveg/json-api instead, and merged this.


Parser Generator

We should decide on the parser generator we're going to use in the rewrite. We could always use ANTLR or even GoldParser.

I have not used any of them. One thing that would be great is if one of these would include both a parser generator and a tree generator, like flex & yacc (combined) for C.

I'm not aware of anything like flex & yacc for C#, but I like Antlr has something like a tree generator.

After some looking, I've found a library called Sprache that we could potentially use.

Looks like a good lightweight package that we could use to create a proof of concept. If it would be successful, we could always switch the parsing mechanism, since it does not affect the language semantics.

That sounds good.


CSUB-463: Load testing for npos

Description of proposed changes
Still trying out things

Practical tips for PR review & merge:

[ ] All GitHub Actions report PASS
[ ] Newly added code/functions have unit tests

[ ] Coverage tools report all newly added lines as covered
[ ] The positive scenario is exercised
[ ] Negative scenarios are exercised, e.g. assert on all possible errors
[ ] Assert on events triggered if applicable
[ ] Assert on changes made to storage if applicable

[ ] Modified behavior/functions - try to make sure above test items are covered
[ ] Integration tests are added if applicable/needed

Codecov Report

Merging #1206 (3035258) into dev (8085dd6) will increase coverage by 4.11%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##              dev    #1206      +/-   ##
==========================================
+ Coverage   69.50%   73.62%   +4.11%
==========================================
  Files         100       75      -25
  Lines       11877    11112     -765
  Branches       89        0      -89
==========================================
- Hits         8255     8181      -74
+ Misses       3622     2931     -691

see 25 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

The failure in https://github.com/gluwa/creditcoin/actions/runs/5820688763/job/15781582765?pr=1206 is caused by an intentional change. The change applies only to fast-runtime and isn't related to production so the failure can be ignored.


Rule request: don't use the in operator on nodes

Continuing conversation from here https://github.com/typescript-eslint/typescript-eslint/pull/5610#discussion_r1014918727: We (typescript-eslint) generally try not to use string in checking pattern on AST nodes, as it's a little imprecise. We normally check for specific types.
- if ('async' in node && node.async) {
+ if (isFunctionLike(node) && node.async) {

How about making this an ESLint rule?
cc @eliasm307 since we were chatting 🙂

@JoshuaKGoldberg cool! So from the title mentioning "nodes" specifically, can I confirm if this rule is meant to be specific to the typescript-eslint/eslint code bases?
Could have a general "no-in" or something which triggers on all usages of "in"? But it could be a bit heavy handed so it would need some options to configure when it should trigger?

Oh sorry yes, to be clear: I do mean specific to typescript-eslint/eslint code bases, and specifically on instances of ESTree.Node or TSESTree.Node. Banning the in operator altogether is too heavyhanded, yeah.

Ah ok, in that case it sounds technically interesting. Assuming it's a rule with auto fixing, it might be challenging sometimes to be able to determine what predicates an "in" usage on a node should be replaced with e.g. Doing "body" in node where node is a generic node could be a number of things that can't be expressed with one predicate, as far as I know.
Not sure what you had in mind, but I've done a quick search across the monorepo and there are about 71 matches for ' in  which isn't too much. So imo I don't know if its worth implementing the auto fixing. I think just a rule that triggers when "in" is used on a Node would be sufficient, then its up to the dev to choose what predicates to replace it with, and this also prevents future "in" usages.
I can't commit to making a PR for this but I'm interested to see what kind of solution someone comes up with.

I agree that it's safer and clearer to check the node type instead of whether the node has a particular property. And it sounds like the in operator is the primary avenue of abuse for this in TypeScript ESLint rules.
Possible rule names that come to mind:

no-property-in-node
no-node-has-property

I don't think an autofixer would be practical for this, and I also don't think it would be necessary anyway.

Side note: I was considering whether we could make this applicable to JavaScript ESLint rules too, but so far, it doesn't seem like it would add much value. Here's my reasoning:
We could also make this semi-applicable to JavaScript ESLint rules by checking for the following examples, with cruder static analysis to ensure that node is from a visitor function parameter since we wouldn't have the variable type information available:

node.hasOwnProperty('foo')
Object.prototype.hasOwnProperty.call(node, 'foo')

However, this might not be very useful since in JavaScript, people typically just use node.foo to check if a node has a property, and we obviously can't disallow that since we don't know if they're checking whether the node has the property or just whether the property is truthy.

@bmish I started working on this, but: this would be the first rule in the plugin that depends on types. I just want to confirm the strategy first. Proposal:

Add @typescript-eslint/utils as an explicit dependency
Create a new plugin analogous to recommended that also includes type-checked rules: maybe, recommended-type-checked to match typescript-eslint?

Does that sound reasonable?

@bmish I started working on this, but: this would be the first rule in the plugin that depends on types. Which means we'd have to settle on a strategy for introducing that concept I think. Proposal:

Add @typescript-eslint/utils as an explicit dependency
Create a new plugin analogous to recommended that also includes type-checked rules: maybe, recommended-type-checked to match typescript-eslint?

The tricky thing here is that we now have two places where "type checking" is cared about:

Whether a rule's functionality is acting on type-checked rules (e.g. this rule only being meant for rules that act with type info)
Whether a rule's implementation uses type information (parserServices.getTypeAtLocation(...))

My hunch is that it's ok to intentionally conflate the two. As in, if a codebase is using types, it probably wants to write rules with intentional property type checking.
Does that sound reasonable?

Adding the dependency sounds fine.
Is there any way we could avoid adding additional configs? I'm generally not a big fan of adding configs as most people just use recommended and thus miss out on everything else. Could this just be part of recommended (in the next major version) and just no-op for users that aren't using TypeScript or don't have type information available?

no-op for users that aren't using TypeScript or don't have type information available?

In theory, yes. In practice it's kind of tricky. Roughly quoting https://github.com/typescript-eslint/typescript-eslint/pull/7440 -> https://typescript-eslint.io/developers/custom-rules#typed-rules: we (typescript-eslint) have typically recommend against changing rule logic based solely on whether type information exists. In our experience, users are generally surprised when rules behave differently with or without type information. Additionally, if they misconfigure their ESLint config, they may not realize why the rule started behaving differently. Our recommendation has been to either gate type checking behind an explicit option for the rule or creating two versions of the rule instead.
Not saying that that's a certainty forever and always 😄 just the current recommendation and reasoning behind it.
A lot of folks' first instinct is to then have the rules behave differently based on file extension: .js & co for untyped, .ts & co for typed. But some projects have type checking enabled in JS files  via JSDoc so that falls apart. 😞

I do think it's a good point that having automatic rule logic based on environmental factors is not necessarily a great practice and can theoretically cause confusion or reduce the user's ability to achieve their desired behavior.
I will admit to violating this principle in some rules I've written, for example, in eslint-plugin-ember where test rules no-op if test isn't in the current file path. This has allowed us to offer streamlined configuration/setup in the form of a single recommended config that users can simply enable for their entire project once and then forget about, without the need to enable separate configs for source code vs. tests, and without sacrificing runtime performance or the risk that test rules will mistakenly flag non-test code. Realistically, this has worked out well for us, even though I realize there are some theoretical downsides.
Perhaps there's a balance to strike between making everything clear and explicit through extra configuration vs. having some things "just work"...
Getting back to the situation where there's a rule that could optionally take advantage of type information, I lean toward sticking with a single rule and just adding the explicit type-checking option you mentioned. Then the user or a recommended-type-checked config could simply enable the rule with that option enabled to opt-in to the smarter type-checked behavior.
What I prefer to avoid is having to duplicate every rule for this. Having to create a new rule just to start taking advantage of type information is a very high barrier to entry, and having additional versions of rules creates a significant maintenance burden for us and unnecessarily multiples the API surface of the plugin...


Find-Module throws warning complaining about missing credentials

Find-Module -Repository PowershellAzureDevopsServices
doesn't work. It throws the following warning:
WARNING: Cannot access 'https://pkgs.dev.azure.com/redacted/redacted/_packaging/PowershellAzureDevopsServices/nuget/v2'. Are you missing 'Credential' parameter in the cmdlet?
If we have to construct a credential from a PAT every time we want to interact in any way with the repo, this solution is not very practical. Is that really the way it's meant to work, or have I messed up something?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 35b3cd51-b365-433b-9149-697582d64e88
Version Independent ID: 1cb1f4a3-5928-223d-592f-f3462fef4e4c
Content: Use Azure Artifacts as a private PowerShell repository - Azure Artifacts
Content Source: docs/artifacts/tutorials/private-powershell-library.md
Product: devops
Technology: devops-artifacts
GitHub Login: @ramiMSFT
Microsoft Alias: rabououn

@RIKIKU - Thanks for your question. I'm not sure whether there is another way to work with this cmdlet. You might look for or submit an issue here.
In the meantime, please consider these resources:

Azure DevOps Services
Azure DevOps Support Bot
Azure DevOps on Stack Overflow


Flatten /err tests

Summary
Next PR in the flattening process. This one flattens the test/unit/math/prim/*/err to test/unit/math/prim/err and the same for the rev/err tests. This time, compared to the meta flatten, the merged files retain the git history of both files.
No tests were removed and there is only one instance where I could delete duplicated code. This was the ErrorHandlingScalar_out_of_range class in the out of range tests.
Tests
The tests remain the same, just merged together.
Side Effects
/
Checklist

[x] Math issue #937

[x] Copyright holder: Rok Češnovar

[x] the basic tests are passing

[x] the code is written in idiomatic C++ and changes are documented in the doxygen

[x] the new changes are tested

Thanks Marco for the review. I addressed the ordering comments. I dont think we should move more things globally, rather the opposite. Especially if its something small with a generic name like function.

Can you double-check check_finite_test? It seems you removed all strings for the function name, so I don't think it will compile.

Ah, thanks. I started putting it globally then I remembered that is probably not going to work with jumbo tests.

Yeah, its not listed on Wiki or anywhere formally. There are some discussions going on Discourse, but those are easy to miss. So its not something we are formally aiming towards, but we did do some changes that make jumbo-build easier to do (for example https://github.com/stan-dev/math/pull/1422). Its highly unlikely that the global using statements would cause problems in jumbo-builds, but in theory they could I guess. So I dont think this is a priority. It wouldnt hurt us to clean it up tho.

Sorry @mcol. I missed one so this will require a re-approval.


0.13.1 Patch Release

What this PR does / why we need it:
0.13.1 Patch release

Re-running failed tests

/rerun-all - rerun all failed workflows.
/rerun-workflow <workflow name> - rerun a specific failed workflow. Only one workflow name can be specified. Multiple /rerun-workflow commands are allowed per comment.

/lgtm
/approve

Had to rebase and push to signoff all the cherry-picked commits


export markdown preview to pdf

VSCode Version:
1.3

OS Version:
OSX 10.11
VS Code`s markdown preview , it's is very beautiful, but it can't export the preview page

Not only pdf but also HTML. Third-part converting is not so beautiful as VS-Code did.


Add Sachin Shetty to Contributors list

Add Sachin Shetty to Contributors list

@sachinsshetty, I'm quite elated about your pull request. I wanna evolve this project to addresses various problems faced by first-time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a pull request and learned that I merged it?
We’ve recently added Facebook share and tweet feature to our web app. Could you please go to https://roshanjossey.github.io/first-contributions/#social-share and share your first contribution to open source?
Also, check out projects with easy issues while you’re there.


feat: add service discovery for hertz

What type of PR is this?
feat

What this PR does / why we need it (English/Chinese):

en: add service discovery for hertz
ch: 添加服务发现

Which issue(s) this PR fixes:

https://github.com/li-jin-gou/nacos-demo/tree/main/example 这是一个 hertz 服务发现的demo @welkeyever @FGYFFFF


Fix drawer alignment

Type

[ ] Bug fix
[ ] New feature
[x] Improvement to existing feature

Related JIRA Issue(s)
https://www.ebi.ac.uk/panda/jira/browse/ENSWBSITES-462
Importance

Description
This is fixing the alignment of the description in the drawer. There are multiple drawers and hence all these files. Also replacing the dl and dd with div.
Views affected
Genome browser.
Other effects

[ ] I have checked any requirements for Google Analytics
[ ] I have created any required tests
[ ] The PR has as its final commit a WASM/JS update commit if any Rust files were updated.

Possible complications
None

@azangru i have now replaced all the float with grid. The PR is ready to be reviewed.


Update CLI extensions available doc

Update CLI extensions available doc.
Triggered by Azure/azure-cli-extensions - TRAVIS_BUILD_ID=626390823
https://github.com/Azure/azure-cli-extensions/commit/32dc96da9c2729f84f2685d74fb12f89cead5453

Docs Build status updates of commit 99b80df:
:clock10: Full build: the average full build time is 7 min(s) 10 sec(s), this is based on the last 312 build(s) for this repository.

Docs Build status updates of commit 99b80df:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/azure-cli-extensions-list.md
:white_check_mark:Succeeded
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


shadow: don't depend on gnome-doc-utils, use itstool

Describe the bug
Shadow currently uses gnome-doc-utils which is not Python 3 compatible and deprecated.
We may use itstool instead https://github.com/shadow-maint/shadow/pull/163.
Note this is needed to build Nix.
PR in https://github.com/NixOS/nixpkgs/pull/72246
cc @jtojnar

Took a patch from fedora rawhide with which I was able to build the man pages
https://github.com/shadow-maint/shadow/pull/184

@jtojnar I saw your reply regarding the README file. That Makefile is a bit like magic to me. Do we absolutely need that to continue with this PR?

#72246 is now in staging-next


hashing base token results in different pool address on different chains

while base currency has address 0 on different networks, the same base token will have different address on different networks (all tokens not deployed with deterministic deployment and with different wallet nonce will have different address on different chains), therefore making it pointless to using deterministic deployment. Also since base currency has same address on all networks but is a different coin, defies the purpose of unique address.
Therefore, new memory variable must be created by hashing owner address and pool name, which will be used as salt in pool creation and as unique id, allowing an owner to have same pool address for pool with same name on different chains, even if different base token. Must check additional gas cost and alternatives.

the fix ensures backwards compatibility with future factory upgrades, where a pool with a different initialization selector or parameters will still have the same address as long as has same name and owner.


Fix deadlock on plugin shutdown.

Signed-off-by: Anusha Ragunathan<EMAIL_ADDRESS>

LGTM

LGTM

@anusha-ragunathan Failures in experimental do not look like the already reported flaky ones.

https://github.com/docker/docker/pull/25553/files changed how "Active" state was interpreted. It's the desired state and not the actual state. As a result, we dont need to update any state of plugin shutdown.


net: lwm2m: add gateway_obj prefix check to lwm2m_message_handler

The idea of the lwm2m gateway object 25 is that messages can be forwarded from a "gateway" to a connected "childdevice". The server can reach any device managed by the gateway by prefixing the LWM2M CoAP request with the prefix announced by the object. To be able to handle these messages, a callback is implemented in the message handler which forwards these messages if required.

FYI @rerickson1 since you seem to have been involved in GW object introduction.

It is unclear to me, how these Gateway objects are supposed to work.

The spec leaves it up to the implementation to do all the work.
We successfully implemented this on BLE end nodes.
The gateway needed to intercept LwM2M messages and see if there was a prefix. If there was, we used callbacks to then strip off the prefix and forward the CoAP message over BLE.
On the BLE end node we ran the LwM2M client and changed the LwM2M engine so it wasnt dependent on sockets. We made an abstraction layer in the engine so you could hook in any transport for sending/receiving the LwM2M CoAP messages.
I can point anyone to all the open source code that made this happen. Getting proper gateway support in the Zephyr tree would be great.
The other piece is having a server that supports it. Has Leshan made any headway yet?
Your proposal sounds like it could work.

From my point of view, this looks OK now.
But I would like @rerickson1 to give a final thought on this, as he has been using the GW object before.
Hopefully this does not conflict the previous usecase.
I think this now makes a sense. Gateway callback may create the CoAP response as they wish and the LwM2M engine actually handles sending&retrying it back.
I hope someone can test this and verify if the code that I suggested is actually working. I would even like if someone can show some examples of its use.

From my point of view, this looks OK now. But I would like @rerickson1 to give a final thought on this, as he has been using the GW object before. Hopefully this does not conflict the previous usecase.
I think this now makes a sense. Gateway callback may create the CoAP response as they wish and the LwM2M engine actually handles sending&retrying it back. I hope someone can test this and verify if the code that I suggested is actually working. I would even like if someone can show some examples of its use.

Agree, this is good for now.
To make this useful, there needs to be be a change to abstract the LwM2M engine away from sockets.
Formalizing a PR based on something like this: https://github.com/LairdCP/zephyr/commit/46c0c9f784c9c94d447df6189672ec23dea17fc2


anstream feature does not exist

> cargo +nightly udeps
error: failed to select a version for `env_logger`.
    ... required by package `replica v1.0.4 (/Users/anacrolix/getlantern/replica-rust)`
versions that meet the requirements `*` (locked to 0.11.5) are: 0.11.5

the package `replica` depends on `env_logger`, with features: `anstream` but `env_logger` does not have these features.
 It has an optional dependency with that name, but that dependency uses the "dep:" syntax in the features table, so it does not have an implicit feature with that name.

failed to select a version for `env_logger` which could resolve this conflict

Sounds like a bug in replica as that feature doesn't exist.

Ah no it's because the default feature lists anstream as a default, but anstream is a feature of a dependency.

As env_logger doesn't have an anstream feature (its an optional dependency enabled via color), this seems to be a bug in replica-rust and not env_logger, so I'm going to go ahead and close this.


delay is not defined

{
"session": "test1",
"data": [
{
"to": 6288***,
"text": "Hello user 1",
"delay": 0
},
{
"to": 6288***,
"text": "Hello user 2",
"delay": 1000
}
]
}
Is my Postman request correct or is there something wrong, and how do I send a request for bulk messaging?

Sorry for being confusing, I think it's the time for refactoring my code.

{ "session": "test1", "data": [ { "to": 6288***, "text": "Hello user 1", "delay": 0 }, { "to": 6288***, "text": "Hello user 2", "delay": 1000 } ] }
Is my Postman request correct or is there something wrong, and how do I send a request for bulk messaging?

Thanks, it's great waiting for it

Hi, I have updated the code. Please pull your code to latest commit.
Here is examples for sending bulk messages
POST /send-bulk-message

Hi, I have updated the code. Please pull your code to latest commit.
Here is examples for sending bulk messages
POST /send-bulk-message
{ "session":"dev", "delay" : 10000, "data": [     {       "to": "628xxxx",       "text": "TESTING1"     },     {       "to": "628xxxx",       "text": "TESTING2"     },     {       "to": "628xxxx",       "text": "TESTING23"     },     {       "to": "628xxxx",       "text": "TESTING24453"     },     {       "to": "628xxxx",       "text": "TESTING2445"     },     {       "to": "628xxxx",       "text": "TESTING256234234"     },     {       "to": "628xxxx",       "text": "TESTING234242424234324"     }   ]}

Big thanks bro... nicely run


Fix Favorites overlay animation

Task/Issue URL: https://app.asana.com/0/856498667320406/1127120102379332
Description:
Sometimes Favorites Overlay is displayed with what seem to be a lag - it appears after the keyboard is animated in. Please se related task for details about the fix.
Steps to test this PR:
According to my experience it is best to test that on an iPad device.

Navigate to some page.
Tap on URL so Overlay is being shown.
Observe whether animation works OK.

Also please double check regressions scenarios:

Tapping URL on empty home screen.
Canceling & re-entering overlay.

Internal references:
Software Engineering Expectations
Technical Design Template

Thanks @brindy :)


the dimension of the visual feature

how to project the 2028-dim bottom-up feature vector to 1024 in section 3.4  ?
Looking forward to your reply, thank u very much.

Via a linear projection. See line 75 in AttModel.py.

oh, I see,  thanks a lot


Simplify release action

Description
This simplifies the release action (which is currently broken by PR #606)
Related Issues
#606
Checklist
N/A
Additional Notes or Comments
N/A

Codecov Report
Patch coverage has no change and project coverage change: +0.04% :tada:

Comparison is base (aa0f7f7) 79.66% compared to head (9c134c9) 79.70%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #619      +/-   ##
==========================================
+ Coverage   79.66%   79.70%   +0.04%
==========================================
  Files          79       79
  Lines        4819     4819
==========================================
+ Hits         3839     3841       +2
+ Misses        980      978       -2

see 1 file with indirect coverage changes

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


Extending IndicBert V2

I have some data for three low resource languages, two of them are not in the list of 24 languages of IndicBERT V2 and for one I may have some more data. I want to continue training on this data from the V2 checkpoint. There is a pre-training script for IndicBERT. Could you please help me with how to do this? In particular, I am not clear about how to use the language codes to continue pre-training. My purpose is to use it for MT as well as for some basic NLP tasks like POS tagging, NER etc.
Should the pre-training be different for multilingual parallel corpora and multilingual monolingual corpora? Or will only fine-tuning be different? In either case, how to proceed properly? I don't have experience working with BERT before.

Thanks for your Q.
You can prepend a language tag  to the sentences you have and continue training. We have not released the original TF ckpts, but only the HF ckpts. I think you should be able to use the this code to try further fine-tuning
WRT the Q on translation, I'm not fully sure how you plan to use this model for translation. This is an encoder-only model and will not be able to do any generation (unless you are referring to initialising the decoder weights also with encoder weights).

For MT, I have something like this in mind:
https://jlibovicky.github.io/2020/03/05/MT-Weekly-BERT-for-MT.html
https://aclanthology.org/D19-5611.pdf
It might not be as good as using,say, mBART for MT, but it might be a good baseline. What is your opinion?
Thanks for the info about how to use language code to continue training.

This looks interesting, I have not tried this before so I don't have an opinion on this.
But if you do this experiment, please do share the results with us.
Happy to help if you have any further questions with the model.

You can actually load encoder-only checkpoints into encoder-decoder models on HF like this. But note that the cross-attentions are initialized randomly and you need a decent amount of data to train them.

Yes,it makes sense. Thanks for the link.

I was busy for a travel for the last few days.
Sure, I will share the results with you once I have tried this out.
On Mon, Feb 6, 2023, 5:14 PM Sumanth Doddapaneni @.***>
wrote:

This looks interesting, I have not tried this before so I don't have an
opinion on this.
But if you do this experiment, please do share the results with us.
Happy to help if you have any further questions with the model.
—
Reply to this email directly, view it on GitHub
https://github.com/AI4Bharat/IndicBERT/issues/1#issuecomment-1418950768,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAQUQJQG2TCFZRZJXKA6XULWWDPZJANCNFSM6AAAAAAUO7KQME
.
You are receiving this because you authored the thread.Message ID:
@.***>


Add Vim Cursor

Vim Cursor is a rectangle with the character inside of it. This commit adds a member function called setVimCursor() and vimCursor() that sets and retrieves the cursor type the QCodeEditor is presenting. This cursor is only visible when FakeVim is attached to the Editor. The Rectangle is visible when in Normal/Visual mode and a zero width line is visible when in insert mode.

The cursor color on my machine is different from your screenshot:

The color of the cursor should be the color of the text.
And, why is it a "I" in insert mode? In my real vim, it is a block (the same as the normal mode) in the insert mode.

BTW, you can update the submodule without merging this into master. You can merge this when the FakeVim in CP Editor is finished.

You can work on FakeVim of CP Editor first. There are too many bugs/problems now, sometimes I can't tell whether it's a problem of the text cursor or a problem of FakeVim itself.

You can work on FakeVim of CP Editor first. There are too many bugs/problems now, sometimes I can't tell whether it's a problem of the text cursor or a problem of FakeVim itself.

It will be helpful if you could list them (maybe here, or by opening a PR from fakevim and in that thread).
As for bugs, I have found some highlighting issues when selecting block in visual mode. Save, Quit are not implemented correctly. I am thinking of how to behave for :w when untitled, :r, :q :q! other functions are not implemented correctly.

It will be helpful if you could list them (maybe here, or by opening a PR from fakevim and in that thread).

There are too many. Can't you find any? I can list them when you think everything is OK.

It will be helpful if you could list them (maybe here, or by opening a PR from fakevim and in that thread).

There are too many. Can't you find any? I can list them when you think everything is OK.

I have already mentioned some issues that I have found. I am just implementing things haven't tested much. But there are limitations of fakevim, it doesn't supports all vim commands. As for how I added support for fakevim, most of code comes from fakevim example.

And, why is it a "I" in insert mode? In my real vim, it is a block (the same as the normal mode) in the insert mode.

It is "I" in my neovim and all other vim emulation tools that I use, like IdeaVim, VSCode Vim Emulation, Visual Studio Vim Emulation. The block represents the "Replace" mode. So If you press "Ins" it toggles from Insert mode to Replace mode and vice versa. Just as expected, in Replace mode it becomes a block.

The color of the cursor should be the color of the text.

This is from Kate (KDE Notepad++ like an editor). It does not changes the cursor colour to text colour. Rather it generates contrast between the cursor and the text using a Difference Composition mode.

auto cp = /* cursor painter */;
cp.setPen(Qt::NoPen);
cp.setBrush(palette().color(QPalette::Base));
cp.setCompositionMode(QPainer::CompositionMode_Difference);

@ouuan could you please review this PR?


refactor(embassy)!: extract arch modules as crates

Description

This PR extracts the arch modules (the manufacturer-specific modules previously found in riot-rs-embassy) as separate, manufacturer-specific crates. A major benefit of this is allowing to generate user-visible documentation for these crates, which was not possible before because (a) only one arch module could be enabled at a time and (b) it was not possible to enable any of them for documentation, because of them being manufacturer-specific.
Extracting these modules as separate crates has required to:

Introduce a new crate (whose temporary name is riot-rs-shared-types) to break cyclic dependencies between crates/types: this new crate is depended upon by every manufacturer-specific crate.
Revisit some types in the new riot-rs-shared-types crate to accommodate manufacturer-specific variants in enums, by introducing simple generics on them.
Work around the orphan rules in some internal cases.
Introduce the relevant Cargo features for individual manufacturer-specific crates. Only features that are actually useful for the crate are introduced. This introduces a slight increase in duplicated features in the tree, but has the benefit of documenting what features are actually provided by each manufacturer-specific crate.

Issues/PRs references

Depends on #391
Depends on #394
Open Questions

Testing
Before autosquashing, the following have been successfully tested in hardware:

example/gpio on nRF52840-DK, nRF5340-DK, ESP32-C6, RP2040, ST-NUCLEO-WB55RG
example/embassy-http-server

on ESP32-C6, RPi Pico W with Wi-Fi
on nRF52840-DK, ST-NUCLEO-WB55RG on Ethernet over USB

TODO

[x] Clean up the circumventions around the orphan rule limitations

Future work

[ ] Generate documentation for these new manufacturer-specific crates

Change checklist

[x] I have cleaned up my commit history and squashed fixup commits.
[x] I have followed the Coding Conventions.
[x] I have performed a self-review of my own code.
[x] I have made corresponding changes to the documentation.

Please squash & rebase. Looks fine already, I'll give it a final review by tomorrow.


Privilege to activate role

Is there any privilege required to activate a role? Or the target user can activate the role?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 3a831056-b759-8539-ca86-9fbb84f331d7
Version Independent ID: 8fca63cc-bd36-d774-1f31-eca19502b006
Content: Activate my Azure resource roles in PIM
Content Source: articles/active-directory/privileged-identity-management/pim-resource-roles-activate-your-roles.md
Service: active-directory
GitHub Login: @rolyon
Microsoft Alias: rolyon

@thuansoldier Thanks for your feedback! We will investigate and update as appropriate.

@thuansoldier Yes, you need to be a "Privileged Role Administrator" role to manage assignments for other administrators in Azure AD PIM.  Please refer to Enable Privileged Identity Management for your directory
 for more information.

@thuansoldier We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Inference example update

Also including suggestion from https://github.com/zsc/tau/pull/1 to use more general class AutoModelForCausalLM instead of OPTForCausalLM to support more models.

Thanks @zsc for your suggestion!


Look into stability of the simulation (particularly collisions since they are still kinda trying to be crazy)

This is a good issue lmao


Prevent duplicate filters in criteria

EntityGroup criteria with multiple entity groups that contain the same occurrences would generate the same filter multiple times.

Does the condition criteria plugin contain multiple entity groups? I thought it would just be conditionPerson. Or do you mean that conditionOccurrence is contained in multiple entity groups?

Nevermind, just saw your Slack message. Now I understand it's the former -- the AoU underlay specifies multiple entity groups.


linux-35 lost external connection from phone device.

Type of Request
bug
Infrastructure Environment
LUCI, Github, Cocoon scheduler, Autosubmit, etc...
What is happening?
linux-35 lost external connection from phone device.

Steps to reproduce
Step 1:
Step 2:
..
Step n:
Expected results
I expect to see X when Y is finished.

Power off machine and then rebooting phone device to restore connection.


Appstudio update mvp-test-component

Pipelines as Code configuration proposal

Pipelines as Code CI/mvp-test-component-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
6 seconds
init

✅ Succeeded
21 seconds
clone-repository

✅ Succeeded
1 minute
build-container

✅ Succeeded
9 seconds
sanity-inspect-image

✅ Succeeded
18 seconds
clair-scan

✅ Succeeded
9 seconds
deprecated-base-image-check

✅ Succeeded
1 minute
clamav-scan

✅ Succeeded
10 seconds
sbom-json-check

✅ Succeeded
7 seconds
sanity-label-check

✅ Succeeded
9 seconds
sanity-optional-label-check

✅ Succeeded
6 seconds
show-summary

Pipelines as Code CI/mvp-test-component-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
6 seconds
init

✅ Succeeded
21 seconds
clone-repository

✅ Succeeded
1 minute
build-container

✅ Succeeded
9 seconds
sanity-inspect-image

✅ Succeeded
9 seconds
deprecated-base-image-check

✅ Succeeded
18 seconds
clair-scan

✅ Succeeded
1 minute
clamav-scan

✅ Succeeded
10 seconds
sbom-json-check

✅ Succeeded
7 seconds
sanity-label-check

✅ Succeeded
9 seconds
sanity-optional-label-check

✅ Succeeded
6 seconds
show-summary


Fix of details for UG & DG

Fix some consistency issues.
Previously we had both use of 'App' and 'app', now it's all 'app'

Linking #148.

This PR is docs only, so I'm going to move ahead with the JAR and wrapup.

Moving to next milestone so that we can wrap up v1.3b, but we could still try to merge this today before the PE dry run if we want.


⚠ Fetchers has degraded performance

In e4466ae, Fetchers ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 486 ms

Resolved: Fetchers performance has improved in 68821be.


Documentation should cover how to prevent container from using swap

File: engine/admin/resource_constraints.md, CC @mstanleyjones
The documentation for --memory-swap is rather confusing. What I wanted to do was run a container without allowing it to use swap. An initial guess would be doing something like
--memory 1g --memory-swap 1g but reading the documentation says that
If --memory-swap is set to the same value as --memory, and --memory is set to a positive integer, the effect is the same as setting --memory-swap to 0 (the value is treated as unset).

that then implies the behaviour is what the behaviour would be if --memory-swap is not set.
If --memory-swap is unset, and --memory is set, the container can use twice as much swap as the --memory setting, if the host container has swap memory configured. For instance, if --memory="300m" and --memory-swap is not set, the container can use 300m of memory and 600m of swap.

To me this is not intuitive behaviour at all but if this is Docker's current behaviour I feel it should be documented more explicitly that this is the case. I also think that given that preventing as much swap use as possible is a common use case I feel that how to achieve this (if it is possible) should be explicitly documented. If it isn't possible to do this it should be documented.

In fact I'm not convinced this documentation is accurate at all. I'm using Docker 17.06.0-ce. When I launch a container like so
docker run --rm -ti --memory 16g --memory-swap 16g image_name

I can inspect the container cgroup to see that memory.memsw.limit_in_bytes and memory.limit_in_bytes are set how I would intuitively expect them to be set
$ cd /sys/fs/cgroup/memory/docker/<id>
$ cat memory.memsw.limit_in_bytes
16777216
$ cat memory.limit_in_bytes
16777216

This directly contradicts what the documentation states.

@cpuguy83 this keeps coming up. Can you help me make it better?

if this is Docker's current behaviour I feel it should be documented more explicitly that this is the case.

Can you explain how it can be more explicitly documented?

I'll have to go through all this again.
I think we had another similar issue...

Ok, the disconnect is that --memory-swap is the memory+swap limit.
Setting the memory-swap limit to the same value as the memory limit effectively means there is no way to use swap in addition to RAM.
It might be nice if we abstracted this better (like with did with --cpus) rather than dealing with the direct cgroup controls.

@cpuguy83

Can you explain how it can be more explicitly documented?

I mean explain explicitly how to setup a container to not use swap space (i.e. set --memory X --memory-swap X). The way the documentation is written write now implies this is impossible with is not the case.

If I understand this right, then you would accomplish the goal of never using swap for a container by setting --memory and --memory-swap to the same value. Right @cpuguy83 ?
(you could also just disable swap on your Docker host :trollface: )

@mstanleyjones That is correct.

@cpuguy83 What happens when both --memory and --memory-swap are unset? I cannot find the default documented.

The default is no limit.

@cpuguy83 If I understand correctly, if both --memory and --memory-swap are unset, and free -h shows total swap as 1.0G, Docker container will use up to 1.0G of swap? If both --memory and --memory-swap are unset, and free -h shows total swap as 0B, Docker container does not use any swap?

I doubt that "free" is cgroup aware.
But yes if there is no swap on the system then the container cannot use swap.


Add work history contact further information request flow

The TRA have identified a number of applications from India where the referee for work history is not of an appropriate level.
The TRA are going to FI the applicant to get a new name and email address - the referee will be for the work period and school.
There are currently 182 applications where the TRA will be requesting this information.
This PR adds elements to the assessor interface to request further information for teachers and flag which work history items this applies to. Additionally this PR adds pages into the teaching interface to provide this information.

Looks good, I've left a few comments. It would be good to split the commit in to smaller chunks as well with descriptions as it's a lot of changes to go in one commit I'd say.

Heya; my internet on my Mac is completely broken ATM. Im heading into the office to try and fix. I don't have slack or emails on my phone so I thought this was the best way to get in contact.


Remote Update (interactions): donovandmc/interactions-rewrite

This pull request has been superseded by #389


scheduled task do not work as expected

Hello,
I created a task to run each 15 minutes via Django admin form, but it runs each minute.
the setting is like this:
Q_CLUSTER = {
    'name': 'DjangORM',
    'workers': 1,
    'retry': 120,
    'catch_up': False,
    'orm': 'default'
}

Are you sure you set the minutes field in the admin for the schedule?
If that field is left blank for some reason, the schedule will default to every minute.

yes I'm sure.
today, i see an interesting behaviour: after about 40 minutes of running, it turned to run as expected!

as the new issue seems same, i post it here:
after some repeats of successful scheduled job, the job just do not run any more.
as i run the cluster with supervisor, the supervisor stop/restart command has no effect to cluster
so i kill the cluster, and start everything again to work until the unexpected freeze again
no log, no exception, !!!

I would love to help you with this. I will need some way of reproducing this, cause when I try this with your settings on my local and my test environment, it works just fine.
Also no one else has ever reported this before, so it is probably a very specific issue.
Is there any way you can give me more details on why this would happen in your setup and not in others?

I ran this locally with your settings:

Created a 15 minute schedule in the admin:

Then I ran it for a few hours, stopped the cluster and restarted it:

It all seems to behave as expected with these settings.

@Koed00 thank you for considerations.
an interesting thing that may help is that when the tasks stop running, in the admin page the next run parameter is around the task last execution time. so the cluster do not try to do it any more.
I'm trying to investigate more on this and let you know when understand what happens here.

@mbande ever found a solution for this?


Game Server Management

Many games have a dedicated server available for them. Most come in the form of a Windows executable that outputs via stdout. We could launch these processes and capture their output and broadcast it over websockets. Start would be easy, just starting the process in the background.
Stop might be more challenging? Some games may work better with an input. For the first iteration we probably don't have to worry about this.

This is largely implemented so I'm closing it. Check the project board for any enhancements.


Sort Metervalues with newest first and fix using correct transactionDB Id

Sort Metervalues with newest first and fix using correct transactionDB Id.

@ChrisWeissmann are there screenshots of the changes, or is the data view pretty much the same?

@ChrisWeissmann are there screenshots of the changes, or is the data view pretty much the same?

added screenshots


add pause requested variable that doesn't switch off on hover

hey Ken,
so my problem was when you explicitly pause the carousel, a mouse over will then restart it (if pause on hover is set to true)
here's the problem in action
http://jsfiddle.net/d7ecuaxw/2/
this pull request fixes it as you can see
http://jsfiddle.net/n5cqfrtq/4/
Let me know what you think, will gladly alter it if you think its necessary.
Cheers,
Fred

Is this related?
https://github.com/kenwheeler/slick/pull/1086

ahhh yes it is, and Joe's fix is better, closing.

actually scratch that, it looks like that bug fix needs to applied to the initDotEvents as well, so the bug still exists.
Its only been fixed in the event that the dots aren't there. I still like Joe's fix better, but I'll create a new pull request later, to cover the dots

:+1:

btw, pull request submitted #1114


Tidying

Remove the reset-to-firmware code and some other unused functions.
(How did I end up in the tools code today...)

Pull Request Test Coverage Report for Build 916037740

0 of 0   changed or added relevant lines in 0 files are covered.
77 unchanged lines in 3 files lost coverage.
Overall coverage increased (+0.3%) to 70.258%

Files with Coverage Reduction
New Missed Lines
%

ttblit/tool/metadata.py
18
64.0%

ttblit/tool/flasher.py
22
60.92%

ttblit/core/blitserial.py
37
20.51%

Totals

Change from base Build 878869875:
0.3%

Covered Lines:
926

Relevant Lines:
1318

💛  - Coveralls

Seems to still work! (I don't know what else I should expect haha)
Batch flashing does make me wonder if the 32blit utility should output the filename/title or some information about what it's flashing.
for f in examples/*/*.blit; do 32blit install $f; done
Flashing...: 42.9kB [00:00, 366kB/s]
Flashing...: 25.4kB [00:00, 322kB/s]
Flashing...: 45.9kB [00:00, 306kB/s]
Flashing...: 23.8kB [00:00, 347kB/s]
Flashing...: 20.2kB [00:00, 231kB/s]
Flashing...: 76.8kB [00:00, 277kB/s]
Flashing...: 38.1kB [00:00, 179kB/s]
Flashing...: 28.7kB [00:00, 357kB/s]
Flashing...: 34.6kB [00:00, 360kB/s]
Flashing...: 24.9kB [00:00, 250kB/s]
Flashing...: 23.9kB [00:00, 290kB/s]
Flashing...: 24.8kB [00:00, 285kB/s]
Flashing...: 1.14MB [00:03, 380kB/s]
Flashing...: 26.0kB [00:02, 13.0kB/s]
Flashing...: 30.1kB [00:00, 295kB/s]
Flashing...: 28.4kB [00:00, 261kB/s]
Flashing...: 100%|███████████████████████████████████████████████████████████████████████████████████████████████████████████| 32.3k/32.3k [00:00<00:00, 363kB/s]
Flashing...: 23.7kB [00:00, 267kB/s]
Flashing...: 53.8kB [00:00, 387kB/s]
Flashing...: 29.9kB [00:00, 159kB/s]
Flashing...: 51.4kB [00:00, 386kB/s]
Flashing...: 28.1kB [00:00, 378kB/s]
Flashing...: 26.1kB [00:00, 285kB/s]
Flashing...: 41.4kB [00:00, 400kB/s]
Flashing...: 25.6kB [00:00, 377kB/s]
Flashing...: 45.8kB [00:00, 296kB/s]
Flashing...: 38.2kB [00:00, 383kB/s]
Flashing...: 30.4kB [00:00, 353kB/s]
Flashing...: 100%|███████████████████████████████████████████████████████████████████████████████████████████████████████████| 53.2k/53.2k [00:00<00:00, 356kB/s]
Flashing...: 124kB [00:00, 340kB/s]
Flashing...: 27.6kB [00:00, 161kB/s]
Flashing...: 35.8kB [00:00, 374kB/s]
Flashing...: 29.4kB [00:00, 299kB/s]
Flashing...: 29.8kB [00:00, 353kB/s]
Flashing...: 2.03MB [00:06, 338kB/s]
Flashing...: 26.2kB [00:03, 7.37kB/s]


Convert wrapping from boolean to enum

Switch from specifying border wrapping with a boolean—true for wrapping (toroidal for rectangular world shape) and false for non-wrapping border—to an enum—specifically the same enum used for the shape since the wrapping options are shape dependent.

See more-shapes branch.

6f503ac6181af5f9514fac3c495033447ee0e5b6 Convert from Boolean to enum shape specification
Convert from specifying border shape with a Boolean (true for round,
elliptic, or circular borders and false for square or rectangular
borders) to specifying border shape using the Shape enum (with
RECTANGULAR for square and rectangular worlds and ELLIPTIC for circular
and elliptic borders).

95411c6a5d1338e4e61db8cccfcf832d57c898af Use Shape to store wrap setting, add cylindrical
Incorporate border wrapping into the Shape enum, using TOROIDAL and WRAPPED_ELLIPTIC for the wrapped versions of RECTANGULAR and ELLIPTIC, respectively.  Also add CYLINDRICAL so worlds with rectangular borders can be wrapped in x, but not z.

Builds on #1.

95411c6a5d1338e4e61db8cccfcf832d57c898af Use Shape to store wrap setting, add cylindrical
Incorporate border wrapping into the Shape enum, using TOROIDAL and WRAPPED_ELLIPTIC for the wrapped versions of RECTANGULAR and ELLIPTIC, respectively.  Also add CYLINDRICAL so worlds with rectangular borders can be wrapped in x, but not z.

In pre-release version 2.0.0-dev-20w29a.


Adding the remaining animations

Feature Description
Current Animations are not working in preview:

Animation
Laser
Snowflake
Picture

Animations I plan to work on:

[x] Animation
[x] Laser

Animations @anhanh11001 will to work on:

[x] Snowflake
[ ] Picture

Would you like to work on the issue?
Yes

Are you still working on this or can we split the work in here so that I can work on making 1 or 2 animations?

@anhanh11001 Currently 4 animations are remaining:
Animation
Laser
Picture
Snowflake
Let's divide it. I can work on Animation and Laser and you can work on Picture and Snowflake

@anhanh11001 are you planning to work on Picture animation mode?

@adityastic will send the PR tomorrow, I was in the test week last week so I didn't have time to do anything, will continue to work from now on!!

@anhanh11001 great


fix regex filter for cleaner_exec - closes refs #36

fix for issue #36

Good work! Could you remove https://github.com/staszek-arsdata/resque-cleaner/commit/49925c9aaaabedd1733671b629fbd786d853bd86 from the pull request? I will look after the version bump.

Thanks. I was having problems with bundler updating the gem in my project, so I added version bump, after pull request.  Looks like this commit has been added to pull request too. I'm new to github. Commit removed. Is it OK now?

great :+1: will merge and do version bumping soon. thanks a lot!

Great! Thanks for awesome resque plugin!

@staszek-arsdata merged, version bumped and pushed to ruby gem: https://rubygems.org/gems/resque-cleaner
thanks again for contributing!


RequestError: TransportError(400, u'search_phase_execution_exception', u'Failed to compile inline script [hamming_score] using lang [native]')

RequestError: TransportError(400, u'search_phase_execution_exception', u'Failed to compile inline script [hamming_score] using lang [native]')

You have to compile and install elasticsearch score plugin first. Follow the README for more details.
Thanks.


Crash in BugsnagClient.m line 818

Describe the bug
Crash of unknown origin coming from Bugsnag. We have seen 1 crash coming from 1 user so far.
Steps to reproduce
Unknown
Environment

Bugsnag version: 6.2.3
CocoaPods version: 1.9.3
Carthage version (if any): n/a
iOS/tvOS/macOS version(s): 14.0.1
Simulator or physical device: iPhone 8 Plus
Xcode version: 12.1
Swift version (if applicable): 5.1

Stack Trace

Stack trace:
Fatal Exception: NSInvalidArgumentException
-[NSOperationQueue addAutoBreadcrumbOfType:withMessage:andMetadata:]: unrecognized selector sent to instance 0x107e18e50

0  CoreFoundation                 0x198d31114 __exceptionPreprocess
1  libobjc.A.dylib                0x1ac557cb4 objc_exception_throw
2  CoreFoundation                 0x198c419b8 -[NSOrderedSet initWithSet:copyItems:]
3  CoreFoundation                 0x198d33758 ___forwarding___
4  CoreFoundation                 0x198d356cc _CF_forwarding_prep_0
5  MyApp                           0x1054df0d4 __42-[BugsnagClient setupConnectivityListener]_block_invoke + 818 (BugsnagClient.m:818)
6  MyApp                           0x1054d6604 BSGConnectivityCallback + 97 (BSGConnectivity.m:97)
7  SystemConfiguration            0x1991cce44 reachPerformAndUnlock
8  SystemConfiguration            0x1991cd6e0 ____SCNetworkReachabilityRestartResolver_block_invoke_2
9  libnetwork.dylib               0x199918930 __nw_resolver_update_client_block_invoke
10 libdispatch.dylib              0x198969298 _dispatch_call_block_and_release
11 libdispatch.dylib              0x19896a280 _dispatch_client_callout
12 libdispatch.dylib              0x1989464fc _dispatch_lane_serial_drain$VARIANT$armv81
13 libdispatch.dylib              0x198946fe8 _dispatch_lane_invoke$VARIANT$armv81
14 libdispatch.dylib              0x198950808 _dispatch_workloop_worker_thread
15 libsystem_pthread.dylib        0x1de6145a4 _pthread_wqthread
16 libsystem_pthread.dylib        0x1de617874 start_wqthread

Hi @sethfri ,
Thanks for raising, we will investigate and get back to you.

This is now fixed in v6.2.6.


Prioritise using allowlist from ShopifySecurityBase

Description
Fixes warnings in applications that use quilt rails in combination with Shopify Security Base
DEPRECATION WARNING: whitelist is deprecated and will be removed from Rails 6.2 (use allowlist instead) (called from call_proxy at /Users/dougedey/.gem/ruby/2.7.3/gems/quilt_rails-3.4.2/lib/quilt_rails/react_renderable.rb:23)

The whitelist method is deprecated and we should be using allowlist when it is available, this was we're compatible with apps using an old version of ShopifySecurityBase where the allowlist method was added.
This is not a breaking change
Type of change

[x] Quilt_rails Patch: Bug (non-breaking change which fixes an issue)
[ ]  Minor: New feature (non-breaking change which adds functionality)
[ ]  Major: Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

[x] I have added a changelog entry, prefixed by the type of change noted above (Documentation fix and Test update does not need a changelog as we do not publish new version)

Shopify's style guide prefers allow-list/deny-list vs. white-list/black-list.

Shopify's style guide prefers avoiding terms like "white-list" and "black-list".
Drop in replacements include "allow-list" and "deny-list", or "clearlist" and "blocklist". Also consider if there is a domain specific term you could use.
For example, "parameter white-list" could be replaced with "parameter allow-list", but "trusted parameters" may more suitable.

After this is merged, I'll do a new PR to bump the dependency on Shopify Security base and remove this check, I think that will be a minor release (but open to it being a major)

After this is merged, I'll do a new PR to bump the dependency on Shopify Security base and remove this check, I think that will be a minor release (but open to it being a major)

Actually, I can't force an optional dependency version in the Gemspec, I'd have to enforce the Dependency in the gemspec, not a if this dependency exists it must be above this version, unless I do that in the code, but that isn't something I like doing.


handle error in /admin/store/create POST when the email address for the store already exists

Here is an example call that triggers the error:
$ curl -v --cookie "adminEmail=wv6kyV14ZoF5tMlVLrBP%2FgPLkvEFKog2Lvu%2F8PY4zt4tWbQwbki7hG3Mn83Zilr6LTGWdphD4mnDL96RvMbcxWj1rZbhfQ%3D%3D" -X POST -d<EMAIL_ADDRESS>'http://localhost:8101/admin/store/create'
Note: Unnecessary use of -X or --request, POST is already inferred.
*   Trying ::1...
* connect to ::1 port 8101 failed: Connection refused
*   Trying <IP_ADDRESS>...
* Connected to localhost (<IP_ADDRESS>) port 8101 (#0)
> POST /admin/store/create HTTP/1.1
> Host: localhost:8101
> User-Agent: curl/7.50.1
> Accept: */*
> Cookie: adminEmail=wv6kyV14ZoF5tMlVLrBP%2FgPLkvEFKog2Lvu%2F8PY4zt4tWbQwbki7hG3Mn83Zilr6LTGWdphD4mnDL96RvMbcxWj1rZbhfQ%3D%3D
> Content-Length: 33
> Content-Type: application/x-www-form-urlencoded
>
* upload completely sent off: 33 out of 33 bytes
< HTTP/1.1 500 Internal Server Error
< Transfer-Encoding: chunked
< Date: Mon, 17 Oct 2016 13:18:26 GMT
< Server: Warp/3.2.8
<
* Connection #0 to host localhost left intact
Internal Server Error

Here is the server log:
[Debug#SQL] INSERT INTO "store_email"("email","created","updated","deleted") VALUES(?,?,?,?); [PersistText "kucipong.dev@gmail.com",PersistUTCTime 2016-10-17 13:18:26.971963991 UTC,PersistUTCTime 2016-10-17 13:18:26.971963991 UTC,PersistNull]
Spock Error while handling ["admin","store","create"]: SqlError {sqlState = "23505", sqlExecStatus = FatalError, sqlErrorMsg = "duplicate key value violates unique constraint \"store_email_pkey\"", sqlErrorDetail = "Key<EMAIL_ADDRESS>already exists.", sqlErrorHint = ""}
POST /admin/store/create
  Params: [("storeEmail","kucipong.dev@gmail.com")]
  Request Body<EMAIL_ADDRESS>  Accept: */*
  Status: 500 Internal Server Error 0.005012023s

Also handle Mailgun errors like this:
[Debug#SQL] INSERT INTO "store_email"("email","created","updated","deleted") VALUES(?,?,?,?); [PersistText "email@email.com",PersistUTCTime 2016-10-24 11:49:51.274245552 UTC,PersistUTCTime 2016-10-24 11:49:51.274245552 UTC,PersistNull]
[Debug#SQL] SELECT "email","created","updated","deleted","login_token","expiration_time" FROM "store_login_token" WHERE "email"=? ; [PersistText<EMAIL_ADDRESS>[Debug#SQL] INSERT INTO "store_login_token"("email","created","updated","deleted","login_token","expiration_time") VALUES(?,?,?,?,?,?); [PersistText "email@email.com",PersistUTCTime 2016-10-24 11:49:51.285502194 UTC,PersistUTCTime 2016-10-24 11:49:51.285502194 UTC,PersistNull,PersistText "q6SOaTVZir336/ARuP9siNvKVuA2PibVEaH9MPLCmmo6xWfcTaMZzOd+l2uKgOGwVHg=",PersistUTCTime 2016-10-25 11:49:51.285502194 UTC]
Spock Error while handling ["admin","store","create"]: Err {errErr = HailgunError, errExtra = Just "Sandbox subdomains are for test purposes only. Please add your own domain or add the address to authorized recipients in domain settings."}
POST /admin/store/create
  Params: [("storeEmail","email@email.com")]
  Request Body: storeEmail=email%40email.com
  Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
  Status: 500 Internal Server Error 6.468709071s


Better test helpers

I want to improve the tests for these, but I also want to get this opened up so I can get feedback on wording for the failure messages.
The problem with using the default ExUnit.Assertions helpers is that they included messages that weren't emails and it wasn't always clear what the problem was. So I've implemented these helpers to give better messages to users when things go wrong. It should hopefully help people debug their tests more quickly and effectively

This looked good to me.


fix(memo-get-gatsby): Updating memo-get-gatsby

:tada: This PR is included in version 1.9.15 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Added support for other front-end frameworks

Added Knockbackjs

@maridilip Please also provide an example website where this can be tested.

I am working on this can u give me two days time as I am away

@maridilip Sure

@maridilip Instead of injecting we can take care of the knockout case in the else statement

ok that sounds fine. i m new to git and there r merge conflicts which i am not sure how to do. I have the code, but unable to update.


Feature Request: Ability to add a caret icon

Hey Max!
Would you be amenable to adding an optional right-ride icon, like in select boxes?  It's nice in scenarios where you want to indicate that some default options will be shown (or even potentially all of them).  I'm currently having to hack it in by wrapping live select, absolutely positioning the icon overtop of the input, and adding an additional hook to send a focus event to the input when the user clicks on the icon itself:

I'm happy to take on this work but I wanted to ask first.
Thank you for your work on this library!
Andrew

Hi Andrew, nice to meet you here!
So basically, when you click the button, it will be just like clicking on the text input field (i.e. the dropdown will open and show the default options) ?
Yes, I'm definitely open to this. I think an open question would be how this button would work together with the clear button (see the "allow_clear" option here). However, I suppose this caret button will be shown only if nothing is selected, right? In which case it will never have to be displayed together with the clear button, so no problem there. Otherwise, we'll have to think of something.
My only general suggestion/request would be to render the button as caret by default, but to make it configurable via a slot, so people can render whatever button they want there if they want a different one. That's also how the clear button works (it's an "x" by default but you can override it with the clear_button slot).
Let me know

Hey hey!  Thanks for the response and sorry for the delay in getting back.  For now I've been working on a fork that I am trying to do in a way that I can hopefully contribute back, but I'm worried it will get a little hairy.

Yes, I'm definitely open to this. I think an open question would be how this button would work together with the clear button (see the "allow_clear" option here). However, I suppose this caret button will be shown only if nothing is selected, right? In which case it will never have to be displayed together with the clear button, so no problem there. Otherwise, we'll have to think of something.

In our design system, it actually shows both the caret and the clear button!  So then it becomes an issue of perhaps needing to provide too many options.  I could be over-thinking what this library should provide vs what the user should take care of on their own.
There are three more issues.  I can create dedicated issues if you would like to discuss further but I figure I would just mention here first:

First isn't a huge deal but I would like to be able to provide a slot for tags.  I would like to use the tag component from our design system directly instead of having to rejig the CSS to match live_select's markup.

I'm not sure how you would feel about this one but it would be nice if live_select could also act as a, uhhh, "dead" select.  I assume this was probably an explicit decision by you (and apologies if I have missed this in the docs) but we have several multi-selects with a finite number of options that would be much simpler to just pass options={@options}.  Saving a round-trip is a nice bonus.

We need keyboard navigation.

I'm than happy to work on all of this stuff.  I have to do it anyway with or without LiveSelect, but would much rather contribute back!
What do you think??

PS, to clarify I know there is options already but I mean an option not to trigger the events to the server on change.  Although again perhaps I'm overthinking this and what I'm looking for is possible on this point as is.  I've been a little overwhelmed the past week.

OMG, I see there are already slots for tags 🤦

In our design system, it actually shows both the caret and the clear button! So then it becomes an issue of perhaps needing to provide too many options. I could be over-thinking what this library should provide vs what the user should take care of on their own.

I'm fine with showing both caret and clear button, even if it means adding another option
To your issues:

First isn't a huge deal but I would like to be able to provide a slot for tags. I would like to use the tag component from our design system directly instead of having to rejig the CSS to match live_select's markup.

You found out that this is already a thing :)

We need keyboard navigation.

That is already implemented. You can navigate the options with the arrow keys and select with the enter key. Doesn't that work for you out of the box? If it doesn't, please open an issue

I'm not sure how you would feel about this one but it would be nice if live_select could also act as a, uhhh, "dead" select. I assume this was probably an explicit decision by you (and apologies if I have missed this in the docs) but we have several multi-selects with a finite number of options that would be much simpler to just pass options={@options}. Saving a round-trip is a nice bonus.

Wouldn't this "dead select" be just like a standard HTML select element or something in between? What would be the difference between a static HTML select and the dead select?

For now I've been working on a fork that I am trying to do in a way that I can hopefully contribute back, but I'm worried it will get a little hairy.

That interests me. When people work on a fork it means that something important is missing. Was it only the caret button or some other missing feature that made you decide to fork you own version?
Btw: I'd be very happy if you'd like to contribute to the project. This and next week are kind of crazy for me (I'm moving to a new place) so apologies if I won't always respond swiftly.

Max,
So sorry for my poor RTFM'ing abilities 😮💨  I've had a pretty bad couple of weeks and a bit overwhelmed and was in "just get this done however I can" mode.  So yes, keyboard navigation works great (I had broken it on my fork 🤦 ) and adding in the caret is simpler than I had made it.
I've simplified my fork and will add the caret in a compatible way and PR it when it's solid.
As for the "dead select," the reason would be to get the multi-select without having to make a whole different component.  Also, I think we're going to use the same style for regular selects (even if I don't think it's the best idea, we'll see).  In any event, it's not the worst to re-create or maybe there is a better way I am not thinking of.
Thanks for your detailed responses and apologies for not lack of attention to detail!

Andrew,
no worries at all! I'm also going through a couple of very intense weeks.

I've simplified my fork and will add the caret in a compatible way and PR it when it's solid.

That sounds great, looking forward to your PR 👍  If you have any questions or need help, don't hesitate to ask here.
Thanks

As for the "dead select," the reason would be to get the multi-select without having to make a whole different component. Also, I think we're going to use the same style for regular selects (even if I don't think it's the best idea, we'll see). In any event, it's not the worst to re-create or maybe there is a better way I am not thinking of.

The styling aspect makes sense, you could copy and paste an already styled live_select and set the "dead" flag whenever you need an ordinary HTML select with same styles. Doesn't sound hard to do and potentially useful. Will give it some thought as soon as I find some time

It's not just styling it's re-implementing the tags as well.  Again, not that this is a huge deal or anything, but it's helpful to have them using the same code.


invalid input syntax for type uuid

Hi, I have searched everywhere but did not meet. I got into trouble with uuid
auth()->user() / Auth::user()

The problem is as below:
SQLSTATE[22P02]: Invalid text representation: 7 ERROR: invalid input syntax for type uuid: "970" (SQL: select * from "users" where "id" = 970 limit 1)

where id should be string. In my model user like this.
protected $table = 'users';
protected $primaryKey = 'id';
public $incrementing = false;
protected $keyType = 'string'

and I've also tried to add
protected $casts = [
        'id' => 'string'
    ];

but still the same result. Please help.
Thank you

Laravel Version: 5.6.*
PHP Version: 7.2
Database Driver & Version: postgresql

Well, you have a session that states that you're user "970". Did you recently change from integers to uuid? Does this session cookie come from another application you're developing on the same domain (usually localhost)?

@sisve thank for response. yes i`m change from integer to uuid. session cookie not from other application. I search any same problem but I not found it working for me.

I'm using emadadly/laravel-uuid and got the same error. After expending some time restarting server through php artisan serve, after change many things on my project and noting that the error won't stopped, I deleted the session cache file inside storage/framework/sessions and then all back to work.

protected $primaryKey = 'id';
protected $keyType = 'string';
https://laravel.com/docs/9.x/eloquent#primary-keys

I had same problem. @dwikyls answer helped me.
I added these lines to my User model
protected $primaryKey = 'id';
protected $keyType = 'string';


OCPBUGS-19419: change trusted bundle volume mount for CPO

What this PR does / why we need it:
Fixes issue where using a custom ca-bundle  CM with a name other than user-ca-bundle would prevent the deployment of the CPO. Fixed this issue by changing the volume mount used by the deployment.
Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes # OCPBUGS-19419
Checklist

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

/retest-required

/lgtm

/retest-required

/cherry-pick release-4.14


fix(debugger-app): fixes #219

use fileURLToPath function to get path of URL instead of .pathname (added in v10.12.0)
fixes #219

hello @meypod are you able to rebase both your PR's to main branch ?


Speedup data uploading for key-value

For .csv files with size ~500mb is necessary ~30-60 minutes to upload it to bee in standalone mode.
It would be great to optimise uploading process and decrease this time.

We can use /chunk/stream to upload via websocket

That would be great, so we could stream into.


Multiple yield parsing

I am running a query with that has multiple yields in it. I am then using the fromFlux() function to parse the data.
The following is the csv response:

#group,false,false,true,true,false
#datatype,string,long,dateTime:RFC3339,dateTime:RFC3339,double
#default,writes_kb,,,,
,result,table,_start,_stop,writes_kb
,,0,2019-05-31T17:54:44Z,2019-05-31T21:54:44.685122992Z,16512.4

#group,false,false,true,true,false
#datatype,string,long,dateTime:RFC3339,dateTime:RFC3339,double
#default,,,,,
,result,table,_start,_stop,reads_kb
,,0,2019-05-31T17:54:44Z,2019-05-31T21:54:44.685122992Z,11111.4

#group,false,false,true,true,false
#datatype,string,long,dateTime:RFC3339,dateTime:RFC3339,double
#default,writes_kb,,,,
,result,table,_start,_stop,execution_sec
,,0,2019-05-31T17:54:44Z,2019-05-31T21:54:44.685122992Z,22222.4

#group,false,false,true,true,false
#datatype,string,long,dateTime:RFC3339,dateTime:RFC3339,long
#default,api_count,,,,
,result,table,_start,_stop,api_count
,,0,2019-05-31T17:54:44Z,2019-05-31T21:54:44.685122992Z,1125

The table gets parsed as

Because each of my results are a single stat, I would expect the data for each of those columns to be an array of length 1, rather than an array of length 4.

This is intentional, but maybe there's something more sensible that should happen instead. The fromFlux function concats individual Flux tables into one large sparse table (see comment here, this operation is known as a spread/recast/pivot in other libraries).
At a high level, what are you trying to achieve with the vis library? I'm up for a quick call about this sometime today.

Talked with @ischolten about this. The output of the Flux parsing is a bit strange for her use case, but she has a reasonable workaround.
Going to close this for now.


Make list of keycodes

I'm configuring my keyplus mini firmware, but I don't know what the keycodes are. There should be a list of them.

Yeah, definitely need to work on the documentation, for the mean time you can see a list of key codes here: https://github.com/ahtn/keyplus/blob/master/host-software/keyplus/keycodes/mapped_keycodes.py
If you want to combine a keycode with a modify, you can use a mod-keycode, so where mod is one of

c -> control
s -> shift
a -> alt keycode
g -> gui / win key

So to make a key that press ctrl+v, use c-v.  To make a key that press ctrl+shift+alt+up use csa-up.


Android/Windows: list of crashing tests

cocos2d-x version:
devices test on: Pocophone F1  / Windows10

ANDROID only:
Tests chrashing "on start"
6:Chipmunk
ANDROID & WINDOWS:
Test chrashing after press "back" (some test be done)
12:yasio
WINDOWS only:

This is also crashing on Windows.
Test chrashing after press "back" (some test be done)
12:yasio

check does the latest master works

check does the latest master works

Chipmunk and yasio works now (Windows and Android).
Thanks.

fix by above referenced commits


[DEVOPS-528]  installer | OS X:  convert to the Buildkite bucket

Switch to Buildkite-provided Cardano builds.

Note that this can't be merged until buildkite lands in cardano-sl master.

@domenkozar, CI has passed..


Advanced Search - overdue lists on hold requests

Describe the bug in current situation
Advanced Search - search overdue requests and it lists "On Hold" requests
Link bug to the User Story
#1213
Impact of this bug
Describe the impact, i.e. what the impact is, and number of users impacted.
All users
Chance of Occurring (high/medium/low/very low)
High
Pre Conditions: which Env, any pre-requesites or assumptions to execute steps?
all env
Steps to Reproduce
Steps to reproduce the behavior:
Go to Advanced Search
Select "Overdue" under "Request Status"
Click Apply search
Actual/ observed behaviour/ results
Result contains "On Hold" requests
Expected behaviour
The list should not includes "On Hold" requests
Screenshots/ Visual Reference/ Source
Search criteria

Actual Result

Expected behavior now works as it should - Thank for fixing! @richard-aot


prevent activity stream duplicates

General Checkups

[x] Have you checked that there aren't other open pull requests for the same issue/update/change?
[x] If your code includes new features and not just bug fixes/copy editing: Did you include new tests?

Description

The activity stream would show duplicate entries for re-joining a project a member was already a member of but where the external project would require new oauth credentials and similarly when data was being made public a 'second time'. These could look weird on the frontend.
This PR would fix these by not adding a second item to the stream if people have already done the action once.
Related Issue

Closes #801
Example

I've tested the code on my local dev DB, but only for the joined-project logic, not the public-shared, as I don't have the public sharing thing set up right now. But that should be identical.

That's cool by me, actually the linter didn't complain about overindent, so I did that now :)

Thanks!


Adding new custom commands is hard

Seriously, who thought that adding the command script path in ProjectSettings was a good and easy idea? Me? I should knew it.

Haha I'm about to add a button and a drag&drop function to add them


How can I focus on Input?

I found the docs about is very simple, Is it out of maintenance? How can I use Input?

https://vue-termui.dev/guide/components/tui-input.html

if in bowser, I can need focus on Input, and then enter something. Now in Terminal, what should I do?

Try press TAB to toggle it.


Protoc Codegen Output

Hey all so I originally used protobuf-codegen rust plugin with protoc to generate the output for a 3D file format that you can find here : https://github.com/HiceS/mirabuf
I was originally running: protoc --rust_out ./libs/rust *.proto and it generated everything correctly.
Now I get the following error while trying to generate with that command
The Rust codegen is highly experimental. Future versions will break existing code. Use at your own risk. You can opt-in by passing 'experimental-codegen=enabled' to '--rust_out'.
doing this gives me a error to specify the kernel as either cpp or upb,
So now I use the following command with the flag enabled
protoc --rust_out=experimental-codegen=enabled,kernel=cpp:./libs/rust/src/ *.proto
The problem is that now the code output is mostly C code with a little rust to do loading which does not port to WASM where I am currently using it effectively.
Here is an example of the original generated file that is still used :
https://gist.github.com/HiceS/dc57fc3bcf2a30ec52abec44450cbc39
Is there anything I am missing or doing incorrectly to get the current file generation ?
Also the built-in build.rs strategy does not work at all for me because it fails to discover all of the files in that directory for input. Ideally I would like to auto-publish a cargo package from my mirabuf repo as a github action.

I have updated my protoc version to libprotoc 23.3

Did this fix your issue ? @HiceS
I'm still trying to make a basic example from a build.rs and take all the proto files in one dir and make the rust equivalent in another, but I've seen like half a dozen repo tonight pretending to do this and never understood how these massive projects were supposed to be libraries to use

I have used some packages in the past but I ended up pre-generating them and publishing them to a crate directly to use. I believe I ended up using protobuf-rs however.

protoc --rust_out without plugin is default Google protobuf codegen, which is meant to be used with Google's protobuf.
It is unrelated to rust-protobuf.

Correct me if I am wrong, follow the documentation there, it will lead to this result. Even if I specify the --plugin param to use rust-protobuf get same result.


Raging Blow

Request to track Warrior's Chest Rune: Raging Blow

[ ] Does it proc from a buff? No, procs from a usable action, expected to be spell ID 402911
[x] Where does it come from (baseline, talent, etc.)? Chest Rune
[x] Should it display a Spell Alert? TBD probably not, to be discussed with warriors

[ ] Where? N/A
[ ] Which texture? N/A
[ ] Which size? N/A
[ ] Change color? N/A
[ ] Spell Alert enabled by default for all shamans? N/A

[x] Should it glow buttons? Yes, because this ability can only be used under certain conditions

[x] Which buttons should it glow? Raging Blow (spell ID to be confirmed)
[x] Which glowing buttons should glow by default? Raging Blow

Implemented in 1.1.0-beta with the following assumptions (confirmation needed by warriors, please!)

Glowing Button with spell ID 402911 (TBC)
Spell Alert displayed when the action is usable
Spell Alert uses texture raging_blow displayed "Left + Right"

Closing issue, because the ability has been tested successfully for months.