[Feature Request]:  Add Comment and Like Buttons to Blog Section

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
I would like to request the addition of comment and like buttons in the blog section of our application. This will allow users to engage with the content more effectively by leaving comments and showing appreciation through likes.
Use Case
Adding comment and like buttons would create a more interactive experience for users. For instance, users can express their thoughts about a specific blog post and interact with other users, fostering a community around the blog.
Benefits

User Engagement: Users will feel more connected to the content, leading to increased engagement and return visits.
Feedback Loop: Comments can provide valuable feedback to content creators regarding what users enjoy or want to see more of.
Community Building: Encouraging discussions in the comments can build a community around the blog, enhancing user retention.

Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC-EXT contributor
[X] I'm a HACKTOBERFEST contributor
[X] I have starred the repository

Please assign the task to me!

@SCR01 I would like to work on the issue. Kindly assign it to me.


min, max, largest, smallest

I finally managed to use my beloved heap to do something useful. This function takes:

a number
a comparator (like the one used for sort)
an iterable
and returns an iterable that returns the n biggest (or smallest, depending on the comparator) items of the sequence.
So, if you have a an unsorted sequence of number from 0 to 99 and you call:

largest(3, unsorted) // you get [97, 98, 99]
largest(3, (a, b) => b - a, unsorted) // you get [2, 1, 0]

Here's the implementation:
import ensureIterable from './internal/ensure-iterable'
import Heap from 'little-ds-toolkit/lib/heap'

function * largest (number, comp, iterable) {
  const heap = new Heap(comp)
  for (const item of ensureIterable(iterable)) {
    heap.push(item)
    if (heap.size() > number) {
      heap.pop()
    }
  }
  const len = heap.size()
  for (var i = 0; i < len; i++) {
    yield heap.pop()
  }
}

export default function curriedLargest (number, comp, iterable) {
  if (arguments.length === 3) {
    return largest(number, comp, iterable)
  } else if (arguments.length === 2) {
    if (Symbol.iterator in comp) {
      iterable = comp
      comp = undefined
      return largest(number, comp, iterable)
    } else {
      return iterable => largest(number, comp, iterable)
    }
  } else {
    return iterable => largest(number, comp, iterable)
  }
}

The running time is O(n log n), just like sorting an array
And it store only the number of items specified.
The real question here is how to call this :smile:

I like the approach used by lodash, that uses a "getKey" function instead of a comparator (used by python too). I am using the _.iteratee function to get the key, enabling the same expressive syntax used by lodash.
So I decided to go for 2 functions: nlargest and nsmallest, both using the internal take-sorted.
This approach enable also to implement consistently another function called: counter that counts how many repetitions we have for a certain object. For example:
const arr = ['foo', 'bar', 'foo', 'foo']
for (const [value, count] of counter(arr)) {
  console.log(`${value} is repeated ${count} times`)
}

printing:
foo is repeated 3 times
bar is repeated 1 times

But this is for another ticket ...


requires tornado >= 4.0

zmq/eventloop/future.py uses ZMQIOLoop.call_later, which was only added in tornado 4.0.
Would be nice to fall back to ZMQIOLoop.add_timeout for tornado < 4.0.

I'm working from the Debian source so I can't just send a pull request but here is the diff I use to work around this issue:

--- pyzmq-15.4.0.orig/zmq/eventloop/ioloop.py
+++ pyzmq-15.4.0/zmq/eventloop/ioloop.py
@@ -175,6 +175,16 @@ if (3, 0) <= tornado_version < (3, 1):
         return mini_loop.close.__get__(self)(all_fds)
     ZMQIOLoop.close = backport_close

+if (3, 0) <= tornado_version < (4, 0):
+    def backport_call_later(self, delay, callback, *args, **kwargs):
+        """backport IOLoop.call_later to 3.0 from 4.0"""
+        return self.call_at(self.time() + delay, callback, *args, **kwargs)
+    ZMQIOLoop.call_later = backport_call_later
+
+    def backport_call_at(self, when, callback, *args, **kwargs):
+        """backport IOLoop.call_at to 3.0 from 4.0"""
+        return self.add_timeout(when, callback, *args, **kwargs)
+    ZMQIOLoop.call_at = backport_call_at

 # public API name
 IOLoop = ZMQIOLoop

I'm more inclined to put an explicit check that requires actual tornado 4.0 in zmq.eventloop.future. Would that work for you?

If it falls back to the minitornado in that case then that's fine for me.

As a side node: With tornado 4.x and the above patch some tests still fail but work without patch. Is the if (3, 0) <= tornado_version < (4, 0) actually working to detect a tornado version between the two limits? Or does it simply always use the backport? (Asking because of backport_close)


Change the default archivePreserveFileTimestamps and archiveReproducibleFileOrder values

Default to archiveReproducibleFileOrder = true and archivePreserveFileTimestamps = false
The idea of this draft PR is to run CI in order to shake out what would break if such a change is made.

Context

Contributor Checklist

[ ] Review Contribution Guidelines.
[ ] Make sure that all commits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
[ ] Make sure all contributed code can be distributed under the terms of the Apache License 2.0, e.g. the code was written by yourself or the original code is licensed under a license compatible to Apache License 2.0.
[ ] Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team.
[ ] Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective.
[ ] Provide unit tests (under <subproject>/src/test) to verify logic.
[ ] Update User Guide, DSL Reference, and Javadoc for public-facing changes.
[ ] Ensure that tests pass sanity check: ./gradlew sanityCheck.
[ ] Ensure that tests pass locally: ./gradlew <changed-subproject>:quickTest.

Reviewing cheatsheet
Before merging the PR, comments starting with

❌ ❓must be fixed
🤔 💅 should be fixed
💭 may be fixed
🎉 celebrate happy things

@bot-gradle test RFN

I've triggered the following builds for you. Click here to see all build failures.

Ready for Nightly (Trigger) (Check)

@bot-gradle test RFN

I've triggered the following builds for you. Click here to see all build failures.

Ready for Nightly (Trigger) (Check)

No functional test failure but pretty big performance regressions on scenarios that did not enable reproducible archives.


Add Shared::ready method to create a shared future that is immediately ready.

Importantly, this affects the behavior of peek without requiring an async context. Otherwise within an async context one can simply clone and await a shared future to achieve the same effect (though perhaps less efficiently).

Well I kind of mentioned it; this differs in allowing you to immediately peek the value. If you are storing Shared to be reused (much along the same lines as the recent commit that adds the Weak Shared references), this makes a difference in allowing you to peek without having ever awaited the value in an async context. I know it seems fairly niche, but I need it at the moment :) however I suppose I could change my store to simply be some trait object that is Future, Clone, and has peek as well. But I don't really see a reason not to add this method.

If you are storing Shared to be reused (much along the same lines as the recent commit that adds the Weak Shared references), this makes a difference in allowing you to peek without having ever awaited the value in an async context.

I'm not sure how the reuse of Shared is related to WeakShared.
(WeakShared is a weak ptr to the Shared that downgraded. Replacing the original Shared with the new Shared does not update the value of cloned Shared and downgraded WeakShared.)
If you need the ability to keep updating shared values, tokio::sync::watch is probably the right solution.

Sorry, what I meant was that I saw the commit for WeakShared mentions the use case of having a cache of stored Shared, and being able to create ready Shared instances in a cache is also useful (as that is what I need it for). So only very loosely related to WeakShared, more related to their example use case.

But if this is a controversial addition, I was able to make a separate abstraction that achieved what was desired. I do think there's no harm in allowing people to directly create Shared in each of its possible states.

@afranchuk Thanks for clarifying.
My main concern is that Shared is used as a future of shared value, not a future of shared future. I think Shared is not efficient enough for that purpose, and in most cases, custom futures based on ready are more efficient and tokio::sync::watch is more flexible.
It's true that there are cases where it's easier to write with this feature like a test that this PR added, but I don't think they're more efficient than combining MaybeDone or Either with Shared.

(If this has enough documentation on performance (like mentioned in the previous comment), we may accept this, but we recommend that you avoid using it if possible.)


Create account form should be more user friendly

Account Name to Register
New Account's Public Key
Owner's Public Key

https://faucet.bitshares.org
https://bitsharestalk.org/index.php/topic,17543.0.html


Request: Support for non-node runtimes

Currently, arweave.crypto.sign() returns different results in runtimes other than node like bun and deno.
Minimum Reproducible Example
import Arweave from "arweave";
import { readFileSync }  from "node:fs";
import { Buffer } from "node:buffer";

async function test() {
  const arweave = Arweave.init({});
  const keyfile = JSON.parse(readFileSync("./keyfile.json").toString());
  console.log(keyfile);
  const sign = await arweave.crypto.sign(keyfile, Buffer('test'));
  const result = [];
  for (const i of sign.values()) {
    result.push(i);
  }
  console.log(result);
}

test();

Node v21.6.0 (changes every time)
[ 86, 248,  33, 216, 255, 242, 133, 113,  84, 150,  11,  97,
  193,  42,   8,  43, 229, 195, 174, 237, 200, 192,  36, 240,
   94, 164, 130, 234, 101, 249, 191, 106, 177, 206,  92, 148,
   27,  40, 162,  81, 113, 183,  65,  21,   0, 191,  91, 248,
   13, 101,  86, ...]

Bun v1.0.26 (consistent)
[ 7, 146, 211, 91, 31, 2, 185, 167, 35, 48, 68, 168, 183, 8, 156, 90, 205, 202, 40,
  58, 105, 252, 250, 146, 35, 42, 234, 244, 77, 72, 146, 226, 233, 178, 234, 108,
  229, 49, 93, 13, 73, 123, 131, 75, 155, 118, 207, 109, 250, 5, 195, 236, 87, 138,
  213, 43, 80, ...]

Deno v1.40.4 (consistent)
[ 38, 201,  37, 195, 237,  40, 113,  32, 210, 138,  14,  10,
  157, 103,  61, 247,  10, 252,  77,  47,  58, 178, 107, 167,
  209, 180, 194, 113,  94, 150,  36,  97,  19,  44, 112,   7,
  231, 140, 131,  57, 205, 108,  40, 214,  64,  84, 194,  96,
   23,  13, 106, ...]

A lot of downstream libraries seem to be using the crypto driver from this library
Including warp-contracts/warp-arbundles.
This is creating a bit problem since trying to sign a bundled data item seems to fail on non-node runtimes.
Any help with regards to this issue will be appreciated.

hi 👋  there's a couple of things i notice here, but the main thing is that this function doesn't accept a node:buffer as an argument. it's a Uint8Array.
perhaps you could test using something like
const sign = await Arweave.crypto.sign(key, new Uint8Array([1,2,3,4]) )

ah, if you wish the result to be the same each time, you need to take away the randomness added by default by salting. you can do this like so:
const sign = await Arweave.crypto.sign(key, new Uint8Array([1,2,3,4]), {saltLength: 0} )

Hey! Thanks for the help. It seems that crypto.constants.RSA_PSS_SALTLEN_MAX_SIGN is undefined for bun.

I'm reopening this as I'd like to further investigate patching this. Supporting bun/deno would be nice!

Cool I'll link the associated issues for tracking:
https://github.com/oven-sh/bun/issues/8831
https://github.com/oven-sh/bun/issues/8832

@rosmcmahon
I got it working by using the ./web/index.js in Bun.
Bun supports Web Crypto, which doesn't seem to have the compat issues from their node:crypto module.
It seems these are the exports that Bun can use:
"exports": {
    "bun": "./index.js",
    "worker": "./index.js",
    "node": "./index.js",
    "require": "./index.js", // if importer is CommonJS
    "import": "./index.mjs", // if importer is ES module
    "default": "./index.js",
}

So, in theory it should be possible to tell Bun to use the web/index.js, which, in turn uses Web Crypto.

Deno also supports Web Crypto, so I would assume this could also be a solution for Deno.

Fantastic @kay-is ! I have a plan to switch everything over to webcrypto anyhow


word clouds?

it might be interesting to render small dynamic word clouds in the browse view.  Perhaps they consider the last week or 1000 utterances (whichever provides more results) and highlight current topics?
an efficient implementation of this probably requires server support and a new API.

I have client-side code to draw a word cloud on HTML5 canvas
https://github.com/timdream/wordcloud/


Add example column

Is your feature request related to a problem? Please describe.
To easily know if there's an issue with the provided function it'd be nice to see an example of the expected output along side the comment, etc. columns.

@OmgImAlexis Started to add examples for the first functions ... will continuously add more examples.

@OmgImAlexis ... done for most of the functions. I will try continuously try improve it. If you have further comments, just feel free to send me your hints ... closing it for now.


Add PubNub to Distributed Computing heading.

Distributed Computing/PubNub - PubNub
Realtime apps made simple. APIs for developers building secure realtime mobile, web, and IoT applications. C# SDKs here. [Free]

It'd be better to change the description because currently it's completely not possible to identify what is it about. Also, since it's a service bus, it's better to put it into Queue section where most of other service buses reside. Also, the library is free but it requires PubNub account to be used, which also has a free plan, but it's not free, it's freemium

Closing the pull request because of lack of interest from the contributor and raised concerns


ZeroDivisionError when server has no swap

Hello
Description
When the machine has no swap, the pg_activity does not open
Software version: 3.0.0
Steps to reproduce:
Configure a machine with no swap, launch pg_activity
Expected results:
pg_activity opens
Actual results:
pg_acrivity crashes with ZeroDivisionError: division by zero
root@db1:~# pg_activity

Traceback (most recent call last):
  File "/usr/local/bin/pg_activity", line 8, in <module>
    sys.exit(main())
  File "/usr/local/pythonenv/pg_activity/lib/python3.7/site-packages/pgactivity/cli.py", line 407, in main
    ui.main(term, dataobj, host, args)
  File "/usr/local/pythonenv/pg_activity/lib/python3.7/site-packages/pgactivity/ui.py", line 250, in main
    width=width,
  File "/usr/local/pythonenv/pg_activity/lib/python3.7/site-packages/pgactivity/views.py", line 572, in screen
    width=width,
  File "/usr/local/pythonenv/pg_activity/lib/python3.7/site-packages/pgactivity/views.py", line 124, in wrapper
    for line in func(term, *args, **kwargs):
  File "/usr/local/pythonenv/pg_activity/lib/python3.7/site-packages/pgactivity/views.py", line 324, in header
    [f"{render(free)} ({render(system_info.swap.pct_free)}) free"],
  File "/usr/local/pythonenv/pg_activity/lib/python3.7/site-packages/pgactivity/types.py", line 704, in pct_free
    return Pct(self.free * 100 / self.total)
ZeroDivisionError: division by zero
root@db1:~# free
              total        used        free      shared  buff/cache   available
Mem:       32296672     6219592      571240      622296    25505840    25097340
Swap:             0           0           0
root@evoluxio-db1:~#

thanks for reporting this !


A few changes

Some changes to improve the readability of the code in general
Please note that const does not make your data imutable :p
Otherwise, your site is beautiful and I hope Olivia will succeed in governing the world

Thanks a lot! :)


chore(deps): bump https://github.com/jenkins-x/jx-cli to 3.0.376

Update jenkins-x/jx-cli to 3.0.376
Command run was ./promote/main

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign cagiti
You can assign the PR to them by writing /assign @cagiti in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Look for NAT IPs instead of getting them from the Router

The router only contains the NAT IPs if they are static. The cluster
however has automatically allocated NAT IPs. These are not listed in the
router and we must get them ourselves

Part of giantswarm/roadmap#1293


Create application to transform data from DynamoDB raw to ES "unified" format

All the data is sitting in DynamoDB – we need something that can pull the data into an Elasticsearch instance.
This task covers doing this for a complete re-ingest operation – where we’re starting from scratch, or we’re changed our ES mappings and need to rebuild our ES tables from scratch. Related: #55.
This task covers 3 parts:

DynamoDB Streams
Transform to ES unified format
Place unified format into queue for updating ES

Resolved by #71.


[SPARK-37779][SQL] Make ColumnarToRowExec plan canonicalizable after (de)serialization

What changes were proposed in this pull request?
This PR proposes to add a driver-side check on supportsColumnar sanity check at ColumnarToRowExec.
Why are the changes needed?
SPARK-23731 fixed the plans to be serializable by leveraging lazy but SPARK-28213 happened to refer to the lazy variable at: https://github.com/apache/spark/blob/77b164aac9764049a4820064421ef82ec0bc14fb/sql/core/src/main/scala/org/apache/spark/sql/execution/Columnar.scala#L68
This can fail during canonicalization during, for example, eliminating sub common expressions (on executor side):
java.lang.NullPointerException
    at org.apache.spark.sql.execution.FileSourceScanExec.supportsColumnar$lzycompute(DataSourceScanExec.scala:280)
    at org.apache.spark.sql.execution.FileSourceScanExec.supportsColumnar(DataSourceScanExec.scala:279)
    at org.apache.spark.sql.execution.InputAdapter.supportsColumnar(WholeStageCodegenExec.scala:509)
    at org.apache.spark.sql.execution.ColumnarToRowExec.<init>(Columnar.scala:67)
    ...
    at org.apache.spark.sql.catalyst.plans.QueryPlan.canonicalized$lzycompute(QueryPlan.scala:581)
    at org.apache.spark.sql.catalyst.plans.QueryPlan.canonicalized(QueryPlan.scala:580)
    at org.apache.spark.sql.execution.ScalarSubquery.canonicalized$lzycompute(subquery.scala:110)
    ...
    at org.apache.spark.sql.catalyst.expressions.ExpressionEquals.hashCode(EquivalentExpressions.scala:275)
    ...
    at scala.collection.mutable.HashTable.findEntry$(HashTable.scala:135)
    at scala.collection.mutable.HashMap.findEntry(HashMap.scala:44)
    at scala.collection.mutable.HashMap.get(HashMap.scala:74)
    at org.apache.spark.sql.catalyst.expressions.EquivalentExpressions.addExpr(EquivalentExpressions.scala:46)
    at org.apache.spark.sql.catalyst.expressions.EquivalentExpressions.addExprTreeHelper$1(EquivalentExpressions.scala:147)
    at org.apache.spark.sql.catalyst.expressions.EquivalentExpressions.addExprTree(EquivalentExpressions.scala:170)
    at org.apache.spark.sql.catalyst.expressions.SubExprEvaluationRuntime.$anonfun$proxyExpressions$1(SubExprEvaluationRuntime.scala:89)
    at org.apache.spark.sql.catalyst.expressions.SubExprEvaluationRuntime.$anonfun$proxyExpressions$1$adapted(SubExprEvaluationRuntime.scala:89)
    at scala.collection.immutable.List.foreach(List.scala:392)

This fix is still a bandaid fix but at least addresses the issue with minimized change - this fix should ideally be backported too.
Does this PR introduce any user-facing change?
Pretty unlikely - when ColumnarToRowExec has to be canonicalized on the executor side (see the stacktrace), but yes. it would fix a bug.
How was this patch tested?
Unittest was added.

Thanks!
Merged to master.

Merged to master, branch-3.2, branch-3.1 and branch-3.0.

Sorry, but it seems that this broke branch-3.1 due to some mismatch.
[info] SparkPlanSuite:
[info] - SPARK-37779: ColumnarToRowExec should be canonicalizable after being (de)serialized *** FAILED *** (7 seconds, 1 milliseconds)
[info]   ColumnarToRowExec was not canonicalizable (SparkPlanSuite.scala:105)
[info]   org.scalatest.exceptions.TestFailedException:
...
[info] *** 1 TEST FAILED ***
[error] Failed: Total 1, Failed 1, Errors 0, Passed 0
[error] Failed tests:
[error] 	org.apache.spark.sql.execution.SparkPlanSuite
[error] (sql / Test / testOnly) sbt.TestsFailedException: Tests unsuccessful
[error] Total time: 378 s (06:18), completed Jan 4, 2022 11:54:14 PM

Weirdly, branch-3.0 is okay. Let me revert this from branch-3.1 first. Could you make a backporting PR to branch-3.2, @HyukjinKwon ?

weird .. let me just revert it from branch-3.1 and branch-3.0 for now.

Thanks for checking this @dongjoon-hyun

Thank you, @HyukjinKwon !

we encountered following exception after upgrade to Iceberg 1.3.1 + Spark 3.4.1
Caused by: java.lang.AssertionError: assertion failed
 at scala.Predef$.assert(Predef.scala:208)
 at org.apache.spark.sql.execution.ColumnarToRowExec.<init>(Columnar.scala:72)
 ... 173 more

also post to https://github.com/apache/iceberg/issues/9092


reviveNumbers should be disabled by default

Thanks for providing this module, it's tremendously helpful!
> import { parse } from "./deps.ts"
undefined
> parse("<foo>001</foo>")
{ foo: 1 }
> parse("<foo>313130e130</foo>")
{ foo: 3.1313e+135 }
> parse("<foo>313130e123</foo>")
{ foo: 3.1313e+128 }

I think it should definitely not be turned on by default, because you might end up losing important information if you're not careful.
As a side-note, usually options like this are designed so that an explicit value of undefined corresponds to the default behavior, which is not the case here. Just wanted to mention that, but I don't really know what to call it other than reviveNumbers.

The default behaviour was changed in v3 to disable both reviveNumbers and reviveBooleans


Bug:  Water Pulse dmg scaling

Info about your system

OS:
Mystery Dungeon mod version:

Additional information (can include other mods if you think this could be useful):
Describe the bug in as much detail
When having additional dmg water pulse scale his smg like a multi hit
Log output (can be extremely useful for crashes)

fixed in 27bb1b70343268eb16226010a72a305fd6859f30


Update CentOS AMIs to version 7.4-1708

Backport of http://github.com/dcos/dcos/pull/2040

update changelog
update CI script to update to 7.4
update packer to use CENTOS_VERSION environment variable

set CENTOS_VERSION in user variables
explicitly pass CENTOS_VERSION in inline cmd
add centos 7.4 AMIs to changelog
create_base_ami.sh updates to 7.4 instead of 7.2
correct AMI name for dcos-centos7
update centos AMIs to 7.4
update govcloud us-gov-west-1 CentOS AMI to 7.4
update changelog for govcloud
add NAT AMI for govcloud region
Default to CentOS 7.4 to match default TeamCity CENTOS_VERSION
High Level Description
What features does this change enable? What bugs does this change fix? High-Level description of how things changed.
Related Issues

DCOS_OSS- Foo the Bar so it stops Bazzing.
DCOS- Foo the Bar so it stops Bazzing.

Checklist for all PR's

[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[ ] Read the DC/OS contributing guidelines
[ ] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[ ] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

PLEASE FILL IN THE TEMPLATE ABOVE / DO NOT REMOVE ANY SECTIONS ABOVE THIS LINE
Instructions and Review Process
What is the review process and when will my changes land?
All PRs require 2 approvals using github's pull request reviews.
Reviewers should be:

Developers who understand the code being modified.
Developers responsible for code that interacts with or depends on the code being modified.

It is best to proactively ask for 2 reviews by @mentioning the candidate reviewers in the PR comments area. The responsibility is on the developer submitting the PR to follow-up with reviewers and make sure a PR is reviewed in a timely manner. Once a PR has 2 ship-it's, no red reviews, and all tests are green it will be included in the next train.

@mesosphere-mergebot bump-ee

@mesosphere-mergebot label ready for review

teamcity/dcos/test/aws/onprem/static looks like flaky vip tests, see: https://jira.mesosphere.com/browse/DCOS_OSS-1463 Re-running.

mergebot/enterprise/build-status/aggregate will not go green, due to expected issues with tox build. This is ready to ship!

Is there a DC/OS JIRA ticket to be closed now that this patch was merged?


The ubuntu-18.04 environment is not suitable for building packages intended for deployment to other 18.04 systems

Description
If a package is built on the ubuntu-18.04 virtual environment (using runs-on: ubuntu-18.04), the resulting .deb file may not run on actual ubuntu 18.04 systems because of spurious dependencies. For example, a dependency on libgcc-s1 can be introduced because the virtual environment contains newer versions of gcc than those present in upstream Ubuntu 18.04.
Thus, it seems the ubuntu-18.04 environment is suitable for running stuff, but not for building stuff intended for deployment to other 18.04 systems.
The right way to build packages is probably to use a container from Canonical.
Area for Triage:

This is probably a documentation issue.
Question, Bug, or Feature?:

Bug
Virtual environments affected

[ ] Ubuntu 16.04
[X] Ubuntu 18.04
[ ] Ubuntu 20.04
[ ] macOS 10.15
[ ] macOS 11.0
[ ] Windows Server 2016 R2
[ ] Windows Server 2019

Image version

ubuntu-18.04
Expected behavior
A build in 18.04 can be deployed to other 18.04 machines.
Actual behavior
The resulting .deb package refuses to install on actual 18.04 systems.
Repro steps
See https://github.com/diffblue/cbmc/pull/5875

Hello, @sree314
Agree, this point should be updated in the official docs. Please create an issue - https://github.com/github/docs.


⚠ Processors has degraded performance

In 6ec8585, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 54 ms

Resolved: Processors performance has improved in 416d751.


[Perl] Rare segfault in rnn gluon test

@sergeykolychev can you elaborate more on this failure? can you share any error log you might have? Does this issue persist even after merging this PR - https://github.com/apache/incubator-mxnet/pull/9414

@anirudhacharya thanks for the report, I'll check it out in next few days

I have not been able to reproduce this issue even after running the test for ~10k times.
@sergeykolychev is this something you are actively looking into? are you okay with closing this issue? from the past many CI runs, I don't think this is failing anymore.

@anirudhacharya go ahead and close the issue. thanks!


Redirect URI not matching

invalid_request: The provided value for the input parameter 'redirect_uri' is not valid. The expected value is a URI which matches a redirect URI registered for this client application.

Did you see #15?

This solution is now outdated, as you can't change app settings in apps.dev.microsoft.com.
You have to go through the Azure setup, which doesn't allow urls that do not start with 'http', making "urn:ietf:wg:oauth:2.0:oob" invalid.
I have the same issue as #15, using the Python sample redirects to a login page, which gets skipped quite fast to the error message :
invalid_request: The provided value for the input parameter 'redirect_uri' is not valid. The expected value is a URI which matches a redirect URI registered for this client application.

@sebomio this tutorial does not have you go to apps.dev.microsoft.com, so I'm not sure what your feedback is about.
I've refreshed this tutorial for the latest version of MSAL, which does change the redirect. See the version in this branch: https://github.com/microsoftgraph/msgraph-training-uwp/tree/refresh-tutorial

Fixed via https://github.com/microsoftgraph/msgraph-training-uwp/pull/33


prompt when tunnel already started

If a user starts a new tunnel, and an old one is already running, give a prompt to ask if we should stop the old and start the new

Already closed in other PRs


Updating to v0.9.25 breaks existing migrations

I am not able to run migrations anymore, after updating to v0.9.25
Node version: v5.10.0, v6.2.1
Npm version: v3.9.3
db-migrate version: v0.9.25
db-migrate-pg version: v0.1.10
When I downgrade to<EMAIL_ADDRESS>all is working again.
Are there any breaking changes? If so, where can I find them?
Verbose run:
db-migrate up --verbose
[INFO] Using dev settings: { driver: 'pg',
  user: 'pg-mitasco',
  password: '******',
  database: 'mitasco-dev3',
  host: 'localhost' }
[INFO] require: ./pg
[INFO] connecting
[INFO] connected
[SQL] select version() as version
[SQL] SHOW search_path
[SQL] SET search_path TO "$user","public"
[SQL] SELECT table_name FROM information_schema.tables WHERE table_name = 'migrations' AND table_schema = 'public'
[INFO] migration table created
[INFO] loading migrations from dir /Users/Ubuntu/WebstormProjects/mitasco/migrations
[INFO] loading migrations from database
[SQL] SELECT * FROM "migrations" ORDER BY run_on DESC, name DESC
[INFO] preparing to run up migration:<PHONE_NUMBER>3034-a
[SQL] BEGIN;
[ERROR] TypeError: Promise is not a constructor
    at exports.up (/Users/Ubuntu/WebstormProjects/mitasco/migrations/20160515183034-a.js:23:12)
    at Migration._up (/Users/Ubuntu/.nvm/versions/node/v6.2.1/lib/node_modules/db-migrate/lib/migration.js:172:32)
    at Migration.up (/Users/Ubuntu/.nvm/versions/node/v6.2.1/lib/node_modules/db-migrate/lib/migration.js:184:8)
    at Object.Migrator.up (/Users/Ubuntu/.nvm/versions/node/v6.2.1/lib/node_modules/db-migrate/lib/migrator.js:84:7)
    at /Users/Ubuntu/.nvm/versions/node/v6.2.1/lib/node_modules/db-migrate/lib/migrator.js:116:18
    at .callback (/Users/Ubuntu/.nvm/versions/node/v6.2.1/lib/node_modules/db-migrate/lib/driver/pg.js:17:44)
    at Query.handleReadyForQuery (/Users/Ubuntu/.nvm/versions/node/v6.2.1/lib/node_modules/db-migrate/node_modules/pg/lib/query.js:89:10)
    at .<anonymous> (/Users/Ubuntu/.nvm/versions/node/v6.2.1/lib/node_modules/db-migrate/node_modules/pg/lib/client.js:163:19)
    at emitOne (events.js:101:20)
    at emit (events.js:188:7)

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/34885683-updating-to-v0-9-25-breaks-existing-migration?utm_campaign=plugin&utm_content=tracker%2F73887&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F73887&utm_medium=issues&utm_source=github).

Um, was it intended that you downgraded to 0.9.25 when you have been on 0.10.x before?

current version of 0.10.x track is https://github.com/db-migrate/node-db-migrate/blob/v0.10.x/package.json#L34

I guess you really accidentally downgraded without noticing this.

Yet my travis build stopped working suddenly, because of that error.
The default package npm gets is a 0.9.xx one?
I am wondering how I got that 0.10.x package, and started working with it in the first place...

same for Travis, it worked before,
must have been because it got a 0.10.x package?
I am still confused, anyways I will close and force a 0.10.x package in my travis build:
before_script:
  - npm install -g db-migrate@@v0.10.0-beta.12 db-migrate-pg

Thx for the reply!

That is strange indeed, npm always pulls a version first that has no suffix like -betaxxx. NPM would get 0.9.x as a default.

FYI, looking back in my travis build history,
looks like npm on travis did pull a beta package, without the suffix:

Either we have a cache problem or the behavior of npm has changed somehow.


ServiceStack.Text version issue

Just got the latest NuGet package which installed ServiceStack.Text version <IP_ADDRESS> correctly.
When I run, though, I get this:
Foo : System.IO.FileNotFoundException : Could not load file or assembly 'ServiceStack.Text, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
What needs to be done?  Anything I can do on my end?

I'm seeing that error... Do I need a more recent version of the DLL?
Could not load file or assembly 'ServiceStack.Text, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.

@Calothis - are you also using a different version of ServiceStack.Text in your project?

Our webapp has ServiceStack 4 installed, is there any way to assembly bind this up or something?  Could not load file or assembly 'ServiceStack.Text, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

I don't know what any of this means...
Alex
On Thu, Sep 10, 2015 at 5:22 PM, Steve McNiven-Scott <
<EMAIL_ADDRESS>wrote:

Our webapp has ServiceStack 4 installed, is there any way to assembly bind
this up or something? Could not load file or assembly 'ServiceStack.Text,
Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null' or one of its
dependencies. The located assembly's manifest definition does not match the
assembly reference. (Exception from HRESULT: 0x80131040)
—
Reply to this email directly or view it on GitHub
https://github.com/danesparza/MailChimp.NET/issues/48#issuecomment-139251546
.


Add support for locale generation using claude AI

Hi @westoque This is a really nice gem idea, I will surely use it a lot.
I gave it a shot at adding Claude support  in #5
Can you take a look and let me know your thoughts?

@wilburhimself oh. i should have put my comment on the proposed settings strategy here. but here's a link:
https://github.com/narralabs/i18n-ai/pull/5#issuecomment-2263384028


Describe which tests failed and why

Perfect.


keepass: 2.39 -> 2.39.1

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/keepass/versions.
These checks were done:

built on NixOS
ran ‘/nix/store/qgy0xnizyq301xhnqrklr75b59y6k7ni-keepass-2.39.1/bin/.keepass-wrapped -h’ got 0 exit code
ran ‘/nix/store/qgy0xnizyq301xhnqrklr75b59y6k7ni-keepass-2.39.1/bin/.keepass-wrapped --help’ got 0 exit code
ran ‘/nix/store/qgy0xnizyq301xhnqrklr75b59y6k7ni-keepass-2.39.1/bin/.keepass-wrapped help’ got 0 exit code
ran ‘/nix/store/qgy0xnizyq301xhnqrklr75b59y6k7ni-keepass-2.39.1/bin/keepass -h’ got 0 exit code
ran ‘/nix/store/qgy0xnizyq301xhnqrklr75b59y6k7ni-keepass-2.39.1/bin/keepass --help’ got 0 exit code
ran ‘/nix/store/qgy0xnizyq301xhnqrklr75b59y6k7ni-keepass-2.39.1/bin/keepass help’ got 0 exit code
found 2.39.1 with grep in /nix/store/qgy0xnizyq301xhnqrklr75b59y6k7ni-keepass-2.39.1
directory tree listing: https://gist.github.com/78c15efa16b6307a93c5f5336a99df32
du listing: https://gist.github.com/c18c593ba095ab336bc0102838e529ca

meta.description for keepass is: '"GUI password manager with strong cryptography"'.
cc @AndrewMorsillo @obadz @joncojonathan @jraygauthier for testing.

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: keepass
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: keepass
Partial log (click to expand)
/nix/store/qgy0xnizyq301xhnqrklr75b59y6k7ni-keepass-2.39.1 /build
/build
Created /nix/store/qgy0xnizyq301xhnqrklr75b59y6k7ni-keepass-2.39.1/lib/pkgconfig/KeePassLib.pc
rscFileExt=ico
glibPreFixupPhase
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/qgy0xnizyq301xhnqrklr75b59y6k7ni-keepass-2.39.1
patching script interpreter paths in /nix/store/qgy0xnizyq301xhnqrklr75b59y6k7ni-keepass-2.39.1
checking for references to /build in /nix/store/qgy0xnizyq301xhnqrklr75b59y6k7ni-keepass-2.39.1...
/nix/store/qgy0xnizyq301xhnqrklr75b59y6k7ni-keepass-2.39.1

Failure on aarch64-linux (full log)
Attempted: keepass
Partial log (click to expand)
make[3]: *** [Makefile:49: profiles-do--all] Error 2
make[2]: *** [Makefile:636: all-local] Error 2
make[2]: Leaving directory '/build/mono-<IP_ADDRESS>/runtime'
make[1]: *** [Makefile:549: all-recursive] Error 1
make[1]: Leaving directory '/build/mono-<IP_ADDRESS>'
make: *** [Makefile:479: all] Error 2
builder for '/nix/store/yr3zyqq05s4vwh8vyiqsbz45bazr2mwa-mono-<IP_ADDRESS>.drv' failed with exit code 2
cannot build derivation '/nix/store/qaza4h08dqxjj15qsi8a5pvfg12gdsv9-dotnetbuildhelpers.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/wl0f879rcqcj6dz39cc2r8j6dsn6248k-keepass-2.39.1.drv': 2 dependencies couldn't be built
error: build of '/nix/store/wl0f879rcqcj6dz39cc2r8j6dsn6248k-keepass-2.39.1.drv' failed


Explicitly define user scope for Microsoft.PowerShell <IP_ADDRESS>

Based off of discussion in https://github.com/microsoft/winget-pkgs/pull/169497#issuecomment-2314552354

Microsoft Reviewers: Open in CodeFlow

Hi @anamnavi,
Do you approve of these changes?
(Automated response - build 891.)


[REVIEW]

GitHub Profile Link
https://github.com/soumdatta81

Reviewed on live stream, looks great, some suggestions

Great to see you halved the banner height already 👍
Add your Org to your profile
Text is very close to the animated image
Widgets take a lot of height, suggest having them side by side
Suggest doing some more code reviews for you contributors graph

Thanks Eddie for your feedback.


Don't force inliner in case of ref type function args

This was required previously, but after the IR refactoring (#4336), this is no longer required, and actually worsens things.
Fixes #4747. For the two tests mentioned there, (both based on https://github.com/hashcloak/fuel-crypto/) the compile time now comes down from

30m -> 16s
180m -> 31s

Also fixes two bugs uncovered:

Bug in DCE - Fixes #4763. (https://github.com/FuelLabs/sway/pull/4823/commits/1b512b87d2273ecd7d34da4a67b40f2f43305123)
Bug in interaction b/w asm gen and reg alloc spiller (https://github.com/FuelLabs/sway/pull/4823/commits/7a404967e732af52bd60e36766df461688c01fff).

Here are some stats from our testsuite.
Code increase is in small tests, where not inlining results in the overheads of a function call dominating. There are a few exceptions to this that need to be investigated though.
But irrespective of the stats, this change is necessary, because the inliner heuristic I'm removing here is not based on any inliner "thought" but as a workaround against some other bug that has been since fixed.

<title></title>
<meta name="generator" content="LibreOffice <IP_ADDRESS> (Linux)"/>
<style type="text/css">
	body,div,table,thead,tbody,tfoot,tr,th,td,p { font-family:"Liberation Sans"; font-size:x-small }
	a.comment-indicator:hover + comment { background:#ffd; position:absolute; display:block; border:1px solid black; padding:0.5em;  }
	a.comment-indicator { background:red; display:inline-block; border:1px solid black; width:0.5em; height:0.5em;  }
	comment { display:none;  }
</style>

Test
master
inliner_fix
% reduction (+ is better)

Testing should_pass/non_payable_implicit_zero_coins
240
240
0

Testing should_pass/forc/contract_dependencies/contract_b
68
68
0

Testing should_pass/forc/contract_dependencies/contract_c
68
68
0

Testing should_pass/forc/contract_dependencies/contract_a
68
324
-376.470588235294

Testing should_pass/forc/dependency_package_field
36
36
0

Testing should_pass/forc/dependency_patching
36
36
0

Testing should_pass/forc/parent_pkg_manifest/contract_a
68
68
0

Testing should_pass/evm/evm_basic
36
36
0

Testing should_pass/language/basic_func_decl
36
36
0

Testing should_pass/language/integer_type_inference
36
36
0

Testing should_pass/language/const_decl_in_library
76
76
0

Testing should_pass/language/mutable_arrays_struct
156
156
0

Testing should_pass/language/unary_not_basic
36
36
0

Testing should_pass/language/associated_const_trait_method
36
36
0

Testing should_pass/language/import_trailing_comma
84
84
0

Testing should_pass/language/struct_field_access
92
92
0

Testing should_pass/language/type_alias
5760
4328
24.8611111111111

Testing should_pass/language/mutable_arrays
116
116
0

Testing should_pass/language/prelude_access
36
36
0

Testing should_pass/language/trait_method_generic_qualified
36
36
0

Testing should_pass/language/generic_where_in_impl_self2
460
460
0

Testing should_pass/language/array_generics
84
84
0

Testing should_pass/language/is_prime
1116
1116
0

Testing should_pass/language/out_of_order_decl
52
52
0

Testing should_pass/language/associated_const_impl_self
36
36
0

Testing should_pass/language/binary_and_hex_literals
36
36
0

Testing should_pass/language/chained_if_let
172
172
0

Testing should_pass/language/builtin_type_method_call
52
52
0

Testing should_pass/language/match_expressions_nested
164
164
0

Testing should_pass/language/raw_identifiers
140
140
0

Testing should_pass/language/struct_init_reorder
116
116
0

Testing should_pass/language/ref_mutable_fn_args_struct_assign
92
92
0

Testing should_pass/language/generic_enum
36
36
0

Testing should_pass/language/op_precedence
36
36
0

Testing should_pass/language/retd_struct
120
120
0

Testing should_pass/language/attributes_warnings
36
36
0

Testing should_pass/language/break_and_continue_block_ret
44
44
0

Testing should_pass/language/typeinfo_custom_callpath
100
100
0

Testing should_pass/language/retd_small_array
60
60
0

Testing should_pass/language/many_stack_variables
780
780
0

Testing should_pass/language/multi_item_import
36
36
0

Testing should_pass/language/ref_mutable_fn_args_struct
84
84
0

Testing should_pass/language/inline_if_expr_const
36
36
0

Testing should_pass/language/contract_caller_as_ret
68
68
0

Testing should_pass/language/mutable_arrays_enum
156
156
0

Testing should_pass/language/ref_mutable_arrays
116
116
0

Testing should_pass/language/tuple_in_struct
916
916
0

Testing should_pass/language/doc_comments
84
84
0

Testing should_pass/language/unary_not_basic_2
36
36
0

Testing should_pass/language/match_expressions_simple
340
340
0

Testing should_pass/language/gtf_intrinsic
92
92
0

Testing should_pass/language/modulo_uint_test
300
300
0

Testing should_pass/language/ret_string_in_struct
80
80
0

Testing should_pass/language/smo_opcode
112
112
0

Testing should_pass/language/arg_demotion_inline
68
68
0

Testing should_pass/language/ret_small_string
64
64
0

Testing should_pass/language/match_expressions_rest
156
156
0

Testing should_pass/language/b256_bad_jumps
36
36
0

Testing should_pass/language/tuple_single_element
108
108
0

Testing should_pass/language/match_expressions_mismatched
116
116
0

Testing should_pass/language/basic_predicate
36
36
0

Testing should_pass/language/if_elseif_enum
756
676
10.5820105820106

Testing should_pass/language/associated_const_impl
36
36
0

Testing should_pass/language/associated_const_trait_const
36
36
0

Testing should_pass/language/implicit_return
52
52
0

Testing should_pass/language/generic_transpose
868
868
0

Testing should_pass/language/insert_element_reg_reuse
5044
4748
5.86835844567803

Testing should_pass/language/where_clause_structs
380
380
0

Testing should_pass/language/enum_variant_imports
844
844
0

Testing should_pass/language/configurable_consts
4476
4444
0.714924039320822

Testing should_pass/language/match_expressions_with_self
396
396
0

Testing should_pass/language/where_clause_impls
524
524
0

Testing should_pass/language/enum_type_inference
52
52
0

Testing should_pass/language/implicit_casting
52
52
0

Testing should_pass/language/binop_intrinsics
948
948
0

Testing should_pass/language/abort_control_flow_good
52
52
0

Testing should_pass/language/match_expressions_structs
212
212
0

Testing should_pass/language/funcs_with_generic_types
36
36
0

Testing should_pass/language/typeinfo_custom_callpath2
100
100
0

Testing should_pass/language/bool_and_or
84
84
0

Testing should_pass/language/eq_and_neq
1332
2188
-64.2642642642643

Testing should_pass/language/const_decl_with_call_path
364
364
0

Testing should_pass/language/unit_type_variants
60
60
0

Testing should_pass/language/ops
5212
5212
0

Testing should_pass/language/far_jumps/many_blobs
11640280
11640280
0

Testing should_pass/language/far_jumps/single_blob
1048656
1048656
0

Testing should_pass/language/ref_mutable_fn_args_call
60
60
0

Testing should_pass/language/size_of
260
260
0

Testing should_pass/language/zero_field_types
52
52
0

Testing should_pass/language/asm_without_return
60
60
0

Testing should_pass/language/where_clause_functions
1932
1932
0

Testing should_pass/language/associated_const_impl_local_same_name
36
36
0

Testing should_pass/language/struct_destructuring
204
204
0

Testing should_pass/language/is_reference_type
516
516
0

Testing should_pass/language/reassignment_operators
260
260
0

Testing should_pass/language/enum_if_let_large_type
436
436
0

Testing should_pass/language/match_expressions_enums
148
148
0

Testing should_pass/language/asm_expr_basic
284
284
0

Testing should_pass/language/same_const_name_lib
28
28
0

Testing should_pass/language/associated_const_abi
36
36
0

Testing should_pass/language/nested_structs
1940
1940
0

Testing should_pass/language/retd_b256
128
128
0

Testing should_pass/language/same_const_name
1036
1036
0

Testing should_pass/language/tuple_types
52
52
0

Testing should_pass/language/tuple_trait
140
140
0

Testing should_pass/language/associated_const_trait
36
36
0

Testing should_pass/language/predicate_while_dep
68
68
0

Testing should_pass/language/generic_impl_self_where
2260
2532
-12.0353982300885

Testing should_pass/language/enum_if_let
640
640
0

Testing should_pass/language/main_returns_unit
36
36
0

Testing should_pass/language/tuple_indexing
68
68
0

Testing should_pass/language/mutable_arrays_nested
196
196
0

Testing should_pass/language/match_expressions_empty_enums
52
52
0

Testing should_pass/language/associated_const_abi_default
36
36
0

Testing should_pass/language/shadowing/shadowed_glob_imports
36
36
0

Testing should_pass/language/eq_intrinsic
588
588
0

Testing should_pass/language/struct_field_reassignment
36
36
0

Testing should_pass/language/generic_structs
52
52
0

Testing should_pass/language/ref_mutable_arrays_inline
116
116
0

Testing should_pass/language/import_with_different_callpaths
2492
3180
-27.6083467094703

Testing should_pass/language/main_args/main_args_ref_copy
60
60
0

Testing should_pass/language/main_args/main_args_copy
52
52
0

Testing should_pass/language/main_args/main_args_ref_ref
60
60
0

Testing should_pass/language/main_args/main_args_various_types
452
452
0

Testing should_pass/language/main_args/main_args_empty
52
52
0

Testing should_pass/language/main_args/main_args_ref
52
52
0

Testing should_pass/language/main_args/main_args_copy_copy
52
52
0

Testing should_pass/language/prelude_access2
36
36
0

Testing should_pass/language/use_full_path_names
36
36
0

Testing should_pass/language/typeinfo_custom_callpath_with_import
164
164
0

Testing should_pass/language/retd_zero_len_array
44
44
0

Testing should_pass/language/where_clause_enums
612
612
0

Testing should_pass/language/generic_functions
36
36
0

Testing should_pass/language/b256_bitwise_ops
25288
14292
43.4830749762733

Testing should_pass/language/mutable_and_initd
164
164
0

Testing should_pass/language/enum_in_fn_decl
116
116
0

Testing should_pass/language/associated_const_abi_multiple
36
36
0

Testing should_pass/language/valid_impurity
68
68
0

Testing should_pass/language/nested_while_and_if
164
164
0

Testing should_pass/language/mutable_arrays_multiple_nested
172
172
0

Testing should_pass/language/where_clause_traits
36
36
0

Testing should_pass/language/supertraits
4204
4204
0

Testing should_pass/language/match_expressions_constants
92
92
0

Testing should_pass/language/tuple_field_reassignment
1188
1188
0

Testing should_pass/language/enum_destructuring
124
124
0

Testing should_pass/language/revert_in_first_if_branch
52
52
0

Testing should_pass/language/logging
472
472
0

Testing should_pass/language/where_clause_methods
1924
1924
0

Testing should_pass/language/ref_mutable_fn_args_bool
52
52
0

Testing should_pass/language/diagnose_unknown_annotations
100
100
0

Testing should_pass/language/bitwise_not
220
220
0

Testing should_pass/language/generic_struct
44
44
0

Testing should_pass/language/primitive_type_argument
52
52
0

Testing should_pass/language/fix_opcode_bug
52
52
0

Testing should_pass/language/trait_method_ascription_disambiguate
36
36
0

Testing should_pass/language/smo
892
892
0

Testing should_pass/language/import_method_from_other_file
508
508
0

Testing should_pass/language/aliased_imports
60
60
0

Testing should_pass/language/left_to_right_func_args_evaluation
188
188
0

Testing should_pass/language/mutable_arrays_swap
116
116
0

Testing should_pass/language/break_and_continue
780
780
0

Testing should_pass/language/generic_type_inference
3916
4236
-8.17160367722165

Testing should_pass/language/empty_method_initializer
416
416
0

Testing should_pass/language/const_inits
3172
3292
-3.78310214375788

Testing should_pass/language/if_implicit_unit
36
36
0

Testing should_pass/language/enum_init_fn_call
812
812
0

Testing should_pass/language/complex_cfg
340
524
-54.1176470588235

Testing should_pass/language/use_absolute_path
36
36
0

Testing should_pass/language/enum_padding
116
116
0

Testing should_pass/language/method_type_args
36
36
0

Testing should_pass/language/method_on_empty_struct
36
36
0

Testing should_pass/language/const_decl
52
52
0

Testing should_pass/language/tuple_access
144
144
0

Testing should_pass/language/impure_ifs
804
1252
-55.7213930348259

Testing should_pass/language/ref_mutable_fn_args_u32
60
60
0

Testing should_pass/language/match_expressions_or
724
724
0

Testing should_pass/language/trait_import_with_star
60
60
0

Testing should_pass/language/generic_where_in_impl_self
460
460
0

Testing should_pass/language/match_expressions_explicit_rets
36
36
0

Testing should_pass/language/while_loops
420
420
0

Testing should_pass/language/generics_in_contract
472
608
-28.8135593220339

Testing should_pass/language/associated_const_trait_impl_method
36
36
0

Testing should_pass/language/contract_caller_dynamic_address
144
144
0

Testing should_pass/language/generic_result_method
652
652
0

Testing should_pass/language/local_impl_for_ord
36
36
0

Testing should_pass/language/match_expressions_inside_generic_functions
540
540
0

Testing should_pass/language/raw_ptr/vec_ret
804
764
4.97512437810945

Testing should_pass/language/raw_ptr/raw_ptr_ret
348
348
0

Testing should_pass/language/const_decl_and_use_in_library
52
52
0

Testing should_pass/language/predicate_while
68
68
0

Testing should_pass/language/test_attribute
28
28
0

Testing should_pass/language/numeric_constants
380
380
0

Testing should_pass/language/generic_impl_self
2796
3012
-7.72532188841202

Testing should_pass/language/generic_inside_generic
196
196
0

Testing should_pass/language/match_expressions
52
52
0

Testing should_pass/language/associated_const_trait_default
52
52
0

Testing should_pass/language/generic_traits
1028
1028
0

Testing should_pass/language/self_impl_reassignment
1204
1140
5.3156146179402

Testing should_pass/language/b256_ops
1064
1064
0

Testing should_pass/language/associated_const_impl_multiple
36
36
0

Testing should_pass/language/multi_impl_self
52
52
0

Testing should_pass/language/array_basics
964
964
0

Testing should_pass/language/tuple_desugaring
228
228
0

Testing should_pass/language/non_literal_const_decl
52
52
0

Testing should_pass/language/supertraits_with_trait_methods
148
148
0

Testing should_pass/language/redundant_return
36
36
0

Testing should_pass/language/nested_struct_destructuring
52
52
0

Testing should_pass/language/test_multiple_attributes
28
28
0

Testing should_pass/language/diverging_exprs
1932
1932
0

Testing should_pass/language/trait_method_qualified
260
260
0

Testing should_pass/language/new_allocator_test
820
820
0

Testing should_pass/stdlib/sha256
556
556
0

Testing should_pass/stdlib/u256_div_test
36228
14956
58.7170144639505

Testing should_pass/stdlib/result
6912
6912
0

Testing should_pass/stdlib/u128_mul_test
1380
1308
5.21739130434783

Testing should_pass/stdlib/require
36
36
0

Testing should_pass/stdlib/address_test
2184
3192
-46.1538461538462

Testing should_pass/stdlib/storage_vec_insert
1736
1944
-11.9815668202765

Testing should_pass/stdlib/eq_custom_type
804
812
-0.99502487562189

Testing should_pass/stdlib/alloc
780
780
0

Testing should_pass/stdlib/u256_ops_test
31084
14244
54.1757817526702

Testing should_pass/stdlib/if_type_revert
36
36
0

Testing should_pass/stdlib/u256_test
4892
5108
-4.41537203597711

Testing should_pass/stdlib/b512_test
2864
3432
-19.8324022346369

Testing should_pass/stdlib/assert_eq_revert
68
68
0

Testing should_pass/stdlib/option
22816
25356
-11.132538569425

Testing should_pass/stdlib/exponentiation_test
3028
3028
0

Testing should_pass/stdlib/vec
143056
121192
15.2835253327368

Testing should_pass/stdlib/vec_swap
27748
28940
-4.29580510307049

Testing should_pass/stdlib/assert_test
276
276
0

Testing should_pass/stdlib/raw_slice
572
572
0

Testing should_pass/stdlib/intrinsics
596
596
0

Testing should_pass/stdlib/ge_test
388
388
0

Testing should_pass/stdlib/u128_test
7428
6708
9.69305331179321

Testing should_pass/stdlib/contract_id_test
304
304
0

Testing should_pass/stdlib/contract_id_type
388
732
-88.659793814433

Testing should_pass/stdlib/chess
2084
2084
0

Testing should_pass/stdlib/raw_ptr
1764
1764
0

Testing should_pass/stdlib/u128_root_test
34652
6372
81.6114509984994

Testing should_pass/stdlib/logarithmic_test
1644
1644
0

Testing should_pass/stdlib/assert_eq
2188
2340
-6.94698354661792

Testing should_pass/stdlib/block_height
76
76
0

Testing should_pass/stdlib/u256_mul_test
36124
7692
78.7066770014395

Testing should_pass/stdlib/eq_generic
36
36
0

Testing should_pass/stdlib/u128_div_test
4460
3388
24.0358744394619

Testing should_pass/stdlib/u128_log_test
33908
5924
82.5291966497582

Testing should_pass/stdlib/identity_eq
6628
2332
64.8159324079662

Testing should_pass/stdlib/b512_struct_alignment
328
328
0

Testing should_pass/dca/impl_trait_single
36
36
0

Testing should_pass/dca/multiple_fns_same_name
36
36
0

Testing should_pass/dca/trait_method
36
36
0

Testing should_pass/dca/unused_trait
36
36
0

Testing should_pass/dca/trait_method_neq
116
116
0

Testing should_pass/dca/alias_lib
84
84
0

Testing should_pass/dca/trait_method_lib
28
28
0

Testing should_pass/dca/multiple_enums_same_name
36
36
0

Testing should_pass/dca/contract/unused_struct_field_array
100
100
0

Testing should_pass/dca/contract/unused_struct_field_enum
92
92
0

Testing should_pass/dca/contract/unused_struct_field
76
76
0

Testing should_pass/dca/contract/abi_fn_params
116
116
0

Testing should_pass/dca/contract/unused_struct_field_tuple
76
76
0

Testing should_pass/dca/unused_struct
36
36
0

Testing should_pass/dca/unused_free_fn
36
36
0

Testing should_pass/dca/impl_self
36
36
0

Testing should_pass/dca/unused_variable
36
36
0

Testing should_pass/dca/all_paths_return
36
36
0

Testing should_pass/dca/allow_dead_code
36
36
0

Testing should_pass/dca/log_stdlib
52
52
0

Testing should_pass/dca/impl_self_alias2
36
36
0

Testing should_pass/dca/struct_field_no_warning
44
44
0

Testing should_pass/dca/log_intrinsic
52
52
0

Testing should_pass/dca/unused_enum
36
36
0

Testing should_pass/dca/constant_struct
64
64
0

Testing should_pass/dca/impl_unused_fn
60
60
0

Testing should_pass/dca/library/fn_params_free
28
28
0

Testing should_pass/dca/library/fn_params_impl
28
28
0

Testing should_pass/dca/library/unused_priv_free_fn
28
28
0

Testing should_pass/dca/library/unused_pub_free_fn
28
28
0

Testing should_pass/dca/library/fn_params_trait
28
28
0

Testing should_pass/dca/unused_variable_in_free_fn
36
36
0

Testing should_pass/dca/generic_fn_trait_contraint
36
36
0

Testing should_pass/dca/func_param
36
36
0

Testing should_pass/dca/alias_type_ascription_generic
36
36
0

Testing should_pass/dca/alias_unused
36
36
0

Testing should_pass/dca/impl_trait_multiple
36
36
0

Testing should_pass/dca/impl_self_alias
36
36
0

Testing should_pass/dca/alias_type_ascription
36
36
0

Testing should_pass/dca/constant_decl_expr
52
52
0

Testing should_pass/dca/constant_while
36
36
0

Testing should_pass/dca/unused_fields
36
36
0

Testing should_pass/static_analysis/cei_pattern_violation_storage_var_read
524
524
0

Testing should_pass/static_analysis/cei_pattern_violation_in_intrinsic_call
260
260
0

Testing should_pass/static_analysis/cei_pattern_violation_in_tuple
260
260
0

Testing should_pass/static_analysis/cei_pattern_violation_in_asm_block
240
240
0

Testing should_pass/static_analysis/cei_pattern_violation_in_while_loop-4
260
260
0

Testing should_pass/static_analysis/cei_pattern_violation_in_asm_block_tr
332
500
-50.6024096385542

Testing should_pass/static_analysis/cei_pattern_violation_smo_intrinsic
296
296
0

Testing should_pass/static_analysis/cei_pattern_violation_more_complex_logic
8232
8276
-0.534499514091351

Testing should_pass/static_analysis/cei_pattern_violation_in_struct
260
260
0

Testing should_pass/static_analysis/cei_pattern_violation_in_asm_block_read
224
224
0

Testing should_pass/static_analysis/cei_pattern_violation_in_while_loop-2
260
260
0

Testing should_pass/static_analysis/cei_pattern_violation_in_while_loop-1
260
260
0

Testing should_pass/static_analysis/cei_pattern_violation_in_while_loop-3
260
260
0

Testing should_pass/static_analysis/cei_pattern_violation_in_func_app-1
260
260
0

Testing should_pass/static_analysis/cei_pattern_violation_in_func_app-2
260
260
0

Testing should_pass/static_analysis/cei_pattern_violation
260
260
0

Testing should_pass/static_analysis/cei_pattern_violation_in_asm_block_tro
1244
1244
0

Testing should_pass/static_analysis/cei_pattern_violation_in_func_app-3
260
260
0

Testing should_pass/static_analysis/cei_pattern_violation_in_if_statement-2
260
260
0

Testing should_pass/static_analysis/cei_pattern_violation_in_asm_block_bal
212
212
0

Testing should_pass/static_analysis/storage_annotations_unused_read
68
68
0

Testing should_pass/static_analysis/cei_pattern_violation_in_codeblocks_other_than_in_functions
260
260
0

Testing should_pass/static_analysis/cei_pattern_violation_in_asm_block_smo
220
220
0

Testing should_pass/static_analysis/cei_pattern_violation_storage_struct_read
516
516
0

Testing should_pass/static_analysis/cei_pattern_violation_storage_var_update
452
452
0

Testing should_pass/static_analysis/cei_pattern_violation_in_standalone_function
260
260
0

Testing should_pass/static_analysis/storage_annotations_unused_read_and_write
68
68
0

Testing should_pass/static_analysis/storage_annotations_unused_write
68
68
0

Testing should_pass/static_analysis/cei_pattern_violation_in_if_statement-1
284
284
0

Testing should_pass/static_analysis/cei_pattern_violation_storage_map_and_vec
2180
2300
-5.5045871559633

Testing should_pass/static_analysis/cei_pattern_violation_in_match_statement-1
452
652
-44.2477876106195

Testing should_pass/supertraits_for_abis_diamond
68
68
0

Testing should_pass/non_payable_zero_coins_let_binding
240
240
0

Testing should_pass/multiple_supertraits_for_abis
100
100
0

Testing should_pass/unit_tests/contract_with_nested_libs
164
164
0

Testing should_pass/unit_tests/script_with_nested_libs
132
132
0

Testing should_pass/unit_tests/should_revert
68
68
0

Testing should_pass/unit_tests/predicate_multi_test
204
204
0

Testing should_pass/unit_tests/lib_single_test
36
36
0

Testing should_pass/unit_tests/regalloc_spill
412
412
0

Testing should_pass/unit_tests/contract_multi_test
372
372
0

Testing should_pass/unit_tests/script_multi_test
96
96
0

Testing should_pass/unit_tests/nested_libs
124
124
0

Testing should_pass/unit_tests/stack_indexing_overflow
4140
4012
3.09178743961353

Testing should_pass/unit_tests/predicate_with_nested_libs
76
76
0

Testing should_pass/unit_tests/lib_multi_test
116
116
0

Testing should_pass/supertraits_via_self
36
36
0

Testing should_pass/test_contracts/storage_configurable
68
68
0

Testing should_pass/test_contracts/context_testing_contract
396
396
0

Testing should_pass/test_contracts/contract_with_type_aliases
172
172
0

Testing should_pass/test_contracts/basic_storage
11628
11820
-1.65118679050568

Testing should_pass/test_contracts/storage_access_contract
10916
10916
0

Testing should_pass/test_contracts/auth_testing_contract
76
76
0

Testing should_pass/test_contracts/nested_struct_args_contract
100
100
0

Testing should_pass/test_contracts/abi_with_tuples_contract
108
108
0

Testing should_pass/test_contracts/test_fuel_coin_contract
196
196
0

Testing should_pass/test_contracts/array_of_structs_contract
196
196
0

Testing should_pass/test_contracts/return_struct
304
304
0

Testing should_pass/test_contracts/abi_with_generic_types
192
192
0

Testing should_pass/test_contracts/balance_test_contract
84
84
0

Testing should_pass/test_contracts/multiple_impl
92
92
0

Testing should_pass/test_contracts/abi_with_same_name_types
112
112
0

Testing should_pass/test_contracts/issue_1512_repro
596
596
0

Testing should_pass/test_contracts/increment_contract
828
828
0

Testing should_pass/conditional_compilation/run
52
52
0

Testing should_pass/empty_fields_in_storage_struct
9872
10088
-2.18800648298217

Testing should_pass/payable_non_zero_coins
196
196
0

Testing should_pass/supertraits_for_abis
100
100
0

Testing should_pass/blanket_impl
52
52
0

This was required previously, but after the IR refactoring (#4336), this is no longer required, and actually worsens things.
Fixes #4747. For the two tests mentioned there, (both based on https://github.com/hashcloak/fuel-crypto/) the compile time now comes down from

30m -> 16s
180m -> 31s

Also fixes two bugs uncovered:

Bug in DCE - Fixes DCE eliminating ref mut storage. #4763. (1b512b8)
Bug in interaction b/w asm gen and reg alloc spiller (7a40496).

The two tests here don't compile successfully on master anymore. So I compiled them with the compiler at the time of #4722 to compare the bytecode sizes then and now with this inliner fix.

2174240 bytes -> 347348 bytes
3590472 bytes -> 653096 bytes


Plural string for 1 of thing (e.g. "1 months")

Example can be seen in your example gif

I recommend using moment to manage this for you

Hey Adam, thank you for the issue and PR!
Right now there is a token for moments timeFrom function: ${time.from}
I will look into fixing the plural/singular issue.

I just got back home and started looking into this.
Is this still an issue or is it only an issue in the demo gif?

Yeah it's currently in 1.10.0, it was just easier to use the gif to demonstrate visually

But only for months, right?
Will release a new version after some further testing.

Not just 'months'; you can see all time units have plurals here

Thanks for being persistent here. For some reason I thought it never could render with one day or one hour.

No problem 👍


NSX-T Controller is built-in NSX-T Manager

NSX-T Controller is built-in NSX-T Manager in modern NSX-T versions.
In the context, I believe the article meant NSX-T Manager anyway.

thanks


Update style.css - More space between icon and text on boxes + figures

More space here:

removed border outline from images (approved by designers @bettybondoc and @jaydenalchin )

cc @adamcogan
I expect this PR to avoid future mistaken reports like these:

https://github.com/SSWConsulting/SSW.CodeAuditor/issues/863#issuecomment-2033320805
https://github.com/SSWConsulting/SSW.CodeAuditor/issues/443#issuecomment-1538424492


style: rearrange order

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Migrating search API to json API format

This PR is to migrate the /search API to support the new JSON API format.
Supporting core PR - https://github.com/almighty/almighty-core/pull/566

Current coverage is 69.22% (diff: 20.00%)

Merging #488 into master will increase coverage by 0.05%

@@             master       #488   diff @@
==========================================
  Files            28         28
  Lines          1252       1251     -1
  Methods         269        269
  Messages          0          0
  Branches        247        247
==========================================
  Hits            866        866
+ Misses          386        385     -1
  Partials          0          0

Powered by Codecov. Last update f55f04d...227c13d


Implement identity in PostgresAdapter

Working on #2070 . Implementing IDENTITY for column in PostgresAdapter.

@MasterOdin any Chance to get this merged for 0.13? Would be great to have Support in cakephp/Migrations at some point. Thanks a Lot!

ping @ajibarra
Otherwise @swiffer you could also make a new PR from those changes and include the mentioned feedback
Then we can merge an alternative PR here as well.

@MasterOdin changes requested has been pushed. For some reason coverage has decreased. One of the issues reported is because of splitting the exception message to avoid PHP CS warning but I can't find the actual reason for the other one (L105-L106) because connect method is called for sure and that lines are executed so I am out of ideas.

@dereuromark Maybe you know?

@MasterOdin changes requested has been pushed. For some reason coverage has decreased. One of the issues reported is because of splitting the exception message to avoid PHP CS warning but I can't find the actual reason for the other one (L105-L106) because connect method is called for sure and that lines are executed so I am out of ideas.

@dereuromark Maybe you know?

The decrease in code coverage is fine. Most likely some of the formatting changes made here touch upon code that's not tested.

The decrease in code coverage is fine. Most likely some of the formatting changes made here touch upon code that's not tested.

Great then, so it is ready to be merged after approval. Thank you @MasterOdin


Create README.md

Any chance you could get rid of the "At the same time" from the differences section?  It really only made sense when it was part of the opening paragraph.

Sure.


updated apidoc build

Coverage increased (+0.03%) to 86.877% when pulling 4a17cf898ceecf6f1c97625e8120b44289ca45eb on whippit:rtd_apidoc into 02be5a49331a7529ee9caf9b072e42a2f84f8cb3 on vivisect:master.


Update to 1.6.23

Update the url, version and sha256.

Thanks very much, pulled!
For future reference, it's useful to have the name of the formula being updated in the commit/pull request title, and our preferred commit message format for version bumps is formula version, e.g. ckan 1.6.23.

Thanks for the infos.
I am not very familiar with git.
I just saw they released the 1.8.3 version a few hours ago. i will try it and make a commit tonight.


Nil point dereference when search query returns 0 results

The collector has a bug where if no repos are returned, a nil panic is given and crashes the collector.
The search query was org:liatrio archived:false topic:o11y
2024-01-23 16:15:17 2024-01-23T21:15:17.028Z    info    service@v0.92.0/service.go:177  Everything is ready. Begin running and processing data.
2024-01-23 16:15:30 panic: runtime error: invalid memory address or nil pointer dereference
2024-01-23 16:15:30 [signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x1faafb0]
2024-01-23 16:15:30
2024-01-23 16:15:30 goroutine 77 [running]:
2024-01-23 16:15:30 go.opentelemetry.io/collector/pdata/pmetric.NumberDataPoint.SetStartTimestamp(...)
2024-01-23 16:15:30     /home/runner/go/pkg/mod/go.opentelemetry.io/collector/pdata@v1.0.1/pmetric/generated_numberdatapoint.go:62
2024-01-23 16:15:30 github.com/liatrio/liatrio-otel-collector/receiver/gitproviderreceiver/internal/metadata.(*metricGitRepositoryBranchTime).recordDataPoint(0x4000154300?, 0x17ad1673004991a6, 0x17ad167554973cb2, 0xdcb, {0x4000983ae8, 0x14}, {0x4000587e00, 0xc})
2024-01-23 16:15:30     /home/runner/work/liatrio-otel-collector/liatrio-otel-collector/receiver/gitproviderreceiver/internal/metadata/generated_metrics.go:294 +0x170
2024-01-23 16:15:30 github.com/liatrio/liatrio-otel-collector/receiver/gitproviderreceiver/internal/metadata.(*MetricsBuilder).RecordGitRepositoryBranchTimeDataPoint(...)
2024-01-23 16:15:30     /home/runner/work/liatrio-otel-collector/liatrio-otel-collector/receiver/gitproviderreceiver/internal/metadata/generated_metrics.go:858
2024-01-23 16:15:30 github.com/liatrio/liatrio-otel-collector/receiver/gitproviderreceiver/internal/scraper/githubscraper.(*githubScraper).scrape.func1()
2024-01-23 16:15:30     /home/runner/work/liatrio-otel-collector/liatrio-otel-collector/receiver/gitproviderreceiver/internal/scraper/githubscraper/github_scraper.go:132 +0x5c4
2024-01-23 16:15:30 created by github.com/liatrio/liatrio-otel-collector/receiver/gitproviderreceiver/internal/scraper/githubscraper.(*githubScraper).scrape in goroutine 95
2024-01-23 16:15:30     /home/runner/work/liatrio-otel-collector/liatrio-otel-collector/receiver/gitproviderreceiver/internal/scraper/githubscraper/github_scraper.go:102 +0x7a8

This has been resolved from some other commit and is no longer an issue.


Support BIOS updates for devices that have different BIOS families?

Most of the devices have a single BIOS family, so BIOS-Update.txt does not allow to specify a firmware family and instead just starts the update process in the hope the Update EXE is smart enough to figure out which ROM file to use.
At least for the ProBook 6570b, this fails. This device has two separate BIOS families and the firmware update requires the file to be named ROM.CAB if no firmware parameter is given.
Right now the only solution is to rename one of the files to ROM.CAB and hope for the best.
Given that BIOS Sledgehammer has the BIOS family already, the question is if BIOS updates should support to define a firmware update file and then throw it at the Update EXE.

Supported with v2.44


Update Composer dependencies (2023-04-29-00-10)

Visual regression test passed!
View the visual regression test report


Faster startup and less memory consumption in integration tests

Adding -XX:TieredStopAtLevel=1 has similar effect with obsoleted -client
option. -Xverify:none simply skips validation of jar files and makes
startup of JVM faster.
This might mitigate the problem described at #624.

1 hour 07 minutes became 56 minutes. 17% improved
https://circleci.com/gh/treasure-data/digdag

Interesting. Let's try it and see what happens.


Make ui.image collisions limited to image width

Right now collisions are limited to the height of the element; Zui never considers the width of an image when detecting clicks. This addresses the issue.
Since the way Zui handles input is related to the window width and the element heigth, it may be interesting in the future to have a better way to limit the collisions of elements on the x axis i.e. by having an endElementX().
If this is something that would be desired I may look into it.
One of the situations where the collisions are faulty is for example when we have tooltips for tabs. the tooltip will appear for the whole window instead of just on hover of the Tab.

Hm, it was intended to work that way so you can do a grid of images using ui.row() and then clicking on any individual cell will register as image click, regardless of image aspect ratio. Maybe we can enable both behaviors somehow?
Right now the input handling is related to window width as you mention but after doing ui.row() the input handling is restricted to that area instead.
Basically zui operates under the currently defined area, and then it's up to the individual element on how the space is utilized. So for example when using a checkbox, it's enough to click anywhere in the area, not necessarily onto the check mark (or even the label) itself. Unfortunately in the case of displaying an image with non 1:1 aspect ratio it can be problematic.

Just added the fix needed to support both. Was pretty straightforward.
FYI I found a bug with image grids. will file a bug report.
If you want to test the fix and see the issue here is a test project: https://github.com/mundusnine/zui-image-grid-test
clone recursively.
Good day :)

Sweet! Is the _windowX > inputX also needed? Or perhaps it's _windowX + _x > inputX?

Sweet! Is the _windowX > inputX also needed? Or perhaps it's _windowX + _x > inputX?

Just added the _x; nice spot ! :)

Thanks!


Model Training

Can you share your code for model training?

  I followed the steps in the documentation to reproduce the results but couldn't segment the cells. Could you help me and give me the complete code? This will be of great help to my scientific research. I'm looking forward to hearing back from you.


Update to FreeBSD 12.2

https://www.freebsd.org/releases/12.2R/announce.html

@JohnTitor: no appropriate reviewer found, use r? to override

@bors r+

:pushpin: Commit b9bf6d1faac705794928566b4e349fb9eb1916e6 has been approved by JohnTitor

:hourglass: Testing commit b9bf6d1faac705794928566b4e349fb9eb1916e6 with merge 4c0a7e5b7ca949088a0ba17784fb043a22e4537e...

:sunny: Test successful - checks-actions, checks-cirrus-freebsd-11, checks-cirrus-freebsd-12, checks-cirrus-freebsd-13
Approved by: JohnTitor
Pushing 4c0a7e5b7ca949088a0ba17784fb043a22e4537e to master...


Moved: Vivaldi.Vivaldi version 4.1.2369.21

This pull request is automatically generated by 🥟 Dumplings
Microsoft Reviewers: Open in CodeFlow

/AzurePipelines run

@wingetbot run

/AzurePipelines run


Kirby 3: template settings override defaults instead of being merged

With the Kirby 3 plugin, there seems to be a difference in how template settings are combined with default settings.
Consider:
c::set('pedroborges.metatags.default', function($page, $site) {
  return [
    'og' => [
      'title' => $page->metatitle(),
      'type' => 'website',
      'site_name' => $site->title(),
      'url' => $page->url(),
      'description' => $page->metadescription(),
      'locale' => explode('.', kirby()->language()->locale())[0],
      'namespace:image' => [...],
    ],
  ];
});

Coupled with:
c::set('pedroborges.metatags.templates', function($page) {
  return [
    'project' => [
      'og' => [
        'namespace:image' => [...],
      ],
    ],
  ];
});

The og tags on a page with a template project contains only those defined in the templates settings, not the defaults.
With the Kirby 2 version, the template specific settings used to be merged with the default. Now they seems to simply replace them.

Thank you for the huge contribution @LeBenLeBen! Just merged you PRs.

@pedroborges Thank you for your time reviewing and releasing 2.0, much appreciated 🙇

You are welcome.
I have changed the option name to match the one used in v1.1.1 (with a dash). Update it your config after upgrading:

pedroborges.meta-tags.default
pedroborges.meta-tags.templates


Postgresql 14 support

Hi,
Trying to build clickhouse_fdw 1.3.0 against postgresql-14 I get the following error.
Could someone please have a look?
[root@archimedes build]# cmake ..
-- The C compiler identification is GNU 8.3.1
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /opt/rh/devtoolset-8/root/usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Setting clickhouse_fdw build type -
-- The CXX compiler identification is GNU 8.3.1
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /opt/rh/devtoolset-8/root/usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found PkgConfig: /bin/pkg-config (found version "0.27.1")
-- Checking for module 'libcurl'
--   Found libcurl, version 7.43.0
-- Checking for module 'uuid'
--   Found uuid, version 2.23.0
-- Configuring done
-- Generating done
-- Build files have been written to: /root/software/clickhouse_fdw-1.3.0/build
[root@archimedes build]# make
[  1%] Building C object src/clickhouse-cpp/contrib/lz4/CMakeFiles/lz4-lib.dir/lz4.c.o
[  2%] Building C object src/clickhouse-cpp/contrib/lz4/CMakeFiles/lz4-lib.dir/lz4hc.c.o
[  4%] Linking C static library liblz4-lib.a
[  4%] Built target lz4-lib
[  5%] Generating ../clickhouse_fdw--1.3.sql
[  5%] Built target clickhouse_fdw_sql
[  7%] Building CXX object src/clickhouse-cpp/contrib/cityhash/CMakeFiles/cityhash-lib.dir/city.cc.o
[  8%] Linking CXX static library libcityhash-lib.a
[  8%] Built target cityhash-lib
[ 10%] Building CXX object src/clickhouse-cpp/clickhouse/CMakeFiles/clickhouse-cpp-lib-static.dir/base/coded.cpp.o
[ 11%] Building CXX object src/clickhouse-cpp/clickhouse/CMakeFiles/clickhouse-cpp-lib-static.dir/base/compressed.cpp.o
[ 12%] Building CXX object src/clickhouse-cpp/clickhouse/CMakeFiles/clickhouse-cpp-lib-static.dir/base/input.cpp.o
[ 14%] Building CXX object src/clickhouse-cpp/clickhouse/CMakeFiles/clickhouse-cpp-lib-static.dir/base/output.cpp.o
[ 15%] Building CXX object src/clickhouse-cpp/clickhouse/CMakeFiles/clickhouse-cpp-lib-static.dir/base/platform.cpp.o
[ 17%] Building CXX object src/clickhouse-cpp/clickhouse/CMakeFiles/clickhouse-cpp-lib-static.dir/base/socket.cpp.o
[ 18%] Building CXX object src/clickhouse-cpp/clickhouse/CMakeFiles/clickhouse-cpp-lib-static.dir/columns/array.cpp.o
[ 20%] Building CXX object src/clickhouse-cpp/clickhouse/CMakeFiles/clickhouse-cpp-lib-static.dir/columns/date.cpp.o
[ 21%] Building CXX object src/clickhouse-cpp/clickhouse/CMakeFiles/clickhouse-cpp-lib-static.dir/columns/decimal.cpp.o
[ 22%] Building CXX object src/clickhouse-cpp/clickhouse/CMakeFiles/clickhouse-cpp-lib-static.dir/columns/enum.cpp.o
[ 24%] Building CXX object src/clickhouse-cpp/clickhouse/CMakeFiles/clickhouse-cpp-lib-static.dir/columns/factory.cpp.o
[ 25%] Building CXX object src/clickhouse-cpp/clickhouse/CMakeFiles/clickhouse-cpp-lib-static.dir/columns/ip4.cpp.o
[ 27%] Building CXX object src/clickhouse-cpp/clickhouse/CMakeFiles/clickhouse-cpp-lib-static.dir/columns/ip6.cpp.o
[ 28%] Building CXX object src/clickhouse-cpp/clickhouse/CMakeFiles/clickhouse-cpp-lib-static.dir/columns/lowcardinality.cpp.o
[ 30%] Building CXX object src/clickhouse-cpp/clickhouse/CMakeFiles/clickhouse-cpp-lib-static.dir/columns/nullable.cpp.o
[ 31%] Building CXX object src/clickhouse-cpp/clickhouse/CMakeFiles/clickhouse-cpp-lib-static.dir/columns/numeric.cpp.o
[ 32%] Building CXX object src/clickhouse-cpp/clickhouse/CMakeFiles/clickhouse-cpp-lib-static.dir/columns/string.cpp.o
[ 34%] Building CXX object src/clickhouse-cpp/clickhouse/CMakeFiles/clickhouse-cpp-lib-static.dir/columns/tuple.cpp.o
[ 35%] Building CXX object src/clickhouse-cpp/clickhouse/CMakeFiles/clickhouse-cpp-lib-static.dir/columns/uuid.cpp.o
[ 37%] Building CXX object src/clickhouse-cpp/clickhouse/CMakeFiles/clickhouse-cpp-lib-static.dir/columns/itemview.cpp.o
[ 38%] Building CXX object src/clickhouse-cpp/clickhouse/CMakeFiles/clickhouse-cpp-lib-static.dir/types/type_parser.cpp.o
[ 40%] Building CXX object src/clickhouse-cpp/clickhouse/CMakeFiles/clickhouse-cpp-lib-static.dir/types/types.cpp.o
[ 41%] Building CXX object src/clickhouse-cpp/clickhouse/CMakeFiles/clickhouse-cpp-lib-static.dir/block.cpp.o
[ 42%] Building CXX object src/clickhouse-cpp/clickhouse/CMakeFiles/clickhouse-cpp-lib-static.dir/client.cpp.o
[ 44%] Building CXX object src/clickhouse-cpp/clickhouse/CMakeFiles/clickhouse-cpp-lib-static.dir/query.cpp.o
[ 45%] Linking CXX static library libclickhouse-cpp-lib-static.a
[ 45%] Built target clickhouse-cpp-lib-static
[ 47%] Building C object src/CMakeFiles/clickhouse_fdw.dir/clickhouse_fdw.c.o
/root/software/clickhouse_fdw-1.3.0/src/clickhouse_fdw.c: In function ‘clickhouseBeginForeignModify’:
/root/software/clickhouse_fdw-1.3.0/src/clickhouse_fdw.c:1119:43: error: ‘ModifyTableState’ {aka ‘struct ModifyTableState’} has no member named ‘mt_plans’; did you mean ‘mt_done’?
                                  mtstate->mt_plans[subplan_index]->plan,
                                           ^~~~~~~~
                                           mt_done
/root/software/clickhouse_fdw-1.3.0/src/clickhouse_fdw.c: In function ‘foreign_grouping_ok’:
/root/software/clickhouse_fdw-1.3.0/src/clickhouse_fdw.c:2159:30: warning: passing argument 1 of ‘make_restrictinfo’ from incompatible pointer type [-Wincompatible-pointer-types]
    rinfo = make_restrictinfo(expr,
                              ^~~~
In file included from /root/software/clickhouse_fdw-1.3.0/src/clickhouse_fdw.c:32:
/usr/pgsql-14/include/server/optimizer/restrictinfo.h:24:22: note: expected ‘PlannerInfo *’ {aka ‘struct PlannerInfo *’} but argument is of type ‘Expr *’ {aka ‘struct Expr *’}
 extern RestrictInfo *make_restrictinfo(PlannerInfo *root,
                      ^~~~~~~~~~~~~~~~~
/root/software/clickhouse_fdw-1.3.0/src/clickhouse_fdw.c:2160:12: warning: passing argument 2 of ‘make_restrictinfo’ makes pointer from integer without a cast [-Wint-conversion]
            true,
            ^~~~
In file included from /root/software/clickhouse_fdw-1.3.0/src/clickhouse_fdw.c:32:
/usr/pgsql-14/include/server/optimizer/restrictinfo.h:24:22: note: expected ‘Expr *’ {aka ‘struct Expr *’} but argument is of type ‘int’
 extern RestrictInfo *make_restrictinfo(PlannerInfo *root,
                      ^~~~~~~~~~~~~~~~~
/root/software/clickhouse_fdw-1.3.0/src/clickhouse_fdw.c:2164:23: warning: passing argument 6 of ‘make_restrictinfo’ makes integer from pointer without a cast [-Wint-conversion]
            grouped_rel->relids,
            ~~~~~~~~~~~^~~~~~~~
In file included from /root/software/clickhouse_fdw-1.3.0/src/clickhouse_fdw.c:32:
/usr/pgsql-14/include/server/optimizer/restrictinfo.h:24:22: note: expected ‘Index’ {aka ‘unsigned int’} but argument is of type ‘Relids’ {aka ‘struct Bitmapset *’}
 extern RestrictInfo *make_restrictinfo(PlannerInfo *root,
                      ^~~~~~~~~~~~~~~~~
/root/software/clickhouse_fdw-1.3.0/src/clickhouse_fdw.c:2159:12: error: too few arguments to function ‘make_restrictinfo’
    rinfo = make_restrictinfo(expr,
            ^~~~~~~~~~~~~~~~~
In file included from /root/software/clickhouse_fdw-1.3.0/src/clickhouse_fdw.c:32:
/usr/pgsql-14/include/server/optimizer/restrictinfo.h:24:22: note: declared here
 extern RestrictInfo *make_restrictinfo(PlannerInfo *root,
                      ^~~~~~~~~~~~~~~~~
make[2]: *** [src/CMakeFiles/clickhouse_fdw.dir/build.make:76: src/CMakeFiles/clickhouse_fdw.dir/clickhouse_fdw.c.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:200: src/CMakeFiles/clickhouse_fdw.dir/all] Error 2
make: *** [Makefile:136: all] Error 2

Using CentOS 7, scl enable devtoolset-8 and postgresql-14 from official pgdg repo.
[root@archimedes build]# pg_config
BINDIR = /usr/pgsql-14/bin
DOCDIR = /usr/pgsql-14/doc
HTMLDIR = /usr/pgsql-14/doc/html
INCLUDEDIR = /usr/pgsql-14/include
PKGINCLUDEDIR = /usr/pgsql-14/include
INCLUDEDIR-SERVER = /usr/pgsql-14/include/server
LIBDIR = /usr/pgsql-14/lib
PKGLIBDIR = /usr/pgsql-14/lib
LOCALEDIR = /usr/pgsql-14/share/locale
MANDIR = /usr/pgsql-14/share/man
SHAREDIR = /usr/pgsql-14/share
SYSCONFDIR = /etc/sysconfig/pgsql
PGXS = /usr/pgsql-14/lib/pgxs/src/makefiles/pgxs.mk
CONFIGURE =  '--enable-rpath' '--prefix=/usr/pgsql-14' '--includedir=/usr/pgsql-14/include' '--mandir=/usr/pgsql-14/share/man' '--datadir=/usr/pgsql-14/share' '--libdir=/usr/pgsql-14/lib' '--with-lz4' '--with-icu' '--with-llvm' '--with-perl' '--with-python' '--with-tcl' '--with-tclconfig=/usr/lib64' '--with-openssl' '--with-pam' '--with-gssapi' '--with-includes=/usr/include' '--with-libraries=/usr/lib64' '--enable-nls' '--enable-dtrace' '--with-uuid=e2fs' '--with-libxml' '--with-libxslt' '--with-ldap' '--with-selinux' '--with-systemd' '--with-system-tzdata=/usr/share/zoneinfo' '--sysconfdir=/etc/sysconfig/pgsql' '--docdir=/usr/pgsql-14/doc' '--htmldir=/usr/pgsql-14/doc/html' 'CFLAGS=-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches   -m64 -mtune=generic' 'LLVM_CONFIG=/usr/lib64/llvm5.0/bin/llvm-config' 'CLANG=/opt/rh/llvm-toolset-7/root/usr/bin/clang' 'PKG_CONFIG_PATH=:/usr/lib64/pkgconfig:/usr/share/pkgconfig' 'PYTHON=/usr/bin/python3'
CC = gcc -std=gnu99
CPPFLAGS = -D_GNU_SOURCE -I/usr/include/libxml2 -I/usr/include
CFLAGS = -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Werror=vla -Wendif-labels -Wmissing-format-attribute -Wformat-security -fno-strict-aliasing -fwrapv -fexcess-precision=standard -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches   -m64 -mtune=generic
CFLAGS_SL = -fPIC
LDFLAGS = -L/usr/lib64/llvm5.0/lib -L/usr/lib64 -Wl,--as-needed -Wl,-rpath,'/usr/pgsql-14/lib',--enable-new-dtags
LDFLAGS_EX =
LDFLAGS_SL =
LIBS = -lpgcommon -lpgport -lselinux -llz4 -lxslt -lxml2 -lpam -lssl -lcrypto -lgssapi_krb5 -lz -lreadline -lpthread -lrt -ldl -lm
VERSION = PostgreSQL 14.1

The same problem

Supported PostgreSQL Versions
PostgreSQL 11-13

Supported PostgreSQL Versions
PostgreSQL 11-13

We know, but postgresql-14 has benefits that we'd like to take advantage of, but we also need clickhouse_fdw ...

Closing this issue, https://github.com/adjust/clickhouse_fdw/pull/79 has been merged :-)


@ should show or not be needed in function expressions

Currently, when a user enters a function expression, they need to precede field references with an @. However, once they field is selected, the @ symbol is no longer shown. This is confusing in that it makes it appear as if field names can be entered without the @. We should either always show the @ symbol or remove its necessity, allowing the automatic distinction between field and function (e.g., IF, ISEMPTY) names based on whether names are followed by a left parenthesis.

We can't really wait until the user types a '(' to determine that the previous name is a field name.  We need to present the dropdown  select menu so they can select the actual field if the same name is used in different subfolders.  We use the '@' to trigger the select menu and then decorate the field by using a bold font (and dropping the '@' as superfluous).

I fully agree with your first statement. As with almost any other tool with content assist, including our own IDEs, I'd argue the established user expectation is as soon as a character is pressed, a content assist menu would offer all possibilities based upon what has been typed. Thus, if 'if' were quickly typed, the content menu would show both all functions that contain 'if', along with a separator and all fields that contain 'if'. There is nothing to tell the user to type an '@' to begin with, and it's misleading when existing field name don't show an '@' was required. It appears as if just typing the name should suffice, which I'd argue is exactly what we should provide.

Showing @ permanently for field reference is confusing for me. We are using it as a temporary control character to trigger field auto completion. We should show the established field as a label instead.

I'm actually advocating to not show it at all. Auto-completion should just be based on the user typing characters, as I explained above. The need to type the @ sign and not showing it is a significant usability issue I believe. Do you mind if I get feedback from the UX team?

@amysueg Would there be someone from the UX team that could weigh in on this?

Is it possible for me to actually try this out somewhere @jpav @pleacu ? Not sure I'm getting the nuance the way I would with a hands-on experience.

wget https://repo1.maven.org/maven2/io/atlasmap/atlasmap-standalone/2.1.5/atlasmap-standalone-2.1.5.jar
java -jar ./atlasmap-standalone-2.1.5.jar

In your favorite browser...
http://localhost:8585/

In AtlasMap - download a source and target document, i.e.
wget https://raw.githubusercontent.com/atlasmap/atlasmap/master/ui/test-resources/json/schema/mock-json-schema.json

On the Source panel - import ./mock-json-schema.json

On the Target panel - import ./mock-json-schema.json

Create a mapping from primitives/stringPrimitive to primitives/stringPrimitive (as an example)

Select the f(x) button in the conditional mapping expression box (top left)

Within the expression box - type  + @.  You'll see a drop-down menu appear with all selectable fields.  In the example - I select  addressList<>/state.  Once selected - state appears in bold font within the expression to identify that it is a field.
The issue is that entering the @ character is the method we've chosen for the user to add fields to the expression box.  The UI relies on the runtime to parse the expression and consequently has no context.  The @ is the method we used in the old angular UI.  Since entering one character would trigger the drop-down I would find it confusing since expression characters for IF, ISEMPTY for example or for built-in functions lcase would cause a drop-down to appear.
My opinion is to not show the @ permanently and to keep it as our way of indicating the user is asking for a field, not a function.  If I want to lowercase and I type lca I don't want auto-complete to find all of my fields that start with lca and having a separate add function button would be confusing.

@pleacu I'm sorry if I misconstrued, but I'm not suggesting to have a separate button to add content, be it functions or fields. The functionality of the f(x) button itself is a separate concern, but like this issue, I would expect it to act as that button does in all other popular spreadsheets with this functionality. That aside, typing 'lca' and getting a dropdown showing all constructs that begin with 'lca', be they fields or functions, is exactly what the expectation would be of the user. This isn't just me throwing that out there, but is well established is almost all tools that provide some sort of content assist, be it spreadsheets like Microsoft Excel, Apple Numbers, and Google Sheets, or tools like our IDE's, like Eclipse, VS Code, etc. This type of behaviors has become the defacto standard for users, and thus now matches the user's mental model. Expecting the user to type an '@' when there is no indication in AtlasMap that that is required, especially given we don't show it for existing field references, is definitely going to confuse users. We have to pick one way or the other, either require it and show it, or don't require it (as content assist should be sufficient) and don't ever show it. Trying to require it and not showing it just not user-friendly and contradicts established expectations, for both developers and citizen users.


Read principal Pole Emploi (pe) file

[x] Setup CLI environnement
[x] Read CSV file using Dask
[x] Add tests for CSV parsing
[x] Read Code Rome
[x] Load Code Rome into DB
[x] Add test for DB operations

:tada: This PR is included in version 1.111.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Capture Patient Race as an entension

Describe the bug
Create FHIR Patient.extension.patient-race (well-known extension) from PID-10.1
To Reproduce
Create a sample HL7V2.6 patient PID segment with aforementioned patient information.
Expected behavior
Patient information should be detected and added to corresponding fields in HL7 FHIR resources.
Example FHIR:
extension": [{
        "url": "http://ibm.com/fhir/cdm/StructureDefinition/local-race-cd",
        "valueCodeableConcept": {
          "coding": [ {
            "system": "http://terminology.hl7.org/CodeSystem/v3-Race",
            "code": "2028-9",
            "display": "Asian"
          } ],
          "text": "Asian"
        }
      }, {
        "url": "http://ibm.com/fhir/cdm/StructureDefinition/local-race-cd",
        "valueCodeableConcept": {
          "coding": [ {
            "system": "http://terminology.hl7.org/CodeSystem/v3-Race",
            "code": "2106-3",
            "display": "White"
          } ],
          "text": "White"
        }
      }
]

Additional context
HL7 FHIR Site
Sample results

The expected coding has been changed.  The request has been updated.

If the HL7V2 is degenerate and has no coding but only text (happens quite a bit), we interpret that as a code without a coding thus:
{
        "url": "http://ibm.com/fhir/cdm/StructureDefinition/local-race-cd",
        "valueCodeableConcept": {
          "coding": [ {
            "code": "W"
          } ]
        }
      }

In Release 1.0.9