Onboard  Meshery

Use Case
Meshery is CNCF playground
A self-service engineering platform, Meshery, is the open source, cloud native manager that enables the design and management of all Kubernetes-based infrastructure and applications (multi-cloud). Among other features, As an extensible platform, Meshery offers visual and collaborative GitOps, freeing you from the chains of YAML while managing Kubernetes multi-cluster deployments.
Ideas of Implementation

Additional Info

Message from the maintainers:
Excited about this feature? Give it a :thumbsup:. We factor engagement into prioritization.

Will try to add it when @michaeljguarino adds it to the application roadmap


Update peserta.md

Modul 2:

[x] Tugas 1
[x] Tugas 2
[x] Tugas 3
[ ] Tugas 4

Tenggat tugas: 20 September 2016

You've met the requirements for Modul 2.
However,  this pull request has a conflict , because someone else's entry has been committed since your created your pull request.
You can manually resolve this by fetching the repo, and git rebaseing your patch (not easy, but a good way to learn git ;-)), or you can cheat and edit the master to create a new pull request.

registration period ended 20 September 2016


【ui】With Hwameistor, you can migrate without selecting a source node first, just click to start

version：hwameistor-operator:v0.14.4

Yes, error should be catched and showen to user when source node has't specified.
{"errcode":203,"description":"SrcNode cannot be empty or cannot be string"}


Replace backtick in run-vault with single quote

Backticks causing unexpected behavior
Removes backticks in favor of single quote to match other items in the
list
Credit to @BonzTM in #77 for initially finding/fixing; isolated to get
fix merged

Build info is here: https://circleci.com/gh/hashicorp/terraform-aws-vault/215
@Etiene Any idea what this test failure is all about? Specific log file is at https://215-103201301-gh.circle-artifacts.com/0/tmp/logs/TestMainVaultCluster.log. Relevant part seems to be:
        			Error Trace:	vault_helpers.go:136
        			            				vault_cluster_enterprise_test.go:60
        			            				test_structure.go:24
        			            				asm_amd64.s:509
        			            				panic.go:366
        			            				testing.go:544
        			            				testing.go:582
        			            				retry.go:56
        			            				vault_helpers.go:398
        			            				vault_helpers.go:233
        			            				vault_cluster_enterprise_test.go:131
        			            				vault_cluster_enterprise_test.go:76
        			            				test_structure.go:24
        			            				vault_cluster_enterprise_test.go:72
        			            				vault_main_test.go:131
        			Error:      	"map[i-0e9f6fdd1fa5ac7d8:map[/opt/vault/log/vault-stdout.log:Error loading configuration from /opt/vault/config: error loading "/opt/vault/config/default.hcl": error parsing 'seal': 1 error occurred:

        			            	* seal.awskms: invalid key "endpoint" on line 5
        			            	Error loading configuration from /opt/vault/config: error loading "/opt/vault/config/default.hcl": error parsing 'seal': 1 error occurred:

        			            	* seal.awskms: invalid key "endpoint" on line 5
        			            	Error loading configuration from /opt/vault/config: error loading "/opt/vault/config/default.hcl": error parsing 'seal': 1 error occurred:

        			            	* seal.awskms: invalid key "endpoint" on line 5
        			            	Error loading configuration from /opt/vault/config: error loading "/opt/vault/config/default.hcl": error parsing 'seal': 1 error occurred:

        			            	* seal.awskms: invalid key "endpoint" on line 5
        			            	 /opt/vault/log/vault-error.log: /var/log/syslog:Dec 10 16:26:51 ip-172-31-21-17 rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="1049" x-info="http://www.rsyslog.com"] start
        			            	Dec 10 16:26:51 ip-172-31-21-17 rsyslogd-2222: command 'KLogPermitNonKernelFacility' is currently not permitted - did you already set it via a RainerScript command (v6+ config)? [v8.16.0 try http://www.rsyslog.com/e/2222 ]
        			            	Dec 10 16:26:51 ip-172-31-21-17 rsyslogd: rsyslogd's groupid changed to 108

The change introduced in #117 added the endpoint attribute to the config; but this is only available in Vault OSS 1.0.0 and Enterprise.  Perhaps the config entry for endpoint wasn't supported in enterprise?
Based on https://github.com/hashicorp/vault/commit/3d1f0d76c07a5584a6d6268a7419bb6bd0809320 it seems endpoint may be a new feature.

@briandbecker you are correct! thanks for catching this. I'm adding a fix in PR #122


[Suggestion] DataFrame.to_tensor function?

When playing around with Scholar/Explorer/Nx I find myself converting my explorer dataframe into an nx tensor in order to feed it into Scholar to train a model.
I end up writing code that looks like this:
train_split_names = Explorer.DataFrame.names(train_split)
train_series_split = Explorer.DataFrame.to_series(train_split)

Enum.reduce(train_split_names, train_series_split, fn n, acc ->
  acc = Map.replace!(acc, n, Explorer.Series.fill_missing(acc[n], :mean))

  if Explorer.Series.dtype(acc[n]) == :string do
    Map.drop(acc, [n])
  else
    Map.replace!(acc, n, Explorer.Series.to_tensor(acc[n]))
  end
end)

I think this should be moved to a DataFrame.to_tensor function.
I'd love to know what the community thinks!

Please see this commit that does precisely that: https://github.com/elixir-nx/explorer/commit/6c84747c13c66e0278ffca8cead128b3875697c4 - it requires latest Nx and Explorer.

Ah, and this issue #507 is to help with filling missing.


Better error message when calling a function that doesn't have a return type set

my code is
function main (string[] args) {
  system:println(getEmployees());
}

function getEmployees() {
  .....
  json employees = messages:getJsonPayload(response);
  return employees;
}

for this I get the error message
foo.bal:6: undefined function 'system:println
which is not that descriptive.

in v0.89 above program throws the bellow error:
ballerina: unexpected error occurred

Tested with below code with 0.95.0 version and it is having descriptive error message.
function main (string[] args) {
  println(getEmployees());
}

function getEmployees() {
  json employees = {name:"apple"};
  return employees;
}

Error message:
error: ../samples/testissue.bal:2:11: assignment count mismatch: expected 1 values, but found 0 error: ../samples/testissue.bal:7:3: return value is not expected


Server side rendering broken since Sep 20th commits

/node_modules/quill/dist/quill.js:2245
var elem = document.createElement('div');
ReferenceError: document is not defined

You'll probably want to file this issue upstream with Quill. The calls to document are in the core editor module.
https://github.com/quilljs/quill/search?utf8=✓&q=document.createElement

@alexkrolick is correct, Quill is tightly coupled to the browser at the moment.
What could be done is to render only a <textarea> on server side. This should be easily accomplished in user code, but I guess we could see if it's possible to add some support here.

I was able to work around this limitation by instantiating react-quill only on the client. Note that import only works on the top level, so I use require.
I imagine the maintainers of this module should be able to prevent calls to the DOM when it's not available, without too much trouble. Big +1 for that change.
Here's my wrapper component to support isomorphic rendering:
import {Component} from 'react'

export default class FormHtmlEditor extends Component {
  constructor(props) {
    super(props)
    if (document) {
      this.quill = require('react-quill')
    }
  }

  render() {
    const Quill = this.quill
    if (Quill) {
      return (
        <Quill
          name={this.props.name}
          theme="bubble"
          value={this.props.value}
        />
      )
    } else {
      return null
    }
  }
}

Yes, ES6 modules are static. You can still probably detect document in the render though:
import React, {Component} from 'react'
import Quill from 'react-quill'

export default class FormHtmlEditor extends Component {
  constructor(props) {
    super(props)
  }

  render() {
    if (document) {
      return (
        <Quill
          onChange={this.props.onChange}
          theme="bubble"
          value={this.props.value}
        />
      )
    } else {
      return null
    }
  }
}

Not sure if we want to add support to the module directly, though - seems a bit too automagicky to me at the moment.

All of my components are bundled up with WebPack and sent from the server using renderToString. When quill is included in the server side bundle via import my server crashes with the folowing output:
/path/to/src/node_modules/quill/dist/quill.js:2377
  var elem = document.createElement('div');
             ^

ReferenceError: document is not defined
    at Object.<anonymous> (/path/to/src/node_modules/quill/dist/quill.js:2377:13)
    at __webpack_require__ (/path/to/src/node_modules/quill/dist/quill.js:36:30)
    at Object.<anonymous> (/path/to/src/node_modules/quill/dist/quill.js:1669:2)
    at __webpack_require__ (/path/to/src/node_modules/quill/dist/quill.js:36:30)
    at Object.<anonymous> (/path/to/src/node_modules/quill/dist/quill.js:76:15)
    at __webpack_require__ (/path/to/src/node_modules/quill/dist/quill.js:36:30)
    at Object.defineProperty.value (/path/to/src/node_modules/quill/dist/quill.js:7798:14)
    at __webpack_require__ (/path/to/src/node_modules/quill/dist/quill.js:36:30)
    at Object.<anonymous> (/path/to/src/node_modules/quill/dist/quill.js:63:19)
    at __webpack_require__ (/path/to/src/node_modules/quill/dist/quill.js:36:30)

My hack as above using require was to work around this crash.

this is how to check if it run in a browser or not (i changed a code from @calvintennant ):
import React, { Component } from 'react'

export default class FormHtmlEditor extends Component {
  constructor(props) {
    super(props)
    if (typeof window !== 'undefined') {
      this.ReactQuill = require('react-quill')
    }
  }

  render() {
    const ReactQuill = this.ReactQuill
    if (typeof window !== 'undefined' && ReactQuill) {
      return (
        <ReactQuill
          onChange={this.props.onChange}
          theme="bubble"
          value={this.props.value}
        />
      )
    } else {
      return <textarea />;
    }
  }
}

I used if (!__SERVER__) instead, looks cleaner

Example of workararounds in Next.js to use React Quill , use  Quill.import, etc.
`import PropTypes from 'prop-types'
import styled from 'styled-components'
import 'stylesheets/richtexteditor.scss'
const modules = {
toolbar: [
[{ header: [false, 1, 2, 3, 4, 5, 6] }],
['bold', 'italic', 'underline', 'strike', 'blockquote'],
[{ list: 'ordered' }, { list: 'bullet' }, { indent: '-1' }, { indent: '+1' }],
['link'],
['clean']
]
}
const formats = [
'header', 'bold', 'italic', 'underline', 'strike', 'blockquote',
'list', 'bullet', 'indent', 'link'
]
const EditorWrapper = styled.div`
background: #fff;
min-height: 230px;
.quill {
min-height: 230px;
.ql-container,
.ql-editor {
  min-height: 187px;
}

}
`
const modifyLink = (Quill) => {
const Link = Quill.import('formats/link')
class MyLink extends Link {
static create(value) {
const node = super.create(value)
value = this.sanitize(value) // eslint-disable-line no-param-reassign
node.setAttribute('href', value)
if (value.startsWith('/')) {
node.removeAttribute('target')
}
return node
}
}
Quill.register(MyLink)
}
export default class RichTextEditor extends React.Component {
static propTypes = {
value: PropTypes.string
}
constructor(props) {
super(props)
if (typeof window !== 'undefined') {
this.ReactQuill = require('react-quill') // eslint-disable-line global-require
}
this.state = {
text: props.value,
isLoading: true
}
this.handleChange = this.handleChange.bind(this)
modifyLink(this.ReactQuill.Quill)
}
componentDidMount = () => {
this.setState({ isLoading: false })
}
handleChange(value) {
const { props } = this
props.onChangeEditor(value, props.name)
this.setState({ text: value })
}
render() {
const { ReactQuill, props, state } = this
const { text } = this.state
if (state.isLoading) {
  return null
}

return (
  <EditorWrapper>
    <ReactQuill
      theme='snow'
      modules={modules}
      formats={formats}
      value={text}
      onChange={this.handleChange}
      className={props.hasError ? 'is-danger' : ''}
      name={props.name}
    />
  </EditorWrapper>
)

}
}
`

I wrote this with dynamic module
import { Spin } from 'antd';
import dynamic from 'next/dynamic';

const QuillNoSSRWrapper = dynamic(
  import('react-quill')
  {
    ssr: false,
    loading: () => <Spin />,
  }
);

export default QuillNoSSRWrapper;

I really liked the solution that @yalamber came up with, using next/dynamic, but I want to have the "placeholder" render the content that would eventually be in the editor, so that it shows the content while the page is hydrating. Unfortunately you don't get access to the props that you pass to QuillNoSSRWrapper within the loading component 😦

This is the cleanest method I have found to import modules that use window or document:
const ReactQuill = typeof window === 'object' ? require('react-quill') : () => false;

I wrote this with dynamic module
import { Spin } from 'antd';
import dynamic from 'next/dynamic';

const QuillNoSSRWrapper = dynamic(
  import('react-quill')
  {
    ssr: false,
    loading: () => <Spin />,
  }
);

export default QuillNoSSRWrapper;

this solution makes the situation what re-render when onChange event performed

thanks @bum-hyun.
Do you have an example code on how to implement this module? Where do I import QuillNoSSRWrapper?

This is the cleanest method I have found to import modules that use window or document:
const ReactQuill = typeof window === 'object' ? require('react-quill') : () => false;

// Use ReactQuill as desired

<ReactQuill
  value={value}
  onChange={handleChange}
/>

You are right. But It is not working like textarea. How can ı pass form data via this editor.

How about resize image ?
I'm using quill-image-resize-module, but it's not working with NextJS.

@Kamez you can try this solution. This worked for my application.
In my eventform I had a field like this:
<Field
            name='body'
            component={renderQuill}
            placeholder='Tell your story'
          />

The component renderQuill has the following setup:
renderQuill.js
import React from 'react'
import dynamic from 'next/dynamic'

const QuillNoSSRWrapper = dynamic(
  () => import('./renderQuillReact'),
  { ssr: false, loading: () =>
Loading ...
 },
)

class renderQuill extends React.Component {
  render () {
    const { input, label, type } = this.props
    return (
        <QuillNoSSRWrapper input={input} label={label} type={type}/>
    )
  }
}

export default renderQuill

As you notice I import a second component './renderQuillReact' that contains the resize module.
renderQuillReact.js component
import React from "react";
import ReactQuill, { Quill } from "react-quill";
import ImageResize from "quill-image-resize-module-react"; // import as default
import { ImageDrop } from "quill-image-drop-module";
Quill.register("modules/imageResize", ImageResize);
Quill.register("modules/imageDrop", ImageDrop);

class renderQuillReact extends React.Component {
    render () {

      const { input, label, type } = this.props
      return (
        <ReactQuill
        modules={Event.modules}
        label={label}
        formats={Event.formats}
        {...input}
        type={type}
        onChange={(newValue, delta, source) => {
          if (source === "user") {
            input.onChange(newValue);
          }
        }}
        onBlur={(range, source, quill) => {
          input.onBlur(quill.getHTML());
        }}
      />
      )
    }
  }

Event.modules = {
  toolbar: [
    [{ header: "1" }, { header: "2" }, { font: [] }],
    ["bold", "italic", "underline", "blockquote"],
    [{ list: "ordered" }, { list: "bullet" }],
    ["link", "image", "video"],
    ["clean"],
    ["code-block"]
  ],
  imageDrop: true,
  imageResize: {
    handleStyles: {
      backgroundColor: "black",
      border: "none",
      color: "white"
    },
    modules: ["Resize", "DisplaySize", "Toolbar"]
  }
};

Event.formats = [
  "header",
  "font",
  "size",
  "bold",
  "italic",
  "underline",
  "blockquote",
  "list",
  "bullet",
  "link",
  "image",
  "video",
  "code-block"
];

export default renderQuillReact;

Hope this solution works for you!

@frietkip Thank you very much.

This is the cleanest method I have found to import modules that use window or document:
const ReactQuill = typeof window === 'object' ? require('react-quill') : () => false;

// Use ReactQuill as desired

<ReactQuill
  value={value}
  onChange={handleChange}
/>

I am facing an error saying Can't read the property 'import' of undefined

This is what i did works fine with SSR on next js
import { SPLayout } from '@layout';
import dynamic from 'next/dynamic';
import { FC, ReactElement } from 'react';

const ReactQuill = dynamic(
	() => {
		return import('react-quill');
	},
	{ ssr: false }
);

const Create: FC = (): ReactElement => {
	return (
		<SPLayout>
			<ReactQuill
				value={'test'}
				onChange={e => {
					console.log(e);
				}}
			/>
		</SPLayout>
	);
};

export default Create;

This is the cleanest method I have found to import modules that use window or document:
const ReactQuill = typeof window === 'object' ? require('react-quill') : () => false;

// Use ReactQuill as desired

<ReactQuill
  value={value}
  onChange={handleChange}
/>

This is the best solution! @samlogan Thanks!!

Not using next on my application, and this solution not worked for me.

Same (nuxt3, SSR).. using ES modules, cant use require, and dynamic import() seems to be behaving strangely with a condition..
Just curious, why cant quill just do nothing if its not running in the client?

Following solution works like a charm:
    const QuillNoSSRWrapper = dynamic(import('react-quill'), {
        ssr: false,
        loading: () =>
Loading ...
,
    })
    return(
QuillNoSSRWrapper theme="snow"/>)


Show submitted transaction that hasn't made to mempool

When a transaction was submitted and it hasn't made it to the mempool yet, the explorer shows a 404. It'd be better to have a new state for a tx that reflects this.
It's related to issue on the wallet https://github.com/hirosystems/stacks-wallet-web/issues/2467

@He1DAr please check what's the deal with this one

It looks like it's an API issue https://github.com/hirosystems/stacks-blockchain-api/issues/1231


Added a New Landing Page Called: Personal Site

Included another landing page project for a Personal Site. This site contains all about the user, their introduction, experience, hobbies, contact, etc.

This is great just in your project make a link back to /index.html for ease of navigation


[BUG] adorable.io is down - might want to look at an alternative.

Describe the bug
While setting up reverse-proxying with NGINX, I used the dev tools to spot if there was anything I hadn't forwarded correctly. Whilst I got everything right, I noticed that api.adorable.io was refferenced - but visiting the domain gave me an error that the DNS name could not be looked up. That, as well as the link given on their Twitter page - both are not reachable.
To Reproduce
Steps to reproduce the behavior:

Open the dev tools
Log in
You now have an error in your console! :)

Expected behavior
A cute avatar. Possibly a bird!
Screenshots

Desktop (please complete the following information):

OS: Windows 10
Browser Opera GX
Version ... latest? Shouldn't matter here anyway. o.o

Additional context
... None I could think of.
Client Log:
... See screenshots. ...

Server Log:
... client-side issue, no server logs needed. ...

this is fixed in master, not released yet

Cool, thanks for letting me know! :)


Add option to copy citation key to clipboard

Create an easy-to-access bib file only repository and provide citation keys as part of each publications' page, so people can use our bib file for their work.
See: https://twitter.com/damiano10/status/1421469676949762051?s=19

Create an easy-to-access bib file only repository
could you explain this in more detail?


best way to combine device-tree interfaces with uDeviceCfg_t in zephyr

Hello,
I noticed that uDeviceCfg_t has more properties than the one in the device tree. for example, pSimPinCode can be set only by the uDeviceCfg_t  structure but not by the device tree. what is the best way to combine properties of uDeviceCfg_t  structure with the device-tree when uDeviceOpen is called since we must pass NULL to uDeviceOpen if device interface is declared in device-tree?
Thank you in advance!

Hi: all of the device and network configuration items that have an effect in the uDeviceCfg_t, uNetworkCfgCell_t, uNetworkCfgGnss_t, uNetworkCfgWifi_t and uNetworkCfgBle_t structures should be settable through the device tree.  The SIM PIN code is not there only because it has to always be set to NULL; we added it to the uDeviceCfg_t structure when we first created it years ago because it seemed logical but ubxlib has never supported setting a SIM PIN (the SIM PIN does not offer any security to speak of as it ends up being sent transparently over a serial port every time the cellular module is powered on).
So it should be possible to do everything you need to do through the device tree; let us know if not.

@mos216: are you OK to close this one now?

Yes sure! thanks again!


perf: ⚡ maybe optimize a bit compiler core

replace some unnecessary template literal

Thanks for the PR but the optimizations do not provide substantial improvements. Closing as stale.


Newly saved config doesn't appear in the list

After typing a new name and clicking 'Save' nothing appears to happen. So I clicked save multiple times...
It wasn't until I left the Load/Save screen and came back again later that I discovered there were now multiple copies of the config I'd saved.
Suggestion: Upon a successful 'Save' the name input box should be emptied and the list of saved configuration names should be immediately updated.
Optional: The config name that was just saved should be highlighted / different color in that list to help make it more obvious that the file was saved.

Right now the text box is filled/stays filled based on which file is selected in the list. Saving a file should add it to the list and highlight it (fix incoming, I missed a func call). I'll be making some more changes to the save/load menu in future updates, but for 1.4 the menu should be functional after this fix. Thanks for reporting.


Google api building error for speech to text

Hi,
I included google , INSTALL-COCOAPODS files in my project. It used to work before.
After updating to Xcode 11, Im getting following errors.
Pods/Target Support Files/gRPC/gRPC-umbrella.h:18:9: include of non-modular header inside framework module 'GRPCClient'
gRPC-ProtoRPC/src/objective-c/ProtoRPC/ProtoRPCLegacy.h:19:9: could not build module 'GRPCClient'
google/longrunning/Operations.pbrpc.h:6:9: could not build module 'ProtoRPC'
I have tried cleaning pods but still not working.

I also have this problem for iPhoneX, iOS 13.1.3

@fiazhussain43  do the following changes in googleapis.podspec
s.dependency "!ProtoCompiler-gRPCPlugin", "~> 1.20.0"
Downgrading gRPCPlugin to 1.20.0 fixed the problem and also use pod version 1.7.5


Using RabbitMQ insted of in-memory bus and execute asynchronous command

Hi,
@kgrzybek Thanks for your great project.
I have a question in my mind, why you don't use RabbitMQ for your message broker insted of in-memory command bus and also use of RabbitMQ for handling asynchronous command insted of hangfire?

You can use RabbitMQ for both cases but you have to keep in mind that RabbitMQ is another executable component (like database) so your overall solution complexity will increase. Another executable means another communication through network, configuration, deployment, maintainance etc.
So, if you don't have architectural drivers to use separate message broker you should take much simpler solution. In Memory Event Bus and Quartz background jobs processor are examples of these kind of solutions. RabbitMQ is powerful but you need to ask yourself if you really need it to solve your business problems.

You can use RabbitMQ for both cases but you have to keep in mind that RabbitMQ is another executable component (like database) so your overall solution complexity will increase. Another executable means another communication through network, configuration, deployment, maintainance etc.
So, if you don't have architectural drivers to use separate message broker you should take much simpler solution. In Memory Event Bus and Quartz background jobs processor are examples of these kind of solutions. RabbitMQ is powerful but you need to ask yourself if you really need it to solve your business problems.

@kgrzybek Yes you right, depending on the project scale and our purpose we can use the appropriate solutions.

It might be interesting to understanding why in a modular monolith replacing the in memory bus is useless.
In the microservice world you typically will update and redeploy an individual service while the rest of the app stays online. In that scenario it's important to persist the integration events in a physical queue rather than in memory.
That's, at least in my understanding, not applicable in a modular monolith since everything is always deployed as a whole.


Modified BuffRederFixedParser to return complete record data

Modified BuffRederFixedParser to return complete record datain returned Row's raw data. Added short and long record test for both BuffReaderFixedParser and BuffReaderDelimParser.

Sorry about the delay, somehow I was not aware of your Pull Request.
Thank you for your contribution.
Benoit


Provide low-memory option for Estimators

As discovered by @mriedel56, running certain memory-intensive meta-analyses (e.g., MKDA Chi-square and SCALE) on vary large datasets (e.g., Neurosynth) tends to cause out-of-memory errors. We can try using memory-mapped files for our larger arrays.

Maybe we can provide an option for our kernel estimators as well. At least with masked=True, since otherwise they return niimgs, which I think map to temporary files automatically in version 2.3+. We use 2.2.1, but I can dig into reproducing the original error fixed in 3525dcbcb6bd5354e2ee5907307cadd06896aa6e to see if it's still a problem.

I removed the restriction at some point without posting here, but it looks like the original error is fixed since we don't have any bugs re: nibabel.

In #319 I started using numpy.memmap in ALESubtraction. Expanding this to other Estimators is going to be a bit harder because we parallelize with multiprocessing in most of them. I'm not sure how to use both parallelization and memory-mapped arrays.


Convert dictionary of dictionary to array

Convert dictionary of dictionary that uses Integers as a Key for the dictionary to an Array of Objects

I'm going to close this PR as it does not provide the proper motivation for this change. Besides that the code is hard to read and does not seem to yield a clear benefit.


refactor redirects & canonical URL generation for path encoding

This is a potential fix for:

https://sentry.io/organizations/rust-lang/issues/3837812670/
https://sentry.io/organizations/rust-lang/issues/3836548500/

plus trying to prevent the issue in other places.
I'm happy to change things if there is a better design :)

r? @jyn514

This is pretty out of cache for me and I'm short on time; I left a brief review but I haven't looked at src/web/rustdoc.rs at all.

Thank you for taking the  time!

I will say this is a lot of changes, and redirects seem to be changing pretty frequently. I would like to settle on one api for internal_redirect even if the internals have to change (i.e. not constantly changing whether it should be prefixed with / and not changing the name of the function so much).

I'm not sure I fully follow. There was not change regarding a needed prefix of / for the redirect.
Are you proposing to merge some of the new methods into one? like internal_redirect and internal_redirect_with_queries? Or even merging it with the main redirect method? Or the extend_path_with_params method?
This design is more focused on keeping the calling sites simple.
Initially I had another approach where I had a simple redirect method that only took a Into<Uri>, where each calling-site had to use encode_path... methods themselves, plus extend_path_with_params.
IMO both approaches have advantages and disadvantages.

( If you want to see the other approach I would take the time to prepare this as a separate PR)

I'll split out the canonical URL part into a separate PR,
and then create a third PR as a proposed different solution for redirect URL encoding

closing this in favor of #1986  and already merged #1985


Set to Kryo serializer when registerKryoSerialization is called

In Storm, users just need to register class serializer. Kryo is the default serializer. However in Heron, the default is Java serializer which doesn't have the functionality. I think it is more consistent to set to KryoSerializer when the registration function is called.
Another option is to set Kryo serializer as the default one. The concern is that some users might be affected by the implicit change.
I am totally open to discussion.

The Heron API is not bound to Storm API. The translation is done by Heron-Storm API. Ideally, the Storm compatibility is supposed to be done in Heron-Storm API.

The Heron API is not bound to Storm API. The translation is done by Heron-Storm API. Ideally, the Storm compatibility is supposed to be done in Heron-Storm API.

Yeah. The translation works (although hacky). This is for native Heron API which works a little differently from the Heron-Storm API.


CyberHive Connect 3.5.1

Checklist for Pull Requests

[ ] Have you signed the Contributor License Agreement?
[x] Is there a linked Issue?

Manifests

[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.6 schema?

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

Hi, new manifest for CyberHive Connect 3.5.1.
Resolve https://github.com/microsoft/winget-pkgs/issues/191529
Microsoft Reviewers: Open in CodeFlow

@microsoft-github-policy-service agree company="CyberHive Ltd."

Verify:

I couldnt find how to have the application display its version number.

Hi @stephengillie, thanks for your help with this, much appreciated.

I couldnt find how to have the application display its version number

To view the Connect version number you can either:

Open the app Title Bar menu, 'About Connect...' is presented as an item
Right click on the Connect System Tray icon, and choose 'About Connect'

Hope that helps!
Many thanks,
James


[Feature] List CHI gastoken and enable CHI burning

By not only listing CHI, and minting it directly in the UI (exchange ETH > CHI), Loopring's contracts should be upgraded to, by user choice ("enable CHI" button, for when GWEI prices are high), burning ETH storage/CHI tokens when doing any onchain/L1 actions, for cheaper fees!

Please use this one for token list. https://loopringexchange.typeform.com/to/nWXj6B

@xiaowheat
Who said this is a token listing request? It's a whole feature suggestion about gastoken for cheaper transactions on Ethereum.


appveyor environment is causing timeout issues

https://ci.appveyor.com/project/3drobotics/dronekit-python/build/1.0.352

This is probably super specific to the MAVLink forwarding feature we have. I imagine all other tests are passing on Windows. A developer with Windows would be able to debug that MAVLink test fairly straightforwardly.

I disabled the Appveyor CI until we figure out how to fix it

AppVeyor works on the latest master and can be re-enabled. See #878.

AppVeyor builds are now enabled, running and successful. This issue can be closed. 🥳

Closed, thanks!


Option to use ScrollArea.Autosize for dynamic height.

Is your feature request related to a problem? Please describe.
I often work with data where record counts fluctuate from very low to very high. When using datatable to view this data I naturally want a scrollable view when record counts are high but I don't want it to take unnecessary space when there are 0-5 records.
Describe the solution you'd like
Mantine has already solved this with <ScrollArea.Autosize/> which has a maxHeight property that enables scrolling after reaching maxHeight. Because you already have height and minHeight I think a natural solution is to have a maxHeight property which (if it is less than height or if height is not set) will use Mantine.Autosize.
Describe alternatives you've considered
Hacking around this by programmatically controlling height, this is clunky and feels very unecessary

Thanks for raising the issue!
I tried your proposed solution, but for some reason <ScrollArea.Autosize/> doesn't play nice with horizontal scrolling.
Maybe I'm missing something, so I'd be grateful if you could come up with a PR...

I'll see what I can come up with, which branch should I point the PR towards? Would you be able to share what you tried on your first pass> It would help me orient myself in the codebase.

Sure. I've published this branch: scrollarea-autosize.
You'll be interested in:

package/DataTableScrollArea.tsx
this example component that is being displayed in the last section of this docs page

Run it locally with yarn dev, go to http://localhost:3000/examples/scrollable-vs-auto-height, last page section (Using ScrollArea.Autosize) and pay attention to horizontal scrolling...

I am having similar issue. @OrionReed How did you achieve AutoSize?

nvm. did this for now.
height={records.length < 10 ? "auto" : 400}


refactor(Guards): Re-implement guards feature to use services

Before we used provideGuard to quickly create guard factory functions. In order to play better with the offline compiler, this changes guards to instead use traditional services.
BREAKING CHANGE:
Before:
const auth = provideGuard(function(http: Http) {

  return function(route: Route, params: any, isTerminal: boolean): Observable<boolean> {
    return http.get('/auth')
      .map(() => true)
      .catch(() => Observable.of(false));
  };

}, [ Http ]);

After:
@Injectable()
export class AuthGuard implements Guard {
  constructor(private http: Http) { }

  protectRoute({ route, params, isTerminal }: TraversalCandidate): Observable<boolean> {
    return this.http.get('/auth')
      .map(() => true)
      .catch(() => Observable.of(false));
  }
}

LGTM


Add docstrings when the dust settles

          Please include doc strings. Chatgpt can be helpful generating them (see below), just make sure to check and keep them updated.

class FipsQuery:
    """
    A query tool to extract, compare, and visualize data based on a given FIPS (Federal Information Processing Standards) code.

    Attributes:
    -----------
    feature_groups_with_weights : dict
        Dictionary containing feature groups and their associated weights.
    feature_groups : list
        List of feature groups.
    data : DataGrabber object
        Instance of the DataGrabber class to fetch required data.
    repo_root : str
        Root directory of the repository.
    fips : int
        The Federal Information Processing Standards code.
    lag : int
        Lag time for considering data. Default is 0.
    top : int
        The number of top locations to consider for some operations. Default is 5.
    outcome_var : str
        Outcome variable to consider, either "gdp" or "population". Default is "gdp".
    time_decay : float
        The decay factor over time. Default is 1.08.
    all_features : list
        List of all features.
    name : str
        Name of the location corresponding to the provided FIPS code.

    Methods:
    --------
    compare_my_outcome_to_others(range_multiplier=2, sample_size=250):
        Compare the outcome of the given FIPS location with other locations.

    find_euclidean_kins():
        Identify locations that are similar to the given FIPS location based on Euclidean distance.

    plot_weights():
        Plot weights of different feature groups.

    plot_kins():
        Plot and visualize the most similar locations to the given FIPS location.
    """

    def __init__(...):
        ...

    def compare_my_outcome_to_others(...):
        """
        Compares the outcome (like GDP or population) of the location specified by the FIPS code
        with a random sample of other locations. It generates a plot comparing these outcomes.

        Parameters:
        -----------
        range_multiplier : int, optional
            Multiplier for the standard deviation to set y-axis limits. Default is 2.
        sample_size : int, optional
            The number of random other locations to be considered for comparison. Default is 250.
        """

        ...

    def find_euclidean_kins(...):
        """
        Identifies and orders locations based on their similarity to the given FIPS location
        by calculating the Euclidean distance between them. The outcome variable, additional features,
        and the time decay are considered for this calculation.
        """
        ...

    def plot_weights(...):
        """
        Visualizes the weights of different feature groups with a plot. It provides insight into
        the importance of each feature group in the current FIPS query.
        """
        ...

    def plot_kins(...):
        """
        Visualizes the locations that are most similar to the location specified by the FIPS code.
        The similarity is based on the previously calculated Euclidean distances. This method generates
        a plot comparing the outcomes of the top similar locations to the FIPS location.
        """
        ```

_Originally posted by @emackev in https://github.com/BasisResearch/cities/pull/35#discussion_r1375468193_

most are done


Refactor LengthRange sequence input to only allow elements in sequence

Currently, sequence input expects two elements (min, max). I want a sequence to have the semantics of exclusively the elements (allowed_length_1, allowed_length_2, allowed_length_3, ...).

Maybe make a separate LengthSequence class for this


Server Error ReferenceError: React is not defined

The  following error appears whenever I edit the '/next/pages/user/_app.tsx'.
Undoing the changes doesn't resolve it :(
error - pages/_app.tsx (16:2) @ MyApp
error - ReferenceError: React is not defined
    at MyApp (webpack-internal:///./pages/_app.tsx:10:163)
    at renderWithHooks (/home/ydrea/white-tree/solito/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5448:16)
    at renderIndeterminateComponent (/home/ydrea/white-tree/solito/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5521:15)
    at renderElement (/home/ydrea/white-tree/solito/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5736:7)
    at renderNodeDestructive (/home/ydrea/white-tree/solito/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5875:11)
    at renderNode (/home/ydrea/white-tree/solito/node_modules/react-dom/cjs/react-dom-server.browser.development.js:6009:12)
    at renderChildrenArray (/home/ydrea/white-tree/solito/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5965:7)
    at renderNodeDestructive (/home/ydrea/white-tree/solito/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5897:7)
    at renderElement (/home/ydrea/white-tree/solito/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5761:9)
    at renderNodeDestructive (/home/ydrea/white-tree/solito/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5875:11) {
  page: '/'
}
  14 |   var Component = _ref.Component,
  15 |       pageProps = _ref.pageProps;
> 16 |   return React.createElement(React.Fragment, null, React.createElement(Head, null), React.createElement(Provider, null, React.createElement(Component, pageProps)));
     |  ^
  17 | }
  18 |
  19 | export default MyApp;

The following error appears whenever I edit the '/next/pages/user/_app.tsx'. Undoing the changes doesn't resolve it :(
error - pages/_app.tsx (16:2) @ MyApp
error - ReferenceError: React is not defined
    at MyApp (webpack-internal:///./pages/_app.tsx:10:163)
    at renderWithHooks (/home/ydrea/white-tree/solito/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5448:16)
    at renderIndeterminateComponent (/home/ydrea/white-tree/solito/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5521:15)
    at renderElement (/home/ydrea/white-tree/solito/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5736:7)
    at renderNodeDestructive (/home/ydrea/white-tree/solito/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5875:11)
    at renderNode (/home/ydrea/white-tree/solito/node_modules/react-dom/cjs/react-dom-server.browser.development.js:6009:12)
    at renderChildrenArray (/home/ydrea/white-tree/solito/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5965:7)
    at renderNodeDestructive (/home/ydrea/white-tree/solito/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5897:7)
    at renderElement (/home/ydrea/white-tree/solito/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5761:9)
    at renderNodeDestructive (/home/ydrea/white-tree/solito/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5875:11) {
  page: '/'
}
  14 |   var Component = _ref.Component,
  15 |       pageProps = _ref.pageProps;
> 16 |   return React.createElement(React.Fragment, null, React.createElement(Head, null), React.createElement(Provider, null, React.createElement(Component, pageProps)));
     |  ^
  17 | }
  18 |
  19 | export default MyApp;

Happened with me too when I tried using useState in _app.js
A little workaround that worked for me was that, instead of
import { useState } from 'react'

I used
import React from 'react'

const [...] = React.useState(...)

Tnx Xinha!

@ydrea You should keep this open as the above solution is a hacky solution.
Maybe this is an issue, for swc minification to work next should be min 12.3
https://stackoverflow.com/questions/73913651/nextjs-swc-react18-referenceerror-react-is-not-defined

yeah this is odd. if you disable SWC minify and use babel instead, does it get fixed? you may need to clear out node_modules and .next folders, run yarn and then yarn web again.

I am not using SWC...

what if you run yarn why react?
my guess is there are multiple versions installed

I couldn't reproduce this with the monorepo starter.

Ah, never mind, I see. If you don't import React inside of _app.tsx, it does indeed throw this error. I'm not exactly sure why. For now, just stick to the workaround. Next 13 is right around the corner, and we won't even have this file anymore.


Alpha gradient colors have color banding

I am trying to render the following SVG:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
<svg width="100%" height="100%" viewBox="0 0 39 1" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xml:space="preserve" xmlns:serif="http://www.serif.com/" style="fill-rule:evenodd;clip-rule:evenodd;stroke-linejoin:round;stroke-miterlimit:2;">
    <g id="tcp_custom_recinput_fade">
        <rect x="0" y="-0" width="39" height="1" style="fill:url(#_Linear1);"/>
    </g>
    <defs>
        <linearGradient id="_Linear1" x1="0" y1="0" x2="1" y2="0" gradientUnits="userSpaceOnUse" gradientTransform="matrix(39,0,0,1,0,0.5)">
            <stop offset="0" style="stop-color:#2d2d2d;stop-opacity:0"/>
            <stop offset="1" style="stop-color:#2d2d2d;stop-opacity:1"/>
        </linearGradient>
    </defs>
</svg>

When rendering this to a PNG at a resolution of 16x3, resvg produces the following output:

When put over a solid #2D2D2D background, it causes some slight color banding:

When I inspect the image, it seems the colors in the gradient differ significantly from #2D2D2D:

Comparing it to the output I get from Affinity Designer, there is no color banding in its output:

SVG doesn't require dither, therefore we do not apply it either.

Sorry, I didn't mean dithering. The gradient is from #2d2d2d at 0 opacity to #2d2d2d at 1 opacity, so I'm not sure dithering is related

This is an expected behaviour: #677
You can try it yourself here: https://fiddle.skia.org/c/67cc2e6de7e644c8dd7402f86b1a1a68

I've tried recreating my setup (gray gradient on a gray background) on that site as follows: https://fiddle.skia.org/c/dfac4678c2c74d0ba855b199005591b0
Then I downloaded the images to an image editor for inspecting:

With increased contrast:

Interestingly, only the CPU version has color bands, the GPU version has no banding at all.
Since resvg uses CPU for rendering, I guess this is expected behaviour? I still wonder if there's any way to get rid of that banding with resvg. Please feel free to close this issue if this is not planned.

If you will figure it out - feel free to send a patch. I have no idea how to solve it.


[0.9.2 Pre Beta 2] This was release as a full release and is being offered to 0.8 users!!!!!!

I assume that offering it as a full release and not a pre-release was unintended.

Ooof.

The discord now has crash logs create discord entries for the crashes in the crash-reports forum. So the crash logs basically get pretty fast feedback. I was likely going to maybe nuke that version or not even offer the 0.9.2 beta line anymore which is probably better. At least until 0.9.1 is finished up.

I also have Homeassistant have google home mini read off the title of any github issue raised.

Apologies then for the early enter on the other issue I just raised which had a mostly blank title and no description. 🤣
I would keep the 0.9.2 pre-beta - just edit the tag and make it pre-release.

Yeah, just that the 0.9.2 stuff is a bit useful but a bigger change than I would want in 0.9.1 (moves to views away from matrices there).

Exactly!


gh #112 code cleanup of dsFPD

Clean up unnecessary code in L1:

Removed the unused variables, and macros and compiled with zero warnings.

FATAL used in all tests is removed except for init and term APIs.

Reviewed the usage of casting.

Re-checked if any new API interface has been added recently and requires an L1 test case, no new API interface was found.

can we define macros? for uBlinkDuration: 500, uBlinkIteration:20 , where ever it is applicable.

Done


Replace "hash" function with "validateCreate" function and match "create" API

Since you don't actually write your own create statements if you are using the SDK (or the CLI), we should just match that API in the validation function as well. Additionally, hash is slightly misleading, because the name doesn't reflect what the API is really designed for... validation.

I'm fine with keeping the name I guess? The confusion came from a discussion on Discord. Seems like a dryrun create option is a good idea 👍, so let's go with that.
In other words, have hash match the create api, and add an options arg to create with a dryrun option. It might be nice to collapse prefix into that options arg as well?

Nice, I like putting pefix into the options.
I'm curious what was the discord discussion?


Fixed reverting property sometimes not working.

Fixed reverting property sometimes not working.
Fixes #7901 and fixes #17753.

This fixes #17753 as well.

Tested and I can confirm that #7901 and #17753 are fixed by 6cc116d.


No Results

Im testing multiple of these,  the MFA test ill use as example.
I get no results available.
Im probably doing something simply wrong but any pointers on why i would get no results?

Several possibilities:

You have no resource which is in sope of the rule. For MFA, if you have no users.
There is a problem of IAM permission (lambda), check the CloudWatch logs of the lambda.
There is a bug in the rule code, check the CloudWatch logs of the lambda.


Default values?

Thanks for a great library. I'm just learning Elixir, so I might miss something obvious here.
Is it possible to somehow specify default values in a schema?
I have something like this:
defparams index_params %{
  filter: %{
    foo_id: :integer,
    bar_id: :integer
  },
  page: %{
    number: :integer,
    size: :integer
  },
  sort: :string
}

filter is not required, but it should default to %{}.
page is not required, but it should default to e.g. %{number: 1, size: 20}.
sort is not required, and should default to e.g. "id"
I could of course write a function that adds the default values, but since Ecto.Schema supports this it could be nice to somehow specify it directly in the schema.

Hey, just added support for actually passing any Ecto.Schema option, you need to give a keyword list instead of just a symbol. So for example, the page field would be:
page: %{
   number: [field: :integer, default: 1],
   size: [field: :integer, default: 20]
}

Note that if an embedded schema like page has any field with default value set, the struct will be created even if no data was present for it on request-params. However if the embed schema has no field with default, likefilterin your example, then it will just be nil, as ecto doesn't allow to set default values for embed schemas. You can work around this by having a dummy field with a default value set inside filter, just to force the whole embed schema to be generated.
I've already fixed this in master and the ecto-2 branch. I'm unable to publish the new version to hex.pm but will try later today. Hope this fixes this issue.

Just for reference, the tests are here

Wow, that was fast, thanks.
It seems like exactly what I need. I will test it later on my own project and provide some feedback.

Hi @vic
Again thanks for the new feature.
I've had a chance to test it in my own project and the default values works as expected.
However, I have build some of my app relying on maps and not structs, so I used Params.changes instead of Params.data. And changes returns a map of only the changes, which does not include default values.
This is technically correct, but somehow useless in the context of this package.
I tried to change my app to use structs instead, but it revealed another problem: Structs returned by data contains id: nil, which does not make sense for this kind of data. This was a problem for me where I recusively pattern match on the key-value pairs of a nested schema.
Do you agree that:

changes should return a map of all values including default values (maybe rename the function?)
Structs from data should not have an id (could be accomplished by setting @primary_key false on each schema)

I will be happy to help with the implementation.

Hey @lasseebert
Yeah, both things you mentions seem right to me.
changes should return the same content as data except that it should be just Maps. perhaps we should use data and then Map.from_struct: the struct constructor ensures default values get populated so then we just need to convert that to nested Maps. And yeah perhaps changes needs to be renamed to something else, any suggestion?
As for the structs from data, yes they should not include id unless it's explicitly declared on the schema by user.
So glad you want to help with the implementation :), give it a go. Tell me if you need some help with (my shameful) code.
Cheers.

It seems that we do need a @primary_key (id) if we want to have relations like embeds_one, so we can't just use @primary_key false. (ref: https://github.com/elixir-lang/ecto/issues/420#issuecomment-72311042)
AFAICS, the primary key is set when the adapter saves the schema to a datastore, which I think will not happen in the use case of this package.
Would it be ok with you that

The primary key is renamed from id to _id
Changes return a Map of all attributes from data except _id

I'm ok with both, go ahead with it, thank you very much :) Btw, should changes be named something different ? perhaps to_map. Initially I named it changes because it was extracting the values that changed in the changeset, but I suppose a better name would be nice. What you think?

I think to_map is a good name.
On Tue, Jun 14, 2016, 03:35 Victor Hugo Borja<EMAIL_ADDRESS>wrote:

I'm ok with both, go ahead with it, thank you very much :) Btw, should
changes be named something different ? perhaps to_map. Initially I named
it changes because it was extracting the values that changed in the
changeset, but I suppose a better name would be nice. What you think?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/vic/params/issues/4#issuecomment-225757087, or mute
the thread
https://github.com/notifications/unsubscribe/AAsb6gijvDVouBhLU-z-jFqrqAphLjl3ks5qLgV9gaJpZM4IuD-w
.

@lasseebert merged your PR #5.
Looks like ecto-2 will be released next week, when that happens I'm going to make the 2.x branch become master so I guess it's fine if we don't backport your changes to the ecto-1 branch.
Thanks for your contribution!

Thanks for you guidance :)


Improved Docker Image

This pull request adds an improved Dockerfile and docker-start.sh.
The new Dockerfile removes the mysql server from it, because it isn't the docker way having more than "one" service running in the container. That's what docker-compose.yml is for (docker-compose up), to create a multi service application (staytus and mysql database server).
The docker-start.sh sets up the config file from the environment variables on every start, so you can move from server to server without the need to move the config file too. You would just run docker-compose up again to start. That's what Docker is thought for, easy setup (through docker-compose). Volumes are for persistent data, not really for config files. ;)
This improves the experience with staytus in combination with docker. :)
Currently the docker-compose.yml links to my image on the docker hub, but you or I can change it to fit your docker hub account.
If you have any questions regarding the new Dockerfile, just ask.
Thanks for creating Staytus!

@astopy I fixed it. It's now using the files from the current folder.

Thanks @Galexrt, lots of great stuff here. I added the original Docker setup (https://github.com/adamcooke/staytus/pull/23 & https://github.com/adamcooke/staytus/pull/44), but docker-compose wasn't really recommended for production use at that point, and I never got around to going back and tidying this up.
These changes mostly look great, I've just sprinkled a few minor points and tweaks through in a couple of places. This will also need some doc updates to the README Docker instructions, to tell users how to start it after these changes.
This probably ties nicely into https://github.com/adamcooke/staytus/issues/52 once it's done. If you briefly poke the settings on DockerHub @adamcooke you can get the image to rebuild automatically on changes to this project, and on updates (e.g. security patches) for the underlying Ruby image.

@pimterry I look into adding the improvements in the upcoming week.
I'll change the README for Docker accordingly too.

@pimterry I have added/changed the following things now:

Added the improvements you suggested.
Added a README.docker.md.
Added the missing ports in the docker-compose.yml.
Rebased all my commits.

One thing that we still need to discuss, is how we handle the password from the docker-compose.yml.

It seems like I did something wrong during rebasing.. If you want me to create a new pr with only my commits.

@pimterry I added the improvements from your comments.

Great, thanks. All looks good to me :+1:

@adamcooke Any chance you can take a look at this? It's all ready now I think, it'd be good to get it merged in. Turning on #52 would be good too, so the Docker Hub build automagically updates on changes.

I'm worried about the current integration with Docker and I would welcome and advise. I have no experience with it whatsoever so I am nervous at every pull request as I have no idea what the best way to go about these things is. I would love to be able to create a repository which contains just the Docker stuff which can be maintained by someone other than me who has experience in this area.
I'm happy to merge this (although it's currently got conflicts - sorry for the delay!) if there's no other alternative but having Docker specific configuration in the core repository doesn't sit well. What happens when there's an alternative to Docker, are we expected to maintain configuration or both in here?

@adamcooke I'm going to resolve the merge conflicts in the next one or two days.
I'm going to add some changes to the Docker container entrypoint so we don't need to make changes for the future, so we don't need to add every new setting to it. Would that be an idea?

Sounds great - thank you

@adamcooke I have now pushed the more dynamic Docker entrypoint.

I'm going to add it in my rebased commit. It should be up in about two hours.

I just pushed the content of the README.docker.md.
I tested the new Docker image now, but I'm running into two errors when running bundle exec foreman start:
root@570cfddd0888:/opt/staytus# bundle exec foreman start
08:57:10 web.1    | started with pid 13684
08:57:10 worker.1 | started with pid 13685
08:57:10 web.1    | /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/rubygems_integration.rb:373:in `block in replace_bin_path': can't find executable bundle (Gem::Exception)
08:57:10 web.1    | 	from /usr/local/lib/ruby/site_ruby/2.3.0/rubygems.rb:298:in `activate_bin_path'
08:57:10 web.1    | 	from /usr/local/bundle/bin/bundle:22:in `<main>'
08:57:10 worker.1 | /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/rubygems_integration.rb:373:in `block in replace_bin_path': can't find executable bundle (Gem::Exception)
08:57:10 worker.1 | 	from /usr/local/lib/ruby/site_ruby/2.3.0/rubygems.rb:298:in `activate_bin_path'
08:57:10 worker.1 | 	from /usr/local/bundle/bin/bundle:22:in `<main>'
08:57:10 web.1    | exited with code 1
08:57:10 system   | sending SIGTERM to all processes
08:57:10 worker.1 | exited with code 1
root@570cfddd0888:/opt/staytus#

Could you tell me what these errors mean, so I can fix them?

Note:
With the dynamic entrypoint, you now specify the settings using environment variables.
For example for the setting STAYTUS_SMTP_HOSTNAME the env var would be SETTING_STAYTUS_SMTP_HOSTNAME. (This even works with lower case vars, example example_user_test would be SETTING_example_user_test.

Puzzling. Bundler is obviously installed because you're running bundle exec foreman start. I've not seen that before whenever I've run it. Perhaps foreman is doing something odd with the environment in docker?

I did some research and it seems that this is caused by a bug in bundler.. (see https://github.com/bundler/bundler/issues/4576).

@adamcooke I fixed the error by implementing a workaround mentioned in the issue https://github.com/bundler/bundler/issues/4576.
My changes are now ready to be merged. :)

@adamcooke Thanks for taking a look at this (sorry it's taken so long for me to join in on this again too!)
Your concerns about having the Docker config here make sense, I think splitting them out is quite sensible, even with the more configurable setup here. Feels unnecessary to tie the distribution code to the larger Staytus codebase, splitting out reviewing would make life easier too, and it's then easier for us to manage setting up integration with Docker Hub etc.
If you want to do this, I'd be happy to maintain it (and I suspect @galexrt would too?). We should probably move this repo and the new one out into a standalone github organisation to do that though, rather than distributing these repos all over.
How would you feel about that? Do you mind setting that up? Should just be a matter of creating the org, moving this repo there (which will automatically set up redirects from the current location for everything), creating a staytus-docker repo too, and adding the two of us to it.

@pimterry There should be no problem in just leaving the three (four with the docs) Docker related files in the repo. File list:

Dockerfile
docker-compose.yml
docker-entrypoint.sh

The image entrypoint I created should be sufficient for the future as if you introduce new variables for example for the Staytus config variable LDAP_HOST Docker users just add SETTING_LDAP_HOST (with value) to their docker-compose.yml file and are good to go.
So the Docker image should have almost zero "maintenance" time. The only time I see time required to fix something with the image is when ground breaking gets changed like the installation procedure.
But even if a change like this occurs you can just hit me and @pimterry up and we'd be glad to fix it fast.

My opinion on moving Docker stuff to a new repo is that there is no need to move the Docker image to a separate repo as we talk about small 4 files and not hundreds of files that are required for the Docker image to be built.

@pimterry I like the idea of not having any deployment specific things in the core repo so a new repo would be great. I'm not too worried about creating an org for it, perhaps you'd like to create a repository in your own account that we can just link to from our docs in this repo?

@galexrt thanks for your contribution. You're doing it right. Shipping a docker image is not shipping a Vagrantfile or something packed. How to use another database service (say Amazon RDS or so) ?

@bersace It isn't documented in the Docker README but take a look at these lines in the entrypoint script: https://github.com/galexrt/staytus/blob/960abd8152746b4503d97b5cb24e54821fe96cc2/docker-entrypoint.sh#L8-L15

@galexrt That is the right way :D

Would be great to see this merge and an automated docker build setup. Noticed the current docker hub image hasn't been updated for 2 years!

Not sure if this PR is still active? Would like to see it get merged, or if it's not active now, I can send another one :)

@PeterDaveHello I'm happy to update the PR, but I didn't get feedback yet on how to continue with the PR.
/cc @adamcooke

Is this PR full on dead at this point? The docker image in the repository is extremely dated.

@maddprof Well as written in the above comment, I have not gotten any feedback from @adamcooke (only @pimterry) over the span of creating the PR till now. I'm still hoping to get a review to update the PR.
@maddprof and anyone using my Docker image, if it is outdated, you can just give me a ping by creating an issue on the GitHub repo for it. I have gone ahead and updated the image, builds are complete right now.

Closing this PR. I don't see this being merged any time in the future.

I do have a bunch of updating coming very soon to address exactly the contents of this PR. I already have a Dockerfile template that I use elsewhere that I'll probably use but it will remove the MySQL server etc.


Fix several modern compiler errors

Description
Tested with fedora core 39, g++-13
How Has This Been Tested?
Compiles successfully now.
Is this pull request on the correct branch?
Against master

Closed in favor of #551. Resync of development and master branches will happen after resolving that request.


0.2.3 release

0.2.3 release

Thanks btw -- I was just about to request this. 🥳

LGTM assuming tests pass -- what's new in Finch 1.0.1?

Two Galley fixes:

https://github.com/finch-tensor/Finch.jl/pull/673
https://github.com/finch-tensor/Finch.jl/pull/670
And sprand fix: https://github.com/finch-tensor/Finch.jl/pull/671


ExpandMessageXMD mishandles very long DST values

The current code assumes that DST is <= 255 bytes long, which in of itself is fine, as the base definition in the RFC and the fact that the extra handling is in a separate section (5.4.3).  While this does fall under "Don't do that then", as it is a public API, the correct thing to do would be to either return an error if the DST is oversized, or to implement the (trivial) handling for it as per the draft.

See #45


Separate CGMES

Convert the CGMES profiles into 'Data exchange standards' instead of Data Objects

Model the data itself as 'data object' e.g., Data Object and model the profile as something else.

Think about aggregation


Add floating ip info in esi node network list

Expand 'openstack esi node network list' output to  Node|MAC Address|Port |Network|Fixed IP|Floating IP|Floating Network
Reduce neutron /networks/id API calls by fetching all networks at once and then convert the network list into a dict {network_id: network_obj}.

I've made the change to reduce the get_network API calls. Let me know what do you think about it.

Thanks! Looks good. One last thing - I also can't figure out the issue with python 3.7. For now, can you edit .github/workflows/test.yml and remove 3.7?

Thanks! Looks good. One last thing - I also can't figure out the issue with python 3.7. For now, can you edit .github/workflows/test.yml and remove 3.7?


Added dsstorewordlist.txt

https://github.com/aels/subdirectories-discover

Perfect wordlist to discover directories and files on target site with tools like ffuf.

It was collected by parsing Alexa top-million sites for .DS_Store files (https://en.wikipedia.org/wiki/.DS_Store), extracting all the found files, and then extracting found file and directory names from around 300k real websites.
Then sorted by probability and removed strings with one occurrence.
resulted file you can download is below. Happy Hunting!

Thanks for the suggestion @ItsIgnacioPortal
There is now a merge conflict - could you fix it up ?

Conflict fixed, and ready to merge!


Transactions query total is incorrect on last page.

Summary of Bug
On the last page of the results of a transaction list query, the total shows as {page count} * {results in last page} which is often far fewer than there actually are and also much less than what earlier pages show.
For example, if there are 65 results, and 30 per page. There will be 3 pages; two with 30, and the last one with 5.. On the last page of results, above the query dropdowns, it will show "Transaction List | 15" instead of  "Transaction List | 65" (or "Transaction List | 90" like the other pages).
In other words, that total is coming being calculated as {page count} * {results in current page}.
But it should be ({page count} - 1) * {max results per page} + {results in last page}.
Or, if the number of results in the last page isn't known until you get there, on other pages, it seems like a decent compromise to just use {max results per page} for {results in last page}. i.e. show the total as {page count} * {max results per page} until you get to the last page, then show ({page count} - 1) * {max results per page} + {results in last page}.
It seems like it knows how many pages there are because even for large result sets, there's a number listed there. Also, as you get close to the last page, the links at the bottom reflect that you're nearing the end. So I wonder if it even needs to be calculated at all, and can just come from whatever is counting the pages.
If we make it just always use the number {page count} * {max results per page}, I suggest putting "about" up there, e.g. "Transaction List | about 90 total"
Version
Whatever's up on https://explorer.provenance.io as of Noon mountain time on July 29, 2022. The lower right says v3.2.0.
Steps to Reproduce

Go to https://explorer.provenance.io/txs
Under "Type" select "Transfer" -> "Send".
Under "Status" select "Failure".
Under "From" select 2022-07-21.
Under "To" select 2022-07-21.
Click "Apply".
Note that it says "Transaction List | 90 total" on page one (above the search parameters).
Click on "2" in the lower right (to go to page 2).
Note that it still says "Transaction List | 90 total"
Click on "3" in the lower right (to go to page 3, the last page).
Note that there are 24 results on this page.

Expected results:
Either a) it still says "Transaction List | 90 total" at the top, or b) it now says "Transaction List | 84 total" (84 = 2 * 30 + 24).
Actual results:
It says "Transaction List | 72 total".
Note: 3 * 24 = 72.
Tip: You can easily get a count of the results on a page by doing ctrl/cmd+F and searching for +UTC.
Other examples:

"Send" "Failed" "2022-07-22" "2022-07-22". There are 50 pages and the last page has 24 results.  So the total then says 1250 (= 50 * 25), but there are actually 1495 (= 49 * 30 + 25).
"Send" "Failed" "2022-07-21" "2022-07-22". There are 53 pages and the last one has 19. The total on the last page says 1007 (=53 * 19), but there are actually 1579 (= 52 * 30 + 19, also = 1495 + 84).

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

Oops. Forgot to include a screenshot:

.


Build an expanded version of the DIY version available for most popular 3D printers

Since i build my first DIY Openbot this week using the published 3d stl files (https://github.com/isl-org/OpenBot/tree/master/body/diy/cad), i realized that the following problems could be adressed:

Most popular 3D printers (like the Ender 3 i used) have a usable print area of 220 x 220 mm. However, the size of the build surface actually measures 235 x 235 mm which can be used for the "Slim_Body" only version. Unfortunately the "Slim_Body" version lacks the most valuable bumpers that the "Regular_Body" provides.
More over I am afraid that the available space inside the DIY version of the bot is very limited, resulting in:

cabling difficulty
preventing any hardware future expansion connectivity, since even if you decide to use extra sensors there is no space inside the shell
assembly difficulty, especially when you need to need to fix connectors that were removed due to cable stress on assembly

As a result:
I have redesigned the bottom and top stl trying to get the best of both worlds, since i would like to avoid the "glued" version for structural integrity reasons.
What i did was the following:

I used the "Regular_Body" version as a template
I replaced the back bumper with a slim one
I reduced the wheelbase to bumper dimension
I created a top cover height towards the half of the openbot, resulting to almost double height from center to back.
As an extra cherry to the pie (after my kids request) i created an extra version with lego combatible bricks patch on top of the back to be able to let them play & learn robotics.

I am attaching some screenshots if you like it and also agree that it could help others!
On the next step i will upload the stl files according to your guidelines

Best regards
Christos

Hi @thias15
I have uploaded all stl+readme file in Pull request #342 and i closed the request
https://github.com/isl-org/OpenBot/pull/342
Please let me know if i missed any step needed for the folder creation
Cheers!

Hi @thias15
Is the #342 working for you, or i shouldn't have closed it prior to review?
Cheers


Qualification tool: Allow app start and app name filtering and test with filesystem filters

Qualification tool: Allow app start and app name filtering (AND based).
Add a bunch of tests for filesystem based filters.

build

need to update for scalastyle

build


Error importing vCenter VM with 2 disk with same name

Description
When you try to import a VM with some disks with same name, OpenNebula fails.
To Reproduce
Import a VM with 2 disk with same name.
Expected behavior
Import should go well.
Details

Hypervisor: vCenter
Version: 5.8 and development

Progress Status

[ ] Branch created
[ ] Code committed to development branch
[ ] Testing - QA
[ ] Documentation
[ ] Release notes - resolved issues, compatibility, known issues
[ ] Code committed to upstream release/hotfix branches
[ ] Documentation committed to upstream release/hotfix branches

We need more information of how reproduce this issue.
Because we try many ways and works fine.
If not we will close it.

cannot reproduce


[ENHANCEMENT] Operator Fusion by MIOpen and Cudnn

🚀 Feature

Latest Cudnn and MIOpen provide basic operator fusion interface， could us move some operator fusion policies to support native MIOpen & Cudnn op fusion.
Motivation

Pitch

Alternatives

Additional context

Reference:
https://docs.nvidia.com/deeplearning/cudnn/developer-guide/index.html#op-fusion
https://rocmsoftwareplatform.github.io/MIOpen/doc/html/fusion.html#

I think we can implement it in the pattern substitution pass which currently supports some operator fusion (e.g., conv-biasadd-relu fusion) by matching fusion patterns and fetching relevant fused_kernel (generated by Antares/TVM) from kernel DB. And we can use cuDNN or MIOpen to replace the kernel fetching procedure.


Bundle without change in implicit behavior in v1.10.0

Prior to version 1.10.0 if you are installing using the explicit flag --without only the arguments provided will be used in the bundle command so if you
$ bundle _1.9.10_ install  --without development:test
# ...
Gems in the groups development and test were not installed.

Then it will only exclude your development and test groups, However with 1.10.0 any config in your .bundle/config will get merged in. So someone in your team checks in their bundle config that looks like this:
$ cat .bundle/config
---
BUNDLE_WITHOUT: unneeded

And you run this
$ bundle _1.10.0_ install  --without development:test

You exclude a group not present in the explicit without flag:
Gems in the groups development, test and unneeded were not installed.

I checked over the changelog and I haven't  yet figured out exactly where this change in implicit behavior came from (forgive me if I missed it in the changelog). Should we retroactively document this change or is it a bug that should be reverted?
cc/ @hone

It was definitely a bug that .bundle/config was ignored if you passed --without. You should be able to run bundle config without foo and then bundle install --without bar to get a bundle without foo or bar.
Unrelated to the behavior change, never ever check in your .bundle directory. It contains repo/checkout local state like the location of the installed bundle, configured git local gems, and other settings that should not be shared between multiple checkouts of a single repo.

We should add that to the changelog for completeness. How does this sound?
  - The `--without` flag now includes bundle config `BUNDLE_WITHOUT` value

We could warn when we find a .bundle/config when someone deploys an app to Heroku.

How about:
## Bugfixes

 - Without groups saved via `config` are no longer ignored when the `--without` flag is used

Warning users who check in their .bundle/config seems like a very good idea.

I like that, I'll send over a doc PR. Btw we're on 1.11.2 as of yesterday. Some minor issues (https://devcenter.heroku.com/articles/bundler-version#known-upgrade-issues), but so relatively smooth sailing.


Got Error 3050000 after pushing action

Got Error 3050000 after pushing action to addressbook contract
cleos push action adr add '{"account":"alice","first_name":"alice","last_name":"in wonderland","street":"white rabbit lane","city":"wonderland","state":"wonderland","zip":"98109"}' -p alice@active
Smart contract code

Looks like it's a type mismatch. In your abi file the type of "zip" is uint32_t but you put a string from your command line.
      "fields": [{
          "name": "account",
          "type": "name"
        },{
          "name": "first_name",
          "type": "string"
        },{
          "name": "last_name",
          "type": "string"
        },{
          "name": "street",
          "type": "string"
        },{
          "name": "city",
          "type": "string"
        },{
          "name": "state",
          "type": "string"
        },{
          "name": "zip",
          "type": "uint32"
        }
      ]

The problem was in calling another contract which is not deployed yet.

Thank you all 😉


[ddc] flaky behavior in for-loop eval test

We have an expression evaluation test that checks for the value of a loop variable on the first iteration of a loop. The test is flaky about 3% of the time in linux bots, but doesn't repro locally (I tested running it >1K times w/o success).
The failure logs suggest that the breakpoint is not hit on the first iteration of the loop, but the second iteration (recent failure).
To reduce flakiness, I'll change the expectations to accept the current behavior (hit the breakpoint on either the first or second iteration), but if it continues to flake, we may prefer to skip it altogether.

After testing a couple ideas, I stumbled upon the cause of this issue. (I added a print to validate that our breakpoint was not improperly added to the increment statement. In doing so, the failure logs revealed what follows...)
In a chain of changes we sped up expression evaluation tests by combining all tests into a single input program and reusing the same page across all test cases. This made a big reduction in timeouts and made tests complete a lot faster (sometimes 5x or more). This came at a cost of loosing some isolation.
Turns out, we have a race when we advance from one test case to the next. We:

(test 1) set a breakpoint
(test 1) start main
(test 1) run all checks at a breakpoint
(test 1) remove the breakpoint
(test 1) resume execution (running the rest of the test and the rest of main)
(test 1) move on to the next test set up, that is:
(test 2) set a breakpoint
etc

Step 6 & 7 are done by our test driver in separate process from the page. So they may complete before step 5 finishes running.
This is what trips the loop-variable test, which was the second test case using a breakpoint inside a loop.
When the previous test finished and resumed execution, the loop continued running and the breakpoint of the second loop test ends up being hit by the from from the first test. This led to broken assumptions about the state of the loop in the second test case.
A few options to bring some isolation between tests are:

a. Don't reuse any breakpoints across tests.
b. Ensure execution is done before step 6
c. Don't reuse reentrant breakpoints.

(b) is requires some infra in the test driver to wait for a signal that main finished running. This may mean monitoring that some state is updated on the page and ping the page periodically for updates until the state changes. Sounds doable but may have a performance cost that we'd like to avoid.
(a) brings isolation because the location where one test stopped is less likely to affect how another test behaves. That siad, we have many test cases that do reuse the same breakpoint for simplicity and turns out that most of them are not reentrant: that makes them in a way isolated by the fact that once resumed the breakpoint cannot be hit again.
This leads me to believe that (c) may be a simpler approach. It behaves like (a), but only requires work on tests containing loops (currently there is only 1 case of a loop breakpoint reused across 2 tests).

Hopefully fixed by 4e0ece2722b887ab61363ac5aceeb46b79976f88


Make sure that runtime/benchmarks are dry-run in CI tests

Follow-up of https://github.com/enso-org/enso/pull/7991 - some build config fixes
Pull Request Description
Ensure that -Dbench.compileOnly system property is correctly forwarded to the benchmarks' runner. So that in the CI Engine tests, benchmarks are dry run.
Important Notes

Fixes dry run benchmarks in Engine Test Action
Fixes Engine Benchmark Action

Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:

[x] The documentation has been updated, if necessary.
[x] Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
[x] All code follows the
Scala,
Java,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.
All code has been tested:

[x] Unit tests have been written where possible.
[x] If GUI codebase was changed, the GUI was tested when built using ./run ide build.

E.g. in https://github.com/enso-org/enso/actions/runs/6929383747/job/18846977787?pr=8330#step:10:15023, one can see that there are, once again, dry run benchmarks in the tests. Let's merge.


tvOS keep focused cell on the left

Hey,
I'm trying to keep the focused UICollectionViewCell on the left, so I'm disabling scrolling on the UICollectionView and scroll myself like this:
- (void)collectionView:(UICollectionView *)collectionView didUpdateFocusInContext:(UICollectionViewFocusUpdateContext *)context withAnimationCoordinator:(UIFocusAnimationCoordinator *)coordinator {     if (!context.nextFocusedIndexPath) {         return;     }     collectionView.scrollEnabled = NO;     [collectionView scrollToItemAtIndexPath:context.nextFocusedIndexPath atScrollPosition:UICollectionViewScrollPositionLeft animated:YES]; }
unfortunately what happens is that the UITableView also scrolls down, which is not what I want, as I'm only scrolling to the right.
Do you have an idea why this is happening? The indexPath for the next UICollectionViewCell is the same for each UITableViewCell, so indexPath 0-0  in UICollectionView is obviously present in each UITableViewCell (I'm guessing that's why the focus engine in tvOS gets a bit confused). But this effect works for example in the Netflix app.
I'll appreciate any help.
Thanks!

Hi there, I'm not sure – I've never done tvOS development. Could be some sort of focus-stealing behaviour, like when you scroll the collection the containing scroll view knows to change? Not sure. When you figure it out, will you let me know?

Sure Ash, I'll try to figure it out today. When I do I'll definitely tell you here. But yes, I also think it's some kind of weird focus stealing behaviour. Let's see, maybe one must disable the scroll on the tableView and detect a horizontal swipe to do that...

Ok, I've figured it out. The trick was to not disable scrolling on the collectionView and add apropriate index calculation in tableView:didEndDisplayingCell:forRowAtIndexPath: - that part was missing in my implementation - now, just using [collectionView scrollToItemAtIndexPath:context.nextFocusedIndexPath atScrollPosition:UICollectionViewScrollPositionLeft animated:YES];  gives you basically the same effect like the Netflix app has on Apple TV.

Awesome! I'm glad you got it figured out 👍


Fix objects and end values

This PR fix the issues described by yousefcodes in #125

@lderezinski @xer0x Any chance for this PR to be reviewed / merged ?


Gradient in pdf rendering from LaTeX output problem

This issue was found from generating charts from LaTeX. The code used to generate the pdf example can be found here
Attach (recommended) or Link to PDF file here:
badexample.pdf
Configuration:

Web browser and its version: Tested on Firefox Quantum 67.0 (64-bit)
Operating system and its version: Windows 10 version 10.0.17134 Build 17134
PDF.js version: confirmed: (PDF.js: 2.2.71) and (PDF.js: 2.0.943)
Is a browser extension: Tested using built-in browser version

Steps to reproduce the problem:

Open attached pdf

What is the expected behavior?
The top of the gradient bar to the right of the chart should not turn white at the top.
Below is a screenshot from Microsoft Edge PDF Viewer (similar results from Chrome (v74.0.3729.169), Adobe Illustrator, and Inkscape, which are all the other pdf viewers I have installed)

What went wrong? (add screenshot)
There's a white gradient at the top of the color bar as seen below:

This screenshot was taken in Firefox (PDF.js: 2.2.71). Same incorrect rendering is produced by the VSCode LaTeX workshop extension which is how this was discovered (PDF.js: 2.0.943)

Possibly a duplicate of issue #7339.

@Snuffleupagus This is the same issue, nice catch! I had been searching and hadn't seen that issue. Thanks


subscribing to control_msgs/msg/JointJog causes failure

Issue template

Hardware description: Teensy 4.1
RTOS: Arduino BareMetal
Version or commit hash: foxy

Steps to reproduce the issue
While testing the NativeEthernet implementation that I'm working on, I tried to subscribe to a topic that uses the JointJog message and discovered that this message type causes the system to hang.
I've modified the micro-ros_subscriber_twist.ino example to provide a serial example of the problem:
#include <micro_ros_arduino.h>

#include <stdio.h>
#include <rcl/rcl.h>
#include <rcl/error_handling.h>
#include <rclc/rclc.h>
#include <rclc/executor.h>

//#include <geometry_msgs/msg/twist.h>
#include <control_msgs/msg/joint_jog.h>

rcl_subscription_t subscriber;
//geometry_msgs__msg__Twist msg;
control_msgs__msg__JointJog msg;
rclc_executor_t executor;
rcl_allocator_t allocator;
rclc_support_t support;
rcl_node_t node;

#define LED_PIN 13

#define RCCHECK(fn) { rcl_ret_t temp_rc = fn; if((temp_rc != RCL_RET_OK)){error_loop();}}
#define RCSOFTCHECK(fn) { rcl_ret_t temp_rc = fn; if((temp_rc != RCL_RET_OK)){error_loop();}}

void error_loop(){
  while(1){
    digitalWrite(LED_PIN, !digitalRead(LED_PIN));
    delay(100);
  }
}

//twist message cb
void subscription_callback(const void *msgin) {
  //const geometry_msgs__msg__Twist * msg = (const geometry_msgs__msg__Twist *)msgin;
  const control_msgs__msg__JointJog * msg = (const control_msgs__msg__JointJog *)msgin;
  // if velocity in x direction is 0 turn off LED, if 1 turn on LED
  digitalWrite(LED_PIN, (msg->duration == 0) ? LOW : HIGH);
}

void setup() {
  set_microros_transports();
  pinMode(LED_PIN, OUTPUT);
  digitalWrite(LED_PIN, HIGH);

  delay(2000);

  allocator = rcl_get_default_allocator();

   //create init_options
  RCCHECK(rclc_support_init(&support, 0, NULL, &allocator));

  // create node
  RCCHECK(rclc_node_init_default(&node, "micro_ros_arduino_node", "", &support));

  // create subscriber
  RCCHECK(rclc_subscription_init_default(
    &subscriber,
    &node,
    //ROSIDL_GET_MSG_TYPE_SUPPORT(geometry_msgs, msg, Twist),
	ROSIDL_GET_MSG_TYPE_SUPPORT(control_msgs, msg, JointJog),
    "micro_ros_arduino_jj_subscriber"));

  // create executor
  RCCHECK(rclc_executor_init(&executor, &support.context, 1, &allocator));
  RCCHECK(rclc_executor_add_subscription(&executor, &subscriber, &msg, &subscription_callback, ON_NEW_DATA));

}

void loop() {
  delay(100);
  RCCHECK(rclc_executor_spin_some(&executor, RCL_MS_TO_NS(100)));
}

Command to send message that should change the LED to LOW:
ros2 topic pub /micro_ros_arduino_jj_subscriber control_msgs/msg/JointJog "{ header:{stamp:{sec: 10, nanosec: 20 }  , frame_id: 'base_link'  }  ,joint_names:['blah'], displacements:[100], velocities:[1],  duration: 0}"
Expected behavior
LED should turn off
Actual behavior
LED does not turn off

Hello @KohlhardtC you are not initing the control_msgs__msg__JointJog message... We have a lot of issues like this so I have wrote a brief explanation in our webpage: https://github.com/micro-ROS/micro-ROS.github.io/pull/312. It is not merged yet but you can read it here.
In general you need to initialize sequence memory for the control_msgs__msg__JointJog msg:
#define STRING_SIZE 100
#define MAX_ENTITIES 3

// Init header frame id string
msg.header.frame_id.capacity = STRING_SIZE;
msg.header.frame_id.size = 0;
msg.header.frame_id.data = (char*) malloc(STRING_SIZE * sizeof(char));

// Init sequence of strings
msg.joint_names.capacity = MAX_ENTITIES;
msg.joint_names.size = 0;
msg.joint_names.data = (rosidl_runtime_c__String*) malloc(MAX_ENTITIES * sizeof(rosidl_runtime_c__String));

// Init each string of the sequence of strings
for(int i = 0; i < MAX_ENTITIES; i++)
{
    msg.joint_names.data[i].data.capacity = STRING_SIZE;
    msg.joint_names.data[i].data.size = 0;
    msg.joint_names.data[i].data.data = (char*) malloc(STRING_SIZE * sizeof(char));
}

// Init doubles sequences
msg.displacements.capacity = MAX_ENTITIES;
msg.displacements.size = 0;
msg.displacements.data = (double*) malloc(MAX_ENTITIES * sizeof(double));

msg.velocities.capacity = MAX_ENTITIES;
msg.velocities.size = 0;
msg.velocities.data = (double*) malloc(MAX_ENTITIES * sizeof(double));

Thanks for the tip, I never would have guessed this to be the case.
Would it be possible to programmatically initialize the memory sequence to help reduce this workload for end users? I am a novice C++ developer and don't have enough grasp on the language to know if there is any chance of making this more convenient.  I wonder how ROS handles this internally? Or maybe we could generate a python script that reads in message files and produces initialization code? It just feels like this is a lot of extra busy work that could be automated in some way.

BTW, thank you for sharing the initialization code. I actually couldn't get it to compile because there was an extra reference to 'data' in the for loop. Here's the working code:
#define STRING_SIZE 100
#define MAX_ENTITIES 3

// Init header frame id string
msg.header.frame_id.capacity = STRING_SIZE;
msg.header.frame_id.size = 0;
msg.header.frame_id.data = (char*) malloc(STRING_SIZE * sizeof(char));

// Init sequence of strings
msg.joint_names.capacity = MAX_ENTITIES;
msg.joint_names.size = 0;
msg.joint_names.data = (rosidl_runtime_c__String*) malloc(MAX_ENTITIES * sizeof(rosidl_runtime_c__String));

// Init each string of the sequence of strings
for(int i = 0; i < MAX_ENTITIES; i++)
{
    msg.joint_names.data[i].capacity = STRING_SIZE;
    msg.joint_names.data[i].size = 0;
    msg.joint_names.data[i].data = (char*) malloc(STRING_SIZE * sizeof(char));
}

// Init doubles sequences
msg.displacements.capacity = MAX_ENTITIES;
msg.displacements.size = 0;
msg.displacements.data = (double*) malloc(MAX_ENTITIES * sizeof(double));

msg.velocities.capacity = MAX_ENTITIES;
msg.velocities.size = 0;
msg.velocities.data = (double*) malloc(MAX_ENTITIES * sizeof(double));

Thanks for the correction! I didn't try it...
The automation of that is required, I agree. But there are some problems regarding the dynamic/static memory selection or on how long are the sequences. The former is typically an application-specific decision, so automating this number can be tricky, but of course, this code can be autogenerated.
I'm going to think about it. Meanwhile, I'm closing this because solved, do not hesitate to reopen if you have other problems.


Update AC-5 through AC-7 control sub-families to accurately reflect our system for review

In order for compliance reviewers to understand our system, we need to update these sub-families of control statements to explain our system (and policies and procedures) in more precise and thorough detail.
Setup
Read the guidance in HOWTO update the SSP before working on this.

AC Google Doc

Please feel free to reach out to Britta for context/guidance as your first step when picking this up. :)
Acceptance criteria
See https://github.com/18F/cg-compliance/issues/176 for the rest of the AC family.
AC-5:

[x] AC-5 statement addresses whether we document separation of duties. (Find out whether we can provide better evidence that we already document separation of duties, or whether we still need to document it.) [SRTM moderate]

AC-6 (1):

[x] Control statement is updated to define in more detail what the security functions are within our various account systems. [SRTM low]

AC-6 (2):

[x] Rewrite control statement to explain how we implement the principle of using "non-privileged accounts or roles, when accessing nonsecurity functions" for AWS, BOSH, Concourse, GitHub, cloud.gov platform, and so on - or mark this as planned and track that planned task in a backlog. [SRTM low]

AC-6 (9):

[x] Control statement is updated to explain how we can audit execution of privileged GitHub functions. [SRTM low]

AC-6 (10):

[x] The paragraph "Only designated Org Managers from the Cloud Operations team can execute privileged functions to the cloud.gov platform. All other accounts are non-privileged accounts." is updated to reflect our system, and the control statement also explains how this control is implemented for AWS. [SRTM low]

AC-7:

[ ] AC-7 answers this question: "Do you know if GitHub enforces a limit on consecutive invalid login attempts?" [PMO comments]
[ ] If appropriate, this has customer responsibility checked off in the origination checkboxes in some way.

We're currently blocked on finishing AC-7 waiting for information on SecureAuth from various sources, but other than that, this is ready for review by @rjbator.

Checked it out and made some comments

Reviewing.

Done. Cleaned up an ready for re-importation into Word on 9/26. Put todo and confusing labels in text so I can actually search on them.


update for django 4.2

update dependencies & tox for django 4.2b1

Hello.
Thank you for this but I would rather wait for a stable release before updating tests.
Warm regards,
Mitch


Remove 'z' from Organization and replace with 's'

Currently, Organization is written with 'z', it must be changed to Organisation.
Following the enhancement ticket: #232

I have been through the site multiple times and all of the spelling appears to have been changed from the American Spelling with 'z' to the British Spelling with 's'.


[MD] Why don't you use the md file format?

Currently I see file format as mdx not showing images on Github Repository

Github no support file mdx


Fix image coding in the Cloud SIEM Integrations articles

Purpose of this pull request
This pull request (PR) fixes link and image coding in the articles in this section:
https://help.sumologic.com/docs/cse/integrations/
Issue number:  Asana ticket Clean up links and image coding in SIEM and SOAR

Select the type of change:

[x] Minor Changes - Typos, formatting, slight revisions
[ ] Update Content - Revisions and updating sections
[ ] New Content - New features, sections, pages, tutorials
[ ] Site and Tools - Updates, maintenance, and new packages for the site, Gatsby, React, etc

Thanks, @kimsauce!


Feature/69 knot.x request response headers handling

I hereby agree to the terms of the Knot.x Contributor License Agreement.

Apprived


Fix typmod issues for vector

Description
Based on the current codeflow in TDS, the typmod is being fetched from pg_attribute even for PG base types. In case of typmod > 4, our code will manipulate it based on assumptions of TSQL types which is wrong. With this commit we explicitly set the typmod to -1 for vector type. Going forward we can do this for other PG basetypes if they can have variable typmod based on data lens.
TASK: BABEL-4687
Signed-off-by: Kushaal Shroff<EMAIL_ADDRESS>Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is under the terms of the Apache 2.0 and PostgreSQL licenses, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

-3 of 11 (72.73%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 72.842%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

contrib/babelfishpg_tds/src/backend/tds/tdsresponse.c
8
11
72.73%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
40997

Relevant Lines:
56282

💛  - Coveralls


New-AzDeployment fails to deploy when used with modules

HI,
Hoping someone can help me. I am trying to deploy a bicep file with a module. I can successfully deploy a resource group from the bicep. However, when I add the module for rbac assignment on the resource group I am getting this error message.
New-AzDeployment: Cannot retrieve the dynamic parameters for the cmdlet. The WriteObject and WriteError methods cannot be called from outside the overrides of the BeginProcessing, ProcessRecord, and EndProcessing methods, and they can only be called from within the same thread. Validate that the cmdlet makes these calls correctly, or contact Microsoft Customer Support Services.

This was originally raised under #1857.
The Az PowerShell team have fixed this under https://github.com/Azure/azure-powershell/issues/14403, which will be available in the next release of the powershell module.

Closing as duplicate


Item type repeats list

Item type repeats list
Testing in DSpace 7, uploading a test item, at "Item Type" there is a list of item types if one clicks on the arrow to the right of the entry box, but as one scrolls, the list repeats over and over.

Closing as a duplicate of #482.  This is a known bug, tentatively scheduled for 7.0beta5


Add rightsHolder to context

This should have happened in 30b638f9. It will require a new release to fix. mea culpa.