V10 thursday updates

responsive homepage
remove layer page and related components
remove color in ui page

Thanks @asudoh! waiting on an updated homepage image to merge this one in.


fix: Crash if WebView is disabled

Summary

When the webview is updated by play store, all apps that has loaded webview gets killed. For background see https://issuetracker.google.com/issues/228611949?pli=1
We have a long-running app and don't want this to happen and while we are not using webview anywhere, we are using websockets that loads it for reading cookies, however we are not using cookies to authenticate the websocket and thus want to disable the webview to avoid loading it unnecessarily and then getting killed unnecessarily.
The webview has support for beeing disabled https://developer.android.com/reference/android/webkit/WebView#disableWebView() however as-is this crashes React Native. It seems to me like this case is very similar to not having web view installed and should be handled in the same way.
Changelog

[Android] [Fixed] - Avoid crash in ForwardingCookieHandler if webview is disabled
Test Plan

Add WebView.disableWebView(); as the first line in MainActivity.onCreate.

Hi @Pajn, thanks for the PR. Could you please rebase on main? We should have fixed the CI issues.

Sorry, my additions skipped the earlier nullcheck. It should be correct now.


Add a collection to the index

Collection name
abc
Maintainer name
brigit
Maintainer contact link (i.e. repo issues link, email)
github.com
Repository URL
github.com
OCI Reference
testref
I acknowledge that this collection provides new functionality, distinct from the existing dev container collections part of this index

[x] Confirm

#sign-off

test

#sign-off


Fixed error while using slave_display_name (was ignored)

Setting the display name using "slave_display_name" did not work here. The following fix solves this.

If you want to merge both, #26 & #27 i can also create a pull request from my master branch, which includes both fixes.

Ok, so I've merged the other one. Could you please rebase to master so that I can merge this one?

Rebased fix_display_name to master. You should be able to merge now.

thanks!

That was fast ;). You're welcome.


Remove sda and scl configure from initialize_platform()

sda.configure() and scl.configure() need to removed from stm32f103c8 platform file once libhal/libhal-soft#36 is resolved

Resolved by #6


Supports ES7 (specificially async/await) features?

I doubt Needlepoint supports async/await because of this:
http://stackoverflow.com/questions/36243840/babel-transpile-getting-arguments-from-outer-function
am I wrong?

I haven't tested it, but you're probably right about it not working. I'll look into adding support.

I am working on the same problem - let me know if you have any good insights. They way I have "solved" it, is in my API, if it's an async/await function, I know that only one param will be passed to it, so I just injected that one param as the only argument. This is of course works, but it's a special case of working; maybe you can come up with something better.


jenkinsfile fixes

Changes

fix docker push command
add post stage that notifies slack channel on unsuccessful builds

Deploy preview for docsdocker ready!
Built with commit ddfc403da2f91c99d53dcf092b82347499b366f9
https://deploy-preview-9399--docsdocker.netlify.com


add Plausible tracking

We need to add the Plausible tracking snippet to the <head> of the landing page:
<script defer data-domain="sheepdog.run" src="https://plausible.io/js/script.js"></script>

I don't know how to do that in Astro…

We need to add the Plausible tracking snippet to the <head> of the landing page:
<script defer data-domain="sheepdog.run" src="https://plausible.io/js/script.js"></script>

I don't know how to do that in Astro…

Shouldn't we also add some kind of client Id for main matter?

no, that's all


[BUG] Investigate multiple calls to cudf::rolling_window() from GpuWindowExec

This was noticed tangentially, when investigating cudf/pull/7568.
The minimal  test-case that reproduced the libcudf issue above consisted of a 0.5KB Parquet dataset containing 15 records across 5 groups.
grouped_rolling_window() seemed invoked once per group, instead of once for the entire column, likely in a bid to keep groups whole. If groups could be packed into larger inputs for grouped_rolling_window(), the performance should be far better.

@mythrocks Is this still relevant?

@mythrocks Is this still relevant?

We could save some time in building the full offsets that are passed to the underlying window operations.

Sorry I missed this.
I didn't actually see a slowdown, just that there seemed to be multiple calls coming through.
I can close this issue for now, and reopen if we find a slow path here.

I want to keep it open because we know that there is duplicate code being called. It may be small, but I want to preserve this because at some point we are going to want to go through the backlog and start fixing things there.  Just unassigned yourself from this for now.


Can't find ores

What datapack(s) do you have installed (including ones made by me- include version if possible).
https://lunus.xyz/VVICBf.png

Run /reload. Copy/paste or post a screenshot of what appears in chat (should say [Loaded  ]).
https://lunus.xyz/BYp4cd.png

What environment are you running the datapack? (Vanilla single player, Vanilla multiplayer, Forge, fabric, spigot, bukkit, paper, optifine, realms, etc). Please specify exact Minecraft version as well.
Vanilla Single Player 1.15.2 (Using Buffet Sky Islands Plains World Type)

What if happening vs. what you expect to happen?
Ores aren't spawning even after searching for a reasonable amount of time and normal Minecraft ores are spawning fine.

The generator is not designed to be run with sky island type maps in the overworld. I may add this feature at some point in the future.


Merge conflicting migrations

I think we have two db migrations committed that had the same parent
migration, which caused a problem when applyin the update. Running
alembic merge heads seemed to fix it.
https://stackoverflow.com/a/51456404/324921

this will be in my PR forthcoming in a few mintues.


Rename request body min rate APIs (#1901)

#1901

Reverted 5c63a585a66368c2c232602c6147d8b26e347786 to stop the bikeshedding
Moved MinimumDataRate to the base Core namespace so people don't need a weird using when setting it in KestrelServerLimits
Allow 0 bytes/second
Require the grace period to be larger than Heartbeat.Interval

📢

I meant to leave a comment with my approval. I approve this pending changing "Minimum" to "Min" in all public APIs.

Updated, will merge when CI is green.

I know I already approved this. Hopeful changing the default is the last thing.


.ZPAQ date modified in future

My command line is:
zpaqfranz a VM_????.zpaq d:\vm -to "" -checktxt -tmp -not swap.* *.mrt *.rct  -m2 -t4
The result is that the .TXT file is created with the correct timestamp, but the ZPAQ archive is offset by +2 hours. I am in GMT+2 (winter time, which is currently exactly GMT+2).

You can try an update

looks good now


page date stamp needs updating

at the top of this page it has
January 13, 2023
but I believe this page has been updated since then.

Wait which page is this?

There is only one page with this date that we have on webmin.com, which is security.md. I will fix that and also will add dates to each event.

This has been fixed. Thanks for the heads up!
Jamie, please rebuild webmin.com.

Done!


allow adapter sort optimization

Adapters can optimize reduce, head, and tail procs.
This PR will allow adapters to optimize sort. Full example here: https://github.com/juttle/juttle-sql-adapter-common/pull/55

@demmer @davidvgalbraith @bkutil

+1

+1


[docs] Migrate Checkbox demos to emotion

[x] I have followed (at least) the PR section of the contributing guide.

The following demos of the Checkbox component were migrated:

[x] Indeterminate
[x] Label
[x] FormGroup
[x] Customized checkbox

Related to #16947

The keyboard focus visible on the customizaton demo is broken

Resolved

I have used the opportunity to breakdown the existing demos. Much better :)

Sure! by default it uses the primary. I will be more careful in the next 🎉

I will be more careful in the next

@vicasas I didn't see any mistake in the migration. The changes I have done were to further improve the page.


[SNOW-80] Adds table and column comments for TEAMMEMBER_LATEST table

This PR adds table and column comments for the TEAMMEMBER_LATEST table. This work and the syntax used is based on #38.

Thanks @thomasyu888, I had noticed that and made the change but forgot to push the commit before requesting review 😅


Wrong position of on cluster clause

https://github.com/silentsokolov/dbt-clickhouse/blob/88c75d4713ad0bd5bab2b9139794fc558b8f9ed1/dbt/include/clickhouse/macros/adapters.sql#L181
on cluster clause should be before modify key word

Thx, fix


[SP-6396] - Backport of PDI-18872 - Zip Bomb error when using the Excel Writer step with Use existing file for writing option

:white_check_mark: Build finished in 12m 25s
Build command:
mvn clean verify -B -e -Daudit -amd -pl plugins/excel/core

:ok_hand: All tests passed!
Tests run: 110, Failures: 0, Skipped: 0    Test Results

:information_source:  This is an automatic message


FastAPI 0.68.0 Breaks Usage of tuple in Input / Output compared to 0.67.0

First Check

[X] I added a very descriptive title to this issue.
[X] I used the GitHub search to find a similar issue and didn't find it.
[X] I searched the FastAPI documentation, with the integrated search.
[X] I already searched in Google "How to X in FastAPI" and didn't find any information.
[X] I already read and followed all the tutorial in the docs and didn't find an answer.
[X] I already checked if it is not related to FastAPI but to Pydantic.
[X] I already checked if it is not related to FastAPI but to Swagger UI.
[X] I already checked if it is not related to FastAPI but to ReDoc.

Commit to Help

[x] I commit to help with one of those options 👆

Example Code
# main.py

import uvicorn
from fastapi import FastAPI, Form

app = FastAPI()

@app.post("/")
def hello(arg: tuple[int, int] = Form(...)) -> str:
    pass

if __name__ == "__main__":
    uvicorn.run("main:app", port=8080)

Description

Run pip install uvicorn fastapi==0.68.0.
Run python ./main.py
Hit localhost:8080/docs, observe internal server error with below validation errors:

pydantic.error_wrappers.ValidationError: 2 validation errors for OpenAPI
components -> schemas -> Body_hello__post -> properties -> arg -> items
  value is not a valid dict (type=type_error.dict)
components -> schemas -> Body_hello__post -> $ref
  field required (type=value_error.missing)

Run pip install fastapi==0.67.0
Hit localhost:8080/docs, observe that endpoint documentation is successfully generated.

Operating System
Linux
Operating System Details
Ubuntu 20.04
FastAPI Version
0.68.0 has bug, 0.67.0 does not have bug.
Python Version
3.9
Additional Context
Any use of tuple in an input (Form, and BaseModel as JSON) or output (BaseModel as JSON) results in above error.

What are you expecting a tuple in a form field to look like?

What are you expecting a tuple in a form field to look like?

Same as it did in 0.67.0, the generated endpoint docs look like this:

I use typing.Tuple for geolocation.
class Model(BaseModel):
    name: str
    location: Tuple[float, float]

This seems a legit use of tuple, no?

I am also having this same problem, which I fixed by downgrading to fastapi version 0.67.0. Specific stack trace details, etc: #3686 (I closed my issue as it was a duplicate of this issue).

According to this: https://stackoverflow.com/questions/57464633/how-to-define-a-json-array-with-concrete-item-definition-for-every-index-i-e-a it's possible to have tuples in openapi3.1.
It could be great if @tiangolo could tell us if FastAPI will support Tuples again or if we need adapt our APIs. For now we are stuck in 0.67

@Mause I have an API that uses tuples in a few places as well. At the moment it looks like I will be forced to pin to 0.67.0 indefinitely to avoid breaking changes to my API. Do you know if there is a plan to fix this regression?

Is there any way to get @tiangolo 's attention on this issue? There are now at least 4 dupes of this issue (#3686, #3782, #3898, and #4168), and 2 open PRs (#3874 & #4169), each with exactly the same 1-line fix which works perfectly. We're all (anyone using tuples) stuck on version 0.67.0 until something is done...

It's seems that FastAPI is not actively maintained anymore and nothing seems to be done to allow someone else to do it (source: https://github.com/tiangolo/fastapi/discussions/3970)
I guess we need to wait for a fork but this could take a lot of time.
I personally modified all the code that needed Tuples to a Dict with 2 keys.
By the way staying in 0.67.0 is not a big deal as there is almost no more evolution.

It's seems that FastAPI is not actively maintained anymore and nothing seems to be done to allow someone else to do it (source: https://github.com/tiangolo/fastapi/discussions/3970)
I guess we need to wait for a fork but this could take a lot of time.
I personally modified all the code that needed Tuples to a Dict with 2 keys.
By the way staying in 0.67.0 is not a big deal as there is almost no more evolution.

I understand your frustration, I am also waiting for this to be fixed.  However, I don't think your claim of FastAPI being unmaintained is true at all.
For better or for worse, FastAPI is a project that stands on the shoulders of several other projects. Advocating for changes and improvements in those projects takes time. See this comment: https://news.ycombinator.com/item?id=29484907

@elrik75 I have the same thought. Look at the merged PR, most recent PR is doc translations and update dependencies.
Here https://github.com/tiangolo/fastapi/issues/1507#issuecomment-640240477 is the answer of this, but I don't think that's is a good solution.
Patching with some workaround(like this PR) is better than waitting for support with bug

Thanks for the discussion everyone! This should be solved by https://github.com/tiangolo/fastapi/pull/3874
It is available in FastAPI 0.73.0, released in the next hours. :tada:
For more context, check the last comment there: https://github.com/tiangolo/fastapi/pull/3874#issuecomment-1019578028

In short, using tuples now won't break the rest of Swagger UI.
And although they are supported by OpenAPI  3.1.0, Swagger UI doesn't support OpenAPI 3.1.0 yet. Even though FastAPI already has a couple of corner cases where it is more compatible with 3.1.0, I can't change the generated version yet, as Swagger UI wouldn't render it at all.
So, you can continue using tuples with FastAPI 0.73.0, those tuples won't always be properly rendered in Swagger UI (as they have never been), but now that won't break the rest of Swagger UI, and you will get the proper validation, etc. :tada:

This issue is solved and can be closed.

@MarioIshac can you close the issue?


Issue with rule-evaluator with self deploy alertmanager

When I was following this steps :- https://cloud.google.com/stackdriver/docs/managed-prometheus/rules-unmanaged#eval-rules-unmanaged
I made changes in the rule-evaluator configmap
apiVersion: v1
kind: ConfigMap
metadata:
  name: rule-evaluator
  namespace: monitoring
  labels:
    app.kubernetes.io/name: rule-evaluator
data:
  config.yaml: |
    global:
      external_labels:
        test: global-rule-evaluator
      evaluation_interval: 30s
    alerting:
      alertmanagers:
        - dns_sd_configs:
          - names:
            - alertmanager.monitoring.svc.cluster.local
          port: 9093
          type: A
    rule_files:
    - "/etc/rules/*.yaml"

After this changes i deploy the rule-evaluator deployment so that if any alert will trigger it will go to my self deploy alertmanager
After this deployment i was seeing this error in the logs of rule-evaluator pods
level=info ts=2022-12-01T13:06:27.137865623Z caller=main.go:450 msg="Loading configuration file" filename=/etc/config/config.yaml
level=error ts=2022-12-01T13:06:27.138282653Z caller=main.go:375 msg="Error reloading config" err="couldn't load configuration (--config.file=\"/etc/config/config.yaml\"): parsing YAML file /etc/config/config.yaml: yaml: unmarshal errors:\n  line 7: field dns_sd_configs not found in type config.AlertmanagerConfig\n  line 10: field port not found in type config.AlertmanagerConfig\n  line 11: field type not found in type config.AlertmanagerConfig"

Here it says that its parsing error and dns_sd_configs not found in type config.AlertmanagerConfig but as per the prometheus documentation :- https://prometheus.io/docs/prometheus/latest/configuration/configuration/#alertmanager_config
The configuration is there as i missing something here
image that i am using for the rule-evaluator :- gke.gcr.io/prometheus-engine/rule-evaluator:v0.5.0-gke.0
if you want to see the deployment file as well let me know i can add that file here as well but its the same which is mention over here :- https://github.com/GoogleCloudPlatform/prometheus-engine/blob/main/manifests/rule-evaluator.yaml

Hi @savanipoojan78,
This is indeed a bug! Thanks for reporting. I believe we just need to change the import line in the rule-evaluator to register all service discovery config types. I'll be iterating in #391 if you wanna take a look!
Cheers

To unblock you in the meantime,
Your DNS config looks like it's pointing to a alertmanager K8s service.  I believe you can use a kubernetes_sd_config to connect to the alertmanager. Something like:
alerting:
  alertmanagers:
  - follow_redirects: true
    enable_http2: true
    scheme: http
    path_prefix: /
    timeout: 10s
    api_version: v2
    relabel_configs:
    - source_labels: [__meta_kubernetes_service_name]
      separator: ;
      regex: alertmanager
      replacement: $1
      action: keep
    - source_labels: [__meta_kubernetes_service_port_number]
      separator: ;
      regex: 9093
      replacement: $1
      action: keep
    kubernetes_sd_configs:
    - role: endpoints
      kubeconfig_file: ""
      follow_redirects: true
      enable_http2: true
      namespaces:
        own_namespace: false
        names:
        - monitoring

Would that be possible to try?

I have made those changes and now i am getting this error in the pod
level=error ts=2022-12-08T05:28:15.937903027Z caller=main.go:144 msg="Error loading config (--config.file=/etc/config/config.yaml)" err="parsing YAML file /etc/config/config.yaml: yaml: unmarshal errors:\n  line 7: cannot unmarshal !!map into config.AlertmanagerConfigs"
apiVersion: v1
kind: ConfigMap
metadata:
  name: rule-evaluator
  namespace: monitoring
  labels:
    app.kubernetes.io/name: rule-evaluator
data:
  config.yaml: |
    global:
      external_labels:
        test: global-rule-evaluator
      evaluation_interval: 30s
    alerting:
      alertmanagers:
        follow_redirects: true
        enable_http2: true
        scheme: http
        path_prefix: /
        timeout: 10s
        api_version: v2
        relabel_configs:
        - source_labels: [__meta_kubernetes_service_name]
          separator: ;
          regex: alertmanager
          replacement: $1
          action: keep
        - source_labels: [__meta_kubernetes_service_port_number]
          separator: ;
          regex: 9093
          replacement: $1
          action: keep
        kubernetes_sd_configs:
        - role: endpoints
          kubeconfig_file: ""
          follow_redirects: true
          enable_http2: true
          namespaces:
            own_namespace: false
            names:
            - monitoring
    rule_files:
    - "/etc/rules/*.yaml"

This is what my config looks like rule-evaluator log the above line and goes into CrashLoopBackOff mode

Ah you need a - in front of follow_redirects as alerting.alertmanagers is an array, not a map.
Note - for the K8s-based service discovery to work for your rule-evaluator deployment, its serviceAccount will need to be able to discover alertmanager endpoints and services within the cluster. Typically, a ClusterRole similar to this will permit everything you need.

Ohh My bad Thank you for pointing that mistake but i ended up using this
alerting:
  alertmanagers:
  - scheme: http
    static_configs:
    - targets:
      - "region-monitoring-kube-pro-alertmanager.monitoring.svc:9093"

Which is working fine.
But i wanted a small help on this
So we are running multiple GKE cluster(in future it may increase) and on each cluster we have kube-prometheus running which is using this image gke.gcr.io/prometheus-engine/prometheus:v2.35.0-gmp.2-gke.0 and push all the metrics to GMP.
Now we have an central cluster which is running the Grafana and gmp-frontend running (gmp-fronted connected to GMP and Grafana connected to gmp-fronted) and alert-manager all the other GKE cluster has the rules and if any rules violet then its send that alert to this central alertmanager , now if i want to make any changes in the rule or alert i have to make those changes in like many cluster it becomes tedious , why i wanted to explore this rule-evaluator is it directly evaluate the rule against the GMP so if i just run the rule-evaluator in central cluster it resolve headache to maintain rules for each cluster. but while going through the Document here its says that (https://cloud.google.com/stackdriver/docs/managed-prometheus/rules-unmanaged#multi-project_and_global_rule_evaluation)
We recommend that you run one instance of the rule evaluator in each Google Cloud project and region rather than running one instance that evaluates against many projects and regions
Now all the cluster send the metrics to just a single google project but cluster are running on different region. i know it says that it support multi-project rule evaluation,
so my question is there any side-effect to using just a single rule-evaluator that run the rules against single google project but multiple GCP region?
And Thank you for this amazing Product  🎉🎉🎉 .

Having a single standalone rule evaluator that evaluates against everything works, but there are a few drawbacks to consider:

You lose the ability to permission alerts/rules by project, meaning that any developer can make a rule for any project/region/cluster and there's no way to stop them.
It also materially decreases reliability, as if the cluster or Cloud region that your rule evaluator runs in goes down, then your alerting goes down globally (even if other regions/clusters are operating normally).
You may not be able to port alerts 1:1, as if your alert expr assumes a cluster scope (e.g. by not having a {cluster='foobar'} filter or a 'sum by (cluster) aggregator) then it may accidentally execute against more data than expected. You'd have to ensure these filters or aggregations are on every single alert expr.
If you have a sum by (project_id) aggregator, then the rule evaluator will write the data back to each individual project instead of to the project in which it's running. This means your service account must have write permissions for each project in your metric scope. If you add a new project to the metric scope, you must also immediately update the service account permissions to allow writes for the new project to avoid errors.

Besides those concerns, the proposed pattern works.
You may also want to consider keeping rules/alerts on a per-cluster basis but using Terraform to configure them. This should address your concern around the tedium of configuring across every cluster without incurring the potential issues listed above.
And you're welcome! Thank you for the praise :-)

I'm going to resolve this issue, as the pending PR is more of a feature request that's tangential to what was discussed here.


Adding missing statement

Purpose
Adding a missing statement and fixing the issue in a link in deploying distributed setup

@HiranyaKavishani , when sending a PR to 3.1.0 please make sure to always send a PR to master as well. As 3.1.0 docs are the latest doc space at the moment.
I added the changes to master in [1]
[1] https://github.com/wso2/docs-apim/pull/1342


Stop the music when the Flutter application is closed

Hello guys, I'm playing music using the audioplayers package in an app.  The package is set to play in the background, but it continues to play when I close my application. How can I solve this problem?  Can I solve it using the application lifecycle?  I will be glad if you help, thanks in advance

Yes.
You can use the Application.detached and stop the audio player.
On Sat, 26 Dec 2020 at 11:42 Berat Kurt<EMAIL_ADDRESS>wrote:

Hello guys, I'm playing music using the audioplayers package in an app.
The package is set to play in the background, but it continues to play when
I close my application. How can I solve this problem? Can I solve it using
the application lifecycle? I will be glad if you help, thanks in advance
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/luanpotter/audioplayers/issues/706, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD4X4XUUCMTFQLSD2MPLNCLSWW4YXANCNFSM4VJ2BBYA
.

--
MUA N. LAURENT: Lead Software Engineer
Akivas Inc. https://akivas.com/
<EMAIL_ADDRESS>Makepe Rhone Poulenc, Douala

Thank you for much! I guess it.

Sorry, the problem could not be solved. App LifeCycle could not solve my job.  Automatically kicks player to foreground when the application closes

@zekkontro Did you try implementing the WidgetsBindingObserver interface in your audio player widget?
Maybe try something like this?
class _AudioPlayerWidgetState extends State<AudioPlayerWidget>
    with WidgetsBindingObserver {
  AudioPlayer _audioPlayer;

Subscribe the audio player widget to the lifecycle
@override
void initState() {
  WidgetsBinding.instance.addObserver(this);
  super.initState();
  ...
}

Unsubscribe the widget when disposed
@override
void dispose() {
  WidgetsBinding.instance.removeObserver(this);
  super.dispose();
  ...
}

Do something when app lifecycle changes
@override
void didChangeAppLifecycleState(AppLifecycleState state) {
  if (state == AppLifecycleState.paused) {
    _audioPlayer.pause(); // or stop
  }
}

@zekkontro Did you try implementing the WidgetsBindingObserver interface in your audio player widget?
Maybe try something like this?
class _AudioPlayerWidgetState extends State<AudioPlayerWidget>
    with WidgetsBindingObserver {
  AudioPlayer _audioPlayer;

Subscribe the audio player widget to the lifecycle
@override
void initState() {
  WidgetsBinding.instance.addObserver(this);
  super.initState();
  ...
}

Unsubscribe the widget when disposed
@override
void dispose() {
  WidgetsBinding.instance.removeObserver(this);
  super.dispose();
  ...
}

Do something when app lifecycle changes
@override
void didChangeAppLifecycleState(AppLifecycleState state) {
  if (state == AppLifecycleState.paused) {
    _audioPlayer.pause(); // or stop
  }
}

@yuenlye thanks for the explanation! that is totally correct, and the right way of doing this.


Add MPU60X0 device driver to TIVA TM4C bring up sequence

Hi everyone,
I saw that the bring up sequence of the Nucleo-144 already registers the MPU60X0 device driver, if requested. So far, i've edited the bring up file on the TM4C board to bind the MPU driver on bring up and it works fine.
I would be happy to open this PR. However I have some questions:
Is there a standard way of executing this device driver binding?
Are there restrictions on the I2C bus? I see many board using the I2C1 only and I'm using I2C0.
Thanks

What i2c restrictions? I used  I2C0 in a tm4c board a few weeks ago.
https://github.com/apache/nuttx/blob/1be95c3313059d31da3607987ce6135faa296dea/boards/arm/tiva/tm4c1294-launchpad/src/tm4c_bringup.c#L353
Did I misread? Pushing code with your question is more efficient. This project can't keep up with issues as it is, so I would just close this issue and open a PR if I were you.


fix(): update to use user.username instead of user.login to match API

Fixes bug where no one is ever a collaborator, due to using outdated 'login' API response.

Thank you so much! This closes #39 :-D


302 Found missing Location header

Currently, there is a backlog ticket to support response headers: https://github.com/ogen-go/ogen/issues/191
Without the support of response headers, there is no way to implement properly HTTP 302 Found
openapi: '3.0.2'
info:
  title: API Title
  version: '1.0'
servers:
  - url: http://localhost:8080

paths:
  /redirect:
    get:
      parameters:
        - name: to
          in: query
          schema:
            type: string
          required: true
      responses:
        '302':
          description: Redirection to landing page
          headers:
            Location:
              description: landing page uri
              schema:
                type: string
                format: uri

In this example the generated code of the response structure is empty:
// RedirectGetFound is response for RedirectGet operation.
type RedirectGetFound struct{}

Also, the generated interface for the handler does not provide any other way to set the response header.
Response example:
~ >>> curl 'http://localhost:8080/redirect?to=https://ogen.dev' -v
*   Trying <IP_ADDRESS>:8080...
* Connected to localhost (<IP_ADDRESS>) port 8080 (#0)
> GET /redirect?to=https://ogen.dev HTTP/1.1
> Host: localhost:8080
> User-Agent: curl/7.82.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 302 Found
< Date: Tue, 17 May 2022 00:26:53 GMT
< Content-Length: 0
<
* Connection #0 to host localhost left intact

As a result, there is no way to implement 302 Found
;(
Btw, thank you for this cool project!

Please try latest release

@shadowspore, amaizing! thank you!
~ >>> curl 'http://localhost:6004/redirect?to=https://ogen.dev' -i
HTTP/1.1 302 Found
Location: https://ogen.dev
Date: Fri, 03 Jun 2022 20:17:45 GMT
Content-Length: 0


Merge dev into main for Deployment

Description
This PR merges the latest changes from the dev branch into the main branch. The dev branch has been tested and includes all necessary updates and fixes for deployment to the live environment.
Type of change

[X] Other Deployment

How Has This Been Tested?

[X] Unit & e2e tests

Checklist:

[ ] I have performed a self-review of my own code.
[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] I have made corresponding changes to the documentation.
[X] My changes generate no new warnings.
[ ] Any dependent changes have been merged and published in downstream modules.
[ ] I have reviewed the Security Best Practices Document.
[ ] I have followed the Naming Conventions Guide for my changes.
[X] I have ensured that my pull request title is descriptive.

closing this pr as it is no longer necessary


Low performance of Object Detection Models in Coral Dev Board

Hi
Recently my company bought a Coral Board Dev and  Coral USB Accelerator to detect some objects in outdoor environment.
We have tried to train MobileNet V1 and V2 using TPU on the Cloud, as well using GPU RT2070 and finally we have implemented other models such as Inception Lite and Tiny Yolo V3 but the results are no good according the accuracy during the performance.
For this reason, I would like to know what else could be done to improve this model in real Object detection in Coral edge device?

@IvanChavR
Provide the exact sequence of commands / steps that you executed before running into the problem.
Thanks!


Add jinja2-strcase Jinja extension

Actual Situation
Hi, copier already vendors https://gitlab.com/dreamer-labs/libraries/jinja2-ansible-filters/ to provide additional helpers and filters in templates. I would like to suggest adding https://pypi.org/project/jinja2-strcase/ as well, as bootstrapping a new project often involves rendering the project name in multiple cases in different contexts. For example, many micro services today include both business code and infrastructure-as-code in the same project. A Python project would require snake_case for the project name, whereas the CDK for AWS infrastructure would idiomatically use CamelCase. Makefile targets would idiomatically need kebab-case. Instead of manually crafting these different representations of the project name, jinja2-strcase would bring this to copier out of the box.
Desired Situation

Proposed solution

Indeed it looks like a nice filter for Copier use case. However, the need for ansible-filters is because of the to_nice_yaml, which is only available there and is very needed for copier answers files, which are a core Copier feature.
We can add it to the list of recommendations, as it really will be useful in many contexts, as you explained.
Does that seem good to you?


Loop working incorrectly when using ngFor

When using ngFor to add swiper-slide and loop is enabled, I noticed that it is no longer possible to go to the previous slide when you are at the first slide. Expected is that you can go back to the last slide when swiping back from the first.
Also when swiping to the next slide on the last one, you go to the second slide instead of the first.
I adapted the demo (by adding loop: true to the config) to demonstrate this issue.
see:
https://plnkr.co/edit/7x82yViclRfuyP4DWG2X?p=preview

Hi guys. Yes, I have got some problem. I tried to use without ngFor - doesn't matter.

It looks like this issue is related to issue 36. I need to upgrade this package to swiper version 4 and I'll see if I can get this fixed then.

I'm facing the same problem, does this issue is contempled to be fixed?

Anyone got any solution on this issue?


package java.lang.management does not exist

Hi There,
I'm trying to convert lucene-core-4.0.0.jar file, while one error raised. please check as below:

Thanks.

J2ObjC does not have a Java VM, so it cannot support classes that manage a VM.
I recommend that you create stub classes for the missing API, which return null, false, or 0 depending on the return value. The easiest way to do this is to start with the output from "javap -protected .".


High CPU usage and crash report: Ubuntu 19.04 / gnome 3.32 / kernel <IP_ADDRESS>

Azure Data Studio Version:
Version: 1.5.2
Commit: f74080c96310354bc92211f1826c0fdce78ca2f6
Date: 2019-03-22T06:07:48.490Z
VS Code 1.30.1
Electron: 2.0.12
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
OS: Linux x64 5.0.0-7-generic

Steps to Reproduce:

Open Azure Data Studio
Look into Gnome system monitor
2 Threads are always at 100%
Reproducible even with all the extensions disabled.
_usr_share_azuredatastudio_resources_app_extensions_mssql_sqltoolsservice_Linux_1.5.0-alpha.71_MicrosoftSqlToolsServiceLayer.1000.log

Also, there's a crash report (Not sure if it's related).

@wandoschneider do you have any additional info on the state of Azure Data Studio after step 1 in the repo.  For example, are there any SQL files open, any active connections, do the threads run at 100% indefinitely or slow down eventually, etc.?  Thanks!

Hi! No files open, no active connections. Just launch the application and the CPU fan starts to scream. They run indefinitely.
Screenshot:

Hi! Not sure what solve the problem, but after updating to the latest release on linux (1.6) the problem is gone.


Parsing release notes from tag message

https://github.com/Goooler/keep-a-changelog/actions/runs/10680426004/job/29601805373
https://github.com/Goooler/keep-a-changelog/releases/tag/v1.1.2

The commit title of 0c3619f5c3e68b2f64ae03335cb241ce9f286b4d has been treated as the release notes.

https://github.com/Goooler/keep-a-changelog/actions/runs/10680510961/job/29602090219
https://github.com/Goooler/keep-a-changelog/releases/tag/v1.1.3

The commit title of 606db3efd78c7682adc817da6158cd63bee8abb7 has been treated as the release notes, and ### Added has been amended to the release title.

git push origin v1.1.4
Enumerating objects: 1, done.
Counting objects: 100% (1/1), done.
Writing objects: 100% (1/1), 711 bytes | 711.00 KiB/s, done.
Total 1 (delta 0), reused 0 (delta 0), pack-reused 0 (from 0)
To https://github.com/Goooler/keep-a-changelog
 * [new tag]         v1.1.4 -> v1.1.4

gh release create v1.1.4 --title v1.1.4 --notes-from-tag
https://github.com/Goooler/keep-a-changelog/releases/tag/v1.1.4

Run this release on my local device, everything works well, see https://github.com/Goooler/keep-a-changelog/releases/tag/v1.1.4.

git push origin v1.1.5
Enumerating objects: 1, done.
Counting objects: 100% (1/1), done.
Writing objects: 100% (1/1), 711 bytes | 711.00 KiB/s, done.
Total 1 (delta 0), reused 0 (delta 0), pack-reused 0 (from 0)
To https://github.com/Goooler/keep-a-changelog
 * [new tag]         v1.1.5 -> v1.1.5

gh release create v1.1.5 --notes-from-tag
https://github.com/Goooler/keep-a-changelog/releases/tag/v1.1.5

Run this release on my local device, the release notes are correct but the title has been amended ### Added, see https://github.com/Goooler/keep-a-changelog/releases/tag/v1.1.5


add more websocket server entrypoints

The websocket server protocol should be based on the expression DSLs instead of TutorialD, as it is now, to make it production-ready. In order not to require a TutorialD javascript parser, the websocket server could parse and return an expression from TutorialD back to the client, ready for execution.

This is implemented as part of the websocket server now.


Add SmartToken contract

Simple Summary
A standard interface for smart tokens based in the ERC20 standard.
Abstract
This standard provides basic functionality to transfer tokens, as well as allow tokens to be approved so they can be spent by another on-chain third party. Also it allows to execute calls on transfers and approvals.
Motivation
A standard interface allows any tokens on Ethereum to be re-used by other applications: from wallets to decentralized exchanges. The ERC20 token standard is widely accepted but it only allows the transfer of value, ethereum users are available to transfer value and data on transactions, with these extension of the ERC20 token standard they will be able to do the same with ERC20 tokens.
Specification
Token
Methods
NOTE: Callers MUST handle false from returns (bool success).  Callers MUST NOT assume that false is never returned!
name - ERC20
Returns the name of the token - e.g. "MyToken".
OPTIONAL - This method can be used to improve usability,
but interfaces and other contracts MUST NOT expect these values to be present.
function name() constant returns (string name)

symbol - ERC20
Returns the symbol of the token. E.g. "HIX".
OPTIONAL - This method can be used to improve usability,
but interfaces and other contracts MUST NOT expect these values to be present.
function symbol() constant returns (string symbol)

decimals - ERC20
Returns the number of decimals the token uses - e.g. 8, means to divide the token amount by 100000000 to get its user representation.
OPTIONAL - This method can be used to improve usability,
but interfaces and other contracts MUST NOT expect these values to be present.
function decimals() constant returns (uint8 decimals)

totalSupply - ERC20
Returns the total token supply.
function totalSupply() constant returns (uint256 totalSupply)

balanceOf - ERC20
Returns the account balance of another account with address _owner.
function balanceOf(address _owner) constant returns (uint256 balance)

transfer - ERC20
Transfers _value amount of tokens to address _to, and MUST fire the Transfer event.
The function SHOULD throw if the _from account balance does not have enough tokens to spend.
A token contract which creates new tokens SHOULD trigger a Transfer event with the _from address set to 0x0 when tokens are created.
Note Transfers of 0 values MUST be treated as normal transfers and fire the Transfer event.
function transfer(address _to, uint256 _value) returns (bool success)

transferFrom - ERC20
Transfers _value amount of tokens from address _from to address _to, and MUST fire the Transfer event.
The transferFrom method is used for a withdraw workflow, allowing contracts to transfer tokens on your behalf.
This can be used for example to allow a contract to transfer tokens on your behalf and/or to charge fees in sub-currencies.
The function SHOULD throw unless the _from account has deliberately authorized the sender of the message via some mechanism.
Note Transfers of 0 values MUST be treated as normal transfers and fire the Transfer event.
function transferFrom(address _from, address _to, uint256 _value) returns (bool success)

approve - ERC20
Allows _spender to withdraw from your account multiple times, up to the _value amount. If this function is called again it overwrites the current allowance with _value.
Users SHOULD make sure to create user interfaces in such a way that they set the allowance first to 0 before setting it to another value for the same spender.
THOUGH The contract itself shouldn't enforce it, to allow backwards compatilibilty with contracts deployed before
function approve(address _spender, uint256 _value) returns (bool success)

allowance - ERC20
Returns the amount which _spender is still allowed to withdraw from _owner.
function allowance(address _owner, address _spender) constant returns (uint256 remaining)

Smart token methods
transferData
Execute a function on _to with the _data parameter, if the function ends successfully execute the transfer of _value amount of tokens to address _to, and MUST fire the Transfer event.
The function SHOULD throw if the call to _to address fails or if _from account balance does not have enough tokens to spend.
Note Transfers of 0 values MUST be treated as normal transfers and fire the Transfer event.
function transfer(address _to, uint256 _value, bytes _data) returns (bool success)

transferDataFrom
Execute a function on _to with the _data parameter, if the function ends sucesfully execute the transfer of _value amount of tokens from address _from to address _to, and MUST fire the Transfer event.
The transferFrom method is used for a withdraw workflow, allowing contracts to transfer tokens on your behalf.
This can be used for example to allow a contract to transfer tokens on your behalf and/or to charge fees in sub-currencies.
The function SHOULD throw if the call to _to address fails or if the _from approved balance by _from to msg.sender is not enough to execute the transfer.
Note Transfers of 0 values MUST be treated as normal transfers and fire the Transfer event.
function transferFrom(address _from, address _to, uint256 _value, bytes _data) returns (bool success)

approveData
Execute a function on _to with the _data parameter, if the function ends sucesfully allows _spender to withdraw from your account multiple times, up to the _value amount. If this function is called again it overwrites the current allowance with _value.
Clients SHOULD make sure to create user interfaces in such a way that they set the allowance first to 0 before setting it to another value for the same spender.
The function SHOULD throw if the call to _to address fails.
THOUGH The contract itself shouldn't enforce it, to allow backwards compatilibilty with contracts deployed before
function approve(address _spender, uint256 _value, bytes _data) returns (bool success)

Events
Transfer - ERC20
MUST trigger when tokens are transferred, including zero value transfers.
event Transfer(address indexed _from, address indexed _to, uint256 _value)

Approval - ERC20
MUST trigger on any successful call to approve(address _spender, uint256 _value).
event Approval(address indexed _owner, address indexed _spender, uint256 _value)

Implementation
The SmartToken is implemented and used in the Lif token, Github Repository
Example implementations are available at

https://github.com/windingtree/LifToken/blob/master/contracts/SmartToken.sol

In the case of our project Winding Tree methods like these will allow us to:

Book hotel rooms or flights in one transaction, executing transfer and book functions implemented in our contracts.
Implement approval of bookings, the user will approve the spent of tokens to the hotel, the hotel will accept them if he allows the user to book the room at that price and reject them if not.
Send encrypted information in token transactions.
Will allow developers to build more complex apps over our platform.

Also, I've been thinking that this can also help the token to not being take in count as a security, because it will be able to do more that just transfer value between users, but not sure if that is accurate.

Hi @AugustoL! I think this proposal is interesting. It's mostly the same as the transferAndCall proposal in ethereum/EIPs#677, right?

Yes is very similar, I have the EIP already written and ready to proposed, but I wanted to propose it first here, I think it will have more acceptance in the community if we show it working in Zeppelin Solidity.
If you want @frangio I can create the PR to add it tomorrow :)

@AugustoL do transferData and transferDataFrom use the same function names as transfer and transferFrom? Why not use the names transferData and transferDataFrom to avoid confusion?

@maraoz yes, I was using that names for the methods but forgot to change it here when I was creating the issue, now the issue has the correct function names :)

SmartToken is the name used by Bancor team for their protocol.
I'm afraid using it here may introduce some confusion.


[Question] Whether dim3(32, 2) work well with wrapSize = 64 for ROCm?

I saw the wrapSize of most AMD devices is 64, so if I want to fully utilize the per-block resources, I am supposed to launch a kernel whose number of threads per block should be the integer-time of 64, right?
If so, for this case kernel<<<.., dim3(32, 2), >>>, I wonder whether the threads per block are executed by 2 different wraps, or within a same wrap?

One warp , size 64

@bensander Great, thanks! Another relative question is whether the following 2 cases have similar performance, or not?
Case-1) kernel<<<(N + 63) / 64, 64>>>(...)
Case-2) kernel<<<(N + 1023) / 1024, 1024>>>(...)

Ignoring other factors like shared memory, I just wonder when both 2 cases following the warpSize requirement, whether Case-1 has larger overhead than Case-2? (as it uses less threads per block compared with Case-2)

Hi @bensander, can one CU schedule 10 work groups together? (each work group has exactly 256 work items)


search-url containing 'exclude stream', incorrectly reconstructs search

Steps to reproduce (on web):

search for -stream:zulip (ie excluding a stream)
the url changes to https://clojurians.zulipchat.com/#narrow/-stream/150796-zulip and results show up
when I do a page reload, I see the search-box now contains -stream:150796-zulip, and no results are found

What I would expect is that the url would correctly reconstruct the search, and yield the same results.
more information

this can be seen in the desktop app as well: submit -stream:zulip, do History > Back, then History > Forward: the search is now -stream:150796-zulip.

@eval Thanks for the report!
I think the fix is something like this, but I need to test it manually and add an automated test:
--- a/static/js/hash_util.js
+++ b/static/js/hash_util.js
@@ -166,12 +166,13 @@ exports.parse_narrow = function (hash) {
             return;
         }

-        const operand  = exports.decode_operand(operator, raw_operand);
         let negated = false;
         if (operator[0] === '-') {
             negated = true;
             operator = operator.slice(1);
         }
+
+        const operand  = exports.decode_operand(operator, raw_operand);
         operators.push({negated: negated, operator: operator, operand: operand});
     }
     return operators;

Thanks for the fix @showell!


gh workflows auto-backport, backport-based-on-label

Remove backport-based-on-label.

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Backport failed for kirkstone-next, because it was unable to cherry-pick the commit(s).
Please cherry-pick the changes locally and resolve any conflicts.
git fetch origin kirkstone-next
git worktree add -d .worktree/backport-9802-to-kirkstone-next origin/kirkstone-next
cd .worktree/backport-9802-to-kirkstone-next
git switch --create backport-9802-to-kirkstone-next
git cherry-pick -x cb070a58956c7e6f9356db4abab4766ee6e6bd16

Backport failed for scarthgap-next, because it was unable to cherry-pick the commit(s).
Please cherry-pick the changes locally and resolve any conflicts.
git fetch origin scarthgap-next
git worktree add -d .worktree/backport-9802-to-scarthgap-next origin/scarthgap-next
cd .worktree/backport-9802-to-scarthgap-next
git switch --create backport-9802-to-scarthgap-next
git cherry-pick -x cb070a58956c7e6f9356db4abab4766ee6e6bd16

Backport failed for styhead-next, because it was unable to cherry-pick the commit(s).
Please cherry-pick the changes locally and resolve any conflicts.
git fetch origin styhead-next
git worktree add -d .worktree/backport-9802-to-styhead-next origin/styhead-next
cd .worktree/backport-9802-to-styhead-next
git switch --create backport-9802-to-styhead-next
git cherry-pick -x cb070a58956c7e6f9356db4abab4766ee6e6bd16


Allow hyprctl dispatch workspace <name> without name: prefix

It would be nice if hyprctl would work with the names used in wlroots. With this change, the patch for waybar would work for named workspaces too. getWorkspaceIDFromString#L194 could test if the input is a valid relative argument and default to test if the named workspace exists and return it. I think this should not break existing setups, but would allow easier scripting.

you can use name:<wlrname> and it will work perfectly fine, even with numbered workspaces.

oh no wait sec
I'll make that, would be easier

you can use name: and it will work perfectly fine, even with numbered workspaces.
I tested this and workspace 5 =/= workspace name:5, so I think it would break existing setups if the waybar-hyprland-git patch or the wiki would be changed in this way.

uhhh that happened. True.

e3b1d3c3c53c2ffad07f2ef91d5a0cf3fa452879


Storage Module Block (RFtools) Bug Ftb Unstable Latest Version 1.10.2

When i am going to craft new storage module tier 1 to tier 2 inside my module storage block  then he delete my old one with all my items inside

Can confirm, just lost my original storage module when attempting to craft a tier 1 to tier 2 while a tier 3 was already inside

I guess FTB Unstable has RFTools 5.17? Then that's a known bug fixed in 5.18

Awesome! Thanks for letting us know


Django 1.11 compatibility

Replaced RequestContext with a simple dict

Solves #134

Codecov Report

Merging #135 into master will increase coverage by 0.01%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master     #135      +/-   ##
==========================================
+ Coverage   63.45%   63.47%   +0.01%
==========================================
  Files          38       38
  Lines        1483     1481       -2
==========================================
- Hits          941      940       -1
+ Misses        542      541       -1

Impacted Files
Coverage Δ

categories/views.py
26.66% <0%> (-0.51%)
:arrow_down:

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 926d85a...af26da6. Read the comment docs.


Promise support?

No. It would increase the complexity of the code base and testing overhead.

Could you expose classes via module.exports (for example, Broker) so that I can use bluebird.promisifyAll to provide a promise-style API?

I'll create a branch and do it there. You happy to test / feedback?

It won't be better!
I will use it in our experimental environment :P

Try
{
  "dependencies": {
    "rascal": "git://github.com/guidesmiths/rascal.git#promises"
  }
}

Promise.promisifyAll(require('rascal').classes)

Thanks for your effort. However it doesn't fully work at least for broker (I haven't tried other classes yet) because:

Broker does not expose its base class  https://github.com/guidesmiths/rascal/blob/promises/lib/amqp/Broker.js#L17
In this way, broker instance methods such as broker.publish won't be promisified.

Broker does not use prototype to define its methods thus bluebird.promisifyAll(Object.getPrototypeOf(someBrokerInstance)); will not work either.

promisify(someBrokerInstance) works but it is not ideal because it is not a one-time setup.
I would try to make some changes and will send you PRs whose implementations are friendly to promisify.

Thanks. I'm to accept a PR.

I made first attempt to make Broker promisify friendly:
https://github.com/breeswish/rascal/commit/c62c4a425093fa6fa7ce522605822cb0e021ff5c?w=1
Simple example rewritten in Promise way and ES 2017:
import bluebird from 'bluebird'
import Rascal from 'rascal'

bluebird.promisifyAll(Rascal.Broker)
bluebird.promisifyAll(Rascal.Broker.prototype)

(async () => {

  const broker = await Rascal.Broker.createAsync(Rascal.withDefaultConfig(config))
  broker.on('error', console.error)

  const subscription = await broker.subscribe('demo_sub')
  subscription
    .on('message', function(message, content, ackOrNack) {
      console.log(content)
      ackOrNack()
    })
    .on('error', console.error)

  setInterval(async () => {
    await publication = broker.publish('demo_pub', new Date().toISOString() + ': hello world')
    publication.on('error', console.error)
  }, 1000)

}())

I am going to test the new broker these days to see if there are any problems :P I will make PR later

Looks good to me. Thanks. After submitting the PR how do you feel about maintaining a 'rascal-as-promised' module?

Thanks, I might not be a good person to maintain that since most of the time I am not working with something related to AMQP :P I prefer to making rascal friendly to promisify tools so that users who want to use a promise style API can easily achieve that while rascal needn't care much about the promise API.

Ok seems that the promise way may lose message..caused by await broker.subscribeAsync('demo_sub')..

Good spot. It's a weakness in the rascal API that you can't safely go async between calling subscribe and registering the on message handler.
Couple of things I might be able to do...

Accept an optional event handler as part of the subscribe function.
Not start consuming messages until an on message event listener was added using the newListener event

Not as easy as I'd hoped.

Would need to take multiple event handlers ('message', 'invalid_message', 'error', 'redeliveries_exceeded')
Breaks the subscrition.cancel behaviour.

Agree with you. BTW Promise is at least a microtask so that changing API is unavoidable to support Promise. This functionality is more difficult than I thought :P

I think the API will be better if the user can subscribe to events before starting to consume messages from rabbit, so I'm still giving it some thought. I have a lot of other stuff on at the moment though so it won't be soon though.

@BorePlusPlus just came up with a nice idea. Instead of consuming messages immediately, if rascal could wait for an on('message') handler to be registered. Will investigate

@BorePlusPlus just came up with a nice idea. Instead of consuming messages immediately, if rascal could wait for an on('message') handler to be registered. Will investigate

Any change we can see this on the master branch?

Currently available on the promise-support branch. I'll publish once I've done some more testing and had it reviewed.

Release as 4.0.0


Add babelrc schema

The json extension defines .bablerc as an extension for JSON file.
Since there also is a schema for .babelrc (schemastore/src/schemas/json/babelrc.json) the JSON extension should also define the schema for .bablerc files.

Schema associations are typically done in the extension that 'owns' the file. E.g. the schema association for .eslintrc is done in the es lint extension.
Also for babel there exists https://marketplace.visualstudio.com/items?itemName=waderyan.babelrc.
I realize that it would be convenient to just have this built-in and we can make an exception for babelrc if you think we should. @egamma ?

Schema associations are typically done in the extension that 'owns' the file. E.g. the schema association for .eslintrc is done in the es lint extension.

This makes good sense.
@waderyan since the babel extension exists then we should add it to the extension tips when a user opens .bablerc file. Assigning the issue to @waderyan

Done with PR https://github.com/Microsoft/vscode-distro/pull/69


Use lmazuel/swagger-to-sdk Docker container

As discussed with @devigned on the Slack workflow channel, SwaggerToSdk needs its own Github repository:

It permits to enable SwaggerToSdk.py Travis testing (rest-api travis is not the right place)
Make a change in SwaggerToSdk.py does not regenerate the SDK (not relevant)

In addition, I created a Docker container with the configured env and the script. See the new Travis file:

It permits to reduce the amount of code in the Travis file
It reduces the time to migrate to Jenkins if needed one day
It allows testing the script easily for anyone who can use Docker
Last but not least, divide by 2x the Travis build time

https://github.com/lmazuel/swagger-to-sdk
https://hub.docker.com/r/lmazuel/swagger-to-sdk/
This commit erases the SwaggerToSdk files from this repo at the same time.

Build failed in Node because the Node configuration file is not using the last configuration format.

@devigned @amarzavery Is there any problem to merge this one, or it's just your are too busy on other things? :)

LGTM!


Update K8s dependencies to 1.18.x

How to categorize this issue?

/area robustness
/kind enhancement
/priority normal
What would you like to be added:
Update the vendor sources in g/g to K8s 1.18.x.

/assign
/in-progress

To track progress: https://github.com/timuthy/gardener/tree/maintenance.vendor

Update: As soon as #2588 has been merged, we proceed with the actual update work.

FYI: This blocks us from updating controller-runtime from 0.5.x to 0.6.x.
We import github.com/gardener/gardener/pkg/apis/core/v1beta1 in our go-code to dynamically create shoots.

Why is this blocking you?
If you are only importing the API packages, you should be good to go for using different versions of k/k or controller-runtime. Right?

This is what I assumed, but seems not to be true:
go build -o bin/manager main.go
# github.com/gardener/gardener/pkg/apis/core/v1beta1
../../../go/pkg/mod/github.com/gardener/gardener@v1.8.0/pkg/apis/core/v1beta1/conversions.go:84:15: scheme.AddConversionFuncs undefined (type *runtime.Scheme has no field or method AddConversionFuncs)
Makefile:57: recipe for target 'build' failed
make: *** [build] Error 2

conversions.go is apparently broken with k8s 1.18 dependencies

Ah ok, makes sense.
Thanks for explaining!

Hello! May I ask you when this update will be done? I currently use these versions of k8s dependencies in my component:
	k8s.io/api v0.18.8
	k8s.io/apimachinery v0.18.8
	k8s.io/client-go v0.18.8
	sigs.k8s.io/controller-runtime v0.6.2

and the old Gardener's dependencies seem not to allow me to build it at all 😞
# github.com/gardener/gardener/pkg/apis/core/v1beta1
/Users/i354518/go/pkg/mod/github.com/gardener/gardener@v1.8.1/pkg/apis/core/v1beta1/conversions.go:84:15: scheme.AddConversionFuncs undefined (type *runtime.Scheme has no field or method AddConversionFuncs)

It seems that the issue from above are caused by https://github.com/kubernetes/kubernetes/issues/84452 + https://github.com/kubernetes/kubernetes/pull/85891. In general we should be able now to switch AddConversionFuncs calls to AddConversionFunc and that should allow vendoring gardener/gardener with<EMAIL_ADDRESS>

I already did that in my WIP branch, e.g. https://github.com/timuthy/gardener/blob/159a91cfb4fa61fc9dfcae95601543c33dc16020/pkg/apis/core/v1alpha1/conversions.go and hope to finish the rest next week.

Hello, @timuthy! May I ask you, what is the change's status?
It's getting more and more urgent from my side to upgrade these dependencies 😞


Unresponsive terminals and window, when closing tab with Ctrl+D

[x] I am on the latest Hyper.app version

Version 1.3.1 (<IP_ADDRESS>8)

[x] I have searched the issues of this repo and believe that this is not a duplicate

OS version and name: OSX 10.11.5 (15F34)

Hyper.app version: Version 1.3.1 (<IP_ADDRESS>8)

Link of a Gist with the contents of your .hyper.js: https://gist.github.com/joakin/d22afb83f702b1971ede77549fbfcf27

Relevant information from devtools (CMD+ALT+I on Mac OS, CTRL+SHIFT+I elsewhere):
Uncaught TypeError: Cannot match against 'undefined' or 'null'.effect @ bundle.js:formatted:1544

The issue is reproducible in vanilla Hyper.app: Yes. Removed my .hyper.js and still broke

Issue
Steps

Open hyper (check responsiveness with ls)
Open a tab with Cmd+T (check responsiveness with ls)
Close tab with Ctrl+D
Back to initial tab. Tab is unresponsive. Can't write on it. Cmd+T opens new tabs but they don't initialize.

Problem persists until the whole window is closed.

Debugging info
When checking the devtools, there's a typeerror comming from the line
const {shell: L} = U().sessions.sessions[F]

Where F (the session id) doesn't exist in the sessions part of the state tree:

So the destructuring blows up.

This behavior worked on previous versions if I recall correctly, given I always close tabs with ctrl+D and didn't notice it before. (I cycle to hyper seasonally to see how it is faring so I'm not sure what the previous version I used extensively was).
Let me know if you need more info!

Same behavior using Cmd+w ?

Sorry forgot to mention it. Closing using CMD+W doesn't seem to show the
problem.
On Fri, Apr 28, 2017, 7:12 PM Hugo Torzuoli<EMAIL_ADDRESS>wrote:

Same behavior using Cmd+w ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/zeit/hyper/issues/1766#issuecomment-298054694, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAoJr1feEtUzjYcT_CpBaq0--hVR96Qaks5r0h3ogaJpZM4NJ66A
.

@joakin I had the same problem as you, but it got fixed in #1698. What happens if you pull down the latest version from master and run it? Do you still have the same problem?

@andrroy Tried latest master (0797f38) and it seems to work fine, so it seems fixed as you suspected!
Going to close then, I'll wait for a release 😄 . Thanks!


refactor: unpack & try_unpack

As I mentioned on Discord. Inspired by this discussion

This is me trying to become more acquainted with the code
We don't have to merge it (genuinely)
Though I do find this code simpler to understand
It's less impressive rust, maybe less abstract, less use of the type system
It's the same verbosity, as measured by lines of code
It does more allocating, more .clone()
But it's actually slightly faster on cargo bench, about 3% on my machine

It doesn't run each try_into_* before doing the next one if that fails
Maybe it allows for fewer eventual optimizations in the future though?

It would need a quick pass to add the regex from today

GPT-4 helped me a lot!

I added a couple of notes on further changes. We're probably doing too much if args.len() == X in lots of places, and could have these as structs & enums in rust, though I'm not sure how deep in the compiler we want them (maybe there's a difference between functions & operators?)

This is way better, as in way more readable.
I went too deep with the no-clone frenzy :D It's actually slower probably because it was searching for impl of functions in linear search. This PR is now using sub-logarithmic lookups (because it's using match).

OK great! Thanks for being open. I was holding that it was "worse but easier rust" — maybe it's actually / actually much worse. I do think this sort of change can make it easier for others to contribute...
I'll update to yesterday's regex addition, resolve hte comments, and leave a couple of notes re strings vs FunctionDecls (i.e. https://github.com/PRQL/prql/pull/2532#discussion_r1183937392)

...and using slice patterns reduces some of the if args.len... verbosity: https://github.com/PRQL/prql/pull/2532/commits/e6fc1f232ab572edce075d7b705b5dd6af9beee1

I'll merge given your ✅ , but happy to do follow-up with any other changes


What is completeCallback

Why does the plugin have successCallback, failureCallback, and completeCallback?
The README says it's an error callback. Then what how is it different form failureCallback?

completeCallback is an optional callback to be called when the file is done playing. A simple implementation of "play" function with all three callbacks could be:
this.nativeAudio.play('audio1', () => {         //completeCallback         console.log('audio1 is done playing')       }).then(() => {         //successCallback         console.log("Success callback for audio1")       }, (err) => {         //failureCallback         console.log("Error callback for audio1: ", err)       })


Correct built-in styles and clarify elmMinimalist documentation

Closes #23

Thank you, I hope to review it later today =)


⚠ Bofrost.at has degraded performance

In 703cae7, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1766 ms

Resolved: Bofrost.at performance has improved in 39b1a1d.


Move web tool test per-test timeout to shard

Move per-test timeout for tools web shard into the test runner so new files will also pick up the timeout.
Mark Windows web_tool_tests as unflaky in prod.  Passing:
https://ci.chromium.org/p/flutter/builders/prod/Windows web_tool_tests/1287
Follow up to https://github.com/flutter/flutter/pull/78386

Google testing failure unrelated.


Discovery Attributtes

Description
After a successful installation, the query interface element to select the Patient Characteristics shows a 'No results found' in the dropdown. The following checks were made to check in multiple installations, and the issue persists:

All the services are running (viz., Elasticsearch, Neo4J, Service and Authenticator).
Indices for Elasticsearch and User Interface are successfully created.
Source has been assigned to relevant discovery groups.

Upon further troubleshooting, /AjaxApi/GetPhenotypeAttributes/(network_key) returns a success 200 status code, but the attribute_values are not being populated as below:

Steps to reproduce the issue

Install Cafe Variome
Create/join a Network
Create Discovery Groups
Create Source
Import/Upload Data
Generate indices (ES, UI)
Head to the Discover page

TODO

[ ] Inspect resources/js/cafevariome/query_builder.js

This is fixed now as of https://github.com/Cafe-Variome/CafeVariome/commit/c2b73d5f881f6bf9ca265da7ed2734c4cea42a46.

Attributes are still not being generated even after the latest and most recent updates and regenerating UI index. The following error is logged:

Review #4 and merge it @aryaei2000


[SPARK-40796][BUILD][FOLLOW-UP] Make Python code generation check only in master(3.4)

What changes were proposed in this pull request?
Make Python code generation check only in master(3.4)
Why are the changes needed?
linter is also triggered in 3.2 and 3.3
Does this PR introduce any user-facing change?
No
How was this patch tested?
CI

Merged to master.

thank you @HyukjinKwon


all: gofmt

Just ran
gofmt -w .

on the project root. That's all. Helps with legibility.

Sorry, we don't accept PRs yet. We use gerrit. See CONTRIBUTING.md.
However, the bigger problem is that the file you're changing is auto-generated, so we shouldn't be changing it here. I'll file a bug in the right place.


fix: Add more information if rav request is timing out

fixes #320

Pull Request Test Coverage Report for Build<PHONE_NUMBER>3
Details

3 of 7 (42.86%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.03%) to 68.27%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

tap-agent/src/agent/sender_allocation.rs
3
7
42.86%

Totals

Change from base Build<PHONE_NUMBER>5:
-0.03%

Covered Lines:
4215

Relevant Lines:
6174

💛  - Coveralls


Typings definitons for Typscript

I'm trying to use lunr in a fresh Angular 2 app installed with the cli.
In the app.module.ts I'm trying to import lunr with
import { lunr } from 'lunr';

But I keep getting errors about that not being a module, or it not finding it.  (yes lunr is in the node_modules folder)
I think/guess that it needs a Typings definition?  I found this one.  But it seems to be considerably out of date, and doesn't solve the problem
https://www.npmjs.com/package/@types/lunr
Or is that not what I need?
TIA

I don't have any experience with either typescript or angular 2 so I'm not really sure what to suggest. If you do figure out what is needed please update this issue with what you found.
Sent from my iPhone

On 21 Nov 2016, at 16:20, Lars Bell<EMAIL_ADDRESS>wrote:
I'm trying to use lunr in a fresh Angular 2 app installed with the cli.
In the app.module.ts I'm trying to import lunr with
import { lunr } from 'lunr';
``
But I keep getting errors about that not being a module, or it not finding it.  (yes lunr is in the node_modules folder)
I think/guess that it needs a Typings definition?  I found this one.  But it seems to be considerably out of date, and doesn't solve the problem
https://www.npmjs.com/package/@types/lunr
Or is that not what I need?
TIA
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Issue has gone stale, closing.

Hello! I have the same problem.

const lunr = require('lunr')
lurn/lurn.js not exported modules, require as file

I would like to open this issue up again.
We're using Lunr in a Typescript project and I may have some spare time to help. I would prefer to keep the typings in this project itself, for reasons including:

Fewer dependencies
Nice to keep definitions close to source code
Projects using lunr don't have to worry about definition version not matching source version
Versionin number makes more sense
Easier for me to contribute to this project then to definitely typed.
Remembering to keep up changes is easier

I'm happy to re-open the issue as I think having TypeScript definitions would be awesome.
That said, I really don't think they should live in this repository.
I'm not familiar with the process of creating a typings file, can this not be something that is automated for each new release? Or some kind of test that can highlight missing or incorrect typings?
Do you have some examples of other JavaScript libraries and where they keep their type definitions?

Types exist https://www.npmjs.com/package/@types/lunr

Hi @gnomeontherun,
Have you got an example or know docs website on how to implement Lunr.js search in Angular 2/4
Thanks

@kchiragowni There is nothing special to do to implement it with Angular 2+. Lunr is available on the global window, so you just access it there.

It seems that the typings at https://www.npmjs.com/package/@types/lunr is quite outdated. For example for lunr v2.1, the index is immutable, but the typings provided still defines the mutation functions such as add/remove on the index.

@olivernn axios is one successful library that maintains the typings within its project. The typings are declared in index.d.ts at root and declared in package.json as "typings": "./index.d.ts".
https://github.com/mzabriskie/axios
With that its typescript users enjoy the benefits which @ncphillips has mentioned, not having to manually add typings from @types (DefinitelyTyped) and sometimes realize the typings are outdated and can't be relied upon.

@kchiragowni  : As @gnomeontherun said, there is really nothing special to do.
If you are using angular cli :
npm install --save lunr
npm install --save-dev @types/lunr

In tsconfig.json, add :
{
  "compilerOptions": {
    "types":[
      "lunr"
    ]
  }
}

And in your component ts file, you can do the same thing as in the lunr guide :
import * as lunr from 'lunr';

const idx = lunr(function () {
  this.ref('name')
  this.field('text')

  documents.forEach(function (doc) {
    this.add(doc)
  }, this)
});

I have rewritten the typescript definitions for lunr based on v2.1.3 and submitted the pull request to DefinitelyTyped.
https://github.com/DefinitelyTyped/DefinitelyTyped/pull/19598
Once it's approved/merged and pushed to npm, typescript users should be able to install the latest definition with npm install --save-dev @types/lunr.
Still, it would be great if the definitions can live as part of this project, so that it gets updated as the project evolves.

@seantanly : Will we still be able to install the definition for v1.0.0 using npm install --save-dev @types/lunr ?

@jbouzekri Definitely, you simply need to define the version of the @types/lunr package you're going to install.
Looking at the current info,
npm info @types/lunr

The latest version is 0.5.29which I assume is the definition that supports lunr v1.0.0.
With that info, you just need to run npm install --save-dev<EMAIL_ADDRESS>which should peg your version of the package to ~0.5.29.
The new package version of the type definition should be 2.1.x.

@seantanly : thanks. It is a little confusing how there is a single repository of typings that produces all these npm @types registrations with different versions.

@jbouzekri DefinitelyTyped is a repository for all external typescript typings, and the repository is automated to publish npm packages under the scope @types upon successful PR merges. The version/author/misc info of the packages is determined by the magic comments inside index.d.ts. For example, the version that I have submitted indicated 2.1, thus the published package version should be 2.1.x.
https://github.com/seantanly/DefinitelyTyped/blob/84f0260d81d798231bab483740a43882d003a153/types/lunr/index.d.ts

@seantanly : Thank you for the explanation. I was looking at Microsoft/types-publisher but I was wondering from where these version numbers were coming from.


Support GitHub Enterprise 2.2

Currently we support back to GitHub Enterprise 3.1 (https://github.com/microsoft/vscode-pull-request-github/wiki#2-is-github-enterprise-supported). This decision was made by considering the following:

The version number of actual users filing issues on GitHub (collected by just asking users in issues what version they were using).
The difficulty in supporting older version (known issues in GHES 2 and test infra only goes back to 3.1).
Data that indicates that most Enterprise users are on 3.3 or higher.

This issue is intended to gauge the need/interest in support version 2.2.

@alexr00 Here is a non-comprehensive list of missing GraphQL object fields that I got on a quick try on GHE 2.21:

PullRequest.{viewerCanDisableAutoMerge, viewerCanEnableAutoMerge, autoMergeRequest, titleHTML}
PullRequestReviewThread.{isOutdated, path}
PullRequestChangedFile.viewerViewedState

The support definitely cannot reach all the way back to 2.2 (circa 2015, was it a typo?), but I wonder if the final releases of GHE 2 can be supported? In the general case, could the introspectivity of GraphQL schemas be used to provide graceful fallback? Also, was there any past release that actually supported GHE 2? (0.28 as the first attempt for GHE support does not work, complaining about the missing isOutdated field).
While there is the deprecation cycle, Enterprises are notoriously bad at keeping up to date for various reasons, so I suppose there might be more such cases in hide among all GHES installations.

I'm Github Enterprise 2.17.5 user. I can't login in by token.

Looks like the interest in GitHub Enterprise 2 is very low, which I'm happy to see because it has been deprecated for a while. Closing as out of scope.


Rev engine for alpha.

This has to wait until the engine bots have cycled. ETA unclear since the Linux engine build hasn't started yet.

Closing in favour of https://github.com/flutter/flutter/pull/9978


Fix typo

Hi @JonCanning, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

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

TTYL, MSBOT;

@JonCanning : Thanks for your contribution to the Azure documentation! The author, @rachelappel, has been notified to review your proposed change.

#sign-off


Error message during installation

We are getting this error message during installation. Any ideas on how to resolve this? Thanks.
make all
cd libs; make
make[1]: Entering directory '/home/microstaff/Software/mccortex/libs'
make[1]: *** No rule to make target 'xxHash/Makefile', needed by 'xxHash'.  Stop.
make[1]: Leaving directory '/home/microstaff/Software/mccortex/libs'
Makefile:324: recipe for target 'libs/string_buffer/string_buffer.h' failed
make: *** [libs/string_buffer/string_buffer.h] Error 2

Did you clone with:
git clone --recursive https://github.com/mcveanlab/mccortex

If you missed the --recursive, you need to run: git submodule update --init --recursive, then try make all again.

Thank you for you help. This has resolved the problem.

I am seeing a similar issue. I am trying to install in a Singularity container running Ubuntu Xenial and am getting the error log
$ make all
echo '#define CTX_VERSION ""' > src/global/version.h
mkdir -p bin
mkdir -p build/kmer31
mkdir -p build/global
mkdir -p build/basic
mkdir -p build/paths
mkdir -p build/graph31
mkdir -p build/graph_paths31
mkdir -p build/alignment31
mkdir -p build/tools31
mkdir -p build/commands31
mkdir -p build/tests31
cd libs; make
make[1]: Entering directory '/mccortex-0.2/libs'
make[1]: *** No rule to make target 'xxHash/Makefile', needed by 'xxHash'.  Stop.
make[1]: Leaving directory '/mccortex-0.2/libs'
Makefile:324: recipe for target 'libs/string_buffer/string_buffer.h' failed
make: *** [libs/string_buffer/string_buffer.h] Error 2

The provided solution of git clone --recursive is not relevant here as I am trying to install from the latest release source. Any ideas of how to fix this?


test/run_tests.pl: Do slowest tests first for parallel runs

This a follow-up on @romen's grand improvement on test execution time in #12326.
When being able to run four tests in parallel at a time, that reduces test run time to some 44% (compared to the 100% before).
It turns out that in our test suite there are two individual tests that take much longer than the others:
80-test_ssl_new and 99-test_fuzz. According to my experiments, each of them takes some 25% of the total time!
Since these have rather high ordinals, they are started rather late, which is on purpose for sequential runs.
However, when running all tests in parallel with HARNESS_JOBS being 4 or some other number that is much less than the number of tests, this leads to the undesirable effect that those two tests are started rather late and continue to run way beyond the finish time of the other (much faster) tests, which considerably reduces the actual gain through parallelism.
This PR makes sure that - as far as any of those slow tests is selected to run - these slow tests are started first,
such that effectively all the time they run in parallel to the other, much faster tests.
In particular, when 4 CPU cores are available to run the tests, for most of the total test execution time

one core runs ssl_test (aka 80-test_ssl_new),
another one runs asn1-test or other parts of 99-test_fuzz such as client-test and server-test,
while the two remaining cores run all the other tests.

According to what I just measured,
with HARNESS_JOBS=4 the gain in overall execution time is some further 18% (compared to not re-ordering the tests).
In other words, compared to sequential execution, the re-ordering reduces the execution time not only to some 44%
but to some 36% (taking the time for executing all tests sequentially as 100%).
Consequently, with this further enhancement of #12326, running all tests now typically takes only around a third of the time,
compared with the time the test suite took when running all tests sequentially.

Another possibility is to split test-fuzz into parts like fuzz-odd and fuzz-even which run the same program but pick odd or even tests.

Another possibility is to split test-fuzz into parts like fuzz-odd and fuzz-even which run the same program but pick odd or even tests.

Splitting the monolithic 25% of the total run time consumed by test_fuzz into 2 chunks of 12,5% each would not give a large benefit
because, due to their ordinal being 99, those two chunks would still be started after all other tests have been started
and because the test_ssl_new would still be a monolith and commence much later than all other tests,
still causing a major loss of effective parallelism.
So rather than gaining some further 18% due to the enhancement proposed here, I estimate the gain would be around 6%.

Sorry, I didn't mean "only split"  I meant "also split"

Sorry, I didn't mean "only split" I meant "also split"

So, you mean as a further enhancement on top of the other two.
Can you suggest a simple way of implementing that, at least for quick experimental purposes?

Can you suggest a simple way of implementing that, at least for quick experimental purposes?

See attached.
patch.txt

Can you suggest a simple way of implementing that, at least for quick experimental purposes?

See attached.
patch.txt

Thanks @richsalz for the suggestion how to split the fuzz tests.
I did various experiments using - and further adapting - it.
It turns out that also the fuzz tests have a very uneven run time distribution:
Each of asn1, client, and server take some 30% of the total fuzzing time,
while all the others take almost negligible time.
I first did the suggested split into "even" and "odd",
then also tried out splitting into asn1, client, server, and the sequence all others,
mostly using HARNESS_JOBS=4 according to my machine having a quad-core CPU.
There was no real gain doing so, even when I additionally prioritized the three CPU-intense fuzz tests,
which just had the effect that initially all four cores had 100% load for a while.
So in the end I see no advantage in splitting up the fuzz tests,
but at least the suggestion was a good motivation and basis for cleaning up 99-test_fuzz.t and
re-structuring it a little such that one could easily do any splitting of the fuzz tests if desired.

I'd say the way of parallelizing the tests as implemented in this PR (based on #12326) should be rather optimal for use with 2, 3, or 4 cores because

the two by far most long running tests test_ssl_new and test_fuzz get started first and will keep 2 cores pretty evenly busy for long time, and
using 2 cores, all other tests are run thereafter with pretty even distribution
using 3 cores, all other tests are run in 1 parallel thread next to test_ssl_new and test_fuzz for long time,
and then until the end of the overall test run the remaining tests run in 3 parallel threads with pretty even distribution.
using 4 cores, all other tests are run in 2 parallel threads next to test_ssl_new and test_fuzz for most of the time,
and towards the end of the overall test run the rather small number of remaining tests run in 4 parallel threads with pretty even distribution.

Of course, the changes take only effect if HARNESS_JOBS is set to a value > 1,
i.e., they do not change anything for sequential runs.

I've squashed and rebased this PR.

This two Travis issues are unrelated.
@levitte, can this be approved now?

This pull request is ready to merge

Merged - thanks @levitte


how to android back button??

main.vue
methods: {
    handleBackButton () {
        if (this.$f7router.history.length > 1) {
             return this.$f7router.back();
         }
},
created () {
    document.addEventListener('deviceready', () => {
        document.addEventListener('backbutton', this.handleBackButton);
    });
}

backbutton not works...
Cannot read property 'history' of undefined
Cannot read property 'back' of undefined

You can use the back property:


LSP :: Error from the Language Server: Method 'textDocument/documentLink' not supported. (Method not Found)

I am just starting to use GLSL on doom emacs. I am getting an error in lsp-glsl mode ( please see below ).  Even the completions are not correct, meaning it is not giving completions for basic keywords like out , uniform. It gives a suggestion list on the pop up but not the correct one. However, flycheck red underline errors are visible. Below is the error I see.
Error on lsp-workspace-show-log
[Trace - 12:52:25 AM] Sending request 'textDocument/documentLink - (55)'.
Params: {
"textDocument": {
"uri":
}
}
[Trace - 12:52:25 AM] Received response 'textDocument/documentLink - (55)' in 5ms.
Result: {
"code": -32601,
"message": "Method 'textDocument/documentLink' not supported."
}
Versions :
emacs      29.1 master 28fb02492 ~/.config/emacs/
doom       3.0.0-pre PROFILE=@0 grafted, HEAD -> master, origin/master, origin/HEAD
3191349 2023-09-14 20:17:24 +0200 ~/.config/doom/
Here is the lsp-describe-session output
-[-] glslls:41290     |-[-] Buffers     |  -[+] textures.vert
-[-] Capabilities        |-[X] workspaceSymbolProvider: nil        |-[-] textDocumentSync:        |  |-[X] willSaveWaitUntil: nil        |  |-[X] willSave: nil        |  |-[-] save:        |  |  -[X] includeText: nil
|  |-[X] openClose: t
|  -[X] change: 1        |-[-] signatureHelpProvider:        |  -[X] triggerCharacters: []
|-[X] renameProvider: nil
|-[X] referencesProvider: nil
|-[X] hoverProvider: t
|-[X] experimental: nil
|-[-] executeCommandProvider:
|  -[X] commands: []        |-[X] documentSymbolProvider: nil        |-[X] documentRangeFormattingProvider: nil        |-[-] documentOnTypeFormattingProvider:        |  |-[X] moreTriggerCharacter: []        |  -[X] firstTriggerCharacter:
|-[-] documentLinkProvider:
|  -[X] resolveProvider: nil        |-[X] documentHighlightProvider: nil        |-[X] documentFormattingProvider: nil        |-[X] definitionProvider: t        |-[-] completionProvider:        |  |-[X] triggerCharacters: []        |  -[X] resolveProvider: nil
|-[-] codeLensProvider:
|  -[X] resolveProvider: nil        -[X] codeActionProvider: nil
Any help on this is highly appreciated. Thank you.

Any solutions? I met the same problem.

As per notice in the README, I don't maintain this project anymore and I'm searching for a new maintainer.


Sort problems

Description of the problem
Padding hack for alphabetical to alphanumeric sort requires more padding to work reliably:

@Robbie1977  - Looks like this is now fixed - with proper numeric sort?
If so, please close.

@Robbie1977  - Looks like this is now fixed - with proper numeric sort?
If so, please close.


Convert to npe2.

Codecov Report

Merging #1 (610ad2b) into main (040c5f2) will increase coverage by 53.52%.
The diff coverage is 95.71%.

@@             Coverage Diff             @@
##             main       #1       +/-   ##
===========================================
+ Coverage   42.18%   95.71%   +53.52%
===========================================
  Files           8        9        +1
  Lines         678      886      +208
===========================================
+ Hits          286      848      +562
+ Misses        392       38      -354

Impacted Files
Coverage Δ

src/napari_psf_analysis/__init__.py
50.00% <50.00%> (ø)

src/napari_psf_analysis/utils/plot_utils.py
88.54% <88.54%> (ø)

src/napari_psf_analysis/_dock_widget.py
91.10% <91.10%> (ø)

..._analysis/_tests/psf_analysis/test_psf_analysis.py
100.00% <100.00%> (ø)

src/napari_psf_analysis/_tests/test_dock_widget.py
100.00% <100.00%> (ø)

...napari_psf_analysis/_tests/utils/test_gaussians.py
100.00% <100.00%> (ø)

...rc/napari_psf_analysis/psf_analysis/PSFAnalysis.py
100.00% <100.00%> (ø)

src/napari_psf_analysis/utils/gaussians.py
100.00% <100.00%> (ø)

src/napari_psf_analysis/utils/psf_lut.py
100.00% <100.00%> (ø)

src/napari_psf_measures/utils/psf_lut.py

... and 5 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 a3d5755...610ad2b. Read the comment docs.


Provide ORF/codon information for each position in the table

Not sure how to do this when a gene/protein is not selected... I guess just assume that we're in gene mode?

Closing - removed data table from site


[Candidate 3v3 Tournament C ZH v1] Soldiers have difficulties entering 1 of 4 bunkers from ramp

Observed behavior
Soldiers have difficulties entering 1 of 4 bunkers from ramp. Some or all of them do not enter the bunker and stop moving at the cliff.
Expected behavior
Soldiers can enter all bunkers from the ramp.
Screenshots

Bunkers removed and replaced with Guard Towers. I will call this fixed


Align definition of scale factor with Zero-Noise Extrapolation literature

The mitigate_with_zne API in Catalyst accepts a scale_factors argument, which represents a range of scalar factors by which the circuit is scaled.
In the literature of Zero-Noise Extrapolation ^1, a scale factor value $\lambda$ is the ratio between the number of gates of the scaled circuit and the number of gates of the original circuit. However, in the Catalyst implementation, the term scale factor is used to denote the number $n$ of foldings of the circuit.
The relation between the two definitions is $\lambda = 1 + 2n$.
For example, scale_factor = 1 (i.e., $\lambda=1$, $n=0$) means that the circuit is not folded.
For  scale_factor = 3 ($\lambda=3$, $n=1$), we have that the circuit is folded once
$$C \rightarrow C(C^{\dagger}C)$$
and the number of gates in the scaled circuit is three times the number of gates in the original circuit.
(See ^2 for a discussion on odd/even/non-integer scale factors.)

This issue is about aligning the definition of scale factor in Catalyst with the literature as above, by either renaming the scale_factors argument in the API, or assigning a new meaning to it.

Implementation in non-catalyst pennylane, for reference: https://github.com/PennyLaneAI/pennylane/blob/1d220cf6d69cbf60c99c5318b5137b69f7d6d30d/pennylane/transforms/mitigate.py#L214-L217

I will tackle that in the upcoming days :+1:

Nice, thanks @rmoyard. Please keep me in the review loop of the design and PRs.
Is the plan to do the same as Pennylane, that is, convert the scale factor in a folding factor and keeping the folding as is? Is it going to be in the frontend or in the dialect?

Yes I think that is the best, I will either add some restrictions because we don't support the fraction scale or just just ignore the fraction scale.
num_global_folds, _ = _divmod(scale_factor - 1, 2)

~num_global_folds~num_folds, since this will have to be the same way for both global and local folding.

Solved by #1120.
I will create a separate issue/feature request for non-integer and fraction scale.


[otbn] Specify memory accesses must be aligned

Fixes #2782

Can you file a follow-up to define what "error" means? This will most likely be something like a "internal processor error alert", which needs to get added to the spec.

I'd intentionally left it vague as we hadn't done any work on specifying the error reporting side of things.
Happy to do a new PR that gives a view on how that should look.

I'd intentionally left it vague as we hadn't done any work on specifying the error reporting side of things.

Yes, that's fine. I only meant a follow-up issue to keep track of it, no need to address it right away.

I'd intentionally left it vague as we hadn't done any work on specifying the error reporting side of things.

Yes, that's fine. I only meant a follow-up issue to keep track of it, no need to address it right away.

What I envision is pretty bare bones but yes maybe I'll begin with an issue.

LGTM!


0.7-beta Resources are missing a way to manually update them

Is your feature request related to a problem? Please describe.
We were able to set the resource value in the previous version of leptos.
This is relevant when doing optimistic updates.
Describe the solution you'd like
Reimplement it

Just out of curiosity: Do you find yourself mostly using this with:

Resources with an empty source signal (Resource::new(|| (), /* ... */))
Resources with a source signal they're responding to (Resource::new(move || some_value.get(), |value| /* ... */))
Both

I'm mostly just asking from a design perspective. It's fine to make resources in general writeable as they currently are, but it's worth considering whether we should split them into
A) An AsyncSignal that is initialized asynchronously/serialized from server to client, but then mutated like a regular signal (either synchronously or asynchronously), and
B) A Resource that is derived from other values and loads asynchronously (how it currently works in 0.7), but can't be mutated itself
Of course maybe mutating something that's also derived is a common pattern and I should just make it the way it was in 0.6, but I'm curious, since we don't have two sources of truth like this (either a local mutation or a reactively-triggered reload) for other derived types, like derived signals or memos.

Currently, I use it with a source signal use_params_map.get() to get the project id from the url.
I dont think that mutating something thats derived is a common pattern, per se.
(At least) the asynchronous nature poses edge cases, where the derivative isnt updated immediately. If it was immediate, I would go with a much simpler data flow.

For completeness lets take the edge case of updating a db entry.
Lets imagine a db entry which can be updated by the client.

client fetches entry
client mutates entry
(client may acknowledge prematurely here)
client sends update request
db replicates the update
db sends acknowledging response
client receives response
client may acknowledge here
client may invalidate here

An acknowledgement triggers the local mutation of the resource.
An acknowledging server response is generally something akin to Result<(), Err>. The server does not send the updated value back.
This is because we do not replace the currently set value with the server value. The client may already acknowledged another update prematurely. If the client and the server went somehow out of sync (e.g. 2 tabs where the same resource was mutated) and the server errors because the version number doesnt match, we can invalidate the resource to refetch. Obviously, the user interaction has to be repeated, which is a minus.

Invalidate
Acknowledge prematurely
Acknowledge on replication
never Acknowledge

always Invalidate
Optimisticly shows changes, but refetches even if the update was successful. Because we show changes immediately the user does not have to wait for the update to be acknowledged by the server and can mutate it again, instantly
Only shows changes, when the server acknowledged it. First we acknowledge that everything is correct, then we refetch. Does not make sense
This is the leptos resource. We invalidate when the source signal changes

Invalidate on version Err
Optimisticly shows changes, only refetches if out of sync. Because we show changes immediately the user does not have to wait for the update to be acknowledged by the server and can mutate it again, instantly
Only shows changes when the server acknowledged it. We only refetch when out of sync
Since we never acknowlegde and only refetch when we are out of sync - we are out of sync after the first update. Does not make sense

never Invalidate
Optimisticly shows changes, but cant recover from out of sync. Because we show changes immediately the user does not have to wait for the update to be acknowledged by the server and can mutate it again, instantly
Only shows changes when the server acknowledged it. Cant recover from out of sync
One-time fetch. Never changes locally. Doesnt make sense

Everything other than never acknowledge requires a local mutation.


could not clone the Skeleton source code

Revel can't clone the skeleton
>> revel new -a app
Revel executing: create a skeleton Revel application
CRIT  13:23:19 revel_logger.go:59: Abort: could not clone the  Skeleton  source code:  path=https://github.com/revel/skeletons:basic/bootstrap4  output=

specs:
>> go version
go version go1.17.1 windows/amd64

Hi, it helped me to install git and mercurial [https://revel.github.io/tutorial/gettingstarted.html#install_git_and_hg](install guide)

Yes git is part of the requirements see here http://revel.github.io/tutorial/gettingstarted.html#install_git_and_hg


FrankDoc support for digester rules for self registering elements

❗ please do not add sensitive information in issues, you can provide extra information via email using issue number as reference ❗
Describe the issue
The FrankDoc generator currently cannot handle digester-rules.xml for elements that do not have a direct relation with a parent element, like JmsRealms and SapSystems, and in a way also for Configuration. The FrankDoc generator currently needs a 'registerMethod' attribute to determine from the Java code the type of these elements.
In absence of a 'registerMethod' attribute the FrankDoc generator should determine the type from the 'object' attribute, the 'beanClass' attribute, or from (when necessary new to introduce) 'type' attribute.
The hierarchical location in the configuration file should be determined from the pattern.
Example configurations:
	<rule pattern="configuration/jmsRealms" type="nl.nn.adapterframework.jms.JmsRealms" factory="nl.nn.adapterframework.configuration.digester.JmsRealmsFactory"/>
	<rule pattern="configuration/sapSystems" object="nl.nn.adapterframework.extensions.sap.SapSystems"/>

Reporter
Gerrit

I don't think that this will simplify the current situtation. I agree that adding dummy methods such as setSapSystems in Configuration is kinda dumb, but automagically determining it would make the relationship between elements even more confusing. There are use cases where these register methods are actually extremly important. A SenderSeries for example can contain n senders, while a SenderWrapper can only contain one. The set and add methods are used to determine the cardinality. Not including these methods in some use cases and including them in some use cases would make everything even more implicit and confusing.
Another thought I had was adding a @DigesterRegisterMethod to all these set and add methods. It doesn't have any functionallity and merely serves as documentation that this method is unused, but is important for the digester. This also has the benefit of easily being able to find these methods using the annotation.