Log rule expansion under log_level=debug upon startup

Motivation
It would be great to have the ability to see rule expansions printed, especially with complex rules using lists, macros and exceptions that are being augmented using append: true. This so the author can make sure that they are as desired.
Feature
When running falco with --option log_level=debug I would like falco to emit the expanded rules after reading all config files.
Alternatives
None?
Additional context
None?

/remove-lifecycle stale

Hey @josb, I recently took on refactoring the rule loader, and now it should be quite easier to add a feature like this. Do you think it would make sense to make this available only with the -v verbose option? Also, would you prefer this to happen for all rules, or having a selective CLI option to print only one?

Hi @jasondellaluce , thanks for doing that! I think putting this under -v would be fine as it's really a debugging aid.Not sure if the extra effort for a CLI option to print a single rule is needed, your call :-)

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

@poiana: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/reopen
/remove-lifecycle rotten

@jasondellaluce: Reopened this issue.

In response to this:

/reopen
/remove-lifecycle rotten

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten

/remove-lifecycle rotten

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten

This will be addressed by this: https://github.com/falcosecurity/falco/pull/2544 :tada:
Moreover, this issue seems already summarized here https://github.com/falcosecurity/falco/issues/2372
Can we close this?


Swift Package Manager Warning

Describe the bug
I'm getting the following warning:
"ignoring declared target(s) 'swift-nio-zlib-support' in the system package"
You can see that they are not supporting it anymore here
Please Update the package to substitute with the new one.
Thanks
Steps To Reproduce
Steps to reproduce the behavior:
1. Go to 'add all the packages to a new project'
2. Click on 'build'
3. See error

Expected behavior
Warnings...
Amplify Framework Version
1.12.0
Amplify Categories
Analytics, API, Auth, DataStore, Predictions, Storage
Dependency manager
Swift PM
Swift version
5.0
CLI version
latest
Xcode version
latest
Relevant log output
Showing Recent Messages
ignoring declared target(s) 'swift-nio-zlib-support' in the system package

Is this a regression? (i.e. was this working before a version upgrade)
No response
Device
latest
iOS Version
latest
Specific to simulators
No response
Additional context
No response

swift-nio-zlib-support is from the underlying dependency from Starscream. Starscream had fixed this issue in their latest version, but this requires us to depend on the next major version of Starscream.
As explained here moving to the next major version is not trivial and require a lot of work. We will update this ticket when we move to the next version of Starscream. Since this is a warning, we believe that this wont affect your app.

Closing this issue in favor of https://github.com/aws-amplify/aws-appsync-realtime-client-ios/issues/44 .


Clarify behavior of command

@shsagir
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@nachoalonsoportillo Thx for the feedback. This is a duplicate of #1609 which is currently being investigated and so I'm closing this PR.
#please-close


fix: resolve issue with null avatar

:tada: This PR is included in version 0.54.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


TypeScript issues with createSelector

Hello, i'm having an issue with TS and createSelector. I was reading the latest release notes for v4.1.3 and v4.1.4 but i wasn't able to find a fix/workaround.
Here's a demo to reproduce the issue: https://stackblitz.com/edit/typescript-vf7zff?file=index.ts
The problem seems related to selectors from createSelector with just one additional argument (complexOne in the demo). Maybe i'm using the "input selectors" in the wrong way but, looking at the notes in v4.1.3, they should be fine.
Here the code for future reference:
import { createSelector } from 'reselect';

interface State {
  foo: string;
  bar: number;
}

const initialState: State = {
  foo: 'This is Foo',
  bar: 1,
};

const getFoo = (state: State) => {
  return state.foo;
};
console.log('getFoo:', getFoo(initialState));

const getBar = (state: State) => {
  return state.bar;
};
console.log('getBar:', getBar(initialState));

const simple = createSelector(getFoo, getBar, (foo, bar) => {
  return `${foo} => ${bar}`;
});
console.log('Simple:', simple(initialState));

// Input selectors with positional args
const firstInput = (_: State, first: string) => first;
// Skip the first arg and return only the second.
const secondInput = (_: State, _first: string, second: number) => second;

const complexOne = createSelector(
  getFoo,
  getBar,
  firstInput,
  (foo, bar, first) => {
    return `${foo} => ${bar} || ${first}`;
  }
);
console.log('Complex:', complexOne(initialState, 'first'));

const complexTwo = createSelector(
  getFoo,
  getBar,
  firstInput,
  secondInput,
  (foo, bar, first, second) => {
    return `${foo} => ${bar} || ${first} and ${second}`;
  }
);
// TS should complain since 'second' should be `number`
console.log('Complex:', complexTwo(initialState, 'first', 'second'));

Versions
TS: 4.5.2
Reselect: 4.1.4
Thank you so much!
Ref: https://github.com/microsoft/TypeScript/issues/45147
Ref: https://github.com/reduxjs/reselect/issues/459

For my last version of typescript which does work with reselect is 4.2.1-rc. Maybe it will help.

I think I'm running into the same issue, here's a minimal reproducing example which does not make much sense but illustrates the issue:
import { createSelector } from 'reselect';

interface State {
    counter1: number;
    counter2: number;
}

const selectTest = createSelector(
    (state: State, numberA?: number) => numberA,
    (state: State) => state.counter2,
    (numberA, counter2) => numberA ? numberA + counter2 : counter2
);

Generated signature:
const selectTest: ((state: {
    counter1: number;
    counter2: number;
}, params_0?: {}) => number) & OutputSelectorFields<(args_0: number | undefined, args_1: number) => number & {
    clearCache: () => void;
}> & {
    clearCache: () => void;
}

The issue is with params_0?: {} which is wrong, it should be params_0?: number as far as I understand.

First question, as per #550: do you have strictNullChecks: true in your tsconfig.json?

strictNullChecks

Actually, no. Thanks for the input

Hmm. I'll try to investigate in the next couple days, although tbh I've spent so much time on reworking these types in the last couple weeks that my brain is kinda fried :)
@lg-kialo if you could provide an actual project repro that would be helpful in trying to debug this.

Hmm. I'll try to investigate in the next couple days, although tbh I've spent so much time on reworking these types in the last couple weeks that my brain is kinda fried :)
@lg-kialo if you could provide an actual project repro that would be helpful in trying to debug this.

Here's a codesandbox which shows the problem: https://codesandbox.io/s/nifty-pascal-0d4kj?file=/src/index.ts

First question, as per #550: do you have strictNullChecks: true in your tsconfig.json?

@markerikson Thanks for the input! I'll try it and drop an update here 👍

I've reverted to 4.1.0 to have selectors return types working again

@guy-st can you provide any additional example projects that show these errors happening? and do you have strictNullChecks or strict turned on?

Same issue here on 4.1.4.
No issue on 4.0.0.
"strict": true,

Folks, right now I cannot replicate this with our typetests. What I really need are more example projects that actually show this problem happening, not just "it fails for me too".

If you edit this sandbox https://codesandbox.io/embed/frosty-violet-ebpxc?fontsize=14&hidenavigation=1&theme=dark
You will get the error:

And if you change the dependencies to 4.0.0 the error gone:

@RoXuS with the types in 4.1+, you should not be supplying generic arguments. createSelector should be inferring these automatically.
Does it work okay if you just delete the entire < > section?

yes it works! Thx, sorry for disturbance!

@markerikson  it is working now with 4.1.4, I can't reproduce either.
Perhaps it was a matter of "reloading the window" in VSCode after installing react-use.
I am using the "JavaScript and TypeScript Nightly" extension in VSCode, perhaps it was related.
No, I didn't have strictNullChecks or strict on.

That's another good question.
Are these errors solely in VS Code, or are they happening at compile time too?

the same issue.

That's another good question.
Are these errors solely in VS Code, or are they happening at compile time too?

The same issue.
With compile too (webpack 5) and in webstorm
(ts 4.4, yarn modern, reselect ^4.0.0) reproduced
but on ~4.0.0 works fine

@edolix : fwiw I see that there is indeed an error in the StackBlitz project, but if I download it and both compile with tsc and open it in VS Code, it compiles clean with no errors. Similarly, copying the code into Reselect's typetests file appears to work correctly.

@markerikson the StackBlitz project shows the errors if you disable the strict mode. The issue seems fixed using strict: true.

@edolix then that's exactly the problem. As discussed in #550 , Reselect needs TS to have strict: true enabled in order to work right.

Just released https://github.com/reduxjs/reselect/releases/tag/v4.1.5 , which should address additional problems around undefined or optional parameters, and all the code samples provided in this issue appear to type-check correctly.
Going to close this issue - if there's any further problems, please open up a new issue, include a reproduction of the problem and ensure you have strict: true enabled.


Create ATSOS::restartJob()

Create method to restart a job in the ATSOS scheduler:
unsigned int ATSOS::restartJob(jobFunction job);

The unsigned int returned is 0 if there is no error and 1 if there is an error. This issue is closely tied to Issue #4: if a job is paused, the user should be able to easily reinstate it at some point.

This issue was resolved.


pg: Add initial porting guide

Porting guide
It focus on i.MX boot flow (SPL) and I've tried to create filenames which might not collide when future other boot flows are added.
I've tried to keep this very linear, but if there are suggestions on how to parallelize we can rework the TOC or structure.

Docs for 125b70a83748d84cf4e094202c1e8703455990dc are browesable at: https://ci.foundries.io/projects/fio-docs/builds/1070/docs/artifacts/html/index.html

Docs for b0141650dbc927931febceee60d7bd452e16dacb are browesable at: https://ci.foundries.io/projects/fio-docs/builds/1071/docs/artifacts/html/index.html

Docs for e837526ba80e120d1fc4ac1808171c8a187a8d22 are browesable at: https://ci.foundries.io/projects/fio-docs/builds/1072/docs/artifacts/html/index.html

Docs for c535736dbff06b49b47666f03c00502726f52ebe are browesable at: https://ci.foundries.io/projects/fio-docs/builds/1073/docs/artifacts/html/index.html

Docs for 0064382b089f99cc32759f78b30688fb38f6f414 are browesable at: https://ci.foundries.io/projects/fio-docs/builds/1074/docs/artifacts/html/index.html

Docs for 686121a6e8bb553659c83e3376d362d719db3e59 are browesable at: https://ci.foundries.io/projects/fio-docs/builds/1081/docs/artifacts/html/index.html

Docs for c66a1941399d447da11e55c11a2be525f5d30f83 are browesable at: https://ci.foundries.io/projects/fio-docs/builds/1082/docs/artifacts/html/index.html

Docs for 29ed3411d24385d0dc8df4e47bcde4017fb1e913 are browesable at: https://ci.foundries.io/projects/fio-docs/builds/1083/docs/artifacts/html/index.html

Docs for 7b9232c3cfa563867217f5d29710c04ff66bd354 are browesable at: https://ci.foundries.io/projects/fio-docs/builds/1084/docs/artifacts/html/index.html

Docs for 5fd5509f28fa2f0a1bd662ffb21c75c22ea0399a are browesable at: https://ci.foundries.io/projects/fio-docs/builds/1085/docs/artifacts/html/index.html

ci-retest

Docs for 004e5e3c692f1e0516073ac6a0382e6de6ec8b24 are browesable at: https://ci.foundries.io/projects/fio-docs/builds/1313/docs/artifacts/html/index.html

Docs for 004e5e3c692f1e0516073ac6a0382e6de6ec8b24 are browesable at: https://ci.foundries.io/projects/fio-docs/builds/1314/docs/artifacts/html/index.html

ci-retest

Docs for 004e5e3c692f1e0516073ac6a0382e6de6ec8b24 are browesable at: https://ci.foundries.io/projects/fio-docs/builds/1316/docs/artifacts/html/index.html


Extremely large size npz files during SuperPoint export_predictions

Hi developers,
I'm trying to train Hfnet. During distillation, the exported npz files exceeded the 100 Gb in 20 minutes. As a result the process stopped because no space left on my device.  My dataset is about 5 Gb of 50 000 images from Berkley DeepDrive dataset.
The command that I'm using is the following:
python hfnet/hfnet/export_predictions.py hfnet/hfnet/configs/superpoint_export_distill.yaml superpoint_predictions --keys local_descriptor_map,dense_scores --as_dataset

Is it reasonable or am I doing something wrong ?

I have the same problem


Does not support in IE11 ?

What version of Ajv are you using? Does the issue happen if you use the latest version?
"ajv": "^8.6.3".
the latest version has the same issue.
Ajv options object
null

JSON Schema
null

Sample data
null

Your code
import Ajv from "ajv";

Validation result, data AFTER validation, error messages
I just import ajv in vue-cli,it work in chrome, but it report error in IE11.

What results did you expect?
Are you going to resolve the issue?
Not sure how to do.

Most likely you need to disable Unicode regex via options - it’s not supported in IE 11

Thanks for your reply. I try to resolve it by this, but the problem remains. It cause by import AJV not new AJV().
import Ajv from "ajv";
const options = {
  unicodeRegExp: false,
  code: { es5: true },
};
const ajv = new Ajv(options);

ajv version<7.0.0, it work fine in IE11.  So I switch the version of 6.12.6. I expect the new version can also support ie11.


Prioritize hardcoded metadata over network-sourced metadata

Fixes a bug where hardcoded metadata for Cloud Instance Discovery was incorrectly built and therefore never worked
Promotes hardcoded Cloud Instance Discovery metadata over cached and network metadata sources

Codecov Report

Merging #6231 (07ebd16) into dev (81d34b4) will decrease coverage by 3.33%.
The diff coverage is 48.68%.

Flag
Coverage Δ

msal-angular
96.73% <96.63%> (+0.22%)
:arrow_up:

msal-browser
86.17% <ø> (-0.30%)
:arrow_down:

msal-common
83.30% <ø> (-1.24%)
:arrow_down:

msal-core
?

msal-node
79.74% <ø> (-3.65%)
:arrow_down:

msal-node-extensions
42.11% <14.19%> (-33.53%)
:arrow_down:

msal-react
94.24% <ø> (-0.45%)
:arrow_down:

node-token-validation
?

Impacted Files
Coverage Δ

...ions/msal-node-extensions/src/utils/Environment.ts
20.51% <0.00%> (-22.08%)
:arrow_down:

...b/msal-browser/src/app/IPublicClientApplication.ts
43.75% <ø> (ø)

...ib/msal-browser/src/app/PublicClientApplication.ts
73.80% <ø> (-21.52%)
:arrow_down:

...er/src/broker/nativeBroker/NativeMessageHandler.ts
86.29% <ø> (+0.33%)
:arrow_up:

lib/msal-browser/src/cache/AsyncMemoryStorage.ts
80.76% <ø> (+2.99%)
:arrow_up:

lib/msal-browser/src/cache/BrowserCacheManager.ts
90.18% <ø> (-1.54%)
:arrow_down:

lib/msal-browser/src/cache/BrowserStorage.ts
87.50% <ø> (-3.41%)
:arrow_down:

lib/msal-browser/src/cache/CryptoKeyStore.ts
80.00% <ø> (-3.34%)
:arrow_down:

lib/msal-browser/src/cache/DatabaseStorage.ts
34.00% <ø> (-4.54%)
:arrow_down:

lib/msal-browser/src/cache/MemoryStorage.ts
100.00% <ø> (ø)

... and 72 more

... and 161 files with indirect coverage changes


Non-blocking Next method for C++ async completion queue

Code changes required to address issue #1004 .

Do not merge this yet as there are no tests for the new non-blocking method.

Ok, I think that you're right. I will change the gpr_timespec uses here to std::chrono . I also have some tests that will get committed and pushed today.

Vijay

I incorrectly classified the last commit as "currently buggy". It looks like it was ok after all (first try!). I believe that this is now ready for review.

I amended the commit to correct the problem in the commit message.

Thanks for the merge!


Navigation in categories

really annoying for the navigation so I don't know if it's possible to keep it on top, to block it etc
same in other categories and sub categories, this is just one ex

To @Margaaux :
Totally agree! To be honest I just don't really know where to put it.
Some solutions on the top of my head:

it could disappear when you scroll down and reappear when you scroll up (easy/quick not very difficult)
it could juste stay at the top of the page (easiest/quickest to do)
it could be a sidebar like a burger menu like this:
 (not hard, but I've never done it before)

What would you prefer?

@Lauraillouz "it could disappear when you scroll down and reappear when you scroll up (easy/quick not very difficult)"
I think it is the best option (at least for now)


Ingestion Status broken when multiple ingestions are started for a collection in LOCAL

Steps to reproduce:

Create a collection
Link 2 data sources to it.

Excepted Behaviour:

when one of the data sources has completed ingestion, its status changes to COMPLETED

Observed Behaviour:

in the attached screenshots, one of the data source has completed ingestion (see unstructured_api CPU usage, it was 200% when both were running) , but both have a status of DATA_INGESTION_STARTED.

when both are completed, the status for both of them is set to COMPLETED

Yes, actually same error occurs in deployed version as well, we shall check on this.


Univalence, stage 0.

@cangiuli @jonsterling It is time to propose your favorite definition of equivalences (as a labeled record).

@jonsterling If you already proved some interesting equivalence somewhere please show me! This PR is done if I can verify it with some interesting examples, but writing them will take some time...

Hmm path is a keyword so the above rule is almost never applicable. Oops.

Apparently I do not know how to comment on one commit. I meant the commit 097dac7a75a743ff11523c8af26b87da0039cc4e.

Hmm something went wrong after rebasing. Now
Thm IdEquiv (#A) : [
  #A hcom type
  >>
  (Equiv #A #A)
] by [
  `(tuple Id (IdIsEquiv #A));
  unfold IdIsEquiv;
  ?
].

gives
Fail: Impossible failure during safeUnfold: nonexhaustive binding failure

but I recall it was fine, and travis seems to agree with me: https://travis-ci.org/RedPRL/sml-redprl/jobs/271302400.

@favonia I wonder if I introduced this in my recent bugfixes to operator unfolding...

@jonsterling Should I leave this to you? I can switch to the category example.

@favonia Yes, I can have a look at the operator unfolding issue; it may take me a day or two though, I have a lot on my plate.

@favonia Ah, I see what happened; there's a change in behavior which causes this kind of definition (where you put a sequent in the goal) not to behave in the way it used to. There's a bug in my fix, but fixing the bug won't fix this code.
I'll try and explain in more detail, and fix everything.

To be honest, I was actually surprised that it worked with a suspicious hypothesis hanging around like that. In some way I am glad it failed, if that is the reason it failed.

@favonia I fixed that bug, and committed it directly to this branch (hope you don't mind).
Going forward, I think we should avoid using sequents at the top level, since the resulting theorems cannot be easily re-used. We should try to use function types and universes wherever possible.

(and equality types!)

Maybe it is obvious, but should I merge this PR now?

@favonia Yes please! Great work, this is a very exciting moment!


Low-level position control frequency (Go1 Edu)

Hi,
I read the other issue (https://github.com/unitreerobotics/unitree_legged_sdk/issues/41) where it's discussed that the low-level position controller runs at a much higher frequency (10-20kHz). I had a few questions regarding this I was hoping you could clarify.

Is there a way to control the frequency of this low-level position controller, or is it fixed?

If I have a policy that runs at 50 Hz (i.e. q_des is changed at 50Hz), does it make any difference what frequency I use for the control loop (udp control_loop() ) that passes this q_des to the low-level position controller? As far as I understand it should make no difference whether I give q_des at 200,500 or 1000 Hz, assuming that the policy output q_des remains the same. Or does sending commands (despite q_des being the same) somehow change the performance of the low-level controller.

In the other thread you mention a range of 10-20kHz, do you have a more exact value?

Thank you and I appreciate your input!

Hello, the highest frequency value of q_des is 1000 Hz. In addition, regarding the more precise value you mentioned, it is not necessary to provide a specific specific value, because it has no specific use


Show name of protocol in conductor

Once the G4P is loaded, there is no indication in the Conductor about the protocol name that I can see.
Would it be nice to add the g4p file name somewhere on the GUI?

Does it not show up in the Experiment Name field on the right hand side? It's greyed out, so it can't be changed. That also means if it's a long name you can't scroll right to see all of it, but you do see at least the first portion of the file name.

Oh, yes. I see it now.
Having a more prominent place could help. In Windows it's often in the title, in this case behind "Fly Experiment Conductor".
Otherwise, being able to scroll and see the whole name would also be good.

Added in commit 67c8077


Old systemd-file in release

The current build.tar.gz somehow doesn't have the current version of amdfand.service in it.
https://github.com/Eraden/amdgpud/releases/tag/1.0.5

Thanks for notice, fixed


Don't duplicate Form Submitter [name] param

When a <form> element's submitter declares a [name] attribute
without a [value] attribute, it is appended to the submission's
FormData instance twice. Due to a quirky difference between Safari and
Firefox + Chrome, the duplication only occurs in Safari, which is a
browser that we are not running our functional test suite against.
In spite of that, this commit adds test coverage to ensure we don't
introduce a similar regression into those browsers.
Testing
Oddly enough, there are several occurrences of doubled-up await await
keywords, which this commit removes.

What would it take to run intern against Safari in CI? Browserstack? GitHub Actions running on macOS?

What would it take to run intern against Safari in CI? Browserstack? GitHub Actions running on macOS?

I don't recall the specifics, but there's problems with running the test suite under Safari that are not CI- or Intern-related.

Thank you!


push/sync artifacts to maven central

Waiting for sonatype to set up the repositories and permissions etc...

Artifacts from 1.0.5 are synced to maven central now.


Sub parsers not supported

Subparsers don't end up documented in the output.

You can test with my library https://github.com/danielperna84/ha-philipsjs
pip install haphilipsjs

python -m haphilipsjs -i dummy -a 1 markdown

As of now, subparses aren't supported because I did not have the time to do it. However, in case you implement it, please feel free to send a PR.


Add more jobs to Jenkins AWS

In starting to think about how 2ndline might start to use the environment, add a few more jobs that might be used, and see if they work in the way we expect.

Updated to address all comments.


Add TypeScript definition file

I generated a type definition file using Microsoft's dts-gen. It needs to be named index.d.ts, so that TypeScript compilers can automatically pick it up:

Also note that if your main declaration file is named index.d.ts and lives at the root of the package (next to index.js) you do not need to mark the "types" property, though it is advisable to do so.

Codecov Report

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

@@          Coverage Diff          @@
##           master   #141   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          12     12
  Lines         255    255
  Branches       49     49
=====================================
  Hits          255    255


Pass maps and slices by value

This requires custom marshallers to distinguish between a nil value
(don't send anything) and an empty value (send empty map/slice).
Refactored marshalling detection logic which also fixed some broken
corner-cases.
Added custom XML marshaller to handle nested elements for slices.

Fixes https://github.com/Azure/autorest.go/issues/607


Android devices randomly disconnect

Description
Android devices would randomly disconnect, even when the device and RenderDoc are left idle.
Steps to reproduce

Turn off battery and background optimizations for RenderDocCmd
Select device via "Replay Context" menu on the bottom left
Observe

The device would disconnect randomly within seconds to minutes, resulting in "Remote server disconnected" status.
qrenderdoc log (personal/device info obfs'd):
RDOC 015612: [16:29:54]             core.cpp( 459) - Log     - RenderDoc v1.14 Windows 64-bit Release (50b2cecc50918e6091f4a8b0e68c0854aca636f1) loaded in replay application
RDOC 015612: [16:29:54]             core.cpp( 470) - Warning - Couldn't open socket for target control
RDOC 012468: [16:29:54]             core.cpp( 459) - Log     - RenderDoc v1.14 Windows 64-bit Release (50b2cecc50918e6091f4a8b0e68c0854aca636f1) loaded in replay application
RDOC 012468: [16:29:54]             core.cpp( 470) - Warning - Couldn't open socket for target control
RDOC 012468: [16:29:54]         settings.cpp( 460) - Log     - Loading config from D:\Users\xxx\AppData\Roaming\renderdoc\renderdoc.conf
RDOC 015612: [16:29:54]      crash_handler.h( 150) - Log     - Timer Waiting for crash handling server - 96.451 ms
RDOC 015612: [16:29:54]      crash_handler.h( 156) - Log     - Created crash-handling server \\.\pipe\RenderDocBreakpadServer46581524596
RDOC 015612: [16:29:54]      crash_handler.h(  87) - Log     - Connecting to server \\.\pipe\RenderDocBreakpadServer46581524596
RDOC 015612: [16:29:54]         settings.cpp( 460) - Log     - Loading config from D:\Users\xxx\AppData\Roaming\renderdoc\renderdoc.conf
QTRD 015612: [16:29:54]       qrenderdoc.cpp(  94) - Log     - QRenderDoc initialising.
QTRD 015612: [16:29:54]       qrenderdoc.cpp(  97) - Log     - Running as administrator
RDOC 015612: [16:29:54]    android_tools.cpp( 347) - Log     - Initialising adb using 'D:\AndroidSDK\platform-tools\adb.exe'
RDOC 015612: [16:29:54]      crash_handler.h(  51) - Log     - Re-using crash-handling server \\.\pipe\RenderDocBreakpadServer46581524596
RDOC 015612: [16:29:54]      crash_handler.h(  87) - Log     - Connecting to server \\.\pipe\RenderDocBreakpadServer46581524596
RDOC 015612: [16:29:54]     d3d11_replay.cpp( 125) - Log     - Running replay on Intel / Intel(R) UHD Graphics 630 <IP_ADDRESS>90
RDOC 015612: [16:29:54] d3d12_sdk_select.cpp( 217) - Log     - No system D3D12 runtime found at C:\Windows\system32\D3D12Core.dll.
RDOC 015612: [16:29:54]     d3d12_replay.cpp( 110) - Log     - Running replay on Intel / Intel(R) UHD Graphics 630 <IP_ADDRESS>90
RDOC 015612: [16:29:54]        vk_replay.cpp(4288) - Log     - Created device.
QTRD 015612: [16:29:54] ToolWindowManager.cpp(1544) - Warning - area parameter ignored for this type
RDOC 015612: [16:29:54]    android_tools.cpp( 321) - Log     - COMMAND: D:\AndroidSDK\platform-tools\adb.exe '-s DEVICEID root'
RDOC 015612: [16:29:54]    android_tools.cpp( 321) - Log     - COMMAND: D:\AndroidSDK\platform-tools\adb.exe '-s DEVICEID shell getprop ro.product.manufacturer'
RDOC 015612: [16:29:55]    android_tools.cpp( 321) - Log     - COMMAND: D:\AndroidSDK\platform-tools\adb.exe '-s DEVICEID shell getprop ro.product.model'
RDOC 015612: [16:29:55]    android_tools.cpp( 321) - Log     - COMMAND: D:\AndroidSDK\platform-tools\adb.exe '-s DEVICEID shell getprop ro.build.version.sdk'
RDOC 015612: [16:29:55]         streamio.cpp( 415) - Warning - Error reading from socket
RDOC 015612: [16:29:55]    remote_server.cpp(1196) - Warning - Didn't get proper handshake
RDOC 015612: [16:29:56]         streamio.cpp( 415) - Warning - Error reading from socket
RDOC 015612: [16:29:56]    remote_server.cpp(1196) - Warning - Didn't get proper handshake
RDOC 015612: [16:29:56]    android_tools.cpp( 321) - Log     - COMMAND: D:\AndroidSDK\platform-tools\adb.exe '-s DEVICEID shell getprop ro.build.version.sdk'
RDOC 015612: [16:29:56]    android_tools.cpp( 321) - Log     - COMMAND: D:\AndroidSDK\platform-tools\adb.exe '-s DEVICEID shell pm list packages org.renderdoc.renderdoccmd'
RDOC 015612: [16:29:56]    android_tools.cpp( 321) - Log     - COMMAND: D:\AndroidSDK\platform-tools\adb.exe '-s DEVICEID shell getprop ro.product.cpu.abi'
RDOC 015612: [16:29:57]          android.cpp(1006) - Log     - Starting RenderDoc server, supported ABIs:
RDOC 015612: [16:29:57]          android.cpp(1008) - Log     -   - armeabi_v7a
RDOC 015612: [16:29:57]          android.cpp(1008) - Log     -   - arm64_v8a
RDOC 015612: [16:29:57]          android.cpp( 275) - Log     - Checking installed version of org.renderdoc.renderdoccmd.arm32 on DEVICEID
RDOC 015612: [16:29:57]    android_tools.cpp( 321) - Log     - COMMAND: D:\AndroidSDK\platform-tools\adb.exe '-s DEVICEID shell pm dump org.renderdoc.renderdoccmd.arm32'
RDOC 015612: [16:29:57]          android.cpp( 316) - Log     - Installed server version (114:50b2cecc50918e6091f4a8b0e68c0854aca636f1) is compatible
RDOC 015612: [16:29:57]    android_tools.cpp( 321) - Log     - COMMAND: D:\AndroidSDK\platform-tools\adb.exe '-s DEVICEID shell am force-stop org.renderdoc.renderdoccmd.arm32'
RDOC 015612: [16:29:57]    android_tools.cpp( 321) - Log     - COMMAND: D:\AndroidSDK\platform-tools\adb.exe '-s DEVICEID shell am force-stop org.renderdoc.renderdoccmd.arm64'
RDOC 015612: [16:29:58]    android_tools.cpp( 321) - Log     - COMMAND: D:\AndroidSDK\platform-tools\adb.exe '-s DEVICEID forward tcp:38969 localabstract:renderdoc_39920'
RDOC 015612: [16:29:58]    android_tools.cpp( 321) - Log     - COMMAND: D:\AndroidSDK\platform-tools\adb.exe '-s DEVICEID forward tcp:38960 localabstract:renderdoc_38920'
RDOC 015612: [16:29:59]    android_tools.cpp( 321) - Log     - COMMAND: D:\AndroidSDK\platform-tools\adb.exe '-s DEVICEID push "D:\Users\xxx\AppData\Roaming\renderdoc\renderdoc.conf" /sdcard/Android/data/org.renderdoc.renderdoccmd.arm64/files/renderdoc.conf'
RDOC 015612: [16:29:59]    android_tools.cpp( 321) - Log     - COMMAND: D:\AndroidSDK\platform-tools\adb.exe '-s DEVICEID shell am start -n org.renderdoc.renderdoccmd.arm64/.Loader -e renderdoccmd remoteserver'

Filtered logcat:
--------- beginning of main
--------- beginning of system
06-15 16:29:59.322  9808  9808 I renderdoc: @60c8650700000001@ RDOC 009808: [16:29:59]   posix_stringio.cpp( 519) - Warning - Couldn't acquire shared lock to '/sdcard/Android/media/org.renderdoc.renderdoccmd.arm64/files/RenderDoc/RenderDoc_2021.06.15_16.29.59.log': 38
06-15 16:29:59.322  9808  9808 I renderdoc: @60c8650700000002@ RDOC 009808: [16:29:59]             core.cpp( 459) - Log     - RenderDoc v1.14 Android 64-bit Release (50b2cecc50918e6091f4a8b0e68c0854aca636f1) loaded in replay application
06-15 16:29:59.323  9808  9808 I renderdoc: @60c8650700000003@ RDOC 009808: [16:29:59]             core.cpp( 470) - Warning - Couldn't open socket for target control
06-15 16:29:59.323  9808  9808 I renderdoc: @60c8650700000004@ RDOC 009808: [16:29:59]         settings.cpp( 460) - Log     - Loading config from /sdcard/Android/media/org.renderdoc.renderdoccmd.arm64/files/renderdoc.conf
06-15 16:29:59.327  9808  9808 I renderdoccmd: Creating lock m_DrawLock
06-15 16:29:59.327  9808  9808 I renderdoccmd: Creating lock m_CmdLock
06-15 16:29:59.375  9808  9838 I renderdoccmd: android_main android_state->window: 0x0
06-15 16:29:59.377  9808  9838 I renderdoccmd: handle_cmd(10)
06-15 16:29:59.384  9808  9838 I renderdoccmd: handle_cmd(11)
06-15 16:29:59.392  9808  9838 I renderdoccmd: handle_cmd(0)
06-15 16:29:59.408  9808  9838 I renderdoccmd: handle_cmd(1)
06-15 16:29:59.408  9808  9838 I renderdoccmd: APP_CMD_INIT_WINDOW
06-15 16:29:59.408  9808  9838 I renderdoccmd: spawning command thread
06-15 16:29:59.408  9808  9838 I renderdoccmd: Trying to splash
06-15 16:29:59.408  9808  9838 I renderdoccmd: Doing a splash
06-15 16:29:59.409  9808  9840 I renderdoccmd: Entering cmd thread
06-15 16:29:59.409  9808  9840 I renderdoc: @60c8650700000005@ RDOC 009808: [16:29:59]    posix_network.cpp( 422) - Log     - Created and bind socket: 95
06-15 16:29:59.412  9808  9840 I renderdoc: @60c8650700000006@ RDOC 009808: [16:29:59]    remote_server.cpp( 986) - Log     - No whitelist IP ranges configured - using default private IP ranges.
06-15 16:29:59.412  9808  9840 I renderdoc: @60c8650700000007@ RDOC 009808: [16:29:59]    remote_server.cpp( 990) - Log     - Create a config file remoteserver.conf in ~/.renderdoc or %APPDATA%/renderdoc to narrow this down or accept connections from more ranges.
06-15 16:29:59.412  9808  9840 I renderdoc: @60c8650700000008@ RDOC 009808: [16:29:59]    remote_server.cpp( 997) - Log     - Allowing connections from:
06-15 16:29:59.412  9808  9840 I renderdoc: @60c8650700000009@ RDOC 009808: [16:29:59]    remote_server.cpp(1006) - Log     - <IP_ADDRESS> / <IP_ADDRESS>
06-15 16:29:59.412  9808  9840 I renderdoc: @60c865070000000a@ RDOC 009808: [16:29:59]    remote_server.cpp(1006) - Log     - <IP_ADDRESS> / <IP_ADDRESS>
06-15 16:29:59.412  9808  9840 I renderdoc: @60c865070000000b@ RDOC 009808: [16:29:59]    remote_server.cpp(1006) - Log     - <IP_ADDRESS> / <IP_ADDRESS>
06-15 16:29:59.412  9808  9840 I renderdoc: @60c865070000000c@ RDOC 009808: [16:29:59]    remote_server.cpp(1010) - Log     - Allowing execution commands
06-15 16:29:59.412  9808  9840 I renderdoc: @60c865070000000d@ RDOC 009808: [16:29:59]    remote_server.cpp(1014) - Log     - Replay host ready for requests...
06-15 16:29:59.424  9808  9841 I renderdoc: @60c865070000000e@ RDOC 009808: [16:29:59]        vk_replay.cpp(4288) - Log     - Created device.
06-15 16:29:59.446  9808  9838 I renderdoccmd: Done splashing
06-15 16:29:59.446  9808  9838 I renderdoccmd: handle_cmd(6)
06-15 16:29:59.446  9808  9838 I renderdoccmd: doing misc splash
06-15 16:29:59.446  9808  9838 I renderdoccmd: Trying to splash
06-15 16:29:59.446  9808  9838 I renderdoccmd: Doing a splash
06-15 16:29:59.455  9808  9838 I renderdoccmd: Done splashing
06-15 16:30:00.699  9808  9840 I renderdoc: @60c865080000000f@ RDOC 009808: [16:30:00]    remote_server.cpp(1067) - Log     - Connection received from <IP_ADDRESS>.
06-15 16:30:00.699  9808  9840 I renderdoc: @60c8650800000010@ RDOC 009808: [16:30:00]    remote_server.cpp(1090) - Log     - Processing connection
06-15 16:30:00.702  9808  9860 I renderdoc: @60c8650800000011@ RDOC 009808: [16:30:00]    remote_server.cpp( 237) - Log     - Returning OK signal for connection from <IP_ADDRESS>.
06-15 16:30:00.727  9808  9840 I renderdoc: @60c8650800000012@ RDOC 009808: [16:30:00]    remote_server.cpp(1067) - Log     - Connection received from <IP_ADDRESS>.
06-15 16:30:00.727  9808  9840 I renderdoc: @60c8650800000013@ RDOC 009808: [16:30:00]    remote_server.cpp(1090) - Log     - Processing connection
06-15 16:30:00.730  9808  9861 I renderdoc: @60c8650800000014@ RDOC 009808: [16:30:00]    remote_server.cpp( 218) - Log     - Promoting connection from <IP_ADDRESS> to active.
06-15 16:30:00.730  9808  9861 I renderdoc: @60c8650800000015@ RDOC 009808: [16:30:00]    remote_server.cpp( 237) - Log     - Returning OK signal for connection from <IP_ADDRESS>.
06-15 16:30:00.735  9808  9861 I renderdoc: @60c8650800000016@ __rdoc_internal_android_logcat 349420282
...
06-15 16:30:26.423  9808  9861 I renderdoc: @60c865220000009f@ __rdoc_internal_android_logcat 349445970
06-15 16:30:26.425  9808  9861 I renderdoc: @60c86522000000a0@ RDOC 009808: [16:30:26]         streamio.cpp( 415) - Warning - Error reading from socket
06-15 16:30:26.426  9808  9861 I renderdoc: @60c86522000000a1@ RDOC 009808: [16:30:26]    remote_server.cpp( 907) - Log     - Closing active connection from <IP_ADDRESS>.
06-15 16:30:26.426  9808  9861 I renderdoc: @60c86522000000a2@ RDOC 009808: [16:30:26]    remote_server.cpp( 909) - Log     - Ready for new active connection...
06-15 16:30:34.200  9808  9840 I renderdoc: @60c8652a000000a3@ RDOC 009808: [16:30:34]    remote_server.cpp(1067) - Log     - Connection received from <IP_ADDRESS>.
06-15 16:30:34.201  9808  9840 I renderdoc: @60c8652a000000a4@ RDOC 009808: [16:30:34]    remote_server.cpp(1090) - Log     - Processing connection
06-15 16:30:34.203  9808  9968 I renderdoc: @60c8652a000000a5@ RDOC 009808: [16:30:34]    remote_server.cpp( 237) - Log     - Returning OK signal for connection from <IP_ADDRESS>.
06-15 16:30:42.146  9808  9840 I renderdoc: @60c86532000000a6@ RDOC 009808: [16:30:42]    remote_server.cpp(1067) - Log     - Connection received from <IP_ADDRESS>.
06-15 16:30:42.146  9808  9840 I renderdoc: @60c86532000000a7@ RDOC 009808: [16:30:42]    remote_server.cpp(1090) - Log     - Processing connection
06-15 16:30:42.147  9808  9970 I renderdoc: @60c86532000000a8@ RDOC 009808: [16:30:42]    remote_server.cpp( 237) - Log     - Returning OK signal for connection from <IP_ADDRESS>.
06-15 16:30:50.099  9808  9840 I renderdoc: @60c8653a000000a9@ RDOC 009808: [16:30:50]    remote_server.cpp(1067) - Log     - Connection received from <IP_ADDRESS>.
06-15 16:30:50.099  9808  9840 I renderdoc: @60c8653a000000aa@ RDOC 009808: [16:30:50]    remote_server.cpp(1090) - Log     - Processing connection
06-15 16:30:50.109  9808  9981 I renderdoc: @60c8653a000000ab@ RDOC 009808: [16:30:50]    remote_server.cpp( 237) - Log     - Returning OK signal for connection from <IP_ADDRESS>.
06-15 16:31:13.295  9808  9840 I renderdoc: @60c86551000000ac@ RDOC 009808: [16:31:13]    remote_server.cpp(1067) - Log     - Connection received from <IP_ADDRESS>.
06-15 16:31:13.295  9808  9840 I renderdoc: @60c86551000000ad@ RDOC 009808: [16:31:13]    remote_server.cpp(1090) - Log     - Processing connection
06-15 16:31:13.298  9808  9985 I renderdoc: @60c86551000000ae@ RDOC 009808: [16:31:13]    remote_server.cpp( 237) - Log     - Returning OK signal for connection from <IP_ADDRESS>.

ADB server log:
adb I 06-15 16:29:50  6628  4896 auth.cpp:417] adb_auth_init...
adb I 06-15 16:29:50  6628  4896 auth.cpp:152] loaded new key from 'D:\Users\xxx\.android\adbkey' with fingerprint xxx
adb I 06-15 16:29:50  6628  9752 transport.cpp:299] DEVICEID: write thread spawning
adb I 06-15 16:29:50  6628 11324 transport.cpp:327] DEVICEID: read thread spawning
adb I 06-15 16:29:50  6628  4896 adb.cpp:141] DEVICEID: already offline
adb W 06-15 16:30:02  6628  4896 sockets.cpp:279] timeout expired while flushing socket, closing
adb W 06-15 16:30:36  6628  4896 sockets.cpp:279] timeout expired while flushing socket, closing
adb W 06-15 16:30:44  6628  4896 sockets.cpp:279] timeout expired while flushing socket, closing
adb W 06-15 16:30:51  6628  4896 sockets.cpp:279] timeout expired while flushing socket, closing
adb W 06-15 16:31:15  6628  4896 sockets.cpp:279] timeout expired while flushing socket, closing

Environment

RenderDoc version: 1.14 stable
Operating System: Windows 10 x64
Graphics API: unrelated
Android device: OPPO Reno6 (ColorOS), OnePlus 8 (LineageOS)

I'm not able to reproduce this problem. I tried on all the android devices I have available and leaving them idle for 5 minutes each I didn't see any disconnections - I wasn't quite clear on how long since you said 'seconds to minutes' but I assume 5 minutes should have caught it.
I've also not heard any reports from anyone else with this problem so I assume the issue is something specific to your setup, and given that Android is generally very unreliable it doesn't seem to me like a RenderDoc bug.
I don't have any OPPO or OnePlus devices to test with, so it may be something specific to those devices, since some android manufacturers break their devices in different ways as there's not much guaranteed to be universally available on all Android devices. That said I did test on LineageOS on one device and I wouldn't expect it to be broken since it's usually fairly reliable.
It may be something to do with your host system, I'd suggest trying maybe a different version of adb. You could try to use the version packaged with RenderDoc which should be working. If you have a different PC you could try that would be worth testing, or even swapping the USB cable you're using.
I can leave this open for now since I can't prove it's not a RenderDoc bug, but without being able to replicate it or having a specific indication of a RenderDoc bug this seems likely to be an Android problem and so not something I can do anything about.

I expected it to be a setup problem, I just don't know where it could be wrong...
The OnePlus device flashed to an AOSP-based OS should pretty much eliminate the background/battery traits from stock, I reckon.
The adb bundled with your Windows release worked well. I checked the version and it's from Feb 2018, circa platform-tools r27.0.1, and that reminded me of an issue I had earlier with ARM's tools, also solved by switching adb version. I then tried r28.0.1 and r28.0.2, and yes similarly only up to r28.0.1 would play well. Switched to another laptop at work and same thing. I could try my personal PC later to eliminate company policy interference.
Why is this a thing though... Any pointer on tracking it down, or should I at this point just redirect it to Google instead?

Unfortunately I can't help with any bugs in adb, that's not anything I have control over or knowledge of. You'd need to report those bugs to Google. If changing adb version also fixed a very similar problem with a different tool that strongly suggests this is an adb bug and not a bug in RenderDoc, or possibly that you have a corrupt version of adb (or incompatible with the device? I know adb is very particular about versions and has poor version compatibility).
Since this is almost certainly not a RenderDoc bug and nothing I can do with, I'm closing this. I can only suggest that you report the bug to Google or stick with the versions of adb that you found to work.


Link to VSCode marketplace for install instructions

Got a question on twitter about this; would be cool if there was a link to the marketplace (possibly from the readme) to install the extension:
https://marketplace.visualstudio.com/items?itemName=matklad.rust-analyzer

In the process of overhauling the website!
https://rust-analyzer.github.io/

Should we close this?


Reference: Include GPU mitigations from new ScaleLib

Once this item is complete in scalelib, include the relevant release.
https://github.com/Azure/cyclecloud-scalelib/issues/41

Is this done?


Test all Known Coders to ensure they Serialize via URN

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[ ] Make sure the PR title is formatted like:
[BEAM-<Jira issue #>] Description of pull request
[ ] Make sure tests pass via mvn clean verify. (Even better, enable
Travis-CI on your fork and ensure the whole test matrix passes).
[ ] Replace <Jira issue #> in the title with the actual Jira issue
number, if there is one.
[ ] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

Fix Coders to not encode VarIntCoders as VarLongCoders, and
VarLongCoders not as known coders.
Ensure that all known coders are tested.
Use getComponents rather than getCoderArguments for known coders.

R: @lukecwik

Done.

Coverage decreased (-0.007%) to 70.082% when pulling 42f5497509ed8fca716966950b4188e069b1ad2b on tgroh:coders_fixes into dc672f42083c375872d87030523545866cea4f55 on apache:master.

Coverage increased (+0.007%) to 70.096% when pulling 42f5497509ed8fca716966950b4188e069b1ad2b on tgroh:coders_fixes into dc672f42083c375872d87030523545866cea4f55 on apache:master.

LGTM


fix: more disk space

Models require more disk space

Included in https://github.com/Azure/kaito/pull/299


implemetation of request_async

@Valentin-Miroshnichenko thank you ! types for fields was added since 3.6 .

@rogeralsing Shall we give @Valentin-Miroshnichenko permission to the repo?

Invited now :)


Cannot figure out how to go back once the user is in the swagger view

Description:

Open a service -> edit design -> go to swagger view

Issues

Cannot figure out how to go back once the user is in the swagger view
The source view and design view buttons do not have tool tips

Affected Versions:
ballerina-0.970.0
OS, DB, other environment details and versions:
Ubuntu 15.10
Firefox - 59.0.2 (64-bit)

Followup issue #9474


fail to load config.json: JSONDecodeError: Expecting value: line 3 column 24 (char 62)

Hi Kaushal,
I'm trying to use fast_bert to deploy BERT ON aws. I have put config.json file under the pretrained model path. When I load the bertlearner object by below:
BertLearner.from_pretrained_model(databunch,BERT_PRETRAINED_PATH,metrics,device,
logger,finetuned_wgts_path=None,is_fp16=args['fp16'],loss_scale=args['loss_scale'],
multi_gpu=multi_gpu,multi_label=True)
I got the error message like:
JSONDecodeError                           Traceback (most recent call last)
 in ()
3 learner=BertLearner.from_pretrained_model(databunch,BERT_PRETRAINED_PATH,metrics,device,
4         logger,finetuned_wgts_path=None,is_fp16=args['fp16'],loss_scale=args['loss_scale'],
----> 5         multi_gpu=multi_gpu,multi_label=True)
6 frames
/usr/local/lib/python3.6/dist-packages/fast_bert/learner.py in from_pretrained_model(dataBunch, pretrained_path, metrics, device, logger, finetuned_wgts_path, multi_gpu, is_fp16, loss_scale, warmup_proportion, fp16_opt_level, grad_accumulation_steps, multi_label, max_grad_norm, use_amp_optimizer, model_type)
87             model = model_class[1].from_pretrained(pretrained_path,
88                                                                   num_labels = len(dataBunch.labels),
---> 89                                                                   state_dict=model_state_dict)
90         else:
91             model = model_class[0].from_pretrained(pretrained_path,
/usr/local/lib/python3.6/dist-packages/transformers/modeling_utils.py in from_pretrained(cls, pretrained_model_name_or_path, *model_args, **kwargs)
285                 cache_dir=cache_dir, return_unused_kwargs=True,
286                 force_download=force_download,
--> 287                 **kwargs
288             )
289         else:
/usr/local/lib/python3.6/dist-packages/transformers/configuration_utils.py in from_pretrained(cls, pretrained_model_name_or_path, **kwargs)
152
153         # Load config
--> 154         config = cls.from_json_file(resolved_config_file)
155
156         if hasattr(config, 'pruned_heads'):
/usr/local/lib/python3.6/dist-packages/transformers/configuration_utils.py in from_json_file(cls, json_file)
185         with open(json_file, "r", encoding='utf-8') as reader:
186             text = reader.read()
--> 187         return cls.from_dict(json.loads(text))
188
189     def eq(self, other):
/usr/lib/python3.6/json/init.py in loads(s, encoding, cls, object_hook, parse_float, parse_int, parse_constant, object_pairs_hook, **kw)
352             parse_int is None and parse_float is None and
353             parse_constant is None and object_pairs_hook is None and not kw):
--> 354         return _default_decoder.decode(s)
355     if cls is None:
356         cls = JSONDecoder
/usr/lib/python3.6/json/decoder.py in decode(self, s, _w)
337
338         """
--> 339         obj, end = self.raw_decode(s, idx=_w(s, 0).end())
340         end = _w(s, end).end()
341         if end != len(s):
/usr/lib/python3.6/json/decoder.py in raw_decode(self, s, idx)
355             obj, end = self.scan_once(s, idx)
356         except StopIteration as err:
--> 357             raise JSONDecodeError("Expecting value", s, err.value) from None
358         return obj, end
JSONDecodeError: Expecting value: line 3 column 24 (char 62)
I'm running this on colab and have run databunch function correctly. So i assume everything required for that function to run is correct such as data path.
Can you give guidance on how to troubleshoot? Thank you!

I am having a similar issue for AWS SageMaker on training.
The outputted error is as follows:
AlgorithmError: Exception during training: Expecting value: line 1 column 1 (char 0) Traceback (most recent call last): File "/opt/ml/code/train", line 154, in train label_col = json.loads(training_config["label_col"]) File "/usr/lib/python3.7/json/__init__.py", line 348, in loads return _default_decoder.decode(s) File "/usr/lib/python3.7/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) File "/usr/lib/python3.7/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
My training_config.json file is as follows:
{
"run_text": "text-classifier",
"finetuned_model": null,
"do_lower_case": "True",
"train_file": "train.csv",
"val_file": "val.csv",
"label_file": "labels.csv",
"text_col": "text",
"label_col": "label",
"multi_label": "False",
"grad_accumulation_steps": "1",
"fp16_opt_level": "O1",
"fp16": "True",
"model_type": "roberta",
"model_name": "roberta-base",
"logging_steps": "300"
}
Looking at the train file, the json.loads(training_config["label_col"])  should be skipped due to the mulit_label=False...
Any help would be appreciated...

My issue looks to be connected to
if  bool(training_config['multi_label']) == True:
With the config as a string, bool converts the result to True each time and this results in a parsing error in the subsequent lines.

It appears that my error was due to my training_config.json file not being formatted with JSON consistent Boolean values. False and True were read as strings and brought about an error.


optimize: supplementary configuration note information

Ⅰ. Describe what this PR did
supplementary configuration note information
Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

See if you can remove unnecessary configuration from conf.txt?

Codecov Report

Merging #2553 into develop will decrease coverage by 0.13%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             develop    #2553      +/-   ##
=============================================
- Coverage      51.43%   51.29%   -0.14%
  Complexity      2807     2807
=============================================
  Files            553      553
  Lines          17699    17699
  Branches        2089     2060      -29
=============================================
- Hits            9103     9079      -24
- Misses          7743     7744       +1
- Partials         853      876      +23

Impacted Files
Coverage Δ
Complexity Δ

...obuf/convertor/BranchRegisterRequestConvertor.java
90.47% <0.00%> (-9.53%)
3.00% <0.00%> (ø%)

...otobuf/convertor/GlobalBeginResponseConvertor.java
92.59% <0.00%> (-7.41%)
3.00% <0.00%> (ø%)

...otobuf/convertor/GlobalCommitRequestConvertor.java
93.75% <0.00%> (-6.25%)
3.00% <0.00%> (ø%)

...otobuf/convertor/GlobalStatusRequestConvertor.java
93.75% <0.00%> (-6.25%)
3.00% <0.00%> (ø%)

...obuf/convertor/GlobalRollbackRequestConvertor.java
93.75% <0.00%> (-6.25%)
3.00% <0.00%> (ø%)

...protobuf/convertor/RegisterTMRequestConvertor.java
94.73% <0.00%> (-5.27%)
3.00% <0.00%> (ø%)

...protobuf/convertor/RegisterRMRequestConvertor.java
90.47% <0.00%> (-4.77%)
3.00% <0.00%> (ø%)

...otobuf/convertor/BranchReportRequestConvertor.java
95.45% <0.00%> (-4.55%)
3.00% <0.00%> (ø%)

...tobuf/convertor/BranchReportResponseConvertor.java
95.45% <0.00%> (-4.55%)
3.00% <0.00%> (ø%)

...otobuf/convertor/BranchCommitRequestConvertor.java
95.83% <0.00%> (-4.17%)
3.00% <0.00%> (ø%)

... and 12 more

@a364176773 need a brief description of pr title.


make trail renderer not render when going from death place to start

https://github.com/notangoose/The-Nine-Second-Rule/blob/bbb7e35eb0170baac4220f5fb47574628f99edda/Assets/Scripts/PlayerController.cs#L156
the respawn function should turn off the trailrenderer, move the player, then turn it back on


Sonic the Inclusive Hedgehog: Watch dbagenesis.com

Sonic the Inclusive Hedgehog requests the watch of the watch_keyword dbagenesis\.com. See the MS search here and the Stack Exchange search here.

dbagenesis\.com has been seen in 0 true positives, 0 false positives, and 0 NAAs.

Approved by Makyen in Charcoal HQ


Fixed line_item total not being used in tax calculations

There was an issue where the total for the line_item was not being used and only the individual price.

@ericsaupe Code looks good to me, assuming tax adjustments are deleted before this is called.

@acreilly can you test this patch and merge quickly if all looks good?

@dhonig @acreilly Thanks!


Solved Issue #623

If the ingverb is first in method Faker::Hacker.say_something_smart, it was not capitalized. This has been now fixed with a small regex hack.
bundle exec rake ran locally, all green.
Thank you.

Is there a reason not to use the capitalize method here?

Hi. I thought capitalize method applies to every word here. Tested with irb, looks like it works in exactly similar way than my solution. If you want this regex to be re-written as capitalize, I can do so.

Yes, that would be great, thanks!

Sorted out. Please note: If there are other capitalized words in the sentence, then the capitalize method will actually turn them lower-case. This is good to keep in mind for the future. This is why I originally used the regex. But since there are none, the built-in function works just as fine.


Should the serve command save pages by default?

Consider if we should change the serve command to not save pages by default (it's unexpected)

Based on the code and documentation provided, I'll analyze whether the realtime compiler should save previewed pages by default.
Currently, the default behavior is to save preview pages (save_preview = true), as seen in:
    'server' => [
        // The default port the preview is served on
        'port' => env('SERVER_PORT', 8080),

        // The default host the preview is served on
        'host' => env('SERVER_HOST', 'localhost'),

        // Should preview pages be saved to the output directory?
        'save_preview' => true,

However, there are several factors to consider:

Purpose of Preview Server: The realtime compiler is meant for local development and previewing changes, as noted in:

The Hyde Realtime Compiler is included with Hyde installations and is what powers the `php hyde serve` command,
allowing you to preview your static site on a local development server without having to rebuild the site.

Development Focus: Hyde emphasizes developer experience and simplicity, as shown in:

- **Developer experience first:** Creating sites with Hyde and contributing to the framework should be a joy.
- **Zero config setup:** You should be able to just install Hyde and start building your project right away. Hyde should follow convention over configuration and come preconfigured with sensible defaults.
- **Customizable when you need it:** While configuration should not be a requirement, the option should always be there. As such, we should provide easy ways for customization to those who need it.

Storage Implications: Saving previews creates additional files that aren't necessarily needed for development purposes.

Change History: A change was made to add this configuration option, as noted in:

### Added
- Added a RealtimeCompiler config option to disable rendered pages being stored to disk in https://github.com/hydephp/develop/pull/1334

Recommendation:
The default should be changed to false because:

During development/preview, saving files is not typically expected or necessary
It creates unnecessary file operations and storage usage
The primary purpose of php hyde serve is for previewing changes, not generating files
If users need to save the files, they can explicitly enable this via configuration
This aligns better with the principle of least surprise - most developers would expect a preview server to just show changes without writing files

The current default of true seems to go against the expected behavior of a development preview server. The setting should remain configurable, but defaulting to false would be more intuitive and aligned with typical development workflows.

Fixed by https://github.com/hydephp/develop/pull/1995


Add a removeAll pathConf cmd to support remove all path conf

What changes are proposed in this pull request?
Please outline the changes and how this PR fixes the issue.
Why are the changes needed?
Please clarify why the changes are needed. For instance,

If you propose a new API, clarify the use case for a new API.
If you fix a bug, describe the bug.

Does this PR introduce any user facing changes?
Please list the user-facing changes introduced by your change, including

change in user-facing APIs
addition or removal of property keys
webui

I'd propose a different approach to do this. Since there is already a remove command, how about we add a --recursive option to remove, which will recursively removes all path configurations starting with the prefix specified by the positional argument.
For example:
bin/alluxio fsadmin pathConf remove -r /

will recursively remove all path confs set on any level, since it's the root path
bin/alluxio fsadmin pathConf remove -r --key "key1,key2" /

will recursively remove path confs with the keys "key1" and "key2" on any level
Contrarily, without the -r option, only the configuration set on the specific level will be removed:
bin/alluxio fsadmin pathConf remove --key "key1,key2" /

will only remove key "key1" and "key2" on the root path, but leaving the same configurations set on any child paths intact. (which should be the current behavior, if not, please leave a comment.)
Finally, the positional argument should be processed on a path component granularity, rather than character granularity, i.e. /tmp is not a prefix of /tmp1/dir, etc.

@dbw9580 Thanks for your review and suggestion. PTAL

@dbw9580 Thanks for the review comments, I changed the code style, PTAL.

@maobaolong the implementation looks good to me. Can you please add tests for this new feature in alluxio.client.cli.fsadmin.pathconf.RemoveCommandIntegrationTest?

@dbw9580 Thank you for your information, I add a case test to the current UT. PTAL

@dbw9580 PTAL.

@dbw9580 Thanks for the suggestion, I reset the previous commit and push a new one to revert the Confighash related code which is not related to this PR, also, i added the recursive usage to the usage method. PTAL.

@elega @dbw9580 Thanks for the review, as all reviewers approved this PR, I merge this PR now.

alluxio-bot, merge this please


cupy.select produces an error

Description
Error:
  File "/root/raytracer/src/sphere.py", line 39, in hit
    return np.select([choose_t1, choose_t2], [t1, t2], np.nan)
  File "/usr/local/lib/python3.10/dist-packages/cupy/_indexing/indexing.py", line 216, in select
    cupy.copyto(result, default)
  File "/usr/local/lib/python3.10/dist-packages/cupy/_manipulation/basic.py", line 38, in copyto
    can_cast = numpy.can_cast(src, dst.dtype, casting)
TypeError: can_cast() does not support Python ints, floats, and complex because the result used to depend on the value.
This change was part of adopting NEP 50, we may explicitly allow them again in the future.

To Reproduce
import cupy as np
type FloatArray = npt.NDArray[np.float64]

...
def hit(self, r: RayArray) -> FloatArray:
  Arr: TypeAlias = FloatArray
  A: Arr = directions.len_squared()
  B: Arr = -2.0 * (ocs @ directions)
  C: Arr = ocs.len_squared() - radiuses * radiuses
  D: Arr = B*B - 4*A*C

  cond = D >= 0 #BoolArray(fix later)
  sq = np.sqrt(np.maximum(D, 0))
  t1: Arr = np.where(cond, (-B - sq) / (2 * A), np.nan)
  t2: Arr = np.where(cond, (-B + sq) / (2 * A), np.nan)

  # np.isnan(t1) == np.isnan(t2) always since the condition is the same
  choose_t1 = (~np.isnan(t1)) & (t1 <= t2)
  choose_t2 = (~np.isnan(t1)) & (t1 > t2)

  print(type(t1))

  return np.select([choose_t1, choose_t2], [t1, t2], np.nan)

Installation
Source (pip install cupy)
Environment
OS                           : Linux-6.5.0-28-generic-x86_64-with-glibc2.35
Python Version               : 3.10.12
CuPy Version                 : 13.2.0
CuPy Platform                : NVIDIA CUDA
NumPy Version                : 2.0.1
SciPy Version                : None
Cython Build Version         : 0.29.37
Cython Runtime Version       : None
CUDA Root                    : /usr/local/cuda
nvcc PATH                    : /usr/local/cuda/bin/nvcc
CUDA Build Version           : 12040
CUDA Driver Version          : 12040
CUDA Runtime Version         : 12040 (linked to CuPy) / 12040 (locally installed)
cuBLAS Version               : (available)
cuFFT Version                : 11201
cuRAND Version               : 10305
cuSOLVER Version             : (11, 6, 1)
cuSPARSE Version             : (available)
NVRTC Version                : (12, 4)
Thrust Version               : 200200
CUB Build Version            : 200200
Jitify Build Version         : <unknown>
cuDNN Build Version          : None
cuDNN Version                : None
NCCL Build Version           : 22105
NCCL Runtime Version         : 22105
cuTENSOR Version             : None
cuSPARSELt Build Version     : None
Device 0 Name                : NVIDIA GeForce RTX 2070 SUPER
Device 0 Compute Capability  : 75
Device 0 PCI Bus ID          : 0000:03:00.0

Additional Information
No response

This is already fixed for CuPy 13.3 (not yet released), you can downgrade NumPy to numpy<2 to avoid it.

Closing as the fix is already in. We plan to ship the fix this month. Thanks for reporting @chopikus!


Cleanup of Master Category pages

Part of the Epic that is to do with the removal of Bootstrap dependencies and translation changes.

Implemented carbon icons and tooltip in new master category component.

Removed hard coded text from table header and implemented input functionality.

This task/issue is closed.


add getSeason function and name constants

Coverage increased (+0.1%) to 88.38% when pulling 4c593825f7b7d8b42a9bee58f895779e42b1ad2c on phobson:add-getseason into db71f783592881ae4015bce9498d01b6456ab949 on Geosyntec:master.

Coverage increased (+0.14%) to 88.42% when pulling 4dc249db572f7c2e92666c30b34a37d1e1e41d86 on phobson:add-getseason into db71f783592881ae4015bce9498d01b6456ab949 on Geosyntec:master.

Coverage increased (+0.18%) to 88.46% when pulling<PHONE_NUMBER>d4c3206f5d5625cce0ca236166c3e1 on phobson:add-getseason into db71f783592881ae4015bce9498d01b6456ab949 on Geosyntec:master.

Coverage increased (+0.18%) to 88.46% when pulling 1ce7b7bb91cc5b41e5af00bcfda21957ecc64ed3 on phobson:add-getseason into db71f783592881ae4015bce9498d01b6456ab949 on Geosyntec:master.


Invalid link in AAS Part 2 v3.0 Section 12.1 (IDTA Number  01002-3-0)

On page 112 there is the following paragraph
The AAS Repository API including AAS API, Submodel API, Submodel Repository API, Serialization API,
and Self-Description API is available at:
https://app.swaggerhub.com/apis/Plattform_i40/RepositoryServiceSpecification/V3.0_SSP-001#
This is a combination of APIs, which forms a service specification according to the Industrie 4.0 Service
Model in Clause 4.1.

The link does not point to any Swagger document.

Same as for #273, you are of course correct and I have prepared a fix for the bugfix version of Part 2.


Terraform provider does not offer a sequential ordering option - implement as init action

Customers using Terraform report that there is no way to execute initialization actions in a sequence.  This init action may be used as a stopgap.  The paths to be loaded as initialization actions should be specified as a metadata argument in the form of a single string with elements separated by a comma or as designated in another metadata argument or environment variable or ldap entry, etc.

I have found no evidence that the suggestion that these init actions are being run in parallel is true.  However, I am using the terraform 1.3 offered internally.  I need to build the same terraform version as is used by the customer so that I can better know whether to close this issue with "Working as intended".

WAI


Password Reset Functionality Not Working

The "Forgot Password" feature currently doesn't function as expected. When attempting to reset the password after entering a valid email, no reset link or token is sent, making it impossible for users to recover their accounts.
Suggested Fix:
Ensure the system is configured to send password reset emails or tokens securely.
Verify that the mail server or backend responsible for sending reset links is properly set up.
Consider using token-based reset URLs or OTPs for added security.

Assign me this issue . I would love to contribute to it.


Change how the up arrow works

Feedback from a user: when I press the up arrow I expect to move up in the textbook as opposed to a previous prompt, haven’t felt a desire to use it as intended yet

Fixed this, can do both now. Will go back in history only if cursor is at selectionStart === 0


ProgressDivider iOS fix & updates on every 1% of progress fix

This commit fixes two issues:

On iOS when the progress divider was checked if it was 1, the check was being done on an NSNumber which meant it always failed. Converted it to an integer to fix.
Originally the code used a progressDivider <= 1 to indicate that it should send all calls across the bridge. It's quite a common use case to want to be updated on every full percentage though, so I have changed this to use a progressDivider <= 0 as an indication that all progress calls should be sent across the bridge. This fix also changes the default progressDivider value to be 0 & updates the docs to reflect this

@cjdell Thoughts on this? This would be a breaking change.

Just as a side note @johanneslumpe  the progressDivider is only in master, not made it into a release yet, so any disruption should be minimal.

@johanneslumpe @locly I think we should accept this PR, it makes much more sense to have 0 mean everything so 1 can be used for each percentage point. Will give it a test now.

@johanneslumpe @locly Manually merged this in


Verify/cleanup the Kernel monkey patch in vmdb/spec/coverage_helper.rb

Is it still needed with ruby 2.0 and beyond?
https://github.com/ManageIQ/manageiq/blob/f1325ba2c6c70cc6214729873e6724e555078935/vmdb/spec/coverage_helper.rb#L3

This issue is no longer on master


Samples consistency: MixedRealitySceneContent vs SceneContent, etc for top level game object

MaintainerySync note: We should make the top level game object name consistent.  Griff will make them consistent when he does his pass on the description panels.

Folks are leaning towards SceneContent for simplicity. I'll go that route