ehl_crb: kernel.timer.tickless failed.

To Reproduce
Steps to reproduce the behavior:

west build -b ehl_crb -p auto tests/kernel/timer/timer_api -DCONF_FILE="prj_tickless.conf"
copy binary to USB/PXE boot media
boot
See error

Logs and console output
*** Booting Zephyr OS build zephyr-v2.5.0-652-g767ba47423fd  ***
Running test suite timer_api
===================================================================
START - test_time_conversions
PASS - test_time_conversions
===================================================================
START - test_timer_duration_period
PASS - test_timer_duration_period
===================================================================
START - test_timer_restart
PASS - test_timer_restart
===================================================================
START - test_timer_period_0
PASS - test_timer_period_0
===================================================================
START - test_timer_expirefn_null
PASS - test_timer_expirefn_null
===================================================================
START - test_timer_periodicity
PASS - test_timer_periodicity
===================================================================
START - test_timer_status_get
PASS - test_timer_status_get
===================================================================
START - test_timer_status_get_anytime
PASS - test_timer_status_get_anytime
===================================================================
START - test_timer_status_sync
PASS - test_timer_status_sync
===================================================================
START - test_timer_k_define
PASS - test_timer_k_define
===================================================================
START - test_timer_user_data
PASS - test_timer_user_data
===================================================================
START - test_timer_remaining
PASS - test_timer_remaining
===================================================================
START - test_timeout_abs
PASS - test_timeout_abs
===================================================================
START - test_sleep_abs
Assertion failed at WEST_TOPDIR/zephyr/tests/kernel/timer/timer_api/src/main.c:750: test_sleep_abs: (late >= 0 && late < k_us_to_ticks_ceil32(100) is false)
expected wakeup at 33208, got 33209 (late 1)
FAIL - test_sleep_abs
===================================================================
Test suite timer_api failed.
===================================================================
PROJECT EXECUTION FAILED

Environment (please complete the following information):

OS: Linux
Toolchain: zephyr-sdk-0.12.2
Commit ID: 767ba47423fd

@pabigot Does this relate to #32339 ?

Does this relate to #32339 ?

I created that as a bug in hopes that we could avoid wasting so much time on this test.  But if the preferred path is to play whack-a-mole, there needs to be separate bugs as they come up.

play whack-a-mole
I never liked that game... :frowning:

I created that as a bug in hopes that we could avoid wasting so much time on this test.

what is blocking you now from re-implementing the test? The fact that it was changed from 'bug' to 'enhancement'? What difference does this make? if you filed a specific bug against the existing test that could be addressed in the current test, it is a bug. Re-implementation of something in my dictionary counts as enhancement because you are not addressing a single issue, you are enhancing the test overall.
If you think this test needs to be re-implemented and it will fix all the issues, the label of the issue should not really block you from moving forward. If a bug label makes you more comfortable, be my guest and change it back...

@pabigot The test case in question here is actually brand new, it contains no tick/ms math at all.  I don't argue that this test deserves rework, I just don't see how that's going to help the issue in question.
At the end of the day timing tests require tuning because (1) real time cannot be "locked", requiring careful initialization timing and slop and forgiveness in results (2) real systems have wildly different performance and tick rate behavior, which impacts those tolerances, and (3) we naturally want timing to be "precise", so have a built-in incentive to overtighten those values.  And we reliably find systems where a combination of hardware, configuration, and occasional bugs bust the limits and show failures.
A rewrite can fix some stuff (the tick/ms math in timer_api is indeed a big problem) but it can't fix the fundamentals.

This issue also found in EHL ACRN platform and show the same log as ehl_crb bare metal, so I comment here instead of filing a new issue for it.
And the issue happened starting from this version:
zephyr: gitlab mainline commit: 23f699bd90 (*** Booting Zephyr OS build zephyr-v2.5.0-484-g23f699bd907f  ***)
zephyr-intel: gitlab mainline commit: 22c6331

This issue also found in EHL ACRN platform and show the same log as ehl_crb bare metal, so I comment here instead of filing a new issue for it.
And the issue happened starting from this version:
zephyr: gitlab mainline commit: 23f699b (*** Booting Zephyr OS build zephyr-v2.5.0-484-g23f699bd907f ***)
zephyr-intel: gitlab mainline commit: 22c6331

Excuse me, their failure test case was different, so I file another issue for this:
https://github.com/zephyrproject-rtos/zephyr/issues/32877

Excuse me, their failure test case was different, so I file another issue for this:

How is this different? This is failing in the same testcase.

Excuse me, their failure test case was different, so I file another issue for this:

How is this different? This is failing in the same testcase.

They failed in different case, ehl crb bare metal is falied on test_sleep_abs(),  arcn ehl is failed test_timeout_abs(). But they are indeed belong to the same testsuite. Should I close the another one for better tracking it?

@andyross any updates?

Can not reproduce this failure anymore on EHL_CRB or ACRN. Confirmed it with @enjiamai  as well on ACRN. So closing this out.


Carto process scoping

Now that we have easier access to a map style we can edit in Maputnik, and we have more editing happening that's revealing the gaps in teh OSM Bright adapted style we're using, it makes sense to go back to the carto design work @tsinn had started in January and port that over to OMT based style.
Also need to think about assessing tags present in the data now and a minimal attempt to anticipate any near term additional needs, without going down the rabbithole of the many, many style tags OHM will need at some point in the future.
Would be nice to get an instance of taginfo stood up so it's easy to see what's in the DB and what's getting added.
┆Created By: Dan Rademacher
┆Due Date: 2019-09-18

This work is underway over in #65, #66 and others


Update exception-handling_4.cs

Not good to have broken examples  This code generates a CS0168 error because e is not used.  You should definitely use it to set IndexOutOfRangeException to the new exception's InnerException.  You do this correctly in the topic "How to: Handle an Exception Using try/catch (C# Programming Guide)"

Hi @rcseacord, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, DNFBOT;

@rcseacord Thank you for finding this and submitting a fix. We really appreciate it.
:shipit: now.


BSOD with Minecraft 1.13.2???

Platform: Windows 10 v1903 (OS Build 18362.53)
Architecture: 64-bit
AdoptOpen version: JRE 8u212-b03
JVM: HotSpot
Joining a world in Minecraft 1.13.2 causes the system to blue screen. Yeah, I dunno either.
Steps to reproduce:

Download MultiMC development version (this is the launcher I used, this probably happens with the vanilla launcher too though)
Create an instance for 1.13.2 (this may happen with other versions, haven't tested)
Launch that instance
In that instance, create a new world
Wait until the "Joining world..." text appears
RIP Windows

@Leo40Git Did this occur with the previous AdoptOpenJDK binary 8u191?

8u191 doesn't seem to be available for Windows. 8u192 is, however, so I'll try that.

BSOD does not occur with 8u192.

BSOD doesn't occur on 8u202, either.

...wait, what? The binary version of 8u212 doesn't cause the BSOD, but the installer version does?

Interesting.  I suspect the installer must link to a DLL that has an
issue.  I’ll swap this to the installer repo and find an engineer
On Fri, 19 Apr 2019 at 11:42, Kfir Awad<EMAIL_ADDRESS>wrote:

...wait, what? The binary version of 8u212 doesn't cause the BSOD, but the
installer version does?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/AdoptOpenJDK/openjdk-build/issues/1050#issuecomment-484847757,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABME2B7NRUTE6GTFJOGNZDPRGOY5ANCNFSM4HG6RV4Q
.

--
Cheers, Martijn (Sent from Gmail Mobile)


MaxGroupPooling Module not found!

I cannot find the code of MaxGroupPooling used in line 102 of micronet.py.
https://github.com/liyunsheng13/micronet/blob/main/backbone/micronet.py#L102
Can you check?

I add the MaxGroupPooling function. Thanks for letting me know. Actually, I do not use this function for MicroNet implementation. It is just used for ablation.

Thanks for the fast reply. I will re-check the code.


Validate parsed accessed tokens.

I've seen cases where Claims["User"]["Name"] is an empty string. I don't have a good repro for when that can happen (last time I saw it, I had signed in when the GitHub API was having issues), but this will validate the access token before creating it and after decoding it.

:+1:


meta-rauc-tegra: switch to using 'verity' bundle format

The kernel configuration already enabled 'verity' support, but the bundle did not.
The 'verity' format is the successor of the legacy 'plain' format which is still supported by RAUC but should not be used for new projects.
Also note that only the 'verity' format allows using RAUC features as streaming, encryption and adaptive updates.
Signed-off-by: Enrico Jorns<EMAIL_ADDRESS>

Hi @ejoerns,
Thank you. The change looks good to me.
Thinking aloud, I am wondering whether it is worth explicitly to enable CONFIG_DM_VERITY in rauc.cfg kernel fragment because the other kernel configuration in the meta-tegra BSP layer may change over time. Anyway, it looks good and I will merge the GitHub pull request.
Thanks,
Leon


added link to user panel and logout on about page

Hello!

Type: bug fix
Link to issue: -

In raising this pull request, I confirm the following:

[x] I have read and understood the Contributing Guidelines
[x] I have checked that another pull request for this purpose does not exist
[ ] I wrote some tests for this PR

Small description of change:
After log in user can't see link to users panel and log out, but can see log in
Thanks

Thank you


Fix tiny typo

can not ➡  cannot
https://www.grammarly.com/blog/cannot-or-can-not/

THANK YOU, @rabernat!


Issue with uploading COSV files

We have with loading ZIP (with many files) or with uploading many files at once
Also need to enhance UI for uploading COSV files: proper table for uploaded files, top-bar for uploading, maybe some extra elements for ZIP archives

[ ] #2679
[x] #2678
[ ] #2685
[ ] Restore processing of raw cosv files after restart
[ ] Need to store content-length of raw cosv file in database
[x] #2688
[ ] #2693

A fold or hide button would be more friendly for users when massive files were selected or uploaded.

Problem in raw cosv files without duplicates:
SELECT substring(file_name, POSITION('/' in file_name) + 1, LENGTH(file_name) - POSITION('/' in file_name) - 5), file_name  FROM raw_cosv_file where status = 'FAILED' and status_message not LIKE '%Duplicate entry%'


Update @angular/cli

We have a somewhat old version of @angular/cli specified in packages.json, and that should be updated.

Fixed!


Fixed minor spacing issues

@abdale : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@abdale - thanks for the fixes.


EF generates different SQL queries for expressions with type conversion using () operator vs 'as' operator

The generated SQL queries are different for an expression with type conversion using () operator vs. an expression with 'as' operator.
Please refer to the following code snippets and relevent log outputs.
Code
context.Set<Animal>().Where(x => x is Dog && ((Dog)x).Name == "Woof").ToList();

Output
 SELECT [x].[Id], [x].[AnimalType], [x].[Name]
 FROM [Animal] AS [x]
 WHERE [x].[AnimalType] IN (3, 2, 1) AND (([x].[AnimalType] = 3) AND ([x].[Name] = N'Woof'))

Code
context.Set<Animal>().Where(x => x is Dog && (x as Dog).Name == "Woof").ToList();

Output
SELECT [x].[Id], [x].[AnimalType], [x].[Name]
FROM [Animal] AS [x]
WHERE [x].[AnimalType] IN (3, 2, 1) AND ([x].[AnimalType] = 3)

Steps to reproduce
Repro included at https://github.com/avinash-phaniraj-readify/EFCoreTestBed/tree/TypeConversionWithAsOperatorError
Further technical details
EF Core version: 2.1
Database Provider: EntityFrameworkCore.SqlServerCompact35
Operating system: Windows 10.0.17134
IDE: Visual Studio 2017 15.7.4

as operator is not server translated hence when you use it in Where, it will be evaluated on client hence missing in SQL.

@smitpatel Is this by design, or has it just not been implemented yet? If the latter, is there a backlog item tracking this?

@smitpatel thanks for you response. I understand why it is not there (technically), but it is more of why it has to be like that (rationale) as @optiks mentioned.


Start and end months, how to force calendar to recognise them?

Hi,
I've just been looking through the calendar and have Garbage Collection entries showing for every month, past and present. I have start and end dates set for each sensor but it doesn't appear to be understood by the calendar. :/
Sadly, my council change their collection dates (December to November for most bins and April to March for one) each year, so there is no point having the dates continue past the end dates and they will more than likely change for the next 12 months.
How can I force the calendar to only show the date ranges set for each sensor?
Thanks!

I am not sure what you mean by start date and end date, but if you mean first and last month then that's weird, they should work with the calendar. I have tested that and it works for me.
The whole integration is made for schedules based on some defined rules. If the rules keep changing, you have two options.
Either update the rules when they change (e.g. at the beginning of new year) - it would update the calendar.
Or use a different integration, like the integration with google calendar, where you can also create recurrent events, but you can also re-schedule them individually.

Sorry, I used the wrong terminology, it should have been first collection month and last collection month.
Where I have a bin sensor with a first collection month of April and the last of March I (probably incorrectly, now I think about it) assumed that it would only populate entries on the calendar for those months and there would be no entries (before or after).
But now I type it out, and based on what you've said, why would it. Sorry, ignore me!


[Build Script Helper] Add an option that indicates the driver is being built for use with a local just-built frontend

When used, we mostly just need to be aware that the build is in a single-target mode and to simplify where the build products are placed, so that they are easier to find from the compiler's build-script.
This will be used from swift's build-script to always build an instance of swift-driver using a host toolchain, in order to patch the swift build directory with the new driver.

@swift-ci please test

@swift-ci please test

@swift-ci please test


Removing hacspec

The plan is to delete all things related to the hacspec sub-crate.
On the other hand, we are keeping the hacspec-crypto crypto backend, as it both (1) serves as a good software-only alternative crypto backend and (2) can be used to along with the cargo hax into fstar command. Note that to do this, I had to do a "mini-wrapper" of secret integers inside hacspec-crypto. The reason is that all the cryptographic functions in hacspec-crypto expect arrays of secret integers, but our EDHOC implementation has no concept of them anymore. Later, we may want to re-add secret integer handling (in places where it makes sense), but for now let's keep it simple and have it isolated in hacspec-crypto.

@chrysn TLDR; it's the second option.
When @malishav started working towards having formal verification of edhoc-rs, hacspec was in v1 and had many restrictions on what Rust constructs could be used. With time, after hacspec-v2 was introduced, support for and more more constructs have been added.
Thus, the current recommendation from the hacspec team is that we write the code in pure Rust, and the hax command should be able to handle it. By "handle it" I mean that cargo hax into fstar will translate edhoc-rs into *.fstar files, which can be used in the formal verification.
That said, some Rust idioms may not yet be supported by hax/hacspec, but in my experience these cases have been usually easy fixes (e.g. use ifs instead of match with @ bindings). In addition, as posted in the first comment, we may later re-add secret integers (U8 and friends) to parts of the code that are relevant to cryptographic operations.

At this point, I've ran out of ideas to fix the fstar step on CI. While there are a few things that we could do on our side (like putting generate_connection_identifier_cbor behind a feature flag), having fstar generation run without any errors depends on fixes from the hacspec side. Maybe we should just comment it out until hax is updated. What do you think @malishav ?

At this point, I've ran out of ideas to fix the fstar step on CI. While there are a few things that we could do on our side (like putting generate_connection_identifier_cbor behind a feature flag), having fstar generation run without any errors depends on fixes from the hacspec side. Maybe we should just comment it out until hax is updated. What do you think @malishav ?

@geonnave: How about we move the F* generation step to be triggered only on releases and we wait for the hacspec team to fix this before releasing a new version?
@W95Psp: do you have any update on the updates needed to get the Rust version to generate F*?

We may need to schedule another session for resolving the fstar, say in the
third week of October?
On Tue, Oct 3, 2023, 18:38 Mališa Vučinić @.***> wrote:

At this point, I've ran out of ideas to fix the fstar step on CI. While
there are a few things that we could do on our side (like putting
generate_connection_identifier_cbor behind a feature flag), having fstar
generation run without any errors depends on fixes from the hacspec side.
Maybe we should just comment it out until hax is updated. What do you think
@malishav https://github.com/malishav ?
@geonnave https://github.com/geonnave: How about we move the F*
generation step to be triggered only on releases and we wait for the
hacspec team to fix this before releasing a new version?
@W95Psp https://github.com/W95Psp: do you have any update on the
updates needed to get the Rust version to generate F*?
—
Reply to this email directly, view it on GitHub
https://github.com/openwsn-berkeley/edhoc-rs/pull/106#issuecomment-1745345713,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABFUVSYIOZAIQVW4ZC64D4DX5Q5P3AVCNFSM6AAAAAA5PN2N62VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBVGM2DKNZRGM
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

That looks nice!
Quick report on the Hax point of view:
Skip c_wrapper
We don't want the module c_wrapper to be extracted. The flag -i on the into subcommand of Hax can be used to skip certain items, i.e.:
cargo hax -C -p edhoc-rs -p edhoc-crypto -p edhoc-ead --no-default-features --features='cb-hacspec, ead-none' --release \; into -i '-c_wrapper::**' fstar
Errors I get running that command

error[HAX0008]: (reject_RawOrMutPointer) ExplicitRejection: I need to inverstigate this one, we get no span information.
error[HAX0010] (edhoc.rs:849:17): we discussed that, I need to look into it. Issue https://github.com/hacspec/hacspec-v2/issues/256
error[HAX0001]:
while loops are not supported yet, see https://github.com/hacspec/hacspec-v2/issues/113
In general, while loops are not very handy to work with from a proof perspective (i.e. there is no built-in invariant about terminaison; when you write a for loop over a finite iterator, you get termination for free)

edhoc.rs:940:9: why not converting that while loop into a for loop? e.g.for i in 0..suites_len {
   if suites[i] <= CBOR_UINT_1BYTE {
       output.content[1 + raw_suites_len] = suites[i];
       raw_suites_len += 1;
   } else {
       output.content[1 + raw_suites_len] = CBOR_UINT_1BYTE;
       output.content[2 + raw_suites_len] = suites[i];
       raw_suites_len += 2;
   }
   i += 1;
}

instead of:let mut i: usize = 0;
while i < suites_len {
    if suites[i] <= CBOR_UINT_1BYTE {
        output.content[1 + raw_suites_len] = suites[i];
        raw_suites_len += 1;
    } else {
        output.content[1 + raw_suites_len] = CBOR_UINT_1BYTE;
        output.content[2 + raw_suites_len] = suites[i];
        raw_suites_len += 2;
    }
    i += 1;
}

lib.rs:337:5: here get_random_byte is not pure, we won't able to very anything that uses that. I think you need something like: https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=d84fb15c9531eb195c76ea629932b5cd (just wrote that quickly, we can chat more about this kind of model later if that's something interesting)

To conclude
I should investigate 1 and 2.
I think 3.i should be rewrote into a for loop, and we should chat about 3.2 and determinism.

@malishav thanks for the review, did the suggested renaming.
@karthikbhargavan I created a group chat on Zulip so we can coordinate the meeting.
@W95Psp excellent, thanks for the detailed report.

edhoc.rs: I replaced the while with a for as suggested.
lib.rs: in fact, we originally intended for this file to be outside the proof, since its main goal is just to provide a developer-friendly wrapper for the core implementation of the protocol. I am playing with the -i flag to try to remove it from the verification.

Oh, right! Then, if lib.rs is excluded that's simplifying things indeed, that's great news :partying_face:
(though we'll have to review the code to make sure there's no seemingly undeterministic calls in the parts we want to extract)

With the interim change of having the generate-fstar job running only on releases or manual dispatch, all CI tests are passing, and this is now ready to merge.

Awesome, congrats on getting this through.
I've gathered from following the discussions that there are some style preferences or requirements that are (now that fstar is generated only on releases) not forcibly upheld now, such as a strong no-go for while loops (which is actually nice b/c we don't really need an unbounded Turing machine for EDHOC) and a soft preference against early return. Is there a comprehensive list somewhere that contributors can read up on to avoid?

Is there a comprehensive list somewhere that contributors can read up on to avoid?

@W95Psp tagging you here, so that we can maybe avoid bothering you too much with hax-compatibility questions in the future 😄


options validation improvements + fix for docker image pull

What type of PR is this?
/kind bug
/kind feature
Any specific area of the project related to this PR?
/area cmd
/area pkg
What this PR does / why we need it:
This PR makes the image pull honor the common docker behavior for image pulls.
Also, this PR introduces the ability to specify semver-ish tags as driverversion options.
Which issue(s) this PR fixes:
Fixes #33
Fixes #34
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

fix: honor docker image pull behaviour
update: accept semver-ish strings as driver version option values

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign leodido
You can assign the PR to them by writing /assign @leodido in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: fntlnz
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [fntlnz]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 4b14e5e6ec19fb2d1df1c343017cfeb0e163b647


Updated: intellij-ultimate 191.7479.19

Newer version of intellij-ultimate (192.7142.36) is now available in master. 814dd47645ec6e9f3142d30ebb66284ad7afd0dc


Null pointers should not be dereferenced

This pull request is focused on resolving occurrences of Sonar rule squid:S2259 - Null pointers should not be dereferenced
You can find more information about the issue here:
https://dev.eclipse.org/sonar/coding_rules#q=squid:S2259
Please let me know if you have any questions.
Kirill Vlasov

@kirill-vlasov Could you please create a JIRA here https://issues.apache.org/jira/browse/HIVE/ and add the JIRA id in the title of the PR?

@kirill-vlasov  Could you please create a JIRA here https://issues.apache.org/jira/browse/HIVE/ and add the JIRA id in the title of the PR?

@belugabehr, it is done - https://issues.apache.org/jira/browse/HIVE-23615

ci fails with a wierd error - "owner can't be null" maybe it's because the PR comes from "unknown repository"


Document translation of text within an image

Adding new option "translateTextWithImage" that can be set to true or false that enables translation of image within a document translation request.
New parameter added for batch and sync document translation.
New parameters added to TranslationStatus, DocumentStatus and DocumentTranslateContent to return the number of images translated successfully and that failed during a document translation operation.
fix https://github.com/Azure/azure-rest-api-specs/issues/31404

Please set like update tspconfig for AI.DocumentTranslation by kazrael2119 · Pull Request #31397 · Azure/azure-rest-api-specs to pass TS SDK generation.

Addeed the BreakingChangeApproved-Benign label because the change adds a new optional query parameter, there is no change in order of the query parameters, the change should not impact the order of appearance of the body parameters and the other header parameter is clientRequestId`, which is a standard header.


amplify cli v4.21.1 introduces graphql mutation dynamo error

Describe the bug
amplify push with v4.21.1 results in an api stack that where sending createThing graphql mutations results in consistant failure with the following error:
{
  "data": {
    "createFoo": null
  },
  "errors": [
    {
      "path": [
        "createFoo"
      ],
      "data": null,
      "errorType": "DynamoDB:AmazonDynamoDBException",
      "errorInfo": null,
      "locations": [
        {
          "line": 2,
          "column": 3,
          "sourceName": null
        }
      ],
      "message": "One or more parameter values were invalid: Type mismatch for key id expected: S actual: NULL (Service: AmazonDynamoDBv2; Status Code: 400; Error Code: ValidationException; Request ID: REDACTED)"
    }
  ]
}

The same action with v4.21.0 (and earlier) results in no error.
Amplify CLI Version
<EMAIL_ADDRESS><EMAIL_ADDRESS>is fine)
To Reproduce
amplify push and then send a createFoo mutation to the api.
Schema:
type Foo
  @model
  @key(
    name: "byBar"
    fields: ["barID"]
    queryField: "fooByBar"
  ) {
  barID: ID!
  Bar: Bar! @connection(fields: ["barID"])
  something: [Something]
    @connection(keyName: "byBar", fields: ["barID"])
}

Autogenerated mutation that creates error when used:

mutation CreateFoo(
  $input: CreateFooInput!
  $condition: ModelFooConditionInput
) {
  createFoo(input: $input, condition: $condition) {
    barID
    bar {
      (stuff)
    }
  }
}

With the input type being:
input CreateFooInput {
  barID: ID!
}

Expected behavior
I expect the mutation to create a new Foo entry in dynamo and no error to be thrown.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: Mac
Node Version: v12.16.2

May I ask if this issue has been fixed? It was working fine until recently where I am also encountering an error each time I try to create a new item.


postfix: enable ldap support by default

Ldap authentication is fairly common in any reasonable sized mail setup.
Our dovecot also comes with ldap support.
Other distributions like debian, archlinux, ubuntu and fedora also
provide ldap support along with their postfix server.
It might be also useful to have database support, but this is a different pull request.
Our openldap package is 2.6 M big at the moment.
du -sh $buildInputs
2.6M    /nix/store/gbd5aqz9s0r5984dr214g9k1513j4v9i-openldap-2.4.46

We might be able to further reduce this by splitting libraries from slapd.
Motivation for this change
Things done

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

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

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

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: postfix
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: postfix
Partial log (click to expand)
strip is /nix/store/vcc4svb8gy29g4pam2zja6llkbcwsyiq-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/i942xg2v2mxnayj0y2q01285lcs7xil6-postfix-3.3.1/libexec  /nix/store/i942xg2v2mxnayj0y2q01285lcs7xil6-postfix-3.3.1/bin  /nix/store/i942xg2v2mxnayj0y2q01285lcs7xil6-postfix-3.3.1/sbin
patching script interpreter paths in /nix/store/i942xg2v2mxnayj0y2q01285lcs7xil6-postfix-3.3.1
/nix/store/i942xg2v2mxnayj0y2q01285lcs7xil6-postfix-3.3.1/libexec/postfix/postmulti-script: interpreter directive changed from " /bin/sh" to "/nix/store/r47p5pzx52m3n34vdgqpk5rvqgm0m24m-bash-4.4-p23/bin/sh"
/nix/store/i942xg2v2mxnayj0y2q01285lcs7xil6-postfix-3.3.1/libexec/postfix/.post-install-wrapped: interpreter directive changed from "/bin/sh" to "/nix/store/r47p5pzx52m3n34vdgqpk5rvqgm0m24m-bash-4.4-p23/bin/sh"
/nix/store/i942xg2v2mxnayj0y2q01285lcs7xil6-postfix-3.3.1/libexec/postfix/.postfix-script-wrapped: interpreter directive changed from "/bin/sh" to "/nix/store/r47p5pzx52m3n34vdgqpk5rvqgm0m24m-bash-4.4-p23/bin/sh"
/nix/store/i942xg2v2mxnayj0y2q01285lcs7xil6-postfix-3.3.1/libexec/postfix/postfix-tls-script: interpreter directive changed from "/bin/sh" to "/nix/store/r47p5pzx52m3n34vdgqpk5rvqgm0m24m-bash-4.4-p23/bin/sh"
/nix/store/i942xg2v2mxnayj0y2q01285lcs7xil6-postfix-3.3.1/libexec/postfix/postfix-wrapper: interpreter directive changed from "/bin/sh" to "/nix/store/r47p5pzx52m3n34vdgqpk5rvqgm0m24m-bash-4.4-p23/bin/sh"
checking for references to /build in /nix/store/i942xg2v2mxnayj0y2q01285lcs7xil6-postfix-3.3.1...
moving /nix/store/i942xg2v2mxnayj0y2q01285lcs7xil6-postfix-3.3.1/sbin/* to /nix/store/i942xg2v2mxnayj0y2q01285lcs7xil6-postfix-3.3.1/bin

Success on aarch64-linux (full log)
Attempted: postfix
Partial log (click to expand)
strip is /nix/store/p9akxn2sfy4wkhqdqa3li97pc6jaz3r1-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/dmkz9hsxqwknrg4rl5gsfdc074i8r448-postfix-3.3.1/libexec  /nix/store/dmkz9hsxqwknrg4rl5gsfdc074i8r448-postfix-3.3.1/bin  /nix/store/dmkz9hsxqwknrg4rl5gsfdc074i8r448-postfix-3.3.1/sbin
patching script interpreter paths in /nix/store/dmkz9hsxqwknrg4rl5gsfdc074i8r448-postfix-3.3.1
/nix/store/dmkz9hsxqwknrg4rl5gsfdc074i8r448-postfix-3.3.1/libexec/postfix/.postfix-script-wrapped: interpreter directive changed from "/bin/sh" to "/nix/store/dsyc1z7ck08ga7l0b1jcxx35wj69qcii-bash-4.4-p23/bin/sh"
/nix/store/dmkz9hsxqwknrg4rl5gsfdc074i8r448-postfix-3.3.1/libexec/postfix/.post-install-wrapped: interpreter directive changed from "/bin/sh" to "/nix/store/dsyc1z7ck08ga7l0b1jcxx35wj69qcii-bash-4.4-p23/bin/sh"
/nix/store/dmkz9hsxqwknrg4rl5gsfdc074i8r448-postfix-3.3.1/libexec/postfix/postmulti-script: interpreter directive changed from " /bin/sh" to "/nix/store/dsyc1z7ck08ga7l0b1jcxx35wj69qcii-bash-4.4-p23/bin/sh"
/nix/store/dmkz9hsxqwknrg4rl5gsfdc074i8r448-postfix-3.3.1/libexec/postfix/postfix-wrapper: interpreter directive changed from "/bin/sh" to "/nix/store/dsyc1z7ck08ga7l0b1jcxx35wj69qcii-bash-4.4-p23/bin/sh"
/nix/store/dmkz9hsxqwknrg4rl5gsfdc074i8r448-postfix-3.3.1/libexec/postfix/postfix-tls-script: interpreter directive changed from "/bin/sh" to "/nix/store/dsyc1z7ck08ga7l0b1jcxx35wj69qcii-bash-4.4-p23/bin/sh"
checking for references to /build in /nix/store/dmkz9hsxqwknrg4rl5gsfdc074i8r448-postfix-3.3.1...
moving /nix/store/dmkz9hsxqwknrg4rl5gsfdc074i8r448-postfix-3.3.1/sbin/* to /nix/store/dmkz9hsxqwknrg4rl5gsfdc074i8r448-postfix-3.3.1/bin


DictReader has a different interface from csv.DictReader

The csv342 version of DictReader cannot accept a list of CSV lines, though the built in version in both Python 2 and Python 3 can do so. If you're interested in accepting patches, I could submit one for this issue.
csv342 on python 2.7
>>> import csv342 as csv
>>> list(csv.DictReader(['a,b', '1,2']))
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/lucaswiman/website/vendor/venv/lib/python2.7/site-packages/csv342.py", line 239, in next
    return self.__next__()
  File "/Users/lucaswiman/website/vendor/venv/lib/python2.7/site-packages/csv342.py", line 220, in __next__
    if self.fieldnames is None:
  File "/Users/lucaswiman/website/vendor/venv/lib/python2.7/site-packages/csv342.py", line 205, in fieldnames
    self._set_fieldnames_from_first_row()
  File "/Users/lucaswiman/website/vendor/venv/lib/python2.7/site-packages/csv342.py", line 199, in _set_fieldnames_from_first_row
    self._fieldnames = next(self.reader)
  File "/Users/lucaswiman/website/vendor/venv/lib/python2.7/site-packages/csv342.py", line 161, in next
    return self.__next__()
  File "/Users/lucaswiman/website/vendor/venv/lib/python2.7/site-packages/csv342.py", line 156, in __next__
    row = self.reader.next()
  File "/Users/lucaswiman/website/vendor/venv/lib/python2.7/site-packages/csv342.py", line 140, in next
    return self.__next__()
  File "/Users/lucaswiman/website/vendor/venv/lib/python2.7/site-packages/csv342.py", line 137, in __next__
    return self._text_stream.next().encode('utf-8')
AttributeError: 'list' object has no attribute 'next'

Python 3.4 (also works on 3.6)
>>> import csv
>>> list(csv.DictReader(['a,b', '1,2']))
[{'a': '1', 'b': '2'}]

Yes, please submit a patch.

Version 1.0.0 is released on PyPI.


bower install fails

Ubuntu x64 16.04 LTS
[...]
bower resolved      https://github.com/FortAwesome/Font-Awesome.git#4.7.0
bower resolved      https://github.com/jquery/jquery-dist.git#3.2.1
bower resolved      https://github.com/twbs/bootstrap.git#3.3.7
bower EHTTP         Status code of 404
npm ERR! Linux 4.4.0-93-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! node v4.2.6
npm ERR! npm  v3.5.2
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>postinstall: ./node_modules/bower/bin/bower install
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script './node_modules/bowe
r/bin/bower install'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the freestep package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     ./node_modules/bower/bin/bower install

npm-debug.log.txt

Whoops; looks like Google code going away broke some stuff. Should be fixed now.


Sequential renaming and performance improvements

I've tried to reduce FindDefinitions calls in the pipeline and it seems working at least for me.
But more testing would be useful.
Also, I've tried to implement #400 but it's quite complicated because two passes of definitions are required.

:white_check_mark: Build ConfuserEx 859 completed (commit https://github.com/mkaring/ConfuserEx/commit/48b9b7e65f by @KvanTTT)

While good for the performance, this change is a really bad idea. The problem is, that due to this change the protections that follow each other can't pick up new injected methods anymore. Also methods that got removed remain in that list.

Ok, I restored the previous behaviour but removed delegates because there is no reason to use them. Also added some microoptimizations.

:white_check_mark: Build ConfuserEx 867 completed (commit https://github.com/mkaring/ConfuserEx/commit/26dec961ec by @KvanTTT)

Ok, I'll drop controversial performance and style changes. Moreover, they are not on a hot path, thus affect performance not significantly.


Rating as 0 on stopstalk

I have solved a decent amount of problems on Codechef and HackerRank, but my rating is showing up as 0.
This has been happening for a while and this is problematic as StopStalk is being used to shortlist candidates for online contests by my uni's placement cell.

Hi @Vyvy-vi, please write to us via this link with your StopStalk handle and registered email address.

I checked an hour ago and it got updated. I'm unsure why it was stuck earlier.
Thanks for the quick response!


[SPARK-48863][SQL] Fix ClassCastException when parsing JSON with "spark.sql.json.enablePartialResults" enabled

What changes were proposed in this pull request?

This PR fixes a bug in a corner case of JSON parsing when spark.sql.json.enablePartialResults is enabled.
When running the following query with the config set to true:
select from_json('{"a":"b","c":"d"}', 'array<struct<a:string, c:int>>')

the code would fail with
org.apache.spark.SparkException: Job aborted due to stage failure: Task 0 in stage 4.0 failed 1 times, most recent failure:
Lost task 0.0 in stage 4.0 (TID 4) (ip-10-110-51-101.us-west-2.compute.internal executor driver):
java.lang.ClassCastException: class org.apache.spark.unsafe.types.UTF8String cannot be cast to class
org.apache.spark.sql.catalyst.util.ArrayData (org.apache.spark.unsafe.types.UTF8String and
org.apache.spark.sql.catalyst.util.ArrayData are in unnamed module of loader 'app')
    at org.apache.spark.sql.catalyst.expressions.BaseGenericInternalRow.getArray(rows.scala:53)
    at org.apache.spark.sql.catalyst.expressions.BaseGenericInternalRow.getArray$(rows.scala:53)
    at org.apache.spark.sql.catalyst.expressions.GenericInternalRow.getArray(rows.scala:172)
    at org.apache.spark.sql.catalyst.expressions.JsonToStructs.$anonfun$converter$2(jsonExpressions.scala:831)
    at org.apache.spark.sql.catalyst.expressions.JsonToStructs.nullSafeEval(jsonExpressions.scala:893)

The patch fixes the issue by re-throwing PartialArrayDataResultException if parsing fails in this special case.
Why are the changes needed?

Fixes the bug that would prevent users from reading objects as arrays as introduced in SPARK-19595. This is more of a special case but it works with the flag off so it would be good to fix it when the flag is on.
Does this PR introduce any user-facing change?

Yes, but it is a bug fix so it would not have worked without this patch overall.
The parsing output will be different due to the partial results improvement:
Previously, we would get null (the partial results are disabled). With this patch and partial results enabled, this will return Array([b, null]). This is not specific to this patch but rather to the partial results feature in general.
How was this patch tested?

I added a unit test.
Was this patch authored or co-authored using generative AI tooling?

No.

cc @HyukjinKwon @cloud-fan @dongjoon-hyun

Merged to master.


[Vertical compaction 3/5] support partial columns write in segment writer

#1112
Add partical columns write interface in segment writer.
In vertical compaction, the key columns will be merged and written into the rowset segments first.
Then the non-key columns are merged by groups.

run starrocks_be_unittest

It's better to give different commit message about different pull request. @wyb


Commit without git add .

The ct -c command runs git add (code). On big projects as well as while developing big features it might problematic. Would it make sense to let the ct -c only do the commit, not the adding. May be the 'adding' can be optional using come flags.
What do you think @ZeroX-DG ?

Totally agree @saneef

Yes I agree and was planing on removing git add . in the next release, thank you @MrWeb for the PR.

In the next release, the custom files flag will be available and the user can use that flag to specify the files that they want to commit.


Error on Mac

zcashd said: Error: Cannot find the Zcash network parameters in the following directory:
"/Users/sonya/Library/Application Support/ZcashParams"
Please run 'zcash-fetch-params' or './zcutil/fetch-params.sh' and then restart.

Just downloaded and opened zec-qt-wallet on my Mac for the first time. Not sure why I got this error — apparently related to zcashd, but I was under the impression that the zec-qt-wallet would handle that for me? I'm on macOS High Sierra 10.13.6, if that's helpful.

I'm curious have you ever run zcashd on this Mac before? Do you have an existing conf file in "/Users/sonya/Library/Application Support/Zcash/zcash.conf"?
That error is from zcashd which is shown by zec-qt-wallet but yeh it should (and does normally) download the params.

I'm guessing that zec-qt-wallet didn't download the params (it should have), which is why you're seeing this error.
Can you check a couple of things for me?

Is there anything in the /Users/sonya/Library/Application Support/ZcashParams directory?
Do you have a zcash.conf in /Users/sonya/Library/Application Support/Zcash/zcash.conf?

In /Users/sonya/Library/Application Support/ZcashParams:

sapling-output.params
sapling-spend.params
sprout-groth16.params
sprout-verifying.key

And yep, /Users/sonya/Library/Application Support/Zcash/ contains zcash.conf.

Very interesting. For some reason, you're missing the sprout-proving.key from https://z.cash/downloads/sprout-proving.key
I wonder why. I'm working on a build that will log what zec-qt-wallet sees, so we can get to the bottom of this. Give me a few minutes.

OK, So I think I know what's happening here, and maybe in #49. zec-qt-wallet sees your zcash.conf, assumes that you've already downloaded the params and tries to start zcashd. But one of the params is missing, so zcashd doesn't start, and zec-qt-wallet is confused.
Maybe zec-qt-wallet should check the params exist even if zcash.conf is present, to ensure everything is fine.

@sonyamann Thanks for helping us get to the bottom of this issue. The problem should (hopefully) be fixed in the newest release here: https://github.com/ZcashFoundation/zec-qt-wallet/releases/tag/0.4.1
Please let us know if it works!

0.4.1 crashes on launch due to hardcoded path, I believe.
Crashed Thread:        0
Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Reason:    DYLD, [0x1] Library missing

Application Specific Information:
dyld: launch, loading dependent libraries

Dyld Error Message:
  Library not loaded: @rpath/QtWidgets.framework/Versions/5/QtWidgets
  Referenced from: /Applications/zec-qt-wallet.app/Contents/MacOS/zec-qt-wallet
  Reason: image not found

Also, the DMG is not signed by an identified developer. This is the first time I get this error message for your builds.

The missing of the sprout-proving.key could be related to https://github.com/zcash/zcash/issues/3652

@rex4539 Thanks for catching that. I was using a different dmg generation tool, and it looks like it doesn't work everywhere. I've reverted the 0.4.1 binary on the releases page back to the old way.

Thank you all for looking into this. Should I uninstall and re-download?

Yes please. Download the new build, install it and it should hopefully download the missing files
https://github.com/ZcashFoundation/zec-qt-wallet/releases/tag/0.4.1

Closing this since it seems like it was fixed in v0.4.1


Create heading

🚀 What is the feature?
Create a html heading for the app, such that people know, that this app is all about. Feel free to be creative. 🕺
ℹ Additional info
Add a screenshot of your changes - if helpful.
Make sure the app works, otherwise the PR cannot be approved.
Link the PR with this issue (in the right panel "Development" -> select issue).

I would like to have this done. If I can be assigned,please!

Sure, I'll assign you :)


Remove spaces in SubResource()/ExtResource/Resource() in text resources

Split from https://github.com/godotengine/godot/pull/32124.
These spaces are not needed for the file to be successfully parsed.
Other types such as Vector3 are no longer serialized with spaces after the opening parenthesis and before the closing parenthesis, so this is also more consistent.
This is technically cherry-pickable to 3.x, but I don't recommend doing so due to the large VCS diffs it can generate (and because Variant types in 3.x are serialized with extraneous spaces).

Thanks!


Control Nodes suffer from jittering when resized using non default anchoring

Godot version
4.1.1.stable ( and  mono ) , 4.2 dev3 ( and mono ) , 4.0 have been tested.
System information
Fedora Linux 38 (Workstation Edition)
Issue description
When a Control node is not left in its default anchor state ( that being anchored to top left ), It will "jitter" when "Custom minimum size" is used to resize it.
Which is an issue since for some reason using the regular "size" will not expand a control node from its centre if using centre anchoring, will not expand leftwards when using top right anchoring, etc.. if intentional i cannot grasp the reason for this, although i'm sure there might be a valid reason to do so. Using custom minimum size is also inconvenient as it messes with animations.
Demo video (zoomed in for clarity )
https://github.com/godotengine/godot/assets/74463310/0c3ee954-d14d-4547-870c-4e709c056900
Steps to reproduce
The minimal reproduction project is as slim as possible and straightforward as possible, to use it simply play the animation player in the only provided scene and the "jitter" can be clearly seen along with labels pointing to its exact location
Minimal reproduction project
Control_Jitter_min_rep_project.zip

I also have this issue, its really messing up my workflow

i managed to fix my jitter issue just by casting the final value assign to an int, seem like the ui system or VBoxContainer have some issue with floating size. not sure if that would fix yours, but you can try to cast to int.

Controls are snapped to integer pixels by default. You can disable this behaviour in the Project Settings by disabling Snap Controls to Pixels, but this can make controls look less crisp.

Im aware of this functionality but it does not stop this issue cropping up in the slightest, as you can see when its disabled the jitter simply seems to have more steps ( which would be sub-pixel now ) but is still there and still a problem for any minimally complex resizing UI
https://github.com/godotengine/godot/assets/74463310/976c5ea6-7809-47de-ad09-55e0d320589a


Use snprintf instead of _snprintf on Windows

_snprintf does not guarantee null termination if the size argument is too small.
Starting with VS2015, the UCRT provides a C99-compliant snprintf. Use it, and
also fix a related issue where _dispatch_client_assert_fail was passing a
too-small size.

cc @MadCoder @compnerd

@swift-ci please test

ping @MadCoder


App doesn't open when we first use it

When participants FIRST logged into the app during Visit 1, the app didn't not open. We went to File --> Exit and re-opened the app, which worked. This was the case for all 6 pilot participants.

In order to log in you have to use the app, which means it must have been open. Are you referring to emWave not opening?

After participants clicked the app icon on desktop and entered their email and pwd, the app tried to open. We saw a beige window open with a spinning circle in it. Since the spinning circle was there for a long time and nothing happened, we exited the app and reopened it, which worked (meaning the we saw the first slide with the instructions for 5-min rest).

This issue is not urgent because the app always opened the second time.

This issue is also present in 1.0.2 version; however, like Kaoru commented it does work when you exit and relaunch the app

I encountered the same issue again today. App works after exiting and restarting.


Replace occurences of first boolean with iterator enumerate (codegen)

This takes advantage of Rusts iterators, to remove the need of an extra boolean to track the first entry in a loop. This also removes an else branch to set the boolean state. There is one instance in codegen_function where this method may need some tweaks, but it was left as-is.

I believe that did the job

occurances -> occurrences
No need to say "squash" in the commit message
This has a conflict

Oh whoops! This is also my first PR, so I'm new to the process. The recent commits have made additions to codegen, so I need to update it.

please squash these again

I can't seem to squash down to a single commit (any further than I have) because of the merge from the latest commits.

Will the current squashed version work or does it need to go further? The re-merge with main makes it so I can't squash it down any further. Is there a way to go further or will this work? I'm still new to PRs.

Will the current squashed version work or does it need to go further?

No merge or fixup commits please :)

I won't be able to do much more at this point, as it's now 4am. What's the next step because I'm not sure how to get this merged. Do I just reimplement my changes on the latest and submit another PR? I can't squash the commits down any more than it is, so I'm not sure what else to do.
It was submitted not long before a bunch of changes to the codegen, so it had conflicts. I managed to merge the latest to fix all the conflicts, so the squash won't work because I needed to pull in the latest.
Could you elaborate on what is required, as I'm not sure how to proceed without starting a new fork and PR.

I'm going to close this as it isn't really a significant change.


Project fails when loaded into VS

When 0.1.2 is loaded into VS, users get the following stack:
2>C:\Users\david\.nuget\packages\ionide.keepachangelog.tasks\0.1.2\build\Ionide.KeepAChangelog.Tasks.targets(14,9): error MSB4018: The "Ionide.KeepAChangelog.Tasks.ParseChangeLogs" task failed unexpectedly.
2>C:\Users\david\.nuget\packages\ionide.keepachangelog.tasks\0.1.2\build\Ionide.KeepAChangelog.Tasks.targets(14,9): error MSB4018: System.IO.FileNotFoundException: Could not load file or assembly 'FSharp.Core, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
2>C:\Users\david\.nuget\packages\ionide.keepachangelog.tasks\0.1.2\build\Ionide.KeepAChangelog.Tasks.targets(14,9): error MSB4018: File name: 'FSharp.Core, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
2>C:\Users\david\.nuget\packages\ionide.keepachangelog.tasks\0.1.2\build\Ionide.KeepAChangelog.Tasks.targets(14,9): error MSB4018:    at Ionide.KeepAChangelog.Parser.parseChangeLog(FileInfo file)
2>C:\Users\david\.nuget\packages\ionide.keepachangelog.tasks\0.1.2\build\Ionide.KeepAChangelog.Tasks.targets(14,9): error MSB4018:    at KeepAChangelog.Tasks.ParseChangelogs.Execute() in /_//src/Ionide.KeepAChangelog.Tasks/Library.fs:line 117
2>C:\Users\david\.nuget\packages\ionide.keepachangelog.tasks\0.1.2\build\Ionide.KeepAChangelog.Tasks.targets(14,9): error MSB4018:    at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
2>C:\Users\david\.nuget\packages\ionide.keepachangelog.tasks\0.1.2\build\Ionide.KeepAChangelog.Tasks.targets(14,9): error MSB4018:    at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__26.MoveNext()
2>C:\Users\david\.nuget\packages\ionide.keepachangelog.tasks\0.1.2\build\Ionide.KeepAChangelog.Tasks.targets(14,9): error MSB4018:
...

IMO this is because we need to support full-framework MSBuild targets. The vs-support branch tracks this need.

Alternative idea - for net472 don't bundle fsharp.core at all and see if the ambient one from VS is picked up?


Wi-Fi Error in diagnostics. No MAC.

Tested in the following scenario.
While plugged into ethernet and wi-fi not setup.
Two of my hotspots v2 version exhibit an error with the Wi-Fi adapter.
WLAN0 MAC | FF:FF:FF:FF:FF:FF
Top LED starts flashing fast.
Firmware is 2<IP_ADDRESS>
Shawaj says:
"I might be wrong but I think the WiFi Mac is a soft Mac and not fixed. So could be software." as I think it may also be software related. This is because if either hotspot is rebooted the MAC is found again and no error for a period of time.
Issue is related to the hotspots in this ticket: 245083

Related to https://github.com/NebraLtd/helium-miner-software/issues/72

Related to https://github.com/NebraLtd/hm-diag/issues/142


How to add different attributes to a label during cascade mask-rcnn hrnet model training?

Hi -
I'm using CVAT tool to create annotations for Safety Data Sheets (SDS) Hazard Pictograms. There are nine pictograms - all have the shape of a Rombus. But each of these 9 images has different names (in other words attributes) - [example: exclamation, flammable, acid, bottle etc.]. CVAT has a mechanism to add attributes to a label. I have only one label (class) which is "pictogram". And I'm adding 9 attributes to this label so that during annotation I can clearly specify the attribute for that picture.
I'm using mmdetection v2.5.0 for training Cascade Mask R-CNN HRNet model to detect the pictograms and its attributes. My annotation file takes the COCO JSON format.
Question:
How do I specify to the training about the label attributes? This is the config file I'm using for training - "cascade_mask_rcnn_hrnetv2p_w40_20e.py", and I have mentioned "classes = [pictogram]" in this config file. I'm not sure how to also specify the attributes so that the model can learn and report the label as well as its attribute when an image is given. Hope you can guide me.
Thanks,
Sekhar H.

We may consider making it a future feature to support multi-label for a single instance, recently there are several issues with this feature. @ZwwWayne @hhaAndroid @RangiLyu

About how to pass a new attribute of instance, you may refer to #5337

Feel free to reopen the issue if there is any question


[FLINK-29646][sql-gateway] rest endpoint return a simpler error message

What is the purpose of the change
this pull request make sql-gateway  fetch key error information instead of return all stack of information, when operation happen error
Brief change log

Modify the method ExceptionUtils.stringifyException and add a parameter to return only root information
AbstractSqlGatewayRestHandler adds a handleException method to catch SqlGatewayException so that it only returns key information to the client

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no)
The S3 file system connector: (no )

Documentation

Does this pull request introduce a new feature? ( no)
If yes, how is the feature documented? (not applicable )

Thanks for your contribution @huyuanfeng2018. I think this pull request should be merged into master branch rather than release-1.16.

Thanks for your contribution @huyuanfeng2018. I think this pull request should be merged into master branch rather than release-1.16.

Thanks @WencongLiu  , I have switched to master

-1. If you only want the root exception to be converted to a string, then only pass the root exception to said util.


NativeScript encountered a fatal error: Error: Value is not a class

I am using your sample code from readme.md for ios.
And I got current error after launching app.
full error text
***** Fatal JavaScript exception - application has been terminated. *****
Native stack trace:
1   0x1011bb73c NativeScript::reportFatalErrorBeforeShutdown(JSC::ExecState*, JSC::Exception*, bool, bool)
2   0x1011ec068 -[TNSRuntime executeModule:referredBy:]
3   0x1005cc748
4   0x184d7dfc0
JavaScript stack trace:
1   NSStringFromClass@file:///app/vendor.js:17108:83
2   start@file:///app/vendor.js:17108:83
3   run@file:///app/vendor.js:17143:8
4   $start@file:///app/vendor.js:16333:18
5   @file:///app/bundle.js:2487:10
6   ./app.ts@file:///app/bundle.js:2492:34
7   webpack_require@file:///app/bundle.js:76:34
8   checkDeferredModules@file:///app/bundle.js:45:42
9   @file:///app/bundle.js:149:38
10  anonymous@file:///app/bundle.js:150:12
11  evaluate@[native code]
12  moduleEvaluation@[native code]
13  @[native code]
14  promiseReactionJob@[native code]
15  require@[native code]
16  anonymous@file:///app/starter.js:2:8
17  evaluate@[native code]
18  moduleEvaluation@[native code]
19  @[native code]
20  promiseReactionJob@[native code]
JavaScript error:
file:///app/vendor.js:17108:83: JS ERROR Error: Value is not a class.
*** JavaScript call stack:
(
)
*** Terminating app due to uncaught exception 'NativeScript encountered a fatal error: Error: Value is not a class.
at
1   NSStringFromClass@file:///app/vendor.js:17108:83
2   start@file:///app/vendor.js:17108:83
3   run@file:///app/vendor.js:17143:8
4   $start@file:///app/vendor.js:16333:18
5   @file:///app/bundle.js:2487:10
6   ./app.ts@file:///app/bundle.js:2492:34
7   webpack_require@file:///app/bundle.js:76:34
8   checkDeferredModules@file:///app/bundle.js:45:42
9   @file:///app/bundle.js:149:38
10  anonymous@file:///app/bundle.js:150:12
11  evaluate@[native code]
12  moduleEvaluation@[native code]
13  @[native code]
14  promiseReactionJob@[native code]
15  require@[native code]
16  anonymous@file:///app/starter.js:2:8
17  evaluate@[native code]
18  moduleEvaluation@[native code]
19  @[native code]
20  promiseReactionJob@[native code]
', reason: '(null)'
*** First throw call stack:
(0x185426d8c 0x1845e05ec 0x1011bbe60 0x1011ec068 0x1005cc748 0x184d7dfc0)

JS ERROR Error: Value is not a class.

And I don't think I use the symbol Value anywhere in my code.

now I have got this one
'NativeScript encountered a fatal error: TypeError: Attempted to assign to readonly property.

@karo-dc you ever fixed that  readonly property error ? i just updated my nativescript app to 5.3 and it hit me just like that, only on IOS , android is working fine


Mentioned users not notified

When using postMessageToChannel and @ mentioning someone they aren't receiving a notification.

I've also tried <@wadewegner|Wade Wegner> in the message, and while that sends me a notification it also doesn't render properly:

And if I use <@wadewegner|WadeWegner> I get no notification.

Marginal improvement. Passing in link_names: 'true' as params ...
const params = {
  link_names: 'true'
};

... and the following  <@wadewegner|Wade Wegner> results in a linked username for me ...

... but still isn't formatted correctly.

Also, it's interesting to note that the following two formats work correctly for channel:
<!channel>
<!channel|channel>

Okay ... so, looks like turning link_names to true makes the standard @wadewegner work. Huh. That was quite the journey.

Okay, maybe not.
Here's some sample text: const message = 'I found a :neutral_face: [excitement (99.7%)] tweet! (FYI @wadewegner.)';
Now it's not notifying me.

If I change the sample text to const message = 'I found a :neutral_face: [excitement (99.7%)] tweet! (FYI @wadewegner .)'; (notice the space after @wadewegner) it works.

Thanks @wadewegner for all debug ;) just what i was looking for ehehhe

@wadewegner does it still work? I used your solution but it isn't working for me

Passing link_names: true worked for me. The bot wasn't able to create links to other channels until I added that like so:
bot.postMessage( event.channel, response, {
    as_user: true,
    link_names: true
} );


Improve workflow for automatic/manual verification of new OSC Collectives

As the host admin of the Open Source Collective, I get an email whenever a new Collective applies to join. There are a couple issues.

It's not clear if the user has come through the workflow where the system verifies that they are a legit core contributor of the Collective they are representing, or if they have gone through the create Collective flow without verification. This is important because we risk allowing an unverified user to claim a Collective they don't have a right to claim.
The email doesn't show if the Collective was already automatically approved, or if I need to manually approve them from the email link - the email includes a big "approve" button so it looks like action needs to be taken. But checking some of them, it seems they are actually already approved. I don't want to receive these emails if there's no action required. But if a Collective needs manual approval, I need to be notified.

@znarf @Betree - is there a workaround that would let me see Collective applications to Open Source Collective that have not already been automatically approved? Because right now, it's not feasible for me to check each email notification manually (the vast majority are already auto-approved), which means that no one gets back to Collectives that have not been automatically approved to manually verify the Collective or suggest a different host.

I don't see any, but creating a very simple page that list all pending applications with "Approve" / "Decline" buttons should take no time. @alannallama would that work for you?

Yes, that would be great. So it would only show the ones that aren't
automatically approved, right?
--
Alanna Irving
<EMAIL_ADDRESS>https://alanna.space
On Tue, 23 Apr 2019 at 17:55, Benjamin Piouffle<EMAIL_ADDRESS>wrote:

I don't see any, but creating a very simple page that list all pending
applications with "Approve" / "Decline" buttons should take no time.
@alannallama https://github.com/alannallama would that work for you?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/opencollective/opencollective/issues/1768#issuecomment-485653911,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABJ6P7TJXXZQXYIXIBVJVBDPR2QFTANCNFSM4G2ZHJWQ
.

@alannallama Yes, it will only show the ones that are not approved yet.
I've made a first version but I saw that we don't have a rejectCollective function yet. Do you often reject collective's application? If you do, what's the process? What information do you need to make the decision?
Current state:

@Betree we don't reject Collectives currently. We just only accept them if they meet the host criteria, and otherwise take no action. I think for this MVP version we can leave that as-is.
In the future, it might be worth building a reject function, especially if we can add a message explaining why the Collective was not accepted, and what they can do now (e.g. apply to another host and how to do that). Currently I fulfil this function by writing the applicant an email. It's OK for the time being as the volume is not high.

Thanks for the details, I'll ship it this week


Audio device is remembered but ignored when starting up.

OS: Windows 10
Issue Descriptions:
When selecting an audio device, gpmd will correctly use that audio device.
However when I close gpmd and reopen it, it will use the default audio device again,
when going to the audio device selection it does show the prefered audio device though,
reselecting it does again use the correct audio device.
Steps to Reproduce:

Select non default audio device
close gpmd
reopen gpmd

Images:
When manually resetting the audio device: http://imgur.com/H3qVfWK
the music comes from the correct audio device as seen in voicemeeter
When restarting gpmd: http://imgur.com/WLC6Nqo
the music comes from the main audio device even though the gpmd audio device selection says it's using another one.
in both cases music was playing.  The audio devices, which are virtual, are at all times present.

This is strange, because it works correctly on my machine and on other machines running Windows 10.
What audio device are you attempting to output to?

As can be seen in the linked images, it's just my builtin audio device with some virtual cables to be able to separate my audio in groups.  I'll try to test it on my laptop to see if it has the same behaviour.

Hmm, I've never tried with Virtual Audio Cables.
I'll give that a go when I have time and if you can try on your laptop that would be great 👍

Please update the issue with more information when you can


Use Cases Page

Closes #30, introducing the preliminary Use Cases Page (hero and body content rows without use case cards below).
Notes:

Just noticed that the faq page commit is accidentally included in this branch/PR. I'm anticipating that FAQs will be merged in first, but if not (or if this causes problems) I can re-open this PR branching directly off of master. Keep me posted.

@lougroshek Use Cases url added ✅
As for the blurry images, these aren't placeholders – does the problem go away after a gatsby clean ?


Add new function doc for 'sentenseCase', 'titleCase'

pr link:
C# https://github.com/microsoft/botbuilder-dotnet/pull/3994
js https://github.com/microsoft/botbuilder-js/pull/2286

Closing now that the PR has been merged into the R10 branch.


[Autocomplete] Value is not nulalble

[ x ] The issue is present in the latest release.
[ x ] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
When setting the value of a controlled Autocomplete component (like in the example Controllable States) I get an error saying null is not assignable to the value field of my Autocomplete:
Type 'null' is not assignable to type 'MyObject| undefined' .ts(2322)

Expected Behavior 🤔
I should be able to set the value props to null, in order for my component to be controlled.
Steps to Reproduce 🕹
I will deliver steps to reproduce later, if needed.

Context 🔦
I should be able to set the value of the field to null, because I need to component to be controlled. If I leave the field undefined, my Autocomplete component will be uncontrolled and I can not switch it easily later.
Your Environment 🌎

Tech
Version

Material-UI
v4.9.12

React
16.13.0

Browser
MS Edge Dev

TypeScript
3.8.3

etc.

Actually, I found the bug and it was on my side 🤦

@eluchsinger I have the same problem right now, so I'm curious what the error was on your side please?
I cannot seem to find a way to have the state to be controlled while at the same time, having the options load asynchronously.

@kizivat I am sorry, I don't remember what it was.
The error occurred when I updated from an old Material-UI Lab version to the latest. I may have to do that on an other project and if I face the same issue again, I will make sure to document it here.

Hey there! I had the same issue, and in my case, it was because the Autocomplete prop disableClearable was set to true.

To fix this, I just removed the disableClearable prop.

Obs: this solution made the button to clear the Autocomplete appear again (something I don't want in my case). To hide this button, I set clearIcon={null}


docs: Remove references to InstanceTag

What
This change removes references to InstanceTag in the examples.
Why

This property doesn't need to be set. The SDK will generate a default if you don't provide it. Removing it simplifies the examples.

This property is never explained anywhere in the readme, so it can
be hard to know what it does and what it's used for. Additionally, the
name InstanceTag is different from the InstanceId that other SDKs
use, making it confusing even to people somewhat familiar with Unleash.

Yeah, I agree. The instanceId is documented in some of the SDKs, but not as a general thing. Probably belongs on the SDK landing page, actually.


Non Yarn way to install this software

Is there a non-yarn way to install this software. I spent about 3 hours trying to get this installed because the app store doesn't work and the login goes to a bad url.
I have about had it with new frameworks people. Pick one and stay with it.

I had the same issue but i was able to get it to run with the appimage on linux. just download, change to executable and open it. there is also an exe and dmg which i would image work just as easy for windows and mac: https://github.com/getstation/desktop-app/releases/tag/v2.0.9

Fixed in 2.1.0


Extract reserved-account-keys crate

Problem

solana_sdk::reserved_account_keys blocks moving out solana_sdk::transaction
It would be good to be able to use important program IDs without importing heavy dependencies or inlining them

Summary of Changes

Extract reserved-account-keys-crate and re-export for backwards compatibility
For every ID definition imported by reserved-account-keys, move that definition to reserved-account-keys and re-export it where it used to be
Make std optional in the new crate. When no features are enabled, the new crate is just a bunch of ID definitions and it compiles very quickly, so there is no noticeable difference in compile time to any crate that pulls its own ID definition from reserved-account-keys

This branches off #3140 so that needs to be merged first

This might be cleaner as two separate crates? One that just contains the ID declarations (perhaps solana-sdk-ids) and another containing ReservedAccountKeys &co.
This would avoid having to do all the feature and target_os stuff that ended up being uglier than I expected

This might be cleaner as two separate crates? One that just contains the ID declarations (perhaps solana-sdk-ids

I see there is already a deprecated solana_program::sdk_ids module so the name would clash. But no other name comes to mind and it wouldn't be the worst thing to clash with

Ok ended up having no choice but two make it two crates because there was a circular dependency when everything was in reserved-account-keys


Candidate possibilities link

Upcoming TODO's

Enhanced search query
Selection of possibilities
Making sure that we delete the possibilities table once we have a verified twitter handle
If we update the TwitterLinkPossibilities model, then we'll need to go through and recalculate the percentages This is probably really important and I will try to change this, otherwise the UI isn't really reflective of the percentages.

@DaleMcGrew please let me know what other ideas you may have.

Thank you @danielvdao, I am pulling this into the develop branch.


Remove branch name from dependency cache

Pull Request Test Coverage Report for Build 671

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 99.741%

Totals

Change from base Build 665:
0.0%

Covered Lines:
286

Relevant Lines:
286

💛  - Coveralls


Make it possible to set a fast field normalizer for JsonOptions and the dynamic mode.

@PSeitz  Can you connect the dots and edit the QuickwitJsonOptions to forward that info to tantivy?

Related https://github.com/quickwit-oss/quickwit/issues/3246

Can we close this?

yes


Brand new project can't build with distillery

After generating a brand new project with mix kitto.new my_dashboard --edge, and adding the distillery dependency, the application can't run:
_build/prod/rel/my_dashboard/bin/my_dashboard foreground
15:53:45.443 [info] Starting Kitto server, listening on <IP_ADDRESS>:4000
/Users/david/Projects/cage/cd_dash/_build/prod/rel/cd_dash/releases/0.0.1/cd_dash.sh: line 723: 83237 Segmentation fault: 11  "$@" -- ${1+$ARGS}

Shutting down..
Node is not running!

Dependencies:
defp deps do
   [
      {:kitto, github: "kittoframework/kitto", branch: "master"},
      {:distillery, "1.3.1"}
   ]
end

Compiled binary with env MIX_ENV=prod mix release --env=prod

Seems like it was an issue with the env MIX_ENV=prod part of the command. Recompiled and now it works.


Add wharley ornelas no Update README.md

Add nodejs devs

Great,@wharley!
Thanks by your contribution.


Fix package dependency

PublicApiGenerator package dependency was wrongly pointing to v1.0.0

Done with fe6ca29087490415b0aa79bfbc6084dd619e2ea9

6.1,6.2 and 6.3 have been unlisted from nuget


Typescript compiler complaining about "assign" usage.

Bug or feature request?
Bug
Description:
Following fairly closely the TODO example the following code won't accept what I wrote for the "onEntry":
import { Machine, actions, EventObject } from "xstate";
const { assign } = actions;

export interface TagContext {
    title: string;
    previousTitle: string | null;
}

export type EventId = "COMMIT";
export interface TagEvent extends EventObject {
  type: EventId;
}

export const TagMachine = Machine<TagContext,any,TagEvent>({
    id: "tag",
    initial: "editing",
    context: {
        previousTitle: null,
        title: ""
    },
    states: {
        editing: {
            onEntry: assign({ previousTitle: ctx => ctx.title }),
            on: {
                COMMIT: {
                    target: "viewing"
                }
            }
        }
    }
})

(Bug) Expected result:
Should compile
(Bug) Actual result:
Argument of type '{ previousTitle: (ctx: TagContext) => string; }' is not assignable to parameter of type 'Assigner<{ previousTitle: string; }, TagEvent> | Partial<{ previousTitle: string | ((context: { previousTitle: string; }, event: TagEvent) => string); }>'.
Type '{ previousTitle: (ctx: TagContext) => string; }' is not assignable to type 'Partial<{ previousTitle: string | ((context: { previousTitle: string; }, event: TagEvent) => string); }>'.
    Types of property 'previousTitle' are incompatible.
      Type '(ctx: TagContext) => string' is not assignable to type 'string | ((context: { previousTitle: string; }, event: TagEvent) => string) | undefined'.
        Type '(ctx: TagContext) => string' is not assignable to type '(context: { previousTitle: string; }, event: TagEvent) => string'.
          Types of parameters 'ctx' and 'context' are incompatible.
            Property 'title' is missing in type '{ previousTitle: string; }' but required in type 'TagContext'.ts(2345)

(Bug) Potential fix:
Somewhere the type definition derails, but I am not actually sure where.
This is typescript 3.4.5 and xstate 4.5.0

Workaround:
onEntry: assign<TagContext>({
  // your assignments here
})

Could this be documented somehow in the ts guide ?

It is, the docs just aren't published yet: https://github.com/davidkpiano/xstate/blob/master/docs/guides/context.md#typescript

Thank you 🙏

t is, the docs just aren't published yet:

I think that this has been removed from the docs in the meantime?
I can't find any reference to assign in the TypeScript guide.


Crouton installation "Failed to download debootstrap." error

Hello people, I recently downloaded ubuntu, and it was working fine, until after logging out I couldn't log back in. So, I decided to powerwash my computer, (as I was facing storage issues) and re-install ubuntu. However, I keep running into this error!
When I put in "sudo sh ~/Downloads/crouton -t unity" I get
Installing xenial-amd64 chroot to /usr/local/chroots/xenial
Downloading latest debootstrap...
Download from Debian gitweb failed. Trying latest release...
https://sources.debian.net/api/src/debootstrap/:
2017-06-19 20:46:15 ERROR 500: Internal Server Error.
Failed to download debootstrap.
Check your internet connection or proxy settings and try again.
I am a noob to both this site and Ubuntu, and all this tech and command stuff, so I have no clue what to do. Also, please speak English, as I don't know what a "crosh" even is...
Any assistance will be appreciated, thank you.

I can confirm the same behavior for me. I have no proxy running, and internet connection is fine. I used a web browser to successfully access ftp://ftp.debian.org
I read some previous issues of simple typographical errors in the scripts pulling these ftp files, so may be a quick fix?!?!
Any help is appreciated. Thanks!

Okay, I've re-enabled gitweb downloading, so try crouton again.  @yuwash, are the debian APIs not reliable at the moment?

Just ran command again. Same result.

Just tried again; seems to be working.

Yeah, crouton only re-downloads the installer once every 30 minutes.  You can also force a re-download by removing the cache: rm -rf /tmp/crouton-installer-cache.

@dnschneid Thank you for the sorta-assistance, my dear sir.

Going to keep this open, awaiting @yuwash's insights.

It seem to be working now, but I have no idea about any recent uptime issues of that api. To test, the following
d_api='https://sources.debian.net/api/src/debootstrap/'
f="$(wget -O- --no-verbose --timeout=60 -t2 "$d_api" | sed -ne 's ^.*\"version\":\ \"\([0-9.]*\)\".*$ debootstrap_\1.tar.gz p' | sort -V | tail -n 1)"
d='http://httpredir.debian.org/debian/pool/main/d/debootstrap/'
wget --no-verbose --timeout=60 -t2 "$d$f"

should result in
2017-06-21 20:11:00 URL:https://sources.debian.net/api/src/debootstrap/ [1354/1354] -> "-" [1]
2017-06-21 20:13:22 URL:http://cdn-fastly.deb.debian.org/debian/pool/main/d/debootstrap/debootstrap_1.0.90.tar.gz [69936/69936] -> "debootstrap_1.0.90.tar.gz" [1]

Same problem here, but I tried everything!

Hi everyone,
At this moment I'm trying to install the gnome desktop environment through crouton.
Enter the following command in the terminal sudo sh ~/Downloads/crouton -t gnome ends up with the following ouput:
Installing xenial-amd64 chroot to /usr/local/chroots/xenial
Downloading debootstrap 1.0.101...
################################################################################################################################################ 100.0%
curl: (22) The requested URL returned error: 404 Not Found
Failed to download debootstrap.
Check your internet connection or proxy settings and try again.
Apparently the requested debootstrap version is not present. It would be very appreciated if somebody could help me out on this.
Thanks in advance!

I'm having the same problem as well.  I deleted the cache, but I'm receiving 404 errors when trying to install it.

same here, leaving on a trip and wanted a small comp to take with me. Guess not.

I’ve tried...
Sudo sh ~/Downloads/crouton -t unity
(Xfce) (gnome)
They all say failed to download debootstrap.
Check your internet connection or proxy settings and try again.
I am Using a acer chromebook and just want to install Ubuntu so I can play RuneScape through it.
Very new to this but I do know how to get into developer mode and download crouton to begin trying to download Ubuntu but don’t seem to be getting anywhere! It use to work before xfce and unity but now I can’t get any to install through crosh/shell ??
Be great if some one could help getting really annoyed lol... 👍🏻

debootstrap is missing from the debian mirrors. I tried downloading it and passing in the -f option but thats not what -f is really used for.

All,
A fix had been merged now that seems to address the problem.
You can do a quick test with something like the following: crouton -r xenial -d -f xenial.bs
If that completes successfully then you can use the '.bs' bootstrap file to install your new chroot with something like this: sudo sh ~/Downloads/crouton -n xenial -f xenial.bs -t ....
-DennisLfromGA


Add Registry Type to Registry Contract or Fork Under SubAccount

Problem
Currently we cannot fund individuals or components.
User Story(s):
As a supporter, I want to donate to individuals and components, so that there isnt the friction of just supporting proejcts
Description
Need a different registry contract, or specify registry type on registry
Acceptance Criteria

specify registry type on registyr contract
set admins for each registry
need to chagne add project to registrer and specify registry type/int
need to change the front end for project registry and filter based on registry type

Limitations

how to make a profile for a compoennt, should we just use existing component metadata
current registry contract may not be compatible to just speicfy registry type in standardized way.

Resources

outline links and relevant resources, references implementations

Idk about the need to differentiate between a project and an individual, as in the end both of them are just an account ID.
I also don't know about components having profiles. What is the user story there? If it's about the builders of the components receiving funding, I'd say the builders should have profiles.


Set notifier version to version of bugsnag-atom

The version number in notifier.version should be the version of the notifier library, rather than the version of the app, which is stored in each event's app.version. Do you automate updating the version in some way? If so I'll amend the PR to update that as well.

I'm not quite sure how the test suite should be handled, though I updated the test for the reporter.

Sorry we missed this. To answer your question about LIB_VERSION, the version of the package can be obtained from the package.json here:
https://github.com/atom/exception-reporting/blob/master/package.json#L4
It is updated in an automated fashion.
To ensure that I understand what's intended here, you want to update the notifier version to be the version of the exception-reporting package because the app version is already reported? The app version is always more accurate for our purposes because while a certain version of exception-reporting may be shared across multiple versions of Atom, a particular app version will only have one version of exception-reporting that matches it.
(In any case, I've put this in the queue for review and see about getting other :eyes: than mine on it :grinning:)

Thanks, @lee-dohm!

To ensure that I understand what's intended here, you want to update the notifier version to be the version of the exception-reporting package because the app version is already reported?

Correct. The notifier properties should be about the exception reporting library itself - it might be the same between versions of atom.
As an example use case, if you were to use the Bugsnag dashboard or API to determine if a new version of the exception-reporting library broke something, or which version introduced a bug, it currently can't be distinguished from the version of atom itself. This probably doesn't make sense as the exception-reporting library has a different release schedule.

The app version is always more accurate for our purposes because while a certain version of exception-reporting may be shared across multiple versions of Atom, a particular app version will only have one version of exception-reporting that matches it.

I think I understand this, but to clarify, notifier.version is used for some debugging purpose by the atom team and is preferred to the app.version property? Would it be useful to have the version of exception-reporting used available as well during triage?

Each version of Atom uses a specific version of each package that is included in the application. For example, you can find exception-reporting here:
https://github.com/atom/atom/blob/a084882cb130fa6f7ffe51a88ebd140292bf4f03/package.json#L91
So while the exception-reporting package has a different release schedule, if we have the Atom version, we can always backtrack to the specific exception-reporting package version if necessary.
Personally, I'm leery of changing the meaning of metadata without changing the name of it because it means that one can't compare data across the breaking point. There is the data set before the change and the data set after the change, but you can't compare the two directly (without excluding the item that was changed from the analysis).

So while the exception-reporting package has a different release schedule, if we have the Atom version, we can always backtrack to the specific exception-reporting package version if necessary.

Gotcha, I think we thought of this library two different ways, one as an immutable part of an atom release and on the other hand as a replaceable component, where someone could test or use a different version of exception-reporting.

Personally, I'm leery of changing the meaning of metadata without changing the name of it because it means that one can't compare data across the breaking point. There is the data set before the change and the data set after the change, but you can't compare the two directly (without excluding the item that was changed from the analysis).

That makes sense. To be clear, this is not changing the app version which you see in Bugsnag. Unless there is already an integration in place using notifier.version directly (which would have to be using the API), the net effect of changing this is the possibility of Bugsnag tracking the error rate from a particular notifier library and assisting with problems. There were supposedly 200+ versions of the exception-reporting library in use in the last month or so (one for every development version of atom which has reported an error, i.e. "1.6.0-dev-52cab67"), which led me to believe there was a problem with the Atom integration which I should investigate. This is what led me to make the change.

@kattrali Cool, thank you for taking the time to explain it! I'll see about getting one of the other devs that is perhaps more familiar with how we view the data to take a peek. Thanks so much for following up :bow:

Thank you for taking a look!

Looks good to me, specs are green, merging. Thanks for this!

This change is in exception-reporting v0.38.0, and will be in atom 1.8 beta. It will be some weeks before the change is reflected in stable.

Thanks all!


BUG: Text Correction - Repetition and Inaccuracy in Footer & Navbar

Is there an existing issue for this?

[X] I have searched the existing issues

What went down?

The section heading in footer must not be "About", as it isn't just talking about "About" section. Rather, it must be called "Visit" or "Check out" or "Pages".
Also, the navbar doesn't seem to have "About" option. That is commonly seen in many sites, and it was also one of the first things I searched for after entering the site. I'd like to incorporate that too.
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a gssoc-24-extd contributor
[X] I want to work on this issue
[X] I check the issue doesn't exist

@pranavajith what you are going to swap let me know ?

Can you clarify by Swap?
I implied I would change "About" to "Pages". If that is not ideal, perhaps "Also Visit" would also work.
@RamakrushnaBiswal


Hystrix default timeout property being ignored

I just tried to update from Dalston.SR4 to Edgware.RELEASE.
I am setting  the hystrix.command.default.execution.isolation.thread.timeoutInMilliseconds property but, since the update to Edgware, the timeout is always 2 seconds. This value comes from AbstractRibbonCommand.getSetter (since commit 146513ae).
I can work around the problem by setting the timeout for a specific command key. I.e., hystrix.command.<HystrixCommandKey>.execution.isolation.thread.timeoutInMilliseconds.

I got the same problem, but workaround that @rworsnop mentioned works fine. Thanks for that ;)

I got the same problem, hystrix.threadpool.default.* props is not working, but hystrix.threadpool.<HystrixThreadPoolKey>.* works.


Can't run current installer even though I have current .net installed

I have .net installed, but the installer wants version 5? If you say no it closes.
Can  you fix the Install? I don't have the Microsoft Visual studio to recompile.
Thanks

Hey, somehow I missed this issue.  I will see about updating the installer.

I just got Voice Attack and my ED friends all love your software. However, like @Hawkcode I can't get past the Close button even though I have 5.0.17 installed.


Include credentials in all front-end fetch requests.

PR against 2.1.0 branch for a maintenance release.
Tested the solution by fetching from the browser. The failing and successful case was replicated.

https://github.com/plotly/streambed/issues/9142

💃

We also need to merge 2.1.0 into master, right? for the next release?

Yes, Im waiting to confirm that nothing else is needed to fix the Ambri issue before merging it into master.


Add verify with fallback

Preparatory work for a second attempt at https://github.com/octokit/webhooks.js/pull/811 .
Behavior
See https://github.com/octokit/webhooks.js/issues/770 and https://github.com/octokit/webhooks.js/pull/811 .
Additional info
Pull request checklist

[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been reviewed and added / updated if needed (for bug fixes / features)
[x] Added the appropriate label for the given change

I am unable to add labels.
Does this introduce a breaking change?

[x] No

Looks like this build is failing only due to a code formatting issue that can be easily resolved!


Bluetooth connection nearly completely not working

Describe the bug
It seems that after pairing, no information gets transmitted between the Flipper and the phone besides it's firmware version.
To Reproduce
Steps to reproduce the behavior:

Open mobile app
Press "Connect" if not connected yet
Press "Synchronize" if not Synching yet

Expected behavior
The progress climbs somewhat smoothly from 0% to 100%, and the new data synchronized from the Flipper appears in the app (such as the data in the archive, or installed apps in the hub). Instead, the progress jumps from 1% to 10%, and then finishes, with no new data in the app.
Logs
``
Android App logs: https://termbin.com/k1ut (Too large to fit in the issue)
Flipper Logs

          _.-------.._                    -,
      .-"```"--..,,_/ /`-,               -,  \
   .:"          /:/  /'\  \     ,_...,  `. |  |
  /       ,----/:/  /`\ _\~`_-"`     _;
 '      / /`"""'\ \ \.~`_-'      ,-"'/
|      | |  0    | | .-'      ,/`  /

|    ,..\ \     ,.-"       ,/    /
;    :    /""`           ,/--==,/-----,
|    -...|        -.___-Z:_______J...---;
Read Manual https://docs.flipperzero.one
Firmware version: 0.93.0 0.93.0 (e8c6e70a built on 12-10-2023)

: info device
format.major                  : 3
format.minor                  : 3
hardware.model                : Flipper Zero
hardware.uid                  :
hardware.otp.ver              : 2
hardware.timestamp            :<PHONE_NUMBER>
hardware.ver                  : 12
hardware.target               : 7
hardware.body                 : 9
hardware.connect              : 6
hardware.display              : 2
hardware.color                : 2
hardware.region.builtin       : 4
hardware.region.provisioned   : PT
hardware.name                 :
firmware.commit.hash          : e8c6e70a
firmware.commit.dirty         : false
firmware.branch.name          : 0.93.0
firmware.branch.num           : 0
firmware.version              : 0.93.0
firmware.build.date           : 12-10-2023
firmware.target               : 7
firmware.api.major            : 39
firmware.api.minor            : 2
firmware.origin.fork          : Official
firmware.origin.git           : https://github.com/flipperdevices/flipperzero-firmware
radio.alive                   : true
radio.mode                    : Stack
radio.fus.major               : 1
radio.fus.minor               : 2
radio.fus.sub                 : 0
radio.fus.sram2b              : 16K
radio.fus.sram2a              : 0K
radio.fus.flash               : 24K
radio.stack.type              : 3
radio.stack.major             : 1
radio.stack.minor             : 17
radio.stack.sub               : 3
radio.stack.branch            : 0
radio.stack.release           : 2
radio.stack.sram2b            : 19K
radio.stack.sram2a            : 14K
radio.stack.sram1             : 0K
radio.stack.flash             : 116K
radio.ble.mac                 : DD145B27E180
enclave.keys.valid            : 10
enclave.valid                 : true
system.debug                  : 1
system.lock                   : 0
system.orient                 : 0
system.sleep.legacy           : 0
system.stealth                : 0
system.heap.track             : 0
system.boot                   : 0
system.locale.time            : 0
system.locale.date            : 0
system.locale.unit            : 0
system.log.level              : 5
protobuf.version.major        : 0
protobuf.version.minor        : 20

: log
Current log level: debug
Use <log ?> to list available log levels
Press CTRL+C to stop...
31849374 [I][BtGap] Disconnect from client. Reason: 13
31849378 [I][BtSrv] Close RPC connection
31849381 [D][GattChar] Updating RPC status char
31849384 [D][GattChar] Updating Flow control char
31849387 [D][RpcSrv] Session terminated
31855857 [I][BtGap] Connection parameters: Connection Interval: 36 (45 ms), Slave Latency: 0, Supervision Timeout: 500
31856027 [D][BtGap] Slave security initiated
31856297 [I][BtGap] Pairing complete
31856303 [I][BtSrv] Open RPC connection
31856307 [D][GattChar] Updating Flow control char
31856312 [D][RpcSrv] Session started
31856315 [D][GattChar] Updating RPC status char
31856320 [D][GattChar] Updating Battery Level char
31857647 [I][BtGap] Rx MTU size: 414
31858096 [I][BtGap] Connection parameters event complete
31858099 [I][BtGap] Connection parameters: Connection Interval: 12 (15 ms), Slave Latency: 0, Supervision Timeout: 500
31858102 [W][BtGap] Unsupported connection interval. Request connection parameters update
31858165 [D][BtGap] Procedure complete event
31858254 [I][BtGap] Connection parameters event complete
31858257 [I][BtGap] Connection parameters: Connection Interval: 36 (45 ms), Slave Latency: 0, Supervision Timeout: 500
31875501 [I][BtGap] Connection parameters event complete
31875503 [I][BtGap] Connection parameters: Connection Interval: 12 (15 ms), Slave Latency: 0, Supervision Timeout: 500
31875506 [W][BtGap] Unsupported connection interval. Request connection parameters update
31875569 [D][BtGap] Procedure complete event
31875658 [I][BtGap] Connection parameters event complete
31875660 [I][BtGap] Connection parameters: Connection Interval: 36 (45 ms), Slave Latency: 0, Supervision Timeout: 500
31892993 [I][BtGap] Connection parameters event complete
31892996 [I][BtGap] Connection parameters: Connection Interval: 12 (15 ms), Slave Latency: 0, Supervision Timeout: 500
31892998 [W][BtGap] Unsupported connection interval. Request connection parameters update
31893062 [D][BtGap] Procedure complete event
31893151 [I][BtGap] Connection parameters event complete
31893154 [I][BtGap] Connection parameters: Connection Interval: 36 (45 ms), Slave Latency: 0, Supervision Timeout: 500
31907347 [D][GattChar] Updating Battery Level char
31924346 [I][BtGap] Connection parameters event complete
31924348 [I][BtGap] Connection parameters: Connection Interval: 12 (15 ms), Slave Latency: 0, Supervision Timeout: 500
31924351 [W][BtGap] Unsupported connection interval. Request connection parameters update
31924415 [D][BtGap] Procedure complete event
31924504 [I][BtGap] Connection parameters event complete
31924507 [I][BtGap] Connection parameters: Connection Interval: 36 (45 ms), Slave Latency: 0, Supervision Timeout: 500

Additional context
You will notice my firmware is in 0.93.0, but the exact same behaviour happens with the latest firmware, therefore I believe it is an Android sided issue.

No new information seemed to actually be transmitted to my device.
All the permissions were given to the app in Android settings.

Please update to latest version 0.102, then try to reproduce issue and attach logs from Flipper and Mobile Phone

Also please set log level to debug

Please update to latest version 0.102, then try to reproduce issue and attach logs from Flipper and Mobile Phone

It has the exact same behaviour on 0.102.3 (that is where I took the screenshots). Either way, I'll send the logs.
Flipper Log
App Log

Also please set log level to debug

I believe it is already debug? "Current log level: debug" Am I missing anything?

Yep, on firmware side it looks alright. Except there is no RPC session being opened.

no information gets transmitted between the Flipper and the phone

What kind of information do you expect to receive?

I expect to receive the keys I have in the Flipper, be able to access it's files, to check it's installed applications, I expect the "full info" submenu to be populated as well. None of this info was present in the app after multiple attempted syncs. Currently I only have a screenshot of the Hub portion of the app not displaying installed apps.

I see that Flipper Zero on file listing (e.g. /any/subghz) gives command_status: ERROR / command_status_value: 1

Are you sure this is all the logs from the flipper that you have for the session? Can you record a video of it?
Can you try using a different sdcard?

These are all the logs, collected as explained in https://docs.flipper.net/mobile-app/bug-report , using https://googlechromelabs.github.io/serial-terminal/ throughout the whole process, and just exporting the logs. The application logs were collected from the start of the app until the end of the procedure, using logcat.

Unfortunately this is the only SD card I have, but I have benchmarked it multiple times, fsck'd, and done full read and write tests, and there have been no issues. It is a 64GB Sandisk MicroSD which I previously used to run a raspberry pi.

Can you record a video? I can't play it back and I don't understand at what point what events are happening.
From an application point of view, flipper just returns an error on any request