Adding more camera feeds

Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
I would like to add more camera feeds with a rolling change in the card. The garden is observed with a few cameras where the Landroid will be visible during the mowing process. I understand the camear feature is the best with a attached camera directly to the Landroid but that is a rare case i guess. By adding more than one camera to the card i will be able to observe the whole area where the Landroid will move.

I think it is not worth implementing in the card what is not related to the mower, but to the surveillance

In my case it is just related to the mower. Just one camera does not see
the moving mower all the time but some other cams can see it from different
angles. A rotation of cameras would see the whole mowing process.
Am Fr., 16. Sept. 2022 um 00:13 Uhr schrieb Barma-lej <
@.***>:

I think it is not worth implementing in the card what is not related to
the mower, but to the surveillance
—
Reply to this email directly, view it on GitHub
https://github.com/Barma-lej/landroid-card/issues/55#issuecomment-1248688839,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADI6EC2FSFW3M2FX5EAKD5TV6ONQPANCNFSM6AAAAAAQKNBPOQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


[backport] chore(ci): clean actions

Release Note
NONE

There are problems with the preflight check, but it does not look to be related as they were also happening previously in this release branch. Merging and having a look on the checks after the merge.


Marked is not defined on Angular-Bootstrap

Hi,
I tried using your plugin to generate my docs but it gives me an error when running the doc app.
marked is not defined on the angular-bootstrap.js
Also what it seems weird to me is when injecting the files you only include:
      [
		'docs/js/docs-setup.js',
		'docs/js/angular.min.js',
		'docs/js/angular-animate.min.js',
		'docs/**/*material-docs.min.*',
		'docs/css/docs.css',
		'docs/css/animations.css',
		'docs/css/prettify.css',
	];

But you don't include the 'docs/js/docs.js'  or the boostrap and prettify files, I had to inject them manually. Once I injected them I got this error

Apologies for just now seeing this @danielarita, will look into it and get back to you


Absolute sizing of visual elements

I notice that the size of everything (colorbars, text, crosshair line width, ...) is scaled to the size of the canvas' size. We did some user testing and people are saying that the colorbar and crosshair line widths are "annoyingly too big."
I see we have the function Niivue.setCrosshairWidth however the width is still scaling with the canvas size. How can we set the size of everything to be absolute?
BTW --> https://niivue.github.io/niivue/features/colormaps.html the checkboxes here are currently suffering from an off-by-one bug: "Wide Crosshairs" seems to set the crosshairs to green, "Gamma" seems to set the crosshairs to wide

@jennydaman

Note that for voxel-based images, the crosshair size is designed to give a scale for the raw voxels. Therefore, the lines appear smaller for higher-resolution images.
For other ornaments (text and colorbars), the scaling is based on textHeight. This is a fraction of screen size (where 0 is invisible) and the default is 0.06. See below for an example of setting this.
If you really want to have an absolute text size, you could add a resize callback for the canvas and scale appropriately. You simply have to compensate for the fact that NiiVue will set the size based on your requested text height and the minimum of your canvas height or width:size = this.opts.textHeight * Math.min(this.gl.canvas.height, this.gl.canvas.width) * scale.
NiiVue is designed to work on any device, including those with extreme aspect ratios. Therefore, it does include some logic to scale the colorbar and crosshair size.
for the live demo, the labels are to the left of their component, so "Wide Crosshairs" refers to the rightmost checkbox, and "Gamma" refers to the slider. Maybe adding some non breaking space between components would make this more clear.

    let opts = {
      textHeight: 0.02, // smaller text and colorbars
      crosshairColor: [0, 0, 1, 1] // green
    }
    const nv = new Niivue((opts = opts))


[Snyk] Upgrade tslib from 2.5.0 to 2.5.3

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade tslib from 2.5.0 to 2.5.3.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 3 versions ahead of your current version.
The recommended version was released a month ago, on 2023-06-02.

Release notes

Package name: tslib

2.5.3 - 2023-06-02What's Changed

Do not reference tslib.es6.js from package.json exports by @ andrewbranch in #208

Full Changelog: 2.5.2...v2.5.3

2.5.2 - 2023-05-18This release explicitly re-exports helpers to work around TypeScript's incomplete symbol resolution for tslib.

2.5.1 - 2023-05-17This release of tslib provides fixes for two issues.
First, it reverses the order of init hooks provided by decorators to correctly reflect proposed behavior.
Second, it corrects the exports field of tslib's package.json and provides accurate declaration files so that it may be consumed under the node16 and bundler settings for moduleResolution.

2.5.0 - 2023-01-26What's New

Fix asyncDelegator reporting done too early by @ apendua in #187
Add support for TypeScript 5.0's __esDecorate and related helpers by @ rbuckton in #193

Full Changelog: 2.4.1...2.5.0

    from tslib GitHub release notes

Commit messages

Package name: tslib

cc5ff03 2.5.3
a471c51 Merge pull request #208 from microsoft/moar-modules
80deca0 Do not reference tslib.es6.js from package.json exports
e623061 Bump version to 2.5.2.
2b57a92 Use named reexport to satsify incomplete TS symbol resolution (#204)
91fcbd0 Reverse order of decorator-injected initializers (#202)
eab3cff Merge pull request #200 from Andarist/fix/import-types
5ef7d1a Update modules/index.d.ts
7def846 Merge pull request #201 from microsoft/fix-esm
4e79d03 Merge pull request #179 from guybedford/patch-4
033b363 Add default export to modules/index.js
897f11e Ensure tslib.es6.js is typed
a0a67d9 Add Node-specific export condition for ESM entrypoint that re-exports CJS
0f84d40 Add propert declaration file for the `import` condition
a100d7b Merge pull request #195 from xfq/https
d58182f http -> https
68870a6 fix: default interop compat for "module" condition

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Included in: https://github.com/equinor/videx-map/pull/82


scripts/halon-rg-schema: New script

Created by: vvv
$ scripts/halon-rg-schema -h
Usage: halon-rg-schema [DIR]
       halon-rg-schema {-h|--help}

Generate Halon resource graph schema in DOT format.

Optional parameter `DIR' specifies the path to Halon sources directory,
which resources information will be read from. `DIR' defaults to current
directory.

Example:
    dot -Tpng -o /tmp/rg.png <(scripts/halon-rg-schema) && open /tmp/rg.png

Closing as an obsolete


Missing SerialPortStream project in unit test projects

When I was compiling your main solution file, the unit tests failed to build before a project reference was not added to the main SerialPortStream assembly. I updated this and all is well. I also created .net 4.7.1 versions of all projects and solutions. Let me know if you are interested in having them. Thanks, works great so far!

Which solution file are you referring to? The SerialPortStream-net40.sln and SerialPortStream-net45.sln work for me, when opening with VS2015. The SerialPortStream-netstandard15 loads with VS2017 and doesn't reference test cases (I don't have the time to support .NET Core, nor Mac).

Also, for 4.7.1, any functional changes, or just reference updates? In which case, if there are no functional changes, I prefer to support the lowest available standard, as they can then be used by any newer version of .NET allowing the greatest possible deployment.

I started by opening the SerialPortStream-net45.sln which include the
projects SerialPortStreamTest-net45 and DatastructuresTest-net45. One or
both of them did not have a project reference to SerialPortStream-net45, so
I added them. They would not compile as is because of the missing
reference. No functional changes for 4.7.1, just updated the project files.
Thanks,
Todd
On Tue, Feb 26, 2019 at 3:20 PM Jason Curl<EMAIL_ADDRESS>wrote:

Also, for 4.7.1, any functional changes, or just reference updates? In
which case, if there are no functional changes, I prefer to support the
lowest available standard, as they can then be used by any newer version of
.NET allowing the greatest possible deployment.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jcurl/SerialPortStream/issues/86#issuecomment-467597828,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ASxwzCE_NYIhxDqQ99BIy26fMvlT2xDsks5vRZcngaJpZM4bSrb3
.

--
Todd Osborne
<EMAIL_ADDRESS>

I'm not able to reproduce the issue when I check out the files on my system. I don't know what is different from yours.
For now, I need to keep with .NET 4.0 as that is what I need, and there is nothing needed to require .NET 4.7.1 (with .NET 4.5 already provided, it is using whatever version of .NET you've got installed).


How to detect a single image

Hello, I successfully trained my dataset
But I want to use the trained model to classify a single image
Want to ask how to do it
I tried changing --data path but can't seem to point to a single image

Hello, I successfully trained my dataset But I want to use the trained model to classify a single image Want to ask how to do it I tried changing --data path but can't seem to point to a single image

Hello, I have recently encountered the same problem as you. Can you provide an email address to facilitate communication? To protect privacy, I will delete this request as soon as I receive the email address.

because it has BN_Linear, it not works when batch_size =1,  you can change the BatchNorm1d to the LayerNorm


Mark BSGFetchedResultsControllerDataSource's init as unavailable

We want to force people to use mandatory init methods.

Done.


🚀[Feature]: Create organization invitations, list organization members

Description
I would love to use this module to invite users to GitHub organizations and be able to list members to check before sending.
Here's how you can list members:
Invoke-GitHubAPI -Method Get -ApiEndpoint /orgs/<org>/members

And how to send an invite:
$splat = @{
    Method = 'Post'
    ApiEndpoint = '/orgs/<org>/invitations'
    Body = @{
        invitee_id = 'githubusername'
        role = 'direct_member'
    } | ConvertTo-Json -Compress
    ContentType = 'application/json'
}
Invoke-GitHubAPI @splat

I intend to fork, make the changes, and submit a PR for your review.

Version 0.9.5 should now support the request.
Send invite: New-GitHubOrganizationInvitation
List members: Get-GitHubOrganizationMembers


Refactor endpoint structure - /api/user endpoints

Guidelines

[x] I read the Contributing Guidelines

This pull request regarding on

[ ] fixed an issue
[ ] developed new feature
[ ] fixed a bug

Briefly describe what you did
I have moved the login/logout and changepassword endpoints to /api/user to group related functionalities and add clarity to the project structure.
Appreciate your contribution to making Linkin better 🚀.

@dubisdev nice work 🔥 .


test: avoid using old emulator logs in startup

I think this will deflake the storage builds.  Consider this:

The script to startup the emulator uses the log file to discover the
port where it is running.
The script launches the emulator in the background and then
immediately tries to read its log
The script fails with "cannot connect", which it is only attempted
after the port is found.
The script then prints an empty emulator log, which could not happen
if the port was found!

But really what is going on is that the shell calls fork(2) to start
the emulator, but before it gets to call exec(2), or before it even
redirects stdout the parent process reads the file, finds the old
ports, then tries to connect. That fails, of course, then it prints the
log file, but that might be empty, or incomplete, or completely
different.
I got paranoid and fixed all the other scripts to start emulators.
Here is a log showing this:
2021-07-16T00:00:13Z (+362s)
---------------------------------------------------------
|   Running Storage integration tests (with emulator)   |
---------------------------------------------------------
2021-07-16T00:00:13Z (+362s): Launching Cloud Storage emulator on port 0
2021-07-16T00:00:13Z (+362s): Cannot connect to emulator; aborting test.
2021-07-16T00:00:13Z (+362s): curl connection test result.
curl: (7) Failed to connect to localhost port 39413: Connection refused
Killing emulator server [25990] ... 2021-07-16T00:00:13Z (+362s): ===> ccache stats

Part of the work for #6832

This change is

Let's merge this and we can talk about whether Bigtable needs it later.

LGTM


ensure coverage flag passed to jest correctly

What is the context of this PR?
Codecov hasn't been checking coverage because coverage reports weren't being generated. This is due to a version mismatch of yarn between our dev machines (> v1) and travis (v0.27.3). In yarn pre-v1, to pass args to package.json scripts you needed a double-dash separator:
yarn test -- --coverage

In yarn > v1, this separator has been retired:
yarn test --coverage

In v1 yarn the coverage flag will be forwarded correctly, but in yarn pre-v1, it will not. This meant that jest never got the coverage flag, lcov reports were not generated, and therefore codecov not correctly checking/enforcing coverage.
How to review
Check the Travis output of this PR. At the very end of the logs will be a call to codecov. If you expand this (using the arrow by line number), you should now see that codecov is finding the reports, where previously it was not.

 Fix code coverage reports/checks (0.5)


Added support for where not in

Adds the SelectBase::whereNotIn() method and related tests.

Thank you very much! This is very useful addition.


Can this work with custom VMs for release pipelines?

Hello.
I have a quick question.  Our release pipelines are set up to use custom, in-house virtual machines for our agent pool.  Would this kind of setup still work (maybe with adjustments to our machines), or would we need to use the Azure Pipelines?
Thank you in advance.

Hi,
As long as the requirements for the solution are installed, it does not matter whether it is your own VMs or Microsoft hosted agents as described in the wiki of this project. For the Microsoft hosted agent, you can list of installed software at:
https://github.com/actions/virtual-environments/blob/main/images/win/Windows2019-Readme.md
It is far from everything in this list that is required for this solution. From the list, you at least need:
Package Management
NPM 6.14.6 - see comment below
NuGet <IP_ADDRESS>26
Tools
Git 2.28.0
Newman 5.2.0 - see comment below
Other
Visual Studio 2019 - see comment below
Comments:
Interestingly, I saw that Newman is actually already preinstalled on this machine. I was not aware of this, why I in my release pipeline used NPM to install Newman. So you only need one of them.
Regarding Visual Studio, you do not need the entire Visual Studio package. This solution only requires MSBuild and .Net to build the solution & execute. So you should be able to get away with installing a subset of Visual Studio 2019.

Closing this issue, as I believe the former comment adequately answers the questions, and no further comments have been provided.


Midside handling mono signals

Currently midside doesn't handle mono signals and returns a print statement about needing stereo signals to process.
Vectorscope is dependent on midside for its functionality and I want vectorscope to plot mono signals.
Midside code without header:
def midside(array, channels, name, code=True):
	# check for stereo or mid/side array
	if channels == '1':
		return print('%s is mono, import 2 channel audio array for mid side processing.' % name)
	else:
		# divide array into stereo components
		left, right = split(array, channels, name)

		if code:
			# Mid/Side encoding
			mid = 0.5 * (left + right)
			side = 0.5 * (left - right)

			encoded = np.stack((mid, side), axis=-1)

			midside = True

			return encoded, midside

		else:
			# Mid/Side decoding
			newleft = left + right # mid + side
			newright = left - right # mid - side

			decoded = np.stack((newleft, newright), axis=-1)

			midside = False

			return decoded, midside

Intended functionality would either:

Continue to only process stereo signals & handle mono in vectorscope
Set mid to the mono array and side to an array of 0's = len of the array
Create a stereo array from 2 of the mono arrays and perform midside encoding

I'm partial to the 3rd since it is the simplest.

Issue fixed with 3rd method.


DDC: Abstract getter or setter overrides declared in class clobber inherited concrete implementations

Declaring abstract getters that override implementations from mixins or superclasses results in the getter being undefined when compiled in the dev compiler.
This issue is also present in the reverse, for setters: declaring abstract setters results in the setter being undefined, which actually throws.
Declaring both abstract getters and setters avoids the issue.
Example:
main() {
  // Abstract getter declared after concrete impl from mixin
  var instance1 = new Class1()..foo = 'bar';
  print(instance1.foo); // null

  // Abstract getter declared after concrete impl from superclass
  // Subclasses of this also fail
  var instance2 = new Class2()..foo = 'bar';
  print(instance2.foo); // null

  // Abstract getter declared in mixin after concrete impl from superclass
  var instance3 = new Class3()..foo = 'bar';
  print(instance3.foo); // bar

  // Abstract getter declared in interface after concrete impl from superclass
  var instance4 = new Class4()..foo = 'bar';
  print(instance4.foo); // bar

  // Mixin overriding abstract getter declared in superclass, which is declared after concrete impl from mixin
  var instance5 = new Class5()..foo = 'bar';
  print(instance5.foo); // bar
}

abstract class GetterAbstract {
  get foo;
}

class GetterConcrete {
  var _foo;

  get foo => _foo;
  set foo(value) => _foo = value;
}

class Class1 extends Object with GetterConcrete {
  get foo;
}

class Class2 extends GetterConcrete {
  get foo;
}

class Class3 extends GetterConcrete with GetterAbstract {}

class Class4 extends GetterConcrete implements GetterAbstract {}

abstract class _Helper_Class5 extends GetterConcrete {
  get foo;
}
class Class5 extends _Helper_Class5 with GetterConcrete {}

This is caused by the setter being redefined for these classes, but not the getter:
  list__main.Class2 = class Class2 extends list__main.GetterConcrete {
    set foo(value) {
      super.foo = value;
    }
  };
  (list__main.Class2.new = function() {
    list__main.Class2.__proto__.new.call(this);
  }).prototype = list__main.Class2.prototype;

You can see this issue in this ES6 reduced test case:
class A {
  get foo() {
    return 'foo'
  }
  set foo(value) {}
}

class B extends A {}

class C extends A {
  set foo(value) {}
}

var b = new B();
console.log(b.foo); // 'foo'

var c = new C();
console.log(c.foo); // undefined

We frequently use this pattern of overriding getters in order to update doc comments for subclasses, so it's unfortunate that this is a problem.
This issue is present in Dart 1.24.0 and 1.25.0-dev.1.0

Possibly related: https://github.com/dart-lang/sdk/issues/29935

@kevmoo # 2 DDC issue for Workiva

any update on this @jmesserly ? Is this fixed under Dart 2 DDC?

It is not fixed yet.

ping. wondering if this will be addressed after dart 2 ships.

ping. wondering if this will be addressed after dart 2 ships.

@robbecker-wf sorry it took so long to get back to you, I've been out of the office.
Yeah I would like to see if we can fix this now that Dart 2 has shipped.

Sent out a fix for review: https://dart-review.googlesource.com/c/sdk/+/72073


Versioning

Hey,
Can the api's be divided into different groups via versioning?
Ex:
Parent V1:
-Api1
-Api2
Parent V2:
-Api1
Currently, it's showing all endpoints in a single list.
And Is it possible to have different docs to each groups?
Ex: Providing a v1 doc to particular vendor access and v2 to other vendors.

Currently it is not possible. It is doable however

Can I expect both features in a future release?


Overview page spanish translation

Commit as part of CCOSS 2020 contribution
Description
This PR fixes #1700
Notes for Reviewers
Signed commits

[X] Yes, I signed my commits.

Excellent. Thank you for this, @Drake8710 and for the reviews, @chaltenio, @jesuslerma.
@Drake8710 just signal when ready for another review.

Thanks for your feedback! @jesuslerma @chaltenio @leecalcote
Sometimes its hard to understand a technical concept at the first time but we are here to learn and collaborate :)

Wow! Impressive, @Drake8710. 😄 Way to stick with this.

@Drake8710 I think there are only a couple of comments left to address. Thanks for taking on this effort.


Error is shown when ballerina home is set in vscode settings.

Description:
When pulling docker module from central, success message is shown and a consecutive error is shown when ballerina home is set in vscode settings.

is this happening because we are not using configured Ballerina distro to pull the module?

We are using shell command execution ballerina pull <module_name> to execute the command. Usually installers should replace ballerina command with the latest.
@srsharon Can you check whether output of the ballerina -v is same as VSCode configured ballerina.home(it should be different in this case).
I suppose, we need to get VSCode configured ballerina.home through the LSP config changes inorder to execute ballerina pull command. WDYT?

Closing since not reproducible in the latest. Please re-open if needed.


thresholds

excuse me , what are the thresholds of the models when operating ''face detection''?
(I mean the thresholds that generate the curves of FDDB and WIDERface in the author's papaer)
thanks!

ok,thank you!

No problem.

excuse me , I have the same question, can you tell me how to do it ?
thanks! @buweiaini


Support for larger DNS responses

I'm seeing the same error message as #214 when using this library for querying SRV records from Consul's DNS interface. It appears to be a similar issue.
When the message size is smaller than 512, my requests succeed. But when the response size increases to 538 B I get an error with "dns: buffer size too small".
 IN SRV
;; ANSWER SECTION:
example.service.consul. 0 IN SRV 1 1 32866 core-i-0a2b2rewr58f-<IP_ADDRESS>.node.dc1.consul.
example.service.consul. 0 IN SRV 1 1 32866 core-i-7fafffwerwwff-<IP_ADDRESS>.node.dc1.consul.
...
...
;; ADDITIONAL SECTION:
core-i-0a2b2rewr58f-<IP_ADDRESS>.node.dc1.consul. 0 IN A <IP_ADDRESS>
core-i-7fafffwerwwff-<IP_ADDRESS>.node.dc1.consul. 0 IN A <IP_ADDRESS>
...
...
;; Query time: 3 msec
;; SERVER: <IP_ADDRESS>#53(<IP_ADDRESS>)
;; WHEN: Fri Feb 19 12:58:10 UTC 2016
;; MSG SIZE rcvd: 538`
On the RFC 2675 https://tools.ietf.org/html/rfc2675
A field that specifies the length in bytes of the UDP header and UDP data. The minimum length is 8 bytes because that is the length of the header. The field size sets a theoretical limit of 65,535 bytes (8 byte header + 65,527 bytes of data) for a UDP datagram. The practical limit for the data length which is imposed by the underlying IPv4 protocol is 65,507 bytes (65,535 − 8 byte UDP header − 20 byte IP header)
This is well below the specified limit. Will there be support for this on this library?

There's a couple of things to cover here. I'll start with the protocol and then go to the practicals.
RFC 1035 defines plain old DNS to 512 byte messages over UDP (65,535 over TCP). EDNS0 allows adding a pseudo RR called the OPT RR which carries additional configuration extensions/options. With this RR the sender of the message can specify what the largest datagram they can receive is, and the responder can adjust the size of the payload they send accordingly. So Consul shouldn't be sending a 538 byte response over UDP unless an EDNS0 OPT is present with a larger buffer size specified.
This package exposes the DNS in a fairly granular way. The UDP buffer size ([]byte{} allocation, not in the EDNS0 sense) can be configured on dns.Client and dns.Conn. The OPT RR is supported and can be added to a dns.Msg manually or via Msg.SetEdns0. If an OPT is present in a dns.Msg handed to Client.Exchange the OPT RR's buffer size will be used as the receive buffer size.

As @asergeyev suggested we should add an option in the client to default to larger buffers. I.e. client.<GoodDescriptiveName> which we then use c.Exchange for Exchange we might just want to default to larger buffers.

@prisamuel were you able to get going with the pointers above?

Closing now that we have slightly better docs. In the end this whole discussion might result in a new function in dnsutil. For now: docs should suffice.

Thanks a lot. The documentation helped a lot.
Unfortunately I don't have an update on the initial issue. But I also found
that Consul can be configured to set to truncate responses.
https://www.consul.io/docs/agent/options.html#enable_truncate
On Wed, Mar 2, 2016 at 10:45 AM Miek Gieben<EMAIL_ADDRESS>wrote:

Closing now that we have slightly better docs. In the end this whole
discussion might result in a new function in dnsutil. For now: docs
should suffice.
—
Reply to this email directly or view it on GitHub
https://github.com/miekg/dns/issues/312#issuecomment-191182232.

[ Quoting<EMAIL_ADDRESS>in "Re: [dns] Support for larger DNS re..." ]

Thanks a lot. The documentation helped a lot.
Unfortunately I don't have an update on the initial issue. But I also found
that Consul can be configured to set to truncate responses.
https://www.consul.io/docs/agent/options.html#enable_truncate

what a strange option. Should default to true imho and the number 3 seems
rather arbitrary.
But anyway, at least they have that option.


[10.x] Trying to get XSRF from cookie if not found anywhere else

If the XSRF token is passed to the client in the cookie response, why not read it from the request cookie if it hasn't been passed anywhere else?
This will allow you not to send extra headers every time and not to show the decrypted CSRF token in the meta tag.
Reading a token from a cookie supports encryption if the middleware (\Illuminate\Cookie\Middleware\EncryptCookies::class) is enabled and will work correctly if disabled.

I believe this has come up many times before - it introduces a security exploit.

To elaborate slightly on the security aspect – we use CSRF tokens to protect against unintended requests that still carry the session since cookies are (depending on their settings and browser defaults) auto-submitted by browsers, sometimes even when the request is originating from another website. Therefore, in order to add any protection, the CSRF token must be transfered/read via another mechanism than a cookie.


Update token and logo - error: unsupported file modified: /dev/null

i got this msgs - unsupported file modified: /dev/null
https://github.com/solana-labs/token-list/pull/9235/checks?check_run_id=4575207689

@keone Could you please take a look it, thanks in advance


Can we decrease brightness of sidebar colour?

Hi @JulienMaille,
Thank you for creating this theme. It looks so much better than default one!
I don't know much about theming but I'd like to make a amall tweak for myself. Could you advise which files I should edit? Specifically I'd like to change the left sidebar background colours to be darker. This is personal preference but if you'd like to consider this for your relase it would help with text accessibility (color contrast). I installed spicetify via powershell.
Best,
Emil

Hello Emil, you wanna darken the sidebar color
https://github.com/JulienMaille/dribbblish-dynamic-theme/blob/1b018f0776e540c5838ffb1a35ab60e01e0a9b5e/dribbblish-dynamic.js#L412
Something like setRootColor("sidebar", lightenDarkenColor(darkerColHex,-40));


Handle OCSP staples in client certificates

While the RFC 6961/6066 CertificateStatus message is only defined for server certificates, the new formulation for TLS 1.3 where the staple is sent in the "status_request" extension body in the certificate in question applies equally well to client certificates as to server certificates, and indeed the extensions is allowed to appear in CertificateRequest messages (and thus for the client Certificates that respond to them).  That said, we currently seem a bit confused about this topic:
https://github.com/openssl/openssl/blob/28833f1465a2dd197f8df80a69095d1913e6e85e/ssl/statem/extensions_srvr.c#L341L343
It actually is defined; we just don't implement it.

This is related to #4449.
Also for the server certs, it turns out that staples are so far not implemented for intermediate certs (which was called OCSP multi-stapling for TLS 1.2), although required by TLS 1.3

@DDvO I don't understand your sentence.  Are you saying TLS 1.3 requires multi-stapling and including intermediate certificates?  I don't think so, please point to where in the RFC you got that conclusion; thanks.

What I mean is section <IP_ADDRESS>: https://tools.ietf.org/html/rfc8446#section-<IP_ADDRESS>

That section says that a server MAY request client cert status so it's not required to implement.  I am not sure how useful it is, since in most cases the origin server is going to authenticate and authorize the incoming client so it doesn't need OCSP data.  Perhaps someone who needs it will do a PR :)
That section also points out that each certificate status is in the separate certificate message, but is not meant to imply that every single cert in the message have OCSP data. I think co-mingling multi-staple with client cert is a bit confusing.

That section says that a server MAY request client cert status

Yes.

so it's not required to implement.

I see this a little different.
From the fact that the RFC allows the server to request the cert status from the client (which of course only makes sense if cert-based authentication of the client is used) I conclude that its TLS stack must support it - otherwise the server has no choice. And the RFC apparently does not state that support for this feature is optional.
What I find a bit ambiguous in the RFC is that in case the server requests the client cert status the client may opt to provide it - should this mean that the client-side implementation does not need to support this, or that the client must have the option to provide it, which would mean that its TLS stack must support it? I tend to understand it in the latter way.

Your conclusion is erroneous.  Either side is free to ignore any extensions that it does not implement, and the counter-party must decide, based on what it gets, wether or not to proceed.  You cannot conclude it's a MUST if the word MUST doesn't appear.  :)

Meanwhile I got a hint from a colleague:
RFC 8446 section 9.2 ("Mandatory-to-Implement Extensions", https://tools.ietf.org/html/rfc8446#section-9.2)
does not include the "status_request" extension (for OCSP responses), so I agree you are right their support is not mandatory.
In particular, OCSP staples for client certs are not required to be implemented for TLS 1.3.

Marking as inactive, to be closed at the end of 3.4 dev, barring further input

PR #20945 ?

is there no newer issue associated with that Pr?  Ok, my fault.

PR #20945 ?

That PR is for server cert multi-stapling not for client certs.

I've made the request somewhat more clear/strong explicitly mentioning multi-stapling
(which means to include the chain of intermediate certs).


My node version is 16.20 and cannot be upgraded. Which version should I use?

λ  yarn add @cyntler/react-doc-viewer
yarn add v1.22.19
warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
[1/5] Validating package.json...
[2/5] Resolving packages...
warning Lockfile has incorrect entry for<EMAIL_ADDRESS>Ignoring it.
warning @umijs/preset-react > @umijs/plugin-test > @umijs/test > jest-environment-jsdom-fourteen > @jest/environment > @jest/transform > jest-haste-map ><EMAIL_ADDRESS>The v1 package contains DANGEROUS / INSECURE binaries. Upgrade to safe fsevents v2
[3/5] Fetching packages...
error<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version ">=18". Got "16.20.0"
error Found incompatible module.
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.

λ node -v
v16.20.0

I found out that you upgraded the node last year, but I am unable to determine the NPM package version before the node upgrade.
Update node js version to 18
My node version is 16.20 and cannot be upgraded. Which version should I use?
Please.

Facing the same issue

Have you find any solution?

Same here
Got anything?

Same here, anything?

<EMAIL_ADDRESS>


URL underline and click-to-open stops at escaped quote

We sometimes encounter URLs that use escaped double-quotes (instead of url-encoding to %22). Browsers still typically accept these URLs, but Monaco stops parsing the URL when it encounters a double-quote. An example can be seen in the repro.
monaco-editor version: 0.21.2
Browser: Google Chrome
OS: MacOS 10.15.6
Playground code that reproduces the issue:
"https://www.foo.com?bar=\"baz\""

Let's track in https://github.com/microsoft/monaco-editor/issues/2145


Simplify plugin configuration

Pull Request Details
Sorry, but I got carried away over the weekend. This PR greatly simplifies the configuration of the plugin in a backward compatible manner (although I deprecated some properties). You may pick individual changes as you which, they are separated into semantically coherent commits.
The new minimal configuration looks like this:
grammarKit {
    lexerSource = layout.projectDirectory.file("<path to *.flex file>")
    parserSource = layout.projectDirectory.file("<path to *.bnf file>")
}

This configuration is mostly equivalent to the following configuration, as it would have to be written manually before my changes:
sourceSets {
    main {
        java {
            srcDir(layout.buildDirectory.dir("generated/sources/grammarkit-lexer/java/main"))
            srcDir(tasks.generateParser)
        }
    }
}

tasks {
    generateLexer {
        sourceFile = layout.projectDirectory.file("<path to *.flex file>")
        targetOutputDir = layout.buildDirectory.dir("generated/sources/grammarkit-lexer/java/main/<pkg>")
        purgeOldFiles = true
    }

    generateParser {
        sourceFile = layout.projectDirectory.file("<path to *.bnf file>")
        targetRootOutputDir = layout.buildDirectory.dir("generated/sources/grammarkit-parser/java/main")
        pathToParser = "<relative path to parser java file>"
        pathToPsiRoot = "<relative path to psi files>"
        purgeOldFiles = true
    }

    compileJava {
        dependsOn(generateLexer)
    }
}

Description
The new, much shorter configuration is possible due to the following individual changes:

Allow GenerateLexerTask to create a subdirectory for the package. This allows us to give the output directory to SourceDirectorySet.srcDir directly. The new behavior is applied if the new property targetRootOutputDir is used, which replaces targetOutputDir. (362e9fc374e)
Make GenerateParserTask.pathToParser and pathToPsiRoot optional. These properties are not needed in most cases, as they are only restricting purgeOldFiles to specific sub-paths of the output directory. (05af19486b5)
Make purging stale files the default. Without purging stale files, incremental builds may run into errors. When the build cache is enabled, even :clean may not be able to fix such issues. For backwards compatibility, the new behavior is only applied when the previously mentioned properties (which were mandatory) are no-longer used. (87ac8151377)
Add default values for targetRootOutputDir in both tasks. This simplifies the configuration and encourages people to use separate output directories for each task. Overlapping output directories are discouraged by Gradle and may cause issues with the build cache. (a8c60bd5088)
Introduce lexerSource and parserSource in the plugin extension. These properties make it possible to specify the source files without having to configure the individual tasks directly. When this property is used, the corresponding tasks are also added as sources to the main source set. (86022b4a4d7073)

I also revised some existing tests in commit a204e863866 and<PHONE_NUMBER>0, but this doesn't have much impact on the other changes. I updated the changelog in commit 1a13907270e.
Related Issue

resolves #178

Motivation and Context
This change makes using the plugin much easier.

You no-longer have to manually configure the directory for the generated files
Stale files are purged by default, preventing build failures in incremental builds
Duplicating information from the source files in the build configuration is no-longer necessary

The package of the lexer
The package of the parser
The class name of the parser
The package containing the PSI classes

You no-longer have to set up task dependencies manually

How Has This Been Tested
I created various “unit” tests to test my changes. (I tripled the total amount of unit tests in this repository.) Furthermore, I tried out the new version with, and without simplifying the configuration on the nix-idea plugin.
Types of changes

[x] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change) – but I deprecated stuff

Checklist

[x] I have read the CONTRIBUTING document.
[ ] My code follows the code style of this project. – Where do I get the code style?
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

I don't think the build failure on GitHub Actions is caused by my changes. The error actually looks quite familiar to me. I think I once fixed the same issue at JetBrains/gradle-changelog-plugin#170. 😅

I rebased this pull request on the current master after #187 has been merged to fix the build.


Error putting S3 policy: AccessDenied

I used the examples/create_rosa_sts_cluster/oidc_configuration/cluster_with_unmanaged_oidc_config to create a ROSA cluster.
I got following error message during creating the S3 bucket. I have no clue which right is missing:
│ Error: Error putting S3 policy: AccessDenied: Access Denied
│ 	status code: 403, request id: xxxx, host id: crypted_host_id
│
│   with module.oidc_config.module.oidc_config_input_resources[0].module.rosa_oidc_config_resources[0].aws_s3_bucket_policy.allow_access_from_another_account,
│   on .terraform/modules/oidc_config.oidc_config_input_resources/oidc_config_resources/create_s3_bucket.tf line 21, in resource "aws_s3_bucket_policy" "allow_access_from_another_account":
│   21: resource "aws_s3_bucket_policy" "allow_access_from_another_account" {

Configuration:

Using previously-installed hashicorp/aws v4.67.0
Using previously-installed terraform-redhat/rhcs v1.2.0-prerelease.1

Any idea?

Hi @fabian-born ,
Have you created rosa cluster on this account before?
If not, make sure you have Completed the ROSA getting started requirements
Have you tried also to use the examples/create_rosa_sts_cluster/oidc_configuration/cluster_with_managed_oidc_config?


Can't make space between section and cells

Hi
How i can make spaces between sections?
i'm using collectionview on storyboard, but inset parameters not working, there's special way to do it with IGListKit?

Hey @dekelm8, try changing the inset of your section controller, like:
class MySectionController: IGListSectionController, IGListSectionType {
  override init() {
    super.init()
    inset = UIEdgeInsets(top: 0, left: 0, bottom: 15, right: 0)
  }
}

Are you setting the insets on UICollectionViewFlowLayout? We had a suggestion to get global section insets working once, maybe we should revisit that.

Thanks that's work.
Really want to say thanks for the great support guys, It's really feel like IG team are full committed for this amazing framework
Thanks Again


pull request for e2e test at 01/06/2017 08:56:09

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Invalid TS typings in output files

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Error compile from source

Hi,
i'm trying to compile from source bwa-meme with the command:
sudo make -j 32

but i have this error and i don't know how to resolve. Can you help me, please?
error.log
I'm working on e2-standard-32 google machine type

Hi,
This fixes the issue!
I updated the code, you can pull the change and retry compiling.
Please let me know if there is another issue.


Bug with delay module in 1.16

Inverting Delay and distortion order and then putting Delay FB at 0db will mute the sound if delay is enabled until restart of the reaper session.
Vst3
Reaper 6.82
win 10

Can't reproduce this one, can you do screen recording or similar?

https://kdrive.infomaniak.com/app/share/795671/67091568-0264-490c-aa78-85c5a89f1a19
Sorry couldn't make obs to record audio, but hopefully you'll get it
It seems it's the drive module that is muting everything...
Not the preciser bug report I reckon !

https://kdrive.infomaniak.com/app/share/795671/085c4ff0-4684-4bba-8b27-0deff5ba4ff1
https://kdrive.infomaniak.com/app/share/795671/65dc2f62-f330-493d-a3f8-36e9e23c6470
Those presets will make some sound when I hit play in reaper. This is due to the delay FX (no problem if disabled)


1000+ series per host causes slow performance in influxdb

I'm running a test using influxdb 9.2 nightly and telegraf 0.1.3 on a single host with SSD. I am sending metrics from 500 hosts to influxdb using telegraf's default plugins and config. Within a week, influxdb begins returning 500 timeout errors to all requests. The database size is 340G with 137,269 unique series.
In https://influxdb.com/docs/v0.9/concepts/schema_and_data_layout.html, it mentions keeping tag cardinality <100k so I dug in to see where all of the tags are coming from. Each VM host sends about 150 series while a physical hypervisor sends over 1000.
Here is the breakdown from one physical server:
disk metrics: 180 (6 metrics * 30 paths)
cpu metrics: 352 (11 data points * 32 cores)
io metrics: 378 (7 metrics * 54 disk partitions)
net metrics: 128 (8 metrics * 16 interfaces)
load/swap metrics: 9
Here is the best case result (with filtering and CPU aggregation):
disk metrics: 48 (6 metrics * 8 paths)
cpu metrics: 11 (11 data points * 1 aggregate cpu value)
io metrics: 378 (7 metrics * 16 disks in iostat)
net metrics: 128 (8 metrics * 16 interfaces)
load/swap metrics: 9
The same update of a VM host reduces the per host metric count from 146 to 50. The doc says "As a rule of thumb, keep tag cardinality below 100,000. " With 1000 series per host, that is at most 100 servers. Even the low end, 50 metrics per host only allows around 2,000 servers. Is this a limitation that can be addressed in telegraf or influxdb?
I love the simplicity and drop-in nature of the telegraf/influxdb/grafana stack. But the system needs to be able to scale out of the box. Multiple databases would make grafana more complex but it might be an short term solution. Is there a better way?

@jhofeditz -- can we see your InfluxDB config file?

https://gist.github.com/jhofeditz/934d8e7f296be1501707

Re-reading the schema and data layout page, is the limit referring to the number of unique values per tag (host=) or the total number of unique tag series (host=,name=,serial=)? My maximum unique values per tag is only around 5,000.
If having >100,000 series is ok, then this is a InfluxDB issue and I'll open the issue there.

D'oh! I might need to change the subject to "telegraf running 100x on one host causes slow performance" :fearful: It turns out that on one server puppet was spawning lots of telegraf clients because /etc/init.d/telegraf status said that telegraf was stopped.
We'll watch to make sure that doesn't happen again. We wiped the database and are now going to give things another week to see how it performs. Sorry about the false alarm.
I would still like to know if the number of metrics is going to impact influxdb at scale, but this specific issue seems to be unrelated. Thanks!


[BUG] Training does not start with the lion optimizer

Code:
optim = create_optimizer_v2(self, 'lion', lr, self.weight_decay)
Error (optimizer Lion):
File "/usr/local/lib/python3.8/dist-packages/timm/data/auto_augment.py", line 382, in __call__     if self.prob < 1.0 and random.random() > self.prob: TypeError: '<' not supported between instances of 'dict' and 'float'
If I start training with other optimizers (for example Adam), then everything works fine

what's self?  ... self is supposed to be the model being trained or parameters, but self also has a weight decay attribute so it's clearly something else...

I've been trialing lion optimizer quite a bit recently w/o issue, not clear what the use context is so closing for now as nothing to go on.


build command times out before ESO container is created

I am trying to build and the process keeps failing because it times out before the EOS container is up and running. I cannot find anywhere to up the wait time or wait indefinitely until EOS container is ready.
yarn run build --> lamington build
thanks!
Gabriels-MBP:skygrid-dapp gabe$ yarn run build
yarn run v1.17.3
$ lamington build
⠼ Starting EOS docker containerREPOSITORY          TAG                                          IMAGE ID            CREATED             SIZE
lamington           eos.v1.8.6-cdt.v1.6.1-contracts.v1.8.0-rc1   5476bb39c8a0        3 hours ago         967MB
⠦ Starting EOS docker container6e22a0cfec884a6be7585cbe63d6d7256cbe6fccce9bd28ca589a8bc7802b542
✔ Starting EOS docker container
✖ Failed to connect with an EOS instance
--> Error: Could not contact EOS after trying for 20 second(s).
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

It really shouldn't take more than 20 seconds to connect to EOS after the docker container is up and running, so I suspect increasing the timeout won't help.
Can you start the docker container yourself outside of lamington to see if EOS is indeed running in there?

I'll assume this is resolved at this point. If you still need help feel free to open a new issue.


Migrated to kotlin gradle, made the project work with jitpack

There's also a fix for #8, i did it before gradle stuff, should I make another fork and add only the gradle changes?

Migrated! Thank you so much for that PR! I've used some hints from here, that I also faced during migration!


COMP: Ensure ITK libraries can be found by dependent projects

See https://github.com/InsightSoftwareConsortium/ITK/issues/1897

Should we just disable ParameterSerializer in Slicer ?

support for dependent packages mentioned

This is done by using the find_dependency function.
I just created an issue to describe what should be done next. See https://github.com/Slicer/ParameterSerializer/issues/9


[BUG]: Cert-csi Qualification failing for OCP 4.17 rca environment.

Bug Description
Cert-csi test is failing with the below error for all the suites in OCP 4.17 rca environment.

Logs
error_logs.txt
Screenshots
No response
Additional Environment Information
No response
Steps to Reproduce
Cluster: OCP 4.17 RCA build
Install operator and driver should be up and running
Install cert-csi
Run : ./cert-csi --debug certify --cert-config config.yaml --vsc vxflexos-snapclass
Expected Behavior
All the suites should pass .
CSM Driver(s)
Powerflex
Installation Type
Operator 1.6.0
Container Storage Modules Enabled
NA
Container Orchestrator
OCP 4.17 RCA
Operating System
Red Hat Enterprise Linux 9.4

The errors are converted into warnings in 4.17 GA build and the suite is passing. Although the changes are present in branch security_context_changes of cert-csi . Closing the issue.


Proposal: Add option "Auto build" in Settings

I think it would be great to have an option like this:

Where you can choose where in the typescript file to build and choose whether you want these to be built or not.

Where you can choose where in the typescript file to build and choose whether you want these to be built or not.

Already exists as an option on tsconfig.json : https://github.com/TypeStrong/atom-typescript/blob/master/docs/tsconfig.md#buildonsave
Should add it to FAQ. Will do that soon :rose: leaving open till then


Builder breaks when field is named self_

Version: 3.3.1
Code:
#[derive(bon::Builder)]
struct Test {
    self_: String
}

Message:
error: bug in the `bon` crate: the macro generated code that contains syntax errors; please report this issue at our Github repository: https://github.com/elastio/bon;
       syntax error in generated code: Error(
           "expected identifier, found keyword `Self`",
       );
       generated code:
       ```rust
                       #[allow(unnameable_types, unreachable_pub, clippy :: redundant_pub_crate)]
       #[doc =
       "Tools for manipulating the type state of [`TestBuilder`].\n\nSee the [detailed guide](https://bon-rs.com/guide/typestate-api) that describes how all the pieces here fit together."]
       mod test_builder
       {
           #[doc(inline)] pub(super) use :: bon :: __ :: { IsSet, IsUnset }; use ::
           bon :: __ :: { Set, Unset }; mod sealed
           { pub(in super :: super) struct Sealed; }
           #[doc =
           "Builder's type state specifies if members are set or not (unset).\n\nYou can use the associated types of this trait to control the state of individual members with the [`IsSet`] and [`IsUnset`] traits. You can change the state of the members with the `Set*` structs available in this module."]
           pub(super) trait State : :: core :: marker :: Sized
           {
               #[doc =
               "Type state of the member `self_`.\n\nIt can implement either [`IsSet`] or [`IsUnset`]"]
               type Self; #[doc(hidden)] const SEALED : sealed :: Sealed;
           }
           #[doc =
           "Marker trait that indicates that all required members are set.\n\nIn this state, you can finish building by calling the method [`TestBuilder::build()`](super::TestBuilder::build())"]
           pub(super) trait IsComplete : State
           { #[doc(hidden)] const SEALED : sealed :: Sealed; } #[doc(hidden)] impl <
           S : State > IsComplete for S where S :: Self : IsSet,
           { const SEALED : sealed :: Sealed = sealed :: Sealed; }
           #[deprecated =
           "this should not be used directly; it is an implementation detail; use the Set* type aliases to control the state of members instead"]
           #[doc(hidden)] #[allow(non_camel_case_types)] mod members
           { pub(in super :: super) struct self_(()); }
           #[doc =
           r" Represents a [`State`] that has [`IsUnset`] implemented for all members."]
           #[doc = r""]
           #[doc =
           r" This is the initial state of the builder before any setters are called."]
           pub(super) struct Empty(());
           #[doc =
           "Represents a [`State`] that has [`IsSet`] implemented for [`State::Self`].\n\nThe state for all other members is left the same as in the input state."]
           pub(super) struct SetSelf < S : State = Empty >
           (:: core :: marker :: PhantomData < fn() -> S >); #[doc(hidden)] impl
           State for Empty
           {
               type Self = Unset < members :: self_ > ; const SEALED : sealed ::
               Sealed = sealed :: Sealed;
           } #[doc(hidden)] impl < S : State > State for SetSelf < S >
           {
               type Self = Set < members :: self_ > ; const SEALED : sealed :: Sealed
               = sealed :: Sealed;
           }
       }
       #[must_use =
       "the builder does nothing until you call `build()` on it to finish building"]
       #[doc =
       "Use builder syntax to set the inputs and finish with [`build()`](Self::build())."]
       #[allow(unused_parens)]
       #[allow(clippy :: struct_field_names, clippy :: type_complexity)] struct
       TestBuilder < S : test_builder :: State = test_builder :: Empty >
       {
           #[doc(hidden)]
           #[deprecated =
           "this field should not be used directly; it's an implementation detail, and if you access it directly, you may break some internal unsafe invariants; if you found yourself needing it, then you are probably doing something wrong; feel free to open an issue/discussion in our GitHub repository (https://github.com/elastio/bon) or ask for help in our Discord server (https://bon-rs.com/discord)"]
           __unsafe_private_phantom : :: core :: marker :: PhantomData <
           (fn() -> S, fn() -> :: core :: marker :: PhantomData < Test < > > ,) > ,
           #[doc(hidden)]
           #[deprecated =
           "this field should not be used directly; it's an implementation detail, and if you access it directly, you may break some internal unsafe invariants; if you found yourself needing it, then you are probably doing something wrong; feel free to open an issue/discussion in our GitHub repository (https://github.com/elastio/bon) or ask for help in our Discord server (https://bon-rs.com/discord)"]
           __unsafe_private_named : (:: core :: option :: Option < String > ,),
       } #[allow(unused_parens)] #[automatically_derived] impl < S : test_builder ::
       State > TestBuilder < S >
       {
           #[doc = r" Finish building and return the requested object"]
           #[inline(always)]
           #[allow(clippy :: inline_always, clippy :: future_not_send, clippy ::
           missing_const_for_fn,)]
           #[must_use = "building a struct without using it is likely a bug"] fn
           build(self,) -> Test < > where S : test_builder :: IsComplete
           {
               let self_ : String = unsafe
               {
                   :: core :: option :: Option ::
                   unwrap_unchecked(self.__unsafe_private_named.0)
               }; Test { self_, }
           } #[doc = "_**Required.**_\n\n"]
           #[allow(clippy :: inline_always, clippy :: impl_trait_in_params, clippy ::
           missing_const_for_fn,)] #[inline(always)] fn
           self_(mut self, value : String) -> TestBuilder < test_builder :: SetSelf <
           S >> where S :: Self : test_builder :: IsUnset,
           {
               self.__unsafe_private_named.0 = :: core :: option :: Option ::
               Some(value); TestBuilder
               {
                   __unsafe_private_phantom : :: core :: marker :: PhantomData,
                   __unsafe_private_named : self.__unsafe_private_named,
               }
           }
       }
       ```
 --> random\src\lib.rs:4:10
  |
4 | #[derive(bon::Builder)]
  |          ^^^^^^^^^^^^
  |
  = note: this error originates in the derive macro `bon::Builder` (in Nightly builds, run with -Z macro-backtrace for more info)

A note for the community from the maintainers
Please vote on this issue by adding a 👍 reaction to help the maintainers with prioritizing it. You may add a comment describing your real use case related to this issue for us to better understand the problem domain.

Thank you for reporting this! I've made a fix to the macro so that it generates Self_ instead of Self when turing the member name into pascal case. Self is the only uppercase keyword in Rust, so this was a special case. The fix was released in a new patch 	3.3.2


registration_token_file is mentioned in hosted docs, but does not actually exist

Saw it mentioned here. Apparently these docs are hosted not from the main branch but some other. I got pretty confused trying to figure this out.
In any case, I believe I need this configuration option in order to securely inject a secret token into the NixOS matrix-conduit service. Generally when plumbing secrets around in NixOS, we avoid ever putting the plaintext directly into a config variable, because this ends up in the /nix/store, visible to all users on the system. Instead, I use SOPS to decrypt the secret and write it to /run/secrets. The file is ready, I just need the ability for conduwuit to read it.

This is already being added in https://github.com/girlbossceo/conduwuit/pull/608, it wasn't removed and its inspiration to be added was for Nix users. I will have to investigate why GitHub Pages are being deployed from branches other than main or tags.


(SpinButton) DefaultValue field does not function, cannot reset control value

The SpinButton component's DefaultValue property seems to have no effect on the control's value. In addition, Reset([SpinButtonControl]) does not work, meaning it is impossible to refresh the component's value without refreshing the app. This presents issues when using the SpinButton for submittable forms, etc.

I have the same issue. Impossible to use the spinbutton unfortunately. Hope someone has a look into it soon, because the spinbutton itself is an awesome thing!

+1 I've seen the same thing.  The value state can't be reset when moving back and forth between canvas screens.  It is somehow maintaining the .value property and I can't reset.  If I increment the control, it resets the value to what is displayed on the screen.

While not a great solution, I did come across an interesting way to reset the SpinButton control leveraging the Suffix property.
Set a variable in the Suffix property of the SpinButton:

When you want to reset the control to the DefaultValue. Set the suffix variable to an empty space (" ").

This triggers a re-render of the control which defualts it back to the DefaultValue.
After this, using a timer control I clear the tempSuffix variable back to blank, I found that in order for the re-render to occur the suffix had to be different. Having this allowed me to reuse the above logic throughout my app 🙂

Hopefully this workaround helps, its a great control so hopefully someone is having a look at this 🙂

This workaround works for me!  thanks for that.  It would be awesome for their to be a reset event or for it to re-render on visible or something similar


remove old config from INC 2.x API

Type of Change
API changed or not
Description
JIRA: https://jira.devtools.intel.com/browse/ILITV-2751
Expected Behavior & Potential Risk
N/A
How has this PR been tested?
unit test
Dependency Change?
N/A

extension test：https://inteltf-jenk.sh.intel.com/job/intel-lpot-validation-top-mr-extension/4813/

extension test rebuild: https://inteltf-jenk.sh.intel.com/job/intel-lpot-validation-top-mr-extension/4838/


Constant time len

Fixes #45
Closes #105

I'm not sure what the right approach to testing this is.

I'm not sure what the right approach to testing this is.

Do you mean benchmarking the constant length or checking that select which uses len() is valid?
You already added tests for the select method so... Nothing more to do.

However, checking that the length is valid is maybe a little bit complex

This is what I meant. I'm trying to think of a clean way to debug_assert that each time the len changes we compare it against the computed len

This is what I meant. I'm trying to think of a clean way to debug_assert that each time the len changes we compare it against the computed len

Wouldn't it be ok to directly do debug_assert_eq!(self.iter().count(), self.len())? As the macro expansion is done at compile-time, therefore the call to iter/count is only done for debug builds.
I just hope that we haven't implemented the count method on our iterator to only call self.len() 😂

I just checked in the playground and the macro expansion indeed work like that: it didn't panic when compiling in release.

Of course it does. Why should it recompute the cached len?

Ok so we should trick by doing a fold instead.

Of course it does. Why should it recompute the cached len?

Ok so we should trick by doing a fold instead.

We'd probably have to wrap it in a black_box. LLVM is very clever.


Replace docker-compose with docker compose

Overview

N/A
Checklist

[ ] I have run this code in development and it appears to resolve the stated issue
[ ] This PR includes tests, or tests are not required/relevant for this PR
[ ] README.md updated and added information about my change
[ ] I have run changie new to create a changelog entry

Tests are red but it looks unrelated to the change.
cc @damian3031

Tests are red but it looks unrelated to the change. cc @damian3031

It's unrelated, these tests are also failing on master. I'll create separate issue and investigate that.

I would add changelog entry about switching to docker compose v2, as this is major version bump https://github.com/docker/compose#about-update-and-backward-compatibility

I would add changelog entry about switching to docker compose v2,

@damian3031  this change affects AFAIK only the test environment. I don't see it noteworthy at the moment. However, please point me where to add the change notes if you feel strongly about it.

I would add changelog entry about switching to docker compose v2,

@damian3031 this change affects AFAIK only the test environment. I don't see it noteworthy at the moment. However, please point me where to add the change notes if you feel strongly about it.

fair enough, I am not strongly in favor of it


Tuple withFst/Snd

To emulate tuple sections.

withFst(x) == (x,)
withSnd(x) == (,x)

https://github.com/samhh/fp-ts-std/commit/1a8900a485560d2f799d1ff2eb09267c3f97a0d0


Report 1304 "Standard Sales - Quote" SetLanguage()

Please add an publisher to the procedure SetLanguage in Report 1304 "Standard Sales - Quote":
[IntegrationEvent(false, false)]
local procedure OnAfterSetLanguage()
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 46955.


Docker version label out of sync

The values for the Docker version labels are out of sync. Example:

org.opencontainers.image.version="9.7.0"

source: https://github.com/CycloneDX/cdxgen/blob/master/ci/Dockerfile#L7
I guess as long as the version is manually managed as part of a regular commit (example) it is going to be difficult to keep the versions in sync. Maybe automatically update the labels using the package.json#version as the single source of truth (Git hook, GH actions step)?

@marcelstoer, you are correct. The process is manual. Have you seen any automated way of doing this?

I've seen a couple of approaches in my career so far:

as part of a release pipeline: the build process would update the version in dependent artifacts (here: Dockerfile), amend the current commit, force push the new state
Git hook: locally via a pre-commit, don't think I ever saw this on remote repo (pre-receive)
update-version in the project root: would take the new version is first argument

To keep life simple, I have set docker labels as 9.8.x, which is close enough.


CSE apt lock hygiene

only invoke an apt command if nothing else is holding a lock
only return after an apt command after locks are verified released

What this PR does / why we need it: Don't run apt commands unless we validate there isn't an apt lock held elsewhere; explicitly wait for lock release after running an apt command.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
If applicable:

[ ] documentation
[ ] unit tests
[ ] tested backward compatibility (ie. deploy with previous version, upgrade with this branch)

Release note:

CSE apt lock hygiene

/lgtm


Creating a reference inside Subcollection

I'm trying to reference an item inside a subcollection and it's not working. Collection and Subcollection are embedded.
Does this work?
Document
+Collection
+Subcollection
+Reference

Hello,
can you paste your code please I did not understand your issue.

Hello, RelMongo does not support references in subcollections


Add SalmonellaFilter

Changelist SalmonellaFilter is implemented

This is a fantastic improvement, thank you! I need to clean this project a bit before i can merge it.

Thank you for merging it! Late is better than never.


[Bug] ISymTable::VisitScope() works incorrectly

Bug report
ISymTable::VisitScope() method works incorrectly, it always choose first scope in list instead of iterating over them.
Environment
Win 10 x64 / Visual Studio 2017
Steps to reproduce the issue

What's the expected result?
VisitScope() should enter first nested scope. The next call of it also move pointer deeper into scopes' tree. But when a user invokes LeaveScope() the pointer should go up to parent scope and move to next available neighbour scope.
What's the actual result?
LeaveScope() doesn't move pointer to next neighbour.

Fixed in efb68224651bab96ff047ced8d5234a3bfa00414


Course ended banner

Description of the PR

Banner for when the course has ended
Closes #610

Testing

unit
integration
e2e
manual

- [x] new unit tests created
- [x] all unit tests pass

- [ ] new integration tests created
- [x] all integration tests pass

- [ ] new e2e tests created
- [x] all e2e tests pass

- [x] manual testing went well

Have you updated the TESTING.md or other relevant documentation on your branch?

[ ] Yes.
[ ] Not yet. I will do it next.
[x] Not relevant.

One comment more: Have you considered making text and color ObservableReadOnlyPropertys and for them, declareDependentOn user? Ideally, there shouldn't be update methods but data should be computed when it's requested.
That would, however require you to implement some kind of caching for ObservableReadOnlyProperty. If you are interested in trying that, you can make a subclass of it that holds the value in Optional<T> field. Then override get to call the getter only if the cached value ain't there (and update it). Then override onValueeChanged to invalidate the cached value before calling super.onValueChanged(...).


Inspect spelling is wrong.

VSCode Version: Code 1.17.0 (be377c0faf7574a59f84940f593a6849f12e4de7, 2017-10-05T06:07:51.906Z)
OS Version: Darwin x64 16.7.0
Extensions:

Extension
Author (truncated)
Version

vscode-helm
tec
0.3.0

Unable to open 'Inspect': Error: unknown command "inpsect" for "helm"

Steps to Reproduce:
1.Right Click and click inspect chart

Reproduces without extensions: Yes/No

Looks like this is from an extension, please open an issue on their repo.


Create Dynamic Array.cpp

Related Issue
Closes: #475
Describe the changes you've made
Added solution in cpp of Dynamic array of hackerank
Language used for coding
C++
Checklist:

[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have documented the code.
[x] New and existing unit tests pass locally with my changes.

@Nivedita967 plss review it


Set up a customer details page

Problem
Right now the only way to view a customer's details is in a relatively small modal.
Eventually we'll want to show a lot more information around customers (such as tags, company info, latest conversations, etc), so we should set up a full page UI for displaying customer details.
Solution
Set up a customer details page.
TODO:

include some designs/screenshots for inspiration
include what information we want to display

Describe alternatives you've considered
We currently just show the info in a modal.
Additional context
Users have requested the ability to see all conversations by customer more easily.
Testing
Please include a screenshot of any UI updates in your PR!
Questions, or need help getting started?
Feel free to ask below, or ping us on Slack :)
(You can also check out our CONTRIBUTING.md)

Sample design from Intercom:

Sample design from Crisp:

We'll probably want to add a bunch of enhancements to this page, but for now the basic page is done :+1:


[BUG] calGridColor not changing

Prerequisites

[x ] Put an X between the brackets on this line if you have done all of the following:

Checked the Quick Start documentation page and confirmed configuration is correct: https://marksie1988.github.io/atomic-calendar-revive/quickstart.html
Checked the FAQs on documentation page for common solutions: https://marksie1988.github.io/atomic-calendar-revive/faq.html
Checked that your issue isn't already filed: https://github.com/marksie1988/atomic-calendar-revive/issues?q=is%3Aissue

Describe the bug
When setting the calGridColor option, the color doesnt change
Steps to Reproduce

set calGridColor

Expected behavior
Calendar view grid color should change to provided color
Actual behavior:
nothing happens
Screenshots
the border should be a pastel yellow but stays grey.

Card Configuration
calGridColor: 'rgba(253, 253, 150, .35)'

Versions

HomeAssistant Version: 110
Plugin Version: 1.5.3

Additional Information

I have noticed that this happens to any config that is within the CSS Styles section


Add Travis dependencies for Node 4.x

@achingbrain Not sure if this will fix the issue that you mentioned in #75 about Travis failing, but this is what we've had to do on other projects. Travis is experiencing technical difficulties today, but I'll check back once the build completes.

Awesome, thanks!

Np! Glad to help. Thanks for the awesome project!


Chapter about Booleans

hey can I help

Nice
On Fri, 30 Jul 2021, 7:06 pm kaneki, @.***> wrote:

hey can I help
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/GitbookIO/javascript/issues/10#issuecomment-889992972,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AN6LY62FDKBH2S7FMNZ6A3LT2LEZXANCNFSM4AN6NKPQ
.

7y

damn thats a long time ago


chore: Add blocks to the grid of sw-mail-template-list

1. Why is this change necessary?
Better extensibility.
2. What does this change do, exactly?
Add some blocks, where no blocks where present.
3. Describe each step to reproduce the issue or behaviour.
4. Please link to the relevant issues (if any).
5. Checklist

[ ] I have written tests and verified that they fail without my change
[x] I have created a changelog file with all necessary information about my changes
[ ] I have written or adjusted the documentation according to my changes
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/NEXT-22183
Please use this issue to track the state of your pull request.

Thanks! :)


Enable singleUserConfiguration Not work

What steps will reproduce the bug?
When I enabled singleUserConfiguration，but nifi pod did not start normally
  singleUserConfiguration:
    enabled: true
    authorizerEnabled: false
    secretRef:
      name: "single-user-credentials"
      namespace: "nifi"
    secretKeys:
      username: "username"
      password: "password"

I found that the authors.xml file could not be found in the path

What is the expected behavior?
I expected that the pod should find the authors.xml file and start normally
What do you see instead?
ssh into the pod and see that the file does not exist in the conf path.

Possible solution
No response
NiFiKop version
v1.5.0
Golang version
go v1.20
Kubernetes version
v1.28.2
NiFi version
No response
Additional context
No response

Hi,
Can you try with
 singleUserConfiguration:
    enabled: true
    authorizerEnabled: true <---
    secretRef:
      name: "single-user-credentials"
      namespace: "nifi"
    secretKeys:
      username: "username"
      password: "password"

@juldrixx Thank you! It works!


Front left corner of Bambu lab printer leading to print failures

Maybe related to temperature or leveling.
Thanks for raising this @Neil-YL

Maybe post on or search Bambu lab forums at some point?

Maybe post on or search Bambu lab forums at some point?

I was told Bambu‘s got an Ai chatbot for troubleshooting, may also give it a try tomorrow

I asked the AI chatbot about the heat bed adhesion troubleshooting and followed this wiki for the manual reset of the bed leveling.
The process required running a G-code command provided in the wikipage and manually adjusting three screws beneath the bedplate. After that, I ran the calibration for both the micro lidar and bed leveling from the Bambu studio.

It seemed that the micro lidar’s calibration board on the right needed cleaning, so I wiped it with a disinfecting wipe. Guide of cleaning lidar and calibration board
This is the micro lidar calibration board:

I tested with two previously failed print jobs, and the adhesion performance has noticeably improved on the left/top edge:

Kevin will have some models printed in the coming days, so we’ll see if the issue is fully resolved.

Kevin said he had several parts printed without any issues last week. If the printer in SLD2 is experiencing similar adhesion issues (according to @cyrilcaoyang ), it may be worth trying this manual bed levelling process as well.


No such file or directory

i recently created #947 on the mypyc repo.
i'm not too optimistic in them helping on this, so i was wondering if you maybe had any other ideas? it seems that this might be a hatch-mypyc issue in the first place.

The package directory differs from the project name https://hatch.pypa.io/latest/plugins/builder/wheel/#default-file-selection
Add:
[build.targets.wheel]
packages = ["src/repro"]

ah, ty

Anytime!


Peer forwarder first cut

Issue #, if available:
Description of changes:
This PR adds the first cut of peer-forwarder plugin.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Also, is there a way to suppress all the unrelated changes from showing up in the PR UI?

@wrijeff My bad. I just synced the side branch with the latest master.

@wrijeff @kowshikn Thanks for the review. Did the change of listing data-prepper ips including localhost. Also merged renamed master.

Tested with the following setup:
version: "3.7"
services:
  data-prepper:
    restart: unless-stopped
    container_name: data-prepper
    build:
      context: ../..
      dockerfile: examples/Dockerfile
    working_dir: /app
    command: sh data-prepper-wait-for-odfe-and-start.sh
    volumes:
      - ../data-prepper-wait-for-odfe-and-start.sh:/app/data-prepper-wait-for-odfe-and-start.sh
      - ../trace_analytics_no_ssl.yml:/app/trace_analytics_no_ssl.yml
      - ../demo/root-ca.pem:/app/root-ca.pem
    ports:
      - "21890:21890"
    networks:
      - my_network
    depends_on:
      - opendistro-for-elasticsearch
  data-prepper2:
    restart: unless-stopped
    container_name: data-prepper2
    build:
      context: ../..
      dockerfile: examples/Dockerfile
    working_dir: /app
    command: sh data-prepper-wait-for-odfe-and-start.sh
    volumes:
      - ../data-prepper-wait-for-odfe-and-start.sh:/app/data-prepper-wait-for-odfe-and-start.sh
      - ../trace_analytics_no_ssl.yml:/app/trace_analytics_no_ssl.yml
      - ../demo/root-ca.pem:/app/root-ca.pem
    ports:
      - "21891:21890"
    networks:
      - my_network
    depends_on:
      - opendistro-for-elasticsearch
  opendistro-for-elasticsearch:
    container_name: node-0.example.com
    image: 'amazon/opendistro-for-elasticsearch:1.10.1'
    ports:
      - '9200:9200'
      - '9600:9600'
    environment:
      - discovery.type=single-node
    networks:
      - my_network
  kibana:
    build:
      context: ../..
      dockerfile: examples/kibana-trace-analytics/Dockerfile
    container_name: odfe-kibana
    ports:
      - 5601:5601
    expose:
      - "5601"
    environment:
      ELASTICSEARCH_URL: https://node-0.example.com:9200
      ELASTICSEARCH_HOSTS: https://node-0.example.com:9200
    networks:
      - my_network
  otel-collector:
    restart: unless-stopped
    image: otel/opentelemetry-collector:0.14.0
    command: ["--config=/etc/otel-collector-config.yml"]
    volumes:
      - ./opentelemetry-collector/otel-collector-config.yml:/etc/otel-collector-config.yml
      - ../demo/demo-data-prepper.crt:/etc/demo-data-prepper.crt
    ports:
      - "55680:55680"
    depends_on:
      - data-prepper
    networks:
      - my_network
  mysql:
    restart: unless-stopped
    image: mysql:latest
    ports:
      - "3306:3306"
    environment:
      - MYSQL_ALLOW_EMPTY_PASSWORD=yes
    networks:
      - my_network
  sample-app:
    restart: unless-stopped
    build:
      context: sample-app
      dockerfile: Dockerfile
    ports:
      - '8082:8082' # inventory
      - '8083:8083' # database
      - '8084:8084' # payment
      - '8085:8085' # auth
      - '8086:8086' # recommendation
      - '8087:8087' # analytics-service
      - '8088:8088' # order
      - '8089:8089' # client-dashboard
    environment:
      - OTEL_EXPORTER=otlp
      - OTEL_EXPORTER_OTLP_ENDPOINT=otel-collector:55680
      - OTEL_RESOURCE_ATTRIBUTES=service.name=analytics-service
      - OTLP=otel-collector
      - MYSQL_HOST=mysql
      - MYSQL_PORT=3306
      - WAIT_HOSTS=otel-collector:55680, mysql:3306
    depends_on:
      - otel-collector
      - mysql
    networks:
      - my_network
networks:
  my_network:

entry-pipeline:
  delay: "100"
  source:
    otel_trace_source:
  processor:
    - peer_forwarder:
        data_prepper_ips: ["data-prepper", "data-prepper2"]
        time_out: 300
        span_agg_count: 48
  sink:
    - pipeline:
        name: "raw-pipeline"
    - pipeline:
        name: "service-map-pipeline"
raw-pipeline:
  source:
    pipeline:
      name: "entry-pipeline"
  processor:
    - otel_trace_raw_processor:
  sink:
    - elasticsearch:
        hosts: [ "https://node-0.example.com:9200" ]
        cert: "/app/root-ca.pem"
        username: "admin"
        password: "admin"
        trace_analytics_raw: true
service-map-pipeline:
  delay: "100"
  source:
    pipeline:
      name: "entry-pipeline"
  processor:
    - service_map_stateful:
  sink:
    - elasticsearch:
        hosts: ["https://node-0.example.com:9200"]
        cert: "/app/root-ca.pem"
        username: "admin"
        password: "admin"
        trace_analytics_service_map: true

data-prepper and data-prepper2 connects to the same ES backend.


Port over to inductive strings. Generic determinsitic automata

Apologies for this monster PR. My goal was to fold in dyck-tracey and then get everything on the same page with respect to an inductive definition of Kleene star and a more generic definition of automata. But modular changes have escaped me this week
The changes are

Removing dead code. Such as Examples.Dyck and Inductive, as we can just make use of the indexed versions
An indexed, inductive version of Kleene star, and corresponding refactors in all of the places that used Kleene star/strings
Aiming at a more reusable definition of deterministic automaton
Migrate the decidability part of the determinization construction to be more portable. Now I import Quiver from cubical-categorical-logic and prove decidability of reachability on that level of generality. Due to this import, cubical-categorical-logic is taken as a dependency in the .agda-lib
the incoming changes from dyck-tracey. There is a missing hole, I think you didn't push some changes that included the definition of ⊗-unit-l⊗-assoc. Further, there are still associativity holes at the bottom of LinearProduct. All of these holes are probably best left as is, as we keep circling the necessity of the coherence theorem

More on 3: the definition of a deterministic automaton that is in Automaton.Deterministic does generalize the previous DFA definition. I had hoped to also generalize the automaton in Indexed.Dyck, but couldn't find a satisfying way. In particular, it is not clear how to expose the DeterministicAutomaton interface to take in a type of tags. Or rather, what is the right property that needs to hold over the type of tags such that the parse and print terms remain generically definable. I think I can experiment more on this, but I want to check everything in before diverging even further
More on 2: just as we did with NFAs, I have preserved a manual version of Kleene star. This makes the NFA-regex isomorphism the only place that makes use of either of these manual definitions, and they can be migrated later

So does this subsume https://github.com/maxsnew/grammars-and-semantic-actions/pull/25?

Quiver is already defined upstream in cubical do you really need to depend on cubical-categorical-logic for this?

@stschaef can you remove the unnecessary dependency on cubical-categorical-logic? You might need to bump the version of cubical in the CI. Also let's not push holes onto main. Comment out whatever proofs depend on the coherence stuff.

@stschaef fix the CI and the whitespace pls


Add contributing doc

📜 Description
This PR adds a "CONTRIBUTING" file at our root level. We want to provide contributors a better understanding how they can work in our project.
💁 Detailed changes:

adds "CONTRIBUTING.md"

"Contributing Guidelines" are based on existing examples from the aiven repositories

❗ I've made some slight changes to that:

I made some sentences more clear to read in order to make it more accessible (based on suggestions from Hemmingway.app)
I added a paragraph about the code of conduct and linked or COC. I feel it's important to make people aware of us following a COC, right in probably one of the first files a contributor would look at.

I added a first draft for creating commit messages. I based the recommendations on the Conventional Commits and How to Write a Git Commit Message. The latter is the article that the aiven internal etiquette for commit messages is also based upon.

Feedback welcome!
I appreciate feedback for this first draft 🙏! The commit message guideline will be grow in the future. I tried to keep it simple for now and e.g. only add prefixes where I felt they will definitely be useful. This should be used as a proposal which we should align upon together.
Resolves: #94
Relates to: #99

**❓  Question **
The linked article about commit messages also recommends:

always start description with a capitalised letter
never use a period at the end of a description

Should we add these also as recommendations (or other rules to form) or is that less important to us?
As you can see with my two commit messages in this PR, I'm already inconsistence because I've a hard time not using a . at the end 🙈


Simplify NPM examples

[x] Remove web server JS from "Hello World" examples and split into its own example
[x] gh-pages for dists

Addressed by devappd/emscripten-npm-examples@63ca0be68f70a8d9861ced19fce5e9ac25afd4e4 and devappd/emscripten-npm-examples@137dca9ff1b43b0cc2d0d957f7e3da97b2388c44


What about points of discontinuity?

The readme says:

Given an expression like x(x + 2 * 3) / (x + 6), slide should be able emit the simplified expression x.

What happens when x = -6? Does slide preserve that the function is not defined on some points in the domain?

Great question. In time, yes. To do this rigorously, a solver/prover (probably Z3, but maybe something else) would need to be incorporated. However there is a lot to do before this is even a priority, and sadly even if I had the time to work on this project seriously it would be at least a year.
Thanks for the issue.


SpendTx's transaction should be an Option

See https://github.com/revault/practical-revault/issues/88

Closed by https://github.com/revault/revault_net/pull/68


LSTR conversion problem

Issue Type
Bug
OS
Ubuntu
OS architecture
x86_64
Programming Language
Python
Framework
PyTorch, ONNX
Model name and Weights/Checkpoints URL
https://github.com/liuruijin17/LSTR
Description
Hello
I can't convert pytorch model to onnx model using the docker environment you provided.
When converting the model, the following logs appear. It seems to be a problem with the torch version, do you know how to solve it?
Thank you !
Relevant Log Output
user@hank:~/workdir/LSTR-main$ python test.py LSTR --testiter 500000 --modality images --image_root ./ --debug
cfg_file: ./config/LSTR.json
loading all datasets...
split: val
loading parameters at iteration: 500000
building neural network...
/usr/local/lib/python3.8/dist-packages/torch/cuda/__init__.py:122: UserWarning:
    Found GPU0 NVIDIA GeForce RTX 2080 which is of cuda capability 7.5.
    PyTorch no longer supports this GPU because it is too old.
    The minimum cuda capability supported by this library is 8.6.

  warnings.warn(old_gpu_warn % (d, name, major, minor, min_arch // 10, min_arch % 10))
/usr/local/lib/python3.8/dist-packages/torch/cuda/__init__.py:145: UserWarning:
NVIDIA GeForce RTX 2080 with CUDA capability sm_75 is not compatible with the current PyTorch installation.
The current PyTorch install supports CUDA capabilities sm_86.
If you want to use the NVIDIA GeForce RTX 2080 GPU with PyTorch, please check the instructions at https://pytorch.org/get-started/locally/

  warnings.warn(incompatible_device_warn.format(device_name, capability, " ".join(arch_list), device_name))
Total parameters: 765754
Traceback (most recent call last):
  File "test.py", line 150, in <module>
    test(testing_db,
  File "test.py", line 65, in test
    nnet = NetworkFactory()
  File "/home/user/workdir/LSTR-main/nnet/py_factory.py", line 67, in __init__
    macs, params, = profile(self.model, inputs=(input_test, input_mask), verbose=False)
  File "/home/user/.local/lib/python3.8/site-packages/thop/profile.py", line 188, in profile
    model(*inputs)
  File "/usr/local/lib/python3.8/dist-packages/torch/nn/modules/module.py", line 1129, in _call_impl
    return forward_call(*input, **kwargs)
  File "/home/user/workdir/LSTR-main/nnet/py_factory.py", line 39, in forward
    return self.module(*xs, **kwargs)
  File "/usr/local/lib/python3.8/dist-packages/torch/nn/modules/module.py", line 1129, in _call_impl
    return forward_call(*input, **kwargs)
  File "/home/user/workdir/LSTR-main/models/py_utils/kp.py", line 213, in forward
    return self._test(*xs, **kwargs)
  File "/home/user/workdir/LSTR-main/models/py_utils/kp.py", line 208, in _test
    return self._train(*xs, **kwargs)
  File "/home/user/workdir/LSTR-main/models/py_utils/kp.py", line 186, in _train
    p = self.bn1(p)  # B 16 180 320
  File "/usr/local/lib/python3.8/dist-packages/torch/nn/modules/module.py", line 1129, in _call_impl
    return forward_call(*input, **kwargs)
  File "/home/user/workdir/LSTR-main/models/py_utils/kp.py", line 53, in forward
    scale = w * (rv + eps).rsqrt()
RuntimeError: CUDA error: no kernel image is available for execution on the device
CUDA kernel errors might be asynchronously reported at some other API call,so the stacktrace below might be incorrect.
For debugging consider passing CUDA_LAUNCH_BLOCKING=1.

URL or source code for simple inference testing code
No response

As stated in the error message. Read the error message.
https://developer.nvidia.com/cuda-11-6-2-download-archive?target_os=Linux&target_arch=x86_64&Distribution=Ubuntu&target_version=20.04&target_type=deb_local


The Testspace Test Results Badges is inaccessible

Are you experiencing an issue with...
shields.io
🐞 Description
The Testspace Test Results Badges is inaccessible
🔗 Link to the badge
https://img.shields.io/testspace/tests/swellaby/swellaby/main

💡 Possible Solution
No response

Hello @henry-hub and thank you for using shields and taking the time to open an issue.
While looking at the shield link you provided I noticed you might be missing the metric path parameter, as this is a required parameter this might be the cause of your issue.
Please take a look at the docs for this shield here
Notice how the url format is https://img.shields.io/testspace/:metric/:org/:project/:space where metric should be one of the following: [total, passed, failed, skipped, errored, untested]
The log posted by the github actions bot also shows that:
 Response status code  🎯
 404
 Handled error  🙅
 NotFound: Not Found: org, project, or space not found

I also think that the project you specified, swellaby does not exist in the swellaby space. Please pick a project that exists at https://swellaby.testspace.com/ like: swellaby:testspace-sample, swellaby:rusty-hook, swellaby:nyc-config or swellaby:dotfiles
I will note that while testing this shield with the default example it worked for me in my local build but did not work on shields.io, So this might be related to an issue with the main deployment or the connection from it to testspace.com.
@chris48s Who can debug the shields.io deployment?

Hello @henry-hub and thank you for using shields and taking the time to open an issue.
I think that the project you specified, swellaby does not exist in the swellaby space. Please pick a project that exists at https://swellaby.testspace.com/ like: , , or swellaby:testspace-sample``swellaby:rusty-hook``swellaby:nyc-config``swellaby:dotfiles
The log posted by the github actions bot also shows that:
 Response status code  🎯
 404
 Handled error  🙅
 NotFound: Not Found: org, project, or space not found

I will note that while testing this shield with the default example it worked for me in my local build but did not work on shields.io, So this might be related to an issue with the main deployment or the connection from it to testspace.com. @chris48s Who can debug the shields.io deployment? Also the github workflow gets the correct response while the shields.io deployment gets inaccessible which does not seems to be right.

Thank you very much for your reply, sorry I used the wrong project, but I still have this problem when I use the existing project, like: https://img.shields.io/testspace/tests/swellaby/swellaby:testspace-sample/main

It is normal for me to try locally, is it possible that testspace.com restricts the use of the shields.io.

I am not sure as this is my first time attempting to solve an issue that might be related to the shields.io operation, I suggest we wait for someone on the team with the expiriance and access to the shields.io host.
I marked the issue with what i belive is the correct label and i already pinged one of the team members that might be able to help us solve this.

thanks

I have also been seeing this same issue recently, with previously-working badge URLs.
I think the issue is Testspace's API server refusing IPv6 connections.
When I ran the badge-cli.js script with the valid sample badge URL https://img.shields.io/testspace/tests/swellaby/swellaby:testspace-sample/main, the result in an ECONNREFUSED error.
% npm run badge "https://img.shields.io/testspace/tests/swellaby/swellaby%3Atestspace-sample/main"
 Request  🏹
 https://swellaby.testspace.com/api/projects/swellaby%3Atestspace-sample/spaces/main/results
{
  "headers": {
    "Accept": "application/json"
  }
}
 Handled error  🙅
 RequestError: connect ECONNREFUSED 2600:1f14:569:e000:d60:2c6a:8d0c:9502:443
    at ClientRequest.<anonymous> (file:///home/ben/projects/shields/node_modules/got/dist/source/core/index.js:792:107)
    at Object.onceWrapper (node:events:629:26)
    at ClientRequest.emit (node:events:526:35)
    at ClientRequest.emit (node:domain:489:12)
    at TLSSocket.socketErrorListener (node:_http_client:501:9)
    at TLSSocket.emit (node:events:514:28)
    at TLSSocket.emit (node:domain:489:12)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1495:16) {
  prettyMessage: 'inaccessible',
  cacheSeconds: undefined,
  response: undefined
}

On the same computer, I get a 200 response for this request using curl, but it needs to fall back from IPv6 to IPv4 to succeed.
% curl -v -H "Accept: application/json" "https://swellaby.testspace.com/api/projects/swellaby%3Atestspace-sample/spaces/main/results"
*   Trying [2600:1f14:569:e000:d60:2c6a:8d0c:9502]:443...
* connect to 2600:1f14:569:e000:d60:2c6a:8d0c:9502 port 443 failed: Connection refused
*   Trying <IP_ADDRESS>:443...
* Connected to swellaby.testspace.com (<IP_ADDRESS>) port 443 (#0)
...elided...
< HTTP/2 200
...elided...

If you force curl to only use IPv6 without allowing it to fall back to IPv4, you get the same connection refused error as Node.
% curl -6 -H "Accept: application/json" "https://swellaby.testspace.com/api/projects/swellaby%3Atestspace-sample/spaces/main/results"
curl: (7) Failed to connect to swellaby.testspace.com port 443 after 34 ms: Couldn't connect to server

I have no idea if this was caused by a Testspace DNS change, a Testspace operational change, a Shields.io code change, or a Shields.io operational change.

I tried to deploy shields on my server, and I can access it normally
https://badge.ihub.pub/testspace/tests/swellaby/swellaby:testspace-sample/main

This issue should be reopened because it's still broken in production:
https://img.shields.io/testspace/tests/swellaby/swellaby:testspace-sample/main

Just because you don't have IPv6 doesn't mean it's fixed for everyone else.

Yeah agreed. I can reproduce this in production and staging, but it works locally.
I haven't had a chance to confirm if it is ipv6 related or not yet. I think I'll need to spin up a review app with TRACE_SERVICES=true or set it on staging. Hopefully that will give me the logs to see what is happening. I'll try to get to this in the next couple of days.

I'll add for awareness that someone from Testspace had contacted me about heavy API volume though it was due to me being the account owner of the projects/spaces they were seeing traffic from.
Based on the information that they shared it didn't seem the concerning traffic was coming from Shields (at least based on the request headers they were seeing), but it's possible they've implemented some protective mechanisms as a result.
Will share more with the Shields maintainers offline

OK. I checked this on staging. I can confirm the error we have is also
RequestError: connect ECONNREFUSED 2600:1f14:569:e000:d60:2c6a:8d0c:9502:443

I don't know what the fix is off the top of my head, but I think we know the cause.
@Aldaviva - were you able to set your local env up to reproduce the issue? If so, any advice on doing so?

I also note that got has a convenient option to force the request's DNS lookup to use IPv4, if you want to pass that in the options attribute of _requestJson().

FYI I followed up with Testspace, and they identified and fixed the root cause. Now I am able to send HTTPS requests to Testspace domains using IPv6 only (at least in my very brief testing with curl).
I don't think anything else needs to be done with Shields.io at this point, but I just wanted to keep the folks here updated.


Automate the service catalog portfolio assignment at initial setup

In the post-deployment steps, it mentions adding the AWSAFTExecution role to the service catalog portfolio within the master account. We overlooked this step-- causing an hour or so of banging our heads against the wall before we looped back to that part in the instructions. Admittedly an RTFM error. However, is there a reason why this step cannot be done programmatically as part of the AFT deployment?
Looking at the service catalog API documentation I see that only a "ListPortfolioAccess" method is documented, however there must be something used behind the scenes at AWS when we grant this access by clicking in the console. If we could use that, it would eliminate another manual step.
Service Catalog API: https://docs.aws.amazon.com/servicecatalog/latest/dg/service-catalog-api-overview.html

Hey @rcuenotag, we're looking at improving this experience, I've gone ahead and created a backlog for this and I'll review with our team.

Hi @rcuenotag, as of AFT 1.4.0 this configuration is set automatically.
Users are no longer required to manually grant AFT roles permissions to the Service Catalog portfolio.

The documentation still says the step is mandatory though. The role doesn't even seem to exist though.


remove duplicate log statement in the proxy

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1203   +/-   ##
=======================================
  Coverage   91.05%   91.05%
=======================================
  Files         114      114
  Lines        7769     7769
=======================================
  Hits         7074     7074
  Misses        467      467
  Partials      228      228

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6ca4445...03171bc. Read the comment docs.


Proof verification failure on stZeroKnowledge2/ecmul_1-2_0_28000_80

Repro is simple: run evm_test_runner pointing to the latest version of plonky2.
Also worth mentioning that theses verification errors happen for several other test cases in the stZeroKnowledge suite, this is just a nice short one with 4 transactions.

It seems it's been addressed by a PR already merged: https://github.com/mir-protocol/plonky2/pull/1140.

@Aphoh can you confirm these tests pass with this patch applied and then close?

They pass!


Release Google.Cloud.Storage.V1 version 4.10.0

Changes in this release:
New features

Change netstandard2.1 target to netstandard2.0 (commit 82bea85)
Support object soft delete (commit ae28cb4)

Created release for Google.Cloud.Storage.V1-4.10.0