bad interpreter

I only get an exception like "bad interpreter"

bash: /usr/bin/snoo: node: Defekter Interpreter: Datei oder Verzeichnis nicht gefunden

What to do?

@Hans-Maulwurf install node >= 7.4.0. :-)

node -v
v7.5.0

that's my output :/

@Hans-Maulwurf just updated something. Could you please git pull / npm i the latest version and try again?

now i get

/usr/bin/env: „node --harmony“: Datei oder Verzeichnis nicht gefunden

Could you run the following command in your terminal?
$ /usr/bin/env node --version
v7.5.0

v7.5.0
using arch linux

I got it working now. It seems it's the way you call node, I changed the first line of cli.js to

#!/usr/bin/node --harmony

and now it's working :)

From what I know #!/usr/bin/env node is the suggested way, as the node binary doesn't necessarily need to be under /usr/bin/. So for users that installed node into e.g. /opt, your solution would not work as well.
I'm really wondering how come that when you run /usr/bin/env node manually it works, but when your shell interprets the shebang statement it apparently can't find it anymore. That's really weird.


Connection broken in View mode

Describe the bug
Connection broken
Looks like a new Service Worker was installed by your browser when it shouldn't have. Refreshing the page should fix this issue. this issue is facing when I want to open side view of web container [ project : Node Js]
If this issue persists, please file an issue.

Link to the blitz that caused the error
https://stackblitz.com/edit/stackblitz-starters-tmcieb?description=Starter project for Node.js, a JavaScript runtime built on Chrome's V8 JavaScript engine&file=index.js,src%2Findex.html&title=node.new Starter
Steps to reproduce

Open project
Open side view in web container
Make changes in files
then reload the side view
this error is showing.

Expected behavior
Expected behaviour that I want that show the run in side view without any problem.
Parity with Local

[X] I have run the project in my local machine and I could not reproduce the issue.

Screenshots

Platform

OS: [e.g. macOS, Windows, Linux]
Browser: [e.g. Chrome, Safari, Firefox]
Version: [e.g. 91.1]

Additional context
nothing

Hey @Prana2580! Sorry for the inconvenience.
We are aware of this issue and have a plan for a better fix that should get rid of that screen entirely.
I'm going to close this issue as this is already tracked in #1358

Thanks


Add support for privateGPT

PrivateGPT is an AI project that allows To Interact with your documents using the power of GPT. This is the software behind the Mozilla's experimental MemoryCache AI. It works locally, so it's privacy friendly and secure. It will help with finding information from large documents and summarize them.
Reference:

PDFgear Copilot

Sorry, I forget to add links of the project.
Repo: https://github.com/imartinez/privateGPT
Docs: https://docs.privategpt.dev/
A plugin of PrivateGPT would be preferable. PrivateGPT is OpenAI API compatible. You can make it work from your company server.

With the release of new AI plugin, you should add documentation or wiki of free online and local AI resources. And also a tutorial on how to set up local LLM instances.


Create base theme provider tag

I've decided to not create the provider tag anymore. Although it looks like the right approach, using import is much cleaner and gives better control of where the developer desires to add the import.


SingleMediaEditor doesn't work with JSON object field type

Hey, I'm trying to use the SingleMediaEditor in an custom contentful extension with a field type that is JSON object but it throws the following error:
Uncaught TypeError: value.sys is undefined
    SingleReferenceEditor SingleReferenceEditor.tsx:84
    render FieldConnector.ts:138
    React 16
    parcelRequire<["index.tsx"]</< index.tsx:29
    j cf-extension-api.js:1
    promise callback*parcelRequire<["../node_modules/contentful-ui-extensions-sdk/dist/cf-extension-api.js"]</</j< cf-extension-api.js:1
    parcelRequire<["index.tsx"]< index.tsx:28
    newRequire src.f69400ca.js:47
    parcelRequire src.f69400ca.js:81
    <anonymous> src.f69400ca.js:120
SingleReferenceEditor.tsx:84:12
The above error occurred in the <FieldConnector> component:
    in FieldConnector (created by ReferenceEditor)
    in Constate (created by ReferenceEditor)
    in ReferenceEditor (created by SingleReferenceEditor)
    in SingleReferenceEditor (created by SingleMediaEditor)
    in SingleMediaEditor
    in div (created by Form)
    in form (created by Form)
    in Form
    in Unknown

Consider adding an error boundary to your tree to customize error handling behavior.
Visit https://fb.me/react-error-boundaries to learn more about error boundaries. react-dom.development.js:19527:12

That is here: https://github.com/contentful/field-editors/blob/3dc7130a751de690903c572edfcdfdf3587b57bf/packages/reference/src/common/SingleReferenceEditor.tsx#L84
Here's the sample app code:
import * as React from 'react';
import { render } from 'react-dom';
import { init, FieldExtensionSDK } from 'contentful-ui-extensions-sdk';
import { GlobalStyles } from '@contentful/f36-components';
import { Form } from '@contentful/forma-36-react-components';
import<EMAIL_ADDRESS>import { SingleMediaEditor } from '@contentful/field-editor-reference';

export const App = ({ sdk }: { sdk: FieldExtensionSDK }) => {
  console.log('sdk', sdk);

  return (
    <Form>
      <SingleMediaEditor
        viewType="card"
        sdk={sdk}
        parameters={{
          instance: {
            showCreateEntityAction: true,
            showLinkEntityAction: true,
          },
        }}
      />
    </Form>
  );
};

init(sdk => {
  render(
    <>
      <GlobalStyles />
      <App sdk={sdk as FieldExtensionSDK} />
    </>,
    document.getElementById('root')
  );
});

{
  "devDependencies": {
    "@babel/core": "7.12.3",
    "@babel/plugin-transform-runtime": "7.12.1",
    "@babel/preset-env": "7.12.1",
    "@babel/preset-react": "7.12.1",
    "@contentful/contentful-extension-scripts": "0.21.0",
    "@contentful/eslint-config-extension": "0.4.3",
    "@types/jest": "26.0.15",
    "@types/react": "16.9.56",
    "@types/react-dom": "16.9.9",
    "@types/webpack-env": "1.15.3",
    "contentful-cli": "1.4.48",
    "cssnano": "4.1.10",
    "eslint": "7.12.1",
    "typescript": "4.0.5"
  },
  "scripts": {
    "start": "rm -rf build && contentful-extension-scripts start",
    "build": "rm -rf build && contentful-extension-scripts build",
    "lint": "eslint ./ --ext .js,.jsx,.ts,.tsx && tsc -p ./ --noEmit",
    "test": "contentful-extension-scripts test --env=jsdom --watch",
    "test:coverage": "contentful-extension-scripts test --env=jsdom --coverage",
    "deploy": "npm run build && contentful extension update --force",
    "configure": "contentful space use && contentful space environment use",
    "login": "contentful login",
    "logout": "contentful logout",
    "help": "contentful-extension-scripts help"
  },
  "resolutions": {
    "parcel-bundler": "1.12.3"
  },
  "dependencies": {
    "@contentful/browserslist-config": "^2.0.0",
    "@contentful/field-editor-date": "^1.0.1",
    "@contentful/field-editor-reference": "^2.21.2",
    "@contentful/forma-36-fcss": "^0.3.4",
    "@contentful/forma-36-react-components": "3.100.2",
    "@contentful/forma-36-tokens": "^0.11.1",
    "contentful-ui-extensions-sdk": "4.3.1",
    "react": "16.14.0",
    "react-dom": "16.14.0"
  },
  "browserslist": [
    "last 5 Chrome version",
    "> 1%",
    "not ie <= 11"
  ]
}

Changed it into an app instead but I get the same issue. Perhaps the problem is the content type that I'm using? Doesn't it support the JSON object content type?

Seems to be working fine with Text and Rich text content types.

Hey @drager, how did you solve the issue? I'm facing the same limitation.

I have the same issue, still looking for a solution.

I didn't need to fix it anymore. I went and used an other field type. But my pr ☝ got it working for SingleMediaEditor.

Hi @drager - any plans to update your PR? Also experiencing the same issue :)

I have the same issue, also looking for a solution.


add support for popout windows by default

Is your feature request related to a problem? Please describe.
I am working on a pixel-art game with a very low resolution, so the high-res panku console windows take up a lot of space when overlaid onto my game. It's also cumbersome to drag them around to reveal the little "popout" button - is there a config setting somewhere I can toggle that makes the console windows default to their own separate OS windows?
Describe the solution you'd like
A project setting or config resource to make console windows appear outside of the game window by default. If this setting is toggled to "true," then closing an OS window with a console feature should not restore that feature to the main screen overlay.
It would also be nice to have an option to specify x/y coordinates and size for where each window should appear (similar to the project settings > display > window > initial position/window width override/window height override options that can be used for the main window)
Describe alternatives you've considered
Manually adding/modifying the script directly in the addons/folder that will force console elements into the positions I want on startup. This would require a bit of digging into how the plugin works and would be cumbersome to update when needed
Additional context
Add any other context or screenshots about the feature request here.

Sorry for the late reply, I'm working on it.


Make a release of seller App UI and Bundle the app in OIAB

Make a release of UI and Bundle the app in OIAB.
Include instructions to bring up the UI in OIAB to validate  the seller App and demonstrate order processing ..

App is added to OIAB - done
Release 0.0.1 is created - done


yiq

Signed-off-by: zoetrope<EMAIL_ADDRESS>

haha, well, that's a good thing.
I don't think I should merge it here, but maybe have a link to your repo.

Added it here: https://github.com/fiatjaf/awesome-jq

@fiatjaf
I'm sorry. This is my mistake.
Thanks for adding the link!


UI/UX adjustments

Streamlining intro, moving design principles to "contribute" section

Thank you for your feedback! I agree with you and will open a new PR without changes in the headings. :)


[tooltip] replace static images with gifs

Usage
-Below are the proposed animations to include in the tooltip usage documentation.
This would replace tooltip_usage_1.png

This would replace tooltip_usage_8.png

looks good john! thanks for doing this. a few edits.
since tooltips are displayed only on hover or focus (the live demo is showing v10 and not v11—i need to open an issue for this), there would not be a focus state in the first image. it would only need to appear on hover.
since there is no mouse in the second image, i think that it would be fine to keep the focus state as if you were using a keyboard. but the focus state would remain active until focus away from the tooltip. so it should be present when the icon has focus and gone when there is no focus.

no problem! here's v2 of tooltip_usage_1

and here's v2 of tooltip_usage_8.  let me know if you need any additional edits.


Update cheatsheet.md

Hey @mkourany92, we were asked not to review PRs without CLA signed.
Could you follow above instruction to sign the CLA so that we can move forward?

/assign

/close

Hi @mkourany92, are you still interested in contributing Kubernetes website?
Please let us know if there are any problem about signing CLA.

@mkourany92 👋🏻 Please feel free to /reopen when you're ready to sign the CLA.
/close


[BUG] github.com cannot find package "github.com/gogf/gf/text/gregex"

Bug Description [describe the bug in detail]
How to reproduction [describe the steps how to reproduce the bug]
Expect [describe your expect result]
Reproduction code [here to show your codes or examples]
Versions

GoAdmin version: [e.g. 1.0.0]
golang version
Browser
OS [e.g. mac OS]

Others [screenshots or others info here]

go get -u -v github.com/gogf/gf
https://goframe.org/index


Fix links in READMEs

This change fixes a couple of links that were recently broken.

Thanks @cesarzc. Since there are additional links in other repos that appear to be broken let's wait until we hear back from the content team on what changed and if there is a link mapping we can use. Otherwise we'll need to do this manual search across all repos.

Closing since it is no longer needed.


Add Validators detailed view

@hoffmannjan commented on Wed Jan 25 2023
So now we have only peers detailed view

And on main page we have some info about validators which is possible to be shown on separate screen:

Maybe we can change it like on this sketch?

cc: @megan-demit

@megan-demit commented on Wed Jan 25 2023
we could keep the Peers block and create a Validators block, to keep them separate, or we could do what you suggested. I think either would be fine.

@megan-demit commented on Wed Feb 08 2023
made the changes to the figma file, reflected in this ticket

@gyroflaw commented on Thu Feb 09 2023

made the changes to the figma file, reflected in this ticket

Also please create a new validator page design.

@megan-demit commented on Thu Feb 09 2023

@RitaMAllenCA @hoffmannjan @caspersteve if this seems appropriate we can add a new ticket for me to do this

@hoffmannjan commented on Mon Feb 13 2023
@megan-demit we can discuss next steps on a meeting today :)

The goal of this task is to modify the main page widgets and split the peers / validators into separate views.


Remove hard dependency on GetQueuedCompletionStatusEx

libuv already works without that API since 153ea114fff672b9c621a5d2bb13cea667b4499e, but still had it as a hard requirement in the import table.
This code uses the the pGetQueuedCompletionStatusEx function pointer instead, hence it also works on systems that don't export GetQueuedCompletionStatusEx.
This simple fix improves compatibility of libuv with ReactOS and Windows XP (latter using Vista+ compatibility libraries like https://github.com/MyTDT-Mysoft/DllCompat)

CI: https://ci.nodejs.org/view/libuv/job/libuv-test-commit/1862/

@ColinFinck Your PR is against master but libuv releases are cut from the v1.x branch. I assume you want to see this show up in a release so can you retarget your PR?


Understanding Variable Response Times from a Local Mistral Model

Hello,
Thank you for the great package, I have been exploring it, and considering using this as a way to host an LLM on my companies Linux server. Our overarching goal was to move away from using the OpenAI API, due to its long and varying response times from the API, and host an open source LLM on our own machine. It seems that Ollama may work for this use case.
However, after doing some initial prompts with the Mistral model, I started to notice the response times were not consistent. I am currently running the code on a CPU on our Linux server (so I did not expect fast response times); however, I did expect consistent response times. From what I understand, the Ollama python packages uses the models that are downloaded to your machine, and therefore are running offline, on that machine, not in the cloud by a third party server (correct me if I am wrong here).
I was surprised to see my first initial responses have around 60 second response time, and then that response time drop down to 10 and 7 seconds, when using the exact same prompt. This behavior is reminds me of cold starts when using serverless infra, but again, I am assuming that this is a local offline model.
I also waited a few minutes, and re ran the script, and got the initial 1 minute response time, then 5 second response times again, so it seems like there some type of initialization or cold start?
Here is the code (hiding the prompt), simply taken from your README.

import ollama

s = time.time()

response = ollama.chat(model='mistral', messages=[
  {
    'role': 'user',
    'content': TEST_PROMPT,
  },
])
print(response['message']['content'])
e = time.time()

Response for exact same input:
(AI) paul@deva-companion-python:/python_backend/AI$ python3 ollama_test.py
 Hi Pippy, this bedroom has so many interesting things. What catches your eye?
Response time: 65.01464176177979
(AI) paul@deva-companion-python:/python_backend/AI$ python3 ollama_test.py
 "Hi Pippy, this bedroom has so many interesting things. What catches your eye?"
Response time: 5.180686712265015
(AI) paul@deva-companion-python:/python_backend/AI$ python3 ollama_test.py
 "Hi Pippy, this bedroom has so many interesting things. What catches your eye?"
Response time: 5.081787586212158
(AI) paul@deva-companion-python:/python_backend/AI$ python3 ollama_test.py
 Hello Pippy! I'm glad you're here. This bedroom has so many interesting things. What catches your eye?
Response time: 6.901242017745972

Some Questions

Is the variable length of response times from an LLM (given the same input) considered normal behavioral?
Why such large differences dropping down from 1 minute to a few seconds?
Is there some type of initialization or cold start happening for the first call? If so why?
Is there some type of caching mechanism with mistral causing this?
Is this due to the random nature of a generative model? (I am more familiar with deterministic models, which have consistent inference times given the same input). (I doubt this, because the varied response tiems are consistent, meaning the first call is 60 seconds, then after that about 5-6).
Am I wrong in my assumption that the python package runs offline?

Thanks again,
Paul

The high timing on the first run is because Ollama needs to load the model into (GPU) memory. Subsequent requests take roughly the same amount of time. There will still be some variance since the outputs will be different. You can set options={'temperature': 0} for reproducible result and more consistent timings.
By default, the model gets unloaded after 5 minutes. Once the model gets unloaded, the next request needs to load the model back into memory. You can change this behaviour by setting keep_alive, e.g. ollama.chat(model='...', messages=[...], keep_alive=...). keep_alive can be either a duration (60s, 5m, 1h) or a number (in seconds). Negative keep_alive, -1, will keep the model in memory indefinitely

Thank you for the response. That hopefully will resolve the loading/ cold start issue. I am still trying to understand how these different parts work together.
I was wondering if you could help me with this question that I originally proposed:
"From what I understand, the Ollama python packages uses the models that are downloaded to your machine, and therefore are running offline, on that machine, not in the cloud by a third party server (correct me if I am wrong here)."

From what I understand, the Ollama python packages uses the models that are downloaded to your machine, and therefore are running offline, on that machine, not in the cloud by a third party server (correct me if I am wrong here).

This is mostly correct. This library implements a Python interface to the Ollama API. As such, it requires a running Ollama instance which can be local (same machine) or remote (hosted by you or someone you trust). The default configurations assume local (<IP_ADDRESS>:11434 to be precise). This Ollama instance is responsible for downloading and running models.


How to safely delete a branched frontend that uses a shared backend?

Amplify CLI Version
10.6.1
Question
Pre-Christmas we set up a new front end (called prod-2) by branching our existing production one in github. The CI will build this if we push just like any other branch. This branch was set to use an existing backend (I think this might have been done via Amplify Console rather than the CLI).
Turns out we don't need that new prod-2 frontend anymore and I want to delete it but I'm a little scared that it might delete the backend too...which is the live production backend! I've removed the backend link in the console for this frontend:

There doesn't seem to be much advice or feedback or reassurance in the console about what will happen if I delete the frontend...will it kill off the backend too?
Under the "General" menu I can select the frontend and then in the Actions drop down select "Disconnect branch" which I think is the way to go about it. Or should I be doing this via the CLI? As I'm unsure if we set this up with the UI or not I'm not sure. I was thinking delete it in the UI should be fine?

When trying to "give it a go" at using the disconnect I always back off at this screen, to me its unclear if it will delete anything I don't want it to:

Can someone give me some pointers to smooth my nerves over about the best/correct way to remove this frontend?

Hey @PeteDuncanson :wave:

Under the "General" menu I can select the frontend and then in the Actions drop down select "Disconnect branch" which I think is the way to go about it. Or should I be doing this via the CLI? As I'm unsure if we set this up with the UI or not I'm not sure. I was thinking delete it in the UI should be fine?

Yes you are correct. From this menu we are able to disconnect the branch, which will remove the frontend and build history, but leave the backend environment untouched.


Document Work for Drive Subsystem

Similar to what #183 is doing.

Driving documentation. Feel free to add anything important.
Link to Doc

I recently updated some documents about how the steering should be implemented and what files we will primarily be working around.


Show sign up/attendee list

in the list you could maybe link to people's profile, or have a button to quickly add as a friend (then we can use the untappd app during orlando to see what people are doing)

Version 1 will be the profile link and people can add from there.
Version 2 will use the Untappd API to add them as friends.

@groovecoder nice work!


Post quantization input scaling / offset

When processing a network model to run on the DPU, can/will the quantization step apply any scaling or offset to the input nodes ?
I'm having troubles with a model that takes an image as an input (range [0; 255] when the DPU API uses int8_t [-128; 127]). When dumping the layers using vai_q_tensorflow dump it seems that all the values are divided by 2 (+1 for odd numbers).
Without applying this extra (hidden) scale in my app, the results from DPU and the dump are not the same.
If there is such a scaling, where can I find information on that ? If not, am I doing something wrong ?

Hi @qukhan ,  the dumped value is just the result of float value that is processed by quantize and dequantize.   See
https://github.com/Xilinx/Vitis-AI/blob/master/Vitis-AI-Quantizer/vai_q_tensorflow/tensorflow/contrib/decent_q/kernels/fix_neuron_ops.h#L179    function dp_quantize_cpu
And when using vai_q_tensorflow dump,  you can set "--dump_float 1" to dump the float tensor data, and check the difference between origin input data and input data after quantize-dequantize.

Hi, thanks for your reply.
It seems that the dpuGet[Input/Output]TensorScale functions do not work properly. They always return 0.

Hi @qukhan  can you indicate where is dpuGet[Input/Output]TensorScale.  I don’t remember this function, can you tell me where the function is?

These are functions of the advanced API. You'll find the code of dpuGetTensorScale  here.
https://github.com/Xilinx/Vitis-AI/blob/master/mpsoc/vitis_ai_dnndk_src/n2cube/src/dpu.cpp#L1853-L1858

Hi, @qukhan
Could you help check which version of N2Cube you are using?
We have a bug related to dpuGetTensorScale but we fixed it in Vitis-AI 1.2 version.

Hi @qukhan
It has been a long time and VAI1.2 has been released. So I close this issue. If you have any problems, please open a new issue. Thank you.


Please consider fixing issues detected by repository checker

Notification from ioBroker Check and Service Bot
Dear adapter developer,
I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter janitza-gridvis for common errors and appropiate suggestions to keep this adapter up to date.
Please see the result of the check below.
ioBroker.janitza-gridvis
   -

:thumbsup: No errors found
WARNINGS:

[ ] :eyes: [W040] "keywords" within package.json should contain "ioBroker"
[ ] :eyes: [W115] "common.tier" is required in io-package.json. Please check https://github.com/ioBroker/ioBroker.docs/blob/master/docs/en/dev/objectsschema.md#adapter.
[ ] :eyes: [W184] "common.title" is deprecated and replaced by "common.titleLang". Please remove from io-package.json.

Please review issues reported and consider fixing them as soon as appropiate.
Warnings reported by repository checker should be reviewed. While some warnings can be considered as a suggestion and be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.
Feel free to contact me (@iobroker-bot) if you have any questions or feel that an issue is incorrectly flagged.
And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.
your
ioBroker Check and Service Bot
@mcm1957 for evidence

All changes done

Thanks for processing and closing this issue.
I will recheck for new issues later. So it's no problem if this issue has been closed premature.
You may start a new check at any time by adding the following comment to this issue:
@iobroker-bot recheck
Please note that I (and the server at GitHub) have always plenty of work to do. So it may last up to 30 minutes until you see a reaction. I will drop a comment here as soon as I start processing.
Feel free to contact me (@iobroker-bot) if you have any questions or feel that an issue is incorrectly flagged.  Let's work together for the best user experience.
your
ioBroker Check and Service Bot


Select example clips the dropdown

It didn't begin well for me, first example seems to be working incorrectly.

Open http://github.hubspot.com/select/docs/welcome/
Shrink the browser vertically to about the size in the screenshot and open the dropdown.
Notice that it's not possible to select the topmost items because they are clipped and one can't scroll there.

Lot's of people view the web from what is basically a mail slot sized hole, I know it's ridiculous, but that is the way it is.
I think it should not expand the floating area topwards out of the window (since one can't scroll there).

Darn it, this is wrong repo, apologies. Created a new issue in right repo: https://github.com/HubSpot/select/issues/48


First gapic bigtable gen

Copied over from api-client-staging/master. Directory structure changed to match google-cloud-java convention.

PTAL

You need to update the room pom to include this in the build.

Added the requisite changes to the pom.xmls.
PTAL

Fixed up the pom.xml. PTAL


Reset to configured offset instead of latest on ErrOffsetOutOfRange

In https://github.com/bsm/sarama-cluster/commit/b8422e8c#diff-5ca1e1d791806b5c07f0f2d070e642f9R24 it looks like this was changed to -1, which if I'm interpreting correctly, is the latest offset: https://github.com/Shopify/sarama/blob/68920ff1be3bbd31449ab1e2c255c50cedeb755c/client.go#L69-L80
If sarama's config.Consumer.Offsets.Initial is set to to sarama.OffsetOldest, then wouldn't we also want that when recovering from ErrOffsetOutOfRange?
I'll fix the test if there's agreement on the change.

Not sure if that's needed the info.Offset is just to keep track of what's being marked as successfully processed. Setting it to -1 just resets it to it's default state


⚠ Bofrost.nl has degraded performance

In 05fa6ae, Bofrost.nl (https://www.bofrost.nl) experienced degraded performance:

HTTP code: 200
Response time: 823 ms

Resolved: Bofrost.nl performance has improved in 7fd67c9.


Add types and roles to data in the inverted index

Add the types and roles to the inverted index and consider them during search when they are provided in the query.

Types in Table 2:
https://sbolstandard.org/wp-content/uploads/2016/06/SBOL2.3.0.pdf
Roles are defined in this OBO file:
https://github.com/The-Sequence-Ontology/SO-Ontologies/blob/master/Ontology_Files/so-simple.obo

Added in #68 .


Abstract methods in command execution and change to proper name

Abstracting Code to improve SLAP
Especially on Edit and Delete Command related classes, since multiple authors have worked on it
I think this PR can hold after v1.5rc as it is a code quality related PR

Refer to #214


Fix gizmos regression

Objective

Fixes #14142

Solution

Make sure a regression test is written on this case that fails for the current code base but works with the suggested patch linked in the aforementioned issue. After this is confirmed to be working, apply the patch.

Testing

Run the regression test in both contexts, outputs were as expected.

Feel free to nit this, wondering how the example based tests are set to run in CI...

So, these tests will get run when we attempt to merge, but I think that in this particular case we can use a standard unit test (without any rendering) to check for regressions. IMO just stick it in the circles.rs file.
That will be more straightforward, be run as part of our ordinary CI / local calls to cargo test and use less compute.

Can gizmos be run headless? I tried to do this and could not get it to stop complaining about not having the shader asset present (i am probably missing something simple, i tried to look for other examples in the other unit tests and the best i found were those end to end tests

I don't think we actually need to generate any gizmos to test this. Can we not just call gizmos.sphere without actually running the system?
I'd prefer to get this merged without a regression test over adding an integration test TBH.

I just checked to see if I could run it headlessly and it appears as if spawning a gizmos struct requires access to create a  Deferred<'s, GizmoBuffer<Config, Clear>>, which seems can only be created through ECS means. This is not unexpected, but means that I will sadly have to remove the test or refactor a lot of code I am not yet qualified to touch.


Allow to pass request headers to action call

Hello @icebob,
I need in my project to pass request headers into context of call action so I created a small change that allows to put them there. I'm aware that this change missing tests (small but it always good to have some automated test to check if it's broken anything) Please tell me what you think about this, cheers!

Coverage decreased (-2.1%) to 95.498% when pulling 8f5cdc1bfd67847fbf7ea3ea87f982070b8098c2 on czolnowski:allow-to-pass-request-headers into 767013ddf1bc569bbcc49529b9c42041c7c97c0c on ice-services:master.

Good idea, but I prefer to use only one property for this.
So the variable name keep as route.attachHeaders. And if it is falsy (undefined, null, false) it won't do anything. If it is an Array, copies the header keys. Could you modify the code according to it?

Btw, I think it would be better to add header to ctx.meta. Because it is transfered in sub calls.
So my idea:
routes: [{
	attachHeaders: [
		"apikey",
		"accept",
		"accept-language"
	]
}]

and it will load it in the Context meta:
ctx.meta = {
    headers: {
   	 apikey: "123123",
   	 accept: "html",
   	 accept-language: "..."
    }
}

And you can access in actions:
actions: {
	list(ctx) {
		console.log(ctx.meta.apikey)
	}
}

What do you think?

Hi @czolnowski!
I implemented a common solution which cover your problem too.
More info: https://github.com/ice-services/moleculer-web/releases/tag/v0.2.3


Print Memories based on the @external attribute

Rather than printing the internal state of all the memories, we should print only those with the @external attribute to more closely align with the verilator behavior.
Should we emit the internal state of all registers? Or do they also require an annotation?

Rad. I think probably just the memories, because AFAIK that's all the Verilator backend can expose too?
(It seems nice to have a flag to optionally dump all state, or perhaps just the registers, as an option.)

A flag for the registers makes sense, it's useful to be able to inspect their state in some of the tests


fix(revit): type mapping null reference

As reported here: https://www.notion.so/speckle/ImportTypes-Failed-ba359f3d6c8a43ccb0027f5ecce5591e?pvs=4
The revitDocumentAggregateCache was never initialized or passed to the FamilyImporter class, this caused a null reference exception. Not sure how this was working before or how it broke?

I thought I had caught all of these. 🙇🏼♂
In general, we shouldn't assume interfaces that are not part of the constructor will be initialised by the time anybody uses them, and conversions should be able to run without caches of any kind.
I'll get on a fix for this ASAP


Type intersection details not rendered

Expected Behavior
I have the following types :
/**
 * Object defining a spherical position
 */
export type Position = {
  longitude: number;
  latitude: number;
};

/**
 * Object defining panorama and animation options
 */
export type PanoramaOptions = Partial<Position> & {
  /**
   * new zoom level between 0 and 100
   */
  zoom?: number;
  /**
   * duration of the transition between all and new panorama
   */
  transition?: boolean | number;
  /**
   * show the loader while loading the new panorama
   * @default true
   */
  showLoader?: boolean;
};

I expect the PanoramaOptions to at least list its three additional properties.

Actual Behavior
Instead absolutely no detail is rendered.

The same behavior is observed with Position & { ... } (supposing Partial throws the parser off) or with an union type Position | { ... }
If that matters I am parsing ".d.ts" files, not typescript source.
Environment

Typedoc version: 0.22.7
TypeScript version: 4
Node.js version: 14.17
OS: W10

Duplicate of #1519, something I want to do, but haven't gotten around to implementing yet


Windows CI: Fix unit test failures

Signed-off-by: John Howard<EMAIL_ADDRESS>Moves TestLoadDaemonCliConfigWithDaemonFlags introduced in #20476 to _unix_test.go as it uses Linux specific fields causing unit test failures on the windowsTP4 context such as shown below:
00:04:05.367 # github.com/docker/docker/docker
00:04:05.367 docker\daemon_test.go:56: c.EnableSelinuxSupport undefined (type *daemon.Config has no field or method EnableSelinuxSupport)
00:04:05.367 docker\daemon_test.go:74: loadedConfig.EnableSelinuxSupport undefined (type *daemon.Config has no field or method EnableSelinuxSupport)

LGTM

LGTM 🐮


Implement RTC

The RTC is a bit strange due to the backup power domain. I tried varying amounts of integration with the standard RCC, REC, PWR methods, but the implementation and semantics conflicted. Instead I added Backup to manage the backup power domain. Right now it's just the RTC but hypothetically it could help manage the backup SRAM and the LSE.
I started out with a minimal Date/Time implementation but found myself implementing more and more functionality so I replaced it with the time crate. It has a no_std mode but always requires an allocator. This isn't an issue for me but I might re-introduce the simple Date/Time and maybe genericize functions that take one of those as an argument.
I moved to the chrono crate since it doesn't require allocation.
Interested in any feedback you have.
Blocked on:

[x] https://github.com/time-rs/time/issues/280
[ ] stm32h7 0.13 (https://github.com/stm32-rs/stm32-rs/pull/446, https://github.com/stm32-rs/stm32-rs/pull/445)

Considering that many peripherals such as for example the ADC do allow multiple clock sources in theory (as of now we limited it to one, but the clock source is actually connected to a MUX we could configure if we so desired inside the chip) would it possibly make sense to have an enum (or a set of structs which implement some trait) which represents clocks we have available to us in general? Since I feel like if we were to actually fully expose the H7 as a Rust interface this is definitely a thing we need to have and reimplementing it over and over again wouldn't be beneficial.
An basic idea without thinking it too much through in depth:

Build structs that represent all of our clocks such as the LSI, LSE, HSI etc. etc. These structs would carry information such as the frequency but also more specialised things such as for example the bypass thing for LSI.

Possibly implement a way to represent divided clocks as structs, this could be easily done once const generics are a thing actually since we can then simply have a type Divided<CLOCK, DIV> with CLOCK being one of the clock structs mentioned from 1 and DIV being the divider as a const generic. However we don't actually have to wait for const generics since most clocks I've seen so far are usually divided by a multiple of 2 so we can probably get away with providing zero sized PhantomData structs for 2,4,8,16,32,64 and maybe 128.

For peripherals that do allow to configure which clock source is their input simply have a function argument of the type T where T is constrainted to implement a marker trait which marks a certain (possibly divided clock source) as usable for this peripheral.

This has the advantage of having a centralized representation of clocks we can use across the chip. Furthermore the Rust compiler as well as docs.rs can still easily tell the user which clocks are allowed for this peripheral:
docs.rs: Check who implementes the peripheral specific marker trait
rustc: If the type does not match, rustc will usually print implementations of the trait it has found for the user so they get docs as a compiler error so to speak.
The disadvantage is of course that we increase our type signature, function signatures etc. by a bit which is not at all an issue for me but I have talked to people that would rather prefer if we did not do that.
Any thoughts on this? Or am I just totally overthinking it at this point xD?

Since you didn't mention it, I'll point you to our existing facilities for changing peripheral clocks: https://docs.rs/stm32h7xx-hal/0.7.1/stm32h7xx_hal/rcc/rec/struct.Cec.html#method.kernel_clk_mux (I didn't know/remember this existed until I started working on the RTC). Looking at the implementing macro you can see that many peripherals have no clock mux, many have group clock muxes where they share a clock source, and some have individual clock muxes:
https://github.com/stm32-rs/stm32h7xx-hal/blob/e6da7dc7bf9cd9f85e4f84a980a94e8cbf18be34/src/rcc/rec.rs#L313-L404
I think it's a reasonable abstraction once you know it exists. I think it'd certainly be possible to improve with some typesystem things, maybe represent the tree-like structure better, but I'm a bit wary about the complication. I remember being a rust noob and finding such things very confusing, and rustdoc is not great at exposing them.
Back to the RTC, the reasons I didn't integrate with this existing clock system are:

The RTC RCC registers are completely different from every other peripheral. It took some ugly hacks to work which didn't seem worthwhile for just one peripheral, so I decided to split it out from the PeripheralRec struct.
The RCC initialization is designed around bringing up a blank-slate reset system. The LSE lives in the backup domain and thus isn't reset unless you reset the whole backup domain (LSE and RTC). There are also lots of specific requirements around configuring the LSE clock, backup domain write protection, and RTC, like you can only set the RTC clock mux one time per backup domain reset, and you can't enable LSECSS until after the RTC is using the LSE.
I didn't think that anything else used the LSE clock. Looking at the STM32CubeMX clock configuration tab (why doesn't the reference manual have a clock tree chart!?) now I see that MCO1, CEC, LPTIMs, LPUARTs, and UARTs all can use the LSE. However I think these use-cases are very rare (nobody has asked for them yet) and the RTC is a much more primary use-case for the LSE. I think it's reasonable to ignore that use-case for now given the implementation and interface complexities they'd introduce. There are many places in the HAL where we choose to support the common use-case at the expense of flexibility and implementability.

I can imagine a system where the LSE is moved into the Backup which is passed to RCC::freeze() which populates the lse_ck in CoreClocks so other peripherals can use it. The main issue is reset. LSE and RTC are reset together so they really want to be initialized together. If you can think of a good interface for this I'd love to hear it.

This is really useful! I haven't looked at it all yet, but looks reasonable so far.
I think implementing ResetEnable separately for the backup domain is fine, especially since the peripheral_reset_and_enable_control! macro is complicated enough already. The documentation already does a reasonable job at describing which clocks are possible for each peripheral, although it's certainly possible to improve it more.
Indeed it would be nice to share the LSE state with the CCDR struct somehow, but agreed that's not essential for this PR.

Thanks for the review! I'll leave this as draft until stm32h7 0.13 then I'll rebase.

Actually it may be a while until 0.13 so I'll revert to the uglier implementation that works with the undocumented registers for now

Could you add the new rtc feature gate to the CI please? It's here and here, see what https://github.com/stm32-rs/stm32h7xx-hal/pull/81 does for an example. Otherwise the example doesn't get built in CI unfortunately.

The example still doesn't work for me unfortunately. It actually needs to be
    loop {
        info!("Time: {}", rtc.time().unwrap());
        let date = rtc.date().unwrap(); // Added this line
        rtc.unpend(rtc::Event::Wakeup);
        asm::wfi();
    }

It appears to be due to RM0433 Rev 7. 46.3.9 Third Paragraph. The read to DR needs to come last. One solution could be a dummy read of DR after every read of SSR or TR (there are several functions with these reads).

The first two paragraphs also talk about the required frequency of pclk4. It would be nice to assert! if PCLK4 is less than seven times the RTC clock frequency (fRTCCLK). That could reasonably happen when using the HSE as a source.

I really should've tested the example after I made those changes, but I left my nucleo board at home... I'll get it working. Thanks for the review!

I think it's nearly there!
After the example is working, I'll finish reviewing it 👍

Reading through that section of the RM again I see a few options:

Fix the order of the shadow register reads and clear the RSF after every read like the RM says. This limits you to one read every RTC clock cycle which is probably 32KHz. I think that could be annoying or surprising for some applications that are trying to read the RTC often for timestamps, etc. and suddenly all their CPU is used waiting around for the RTC. Two solutions to that:
A. Return nb::Result and let the user do work while the RTC is not ready to read. This pushes the complexity to the user, and how many people are set-up to handle async operations properly right now?
B.  Read the whole time/date in each member function that reads any component, and store the result. Subsequent reads will check the RSF and if it's not set use the memoized value.
Disable the shadow register and read directly from the RTC TR/DR/SSR. You now have to read twice to make sure the registers didn't change during your read. "While BYPSHAD=1, instructions which read the calendar registers require one extra APB
cycle to complete." So that effectively quadruples the read time since we need to read twice and it takes twice (?) as long, not that it really matters.

It looks like both 1.B and 2 would work, but there's one more thing:

After waking up from low-power mode (Stop or Standby), RSF must be cleared by software.
The software must then wait until it is set again before reading the RTC_SSR, RTC_TR and
RTC_DR registers.

We don't support low-power mode in the HAL, though it's pretty common to use wfi(). We could implement some sort of callback system that tells the RTC when we wake up from sleep/standby; maybe there's a register we can read somewhere that will tell us.
But it would be so much easier to just disable the shadow register. I can't see any reason not to. RSF is convenient to wait for shift and initialization to complete but we can check those flags manually if we have to.

There were two additional issues which caused the example to not work:

RTC interrupts are routed through EXTI to NVIC, presumably so they can wakeup the core or D3. You need to enable the interrupts in EXTI as well. Thanks ST for not mentioning this anywhere at all.
The RTC_WKUP interrupt handler didn't unpend the interrupt so it just ran forever. 🤦♂

@richardeoin this should be ready for review again when you have the time.

Great, thanks for fixing up the example.
I think that disabling the shadow registers and reading directly (BYPSHAD=1) is a good solution. It does mean every read takes a little longer but it's worth it. Both to avoid blocking waiting for RSF to go high, and needing to do things on wakeup. (BTW for the example in release mode, I measure about 500 cycles for the rtc.data_time().unwrap() call in the interrupt. That's fine)
I just have one comment about enable_wakeup, otherwise this is ready to merge.

bors r+

@mattico What do you think of the rustfmt check in CI? Having consistent formatting is nice, and it means there should never be any formatting noise in diffs. However it's quite annoying when submitting a PR, unless you have rustfmt-on-save in your editor (a personable choice imo).
Could it be an optional check? Even better would be that bors runs rustfmt when merging the PR, but I don't know if bors supports that.

@richardeoin I like having the code consistently formatted and I think it's good to have a PR check.
The reason I have trouble with it is that I primarily develop stm32h7hh-hal in a submodule of my firmware project which uses nightly. The nightly rustfmt formats differently from the stable rustfmt that CI uses so I don't use format-on-save and need to remember to cargo fmt. I am not good at remembering :)


Italian translation tutte/tutto mismatch when closing all tabs

Windows Terminal version
1.17.1023
Windows build number
10.0.19045.2728
Other Software
No response
Steps to reproduce

Configure Windows Terminal to display in Italian.
Start Windows Terminal and open a second tab.
Click the close button of the window.
A prompt appears asking whether you want to close all tabs.

Expected Behavior
Matching number and gender.
Actual Behavior
The question is "Vuoi chiudere tutte le schede?", and below that, there are two buttons "Chiudi tutto" and "Annulla".
The word "tutte" in the question is feminine plural, but the word "tutto" in the button is masculine singular.
It seems strange that these do not match.

I'm sorry for the long wait! This is now tracked at MSFT-44562190.


The embedding model with vLLM backend does not have the “Embedding Only” tag

Model: intfloat/e5-mistral-7b-instruct

Environment

GPUStack version: main(b805d00)

Test Result: pass
Only embedding models based on the "Gemma2Model" and "MistralModel" architectures are supported now. https://docs.vllm.ai/en/latest/models/supported_models.html#text-embedding


Lstu ynh package correction

Needs some testing but:

works as public app
works as private app

I added a todo list in the README.

it's ok. let's merge. Really thanks. You are admin of this package too, I think. :)

You are admin of this package too, I think

Possible, but I don't like to merge on someone's work without his agreement if I wasn't involved before.

Don't worry. You are now a contributor of this package. :) You are admin but yes, doing PR is better.


Release new version

There have been some nice improvements and fixes since 1.1.11 was released.  It would be great if the release process could produce a new version!

It is very interesting that there haven't been a release since 1.1.11. The most misleading fact is that the README tells you to use pip for installation but pip actually installs  scikit-video 1.1.11 whereas the master git branch is ahead of 1.1.11, leading to confusing errors. So please either release a new version or mention this in the README.


Need libxml2-dev libxslt1-dev to build rails

Not sure which image your From ruby:2.2 stands for.  I suppose it would be the image build from here: https://github.com/docker-library/ruby/tree/master/2.2
Then I tried to build on top of which I've build with wheezy image, then I found the following patch was needed to finish building.
  diff -ub rails/Dockerfile Dockerfile
--- rails/Dockerfile    2015-05-26 16:18:13.650495822 +0800
+++ Dockerfile  2015-05-26 16:26:18.415989564 +0800
@@ -1,11 +1,19 @@
 FROM ruby:2.2

 # see update.sh for why all "apt-get install"s have to stay as one long line
-RUN apt-get update && apt-get install -y nodejs --no-install-recommends && rm -rf /var/lib/apt/lists/*
-
+RUN curl -sL https://deb.nodesource.com/setup | bash - \
+        && apt-get update \
+        && apt-get install -y nodejs --no-install-recommends \
+        && rm -rf /var/lib/apt/lists/*
 # see http://guides.rubyonrails.org/command_line.html#rails-dbconsole
-RUN apt-get update && apt-get install -y mysql-client postgresql-client sqlite3 --no-install-recommends && rm -rf /var/lib/apt/lists/*
-
+RUN apt-get update \
+        && apt-get install -y mysql-client postgresql-client sqlite3 \
+        && libxml2-dev libxslt1-dev --no-install-recommends \
+        && rm -rf /var/lib/apt/lists/*
 ENV RAILS_VERSION 4.2.1
+RUN gem install nokogiri -- --use-system-libraries
 RUN gem install rails --version "$RAILS_VERSION"

Given that the recommended usage for Rails itself is to add it to your project's Gemfile and use bundle to install it, the rails official image has been deprecated as of Jul 5 in favor of using the ruby image directly (see https://github.com/docker-library/docs/pull/503 for more details).
Sorry for the inconvenience!  Since the image will not be receiving anything besides minor maintenance updates (version bumps for example), we're closing out old issues accordingly.  Thanks!


Clearing a KeyboardDatepicker value opening the calender unlike KeyboardDatePicker.

I have added a clear button in both DatePicker and KeyboardDatePicker. The ideal behavior should be, the values should be cleared which is happening correctly in KeyboardDatePicker, but in the case of DatePicker, the calendar is opening on clicking the clear button.

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
The calendar is opening on clicking the clear button in DatePickerComponent.
Expected Behavior 🤔
Just the text field should be cleared, as happening in the case of KeyboardDatePicker.
I have reproduced the issue in the following code sandbox.
https://codesandbox.io/s/material-ui-pickers-usage-demo-8gu6h?file=/package.json

@sirajalam049 Do you have a reproduction with v4.0.0-alpha.7? We do no longer maintain v3.

@oliviertassinari , I tried, but there is an error in the alpha version, MuiPickersUtilsProvider is not exported from @material-ui/pickers. Then I went to the documentation and click edit, and saw all examples are using v3. So if I can have a basic running example of it in v4, then I could replicate the issue in that version.

@sirajalam049 try with https://codesandbox.io/s/wonderful-tereshkova-zrngh?file=/package.json


Kulfy: Watch thecoraltech.com

Kulfy requests the watch of the watch_keyword thecoraltech\.com. See the MS search here and the Stack Exchange search here.

thecoraltech\.com has been seen in 0 true positives, 0 false positives, and 0 NAAs.

Approved by Thomas Ward in Charcoal HQ


Possbility to override the default namin strategy of span names.

Currently the building of Span names are hard coded in  the span builder.
zipkin2.Span.Builder
    public Builder name(@Nullable String name) {
      this.name = name == null || name.isEmpty() ? null : name.toLowerCase(Locale.ROOT);
      return this;
    }

Imn a distrubuted world  not all using zpking as tracer. For having common naming strategy it cloud be very helpgul to make that area modifyable.

@suikast42 are you asking about...

using zipkin2.Span in code you control
using zipkin2.Span in code you use, but don't control (e.g. otel's java library)

maybe that library has a way to change it

zipkin's internal use of zipkin2.Span

the default would only apply for the rare case of a span with no name

I'll give you a link to one way people modify data after zipkin collected it when using elasticsearch https://github.com/openzipkin/zipkin/tree/master/zipkin-storage/elasticsearch#customizing-the-ingest-pipeline
I don't expect us to change the builder type itself as it is uncommon and surprising for a builder to take defaults externally.
However, but there's probably a way to help you with your problem. as we use issues for code, mind moving to https://app.gitter.im/#/room/#openzipkin_zipkin:gitter.im ?


thread_id is typed as a string but Sentry actually sends ints

Problem Statement
https://github.com/getsentry/sentry-go/blob/master/interfaces.go#L244
^This field, thread_id, is typed as a string but Sentry actually sends ints. This is blocking us from deserialising any event from Sentry.
This is the only issue with the modelling I've found.
Background:
We have the Android Sentry SDK set up in our app. We've got a Go webhook consuming alert events. These events cannot be deserialised currently because of this bug. Not sure if this problem is somehow specific to event_alerts coming from a JVM/Android project or not.
The original issue was raised here.
https://github.com/getsentry/sentry-go/issues/767
Solution Brainstorm
No response
Product Area
Issues

Already tracked here https://github.com/getsentry/sentry-go/issues/767


Clients cannot connect to server

Hello, I'm trying to run a Half Life 2 Deathmatch Server, in a Centos 7 box.
The image works well, and the server start successfully, but when trying to connect from the game, there's no response, and the server's console don't show any player trying to connect.
This is how I'm trying to run it:
docker run -it  --rm  -p 27015:27015/udp  --name "HL2" sourceservers/hl2mp 'srcds_run -game hl2mp -port 27015'
Don't know if there is something missing.
Thank you for any help.

@ggMartinez perhaps you can try adding a starting map using +map cvar.
srcds_run -console -usercon -secure -game hl2mp -port 27015 +map dm_lockdown -maxplayers 16 +sv_lan 0

and enter status command in the server console. Ensure those cvars match the server status.

That worked, thank you!

glad it worked for you. You can also try the preliminary docker-compose.yml example in #26


Makes properties that should remain unminified compatible with tools …

…other than rollup/terser
Fixes #1970.
Note, does not appear to impact build size at all.

Actually, can you revert the changelog.md changes and instead do npm run add changeset?


Make the Amazon SQS visibility timeout be configurable in Wolverine

See SqsListener.DeferAsync()

Irrelevant with recent changes.


www: Fix animation.

Fix animation on harp.gl website introduced by mistake in #1392 .

Codecov Report

Merging #1463 into master will increase coverage by 0.16%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1463      +/-   ##
==========================================
+ Coverage   56.31%   56.47%   +0.16%
==========================================
  Files         273      262      -11
  Lines       24484    24361     -123
  Branches     5490     5464      -26
==========================================
- Hits        13787    13757      -30
+ Misses      10697    10604      -93

Impacted Files
Coverage Δ

@here/harp-materials/lib/DisplacementFeature.ts
50.00% <0.00%> (-50.00%)
:arrow_down:

@here/harp-mapview/lib/geometry/DisplacedMesh.ts
21.73% <0.00%> (-20.27%)
:arrow_down:

@here/harp-mapview/lib/DecodedTileHelpers.ts
56.88% <0.00%> (-1.02%)
:arrow_down:

@here/harp-mapview/lib/PickHandler.ts
18.91% <0.00%> (-0.71%)
:arrow_down:

@here/harp-geometry/lib/ClipPolygon.ts
96.96% <0.00%> (-0.47%)
:arrow_down:

@here/harp-mapview/lib/Tile.ts
72.75% <0.00%> (ø)

@here/harp-utils/lib/Mixins.ts
76.92% <0.00%> (ø)

@here/harp-test-utils/lib/WebGLStub.ts
100.00% <0.00%> (ø)

@here/harp-utils/lib/SampleBilinear.ts
100.00% <0.00%> (ø)

@here/harp-materials/lib/CopyMaterial.ts
100.00% <0.00%> (ø)

... and 39 more

Continue to review full report at Codecov.

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


Teams Live Share tutorial: link in development section is broken

https://learn.microsoft.com/en-us/microsoftteams/platform/apps-in-teams-meetings/teams-live-share-tutorial#deployment
Toolkit link under development section is broken
Fix:

After you're ready to deploy your code, you can use Teams Toolkit or the Teams Developer Portal to provision and upload your app's zip file.

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

ID: c4095988-9b54-4919-411d-4db9b081af57
Version Independent ID: c4095988-9b54-4919-411d-4db9b081af57
Content: Live Share code tutorial - Teams
Content Source: msteams-platform/apps-in-teams-meetings/teams-live-share-tutorial.md
Service: msteams
GitHub Login: @surbhigupta
Microsoft Alias: stevenic

Hello @corinagum - Thanks for raising this issue.
@surbhigupta12 - Please help us here to fix the broken link.


fixes issue where hostnames would change on package reinstall/update

This ultimately fixes Start9Labs/lnd-wrapper#35

👍


YARN-10720. (branch-2.10) YARN WebAppProxyServlet should support connection timeout…

… to prevent proxy server from hanging.  This PR is to run the precommit job for this backport. I also opened #4102 to backport to branch-3.2.
How was this patch tested?
Ran TestWebAppProxyServlet locally.
For code changes:

[x] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
n/a Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
n/a If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
n/a If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
11m 33s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ branch-2.10 Compile Tests _

+0 :ok:
mvndep
2m 14s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
12m 43s

branch-2.10 passed

+1 :green_heart:
compile
8m 19s

branch-2.10 passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
compile
6m 55s

branch-2.10 passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

+1 :green_heart:
checkstyle
0m 57s

branch-2.10 passed

+1 :green_heart:
mvnsite
1m 57s

branch-2.10 passed

+1 :green_heart:
javadoc
1m 54s

branch-2.10 passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
javadoc
1m 33s

branch-2.10 passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

+1 :green_heart:
spotbugs
3m 54s

branch-2.10 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 19s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 25s

the patch passed

+1 :green_heart:
compile
7m 53s

the patch passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
javac
7m 53s

hadoop-yarn-project_hadoop-yarn-jdkAzulSystems,Inc.-1.7.0_262-b10 with JDK Azul Systems, Inc.-1.7.0_262-b10 generated 0 new + 138 unchanged - 10 fixed = 138 total (was 148)

+1 :green_heart:
compile
6m 39s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

+1 :green_heart:
javac
6m 39s

hadoop-yarn-project_hadoop-yarn-jdkPrivateBuild-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07 with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07 generated 0 new + 128 unchanged - 10 fixed = 128 total (was 138)

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 54s
/results-checkstyle-hadoop-yarn-project_hadoop-yarn.txt
hadoop-yarn-project/hadoop-yarn: The patch generated 1 new + 231 unchanged - 0 fixed = 232 total (was 231)

+1 :green_heart:
mvnsite
1m 48s

the patch passed

+1 :green_heart:
xml
0m  1s

The patch has no ill-formed XML file.

+1 :green_heart:
javadoc
1m 45s

the patch passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
javadoc
1m 27s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

+1 :green_heart:
spotbugs
4m 18s

the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 42s

hadoop-yarn-api in the patch passed.

+1 :green_heart:
unit
3m 14s

hadoop-yarn-common in the patch passed.

+1 :green_heart:
unit
0m 36s

hadoop-yarn-server-web-proxy in the patch passed.

+1 :green_heart:
asflicense
0m 38s

The patch does not generate ASF License warnings.

88m 45s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4103/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4103

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell xml

uname
Linux cd09d98a63a0 4.15.0-163-generic #171-Ubuntu SMP Fri Nov 5 11:55:11 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-2.10 / bbf1250e054faedcd40e14024f3c4be1717838ea

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

Multi-JDK versions
/usr/lib/jvm/zulu-7-amd64:Azul Systems, Inc.-1.7.0_262-b10 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4103/1/testReport/

Max. process+thread count
111 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-web-proxy U: hadoop-yarn-project/hadoop-yarn

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4103/1/console

versions
git=2.17.1 maven=3.6.0 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.


Support references between Terraform modules

[x] module block

[x] Relative path
[x] Remote (using get command ?)

[ ] terraform_remote_state resource

[ ] artifactory
[ ] atlas
[ ] consul
[ ] etcd
[ ] http
[ ] s3
[ ] swift

Related documentation:
module block - get command

I don't think the plugin should download modules automatically.
But after terraform get is launched externally, it would be cool to read them from .terraform/modules/

How does remote state relate to this feature?

Hi!
The remote modules are detected correctly, as long as they are in the git repo's root.
In case they are in a subdir (like in https://github.com/opencredo/letsencrypt-terraform), it fails to detect them.
I think the plugin should try to look for //s in the module source (like in source = "github.com/opencredo/letsencrypt-terraform//modules/acme-cert-request") and if there is a //, look for the module in the path after //.

@scream314 From next plugin release subdirectories would be also successfully detected

@VladRassokhin Thanks for the update on this!

Hey all is this the same as using remote state?
data "terraform_remote_state" "global" {
  backend = "s3"
  config {
    bucket = "state-bucket"
    key = "key.tfstate"
    region = "region"
  }
}

I'm unable to get autocomplete/validation when using any state from another state file like this.

@VladRassokhin Is the fix for completion of remote modules been merged? I don't seem to be able to auto-complete any variables or outputs from remote directories by using local ones works.

@iTsFILIPOficial for remote modules it's supported for several months already, if you have some problems please create a new issue. Also ensure to run terraform get

Actualy, after a terraform get the auto-completion not work

WARN - .terraform.config.model.Module - Terraform Module 'remote-module' with source<EMAIL_ADDRESS>directory not found locally under 'PsiDirectory:/opt/poc/terraform', use terraform get to fetch modules.

The function computeModuleStorageName get the md5 hash by: "root.$path-$source"
But terraform get set the hash by : "1.$path;$source"

@nicolas-rey Thanks for sharing. Probably there was some change in Terraform code, I'll take a look.

Fixed modules referencing, would be available in upcoming release.

Hi there,
with the fix introduced in 0.6.12 the referencing of local modules seems to got broken.
The following example:
structure:

root

terraform.tfvars
module_a

output.tf

module_b

.terraform

modules

modules.json
{{my-hashed-module}}

output.tf

main.tf
terraform.tfvars

...

--- module_a/output.tf ---
output "foo" {
  value = "bar"
}

--- module_b/main.tf ---
module "module_a" {
  source = "../module_a"
}

resource "some_resource" "my-resource" {
  foo = "${module.module_a.foo}"
}

As you might have already seen, I'm using terragrunt in my project, to be able to plan etc. module_b on it's own (executing terragrunt in the module's directory) or all modules together (executing terragrunt in the root directory).
Since the reference from module_b to module_a is a local file reference ("../module_a"), I would have expected auto-completion and referencing to consider the actual file in module_a.
However, with the update to 0.6.12 the plugin began to only consider files in ".terraform/modules/{{my-hashed-module}}". This becomes problematic, when I want to edit the original file in module_a by "ctrl + left-click" jumping to it - which brings me to the generated file in ".terraform/modules/{{my-hashed-module}}".
It is also a problem, because Intellij will mark the module as non-existent as long as I didn't run any terraform command to generate the ".terraform" directory contents.
I currently reverted back to 0.6.10, which did support the wanted behaviour.
Is there any chance, that you can try out yourself and fix the issue?
Thanks in advance.
Regards,
Alex

@alxgrk AFAIR since 0.6.14 (or even 0.6.13) relative module paths fixed and plugin would navigate to plugin source, not .terraform/modules/HASH/.

I'm closing issue since 'module' blocks are supported and there's no visible API in Terraform to fetch remote states.


validDestination address

Consider preventing the transfer of tokens to the same address of the smart contract.
validating that the "to" address is neither 0x0 nor the smart contract's own address:
modifier validDestination( address to ) {
    require(to != address(0x0));
    require(to != address(this) );
    _;
}

The modifier should then be applied to the "transfer" and "transferFrom" methods:

validDestination address issue are solved sucessfully


The really url of karmada operator

:warning: This repo is not active  :warning:
The really url of karmada operator exist on repo of karmada.
https://github.com/karmada-io/karmada/tree/master/operator

Why not archive or delete this repo? It makes users feel confused.
/cc  @RainbowMango @calvin0327

/assign
We should remove or archive this repo.

Refer to https://github.com/karmada-io/community/issues/38.


Front page does not represent the tool

Seems the current page of https://rxjs.dev does not represent the tool, but instead some unrelated articles. Do you mind removing them in favor of showing what is rxjs and why would someone stumbling upon it want to use it?

it is intended representation and we'll evaluate those over time.

Intended representation of unrelated topic? I am not sure how does that help rxjs.


A problem with exists function

index_ variable is a map that holds the arguments that are added using addArgument.
The exists function is currently written as follows
bool exists(const String& name) const { return index_.count(delimit(name)) > 0; }
so a code like the one below will always enter the if's body, even if the clean argument has not been sent to the program,
parser.addArgument("-c", "--clean");
// parsing passed arguments
parser.parse(size_t(__argc), const_cast<const char **>(__argv));
if (parser.exists("clean")) {
   // ...
}

This is inconsistent with the definition given for the exists function

exists()              check if an argument has been found

Thank you for your efforts,
Sincerely,
Ahmad

I'd suggest the following to fix the problem with the exists method.
    bool exists(const String& name) const {         auto it = index_.find(delimit(name));         return (it != index_.end()) && (arguments_[it->second].fixed_nargs > 0);     }


calling service.get_template() triggers an error in Python 3.7

Executing service.get_template() in Python 3.7 results in RuntimeError: generator raised StopIteration. The example is below is when accessing FlyMine; however, I have seen the same thing happens for YeastMine.
Demonstrating the issue:
Go to here and scroll fown to the 'Tutorial 7: Templates' section. Under there click the launch binder badge and try running the first cell after the session spins up. The error will come up. as currently the Binder instances are defaulting to Python 3.7.
Example output from the demonstration:

I suspect it is related to the second item under 'Changes in Python Behavior' here as currently the Binder instances are defaulting to Python 3.7.. A possible fix to a related issue is shown here. It looks like incorporating that approach to line 477 of intermine/query.py may fix it.

@fomightez - thanks for reporting this! I've submitted a PR that hopefully will fix the issue, but until it's deployed, there is a workaround for binder - specifying python 3.5 in runtime.txt.
https://github.com/yochannah/intermine-ws-python-docs/blob/template-error/runtime.txt

The problem still persists. Tested with Python 3.7.10

Problem also present with python version : 3.8.11. Anyone found a workaround the problem?

Note that I cannot use Python 3.5 (as suggested workaround above) since I am using other dependencies requiring Python 3.7+

Thanks for info.
Using the dev version is an option but for publishing workflow using intermine is not ideal.
Is there any change to have a newer working version pushed to pypi and conda (I am using the conda channel)?
Thanks

Hmmm - I no longer work at InterMine but I'll just namedrop @leoank and @uosl just to make sure current InterMine staff see this issue is still open...

Thanks for bringing this to our attention. We have our hands full at the moment, but hopefully later this week we'll look at making another release.

@jburel we have just release 1.12.0

Thanks @danielabutano I will give it a try


outdated musl binary

hello, I don't know if it is the right place to report this issue but the mediaplex-linux-x64-musl isn't updated (0.0.1 instead of 0.0.9)
this issue mean that mediaplex doesn't work when running on alpine
Edit: musl removed here: https://github.com/androzdev/mediaplex/pull/4

https://github.com/androzdev/mediaplex/releases/tag/v1.0.0


correct man docker-pull

Signed-off-by: Sally O'Malley<EMAIL_ADDRESS>

LGTM - @thaJeztah @moxiegirl

LGTM, !m @sallyom :smile:


dag fails to render with some workflows

Ran into this with the aid of new workflows from @buchanae
Bug Report
Expected behaviour
DAG should render, just like https://dockstore.org/workflows/BD2KGenomics/dockstore_tool_star_fusion (there may be a delay or a need to click between tags a few times which is also an issue) or https://dockstore.org/workflows/h3abionet/h3agatk
Actual behaviour
https://dockstore.org/workflows/smc-rna-challenge/beccyl-7238196/smc-rna-challenge-beccyl-7238196 fails to render altogether. The web service indicates a 204, meaning it (the dag code) has some problem understanding the CWL document although this isn't across the board since we're able to pull out content for the Info tab.
Steps to reproduce the behaviour
Go to https://dockstore.org/workflows/smc-rna-challenge/tnv-7269246/tnv-7269246 and try out the DAG tab
Environment (Browser or OS and Dockstore version)
DockstoreUI - 1.2.3
DockstoreApi - 1.2.3
┆Issue is synchronized with this Jira Story
┆Issue Type: Story
┆Fix Versions: Dockstore 2.X
┆Issue Number: DOCK-485

Still a thing

No longer a thing
https://staging.dockstore.org/workflows/github.com/smc-rna-challenge/tnv-7269246/tnv-7269246:master?tab=info is the URL


Support 1inch Fusion

@mraniki fantastic helper library in active current development unlike others!  :+1:
Based on everything happening with CEX users do need DEX :shipit:
Please see 1inch Fusion + Fusion SDK  only 18 lines of code.

[x] Auto Routing
[x] Liquidity Aggregation
[x] Zero gas fees
[ ] Check slippage e.g < -2%
[ ] Check price impact e.g < -1%
[ ] Split % Order Amount into e.g 3 chunks to get best price
[ ] Logging for BUY / SELL = % Profits (PnL) :tada:

Using Tradingview alert Webhook to DiFi bot to execute DEX trades.

Yeah that is definitely the goal. thanks for the encouragement. check my dex trading tool (https://github.com/mraniki/tt). Problem with 1inch is that they are blocking now their api. so main option via uni swapv2 type router is the best approach. I'm exploring Apollox as there is forex now on their V2 but no documentation yet

More encouragement for active project 🥇
I am supporting with comments elsewhere to point people here:
:iphone: :phone:
See the TalkyTrader project by @mraniki here:
https://github.com/mraniki/tt
Python DEX Token Swap Library:
https://github.com/mraniki/dxsp

@tnd3 built has been done but there is an issue with 1inch api being tracked here
https://github.com/mraniki/dxsp/issues/189
Until this is resolved by 1inch we only have normal router access via uniswap lib or 0x access


return 204 on workflows retire subjects

provide the correct status code for retire subjects with no content reponse.
Review checklist

[ ] First, the most important one: is this PR small enough that you can actually review it? Feel free to just reject a branch if the changes are hard to review due to the length of the diff.
[ ] If there are any migrations, will they the previous version of the app work correctly after they've been run (e.g. the don't remove columns still known about by ActiveRecord).
[ ] If anything changed with regards to the public API, are those changes also documented in the apiary.apib file?
[ ] Are all the changes covered by tests? Think about any possible edge cases that might be left untested.

LGTM


Add event types and decoder for evm module

We should add the missing event types and decoder for the evm module (for go and ts-web client SDKs).

adding myself


two-stage docker build

This removes the go sdk from the final container, making it smaller. I also moved the inner port to 80, which is the default for HTTP. Users can remap it to whatever they want using Docker.
Basically just copy-pasted the Docker docs: https://docs.docker.com/develop/develop-images/multistage-build

sweet! thanks @nicolov. I ll add Bazel docker rules next, should make building and pushing images easier.


ionic 6 -android missing com.android.volley:volley

I have a brand new ionic 6 capacitor 4.7 app with a single page
I'm not able to get the project building when using the plugin
"dependencies": {
"@angular/common": "^15.0.0",
"@angular/core": "^15.0.0",
"@angular/forms": "^15.0.0",
"@angular/platform-browser": "^15.0.0",
"@angular/platform-browser-dynamic": "^15.0.0",
"@angular/router": "^15.0.0",
"@capacitor-community/google-maps": "^2.0.0-beta.1",
"@capacitor/android": "^4.7.0",
"@capacitor/app": "4.1.1",
"@capacitor/core": "4.7.0",
"@capacitor/haptics": "4.1.0",
"@capacitor/keyboard": "4.1.1",
"@capacitor/status-bar": "4.1.1",
"@ionic/angular": "^6.1.9",
"ionicons": "^6.0.3",
"rxjs": "~7.5.0",
"tslib": "^2.3.0",
"zone.js": "~0.11.4"
},
its failing with the following information
Execution failed for task ':app:mergeDebugResources'.
[capacitor]         > Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
[capacitor]         > Could not find com.android.volley:volley:1.1.1.
[capacitor]         Searched in the following locations:
[capacitor]         - https://dl.google.com/dl/android/maven2/com/android/volley/volley/1.1.1/volley-1.1.1.pom
[capacitor]         - https://repo.maven.apache.org/maven2/com/android/volley/volley/1.1.1/volley-1.1.1.pom
[capacitor]         - file:/C:/Ionic/Testing stuff/test-01/android/capacitor-cordova-android-plugins/src/main/libs/volley-1.1.1.jar
[capacitor]         - file:/C:/Ionic/Testing stuff/test-01/android/capacitor-cordova-android-plugins/src/main/libs/volley.jar
[capacitor]         - file:/C:/Ionic/Testing stuff/test-01/android/app/libs/volley-1.1.1.jar
[capacitor]         - file:/C:/Ionic/Testing stuff/test-01/android/app/libs/volley.jar
[capacitor]         Required by:
[capacitor]         project :app > project :capacitor-community-google-maps > com.google.android.libraries.maps:maps:3.1.0-beta
The  installation process was just as instructed
npm i --save @capacitor-community/google-maps
npx cap sync
Is it because i'm using capacitor > v4

I have found a solution so that the project build.
I had to add jcenter to the build.gradle file
allprojects {
repositories {
google()
mavenCentral()
jcenter() // this line :)
}
}


Simplify gen_txt.py

I believe gen_txt.py is doing too much work. It should not be necessary to process the dataset for different input resolutions of the network, as the yolo input coordinates are basically UV coordinates and are relative to input image dimensions. (Unless you do letterbox rescaling I guess...)
https://github.com/AlexeyAB/Yolo_mark/issues/60#issuecomment-401854885
Current implementation:
def txt_line(cls, bbox, img_w, img_h):
    """Generate 1 line in the txt file."""
    assert INPUT_WIDTH > 0 and INPUT_HEIGHT > 0
    x, y, w, h = bbox
    x = max(int(x), 0)
    y = max(int(y), 0)
    w = min(int(w), img_w - x)
    h = min(int(h), img_h - y)
    w_rescaled = float(w) * INPUT_WIDTH  / img_w
    h_rescaled = float(h) * INPUT_HEIGHT / img_h
    if w_rescaled < MIN_W or h_rescaled < MIN_H:
        return ''
    else:
        cx = (x + w / 2.) / img_w
        cy = (y + h / 2.) / img_h
        nw = float(w) / img_w
        nh = float(h) / img_h
        return '%d %.6f %.6f %.6f %.6f\n' % (cls, cx, cy, nw, nh)

Implementation from https://github.com/theAIGuysCode/OIDv4_ToolKit:
# function that turns XMin, YMin, XMax, YMax coordinates to normalized yolo format
def convert(filename_str, coords):
    os.chdir("..")
    image = cv2.imread(filename_str + ".jpg")
    coords[2] -= coords[0]
    coords[3] -= coords[1]
    x_diff = int(coords[2]/2)
    y_diff = int(coords[3]/2)
    coords[0] = coords[0]+x_diff
    coords[1] = coords[1]+y_diff
    coords[0] /= int(image.shape[1])
    coords[1] /= int(image.shape[0])
    coords[2] /= int(image.shape[1])
    coords[3] /= int(image.shape[0])
    os.chdir("Label")
    return coords

Note the lack of INPUT_WIDTH and INPUT_HEIGHT.

Do you require this parameter to filter small objects? Or can we calculate the size of objects independent of network input?

Do you require this parameter to filter small objects? Or can we calculate the size of objects independent of network input?

Do you require this parameter to filter small objects?

Yes.  By filtering out objects that are too small, we would be asking the yolo model to learn more realistic targets.  It would produce a object detector that performs better at inference time.  (Don't just believe my words.  You could experiment/verify it by yourself.)

Do you require this parameter to filter small objects?

Yes.  By filtering out objects that are too small, we would be asking the yolo model to learn more realistic targets.  It would produce a object detector that performs better at inference time.  (Don't just believe my words.  You could experiment/verify it by yourself.)

Hi, I totally agree with you regarding the performance improvements. However, by replacing the height/width with relative targets you can omit the input dimensions of the network and prepare the dataset only once for all input resolutions, which is more convenient for MLOps pipelines.
MIN_W = 0.01
MIN_H = 0.01
#
w_rescaled = float(w) / img_w
h_rescaled = float(h) / img_h
if w_rescaled < MIN_W or h_rescaled < MIN_H:
    return ''

0.01 times 608 is roughly 6 and 0.01 times 416 is 4, so you get about the same result for both common yolov4 configurations without having to know the input dimensions in advance.
This change is very opinionated of course. I was including this in my automated data preparation workflow and wanted to share it with you in case you will automate this repo in the future. Considering it closed.

Hi, I totally agree with you regarding the performance improvements. However, by replacing the height/width with relative targets you can omit the input dimensions of the network and prepare the dataset only once for all input resolutions, which is more convenient for MLOps pipelines.
MIN_W = 0.01
MIN_H = 0.01
#
w_rescaled = float(w) / img_w
h_rescaled = float(h) / img_h
if w_rescaled < MIN_W or h_rescaled < MIN_H:
    return ''

0.01 times 608 is roughly 6 and 0.01 times 416 is 4, so you get about the same result for both common yolov4 configurations without having to know the input dimensions in advance.
This change is very opinionated of course. I was including this in my automated data preparation workflow and wanted to share it with you in case you will automate this repo in the future. Considering it closed.


Let the nmap device tracker return upper case MAC addresses.

I noticed this bug because my known_devices.csv always contained "unknown device". After this patch, it is filled with the correct names.
The webinterface is still not showing my devices, but I'm still investigating that.

Coverage remained the same at 74.69% when pulling 71ac550e7d2e4567dd4395c1e3a761314e86df0c on Dutchy-:master into 9d41958b3a35d98badb988dcb1303aa46d812ea0 on balloob:master.

This is not needed, the device tracker converts all found mac addresses to uppercase (source).

That may be intended, but consider this a bug report then; devices were not correctly detected because the case did not match in this function: https://github.com/balloob/home-assistant/blob/master/homeassistant/components/device_tracker/nmap_tracker.py#L94
This is because self.last_results contains lower case mac addresses.

Okay I totally linked the wrong thing. Meant to link this.
The device tracker started converting everything to uppercase on Feb 27 (f6f76acdb0edb49362e49dbecb57ea6b55538b5f) so I am not sure how this issue can occur.

The nmap tracker generates a list of devices here. It is sent to the device tracker where it is converted to upper case. It is then sent back to the nmap tracker to the function i linked in my previous post (through this call here. At this point it is comparing lower to upper case mac addresses. I hope this helps.

You are totally right, I'm so sorry! Thanks for fixing this.
Can you point it at the dev branch and I'll be happy to merge it.

Closing, see #143


Add Module and Namespace in nested module and type pages

Adds module and namespace information to the "TypeInfo" and "ModuleInfo" types.
This information is used to add namespace name and links to the parent module in type.cshtml and module.cshtml templates.
Adds test case to review that templates can be generated with correct information.
This will fix #53

This looks like a very useful addition, thanks for doing this!
The only thing I would perhaps do a bit differently is to expose the additional information in a way that makes it a bit easier to use in the C# code in the template, so that you do not have to write things like:
if (FSharpOption<Module>.get_IsSome(@Model.ParentModule)) ...

Wouldn't the following work instead?
if (Model.ParentModule.IsSome) ...

I think this should actually work - if so, could you please simplify the template?
(if this doesn't work, then I'm not sure what would be better - I guess we could add HasParentModule or even return null - woohoo!)

Yep, while adding the link to the template it didn't feel right doing if (FSharpOption<Module>.get_IsSome(@Model.ParentModule)) ..., I will review if I can do something better than returning null.

Definitely if (Model.ParentModule.IsSome) ... is not possible.
I have added HasParentModule property to TypeInfo and ModuleInfo records, and I have added the Exists extension  method to the Module option following @ldfallas http://langexplr.blogspot.co.at/2008/06/using-f-option-types-in-c.html
I prefer the Exists extension method. If you agree I would remove the HasParentModule property.

Thanks, this is a nice trick :-).


Make Autotune Section

#1731  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @craig-statsig and the rest of your teammates on  Graphite


make tests failing at hello_world_component

make tests is giving following error at commit bee515038e
libhpx_hello_world_component.so: undefined reference to `hpx::cout'
collect2: error: ld returned 1 exit status
CMakeFiles/hello_world_client.dir/build.make:127: recipe for target 'hello_world_client' failed
make[6]: * [hello_world_client] Error 1
CMakeFiles/Makefile2:104: recipe for target 'CMakeFiles/hello_world_client.dir/all' failed
make[5]: * [CMakeFiles/hello_world_client.dir/all] Error 2
Makefile:83: recipe for target 'all' failed
make[4]: * [all] Error 2
tests/unit/build/CMakeFiles/cmake_build_dir_test.make_compile.dir/build.make:57: recipe for target 'tests/unit/build/CMakeFiles/cmake_build_dir_test.make_compile' failed
make[3]: * [tests/unit/build/CMakeFiles/cmake_build_dir_test.make_compile] Error 2
CMakeFiles/Makefile2:28127: recipe for target 'tests/unit/build/CMakeFiles/cmake_build_dir_test.make_compile.dir/all' failed
make[2]: * [tests/unit/build/CMakeFiles/cmake_build_dir_test.make_compile.dir/all] Error 2
CMakeFiles/Makefile2:300: recipe for target 'CMakeFiles/tests.dir/rule' failed
make[1]: * [CMakeFiles/tests.dir/rule] Error 2
Makefile:266: recipe for target 'tests' failed
make: * [tests] Error 2

But make tests are passing at commit 69100ee061 successfully.

@Anushi1998 seems like it's happening with gcc. The circle script with clang runs just fine.

I got the same error while linking hello_world_client in make tests.
(mak example completed successfully)
Is there any fix for this problem?
I'm using g++ 8.1.0 with the HPX Version 1.1.0 downloaded from the Ste||ar site. Boost 1.68.0 was build with c++std=17 and cmake ist up-to-date with version 3.13.0-rc2.

@arkantos493 are you using the current master? In case your commit is of version 1.1.0, it will throw a linking error since this error was discovered later (hence part of the milestones for version 1.2).

@NK-Nikunj That might be the problem. So now I cloned the current git repo, but it appears that now not even the normal make is successfully:

In member function ‘int hpx::threads::topology::get_numa_domain(const void*) const’:
../hpx/src/runtime/threads/topology.cpp:1332:13: error: ‘HWLOC_MEMBIND_BYNODESET’ was not declared in this scope
HWLOC_MEMBIND_BYNODESET);
^~~~~~~~~~~~~~~~~~~~~~~
../hpx/src/runtime/threads/topology.cpp:1332:13: note: suggested alternative: ‘HWLOC_MEMBIND_PROCESS’
HWLOC_MEMBIND_BYNODESET);
^~~~~~~~~~~~~~~~~~~~~~~
HWLOC_MEMBIND_PROCESS
../hpx/src/runtime/threads/topology.cpp:1331:19: error: ‘hwloc_get_area_memlocation’ was not declared in this scope
int ret = hwloc_get_area_memlocation(topo, addr, 1,  ns,
^~~~~~~~~~~~~~~~~~~~~~~~~~
../hpx/src/runtime/threads/topology.cpp:1331:19: note: suggested alternative: ‘hwloc_get_area_membind’
int ret = hwloc_get_area_memlocation(topo, addr, 1,  ns,
^~~~~~~~~~~~~~~~~~~~~~~~~~
hwloc_get_area_membind
src/CMakeFiles/hpx.dir/build.make:1297: recipe for target 'src/CMakeFiles/hpx.dir/runtime/threads/topology.cpp.o' failed
make[2]: *** [src/CMakeFiles/hpx.dir/runtime/threads/topology.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
CMakeFiles/Makefile2:1828: recipe for target 'src/CMakeFiles/hpx.dir/all' failed
make[1]: *** [src/CMakeFiles/hpx.dir/all] Error 2
Makefile:140: recipe for target 'all' failed
make: *** [all] Error

I tried setting hwloc manually with the -DHWLOC_ROOT cmake flag and using the default version without flag.

What version of hwloc are you using?

Thanks for the reply. I used hwloc 1.11 from the apt repositories. After I manually installed version 2.0.2 it worked.

@arkantos493 thanks for reporting back. Could you also tell me the patch number of the 1.11 version that you tried? Our build should work with any 1.11 but that doesn't seem to be the case.

Thanks @arkantos493, in that case your problem should be solved now that #3528 has been merged.


Normalize Callable naming convention

Multiple Griptape classes have Callable properties. We use the following naming convention for them:

_func. For example SnowflakeSqlDriver.connection_func.
_fn. For example, LocalVectorStoreDriver.relatedness_fn.
Method-like. For example, BasePromptDriver.prompt_stack_to_string.

The team decided to normalize all callable properties to follow the _fn naming convention.

After revisiting the naming conventions, we decided against using the _fn suffix, as it felt unpythonic and inconsistent with naming conventions for other field types. For instance, we don't use _str for string fields, so there's no need to treat callables differently.
For callable fields and methods, the following guidelines should be used:

Action Functions: Functions that perform an action should be named using a verb or verb phrase that clearly describes what the function does.

SnowflakeSqlDriver.connection_func → SnowflakeSqlDriver.create_connection
LocalVectorStoreDriver.relatedness_fn → LocalVectorStoreDriver.calculate_relatedness
BasePromptDriver.prompt_stack_to_string → BasePromptDriver.convert_prompt_stack_to_string

Boolean Functions: Functions that return a boolean should be prefixed with predicates such as is_, has_, or can_ to indicate a state or condition.

Event Handlers: Functions that react to events should be prefixed with on_. These functions typically don’t return a value but are triggered in response to an event. If a function transforms an event or returns a value based on it, it should follow the first rule (e.g., process_event).

Keep in mind that these are guidelines, not strict rules, and can be adjusted based on context.

Some team members have noted that these naming conventions may be more appropriate for class methods than class fields. For example, create_connection could be misinterpreted as a boolean that indicates whether a connection should be created.
To avoid this confusion, we are standardizing class field naming to be noun-based. Below are some of the conventions I landed on in #1275.
*_factory: Used for functions that create a new instance of an object.
*_provider: Used for functions that supply a value. These functions may create new instances, as long as the value represents the same resource or value.
*_formatter: Formats an object or value, typically into a string or another representation.
*_callback: Used for functions that react to or handle a specific event or condition.
*_handler: Used for functions responsible for actively managing or processing an event or task.
*_calculator: Used for functions that compute or derive a specific value.
Again, these aren't hard-and-fast rules, but hopefully they provide a clear framework to guide future naming descisions.

And finally, after even more discussion we've settled on a variation of the initial proposal:

Action Functions: Functions that perform an action should be named using a verb or verb phrase that clearly describes what the function does.

SnowflakeSqlDriver.connection_func → SnowflakeSqlDriver.create_connection
LocalVectorStoreDriver.relatedness_fn → LocalVectorStoreDriver.calculate_relatedness
BasePromptDriver.prompt_stack_to_string → BasePromptDriver.convert_prompt_stack_to_string

Boolean Functions: Functions that return a boolean should be prefixed with predicates such as is_, has_, or can_, indicating a state or condition.

Callbacks/Hooks: Functions that execute during specific events should be prefixed with on_. This naming convention avoids assumptions about the function's behavior, emphasizing that it reacts to an event.

This article comes closest to summarizing these ideas.
Addressing Previous Points:

Verbs sound like booleans: While it's true that verbs can resemble boolean names, our extensive use of type hints should minimize ambiguity. Additionally, we can improve our boolean function names over time.
What happened to nouns?: Attempting to force noun-based names for functions (e.g., "factory" or "provider") felt clunky and could be confusing for users unfamiliar with these terms. A consistent verb-based naming convention, with a few exceptions, is simpler and clearer.


Help for adding Requirements in README

I would like to clarify the README with exact requirements for this plugin to work, but I'm a bit lost with recent cordova and/or cordova-ios (I assume the later depends somehow on the former), iOS versions, Xcode versions and so on.
AFAIU:

Xcode >= 7.2.1
cordova 3.X (4.X is not valid until #90 is done)
cordova-ios ?
iOS >= 9 (due to some JS stuff in Safari), but maybe it works in iOS 8 too...

May somebody help on this?

All that LGTM.

Which cordova-ios? or just the default coming with cordova 3.X when calling cordova platform add ios?

Oh, wait, it's actually cordova-ios the one that needs to be < 4. cordova is 5.x by now, that's ok.

I believe it should be cordo-ios version 3.9.2

cordova ANY
cordova-ios 3.9.X ?

That?

Yes. Because cordova 5.x is needed to support the new Android 6.0 permissions system

Thanks


Add authorization verification function

Story
The authorization checks within the API are repetitive, and could be DRY'er.
Description
Every API method that requires an authorization check has an individually coded assessment.
Done When
The authorization functionality is contained within a separate function to improve code re-usability.

Feature implement in registry-web-platform-registry-dev silver cluster: November 9, 2020.


fix: Fix hovering area position, #25

This PR fixes the position of the hovering area.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


add to invite codes fields required for uproxy to accept tokens

See also:
https://github.com/uProxy/uproxy-lib/pull/319

:+1:


Fix deployment issue with leading slash in config key

Potentially prevent key from starting with a slash...

Or strip leading and trailing slashes


Write a Java program to find cube of a number

Description
Write a Java program to find cube of a number
Input  : 2
Output : 8

How to contribute

Save the solution in FindCubeOfANumber.java file
Add FindCubeOfANumber.java file in find-cube-of-a-number folder

!assign


Building failed E0658

Bug Report

What version of TiKV are you using?
tikv-4.0.11
What operating system and CPU are you using?
CentOS
Steps to reproduce

make
rustc --version
rustc 1.42.0-nightly (0de96d37f 2019-12-19)

What did you expect?
when build tikv 4.0.11 it report
error: aborting due to 11 previous errors

For more information about this error, try `rustc --explain E0658`.
error: could not compile `object`.
warning: build failed, waiting for other jobs to finish...
error: build failed

Running rustc --explain E0658 display
An unstable feature was used.

Erroneous code example:

#[repr(u128)] // error: use of unstable library feature 'repr128'
enum Foo {
    Bar(u64),
}

If you're using a stable or a beta version of rustc, you won't be able to use
any unstable features. In order to do so, please switch to a nightly version of
rustc (by using rustup).

If you're using a nightly version of rustc, just add the corresponding feature
to be able to use it:

#![feature(repr128)]

#[repr(u128)] // ok!
enum Foo {
    Bar(u64),
}

What did happened?

We have updating rustc several times, you can check the version in file rust-toolchain. It's recommended to use rustup, which will pick the correct version for you.


Custom Region Folding Problem

I have just installed brackets and the custom region fold extension.
I am on a Mac and have created a project/folder “project_collapse_test”.
In the project folder there are both “brackets.json” and “.brackets.json” files containing the following:
{
"custom-region-fold.startRegionWord": "start_chapter",
"custom-region-fold.endRegionWord": "end_chapter"
}
When I edit (with brackets) the following text file (test.txt):

// abc start_chapter
5)
6)
7)
8)
9)
10)
// end_chapter
11)
12)
and go to View > Collapse All
nothing happens.
If I select text and select:
View > Collapse Current
it works.

@chuck-brackets-questions The custom region folding recognises the region keywords only in the comments section of a file. The problem with your example is that comments are not really recognised in .txt files (as far as I know - although there might be a code mirror mode with an extension close enough to the plain text that you might be able to use). As a proof of concept you can try the same example in a markdown .md file (using # as a comment delimeter) or a javascript .js file using // as a comment delimeter.
Hope this helps.

Extension question / problem should be asked on the extension repository.
Closing.


OnFinishedEvent with a loop is fired at each tick

When setting a finite loop, the OnFinishedEvent is fired at each tick. I think it should be registered as an OnComplete callback rather than AppendCallback callback.

Sorry that it took me so long to be able to take a look at this, but actually using the OnComplete for this causes other problems when rewinding tween as well.
I will investigate this further to try to find a better solution

Thanks! My solution was to set the loop under the step, then add a callback on the next step. This works for simple tweens.

I'm glad you figure out a better way of handling it!  I will close the issue for now! :D


Problems querying using CamelCasePropertyNamesContractResolver

I would like to use a general CamelCasePropertyNamesContractResolver for Json.NET.
This works well for serialization/deserialization but not when querying on properties using LINQ since that seems to require the JsonPropertyAttribute.

This appears to be a duplicate of https://github.com/Azure/azure-documentdb-dotnet/issues/55


Make IbanCheckDigit#validate return false instead of raising an exception for null or less than 5 characters strings

Currently IbanCheckDigit#validate raise an exception for null or less than 5 characters strings.
Should this method return false instead ?

This issue relates to #183.