Ingress: Add tests for various other ingress controllers

closes https://github.com/linkerd/linkerd2-conformance/issues/7
https://github.com/linkerd/linkerd2-conformance/pull/1 introduced tests for ingress to verify the working of ingress-nginx controller with Linkerd. This PR adds tests for the following controllers:

[x] Traefik
[x] Contour
[x] Gloo
[x] Ambassador

@ihcsim @Pothulapati I've opened a refactored (cleaner and simpler) version of this PR - https://github.com/linkerd/linkerd2-conformance/pull/19 that only tackles nginx, ambassador and traefik ingress for now. Haven't directly made that change here so that the gloo and contour tests aren't lost from this PR. :)
Because gloo and contour have a slightly different process from these ingress controllers, we should tackle them in a separate PR once  https://github.com/linkerd/linkerd2-conformance/pull/19 gets merged. WDYT?

@mayankshah1607 Thanks! Yeah, separate PRs for the other ingress controllers that require more configuration make sense to me.

Closing this once since https://github.com/linkerd/linkerd2-conformance/pull/19 got merged. :)


There should be a section about certificates etc.

The gRPC features are very exciting, but I hit a snag immediately using the templates. When the ASP.NET Core gRPC service was not setup using TLS/HTTPS, I changed that immediately by reflex, TLS all the things :)
But when using the client you can either have it use SslCredentials.Insecure (now goes against every fiber of my being, hehe) or manage certificates and keys manually which is a pain I think.
I'm not sure why you manually have to handle that, I was looking at the new managed client using HttpClient, but that is the same deal I think. I don't know enough about gRPC, TCP, HTTP/2 and TLS to understand why :)
So a section in the docs explaining why that is and best practices for managing certificates etc. would be a good idea if we, for some reason, are not able to just let HttpClient handle it...

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 1d298a6c-8ddc-dbc8-d219-0fa7138442c2
Version Independent ID: b96be346-958a-cfcd-d80a-c352d64223e8
Content: Create a .NET Core gRPC client and server in ASP.NET Core
Content Source: aspnetcore/tutorials/grpc/grpc-start.md
Product: aspnet-core
Technology: aspnetcore-tutorials
GitHub Login: @JunTaoLuo
Microsoft Alias: johluo

In preview 7 the docs will recommend using HTTPS everywhere via the new HttpClient driven gRPC client
Related PR: https://github.com/aspnet/AspNetCore.Docs/pull/13051

Fixed in https://github.com/aspnet/AspNetCore.Docs/pull/13051


Error importing a CSV

Describe the bug
When trying to import a 500MB CSV Meilisearch throws an exception that the Payload is to big.
The "MEILI_HTTP_PAYLOAD_SIZE_LIMIT" is set to '1Gb', so this should not be the problem.
Tried to set it to '2Gb' and it fails again.
Setting the "MEILI_HTTP_PAYLOAD_SIZE_LIMIT" to '10Gb', seems to work.
To Reproduce
Steps to reproduce the behavior:

Start Meilisearch with MEILI_HTTP_PAYLOAD_SIZE_LIMIT of 1Gb.
Try to import a 500Mb CSV file.

Expected behavior
I expected my CSV (500MB) file to import without a problem since the MEILI_HTTP_PAYLOAD_SIZE_LIMIT is set to 1Gb.
Screenshots
Docker Compose:

CSV Size:

Exception:

Meilisearch version:
1.10.1
Additional context
I am using a Meilisearch Docker image.

I just saw that the conversion is in "gygabits" and not "gigabytes".
Probably this should be mentioned in the docs, since "Gb" is very easy to overlook.


Update django.po

Small orfographic, grammatic changes

Small orfographic, grammatic changes.

Thanks for the report, however, translations are handled at Transifex.


Update DG

Update Design Section
Each of one of us to update our own feature under Implementation feature
Update Manual Testing Section.

Update Status

[x] Teng hon
[x] Calvin
[x] Ethan
[x] Wang bin
[X] Peiyuan

Everyone has completed their share of updating DG.


Write a data release script

We're publishing / archiving our data releases at Zenodo, and they provide a RESTful API that we can access from within Python to automate the release process and to populate the Zenodo metadata fields, many of which we already compile for our own metadata.
In addition, we need to make sure that we generate the archived data in a controlled and reproducible way -- using a particular published release of the catalystcoop.pudl package, in a well-defined Python environment.
This will all be much more reliable and repeatable (and easier) if we have a script that does it for us the same way ever time. What all would such a script need to do?

Create a reproducible software environment: Install the most recently released version of catalystcoop.pudl in a fresh conda environment along with all of its dependencies, and record the entire list of installed python packages and their versions in an environment.yml or requirements.txt file.
Acquire fresh data: Download a fresh copy of all of the input data to be packaged, so we know what date it is from. Otherwise we all have potentially different collections of older downloads in our datastores, since sometimes agencies go back and alter the data after its initial publication.
Run the ETL process: Using the installed PUDL software and the fresh data, generate the bundle of tabular data packages to be released. This may include reserving one or more DOIs using the Zenodo API (See Issue #419).
Validate the packaged data: Populate a local SQLite DB with all of the data to be released, and run the full set of data validation tests on it. Any failures should be documented in the data release notes.
Create a compressed archive of the inputs: This is a .zip or .tgz of the datastore which was used in the ETL process, for archiving alongside the data packages, so that the process can be reproduced. Should this be one giant file? Or should we break it out by data source?
Create a compressed archive of the outputs: This is a .zip or .tgz of each of the individual data packages that's being archived. Keeping the data packages separate means people can download only the ones that they need/want.
Upload everything to Zenodo: If a DOI has been reserved earlier in the process, we'll need to make sure that we're uploading to that same archive. Stuff to archive includes:

the compressed archive(s) of the input datastore.
the environment.yml file defining the python environment that was used.
the compressed archives of the output data packages.
a script which, given the contents of the Zenodo archive, can perfectly re-create the archived data packages. This will probably be the same script that this issue is referring to.

Populate Zenodo metadata: Using existing metadata (and possibly some additional information that is given to the data release script as input), populate the metadata associated with the data release at Zenodo using their RESTful API.

Another thing to maybe discuss here is at what granularity do we want to archive this data and assign DOIs?

We want users to be able to download data packages individually, rather than requiring everyone to pull down everything. This can be done either by archiving them separately on Zenodo, even though they've been generated as part of the same ETL process, or by keeping each of the data packages archived as separate files within the Zenodo archive.
We want to make it clear that all of the data packages generated as part of a single ETL run -- using the same input data and the same software environment -- are part of the same overall release of PUDL data and can be used together. If they're not in the same Zenodo archive, we'll need to link them together by their independent DOIs.
We want to keep track of breaking changes between releases, which in theory should be doable using the data package version numbers, in the individual data package metadata. Right now it seems like every release will be breaking... but hopefully it'll stabilize over time.

I've been leaning toward releasing all the data packages in the same Zenodo archive, so they are obviously linked to each other, and so there's less overhead in doing a data release, and less duplication in what's getting archived. In this scenario all the data packages would share the single DOI that's assigned to the overall Zenodo archive... but is that wrong? Is that an okay way to use the DOIs?
The alternative would be to generate all the data packages at the same time, and then push each of them up to their own Zenodo archives, with their own DOIs. If we have a script that can do that in an automated way, maybe it's not much more overhead, but it seems like it might be more confusing for users to navigate.

@lwinfree I'm curious if you have thoughts on the correct way to use DOIs in connection with the published data packages, as discussed above..

Inputs that we need to feed into this script:

The master PUDL data DOI at Zenodo -- this points at the archive as a whole, not any individual release, and always re-directs to the most recent version.  We'll need this for reserving an appropriate version specific DOI.
An ETL settings file that defines:

Data package bundle name
Data package names / titles / descriptions
Data package versions
Data package contents (years, states, tables, etc.)

The ETL settings file should allow us to automatically:

Download the required data to a local data store.
Run the ETL process, generating data packages.
Reserve an appropriate versioned DOI for the data package bundle to be archived.

If there's additional metadata that we need to populate at Zenodo, where should that live? Should we make sure that all of it is available within the datapackage metadata? Should it be stored in the ETL settings file? Should it be in its own YAML or JSON file?

Hi @zaneselvans ! OK I think I am leaning towards:

I've been leaning toward releasing all the data packages in the same Zenodo archive, so they are obviously linked to each other, and so there's less overhead in doing a data release, and less duplication in what's getting archived. In this scenario all the data packages would share the single DOI that's assigned to the overall Zenodo archive... but is that wrong? Is that an okay way to use the DOIs?

Breaking it down, I think the main archive should definitely have a DOI. I think it makes sense to have all the data packages in the same archive. I understand that if all the datapackages have the same DOI (that is, the archive DOI), then it could be confusing. But, could you generate a separate UUID for each datapackage during the ETL? In the ID field? So that the whole archive has a DOI but each datapackage is identifiable with its UUID?

Right now the UUID identifies the ETL run that generated the data packages -- every run gets its own UUID which is stamped in all the data packages it outputs, and this UUID is used to verify inter-package compatibility any time the data packages are used together -- like when all the resources are combined into a single data package and that package is loaded into a database (since the ETL parameters could change between runs, and we don't want packages which were generated under different circumstances to be accidentally used together).
In the case where each data package (EPA CEMS, FERC Form 1, EIA 860/923) is archived as its own resource on Zenodo, there would be no "main" archive -- each of them would have their own master DOI, and their own lineage of versioned DOIs, and the only things linking particular versions of those packages together would be the ETL UUID, and any Zenodo level metadata pointing at other specific versioned DOIs for the other packages which are compatible with an individual package.
I guess another option would be to do both of these things -- have independent CEMS, FERC1, and EIA data packages, with their own DOIs, and also have a master PUDL Data Release archive, which has its own DOI, and which contains another copy of each of the independent data packages, with its own personal DOI stamped inside it.  But that level of duplication seems kinda silly.
Another another option (which is maybe what you were suggesting) is that the individual data packages could just... not have DOIs in them at all and instead be identified by UUIDs alone.  There could be a UUID in the id field, and another UUID in the datapkg-bundle-id field (which indicates compatibility).  But then someone who finds themselves with just the data package doesn't have a clear reference pointing to the authoritative source for the package, like a DOI would provide...

Another snag!
We want the data that we're publishing to be reproducible, which means it needs to be processed by a published release of the PUDL software (v0.2.1) that can be referenced in an environment.yml file or some other record of the software environment, and reproduced by a user later.  We also want the data to be validated before we publish it -- if ever there were a time when the data validation matters, it's when we're publishing data for others to use.
However at the moment these two things are at odds, because at the moment the data validation can only be run using pytest and tox and the mechanics of running the data validation is encoded in the tests/validation modules rather than the distributed package. We also don't want to get into a situation where in order to attempt to do a data release, we need to release a new version of PUDL, and then debug data release related issues, and then release another new version of PUDL, etc. for several cycles.
I think the right solution probably goes along with issue #400, moving the data validation test-case specifications into package_data, and any required functions into pudl.validate if they aren't already there, in such a way that:

the validation test modules can easily use the test cases to parameterize the tests,
the data validation debugging notebook(s) can easily make use of the test cases to visualize what's going on,
we can write a stand-alone data validation script which can be distributed as part of the package, and run after generation of the to-be-published data packages.

However, in the mean time, it seems like it might be best to just get something rough published in the same form that we expect to be publishing future data releases, so that people can at least play with the data, without having to run the whole ETL pipeline, and we can get the DOI established, and start playing with the Zenodo API a little...

Hi Zane!
For the DOI question, have you come to a conclusion? I'm happy to jump on a call to discuss if that would help (we can chat at our normal call on Monday, but I'm happy to chat earlier too). My thoughts in a nutshell: the large zenodo archive (containing datapacakges all generated by the same ETL, which should all be compatible*) gets one DOI. The datapackages inside that archive get 2 IDs - one that is the UUID for the datapackage, and one that is called something like "master_archive_id" that is the same as the archive's DOI. That way the single datapackages can be linked back to the master archive. Does that make sense? Am I missing something? I had to draw out a diagram to think this through 🙃
*assuming that all datapackages from the same ETL should be compatible
For the validation question, I'm going to tag @roll, but I think your idea here is correct:

I think the right solution probably goes along with issue #400, moving the data validation test-case specifications into package_data, and any required functions into pudl.validate if they aren't already there

Yeah, I think without changes to the metadata specification, that's probably the best thing to do. We already have a datapkg-bundle-uuid field at the package level, so I guess we can just add a parallel datapkg-bundle-doi field alongside it for the bundles that get archived, and set the id field to a generic UUID so it can definitely be uniquely identified if it's found in the wild somewhere.


i want to select date from fscalender and print on label

Can any one please help me how to select date and print on label

@vishalofficial96 you can implement FSCalendarDelegate and use
- (void)calendar:(FSCalendar *)calendar didSelectDate:(NSDate *)date atMonthPosition:(FSCalendarMonthPosition)monthPosition

@vishalofficial96 Watch the sample projects,

I am using this library, but this method returns the previous day to me rather than actual selected date. For ex: I am selecting 25th April on calendar view, but in this method I receive 24th April. Any possible solutions?

@priya1588  you have to convert time From IST to UTC

@priya1588 Show this simple code
cell.lblStartTime.text = Utilities.getFormatedTimeInStringGMT(dateTime: Utilities.localDateFromUTC(timestamp:<PHONE_NUMBER>))

Hi @priya1588.
Unfortunately, @vishalofficial96 answer is not fully correct.
NSDate only represents an absolute point in time. It has no concept of timezone.
Parameter date from - (void)calendar:(FSCalendar *)calendar didSelectDate:(NSDate *)date atMonthPosition:(FSCalendarMonthPosition)monthPosition is a 00:00 of specific date. When you  po the object or compare it with the other NSDate(current time, for example); system, assume that it is UTC timestamp and convert it into local time (that is where you have an issue, unless you live in GMT).
So to properly compare two NSDate you need to use NSDateComponents.
For example:
 - (NSComparisonResult)compareDatesWith:(NSDate*)otherDate {
     NSCalendar* calendar = [NSCalendar currentCalendar];

     unsigned unitFlags = NSCalendarUnitYear | NSCalendarUnitMonth |  NSCalendarUnitDay;
     NSDateComponents* comp1 = [calendar components:unitFlags fromDate:self];
     NSDateComponents* comp2 = [calendar components:unitFlags fromDate:otherDate];
     NSInteger comparison = [comp1 year] * 10000 + [comp1 month] * 100 + [comp1 day] -
             ([comp2 year] * 10000 + [comp2 month] * 100 + [comp2 day]);

     return comparison > 0 ? NSOrderedDescending : comparison < 0 ? NSOrderedAscending :      NSOrderedSame;
 }


WIP: SLE15SP5, Missing stuff for Debian11/EL8/Leap15.4

What does this PR change?
This PR was originally about 4.4, but let's restrict it to SLE15SP5, so we can merge asap.

Add SLE15SP4
Fix missing stuff for Debian11/EL8/Leap15.4

I also noticed Ubuntu 22.04 is missing, but I leave that for someone else to fix it.

Closing. Got too many conflits, so we better have a new PR for this.


[Feature] Don't launch drop-down when clearing an item.

I think when just want to remove one or two items and not add others, the dropdown should not be shown automatically.
Or maybe make it optional: data-show-dropdown-on-clear="false"

If the dropdown is closed, then when you delete one or two items the dropdown will still remain closed

My bad. You'r right. But when data-searchable="true" and you then click X the dropdown will open...


Lint CSS code with stylelint (as part of the boilerplate)?

The boilerplate issue mentions adding structured CSS.
Do you want me to submit a PR that adds linting to each component's CSS, using stylelint and the stylelint-config-standard? Although the config won't help enforce the use of CSS Modules, it will catch little coding mistakes like accidental shorthand overrides and invalid hex colours.
As an aside, it's awesome to see stylelint get a mention in the early mock-up designs! :)

Yeah sure, sgtm!

Good idea


Redirect issues

There is an issue where the client will request a asset for a website but the proxy will think it as the proxy root instead of the website that is hosting the requested asset.
For example:
By going to https://google.com on the proxy, the website will request the Google logo, but will instead try to request it from the proxy's root instead of Google's root.
https://************.herokuapp.com/images/branding/googlelogo/1x/googlelogo_color_272x92dp.png instead of https://************.herokuapp.com/https://google.com/images/branding/googlelogo/1x/googlelogo_color_272x92dp.png

This proxy should not be used as a generic web proxy. It only adds CORS headers to allow cross-origin reads, and makes no attempt at trying to resolve relative URLs. I suggest to look for alternatives if you need a generic web proxy.


feat: make interface responsive

I think we can make the interface responsive, for two purposes:

I can imagine that people share playground links, with the receiving party opening the playground on their phone. Not to edit, but just to check the results.

Having the playground side-by-side on a single monitor with other editing tools makes sense. The current layout is quite wide and limits the efficiency in "split screen" layouts.

Quick sketch:

Based on what I see in the tailwind docs, this shouldn't be hard.

Closed by #16


Microk8s 1.24 Service Account Tokens Not Generated

Hi everyone, I'll start by saying that this is a great project, thank you!
Summary
In Microk8s v1.24/stable, service account token generation does not occur.

What Should Happen Instead?
In Microk8s v1.23/stable, service account tokens are generated automatically.   We did not see anything related to this in the release notes.  If this divergence is intended, could you point us towards materials that would help in recreating the previous functionality?

Reproduction Steps

Run on Windows 10 Pro with Hyper-V enabled

Quick Create an Ubuntu 20.04 VM in the Hyper-V manager on

Install microk8s v1.24/stable.  sudo snap install microk8s --classic --channel=1.24/stable
View service accounts without tokens sudo microk8s kubectl get sa -A

Introspection Report

The following inspection reports are run on the same machine about 10 or so minutes apart.
1.24/stable - no tokens generated
inspection-v1.24.zip
1.23/stable - tokens generated
inspection-v1.23.zip

I think its related to this change in upstream k8s https://github.com/kubernetes/kubernetes/pull/108309
https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.24.md#no-really-you-must-read-this-before-you-upgrade
https://kubernetes.io/docs/concepts/configuration/secret/#service-account-token-secrets


docs: Update GoFrame V2 Adapter

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@hailaz plz sign CLA:

@hailaz plz sign CLA:

done

@hailaz plz fix conflicts:


update getting-started.md

Signed-off-by: yingbai<EMAIL_ADDRESS>
What this PR does / why we need it:
Update doc info for getting-started.md for default KUBEVIRT_PROVIDER version
Close previous PR #6129 and resubmit with dco-signoff
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

None

/assign @rmohr    I have updated the getting-started.md  with you and dankenigsberg's suggestion.


Remove greedy GPU scheduling logic

When the UCR transition is complete we need to remove the special greedy GPU resource handling.

New wrinkle. We have to be able to identify which GPU indices we have available in the case of other frameworks consuming GPUs as well. Imagine the scenario where we have Scale and Lame framework both wanting to run GPU jobs on a single node with 4 GPUs. Lame framework has already accepted a GPU offer and launched a task that consumes 1 GPU, just so happening to get GPU index #3. Now Scale comes along with a job that requires 2 GPUs. How is Scale going to know if it should use GPUs 1/2 or 2/3 or 3/4 or 1/3 or 1/4 or 2/4? We have no way to coordinate between framework which GPUs are being used. We could obviously query the node with nvidia utilities, but this will add a huge amount of latency. It would be much preferred to just request the number of GPUs over having to specify the explicit GPU ID. We should first investigate how DCOS UCR is handling that and attempt to replicate that behavior with nvidia-docker2. If not currently possible, lets reach out to nvidia-docker team about another way of specify GPU resource... maybe an enhancement request.


Minigrid environment

I was looking at the implementation of the minigrid environment as inspiration to create my own environment. I noticed that the correspoin efficient muzero config doesnt actually use the environment. In fact it can be removed entirely and efficient muzero runs normally. Is this intended ?

Hello, what exactly does it mean by "efficient muzero config doesn't actually use the environment"? Our configuration definitely uses this minigrid environment. Could you please provide more details about the issue? Thank you.


Be a little more Lazy

We have methods that return Xyz<Seq<...>, ...>.
These should return a Stream instead of other Seq implementations in order to avoid unnecessay computations.

I see some more opportunities where a Stream can be used instead of other implementations.
Ex : https://github.com/javaslang/javaslang/blob/master/javaslang/src/main/java/javaslang/collection/AbstractsQueue.java#L62
Can I refactor them here or should they go in another PR ? 😄

@ashrko619 please let's keep the scope of this PR focused on the methods that return wrapped Seq types.

I see some more opportunities where a Stream can be used instead of other implementations.

We should discuss these by creating issues first. I would not 'refactor' the example you mentioned. A queue is backed on two lists: rear and front.
It makes most sense to switch to a Stream return type when having costly operations that can be deferred by making them intermediate/lazy. In your example of the Queue (link above) the List is only used to iterate elements. Also making the whole Queue lazy makes not much sense in my opinion because the elements are already known (they are enqueued and dequeued). Lazy evaluation makes most sense when the elements are not yet known.

Fixed with #1605


removed watermark, added defaults to auto-update

Checklist

[x] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[x] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary.

Motivation and Context

Description

Why did you remove the watermark option?

It is an old feature that is not supported any more.
Here is the updated list: https://docs.testfairy.com/API/Upload_API.html
On Thu, Feb 8, 2018 at 8:58 PM, Jan Piotrowski<EMAIL_ADDRESS>wrote:

Why did you remove the watermark option?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/fastlane/fastlane/pull/11804#issuecomment-364213204,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGyX4I8FvjF9Qa0brG7J8pzXdzCfOxUwks5tS0PVgaJpZM4R-rdT
.


javax expression language not included with client jar

the javax.el api and implementation is required by the hibernate validator used in Genie common for bean validation. Originally we didn't mark the el (expression language) libraries as runtime dependencies since our target deployment (tomcat) provides them. People have complained saying new Genie client (2.2.0) won't run because they don't have these libraries in their non-Tomcat based applications. Will mark the jars as runtime in genie-common and then remove them in genie-web so that people who need them will get them but our web deployment won't have problems.

After further thought/review going to follow pattern set by Hibernate and leave it out. Most of our users run in a servlet/EE container. Will add a FAQ to the wiki for SE users.

Added FAQ to the wiki.


zip feature

It's possible to gzip the sql backup files?
Maybe as an option on the dockerfile like "ENABLE_GZIP": true
Thanks

Please!

looks like this guy has a solution https://github.com/olegabr/mysql-backup/commit/a2c77f1db76b8764575099dd23e33c247208df55#diff-1b0c2b516b83393edb7200ad5ff12181


when i use brave-instrumentation-dubbo-rpc, i find some error

Describe the Bug
hi, when i use brave-instrumentation-dubbo-rpc, i find some error.
there is my demo: https://github.com/zhaojigang/dubbo-demo

dubbo-demo-provider implements DemoService
dubbo-demo-provider2 implements  HelloService
dubbo-demo-consumer invoke DemoService and HelloService one by one

i think this invoke only can generate one traceId, but two.

and dependency picture is incorrect


Support assignment to attributes.

This PR adds support for assignment to an attribute x.y = z, in addition to the previously supported cases of assignment to a variable and assignment to a subscript.

CC @vinx13 @shingjan

@Lunderberg Could you add a test case for multiple assignment: x.y, z = 1, 2 or something like that

@tkonolige Currently, multiple assignment doesn't work in this PR for attribute assignment, for the same reason that multiple assignment doesn't work for subscript assignment in the main branch.  Both are handled in Compiler.compile_stmt by replacing the entire assignment with BuiltinOp.SubscriptAssign or BuiltinOp.AttrAssign.  The path handling multiple assignment requires that all assigned variables be synr.ast.Var instances, and doesn't allow for expressions that evaluate to assignable values during Transformer.do_transform.
import synr

def func_multi_assign():
    x, y = 1, 2

def func_multi_subscript_assign():
    x[0], y = 1, 2

def func_multi_attr_assign():
    x.y, z = 1, 2

for func in [
    func_multi_assign,
    func_multi_subscript_assign,
    func_multi_attr_assign,
]:
    try:
        synr.to_ast(func, synr.PrinterDiagnosticContext())
        print(f"Success: {func.__name__}")
    except RuntimeError as e:
        print(f"Failure: {func.__name__}\n{e}")

Output below.
Success: func_multi_assign
Failure: func_multi_subscript_assign
Parse error on line ./example.py:11:5:
    x[0], y = 1, 2
    ^
Left hand side of assignment (x in `x = y`) must be a variable or a list of variables (`x, z = y`), but it is <class 'synr.ast.Call'>
Failure: func_multi_attr_assign
Parse error on line ./example.py:15:5:
    x.y, z = 1, 2
    ^
Left hand side of assignment (x in `x = y`) must be a variable or a list of variables (`x, z = y`), but it is <class 'synr.ast.Attr'>


Implement Ranges in Timeline

Borrows from work mentioned here:
https://github.com/namespace-ee/react-calendar-timeline/issues/74#issuecomment-282667355

Does somebody know what's the status of the ranges feature? I read here somewhere that it should be converted into a plugin. Has this been done yet? If not is there a repo somewhere where I can jump in, maybe do a PR?

There's been no movement on this feature however I'm going to start on an approach soon that might replace the plugin system.  When I get around to it, I will post a roadmap issue and open things up for discussion.

This should be achievable via solution implemented in https://github.com/namespace-ee/react-calendar-timeline/issues/364

Released in 0.19.0


TORCH_USE_CUDA_DSA

python test_real_denoising_sidd.py
got this error:
RuntimeError: CUDA error: no kernel image is available for execution on the device
Compile with TORCH_USE_CUDA_DSA to enable device-side assertions.

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."


Create a function to capture the color in hexadecimal of selected x,y canvas coord

Create a function to capture the color in hexadecimal of selected x,y cavas coord
This function takes two parameters:
function getCoordHexColor(xAxis, yAxis) { }
This may return an hex color as string
OBS. Create a branch from existing road-draw branch
https://github.com/marcoshmendes/final-lap/tree/road-draw
Doc Reference
https://developer.mozilla.org/en-US/docs/Web/API/Canvas_API/Tutorial/Pixel_manipulation_with_canvas#a_color_picker

@Pe-Ferreira  can i count on you for this?

Sure, captain!

@Pe-Ferreira i can't see PR sir!


fix(deps): update dependency daisyui to v4.5.0

This PR contains the following updates:

Package
Type
Update
Change

daisyui (source)
dependencies
minor
4.4.24 -> 4.5.0

Release Notes

saadeghi/daisyui (daisyui)
v4.5.0
Compare Source
Features

added some Chinese translations (#2707) (c122353)

Bug Fixes

prose code fallback color for old browsers. closes: #2715 (0471a04)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.

Autoclosing Skipped
This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.


Seems like $scroll smooth is not smooth anymore?

It just snaps to the top of the page if I use this code:
$scroll(0, {behavior: 'smooth'})

Or this:
$scroll(0)

And that is on a very long page with a fixed back-to-top button, after clicking on it you snap back to top in an instant.

Thanks, can you post more details about which browser (including the version) you are using? The project hasn't been updated for 3 months.

Windows 10 Pro with Chrome 91.0.4472.164 (latest)

I tried the latest version of Chrome (92.0.4515.107) and it seems to work correctly. I'm a mac user but there shouldn't be any difference with chrome. Can you create a codepen to replicate the issue please? Thanks.
P.s. I think it also won't work if your OS is configured to disable the amount of non-essential motion. (https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-reduced-motion).
This is a specific user setting and it's not possible to ignore it.

P.s. I think it also won't work if your OS is configured to disable the amount of non-essential motion. (https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-reduced-motion).
This is a specific user setting and it's not possible to ignore it.

YES! You are right, never thought about that being a possibility. But indeed the culprit for me lies in the disabling of motion in Windows.


fix: Edit Task modal now retains edits to Cancelled date

Types of changes

Changes visible to users:

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

Internal changes:

[x] Tests (prefix: test - additions and improvements to unit tests and the smoke tests)

Description

When changing status type to CANCELLED, use the Cancelled Date as today instead of the Done Date.
Motivation and Context
Fixes #3089

#3089

How has this been tested?

running existing tests

this actually fixed two of the existing tests, not just the one that linked to the issue being fixed here

manual exploratory testing

Screenshots (if appropriate)
Checklist

[x] My code follows the code style of this project and passes yarn run lint.
[x] My change has adequate Unit Test coverage.

Terms

[x] My contribution follows this project's contributing guide
[x] I agree to follow this project's Code of Conduct

Hi @ilandikov, if/when you have time, could you review this please?

Feel free to resolve by yourself and merge =)

One more thing, should there be a test added to EditableTask.test.ts? At the end of the day, it's that class that changes the behaviour, and EditableTask.applyEdits() is tested, but not with regards to the changes in this PR

One more thing, should there be a test added to EditableTask.test.ts? At the end of the day, it's that class that changes the behaviour, and EditableTask.applyEdits() is tested, but not with regards to the changes in this PR

In an ideal world, probably yes - fair point.
However, I'm comfortable that the changes are covered in tests somewhere though - and feel I've spent enough time on this issue... If it fails again, we will find it.


Downgrade nodejs version from 18 to 16

Executing the bin/build-js.sh script shows a Deprecated-warning:
@Deprecated: You are using an incompatible Node.js version. Supported version range: ^16.0.0

Hi @M-arcus
Thank you for the pull request.
This global change doesn't fit to our current projects.
You might want to overwrite the setting within your own configuration.
In your devenv.nix file you copied from the example folder, you can add languages.javascript.package = pkgs.nodejs-16_x; to overwrite the original config.
Alternative, you can add a custom devenv.local.nix file to extend any devenv.nix file.
Does this work for you?

Thanks, this works.


company-box selection box opens in the wrong direction

Observed behavior
The completion box opens to the top covering the current line.

Expected behavior

Disabling company-box fixes the problem. But it no longer uses the childframes feature.

System information

Using haskell with +intero.

Click to expand

OS: darwin (x86_64-apple-darwin17.5.0)
Emacs: 26.1 (May 30, 2018)
Doom: 2.0.9 (develop f112a2a83f96bc7f887fa47f884aea3ae95ba901)
Graphic display: t (daemon: nil)
System features: JPEG RSVG IMAGEMAGICK NOTIFY ACL GNUTLS LIBXML2 ZLIB TOOLKIT_SCROLL_BARS NS MODULES THREADS
Details:elc count: 1
uname -a:  Darwin LF02Q331602A90M.local 17.5.0 Darwin Kernel Version 17.5.0: Fri Apr 13 19:32:32 PDT 2018; root:xnu-4570.51.2~1/RELEASE_X86_64 x86_64
modules:   (:feature (evil +everywhere) file-templates (lookup +devdocs +docsets) spellcheck (syntax-checker +childframe) workspaces :completion (ivy +fuzzy) :ui doom-dashboard doom-modeline evil-goggles hl-todo nav-flash neotree (popup +all +defaults) tabbar unicode vi-tilde-fringe vc-gutter window-select pretty-code :editor :emacs ediff electric eshell imenu term vc :tools gist macos make magit pdf tmux upload wakatime :lang (cc +irony +rtags) common-lisp clojure data erlang elixir elm emacs-lisp go (myhaskell +intero) javascript lua markdown nix ocaml (org +attach +babel +capture +export +present) perl purescript python rest ruby rust scala sh swift web :collab :config)
packages:  n/a
exec-path: (~/.cargo/bin/ /usr/local/bin/ /usr/bin/ /bin/ /usr/sbin/ /sbin/ ~/.gem/bin/ ~/.cargo/bin/ ~/.local/bin/ ~/bin/ ~/Library/Android/sdk/tools/ ~/Library/Android/sdk/platform-tools/ /usr/local/Cellar/emacs-plus/26.1/libexec/emacs/26.1/x86_64-apple-darwin17.5.0/)

I cannot reproduce this. This may be a MacOS specific issue; childframes appear to be less stable on MacOS than on Windows or Linux.

I'm not using doom-emacs, but I'm using a lot of ideas from both you and Spacemacs, and I am having some serious issues with child frames on my High Sierra computer, with company-box and my Emacs in fullscreen company-box keeps opening black windows on my computer and it's seriously annoying. I've had to disable it for now.

@zeronone Sorry for the late reply. Are you still experiencing this issue?

What is the version of emacs you use?
I had issue with tooltip not well displayed when using emacs-plus whereas it works fine with emacs-mac port

Sorry for late reply, I moved to emacs-mac port. It seems to be fine now.

Since this is an Emacs/MacOS that cannot be resolved from Doom (as far as I know), I'll close this thread. If you find any evidence to the contrary, please let me know here!


HTML import for Lodash

To create a HTML import for Lodash instead of using <script> tag as Polymer won't be able to deduplicate duplicated <script> tags which is why loading Lodash's script at top-level document.

No longer depend on Lodash. See commit 89777d38f287ef9571281c6a57d9bc04027543d9.


Change motor internals to better match ophyd

To ease in migration it would be good if the underlying signals in Motor had the same name as EpicsMotor. For example, user_readback in EpicsMotor is readback in Motor. We should go through and try and keep consistency unless there is a good reason to change the name.
Additionally, there are a number of parameters that are not exposed:

Limits (see https://github.com/bluesky/ophyd-async/issues/41)
Acceleration

I think I might have changed my mind that we need to keep internal signal names the same. It's only a minor change from ophyd

Discussed offline, attribute names should match as much as possible

It would also be good to add the fields we're missing in https://github.com/DiamondLightSource/hyperion/issues/1235


(WIP)Docs migration

This is for reference only while we're working on the docs_migration branch.

Waiting for CLA signature by @cwcowellshah
@cwcowellshah - We require a Contributor License Agreement (CLA) for people who contribute to Puppet, but we have an easy click-through license with instructions, which is available at https://cla.puppet.com/
Note: if your contribution is trivial and you think it may be exempt from the CLA, please post a short reply to this comment with details. http://docs.puppet.com/community/trivial_patch_exemption.html

CLA signed by all contributors.

CLA signed by all contributors.


Info editing tool for the schema.

This branch includes a python tool allowing to edit a file inserting new system defaults from the command line.
Thus a file created from the template or by the schema editor here:
https://www.vi4io.org/hpsl/addpage-tmp
can be exported to json, then modified with the tool, then read back.
A lightweight verification using the actual schema will be implemented.

Hi, I've now done enough for this project and will not update it further until it is discussed and there are specific requests.
It works sufficiently well to be discussed during our meeting.
One can add information for example by calling:
$ ./info-creator/io500_add_osinfo.py site.json
Example output on my system:
Site.Supercomputer.Nodes.name = kunkel-ThinkPad-X1
Site.Supercomputer.Nodes.kernel version = 5.4.0-58-generic
Site.Supercomputer.Nodes.Processor.architecture = x86_64
Site.Supercomputer.Nodes.Processor.model = Intel Core i7-7500U
Site.Supercomputer.Nodes.Processor.frequency = 2.7 GHz
Site.Supercomputer.Nodes.Processor.cores = 4
Site.Supercomputer.Nodes.distribution = Ubuntu
Site.Supercomputer.Nodes.distribution version = 20.04
Site.nationality = GBR
The updated site.json can then be uploaded to the webpage and changed/edited there.

Hi, I've now done enough for this project and will not update it further until it is discussed and there are specific requests.
It works sufficiently well to be discussed during our meeting.
One can add information for example by calling:
$ ./info-creator/io500_add_osinfo.py site.json
Example output on my system:
Site.Supercomputer.Nodes.name = kunkel-ThinkPad-X1
Site.Supercomputer.Nodes.kernel version = 5.4.0-58-generic
Site.Supercomputer.Nodes.Processor.architecture = x86_64
Site.Supercomputer.Nodes.Processor.model = Intel Core i7-7500U
Site.Supercomputer.Nodes.Processor.frequency = 2.7 GHz
Site.Supercomputer.Nodes.Processor.cores = 4
Site.Supercomputer.Nodes.distribution = Ubuntu
Site.Supercomputer.Nodes.distribution version = 20.04
Site.nationality = GBR
The updated site.json can then be uploaded to the webpage and changed/edited there.

So the next logical step would be to add an info_editor/io500_add_lustre_info.py script that would extract available information from the client, and/or from the server if it was run there?  My Python-fu is very weak, but I might be able to cargo-cult enough code from one of the other scripts to extract information from Lustre.  Failing that, I could at least generate a list of "how to get this input -> schema field" mappings so that it could be added.

So the next logical step would be to add an info_editor/io500_add_lustre_info.py script that would extract available information from the client, and/or from the server if it was run there?  My Python-fu is very weak, but I might be able to cargo-cult enough code from one of the other scripts to extract information from Lustre.  Failing that, I could at least generate a list of "how to get this input -> schema field" mappings so that it could be added.

What is a bit strange is that it has marked me as "adilger approved these changes" but I only gave approvals to a subset of the patches.  I don't use Github much, so I don't know if that is working as expected.

What is a bit strange is that it has marked me as "adilger approved these changes" but I only gave approvals to a subset of the patches.  I don't use Github much, so I don't know if that is working as expected.

Thanks @adilger for the improvements. It is better.

I think it is best to create a new repository and outsource these tools to be more agile and allow externals to collaborate. Given that this is a contribution by VI4IO relevant for IO500 and the CDCL, I think it is well placed there.


Drawfile rendering crashes if CPU is in ARMv7 Strict mode

To reproduce:

In !Boot, set the CPU mode to ARMv7 Strict
Start ClearView
Drop the "QuickGuide.SmManual" example onto ClearView
Click "Next topic" (first toolbar button)
ClearView crashes (data abort)

The abort address is inside RISC_OSLib's Drawfile handling code.

This is caused by a bug in RISC_OSLib. Sprow has provided a fixed RISC_OSLib, see https://www.riscosopen.org/forum/forums/1/topics/15189#posts-101060
This works as a workaround, for now

Keep this open until we have confirmation that RISC_OSLib has been patched.

ROLib has been fixed in the ROOL CVS but will leave this open until the next version of the C compiler lands in my inbox -- hopefully with ROLib fixed.

Confirmed fixed in DDE29c


Arbitrary selector names in devtools

I'm submitting a feature request

Library Version:
0.1.14

Browser:
Chrome 54 & Firefox 49

Current behavior:
CSS selector names like "styles.some-descriptive-selector-name" are converted by Aurelia UX to arbitrary names like ".node_au_ux_12" and ".base_node_au_ux_13", and these are what's shown in the browsers' devtools. (In the above browser versions, at least)
Expected/desired behavior:
It would be better if Aurelia UX were to keep the selector names as close to the original as possible.
For example, the above CSS selector could be converted to something like ".au-ux-some-descriptive-selector-name", adding a number prefix/suffix if the class name is not unique.

We can change the format of the name, but we do need to always attach a unique id onto it since we cannot assume there isn't foreign css on the page (or another instance of the same app) that might conflict.

I'm sorry - I just realized this already works correctly. (node & base_node were my selector names - I'm not sure how I missed this before)


Check wording in image.sh.

The wording appears to be off in the file ~/adsb-receiver/bash/image.sh when selecting a MySQL remote database installation.

Mirrored setup steps and questions pertaining to the advanced remote MySQL setups to that found in ~/adsb-receiver/bash/portal/install.sh.


Can't sign in with android

Hi.
Thank you for the android version, I was waiting for it!
Unfortunately, I can't pass the sign in step.
The click on button doesn't do anything.
I'm on Samsung Galaxy s6, android 7, official rom.
If I can help you with some logs, I'll be glad to.
Thanks for your work.
Matt'

@mathieutu cross checked on my android and it works. When you click on the sign in button it opens up the browser rather than using the in app web view (an improvement I will suggest in the coming days). So I guess the browser isn't firing up. Do you have the latest chrome installed on your phone? If yes you can clear Chrome's cache, force-stop it and retry after few minutes. Let me know if that works or not :)

Hi! I was able to sign in from my Android device. I would try also with another browser and make it the default to check if it is a browser thing or from the app. It may help if some else has the issue. I'm on Android 7.1

Thank you so much @AndonyNS @introwit :)
Thank you @mathieutu - we're so happy to have the Android version finally released as well! I can't reproduce the issue as well however- it's the sign in button on the onboarding swiper screens that doesn't seem to do anything correct? Let us know if changing the default browser on your device works, if it doesn't don't worry we'll figure out what's going on.
Will appreciate it if any other Android users who experience anything remotely similar to let us know as well!

Yes this is this button.
I have Firefox last version.
I'll try to change it and re test (but anyway, I shouldn't do that for a normal use).

Ok, I've found it.
When I remove Firefox from default browser, the signIn redirected me on another git app I had on my device (fasthub), and its internal browser. I wasn't able to press the github "authorize" button (stay deactivated).
I've uninstalled it, and now when I press signIn, I'm going to firefox, and no problem to signIn.
I've re setted Firefox as the default browser, and no problem.
I think that as @introwit said, the in app web view is really needed to avoid theses conflicts..

Thank you @mathieutu, apologies for the struggle needed to solve this problem :(
Going to prioritize that ticket and make sure we have that implemented soon. If no one picks it up sooner, it'll be the next thing I work on.
Will close this ticket as we have that one to reference the problem. Thanks again for logging this mate 🙌


Examples missing documentation

We now have two examples, but it is not quick to see what each of them does. All example files should have initial (class) documentation that explains what happens and what the main features are that one can see from this. It should also be mentioned which vlog4j modules are required to be loaded for this.

done


Port multiple queries for view test from .NET

During test fest, we saw a stale query using Android 1.4-44 (ForestDB). Upon investigation, we saw that multiple queries were created for the view. After fixing the sample app to only create on view, the issue went away.

.NET unit test TestMultipleQueriesOnSameView
https://github.com/couchbase/couchbase-lite-net/blob/master/src/Couchbase.Lite.Tests.Shared/ViewsTest.cs#L2136

PR: https://github.com/couchbase/couchbase-lite-android/pull/1079

The issue is not reproducible by the ported unit test.


UAT: Ability to delete files permanently

There are times when a PDF is generated during a draft process like in order or application creation or in case e-filing, we may generate a few PDFs as the file goes back and forth between scrutiny.
need to clearly call out if all PDFs need to be stored or there are some files that can be deleted.
For deletion, need to upgrade the filestore platform service
cc @subhashini-egov @suresh12

Closing this ticket as duplicate #1924


[DVSPIMP-2786] Dockerization.

This is a link to recorded video https://drive.google.com/file/d/192hNlDCUOO4BmHiOw21fO1snGIQ09qxS/view?usp=sharing

Coverage remained the same at 44.864% when pulling 56e7e85200b8608594da51166f27888588213651 on trilogy-group:feature/dockerization into ad49dacb29f6b9dab22171af9da92e9b44abf909 on jlfwong:master.

Hi! I, uh, don't really know what this is? It seems like a dockerized development environment for speedscope?
I'm also not sure if this was targeting the wrong branch? Was this just accidentally targeted to upstream instead of your fork? I see https://github.com/trilogy-group/speedscope/pull/1 is still open?
It looks like there's probably no action required here on my part -- is that right?

Hi Jamie,
Sorry about that. We hit the wrong fork.


nixos/x11: create xkb option by default

without this
nix-repl> nixosTests.xfce.nodes.machine.services.xserver.xkb
error: The option 'nodes.machine.services.xserver.xkb' is used but not defined.

with this
nix-repl> nixosTests.xfce.nodes.machine.services.xserver.xkb
{ dir = "/nix/store/096yg7fc67py86w0bm6g7a32npgyh5ic-xkeyboard-config-2.39/etc/X11/xkb"; layout = "us"; model = "pc104"; options = "terminate:ctrl_alt_bksp"; variant = ""; }

Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Is there any use to this being a submodule? The options could have just been prefixed with xkb.
I mean, like in here.

Is there any use to this being a submodule? The options could have just been prefixed with xkb. I mean, like in here.

No reason, I think we both just forgot that was possible.
https://github.com/NixOS/nixpkgs/pull/260975

Is there any use to this being a submodule? The options could have just been prefixed with xkb. I mean, like in here.

No reason, I think we both just forgot that was possible.

Not so much forgot as never knew that was a possibility. Maybe the docs should be updated to reflect that this should be the default way to group options when there are no options at the top level?
Thank you both for helping and clarifying!


How to Simplify Geometries at Lower Zoom Levels and Use Full Detail at Higher Zoom Levels?

Goal:
At lower zoom levels (e.g., zoom levels 0-4), I want to display countries using highly simplified geometries to ensure that the tiles are very small in size.
At higher zoom levels (e.g., zoom levels 5 and above), I want to progressively include more detailed geometry, eventually using the full detail available in the source data.
Could you please provide guidance on how to set up Tippecanoe to achieve these goals? Any specific commands or examples would be greatly appreciated.

You should be able to lower the tile resolution and raise the simplification level at low zooms, while retaining full detail at maxzoom. For example:
tippecanoe -zg -f -o out.mbtiles --no-simplification-of-shared-nodes --no-tiny-polygon-reduction --low-detail=9 --simplification=3 --full-detail=12 --simplification-at-maximum-zoom=1 tl_2022_us_county.json

to create highly simplified, low-resolution tiles at lower zoom levels, while retaining full detail and normal simplification at maxzoom.
The --no-simplification-of-shared-nodes and --no-tiny-polygon-reduction options are to reduce the artifacts that would otherwise be visible in oversimplified and low-resolution tiles, respectively.

Thank you for your help with my previous queries!
tippecanoe -Z0 -z4 --projection=EPSG:4326 -l land \
    $INPUT_PATH/land.geojson -e $LOCAL_SERVER --force --no-tile-compression \
    --visvalingam --low-detail=11 --full-detail=11 --simplification=2

The problem now is that there are a lot of small polygons. For zoom level 0, these are not relevant, they just increase tile size.

My goal now is to remove the small polygons based on size at low zoom levels. I successfully used --drop-smallest-as-needed along with --maximum-tile-bytes=20000 to filter out small polygons at zoom level 0. However, I would like to remove polygons below a certain polygon size threshold (e.g., less than 4 pixels) across different zoom levels, not just based on tile size.
I have tried to use  --drop-polygons -r 1.6 but, it seems to remove large polygons, not small ones.
Could you advise on how to effectively remove these small polygons?
Thank you for your guidance!


How to change color range of heatmap chart

This is a great plugin, I just wanna know if there is any easy way to change color range of heatmap? For example, the lowest value will be red, and highest value should be green.
Thanks.
Best Regards,
Kenny

I have exactly the same question as the previous one, is there a way to select red, yellow, green cell backgrounds?
Thanks in advance, Mike

Hi Mike,
I need to upgrade this plugin then, let me find sometime to do it.
Currently it won’t support changing the map chart background.
On Tue, 14 Mar 2023 at 3:14 AM, mikedavidson1959blue <
@.***> wrote:

I have exactly the same question as the previous one, is there a way to
select red, yellow, green cell backgrounds?
Thanks in advance, Mike
—
Reply to this email directly, view it on GitHub
https://github.com/tkarkuvelraja/heat_map_chart_apex_plugin/issues/1#issuecomment-1467006732,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUKVGE6UXIVLL2LZP4B5QM3W36IL5ANCNFSM5B5L3O5A
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***
com>

--
Regards,
Karkuvelraja Thangamariappan,
+971 582036853


Add WebAppCreateStep

Based on https://github.com/microsoft/vscode-azuretools/pull/625
Should be mostly copying code with no functional differences.

🙇


Multiple Scopes Per Resource does not work with Basic Auth

Description:
Multiple scopes are not taken into account when validating using BasicAuthAuthenticator.
Need to fix reading multiple scope attachment per resource from local entry swagger for both REST APIs and GraphQL APIs.
WSO2 API-M 3.2.0-RC1

Fixed with https://github.com/wso2/carbon-apimgt/pull/9118


Connecting to node

When connecting to a node as a producer, change the text when clicking on a node on the map from "Add node" to "Connect to node"

After talking to Albin we're decided to continue with add / remove since it's more commonly used.


Merge happened but did not show logo or Token name, Changed Token address and coin from Koin

Please note: This repository is being rebuilt to accept the new volume of token additions and modifications. PR merges will be delayed.

I agree to not ping anybody on Discord/Twitter/email about this pull request. Instead I will inquire by posting a new comment in the pull request if needed.

PRs are reviewed in bulk and and can take up to two weeks to be merged.
This repository is managed using an auto merge action. Please ensure your PR has no deleted lines, and it will be merged.
Please provide the following information for your token.
Please include change to the src/tokens/solana.tokenlist.json file in the PR.
DON'T modify any other token on the list.
At minimum each entry should have

Token Address:
Token Name:
Token Symbol:
Logo: (logo should be uploaded under assets/mainnet//*.<png/svg>)
Link to the official homepage of token:
Coingecko ID if available (https://www.coingecko.com/api/documentations/v3#/coins/get_coins__id_):

Auto merge requirements
Your pull request will be automatically merged if the following conditions are met:

Your pull request only adds new tokens to the list. Any modification to existing
tokens will require manual review to prevent unwanted modifications.

Your pull request does not touch unrelated code. In particular, reformatting changes to unrelated
code will cause the auto merge to reject your PR.

Any asset files added correspond to the token address you are adding. Asset files
must be PNG, JPG or SVG files.

Your change is valid JSON and conforms to the schema. If your change failed validation,
read the error message carefully and update your PR accordingly.

No other tokens shares the same name, symbol or address.

For example, this change would be rejected due to unrelated changes:

The bot runs every 60 minutes and bulk-merges all open pull requests to prevent conflicts.
This means that you need to wait up to 60 minutes for your pull request to be merged or reprocessed.

I have the same issue of it not showing the name and logo.

Please tell me if you managed to solve this!


Search engine shortcomings

Team, the new search is only partially useful as it has lost the ability to take you the exact location within the page as the old page search used to do.
What we need is to add additional functionality so once the link is clicked on the results pop-up, the new page is opened and scrolled to the location of the first instance. Otherwise, you still have to do a page search to find the exact location. Which defeats the purpose of a search engine.  Ideally, there would also be a next button  so you can scroll trough all of the found instances within the page... as any standard search would...
**Also I find the search results to be wrong at times. For example if you go to http://docstrap.github.io/docstrap/themes/cosmo/index.html and search for 'gus', 2 results will come back to pages that do not have any occurrences of gus in them. Why is this happening?
**
Lastly, it would be nice to search for sentences instead of random words within a page. For example, if I search for 'The code is wrong' ( note I put I quote marks around the sentence) I would want to get instances of that exact complete sentence. But if you search for the same without quotes around them, then it would be the current functionality.

The search was user contributed and I patched it up - we use another package to help us search so maybe this is possible - you are welcome to make a pull request.

Thank you
On Fri, Apr 22, 2016 at 12:50 AM, Luke Page<EMAIL_ADDRESS>wrote:

The search was user contributed and I patched it up - we use another
package to help us search so maybe this is possible - you are welcome to
make a pull request.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/docstrap/docstrap/issues/205#issuecomment-213254269

--
Thank you,
Gus Matlis
ChartIQ


Install fail

I'm getting dependency conflicts when installing (fresh install) the client modules:
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@wagmi/core
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   client
npm ERR<EMAIL_ADDRESS>npm ERR!     node_modules/@sac/interface
npm ERR!       workspace client from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR<EMAIL_ADDRESS>npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   client
npm ERR<EMAIL_ADDRESS>npm ERR!     node_modules/@sac/interface
npm ERR!       workspace client from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/kipling/.npm/_logs/2023-07-29T02_33_43_473Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/kipling/.npm/_logs/2023-07-29T02_33_43_473Z-debug-0.log

Also, a readme in the client dir would be a good starting point

nvm, looks like it's yarn
A readme would be good tho

Thanks for filing this. I should have some better docs and filed a n issue for it: #2


No active hosts found

With 3 docker machines "running" the docker-machine ls command does not list any of the docker machines as active. Also ran the following command:
eval $(sudo docker-machine env default)
The machine name is used instead of 'default'.
The following command outputs "No active hosts found"
docker-machine active

Thanks for the issue.  Please don't sudo docker-machine.  Machine is not meant to be invoked as a superuser.  Environment variables, path, etc. change between users and that may explain some of the issues you're seeing.

But even without "sudo" same issue.

So, even if you run:
$ eval $(docker-machine env)
$ docker-machine ls

No hosts show up as active?  What's the output of env | grep DOCKER in this case?

Thanks. Running the docker-machine commands without 'sudo' fixed the error and active host gets listed.
But, had to run  docker-machine as 'root' user with sudo -i
Not documented, docker-machine is to be run as 'root'
On Tue, 3/1/16, Nathan LeClaire<EMAIL_ADDRESS>wrote:
Subject: Re: [machine] No active hosts found (#3126)
To: "docker/machine"<EMAIL_ADDRESS>Cc: "dvohra"<EMAIL_ADDRESS>Received: Tuesday, March 1, 2016, 11:38 AM
So, even if you run:
$ eval $(docker-machine env)
$ docker-machine
ls
No hosts show up as active?  What's the output of
env | grep DOCKER in this case?
—
Reply to this email directly or view
it on GitHub.

Thanks. Running the docker-machine commands without 'sudo' fixed the error and active host gets listed.
But, had to run  docker-machine as 'root' user with sudo -i
Not documented, docker-machine is to be run as 'root'

I can confirm that with Docker version 1.11.2, build b9f10c9, no hosts show up as active and env | grep DOCKER outputs nothing.  I never ran docker-machine with sudo, always as my own user.

As suggested, run as sudo.

@dvohra I was confused by the documentation and cli output, I hadn't run eval $(sudo docker-machine env default).  When I ran that (without sudo), docker-machine active worked.

@dvohra I'm guessing the problem is that your actual machine was still running as root?  I would assume if you blow it away and run all the commands again with sudo then everything should work...

Either as root user or with sudo is fine.


Remove compile-time configuration options

Fixes #93
Configuration struct:
I have created a configuration struct. It's not opaque, we need to discuss this. I don't believe it has to be opaque necessarily.
The configuration struct is copied on csp_init, and shared to all csp modules through a global csp_conf symbol declared in csp_init.h. We could perhaps eliminate the use of a global if we wish. It would require internal functions in csp_conn_innit() and friends to take more arguments.
Allocations:
Generally i have replaced all static allocations with one-time calls to calloc/malloc.
Note: This was just my quick fix for this. I believe it could be made prettier with some love. Also i think we should update documentation and such.

I think the major version should correspond to the protocol header, not the API. So all csp 1.x is compatible and so forth.
In almost every release we have had minor API changes, this however affects everybody. But considering we only release once every year or two, i think it would be okay to go with just version 1.5.

The data structure should be static, not const.
static csp_conf_t csp_conf;
// get default shouldn't touch the actual csp_conf data
csp_conf_get_default(csp_conf_t * conf)
{
conf->xx = something;
}
int csp_init(const csp_conf_t * conf)
{
csp_conf = *conf; // make copy
}
const csp_conf_t * csp_conf_get(void)  // const provides read access, but prevents/warn about write access
{
return &csp_conf;
}
This provides support for bettes module programming, where one part of the software can initialize csp with address, model, revision etc. and another (generic part) can read for some purpose, printf("revision: %s", csp_conf_get()->revision).

From: Johan De Claville Christiansen<EMAIL_ADDRESS>Sent: Wednesday, August 16, 2017 10:09:27 PM
To: libcsp/libcsp
Cc: Per Wulff; Comment
Subject: Re: [libcsp/libcsp] Remove compile-time configuration options (#98)
@johandc commented on this pull request.

In src/csp_init.chttps://github.com/libcsp/libcsp/pull/98#discussion_r133553489:

+#include "csp_conn.h"
+#include "csp_qfifo.h"
+#include "csp_port.h"

+#include "csp_init.h"
+
+csp_conf_t csp_conf;
+
+uint8_t csp_get_address(void)
+{

  return csp_conf.address;

+}
+
+int csp_init(csp_conf_t * conf) {
+

  /* Make a copy of the configuration

It cannot be a const if the csp_conf_get_default() function may modify it. Also a const csp config cannot be changed at boot time, for example to set the csp address or any other parameter.
csp's internal configuration is a static already, but it's only exposed to those who include csp_init.h. And csp_init.h is only available in the src folder of CSP. So yes, we actually don't allow the user to get the configuration from CSP. However, the application should be able to get the same information as was put into csp from the same source (i.e. defines or the parameter system).
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/libcsp/libcsp/pull/98#discussion_r133553489, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ATzzRE-YtOX4uflPVHj9N5dKlxVO9nxSks5sY0x3gaJpZM4Otib8.

Yes, disregard that reply. I found out what you meant after sending it, so i changed it back on github, but it still arrived at your inbox....
I have factored in your comments in two small commits.
The internal variable in csp is still not static, so it can be shared with other internal csp modules through csp_init.h - I think that's just easier as long as we ensure csp_init.h is not exported.


The name of game on cards not visible

Description
The name of game on cards is behind the content which is not clearly visible i would like to work on it
Screenshots
No response
Additional information
No response

Already assign to someone.


question for fine-tune model on another dataset

❓ Questions and Help
May I ask that when fine-tuning a pretrained model (say faster R-CNN) on another dataset, which metric should be monitoring most in order to tune the learning rate. Is that total loss or other individual loss? Will the /tools/train_net.py output a loss curve? Thanks a lot!

The total loss is a good proxy, but overall what you ultimately want is the mAP on the validation set.
tools/train_net.py outputs the losses in a text file, you'd need to parse it or adapt the code to plot straight away to TensorBoard / Visdom / etc.
tools/train_net.py will store model checkpoints every x iterations, you can evaluate the quality of the checkpoint on the validation set using tools/test_net.py.


chat seems to hang when installed with pipx

Turns out on Mac there's another command line utility called chat, so it's a name clash. What hangs is that chat utility, not our script... So we'll have to rename it to something more unique.


Fix the top-k such that the jax and numpy implementations are equivalent

I have been adding testing to the Farama foundation jumpy fork, https://github.com/Farama-Foundation/Jumpy and found that the top-k jax and numpy implementations are not equivalent.
The jax (and tf) implementations return an ordered top-k and indices.
This PR makes the top-k function equivalent for numpy and jax
@pytest.mark.parametrize(
    "x, k, ret",
    [
        (jp.array([5, 7, 1, 2]), 2, ([7, 5], [1, 0])),
        (jp.array([5, 9, 7, 1, 2]), 3, ([9, 7, 5], [1, 2, 0])),
        # Jax array
        (jp.array([5, 7, 1, 2], dtype=jnp.int32), 2, ([7, 5], [1, 0])),
        (jp.array([5, 9, 7, 1, 2], dtype=jnp.int32), 3, ([9, 7, 5], [1, 2, 0])),
    ],
)
def test_top_k(x, k, ret):
    """Checks if the result of `top_k` on the given inputs equals the expected output."""
    top, indices = jp.top_k(x, k)
    assert len(top) == len(indices) == len(ret[0]) == len(ret[1])
    assert onp.array_equal(top, ret[0])
    # Checks that the index values in x are equal to the top values.
    assert all(t == x[i] for t, i in zip(top, indices))

Good catch - thanks for fixing this!


custom_unlocked_appearnces

looks like there is a table missing, and there is no respect sql in update folder

That table is added by the transmog module. Did you compile with that module as well?

That table is added by the transmog module. Did you compile with that module as well?

Yes, Thank you for enlighten me, I forgot modules sql, I applied sql provided by the module and now it runs fine, please close this issure.


Add zstd library

The graphics dumps and memory dumps compress extremely well and very quickly with this library.

Takes 0.5 seconds to compress graphics dumps from ~18 MB to 5 MB.
Takes 0.6 seconds to compress 128 MB main memory dump to 7.3 MB.


Loop not working on audio elements.

As per @modulesio  - "ok loop key looks like it's not routed from the element to to the backing context"

On the JS side the entry point is here: https://github.com/webmixedreality/exokit/blob/master/src/DOM.js#L1722
This is supported by our bindings: https://github.com/webmixedreality/exokit/blob/master/deps/exokit-bindings/webaudiocontext/src/Audio.cpp#L159 (and also suported by WebAudio)
I remember using this, so this is a regression -- on the JS bindings/DOM side.

Related: https://github.com/webmixedreality/exokit/issues/678


Move this repo's CI to GitHub Actions

Our Travis-CI ran out of quota, no builds will be run any more for now: https://travis-ci.com/github/casbin/casbin-website

Builds have been temporarily disabled for public repositories due to a negative credit balance. Please go to the Plan page to replenish your credit balance or alter your Consume paid credits for OSS setting.

@closetool

@hsluoyz can I work on this issue ?

Fixed by: https://github.com/casbin/casbin-website/commit/f368c511ba6aff8ab515ac2862ef1b0bb6eae224


Parameter settings in AffineRegularizationLoss function

Hi, Thanks for sharing the code!
I have a few questions on the implementation of the AffineRegularizationLoss function. It seems the prediction of the optical already contains the identity mesh grid, and coordinates are normalized to [-1, 1]. so the flow warping process is directly applying the F.grid_sample function on the image or the feature maps.
For the AffineRegularizationLoss function, in line 222, the losses.py,
https://github.com/csyxwei/FFWM/blob/d42c578cabe1b81c6b1bb0c3cb707b190fca3c68/models/losses.py#L222
It seems the mesh grid should be re-normalized back to the range of [h,w]. So I wonder, why the parameter of tensor.mul() should be 128.0.  I mean, for flow field flow128, it should be ok, but for different sizes of the flow fields, say,flow64 and flow32, the number should be different? Is that right? or is it the intended case?
Thanks a lot! :)

Hi,
You are right. For different sizes of flow fields, the number should be different, i.e., 64  for flow64 and 32  for flow32.  Thanks for pointing out this error!  The code should be:
b, c, h, w = flow_field.size()
grid = flow_field.add(1.0).div(2.0).mul(h)

By the way, as the AffineRegularizationLoss constrains transformation between the source coordinate matrix  and target coordinate matrix is an affine transformation,  multiplying a coefficient to the target coordinate matrix (128) does not conflict with it. This error will not affect the training of FlowNet.

Thanks for the prompt reply and clarification, I will close this issue.
Thanks a lot!


Switch default branch to main

As of #345 Hound has support for default branches other than master. It makes plenty of sense that Hound itself set its default branch to main.

A lot of repositories still use master as default branch and I would imagine some of them will still keep it. Could hound maybe support both? I.e. for new repos and those whose owners renamed default branch to main but also older repos which for any reason have not renamed the master to main?

A lot of repositories still use master as default branch and I would imagine some of them will still keep it. Could hound maybe support both? I.e. for new repos and those whose owners renamed default branch to main but also older repos which for any reason have not renamed the master to main?

Hey @arne-rusek, this issue is specifically about the hound repository itself. This repo's default branch should be main. Hound itself currently supports any name of default branch, and should be able to auto-detect the default branch name of most git repos.

Hey @arne-rusek, this issue is specifically about the hound repository itself. This repo's default branch should be main. Hound itself currently supports any name of default branch, and should be able to auto-detect the default branch name of most git repos.

Hey @arne-rusek, this issue is specifically about the hound repository itself. This repo's default branch should be main. Hound itself currently supports any name of default branch, and should be able to auto-detect the default branch name of most git repos.

Oh, I did not read the description properly, thank you for explanation.

Hey @arne-rusek, this issue is specifically about the hound repository itself. This repo's default branch should be main. Hound itself currently supports any name of default branch, and should be able to auto-detect the default branch name of most git repos.

Oh, I did not read the description properly, thank you for explanation.

No worries, it's worded a bit confusingly.

No worries, it's worded a bit confusingly.


Concurrency 1 only maintened 15 minutes

A throttling strategy is set to concurrency 1
Sidekiq::Throttled::Registry.add(:big_parser, concurrency: { limit: 1 })

With multiples workers using this strategy
class UpdateCatalogDailyWorker
  include Sidekiq::Worker
  sidekiq_options backtrace: 4, retry: false
  include Sidekiq::Throttled::Worker
  sidekiq_throttle_as :big_parser

  def perform
  end
end

When I run many jobs the no-concurrency is maintained only for 15 min

default lock ttl is 15 minutes. Increase it tobe bigger than your jobs are taking:
Sidekiq::Throttled::Registry.add(:big_parser, concurrency: { limit: 1, ttl: 1.hour.to_i })

hey Ixti, from what I noticed, even once the job is done, it will not pull in another job until the ttl is done. Is there a way to lock for either: job is done or 1 hour (whatever is shorter)?

@erated Are you sure you are referring to concurrency throttling? As what you describe is a behaviour of threshold throttling.

@ixti I found this after 2 days of googling and stuff. Please have it somewhere in readme. Thanks

This is vital information.  Found it after noticing my production jobs were not respecting concurrency.  +1 to add to the README.

@kjvarga totally open for PRs on improving documentation


Formatter breaks with 2 has clauses

Ran into this while defining set. This will cause the formater to fail:
Set k := Dict.Dict k {}
    | k has Hash & Eq
     has [
         Eq {
             isEq,
         },
     ]

This syntax is no longer supported

Thanks for checking @JRI98 :)