[SPARK-25734][SQL] Literal should have a value corresponding to dataType

What changes were proposed in this pull request?
Literal.value should have a value a value corresponding to dataType. This pr added code to verify it and fixed the existing tests to do so.
How was this patch tested?
Modified the existing tests.

Test build #97384 has started for PR 22724 at commit 9115d26.

LGTM

Test build #97384 has finished for PR 22724 at commit 9115d26.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
      s\"but $

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/97384/
Test FAILed.

Test build #97419 has started for PR 22724 at commit b00f4bb.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/4009/
Test PASSed.

Test build #97427 has started for PR 22724 at commit a30e9ce.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/4017/
Test PASSed.

Merged build finished. Test PASSed.

Test build #97427 has finished for PR 22724 at commit a30e9ce.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/97427/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/4020/
Test PASSed.

Test build #97431 has started for PR 22724 at commit 56b4778.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/4021/
Test PASSed.

Test build #97432 has started for PR 22724 at commit 4df5abd.

Test build #97431 has finished for PR 22724 at commit 56b4778.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/97431/
Test FAILed.

Test build #97433 has started for PR 22724 at commit 1c042f3.

LGTM pending jenkins

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/4022/
Test PASSed.

Test build #97432 has finished for PR 22724 at commit 4df5abd.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

I'm checking the reason of the test failures...

Test build #97433 has finished for PR 22724 at commit 1c042f3.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/97433/
Test FAILed.

Test build #97439 has started for PR 22724 at commit 60a7793.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/4024/
Test PASSed.

Test build #97443 has started for PR 22724 at commit 77f65f9.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/4027/
Test PASSed.

Test build #97439 has finished for PR 22724 at commit 60a7793.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/97439/
Test FAILed.

Test build #97443 has finished for PR 22724 at commit 77f65f9.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/97443/
Test FAILed.

Test build #97451 has started for PR 22724 at commit a2f0288.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/4031/
Test PASSed.

LGTM, but this is a breaking change, so I'd suggest to do it only for 3.0 and add a note to the migration guide. WDYT?

yea, its ok to do so.

Literal is an internal API, and AFAIK end-users can't construct an invalid Literal with public APIs. If they can, then it's a bug and we have a problem...

yes, you're right. So we don't need any migration note. But what if a user uses Literal directly? He/she shouldn't, but we cannot exclude this is happening. So I'd still target this for 3.0 only.

yea +1 on 3.0 only, this is kind of a developer API, advanced users may use it.

Test build #97451 has finished for PR 22724 at commit a2f0288.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/97451/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/4035/
Test PASSed.

Test build #97457 has started for PR 22724 at commit 04a535d.

Test build #97457 has finished for PR 22724 at commit 04a535d.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/97457/
Test PASSed.

thanks, merging to master!


chore(docs): fix misspelling in README

Simply correcting the misspelling|typo of you're/your.

Codecov Report

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

@@          Coverage Diff          @@
##           master   #250   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           4      4
  Lines         295    295
  Branches       71     71
=====================================
  Hits          295    295

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 936c8e0...07b7285. Read the comment docs.


Make IR-video tracker work when pixels are not saturated

The SimpleBlobDetector() call is not detecting blobs in simulated images when the LEDs do not saturate the pixels they are in.  This restricts the code to working when the gain/exposure is such that the LEDs are saturated, which is a limitation it would be good to remove.

Adjusting the LED brightness has resolved this issue.


Yotta to stash linked modules

There were many times problems during the development, when clean of modules was required to do to get fresh new dependencies (not all of them were linked), which caused that link modules were gone. what's the behaviour for linked modules after yotta clean, or when changing a target?
I overcome this taking pictures of all my linked modules, and manually restore them. Is there a way how yotta can capture what are linked repo (at least names for give target)? I am thinking about something like stash pop/push functionality.
@rgrover You had similar problems when local linking, you might add some more info.

to be clear: yotta clean does not remove the modules cache directory, only the build directory.
It sounds like we should fix whatever the underlying problem was that caused you to have to remove the modules directory in the first place: it might have been this issue?

I have been testing the latest yotta version in the last 2 hours, and seems to be consistent when changing targets or updating modules. I'll close this for now. If I ever come back to this, I'll reopen and add detailed description.


documentation/cli: fix typo

format whatis <expression>

nit: commit message should be documentation/cli not document/cli. Will merge after that is corrected.

Done,Fix and rebase.Thx.


Camera: Take snapshot issue

Does the take snapshop option work with the vivint camera in this integration.  I can't seem to get the snapshot saved to a file or am I just doing something wrong

Yes, snapshots should work just find.


Deprecated member initializers

For shapes with deprecated member variables

Remove deprecated variables from standard init function
Add an additional init which is flagged as deprecated which includes deprecated variables

Soto Code generator PR is https://github.com/soto-project/soto-codegenerator/pull/34
This resolves #352

Is there a reason to keep a deprecated initialiser around if we're prepping a major release?

Is there a reason to keep a deprecated initialiser around if we're prepping a major release?

These are variables deprecated by AWS. I won't be able to tell the difference between a newly deprecated variable and one deprecated prior to v6, so won't know if I can delete it. So am just sticking to deprecating all of them. AWS's versioning of model files is separate from the Soto version.


[change-case] not working correctly with Latin characters

Extension
https://www.raycast.com/es183923/change-case
Description
When you use the extension with Latin characters like ó or ' they do not appear in the extension resulting in words with missing characters. I see that also commas, if they come after a Latin character, are not included.

Yes, that's because the lib that is used doesn't support these characters. Feel free to PR a fix using a different lib that supports accents and other characters.

I would love to, unfortunately, I am not a JS/TS developer.

Merged in https://github.com/blakeembrey/change-case/pull/296
Need to update change-case version once it comes out.

Related issues: #7420 #7452

@raycastbot reopen this issue


Removes the extra visibility from access_loggers.stream

Commit Message: Removes the extra visibility from access_loggers.stream
Additional Description:
In the effort to enforce the visibility policy of extensions #35026,
this removes //test:__subpackages__ visibility from stream access logger
extension. To achieve that, this migrates its configuration tests previously
placed in test/common/access_log/ to the correct location in test/extensions/**.
Risk Level: none
Testing: done
Docs Changes: n/a
Release Notes: n/a
Platform Specific Features: n/a

/retest

/retest

/retest


chore(release): prepare for release

Description
Latest release for FlutterFire CLI - 0.3.0-dev.17
Type of Change

[ ] ✨ feat -- New feature (non-breaking change which adds functionality)
[ ] 🛠 fix -- Bug fix (non-breaking change which fixes an issue)
[ ] ❌ ! -- Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🧹 refactor -- Code refactor
[ ] ✅ ci -- Build configuration change
[ ] 📝 docs -- Documentation
[ ] 🗑 chore -- Chore

closed in favour of: https://github.com/invertase/flutterfire_cli/pull/209


Create Redux store to track QC status

Background
Link to issue
https://biomage.atlassian.net/browse/BIOMAGE-608
Link to staging deployment URL
TBD
Links to any Pull Requests related to this
N/A
Anything else the reviewers should know about the changes here
As agreed with Agi, the only purpose of this ticket is to track whether or not the pipeline is currently running. A Redux store did not need to be created because we can query the API directly for this data. In addition, this data may be subject to change relatively quickly and it is more difficult to block high-level components like pages based on the contents of the Redux store.
It also includes a sample component on how to block out pages and paths if a pipeline is running. This is partially in scope for another ticket, BIOMAGE-498, but it was necessary in order to test properly if the alternative way I proposed meets the requirements for the downstream tickets.
Changes
Code changes
Added a check in _app.jsx that automatically queries the state of the pipeline on page load. Depending on the data, it can trigger ContentWrapper to disable or enable pages from loading. We can also potentially use this data downstream in BIOMAGE-498 directly, depending on the implementation there.
Definition of DONE
Your changes will be ready for merging after each of the steps below have been completed:
Testing

[x] Unit tests written
[x] Tested locally with Inframock
[ ] Deployed to staging

To set up easy local testing with inframock, follow the instructions here: https://github.com/biomage-ltd/inframock
To deploy to the staging environment, follow the instructions here: https://github.com/biomage-ltd/biomage-utils
Documentation updates
Is all relevant documentation updated to reflect the proposed changes in this PR?

[x] Relevant Github READMEs updated
[x] Relevant wiki pages created/updated

Approvers

[ ] Approved by a member of the core engineering team
[ ] (UX changes) Approved by vickymorrison (this is her username, tag her if you need approval)

Just before merging:

[ ] After the PR is approved, the unstage script in here: https://github.com/biomage-ltd/biomage-utils is executed. This script cleans up your deployment to staging

Optional

[x] Photo of a cute animal attached to this PR

Changes requested by @aerlaut are done.


Chainpoint Package for anchoring data to public blockchains

Overview:
This package allows you to submit hashes to nodes on the Chainpoint Network that will subsequently anchor data to the Bitcoin blockchain. This allows one to cryptgraphically prove that a particular piece of data existed at a point in time.
Methods:
1) SubmitHashes(uris NodeList, hashes []string)
The SubmitHashes function will submit a list of hashes to every Chainpoint Node provided to it via the function's first argument uris of type NodeList. Submitting to multiple Chainpoint Nodes to achieve your required level of redundancy is advised. Only a single Chainpoint Proof is required to attest the existence of your data.
The SubmitHashes function will return an array of ProofHandles[]:
type ProofHandle struct {
	Hash       string `json:"hash"`
	HashIDNode string `json:"hashIdNode"`
	Uri        string `json:"uri"`
}

Note: The HashIDNode value being returned is a UUID V1

Example:
var RANDOM_NODES = []Node{{PublicUri: "http://<IP_ADDRESS>"}, {PublicUri: "http://<IP_ADDRESS>"}}

hashes := []string{"1957db7fe23e4be1740ddeb941ddda7ae0a6b782e536a9e00b5aa82db1e84547"}
proofHandles, err := SubmitHashes(RANDOM_NODES, hashes)

The result returned by SubmitHashes is of type []ProofHandle
type ProofHandle struct {
	Hash       string `json:"hash"`
	HashIDNode string `json:"hashIdNode"`
	Uri        string `json:"uri"`
}

2) GetProofs(proofHandles []ProofHandle)
The GetProofs function accepts a list of Proof Handles and will retrieve their corresponding Chainpoint Proofs. This function includes the subtle optimization of grouping Proof Handles by Chainpoint Node PublicUri's and will issue one HTTP GET request with an embedded header value consisting of a comma-delimited string of hashIdNode values dictating which Proofs need to be resolved and returned to the requestor.
The GetProofs functions returns a type of []ProofBody
type ProofBody struct {
	Anchors    []interface{} `json:"anchors_complete"`
	HashIDNode string        `json:"hash_id_node"`
	Proof      interface{}   `json:"proof"`
}

By default, the Proof returned is a base64 encoded string and is essentially the only piece of data that needs to be persisted. This base64 encoded Proof will be used in any requests to verify the integrity of a Proof.
Example:
// Step #1: Submit Hashes
proofHandles, err := SubmitHashes(RANDOM_NODES, hashes)

// Delaying the invocation to `GetProofs` is required due to the nature of how the Chainpoint Network operates. More info as to why can be provided upon request.
time.Sleep(18 * time.Second)

// Step #2: Provide the returned `Proof Handles` result from invoking `SubmiHashes()` as the only argument to `GetProofs()`
proofs, err := GetProofs(proofHandles)

3) VerifyProofs(proofs []string)
The VerifyProofs function accepts a list of base64 encode strings that will be submitted to any Chainpoint Node for verification. The verification process will perform the required cryptorgraphic operations for both cal and btc branches to verify the integrity of the Chainpoint Proof(s) that have been submitted.
Example:
// Step #1: Submit Hashes
proofHandles, err := SubmitHashes(RANDOM_NODES, hashes)

// Delaying the invocation to `GetProofs` is required due to the nature of how the Chainpoint Network operates. More info as to why can be provided upon request.
time.Sleep(18 * time.Second)

// Step #2: Provide the returned `Proof Handles` result from invoking `SubmiHashes()` as the only argument to `GetProofs()`
proofs, err := GetProofs(proofHandles)

// Step #3: Provide the returned `Proof` base64 encode strings that were returned from the `GetProofs()` function call as the only argument to `VerifyProofs()`
verifiedProofs, err := VerifyProofs([]string{"<base64EncodedProof>, ..."})

The call to VerifyProofs() will return a list of Proof verifications that have the following type:
type VerifiedProofs []struct {
	ProofIndex          int       `json:"proof_index"`
	Hash                string    `json:"hash"`
	HashIDNode          string    `json:"hash_id_node"`
	HashSubmittedNodeAt time.Time `json:"hash_submitted_node_at"`
	HashIDCore          string    `json:"hash_id_core"`
	HashSubmittedCoreAt time.Time `json:"hash_submitted_core_at"`
	Anchors             []struct {
		Branch string `json:"branch"`
		Type   string `json:"type"`
		Valid  bool   `json:"valid"`
	} `json:"anchors"`
	Status string `json:"status"`
}

Pull Request Comments:

Please provide any feedback regarding design patterns, coding style guide faults, etc. that are of concern so they can be resolved.
Unit tests are coming soon!

This looks great, thanks!
@pkankipati and I will review this week.

Also @mdawn


Add support for PureRef files

Hi there! I love the app; it works very well!
I was wondering if it was possible to add support for loading in (and maybe saving as, too?) PureRef project files, so it's possible to work on a project on both PC and mobile interchangeably.
Oh, and another small thing that might be nice is adding that when you long press a button, a small toast message pops up next to it with the name of the button. I just had to look at the code to find the difference between the Save and Save As button.

Potentially. It would depend on how many incompatible fields there are in the .pur format that aren't in the default format. Also, since it's proprietary the format could change in the future. It would just mean some work to add an import/export feature, but I am busy with other things at the moment.

Any chance for support to come ?


Replaced modwork.shop links (dead) with modworkshop.net links (not dead)

modwork.shop is dead

pog
(I'll let you handle updating the version number in mod.xml and updating the modworkshop version)


[Feature]: add support for ibm db2

Is there an existing issue for this?

[X] I have searched the existing issues

Summary
Hi all, good project!
I noticed that in in database list is missing ibm db2 as400 driver .
Why should this be worked on?
A lot companies still use as400 as mainframe ( in example my company )

Can confirm this, as I also have a client that currently searches for LC Applications and needs to connect to their AS/400 DB/2 Database.

We are also using as400 systems, adding the driver enable us to use this nice solution

news on that?


[Proposal] Eloquent set cast attribute dynamically

In laravel 5.1 there is new feature called Attribute Casting
My question is, it is possible to make attribute casting dynamically ?
for example, if there is table with columns :

Id
Name
Value
Type

1
Test_Array
[somearray]
array

2
Test_Boolean
someboolean
boolean

it is possible to set of value attribute cast, depends on type field, that work both in write(create/update) and fetch ?
in Eloquent Model there is setAttribute method, how about to add method setCasts()  too. ?

I was test it, add the setCasts() method within my own model.
<?php

namespace App;

use Illuminate\Database\Eloquent\Model;

class Option extends Model
{
	/**
     * The attributes that are mass assignable.
     *
     * @var array
     */
    protected $guarded = [];

    public function setCasts(array $casts)
    {
    	$this->casts = $casts;
    	return $this;
    }
}

// this is work
$options = (new \App\Option)->setCasts(['value' => 'array']);
$options->fill($data)->save();

// but using create() method doesn't work
$options = (new \App\Option)->setCasts(['value' => 'array'])->create($data);


Apply the same approach to standard multi-view hand-eye problems

Dear authors,
thanks for the work, it is very impressive and seems useful also in other multi-camera setups.
E.g., we would like to apply the same method to "standard" robot-camera hand-eye problems, when more than one camera is involved. Can you give a short list of steps that you would follow in that case?
In particular, I see that your code is implementing the calibration of non-overlapping camera setups, in which the external Vycon system is required. What if the setup is the following?

1 Robot that mounts the calibration board on his end-effector
N cameras looking at the robot, observing the scene and the chessboard moving in the workspace

I understood that your problem can be easily ported to our setup by taking into account some "modifications" to your implementation, e.g. the GT trajectory in your case is the trajectory of the chessboard in the Vycon reference system, in our this should be the trajectory of the chessboard in the robot reference system, so, your Vycon origin is equivalent to our robot origin, am I right?
Last thing, is there a way to get from your code the position of each camera w.r.t. the vycon system? I understand the result of your implementation is doing the following assumptions:

camera 1 is the reference
each camera extrinsics is expressed w.r.t. camera 1

Correct?
Thanks in advance for your help.

Hi,
Thanks for your messages.
Yes it could be extended to the setup you described, if you replace the Vycon system to your carefully calibrated robot arm., and Vycon origin is equivalent to the robot origin.
Besides, you can definately get the position of each camera w.r.t to the vycon system, and actually it is one of the direct output of the solver.
If anymore questions, feel free to post here or send to my emails<EMAIL_ADDRESS>or you can read our paper:
https://arxiv.org/pdf/2202.00886.pdf
BR,
Yifu


255 security

I think, it would be better, if @fblampe had a look at this. I do not understand most of it. For the JS part, @Holger-GZ might help? Or do the review?


Howto round time labels with moment.js

Hi !
I start to use the time labels with moment.js
I added slight modification using:
return moment.unix(value).format('HH:mm');
instead of
return moment(value).format('HH:mm');
This is just to get rid of the 3 last digit "milliseconds" in my timestamps.
My aim is to display some graphs over 24h.
The labels works but have unconvenient format, like: 21h25 1h24 5h23 9h22 13h21 and 17h20.
Would it be possible to round a bit those values?
For example, start from 21h00 and then every 4 hours.  (21h-1h-5h-9h-13h-17h)

Just to share some findings:
return moment.unix(value).startOf('hour').format('HH:mm');
Will show nice values, but wrong...the graph remain exactly same as before while I expect it to be shifted.
(for example, if I start from 21h00 instead of 21h25, it should be 25min shifted)

Ok, I found a workaround:
I added in my a series 2 data, one at the rounded 1st hours, and rounder to the upper last hours.
Both timestamp has no data (y: "None"), the no point/line appear on graph.
Seems to work.

Ok, now I have an other question:
Can I use a fixed scale on X axis ? if yes, how ?
Is it possible to just specify low and high value for x axis only ? (1st and last point on x) ?

Hello @bonjour81 👋
Chartist has recently been updated to version 1.0 with some new exciting changes like ESM and TypeScript support. The migration guide can be found right here.
Please let me know if the question is still relevant to you so we can further look into it!


Add transpose before ExtractSliceOp

Addresses this SHARK-TestSuite issue related to ExtractSliceOp causing compilation failures. torch-mlir is generating tensor.extract_slice ops that split the tenser in two along the innermost dimension. This prevents the extract_slice ops from being converted into memref.subview ops.
Also, the same can be done for the concat op (from the issue) but I wanted to get this out because it fixes the compilation error with SHARK-TestSuite

I'm not sure we want to do this. This looks like a codegen problem that we're solving by changing the form in global optimization. In general extracting from the outer most dimension is best, however that's something that needs to be applied prescriptively (see the option for transposing concat behind a flag here:
https://github.com/iree-org/iree/blob/58feff319e2fd0dff7909358741a26ffa5807823/compiler/src/iree/compiler/GlobalOptimization/DecomposeConcat.cpp#L96
) and otherwise you run the risk of paying the cost of two additional transposes.

Okay, It does seem to need a fix below flow. Is the problem that transpose+extract vs extract should have no difference at the flow level (and the reason it does is due to codegen not finding the optimization)?
I will need some help with fixing this at the codegen level. @hanhanW would you be able to direct me?

Is the problem that transpose+extract vs extract should have no difference at the flow level (and the reason it does is due to codegen not finding the optimization)?

The issue I have is that AFAICT the choice between extract_slice and transpose + extract_slice is dependent on it's producers and consumers, hence why the concat pattern is behind a flag. Looking closer at your example test, the pattern does seem reasonable in this case though. I think this would be good to land behind a flag (maybe factored under the same flag as the concat transposing flag) which we aim to make default once we understand the effects across workloads better.

I will need some help with fixing this at the codegen level. @hanhanW would you be able to direct me?

Sorry I missed the original issue. So it looks like it is generating 150K IRs which is really bad. Looking at the example, I wonder if they are collapsed to 2D tensor or not before going to codegen or not. https://github.com/iree-org/iree/pull/17530 could help the big vector issue.

Sorry I missed the original issue. So it looks like it is generating 150K IRs which is really bad. Looking at the example, I wonder if they are collapsed to 2D tensor or not before going to codegen or not. #17530 could help the big vector

I just tested with those changes and it fixes the 150k IR ops being created, but iree still fails due to excessive stack allocation from alloca of memref<1024x7x7x2x32f>.

I took a look at the IR dumps (and thank you for attaching it!), I wonder why do we fuse generic + extract_slice + generic into a single dispatch? The tensor.extract_slice op does not implement tiling interface, which should not show up in between. I feel that it should belong to its own dispatch, and becomes a copy op? The fusion result in my mind is dispatch(generic) + dispatch(copy) + dispatch(generic). Does it make more sense?

Both the dequantize-like generic and the slice get cloned. It comes from here: https://github.com/iree-org/iree/blob/d7744b74023c6096d6d11c97d9d0f0277edda28a/compiler/src/iree/compiler/Dialect/Flow/Transforms/RegionOpUtils.cpp#L598-L609
It should be fused as to not materialize any f32 tensors are on the edges of dispatches (because the first linalg.generic is a dequantization-like operation). The transposes need to be moved above the generic so they can be added to the same dispatch. Also, it might make sense to change the logic around cloning extract_slices to only clone read-only or continuous extract_slice ops (transposes make this continuous).

Just to note here, @IanWood1  and I discussed this more. It might make more sense to take a broader view of this. The issue here is that the concat is happening on the inner most dimension and working backwards that gets the extract_slice along the inner most dimensions. Working from the concat backwards we might be able to reason about the extract_slice better, instead of doing this as a one-off.
Does this capture our discussion correctly @IanWood1 ?

If this is starting from a tensor.concat, we can try turning on --iree-opt-outer-dim-concat. Agree that concat is certainly easier to reason about than extract_slice and would be better to start with. Also if benchmarks are happy with this change, then I won't block, but I'm not yet convinced that it's always best to transpose concatenations along the inner most dimensions to the outer most (at least we saw one case in llama where it seemed as though such a transpose was counter productive).

If this is starting from a tensor.concat, we can try turning on --iree-opt-outer-dim-concat. Agree that concat is certainly easier to reason about than extract_slice and would be better to start with. Also if benchmarks are happy with this change, then I won't block, but I'm not yet convinced that it's always best to transpose concatenations along the inner most dimensions to the outer most (at least we saw one case in llama where it seemed as though such a transpose was counter productive).

I think the plan is to start with a pre-processing pass and use when needed.


Action is not within action space error while running Hopper-v1.

I tried to reproduce hopper-v1 on ubuntu on the latest commit, but I am getting the following error/warning. Could you please help me to figure out what I am doing wrong ?

I think the issue is because of the new version Hopper-v1 that seems to have different range of action space values.

This is a bug but it won't cause any functional problem. I should modify the code to clip the actions to be within the range. I didn't notice this issue before because Gym didn't print out those warning.

Thanks :)


Fix selector / series formatting for empty metric names

Fixes https://github.com/prometheus/prometheus/issues/15335

@jesusvazquez Whoops I opened this PR against main when I just said I was gonna open it against release-3.0 😅 I'll just do both then.


Get-DbaHelpIndex, added fragmentation, fixes #1216

Type of Change

[ ] Bug fix (non-breaking change, fixes #)
[x] New feature (non-breaking change, adds functionality)
[ ] Breaking change (effects multiple commands or functionality)
[ ] Ran manual Pester test and has passed (`.\tests\manual.pester.ps1)
[ ] Adding code coverage to existing functionality
[ ] Pester test is included
[ ] Nunit test is included
[ ] Documentation
[ ] Build system

Purpose
Add fragmentation info as requested in #1216
Approach
A simple join to dm_db_index_physical_stats sufficed.

Let's review this in the process and while I'm fresh with it, the select is a beast.........seems to me it needs a bit of love but ATM I lack forces for a good style review to port this to 1.0 readyness.

I'd be happy to.

on top of my head, I'd start with:

it accepts only a single sqlinstance

check that, it was a bunch of changes

oh wait, i need to add our normal 3, brb

i messed up the test. will fix in dev if it fails, i wanna get this show on the roadd


Command external airlocks

About the PR

Adds a new variant of an external access airlocks that requires command access.
Why / Balance

I need it for mapping (for the AI core specifically)
Requirements

[X] I have read and am following the Pull Request and Changelog Guidelines.
[X] I have added media to this PR or it does not require an ingame showcase.

#33333
🎉🎉🎉🎉🎉🎉🎉


Understanding the interval column

Question to VMM.
The sheet vegetatie-ontwikkeling has a column called interval with a controlled vocabulary: 0-10m, 10-20m,20-30m, ... up to 90-100m. These values cannot be related to depth as the depth of the waterbodies is never as deep as 100m (most of them are 1 to 2 meters deep). Is it the distance to the banks? Is it the distance upstream or downstream?

Based on pdf in attachment, the data are related to 100m transects. They are then divided in 10 subtransects, each of them 10 meter long. The XY coordinates of the 100m transect is the most downstream point. Original text in Dutch from pdf:

De xy-coördinaten worden ter plaatse zo precies mogelijk met de GPS bepaald op het meest
stroomafwaartse punt van het traject.

GP_3111_v7.pdf
.

Corrected in 503059b3d65820f2d98248b6d67fba9770c20c89. Expressed as:
21327837,submerged plants 0-10m upstream,frequent to abundant,,
21327837,submerged plants 10-20m upstream,frequent to abundant,,
21327837,submerged plants 20-30m upstream,frequent to abundant,,
21327837,submerged plants 30-40m upstream,frequent to abundant,,
21327837,submerged plants 40-50m upstream,frequent to abundant,,
21327837,submerged plants 50-60m upstream,frequent to abundant,,
21327837,submerged plants 60-70m upstream,frequent to abundant,,
21327837,submerged plants 70-80m upstream,frequent to abundant,,
21327837,submerged plants 80-90m upstream,frequent to abundant,,
21327837,submerged plants 90-100m upstream,frequent to abundant,,

Even though starting position is precise, the coordinate uncertainty radius is set to 100m (the maximum distance walked) because occurrences are collected along the way.


how to set that align in columns case branch?

how to set that align in columns case branch
for example：
when(type){
1-> true
else -> false
}
expect: align arrow

@xyz-fly sorry for the delay.
do you mean you'd expect:
when(type){
1-> true
else -> false
}

to be formatted to
when(type) {
    1    -> true
    else -> false
}

?
if so, that is relatively non-standard formatting, and it would actually be rather difficult to implement, so that's not something we'd support. Please re-open if I'm misunderstanding.


Disable for some tokens

Hi. Great module.
Can you add an option in the token settings to disable token hover?
It's useful when you have tokens you don't want to show art.

3D models with the 3d module
Item piles
etc

Hi Brunocalado,
This is a new feature in v2.0.1 of Image hover, you will need to update the module, glad you like my module!


✨ I want to add bitbucket pipline Integration

What are you trying to do?
https://docs.dagger.io/7442989/cookbook#integrations
Unfortunately, there is no integration for bitbucket pipeline in the documentation.
It would be nice if this part could be added. :)
Why is this important to you?
There are many users who use bitbucket pipeline. If the function is introduced, I think that companies will use it a lot in enterprise units.
How are you currently working around this?
No response

I can take this on :)

Hi @paikend,
I'm sorry to inform, but after looking into the issue, we are currently unable to run dagger from bitbucket pipelines.
Bitbucket has restricted the ability to run docker commands with the --privileged flag set to true (source), and currently dagger is configured to run Buildkit with privileged set to true: dagger/engine/server/buildkitcontroller.go.
The request was made in this discussion as well.

Hi @dzeleniak,
Thank you for your efforts to support.
I posted an issue on the bitbucket community.
I'm interested in the CI/CD field, so I want to help Dagger grow.
thank you

Is it really required to run dagger in privileged mode?
Maybe this can be changed to be configurable from the outside as a tradeoff between having only a subset of features vs having no dagger at all.
I think generally it is not a very good practice from a security point of view to even allow containers running in privileged mode?

Yes, Dagger requires privileged mode. The operator manual has a section that explains why.
@jpadams addressed a while back:

https://github.com/dagger/dagger/discussions/1677#discussioncomment-3195089

Closing since there are no new alternatives in the last 6 months.


new website background, same as ig post

new website bg now added
will be released in next version (beta 4.1)


add support for openshift in e2e tests

Right now we generate openshift configs like DeploymentConfig and Routes, add tests to e2e test suite to test this.

We can start using oc cluster up openshift cluster to run the test suite
And then find a way to talk to openshift cluster to query the openshift objects to write the tests for openshift

What's the status on this @ashetty1 I could possible help with this.


Error: no matching manifest for linux/arm64/v8 in the manifest list entries

I'm having this error when trying to pull on Docker:
docker pull ghcr.io/luislavena/greek-steam:8.2.25

Got this first when trying to deploy a Laravel Vapor app from my local:

==> Building Container Image
Build command: docker build --pull --file=internal.Dockerfile --tag=client-website:internal --build-arg='__VAPOR_RUNTIME=docker' .
#0 building with "desktop-linux" instance using docker driver

#1 [internal] load .dockerignore
#1 transferring context: 2B done
#1 DONE 0.0s

#2 [internal] load build definition from internal.Dockerfile
#2 transferring dockerfile: 104B done
#2 DONE 0.0s

#3 [internal] load metadata for ghcr.io/luislavena/greek-steam:8.1
#3 ERROR: no match for platform in manifest sha256:0ee93204daafcafacaf39ceee519bb96e3ccac119ae56b749af033b748158112: not found
------
 > [internal] load metadata for ghcr.io/luislavena/greek-steam:8.1:
------
internal.Dockerfile:1
--------------------
   1 | >>> FROM ghcr.io/luislavena/greek-steam:8.1
   2 |
   3 |     COPY . /var/task
--------------------
ERROR: failed to solve: ghcr.io/luislavena/greek-steam:8.1: no match for platform in manifest sha256:0ee93204daafcafacaf39ceee519bb96e3ccac119ae56b749af033b748158112: not found

In Process.php line 270:

  The command "docker build --pull --file=internal.Dockerfile --tag=client-website:internal --build-arg='__VAPOR_RUNTIME=docker' ." failed.

  Exit Code: 1(General error)

  Working directory: ~/client/client-website/.vapor/build/app

  Output:
  ================

  Error Output:
  ================
  #0 building with "desktop-linux" instance using docker driver

  #1 [internal] load .dockerignore
  #1 transferring context: 2B done
  #1 DONE 0.0s

  #2 [internal] load build definition from internal.Dockerfile
  #2 transferring dockerfile: 104B done
  #2 DONE 0.0s

  #3 [internal] load metadata for ghcr.io/luislavena/greek-steam:8.1
  #3 ERROR: no match for platform in manifest sha256:0ee93204daafcafacaf39ceee519bb96e3ccac119ae56b749af033b748158112: not found
  ------
   > [internal] load metadata for ghcr.io/luislavena/greek-steam:8.1:
  ------
  internal.Dockerfile:1
  --------------------
     1 | >>> FROM ghcr.io/luislavena/greek-steam:8.1
     2 |
     3 |     COPY . /var/task
  --------------------
  ERROR: failed to solve: ghcr.io/luislavena/greek-steam:8.1: no match for platform in manifest sha256:0ee93204daafcafacaf39ceee519bb96e3ccac119ae56b749af033b748158112: not found

Hello @antonioribeiro, the existing container images do not support arm64 platform (linux/arm64).
It should be simple to add linux/arm64 support to the same image, following what I've done with hydrofoil-php. That is, of course, if you're building on arm64 and deploying to arm64 containers.
However, If you're using an Apple Silicon machine to build and then deploy to amd64, it could be the issue. There are some notes on Vapor own blog, but the example uses a specific tag for the architecture. Their docs are a bit vague about it too, so not precisely sure how to trigger the build of amd64 instead of arm64.
Let me know if that somehow helps.
Cheers.

@luislavena, I'm using an Apple Silicon, and your clues helped, yes! As we are currently using runtime: docker switching to runtime: docker-arm and also moving to hydrofoil: FROM ghcr.io/luislavena/hydrofoil-php:8.1 fixed it.
If you could add linux/arm64 support to greek-steam, it would be great.
Thank you!

@antonioribeiro please note that hydrofoil-php is kit meant for production usage as is using the dev mode PHP configuration.
I keep this open until I push a multi arch container image.
Cheers,

I know, @luislavena , it was just to test if it would work.
Cheers!


SpectrogramUpsampler only can be used when hop_samples=256 how to make it to support more  hop_samples

thecode in this repository only support  hop_samples=256

if i try change it i will get

i try it to fix it

but i think it not a good way to fix it
could i have other way to fix it and make it support more hop_samples

The hop size is tightly coupled with the upsampler module. You'll have to make changes to the transposed convolutions whenever you change the hop size. Here's an example of how you could change the hop size to 300: https://github.com/lmnt-com/diffwave/issues/6. In general, though, you'll have to compute the right arguments for the transposed convolutions.

The hop size is tightly coupled with the upsampler module. You'll have to make changes to the transposed convolutions whenever you change the hop size. Here's an example of how you could change the hop size to 300: #6. In general, though, you'll have to compute the right arguments for the transposed convolutions.

thank i fix it
and
if i want use sample_rate=44100
which Model params
i should make it bigger than Default params？


Change build_streaming_cifar10_dataloader() to use v2 by default

Fixes 1729 to use v2 streaming dataloader by default instead of v1.

Fixes https://github.com/mosaicml/composer/pull/1729 to use v2 streaming dataloader by default instead of v1.


WIP: Updated rebase 0.17 deps

Can we keep BOOST_CHECK_EQUAL(a, b) over BOOST_CHECK(a == b), the second one do not show the 2 values when it fails.

Can we keep BOOST_CHECK_EQUAL(a, b) over BOOST_CHECK(a == b), the second one do not show the 2 values when it fails.

Yes.  BTW, this is still WIP, not expecting it'll merge soon.  It's also an alternate/experimental take on #258


search_dates doesn't support custom date formats

It would be nice to add support fot his, but I don't know how feasible it is.
Original comment: https://github.com/scrapinghub/dateparser/issues/833#issuecomment-734296359

Maybe we could move the date_formats to the settings instead of using a parameter. I didn't think this to much, but it could make sense to change this API (first adding support for both formats and later deprecating the second one).
Let me know your opinions.

This is something that would be very useful to me too. Would be willing to contribute a PR if the design could be agreed.


Plurals don't work for i18n package

Describe the bug
The i18n package is missing the CLD rule parser, so plurals don't work for many languages.
To Reproduce
Per https://github.com/OpenRefine/OpenRefine/issues/1858#issuecomment-637274292
$.i18n().locale = 'en';
$.i18n("$1 de $2 {{plural:$2|page|pages}}", 5, 10);
$.i18n().locale = 'fr';
$.i18n("$1 de $2 {{plural:$2|page|pages}}", 5, 10);

The last line gives this:
project-bundle.js:28751 Uncaught ReferenceError: pluralRuleParser is not defined
    at Object.getPluralForm (project-bundle.js:28751)
    at Object.convertPlural (project-bundle.js:28751)
    at Object.plural (project-bundle.js:28744)
    at Object.emit (project-bundle.js:28744)
    at project-bundle.js:28744
    at Function.map (project-bundle.js:504)
    at Object.emit (project-bundle.js:28744)
    at Object.parse (project-bundle.js:28739)
    at a.parse (project-bundle.js:28723)
    at Function.e.i18n (project-bundle.js:28723)

Proposed solution
Include https://github.com/santhoshtr/CLDRPluralRuleParser/blob/8baf9aedc428924fe6ee508b3d952cb5564efb3a/src/CLDRPluralRuleParser.js
(and perhaps https://github.com/santhoshtr/CLDRPluralRuleParser/blob/8baf9aedc428924fe6ee508b3d952cb5564efb3a/data/plurals.json)
(check for the appropriate version to match the version of Wikimedia i18n that we're using)
OpenRefine:

Version 3.4 beta - current master

@tfmorris: it tested the french with this example, and it still doesn't work.
so I created a simple web page with jQuery
https://raw.githubusercontent.com/antoine2711/jQuery_i18n/master/index.html, with jQuery 3.2.1, and jQuery.i18n v1.0.7. And this works fine. But, on our codebase, jQuery v1.13.1 jQuery.fn.jquery "1.11.1", French is still not working.
But, if in file jquery.i18n.language.js, If remove the "fr" definition, then, the english fallback works fine.
So, is it possible to ask dependabot to update jQuery?
Regards,
Antoine

@antoine2711 There's a long standing issue to migrate jQuery for us... but it is now a bit more involved.  Not impossible, but a bit involved.  In fact, I think probably now involves a double-migration, but I could be wrong?
1st thing would be updating the jQuery migrate plugin.

here: https://github.com/OpenRefine/OpenRefine/blob/master/main/webapp/modules/core/externals/jquery-migrate-1.2.1.js
and here: https://github.com/OpenRefine/OpenRefine/blob/master/main/webapp/modules/core/MOD-INF/controller.js

If you have approximately 40 hours to spare :-) ...
You can get started reading about migrating here:  https://jquery.com/upgrade-guide/3.0/

@antoine2711 There's a long standing issue to migrate jQuery for us... but it is now a bit more involved. Not impossible, but a bit involved. In fact, I think probably now involves a double-migration, but I could be wrong?
1st thing would be updating the jQuery migrate plugin.

here: https://github.com/OpenRefine/OpenRefine/blob/master/main/webapp/modules/core/externals/jquery-migrate-1.2.1.js
and here: https://github.com/OpenRefine/OpenRefine/blob/master/main/webapp/modules/core/MOD-INF/controller.js

If you have approximately 40 hours to spare :-) ...
You can get started reading about migrating here: https://jquery.com/upgrade-guide/3.0/

Hi @thadguidry,
Then, since I can get the same result with deleting 3 lines in a file (If in file jquery.i18n.language.js, I remove the "fr" definition, then, the english fallback works fine), this might be a far easier path! ;-)
I wonder, before asking, I search for a jQuery issue (one who would have what you just wrote) and I didn't find one. Do you think I should create one with the data you provided here?
Regards,
Antoine

I think around 2013/2014?  You'd have to poke around.  Might not even be an issue created, but was discussed, maybe mailing list?  Anyways, @ultraklon did some of that for us before.  And jQuery was captured as part of that EPIC for sure in the Project UI Improvements 2019/2020 but no tasks or issues made by me because we don't have a dedicated frontend UI person AND we haven't decided on our Roadmap completely for 4.0 what it needs to include AND if Vue.js is baby-stepped AND then what remains of jQuery in places and how to handle its migration if we need to!
In essence,  someone can volunteer lots of time to research and do that if they have the frontend skills while keeping in lock step with changes happening in our master branch. :-)  Piece of cake, right?

I think you personally would find the jQuery migration very interesting.

@thadguidry: yes, I would love it. I have a busy schedule and no free time (I'm steeling time now), but I like to code OR and contribute, so yes. In order not to generate chatter here, I'll cut short.
I will propose a PR for this issue to fix the problem of plurals in "FR", till we figure for jQuery.
Regards,
Antoine

@thadguidry: PR #2762 will fix french plurals, until jQuery is updated.
Regards,
Antoine

Reopening. @antoine2711 @thadguidry feel free to reopen issues yourselves if testing demonstrates that they're not really fixed.

There's a long standing issue to migrate jQuery for us... but it is now a bit more involved.

@thadguidry What's the issue number? The only thing close that I can find is my 2013 issue #817.

@tfmorris That issue and the Project writeup for the UI improvements: https://github.com/OpenRefine/OpenRefine/projects and https://github.com/OpenRefine/OpenRefine/projects/2 and the Google Docs project writeups for Phase 1 and 2 if you haven't seen them before.

Reopening. @antoine2711 @thadguidry feel free to reopen issues yourselves if testing demonstrates that they're not really fixed.

@tfmorris: can I get your support to merge this issue, and we can talk more about jQuery in another issue.
Regards,
Antoine

can I get your support to merge this issue, and we can talk more about jQuery in another issue.

@antoine2711 Just attempting to close out the side conversation that @thadguidry and you were having. It appears there is no existing issue, so I consider the case closed. From my point of view, things that aren't documented in an issue don't exist on the backlog.
PRs get merged. Issues get closed. The associated PR, #2774, will close this issue when it gets merged (after review of course).

PRs get merged. Issues get closed. The associated PR, #2774, will close this issue when it gets merged (after review of course).

@tfmorris: perfect. Thanks.
I've read a lot of things about i18n and such, but nothing I can document here (neither text nor links). But plurals in French and English are the same. I would consider updating jQuery OT in an PR talking about French plurals unless a link, direct ou indirect, can be provided, which nobody here did. I did a simple page with jQuery 3.2.1 and i18n v1.0.7 on my rep, and french plurals with the i18n.languages.json properly filed and everything worked. Could that translate in updating jQuery in OR to v3.x would also fix this problem? Maybe, but the cost is way beyond what I could dedicate/master.
But here, I think a small step that fixes a defined issue, document possible path to go beyond, is worth being consider a step forward.
Looking forward for the next. Regards,
Antoine

@tfmorris When translators need to deal with plurals, where will the documentation for that be located?  So can you also add to the scope of this issue to also:

[ ] Add information for users on how to use plurals into the translating docs wiki page https://github.com/OpenRefine/OpenRefine/wiki/Translate-OpenRefine

@tfmorris When translators need to deal with plurals, where will the documentation for that be located? So can you also add to the scope of this issue to also:

[ ]  Add information for users on how to use plurals into the translating docs wiki page https://github.com/OpenRefine/OpenRefine/wiki/Translate-OpenRefine

@thadguidry, @tfmorris: I've added a few paragraphs to talk about plurals, substitution, for translation. But I feel it is less than optimal, though a good start. Care to give it a look?
Regards,
Antoine

@tfmorris @antoine2711 Thank you both for collaborating on those doc improvements! Gracias! Merci!

That issue and the Project writeup for the UI improvements: https://github.com/OpenRefine/OpenRefine/projects and https://github.com/OpenRefine/OpenRefine/projects/2 and the Google Docs project writeups for Phase 1 and 2 if you haven't seen them before.

@thadguidry None of those links included any links to an issue for updating jQuery, so I created #2932. It would be super helpful if folks could create actual Github issues for identified needs (and bugs) so that tasks can be properly tracked.

@tfmorris Thanks Tom.  Yes, @wetneb @magdmartin and I talked about just that the other day on advisory committee meeting along with creating more design documents for community review on Google Docs or Hackmd.io


Express Entities can't be used in a form unless the user is an administrator.

Can't launch express form widget even if user has access to view the express entries in the dashboard.

Modify express css/js asset to work when not logged in (right now it doesn't include enough assets)
Add a new permission – search_express_entries – that defaults to Administrators in upgrade, but controls whether the user can view the express entries in the Dashboard/dialog controller.
Make controllers/dialog/express/search.php use a GET parameter named exEntityID instead of the controller method.
Use the GET parameter in the canAccess() method. Check the permissions of the results folder instead of erroring out if the user doesn't have dashboard access. The dashboard access shouldn't matter – it's the permissions of the results folder that matter. Check against the search_express_entries permission.

What's the issue?

When the form block is published, and you click on the "choose entry" field, you can see the concrete toolbar behind it, likely a style issue.
Also, I noticed that the "choose entry" button is only visible when logged in, however the label is still there. Does that have something to do with permissions?

Regarding the Choose Entry button – I'm not sure I understand. Isn't that part of the block dialog? How would you access that if you weren't logged in?

I have attached screenshots of what I'm seeing when not logged in, and logged in.
When logged in and you click the "choose entry" button, I see the modal style issue. Getting the same thing in both Firefox and Chrome.

Ah, I understand. I have updated the issue with details and moved it into the 8.1 milestone.

Leaving this to 8.1 seems to be placing a big obstacle in the way of sites exploiting express, especially as the default forms block is now express based and the old forms block is only retained for historical support.


Fix new_era() arguments mix-up.

This fixes the root cause of https://github.com/casper-network/casper-node/issues/1558.
To make the tests work reliably we should also set the standstill alert to a value lower than the minimum era duration and the auction_delay to 1, though. (See issue comment.)

Maybe it could take a switch_block_header as an argument?

Yes, I'm planning to do something like that next week.

bors merge


fix: wrap: false

Fix RM-XYZ

🧰 Changes
Fixes unwrapping the reusable content.
🧬 QA & Testing

Broken on production.
Working in this PR app.

This PR was released!
🚀 Changes included in v6.77.3


Add DELETED_MULTISIG_TRANSACTION event

Add DELETED_MULTISIG_TRANSACTION event
Closes #1805

@moisses89 I committed your suggestion, can you review again?


Changes to support installation of Chocolatey from Chocolatey.org using TLS 1.2

This was an accidental pull request and was intended for a different repository


Feature: Streamlit Interactive v1.0

Pull Request Title
Interactive streamlit application with file upload and new column based UI
Related Issue
N/A
Description
This new interactive streamlit application allows users to directly upload or drag-and-drop the PDF files using streamlit's file_uploader component. The application also includes a new UI to allow side-by-side comparisons for each of the following:

Parsed Data
Extracted Keywords
Extracted Entities
Keywords & Values
Key Topics

Type

[ ] Bug Fix
[X] Feature Enhancement
[ ] Documentation Update
[X] Code Refactoring
[ ] Other (please specify):

Proposed Changes
N/A
Screenshots / Code Snippets (if applicable)
Landing Page:

Notification while uploading a file - Also includes a spinner to show progress:

After processing:

Each component holds the grid layout to avoid overlap for easy comparison:
Only 1 expander opened:
Both expanders opened:

The Similarity Score and common words has been pushed to the bottom section outside of the grid:

The Similarity Score also changes color based on the following rules - subject to change:
# Default color to green
score_color = "green"
if similarity_score < 60:
    score_color = "red"
elif 60 <= similarity_score < 75:
    score_color = "orange"

How to Test

Execute pip install -r requirements.txt to upgrade streamlit and other dependencies
Include config.yml file if similarity score needs to be calculated
Execute streamlit run streamlit_interactive.py
Upload/Drag-and-drop the resume and job description PDF
Done

Checklist

[X] The code compiles successfully without any errors or warnings
[X] The changes have been tested and verified
[ ] The documentation has been updated (if applicable)
[X] The changes follow the project's coding guidelines and best practices
[X] The commit messages are descriptive and follow the project's guidelines
[X] All tests (if applicable) pass successfully
[ ] This pull request has been linked to the related issue (if applicable)

Additional Information

Hi there! Firstly, huge thanks for your contributions and effort! I've gone through the recent commit, and I noticed a few things that might need some adjustments:

The extracted entities graphs seem a bit stretched. I wonder if setting the layout to "wide" might enhance the visualization. You can check the screenshot .

I observed that the key topics are currently being extracted only from the job description and not from the resume. Ideally, having key topics from both sources would provide a more comprehensive analysis. Although keywords and values are accurately extracted from the resume, the same isn't happening for the JD.

One thing I noticed during my run was that the score wasn't displayed. Understanding the match score is crucial, so I'm wondering if there's a reason why it's not visible.

Your work is greatly appreciated, and I'm looking forward to your insights on these observations! 🌟

@imhalcyon I need those resume jsons for the streamlit cloud file to run the demo properly.

@srbhr , sure. I've reverted that commit. Please check now.

Hello @srbhr , is this still being tested?

Changes look really cool.


Small fixes

b29abea Fix a warning in slideflow studio that happens when a remainder is 0
4a6a8db is a temporary fix for TransMIL which would not work because it does not currently implement return_attention

Thanks @matte-esse . I removed the TransMIL fix from this as I'll want to review it separately.


[Bug]: plugin is not installing

Describe the bug
Obisidian version: 1.5.8 (Installer 1.4.16).
After clicking install in the plugin page plugin is not installed
Relevant errors (if available) from notifications or console (CTRL+SHIFT+I)
No response
Steps to reproduce
Go to community plugins, open Git plugin page, then click Install
Expected Behavior
No response
Addition context
No response
Operating system
macOS
Installation Method
Other
Plugin version
2.24.0

Sorry, it was a problem with MacOS


swiProlog: fix and document pack install

Motivation for this change
Couldn't install SWI-Prolog with extra packs
Things done

Add pack install path to swipl pack search path
Document use of local pack install

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

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

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

Result of nixpkgs-review pr 115381 at 4f96e269 run on x86_64-linux 1

5 packages built:

ape
apeClex
pakcs
swiProlog
swiPrologWithGui


Rust client functions

New features

rust: new create_cam function allowing to create a CooperativeAwarenessMessage from minimal information (fixes #131)
rust: fix MobilePerceivedObject heading computation (fixes #98)

How to test

Launch json_counter example
cargo run --example json_counter

Example runs and yields about the number of JSON messages received among the total

Received 1000 messages including 997 as JSON
Received 2000 messages including 1997 as JSON
Received 3000 messages including 2997 as JSON
...

Configure OTLP collector
Edit the example/config.ini file to set the OTLP collector endpoint config by filling the following section
[telemetry]
host="otlp.domain.ext"
port=4318
; Optionnal, defaults to "v1/traces"
path="custom/v1/traces"

Launch telemetry example
cargo run --example telemetry --features telemetry

Example runs and sends 4 traces
Transport: standard MQTT; TLS disabled
INFO [telemetry] logger ready on log
INFO [telemetry] Send a trace with a single span 'ping' root span
INFO [telemetry] └─ Ping                  trace_id: 4d9183d7274f4b8c850d46887f35141a, span_id: bd458664e66f860e
DEBUG [reqwest::connect] starting new connection: http://<IP_ADDRESS>:18000/
INFO [telemetry] Send a trace with a single span 'pong' root span linked with the previous one 'ping'
INFO [telemetry] └─ Pong                  trace_id: 8479671f21bf9b0fd166b8ead1ff2761, span_id: 3c153c5e70a8a2a2
INFO [telemetry] Send a single trace with two spans
INFO [telemetry] └─ Root                  trace_id: cd4a1ee42952fcafc5eaf61f1881eca2, span_id: 7580f10ca1595e5b
INFO [telemetry]    └─ Child              trace_id: cd4a1ee42952fcafc5eaf61f1881eca2, span_id: d570aff4e9889e95
INFO [telemetry] Send a trace with 3 spans from 3 threads
INFO [telemetry] └─ Main thread           trace_id: 6b1fe1d4b7aa574bbbe4b987053bcfd2, span_id: e5050064d17d0527
INFO [telemetry]    ├─ Sender thread      trace_id: 6b1fe1d4b7aa574bbbe4b987053bcfd2, span_id: 9f449076f02efdd6
INFO [telemetry]    └─ Listener thread    trace_id: 6b1fe1d4b7aa574bbbe4b987053bcfd2, span_id: d1bb7d93ec83207e

Prepare a test script
cat <<EOF > /tmp/test_copycat.sh
#! /usr/bin/bash
mosquitto_pub -h test.mosquitto.org -p 1884 -u rw -P readwrite -t default/outQueue/v2x/cam/ora_car_testcon2/2/2/2/2/2/2/2/2/2/2/2/2/2/2/2/2/2/2/2 -m '{"type":"cam","origin":"self","version":"1.2.0","source_uuid":"ora_car_2222","timestamp":1618591358923,   "message":{"protocol_version":2,"station_id":1077952580,"generation_delta_time":31571,"basic_container":{"station_type":5,   "reference_position":{"latitude":486230934,"longitude":22419064,"altitude":10000},"confidence":{"position_confidence_ellipse":   {"semi_major_confidence":0,"semi_minor_confidence":0,"semi_major_orientation":0},"altitude":1}},"high_frequency_container":   {"heading":2375,"speed":137,"drive_direction":0,"vehicle_length":47,"vehicle_width":24,"longitudinal_acceleration":1,   "lateral_acceleration":0,"vertical_acceleration":0,"yaw_rate":-27,"lane_position":0,"curvature":0,"confidence":{"heading":2,   "speed":3,"vehicle_length":1,"vehicle_width":1,"longitudinal_acceleration":5,"yaw_rate":6,"lane_position":1,"curvature":7}},   "low_frequency_container":{"vehicle_role":0,"exterior_lights":"00000000","path_history":[{"path_position":{},   "path_delta_time":1}]}}}'
sleep 0.2
mosquitto_pub -h test.mosquitto.org -p 1884 -u rw -P readwrite -t default/outQueue/v2x/cam/ora_car_testcon2/2/2/2/2/2/2/2/2/2/2/2/2/2/2/2/2/2/2/2 -m '{"type":"cam","origin":"self","version":"1.2.0","source_uuid":"ora_car_2222","timestamp":1618591358923,   "message":{"protocol_version":2,"station_id":1077952580,"generation_delta_time":31571,"basic_container":{"station_type":5,   "reference_position":{"latitude":486230934,"longitude":22419064,"altitude":10000},"confidence":{"position_confidence_ellipse":   {"semi_major_confidence":0,"semi_minor_confidence":0,"semi_major_orientation":0},"altitude":1}},"high_frequency_container":   {"heading":2375,"speed":137,"drive_direction":0,"vehicle_length":47,"vehicle_width":24,"longitudinal_acceleration":1,   "lateral_acceleration":0,"vertical_acceleration":0,"yaw_rate":-27,"lane_position":0,"curvature":0,"confidence":{"heading":2,   "speed":3,"vehicle_length":1,"vehicle_width":1,"longitudinal_acceleration":5,"yaw_rate":6,"lane_position":1,"curvature":7}},   "low_frequency_container":{"vehicle_role":0,"exterior_lights":"00000000","path_history":[{"path_position":{},   "path_delta_time":1}]}}}'
sleep 0.2
mosquitto_pub -h test.mosquitto.org -p 1884 -u rw -P readwrite -t default/outQueue/v2x/cam/ora_car_testcon2/2/2/2/2/2/2/2/2/2/2/2/2/2/2/2/2/2/2/2 -m '{"type":"cam","origin":"self","version":"1.2.0","source_uuid":"ora_car_2222","timestamp":1618591358923,   "message":{"protocol_version":2,"station_id":1077952580,"generation_delta_time":31571,"basic_container":{"station_type":5,   "reference_position":{"latitude":486230934,"longitude":22419064,"altitude":10000},"confidence":{"position_confidence_ellipse":   {"semi_major_confidence":0,"semi_minor_confidence":0,"semi_major_orientation":0},"altitude":1}},"high_frequency_container":   {"heading":2375,"speed":137,"drive_direction":0,"vehicle_length":47,"vehicle_width":24,"longitudinal_acceleration":1,   "lateral_acceleration":0,"vertical_acceleration":0,"yaw_rate":-27,"lane_position":0,"curvature":0,"confidence":{"heading":2,   "speed":3,"vehicle_length":1,"vehicle_width":1,"longitudinal_acceleration":5,"yaw_rate":6,"lane_position":1,"curvature":7}},   "low_frequency_container":{"vehicle_role":0,"exterior_lights":"00000000","path_history":[{"path_position":{},   "path_delta_time":1}]}}}'
sleep 0.2
mosquitto_pub -h test.mosquitto.org -p 1884 -u rw -P readwrite -t default/outQueue/v2x/cam/ora_car_testcon2/2/2/2/2/2/2/2/2/2/2/2/2/2/2/2/2/2/2/2 -m '{"type":"cam","origin":"self","version":"1.2.0","source_uuid":"ora_car_2222","timestamp":1618591358923,   "message":{"protocol_version":2,"station_id":1077952580,"generation_delta_time":31571,"basic_container":{"station_type":5,   "reference_position":{"latitude":486230934,"longitude":22419064,"altitude":10000},"confidence":{"position_confidence_ellipse":   {"semi_major_confidence":0,"semi_minor_confidence":0,"semi_major_orientation":0},"altitude":1}},"high_frequency_container":   {"heading":2375,"speed":137,"drive_direction":0,"vehicle_length":47,"vehicle_width":24,"longitudinal_acceleration":1,   "lateral_acceleration":0,"vertical_acceleration":0,"yaw_rate":-27,"lane_position":0,"curvature":0,"confidence":{"heading":2,   "speed":3,"vehicle_length":1,"vehicle_width":1,"longitudinal_acceleration":5,"yaw_rate":6,"lane_position":1,"curvature":7}},   "low_frequency_container":{"vehicle_role":0,"exterior_lights":"00000000","path_history":[{"path_position":{},   "path_delta_time":1}]}}}'
sleep 3
mosquitto_pub -h test.mosquitto.org -p 1884 -u rw -P readwrite -t default/outQueue/v2x/cam/ora_car_testcon2/2/2/2/2/2/2/2/2/2/2/2/2/2/2/2/2/2/2/2 -m '{"type":"cam","origin":"self","version":"1.2.0","source_uuid":"ora_car_2222","timestamp":1618591358923,   "message":{"protocol_version":2,"station_id":1077952580,"generation_delta_time":31571,"basic_container":{"station_type":5,   "reference_position":{"latitude":486230934,"longitude":22419064,"altitude":10000},"confidence":{"position_confidence_ellipse":   {"semi_major_confidence":0,"semi_minor_confidence":0,"semi_major_orientation":0},"altitude":1}},"high_frequency_container":   {"heading":2375,"speed":137,"drive_direction":0,"vehicle_length":47,"vehicle_width":24,"longitudinal_acceleration":1,   "lateral_acceleration":0,"vertical_acceleration":0,"yaw_rate":-27,"lane_position":0,"curvature":0,"confidence":{"heading":2,   "speed":3,"vehicle_length":1,"vehicle_width":1,"longitudinal_acceleration":5,"yaw_rate":6,"lane_position":1,"curvature":7}},   "low_frequency_container":{"vehicle_role":0,"exterior_lights":"00000000","path_history":[{"path_position":{},   "path_delta_time":1}]}}}'
EOF

Launch copycat example
cargo run --example copycat --features geo_routing

=> The example correctly runs

Launch the script
chmod +x /tmp/test_copycat.sh && /tmp/test_copycat.sh

=> Several reception must be logged

DEBUG [copycat] item received: Packet { topic: GeoTopic { prefix: "default", queue: Out, suffix: "v2x", message_type: CAM, uuid: "ora_car_testcon2", geo_extension: Quadkey { tiles: [Two, Two, Two, Two, Two, Two, Two, Two, Two, Two, Two, Two, Two, Two, Two, Two, Two, Two, Two] } }, payload: Exchange { type_field: "cam", origin: "self", version: "1.2.0", source_uuid: "ora_car_2222", timestamp:<PHONE_NUMBER>923, path: [], message: CAM(CooperativeAwarenessMessage { protocol_version: 2, station_id:<PHONE_NUMBER>, generation_delta_time: 31571, basic_container: BasicContainer { station_type: Some(5), reference_position: ReferencePosition { latitude: 486230934, longitude: 22419064, altitude: 10000 }, confidence: Some(PositionConfidence { position_confidence_ellipse: Some(PositionConfidenceEllipse { semi_major_confidence: Some(0), semi_minor_confidence: Some(0), semi_major_orientation: Some(0) }), altitude: Some(1) }) }, high_frequency_container: HighFrequencyContainer { heading: Some(2375), speed: Some(137), drive_direction: Some(0), vehicle_length: Some(47), vehicle_width: Some(24), curvature: Some(0), curvature_calculation_mode: None, longitudinal_acceleration: Some(1), yaw_rate: Some(-27), acceleration_control: None, lane_position: Some(0), lateral_acceleration: Some(0), vertical_acceleration: Some(0), confidence: Some(HighFrequencyConfidence { heading: Some(2), speed: Some(3), vehicle_length: Some(1), yaw_rate: Some(6), longitudinal_acceleration: Some(5), curvature: Some(7), lateral_acceleration: None, vertical_acceleration: None }) }, low_frequency_container: Some(LowFrequencyContainer { vehicle_role: Some(0), exterior_lights: "00000000", path_history: [PathHistory { path_position: PathPosition { delta_latitude: None, delta_longitude: None, delta_altitude: None }, path_delta_time: Some(1) }] }) }) }, properties: PublishProperties { payload_format_indicator: None, message_expiry_interval: None, topic_alias: None, response_topic: None, correlation_data: None, user_properties: [], subscription_identifiers: [], content_type: None } }

=> One message publication must be logged

DEBUG [libits::client::application::pipeline] Packet to publish...
INFO [libits::client::application::pipeline] Cannot trace exchange, missing gateway component name in node configuration
DEBUG [libits::client::application::pipeline] Packet published!
DEBUG [rumqttc::v5::state] Publish. Topic = default/inQueue/v2x/cam/com_orange_its-client_10000/2/2/2/2/2/2/2/2/2/2/2/2/2/  2/2/2/2/2/2, Pkid = 2, Payload Size = 962

Test 6 KO:
$ cargo run --example copycat --features geo_routing
   Compiling libits-client v2.0.0 (/home/nyma7486/dev/work/5GCroCo/its-client/gh-209/rust)
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 4.34s
     Running `target/debug/examples/copycat`
Transport: standard MQTT; TLS enabled
INFO [copycat] logger ready on log
INFO [libits::client::application::pipeline] Analysis thread count set to: 4
Log is written to log/copycat_rCURRENT.log
INFO [libits::client::application::pipeline] mqtt client subscribing starting...
INFO [libits::client::application::pipeline] mqtt client subscribing finished
INFO [libits::client::application::pipeline] Starting MQTT listening thread...
INFO [libits::client::application::pipeline] MQTT listening thread started!
INFO [libits::client::application::pipeline] starting mqtt router dispatching...
INFO [libits::client::application::pipeline] mqtt router dispatching started
INFO [libits::client::application::pipeline] starting monitor reception thread...
INFO [libits::client::application::pipeline] monitor reception thread started
INFO [libits::transport::mqtt::mqtt_client] listening started
INFO [libits::transport::mqtt::mqtt_router] Registered route for topic: default/outQueue/v2x/cam
INFO [libits::client::application::pipeline] starting filtering...
INFO [libits::client::application::pipeline] starting analyser generation...
INFO [libits::client::application::pipeline] starting analyser generation...
INFO [libits::client::application::pipeline] starting analyser generation...
INFO [libits::client::application::pipeline] starting analyser generation...
INFO [libits::client::application::pipeline] filter started
INFO [libits::client::application::pipeline] Starting configuration reader thread...
INFO [libits::transport::mqtt::mqtt_router] Registered route for topic: default/outQueue/v2x/cpm
INFO [libits::transport::mqtt::mqtt_router] Registered route for topic: default/outQueue/v2x/denm
INFO [libits::transport::mqtt::mqtt_router] Registered route for topic: default/outQueue/v2x/cam
INFO [libits::transport::mqtt::mqtt_router] Registered route for topic: default/outQueue/info
INFO [libits::client::application::pipeline] Configuration reader thread started!
INFO [libits::client::application::pipeline] starting monitor reception thread...
INFO [libits::client::application::pipeline] monitor reception thread started
INFO [libits::client::application::pipeline] Starting MQTT publishing thread...
INFO [libits::client::application::pipeline] Cannot trace exchange, missing gateway component name in node configuration
INFO [copycat] we start to schedule<PHONE_NUMBER> from ora_car_2222
INFO [libits::client::application::pipeline] Cannot trace exchange, missing gateway component name in node configuration
INFO [copycat] we start to schedule<PHONE_NUMBER> from ora_car_2222
INFO [libits::client::application::pipeline] Cannot trace exchange, missing gateway component name in node configuration
INFO [copycat] we start to schedule<PHONE_NUMBER> from ora_car_2222
INFO [libits::client::application::pipeline] Cannot trace exchange, missing gateway component name in node configuration
INFO [copycat] we start to schedule<PHONE_NUMBER> from ora_car_2222
INFO [libits::client::application::pipeline] Cannot trace exchange, missing gateway component name in node configuration
INFO [copycat] we start to schedule<PHONE_NUMBER> from ora_car_2222
INFO [copycat] we treat the scheduled item 1<PHONE_NUMBER> from ora_car_2222
INFO [libits::client::application::pipeline] Cannot trace exchange, missing gateway component name in node configuration

Logs seems fine but only missing the debug lines, I must have the log level environment variable set to debug by default on my side
Please check using : RUST_LOG=debug cargo run --example copycat --features geo_routing


Pagination control keywords per_page= and page= are missing from many client list() and list_*() methods

All client list() and list_*() methods need to support pagination. The default per_page=20 clips many large lists without warning.
For example client.ssh_keys.list(per_page=50, page=1) is supported but client.domains.list(per_page=50, page=1) and  client.domains.list_records(domain_name='my.domain', per_page=50, page=1) are not.

Hi there,
Thank you so much for bringing this to our attention. Our domains and domain records API endpoints definitely support pagination and that should have been reflected in Pydo. We believe we've found the bug in Pydo that has caused this and have created a ticket to fix it. We have prioritized the ticket in our backlog to get to it sooner rather than later. We will close this issue once it is resolved.

We've merged the fix and cut a new release, pydo 0.1.4. Thank you again for bringing this to our attention and please don't hesitate to reach back out for anything else.


Rust docs: carnix command broken

Running carnix -o hello.nix --src ./. Cargo.lock --standalone as described in rust.section.md yields
error: Found argument '-o' which wasn't expected, or isn't valid in this context

Environment: carnix version 0.9.8 (nixpkgs-unstable.carnix).
cc @P-E-Meunier

It's not broken, it just changed syntax, as indicated by carnix --help.

I did update the manual at some point on my machine, but an unfortunate git rebase got rid of my changes, sorry about that.

The issue hasn't been fixed yet, I think this should be reopened.

This is not a nixpkgs issue, as @P-E-Meunier elaborated. If you don't like that carnix changed the syntax you should file an issue for carnix

The outdated command is from the nixpkgs docs (rust.section.md), so that makes it a nixpkgs issue.

Oh I didn't see you mention that, sorry!

@P-E-Meunier don't suppose you've found some time to update those docs yet?

While the issue primarily about rust.section.md, and carnix seems to be a stumbling block for many I'll add unopinionated recomenation to use crate2nix instead of carnix.

Carnix hasn't been updated in over a year, and the pijul nest repository linked in https://crates.io/crates/carnix is not available anymore.

@P-E-Meunier are you still maintaining carnix? Have you switched to use something else instead?

carnix has been archived so it should be removed from the manual
the most popular ones for out of nixpkgs usage are naersk and cargo2nix while rustPlatform.buildRustPackage is used in nixpkgs
https://nixos.org/manual/nixpkgs/unstable/#compiling-rust-crates-using-nix-instead-of-cargo

I am working on a pr to remove carnix completely, but I'm not sure who should be the replacement
Some possible candidates I found:

crate2nix - this is the one I'm leaning towards, already packaged in nixpkgs and seems to integrate with buildRustCrate
cargo2nix - looks similar to crate2nix, not sure how they compare
naersk - no code generation, seems to be very popular
crane - looks similar to naersk, seems to have grown in popularity recently

I am working on a pr to remove carnix completely, but I'm not sure who should be the replacement
Some possible candidates I found:

crate2nix - this is the one I'm leaning towards, already packaged in nixpkgs and seems to integrate with buildRustCrate
cargo2nix - looks similar to crate2nix, not sure how they compare
naersk - no code generation, seems to be very popular
crane - looks similar to naersk, seems to have grown in popularity recently

I'm using naersk in all my rust projects and have had no issues with it, I especially like that it doesn't generate any files
For outside of nixpkgs usage we should point to naersk while for in nixpkgs usage we should just keep using cargoSha256
IMHO

So do you think we should just remove this section?
compiling rust crates using nix instead of cargo


⚠ Bofrost.at has degraded performance

In 1f76f9f, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1663 ms

Resolved: Bofrost.at performance has improved in 465980c.


Where does GraphQL fit in clean code architecture?

Hi,
I have only recently started to look at GraphQL. Coming across  to this repository also recently, I'm wondering where does GraphQL fit in this context.
From my understanding, GraphQL solves the problem of having too many API endpoints by providing a more flexible querying system:

By using GraphQL, where does it fit?

is it just another way of writing the application layer? Instead of writing commands and queries, you define the application layer with queries and resolvers etc...
OR, should it exists as a layer between WebUI and Application layer?
OR, between the Application layer and Persistence layer?

Can GraphQL reduce the amount of code written in the Application layer? Or reduce the maintenance required in the future? Could it make it better the application layer better?
However by doing this, you probably will need to dependent on a library to map GraphQL queries to EF core, which it does exists. Does it breaks clean code architecture?

Let me know if this is not the right place to ask questions here. Cheers!
Simon
I'm a young software developer who haven't finished reading the Clean Architecture. Love the content here. It answers many questions that I've had over in previous projects. So thank you :)

Apologies if this isn't considered construcive, but I would like to echo feedback regarding where GraphQL would best fit with this type of (clean) architecture.

Hi @simont789 - thanks for the question. Apologies, however I've not had the opportunity to explore this in detail at this stage. It's not on my radar right now, but I may explore it in the future.
Sorry I couldn't be of help. Good luck with your research. 😄


Support bridged token transfers from any chain

At the moment the API does not allow the user to set a global consensus systems as destination of the transfers (in order to perform a transfer of assets to a different ecosystem via the Bridge Hub).
To support this feature, the input params of the API will need to be adapted to a string beyond just the paraID as it is currently. Potentially, the destination address format/typing may need to be expanded too.
In terms of directions, it may make sense to introduce two (or three) new directions:

systemToBridge (should be covered by the new transferAssets call of pallet XCM.
paraToBridge (currently not supported by paras runtime).
RelayToBridge (to transfer the native DOT/KSM to a different eco).

Related issue: https://github.com/paritytech/asset-transfer-api/issues/371

As commented recently the paraToBridge direction should be already supported in certain parachains on mainnet (f.e., moonbeam, mythos, astar and byfrost) since the call transfer_assets_using_type_and_then has been already enabled in their runtimes, and assuming execution fees on Asset Hub step are paid in an asset qith a liquidity pool with DOT (f.e. USDC/T)


numpy.datetime64 not accepted as date

I get TypeError: Expected 'date' to be type: [str, datetime.date, datetime.datetime]. Got: <class 'numpy.datetime64'>.
My data type: datetime64[ns]

Hi, thanks for the heads up! This should be a quick fix, will take care of it in the next release. Keeping you posted!
In the meantime, using np.datetime_as_string(your_timestamp, unit='D') should do the trick mapping your data type to a data type (str) that is accepted by the current release.


Can anyone edit the Wiki to add their Koa middleware?

I published https://www.npmjs.com/package/koa-server-push yesterday but usually there is a process getting it on a list like that, so just looking for a green light to add it to the list.

yep!


Remove unnecessary import in README

Hey,
the import of the aws-lambda-go is
a) Broken. Because it's missing a /lambda at the end
and
b) Unnecessary for the example and go build will complain.
So I removed it ;) This also 'fixes' the problem in  #22
Best regards,
Felix

thanks!


fix(challenges): Regex Asterisk Challenge

[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] None of my changes are plagiarized from another source without proper attribution.
[x] All the files I changed are in the same world language (for example: only English changes, or only Chinese changes, etc.)
[x] My changes do not use shortened URLs or affiliate links.

Fixes description and adds several tests to close a long standing issue with this challenge's description.
Closes #17872

@scissorsneedfoodtoo I'd appreciate if you could also remove the testString from the testString and only let the assert be there. Due to new changes, only the text string would be used everywhere now with reserved exceptions

@thecodingaviator, thanks, I didn't realize that. So with the recent changes the tests should be:
  - text: Your regex should not match "aaaa".
    testString: assert(!chewieRegex.test('aaaa'));

Is that right?

@scissorsneedfoodtoo IMO that is right, but since I have never tried it, @RandellDawson would be a better person to consult that with

@scissorsneedfoodtoo , @thecodingaviator This is not something we should require users to do on a PR, but it is now an option we can implement.  If we expect this, I believe it should be in the How to Work on Guide Challenges documentation and then only apply to PRs after that policy is implemented.
In general, we should not hold up PRs for extra stuff which goes beyond the original scope of the PR or issue the PR attempts to close.  If other fixes are needed beyond that scope, I believe they should be put on a new issue, so a discussion can take place and a separate PR created to address concerns.
I see many good PRs held up from a merge, because we find other issues beyond the original scope.  Many times these PRs go stale, which seems unnecessary IMHO.
FYI - Removing the message argument from the assert only applies when there is a single assert in a testString per text.  There are some challenges which use throw and may only have one text, but multiple asserts.

@RandellDawson, thanks for clearing that up. Makes sense and I'll keep it in mind going forward.
@thecodingaviator, I don't mind removing the message arguments here, even if if it's a bit outside the scope of this PR. I tested it yesterday and it seemed to work fine.

@thecodingaviator, Sorry for the delay! I removed the unnecessary string arguments from testString. Could you take another look when you can?

@scissorsneedfoodtoo See this, it passes:

But just by changing the top line, it fails the same RegEx, we should be checking for the regex but without using the chewieQuote:

@scissorsneedfoodtoo Working with @thecodingaviator, we came up with the following verbiage for both the Instructions and the actual tests.  We believe this should resolve the original issue and make the instructions clearer.
Instructions

For this challenge, chewieQuote has been initialzied as "Aaaaaaaaaaaaaaaarrrgh!" behind the scenes. Create a regex chewieRegex that uses the * character to match an uppercase "A" character immediately followed by zero or more lowercase "a" characters in chewieQuote. Your regex does not need flags or character classes, and it should not match any of the quotes.

Tests
tests:
  - text: Your regex chewieRegex should use the * character to match zero or more a characters.
    testString: assert(/\*/.test(chewieRegex.source));
  - text: Your regex should match "A" in chewieQuote.
    testString: assert(result[0][0] === 'A');
  - text: Your regex should match only "aaaa" when immediately preceeded by "A" in chewieQuote.
    testString: assert(result[0].slice(1, 5) === 'aaaa');
  - text: Your regex should match "Aaaaaaaaaaaaaaaa" in chewieQuote.
    testString: assert(result[0] === 'Aaaaaaaaaaaaaaaa');
  - text: Your regex chewieRegex should match 16 characters in chewieQuote.
    testString: assert(result[0].length === 16);
  - text: Your regex should not match any characters in "He made a fair move. Screaming about it can't help you."
    testString: assert(!"He made a fair move. Screaming about it can't help you.".match(chewieRegex));
  - text: Your regex should not match any characters in "Let him have it. It's not wise to upset a Wookiee."
    testString: assert(!"Let him have it. It's not wise to upset a Wookiee.".match(chewieRegex));

Please let us know if you think these changes would work.

@RandellDawson and @thecodingaviator, just tested these changes and everything LGTM. Thank you both for all your help with this! The new wording for the instructions and tests read very well, and moving the chewieQuote variable to the before test section to prevent accidental changes was a great idea.
Please go ahead an commit them when you get a chance

@scissorsneedfoodtoo After looking at my suggestion a bit more, we decided it no longer made sense to have the following test, so I removed it.
  - text: Your regex should match only "aaaa" when immediately preceeded by "A" in chewieQuote.
    testString: assert(result[0].slice(1, 5) === 'aaaa');

@RandellDawson, that sounds good. Seems redundant with all the other tests.

Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 📝

Thank you for the merge, and for all of your help with this @thecodingaviator and @RandellDawson!


Update model_instructions.md

add extra statement that may generalise the prompt ability

In fact, this instruction, as I tested on other system, should be unique on Claude, which already know its name. And if you want to use it on other models, just change the name to whatever you like.😉

That's Ok.But I think it would be trivial to change accordingly


Refactoring

I am not sure if I will have the time, but still, somebody might if I can't, so...
How can we enable all the refactorings for VS Code?
I mean in terms of calling Phpactor (I can research the corresponding code for VS Code). I noticed some of them are available on the command line while others seem to be more tricky to invoke and are available only in VIM.
Considering how few tools do refactoring for PHP (I found only this one), even slow implementation should be better than nothing.

This is more a question of enabling them for the language server, and probably better raised in https://github.com/phpactor/phpactor where other people can see it.
In general this is mostly just a question of effort, but it is ultimately the goal to have all the refactorings available from the language server.

Currently you should have a few code actions (import missing classes, add missing properties, complete constructor etc)

Feel free to move this issue. Or should I create another one?
If it is about changing the language server I am probably out of my depth there.

Currently you should have a few code actions (import missing classes, add missing properties, complete constructor etc)

Yes, I saw one of them - the Import. Not sure how to test the others.


[Monitoring V2] Broken links via proxy due to ExternalURL / RootURL defaults

Note: leaving this as a rancher/rancher issues until it has been identified whether any backend changes are required. If none are required, I'll move this over to rancher/dashboard.
Issue
When utilizing links that are generated via kube-proxy such as in https://github.com/rancher/dashboard/issues/1064 in Monitoring V2, there are issues with rendering particular pages on the Prometheus, Grafana, and AlertManager UIs since they each require users to have set the External URL / Root URL fields on deploying the Helm chart in order to successfully be able to show the page. As of yet, this issue has been found to cause issues in rendering the following pages:

Prometheus: /graph endpoint requires the ExternalURL to be set correctly in order to make /query requests
Grafana: most links are broken since the Root URL needs to be set for Grafana and the External URL that is placed into the Prometheus datasource URL is incorrect
AlertManager: no known issues, but it's possible some advanced configuration may encounter these issues.

The solution for this is to set the following fields on deployment:
# Sets https://github.com/helm/charts/blob/506eedd8f3d58e73fd3f7b3fecfec38f9f45aedb/stable/prometheus-operator/templates/prometheus/prometheus.yaml#L55-L61
prometheus:
  prometheusSpec:
    externalURL: <url>

# Sets https://github.com/helm/charts/blob/76982a553754904036b661d4b3c6bbb829c35886/stable/prometheus-operator/templates/alertmanager/alertmanager.yaml#L21-L27
alertmanager:
  alertmanagerSpec:
    externalURL: <url>

grafana:
  grafana.ini:
    server:
      root_url: <url>

However, there are three possible cases for what this URL should be:

Using Rancher: <rancher-url>/k8s/clusters/<cluster-id>/api/v1/namespaces/cattle-monitoring-system/services/http:<service-info>/proxy
Using kubectl proxy: http://localhost:8001/api/v1/namespaces/cattle-monitoring-system/services/http:<service-info>/proxy
Using an Ingress: Needs to be configured by the user; for AlertManager and Prometheus, an Ingress that is configured through the deployment automatically updates the external URL values, but for Grafana this value is not automatically configured.

where <service-info> would be rancher-monitoring-grafana:80, rancher-monitoring-prometheus:9090, or rancher-monitoring-alertmanager:9093.
What should the expectation be with the default values for the Helm chart on deployment?
Proposed Solution
Don't change the Helm chart defaults. If a user is deploying Rancher Monitoring via the dashboard, we'll have the Magic URL above auto-filled out under:

the existing External URL field for the Prometheus - Network Advanced Configuration
a newly exposed External URL field for the Grafana - Network Advanced Configuration which will be tied to grafana.grafana.ini.server.root_url
a newly exposed External URL field for the AlertManager - Network Advanced Configuration which will be tied to alertmanager.alertmanagerSpec.externalURL

As a result, if a user deploys the Rancher Monitoring chart via Dashboard, the expectation would be that the user will not also be using kubectl proxy to directly access these components without modifying these external URL values.
If a user deploys the Rancher Monitoring chart via the Helm chart, however, they will be responsible for making sure this value is updated, which can be mentioned in the Rancher Monitoring documentation. This may or may not involve updating the values for kubeproxy to be usable, although using something like kubectl port-forward seems to have been working as expected either way.
If the user uses an Ingress, they will know to modify these values since they are in the same section where an Ingress would likely be configured on the deployment.

Summary of Design Discussion
Instead of expecting the UI to maintain the custom logic for filling in each of these external URL / root URL fields, UI will instead expose fields (described in https://github.com/rancher/rancher/issues/28495) in order to allow the charts to construct the External / Root URLs necessary here (i.e. the Cluster ID and the Rancher URL used).
The backend changes in order to support these fields that should be exposed by the UI are located in https://github.com/rancher/charts/pull/582.

Prioritizing the fix for https://github.com/rancher/rancher/issues/29068 separately from this PR; once this fix is in, every path in Prometheus, Grafana, and Alertmanager should work as expected except for the Try experimental React UI link on the Prometheus /graph endpoint.

install the monitoring v2 into a downstream cluster in rancher:master-head 67e24f2 docker install setup
confirm that all links for monitoring works.


security: fix CVE-2022-30630

This is a PRIVATE issue tracked in b/231318890 and fixed by http://tg/1422952.
This is for 1.17.12 and 1.18.4.

@gopherbot please open backport issues for this security fix


Removed empty array, since webpack 2 doesn't support them anymore.

Issue: Couldn't start RN storybook with Production environment.
What I did
Removed empty array, since that was breaking webpack.
How to test
https://github.com/wix/storybook-server - Try to run npm run start.

Looks clean, is this breaking in any way?


Generate correct URIs

Encode the URIs for subject and templates correctly (e.g., example.org/NEW YORK --> example.org/NEW YORK)
Have a parameter in the config like:
uri.encode=(" "->"%20"),,(","->""),,("á"->"a"),,("é"->"e"),,("í"->"i"),,("ó"->"o"),,("ú"->"u"),,("ü"->"u"),,("ñ"->"n"),,("\u00B4"->"%C2%B4")

Morph-RDB has it.

quote() generates URIs correctly and its overhead is very little. I close the issue.

quote() generates URIs correctly and its overhead is very little. I close the issue.


query log not rotated automatically - file locked by SimpleDNSCrypt process

The query log is not rotated automatically as long as the Gui is running.
Closing the Gui and restarting the dns-crypt proxy service solves this issue.

@scubasunny since this is a "live log" and entries are to be displayed immediately, the file must remain open.
For example, if FileSystemWatcher is used, the entries are displayed with a delay.
Simple DNSCrypt does not have to be started to use dnscrypt-proxy.


add archive column

S1 ./refine build
S2 ./refine test
S3 ./refine
S4. upload a compressed file and verify the archive file name is added as column

@wetneb  just updated the pull request added several tests.
Following is the screen when running with the pull request

Can you take a look when you have time?

Does this address an open issue? Can you link it please?

This is a breaking change to a public extension API. We don't make many promises to extension writers, but the Importer API is one of the few.
The fact that this requires changes to every single one of our importers is a clear sign that something is afoot. All those importers that we don't control will break and be incompatible with the next release.
We need to figure out a different way to do this which preserves the compatibility of the public API.


dont munge logging for simulate queue

Don't set rails to debug when simulating the queue.
The user often wants to be in debug mode
But that will have already been set for other means.

I (rarely) need to turn off sql logging in my environment when running the queue.
And I can do this as a one off.
But I wouldn't expect running the queue to modify my logging preferences.
And most developers have their desired logging configured before calling this
method
I can appreciate closing or merging.

👍 Makes sense to me

LGTM

This was put into place originally because we don't have a separation of logging for development.log and rails console.  Many people in the UI team want "info" for development.log, but when simulating they want "debug".  I agree that it should not be set here though...I have partial code to separate out console log levels, so perhaps I'll just push that along now :)

@Fryguy I thought there was some reason hidden in there


Consider using the intake library

It could be interesting to replace our home grown esmvaltool/_data_finder.py module by the much more advanced intake library and the associated intake-iris plugin.

I started sniffing around intake - easy to install via conda and looks easy to use (I ran the little exaple here [https://buildmedia.readthedocs.org/media/pdf/intake/latest/intake.pdf][docs] but it looks to me this something accountants or auditors would rather use than us...maybe I'll find something cooler the more I look at it


React v0.14 compatibility

start from React v0.14, react split into two packages, react and
react-dom.
ref: https://facebook.github.io/react/blog/2015/07/03/react-v0.14-beta-1.html#two-packages

As I mentioned in in this comment, the ngReact.min.js file needs to be generated. There are also deprecation warnings appearing during the test run due to the usage of React.unmountComponentAtNode in both test files. Is this something that should be addressed now since we're here?

@kasperp Now that react 0.14 stable has been released should we get something merged to master?

Yes we should is there anything besides bumping the React version that prevents that ? You had a couple of comments that I guess needs to be addressed.

@kasperp Addressed them in #109

close via #109