feat(config): add rocksdb.nocompression_for_first_levels to allow configure levels without compression

references: https://github.com/apache/kvrocks/issues/2602
add rocksdb.nocompression_for_first_levels to allow configure levels without compression

From the CI log, we need to add vector.reserve() before the loop containing vector.push_back().

@PragmaTwice what do you think about rename nocompression_for_first_n_levels  -> start_compression_level?

Perhaps, if you're a heavy write system, maybe you can enable different compression in different level, like lz4 in low level and zstd in high level...

maybe we could specific compression setting by level? user could mark l0/l1 as snappy or lz4 compression style
l0/l1 nocompression is common type of usage,  use or not,
rocksdb.nocompression_for_first_n_levels  indicate user could make l2/l3... no compression, user may not know about rocksdb stuff, make them confused about what senerio to use it
instead, let user specifc what compression style level used, maybe more clear.

So AFAIK, just like #2607 . You'd like to enable compression on L1 ( or even L0 ) for write intensive case?

yes, write 128on disk is better, then write uncompressed 1gb on disk. Now cpu usage is only 1/8 cores. so i need able to load cpu and decrease disk usage.
it is not general case, but in my case it will help me to use disks with fewer throughput and and as a consequence of ec2 limitations - cheaper ec2 instance

maybe we could specific compression setting by level? user could mark l0/l1 as snappy or lz4 compression style

I think this is a good point
Something similar to the more advanced settings in kvrocks. By default, the "compression" settings are used, but if the new setting "compression_by_levels" is specified, it takes precedence, and the "compression" setting is ignored.

Maybe we should first check this in, would you mind fix the comments firstly?

@PragmaTwice what do you think about rename nocompression_for_first_n_levels -> start_compression_level?

Seems compression_start_level or compression_begin_level is better.

@PragmaTwice what do you think about rename nocompression_for_first_n_levels -> start_compression_level?

Nice. But seems compression_start_level or compression_begin_level is better to me.

renamed


Allow post-rollout-tasks on containers without bash.

Currently, exec-post-rollout-tasks-run.sh assumes bash is available in the service container.
https://github.com/amazeeio/lagoon/blob/master/images/oc-build-deploy-dind/scripts/exec-post-rollout-tasks-run.sh#L3
And for example it's not available by default in the redis container - docker run amazeeio/redis bash
Perhaps we could add another option to allow sh but default to using bash.

this has been implemented


Not Responsive

Pages are not responsive to the size of window.

Can you make all pages responsive?

yes i will make it


User defined physical petsc preconditioner

Hi all,
For now if I want to define a user defined physical PETSc preconditioner for nonlinear problem, I need to define an Operator which implements Mult() to compute residual and GetGradient() to compute jacobian at each Newton iteration. Why cannot we construct a preconditioner at the same time?
In addition, if I want to construct a preconditioner for solving linear system at each Newton iteration, I need define a PetscPreconditionerFactory.
In fact you can construct a preconditioner when establishing jacobian (i.e., GetGradient()) at the same time with
SNESSetJacobian(snes, NULL, NULL, __mfem_snes_jacobian, (void *)snes_ctx)

But I have checked function __mfem_snes_jacobian() in which you are only able to set jacobian with
mfem::Operator& J = snes_ctx->op->GetGradient(*xx)
So I think that it will be better for an Operator to implement Mult(), GetGradient() and something like GetPreconditioiner() at the same time. Now you can define a newton_solver and preconditioner at the same time like below
        newton_solver = new PetscNonlinearSolver(h1_space->GetComm(), *op, "newton_");
        // newton_solver->SetPreconditionerFactory(jac_factory); // you dont need this anymore !!!

Do you think this is a good idea?
Thanks in advance.

Thanks @stefanhenneking
I got it.


⚠ Bofrost.be has degraded performance

In 8d0ec76, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1098 ms

Resolved: Bofrost.be performance has improved in d0041f7 after 9 minutes.


merge package from arlac77/npm-package-template

package.json

chore(package<EMAIL_ADDRESS>

Codecov Report

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

@@          Coverage Diff          @@
##           master   #348   +/-   ##
=====================================
  Coverage      75%    75%
=====================================
  Files           1      1
  Lines           8      8
=====================================
  Hits            6      6
  Misses          2      2

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6f9a816...5136e2a. Read the comment docs.

Coverage remained the same at 70.0% when pulling 5136e2aca16fc228879358576d16314ea3784583 on template-sync-1 into 6f9a8163c51b2aafb29f498082baae8747a18c28 on master.


replace /usr/bin/terraform? [y]es, [n]o, [A]ll, [N]one, [r]ename:  NULL

Describe the bug
this action seems to fail deleting terraform binary
To Reproduce
githubactions
      - name: Pre-commit Terraform
        uses<EMAIL_ADDRESS>        with:
          terraform-version: "1.3.6"
          terraform-docs-version: ${{ env.TERRAFORM_DOCS_VERSION }}
          tflint-version: ${{ env.TFLINT_VERSION }}

Expected behavior
for the install to work from a temp folder
Screenshots

Desktop (please complete the following information):

OS: ubuntu 20

Additional context
githubactions

is this still an issue?

closing for now


Namespaces - probably a question, not an issue

I'm trying to generate the html forms for a schema that has another namespace used for elements under appinfo, but I keep getting errors that I can't resolve.  To demonstrate, based on your double import example, I've added a new namespace and some elements in appinfo.
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:lx="https://github.com/MichielCM/xsd2html2xml/definition" xmlns="https://github.com/MichielCM/xsd2html2xml/doubleImport" targetNamespace="https://github.com/MichielCM/xsd2html2xml/doubleImport" elementFormDefault="qualified">
	<xs:simpleType name="doubleImportedType">
		<xs:restriction base="xs:string">
			<xs:pattern value="(TRUE|FALSE)"/>
		</xs:restriction>
	</xs:simpleType>
	<xs:element name="doubleImportedElement" type="xs:boolean">
			<xs:annotation>
			<xs:documentation>Yes No Option</xs:documentation>
			<xs:appinfo>
				<lx:mapping>xyz</lx:mapping>
				<lx:instructions>YesNo</lx:instructions>
			</xs:appinfo>
		</xs:annotation></xs:element>
</xs:schema>

Do I need to configure something with respect to the namespace to get this to work? I note that the windows app loads this successfully.
I currently get an error:
xsl:attribute: The QName 'data-appinfo-lx:mapping' has no namespace binding in scope in the stylesheet; this is an error, since the namespace was not specified by the instruction itself.
Thanks & Cheers,
Shane

Hi Shane, that's an error on my part. App-info elements are added to HTML tags as attributes. But that code doesn't take into account prefixes. I'll have a look.
The Windows application currently runs on version 2.x, which didn't have this feature.

Hi Shane, the latest commit should fix it.

Thanks Michiel, that’s great thanks. I’ve tested it on our schema and it looks good. Cheers, Shane


Add support for selecting fields

Problem
A crucial part of modern and performant ORMs is the ability to choose what fields are returned, Prisma Client Python is currently missing this feature.
Mypy solution
As we have a mypy plugin we can dynamically modify types on the fly, this means we would be able to make use of a more ergonomic solution.
class Model(BaseModel):
  id: str
  name: str
  points: Optional[int]

class SelectedModel(BaseModel):
  id: Optional[str]
  name: Optional[str]
  points: Optional[int]

ModelSelect = Iterable[Literal['id', 'name', 'points']]

@overload
def action(
	...
) -> Model:
	...

@overload
def action(
	...
	select: ModelSelect
) -> SelectedModel:
	...

model = action(select={'id', 'name'})

The mypy plugin would then dynamically remove the Optional from the model for every field that is selected, we might also be able to remove the fields that aren't selected although I don't know if this is possible.
The downside to a solution like this is that unreachable code will not trigger an error when type checking with a type checker other than mypy, e.g.
user = await client.user.find_first(select={'name'})
if user.id is not None:
  print(user.id)

Will pass type checks although the if block will never be ran.
EDIT: A potential solution for the above would be to not use optional and instead use our own custom type, e.g. maybe something like PrismaMaybeUnset. This has its own downsides though.
EDIT: I also think we may also want to support setting a "default include" value so that relations will always be fetched unless explicitly given False. This will not change the generated types and they will still be Optional[T].
Type checker agnostic solution
After #59 is implemented the query builder should only select the fields that are present on the given BaseModel.
This would mean that users could generate partial types and then easily use them to select certain fields.
User.create_partial('UserOnlyName', include={'name'})

from prisma.partials import UserOnlyName

user = await UserOnlyName.prisma().find_unique(where={'id': 'abc'})

Or create models by themselves
class User(BaseUser):
  name: str

user = await User.prisma().find_unique(where={'id': 'abc'})

This will make typing generic functions to process models more difficult, for example, the following function would not accept custom models.:
def process_user(user: User) -> None:
  ...

It could however be modified to accept objects with the correct properties by using a Protocol.
class UserWithID(Protocol):
  id: str

def process_user(user: UserWithID):
  ...

An interesting potential solution can be found here: https://gist.github.com/RobertCraigie/1b6a8a54f0da65f8006558918ff83e9a

Selecting fields  is really helpful, hope this feature will be implemented soon, thank you.

Is model field selection available ?

@lekhnath Yes the solution mentioned in the "Type checker agnostic" section has been implemented, see these docs for more information: https://prisma-client-py.readthedocs.io/en/stable/reference/selecting-fields/


Enhancement Suggestion for HTTP Helper

In the past few days, I used given http example and it worked pretty well. However, I think that existing functions do not meet all of my requirements.
First, sometimes I do not need validation of response body. For instance, I would like to deploy a template web application, but I am not aware of the whole body of this web app. As a result, I only care about whether I can get an http response successfully, instead of checking contents.
Second, in some cases, I would like to validate specific parts of response body, not the whole content. For example, I want to launch a Ubuntu Linux server and run commands to install nginx. This process can be done using checkSshCommandE. Next, after I open port 80 to allow http request, I would like to send an http request to see whether the response body contains the word "nginx". In this circumstance, the body is really long and even varies among different versions. By contrast, I can make sure that the content contains "nginx". So my requirement here is just to check a substring.
In above cases, I have to write my own test code using retry.DoWithRetry, HttpGet, etc. I wonder whether these enhancement suggestions are really worthwhile. If needed, I can add some features and make pull requests. Thanks a lot!

Did you look at HttpGetWithCustomValidation and HttpGetWithRetryWithCustomValidation?

OK I will try to write my own validation response function and run the test. Thanks for instruction.

OK, great!

This is how I got it to work in case anyone wants to see an example.
https://github.com/mingfang/terraform-provider-k8s/blob/master/test/modules/prometheus/basic_test.go
It's very basic but unfortunately I'll have to cut and paste this code to every test.
Hopefully terratest will natively support this validation soon.


EventGridTrigger batching not working

I'm currently unable to get EventGridTrigger to work with batches.
My function uses .NET 5.0 dotnet-isolated runtime with the following trigger:
public async Task Run([EventGridTrigger] EventGridTriggerData eventGridEvent, FunctionContext context)

I've tried using
[EventGridTrigger] EventGridTriggerData[] eventGridEvents

but that just crashes the function.
EventGridTriggerData is
public class EventGridTriggerData
{
    public string Id { get; set; }
    public string Topic { get; set; }
    public string Subject { get; set; }
    public string EventType { get; set; }
    public DateTime EventTime { get; set; }
    public IDictionary<string, object> Data { get; set; }
}

I've set up the Event subscription on my Azure BLOB storage account and enabled batching, however my code is triggered once per each BLOB that lands in the container I'm subscribed to (Subscription is only for "Blob Created" event and created with EventGridSchema schema).

Any advice here?

@nixa333 we'll need to investigate this before we can provide any guidance, but it does seem to be a defect if this is happening as described. We'll work on setting up a repro, but if you have one built, that would help ensure we're validating the same flow.
Can you also share the version of the Event Grid package you're using?

@fabiocav the code is actually as simple as what I've attached in the original post. Plain .NET 5.0 function with EvebtGridTrigger does not work.
[Function("Function")]
public async Task Run([EventGridTrigger] EventGridTriggerData eventGridEvent, FunctionContext context)

Here's a screenshot of all nugets with versions

And important part of the .csproj
<PropertyGroup>
	<TargetFramework>net5.0</TargetFramework>
	<AzureFunctionsVersion>v3</AzureFunctionsVersion>
	<OutputType>Exe</OutputType>
</PropertyGroup>

host.json
{
    "version": "2.0",
    "logging": {
        "applicationInsights": {
            "samplingSettings": {
                "isEnabled": true,
                "excludedTypes": "Request"
            }
        }
    },
    "functionTimeout": "01:00:00"
}

As far as the Azure part goes, I have a Locally redundant StorageV2 (general purpose v2),
Event Grid System Topic:

And an event subscription created directly through storage account with filtering set to react only to a specific container:

with Web Hook endpoint https://....azurewebsites.net/runtime/webhooks/EventGrid?functionName=Function

and Additional features set as seen in the original post screenshot
Azure function config:

Adding this to the backlog for sprint assignment.

Any idea when this will be addressed? Or is there another way to implement batching with event grid triggered functions that works around this?

@nixa333 @jblanchet
I was experiencing the same problem. but on .NET 6.0.
Today I managed to fix it by upgrading to .NET 7.0, upgrading the Extensions.EventGrid to the latest (3.3.0) and setting a flag on the EventGridTriggerAttribute, like this:
public async Task Run([EventGridTrigger(IsBatched = true)] EventGridEvent[] eventGridEvents, FunctionContext context)
Such flag was introduced on version 3.3.0, Not sure upgrading do .NET 7.0 was required, but I did it nonetheless.
Here's a screenshot of the nuggets I used:

Here's the sample code that led me to this solution:

This should be address with the latest EventGrid package and the use of the IsBatched attribute [EventGridTrigger(IsBatched = true)]


Update intro.md

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=ru
Description of changes:
Extend the list of supported platforms, according to the documentation
See https://cloud.yandex.ru/docs/ydb/reference/ydb-sdk/

Все готово!
Проверьте результат: RU,
Check the result: EN.

Hi. Thank you for the fix!
This doc source has moved to https://github.com/ydb-platform/ydb/blob/main/ydb/docs/ru/core/reference/ydb-sdk. I would appreciate if you make another PR against the new location, including both RU and EN source changes. We'll be happy to merge it with your authorship then.

Sorry, I was not quite specific about the page address. The page fixed by this PR is located here: https://cloud.yandex.ru/docs/ydb/concepts/, and it states:

To interact with YDB, you can use the YDB CLI or SDK for Java, Python, Node.js, PHP, and Go.

I've added C# to the list.
As for this link (https://cloud.yandex.ru/docs/ydb/reference/ydb-sdk/) - I used it as a reference to what languages are actually supported.
Could you please reopen the PR? I've added changes in both languages.

I just press Edit on Github on the page and get redirected to this repo, this exact page I changed. Does this mean, the link on the page is also wrong?


Adds unit tests

Summary of Changes

Adds unit tests for the column description and the popular tables APIs.
Excludes import statements from the test coverage report.

Tests
Documentation
None
CheckList
Make sure you have checked all steps below to ensure a timely review.

[x] PR title addresses the issue accurately and concisely. Example: "Updates the version of Flask to v1.0.2"

In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

[x] PR includes a summary of changes.
[x] PR adds unit tests, updates existing unit tests, OR documents why no test additions or modifications are needed.
[x] In case of new functionality, my PR adds documentation that describes how to use it.

All the public functions and the classes in the PR contain docstrings that explain what it does

[x] PR passes make test

Codecov Report

Merging #84 into master will decrease coverage by 0.8%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #84      +/-   ##
==========================================
- Coverage   74.85%   74.04%   -0.81%
==========================================
  Files          19       19
  Lines        1010      894     -116
  Branches       88       85       -3
==========================================
- Hits          756      662      -94
+ Misses        231      209      -22
  Partials       23       23

Impacted Files
Coverage Δ

metadata_service/api/popular_tables.py
100% <100%> (+28.57%)
:arrow_up:

metadata_service/api/system.py
37.5% <0%> (-20.84%)
:arrow_down:

metadata_service/api/healthcheck.py
50% <0%> (-16.67%)
:arrow_down:

metadata_service/api/tag.py
55.55% <0%> (-13.68%)
:arrow_down:

metadata_service/api/user.py
25% <0%> (-7.15%)
:arrow_down:

metadata_service/api/table.py
42.85% <0%> (-5.2%)
:arrow_down:

metadata_service/proxy/base_proxy.py
67.3% <0%> (-3.39%)
:arrow_down:

metadata_service/proxy/statsd_utilities.py
81.25% <0%> (-2.97%)
:arrow_down:

metadata_service/proxy/neo4j_proxy.py
73.17% <0%> (-1.33%)
:arrow_down:

... and 9 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 44f00e8...e83d9df. Read the comment docs.


Splunk CFN fails if the disk volume is set higher that 14000 GB

The stack fails likely due to disk volume issue using the CFN template. The first instance provisioned by the template is Splunk cluster-master, however, if the disk size specified is 14000GB and above the stack creations fails with error: 	'Failed to receive 1 resource signal(s) within the specified duration'
This would likely be due to the IOPS allocation taking a bit longer to format and mount the volume which would be causing the cfn-signal to timeout and thus initiating roll-back of the Stack.

Thx for reporting this @prats84 . We're currently looking at this issue.
Are you deploying in a new or existing VPC?

Existing VPC.

This can be closed. cc @sshvans.


Add aggregator example in README.md

Before merging this, I would like to add another code example above with torchjd.backward and torchjd.mtl_backward.
Right now, it's hard to understand because we didn't say yet what torchjd.backward and torchjd.mtl_backward are.

@PierreQuinton you can already review even if it's a draft.

Closing in favor of #130


fix(switch): immproved animation performance

Description, Motivation and Context
To discuss. Some teams using our Switch component reported that it's toggle animation was lagging when clicking on it trigger heavy computation of their pages.
Heavy computation is an issue on their side, but it seems those styles help makes seems smoother (we tested it).
WDYT ?
Types of changes

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

@Powerplex ,
Did you try using the will-change property? Because it seems from your updates that we will be animating the margin instead of using transforms, which is counterintuitive, as it is widely known that one should always prefer using transform for performant CSS animations.


Clarify mutate existing force reconciliation

Related issue
Clarify the force reconciliation for mutate existing policies.
https://github.com/kyverno/kyverno/pull/9230
This needs to be cherry-pick to 1.11 docs.

Proposed Changes

Checklist

[x] I have read the contributing guidelines.
[x] I have inspected the website preview for accuracy.
[x] I have signed off my issue.

@chipzoller - how do we track for cherry-picking?

We label same as we do on Kyverno/Kyverno.

/cherry-pick release-1-11-0


Training metrics not reported in log file

🐛 Bug
Forwarding issue found in Kaggle participation
seems all training metrics are missing in CSVLogger
Please reproduce using the BoringModel

To Reproduce
https://github.com/Borda/kaggle_plant-pathology/issues/9
Expected behavior
have complete logging
Environment

PyTorch Version (e.g., 1.0): 1.7
How you installed PyTorch (conda, pip, source): 1.3.4

Additional context

@Borda I created a minimal example to reproduce the issue but cannot find the configuration where the metrics are not logged
class CustomModel(BoringModel):
    def training_step_end(self, training_step_outputs):
        self.log("train_acc", 1., prog_bar=False)
        self.log("train_prec", 1., prog_bar=False)
        self.log("train_f1", 1., prog_bar=True)
        return super().training_step_end(training_step_outputs)

def test_integration(tmpdir):
    trainer = pl.Trainer(
        logger=CSVLogger(tmpdir),
        max_epochs=1,
    )
    model = CustomModel()
    trainer.fit(model)

    metrics = pd.read_csv(f'{trainer.logger.log_dir}/metrics.csv')
    print(metrics)

which produces the following output
metrics
   train_acc  train_prec  train_f1  epoch  step
0        1.0         1.0       1.0      0    49

I have another very simple model and still missing all train metrics
https://github.com/Borda/kaggle_brain-tumor-3D/blob/main/kaggle_brain3d/models.py


Switch build system from Browserify to webpack

@electronicwhisper – I think webpack is going to be a better foundation for the build system. It's fast, will take care of compiling both Coffeescript & Stylus (and maybe fonts?) and provides a rad live-reloading development server.
In reply to your notes in #39:

Re: react.min.js vs. react.js – The React readme says:

Note: by default, React will be in development mode. The development version includes extra warnings about common mistakes, whereas the production version includes extra performance optimizations and strips all error messages.
To use React in production mode, set the environment variable NODE_ENV to production. A minifier that performs dead-code elimination such as UglifyJS is recommended to completely remove the extra code present in development mode.

This build process does that dance when building for production, but not when running the dev server. That way we get quality React error messages during development. If performance is sometimes a problem during development, we could refine this system to allow running the dev server with React in either development or production mode.

Re: build speed – The production build process takes a while (since Uglify is kind of slow), but the dev-server is real fast. You should try it out.

Re: distribution – I set things up so that the CSS links are bundled, so no more copying anything from node_modules for distribution! (Or thirdparty, for that matter.) I think all you need now is index.html and dist. We might want to add a script to copy these into a clean directory.

Todo

[ ] Update readme.md (and anything else that refers to the build system).
[ ] Make sure autoprefixer is successfully doing whatever it was put in place to do.

Sweet!
Autoprefixer was just so I could write the CSS without having to worry about browser prefixes. I'm not even sure what the state of browser prefixes is these days. I think flexbox on Safari was the culprit that drove me to the autoprefixer solution.


Chore/config

adds clippy and rustfmt config
the rustfmt config file is lifted straight from another project of mine, so I expect you'll have some opinions about which config to keep, and which to remove. Normalising comments is nice to have. Import coalescing and reordering tend to be more divisive. What do you think?
the clippy config file sets the MSRV. This prevents clippy from making suggestions involving syntax which is not compatible with the MSRV
update: I've also updated the CI script

install toolchain in a consistent way across jobs
use nightly toolchain for clippy and rustfmt

@foresterre thanks for the feedback. I'll split this up into separate PRs.
i'll close for now


feat(cli): adapt to new api

JCloud CLI for Operator-based API
Deploy a Flow

Deploy a Flow (expose Executors & Gateway)

Get Flow Status
jc status <flowid>

Get Flow Status (Verbose)
jc status <flowid> --verbose

List all Flows
jc list --phase all

Filter Flows by phase
jc list --phase <Phase>

Filter Flows by name
jc list --phase <Phase> --name <Name>

Delete a Flow

TBD

[ ] Run Integration tests GHA manually & comment the link.

@jina-ai/team-wolf

Integration tests: https://github.com/jina-ai/jcloud/actions/runs/3453797552 :heavy_check_mark:


DocWorks for wix-crm-backend - 4 changes detected, but 1 issue detected

changes:
Service wix-crm-backend operation emailContact has changed param toContact type
Service wix-crm-backend operation emailContact has changed param toContact doc
Service wix-crm-backend operation emailContact has changed description
Service wix-crm-backend operation emailContact.examples[0] has changed title
issues:
Operation emailContact has an unknown param type wix-users.TriggeredEmailOptions (contacts.js (63))

Removed the contactInfo object from the emailContact endpoint to restore its previous state, because this endpoint has to be deprecated.


after dispose phantom, the other phantom stdout not work

i need help, friends~
as the code:
1、set phridge.config.stdout to my stream
2、phridge.spawn() to create phantomA and  phantomB
3、phantomA.dispose()
4、open a page by phantomB. i am sure that phantom has accessed the local page by log, but the phantom stdout do not through my stream
var phridge = require('phridge');
var through = require('through'); //https://github.com/dominictarr/through

//set stdout to the two-way stream(by through), so i handle the messages from phantom
phridge.config.stdout = through(function(buf){
    console.log(buf.toString());
    this.queue(buf);
}, function(){
    this.queue(null)
});

var phantomA, phantomB;

phridge.spawn()
    .then(function(phantom){
        phantomA = phantom;

        return phridge.spawn();
    })
    .then(function(phantom){
        phantomB = phantom;

        return phantomA.dispose();
    })
    .then(function(){
        var page = phantomB.createPage();
        return page.run(function(resolve){
            var page = this;
            page.open('http://localhost/touch', function(){
                console.log(page.url);                 //not to my std stream
                resolve();
            })
        })
    })
    .then(function(){
        console.log('done');
    });

some advice??
thank you!

Published with 1.0.8

it works fine, thank you!


Use the new host memory allocation API

This is step 2 in getting all host memory allocations to go through a single API. https://github.com/rapidsai/cudf/pull/17197 added in a new raw allocation API. This starts to use that new API. I will then put up another PR to CUDF that will switch HostMemoryBuffer.allocate to always call the default allocator's allocate API, which should make it so that effectively all large host memory allocations go through our default allocator HostAlloc.
After that I will start to clean up the code and remove places where we pass in HostAlloc as a separate allocation API to CUDF APIs.

Please note that this will not compile until Oct 30th or so, when it's dependency finishes going through CI.

I updated the code to also fix an issue that was showing up with row to columnar exec. It is a bug where the integration tests were failing because we are now injecting retry OOMs in places that we were not before. Because all of the processing goes through a single API now.
I think there may be some more issues that I need to debug. I am seeing an issue with the time zone DB too. But it is a bit harder to reproduce and the fix for it would likely be in spark-rapids-jni. So feel free to review this.

build


changes to remove email filter on company users get

Short description outlining key changes/additions
JIRA Ticket Number
Type of change

[ ] Bug fix
[ ] New feature
[ ] Breaking change
[ ] Infrastructure change

Pull request checklist

[ ] I have added unit tests for new code that I have added
[ ] I have added/updated functional tests where appropriate
[ ] The code follows our coding standards

An exhaustive list of peer review checks can be read here

CI: Security warnings found!


KT-11708: Go to declaration doesn't work on a call to function with SAM conversion on a derived type

Tracking issue for https://youtrack.jetbrains.com/issue/KT-11708

Works as expected with the Kotlin plugin 1.1-M03+.


The following build commands failed The following build commands failed: 	CompileXIB Resources/PreferencesWindow.xib

I 've copied the 'boost' folder in the downloaded 'boost_1_60_0' to /opt/local/include/ and also done:sudo gem install cocoapods && pod setup
then
cd Karabiner-master
make
results in the
** BUILD FAILED **
The following build commands failed:
CompileXIB Resources/PreferencesWindow.xib
(1 failure)
make[4]: *** [all] Error 65
make[3]: *** [all] Error 2
make[2]: *** [all] Error 2
make[1]: *** [build] Error 2
make: *** [all] Error 2
how to fix this failure

What is your Xcode version?
Please use Xcode 7.2.

now I've installed Xcode 7.2.1. Now the build has succeeded but returned the same errors.
** BUILD SUCCEEDED **
xcodebuild
-workspace *.xcworkspace
-scheme Pods
-configuration Release
build
SYMROOT=pwd/build
Build settings from command line:
SYMROOT = /Users/manoharreddy/Desktop/Karabiner-master
xcodebuild: error: Unknown build action 'copy/src/core/server/build'.
make[4]: *** [all] Error 65
make[3]: *** [all] Error 2
make[2]: *** [all] Error 2
make[1]: *** [build] Error 2
make: *** [all] Error 2

Please confirm you installed command line tools.

Yes command line tools have also been updated.


UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from  to before v4.9.276",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=331f5923fce4f45b8170ccf06c529e8eb28f37bc"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "331f5923fce4f45b8170ccf06c529e8eb28f37bc",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "tty: serial: 8250: serial_cs: Fix a memory leak in error handling path\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v4.9.276 by commit 331f5923fce4f45b8170ccf06c529e8eb28f37bc. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1001451


(PUP-3042) Report resources in a cycle as failed

Prior to this commit, when a dependency cycle was detected in the resource
graph, the transaction would fail immediately with an error describing the
cycle. However, the resources in question were not considered problematic in
anyway. This commit updates transaction evaluation to consider resources
involved in a cycle as failed:

Rather than fail when detecting resource dependency cycles, we return this
information back up to the caller to decide what to do with. Erroring was an
unexpected side-effect anyway given the name of the method is
report_cycles_in_graph. Still emit an error message though, as this is
thematically inline with "reporting cycles".

Add a new handler defined in the context of Puppet::Transaction that is
invoked in the context of relationship graph traversal with the detected
dependency cycles. Because the handler is defined in the context of
Puppet::Transaction our transaction report is in scope.

Given access to the report, mark all resources involved in a dependency cycle
as failed, and then fail the transaction. This has the same behavioral
characteristics as before (failing to evaluate any resources in the graph
upon discovery of a dependency cycle), but the final report should note the
failed resources.

Also passes relevant acceptance tests:
sxs58nn51z3byzy.delivery.puppetlabs.net (ubuntu1604-64-1) 16:12:30$ puppet apply --verbose /tmp/apply_manifest.pp.eukcFC
  Notice: Compiled catalog for sxs58nn51z3byzy.delivery.puppetlabs.net in environment production in 0.02 seconds
  Info: Applying configuration version '1496790752'
  Error: Found 2 dependency cycles:
  (Notify[a1] => Notify[a2] => Notify[a1])
  (Notify[b1] => Notify[b2] => Notify[b1])
  Try the '--graph' option and opening the resulting '.dot' file in OmniGraffle or GraphViz
  Error: Failed to apply catalog: One or more resource dependency cycles detected in graph

sxs58nn51z3byzy.delivery.puppetlabs.net (ubuntu1604-64-1) executed in 1.51 seconds
Exited: 1
Begin teardown
End teardown
tests/cycle_detection.rb passed in 3.16 seconds
...
sxs58nn51z3byzy.delivery.puppetlabs.net (ubuntu1604-64-1) 16:12:33$ puppet apply /tmp/report_finalized.BRDV4q/manifest.pp
  Notice: Compiled catalog for sxs58nn51z3byzy.delivery.puppetlabs.net in environment production in 0.02 seconds
  Error: Found 1 dependency cycle:
  (Notify[bar] => Notify[foo] => Notify[bar])
  Try the '--graph' option and opening the resulting '.dot' file in OmniGraffle or GraphViz
  Error: Failed to apply catalog: One or more resource dependency cycles detected in graph

sxs58nn51z3byzy.delivery.puppetlabs.net (ubuntu1604-64-1) executed in 1.52 seconds
Exited: 1

sxs58nn51z3byzy.delivery.puppetlabs.net (ubuntu1604-64-1) 16:12:34$ env PATH="/usr/bin:${PATH}" ruby /tmp/report_finalized.BRDV4q/check_report.rb /opt/puppetlabs/puppet/cache/state/last_run_report.yaml

sxs58nn51z3byzy.delivery.puppetlabs.net (ubuntu1604-64-1) executed in 0.51 seconds
Begin teardown
End teardown
tests/reports/finalized_on_cycle.rb passed in 2.79 seconds

In the console, this results in:

and events:

supersedes https://github.com/puppetlabs/puppet/pull/5914

CLA signed by all contributors.

I think one or more acceptance tests need updating due to changes in the console output:
$ env PAGER= git grep cycle .
tests/cycle_detection.rb:test_name "cycle detection and reporting"
tests/cycle_detection.rb:step "check we report a simple cycle"
tests/cycle_detection.rb:  assert_match(/Found 1 dependency cycle/, stderr,
tests/cycle_detection.rb:               "found and reported the cycle correctly")
tests/cycle_detection.rb:step "report multiple cycles in the same graph"
tests/cycle_detection.rb:  assert_match(/Found 2 dependency cycles/, stderr,
tests/cycle_detection.rb:               "found and reported the cycle correctly")
tests/parser_functions/calling_all_functions.rb:    #         :reuse,:recycle
tests/reports/finalized_on_cycle.rb:test_name "Reports are finalized on resource cycles"


Fix wrong video frame when update

frame on video texture is incorrect... fix it
Pre-Merge Checklist

[ ] Tests and/or benchmarks are included
[ ] Documentation is changed or added
[x] Lint process passed (npm run lint)
[x] Tests passed (npm run test)

Could you provide an example so we can verify?

OK

I think we fixed it in v5.
@meowtec Did you test it on your videos? I think that onBaseTextureLoaded fired before onBaseTextureUpdated and it actually switches noFrame to false by assigning something to frame property. Is it true that in your case onBaseTextureLoaded is not fired, but onBaseTextureUpdated is fired?

https://jsfiddle.net/3ytxwes9/

@ivanpopelyshev
Because I am using frame property to crop videos and images, the behavior on video is incorrect.
Yes I am using PIXI@4, maybe will upgrade to v5, but not now.

please elaborate. Do you change baseTexture width/height manually somehow?

No, my code:
  const texture = Texture.from(media)
  texture.frame = new Rectangle(
    0,
    0,
    texture.width * 0.5,
    texture.height * 0.5,
  )
  const sprite = new Sprite(texture)
  sprite.width = app.screen.width / 2
  sprite.height = app.screen.height / 2
  sprite.x = 0
  sprite.y = 0

  app.stage.addChild(sprite)

I just crop a video and put it to the stage.

Please look the reproduction: https://github.com/pixijs/pixi.js/pull/5777#issuecomment-501336118

Here's with this fix applied:
https://jsfiddle.net/ye2mn6u7/

I have two sprites: one for video and the other one for image.
They has the same width/height, the same texture width/height, and the same frame.
So I except them having the same size on the screen, right? But the video sprite is much bigger (2x2) them the image sprite.

You mean that I just override the onBaseTextureUpdated function?
That is also OK.

@meowtec is this still something you're looking for or did you find a workaround?

@bigtimebuddy I just have overwritten Texture.prototype.onBaseTextureUpdated = function() {...} in my project.


ZEPPELIN-186: Apache Phoenix interpreter

Include an interpreter for Apache Phoenix
Almost identical to Hive interpreter. Could/should generic JDBC interpreters be combined in future work?

Thanks for the contribution! LGTM.
I think having generic JDBC interpreter is good idea. especially if JDBC interpreter features something similar to Dependency loader, so it can download and load jdbc driver from maven repository.

@randerzander, while working on the postgresql and geode i had to consider few details (credit to @martin-g for pointing them out) that you can find helpful as well .

You may want to define a maxResultRow to restrict the max number of result displayed or you risk to kill your zeppelin. In couple of occasions I've forgotten to set sql LIMIT  and managed to freeze the front end.
As a safeguard you can call the close() in your open method before opening the connection
For testing use proper Mockito and MockRunner PostgreSqlInterpreterTest.java

@Leemoonsoo, i've been thinking for implementing Dep loaded in the context of postgresql. My intention was to enable different psql drivers to be used but if we implement this then it will turn the psql interpreter into a generic JDBC interpreter (may have to change the name then).
Is it possible to generalize the current Dependency implementation or reuse part of it?

I suggest separating the Generic JDBC interpreter into its own feature as a separate effort, then picking which of the existing interpreters can be collapsed into it.
Thoughts?

@randerzander what do you think about feedback from @tzolov ?

You may want to define a maxResultRow to restrict the max number of result displayed or you risk to kill your zeppelin. In couple of occasions I've forgotten to set sql LIMIT and managed to freeze the front end.
As a safeguard you can call the close() in your open method before opening the connection
For testing use proper Mockito and MockRunner PostgreSqlInterpreterTest.java

@tzolov generalizing Dependency implementation is definitely a direction (along with generalizing ZeppelinContext). We can think two different level of generalize.

generalize dependency downloading
Generalize package org.apache.zeppelin.spark.dep
generalize dependency interpreter
Generalize package org.apache.zeppelin.spark.dep and DepInterpreter

First, thanks for the review and feedback, @Leemoonsoo  and @tzolov -
I agree with the first 3, and will follow up with those changes.
However, I think we should keep the test as is for now. I will need to make a followup commit using PhoenixConnection and PhoenixStatement instead of the generic JDBC anyway- Phoenix has SQL syntax for dynamic columns that generic JDBC would reject as invalid.

First two feedbacks incorporated.
@tzolov Having looked closer at your Mockito example, I think it may work. I'll follow up here ASAP.

@tzolov @Leemoonsoo incorporated all feedbacks. Added ability to use upsert and DDL statements by switching to execute instead of executeQuery.

Apart from the comments above it looks good.
i've forgotten to mention to use execute instead of executeQuery but i've figured it out :)

@Leemoonsoo, i will start a new (dedicated) thread on the subject of generalizing and reusing the Dependency functionality.  Is there a JIRA ticket for it or shall i open new one?

@tzolov generalizing Dependency implementation is definitely a direction (along with generalizing ZeppelinContext). We can think two different level of generalize.

generalize dependency downloading
Generalize package org.apache.zeppelin.spark.dep
generalize dependency interpreter
Generalize package org.apache.zeppelin.spark.dep and DepInterpreter

@tzolov I think you can open new one. Thanks!

moving the result set and statement closes to the finally block broke upserts.. another commit coming once I figure that out.

Thanks for your help @tzolov and @Leemoonsoo I think I've got it this time!

any other feedback guys?

@randerzander  Thanks for your great work! Just out of curiosity, I believe it would be nice to have the default dependency from Apache release artifacts. i.e, 4.4.0-HBase-0.98 or 4.4.0-HBase-1.0 ...
The phoenix-core's version from Apache is a combination of Phoenix version and HBase version.

Oops, good catch thanks!

I used HBase 1.1 since that's the latest and deployed by default with the newest HDP.
Phoenix is releasing 4.5 soon- how does Zeppelin team prefer to manage version bumps?

HBase team suggest downloading 1.0.x[1] because it is the current stable release. IMO, 1.0 would be appropriate default for now. If there are incompatible changes which break building the interpreter, we may consider adding 'profiles' for versions in each release. What do you think? @randerzander
[1] http://apache.mirror.cdnetworks.com/hbase/

rolled back to 1.0- seems to work fine with HBase 1.1 - Phoenix 4.4 deployments too. -Dphoenix.version build arguments will probably suffice.

@Leemoonsoo @tzolov @youngwookim more feedback?

Looks great!

+1

+1
Thanks @randerzander !!


feat(core): APP use new SDK component

Description

Use SDK ChatPromptTemplate in dbgpt/app/scene and base_chat
Format dbgpt/app codes.
Move the http APIs of conversation to dbgpt/serve/conversation
Use StorageConversation in base_chat

How Has This Been Tested?
make test
Snapshots:
Include snapshots for easier review.
Checklist:

[x] My code follows the style guidelines of this project
[x] I have already rebased the commits and make the commit message conform to the project standard.
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] Any dependent changes have been merged and published in downstream modules

Closes #1045

ChatExcel scene， when refreshed, the error will occur.
IsADirectoryError: [Errno 21] Is a directory: 'xxx/github/eosphoros-ai/DB-GPT/pilot/data/chat_excel/

More format


⚠ Bofrost.es has degraded performance

In aac11a0, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1489 ms

Resolved: Bofrost.es performance has improved in 7f4bb6b after 6 minutes.


Make networkx optional, remove xfail from greedy

Small change to avoid the import of networkx in mapclassify.greedy if it is not used.
Since the CI now comes from conda-forge, I am also removing @pytest.mark.xfail (issue with rtree should be resolved).

Hmm, I'll have to figure out why the outcome of strategy="smallest_last" varies across environments.
@jGaboardi is there a way how to run tests in all environments to find the pattern?

Codecov Report

Merging #77 into master will decrease coverage by 0.1%.
The diff coverage is 71.4%.

@@           Coverage Diff            @@
##           master     #77     +/-   ##
========================================
- Coverage    85.7%   85.6%   -0.1%
========================================
  Files           8       8
  Lines        1478    1465     -13
========================================
- Hits         1267    1254     -13
  Misses        211     211

Impacted Files
Coverage Δ

mapclassify/greedy.py
91.4% <66.7%> (+0.1%)
:arrow_up:

mapclassify/tests/test_greedy.py
100.0% <100.0%> (ø)

@martinfleis

EDIT: it fails on Python 3.6.

Any idea about what's going on here yet?

I am trying to figure it out. So far it seems that networkx algorithm just returns different result. Both are topologically correct, but the distribution of labels is slightly off.

Confirmed as an issue in networkx (https://github.com/networkx/networkx/issues/3993). I will skip the test in Python 3.6 for now.

Confirmed as an issue in networkx (networkx/networkx#3993). I will skip the test in Python 3.6 for now.

Nice work!

It looks like rtree wasn't added to requirements_tests.txt.


Add try catch block to model refresh in compute/storage pages

Have model refresh calls placed in separate try/catch - we should still show the "instance updated" message even if the refresh failed (but want to still display an error about the refresh failing).

Pull Request Test Coverage Report for Build 684729912

0 of 5 (0.0%)  changed or added relevant lines in 2 files are covered.
99 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.002%) to 43.257%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

extensions/arc/src/ui/dashboards/postgres/postgresComputeAndStoragePage.ts
0
2
0.0%

extensions/arc/src/ui/dashboards/miaa/miaaComputeAndStoragePage.ts
0
3
0.0%

Files with Coverage Reduction
New Missed Lines
%

extensions/arc/src/ui/dashboards/postgres/postgresComputeAndStoragePage.ts
99
1.27%

Totals

Change from base Build 684638300:
-0.002%

Covered Lines:
25462

Relevant Lines:
53699

💛  - Coveralls


[WIP] Add Task: TextPrediction

Work in progress. Add TextPrediction functionality to AutoGluon.

Why is so much code here, such as Bert and other very low level functionality which I'd expect to be in GluonNLP?

@Innixma Since GluonNLP is upgrading to numpy and will be backward-incompatible to v1.7, we decide to move the necessary features to AG directly and make sure that the text part works. I will first add these to utils/nlp. Later, we can remove nlp and use gluonnlp directly.

Job PR-556-1 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/1/index.html

Job PR-556-2 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/2/index.html

Job PR-556-3 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/3/index.html

Job PR-556-4 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/4/index.html

@Innixma Since GluonNLP is upgrading to numpy and will be backward-incompatible to v1.7, we decide to move the necessary features to AG directly and make sure that the text part works. I will first add these to autogluon/contrib/nlp. Later, we can remove nlp and use gluonnlp directly.

Would it be possible to use whatever version of GluonNLP works with 1.7? How much of the contrib code is content which does not exist in a 1.7 compatible GluonNLP version? Could we use GluonNLP and just add the extra code to contrib?
Are we planning on updating the contrib code to keep aligned with GluonNLP? What if we encounter defects in the contrib code? Isn't this equivalent to maintaining a 1.7 compatible GluonNLP branch + PyPi, and if so, why not have it live in GluonNLP's repo?
If all of this doesn't work, I'm potentially OK with the current approach, but it seems to be a bit extreme.

@Innixma My plan is to remove the codes in contrib in the a future upgrade of AutoGluon, in which we will support MXNet 2.0. We will make sure that the frontend .fit() API is the same.

@Innixma My plan is to remove the codes in contrib in the a future upgrade of AutoGluon, in which we will support MXNet 2.0. We will make sure that the frontend .fit() API is the same.

I understand that the plan is for this contrib code to be temporary. I am asking if we can instead have the contrib code live in a separate GluonNLP branch that remains compatible with mxnet 1.7 (as it seems to me that the contrib files are effectively a modified GluonNLP).
@jwmueller @zhreshold @szha , do any of you have comments on this?

@Innixma maintaining compatibility with 1.7 for new toolkit development is an overhead we won't be able to take.

@Innixma maintaining compatibility with 1.7 for new toolkit development is an overhead we won't be able to take.

@sxjscience @szha :  Is it possible to fork a separate 1.7-compatible version of only the GluonNLP functionality needed for autogluon?
This would not be maintained/intended for GluonNLP users (can explicitly state this in the new repo's README), but could basically just be a separate repo like GluonNLPutils-mx17 that is imported by autogluon.
This may be preferred because then autogluon can still import GluonNLP (for its existing TextClassification task) for mxnet<=1.6 users, and autogluon can simultaneously import GluonNLPutils-mx17 (for the pending TextPrediction task) for mxnet==1.7 users.  Maybe this'll simplify the resulting autogluon CI too, and mitigate confusion regarding which GluonNLP code in autogluon is coming only from the 1.7-compatible version vs the <=1.6-compatible version (because imports in the autogluon codebase would clearly either come from GluonNLP or GluonNLPutils-mx17). It'll also offer a cleaner transition for autogluon from MXNet 1.7 -> 2.0, since the gluonNLP imports will simply change at that point in time rather than 1000s of lines of internal autogluon code from the nlp/ folder being deleted.

a separate repo

What's the difference between this and having the code in AutoGluon?

That said, @sxjscience let's try to include only the used components so that the amount of code checked in can be reduced for easier review.

@jwmueller @Innixma the current APIs are different to the rest tasks in minor cases. such as model.report('report'), while other tasks use model.results['xxx'] to query the results. We want to make sure all tasks have a consistant user experience.

@jwmueller @Innixma the current APIs are different to the rest tasks in minor cases. such as model.report('report'), while other tasks use model.results['xxx'] to query the results. We want to make sure all tasks have a consistant user experience.

We will make sure to give a review and try to maintain consistency. At present we are waiting for the development to stabilize and for the GluonNLP code to be moved to a separate package as communicated.

@sxjscience It may be useful for you to rebase the code onto mainline so the CI is able to run on this PR. It may help in your development.

for the GluonNLP code to be moved to a separate package as communicated.

I think we didn't agree on this.

for the GluonNLP code to be moved to a separate package as communicated.

I think we didn't agree on this.

Can you sync with Xingjian? He mentioned this yesterday.

Thanks. I just talked to Xingjian and we will create a autogluon-contrib-nlp

Job PR-556-134 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/134/index.html

Job PR-556-135 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/135/index.html

Job PR-556-143 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/143/index.html

Job PR-556-144 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/144/index.html

Job PR-556-145 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/145/index.html

Job PR-556-161 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/161/index.html

Job PR-556-162 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/162/index.html

Job PR-556-163 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/163/index.html

Job PR-556-164 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/164/index.html

Job PR-556-165 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/165/index.html

Job PR-556-166 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/166/index.html

Job PR-556-167 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/167/index.html

Job PR-556-168 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/168/index.html

Job PR-556-169 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/169/index.html

Job PR-556-170 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/170/index.html

Job PR-556-171 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/171/index.html

Job PR-556-172 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/172/index.html

Job PR-556-173 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/173/index.html

Job PR-556-174 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/174/index.html

Job PR-556-175 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/175/index.html

Job PR-556-176 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/176/index.html

Job PR-556-177 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/177/index.html

Job PR-556-178 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/178/index.html

Job PR-556-179 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/179/index.html

Job PR-556-181 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/181/index.html

Job PR-556-182 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/182/index.html

Job PR-556-183 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/183/index.html

Job PR-556-184 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/184/index.html

Job PR-556-185 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/185/index.html

Job PR-556-186 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/186/index.html

Job PR-556-187 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/187/index.html

Job PR-556-188 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/188/index.html

Job PR-556-189 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/189/index.html

Job PR-556-190 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/190/index.html

Job PR-556-191 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/191/index.html

Job PR-556-192 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/192/index.html

Job PR-556-193 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/193/index.html

Job PR-556-194 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/194/index.html

Job PR-556-195 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/195/index.html

Job PR-556-196 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/196/index.html

Job PR-556-197 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/197/index.html

Job PR-556-198 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/198/index.html

Job PR-556-199 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/199/index.html

Job PR-556-200 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/200/index.html

Job PR-556-201 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/201/index.html

Job PR-556-202 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/202/index.html

Job PR-556-203 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/203/index.html

Job PR-556-259 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/259/index.html

@Innixma @jwmueller Should be ready for review/merge. I've fixed the document.

Job PR-556-260 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/260/index.html

Job PR-556-261 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/261/index.html

Job PR-556-262 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/262/index.html

Job PR-556-263 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/263/index.html

Job PR-556-264 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/264/index.html

Job PR-556-267 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/267/index.html

Job PR-556-268 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/268/index.html

Job PR-556-269 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/269/index.html

Job PR-556-270 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/270/index.html

Job PR-556-271 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/271/index.html

Job PR-556-272 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/272/index.html

Job PR-556-273 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/273/index.html

Job PR-556-274 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/274/index.html

Job PR-556-275 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/275/index.html

Job PR-556-286 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/286/index.html

@sxjscience Why did the last commit succeed CI but the previous one fail?
mxnet-cu100 1.7.0b20200730 requires graphviz<0.9.0,>=0.8.1, but you'll have graphviz 0.14.1 which is incompatible.

I've manually terminated some tests. Also, just updated graphviz<0.9.0,>=0.8.1.

Job PR-556-287 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-556/287/index.html


ALT + SHIFT Shortcut Doesn't Show on Screen

How to update the shortcut list? Is it possible to customize the shortcut lists to show up on the screen?

Correct. :(
Will this be fixed soon?


Webklex\PHPIMAP\Exceptions\GetMessagesFailedException  Invalid message date.

So currently I am having an issue with fetching emails from a mailbox due to an invalid message date of 1 mail. Although this is only 1 mail, this stops the entire mailbox from read out and I can't seem to find a solution for the issue.
The code, which seems like basic throws error:  Webklex\PHPIMAP\Exceptions\GetMessagesFailedException   Invalid message date. I have not changed the config regarding the date formats either.
$inboxMessages = $this->inboxFolder->messages()->all()->get(); $spamMessages = $this->spamFolder->messages()->all()->get();
Is there a way to get the fetch working with filtering out the invalid one?

@Webklex Is it also possible to solve this issue without editing the composer package?

Hi @dannylifino ,
yes there is, if you use the current master. As you can see in https://github.com/Webklex/php-imap/commit/8cf23675169a22aa9eb7a6a3c15947b7f8d4cf76 the exception will now contain the troubling date :)
Best regards,

Hi @dannylifino ,
please give v3.0.0-alpha a try :)
Best regards,

I'm having the same problem, debugging find out that date with format "2022.07.27-14.35.59" its not parseable. can you fix that @Webklex . thanks in advance


Rule to prohibit closures?

Sometimes I accidentally write a python script like this:
import polars as pl

def f(data_1: pl.DataFrame):
    return data_1.join(data_2, on="...")

if __name__ == "__main__":
    data_1 = pl.DataFrame(...)
    data_2 = pl.DataFrame(...)
    result = f(data_1)

It can be easy to miss the mistake when f has more arguments.
I understand that sometimes people deliberately define global constants, and read from those constants without passing them into a function. But it would be nice to have an option to prohibit that pattern, and force all variables to be passed in explicitly. Is it feasible or desirable for ruff to make an optional rule like that?

Restricting any use of closures is too restricting with Ruff's current rule model. We might be able to support a rule like this once #1774 has been completed.
Even then, restricting all closures seems fairly strict and it would probably be good to come up with a more specific heuristic to reduce the false positives where the use of closures is intended.


template files should end with .j2

applies to local settings templates in django role; check for others

implemented in #166


tests: Test directory organisation

It'd be nice to prefix all the test cases targeting some specific Anchor functionality with anchor-. We could eventually break out all the misc tests into this style, e.g. tests/anchor-idl-parsing, tests/anchor-cpi (probably still tests/anchor-misc 😉) etc. It'd make it easier to know where to add tests for new functionality and make it easier to audit the existing test cases to find missing ones.
Right now it isn't clear which tests are targeting Anchor features and which are example programs.
Ref https://github.com/project-serum/anchor/issues/1625, https://github.com/project-serum/anchor/issues/1624, https://github.com/project-serum/anchor/issues/1236

agreed. we should find a way to make differentiate them more clearly.
but it seems to me as if the more idiomatic solution would be to use a better directory structure instead of basically implying a directory structure through prefixes in the names.
e.g. we could put the examples into an examples directory that lives in the root or the tests directory


jsx-wrap-multilines and conditional rendering

Hi! What do you think about using conditional rendering in this form?

Hello!

  {unreadMessages.length > 0 &&

      You have {unreadMessages.length} unread messages.

  }

(example from https://facebook.github.io/react/docs/conditional-rendering.html#inline-if-with-logical--operator)
Perhaps the rule should dictate a next style?

Hello!

  {unreadMessages.length > 0 && (

      You have {unreadMessages.length} unread messages.

  )}

Now the first option will not lead to a warning. Even if it's right, what do you think about the first and second examples?

I agree that this rule should enforce the second example. To make it non-semver-major, we'd need to add a new option conditional.

Taking a look at this.

Seems like this was added in another PR, hence closed my related PR.
To achieve this functionality, use the option: {logical: 'parens'} or {logical: 'parens-new-line'}.


Upgrade internal terraform to 0.13 or 0.14

As a user pointed out, newer Terraform built-in functions like sum are not supported in Terragrunt at the moment. We currently pull terraform v0.12.24. Can we update this to a newer version?
Related

0.13.0 is where sum was added (release notes)
We updated CI to use terraform 0.13 (merged PR)
We added support for terraform 0.14 (merged PR)

Any interest in enabling dependabot or renovatebot to automatically get PRs to update those dependencies? Might be easier to keep up than relying on users occasionally opening issues...

Any interest in enabling dependabot or renovatebot to automatically get PRs to update those dependencies? Might be easier to keep up than relying on users occasionally opening issues...

I spent some time looking into this. There are a bunch of different libraries that got moved within k8s.io/api and so forth. It will be a bit of a yak shave to get the appropriate versions of indirectly dependent packages.

I spent some time looking into this. There are a bunch of different libraries that got moved within k8s.io/api and so forth. It will be a bit of a yak shave to get the appropriate versions of indirectly dependent packages.

Another update: So, we think the main issue comes from the fact that go modules support in kubernetes is a bit shoddy right now and we might have to hack it to avoid go modules pulling in the wrong versions. It will just take some focus time to iron out.

enabling dependabot or renovatebot to automatically get PRs to update those dependencies

I wonder if renovatebot/dependabot would help here. We'd still have to correct the indirect dependency issues.

Another update: So, we think the main issue comes from the fact that go modules support in kubernetes is a bit shoddy right now and we might have to hack it to avoid go modules pulling in the wrong versions. It will just take some focus time to iron out.

enabling dependabot or renovatebot to automatically get PRs to update those dependencies

I wonder if renovatebot/dependabot would help here. We'd still have to correct the indirect dependency issues.


Revert "[sil-capture-propagation] Support generic partial_apply instr…

…uctions"

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

Did you create this revert on accident?

This is a duplicate of https://github.com/apple/swift/pull/8098.  Please do not open pull requests with stale branches.


Chrome touch events mode forced doesn't work

Hello,
I'm working on a Raspberry Pi project and it seems that there's no way I can force the touch screen events on chrome. I tried to launch chrome with:
chromium --kiosk --enable-kiosk-mode --enabled --touch-events --touch-events-ui --disable-ipv6 --allow-file-access-from-files --disable-java --disable-restore-session-state --disable-sync --disable-translate --disk-cache-size=1 --media-cache-size=1 http://materializecss.com/
Using this, most testing websites marks the browser as touch-enabled device.
Please note that everything is working well on the Chrome application for Android.
Any ideas?

I'm closing it since with further searches, it seems to be a chrome bug.


Add helper methods for sending packets

Creating an issue for transparency with the Changelog. PR on the way.

I'll submit that after a merge on #1

Excellent, thank you!

Hi @WhittlesJr. Thanks for the packet helper utilities PR, I am going to think about whether I want to include this in the project or not because my intention for the library is to be very barebones. Nonetheless I will give it some thought when I have time and get back to you.

Thank you for the consideration!

@muattiyah, have you reached a conclusion?

I think I want to keep the wrapper the way it is now (without a layer of abstraction), at least until (someday) we expose the rest of the Java API (multicast, ...etc).


Add Capella iQ Supplemental terms dialog box

Added a dialog box for the "Accept iQ Supplemental terms" so that the org owner is able to review and accept before proceeding to login. If the user is not a org owner, the user will be asked to check with the org owner and logged out.

LGTM


Cleaned the SCSS

The footer now only extends across half the screen width for me, and a non-clickable "Sections" text appeared as well. Could you have a look at that? See attached.


Remove unnecessary newlines in matrix readme

There are several newline character in the README for the matrix exercise that are causing formatting issues as described in #835.

Thanks for a) Raising this issue, b) Fixing it :heart:


Why is 36px of padding added to bottom of body when panel minimized?

I just realized that this adds 36px of padding at the bottom of the body when it's minized:
body.lobipanel-minimized {
padding-bottom: 36px;
}
It was messing up the scrolling on my page, getting a scrollbar appear and the content scrolling up 36px to far.
I set it to 0 in my css, which seemed to deal with it, but I am curious why this padding is added by lobipanel in the first place.
Thanks!

That was done because When a panel is unpinned and minimized it creates a fixed toolbar at the bottom of the page and it may overlap the content at the bottom of the body.


Cleaning the superfluous dependancies

Issue fixed here
https://github.com/conda-forge/wxpython-feedstock/pull/81

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender


Pretty URL not working V4.1.2?

Seems like there is no difference in the output build with or without

activate :directory_indexes

in the config.rb
Has there been a change?

I traced the error.  I have this line in my config
set :index_file, "index.htm"
and this caused the pretty url to not work.
FWIW under V3 this option also did not create the correct target file as described in the documentation here https://middlemanapp.com/advanced/pretty_urls/

Ah, I see. The extension expects the extensions of the source files and the index file to match. So it's looking for original-file.htm, but I suspect you're still using .html for those other files.
I think this is a bug and will fix.


Github Sync: Groups are not maintained and all of them are under Others

When I pull the JSON from Github, the groupings are not working as expected. All of them are added under others but the local JSON was rendered properly
Attached is the screenshot.

How does your JSON input look like? Do each of these tokens in JSON have a type: color property? The plugin usually puts tokens into the other category when it can't find a type property on the token.

Closing this for now, feel free to reopen if the issue persists


Compiler-libs Btype.hash_variant

Sometimes it's convenient to serialize a polymorphic variant using it's hash value. Unfortunately Btype.hash_variant is not accessible from a ppx_deriving plugin. And I cannot dynload ocamlcommon.cma because it uses unsafe features. Do you know the way to calculate hash value without copy&paste from btype.ml?

There isn't. (Except Obj.magic, but that's even worse.)

Wish granted: https://github.com/whitequark/ppx_deriving/commit/7e21e335a80f27c2fcaaf8bacac66dcab3759484.


[WelcomeUX] 'Clone git repository' errors when new SCM is enabled

Testing #18091

Ensure new SCM experience is enabled
Click 'Clone git repo...'

Error notification says 'Unable to open 'workbench.action.git.clone': Could not resolve any model with provided uri.'

I have verified that the clone git repository link is gone
But I would have expected that the git clone link is still there and that it actually works.
In the future we will only use this version of git and we should still have this funcionality in the welcome page

It's still there is you disable SCM preview. Stable will ship with it disabled. Adding the link back with the new SCM is on my list.


Add tox to CI

Just to put the cherry on top, let's add Tox to make sure that it runs on multiple versions of Python.

This is too much of a pain to do for this project. It's fine for projects with a dedicated CI server to install dependencies onto, but it's not okay for Docker containers.


Setting up ci for mysql and postgres test

Add Mysql unittest to CI
Fix plugin usage from tests

Manual tests:

Tested user interaction using Mysql
Tested user interaction using Postgres
Tested data persistency in Postrgres from previous release to the new one after migrations

good, now we have it where we want it, failing due mysql:
django.db.utils.OperationalError: (1170, "BLOB/TEXT column 'raw' used in key specification without a key length")
time to fix it 🔧

@glennmatthews one of the hottest topics here is how to manage the migrations that need to be update to be applied to Mysql (because of different restrictions).
The option I took was to update the current migrations to make it work: https://github.com/nautobot/nautobot-plugin-circuit-maintenance/pull/159/commits/cd695c279e99ec15746b51c03f46e9e3171aeac3
Looking for your feedback to understand if there is a better way of getting this working

@glennmatthews what do you think about the changes in the migrations to make them compatible with Mysql? do you see any potential drawback?

I presume you've tested with deploying the updated plugin atop an existing PostgreSQL deployment with existing data? Did everything get preserved correctly?

I presume you've tested with deploying the updated plugin atop an existing PostgreSQL deployment with existing data? Did everything get preserved correctly?

Not yet, I was waiting for your guidance on that.
so, to test it, is it simple as have data from a previous release and run the new/modified migrations on to of it?
does it make sense to test migrations from older versions?

I presume you've tested with deploying the updated plugin atop an existing PostgreSQL deployment with existing data? Did everything get preserved correctly?

Not yet, I was waiting for your guidance on that. so, to test it, is it simple as have data from a previous release and run the new/modified migrations on to of it? does it make sense to test migrations from older versions?

Oh gosh. I didn't realize you hadn't tested the migration changes at all yet. :-( I have no idea if the approach you're following here will work or not - definitely need to test with data from a previous release, install the new release, and check whether nautobot-server showmigrations and nautobot-server migrate work or complain.

I presume you've tested with deploying the updated plugin atop an existing PostgreSQL deployment with existing data? Did everything get preserved correctly?

Not yet, I was waiting for your guidance on that. so, to test it, is it simple as have data from a previous release and run the new/modified migrations on to of it? does it make sense to test migrations from older versions?

Oh gosh. I didn't realize you hadn't tested the migration changes at all yet. :-( I have no idea if the approach you're following here will work or not - definitely need to test with data from a previous release, install the new release, and check whether nautobot-server showmigrations and nautobot-server migrate work or complain.

No problem @glennmatthews , I finally done the pending tests and did some minor adjustments, and it looks like everything is working.
Manual tests done:

Tested user interaction to fetch emails from Gmail Service Account with Postgres and Mysql in last release
Tested data persistency from previous release to the new one in Postgres

What is the Nautobot console output when you start the server for the first time after upgrading from a previous version of the plugin?

What is the Nautobot console output when you start the server for the first time after upgrading from a previous version of the plugin?

Only DB and Nautobot server output:
db_1             |
db_1             | PostgreSQL Database directory appears to contain a database; Skipping initialization
db_1             |
db_1             | 2021-12-17 14:44:17.841 UTC [1] LOG:  starting PostgreSQL 14.0 on x86_64-pc-linux-musl, compiled by gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424, 64-bit
db_1             | 2021-12-17 14:44:17.841 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
db_1             | 2021-12-17 14:44:17.841 UTC [1] LOG:  listening on IPv6 address "::", port 5432
db_1             | 2021-12-17 14:44:17.846 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
db_1             | 2021-12-17 14:44:17.853 UTC [22] LOG:  database system was interrupted; last known up at 2021-12-17 14:35:08 UTC
db_1             | 2021-12-17 14:44:18.193 UTC [22] LOG:  database system was not properly shut down; automatic recovery in progress
db_1             | 2021-12-17 14:44:18.196 UTC [22] LOG:  redo starts at 0/16FAD90
db_1             | 2021-12-17 14:44:18.248 UTC [22] LOG:  invalid record length at 0/1BFCEF0: wanted 24, got 0
db_1             | 2021-12-17 14:44:18.248 UTC [22] LOG:  redo done at 0/1BFCEC8 system usage: CPU: user: 0.03 s, system: 0.01 s, elapsed: 0.05 s
db_1             | 2021-12-17 14:44:18.459 UTC [1] LOG:  database system is ready to accept connections
nautobot_1       | Performing database migrations...
nautobot_1       | Operations to perform:
nautobot_1       |   Apply all migrations: admin, auth, circuits, contenttypes, dcim, extras, ipam, nautobot_circuit_maintenance, sessions, social_django, taggit, tenancy, users, virtualization
nautobot_1       | Running migrations:
nautobot_1       |   Applying extras.0012_healthchecktestmodel... OK
nautobot_1       |   Applying extras.0013_default_fallback_value_computedfield... OK
nautobot_1       |   Applying nautobot_circuit_maintenance.0011_mysql... OK
nautobot_1       |   Applying virtualization.0003_vminterface_verbose_name... OK
nautobot_1       |
nautobot_1       | Generating cable paths...
...
nautobot_1       | Finished.
nautobot_1       |
nautobot_1       | Collecting static files...
nautobot_1       |
nautobot_1       | 972 static files copied to '/opt/nautobot/static'.
nautobot_1       |
nautobot_1       | Removing stale content types...
nautobot_1       |
nautobot_1       | Removing expired sessions...
nautobot_1       |
nautobot_1       | System check identified some issues:
nautobot_1       |
nautobot_1       | WARNINGS:
...
nautobot_1       | Performing system checks...
nautobot_1       |
nautobot_1       | System check identified no issues (0 silenced).
nautobot_1       | December 17, 2021 - 14:45:18
nautobot_1       | Django version 3.1.13, using settings 'nautobot_config'
nautobot_1       | Starting development server at http://<IP_ADDRESS>:8080/
nautobot_1       | Quit the server with CONTROL-C.
nautobot_1       | 14:45:18.579 INFO    nautobot             __init__.py                              setup() :
nautobot_1       |   Nautobot initialized!

Good to see that it applies the 11_mysql migration but I'm concerned that the updates made to the earlier migrations aren't getting applied. I suspect that if you check the DB after this migration, for instance, Note.title is still a TextField (varchar?) rather than a 512-character-max-length CharField, which is different than you'll probably see if you create the DB fresh from scratch with all of the migrations being applied.
Maybe we can take https://github.com/nautobot/nautobot-plugin-chatops/pull/76/files as an example (where it has logic in the migrations to do things differently for Postgres vs MySQL as connection.vendor?) Sorry to bring this up so late in this review.

Good to see that it applies the 11_mysql migration but I'm concerned that the updates made to the earlier migrations aren't getting applied. I suspect that if you check the DB after this migration, for instance, Note.title is still a TextField (varchar?) rather than a 512-character-max-length CharField, which is different than you'll probably see if you create the DB fresh from scratch with all of the migrations being applied.
Maybe we can take https://github.com/nautobot/nautobot-plugin-chatops/pull/76/files as an example (where it has logic in the migrations to do things differently for Postgres vs MySQL as connection.vendor?) Sorry to bring this up so late in this review.

yes, I also think you are right, and I should handle the exceptions by `connection.vendor

@glennmatthews I used the approach you suggested in ea2dab1e29a44501e88de93b760fd4e9c56ce9f1
Does this looks better?


Identifier Validation: Remove _validateIdentifiers

Remove _validateIdentifiers since the rule should check for the identifiers it is expecting instead of relying on abstract to know every identifier.
@ingluisjimenez
@DFoxinator

👍

👍


Radix Sort

Description
Algorithm and code for radix sort under Sorting Algorithms along with proper explanation as well as detailed documentation.
Domain
Algorithm
Type of Contribution
Addition
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of LearnCPP.

/assign


 However https://github.com/facebookincubator/create-react-app/pull/1705 is a proper fix for this, so I think we should remove the _ rule in the next major bump. This would fix https://github.com/facebookincubator/create-react-app/issues/1387.

Also, why do we have vars: 'local' rather than the default 'global setting?

I can submit a PR.
Though I am not sure about the vars setting. Can't find a use case of having an unused global variable.

If you could go through the git blame history for who added it and why, that could help. Or maybe there was no good reason at all.

Seems like there was no good reason.
It was there since custom eslint rules were added in the begining. See #27

We probably took it here then. Would be nice to learn why Airbnb config specifies this.

Maybe @ljharb could say!

The default setting in eslint was local at the time Airbnb set their config. Eslint later changed the default to all (global) and I'm guessing Airbnb never updated.

@gaearon should the vars setting be set to default?

Yea.

see #1763

This setting certainly predates my involvement with the Airbnb config. I can't see any reason not to change it to "all" - can someone file an issue, or better, send a PR explaining the rationale?

@doshisid Do you mind following up with @ljharb and raising an issue in Airbnb ESLint config repo too?

Fixed by https://github.com/facebookincubator/create-react-app/pull/1763.

Sure, I'll do it.


Simplify adding a DbItem to a Db and getting the Item instance back out of the FakeDb

Asked by @kamsar in Twitter. The problem is that in order to get an Item instance, one have to write three lines of code:
DbItem dbItem = new DbItem("item");
db.Add(dbItem);
Item item = db.GetItem("/sitecore/content/item");

There is a suggestion to introduce new db.Create() extension method which would combine the Add() and GetItem() functionality:
DbItem dbItem = new DbItem("item");
Item item = db.Create(dbItem);

:+1:

I very much like the idea!
I was thinking about the semantic though and I'm not sure I like bolting on extension methods to the Db object. It looks a little bit out of place. I was searching for an example and fluent assertions come to mind with their  Should().
What if if we did something like Db.Api.Create() or even Db.Api().Create() anticipating future overloads?
Just thinking out loud. Again, fully support the idea of having a shortcut API for add-and-get. But if it's a beginning of a fluent API of sort then maybe Db itself is not a good home for new extension methods?
Thought? Am I overthinking?
Sent from my iPhone

On Oct 27, 2015, at 2:56 PM, Kam Figy<EMAIL_ADDRESS>wrote:
—
Reply to this email directly or view it on GitHub.

So, technically it is possible to return an Item from the existing db.Add() methods. It'll not be a breaking change and there are no new methods needed in this case.
I just have a feeling that the Add() method should always be void and Create() should return some result. Tried to find examples in .NET and Sitecore API but realized that it's not so obvious. There are numerous variants available...
I don't think there is a place for the fluent API. There are two user scenarios:

I want to add items to my database, meaning there are some items needs to be there. I don't need the Item instances right here in the test, I might get them in my SUT later if necessary. Db.Add() or collection initializers are used.

I need to get a Sitecore Item instance right here, right now. I want to create it using the minimal code: Item item = db.Create("home").

But.. looking on the second scenario, I also have a feeling that smth is wrong here...
//cc: @kamsar

The alternative might be to introduce builders. For instance:
var item1 = db.Build<Item>().FromDbItem(new DbItem("root"));
var item2 = db.Build<Item>().WithName("home");

@pveller Yep, that is the fluent API :-D

Totally! :) I knew something was wrong with the db.Create() and I also remember mentioning the fluent API back when @kamsar asked for the simple add-and-get.
I like it a lot. Builders it is!


Create migrate-process-to-active-window-station.yml

need example. will provide when i have a moment.

Should we remove the example section and make this a nursery rule for now?

yeah let’s do that


GUI design

Testing technologies and making the first draft

Formular.zip
first form version done by @PeterDuska

looks good, I think we could include some way to download all pictures at once.

Added button at the top of the report


[QUESTION] Is it possible to get a tweet object from just its id?

I know just the id of a tweet. Is there any way I can get the twint tweet object corresponding to this tweet? I don't know the username of the user beforehand.

To explain my use case a bit further,
I have tweet 1. Suppose tweet 1 is a reply to tweet 2. I am trying to obtain information about tweet 2 from just tweet 1.
I've managed to get the conversation_id of tweet 1 and am trying to obtain tweet 2 using this. Hope this explains my use case a bit better.

Sounds like you want to hydrate tweets - you can use twarc for that https://github.com/DocNow/twarc

@neon-ninja Thanks for your response. Yes, that should do it!
Closing the issue.


fix: Added --locked so CI will use dependencies in the lock file

This should fix some of the errors in CI. Specifically the end to end tests.

Tests currently fail with
   Compiling synth-core v0.6.3 (/home/runner/work/synth/synth/core)
error[E0599]: no associated item named `MAX` found for struct `chrono::NaiveDateTime` in the current scope
   --> core/src/graph/series.rs:250:85
    |
250 |         let (mut earliest_index, mut earliest) = (0, &chrono::naive::NaiveDateTime::MAX);
    |                                                                                ^^^ associated item not found in `chrono::NaiveDateTime`

For more information about this error, try `rustc --explain E0599`.
error: could not compile `synth-core` due to previous error
warning: build failed, waiting for other jobs to finish...
Error: Process completed with exit code 101.

Just avoiding Chrono's and reverting some commits will probably let the code pass CI.

Seems like this is the first stable PR. Great job Sam.


Background jobs leave scary zombies

With the way we fork and exec without wait for background jobs at the moment, they will remain zombies until the shell itself is exited.
Zombies are scary and bad. I'm sure the solution will come at the time we implement #6.

We've stopped using the potentially dangerous fork function and instead call fork_and_wait on all jobs, including background jobs. See #4 for a solution to that.


sticky top and fixing the portraits: WIP

work in progress: do not merge yet.

ok fixed nav bar transparency issue, drop box is still colliding with donut


[Warhammer 4e Character Sheet] Magic fix

[x] The pull request title clearly contains the name of the sheet I am editing.
[x] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[x] The pull request makes changes to files in only one sub-folder.
[x] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

Changes / Description

Fixed Lore effect mapping and arcane custom name
Add il8n tags

Character Sheet Info Roll20 Internal Use only.

@nmbradley hi char sheet are is not working since this PR, just see a white bar. this is on all servers. Is something wrong from last week ? might need to revert.

I've manually rebuilt the sheet to see if it fixes the issue, if this doesn't resolve the issue I can revert.

@nmbradley no change


Issue with TeensyLC

Hi luni64,
I have a strange issue with EncoderTool on TeensyLC.
Here's the MWE:
#include <EncoderTool.h>

using namespace EncoderTool;
PolledEncoder enc;

void setup() {
  Serial.begin(9600);
  enc.begin(5, 6, 4, CountMode::half, INPUT_PULLUP);
}

void loop() {
  enc.tick();
  if(enc.valueChanged())
    Serial.println(enc.getValue());
}

On Teensy 3.2 this works perfectly fine: each detent will increment/decrement by 1. On TeensyLC, however, it will keep incrementing like crazy (without turning the encoder) with each iteration of loop() - but only for every other detent. I'm using this encoder. Is there anything that comes to mind?
Cheers!

This looks weird. Unfortunately I'm currently not at home and don't have a LC with me. I'll have a look on Sunday.

Thanks a lot!

I can reproduce this. It looks like there is a bug in the direct read code for the T-LC. I'll have a closer look later. As a quick workaround you can do the following:
Change line 46 in the library file cores.h as shown here:

This disables the direct read code for the T-LC so that it falls back to a standard digitalRead/digitalWrite which works here.
Can you please check if this works for you as well?

Thanks for looking into this! I can confirm that the workaround helps.

Great, I'll look for a permanent solution asap

Thanks for the fix Lutz! It works as expected now.

Great, let me know if you find something else


chore: update ubuntu and add safe dir vars

Contributor Comments
This PR updates the base Ubuntu image to 22.04 and adds environment variables for detecting a .git directory mounted in the container and setting it as safe.
Pull Request Checklist
Thank you for submitting a contribution to easy_infra!
In order to streamline the review of your contribution we ask that you review and comply with the below requirements:

[x] Rebase your branch against the latest commit of the target branch
[x] If you are adding a dependency, please explain how it was chosen
[x] If manual testing is needed in order to validate the changes, provide a testing plan and the expected results
[x] If there is an issue associated with your Pull Request, link the issue to the PR.

https://github.com/SeisoLLC/easy_infra/blob/cb54751d9ff5e6bb7eccd8211bbbedfc9c341335/easy_infra/utils.py#L41 may be the reason for the test failure. It's doing updates using a previously release easy_infra image which is 20.04 so it won't align with 22.04.  Probably need to manually fix (find/specify the right version for 22.04 in easy_infra.yml) and then after this merge the auto updates will work again.

This is blocked on https://github.com/SeisoLLC/easy_infra/pull/279


Fix mapping of MAV_STATE

closes #12
Previously, mavlink_vehicles was mapping the more specific mavlink MAV_STATE
enum to a more generic STATUS enum as follows:
MAV_STATE_UNINIT -> mavlink_vehicles::status::STANDBY
MAV_STATE_BOOT -> mavlink_vehicles::status::STANDBY
MAV_STATE_CALIBRATING -> mavlink_vehicles::status::STANDBY
MAV_STATE_ACTIVE -> mavlink_vehicles::status::ACTIVE
MAV_STATE_CRITICAL -> mavlink_vehicles::status::STANDBY
MAV_STATE_EMERGENCY -> mavlink_vehicles::status::STANDBY
MAV_STATE_POWEROFF -> mavlink_vehicles::status::STANDBY
This simplification has been placed taking in consideration only a specific use
case: determine whether the vehicle is already flying (ACTIVE) or not
(STANDBY). While testing It has been noted that the states STATE_CRITICAL and
STATE_EMERGENCY might also be set during flight, and so, those should also be
mapped to mavlink_vehicles::status::ACTIVE.
This is what this patch does:
MAV_STATE_UNINIT -> mavlink_vehicles::status::STANDBY
MAV_STATE_BOOT -> mavlink_vehicles::status::STANDBY
MAV_STATE_CALIBRATING -> mavlink_vehicles::status::STANDBY
MAV_STATE_ACTIVE -> mavlink_vehicles::status::ACTIVE
MAV_STATE_CRITICAL -> mavlink_vehicles::status::ACTIVE
MAV_STATE_EMERGENCY -> mavlink_vehicles::status::ACTIVE
MAV_STATE_POWEROFF -> mavlink_vehicles::status::STANDBY
Signed-off-by: Guilherme Campos Camargo<EMAIL_ADDRESS>

Can Emergency and Critical be set while the vehicle is not flying? If so, won't this generate any problem?
If not, LGTM.

I have noticed that those states might be set in some specific cases when the vehicle is not flying: for example when the default gcs (255), for some reason, connects to the ardupilot bu then, for some reason,  stops sending heartbeats.
In our use-case this will not happen since the FS_GCS_ENABLE parameter is set to 0 in the SITL EEPROM, however I agree that we must take a closer look into it to properly solve this problem.
I will merge this PR now, since it is critical to have our use-case working properly, however I'll leave an Issue open explaining the problem.


Add 'Expiration' to Set-VdcCredential and Get-VdcCredential and add New-VdcCredential

Summary of the new feature/enhancement
When a credential is added via the GUI a date is added automatically added to the Expires field 10 years in the future. This is marked as a required field in the GUI using *. Neither Get-VdcCredential nor Set-VdcCredential currently reads this field.
New-VdcCredential is needed to add a brand new credential to the system.
Currently when using the API, New-VdcObject can create any of the different credential types as an object by specifying the class. It, however, does not write the actual credential itself without many extra calls.
Using Set-Credential to add the credential itself works for the 3 types supported (currently Username, Password and Certificate) but does not add the Expiration field to a new object that is needed to add the Expiries date. This results in a date of '01/01/0001 07:00:00' being set. Additionally, it does not support certificate credentials that are linked to an existing certificate using the 'Certificate DN' value.
Get-VdcCredential does not retrieve this value and it has to be read by using Get-VdcAttribute.
Proposed technical implementation details
I propose refactoring these functions to support all of the credential types, the Expiration value (using a Datetime object type), the Certificate DN value and any other values needed. The addition of New-VdcCredential (using POST Credentials/Create) as a function will make it easier to add any of the different credential types.

I'm going to break this up into different issues, lots being asked.


fix link and text in roadmap

Proposed changes
fix link and text in roadmap
Types of changes
only change in the documentation

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)

Checklist

[x] I have read the CONTRIBUTING doc
[x] I have signed the CLA
[ ] I have updated the RELEASE_NOTES

@modularTaco thanks for this! If I could ask just one small favour before we merge this PR. I've added a checkbox above "have updated the RELEASE_NOTES", can you please put a tick in and also update RELEASE_NOTES.md with a one-liner referring to this PR, here's an example from a recent PR

https://github.com/orchestracities/ngsi-timeseries-api/pull/604/files#diff-68d24fa81558aae3d8c59e2aa57a4fa719ea3b04d7fa14beff45f16f00858f50R33

@modularTaco thanks for this! If I could ask just one small favour before we merge this PR. I've added a checkbox above "have updated the RELEASE_NOTES", can you please put a tick in and also update RELEASE_NOTES.md with a one-liner referring to this PR, here's an example from a recent PR

https://github.com/orchestracities/ngsi-timeseries-api/pull/604/files#diff-68d24fa81558aae3d8c59e2aa57a4fa719ea3b04d7fa14beff45f16f00858f50R33

done :+1: