CUDA: Add overloads generated by specialization to the current dispatcher.

Adding overloads to the current dispatcher when specializing saves recreating the overload for subsequent calls to the unspecialized dispatcher that would have used the overload.
This also has the side effects of making overloads available after a call to ForAll() on a dispatcher.
This provides an alternative to the implementation in #9057, which also aimed to make overloads available after a ForAll() call, but did it by changing the way ForAll() worked and potentially increasing latency for calls on specialized dispatchers (of which there are some use cases in cuDF).
Whilst looking into this I also noticed that all the CUDA dispatcher specialize tests worked in an "unexpected" way and didn't provide a good pattern to follow for this test added in this PR, so they are all fixed up in this PR too.

gpuci run tests

gpuci run tests

The PR still works with my cuDF example for numba-inspector.

Still planning to finish this when I get a moment.

Missed this due to being on PTO, going to reopen it to keep it relevant (to get round to one day).

Created Issue https://github.com/NVIDIA/numba-cuda/issues/100 to avoid losing track of this work over there.


The Ukraine card and the nav are touching, and it doesn't look the greatest

I can't fix (you :fnafmoment:) it.

I was about to make this

just add
<br />

Use CSS margin.
On Mon, Apr 25, 2022, 7:15 PM yooit_32 @.***> wrote:

just add

—
Reply to this email directly, view it on GitHub
https://github.com/AspectOS/aspectos.github.io/issues/44#issuecomment-1109128833,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AW7ZWTOSGBBUURCGWXPRK7TVG4RQDANCNFSM5UJSAFCQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Fixed

Mistake. Fixable by #46

Has this been fixed? I'm on an issue closing spree.

Has this been fixed? I'm on an issue closing spree.

It will be when #46 is merged

Has this been fixed? I'm on an issue closing spree.

It will be when #46 is merged

In that case, i guess i'll close it.


lengthy static-file configuration value will cause unexpected results

This one got me wondering. It appears that if you add a long file extension to the static-file configuration it kind of erases the previous set values. My very long file extension is .webmanifest.
Consider this minimal example
$ goaccess --version
GoAccess - 1.5.1.
For more details visit: https://goaccess.io/
Copyright (C) 2009-2020 by Gerardo Orellana

Build configure arguments:
  --enable-utf8
  --enable-geoip=mmdb
  --with-getline
  --with-openssl

access.log
<IP_ADDRESS> - - [30/Jun/2021:11:11:38 +0000] "GET /robots.txt HTTP/1.1" 200 5066 "-" "curl/7.68.0"
<IP_ADDRESS> - - [30/Jun/2021:11:39:58 +0000] "GET /site.webmanifest HTTP/1.1" 200 5030 "-" "curl/7.68.0"

.goaccessrc
log-format COMBINED
static-file .txt
static-file .webmanifest

And I run: $ goaccess access.log
Results
site.webmanifest end up being a static request, but robots.txt does not.

Expected results
I am expecting both files to count as static requests.
In my specific case I simply renamed the file extension to .manifest along with changing the file name and log entries, and that works just fine.

Sorry for the delay on this and thanks for reporting this. This has been fixed and will be pushed out in the upcoming release to be out soon. You can always test it out by building from development and let me know how it goes on your end.
Closing this. Feel free to reopen it if needed.


Publish 5/11/2020 10:30 AM PT

Docs Build status updates of commit 154e502:
:clock10: Pending: waiting for processors (9 builds ahead of you)
:warning: Docs Build is busy, currently there are 9 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 154e502:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/windows/bitlocker/Get-BitLockerVolume.md
:white_check_mark:Succeeded

docset/windows/fileserverresourcemanager/New-FsrmStorageReport.md
:white_check_mark:Succeeded

docset/windows/netldpagent/NetLldpAgent.md
:white_check_mark:Succeeded

docset/windows/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded

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.

There is a delay with the build system

Docs Build status updates of commit 154e502:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/windows/bitlocker/Get-BitLockerVolume.md
:white_check_mark:Succeeded

docset/windows/fileserverresourcemanager/New-FsrmStorageReport.md
:white_check_mark:Succeeded

docset/windows/netldpagent/NetLldpAgent.md
:white_check_mark:Succeeded

docset/windows/netsecurity/New-NetFirewallRule.md
:white_check_mark:Succeeded

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.


Fixed issue #217

Delete Account button has been added, and is working as expected - a confirmation pop-up appears after clicking the Delete Account button, after the confirmation has been made the user account is deleted and the user is logged out. Old username can be used again to register a new account if required.

Just finished cleaning up the code and moving things as per your request. Installed eslint extension for VSCode but it only pointed out some of the stuff you mentioned in the PR change request, had to fix everything manually.

Oh just noticed eslint did in fact fix some stuff, namely it added the spaces between import brackets and swapped " for ' in certain places so that it matches with everything else.


BLD: remove support for the Bento build system.

Bento doesn't work well on Python 3, and hasn't been maintained
for the last couple of years.  Build support in SciPy was useful
until recently, but the costs have started to outweigh the benefits.
It was a good ride....
Mailing list thread about this: https://mail.python.org/pipermail/scipy-dev/2018-July/022923.html

I've done the dirty deed. Thanks Ralf.


Does not work in combination with longjohn

When used in combination with https://github.com/mattinsler/longjohn, produces no stack trace.
Extending Error object directly:
/Users/gajus/Documents/dev/gajus/mightyql/dist/index.js:86
    throw new _errors.NotFoundError();
          ^
Error: Resource not found.
    at exports.many (/Users/gajus/Documents/dev/gajus/mightyql/dist/index.js:86:11)
---------------------------------------------
    at Object.<anonymous> (/Users/gajus/Documents/dev/applaudience/showtime-api/src/bin/server.js:42:9)
    at Module._compile (module.js:571:32)
    at loader (/Users/gajus/Documents/dev/applaudience/showtime-api/node_modules/babel-register/lib/node.js:144:5)
    at Object.require.extensions.(anonymous function) [as .js] (/Users/gajus/Documents/dev/applaudience/showtime-api/node_modules/babel-register/lib/node.js:154:7)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439:3)
    at Function.Module.runMain (module.js:605:10)
    at Object.<anonymous> (/Users/gajus/Documents/dev/applaudience/showtime-api/node_modules/babel-cli/lib/_babel-node.js:154:22)
    at Module._compile (module.js:571:32)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439:3)
    at Module.runMain (module.js:605:10)

Extending es6-error:
/Users/gajus/Documents/dev/gajus/mightyql/dist/index.js:86
    throw new _errors.NotFoundError();
          ^
NotFoundError: Resource not found.
    at exports.many (/Users/gajus/Documents/dev/gajus/mightyql/dist/index.js:86:11)

This is a major bummer, because it makes it impossible to debug code that uses setTimeout, setImmediate, nextTick.

Can you provide a simple example that causes this? Using node v7.7.4, the following script gave correct-looking output (I also tried simpler cases with just setTimeout, nextTick):
require('longjohn');
const { EventEmitter } = require('events');
const ExtendableError = require('es6-error');

class NotFoundError extends ExtendableError {}

class MyEE extends EventEmitter {
  emitErr() {
    this.emit('error', new NotFoundError('not found'));
  }
}

let x = new MyEE();

function causeAnErrorSoon() {
  setTimeout(function() {
    x.emitErr();
  }, 500);
}

causeAnErrorSoon();

Output:
/Users/bjy/workspace/es6-error/test.js:9
    this.emit('error', new NotFoundError('not found'));
                       ^
NotFoundError: not found
    at MyEE.emitErr (/Users/bjy/workspace/es6-error/test.js:9:24)
    at Timeout.<anonymous> (/Users/bjy/workspace/es6-error/test.js:17:7)
    at ontimeout (timers.js:380:14)
    at tryOnTimeout (timers.js:244:5)
    at Timer.listOnTimeout (timers.js:214:5)
---------------------------------------------
    at causeAnErrorSoon (/Users/bjy/workspace/es6-error/test.js:16:3)
    at Object.<anonymous> (/Users/bjy/workspace/es6-error/test.js:21:1)
    at Module._compile (module.js:571:32)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439:3)
    at Module.runMain (module.js:605:10)
    at run (bootstrap_node.js:427:7)

I think I rushed to report this issue. There is something low level going on that I haven't managed to isolate yet. Sorry.
Closing this for now.

I think I rushed to report this issue. There is something low level going on that I haven't managed to isolate yet. Sorry.

I am not even able to get the expected stack traces with:
console.log( "new Error('test').stack", new Error('test').stack );

just before throwing the error.

No worries! Feel free to reopen if it ends up being an issue with es6-error.


Add DSTOR and NOMADS as alternative sources for NWM data loading

DSTOR URL (version specific):  https://nwcal-dstore.nwc.nws.noaa.gov/nwm2.2/(standard nwm path structure)
NOMADS URL: (not version specific):  ftp://ftpprd.ncep.noaa.gov/pub/data/nccf/com/nwm/prod/(standard nwm path structure)

Hi @kvanwerkhoven is the DSTOR link above broken?  I get a result from the NOMADS link but not the DSTOR url.

@samlamont Only NOAA staff (with VM access) have access to DSTOR - sorry, should have made that clear.  We need to set it up as an option in the same way we do for NOMADS.  But won't be able to test it for DSTOR.  Jason in ISED can test it for us once it is updated in the code and he has installed locally.


Coltoneshaw postgres13 docs

Summary
Updated docs for postgres versions across all platforms since we no longer support a version lower than postgres 10.

Thank you so much, @coltoneshaw, for these amazing docs updates! I've added @streamer45 as a technical reviewer since he and I have been recently discussing the need for these important updates.
I've noticed that most of the PostgreSQL replacements made in this PR are changing older 9.x PostgreSQL references to PostgreSQL 13. I'm wondering if, instead of referencing version 13 specifically, taking a {version} approach would be reasonable? If we were to move to a more generic approach, are there any sub-steps that would be problematic using such an approach from your perspective?

@cwarnermm - I don't disagree, maybe a version approach. It's already in the docs for ubuntu, and RHEL 8. I only added the steps where the default repo didn't seem to include postgres 10+. But we can point them to the postgres redhat link and tell what version to install. Circumventing the install steps in our guide.

My thinking is that the version agnostic approach should be preferred as long as it doesn't hinder the ability of the end user to follow and execute. So, in the case where an OS (or distribution) only has a specific version supported it makes sense to go with that as using anything else would either not work or add unnecessary complexity.

@coltoneshaw - Are you open to applying updates using a version-agnostic approach?

I definitely can update these. Just so I understand though. Let's say that the default postgres on a distro is less than 10.x, we want to just point them to the postgres docs and say "follow docs to get the latest" then follow along? Right now I just have those docs for the distros that i know have a lower version by default.

The reason I'm trying to be clear is that for:

So, in the case where an OS (or distribution) only has a specific version supported it makes sense to go with that as using anything else would either not work or add unnecessary complexity.

If this distro uses postgres 9.x they cannot use Mattermost, so we'd want to ensure they're not using that. For example, centos 7 you can do the below which is not what we want them to do since they'd have to then uninstall and upgrade.
[vagrant@localhost ~]$ sudo yum install postgresql-server postgresql-contrib
...
install stuff
...
[vagrant@localhost ~]$ psql -V
psql (PostgreSQL) 9.2.24
[vagrant@localhost ~]$

In the specific case, if https://download.postgresql.org/pub/repos/yum/reporpms/EL-7-x86_64/pgdg-redhat-repo-latest.noarch.rpm provides multiple versions then it should be fine to leave the version as a variable with a clear note that they'll need >= 10.
This is to make things simpler on our side (maintenance) of course but also leave the user with the choice (they might not always want the newest possible version).

@streamer45 - Are you open to reviewing this PR for technical accuracy?

@cwarnermm - Thanks! Let me switch some of the language to the RHEL 6 and CentOS 7 docs to be version agnostic since they use the 'latest' download.

@cwarnermm - Just fixed RHEL 6 / 7 to be version agnostic.
Looking at RHEL 8 / Ubuntu the only other way to future proof these docs would be to replace the stand install with the steps to add the postgres repo and specify a version (like rhel 6/7 or centos ). That way when the version from the OS gets outdated we don't have to many any changes. Not sure what process is more clear.

@coltoneshaw - Your updates feel like a very good step forward more generic approaches to our install documentation. @streamer45 - Do you have any additional feedback or recommendations on how to proceed with these specific updates?

@cwarnermm - Anything left on this before we can merge it?


[Meta] Establish Public OpenSearch Release Process with Supporting Documentation

OpenSearch is a fast-growing community-contributed project consisting of multiple repositories with ~600 contributors who actively participate in the day-to-day growth of the project. The OpenSearch Project team has been hosting public meetings for some time, where community members can join the meetings and actively participate in the development activities alongside the maintainers. The release activities, operations, and feature discussions, however, are primarily driven by privileged organization members with domain knowledge not fully transparent to the community. As an open source project, it is imperative that OpenSearch move towards a fully transparent release process that can be jointly owned or participated by any member of the OpenSearch Maintainer community. This includes release planning, and concrete tasks needed to build, stage, test, and release the production ready artifacts. This meta issue captures the process and howTo documents needed to enable any OpenSearch maintainer to participate in (or drive) the OpenSearch release cycle in a fully transparent way.

[ ] Document Top-Level Formal Release Process
[ ] Document communication templates for soliciting community volunteers
[ ] Document technical steps for Feature Freezing the ecosystem
[ ] Document technical steps for creating release candidates (RC)
[ ] Document technical and communication steps for integration, backwards compatibility, smoke, and performance testing the release candidate with the community
[ ] Document technical steps for staging the RC
[ ] Document technical steps for official release of the RC artifacts
[ ] Document post release activities (e.g., announcements, PR, social media)

/cc @bbarani

@nknize A lot of this exists at various degrees of thoroughness in https://github.com/opensearch-project/opensearch-build#releasing-opensearch and has been iterated upon incrementally. What are the major pieces missing?

What are the major pieces missing that are not in there? Maybe just add words?

Possibly just words? Maybe a complete refactor of this documentation to be more community friendly by way of a simple top level process that pulls the disparate pieces together in a single place, and teases it away from things like code of conduct, contributing, etc.
It needs to be simple for any community member to initiate a release. Mechanisms are missing like public communication templates for smoke testing the release such as:
###########################################################################################
Please vote for release candidate 1 for OpenSearch 2.10.0
The artifacts can be downloaded from:

OpenSearch - Build 7771 (Note: Windows version does not have performance analyzer plugin)

arm64 [manifest] [tar] [rpm][deb]
x64 [manifest] [tar] [rpm] [deb] [windows]

OpenSearch Dashboards - Build 6100

arm64 [manifest] [tar][rpm][deb]
x64 [manifest] [tar][rpm] [deb] [windows]

You can execute the tests directly using the below command:
Testing the Distribution
Tests the OpenSearch distribution, including integration, backwards-compatibility and performance tests.
./test.sh
More info on testing the distribution: https://github.com/opensearch-project/opensearch-build/blob/main/README.md#testing-the-distribution
The vote will be open until next Monday, i.e. until 2023-05-23 11:00 UTC.
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)
###########################################################################################
I think we should have a good single RELEASE_PROCESS.md for formalizing just the release process, something like:

Release cycle overview

"OpenSearch currently releases major, minor and patch versions on a regular cadence as explained in the release page. The infrastructure to automatically build, test and release artifacts are available at https://build.ci.opensearch.org/."

Roles and Responsibilities

Release Manager - blah
Repository Manager - blah
Maintainers - blah
Project Management Committee - blah

Release Process

Here are the steps involved in the OpenSearch Release Process:

Preparation
Release branch readiness
Code complete / feature freeze
Release Candidate (RC) creation
Integration, BWC, Smoke and Performance Testing
Staging the RC
Releasing the Candidate
Post Release Activities

Documentation (How To Guides, Announcement Templates)
* Communication Template for Requesting Release Manager and Repository Volunteers
* Feature Freeze Process
* RC Creation Steps
* Testing Steps and Communication Templates
* Staging Release Candidate
* Releasing and Post Release Activities

On-boarding a new plugin shouldn't be in the release process doc. It should be a separate process that documents the governance around how the project maintainers (maybe future PMC) collectively decide (e.g., vote?) to include a new plugin into the "ecosystem".

@bbarani do you want to open a PR for the top level RELEASE_PROCESS.md?
The follow on PRs may not need to be individual .md files for the "Documentation" maybe they're just links to existing MD files that make it easier for the community to grok.

@nknize @dblock I will open a PR for RELEASE_PROCESS.md as mentioned in this comment soon.

Opened a RFC along with PR with the steps to document the release cycle process for OpenSearch releases.


Add optional debugger logging

This will help us track down race various debugging oddities that people are running into.

Could you give more information about areas where debugger logging could be added?

Sure thing! Turns out we already log all the info we need when the debugger is attached (it all passes through AD7Engine.DebugWriteLine)
https://github.com/Microsoft/nodejstools/blob/master/Nodejs/Product/Nodejs/Debugger/DebugEngine/AD7Engine.cs#L1293
So it would be helpful to be able to optionally save this out to a log file rather than it only being available when a debugger is attached. That way when people run into an issue, we can ask them to turn on logging, and when they send it to us, we can just do a diff their machine's output with what what we might expect it to be.


Payload is empty on the FULFILLED action and it shouldn't

Problem
The FULFILLED action (I call it SUCCESS) doesn't send any data in the payload. I'm using axios and normalize to flat my responses. I created a function called fetchData in my api folder, so when I call the fetchOrders action it should run this function, but instead when I get the SUCCESS action, the payload doesn't exist. What can be wrong? Should I define another parameter in the payload? The code example is bellow
Version Number
Redux promise middleware v4.2.0
Axios v0.15.0
Normalizr v3.0.2
Code Example
api.js
import axios from 'axios';
import { normalize } from 'normalizr';
import { camelizeKeys } from 'humps';

const API_ROOT = 'http://localhost:3000/api';

export const fetchData = (endpoint, schema) => {
  const fullUrl = (endpoint.indexOf(API_ROOT) === -1) ? API_ROOT + endpoint : endpoint;

  return axios.get(fullUrl)
    .then(response => {
        if (!response.data.success) {
          return Promise.reject(response.data);
        }
        const camelizedJson = camelizeKeys(response.data.data);
        const lastFecth = Date.now();
        return Promise.resolve(Object.assign({},
          normalize(camelizedJson, schema),
          { lastFecth }
        ));
      }
    );
}

order.js: file with orders actions
import * as api from '../api';
import * as Schemas from '../api/schema';
import { addEntity, updateError } from './';

// ... other actions

export const FETCH_ORDERS = 'FETCH_ORDERS';

const fetchOrders = ()=>(dispatch)=>(dispatch({
	type: FETCH_ORDERS,
	payload: {
			promise: api.fetchData('/orders',Schemas.ORDER)
				.then((response)=>(dispatch,action)=>{
				dispatch(addEntity(response.entities));
				})
				.catch((error)=>(updateError(error)))
			}
}));

Expected Behavior
When I call FETCH_ORDERS action, it should call the API using the api.fetchData function. This returns a promise with the data in it. If it successful it should update the state, otherwise it should catch the error.
Actual Behavior
The action fulfilled is reached but without payload, the reducer sends an error because of it and the catch of the promise is fired

The action fulfilled is reached but without payload...

I have not used Axios before, but it is a promised based library, meaning it will return a promise. You don't need to call Promise.reject and Promise.resolve, like you are now. That just creates another layer of abstraction where one promise is returning a second promise. This is likely why the fulfilled action is dispatched but without a payload.
export const fetchData = (endpoint, schema) => {
  const fullUrl = (endpoint.indexOf(API_ROOT) === -1) ? API_ROOT + endpoint : endpoint;

  return axios.get(fullUrl)
    .then(response => {
        if (!response.data.success) {
          throw response.data;
        }

        const camelizedJson = camelizeKeys(response.data.data);

        const lastFecth = Date.now();

        return Object.assign({},
          normalize(camelizedJson, schema),
          { lastFecth }
        );
      }
    );
}

Try making this change and let me know if that resolves your issue.

Thanks @pburtchaell ! That recommendation works really well.
Also I delete the dispatch(addEntity(response.entities));  in then and change the reducer to add an entity according to action payload.


scrape-a-grave not working (2023)

Attempted running scrape-a-grave without making any modifications to the code. It is unable to scrape any of the 9 test URL's in input.txt
Error: <class 'urllib.error.HTTPError'>
Successfully parsed 0 of 9
In debugging the code I discovered that the site is now blocking site scrapping code. This is what returns:

  Access denied

  Error code

   1020

  You do not have access to www.findagrave.com.

  The site owner may have set restrictions that prevent you from accessing the site.

I have a working scraper, but not sure if it's a good idea to post it publicly.   email me at my username at gmail

I have the same issue, the scraper is not working anymore and it is a little bit annoying. But what annoys me even more is that I can't download my full data (data entered by me) from findagrave.com website, although the website gives such an option. Everything that I get after downloading my data from fingagrave.com is just a URL with grave ID, and the date when the data was entered and nothing more, and that sucks. I even can't get all the attribute information (Full name, date of birth, place of birth, date of death, place of death, etc.) that was created by me. Can anyone fix this scraper so that this thing works again?


Check renewal

Hi,
Thanks, your tutorial worked like a charm on GKE !
However, in the section "Get a certificate for your domain" , I didn't get the
"Normal   RenewalScheduled      Certificate scheduled for renewal in 1438 hours" line (see [1]).
How to check if my certificates will be renewed as expected  ?
Thanks
Events:
  Type    Reason          Age   From          Message
  ----    ------          ----  ----          -------
  Normal  CreateOrder     44m   cert-manager  Created new ACME order, attempting validation...
  Normal  DomainVerified  37m   cert-manager  Domain "dogs.test.florat.net" verified with "http-01" validation
  Normal  IssueCert       37m   cert-manager  Issuing certificate...
  Normal  CertObtained    37m   cert-manager  Obtained certificate from ACME server
  Normal  CertIssued      37m   cert-manager  Certificate issued successfully

I found the answer [1] , see also https://github.com/jetstack/cert-manager/issues/773
:
kubectl logs -n kube-system -l app=cert-manager -c cert-manager
I1011 09:34:41.167077       1 helpers.go:201] Found status change for Certificate "dogs-com-tls" condition "Ready": "False" -> "True"; setting lastTransitionTime to 2018-10-11 09:34:41.16707078 +0000 UTC m=+3827.273067415
I1011 09:34:41.167397       1 sync.go:206] Certificate default/dogs-com-tls scheduled for renewal in 1438 hours


Take another look at output_yaml argument

I'm putting this in an issue because it probably should be addressed but things are working and I don't have the energy to dive into anything else regarding #171 right now.
The output_yaml argument is not working. @carriewright11 mentions it might absolutely need to be called _output.yml which seems like a silly thing but might very well be the case.
Later if I figure out how to fix this better, we can get rid of lines 53 - 58 in render_coursera.R
Originally posted by @cansavvy in https://github.com/jhudsl/DaSL_Course_Template_Bookdown/pull/177#r703676198

This is taken care of.


page link returns error

Description
Link from "loss collection" on page https://nixtlaverse.nixtla.io/neuralforecast/models.nbeats.html
does not work
Link
https://nixtlaverse.nixtla.io/neuralforecast/losses.pytorch.html

Thanks for reporting - it also doesn't work when I try it.
We'll make a few doc fixes.


Payload format v2

publisher and subscriber should support only v2 payloads
new payload format should have these new fields:

magic number at the start
source TTL
sequence length (already contains the iteration counter)

Full v2 payload (128 bytes):

Field
Size in bytes
Comment

Magic number
4
ASCII character values for "mbit"

Format version
1
value 2

Source TTL
1

Multicast port
2

Multicast address
4

Time of departure
4
nanoseconds part

Time of departure
8
seconds from epoch

Sequence iteration counter
8

Sequence length
8

Session ID
8

Interface name
16
not terminated with NUL

Hostname
64
not terminated with NUL

all integers are unsigned and stored in the network byte-order
all strings are fixed-length and padded with NUL bytes

done in e0640fe


Add support for MappedTypes and MappedJdbcTypes

It is very useful to have MappedTypes if you work at all with UUIDs. This could be added I think in a simlar way to how Mappers work now - look for any class with an annotation of MappedTypes (or MappedJdbcTypes) and then add them to the configuration.
I'd be more than happy to try and take a first pass at it if someone would point me in the right direction.
Thanks!

Thanks @kbrumer and please go ahead to try scanning the MappedTypes annnotation by using CombinedIndexBuildItem just like we do with Mapper in MyBatisProcessor::addMyBatisMappers(...)

And I think it could be helpful to add some unit tests.

@zhfeng My PR (the second one) is complete with a unit test. Please let me know if you have any questions or comments. Thanks!

Thanks @kbrumer and it could be better to add a similar one to the integration-tests and run the tests in the native mode. And I will merge your PR and leave this in a new issue.


Support PHP 8 and its new features

This list is based on https://github.com/phpactor/phpactor/issues/1135
Package Support
Ensuring that all packages support 8.0 and phpat can be composer-installed in a PHP 8.0 environment
Language Support
Constructor promotion
class CustomerDTO
{
    public function __construct(
        public Email $email,
        public DateTimeImmutable $birth_date,
    ) {}
}

Named Parameters
$data = new CustomerData(
    email: new<EMAIL_ADDRESS>);

Union Types
Currently supported in docblocks
class Example {
    private int|float $foo;
    public function squareAndAdd(float|int $bar): int|float {
        return $bar ** 2 + $foo;
    }
}

$class is instanceof Foo|Bar

Attributes
First step: Ensure they do not break Method Arguments, Class Properties, Closures, Anonymous Classes...
Second step: Recognise declared classes as dependencies
info: https://php.watch/articles/php-attributes
Match and Throw Expression
match ($class) {
    $class instanceof Foo => 'one',
    $class instanceof Bar => 'bar',
    default throw new Exception('asd');
}

There are currently a couple of things standing in the way of PHP8 support:

carlosas/simple-event-dispatcher`

https://github.com/carlosas/simple-event-dispatcher/pull/1 should resolve that

roave/better-reflections

See also: https://github.com/Roave/BetterReflection/issues/701

There are currently a couple of things standing in the way of PHP8 support:

carlosas/simple-event-dispatcher`

https://github.com/carlosas/simple-event-dispatcher/pull/1 should resolve that

roave/better-reflections

See also: https://github.com/Roave/BetterReflection/issues/701

Hi @carlosas any updates on this topic? Is support for php8 coming soon?

Hello @Lukasz93P
I'm doing some work in a dev branch to support PHP 8.0, but it will still not catch some new features (so it might not find relations on, for instance, union types) or the execution might even fail. I'm going to continue working on the support so hopefully I will release it soon-ish.
Right now you can test the progress using the version v0.8.x-dev

I have created some tests and with the recent changes the current support in v0.8.x-dev is:
Package Support :white_check_mark:
Constructor promotion :white_check_mark:
Named Parameters :white_check_mark:
Union Types :white_check_mark:
Attributes :x:
Match and Throw Expression :white_check_mark:

@carlosas  "it will still not catch some new features", ok it sounds great despite that, I will be very happy being able to install this package with php version specified as 8 in my composer file, thats all, so thanks for answering my question.

Released https://github.com/carlosas/phpat/releases/tag/0.8.0


Eslint cannot format document that are too deep in the filetree ...

Took me a while to reproduce the issue. The plugin cannot accept file that are deeper than 6 directories ...
I have a document under packages/ask-generic-react/src/theme/storybook/text/index.stories.tsx -> if I try to format it with eslint using the command Format or in autosave, I get a error message in the taskbar "Cannot format document ...."
If I move the same file, one level upper in the filetree: packages/ask-generic-react/src/theme/storybook/index.stories.tsx, the formater works ...
I'm running VSCode on ubuntu linux.

Works for me.

Can you please provide me with a GitHub repository I can clone that demos what you are experiencing.

Sorry I can't with my actual repo, it's a company private one.

Can you distill something?


deployment lifecycle: deleting

Typically the lifecycle of a VNF is as follows:
create bigips  -> setup cluster -> deploy applications -> sync -> delete applications -> delete sync -> delete cluster -> delete bigips
Note: I'm not taking into account scale-in/scale-out which I mention in https://github.com/F5Networks/f5-openstack-heat/issues/126
This is typically deployed using a single heat template.
When the delete operation is triggered on the Heat template the applications are deleted and therefore the bigips get out of sync. This makes fail deleting the template because currently F5::Cm::Cluster requires the pair to be in sync before removing the F5::Cm::Cluster resource type.
I can see two options to solve this issue:

on F5::Cm::Sync deletion the synchronization is triggered again.
Allow F5::Cm::Cluster to have the option to allow not requiring the units being in sync. Btw, F5::Cm::Cluster doesn't require the bigips to be previously in sync to be created... so why requiring this state on deletion?

Maybe we could implement both as options so the user chooses his desired behavior and we don't anticipate all use cases.

This is tightly bound to the aggressive teardown issue in the sdk. This would have to be 'best effort', since we cannot guarantee the final state of the devices if the starting state of the cluster is not known (meaning a user went into the cluster and manually manipulated the members). This work would take around a week as well. It is mostly work in the sdk.

The thing we should be able to ensure is that the cluster stack will be removed from the database.

Note: I have updated the issue description to hopefully better describe it

I find that only changing the F5::Cm::Cluster behavior would not suffice to match orchestrator's expected behavior of a VNF because of the need of deleting resources when deploying and create new resources when deleting.
Following NFV model the lifecycle should be

VNFD would be a Heat Template that creates a shared VNF used by several NSD (Network Service Descriptors)

[deployment start]
create bigips  -> setup cluster
[deployment completed]

The deletion of the VNF would be just undoing the created resources.

A NSD would be just

[deploy service]
deploy configuration in cluster
[deploy service completed]

Again, the deletion of the NS would just be undoing the created resources.
I wonder if the following could be a good approach:

F5::Cm::Cluster to have an attribute that would allow auto-sync between the F5's in the cluster
Deploying services would would be done to a F5::Cm::Cluster target instead of a F5::BigIP::Device as it is currently only allowed.

This would allow:

By having the cluster automatically in sync would avoid F5::Cm::Cluster failures when deleting this resource unless something is really wrong.
By allowing deploying config resources types to a cluster allows to do not depend if a given BIG-IP unit is available or not: the config will be copied to one of the units that are available and eventually automatically sync'ed.

Also note that these two together would allow the lifecycle that orchestrators expect.
The caveat I find is that currently the LBaaS agent does not work with config sync and instead it replicates the configuration to all the F5 nodes.


Add machine class to the Cluster API

This issue tracks discussion on adding machine class (as used/suggested in several API discussions) and any work required to make that happen if we decide to do it.

Assigning to @roberthbailey to drive discussion and decision.

This issue was moved to kubernetes-sigs/cluster-api#22


useIsKeyPressed hook

Feature Description
See https://github.com/google/web-stories-wp/pull/886#discussion_r400606709 . Minor refactor for the keyboard handling allowing for a shortcut hook to determine whether a key is currently being pressed.

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria
QA Instructions

@dvoytenko
An easy fix for this is to do the following:
keyboard/index.js >
export function useIsKeyPressed(targetKey, deps = undefined) {
  const [isKeyPressed, setIsKeyPressed] = useState(false);
  useGlobalKeyDownEffect(targetKey, () => setIsKeyPressed(true), deps);
  useGlobalKeyUpEffect(targetKey, () => setIsKeyPressed(false), deps);
  return isKeyPressed;
}

multiSelectionMovable.js >
  const canSnap = !useIsKeyPressed('meta');
  const throttleRotation = useIsKeyPressed('shift');

However talking to @barklund I realised that @dvoytenko has some ideas on using a single global provider that remembers all states of all relevant keys.
Pinging @dvoytenko, do you think its worth it for me to fix this issue with the solution provided above, or should we just mark this obselete and then create a new issue for a single global provider.

Yeah. Looks good to me. Just a minor nit. Let's make a pair: useIsKeyPressed(ref, keyNameOrSpec) and useGlobalIsKeyPressed(keyNameOrSpec).


font size

Can I change the font size of the button?
I think the large button is not big enough.

The large size button matches the height and font-size of the buttons you see on any GitHub repository page. There is no plan to make font-size customizable.


Targets

The must specify --input and --output when using rollup --watch message appears when using targets, because there's no options.dest

Actually this was an issue in Rollup itself. Closing


SAKIII-4269 don't display welcome message for anon

https://jira.sakaiproject.org/browse/SAKIII-4269

Verified and merged.


Power on from Home-Assistant

Is your feature request related to a problem? Please describe.
I am using the intrgration with the DMP-A8.
It works nice - and i primarily use it to turn on my Mono amps - when the amp is powered on.
Describe the solution you'd like
Could it somehow be possible to turn the unit on from the Mediaplayer?
I now i can use WOL - but why not build it into the mediaplayer?
Describe alternatives you've considered
WOL switch :)
Additional context
Not much more than that.

Hi @hostrup,
I tried implementing that but didn't manage to do so. The API used in this integration is entirely unavailable when the device is turned off.
Does the Eversolo app offer this feature? If so, we can find out how they do it
I use the setting to turn on the device when the power is back on. I have some automations that turn power on and turn off the Eversolo and afterwards the power. Maybe you can use the available/unavailable info from the media player to turn other devices on/off.
Chris

Hi Chris!
Yes i saw that the API seems totally unavailable when the device is in standby.
But i found out that simply by sending a wake-on-lan packet to the IP - will wake i up.
So i created a WOL sensor i HA - that i can use to turn it on.

Sorry for replying late. So the behavior that you'd like to see is that the integrations sends a magic packet when pressing the turn on button, right?

Hi! i just created a simple switch - and that works nice. i think i might look into creating a new mediaplayer as a template - and then use that switch as on / off - then i can use the "player control" to turn it on and off.
Everything else works wonders.

Closing because WOL power on won't be implemented for now.


Rename to tolerance for perc diff and put into actions

Put the percent chance of each action taken on the selector and change the name to tolerance

Make sure to sort by priority

also need to move this to pipeline constants


Add logic to deal with <IP_ADDRESS>/0 which ipset not support.

fix: repair <IP_ADDRESS>/0 cidr which ipset not support
Reason for Change:
Ipset doesn't support <IP_ADDRESS>/0 cidr. A general approach is convert it to <IP_ADDRESS>/1 and <IP_ADDRESS>/1

fix: Bug Fixes 🐞

Can we add a test to validate this scenario?

Can we add a test to validate this scenario?

Let me figure out a unit test.

Interesting solution, approved


Standardize queue names

This is really risky, as many other services use the current queue names, so it should be marked as breaking changes and anyone using it should ensure to update their queue names in custom microservices to avoid possible issues.
Queue names right now do not follow any standard, and due to that, if we create an operator with name membersSignup, eventName members.signup and route created, you'll have the following queues created in your rabbit instance:

sbo-ms.members.signup.dead-letter.created
sbo-ms.membersSignup.members.signup.created

Dead letters came after default queues, so I guess the ones having the incorrect name are dead-letter ones, but I'm not sure. @gtrias sorry to bother you with this, but what you think? Which queue names are better?
Changing the dead-letter queues would be easier, as we're not (at least us..) listening to that queues except from switchboard operator, so changing them wouldn't be pain. Can't say the same for the default queue names.

Addressed in version 2.0.0

@elboletaire ei mira @Ander161 addressed


Any ideas of this table overflow error?

Not sure anyone see this before:
Error executing vim.schedule lua callback: table overflow
stack traceback:
        [C]: in function 'insert'
        ...e/pack/packer/opt/windline.nvim/lua/wlfloatline/init.lua:95: in function 'render_comp'
        ...e/pack/packer/opt/windline.nvim/lua/wlfloatline/init.lua:121: in function 'render_float_status'
        ...e/pack/packer/opt/windline.nvim/lua/wlfloatline/init.lua:196: in function 'tick'
        ...k/packer/opt/windline.nvim/lua/wlanimation/animation.lua:82: in function ''

It is the first time I saw this.
If comp.text() function through an error, will this happen? Some time I saw this error:
Error executing vim.schedule lua callback: ...ker/opt/nvim-treesitter/lua/nvim-treesitter/ts_utils.lua:23: bad argument #1 to 'sub' (string expected, got nil)
stack traceback:
	[C]: in function 'sub'
	...ker/opt/nvim-treesitter/lua/nvim-treesitter/ts_utils.lua:23: in function 'get_node_text'
	.../pack/packer/opt/nvim-treesitter/lua/nvim-treesitter.lua:40: in function 'get_line_for_node'
	.../pack/packer/opt/nvim-treesitter/lua/nvim-treesitter.lua:72: in function 'statusline'
	~/.config/nvim/lua/modules/ui/eviline.lua:83: in function 'current_treesitter_context'
	~/.config/nvim/lua/modules/ui/eviline.lua:105: in function 'current_function'
	~/.config/nvim/lua/modules/ui/eviline.lua:344: in function 'text'
	...e/pack/packer/opt/windline.nvim/lua/wlfloatline/init.lua:76: in function 'render_comp'
	...e/pack/packer/opt/windline.nvim/lua/wlfloatline/init.lua:114: in function 'render_float_status'
	...e/pack/packer/opt/windline.nvim/lua/wlfloatline/init.lua:179: in function 'tick'
	...k/packer/opt/windline.nvim/lua/wlanimation/animation.lua:82: in function ''
	vim.lua: in function <vim.lua:0>⏎

Not sure if those two related.

can you share your config and WindLineBenchmark result

This issue is not easy to reproduce. And I am not sure if it caused by windline or other plugins that corrupt the memory.
My windlineBenchmark:
Status:
%#WLred_black#▊  %#WLmagenta_NormalBg#  master%#WLNormalFg_NormalBg#29.91k %#WLmagenta_NormalBg#elastic_search_query_executor.go  %#WLred_NormalBg#  0%#WLyellow_b_NormalBg#  24%#WLblue_NormalBg#  0%#WLNormalFg_NormalBg# %#WLgreen_light_NormalBg#🐼%#WLNormalFg_NormalBg#  %#WLgreen_b_NormalBg#  func (esqe *ElasicSearchQueryExecutor) ExecuteCombinedSegmentsCou%#WLNormalFg_NormalBg# %= %3l:%-2c %3p%% %#WLblue_NormalBg#▃▃%#WLmagenta_NormalBg# null-ls|gopls %#WLgreen_NormalBg# 0%#WLred_NormalBg#  0%#WLblue_NormalBg# 柳0%#WLNormalFg_NormalBg# %#WLblue_NormalBg# inte/doma/execr%#WLNormalFg_NormalBg#  %#WLred_black#▊
Time:
render 10000 time : *1.65144345*
Comp:
          time         name num    text
01 *0.030331802*              10000 - %#WLred_black#▊
03 *0.03400991*      vi_mode 10000 - %#WLred_black# 
04 *0.004638201*              10000 - %#WLmagenta_NormalBg#  master
05 *0.024150287*         file 10000 - %#WLNormalFg_NormalBg#29.91k %#WLmagenta_NormalBg#elastic_search_query_executor.go
06 *0.01601366*   diagnostic 10000 - %#WLred_NormalBg#  0%#WLyellow_b_NormalBg#  0%#WLblue_NormalBg#  0
07 *0.005702096*    signature 10000 - %#WLNormalFg_NormalBg# %#WLgreen_light_NormalBg#🐼%#WLNormalFg_NormalBg#
08 *0.449944048*     funcname 10000 - %#WLNormalFg_NormalBg# %#WLgreen_b_NormalBg#  func (esqe *ElasicSearchQueryExecutor) ExecuteCombinedSegmentsCou%#WLNormalFg_NormalBg#
09 * 0.0015075*              10000 - %=
10 *0.00315237*              10000 - %#WLNormalFg_NormalBg# %3l:%-2c
11 * 0.0198207*              10000 - %3p%% %#WLblue_NormalBg#▃▃
12 *0.002764212*              10000 - %#WLmagenta_NormalBg# null-ls|gopls
13 *0.039128698*          git 10000 -  %#WLgreen_NormalBg# 0%#WLred_NormalBg#  0%#WLblue_NormalBg# 柳0
14 *0.430337154*       folder 10000 - %#WLNormalFg_NormalBg# %#WLblue_NormalBg# inte/doma/execr%#WLNormalFg_NormalBg#
15 *0.010041936*              10000 - %#WLNormalFg_NormalBg#
16 *0.031752759*              10000 - %#WLred_black#▊

My setup:
https://github.com/ray-x/nvim/blob/master/lua/modules/ui/eviline.lua
And this:
https://github.com/ray-x/nvim/blob/647175967b8ecd34758620cbae7cdd5408320421/lua/core/lazy.lua#L185-L187
I am adding more logs to both nvim-treesitter and windline to see what was going on and hope I can bring more info.

you can use cache component on component "folder" so it don't calculate everytime status draw.
https://github.com/ray-x/nvim/blob/master/lua/modules/ui/eviline.lua#L319.
https://github.com/windwp/windline.nvim/wiki/component#cache-value-on-buffer
and move require to outside of text function because require on impatient do a lot of thing
https://github.com/ray-x/nvim/blob/master/lua/modules/ui/eviline.lua#L85.
maybe it improve performance a bit but i am not sure it is fixed your issue.
it fix another strange issue  #24  so you can try.

I am dumping logs here:
      if text and text ~= "" then
        if #state.text_groups > 100 then
          lprint(state.text_groups)
        end
        table.insert(state.text_groups, {
          text = text:gsub("%%%%", "%%"),
          hl = comp:make_hl(hl, hl_data.default),
        })
      end

Please refer to the log.
You can see state.text_groups is growing over the period
error_Head.log
I can see the plugin will reset it to {}. But for some reason, it did not reset and keep growing until it overflow.

My theory is one of the components was blocked and failed to response in 300ms tick. This makes the request piled up and blow off the stack.

interesting. how do you reproduce it :)

I have about 10 nvim instances opened. And each one may open a git repo/project( lua, go, javascript etc). I leave them alone and only check back every 1 hour or two. And after ~3 hours, one instance crash with the overflow error.

can you try to use branch thread.

I am using thread branch now. Will keep you posted.

I am afraid it was not fixed
I log the items and state here:
local function render_float_status(bufnr, winid, items)
  state.comp = {}
  state.mode = mode()
  Comp.reset()
  local total_width = vim.o.columns
  local status = ""
  local cur_position = 0
  state.text_groups = {}
  state.thread_id = state.thread_id + 1
  for _, comp in pairs(items) do
    if #state.text_groups > 50 and #state.text_groups < 200 then
      lprint(items, state)
    end
 ...

And the log is attached:
windline.log
From the logs I can see text_groups has duplicate items and it is growing after a few hours.
Maybe we should either add a mutex to text_groups. Or use map instead of array. Or maybe pass it through instead of use it as a global object.

it already a global object.
lua print(vim.inspect(WindLine.state.text_groups)

{
      hl = "WLred_black",
      text = "▊"
    }, {
      hl = "WLred_black",
      text = "  "
    }, {
      hl = "WLmagenta_NormalBg",
      text = "  master"
    }, {
      hl = "WLNormalFg_NormalBg",
      text = "5.06k"
    }, {
      hl = "",
      text = " "
    }, {
      hl = "WLmagenta_NormalBg",
      text = "SegmentContext.js "
    }, {
      hl = "",
      text = " "
    }, {
      hl = "WLred_black",
      text = "▊"
    }, {
      hl = "WLred_black",
      text = "  "
    }, {
      hl = "WLmagenta_NormalBg",
      text = "  master"
    }, {
      hl = "WLNormalFg_NormalBg",
      text = "5.06k"
    }, {
      hl = "",
      text = " "
    }, {
      hl = "WLmagenta_NormalBg",
      text = "SegmentContext.js "
    }, {
      hl = "",
      text = " "
    }, {
      hl = "WLred_black",
      text = "▊"
    }, {
      hl = "WLred_black",
      text = "  "
    }, {
      hl = "WLmagenta_NormalBg",
      text = "  master"
    }, {
      hl = "WLNormalFg_NormalBg",
      text = "5.06k"
    }, {

i think it happen on diagnostic component. after the file name component
{
      hl = "WLmagenta_NormalBg",
      text = "SegmentContext.js "
    },
``
 it can continue to display another component.

Both of which is from lsp. The position/file does not have either diagnostic info nor lsp signature. So it is ok for those fields to be empty.

I try to lock thread_id on a tick function and add reset text_group when it  have different thread_id. maybe it work

Sure, I will give it another try. Thanks!

@ray-x  i disable update floatline when nvim lost focus.

In fact, in yesterday's version, I can still see the text_groups growing, but it stopped at 60 instead of going all the way to blow off table length limitation.
I will try your new version and see how it works.

I am still seeing the same thing today. No overflow, but text_groups size can grow over 50.

it still happen on inactive time?

It happened when I re-enter the inactive nvim instance this time.

it happen on inactive time and after display diagnostic component
so think it similar to that
https://github.com/nvim-lualine/lualine.nvim/issues/462
https://github.com/neovim/neovim/issues/16501
are you use mac ? maybe it have a problem with lua on mac to restore memory.

I still merge that to save some CPU power on inactive time :).
but i think it is a problem on upstream

Yes. I agree it might be related. I am using MacOS.
It annoyed me earlier because when table overflow, the nvim instance was frozen and used lots of memory (>8G virtual memory) and I have to kill it manually.
So far that issue does not happen. You can mark it as upstream and close the issue.
Thanks for your help.

ok i merge it to master

Verified on master.


Wrap all plugin imports in require.resolve()

Motivation
(Write your motivation here.)
As per the breaking change in 2.0.0-alpha56 plugin call need to be wrapped in require.resolve(...). Add this to the examples.
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work. Bonus points for screenshots and videos!)
Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/facebook/docusaurus, and link to your PR here.)

Thanks @TomBrien
Do you mind updating as well the /docs folder? otherwise on next release your docs changes will be reverted. The versioned_docs folder is for already released versions, and will not be used for next releases.

My bad just hit the edit on GitHub button. Sure will move that over now

I think this only serves as a workaround due to a bug in the current version, and will not be necessary after we release the next alpha version is that right?. cc @SamChou19815

Yes, but I think it makes sense to make the change only in alpha-56 versioned docs.

Will revert the second commit :)

Thank you very much @TomBrien!


Run metadata tests with -H:+ThrowMissingRegistrationErrors.

To allow for a better user experience in Native Image, we are currently working on -H:+ThrowMissingRegistrationErrors. We eventually want to turn it on by default. Before that can happen, we need to run the metadata tests in this repo with the flag. This will also allow the Spring team to test out the new mode.

Does resolving the current issue mean providing GraalVM Reachability Metadata for Junit first? I will say that I was surprised to see in https://github.com/apache/shardingsphere/pull/33179 that -H:ThrowMissingRegistrationErrors= causes exceptions related to org.junit.** to be thrown.

Yes, we need to fix JUnit support first.


fix fragment index bug, resolves #376

ping @idning

@manjuraj

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

This was fixed in the same way(ncontinuum->nserver) in #595 (when I was looking into a segmentation fault for memcached gets that had the same root cause and the same findings - https://github.com/twitter/twemproxy/issues/563#issuecomment-784613830) - I hadn't seen your PR prior to merging that and had only been added as an external collaborator 2 days ago.


Create script for starting Fluo clusters in Amazon EC2

It would be helpful if Fluo had a script for starting a Fluo cluster in Amazon Web Services.  This 'fluo-ec2' script could be written in python and utilize the boto library for interacting with AWS.  It could start up pre-built AWS images (AMIs) containing all software needed to run a certain version of Fluo.
When creating this script, it may help to reference the spark-ec2 script (docs, code).  Also, the fluo-ec2 script could live in its own repo.
Eventually, the Fluo AMI could include Graphite and the 'fluo-ec2' script could configure Fluo containers to send to it.

Issue can be closed with completion of fluo-deploy script


Refactor cam control

This changes the semantics of the connection between a camerapath and a layer slightly.
The old format matched camerapaths in camerapaths.json with corresponding layers in layers.json by their index in the list. This made it difficult to actually keep a camerapath connected to the proper
layer.
A full rework of the system (diffent camerapaths in different files or something similar) might be best, but that's too much work to be completed before solskogen 2015.
The old format meant that a camerapath was linked to an instance of the layer, i.e. two different instances of the layer could (and would) have different camerapaths. With the new system, the camerapath is instead linked to the 'type' of the layer, as camerapaths.json is no longer a list, but a dictionary where the layer type is the key for each dictionary.
This should make it easier to manage the relation between layers and camerapaths, and I doubt the possibility of using different camerapaths for different instances of the same layer will be missed.

Oops, spotted a mistake in example-project. will fix

Ping

I tweaked the format a bit further, will test that all of it works properly before this should be merged.

I tweaked the format a bit further, will test that all of it works properly before this should be merged.

Was this tested?

Nope.

I did test it quite a bit more after I commented. Shouldn't be more broken than the previous version


Improve Indicator Table

closes #1055
Prerequisites:

[x] Unless it is a hotfix it should be merged against the dev branch
[x] Branch is up-to-date with the branch to be merged with, i.e. dev
[x] Build is successful
[x] Code is cleaned up and formatted

Summary

Minor nit: can we make N/A and unit-less values align with the right edge of values instead of the right edge of units?

-->

how about that:


Drawing order different to map info order

Mapsui Version
Main
Mapsui Platform
WPF
Device
Windows 10
Describe the bug
If you add PointFeatures to a MemoryLayer one after one, they are drawn in wrong order. The last added will be drawn last, the first added will be drawn first. The problem is, that the map info works the other way. The function is checking the last added first and the first added last. That is no problem until the features overlap. If this is the case, the feature later added is drawn below the earlier added, but gets the map info event earlier.
To Reproduce
See video below
Expected behavior
Drawing and touching should be consistent. I'm not sure, what is the idea behind drawing in this case. Should the first added feature be drawn first (as expected by touching) or should it be drawn last (then we have to change touching order).
Screenshots
I added a video showing the problem:
https://github.com/Mapsui/Mapsui/assets/4381223/3b7e3360-3f49-4351-9d7d-25f9bf5435be

One info I missed in the description of the video is the order of adding the markers to the map. I added first the @ marker, then the A marker and so on. Z marker was the last added one.

Looked into this problem. Seems in conjunction with ConcurrentBag, which isn't an ordered list. This shouldn't be used here, because when features overlap, it isn't possible to say, which is the upper and which is the lower.
That said, we have to find something else as list for MemoryLayer.

Is this issue now fixed with the id sorting fix, or is there something else to fix? We could have a more general discussion about how to determine the order but lets have that here: https://github.com/Mapsui/Mapsui/issues/2421


[css] Added "ol.tree" to the selectors

Hi,
It happened to me that I wanted to display vars in a page with a menu and its items were moved by the "li" selector

Thanks, you are right. I'll merge tree.css soon.


CONTRIBUTING.md missing to state JS contributions

Currently we are accepting contributions in C, C++, Java, Python and Go but other languages may be considered after a discussion.

Since we have started JavaScript submissions too, so we need to add JS there as well.

Can I work on this ? 😆

Hard luck, my other issue just got merged :laughing:

Do we really need a PR for this @aviaryan ?

Yes please send a PR. Will you like to work on this?

Yes, assign me please :+1:


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Make atscppapi::RegisterGlobalPlugin return a value.

TSError doesn't abort the execution, so a plugin might fail to be
registered and TSPluginInit might continue execution.
With this change, atscppapi::RegisterGlobalPlugin returns a boolean that
a plugin can check to decide whether to abort or continue.
Signed-off-by: David Calavera<EMAIL_ADDRESS>

I can also change the examples and current plugins if this change is approved.

[approve ci]

Looks reasonable to me. Could you send an API proposal on dev@ mailing list?

I've updated the examples and plugins too.

[approve ci]


Tech: Provide selenide and appium java client on api level

@rosolko Ups, superseded by commit https://github.com/selenide/selenide-appium/commit/4d2cd18f665193165f4dabfd66870c64cc08d939 :)


Revert "198 clean memory utilisation"

Reverts R-Type-Epitech-Nantes/R-Type#208

Codecov Report

Merging #212 (7d4aa80) into master (e6de0a4) will decrease coverage by 0.01%.
The diff coverage is 4.54%.

@@            Coverage Diff             @@
##           master     #212      +/-   ##
==========================================
- Coverage   30.47%   30.45%   -0.02%
==========================================
  Files          96       96
  Lines        1854     1855       +1
  Branches      901      902       +1
==========================================
  Hits          565      565
  Misses        942      942
- Partials      347      348       +1

Impacted Files
Coverage Δ

Server/Room.cpp
0.00% <0.00%> (ø)

libs/Transisthor/Transisthor.cpp
63.03% <0.00%> (-0.17%)
:arrow_down:

...SLogic/Client/Systems/SendNewlyCreatedToServer.cpp
0.00% <0.00%> (ø)

...ransisthorECSLogic/Client/Systems/SendToServer.hpp
0.00% <0.00%> (ø)

...Logic/Server/Systems/SendNewlyCreatedToClients.cpp
0.00% <0.00%> (ø)

...ransisthorECSLogic/Server/Systems/SendToClient.hpp
0.00% <0.00%> (ø)

libs/Communicator/Sender.cpp
45.16% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


[RFC] kpod Command Line Discussion

I've started implementing some CLI commands for kpod, and realized that I didn't have a solid grasp on how to lay out the CLI for common commands. @mrunalp had a good idea where he wanted to go with it, but we agreed it was reasonable to put it up for comment and discussion.
The way I've been thinking of approaching it is to split the CLI into separate commands for containers and pod operations (tentatively, kpod pod and kpod ctr) with further commands (launch, list, remove, get) for each - so kpod pod launch to launch a new pod, kpod ctr remove to remove a container, etc. Container operations would mostly require a target pod be given (save things like list). The downside of this is a that it ends up more verbose than just switching between acting on a single container or a whole pod with flags.

@mrunalp You had a different way of laying out commands, but I don't remember it well enough to write it out myself, so I'll leave that to you

so removing a container would be:
kpod ctr remove my-pod my-container

... seems pretty logical and easy to remember.
The alternative, since for container operations you pretty much always need to list a pod, would be to imply.  That is, if I type kpod remove my-pod it removes the pod, but kpod remove my-pod my-container removes the container from the pod.  That would save typing, except that it wouldn't work for all commands.

We have moved kpod to following the docker syntax for commands.  I think that is simplest and easiest for people to convert.  I think we should close this issue.
@mrunalp @runcom Please close this.


Junction points on NTFS volumes (mklink /j) not seen in DriveFS

DriveFS doesn't seem to see or traverse NTFS junction points. Here is the sample command line / bash session.  The junction point junc doesn't show up in the bash session.
C:\Users\monro\OneDrive\Saved Games>ver

Microsoft Windows [Version 10.0.14367]

C:\Users\monro\OneDrive\Saved Games>dir /a
 Volume in drive C is System
 Volume Serial Number is 4203-D40A

 Directory of C:\Users\monro\OneDrive\Saved Games

2016-06-20  09:12 AM    <DIR>          .
2016-06-20  09:12 AM    <DIR>          ..
2016-06-17  06:11 PM               282 desktop.ini
               1 File(s)            282 bytes
               2 Dir(s)  163,485,835,264 bytes free

C:\Users\monro\OneDrive\Saved Games>mkdir test

C:\Users\monro\OneDrive\Saved Games>mklink /j junc test
Junction created for junc <<===>> test

C:\Users\monro\OneDrive\Saved Games>dir /a
 Volume in drive C is System
 Volume Serial Number is 4203-D40A

 Directory of C:\Users\monro\OneDrive\Saved Games

2016-06-20  09:13 AM    <DIR>          .
2016-06-20  09:13 AM    <DIR>          ..
2016-06-17  06:11 PM               282 desktop.ini
2016-06-20  09:13 AM    <JUNCTION>     junc [C:\Users\monro\OneDrive\Saved Games\test]
2016-06-20  09:12 AM    <DIR>          test
               1 File(s)            282 bytes
               4 Dir(s)  163,485,765,632 bytes free

C:\Users\monro\OneDrive\Saved Games>bash
monroe@DEV-MONROE:/mnt/c/Users/monro/OneDrive/Saved Games$ ls -la
total 4
drwxrwxrwx 2 root root   0 Jun 20 09:13 .
drwxrwxrwx 2 root root   0 Jun 20 08:26 ..
-rwxrwxrwx 1 root root 282 Jun 17 18:11 desktop.ini
drwxrwxrwx 2 root root   0 Jun 20 09:12 test
monroe@DEV-MONROE:/mnt/c/Users/monro/OneDrive/Saved Games$

Not sure if this is a dupe of #201 or not (not enough info in that issue), but it's the closest one I could find.  If the fix for #201 is relevant, I guess it hasn't made it into the Fast ring as of build 14367.

This is by design for the anniversary edition. Today Windows symlinks/junction points remain visible only inside Windows and Linux symlinks created inside WSL remain visible inside WSL. They are not accessible to each other.
Two primary reasons

The name spaces in Windows and Linux are different. There are volumes in Windows not accessible by WSL yet, think FAT partitions, removable volumes etc. Similarly there are Linux virtual file systems like /proc not accessible from Windows.
Linux symlinks are created by WSL using a custom reparse point which Windows does not compute and WSL ignores all other reparse points.

Open to revisiting the decision based on user feedback in the future.

The "By Design" response should definitely be considered temporary / a workaround.  The Windows NTFS implementation of - for example - symlinks - is perfectly fine, and should be completely interpretable as WSL symlinks.  Junctions can be viewed as a primitive symlink that happens to be an absolute pathname link text - and is easily reversibly translated.
The current status of "by design" implies limited interoperability of the 2 subsystems, improving the value of just using Linux in a VM.

@dethoma @benhillis  thanks for the response.  Based on #201, I wasn't sure whether this was by design or a bug, but I can understand it being a limitation for the Anniversary release.  In the future it would be nice if WSL at least tried to parse a greater subset of reparse points (eg, junction points) and errored out if the target volume type is not compatible with DrvFS.

@jamesdavidhoward As Deepu alluded to, we're nearing the release of the Windows 10 anniversary update and unfortunately that means that we will not have time to address every issue on this forum in the update.  I would highly recommend visiting our user voice page and making your voice heard there about the features you'd like us to work on in future releases.

I concur with the prior comment about acceptability of improving handling
and visibility of junctions (and symlinks and hardlinks) after the
"Anniversary Release".  My expectation, based on importance and frequency
of requests for this, is to see:
1.) a commitment to improve this
2.) identify it as "fix future" or (something like) "after Anniversary"
The current responses are non-responses; the kind of thing that would get
me a frown from my Intel managers...

James D. Howard<EMAIL_ADDRESS>

@jamesdavidhoward -- I can't speak for Microsoft specifically (haven't worked there in a long time), but I've previously posted professionally/regularly on a technical forum on behalf of HP.  If I had given "real" answers on that forum, in the sense that you're referring to, I would have gotten much worse than just a frown from any of my managers :-)
Answers posted by employees to a public forum can have legal and contractual significance in terms of revenue recognition, etc.  I've seen (not on said HP forums) a large team at a major tech company thrown months off schedule because of one incorrect comment somewhere on the Internet by a low-level employee that a customer interpreted as a commitment.  I imagine you've encountered the same in your years at Intel too.
So, if you want a decision, talk to a PM, and wait in line while they process your request :-)  My experience here (though anyone who actually works at Microsoft is of course welcome to correct my understanding) is that such commitments have been more forthcoming on the UserVoice forum, which I think is better designed to gather feedback on broader issues that thousands of people care about in different ways.
In contrast -- this github site seems to get responses directly from Microsoft engineers.  Exactly the people who my manager would have wanted to not make public commitments on the Internet :-)  But if you've got a specific bug or technical question and you want an answer right now, nothing beats a direct line to the people who know the code.

Reopening while on backlog.

If anyone would like this functionality, there's a UserVoice for it; go here to up-vote:
https://wpdev.uservoice.com/forums/266908-command-prompt-console-bash-on-ubuntu-on-windo/suggestions/13351308-junction-support

Is there any news on this and syncronising links and junctions in general? I really want to use wsl with npm and VS Code but this is a blocking issue

mklink (NTFS junctions) are seen as symlink in WSL (fall creator update 1709)
But beware that it's case sensitive, and WSL cares about it.
mklink /D node_modules D:\dvp\node_modules\async
dir node_modules
<JUNCTION>     async-co [D:\dvp\node_modules\async-co]
=> seen as symlink to /mnt/d/dvp/node_modules in WSL

Whereas
mklink /D node_modules d:\dvp\node_modules\async  (note the lowercase D)
dir node_modules
<JUNCTION>     async-co [d:\dvp\node_modules\async-co]  (works in windows)
=> invalid link in WSL

doesn't work for me at all. Am on fall update.
On C: to C:

mklink /D creates a symb link as described
mklink /J creates a junction

both appear in bash ls as red and give io/error.
Does Fall update require reinstalling WSL link Creators did?

Correction! it does work! I forgot to use capital U for users in my destination path!
However /D does created a SYMBLINKD not JUNCTION - but it works
I Find the reverse doesn't seem to work. Should it?
ln -s desktop /mnt/C/Users/steve/Desktop is seen as this in cmd dir
<JUNCTION>     desktop3 [...]
where ... is expected to b C:\User\steve\Desktop
and access fails to see the desktop contents.

This is fixed as of Insiders build 16215 - https://docs.microsoft.com/en-us/windows/wsl/release-notes#build-16215

This is not fixed.
I see that in in 16215 'Support directory junctions in drvfs.' sounds like someone thinks this works...
But today...
[panther@panther-pc sack]$ ls -ls /mnt/c/general
ls: cannot read symbolic link '/mnt/c/general/android': Input/output error
ls: cannot read symbolic link '/mnt/c/general/android.x': Input/output error
ls: cannot read symbolic link '/mnt/c/general/build': Input/output error
ls: cannot read symbolic link '/mnt/c/general/build.other': Input/output error
ls: cannot read symbolic link '/mnt/c/general/work': Input/output error
total 0
0 lrwxrwxrwx 1 root root 0 Aug  4 09:31 android
0 lrwxrwxrwx 1 root root 0 Dec 19  2017 android.x
0 lrwxrwxrwx 1 root root 0 Dec 19  2017 build
0 lrwxrwxrwx 1 root root 0 Dec 19  2017 build.other
0 lrwxrwxrwx 1 root root 0 Dec 15  2017 work
[panther@panther-pc sack]$ ls -ls /mnt/c/general/work
ls: cannot read symbolic link '/mnt/c/general/work': Input/output error
0 lrwxrwxrwx 1 root root 0 Dec 15  2017 /mnt/c/general/work
[panther@panther-pc sack]$ ek

C:\general>dir
 Volume in drive C is OS
 Volume Serial Number is F27E-3A0D

 Directory of C:\general

08/04/2018  08:31 AM    <DIR>          .
08/04/2018  08:31 AM    <DIR>          ..
08/04/2018  08:31 AM    <JUNCTION>     android [\??\Volume{c528513d-e5a0-45f2-9cb6-324aaf67eea9}\]
12/19/2017  10:59 AM    <JUNCTION>     android.x [\??\Volume{bf7cb924-0000-0000-0000-100000000000}\]
12/19/2017  10:55 AM    <JUNCTION>     build [\??\Volume{30204767-0000-0000-0000-100000000000}\]
12/19/2017  11:03 AM    <JUNCTION>     build.other [\??\Volume{4523f244-19b2-4fb6-9b4d-32a31ddd458f}\]
12/15/2017  07:11 PM    <JUNCTION>     work [\??\Volume{3020476d-0000-0000-0000-100000000000}\]

This is not fixed. Junctions are still inaccessible inside of WSL2 Ubuntu, W10 Build 20215.1000.

Still broken on WSL 2 (Debian) with Kernel 5.10.43 on Windows 11 22449.rs_prerelease.210827...


fix: update conda env file and fix bug in starting app

This PR aims to solve some bugs

I updated conda env file
Fix code lines in seismicedubox.py for starting the web app
Update README.md

I was trying to reproduce the error that @JoseMariaGarciaMarquez mention in #1 but It seems that I do not have the needed files to test it.

LGTM. I've already uploaded the SEGY file to the drive.:
https://drive.google.com/drive/folders/1pBpwM7Zxjay11RMB-D_svXUdor_k6ZHA?usp=sharing


How to disable the extension in a workspace?

Hi,
I have a doubt, this extension conflicts with Deno projects.
Deno extensions recommend disabling TypeScript support to work correctly. How to disable the extension only in the workspace running Deno?
Thanks in advance

⚠ Archived: Although it was fun to build my nova extensions, I haven't ended up using Nova regularly and can't devote the time to maintenance. Feel free to reach out if you want to fork and start maintaining an alternative.


fixing the main readme file

Great! One minor point: we now use larq.dev and github.com/larq/larq interchangeably. We should probably pick one.

👍 I think make sense to pick the larq.dev should I change the larq zoo links to https://larq.dev/models/ instead of the repo on github as well?

Yes I think so, although this link may become https://docs.larq.dev/zoo after today, but again if that's the case I'll send a PR to fix it when that happens.


New version: KristenMcWilliam.Nyrna version 2.11.1 [FP-O]

Result: Installation Failed

Manifest
Add/Remove Programs

Name
Nyrna

Version
2.11.1

Publisher
Kristen McWilliam

ProductCode

Auto-updated by vedantmgoyal2009/winget-pkgs-automation in workflow run 5723

@wingetbot run

This package installs normally, but requires Microsoft.VCRedist.2015+.x64 to run:

/AzurePipelines run


Fixed UG for overall descriptions and rate, changed aesthetics for html page

Fixes #215 #157 #210 #200 for documentation.
Updated:

Introduction Catchy Phrase
Overall description
Grammar typo in rate command
Performance rating graph description
rate once per day note
Aesthetic changes to the HTML site for colors

Codecov Report

Merging #227 (533aef5) into master (21df779) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #227   +/-   ##
=========================================
  Coverage     56.41%   56.41%
  Complexity      499      499
=========================================
  Files            93       93
  Lines          2145     2145
  Branches        259      259
=========================================
  Hits           1210     1210
  Misses          865      865
  Partials         70       70

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Tutorial kprobe on do_sys_open records no events

I walked through the basic tutorial without error, but did not get any output/events. Progs and maps as inspected with bpftool seemed fine. Eventually I realized that even this kprobe usage example doesn't record any events, suggesting the problem is outside the scope of redbpf. Then tried the echo example and it works.
I don't know where this belongs / what causes it / how to fix it. I thought I post it here to make folks aware and help those who end up google'ing for the same "error".
Kernel: 5.16.5-arch1-1
LLVM: 13.0.0-6

Same problem
5.15.16-1-MANJARO
13.0.0

I think I got it:
https://man.archlinux.org/man/kernel_lockdown.7
Don't know how to fix it just yet, other then disabling secure boot.
Will test it out tomorrow

Ok so I couldn't sleep...
sudo bpftrace -e 'tracepoint:syscalls:sys_enter_open { printf("%s %s\n", comm, str(args->filename)); } '

Just seems to do nothing, but on the other hand
sudo bpftrace -e 'tracepoint:syscalls:sys_enter_openat { printf("%s %s\n", comm, str(args->filename)); }'

does give output.
It turns out the issue was not kernel lockdown, but instead the same referenced in this thread

For those stumbling about this issues like me, the problem is that most processes don't use the open syscall, but the openat syscall instead.

But for some reason I can't get the tutorial to attach to anything else...

Alright, check out https://github.com/foniod/redbpf/issues/266
The tutorial was changed from do_sys_openat2, which actually works for me.
I will probably open a PR tomorrow to add some kind of advisory to the tutorial.
And you know what? I learned something about my system using bpf ;)

Hello @joachimneu
Does the answer from @cr0ax solve your issue?

Haven't tried, but makes sense, thanks!


Error when newest typescript is installed

v2.0.1 doesn't work with the newest typescript version.
I saw that plugin has a dependency for typescript:^3.9. With this version everything works but when I update typescript to 4.3.5 I get this error:
--ts_out: TypeError: Cannot read property 'kind' of undefined
v1.0.13 didn't have any problems with typescript 4.

This installs fine for me:
npm init -y
npm i<EMAIL_ADDRESS><EMAIL_ADDRESS>curl https://raw.githubusercontent.com/timostamm/protobuf-ts/master/packages/test-fixtures/msg-readme.proto > msg-readme.proto
npx protoc --ts_out . -I . --experimental_allow_proto3_optional msg-readme.proto

node_modules/typescript will be 4.3.5.
node_modules/@protobuf-ts/plugin/node_modules/typescript will be 3.9.10.
Can you provide some details how you encountered this error?

I'm using yarn Plug'n'Play:
yarn set version berry
yarn init
yarn add<EMAIL_ADDRESS><EMAIL_ADDRESS>curl https://raw.githubusercontent.com/timostamm/protobuf-ts/master/packages/test-fixtures/msg-readme.proto > msg-readme.proto

add script to your package.json:
"scripts": {"proto": "protoc --ts_out . -I . --experimental_allow_proto3_optional msg-readme.proto"},

yarn proto

The yarn pre-release version gets confused by @protobuf-ts/plugin's typescript peer dependency and updates it's non-peer dependency.
This will likely be fixed before yarn 2.0 is released, but we better drop the peer dependency until then.
Fix is released in<EMAIL_ADDRESS>Thanks for the report! Please reopen if you notice something off.


easeParams do not work when tweening multiple properties

Version

Phaser Version: v3.15.1-FB

Description
When using the syntax for tweening multiple properties the easeParams option does not work.
Example Test Code
This does not work:
this.scene.tweens.add({
    targets: this,
    angle: {
        value: 90,
        duration: 200,
        ease: 'Elastic.easeOut',
        easeParams: [ .5, .5 ], // Ignored
    },
    y: {
        value: 100,
        ease: 'Cubic.easeOut',
        duration: 300,
    }
});

This works:
this.scene.tweens.add({
    targets: this,
    angle: 90,
    duration: 200,
    ease: 'Elastic.easeOut',
    easeParams: [ .5, .5 ],
});

this.scene.tweens.add({
    targets: this,
    y: 100,
    duration: 300,
    ease: 'Cubic.easeOut',
});

I'm also having this issue.  Any luck finding a solution?

Thank you for submitting this issue. We have fixed this and the fix has been pushed to the master branch. It will be part of the next release. If you get time to build and test it for yourself we would appreciate that.


Secure boot check fails after reflashing bootloader (IDFGH-13425)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report
I got new device and enabled the secure boot option and selected Secure bootloader mode (Reflashable) and attached the (secure_boot_signing_key.pem) Secure boot private signing key in menuconfig. Then I uploaded my firmware and everything worked fine.
My question, is key is automatically burned into chip of secure boot?
ABS_DONE_0 (BLOCK0)                                Secure boot V1 is enabled for bootloader image     = True R/W (0b1)
if yes, in which BLOCK? Because in summary I don't see any BLOCK0
However, I faced some issue and mistakenly erased all the flash from 0x00 . According to docu, it should be fine as we have set re-flashable into config.
After that I run the following command
esptool.py --before default_reset --after no_reset write_flash --flash_mode dio --flash_freq 40m --flash_size 4MB 0x0 build/bootloader/bootloader-reflash-digest.bin --force and works fine.
Then
esptool.py --before default_reset --after no_reset --chip esp32  write_flash --flash_mode dio --flash_size 4MB --flash_freq 40m 0x20000 build/partition_table/partition-table.bin 0x68000 build/ota_data_initial.bin 0x70000 build/iot_c.bin
After that I try to run with idf.py monitor but getting the following error.
rst:0x10 (RTCWDT_RTC_RESET),boot:0x1b (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff00b8,len:2280
load:0x40078000,len:21916
ho 0 tail 12 room 4
load:0x40080400,len:4
load:0x40080404,len:2856
secure boot check fail
ets_main.c 371
ets Jun  8 2016 00:22:57

I was forgetting, when I flashed first time bootloader on 0x1000, everything worked fine.

@sachin0x18 Can you help me please. Because I saw that you answered the similar question.

Hi @AmritpalSinghSarao!

My question, is key is automatically burned into chip of secure boot?

Yes, at the first boot, the bootloader burns the key into the BLOCK2.

secure boot check fail

Try to write the bootloader-reflash-digest.bin without the --flash_mode dio --flash_freq 40m --flash_size 4MB flags I suspect that they are different from what you have in the binary file and esptool changes the bootloader image on the fly and do not change the signature.
esptool.py --before default_reset --after no_reset write_flash  0x0 build/bootloader/bootloader-reflash-digest.bin --force

Follow instructions in the doc to get Reflashable Software Bootloader - https://docs.espressif.com/projects/esp-idf/en/stable/esp32/security/secure-boot-v1.html#reflashable-software-bootloader.

@KonstantinKondrashov
I run your command but have the same issue.
Erasing the flash could have had impact on device?
Just wondering is there any way to check if that bootloader was flashed with re-flashable mode not one-time?
I am quite sure that we did with re-flashable mode which is our default setting.

@AmritpalSinghSarao

Can you please confirm if you had indeed flashed the secure boot key using espefuse.py burn_key command? The command gets auto-generated during the 1st build phase and its highlighted under title "Burn secure boot key to efuse using".
Re-flashable bootloader setting you can confirm from your sdkconfig - CONFIG_SECURE_BOOTLOADER_REFLASHABLE entry
Please share output of espefuse.py summary command and your project sdkconfig here

Side-note: If you are using ESP32 with rev >= 3.0 then its highly recommended to use secure boot v2 scheme.

@mahavirj Thanks for your response.

I have never run espefuse.py burn_key. I have only run idf.py bootloader-flash
I know that, but wanted to confirm whether we can check or not, that which setting was set while flashing boot.
I can't provide that information soon, it might take 2 week.
Please keep this issue open. I will espefuse.py summary once I have that device back.

@mahavirj
=== Run "summary" command ===
EFUSE_NAME (Block) Description  = [Meaningful Value] [Readable/Writeable] (Hex Value)
Calibration fuses:
ADC_VREF (BLOCK0)                                  True ADC reference voltage                         = 1156 R/W (0b01000)
Config fuses:
WR_DIS (BLOCK0)                                    Efuse write disable mask                           = 256 R/W (0x0100)
RD_DIS (BLOCK0)                                    Disable reading from BlOCK1-3                      = 2 R/W (0x2)
DISABLE_APP_CPU (BLOCK0)                           Disables APP CPU                                   = False R/W (0b0)
DISABLE_BT (BLOCK0)                                Disables Bluetooth                                 = False R/W (0b0)
DIS_CACHE (BLOCK0)                                 Disables cache                                     = False R/W (0b0)
CHIP_CPU_FREQ_LOW (BLOCK0)                         If set alongside EFUSE_RD_CHIP_CPU_FREQ_RATED; the = False R/W (0b0)
ESP32's max CPU frequency is rated for 160MHz. 24
0MHz otherwise
CHIP_CPU_FREQ_RATED (BLOCK0)                       If set; the ESP32's maximum CPU frequency has been = True R/W (0b1)
rated
BLK3_PART_RESERVE (BLOCK0)                         BLOCK3 partially served for ADC calibration data   = False R/W (0b0)
CLK8M_FREQ (BLOCK0)                                8MHz clock freq override                           = 54 R/W (0x36)
VOL_LEVEL_HP_INV (BLOCK0)                          This field stores the voltage level for CPU to run = 0 R/W (0b00)
at 240 MHz; or for flash/PSRAM to run at 80 MHz.0
x0: level 7; 0x1: level 6; 0x2: level 5; 0x3: leve
l 4. (RO)
CODING_SCHEME (BLOCK0)                             Efuse variable block length scheme
= NONE (BLK1-3 len=256 bits) R/W (0b00)
CONSOLE_DEBUG_DISABLE (BLOCK0)                     Disable ROM BASIC interpreter fallback             = True R/W (0b1)
DISABLE_SDIO_HOST (BLOCK0)                                                                            = False R/W (0b0)
DISABLE_DL_CACHE (BLOCK0)                          Disable flash cache in UART bootloader             = False R/W (0b0)
Flash fuses:
FLASH_CRYPT_CNT (BLOCK0)                           Flash encryption is enabled if this field has an o = 0 R/W (0b0000000)
dd number of bits set
FLASH_CRYPT_CONFIG (BLOCK0)                        Flash encryption config (key tweak bits)           = 0 R/W (0x0)
Identity fuses:
CHIP_PACKAGE_4BIT (BLOCK0)                         Chip package identifier #4bit                      = False R/W (0b0)
CHIP_PACKAGE (BLOCK0)                              Chip package identifier                            = 1 R/W (0b001)
CHIP_VER_REV1 (BLOCK0)                             bit is set to 1 for rev1 silicon                   = True R/W (0b1)
CHIP_VER_REV2 (BLOCK0)                                                                                = False R/W (0b0)
WAFER_VERSION_MINOR (BLOCK0)                                                                          = 0 R/W (0b00)
WAFER_VERSION_MAJOR (BLOCK0)                       calc WAFER VERSION MAJOR from CHIP_VER_REV1 and CH = 1 R/W (0b001)
IP_VER_REV2 and apb_ctl_date (read only)
PKG_VERSION (BLOCK0)                               calc Chip package = CHIP_PACKAGE_4BIT << 3 + CHIP_ = 1 R/W (0x1)
PACKAGE (read only)
Jtag fuses:
JTAG_DISABLE (BLOCK0)                              Disable JTAG                                       = True R/W (0b1)
Mac fuses:
MAC (BLOCK0)                                       MAC address
= 94:3c:c6:b1:fe:10 (CRC 0x37 OK) R/W
MAC_CRC (BLOCK0)                                   CRC8 for MAC address                               = 55 R/W (0x37)
MAC_VERSION (BLOCK3)                               Version of the MAC field                           = 0 R/W (0x00)
Security fuses:
UART_DOWNLOAD_DIS (BLOCK0)                         Disable UART download mode. Valid for ESP32 V3 and = False R/W (0b0)
newer; only
ABS_DONE_0 (BLOCK0)                                Secure boot V1 is enabled for bootloader image     = True R/W (0b1)
ABS_DONE_1 (BLOCK0)                                Secure boot V2 is enabled for bootloader image     = False R/W (0b0)
DISABLE_DL_ENCRYPT (BLOCK0)                        Disable flash encryption in UART bootloader        = False R/W (0b0)
DISABLE_DL_DECRYPT (BLOCK0)                        Disable flash decryption in UART bootloader        = False R/W (0b0)
KEY_STATUS (BLOCK0)                                Usage of efuse block 3 (reserved)                  = False R/W (0b0)
SECURE_VERSION (BLOCK3)                            Secure version for anti-rollback                   = 0 R/W (0x00000000)
BLOCK1 (BLOCK1)                                    Flash encryption key
= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 R/W
BLOCK2 (BLOCK2)                                    Security boot key
= ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? -/-
BLOCK3 (BLOCK3)                                    Variable Block 3
= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 R/W
Spi Pad fuses:
SPI_PAD_CONFIG_HD (BLOCK0)                         read for SPI_pad_config_hd                         = 0 R/W (0b00000)
SPI_PAD_CONFIG_CLK (BLOCK0)                        Override SD_CLK pad (GPIO6/SPICLK)                 = 0 R/W (0b00000)
SPI_PAD_CONFIG_Q (BLOCK0)                          Override SD_DATA_0 pad (GPIO7/SPIQ)                = 0 R/W (0b00000)
SPI_PAD_CONFIG_D (BLOCK0)                          Override SD_DATA_1 pad (GPIO8/SPID)                = 0 R/W (0b00000)
SPI_PAD_CONFIG_CS0 (BLOCK0)                        Override SD_CMD pad (GPIO11/SPICS0)                = 0 R/W (0b00000)
Vdd fuses:
XPD_SDIO_REG (BLOCK0)                              read for XPD_SDIO_REG                              = False R/W (0b0)
XPD_SDIO_TIEH (BLOCK0)                             If XPD_SDIO_FORCE & XPD_SDIO_REG                   = 1.8V R/W (0b0)
XPD_SDIO_FORCE (BLOCK0)                            Ignore MTDI pin (GPIO12) for VDD_SDIO on reset     = False R/W (0b0)
Flash voltage (VDD_SDIO) determined by GPIO12 on reset (High for 1.8V, Low/NC for 3.3V)

Security features

CONFIG_SECURE_SIGNED_ON_BOOT=y
CONFIG_SECURE_SIGNED_ON_UPDATE=y
CONFIG_SECURE_SIGNED_APPS=y
CONFIG_SECURE_BOOT_V1_SUPPORTED=y
CONFIG_SECURE_SIGNED_APPS_ECDSA_SCHEME=y
CONFIG_SECURE_BOOT=y
CONFIG_SECURE_BOOT_V1_ENABLED=y
CONFIG_SECURE_BOOTLOADER_ONE_TIME_FLASH is not set
CONFIG_SECURE_BOOTLOADER_REFLASHABLE=y
CONFIG_SECURE_BOOT_BUILD_SIGNED_BINARIES=y
CONFIG_SECURE_BOOT_SIGNING_KEY="secure_boot_signing_key.pem"
CONFIG_SECURE_BOOTLOADER_KEY_ENCODING_256BIT=y
CONFIG_SECURE_BOOTLOADER_KEY_ENCODING_192BIT is not set
CONFIG_SECURE_BOOT_INSECURE is not set
CONFIG_SECURE_FLASH_ENC_ENABLED is not set
end of Security features
I went through the documentation again, if we run idf.py bootloader-flash, it will will generate the hardware generated key and will burn it, even though, we have selected the re-flashable option. To have, the re-flashable, I should have used my own key.
I think, this might have created some confusion.

@AmritpalSinghSarao
The step to burn secure boot v1 specific key is highlighted in the documentation section here (step 4): https://docs.espressif.com/projects/esp-idf/en/latest/esp32/security/secure-boot-v1.html#reflashable-software-bootloader. If you have missed out on that then it is not possible to update the bootloader on this device.
FWIW, we are trying to integrate different security workflows through qemu (emulator) port for different targets. This will allow to establish the workflow under emulator setup and then it can be moved to real hardware. Please keep an eye on the documentation guide here: https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-guides/tools/qemu.html
Closing the issue, please feel free to re-open if you have more questions


m04-code-level-design

I give this lecture on Wednesday nite.   Still need to decide whether these activities will be required.

i wouldn't mind skipping this activity.

Need to add calendar entry (update /_data/modules.yml)
Add the following in activity handout: ("See canvas assignment for details")
Need to update title slide / instructor names.
Rest LGTM (mostly same as last semester which was good, no negatives from previous feedback)

Calendar is fixed.
Authors on title slide is fixed.
I didn't add "See canvas assignment for details".   First, we agreed that we weren't going to assign either of these activities, and second, this sentence didn't appear in previous handouts (though maybe it should-- I will look at what I'm doing for M06.
Feel free to merge if it's ok with you.


ARTEMIS-3993 Fix test

[INFO] There is 1 error reported by Checkstyle 9.2.1 with /home/runner/work/activemq-artemis/activemq-artemis/artemis-server/../etc/checkstyle.xml ruleset.
Error:  src/test/java/org/apache/activemq/artemis/core/config/impl/FileConfigurationParserTest.java:[40,8] (imports) UnusedImports: Unused import - org.apache.activemq.artemis.nativo.jlibaio.LibaioContext.

I went ahead and fixed this and pushed directly to main since it was blowing up everybody's PR builds.


FROM python:3.10-slim-buster

Pull Request
Description
update docker version
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.
Please also list any relevant details for your test configuration

[ ] Yes

If your changes affect data processing, have you plotted any changes? i.e. have you done a quick sanity check?

[ ] Yes

Checklist:

[ ] My code follows OCF's coding style guidelines
[ ] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have checked my code and corrected any misspellings

Codecov Report

Merging #84 (a80ebf8) into main (2fc40cf) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #84   +/-   ##
=======================================
  Coverage   98.21%   98.21%
=======================================
  Files           9        9
  Lines         224      224
=======================================
  Hits          220      220
  Misses          4        4

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more