RFP sdkman

http://sdkman.io is a package for technology built on JVM(java virtual machine) such as grails, groovy, gradel etc

I think this package is not available for Windows though, judging from their install page: http://sdkman.io/install.html

@joachimschmidt557 looks like you're right, guess we can just close this one then.
@sufian07 feel free to re-open this issue when windows support have been added to the software.


serverless/next: Return 405 Method Not Allowed for methods that are not being implemented

For Next.js with App Router, any unimplemented methods will return 404 instead of 405:
Taking example from https://github.com/ts-rest/ts-rest/blob/main/apps/example-next/
import { initContract } from '@ts-rest/core';
import { z } from 'zod';

const c = initContract();

export const testContract = c.router(
  {
    test: {
      method: 'GET',
      path: '/test/:id',
      pathParams: z.object({
        id: z.coerce.number(),
      }),
      query: z.object({
        foo: z.string(),
        bar: z.number(),
      }),
      responses: {
        200: z.object({
          id: z.number(),
          foo: z.string(),
          bar: z.number(),
        }),
      },
    },
  },
  {
    strictStatusCodes: true,
  },
);

POST request to /test/:id will return HTTP 404:
{
  "message": "Not Found"
}

I think it's the optimal default behavior to use a 404 response for security reasons, so as not to disclose the HTTP methods available for a given route.

Agree with @LudovicGen. Also with how the routers are implemented, there's no quick way to match an existing path, but for a non-existent method. We'd have to manually add routes for the missing methods, in order to serve up the 405 response, which would just render the entire router slower.
We can't change this anyway, because it would be a breaking change. If you want to serve 405's you can just add them manually for now.


Add bucket replication support

Support to set x-qs-metadata-directive header

cc @owarai,  PTAL

as presented in PR #104, code should be regenerated here.


v1.11 backports 2023-02-27

[x] #23552 -- node: require ipv4 address when wireguard is enabled (@giorio94)

Once this PR is merged, you can update the PR labels via:
$ for pr in 23552; do contrib/backporting/set-labels.py $pr done 1.11; done

/test-backport-1.11

All tests are passed, review is in. Merging this in.


Reconstruction and filtering methods to reduce oscillations

[ ] Gegenbauer reconstruction for Fourier methods, cf. Script 3.18 of Hesthaven (2018) Numerical methods for conservation laws
[ ] Some Padé reconstructions?
[ ] Total variation denoising, cf. Condat (2013) A Direct Algorithm for 1-D Total Variation Denoising
[ ] Total variation denoising with overlapping group sparsity, cf. Selesnick and Chen (2013)

I'm working on it in https://github.com/ranocha/Postprocessing.jl.


EmbeddedInput instead of ReferenceInput to use embedded data coming from the server

I think that along the same lines that EmbeddedArrayInput works there is need for EmbeddedInput that works for one element - something that would solve my issues here: https://stackoverflow.com/questions/46592926/how-to-leverage-embedded-resources-in-referencearrayinput-and-referencearrayfiel
https://stackoverflow.com/questions/46592587/how-to-correctly-render-referenced-entities-in-list-when-i-have-objects-instead
Unless it works for one or many inputs at the same time - I will try it
Thanks!

You can use EmbeddedArrayInput to solve your problem. but you need to write a custom selectbox input to be put inside it.
That select box should return a value like {id: "1", name: "name 1" } and display only the name.
I'm closing this since it's a general AOR question and also application related. it's too far from the purpose of aor-embedded-array


json results type

ldf-query-polling-response and ldf-query-streaming-response-partial return json strings, and ldf-query-streaming-response-end returns a bunch of rows, each as json, concatenated together.
I can't see how anyone would use that concatenated json, so maybe it's better to save time and memory to not collect it.
More importantly, why jsonify the rows for the other events? All callers will just have to parse them. The demo code doesn't even seem to be expecting that json, as it calls JSON.stringify on the e.detail.response strings as if they were row objects.

I simply wrap @RubenVerborgh's browser.js. Ruben, what is your reaction to Drew's remarks above? I guess I am a couple of builds behind and missed the repo rename apparently…

Well, the  data callback here receives a row object or a triple (which is perhaps misleading called chunk here). So basically, by removing the JSON.stringify instances, you can pass the raw JSON object.
About the renaming: the old Browser.js project had the browser version of Client.js. However, we have now changed this. The new Client.js is its own browser version which you can generate through browserify. The new https://github.com/LinkedDataFragments/jQuery-Widget.js is now a jQuery widget that uses the browserified code. I've added [instructions on how to generate a browserified version easily].

@RubenVerborgh, shall we discuss the migration path to the latest version of jQuery-Widget.js over a quick VC (calendar week 38 would work, traveling this week)?

@tomayac It should come down to simply updating dependencies/ldf-client-browser.js to the ldf-client-browser.js which is now generated by Client.js (you wouldn't need jQuery-Widget.js). But we sure can do a VC, ping we when you're available.


[feature] Topology history (snapshots - way back machine)

Implement a way to save daily snapshots of the network topology so users can go back in time and analyse the status of the network in specific past dates.
A switcher in the visualizer shall be added to modify the date of the topology, the switcher should default to "latest" but has to allow to go back in time.

@nemesisdesign I'm thinking to implement it by defining:

[ ] A model named Snapshot with the fields, date, topology and data
[ ] A function named save_snapshot which saves the network graph data in string format by retrieving it from the API.
[ ] A script that will be run by a cron to trigger the save_snapshot function.
[ ] A switcher view which will return the topology data using date and topology.

My doubts are:

Should a cron be written in django-netjsongraph or will that be called from openwisp2? Or maybe both?
How should a switcher look? A date picking tool maybe?

I will focus on replying to the other outstanding issues first, which I hope we can address asap so we can start deploying this app in the openwisp2 ecosystem very soon.
Ping me again on this issue when we have finished the other issues.

@rohithasrk I'm replying to these questions and other on the OpenWISP chat, please update this issue when we have finished discussing

After discussing about the feature with @nemesisdesign, we've come to the following conclusions. We will be defining:

[ ]  A model named Snapshot with the fields: date, topology and data
[ ] A new class function named save_snapshot() of the topology model, which saves the network graph data in string format by retrieving it from the API.
[ ] A new API url/view pair. The url being of the form /api/v1/topology/<uuid>/history/?date=<date> and the view querying the database and returning the data in NetJSON format.
[ ] The switcher will be a date picking tool and a script checking out for the change events which could help generate the network topology graph.
[ ] A command save_snapshot just like update_topology.
[ ] A test suite for the above implementation.

As of now, this is the simplest implementation of the feature and has limitations such as one saving only one snapshot of topology per day, i.e., the data will be overwritten if the save_snapshot function is called more than once in a single day.

@rohithasrk great summary, proceed! 👍

Hi,
a couple of years ago I did something similar to save snapshots of the topology and to make some stats:
https://github.com/leonardomaccari/django-netjsongraph
https://github.com/leonardomaccari/django_easy_network_stats
don't expect great code (my first Django experience) but you may get some ideas.

@leonardomaccari thanks for refreshing my memory, where did you store the data? I see an update model but I can't find where exactly the graph data is stored

@leonardomaccari technical discussion is going ahead on pull request #49


uproot4.iterate on Empty TTree Object

I am using uproot version 4.0.7 iterate to read through several TTree objects.
When a TTree object happens to be empty (i.e. with no entries), I get an error.
I think the correct behavior should be that no error is encountered and the empty Tree is ignored.
I have attached a sample ROOT file with an empty Tree inside:
empty_tree.txt
Please rename empty_tree.txt to empty_tree.root.
The code that fails to read it is:
import uproot
print("uproot.__version__", uproot.__version__)

for dataframe in uproot.iterate("empty_tree.root:empty_tree", ['var'], library='pd'):
	print("dataframe\n", dataframe)

The error message I see is:
uproot.__version__ 4.0.7
Traceback (most recent call last):
  File "iterate_through_empty_tree.py", line 5, in <module>
    for dataframe in uproot.iterate("empty_tree.root:empty_tree", ['var'], library='pd'):
  File "/home/name/.opt/python/miniconda3.8/envs/omega-analysis/lib/python3.8/site-packages/uproot/behaviors/TBranch.py", line 205, in iterate
    for item in hasbranches.iterate(
  File "/home/name/.opt/python/miniconda3.8/envs/omega-analysis/lib/python3.8/site-packages/uproot/behaviors/TBranch.py", line 1316, in iterate
    entry_step = _regularize_step_size(
  File "/home/name/.opt/python/miniconda3.8/envs/omega-analysis/lib/python3.8/site-packages/uproot/behaviors/TBranch.py", line 3540, in _regularize_step_size
    return _hasbranches_num_entries_for(
  File "/home/name/.opt/python/miniconda3.8/envs/omega-analysis/lib/python3.8/site-packages/uproot/behaviors/TBranch.py", line 3523, in _hasbranches_num_entries_for
    num_entries = int(round(target_num_bytes * total_entries / total_bytes))
ZeroDivisionError: float division by zero

Thanks!
(Sheesh—division by zero!)


France.tv

Checklist

[x] I'm reporting a broken site support
[x] I've verified that I'm running youtube-dl version 2020.05.08
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[x] I've searched the bugtracker for similar issues including closed ones

Verbose log

PASTE VERBOSE LOG HERE

Description

WRITE DESCRIPTION HERE

https://www.france.tv/france-2/les-pouvoirs-extraordinaires-du-corps-humain/1437583-deconfinement-vivre-avec-le-virus-posez-toutes-vos-questions.html
don't work


[MB-14747] Update customer and office move APIs to save ppm closeout location

Jira ticket for this change
Summary
This modifies one existing customer API PATCH /moves/{id} and creates a new office API PATCH /moves/{locator}/closeout-office to save the chosen closeout office from each app.
For the customer endpoint I had to remove an unused field selectedMoveType that is no longer being utilized and added the closeoutOfficeID to the payload.  The endpoint also wasn't using eTag's so I added that header to the request.  I moved the actual database logic into the shared service with the office.
Setup to Run Your Code

💻 You will need to use three separate terminals to test this locally.
Terminal 1
Start the Storybook locally.
make storybook

Terminal 2
Start the UI locally.
make client_run

Terminal 3
Start the Go server locally.
make server_run

Additional steps

Access the
Login as a

Verification Steps for Author
These are to be checked by the author.

[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

Verification Steps for Reviewers
These are to be checked by a reviewer.

Frontend

[ ] User facing changes have been reviewed by design.
[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] There are no new console errors in the browser devtools
[ ] There are no new console errors in the test output
[ ] If this PR adds a new component to Storybook, it ensures the component is fully responsive, OR if it is intentionally not, a wrapping div using the officeApp class or custom min-width styling is used to hide any states the would not be visible to the user.

Backend

[ ] Code follows the guidelines for Logging
[ ] The requirements listed in Querying the Database Safely have been satisfied.

Database
Any new migrations/schema changes:

[ ] Follows our guidelines for Zero-Downtime Deploys
[ ] Have been communicated to #g-database
[ ] Secure migrations have been tested following the instructions in our docs

Screenshots

Fails

:no_entry_sign:
Yarn Audit Issues Found:
high - Prototype Pollution in JSON5 via Parse Method
Package json5
Patched in >=2.2.2
Dependency of @trussworks/react-file-viewer
Path @trussworks/react-file-viewer > pdfjs-dist > worker-loader > loader-utils > json5
More info https://github.com/advisories/GHSA-9c47-m6qq-7p4h
1 high vulnerabilities and 0 critical vulnerabilities found

Warnings

:warning:
This PR does not include changes to unit tests, even though it affects app code.

Messages

:book:
:link: MB-14747

  Generated by :no_entry_sign: dangerJS against 01ac275b50b791b0039f75aa493eabfa581d1c2c


feat: wrench model predictive controller on 2D spacecraft

To complete a nice set of initial controllers, I've started on an MPC that publishes thrusts and torques (the wrench, separated over two publishers as per the PX4 message types).
Currently, the robot spins around its z-axis so I still need to fix that.

@joris997 you might need to merge the latest master to your branch to make sure it is up to date.

@joris997 you might need to merge the latest master to your branch to make sure it is up to date.

I would suggest a rebase

@joris997 Could you add instructions on how to configure the different modes of the MPC?


lightrag_openai_compatible_demo. file. Questions to ask

I saw that you modified the code yesterday, but I feel that there are some areas that are not correct, especially the file reading and querying parts of the asynchronous code. Would it be better to switch to asynchronous?
 with open("./hanye.txt", "r", encoding="utf-8") as f:             content = f.read()    await rag.ainsert(content)
naive_result = await rag.aquery(query, param=QueryParam(mode="naive"))         print("Naive search result:", naive_result)

Actually, I give the pr yesterday just to aovid the potential embedding problem (you can check it out in the closed pull request history), the original code is not asynchronous so I keep the original style. I have tried to switch to asynchrounous as you described which indeed reduced the response time. But I think that maybe it is not necessary since it is just a demo, and the synchronous  query is much easier for users to understand. If you truly want to switch to asynchrounous, I can give another pr or you can give a pr yourself (if the author think it is acceptable).

Sorry, I think I missed some points in the last response. The indexing and query procedure you mentioned here should be synchronous . If you set thme to asynchronous mode, the program will probably raise errors since the indexing process must behind the rag initilization, and the query process must behind the indexing process, which means the order is critical, but the asynchronous mode cannot gurantee the order. I said in the last response that "I tried to switch to asynchrounous..." is the case that I have already done the indexing and the initialization process, every time I just do the query process so asynchrounous mode is fast and reasonable at that time. I hope this can clarify your question.


4.10. Biogeochemistry Simulation Documentation Error

In the documentation for "4.10. Biogeochemistry Simulation",
"depth_g77.bin" is stated as the bathymetry data file.
However, in the input files and data file, "bathy.bin" is used.

@dustincarrollocean thanks for pointing this out. Do you think you can correct this in a small PR?

Sure Martin

This issue has been fixed by PR #509, close it.

done


158 Use checkbox and textfield in table

This change is

I elected to merge this for you so it doesn't need to go another round of merging in main when someones elses PR gets in before yours. Hope that is ok.


Design (Engineering): Scroll state header out of view

Is it possible for the state header to scroll out of view?

Taking suggestion & closing.


patch/optional_msm_import

allow importing MycroftSkill class without having msm installed, this makes subclassing easier
only skill_manager.py and skill_updater.py actually use msm

commits dropped in favor of #24


Deprecating warnings

Hi,
first of all, thanks for the awesome library.
Is there a plan to fix all the deprecating warnings which are already showing up in sf 2.8.x.
PS: This should also help for easier compatibiliy to sf 3.x, when time comes.
best regards,
horfic

Hi @horfic,
The current plan on releasing a SF 3.0 version will be some where in the next month please follow PR #36 for more information when it is available.
Happy new years.

Hi @horfic,
The current plan on releasing a SF 3.0 version will be some where in the next month please follow PR #36 for more information when it is available.
Happy new years.

I'm closing this because the master branch now has support for Symfony 3 and where possible avoids deprecation warnings.


Add context to addTelemetryInitializer callback?

In https://github.com/microsoft/ApplicationInsights-node.js , you can modify the telemetry using addTelemetryProcessor which executed with envelop and context (the context changes according to the collected data, for example: the req/res for HTTP requests).
Any chance we can do the same for the library? :)

Nevermind, needed to pust this under https://github.com/microsoft/ApplicationInsights-JS#readme :D

Yep, ideally this SDK should share, as much as possible, an API/feature surface with the node.js SDK. I'll add this to our backlog

Thanks @markwolff ! I can create a PR to add it, can you maybe just point me to the code that manages that?

@dotansimha It would be inside the "analytics plugin". Here is the entry point (you will also need to update the same function located in AISKU/Initialization.ts to match the interface change.
https://github.com/microsoft/ApplicationInsights-JS/blob/9705984134fcc5244bc5f6838163d766a8be5744/vNext/extensions/applicationinsights-analytics-js/src/JavaScriptSDK/ApplicationInsights.ts#L455-L457
This plugin already has "context" available to it via this._properties.context.
https://github.com/microsoft/ApplicationInsights-JS/tree/master/vNext/extensions/applicationinsights-properties-js/src/Context


Update dmlc-core, fix default ctors of NodeEntry

MXNet uses nullptr to designate a node in which autograd is not enabled.
Thanks for contributing to TVM!   Please refer to guideline https://docs.tvm.ai/contribute/ for useful information and tips. After the pull request is submitted, please request code reviews from Reviewers.

@tqchen is CI working?

The CI is reporting lint error that you will need to fix http://ci.tvm.ai:8080/blue/organizations/jenkins/tvm/detail/PR-3017/2/pipeline

@larroy please act to fix the CI's lint report


DIP updates required

[ ] DIP3 masternode rewards section will not match implementation following MN_RR change (evonodes will only receive 1 core chain payout just like regular masternodes)
[ ] DIP15 DashPay contract section has not been update with all changes made in the implementation

consider adding this one, please - https://github.com/dashpay/dips/pull/153


Send labels with the initial ws connection headers

fixes #1136

Not 100% sure this is the right way... should we send node information on websocket connect event (now it's websocket:connected which happens too late)?

As discussed, sending info on websocket connect does not help here because it's also too late.

If we don't want to use the headers to send the info, I can think of two alternative approaches. Both need some refactoring on the node plugging sequence.

In this case server would request the info from agent and after receiving it would execute the node plugging functionality. This would require new RPC api on agent side and refactoring of the node_plugger sequence.

In this case agent would send the full node info data after the ws connection is opened. Server executes the node plugger functionality after receiving this initial node info. This would require some mechanism to keep track of whether or not initial node plugging functionality is executed or not as agent periodically send the full info to the server.
Some other options, all which might be bad ideas :) :

Send the node_info data on the initial connect as base64 encoded query param
Send the node_info data on the initial connect as base64 encoded header field

As for now, the only critical extra info is the labels and to send those the custom header field is pretty simple solution.

Ok, maybe using headers is fine for bug fixing this race condition. We can refactor this logic later to match your diagram.


Update to Cosmos SDK v0.44

Currently, pre-release
https://github.com/cosmos/cosmos-sdk/releases/tag/v0.43.0-alpha1
may be worth basing 1.0 RFC off here, as it contains quite a few breaking changes and the future state sync hook patch will be on top of it

This is way too unstable to consider for our release coming out in the next few days.
I would consider this stable once it is live on multiple testnets and has been heavily tested by the community. (It was already v0.42.1 or so that was really the stable Stargate release).
Depending on the QA process, we could consider updating for 1.0. Otherwise, a stable 1.0 based on 0.42.x and make a 1.1 wasmd release with 0.43.x (with a migration path and same contract structure)

I have my eye on this release for quite some time. It was supposed to have an rc about 4 weeks ago, and there is quite a list of work to do: https://github.com/cosmos/cosmos-sdk/milestone/26
Having been burnt by Stargate releases a number of times, we will be conservative in updating deps.

I would consider this stable once it is live on multiple testnets and has been heavily tested by the community.

I concur with this sentiment.
It is worth considering that at least for the Provenance networks we will not have testnets running the 0.43 version until we have some sort of wasm dependency (xxxx-alpha?) available that is compatible.

I was checking with IBC team - they are following the SDK releases and are already testing with 0.43-beta

Thanks for the input @robert-zaremba
Yeah, that list looked quite long and far from release. Hope it is much quicker as you say.
Has a similarly thorough audit gone through ibc-go 1.0 or how is that being coordinated?
I assume any real app will need cosmos sdk 0.43 and ibc-go 1.0 and that it needs a 0.43 final before ibc-go 1.0 can be published.

for reference, since then -- https://github.com/cosmos/cosmos-sdk/releases/tag/v0.43.0-rc1 -- final release soon.
https://github.com/cosmos/ibc-go/releases/tag/v1.0.0-rc0

Yeah, good update.
May be good looking at again before 1.0.
Is there any chain that would want to use CosmWasm 1.0 with CosmosSDK 0.42?

Provenance is beginning a pretty significant set of changes to support 0.43. The headline features of feegrant and authz are driving the desire to adopt this release sooner than later.
Our existing 0.42 testnet/mainnet release with Cosmwasm is slated for bugfixes only going forward.

One nice thing in 0.43 is https://github.com/cosmos/cosmos-sdk/blob/master/docs/architecture/adr-041-in-place-store-migrations.md that modules are versioned -- so it may be good to have 1.0 based on that even if feegrant/authz aren't initially supported.
One more compelling item is that there's a corresponding ibc-go 1.0.0 aligned with 0.43: https://github.com/cosmos/ibc-go/releases which, among other things, contains fixes to the solo machine client (solo machine client doesn't work in 0.42)

It is now at rc2...

may be worth basing 1.0 RFC off here, as it contains quite a few breaking changes and the future state sync hook patch will be on top of it

btw, just reviewing https://github.com/cosmos/cosmos-sdk/issues/7340#issuecomment-882579080 and it seems there isn't even a design for this, much less a plan to integrate it. I do not think this will end up in the Cosmos SDK this year unless some CosmWasm-based chain champions it. And I kind of doubt it would make it in 0.43

We have feature and api freeze for cosmwasm 0.16, which is 1.0 RFC
We are finalizing wasmd 0.18 in the next few weeks. Only api changes expected are around events, but there may be a few others. It should be cut in max 2 weeks.
Both those are 1.0 RFC and we plan to test those with other chains.
0.43.0 is still in rc and it is too risky to include it now. 1.0 will base on 0.42.x
That said, once we cut a 1.0, we could start a new branch with 0.43 support. Confio doesn't have much energy motivation on this until 0.43 is on the Cosmos Hub. Based on past experience only versions deployed to gaia have LTS promises.
But if Provenance wants to do such work, we are happy to review and maintain such a 0.43 branch. I would wait until 0.18 is release to start it, so we'd only have to merge in bugfixes from master.

Currently we have a patched up version that is letting us build and test the rest of our system but soon we need to focus on finishing our smart contract integration so we can get to release.
I have a couple of engineering resources that we are able to dedicate to this. I would like to work close with the cosmwasm team if we were to contribute work on a 0.43 solution. Let's chat Monday @ethanfrey

I added a related issue in CosmJS, which is likely needed for any full-stack cosmwasm solution based on 0.43 as well: https://github.com/cosmos/cosmjs/issues/865
You can add questions there and maybe Simon can explain better what happened, but the SDK team seemed to have made client API breaking changes leaving it very difficult for a client to support both 0.42 and 0.43 at the same time... we have to pick one, not both.

We are releasing RC3 today, IBC / x/capability bug is merged (which is also related to 0.42.8). The CosmoJS issue shouldn't be a problem.
Many chains are going to upgrade to 0.43 and it has lot of great things which didn't make it into Stargate (due to Stargate bugs fix releases 0.40-0.42). 0.43 has been in feature freeze since beginning of May. Features like new keys (secp256r1), authz and feegrant are very useful and it will be great to have cosmwasm joining the party for the stable release!

For reference: https://github.com/terra-money/core/tree/master/x/wasm Terra is on 0.43

Provenance has been keeping a branch of the wasm module for 0.43 current with frequent merges from the master cosmwasm upstream branch. Remaining tasks include some updated IBC test contracts to ensure the entire go-ibc 1.0.0 suite passes. We intend to continue merging updates from upstream in until the final 0.18 is released. Testing and certification work with our existing contracts is on going.
https://github.com/provenance-io/wasmd/tree/provenance-409-cosmos-v0.43

The recently tagged v0.18.0-rc3 is complete except for some minor tweaks in how we handle events in submessages. But that should be a good place to base on. We should cut v0.18.0 next week.
Once we cut that, if you want to rebase your branch on it and make a PR, we can take a look at the code. (You don't have to rebase, but any approach that shows the minimal diff... sometimes lots of merges from master can make hard PR reviews).
Thank you for this initiative.

I will rename the issue to v0.44

the v0.44 release (hopefully today) which will be the v0.43  + a breaking security patch.

https://discord.com/channels/669268347736686612/680435043570941973/882217645708050442

Whereas:

we have not yet hit 1.0 (due to hunting down security issues and sdk integration details)
and there are 4 networks running with a  fork of wasmd to add 0.44 sdk comptability
and the gaia testnet is using Cosmos SDK 0.44 (promising better support)

We propose to:

close all known issues in the v1.0 milestone and tag a 0.21 release
make a PR to update wasmd to use Cosmos SDK 0.44
tag a 0.22 release and get some feedback and testing on it
pull select issues from the v1.x milestone and v2.0 milestone
tag 1.0.0-beta
Audit time

We cannot promise a timeline, but we can promise the priority list. Issues not on these milestones that are not security related will not be considered for v1.0 unless there are exceptional circumstances.
If you have a fork that added 0.44 support that we should use as reference, feel free to add a link in the comments.

Please note that this code will in no way be ready for some network's planned Dec 15 upgrade and that plan was made without any consultation to Confio or our roadmap.
We have pulled this up in priority and included it in 1.0 by popular demand, but not for any particular release date. It should be ready sometime in January (after holidays).

It should be ready sometime in January (after holidays).

Does ready in this case mean 'code complete' or does it mean 'tested and official release cut'
In either case a consuming project would need to budget time for their own integration and testing which would likely mean a best case dependent project upgrade no earlier than February or so...

I would assume an official release of wasmd based on the 0.45 "bug fix" release in January. Not necessarily 1.0 (likely 0.22), but a tested integration including with IBC and contracts.

Cosmos SDK v0.45 Relesed!

Wonderful!
https://github.com/CosmWasm/wasmd/pull/721 is on the rc. Time to merge


[0.8.4] data-attribute would be nice

in bootstrap vue, it was possible (on almost components) to set the data-attribute, for example:
  <b-dropdown-item @click="onclick_searchtype"  data-searchtype="lastname">Lastname</b-dropdown-item>
I use it a lot, and it's a handy way to assign data to an element.
what do you thing, is it possible to add this feature as in bootstrap-vue ?

Please gather documentation on Bootstrap-vue that highlights this behavior. I have never heard of this.

it is not part of the official bootstrap vue documentation, but look here:
https://bootstrap-vue.org/docs/reference/changelog#bug-fixes-v2180
(search for "data-")
bootstrap vue didn't cut it away
the data-attribute is an important part for javascript programmer
https://developer.mozilla.org/en-US/docs/Learn/HTML/Howto/Use_data_attributes
standard components have a lot of data-attributes:
<button type="button" class="btn btn-primary" data-bs-toggle="modal" data-bs-target="#exampleModal">
Q: How can i set my own  data-attributes now ?

this exam snippets works with data-attribut
 <b-form-select
          data-myjob="expert"
          :options="searchoptions"
          size="sm"
          v-model="searchtype" >
 </b-form-select>

this does not work
<b-dropdown-item data-searchtype="lastname">Lastname</b-dropdown-item>


Feature/multiple currency support

What does this implement/fix? Explain your changes.

New Price component to render price
If display currency is different then base currency, then this PR multiplies base price with exchange rate and show currency currency symbol.
In Order related screen, order_currency_code is used to determine price and currency symbol, instead of display currency

Does this close any currently open issues?
close #98
Any other comments?

[ ] TODO: Show currency picker to change currency in the app

Where has this been tested?

Magento Version: [2.1.0]
Device: [Android Emulator Nexus 5X]
OS: [PIE 8.0]
Version [28]

Don't merge, one functionality is left, to show dropdown to change currency


Getting PEER_FLOOD Error by adding users to group

My program is searching users with specifics from a group and adds them to another group. After like 50 users added I can't add anymore and getting the error "PEER_FLOOD" as result.
I have already tried to wait 2 minutes after every added user but still after ~50 users i am getting this error. After this I can't add anyone at all for a day or something. But I can still make requests like getUser().
What exactly are the limits? How can I avoid being markes as spam? How many users in what time period am I allowed to add?

You are unallowed to add random users to groups against their will, so the effective limit is 0. Short spikes are allowed, but if invited people will mark you and your chat as spam, you will not be able to invite more people and your account can be spam-blocked. If these people want to join the group, then you can send them invite link and they will join it themselves.
Anyway, it isn't a question or issue concerning TDLib.

Mhhh i am pretty sure that getting the PEER_FLOOD error is not due to being marked as spam manually. It has to be a mechanism which does it when you reach a limit. Are you sure?


Traing Loss problem.

When I used your algorithm and parameters to train on both the WTH dataset and my own dataset, I found that the loss was very low in the first epoch, but increased sharply in the second epoch, and subsequently, the loss remained higher than in the first epoch. The variation in the training loss is perplexing, and I hope you can provide some insights.

I think it is the problem of loss function, the loss function of Time Domain Contrastive Loss using the MOCO loss, but add a denominator

I assume it is not necessary. if you delete this one. you may solve the problem.
And the loss code in CoST/cost.py Class CoSTModel I write is:
def compute_loss(self, q, k, k_negs):
# compute logits
# positive logits: Nx1
l_pos = torch.einsum('nc,nc->n', [q, k]).unsqueeze(-1)
# negative logits: NxK
l_neg = torch.einsum('nc,ck->nk', [q, k_negs])
# logits: Nx(1+K)
logits = torch.cat([l_pos, l_neg], dim=1)

# apply temperature
logits /= self.T

# labels: positive key indicators - first dim of each batch
labels = torch.zeros(logits.shape[0], dtype=torch.long).cuda()

# Mask to zero-out positives in the denominator
mask = torch.ones_like(logits)
mask[:, 0] = 0

# Apply mask and calculate cross-entropy loss
logits_masked = logits - (mask * 1e9)  # Using a large value to mask
loss = F.cross_entropy(logits_masked, labels)

return loss

Hope this would help.

Thank you. I made the modification according to your suggestion, and this problem has been solved.

Thank you. I made the modification according to your suggestion, and this problem has been solved.

Great, good to help. hhhhh, follow me, star me, thank you. hhhhhhh

Thank you. I made the modification according to your suggestion, and this problem has been solved.

By the way, the moco v2 is using this paper's loss function. I just noticed that.


[9.x] Use stable packages only in CI

This changes the minimum stability for framework to "stable". This is because of recent changes made in Composer that allow a wider selection of dev branches. Using "dev" on a stable branch like 9.x could lead to certain development packages being loaded in CI and giving unexpected results (either failures or success states where it's unwanted). By indicating we only want stable versions of packages we can test more accurate for real-life situations in apps.
Development branches for framework (currently 10.x and master) can still use "dev" if needed but as soon as they come closer to their release date it's best to also give them the "stable" stability so we're sure packages have stable versions tagged that are compatible.

This could be a breaking change, it broke our pipelines. Maybe this should be in a major release instead of a minor release.

If the package is consumed properly, it should make no difference. That config only affects how we install our own packages when running our CI and the like, and has no effect on peer dependencies when laravel is installed as a package.

@driesvints It affects the pipeline of an unreleased package, which is still marked as dev

Please share your composer.json so I can reproduce this. And the composer command you run to trigger this.


How to clone to a standalone host rather than a cluster?

Hi,
It seems that currently it is required to have a cluster in the VCenter, otherwise I can't get the clone to work..
Is it possible to deploy to a standalone host in the VCenter? If yes, could you please send me an example "config.yml" which I can use?
thanks a lot,
Marius

anyone can help, please?

@maneamarius I'm not sure if a single host depolyment would work, I've never tried. You could try setting cluster in config.yml to the single ESXi host name. I can't guarantee that will work though.
Alternatively, perhaps you can create a cluster in vCenter that consists of the single host?

I've tried everything I could think of.. I can't make it work with standalone host...
I ended up doing what you said in the meanwhile.. created a cluster and added this host to the cluster.
But we shouldn't do that, ezmomi should be able to work with standalone host.. :(

@maneamarius thanks for the feedback about the limitation and your solution. Doubtful I will have time to implement single host provisioning, but I will leave this here as a feature request.


./src/messages/cquery_freshen_index.cc:16:8: error: 'Run' overrides a member function but is not marked 'override' [-Werror,-Winconsistent-missing-override]

add override

Fixed in https://github.com/jacobdufault/cquery/commit/fb55731aa04176676bf5abd6e8340441a4f8df9c.


provide a library support c++11

server code is written by c++11, can you provide a library support c++11

no


MAINTAINERS: update mbolivar status

Revert to my old username on west and drop my long-inactive LED strip involvement.
(I'm intentionally not adding myself back to the devicetree collaborators list -- I'm not able to help out there at this time.)

Please make sure to also apply as a contributor to the GH org so that your +1s on PRs get the green checkmark
Also s/me/mbolivar/ in your commit message please
Welcome back :)


Npm start task

This moves the "run a server" into the project as an npm script, using live-server, such that people don't really need to run their own global server if they don't want to set one up, including globally installing live-server (as an npm script, live-server runs from the node_modules dir)

@Pomax can you rebase on the bramble branch?  Right now master points at Adobe's stuff.

yeah, this is a little silly


Series quality chooses unknown over known quality

Expected behaviour:
Any known quality should be better than an unknown.
Actual behaviour:
Log:
2022-05-13 08:36:14 DEBUG    series        demo             start with entities: ['ABC.22.05.13.DEF.SD.MP4-GHI', 'ABC.22.05.13.DEF.1080p.MP4-JKL']
2022-05-13 08:36:14 DEBUG    series        demo             current entities: ['ABC.22.05.13.DEF.SD.MP4-GHI', 'ABC.22.05.13.DEF.1080p.MP4-JKL']
2022-05-13 08:36:14 DEBUG    series        demo             -------------------- process_propers -->
2022-05-13 08:36:14 DEBUG    series        demo             propers - downloaded qualities: {}
2022-05-13 08:36:14 DEBUG    series        demo             continuing w. entities: ['ABC.22.05.13.DEF.SD.MP4-GHI', 'ABC.22.05.13.DEF.1080p.MP4-JKL']
2022-05-13 08:36:14 DEBUG    series        demo             best entity is: `ABC.22.05.13.DEF.SD.MP4-GHI`

Additional information:

FlexGet version: 3.3.8
Python version: 3.9.7
Installation method: Docker wiserain/flexget:latest

How is it unknown? SD is equivalent to 480p

Sorry, I could've included more of the log. To me it looks like SD is detected as unknown.
2022-05-13 08:36:14 DEBUG    series.db     demo             adding release `<SeriesParseResult(data=ABC.22.05.13.DEF.SD.MP4-GHL,name=ABC,id=22 05 13 DEF,season=None,season_pack=None,episode=None,quality=unknown,proper=0,special=False,status=OK)>`
2022-05-13 08:36:14 DEBUG    series.db     demo             -> added `<Release(id=None,quality=unknown,downloaded=None,proper_count=0,title=ABC.22.05.13.DEF.SD.MP4-GHL)>`
2022-05-13 08:36:14 DEBUG    series        demo             start with entities: ['ABC.22.05.13.DEF.SD.MP4-GHL', 'ABC.22.05.13.DEF.1080p.MP4-JKL']
2022-05-13 08:36:14 DEBUG    series        demo             current entities: ['ABC.22.05.13.DEF.SD.MP4-GHL', 'ABC.22.05.13.DEF.1080p.MP4-JKL']
2022-05-13 08:36:14 DEBUG    series        demo             -------------------- process_propers -->
2022-05-13 08:36:14 DEBUG    series        demo             propers - downloaded qualities: {}
2022-05-13 08:36:14 DEBUG    series        demo             continuing w. entities: ['ABC.22.05.13.DEF.SD.MP4-GHL', 'ABC.22.05.13.DEF.1080p.MP4-JKL']
2022-05-13 08:36:14 DEBUG    series        demo             best entity is: `ABC.22.05.13.DEF.SD.MP4-GHL`
2022-05-13 08:36:14 DEBUG    series        demo             downloaded_qualities: []
2022-05-13 08:36:14 DEBUG    series        demo             wanted qualities: {<Requirements(1080p h265)>}
2022-05-13 08:36:14 DEBUG    series        demo             ep: `ABC.22.05.13.DEF.SD.MP4-GHL`, quality: `unknown`
2022-05-13 08:36:14 DEBUG    series        demo             `unknown` is an unwanted quality
2022-05-13 08:36:14 DEBUG    series        demo             ep: `ABC.22.05.13.DEF.1080p.MP4-JKL`, quality: `1080p`
2022-05-13 08:36:14 DEBUG    series        demo             `1080p` is an unwanted quality
2022-05-13 08:36:14 DEBUG    series        demo             timeframe: 24 hours
2022-05-13 08:36:14 DEBUG    series        demo             timeframe: 1 day, 0:00:00, first_seen: 2022-05-13 08:29:15.106735, expires: 2022-05-14 08:29:15.106735
2022-05-13 08:36:14 INFO     series        demo             `ABC`: timeframe waiting for 23h:53min. Currently best is `ABC.22.05.13.DEF.SD.MP4-GHL`.
2022-05-13 08:36:14 DEBUG    backlog       demo             Saving ABC.22.05.13.DEF.SD.MP4-GHL


Trying to make it work with mdbreact's Input tag

I am trying to leverage the renderInput prop so that it uses the Input component from mdbreact (https://mdbootstrap.com/react/) like this:
...
renderInput={(props) => <Input {...props} label="MyLabel" icon="user" error="wrong" success="right" />}
... />

However, whenever I click on the resulting input field and try to enter a character, it crashes with
Uncaught TypeError: node.getBoundingClientRect is not a function
    at Autocomplete.setMenuPositions (bundle.js?e7452783c6a51b5f1d7e:37758)
    at Autocomplete.componentDidUpdate (bundle.js?e7452783c6a51b5f1d7e:37670)

How to make this work? If i use a composition of regular html div and input tags, it works, but is missing the animations and UX provided by the Input component

As explained in the renderInput documentation:

At the very least you need to apply props.ref and all props.on event handlers. Failing to do this will cause Autocomplete to behave unexpectedly.

Passing all the props to <Input> isn't enough here, as it's not a native <input> element, rather a wrapper around it. I'm not familiar with mdb, so you'll have to figure out if it's possible to pass an input-ref down to the actual input element.

For future reference, this is how I made it work - seems a bit hacky, but does the job. The key was not to use the Input element, but the undelying TextField element:
renderInput={(props) => <TextField {...props} type='text' label="MyLabel" icon="user" error="wrong" success="right" ref={(el) => {if (el) {props.ref(el.inputElRef); this.state.inputEl=el.inputElRef;}}}/>}
...
onSelect={(val) => {this.setState({masterId: val}); this.state.inputEl.value=val;}}

Note the hard-assignnment of the value during onSelect.


Duplicate method

https://github.com/PacktPublishing/Laminas-Web-Development/blob/3896852da56e3d14154ccc634ca22461b384146c/chapter11/whatstore/module/Store/src/Model/Customer.php#L33
This is why I suggested to move this to a filter. The custom filter can then be attached like any other filter and can be applied to any entity that implements the InputAwareInterface or InputProviderInterface. Keeps the code DRY.

Very good suggestion.
I understand that if you can solve the problem immediately, you must do it.
However, this is not the planned moment to talk about filter customization. This is approached in Chapter 13.

Gotcha,. I'm trying not to read ahead because I feel it might skew my perception of the text as it stands so please bare with me if I suggest changes that are addressed later.

Opportunity was found.


Input Fields Instead of Textarea

Can the installer have input fields for entering the database details instead of the whole textarea giving the .env file?

Yes, it can be done by splitting the .env file lines and put each one of them in its own input and then merge the content and put it back in the .env file.

Maybe also generate the application key in the step and also set the APP_DEBUG to false.

yes, I 2nd the motion, want to see some improvements in next release.
Anyway thanks for the web installer it's working good in laravel 5.3.

You can use the forked version for laravel 5.4. I has input fields instead of textarea.
https://github.com/Froiden/laravel-installer

These have been added the proper Laravel way in https://github.com/RachidLaasri/LaravelInstaller/pull/89.

@RachidLaasri I think this can be closed.


Empty region names and missing javadoc in some tests

Description
To Reproduce
    public int[] arrayCopy() {
        int[] fst = {1, 2, 3};
        int[] snd = {4, 5, 6};

        System.arraycopy(fst, 0, snd, 0, 3);
        return snd;
    }

Steps to reproduce the behavior:

Open algorithms/Sort.java sample from UTBot project
Or use code sample from above.
In plugin settings set generation method to 95% Symbolic
Use plugin to generate tests
Open the generated test

Expected behavior
Every test is placed in region with name and has proper java doc description
Actual behavior
Quite many regions have no names and some tests have no javadocs
Visual proofs (screenshots, logs, images)
Here is one of generated test:
public class SortTest {
    ///region Test suites for executable org.example.Sort.arrayCopy

    ///region

    @Test
    public void testArrayCopy1() {
        Sort sort = new Sort();

        int[] actual = sort.arrayCopy();

        int[] expected = {1, 2, 3};
        assertArrayEquals(expected, actual);
    }

...

@tyuldashev the default behaviour - do not generate summaries/regions if something goes wrong (it should be logged by logger.error to the log). We are not guarantee at this moment that all tests will have regions and other summaries.
Sometimes it's a developer bug in summaries, sometimes it's the limitation of summaries functionality.
I suggest or copy the reason of crash from logs (if it's the same it's one bug if is different—there are a few bugs) or copy generated results (with missed summaries)

On my laptop looks like it's reproduced and related to the problem #1227

@tyuldashev @alisevych Looks like it was fixed by #1227 closed earlier, it's not reproduced on my side

@tyuldashev @alisevych please reproduce and close, the bug is not reproduced on the master and closed earlier
For example, the following test is generated
public final class SortTest {
    ///region Test suites for executable custom.Sort.arrayCopy

    ///region FUZZER: SUCCESSFUL EXECUTIONS for method arrayCopy()

    /**
     * @utbot.classUnderTest {@link Sort}
     * @utbot.methodUnderTest {@link Sort#arrayCopy()}
     */
    @Test
    @DisplayName("arrayCopy: arg_0 = Sort()")
    public void testArrayCopy() {
        Sort sort = new Sort();

        int[] actual = sort.arrayCopy();

        int[] expected = {1, 2, 3};
        assertArrayEquals(expected, actual);
    }
    ///endregion

    ///endregion
}

@amandelpie yes, looks like this one fixed, there is one question though: should region have name even when Summaries generation is Disabled? In latter case region name still could be empty.

Per discussion, that's okay that region name is empty when summaries disabled in the settings. So closing the case as fixed.


[FEATURE]: Drop cumulus-ui 'xhr' dependency from package.json

After changes are published to npm (see USACE/usace-bundles#6, USACE/usace-bundles#8), cumulus-ui should be able to update to the latest version of @usace/create-jwt-api-bundle and drop xhr as a direct dependency in cumulus-ui/package.json

usace bundles have been published, I've switched the tailwindui branch to use the new version and will do some testing there.  once we move to tailwindui this will be fixed

new tailwindui was deployed to stable a couple weeks ago


Performing git stats encountered an error

ths
I change serveral machine
and got the same result
[root@cns-vs-d0026 ~]# git_stats  Traceback (most recent call last): 	23: from /usr/local/ruby/bin/git_stats:23:in '
22: from /usr/local/ruby/bin/git_stats:23:in load' 	21: from /usr/local/ruby/lib/ruby/gems/2.7.0/gems/git_stats-1.0.17/bin/git_stats:8:in <top (required)>'
20: from /usr/local/ruby/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:72:in require' 	19: from /usr/local/ruby/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:72:in require'
18: from /usr/local/ruby/lib/ruby/gems/2.7.0/gems/git_stats-1.0.17/lib/git_stats/cli.rb:2:in <top (required)>' 	17: from /usr/local/ruby/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:72:in require'
16: from /usr/local/ruby/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:72:in require' 	15: from /usr/local/ruby/lib/ruby/gems/2.7.0/gems/git_stats-1.0.17/lib/git_stats.rb:5:in <top (required)>'
14: from /usr/local/ruby/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:72:in require' 	13: from /usr/local/ruby/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:72:in require'
12: from /usr/local/ruby/lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/all.rb:3:in <top (required)>' 	11: from /usr/local/ruby/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:72:in require'
10: from /usr/local/ruby/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:72:in require' 	 9: from /usr/local/ruby/lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/core_ext.rb:1:in <top (required)>'
8: from /usr/local/ruby/lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/core_ext.rb:1:in each' 	 7: from /usr/local/ruby/lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/core_ext.rb:2:in block in <top (required)>'
6: from /usr/local/ruby/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in require' 	 5: from /usr/local/ruby/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in require'
4: from /usr/local/ruby/lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/core_ext/object.rb:3:in <top (required)>' 	 3: from /usr/local/ruby/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:72:in require'
2: from /usr/local/ruby/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:72:in require' 	 1: from /usr/local/ruby/lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/core_ext/object/duplicable.rb:106:in <top (required)>'
/usr/local/ruby/lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/core_ext/object/duplicable.rb:111:in <class:BigDecimal>': undefined method new' for BigDecimal:Class (NoMethodError)
[root@cns-vs-d0026 ~]#
`

duplicate #106


Move toggleModal's area to arguments list.

It is about jquery.toggleModal.js.

Waiting on please review comment :)

@vogdb So we cancel this?

Yes. Closed.


django1.7 AppRegistryNotReady

I use Sphinx build docs, raise error.

I had this issue migrating from 1.6 to 1.7 because I defined a filter in models.py.  I moved the filter class to a new filters.py and that solved the problem.

I moved the filter to a new file, but I'm still having this issue trying to use the filter in a view.

I'm going to need something like a minimal reproduce case here. Preferably a failing test case.
As described, it's hard to see what the issue could be: importing a model into a filters module and then importing the filter into a views module is the basic example set-up, it works — or A) there'd be more shouting and B) the project I have running in front of me now wouldn't work.
So the question is what are you doing differently? Currently there's not enough to be able to say.
I'll leave this open for a few days to see if there's any more info but if not I'll close it as not-reproducible. (In this case we can always reopen if needed.)


Update lock to normalize home dep

I'm not sure what happened, but in #11840 Cargo.lock was updated in such a way that the home dependency had a qualified source, even though it was equivalent to crates.io. This should only happen if there is some ambiguity (like if something had a path source to the in-tree home).
This causes the Cargo.lock file to be modified whenever running cargo commands locally.  This doesn't fail --locked because the resolve is equivalent, pointing to the the same source.
Closes #12082

Thanks!
@bors r+

:pushpin: Commit 5c99dc43cb8b6193bcc12e299fa4bca1a87592d0 has been approved by weihanglo
It is now in the queue for this repository.

:hourglass: Testing commit 5c99dc43cb8b6193bcc12e299fa4bca1a87592d0 with merge 7d118441f7fd736294cbd483c55e04809884be7b...

:sunny: Test successful - checks-actions
Approved by: weihanglo
Pushing 7d118441f7fd736294cbd483c55e04809884be7b to master...


Add "cost to here" to predecessors and PathInfo?

Change predecessors[v] = (u, e, cost_of_e) to predecessors[v] = (u, e, cost_of_e, cost_of_s_to_u_plus_cost_of_e) in single_source_shortest_paths(), add a corresponding field to PathInfo, and update extract_shortest_path_from_predecessor_list().
I'm not sure off the top of my head what the use cases for this might be, but I saw that someone created a fork to replace cost_of_e with cost_of_s_to_u_plus_cost_of_e, so it's worth considering.

As this is just sum(info.costs[:i]), it doesn't seem super useful except as a convenience. It would change the API (the return value of find_path() in particular), so it would have to be added to v3. I'm thinking it doesn't seem worth the effort.


docs: fix link to all_policy_templates example file

Issue #, if available:
#1677
Description of changes:
Updated URL of file in doc
Description of how you validated changes:
Checklist:

[ ] Write/update tests
[ ] make pr passes
[ ] Update documentation
[ ] Verify transformed template deploys and application functions as expected

Examples?
Please reach out in the comments, if you want to add an example. Examples will be
added to sam init through https://github.com/awslabs/aws-sam-cli-app-templates/
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #1682 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop    #1682   +/-   ##
========================================
  Coverage    94.09%   94.09%
========================================
  Files           86       86
  Lines         5418     5418
  Branches      1084     1084
========================================
  Hits          5098     5098
  Misses         148      148
  Partials       172      172

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 d09ed7b...1dd8ed8. Read the comment docs.


Ancestry without DP

Stacked branch, splits Ancestry into 3 separate stages. I kinda ran out of stamina on this one so it's partially implemented...

Add Background - runs in QOB, no need for Dataproc here. This is just a join across many different tables. This stage is optional, instead of ancestry_pca deciding whether or not to run a method inside Dataproc based on config
Run PCA - local Hail, removes samples that need to be removed, and generates 3 new tables which are copied to GCP
Infer Ancestry - local Hail, either uses the SampleQC table, or output of the AddBackground stage if it runs (depending on config)...

None of this is polished, the Ancestry stage still exists as originally implemented, and AncestryPlots still uses the standard Dataproc-generated outputs as input
For discussion - a comment in cpg_workflows/large_cohort/ancestry_pca.py

It looks like we're adding some annotations only to a VDS object, and not if we generate a dense MT from a MT. Is that intentional?

Codecov Report
Attention: Patch coverage is 90.47619% with 2 lines in your changes missing coverage. Please review.

Please upload report for BASE (relatedness_no_dp@e495c33). Learn more about missing BASE report.

Files with missing lines
Patch %
Lines

cpg_workflows/targets.py
91.66%
1 Missing :warning:

cpg_workflows/utils.py
66.66%
1 Missing :warning:

Additional details and impacted files
@@                 Coverage Diff                  @@
##             relatedness_no_dp     #878   +/-   ##
====================================================
  Coverage                     ?   78.50%
====================================================
  Files                        ?       10
  Lines                        ?     1791
  Branches                     ?        0
====================================================
  Hits                         ?     1406
  Misses                       ?      385
  Partials                     ?        0

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

Closing as...... we're going in a different direction here, and it's not my job 😇


Treat binders in hcom/coe as functions rather than closures

I'd like to think of hcom/coe as constants in the logical framework (regardless of whether we end up implementing them this way); so, in particular, it would be appropriate to think of the line and tube things as lambda-bound functions.
This would imply #35.

Resolved by #33


docs: add integration example with Grommet

FYI @tdonhauser

FYI @brillout I've put this example in a separate repo because:

I didn't feel like putting it in this repo because it's based on vike-react
I didn't feel like putting it in the vike-react repo because it's based on having ejected onRenderHtml() and a bunch of files it depended on.

So I feel like the example would look nicer if it was either based on Vike directly, or if we had a nicer way of having it on top of vike-react without ejecting so much code (maybe a bit the same spirit as https://github.com/vikejs/vike-react/issues/28 )
So it's a bit of a misfit right now but maybe later we can make it a first-class example.

Sorry I realize I should have merged "rebase", so without a merge commit. I'll do that next time.

So I feel like the example would look nicer if it was either based on Vike directly, or if we had a nicer way of having it on top of vike-react without ejecting so much code (maybe a bit the same spirit as vikejs/vike-react#28 )

Yes, that'd be 💯:

Making vike-react ejectable. (FYI stem-react, which is the experimental precursor of vike-react, is ejectable but it's using the old design. We could port that functionality to vike-react and the new design.)
Having an ejectable integration vike-gromment that seamlessly integrates with Vike/vike-react.

If we manage to pull it off, I think such ejectable integrations would be a tremendous added value.

Sorry I realize I should have merged "rebase", so without a merge commit. I'll do that next time.

No problems, the commit history is fairly messy anyways.


Add pre-commit hooks with linters

Use pre-commit to check that files respect some format (black, isort, ...)
Add a step checking these hooks in github workflow
Format all files to respect the hooks

You can now use

pre-commit on all files once in a while with pre-commit run -a
pre-commit at each commit with pre-commit install

Let us wait for PR #1 before merging this one.


UnitVolume tests fail on Linux

This test fails on Linux:
    func testWithNonBaseUnits() {
        let factor1 = Measurement(value: 100, unit: UnitArea.squareCentimeters)
        let factor2 = Measurement(value: 10, unit: UnitLength.millimeters)
        let actual: Measurement<UnitVolume> = factor1 * factor2
        let expected = Measurement(value: 100, unit: UnitVolume.cubicCentimeters)
        AmpereTest.assertEqual(actual, expected)
    }

XCTAssertEqual failed: ("0.0001 m³") is not equal to ("0.001 m³") - "0.0001 m³" is not equal to "100.0 cm³"
This is due to a bug in swift-corelibs-foundation. Some of the conversion coefficients for UnitVolume are wrong.

Reported to bugs.swift.org: SR-11766.
PR: https://github.com/apple/swift-corelibs-foundation/pull/2561


Memory leak: Navigating in the TOC (DocumentationReader) gets slower after subsequent clicks

Investigate.

Found out what is the root of the evil:
https://github.com/substance/substance/blob/master/ui/TOCPanel.js#L53
It seems that because the owner is confused and I manually need bind the click handler to this the handler gets attached on each rerender, causing the slowdown we observe. I can workaround this via jQuery click handler but we should get this fixed soon via #313.

Is it possible that component click handlers are leaking always?
this.render = function() {
  var that = this;

  return $$('a').append('MEEH')
    .attr('href', '#')
    .on('click', function() {
      console.log('clicked');
      that.rerender();
    });
}

This causes a lot of 'clicked' logs.

With the current issue-312 branch I have fixed the owner/parent issues.
It seems to me that this is resolved with that.
@michael could you try out plz?

Fixed via #346


Question about binding a volume to write to in container

Hello,
i tried using CBL Mariner 2.0 distroless to write into a directory that is mapped to a volume on the host but with no success.
Here is my Dockerfile:
FROM mcr.microsoft.com/cbl-mariner/base/core:2.0 AS publish
ENV DOTNET_CLI_TELEMETRY_OPTOUT 1
RUN tdnf -y install dotnet-sdk-6.0 ca-certificates-microsoft
WORKDIR /app
COPY ["Dark.csproj", "./"]
RUN dotnet restore "Dark.csproj" --runtime linux-x64
COPY . .

ENV ASPNETCORE_URLS=http://+:5000
ENTRYPOINT ["./Dark"]

As You can see in the last COPY statement I want to make the /app directory writeable to the non-root app user.
What can I do to write something to the Data folder?
Thanke in advance.
Greetings,
Markus

@MarkusRodler for chown to work you might need to add first a user app and group app. Try increasing verbosity when running your container, like docker run --progress=plain --rm ... for more feedback.

@MarkusRodler Can you try adding this to your code
RUN CHMOD ....

You can specifically change access perms I guess?

@MarkusRodler, it appears to be related to a permissions issue, for which there is a workaround provided. Consequently, we are closing this bug report. in case if you continue to experience any impact, please do not hesitate to open a new bug report.


How can I integrate socket.io with nuxt-app?

Or how and where can I get the http(s).Server object?

Or how and where can I get the http(s).Server object?

I guess you'd have to initialize nuxt with either Express or Koa?

https://medium.com/javascript-in-plain-english/introduction-to-nuxt-socket-io-b78c5322d389
I found this article on the topic. Apparently, there is a module. I love the dev community.

Hi, EmmyMay! Thanks. It's so nice of you to give me the information. I could fix the problem!


uwb firmware updates

added lunabot_embedded readme

whats left to do:

look at the test_netzer_encoder.ino then go into the interfaces.cpp and interfaces.hpp and look at the EncoderBus class.
make an equivalent class for uwb in interfaces.cpp under sensors using the uwb_sensor_test.ino as reference
then in the robot.cpp, make another namespace for uwb, and add an update fn similar to other sensors
then adjust the teensy_main.ino with the respective update fn for each uwb sensor distance field

try to get everything to compile first. you can compile on the luna computer by running the following commands:
jetson code:
catkin build

firmware:
roscd lunabot_embedded/firmware/teensy_main
teensy_compile

also can add ^ to readme too.


[WASM] implement (de)serializer to StdError

This is because the returned value of callable points needs available to (de)serialize.
Now StdError cannot be serialize, so callable point cannot return StdResult.

closed via #313


Use input name as output name for Fn API sink.

This appears to match what the Dataflow harness does.
Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[ ] Make sure the PR title is formatted like:
[BEAM-<Jira issue #>] Description of pull request
[ ] Make sure tests pass via mvn clean verify.
[ ] Replace <Jira issue #> in the title with the actual Jira issue
number, if there is one.
[ ] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

R: @vikkyrk, @tvalentyn

Redundant with #3445.


DATEPICKER: Previous month arrow displaying on initial load

Please verify the version of auro-form you have installed
1.5.0
Please describe the bug
When setting the calendarStartDate and caledarFocusDate to the same month, the previous month arrow appears upon first load. Once you interact with the datepicker by traversing through months, the arrow disappears.
Expected behavior
Previous month arrow does not display when calendarFocusDate and calendarStartDate point to the same month.
Exit criteria
Issue is fixed and both arrows for navigating months display properly.

Closing out this ticket as it will addressed in separate issue:

https://github.com/AlaskaAirlines/auro-formkit/issues/154


InvalidOperationError on Authenticate

Hey ,
When calling the kerberosClinet.Authenticate() , am getting the InvalidOperationError - "Connection pool maxed out at 11 connections " . Could I get some help regarding possible scenarios which can make this issue crop up and any possible solution ?

This happens when a client attempts to connect to more than 10 unique KDCs within a 30 second window. The client will pool all outbound connections based on target address, so one client to 11 KDCs will throw an error. The client is intended to be a on per-user basis and it will stick to whichever KDC it succeeded against first for a period of time or until it fails in the future, so it's unusual for the client to successfully connect to multiple servers in such a short period of time. I suppose if you're trying to open connections in parallel you could hit the maximum after all the pools are filled up, though that's not recommended.
Can you describe what you're trying to do here?
Also, there was this bug recently https://github.com/dotnet/Kerberos.NET/pull/158. It was fixed and there's an updated nuget package too.
Worst case you can bump up the max pool size:
var tcp = client.Transports.OfType<TcpKerberosTransport>().FirstOrDefault();
tcp.MaxPoolSize = 200;

Thank you Steve.
What I am trying to do is - from a .Net Core 3.1 application , I need to call a web api and pass a kerberos token to it. Currently , for every webapi call , am calling kerberosClinet.Authenticate() and then kerberosClient.GetServiceTicket() . The frequency of calling the web api is high. It can be upto 20-30 time in a minute. So , after some time of execution , I start getting the error which I have mentioned above.

I would recommend reusing the client if you can. It's intended to be used on a 1:1 basis per client credential.
Otherwise I would recommend increasing the MaxPoolSize to something larger and see if that resolves it. It sounds like you're genuinely making lots of connections concurrently which can't be pooled.

Hey Steve ,
I did resuse the client this time. But , the next error came up after approx 10-12 hrs . It said that "Cannot request a service ticket until a user is authenticated" . I am assuming that it means the client authorization has expired. Is there any way we can verify if the authorization is active or expired before calling the kerberosClient.GetServiceTicket() ?

You might try enabling ticket renewal.
client.RenewTickets = true;
That will keep tickets alive for about 14 days, at which point you must force a reauth.

From: NidG<EMAIL_ADDRESS>Sent: Wednesday, May 13, 2020 1:45:11 AM
To: dotnet/Kerberos.NET<EMAIL_ADDRESS>Cc: Steve Syfuhs<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [dotnet/Kerberos.NET] InvalidOperationError on Authenticate (#162)
Hey Steve ,
I did resuse the client this time. But , the next error came up after approx 10-12 hrs . It said that "Cannot request a service ticket until a user is authenticated" . I am assuming that it means the client authorization has expired. Is there any way we can verify if the authorization is active or expired before calling the kerberosClient.GetServiceTicket() ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/dotnet/Kerberos.NET/issues/162#issuecomment-627842464, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAJHTYOXWOSLT5BBQHOAEETRRJMZPANCNFSM4M53ZLKA.


Include Github releases in docs

Uses https://sphinx-github-changelog.readthedocs.io/en/latest/ to pull the changelog from Github Releases.
Requires SPHINX_GITHUB_CHANGELOG_TOKEN to be set to build the changelog.

And that worked https://xpublish--194.org.readthedocs.build/en/194/changelog.html


Option to send either raw HTML or body.innerText (default)

Up for debate. Today, just the text from body is grabbed, but having a better extraction process for this in the back end (browser that too, but more code space than a bookmarklet).
Then it can be up to the receiving end to do extraction of text. Daq-proc could have a cheerio processor included.

Make it a switch so the user can choose. Not sure how to do this without doing code for all the endpoint services.

To not break everything, make body.innerText default, so re-added bookmarklets behave the same.

This is what I'll try:
When reading
Check if rawHTML key exists. If yes, check if true (get raw HTML) / false (get body.innerText). If it doesn't exist / is not set, get body.innerText. This way, old bookmarklets indexedDBs will work with new code.
When writing / creating
rawHTML defaults to true. This will be the most common case for a search engine, document processing when the search engine reads the data from where it's stored. At this point it's easier to create elaborate document processors than in the bookmarklets code.

Whis goes really well with daq-proc, since cheerio is now a part of it. Will be able to have lots more logic in how to extract content from a page.


Support https links for Source/Sinks

Motivation
Currently we support submitting sources/sinks with an archive thats a weblink. This support is restricted to http links only. This pr adds support for https links as well.
Modifications
Describe the modifications you've done.
Verifying this change

[ ] Make sure that the change passes the CI checks.

(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

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): (yes / no)
The public API: (yes / no)
The schema: (yes / no / don't know)
The default values of configurations: (yes / no)
The wire protocol: (yes / no)
The rest endpoints: (yes / no)
The admin cli options: (yes / no)
Anything that affects deployment: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
If a feature is not applicable for documentation, explain why?
If a feature is not documented yet in this PR, please create a followup issue for adding the documentation

@jerrypeng you are right!


Rule Applied Twice Bug

I am encountering a bug where the actions for the actions in a rule will trigger twice in one execution. Normally, this is fine, if the rules are monotonic. But if you have a function that returns a primitive and has a merge function, then setting it twice could lead to incorrect results.
Reproducible use case
Here is a way to reproduce this bug. It's not super minimal, but it is a lot more minimal than the Python code I extracted it from.
What it does is turns an expression graph into a string of statements of each expression.
It works bottom-up, generating a string for each expression and also adding to the statements, if the expression defines a new variable, and incrementing the gensym.
It basically works, but it seems like the actions in the multiply rule are run twice on the same nodes instead of just once.
(function statements () String :merge (+ old new) :default "")
(function gensym () i64 :merge (+ old new) :default 0)
(sort Math)
(function Num (i64) Math)
(function Var (String) Math)
(function Add (Math Math) Math)
(function Mul (Math Math) Math)
(function expr (Math) String)
(rule ((= x (Var s)))
      ((set (expr x) s))
         )
(rule ((= x (Num i)))
      ((set (expr x) (to-string i)))
         )
(rule ((= x (Add y z))
       (= y_expr (expr y))
       (= z_expr (expr z)))
      ((set (expr x) (+ "_" (to-string (gensym))))
       (set (statements) (+ (+ "_" (to-string (gensym))) " = " y_expr " + " z_expr "
"))
       (set (gensym) 1))
         )
(rule ((= x (Mul y z))
       (= y_expr (expr y))
       (= z_expr (expr z)))
      ((set (expr x) (+ "_" (to-string (gensym))))
       (set (statements) (+ (+ "_" (to-string (gensym))) " = " y_expr " * " z_expr "
"))
       (set (gensym) 1))
         )
(Mul (Num 2) (Add (Var "x") (Num 3)))

(run 3)

(extract (statements))
(extract (expr (Mul (Num 2) (Add (Var "x") (Num 3)))))

It should print out:
"_0 = x + 3
_1 = 2 * _0
"
"_1"

But it duplicates the second statement instead:
"_0 = x + 3
_1 = 2 * _0
_1 = 2 * _0
"
"_1"

I am starting to debug this issue.
I added a few println's to see try to pinpoint what's going on. Here is a bit of the trace that I think is thee problem area:
Running Program([Load(Subst(2)), Load(Subst(7)), Set("expr"), Load(Subst(3)), Set("statements"), Literal(Int(1)), Load(Stack(0)), Set("gensym")])
Running Program([Literal(String("_")), CallFunction("gensym", true), Load(Stack(1)), CallPrimitive(Prim(to-string), 1), Load(Stack(0)), Load(Stack(2)), CallPrimitive(Prim(+), 2), Load(Subst(2)), Load(Stack(3)), Set("expr"), Literal(String(" = ")), Literal(String(" * ")), Literal(String("\n")), Load(Stack(3)), Load(Stack(4)), Load(Subst(4)), Load(Stack(5)), Load(Subst(3)), Load(Stack(6)), CallPrimitive(Prim(+), 6), Load(Stack(7)), Set("statements"), Literal(Int(1)), Load(Stack(8)), Set("gensym")])
  Concating: "_"
  Concating: "1"
  - > res: "_1"
  Concating: "_1"
  Concating: " = "
  Concating: "2"
  Concating: " * "
  Concating: "_0"
  Concating: "\n"
  - > res: "_1 = 2 * _0\n"
Running Program([Load(Subst(0)), Load(Subst(1)), CallPrimitive(Prim(+), 2)])
  Concating: "_0 = x + 3\n"
  Concating: "_1 = 2 * _0\n"
  - > res: "_0 = x + 3\n_1 = 2 * _0\n"
Running Program([Load(Subst(2)), Load(Subst(7)), Set("expr"), Load(Subst(1)), Set("statements"), Literal(Int(1)), Load(Stack(0)), Set("gensym")])
Running Program([Load(Subst(0)), Load(Subst(1)), CallPrimitive(Prim(+), 2)])
  Concating: "_0 = x + 3\n_1 = 2 * _0\n"
  Concating: "_1 = 2 * _0\n"
  - > res: "_0 = x + 3\n_1 = 2 * _0\n_1 = 2 * _0\n"

The last concat is the incorrect one, the _1 line shows up twice. The program before it is run I assume in the merge function for statements. The issue is that this has already been run.

I think this is related to #93. Basically, because there are sets in actions, semi-naive evaluation needs to duplicate the rule to ensure the correctness of semi-naive evaluation. If you run the rule with --naive flag, the output is as expected. In general, however, to ensure correctness, actions should be idempotent, and the merge function should either be a max operation or union, both of which are idempotent.

I agree with @yihozhang, and I also think that my proposal in #228 would fix this problem

If you run the rule with --naive flag, the output is as expected.

I gave this a go, and it's true that this will not have the double output. However, if you change it to more than (run 3) like (run 10), the --naive` run will have many more duplicate outputs. Whereas the non-naive flag will only have the one duplicate output.
So to recap:

With the default (seminaive) it will "properly" saturate  after running the action once, but in the one time it runs it it mistakenly duplicates the merge command
With --naive it will not saturate, infinitely adding to the string, but each time it adds it will only add it once.

I think I will close this with the understanding that non-monotonic merge functions are undefined behavior and they should not be relied on!


update grpcio

Signed-off-by: Xintao<EMAIL_ADDRESS>
What have you changed?
grpcio release 0.5.0, TiKV needs update.
What is the type of the changes?

Engineering (engineering change which doesn't change any feature or fix any issue)

How is the PR tested?

No

Does this PR affect documentation (docs) or should it be mentioned in the release notes?

No

Does this PR affect tidb-ansible?

No

Refer to a related PR or issue link (optional)
Prepare for the next PR about the issue

Seems that grpcio updated the version of prost to 0.6.1, which is not compatible with the old version.

Seems that grpcio updated the version of prost to 0.6.1, which is not compatible with the old version.

This PR is pending waiting for other dependencies to be resolved.

/merge

/merge

Why does this PR contains a change in https://github.com/tikv/tikv/commit/4a883dc46263e09fa8a2176a1be72c722f69af3f ?

Why does this PR contains a change in 4a883dc ?

To resolve conflicts


Webos discovered but not added in the UI

Home Assistant release (hass --version):
0.33.0.dev0
Python release (python3 --version):
Python 3.5.2
Component/platform:
discovery, webos
Description of problem:
Although https://github.com/home-assistant/home-assistant/pull/4250 was merged and the updated netdisco 0.7.6 works and dicovers the TV when run with python3 -m netdisco, HA still fails to add it to the web interface unless I manually specify the IP.
Expected:
Add discovered WebOS TV to the UI interface
Problem-relevant configuration.yaml entries and steps to reproduce:
media_player LG_TV:
  platform: webostv
  name: LG TV Dormitor
  customize:
    sources:
      - livetv
      - youtube

Additional info:
I've tried to debug myself the issue by launching "hass --open-ui" cmd manually and this is what I saw in the logs:
1st I see in the logs "ERROR:homeassistant.components.media_player.webostv:No TV found in configuration file or with discovery"
And funny enough, later on I see "INFO:homeassistant.components.discovery:Found new service: webos_tv <IP_ADDRESS>"
This makes me thing that the TV is discovered too late :(
OFF-TOPIC:
Now, as I've stated in earlier comments I'm not a python developer and I don't know how to debug myself HA issues, meaning I've tried to modify homeassistant/components/media_player/webostv.py by adding an extra log line but my change is not reflected; do I need to do anything else or how can I debug in general an issue in HA ?

This requires two steps:

Discovery component in hass needs to know this device is discoverable https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/discovery.py#L26
The webOS platform needs to be able to handle discovery info that is passed in .

Indeed...right now there's a pr on netdisco mentioned to enhance the info from webos...and soon I'll submit also the code in HA to reuse webos info, as right now after debugging I've noticed that its missing and that's why autodiscovery was not working for webos


Create Python bindings?

Hi,
Thanks for your work :)
To the best of my knowledge, python does not have a well maintained JSONPath library. Maybe it could be a good idea to create python bindings so that this library could be used from python.

Hi.
Thank you!
That is a very interesting idea.
But it needs to take a close look at how to do that.
Maybe you have something in mind already?

Hi,
Unfortunately I am not of much help here :( I just know it should be possible with pyo3.

No worries. I will give it a look

Hey folks, I started some work on creating python bindings:
https://github.com/night-crawler/jsonpath-rust-bindings
maturin develop

python
>>> from jsonpath_rust_bindings import jsonpath
>>> from jsonpath_rust_bindings import Finder
>>> f = Finder({'a': {'b': 42}})
>>> f
<builtins.Finder object at 0x7f342d92cc90>
>>> f.find('$.a')
[<builtins.JsonPathResult object at 0x7f342d4fe2f0>]
>>> f.find('$.a')[0]
<builtins.JsonPathResult object at 0x7f342d4fe830>
>>> f.find('$.a')[0].data
{'b': 42}

There's a standing question in regards Rust -> Python && Python -> Rust PyObject conversion and cloning: https://github.com/night-crawler/jsonpath-rust-bindings/blob/main/src/lib.rs#L48
Is it possible to have a JsonPathFinder not owning a Value?

Hey! Great to hear that! Thank you!
Is it possible to have a JsonPathFinder not owning a Value?
yeah, as far as I understand your question it is not possible since the given structure literally takes ownership of it.
pub struct JsonPathFinder {
    json: Box<Value>,
    path: Box<JsonPathInst>,
}

But this structure is just a helper structure to handle the given JSON (usually) from string and the given query(also usually from string).
You can try to avoid possession of the JSON value using a query directly.
  #[test]
    fn no_clone_api_test() {
        fn test_coercion(value: &Value) -> Value {
            value.clone()
        }

        let json: Value = serde_json::from_str(template_json()).expect("to get json");
        let query =<EMAIL_ADDRESS>size 10)].title")
            .expect("the path is correct");

        let results = query.find_slice(&json);
        let v = results.get(0).expect("to get value");

        // V can be implicitly converted to &Value
        test_coercion(v);

        // To explicitly convert to &Value, use deref()
        assert_eq!(v.deref(), &json!("Sayings of the Century"));
    }

is it what you need?

Great to hear that! Thank you!

Thank you too for your jsonpath efforts!

You can try to avoid possession of the JSON value using a query directly.

Right. In fact, I just wanted to have paths to the original extracted values returned always and got lost in the API a bit. I could use json_path_instance() function directly: https://github.com/night-crawler/jsonpath-rust-bindings/blob/main/src/lib.rs#L39
A side note and probably an off-topic. Currently, I'm converting PyObjects to Values with pythonize crate, and it seems that it clones the original values, which is not very efficient and has a side effect better demonstrated below:
Python 3.11.5 (main, Aug 30 2023, 19:09:52) [GCC 13.2.1 20230730] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> original_object_i_want_to_mutate = {'a': {'b': 'sample b'}}
>>> from jsonpath_rust_bindings import Finder
>>> f = Finder(original_object_i_want_to_mutate)
>>> b_dict = f.find('$.a')[0].data
>>> b_dict
{'b': 'sample b'}
>>> b_dict['new'] = 42
>>> original_object_i_want_to_mutate
{'a': {'b': 'sample b'}}

I wonder if it's wise to pursue it now, or save it for later. Any thoughts?

Right. In fact, I just wanted to have paths to the original extracted values returned always and got lost in the API a bit. I could use json_path_instance() function directly: https://github.com/night-crawler/jsonpath-rust-bindings/blob/main/src/lib.rs#L39

yeah, that works as well :). Great.

A side note and probably an off-topic. Currently, I'm converting PyObjects to Values with pythonize crate, and it seems that it clones the original values, which is not very efficient and has a side effect better demonstrated below:

Yeah, I will need to take a look at how the crate serializes the objects, but at first glance, looking into this test or that one it seems possible that the data gets cloned.
But, I wonder how to avoid cloning between Rust and Python as we don't share one object but transfer the data (maybe, I don't grasp it clearly though).
Anyway, regarding data mutations for now, even if you had gotten the pointer to the slice of original data, you would not be able to modify it, at least, from rust. There are a couple of open issues: #48 and #12
I would proceed with cloning now and then think about how to avoid it but later on.

So, here's the result: https://pypi.org/project/jsonpath-rust-bindings/
Regarding the conversion problem, there's already an issue but solutions mentioned in comments don't look like zero-copy to me. I'll allocate some time this week to see what else I can do with it.
And yet again, thank you!

that would be nice if you add a couple of lines into the readme, mentioning binding.

I apologize for the confusion, probably pypi returned you an old cached version with an empty readme (v0.1.0). The current one 0.1.1 explicitly specifies the link to the jsonpath-rust project. Also, I updated the readme with your name just in case (not yet published to the pypi).
If I didn't get the meaning of mentioning binding, please follow up on this or DM me. Thank you.

Ah sorry, I did mention it vaguely and that was the cause of the confusion. I meant the readme of this project.
Just a couple of lines that the current crate has a py binding with a link to it.


Integrate interchain-accounts and interchain-staking modules

Decided not to stake and divert funds to community pool / DAO instead.


Question about using keras without backend

Hi there,
In some cases, I just want to use awesome tools in keras without any backend framework. But I notice that there are mandatory conditions to run backend in keras/__init__.py and backend/__init__.py.
Is it possible to cancel or loosen those restrictions?
For example, allowing user to set _BACKEND = NONE.

It's not possible right now. But you can do a dummy backend and load it. To do that, you need to load an external backend. There is a PR to update the documentation to explain how to do that. See #11405


develop

feat(components): add Link
refactor(button): change color
refactor(button): add variant
docs(button): add disabled
style(link): change ILinkProps
docs(link): add href
feat(link): change classes
feat(link): add link color style
refactor(button): change classes
feat(button): add link color style
docs(link): change readme
test(link): add test for link color

Codecov Report

Merging #134 (248ea2f) into master (6cd3037) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master      #134   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            4         4
  Lines           31        31
  Branches        13        13
=========================================
  Hits            31        31

Impacted Files
Coverage Δ

src/components/Button/Button.tsx
100.00% <ø> (ø)

src/components/Link/Link.tsx
100.00% <100.00%> (ø)

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 6cd3037...248ea2f. Read the comment docs.


Broken link to ISO 27552

ISO/IEC27552 was renamed 27701 when published. Accordingly, the page at BSI is apparently updated breaking the link from this doc page.

A dokumentum adatai
⚠ Ezt a szakaszt ne szerkessze. A szakasz a docs.microsoft.com ➟ GitHub-problémák hivatkozásaihoz szükséges.

ID: aa744bac-87cf-7075-f9da-8254aaa1dd04
Version Independent ID: 3ce4c211-4adb-5a1f-d03b-8ac98d7fe885
Content: Azure accountability readiness checklist for the GDPR
Content Source: microsoft-365/compliance/gdpr-arc-Azure.md
Product: microsoft-365-enterprise
GitHub Login: @robmazz
Microsoft Alias: robmazz

@officedocsbot assign @mypil

@gaborvar - Thank you for submitting feedback.
I will get this issue over to the Microsoft 365 writing team for investigation.
Thank you for reporting and making the docs better. Much appreciated.
I made a note to request the team to update this when the work is complete.


Fixed issue #39284 by updating the challenge hours

Checklist:

[x ] I have read freeCodeCamp's contribution guidelines.
[x ] My pull request has a descriptive title (not a vague title like Update index.md)
[x ] My pull request targets the master branch of freeCodeCamp.
[x ] All the files I changed are in the same world language, for example: only English changes, or only Chinese changes, etc.

Closes #39284

Solved the issue by updating the challange hours from 400 to 300 in certificate.js

Hello~!
Thank you for submitting a potential fix, however I believe this is not correct. It looks like you are changing the estimated course length to 300 hours, but per this comment the estimates in the API are correct and it is the curriculum map that needs to be updated. 🙂

Hello~!
Thank you for submitting a potential fix, however I believe this is not correct. It looks like you are changing the estimated course length to 300 hours, but per this comment the estimates in the API are correct and it is the curriculum map that needs to be updated. slightly_smiling_face

The whole day i tried to remove this bug by trying to change this bug by exploring through the get_challenges and curriculum and all ...but i didn't get that how it is taking 400 hours instead of 300 hours.
And i am in doubt is that whether the freecodecamp is giving 400 hour instead of 300 hours, as i commit earlier in the code.

Thanks a lot for the pull request @anto-pv, we understand you are interested in fixing the estimates. Its a misconfiguration on the client views. I will add some comments on the thread.


test-branch/execute-job/wrong-commit-sha-on-pr/3e9e8c77-b93c-4d22-a45b-f50f64147d46

PR for testing f83d0c4476a908536ca462dcd2b85a3b5a37751a

/canonical/self-hosted-runners/run-workflows 8bb955d8c485c3813934e08182c08cc1072740bc


Update conda recipes for Ibis 0.5.1

Built and tested on osx-64, linux-64, and win-64.
Conda packages for Ibis 0.5.1 can be installed using:
conda install ibis-framework -c koverholt

thanks!


fix: check for 'patched_versions' key

This is a PR to solve this issue : https://github.com/nexB/vulnerablecode/issues/154

Thank you for the PR! , the code will fix the  key error but that's not enough . We need to make some changes to the rust-sec importer to adopt to their changed schema. The files with absence of patched_versions field  have adopted a new way to denote patched versions, we have to collect that data. So simply checking for the patched_versions field wont fix the problem completely.

@sbs2001 this is the new Schema
{'advisory': {'id': 'RUSTSEC-2019-0016', 'package': 'chttp', 'date': '2019-09-01', 'title': 'Use-after-free in buffer conversion implementation', 'description': 'The From<Buffer> implementation for Vec<u8> was not properly implemented,\nreturning a vector backed by freed memory. This could lead to memory corruption\nor be exploited to cause undefined behavior.\n \nA fix was published in version 0.1.3.\n', 'url': 'https://github.com/sagebind/isahc/issues/2', 'keywords': ['memory-management', 'memory-corruption']}, 'versions': {'patched': ['>= 0.1.3'], 'unaffected': ['< 0.1.1']}}

I've updated my PR to work with the new schema:
unaffected_version_range_list = advisory['versions'].get(
            'unaffected', [])
patched_version_range_list = advisory['versions']['patched']

LGMT !  @EslamHiko thank you ++ .
@haikoschol  please review and merge.

@EslamHiko @sbs2001 thank you!


Request for hoavan high school

Added hoavan.txt to request the inclusion of Hoa Van High School in the IntelliJ Education Pack list.

@joanjudiqddoe Regrettably, this request has signs of fraud. I have to close it without merging.
It does not mean that something is wrong with the school. The issue is related to a combination of suspicious factors related to the domain itself.
Please enroll to GitHub Student Developer Program at https://education.github.com/discount_requests/application. Then apply for JetBrains educational subscription with your GitHub account (GitHub tab at https://www.jetbrains.com/shop/eform/students).
Thank you for your understanding!


Thoughts about categories

....

feedback from UX coach: categories list too much profiles to browse. Is it possible to limit these profiles to around 50?
Options:

have aggregations to filter as in search
create smaller/more specific categories


Import external references by default

Following #30, now that we have simplified a lot the references code in this project, I think that it may be a good moment to switch to a mode where we resolve/bundle all the references by default.
This is the goal of this PR.
However, we have to keep 2 things in mind:

resolving references by default implies opening/reading/parsing the source files. So we add more logic as the default behavior, that could lead to potential bugs (that, at the moment, we don't monitor)
the previous --import-external-references is now obsolete. In its current state, this PR fully removes it. It means that any call with it will lead to an error. Some of our users automatically update the gem, without any limitation about the used version, so it could break their CI until they remove the call. We can also keep it for now as a dead parameter, adding a deprecation warning as we do for the --id before we remove it in a new version.

@Polo2 do you have opinions on this? Maybe, also, @paulRbr if you want to have a look?

So we add more logic as the default behavior, that could lead to potential bugs

this could be mitigated by:

checking most common errors (http calls leading to 404, inexistent local file, …) to help the end users debug their own configuration
for any other error, warn the user that we don't know what's wrong and ask them to send a bug report to https://github.com/bump-sh/bump-cli/issues

In its current state, this PR fully removes it. It means that any call with it will lead to an error.

I agree with @Polo2: add a depreciation warning instead of stopping with an error

Thanks for the comments folks, I agree with both of you. I kept the legacy parameter and added a deprecation warning in this PR.
I will also add another PR before releasing the new gem version with a better message for runtime errors.


Add a flag to skip every test that requires credentials

Hello!

Vote on this issue by adding a 👍 reaction
If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

It will be useful to have a way to run all tests that do not require cloud credentials. If not useful internally, I'm sure it will be appreciated by third-party contributors who do not have time to setup test credentials. Currently the framework is setup to run some tests that do end up requiring credentials (E2E quick, PreviewOnly upgrade), but it already is starting to have some tests that can exercise the provider without requiring credentials (PreviewOnly quick) and we expect to have more of these in the future, especially if they are snapshot based.
The concrete suggestion here is to implement a flag, perhaps --provider-unit or --provider-no-creds, that would skip all tests that would fail if credentials are not present. This flag can later on support a Makefile target or some such helper.
Affected area/feature

@danielrbradley quick idea from this morning discussion. It's not strictly necessary but I think it can be useful.

I think this is tricky to know because it depends on the provider implementation. Some providers require cloud access to validate credentials during their Configure call while others only check that required fields are set.

Perhaps the provider could mark  or communicate this to the framework.
Or perhaps we could go the other way and add flags that make providers skip cred verification specifically so that they would be more amenable to testing under this flag.