"src" dir missing in package

In contrast to 1.7.1, the src dir is missing in 1.8.0, and therefore importing the ES6 modules (via import Oidc from "oidc-client/index") doesn't work anymore :(
1.7.1:

1.8.0:

ok, i suck. i'll fix it tomorrow.

have a look again please at 1.8.1 and let me know. thanks

... so we're getting closer :)

fml, yea, i wasn't thinking when i was trying to prune npmignore. try once more, please

Yeah! Works now. Many thanks!


chore: Laravel 11 support

LGTM

Hey 👋 thanks for your work, i've just updated the dependencies in other PRs so pint etc does not clutter this PR.
Would you be able to rebase your changes on the latest main branch?
Otherwise, I can take over.
Thank you very much ✌

@saibotk Done 🚀

Perfect, looks good. Can you just add some phpstan ignores to the docrine type calls? Then we are good to go 💅

Sure thing! Just added the PHPStan ignores for the Doctrine type calls as suggested. Ready to merge whenever you are! 😊🚀

@saibotk Just wanted to check on the Laravel 11 support pull request. It’s merged for a couple of days now. Can we expect a release soon? Thanks! 👍🚀


WiP Remove the dependency from linker-interface on scalajs-ir.

And since sbt-scalajs only depends on linker-interface, this transitively removes the dependency from sbt-scalajs on scalajs-ir as well.

@gzm0 This needs a serious cleanup and decomposition in meaningful commits. At this point I'd like your opinion on whether this is something worth doing at all.
This allows the sbt plugin, along with any other build tool depending on the linker-interface, not to have any dependency on scalajs-ir. Currently, the fact that we receive scalajs-ir on the classpath because of linker-interface, but that we then load scalajs-linker reflectively, means that the version of scalajs-linker-interface must be exactly equal to that of scalajs-linker. While that is fine for sbt-scalajs, which is co-developed with scalajs-linker, it can be problematic for other build tools. Indeed, they are typically not built for one specific version of scalajs-linker, but instead load the right one depending on a setting. Nevertheless, they typically have to statically link against one version of scalajs-linker-interface. This means that it is very difficult for them not to encounter clashes.
On principles as well, when depending on scalajs-linker-interface we were automatically get scalajs-ir, whose versioning policy is equal to interface.unstable, yet its package name does not make that clear.

There are some difficulties, the most notable one being the fact that IRFileImpl must use "untyped" definitions for def entryPointsInfo and def tree. Previously they were ir.EntryPointsInfo and ir.Trees.ClassDef, but that is not available anymore. I made them completely abstract types, and introduced linker.standard.ConcreteIRFileImpl to safely cast between the abstract types and the concrete IR types.

but that we then load scalajs-linker reflectively, means that the version of scalajs-linker-interface must be exactly equal to that of scalajs-linker

Isn't this the case anyways because of interface.unstable?

Yes and no. interface.unstable is, in practice, much more stable than ir.*. ir.* changes every time we introduce a new IR node or change the IR in any way. It also contains the IR version numbers themselves.
It is practical to program against the binary interface of scalajs-linker-interface and link with many different versions of scalajs-linker. It's not practical to link scalajs-linker with a version of scalajs-ir that is not exactly equal.
At least that's my impression.

That's fair. So then to me, the major challenge is that the current linker interface assumes that IR file implementations are valid independently from the linker being used. (This is not an entirely hypothetical scenario, one could imagine using the cache of one version with another linker).
If we are really strict, this is something we have committed to, in the public interface. (I did, at some point, toy with path-dependent types for these things, but rejected it, because the typing would be a nightmare in sbt).
An idea of how to address this:

Change the unstable API of IRFiles to rely on byte blobs, rather than IR.
At this point, the cache is useless, as it cannot deserialize anymore.
Create a cached linker type, that allows to create linkers from a cache (this would likely also make a IRFileCache.Cache like type obsolete).

We'd have to leave the existing type definitions around, but we can make them less efficient (basically only have them work on byte blobs).
The downside is the funky API, where you cannot create a single linker, you have to create a CachedLinkerFactory or whatever and use that to create linkers. (OTOH, IRFileCache would disappear from the non-deprecated interface).

So then to me, the major challenge is that the current linker interface assumes that IR file implementations are valid independently from the linker being used. (This is not an entirely hypothetical scenario, one could imagine using the cache of one version with another linker).
If we are really strict, this is something we have committed to, in the public interface.

Have we? I don't think we have, because at the moment it's simply impossible to have two different scalajs-linker's at all (at least not without loading two different scalajs-linker-interface's as well, in which case the whole thing here is a non-issue).
To make sure we are talking about the same thing, when you say "independently from the linker being used", are you talking about a) the instance of Linker or b) the classloaded scalajs-linker artifact? From:

(I did, at some point, toy with path-dependent types for these things, but rejected it, because the typing would be a nightmare in sbt).

it seems you meant a). But in the a) case, nothing changes with this PR. We're still able to pass (cached) IR files to different instances of Linker. We just have to make sure that they come from the same classloaded scalajs-linker, but I think that's a fair requirement that is quite common in JVM classloaded artifacts.

Have we? I don't think we have, because at the moment it's simply impossible to have two different scalajs-linker's at all

In the context of loading different artifacts, yes. But different linker implementations is absolutely possible:
val myFiles = PathIRFile(...)
val irCache = StandardImpl.irFileCache()
val stdLinker: Linker = StandardImpl.linker(config)
val myAwesomeLinker: Linker = new MyAwesomeLinker()

stdLinker.link(irCache.cached(myFiles))
myAwesomeLinker.link(irCache.cached(myFiles))

If myAwesomeLinker has a different IR, with this PR, this will throw a CCE somewhere. Note that for this example to fail, we do not even need any classloading at all.

Right. That's in theory possible, indeed. I don't think it's a valid use case, though. In my mind the abstract types in IRFileImpl are abstract proxies for ir.EntryPointsInfo and ir.Trees.ClassDef only. That's why the casting functions are in standard.*. Casting them to something else than the IR classes in scalajs-ir is incorrect, in my view of this API.

Hum, but your argument requires implementation details from the point of view of linker.interface. That shouldn't be the case. Whatever linker.interface allows you to do should be possible, regardless of implementation details.
If casting the abstract types to something else is incorrect, the interface giving access to it should not allow it.
Maybe to put it in other words: In the current API, there is nothing (theoretical or practical) that prevents two different concrete instances of Linker to exist at the same time. There is something that prevents two different instances of ir to exist (in the sense that interface depends on it).
If we want to remove the second restriction (and I do believe this is a desirable goal), we need to make sure the interface does not pretend to have more degrees of freedom than will actually work. So if there are two different concrete instances of Linker depending on two different instances of ir, we need to make sure they do not interact with each other (at the IR level at least).

This is probably not worth keeping open after 2 years of inactivity. 😅


Remote GPIO

Is it possible to add the remote GPIO function as well?

The remote GPIO does not directly interact with hardware and is not going to be removed from Home Assistant.
https://www.home-assistant.io/integrations/remote_rpi_gpio/


"replace" and "reset" not working?

Version
v3 is SLOW for Android right now (because React Native ExperimentalNavigation is slow), see #355, no need to create new issue!
Tell us which versions you are using (react native 0.22 is required for v3!):

react-native-router-flux v3.22.22
react-native v0.24.1 (react 0.14.8)
redux 3.5.2

Expected behaviour
Calling Actions.someAction({ type: 'replace' }) (or reset) should change the current route/component to someAction.
Actual behaviour
The route changes but does not cause the view to re-render, leaving part of the UI from the previous route visible.
It appears that the menu changes but the underlying component does not re-render for some reason.
I have attempted to call this action in my container component, an action and a Scene's onLeft/onRight all with the same effects. Navigation seems to work otherwise if I use the default push type.
Steps to reproduce

Create two routes (myFirstRoute, mySecondRoute)
Navigate to mySecondRoute route from myFirstRoute, have an action that calls Actions.myFirstRoute({ type: 'reset' })
The route changes but part of the mySecondRoute still displays on the screen

Yes, I have the same situation when I try to use reset after authentication...

#525 !

@cridenour I see that now but please realize the current readme does not say this anywhere. Until that changes, I imagine a lot more similar issues are created unfortunately.
That said, it looks like v0.26.0 was just released so I imagine this won't be an issue soon.
Cheers 🍻


revad: move loaders to single loader

Codecov Report

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

@@           Coverage Diff           @@
##           master      #33   +/-   ##
=======================================
  Coverage   76.19%   76.19%
=======================================
  Files           2        2
  Lines          42       42
=======================================
  Hits           32       32
  Misses          5        5
  Partials        5        5

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 7e7f7b2...54e4370. Read the comment docs.


get notifications in array

I want something like this:
array(
    "info" => ["info", "messages"],
    "error" => ["error", "messages"]
    // etc...
);

Can you post more details on this?


Wrap MLPerf training scripts into Unified Job yaml format and create testing script

Check out MLPerf training reference implementation and company's submission results. Find the ones can be used in Alnair cluster (no specific hardware requirements, like A100, TPU...). Download data set to NSF drive. Wrap into Kubernetes compatible format, and test out in clusters.
Note:
Prepare at least 3 different types of training jobs (object detection, reinforcement learning ...)

Chose Nvidia's DeepLearningExample repo, which is better maintained. SageMaker also use this repo for some of their examples.
Currently picked

Pytorch, Image Segmentation, MaskRCNN; Coco dataset, 40GB
Pytorch, Translation, Transformer; WMT English-German dataset, 1.3 G
Pytorch, Forecasting, TFT; electricity and traffic benchmark datasets.

Issue 1: transformer image built based on nvidia driver 465, current machine installed driver 460. Container cannot run.
Upgrade machine driver version to 470.
Accidentally upgrade kubeadm version from 1.21.1-00 to 1.23, cannot join the cluster (version 1.21).
remove kubeadm, kubelet, kubectl and reinstall with version.

Copy training data to /nfs_3/alnair
Control training time (max epoch/iteration, loss) to end early for testing purpose. Performance data reported after training ends.
Default training use 8 cards. Titan34 only has 7 works.

in the transformer image validation stage, when calculate bleu score against 'valid.raw.de' dataset, trigger OOM issue, try to change dataset different ways, cause mismatch stream length. Not sure the detailed issue, comment the bleu score function for now.

Transformer image save checkpoint, one file is 2.7GB! And after one success run and saved checkedpoint, training will not rerun next time launch the job. Checkpoint file is found in the reference path, so no re-computation.


travis: add matrix for postgres

This updates our CI to test Postgres 9.4, 9.5, and 9.6.

Removed Go versions?

Testing against tip of Go isn't super useful unless we were maybe benchmarking things. It also makes the matrix very large 2*3


FetchServer No headers on Response object

I noticed that headers are somehow not passed to Response object.
I have a simple setup like this
const restServer = new FakeRest.FetchServer('http://localhost:3000');
restServer.toggleLogging();
restServer.init(data);
restServer.addResponseInterceptor(function (response) {
  console.log('Response interceptor', response);
  return response;
});
fetchMock.mock('begin:http://localhost:3000', restServer.getHandler());

// and somewhere in the code
fetch('http://localhost:3000/scans?' + queryString, { headers })
    .then(res => {
      console.log('fetch response headers', res.headers);
    });

FetchServer log shows correct headers.

I tried with fetchMock version 5 and the newest 9, same results.
Tested on Chrome and Firefox.

Nevermind, Headers are not showing properties like any other simple object. I should use get method to get header property. My bad, closing this.


Remove Blue squarre qui resize l'image

Hi,
My issue is the following :
If I want to put a large image in my component and the size exceeds a blue square appears to resize the image, how do I remove this feature?
This square appears when there is a scollbar (circled in red on the image)
In the second image we can see that the square continues to the full size of the image.
As requested above I only want to remove the blue square and leave the image size. Just be able to scroll in my component
Thanks

This issue is fixed in version 3.0.0.
It is expected that it will take several months to deploy.


Fix replay component position while editing message

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/19398
PROPOSAL: https://github.com/Expensify/App/issues/19398#issuecomment-1557638104
Tests

Open the app
Open any report
Hover on any message send by you, click on reply in thread and add new message in it
Revisit the original report and add emoji reaction to it (observe that emoji reaction and '1 Reply' message is aligned vertically)
Edit the parent message used in step 3 and observe that '1 Reply' message should be aligned to composer start as emoji reaction

[x] Verify that no errors appear in the JS console

Offline tests

Same as above
QA Steps

Open the app
Open any report
Hover on any message send by you, click on reply in thread and add new message in it
Revisit the original report and add emoji reaction to it (observe that emoji reaction and '1 Reply' message is aligned vertically)
Edit the parent message used in step 3 and observe that '1 Reply' message should be aligned to composer start as emoji reaction

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[X] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

Android

Reviewing in an hour

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/MonilBhavsar in version: 1.3.24-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@dhairyasenjaliya Offline QA for this PR is failing because of this issue https://github.com/Expensify/App/issues/20265

🚀 Deployed to production by https://github.com/roryabraham in version: 1.3.24-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
failure ❌

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/roryabraham in version: 1.3.24-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
cancelled 🔪

🍎 iOS 🍎
cancelled 🔪

🕸 web 🕸
success ✅


Deprecation warning due to invalid escape sequences

Deprecation warnings are raised due to invalid escape sequences. This can be fixed by using raw strings or escaping the literals. pyupgrade also helps in automatic conversion : https://github.com/asottile/pyupgrade/
find . -iname '*.py' | grep -v example | xargs -P4 -I{} python3.8 -Wall -m py_compile {}
./qtawesome/icon_browser.py:110: DeprecationWarning: invalid escape sequence \.
  reString += "^%s\." % group

Hi @tirkarthi thanks for the suggestion! Would you like to implement/check the changes that would need to be done? Let us know :)


CB-9657 DataLake runtime version is null

See detailed description in the commit message.

still need to test it e2e, but ready for review


Set max size on images for mobile

Thanks for all these notes! I just pushed some updates to address all the items from your Jekyll Talk comment. Some of the design elements are a bit remedial, I know, but definitely an improvement on the site before your feedback.


Add registered_parameter_handlers property to ForceField

Resolves https://github.com/openforcefield/openforcefield/issues/369 and makes it I don't have to do for handler_name in ff._parameter_handlers.keys(): ... when trying to splice out individual ParameterHandler objects in a force field that was passed to the system
There is a potentially-more-elegant solution proposed in the issue; this is the easier approach

[x] Tag issue being addressed
[x] Add tests
[x] Update docstrings/documentation, if applicable
[ ] Update changelog

Codecov Report

Merging #632 into master will decrease coverage by 17.14%.
The diff coverage is 100.00%.


Disable fullscreen button if fullscreen is disabled

Some inspiration for how to disable the button from https://www.smashingmagazine.com/2021/08/frustrating-design-patterns-disabled-buttons/

After making the PR, I remembered about https://github.com/muxinc/media-chrome/discussions/134.
The question is does this make fullscreen an unavailable thing? In some ways, I think that the behavior of showing the button but having it be disabled is the correct one for this. For example, if you're putting your player in an iframe, you can see that the button doesn't work and maybe you won't notice if the button isn't there altogether.

After making the PR, I remembered about #134. The question is does this make fullscreen an unavailable thing? In some ways, I think that the behavior of showing the button but having it be disabled is the correct one for this. For example, if you're putting your player in an iframe, you can see that the button doesn't work and maybe you won't notice if the button isn't there altogether.

I can get on board with that but for this first change I would keep it consistent with pip, airplay, cast, etc.
the users still are free to do what they like with that [media-fullscreen-unavailable] attribute CSS selector.
I would say yes, it makes fullscreen unavailable in that context. it's disabled for that user.

yeah, I'll update this PR to make a fullscreen-unavailable. Based on the discussion in #134 it seems like media-chrome doesn't do default styles for unavailable currently.


issue #291 mutability of headers

Signed-off-by<EMAIL_ADDRESS><EMAIL_ADDRESS>Description
This change initializes request headers by value, instead of reference, from connection headers. A test is added to confirm that correct behavior.
Issues Resolved
https://github.com/opensearch-project/opensearch-js/issues/291
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Good morning, @mmtdm
we're investigating why this PR does not trigger the github workflows to run the tests for this change. I also notice that Github actions have been disabled on your fork of this repo: https://github.com/mmtdm/opensearch-js/actions. I wonder if it's related. Let me know if you're able to restore github actions on your end while we wait to hear back from github support.
Thank you for your patient.

github throttled my account for running too many actions. I just re-ran actions for this MR and it failed here, please advise

We introduced a CHANGELOG, add a line to it describing your change, please.

@mmtdm Looks like you need to rebase your main. Generally I recommend working off a branch and keeping your main in sync with upstream to make it easier.

on it, thank you

not sure why github reporting there is merge conflict on changelog.md here, I cannot see any conflict. Also not sure why so many extra commits appear in commit history of this MR, it should only modify three files, changelog, connection.ts, and test

@dblock @nhtruong looks like things are good to go


HamiltonianGate

Introducing HamiltonianGate, and tests. Tests pass. Also allows complex resolution of ParameterExpression.
Summary
HamiltonianGate takes a hermitian matrix or Operator and time parameter (I wanted to name this t but pylint didn't let me), and resolves to a Unitary gate equal to e^iHt. This allows such evolutions to be added to a circuit and the time parameter bound later.
Context: I believe this will be a major performance improvement in Aqua simulation, avoiding constructing large evolution circuits for ansatze like UCCSD.

I wanted to name this t but pylint didn't let me

You can edit .pylintrc and insert t as a good-name

@ajavadia should I?

This can quickly lead to trouble if the user does not use normalized units for their Hamiltonian.  For example:
A = array([[1000,  0],
           [0, 1000]])

fails because of the expm

This can quickly lead to trouble if the user does not use normalized units for their Hamiltonian. For example:
A = array([[1000,  0],
           [0, 1000]])

fails because of the expm

I tried this and it seems to work ok. What's the failure you're thinking of?

Namely that this
https://github.com/Qiskit/qiskit-terra/blob/00a53690e5c06d66fb0bc42a5059a999add98179/qiskit/extensions/hamiltonian_gate.py#L82
will fail.

I see this:
>>> A = np.asarray([[1000,  0],[0, 1000]])
>>> scipy.linalg.expm(-1j * A)
Out[6]:
array([[0.56237908-0.82687954j, 0.        +0.j        ],
       [0.        +0.j        , 0.56237908-0.82687954j]])

Am I missing something?

@mtreinish would you mind approving? It says I still need your approval as a codeowner for some reason (even though kdk already approved).

I am not a big fan of the name as it makes me think it is not simply a unitary with a  Hermitian matrix as the input.  This being said i have wasted 20 min thinking of a name and i cant get a better one so im good.

Thanks! Will correct the typo in the changelog


(hitch + nixos/services/hitch): (init at 1.4.8)

Motivation for this change
Add the Hitch TLS reverse proxy as an option for TLS termination.
Things done

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

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

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[n/a] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

cc @Dridi @daghf if hitch would drop ambient capabilities like cap_net_bind_service it would be feasible to start it without root. There also a number of other service hardening option in systemd that could be implemented, but those are usually better maintained upstream, because without inside knowledge they are hard to maintain https://github.com/NixOS/nixpkgs/blob/master/nixos/modules/services/web-servers/traefik.nix#L105

Whoops, sorry about the churn. I was doing some housekeeping.

Removed bin. Thanks for the review!


Build Error : Can't find variable H19 in CertiGC

I was trying to build CertiGraph. But build fails with the following
File ".//CertiGC/verif_forward1.v", line 164, characters 74-77:
Error: The variable H19 was not found in the current environment.
I am on the latest commit 786e7ed1172b9025990cd849077e7103b8c64e47
of  branch "live"

Could you please tell me the version of Coq you are using to build CertiGraph?

Later I ran the command "opam install --deps-only . " in the project directory to install required versions.
Now I am using Coq version 8.16.1.
The previous error is gone  and now getting this one.
File ".//binheap/verif_binary_heap.v", line 361, characters 99-104:
Error: Tactic failure: Classical tauto failed.

Some examples in the CertiGraph project are outdated in new versions of Coq or VST. You can run make -k to ignore the uncompilable examples. At least the core formalization part of graph theory and the verification of the garbage collector still work.

This time with make -k build finished .
Maybe irrelevant but
How is VSCoq ? What's your setup for Coq? CoqIDE, Proof General or VSCoq ?

I'm using Proof General.

Thanks a lot.


Added client.spectateModeToggle()

Switches between free view and leader locked view on agar.io official servers, on Ogar server switches the client being spectated and cycles through them.
I'm not 100% sure on the naming of the method, but I ran some quick tests using a spectator bot and it appeared to work pretty spiffy.  Implements #20 as suggested by @henopied, furthermore, the moveTo() after the mode toggle works like a champ.

Hi.
Great work!
According to wiki packet 19 is sent when Q is released so sending 19 is necessary, so can you please remove comment from line 511?
Meanwhile i will write readme and changelog.
Thank you.


How to get raw binary files for sleipnir-dataset

Hello
How can I collect binary files for your dataset? I want to train my model based on your dataset but it requires raw binary files rather than extracted files.
Thanks

Hi @vietvo89 ,
We created the corpus of malicious and benign PE files from VirusShare [3] and internet download sites.
Due to license issues, unfortunately, we can not share these binary files and we have just shared the extracted features as you mentioned.
If you are interested in binary files, then we suggest collecting them on your own.
Hope it helps.
Best,

Hi @ash-aldujaili
I see your point and thank you for your reply. Just one more thing. For the benign ones, have you gotten them from VirusShare or any specific download sites? I have sufficient malware samples and need more benign samples. I know VirusTotal (not VirusShare) can provide both of them but with enterprise access that costs a lot of money. I think it is inevitable but at this stage of my research, I am looking for a small dataset for demonstration and proposal first.
Thanks


Rolling back to 2.3.1

I'm trying to roll back to 2.3.1 from 2.4 as its  breaking my modules. I have tried to download the manifest link but the one provided (which says 2.3.1) Just downloads 2.4

This manifest will download 2.3.1 https://github.com/foundryvtt/dnd5e/releases/download/release-2.3.1/system.json
I'd recommend heading to the discord to help troubleshoot this.

I tried the link but it  came up with invalid URL

Uninstall the DnD system, then click the Install System button and paste the URL in the bottom, it will then install 2.3.1

You will need to then restore your world from your backup made before launching it with 2.4.0

Huh... If click install it will instantly install 2.4, i don't get an option to add a link to the manifest url.

Head to the Discord to troubleshoot.


Diagnose firewall inter-cluster and nat-discovery not working on Azure clusters

What happened:
When subctl diagnose firewall ... inter-cluster as well as nat-discovery commands are executed on Azure OCP clusters, it was seen that even though the necessary ports were opened and all e2e tests were passing, the diagnose commands were returning error.
[sgaddam@localhost aws-ocp]$ subctl diagnose firewall inter-cluster --context sgaddam-azure-spoke1 --remotecontext sgaddam-azure-spoke2
 ✗ Checking if tunnels can be setup on the gateway node of cluster "sgaddam-azure-spoke1"
 ✗ The tcpdump output from the sniffer pod does not include the message sent from client pod. Please check that your firewall configuration allows UDP/4500 traffic on the "subgw-southce-43b688-lswfm" node. Actual pod output:
....a.....Z$BVS...8... ...%!S(MISSING)+...g.P.9...Psk.1."..X.Q.h
07:22:14.697006 eth0  In  IP <IP_ADDRESS>.4500 > <IP_ADDRESS>.4500: UDP-encap: ESP(spi=0xfa1d61db,seq=0x1b18), length 88
E..t..@.9....f.h.........`....a.....Z$BVS....o..!/.8fY.q"..d.!.xB...9.o^...#:.3.
07:22:14.697132 br-ex In  IP <IP_ADDRESS>.4500 > <IP_ADDRESS>.4500: UDP-encap: ESP(spi=0xfa1d61db,seq=0x1b18), length 88
E..t..@.9....f.h.........`....a.....Z$BVS....o..!/.8fY.q"..d.!.xB...9.o^...#:.3.
07:22:14.752752 eth0  In  IP <IP_ADDRESS>... (truncated)
 ✗ Could not determine if Tunnels can be established on the gateway node of cluster "sgaddam-azure-spoke1"
Error running command: the tcpdump output from the sniffer pod does not include the message sent from client pod. Please check that your firewall configuration allows UDP/4500 traffic on the "subgw-southce-43b688-lswfm" node. Actual pod output:
....a.....Z$BVS...8... ...%S+...g.P.9...Psk.1."..X.Q.h
07:22:14.697006 eth0  In  IP <IP_ADDRESS>.4500 > <IP_ADDRESS>.4500: UDP-encap: ESP(spi=0xfa1d61db,seq=0x1b18), length 88
E..t..@.9....f.h.........`....a.....Z$BVS....o..!/.8fY.q"..d.!.xB...9.o^...#:.3.
07:22:14.697132 br-ex In  IP <IP_ADDRESS>.4500 > <IP_ADDRESS>.4500: UDP-encap: ESP(spi=0xfa1d61db,seq=0x1b18), length 88
E..t..@.9....f.h.........`....a.....Z$BVS....o..!/.8fY.q"..d.!.xB...9.o^...#:.3.
07:22:14.752752 eth0  In  IP <IP_ADDRESS>... (truncated)

subctl version: v0.15.0-rc0

[sgaddam@localhost aws-ocp]$ subctl diagnose firewall nat-discovery --context sgaddam-azure-spoke1 --remotecontext sgaddam-azure-spoke2
 ✗ Checking if nat-discovery port is opened on the gateway node of cluster "sgaddam-azure-spoke1"
 ✗ The tcpdump output from the sniffer pod does not include the message sent from client pod. Please check that your firewall configuration allows UDP/4490 traffic on the "subgw-southce-43b688-lswfm" node. Actual pod output:

 ✗ Could not determine if nat-discovery port is allowed in the cluster "sgaddam-azure-spoke1"
Error running command: the tcpdump output from the sniffer pod does not include the message sent from client pod. Please check that your firewall configuration allows UDP/4490 traffic on the "subgw-southce-43b688-lswfm" node. Actual pod output:

subctl version: v0.15.0-rc0

What you expected to happen:
subctl diagnose firewall commands should report a message that the required firewall ports are opened.
How to reproduce it (as minimally and precisely as possible):
Install OCP 4.12.10 version on Azure cloud and run the diagnose commands.
I found this issue as part of Submariner 0.15.0-rc0 test-day on Azure clusters and it might be even applicable to other cloud providers as well.
Environment:

Diagnose information (use subctl diagnose all):
Gather information (use subctl gather)
Cloud provider or hardware configuration: Azure with OCP 4.12.10
Install tools: subctl 0.15.0-rc0
Others:

Talking to @aswinsuryan about this, it seems we're stuck between port issues either way (4500 conflict if we move to the gateway node). The long-term answer is to move to LB mode. This is already documented.


child's width is set after mounting, causing a sliding / unintended effect

I think the problem is happening with componentDidMount some where not being invoked on the server with server-side rendering.

@mmahalwy is this still relevant? If so, can you provide more details?


AWS elb creation fails when there are multiple subnets in one AZ

I am trying to launch an ELB with kubernetes from cloudformation. I created the VPC, named it kubernetes-vpc, then,  I created the subnets.
I need the RDS instance for a CI environment, so finally, I launched the RDS instance and the RDS wizard, with my consent, created a new subnet in an availability zone used by another subnet inside kubernetes-vpc.
This is the error message I get when the controller manager tries to attach the instances to the ELB.
kube-controller-manager[2132]: E0806 02:44:42.322509    2132 servicecontroller.go:173]
Failed to process service delta.
Retrying: failed to create external load balancer for service default/mycustomservice:
InvalidConfigurationRequest: ELB cannot be attached to multiple subnets in the same AZ.

The docs should warn about creating multiple subnets in the same availability zone inside kubernetes-vpc or group the AZs before giving their names to the controller manager.

@justinsb

Personally, I think we should just harden the AWS cloudprovider for creating (or selecting) a valid ELB regardless of subnet configuration. Since we can only select one subnet per AWS's requirements, I see a few different ways that we could do this:

Attach a tag to the subnet in which we want to associate ELBs. This would create an easy method for selecting subnets.
Parse the route tables to select a subnet that has an IGW attached -- we could assume a public subnet at that point.

Outside of the main issue, it would also be nice if we had a mechanism for attaching to an existing ELB. Again, modifications would be needed to update the set of listeners:

Make use of labels to group services together in logical groups. This would work well with one of the proposed subnet rules above.
A new option could be added to service definitions to directly identify an existing ELB. This may take more work since it would probably have an impact on APIs above the cloudprovider layer, but this would allow for a high level of flexibility.

@justinsb @satnam6502  Do you mind weighing in on what should be a proposed/acceptable solution for selecting an appropriate subnet and/or load balancer when creating a service? I have some free time to work on the fix, but I think a consensus on a method for and priority of selection should be made first.

We are trying to form working groups to discuss various aspects of Kubernetes and there will be a group which has external access as one of its main focus items. I would propose that folk on this thread consider joining that group and help discuss/drive a design going forward which has wider consensus. I think improving the situation is a non-trivial work item. @thockin

Hi @eramus - thank you for figuring out the problem and being willing to work on a fix.
The approach I was taking was that we should match by tags, in particular the "KubernetesCluster" tag.  I have a WIP "under-the-hood" document here: https://github.com/GoogleCloudPlatform/kubernetes/pull/11938/files
So we should be tagging the subnets with a KubernetesCluster tag, and we should be filtering on that also.
The default kube-up script does tag the subnet with the KubernetesCluster tag, and it looks like the code will also filter subnets on the KubernetesCluster tag.
So I suspect that either (1) we have a bug or (2) this is another case where the non-kube-up scripts do things a little differently in ways that don't quite work.  The latter is my motivation for writing the "under the hood" document in #11938.
On your point about reusing an existing ELB, I think everyone agrees there.  I think the reason it didn't make V1 is that the security model around it isn't particularly clear; and that we probably would want to do something similar to PersistentVolume / PersistentVolumeClaim, but there simply wasn't time.
@satnam6502 I hope I get invited to the AWS working group :-)

Hi All,
I could see two errors when creating ELB for service with cloudformation kubernetes stack.
Error when service created first time:
creating loadbalancer failed	failed to create external load balancer for service default/service_name: error tagging security group: InvalidParameterValue: Value ( '' ) for parameter Tag key is invalid. Tag key cannot be null or empty. status code: 400, request id: []
When running describe service again (kubectl describe svc service_name):
failed to create external load balancer for service default/service_name: InvalidConfigurationRequest: ELB cannot be attached to multiple subnets in the same AZ.
Please let me know your inputs on this.

@justinsb I've followed these steps with my current k8s cluster:

Attached name: kubernetes-vpc tag  to vpc.
Attached KubernetesCluster: foo tag name to instances and security groups with cloudformation.
Attached KubernetesCluster: foo tag name to subnets and vpc manually.
Launch the service to create the ELB.

It didn't work, I got InvalidConfigurationRequest: ELB cannot be attached to multiple subnets in the same AZ. from the events log.
I finally deleted the extra subnet and now all my subnets are unique inside each AZ; this is a workaround but k8s is able to create ELBs. The extra subnet wasn't necessary in my case, it was just an accident after a lousy RDS instance creation; however, there must be use cases for multiple subnets in the same AZ.

Tagging really isn't sufficient here, though is a place to start.  We really want the ability to create both "public" LoadBalancers (for Internet facing services) and "private" LoadBalancers for use only within the VPC by other non-Kubernetes instances.  I think that requires subtyping of the LoadBalancer so an appropriate subnet can be chosen - perhaps allow a subnet tag to be passed into the Service config for this case?
In addition, we also want services exposed as LoadBalancers to be able to provide friendly names through DNS CNAME records - but that's probably a separate request :)

So the fix works in the sense only one subnet per AZ is picked but it doesn't really work because it picks the subnets randomly so in my case it picked up subnets that are private so the ELBs couldn't be reached. There doesn't seem to be a reliable way to determine if subnets are public or private (looking at the route table and check if traffic is sent to an internet gateway?) so it looks like we really need what @chrisleck-old-personal suggested i.e. the ability to pass which subnets should be used. It doesn't seem there is any ticket about this issue, although #16083 seems related. At the moment it's pretty much impossible to use ELBs in AWS with a standard vpc topology.

+1 to @jtblin

+1 to @jtblin

+1 on this issue. Is the fix available in V1.1.7? I used this version today and I still get the error "InvalidConfigurationRequest: ELB cannot be attached to multiple subnets in the same AZ."

I submitted a PR (#17912) for that but there is some discussion around whether it is actually needed.
Tagging the subnets properly fixed the issue for me in the meantime, see https://github.com/kubernetes/kubernetes/blob/master/docs/design/aws_under_the_hood.md.

So what if I want some ELBs to be in private and some in public subnets? Is that something people think as being valuable? Currently, all my ELB management is via Terraform, and I only use NodePort in Kubernetes. More control on ELBs from k8s would be very helpful.

@manojlds Just curious, how do you use NodePorts? Do you just assign some static IP to a minion/node and use the port with it?

@gopinatht - i point the ELB at the ASG of kubernetes nodes and configured to look at the NodePort for the corresponding service.

@manojlds thanks! did not know we could do that but that makes sense.

Tagging the subnets doesn't work well in all circumstances - for instance, I'm not using kube-up, and some of my clusters go into VPCs that I cannot edit the tagging of. Passing a flag with allowed subnets is greatly preferred.

@jcderr I don't think we require a tag on the VPC (if we do, we can probably relax that requirement).  But - at least for now - k8s realistically runs best in its own subnet that it "owns".  This issue is pretty meandering, so if tagging subnets is a problem, perhaps you can open a new one, and explain your particular use case!
And you should use kube-up :-)


:construction_worker: feat: Update changeset to mud version

Description
Updates changeset to the same as mud in https://github.com/latticexyz/mud/pull/1036
Testing
Explain the quality checks that have been done on the code changes
Additional Information

[ ] I read the contributing docs (if this is your first contribution)

Your ENS/address:

Current dependencies on/for this PR:

main

PR #185

PR #186

PR #187

PR #188

PR #189

PR #190

PR #197   👈

This comment was auto-generated by Graphite.


Invalid memory address or nil pointer dereference on vm.Delete()

Hi!
Function Delete for VM fails with
runtime error: invalid memory address or nil pointer dereference
My code
ctx := context.Background()
// Use vm.Status != "stopped" because vm.IsStopped()/vm.IsRunning() always returns 'false'
if vm.Status != "stopped" {
	task, err := vm.Stop(ctx)
	if err != nil {
		log.Error(err)
		return err
	}
	status, completed, err := task.WaitForCompleteStatus(ctx, 10, 3, 5, 10)
	if err != nil {
		return err
	}
	if !status && !completed {
		return fmt.Errorf("cannot stop vm %v", vmid)
	}
}

task, err := vm.Delete(ctx)
if err != nil {
	log.Error(err)
	return err
}
status, completed, err := task.WaitForCompleteStatus(ctx, 10, 3, 5, 10)
if err != nil {
	return err
}
if !status && !completed {
	return fmt.Errorf("cannot delete vm %v", vmid)
}

vm.Stop works but vm.Delete fails
runtime error: invalid memory address or nil pointer dereference
/usr/lib/go/src/runtime/panic.go:261 (0x450ef7)
        panicmem: panic(memoryError)
/usr/lib/go/src/runtime/signal_unix.go:861 (0x450ec5)
        sigpanic: panicmem()
/home/snels/go/pkg/mod/github.com/luthermonson/go-proxmox@v0.0.0-beta3/virtual_machine.go:54 (0x940e5b)
        (*VirtualMachine).HasTag: if v.VirtualMachineConfig.Tags == "" {
/home/snels/go/pkg/mod/github.com/luthermonson/go-proxmox@v0.0.0-beta3/virtual_machine.go:337 (0x943616)
        (*VirtualMachine).deleteCloudInitISO: if v.HasTag(MakeTag(TagCloudInit)) {
/home/snels/go/pkg/mod/github.com/luthermonson/go-proxmox@v0.0.0-beta3/virtual_machine.go:324 (0x943436)
        (*VirtualMachine).Delete: if ok, err := v.deleteCloudInitISO(ctx); err != nil || !ok {
/home/snels/git/pve-api-gateway/pkg/pve/vm.go:542 (0x952464)
        deleteVM: task, err := vm.Delete(ctx)

Am I doing something wrong or is the problem in the module?

how did you make the vm you are making these Delete calls against? because it's complaining that the vm config is nil and that is populated here: https://github.com/luthermonson/go-proxmox/blob/main/nodes.go#L76-L78
did you not make the vm via node.VirtualMachine(ctx, id)?

you can use beta4 release now which has a nil check and won't error there... the delete is checking for an existing cloud init iso made by the package and if the config is empty it can't really do that so we will just continue on. you should consider before manipulating your vms though to pull full info for the vm via node.VirtualMachine as it gives you the most complete information for that vm


Sound remix

@DevonBird just a heads-up. I'm going to merge this real soon. It has a bunch of fixes in it for the soundtest panel, and implements the spin powerup sounds.

Fixes lots of things in #89


ONNX import/export: Upsampling

Description
Support ONNX import/export of Upsampling operator.
Fixes #12851
Depends on https://github.com/apache/incubator-mxnet/pull/15811
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[x] Changes are complete (i.e. I finished coding on this PR)
[x] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[x] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[x] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

Add ONNX importer/exporter, relevant test

Comments

This depends on another PR which adds support for tuple of scales in upsampling operator. Ack: @benhe2011 for testing this PR and updating upsampling operator.

@mxnet-label-bot add [ONNX, pr-awaiting-review]

Depends on #15811

if it depends on the above PR, which is not merged, then how are the tests passing?

Any update on this PR?

Any  development? Also facing an Upsampling issue trying to import:
https://github.com/onnx/models/blob/master/vision/style_transfer/fast_neural_style/models/opset8/mosaic.onnx

Thanks for working on this, I am interested in exporting a model to ONNX with Upsampling (nearest). Currently it complains AttributeError: No conversion function registered for op type UpSampling yet..
It would really great if this PR can move on and get merged.

I'd like to reiterate what @oeway said by first thanking you for working on this. Also, please note there is no way to redesign a model around this problem as alternatives such as repeat and deconvolution also cause the export to fail. This problem has been lingering for quite some time. Maybe @szha can assign this to someone.
Thank you

@jeremiedb @oeway @oriori I have asked( offline) @vandanavk to rebase the PR. Once she does, I will review/merge the PR.

Pinging @vandanavk. BTW, since master branch is for 2.0 development and Upsampling op will be reorganized elsewhere, based on the change, I recommend switching the target branch to 1.x instead.
cc @sandeep-krishnamurthy on ONNX op coverage

@vandanavk @anirudhacharya @kreid415 @jeremiedb @oeway Sorry to bother you again, I want to import ONNX model from MXnet, I changed my corresponding file according to Files changed, another error occurred after I changed:
Traceback (most recent call last):
  File "/home/amax/anaconda3/envs/tvm-build/lib/python3.8/runpy.py", line 194, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/home/amax/anaconda3/envs/tvm-build/lib/python3.8/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/home/amax/.vscode-server/extensions/ms-python.python-2021.11.1422169775/pythonFiles/lib/python/debugpy/__main__.py", line 45, in <module>
    cli.main()
  File "/home/amax/.vscode-server/extensions/ms-python.python-2021.11.1422169775/pythonFiles/lib/python/debugpy/../debugpy/server/cli.py", line 444, in main
    run()
  File "/home/amax/.vscode-server/extensions/ms-python.python-2021.11.1422169775/pythonFiles/lib/python/debugpy/../debugpy/server/cli.py", line 285, in run_file
    runpy.run_path(target_as_str, run_name=compat.force_str("__main__"))
  File "/home/amax/anaconda3/envs/tvm-build/lib/python3.8/runpy.py", line 265, in run_path
    return _run_module_code(code, init_globals, run_name,
  File "/home/amax/anaconda3/envs/tvm-build/lib/python3.8/runpy.py", line 97, in _run_module_code
    _run_code(code, mod_globals, init_globals,
  File "/home/amax/anaconda3/envs/tvm-build/lib/python3.8/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/home/amax/zmb/segnet_tvm/net_random/to_onnx.py", line 69, in <module>
    load_onnx_mxnet()
  File "/home/amax/zmb/segnet_tvm/net_random/to_onnx.py", line 62, in load_onnx_mxnet
    sym, arg = onnx_mxnet.import_model(onnx_path)
  File "/home/amax/anaconda3/envs/tvm-build/lib/python3.8/site-packages/mxnet/contrib/onnx/onnx2mx/import_model.py", line 59, in import_model
    sym, arg_params, aux_params = graph.from_onnx(model_proto.graph)
  File "/home/amax/anaconda3/envs/tvm-build/lib/python3.8/site-packages/mxnet/contrib/onnx/onnx2mx/import_onnx.py", line 115, in from_onnx
    mxnet_sym = self._convert_operator(node_name, op_name, onnx_attr, inputs)
  File "/home/amax/anaconda3/envs/tvm-build/lib/python3.8/site-packages/mxnet/contrib/onnx/onnx2mx/import_onnx.py", line 61, in _convert_operator
    op_name, new_attrs, inputs = convert_map[op_name](attrs, inputs, self)
  File "/home/amax/anaconda3/envs/tvm-build/lib/python3.8/site-packages/mxnet/contrib/onnx/onnx2mx/_op_translations.py", line 806, in upsampling
    scale = tuple(new_attrs.get('scale'))[2:]
TypeError: 'NoneType' object is not iterable

Since I'm new to these, I don't quite understand what the error is. By the way, can Upsample be imported into MXNET so far? Has this been achieved? Thank you and look forward to your reply.


feat: Generic Database Adapter

WIP: Adds a generic database crate.
This is the culmination of several ideologies of what storage should look like, taking notes from RocksDbAdapter, MicroKV and RocksDB.
Overview:

Has columns or namespaces similar to RocksDB or MicroKV, except unlike MicroKV there isn't a need for secret passphrases
KV pairs are serialized in the same manner as RocksDB
Interaction isn't broken between the current RocksDbAdapter even if switched out for DbAdapter
Testing can be more in line with actual storage than with MockTreeStore
Generics make it easy to change the backing DB if we should want to move away from RocksDB
Potential to use it for integral_db's table code

Closing for now, may reopen later if needed.


Add 1-31 release branch support

Issue #, if available:
#2399
Description of changes:
Add EKS-D 1-30 release branch support for build-tooling projects.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve

/test metrics-server-presubmit

/test bottlerocket-bootstrap-tooling-presubmit

/test bottlerocket-bootstrap-tooling-presubmit

/test validate-generated-presubmit


Hookup a basic scheduler to consume tasks from the cloud run pubsub q…

…ueue.
This runs in kubernetes now because it will eventually need to create k8s pods.
Creating from inside the cluster is easier than allowing access from outside.

Right now this just logs the payload. Up next is time to deserialize and create pods!

Right now this just logs the payload. Up next is time to deserialize and create pods!


Introduce queryWith

This allows to install an additional hook to be installed, so that you can execute some arbitrary action whenever the files that you are watching are modified.
The diff as shown by GitHub is a little messy, but the changes are minimal: we record an optional OnModified hook in the _cache; query is now a thin wrapper around the more general queryWith, which just ensures that the hook passed gets added to the cache, and the event processing loop in newFileCache is modified to execute the hook whenever we remove an entry from the cache.

Thanks for this PR!


Add mechanism to link templates versions to generator versions

We should have a mechanism to figure out which versions of the generator are supported by each template.
Proposed solutions:

Have a metadata field on the template config file indicating the minimum Generator version it works with and probably the maximum version too. It could be a version range or we directly assume it works with the whole major version.
Have the generator as a dependency of the template. This way, people will install and use the template from the template instead of from the generator. Not incompatible with the previous approach.

Added the generator param to all the templates (except the python and typescript ones):

https://github.com/asyncapi/java-spring-template/pull/23
https://github.com/asyncapi/java-spring-cloud-stream-template/pull/21
https://github.com/asyncapi/nodejs-template/pull/10
https://github.com/asyncapi/nodejs-ws-template/pull/6
https://github.com/asyncapi/markdown-template/pull/12
https://github.com/asyncapi/html-template/pull/18


[question/request] processing stdin?

With other tools like black one can pass a file via stdin cat myfile.py | black - and it will be formatted.
Could ruff do something similar cat myfile.py | ruff -, or does ruff need to know the path of the file?
This could be helpful in the case where an editor would pass the contents of a buffer via stdin and get those contents ruffed.
Thanks in advance

(So broadly speaking: we output the errors, unless you pass --fix, in which case we pass you the fixed contents.)

aha, ok thanks adding --fix flag does the trick 🎊 cat setup.py | ruff - --fix


Rendertron returning base href of Angular application as "https://null"

Rendertron version: 3.1.0
Angular version: 11.2.14
I have Rendertron running in an azure container and being accessible through the URL of an azure App Service. I am using Firebase cloud functions to divert traffic to this based on https://github.com/justinribeiro/pwa-firebase-functions-botrender/blob/master/functions/index.js
When I use the app service from Azure, the base href gets written to "https://null" which causes a bunch of issues in trying to find assets from relative URLs. The base href is usually '/'
<base href="https://null">
Example of errors I get because of this:
aEhtQi9K2tljTpIw6lHk:36 GET https://null/assets/styles/cookieconsent.min.css net::ERR_NAME_NOT_RESOLVED
aEhtQi9K2tljTpIw6lHk:40 GET https://null/styles.7723db603dedc70e2fc3.css net::ERR_NAME_NOT_RESOLVED
aEhtQi9K2tljTpIw6lHk:66 GET https://null/assets/img/logo.svg net::ERR_NAME_NOT_RESOLVED
null/assets/site.webmanifest:1 GET https://null/assets/site.webmanifest net::ERR_NAME_NOT_RESOLVED
null/assets/favicon-32x32.png:1 GET https://null/assets/favicon-32x32.png net::ERR_NAME_NOT_RESOLVED
null/assets/favicon-16x16.png:1 GET https://null/assets/favicon-16x16.png net::ERR_NAME_NOT_RESOLVED

Somethings I have tried:

Using the rendertron demo that is available at https://render-tron.appspot.com/
Result: It page renders correctly. The base href gets written as the full domain name.

Using a locally running container of my docker image on my laptop
Result: It page renders correctly. The base href gets written as the full domain name.

This issue only seems to be occurring from the instance running in Azure. I have tried upgrading the service plan but that didn't seem to have an effect.
The original plan was P1V2 (which didn't seem to be getting overwhelmingly utilized)
I upgraded up to P3V2 but it didn't appear to cause any different behavior.
I have looked at the logs of my firebase function and it doesn't look like it surpassing the 10 second time limit (but I could be wrong) and I am not sure if that could be the culprit anyway.
Nonetheless, the page does render but not correctly since the relative urls are broken.
I would sincerely appreciate any help you have.
Thank you.

Same

Same here

In general, as we're deprecating the project, you should look into alternative approaches to rendering on the web.


dragging and dropping tabs isn't working

Open a couple tabs, then try to drag one to the left or right and I see:
tab.jsx:63 Uncaught TypeError: this.props.onDragStart is not a function
Screenshot:

This was mostly disabled a few weeks ago with some refactor, I wanted to keep it but linting made not using it needlessly frustrating. No idea if worth to keep as we don't know if we'll have tabs, or just remove it.

I vote removing it


Add dyn keyword support

In rust 1.27 a new "dyn" keyword was introduced:
https://blog.rust-lang.org/2018/06/21/Rust-1.27.html#dyn-trait
This keyword is used in similar places as the mut keyword.

Good point. I will add it as well.

NIce, thanks! Could you also add some tests for the various use cases so that these keywords are tested properly and won't break in future?

Yep, I will look into that. I haven't written a test for a grammar yet, but I will look at your test cases and try to write them accordingly.

Phew, added a couple of test cases. I realized that the impl Type is only recognized in the currently allowed positions. In future impl Traits will be implemented e.g. for local variable declarations and global variables (see https://github.com/rust-lang/rust/issues/34511) to detect those correctly, bigger changes have to be done to the grammar definition. Funnily the impl keyword will be highlighted, but it will be recognized as an impl block for types/traits. I don't think this is worth to be tackled currently.
But in future changes to do correct detection may have other positive side effects. E.g. the angle brackets for generic types are currently not highlighted consistently. When detecting variable declarations including type definitions, this may be fixed as a side effect.

Can this be merged?

Sorry for the delay. Looks very good to me. Thanks a lot for taking the time to cover everything with test cases. Good work!


mpremote: init at 1.20.0

Description of changes
mpremote is an integrated set of utilities to remotely interact with and automate a MicroPython device over a serial connection.

Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 249718 run on x86_64-linux 1

2 packages built:

mpremote
mpremote.dist


Popover position for menu item will alwasy have a 32px gap

Since the MenuList use transform style such as "transform: translate(0px, 32px);" to make it under or on the top of the menu button, if I use popover for a menu item as below:
	<Popover trigger="hover" nextToCursor>
		<PopoverTrigger>
			<Box>
				<MenuItem onKeyDown={(e) =>handleClick(e)} >
					<Text className="menu-item" ref={ref}>{item.name}</Text>
				</MenuItem>
			</Box>
		</PopoverTrigger>
		<PopoverContent>
			<PopoverBody>
				<Text>{item.name}</Text>
			</PopoverBody>
		</PopoverContent>
	</Popover>

The popover position will always have a 32px gap between the Text element.
But if change the transform style for MenuList to margin-top:32px, the position for popover will be correct.

I will close this issue when PR #297 is merged


0.17.0

Document these in release notes:
#667
#679
#561
#403
#224
#665

@dave-doty I finished drafting up the release note, let me know if there's anything you would like to change (or you can edit it yourself).
Additionally, I found a bug that should be addressed before merging to main as this bug only appears on dev and is breaking "Move Group" which is something that is already working in main: #696

What happened to the automated release notes generator? It should have put something here:
https://github.com/UC-Davis-molecular-computing/scadnano/releases


[Feature]: Deploy Shopify CLI App to Linux/Nginx server

What area(s) will this request affect?
Deployment
What type of change do you want to see?
Substantial change to existing feature
Overview
I build a Shopify CLI App at latest version and Shopify has limited choice of deploy solution
Motivation
Im trying to deploy my app to my existing Nginx server. Shopify deployment docs only cover for Heroku or Fly.io [https://shopify.dev/docs/apps/deployment/web]. However, it doesn't work at all
Has Shopify solved this problem? If this problem has solved, please give me a solution

Hi @Mzn98, when you say that

However, it doesn't work at all

Are you getting some errors when trying the steps outlined in the docs?

I solved my own problem. Thanks!

how did you solve it?


Meep improvements

how can we plot refractive index colorbar on meep?
how can we use plot2D when the simulation is 3d?

import gdsfactory.simulation.gmeep as gm
import gdsfactory.simulation as sim
import meep as mp
import gdsfactory as gf

nm = 1e-3

c = gf.components.mmi1x2(cross_section=gf.cross_section.nitride)
fig = c.plot()

# How can we plot the epsilon or refractive index?
sim = gm.get_simulation(c, is_3d=False)['sim']
sim.plot2D(output_plane=mp.Volume(size=sim.cell_size, center=mp.Vector3(0, 0, 0*nm)))

# This does not work
sim = gm.get_simulation(c, is_3d=True)['sim']
sim.plot2D()

@SkandanC
@smartalech
@HelgeGehring

For plotting a 2D slice of a 3D simulation one dimension of size needs to be zero, like
sim.plot2D(output_plane=mp.Volume(size=mp.Vector3(sim.cell_size.x, sim.cell_size.y, 0.), center=mp.Vector3(0, 0, 0 * nm)))

This is how it says to do in the Meep documentation. Perhaos could be a starting poitn for us.

how can we use plot2D when the simulation is 3d?

@HelgeGehring is right. The idea is you need to pass a plane to visualize (specified by a Volume object).

how can we use plot2D when the simulation is 3d?

The output of plot2D() returns the axis handle of the plot. You should be able to loop through this handle until you find the relevant imshow data structure, which you can then use to create a colorbar.
I don't have any examples offhand... the last time I actually did this was when I wrote the function 3+ years ago...

Would it be a good idea to do have something similar to gf.simulation.add_simulation_markers() but with a transparent box added which represents the PML? I feel like this could be useful in creating 3D scenes of Meep sim objects.

Sure that'd be great. Meep PRs are always welcome. 3D rendering with python has come a long way since we first added visualization support to meep.

Thank you Skandan, Alec and Helge
The colorbar seems now more of a meep issue than gdsfactory issue
https://github.com/NanoComp/meep/issues/2286


Landing Page for Design System Documentation

😯 Problem to Solve
We need a compelling landing page for the Nimble Design System documentation.
Initially, this will likely just be the home page of Storybook, or link to it.
💁 Proposed Solution
Here are some examples of landing pages from other design systems:
https://www.fast.design/
https://www.lightningdesignsystem.com/
https://carbondesignsystem.com/
https://spectrum.adobe.com/
https://clarity.design/
https://ni.github.io/design-system/   😁
📋 Tasks

[ ] Create design for landing page
[ ] Implement landing page

As this page will largely be a jumping off point to other areas (for now) where should/could we link it to?

Storybook
Nimble Repo

Specific spots in repo (Issues, for example)

Sample apps
Fuse?? (might confuse folks....not sure)

@rajsite @NIbokeefe @leslieab @RickA-NI @atmgrifter00 @mollykreis @msmithNI @m-akinc @fredvisser @jattasNI

Other ideas, not sure if good:

link to ni.com. Good because it associates the design system with NI. Possibly confusing because ni.com itself doesn't use Nimble.
link to real apps that use design system. e.g. the URL of our major client once it's hosted publicly

https://atlassian.design/components/breadcrumbs/examples
https://m3.material.io
https://spotify.design/article/reimagining-design-systems-at-spotify
https://indeed.design/brand/iconography
https://polaris.shopify.com

Nathan,
There are two pages on this spec.

Page 1 full screen
Page 2 example of a smaller window resize, with scrolling.

Notes:  I've chosen to go with the clean/simple execution for the links (Storybook, Github, etc). If it's too problematic; where the links are overlap on the background we can always go with the "footer" or "card" execution.
XD Spec:
https://xd.adobe.com/view/b9a38ee3-a4ca-42de-9a83-8733bb563876-ecf0/
Production asset attached as SVG.  Reach out to me if you need the illustrator file.


Blazor WebAssembly App template missing

Installed VS 2019 Preview 16.6.0 Preview 2.1, followed the instructions above.  However, at step #5 I cannot proceed because the Blazor WebAssembly App option does not exist.  I tried to follow the instructions here:
https://stackoverflow.com/questions/59272624/missing-visual-studio-2019-blazor-webassembly-app-template
Which pointed me here:
https://www.nuget.org/packages/Microsoft.AspNetCore.Blazor.Templates
Which showed that it was deprecated, and led me here:
https://devblogs.microsoft.com/aspnet/blazor-webassembly-3-2-0-preview-2-release-now-available/
Which finally did work.
I think this could be added to the VS 2019 preview by default.

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

ID: c07e57dc-526f-9479-4695-de7d8f06eb9a
Version Independent ID: 8226ed72-69b2-3c93-a931-218bd11cf9c8
Content: Get started with ASP.NET Core Blazor
Content Source: aspnetcore/blazor/get-started.md
Product: aspnet-core
Technology: aspnetcore-blazor
GitHub Login: @guardrex
Microsoft Alias: riande

It was added. I don't have any information on the current guidance not working for 16.6 Preview 2. Sometimes, devs have had to reinstall the template to get it to appear. Sometimes, upgrading VS exhibits the same behavior and requires a template re-install, and I've sporadically experienced a required re-install myself. Release 3.2 is due to come out in May. After release, Blazor WebAssembly will be supported across-the-board and no separate template install command will be required. I believe that issues pertaining to template install and availability will go away completely at that point.


Consider adding cursor-box API (cursor equivalent of mouse-box)

cursor-box would return the box that the cursor is within (similar to how mouse-box returns the box that the mouse is over).
Without such an API, I'm not sure how to implement features similar to the builtin help feature that annotates the procedure name under the cursor with the procedure's input names. Here's an example of that builtin help feature. If I type the procedure name item:

and then hit ctrl+?, then the procedure name gets annotated with the names of its parameters: N and BOX:

I don't think that could be implemented without knowing which box the cursor is in.

I think that self plays this role for the cases that I care about. When you begin executing some code (e.g. by hitting a keyboard shortcut you've registered), self refers to the box where execution began which is probably also where your cursor is.


testing for impossible inputs needs to be removed

you still have testing for impossible inputs, like aphasia on the left with neutral dominant hemisphere, which shouldn't even be allowed and won't be possible from the checkboxes. I removed these in the past and you reverted the changes.
As even the master branch is failing, it has become a huge tangle of issues and failed testing, some of which seem based and different interpretations on what should actually be happening under the hood?

you still have testing for impossible inputs, like aphasia on the left with neutral dominant hemisphere, which shouldn't even be allowed and won't be possible from the checkboxes. I removed these in the past and you reverted the changes.

I'll remove the tests for impossible inputs. You didn't say why you removed them.

As even the master branch is failing, it has become a huge tangle of issues and failed testing, some of which seem based and different interpretations on what should actually be happening under the hood?

I'm not sure what you mean. If it's not related to the tests you mention, you can create a new issue.

Also, if they are impossible, shouldn't the package raise an error when being queried?

Please let me know what  you think about this: https://github.com/thenineteen/Semiology-Visualisation-Tool/issues/56#issuecomment-610560205

erm, depends what you think the package does, or want it to do.
if there are no checkboxes, why waste time giving errors that won't be utilised?
this is part our teething issues as we try to mould everything together including GUI


FINERACT-986: Update spotbugs to v4.2.0

Update spotbugs to v4.2.0
Description
Describe the changes made and why they were made. Ignore if these details are present on the associated Jira ticket
Checklist
Please make sure these boxes are checked before submitting your pull request - thanks!

[ ] Commit message starts with the issue number from https://issues.apache.org/jira/projects/FINERACT/. Ex: FINERACT-646 Pockets API.

[ ] Coding conventions at https://cwiki.apache.org/confluence/display/FINERACT/Coding+Conventions have been followed.

[ ] API documentation at fineract-provider/src/main/resources/static/api-docs/apiLive.htm has been updated with details of any API changes.

[ ] Integration tests have been created/updated for verifying the changes made.

[ ] All Integrations tests are passing with the new commits.

[ ] Submission is not a "code dump".  (Large changes can be made "in repository" via a branch.  Ask on the list.)

Our guidelines for code reviews is at https://cwiki.apache.org/confluence/display/FINERACT/Code+Review+Guide

@vorburger @awasum LGTY?

Of you have to use Suppress (it would be better to avoid it), then please
create a JIRA and add a comment like this: @SuppressWarning("...") // TODO
FINERACT-123

Of you have to use Suppress (it would be better to avoid it), then please create a JIRA and add a comment like this: @SuppressWarning("...") // TODO FINERACT-123
…

Suppress is not helping here. Unfortunately.

I tried forcing the function to be able to accept a null parameter, but that just won't do:
   org.apache.fineract.portfolio.savings.domain.SavingsAccountCharge since first historized release unspecified In class org.apache.fineract.portfolio.savings.domain.SavingsAccountCharge In method org.apache.fineract.portfolio.savings.domain.SavingsAccountCharge.percentageOf(BigDecimal, BigDecimal) Parameter value At SavingsAccountCharge.java:[lines 540-548] value must be non-null but is marked as nullable This parameter is always used in a way that requires it to be non-null, but the parameter is explicitly annotated as being Nullable. Either the use of the parameter or the annotation is wrong.
This got me thinking, why would the default value for a decimal be null instead of zero. It's a glitch that has worked well so far, probably because we never stumble on the crash. The method is vouched to fail if a null value is passed through.

The method is updating the values, in the savings account charge now the null value was there to initialise it , might be the case that it was checking for null values somewhere else while applying the charges and then based on that computing from zero.
This could be interesting to note that we can start to remove all the null values where it should be a bigDecimal as zero functionally .
What are your thoughts ?

Had some other concern, passing a ZERO to the function and performing a ZERO multiplication means the method returns a ZERO. I fear what a bunch of ZEROs everywhere may do to the core system functions.

I just created https://issues.apache.org/jira/browse/FINERACT-987 for this.

@awasum, @vorburger, @maektwain can we conclude this thread on these changes?


More detailed explanation of "host address owned" and "host address scanned"

💡 Summary
Please update the language for the vulnerability scanning report for VS scans to include clarification on host address owned vs host address scanned.
Motivation and context
In support of voice of customer feedback. We were requested to provide additional clarification on the difference between host address owned and host address scanned.
Implementation notes
My recommendation is that we address this in the FAQ section.
Acceptance criteria
How do we know when this work is done?

[] FAQ section updated addressing addresses owned vs scanned.

Currently working on updating the issue requirements.

@cfx47  can you come up with a FAQ or way to capture the difference between the two so we can update the requirements?

Hey @dav3r can you transfer this to the cyhy-reports repository since I do not have the ability do so.

@KeithBonesJr I can move this issue if you want, though as we discussed earlier, one of the items in this issue ("last scope update") will require changes to cisagov/cyhy-core, as well as cisagov/cyhy-reports.
Is there a particular reason you want to move this issue to cisagov/cyhy-reports?  It's fine with me if this issue remains in this repo, but if you have a reason to move it, I'm interested in hearing it.

No we can keep it as is. I completely forgot about the mention of cyhy-core. We can keep it as is.

@jeffkause I updated the requirements to show what has been completed. How do you want to proceed with the last requirement?


Add Target Closure Sensor

Fix https://github.com/iMicknl/ha-tahoma/issues/729

Should we disable the sensor by default?


[Website] Builds using https://pulsar.incubator.apache.org as baseurl switch to TLP address

Motivation
The project graduated three years, but the base url in the website is still using the incubator url.
Modifications
Changed the url is the docusaurus configurations.
Verifying this change

[X] The websites still build with this change.

This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): (no)
The public API: (no)
The schema: (no)
The default values of configurations: (no)
The wire protocol: (no)
The rest endpoints: (no)
The admin cli options: (no)
Anything that affects deployment: (no)

Documentation
Check the box below and label this PR (if you have committer privilege).
Need to update docs?

[X] no-need-doc
The changes are in the website build configurations

Hi @tuteng @urfreespace can you help review? Thanks


Tune the process with what we learned from these interviews

Parent objective:  #33
Progress: 0%

[ ] [P0] Create research on candidates' sentiment towards on-site and remote interviews

Q2 status: subtasks were completed, but the key result itself not. Moving this to Q3.

[P0] Create research on candidates' sentiment towards on-site and remote interviews -> Research and draft done, need to create actual survey, formal survey policy, and send to candidates


fixing go get command in README

The go get command is outdated and referencing the old repo.

Thanks a lot for contributing! :+1:

Wow that was quick. Thank you! :)


Feat: add new sorting icons

Summary of changes

introducing 3 new custom icons: dvSort, dvSortAsc, dvSortDesc
override the lineup default sort icons via css with our custom icons

Screenshots

Additional notes for the reviewer(s)

Thanks for creating this pull request 🤗

Tested in BioInsight :heavy_check_mark:


Atom Beautify could not determine a supported beautifier to handle this file with grammar "Null Grammar" and extension "undefined".

Atom Beautify could not determine a supported beautifier to handle this file with grammar "Null Grammar" and extension "undefined".
1.39.1  mpb，thanks！

format json file，eg：{"status":"new","currUserId":"11111","unReadSize":14}

some stack trace:
TypeError: Cannot read property 'name' of undefined
at HTMLElement.debug (/Users/ql/.atom/packages/atom-beautify/src/beautify.coffee:363:54)
at CommandRegistry.handleCommandEvent (/Applications/Atom.app/Contents/Resources/app/static/:11:348736)
at CommandRegistry.dispatch (/Applications/Atom.app/Contents/Resources/app/static/:11:347211)
at AtomEnvironment.dispatchContextMenuCommand (/Applications/Atom.app/Contents/Resources/app/static/:1:717275)
at EventEmitter.t (/Applications/Atom.app/Contents/Resources/app/static/:1:725281)
at EventEmitter.emit (events.js:182:13)


Fix unPreciseDuration

It should normalize everything to a particular unit and not just remove the constructor. Also, the constants defined in Data.Time.PreciseDuration.Internal should probably be BigInts.

Done in #20


Non-lethal double-barreled shotgun for booze storage

About the PR

Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog

:cl:

tweak: Double-barreled shotgun from bartenders booze storage has been replaced with non-lethal version

lEtS bAbY pRoOf ThE gAmE ThAt SoUnDs LiKe FuN

dont spam useless shit on github

merg, doesnt make much sense to have 2 lethal + 24 nonlethal shells

How can I request a review?


Workitemtype system fields Question

Hello,
For PBI and bug, I am trying to derive different values based on the system.state values like below. For some reason it is showing all for both WIT's. Please help
{
  "version": 1,
  "cascades": {
    "System.WorkItemType": {
      "Product Backlog Item": {
        "System.State": {
          "New": {
            "Custom.SubState": [
              "Ready for Grooming",
              "Ready for Implementation"
            ]
          },
          "Committed": {
            "Custom.SubState": [
              "Blocked",
              "In Code Review",
              "In Dev testing",
              "Merged"
            ]
          },
          "Done": {
            "Custom.SubState": ["Completed"]
          }
        }
      },
      "Bug": {
        "System.State": {
          "New": {
            "Custom.SubState": ["Ready for Implementation"]
          },
          "Committed": {
            "Custom.SubState": [
              "Blocked",
              "In Code Review",
              "In Dev testing",
              "Merged",
              "Needs More Info",
              "Pending Information from Customer"
            ]
          },
          "Done": {
            "Custom.SubState": ["Completed"]
          }
        }
      }
    }
  }
}

Hello @prashanthbv12.
Currently we do not support config with nested multiple layers like in your example. Extension has limitation that its loading maybe delayed due to connection/performance issues. That is why we not recommending to use it with system fields at least for now as it affects overall user experience.
In order to create valid configuration for your cascades take a look at example in Readme


Test improvements

Test that read_dataset() traps and removes bad temperature and/or flux values
Related: should records with bad fluxes be removed entirely? Or just the flux NA'd, like for CSR_TCHAMBER?

Note that the make_cosore_release test is empty

This has been addressed in #89 and #86


added connecting snackbar and snackbar.dart file

Added 'snackbar.dart' file to show the snackbar. I have created this file inside widget folder and then imported it in app.dart and message_list.dart file .
working : I have used "connectivity_plus: ^5.0.2" package to implement this.   This package allows developers to see the connectivity of device . This helps us to determine  whether our device has active internet connection or not .
Video link:-
https://github.com/zulip/zulip-flutter/assets/112092492/911a49a4-568c-4b29-82bc-1c8d0bf5872b

Nice work but it can be improved, according to the commits discipline your commits need some restructure.

thankyou @Khader-1 for your feedback . appreciated your inputs and i will definetly work on it

Thanks @Khader-1 for the initial review! And thanks @satyam372 for the contribution.
For cross-reference: it looks like this started as #583 and then became #586.
@satyam372 For future pull requests, it's better to update the existing PR than to close it and open a new one. See https://zulip.readthedocs.io/en/latest/git/pull-requests.html#update-a-pull-request .


HDDS-8518. Admin SCM decommission command primordial node support

What changes were proposed in this pull request?
Changes to SCM decommission command to support decommissioning of primordial SCM node.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-8518
How was this patch tested?
Manual testing - decommissioning primordial scm node:
Bring up cluster with SCM-HA 3 nodes, primary scm nodeid = scm1
bash-4.2$ ozone admin scm roles
scm1.org:9894:LEADER:3f61f995-7316-47a5-ba1f-255749874c7d:<IP_ADDRESS>
scm3.org:9894:FOLLOWER:9ab89602-7c32-4f52-8c78-5f9a620ef70a:<IP_ADDRESS>
scm2.org:9894:FOLLOWER:35b1e08f-660c-4c7c-86d3-7a02e082b2a8:<IP_ADDRESS>

Transfer scm leader to non-primordial node, scmid=scm3
bash-4.2$ ozone admin scm transfer --newLeaderId=9ab89602-7c32-4f52-8c78-5f9a620ef70a
Transfer leadership successfully to 9ab89602-7c32-4f52-8c78-5f9a620ef70a.

Decommission primordial scm node:
bash-4.2$ ozone admin scm decommission --nodeid=3f61f995-7316-47a5-ba1f-255749874c7d
Decommissioned Scm 3f61f995-7316-47a5-ba1f-255749874c7d

bash-4.2$ ozone admin scm roles
scm3.org:9894:LEADER:9ab89602-7c32-4f52-8c78-5f9a620ef70a:<IP_ADDRESS>
scm2.org:9894:FOLLOWER:35b1e08f-660c-4c7c-86d3-7a02e082b2a8:<IP_ADDRESS>

@neils-dev , thanks for working on this. The patch overall looks good. Could you add a robot smoke test for this decommission process?  Robot test can be put under  hadoop-ozone/dist/src/main/smoketest/scmha.

Thanks @ChenSammi. Added robot test for testing scm decommissioning.  Tested in ozonesecure-ha.

Robot test can be put under hadoop-ozone/dist/src/main/smoketest/scmha.

Thanks @neils-dev, the patch LGTM +1.


Add make format target

We can use yapf for it. Also the CI should check the style

fixed with #39

fixed with #39


error: Failed to open TCP connection to localhost:8080 (Cannot assign requested address - connect(2) for "localhost" port 8080)

error: Failed to open TCP connection to localhost:8080 (Cannot assign requested address - connect(2) for "localhost" port 8080)
I have been tinkering around with docker-compose.yml and some other command line settings, but to no avail, so I thought at this point it might be best to ask here.
On my machine, I have a local web application (built in java) that is running on localhost:8080. It provides the FHIR endpoints that Inferno checks, and separately I have an OAuth microservice running in order to authenticate.
When I have my inferno docker up and running, and I attempt to run the Standalone Patient App - Full Access test, I come across this error.
I figured this was happening because the Inferno container isn't able to access the localhost that I can on my machine. However, I can't for the life of me figure out how to make that possible. Seems like a network bridge is needed, which I've attempted, but I must be doing something wrong in the context of this repo.
Not sure if you folks would know how to help in my peculiar situation, but any help is appreciated.

Some additional info from the container console:
worker_1             | I, [2022-04-08T00:42:59.267681 #1]  INFO -- : Initializing client with http://localhost:8080/api/fhir/r4
worker_1             | I, [2022-04-08T00:42:59.267820 #1]  INFO -- : Configuring the client to use no authentication.
worker_1             | I, [2022-04-08T00:42:59.269268 #1]  INFO -- : GETTING: http://localhost:8080/api/fhir/r4/metadata
worker_1             | E, [2022-04-08T00:42:59.271611 #1] ERROR -- : GET - Request: http://localhost:8080/api/fhir/r4/metadata failed! No response from server: Failed to open TCP connection to localhost:8080 (Cannot assign requested address - connect(2) for "localhost" port 8080)
worker_1             | E, [2022-04-08T00:42:59.272388 #1] ERROR -- : /usr/local/lib/ruby/2.7.0/net/http.rb:960:in `initialize': Failed to open TCP connection to localhost:8080 (Cannot assign requested address - connect(2) for "localhost" port 8080) (Errno::EADDRNOTAVAIL)

UPDATE: Soon after posting this I was able to figure out that my API URL just needs to contain my shared network IP rather than localhost. All good now. Able to authenticate successfully and retrieve an access_token.
However, when I move on over to the Single Patient API Test, the Submit button is disabled/greyed-out on the Run All Tests modal. All the necessary info seems to be there: the FHIR endpoint, the SMART App Launch Credentials, and the Patient ID. Any idea why this could be?

Glad you were able to figure out how to connect to a service on your same machine.  We should add a section in the README or similar with instructions on how to do this.  Using your machine's IP address is one option, another is to use host.docker.internal, which is a host that docker sets up for your containers to connect to the host machine. That works for me, though I've heard others have had issues with that approach.
Hmmm, we should add some kind of message about what is missing, if it isn't obvious.  So you already ran one of the launch tests to get a valid authorization token, then clicked on 'Single Patient API' and then 'Run Tests'?  Could you provide a screenshot of the modal?

I'm glad too, it was rough for a minute there.
Yep that's exactly what I did. Here's a screenshot. I'm wondering if it is due to Patient ID from SMART App Launch field being empty?

Hmmm, I'm not sure why you are getting Patient IDs listed twice.  I take it you are running off a clone of main?  Did you get a patient context in your launch, or did you type in the "Patient IDs (required)" field in the bottom?
At the bottom of the page, what version of inferno-core are you using?

Running off a clone, yep. Cloned the day before yesterday.
No patient context, I typed that patient ID myself.
Same version. 0.2.0
Perhaps I'll try a fresh clone tomorrow morning and see what happens.

Thanks, we'll take a closer look tomorrow, and may have follow-up questions.  I think this issue might be resolved if the previous launch you did provided a patient in context, but there are other strange things going on here I'd like to fix ASAP.  Thank you for the report!

@arscan I was able to execute the Single Patient API tests just now. I realized it was because my OAuth response doesn't contain the patient ID that I authenticated with, which explains why my "Patient ID from SMART App Launch" field was empty.
My team and I will have to go in and add that to our OAuth response, but for now I alleviated this by opening single_patient_api_group.rb and changing that field's locked property from true to false. So now I could manually enter the ID.

@dwebe003
I close this ticket as no activity in the last three month. If you are still experiencing the same problem, you can either create a new issue or reopen this one.
Thank you.


About window is shown incorrect Indigo version

*Steps to reproduce:

Launch Ketcher with the Remote mode
Click on the About button

Expected behavior:
Correct version number is shown
Actual behavior:
The incorrect version <IP_ADDRESS>-gd1a8a571b-x86_64-linux-gnu-10.2.1 is shown

OS: [Windows NT 10.0 Win64; x64]
Browsers: Google Chrome: Version 100.0.4896.88/FireFox: Version 99.0.1 (64-bit)
Ketcher v2.4.2-289-g37dea6b3

Related issue in the Indigo: https://github.com/epam/Indigo/issues/715

Verified as fixed on Release 2.5.0.


Version naming

Installing the package on osx, i notice this warning
/usr/local/lib/python2.7/site-packages/setuptools/dist.py:294: UserWarning: The version specified ('1.32-rcor') is an invalid version, this may not work as expected with newer versions of setuptools, pip, and PyPI. Please see PEP 440 for more details.

Not sure if it is anything to worry about though, so no patch provided :-)
$ ag 1.32-rcor
afl_utils.egg-info/dependency_links.txt
1:https://github.com/rc0r/exploitable/tarball/experimental#egg=exploitable-1.32-rcor

afl_utils.egg-info/requires.txt
1:exploitable==1.32-rcor

setup.py
23:    'exploitable==1.32-rcor',       # needed for gdb script execution
29:    'https://github.com/rc0r/exploitable/tarball/experimental#egg=exploitable-1.32-rcor'

nm the noise. It was my fault for using python 2.7 (system default on osx)

Well, the version naming of the hacked exploitable plugin does not comply with PEP 440 as indicated by the warning.
However I chose this naming in order to avoid conflicts with the original/official exploitable package. (f.e. to avoid pulling the wrong version from PyPI during afl-utils setup).
My hacked version is not intended for publication on PyPI, so I guess this should not be a problem.
afl-utils' setup.py automatically pulls the right exploitable package from my GH and installs it (use a virtualenv!). If you run into problems during setup, feel free to report issues or ask for guidance!

Ah, I see! Yes i had a minor issue with setup, sending a patch.


Change detection loads all labels without a filter.

While the number of labels is relatively low the page loads at a usable speed.
As time goes by the label count will increase. Making the page slower.
Adding a filter (drop down select box or something) for Labels filtered by schema, All schemas being the last option.

I've added filtering for schemas to the footer for easier search, and customized the filter function to search for a substring (any place) rather than just for labels starting with the typed value. I don't think that fetching the data from server is the bottleneck here - could you link a page that feels slow? It's possible that something with multiple <Labels ... /> fetches the list of labels multiple times; I am relying on browser caching to save us from this but maybe Horreum is not hinting the browser enough.

There's several things that could get slow: DB lookup, JSON transfer, rendering. At this point we don't see which part could be the problem, so I won't optimize prematurely.
If you find a case I could analyze & improve, or have a general UX problem with label lookup, please reopen.


Overloads for StartStream that return IEventStream

Works similar to the internal method IEventIdentityStrategy<TId>.StartStream<TDoc>(). Provides 3 ways to create a new stream, returning IEventStream<T> with the supplied aggregate set.

The goal with this pr is to allow the same behaviour for adding events to a stream regardless of if that stream is new or existing.
For example, I can write a service such as the following and call it from a create method and an update method.
public interface IDocumentAuthorService {
    Task AddAuthor(IEventStream<Document> stream, IQuerySession session, string userId);
    void RemoveAuthor(IEventStream<Document> stream, string userId);
}

@jeremydmiller is there anything I should add to this addition?

I am going to close this as it doesnt really matter for 2 reasons

Once a FetchForWriting is done, all subsequent calls to Events.Apply() are automatically optimistic.
Calling FetchForWriting with a non-existent stream has the same effect as this pr's StartStream method.


TypeError XMLWriter::writeAttribute(): Argument #2 ($value) must be of type string, null given

What steps will reproduce the problem? If a null value is placed into the value of the name value pair in a build array.
What is the expected result? Running without this error.
What do you get instead? The above error.
Additional info

Q
A

Version
1.0.?

PHP version

Operating system

This was encountered in the following code when using
use Sabre\Xml\Writer;
 /**      * @var array $this->invoiceLines      * @var array $invoiceLine      */     foreach ($this->invoiceLines as $invoiceLine) {        $writer->write($invoiceLine);     }
This issued can be resolved by inserting an Exception in the code before the array is built ensuring that no null values filter through the code.


⚠ Bofrost.com has degraded performance

In 054b218, Bofrost.com (https://www.bofrost.com) experienced degraded performance:

HTTP code: 200
Response time: 572 ms

Resolved: Bofrost.com performance has improved in d8753d4 after 6 minutes.


Facebook

I need see the friend and the page yo my girls friend

One friend blog me accidentEl 10/05/2017 6:18 a. m., Jonas Gehring<EMAIL_ADDRESS>escribió:Closed #11.
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.