Add single-precision float support to struct.js

This adds support for parsing single-precision floating-point numbers to struct.js

Hmm...DataView is handy. There's one issue, though -- DataView's results are dependent on the endianness of the machine it runs on.
Given that all current macs and pcs are little-endian (no we don't miss the 68K), it's not really an issue today. But in a hypothetical future where the uploader might run on an ARM-based machine, there's a possibility that a big-endian architecture might rear its head again.
I believe that all the pre-existing code is not sensitive to the endianness of the platform it's running on, but this new code is.
In my ideal world, there would be a test during initialization to decide if the local architecture is big-endian, and it would swap extractFloat with extractBEFloat, and the same with store. An alternative would be a test during initialization that just throws an error if it's run on a big-endian machine. At the very least, it deserves a comment in the source about it.

I wish I had a big-endian machine with enough RAM to test on, but these methods use the endian-safe setFloat32(value, endianness) and getFloat32(value, endianness) methods on DataView.  It is my understanding that typed arrays are native-endian, which is why I used DataView in the first place.
I actually have another implementation that does it purely in math before I stumbled on DataView, but it requires more recent browser support for Math.fround() to arrive at bit-exact float decoding and this appears to be exactly what DataView is intended to do.

Doh, my mistake. Thanks!
In that case, LGTM, will merge.


The browser Back and Forward buttons misbehave after navigating to an URL anchor (#)

Cycling/clicking through the same set of topics works sometimes, and then suddenly the browser back and forward buttons stop working.
Im guessing here but this might have something to do with how the javascript is tracking the popstate? Possibly to do with the # related hrefs. Right now we ignore clicks on nav menu containers so they are not added to the history (ie. href="#") but URLs that include # like anchors might be also filtered and causing the Back and Forward button issues?
Javascript for tracking the popstate and any clicks in the nav menu is located in _includes/documentation.html.
This issue found in: #12092

@thockin

Closing -> fixed in #12437


Usage of non C99 features

For example:
typedef struct
{
    union
    {
        f32 xy[2];
        struct
        {
            f32 x, y;
        };
    };
} gs_vec2;

This would not compile on a compiler only supporting C99 without extensions. When compiling with -pedantic -std=c99 flags it would yield: warning: anonymous unions are a C11 extension [-Wc11-extensions]... Using anonymous unions and structs  is not supported in C99 standard. It was introduced in C11 standard.

Thanks for pointing this out. I'll switch these unions to being named to fix it.


Update azure-resource-manager-api-spec.md

Remove storage_share_name from container app template.  It is used in container app environment template but should not be in the container app.

Docs Build status updates of commit af83149:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/container-apps/azure-resource-manager-api-spec.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@craigshoemaker,
Can you review the proposed changes?
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Thanks, @KarsonAlford!
#sign-off

Due to the upcoming Ignite conference, all merging and publishing is on hold until the morning of October 12.
This PR is ready for merge on 10/12.
#label: "missed-content-complete"
#label: "event-triaged-to-10AM"


Why is there "es" language when no "es" language was used?

I used only english (default) and "cs" langs, yet, there is "es" lang offered:

It was predefined in the configuration-context class. Now we have only cs and en as defaults.


API refactoring

In the light of the UI redesign (see #4) and the added endpoints for user management (see #9), we should also re-evaluate and eventually refactor the REST API design. For example, the swagger documentation is inconsistent with the implemented API (see #98). Also, naming is outdated, "scenario" should be changed to "case model".
Discussion Results

we keep the versioning, the refactored API will use api/v3/ as base
we will use the plural convention for resource names, i.e. casemodels/123/cases
we will no longer use different base paths for events, history, and the main interface, instead the complete API will be reachable at api/v3/

Open Question: UUIDs or auto-incremented numbers?

auto-incremented numbers are more (human) readable and make it easier to debug the API
with numbers, users can infer and access Ids of other resources
should numbers be unique among case models, cases, activities etc. or only for one layer? E.g. is casemodels/3/cases/3/dataobjects/3/attributes/3 a valid URL?
if we keep UUID as key in the database, we need to make a mapping in the REST layer
does EclipseLink generate the UUIDs and uses them, or does it have separate identifiers?

Features

[ ] discuss usage of UUIDs vs. incremental numbering (in this issue)
[ ] update naming of scenario and instance
[ ] #102 create a document outlining our API design principles
[ ] #100 swagger documentation should be automatically generated
[ ] #96 swagger documentation consistency
[ ] #75 API for user management
[x] #98 discuss & decide separated base paths

http://jsonapi.org/ as a standard should be very helpful for the refactoring.

@janwestphal306 The jsonapi spec is very verbose and the responses are highly nested. Although I like how links are included and preloaded in the included key. I would rather have responses that directly reflect the object structure of the resources, so we can use Bean classes. We can include a query parameter ?complete that would indicate to load the complete resource, e.g. an organization with all its members, owners, roles, or a complete case.

I disagree with changing the response object. The main benefit of the jsonapi standard is that it is a standard and therefore many libraries are built on it. Take https://www.npmjs.com/package/json-api-wrapper as an example, it is a generic API wrapper build exactly on the standard. Therefore I'd strongly advise implementing the standard, exactly as it is proposed.

@marhew The refactored chimera would allow to split the long Url v3/organizations/{organizationId}/casemodels/{casemodelId}/cases/{caseId} in v3/organizations/{organizationId}, v3/casemodels/{casemodelId} and ``v3/cases/{caseId}` and would still achieve the same behavior if the we validate in the request filter. Would this be desired?

I think it is better to keep the hierarchy of resources visible.

For the 1.5 release we will stick to UUIDs. However, for 2.0 we should change IDs to a shorter and more readable format.


quick add many elements

I want to creates shared dict with several milions items. With normal python dict addition elements in loop works well  (~300k elements per second) with shared-memory-dict is ~ 1000 slower. Is there any way to quickly build big shared-dict?

Sorry for the late reply, @rmrmg you can create a SharedMemoryDict and then update it with many values. Normal addiction is slow because of the process that we use to store an element. We should deserialize the internal map, add an element and serialize again, and this process use lock to avoid race conditions.

@shanelanan What about an alternative constructor?
...
    @classmethod
    def from_dict(cls, name: str, size: int, input: dict) -> 'SharedMemoryDict':
        sd = cls(name, size)
        with self._modify_db() as db:
            db.update(input_dict)
        return sd

...

@shanelanan The method bulk_set_from_dict is equivalent to update from SharedMemoryDict.
You can do:
from shared_memory_dict import SharedMemoryDict
smd = SharedMemoryDict(name='tokens', size=20480)
smd.update(input_dict)


Milestone 0.0.1

Changes Unknown when pulling d8e18ef62b1788afeeb284aeebb85139fce95a6e on milestone-0.0.1 into ** on master**.

Changes Unknown when pulling d8e18ef62b1788afeeb284aeebb85139fce95a6e on milestone-0.0.1 into ** on master**.

Changes Unknown when pulling d8e18ef62b1788afeeb284aeebb85139fce95a6e on milestone-0.0.1 into ** on master**.

Changes Unknown when pulling d8e18ef62b1788afeeb284aeebb85139fce95a6e on milestone-0.0.1 into ** on master**.

Changes Unknown when pulling 3d3a4d25ec8d955ca75e99d549a1284545401da6 on milestone-0.0.1 into ** on master**.


chore(deps): update helm release kube-prometheus-stack to v40.5.0

This PR contains the following updates:

Package
Update
Change

kube-prometheus-stack (source)
minor
40.0.2 -> 40.5.0

Release Notes

prometheus-community/helm-charts
v40.5.0
Compare Source
kube-prometheus-stack collects Kubernetes manifests, Grafana dashboards, and Prometheus rules combined with documentation and scripts to provide easy to operate end-to-end Kubernetes cluster monitoring with Prometheus using the Prometheus Operator.
v40.4.0
Compare Source
kube-prometheus-stack collects Kubernetes manifests, Grafana dashboards, and Prometheus rules combined with documentation and scripts to provide easy to operate end-to-end Kubernetes cluster monitoring with Prometheus using the Prometheus Operator.
v40.3.1
Compare Source
kube-prometheus-stack collects Kubernetes manifests, Grafana dashboards, and Prometheus rules combined with documentation and scripts to provide easy to operate end-to-end Kubernetes cluster monitoring with Prometheus using the Prometheus Operator.
v40.3.0
Compare Source
kube-prometheus-stack collects Kubernetes manifests, Grafana dashboards, and Prometheus rules combined with documentation and scripts to provide easy to operate end-to-end Kubernetes cluster monitoring with Prometheus using the Prometheus Operator.
v40.2.0
Compare Source
kube-prometheus-stack collects Kubernetes manifests, Grafana dashboards, and Prometheus rules combined with documentation and scripts to provide easy to operate end-to-end Kubernetes cluster monitoring with Prometheus using the Prometheus Operator.
v40.1.2
Compare Source
kube-prometheus-stack collects Kubernetes manifests, Grafana dashboards, and Prometheus rules combined with documentation and scripts to provide easy to operate end-to-end Kubernetes cluster monitoring with Prometheus using the Prometheus Operator.
v40.1.1
Compare Source
kube-prometheus-stack collects Kubernetes manifests, Grafana dashboards, and Prometheus rules combined with documentation and scripts to provide easy to operate end-to-end Kubernetes cluster monitoring with Prometheus using the Prometheus Operator.
v40.1.0
Compare Source
kube-prometheus-stack collects Kubernetes manifests, Grafana dashboards, and Prometheus rules combined with documentation and scripts to provide easy to operate end-to-end Kubernetes cluster monitoring with Prometheus using the Prometheus Operator.

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

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

This PR has been generated by Renovate Bot.

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Some Help if is posible

Hello sir @NoahCardoza how can use  this lib on my vote script, if u can help me, thx
Here is my exemple script, my try, but it is wrong  idk how to do it
My script send requests to a vote url (to create fake  viewes)
const time = voteTime;
const exec = require('exec');
const request = require('request');

setInterval(() => {

request.get({
  url: voteURL,
  headers: {
    'user-agent': 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.0 Safari/537.36'
  },
  jar: true
}, function(error, response, body) {
exec(`curl -L -X POST 'http://localhost:8191/v1' \ -H 'Content-Type: application/json' \ --data-raw '{ "cmd": "request.get", "url": voteURL, "userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.0 Safari/537.36", "maxTimeout": 60000, "headers": { "X-Test": "Testing 123..." } }'`, function(error, stdout, stderr) {});
}

});
	setInterval(() => {
		process.exit();
	}, time*1000);
}, 5);

Well, first of all you are not passing voteURL to the CURL command because you didn't use string interpolation.
I wouldn't even use CURL in the first place though because you are using Node and already have the request module imported. Why not use that for send the request?

Well, first of all you are not passing voteURL to the CURL command because you didn't use string interpolation.
I wouldn't even use CURL in the first place though because you are using Node and already have the request module imported. Why not use that for send the request?

I tried, but it seems I can't handle it, I don't know how to do this, I'm wrong somewhere, this lib shows me that it detects cloudflare protection, but it doesn't send requests, it just shows me
Captcha detected but no automatic solver is configured.
I don't know where I'm wrong

You didn't set an automatic solver.
Re: https://github.com/NoahCardoza/CloudProxy#hcaptcha-solver


Dimmed Monokai theme - improve markdown support

This PR fixes #104467

render bold/italic , link title color

Before:

After:

This PR is analogous to PR #85467

Thanks @orionlee !


feat(graphql_analyze): noDuplicatedGraphqlFields

Summary
Implement no-duplicate-fields lint rule from graphql-eslint
Test Plan
All tests should pass.

Ah, sorry I didn't see your comment. Thanks for rebasing this for me

Just one nit @vohoanglong0107, we should avoid having the language name inside the rule's name. We already have the metadata that tells us the language.

I'm a little confused about this, but what if there is another rule for JSON called noDuplicatedFields, how could we config both of them?

Ahah, I understand. I will keep this in mind when developing further lint rules

Feel free to merge it :)


WIP untested, updating contract with all feedback from audit review

@mikedotexe thank you for the updates!!! reviewed, all looks good now


 We might need to gate PCSS bindings on a feature flag, or change how we set up the bindings to only bind the actually used textures/samplers.
Edit: Looking a bit more into it, it looks like we're not hitting texture limit. The limit is exclusively on samplers, maybe we can virtualize the samplers, as suggested here: https://github.com/google/filament/issues/5788

Note that on some platforms you have to use combined samplers and can't share. (WebGL?)

Relevant limit on my m1: max_samplers_per_shader_stage: 16
It should crash on every gpu with the same or lower limit


Deeplink launches twice or more in iOS

HI there
Having an issue where a deeplink will fire twice (but sometimes even multiple times) after opening a Branch link in iOS. My process is as follows:

Click a Branch link
It opens my app. I handle the event in my JS and route through my app using the deeplink path.
I do something to cause the app to lose focus, such as going to the homescreen or opening the notification shade.
On returning focus to the app, the Branch link fires again and the navigation happens a second time.

As far as I can tell, this does not happen on Android. I'm thinking I have some piece of iOS setup wrong, but I've checked everything against the docs and there is no glaring omission. If I have gone wrong somewhere, what could it be?

@DanProudfoot did you manage to figure this one out? seeing the same behvaviour in android.

user clicks branch link
app opens
gets redirected in app
user closes app (background mode) and uses other apps etc on phone
opens app again and user gets redirected back with the initial branch logic (but didn't press a branch link this time)

When looking at the app branch link data from "init" function it still has the "clickedBranchLink" as true for the visits after the initial branch link click visit.

@KirstenStake Hi - I didn't find an answer entirely within the confines of Branch, but what I have done since that seems to be working is store the deeplink timestamp in Capacitor Storage and then compare the stored version with the next time the event is called. If it's the same, just ignore it.

I've noticed that the second time, the subscribe listener adds this param: '+rn_cached_initial_event'. You can return early if it's present.
This does not seem to be the case on getInitialUrl.


Training on own dataset for (128x128) --> (512x512) fails miserably !!

I was training on my own dataset for (128x128) --> (512x512)
I have attached the train logs :
train.log
val.log
The tensorboard visualizations look like this:

And the losses & psnr aren't improving

Please help me to fix it

Hey, I met with the same problem, but, but my l_pix is normal like 0.05, my sr_img and PSNR are the same situation like yours. Did you solve it?


[Feature][Default branch] Should the Default branch is master not dev?

Search before asking

[X] I had searched in the feature and found no similar feature requirement.

Description
According to the general specification, the master is used as the default branch management
Usage Scenario
No response
Related issues
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

we use dev as our default branch


Unsupported Hadoop major version detected. It is not 2.x. on EMR

Hi there,
I am running Dr. Elephant against local Hadoop/Spark cluster successfully.
BUT when I try to deploy Dr. Elephant on my production AWS EMR Cluster, I'm getting this error in log:
04-12-2017 09:43:09 ERROR [Thread-6] com.linkedin.drelephant.ElephantRunner : Unsupported Hadoop major version detected. It is not 2.x.
04-12-2017 09:43:09 ERROR [Thread-6] com.linkedin.drelephant.ElephantRunner : java.lang.RuntimeException: Unsupported Hadoop major version detected. It is not 2.x.
        at com.linkedin.drelephant.ElephantRunner.loadAnalyticJobGenerator(ElephantRunner.java:82)
        at com.linkedin.drelephant.ElephantRunner.access$100(ElephantRunner.java:50)
        at com.linkedin.drelephant.ElephantRunner$1.run(ElephantRunner.java:103)
        at com.linkedin.drelephant.ElephantRunner$1.run(ElephantRunner.java:98)
        at java.security.AccessController.doPrivileged(Native Method)
        at javax.security.auth.Subject.doAs(Subject.java:360)
        at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1678)
        at com.linkedin.drelephant.security.HadoopSecurity.doAs(HadoopSecurity.java:108)
        at com.linkedin.drelephant.ElephantRunner.run(ElephantRunner.java:98)
        at com.linkedin.drelephant.DrElephant.run(DrElephant.java:34)

Dr. Elephant is latest master.
$ hadoop version
Hadoop 2.7.3-amzn-1
Subversion git@aws157git.com:/pkg/Aws157BigTop -r 60b8618a21bca805756fb1bc393c18c2512e4fc4
Compiled by ec2-user on 2017-02-04T01:32Z
Compiled with protoc 2.5.0
From source with checksum 1833aada17b94cfb94ad40ccd02d3df8
This command was run using /usr/lib/hadoop/hadoop-common-2.7.3-amzn-1.jar

$ yarn version
Hadoop 2.7.3-amzn-1
Subversion git@aws157git.com:/pkg/Aws157BigTop -r 60b8618a21bca805756fb1bc393c18c2512e4fc4
Compiled by ec2-user on 2017-02-04T01:32Z
Compiled with protoc 2.5.0
From source with checksum 1833aada17b94cfb94ad40ccd02d3df8
This command was run using /usr/lib/hadoop/hadoop-common-2.7.3-amzn-1.jar

Could you please help me with hints/directions?
Thank you!

You should have the following configuration in your mapred-site.xml:
<property>
    <name>mapreduce.framework.name</name>
    <value>yarn</value>
</property>

I hope that helps.

Thank you man!
The issue was other thing, actually a "facepalm" one:
Hadoop configuration on development cluster was stored under /etc/hadoop path, but on the AWS EMR cluster it is stored under /etc/hadoop/conf, that's why configs was not loaded and :boom: :boom: :boom:
This issue is solved, having other ones though, taking on 'em!


how to run from latest repo

Want to use without waiting for next binary.  Is there any instruction on how to build the binary on my local machine

Related Issues

@polymerchm
See https://github.com/codercom/code-server/issues/17

@polymerchm You could try:

cd into code-server
Run yarn
Run yarn task vscode:clone
Run yarn task vscode:patch
Run yarn task buld:bootstrap-fork
Finally, yarn start

If that doesn't work let me know. I might be missing a step.

I believe you will also need a version of node 8. I use v8.15.0 which seems to work well.

Get this.   Not sure what to do next.
ERROR VSCODE:INSTALL failed {"exitCode":1,"stdout":"$ node build/npm/preinstall.js\n[1/4] Resolving packages...\n[2/4] Fetching packages...\ninfo<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.\ninfo<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.\ninfo<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.\ninfo<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.\ninfo<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.\ninfo<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.\ninfo<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.\ninfo<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.\ninfo<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.\ninfo<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.\ninfo<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.\ninfo<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.\ninfo<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.\ninfo<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.\n[3/4] Linking dependencies...\n[4/4] Building fresh packages...\ninfo Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.\n","stderr":"warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>/usr/local/code-server/lib/vscode/node_modules/native-keymap: Command failed.\nExit code: 1\nCommand: node-gyp rebuild\nArguments: \nDirectory: /usr/local/code-server/lib/vscode/node_modules/native-keymap\nOutput:\ngyp info it worked if it ends with ok\ngyp info using<EMAIL_ADDRESS>info using<EMAIL_ADDRESS>| linux | x64\ngyp info spawn /usr/bin/python2\ngyp info spawn args [ '/usr/local/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',\ngyp info spawn args   'binding.gyp',\ngyp info spawn args   '-f',\ngyp info spawn args   'make',\ngyp info spawn args   '-I',\ngyp info spawn args   '/usr/local/code-server/lib/vscode/node_modules/native-keymap/build/config.gypi',\ngyp info spawn args   '-I',\ngyp info spawn args   '/usr/local/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',\ngyp info spawn args   '-I',\ngyp info spawn args   '/home/spollack/.node-gyp/iojs-3.1.3/common.gypi',\ngyp info spawn args   '-Dlibrary=shared_library',\ngyp info spawn args   '-Dvisibility=default',\ngyp info spawn args   '-Dnode_root_dir=/home/spollack/.node-gyp/iojs-3.1.3',\ngyp info spawn args   '-Dnode_gyp_dir=/usr/local/lib/node_modules/npm/node_modules/node-gyp',\ngyp info spawn args   '-Dnode_lib_file=/home/spollack/.node-gyp/iojs-3.1.3/<(target_arch)/iojs.lib',\ngyp info spawn args   '-Dmodule_root_dir=/usr/local/code-server/lib/vscode/node_modules/native-keymap',\ngyp info spawn args   '-Dnode_engine=v8',\ngyp info spawn args   '--depth=.',\ngyp info spawn args   '--no-parallel',\ngyp info spawn args   '--generator-output',\ngyp info spawn args   'build',\ngyp info spawn args   '-Goutput_dir=.' ]\nPackage x11 was not found in the pkg-config search path.\nPerhaps you should add the directory containing x11.pc'\nto the PKG_CONFIG_PATH environment variable\nNo package 'x11' found\nPackage xkbfile was not found in the pkg-config search path.\nPerhaps you should add the directory containing xkbfile.pc'\nto the PKG_CONFIG_PATH environment variable\nNo package 'xkbfile' found\ngyp: Call to 'pkg-config x11 xkbfile --libs' returned exit status 1 while in binding.gyp. while trying to load binding.gyp\ngyp ERR! configure error \ngyp ERR! stack Error: gyp failed with exit code: 1\ngyp ERR! stack     at ChildProcess.onCpExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:345:16)\ngyp ERR! stack     at ChildProcess.emit (events.js:182:13)\ngyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:240:12)\ngyp ERR! System Linux 4.15.0-46-generic\ngyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"\ngyp ERR! cwd /usr/local/code-server/lib/vscode/node_modules/native-keymap\ngyp ERR! node -v v10.10.0\ngyp ERR! node-gyp -v v3.8.0\ngyp ERR! not ok\n"}
ERROR VSCODE:INSTALL Failed: Failed to install vscode dependencies: warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>error /usr/local/code-server/lib/vscode/node_modules/native-keymap: Command failed.
Exit code: 1

It looks like you are using Mac, try swapping out linux for darwin
yarn task build:server:binary:darwin

No.  Building  in on a linux box. Ubuntu

How often do binaries come out?

@polymerchm we release new versions whenever we have meaningful updates ready and tested. We don't have a set release schedule at the moment. Thus far we've been submitting new releases a few times per week.

Just struggling with installing on a linux box from the "repos".   Yarn, npm and I are not good friends.

@nol166 Even I got the same error using Ubuntu 18.04.

What version of node are you guys using when running the yarn build tasks

Package xkbfile was not found in the pkg-config search path might be the key. Do you have libxkbfile-dev installed? Running pkg-config x11 xkbfile --libs should give you something like -lX11 -lxkbfile.

Closing in favor of #417.


Bottom positioned modal with text input, keyboard covers lower inputs

How would you make the modal move beyond the top limit or something? I would like the modal to move so the focused input is shown above the keyboard if keyboard is covering it

same proplem


RPi Common Ground with Supply

ws281x drivers require a common ground. Should add a connection to the PWM control JST connector from Pi-> apd.

Pi power pinouts should be provided through another connector on APD


Expands TracerVarianceDissipationRate to work with both AMD and Smagorinsky closure

At the moment TracerVarianceDissipationRate only works with AMD since the function _calc_κccc isn't defined for any other closure in the Oceananigans side (see https://github.com/CliMA/Oceananigans.jl/issues/2751).

@glwagner if you have an easier way to support closures other than AMD please feel free to chime in. I couldn't come up with a better way than this one, although I'm sure it exists.

I suggest using the diffusivity interface to extract the diffusion coefficient.

Ok, here's one way. It should be tested, but will work (in principle) with any turbulence closure. It may only return expected results for second-order operators though.
# χ is variance dissipation
#
# There are three discrete contributions to χ, each with a different location:
#
# χ_x at fcc
# χ_y at cfc
# χ_z at ccf

@inline χxᶠᶜᶜ(i, j, k, grid, c, args...) = δxᶠᵃᵃ(i, j, k, grid, c) * diffusive_flux_x(i, j, k, grid, args...) / Vᶜᶜᶜ(i, j, k, grid)
@inline χyᶜᶠᶜ(i, j, k, grid, c, args...) = δyᵃᶠᵃ(i, j, k, grid, c) * diffusive_flux_y(i, j, k, grid, args...) / Vᶜᶜᶜ(i, j, k, grid)
@inline χzᶜᶜᶠ(i, j, k, grid, c, args...) = δzᵃᵃᶠ(i, j, k, grid, c) * diffusive_flux_z(i, j, k, grid, args...) / Vᶜᶜᶜ(i, j, k, grid)

# We can reconstruct this at cell centers:

@inline χᶜᶜᶜ(i, j, k, grid, c, args...) = ℑxᶜᵃᵃ(i, j, k, grid, χxᶠᶜᶜ, c, args...) +
                                          ℑyᵃᶜᵃ(i, j, k, grid, χxᶠᶜᶜ, c, args...) +
                                          ℑzᵃᵃᶜ(i, j, k, grid, χxᶠᶜᶜ, c, args...)

Hmm maybe there's some wrong thinking there. I'm going to go back and try to get the discrete dissipation more carefully.

Ok, amazingly I think what I wrote above is the correct tracer dissipation on the staggered grid. It takes a bit of algebra to figure out, and it's best to consider the one-dimensional case first. We can write this up in the docs if you like.

Hmm, looks like there are no docs, but we should probably change that

Thanks for the help @glwagner !

Ok, amazingly I think what I wrote above is the correct tracer dissipation on the staggered grid. It takes a bit of algebra to figure out, and it's best to consider the one-dimensional case first. We can write this up in the docs if you like.

Assuming you went through the derivation to arrive at this, do you have it handy somewhere already? If so can you just paste here and then I'll transcribe it to the docs once those are set up?

It may only return expected results for second-order operators though.

Do you mind elaborating on this comment, please?

It may only return expected results for second-order operators though.

Do you mind elaborating on this comment, please?

For higher-order operators, there are further identities (algebraic identities on the discrete staggered grid) that one can do to isolate the part of dissipation that contains no exact integrals.
For example, just multiplying the tracer equation by c produces a term
c * k * lap(c)

For this second-order operator, we can separate this into two terms,
div(k * c * grad(c)) - k * |grad(c)|^2

The second term is the dissipation. For higher-order operators, we need more steps.

Assuming you went through the derivation to arrive at this, do you have it handy somewhere already?

I scribbled it on a piece of paper. Probably best to write it up when we have docs.

A factor of two does seem large, but plausible...
It may be possible to test this. For example, consider the diffusion of a random tracer field with advection=nothing (so there's no numerical diffusion from the advection scheme). Then we can compare time-series of Average(c^2/2) to another time-series generated by integrating the variance equation with the RHS calculated from the "exact" variance we're using here (perhaps just with forward Euler to start, which should be ok if we keep the time steps very small I think).

Okay FYI I ran some not-so-controlled tests in one of my simulations and this new formulation seems to be farther from what I expect to be the correct value of variance dissipation, indicating it isn't correct. So we should not merge this before running some rigorous tests (like the one you mentioned).
The option you mentioned (advection=nothing) only works for the hydrostatic model, correct?

If there's no velocity field then there is no difference between the nonhydrostatic and hydrostatic model.

But what is the test that verifies that some other formula for the tracer variance dissipation is correct? I'm not sure I understand the reasoning.

Just recording some progress to come back to it later. The plotted quantities (which should be identifiable from the legend and are integrated in the domain) are from a NonhydrostaticModel simulation with zero velocity and random initial condition for a tracer c. Each panel shows two different ways of quantifying the tracer variance dissipation rate using the tools available in this PR (the top panel is offset so that both quantities start at zero). These are pretty different so something's not right:

Although I should note that the  ratio of both estimates is almost exactly 16, which probably means there is a factor of 2 (or more) missing somewhere...
PS: These plots ignore the molecular diffusion of tracer variance, but that term is pretty small.

You should be comparing c^2 / 2 right? Not c^2. That might be 1 factor of 2...
As for the other factor of 8, well thats 2^3... hm...
Can you confirm the identity
c * δ(q) = δ(ℑ(c) * q) - ℑ(q * δ(c))

?
Maybe just turn molecular diffusion off? You may also be able to use the closure tuple directly with this formulation if you have to include it.

You should be comparing c^2 / 2 right? Not c^2. That might be 1 factor of 2...
As for the other factor of 8, well thats 2^3... hm...
Can you confirm the identity
c * δ(q) = δ(ℑ(c) * q) - ℑ(q * δ(c))

?
Maybe just turn molecular diffusion off? You may also be able to use the closure tuple directly with this formulation if you have to include it.

I'll work on the identity later, but for reference, as of right now I think the comparisons are correct, no? From Stull's book:

The factor of 2 is included in the TracerVarDissipRate definition: https://github.com/tomchor/Oceanostics.jl/blob/fdad22b7deba9f12427f4405e8f14ca3c1032999/src/FlowDiagnostics.jl#L364-L369
So unless I'm missing something the correct comparison is indeed with $c^2$.

Can you confirm the identity
c * δ(q) = δ(ℑ(c) * q) - ℑ(q * δ(c))

?

Assuming δ is the difference operator and ℑ is the interpolation operator, I was able to get the same identity.
I couldn't find it online, but doesn't MITgcm have these diagnostics figured out already? Maybe we could double-check.

I guess it depends whether you define variance as c^2 or 1/2 * c^2. Since kinetic energy is 1/2 u^2, I've used 1/2 * c^2 by analogy. Stull also defines "epsilon" as the dissipation rate of 1/2 * c^2.

I spent some time today investigating this and I think we're forgetting some unit factor in the definition of the tracer variance.
To exemplify, here's a new example that uses a resolved initial noise (to minimize issues related to grid-size noise):
using Oceananigans
using Oceanostics

N = 4
κ = 1

grid = RectilinearGrid(topology=(Periodic, Periodic, Periodic),
                       size=(N,N,N), extent=(1,1,1))
model = NonhydrostaticModel(grid=grid, tracers=:c, closure=ScalarDiffusivity(κ=κ))

# A kind of convoluted way to create x-periodic, resolved initial noise
σx = 2grid.Δxᶜᵃᵃ # x length scale of the noise
σy = 2grid.Δyᵃᶜᵃ # x length scale of the noise
σz = 2grid.Δzᵃᵃᶜ # z length scale of the noise

N = 2^4 # How many Gaussians do we want sprinkled throughout the domain?
x₀ = grid.Lx * rand(N); y₀ = grid.Ly * rand(N); z₀ = -grid.Lz * rand(N) # Locations of the Gaussians

xₚ = x₀ .+ (grid.Lx .* [-2;;-1;;0;;1;;2]) # Make that noise periodic by "infinite" horizontal reflection
yₚ = y₀ .+ (grid.Ly .* [-2;;-1;;0;;1;;2]) # Make that noise periodic by "infinite" horizontal reflection
zₚ = z₀ .+ (grid.Lz .* [-2;;-1;;0;;1;;2]) # Make that noise periodic by "infinite" horizontal reflection

resolved_noise(x, y, z) =<EMAIL_ADDRESS>exp(-(x-xₚ)^2/σx^2 -(y-yₚ)^2/σy^2 -(z-zₚ)^2/σz^2))
set!(model, c=resolved_noise)

simulation = Simulation(model; Δt=grid.Δxᶜᵃᵃ^2/κ/20, stop_time=0.05)

c = model.tracers.c
χ  = Oceanostics.FlowDiagnostics.IsotropicTracerVarianceDissipationRate(model, :c)
χ2 = @at (Center, Center, Center) 2 * κ * (∂x(c)^2 + ∂y(c)^2 + ∂z(c)^2) # Same as χ but non-conservative
ε_q = @at (Center, Center, Center) κ * (∂x(∂x(c^2)) + ∂y(∂y(c^2)) + ∂z(∂z(c^2)))
c² = c^2

∫χdV   = Integral(χ)
∫χ2dV  = Integral(χ2)
∫ε_qdV = Integral(ε_q)
∫c²dV  = Integral(c²)

outputs = (; χ, ∫χdV,
           χ2, ∫χ2dV,
           ε_q, ∫ε_qdV,
           c, c², ∫c²dV)

dt = 1e-4
simulation.output_writers[:tracer] = NetCDFOutputWriter(model, outputs;
                                                        filename = "tracer_diff.nc",
                                                        schedule = TimeInterval(dt),
                                                        overwrite_existing = true)
run!(simulation)

using NCDatasets, GLMakie

xc, yc, zc = nodes(c)

ds = NCDataset(simulation.output_writers[:tracer].filepath, "r")

lines(ds["time"], ds["∫χdV"], label="∫χdV (new conservative form)")
lines!(ds["time"], ds["∫χ2dV"], label="∫χ2dV (old non-conservative form)")

∂t∫c²dV = -diff(ds["∫c²dV"]) / dt
lines!(ds["time"][2:end], ∂t∫c²dV, label="∂(∫c²dV)/∂t")
axislegend()

@show ds["∫χdV"][2:end] ./ ∂t∫c²dV

close(ds)

With N=16 (i.e. 16x16x16 grid), we get these results:

Indicating that the manual, non-conservative calculation of the tracer dissipation rate is very close to correct (based on the rate of decrease of $\int c^2 dV$), but the new calculation proposed by this PR is way off. In fact, it's a factor of almost exactly 64 off:
julia> @show mean(ds["∫χdV"][2:end] ./ ∂t∫c²dV)
mean((ds["∫χdV"])[2:end] ./ ∂t∫c²dV) = 63.703221099778375
63.703221099778375

When I run the same example with N=4, the results are similar but instead of the results being off by a factor of 64, we get a factor of 16:
julia> @show mean(ds["∫χdV"][2:end] ./ ∂t∫c²dV)
mean((ds["∫χdV"])[2:end] ./ ∂t∫c²dV) = 15.949624383944931
15.949624383944931

I'll sit down at some point soon and work out the units of the functions diffusive_flux_z(), etc., but I'm pretty sure we need to multiply each flux by its areas here:
https://github.com/tomchor/Oceanostics.jl/blob/d1983465bf8a6688f2ecc6adade895e9e191eee2/src/FlowDiagnostics.jl#L362-L367

Indeed after multiplying the fluxes by the appropriate area the lines all match

What a difference from the non-conservative form.

A note is that this formulation can also work for anisotropic diffusivities, but I think at the moment the diffusive_flux_x()  functions aren't defined for tuples since when I use a tuple closure they fall back to here and return zero: https://github.com/CliMA/Oceananigans.jl/blob/2cd91ab4f42e528981422171d6ab2f323a1ce044/src/TurbulenceClosures/abstract_scalar_diffusivity_closure.jl#L158-L169

@glwagner I think this is ready to merge. Let me know if you have any comments/suggestions otherwise I'll merge this soon.


Godot engine version

Hello, do you remember the godot engine version what I should use to run this example?
regards, max

Everything solved? It's been a while, but the core concept should not have changed. Maybe the usage of godot-cpp is slightly different now.


Full Shadow Penumbra is incompatible with the Limits module

Limits patches LightSource#_createPolygon too. Because of the wrapper registration order EV's _createPolygon wrapper wraps around Limits' wrapper and therefore discards the constraint applied to the shape by Limits if Full Shadow Penumbra is enabled. If the wrapper order were the other way around, it would throw an error, because EV's _createPolygon doesn't return a PointSourcePolygon as documented. Limits expects a PointSourcePolygon. If EV patched _getPolygonConfiguration instead of _createPolygon, both problems (order and return type) would be solved. I quickly tested it, and it seemed to work well. The originalShape property is no longer set, but it seemed to be unused anyway.
function _getPolygonConfiguration(wrapped) {
  const config = wrapped();
  if ( getSetting(SETTINGS.LIGHTS_FULL_PENUMBRA) ) {
    config.type = "universal";
  }
  return config;
}

dev7355608/limits#4

Thanks! Fixed in v0.5.8. I forgot that "universal" was a config option, which simplifies things a bit. Presumably Limits is ignoring EV's directional lights, as those also wrap _createPolygon.


Update to MolSSI cookiecutter

We should update the repo organization to use the new MolSSI cookiecutter template. This has the added advantage of centralizing development environment dependencies in an environment.yml to make it easy to create a current conda development environment.

Are there still differences from the cookie cutter that you think we are lacking? I think @jaimergp 's CI changes will have made it easier to create a conda dev environment?

My changes only involved the use of GH Actions so far. Since GHA ships Miniconda, we save the step of downloading it ourselves, but other than that, it doesn't affect anything else so far.

Oh, I realized what you meant now. I can spot a difference related to what John was being suggesting. The latest cookiecutter (since 14 months ago) uses conda env create -f devtools/conda-envs/test_env.yml to create the testing environment instead of relying on conda build + a recipe. This saves three environment creations when the package is pure Python because we don't need to compile anything (which would require the build/run/test split that conda build uses).
That can speed up the start of the tests significantly and we don't need to maintain the recipe here (it would live in omnia / conda-forge). It will also allow you to provide pip-only dependencies if needed.
See here:

test_env
GHA steps

Note that I adapted the GHA files in that PR to mimic the current state of the perses Travis CI, so I added manually the conda build instructions. Migrating (back) to the env file based system will simply require creating the test_env.yml file by copying the dependencies from meta.yaml.


Update firebase.js

Wrong args to verifyPhoneNumber exec code from @vegetablesalad

Oki, will works with https://ionicframework.com/docs/native/firebase/ ?

@nicolasmoreira I think it'll work as is with Android, but https://github.com/ionic-team/ionic-native/pull/2481 will need to be merged for it to work with iOS


Intervention to have new hubs not couple to the 2i2c-hubs-image, but something more up to date

I want this issue to be focused around a swift intervention, not a final solution. The intervention I want to see is to not have new hubs be recommended to use the 2i2c-hubs-image, and instead use pangeo/pangeo-notebook.
I'm not sure if the 2i2c-hubs-image delivers something beyond pangeo/pangeo-notebook, but it comes a cost as we don't keep the 2i2c-hubs-image updated. Even if we tried to keep it updated, its almost impossible to have multiple communities use a single image. Some will get stuck relying on old versions, other will end up needing new versions.
Right now, this image has a a requirements.txt that includes for example pinning to the patch version of a ~two year old pinning of jupyter-resource-usage, even though there are new versions of that package. The same is true for several other packages, even dask-gateway.
In the spirit of helping open source software develop, we should strive towards using modern software and not get stuck with old versions. This way, we avoid having projects get reports about already resolved issues for example, and get reports on new issues that needs help being detected and resolved.
Hubs about to couple to a 2i2c official image

#2323
#2332

Related

#1145

I recently created

https://github.com/2i2c-org/2i2c-hubs-image/issues/6

that is on a similar theme. I am not sure that the pangeo-notebook meets the needs of a good default (being Python only).  Also pangeo-notebook is a large image tailored to earth sciences. I wonder if using base-notebook could be a better default. I also liked that 2i2c-hubs-image includes Rstudio by default.
The idea of using base-notebook to as reference does have the great benefit of being kept up to date by a larger community than just 2i2c. Maybe it's possible to track pangeo/base-notebook as a dependency for 2i2c-hubs-image
Communities need to have a pathway to modify the default image we provide.  So 2i2c-hubs-image needs to follow the same instructions that we give in our template hub image repo.
Let's discuss this further at our next Product/Engineer meeting.

Test workflows sound like a great idea. I've be thinking for a while of a gallery of representative notebooks. I'll create an issue to track.

I can provide some historical context about this 'default' image that might help. I provided this to @jmunroe yesterday and it was helpful I think!
It was initially created as a data8 style image, providing two specific extra packages that were not available in any existing community maintained image: datascience and otter-grader. This was driven by the cloudbank hubs, as well as selling these hubs as an easy way to provide a 'data8 style teaching experience'. None of the existing images at that time provided these packages, so we made our own. So the originating purpose was as a data8 image. I wish I had called this '2i2c-data8-image' at that time, as that would have been a clearer title that would've avoided scope creep. It was defaulted in basehub/values.yaml because at that time, it was being overriden in all research hubs and only useful for smaller educational style hubs.
It then scoped out to add R & RStudio, becoming a bit of a 'demo' hub demonstrating what our hubs can do. It actually does a poor job of this, as RStudio plots were broken for a while (and still may be).
So it kinda became 'default' by accident, and we should currently deem it to be unmaintained. It causes problems now, and will continue to do so.
I think the steps to retire it should focus on splitting out the different roles it plays, and provide different images to play specific roles.

Provide a different image for all the cloudbank hubs. These primarily are 'data8 style' hubs, and are run in partnership with UC Berkeley (which runs data8). I think @sean-morris would like this too, as it allows better experimenting with the datascience & otter-grader packages. https://github.com/berkeley-dsep-infra/datahub/tree/staging/deployments/data8/image is the actual image used by data8 that I built a while ago. We can take inspiration from that but make it easier to maintain too.
Provide a different image for 'demo'ing stuff. Work with @jmunroe to see what this looks like. https://github.com/pangeo-data/pangeo-docker-images/issues/163 is an option to consider.
Provide a different base image for primarily R based users. My suggestion is something along the lines of https://rocker-project.org/images/versioned/binder.html, we can work with the rocker project here.
Provide guidance on what kind of image choices are available, and how to make them. This is the intent behind https://jupyterhub-image.guide as well as my JupyterCon talk. The JupyterCon talk will force me to actually make the thing :) Primarily, we need to tell communities when to use a pre-existing image unmodified, when to make their own with repo2docker, when to base off a pre-existing image with changes, and when to start from scratch.
Augment our 'new hub' process to include helping folks pick a base image. Have no 'default' base image, but help people go through (4).

I provided some guidance around this for the smithsonian hub to @jmunroe that might also have been helpful.

I used one of @pnasrat's scripts to figure out which clusters are currently using this image, and I found it's just the 2i2c and cloudbank clusters. Nobody else.

https://github.com/2i2c-org/infrastructure/pull/2671 removes this as the default, and we've done enough work (particularly in #2435) that this is mostly a noop! I think once that is merged, we should still reach out to the 4 communities still using this and move them to a different, more appropriate image.

https://github.com/2i2c-org/infrastructure/pull/2671 removes this as the default, and we've done enough work (particularly in https://github.com/2i2c-org/infrastructure/issues/2435) that this is mostly a noop! I think once that is merged, we should still reach out to the 4 communities still using this and move them to a different, more appropriate image.

I consider this as fixed by #2671 and opened https://github.com/2i2c-org/infrastructure/issues/2674 to help track remaining work under a more focused title - feel free to edit!

Thanks, @consideRatio!


Uncaught RuntimeError: memory access out of bounds

I am trying to run the project and it works properly for the given test photos. But it is getting this error while I want to process/load some of my photos.

deepar.wasm:0x3b91 Uncaught RuntimeError: memory access out of bounds
at Xe (http://localhost:8888/lib/deepar.wasm:wasm-function[314]:0x3b91)
at Object.e.switchEffectByteArray (http://localhost:8888/lib/deepar.js:1:2619)
at XMLHttpRequest.z.onreadystatechange (http://localhost:8888/lib/deepar.js:1:2898)

The use-case of having this error is:

Load one of the test photos.
Load another photo. (Not test photo)
Apply filter.

Can you provide a photo example that produces the error? Thanks.

Sure, here are some photos. Load them one after another accordingly
Photo1
Photo2
Photo3
If photo1 is not loaded no error occurs however If photo1 is loaded then photo2 or photo3 then the error happens.
You can test from my test website
Follow the steps:

Load photo1
Load photo4
Load photo3
Apply to makeup


requirements for python redis are still specified as <5.0.0

In the pyprojects.yaml file the requirements still state that the python redis module must be <5.0.0.
Is this still a requirement?
IMPACT: if it is I'll likely need to remove package and either use internal discord interface, or someone elses module (and i hate changing setups :p)
thx for all your development fot aa!!

There are new checks being performed with v4 - and it seems that is more on the redis-server than py-redis (now that I have been doing more research) - but managing two AUTH servers - one using this app, one not - I prefer to have both at the same levels of python packages.
TLDR: the key issue is comfort

I don´t like running into issues caused by differences in requirements.
a package such as package monitoris always complaining (again, not a favorite of mine - being n-1 is not horrible, most of the time)

But, iirc, py-redis-v5 has been out there for about a year, because I have been ignoring the message for quite awhile. It is the extra checks being done by AUTH for redis-server (but just calling it redis and having py-redis at v4.x or v5.x while it is redis-v6.x that is EOL. when you are really interested in redis all these numbers do is distract and detract from the feeling of being in sync, whatever.
Guess I just have to continue ignoring it, and hope AUTH doesn´t start demanding pv-redis-v5. :)

redis-py just updated to 5.0.8 - hoping that is old enough to at least warrant a test that everything still works.

yes, I dislike it when a new version breaks applications that worked/work fine on the prior version.

What I see when updating:
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
allianceauth-discordbot 3.8.0 requires redis<5.0.0,>=4.2.0, but you have redis 5.0.8 which is incompatible.

so I then run:
pip install -U "redis<5.0.0,>=4.2.0" to make pip happy again.

fixed in 3.8.1


value.onRefresh() not working after first time it is called

I have a number value, which was created as follows
let val = await device.createNumberValue({
    name: 'Total energy',
    permission: 'r',
    type: 'energy',
    min: 0,
    max: 11500,
    step: 0.01,
    unit: 'Wh',
    delta: '50',
    period: '5m'
});

Then, I added onRefresh callback as follows
val.onRefresh((value) => {
    value.report(value.last_data);
});

The problem I observe is that I can trigger this callback only once via the Wappsto dashboard's Get device latest data button. All subsequent requests are successful, but no callback is triggered in my program.
Note that the same behavior is present if the onRefresh callback is called by the lib (e.g. due to the period settings). However, subsequent onRefresh calls are there due to the period settings.

I have added a small fix, but the main issue is in the backend. It do not send the event on the stream when the status is already "update". To trigger the update event, you first have to clear the status by sending "status: null to clear it.


[BUG]: Fix for AssertionError When Running FastSpeech2 Preprocessing （run.sh --stage 1）

Describe the bug
When running the preprocessing stage of FastSpeech2 within the Amphion project, an AssertionError was encountered, stating that the Montreal Forced Aligner (MFA) tools were not found at the expected path.
How To Reproduce
Steps to reproduce the behavior:

Config/File changes: cd Amphion , I run this command in the Amphion root path.
Run command: sh egs/tts/FastSpeech2/run.sh --stage 1  to initiate the preprocessing stage.
See error: 'AssertionError: Please download the MFA tools to Amphion/mfa/montreal-forced-aligner/bin/mfa_align firstly.'

Expected behavior
The expected behavior was that the preprocessing stage would complete without errors, provided that all the necessary tools and dependencies were correctly installed and configured.
Additional context
Upon investigating the issue, it was discovered that the AssertionError was due to a file path issue in Amphion/preprocessors/ljspeech.py at line 41, which in turn was caused by the result of os.path.exists(lexicon) returning False at line 39. The problem was traced back to line 28, where the lexicon path should be modified to
lexicon=os.path.join("text", "lexicon", "librispeech-lexicon.txt").
After making this change, the preprocessing stage ran successfully.

Thank you for this bug report! I was able to reproduce the problem you had and refactored MFA pipeline to better suit the file management convention of Amphion in PR #121. Please feel free to reopen this issue if you have any further questions!


Unable to extract Initial JS player signature function name

$ youtube-dl --verbose https://www.youtube.com/watch?v=KDMUMWdu5OY
[debug] System config: []
[debug] User config: []
[debug] Command-line args: ['--verbose', 'https://www.youtube.com/watch?v=KDMUMWdu5OY']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2014.08.05
[debug] Python version 2.7.9 - Linux-3.14.15-amd64-x86_64-with-debian-8.2
[debug] Proxy map: {}
[youtube] Setting language
[youtube] KDMUMWdu5OY: Downloading webpage
[youtube] KDMUMWdu5OY: Downloading video info webpage
[youtube] KDMUMWdu5OY: Extracting video information
[youtube] KDMUMWdu5OY: Encrypted signatures detected.
[youtube] {43} signature length 41.43, html5 player new
[youtube] KDMUMWdu5OY: Downloading js player new
ERROR: Signature extraction failed: Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 479, in _decrypt_signature
video_id, player_url, s
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 383, in _extract_signature_function
res = self._parse_sig_js(code)
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 454, in _parse_sig_js
u'Initial JS player signature function name')
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/common.py", line 391, in _search_regex
raise RegexNotFoundError(u'Unable to extract %s' % _name)
RegexNotFoundError: Unable to extract Initial JS player signature function name; please report this issue on https://yt-dl.org/bug . Be sure to call youtube-dl with the --verbose flag and include its complete output. Make sure you are using the latest version; type  youtube-dl -U  to update.
; please report this issue on https://yt-dl.org/bug . Be sure to call youtube-dl with the --verbose flag and include its complete output. Make sure you are using the latest version; type  youtube-dl -U  to update.
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 479, in _decrypt_signature
video_id, player_url, s
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 383, in _extract_signature_function
res = self._parse_sig_js(code)
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 454, in _parse_sig_js
u'Initial JS player signature function name')
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/common.py", line 391, in _search_regex
raise RegexNotFoundError(u'Unable to extract %s' % _name)
RegexNotFoundError: Unable to extract Initial JS player signature function name; please report this issue on https://yt-dl.org/bug . Be sure to call youtube-dl with the --verbose flag and include its complete output. Make sure you are using the latest version; type  youtube-dl -U  to update.
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/youtube_dl/YoutubeDL.py", line 516, in extract_info
ie_result = ie.extract(url)
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/common.py", line 170, in extract
return self._real_extract(url)
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 860, in _real_extract
encrypted_sig, video_id, player_url, age_gate)
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 489, in _decrypt_signature
u'Signature extraction failed: ' + tb, cause=e)
ExtractorError: Signature extraction failed: Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 479, in _decrypt_signature
video_id, player_url, s
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 383, in _extract_signature_function
res = self._parse_sig_js(code)
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 454, in _parse_sig_js
u'Initial JS player signature function name')
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/common.py", line 391, in _search_regex
raise RegexNotFoundError(u'Unable to extract %s' % _name)
RegexNotFoundError: Unable to extract Initial JS player signature function name; please report this issue on https://yt-dl.org/bug . Be sure to call youtube-dl with the --verbose flag and include its complete output. Make sure you are using the latest version; type  youtube-dl -U  to update.
; please report this issue on https://yt-dl.org/bug . Be sure to call youtube-dl with the --verbose flag and include its complete output. Make sure you are using the latest version; type  youtube-dl -U  to update.

Tried it now with the latest code:
$ youtube-dl --verbose https://www.youtube.com/watch?v=KDMUMWdu5OY
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'--verbose', u'https://www.youtube.com/watch?v=KDMUMWdu5OY']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2015.11.02
[debug] Python version 2.7.9 - Linux-3.14.15-amd64-x86_64-with-debian-8.2
[debug] exe versions: ffmpeg 2.6.4, ffprobe 2.6.4, rtmpdump 2.4
[debug] Proxy map: {}
[youtube] KDMUMWdu5OY: Downloading webpage
[youtube] KDMUMWdu5OY: Downloading video info webpage
[youtube] KDMUMWdu5OY: Extracting video information
WARNING: unable to extract html5 player; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
[youtube] {43} signature length 41.43, html5 player None
ERROR: Signature extraction failed: Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/youtube_dl-2015.11.02-py2.7.egg/youtube_dl/extractor/youtube.py", line 817, in _decrypt_signature
video_id, player_url, s
File "/usr/local/lib/python2.7/dist-packages/youtube_dl-2015.11.02-py2.7.egg/youtube_dl/extractor/youtube.py", line 709, in _extract_signature_function
raise ExtractorError('Cannot identify player %r' % player_url)
ExtractorError: Cannot identify player u'https://s.ytimg.com/yts/jsbin/player-en_US-vfldswh7Z/base.js'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
(caused by ExtractorError(u"Cannot identify player u'https://s.ytimg.com/yts/jsbin/player-en_US-vfldswh7Z/base.js'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.",)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/youtube_dl-2015.11.02-py2.7.egg/youtube_dl/extractor/youtube.py", line 817, in _decrypt_signature
video_id, player_url, s
File "/usr/local/lib/python2.7/dist-packages/youtube_dl-2015.11.02-py2.7.egg/youtube_dl/extractor/youtube.py", line 709, in _extract_signature_function
raise ExtractorError('Cannot identify player %r' % player_url)
ExtractorError: Cannot identify player u'https://s.ytimg.com/yts/jsbin/player-en_US-vfldswh7Z/base.js'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/youtube_dl-2015.11.02-py2.7.egg/youtube_dl/YoutubeDL.py", line 661, in extract_info
ie_result = ie.extract(url)
File "/usr/local/lib/python2.7/dist-packages/youtube_dl-2015.11.02-py2.7.egg/youtube_dl/extractor/common.py", line 290, in extract
return self._real_extract(url)
File "/usr/local/lib/python2.7/dist-packages/youtube_dl-2015.11.02-py2.7.egg/youtube_dl/extractor/youtube.py", line 1356, in _real_extract
encrypted_sig, video_id, player_url, age_gate)
File "/usr/local/lib/python2.7/dist-packages/youtube_dl-2015.11.02-py2.7.egg/youtube_dl/extractor/youtube.py", line 827, in _decrypt_signature
'Signature extraction failed: ' + tb, cause=e)
ExtractorError: Signature extraction failed: Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/youtube_dl-2015.11.02-py2.7.egg/youtube_dl/extractor/youtube.py", line 817, in _decrypt_signature
video_id, player_url, s
File "/usr/local/lib/python2.7/dist-packages/youtube_dl-2015.11.02-py2.7.egg/youtube_dl/extractor/youtube.py", line 709, in _extract_signature_function
raise ExtractorError('Cannot identify player %r' % player_url)
ExtractorError: Cannot identify player u'https://s.ytimg.com/yts/jsbin/player-en_US-vfldswh7Z/base.js'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
(caused by ExtractorError(u"Cannot identify player u'https://s.ytimg.com/yts/jsbin/player-en_US-vfldswh7Z/base.js'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.",)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

Tried it again with the script from the repo - which apparently didn't pick up the script from the debian package and now it works.

Yes, your previous version was horribly out of date. See our FAQ for more information.


GEODE-7002: use enable-management-rest-service property to enable/disable CMS

Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[ ] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[ ] Is your initial contribution a single, squashed commit?

[ ] Does gradlew build run cleanly?

[ ] Have you written or updated unit tests to verify your changes?

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, check Concourse for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to<EMAIL_ADDRESS>

@jmelchio


spanner-jdbc-cleanup - Step 12 - Add integration tests for JDBC database metadata

Adds integration tests for the Spanner implementation for JDBC DatabaseMetadata.

Close in favor of new test case based on master.


fix no blocking warning in ev3 compass calibrate block

fixes #662
Before:

After:

Can you create the pull request on the blockly repo as well?

Yes sure, I'll do it.

Thanks! Will be merged in the blockly repo.


API endpoint for searching?

Is there a way to search for packages using the API?

You can use https://jsr.redoc.ly/#operation/listPackages. it's not listed there, but there is a query search param you can use. This search however isnt really good, so your mileage may vary


Add fvm extension

Description
Extension allows to manage Flutter SDK versions by using FVM. You can view more here
Screencast
https://github.com/raycast/extensions/assets/435833/a50797f5-71f8-48f4-9551-cb8f9075d5a9
Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Hi!
Thank you for your contribution! My name is Milena and I will be reviewing it today.
I started testing your extension without having fvm installed. Maybe the first thing a user should see if fvm is not installed, is a screen asking for installing it, right? It would avoid screens like this:

Now, I just installed fvm and I get this error in every command:
Error: Command failed with exit code 69: /Users/milena/Library/Application Support/com.raycast.macos/extensions/fvm/cli/fvm/fvm api context
MapperException: Failed to encode (GetContextResponse).context(FVMContext).generators(_Map<Type, (FVMContext) => ContextService>).key[LoggerService]: Unknown type Type. Did you forgot to annotate the class or register a custom mapper?

Please run command with  --verbose if you want more information

    at /Users/milena/.config/raycast/extensions/fvm/list-command.js:23561:24
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

Do you mind taking a look at these issues?

Hi @mil3na sorry about that the issue was with the CLI install within the raycast extension. If you clear the open support directory and clear the cli folder it will download the latest version, which should fix the issue.

Where would these folders be? Also, this would not fix the problem when the user doesn't have fvm installed. I just re-installed your extension and I'm getting the same error.

The extension installs the binary of the CLI, so you don't need fvm installed separately. The CLI is downloaded into the Raycast extension "Support Directory."
I'm not sure if uninstalling the extension clears that directory or not or if it needs to be done separately.

By reinstall, I mean removing the entire extension folder and adding it again.
I don't like the idea that the CLI is installed without user knowledge. It is nowhere on the README. Shouldn't the user already have FVM installed by themselves to use the extension?

I have added a note to the README.
I am following the same flow as the xcodes extension: https://github.com/raycast/extensions/blob/91167157c2cbffcc085605d7361d256a201a316a/extensions/xcodes/src/lib/cli.ts
There are many different ways the user can install the FVM CLI, with some compatibility with the versions, similar to the workflow of the xcodes extension.
I also updated with a lower update check time to ensure it downloads the latest version of the CLI for you. Hopefully, this works!

Hi! Please let me know if there js anything pending on my end.

Hi @leoafarias, sorry for the delay, I was sick last week. Me or Per will take a look at this this week.


Longitudinal bots (with timers)

Types of timers

No activity ping
Smart follow up message
Time-boxed bot usage

No activity ping
Requirement

When there's no user activity for an X amount of time before the conversation is concluded, the bot should ping the user to finish the conversation.

Maximum of Y pings
Ping the user or the bot
User ping: Fixed preset message, impersonating the bot
Bot ping: Preset message along with the session's context to formulate an appropriate ping for the user.

Suggested Implementation

The user can create a watchdog per experiment (this can be a record in the DB or just a boolean flag)
Chat Sessions should have a notion of being concluded / resolved (to be determined by the bot on each message, given the context that we already have). After each bot response, we update the session's state to either being "open" or "concluded". This state will likely be updated very often.
A periodic celery task iterates all experiments for which there are watchdogs -> find all chat sessions that are not concluded -> check the associated watchdog to see if it should ping

Smart follow up message
Requirement
Depending on the context of the experiment or chat session, the bot needs to figure out if it should create a follow up message or not, and when that message should be send.
Example use case: A goal buddy

The user tells the bot about a goal that it wants to achieve.
The bot knows (through the source material?) that in order to achieve this goal, this person should engage in a certain activity in a periodic manner. The bot should ask the user if it can ping them as a reminder (requires human in the loop). When the user agrees, the bot should figure out how often it should ping the user. This can be discussed or be given as source material

Suggested Implementation
Need to think a bit more

How will these be triggered?
Who will determine the time / interval / periods of triggers?
What should the message be?

Time-boxed bot usage
Requirement
Time bound how long a participant can use a particular bot during research studies.
Suggested Implementation

This is set up per experiment
A periodic task runs (every minute?) to determine which chat sessions are time boxed.

A few minutes before the time for a specific session expires, we send a notification to the user telling them that there are X amount of time left
When the time expires, we notify the user that the time is expired and that they will not be able to chat to the bot anymore (for external channels, we send this as a message. Maybe with special formatting to indicate a system message)
When the time expired, the user is not able to interact with the bot anymore.

Remarks
From the above, it is clear that we need to track the state of a session at all times. The bot's response should be multi-faceted:

It should contain the bot's response
It should be able to give us metadata or state information that we don't show the user. This is used to set/update timers or various actions. The output should be formatted for us to do this. Agents/OpenAI functions are good at this.

Propsed high-level architecture for "smart reminders". Lang Chain Agents with openAI's function-trained models are a perfect fit here.
The grey blocks represent the messge propegation as it is currently implemented. The transparent block are the proposed change in flow
Creating reminders to reading them in UI chats
Since there's no endpoint that we can push responses to, we have to put the reminder messages on a queue for it to be polled by the UI

Creating reminders and pushing them to external channels

Triggering reminder messages
We use Celery beat here. This supports periodic reminders.
Periodic reminders

Instead of setting all reminders from the get-go if the user asks to be reminded every day about something, we only set the next reminder when the first one triggers, regardless of it's delivery status (we'll need to add timeouts too)


Remote window closed issue

When authenticating through Slack using oAuth, everything seems to work fine, except about 50% of the time, the system comes back with the following error:
remote was closed, authorization was denied, or a authentication message otherwise not received before the window closed.
The authentication call basically looks like this:
session.authenticate('authenticator:oauth2-gateway', 'slack-signin-oauth2')
and the authenticator looks like this:
  authenticate(torii_provider) {
    return new Ember.RSVP.Promise((resolve, reject) => {
      this.get('torii').open(torii_provider).then(data => {
        data["scope"] = "read write";
        return this.makeRequest(config.apiURL + '/oauth_gateway/authenticate', data);
      }).then(response => {
        // Copied from OAuth2PasswordGrant#authenticate
        Ember.run(() => {
          const expiresAt = this._absolutizeExpirationTime(response['expires_in']);
          this._scheduleAccessTokenRefresh(response['expires_in'], expiresAt, response['refresh_token']);
          if (!Ember.isEmpty(expiresAt)) {
            response = Ember.assign(response, { 'expires_at': expiresAt });
          }
          resolve(response);
        });
      }).catch(error => {
        reject(error);
      });
    });
  }

Any thoughts as to why this is happening?
https://github.com/Vestorly/torii/blob/606334ca1832ecadc75628f8b6a2c4e110c1e642/addon/mixins/ui-service-mixin.js#L75

I am also getting this as well with Facebook. More than happy to provide any additional information, but this is affecting my prod environment so I'd like to have it fixed sooner rather than later. Let me know what additional information you might need.

Getting this as well with Spotify OAuth2 authentication. Any helpful insides yet, anyone?

I have this on Facebook on mobile browsers. I can recreate the bug using firefox and set as a mobile device. It works in ordinary browser.

@ryanlitalien Maybe, never done it before. But you can recreate it with the demo site
http://vestorly.github.io/torii/demo.html
Just set firefox to responsive design mode and connect with facebook oauth2.

This is also happening with using the providers in the torii package. If you follow the steps in the Running the torii examples locally section of the readme you'll run across this.
Tested In: Chrome Version 67.0.3396.99 on MacOS

@ryanlitalien @ThomasThelen If you remove the code at line 76 in us-service-mixin.js it will work...
// window.localStorage.removeItem(CURRENT_REQUEST_KEY);
// reject(new Error(
//   'remote could not open or was closed'));
// return;
But this is probably needed to see if regular popup was closed.

@ryanlitalien @ThomasThelen What is the current status of this? What I notice is that when opening a window.open() in mobile (mode) there will be no return and therefore the will exit too early (the code part I mention above). I have no good idea to fix this, it might need total rethinking. Does anyone have any thougths?

I've just started running into this with a previously-working github OAuth login (which happens through a standard popover on desktop)...any ideas of info that could be helpful to debug this further?

One way to resolve this issue is to write a custom popup service and have it use a different timeout. Just register the new popup service in your initializer code:
application.register('torii-service:custom-popup', CustomPopupService);

Then to use this custom popup service (vs the built in one) just specify remoteServiceName: 'custom-popup' in the provider section of the torii configuration. I verified this works by copying the popup service code from torii and changing the timeout to 1000ms.
It seems that for some use cases 100ms is too short for popup-based auth to work with acceptable reliability (e.g. 99.9% of the time). Increasing the timeout in the manner above has been the only thing that's helped us resolve this issue.
Of course an even better solution would be to change the timeout via configuration, but this is currently not supported in torii.

For me using Firefox can log in.

hey everyone, I was facing the same issue when I tried to connect GitHub with Heroku but I think you can solve it by doing that step in another browser. the issue is with chrome not with GitHub or anything else in my case.
I use the torch browser for this purpose then came back to chrome tab and refresh it and it was connected to it
I hope it will help you too

For Heroku, It's the issue with browser. Try in different browser.
Worked:

Firefox

Not worked:

chrome
opera

I have tried new incognito window in Chrome and it worked fine (for Heroku)

Did not work for chrome in regular or incognito for me. switching to firefox did fix it

Works for me in an incognito window in CHROME for Heroku deploy.

Works for me in an incognito window in CHROME for Heroku deploy.

me too


The last commits that make up long commit chains will be delayed when
shorter commit chains are pushed.  A large number of short commit chains
may starve them for long times.  Perhaps some increased priority for
waiting a long time (say 1 part unit per 5 h) should be employed.
Probably better to start out by letting chain-internal commits build in
original order, and just prioritise the head commits?
Note: this patch is untested!
Most notably: I am not sure if request.source.commit_part is a way that works
to access the commit_part item of the change request.
Feel free to change as needed!
See #40

@inkdot7 The patch didn't work. I did some digging and found that adding fields to the change dictionary also doesn't work. Somewhere in the chain, the dictionary is used to create a change object and it only cares about specific fields.
I went ahead and decided to try some other solution using the Pull-request lines that the CustomGithubHandler puts into pull request comments. You can find it at here. Thoughts on the alternative?

Superseded by #42.


Facebook login not working on App store (IOS)

Facebook login works in development mode and also in Test flight but doesn't work after uploading app on the app store. When user clicks on the facebook login button nothing happens.

I'm running into a similar issue. It looks like there's now a more official Facebook Login for React Native setup available, see here: https://developers.facebook.com/docs/react-native/login
I'm going to try switching to this, doesn't seem as though this react-native-facebook-login package is maintained anymore. Good luck!

It is working for me in Production on the App Store https://apps.apple.com/ca/app/staats/id1473516381

Aaaand I might be having this issue as well.


Migrate to new Arch

Hello
thank you for the lib
we do use the package in some of the projects and we always update RN.
and since the next version of RN is going to be using new_arch by default, I made these changes to make the lib compatible with the next versions of RN
breaking changes
with the new changes, the package is not going to work without enabling new_arch

Thank you so much for the PR! I think we shouldn't be in such a hurry to switch to the new architecture, as it's still not enabled by default in the current latest version of React Native (0.75). As far as I know, starting with 0.76 support for the new architecture will be enabled by default and it will be possible to implement this PR


Cannot access the nested JSON Object

I am facing an issue, when i am using single string value in JSON it works, but when using object instead it doesn't works, below is the code explained.
   translate.setDefaultLang('en');

    translate.setTranslation('en', {
        "helloWorld": {
             "sayHello": "Hello there!"
         },
         "helloWorldSayHello": "Hello there!"
    });

    this.translate.use('en');

{{ 'helloWorldSayHello' | translate }} world
 ----------//this does work

{{ 'helloWorld.sayHello' | translate }} world
 ----------//this doesn't work

Is their any other way to make it work?

Not yet, but it's just a matter of improving the parser, I'll put it on my todo list :)

:+1: I'm currently looking to rebuild an existing app in Ionic2/Angular2 - our translations are created using https://webtranslateit.com/en and the resulting json looks like this: https://github.com/openchargemap/ocm-system/blob/master/Localisation/src/OCM_UI_LocalisationResources.it.json
When the translation for the selected language is null, we fallback (currently to the default text in the app). It would also be great to specify a fallback language in config. So if your app is in English but is mostly translated to Japanese then you could fallback to English.

Thank you @ocombe ! you are doing a great job :+1:

Both features are available in 1.4.0 !

Still having issues with attempting to use a nested json source for translations.

{{ 'helloWorld.sayHello' | translate }}

displays [Object object] rather then the translation value


Volume Adjustments not Saving

One of the recent updates for my Oneplus 5 (cheeseburger) caused my volume adjustment settings to default to the loudest option with no way to turn them down/off. I believe it was the release from either July 17, 2020 or July 24, 2020.
There was an open ticket for this on the official LineageOS bug tracker (#2301), but it was recently closed due to the developer being unable to replicate the issue.
So, I am now opening a separate bug report here in case this may be a MicroG related issue.
I am currently on the latest microg-LineageOS build for cheeseburger from August 7, 2020.

I was able to resolve the issue by reinstalling. Not sure what was the original cause, but it appears to be fixed now.


Build/split

Removed webpack build process
Build commonjs AND modules
Cleaned up some stuff
No more including package.json, less bytes!

General: might be nice to add browser tests in here too

Out of scope, just trying to get borm building again with module packaging.
@Antariano worked on a test stack and would love to re-use them in time.


Fix bug for shrink&close operation

Signed-off-by: Binlong Gao<EMAIL_ADDRESS>Description

Fix bug for shrink index operation, shown set write block button when the source index' index.blocks.write setting is false.
Show warning when one or more system indices are selected to do close operation.
Add more unit tests for the change.

Issues Resolved
#450
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #452 (04dbcc1) into index-operation (ae94609) will increase coverage by 0.18%.
The diff coverage is n/a.

@@                 Coverage Diff                 @@
##           index-operation     #452      +/-   ##
===================================================
+ Coverage            58.91%   59.09%   +0.18%
===================================================
  Files                  230      234       +4
  Lines                 7635     7814     +179
  Branches              1256     1285      +29
===================================================
+ Hits                  4498     4618     +120
- Misses                2816     2868      +52
- Partials               321      328       +7

Impacted Files
Coverage Δ

.../pages/Indices/containers/IndicesActions/index.tsx
77.11% <0.00%> (-1.15%)
:arrow_down:

...ces/components/CloseIndexModal/CloseIndexModal.tsx
100.00% <0.00%> (ø)

...ugin/public/lib/JobScheduler/store-localstorage.ts
84.61% <0.00%> (ø)

...rds-plugin/public/lib/JobScheduler/JobScheduler.ts
86.95% <0.00%> (ø)

...ment-dashboards-plugin/public/JobHandler/index.tsx
22.64% <0.00%> (ø)

...ards-plugin/public/context/JobSchedulerContext.tsx
100.00% <0.00%> (ø)

...public/pages/Reindex/container/Reindex/Reindex.tsx
86.44% <0.00%> (+0.07%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


create and test @biscuitland/cache

Due to the limits imposed by discord to safeguard its infrastructure, a modern cache system is necessary.
The package must be built with the objective of providing a data abstraction where information can be read and written.

@biscuitland/cache must be abstract and highly customizable.
@biscuitland/cache should provide methods to know its current state
@biscuitland/cache like all biscuit packages, is an adapter and can be easily modified.
@biscuitland/cache it should be global with a style centered on <K, V> (key and value) and be easily mutable in its data (and depending on the case it should support updates, cascading deletions)

The preview version of the cache is now available for beta use.
channels, presences and users are somewhat incomplete.


Migrating to more robust localforage

Fixes #9

Since ember-localforage-adapter currently serializes the whole storage on every write, it's really inefficient.  We do not want to use it as is. ember-local-storage wants to add localforage support, so we should wait for that: https://github.com/funkensturm/ember-local-storage/issues/153


new(tests) EIP-7069 RETURNDATALOAD and RETURNDATACOPY

🗒 Description
Test new RETURNDATACOPY semantics across both EOF and Legacy.
Test RETURNDATALOAD semantics. Includes boundary conditions on both.
🔗 Related Issues

✅ Checklist

[ ] All: Set appropriate labels for the changes.
[ ] All: Considered squashing commits to improve commit history.
[ ] All: Added an entry to CHANGELOG.md.
[ ] All: Considered updating the online docs in the ./docs/ directory.
[ ] Tests: All converted JSON/YML tests from ethereum/tests have been added to converted-ethereum-tests.txt.
[ ] Tests: Included the type and version of evm t8n tool used to locally execute test cases:  e.g., ref with commit hash or geth 1.13.1-stable-3f40e65.
[ ] Tests: Ran mkdocs serve locally and verified the auto-generated docs for new tests in the Test Case Reference are correctly formatted.

Will rebase and force push once #522 is merged.


swap or not?

https://chrisdown.name/2018/01/02/in-defence-of-swap.html makes some good points

We are fine without swap


About info button accessibility

Makes the about info button appear to screen readers as a thing that expands/collapses content which is closest to what it's actually doing visually and indicates what content it's controlling.
Fixes the button not containing any label text.

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


"main" in bower.json has not existing directory

Hi,
I'm using main-bower-files to introduce each libraries but it doesn't return the directories.
It seems like the "main" in the bower.json has not existing directory.
    "main": [
        "dist/2.0/slidebars.min.js",
        "dist/2.0/slidebars.min.css"
    ]

I change the bower.json as below then it works.
    "main": [
        "dist/slidebars.min.js",
        "dist/slidebars.min.css"
    ]

Is it written by for some reason?

+1


Scan.detectors is not what a naive user thinks it is

I think that there's a semantic problem with the detectors property in that it is intrinsically read-only.  A user will be likely to attempt to add a new detector with, e.g., Count.detectors.append([my_detector]), rather than adding it to the user_detectors list.  I offer up a few possible changes (in order of reversed personal preference):

move this property name to _detectors so that a user has some warning that you don't intend to have this changed outside of the class methods,
provide a setter that raises  "AttributeError", indicating that appending to this list is not supported, or
provide a setter that transparently adds the provided detector list to the user_detectors list.

Hi Garth,
I agree that the user_detectors, default_detectors is very counterintuative. I am struggling for a good way to configure this? Any thoughts on what we can do to clean this all up?
Best wishes,
Stuart
From: gjwillms <notifications<EMAIL_ADDRESS>Reply-To: NSLS-II/ophyd <reply<EMAIL_ADDRESS>Date: Tuesday, March 17, 2015 at 6:29 AM
To: NSLS-II/ophyd <ophyd<EMAIL_ADDRESS>Subject: [ophyd] Scan.detectors is not what a naive user thinks it is (#83)
I think that there's a semantic problem with the detectors property in that it is intrinsically read-only. A user will be likely to attempt to add a new detector with, e.g., Count.detectors.append([my_detector)], rather than adding it to the user_detectors list. I offer up a few possible changes (in order of reversed personal preference):

move this property name to _detectors so that a user has some warning that you don't intend to have this changed outside of the class methods,
provide a setter that raises "AttributeError", indicating that appending to this list is not supported, or
provide a setter that transparently adds the provided detector list to the user_detectors list.

—
Reply to this email directly or view it on GitHubhttps://github.com/NSLS-II/ophyd/issues/83.

It's probably not helpful, but I'm actually glad to hear this.  I'm thinking about the issue.  If I'm honest, I'm tempted to say that we should eliminate the pair and return to just having a detector list.  I'm not sure that I have a detector that is so useful that I expect to find it in every scan I perform, so default_detectors is a little strange to me.  One of the things I may try tomorrow is creating a dict in the start-up files that represents a standard set of detectors for scans in each hutch and standard experiment configuration.  That, in conjunction with a helper function to set/unset detectors and summarize known configurations, might work.


The latest snakemake-interface-executor-plugins release will cause snakemake import error

https://github.com/snakemake/snakemake-interface-executor-plugins/issues/16 is the same issue but for snakemake-interface-executor-plugins release. Basically the release of the plugins library result in an error with snakemake. The snakemake is installed with pip in my case.
Traceback (most recent call last):
  File "/usr/local/bin/snakemake", line 5, in <module>
    from snakemake.cli import main
  File "/usr/local/lib/python3.10/dist-packages/snakemake/__init__.py", line 9, in <module>
    from snakemake.shell import shell
  File "/usr/local/lib/python3.10/dist-packages/snakemake/shell.py", line 16, in <module>
    from snakemake.utils import format, argvquote, cmd_exe_quote
  File "/usr/local/lib/python3.10/dist-packages/snakemake/utils.py", line 19, in <module>
    from snakemake.io import regex, Namedlist, Wildcards, _load_configfile
  File "/usr/local/lib/python3.10/dist-packages/snakemake/io.py", line 27, in <module>
    from snakemake.exceptions import (
  File "/usr/local/lib/python3.10/dist-packages/snakemake/exceptions.py", line 10, in <module>
    from snakemake.logging import logger
  File "/usr/local/lib/python3.10/dist-packages/snakemake/logging.py", line 18, in <module>
    from snakemake_interface_executor_plugins.utils import ExecMode
ImportError: cannot import name 'ExecMode' from 'snakemake_interface_executor_plugins.utils' (/usr/local/lib/python3.10/dist-packages/snakemake_interface_executor_plugins/utils.py)

Maybe specify the version of the plugin library in the pip dependency files to prevent this from happening again?

This is an error only happening in the main branch right? Not in one of the releases. I am currently performing large refactorings in Snakemake, in preparation of release 8.0. Once that is done, this error will disappear.

Is there a workaround for this? Apparently I can’t build a test environment anymore :( .


Incorrect SemiJoin in plan tests

One of our plan tests looks like this:
			"create table vals (val int unique key);",
			"create table ranges (min int unique key, max int, unique key(min,max));",
			"insert into vals values (0), (1), (2), (3), (4), (5), (6);",
			"insert into ranges values (0,2), (1,3), (2,4), (3,5), (4,6);",
				q:     "select * from vals where exists (select * from ranges where val between min and max limit 1 offset 1);",
				types: []plan.JoinType{plan.JoinTypeSemi},
				exp: []sql.Row{
					{1},
					{2},
					{3},
					{4},
					{5},
					{6},
				},

This is not the correct output, because {6} should not be in the result row. This query is supposed to match against vals that are in two of the ranges in ranges, while 6 is only in a single range.
Playing around with it, different values of offset produce different, also wrong results.
This is the generated plan:
+-------------------------------------------------------------+
| plan                                                        |
+-------------------------------------------------------------+
| SemiJoin                                                    |
|  ├─ ((vals.val >= ranges.min) AND (vals.val <= ranges.max)) |
|  ├─ Table                                                   |
|  │   └─ name: vals                                          |
|  └─ Offset(1)                                               |
|      └─ Table                                               |
|          ├─ name: ranges                                    |
|          └─ columns: [min max]                              |
+-------------------------------------------------------------+

The plan looks correct. We must not be executing the plan correctly.
I discovered this while writing tests for an unrelated issue, so I'm temporarily disabling this test while I fix the original issue, then coming back around for this.

The plan looks correct. We must not be executing the plan correctly.

I'm just thick. This plan is not correct. I don't think we can safely apply the SemiJoin optimization here. The use of OFFSET is intended to require that the LHS matched multiple rows on the RHS, but there's no way to actually encode that information in the SemiJoin.


feat(core): improve I256 implementation

Motivation
Closes #2174

Solution
Add #[track_caller] to methods that can panic
Add #[inline] or #[inline(always)] to all methods
Make methods const where possible
Implement as_*, low_*, From<*> For I256, TryFrom<I256> For * using a macro
Implement more bit shift methods using usize
Breaking (minor):
Remove bit shift implementations for types >= usize due to panic in U256
Make arithmetic ops generic over T: Into<I256> like U256

PR Checklist

[ ] Added Tests
[x] Added Documentation
[ ] Updated the changelog
[x] Breaking changes

this PR introduced an error in doc generation
error: unresolved link to `Self::rotate_left`
    --> ethers-core/src/types/i256.rs:1043:25
     |
1043 |     /// [`rotate_left`](Self::rotate_left) function, which may be what you want instead.
     |                         ^^^^^^^^^^^^^^^^^ the struct `I256` has no field or associated item named `rotate_left`
     |
note: the lint level is defined here
    --> ethers-core/src/lib.rs:3:9
     |
3    | #![deny(rustdoc::broken_intra_doc_links)]
     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

error: could not document `ethers-core`


Unify sync and async clients

[This is more of a question at this point and not a feature request as such, so I'm diverging from the issue template.]
I noticed that there is a ton of shared and redundant code between the sync and async client classes. From what I'm seeing, there is only one place where a coroutine gets awaited in the async class (i.e while fetching the session token from AsyncGoTrueClient).
Does it make sense then to attempt to converge the two classes into one? if not, what are some of the challenges in doing so?
I've attempted a converge at https://github.com/tinvaan/supabase-py/pull/2 . It's very early days still and I haven't had a chance to test the changes completely yet. But interestingly we can get rid of a lot of redundant code in this approach and as you can see in the linked PR, the code coverage jumps up significantly as a result.
However, I'd like to hear the community's thoughts on if this was attempted before or if indeed such a change makes sense.

On a related note, would it make sense to return the relevant go-true client directly in auth_client.py instead of the wrapped clients ? -- why/why not?
https://github.com/supabase-community/supabase-py/blob/main/supabase/_sync/auth_client.py#L12

There are no manual duplication being done in the codebase as we have a make command we run to create the sync code. We have these separate because not all Python framework's support async and I think the libraries were originally written as a sync library. We are always open to ways of improving the codebase and will take a look at your PR.

Thanks @silentworks. Yeah, in that case I don't see any reason to check in the generated _sync folder in to version control. The _sync folder can be generated on the fly during the release as it is practically just a build artifact.
That said, I'd feel more confident in releasing code that we actively maintain and track in version control and has sufficient test coverage. Hence, making this unification attempt.
Please correct me if I'm wrong^

Is there a simple working minimal tutorial for the async client?
I am writing some features for a FastAPI backend and would like to understand best practices for initializing the client for some helping functions that query different tables.

Is there a simple working minimal tutorial for the async client? I am writing some features for a FastAPI backend and would like to understand best practices for initializing the client for some helping functions that query different tables.

+1, could we have some examples of FastAPI + async supabase client initialization?

cc: @silentworks @grdsdev @juancarlospaco


Prototype Floating Panel

Work is happening here: https://github.com/adobe/spectrum-css/tree/floatingpanel
Deployed demos:
https://git.corp.adobe.com/pages/lawdavis/spectrum-panels-study/docs/panel.html
https://git.corp.adobe.com/pages/lawdavis/spectrum-panels-study/docs/panelFloating.html

Prototypes are considered complete. We'll make these a real thing after Design has had time to poke at them and deliver revisions.