dnscrypt-proxy v1.9.3 doesn't work with dnscrypt-loader

I've installed / upgraded dnscrypt-proxy, using dnscrypt-loader, using these instructions. dnscrypt-proxy and dnscrypt-loader do not start anymore.
The syslog messages are:
Jan 19 10:06:06 raspberrypi dnscrypt-loader: The path to resolvers.csv on dnscrypt-loader script
Jan 19 10:06:06 raspberrypi dnscrypt-loader: differs from dnscrypt-proxy setup
Jan 19 10:06:06 raspberrypi dnscrypt-loader: Please change dnscrypt-loader 'cCSVBaseDir' and 'cSIGBaseDir' parameters to
Jan 19 10:06:06 raspberrypi dnscrypt-loader: cCSVBaseDir='/'
Jan 19 10:06:06 raspberrypi dnscrypt-loader: cSIGBaseDir='/'
Jan 19 10:06:06 raspberrypi dnscrypt-loader: Edit script at /usr/local/sbin/dnscrypt-loader
Changing the parameters, as indicated by this message doesn't solve the problem...
the resolver.csv files are in /usr/local/share/dnscrypt-proxy, this path matches the configuration in the (unchanged) dnscrypt-loader configuration file (/usr/local/sbin/dnscrypt-loader)

Hello jpgpi250
To try to resolve the problem,
match the paths defined in the parameters with the path where dnscrypt-proxy and resolvers.csv were saved.
Using whereis and find commands examples:
$ whereis dnscrypt-proxy
dnscrypt-proxy: /usr/local/sbin/dnscrypt-proxy
Set cProxyBaseDir to:
cProxyBaseDir="/usr/local/sbin/"
$ find / -name dnscrypt-resolvers.csv
/usr/local/share/dnscrypt-proxy/dnscrypt-resolvers.csv
Set cCSVBaseDir and cSIGBaseDir to:
cCSVBaseDir="/usr/local/share/dnscrypt-proxy/"
cSIGBaseDir="/usr/local/share/dnscrypt-proxy/"
Thanks for reporting this issue.

I've checked the configuration paths, they match
system info 2016-11-25-raspbian-jessie-lite, running on raspberry pi 3 model B
when trying to start dnscrypt-loader, this is the output:
sudo dnscrypt-loader
Thu Jan 19 14:26:46 2017 [ERROR] Error: no resolver name given, no configuration file either.
Thu Jan 19 14:26:46 2017 [ERROR] The easiest way to get started is to edit the example configuration file
Thu Jan 19 14:26:46 2017 [ERROR] and to append the full path to that file to the dnscrypt-proxy command.
Thu Jan 19 14:26:46 2017 [ERROR] Example: dnscrypt-proxy /usr/local/etc/dnscrypt-proxy.conf
Thu Jan 19 14:26:46 2017 [ERROR] The local list of public resolvers is loaded from: [/usr/local/share/dnscrypt-proxy/dnscrypt-resolvers.csv]
Thu Jan 19 14:26:46 2017 [ERROR] Consult https://dnscrypt.org for more information about dnscrypt-proxy.
dirname: missing operand
Try 'dirname --help' for more information.
The path to resolvers.csv on dnscrypt-loader script
differs from dnscrypt-proxy setup
Please change dnscrypt-loader 'cCSVBaseDir' and 'cSIGBaseDir' parameters to
cCSVBaseDir='/'
cSIGBaseDir='/'
Edit script at /usr/local/sbin/dnscrypt-loader

Run this command please
dnscrypt-proxy | awk  '/resolvers.csv/ NR>1 {print $1}' RS=[ FS=]

result:
Thu Jan 19 15:37:04 2017 [WARNING] This system doesn't provide enough entropy to quickly generate high-quality random numbers
Thu Jan 19 15:37:04 2017 [WARNING] Installing the rng-utils/rng-tools or haveged packages may help.
Thu Jan 19 15:37:04 2017 [WARNING] On virtualized Linux environments, also consider using virtio-rng.
Thu Jan 19 15:37:04 2017 [WARNING] The service will not start until enough entropy has been collected.
Thu Jan 19 15:37:04 2017 [ERROR] Error: no resolver name given, no configuration file either.
Thu Jan 19 15:37:04 2017 [ERROR] The easiest way to get started is to edit the example configuration file
Thu Jan 19 15:37:04 2017 [ERROR] and to append the full path to that file to the dnscrypt-proxy command.
Thu Jan 19 15:37:04 2017 [ERROR] Example: dnscrypt-proxy /usr/local/etc/dnscrypt-proxy.conf
Thu Jan 19 15:37:04 2017 [ERROR] The local list of public resolvers is loaded from: [/usr/local/share/dnscrypt-proxy/dnscrypt-resolvers.csv]
Thu Jan 19 15:37:04 2017 [ERROR] Consult https://dnscrypt.org for more information about dnscrypt-proxy.

I noticed there is no longer a dnscrypt-proxy.conf file in /usr/local/etc
I've copied my backup configuration file in that location (from dnscrypt v1.9.1)
rebooted the system, the result (and output) are the same

Ok, I'll need some time to investigate and fix (ASAP) this incompatibility See the message Frank Denis posted. Upgrading is unnecessary except if you use musl libc.

just letting you know that v1.9.2 has the same problem. The last known good version is 1.9.1

Thank, I'll simulate with each version to correct the errors.

Same here on Ubuntu.

Any update on this issue?

Me too, the same problem, dnscrypt-loader v1.2 and dnscrypt-proxy v1.9.4 on raspberry pi raspbian jessie.


Check support of epoll EPOLLEXCLUSIVE

TiKV has switched to gRPC event epollex which requires the underlying linux supports epoll EPOLLEXCLUSIVE. TiDB Ansible should check it before depolying.
Here is a simple programm that checks the EPOLLEXCLUSIVE.
/*
 *
 * Copyright 2017 gRPC authors.
 *
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *     http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 *
 */

#include <errno.h>
#include <sys/eventfd.h>
#include <sys/epoll.h>
#include <unistd.h>
#include <stdio.h>

#ifndef EPOLLEXCLUSIVE
#define EPOLLEXCLUSIVE (1 << 28)
#endif

/* This polling engine is only relevant on linux kernels supporting epoll() */
bool grpc_is_epollexclusive_available(void) {
  static bool logged_why_not = false;

  int fd = epoll_create1(EPOLL_CLOEXEC);
  if (fd < 0) {
    if (!logged_why_not) {
      printf(
              "epoll_create1 failed with error: %d. Not using epollex polling "
              "engine.",
              fd);
      logged_why_not = true;
    }
    return false;
  }
  int evfd = eventfd(0, EFD_NONBLOCK | EFD_CLOEXEC);
  if (evfd < 0) {
    if (!logged_why_not) {
      printf(
              "eventfd failed with error: %d. Not using epollex polling "
              "engine.",
              fd);
      logged_why_not = true;
    }
    close(fd);
    return false;
  }
  struct epoll_event ev;
  /* choose events that should cause an error on
     EPOLLEXCLUSIVE enabled kernels - specifically the combination of
     EPOLLONESHOT and EPOLLEXCLUSIVE */
  ev.events = (uint32_t)(EPOLLET | EPOLLIN | EPOLLEXCLUSIVE | EPOLLONESHOT);
  ev.data.ptr = NULL;
  if (epoll_ctl(fd, EPOLL_CTL_ADD, evfd, &ev) != 0) {
    if (errno != EINVAL) {
      if (!logged_why_not) {
        printf(
            "epoll_ctl with EPOLLEXCLUSIVE | EPOLLONESHOT failed with error: "
            "%d. Not using epollex polling engine.",
            errno);
        logged_why_not = true;
      }
      close(fd);
      close(evfd);
      return false;
    }
  } else {
    if (!logged_why_not) {
      printf(
              "epoll_ctl with EPOLLEXCLUSIVE | EPOLLONESHOT succeeded. This is "
              "evidence of no EPOLLEXCLUSIVE support. Not using "
              "epollex polling engine.");
      logged_why_not = true;
    }
    close(fd);
    close(evfd);
    return false;
  }
  close(evfd);
  close(fd);
  return true;
}

int main() {
    if (grpc_is_epollexclusive_available()) {
        printf("epollexclusive is available\n");
        return 0;
    } else {
        printf("epollexclusive is NOT available\n");
        return 1;
    }
}

Compile: gcc -static-libstdc++ -std=c++11 epoll_chk.cc
Cc https://github.com/tikv/tikv/pull/4028

Closed via #663


Don't fail PR check on minor reduction in coverage

The reduced coverage is visible enough in the PR. Failing the check is just annoying.

Should hopefully be resolved by #123


XML Notepad version <IP_ADDRESS>

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

All manifest files should be under leaf directory.

This PR appears to modify more than one manifest.

woops how did that happen.


Enable hanging punctuation in body text

Current appearance:

Look at that paragraph that starts with a double quote. That doesn’t look very nice. Booooo.
This is what I see if I add hanging-punctuation: first to the style of p:

All the words form a nice left edge. Doesn’t that look much nicer?
I suggest enabling this on all body text.

This is going to be a lot of effort and too fiddly to fix in a way that works across all browsers.


Bump to v0.9.10

https://github.com/romanz/electrs/releases/tag/v0.9.10
Release Notes: https://github.com/romanz/electrs/blob/master/RELEASE-NOTES.md#0910-nov-3-2022

Tagging @mayankchhabra and @nevets963 for review...


⚠ Bofrost.de has degraded performance

In d66c3e7, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1014 ms

Resolved: Bofrost.de performance has improved in 77618c1 after 19 minutes.


Flutter/Dart Upgrade

@emmett-deen I didn't see the Flutter version set anywhere for builds. Does it use the latest version? Or is it set somewhere externally?
This PR includes the following-

Bump to Dart 3.0
Updated packages
Migrated deprecated code
Added VS Code launch json

Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I added new tests to check the change I am making or feature I am adding, or the PR is test-exempt.
[x] All existing and new tests are passing.

I don't know what happened to my CICD pipeline to deploy this, but I will get one set up again.


[$rootScope:infdig] and multiple http calls when using with angular 1.4.8

I can't seem to use ui-calendar with angular 1.4.8. It causes an error in the log, calls the eventSource multiple times and also adds the events to often to the calendar.
I created a jsfiddle showing the issue:
https://jsfiddle.net/0gb2cd96/2/
The error log is:
Error: [$rootScope:infdig] http://errors.angularjs.org/1.4.8/$rootScope/infdig?p0=10&p1=%5B%5B%7B%22ms…urn%20g%7D%22%2C%22newVal%22%3A%5B20%5D%2C%22oldVal%22%3A%5B18%5D%7D%5D%5D
    at Error (native)
    at https://cdnjs.cloudflare.com/ajax/libs/angular.js/1.4.8/angular.min.js:6:416
    at r.$digest (https://cdnjs.cloudflare.com/ajax/libs/angular.js/1.4.8/angular.min.js:131:499)
    at r.$apply (https://cdnjs.cloudflare.com/ajax/libs/angular.js/1.4.8/angular.min.js:134:78)
    at https://cdnjs.cloudflare.com/ajax/libs/angular.js/1.4.8/angular.min.js:20:59
    at Object.e [as invoke] (https://cdnjs.cloudflare.com/ajax/libs/angular.js/1.4.8/angular.min.js:39:394)
    at c (https://cdnjs.cloudflare.com/ajax/libs/angular.js/1.4.8/angular.min.js:19:482)
    at yc (https://cdnjs.cloudflare.com/ajax/libs/angular.js/1.4.8/angular.min.js:20:274)
    at Zd (https://cdnjs.cloudflare.com/ajax/libs/angular.js/1.4.8/angular.min.js:19:83)
    at HTMLDocument.<anonymous> (https://cdnjs.cloudflare.com/ajax/libs/angular.js/1.4.8/angular.min.js:294:192)

I have some problem
Please tell me solution, if you resolve this.


Apply Equinix TF Modules examples/ conventions (using existing samples)

Apply Equinix TF Modules examples/ conventions (using existing samples). (for more on the conventions, see https://github.com/equinix-labs/equinix-labs/blob/main/terraform-modules.md -- not all applied in this PR).
Continues #63

If not in this PR, than in a successor, the provider definition should move into the examples/ and the README.md should give instruction to run the project from the examples.


Add last_update files to blog posts

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Description
Implement blog page last updated time.
Has this been requested on Canny?
No response
Motivation
Blog like a docs require updates, may be typo fixes, or often API changes of product for examples, or some new announcements
API design
Like a PR for docs: https://github.com/facebook/docusaurus/pull/7461
Have you tried building it?
No response
Self-service

[ ] I'd be willing to contribute this feature to Docusaurus myself.

I think you're asking for something different, but I wanted to check if either of these approaches addresses your needs?

https://johnnyreilly.com/adding-lastmod-to-sitemap-git-commit-date
https://johnnyreilly.com/docusaurus-createfeeditems-api-git-commit-date

Both of the above relate to sitemaps / rss - I suspect that's not what you're after but I thought I'd ask

I'd be happy to work on it.
As it's already in Docs, it'll be easy to add it to blogs, and it'll help me learn the code so I can start contributing

I'd be happy to work on it. As it's already in Docs, it'll be easy to add it to blogs, and it'll help me learn the code so I can start contributing

Just do it!

So what I understand is that you want all this but for blog posts?

It's important to understand if there's a strong use case to introduce this new feature.
Is this something that you actually need in practice for a concrete use case, or simply an improvement that you imagined would be useful but don't particularly plan to immediately use it?
Do you have any real/production live blog post URL to share, on which you'd like to show this new last update data?

So what I understand is that you want all this but for blog posts?

Yes

Is this something that you actually need in practice for a concrete use case, or simply an improvement that you imagined would be useful but don't particularly plan to immediately use it?
Do you have any real/production live blog post URL to share, on which you'd like to show this new last update data?

Why isn't this feature useful? This could be a company blog, not necessarily mine or anyone else's. Personally, I'm willing to use this functionality on my own site because I want visitors to know that the article has undergone a change after publication due to a new version of the library or something like that. And why should I answer this question in the first place? If this functionality is available in the documentation pages, why not ask yourself why this functionality is in the documentation? We are not perfect, we are not blamelessly wrong. We learn from our mistakes.

@ZhymabekRoman we try to only build features that people will actually use in practice. If people just come up with "ideas" and don't plan to use them in practice, is this actually useful to build it in the first place? I ask similar questions in almost all feature requests, not just this one.

And why should I answer this question in the first place? If this functionality is available in the documentation pages, why not ask yourself why this functionality is in the documentation?

Not sure why you take it that way, I just kindly ask you to play the game of describing your use case so that we figure out if it's worth it to implement, and eventually get insight on how to design it best. I'm not saying this feature is not useful, I'm just saying I'd like to know more. Ideally, we'd like to have multiple users say "I plan to use this feature because for reason X" before implementing it. Now as it's already on the docs plugin, that seems reasonable to be consistent and add this to the blog plugin too, but there are certainly some subtilities to handle for this specific case that we could discuss first.

We are not perfect, we are not blamelessly wrong. We learn from our mistakes.

I have no idea what you mean here sorry 😅

Personally, I'm willing to use this functionality on my own site

Is this the blog you plan to use this on?
https://zhymabekroman.github.io/blog/posts

because I want visitors to know that the article has undergone a change after publication due to a new version of the library or something like that.

Did you already have the use case on your blog? I only see one post in the link above, would it be important to show that edit date?
Wouldn't it be better to use your own words to describe why the blog post has been edited instead of just showing an author/date at the bottom?
Do you plan to use Git edit date for that or explicit frontMatter?
Again, I'd like you to be very concrete. If you want an edit date to appear on a specific blog post, please share the URL, and explain why you want the edit date to appear.
For example:

I want the edit date to appear on blog post [url] in a similar way it does for docs because [reason]. I plan to provide this edit date through [git history | frontMatter]. Using custom text in the blog post intro is not a good workaround because [reason]...

Questions to be answered:

Is displaying the editing author actually useful? Unlike docs, blog posts have a list of authors at the top.
Should the edit date appear on the paginated list? (the list view does not exist for docs but does for blog posts)
Should this impact SEO meta tags or sitemap? probably
Should this impact the RSS feed order?

I hope you understand better why I ask all those questions now.
The goal is not to rush into implementing an idea but to collect community feedback before implementing this so that we implement it the right way.

I'm also interested in this feature. My input:

I don't think the editing author is useful, since blog authors are explicitly defined.
I think the edit date should be displayed as "Updated " at the top rather than at the bottom of the post. (The original post date should be preserved, or there should be an option as to which date is displayed.)
We should allow for explicitly setting the edit date via frontmatter in addition to auto-detecting the date via the git history.
Whether this impacts the RSS feed order should be dependent on whether or not the original date is preserved/displayed.
If the RSS feed order is changed, will the date in the URL change as well? Again, I think this is dependent on whether or not the original date is preserved/displayed. But if the original date is hidden and the URL and feed is updated, then why not just republish the edited post with the new date and remove the original?

I'm no expert in SEO, but I agree we should take a careful and deliberate approach here instead of rushing into the implementation.

As for why this feature may be useful: for my work, we're currently updating some of our previously published blog posts for SEO, and it's desirable to make it clear that the content has been updated since the original publish date.

Thanks for your feedback.

I think the edit date should be displayed as "Updated " at the top rather than at the bottom of the post

Agree, also looks better to me. I've seen a few blogs doing that already.

Whether this impacts the RSS feed order should be dependent on whether or not the original date is preserved/displayed.

Not a super fan of too magical behaviors like this. Will all users expect such behavior? At the same time we try to have sensible defaults so I don't know 🤷♂
Maybe we should do nothing, and let users decide if they want to sort the feed themselves?
@johnnyreilly added a createFeedItems hook where you can re-order the feed based on the update date if you want to.
https://docusaurus.io/blog/releases/2.3#blog-createfeeditems

in addition to auto-detecting the date via the git history.

The tricky part is that if you want to edit a blog post typo or any other maintenance-related edit that is not significant, you maybe don't want that fix to have an effect on the last update date?
A scenario that we probably want to avoid: you edit a typo in a very old blog post, and now it's last edited in 2023, at the top of your RSS feed, and your feed readers get pinged to read it while content didn't really change...
This Git-based thing should probably not be a default? or maybe we shouldn't build it at all?

@slorber, Yes, I would like to use it on my blog. I needed this functionality when I updated the last article by adding and changing some applications from the list (see the last blog post). At least it would show that the article has been updated, as many blogs do. I apologise for being rude, it's been a bad day.

This Git-based thing should probably not be a default? or maybe we shouldn't build it at all?

I think making git-based blog page update by default is not required functional. Presonally I would like to manually enter the update date in the blog post properties.

Thanks for understand and the feedback.
So what I understand is that

we should only build the frontMatter last_update feature
we should not necessarily use the same design as docs
we can leave the RSS feed unchanged, createFeedItems is probable flexible enough to give control
we can wait for more feedback before implementing the git last-update to see if it's really useful

Any idea how the date should be integrated in the current design?
This looks a bit weird to me:

Any existing blog to share displaying an update date that we could use as an inspiration?

in addition to auto-detecting the date via the git history.

The tricky part is that if you want to edit a blog post typo or any other maintenance-related edit that is not significant, you maybe don't want that fix to have an effect on the last update date?

I think correcting typos or broken links warrants updating the date IMO.
Otherwise, you could use the same argument for docs that maintenance-related edits shouldn't have an effect on the displayed date.

A scenario that we probably want to avoid: you edit a typo in a very old blog post, and now it's last edited in 2023, at the top of your RSS feed, and your feed readers get pinged to read it while content didn't really change...

Perhaps we shouldn't alter the feed order after all.

This Git-based thing should probably not be a default? or maybe we shouldn't build it at all?

Implementing the frontmatter option first sounds reasonable to me! The git-based option would just be a "nice-to-have" to avoid needing to manually manage the date value.

Any idea how the date should be integrated in the current design?

If we want to keep things simple, maybe something like this:

Similar to how we mark the publish date with datePublished, we'd want to add the dateModified itemprop to the update date.

Hey :)
i'm surprised this feature is available on docs, but not in blog
What is the status about this feature ?
I've start migration my old blog to new one with docusaurus
And i'rewrite all article and fix some mistake, but i want to keep the write date and add an update date :)
Can i help ?
Thanks

@Horsty80

i'm surprised this feature is available on docs, but not in blog

Those are different plugins, with different frontMatter, options and page layouts/designs

What is the status about this feature ?
Can i help ?

I'm focusing on Docusaurus v3 (MDX 2 + React 18) and this feature is not a high priority on my todo list
Unless someone from the community steps in, and produces a final feature design + draft PR to review, this won't progress in the short term

I'm also interested in such a feature.
My use case is a chronology site (a preview is available at https://cronica-it.github.io/preview/). The chronological events are blog posts with some additional metadata to define the event date and duration.
The posts are not write and forget, they are alive, and require updates from time to time, as more details are discovered related to the events.
It would be very useful to know who updated the post and when was it last updated. For this use case, with frequent updates, the date must be extracted automatically from the git date, since manually updating front matter properties is too tedious and error prone.

I already implemented this feature in my fork, here is the commit:

https://github.com/cronica-it/docusaurus-chronology/commit/83e5293121aeb8c9b419be0fc0857cd56a5f72cc

@ilg-ul Great job! Thank you so much!

Thank you @ZhymabekRoman, but wait for this to be upstreamed. There were many new features in my chronology fork and it'll take some time to integrate them.

@slorber Sébastien, do you plan to cover this too with your colleague?

No, we still don't have a clear design for this feature afaik.

Note this feature is similar to https://github.com/facebook/docusaurus/issues/6218 in a way: we have an existing Markdown/MDX document and we want to display extra metadata about it somewhere in the theme.
This can now be implemented in userland starting Docusaurus v3.1 thanks to the parseFrontMatter hook:
https://docusaurus.io/blog/releases/3.1#parsefrontmatter-hook
See the comment I made here: https://github.com/facebook/docusaurus/issues/6218#issuecomment-1941157754
Since many of you want to implement this feature I'm going to post the recipe here too, adapted for this specific blog last update case.
The v3.1 parseFrontMatter hook allows you to automatically add a frontMatter.lastUpdated field to your blog posts
(in case defining this manually is not an option)
async function getLastUpdated(filePath: string) {
  // Read the metadata you want from Git or any other system here...
  return {
    at: "3 O'clock",
    by: "Seb",
    picture: "https://github.com/slorber.png",
  }
}

const config: Config = {
  markdown: {
    parseFrontMatter: async (params) => {
      const result = await params.defaultParseFrontMatter(params);
      const lastUpdated = await getLastUpdated(params.filePath);
      return {
        ...result,
        frontMatter: {
          ...result.frontMatter,
          lastUpdated,
        }
      }
    }
  },
}

export default config;

Then you can swizzle the blog component you want and render that front matter anywhere in the UI:
yarn docusaurus swizzle @docusaurus/theme-classic BlogPostItem/Footer --wrap --typescript
import React from 'react';
import Footer from '@theme-original/BlogPostItem/Footer';
import type FooterType from '@theme/BlogPostItem/Footer';
import type { WrapperProps } from '@docusaurus/types';
import { useBlogPost } from '@docusaurus/theme-common/internal';

type Props = WrapperProps<typeof FooterType>;

function LastUpdatedFooter() {
  const { frontMatter, isBlogPostPage } = useBlogPost();

  const lastUpdated = (frontMatter as any).lastUpdated as {
    at: string;
    by: string;
    picture: string;
  };

  // Do not show this data for paginated lists
  if (!lastUpdated || !isBlogPostPage) {
    return null;
  }

  return (
    <div
      style={{
        marginTop: 20,
        marginBottom: 20,
        display: 'flex',
        flexDirection: 'row',
        alignItems: 'center',
      }}
    >
      Last updated by{' '}
      <img
        src={lastUpdated.picture}
        style={{ margin: 5, width: 20, height: 20, borderRadius: 20 }}
      />{' '}
      {lastUpdated.by} at {lastUpdated.at}
    </div>
  );
}

export default function FooterWrapper(props: Props): JSX.Element {
  return (
    <>
      <Footer {...props} />
      <LastUpdatedFooter />
    </>
  );
}

Result:

Runnable sandbox: https://stackblitz.com/edit/github-kk5bsa?file=docusaurus.config.ts,src%2Ftheme%2FBlogPostItem%2FFooter%2Findex.tsx

Considering it is possible to implement in userland thanks to existing Docusaurus primitives, if we ever add this feature to Docusaurus core, this would only be an "opinionated shortcut" to the above solution.
By opinionated I mean: limited to reading history on Git (and not other VCS), and displaying the last update date in some predefined place such as the blog footer. This also means our opinions won't please everyone.
For this reason, there's no reason to rush implementing this feature officially. I'd rather see a few successful userland implementations first so that we understand the common denominator of the solutions, which would help us craft a good opinionated solution that pleases a maximum number of users.

Given that this feature is already implemented for docs pages, why not provide the same implementation for blog posts, and, only for more complicated use cases, expect the users to swizzle and change the look?
I did exactly this in my fork, and I think that this solution might be acceptable for most of the regular users, who are not very keen to swizzle and write a lot of code for a relatively small feature.

Any other opinions on this solution? Is it acceptable as a common denominator?

@ilg-ul as you can see @TheCatLady has different opinions from yours.
https://github.com/facebook/docusaurus/issues/8657#issuecomment-1442377798
https://github.com/facebook/docusaurus/issues/8657#issuecomment-1440690880

If we implement what you like, other users might not like it.
If we implement what other users like, you might not like it.

The goal of designing a feature is to find a solution that most users will like. If we can all agree on what should be implemented, the implementation is likely easy.
The hard part is to figure out what should be implemented in the first place.
If I see 10 sites with userland implementations of this feature, 9 of them have opinion A and 1 of them has opinion B, we know that it's more likely users want us to implement opinion A, and can find a common denominator that would satisfy the subtleties of 9 implementations.
Also there's a big difference between someone having a theorical opinion in a GitHub comment, and someone really shipping his opinion to a production website.
In your case, you have a concrete demo of your opinion running live, so it adds weight to your comment: https://cronica-it.github.io/evenimente/2023/conferinta-dtc-30-ani-internet/

(but as you can see there's probably some design to fix 🤪 )

So, I'm not against implementing it, but I'd like to know first if people can agree on this design.
And if you disagree with the design proposed by @ilg-ul, what is your alternative solution?
Now that there is a provided solution to implement your alternative solution, are you willing to ship it to production to prove that you stand by your opinion?
Please vote on this comment:

👍
👎

And eventually: add a comment explaining your choice if you have something interesting to say.

Ah, sorry, I don't want to appear smarter than I am, I'm not suggesting any design in particular, I'm only suggesting, for consistency reasons, to use the same design for docs and for blog posts, whatever it is.
So, if the design used for docs is not good, it must be improved, to the point where it can be used everywhere, in docs and in blog posts too.
As for the actual format used to display the text, for me it is not relevant, I'm fine with the one used for docs; if the majority of the users got used to it and find it acceptable, the minority can swizzle the components and customise it.
Anyway, before voting for a specific look, I think that we should decide between your current solution (not implementing anything and asking everyone wanting to use it to accept the pain of swizzling) and a solution based on a common denominator, consistent with the docs, where only a minority will have to swizzle.
My vote goes to consistency and avoiding swizzling.

Agree 👍
Unless someone is against this idea, we'll start working on a PR with my apprentice
@TheCatLady if you don't like the proposal above, now is the best time to push back 😉

we'll start working on a PR with my apprentice

Feel free to reuse any parts of my commit (https://github.com/cronica-it/docusaurus-chronology/commit/83e5293121aeb8c9b419be0fc0857cd56a5f72cc). And be sure you fix that css that I messed ;-)

Hello, I'm also interested in that feature. I swizzled src/theme/BlogPostItem/Header/Info/index.js specially for that case but I would be happy if it was included in main codebase.
When it comes to SEO it has to use the itemprop="dateModified" attribute as described on Google documentation e.g.
<time datetime="2020-05-27T00:00:00.000Z" itemprop="dateModified">May 27, 2020</time>

It also has to be in ISO 8601 format which I ignored at first and google pointed it out in their tooling 😛.
On my fork, I did this after a spacer and made dates italic:

Thanks, we'll have to remember to add the dateModified Structured Data as well (but I can count on @johnnyreilly to remind us on that 🤪 ).
Note: we recently migrated from Microdata to JSON+LD since Google prefers that:
https://github.com/facebook/docusaurus/pull/9669
(will be in Docusaurus v3.3+, not 3.2)

Similarly to the docs plugin, Docusaurus v3.2 will have blog last update dates if you turn on the blog plugin options. You can override those with custom front matter.
PR: https://github.com/facebook/docusaurus/pull/9912
Preview: https://deploy-preview-9912--docusaurus-2.netlify.app/blog/releases/3.1/
We keep the same design as for docs last update UI. If you want another UX/UI you can swizzle the appropriate blog components, the last update metadata is available here.


Project: Database

Include a basic SQLite file in the repo.

Project started.

Kind of bummed that this has to go outside of the standard library. However, it's such a critical part of day to day life that we need to practice with at least one type of database.


Change CommandToRun from a text box to a history text box

Thus, the most recently run commands will be available for
easy re-use.

@BruceForstall,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@vancem PTAL

@vancem Updated to respond to CR feedback.


Freeze after "Running AppleScript to make Finder stuff pretty"

Hi everyone, I'm having an issue with the latest create-dmg version 1.2.0. One of the last steps "Running AppleScript to make Finder stuff pretty: [...]" is hanging.
At first, I noticed that this happens with our own script but I tried out create-dmg/examples/01-main-example as well... same issue. I'm using macOS 13.5.2 (Apple Silicon M1) and also experienced this in a VM with macOS 12.6 (Apple Silicon M1).
Reproducible steps:

Download this repository.
Run ./sample from 01-main-example.

~/Downloads/create-dmg-master/examples/01-main-example $ ./sample
Creating disk image...
......
created: /Users/<redacted>/Downloads/create-dmg-master/examples/01-main-example/rw.73859.Application-Installer.dmg
Mounting disk image...
Device name:     /dev/disk10
Searching for mounted interstitial disk image using /dev/disk10s...
Mount dir:       /private/tmp/dmg.CL3r40
Copying background file 'installer_background.png'...
Making link to Applications dir...
/private/tmp/dmg.CL3r40
Running AppleScript to make Finder stuff pretty: /usr/bin/osascript "/var/folders/hf/tlb4sd996lsb_4twv3fl9c9h0000gn/T/createdmg.tmp.XXXXXXXXXX.WvEDwyxQ" "dmg.CL3r40"

I'm unable to reproduce this issue with create-dmg 1.1.0. I also reviewed the diff between 1.1.0 and 1.2.0 but couldn't find anything obvious. Anyone else have an idea?
Edit: I've installed create-dmg via brew. Is this a "problem"? I've read something about it being a sandboxed system. But still, the main example should work?

Just reproduced it. Not sure what happened, tried yesterday and had no issues.

Seems my last commit fails, so I'm fixing it https://github.com/create-dmg/create-dmg/commit/b116760624fc43906de1e65285445aee73cb3d89

Edit: I've installed create-dmg via brew. Is this a "problem"? I've read something about it being a sandboxed system. But still, the main example should work?

Not a problem at all. The tests at brew are sandboxed, but on your computer works the same as if you manually clone the repo and execute the script.

Fixed in 1.2.1

Thank you for the quick fix! 🙌

I'm hitting this issue and everything looks like I'm using 1.2.1 except create-dmg --version, which says 1.2.0.
I have uninstalled and reinstalled create-dmg via brew, and it says it's installing 1.2.1. However, the --version always says 1.2.0.
Before I go crazy, is it possible that v1.2.1 is reporting version 1.2.0 when calling the command create-dmg --version?

Yep, it’s fixed in the repo but the 1.2.1 archive says 1.2.0.
On Sun, 12 Nov 2023 at 18:05 Daniel González Reina @.***>
wrote:

I'm hitting this issue and everything looks like I'm using 1.2.1 except create-dmg
--version, which says 1.2.0.
I have uninstalled and reinstalled create-dmg via brew, and it says it's
installing 1.2.1. However, the --version always says 1.2.0.
Before I go crazy, is it possible that v1.2.1 is reporting version 1.2.0
when calling the command create-dmg --version?
—
Reply to this email directly, view it on GitHub
https://github.com/create-dmg/create-dmg/issues/154#issuecomment-1807184713,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADVHI5YKXA53DEIENOD2JLYED6UTAVCNFSM6AAAAAA476WPSWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBXGE4DINZRGM
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

Well the good news it that I'm not crazy 😅. The bad news is that I'm facing this issue on 1.2.1. Should I open a new issue to track it?

I just found a workaround by accident. It looks like deleting something in finder causes the AppleScript to get unstuck. I haven't really tested if it's anything, but the following has worked every time:

Find the temp .dmg created while running the AppleScript
Copy the temp .dmg
Delete the temp .dmg copy

Maybe that also hints at what might be causing the problem.


Persistent model requires exact dimension to predict

Thank you for putting this great project together, I have been using it since it was 0.3.1. Trying to use version 2.0, but I'm stumped on an issue I can't seem to get past.
Basically, I have a persistent model
$estimator = new PersistentModel(
new LogisticRegression(64, new Adam(0.01)),
new Filesystem($modelName, true)
);
$estimator->train($training);
$estimator->save();
This all works perfectly, and if I validate the model in the same PHP session it works!. But if I try to load the persistent model in a different PHP session then this happens
$dataset = Labeled::fromIterator(new CSV($filename,true))
->apply(new NumericStringConverter())
->apply(new OneHotEncoder())
->apply(new ZScaleStandardizer());
$estimator2 = PersistentModel::load(new Filesystem($modelName));
$predictions = $estimator->predict($dataset);
78
sample1.rbx
Rubix\ML\Exceptions\IncorrectDatasetDimensionality
Dataset must contain samples with exactly 2107 dimensions, 81 given.
at vendor/rubix/ml/src/Specifications/DatasetHasDimensionality.php:64
60▕      */
61▕     public function check() : void
62▕     {
63▕         if ($this->dataset->numFeatures() !== $this->dimensions) {
➜  64▕             throw new IncorrectDatasetDimensionality($this->dataset, $this->dimensions);
65▕         }
66▕     }
67▕ }
68▕
The model was trained with 2000 records, but for prediction, I'm only passing 78 records, which triggers the error message. In previous version I was able to predict by only passing one record. Is there something different I need to do with version 2.0 ? Or is it a bug?
My configs...
composer
"php": "^8.0.2",
"guzzlehttp/guzzle": "^7.2",
"laravel/framework": "^9.19",
"laravel/sanctum": "^2.14.1",
"laravel/tinker": "^2.7",
"rubix/ml": "^2.0"
PHP 8.0.14 (cli) (built: Dec 21 2021 15:10:46) ( NTS )
Copyright (c) The PHP Group
Zend Engine v4.0.14, Copyright (c) Zend Technologies

The problem seems to be that you are not using the Transformer fittings from the training session when performing inference. Otherwise, OneHotEncoder would have created the extra columns needed.
You can either save the Transformer fittings and then load them into the inference script, or you can save them in a Pipeline with the model all at the same time.
See
https://docs.rubixml.com/2.0/model-persistence.html#persisting-transformers
https://docs.rubixml.com/2.0/preprocessing.html#transformer-pipelines

Andrew!,
That did it!. Well done. Works like a charm. I will spell it out here for those who might have the same issue going forward. And please let me know if there is a better way to do it.

To train the model and save it with the transformer fittings I changed the trainer initialization to this:
`
// Load your labeled dataset to train the model
$dataset = Labeled::fromIterator(new CSV($filename, true));
// Instantiate hot encoder with training algo
$estimator = new PersistentModel(new Pipeline([
new NumericStringConverter(),
new OneHotEncoder(),
new ZScaleStandardizer(),
],  new LogisticRegression(64, new Adam(0.01))),new Filesystem($modelName, true));
// Then easy as
$handle = $estimator->train($training);
$estimator->save();
In another process you could do the following to predict values, in this case, I'm loading an unlabeled dataset:
$dataset = unlabeled::fromIterator(new CSV($filename,true));
// Load your trained model ...
$estimator = PersistentModel::load(new Filesystem($model));
// Pass your unlabeled data to predict  ...
$predictions = $estimator->predict($dataset);
// User $predictions as needed.
`
:-)


⚠ Bofrost.de has degraded performance

In 20a9c61, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1247 ms

Resolved: Bofrost.de performance has improved in 27f33ac after 6 minutes.


Miss warning because stay scrolled down

URL
No response
How to reproduce the issue?
First we click on a train platform, one that might be near you, it doesn't matter.

Ah, there is a warning. So we fix it. Then we scroll down to see what the results of fixing it were:

So far so good. OK, now let's click on a different platform:

Note how, even though we are now looking at a different platform, we are still scrolled down.
That might be usually in fact what we want. However, we miss a very important warning, that we will only see if we happen to scroll back up:

Sure, you might say I am supposed to keep my eyes on this at the bottom,

But that isn't easy to remember.
Anyway, sure, don't scroll the panel back up, but at least somehow alert the user that there is something unusual up there. Thanks.
Screenshot(s) or anything else?
(Yes, two platforms with the same warnings, because both platforms needed to be upgraded.)
Which deployed environments do you see the issue in?
Linux
What version numbers does this issue effect?
No response
Which browsers are you seeing this problem on?
Chrome

Related #7839


Support for Firebase Authentication Triggers

Support for functions.auth.user().onCreate & functions.auth.user().onDelete
Reference Docs:
https://firebase.google.com/docs/reference/functions/functions.auth.UserBuilder
https://firebase.google.com/docs/functions/auth-events
Thanks!

Thanks for submitting this request.
Some notes: looks like at least UserInfo and UserMetadata can be reused from firebase_admin_interop. UserRecord looks similar but hides some fields (like passwordHash) so might be better to create separate binding.
@Cretezy just wondering if you planned to tackle this any time soon? I should have some time in a couple days to get this don, so don't want us both spend time doing the same thing.

Yeah, I can work on it tonight and tomorrow. I'll have a PR within a day hopefully!

Started https://github.com/pulyaevskiy/firebase-functions-interop/pull/17

Merged!

I'm about to release a Pub version. Stay tuned!

https://pub.dartlang.org/packages/firebase_functions_interop/versions/1.0.0-dev.3.0
Thanks @Cretezy !
@TonyDowney please report if you find any issues with the new version.


Factorization clarification question

I'm writing some custom BW code (can share over email, but is still to remain private for now) where I observe a ~60% speed increase (2600 solve/sec vs 1600 solve/sec) when I factorize beforehand.
Are you certain the below is correct?
https://github.com/haasad/PyPardiso/blob/0f7afd061e68f8ef3e7f77c4aeb3f3b5070bb006/pypardiso/scipy_aliases.py#L73-L74
You may be correct that the computational/memory cost is not worth it if you only perform a few -whatever number few is- Ax=b solves, on the same A, but when I do many solves (>20k), this does seem to matter quite a lot.

edit: Also note that def factorize() itself has conflicting information with the above.
https://github.com/haasad/PyPardiso/blob/0f7afd061e68f8ef3e7f77c4aeb3f3b5070bb006/pypardiso/pardiso_wrapper.py#L145-L152

I am 99% sure that the difference your are seeing is due to https://github.com/haasad/PyPardiso/blob/0f7afd061e68f8ef3e7f77c4aeb3f3b5070bb006/pypardiso/scipy_aliases.py#L44. If the matrix wasn't factorized the difference would be at least an order of magnitude slower. What this line does is make sure the A matrix, which is factorized, is the same now as when it was factorized in the first place. factorize doesn't make this check and is therefore somewhat faster.

You should be able to do the following for maximum speed:
import pypardiso

solver = pypardiso.ps
solver.factorize(A)
solver.set_phase(33)
x = solver._call_pardiso(A, b)

This skips all the checks etc.

Thanks for your replies both!
I'll experiment with Adrians solution by rewriting def solve_linear_system() and def decompose_technosphere() and see how that (doesn't?) change results
I'll report back with some findings

Please be aware that factorized is in a way just a convenience function, so pypardiso can be used as drop-in replacement for scipy.sparse.linalg.factorized. It still uses pypardiso.spsolve under the hood and pypardiso.spsolve always does a factorization for re-use by subsequent calls to spsolve.

I think I found the reason for the the performance difference that you see. I assume the brightway technosphere matrix is in csc format?
factorized converts A to csr format and keeps a copy of it:
https://github.com/haasad/PyPardiso/blob/0f7afd061e68f8ef3e7f77c4aeb3f3b5070bb006/pypardiso/scipy_aliases.py#L77
spsolve converts to csr on every call:
https://github.com/haasad/PyPardiso/blob/0f7afd061e68f8ef3e7f77c4aeb3f3b5070bb006/pypardiso/scipy_aliases.py#L41-L42
Unfortunately my commit message from 2016 is pretty useless: https://github.com/haasad/PyPardiso/commit/7a60c843a1caa2f67a61629ffeeb9b6de47dedb3
pardiso can deal with both csc and csr formats:
https://github.com/haasad/PyPardiso/blob/0f7afd061e68f8ef3e7f77c4aeb3f3b5070bb006/pypardiso/pardiso_wrapper.py#L219-L227

Looks like I actually wrote down the reasoning for this in #7, even with a jupyter notebook and everything :blush:

Alright, here's some findings:

@cmutel
I am 99% sure that the difference your are seeing is due to
https://github.com/haasad/PyPardiso/blob/0f7afd061e68f8ef3e7f77c4aeb3f3b5070bb006/pypardiso/scipy_aliases.py#L44

I'm not entirely sure this is correct. I think it may be the conversion to csr that is costing so much time.
https://github.com/haasad/PyPardiso/blob/0f7afd061e68f8ef3e7f77c4aeb3f3b5070bb006/pypardiso/scipy_aliases.py#L41-L42
When I convert my BW matrices to csr beforehand, I get the same speed as calling lca.decompose_technosphere() (which does this for us). solver._check_A does, however, re-do the checks for csc/csr, which doesn't seem needed when calling spsolve as we already convert to csr anyway.
I think if Brightway would set it's default format to csr instead of csc, we can speed up these calculations by default. The current BW25 implementation (which blocks the factorization in lca.decompose_technosphere()) seems to be incurring a speed penalty for no reason unless user thinks to convert lca.technosphere_matrix to csr themselves. This confirms what Adrian is saying in this comment. I understand the original csc format for UMFPACK compatibility, but most users are on x86 and thus use pypardiso, so perhaps this default is not the best.

@haasad
You should be able to do the following for maximum speed:
import pypardiso

solver = pypardiso.ps
solver.factorize(A)
solver.set_phase(33)
x = solver._call_pardiso(A, b)

This adds about ~10% speed for me, while nice if you know what you're doing, perhaps it's safe that this is indeed not done for BW.
Now to look ahead:
What makes sense for BW?
I would like to see lca.decompose_technosphere() not be blocked when using pypardiso -especially with a wrong warning type- but perhaps I'm misunderstanding something here?
Furthermore, does it make sense to set the sparse format based on the solver we're checking the solver anyway, so setting the 'correct' sparse format could help speed things up.
Let me know if you'd like to see a PR for BW25 Chris, I'll try and so it soon-ish then.

I would like to see lca.decompose_technosphere() not be blocked when using pypardiso -especially with a wrong warning type- but perhaps I'm misunderstanding something here?

pypardiso always does a factorization + solve, the warning in bw2calc is correct
the benefits that you see don't come from factorization, but are a side-effect of not having to do the repeated sparse format conversion, i.e. A = A.tocsr()
pypardiso needs the brightway technosphere matrix to be in csr, that's why the conversion to csr is enforced in pypardiso.spsolve

the reasoning for this is explained in #7

Furthermore, does it make sense to set the sparse format based on the solver we're checking the solver anyway, so setting the 'correct' sparse format could help speed things up.

I also think that the best way would be if brightway uses csr format as default in combination with pypardiso.

This adds about ~10% speed for me, while nice if you know what you're doing, perhaps it's safe that this is indeed not done for BW.

I don't think the trade-off of 10% speed versus skipping all safety checks is worth it. If you do an LCA calculation, modify some values in the technosphere matrix and then do another LCA calculation, you might get completely wrong results without the checks in pypardiso.

pypardiso always does a factorization + solve, the warning in bw2calc is correct

Well, partially IMO. By giving this warning and putting the factorization in an else:, BW users with pypardiso (which is still most of them) will keep using a csc format technosphere, as previously lca.decompose_technosphere() would convert this to csr. In BW25, a user would now need to manually convert their technosphere, or face a ~60% speed loss as the technosphere needs to be converted to csr for every new FU.
We can either automatically keep technosphere (and for consistency also biosphere?) in the correct format for the solver (csc for scipy, csr for pypardiso) -which is the best solution IMO-, or, we allow lca.decompose_technosphere() to call factorized(), which would convert the technosphere to the correct csr format.
I'll close this discussion now, I think we can continue in https://github.com/brightway-lca/brightway2-calc/issues/98 as this is a BW issue, not a pypardiso issue.


TUT 3 - HPL

Please clarify this section, and add the calculator as a tip after step 5 in the HPL section

done


[MSRC 63764] Removed credentials being logged on console and debug logs for External TFS

Bump up extension version. I think it should be 15.186.0 as 186 is the on-going sprint - https://whatsprintis.it


terraform-ls: 0.11.0 -> 0.12.0

Motivation for this change
Things done

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

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

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

Result of nixpkgs-review pr 108896 1

1 package built:

terraform-ls

Result of nixpkgs-review pr 108896 1

1 package built:

terraform-ls

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108896 run on x86_64-linux 1

1 package built:

terraform-ls

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108896 run on x86_64-linux 1

1 package built:

terraform-ls


Include authentication UI example at examples page

Which scope/s are relevant/related to the feature request?
Docs
Information
The current examples page at https://www.spartan.ng/examples/ has only two examples of using spartan/ui components for building UIs.
The goal with this feature/enhancement its adding an authentication example, similar to what we have at shadcn/ui example page at https://ui.shadcn.com/examples/authentication.
Describe any alternatives/workarounds you're currently using
No response
I would be willing to submit a PR to fix this issue

[X] Yes
[ ] No

Great idea! I would love for us to recreate the examples that shadcn provides!

Great idea! I would love for us to recreate the examples that shadcn provides!

Thanks @goetzrobin ! I'm going to take a crack at it!


Velocity bottleneck tests

tests for FollowerStopper controller
added a test for PISaturation
removed HandTunedController

Pull Request Test Coverage Report for Build 2852

54 of 54 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+1.0%) to 87.783%

Totals

Change from base Build 2845:
1.0%

Covered Lines:
7523

Relevant Lines:
8570

💛  - Coveralls


mate: reformat nix expressions and use git repository to list versions for the update script

Description of changes

mate: reformat nix expressions
mate: update script list versions from the git repository

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

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


New version 1 2 2

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


fix(generator): also scan parameter comments for references

Fixes #11885.

This change is

Is this unit-testable?

Is this unit-testable?

Enabled coverage in an existing test by correcting the name of the (copied) LogEntry message.  Now golden/v1/golden_kitchen_sink_client.h will have a link for a reference originating in a method-signature parameter comment.

If we revert the generator changes, nothing would fail. We typically run generate-libraries and commit the result. Just saying.

If we revert the generator changes, nothing would fail.

Wouldn't the golden tests fail?

We typically run generate-libraries and commit the result. Just saying.

Acknowledged.  But that is an indictment of the "run generate-libraries and commit the result" process.  Any changes committed to golden files should be justified.


GSD Request

--- GSD JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v4.9 to before v5.15.12",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=d9fe64e511144c1ee7d7555b4111f09dde9692ef",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=d259f621c85949f30cc578cac813b82bb5169f56"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "d9fe64e511144c1ee7d7555b4111f09dde9692ef",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "d259f621c85949f30cc578cac813b82bb5169f56",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "asix: fix uninit-value in asix_mdio_read()\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.15.12 by commit d259f621c85949f30cc578cac813b82bb5169f56, it was introduced in version v4.9 by commit d9fe64e511144c1ee7d7555b4111f09dde9692ef. For more details please see the references link."
}
--- GSD JSON ---

This issue has been assigned GSD-2021-1002824


S3 API: failed to write to replicas for volume xx: file over the limited 268435456 bytes

Sponsors SeaweedFS via Patreon https://www.patreon.com/seaweedfs
Report issues here. Ask questions here https://stackoverflow.com/questions/tagged/seaweedfs
Describe the bug
When using S3 API PutObject to upload a large file (> 256 MB), S3 gateway will throw 500 Internal Error.
The log of S3 gateway recorded that
E0808 09:56:49     1 s3api_object_handlers.go:294] upload to filer error: failed to write to replicas for volume 22: [volume-test-3.volume-test:8080]: file over the limited 268435456 bytes

System Setup

List the command line to start "weed master", "weed volume", "weed filer", "weed s3", "weed mount".

The seaweedfs cluster is built on top of Kubernetes. Masters, volumes, filers and s3 gateways are replicated x 3.
weed master -defaultReplication 001 -ip $(hostname).master-test-peer -peers master-test-0.master-test-peer:9333,master-test-1.master-test-peer:9333,master-test-2.master-test-peer:9333
weed volume -dataCenter dc1 -rack rack1 -dir /data -ip $(hostname).volume-test -max 10 -mserver master-test:9333 -port 8080
weed filer -master master-test:9333
weed s3 -config /etc/seaweedfs/s3-config.json -filer filer-test:80

OS version

Ubuntu 18.04.3 LTS
Linux 4.4.0-159-generic #187-Ubuntu SMP Thu Aug 1 16:28:06 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

output of weed version

version 30GB 1.87  linux amd64

if using filer, show the content of filer.toml

[mysql]
enabled = true
username = "seaweedfs"
password = "*******************"
hostname = "mysql-cluster-test-mysql-master.mysql"
database = "seaweedfs"
port = 3306

Expected behavior
The file should be uploaded successfully.

Thanks for the detailed error report.
Fixed in 3b1a95ac26debb3080794bf8605ea2d5636818c7


Crash on startup

Description
When trying to open the alvr app on manjaro linux (portable), the client just crashes.
General Troubleshooting
Output from terminal
(alvr_launcher:33924): Gtk-WARNING **: 10:43:25.276: Theme parsing error: gtk.css:73:46: The style property GtkScrolledWindow:scrollbars-within-bevel is deprecated and shouldn't be used anymore. It will be removed in a future version
DEBUG [ureq::stream] connecting to <IP_ADDRESS>:8082 at <IP_ADDRESS>:8082
DEBUG [druid::localization] available locales [], current en-US
DEBUG [druid::localization] resolved: [en-US]
INFO  [druid_shell::platform::gtk::application] gtk: Activated application
steam.sh[33948]: Running Steam on manjarolinux 21.2.6 64-bit
steam.sh[33948]: STEAM_RUNTIME is enabled automatically
setup.sh[34022]: Steam runtime environment up-to-date!
steam.sh[33948]: Steam client's requirements are satisfied
DEBUG [ureq::stream] connecting to <IP_ADDRESS>:8082 at <IP_ADDRESS>:8082
DEBUG [ureq::stream] connecting to <IP_ADDRESS>:8082 at <IP_ADDRESS>:8082
DEBUG [ureq::stream] connecting to <IP_ADDRESS>:8082 at <IP_ADDRESS>:8082
DEBUG [ureq::stream] connecting to <IP_ADDRESS>:8082 at <IP_ADDRESS>:8082
DEBUG [ureq::stream] connecting to <IP_ADDRESS>:8082 at <IP_ADDRESS>:8082
DEBUG [ureq::stream] created stream: TcpStream { addr: <IP_ADDRESS>:43728, peer: <IP_ADDRESS>:8082, fd: 14 }
DEBUG [ureq::unit] sending request GET http://<IP_ADDRESS>:8082/index.html
DEBUG [ureq::unit] writing prelude: GET /index.html HTTP/1.1
Host: <IP_ADDRESS>:8082
User-Agent: ureq/2.4.0
Accept: */*
accept-encoding: gzip
DEBUG [ureq::unit] response 200 to GET http://<IP_ADDRESS>:8082/index.html
DEBUG [ureq::stream] dropping stream: TcpStream { addr: <IP_ADDRESS>:43728, peer: <IP_ADDRESS>:8082, fd: 14 }

Hardware
https://linux-hardware.org/?probe=6c6203c7ff
Installation
ALVR Version:
Latest
SteamVR Version:
Latest
Install Type:

[x] Portable (zip)

OS Name and Version (winver on Windows or grep PRETTY_NAME /etc/os-release on most Linux distributions):
Manjaro Linux

im having the same problem did you fix this?


Logbook breaks when names of non-existent things (including DLC content when not owned) or Twisted Scavengers are added to the sort list.

LogOutput.log

makes sense, not a bug but maybe ill add a skip as an enhancement

That will be very helpful, thanks!


fix(snap): defer service startup till after configure hook runs

This PR modifies the way the snap install and configure hooks when the snap in installed in order to ensure that snap configuration provided at install time is processed before services are started. This is working around an issue with snapd where snap configuration at install time is not made available to the snap until the configure hook is called, which is after the services have already been started.
So, this PR disables all of the services in the install hook, and then in the configure hook, the services are started after configuration has been processed.
Note - this PR supersedes PR #3791.

If your build fails  due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-go/blob/main/.github/Contributing.md
PR Checklist
Please check if your PR fulfills the following requirements:

[x] I am not introducing a breaking change (if you are, flag in conventional commit message with BREAKING CHANGE: describing the break)
[x] I am not introducing a new dependency (add notes below if you are)
[*] I have added unit tests for the new feature or bug fix (if not, why?)

units tests to be added before this is taken out of draft status

[x] I have fully tested (add details below) this the new feature or bug fix (if not, why?)
[NA] I have opened a PR for the related docs change (if not, why?)

This fix relates to the install behavior of the snap, and as such should be transparent to the installer.

Testing Instructions

Install the snap built from this PR and verify that all of the expected services start
Confirm that device-virtual can be enabled ($ sudo snap set edgexfoundry device-virtual=on)
Confirm that kuiper can be enabled ($ sudo snap set edgexfoundry kuiper=on); ensure that both kuiper and app-service-configurable are started
Confirm that support-notifications and support-scheduler can be started (e.g. snap set... support-scheduler=on)
Confirm that security-proxy can be disabled ($sudo snap set security-proxy=off)

Additional test instructions will be added to this PR as it progresses. The more advanced cases require a custom gadget snap which provides default configuration. This is currently the only way to disable secret-store usage. If possible, this PR will be extended to support dynamically disabling secret store usage, but this is currently blocked on issue #3712.
Also note, this has been tested using our in-progress checkbox provider for Jakarta and all of the tests pass.
New Dependency Instructions (If applicable)

I just force-pushed again resolving the following comments from @farshidtz:

changed config options install=true to install-mode: defer-startup
rm INSTALL const
collapsed a few case statements to remove usage of fallthrough
removed 'install' from the comment describing the possible values for a service config option

One more forced push which updates the defer-startup logic, after testing with some pre-configured services.

Running the current TAF tests against this snap succeeds - we get the same results as with the latest/edge snap. The TAF tests do test functionality including

installing the snaps and starting services
enabling and starting  services including device-virtual, app-service-configurable, support-notifications and support-scheduler

Formatting issues caught by the CI can be resolved:

away from the IDE:

$ cd edgex-go/snap/local/hooks/
$ go fmt ./...
cmd/install/install.go
cmd/configure/configure.go

if IDE is open in snap/local/hooks, simply:

go fmt ./...

using the more flexible gofmt (if you have it):

gofmt -w snap/local/hooks

For the sake of simplifying further reviews, it would be great if you add future changes in new commits, rather than amending old ones.

@farshidtz given the time frame involved, I'm going to politely decline this request and continue to use forced push(es) to land my remaining changes. I'll be very specific in comments if/when I do this. We also covered this in our team sync, and I suggested we use one of our future meetings to discuss the topic.

Force pushed two changes:

apply gofmt
rebased on origin/main

Force pushed what's hopefully my last changes:

fixed a typo in snap/README
updated incorrect comments
minor tweaks to a few log statements
renamed configure hook getEdgeXServices to getEdgeXRefServices and added clarifying comments
replaced a switch statement in disableSecretStoreAndRestart
made serviceList a loop var in handleAllServices
replace two append(serviceList, ...) statements with []string{ s }


Dont forcefully set service_name option on any exporter

Some exporters do not define this option (OTLP f.e.) and setting this option
breaks them.

@cedricziel
Thanks for your contribution and sorry again for the late response.
As I mentioned on slack, we are busy setting up the infrastructure to have better 2e2 test at the moment.
There is one integration test failing due to your change.
I know the integration tests are not an easy read at the moment, so here is how you can fix the test.
I believe removing the 'service_name' => 'foo', entry should do the trick.
https://github.com/open-telemetry/opentelemetry-php-contrib/blob/main/tests/Integration/Symfony/OtelSdkBundle/DependencyInjection/OtelSdkExtensionTest.php#L338
The other way would be to add a serviceName to the MockExporter -> https://github.com/open-telemetry/opentelemetry-php-contrib/blob/main/tests/Integration/Symfony/OtelSdkBundle/Mock/SpanExporter.php
However I'm not really sure atm, if that would break any other tests.

Merging this, since the tests should be fixed with: https://github.com/open-telemetry/opentelemetry-php-contrib/pull/47


Follow overlay is missing input labels

Quick summary
If I use the follow me block and open the overlay, I noticed that there are no labels available. As regular user, I’m fine with that, but at least for accessibility there should be invisible labels for screen readers.
Steps to reproduce

Create a page with the "Follow me" block.
Open the page
Open the overlay
Look into the source code

What you expected to happen
A label for each input field is available, especially for screen readers.
What actually happened
The label for the input fields are missing.
Impact
Some (< 50%)
Available workarounds?
No but the platform is still usable
Logs or notes
No response

Thanks for opening the issue @MatzeKitt 👍🏻


Include hideToolbar prop in the RichTextEditor

Release Type: Non-Breaking Feature
Fixes https://x-team-internal.atlassian.net/browse/XP-2780
Description
This PR includes ability to hide the toolbars of RichTextEditor via pro hideToolbar.
Checklist

[x] set yourself as an assignee
[x] set appropriate labels for a PR (In Review or In Progress depending on its status)
[x] move respective JIRA issue to the IN REVIEW column
[x] make sure your code lints (npm run lint)
[x] Flow typechecks passed (npm run flow)
[x] Snapshots tests passed (npm run jest)
[x] component's documentation (.stories.js file) is changed or added accordingly to reflect any new or updated use cases or variants usage
[x] if any snapshots have been changed, verify that component still works and looks as expected and update the changed snapshot
[x] manually tested the component by running it in the browser and checked nothing is broken and operates as expected!

Related PRs

branch
PR

XP-2780-add-new-profile-summary
Auto

Steps to Test or Reproduce

Grab the latest from this branch
Run npm start
Go to http://localhost:9001/?selectedKind=UI Components%2FRichTextEditor&selectedStory=with hidden toolbar
Observe that the toolbar is not visible anymore

Impacted Areas in Application
RichTextEditor
Screenshots

@bernardodiasc Could you please resolve conflict?

Fixed the merge conflict.

hey @nicksp I updated the variable name, this is in review again. Thanks!

Let's add a build, and we're good to go 😄


ChangeSets: write sample data generator

Can we prioritise this one ?  getting nervous that this area is getting a lot of commits and we have no real way of seeing the end result.


Front end

Reading material thoughts on anything front end related

Looked into the landscape of css libraries today. The purpose was to explore what is the most minimal I can do for a frontend without npm if I can get away with it.
SimpleCSS
https://simplecss.org
Bulma
https://bulma.io
gov uk design system
https://design-system.service.gov.uk/get-started/
US design system
https://designsystem.digital.gov/how-to-use-uswds/
Beercss
https://github.com/beercss/beercss


run app from android studio issue on macOS

when i run app from android studio, it will stop at 'installing app ....', but it's actually installed and it can receive debugPrint output.it cause hot reload will not be performed

[✓] Flutter (Channel master, v1.4.13-pre.5, on Mac OS X 10.13.6 17G65, locale
    zh-Hans-CN)
    • Flutter version 1.4.13-pre.5 at /Volumes/资料/flutter/flutter
    • Framework revision ed49122aa3 (25 hours ago), 2019-04-08 20:22:34 -0700
    • Engine revision ff1bcdc009
    • Dart version 2.2.1 (build 2.2.1-dev.3.0 None)

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /Users/mac/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling
      support)
    • Platform android-28, build-tools 28.0.3
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_152-release-1248-b01)
    • All Android licenses accepted.

[✓] iOS toolchain - develop for iOS devices (Xcode 10.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 10.1, Build version 10B61
    • ios-deploy 1.9.4
    • CocoaPods version 1.6.1

[✓] Android Studio (version 3.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 33.1.1
    • Dart plugin version 182.5215
    • Java version OpenJDK Runtime Environment (build
      1.8.0_152-release-1248-b01)

[!] Proxy Configuration
    • HTTP_PROXY is set
    ! NO_PROXY is not set

[✓] Connected device (1 available)
    • Google • <IP_ADDRESS>:5555 • android-x86 • Android 9 (API 28)

! Doctor found issues in 1 category.

it also can be reproduced in stable channel

everything is ok on windows10

Hi, sorry for the delay, I just want to check if you could solve this problem.

Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.


Add plugin: hexo-next-darkmode

Check List
Please read and check followings before submitting a PR.

[ ] I want to publish my theme on Hexo official website.

[ ] I have read the theme publishing doc.
[ ] name is unique.
[ ] link URL is correct.
[ ] preview URL is correct.
[ ] preview URL web site is rendered correctly.
[ ] Add a screenshot to source/themes/screenshots.
[ ] Screenshot filename is same as value of name.
[ ] Screenshot size is 800 * 500.
[ ] Screenshot file format is png.

[x] I want to publish my plugin on Hexo official website.

[x] I have read the plugin publishing doc.
[x] name is unique.
[x] link URL is correct.

[ ] Others (Update, fix, translation, etc...)

Languages:
[ ] en English
[ ] ko Korean
[ ] pt-br Brazilian Portuguese
[ ] ru Russian
[ ] th Thai
[ ] zh-cn simplified Chinese
[ ] zh-tw traditional Chinese

If it’s just next theme support, I think you’d better submit a PR to https://github.com/next-theme/awesome-next


Ensure that meta-data can be unselected for all API routes

Even if you un-select the include metadata option in the download form, this path still returns the metadata header. Metadata should not be returned for any route if not selected as part of the data form.
https://paleobiodb.org/data1.2/occs/taxa.txt?rank=max_genus&interval=Phanerozoic&limit=100

This will be fixed in next week's update. The summary material will only appear in downloads if the "metadata" box is checked (or, equivalently, if the 'datainfo' parameter appears in the download URL). Otherwise, in CSV format, the header line will be the first line of the output.

That's great news, but I was under the impression that you were hesitant to fix this until 1.3 because it could technically be a breaking change for some people?


Reintegrate narrowed inference checks for number and bigint literals

Once we migrate and can update our TS version for our demos, these checks should be reenabled:
https://github.com/arktypeio/arktype/blob/91b7631ed8c5a7452621e20e4b4d1e29a4b8df4a/src/parse/string/shift/operand/unenclosed.ts#L74
https://github.com/arktypeio/arktype/blob/91b7631ed8c5a7452621e20e4b4d1e29a4b8df4a/dev/test/unenclosed.test.ts#L67
https://github.com/arktypeio/arktype/blob/91b7631ed8c5a7452621e20e4b4d1e29a4b8df4a/dev/test/unenclosed.test.ts#L121

Also need to reenable TS 4.8 tests, as we  had to disable them due to an infinite loop in ts-morph related to the changes we made above

Now that StackBlitz supports TS4.9 in their default EngineBlock project, these checks can be reintegrated.


Split directus url to server and client urls.

Is your feature request related to a problem? Please describe.

Currently I'm working on creating separate dev enviroment fully runing in docker (nginx, node app, directus). When nitro server is calling directus for the initial page load it is unable to access it via domain ex. "localcms.example.com". It must use different docker container name ex. "directus". Changing it via runtimeConfig to "directus" causes redirecting to different page on client side to not work.
Unfortunatully I'm unable to set different url's for server and browser, this does not allow me to proceed with my app.
Describe the solution you'd like

In useDirectusUrl.ts I would like to add condition to check if process is running on server and based on this use either server url or client url. If server url is not provided then it uses previous url that can be setup in runtime config, so it won't be breaking change.
Describe alternatives you've considered

I've tried to setup docker and nginx to allow me to always use domain not container name. But I found it impossible to do. Same for setting different addresses in nuxt directly.
Additional context

Cannot think of anything more.

Currently I'm working on creating separate dev enviroment fully runing in docker (nginx, node app, directus).

Could you describe a bit more your current and desired deployment? How are you configuring your direcuts url? Do you have any reproduction to share?
The other nuxt-directus maintainer's could correct me and probably provide a better opinion than mine, but in the meantime I could reply in regard of Nuxt and Docker/Kubernetes:

In useDirectusUrl.ts I would like to add condition to check if process is running on server and based on this use either server url or client url. If server url is not provided then it uses previous url that can be setup in runtime config, so it won't be breaking change.

Unfortunately the process of separating server/client execution is not simple as "black" and "white". IIRC, for example, there are a number of calls during server hydration and initial state management that are made server side but passed as-is to client side, potentially breaking SSR for things like image/file urls that require authentication. Not to mention a number of deployment specific optimization that Nitro/Nuxt do for each type of environment, potentially requiring further edge cases.

I've tried to setup docker and nginx to allow me to always use domain not container name. But I found it impossible to do. Same for setting different addresses in nuxt directly.

Docker/Kubernetes on the other hand, when configured properly with reverse proxies (I imagine nginx in your case), will assign localcms.example.com as a domain for that container too (effectively acting like the container name itself). So unless the Nitro call is proxied outside your Docker stack, or worst the Docker Stack itself isn't aware of that external domain (for example using only port binding), everything should work correctly so there must be something else.

Could you describe a bit more your current and desired deployment? How are you configuring your direcuts url? Do you have any reproduction to share?

Currently I have node app running on my local machine, and every request is made via localhost and port. Also every dev that would like to start working on this project will have to setup correct node version etc. I don't like it and I would like to move whole dev enviroment to docker. I've runed into the problem where either reloading page is not working or redirecting to different page is not working.
My configuration is via .env:
NUXT_PUBLIC_DIRECTUS_URL = http://localcms.example.com (This works when I'm redirecting to different page)
NUXT_PUBLIC_DIRECTUS_URL = http://directus:8055 (This works when reloading page (Directus is container name))
I don't have any reproduction repo but I will create one. After I fail to implement it via docker config.

Not to mention a number of deployment specific optimization that Nitro/Nuxt do for each type of environment, potentially requiring further edge cases.

You are right. I didn't think of that. I will try to test it with change that is currently working for me:

Docker/Kubernetes on the other hand, when configured properly with reverse proxies (I imagine nginx in your case), will assign localcms.example.com as a domain for that container too (effectively acting like the container name itself).

I will try this.

So we are talking about a full local stack deployment for dev only right? What is nginx for then?
Since we are talking about a local Docker deployment if you are using Docker Desktop you might use the internal resolver that comes with it (you could look at it as a localhost replacement):
NUXT_PUBLIC_DIRECTUS_URL = 'http://host.docker.internal:8055'

Yes, I wanted to create full local dev stack. Nignx was needed so that I don't have to install nginx on my local machine and still use domains on windows without creating some workarounds/extended config. I've tried creating container network which didn't work and assigning static ip to container to then alter hosts file in one of them is just not ideal solution, so I droped both.
This worked like a charm:
NUXT_PUBLIC_DIRECTUS_URL = 'http://host.docker.internal:8055'

But I had to expose port 8055 which I didn't want to do initially but It looks like it is needed in this case. There wasn't any reason for me to not want to expose it other that just exposing less to omit feature problems.
Thanks for help! I think we can close this feature request as it is no longer needed I think.


BSOD issues (xBrowse's BSOD):

^^ bsod of xbrowse
Causes if browse is not starting in 15seconds
---Known Issues
--Sometimes BSOD appears then app starts (huh what?)

would be fixed soon i g from my end


Support for lateral join on query builder

We love your work and titbits on twitter.
Recently, we had an usecase to implement lateral join in laravel. Since it is specific to Postgres grammar, we used raw query to implement in our project.
Do you have any plan to extend postgres query builder in future? For example: lateral join with query builder.

Thanks for the feedback ❤
I am open to almost any feature anyone may need. Lateral joins are a nice feature and I am using them too and needed to go back to raw queries. But they are not as easy to implement.
I currently see two possible ways of adding them:

I add the joinSubLateral, leftJoinSubLateral, rightJoinSubLateral and crossJoinSubLateral methods
I check whether my pull request to Laravel 9 for improved query expressions can be used to implement lateral joins.

I, personally, would prefer the second case with an API like the following, but I have to check whether this will really work:
$subquery = DB::table('table2)->...();

DB::table('table')
  ->joinSub(new LateralQuery($subquery))
  ->...();

I really liked the idea of supporting lateral subquery joins as I am using them too. Query expressions did not work because of how laravel does encapsulate subqueries.
I've added crossJoinSubLateral, joinSubLateral and leftJoinSubLateral. Each one has the same behavior as their Laravel counterparts, but now they are lateral subquery joins.


xcode9正式版上报错

New Issue Checklist
🚫 If this template is not filled out your issue will be closed with no comment. 🚫

[ ] I have looked at the Documentation
[ ] I have read the F.A.Q.
[ ] I have filled out this issue template.

Issue Info

Info
Value

Platform
e.g. ios/osx/tvos

Platform Version
e.g. 8.0

SnapKit Version
e.g. 0.19.0

Integration Method
e.g. carthage/cocoapods/manually

Issue Description
⚠ Replace this with the description of your issue. ⚠

As per issue template this issue is being closed due to containing no content.


fix for plan deletion

Fixes #2643 .
Changes proposed in this PR:

set the Plan's org_id to that of the Role record's user if it is not set

Ideally the upgrade:v2_2_0_part1 upgrade task would have been run and none of the Plan records would have a nil org_id. This addresses the issue though for scenarios where the plans.org_id is nil for some reason.

Thanks @briri
We refreshed the data on the test server before deploying out the Rails5 work, but I don't think we ever ran through the migration tasks when upgrading that.


YAML 1.2 support

Since no practical and theoretical needs in this feature - i close this ticket. If anyone ever interested - implement it and do pull-request.


DB Connection

avramirez: all settings are correct but am getting the error
Unable to connect to your database server using the provided settings.
Filename: core/Loader.php
Line Number: 346

Wow this project is two years ago. I didnt even think someone will try it.
system/core is code igniter code.
Are you sure your DB Settings is correct? Post it here

me tooo sir! ahaha.

ahahahaha @jorelkimcruz  you help him ahahaha


added pr template

issue: #13
@diyajaiswal11
can you  please add appropriate tags to issue and pr? the tags that you have added to the issue is not correct.

@diyajaiswal11 can you please review this pr and please add gssoc21 and level tags to both issue and pr I think the way u have taged gssoc is not gonna count so please change that

@diyajaiswal11 can you please review this pr and please add gssoc21 and level tags to both issue and pr I think the way u have taged gssoc is not gonna count so please change that

Make the following changes :

Please correct the spelling of issues in the first line.
Remove the screenshots section as it may not be required in all the cases.

@diyajaiswal11 I have updated it can you please add gssoc21 and a level tag to both this pr and its issue.


Refactor: refresh views should return proper JSON, not HTML-in-JSON

Even though it is a nice feature, it is bad coding style in my opinion. The JSON API should deliver proper JSON

Why not just implement django-rest-framework and use a proper API


AtomicUpdateFileOutputStream does not work on Windows

On Windows, need to avoid using it.

Fixed in 3db65c0.


Reset button on Web interface returns 404

The "Reset" button on the throttled interface returns a 404 Not Found though everything else on the Throttled page looks correct. Any ideas on what to check?

What is sidekiq and sidekiq-throttled version are you using?

Sidekiq 4.2.10
sidekiq-throttled 0.7.2

I was able to reproduce that. Thanks for the report. Will find solution ASAP

So, we add delete action. According to specs, that delete action works perfectly correct. There's one trick about DELETE verb. There's no way to "issue" that verb using simple html attribute, so usually either XHR is used, or magic _method param is passed instead as part of POST form.
So, after sidekiq moved away from sinatra, I believe they have dropped support of that magic param. And most likely the solution is to simply replace method="post" with method="delete" for the form of the reset button. Although I'm not sure if that will be the right solution. So far I believe going the most dumb way will be better:

bind action to post instead of delete
change action's url to be throttled/{id}/reset


Add ssl or tls connection for sending email.

Add a secure connection for sending email.
** Currently the email sent through this code is not secure.**

I can pick this up.


Allow direct html-representation for SEO

Currently, a Tapspace user interface generates HTML purely from JavaScript data structures. Therefore the initial HTML page downloaded from a server is void of content. Some search engine bots, crawlers and clients with JS disabled do not execute javascript. Although at least Google has done so for years. They see only the blank page.
Should Tapspace be able to read plain html markup and construct the space from it? Data-attributes can be used to define transformation, size, and interaction mode. However, complex applications still require additional JS code. For example, consider a tap handler that rotates the item by 90 degrees.
For just browsing purposes the plain html markup might be enough. However, in practice, not everything can be downloaded at once. It is out of the scope of Tapspace to set in stone how the dynamic content retrieval happens. Let us let the issue sink in for a while...

It would feel awkward to parse an abstract tree from html and generate something from that on Canvas or WebGL. Direct html-representation pushes us toward removing the multiview feature, and SpaceView too. A major reason for their existence is the possibility of having a SpaceViewCanvas and SpaceViewWebGL.

In v2, the affine DOM and the normal DOM have 1:1 correspondence. Therefore it is possible to render HTML structures directly to document for SEO benefits and then move the elements to the space when the library and app code runs.


Dark Mode for the website?

I just wondering if the dark/night mode for the website is possible?

No plans for it atm, but you are welcome to send pull req


Domain activation is Failed

App Id: d2xdzjxsgfm9x3
Region: eu-west-1
Step: Domain activation
Status: Failed
Issue
Domain activation does not work because it says it incorrectly that my DNS record that points to another CloudFront distribution.
Steps:

Because I did not have direct access to the DNS, it took a long time to add the records to the DNS.
The verification process timed out.
And because the Retry button never works, I had to delete the domain and add it again
After 5 attempts I could finally delete the domain.
I cannot activate the desired subdomain name at this time, because there is probably a distribution somewhere that is not cleaned up.
I am 100% sure that there is not somewhere a CloudFront distribution on our side.

Error message
One or more aliases specified for the distribution includes an incorrectly configured DNS record that points to another CloudFront distribution.
Additional information

My Amplify App should only run on a subdomain, not the root.

@swaminator @nimacks What can I do best to resolve this?
I have sent several emails to<EMAIL_ADDRESS>, never received an answer
I created this issue on Github
I have waited as mentioned more than 6 hours.
Do I have to purchase technical support from AWS? While the Amplify Console is clearly not working?

@daannijkamp , Sorry for the delay in getting back to you. Your account has two custom domains attached to it. The first one is active and I can confirm that I was able to visit the site without issue. Your second custom domain however is having issues and returns the message CNAMEAlreadyExistsException. Can you confirm that you were looking to setup two different domains to point to the same app?

That's correct.
amplifyapp.our-company-name.com
(For testing and portfolio purposes, active and and is currently working)
amplifyapp.customers-company-name.com
(customer's production environment, not working and returns the CNAMEAlreadyExistsException)
Do you think two different domains for the same app is the issue?

Hi, I searched your domain CNAME record. Looks like it's already attached to a CloudFront distribution: d1cvpwo3qmpa4m.cloudfront.net.
You could use whatsmydns tool to see details.
Link: https://www.whatsmydns.net/#CNAME/${Your custom domain}
Please delete the domain in that app first and try to attach it again.

@nimacks @swaminator @garyleefight As far as I understand now, I have found the potential problem. Tip, maybe you can make the following sentence red. Instead of in font size of 8px and light gray.

Please wait till your domain status becomes AVAILABLE before updating your DNS provider

@daannijkamp Glad you figured it out. I contacted with CloudFront team. You have a "dangling" DNS record that points to a distribution that doesn't exist in CloudFront in this case. This is the solution:
If your DNS record points to a distribution that is not the distribution that you are creating or modifying, then you can't add the alternate domain name to your distribution. In this scenario, you must update your DNS at your DNS provider before you can add the domain name for your CloudFront distribution.
For further information:
https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/troubleshooting-distributions.html
https://docs.amazonaws.cn/en_us/AmazonCloudFront/latest/DeveloperGuide/CNAMEs.html#alternate-domain-names-remove-domain
https://aws.amazon.com/premiumsupport/knowledge-center/resolve-cnamealreadyexists-erro

@garyleefight Thanks for your help!
Some extra information to improve the user experience:
If the verification process gets stuck and the retry button does not work again, the only option is to delete the domain and add it again.
When you do this, you will see the same old cloudfront domain with "View DNS".
That is why I assumed that the cloudfront domain was not going to change.


Consider ditching file manager logging proxy

Consider removing the file manager logging proxy, and implement logging in PathFileManager directly under debug/trace.
Remove the config options for file manager logging as well.

Going to keep this for now and re-open closer to when this project is nearer a releasable state, if I still think this is going to be an improvement.


Fix definition of Krikri::Harvester.entity_behavior

Move the definition of Krikri::Harvester.entity_behavior to the included block, because Harvester is a mixin.
Add a test to ensure that a class mixing in Harvester receives Krikri::OriginalRecordEntityBehavior from a call to .entity_behavior.

:+1: Will merge if CI is happy.

Noting that Travis showed some unusual Solr problems when running this branch. It looks like a Travis container and/or networking issue, but we should look out for similar errors once this is merged.


Add ETL exercise

I think this one is pretty good for JSON handling.

Btw you don't need to mark these as x:size/large, they take me about 10 minutes lol


Error on install, not work config module ()

Error on install:
Integrity constraint violation: 1062 Duplicate entry '75-974-1' for key 'PRIMARY'
The config page for the module does not work.

Install on PS 8.1.2 with PHP 8.1.23 and apache 2.4.52.
Many thanks !!!

Hello @Luifer-dnk
Could you try latest release ?
https://github.com/TeamEver/everpsblog/releases/tag/V5.5.11
This should resolve the issue

Same error on intall:

But now i can access at config page.
I test on two install clean.
Many thanks !!!

Good morning
Could you try with the latest release available here?
https://github.com/TeamEver/everpsblog/releases/tag/V5.6.1
Thanks in advance

Good morning Could you try with the latest release available here? https://github.com/TeamEver/everpsblog/releases/tag/V5.6.1 Thanks in advance

On front office.

Fixed:
Add private on class:

Hello @Luifer-dnk
I've just committed fix, thanks for all 👍

Working !!!


Look at support for threaded servers

Add support for setting up the stack via pytest-httpbin.
https://github.com/kevin1024/pytest-httpbin/blob/master/pytest_httpbin/serve.py
This should be relatively simple:

Add a registration utility to work with pytest-httpbin
wrapper to convert the stack to/from a WSGI  app that can be served with pytest-httpbin

Note: This would probably solve the asyncio style cases since the stack would actually be a "normal" server.

Closing this as https://github.com/TestInABox/stackInAWSGI will actually solve this use case as described.


[FLINK-6280] [scripts] Allow logging with Java flags

Evaluate user-defined Java options immediately before starting services and rotate all log files.

Can you explain a bit more what this change does exactly? Does it make sure that if you put bash commands into the java opts to compute flags, it evaluates those?
Can you elaborate why this needs a change in the log rotation logic?

I had provided some examples in the JIRA, but yes, it allows delaying evaluation of the java opts (with double quotes) until immediately before the daemon is started. This allows creating additional log files such as for JFR or JitWatch (the two use cases I have needed, I expect there are more). In addition the log rotation, Flink may be running multiple TaskManagers on the same instance so reusing Flink's log naming scheme prevents overwriting files.

@StephanEwen added some documentation covering use and examples.

Okay, got it. The docs and examples did help a lot.
This looks good to me, +1 to merge

Feel free to merge...


Is compiler-rt really necessary for oneMKL; could there be an alternative?

compiler-rt is not built by default using the standard configure.py script from https://github.com/intel/llvm , it takes a long time to build.
However compiler-rt is currently required by at least some oneMKL backends, see https://github.com/oneapi-src/oneMKL/issues/336
I have no idea to what extent compiler-rt is used. If this dependency could be removed easily then it would make the process of building oneMKL from open source much more straightforward.

@sbalint98 or @TejaX-Alaghari do you have any insights into this question?

Sorry, I should close this. compiler-rt is required by rocm (see https://github.com/intel/llvm/issues/10612#issuecomment-1664149574), so this nothing that can be changed by oneMKL.


slow build

I am seeing very slow build times. Is everything being re-compiled or just the changed elements?
[14:42:31] Starting 'reload'...
[BS] Reloading Browsers...

[BS] Reloading Browsers...
[BS] Reloading Browsers...
[14:44:46] Finished 'reload' after 4.78 ms

Dupe of #141
Yes it's very frustrating!


Added verify_peer property to provider.

While using this provider I ran across an issue that required me to be able to set the verify peer option for Puppet::Network::HttpPool.http_instance to false.  By adding it as a parameter with a default of true, normal behavior if the option is left off, I added the functionality.

From what I can tell... LGTM.  Shame we don't have any spec tests yet.


Fixed windows close bug

Ended up being a simple fix, but it was tough to find.  The screenshot needs to be generated before the interactive renderer starts.

Awesome, thank you for figuring this out!!


dependency update

Please update dependencies due to CVEs :
scala-library-2.10.4.jar                                                                            | CVE-2017-15288
log4j-core-2.0-rc1.jar                                                                              | CVE-2017-5645, CVE-2020-9488

Done. Release to sonatype pending.

Published release

maven part of the readme does not seem to be updated....

That's true. I updated it by now. Thank you!