Cannot read property css of undefined in the first screen, Select Language

Brief Description: Clicking next on the very first onboarding screen doesn't work because this.accWin is undefined.
Operating System (OS and version): macOS 10.12.5
OpenBazaar version (shown on About OpenBazaar page in menu): 1.1.11
Hardware: Macbook Pro 2016
Reproducible (Always / Almost Always / Sometimes / Rarely / Couldn't Reproduce): Always
Steps to reproduce:

Install app
Launch, See "Select Your Language" with English preselected
Click "Next >"

Observed Behavior:
Nothing happens. Opening developer tools shows this error every time "Next >" is pressed:

Expected Behavior:
I move to the next screen of onboarding
Originally reported here by @lekevicius
https://github.com/OpenBazaar/openbazaar-desktop/issues/579

This appears to be caused by line 50 of currencyListVw.js, which is calling "https://api.bitcoinaverage.com/ticker/global/all". That call takes a long time to resolve, and appears to be failing, which prevents the accordion from initializing.
If the user waits for the call to fail, they will be able to proceed, but the only currency option will be Bitcoin.
The url to retrieve a list of currency should be updated to one that works, or a conservative default list should be used.
In addition, a spinner or other indicator should be added so users know they are waiting on the response for the currency, and a message should be shown if it fails.

This has been fixed by updating the API.


Potential Acceleration Solution for AMD GPU / Integrated Graphics

Potential Acceleration Backend for new AMD GPU / Integrated Graphics, which may be helpful.
DirectML#TensorFlow-with-DirectML-Preview
repo: tensorflow-directml.
It uses Microsoft's DirectX 12, rather than NVIDIA CUDA, to accelerate deep neural network's computation.
(Note that it is still in the preview stage.)
Requirements:
One of the following supported GPUs:
AMD Radeon R5/R7/R9 2xx series or newer
Intel HD Graphics 5xx or newer
NVIDIA GeForce GTX 9xx series GPU or newer

Users who own the specific GPU and are interested in this, could test it with Style2Paints V3.
(sorry that I can't test the method, due to lack of specific hardware.)

Looks good and I will try it later.

Unfortunately Win 7 does not support DirectX 12 but about many my artist friends are still using win 7. And some of them are using something like "win7 + GTX 1050" which is somewhat weird but is the fact.

It's hard to keep support to both api? not sure, if you that will like double your work.

I noticed that when migrating to tensorflow-directml, the device placement in config.py may need change to /DML:0.
(Issue: https://github.com/microsoft/tensorflow-directml/issues/225,  gpu-faq)
I'm not familiar with the tensorflow-directml, so I'm not sure how many other changes are needed.

PS: DirectML's current shaders are mostly optimized for inference stage (roadmap), standard or example performance benchmarks that include training stage may be slow. So benchmarks including training process may not be accurate. Style2Paints doesn't need training stage.
I guess on NVIDIA cards, directML may be slower than CUDA. But on AMD GPU / Integrated Graphics, directML  may bring performance gain.

A good news is that:
migrating to tensorflow-directml seems not difficult, the main change in code is only the following:
(Currently I can't test it, but I infer from other's issue.)
from:
with tf.device('/GPU:0'):
to:
with tf.device('/DML:0'):
Ref: https://github.com/microsoft/tensorflow-directml/issues/225#issuecomment-840211943

Sound


Markdown Formatting not Rendering Properly in mdxeditor

The mdxeditor does not seem to render Markdown formatting correctly in a Create React App project. When passing Markdown-formatted text into the editor, it appears as plain text instead of being properly formatted with headings and lists.
Create React App version: 5.0.1
React version: 18.2.0
mdxeditor version: 1.9.2
import React from "react";
import {
  MDXEditorMethods,
  MDXEditor,
  headingsPlugin,
  UndoRedo,
  BoldItalicUnderlineToggles,
  toolbarPlugin,
  markdownShortcutPlugin,
  listsPlugin,
  linkPlugin,
  quotePlugin,
  frontmatterPlugin,
  diffSourcePlugin,
  tablePlugin,
} from "@mdxeditor/editor";
import<EMAIL_ADDRESS>
const frontmatterMarkdown = `# hello
- a
- b

> hello world
`;

function DocumentEditor() {
  const ref = React.useRef<MDXEditorMethods>(null);
  return (
    <div className="w-full h-[80vh] max-h-80vh mt-2">
      <MDXEditor
        markdown={frontmatterMarkdown}
        plugins={[
          frontmatterPlugin(),
          listsPlugin(),
          linkPlugin(),
          tablePlugin(),
          quotePlugin(),
          headingsPlugin(),
          toolbarPlugin({
            toolbarContents: () => (
              <>
                <UndoRedo />
                <BoldItalicUnderlineToggles />
              </>
            ),
          }),
          markdownShortcutPlugin(),
          diffSourcePlugin({
            diffMarkdown: "An older version",
            viewMode: "rich-text",
          }),
        ]}
        contentEditableClassName="prose"
      />
    </div>
  );
}

export default DocumentEditor;

Most likely, you have tailwind reset which wipes out the formatting. https://github.com/mdx-editor/editor/issues/29.


Feat/6 fastify plugin

Issue: #6
Added a Fastify plugin to complement the existing Express middleware and NestJS guard.
The plugin:

Checks if a request is allowed based on the user's plan limits
Returns 402 (Payment Required) if the request exceeds limits
Tracks usage by incrementing counters after successful requests

Usage:
import { priciPlugin } from '@prici/sdk/fastify';

await fastify.register(priciPlugin, {
  sdk: priciSdk,
  fieldId: 'api-calls'
});

Update the pnpm lock to pass the tests.

@davidmeirlevy I wrote unit tests but when I run them (or any other tests) it fails with some jest error and module loader.

There's no jest in this project.
It's node native test runner.

There's no jest in this project. It's node native test runner.

OK! That makes sense! because I ran it using the jest extension 😅
I ran it from the package json script and it worked.

pnpm build still doesn't work and I don't understand why


TypeScript - component is not in TablePaginationProps

component is missing in TablePaginationProps which is causing TS error when trying to use <TablePagination> with component='div'

It's getting omitted here
https://github.com/mui-org/material-ui/blob/9291574278db8d83feb5d7aa0cce6b5d58dafba1/packages/material-ui/src/TablePagination/TablePagination.d.ts#L47

@merceyz That is not the props that are exported.
@murbanowicz Please follow the issue template (specifically versions, code and tsconfig.

Tech
Version

Material-UI
4.0.2

React
16.8.6

Browser

TypeScript
3.5.1

etc.

removing | 'component' from the line @merceyz referenced seemed to fix it for me

Just ran into the very same issue. component is not a valid prop for the TablePagination component, even though the docs say so.
I am willing to submit a pull request. @eps1lon Please let me know, which file is the correct one, if packages/material-ui/src/TablePagination/TablePagination.d.ts is not.

Tech
Version

Material-UI
v4.2.0 (latest)

React
16.8.6 (latest)

TypeScript
3.5.3 (latest)


Front End Roles

adjusting front end developer skills
adding senior front end developer role
adding browser dev tools competency
adding webpack competency

Split out engineering base skills, starting with the following:
<skills>
Git
Github
Kanban
Regex
Research
</skills>


Getting the schema of the "datadog" plugin does not produce a JSON response

Summary
Attempting to get the schema of the "datadog" plugin when calling the "/plugins/schema/datadog" endpoint on the admin API directly returns a 200 OK response but without a JSON body:
$ curl -v http://localhost:8001/plugins/schema/datadog
*   Trying <IP_ADDRESS>...
* TCP_NODELAY set
* Connected to localhost (<IP_ADDRESS>) port 8001 (#0)
> GET /plugins/schema/datadog HTTP/1.1
> Host: localhost:8001
> User-Agent: curl/7.54.0
> Accept: */*
>
< HTTP/1.1 200 OK
< Date: Mon, 05 Nov 2018 01:19:07 GMT
< Content-Type: application/json
< Connection: keep-alive
< Access-Control-Allow-Origin: *
< Server: kong/1.0.0rc2
< Content-Length: 0
<
* Connection #0 to host localhost left intact

The following message is produced within the Kong error logs:
2018/11/05 01:19:07 [debug] 4887#0: *32 [lua] init.lua:307: No API endpoints loaded for plugin: statsd
2018/11/05 01:19:07 [debug] 4887#0: *32 [lua] init.lua:299: Loading API endpoints for plugin: prometheus
2018/11/05 01:19:07 [debug] 4887#0: *32 [lua] init.lua:307: No API endpoints loaded for plugin: request-termination
2018/11/05 01:19:07 [error] 4887#0: *32 [lua] responses.lua:160: [admin] could not encode value: Cannot serialise number: must not be NaN or Infinity, client: <IP_ADDRESS>, server: kong_admin, request: "GET /plugins/schema/datadog HTTP/1.1", host: "localhost:8101"
2018/11/05 01:19:07 [info] 4887#0: *32 client <IP_ADDRESS> closed keepalive connection

This happens on a vanilla instance of Kong 1.0.0rc2, running with PostgreSQL on Linux with only the bundled plugins preloaded.
Steps To Reproduce

Install Kong Community Edition ver. 1.0.0rc2 from the CentOS 6 RPM
Set plugins = bundled in Kong configuration
Initialise DB and start Kong
Run curl http://localhost:8001/plugins/schema/datadog

Additional Details & Logs

Kong version = 1.0.0rc2
Kong debug-level startup logs = kong-start.log attached
Kong error logs = error.log attached
Kong configuration = config.txt attached
Operating system = Amazon Linux AMI release 2017.03

Any idea on how to manually solve this ?
Is this linked to some value stored into postsgres ?


fix(tooltip): show tooltip on both label and control

FX-1874
Description
The tooltip for the radio and checkbox with the label was positioned incorrectly and was not visible if we hover over the label. It was always centered relatively on radio or checkbox. Now it is either in the center of the button or in the center of the button and label.
The problems that I solved here:

Pass only one ref to the child component. In case we have label pass ref to the label, otherwise, pass it to the button(checkbox or radio)
Pass listeners (onMouseLeave, onMouseOver) from Tooltip to the label
Created two examples in Radio and Checkbox components instead of Tooltip, because changes were done in these components

How to test

Go to Radio and Checkbox story
Scroll down to the With tooltip example
Tooltip should be centered

Screenshots

Review

[ ] Read CONTRIBUTING.md and Component API principles
[ ] Annotate all props in component with documentation
[ ] Create examples for component
[ ] Ensure that deployed demo has expected results and good examples
[ ] Ensure that tests pass by running yarn test
[ ] Ensure that visuals tests pass by running yarn test:visual. If not - check the documentation how to fix visual tests
[ ] Ensure the changed/created components have not caused accessibility issues. How to use accessibility plugin in storybook.

PR commands

List of available commands:

@toptal-bot run all - Run whole pipeline
@toptal-bot run build - Check build
@toptal-bot run visual - Run visual tests
@toptal-bot run deploy:documentation - Deploy documentation
@toptal-bot run package:alpha-release - Release alpha version

I've noticed, that in the disabled state a tooltip still appears.

I've noticed, that in the disabled state a tooltip still appears.

I think it is expected behavior because we can use it when we want to tell the user why it is disabled. Whether the tooltip should be displayed is up to the consumer of the component

I've noticed, that in the disabled state a tooltip still appears.

I think it is expected behavior because we can use it when we want to tell the user why it is disabled. Whether the tooltip should be displayed is up to the consumer of the component

maybe, but it's not shown in the current production version.

maybe, but it's not shown in the current production version.

Do you want me to add two more stories with a disabled checkbox and radio with a tooltip? Tooltip is just a wrapper around any component. Component wrapped in the Tooltip can have 50 states (e.g. disabled, active, different variants etc.). I don't think that we need to show a separate story for every state + tooltip

@MrBra1nwash I think @dmaklygin means that the disabled checkbox should not show a tooltip just like it does not show the tooltip in master, as there is a risk that it might break things if somebody relies on this (that disabled checkboxes do not show tooltips).

@MrBra1nwash I think @dmaklygin means that the disabled checkbox should not show a tooltip just like it does not show the tooltip in master, as there is a risk that it might break things if somebody relies on this (that disabled checkboxes do not show tooltips).
Thank you for the clarification :) But it is actually a bug in Picasso. Tooltip doesn't work with Checkbox or Radio. If someone relies on the bug we don't need to adjust to it. If Picasso owners consider it as a breaking change I can make this update major

https://user-images.githubusercontent.com/16545305/122569344-52814a80-d053-11eb-8e21-caeb031a5cc4.mov

@MrBra1nwash I think @dmaklygin means that the disabled checkbox should not show a tooltip just like it does not show the tooltip in master, as there is a risk that it might break things if somebody relies on this (that disabled checkboxes do not show tooltips).

Thank you for the clarification :) But it is actually a bug in Picasso. Tooltip doesn't work with Checkbox or Radio. In my PR I fixed this bug. If someone relies on the bug we don't need to adjust to it. If Picasso owners consider it as a breaking change I can make this update major
Screen.Recording.2021-06-18.at.16.34.17.mov

This change would not require people to fix somehow the component, tests also most likely would not fail. So I would release this as a non-breaking change. People will just receive a new functionality, a new feature. So Minor update looks valid to me 👍

This change would not require people to fix somehow the component, tests also most likely would not fail. So I would release this as a non-breaking change. People will just receive a new functionality, a new feature. So Minor update looks valid to me 👍

Thanks. Changed from fix to feat


⚠ Bofrost.be has degraded performance

In b1b5919, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1496 ms

Resolved: Bofrost.be performance has improved in 96d7d66.


Add conditions to keep the hover widget when there is active selection

Tries to fix https://github.com/microsoft/vscode/issues/81904.
Open to discussion!

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: neslinesli93 sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Sorry about the delay in someone looking at this, but this doesn't seem to work anymore. Additionally, if the user moves the mouse at all outside of the hover it would hide and we also have a workbench-level hover now which complicates this further.


feat(es7): Enable es7.objectRestSpread

This will enable us writing this like:
let { x, y, ...z } = { x: 1, y: 2, a: 3, b: 4 };

or
var defaults = { first: 'John', last: 'Doe', age: 42 };
var trainer  = { last: 'Smith', age: 35 };
trainer      = { ...defaults, ...trainer, age: 36 }
// => { first: 'John', last: 'Smith', age: 36 }

More info: https://github.com/sebmarkbage/ecmascript-rest-spread
Babeljs should have this enabled by default, but it seems than for it
to work when using the babel plugin for webpack, we need to explicitly
enable it.

About the issue: https://github.com/babel/babel-loader/issues/117

I blindly copy-pasted the solution suggested in an issue in babel-loader at first. Then I tried with stage: 2 and this failed. Now I'm having segfaults on npm run dev :/

segfault is really weird

I deleted my node_modules and re-npm install-ed it and it is working fine. I think webpack might not like live-editing of .babelrc.
I've re-pushed with stage:2

I deleted my node_modules and re-npm install-ed it and it is working fine. I think webpack might not like live-editing of .babelrc.

If you just upgrade node then you need to rm -rf node_modules indeed. Because some of the modules have native code compilation. Thus it can fail when upgrading major node.

Oh ok, makes sense. Thanks for the trick.


only run windows e2e on main

This test is flaky and fails often. We should fix it, but in the meantime, it slows us down on every push and PR waiting for it to finish before we can rerun other actions.
Test plan
CI

@dominiccooney feel free to revert if you don't think this is a good idea.

Whoops, this change was incorrect. Fixing.


[SLS-2195] Undo server side stats computation (remove computeStatsKey)

What does this PR do?
Due to issues with client side stats computations, we switched to server-side stats computations historically. Since those issues are resolved, we can switch back to client-side stats computations. This is already done in the extension, but using a tag blacklist. We should remove the code which adds _dd.compute_stats in the first place.

Motivation

https://datadoghq.atlassian.net/browse/SLS-2195
Additional Notes

This change is essentially a no-op because the _dd.compute_stats tag is already being filtered out by the tags blacklist.
Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

No change in behaviour.
Reviewer's Checklist

[x] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[x] A release note has been added or the changelog/no-changelog label has been applied.
[x] Changed code has automated tests for its functionality.
[x] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[x] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the config template has been updated.

Going to make the changes in another PR.


Rename

... to something with tesseract

I guess tesstrain is the obvious one unless you want to go Schläfli or similar (cube was already used).

We should do this asap. I already read formulations like

I trained with ocrd and...

Do you want to keep "ocrd" in the name (e. g. ocrd_tesstrain)? If not, moving the code to https://github.com/tesseract-ocr might also be an option.

Do you want to keep "ocrd" in the name (e. g. ocrd_tesstrain)?

I do not. As @wrznr says, it is misleading here.

If not, moving the code to https://github.com/tesseract-ocr might also be an option.

I'd favor that.

@zdenop and @Shreeshrii suggest a new repository there (see discussion at the tesseract-dev forum).
I suggest to name it https://github.com/tesseract-ocr/tesstrain.
If that is fine for everybody, @zdenop could create it, and we could transfer the content from ocrd-train.

An alternate solution would be transferring the ownership. That has the advantage that everything is transferred (wiki, issues, stars, ...), but needs (temporarily) modified rights on GitHub.

I guess transferring the repository is much easier than copying the contents. Is it sufficient if add @stweil as an owner to this repo? Or who would be the most logic choice?

Maybe any owner of the repository can initiate the transfer to https://github.com/tesseract-ocr. Then @zdenop should get an e-mail giving the option to accept or reject the transfer. If the new owner doesn't accept the transfer within one day, it won't complete (see https://help.github.com/en/articles/transferring-a-repository#about-repository-transfers).
@wrznr or @kba, you can just try that. After having accepted the transfer, @zdenop would still have to rename the repository from ocrd-train to tesstrain.

You need permission to create new repositories in the organisation you're transferring to. If I try to transfer to tesseract-ocr:

You don’t have the permission to create repositories on tesseract-ocr

I'll give you owner rights and you can try yourself @stweil

I see. For transfers to an organization different rules apply: https://help.github.com/en/articles/transferring-a-repository#repository-transfers-and-organizations.
As I am only a member at tesseract-ocr and members are currently not allowed to create new repositories there, I get the same error message when I try a transfer. We need help from @zdenop who must either give me the right to create the new repository or who must be added to the list of owners of the current ocrd-train. @zdenop, which variant is easier for you?

@stweil : try now: I changed your role in tesseract organization (for this task)

Thank you, @zdenop and all others who were involved in the discussion and process.
The repository is moved and renamed now, so this issue can be closed. We can now consider updating the README, maybe changing the directory structure and moving the training scripts from https://github.com/tesseract-ocr/tesseract/tree/master/src/training to tesstrain.

There are many references to ocrd-train in forum posts etc. Is it possible to have a dummy repo which redirects to the new repo?
Or, does github automatically redirect pages when a repo has been renamed/moved?

It will automatically redirect.

Great. Thanks!


[Removal]: Cuddly Ebony Huskie

Hotspot Name
Cuddly Ebony Huskie
Hotspot b58 Address
1128nDozMUUgzcWmJovGYW235HwMa3UPgW9fjRccLVGXX6uDC8Q6
Discord Handle
BogdanG#1799
Hotspot Manufacturer
SenseCap
Removal Reason
This hotspot was bulk added to the denylist along withe the whole town again.
Modifications
No
Extra forwarders
No
Extra antennas
No
Additional Information
Hi again im the owner of Blunt Ivory Ferret,Cold Tan Beetle,Cuddly Ebony Huskie and Fast Jetblack Finch all they are regular.
Please remove them from the denylist.

We do not have sufficient evidence to remove these hotspots from the denylist. This is an automated comment due to the volume of addition and removal requests. A future tool is in the works to provide more insight into the analysis approach made by the Helium team and community members that maintain this list.

We have taken into account this removal request in the next iteration of the denylist. It may take some time before it's processed. This is an automated comment due to the volume of addition and removal requests. A future tool is in the works to provide more insight into the analysis approach made by the Helium team and community members that maintain this list.


Can't compile a dependency without a contract/ folder

Environment information

OS: linux
Python Version: 3.9.9
ape and plugin versions:

$ ape --version
# ...copy and paste result of above command here...

$ ape plugins list
# ...copy and paste result of above command here...

Contents of your ape-config.yaml (NOTE: do not post anything private like RPC urls or secrets!):

$ cat ape-config.yaml
dependencies:
    - name: some-dep
      ...

What went wrong?
$ ape compile
WARNING: No source files found in '~/path/to/project/contracts'.

How can it be fixed?
Fill this in if you have ideas on how the bug could be fixed.

I am not able to reproduce.
My demo project does not specify contracts_folder and still compiles.
Is there something else going on?

I am not able to reproduce. I require more information.
My demo project does not specify contracts_folder and still compiles.
Is there something else going on?
(my config: https://github.com/unparalleled-js/ape-demo-project/blob/main/ape-config.yaml#L26)

This but actually delete the contracts/ folder and then do ape compile

This but actually delete the contracts/ folder and then do ape compile

Ahh, I understand - the project has no contracts but still uses dependencies.
On it!


lint(scripts/lint-style): Add linting for lower-case clashes

Introduce a global check on git-managed filenames in the whole repository, making sure that the filenames are distinct also up to upper/lower casing.
Fixes an issue that came up when two file names that only differed by their casing were imported in a case-insensitive operating system.
As a check, I pushed branch#adomani/testUpperLowerLinter from this PR containing CODe_OF_CONDUCT.md alongside CODE_OF_CONDUCT.md.  The linter failed on that branch.

The linter output looks a bit strange in the test branch on github actions, the input and output lines seem to get interspersed.
Personally I don't mind that so much I think the output is sufficient to get the point across.

I noticed that and I wonder if it is due to the options set at the beginning of the file.  On my computer, the output is what I expect it to be.
I can remove all printouts other that the clashing filenames, if it is preferable.


Wrong entry selected in Component Browser if Enter is pressed too fast

See the following video:
https://github.com/enso-org/enso/assets/1436948/20560589-28a5-47a8-b1f2-79560eb5f81c
On the first try I typed first and pressed Enter so fast that the keystrokes of first did not even get a chance to render... So it inserted the default node: to_table - totally ignoring what I typed.
On second try I was slow and the CB actually did manage to select the first and then it inserted correctly the node first. Yay.
On third try I was just right - you can see that my keystrokes did make first appear in the new-node-creation-field - so they were registered. But the searched did not yet switch to the correct entry before the Enter event was processed. And so even though the Node displayed first, after clicking Enter, to_table was inserted again.
It seems that the "Enter" action is processed too soon. Some sort of event queueing should happen to ensure that all necessary processing of keystrokes that have been inputted is finished, before processing of Enter, dependant on these, starts.
Otherwise, maybe the "Enter" keystroke should simply not register if other events are being processed (giving the user a chance to wait until all 'settles', the CB displays the correct entry etc. and to try pressing Enter again afterwards).
Regardless of the solution, I think the current behaviour is problematic. As a fast-typing user I'm punished - I have to explicitly wait until the CB loads and switches to the right option (which takes 2s+ after warmup and even worse on first try - that is ages for text editing usecases where one can do 80 words per minute - i.e. typing one full word (= method name) usually takes around 1s).

I thought this was meant to be fixed by #6812 but I'm running a build containing this commit and the behaviour is as shown on the video.

This should be actually fixed by https://github.com/enso-org/enso/pull/6875 which is not merged yet, so probably you haven't had this fix.
It's a duplicate of #6733 or #6908 or both.


Resolve webview UI toolkit bundling and loading

Looks like webview UI toolkit added in #8 is not being properly bundled and loaded in this extension for the table view toolbar UI controls setup:

It does work in tabular data viewer debug (see reload, and goto last and first table row buttons in table view toolbar):

that change fixes it for now:

patched and updated published version in this release: https://github.com/RandomFractals/tabular-data-viewer/tree/v1.2.0


fix accordion and plus/minus

Fixes #2558  .
Changes proposed in this PR:

small changes to JS to fix accordion and plus/minus signs

Looks like ESLint's complaining about the number of spaces used (althought as a separate issue, ESLint the action isn't failing, just the one that gates asset-compilation)
to make troubleshooting the linter issues locally easier, you can run
yarn run eslint './app/javascript/**/*.js' or rails webpacker:compile

as @xsrust noted, looks like maybe the linter does not like the spacing/indentation. Feel free to merge yourself once that's been addressed


About embedding selection of reward model

Thank you for the great work! I just have a small question regarding the training and inference stage of the reward model. In the encode_pair function in train/src/ImageReward.py you are using last_hidden_state[:, -1, :] of the embedding, but in encode_data function and in the inference stage in ImageReward/ImageReward.py you are using last_hidden_state[:,0,:]. Why are they different? What is the intention of using the first or the last dimension? Thanks a lot!

Thanks for pointing this out, there was a mis-edit when we were organizing our training code and it has now been corrected. They should all be last_hidden_state[:,0,:].


Adding lemmas to dependency parses

Dependency parses can now contain lemmas in the last column, if NLTK as well as the WordNet corpus for NLTK are both installed. This is done by passing with_lemmas=True to the dep_parse_sentence() method of a dependency parser object. If either NLTK or the WordNet corpus is not installed, then passing with_lemmas=True will print a warning and produce the regular dependency tree without lemmas.
There are also new unit tests for dependency parsers testing the lemma functionality.
This PR also contains some other changes pertaining to making the CircleCI builds more efficient and working around the 4GB RAM limit they have on their containers.

@aoifecahill can you please test this out since you are going to be one of the main consumers for this? :)

This works mostly as I would expect it, except for the sentence initial words. I think this needs to be lowercased before being sent to the lemmatizer?

Good call! Somehow I was under the impression that morphy (the wordnet lemmatizer) lowercases internally but it doesn't look like it. Will fix.

@aoifecahill, it's fixed.

Looks good to me, thanks!


Error: The model gpt-4-preview does not exist

When labeling: ERROR: Error code: 404 - {'error': {'message': 'The model gpt-4-preview does not exist', 'type': 'invalid_request_error', 'param': None, 'code': 'model_not_found'}}
The model name was deprecated a while ago, now we have either gpt-4 or gpt-4-turbo-preview.
https://platform.openai.com/docs/models/gpt-4-and-gpt-4-turbo
As a quick fix, I locally edited latenscope/models/chat_models.json where the package was installed.

this was fixed in https://github.com/enjalot/latent-scope/commit/66ca7ee08659b18f7c7cf3eb1a80f325ed830662
it will be included in a 0.1.1 release soon!


Expose super properties as currentSuperProperties

I had my own category for ARAnalytics to extend it for my project but was limited by not having access to superProperties (since sharedInstance is not exposed either). For now, I'm using this fork in my Podfile, but thought this could go in the main project.

        1 Error

  </th>
 </tr>

:no_entry_sign:
Please include a CHANGELOG entry.
You can find it at CHANGELOG.md.

  Generated by :no_entry_sign: danger

I'm 👍 with this

Want to try wrap this up and get it in?

It looks like there was a problem with running the danger ci all those months ago. It timed out or something. I'm not sure how to get it to rerun the check.


Support creating OpenShift VCS labels

Feature Request
Is your feature request related to a problem?
There's a standard set of labels OpenContainers labels/annotations which allow you to specify information such as where the source repository is and what revision is used.
By default, microservices created by the Appsody project set the following labels:
    image.opencontainers.org/created: "2020-03-17T11:48:58Z"
    image.opencontainers.org/documentation: https://github.com/seabaylea/backend
    image.opencontainers.org/revision: 8be7def88e73b0e311b8517bd0a960bc03f5282d-modified
    image.opencontainers.org/source: https://github.com/seabaylea/backend/tree/master
    image.opencontainers.org/url: https://github.com/seabaylea/backend

However, OpenShift uses its own labels to store version control information.
Describe the solution you'd like
Where the application provides open container label, but not the corresponding OpenShift annotations, the Runtime Component Operator could create the OpenShift equivalents (when deploying to OpenShift).
The list of OpenShift labels and annotations are here:
https://github.com/gorkem/app-labels/blob/master/labels-annotation-for-openshift.adoc
The relevant two in this scenario are:
app.openshift.io/vcs-uri
app.openshift.io/vcs-ref

Resolved by PR https://github.com/application-stacks/runtime-component-operator/pull/54


Desktop Mode Save Action Behaviour

Hi. I am really enjoying using Piskel, and am using the Desktop / Node-Webkit version.
It seems that you are detecting when you are running in Node-Webkit and have a different save behaviour (select file path and name), which is great. I was thinking that it would be nice to extend this to behave more like a full native app when running on the Desktop.
I was thinking that what is needed is a "Save As" action, that would remember the chosen filename, and would allow a faster re-save to that same file. I see that it is in your roadmap, but I'd really like to see a ctrl-s save keypress. That could save either into the browser in the web version, or in Desktop mode, into the target file path.
I'm always compulsively hitting ctrl-s in every app I use, and I miss it in piskel :)
I'm quite familiar with node.js and Node-Webkit, and if I can find the time I'd like to contribute in this area if I can. Have you had any thoughts on similar lines? It's not the most glamorous feature, but it would make the offline workflow smoother.

Hi !
I would love to improve the 'save' flow, so totally in favor of working on this (I also miss the ctrl+S !)
The 'Save as File' feature is relying on a link with a download attribute. In node-webkit, this triggers the 'Save As' popup automatically. There is no specific implementation :) I assume it's the default behavior of node-webkit for download links.
Looking at the documentation, node-webkit can use all the Node.js APIs, including the filesystem API (https://nodejs.org/api/fs.html). So technically, this looks feasible.
If we can do a good file-based save system, we can simplify the UI a lot for the node webkit version (remove the name/description form, remove the save offline section ...).

If we can hold onto the full save file name and path, then we can easily bind ctrl-s to a re-save action. (Rather than opening the dialog again and timestamping the file name, as it does for the web version.)
I should have time this weekend to try it, so I'll let you know how it goes. Thanks. :)

Hi. I've made some progress. I've added a util for detecting when running in Node-Webkit. When Node-Webkit is detected, the save action opens a dialog using a different system that is able to acquire the full path to the file. The file is then saved using the node file system api. (By the way, the dialog can be opened in the browser too, and I think it could be used to select the save destination, if you wanted that feature in the browser version.)
The next step is to hold on to the file path between saves, and skip the save dialog next time the save action is triggered. I realise that this is potentially dangerous, so I need to be able to check that we are definitely saving the same document and not a new one. Are their any events, flags, or document ids I could use to check for that?
I started adding ctrl-s functionality into SaveController, but I notice that it is only initialised when you expand the save panel. It works after that though. I'm still working out the structure of the project, so it's just sitting in SaveController for now.
If you'd like to take a look at the work-in-progress, you can check out the "desktop-save-action" branch in my fork:
https://github.com/leegrey/piskel/commits/desktop-save-action

(almost no computer time these days, don't worry if I don't respond quickly :) )

Are their any events, flags, or document ids I could use to check for that?

I don't think we can reuse anything here. I suggest we store the save-path on the Piskel instance stored in pskl.app.piskelController. Then we need to review where we create a new Piskel instance and if this save-path should be propagated to the new instance. For example :

in History Service (undo/redo), when we recreate a Piskel instance, the save-path should be kept
in Import Controller when we import a piskel from a file or an image, save-path should be reset

What do you think ?

SaveController only initialized when opening settings panel

For now you can leave the code here. We should split this file into a Controller dedicated to handle events coming from the Save settings panel, and a Service instantiated at application startup, with the save logic + keyboard listeners.
I'll have a look at your fork during the week !

Thanks for the feedback. I've continued to read through the code and am starting to have a clearer understanding of how things work. I was thinking the same thing about the SaveController, since ctrl-s etc need to work before the save panel is opened.
I'll try out your suggestion about storing the save path this week.

I've implemented the storing and propagation of the savePath as you suggested. I've also added a Node-Webkit based file load function so we can hold onto the full savePath when loading a piskel file. Everything seems to be working nicely. The main issue now is that the keyboard shortcut listener for ctrl-s is not initialised until the first time you open the save panel. I'll create a service for this as you suggested, and move some of the save logic out of SaveController.

Looks great !
May I ask about your development environment for node-webkit ? Do you build the app every time you need to test a change or is there a better way ?

I'm just using a standalone version of Node-Webkit, pointing at the /src folder. It uses the "?debug" query string to use the non-packaged source, just like in the "grunt server:debug" configuration. Node-Webkit has the chrome developer tools turned on by default, so development is basically the same as in the browser, no build required. Just hit refresh to see changes.

I just had a look at your fork and did a quick compare with the current master.
Everything looks fine and inline with the project =>  feel free to submit a PR whenever you're ready :)
Thanks !

Will do! I just wanted to give it a once over before making a Pull Request. (I've been too distracted making pixel art!) I'll do that tonight. Thanks :)

Released in v0.5.0. Thanks !


Why do I always get back Tenant1?

I have updated the host file with the dev.local entry but I still get Tenant1 all the time. Please help!!

me,too.

Please see the updated docs/example project.


SimplePie newsblocks.inc.php stops jQuery.mmenu from showing menu on click

Hi, I am completely out of my depth here.
I have recently integrated the latest jQuery.mmenu download into a website, in which I am using SimplePie version 1.1.3 with newsblocks.inc.php version 2.0, to make an RSS feed aggregator.
I'm using JQuery v1.10.1 and jquery.mmenu.min.all.js with jquery.mmenu.all.css.
The menu works fine for all pages except the one page that uses newsblocks.inc.php and simplepie.inc. On this page, when clicking the link at:
div class="header_menu"
a href="#menu" /a Demo
/div
which usually opens the menu, I just get #menu appended onto the page address in the browser address bar and nothing happens with the menu (it stays hidden).
jquery.mmenu.debugger.js doesn't report any errors.
Has anyone seen this before? Have any idea of a work around?
I am completely scratching my head. My knowledge of JS is poor so delving into  jquery.mmenu.min.all.js is proving very difficult.
Any help would be be much appreciated.
Cheers,
Dan.

Don't unbind the click event from the body...
If that isn't an option, I guess you could try to fire the mmenu plugin after all other scripts. Maybe even onWindowLoad instead of onDocumentReady.

Don't unbind the click event from the body...
If that isn't an option, I guess you could try to fire the mmenu plugin after all other scripts. Maybe even onWindowLoad instead of onDocumentReady.


Update docker-compose.yml

When Dockerfile.notebooks was renamed to Dockerfile, this file wasn't updated.

#56

thanks!


AttributeError: module 'tornado.gen' has no attribute 'Task'

Im getting this error:
mopidy[30379]: [youtube] IXNrM3PTIZ0: Downloading webpage
mopidy[30379]: [download] Destination: /var/cache/mopidy/youtube/IXNrM3PTIZ0.webm
mopidy[30379]: [788B blob data]
mopidy[30379]: ERROR    [HttpServer] tornado.application Uncaught exception GET /youtube/IXNrM3PTIZ0.webm (<IP_ADDRESS>)
mopidy[30379]: HTTPServerRequest(protocol='http', host='localhost:6680', method='GET', uri='/youtube/IXNrM3PTIZ0.webm', version='HTTP/1.1', remote_ip='<IP_ADDRESS>')
mopidy[30379]: Traceback (most recent call last):
mopidy[30379]:   File "/usr/lib/python3/dist-packages/tornado/web.py", line 1704, in _execute
mopidy[30379]:     result = await result
mopidy[30379]:   File "/usr/lib/python3/dist-packages/tornado/gen.py", line 234, in wrapper
mopidy[30379]:     yielded = ctx_run(next, result)
mopidy[30379]:   File "/usr/local/lib/python3.9/dist-packages/mopidy_youtube/web.py", line 100, in get
mopidy[30379]:     yield tornado.gen.Task(self.flush)
mopidy[30379]: AttributeError: module 'tornado.gen' has no attribute 'Task'
mopidy[30379]: ERROR    [HttpServer] tornado.general Cannot send error response after headers written
mopidy[30379]: ERROR    [HttpServer] tornado.general Failed to flush partial response
mopidy[30379]: Traceback (most recent call last):
mopidy[30379]:   File "/usr/lib/python3/dist-packages/tornado/web.py", line 1704, in _execute
mopidy[30379]:     result = await result
mopidy[30379]:   File "/usr/lib/python3/dist-packages/tornado/gen.py", line 234, in wrapper
mopidy[30379]:     yielded = ctx_run(next, result)
mopidy[30379]:   File "/usr/local/lib/python3.9/dist-packages/mopidy_youtube/web.py", line 100, in get
mopidy[30379]:     yield tornado.gen.Task(self.flush)
mopidy[30379]: AttributeError: module 'tornado.gen' has no attribute 'Task'
mopidy[30379]: During handling of the above exception, another exception occurred:
mopidy[30379]: Traceback (most recent call last):
mopidy[30379]:   File "/usr/lib/python3/dist-packages/tornado/web.py", line 1204, in send_error
mopidy[30379]:     self.finish()
mopidy[30379]:   File "/usr/lib/python3/dist-packages/tornado/web.py", line 1158, in finish
mopidy[30379]:     self.request.connection.finish()
mopidy[30379]:   File "/usr/lib/python3/dist-packages/tornado/http1connection.py", line 511, in finish
mopidy[30379]:     raise httputil.HTTPOutputError(
mopidy[30379]: tornado.httputil.HTTPOutputError: Tried to write 16877411 bytes less than Content-Length

When?

Thanks @kingosticks , and apologies @9acca9 for my abrupt response - as Nick says, it is difficult to deal with bug reports that don't include a bit of context, which can be frustrating.
But it does look like I have some things to look into, so thanks for raising the issue.
Cheers
Nik

Oh, sorry. I was very tired and don't notice that I was not writing the context when create the post.
Thanks for all your work.

I've been getting this after upgrading recently. Mopidy 3.4.1, Mopidy-YouTube 3.6.1 and yt-dlp 2023.2.17
Feb 21 18:09:42 hn mopidy[4816]: INFO     2023-02-21 18:09:42,662 [4817:HttpServer] mopidy_youtube.web
Feb 21 18:09:42 hn mopidy[4816]:   started serving KlTMTxhz9Kg.webm to gstreamer
Feb 21 18:09:42 hn mopidy[4816]: ERROR    2023-02-21 18:09:42,856 [4817:HttpServer] tornado.application
Feb 21 18:09:42 hn mopidy[4816]:   Uncaught exception GET /youtube/KlTMTxhz9Kg.webm (<IP_ADDRESS>)
Feb 21 18:09:42 hn mopidy[4816]: HTTPServerRequest(protocol='http', host='localhost:6680', method='GET', uri='/youtube/KlTMTxhz9Kg.webm', version='HTTP/1.1', remote_ip='<IP_ADDRESS>')
Feb 21 18:09:42 hn mopidy[4816]: Traceback (most recent call last):
Feb 21 18:09:42 hn mopidy[4816]:   File "/usr/local/lib/python3.9/dist-packages/tornado/web.py", line 1713, in _execute
Feb 21 18:09:42 hn mopidy[4816]:     result = await result
Feb 21 18:09:42 hn mopidy[4816]:   File "/usr/local/lib/python3.9/dist-packages/tornado/gen.py", line 234, in wrapper
Feb 21 18:09:42 hn mopidy[4816]:     yielded = ctx_run(next, result)
Feb 21 18:09:42 hn mopidy[4816]:   File "/usr/local/lib/python3.9/dist-packages/mopidy_youtube/web.py", line 100, in get
Feb 21 18:09:42 hn mopidy[4816]:     yield tornado.gen.Task(self.flush)
Feb 21 18:09:42 hn mopidy[4816]: AttributeError: module 'tornado.gen' has no attribute 'Task'
Feb 21 18:09:42 hn mopidy[4816]: ERROR    2023-02-21 18:09:42,857 [4817:HttpServer] tornado.general
Feb 21 18:09:42 hn mopidy[4816]:   Cannot send error response after headers written

Thanks @nbx3 for promoting me on this; I'd completely forgotten about it, and have been busy with other things. I'll bump it up my to-do list...
Cheers
Nik

Maybe fixed by https://github.com/natumbri/mopidy-youtube/commit/0a069b75716bddfc849492c3df9f450fa4563c61 ?

Hi - yes, I think it is fixed by that one. I just haven't had a chance to test it or push it out to pypi.
I'll see if I can do it today... Hopefully it is actually fixed!

I did some basic testing and playing youtube videos now works.

OK, on the strength of that testing, I've pushed a new release - thanks!  If it comes back, reopen please.


perf(chokidar): avoid fs calls on ignored files

Description
There are will be some extra fs calls on the ignored files (e.g especially when generating .vite cache) in chokidar. I think we could optimize it. But I also notice that https://github.com/paulmillr/chokidar is less active now, so maybe we can add  a pnpm patch for it.
This pr will avoid unnecessary calculations when ignored files change. I tested https://github.com/Lani/vite-2.7-slow before and after this pr. There will be 20-50ms faster after this pr when initial startup.

Additional context
I will send a PR to fix this upstream later. And once it gets merged, we can revert this and upgrade chokidar to the new one.

What is the purpose of this pull request?

[ ] Bug fix
[ ] New Feature
[ ] Documentation update
[x] Other

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Read the Pull Request Guidelines and follow the PR Title Convention.
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[x] Ideally, include relevant tests that fail without this PR but pass with it.

/ecosystem-ci run

Histoire is failing in main, and I got the same error for Iles in https://github.com/vitejs/vite/pull/12572#issuecomment-1483599927. This looks safe to merge.
Awesome work @sun0day! Let's merge it so we give time for folks to test this while we are in beta.


Missing option to change R-engine/interpreter

This video from RTVS 0.3 explains how to change between CRAN, MRAN etc., using:
Options > R Tools > Advanced > General > R Engine (64-bit)
This option is not available in my fresh install (RTVS_2017-03-07.4.exe).
Where can I switch to MRAN? (I already install Microsoft R Open).

RTVS for 2017 will be back in april/may time frame.
meanwhile, RC3 is available for 2015.
thanks.
On Fri, Mar 10, 2017 at 12:47 AM, th0ger<EMAIL_ADDRESS>wrote:

This video https://www.youtube.com/watch?v=KPS0ytrt9SA from RTVS 0.3
explains how to change between CRAN, MRAN etc., using:
Options > R Tools > Advanced > General > R Engine (64-bit)
This option is not available in my fresh install (RTVS_2017-03-07.4.exe).
Where can I switch to MRAN? (I already install Microsoft R Open).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/RTVS/issues/3285, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAtUVMDezwB0CyvTuLrUukOHB8KL4kBzks5rkQ4rgaJpZM4MZHmZ
.

I don't think this is about VS 2017. It's about a recent build of RTVS from 2017 :)
@th0ger, we have reworked handling of R implementations since 0.3 significantly. Now we try to detect all that you have installed, and show them all in the Workspaces tool window - you can show it via R Tools | Windows. There, you can easily switch between them, and manually add any missing ones that auto-detect didn't handle.

R Tools -> Windows -> Workspaces.


Outdated files in the dev-1.20-ko.1 branch (partial)

#25521 is the umbrella issue of this.
to be modified

[ ] content/en/docs/tasks/administer-cluster/highly-available-master.md 1 file changed, 33 insertions(+)
[ ] content/en/docs/tasks/administer-cluster/kubeadm/adding-windows-nodes.md 1 file changed, 74 insertions(+), 19 deletions(-)
[ ] content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade.md 1 file changed, 92 insertions(+), 213 deletions(-)
[ ] content/en/docs/tasks/network/validate-dual-stack.md 1 file changed, 96 insertions(+), 23 deletions(-)
[ ] content/en/docs/tasks/run-application/horizontal-pod-autoscale.md 1 file changed, 69 insertions(+)

2 files to be renamed

[ ] R073 content/en/examples/service/networking/dual-stack-ipv4-svc.yaml -> content/en/examples/service/networking/dual-stack-ipfamilies-ipv6.yaml
[ ] R076 content/en/examples/service/networking/dual-stack-ipv6-lb-svc.yaml -> content/en/examples/service/networking/dual-stack-prefer-ipv6-lb-svc.yaml

/assign @kosehy
/milestone dev-1.20-ko.1

/language ko

/triage accepted


MSID: 96223 Version: 1 DOI: 10.1101/2<IP_ADDRESS>4653

MSID: 96223
Version: 1
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>4653
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=96223
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>4653

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/96223v1
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>4653
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/96223/v1/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

Please ensure author response is included (was added after the reviews were posted)


Add has_barriers

Summary of changes
This pull request includes changes to the src/pyqasm/modules/base.py file to add functionality for detecting barrier operations in quantum programs, as well as updates to the corresponding tests in tests/qasm3/test_barrier.py.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
:loudspeaker: Thoughts on this report? Let us know!


Invalid operation types when using nested fragment and skipTypename

Describe the bug
The generated types for operations references non-existing types when using nested fragment and skipTypename: true
To Reproduce
https://codesandbox.io/s/sleepy-chebyshev-tqgrh?file=/types.ts

My GraphQL schema:

schema {
  query: Query
}

type Query {
  animals: [Animal!]!
}

interface Animal { id: ID! }
type Duck implements Animal { id: ID! }
type Lion implements Animal { id: ID! }
type Puma implements Animal { id: ID! }
type Wolf implements Animal { id: ID! }

My GraphQL operations:

fragment CatFragment on Animal {
  ... on Lion { id }
  ... on Puma { id }
}

query kitty {
  animals { ...CatFragment }
}

My codegen.yml config file:

generates:
  types.ts:
    plugins:
      - typescript
      - typescript-operations
    config:
      skipTypename: true

Generated types
type CatFragment_Lion_Fragment = Pick<Lion, "id">;
type CatFragment_Puma_Fragment = Pick<Puma, "id">;

export type CatFragmentFragment =
  | CatFragment_Lion_Fragment
  | CatFragment_Puma_Fragment;

export type KittyQuery = {
  animals: Array<
    | CatFragment_Duck_Fragment
    | CatFragment_Lion_Fragment
    | CatFragment_Puma_Fragment
    | CatFragment_Wolf_Fragment
  >;
};

Expected behavior
It should use the generated fragment type in the query
type CatFragment_Lion_Fragment = Pick<Lion, "id">;
type CatFragment_Puma_Fragment = Pick<Puma, "id">;

export type CatFragmentFragment =
  | CatFragment_Lion_Fragment
  | CatFragment_Puma_Fragment;

export type KittyQuery = {
  animals: Array<CatFragmentFragment>;
};

Environment:

@graphql-codegen/typescript: 1.13.3
@graphql-codegen/typescript-operations: 1.13.3
NodeJS: 10.20

Looks like this bug still exists with the following versions:
    "@graphql-codegen/cli": "1.21.5",
    "@graphql-codegen/core": "1.17.10",
    "@graphql-codegen/import-types-preset": "1.18.2",
    "@graphql-codegen/introspection": "1.18.2",
    "@graphql-codegen/schema-ast": "1.18.3",
    "@graphql-codegen/typescript": "1.22.1",
    "@graphql-codegen/typescript-operations": "1.18.0",

Looks like this bug still exists with the following versions:
    "@graphql-codegen/core": "1.17.10",
    "@graphql-codegen/typescript": "1.22.1",
    "@graphql-codegen/typescript-operations": "1.18.0",

Just as a side-note: You don't have to use core explicitly (unless you use programmatic API).

Just writing this here because some developers asked that, and it seems related to the topic here.
If you have interface Animal and you have 4 types that implements this interface, it means that the fields that are defined as Animal in their return type, can return all 4 options of that type.
type Query {
  animals: [Animal!]! # This field can return Duck/Lion/Puma/Wolf
}

interface Animal { id: ID! }
type Duck implements Animal { id: ID! }
type Lion implements Animal { id: ID! }
type Puma implements Animal { id: ID! }
type Wolf implements Animal { id: ID! }

And that's regardless of the fragments or queries that you are asking for.
For example, if you are querying for the animals field, and you have fragments from Duck and Lion - that means that you ask for specific fields in case of a Duck/Lion, but you'll get an empty object in case of Puma and Wolf are returned. It doesn't apply a filter, it's just a selection set.
For the specific point on that issue:
Seems like we have a real issue here with the missing fragments that codegen generates. I managed to reproduce that in:  https://github.com/dotansimha/graphql-code-generator/pull/6161
Seems like we skip generation of fragment sub-types when skipTypename: true. So actually, the result of the generation should still be:
export type KittyQuery = {
  animals: Array<
    | CatFragment_Duck_Fragment
    | CatFragment_Lion_Fragment
    | CatFragment_Puma_Fragment
    | CatFragment_Wolf_Fragment
  >;
};

But the references fragments like CatFragment_Duck_Fragment should be defined as:
type CatFragment_Duck_Fragment = {}

Fixed in<EMAIL_ADDRESS>


Release proposal 14.3.4

Proposal for a patch release, just to bump the eslint config package with a patch bump.
It includes the relaxation of no-return-await, that was discussed here: https://github.com/standard/standard/issues/1442, and merged here: https://github.com/standard/eslint-config-standard/pull/164
Since there is no rush this time I'll let this issue be open either until a few people from the team have signed off, or unless I get no objections in a few days. Maybe about a week is resonable?

Releasing now 🚀

Thank you, @LinusU !

Thanks for doing this release, @LinusU


Using GCIR to deploy to JBoss

Hi, I'm in the last step of my script, where the built WAR (using ANT) is deployed to JBoss. I am doing this by copying the WAR file to the deployments folder of JBoss. I need to know which user runs the runner so I can give appropriate permissions to write to write to that folder. I tried adding the gitlab_ci_runner user to the wildfly group (which runs the JBoss), and chmod g+w to the deployments dir to no avail.
rm -f /opt/wildfly/standalone/deployments/dist.war*
rm: cannot remove `/opt/wildfly/standalone/deployments/dist.war.undeployed': Permission denied

Hi @acwilan. I'm having the same issue.
I think I'm missing something. How did you solve your issue?

@jlucasps I don't remember, but I think I ended up using a maven plugin to directly publish to JBoss using the management interface

Hum... ok.
I think my issue is different. But anyway, thank you very much.


Switch targets to object-oriented

Target is an object with the following methods

getContentSelection (used for selection, get text, highlight for reference)
getRemovalDecorationRange
constructChangeEdit (takes text)
constructInsertionEdit (takes text and returns edit that has range as a selection, so that paste can use empty string then set cursor to active before pasting)
constructRemovalEdit

The target will also have the following, but somehow hide it before action sees it because it shouldn't be used there. It's mostly for downstream pipeline stages, eg "after":

Trailing delimiter range
Leading delimiter range

Positional modifier is just a pipeline stage
Need to have proper "insert" command and then can distinguish between "insert after" vs "change after" (changes delimiter)

Remove inside/outside as proper modifiers
Add start of/end of as proper modifiers
Create a draft target type used in the pipeline. Gets converted into a function only finalized target at the end.

I think we prob potentially want edit constructors instead of ranges, eg for camel-case, no?

I think we prob potentially want edit constructors instead of ranges, eg for camel-case, no?

I think we prob want constructInsertionEdit to take a list of texts, so that we can handle #184

We can do that


[spark] Change Spark extension API

Description
Brief description of what this PR is about
Change Spark extension API

Implement HasInputCol/HasInputCols, HasOutputCol/HasOutputCols in each specific task
Add prediction column to the input dataframe instead of replacing the columns
ImageClassifier output struct type output
TextTokenizer output struct type output

Codecov Report
Base: 72.08% // Head: 74.27% // Increases project coverage by +2.18% :tada:

Coverage data is based on head (93c7733) compared to base (bb5073f).
Patch coverage: 73.71% of modified lines in pull request are covered.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@             Coverage Diff              @@
##             master    #2388      +/-   ##
============================================
+ Coverage     72.08%   74.27%   +2.18%
- Complexity     5126     6781    +1655
============================================
  Files           473      664     +191
  Lines         21970    29492    +7522
  Branches       2351     3060     +709
============================================
+ Hits          15838    21906    +6068
- Misses         4925     6097    +1172
- Partials       1207     1489     +282

Impacted Files
Coverage Δ

api/src/main/java/ai/djl/modality/cv/Image.java
69.23% <ø> (-4.11%)
:arrow_down:

...rc/main/java/ai/djl/modality/cv/MultiBoxPrior.java
76.00% <ø> (ø)

...rc/main/java/ai/djl/modality/cv/output/Joints.java
71.42% <ø> (ø)

.../main/java/ai/djl/modality/cv/output/Landmark.java
100.00% <ø> (ø)

...main/java/ai/djl/modality/cv/output/Rectangle.java
72.41% <0.00%> (ø)

...i/djl/modality/cv/translator/BigGANTranslator.java
21.42% <0.00%> (-5.24%)
:arrow_down:

.../modality/cv/translator/ImageFeatureExtractor.java
0.00% <0.00%> (ø)

.../ai/djl/modality/cv/translator/YoloTranslator.java
27.77% <0.00%> (+18.95%)
:arrow_up:

...ain/java/ai/djl/modality/cv/util/NDImageUtils.java
67.10% <0.00%> (+7.89%)
:arrow_up:

api/src/main/java/ai/djl/modality/nlp/Decoder.java
63.63% <ø> (ø)

... and 629 more

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

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


MIP-X09

@anajuliabit @ElliotFriedman If I try to generate calldata locally via source proposals/mips/mip-x09/x09.sh && forge script proposals/templates/MarketUpdate.sol
I get the following error for Moonbeam xcDOT:
[17952] mxcDOT::_setReserveFactor(500000000000000000 [5e17])
    │   │   │   ├─ [12272] 0x47DFFebeF33719315bD5a91DB6BFb81691347914::_setReserveFactor(500000000000000000 [5e17]) [delegatecall]
    │   │   │   │   ├─ [6] xcDOT::balanceOf(mxcDOT: [0xD22Da948c0aB3A27f5570b604f3ADef5F68211C3]) [staticcall]
    │   │   │   │   │   └─ ← [Revert] EvmError: Revert
    │   │   │   │   └─ ← [Revert] EvmError: Revert
    │   │   │   └─ ← [Revert] EvmError: Revert
    │   │   └─ ← [Revert] revert: MultichainGovernor: execute call failed
    │   └─ ← [Revert] revert: MultichainGovernor: execute call failed
    └─ ← [Revert] log != expected log

If I remove the mxcDOT entry from the json, I am able to generate the calldata without issues. Could you please advise?

@rsrizvi fix is in this PR, please take a pass #442

Thanks. What is TLDR on this etch mechanism? I'm fine to approve if you are confident in the change

@ElliotFriedman Please merge your referenced PR, then I will pull master, push, and also regenerate the calldata

rameel@Mac moonwell-contracts-v2 % source proposals/mips/mip-x10/x10.sh && forge script proposals/templates/MarketUpdate.sol
JSON_PATH=proposals/mips/mip-x10/x10.json
DESCRIPTION_PATH=proposals/mips/mip-x10/x10.md
PRIMARY_FORK_ID=0
[⠊] Compiling...
[⠒] Compiling 12 files with Solc 0.8.10
[⠘] Compiling 230 files with Solc 0.8.19
[⠔] Solc 0.8.10 finished in 653.26ms
[⠑] Solc 0.8.19 finished in 13.78s
Compiler run successful!
Script ran successfully.
Gas used: 39162623

== Logs ==

--------------- Proposal Description ----------------
 # MIP-X10: Gauntlet's Monthly Recommendations (12/13/2024)

## Base

A proposal to adjust 4 risk parameters:

| Risk Parameter          | Current Value | Recommended Value |
| ----------------------- | ------------- | ----------------- |
| USDbC Supply Cap        | 110,000       | 1                 |
| USDbC Borrow Cap        | 110,000       | 1                 |
| USDbC Collateral Factor | 69%           | 63%               |
| weETH Collateral Factor | 74%           | 78%               |

<sub> \*Cap Recommendations will be implemented via Guardian </sub>

### IR Parameters

A proposal to adjust IR parameters for USDC, EURC and cbBTC:

| USDC IR Parameters | Current   | Recommended |
| ------------------ | --------- | ----------- |
| Base               | 0         | 0           |
| Kink               | 0.9       | 0.9         |
| Multiplier         | **0.056** | **0.061**   |
| Jump Multiplier    | 9         | 9           |

| EURC IR Parameters | Current   | Recommended |
| ------------------ | --------- | ----------- |
| Base               | 0         | 0           |
| Kink               | 0.9       | 0.9         |
| Multiplier         | **0.056** | **0.061**   |
| Jump Multiplier    | 9         | 9           |

| cbBTC IR Parameters | Current   | Recommended |
| ------------------- | --------- | ----------- |
| Base                | 0         | 0           |
| Kink                | **0.6**   | **0.35**    |
| Multiplier          | **0.067** | **0.045**   |
| Jump Multiplier     | **3**     | **2**       |

## Optimism

A proposal to adjust 4 risk parameters:

| Risk Parameter         | Current Value | Recommended Value |
| ---------------------- | ------------- | ----------------- |
| WBTC Collateral Factor | 50%           | 10%               |
| WBTC Supply Cap        | 1             | 0.0001            |
| WBTC Borrow Cap        | 0.1           | 0.0001            |
| WETH Supply Cap        | 10,000        | 12,000            |

<sub> \*Cap Recommendations will be implemented via Guardian </sub>

### IR Parameters

A proposal to adjust IR parameters for USDC, USDT,and DAI

| USDC IR Parameters | Current   | Recommended |
| ------------------ | --------- | ----------- |
| Base               | 0         | 0           |
| Kink               | 0.9       | 0.9         |
| Multiplier         | **0.056** | **0.061**   |
| Jump Multiplier    | 9         | 9           |

| USDT IR Parameters | Current   | Recommended |
| ------------------ | --------- | ----------- |
| Base               | 0         | 0           |
| Kink               | 0.9       | 0.9         |
| Multiplier         | **0.056** | **0.061**   |
| Jump Multiplier    | 9         | 9           |

| DAI IR Parameters | Current   | Recommended |
| ----------------- | --------- | ----------- |
| Base              | 0         | 0           |
| Kink              | 0.9       | 0.9         |
| Multiplier        | **0.056** | **0.061**   |
| Jump Multiplier   | 9         | 9           |

## Moonbeam

A proposal to adjust 6 total risk parameters:

| Parameter                 | Current Value | Recommended Value |
| ------------------------- | ------------- | ----------------- |
| WBTC.wh Borrow Cap        | 0.5           | 0.1               |
| USDC.wh Collateral Factor | 42%           | 39%               |
| WETH.wh Collateral Factor | 38%           | 33%               |
| WBTC.wh Collateral Factor | 15%           | 14%               |
| xcDOT Reserve Factor      | 35%           | 50%               |
| WGLMR Reserve Factor      | 35%           | 50%               |

<sub> \*Cap Recommendations will be implemented via Guardian </sub>

Our recommendation post is located in the forums, please refer to this
[link](https://forum.moonwell.fi/t/gauntlet-base-optimism-moonbeam-moonriver-monthly-recommendations-2024-12-13/1458).
By approving this proposal, you agree that any services provided by Gauntlet
shall be governed by the terms of service available at gauntlet.network/tos

----------------- Proposal Actions ------------------

  1). Set collateral factor to<PHONE_NUMBER>00000000 for mUSDCwh
  target: 0x8E00D5e02E65A19337Cdba98bbA9F84d4186a180
value: 0
payload:
  0xe4028eee000000000000000000000000744b1756e7651c6d57f5311767eafe5e931d615b00000000000000000000000000000000000000000000000005698eef06670000
  Proposal type: Moonbeam

  2). Set collateral factor to<PHONE_NUMBER>00000000 for MOONWELL_mETH
  target: 0x8E00D5e02E65A19337Cdba98bbA9F84d4186a180
value: 0
payload:
  0xe4028eee000000000000000000000000b6c94b3a378537300387b57ab1cc0d2083f9aeac0000000000000000000000000000000000000000000000000494654067e10000
  Proposal type: Moonbeam

  3). Set collateral factor to<PHONE_NUMBER>00000000 for MOONWELL_mWBTC
  target: 0x8E00D5e02E65A19337Cdba98bbA9F84d4186a180
value: 0
payload:
  0xe4028eee000000000000000000000000aaa20c5a584a9fecdfedd71e46da7858b774a9ce00000000000000000000000000000000000000000000000001f161421c8e0000
  Proposal type: Moonbeam

  4). Set reserve factor to<PHONE_NUMBER>00000000 for mxcDOT
  target: 0xD22Da948c0aB3A27f5570b604f3ADef5F68211C3
value: 0
payload:
  0xfca7820b00000000000000000000000000000000000000000000000006f05b59d3b20000
  Proposal type: Moonbeam

  5). Set reserve factor to<PHONE_NUMBER>00000000 for mGLIMMER
  target: 0x091608f4e4a15335145be0A279483C0f8E4c7955
value: 0
payload:
  0xfca7820b00000000000000000000000000000000000000000000000006f05b59d3b20000
  Proposal type: Moonbeam

  6). Set collateral factor to<PHONE_NUMBER>00000000 for MOONWELL_WBTC
  target: 0xCa889f40aae37FFf165BccF69aeF1E82b5C511B9
value: 0
payload:
  0xe4028eee0000000000000000000000006e6ca598a06e609c913551b729a228b023f06fdb000000000000000000000000000000000000000000000000016345785d8a0000
  Proposal type: Optimism

  7). Set JRM for 0x9c3431faf6aF953815893ca4661B8F437ce0Ee22 for MOONWELL_USDC
  target: 0x8E08617b0d66359D73Aa11E11017834C29155525
value: 0
payload:
  0xf2b3abbd0000000000000000000000009c3431faf6af953815893ca4661b8f437ce0ee22
  Proposal type: Optimism

  8). Set JRM for 0x9c3431faf6aF953815893ca4661B8F437ce0Ee22 for MOONWELL_USDT
  target: 0xa3A53899EE8f9f6E963437C5B3f805FEc538BF84
value: 0
payload:
  0xf2b3abbd0000000000000000000000009c3431faf6af953815893ca4661b8f437ce0ee22
  Proposal type: Optimism

  9). Set JRM for 0x9c3431faf6aF953815893ca4661B8F437ce0Ee22 for MOONWELL_DAI
  target: 0x3FE782C2Fe7668C2F1Eb313ACf3022a31feaD6B2
value: 0
payload:
  0xf2b3abbd0000000000000000000000009c3431faf6af953815893ca4661b8f437ce0ee22
  Proposal type: Optimism

  10). Set collateral factor to<PHONE_NUMBER>00000000 for MOONWELL_USDBC
  target: 0xfBb21d0380beE3312B33c4353c8936a0F13EF26C
value: 0
payload:
  0xe4028eee000000000000000000000000703843c3379b52f9ff486c9f5892218d2a065cc800000000000000000000000000000000000000000000000008be35a9807f0000
  Proposal type: Base

  11). Set collateral factor to<PHONE_NUMBER>00000000 for MOONWELL_weETH
  target: 0xfBb21d0380beE3312B33c4353c8936a0F13EF26C
value: 0
payload:
  0xe4028eee000000000000000000000000b8051464c8c92209c92f3a4cd9c73746c4c3cfb30000000000000000000000000000000000000000000000000ad31dde0cce0000
  Proposal type: Base

  12). Set JRM for 0x01635c141C070944EAE7919443ff61dB2a6a4597 for MOONWELL_USDC
  target: 0xEdc817A28E8B93B03976FBd4a3dDBc9f7D176c22
value: 0
payload:
  0xf2b3abbd00000000000000000000000001635c141c070944eae7919443ff61db2a6a4597
  Proposal type: Base

  13). Set JRM for 0x01635c141C070944EAE7919443ff61dB2a6a4597 for MOONWELL_EURC
  target: 0xb682c840B5F4FC58B20769E691A6fa1305A501a2
value: 0
payload:
  0xf2b3abbd00000000000000000000000001635c141c070944eae7919443ff61db2a6a4597
  Proposal type: Base

  14). Set JRM for 0x2B42e79f46e4E5d8966b098140915d1E7355E1E6 for MOONWELL_cbBTC
  target: 0xF877ACaFA28c19b96727966690b2f44d35aD5976
value: 0
payload:
  0xf2b3abbd0000000000000000000000002b42e79f46e4e5d8966b098140915d1e7355e1e6
  Proposal type: Base

----------------- Proposal Calldata ------------------

  [encoded data, 16330 characters]


Dropdown for require in JS should also show JSON files

VSCode Version: Version 1.23.1 (1.23.1)
OS Version: macOS 10.13.4 (17E199)

Steps to Reproduce:

Create a JSON file.
Create a JS file. In the file, start typing: require(./.
At this point, the dropdown for files in the current dir will appear. The JSON file that we created does not appear in the list. Yet it should, since requiring JSON files in JS is perfectly valid, and will simply return a JS object.

Does this issue occur when all extensions are disabled?: Yes

importing json files is not supported by all runtimes so you currently have to opt in to this feature. In VS Code insiders, set  "resolveJsonModule": true in your jsconfig or tsconfig
{
    "compilerOptions": {
        "module": "commonjs",
        "target": "es2016",
        "jsx": "preserve",
        "resolveJsonModule": true
    },
    "exclude": [
        "node_modules",
        "**/node_modules/*"
    ]
}


RealSense SDK2.0 and hand tracking/gesture recognition algorithms

Are there any hand tracking and hand gesture recognition algorithms in RealSense SDK2.0? Does the D400 camera work with previous version of SDK? What camera and SDK version are better if I'm going to work with hand gesture recognition?

Hello @VeraCurly,
There are currently no hand tracking and hand gesture recognition algorithms in RealSense SDK2.0. They are being evaluated for a future a release. The D400 cameras work only with this SDK.
The combination of SR300 camera and RealSense SDK for Windows Release 3 are capable of doing hand gesture recognition. However, both of these products are discontinued.
Regards,
Jesus
Intel Customer Support

Thank you for the fast answer!

Is there any update on this? Has the hand tracking support been added to the SDK2.0 yet?

Hello @zrenegade,
All the hand tracking info for SDK 2.0 can be found here: https://github.com/IntelRealSense/hand_tracking_samples. Note that SDK 2.0 does not have hand-tracking support built-in. These are samples that show how to do it using the SDK.
Regards,
Jesus
Intel Customer Support

Hello @liarokapisv,
You are right. The hand tracking samples are extremely out of date. Notice they were put up over a year ago and have not been updated since.
I recommend you take a look at Nuitrack.com, which has created an SDK with skeletal and tracking algorithms for the D400 series cameras.
Regards,
Jesus G.
Intel Customer Support

Can I package an Unreal project with a Windows version?

Nuitrack currently does only palm tracking and there is no finger/gesture tracking, hopefully somebody will pickup the realsense handtracking and port it to librealsense 2.

I am going to proceed with a project that recognizes hands with real license d435.
Nulitrack says Unreal only supports Android.
Did you package successfully with Windows version?

Hello @simpple28 , Did you come up with any hand recognizer for d435?

So if intel realsense D415 is used for hand tracking, should I choose opencv or Nulitrack? Seek advice! Thanks!

Nuitrack当前仅执行手掌跟踪，并且没有手指/手势跟踪，希望有人能够使用realsense手动跟踪并将其移植到librealsense 2。

那么我认为Cubemos Skeleton Tracking SDK是不可行的方案。那么我要想用D415做手部追踪该怎么做啊。希望得到前辈的指点！感谢！

Hello L-xn, you can use either one. It depends on how comfortable you are developing your own solutions and if the Nuitrack SDK provides what you are looking for. The Nuitrack SDK must be purchased. I recommend contacting Nuitrack to determine if it will fit your needs.

您好@ L-xn，您可以使用任何一个。这取决于您开发自己的解决方案的舒适程度以及Nuitrack SDK是否提供您想要的东西。必须购买Nuitrack SDK。我建议联系Nuitrack以确定它是否适合您的需求。

If I use opencv, is there any information about this? Thank you!


Improve guidance for helping users debug performance issues

Is your proposal related to a problem?

This project receives a large number of performance related questions of the form:

Why is <component> using so much memory?
Please help, <component> is running slowly.

The level & detail of information provided in these reports can vary quite a lot. The standard bug report that users fill out only asks them for relevant logs for a given component. In the process debugging an issue, the folks involved usually end up sharing screenshots of queries that eventually help us debug the issue.
This creates two problems:

There is often significant latency between the user raising the issue, and the requisite information being shared to enable debugging.
Only experienced maintainers with significant relevant context know what additional metrics and information to ask for. This means newbie contributors (me) can't help progressing user performance tickets.

Describe the solution you'd like

I would like Thanos to follow the example set by upstream Prometheus (1,2,3), and produce a set of deep dive / internals dashboards. This would then form the standard request for information from users when a performance related issue is raised.
This would improve the quality and velocity of communication: the users knows the information they will be asked for, newbie contributors can request the information if it has not yet been provided.
How?
These dashboards will be maintained in the thanos/mixin directory, separately from the existing 'overview' dashboards.
To make it as easy as possible for users to get these dashboards into their Grafana instances, we will:

Vendor the resulting JSON outputted in the local directory.
Upload the JSON to grafana.com so users can import it with a simple ID - example.

Describe alternatives you've considered

Keep doing what we're doing - and muddle through :man_shrugging:
Additional context

Kind of related to https://github.com/thanos-io/thanos/issues/4338

still relevant


Question about Python source gode example for QIF applications

Hi,
I'm trying to run the Python source code example.
According to the readme file, it says I have to copy a QIF schema file into QIF3.0_Open_Source_Apps\Python\PyXB\QIFApplications folder, but I cannot find any schema file in the example document.
Does it mean I can simply find a QIF schema file and add it into that folder?
Is it supposed to have a schema file inside the example document which is currently missing?
Dave

Hi Dave,
You need to download QIF3.0 from the DMSC QIF site.  It contains schemas and the standard in pdf format.  You then drag and drop the schema files out of the XSD folder into the QIFApplications folder.
Best,
Cole

Hi Cole,
Thank you for the elaborations!
Best regards,
Dave
山衛科技股份有限公司
Samwells Testing Inc.
新北市汐止區康寧街169巷25號11樓之1
11F-1, No. 25, Lane 169, Kangning St., Xizhi Dist., New Taipei City 22180, Taiwan.
Tel: +886-2-2692-1400
Mobile: +886 963-718-303
e-mail<EMAIL_ADDRESS>From: Cole St John
Date: 2020-07-08 16:59
To: QualityInformationFramework/qif-community
CC: DGW1978; Author
Subject: Re: [QualityInformationFramework/qif-community] Question about Python source gode example for QIF applications (#7)
Hi Dave,
You need to download QIF3.0 from the DMSC QIF site. It contains schemas and the standard in pdf format. You then drag and drop the schema files out of the XSD folder into the QIFApplications folder.
Best,
Cole
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
--
Avast 防毒軟體已檢查此封電子郵件的病毒。
https://www.avast.com/antivirus


Implement transaction signing/verification in XBR simple buyer/seller

https://github.com/xbr/xbr-protocol/blob/958053a877c696da1876fd2dfac664b4bae22c9a/xbr/_seller.py#L94
https://github.com/xbr/xbr-protocol/blob/958053a877c696da1876fd2dfac664b4bae22c9a/xbr/_seller.py#L200

This has been implemented


diary - slice, value, select relations

There is a need to alling

element's value
slot expression for location in datadom
event
value expression propagated into slot
initial slot value expression

Ideas to think about

#
markup
sl. init
sl. from
event
effect

1
<input slice="s">
no
value
change
1:1 slice⮂value

2
<input slice="s" value="A">
A
value
change
slice⮂value, w/ initial

3
<input slice="s" value="A" slice-event="tap"/>
A
value
tap
^, on sync on type

4
<input slice="s" value="{$a}" slice-event="tap" />
attr a
attr
tap
^ w/ initial from attr

5
<input slice="s" value="B" slice-value="'x'+@value" />
expr
expr
change
on click s="xBchanged", init by expr, static value

6
<input slice="s" slice-value="'x:'+@pageX"  slice-event="mousemove" />

mouse
on move s="x:123"

Aspects

initial slice value
initial element value
on event slice data
slice-driven value

Things to think over:

element value gives just inital value,
value is changed by element in runtime.
on re-render value is overriddidden by template.  Hence value can not be used to keep the state/changes.
the goal of slice is to define

the query to populate the slice

initially
on event in runtime

when value is missing, the data selector to set initial value

Slice related attributes:

slice="name-of-slice"
slice-event="tap",  Replacement for slice-update
slice-value="@value"  - xPath evaluation of value assigned to slice.

Attributes passed to slice-value made as combination of element attributes (@value is a runtime value of element) and event object fileds. Like in MouseEvent @pageX

related: #42

Does the removable of the slice=s element trigger the slice-update event?

@jasvir , that has to be defined in the scope of this issue.
IMO the slice-event ( replacement for slice-update ) should disable the slot initialization. The syntetic init event can be used if there is a need.
<input slice="s" > IMO is equals to
<input slice="s" slot-event="change init" slotvalue="/datadom/slice/s">

@jasvir , are there concerns on naming convention for slice attributes ?

@jasvir , you right. It has to be consistent. And during conversation I have misused slot and slice sometimes.
The slot is UI DOM injection in current HTML template standard. slice is datadom part ( /datadom/slice/xxx ) which is part of this discussion.
So slice-event can be later translated to sliceEvent as you mentioned.
Now to the match of attributes to elements.
slice is an attribute and slice-event is another attribute on same element. Like
<input slice="xxx" slice-event="keyup" />

But sometimes we would need to populate into different slices with own values. For that own tag has to be used for each slice to avoid confusion.
<textarea>
    <slice name="a" slice-event="keyup" slice-value="'typed '+$value" ></slice>
    <slice name="b" slice-event="keyup" slice-value="char_count($value)" ></slice>

In scenario ^^ the same event to populate different values into different slices. I.e. a="typed GFDFAHGF", b=22.
More in #42

One more thought but I'm not sure this is the right issue for me to add it to... DOM elements have a convention of making executable code in attributes ie event handlers have the convention of starting with on...so onload, onmousedown etc (heh except online). This makes the life of sanitizers easier.  I don't fully understand the semantics of slice-value but if you have expressions in there, it's worth thinking through if you want a convention between dead data attributes and active code.

@jasvir , the custom-element syntax is a mix of HTML and XSLT conventions. It does not use onXxx event handlers with JS code on it. It does not prohibit its use though. At least for now.
XSLT and custom-element attributes do expression evaluation via XPath. There are various attributes and {xPath} convention for such expressions. select, test, etc... Those do not have prefixes and special convention, just hardcoded names.
The slot attribute prefix can be used for recognition that the value is XPath expression. I.e. "active" attributes:

slice is XPath of slot name selection in /dataset/slice/
slice-value is XPath to be evaluated on event
slice-event is event names union, can be XPath as well...

As for "active" part... the template by itself is active markup. Not just its parts like attributes. custom-element is comprize mostly template.

Sample of default value and slot assignment:

Status update. Implemented in develop branch. Unit tests tbd for release. Will be shipped along with #42


Handbook update: how to add multiple hosts or authors.

Description
Updated the marketing blog and webinar section to include instructions on how to add more than one author or host and how to include guests.
Related Issue(s)
#1801
Checklist

[x] I have read the contribution guidelines
[x] I have considered the performance impact of these changes
[ ] Suitable unit/system level tests have been added and they pass
[ ] Documentation has been updated

Gracias! ☺


Hyundai: 2015-16 Genesis resume from standstill fix

Allows 2015-16 Hyundai Genesis to accept the resume command from standstill when the lead car drives away.

route ID

3687c15bdfe09295|2022-08-27--15-54-09
3687c15bdfe09295|2022-09-02--19-54-13

Hmm, the current command doesn't work on that car?

The current command is inconsistent according to multiple users. This issue has been around throughout the years, and this solution has been in forks for quite some time.

Hmm, the current command doesn't work on that car?

I don't really like that there are two code paths here. Let's try to merge them. The main two differences here are incrementing the counter and the max number of messages.

User tested with the merged version and works for his 2015 Genesis: 3687c15bdfe09295|2022-09-02--19-54-13

Glad we got them merged. Has this been tested on cars where the current resume already works? Which change fixes the Genesis: frequency, sending them in a burst, or both?

Glad we got them merged. Has this been tested on cars where the current resume already works? Which change fixes the Genesis: frequency, sending them in a burst, or both?

It does work with the Hyundai Sonata, I could give it a go tomorrow to confirm.
Both the frequency and sending them in a burst worked for the Genesis.

If it was inconsistent it sounds like a timing issue where we keep sending the message at the wrong time to get the ECU to pick it up. Has anyone tried simply changing the interval to an odd number like 0.09 sec (11.11 Hz) or 0.07 sec (14.29 Hz)?

We've tested with the odd numbers and they all behave the same. Users have been testing with this on my fork for weeks and it has been consistently resuming. I believe this is good to merge.

@adeebshihadeh want me to test this on our cars here?

@adeebshihadeh @sshane Is there anything else needed for this PR to merge? It has been tested by multiple users and is working as expected with no issues.

I don't doubt that this works, but it still seems like it's unclear what the fix is here. I'd like to know whether it's the sending in bursts, the frequency change, or both.

I just tested both parts of this code separately. The 20hz didn't seem to fix anything but the extra messages did allow my car to start from a stop.
Here is the branch I used to test:
https://github.com/SeanCox/openpilot/tree/Hyundai--2015-16-Genesis-resume-from-standstill-fix-extra-messages
Here is a route with it working:
85eab094426c2649|2023-02-02--17-56-18--0

I just tested both parts of this code separately. The 20hz didn't seem to fix anything but the extra messages did allow my car to start from a stop.
Here is the branch I used to test: https://github.com/SeanCox/openpilot/tree/Hyundai--2015-16-Genesis-resume-from-standstill-fix-extra-messages
Here is a route with it working: 85eab094426c2649|2023-02-02--17-56-18--0

Thanks for testing this. Are you able to also provide a route with you testing the 20Hz change and failed to spam the button? Would be nice to see the comparisons between both of them.

@sunnyhaibin Here are my notes from testing:
Cruse Control Resume Tests
No changes
Branch:
https://github.com/SeanCox/openpilot
Route:
85eab094426c2649|2023-02-02--17-14-35--6
Test: Failed
20hz
Branch:
https://github.com/SeanCox/openpilot/tree/Hyundai--2015-16-Genesis-resume-from-standstill-fix-20hz
Route:
85eab094426c2649|2023-02-02--17-41-38–0
Test:
Failed
Extra messages
Branch:
https://github.com/SeanCox/openpilot/tree/Hyundai--2015-16-Genesis-resume-from-standstill-fix-extra-messages
Route:
85eab094426c2649|2023-02-02--17-56-18--0
Test: passed
Both 20hz and Extra Messages:
Branch:
https://github.com/SeanCox/openpilot/tree/Hyundai--2015-16-Genesis-resume-from-standstill-fix
Route:
Not tested
Test:
Not tested

@adeebshihadeh What do you think about the state of this PR? Is there anything else needs to be done/tested to get this merged in? Thank you.

Thanks for testing @SeanCox; your tests were quite helpful. @sshane can you take this one over and test on our sonata and optima?

@SeanCox I made a minor change to the counters that should have no impact. Can you stress test this one more time?

Realized my refactor made it send once, then wait 10 frames, then send 5 times in a row, rather than the originally intended send 5 times immediately, wait 10 frames, send 5 times...etc.
However this seems to be a good compromise, as sometimes the Optima I tested this one resumed with just one frame, and sometimes it needed the 5 frame burst to get it resuming, so trying the original behavior first and waiting should be fine. The original resume_count logic also would have this bug if we exited standstill right before resetting the last button frame.

@SeanCox I made a minor change to the counter that should have no impact. Can you test it out real quick?

I will test this later today.

On our Sonata:
Frames to resume:
This PR: 5.804165272815535 frames, 103 runs
Stock: 5.6490840389312975 frames, 131 runs

@SeanCox did you test it out

I see a few cases from your dongle of this working as expected

yeah, I was just about to post this route 85eab094426c2649|2023-02-15--18-42-04--0


lagrange: 1.6.2 → 1.6.4

Motivation for this change
Changelog
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 135427 at 26397e77 run on x86_64-linux 1

1 package failed to build:

lagrange

1 suggestion:

warning: missing-phase-hooks
installPhase should probably contain runHook preInstall and runHook postInstall.
Near pkgs/applications/networking/browsers/lagrange/default.nix:46:3:
   |
46 |   installPhase = lib.optionalString stdenv.isDarwin ''
   |   ^

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement. Does something look off? Please file an issue or reach out on IRC.

Failed to build on x86_64-linux due to temporary problem with connection to git.skyjake.fi. @r-rmcgibbo try again.


[WW-5081] Makes textarea compatible with W3C

Fixes WW-5081

Coverage remained the same at 49.224% when pulling 0d622cfa96dbbc1e286347f30a7527505aeb0ed0 on WW-5081-cols-rows into dbd2f283dad418f0e5856f3c5d7deea0349b10fa on master.


Task-based Inspection for Mingsai #14

Please review the IM3 of 4.4.5 Instance Models section of the SRS, could you understand this notation and what is the input and output of this project according to it?

Yes, I can understand.
It's not 'chloride exposure rate'. Surface chloride concentration is more accurate.


[Material] Update BottomNavigationBar motion to current Material guidelines

Update BottomNavigationBars motion to be up to date with Material Design standards.
Current Material Design guidelines for BottomNavigationBar.
Changes:

"Fixed" Bottom navigation bar label text no longer grows when selected.
"Fixed" Bottom navigation bar icon + text no longer rise when selected.
"Shifting" Bottom navigation bar icon + text no longer Move in the X direction.

BottomNavigationBarType
Current
Proposed

Fixed

Shifting

Note:

This PR involves visual changes.
This PR does not affect the API in any way.

Updated goldens for bottom_navigation_bar_test https://github.com/flutter/goldens/commit/b15e2eef0dfe05d1aaa5077edd7f431aa168e260
Closes https://github.com/flutter/flutter/issues/23178

I updated the PR to point to the latest goldens.

Closing in favor of https://github.com/flutter/flutter/pull/27698/, which, rather than make a visually breaking change that takes away the old functionality, expands on the BottomNavigationBar API and allows for several requested features in addition to the behaviors described here.


Setup virtual iridium

Satellite hardware emulation.
Description

Emulates the network data flow from Local Transceiver <-> Remote Transceiver.

Serial communication
HTTP communication

Eliminates the need for a separate mock Local/Remote Transceiver implementation
See https://github.com/UBCSailbot/network_systems/pull/26 for a the script that automates the process of running virtual iridium

Verification

See https://github.com/UBCSailbot/network_systems/tree/virtual-iridium-setup/scripts#run-virtual-iridium

Note: This PR modifies the workflow to exclude the virtual_iridium repository in lint checks because it's a legacy codebase made for Python2. Refactoring it for Python3 is not worth the investment.

Are any infrastructure changes required to communicate with the actual satellite? If so, does this PR address this?

We need infrastructure to configure the serial port to communicate with the actual satellite. This PR does not address it.


PlayerZero Web Docs (Deploy)

Docs Commit for PlayerZero Web
Insert actions block

Proposed changes

Merge timing

Related issues (optional)
Duplicates #4135

Thanks @markzegarelli 🙌 !
I missed the actions block part

These changes look great, thanks @stayseesong
@markzegarelli can you accept them? I think since you're the PR author, I can't accept the suggested changes.
Also happy to go in and make the changes directly on the file itself if faster.

@stayseesong @markzegarelli is there anything else to be done on our end before the deploy?


[Enhancement] compatible with old cn

Fixes #issue
maually backport for pr： https://github.com/StarRocks/starrocks/pull/32084
What type of PR is this:

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[x] Yes, this PR will result in a change in behavior.
[ ] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto-backported to the target branch

[ ] 3.2
[ ] 3.1
[ ] 3.0
[ ] 2.5

[FE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

[BE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)


Add features content to main page

Add features YAML file with placeholder content.
Add real content to that file.

Hood benchmark comparison:
:warning: Decoding (Threshold:<PHONE_NUMBER>331772)

Benchmark
Value

master_benchmark
11286.065251733136

helios_benchmark
11165.705179515353

:heavy_check_mark: Parsing (Threshold:<PHONE_NUMBER>932287)

Benchmark
Value

master_benchmark
21987.79566335548

helios_benchmark
22101.854546688155

@MaureenElsberry I would like your lang review here

Could we merge this then? :thinking:


Added DotupBashSettings

DotupBashSettings - Script to load and save settings (Key-Value Pair) from/to files

Thank you for submitting this entry - I will be closing this because it does not fit the requirements of awesome-bash entries. Specifically, it does not have a minimum of 50 GitHub stars.


Possible to run dart scripts standalone?

I'd like to distribute a CLI tool written in dart to systems that do not have the Dart SDK installed. Is it possible to ship a prepackaged Dart SDK or something with it so it can run as intended?

No, it is not (directly) possible. I can close as a duplicate of #27596.
(The other option is copying what dart-sass does: https://github.com/sass/dart-sass#standalone)


fix bug of remote_podspec resource copy

Issue: #3
Description
The reason for this bug is that all copy behaviors assume that the podspec file and related resources exist in the same path, but the remote podspec file does not meet this situation, so any copy behavior will produce errors or invalid results.
Idea

add a temporary directory to download all files described by remote podspec, the path method used before when accessing resources during the construction process is podspec_dir, I changed it to pod_source_dir,it can map the path according to local or remote.
All pods will be treated as local pods after the download is complete
I once thought about whether this problem can be handled in the copy process, but I think it will make the processing of the copy process more complicated, but the current modification puts the processing in the early stage, this will make the subsequent processing flow easier.

@dnkoutso Hi，can you review it?
maybe I should make some changes, I want to hear your opinion.