Adding verified domain with .com.br returns error Url should not contain subdomains including "www"

Describe the bug
I'm trying to add my domain https://microhobby.com.br/ to verify my extensions ownership but the platform seems to be detecting .br as a subdomain. So, I'm getting the error Url should not contain subdomains including "www" when I hit the save button.
To Reproduce
Steps to reproduce the behavior:

Go to Manage Publishers & Extensions
Click on Publisher details
Set the Verified Domain field to any ".com.br" domain
Save
See error

Expected behavior
Be able to use ".com.br" domains to verify ownership.
Desktop (please complete the following information):

OS: Windows 11 Dev Channel
Browser Microsoft Edge
Version 95.0.1020.53 (Official build) (64-bit)

@roblourens @prashantvc I still don't know if this is something wrong on my side or on your side. In my opinion ".com.br" domains should also be valid and your verification is wrong, thinking that .br is a subdomain instead of a country code.

This sounds like a bug to me; we are going to pick it up for next sprint. Thanks for reporting :)

@prashantvc As per this RFC https://datatracker.ietf.org/doc/html/rfc1034#:~:text=A domain is,D%2C D%2C and " ".
In this url:
br is the Top level domain
com is the primary domain
microhobby is the subdomain
So this error is expected. Please correct me if I'm wrong.

Having the same issue with a .co.uk domain.

@prashantvc As per this RFC https://datatracker.ietf.org/doc/html/rfc1034#:~:text=A domain is,D%2C D%2C and " ".
In this url: br is the Top level domain com is the primary domain microhobby is the subdomain
So this error is expected. Please correct me if I'm wrong.

No, this error is not expected. "com.br" as "co.uk" are the Top level domain (TLD) in this case. Look this RFC https://datatracker.ietf.org/doc/html/rfc1591#section-2

I have the same issue with a .com ...

I'm closing this because it's now working. I was able to verify my .com.br domain.


parent_as in assoc

I have a question regarding a possible feature (a PR I could work on):
I sometimes have a query filter that needs to do an "exists" joined on a parent, it would be great if I could do something like:
    query
    |> where(
      exists(
        from(
          c in assoc(parent_as(:foo), :category),
          where: c.id == ^category_id,
          select: true
        )
      )
    )

But now I have to manually join because I can't use parent_as inside assoc:
    query
    |> where(
      exists(
        from(
          c in "foo_category",
          where: c.foo_id == parent_as(:foo).id and c.id == ^category_id,
          select: true
        )
      )
    )

Would it be easy to add support for the former? (I could work on that)
Ideally I would also like this to work (but I'm not sure how hard this is):
    query
    |> where(
      [foo: f],
      exists(
        from(
          c in assoc(f, :category),
          where: c.id == ^category_id,
          select: true
        )
      )
    )

Closing this. If still interested, a PR is welcome!


row labels don't always show on interactiveheatmap

In Arbor applications, species names don't show for character matrices.  For example, the interactiveheatmap currently looks good for the anolisDataAppended dataset, but not for geospiza_characters or for a few others I tried.  Often the species names are converted to indexes instead.

Interesting. Have you tracked down any specific property of the table that causes this difference?


Refold

Sorry I never responded here. I wasn't sure what this PR was about. It seems to have changed a lot of things. What has changed and why?


Misbehavior in Safari

If your timezone is +3:30 (Iran) These expressions:
moment(new Date(2018,2,21,0,0,0)).startOf('day').format('YY/MM/DD HH:mm:ss ZZ')
moment(new Date(2018,2,22,0,0,0)).startOf('day').format('YY/MM/DD HH:mm:ss ZZ')

both return "18/03/21 00:00:00 +0330" in Safari.
Environment:
Safari 11.03, MacOS High Sierra (10.13.3)
There's no problem in Chrome.
console.log( (new Date()).toString())
console.log((new Date()).toLocaleString())
console.log( (new Date()).getTimezoneOffset())
console.log( navigator.userAgent)
console.log(moment.version)

Result:
"Sat Mar 03 2018 20:12:57 GMT+0330 (+0330)"
"3/3/2018, 8:12:57 PM"
-210
"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/604.5.6 (KHTML, like Gecko) Version/11.0.3 Safari/604.5.6"
"2.14.1"

If you run this JSBin in Safari with the above mentioned timezone you should see the results mentioned above in console.

For reference: This was first reported in moment-jalali here: https://github.com/jalaali/moment-jalaali/issues/128.

This sounds like a bug in Date, not in moment.
Can you check the value of new Date(2018,2,22,0,0,0).valueOf() in Chrome and Safari?

Sure, this is in Chrome:
> new Date(2018,2,22,0,0,0).valueOf()
<<PHONE_NUMBER>000
> new Date(2018,2,22,0,0,0)
< Thu Mar 22 2018 01:00:00 GMT+0430 (+0430)

This is in Safari:
> new Date(2018,2,22,0,0,0).valueOf()
<<PHONE_NUMBER>000
> new Date(2018,2,22,0,0,0)
< Wed Mar 21 2018 23:00:00 GMT+0330 (+0330)

Hello.
I am struggling with the same problem and can't seem to find a fix yet. Maybe someone will figure it out eventually...
Here is what I am using:
Firefox:
var time_zone_br = Intl.DateTimeFormat().resolvedOptions().timeZone;
console.log(time_zone_br);
var date_tz =  moment("2018-03-20 16:20").tz(time_zone_br).format("YYYY-MM-D HH:mm");
console.log(date_tz);
> America/Montreal
> 2018-03-20 12:20

Chrome:
var time_zone_br = Intl.DateTimeFormat().resolvedOptions().timeZone;
console.log(time_zone_br);
var date_tz =  moment("2018-03-20 16:20").tz(time_zone_br).format("YYYY-MM-D HH:mm");
console.log(date_tz);
> America/Montreal
> 2018-03-20 12:20

Safari:
var time_zone_br = Intl.DateTimeFormat().resolvedOptions().timeZone;
console.log(time_zone_br);
var date_tz =  moment("2018-03-20 16:20").tz(time_zone_br).format("YYYY-MM-D HH:mm");
console.log(date_tz);
> [Log] America/Montreal
> [Log] 2018-03-20 16:20

@sassanh I think it's pretty clear that there is some DST going on there. Browsers (and Safari in particular) are notoriously buggy in that regard. In moment 3.x DST will be handled internally, so all of that will go away. 2.x however -- there is no solution, other than to write tons of checks around each moment creation.
You can also try to pass the variables directly to moment, because using moment(new Date(...)) means you pick the bugs of Date on the way.

Thanks for clarification, I guess this is resolved till 21 March 2019 when this issue can show it again.

I have same problem too. Chrome and Safari shows different times. Do you guys have any solution?

This is an ongoing problem with dates and Safari both on desktop and on mobile. Unfortunately all browsers on iOS use Safari as an underlying platform, so they're all broken because Safari is.


Exit code is 0 on failed builds

Never mind...

I'm pretty sure this was an actual issue, and I'm not pushing a fix which will be published in 0.6.1 (hopefully today)

Fix published.


How to import dependencies which are not available in npm registry

I was deploying some contracts written on solidity for EVM on tron. I changed all the things that were needed for the file to compile. But i was unable to download some dependencies which are not available on npm like
import { ClonesWithImmutableArgs } from<EMAIL_ADDRESS>import { Bytes32AddressLib } from<EMAIL_ADDRESS>Since the above contracts are not deployed on TVM, should i deploy, download and use them in a relative path?

Of course, you can write the code directly in the source code file.

If you have source files, you can store them in the same directory. Import these files like the following.
import { ClonesWithImmutableArgs } from "./ClonesWithImmutableArgs.sol"
import { Bytes32AddressLib } from "./Bytes32AddressLib.sol"

Thanks a lot , this solved the issue.


Add SimpleLogin to mail software list

Project URL

https://github.com/simple-login/
https://simplelogin.io
Category

Mail
Description

Open source email alias solution to protect your email address
Why it should be included to Awesome macOS open source applications  (optional)
The project is 100% open source: the back-end, Mac app (Safari extension) and Chrome/Firefox extensions are open source.
Checklist

[X ] Edit applications.json instead of README.md.
[ X] Only one project/change is in this pull request
[ X] Screenshots(s) added if any
[ X] Has a commit from less than 2 years ago
[ X] Has a clear README in English

          1 Warning

:warning:
Found 1 link issue, a project collaborator will take care of these, thanks :)

Link issue by awesome_bot

Line
Status
Link

7764
404
https://raw.githubusercontent.com/AlexPerathoner/SlimHUD/master/IconFull.png

  Generated by :no_entry_sign: Danger

@nguyenkims Thank you 👍


Fix csrf error on admin page

Purpose
When trying to login to the Django admin site, we get a CSRF 403 error page:

Proposal

Fix CSRF_TRUSTED_ORIGINS setting in Development environment
set the security key via the environment variable and not in the setting file

@kernicPanel : Hello
I think we have always the probleme.
With our deployement I ve this error .

Hi @Moustique82
Did the DJANGO_CSRF_TRUSTED_ORIGINS environment variable match your actual url ?

merci @kernicPanel

In the settings.py, localhost is configured I tried to change by CSRF_TRUSTED_ORIGINS = ["https://url_magnify:8070"] but I ve the same result


AutoDisposeStreamProvider rebuilds the widget tree and reinvoces itself endlessly.

Describe the bug
Every time AutoDisposeStreamProvider  emits a value, my widget tree is rebuilt and AutoDisposeStreamProvider is invoked again.
Resulting in endless  recursive AutoDisposeStreamProvider invocation.
To Reproduce
I have the follwoing provider:
  AutoDisposeStreamProvider<QuestionsDto> getQuestionsList(int questionCount) {
    return StreamProvider.autoDispose<QuestionsDto>((ref) {
      return _mGetQuestionListUseCase.call(questionCount);
    });
  }

It uses the follwoing repo:
class QuestionsRepositoryImpl extends QuestionsRepository {
  late QuestionsRetrofitService _mQuestionsRetrofitService;

  QuestionsRepositoryImpl(QuestionsRetrofitService retrofitService) {
    _mQuestionsRetrofitService = retrofitService;
  }

  @override
  Stream<QuestionsDto> getQuestions(int recordsCount) {
    return Stream.fromFuture(_mQuestionsRetrofitService.getQuestions(recordsCount, "view")).asyncMap((value) {
      return QuestionsToQuestionsDtoTransformer().transform(value);
    });
  }
}

Them I am watching this provider in my widget tree like this:
  @override
  Widget build(BuildContext context, WidgetRef ref) {
    AsyncValue<QuestionsDto> response = ref.watch(_mViewModel.getQuestionsList(1)); //<-----------

    return Container(
        width: MediaQuery.of(context).size.width,
        child: Stack(
          children: [
            //background
            LayoutBuilder(builder: (BuildContext context, BoxConstraints constraints) {
              return Container(height: constraints.maxHeight, color: QuizTimeColors.background_purple);
            }),
            response.when(data: (data) { //<-----------
              return getDataWidget(ref);
            }, error: (stack, error) {
              return Text("");
            }, loading: () {
              return Text("");
            })
          ],
        ));
  }

Expected behavior
I have expected that the AutoDispose StreamProvider will be invoked once and thats it.
It feels like I am just using something wrong, if so please, point me into the right direction.

You're misusing providers. Providers should be global finals, not obtained from functions
Something like getQuestionsList is not reasonable and is the cause of your problem (since you're effectively creating a new provider everytimes).
Instead make a global variable


Improved testing options

Improved version of #286
Changes:

Allows you to run: npm run test:e2e -- --browser=chrome --metric=TTFB for example to limit tests to a particular browser and/or metric.
Adds a precommit test for any stray it.only's, depends.only's, or browser.debug's accidentally left around while testing.
Adds instructions to contributing file.
Moves Code of Conduct and Contributing files to more commonly known locations to make them easier to find.

@tunetheweb I made a few tweaks to the code that I thought make things a bit clearer. Let me know if you have any issues with these changes, otherwise feel free to merge.

@philipwalton , I'll see your one array and raise you some more :-)

I also added a unit test GitHub action.
I tried the e2e test but couldn't get it working. Even restricting it to Chrome required a number of extra options ( args: ['headless', 'disable-gpu', 'remote-debugging-pipe'],) and still fails CLS tests (though the others pass). Let's leave for now and might revisit later. Apparently it can be a bit flakey anyway, plus our tests are a little flakey themselves, so maybe not a good fit for CI.

@philipwalton happy to merge? Or wanna have one last look after latest changes?


Limits on rotations when combining EPIs?

Inspired while thinking about #297: for SyN-SDC in fMRIPrep, we collate BOLD series based on their effective echo spacing/total readout time and phase-encoding direction. If you consider cases where subjects adjust their heads between runs or leave the scanner, it seems like there is potential to have significantly different distortion profiles.
Consider a case where in session 1, the subject's head is rotated ~15deg to the left of plumb about the vertical axis (in the axial plane), and ~15deg to the right in session 2. You would now have a 30deg difference in the direction of susceptibility artifacts between the two scans. An average EPI reference would increase noise, rather than reduce it. Rotations about the transverse axis will also impact the distortion.
If this reasoning is correct, it's possible that this is responsible for some SyN-SDC artifacts in multi-run datasets. I will be testing a multi-run dataset on a per-run basis (via the expedient of just changing the TRT because it doesn't matter).
If this is the case, perhaps the "correct" solution is to estimate the fieldmap in T1 space and average that across BOLD images, rather than averaging the BOLD references and estimating the fieldmap. A compromise for efficiency could be to estimate the alignment between BOLD references and cluster images that are sufficiently close together.

Per meeting, try to get wrangler to generate 1 fieldmap per BOLD. If this works, get it into 2.2.0


PgSync detects changes but does not trigger building ElasticSearch indices until restart

PGSync version: master: 454d5cf0d51db440246643098b2603d59f64e3a1
Postgres version: debezium/postgres:13-alpine
Elasticsearch version: elasticsearch:7.13.4
Redis version: redis:6.2.4-alpine3.14
Python version: python:3.7
Problem Description: PgSync detects changes but does not trigger building ElasticSearch indices until restart of pgsync when running in daemon mode. Behavior as such, everything startups up fine, pgsync logs the usual message about polling 0, then I do a large insert of about 45k entries into a table that pgsync is watching, it detects the changes and I get the following output, it then stays stuck with the polling response now with ~45k detected, but the indices are never built even after wait for hours, haven't yet tried days. If I simply restart the pgsync portion of the docker app, when it comes back up it appears to appropriately kick off the sync and data shows up in elasticsearch to be queried:
pgsync         | Polling db redactedb: 0 item(s)
pgsync         | Polling db redactedb: 0 item(s)
pgsync         | Polling db redactedb: 0 item(s)
pgsync         | Polling db redactedb: 0 item(s)
pgsync         | Polling db redactedb: 0 item(s)
pgsync         | Polling db redactedb: 0 item(s)
redactedservice| Updates are triggered to start here....
pgsync         | Polling db redactedb: 1 item(s)
pgsync         | Polling db redactedb: 1 item(s)
pgsync         | Polling db redactedb: 1 item(s)
pgsync         | Polling db redactedb: 1 item(s)
pgsync         | Polling db redactedb: 1 item(s)
pgsync         | Polling db redactedb: 1 item(s)
pgsync         | Polling db redactedb: 1 item(s)
pgsync         | Polling db redactedb: 1 item(s)
pgsync         | Polling db redactedb: 1 item(s)
pgsync         | Polling db redactedb: 1 item(s)
pgsync         | Polling db redactedb: 1 item(s)
pgsync         | Polling db redactedb: 1 item(s)
pgsync         | Polling db redactedb: 1 item(s)
pgsync         | Polling db redactedb: 1 item(s)
redactedservice| Updates happen here - Done!
redis          | 1:M 23 Jul 2021 20:09:42.016 * 10000 changes in 60 seconds. Saving...
redis          | 1:M 23 Jul 2021 20:09:42.017 * Background saving started by pid 14
redis          | 14:C 23 Jul 2021 20:09:42.026 * DB saved on disk
redis          | 14:C 23 Jul 2021 20:09:42.026 * RDB: 0 MB of memory used by copy-on-write
redis          | 1:M 23 Jul 2021 20:09:42.117 * Background saving terminated with success
pgsync | Polling db redacteddb: 44,284 item(s)
pgsync | Polling db redacteddb: 44,284 item(s)
pgsync | Polling db redacteddb: 44,284 item(s)
pgsync | Polling db redacteddb: 44,284 item(s)
pgsync | Polling db redacteddb: 44,284 item(s)
pgsync | Polling db redacteddb: 44,284 item(s)
pgsync | Polling db redacteddb: 44,284 item(s)
pgsync | Polling db redacteddb: 44,284 item(s)
pgsync | Polling db redacteddb: 44,284 item(s)
pgsync | Polling db redacteddb: 44,284 item(s)
pgsync | Polling db redacteddb: 44,284 item(s)
pgsync | Polling db redacteddb: 44,284 item(s)
pgsync | Polling db redacteddb: 44,284 item(s)
pgsync | Polling db redacteddb: 44,284 item(s)
pgsync | Polling db redacteddb: 44,284 item(s)
postgres | 2021-07-23 20:32:06.740 GMT [61] LOG: starting logical decoding for slot "redacteddb_redactedindex1"
postgres | 2021-07-23 20:32:06.740 GMT [61] DETAIL: Streaming transactions committing after 0/24E12C8, reading WAL from 0/24E1290.
postgres | 2021-07-23 20:32:06.740 GMT [61] STATEMENT: SELECT xid, data
postgres | FROM PG_LOGICAL_SLOT_GET_CHANGES('redacteddb_redactedindex1', NULL, NULL)
postgres | 2021-07-23 20:32:06.741 GMT [61] LOG: logical decoding found consistent point at 0/24E1290
postgres | 2021-07-23 20:32:06.741 GMT [61] DETAIL: There are no running transactions.
postgres | 2021-07-23 20:32:06.741 GMT [61] STATEMENT: SELECT xid, data
postgres | FROM PG_LOGICAL_SLOT_GET_CHANGES('redacteddb_redactedindex1', NULL, NULL)
pgsync | Polling db redacteddb: 44,284 item(s)
pgsync | Polling db redacteddb: 44,284 item(s)
postgres | 2021-07-23 20:32:07.445 GMT [63] LOG: starting logical decoding for slot "redacteddb_redactedindex2"
postgres | 2021-07-23 20:32:07.445 GMT [63] DETAIL: Streaming transactions committing after 0/24E12C8, reading WAL from 0/24E1290.
postgres | 2021-07-23 20:32:07.445 GMT [63] STATEMENT: SELECT xid, data
postgres | FROM PG_LOGICAL_SLOT_GET_CHANGES('redacteddb_redactedindex2', NULL, NULL)
postgres | 2021-07-23 20:32:07.445 GMT [63] LOG: logical decoding found consistent point at 0/24E1290
postgres | 2021-07-23 20:32:07.445 GMT [63] DETAIL: There are no running transactions.
postgres | 2021-07-23 20:32:07.445 GMT [63] STATEMENT: SELECT xid, data
postgres | FROM PG_LOGICAL_SLOT_GET_CHANGES('redacteddb_redactedindex2', NULL, NULL)
pgsync | Polling db redacteddb: 44,284 item(s)
pgsync | Polling db redacteddb: 44,284 item(s)
pgsync | Polling db redacteddb: 44,284 item(s)
pgsync | Polling db redacteddb: 44,284 item(s)
pgsync | Polling db redacteddb: 44,284 item(s)
pgsync | Polling db redacteddb: 44,284 item(s)
pgsync | Polling db redacteddb: 44,284 item(s)
pgsync | Polling db redacteddb: 44,284 item(s)
pgsync | Polling db redacteddb: 44,284 item(s)
pgsync | Polling db redacteddb: 44,284 item(s)
pgsync | Polling db redacteddb: 44,284 item(s)

promptly after restart:
postgres | 2021-07-23 20:38:47.579 GMT [159] LOG: incomplete startup packet
postgres | 2021-07-23 20:38:49.857 GMT [160] LOG: logical decoding found consistent point at 0/251D408
postgres | 2021-07-23 20:38:49.857 GMT [160] DETAIL: There are no running transactions.
postgres | 2021-07-23 20:38:49.857 GMT [160] STATEMENT: SELECT *
postgres | FROM PG_CREATE_LOGICAL_REPLICATION_SLOT('redacteddb_redactedindex1', 'test_decoding')
postgres | 2021-07-23 20:38:51.799 GMT [162] LOG: logical decoding found consistent point at 0/2528918
postgres | 2021-07-23 20:38:51.799 GMT [162] DETAIL: There are no running transactions.
postgres | 2021-07-23 20:38:51.799 GMT [162] STATEMENT: SELECT *
postgres | FROM PG_CREATE_LOGICAL_REPLICATION_SLOT('redacteddb_redactedindex2', 'test_decoding')
postgres | 2021-07-23 20:38:52.572 GMT [163] LOG: starting logical decoding for slot "redacteddb_redactedindex1"
postgres | 2021-07-23 20:38:52.572 GMT [163] DETAIL: Streaming transactions committing after 0/251D440, reading WAL from 0/251D408.
postgres | 2021-07-23 20:38:52.572 GMT [163] STATEMENT: SELECT xid, data
postgres | FROM PG_LOGICAL_SLOT_PEEK_CHANGES('redacteddb_redactedindex1', NULL, NULL)
postgres | WHERE CAST(CAST(xid AS TEXT) AS BIGINT) < 579
postgres | 2021-07-23 20:38:52.572 GMT [163] LOG: logical decoding found consistent point at 0/251D408
postgres | 2021-07-23 20:38:52.572 GMT [163] DETAIL: There are no running transactions.
postgres | 2021-07-23 20:38:52.572 GMT [163] STATEMENT: SELECT xid, data
postgres | FROM PG_LOGICAL_SLOT_PEEK_CHANGES('redacteddb_redactedindex1', NULL, NULL)
postgres | WHERE CAST(CAST(xid AS TEXT) AS BIGINT) < 579
postgres | 2021-07-23 20:38:52.691 GMT [163] LOG: starting logical decoding for slot "redacteddb_redactedindex1"
postgres | 2021-07-23 20:38:52.691 GMT [163] DETAIL: Streaming transactions committing after 0/251D440, reading WAL from 0/251D408.
postgres | 2021-07-23 20:38:52.691 GMT [163] STATEMENT: SELECT xid, data
postgres | FROM PG_LOGICAL_SLOT_GET_CHANGES('redacteddb_redactedindex1', NULL, 18)
postgres | WHERE CAST(CAST(xid AS TEXT) AS BIGINT) < 579
postgres | 2021-07-23 20:38:52.691 GMT [163] LOG: logical decoding found consistent point at 0/251D408
postgres | 2021-07-23 20:38:52.691 GMT [163] DETAIL: There are no running transactions.
postgres | 2021-07-23 20:38:52.691 GMT [163] STATEMENT: SELECT xid, data
postgres | FROM PG_LOGICAL_SLOT_GET_CHANGES('redacteddb_redactedindex1', NULL, 18)
postgres | WHERE CAST(CAST(xid AS TEXT) AS BIGINT) < 579
postgres | 2021-07-23 20:38:52.808 GMT [164] LOG: starting logical decoding for slot "redacteddb_redactedindex1"
postgres | 2021-07-23 20:38:52.808 GMT [164] DETAIL: Streaming transactions committing after 0/2528918, reading WAL from 0/2528918.
postgres | 2021-07-23 20:38:52.808 GMT [164] STATEMENT: SELECT xid, data
postgres | FROM PG_LOGICAL_SLOT_PEEK_CHANGES('redacteddb_redactedindex1', NULL, NULL)
postgres | WHERE CAST(CAST(xid AS TEXT) AS BIGINT) >= 579 AND CAST(CAST(xid AS TEXT) AS BIGINT) < 580
postgres | 2021-07-23 20:38:52.808 GMT [164] LOG: logical decoding found consistent point at 0/2528918
postgres | 2021-07-23 20:38:52.808 GMT [164] DETAIL: There are no running transactions.
postgres | 2021-07-23 20:38:52.808 GMT [164] STATEMENT: SELECT xid, data
postgres | FROM PG_LOGICAL_SLOT_PEEK_CHANGES('redacteddb_redactedindex1', NULL, NULL)
postgres | WHERE CAST(CAST(xid AS TEXT) AS BIGINT) >= 579 AND CAST(CAST(xid AS TEXT) AS BIGINT) < 580
elasticsearch | {"type": "server", "timestamp": "2021-07-23T20:38:53,304Z", "level": "INFO", "component": "o.e.c.m.MetadataMappingService", "cluster.name": "docker-cluster", "node.name": "804f29411055", "message": "[redactedindex2/HXN-jJU5QEePidn7oU5Lsw] create_mapping [_doc]", "cluster.uuid": "HqmNm-uBTsS23OGbAMXOyw", "node.id": "jBomOdReSYe-pMcKI5gXcQ" }
postgres | 2021-07-23 20:38:55.084 GMT [165] LOG: starting logical decoding for slot "redacteddb_redactedindex2"
postgres | 2021-07-23 20:38:55.084 GMT [165] DETAIL: Streaming transactions committing after 0/2528950, reading WAL from 0/2528918.
postgres | 2021-07-23 20:38:55.084 GMT [165] STATEMENT: SELECT xid, data
postgres | FROM PG_LOGICAL_SLOT_PEEK_CHANGES('redacteddb_redactedindex2', NULL, NULL)
postgres | WHERE CAST(CAST(xid AS TEXT) AS BIGINT) < 581
postgres | 2021-07-23 20:38:55.084 GMT [165] LOG: logical decoding found consistent point at 0/2528918
postgres | 2021-07-23 20:38:55.084 GMT [165] DETAIL: There are no running transactions.
postgres | 2021-07-23 20:38:55.084 GMT [165] STATEMENT: SELECT xid, data
postgres | FROM PG_LOGICAL_SLOT_PEEK_CHANGES('redacteddb_redactedindex2', NULL, NULL)
postgres | WHERE CAST(CAST(xid AS TEXT) AS BIGINT) < 581
postgres | 2021-07-23 20:38:55.194 GMT [166] LOG: starting logical decoding for slot "redacteddb_redactedindex2"
postgres | 2021-07-23 20:38:55.194 GMT [166] DETAIL: Streaming transactions committing after 0/2528950, reading WAL from 0/2528918.
postgres | 2021-07-23 20:38:55.194 GMT [166] STATEMENT: SELECT xid, data
postgres | FROM PG_LOGICAL_SLOT_PEEK_CHANGES('redacteddb_redactedindex2', NULL, NULL)
postgres | WHERE CAST(CAST(xid AS TEXT) AS BIGINT) >= 581 AND CAST(CAST(xid AS TEXT) AS BIGINT) < 582
postgres | 2021-07-23 20:38:55.194 GMT [166] LOG: logical decoding found consistent point at 0/2528918
postgres | 2021-07-23 20:38:55.194 GMT [166] DETAIL: There are no running transactions.
postgres | 2021-07-23 20:38:55.194 GMT [166] STATEMENT: SELECT xid, data
postgres | FROM PG_LOGICAL_SLOT_PEEK_CHANGES('redacteddb_redactedindex2', NULL, NULL)
postgres | WHERE CAST(CAST(xid AS TEXT) AS BIGINT) >= 581 AND CAST(CAST(xid AS TEXT) AS BIGINT) < 582
redis | 1:M 23 Jul 2021 20:38:55.297 * 100 changes in 300 seconds. Saving...
redis | 1:M 23 Jul 2021 20:38:55.297 * Background saving started by pid 17
redis | 17:C 23 Jul 2021 20:38:55.310 * DB saved on disk
redis | 17:C 23 Jul 2021 20:38:55.310 * RDB: 0 MB of memory used by copy-on-write
redis | 1:M 23 Jul 2021 20:38:55.398 * Background saving terminated with success
redis | 1:M 23 Jul 2021 20:39:56.094 * 10000 changes in 60 seconds. Saving...
redis | 1:M 23 Jul 2021 20:39:56.095 * Background saving started by pid 18
redis | 18:C 23 Jul 2021 20:39:56.103 * DB saved on disk
redis | 18:C 23 Jul 2021 20:39:56.103 * RDB: 0 MB of memory used by copy-on-write
redis | 1:M 23 Jul 2021 20:39:56.196 * Background saving terminated with success

pysync/docker/runserver.sh modified to the following:
#! /bin/sh
./wait-for-it.sh postgres:5432 -t 60
./wait-for-it.sh elasticsearch:9200 -t 60
./wait-for-it.sh redis:6379 -t 60
bootstrap --config examples/redacted/schema.json
pgsync --config examples/redacted/schema.json --daemon

pgsync/examples/redacted/schema.json added:
[
{
"database": "redacteddb",
"index": "redactedindex1",
"nodes": {
"table": "redactedtable1",
"schema": "redactedschema1",
"columns": [
"id",
"value"
]
}
},
{
"database": "redacteddb",
"index": "redactedindex2",
"nodes": {
"table": "redactedtable2",
"schema": "redactedschema1",
"columns": [
"id",
"description"
]
}
}
]

pgsync/examples/redacted/schema.py added:
import json
from datetime import datetime
import click
import sqlalchemy as sa
from sqlalchemy.ext.declarative import declarative_base
from sqlalchemy.schema import UniqueConstraint
from pgsync.base import create_database, pg_engine
from pgsync.helper import teardown
from pgsync.utils import get_config
@click.command()
@click.option(
"--config",
"-c",
help="Schema config",
type=click.Path(exists=True),
)
def main(config):
config = get_config(config)
teardown(config=config)

if name == "main":
main()

docker-compose.yml snippet:
postgres:
container_name: postgres
networks:
redacted_net:
build:
context: ../.
dockerfile: Postgres.production.dockerfile
ports:
- "5433:5432"
environment:
- POSTGRES_USER=redacted-user
- POSTGRES_PASSWORD=redacted-pw
- POSTGRES_DB=redacteddb
restart: on-failure
redis:
container_name: redis
networks:
redacted_net:
image: redis:6.2.4-alpine3.14
command: redis-server --requirepass PLEASE_CHANGE_ME
elasticsearch:
container_name: elasticsearch
networks:
redacted_net:
image: elasticsearch:7.13.4
ports:
- "9201:9200"
- "9301:9300"
environment:
- xpack.security.enabled=false
- network.host=<IP_ADDRESS>
- http.host=<IP_ADDRESS>
pgsync:
container_name: pgsync
networks:
redacted_net:
build:
context: ../pgsync/.
dockerfile: Dockerfile
command: ./runserver.sh
sysctls:
- net.ipv4.tcp_keepalive_time=200
- net.ipv4.tcp_keepalive_intvl=200
- net.ipv4.tcp_keepalive_probes=5
labels:
org.label-schema.name: "pgsync"
org.label-schema.description: "Postgres to elasticsearch sync"
com.label-schema.service-type: "daemon"
depends_on:
- postgres
- redis
- elasticsearch
environment:
- PG_USER=redacted-user
- PG_HOST=postgres
- PG_PASSWORD=redacted-pw
- LOG_LEVEL=INFO
- ELASTICSEARCH_PORT=9200
- ELASTICSEARCH_SCHEME=http
- ELASTICSEARCH_HOST=elasticsearch
- REDIS_HOST=redis
- REDIS_AUTH=PLEASE_CHANGE_ME
Error Message (if any):

The log seems to indicate changes were propagated to Elasticsearch.
Can you provide more details of an event that was added to the database but not synced to Elasticsearch?
You can also run the daemon in verbose mode with -v

I had the same issue, at first when I ran pgsync it would sync the docs to elasticsearch but no further changes would be pushed to elasticsearch in daemon mode, what I did wrong is that I didn't had a primary key in the table before and after installing and configuring pgsync I added the primary key to the table, So after creating a new table and giving it a primary key at the time of creation solve my issue!


Apply patch for SHIRO-435

Applied the suggested patch for SHIRO-435, after verifying it in a proprietary project.
According to Pierre-Alexandre Meyer, it has also been verified in Kill Bill.

Nice! thanks!


Maybe a HTTP client channel should advise on questionable recv patterns

Say a revc pattern for an HTTP client references statusCode instead of statuscode, which is what's used. Maybe the channel should issue a (runtime) warning -- with some option to suppress those warnings?

I like that idea.

See #52.


interval "once"?

I try to deploy some small apps with caddy git, but it shouldn't updated automatically. Just should clone the current git repo during deployment.
Could you add an interval "once" option instead of the time in seconds?

What I'll do instead for now is allow 0 or -1 for interval to indicate never.
A workaround is a very long time or specify a hook url.

So 0 or -1 should work with initial clone Düring Start?
Would be fine for me!
Haven't take a look at hook URL, could also work...

Done. interval -1 disables periodic pull.

Thanks!  :)


Rule W605 cause panic

ruff 0.3.3
(latest changes from main branch)
ruff  *.py --select W605 --no-cache --fix --unsafe-fixes --preview --output-format concise --isolated

file content:
cmd = f"""
GRANT ALL PRIVILEGES ON SCHEMA api TO {kwollect_user};
    req += "\\n" \
  params      JSONB             DEFAULT '{{}}'
    CASE WHEN metrics.device_id ~ '^[a-z+-\d+$' THEN '1' ELSE '2' END AS idx1,
"""

error
All checks passed!

error: Panicked while linting /opt/tmp_folder/11322743460824035852.py: This indicates a bug in Ruff. If you could open an issue at:

    https://github.com/astral-sh/ruff/issues/new?title=%5BLinter%20panic%5D

...with the relevant file contents, the `pyproject.toml` settings, and the following stack trace, we'd be very appreciative!

panicked at /home/runner/work/Automated-Fuzzer/Automated-Fuzzer/ruff/crates/ruff_source_file/src/locator.rs:463:23:
byte index 173 is not a char boundary; it is inside '\u{9f}' (bytes 172..174) of `cmd = f"""
GRANT ALL PRIVILEGES ON SCHEMA api TO {kwollect_user};
    req += "\\n" \
  params      JSONB             DEFAULT '{{}}'
    CASE WHEN metrics.device_id ~ '^[a-z\+\\-\d+$' THEN '1' ELSE '2' END AS idx1,
"""`
Backtrace:    0: ruff::panic::catch_unwind::{{closure}}
             at ./ruff/crates/ruff/src/panic.rs:31:25
   1: <alloc::boxed::Box<F,A> as core::ops::function::Fn<Args>>::call
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/alloc/src/boxed.rs:2029:9
   2: std::panicking::rust_panic_with_hook
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/panicking.rs:783:13
   3: std::panicking::begin_panic_handler::{{closure}}
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/panicking.rs:657:13
   4: std::sys_common::backtrace::__rust_end_short_backtrace
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/sys_common/backtrace.rs:171:18
   5: rust_begin_unwind
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/panicking.rs:645:5
   6: core::panicking::panic_fmt
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/core/src/panicking.rs:72:14
   7: core::str::slice_error_fail_rt
   8: core::str::slice_error_fail
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/core/src/str/mod.rs:88:9
   9: core::str::traits::<impl core::slice::index::SliceIndex<str> for core::ops::range::Range<usize>>::index
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/core/src/str/traits.rs:231:21
  10: core::str::traits::<impl core::ops::index::Index<I> for str>::index
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/core/src/str/traits.rs:61:15
  11: ruff_text_size::range::<impl core::ops::index::Index<ruff_text_size::range::TextRange> for str>::index
             at ./ruff/crates/ruff_text_size/src/range.rs:430:14
  12: ruff_source_file::locator::Locator::slice
             at ./ruff/crates/ruff_source_file/src/locator.rs:463:23
  13: ruff_linter::fix::apply_fixes
             at ./ruff/crates/ruff_linter/src/fix/mod.rs:98:25
  14: ruff_linter::fix::fix_file
             at ./ruff/crates/ruff_linter/src/fix/mod.rs:48:14
  15: ruff_linter::linter::lint_fix
             at ./ruff/crates/ruff_linter/src/linter.rs:580:14
  16: ruff::diagnostics::lint_path
             at ./ruff/crates/ruff/src/diagnostics.rs:280:14
  17: ruff::commands::check::lint_path::{{closure}}
             at ./ruff/crates/ruff/src/commands/check.rs:194:9
  18: std::panicking::try::do_call
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/panicking.rs:552:40
  19: std::panicking::try
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/panicking.rs:516:19
  20: std::panic::catch_unwind
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/panic.rs:142:14
  21: ruff::panic::catch_unwind
             at ./ruff/crates/ruff/src/panic.rs:40:18
  22: ruff::commands::check::lint_path
             at ./ruff/crates/ruff/src/commands/check.rs:193:18
  23: ruff::commands::check::check::{{closure}}
             at ./ruff/crates/ruff/src/commands/check.rs:94:17
  24: <rayon::iter::filter_map::FilterMapFolder<C,P> as rayon::iter::plumbing::Folder<T>>::consume
             at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-1.9.0/src/iter/filter_map.rs:123:36
  25: rayon::iter::plumbing::Folder::consume_iter
             at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-1.9.0/src/iter/plumbing/mod.rs:179:20
  26: rayon::iter::plumbing::Producer::fold_with
             at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-1.9.0/src/iter/plumbing/mod.rs:110:9
  27: rayon::iter::plumbing::bridge_producer_consumer::helper
             at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-1.9.0/src/iter/plumbing/mod.rs:438:13
  28: rayon::iter::plumbing::bridge_producer_consumer
             at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-1.9.0/src/iter/plumbing/mod.rs:397:12
  29: <rayon::iter::plumbing::bridge::Callback<C> as rayon::iter::plumbing::ProducerCallback<I>>::callback
             at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-1.9.0/src/iter/plumbing/mod.rs:373:13
  30: <rayon::slice::Iter<T> as rayon::iter::IndexedParallelIterator>::with_producer
             at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-1.9.0/src/slice/mod.rs:777:9
  31: rayon::iter::plumbing::bridge
             at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-1.9.0/src/iter/plumbing/mod.rs:357:12
  32: <rayon::slice::Iter<T> as rayon::iter::ParallelIterator>::drive_unindexed
             at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-1.9.0/src/slice/mod.rs:753:9
  33: <rayon::iter::filter_map::FilterMap<I,P> as rayon::iter::ParallelIterator>::drive_unindexed
             at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-1.9.0/src/iter/filter_map.rs:46:9
  34: <rayon::iter::fold::Fold<I,ID,F> as rayon::iter::ParallelIterator>::drive_unindexed
             at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-1.9.0/src/iter/fold.rs:59:9
  35: rayon::iter::reduce::reduce
             at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-1.9.0/src/iter/reduce.rs:15:5
  36: rayon::iter::ParallelIterator::reduce
             at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-1.9.0/src/iter/mod.rs:998:9
  37: ruff::commands::check::check
             at ./ruff/crates/ruff/src/commands/check.rs:165:10
  38: ruff::check
             at ./ruff/crates/ruff/src/lib.rs:409:13
  39: ruff::run
             at ./ruff/crates/ruff/src/lib.rs:191:33
  40: ruff::main
             at ./ruff/crates/ruff/src/main.rs:65:11
  41: core::ops::function::FnOnce::call_once
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/core/src/ops/function.rs:250:5
  42: std::sys_common::backtrace::__rust_begin_short_backtrace
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/sys_common/backtrace.rs:155:18
  43: std::rt::lang_start::{{closure}}
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/rt.rs:166:18
  44: core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/core/src/ops/function.rs:284:13
  45: std::panicking::try::do_call
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/panicking.rs:552:40
  46: std::panicking::try
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/panicking.rs:516:19
  47: std::panic::catch_unwind
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/panic.rs:142:14
  48: std::rt::lang_start_internal::{{closure}}
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/rt.rs:148:48
  49: std::panicking::try::do_call
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/panicking.rs:552:40
  50: std::panicking::try
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/panicking.rs:516:19
  51: std::panic::catch_unwind
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/panic.rs:142:14
  52: std::rt::lang_start_internal
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/rt.rs:148:20
  53: main
  54: <unknown>
  55: __libc_start_main
  56: _start

python_compressed.zip

Probably this is due to {{}} being normalized to {} in lex_fstring_middle_or_end which is inside crates/ruff_python_parser/src/lexer.rs, which causes the range defined in crates/ruff_linter/src/rules/pycodestyle/rules/invalid_escape_sequence.rs:175 to deviate from the actual range in the content.
This seems to put a wrong diagnostic.
I'm now thinking of adding new token which matches only {{ inside f-string, but will there be better options?

@dhruvmanila any chance this is fixed in the new parser. I'm asking because you made some changes to string lexing/parsing

No, this isn't fixed in the new parser. Although I might know why the problem is occurring. I'll need to look at the W605 rule and string parsing.
A minimal way to reproduce this is using the following code:
# The curly brace escape is important
f"{{}}+-\d"

And running it using:
$ cargo run -- check --select W605 --no-cache --preview --output-format full --isolated ~/playground/ruff/src/play.py
/Users/dhruv/playground/ruff/src/play.py:1:7: W605 [*] Invalid escape sequence: `\d`
  |
1 | f"{{}}+-\d"
  |       ^^ W605
  |
  = help: Use a raw string literal

Found 1 error.
[*] 1 fixable with the `--fix` option.

As you can see, the highlighted range is incorrect.
This creates other errors like for example if there's a newline in the string, which is a valid escape sequence, the fix can't be to prefix the f-string with r but instead to escape the invalid sequence. This leads to an invalid fix:
$ cargo run -- check --select W605 --fix --diff --no-cache --preview --output-format full --isolated ~/playground/ruff/src/play.py
--- /Users/dhruv/playground/ruff/src/play.py
+++ /Users/dhruv/playground/ruff/src/play.py
@@ -1 +1 @@
-f"\n{{}}+-\d+"
+f"\n{{}\}\+\\\-\d+"

Would fix 5 errors.

And, when you include the weird character in the mix, you get the panic:
f"\n{{}}�+-\d+"

And, we can even reproduce it in a way that the fix never converges.

I can look at it tonight.


[IoT] Track 2 SDK updates for DPS and IoT Central

Description

Update SDKs for IoT Central and IoT Device Provisioning Service to track 2.
This also bumps the API-version for DPS from 2018-01-22 to 2020-03-01
Testing Guide

History Notes

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

IoT

@yonzhan / @zhoxing-ms  just a heads up - this is an initial PR just to get our track 2 changes going, we're waiting on some new stable api-version SDK updates for DPS and Hub in order to add a few more changes to this PR

@c-ryan-k Thanks for the update. Please let us know when the PR is ready for review

@c-ryan-k, is this PR ready for review?

@jsntcy sorry this one's gonna get split up into two different PRs  - our SDKs aren't quite ready yet for the features this update will support - I'll close this for now and have a new PR later. Apologies for letting it sit.

@c-ryan-k, so you will create a PR only for track 2 migration?


Injecting the provenance resource when it is missing

This PR adds a provenance resource when one is missing as well as sets the processing mode filter to evaluate to true so that the sample message for Connectathon can be processed as is.
If you are suggesting a fix for a currently exploitable issue, please disclose the issue to the prime-reportstream team directly outside of GitHub instead of filing a PR, so we may immediately patch the affected systems before a disclosure. See SECURITY.md/Reporting a Vulnerability for more information.
Test Steps:

Navigate to http://build.fhir.org/ig/HL7/home-lab-report/Bundle-bundle-at-home-in-vitro-test-results-p-noelle.json.html to get the test message
Update the state in the message to be IG
Send the message through /reports
Check that the message is sent to an organization via /waters/report/<insert_id_here>/history

Changes

Add the provenance resource when it is missing from the message
Set the processing mode filter to something that will make it evaluate to true.

Checklist
Testing

[x] Tested locally?
[x] Ran ./prime test or ./gradlew testSmoke against local Docker ReportStream container?
[ ] (For Changes to /frontend-react/...) Ran npm run lint:write?
[ ] Added tests?

Process

[ ] Are there licensing issues with any new dependencies introduced?
[ ] Includes a summary of what a code reviewer should test/verify?
[ ] Updated the release notes?
[ ] Database changes are submitted as a separate PR?
[ ] DevOps team has been notified if PR requires ops support?

Linked Issues

Fixes #9125

To Be Done
Create GitHub issues to track the work remaining, if any

#issue

Specific Security-related subjects a reviewer should pay specific attention to

Does this PR introduce new endpoints?

new endpoint A
new endpoint B

Does this PR include changes in authentication and/or authorization of existing endpoints?
Does this change introduce new dependencies that need vetting?
Does this change require changes to our infrastructure?
Does logging contain sensitive data?
Does this PR include or remove any sensitive information itself?

If you answered 'yes' to any of the questions above, conduct a detailed Review that addresses at least:

What are the potential security threats and mitigations? Please list the STRIDE threats and how they are mitigated

Spoofing (faking authenticity)

Threat T, which could be achieved by A, is mitigated by M

Tampering (influence or sabotage the integrity of information, data, or system)
Repudiation (the ability to dispute the origin or originator of an action)
Information disclosure (data made available to entities who should not have it)
Denial of service (make a resource unavailable)
Elevation of Privilege (reduce restrictions that apply or gain privileges one should not have)

Have you ensured logging does not contain sensitive data?
Have you received any additional approvals needed for this change?

Hmm, I think we should aim to merge this with master. The reason this isn't on master yet is because its not a problem, for now, since we don't support sending FHIR. However, with the completion of #9261, master branch will support sending FHIR,  and so this should go to master as well?

Hmm, I think we should aim to merge this with master. The reason this isn't on master yet is because its not a problem, for now, since we don't support sending FHIR. However, with the completion of #9261, master branch will support sending FHIR, and so this should go to master as well?

Should I maybe split this into two PRs then? One that will add the provenance and unit testing. The other that will go to the connectathon branch and update the organizations.yml file since it seems like we are using the ignore org? Or are we not planning to use the ignore org for the connectathon @arnejduranovic ?

Moving this PR to draft until I get it ready for a master branch change rather than a quick connectathon change.

Just as a follow up, discussed with Arnej and decided we were not creating a tech debt ticket. Tests are updated.


modify docker to start kafka and add kafka test

I modified the docker setup to start kafka in the same container as zookeeper.  (Putting them in separate containers adds a lot of complication and doesn't seem to add any value.)
I've added a test that uses the kafka firehose. It starts an indexing task using serverTime, sends some data using current timestamps, and verifies some queries.
I added a getKafkaHost() function to the configuration classes.
We have a test environment that uses multiple hosts, with zookeeper running on its own host.  When we ran integration tests there that use druid's service discovery code to find a realtime port, the port wasn't being found because service discovery was seeing localhost instead of the actual host as the zookeeper address.  To get around this, we bound CuratorConfig to a new class IntegrationTestingCuratorConfig that overrides getZkHosts() with a function that gets the zookeeper address from the config file.

LGTM

taken care of by https://github.com/druid-io/druid/pull/1859

@rasahner can this be closed then?


Created new 0.4.0 tag

Coverage decreased (-0.02%) to 28.59% when pulling 83149f709fd9d0cde0261b3f7a63a47450309d14 on tanchik194:master into 71a0583f1935b484c7b711f632f353c28791d3e8 on nixsolutions:master.


Getting a wrong Essence SampleRate Error for Interlaced ProRes content

For ProRes MXF files the edit rate is not doubled in case of interlaced in contrast to J2k material. This has to do with the fact that the fields are stored together in ProRes and separately in J2K.
CPL_0.txt

Duplication of #369


Where to take this project: direction, thoughts, proposals

Following the recommendation in https://github.com/python/typeshed/issues/1702#issuecomment-340888642 of:

I actually recommend waiting for PEP 561 and its implementation. Having incomplete stubs in typeshed (which I presume the machinalis stubs are) is worse than no stubs, as we've found out with some other packages (sqlalchemy was actually withdrawn for this reason).

I think we need to orientate the development of this repository specifically around how PEP 561 will work and whatever work flow is necessary to support that integration.
There are some notes around this on the mypy documentation:

https://mypy.readthedocs.io/en/latest/installed_packages.html#making-pep-561-compatible-packages

I see no existing ticket regarding adding type hints on the Django tracker:

https://code.djangoproject.com/search?q=type+hints&noquickjump=1&changeset=on&milestone=on&ticket=on&wiki=on

It probably makes sense to drop a mail on the dev list to see where we can coordinate.
Open to any thoughts!
I can put an hour or two each week and use Django in my day to day work, so I would definitely like to have access to the type hint system going forward. It's also a way to give back to the Django community which really has got me a long way so far ...

Here's some discussions from the Django development mailing list:

https://groups.google.com/forum/#!searchin/django-developers/type$20hint|sort:date/django-developers/s5yW3kt5JEA/POgy8coxBAAJ
https://groups.google.com/forum/#!searchin/django-developers/type$20hint|sort:date/django-developers/trTEbURFhEY/H3WsHV5pDgAJ

Oh, right, it seems someone has already started to do this:

https://www.djangoproject.com/weblog/2016/jun/30/pycharm-and-django-fundraiser/

However, I then saw this:

The JetBrains announcement that they want to fund the project isn't a guarantee that it'll be implemented. The feature needs to go through the normal feature acceptance process, which as Markus said, might involve a DEP.
Assuming the idea is accepted, my sense on timing would be to wait until January when Django drops support for Python 2.7 and 3.4 in master. Then we could use inline annotations rather than the stub files.
Past discussions of type hinting:
https://groups.google.com/d/topic/django-developers/z_P1TvJ6QG8/discussion
https://groups.google.com/d/topic/django-developers/xOTmq93YZuQ/discussion

It seems others were waiting for PEP 561 as well.
I'll create a new mail on the development list and see what kind of traction it gets.

Just fired a mail at https://groups.google.com/forum/#!forum/django-developers.
Hasn't appeared just yet but should at some point. Hopefully discussion moves along there.

Closing off, things have moved along, we're moving along at:

https://github.com/TypedDjango/django-stubs#django-stubs


Vertically shard queries by le if no histogram_quantile function

[ ] I added CHANGELOG entry for this change.
[x] Change is not relevant to the end user.

Changes
We currently exclude le as a sharding label at all.
However, le can still be used as a sharding label if the query is like sum by (le) (xxxxx), when there is no histogram_quantile function left.
Verification

Thanks! @MichaHoffmann


单智能体聊天，回复的答案会被后面的内容覆盖，导致输出的内容不完整

Search before asking

[X] I had searched in the issues and found no similar issues.

Operating system information
Windows
Python version information

=3.11

DB-GPT version
main
Related scenes

[ ] Chat Data
[ ] Chat Excel
[ ] Chat DB
[ ] Chat Knowledge
[ ] Model Management
[ ] Dashboard
[ ] Plugins

Installation Information

[ ] Installation From Source

[ ] Docker Installation

[ ] Docker Compose Installation

[ ] Cluster Installation

[ ] AutoDL Image

[ ] Other

Device information
cpu
Models information
deepseek
What happened

自定义单智能体应用，答案输出只保留最后内容输出
What you expected to happen
完整的答案内容
How to reproduce
创建单智能体应用，聊天
Additional context
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

yeah, it's a prompt problem, you can define your prompt by yourself


Sb sync layer reorg stable sync 2

What ❔

Why ❔

Checklist

[ ] PR title corresponds to the body of PR (we generate changelog entries from PRs).
[ ] Tests for the changes have been added / updated.
[ ] Documentation comments have been added / updated.

The Ci already passed during review of the same PR.+ it was approved by @kelemeno , so merging


Improve HexFormatter scan command

scan -fi org.apache.accumulo.core.util.format.HexFormatter -r 313c
is confusing and too long... make it do this:
scan -hex

Although this might help the hex formatting case... we probably shouldn't design around a single use case. We have to look at the entire configuration space. Lots of little "convenience options" like this could get unwieldy if we don't draw a line somewhere, because everyone's going to want to get theirs baked in.
This is sort of the problem we got into with aggregator configuration in the shell... we had specialized configs for aggregators... but generalized configs for other iterators, including combiners. Although a bit long, the generalized configs were probably better long-run, rather than try to continue to maintain lots of little one-off specialized configs.
That said, a lot of people deal with binary data in Accumulo, and seeing data encoded as base16, hexadecimal, base32, or base64, might be really useful as a general rule to have baked in, so I wouldn't be opposed if we provided those basic facilities, and drew the line on anything else.

I only did this to drop the ScanInterpeter stuff

One option is to deprecate the formatting and interpreter options for 2.0 in the shell and not add the -hex option.  Going forward those shell options could be removed.  The deprecation message could ask user to open an issue if they need these features.

OK so sounds like we don't want a "scan -hex" option but we should deprecate the confusing shell options in 2.0 for possible removal in 2.1?

Could put the earliest version they would be removed in the message.

I will wait for feedback from @ctubbsii before making any changes.  I can't tell from his comments if he is for or opposed to this change.

I'm not opposed to the change. I'm just confused at the underlying motivation. Is the goal to simplify/consolidate the scan options? Is it to remove the ScanInterpreter because it's confusing? Is it to add a hex output? It's not clear to me what the goal is.
Without understanding what is motivating the specific changes, it's hard for me to fully get behind a solution. So, I'm just trying to offer generic words of caution, so we don't get stuck with something we'll regret later. This specific change feels a bit lateral to me, and not obviously better than what exists now.
Also, none of the current behavior or suggested changes really fix the underlying problem. All of this only exists (and we maintain it) because people want to scan from something like a command-line, and manipulate the output without writing code. Back in 2013, I suggested what I think is the best solution for this: separate utilities to replace the shell, so that output can be directly piped to whatever tools users want to use to manipulate their scan output for analysis and/or presentation.
I'd rather we had a scan utility that was independent of "shell" than try to provide an API within the shell for doing stuff in code a user can already do with existing utilities available in their terminal. With the client properties improvements, perhaps it's worth revisiting that now, and deprecating all the scan commands, rather than just specific presentation options? With a stable client API in Accumulo, we don't even have to release this separate utility as often as we release Accumulo. It would just use our public API to read a client config file, create a client, scan, and exit.

Is  the goal to simplify/consolidate the scan options? Is it to remove the ScanInterpreter because it's confusing? Is it to add a hex output?

All of the above.

I'd rather we had a scan utility that was independent of "shell" than try to provide an API within the shell for doing stuff in code a user can already do with existing utilities available in their terminal. With the client properties improvements, perhaps it's worth revisiting that now, and deprecating all the scan commands, rather than just specific presentation options? With a stable client API in Accumulo, we don't even have to release this separate utility as often as we release Accumulo. It would just use our public API to read a client config file, create a client, scan, and exit.

That would be nice.  But you probably spent more time writing this then I spent on this PR.

I have wanted to experiment with using Accumulo client API in the new JDK11 Java shell.  The easier that is, maybe the less these cumbersome options on the scanner are needed. Also the option to run scripts in the Accumulo shell, which was added after the formatter and interpreters, make these scan options less relevant.

This could be done for 2.1.  Leaving it open for now.

Closing in favor of #2787


Question about size mismatch in trained models.

Thanks for sharing your sharing!
I've tried to modify the SiamRPNRes22 to  SiamRPNRes19 in parameters:
    """     ResNet with 19 layer utilized in CVPR2019 paper.     Usage: ResNet(Bottleneck_CI, [2, 4], [True, False], [False, True], 64, [64, 128])     """
and got 20 models in exactly same size, like 610.8 MiB.
Then I tested those models by python ./siamese_tracking/test_siamrpn.py --arch SiamRPNRes19 --resume ./snapshot/checkpoint_e50.pth --dataset VOT2017 --cls_type thinner
and got size mismatch errors like:

RuntimeError: Error(s) in loading state_dict for SiamRPNRes19:
size mismatch for connect_model.template_cls.weight: copying a param of torch.Size([1280, 512, 3, 3]) from checkpoint, where the shape is torch.Size([5120, 512, 3, 3]) in current model.
size mismatch for connect_model.template_cls.bias: copying a param of torch.Size([1280]) from checkpoint, where the shape is torch.Size([5120]) in current model.
size mismatch for connect_model.template_reg.weight: copying a param of torch.Size([5120, 512, 3, 3]) from checkpoint, where the shape is torch.Size([10240, 512, 3, 3]) in current model.
size mismatch for connect_model.template_reg.bias: copying a param of torch.Size([5120]) from checkpoint, where the shape is torch.Size([10240]) in current model.
size mismatch for connect_model.search_cls.weight: copying a param of torch.Size([256, 512, 3, 3]) from checkpoint, where the shape is torch.Size([512, 512, 3, 3]) in current model.
size mismatch for connect_model.search_cls.bias: copying a param of torch.Size([256]) from checkpoint, where the shape is torch.Size([512]) in current model.
size mismatch for connect_model.search_reg.weight: copying a param of torch.Size([256, 512, 3, 3]) from checkpoint, where the shape is torch.Size([512, 512, 3, 3]) in current model.
size mismatch for connect_model.search_reg.bias: copying a param of torch.Size([256]) from checkpoint, where the shape is torch.Size([512]) in current model.

could you pls to tell me where can I modify and solve the mismatch problem?

Thanks for sharing your sharing!
I've tried to modify the SiamRPNRes22 to SiamRPNRes19 in parameters:
 """ ResNet with 19 layer utilized in CVPR2019 paper. Usage: ResNet(Bottleneck_CI, [2, 4], [True, False], [False, True], 64, [64, 128]) """
and got 20 models in exactly same size, like 610.8 MiB.
Then I tested those models by python ./siamese_tracking/test_siamrpn.py --arch SiamRPNRes19 --resume ./snapshot/checkpoint_e50.pth --dataset VOT2017 --cls_type thinner
and got size mismatch errors like:

RuntimeError: Error(s) in loading state_dict for SiamRPNRes19:
size mismatch for connect_model.template_cls.weight: copying a param of torch.Size([1280, 512, 3, 3]) from checkpoint, where the shape is torch.Size([5120, 512, 3, 3]) in current model.
size mismatch for connect_model.template_cls.bias: copying a param of torch.Size([1280]) from checkpoint, where the shape is torch.Size([5120]) in current model.
size mismatch for connect_model.template_reg.weight: copying a param of torch.Size([5120, 512, 3, 3]) from checkpoint, where the shape is torch.Size([10240, 512, 3, 3]) in current model.
size mismatch for connect_model.template_reg.bias: copying a param of torch.Size([5120]) from checkpoint, where the shape is torch.Size([10240]) in current model.
size mismatch for connect_model.search_cls.weight: copying a param of torch.Size([256, 512, 3, 3]) from checkpoint, where the shape is torch.Size([512, 512, 3, 3]) in current model.
size mismatch for connect_model.search_cls.bias: copying a param of torch.Size([256]) from checkpoint, where the shape is torch.Size([512]) in current model.
size mismatch for connect_model.search_reg.weight: copying a param of torch.Size([256, 512, 3, 3]) from checkpoint, where the shape is torch.Size([512, 512, 3, 3]) in current model.
size mismatch for connect_model.search_reg.bias: copying a param of torch.Size([256]) from checkpoint, where the shape is torch.Size([512]) in current model.

could you pls to tell me where can I modify and solve the mismatch problem?

Hi, thanks for your interest. It seems that the channels in RPN head are not correct. Could u check it again? BTW, it's suggested to test all epochs instead of the last epoch.

there are codes related, pls check these:
`class SiamRPNRes19(SiamRPN_):
def init(self, **kwargs):
super(SiamRPNRes19, self).init(**kwargs)
self.features = ResNet19()
inchannels = self.features.feature_size
    if self.cls_type == 'thinner': outchannels = 256
    elif self.cls_type == 'thicker': outchannels = 512
    else: raise ValueError('not implemented loss/cls type')

    self.connect_model = RPN_Up(anchor_nums=self.anchor_nums,
                                inchannels=inchannels,
                                outchannels=outchannels,
                                cls_type = self.cls_type)`

`class RPN_Up(nn.Module):
"""
For SiamRPN
"""
def init(self, anchor_nums=5, inchannels=256, outchannels=256, cls_type='thicker'):
super(RPN_Up, self).init()
    self.anchor_nums = anchor_nums
    self.inchannels = inchannels
    self.outchannels = outchannels

    if cls_type == 'thinner': self.cls_channel = self.anchor_nums
    elif cls_type == 'thicker': self.cls_channel = self.anchor_nums * 2
    else: raise ValueError('not implemented cls/loss type')

    self.reg_channel = 4 * self.anchor_nums

    self.template_cls = nn.Conv2d(self.inchannels, self.outchannels * self.cls_channel, kernel_size=3)
    self.template_reg = nn.Conv2d(self.inchannels, self.outchannels * self.reg_channel, kernel_size=3)

    self.search_cls = nn.Conv2d(self.inchannels, self.outchannels, kernel_size=3)
    self.search_reg = nn.Conv2d(self.inchannels, self.outchannels, kernel_size=3)
    self.adjust = nn.Conv2d(self.reg_channel, self.reg_channel, kernel_size=1)

def _conv2d_group(self, x, kernel):
    batch = kernel.size()[0]
    pk = kernel.view(-1, x.size()[1], kernel.size()[2], kernel.size()[3])
    px = x.view(1, -1, x.size()[2], x.size()[3])
    po = F.conv2d(px, pk, groups=batch)
    po = po.view(batch, -1, po.size()[2], po.size()[3])
    return po

def forward(self, z_f, x_f):
    cls_kernel = self.template_cls(z_f)
    reg_kernel = self.template_reg(z_f)

    cls_feature = self.search_cls(x_f)
    loc_feature = self.search_reg(x_f)

    _, _, s_cls, _ = cls_kernel.size()
    _, _, s_reg, _ = reg_kernel.size()

    pred_cls = self._conv2d_group(cls_feature, cls_kernel)
    pred_reg = self.adjust(self._conv2d_group(loc_feature, reg_kernel))

    return pred_cls, pred_reg`

cls_type

It seems you use different cls_type between training and testing?

That's it! That is where my problem lies.It bothered me for weeks.
Thank you again for your patient. You may close the issue.

That's it! That is where my problem lies.It bothered me for weeks.
Thank you again for your patient. You may close the issue.

Glad that I can help you. You can also try this backbone to see whether it brings better results.

cls_type

It seems you use different cls_type between training and testing?

thanks alot


Remove deprecated constants

Context
This PR is part of the variant aware dependency management API cleanup. It removes:

Usage.FOR_COMPILE (superceded by Usage.JAVA_API)
Usage.FOR_RUNTIME (superceded by Usage.JAVA_RUNTIME)
JavaPlugin.JAR_TYPE (superceded by ArtifactTypeDefinition.JAR_TYPE)

This pull request must not be merged yet, only reviewed, because alpha6 of the Android plugin still uses those constants. Once the sources of the Android plugin have no trace of the original constants, we can merge this PR.
Fixed gradle/performance#562

./gradlew clean assembleDebug passes on perf-android-large with plugin version 3.0.0-beta2, which wasn't the case a few weeks ago, so I think the usages were removed from the Android codebase.


[Bug]: The Discard button in Table widget is not visible due to min-dimensions of button-type widget

Is there an existing issue for this?

[X] I have searched the existing issues

Description
The Discard button in Table widget is not visible due to min-dimensions of button-type widget
Steps To Reproduce

Public Sample App
No response
Environment
Production
Issue video log
No response
Version
Cloud/Self-hosted

This is no longer reproducible.
I guess the refactor we did in #24627 might resolved this issue.
@kamakshibhat-appsmith please re-open if this is still reproducible


Permit newer versions of requests

Required to fix CVE-2023-32681

There's no need to rebase.
Please note that your commit also checks in the venv/ directory, which I doubt is intentional: https://github.com/aws/aws-elastic-beanstalk-cli/commit/7d2ba9837b717a71061c1ad075a2ae375b2b26f8

Should I publish another commit after removing the venv directory from my local ?

@alex can we get a release for this? Thanks

I do not work for AWS, I am not a maintainer of this package, I cannot answer questions about a release or how to handle a bad commit.
These questions should be directed to the maintainers/AWS.


/pentestgpt/utils bug

@dataclasses.dataclass
class Conversation:
    conversation_id: str = True ``
    message_list: List[Message] = dataclasses.field(default_factory=list)

    def __hash__(self):
        return hash(self.conversation_id)

    def __eq__(self, other):
        if not isinstance(other, Conversation):
            return False
        return self.conversation_id == other.conversation_id

in this part of the code the variable None should be changed to True
Otherwise we get an error:
Traceback (most recent call last):
File "/Users/pavelbardin/venv/bin/pentestgpt", line 8, in
sys.exit(main())
File "/Users/pavelbardin/venv/lib/python3.10/site-packages/pentestgpt/main.py", line 61, in main
pentestGPTHandler.main()
File "/Users/pavelbardin/venv/lib/python3.10/site-packages/pentestgpt/utils/pentest_gpt.py", line 731, in main
self.initialize(previous_session_ids=loaded_ids)
File "/Users/pavelbardin/venv/lib/python3.10/site-packages/pentestgpt/utils/pentest_gpt.py", line 260, in initialize
self._feed_init_prompts()
File "/Users/pavelbardin/venv/lib/python3.10/site-packages/pentestgpt/utils/pentest_gpt.py", line 187, in _feed_init_prompts
_reasoning_response = self.reasoningAgent.send_message(
File "/Users/pavelbardin/venv/lib/python3.10/site-packages/tenacity/init.py", line 289, in wrapped_f
return self(f, *args, **kw)
File "/Users/pavelbardin/venv/lib/python3.10/site-packages/tenacity/init.py", line 379, in call
do = self.iter(retry_state=retry_state)
File "/Users/pavelbardin/venv/lib/python3.10/site-packages/tenacity/init.py", line 326, in iter
raise retry_exc from fut.exception()
tenacity.RetryError: RetryError[<Future at 0x117b0ef80 state=finished raised KeyError>]

May I know what command did you run when you encounter the above error? It seems that the problem is about the connection


无法正常连接

运行指令scoop bucket add scoop-cn https://ghp.ci/https://github.com/duzyn/scoop-cn后，输出如下：
direct (Not in CN): https://ghp.ci/https://github.com/duzyn/scoop-cn
Checking repo... ERROR 'https://ghp.ci/https://github.com/duzyn/scoop-cn' doesn't look like a valid git repository

Error given:
fatal: unable to access 'https://ghp.ci/https://github.com/duzyn/scoop-cn/': Recv failure: Connection was reset

因为代理ghp.ci被墙了，现在已将ghp.ci换为ghgo.xyz。更换代理地址后应该可以正常工作了


integral_constant is not convertible to bool

I'm getting a compile error with the following call to hana::is_convertible:
#include <boost/hana.hpp>

namespace hana = boost::hana;

static_assert(
  hana::is_convertible<
    hana::bool_<true>
  , bool
  >::value
);

output:
/usr/local/include/boost/hana/core/to.hpp:36:22: error: ambiguous partial specializations of
      'to_impl<bool, boost::hana::integral_constant<bool, true>, boost::hana::when<true> >'
    struct to_impl : to_impl<To, From, when<true>> { };
                     ^
/usr/local/include/boost/hana/core/to.hpp:153:52: note: in instantiation of template class
      'boost::hana::to_impl<bool, boost::hana::integral_constant<bool, true>, void>' requested here
        static_cast<convert_detail::no_conversion>(*(to_impl<To, From>*)0)
                                                   ^
bool_conversion.cpp:6:9: note: during template argument deduction for class template partial
      specialization 'is_convertible<type-parameter-0-0, type-parameter-0-1,
      decltype((void)static_cast<convert_detail::no_conversion>(*(to_impl<To, From> *)0))>' [with From =
      boost::hana::integral_constant<bool, true>, To = bool]
  hana::is_convertible<
        ^
/usr/local/include/boost/hana/core/to.hpp:47:12: note: partial specialization matches [with To = bool,
      From = boost::hana::integral_constant<bool, true>, condition = true]
    struct to_impl<To, From, when<condition>> : convert_detail::no_conversion {
           ^
/usr/local/include/boost/hana/core/to.hpp:56:12: note: partial specialization matches [with To = bool,
      From = boost::hana::integral_constant<bool, true>]
    struct to_impl<To, From, when<convert_detail::is_valid<
           ^
/usr/local/include/boost/hana/core/to.hpp:171:12: note: partial specialization matches [with To = bool,
      From = boost::hana::integral_constant<bool, true>]
    struct to_impl<To, From, when<

Is this expected behaviour? I would at least expect it to compile and result in true/false.

This is not expected. Taking a look.

I can take a look too if you don't have time. Just let me know the expected result.
(I would guess it should be convertible)

So, I got the following test case:
// Copyright Louis Dionne 2013-2017
// Distributed under the Boost Software License, Version 1.0.
// (See accompanying file LICENSE.md or copy at http://boost.org/LICENSE_1_0.txt)

#include <boost/hana/bool.hpp>
#include <boost/hana/core/to.hpp>
#include <boost/hana/integral_constant.hpp>
namespace hana = boost::hana;

static_assert(hana::is_convertible<hana::bool_<true>, bool>::value, "");
static_assert(hana::is_convertible<hana::integral_constant<int, 1>, int>::value, "");
static_assert(hana::is_convertible<hana::integral_constant<int, 1>, long>::value, "");

int main() { }

The problem is that we have specializations of hana::is_convertible for stuff that can be static_casted to the underlying value_type (which is the case for hana::integral_constant), but also for models of the hana::IntegralConstant concept. They both match and we get the ambiguous specialization. We could simply add another specialization to disambiguate, or find a prettier solution. I wouldn't mind you thinking about that solution, otherwise I'll do it (but I have no ETA).

I can take a look too if you don't have time. Just let me know the expected result.
(I would guess it should be convertible)

I think it should be convertible, but not an embedding (since there's a loss of constexpr-ness).

Then I'm tempted to say that this is incorrect (not the error itself):
/usr/local/src/hana/test/integral_constant/udl.cpp:28:1: error: static_assert failed ""
static_assert(-1234_c == -1234ll, "");
^             ~~~~~~~~~~~~~~~~~~
1 error generated.

The specialization of to_impl for Constant makes it embedded with its value_type. Is that correct?

Ahh, actually, the documentation for Constant says:

Any Constant c holding an underlying value of tag T is convertible to any tag U such that T is convertible to U. Specifically, the conversion is equivalent to
to<U>(c) == to<U>(value<decltype(c)>())

Also, those conversions are marked as an embedding whenever the conversion of underlying types is an embedding. This is to allow Constants to inter-operate with constexpr objects easily:
plus(int_c<1>, 1) == 2

Strictly speaking, this is sometimes a violation of what it means to be an embedding. Indeed, while there exists an embedding from any Constant to a constexpr object (since Constant is just the canonical inclusion), there is no embedding from a Constant to a runtime object since we would lose the ability to define the value method (the constexprness of the object would have been lost). [...]

Hence, the conversion should be marked as an embedding.

I think this identifies a problem in that there can be discrepancies between to and is_convertible because is_convertible uses the raw type of From when calling to_impl directly. It should probably use the tag of From.

The documentation for is_convertible says:

Specifically, is_convertible<From, To> is whether calling to<To> with an object of data type From would not trigger a static assertion.

IOW, From is already expected to be a tag. Is my reading incorrect?

Ah, right. I think you explained that to me before as well. :sweat_smile:


1.16.5 Default preset contains Fossil errors.

OTG Plugin or Mod

[X] OTG Mod for Forge

OTG Version
OpenTerrainGenerator-1.16.5-0.0.17r1.jar
Forge or Spigot Versions
forge-1.16.5-36.2.2
What other plugins are you running?
None
Description
The default preset contains fossil errors: Fossil(1.156) These errors also sometimes show up for biomes that have no Fossil() resource. I was however not able to reproduce it using a simple one biome setup.
On a side note I could not find the Fossil() resource anywere (not on the wiki, not in a default writeall biome) also, it would be beneficial to new users to have the default preset set to writeall.
Startup Log:
[02aug2021 20:20:31.533] [main/INFO] [cpw.mods.modlauncher.Launcher/MODLAUNCHER]: ModLauncher running: args [--gameDir, ., --launchTarget, fmlserver, --fml.forgeVersion, 36.2.2, --fml.mcpVersion, 20210115.111550, --fml.mcVersion, 1.16.5, --fml.forgeGroup, net.minecraftforge, nogui]
[02aug2021 20:20:31.536] [main/INFO] [cpw.mods.modlauncher.Launcher/MODLAUNCHER]: ModLauncher 8.0.9+86+master.3cf110c starting: java version 1.8.0_152 by Oracle Corporation
[02aug2021 20:20:31.547] [main/WARN] [cpw.mods.modlauncher.SecureJarHandler/]: LEGACY JDK DETECTED, SECURED JAR HANDLING DISABLED
[02aug2021 20:20:31.867] [main/INFO] [net.minecraftforge.fml.loading.FixSSL/CORE]: Added Lets Encrypt root certificates as additional trust
[02aug2021 20:20:31.894] [main/INFO] [mixin/]: SpongePowered MIXIN Subsystem Version=0.8.2 Source=file:/D:/Minecraft%20Developmental%20Releases/DregoraMod1.66.5/Minecraft/libraries/org/spongepowered/mixin/0.8.2/mixin-0.8.2.jar Service=ModLauncher Env=SERVER
[02aug2021 20:20:32.666] [main/INFO] [cpw.mods.modlauncher.LaunchServiceHandler/MODLAUNCHER]: Launching target 'fmlserver' with arguments [--gameDir, ., nogui]
[02aug2021 20:20:37.821] [modloading-worker-2/INFO] [net.minecraftforge.common.ForgeMod/FORGEMOD]: Forge mod loading, version 36.2.2, for MC 1.16.5 with MCP 20210115.111550
[02aug2021 20:20:37.821] [modloading-worker-2/INFO] [net.minecraftforge.common.MinecraftForge/FORGE]: MinecraftForge v36.2.2 Initialized
[02aug2021 20:20:38.239] [main/INFO] [net.minecraftforge.registries.GameData/]: Potentially Dangerous alternative prefix `minecraft` for name `otg`, expected `otg`. This could be a intended override, but in most cases indicates a broken mod.
[02aug2021 20:20:38.599] [main/ERROR] [otg/]: [Configs] Invalid biome name Dregora_Swampland in biome group TemperateBiomes
[02aug2021 20:20:38.745] [main/INFO] [otg/]: [Configs] 1 biomes Loaded
[02aug2021 20:20:38.745] [main/INFO] [otg/]: [Configs] Dregora_Fungal
[02aug2021 20:20:38.819] [main/ERROR] [otg/]: [Configs] Invalid resource Fossil in Desert Lakes on line 213: Resource type Fossil had invalid parameters and could not be parsed, error: java.lang.ArrayIndexOutOfBoundsException: 1
[02aug2021 20:20:38.821] [main/ERROR] [otg/]: [Configs] Invalid resource Fossil in Desert Lakes on line 213: Resource type Fossil had invalid parameters and could not be parsed, error: java.lang.ArrayIndexOutOfBoundsException: 1
[02aug2021 20:20:38.857] [main/ERROR] [otg/]: [Configs] Invalid resource Fossil in Swamp on line 213: Resource type Fossil had invalid parameters and could not be parsed, error: java.lang.ArrayIndexOutOfBoundsException: 1
[02aug2021 20:20:38.858] [main/ERROR] [otg/]: [Configs] Invalid resource Fossil in Swamp on line 213: Resource type Fossil had invalid parameters and could not be parsed, error: java.lang.ArrayIndexOutOfBoundsException: 1
[02aug2021 20:20:38.934] [main/ERROR] [otg/]: [Configs] Invalid resource Fossil in Desert Hills on line 212: Resource type Fossil had invalid parameters and could not be parsed, error: java.lang.ArrayIndexOutOfBoundsException: 1
[02aug2021 20:20:38.935] [main/ERROR] [otg/]: [Configs] Invalid resource Fossil in Desert Hills on line 212: Resource type Fossil had invalid parameters and could not be parsed, error: java.lang.ArrayIndexOutOfBoundsException: 1
[02aug2021 20:20:38.976] [main/ERROR] [otg/]: [Configs] Invalid resource Fossil in Swamp Hills on line 212: Resource type Fossil had invalid parameters and could not be parsed, error: java.lang.ArrayIndexOutOfBoundsException: 1
[02aug2021 20:20:38.977] [main/ERROR] [otg/]: [Configs] Invalid resource Fossil in Swamp Hills on line 212: Resource type Fossil had invalid parameters and could not be parsed, error: java.lang.ArrayIndexOutOfBoundsException: 1
[02aug2021 20:20:39.019] [main/ERROR] [otg/]: [Configs] Invalid resource Fossil in Desert on line 212: Resource type Fossil had invalid parameters and could not be parsed, error: java.lang.ArrayIndexOutOfBoundsException: 1
[02aug2021 20:20:39.021] [main/ERROR] [otg/]: [Configs] Invalid resource Fossil in Desert on line 212: Resource type Fossil had invalid parameters and could not be parsed, error: java.lang.ArrayIndexOutOfBoundsException: 1
[02aug2021 20:20:39.035] [main/INFO] [otg/]: [Configs] 71 biomes Loaded
[02aug2021 20:20:39.035] [main/INFO] [otg/]: [Configs] Sky, Desert Lakes, Gravelly Mountains, Dark Forest Hills, Shattered Savanna Plateau, Birch Forest, Snowy Tundra, Modified Wooded Badlands Plateau, Swamp, The Void, Tall Birch Forest, Snowy Taiga Mountains, Beach, Snowy Beach, Giant Tree Taiga Hills, Shattered Savanna, Wooded Hills, Taiga, Birch Forest Hills, Bamboo Jungle Hills, Jungle Hills, Ice Spikes, Plains, Deep Warm Ocean, Snowy Taiga, Wooded Mountains, Snowy Mountains, Badlands, Mountain Edge, Lukewarm Ocean, Dark Forest, Giant Spruce Taiga, Tall Birch Hills, Badlands Plateau, Jungle, Cold Ocean, Frozen Ocean, Stone Shore, Savanna, Eroded Badlands, Sunflower Plains, Desert Hills, Swamp Hills, Modified Badlands Plateau, Giant Tree Taiga, Jungle Edge, Modified Jungle Edge, Wooded Badlands Plateau, Mountains, Mushroom Fields, Deep Lukewarm Ocean, Taiga Mountains, Ocean, River, Snowy Taiga Hills, Giant Spruce Taiga Hills, Taiga Hills, Savanna Plateau, Flower Forest, Deep Cold Ocean, Gravelly Mountains+, Modified Jungle, Warm Ocean, Mushroom Fields Shore, Frozen River, Forest, Desert, Bamboo Jungle, Deep Frozen Ocean, Hell, Deep Ocean
[02aug2021 20:20:39.461] [Forge Version Check/INFO] [net.minecraftforge.fml.VersionChecker/]: [forge] Starting version check at https://files.minecraftforge.net/net/minecraftforge/forge/promotions_slim.json
[02aug2021 20:20:40.176] [Forge Version Check/INFO] [net.minecraftforge.fml.VersionChecker/]: [forge] Found status: AHEAD Current: 36.2.2 Target: null
[02aug2021 20:20:41.548] [main/INFO] [com.mojang.authlib.yggdrasil.YggdrasilAuthenticationService/]: Environment: authHost='https://authserver.mojang.com', accountsHost='https://api.mojang.com', sessionHost='https://sessionserver.mojang.com', servicesHost='https://api.minecraftservices.com', name='PROD'
[02aug2021 20:20:42.271] [main/WARN] [net.minecraft.command.Commands/]: Ambiguity between arguments [otg, export, help] and [otg, export, name] with inputs: [help]
[02aug2021 20:20:42.272] [main/WARN] [net.minecraft.command.Commands/]: Ambiguity between arguments [otg, export, name, center] and [otg, export, name, preset] with inputs: [stone]
[02aug2021 20:20:42.282] [main/WARN] [net.minecraft.command.Commands/]: Ambiguity between arguments [teleport, destination] and [teleport, targets] with inputs: [Player, 0123, @e, dd12be42-52a9-4a91-a8a1-11c01849e498]
[02aug2021 20:20:42.283] [main/WARN] [net.minecraft.command.Commands/]: Ambiguity between arguments [teleport, location] and [teleport, destination] with inputs: [0.1 -0.5 .9, 0 0 0]
[02aug2021 20:20:42.284] [main/WARN] [net.minecraft.command.Commands/]: Ambiguity between arguments [teleport, location] and [teleport, targets] with inputs: [0.1 -0.5 .9, 0 0 0]
[02aug2021 20:20:42.285] [main/WARN] [net.minecraft.command.Commands/]: Ambiguity between arguments [teleport, targets] and [teleport, destination] with inputs: [Player, 0123, dd12be42-52a9-4a91-a8a1-11c01849e498]
[02aug2021 20:20:42.286] [main/WARN] [net.minecraft.command.Commands/]: Ambiguity between arguments [teleport, targets, location] and [teleport, targets, destination] with inputs: [0.1 -0.5 .9, 0 0 0]
[02aug2021 20:20:42.321] [main/INFO] [net.minecraft.resources.SimpleReloadableResourceManager/]: Reloading ResourceManager: Default, OpenTerrainGenerator-1.16.5-0.0.17r1.jar, forge-1.16.5-36.2.2-universal.jar
[02aug2021 20:20:43.065] [Worker-Main-12/INFO] [net.minecraft.item.crafting.RecipeManager/]: Loaded 7 recipes
[02aug2021 20:20:43.912] [Worker-Main-12/INFO] [net.minecraft.advancements.AdvancementList/]: Loaded 927 advancements
[02aug2021 20:20:44.761] [Server thread/INFO] [net.minecraft.server.dedicated.DedicatedServer/]: Starting minecraft server version 1.16.5
[02aug2021 20:20:44.761] [Server thread/INFO] [net.minecraft.server.dedicated.DedicatedServer/]: Loading properties
[02aug2021 20:20:44.761] [Server thread/INFO] [net.minecraft.server.dedicated.DedicatedServer/]: Default game type: SURVIVAL
[02aug2021 20:20:44.762] [Server thread/INFO] [net.minecraft.server.MinecraftServer/]: Generating keypair
[02aug2021 20:20:44.831] [Server thread/INFO] [net.minecraft.server.dedicated.DedicatedServer/]: Starting Minecraft server on *:25565
[02aug2021 20:20:44.836] [Server thread/INFO] [net.minecraft.network.NetworkSystem/]: Using default channel type
[02aug2021 20:20:45.547] [Server thread/WARN] [net.minecraftforge.common.ForgeConfigSpec/CORE]: Configuration file .\Debug\serverconfig\forge-server.toml is not correct. Correcting
[02aug2021 20:20:45.548] [Server thread/WARN] [net.minecraftforge.common.ForgeConfigSpec/CORE]: Incorrect key server was corrected from null to its default, SimpleCommentedConfig:{}.
[02aug2021 20:20:45.549] [Server thread/WARN] [net.minecraftforge.common.ForgeConfigSpec/CORE]: Incorrect key server.removeErroringEntities was corrected from null to its default, false.
[02aug2021 20:20:45.549] [Server thread/WARN] [net.minecraftforge.common.ForgeConfigSpec/CORE]: Incorrect key server.removeErroringTileEntities was corrected from null to its default, false.
[02aug2021 20:20:45.549] [Server thread/WARN] [net.minecraftforge.common.ForgeConfigSpec/CORE]: Incorrect key server.fullBoundingBoxLadders was corrected from null to its default, false.
[02aug2021 20:20:45.549] [Server thread/WARN] [net.minecraftforge.common.ForgeConfigSpec/CORE]: Incorrect key server.zombieBaseSummonChance was corrected from null to its default, 0.1.
[02aug2021 20:20:45.549] [Server thread/WARN] [net.minecraftforge.common.ForgeConfigSpec/CORE]: Incorrect key server.zombieBabyChance was corrected from null to its default, 0.05.
[02aug2021 20:20:45.550] [Server thread/WARN] [net.minecraftforge.common.ForgeConfigSpec/CORE]: Incorrect key server.logCascadingWorldGeneration was corrected from null to its default, true.
[02aug2021 20:20:45.550] [Server thread/WARN] [net.minecraftforge.common.ForgeConfigSpec/CORE]: Incorrect key server.fixVanillaCascading was corrected from null to its default, false.
[02aug2021 20:20:45.550] [Server thread/WARN] [net.minecraftforge.common.ForgeConfigSpec/CORE]: Incorrect key server.dimensionUnloadQueueDelay was corrected from null to its default, 0.
[02aug2021 20:20:45.551] [Server thread/WARN] [net.minecraftforge.common.ForgeConfigSpec/CORE]: Incorrect key server.treatEmptyTagsAsAir was corrected from null to its default, false.
[02aug2021 20:20:45.551] [Server thread/WARN] [net.minecraftforge.common.ForgeConfigSpec/CORE]: Incorrect key server.fixAdvancementLoading was corrected from null to its default, true.
[02aug2021 20:20:45.576] [Server thread/INFO] [net.minecraft.server.dedicated.DedicatedServer/]: Preparing level "Debug"
[02aug2021 20:21:02.991] [Worker-Main-15/INFO] [otg/]: [Main] Loading structures and pre-generator data
[02aug2021 20:21:02.996] [Worker-Main-15/INFO] [otg/]: [Main] Loading done
[02aug2021 20:21:03.287] [Server thread/INFO] [net.minecraft.server.MinecraftServer/]: Preparing start region for dimension minecraft:overworld
[02aug2021 20:21:03.339] [Worker-Main-9/INFO] [net.minecraft.world.chunk.listener.LoggingChunkStatusListener/]: Preparing spawn area: 0%
[02aug2021 20:21:03.789] [Worker-Main-11/INFO] [net.minecraft.world.chunk.listener.LoggingChunkStatusListener/]: Preparing spawn area: 1%
[02aug2021 20:21:04.290] [Worker-Main-9/INFO] [net.minecraft.world.chunk.listener.LoggingChunkStatusListener/]: Preparing spawn area: 6%
[02aug2021 20:21:04.788] [Worker-Main-15/INFO] [net.minecraft.world.chunk.listener.LoggingChunkStatusListener/]: Preparing spawn area: 12%
[02aug2021 20:21:05.289] [Worker-Main-10/INFO] [net.minecraft.world.chunk.listener.LoggingChunkStatusListener/]: Preparing spawn area: 19%
[02aug2021 20:21:05.788] [Worker-Main-15/INFO] [net.minecraft.world.chunk.listener.LoggingChunkStatusListener/]: Preparing spawn area: 26%
[02aug2021 20:21:06.289] [Worker-Main-13/INFO] [net.minecraft.world.chunk.listener.LoggingChunkStatusListener/]: Preparing spawn area: 33%
[02aug2021 20:21:06.809] [Worker-Main-11/INFO] [net.minecraft.world.chunk.listener.LoggingChunkStatusListener/]: Preparing spawn area: 42%
[02aug2021 20:21:07.289] [Worker-Main-13/INFO] [net.minecraft.world.chunk.listener.LoggingChunkStatusListener/]: Preparing spawn area: 48%
[02aug2021 20:21:07.789] [Worker-Main-13/INFO] [net.minecraft.world.chunk.listener.LoggingChunkStatusListener/]: Preparing spawn area: 60%
[02aug2021 20:21:08.289] [Worker-Main-14/INFO] [net.minecraft.world.chunk.listener.LoggingChunkStatusListener/]: Preparing spawn area: 69%
[02aug2021 20:21:08.791] [Worker-Main-13/INFO] [net.minecraft.world.chunk.listener.LoggingChunkStatusListener/]: Preparing spawn area: 81%
[02aug2021 20:21:09.289] [Worker-Main-8/INFO] [net.minecraft.world.chunk.listener.LoggingChunkStatusListener/]: Preparing spawn area: 91%
[02aug2021 20:21:09.628] [Server thread/INFO] [net.minecraft.world.chunk.listener.LoggingChunkStatusListener/]: Time elapsed: 6340 ms
[02aug2021 20:21:09.628] [Server thread/INFO] [net.minecraft.server.dedicated.DedicatedServer/]: Done (24.118s)! For help, type "help"

Fossil resource parameters have changed as of 0.0.13: Fossil(chance,minAltitude,maxAltitude)

Should be fixed now. Fossil() lines were written improperly on the default preset.


silabs: Drop obsolete clock configuration

Silabs Series-2 (all the EFR32xg2x chips) use the new clock driver
introduced in commit bda8ae8c3f0 ("drivers: clock_control: silabs: Add clock
control driver"). This driver get all the configuration from the Device
Tree.
The CMU (Clock Management Unit) options (CMU_HFXO_FREQ, CMU_HFRCO_FREQ,
CMU_NEED_LFXO, CMU_HFCLK_HFXO, etc...) are now only used for Series-0 and
Series-1. It does not make sense to declare them with Series-2.

https://github.com/zephyrproject-rtos/zephyr/pull/82737 waz merged so update xg23 too

v2:

rebase on main
also remove config introduced with xg23_rb4210a

@jerome-pouiller needs a rebase

v3:

rebase on main


feat(snippet): add Fix playlist hover effect

As title said.
Card preview:

Is playlist hover a fix or an addition?

Is playlist hover a fix or an addition?

Fix, Spotify added this element as an overlay in rootlist items in recent versions that, well, overlaid the previous anchor element. This snippet just applies display: none on top of it and returns the default hover behavior in themes.


Green sage lamp in citadel doesn't break for other players.

The task updates just fine, but the lamp physically is not broken.
All this does is leave the door closed, and breaking the lamp will open the door (and not give a cell since it's already collected).
So it's a very minor bug


Supply short definition for urn:cite:perseus:latlexent.lex11.1

"Abanteus" lacks a short definition; should be "An adjective describing belonging to Abas (king of Argos)."

Review of short definitions becomes unnecessary because of #19 and our decision to reformat the lemma database and source file.


[milvus] S3 miss the region/useVirtualHost settings

What this PR does / why we need it:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [mychartname])
[x] PR only contains changes for one chart

https://github.com/milvus-io/milvus/compare/v2.2.12...v2.2.13?diff=unified

minio settings add region/useVirtualHost

@orrn You'd commit your pr with git commit -s to add a dco.

@orrn您可以将您的项目添加到git commit -sdco。

I have added dco.


Low contrast for table cells in Dark Mode

Improve documentation
Link

Example (adminpack)

Describe the problem
When in dark mode, text in table cells has extremely low contrast.
Describe the improvement
Text should not have extremely low contrast. 🙂
Additional context

I would like to work on this. Please assign this task to me.

@zachallaun, thanks for the bug report!
@SyedMuzamilM, go right ahead and submit a PR if you'd like to work on it – no need to wait to be assigned 😄

Thanks. Ok will submit a PR.


NotFoundError: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node.

NotFoundError: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node.

NotFoundError: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node.
▶ 21 stack frames were collapsed.
onChange
./editor/index.jsx:217
214 |   editorState.setConvertOptions(getConvertOptions(this.editorProps))
215 | }
216 |

217 | this.setState({ editorState }, () => {
| ^  218 |   this.props.onChange && this.props.onChange(editorState)
219 |   callback && callback(editorState)
220 | })
View compiled
▼ 3 stack frames were expanded.
DraftEditor._this.update
./F:/tulvapp/client/node_modules/draft-js/lib/DraftEditor.react.js:145
resolveComposition
./F:/tulvapp/client/node_modules/draft-js/lib/DraftEditorCompositionHandler.js:162
(anonymous function)
./F:/tulvapp/client/node_modules/draft-js/lib/DraftEditorCompositionHandler.js:79
▲ 3 stack frames were expanded.
This screen is visible only in development. It will not appear if the app crashes in production.
Open your browser’s developer console to further inspect this error.  Click the 'X' or hit ESC to dismiss this message.


Update conformance model

This PR develops the under-specified #conformance model. Resolves https://github.com/solid/notifications/issues/106 .
The work herein follows the guidelines in https://www.w3.org/TR/spec-variability/ and https://www.w3.org/TR/qaframe-spec/ , and applies http://www.w3.org/ns/spec# .
To simplify the review process, this PR focuses on the #conformance section and leaves out updates intended to be throughout the specification corresponding to these changes that will be included in a follow up PR.

This PR proposes

Client
Notification Server
Resource Server

I think we should look into something a little bit more specific, for the Subscription flow:

Subscription Client
Subscription Server
Resource Server

For the Notification flow:

Notifications Sender
Notifications Receiver

This should avoid confusing naming since for target (delivery) based notifications flows, currently Webhook and LDN

Notifications Sender - acts as HTTP client
Notifications Receiver - acts as HTTP server

Terminology wasn't modified in this PR so github doesn't allow inline suggestions on those lines. I made dedicated PR with matching updates for two term definitions to use subscription client #128

Merging as per CG agreement: https://github.com/solid/notifications-panel/blob/main/meetings/2022-12-01.md#update-conformance-model with the understanding that the requested changes are accepted . Will also merge https://github.com/solid/notifications/pull/128 as part of one of the follow ups.


Fix NoneType error when energy sensors are unavailable

Fixes #104. Untested.

Thank you for this workaround. I applied it manually on my installation and it helped.

thanks for this - a fix for the problem was merged as PR #204 - I wasn't aware of your open pull request when I created mine, sorry.


Fix Pointer mapping with Environment Variables

Addresses: https://github.com/iamolegga/enviper/issues/6
Previously, when using Environment Variables without a Config file, pointers were not unmarshalling into structs. This fix addresses that defect and adds a unit test for validation.

Sweet! Thanks for merging this @iamolegga.

@jguttman94 thanks for your pr. Just refactored tests and it almost works, the only trouble with a map so far. I'll try to make it work, but if no luck I'll need someone's help (will push this to separate branch) 😅 After that we can make a new release. Stay in touch ✌


What model is V2.5 based on?

I see that V3.0 is based on Llama-70b. What is the 2.5 one based on? Thanks!

Hi, it is based on Llama-3-8B.


[Azure Arc] Going to SQL manage dashboard pops open the connection panel

When attempting to open a MIAA dashboard, connection dialog pops open.

This isn't random - we need a SQL connection to query for certain things like databases.
But the design here isn't great - we should make it clearer what the dialog is for (likely for now just having another custom connection dialog to prompt the user for username/password)


Remove mix alias and run rustfmt.

I think now that we can import mixer directly from sdl2 instead of having to import sdl2_mixer, the alias is as little less useful and having a more direct import could be better.
Latest rustfmt is also run.

This PR needs rebase.

@bvssvni Could you squash-merge if/when you merge? Thanks.

Travis CI fails due to a compiler bug, see https://github.com/PistonDevelopers/image/issues/645. Merging.


Fix for boolean equality check - DFJR-933

Weird happenings when is_round returns a boolean and the Jinja equality check fails. This fixes that by coercing to a string.
Changes

Modified cfgov/jinja2/v1/_includes/organisms/sidebar-breakout.html to fix boolean comparison issue.

Testing

Add a sidebar breakbout and toggle the round property. Preview. Check the width of the breakout image.

Review

@jimmynotjim
@anselmbradford
@KimberlyMunoz
@kave

Screenshots

Checklist

[ ] Changes are limited to a single goal (no scope creep)
[ ] Code can be automatically merged (no conflicts)
[ ] Code follows the standards laid out in the front end playbook
[ ] Passes all existing automated tests
[ ] New functions include new tests
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged
[ ] Visually tested in supported browsers and devices
[ ] Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)

:+1:

:+1:


Build fail after dependency zmk-dev-arm update to 3.5

This was the change on :
chore(ci): Bump to 3.5 Docker images: https://github.com/zmkfirmware/zmk/commit/94aa7d8d532f1e84e8e8b9fa96c522468dfc259d
I have a fork from this repo that also depends on https://github.com/zmkfirmware/zmk and started to fail on build:

Failing build example
The summary of the error:
'label' is marked as deprecated in 'properties:' in /__w/hillside-zmk-config/hillside-zmk-config/zephyr/dts/bindings/display/solomon,ssd1306fb-i2c.yaml for node /soc/i2c@40003000/ssd1306@3c.
devicetree error: 'pinctrl-0' is marked as required in 'properties:' in /__w/hillside-zmk-config/hillside-zmk-config/zephyr/dts/bindings/spi/nordic,nrf-spim.yaml, but does not appear in <Node /soc/spi@40004000 in '/__w/hillside-zmk-config/hillside-zmk-config/zephyr/misc/empty_file.c'>
CMake Error at /__w/hillside-zmk-config/hillside-zmk-config/zephyr/cmake/modules/dts.cmake:279 (message):
  gen_defines.py failed with return code: 1
-- In: /tmp/tmp.k5MDIcFl7Q/zephyr, command: /usr/bin/python3;/__w/hillside-zmk-config/hillside-zmk-config/zephyr/scripts/dts/gen_defines.py;--dts;/tmp/tmp.k5MDIcFl7Q/zephyr/zephyr.dts.pre;--dtc-flags;'';--bindings-dirs;/__w/hillside-zmk-config/hillside-zmk-config/zmk/app/module/dts/bindings;/__w/hillside-zmk-config/hillside-zmk-config/zmk/app/dts/bindings;/__w/hillside-zmk-config/hillside-zmk-config/zephyr/dts/bindings;--header-out;/tmp/tmp.k5MDIcFl7Q/zephyr/include/generated/devicetree_generated.h.new;--dts-out;/tmp/tmp.k5MDIcFl7Q/zephyr/zephyr.dts.new;--edt-pickle-out;/tmp/tmp.k5MDIcFl7Q/zephyr/edt.pickle;--vendor-prefixes;/__w/hillside-zmk-config/hillside-zmk-config/zmk/app/dts/bindings/vendor-prefixes.txt;--vendor-prefixes;/__w/hillside-zmk-config/hillside-zmk-config/zephyr/dts/bindings/vendor-prefixes.txt
Call Stack (most recent call first):
  /__w/hillside-zmk-config/hillside-zmk-config/zephyr/cmake/modules/zephyr_default.cmake:129 (include)
  /__w/hillside-zmk-config/hillside-zmk-config/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
  /__w/hillside-zmk-config/hillside-zmk-config/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
  CMakeLists.txt:8 (find_package)

I forked this project today and tried to build the 52 key keymap and ran into the same issue. @mmccoyd can you please help?

I'm checking the PR that made the change:

https://github.com/zmkfirmware/zmk/pull/1995

We could take some inspiration from there.

It can be fixed by #10

Thank you @alparo.
This PR fixes it: https://github.com/mmccoyd/zmk-config/pull/10