Issue/20 provider selection in tests

Description
Added support for fine-grained test selection, based on the provider used in the test:

Created marker for each provider type
Created pytest options to select those tests
Updated the documentation to specify those new markers and options

Closes #20

https://github.com/inmanta/terraform/commit/8f33955100b7a034462c0a26e40beb2a5494f08b


[Parser] Missed signed cast of CurPtr

A char is unsigned by default on PowerPC. CurPtr is cast
to a signed char whenever a signed comparison is required,
but we are missing one place.
This fixes a testcase failure in Parse/BOM.swift

Good catch. Please move the cast outside the pointer dereference to avoid introducing a TBAA violation.  IOW, please use "(signed char)*CurPtr++"

Good point, how does this look?

Running tests.

Thank you!

Thanks!


do not scm->registry swizzle by default

motivation: swizzling behavior may come surprising, make it the user decision
changes: disable swizzling by default

@swift-ci smoke test

@compnerd @shahmishal seems like the windows build is broken?

@swift-ci smoke test Windows


Strategy='dp' is not multi-gpu when calling predict()

Bug description
This seems like a feature, but I would argue it's a bug.
Strategy='dp' allows for multi-gpu training, but when called during inference (i.e. model.predict()), it remains single gpu.
This requires one to use strategy='ddp', which is obviously faster for a number of reasons, but if copying the data N times in memory is a constraint, is not ideal.
DP should also be multi-gpu.
What version are you seeing the problem on?
No response
How to reproduce the bug
No response
Error messages and logs
# Error messages and logs here please

Environment

Current environment
#- Lightning Component (e.g. Trainer, LightningModule, LightningApp, LightningWork, LightningFlow):
#- PyTorch Lightning Version (e.g., 1.5.0):
#- Lightning App Version (e.g., 0.5.2):
#- PyTorch Version (e.g., 2.0):
#- Python version (e.g., 3.9):
#- OS (e.g., Linux):
#- CUDA/cuDNN version:
#- GPU models and configuration:
#- How you installed Lightning(`conda`, `pip`, source):
#- Running environment of LightningApp (e.g. local, cloud):

More info
No response

The DP strategy gets set up for all trainer stages the same way, unconditionally here:
https://github.com/Lightning-AI/lightning/blob/a020506a81a671e380872aa5e435647b549e14e6/src/pytorch_lightning/strategies/dp.py#L70-L75
And all step methods run through the DP wrapper:
https://github.com/Lightning-AI/lightning/blob/a020506a81a671e380872aa5e435647b549e14e6/src/pytorch_lightning/strategies/dp.py#L131-L149
In order to make use of multi-gpu, you must use trainer.predict(), not model .predict(). Based on your description, I'm confident that you confused these. This would definitely explain why you saw it only run on a single GPU, and is the expected behavior because the LightningModule itself, when used without the Trainer, will not do any distributed operations by itself.
I'm closing the issue now for these reasons:

model.predict() was called instead of trainer.predict(), observations are expected behavior
We deprecated the DP strategy in 1.9.x and removed it in 2.0.0. The explanation of why can be found in our release notes here. Hence, we will only fix impactful bugs. Otherwise the use of DP remains discouraged and won't see any further development.

Let me know if you have any further questions.


error in search on dev1 (6/28/19 - 1:21 pm) -restricted to 2-handed signs

I was doing some sanity checks on the data now on the dev1 server, and I only found one issue, which is not an error in annotation, but something not working right with the underlying representation or the search:
(1h)part:indef is showing up in a search restricted to 2-handed signs.

This is still a problem.

These two are showing up for a 2-handed search.  The (1h)POINT is an annotation error.  I have fixed and put the file for re-upload.  However, the other one was correctly annotated as 1-handed.  It's just one example.  Not sure why just this one example is showing up in search results restricted to 2-handed signs.


opti: charge_gas

Time spent on this PR:
Pull request type

Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[x] Other (please describe): opti

What is the current behavior?

Resolves #1261
What is the new behavior?

Fix async tests with patching
Tests using get_contract were skipped in local and CI due to not being able to run this function as get_solidity_contract was not awaited and get_contract not marked as async. With those changes, they now run in local and CI. They are using a sync version of get_contract.
chage_gas consume less step
A gain of 10%

Before: 156118
After with ref implementation: 143752
After with inlining: 141462

Test run: poetry run pytest tests/src/kakarot -k test_loop_profiling\[10] --profile-cairo
Before: 156118

After with ref implementation: 143752

After with inlining: 141462

This change is

lgtm under the assumption that gas_left < RC_BOUND

Let's wait to close https://github.com/kkrt-labs/kakarot/pull/1329 before merging this one then


Add header numbering and save numbers to nodes during transform

addNumbersToNodes transform determines numbers for containers, math, and headers and adds them to the respective nodes
header numbering follows 1, 1.1, 1.2, 2 etc pattern based on header depth
numrefs and eq refs are only resolved if node is numbered
tests!

This is dependent on updates to myst-spec here: https://github.com/executablebooks/myst-spec/pull/36

Nice, new changes look good. Will wait til monday morning for https://github.com/executablebooks/myst-spec/pull/36 to merge!


False negative for Pediatric Research/Nature

https://doi.org/10.1203/00006450-199609000-00005 is available at https://www.nature.com/articles/pr19962641 in HTML full text. https://www.nature.com/articles/pr19962641.pdf is a placeholder PDF "Sorry, we don’t have this article in PDF format" although it gives HTTP 200 as status code...
API:
{
  "best_oa_location": null,
  "data_standard": 2,
  "doi": "10.1203/00006450-199609000-00005",
  "doi_url": "https://doi.org/10.1203/00006450-199609000-00005",
  "genre": "journal-article",
  "is_oa": false,
  "journal_is_in_doaj": false,
  "journal_is_oa": false,
  "journal_issns": "0031-3998,1530-0447",
  "journal_name": "Pediatric Research",
  "oa_locations": [],
  "published_date": "1996-09-01",
  "publisher": "Springer Nature",
  "title": "Maternal Acute Fatty Liver of Pregnancy Associated with Fetal Trifunctional Protein Deficiency: Molecular Characterization of a Novel Maternal Mutant Allele",
  "updated": "2018-06-19T02:41:42.279793",
  "year": 1996,
}

https://support.unpaywall.org/public/tickets/70bc6461ff7844e37b2cdbdddd31ad3a32821561d5189395d279003abc9b0782


verified CA token download button broken

After verifying an external CA, I'm unable to download the token. The cert icon is visible, but clicking has no effect.

regarding feature added in https://github.com/openziti/ziti-console/issues/35

Looks like a duplicate issue was opened for this and closed as part of this PR:
https://github.com/openziti/ziti-console/pull/549
Marking this issue as closed.


Type-level narrowing constraints (like as const)

Suggestion
In userland code, you can use as const, but as a library author, I often want to provide the best possible experience, and when there's an opportunity for a literal value to be produced, I would like to infer that value for my users without them having to use (or remember to use) as const.
🔍 Search Terms
constant literals, Math.random, require as const, infer literals, readonly by default
✅ Viability Checklist
My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

⭐ Suggestion
Provide an ability to narrow types at the type level (i.e. without JavaScript where you can use as const).
📃 Motivating Example
const notLiteral = () => "A";

A type like this produces () => string.  I can improve the situation by specifying as const, which will cause it to produce () => "A".

Note: I'm not totally sure how related this is, but I've seen > () => Math.random() > 0.5 ? "A" : "B" which produces () => "A" | "B", and it's not clear to me what the difference is from the example above

However, in the context of a library, a library author doesn't have the option to do this in the type level.  Something for this use-case would be a nice improvement:
////// LIBRARY CODE
const UploadThingServerHelper = <ValidRoutes,>(
  route: {
    readonly [Route in keyof ValidRoutes]: {
      middleware: () => ValidRoutes[Route]; // how can a library author force a more specific type here?
      onUpload: (response: { metadata: ValidRoutes[Route] }) => void;
    };
  }
) => {};

////// END USER CODE
const FileRouter = UploadThingServerHelper({
  example: {
    middleware: () => "someValue", // and end-user must remember to put `as const` here to force it to return a literal
    onUpload: response => {
      response.metadata; // the result is that the type here is not as narrow as it could be for the best user experience
      //       ^?
    },
  },
});

💻 Use Cases
This is useful for libraries trying to provide a great user experience with great inferencing.  It should be a backwards compatible change.  There are no workarounds that I'm aware of (from the code of a library).

You can already do this:
function A<T>(val: T) {}
function B<const T>(val: T) {}

A(123) // Typed number
B(123) // Typed 123

I'm not clear how this solves the use case.  here's a playground link.
Can you update the library code such that response.metadata returns "someValue" not string?
In your example you are typing an argument, but it doesn't seem to work so well if you type the return value:

@dimitropoulos Reusing your example from above, here's how to narrow the type.
type Narrowable = string | number | bigint | boolean;
const UploadThingServerHelper = <ValidRoutes extends Record<string, Narrowable>>(
  route: {
    readonly [Route in keyof ValidRoutes]: {
      middleware: () => ValidRoutes[Route],
      onUpload: (response: { metadata: ValidRoutes[Route] }) => void;
    };
  }
) => {};

ts-toolbelt also has the F.Narrow util that work in a similar way.
middleware: () => F.Narrow<ValidRoutes[Route]>,

I accidentally got pointed here by @jcalz's comment here and it turns out that my PR from yesterday fixes the problem mentioned here. @dimitropoulos, could you check if that covers the whole thing you reported here?

@Andarist I didn't run it myself, but it certainly seems like it would solve the problem!


Like "Export Disparity" but without rgb images

Hi nagadomi! Any chance we can get this option for those who use other methods for the final conversion? Not sure if it will give even a slight boost to speed, but the storage savings and less drive usage would be super helpful.

See #173
One thing to understand is that if you export only the depth from the video, the frame positions may not match the video (RGB frame) for various reasons. That is a more troublesome problem than disk space.
If you want to use other video editing software, it is better to request a Depth Estimation add-on/plugin/custom-node for that software.

So right now I am doing export disparity, and using just the resulting depth PNGs along with the original video in Resolve and it works perfect every time. I never touch the rgb frames except to delete them. Unless the act of creating the rgb frames somehow changes the number or order of the depth PNGs it should work fine, no?

Since iw3 always uses fixed FPS filter, the frame position may be shifted/skipped by start durtion, variable frame rate, changing frame rate etc.
I have no way of knowing how other software handles frame positioning.

I am planning to add a checkbox for Advanced Settings to hide some settings options. I can add "Export (Dpeth Only)" in it. But remember, I do not recommend using that feature in my opinion.

If you think it will definitely not work then that's ok. But if you think there is a chance, I will be happy to test it out! The only necessity is that the depth images come out in the correct order numbered the same way they are now.

When synchronization between depth and rgb frames is required:
The method of outputting depth only can work or not, depending on the input video file and FPS setting.
The method of outputting rgb and depth synchronously works fine in all cases.
In my opinion, using unreliable methods to save disk space is not a good choice.
However, there are cases where only depth is required without need to synchronize with rgb frames, e.g. controlnet input. For this super logical reason I can add Export (Depth Only) feature.

I'd like to give it a try and see what you are talking about if you don't mind

seconding this, would be very helpful in multi-pass 3D renderings by saving storage space (and possibly processing power depending on how it was implemented)


avr/DA/DB/DD

Will the library work properly with the avr/DA/DB/DD ?

Unlikely. This library was written for Arduino/ESP compatible devices. Someone may be able to get it working with other hardware, but that isn't something I'm able to help with.

if he uses the dxcore core (Arduino core for AVR DA, DB,  DD-series)and the Arduino IDE, can it change the situation?

I do not know. I have no experience with that. All I can suggest is to try it and see!


Can organization admins add new skills to the system?

Can an organization admin add new skills to the system, and if not, should they be able to?
As new organizations come to use the system, they will want skills to be available that are relevant to the particular domains they work under. So, someone fitting a smoke alarm for example could, conceivably, have a skill of "Ladder Operation".
I am unable to confirm this directly as I cannot verify a new account to use as an organization admin.
If organization admins can add new skills directly, then I would suggest this issue be abandoned.
@billwagner, @oohmcgoo

Tagging @ohmcgoo and @tonysurma for guidance here.

My apologies Adam-p - I have two different projects open on Github and I have unfortunately raised some issues against your system that were intended for htbox/allready.
My apologies - they'll drag me out the building and throw me in the Thames momentarily!
Martin.


Battleye Remotexec log

I am getting the following in my remote exex log. Any ideas?
#0 "avs_fnc_refuelpayment ["DwbiNoYk",R :1 (Spackler) REMOTE,-250,false]"

Have you merge your "description.ext" with that of mod, like explain in "Installation.txt" ?

If yes, add this line in your remoteexec.txt (Line 2):
!="avs_fnc_refuelpayment [.,.]"


topicctl: 1.1.1 -> 1.2.0

Motivation for this change
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[X] Tested, as applicable: I ran this against a work kafka cluster and it was fine
[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[X] Tested basic functionality of all binary files (usually in ./result/bin/)

Thanks! ^_^


[containerapp] Add Support for Qdrant dev service

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

For new extensions:

[x] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

containerapp

this is ready for review, i believe.

more comment add.

added env deletion after test run.

@zhoxing-ms could you please help review this PR. it's a part of ongoing Springboard dev services work for container apps and some upcoming demos are contingent on it. thank you!!

@Greedygre Could you please help review this PR?

https://github.com/Azure/azure-cli-extensions/pull/6726#issuecomment-1707396143 If you want to release a new extension version for this PR, please also upgrade the version defined in setup.py

Hi @bgashirabake
Could you please comments for fix the history.rst.

@Greedygre Could you please help review this PR?

I have reviewed this PR.

#6726 (comment) If you want to release a new extension version for this PR, please also upgrade the version defined in setup.py

BTW, #bgashirabake
We generally release new extension versions periodically. Please do not update setup.py .

@Greedygre Could you please help review this PR?

i hadn't seen @Greedygre's comments. resolving them now.


Automated cherry pick of #6321: Remove unexpected AltName after rename interface (#6321)

Cherry pick of #6321 on release-2.0.
#6321: Remove unexpected AltName after rename interface (#6321)
For details on the cherry pick process, see the cherry pick requests page.

@gran-vmv there are lots of golangci-lint error shows cannot use &netlink.Handle{}... I suppose we need to do netlink bump up as well for old releases?

This PR rely on #6193 backported.


The page build failed with the tag "asset_path"

The page build failed with the following error:
The tag asset_path on line 1 in _posts/2016-10-15-chalk-sample-post-with-all-elements.md is not a recognized Liquid tag. For more information, see https://help.github.com/articles/page-build-failed-unknown-tag-error.
I think, The tag "og_image" is not configured....

@nowStackOverflow I'll fix that tonight! Thanks for finding out :)

@nowStackOverflow I cannot replicate this issue. For me it works perfectly.

Did you run bundle install?

@nielsenramon Hei~I also have the same error.
I just forked your theme and changed the CNAME. And every time I tried to change some original documents or create a new one, I got a e-mail to remind me there is en error.

I tried many ways to solve this error.  but I haven't figured out yet. This repository is being used experimentally on my repository.

@nowStackOverflow @longxyer You cannot use Chalk the default way on Jekyll btw, you have to use bin/deploy to do so. Chalk uses non-supported plugins.
bin/deploy will push a working version to gh-pages branch :)

Thank you for your answers...
So...
Do I have to repeat it everytime?
like this?
git add -fA
git commit --allow-empty -m "$(git log -1 --pretty=%B) [ci skip]"
git push -f -q origin gh-pages

@nowStackOverflow Please read the README.
All you have to do is push to your master branch (or any other branch) and run bin/deploy
This will take care of everything.
More information can be found here: http://kickster.nielsenramon.com/


Fix scheme for URIs, add coverage to detect regressions in the future.

https://github.com/bytecodealliance/wasmtime/pull/6357 broke the scheme formatting by adding an extra :// but the tests didn't have enough coverage to catch it.
Improve the tests, fix the bug.
cc @pchickey @eduardomourar

@alexcrichton this should probably be cherry-picked into 9.0.x because without it, http requests are pretty broken.

Given the experimental status of wasi-http I would personally say that this doesn't warrant a backport, but I'll defer to @pchickey's judgement.

Because, as Brendan says, requests are pretty broken without this fix, I will take care of backporting it to the release branch.

@pchickey thanks, sorry, I should have checked if that commit was in the 9.0.x branch before I made my comment, I just assumed it was...


Discuss addtional links on index page

We could link to some additional pages from the landing page with tiles e.g.:

RDMkit TSD assembly
NFEGA
DSW-NO
FAIRdom Hub
...

We decided to create two sections: Knowledge Sources (1), and Norwegian RDM Tools (2)
DSW-NO and NFEGA will go under (2)
FAIRdom Hub under (1)
Life Sciences RDM group Norway under (1)

FAIRdom Hub under (1) - this is more a tool than a knowledge resource.
Life Sciences RDM group Norway under (1) - maybe this deserves an entry somewhere else?

Can we resolve this one, @korbinib? let me know and I can make the changes


Custom element UI

Can the picker palette be launched outside of the iFrame generated when using the element custom UI.  Alternatively, can the built-in picker palette to WCH be called using parameters including a call-back.

The picker can be loaded in any iframe element within a page, so I may need more details on what you're trying to implement.
The picker has several configurable settings we set via query parameters in the URL. This typically controls what kind of content the picker can return. Regarding callbacks, when an image / content is selected, the picker sends a parent POST message that contains information about that CONTENT or ASSET.
The picker also sends additional parent POST messages that we use as callbacks inside of WCH but if the picker is loaded outside of WCH these are disabled by default. You can enable them by adding sendCustomEvents=true as a query param to your request for the picker. The only events we send at this time are:
assetLicensingInProgress: this message is fired when an asset begins licensing inside of the picker.
assetLicensingCompleted: this message is fired when an asset completes licensing or runs into an error
close: this message is fired when the user presses his ESC key when inside of the picker (which should close the picker if the parent frame is listening for this message)


Add authorization header on ajax request

hi I was wondering if there was anyway to add authorization header on ajax request ?

Yes, you can accomplish this by defining custom function for fetching data from server:
$('textarea').mentionsInput({
    source: function(request, callback) {
        $.get({
            url: 'http://example.com',
            data: {term: request.term},
            success: callback,
            beforeSend: function (xhr) {
                xhr.setRequestHeader ("Authorization", "Basic " + btoa(username + ":" + password));
            }
        });
    }
});


[otbn] Should we error out when incrementing "past 31" for WDR in BN.LID / BN.SID

When discussing the behaviour of increments, Philipp suggested that we could raise an error if the WDR index was incremented past 31, since it probably shows a bug in the code.
The current spec allows code like this:
    addi x2, x0, 16
    addi x3, x0, 24
    addi x4, x0, 0x100
    loopi 8, 3
      bn.lid x2++, 0(x4)
      bn.lid x3++, 32(x4)
      addi x4, x4, 64

to load up "striped" data without too much pointer manipulation. The last iteration of that loop will wrap x3 around from 0x1f to zero. This wouldn't be allowed with the proposed change.
Should we raise an error in this case?

Presumably we want whatever behaviour we choose to be consistent with BN.MOVR too?
I was wondering if we should raise an error if the GPR doesn't contain a valid WDR Index (i.e. it's a number greater than 31). Currently we just feed the bottom 5 bits as a register read address and ignore the rest. While the wrapping behaviour could be useful an out of range index seems more like a straight programming error in all cases.

Presumably we want whatever behaviour we choose to be consistent with BN.MOVR too?
I was wondering if we should raise an error if the GPR doesn't contain a valid WDR Index (i.e. it's a number greater than 31). Currently we just feed the bottom 5 bits as a register read address and ignore the rest. While the wrapping behaviour could be useful an out of range index seems more like a straight programming error in all cases.

Yes, definitely about BN.MOVR.
For the top bits of the WDR index... maybe? I'm not keen, but only because it means the RIG won't generate quite such "random" programs. Probably not a strong argument! Since we have an ANDI instruction, I would think that any code that genuinely wants to grab the bottom bits from something could use that to only take a 1-cycle penalty.

Yes, definitely about BN.MOVR.
For the top bits of the WDR index... maybe? I'm not keen, but only because it means the RIG won't generate quite such "random" programs. Probably not a strong argument! Since we have an ANDI instruction, I would think that any code that genuinely wants to grab the bottom bits from something could use that to only take a 1-cycle penalty.

Yes, definitely about BN.MOVR.
For the top bits of the WDR index... maybe? I'm not keen, but only because it means the RIG won't generate quite such "random" programs. Probably not a strong argument! Since we have an ANDI instruction, I would think that any code that genuinely wants to grab the bottom bits from something could use that to only take a 1-cycle penalty.

Yes, definitely about BN.MOVR.
For the top bits of the WDR index... maybe? I'm not keen, but only because it means the RIG won't generate quite such "random" programs. Probably not a strong argument! Since we have an ANDI instruction, I would think that any code that genuinely wants to grab the bottom bits from something could use that to only take a 1-cycle penalty.

@cdgori commented on the parent issue, and I'm copying the comment here to keep everything together:

Seems like the re-alignment of zero-reg will make this wrapping behavior more likely/common? So allowing the wrap around is necessary/useful. I had originally thought we could just narrow the functionality to disallow this wrap but seems like that is not going to be the case.
I do think having any bits 31..5 set in the WDR reference is very bad and we should detect it. I'm also not convinced that alert is sufficient here, maybe some more drastic action is needed, as we would have for detected glitches/faults. (I am not generally sympathetic to "programmer error" here as this code should be very thoroughly tested, so things that should not occur should be flagged as such, because they are often indicators of / correlated to attack scenarios.)

@cdgori commented on the parent issue, and I'm copying the comment here to keep everything together:

Seems like the re-alignment of zero-reg will make this wrapping behavior more likely/common? So allowing the wrap around is necessary/useful. I had originally thought we could just narrow the functionality to disallow this wrap but seems like that is not going to be the case.
I do think having any bits 31..5 set in the WDR reference is very bad and we should detect it. I'm also not convinced that alert is sufficient here, maybe some more drastic action is needed, as we would have for detected glitches/faults. (I am not generally sympathetic to "programmer error" here as this code should be very thoroughly tested, so things that should not occur should be flagged as such, because they are often indicators of / correlated to attack scenarios.)

Probably part (2) is more relevant to #4806 (I'll update that in a sec).

Probably part (2) is more relevant to #4806 (I'll update that in a sec).

The plan:

Raise an error if any of the top bits are set.
Increment without wrap-around. That way, you can increment from w31 to "32". That's fine, but using the register again will cause an error.

RIG changes required are tracked in #5731.


Dockerfile scanning

5 new dockerfile checks.
From CIS:

Ensure that COPY is used instead of ADD in Dockerfiles
Ensure that HEALTHCHECK instructions have been added to container images
Ensure update instructions are not use alone in the Dockerfile
Ensure that a user for the container has been created

Just a best practices:

Ensure port 22 is not exposed

similar: hadolint


Add transparent robocop logo in PNG format

A logo is a modification of original Robot Framework logo which is published under Creative Commons (CC BY-SA 4.0) license.
It has integrated police hat that refers to RoboCop - a fictional cybernetic police officer.
The logo symbolizes a person that always stick to the rules 😉.
Original RoboCop had 3 prime directives that he was following which also drives the progress of robotframework-robocop:

First Directive: Serve the public trust

Which lies behind the creation of the project - to serve developers as a tool to build applications they can trust

Second Directive: Protect the innocent

Where the innocent is a tester or a developer that has no intention to produce ugly code but sometimes, you know, it just happens

Third Directive: Uphold the law

Following the coding guidelines established in the project are something very important to keep the code clean, readable and understandable by others and robotframework-robocop is a tool that can help to stick the rules.

Please add those sentences to our readme as our motto from now on :)!


Fix headers logic in json-schema loader

Description
I've noticed two issues with json-schema loader that affect the functionality of network request resolvers.

The headers defined in the schema have precedence over the headers defined in the Mesh handler config
Interpolated headers are attached with an "undefined" value

Point 1 means that if a user defines in the source handler that a header value should come from a specific variable (e.g. from context), this will be ignored because the default header defined in the schema overrides this by always applying the header value from args.
Point 2 means that headers with an interpolated value that resolves to "undefined" are sent to the underlying API, which might well reject the request because of an unexpected header value (e.g. "api-version: undefined"). Headers with this value should simply not be sent to the server.
Type of change

[x] Bug fix (non-breaking change which fixes an issue)

Checklist:

[x] I have followed the CONTRIBUTING doc and the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings
[x] New and existing unit tests and linter rules pass locally with my changes

Fixed via #4506


Support for ephemeral containers .. NamespaceMode=Target

CRI-API interface has added a namespace mode=Target where we can specify the container to share namespaces (PID, IPC) with another container in the same pod. Is there plan to support this NamespaceMode?
Ref: https://github.com/kubernetes/cri-api/commit/758f2d9705802acd1678630cac0abcba51e869a4

Not planned yet... let's see if this makes sense for containerd v1.5.
Related links.
KEP: https://git.k8s.io/enhancements/keps/sig-node/20190212-ephemeral-containers.md
Follow up KEP for finishing out ephemeral support: https://github.com/kubernetes/enhancements/pull/1690
PR for kublet/dockershim changes and related CRI changes: https://github.com/kubernetes/kubernetes/pull/84731

@phanhuy1502  Containerd has been support this. See: Support PID NamespaceMode_TARGET


Add config map to the README

Adding the configmap and explanations about its values to the README

/lgtm


Avoid adding new copies of the SDK compiled to Javascript

Running programs compiled by DDC requires the dart sdk libraries are compiled to a Javascript module. There are currently three module formats distributed with the SDK. We want to add a forth. We also need to add sound null safety versions.
That means distributing 8 versions of the sdk compiled to Javascript for DDC.
Removing the existing versions has been difficult but it's doable. See https://github.com/dart-lang/sdk/issues/35988
We would like to avoid adding more copies and generate them locally as needed.

All integrations of DDC now build their own version of the dart sdk to Javascript so we no longer need to distribute them. Going forward we are no longer going to include them in new versions of the SDK. For backwards compatibility the versions are still there that support running with weak null safety, but to my knowledge none of the supported build systems still use them. We might remove them in an upcoming release, or just wait until we no longer support weak mode.


Align with CI repo

https://github.com/jonhoo/rust-ci-conf

Codecov Report

Merging #44 (6c2c554) into main (c851429) will increase coverage by 12.5%.
The diff coverage is n/a.

Additional details and impacted files

Impacted Files
Coverage Δ

src/record.rs
100.0% <0.0%> (ø)

src/pointer.rs
100.0% <0.0%> (ø)

src/hazard.rs
78.0% <0.0%> (+1.5%)
:arrow_up:

src/domain.rs
92.1% <0.0%> (+10.9%)
:arrow_up:

src/lib.rs
58.9% <0.0%> (+26.5%)
:arrow_up:


fix fcd example

Overall, I think we may want to make the contract a little bit applicable to some typical use-cases.
For example, we check the latest UmbChain price and make certain decisions such us sending token to someone.
Betting platform.

submitBet: ETH-USD > 1000 within 1 month
getWin(int betID) {
Bet bet = bets[betID];
if (chainUmb(bet.ticker) > bet.value && (block.timestamp - bet.time) < bet.duration) {
umbToken.transfer(bet.address);
}
}

This is a very simple scenario, yet it can be used in in the real world.

Overall, I think we may want to make the contract a little bit more applicable to some typical use-cases.

the goal of this reference app is not to create product, but to show how to connect and use oracle. We need to keep it as simple as possible.

demonstrates some flaws in our design

what flow?

is to primitive

this is the whole point of this app - must be as simple as possible.

👍


dockerize sandmark-nightly

Setup of sandmark-nightly on multiple machines can be made easier as a docker container

This issue can be closed because Dockerfile to run nightly app in a docker container now added


[svelte-flow] base.css: controls not styled

Describe the Bug
...
Your Example Website or App
No response
Steps to Reproduce the Bug or Issue
...
Expected behavior
...
Screenshots or Videos
No response
Platform

OS: [e.g. macOS, Windows, Linux]
Browser: [e.g. Chrome, Safari, Firefox]
Version: [e.g. 91.1]
...

Additional context
No response

fixed in 0.0.20

Controls set the background
？


Upon opening planner

-Displayed current day at the top of the calendar
-scroll function presents time blocks for standard business hours

Have completed time and day on planner

This is completed. The display clock function pulls the date from a locale time string. The layout of the date is also specified in this function.


[Device Support Request] Danfoss Icon2 Room Sensor (088U2121)

Problem description
I would like to have the Danfoss Icon2 Room Sensor (088U2121) fully supported under ZHA.
Note that there is a similar request for zigbee2mqtt, Danfoss Icon2 Room Sensor (088U2121).
The device is recognized by ZHA but some values returned are incorrect:
Device info 0x8040 by Danfoss Firmware: 0x0000010c
IEEE: 8c:f6:81:ff:fe:82:4a:00
Nwk: 0xc938
Device Type: EndDevice
LQI: 255
RSSI: -33
Last seen: 2024-01-15T16:33:34
Power source: Battery or Unknown
Controls
Thermostat Heat 21 °C Currently: 24.2 °C
Sensors
Humidity 26.0%
HVAC action Unknown
Temperature -327.7 °C
Diagnostic
Battery 100%
Identity PRESS
LQI
RSSI
Logbook
January 15, 2024
Danfoss 0x8040 Identify changed to January 15, 2024 at 4:20 PM triggered by service Button: Press
4:20:48 PM - 25 minutes ago - John Connett
Note that the Thermostat temperature is correct (24.2 °C) but the Sensors temperature is wrong (-327.7 °C)
Solution description
I would like the Danfoss Icon2 Room Sensor (088U2121) to be fully supported.
Screenshots/Video
Screenshots/Video
[Paste/upload your media here]

Device signature
Device signature
{
  "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4678, maximum_buffer_size=82, maximum_incoming_transfer_size=82, server_mask=11264, maximum_outgoing_transfer_size=82, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)",
  "endpoints": {
    "1": {
      "profile_id": "0x0104",
      "device_type": "0x0301",
      "input_clusters": [
        "0x0000",
        "0x0001",
        "0x0003",
        "0x0020",
        "0x0201",
        "0x0204",
        "0x0402",
        "0x0405",
        "0x0b05"
      ],
      "output_clusters": [
        "0x0003",
        "0x0019"
      ]
    }
  },
  "manufacturer": "Danfoss",
  "model": "0x8040",
  "class": "zigpy.device.Device"
}

Diagnostic information
Diagnostic information
{
  "home_assistant": {
    "installation_type": "Home Assistant OS",
    "version": "2024.1.3",
    "dev": false,
    "hassio": true,
    "virtualenv": false,
    "python_version": "3.11.6",
    "docker": true,
    "arch": "x86_64",
    "timezone": "Europe/London",
    "os_name": "Linux",
    "os_version": "6.1.71-haos",
    "supervisor": "2023.12.0",
    "host_os": "Home Assistant OS 11.4",
    "docker_version": "24.0.7",
    "chassis": "vm",
    "run_as_root": true
  },
  "custom_components": {},
  "integration_manifest": {
    "domain": "zha",
    "name": "Zigbee Home Automation",
    "after_dependencies": [
      "onboarding",
      "usb"
    ],
    "codeowners": [
      "@dmulcahey",
      "@adminiuga",
      "@puddly",
      "@TheJulianJES"
    ],
    "config_flow": true,
    "dependencies": [
      "file_upload"
    ],
    "documentation": "https://www.home-assistant.io/integrations/zha",
    "iot_class": "local_polling",
    "loggers": [
      "aiosqlite",
      "bellows",
      "crccheck",
      "pure_pcapy3",
      "zhaquirks",
      "zigpy",
      "zigpy_deconz",
      "zigpy_xbee",
      "zigpy_zigate",
      "zigpy_znp",
      "universal_silabs_flasher"
    ],
    "requirements": [
      "bellows==0.37.6",
      "pyserial==3.5",
      "pyserial-asyncio==0.6",
      "zha-quirks==0.0.109",
      "zigpy-deconz==0.22.4",
      "zigpy==0.60.4",
      "zigpy-xbee==0.20.1",
      "zigpy-zigate==0.12.0",
      "zigpy-znp==0.12.1",
      "universal-silabs-flasher==0.0.15",
      "pyserial-asyncio-fast==0.11"
    ],
    "usb": [
      {
        "vid": "10C4",
        "pid": "EA60",
        "description": "*2652*",
        "known_devices": [
          "slae.sh cc2652rb stick"
        ]
      },
      {
        "vid": "1A86",
        "pid": "55D4",
        "description": "*sonoff*plus*",
        "known_devices": [
          "sonoff zigbee dongle plus v2"
        ]
      },
      {
        "vid": "10C4",
        "pid": "EA60",
        "description": "*sonoff*plus*",
        "known_devices": [
          "sonoff zigbee dongle plus"
        ]
      },
      {
        "vid": "10C4",
        "pid": "EA60",
        "description": "*tubeszb*",
        "known_devices": [
          "TubesZB Coordinator"
        ]
      },
      {
        "vid": "1A86",
        "pid": "7523",
        "description": "*tubeszb*",
        "known_devices": [
          "TubesZB Coordinator"
        ]
      },
      {
        "vid": "1A86",
        "pid": "7523",
        "description": "*zigstar*",
        "known_devices": [
          "ZigStar Coordinators"
        ]
      },
      {
        "vid": "1CF1",
        "pid": "0030",
        "description": "*conbee*",
        "known_devices": [
          "Conbee II"
        ]
      },
      {
        "vid": "0403",
        "pid": "6015",
        "description": "*conbee*",
        "known_devices": [
          "Conbee III"
        ]
      },
      {
        "vid": "10C4",
        "pid": "8A2A",
        "description": "*zigbee*",
        "known_devices": [
          "Nortek HUSBZB-1"
        ]
      },
      {
        "vid": "0403",
        "pid": "6015",
        "description": "*zigate*",
        "known_devices": [
          "ZiGate+"
        ]
      },
      {
        "vid": "10C4",
        "pid": "EA60",
        "description": "*zigate*",
        "known_devices": [
          "ZiGate"
        ]
      },
      {
        "vid": "10C4",
        "pid": "8B34",
        "description": "*bv 2010/10*",
        "known_devices": [
          "Bitron Video AV2010/10"
        ]
      }
    ],
    "zeroconf": [
      {
        "type": "_esphomelib._tcp.local.",
        "name": "tube*"
      },
      {
        "type": "_zigate-zigbee-gateway._tcp.local.",
        "name": "*zigate*"
      },
      {
        "type": "_zigstar_gw._tcp.local.",
        "name": "*zigstar*"
      },
      {
        "type": "_uzg-01._tcp.local.",
        "name": "uzg-01*"
      },
      {
        "type": "_slzb-06._tcp.local.",
        "name": "slzb-06*"
      }
    ],
    "is_built_in": true
  },
  "data": {
    "ieee": "**REDACTED**",
    "nwk": 16866,
    "manufacturer": "Danfoss",
    "model": "0x8040",
    "name": "Danfoss 0x8040",
    "quirk_applied": false,
    "quirk_class": "zigpy.device.Device",
    "quirk_id": null,
    "manufacturer_code": 4678,
    "power_source": "Battery or Unknown",
    "lqi": 255,
    "rssi": -5,
    "last_seen": "2024-01-16T15:05:42",
    "available": true,
    "device_type": "EndDevice",
    "signature": {
      "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4678, maximum_buffer_size=82, maximum_incoming_transfer_size=82, server_mask=11264, maximum_outgoing_transfer_size=82, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)",
      "endpoints": {
        "1": {
          "profile_id": "0x0104",
          "device_type": "0x0301",
          "input_clusters": [
            "0x0000",
            "0x0001",
            "0x0003",
            "0x0020",
            "0x0201",
            "0x0204",
            "0x0402",
            "0x0405",
            "0x0b05"
          ],
          "output_clusters": [
            "0x0003",
            "0x0019"
          ]
        }
      },
      "manufacturer": "Danfoss",
      "model": "0x8040"
    },
    "active_coordinator": false,
    "entities": [
      {
        "entity_id": "sensor.danfoss_0x8040_battery",
        "name": "Danfoss 0x8040"
      },
      {
        "entity_id": "sensor.danfoss_0x8040_temperature",
        "name": "Danfoss 0x8040"
      },
      {
        "entity_id": "sensor.danfoss_0x8040_humidity",
        "name": "Danfoss 0x8040"
      },
      {
        "entity_id": "sensor.danfoss_0x8040_hvac_action",
        "name": "Danfoss 0x8040"
      },
      {
        "entity_id": "climate.danfoss_0x8040_thermostat",
        "name": "Danfoss 0x8040"
      },
      {
        "entity_id": "button.danfoss_0x8040_identify",
        "name": "Danfoss 0x8040"
      }
    ],
    "neighbors": [],
    "routes": [],
    "endpoint_names": [
      {
        "name": "THERMOSTAT"
      }
    ],
    "user_given_name": null,
    "device_reg_id": "0bfcfdb1b6dd7085664c22e6e2ca3a07",
    "area_id": null,
    "cluster_details": {
      "1": {
        "device_type": {
          "name": "THERMOSTAT",
          "id": 769
        },
        "profile_id": 260,
        "in_clusters": {
          "0x0000": {
            "endpoint_attribute": "basic",
            "attributes": {
              "0x0004": {
                "attribute_name": "manufacturer",
                "value": "Danfoss"
              },
              "0x0005": {
                "attribute_name": "model",
                "value": "0x8040"
              }
            },
            "unsupported_attributes": {}
          },
          "0x0001": {
            "endpoint_attribute": "power",
            "attributes": {
              "0x0021": {
                "attribute_name": "battery_percentage_remaining",
                "value": 200
              }
            },
            "unsupported_attributes": {
              "0x0020": {
                "attribute_name": "battery_voltage"
              },
              "0x0033": {
                "attribute_name": "battery_quantity"
              },
              "0x0031": {
                "attribute_name": "battery_size"
              }
            }
          },
          "0x0003": {
            "endpoint_attribute": "identify",
            "attributes": {},
            "unsupported_attributes": {}
          },
          "0x0020": {
            "endpoint_attribute": "poll_control",
            "attributes": {
              "0x0000": {
                "attribute_name": "checkin_interval",
                "value": 13200
              }
            },
            "unsupported_attributes": {}
          },
          "0x0201": {
            "endpoint_attribute": "thermostat",
            "attributes": {
              "0x001b": {
                "attribute_name": "ctrl_sequence_of_oper",
                "value": 2
              },
              "0x0000": {
                "attribute_name": "local_temperature",
                "value": 2392
              },
              "0x0016": {
                "attribute_name": "max_heat_setpoint_limit",
                "value": 3500
              },
              "0x0015": {
                "attribute_name": "min_heat_setpoint_limit",
                "value": 400
              },
              "0x0012": {
                "attribute_name": "occupied_heating_setpoint",
                "value": 2100
              },
              "0x001c": {
                "attribute_name": "system_mode",
                "value": 4
              }
            },
            "unsupported_attributes": {
              "0x0002": {
                "attribute_name": "occupancy"
              },
              "0x0003": {
                "attribute_name": "abs_min_heat_setpoint_limit"
              },
              "0x0004": {
                "attribute_name": "abs_max_heat_setpoint_limit"
              },
              "0x0005": {
                "attribute_name": "abs_min_cool_setpoint_limit"
              },
              "0x0006": {
                "attribute_name": "abs_max_cool_setpoint_limit"
              },
              "0x0007": {
                "attribute_name": "pi_cooling_demand"
              },
              "0x0008": {
                "attribute_name": "pi_heating_demand"
              },
              "0x0010": {
                "attribute_name": "local_temperature_calibration"
              },
              "0x0017": {
                "attribute_name": "min_cool_setpoint_limit"
              },
              "0x0011": {
                "attribute_name": "occupied_cooling_setpoint"
              },
              "0x0013": {
                "attribute_name": "unoccupied_cooling_setpoint"
              },
              "0x0014": {
                "attribute_name": "unoccupied_heating_setpoint"
              },
              "0x0018": {
                "attribute_name": "max_cool_setpoint_limit"
              },
              "0x001e": {
                "attribute_name": "running_mode"
              },
              "0x0029": {
                "attribute_name": "running_state"
              }
            }
          },
          "0x0204": {
            "endpoint_attribute": "thermostat_ui",
            "attributes": {},
            "unsupported_attributes": {}
          },
          "0x0402": {
            "endpoint_attribute": "temperature",
            "attributes": {
              "0x0000": {
                "attribute_name": "measured_value",
                "value": -32768
              }
            },
            "unsupported_attributes": {}
          },
          "0x0405": {
            "endpoint_attribute": "humidity",
            "attributes": {
              "0x0000": {
                "attribute_name": "measured_value",
                "value": 2700
              }
            },
            "unsupported_attributes": {}
          },
          "0x0b05": {
            "endpoint_attribute": "diagnostic",
            "attributes": {},
            "unsupported_attributes": {}
          }
        },
        "out_clusters": {
          "0x0003": {
            "endpoint_attribute": "identify",
            "attributes": {},
            "unsupported_attributes": {}
          },
          "0x0019": {
            "endpoint_attribute": "ota",
            "attributes": {},
            "unsupported_attributes": {}
          }
        }
      }
    }
  }
}

Logs
Logs
[Paste the logs here]

Custom quirk
Custom quirk
[Paste your custom quirk here]

Additional information
No response

As noted against the zigbee2mqtt issue:
According to the Cluster Library Specification Document 07-5123 Revision 8 in section <IP_ADDRESS>.1 MeasuredValue Attribute: A MeasuredValue of 0x8000 indicates that the temperature measurement is unknown.
So it appears to be a valid response when the temperature measurement is unknown. Perhaps there should be a test for that specific value rather than reporting -327.68 °C?

This may be slightly off-topic. I was comparing the contents of Download diagnostics with attributes visible through Manage zigbee device.
For example, consider the Cluster Library Specification Document 07-5123 Revision 8, section 6.6 Thermostat User Interface Configuration. The relevant section of the diagnostics is:
          "0x0204": {
            "endpoint_attribute": "thermostat_ui",
            "attributes": {},
            "unsupported_attributes": {}

However, if inspected using Manage zigbee device then three attributes are visible, two mandatory: TemperatureDisplayMode (Id: 0x0000) and KeypadLockout (Id: 0x0001); and one optional: ScheduleProgrammingVisibility (Id: 0x0002). READ ATTRIBUTE returns values for the two mandatory attributes and None for the optional attribute.
I would have expected Download diagnostics, in this case, to list the two mandatory attributes and list ScheduleProgrammingVisibility in unsupported_attributes. I'm not sure if this is a bug or a feature ...
My experience with ZHA is very limited. If there is a tool that can characterize which attributes are supported by a new device that would be very useful. Would stepping through all the options in Manage zigbee device uncover them?

Still interested in full support for this device. Will put in more effort if time permits.

If I can be at any help with getting info about the device (we're having both 088U2121 and 088U2122 in our house), I would gladly help.
Unfortunately my knowledge on how to create quirks and similar in HA is limited (haven't done that yet).
//Anders


What to do after Maven build succeeded?

I'm using Eclipse and I' have a Maven project that includes the library (it is in Eclipse), the dependencies in the xml file and my own programm code.
After I added the Apikey and secretkey to the variables, I ran it as a Maven build (took "clean verify" as lifecycle, idk what thsi is, just random picked one...) succeeded, but now?
What do I have to do now for connecting to the API?
I'm very grateful for eyerone who can help me, I' pretty young and want to learn coding, also crypto interests me, so I want to combine it... Sry if this is a bonehead question :/

Hi @Zynatrixx , to connect to the API you need to use either the REST client or the WebSocket client. The best way to get started is by running the examples in the example folder, and then start adapting that code for your specific needs.


(Ternary-) Bit Vector

We need to have an implementation of fast bit vectors and ternary bit vectors, as they are defined in the paper. This will be one of the core parts of the engines and should therefore be implemented without using a bitvector library (we need to optimize every bit).
In the first step, these bit vectors should support all of the necassery operation to implement inverse semantics for simpler operations like ADDI and MUL.
Implementationwise, I think it would be good to create 2 Types (binary- and ternary bit vectors) and overload operators to fit our semantics (https://doc.rust-lang.org/std/ops/index.html#traits). Besides this basic operators we also have to implement functions like: ctz() or mcb().

@AlexLoitzl is that a good description of what we need? Do you have anything else to add?

This seems very reasonable, although I wouldn't worry about binary vectors in the beginning. This seems like a lot of work, since we need to consider cases where both types of vectors can appear on either side of an operator and the behaviour is different for each of those. We should definetly keep this in mind, but it seems like a lot of work and maybe the payoff is minimal. I'm not sure yet, how often and for how long a binary vector is relevant since I assume as soon as we encounter a ternary vector the output of our calculation will be a ternary vector as well. (Most of the time)

@ChristianMoesl @AlexLoitzl Yes, I'd be careful with optimizations so early. Try to stay close to the logic for now. Correctness and clarity is more important than performance right now. You will first need to understand exactly what you need to support.

@AlexLoitzl Good point, I am totally on your side with that. We should only implement (or overload) those operators, that we actually need and therefore have to implement anyway. But we should do that in a somewhat self-contained way in a bitvector module. Btw. you can overload add for 2 different types.
@ckirsch Sure, we won't optimize at the beginning, but we want to have the potential to optimize and therefore want to have our own implementation (rather using a external library). I wrote that specific line, because @finga had a fancy idea, were he wants to specify a Ternary Bit type and would implement the vector on a bit level, rather than on word level, which in my opinion goes a bit to far.
I mean, it would be fun to implement a full-adder for ternary bit vector's on bit level, but that's hopefully not necassery :)

I fixed the descritpion based on your comments.

The thing is that we don't know yet on which level those operators need to be implemented. Right? Or at least I don't know. I sent an email to Armin to see if we can get their source code.

We don't know, yes. But we can find out as we go.
Anyway it would be good for us to look into Bitwuzla source code. Thanks for that!

#39 adds word level semantics for ternary and binary bit vectors. This is described in their paper about bit vector semantics.


"set" should be declare vars global

It would be fine, if child-templates could pass information to the parent via the "set" method.
Example:
parent.pebble:
##################
Title: {{ title }}
{% block content %}{% endblock %}
##################
child.pebble
##################
{% extends "parent" %}
{% block content %}
{% set title = "My Title" %}
{% endblock %}
##################
Currently, this is not working, or am I wrong?
(I know, this can be partly done by using many different blocks. But passing this via vars is more convenient and more flexible. BTW twig does allow this already:
http://stackoverflow.com/questions/17244162/symfony2-twig-how-can-i-send-parameters-to-the-parent-template
Do you think, this can be implemented?

I'm sorry - it just works. If you move the "{% set title = "My Title" %}" out of the block - then it works !!
##################
{% extends "parent" %}
{% set title = "My Title" %}
{% block content %}
..
{% endblock %}
##################


[BACKLOG-21387] Updating the 'get fields' behavior for Csv Input Step

Build Completed
:x: This pull request has errors. They will need to be addressed before it can be accepted. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -B -fn -f 'pom.xml' -pl 'ui,engine,core' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'ui,engine,core' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  core/src/main/java/org/pentaho/di/core/row/value/ValueMetaBase.java
  core/src/main/resources/org/pentaho/di/i18n/messages/messages_en_US.properties
  engine/src/main/java/org/pentaho/di/trans/steps/textfileinput/TextFileInput.java
  ui/src/main/java/org/pentaho/di/ui/core/dialog/BaseDialog.java
  ui/src/main/java/org/pentaho/di/ui/core/dialog/EnterNumberDialog.java
  ui/src/main/java/org/pentaho/di/ui/core/widget/TableView.java
  ui/src/main/java/org/pentaho/di/ui/trans/step/common/FieldSelectionDialog.java
  ui/src/main/java/org/pentaho/di/ui/trans/step/common/GetFieldsCapableStepDialog.java
  ui/src/main/java/org/pentaho/di/ui/trans/step/common/GetFieldsSampleDataDialog.java
  ui/src/main/java/org/pentaho/di/ui/trans/steps/csvinput/CsvInputDialog.java
  ui/src/main/java/org/pentaho/di/ui/trans/steps/textfileinput/TextFileCSVImportProgressDialog.java

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes (click to expand)
org.pentaho.di.trans.step.StepMeta

Branch Change: -0.7% :small_red_triangle_down:
Complexity Change: -0.6% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:
Line Change: -0.3% :small_red_triangle_down:

org.pentaho.di.trans.steps.dimensionlookup.DimensionLookupMeta

Branch Change: -1.8% :small_red_triangle_down:
Complexity Change: -1.1% :small_red_triangle_down:
Instruction Change: -0.4% :small_red_triangle_down:
Line Change: -0.3% :small_red_triangle_down:

org.pentaho.di.trans.steps.ldifinput.LDIFInputMeta

Branch Change: -1% :small_red_triangle_down:
Complexity Change: -0.7% :small_red_triangle_down:

org.pentaho.di.trans.steps.memgroupby.MemoryGroupByMeta

Branch Change: -2.2% :small_red_triangle_down:
Complexity Change: -2.6% :small_red_triangle_down:

org.pentaho.di.trans.steps.singlethreader.SingleThreaderMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.sort.SortRowsMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.sortedmerge.SortedMergeMeta

Instruction Change: -0.2% :small_red_triangle_down:

org.pentaho.di.trans.steps.uniquerows.UniqueRowsMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.webservices.WebServiceMeta

Branch Change: -1.7% :small_red_triangle_down:
Complexity Change: -1.2% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.ui.repository.pur.repositoryexplorer.model.UISecurityRole

Branch Change: -1.8% :small_red_triangle_down:
Complexity Change: -1.5% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:
Line Change: -0.5% :small_red_triangle_down:

org.pentaho.di.trans.steps.salesforceinsert.SalesforceInsertMeta

Instruction Change: -0.1% :small_red_triangle_down:

:new: org.pentaho.di.ui.core.dialog.BaseDialog

Coverage: 0% :exclamation:

:new: org.pentaho.di.ui.trans.step.common.FieldSelectionDialog

Coverage: 0% :exclamation:

:new: org.pentaho.di.ui.trans.step.common.GetFieldsCapableStepDialog

Coverage: 0% :exclamation:

:new: org.pentaho.di.ui.trans.step.common.GetFieldsSampleDataDialog

Coverage: 0% :exclamation:

Note: The list of offending coverage changes extends beyond the presented results and was truncated to prevent reaching the comment size limit.

Checkstyle violations
The code submitted is not complying with one or more of our guidelines. To perform these checks locally, please use this tool.
/home/buildguy/project/ui/src/main/java/org/pentaho/di/ui/core/dialog/BaseDialog.java

:heavy_exclamation_mark: Unused import - org.eclipse.swt.events.SelectionAdapter. at Line: 26 Column: 8

/home/buildguy/project/ui/src/main/java/org/pentaho/di/ui/trans/step/common/FieldSelectionDialog.java

:heavy_exclamation_mark: 'static' modifier out of order with the JLS suggestions. at Line: 51 Column: 17

/home/buildguy/project/ui/src/main/java/org/pentaho/di/ui/trans/step/common/GetFieldsCapableStepDialog.java

:heavy_exclamation_mark: Unused import - org.pentaho.di.core.exception.KettleException. at Line: 31 Column: 8

/home/buildguy/project/ui/src/main/java/org/pentaho/di/ui/trans/step/common/GetFieldsSampleDataDialog.java

:heavy_exclamation_mark: 'boolean' has incorrect indentation level 2, expected level should be 4. at Line: 49

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -B -fn -f 'pom.xml' -pl 'ui,engine,core' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'ui,engine,core' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  core/src/main/java/org/pentaho/di/core/row/value/ValueMetaBase.java
  core/src/main/resources/org/pentaho/di/i18n/messages/messages_en_US.properties
  engine/src/main/java/org/pentaho/di/trans/steps/textfileinput/TextFileInput.java
  ui/src/main/java/org/pentaho/di/ui/core/dialog/BaseDialog.java
  ui/src/main/java/org/pentaho/di/ui/core/dialog/EnterNumberDialog.java
  ui/src/main/java/org/pentaho/di/ui/core/widget/TableView.java
  ui/src/main/java/org/pentaho/di/ui/trans/step/common/FieldSelectionDialog.java
  ui/src/main/java/org/pentaho/di/ui/trans/step/common/GetFieldsCapableStepDialog.java
  ui/src/main/java/org/pentaho/di/ui/trans/step/common/GetFieldsSampleDataDialog.java
  ui/src/main/java/org/pentaho/di/ui/trans/steps/csvinput/CsvInputDialog.java
  ui/src/main/java/org/pentaho/di/ui/trans/steps/textfileinput/TextFileCSVImportProgressDialog.java

Newly Fixed Tests:
org.pentaho.di.trans.streaming.common.BlockingQueueStreamSourceTest.streamIsPausable:
:large_blue_circle: junit.framework.AssertionFailedError
junit.framework.AssertionFailedError
	at org.pentaho.di.trans.streaming.common.BlockingQueueStreamSourceTest.getQuickly(BlockingQueueStreamSourceTest.java:225)
	at org.pentaho.di.trans.streaming.common.BlockingQueueStreamSourceTest.streamIsPausable(BlockingQueueStreamSourceTest.java:136)

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes.

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -B -fn -f 'pom.xml' -pl 'ui,engine,core' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'ui,engine,core' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  core/src/main/java/org/pentaho/di/core/row/value/ValueMetaBase.java
  core/src/main/resources/org/pentaho/di/i18n/messages/messages_en_US.properties
  engine/src/main/java/org/pentaho/di/trans/steps/textfileinput/TextFileInput.java
  ui/src/main/java/org/pentaho/di/ui/core/dialog/BaseDialog.java
  ui/src/main/java/org/pentaho/di/ui/core/dialog/EnterNumberDialog.java
  ui/src/main/java/org/pentaho/di/ui/core/widget/TableView.java
  ui/src/main/java/org/pentaho/di/ui/trans/step/common/FieldSelectionDialog.java
  ui/src/main/java/org/pentaho/di/ui/trans/step/common/GetFieldsCapableStepDialog.java
  ui/src/main/java/org/pentaho/di/ui/trans/step/common/GetFieldsSampleDataDialog.java
  ui/src/main/java/org/pentaho/di/ui/trans/steps/csvinput/CsvInputDialog.java
  ui/src/main/java/org/pentaho/di/ui/trans/steps/textfileinput/TextFileCSVImportProgressDialog.java

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes (click to expand)
org.pentaho.di.core.injection.bean.BeanInjector

Branch Change: -0.7% :small_red_triangle_down:
Complexity Change: -1.2% :small_red_triangle_down:

org.pentaho.di.trans.step.StepMeta

Branch Change: -0.7% :small_red_triangle_down:
Complexity Change: -0.6% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:
Line Change: -0.3% :small_red_triangle_down:

org.pentaho.di.trans.steps.csvinput.CsvInputMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.dbproc.DBProcMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.groupby.GroupByMeta

Branch Change: -2.1% :small_red_triangle_down:
Complexity Change: -2.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.ifnull.IfNullMeta

Branch Change: -2% :small_red_triangle_down:
Complexity Change: -1.9% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:

org.pentaho.di.trans.steps.memgroupby.MemoryGroupByMeta

Branch Change: -4.4% :small_red_triangle_down:
Complexity Change: -5.2% :small_red_triangle_down:

org.pentaho.di.trans.steps.rowgenerator.RowGeneratorMeta

Branch Change: -2.6% :small_red_triangle_down:
Complexity Change: -1.5% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.setvalueconstant.SetValueConstantMeta

Instruction Change: -0.2% :small_red_triangle_down:

org.pentaho.di.trans.steps.singlethreader.SingleThreaderMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.sortedmerge.SortedMergeMeta

Instruction Change: -0.2% :small_red_triangle_down:

org.pentaho.di.trans.steps.webservices.WebServiceMeta

Branch Change: -1.7% :small_red_triangle_down:
Complexity Change: -1.2% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.salesforceupsert.SalesforceUpsertMeta

Instruction Change: -0.1% :small_red_triangle_down:

:new: org.pentaho.di.ui.core.dialog.BaseDialog

Coverage: 0% :exclamation:

:new: org.pentaho.di.ui.trans.step.common.FieldSelectionDialog

Coverage: 0% :exclamation:

Note: The list of offending coverage changes extends beyond the presented results and was truncated to prevent reaching the comment size limit.

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -B -fn -f 'pom.xml' -pl 'ui,engine,core' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'ui,engine,core' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  core/src/main/java/org/pentaho/di/core/row/value/ValueMetaBase.java
  core/src/main/resources/org/pentaho/di/i18n/messages/messages_en_US.properties
  engine/src/main/java/org/pentaho/di/trans/steps/textfileinput/TextFileInput.java
  engine/src/main/resources/org/pentaho/di/trans/steps/csvinput/messages/messages_en_US.properties
  ui/src/main/java/org/pentaho/di/ui/core/dialog/BaseDialog.java
  ui/src/main/java/org/pentaho/di/ui/core/dialog/BaseMessageDialog.java
  ui/src/main/java/org/pentaho/di/ui/core/dialog/EnterNumberDialog.java
  ui/src/main/java/org/pentaho/di/ui/core/widget/TableView.java
  ui/src/main/java/org/pentaho/di/ui/trans/step/common/CommonStepDialog.java
  ui/src/main/java/org/pentaho/di/ui/trans/step/common/FieldSelectionDialog.java
  ui/src/main/java/org/pentaho/di/ui/trans/step/common/GetFieldsCapableStepDialog.java
  ui/src/main/java/org/pentaho/di/ui/trans/step/common/GetFieldsSampleDataDialog.java
  ui/src/main/java/org/pentaho/di/ui/trans/steps/csvinput/CsvInputDialog.java
  ui/src/main/java/org/pentaho/di/ui/trans/steps/textfileinput/TextFileCSVImportProgressDialog.java

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes (click to expand)
org.pentaho.di.core.injection.bean.BeanInjector

Branch Change: -0.7% :small_red_triangle_down:
Complexity Change: -1.2% :small_red_triangle_down:

org.pentaho.di.job.entries.evaluatetablecontent.JobEntryEvalTableContent

Branch Change: -1.1% :small_red_triangle_down:
Complexity Change: -1.1% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.job.entries.waitforsql.JobEntryWaitForSQL

Branch Change: -0.8% :small_red_triangle_down:
Complexity Change: -1% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.csvinput.CsvInputMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.rowgenerator.RowGeneratorMeta

Branch Change: -2.6% :small_red_triangle_down:
Complexity Change: -1.5% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.sort.SortRowsMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.sortedmerge.SortedMergeMeta

Instruction Change: -0.2% :small_red_triangle_down:

org.pentaho.di.trans.steps.salesforceupdate.SalesforceUpdateMeta

Instruction Change: -0.2% :small_red_triangle_down:

:new: org.pentaho.di.ui.core.dialog.BaseDialog

Coverage: 0% :exclamation:

:new: org.pentaho.di.ui.core.dialog.BaseMessageDialog

Coverage: 0% :exclamation:

:new: org.pentaho.di.ui.trans.step.common.FieldSelectionDialog

Coverage: 0% :exclamation:

:new: org.pentaho.di.ui.trans.step.common.GetFieldsCapableStepDialog

Coverage: 0% :exclamation:

:new: org.pentaho.di.ui.trans.step.common.GetFieldsSampleDataDialog

Coverage: 0% :exclamation:


Improvements to quota doc.

Address review comments in #11487

fixed.

LGTM

NOTE: MERGE THIS AFTER #11487


Add José Antonio Páez University

Hello, i'm sorry for the previous request, i made a mistake commiting every file in the folder, please add my university:
Universidad José Antonio Páez
José Antonio Páez University
Domain: https://ujap.edu.ve/
Have a great day!

@jbustoos22 First stage of verification passed, official domain is ujap.edu.ve as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@jbustoos22 Pull request merged. Thank you!


mnist data download failure

When I use
from tensorflow.examples.tutorials.mnist import input_data
mnist = input_data.read_data_sets("/tmp/mnist/", one_hot = True)
It seems that I cannot download the gz files from the googleapis? Error as below
urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:749)>
Then I manually visit the source site, also error xml replied as below:

AccessDenied
Access denied.

Anonymous caller does not have storage.objects.get access to cvdf-datasets/mnist.

So how can I fix the problem? Thanks a lot.

Please provide details about what platform you are using (operating system, architecture). Also include your TensorFlow version. Also, did you compile from source or install a binary?
Also, can you go through the link1 , link2  and link3 and see if it helps you. Thanks!

Sir     I think it's the problem for China only.  I tried to manually download it by whether and everything went well already.  So you may close the ticket and thank you for your support. Best RegardRoger Yu发自我的华为手机-------- 原始邮件 --------发件人： ravikyram<EMAIL_ADDRESS>2019年12月16日周一 下午2:17收件人： tensorflow/tensorflow<EMAIL_ADDRESS>rogeryuchao<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>  题： Re: [tensorflow/tensorflow] mnist data download failure (#35130)Please provide details about what platform you are using (operating system, architecture). Also include your TensorFlow version. Also, did you compile from source or install a binary?
Also, can you go through the link1 , link2  and link3 and see if it helps you. Thanks!
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.

@rogeryuchao
I am closing the issue   since the query is been resolved. Thanks!


Missing Kethane on 1.0 but not Kerbonite

The Kerbonite mod is suposed to work with Kethane, it appears in 1.0 but Kethane not, when searching for CKAN compatible mods.

We'll be happy to update Kethane once there's a new release. Presently we index Kethane v0.9.2 which is the most recent release. There's a patch available to use Kethane with 1.0.2 but as a general rule CKAN doesn't index patches.

I mean only 1.0.0 girl!

What?

I mean that I play KSP in 1.0.0, and there is no Kethane for 1.0.0, only for 1.0.2 and later. Even then Kerbonite just appears in 1.0.0 CKAN compatibles list, even though the dependency Kethane isn't!

Karbonite does not depend on Kethane. Karbonite is an alternative to Kethane.
http://forum.kerbalspaceprogram.com/threads/89401

Oh thanks. That clarify all.
"So much decision power you have made me decide you're male." - forget that :white_check_mark:

But CKAN says Karbonite depends on Kethane, thus I can't install Karbonite in CKAN!

What version of Karbonite are you trying to install?

But CKAN says Karbonite depends on Kethane, thus I can't install Karbonite in CKAN!
Karbonite 1.0.0.

There is not a single mod in all of CKAN that depends on Kethane. https://github.com/KSP-CKAN/CKAN-meta/search?utf8=✓&q=kethane
AGExt supports Kethane.
Extraplanetary-Launchpads recommends Kethane.
No mod depends Kethane.

In my CKAN Karbonite depends Kethane.

Maybe you have very old metadata? Press refresh, make sure you have the most recent version of CKAN.

Wait, I was saying about KarbonitePlus! And Karbonite don't appear to have an 1.0.0 version, unlike Karbonite.
That confused me until I checked CKAN. I confused Karbonite - KarbonitePlus with Kethane - Karbonite. Wow!

So you're trying to install KarbonitePlus and it's failing to give you Karbonite?

Are you able to install Karbonite on its own?

No, I can't install Karbonite on its own because it won't appear in the compatible mods list. Yes, I am "trying to install KarbonitePlus and it's failing to give [me] Karbonite".

While there was a Karbonite available for 1.0.0, we cannot meet Karbonite's dependency on FirespitterCore because there was no release for 1.0.0. There were only 5 days between the releases of KSP 1.0.0 and 1.0.2 and in that span of time Firespitter did not have a release.
In other words, without a Firespitter, there's no FirespitterCore, which means no Karbonite, which means no KarbonitePlus.
For the release list for Firespitter see: https://github.com/snjo/Firespitter/releases

I can make the 1.0.0 version, I am downloading the source code. It is my first time I mess with CKAN files and such, but believe me. I'll do a pull request when I compatibilize it!

Closing this, as it's not a CKAN issue. We'll index the Firespitter release once it's on https://github.com/snjo/Firespitter/releases

The project is in https://github.com/Gustavo6046/FireSpitter-1.0.0/tree/master anyone contributing to it. We will later do a pull request to the original Firespitter.

A few things.  First - I will absolutely not take a pull request for FireSpitter to go back to 1.0.0.  Second, you're in violation of the FireSpitter license - so to CKAN folks, please be aware that any attempt by Gustavo6046 to add FireSpitter stuff to CKAN is unauthorized.  Third.  There is no Karbonite release for 1.0.0 - again, any attempt to CKAN this is just muddying the waters - Karbonite is a 1.0.2+ mod (soon to be 1.0.4).  Lastly.  Karbonite has as much to do with Kethane as Ham does with Hamsters.

@BobPalmer: Don't worry, we CKAN people are sensible. @Gustavo6046 is either a troll or very odd/misinformed and nothing he says is regarded with any degree of seriousness.
When I saw https://github.com/snjo/Firespitter/pull/122 I had a chuckle, knowing it would (and should) be closed. His OP in https://github.com/KSP-CKAN/CKAN/issues/1314 was also particularly weird/funny.

Well you admited the reason and the fault, "nothing [me] says is regarded with any degree of seriousness by the CKAN team." I just wish to play KerbonitePlus in 1.0.0 since it seems K+ is for some reason avaiable in 1.0.0. Whatever, I am misinformed either, I am a bit lazy to check in the forums (that's why I use CKAN ;) ) so let's not feel much. I can live without it.
Know that LPIP? I could carry a entire plugin with only a single .lpf file! I only needed LPIP to install the file into the gamedata. And the file was keeped, so that I could install twice, and carry it without needing temporary copies or multiple downloads!


raftstore: refine raft log gc tick.

Signed-off-by: MrCroxx<EMAIL_ADDRESS>
What problem does this PR solve?
Problem Summary:
Previously (before tikv#8668), trigger gc will force WAL sync in apply thread, and use skip_gc_raft_log_ticks to reduce syncing. After tikv#8668, syncing is moved to background worker thread, and CompactLog cmds are batched. So there is no need to use skip_gc_raft_log_ticks anymore.
What is changed and how it works?
What's Changed:
Remove skip_gc_raft_log_ticks and related codes.
Tests

Unit test
Integration test

Side effects
Release note
Config `raftstore.raft-log-reserve-max-ticks` is discarded.
`raftstore.raft-log-gc-tick-interval` default value is replaced with an optimized value (10s => 1s).

/cc @hicqu @Little-Wallace @gengliqi PTAL if removing it is okay.

@Little-Wallace @gengliqi PTAL.

/release

/release

Benchmark on benchbot:
new config:
[Summary] DELIVERY - Takes(s): 1798.8, Count: 134948, TPM: 4501.2, Sum(ms): 66074225.0, Avg(ms): 490.0, 50th(ms): 503.3, 90th(ms): 604.0, 95th(ms): 637.5, 99th(ms): 838.9, 99.9th(ms): 1073.7, Max(ms): 1677.7
[Summary] DELIVERY_ERR - Takes(s): 1798.8, Count: 17, TPM: 0.6, Sum(ms): 2862.3, Avg(ms): 168.3, 50th(ms): 218.1, 90th(ms): 251.7, 95th(ms): 260.0, 99th(ms): 260.0, 99.9th(ms): 260.0, Max(ms): 260.0
[Summary] NEW_ORDER - Takes(s): 1799.3, Count: 1520622, TPM: 50706.0, Sum(ms): 218444877.1, Avg(ms): 143.7, 50th(ms): 142.6, 90th(ms): 209.7, 95th(ms): 226.5, 99th(ms): 285.2, 99.9th(ms): 352.3, Max(ms): 637.5
[Summary] NEW_ORDER_ERR - Takes(s): 1799.3, Count: 54, TPM: 1.8, Sum(ms): 2270.4, Avg(ms): 41.8, 50th(ms): 30.4, 90th(ms): 75.5, 95th(ms): 151.0, 99th(ms): 151.0, 99.9th(ms): 151.0, Max(ms): 151.0
[Summary] ORDER_STATUS - Takes(s): 1799.4, Count: 134509, TPM: 4485.2, Sum(ms): 7606000.0, Avg(ms): 56.6, 50th(ms): 50.3, 90th(ms): 100.7, 95th(ms): 121.6, 99th(ms): 159.4, 99.9th(ms): 192.9, Max(ms): 604.0
[Summary] PAYMENT - Takes(s): 1799.3, Count: 1450959, TPM: 48383.5, Sum(ms): 160504927.0, Avg(ms): 110.7, 50th(ms): 104.9, 90th(ms): 167.8, 95th(ms): 184.5, 99th(ms): 251.7, 99.9th(ms): 352.3, Max(ms): 771.8
[Summary] PAYMENT_ERR - Takes(s): 1799.3, Count: 21, TPM: 0.7, Sum(ms): 600.0, Avg(ms): 28.5, 50th(ms): 23.1, 90th(ms): 50.3, 95th(ms): 52.4, 99th(ms): 151.0, 99.9th(ms): 151.0, Max(ms): 151.0
[Summary] STOCK_LEVEL - Takes(s): 1799.4, Count: 135268, TPM: 4510.4, Sum(ms): 7330436.8, Avg(ms): 54.2, 50th(ms): 50.3, 90th(ms): 88.1, 95th(ms): 104.9, 99th(ms): 142.6, 99.9th(ms): 184.5, Max(ms): 570.4
tpmC: 50706.0, efficiency: 394.3%

old config:
[Summary] DELIVERY - Takes(s): 1798.7, Count: 138259, TPM: 4611.9, Sum(ms): 70895513.2, Avg(ms): 513.2, 50th(ms): 520.1, 90th(ms): 604.0, 95th(ms): 637.5, 99th(ms): 872.4, 99.9th(ms): 1140.9, Max(ms): 2013.3
[Summary] DELIVERY_ERR - Takes(s): 1798.7, Count: 22, TPM: 0.7, Sum(ms): 4455.0, Avg(ms): 202.4, 50th(ms): 201.3, 90th(ms): 352.3, 95th(ms): 402.7, 99th(ms): 436.2, 99.9th(ms): 436.2, Max(ms): 436.2
[Summary] NEW_ORDER - Takes(s): 1799.2, Count: 1557120, TPM: 51927.4, Sum(ms): 218714035.3, Avg(ms): 140.5, 50th(ms): 134.2, 90th(ms): 201.3, 95th(ms): 218.1, 99th(ms): 260.0, 99.9th(ms): 335.5, Max(ms): 2684.4
[Summary] NEW_ORDER_ERR - Takes(s): 1799.2, Count: 92, TPM: 3.1, Sum(ms): 8041.9, Avg(ms): 87.5, 50th(ms): 83.9, 90th(ms): 117.4, 95th(ms): 121.6, 99th(ms): 201.3, 99.9th(ms): 201.3, Max(ms): 201.3
[Summary] ORDER_STATUS - Takes(s): 1799.2, Count: 138323, TPM: 4612.7, Sum(ms): 7557162.9, Avg(ms): 54.7, 50th(ms): 50.3, 90th(ms): 92.3, 95th(ms): 113.2, 99th(ms): 142.6, 99.9th(ms): 167.8, Max(ms): 335.5
[Summary] ORDER_STATUS_ERR - Takes(s): 1799.2, Count: 2, TPM: 0.1, Sum(ms): 112.4, Avg(ms): 56.1, 50th(ms): 44.0, 90th(ms): 71.3, 95th(ms): 71.3, 99th(ms): 71.3, 99.9th(ms): 71.3, Max(ms): 71.3
[Summary] PAYMENT - Takes(s): 1799.2, Count: 1485836, TPM: 49550.5, Sum(ms): 155152651.5, Avg(ms): 104.5, 50th(ms): 96.5, 90th(ms): 159.4, 95th(ms): 176.2, 99th(ms): 234.9, 99.9th(ms): 318.8, Max(ms): 2080.4
[Summary] PAYMENT_ERR - Takes(s): 1799.2, Count: 34, TPM: 1.1, Sum(ms): 2279.8, Avg(ms): 66.8, 50th(ms): 62.9, 90th(ms): 92.3, 95th(ms): 151.0, 99th(ms): 201.3, 99.9th(ms): 201.3, Max(ms): 201.3
[Summary] STOCK_LEVEL - Takes(s): 1799.2, Count: 138718, TPM: 4625.9, Sum(ms): 7624353.3, Avg(ms): 55.0, 50th(ms): 50.3, 90th(ms): 88.1, 95th(ms): 104.9, 99th(ms): 142.6, 99.9th(ms): 167.8, Max(ms): 385.9
tpmC: 51927.4, efficiency: 403.8%

According to former benchmark. use raft-log-gc-tick-interval=1s can reduce 18%~38% raftdb write bandwidth (compared with 10s).

@MrCroxx What's the configuration for the result you pasted? Is the CPU utilization high enough to demonstrate the negative effect?

What's the configuration for the result you pasted? Is the CPU utilization high enough to demonstrate the negative effect?

@tabokie  Both configuration are default for each branch. In all of the previous benchmarks, the increasement (from 4% to 8%) of CPU utilization is not that high to affect the result a lot.

@MrCroxx I am referring to the benchmark configuration, and tikv-server cpu utilization. When tikv has throttled the server, 8% difference could mean a lot.

@MrCroxx I am referring to the benchmark configuration, and tikv-server cpu utilization. When tikv has throttled the server, 4% difference could mean a lot.

@tabokie The workload is tpcc1000. Unfortunately the metrics are pruged by the benchbot, so I cannot give the exact CPU utilization of tikv-server. But those of pervious benchmark jobs are at 75%~85%.

@MrCroxx Can you paste the workload, threads count, and topology(1kv) besides the benchmark result above? And I think you should also run tpcc and sysbench with 800 threads, this time keep an eye on the grafana panel.

What's the current blocker of this one?

@MrCroxx Any progress running some benchmarks with high thread count? You can still use benchbot, it opens Grafana portal during the test.

@tabokie @yiwu-arbug I want to delay the raft log gc tick optimization after RaftEngine GA. Now there is still an underlying tick batching, which is good for Rocksdb but I don't think RaftEngine needs it. I think maybe refine the tick and batch logic after RaftEngine GA is better.

@tabokie @yiwu-arbug I want to delay the raft log gc tick optimization after RaftEngine GA. Now there is still an underlying tick batching, which is good for Rocksdb but I don't think RaftEngine needs it. I think maybe refine the tick and batch logic after RaftEngine GA is better.

@MrCroxx RaftEngine has a long way before GA. Meanwhile we will need the raftlog GC tick change as and intermediate optimization.

/release

/rebuild

/release

/release

/release

/release

/rebuild

/release

/merge

/merge


Raw byte size limit when visualize

Set a limit when visualizing the raw bytes so large file doesn't get visualized

Set a threshold instance wide
Backend endpoint to provide bytes to frontend

If there is vis config, provide from visualization bytes
If there isn't provide the raw bytes
The cutoff can be handled by this endpoint.
The endpoint can give messages indicate that threshold is over

@tcnichol , @ddey2 is going to take a look at this one.


[Enhancement]: Azure pre-created RG scoped role

Version
cndi v1.13.4
kubeseal v0.21.0
terraform v1.5.5
Please provide a summary of the enhancement you are proposing:
It should be possible to tell CNDI that we will bring our own resource group instead of one being provisioned automatically. This enables creating better app registration service accounts which are limited to only one resource group.
Please provide the motivation or use case for this enhancement:
When CNDI provisions a resource group, it must inherently give access to all other resource groups. There is no way to limit a Service Account to only working within a given RG unless the RG is created first by hand.
How can we best workaround this issue so far?
Currently users should limit the blast radius of an app registration by creating a new domain-aligned Azure Subscription.
With RG level permissions, CNDI clusters and their Service Accounts could be deployed safely in the same subscription as other private resources.
How would you approach solving this problem within CNDI?
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

we should also explore the option of allowing multiple CNDI clusters per resource group by leveraging prefixes to avoid collisions


Made PythonVariable class public

I have an application that makes extensive use of PythonAst to create auto-completion lists. It would be very beneficial to have IronPython.Compiler.Ast.PythonVariable class as public, otherwise it is troublesome parsing AST structure.

This was already incorporated in your other PR (https://github.com/IronLanguages/ironpython2/pull/573)


HuggingFace Inference API cutting responses short

There seems to be an issue running the model on huggingface (https://huggingface.co/Norm/nougat-latex-base), as responses seem to be cut short. Take for example this image:

The output is:
\mathrm{{QFT}}:|x\rangle\mapsto{\frac
I'm not sure if this is a temporary HF issue, or has the model been updated recently?

@lucasvanmol I didn't update the model recently. Could you downgrade to transformers==4.34.0 and try again? It's odd because I trained the model with a max sequence length of 800. You can check the config file here. And I just ran the example in my environment (transformers==4.34.0 ), the output looks good:
\\mathrm{QFT}:|x\\rangle\\mapsto\\frac{1}{\\sqrt{N}}\\sum_{k=0}^{N-1}\\omega_{N}^{x k}|k\\rangle.

It is probably an HF issue?

Yeah, running the model myself it seems perfectly fine. It's just the HF API that's causing trouble, but I'm not sure what the cause is, as it wasn't happening a few days ago.

@lucasvanmol Yeah, I reproduced the bug. Several examples I tested successfully now returned a short result as well.  This is highly an hf issue.

I seem to have found a solution to this issue, but I'm still a bit baffled why this is suddenly needed. Adding in an extra max_new_tokens parameter gives the desired result:
import requests
import base64

API_URL = "https://api-inference.huggingface.co/models/Norm/nougat-latex-base"
headers = {"Authorization": f"Bearer {API_TOKEN}"}

def query(q):
    response = requests.request("POST", API_URL, headers=headers, json=q)
    return response.json()

image = open("test.png", "rb")
image_b64 = base64.b64encode(image.read())
data = query({"inputs" : image_b64.decode("utf-8") , "parameters" : {"max_new_tokens" : 800}})
print(data)
image.close()

I think you might be able to include this parameter in the inference widget by adding something like this to the model card in HF:
inference:
  parameters:
    max_new_tokens: 800

see https://huggingface.co/docs/hub/models-widgets#how-can-i-control-my-models-widget-inference-api-parameters

@lucasvanmol I tried to add the parameters into the widget meta config, but it still fails to work.

Seems that all other checkpoints, including facebook/nougat-base, are having the same problem

I have finetuned on my custom dataset for handwritten equations. After downloading the weights .pth file and using it on colab directly it shows the following errors:
Repository Not Found for url: https://huggingface.co/try.pth/resolve/main/config.json.
Please make sure you specified the correct repo_id and repo_type.
If you are trying to access a private or gated repo, make sure you are authenticated.
Invalid username or password.
OSError: try.pth is not a local folder and is not a valid model identifier listed on 'https://huggingface.co/models'
If this is a private repository, make sure to pass a token having permission to this repo either by logging in with huggingface-cli login or by passing token=<your_token>
Can someblody please help how to use the new model weights for inference

@Shobhit1201
Please check this thread.

thank you, it helps in inference. But if i need to use these weights for further training, what should i do?

@Shobhit1201 The codebase supports further training from a certain checkpoint. Please check the codes here
To utilize this feature, you need to specify the absolute path to the checkpoint in config.yaml file, which can be found here

@NormXU this worked, thank you!!
Now if i want to evaluate on my test set, and calculate token_acc and edit_dist, is there script for that as well?

@Shobhit1201 Yes, there is. Check this. The eval func is used to calculate token_acc and edit_dis

@lucasvanmol Thanks for that suggestion! The max_new_tokens parameter worked for me. I was able to retrieve a longer response.
Context:
Previously I was using: max_tokens: 1000 which gave a truncated response. I replaced that with max_new_tokens: 1000 and it gave a better result.

Two new errors coming now,
Error 1: while installing the requirements:
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
accelerate 0.34.2 requires huggingface-hub>=0.21.0, but you have huggingface-hub 0.17.0 which is incompatible.
Error 2: from huggingface_hub import split_torch_state_dict_into_shards
ImportError: cannot import name 'split_torch_state_dict_into_shards' from 'huggingface_hub' .

@Shobhit1201 You can try to run
pip install --upgrade huggingface-hub

hey it was having dependency issue with the older version of transformers specified in the requirements file, so i upgraded both and it worked fine.

Hey,
i used the inference script:
model_name = "Norm/nougat-latex-base"
checkpoint_path = "/content/drive/MyDrive/nougat-base_epoch97_step18000_lr3.805302e-08_avg_loss0.01257_token_acc0.11251_edit_dis0.38271.pth"  # this is your fine-tuned checkpoint
device = "cuda" if torch.cuda.is_available() else "CPU"
Initialize the model
model = VisionEncoderDecoderModel.from_pretrained(model_name).to(device)
load the model weight
state_dict = torch.load(checkpoint_path, map_location=torch.device("cpu"))
model.load_state_dict(state_dict, strict=True)
output:
then this:
!python /content/nougat-latex-ocr/examples/run_latex_ocr.py --img_path "/content/1.png"
but getting the following error: from nougat_latex.util import process_raw_latex_code
ModuleNotFoundError: No module named 'nougat_latex'
I have encountered the same error eralier also. Please help @NormXU

@Shobhit1201

ModuleNotFoundError: No module named 'nougat_latex'

The nougat_latex module is here
You need to download the source code first, or, if you prefer not to download the entire codebase, you can copy and paste the nougat_latex module.

hey @NormXU, I finetuned it on my custom dataset of mathematical equations but the model doesn't seen to improve even after increasing the resolution. What can I do to improve the performace on my dataset?
Is there any way to make changes in the model architecture?

I believe changing the model architecture should typically be the last action to take. First, I'd recommend examining your dataset—specifically, the height-to-width ratio distribution and the range of widths in the equation image clips. Next, consider adjusting the padding to better align with this distribution. Hope this helps!

I have a very varied set of equations like (736 * 63), (652 * 679), (1104 * 96), (984 * 964), (1256 * 328)...
Width Range: Min = 159, Max = 1562
Height Range: Min = 24, Max = 1168
Mean Width: 781.24, Mean Height: 320.87
Median Width: 758.0, Median Height: 295.0
What can i do. and what part of the code should i look at?

@Shobhit1201 You can adjust the image preprocessing to ensure the training images are not rescale too much and keep the input images as close to their native resolutions as possible. Code here.

i want to train for these types of images, but unable to do even after adjusting the resolution. Can you please suggest some changes.

@NormXU understood. But i am new to this therefore i am unable to understand how to train/finetune the original model. i tried to use the original model checkpoints in your version to finetune but it gives some error that weights are missing or unexpected but for inference it works fine. Could be please help how should i move forward.

@Shobhit1201 Could you please open a new issue? I'm happy to help, but your problem is unrelated to this one.


feature/CEL filter implementation

In addition to PR #23 I have implemented a filter function for resources with the cel-go library. It can be used to built dynamic filter expressions over all available columns.
Example:
--filter '(Name == "SomeName" || matches(Name, "RegExpr")) && URI.startsWith("https://auth.")'
For the references to Password and Description, I have use function references. This guarantees, that the overhead with separated queries to the server will execute only when needed. I have also tested that if the reference is used multiple times, the execution only happens once.
When you think this is fine, I can implement this solution for other commands too.

Hi @speatzle
I outsourced the code of filtering in a separate file. And you're right. I don't know what my mistakes were, but in my first tests, the generation of a timestamp didn't work. So I implemented this overloading function. After reading the CEL specs and trying again, the built-in function timestamp(string) worked fine. I've written a second example in the argument description for this.

Hi @speatzle
I've implemented the filter tag in the other sub-commands too. Please check and review the changes. I think now we have a usable functionality.


feat(p2p): remove redundant checks on sending methods

Closes #3511.

PR checklist

[x] Tests written/updated
[ ] Changelog entry added in .changelog (we use unclog to manage our changelog)
[ ] Updated relevant documentation (docs/ or spec/) and code comments
[x] Title follows the Conventional Commits spec

Changed the destination branch to prevent lint errors. It should be updated to main once https://github.com/cometbft/cometbft/pull/3510 is merged.

(Seemed like they both should be handled at different layers of abstraction, e.g. not gossiping if the peer doesn't have a channel)

Yes, after https://github.com/cometbft/cometbft/pull/3512 we have this API method, so the sender can check this condition before using send methods.


🐛[firebase_core] iOS could not build module 'firebase_core' on Flutter 2.8, FirebaseCore 1.10.5

Bug report
Describe the bug
After upgrading to Flutter 2.8 xCode build failing.
GeneratedPluginRegistrant.m:12:9: fatal error: module 'firebase_core' not found
@import firebase_core;
~^~~~~~~
1 error generated.
Flutter doctor
Run flutter doctor and paste the output below:
Click To Expand
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 2.8.0, on macOS 12.0.1 21A559 darwin-arm,
locale hu-HU)
[✓] Android toolchain - develop for Android devices (Android SDK version
31.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 13.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2020.3)
[✓] VS Code (version 1.63.0)
[✓] Connected device (2 available)
• No issues found!

Flutter dependencies
Run flutter pub deps -- --style=compact and paste the output below:
Click To Expand
get: ^4.1.4
intl: ^0.17.0
easy_localization: ^3.0.0
http: ^0.13.3
uuid: ^3.0.4
intl_phone_field: ^2.1.0
flutter_local_notifications: ^9.0.2
flutter_rating_bar: ^4.0.0
flutter_spinkit: ^5.1.0
geolocator: ^8.0.0
webview_flutter: ^3.0.0
url_launcher: ^6.0.9
share_plus: ^3.0.4
flutter_advanced_segment: ^2.0.1+2
font_awesome_flutter: ^9.1.0
expandable: ^5.0.1
flutter_switch: ^0.3.2
image_picker: ^0.8.4+4
image_crop: ^0.4.0
flutter_native_image: ^0.0.6
qr_code_scanner: ^0.6.1
firebase_core: ^1.10.5
firebase_messaging: ^11.2.3
google_sign_in: ^5.0.4
sign_in_with_apple: ^3.1.0

@palvajk
I tried the official plugin example on latest stable and it compiled and built properly without any issues.
Running "flutter pub get" in firebase_core_example...
Launching lib/main.dart on iPhone 12 Pro Max in debug mode...
Running pod install...
Running Xcode build...
Xcode build done.                                           26.5s
Debug service listening on ws://<IP_ADDRESS>:53952/ybMtCv-hZkI=/ws
Syncing files to device iPhone 12 Pro Max...

Can you try this solution and see if it works for you ?

@darshankawar
I tried you linked solution but it didn't help, but i created a new project with firebase_core and it worked fine. I don't understand why my older project doesn't work. I perform all cache clean, deleted the Pods library, reinstalled pods and still the same error.

On what platform are you trying to run? I have problems compiling and running my Flutter app on MacOS.

@a-v-ebrahimi I use macOS too.

Having the same problem. @palvajk Are you also using a Mac with M1?

@masewo
I use M1 Mac as well. But if i create a new project and add firebase_core, its build fine.

@palvajk Same here. I looked for overlaps in our pubspecs. Try adding google_sign_in to the new project. Then it starts not being able to build anymore.

@masewo
I will try to add google_sign_in to the new project. My error is not the same like the other issue, but we will see. I stay the 2.5.3 until the issue resolve

Same here:
/ios/Runner/GeneratedPluginRegistrant.m:12:9: Module 'connectivity_plus' not found

.

UPDATE
#https://github.com/flutter/flutter/issues/94914#issuecomment-992239759
This comment helped me! The error was gone, but I need to remove sign_in_with_google temporarily.

@palvajk
Based on the thread above, it seems the issue is related to google_sign_in plugin and not with firebase_core, so I suggest you to file related plugin issue in flutter/flutter repo. Since your issue is resolved based on above comment, I"ll close it. If you disagree, write in comments and I'll reopen.