UI frequently locks up

I have this happen multiple times an hour where the UI becomes unresponsive and when I press F3 it also stops updating and I'm forced to restart the game. Not sure if this is a content or engine issue.
I haven't really found a reliable reproduction for it but when I do I'll dump it here.

Has this been reported of again in the last few months?


any insight you could provide would be super appreciated

Infracost trips on something in your module: infracost/infracost#1968.
It is unlikely anything wrong with your module, but I was hoping you might have some insight, or maybe the infracost devs will have questions that you can easily answer.

I've responded on that issue.


[Documentation] Fix links from networking to navigation in The Basics.

Fixes #8611.
Once this lands, we may want to cherry-pick it into 0.29 to fix the broken links.

@facebook-github-bot shipit

Thanks for importing. If you are an FB employee go to Phabricator to review.


Support MIG tables

@siddharth-krishna would you be up for this one? 😄

Sure! Could you give me some pointers on the details of the task? Should I look at times doc part 4? Thanks

Unfortunatelly, I don't think there is much there...
Basically, it works as a kind of a combinaton of the UPD / INS variants, i.e. the value is obtained as UPD, but it's added as INS with some of its properties changed. For example, in the following table an existing year1 value is multiplied by 0.9 and is inserted as year2.

Attribute
Year1
Year2
SourceScen
AllRegions
Pset_PN

NCAP_COST
2020
2030
ELC_EIA_AEO2022
*0.9
E_NUC*01

Know columns for this table type include attribute2, commodity2, etc. To be able to generalise table processing, if empty, I think, values for those fields should be filled using attribute, commodity, etc.

Thanks. I'll take a crack at it!

In Demo 4, we have this MIG table that has a year2 column but no year. Does this mean we just insert the value 5 for year 0 (i.e. if we have no year value then year2 cannot be written in terms of it, e.g. *0.9).
sheetname: Interpol_Extrapol_Defaults
range: B4:G6
filename: benchmarks/xlsx/DemoS_004/SysSettings.xlsx
tag: ~TFM_MIG
types: LimType (object), Attribute (object), Year2 (object), AllRegions (object), Pset_PN (object)
LimType,Attribute,Year2,AllRegions,Pset_PN
UP,ACT_BND,0,5,

Also, would the output data be the same if we replaced the TFM_MIG table above with the following TFM_UPD one? Perhaps one way to implement MIG tables is to reduce them to UPD tables that have the same result?
tag: ~TFM_UPD
LimType,Attribute,Year,AllRegions,Pset_PN
UP,ACT_BND,0,5,*

(i.e. if we have no year value then year2 cannot be written in terms of it, e.g. *0.9)

Unless not having year means any/every year for which attribute is present... *0.9 then becomes problematic in case multiple records are present (i.e. how to assign them to a single year2)? However, since in our case there is just 5 (i.e. no multiplication), there would not be any ambiguity.
The example of an TFM_UPD table would/should not work, because it requires a pre-existing record with year=0. A TFM_INS on the other hand would work. However, compared to TFM_MIG, it would create a record with year=0 even if there is no data for any other years specified.

There is some discussion on specifying interpolation settings in Veda 2.0 (and how it is different from Veda-FE) here


ISSUE #73 Use touchTap event instead of touchstart.

So we need a tapEvent since react doesnt support it (yet). It's possible to do a custom solution that saves touchStarts position and a timestamp. Then onTouchEnd compare that position and check how long time that has passed. This way we can ignore scrolling and "long touches".
A faster and more clean solution is the [react-tap-event-plugin] (https://github.com/zilverline/react-tap-event-plugin/blob/master/README.md). It hooks into reacts event system and adds a touchTap event.
Then when react adds touchTap event its easy to remove this dependency.
From react-tap-event-plugin:
You've probably heard of iOS's dreaded 300ms tap delay.  React's onClick attribute falls prey to it.  Facebook's working on a solution in the form of TapEventPlugin, but it won't be made available until 1.0.
If you're reading this, you're probably working on a project that can't wait until they figure out how they want to publish it.  This repo is for you.
When Facebook solves #436 and #1170, this repo will disappear.

If you want to try it out on a phone you could change server.js to:
}).listen(3000, 'localhost', function(err, result) {
}).listen(3000, '', function(err, result) {
This way you can surf to your ip instead of using localhost. This is also possible to do from your phone as long as you are on the same network :)

Thanks a lot!

@bachstatter Including react-tap-event-plugin in react-autosuggest presents a challenge: If another 3rd party component or the app itself uses react-tap-event-plugin, we'll get:

Uncaught Error: Invariant Violation: EventPluginRegistry: Cannot inject two different event plugins using the same name, TapEventPlugin.

See: https://github.com/zilverline/react-tap-event-plugin/issues/47
What are your thoughts about not including react-tap-event-plugin as part of react-autosuggest, and make it clear in the readme that it needs to be included manually to support mobile devices? Alternatively, we could add a config option in react-autosuggest to conditionally include react-tap-event-plugin. Or, maybe you have a better idea?

Thats an interesting challenge. I'm not sure if the best solution is to add a config option or just some instructions in the readme.
I found a third solution, we can find all events in the EventPluginRegistry. This if statement is false before injectTapEventPlugin() is invoked and true after. I'm not sure how reliable this is, but it seems to work.
import { registrationNameModules } from 'react/lib/EventPluginRegistry';

if (!registrationNameModules.onTouchTap) {
  injectTapEventPlugin();
}

What do you think? We could wait and see if zilverline respond to your issue.

@bachstatter Checking registrationNameModules.onTouchTap is problematic, I think. If some other library is doing something with onTouchTap, and it run first, our code will do nothing. Or, if react-autosuggest runs first, we'll break the other plugin functionality.

The first case should be fine, since if onTouchTap is injected by some other library we wouldn't need to do it. But it might break other projected trying to use onTouchTap.
We could use https://github.com/JedWatson/react-tappable and wrap each item with the a Tappable component.
I'm not sure which solution is best...


spec m.login.msisdn UI auth type

added as part of msisdn registration / signin

gdocs link would be super-helpful here, @dbkr

https://docs.google.com/document/d/1-6ZSSW5YvCGhVFDyD2QExAUAdpCWjccvJT5xiyTTG2Y/edit#heading=h.79ot48krpkq7

it turns out that when we are talking about UI auth we don't mean UI auth, we mean /login, which makes this a dup of #829

Sorry, there is a separate msisdn flow for UI auth that needs spec (it's what we use to register with a msisdn).
The doc for this is here: https://docs.google.com/document/d/1oBJ86MfFGZ4TE4YaM8I9ngY7R3FED74122jRM9C54-Y/edit


Customized flags for backendRuntimes

What would you like to be added:
Right now, we have at most two inferenceModes in backendRuntime, one is Default, another is  SpeculativeDecoding, what if people wants to customized there flags for easy usage and refer to the mode in the backendRuntimeConfig, considering flags are really really complex in the inference engine.
Some of our users have little knowledge with the inference engine, so they have no idea how to set the flags to make the inference engine perform better, where this can help.
Generally looks like:
  backendRuntimeConfig:
    mode: customziedOne
    resources:
      limits:
        cpu: 8
        memory: "16Gi"

apiVersion: inference.llmaz.io/v1alpha1
kind: BackendRuntime
metadata:
  labels:
    app.kubernetes.io/name: backendruntime
    app.kubernetes.io/part-of: llmaz
    app.kubernetes.io/created-by: llmaz
  name: vllm
spec:
  args:
    - mode: Default
      flags:
        - --model
        - "{{ .ModelPath }}"
        - --served-model-name
        - "{{ .ModelName }}"
        - --host
        - "<IP_ADDRESS>"
        - --port
        - "8080"
    - mode: CustomizedOne # new added.

Why is this needed:
Better to manage the flags and provide some best practices to the users.
Completion requirements:
This enhancement requires the following artifacts:

[x] Design doc
[x] API change
[x] Docs update

The artifacts should be linked in subsequent comments.

/kind feature

Waiting for feedbacks.


UI/UX Design category added

Vishal Saraiwal here, I have added UI Design tools to the New category to the menu and also added its tools here in db JSON.
I have added 9 UI Design Tools to Websites.

Are all the tools you added free? Also, could you shorten the description of the Unblast UI Templates?

also attach the issue you are solving

@JasonDsouza212 , Yes all the tools are free and also i make a new pull request please accept it now


Create an school website

I can Create an School Website for you

Thank you very much i would

`---
title: 'About '
shortTitle: ''
intro: 'Article intro. See tips for a great intro below.'
product: "optional product callout"
type: overview
topics:

topic
versions:
version

{% comment %}

Follow the guidelines in https://docs.github.com/contributing/writing-for-github-docs/content-model#conceptual to write this article.
Great intros give readers a quick understanding of what's in the article, so they can tell whether it's relevant to them before moving ahead. For more tips, see https://docs.github.com/contributing/writing-for-github-docs/content-model
For product callout info, see https://github.com/github/docs/tree/main/content#product
For product version instructions, see https://github.com/github/docs/tree/main/content#versioning
Remove these comments from your article file when you're done writing.
{% endcomment %}

A section here
{% comment %}
Write one or two paragraphs about the main idea of your topic, as a summary.
Make sure you don't have any content that isn't preceded by a header, or it won't be linkable in our table of contents.
{% endcomment %}
Another section here
{% comment %}
Write one or two paragraphs about another element of your topic.
Keep adding headers and sections until you've completed your article.
{% endcomment %}
Further reading
{% comment %}
Optionally, include a bulleted list of related articles the user can reference to extend the concepts covered in this article. Consider linking to procedural articles or tutorials that help the user use the information in your article.
{% endcomment %}

"Article title"`


Add info about using urlencoded client_id

To get the client working, one needs to use the url encoded version of the API client_id found on the Barentswatch "min side". Non url encoded client_id throws a 401 error

Fixed by making sure that client_id always is url encoded by the client.


Status page - markdown transform sometimes yields garbage

Sometimes Markdown generates garbage (e.g. repetitious and incorrect HTML) when we call Transform.
Restarting the service has been shown to fix the issue.
Markdown may not be thread-safe, or it may start to have issues over time.

This was fixed and deployed


cargo-credential-1password: Fix README

What does this PR try to resolve?
The README.md file of the cargo-credential-1password package does not match the implemented reality (anymore?).

--sign-in-address and --email are not actually supported by the implementation
manually calling op signin appears to be unnecessary

This PR also adds configuration instructions directly to the README.md so that they show up on crates.io.

Thanks, I went ahead and bumped the version to fix the check and get the docs updated.
@bors r+

:pushpin: Commit 6b7e2023a5a47a67f428080864a79278c9f7c156 has been approved by ehuss
It is now in the queue for this repository.

:hourglass: Testing commit 6b7e2023a5a47a67f428080864a79278c9f7c156 with merge 85273ad0bb92d120c8a2d4727d9ec7824e647240...


Telemetry: Add new metrics for new v2.2.0 key features

Version: v2.2.0
What kind of request is this (question/bug/enhancement/feature request):
Enhancement
Enhancement Details:
We should add new metrics to telemetry for new v2.2 features. For example, we currently have no way of knowing how many people are utilizing Multi-Cluster Apps and Monitoring.
Items

[x]  "#" of Cluster Templates, enforcement on/off - Ricky
[x] "#" of HPA - Caleb
[x] ~"#" of Cloud Credentials - Ricky~
[x] ~"#" of Node Templates~
[x] Istio enabled - Ricky
[x] Monitoring enabled - Ricky
[x] Logging enabled/provider- Ricky
[x] # Pipeline enabled - Ricky
[x] Pipeline feature enabled - Ricky
[x] # Pipeline per provider enable - Ricky
[x] Double check new auth providers are reporting (google) - Caleb
[x] library apps counter - Ricky/Caleb
[x] Info about CloudProvider enabled in RKE config, see Alena's comment - Caleb

-- EDIT (Ricky)
How to test:

go to settings and set "telemetry-opt" to "on"
go to rancher_url/v1-telemetry
perform action for stat being tested and refresh v1-telemetry. Confirm data has been incremented, changed, toggled, etc. (which ever is appropriate for particular metric)

Items specific testing notes:

'#' of Cluster Templates and enforcement

Create new cluster template and check metric. In setting toggle "cluster-template-enforcement" and check metric.

'#' of HPA

With an app already live, go to resources -> hpa -> add hpa and create one targeting your workload. In telemetry it will show up under project/hpa.

'#' of Cluster Credentials

Create a few new cluster credentials and confirm that metrics matches number of cloud credentials.

Istio, monitoring, logging

Enable each and confirm it is reflected in metrics

'#' of Pipeline enabled

Enable example pipelines and confirm that count is reflected in metric.

Pipeline feature enabled:

Setup any pipeline provider and check that metric shows pipeline feature is enabled.

'#' of pipeline per provider

Create pipelines in diff projects with diff provider and confirm counts are reflected.

Double check new auth providers are reporting

Setup an auth provider, if possible use google as that is newest. Add some users from it. Now in telemetry under install/users you will see both local and google specific users and groups.

Library apps counter

Add a few applications in various clusters, now in telemetry under project/charts you should see them listed.

Info about CloudProvider enabled in RKE config, see Alena's comment

Create a cluster with RKE (like ec2) and now in telemetry under cluster/cloudProvider you should see 'aws'.

Firstly, we need to enumerate all the new features that need added.
@cloudnautique maybe you can tell us what you want?
I think I heard @tfiduccia and @vincent99 talking about this. Do yall have specifics? Not just features, but the aspects of those features you want tracked.
Going to be honest, with v2.3.0 date looming, this is on the chopping block for me, but I think it should be a fast follow up in v2.3.1. or 2. Will leave it in for now in case we do have bandwidth for it.
@rmweir this should be prioritized below any bugs.

catalogs deploy in Library charts ?

testing notes in description

Version: master-head (v2.3) (9/9/19)
Upon opting into telemetry and then hitting the v1-telemetry endpoint I get an HTTP 502.
Rancher server debug logs show:
2019/09/10 01:22:50 http: proxy error: dial tcp <IP_ADDRESS>:8114: connect: connection refused
2019/09/10 01:24:47 [DEBUG] Requesting user: user-v8f26, Requesting groups: [system:authenticated] Impersonate user:  Impersonate group: []
2019/09/10 01:24:47 [DEBUG] Triggering auth refresh on user-v8f26
2019/09/10 01:24:47 [DEBUG] Skipping refresh for user-v8f26 due to max-age
2019/09/10 01:24:47 http: proxy error: dial tcp <IP_ADDRESS>:8114: connect: connection refused
2019/09/10 01:24:47 [DEBUG] 2019/09/10 01:24:47 http: TLS handshake error from REDACTED_IP:33026: remote error: tls: unknown certificate
2019/09/10 01:24:47 [DEBUG] 2019/09/10 01:24:47 http: TLS handshake error from REDACTED_IP:47049: remote error: tls: unknown certificate

Can confirm the new release binary isn't working. Also not all commits made it into the release. Looking into it.

@davidnuzik new working telemetry binary in rancher master branch now

Testing note: test with rc3

All areas have been validated now. Please reference my comment above with the checkboxes: https://github.com/rancher/rancher/issues/19231#issuecomment-530592365


Will there be any executable edition?

I really like this project and it is really handy but I wonder if there could be any ".exe" release or "elf" for Linux. It would be really great for systems with low space and which wouldn't require node at all.
P.S. Flair this as Discussion

Some node -> binary systems:
https://www.npmjs.com/package/pkg
https://www.kidsil.net/2020/03/nodejs-to-binary/

Some node -> binary systems:
https://www.npmjs.com/package/pkg https://www.kidsil.net/2020/03/nodejs-to-binary/

You need node installed to run pkg binaries. I tried it. Doesn't work.

Pkg seems to support it:
"Now you can use your output executable app.exe as a standalone compiler that does not require Node or NPM anymore."
https://dev.to/jochemstoel/bundle-your-node-app-to-a-single-executable-for-windows-linux-and-osx-2c89


Extract shader and material storage

Extract our global variable, shader and material storage classes

I'm still hunting a bug when exiting where it looks like it frees up materials before meshes are destroyed with the result its accessing materials while cleaning up that are no longer applicable.
It could also be that they are not removed from the dirty list correct (seems to go past them)
But I've been working on this all day and my brain is fried.
Put it ready for review because this is 99% complete and this one is HUGE

Note, CI is happy now that I've added an extra NULL condition check however on exit of the application I'm still getting the errors mentioned in the previous post around Materials being accessed for which the RID is no longer valid.
I'm stuck on knowing why.

Oh FFS... Just found out the material errors on close also happen in master and were probably introduced by something else...
Needs to be fixed but I don't think they are introduced by this PR so I call this ready for full review.

By looking at it, I now feel materials, shaders and global variables could be a single file (Renderer::Material) since more or less they are all part of the same thing and interact at the very low level.

Following this logic it may make more sense to have:
Renderer::MeshStorage (containing mesh, multimesh and skeleton)
Renderer::LightStorage (containing all light information)
Renderer::GIStorage (containing reflection probe, voxelGI and lightmap) // <- Either this or we make GI a whole object merging storage and logic
Renderer::Particles (containing both storage and particle system logic)
Renderer::VolumetricFog (containing fog storage, fog volume and fog logic, including volumetric fog?)
Renderer::RenderTarget (containing render target data)
I would not be so afraid to mix up logic and storage for many things that make sense.
The problem is mostly that we have some functions like:
virtual RS::InstanceType get_base_type(RID p_rid) const
or
virtual void base_update_dependency(RID p_base, DependencyTracker *p_instance) = 0;
That kind of relies on everything being in the same place.

Renderer::GIStorage (containing reflection probe, voxelGI and lightmap) // <- Either this or we make GI a whole object merging storage and logic, or separate out ReflectionProbe.

Shouldn't reflection probes go together with decals, since both are clustered elements?

Looks good to me! Pending @clayjohn to re-review I guess.

When I try to compile after this commit, (Windows, MSVC version 14.1, arch amd64, bits=64), I'm getting an error saying the Shader class is ambiguous:
CompilationError.txt
I imagine other compilers have better methods of disambiguating, but I was able to fix it on my end by making the namespace reference explicit
Is this correct?


expose csi and ccm logs to the end user

How to categorize this PR?

/area logging
/kind enhancement
/priority normal
What this PR does / why we need it:
Add two new dashboards exposed to the end users which will show logs for Cloud Control Manager and the CSI Plugin Controller
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note:

New dashboards which expose logs for `cloud-controller-manager` and `csi-packet-controller`.

/cla


Pull cloud project with parameters failing

> lean cloud pull --project 15268993
Error: 1 validation error for QCParameter
type
  Field required [type=missing, input_value={'key': 'Test', 'value': ...x': 184.5, 'step': 12.3}, input_type=dict]
    For further information visit https://errors.pydantic.dev/2.0.1/v/missing

> lean --version
lean 1.0.157

I'm also getting a similar error when pulling. Seems this is because my cloud project has parameters and the CLI didn't recognize them correctly.
# lean login
┌──────────────────────────────────────────────── Announcements ─────────────────────────────────────────────────┐
│ 2022-08-26: We've added support for python 3.10 and deprecated python version 3.6.                             │
│ 2022-05-23: We've added new json based approach of adding new modules to reduce the overhead and duplications. │
│ 2022-02-02: We've added cloud live support for Samco and Zerodha brokerages for India Market                   │
│ 2022-01-26: We've added support for Samco brokerage for India Market and FTX.US Exchange                       │
│ 2021-11-17: We've added support for Kraken and FTX brokerages                                                  │
│ 2021-06-21: We've just released a new opening video of the CLI:                                                │
│             https://youtube.com/watch?v=QJibe1XpP-U                                                            │
│ 2021-06-21: Building an Algo on Privacy Keywords using TiingoNews:                                             │
│             https://quantconnect.com/blog/building-an-algo-on-privacy-keywords-using-tiingonews/               │
│ 2021-06-11: Check out our mini video series on how to use the CLI:                                             │
│             https://youtube.com/playlist?list=PLD7-B3LE6mz61Hojce6gKshv5-7Qo4y0r                               │
└────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘
Your user id and API token are needed to make authenticated requests to the QuantConnect API
You can request these credentials on https://www.quantconnect.com/account
Both will be saved in /root/.lean/credentials
User id: 76518
API token: ****************************************************************
Successfully logged in
# lean init
Select the organization to use for this Lean CLI instance: Yuke Wang
Using selected organization "Yuke Wang"
This command will create a Lean configuration file and data directory in the current directory
The current directory is not empty, continue? [y/N]: y
Downloading latest sample data from the Lean repository...
Download Progress 10.0 MB
Download Progress 30.0 MB
Download Progress 50.0 MB
Download Progress 70.0 MB
Download Progress 90.0 MB
Download Progress 110.0 MB
Download Progress 130.0 MB
Download Progress 150.0 MB
Download Progress 170.0 MB
Download Progress 190.0 MB
What should the default language for new projects be? (python, csharp) [python]:
The following objects have been created:
- lean.json contains the configuration used when running the LEAN engine locally
- data/ contains the data that is used when running the LEAN engine locally

The following documentation pages may be useful:
- Setting up local autocomplete: https://www.lean.io/docs/v2/lean-cli/projects/autocomplete
- Synchronizing projects with the cloud: https://www.lean.io/docs/v2/lean-cli/projects/cloud-synchronization

Here are some commands to get you going:
- Run `lean create-project "My Project"` to create a new project with starter code
- Run `lean cloud pull` to download all your QuantConnect projects to your local drive
- Run `lean backtest "My Project"` to backtest a project locally with the data in data/
# lean cloud pull
Error: 4 validation errors for QCParameter
min
  Field required [type=missing, input_value={'key': 'length', 'value': '20'}, input_type=dict]
    For further information visit https://errors.pydantic.dev/2.1.2/v/missing
max
  Field required [type=missing, input_value={'key': 'length', 'value': '20'}, input_type=dict]
    For further information visit https://errors.pydantic.dev/2.1.2/v/missing
step
  Field required [type=missing, input_value={'key': 'length', 'value': '20'}, input_type=dict]
    For further information visit https://errors.pydantic.dev/2.1.2/v/missing
type
  Field required [type=missing, input_value={'key': 'length', 'value': '20'}, input_type=dict]
    For further information visit https://errors.pydantic.dev/2.1.2/v/missing
# lean --version
lean 1.0.157
# python3 --version
Python 3.8.17
# cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

I have encountered similar issue. When running "lean cloud pull", the below error messages occurred:

When running "lean cloud push", only projects without built-in parameters can be pushed. Those with parameters generated the same error messages as above.

Many thanks to John and Martin. Problem solved!


WIP: publish to npm, and support more branch actions

publish to npm
support more branch actions, for One git alias.br = !git-br support list branches with description and other git branch actions.

fixed the tests, there was something about leaving the branches hanging between the tests, but now seems to work. Thank you!


New linter: SublimeLinter-contrib-coffee-jshint

https://github.com/univerio/SublimeLinter-contrib-coffee-jshint
Uses coffee-jshint to lint CoffeeScript files.

linter.py fails pep257 linting
unnecessary imports from __future__, this code only runs in python3.3

after those are fixed please make a release.
THANKS!!

Done. Release is 0.0.1.

It's been added to Package Control, and you should see it within an hour. Thanks again!


replace broken show function in GitHub API example

Closes #449

I've been following that issue today via email but wasn't on my computer to verify it for myself.
GitHub API library must have changed its method show() to getDetails() at some point.
Thanks for the PR!


enhancement: Update Otel HTTP semantic conventions

Description
Updated the Otel HTTP semantic conventions to the stable release version convention.
Previous Conventions(v1.20.0): https://github.com/open-telemetry/opentelemetry-specification/blob/v1.20.0/specification/trace/semantic_conventions/http.md#http-server
New Conventions(1.23.0): https://github.com/open-telemetry/semantic-conventions/blob/v1.23.0/docs/http/http-spans.md#http-server
I have not yet tested this PR and hence opened this as a draft, need knowledge transfer on how correct metrics can be traced and tested with Cerbos.
cc - @charithe
Fixes #1910
Checklist

[X] The PR title has the correct prefix
[X] PR is linked to the corresponding issue
[X] All commits are signed-off (git commit -s ...) to provide the DCO

Testing this is a bit difficult because you're essentially trying to verify the non-existence of something. I suppose you could make dropHighCardinalityLabels a noop and compare the before and after results to make sure the filtering worked.

make prometheus to start Prometheus
make dev-server to start Cerbos
make check-http to send some test requests
Inspect the labels of one of the http metrics (e.g. http_server_duration_milliseconds_count) in the Prometheus UI (http://localhost:9090)

@charithe as discussed over slack, you can merge it now if review is done.
Thanks


create before and after login version of Descriptions page

create WindeDesriptionBeforeLogin and BeerDescriptionBeforeLogin and exchange with login version

nice one Kenny!


Create Docker Image

To run the 'Hello World' demo using the Docker backend a Docker image containing flowserv is required.

Closed by commit 60e512312adc9dfeeb6a57514dc4a26855288440.


Confidence is unreliable

Browser
n.a. (server-issue)
Expected behavior
Robat sends a not-sure response if the message send by the client doesn't make any sense
Actual behavior
Robat sends the not-sure response on the most simple statements like "Hello" at times.
It seems like the confidence value is all over the place in actual use. Maybe we should reconsider this method of checking if we have a valid answer.. 🤔

We've removed confidence completely in #52


Migrate freeze-test to cpp (RIPD-1154)

Port all active tests in freeze-test.coffee to c++.

Left some minor comments. Test looks great, nice job @mellery451
👍

Current coverage is 65.52% (diff: 100%)

Merging #1934 into develop will increase coverage by 0.07%

@@            develop      #1934   diff @@
==========================================
  Files           698        698
  Lines         49745      49745
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits          32562      32597    +35
+ Misses        17183      17148    -35
  Partials          0          0

Powered by Codecov. Last update 4d7b1a3...1b737f9

Merged as 28ae522ea2d85d066ceeb23d30ade451fd1e424d.


prepare examples for using as manual tests

To be able to do:
$ cd ./examples/fully-featured
$ nix flake show .
$ nix build .#nixosConfigurations.Morty.config.system.build.toplevel

$ cd ./examples/somewhat-realistic
$ nix flake show .
$ nix build .#nixosConfigurations.HostnameOne.config.system.build.toplevel
$ nix build .#nixosConfigurations.HostnameTwo.config.system.build.toplevel

$ cd ./examples/fully-featured
$ nix flake show .
warning: creating lock file '/home/blaggacao/ghq/github.com/gytis-ivaskevicius/flake-utils-plus/examples/fully-featured/flake.lock'
warning: Git tree '/home/blaggacao/ghq/github.com/gytis-ivaskevicius/flake-utils-plus' is dirty
git+file:///home/blaggacao/ghq/github.com/gytis-ivaskevicius/flake-utils-plus?dir=examples%2ffully-featured
├───abc: unknown
├───apps
│   ├───aarch64-linux
error: not an app definition

$ cd ./examples/somewhat-realistic
$ nix flake show .
warning: Git tree '/home/blaggacao/ghq/github.com/gytis-ivaskevicius/flake-utils-plus' is dirty
git+file:///home/blaggacao/ghq/github.com/gytis-ivaskevicius/flake-utils-plus?dir=examples%2fsomewhat-realistic
├───nixosConfigurations
│   ├───HostnameOne: NixOS configuration
│   └───HostnameTwo: NixOS configuration
├───overlay: Nixpkgs overlay
└───pkgs: unknown
$ nix build .#nixosConfigurations.HostnameOne.config.system.toplevel
warning: Git tree '/home/blaggacao/ghq/github.com/gytis-ivaskevicius/flake-utils-plus' is dirty
error: cannot coerce a list to a string

       at /nix/store/60rlyq4bv010p2jqh42hxlyq8g297wfl-source/lib/modules.nix:150:89:

          149|           unifyModuleSyntax fallbackFile fallbackKey (applyIfFunction fallbackKey m args)
          150|         else unifyModuleSyntax (toString m) (toString m) (applyIfFunction (toString m) (import m) args);
             |                                                                                ^
          151|
(use '--show-trace' to show detailed location information)

I've added some commits to this branch on my fork: https://github.com/chvp/flake-utils-plus/tree/da/use-examples-as-tests
They solve the real failures in nix flake show and nix flake build. Building still doesn't succeed, since the nixos builder expects a root filesystem and a bootloader to be configured.

The somewhat-realistic example also has only one host in nix flake show, similar to what I reported in #6.

That does make sense, one of the hosts has the output = "darwinConfigurations" and nix flake show only shows hosts under nixosConfigurations because thats the only output it can recognize. But if you look in nix repl, or evaluate .#darwinConfigurations you might see the other host.
I'm not sure if thats what you are talking about, but this is something I have seen.

I'm not sure if thats what you are talking about, but this is something I have seen.
edit: looks like HostNameOne and HostNameTwo should be shown under nixosConfigurations, so it might be something else.

Just to make it clear: I was talking about the missing HostnameTwo in the flake's nixosConfigurations output.

@chvp Thank you! I just merged your art in here!

I see what @chvp reports on somewhat-realistic. I'll have a look at it later. It might be my fault.
@gytis-ivaskevicius other than that, I think this branch is ready to merge in staging snd should make (manual) testing a little easier.


Create 0000-01-02-sdwanms.md

added my first file in _posts folder and a comment in the middle of the code.

closing

close pull request


Make all URLs absolute

At the moment many of the URLs are relative in Postleaf .i.e /themes/empower-theme/css/styles.css
There are some performance improvements by having absolute URLs instead. http://website.com/themes/empower-theme/css/styles.css
Essentially the browser has less work to do to locate files with absolute URLs vs relative URLs.

To clarify, Postleaf uses root-relative URLs (e.g. /path/to/file.ext) as opposed to relative URLs (e.g. 'path/to/file.ext`), so the browser simply prepends the hostname, which doesn't incur a performance hit.
The reason I'm using root-relative URLs is because it makes stored content and backup files more portable. You can effortlessly clone the site and move it between dev/staging/production and you only need to modify a single .env file.
I'm closing this since storing absolute URLs doesn't provide any obvious benefit, but does make things more difficult. For example:

Postleaf would need to watch for changes to APP_URL in .env
On change, values in the database would need to be updated
Post content would need to be parsed to properly update URLs

Even if there were a performance hit, it would be on the client-side. In this type of app, it would be negligible. 🙂

I see you're point about portability. Hadn't thought of that.


Native Cheat Commands not recognized when BP Cheat Manager is used

I have a C++ CheatManager that inherits from UMetaCheatManager that has some cheats in it.
If my PlayerController has the native CheatManager set, then its commands work fine.
If my PlayerController has a BP derived CheatManager set, the commands are recognized for auto complete but don't actually work. Log states: Command not recognized

Thank you for bringing this issue to my attention. I'll address it in the upcoming UE5.4 update. I'll keep you updated once I've managed to reproduce and fix it.


Question about Ablation Experiments

Hi, thank you for your great work!
I have been exploring the codebase and noticed that the pointnet_type parameter can only be set to pointnet. When attempting to use other values, the code in pointnet_extractor.py raises a NotImplementedError with the message pointnet_type: {pointnet_type}. I wonder if that indicates only the DP3 encoder for point cloud data is currently supported in this repository.
In your paper, you mention Ablation Experiments with other 3D representations such as depth images, RGB-D images, and voxels, as well as DP3 encoder comparisons with other point cloud encoders like PointNet++, Point Transformer, etc.
Unfortunately, I couldn't find the corresponding code for these implementations in the repository.
Could you please provide guidance on the following:

Where can I find the code for processing other 3D representations (depth, RGB-D, voxel, etc.) and their corresponding DP3 encoders?
Where is the implementation for the other point cloud encoders (PointNet++, Point Transformer, etc.) mentioned in your paper?

Thank you very much for your time and support.
Best regards!

Hi, thank you for your interest. This code base only provides the implementation of DP3.
For other representations, you could refer to their original code.
For example:

the voxel encoder is from visual dexterity.
PointNet++ / PointTransformer/PointNeXt are available in openpoints
depth is already included, and is encoded by image encoder from Diffusion Policy.


Add build restart option

Can we benefit from what we've learnt with nvidia? And show the log above the button.

does it not do this? ... oh maybe I only implemented that for deploy
I want to implement this generally for goals

Although some failures may be non-transient and there should be no trying again. Eg a compile error is a build failure you wouldn't retry. As is deployment of an invalid artifact.


M1 Mac Support

GoReleaser supports darwin_arm64 and version 0.5.0 had this support

Cloning and running goreleaser build locally works just fine on 0.6.0. Perhaps the artifact did not upload?

This is an issue for us too, would be great to have this resolved, though 0.5.0 is fine for us for now.

Ahh yes good hinting @mhornbacher! It seems we will need to update some stuff to get this working again.

I think we'll need to upgrade GoReleaser according to https://goreleaser.com/deprecations/#builds-for-darwinarm64.
It might be a little hard to test exactly this script locally for you, but you could probably manually test it out against GoReleaser to reproduce this issue and then confirm upgrading fixes it and provide us PR if you're up for it. The line/file you are looking for should be https://github.com/buildkite/terraform-provider-buildkite/blob/da1f22856c3943620f6cd5bc404624e42b16a1a7/.buildkite/steps/release.sh#L48

@jradtilbrook I updated the download and tested a goreleaser build in docker-compose just as it is run in CD and it generated the binary just fine :)


AttributeError: 'Blob' object has no attribute 'mask'

AttributeError: 'Blob' object has no attribute 'mask'  @cs-chan  thanks!

Hi,
Please refer to the following paper to get the modified CAFFE library in order to use the mask attribute:
Han, S., Pool, J., Tran, J., & Dally, W. (2015). Learning both weights and connections for efficient neural network. In Advances in Neural Information Processing Systems (pp. 1135-1143).


Feature: Option to download beatmaps from mirror sites

It will be easy and fast to download beatmaps for non supporter users
but as you know, so many mirrors we have lol(NeriNyan, beatconnect, Chimu, sayobot, Mino...)
so my recommendation idea is allows the user to edit the download link except for the mapset id
for example)
https://api.nerinyan.moe/d/ + beatmapsetID
~~~~~~~~~~~~~~~~~~~~~~~~~~~
              ^
          editable

Thank you, that sounds like a good feature. I'll see what I can do


emacs-tree-sitter.org: use (require 'tree-sitter-langs)

The documentation as it is confusing: it basically says you have to
enable tree-sitter-mode, and stuff will just work. Well it actually
doesn't, because the variable tree-sitter-major-mode-language-alist
won't get set until you execute (require 'tree-sitter-langs).
And it is not clear at all that this line needs to be executed because
all you get is No language registered for major mode message. Usually
lack of (require) results in missing function definitions, so in this
case there's no reason a user seeing the error would think "aha, I need
a (require) call".
So let's avoid confusion by mentioning the (require) line explicitly.

This is an issue with autoloading. It should be fixed by https://github.com/emacs-tree-sitter/tree-sitter-langs/commit/55a444fd6c68801f76b6f4642a1c9b4e4ba6338f.
Please let me know if that helps.
Thanks for pointing out the potential confusion anyway! I'll update the error message, and add more clarifications on the role of tree-sitter-langs to the doc.

Thank you! What can be even  better than a documented problem? Having no problem at all! Thanks for the fix!


Binding Application Security Groups by organization admin

Issue
My goal is to create definition of security group as CF admin and let an organization admin bind them to his spaces. For example, there are 2 orgs: orgA and orgB and 4 user-provided-services:

orgA-dbProd
orgA-dbDev
orgB-dbProd
orgB-dbDev

I want to create them as CF admin :
# orgA
cf create-security-group orgA-dbProd ./orgA-dbProd.json
cf create-security-group orgA-dbDev ./orgA-dbDev.json
# orgB
cf create-security-group orgB-dbProd ./orgB-dbProd.json
cf create-security-group orgB-dbDev ./orgB-dbDev.json

and give the org admins rights to bind them to the org spaces:
# orgA
cf allow-bind-security-group orgA-dbProd orgA
cf allow-bind-security-group orgA-dbDev orgA
# orgB
cf allow-bind-security-group orgB-dbProd orgB
cf allow-bind-security-group orgB-dbDev orgB

and now admin should be able to bind them to the selected spaces.
Context
As a CF admin I don't want to have knowledge about org spaces configuration.
My responsibility is to configure org-level and let org-admin do his config.

@ssisil & @Gerg any thoughts here? This is somewhere in VAT's backlog for v3ification, but I don't know how much we've thought about something like allow-bind-security-group.

This flow reminds me of isolation segments. Isolation segments are admin-managed, but can be entitled to organizations, which then allows org-level configuration.


Remove the unimplemented monolithic upload section from the API

Signed-off-by: Richard Scothern<EMAIL_ADDRESS>

To be reinstated with #1170 (or equivalent)

Reluctant LGTM

LGTM on the presumption that this doc is premature to the implementation?

This should have been left in as part of the specification, even if it is unimplemented. The documentation provides guidelines for implementation.
If we need a separate API usage guide, we should do that. However, this is specification and should be treated as such.

Problem is, people outside docker are writing apps based on the spec. Perhaps each spec needs a major version number (e.g., 2.2) so that it matches the actual implementation of that version of the registry? That way, a future version (e.g., 2.5) could have a spec 2.5 and future functionality plans could go into that?

@cliffbdf https://github.com/docker/distribution/blob/master/docs/spec/api.md#changes has the versioning. Either way, the specification should not be used as an implementation guide. There needs to be a separate documentation indicating implementation status.
It is unfortunate that this change came without an update to the change log.
I really think this should be reverted.

A separate document indicating implementation status would work for me. (I am a user of the registry, writing code that accesses the registry via its API.) I suggest that if a separate implementation status doc is created, that the v2 spec mention that doc's location at the beginning of the v2 spec, so that one can easily find the implementation status.

So I now compute the digest manually - it does not match the directory name that contains the layer. But no problem. But I discovered that the digest must have the SHA format prepended to it - in this case, "sha256: ". I know that is in the docs somewhere, where digests are discussed, but it might be good to add it to the v2 spec since merely stating that the digest should be provided as a query string is probably not sufficient to inform people that the digest must prepend "sha256:". Just a suggestion :-)

@cliffbdf It is right there: https://github.com/docker/distribution/blob/master/docs/spec/api.md#content-digests. There is also this: https://godoc.org/github.com/docker/distribution/digest.

Indeed. Thanks!

On May 13, 2016, at 6:57 PM, Stephen Day<EMAIL_ADDRESS>wrote:
@cliffbdf https://github.com/cliffbdf It is right there: https://github.com/docker/distribution/blob/master/docs/spec/api.md#content-digests https://github.com/docker/distribution/blob/master/docs/spec/api.md#content-digests. There is also this: https://godoc.org/github.com/docker/distribution/digest https://godoc.org/github.com/docker/distribution/digest.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub https://github.com/docker/distribution/pull/1702#issuecomment-219178800

Indeed, someone in this group was nice enough to point me to some BNF for names: https://github.com/docker/distribution/blob/master/reference/reference.go#L4 I think that users of the API will greatly benefit from that BNF becoming part of the API spec. I had forgot to check it, and having it in the spec would have helped me to discover my digest syntax error (which would have saved Steve from having to point it out - thanks Steve!)
But now I am struggling with the "last mile" of posting an image to v2: I am getting a 400:
{"errors":[{"code":"MANIFEST_INVALID","message":"manifest invalid","detail":{}}]}
But my manifest appears valid, although it is not clear from the spec if the history and signature fields are required. I don't have either - so I hope they are not! I wish that the "detail" part of the message provided some details - would be very helpful ;-)

@cliffbdf I'd really recommend reading the client code. There are a number of comments and tests that will explain to all of these problems without having to have us explain each detail, possibly missing important aspects.
The problem here is that the signature field is a part of the manifest specification, which the API does some validation on. You'll have to refer the manifest specification for the specific revision you are interested in.

Ah, yes, I forgot that there is a separate manifest spec. Thanks Stephen!


[HOLD 48627][$250] [Search v2.1] Searching for expense with description [FINDME] crashes app

BUG: Searching for expense with description [FINDME] crashes app
From:
@alexbeaman
Action Performed:

Go to search page -> Description
Enter a description to search [FINDME]
Click search
Expected Result: Results should show
Actual Result: App shows "Hmmm...  it's not here" page
Platforms: Web at least
Version Number: Latest staging (maybe prod too)
Screenshots or Videos: :thread:
If you think the bug is part of a Wave or VIP project, please cross-post in that room. List in bookmarks above.

cc @Kicu @289Adam289 @Guccio163
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~021834291053186780504
Upwork Job ID:<PHONE_NUMBER>186780504
Last Price Increase: 2024-09-12

Issue OwnerCurrent Issue Owner: @

@luacmartins I think proposal from https://github.com/Expensify/App/issues/48627 will solve this issue

I agree. Pinged the contributor to also add this issue to the list of solved issues. Thanks!

This is solved by https://github.com/Expensify/App/pull/49229. Closing


Make sure the player always sees the latest version of the game state

We can use timestamps for that

While we use TCP connection, the players always see the latest version of the game state. If we change to UDP we can reopen this issue.


Implement "chants by CantusID" list page

like this one: https://cantus.uwaterloo.ca/id/ah50270. There should be a link to this list page on the last column of sequence list page.

implemented in 37e9fdca08146ee821eed959cbf16b84926faf12 and 2bf879482ae8ef676f471f8a935e50f12fe28f41


[WIP][OSF-7177] MFR errors to keen.io

Purpose:
OSF-7177
Add facility for logging errors to keen.io
Configure most salient errors to log to keen.io
Use python std library:logging logger/handler idiom
Changes:
Update exceptions to pass keen_data on raise
mfr/core/exceptions.py
mfr/extensions/codepygments/exceptions.py
mfr/extensions/image/exceptions.py
mfr/extensions/jasp/exceptions.py
Add logging keen_logger and handler keen_handler for use in logger/handler idiom
mfr/server/app.py
mfr/core/remote_logging.py
Configure keen_data for most salient errors
mfr/core/utils.py
mfr/extensions/codepygments/render.py
mfr/extensions/image/export.py
mfr/extensions/jasp/render.py
mfr/providers/osf/provider.py
Add call to keen_logger when error received by tornado.
Add generic keen_data for all keen_logger calls
mfr/server/handlers/core.py
Add config to settings for separate keen collection for errors
mfr/server/settings.py
Side effects
None
Configuration
Current requires an ID and Key be configured so as to allow for using a separate keen collection.
~/.cos/mfr-test.json
{
  "SERVER_CONFIG": {
    "ANALYTICS": {
      "KEEN": {
    ┆   "ERRORS": {
    ┆   ┆ "PROJECT_ID": "",
    ┆   ┆ "WRITE_KEY": ""
        },
.....

[#OSF-7177]

Closing in favor of ddba0dcfe3214.  The code to use the python logging module to handle keen error logging has been preserved as a feature branch.  This branch is just a crude extraction of the important parts and doesn't flake, compile, or merge cleanly into develop.  One day soon, though...


pull request for e2e test at 01/02/2017 20:26:11

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Some questions in reproducting results

I ran the code according to the guide in the README without modifying the code, but the results I get are a bit different from the paper, is there any possible reason for this?
My log here:
Namespace(device='cuda:3', data='./data/METR-LA', adjdata='./data/METR-LA/adj_mx.pkl', adjtype='doubletransition', seq_length=12, nhid=32, in_dim=2, num_nodes=207, batch_size=16, dropout=0.0, epochs=100, print_every=200, seed=-1, save='./experiment/METR-LA_0/TESTAM', expid=1, load_path=None, patience=15, lr_mul=1, n_warmup_steps=4000, quantile=0.7, is_quantile=False, warmup_epoch=0)
Train the model with 205435 parameters
start training...

Average Training Time: 189.2072 secs/epoch
Average Inference Time: 7.7535 secs
Training finished
The valid loss on best model is 2.9748
Evaluate best model on test data for horizon 1, Test MAE: 2.4027, Test MAPE: 0.0608, Test RMSE: 4.3709
Evaluate best model on test data for horizon 2, Test MAE: 2.6633, Test MAPE: 0.0696, Test RMSE: 5.1697
Evaluate best model on test data for horizon 3, Test MAE: 2.8549, Test MAPE: 0.0766, Test RMSE: 5.7345
Evaluate best model on test data for horizon 4, Test MAE: 3.0130, Test MAPE: 0.0829, Test RMSE: 6.1764
Evaluate best model on test data for horizon 5, Test MAE: 3.1466, Test MAPE: 0.0884, Test RMSE: 6.5392
Evaluate best model on test data for horizon 6, Test MAE: 3.2659, Test MAPE: 0.0935, Test RMSE: 6.8510
Evaluate best model on test data for horizon 7, Test MAE: 3.3701, Test MAPE: 0.0980, Test RMSE: 7.1191
Evaluate best model on test data for horizon 8, Test MAE: 3.4618, Test MAPE: 0.1019, Test RMSE: 7.3454
Evaluate best model on test data for horizon 9, Test MAE: 3.5433, Test MAPE: 0.1053, Test RMSE: 7.5382
Evaluate best model on test data for horizon 10, Test MAE: 3.6212, Test MAPE: 0.1085, Test RMSE: 7.7152
Evaluate best model on test data for horizon 11, Test MAE: 3.6942, Test MAPE: 0.1113, Test RMSE: 7.8761
Evaluate best model on test data for horizon 12, Test MAE: 3.7665, Test MAPE: 0.1141, Test RMSE: 8.0307
On average over 12 horizons, Test MAE: 3.2336, Test MAPE: 0.0926, Test RMSE: 6.7055
Total time spent: 7924.1520

Thank you for your great question.
TL;DR: It comes from the unstable route training during the initial phase. You can set warmup_epoch to stabilize/reproduce results.
Below are detailed explanation.
It may be caused by suboptimal routing due to the unstable initial route learning. You can see each expert's performance by running test.py, confirming that they are incorrectly routed. To fix such You may set the small warmup_epoch (e.g., 5 epochs) to stabilize them.
Actually, the current training sequence of gating networks is suboptimal and needs improvement; Which means, it may mislead the input to the second- or third-best expert. It is our future research goal and we try our best to improve such suboptimal route selection.
Further questions are welcome

Thank you for your prompt reply. I modified the warm epoch to 5 and the results did get better but it doesn't look like it exceeded the baseline in the original article. is there something else I need to tweak?
Here is the new log. I omit the first few epochs log to make it not so long.
Epoch: 048, Inference Time: 7.5892 secs
Epoch: 048, Train Loss: 3.0352, Train MAPE: 0.0679, Train RMSE: 5.1720, Valid Loss: 2.6798, Valid MAPE: 0.0738, Valid RMSE: 5.1405, Training Time: 185.3764/epoch
Early Termination!
Average Training Time: 187.4990 secs/epoch
Average Inference Time: 7.7179 secs
Training finished
The valid loss on best model is 2.6721
Evaluate best model on test data for horizon 1, Test MAE: 2.2504, Test MAPE: 0.0545, Test RMSE: 3.9607
Evaluate best model on test data for horizon 2, Test MAE: 2.4852, Test MAPE: 0.0621, Test RMSE: 4.6657
Evaluate best model on test data for horizon 3, Test MAE: 2.6497, Test MAPE: 0.0680, Test RMSE: 5.1444
Evaluate best model on test data for horizon 4, Test MAE: 2.7825, Test MAPE: 0.0731, Test RMSE: 5.5305
Evaluate best model on test data for horizon 5, Test MAE: 2.8924, Test MAPE: 0.0776, Test RMSE: 5.8434
Evaluate best model on test data for horizon 6, Test MAE: 2.9856, Test MAPE: 0.0815, Test RMSE: 6.1093
Evaluate best model on test data for horizon 7, Test MAE: 3.0703, Test MAPE: 0.0850, Test RMSE: 6.3443
Evaluate best model on test data for horizon 8, Test MAE: 3.1467, Test MAPE: 0.0881, Test RMSE: 6.5505
Evaluate best model on test data for horizon 9, Test MAE: 3.2150, Test MAPE: 0.0910, Test RMSE: 6.7311
Evaluate best model on test data for horizon 10, Test MAE: 3.2779, Test MAPE: 0.0936, Test RMSE: 6.8935
Evaluate best model on test data for horizon 11, Test MAE: 3.3353, Test MAPE: 0.0959, Test RMSE: 7.0382
Evaluate best model on test data for horizon 12, Test MAE: 3.3931, Test MAPE: 0.0983, Test RMSE: 7.1796
On average over 12 horizons, Test MAE: 2.9570, Test MAPE: 0.0807, Test RMSE: 5.9993
Total time spent: 9417.1009

One more question, I think after training TESTAM uses the same expert for all inputs instead of dynamically choosing different  expert, am I correct in my understanding?
Looking forward to your reply

We encountered the same problem during the replication process, using 5 warning epochs. The final MAE in the third step of PEMS-BAY was 1.385, the MAE in the sixth step was 1.687, and the MAE in the twelfth step was 1.952. This is significantly different from the results reported in the paper and does not exceed many baselines. Do we need to adjust the hyperparameters to achieve the results in the paper?

We noticed that there may exist improper routing, which chooses only one expert regardless of regression error. We are now testing the load balancing loss function to reduce such inferiority.
Even worse, in the case of the PEMS-BAY, TESTAM sometimes selects the "worst" expert :( In that case, the MAE could be much larger than the reported one.
We'll try our best to fix the issue and after the test, we'll update the code accordingly.

@Jimmy-7664 @randomforest1111 Thank you for your continuing interest in our paper!
The problem comes from the current version of Python and PyTorch blocked index-based in-place operation.
We now revised our pseudo-label generation process accordingly. For your information, I've left notes in README.md file.
Even though we revised the pseudo-label generation and avoided selecting "improper experts," we still have some issues, such as routing may be biased toward one expert. We provide some functions that may be helpful for better routing, such as load balancing loss function or uncertainty measurements.
We still trying to improve our model, so keep touching with us!
Thank you again for your great attention and interest in our paper and I hope this change resolved your problems.


Move to less threads per sample for multi-sample runs.

Problem Description
Currently, rotary gives every multithreaded rule the complete set of CPU threads. However, these jobs often only sometimes use all these available threads all the time. For example, flye will have a sizeable multithreaded stage followed by a rate-limiting single-threaded stage. However, because this rule is designated as requiring all threads, no other jobs can be started simultaneously while flye is on this single threads stage. When processing multiple samples, the wall time of a rotary run could be increased by giving each sample a subset of the total thread count, allowing the Snakemake scheduler to better intertwine jobs from different samples together and run them simultaneously. For example, if the two samples were processed using flye simultaneously rather than sequentially, then at least the single-threaded stage of each sample could be processed simultaneously, leading to a speed-up.
Problem Solution
Create a function that generates the number of threads for rotary multithreaded rules based on the number of threads available and the number of samples to process.
Notes
Applications like Interproscan run one thread per tool by default but run multiple tools simultaneously. So, tuning can be required to tune thread-to-job ratios. Running more threads than expected can sometimes lead to performance gains if jobs are completed fast enough.

If we have the time, we could use load-averaging numbers (https://scoutapm.com/blog/understanding-load-averages) from multiple runs to find the best parameters regarding sample-to-thread ratios. However, a function that does something like one sample per 1/4 of total threads should be sufficient for now. It makes sense to leave some rules as they are because they are already running quite efficiently multithreaded (this is more important in the later annotation stage rules, so you don't get an ending where you are waiting for one sample to be annotated alone after it has been assigned only 4 threads of 12).

Also, there are situations where some jobs may plateau in performance. For example, HMMER3 plateaus in performance after eight threads due to IO bottlenecks. This is also something to consider, especially if you're trying to spread jobs across a computer with a high CPU count.

@jmtsuji Thoughts?

@LeeBergstrand Great idea -- I agree that we will get better performance across multiple samples if we decrease the thread counts to individual jobs. Aside from the caveats you've already mentioned, one key thing to watch for will be RAM -- if multiple high-RAM processes run simultaneously (e.g., GTDB, possibly Flye, etc.), then the user's system could crash. Like you mentioned, I think a good starting point could be to calculate a thread count (and "memory count" where applicable) for jobs that we think could run well in parallel. This count could be something like minimum 4 threads (or # of user provided threads, if <4), maximum 1/4 of provided threads. We could then use this thread count for rules that we think could run well in parallel. Other rules (like GTDB, possibly Flye, etc.) could be given the full thread count. In future, we could allocate resources in a more nuanced way like you mentioned, if we really wanted to optimize performance. (Another nuance we could add would be to include memory estimates for rules, so that users with tons of RAM could run multiple Flye or GTDB instances simultaneously, for example.) Thoughts?

@jmtsuji Yes, memory is also a concern that complicates things. I will think about this in more detail.

@LeeBergstrand Great idea -- I agree that we will get better performance across multiple samples if we decrease the thread counts to individual jobs. Aside from the caveats you've already mentioned, one key thing to watch for will be RAM -- if multiple high-RAM processes run simultaneously (e.g., GTDB, possibly Flye, etc.), then the user's system could crash. Like you mentioned, I think a good starting point could be to calculate a thread count (and "memory count" where applicable) for jobs that we think could run well in parallel. This count could be something like minimum 4 threads (or # of user provided threads, if <4), maximum 1/4 of provided threads. We could then use this thread count for rules that we think could run well in parallel. Other rules (like GTDB, possibly Flye, etc.) could be given the full thread count. In future, we could allocate resources in a more nuanced way like you mentioned, if we really wanted to optimize performance. (Another nuance we could add would be to include memory estimates for rules, so that users with tons of RAM could run multiple Flye or GTDB instances simultaneously, for example.) Thoughts?

From the Flye FAQ docs:

For a typical bacterial assembly with ~100x read coverage, Flye needs <10 Gb of RAM and finishes within an hour using ~30 threads. This will scale linearly with the increase in read coverage. If you coverage is above 100x, consider use --asm-coverage 100 to use the longest 100x reads for disjointig assembly - this should speed things up.

@jmtsuji This is what I have seen so far. Most of the bacterial genomes I've been processing use about ~10 Gb of RAM or slightly less than that.

@jmtsuji  I also tested the passing the following snakemake parameter that provided the desired effect.

--max-threads
Define a global maximum number of threads available to any rule. Rules requesting more threads (via the threads keyword) will have their values reduced to the maximum. This can be useful when you want to restrict the maximum number of threads without modifying the workflow definition or overwriting rules individually with –set-threads.


add metadata

Based on #308, this adds metadata to the gemspec.
#308 wasn't 100% perfect, so I included that commit, then changed on top of
that.

Released in 2.21.4


Handle relative paths in case the cusom JSON Schema is a valid local path

Hey everyone, I faced an issue that I can't validate STAC Items with against a custom local schema with relative paths. This PR fixes the behavior. I hope it works for you as well!
This PR adds a local resolver in case the custom schema is a valid local path.
Closes #53

I'm wondering, should not the error code be the non zero code return in case of a failure validation? Or it intentionally returns 0?


PostingsForMatchersCache: don't create new spans, reduce logging verbosity

Follow-up of https://github.com/grafana/mimir-prometheus/pull/553
Creating a new span for each promQL matcher for each query can end up being too verbose to navigate in grafana. This PR replaces the span with a trace log.
Overall starting a span was also expensive - according to profiles it's about 9% of the CPU of PostingsForMatchers and it's about 25% of the memory allocations. Adding events is about 2% of the CPU and ~5% of the allocations.
CPU

CPU Details

Allocations

In addition to that it removes some log lines in postingsForMatchersPromise because I think they just log the same thing multiple times. I also removed some calls to AddEvent to amortize the cost of tracing further.

I didn't see these spans for ingester queries in Mimir, so created https://github.com/grafana/mimir/pull/8242


NFDiv-3481 Welsh Webchat Support

https://tools.hmcts.net/jira/browse/NFDIV-3481

This is done but I'm closing until we hear from the business about whether or not they want it. Track the JIRA for updates


Target: serverless still required react, react-dom to be installed

Bug report
Describe the bug
next start a serverless build, still prompt me the error that require 'react', 'react-dom'.
I thought the React is inlined with the output, isn't it?

It's inlined in the bundle indeed.
You shouldn't use next start to production host the serverless target, it's not optimized to run everything as a single "server" instead the bundles should be wrapped and served separately

I was trying to deploy the serverless build to AliCloud which has its own implementation for Serverless where res and req objects are slightly different with next's output.
Am I supposed to write a custom server to hook them up? or any good idea?


Payment sandbox environment

Version of react-native-iap
"react-native-iap": "^6.0.0-rc.23",

Version of react-native
"react-native": "0.64.0",

Platforms you faced the error (IOS or Android or both?)
Android
Expected behavior
I can test the payment process
Actual behavior
App forces me to use real card
Tested environment (Emulator? Real Device?)
Emulator
Steps to reproduce the behavior
Run  requestPurchase('SKU_ID')
Hello,
when I run requestPurchase('SKU_ID') method Google Pay shows with valid price but I cant test if it's going ok because of need to input the valid credit/debit card. I'm newbie in react native but as far as I understand in DEV environment, on emulator which is logged in with invited tester account, the expected behaviour is to pass the payment without need of transfering real money.
What am I doing wrong?

I think you need to add the Google account you're logging with on the emulator to the "License Testing" list in the Google Play console (it's under 'Settings').

Thank you! that's correct :) it works now.


Package request: guymager

Guymager is a tool many forensics folk rely on for imaging devices and needed for creating a rounded forensics OS.
Info from site:
Guymager is a free forensic imager for media acquisition.
Its main features are:
Easy user interface in different languages
Runs under Linux
Really fast, due to multi-threaded, pipelined design and multi-threaded data compression
Makes full usage of multi-processor machines
Generates flat (dd), EWF (E01) and AFF images, supports disk cloning
Free of charges, completely open source
Metadata
guymager:

homepage URL: https://guymager.sourceforge.io/
source URL: https://sourceforge.net/p/guymager/code/HEAD/tree/
license: GPLv2
platforms: linux

libguytools:

source URL: https://sourceforge.net/p/libguytools/code/HEAD/tree/
license: GPLv2
platforms: linux

I tried to package guymager, and ended up with whats in antonmosich/nixpkgs in the guymager branch. I haven't managed to actually run it so far though.

I can't find any reference to Guymager in your repo.
Where should I look?

https://github.com/antonmosich/nixpkgs/tree/guymager
It is there, in that branch.


I am using this template!

I am using this template to build my website! Thank you for this wonderful academic homepage template.
The link to my website is: https://boqiuphd.github.io/

Thanks!


reduce OP queries: combine n/w/r

currently, for each Overpass API call, a single query for nodes, ways and relations is fired.
overpass-api.de has a limit of one query a time, before slowing down requests, so we at least can reduce queries to one (1) per map action.

workaround deployed: for each query type, a different overpass server is used.
=> POIs load much faster now :-)


Latency measurements for hololens client

Hi, we need to test different network configurations in order to determine which one would work best for our use case. I see that you run several efficiency tests with hololens on your own (issue #133). Did you use any tool for measuring latency/capacity that you would recommend? If not, are there any hooks in the code for tracking such data?

@machur We've recently added that feature in the DirectX client. You can enable SHOW_DEBUG_INFO flag:
https://github.com/CatalystCode/3dtoolkit/blob/master/Samples/Client/DirectxUWP/DirectxClientComponent/Content/VideoRenderer.h#L6

@phongcao thanks!


Feature/vpn gateway

Ticket Number

UCD-1071
Description of change

Create a VPN Link connection between our infrastructure and the infrastructure that the Horizon API lives in. This is optional (defaulting to false) as the VPN gateway can take up to 60 mins to provision. It's also not required in the production instance as that will be in the same subscription.
IMPORTANT
Merging into master to trigger the infrastructure change. Once merged, a rebase from master to develop must be done
Checklist

[ ] Requires infrastructure changes
[ ] If adding or remove environment variables (e.g. in docker-compose.yaml) then I have updated the appropriate Helm chart
[ ] I have updated the documentation accordingly
[ ] My commit history in this PR is linear
[ ] New features have tests
[ ] Breaking change (team conversation required)

Important
Please do not merge from master (please only rebase). This keeps the history linear and easier to debug.

This replaces #187


Update Minishift and CDK versions

The Minishift version in the docs is currently listed as 1.5.0,
CDK version is listed as 3.0.0.
AFAIK, this is no longer true, as we have moved to  CDK version 3.1.1.
We are also currently using Minishift version 1.7.0.
resolved in PR #708

fixed in #708


Add pre_get_config for Juniper

Need to set the cli screen length to 0 to ensure initial lines are not lost.

Thank you!


Change the error value

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@bed0d1b). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master       #2   +/-   ##
=========================================
  Coverage          ?   84.00%
=========================================
  Files             ?        1
  Lines             ?      150
  Branches          ?        0
=========================================
  Hits              ?      126
  Misses            ?       24
  Partials          ?        0

Flag
Coverage Δ

unittests
84.00% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out 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 bed0d1b...71524f4. Read the comment docs.


User image is not uploading when you clicked image from device camera and clicked image quality is also very poor.

Expected behavior
Memento Calendar is a modern namedays app for Android. In this app you can see upcoming events like birthdays etc. of your contacts or you can also add a new event for your contact from the app in 'Add a new event section'. While adding a new event for your contacts you can also set profile pictures to your contacts from your gallery or from your camera. When you select camera to add a profile picture, your device camera will open and you need to click a new image. After clicking image the image will upload and show in contact image area (at place of blue area).

Actual behavior
Today i installed Memento Namedays android app and after installing i came to main screen of where i can see list of my added events or i can add a new event on clicking the "+" button. I clicked on the "+" button to add a new event. After clicking on "+", a new page opened where i can create a new event with user image, contact name and event dates. I clicked on user image(the blue area with white user icon) to add contact image, select camera, click a new image and select ok. I came back to add event screen but the image i clicked from my camera is not uploaded at place of user image placeholder.

How to reproduce
To reproduce the bug follow the following steps -

Open app and click on "+" button to add a new event.
Now click on camera icon to upload a picture and select camera to click a picture.
Click image from device camera and click ok.

Now you see that your clicked image is not set as contact profile image.

* Device:  Samsung J7 Prime
* Operating system: Android 7.0 Nougatt
* App Version: v11.2

Recording Of The Bug
https://youtu.be/VNzcpiORv1E
Posted on Utopian.io -  Rewarding Open Source Contributors

Thanks for opening this issue @iamank1t.
I can confirm that the issue exists, but I haven't had the time yet. I'll pick it up as soon as I'm done with the version I am working on, or hopefully someone else might pick it up 😄

Sound cool sir!
On 18 Feb 2018 19:43, "Alex Styl"<EMAIL_ADDRESS>wrote:

Thanks for opening this issue @iamank1t https://github.com/iamank1t.
I can confirm that the issue exists, but I haven't had the time yet. I'll
pick it up as soon as I'm done with the version I am working on, or
hopefully someone else might pick it up 😄
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/alexstyl/Memento-Calendar/issues/168#issuecomment-366518965,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AgWf4UltKC22WNJOJVfFOBrNsxNXd6SGks5tWC_wgaJpZM4SF7d7
.

Sorry this took for ever, but a fix is coming in #188
I'm closing this and hopefully the next update from the Playstore won't have the issue :)


add caching mechanism to ModelUtility.splitIncompatibleMaterials

to avoid material duplication, i added a caching mechanism to the function.
fixes https://github.com/AnalyticalGraphicsInc/cesium/issues/8004

Thanks for the pull request @jbo023!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

:grey_question: Unit tests were not updated.

Make sure you've updated tests to reflect your changes, added tests for any new code, and ran the code coverage tool.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.
[ ] Works (or fails gracefully) in IE11.

Thanks again for your contribution @jbo023!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @jbo023!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks for the PR @jbo023!  Sorry it's taken a little while for us to review this.  I should be able to look at it this week.

I'm probably not the right person to review this PR.  I scanned through it, and this honestly doesn't look like too much of a win to me.  But I'm not very familiar with this part of the code.
@likangning93 or @lilleyse, can you take a look?

Thanks again for your contribution @jbo023!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @jbo023!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @jbo023!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

@jbo023 I'm hoping to review this soon.

i rebased the changes to the current Master

Thanks again for your contribution @jbo023!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @jbo023!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @jbo023!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @jbo023!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @jbo023!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @jbo023!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @jbo023!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @jbo023!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @jbo023!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @jbo023!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @jbo023!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @jbo023!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @jbo023!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @jbo023!
No one has commented on this pull request in 90 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 90 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

I'm planning on fixing this in the model-loading refactor branch, though it's not ready for testing yet. Just to keep the PR list tidy I'm going to close this. Thanks @jbo023


Create a demos repository

And list all the demos with some information, a bit like the integration did with integration-guides.
https://github.com/meilisearch/demos

@CaroFG I feel like it's done, no?

Yes


Remove empty suites from ok_tests

When locking tests, suites that are empty will be removed. This might arise if all the test cases in a suite are hidden -- all the hidden cases will be removed, leaving an empty suite. The empty suite will then be removed as well.
This is an alternative solution to #11 . This minimizes the number of fields staff members have to keep track of.
Resolves #11 .

LGTM. Merging.


Test helper for relationships

I'm not sure if I haven't found them or if they do not exist yet. Are there any helpers to test the relationship retrieval/creation/update of an resource. I would expect something like doReadRelationship(). If thats missing (and not coming very soon) I would implement that on my own and can, of course, create a pull request..

Hi! Sorry for slow reply - missed this issue being created.
They don't exist at the mo but definitely my intention to add some in. I need to do quite a bit of work around the relationship endpoints as there's a few things missing for them at the mo.
Thanks for the offer of a pull request. If you wanted/have time to submit one then it'd be very welcome. As you say, the method names would be along the same names as the existing one on InteractsWithResources, so:

doReadRelatedResource
doReplaceRelationship
doAddToRelationship
doRemoveFromRelationship

i.e. match the controller method names as defined here:
https://github.com/cloudcreativity/laravel-json-api/wiki/Routing
Obviously happy to help out with questions/review if needed. If you're not able to submit a pull request then these are definitely on my to-do list.

Hey! Thanks for your reply. I think I can work on that in the near
future. Doesnt seem to be too much work to me. Unfortunately there are
some other things that come first. So might take a little time to get
this done. I come back to you soon.
Am Di, 8. Nov, 2016 um 11:09 schrieb Christopher Gammie
<EMAIL_ADDRESS>
Hi! Sorry for slow reply - missed this issue being created.
They don't exist at the mo but definitely my intention to add some
in. I need to do quite a bit of work around the relationship
endpoints as there's a few things missing for them at the mo.
Thanks for the offer of a pull request. If you wanted/have time to
submit one then it'd be very welcome. As you say, the method names
would be along the same names as the existing one on
InteractsWithResources, so:
doReadRelatedResource
doReplaceRelationship
doAddToRelationship
doRemoveFromRelationship
i.e. match the controller method names as defined here:
https://github.com/cloudcreativity/laravel-json-api/wiki/Routing
Obviously happy to help out with questions/review if needed. If
you're not able to submit a pull request then these are definitely on
my to-do list.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

that's ok - don't worry if it takes a bit of time. I'm also tied up with work deadlines this month anyway, so probably won't be looking at the next step of development for this until December anyway

Closing this because test helpers for relationship requests are now on the 1.x-dev branch


update versions

Updated Python versions
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

maybe update the package version in setup.py

This would be really usefull to merge in.


DRILL-1942-concurrency-test: new smoke test for concurrent query exec…

…ution;
useful to checking on the new allocator's locking schemes.
Made the SilentListener in BaseTestQuery.java public so it could be reused. Added new TestTpchDistributedConcurrent.java as a unit test. No other changes.
Unit tests (mvn install) pass.

I added code to collect errors, as well as to interrupt the test thread when an error occurs.

Addressed Sudheesh's comments. Unless Jason has anything else, can we please get this merged now?

+1 looks like all comments are addressed.


Go 1.10

This CL adds support for Go-1.10.
It also adds 1.9.x and 1.10.x to the list of Go versions to test with Travis-CI.

@sbinet in case it's of interest I've, coincidentally, just pushed up #26


[Improvement-5275][Server] Fix wrong excludeFilters and move zk/ZKMasterClient and registry/ServerNodeManager into master

Purpose of the pull request
[Improvement-5275][Server] Move zk/ZKMasterClient and registry/ServerNodeManager into master
This closes #5275 and closes #5176
Brief change log

Move zk/ZKMasterClient and registry/ServerNodeManager into master, and the code will be clearer and easier to understand
Remove org.apache.dolphinscheduler.server.zk.ZKMasterClient and org.apache.dolphinscheduler.server.registry.ServerNodeManager in the WorkerServer

Verify this pull request
This change added tests and can be verified as follows:

Manually verified the change by testing locally.

@CalvinKirs Please review


add android version .apk

Please provide a version for android, with .apk installation package and configuration to be read as a file, so we could use rathole on mobile phones too.

You could also use Termux and run the binary that way, there are aarch64 / armv7 builds available.

You could also use Termux and run the binary that way, there are aarch64 / armv7 builds available.

i didn't know that, thanks!


QA - Test of the Unsplash & Coverr 3P integration

Task Description
Please ensure that the integration of the 3rd Party media providers is working as expected.
User is able to

[ ] Browse images from Unsplash / Coverr
[ ] Filter images from Unsplash / Coverr
[ ] Insert images from Unsplash / Coverr
[ ] Select and deselect an Unsplash category to view images for it.
[ ] Search videos and images in both Unsplash and Coverr.
[ ] Images/videos inserted via Unsplash/Coverr render properly in the output AMP story.
[ ] Images/videos inserted via Unsplash/Coverr can be manipulated without issues in the canvas.
[ ] Pagination in the media gallery works as expected, especially when switching between provider tabs and performing things such as search, selecting a category, etc.

You will need to enable the media3pTab and coverrTab flags to test this

When would we be able to start this testing? cc: @csossi

Hi Claudio, do you think you'll have bandwidth to test this?

sure, @diegovar - this the extent of the scope here?:
User is able to
Browse images from Unsplash / Coverr
Filter images from Unsplash / Coverr
Insert images from Unsplash / Coverr

Sorry for the late reply. Not that Coverr provides only videos, not images.
I'd add the following:

Select and deselect an Unsplash category to view images for it.
Search videos and images in both Unsplash and Coverr.
Images/videos inserted via Unsplash/Coverr render properly in the output AMP story.
Images/videos inserted via Unsplash/Coverr can be manipulated without issues in the canvas.
Pagination in the media gallery works as expected, especially when switching between provider tabs and performing things such as search, selecting a category, etc.

Hi Claudio, any updates on this?

Clicked the arrow in order to see available categories:

Categories appeared. Selected "Travel"

Images correctly filtered, but thought that arrow would reappear in case user wants to now select a diff category:

Also noticed that Search field is disabled/disappears on selecting image category, only reappearing when user deselects category. Is this intentional?

Hi Claudio, thanks for spotting that. We've fixed #4404 by merging #4405 which means you should now be able to expand the categories section when a category is selected.
The search field being disabled while a category is selected is intentional.

Verified in QA


feat: multiple wifi credentials

I keep having to reset the credentials because I have multiple play spaces with two different login credentials, so I decided to make this to make my problem more bearable

I already have a better solution on hand, give me a few days to polish it up though :)

Would it be wise to reconsider this patch? Seems like #164 wasn't viable

Only if you're up to rewriting the WifiHandler into a class and refactoring some of the code in there (you can copy paste most stuff from my PR, probably).

Yeah I'd make it work on the newest versions, just asking if its worth the effort

Just to note, this patch is multiple HARDCODED wifi credentials, not multiple dynamic ones


Extract core styles to plugin or stylesheet

Initial pass to remove Tailwind classes from views into CSS files with @apply (CSS files could be restructured, moved, or imported differently to how they are now, the work in this stage is just to create the files)

[x] actions
[ ] forms
[ ] infolists
[ ] panels
[ ] schema
[x] spark-billing-provider
[x] spatie-laravel-google-fonts-plugin
[x] spatie-laravel-media-library-plugin
[x] spatie-laravel-settings-plugin
[x] spatie-laravel-tags-plugin
[x] spatie-laravel-translatable-plugin
[x] support
[x] tables
[ ] upgrade
[x] widgets

Donate 💰 to fund this issue

You can donate funding to this issue. We receive the money once the issue is completed & confirmed by you.
100% of the funding will be distributed between the Filament core team to run all aspects of the project.
Thank you in advance for helping us make maintenance sustainable!

@danharrin you can document your experiment findings here if you like.

CSS layers will make theming much easier already: https://developer.mozilla.org/en-US/docs/Web/CSS/@layer.

Just wanted to throw in, that we should consider introducing more CSS vars for everything like colors to make stuff more customisable.

Could you clarify what you mean specifically, @pxlrbt?

What I mean is, that it would be good if it's possible to extract some often used configs to CSS vars, to allow easier customization. Colors would probably be the easiest. Other parts may be trickier. Also determining what might be useful could be tricky 😅
--sidebar-background
--sidebar-color
--border-radius

Naming design tokens is definitely tricky. Especially when keeping extensibility in mind.

Just wanted to mention this doesn't solve the table performance issue: https://github.com/filamentphp/filament/issues/9304#issuecomment-2315856913.

i had made a tool can do that it can extract all tilwindcss classess from a view files and compile them to a new style sheet after that it scan the view files to add random classess for each element.


Circle Swatch in Legend - Final Circle Missing

Hi there,
When changing the legend to "colorkey_swatch_shape=:circle" the final label color goes missing. E.g. see image below produced by the following:
df1 = DataFrame(x = rand(10), y = rand(10), label="A")
df2 = DataFrame(x = rand(10), y = rand(10), label="B")
df3 = DataFrame(x = rand(10), y = rand(10), label="C")
df = [df1; df2; df3]
plot(df, x="x", y="y", color="label", Theme(colorkey_swatch_shape=:circle), Geom.point)

Am using Julia v0.3.8 and Gadfly v0.3.12

This is fixed in master (by https://github.com/dcjones/Gadfly.jl/commit/f8d5d3ccd248445e604b807fa39ea75a2ae94449).


feat: add --releaseDate to git node release

This will enable us to automate release proposal
creation: https://github.com/nodejs/security-wg/issues/860

I think npm run lint-fix did that btw.


Help key redirects to a non-accessible webpage

The help key brings up information on each type block in a new webpage. Click on a block and then use the correctly designated hot key. Some of the webpages that are used are github and wikipedia. Neither of these are accessible. Pages that are accessible with short concise information about the blocks would be better to link to.

We have made a Quick Reference Guide that will be linked to instead of wikipedia/Github. There are pages for each category of blocks as well as a homepage and soon to be a key strokes information page too. The anchor tags that will be used to link to the correct spot on the page are equivalent to the "type" of the block. The type of block is an attribute in the XML.

 The homepage needs a better/more accurate description and the hotkeys pages needs to be filled in with content.

Since the quick ref is made and this issue is a duplicate of "help URL of each block needs to be corrected"  Im going to close it.


Respect minimum idle timeout of 3 PTOs

Currently the idle timeout can be lower than 3 PTOs.
RFC 9000 Section 10.1 states:

[...] To avoid excessively small idle timeout periods, endpoints MUST increase the idle timeout period to be at least three times the current Probe Timeout (PTO). [...]

This is a for example a problem if Config.MaxIdleTimeout is set to a value below the path RTT.
The connection then times out immediately after the handshake.
Suggestion: add connection.nextIdleTimeoutTime() that respects the lower bound.
This should also affect the connection.nextKeepAliveTime().
The Config.HandshakeIdleTimeout should remain unaffected, since no RTT measurements are available anyways.

Makes sense. Want to submit a patch?

@birneee I had to revert #3859, since it was causing CI failures on master (changed mock interface).
Could you reopen the PR, rebased on top of the current master. Your changes were good, and I'd like to get them into the next release.


Fixing sync with upstream

It looks like that #120 was merged with squash merge, the bot tried to merge the conflicts in #123 but the commit fc7f60f2bd1c304f0122f5fd09b8256e7d563f1c created by it was targeting a different source.
Here's what I did to fix:

Reverted squash merge from #120
Applied the changeset from Sync with reactjs.org @ 8803c63 again
Applied the changeset from Sync with reactjs.org @ b50fe64c by merging b50fe64c manually

Result: Both syncs have been applied so we are tracking b50fe64c correctly.
As you can see in the screenshot from upstream, it matches with the changes below:

Replaces #123 so it can be closed

Thanks for fixing this! Looks good.


Enable debug info for inlined generics by default. It works now.

(For some reason I thought I already did this 2 months ago...)

@swift-ci test

@swift-ci test source compatibility

Chatto failures look unrelated.


Simple_form in Rails 6 can't render nested attributes

The title is quite self-explanatory.
Here are the models:
class Adventure < ApplicationRecord
  alias_attribute :pcs, :player_characters

  has_many :player_characters, dependent: :destroy
  accepts_nested_attributes_for :player_characters
end

class PlayerCharacter < ApplicationRecord
  belongs_to :adventure
end

And here my views:
# _form.html.erb

<%= simple_form_for @adventure do |f| %>
  <%= f.input :email %>
  <%= f.input :test %>

PCs

    <%= f.simple_fields_for :player_characters do |player_character| %>
      <%= render 'player_character_fields', f: player_character %>
    <% end %>
  <%= f.submit %>
<% end %>

# _player_character_fields.html.erb

  <%= f.input :path %>
  <%= f.input :race %>
  <%= f.input :name %>
  <%= f.input :player_name %>

With this code the simple fields just don't render. If I remove accepts_nested_attributes_for from the model the simple fields render, but I can't create a new nested model as intended. If I change the code to the rails inbuilt form_for everything works as intended.
Ruby 2.6.3
Rails <IP_ADDRESS>
Simple_form 5.0.2

@Naokimi Thanks for the report 🙌
Could you please provide us a sample application that reproduces the issue in isolation?
That would help us find the issue.

huh,
I swear I had it happening in two different repositories but now I went back to them, rewrote the forms with simple_form and both seem to be working fine...
I'll close the issue for now.

I've the same issue, so it's still actual.
Gonna make a sample project this evening.

Update: https://github.com/Vinnie1991/simple-forms_nesting
The models are
`class Event < ApplicationRecord
has_many :time_records
when I enable this code, the TimeRecords fields disappear
accepts_nested_attributes_for :time_records
end
`
class TimeRecord < ApplicationRecord   belongs_to :event end
Form is:
`
<%= simple_form_for(@event) do |f| %>
<%= f.error_notification %>
<%= f.error_notification message: f.object.errors[:base].to_sentence if f.object.errors[:base].present? %>

    <%= f.input :title %>
<%= f.simple_fields_for :time_records do |form| %>

  <%= form.date_field :from_date %>
  <%= form.date_field :till_date %>

<% end %>

    <%= f.button :submit %>

<% end %>
`
When I enable accepted_nested_params, the two datefields disappear from the view.
Ruby 2.6.6
Rails <IP_ADDRESS>
SimpleForms 5.0.2


make wizard for most crucial settings

ask for battery saving (app will not work)
ask for custom messenger (already responded will not work)
ask for intelligent auto detection if user want


Failed when using Azure Cache for Redis Enterprise to replace Redis on ACI

Hello
I Created Azure Cache for Redis Enterprise with Search and Json Modules,and configure the app setting of Azure APP servcie, which I set the Redis endpoint,port(10000) and password.But it failed when running .throw the below errors.Any suggestions?

Thanks,
Teo

I read the source code of demo,I found the redis port is  "6379" ,which has been biult on your docker image(
fruocco/oai-embeddings) ,but azure cache for redis enterprise only use the port "10000" ,so we need to biuld our own image as the redis port has not been configured as the app environment of demo's azure app service.Any suggestions would be so much appreciated.

hi @teo-ma , thanks for highlighting this issue with ACRE. Sounds like a problem in checking the modules available in the Redis instance. We should temporarily work around it while we get a solution at the product level.
For the port, you can specify it in the environment without rebuilding the image. (REDIS_PORT)

Thanks @ruoccofabrizio for kindly comments.
I tested this demo locally with Azure Redis Enterprise, which selected Search Module.So would you give me some suggestions on which azure redis  modules I should select when creating Azure Redis Enterprise?

We identified an issue with LangChain and submitted a fix. As soon as it's merged, we'll upgrade the code accordingly. Thanks again for the heads up! @teo-ma

@teo-ma : The issue should be fixed as LangChain merged our changes. Please try again, setting the following ENV variables:
REDIS_ADDRESS=YOUR_AZURE_REDIS_ADDRESS
REDIS_PORT=10000
REDIS_PASSWORD=XXX