Add ETag support to both server and client

Is your feature request related to a problem? Please describe.
The ETag is not returned from the server's API. There is no configuration to enable it.
The client doesn't make use of ETag at all.
Describe the solution you'd like
The ETag header can be easily added to the response header using the ShallowEtagHeaderFilter of Spring Web. This calculates the value from the response body. In case of GIT being configured as the environment repository, the ETag can be set to the value of the commit ID of the given label. This would simplify the ETag calculation (i.e. doesn't need to resolve all files) and would add the possibility to return ETag in the HEAD response body.
The client can then consider the ETag to figure out if it needs to fetch the configuration from the server again. This is useful in the configuration reload use cases.
Describe alternatives you've considered
none
Additional context
n/a

I have a working implementation of the general requirement that passes the tests, and could submit a PR if you'd like. Essentially, it was sufficient to add ShallowEtagHeaderFilter to EnvironmentRepositoryConfiguration.
To implement the specific solution based on Git commit hashes, I'd need a pointer to the code locations where I could conveniently get hold of these. If you could give me a rough idea, I'd be happy to add that as well.


Move out protos from nearcore repo into a separate repo

Protos are part of the specification that different components of the system use.
We should have them in separate repo, that also provides Rust, JS, Python, etc packages that ppl can use without needing to re-build them.

No more protos


Update download links for ancestry random forest models

Resolves #1141
To be merged and deployed after https://github.com/broadinstitute/gnomad-blog/pull/119 is merged and deployed
Updates the download links on the gnomAD browser to point to the newer ONNX formatted random forest models.

rileyhgrant I merged broadinstitute/gnomad-blog#119

Great, thanks for letting me know, and for doing that @jkgoodrich!


[gNMI-1.5]: Update telemetry_port_speed_test

There could be a timing issue where OperStatus state is not updated yet, update the test to use gnmi.Await() and print out the received value if the value doesn't match the expected value.

Pull Request Functional Test Report for #2921 / 5c739d19763c74feb2ee5744848dfddfff729685
Virtual Devices

Device
Test
Test Documentation
Job
Raw Log

Arista cEOS

RT-1.52: BGP multipath UCMP support with Link Bandwidth CommunitygNMI-1.5: Telemetry: Port Speed Test

Cisco 8000E

RT-1.52: BGP multipath UCMP support with Link Bandwidth CommunitygNMI-1.5: Telemetry: Port Speed Test

Cisco XRd

RT-1.52: BGP multipath UCMP support with Link Bandwidth CommunitygNMI-1.5: Telemetry: Port Speed Test

Juniper ncPTX

RT-1.52: BGP multipath UCMP support with Link Bandwidth CommunitygNMI-1.5: Telemetry: Port Speed Test

Nokia SR Linux

RT-1.52: BGP multipath UCMP support with Link Bandwidth CommunitygNMI-1.5: Telemetry: Port Speed Test

Openconfig Lemming

RT-1.52: BGP multipath UCMP support with Link Bandwidth CommunitygNMI-1.5: Telemetry: Port Speed Test

Hardware Devices

Device
Test
Test Documentation
Raw Log

Arista 7808

RT-1.52: BGP multipath UCMP support with Link Bandwidth CommunitygNMI-1.5: Telemetry: Port Speed Test

Cisco 8808

RT-1.52: BGP multipath UCMP support with Link Bandwidth CommunitygNMI-1.5: Telemetry: Port Speed Test

Juniper PTX10008

RT-1.52: BGP multipath UCMP support with Link Bandwidth CommunitygNMI-1.5: Telemetry: Port Speed Test

Nokia 7250 IXR-10e

RT-1.52: BGP multipath UCMP support with Link Bandwidth CommunitygNMI-1.5: Telemetry: Port Speed Test

Help

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 55.448%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1949

Relevant Lines:
3515

💛  - Coveralls


How to manage input value in column?

I have case when one of the columns must be controled input...
CodeSandbox - https://codesandbox.io/embed/wqrmj7410k
What is the best approach to manage value of this input?

https://codesandbox.io/s/j7y248799y
How about that?

https://codesandbox.io/s/j7y248799y
How about that?

sorry but I don't see any changes only in dependencies was add lodash

Ah damn, ok let me work on this example again. Sorry about that. I'll have some time this weekend

I was able to achieve this with customBodyRender in a column:
customBodyRender: (value, tableMeta, updateValue) => {
  return (
    <div>
      <input
        type="number"
        onBlur={event => {
          updateValue(event.target.value);
          // then you could call some function to update your state somewhere
          this.someFunctionToUpdateState({})
        }}
      />
    </div>
  );
}

The only issue is that I am unable to sort the table and have those input values stay in the correct row - I had it working at one point but something blew up and I must have obliterated my solution. I've tried setting defaultValue in the input prop, but no luck.

@aflansburg The problem is that your inputs need a value or they will not be sorted properly, as there will be nothing to sort them on. I have a PR up with an updated example of some form inputs being added to a table.

@gabrielliwerant Yeah thanks, I just noticed that - so I was using onBlur as the onChange method causes rerendering of every row so typing in the input element was a bit laggy. If I can figure out a way to prevent rows without changed inputs from re-rendering it should kill the lag. I've moved to using a ref which seems to have helped so my component looks more like this now - in case anyone else comes across a similar use case:
<input
  ref={input}
  style={{ width: 60 }}
  type="number"
  value={requested || value}
  onChange={event => {
    updateValue(input.current.value);
    this.updateSomeArray({});
  }}
/>


__tuple_leaf assignment operators need to silence nvcc warnings

Because they can execute user code, __tuple_leaf::operator()s need to be annotated in such a way as to silence warnings of the form warning: calling a __host__ function from a __host__ __device__ function is not allowed.

Also swap, because it may call a user-defined swap function via ADL.


Single port design

Hey,
Please have a look at the Single Endpoint for Infinispan Server design.
There's also a bonus here... Since our Wiki doesn't allow inline comments, I would like to propose storing designs in a dedicated directory along with the sourcecode. This approach has been successfully used by Kubernetes and I highly encourage us to take this path.
Thanks,
Sebastian

Let's use the newly-created repo https://github.com/infinispan/infinispan-designs for this
Using the main infinispan repo creates noise, triggers CI, etc.


fix(examples): Dynamic Rollup Config Loading

Description
Updates the trusted-sync example to dynamically load the rollup config based on the l1 chain id.
In the future this will be upstreamed into the superchain-registry.
Metadata
Fixes #292.

Codecov Report
Attention: Patch coverage is 0% with 8 lines in your changes missing coverage. Please review.

Project coverage is 79.4%.

Files
Patch %
Lines

crates/derive/src/online/alloy_providers.rs
0.0%
8 Missing :warning:

Additional details and impacted files

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Error transcribing file on line 'NoneType' object is not iterable

Which OS are you using?

OS: Windos 10

Short videos like songs work well.
However, longer videos (large in size) will cause errors.
As you suggested in #97, I tried downgrade the version of faster-whisper , or remove venv and reinstalling install.bat, but the same error occurs.
I have 16g vram,  nvcc --version is below
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2024 NVIDIA Corporation
Built on Tue_Feb_27_16:28:36_Pacific_Standard_Time_2024
Cuda compilation tools, release 12.4, V12.4.99
Build cuda_12.4.r12.4/compiler.33961263_0
Error :
Error transcribing file on line 'NoneType' object is not iterable
D:\project\Whisper-WebUI\venv\lib\site-packages\torch\cuda\memory.py:330: FutureWarning: torch.cuda.reset_max_memory_allocated now calls torch.cuda.reset_peak_memory_stats, which resets /all/ peak memory stats.
warnings.warn(
Traceback (most recent call last):
File "D:\project\Whisper-WebUI\venv\lib\site-packages\gradio\queueing.py", line 495, in call_prediction
output = await route_utils.call_process_api(
File "D:\project\Whisper-WebUI\venv\lib\site-packages\gradio\route_utils.py", line 232, in call_process_api
output = await app.get_blocks().process_api(
File "D:\project\Whisper-WebUI\venv\lib\site-packages\gradio\blocks.py", line 1561, in process_api
result = await self.call_function(
File "D:\project\Whisper-WebUI\venv\lib\site-packages\gradio\blocks.py", line 1179, in call_function
prediction = await anyio.to_thread.run_sync(
File "D:\project\Whisper-WebUI\venv\lib\site-packages\anyio\to_thread.py", line 56, in run_sync
return await get_async_backend().run_sync_in_worker_thread(
File "D:\project\Whisper-WebUI\venv\lib\site-packages\anyio_backends_asyncio.py", line 2144, in run_sync_in_worker_thread
return await future
File "D:\project\Whisper-WebUI\venv\lib\site-packages\anyio_backends_asyncio.py", line 851, in run
result = context.run(func, *args)
File "D:\project\Whisper-WebUI\venv\lib\site-packages\gradio\utils.py", line 678, in wrapper
response = f(*args, **kwargs)
File "D:\project\Whisper-WebUI\modules\faster_whisper_inference.py", line 128, in transcribe_file
self.remove_input_files([fileobj.name for fileobj in fileobjs])
TypeError: 'NoneType' object is not iterable

Hi, sorry for the late response.
This issue seems to be the same with #77, if it only happens when you upload a huge file.
I guess this is related to how gradio caches files, but this is hard to reproduce because it seems to be directly related to PC performance.


add the css private filters

CLA is valid!

thanks @neraliu. reviewed out-of-band. closing this PR for further improvement.


image does not appear to support vendoring

I am using the app engine flex environment.
When I deploy, the cloud build fails:
Step 3/3 : RUN go-wrapper install -tags appenginevm
---> Running in e3aebcd0fd0e
exec go install -v -tags appenginevm
main.go:10:2: cannot find package "github.com/gorilla/mux" in any of:
/usr/local/go/src/github.com/gorilla/mux (from $GOROOT)
/go/src/github.com/gorilla/mux (from $GOPATH)
/go/src/app/_gopath/src/github.com/gorilla/mux
The command '/bin/sh -c go-wrapper install -tags appenginevm' returned a non-zero code: 1
ERROR
ERROR: build step "gcr.io/cloud-builders/docker@sha256:c99ef71791f407f8d2deaf782feceb00f4c5b59d0e8f7e50160acf9dd638d6failed: exit status 1

I checked the archive used to build the container. The code in question is in:
_gopath/src/github.com/btc/apartment-service/vendor/github.com/gorilla/mux
apartment-service (master) λ. gcloud  version                                                                                2
Google Cloud SDK 179.0.0
app-engine-go
app-engine-python 1.9.62
beta 2017.09.15
bq 2.0.27
core 2017.11.06
gcloud
gsutil 4.28
kubectl

Can you try the beta build pipeline?  The latest beta build pipeline should be able to handle vendor and internal directories.
See announcement for what's different with this beta build pipeline --
https://groups.google.com/forum/#!msg/google-appengine-go/cG_JAAX73Zg/27wXKI7aBQAJ
I'd recommend using latest gcloud version 179.0.0 as it does contain the support for vendor/internal directories.
Do let me know if you run into other issues.


[WIP] Better ESLint config

Lint the entire codebase instead of just src and tests.
Rely on ESLint's --fix to adjust code style of .js files (.vue files do not work with --fix, so still need to be adjusted manually)
Add .eslintrc files for some subdirectories directories, so that ESLint better understands their context and will not unnecessarily display errors in text editors with ESLint integration.

@yyx990803 This is still a work in progress, but I'd love to hear what you think about this general direction?

I'm not sure - feels clunky to have so many .eslintrc lying around. Although I don't have a better idea at this moment - will take a look later.

My biggest problem with it is that most of those .eslintrcs obliterate the project's main linting rules with "root": true. I'd love a linting-package-agnostic way of disabling entire classes of rules, with something like this:
"parserOptions": {
  "ecmaVersion": 5
}

But it seems to have no effect. 😞

The most significant pain for AirBnb users has been resolved with the addition of .eslintignore, so closing.


Added Clock Loader

Fixes Issue🛠

Closes #191
Description👨💻

Type of change📄

[] New feature (non-breaking change which adds functionality)

Added a clock Loader

How this has been tested✅

Checklist✅

[] My code follows the style guidelines of this project
[] I have performed a self-review of my own code
[] I have commented my code, particularly in hard-to-understand areas
[] I have added demonstration in the form of GIF/video file
[] I am an Open Source Contributor

Screenshots/GIF📷

Resolve the conflicts pls @Dhairya1Gupta

Resolve the conflicts pls @Dhairya1Gupta

Can You please specify the issue? @Rakesh9100

Pull the latest changes from the original repo to your local @Dhairya1Gupta


[chore]: Consider more open source friendly license

Summary
This source code snapshot currently uses the GPL3.0 license, which has a reputation for making projects harder to modify and reuse, which stifles open source collaboration.
Consider alternatives such as CC0, which is a precedent set by government consultancies like 18F, as seen here
Acceptance Criteria

Re-evaluate choice of license and potential ramifications
If desired (and approved by the relevant legal parties), update LICENSE.md to use the updated license policy

Resources

https://www.gnu.org/licenses/gpl-3.0.en.html
https://creativecommons.org/share-your-work/public-domain/cc0/
https://github.com/18F/open-source-policy/blob/master/LICENSE.md

Closed via 690aa3baad3a9f01ce2c6fbdd79ab707986a4a29


[Monitoring V2] Add pushprox for kubelet and node-exporter

Raising RFE for this as per the discussion in https://github.com/rancher/docs/issues/2493#issuecomment-790963731.
Node-exporter runs on the hostNetwork by default so we will need a pushprox to avoid opening ports to all nodes.  Kubelet is also monitored so we need a pushprox for that one.
gz#15946

Needs a UI issue attached to it to expose these options on the UI.

@aiyengar2 @gaktive @nwmac Do we need this UI issue to be fixed for this issue ? I see the UI issue is in 2.6.x milestone.

@aiyengar2 @gaktive @nwmac Do we need this UI issue to be fixed for this issue ? I see the UI issue is in 2.6.x milestone.

Nope, the way the push-prox exporters are structured they are optional extras for a hardened environment.  I don't think we need any additional UI elements.  I'll close out the issue

Tested on rancher/rancher:master-head e83ac8c with rancher-monitoring-100.0.0+up16.6.0 deployed on custom RKE2 cluster with k8s v1.21.2+rke2r1 and on RKE1 with k8s v1.20.7-rancher1-1
chart repo commit: 375fdb1a74e2bb1418e8d03d7831c76c679883a7
prometheus-node-exporter

pushproxy is used by default
I see that for scraping following metrics a pushprox-client is used - the output was taken from one of the rancher-monitoring-prometheus-node-exporter* pod processes:

pushprox-client --fqdn=redacted_ip --proxy-url=http://pushprox-kube-scheduler-proxy.cattle-monitoring-system.svc:8080 --metrics-addr=:10012 --allow-port=10251 --use-localhost
pushprox-client --fqdn=redacted_ip --proxy-url=http://pushprox-kube-proxy-proxy.cattle-monitoring-system.svc:8080 --metrics-addr=:10013 --allow-port=10249 --use-localhost
pushprox-client --fqdn=redacted_ip --proxy-url=http://pushprox-kube-controller-manager-proxy.cattle-monitoring-system.svc:8080 --metrics-addr=:10011 --allow-port=10252 --use-localhost
pushprox-client --fqdn=redacted_ip --proxy-url=http://pushprox-kube-etcd-proxy.cattle-monitoring-system.svc:8080 --metrics-addr=:10014 --allow-port=2381 --use-localhost

corresponding pushprox-kube-*-proxy* pods are running
all the metrics above are healthy (and listening on public ip of the node over endpoint) in Prometheus Targets view

kubelet

pushproxy must be enabled first for kubelet eg. by setting hardenedKubelet.enabled: true in values (otherwise it scrapes the metrics directly from kubelet container over hostNetwork which has similar result - both are on public ip)
then the pods pushproxy-kubelet-client* (DS)  and pushprox-kubelet-proxy-* (1 RS) are deployed
this is pushprox-client process taken from one of the pushprox-kubelet-client*` pod:

pushprox-client --fqdn=redacted_ip --proxy-url=http://pushprox-kubelet-proxy.cattle-monitoring-system.svc:8080 --metrics-addr=:10015 --allow-port=10250 --use-localhost --insecure-skip-verify --token-path=/var/run/se
crets/kubernetes.io/serviceaccount/token

The metrics from kubelet are healthy in Prometheus Targets view

This is example of the metrics targets (kubelet and kube-scheduler form node-exporter) with pushprox labels:

I'd say it works as expected. Close.


Drag n drop bugs, FireFox and IE

In FireFox there is an error in syntheticDataTransferFactory, because the arrays files and types can be null instead of zero length.
In IE there is an error when dragging items from outside the browser, because IE forbids access to effectAllowed in this case.
I have a quick PR that prevents both of these errors.
I also wanted to discussion the possibility of changing the events, by changing all of the SyntheticEvent classes to each be a simple proxy that wraps an instance if JsObject, instead of copying all of the values from the object during construction.  This was mentioned in #49 as a possible performance improvement, and I think it could improve the code as well.  I am curious if anyone else would see any drawbacks or problems with this idea.

See #62


OptionPickerFormItem with UISearchBar

You could put a search bar in OptionPickerFormItem . I think it would be interesting. ps: I tried to put but failed in all attempts .

How do you think the api should be like for this?
Can't promise anything.

So, any chance for this feature? Can we add Search Bar nowadays? @neoneye

So, any chance for this feature? Can we add Search Bar nowadays? @neoneye

I'm no expert in iOS' search controls. I have coded it several times, and I think Apple's api is messy in this area. So it's tricky making a solution that encapsulates this in a future proof way.
If you have ideas for how it ideally should work, then please share, or submit a pull requests.

I'm no expert in iOS' search controls. I have coded it several times, and I think Apple's api is messy in this area. So it's tricky making a solution that encapsulates this in a future proof way.
If you have ideas for how it ideally should work, then please share, or submit a pull requests.


package org.python does not exist

Want this to work as I much prefer working in Python, but I realize this is still all in alpha
Anyway, working through the setup and tutorial
(note I already tried downgrading all the toga packages to various 'dev?' versions)
I am on MacOSX, I have installed Android Studio and Android SDK No. 15
I installed jython via the executable jar downloaded from jython.org
I have set these env variables:
ANDROID_HOME=/Users/foo/Library/Android/sdk
ANDROID_SDK_HOME=/Users/foo/Library/Android/sdk
CLASSPATH=:/Users/foo/jython2.7.0/javalib/
JYTHON_HOME=/Users/foo/jython2.7.0/
JYTHON_PATH=/Users/foo/jython2.7.0/bin
JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk1.8.0_181.jdk/Contents/Home
PATH=/Users/foo/src/pybee/tutorial/venv/bin:/Library/Frameworks/Python.framework/Versions/3.5/bin:/Library/Frameworks/Python.framework/Versions/3.7/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Users/foo/Library/Android/sdk/tools:/Users/foo/Library/Android/sdk/platform-tools:/Users/foo/Library/Android/sdk/tools/bin:/Users/foo/jython2.7.0/bin:/Users/foo/Library/Android/sdk/platform-tools/

Here is the status of pip freeze:
arrow==0.12.1
binaryornot==0.4.4
boto3==1.8.7
botocore==1.11.7
briefcase==0.2.6
certifi==2018.8.24
chardet==3.0.4
click==6.7
colosseum==0.1.6
cookiecutter==1.6.0
Django==1.10.6
django-environ==0.4.1
docutils==0.14
future==0.16.0
idna==2.7
Jinja2==2.10
jinja2-time==0.2.0
jmespath==0.9.3
MarkupSafe==1.0
poyo==0.4.1
python-dateutil==2.7.3
requests==2.19.1
rubicon-objc==0.3.0
s3transfer==0.1.13
six==1.11.0
toga==0.3.0.dev9
toga-cocoa==0.3.0.dev9
toga-core==0.3.0.dev9
toga-django==0.3.0.dev9
travertino==0.1.2
urllib3==1.23
voc==0.1.5
whichcraft==0.4.1

Running:
python setup.py android -s

gives:
python setup.py android -s
running android

 * Updating user code...
 * Installing requirements...
No requirements.
 * Installing platform requirements...
Collecting toga-android==0.3.0.dev9
  Using cached https://files.pythonhosted.org/packages/34/7d/444f07d35d0f0c9b4e394003548b9100b8cac937c44406646f31b9dd30de/toga_android-0.3.0.dev9-py3-none-any.whl
Collecting toga-core==0.3.0.dev9 (from toga-android==0.3.0.dev9)
  Using cached https://files.pythonhosted.org/packages/50/a1/ebc3b57145b03b644cc53c2693838eb3afafdb686eec2dffd90cf3548d09/toga_core-0.3.0.dev9-py3-none-any.whl
Collecting travertino>=0.1.0 (from toga-core==0.3.0.dev9->toga-android==0.3.0.dev9)
  Using cached https://files.pythonhosted.org/packages/56/3f/f03efe63c2bdc72763ac39777c9ebbab98605ced5c74aefe48b4fa0abb4d/travertino-0.1.2-py3-none-any.whl
Installing collected packages: travertino, toga-core, toga-android
Successfully installed toga-android-0.3.0.dev9 toga-core-0.3.0.dev9 travertino-0.1.2
 * Installing project code...
Processing /Users/foo/src/pybee/tutorial/foo
Building wheels for collected packages: foo
  Running setup.py bdist_wheel for foo ... done
  Stored in directory: /private/var/folders/1c/1qj0qxz12hsd9vv12cwqt52c0000gn/T/pip-ephem-wheel-cache-c2zw19d_/wheels/65/6d/ba/b02dea699a7a4bd5291fd0a9aa06d2cfa4cf374357282bc1b8
Successfully built foo
Installing collected packages: foo
Successfully installed foo-0.0.1
 * No icons defined - using default...
 * No splash screen defined...

Installation complete.

Starting Foo
The Task.leftShift(Closure) method has been deprecated and is scheduled to be removed in Gradle 5.0. Please use Task.doLast(Action) instead.
        at build_31u9w8uw06fomdcszurr6ar53.run(/Users/foo/src/pybee/tutorial/foo/android/build.gradle:11)
The JavaCompile.setDependencyCacheDir() method has been deprecated and is scheduled to be removed in Gradle 4.0.
The TaskInputs.source(Object) method has been deprecated and is scheduled to be removed in Gradle 4.0. Please use TaskInputs.file(Object).skipWhenEmpty() instead.
:preBuild UP-TO-DATE
:preDebugBuild UP-TO-DATE
:checkDebugManifest
:preReleaseBuild UP-TO-DATE
:prepareComAndroidSupportAnimatedVectorDrawable2511Library UP-TO-DATE
:prepareComAndroidSupportAppcompatV72511Library UP-TO-DATE
:prepareComAndroidSupportSupportCompat2511Library UP-TO-DATE
:prepareComAndroidSupportSupportCoreUi2511Library UP-TO-DATE
:prepareComAndroidSupportSupportCoreUtils2511Library UP-TO-DATE
:prepareComAndroidSupportSupportFragment2511Library UP-TO-DATE
:prepareComAndroidSupportSupportMediaCompat2511Library UP-TO-DATE
:prepareComAndroidSupportSupportV42511Library UP-TO-DATE
:prepareComAndroidSupportSupportVectorDrawable2511Library UP-TO-DATE
:prepareDebugDependencies
:compileDebugAidl UP-TO-DATE
:compileDebugRenderscript UP-TO-DATE
:generateDebugBuildConfig UP-TO-DATE
:generateDebugResValues UP-TO-DATE
:generateDebugResources UP-TO-DATE
:mergeDebugResources UP-TO-DATE
:processDebugManifest UP-TO-DATE
:processDebugResources UP-TO-DATE
:generateDebugSources UP-TO-DATE
:incrementalDebugJavaCompilationSafeguard UP-TO-DATE
:compileDebugJavaWithJavac
:compileDebugJavaWithJavac - is not incremental (e.g. outputs have changed, no previous execution, etc.).
/Users/foo/src/pybee/tutorial/foo/android/src/android/PythonActivity.java:12: error: package org.python does not exist
    static org.python.Object _listener;
                     ^
/Users/foo/src/pybee/tutorial/foo/android/src/android/PythonActivity.java:19: error: package org.python does not exist
    static public android.app.Activity setListener(org.python.Object listener) {
                                                             ^
/Users/foo/src/pybee/tutorial/foo/android/src/android/PythonActivity.java:91: error: package org.python does not exist
                org.python.Object [] args,
                          ^
/Users/foo/src/pybee/tutorial/foo/android/src/android/PythonActivity.java:92: error: package org.python does not exist
                java.util.Map<java.lang.String, org.python.Object> kwargs
                                                          ^
/Users/foo/src/pybee/tutorial/foo/android/src/android/PythonActivity.java:55: error: package org.python.java does not exist
                _listener.__setattr_null("_impl", new org.python.java.Object(this));
                                                                     ^
/Users/foo/src/pybee/tutorial/foo/android/src/android/PythonActivity.java:74: error: package org.python.exceptions does not exist
                throw (org.python.exceptions.BaseException) e.getCause();
                                            ^
/Users/foo/src/pybee/tutorial/foo/android/src/android/PythonActivity.java:80: error: package org.python.exceptions does not exist
                throw new org.python.exceptions.RuntimeError(message);
                                               ^
/Users/foo/src/pybee/tutorial/foo/android/src/android/PythonActivity.java:100: error: package org.python does not exist
                org.python.Object method = _listener.__getattribute_null(method_name);
                          ^
/Users/foo/src/pybee/tutorial/foo/android/src/android/PythonActivity.java:102: error: package org.python does not exist
                    ((org.python.Callable) method).invoke(args, kwargs);
                                ^
Note: /Users/foo/src/pybee/tutorial/foo/android/src/android/PythonActivity.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
9 errors
:compileDebugJavaWithJavac FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':compileDebugJavaWithJavac'.
> Compilation failed; see the compiler error output for details.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

Total time: 1.189 secs
    $ adb logcat Python:* *:E

App started.

Thanks for clues and Godspeed

Got exactly the same problem, did u solve this?


preprocess: parallelize get_all_host_reads rule

Since the get_all_host_reads rule in preprocess.smk can be a somewhat long running rule, we could try splitting it up like this:

Run the samtools view and bamToFastq commands as a rule that is parallelized over input bams, rather than with the for loop
Run the cat ... | pigz ... step as a downstream rule that is parallelized over R1,R2

Thanks for finding this!  resolved


Cannot compile polybar

I tried to compile polibar via setup.py.
After install all missing it fails on building:
http://pastebin.com/rwRuW5R9
Some info:
Debian jessie
Used Clang v3.5.0-10 to compile.

I see that you are trying to compile old code so update the code base and try again

Tested, same error.
I downloaded via git clone:
git clone https://github.com/jaagr/polybar/
Then cd polybar/, sudo ./build.sg

what's the output of
$ git describe --tags

3.0.4

While in the build folder, try running
$ cmake -DWITH_XRANDR_MONITORS=0 ..
$ make

I edited build.sh because i need all these parameters (to use clang else gcc).

Debian clang version 3.5.0-10 (tags/RELEASE_350/final) (based on LLVM 3.5.0) Target: x86_64-pc-linux-gnu

Are there any more recent versions available for your distro? If so, I'd recommend upgrading and it should work fine.

Everything is updated.
Debian GNU/Linux 8.7 (jessie)

I updated gcc to latest version but I cannot compile:
$ cmake ..
-- The C compiler identification is GNU 6.3.0
-- The CXX compiler identification is GNU 4.9.2
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- No build type specified; using RelWithDebInfo
CMake Error at cmake/common/utils.cmake:9 (message):
  Compiler not supported (Requires clang-3.4+ or gcc-5.1+)
Call Stack (most recent call first):
  cmake/01-core.cmake:47 (message_colored)
  CMakeLists.txt:15 (include)

-- Configuring incomplete, errors occurred!
See also "/home/adp/.i3/polybar/build/CMakeFiles/CMakeOutput.log".

Clang version: 3.5.0-10
Gcc version: 6.3.0

The CXX compiler identification is GNU 4.9.2
Try to recreate the build folder

Updated cxx too.
Same error: http://pastebin.com/jJbE3qiV

error: debug information for auto is not yet supported

This looks like a clang error. Are you sure gcc is being used?

I edited build.sh removing clang support. (Forcing gcc use)
Now everything works :)
Conclusion:

Works only with gcc
Swap order of gcc with clang (Try to use gcc first)

Clang works fine but you were using an old version. I use it myself as I prefer it to gcc

@AlessioDP Can you please share your build.sh with gcc?

@QiangF I just added:
cxx="g++"
cc="gcc"

before cmake (line 66)

have the same problem...
with:
/tmp/polybar/build$ clang-3.8 --version
clang version 3.8.0-2ubuntu3~trusty5 (tags/RELEASE_380/final)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /usr/bin

and
/usr/bin/gcc-5 --version
gcc-5 (Ubuntu 5.5.0-12ubuntu1~14.04) 5.5.0 20171010
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

@fifdick Does compiling with gcc not work? If not, please open a new issue describing this issue and include the build log. Also consider upgrading your distro, 14.04 is end-of-life next april.


Custom integration 'monitor_docker' calls async_write_ha_state

Just installed 2024.5 and logs say:

Detected that custom integration 'monitor_docker' calls async_write_ha_state from a thread at custom_components/monitor_docker/switch.py, line 227: self.async_schedule_update_ha_state().
Please report it to the author of the 'monitor_docker' custom integration.

So.... Here I am! :-)

Yep, the same ova here:
[Docker] esphome-updater: Container not available anymore (3) (Detected that custom integration 'monitor_docker' calls async_write_ha_state from a thread at custom_components/monitor_docker/switch.py, line 227: self.async_schedule_update_ha_state(). Please report it to the author of the 'monitor_docker' custom integration.)
Traceback (most recent call last):
  File "/config/custom_components/monitor_docker/helpers.py", line 757, in _run
    self._notify()
  File "/config/custom_components/monitor_docker/helpers.py", line 1310, in _notify
    callback()
  File "/config/custom_components/monitor_docker/switch.py", line 227, in event_callback
    self.async_schedule_update_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1258, in async_schedule_update_ha_state
    self.async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1008, in async_write_ha_state
    self.hass.verify_event_loop_thread("async_write_ha_state")
  File "/usr/src/homeassistant/homeassistant/core.py", line 440, in verify_event_loop_thread
    frame.report(
  File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 162, in report
    _report_integration(what, integration_frame, level, error_if_integration)
  File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 203, in _report_integration
    raise RuntimeError(
RuntimeError: Detected that custom integration 'monitor_docker' calls async_write_ha_state from a thread at custom_components/monitor_docker/switch.py, line 227: self.async_schedule_update_ha_state(). Please report it to the author of the 'monitor_docker' custom integration.

HA 2024.5.2.

@dapuzz I changed the repo to master as mentioned here:
https://github.com/ualex73/monitor_docker/issues/144#issuecomment-2092560979
...and it's works!

I released the master as v1.15. I will close this ticket, please reopen if you find another issue.


Plate Settler spacer pipe specification

@monroews I cannot find documentation on the plate settler spacer pipe specification. In this [file] (https://docs.google.com/spreadsheets/d/1UPWzB1XgeCndprMN8Inm6SqEkhQoMA-GpteLmXRBW5Y/edit#gid=1608333328), on the sed tank sheet, Module_SDRSpacer is reported to be 17 but I am unsure where this comes from.

There are relatively few different SDRs available for small pipe sizes. I'd expect that for the plate settlers we use the thinnest wall pipes that is commercially available.


Document not up to date for .NET 5/6

There is no ApplicationDeployment class available in .NET 5/6.

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

ID: b4c30cb0-8e88-4277-bfb9-e32d85538ce2
Version Independent ID: 84b1bcd6-9554-b545-134f-ad66fb66e114
Content: Automatic app updates using ClickOnce deployment API - Visual Studio (Windows)
Content Source: docs/deployment/how-to-check-for-application-updates-programmatically-using-the-clickonce-deployment-api.md
Product: visual-studio-windows
Technology: vs-ide-deployment
GitHub Login: @Mikejo5000
Microsoft Alias: mikejo

@simmotech -- Simon, thank you for your feedback.  Please consider these resources:

Visual Studio on Microsoft Q&A
Visual Studio MSDN Forum
Stack Overflow
Reddit

@Mikejo5000 -- Mike, please look into this issue.

@simmotech Thanks for pointing this out. I've updated the articles referencing ApplicationDeployment class with a note. More updates coming with .NET 7.


Start of the app shows pending state for the transaction

When the app is started all the transactions are rendered with the pending state and flips to non-pending after a while.

I found out the issue, the isPending state is evaluated for a given BlockHeight but this value is optional and when there is no one provided the fallback is pending. As a solution, determination of isPending should never allow optional height for the input.


a PR to validate that pr's between non-master branches still get the validation build action run on them

a PR to validate that pr's between non-master branches still get the validation build action run on them
will validate and close without completing, and will delete this branch after testing is complete.

the PR did run the validation build, like it should have.


Question please

Please how can you set up with Azure ASAP.Also can I use additional tools with it and will it work like the pre-installed tools.

Just tried to get it working with Azure to no avail. It's a very finicky and lengthy process.


MTL-2296: we can't use >= 2.5.0 on CSM

Summary and Scope

Fixes: MTL-2296

Issue Type

Bugfix Pull Request

Prerequisites

[ ] I have included documentation in my PR (or it is not required)
[ ] I have tested this by building an image using this branch HEAD, or this is does not pertain to the node-images pipeline.
[ ] I tested this on internal system or this pertains to the node-images pipeline (if yes and not build related, please include results or a description of the test)
[ ] I tested this on a vshasta system or this pertains to the node-images pipeline (if yes and not build related, please include results or a description of the test)

Idempotency

Risks and Mitigations

/backport main


Sync the change rhods-2.4 with fixes.

Major changes: https://github.com/opendatahub-io/notebooks/pull/332
Related-to:
https://github.com/opendatahub-io/notebooks/issues/331
https://github.com/opendatahub-io/notebooks/issues/301
https://github.com/opendatahub-io/notebooks/issues/327
https://github.com/opendatahub-io/notebooks/pull/325
JIRA: https://issues.redhat.com/browse/RHODS-12834

Didnt do the cherry-pick explicity, as all the source code seems like repo based changes
and doesn't have impact on the content.
Merging this in to get the RHODS 2.4 ready.


Fixes and QoL Additions

Adding fastqsanger to the list of fastq regex patterns.

This is needed as there were cases where fastqsanger wasn't being considered as a fastq file, while lead to kmer_cov_freq not being considered.

Adding average coverage value column to the subtyping result.

Requested so that a user can check coverage in the results.

Fixing order of parameters for blast method.

Incorrect order of parameters was causing the blast method to fail.

Further questions:

Do you think it's a good idea to have coverage present in the subtyping result? Or would you rather this be a new column in the DataFrame for match_results?

We could peek at the first X bytes of the file if the file extension is unknown (e.g. is the first non-whitespace character an > then it's fasta, if the first character is @ then it's fastq, if the filename matches .*\.gz$ read the first X uncompressed bytes of the file to determine if it's fasta or fastq). Maybe instead of a regex we could just have a dict of known file extensions to their respective parsing functions or an enum.

In addition to mean coverage, we could also report the median coverage from the frequency of all kmers. I'm wondering if it would be worthwhile to report separate coverage values for when you observe mixed subtyping results. For now it might be best to just show one for the negative tiles.

I think most people would want to see coverage in their results, but definitely in a separate column. I think it might be a good idea to add it to all reports even the tech report since it is valuable QA/QC info on it's own.

@peterk87 I also added a new flag which adds the ability to output JSON representations of the results files. This is needed for when we populate the tech results table on IRIDA.

@peterk87
When you say take the average of the negative tiles, why is this the case?

Does the coverage of the negative tiles show how plausible the results are in terms of the higher the coverage of negative tiles, the more certainty you have with the positive hits?

If this is the case, should we just show the median frequency of the negative tiles in the coverage column?

I spoke with Marisa and Genevieve, and they would like to see that coverage for all tiles is present in

results.tab
tech_results.tab

Then they would like to see a warning when overall tile coverage is < a given value. (Default 20)


fix: Revert the use of SET operation when updating Money Requests

Details
This is a straight revert of https://github.com/Expensify/App/pull/31340 with a fix for https://github.com/Expensify/App/issues/33103
Fixed Issues

$ https://github.com/Expensify/App/issues/33098
PROPOSAL: https://github.com/Expensify/App/issues/33098#issuecomment-1858118738
Tests

Same as QA
Offline tests

Same as QA
QA Steps

Go offline
Navigate to the created expense details page (or create one)
Click on the date
Change it once

[ ] Verify the date is changed, and a proper message is added, e.g. changed the date to 2023-12-14 (previously 2023-12-15)

Click on the date again
Change it for the second time

[ ] Verify the date is changed again with a corresponding message

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome
https://github.com/Expensify/App/assets/12595293/c8e3b725-93bc-45aa-b1e1-3e7554b00175

iOS: Native
https://github.com/Expensify/App/assets/12595293/d7a90468-43c0-4153-95af-9d08061b61fc

iOS: mWeb Safari
https://github.com/Expensify/App/assets/12595293/f06bc29b-5f32-48dd-8097-84b38eed3a4f

MacOS: Chrome / Safari
https://github.com/Expensify/App/assets/12595293/e7071d55-e573-44e2-9399-e99cf9f7d31d

MacOS: Desktop
https://github.com/Expensify/App/assets/12595293/41ff21df-8501-46f4-a505-536e9e373079

@situchan I'm having trouble running my native Android build right now (couldn't fix it for 4 hours already). I would appreciate it if you could attach a recording from your side considering the issue is urgent 🙏
All the other platforms are attached already.

@situchan thanks, done ✔

Reviewer Checklist

[x] I have verified the author checklist is complete (all boxes are checked off).
[x] I verified the correct issue is linked in the ### Fixed Issues section above
[x] I verified testing steps are clear and they cover the changes made in this PR

[x] I verified the steps for local testing are in the Tests section
[x] I verified the steps for Staging and/or Production testing are in the QA steps section
[x] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[x] I checked that screenshots or videos are included for tests on all platforms
[x] I included screenshots or videos for tests on all platforms
[x] I verified tests pass on all platforms & I tested again on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[x] I verified proper code patterns were followed (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I verified that this PR follows the guidelines as stated in the Review Guidelines
[x] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native
https://github.com/Expensify/App/assets/108292595/3fe25ec5-0386-46ba-bf47-784fc5e4b39e

Android: mWeb Chrome
https://github.com/Expensify/App/assets/108292595/c75b28df-5e54-4245-b178-9ef2bcc350eb

iOS: Native
https://github.com/Expensify/App/assets/108292595/a210d5ce-0044-4e8c-b561-2a3298ea0625

iOS: mWeb Safari
https://github.com/Expensify/App/assets/108292595/27241892-a2c2-4a62-83fb-6369bf8d7613

MacOS: Chrome / Safari
https://github.com/Expensify/App/assets/108292595/a210d5ce-0044-4e8c-b561-2a3298ea0625

MacOS: Desktop
https://github.com/Expensify/App/assets/108292595/236a83f5-9b98-4efb-a95d-66497c92ee84

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Cherry-picked to staging by https://github.com/Julesssss in version: 1.4.13-7 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Deployed to production by https://github.com/jasperhuangg in version: 1.4.13-8 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Updating icon path case sensitivity

Haha, oops - I thought I was creating this PR in my own fork, but will still leave it here for you. Fantastic tool, thanks for making it public!


feat: add orphan Type to IJSONApplication to save types

This is a small PR.
This PR modify IJsonApplication types.
Now IJsonApplication keeps the original Type which is passed to typia.json.application.
This is useful if we make third-party library using typia(ex. https://github.com/ryoppippi/typiautil/blob/ab71cf9cbb73c751474136c6698a3ea23eb8f4b1/openai/mod.ts#L17)
Before submitting a Pull Request, please test your code.

If you created a new feature, then create the unit test function, too.

```bash
# COMPILE
npm run build

# RE-WRITE TEST PROGRAMS IF REQUIRED
npm run test:template

# BUILD TEST PROGRAM
npm run build:test

# DO TEST
npm run test
```

Learn more about the [CONTRIBUTING](CONTRIBUTING.md)

Hmm, I'll check why test fails

Thanks. I'll check later

@samchon
I faced a lot of issues when I run npm run generate.

Ah, I'm sorry. Run npm run template command instead.

@samchon
OK! thanks!

Hmm, you can remove it if you want


Error occurred when press enter on an empty list

Step for reproducing:
1.enter long string (no autocomplete values);
2.press the enter key;
result: error in console
@

i am also looking for a way to handle this, or an option to load a url at this point

For anyone reading this, I had the same problem: I forked the repo and changed line vue-autocomplete.vue:244 into this this.json.length ? this.selectList(this.json[this.focusList]) : e.target.form.submit(). This was sufficient for my use case, but otherwise you could hook it up to another method.

Another possible way to work around this is to attach a listener to the input and suppress the enter key in appropriate circumstances.
  mounted() {
    const input = this.$refs.autocomplete.$refs.input
    input.addEventListener('keydown', this.suppressEnter, false)
  },
  methods: {
    suppressEnter(e) {
      // Enter when there are no results breaks things.  This is a bug in the plugin, but this works around it.
      if (e.which === 13 && this.results.length === 0) {
        e.preventDefault()
        return false
      }
    },


PositionPlugin: calculate center from extent when not available

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

3 of 3 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.01%) to 99.669%

Totals

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

Covered Lines:
13499

Relevant Lines:
13501

💛  - Coveralls


failed to parse a pgn with 'LineBuffer underflow'

xx1507203.pgn.gz
via fastpopular:
~/chess/vondele/fastpopular/fastpopular --file ./xx1507203.pgn --maxPlies 60 --stopEarly --countStopEarly 6 --minCount 2 --saveCount --omitMoveCounter --cdb -o test.epd
Found 1 .pgn(.gz) files, creating 1 chunks for processing.
Error when parsing: ./xx1507203.pgn
LineBuffer underflow
Processed 1 files
Retained 0 positions from 0 unique visited in 0 games.
Total time for processing: 0.003 s

Not yet clear what is causing this, I suspect the header, since fastpopular found no moves.

Ah, I guess I see it:
[Variation "Abbazia defence (classical defence, modern defence[!])"]
There is a [!] in the Variation string. Probably causing havoc in finding the closing ']'

yeah, all failed pgns contain that string.

Or others...
[WhiteTeam "FischerâEuro[]s Catch"]
[White "H[+]hler, P."]
[Black "Kri[#]anoviæ, Zvonko"]
[White "R[+]ssler, E."]
[BlackTeam "Club dâEuro[]escacs Platja d'Aro"]
...

I guess there could be even unmatched [] so probably need to look for the end of the string?


Remove FileWriter

It would be great to move FileWriter into its own or another module (concerto-tools?). It depends on mkdirp which drags in minimist.

Can I work on this to move FileWriter to codegen in concerto-tools?

I'm unclear whether we should remove FileWriter now that we have code in concerto-core to resolve external models and drop them to disk, unless we feel like moving that functionality entirely in a different place e.g., concerto-cli.

FileWriter is still used in PlantUMLGenerator which is used in parsejs.js See #69.

Addressed as part of #122 pending review


ARABIC END OF AYAH (U+06DD) followed by a number ۝١ is rendered incorrectly

Description
Entering the end of ayah symbol followed by a number, should encircle the number, .e.g.
U+06DDU+0661
should be rendered as
۝١
It works correctly in  LibreOffice Writer  using Noto Sans Arabic font. This failed using typst
Reproduction URL
https://typst.app/project/pFeXLY0VVrRyfu5vU24Say
Operating system
Linux
Typst version

[X] I am using the latest version of Typst

That's how it looks to me, is that not how it's supposed to look?
At least it looks pretty similar in the browser:

I'm pretty sure that's a font issue. Here's what I get using the font "Segoe UI" in Word:

And here the result when I change it to Noto Sans Arabic:

I just tried it in Libre Office Writer, too, and got the exact same result.

@LaurenzV what you have with "Segoe UI" in Word is the correct rendering. May be your "Noto Sans Arabic" font is not updated the latest?

Could you show a picture of how it looks for you?

Not sure then, would have to look into it. But in any case, if something is wrong then it's probably a bug in rustybuzz, because that's the library we use for shaping.

Umm! This is getting nasy then. With rustybuzz announcing it "is effectively dead". What's the easiest way to test the library directly?

I'll look into it when I find the time to do so.

Doesn't rustybuzz handle the shaping part only? I am not sure about the rendering part. The shape function output matches that of harfbuzz as can be seen here:
$ ./shape --font-file NotoSansArabic-Regular.ttf --text "۝١"
uni0661.small=1@538,80+0|uni06DD=0+1370

$ hb-shape NotoSansArabic-Regular.ttf "۝١"
[uni0661.small=1@538,80+0|uni06DD=0+1370]

It only handles the shaping part.
But the rendering with harfbuzz looks wrong for me too (even though different to what appears in Typst):
hb-view NotoSansArabic-Regular.ttf "۝١"

So not sure, either a harfbuzz issue or something is wrong with the font (or something is wrong with my computer).

Although I don't speak Arabic.

May be I should explain the problem in a simplified way and remove any part that requires any Arabic knowledge. In Unicode terms this is called "subtending marks". In this case, the first character is just a circle and the second is the number one. The circle is empty but when followed by a number, the fonts and the shaping engine has their logic to substitute the number one with a smaller version that fits inside the circle and move it to fit perfectly. Of course not all the fonts support the full range of Arabic features, but as you figured out "Segoe UI" supports subtending, and you can do your tests with it.
That's said, assuming your version of noto fonts are current, try the --direction option so as to prevent incorrect auto-detection. Also, try other fonts like Amiri, Calibri, Traditional Arabic, Arabic Typesetting. Whichever works for you is enough to compare. Let's even use the Latin number "1" instead of the Arabic one.
$ pacman -Q harfbuzz
harfbuzz 8.3.0-2
$ hb-info NotoSansArabic-Regular.ttf |rg Version
Version: Version 2.012; ttfautohint (v<IP_ADDRESS>-5d5b)
$ hb-view --direction=ltr NotoSansArabic-Regular.ttf -u 6dd,661

$ hb-view --direction=ltr NotoSansArabic-Regular.ttf -u 6dd,31

hb-view --direction=ltr Amiri-Regular.ttf -u 6dd,31

Let me know how it goes, and if you need any help we can ask the harfbuzz gurus for advice.

Okay, for some reason the font on Google Fonts was veeery outdated. 😅 Even though I downloaded a fresh copy... But downloading it directly from GitHub I can now reproduce it.
So yeah, maybe a rendering issue after all. But as I said, I don't know when I can investigate it, will probably take a while, since I'm also still relatively new in that area.

Yes, I understand. But after these findings, can you point to which library could be the cause and whether the upstream label is still correct?

Actually, nevermind, seems like it isn't a bug, for some reason Typst was just still loading an old Noto Arabic for me... So here is what I did:

Delete all local instances of Noto Sans Arabic. Verify that Typst isn't able to detect any instances of Noto Sans Arabic by invoking cargo run -- fonts

Download NotoSansArabic-Regular.otf from here: https://notofonts.github.io/

Put it in some folder on your PC.

Create the following file;

#set page(width: auto, height: auto, margin: 30pt)
#set text(size: 40pt, font: "Noto Sans Arabic")

۝١

Run it with cargo run -- c --font-path assets/inc_fonts  typst.typ typst.png.

Result:

Umm! I am using Arch Linux which already uses the latest version of noto fonts but I see now that the bug is fixed in the latest commits after the release. I am not sure which one but my current version of typst
> typst -V
typst 0.10.0 (70ca0d25)
typst compile noto.typ noto.png

whereas,
> ./typst -V
typst 0.10.0 (f5a2a9a9)
typst compile noto.typ noto.png

Anyway, I am glad that it's been fixed and thanks to you and whoever fixed it.

Just update the v

Just update the version of the font on typst.app before closing.

The web app has a different repository https://github.com/typst/webapp-issues/issues
It would be better if you created an issue there to update the font.


Fix TSLint warnings in msbot-connect-dispatch

Proposed Changes
Fix the following warnings in the file msbot-connect-dispatch.ts:

typedef
no-any
interface-name
quotemark
max-line-length
no-empty
prefer-const
one-line
curly
switch-default
switch-final-break
whitespace
newline-before-return
eofline

Testing
Travis will no longer report this issue.

Changes already merged into Microsoft/master


Flat values for log config

Using a yaml dict for the log config (and only the log config)
wasn't really useful, made a gratuitous special case, and made
passing log conf as environment variable much harder.

Coverage decreased (-0.3%) to 90.944% when pulling<PHONE_NUMBER>bda6fb52fcd76f7a5ef154d6c5b49e on flatlogs into 10f459eb940627a1c7b7232dda7914860bb1b821 on master.


tf.contrib.summary.scalar does not record anything outside of always_record_summaries in eager execution

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Colab
TensorFlow installed from (source or binary): Colab builtin
TensorFlow version (use command below): 1.14.0
Python version: 3.6.8
GCC/Compiler version (if compiling from source): [GCC 8.0.1 20180414 (experimental) [trunk revision 259383]]

Describe the current behavior
https://colab.research.google.com/drive/1c1SUEet_jCxvW8D_ZlmOCPJvutB3PhCD
This code does not record anything in eager execution mode.
writer = tf.contrib.summary.create_file_writer(os.path.join(logdir, 'contrib'))
with writer.as_default():
  for i in range(1000):
    if i % 10 == 0:
      tf.contrib.summary.scalar('sin', math.sin(2*math.pi/500), step=i+1)
writer.close()

Describe the expected behavior
tf.contrib.summary.scalar should save records even out side of always_record_summaries()  by default.
It's very unnatural that we need to call always_record_summaries or record_summaries_every_n_global_steps to save records in eager execution mode.
https://www.tensorflow.org/guide/eager#summaries_and_tensorboard
Code to reproduce the issue
https://colab.research.google.com/drive/1c1SUEet_jCxvW8D_ZlmOCPJvutB3PhCD

We're no longer making changes to the contrib summary API, but if you try the TF 2.0 tf.summary API, it should look similar to contrib, but doesn't require calling always_record_summaries() - summaries are on by default.


Implement a Standard Way to access Models

Issue description
To ensure a scalable and maintainable system, every model should have a standardized access method. Currently, the system needs to adapt three ways of accessing three models.
Expected Behavior
Models are accessed using the same request format each time, with a consistent header and body. The api_key and endpoint_url parameters are expected to be unique for each model.
Current Behavior
Currently, there are three different ways to call three models. Here's a list of functioning headers and body by models
Nachet-6seed:
headers = {
    "Content-Type": "application/json",
    "Authorization": ("Bearer " + endpoint_api_key),
}

body = {
    "input_data": {
        "columns": ["image"],
        "index": [0],
        "data": [image_bytes],
    }
}

Seed-detector:
headers = {
    "Content-Type": "application/json",
    "Authorization": ("Bearer " + endpoint_api_key),
    'azureml-model-deployment': 'seed-detector-1'
}

body = {
    "input_data": {
        "columns": ["image"],
        "index": [0],
        "data": [image_bytes],
    }
}

Swin:
headers = {
   "Content-Type": "application/json",
   "Authorization": ("Bearer " + api_key),
}

body = b64encode(image)

Additional Context
Issue 51 Implement Model Switching Functionality in Inference Request

@amirardalan9473 can you provide an explanation and link to documentation on how the app.py/score.py is selected and inserted for the model.
"standard way" should be standardized API
also needs discussion on what functionality and data format we want for that API


[nz-code-editor] Configure MonacoEnvironment before (first) load

What problem does this feature solve?
Since monaco-editor 0.22.0¹, the global monaco object is only defined if you add
window.MonacoEnvironment = { globalAPI: true };

It would be nice if ng-zorro had some hook to configure MonacoEnvironment (also for potential other use-cases) before monaco-editor is actually loaded. Also, the documentation for onLoad is now slightly incorrect/incomplete:

The hook invoked when the resource of monaco editor is loaded. At this moment and afterwards the global variable monaco is usable

¹ https://github.com/microsoft/monaco-editor/blob/main/CHANGELOG.md
What does the proposed API look like?
Extend NzConfig#codeEditor with either an object or a function to modify MonacoEnvironment.

@hullis @simplejason
"ng-zorro-antd": "^13.2.0",
Error: node_modules/ng-zorro-antd/core/config/config.d.ts:9:29 - error TS2307: Cannot find module 'monaco-editor' or its corresponding type declarations.

import { Environment } from 'monaco-editor';

@hullis @simplejason
"ng-zorro-antd": "^13.2.0",

Error: node_modules/ng-zorro-antd/core/config/config.d.ts:9:29 - error TS2307: Cannot find module 'monaco-editor' or its corresponding type declarations.

import { Environment } from 'monaco-editor';

Did you fix it? Same problem here

Hi @thekhegay. Have you installed the monaco-editor package? ng-zorro-antd does not list monaco-editor as a dependency for a reason.

I had to install monaco-editor to solve the problem idk why. I don't use it

I had to install monaco-editor to solve the problem idk why. I don't use it

For sorry that. The problem is on out side. We will fix it soon.

https://github.com/NG-ZORRO/ng-zorro-antd/blob/99f4141826489f81e78d27e1bcb754726dee29d5/components/core/config/config.ts#L11
@yangjunhan Should not import type declaration here. Forcing all users to install monaco editor.

@hullis any updates?

@hullis any updates?

This problem should have been fixed in our recent release.


[Equalizer] data-equalize-on medium is not default

How can we reproduce this bug?

Step one: Implement an equalizer row.
Step two: Add data attribute data-equalize-on

What did you expect to happen?
Since the default for data-equalize-on is medium I expect equalizer to not fire on small but wait for the medium breakpoint.
What happened instead?
Nothing changes. small continues to equalize.
Hack
Just as it is in the Basics example code data-equalize-on="medium" the value must be applied.

Test case:

CodePen with Foundation 6

Looks like there is a conflict of default settings.

If you add equalize-on-stack="false" it should do it. And we'll change the default setting to reflect that to reduce this confusion.

Done df70a3b`

Thanks. I discoverd I could use that approach as well. But I couldn't decide which was the better "mobile first" way of attacking the issue. Finally decided that in my case equalize-on-stack="false" looked like a mobile hack while data-equalize-on="medium" appeared more progressive.

For me, it is not working.
I set <div class="business-listing-outer-container" data-equalizer data-equalize-on="medium">
but on mobile still watching.


supposed sudo

supposed sudo as script gets stuck on ubuntu server 20.04 due to insufficient permissions

You generally wouldn't want to be using sudo to do the git clone etc, and if you did, you should make that choice explicitly yourself instead of being lead there by these instructions.  On the other hand, the apt install more or less has to run as root to be useful.
I'm guessing you located yourself in a root-owned directory instead of doing this in a directory your user has write access to.

thats right. Tried to clone to /opt/madmax


Testnet: Kzgrs config

1. What does this PR implement
This PR introduces changes related to the cfgsync utility, specifically adding new functionality for configuration synchronization between nodes. It also includes adjustments to the Docker Compose configurations.
2. Does the code have enough context to be clearly understood?
The code includes documentation and contextual comments where necessary..
3. Who are the specification authors and who is accountable for this PR?
@bacv, Nomos Engineering
4. Is the specification accurate and complete?
N/A
5. Does the implementation introduce changes in the specification?
N/A
Checklist

[x] 1. Description added.
[x] 2. Context and links to Specification document(s) added.
[x] 3. Main contact(s) (developers and specification authors) added
[x] 4. Implementation and Specification are 100% in sync including changes. This is critical.
[x] 5. Link PR to a specific milestone.

Is cfgsync a dispatcher of cfgs for the testnet nodes?

Is cfgsync a dispatcher of cfgs for the testnet nodes?

Yes, cfgsync replaces etcd and bash scripts for syncing the configurations for potentially arbitrary number of nodes in the network. In my opinion the key changes are reflected here:
https://github.com/logos-co/nomos-node/blob/24e81ab86e7169462036a4937ef40644b4e30393/compose.static.yml#L5-L13
https://github.com/logos-co/nomos-node/blob/24e81ab86e7169462036a4937ef40644b4e30393/testnet/scripts/run_nomos_node.sh#L1-L11

When a network is started, the cfgsync-server starts listening for a number of nodes to announce them selves;
If correct number of nodes requested config, cfgsync responds to all with the configuration;
Node is not started if cfgsync-client returns an error.


NSCalendarsUsageDescription - App rejected due to required permission and missing key

If you are creating an issue for a BUG please fill out this information. If you are asking a question or requesting a feature you can delete the sections below.
Failure to fill out this information will result in this issue being closed. If you post a full stack trace in a bug it will be closed, please post it to http://gist.github.com and then post the link here.
Bug Information
Version Number of Plugin: <IP_ADDRESS>
Device Tested On: iOS 11.4
Simulator Tested On: iOS 11.4
Version of VS:  15.7.2
Version of Xamarin:<IP_ADDRESS>8
Versions of other things you are using:
Steps to reproduce the Behavior
Using the permission plugin triggered a rejection from apple due to missing 'NSCalendarsUsageDescription' key that needs to acknowledge in the info.plist
Expected Behavior
The plugin doesn't actually and shouldn't required calendar permission to function.
Actual Behavior
Message from Apple when app is submitted for review:
"Missing Info.plist key - This app attempts to access privacy-sensitive data without a usage description. The app's Info.plist must contain an NSCalendarsUsageDescription key with a string value explaining to the user how the app uses this data."
Code snippet
Screenshots

see: https://github.com/jamesmontemagno/PermissionsPlugin#ios-specific

This is addressed in 5.0-beta: https://montemagno.com/optimizing-xamarin-apps-libraries-with-the-linker/

I'm a bit of newbie here...  using Xam.Plugin.Media to take pics in app (I was amazed -- AMAZED! -- at how easy this was).  But, when I submitted, I got App reject due to permission missing.     Having read the above coment about Plugin.Permission and 5.0 beta, I went to VS NuGet window and got Plugin.Permissions and bumped it (and only it) to v5,0.0-beta.  But, still getting rejects.  Did I miss something?  I have Linker Behavior set to "Link Framework SDKs Only" in Release.

You would need to be on: https://www.nuget.org/packages/Xam.Plugin.Media/4.3.0-beta which uses the latest APIs. Then after that Link Framework SDKs ONly.

I'm facing a similar issue. Using the following builds with "Link Framework SDKs only":

Xamarin.Forms v<IP_ADDRESS>6342-pre2
Plugin.Permissions v5.0.0-beta
Xam.Plugin.Media v4.3.0-beta

Rejection reason: "The app's Info.plist file should contain a NSCalendarsUsageDescription key with a user-facing purpose string"
As with the OP, the app in question doesn't know/care about the calendar. Anything else that could account for this?

Should add that in addition to NSCalendarsUsageDescription, I'm also being inexplicably warned about NSLocationAlwaysUsageDescription and NSLocationWhenInUseUsageDescription. In these cases it is just a warning, not basis for rejection, but obviously still a concern.

Are you using and calling Permissions Plugin anywhere yourself?

@jamesmontemagno - yes, I'm making the following 3 calls:
CheckPermissionStatusAsync(Permission.Storage)
RequestPermissionsAsync(new[] { Permission.Camera, Permission.Storage })
OpenAppSettings()

Yes, if you use the old API like that then it will not get linked out. You must use the new api in 5.0

To sum-up the solution to this problem (which was working for me).

Use Plugin.Permissions v5.0.0-beta (Forms and PCL)
If you don't have Plugin.Permissions v5.0.0-beta (or newer) but have Xam.Plugin.Media use Xam.Plugin.Media v4.3.0-beta (or newer) (Forms and PCL)
If you use directly the api to check permissions, be sure to not use a deprecated method (follow readme instructions, Visual Studio prompt you when you are using Deprecated methods).


remove the state option from exchangeWebFlowCode()

The state option for exchangeWebFlowCode() has no purpose and should be removed
The state option used to be documented at https://docs.github.com/en/developers/apps/building-oauth-apps/authorizing-oauth-apps#parameters-1, but it turned out that it was not used in the code, so it got removed. We should adapt our implementation and documentation according in order to not confuse developers as in https://github.com/octokit/auth-oauth-user-client.js/pull/3#discussion_r680541208
Pull request welcome! We can remove the state option from the types, we do not consider type changes such as this a breaking change as it's not impacting production environments, it only complains at build time.

done  via https://github.com/octokit/oauth-methods.js/pull/52


Hello there i'm trying to run a test on Non-toxin CD 's MGE, but i encounter an error which i can't slove

like this , does it means my contents in the  .fna file is not fit the workflow? i am able to  finish running the 2.4G files  used in tutorial ,
my workdir is like this:
----BJ22012
----00.assembly
----00.bam
----00.genome
bam and bam.bai files was created as tutorial showed but assembly file and genome file was using a assembled but not known which approach file and not sure if it is fit for the workflow , if workflow itself needs a specific format on contents please give a short sample , thanks for anyone who could help.

How many files are you working with?  Can you share some of the inferseq files that were generated?

How many files are you working with?  Can you share some of the inferseq files that were generated?

it only generated an empty inferseq file and directory only generated 01.mgefinder and 03.results ,i only work with one fna file to test my own work

I had the same problem, have you solved it yet?


future_to_promise Promise is not rejected if rust panics asynchronously

Describe the Bug
From the future_to_promise documentation:

If the future provided panics then the returned Promise will not resolve. Instead it will be a leaked promise. This is an unfortunate limitation of wasm currently that’s hoped to be fixed one day!

This behavior is very undesirable, so I think it would be good to have a bug on file for it.
I'm also curious about what the exact wasm limitation is, and where I can follow plans to fix it.
Steps to Reproduce
Rust:
use js_sys::Promise;
use wasm_bindgen::prelude::*;
use wasm_bindgen_futures::{future_to_promise, JsFuture};

#[wasm_bindgen]
pub fn mywasmfun() -> Promise {
    future_to_promise(mywasmfun_impl())
}

async fn mywasmfun_impl() -> Result<JsValue, JsValue> {
    panic!("Please catch this panic");
}

JS:
import init, { mywasmfun } from './pkg/wasm_bindgen_async_panic.js';

async function run() {
  await init();

  try {
    await mywasmfun();
  } catch (e) {
    console.log("Caught exception:", e);
  }
}

run();

Expected Behavior
Panics should be propagated upwards the "async stack" so that any awaits on the JS side can catch panics and don't keep waiting forever.
Actual Behavior
The panic never propagates, the await never completes.

So, from what I understand, the promise can only reject if something calls its reject handler. Usually this handler would be called from the Rust code. But since the Rust code has panicked, there's no one to call reject.
Might there be a way to make the JS-side of the bindings smarter, so that it can catch the panic exception and call reject without help from the Rust side?

Thanks for the report, but panics unfortunately basically don't work as means of communicating errors. Given the lack of exception handling in wasm handling panics is extremely difficult right now and largely not done by wasm-bindgen, leading to issues such as this. This is unlikely to change in the near future unfortuantely.

@alexcrichton  do you see a way to do error handling with rewriting the binary? Could the unreachable instruction be replaced by a wasm-bindgen call that would end up rejecting the Promise?

@xtuc Thank you for investigating this problem. May I ask, does that commit you made fixes this issue?

I'm going to close this as not really actionable.
The solution is to implement the exception handling proposal in Rust, until then panic! aren't supported and are more or less unsound. See #3687.


Fix all issues reported by checkstyle and make build fail if checkstyle fails

Pull request checklist
Please check if your PR fulfills the following requirements:

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been reviewed and added / updated if needed (for bug fixes / features)
[ ] The Unreleased section in CHANGELOG.md has been amended to reflect the changes in this PR
[X] Build (mvn verify) was run locally and any changes were pushed
[X] The pull request is against the correct branch (master for bug fixes, develop for new functionality)

Pull request type

Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[X] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Issue Number: N/A
What is the new behavior?

Checkstyle checks will now fail the build if violated
Checkstyle configuration has been fixed: the previous one was corrupted by the Eclipse Checkstyle editor

Does this introduce a breaking change?

[ ] Yes
[X] No

Other information

Checklist for maintainers
Releases

[ ] Do NOT push the green merge button on GitHub.
Follow the latest version of the developer/maintainer docs for making releases.

Build failed due to regression in Maven: https://issues.apache.org/jira/browse/MNG-6765.

Now build fails due to Checkstyle error (no space after <p>), although when tested locally it works just fine :(.


feat: Support ormb cmd proxy

What this PR does / why we need it:
Add your description
Which issue(s) this PR is related to (optional, link to 3rd issue(s)):
Fixes #
Reference to #

Special notes for your reviewer:
/cc @your-reviewer

Release note:

NONE

/cc @gaocegege

/lgtm
/approve


MINOR: Add tests for GroupedDropdownField empty strings

These bugs were never present in SS4 as the relevant code had a
substantial rewrite at the same time they were introduced in SS3.
In SS3, test C still fails.
Fixes #4705
Fixes #4987
Fixes #4783

Style failure... fixing


Vite version out of date

What is the plan for getting Vite up to date? We're currently pinned to 2.1.4, 2.1.5 has been out for a while and 2.2.1 just dropped. Also what is the deal with vite-fix-2390? We expect that to go away eventually?

vite-fix-2390 is not required anymore for >=2.2.0. It was a big release and I'm waiting a bit until goes through "real life testing".
If someone needs 2.2.x now, let me know and I'll skip the waiting and release a new vite-plugin-ssr right away.

We're currently pinned

We will not be pinned anymore.

Awesome!!

There are still some changes going on in 2.2.x so the plan is to wait a couple of days.

As of 0.1.0-beta.35, any Vite version >=2.2.3 can be used; the vite-fix-2390 package is not necessary anymore.


Stuck in cutscenes

Version
3.1.8 (2f583cd)
Seed
R720-W1M2-XXHH40C5Z9Y0003JZZZZZZZ5ZZZZZZZZZZZZZZZZZZZZZZZZZ
Scenario
RE 2 (Leon A)
Player Character
Alfred (CVX)
What happened?
Got stuck in cutscenes at the start and the end of the first Ada section of Leon A.
Playing as Alfred but got swapped to Kendo (RE2 Original) during both cutscenes. Kept walking around in circles during the cutscene before you swap to Ada. Speeding up the game seemed to fix it after a minute or two. Got stuck walking into the metal shutter during the cutscene at the end of Ada section. Not fixed by speeding up the game for a couple of minutes nor by teleporting into the room again.

I was not able to reproduce this


Ignite seems to be ignoring the JVM's user.timezone setting

I have two apache ignite clusters running on different servers, both instances specify -J-Duser.timezone=UTC on the ignite command line.
One of the servers appears to be ignoring this JVM setting, and I am pulling my hair out trying to figure out why.
Server A is Windows, and there are two Ignite nodes running on the same server ; Server B is AlmaLinux 8, there are actually two servers, each running an Ignite node...I have verified that they are being run the same way on each server.
The Ignite version is: gridgain-community-8.8.22
I run the following query on both instances:
SELECT FORMATDATETIME(TIMESTAMP '2001-02-03 04:05:06', 'EEE, d MMM yyyy HH:mm:ss z', 'en', 'GMT')
On server A, this returns what I expect:
Sat, 3 Feb 2001 04:05:06 GMT
On server B, though, it returns this:
Sat, 3 Feb 2001 10:05:06 GMT
The server time zone for both servers is CDT. So on server B, Ignite appears to be using the server time zone instead of the one specified in the JVM user.timezone parameter. I am at a loss as to how to figure out why this is the case, and am hoping someone here might be able to help.
The command line for Server A is:
ignite.bat -J-Duser.timezone=UTC ..\config\ignite-config.xml
The command line for Server B is:
/opt/ignite/bin/service.sh start -J-DIGNITE_SKIP_CONFIGURATION_CONSISTENCY_CHECK=true -J-Duser.timezone=UTC /etc/ignite/ignite-config.xml

It looks like the issue was caused by the database being created with Ignite running under the incorrect time zone setting.


Feature Request: Kill Switch?

Same - I tried today, setting up a killswitch with iptables rules... it was frustrating, but I know thats my fault. I looked in ca_vancouver.opvn, the remote line, and tried to come up with two sets of rules... both failed to operate as a good killswitch:
Rules 1:
:INPUT DROP [0:0]
:FORWARD DROP [0:0]
:OUTPUT DROP [0:0]
Allow local loopback device
-A INPUT -i lo -j ACCEPT
-A OUTPUT -o lo -j ACCEPT
Allow local network
-A INPUT -s <IP_ADDRESS>/24 -j ACCEPT
-A OUTPUT -d <IP_ADDRESS>/24 -j ACCEPT
Allow established and related incoming traffic
-A INPUT -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
Allow all traffic out on the VPN (tun+) interface
-A INPUT -i tun+ -j ACCEPT
-A OUTPUT -o tun+ -j ACCEPT
Allow VPN connection establishment
-A OUTPUT -d <IP_ADDRESS>/32 -j ACCEPT
-A OUTPUT -d <IP_ADDRESS>/32 -j ACCEPT
-A OUTPUT -p udp -m udp --dport 1197 -j ACCEPT
Reject all other outgoing traffic
-A OUTPUT -j REJECT --reject-with icmp-net-unreachable
COMMIT
Rules 2:
Switch to root (if not already)
sudo su
Flush all existing rules
iptables -F
Set default policies to DROP
iptables -P INPUT DROP
iptables -P FORWARD DROP
iptables -P OUTPUT DROP
Allow local loopback device
iptables -A INPUT -i lo -j ACCEPT
iptables -A OUTPUT -o lo -j ACCEPT
Allow local network
iptables -A INPUT -s <IP_ADDRESS>/24 -j ACCEPT
iptables -A OUTPUT -d <IP_ADDRESS>/24 -j ACCEPT
Allow established and related incoming traffic
iptables -A INPUT -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
Allow all traffic out on the VPN (tun+) interface
iptables -A INPUT -i tun+ -j ACCEPT
iptables -A OUTPUT -o tun+ -j ACCEPT
Allow VPN connection establishment
iptables -A OUTPUT -d <IP_ADDRESS>/32 -j ACCEPT
iptables -A OUTPUT -d <IP_ADDRESS>/32 -j ACCEPT
iptables -A OUTPUT -d <IP_ADDRESS>/32 -j ACCEPT
iptables -A OUTPUT -p udp -m udp --dport 1198 -j ACCEPT
Reject all other outgoing traffic
iptables -A OUTPUT -j REJECT --reject-with icmp-net-unreachable
Verify the rules
iptables -L -v -n
To save the rules after testing (if everything works)
iptables-save > /etc/iptables/iptables.rules
systemctl enable iptables
I know I posted two different formats - at any rate, can anyone help me find my issue?


Fix Python compare_versions function

Is this PR related to a proposed Issue?
No
What changes were proposed in this PR?
The compare_versions function in python/geospark/core/jvm/config.py seems to have a bug.
I think this function is supposed to return True if the left side is equal or higher than the right, but it's broken in some cases.
In [1]: from geospark.core.jvm.config import compare_versions

In [2]: compare_versions('1.2.3', '1.0.0')
Out[2]: True

In [3]: compare_versions('1.0.0', '1.3.2')
Out[3]: False

In [4]: compare_versions('1.3.2', '1.2.3')
Out[4]: False <- ??

This PR fixes the above bug.
How was this patch tested?
I locally ran cd python; pytest tests/utils/test_geo_spark_meta.py and confirmed it succeeded.
Did this PR include necessary documentation updates?
No

Thank you for finding the bug. I have no idea why your build is failing so I manually retried it.

@Imbruced Thank you for the review!

I have no idea why your build is failing so I manually retried it.

It looks like there are some reasons. I think I can submit another PR for fixing them in a few days.

For now, building GeoSpark generates geospark-1.3.2-SNAPSHOT.jar and geospark-sql_3.0-1.3.2-SNAPSHOT.jar by default, but the current regular expressions in .travis.yml don't match these filenames.

Spark 2.4.4 is downloaded in .travis.yml, but it may not be compatible with 3.0.0.

GeoTools were changed as 'provided' dependency due to the license incompatibility, so we have to download and deploy them manually to run full tests.

Thanks for the comment, that's a good improvement for clarity!
I've just updated my PR.


C++ program for reversal algorithm

Changes:
C++ program for reversal algorithm added.

D o n e

Done   Sent from Mail for Windows From: Princeton21Sent: 22 October 2022 17:12To: Princeton21/Data-Structures-and-AlgorithmsCc: Nitin singh; AuthorSubject: Re: [Princeton21/Data-Structures-and-Algorithms] C++ program for reversal algorithm (PR<EMAIL_ADDRESS>requested changes on this pull request.add your code in the specific folder and rename it accordingly.—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>


Blog post marked as malicious

References to the blog post serving as the 'inspiration for this gem' are flagged by Malwarebytes as malware distribution nodes. The website hosting that post may have been compromised.

I have tried to find out why this is happening.  Anybody with experience in this area wanna help?

Typically these flags happen when the given site has been reported as having distributed malware to multiple clients. It's possible the blog was compromised and an attack was mounted on it, perhaps one that can't be detected by a client, such as an XSS attack.
This is why https is becoming more of a standard. In standard unsecured http, there is no way of knowing if the site has been modified.
Anyways, I believe these sorts of alerts are usually from a website that has already distributed malware rather than one with proper conditions.
I don't claim to be a security expert and I may be wrong on one or more of these points.

On Oct 31, 2016, at 4:34 PM, Jeff Morgan<EMAIL_ADDRESS>wrote:
I have tried to find out why this is happening. Anybody with experience in this area wanna help?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I'm going to close this since it is not really about the page-object gem.


Installing Software Dependencies

We currently use pypostal to parse addresses within our crawlers (https://github.com/openvenues/pypostal).  This software requires some C code to be installed.  After installed the pre-requisites, the libpostal software needs the C libraries to be installed and set up.  Is this something that can be set up to run in the Crawlab container (see the relevant section below).  One other option I'm considering is running another container on my Ubuntu server with the libpostal API (https://github.com/johnlonganecker/libpostal-rest-docker), but I'm not sure if Crawlab would have access to the localhost API on my Ubuntu server.  Let me know what you think would be a workable solution.
git clone https://github.com/openvenues/libpostal
cd libpostal
./bootstrap.sh
./configure --datadir=[...some dir with a few GB of space...]
make
sudo make install
On Linux it's probably a good idea to run
sudo ldconfig

Hi, you can actually enter the Docker container to manually install the required library.
docker exec -it <container_name> bash

# commands to install the library
...

This worked beautifully.  Thanks for your help with this item!


automatically update release-please library

TL;DR
As new bug fixes and features are released for @googleapis/release-please, it would be nice if this project could be triggered to chore: build dist with the new version.
Would reduce the amount of maintenance with having to manually trigger the build PR every time.
Detailed design
No response
Additional information
See: #424

This would be amazing, we're currently waiting for version https://github.com/googleapis/release-please/releases/tag/v16.13.0 to be used


Add ability to change speed for each printer

From BGFiscalPrinterSetup.md

ВНИМАНИЕ: Библиотеката очаква серийният порт на фискалното устройство (ФУ) да е конфигуриран за скорост 115200 bps. Повечето ФУ са настроени за тази скорост, но ако това не е така, то може да го конфигурирате със сервизната му програма или в оторизирания сервиз.

Hello guys, first, great and quick support on the library.
I'd like to ask, would it be possible to set the speed for each fiscal device/printer when we are adding it manually?
Or another alternative would be if we are able to change the value in configuration json.
I would be nice if we are able to change the value of timeout too (currently 800ms).
Apologies if there's already a way to override those values. Unfortunately I was not able to find them in docs or closed issues.
Best regards, Denislav

The Speed or the Timeout? There is a big difference.
You can set the speed from the URI, for example: bg. dt.c.isl://COM5:9600

The timeout is good idea, but overriding the defaults can cause an unexpected behavior in some of the devices. I am afraid that it will triger more issues and we will be forced to limit that parameter with lower and upper bounds. What is the use case, in which you want manually to change the timeout?


Build aarch64 packages

Currently the Debian repository is only for armhf, most people will use RPi3 and RPi4's in 64-bit mode, so support them.

this seems to just work if line 32 of install.sh is changed to something like:
if uname -a | fgrep -ivq -e aarch -e arm; then
64bit kernel supports 32 bit just fine

this seems to just work if line 32 of install.sh is changed to something like:
if uname -a | fgrep -ivq -e aarch -e arm; then
64bit kernel supports 32 bit just fine

I think you misunderstood, with that change:
 ./install-rasp.sh
gpg: pub  rsa4096/09146F2F7953A455 2017-06-15  David Cooper<EMAIL_ADDRESS>gpg: no running gpg-agent - starting '/usr/bin/gpg-agent'
gpg: waiting for the agent to come up ... (5s)
gpg: connection to agent established
OK
deb https://dtcooper.github.io/raspotify raspotify main
Hit:1 https://download.docker.com/linux/ubuntu focal InRelease
Get:2 https://dtcooper.github.io/raspotify raspotify InRelease [1706 B]
Hit:3 http://ports.ubuntu.com/ubuntu-ports focal InRelease
Get:4 http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease [114 kB]
Get:6 http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease [101 kB]
Get:5 https://packages.cloud.google.com/apt kubernetes-xenial InRelease [9383 B]
Get:7 http://ports.ubuntu.com/ubuntu-ports focal-security InRelease [114 kB]
Fetched 339 kB in 2s (141 kB/s)
Reading package lists... Done
N: Skipping acquire of configured file 'main/binary-arm64/Packages' as repository 'https://dtcooper.github.io/raspotify raspotify InRelease' doesn't support architecture 'arm64'
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package raspotify

PR's welcome to enable aarch64 support.

Duplicate of https://github.com/dtcooper/raspotify/issues/263


Hannah's drawing app snapshot

@wagerpascal are we using google videochat tomorrow? my gmail address is<EMAIL_ADDRESS>

Google videochat is fine for tomorrow. But didn't we talk about a different method initially?
Anyways, my email is<EMAIL_ADDRESS>.

Looks good.
Merged.


upgrade: viem and wagmi to v2

Upgraded viem and wagmi to v2. (wagmi v2 40% smaller)

Thank you for your contribution, we will review as soon as possible.

Appreciate it @dasanra!


[low] Image Uploader/Editor for adding Locomotive images

23rd March 2021: will not be implemented as full webui interface, user must provide locomotive images manually in a specific directory, the must have the same name as the locomotive and will be loaded on demand.
Wiki entry will follow.

added wiki article
https://github.com/cbries/railessentials/wiki/Adding-Locomotive-Images-Photos


UnboundLocalError: local variable 'strand' referenced before assignment

how to solve it?
when I run predict_sites,it will happened

There is no ratio.0.5.tsv/sam_parse2.txt/genome.0.5.bed/genome_abandance.0.5.bed in this folder of result,but others have. Thank you.


Bad action name in french

In french, "ingenuity" is "Ingéniosité" instead of "Inqéniosité" (g not q)
@see http://xivdb.com/action/277
Thanks ! Great works ! :)

Uploaded to beta site.