Handle notification callback in the background

PR Type
New feature - Hold notifications when the app is in background and and call the app callback once back in foreground.

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation  changes
[ ] Other... Please describe:

PR Checklist
Please check your PR fulfills the following requirements:
Bugfixes:

[x] Regression testing has been carried out using the example project to ensure the intended bug is fixed and no regression bugs have been inadvertently introduced.

New features/enhancements:

[x] Exhaustive testing has been carried out for the new functionality
[x] Regression testing has been carried out to ensure no existing functionality is adversely affected
[ ] Documentation has been added / updated
[ ] The example project has been update to validate/demonstrate the new functionality.

What is the purpose of this PR?
New message notifications, call the onMessageReceived callback. This might be important to handle new notifications by the app, especially data notifications. In both Android and iOS, the plugin is calling the onMessageReceived callback but when the application is in the background for more than 20-30 seconds, the callback does not execute.
In case of Android, when the app is not active (the main activity is closed), the callback is not valid as the WebView does not exist.
The plugin already implements a queue to hold any pending notifications until the app calls onMessageReceived for the first time or the plugin has finished initializing.
This PR extends the functionality of this queue to hold any pending notifications when the app is in the background or inactive. As soon as the application resumes, the plugin will send all pending notifications back to the onMessageReceived callback.
Does this PR introduce a breaking change?

[x] Yes
[ ] No

The default behavior of the plugin when sending notifications to the onMessageReceived callback when the app is in the background is not consistent and depends on the device type and the amount of time the application is in the background. The new behavior must be documented and properly explained.
In case some applications rely on notifications being sent while the app is in the background, this change might break this behavior as notifications will never be calling onMessageReceived callback when the app is in the background.
There should be minimal or no impact on visible notifications.
What testing has been done on the changes in the PR?
Multiple Android and iOS devices tested in all states for processing data notifications.
What testing has been done on existing functionality?
Other notification types seem to not being impacted. No other functionality of the plugin has been changed.
Other information
Bringing this PR to the public discussion to understand if this is something that should be integrated in the plugin. If this is something valuable or could break the existing behavior or something we couldn't think about.

Thanks, this is a valuable contribution. I'll test this on the dev branch, document the behaviour, and bump the major version of the plugin before releasing due to the breaking change.

I have made an attempt to document the new behaviour: https://github.com/dpa99c/cordova-plugin-firebasex/commit/980c6e9e76bf244ecdb236b6cd3039d0d65040d4
I'd be most grateful if you have time to quickly review and confirm this is correct.

I'm just wondering if, to aid with backward-compatibility for any applications currently using this plugin and depending on notification payloads being immediately delivered while the app is in the background (rather than queued), we could add support for an optional property in the notification payload e.g. immediate_delivery: true which would bypass the queue and deliver the payload right away after the notification arrives?

to aid with backward-compatibility
notification payload e.g. immediate_delivery: true

This can be a safer option, but I think this option should not involve the server side (sender), but rather be a client side option instead. Can be added as an optional parameter to onMessageReceived function or even a plugin variable.
From our testing, no modern device was found that is receiving data notifications while the app is in the background. Therefore, not sure if anyone can rely on receiving messages in the background at all.

to aid with backward-compatibility
notification payload e.g. immediate_delivery: true

This can be a safer option, but I think this option should not involve the server side (sender), but rather be a client side option instead. Can be added as an optional parameter to onMessageReceived function or even a plugin variable. From our testing, no modern device was found that is receiving data notifications while the app is in the background. Therefore, not sure if anyone can rely on receiving messages in the background at all.

OK, we can make it a plugin variable set at plugin install time which is false by default but if anyone wants to risk using it (maybe they have a specific use case) then they have the option

I have implemented the plugin variable for iOS as well and tested on both platforms (iOS was missing a call to send pending notifications on app resume which is also fixed). It passes my set of manual tests now, so I've merged it to master branch and we'll see what users make of the new behaviour.


Remove DockerContainer from beam_fn_api

beam_runner_api.Environment is the message to use to represent an
execution environment or container.
Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Run mvn clean verify to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

LGTM, feel free to merge


XY Chart: Add y-axis

Other charts, like the Resource Status, do not have a y axis, but still need to be vertically aligned with all other charts. This creates an empty space that we can leave empty or use in some other way.
I put together 3 options for using this space:

Option A: y-axis outside xy chart, other charts stay as they are.

Option B: y-axis inside xy chart, other charts and top x axis show blue empty space.

Option C: y-axis inside xy chart, other charts have the extra space on the left filled by the tree (text). Top x axis is indented.

I will give another example of how it could be done:

From
https://github.com/d3/d3-axis
I am thinking that it could be interesting with a couple of base assumptions.

Users read the center of the view more than the sides
Zooming is a more common action than panning.

However, the only way to be sure is to try it out some more.

@Rodrigoplp-work Thanks for taking the time to post design options in advance! I like the option you went with in the PR #567.


APS-609: Hide the Raw combined applications and placement requests do…

…wnload report option
Context

Changes in this PR
Hide the Raw combined applications and placement requests download report option
Screenshots of UI changes
Before
After

Please squash the commits before merging


Enhancement, get planner by rosterId

Right now the command planner plan get retrieves the plan when you provide the rosterId next to id or title. Let's enhance the command so you can retrieve the plan just by providing the rosterId option.
The options ownerGroupId and ownerGroupName optionset should only run when title is provided.
Example:
m365 planner plan get --rosterId "RuY-PSpdw02drevnYDTCJpgAEfoI"

instead of
m365 planner plan get --title PlannerTitle --rosterId "RuY-PSpdw02drevnYDTCJpgAEfoI"

This should already be implemented if I'm not mistaken by #4406.

This should already be implemented if I'm not mistaken by PR #4432 (issue #4401)

let me be more specific, right now it is implemented, but you have to provide title or id & rosterId, we should be able to provide rosterId single like discussed  here

Let's make the commands consistent indeed, would you like to fix this @nicodecleyre?

@nicodecleyre, how would you be able to get a plan by rosterId if there are more plans in said roster?

@nicodecleyre, how would you be able to get a plan by rosterId if there are more plans in said roster?

There is only the ability to have one plan per roster and not multiple.

Let's make the commands consistent indeed, would you like to fix this @nicodecleyre?

Sure

There is only the ability to have one plan per roster and not multiple.

Are you sure @MathijsVerbeeck, it seems odd that the graph endpoint returns an array for it:
https://learn.microsoft.com/en-us/graph/api/plannerroster-list-plans?view=graph-rest-beta&tabs=http

I find it odd, but somewhere else I read 'A plannerRoster can contain one plan.', so you must be correct

Graph endpoint indeed returns an array, but if you try to add multiple plans to the same roster, you are getting an error. Also in the documentation they always refer to a single plan, never multiple plans. E.g. "when you remove the roster, the plan and its tasks are also removed".


Error after precmd refactor.

This just popped up today for me, without any changes to headline configuration.  I suspect my dotfiles manager just pulled the newest version of the theme for the first time in a while (set to pull newest copy in main every ~6 months).
headline-precmd:26: closing brace expected

This is on zsh 5.8 (x86_64-redhat-linux-gnu) on Rocky9.2.
No issues on zsh 5.9 (arm-apple-darwin21.3.0) on Sonoma 14.7.

I believe I've fixed the issue. Let me know if it works for you now

Works great for me.  Thanks so much for a quick solution, and for maintaining this nice theme.


Remove -m option in dockerfile

Image fails to run with -m function

I think this would just start the python interpreter and not execute any ebbo code.


Logbook and History showing not found

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.25.2
Python release (python3 --version):
python 3.4.5
Component/platform:
loggbook history
Description of problem:
from frontend the logbook does not show any state changes or history. The history component says no state history found.
Expected:
used to just load the history to view.
Problem-relevant configuration.yaml entries and steps to reproduce:

Traceback (if applicable):

Additional info:
There are no nu-ordinary exceptions in the logs or anything.

Everything seems to work fine here. Tested in all major browsers.
Which browser and operating system do you use?

Ok I Don't know what was going on but it seems to be working now

I've the same issue on my productive system. After update I don't see any history or recorde data for a while. After ~8 hour it was working...

Can you see recent events? Or is the display always a couple (8?) hours behind?

And what happens when you change dates?

I think it was a cache trouble of my chrome


Add before-push hook to check unit tests

What is the motivation for adding / enhancing this feature?

Continuation of #3444  with running tests:unit on pre-push stage
What are the acceptance criteria

[ ] push needs to run tests:unit

Can you complete this feature request by yourself?

[ ] YES
[ ] NO

Which Release Cycle state this refers to? Info for developer.
Pick one option.

[x] This is a normal feature request. This should be available on https://test.storefrontcloud.io and then after tests this can be added to next Vue Storefront version. In this case Developer should create branch from develop branch and create Pull Request 2. Feature / Improvement back to develop.
[ ] (Pick this option only if you're sure) This is an important improvement request for current Release Candidate version on https://next.storefrontcloud.io and should be placed in next RC version. In this case Developer should create branch from release branch and create Pull Request 3. Stabilisation fix back to release.
[ ] (Pick this option only if you're sure) This is a critical improvement request for current Stable version on https://demo.storefrontcloud.io and should be placed in next stable version. In this case Developer should create branch from hotfix or master branch and create Pull Request 4. Hotfix back to hotfix.

Additional information

Related PR: https://github.com/DivanteLtd/vue-storefront/pull/3646


Implement limiting the number of entries

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

Project coverage is 75.55%. Comparing base (6b411ed) to head (5cc397e).
Report is 3 commits behind head on main.

Files with missing lines
Patch %
Lines

src/segmented_cache_helpers.erl
80.64%
6 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #18      +/-   ##
==========================================
+ Coverage   75.28%   75.55%   +0.26%
==========================================
  Files           4        4
  Lines         174      180       +6
==========================================
+ Hits          131      136       +5
- Misses         43       44       +1

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


Add CodeWarrior Branch

Have FRAY compiling locally with CodeWarrior. Would like to make a branch for it that likely won't go maintained, outside of using it to test for matching assembly/performing a compiler attack on confusing functions.

[ ] Fix DVD loading. Currently cannot find GmTitle.usd with the library DVDFastOpen, and my custom version causes an alignment issue.
[ ] Figure out optimization settings. Can test a known matching function, such as TObj's functions.

Decided not to do this for now.


window.parentIframe does not get set in an angular context

First of all, I don't know if this is related to angular at all. Actually, I doubt it but I figured it might be an interesting piece of information.
If have an angular app, that I want to include in an iframe with the resizer. The resizing works perfectly, only sending messages from the iframe to the parent does not work at all. The reason is, that the parentIframe will not be added to the window object of the iframe. Neither to window nor to the $window services that is exposed via angular. I added a couple of tests to my app to see if it is due to delay, but it just never appears:
      var test = function() {
        if ('parentIFrame' in window) {
          console.log('found it in window');
        }
        else {
          console.log('not in window');
        }

        $timeout(test, 1000);
      };
      test();

      var test2 = function() {
        console.log('test2 triggered');
        window.iFrameResizer = {
          readyCallback: function(){
            console.log('test2 callbacl');
              var myId = window.parentIFrame.getId();
              window.xyz = window.parentIFrame;
              console.log('The ID of the iFrame in the parent page is: '+myId);
          }
        }
      }
      test2();

The callback never gets executed. The resizing itself works properly. I looked a bit into the code and saw the setupPublicMethods() method which seems to add the parentIFrame object to the window. The log statements inside this method never get executed. No hint in the log about init messages that are sent from the parent to the client. Since the resizing doesn't seem to make use of these public functions, that seems to be the reason why resizing works.
Any idea at what point I could start digging deeper to find out why this is happening?

Don't really do Angular, however, I'd suggest looking at where the iframeResizer object gets bound to the window. Not sure how Angular would block that from happening, or what $window is. Could you test for the later their and bind to both if it exists?
If you make a simple test case, I'd be interested to take a look at some point, but hyper busy right now.

I use iframeResizer + AngularJS 1.2 and 1.3 on production, and I don't have this kind of problem. Aren't you forgetting to add the contentWindow script inside the angular page or calling it before the frame is ready?

Trying to do the same with Angular 2. Maybe Luiz has had a change to make it work with it?


Remove mirrors dependency?

Hy @thosakwe, do you have any plans on removing mirrors dep (ex. in quiver package)? Would be awesome for aot compilation.

This has already been done; Angel 2.0 has no dart:mirrors dependency whatsoever. Make sure you’re not using Jael, or MirrorsReflector.

But the framework uses quiver, that depends on mirrors, I just checked.

Only the hash code computation functionality from quiver is used. I’ve never run into an issue using dart2aot with Angel.

Previous discussion: https://github.com/angel-dart/angel/issues/103

Oh, may be I'm doing something wrong then, I run dart2aot bin/main.dart bin/main.dart.aot on a pretty basic demo app and it tells me error: import of dart:mirrors with --enable-mirrors=false

I’d have to see your code to know, but package:angel_framework doesn’t use dart:mirrors. If you used angel init, then you should definitely take a look at https://github.com/angel-dart/angel/issues/103.

As an added note, there’s no quiver dependency, only quiver_hashcode: https://github.com/angel-dart/framework/blob/master/pubspec.yaml

Sounds interesting, this is my repo, I have read the conversation, but it still does not work: https://github.com/denisbakhtin/hello_angel

angel_hot isn’t intended for AOT use, it’s development-only. Also, I highly doubt it will work at all, since hot reload is VM-only.

Ok i will try without it :)

Yes, angel_hot was the reason, thank you for explanation!


How to use iPhone hooks to open image in app

How do you implement the {{id}} option in Templating so that it opens the image in the Instagram app instead of opening a new window in the browser as I have it now?

Closing as complete.


Rust 1.77.2 upgrade

Clippy is now able to warn about unused fields, I did some investigating for each case but it's possible I made mistakes.

What's the status on this @Anton-4 or @folkertdev? This looks good to me.

Yeah Folkert's concern is valid here, let's wait a bit for @ayazhafiz to check out his comment.


TypeError: Cannot call a class as a function

Do you want to request a feature or report a bug?
Bug
What is the current behavior?
My code is running fine in production but tests are not passing when importing an object from a file, error is: TypeError: Cannot call a class as a function at at _classCallCheck (node_modules/react-native/jest/mockComponent.js:9:616)
Object I'm importing:
export const Fabric = {
  Crashlytics: {
    logException: jest.fn(),
    setString: jest.fn(),
    setUserEmail: jest.fn(),
    recordError: jest.fn()
  },
  Answers: {
    logSignUp: jest.fn(),
    logException: jest.fn(),
    logCustom: jest.fn(),
    logLogin: jest.fn()
  },
};

import statement
const {Answers} = require('../../../test/setup').Fabric;
Commenting that line ^ makes the test pass
Just adding that import statement throws Cannot call a class as a function at at _classCallCheck (node_modules/react-native/jest/mockComponent.js:9:616)
The same import statement works fine in other files, this error happens running jest -u --runInBand, doesn't happen when running the code in production.
The actual test:
const tree = renderer.create(
      <MyComponent />
    ).toJSON();
expect(tree).toMatchSnapshot();

What is the expected behavior?
Test should pass or tell me what the real problem is.
Please provide your exact Jest configuration and mention your Jest, node, yarn/npm version and operating system.
"jest": {
    "collectCoverageFrom": [
      "**/*.{js,jsx}",
    ],
    "haste": {
      "defaultPlatform": "ios",
      "platforms": [
        "android",
        "ios"
      ],
      "providesModuleNodeModules": [
        "react-native"
      ]
    },
    "globals": {
      "__TEST__": true
    },
    "moduleNameMapper": {
      "^image![a-zA-Z0-9$_-]+$": "GlobalImageStub",
      "^[./a-zA-Z0-9$_-]+\\.(bmp|gif|jpg|jpeg|png|psd|svg|webp)$": "RelativeImageStub",
      "^React$": "<rootDir>node_modules/react",
      "\\./datepicker$": "<rootDir>/node_modules/tcomb-form-native/lib/templates/bootstrap/datepicker.ios.js",
      "\\./select$": "<rootDir>/node_modules/tcomb-form-native/lib/templates/bootstrap/select.ios.js"
    },
    "modulePathIgnorePatterns": [
      "<rootDir>/node_modules/react-native/Libraries/react-native/",
      "<rootDir>/node_modules/react-native/packager/",
      "<rootDir>/node_modules/react-native-fabric/"
    ],
    "transformIgnorePatterns": [
      "node_modules/(?!(jest-)?react-native|tcomb-form-native|react-clone-referenced-element)"
    ],
    "setupFiles": [
      "<rootDir>/node_modules/react-native/jest/setup.js"
    ],
    "testEnvironment": "node",
    "testResultsProcessor": "./node_modules/jest-junit",
    "collectCoverage": true,
    "verbose": false
  },

OS macOS Sierra 10.12.2
npm -v 3.10.8
node -v v6.7.0
jest ^18.1.0

this line was breaking it: global.__DEV__ = false;


Building from source not using cuda defined path

I am trying to compile jax from source on a Linux CentosOS7 machine using cuda-10.1.243 and cudnn-<IP_ADDRESS> with python 3.6.8. I have defined the cuda path and the cudnn path as follows:
CUDA_ROOT:
/opt/spack/c7.7/compilers-20200612/spack/opt/spack/linux-centos7-x86_64/gcc-4.8.5/cuda-10.1.243-7pddwdl3rtgpr5cmojwalw266jg64clc/

and
CUDNN_ROOT:
/opt/spack/c7.7/stock-20200612/spack/opt/spack/linux-centos7-x86_64/gcc-7.5.0/cudnn-<IP_ADDRESS>-10.2-linux-x64-jj7xix24767akabowzvo4lq2nwlbapuv/

When I run
$python build/build.py --enable_cuda --cuda_path $CUDA_ROOT --cudnn_path $CUDNN_ROOT`

in the command line, the initialization goes fine, but then afterwards I get an error. It seems that it's linking to /usr/local/cuda incorrectly even though I defined a different root. See below:
     _   _  __  __
    | | / \ \ \/ /
 _  | |/ _ \ \  /
| |_| / ___ \/  \
 \___/_/   \/_/\_\

Bazel binary path: ./bazel-2.0.0-linux-x86_64
Python binary path: /home/kchowdh/gpu_test_py36/bin/python
Python version: 3.6
MKL-DNN enabled: yes
-march=native: no
CUDA enabled: yes
CUDA toolkit path: /opt/spack/c7.7/compilers-20200612/spack/opt/spack/linux-centos7-x86_64/gcc-4.8.5/cuda-10.1.243-7pddwdl3rtgpr5cmojwalw266jg64clc/
CUDNN library path: /opt/spack/c7.7/stock-20200612/spack/opt/spack/linux-centos7-x86_64/gcc-7.5.0/cudnn-<IP_ADDRESS>-10.2-linux-x64-jj7xix24767akabowzvo4lq2nwlbapuv/
CUDA compute capabilities: 3.5,5.2,6.0,6.1,7.0

So it's setting the user defined folders correctly, but then it tries to look in the wrong folder:
Building XLA and installing it in the jaxlib source tree...
./bazel-2.0.0-linux-x86_64 run --verbose_failures=true --config=short_logs --config=mkl_open_source_only --config=cuda --define=xla_python_enable_gpu=true :install_xla_in_source_tree /home/kchowdh/jax/build
INFO: Options provided by the client:
  Inherited 'common' options: --isatty=0 --terminal_columns=80
INFO: Reading rc options for 'run' from /home/kchowdh/jax/.bazelrc:
  Inherited 'common' options: --experimental_repo_remote_exec
INFO: Reading rc options for 'run' from /home/kchowdh/jax/.bazelrc:
  Inherited 'build' options: --repo_env PYTHON_BIN_PATH=/home/kchowdh/gpu_test_py36/bin/python --python_path=/home/kchowdh/gpu_test_py36/bin/python --repo_env TF_NEED_CUDA=1 --action_env TF_CUDA_COMPUTE_CAPABILITIES=3.5,5.2,6.0,6.1,7.0 --distinct_host_configuration=false --copt=-Wno-sign-compare -c opt --apple_platform_type=macos --macos_minimum_os=10.9 --announce_rc --define open_source_build=true --define=no_aws_support=true --define=no_gcp_support=true --define=no_hdfs_support=true --define=no_kafka_support=true --define=no_ignite_support=true --define=grpc_no_ares=true --spawn_strategy=standalone --strategy=Genrule=standalone --cxxopt=-std=c++14 --host_cxxopt=-std=c++14 --action_env CUDA_TOOLKIT_PATH=/opt/spack/c7.7/compilers-20200612/spack/opt/spack/linux-centos7-x86_64/gcc-4.8.5/cuda-10.1.243-7pddwdl3rtgpr5cmojwalw266jg64clc/ --action_env CUDNN_INSTALL_PATH=/opt/spack/c7.7/stock-20200612/spack/opt/spack/linux-centos7-x86_64/gcc-7.5.0/cudnn-<IP_ADDRESS>-10.2-linux-x64-jj7xix24767akabowzvo4lq2nwlbapuv/
INFO: Found applicable config definition build:short_logs in file /home/kchowdh/jax/.bazelrc: --output_filter=DONT_MATCH_ANYTHING
INFO: Found applicable config definition build:mkl_open_source_only in file /home/kchowdh/jax/.bazelrc: --define=tensorflow_mkldnn_contraction_kernel=1
INFO: Found applicable config definition build:cuda in file /home/kchowdh/jax/.bazelrc: --crosstool_top=@local_config_cuda//crosstool:toolchain --define=using_cuda=true --define=using_cuda_nvcc=true
Loading:
Loading: 0 packages loaded
INFO: Call stack for the definition of repository 'local_config_cuda' which is a cuda_configure (rule definition at /home/kchowdh/.cache/bazel/_bazel_kchowdh/cc36dafb1b8e245ab9b2a660c3a2dc0d/external/org_tensorflow/third_party/gpus/cuda_configure.bzl:1430:18):
 - /home/kchowdh/.cache/bazel/_bazel_kchowdh/cc36dafb1b8e245ab9b2a660c3a2dc0d/external/org_tensorflow/tensorflow/workspace.bzl:97:5
 - /home/kchowdh/.cache/bazel/_bazel_kchowdh/cc36dafb1b8e245ab9b2a660c3a2dc0d/external/org_tensorflow/tensorflow/workspace.bzl:76:5
 - /home/kchowdh/jax/WORKSPACE:46:1
Loading: 0 packages loaded
    currently loading: build
ERROR: An error occurred during the fetch of repository 'local_config_cuda':
   Traceback (most recent call last):
	File "/home/kchowdh/.cache/bazel/_bazel_kchowdh/cc36dafb1b8e245ab9b2a660c3a2dc0d/external/org_tensorflow/third_party/gpus/cuda_configure.bzl", line 1400
		_create_local_cuda_repository(<1 more arguments>)
	File "/home/kchowdh/.cache/bazel/_bazel_kchowdh/cc36dafb1b8e245ab9b2a660c3a2dc0d/external/org_tensorflow/third_party/gpus/cuda_configure.bzl", line 1075, in _create_local_cuda_repository
		_find_libs(repository_ctx, <2 more arguments>)
	File "/home/kchowdh/.cache/bazel/_bazel_kchowdh/cc36dafb1b8e245ab9b2a660c3a2dc0d/external/org_tensorflow/third_party/gpus/cuda_configure.bzl", line 606, in _find_libs
		_check_cuda_libs(repository_ctx, <2 more arguments>)
	File "/home/kchowdh/.cache/bazel/_bazel_kchowdh/cc36dafb1b8e245ab9b2a660c3a2dc0d/external/org_tensorflow/third_party/gpus/cuda_configure.bzl", line 501, in _check_cuda_libs
		execute(repository_ctx, <1 more arguments>)
	File "/home/kchowdh/.cache/bazel/_bazel_kchowdh/cc36dafb1b8e245ab9b2a660c3a2dc0d/external/org_tensorflow/third_party/remote_config/common.bzl", line 217, in execute
		fail(<1 more arguments>)
Repository command failed
No library found under: /opt/spack/c7.3/base2/spack/opt/spack/linux-centos7-x86_64/gcc-4.8.5/cuda-8.0.44-7damutmq5sdv5bzxgccunxoppdc5hymy/lib64/libcublas.so.10

The CUDA_ROOT I defined above is NOT being used in the compilation. From above, it looks like the compilation is trying to look in /usr/local/cuda which (on this machine) is linked to
/opt/spack/c7.3/base2/spack/opt/spack/linux-centos7-x86_64/gcc-4.8.5/cuda-8.0.44-7damutmq5sdv5bzxgccunxoppdc5hymy

I am not the admin on the system so I cannot change this (although I am trying to get it fixed). So somewhere in the build code it is using /usr/local/cuda and not $CUDA_ROOT.

I think it may be an issue with the bazel installation. Is there a way to edit the bazel configuration to force it to look into the custom CUDA ROOT?

I was able to solve this problem by defining TF_CUDA_PATHS ahead of the installation. In my terminal I ran
export TF_CUDA_PATHS=$CUDA_ROOT,$INCLUDE,$LD_LIBRARY_PATH
After this, bazel was able to find the correct path to cuda. I also had to upgrade my gcc to 7.5.0 FYI.


UCS-73 : Review policy wrapper

A small simplification of the PolicyWrapper.
Solves a sonar warning for a too much complex function.

I've extended a bit this work and opted to not use Optionals in the build functions of these wrappers.
Instead I'm throwing exceptions.
The rest of the code has been adjusted, tested.
There's also a minor cleanup of the pdp


Exclude file from traceback no longer working with relative path

I had the habit of giving __file__ to exclude_file_from_traceback(), and I think it worked back then.
But now it does no longer works. I don't really know what changed, so I'm starting to inspect:
Locally on my machine it works, but __file__ is absolute, on HackInScience __file__ contains ./check.py and it does not work.
If I call exclude_file_from_traceback with "./check.py" or "check.py" it does not get excluded.
I don't know if it's indended to work as is, or if exclude_file_from_traceback should call .resolve() on it before check if the file exists?

I'm not familiar with .resolve() but what I am guessing from the name is that this is something that should be done.  I will investigate...

I'm investingating in my DB, looks like it changed recently:
hkis=> select date_trunc('month', created_at) d, 100 * sum(case when correction_message like '%check.py%' then 1 end) / count(1) from website_answer group by d order by d;
 2021-01-01 00:00:00+01 |        0
 2021-02-01 00:00:00+01 |        1
 2021-03-01 00:00:00+01 |        1
 2021-04-01 00:00:00+02 |        2
 2021-05-01 00:00:00+02 |        2
 2021-06-01 00:00:00+02 |        1
 2021-07-01 00:00:00+02 |        2
 2021-08-01 00:00:00+02 |        2
 2021-09-01 00:00:00+02 |        1
 2021-10-01 00:00:00+02 |        1
 2021-11-01 00:00:00+01 |       11

We went from 1%±1% during the previous month to 11% this month.
The 1%±1% can be explained easily by me forgetting the exclude line in a few exercises...

I cannot figure out what would have changed recently; perhaps you changed the version of friendly-traceback you used recently.  I propose to replace (copy-pasted)
    if not os.path.isfile(full_path):
        raise RuntimeError(
            f"{full_path} is not a valid file path; it cannot be excluded."
        )
    # full_path could be a pathlib.Path instance
    full_path = str(full_path)
    EXCLUDED_FILE_PATH.add(full_path)

by the following (untested)
# full_path could be a pathlib.Path instance
full_path = str(full_path)
full_path = os.path.abspath(full_path)  # new
if not os.path.isfile(full_path):
    raise RuntimeError(
        f"{full_path} is not a valid file path; it cannot be excluded."
    )
    EXCLUDED_FILE_PATH.add(full_path)

and do a similar conversion using os.path.abspath in is_excluded_file.

So, I sshd to correction servers to try various versions of friendly-traceback, and now the bug dissapeared.
I had 0.4.62 on both servers, I tried 0.4.59, 0.4.60, 0.4.61, and back to 0.4.62 and no bug.
I hate when this happen.
I'm staring blankly to:
    Uninstalling friendly-traceback-0.4.62:
      Successfully uninstalled friendly-traceback-0.4.62
Successfully installed friendly-traceback-0.4.59

prooving I was previously using 0.4.62, and all other line showing no other dependencies being updated during the upgrade session... wow...

Weird. Still, I decided to add the conversion to the absolute path just in case.  This is in the newest version (0.4.63) just uploaded.

So, I tried various versions of friendly-traceback and its dependencies:
   28  pip install friendly-traceback==0.4.59
   29  pip install friendly-traceback==0.4.60
   30  pip install friendly-traceback==0.4.61
   31  pip install friendly-traceback==0.4.59
   32  pip install friendly-traceback==0.4.61
   33  pip install friendly-traceback==0.4.62
   34  pip install friendly-traceback==0.4.59
   35  pip install friendly-traceback==0.4.55
   36  pip install friendly-traceback==0.4.59
   37  pip install stack-data==0.1.2
   38  pip install stack-data==0.1.0
   39  pip install pure-eval==0.2.1
   41  pip install asttokens==2.0.4
   42  pip install executing==0.5.3
   43  pip install pure-eval==0.1.1
   44  pip list
   45  pip install friendly-traceback==0.4.55
   46  pip install friendly==0.4.21
   47  pip install friendly-traceback==0.4.39
   48  pip install friendly-traceback==0.4.20
   49  pip install friendly-traceback==0.4.39

without being able to make it work with an old version.

Weird. Still, I decided to add the conversion to the absolute path just in case. This is in the newest version (0.4.63) just uploaded.

It correctly fixed the issue, thanks \o/ \o/


decoder: formatting improvements

Besides refactoring the log formatting code, this PR introduces a few new features:
{c} metadata specifier
Now it's possible to add {c} to the log format in order to print the crate name. I'm currently parsing this out of the module path, there may be better ways to do this.
More detailed {f} metadata specifiers
I found the {f} specifier to be not very useful in most cases, mainly because a lot of files are called mod.rs. Now it's possible to increase how detailed to print the path to the file by adding {ff}, {fff}, etc... to the log format. With {ff} the Formatter would print format/mod.rs instead of just mod.rs, which I think is much more useful.
Zero-padding support
I added the zero-padding functionality from #780 to this PR. Now it's possible to zero-pad metadata specifiers, such as the timestamp or the line number.

I am actually a bit unsure how to go about it. Yes, the default format logic is duplicated in https://github.com/knurling-rs/probe-run/pull/425, but it is actually a bit different than in probe-run and also different than in this PR. Yes they check if there is a timestamp or not, but they also have a --no-location flag. So the code on that side would not necessarily get more simple by this PR. Also note that they are not using log and therefore not defmt_decoder::log::init_logger.

Yes they check if there is a timestamp or not, but they also have a --no-location flag.

I'd then propose to add a no-location flag to DefmtLoggerConfig. I don't see why not, it seems like it would be a fairly common configuration option.

Also note that they are not using log and therefore not defmt_decoder::log::init_logger

I think all of this logic would end up in the Formatter introduced in #781, so I don't see this as an issue.

Makes sense

I did a relatively big refactor of all the formatting stuff.

I did a relatively big refactor of all the formatting stuff.

Cool, thank you! I will hand over the project to a colleague this week. He will come back to you.

Hi @Urhengulas, do you know if your colleague will have time for some reviews soon?

I'll take a look now.

Looks good to me. It'll need a rebase to fix the CHANGELOG, and perhaps we could squash the first three commits, just for neatness.

Rebased now :)

Ping @jonathanpallant


Support afterCreate/afterUpdate database triggers

Problem
The Prisma client offers a way to modify inbound queries and updates to the database through middleware but offers no way to trigger actions based on the full result of a create/update operation.
For example, say I want to create a Post model with a default id that's generated by the database and a corresponding PostRevsion model for the creation and every update to the Post. There's no way for one to use middleware to create a PostRevision and reference back to the Post because the middleware has no access to the final database generated data. It is a similar case with updates which might only partially update the contents of Post meaning the middleware has no access to the complete Post to create a revision of.
Suggested solution
Copied from #653:
Prisma Client should have a way to define functions before and after crud operations. Here is an example that I thought of which would be pretty common. The Sequelize link I posted above also has plenty of examples and concepts, basically an instruction guide on what to include.
prisma = new PrismaClient();
prisma.setTriggers(prisma => ({
  beforeOrderCreate: async (args: OrderCreateArgs): Promise<OrderCreateArgs> => {
  const grandTotal = calcGrandTotal(args.data.lineItems.create);
  // Error can be thrown here
  await processPayment(grandTotal, args.data.user.connect.id);
  return {
    ...args,
    {
      data: {
        ...args.data,
        grandTotal
      }
    }
  })
  afterOrderCreate: async (order: Order): Promise<void> => {
    const user = await prisma.order.findOne({ where: { id: order.id } }).user();
    if (user.acceptsEmail) {
       await sendEmailToCustomer(order.id, order.grandTotal, user.name);
    }
  },
  afterOrderUpdate: async (newOrder: Order, oldOrder: Order): Promise<void> => {
    if (newOrder.grandTotal !== oldOrder.grandTotal) {
      await prisma.creditNote.create({
        data: {
          amount: newOrder.grandTotal - oldOrder.grandTotal,
          order: { connect: { id: newOrder.id }
        }
      }
    }
  }
}))

From me:
This feature would be even more powerful if coupled with long-running transactions but it's perhaps already too complex.
Alternatives
Alternatively, providing a way to define these triggers within schema.prisma would be sufficient for my use case while also providing the transactional guarantees required.
Additional context

Ok, I've had a look at Prisma Migrate and the migration workflow and generated SQL it provides seems to work for the alternative I outlined. I'll close this issue once I've explored it further. :)

Ok, I've had a look at Prisma Migrate and the migration workflow and generated SQL it provides seems to work for the alternative I outlined. I'll close this issue once I've explored it further. :)

I've managed to workaround this issue by creating database triggers using SQL. Closing.

I've managed to workaround this issue by creating database triggers using SQL. Closing.


Add specs for Random::Formatter#alphanumeric

Another one for Ruby 3.3 (#1216), but this adds some specs for earlier Ruby versions too.
There are more methods defined on RandomFormatter, we should probably add specs for the remaining methods too.

There are failures on Ruby 3.0. Could you please take a look?


Ability to specify the filename when saving in crop()

Hi, would be nice if its possible to set Ability to specify the filename when saving in crop()
export function crop(frame: Frame, config?: CropConfig | undefined): CropResult

export interface CropConfig{
  cropRegion?: CropRegion;
  includeImageBase64?: boolean;
  saveBitmap?: boolean;
  saveAsFile?: boolean;
  fileName?: string;
}

Thanks so much

You can use a file system plugin to do this: https://www.npmjs.com/package/react-native-file-access


attr-unsafe-chars rule overprotective?

I'm getting an "attr-unsafe-char" failure with the following elements (in a xhtml file):
<link rel="icon" type="image/x-icon" href="data:image/x-icon;base64,R0lGODlhEAAQAKEAAAAAAICAgP///wAAACH/
    C05FVFNDQVBFMi4wAwEAAAAh/hFDcmVhdGVkIHdpdGggR0lNUAAh+QQBZAADACwAAAAAEAAQAAACJIyPacLtvp5kEUwYmL00i81VXK
    eNgjiioQdeqsuakXl6tIIjBQAh+QQBZAADACwAAAAAEAAQAAACIIyPacLtvp5kcb5qG85iZ2+BkyiRV8BBaEqtrKkqslEAADs="/>

and
<svg xmlns="http://www.w3.org/2000/svg" version="1.1" width="20" height="20" viewBox="0 0 500 500">
  <path d="M 250, 0 c -138, 0 -250, 112 -250, 250, 0, 112, 73.3, 206, 174, 238, 10, 1, 14 -6, 14 -12
           v -43 c -70, 16 -84 -33 -84 -33 -11.8 -29 -28.1 -37 -28.1 -37 -22.8 -15, 1.7 -15, 1.7 -15,
           25.4, 2, 38.4, 26, 38.4, 26, 22, 38, 58, 27, 73, 21, 2 -16, 8 -28, 15 -34 -55 -6 -114 -28
           -114 -124, 0 -27, 9.5 -49, 25.5 -67 -2 -6 -11 -32, 3 -66, 0, 0, 21 -6.8, 68, 26, 20 -6, 42
           -9, 63 -9 s 43, 3, 63, 9 c 47 -32.9, 68 -26, 68 -26, 14, 34, 5, 60, 3, 66, 16, 18, 26, 40,
           26, 67, 0, 96 -59, 117 -114, 123, 8, 8, 16, 23, 16, 47 v 68 c 0, 7, 5, 14, 17, 12, 99 -33,
           171 -127, 171 -237, 0 -138 -112 -250 -250 -250 z" fill="#333333"/>
</svg>

...in the "href" and "d" attributes, respectively. What are the unsafe chars in these cases, exactly? The regex in the wiki page isn't easy to decipher.

Done: https://github.com/yaniswang/HTMLHint/commit/30860c94546c11c3a34af1a463ed9c19e6ff5a2a

Ah, of course, the newlines. I should have guessed. Thanks for the quick fix :)


Taskbar icon

Operating system: Windows 10.
Messenger for Desktop version: 2.0.8 stable.
The tray icon is fine, the taskbar icon however isn't working. I tried reinstalling.

Just an update: if I pin the icon to the taskbar using the shortcut created on the desktop during the installation it's fixed but if I launch the app without pinning it that way it gives the same result as the screenshot. So I think the icon is somehow not linked with the application itself? not sure how it all works.

already mentioned here https://github.com/aluxian/Messenger-for-Desktop/issues/1206  ... it is issue persisting from older releases ...

I have repaired this issue, but I cannot provide exact description as I have repaired it now and I cannot look at it again.
The problem is in links. If you install new version, even new link links to new version app, but icon link is targeted to version, that no longer exists. The problem is, that the icon is not loaded from direct link or exe, but from another link somewhere in Programs folder of user. I remember, that I have found some 2.0.7 link which were able to launch 2.0.9 app, but the icon on change alerted, that it cannot find 2.0.7 directory.
You have to replace links for app on your drive (use search toolbar for it) and than the icon on taskbar is good.
The truth is, that the current installer makes quite a mess in filesystem. Best thing will be creating classic windows installer with Program Files installation path and without versioning. Jist copy it to one folder and the app will be always in that folder, links will have same name and no problem....

Thanks for the detailed info. I'm going to close this as a duplicate and continue tracking this problem here: https://github.com/aluxian/Messenger-for-Desktop/issues/1206


NVTabular - Add tests to DFEncoder

[ ] Start with sample tests representative of the DFP type workloads (i.e. use DFP sample data) that run using the existing DFEncoder in the separate repo
[ ] Run all those same tests using the new implementation, validating the output against the old code
[ ] Add new tests for any additional features that were added above and beyond due to NVT

As of 23.07, new tests have been added for DFP and NVTabular is now used for all ETL. Closing


fix: ignore static fields and properties

Closes #376
Closes #379

Codecov Report

Merging #380 (361c705) into main (685d6ee) will decrease coverage by 0.19%.
The diff coverage is 94.11%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main     #380      +/-   ##
==========================================
- Coverage   91.91%   91.73%   -0.19%
==========================================
  Files         126      126
  Lines        3921     3931      +10
  Branches      544      548       +4
==========================================
+ Hits         3604     3606       +2
- Misses        210      214       +4
- Partials      107      111       +4

Impacted Files
Coverage Δ

...Riok.Mapperly/Diagnostics/DiagnosticDescriptors.cs
100.00% <ø> (ø)

...Mapperly/Descriptors/UserMethodMappingExtractor.cs
92.43% <33.33%> (-5.97%)
:arrow_down:

...iptors/MappingBuilders/DictionaryMappingBuilder.cs
86.36% <100.00%> (+0.31%)
:arrow_up:

...iptors/MappingBuilders/EnumerableMappingBuilder.cs
94.51% <100.00%> (+0.43%)
:arrow_up:

src/Riok.Mapperly/Descriptors/WellKnownTypes.cs
96.15% <100.00%> (+2.40%)
:arrow_up:

src/Riok.Mapperly/Helpers/SymbolExtensions.cs
87.36% <100.00%> (+0.70%)
:arrow_up:

... and 1 file with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Add API to support clearing of task caches from fly

Add API to support clearing of task caches from fly.  Supports concourse/concourse#1817.
Intended to go with:
concourse/go-concourse#16
concourse/fly#254

No prob!  I've made the requested changes.  Also, I wasn't sure where to put the new ClearTaskCacheResponse struct, but I've put it in task.go for now.

Thanks a lot! Merged it manually with a commit on top to change the query param (minor consistency nitpick). I also opened https://github.com/concourse/concourse/issues/2517 fyi for additional acceptance test coverage for this, which we're happy to do ourselves or help you out if you wanna do it yourself.


negative loss

Hi :
I am using the GPU version RNNTLoss, but the loss is negative.
the shape of logits and targets is as follows:
targets: [batch_size, U]
logits: [batch_size, T, U+1, hidden]
RNNTloss(logits, targets, input_len, target_len)

However when I run on cpu, the loss is normal.

@HawkAaron
there is no activation function before rnntloss

Did you follow the same procedure as bellow?
GPU: logits -> RNNTLoss
CPU: logits -> log_softmax -> RNNTLoss

@HawkAaron
my procedure is as bellows.
CPU: logits -> RNNTLoss
GPU: logits -> RNNTLoss
both of them have no activation before RNNTLoss.

Could you update the code and rebuild again?  Everything is ok in my environment.
please provide more information if this problem happened again. (python, pytorch, cuda, gcc)

I have updated the latest code. But I haven't solve the problem. So I calculate the RNNTLoss on cpu at last. Maybe I will find the problem later when I debug my code.

I have the same problem when using tensorflow 1.15.0.rc2 (CUDA 10, gcc 7.4.0)
all tests (gpu_test, cpu_tests, tensorflow tests) are passed
Previously I used tf 1.10 and everything was ok, then I upgraded tf, rebuild RNNTLoss, and get negative loss.
I install RNNTLoss using the following steps in docker:
ENV CUDA_HOME /usr/local/cuda
ENV LD_LIBRARY_PATH="/usr/local/cuda/lib64:${LD_LIBRARY_PATH}"
RUN cd /rnnt/rnnt-loss && mkdir /rnnt/rnnt-loss/build
RUN cd /rnnt/rnnt-loss/build && cmake -DCUDA_TOOLKIT_ROOT_DIR=$CUDA_HOME .. &&
make
RUN ldconfig /usr/local/cuda/lib64/stubs &&
cd /rnnt/rnnt-loss/tensorflow_binding && CUDA=$CUDA_HOME python3 setup.py install

update:
I tried to rerun experiment with updated version of RNNTLoss and tf 1.10 and got negative loss.
My previous RNNTloss version was in 6e33845c9acecce0c9489f1f2c333f2ef548d986 commit and everything was OK in tf 1.10 (but this version doesn't work with tf 1.15)
Also, I got the following error using tf 1.10:
src/warprnnt_op.cc:8:52: fatal error: tensorflow/core/framework/bounds_check.h: No such file or directory
this file was renamed for tf >= 1.14 support and doesn't exist now for tf 1.10

Just a quick question: Should the blank label be compulsorily 0? What about GPU vs CPU?

I observed that a high learning rate, led to a steep decline in the loss and subsequently the loss started becoming negative for some examples in the batch. This was observed with a LR of 1e-4, on my data. Unsure, if the cause is the network code or rnnt-loss code. Any comments?

UPD:
I tried to rerun experiment with updated version of RNNTLoss and tf 1.10 and got negative loss.
My previous RNNTloss version was in 6e33845 commit and everything was OK in tf 1.10 (but this version doesn't work with tf 1.15)
Also, I got the following error using tf 1.10:
src/warprnnt_op.cc:8:52: fatal error: tensorflow/core/framework/bounds_check.h: No such file or directory
this file was renamed for tf >= 1.14 support and doesn't exist now for tf 1.10
UPD2:
I found a bug in my code: the problem was in wrong blank_index, everything is OK now.

I also have the question that is it reasonable to have negative loss, maybe it is because the probability i s the sum of all alignments, which means the probability  can be larger than 1 and the loss can be negative?
BTW, what do you mean by "the problem was in wrong blank_index"??

The recent pull request #64 may fix this issue.

@Sudharsansai  The blank label can be any class inside your vocab (with blank included).


STEP-10: Add controller, service and DTO's for "Full information"

Create controller, service and DTO's classes for "Full information"
Acceptance criteria:

Controller created
Service created
DTO's created

Implements in https://github.com/EllsaG/power-supply-design/pull/49 pull request.


Notifications Modals

When user clicks view the correct modal comes up for the user to preform the correct action.
Modals include:

[ ] Unsigned orders, market liquidity
[ ] cancel orders, cancel all orders in resolved market
[ ] sell complete sets
[ ] claim winning proceeds
[ ] finalize market
[ ] claim reporting fees and staked REP

@bthaile -- Is this duped with the transaction work the @andrewdamelio did?

This task is specifically for modals. The notifications have a ‘view’ button that brings up modals. This is a list of the individual modals. @johndanz can you check off the ones done

@JohnDanz this tix was meant as a high level checklist. I ended up creating individual tix thinking each modal can be hooked up to notifications and tested.
When you think you have all the modals done check them off.

all in individual tickets - closing this


bug: qs.reports.html: TypeError

Consider the following return series, which will be used as input for qs.reports.html:
2001-12-31: 0.0000
2002-01-02: 0.0000
2002-01-03: 0.0150
2002-01-04: -0.0020
...
In this specific case, I do get a TypeError: operands could not be broadcast together with shapes (258,), (259,). Unfortunately, I am not able to provide the concrete Traceback as I am working behind a corporate firewall (no copy&paste). However, the problem seems to be originated here:
https://github.com/ranaroussi/quantstats/blob/0f66023d421d864387c596f245244e0f324d7577/quantstats/reports.py#L131-L134
From what I can tell, this bug only appears when the very first entry of the return series is zero and from a different year compared to the second entry in the return series. However, this needs some more investigation on your side.

Can this bug be replicated on your side?


Does not Support new Firebird 3.X DataTypes

Does not support BIGINT and BOOLEAN data types (likely others).  Cannot display metadata properly, and cannot perform selects.  Essentially tool is now useless if using newer types.  Great tool, would love to see it updated.

Hi, please test the latest snapshot available and let me know if it's working
https://github.com/mariuz/flamerobin/releases/tag/<IP_ADDRESS>

Works like a charm.  Viewing Table properties no longer throws an error.  Looking forward to a 64 bit release.


Error: Cannot find module '@babel/runtime/helpers/interopRequireWildcard'

When running babel-node with this preset, I am encountering the following error and call stack:
internal/modules/cjs/loader.js:628
    throw err;
    ^

Error: Cannot find module '@babel/runtime/helpers/interopRequireWildcard'
Require stack:
- /Users/pauljaworski/Projects/ponto-api/src/index.js
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:625:15)
    at Function.Module._load (internal/modules/cjs/loader.js:527:27)
    at Module.require (internal/modules/cjs/loader.js:683:19)
    at require (internal/modules/cjs/helpers.js:16:16)
    at Object.<anonymous> (/Users/pauljaworski/Projects/ponto-api/src/index.js:3:31)
    at Module._compile (internal/modules/cjs/loader.js:776:30)
    at Module._compile (/Users/pauljaworski/Projects/ponto-api/node_modules/pirates/lib/index.js:99:24)
    at Module._extensions..js (internal/modules/cjs/loader.js:787:10)
    at Object.newLoader [as .js] (/Users/pauljaworski/Projects/ponto-api/node_modules/pirates/lib/index.js:104:7)
    at Module.load (internal/modules/cjs/loader.js:643:32) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [ '/Users/pauljaworski/Projects/ponto-api/src/index.js' ]
}

The issue goes away when I switch to @babel/preset-env, so I'm assuming it's coming from this preset. Happy to provide more information if needed. Thanks!

I believe this is happening because this preset uses @babel/plugin-transform-runtime which requires that you have @babel/runtime installed as a dependency in your application. There is a peerDependency on that package here that needs to be satisfied in your application: https://github.com/airbnb/babel-preset-airbnb/blob/388dcef304c30290dd365948d232dde2bbba168e/package.json#L35
You should see a warning about this when you npm install if you don't have that peerDependency requirement met.


New package: RoughSurfaces v0.1.1

Registering package: RoughSurfaces
Repository: https://github.com/rleegates/RoughSurfaces.jl
Created by: @rleegates
Version: v0.1.1
Commit: c261df3ac30609d6be2c555eda5eeb6396f4ce33
Reviewed by: @rleegates
Reference: https://github.com/rleegates/RoughSurfaces.jl/commit/c261df3ac30609d6be2c555eda5eeb6396f4ce33#commitcomment-140704567

Thank you for submitting your package! However, please extend the README a bit more before the registration can be merged. At the very least, it should include a small usage example. Without any documentation, a package isn't really usable for the General public.


Handling of multiple acquisition runs as a single processing run

Use Cases:

Several long period runs, possibly broken up by a power outage for example
Regular High Frequency, short-duration acquistions, e.g. ZEN

Case 2 can be handled by breaking  process_mth5_decimation_level into:
#stft_agg = []
#for run in runlist:
# stft_obj = make_stft_decimation_level()
#stft_agg.append(stft_obj)
# tf_obj = process_stft_decimation_level(stft_agg)

ProcessingRunTS class could be used to manage, or at least reference the data
This acts to Merge runs/ processing mixed runs

Desired Elements:
-The ability to slice mth5 runs based on time interval.  (A workaround was used to put this functionality into VA Tech analysis but this will be needed in general for trimming remote references.)
Could be done by trimming an existing run ts or by loading with a time interval argument
method for handling changes in metadata from run to run (this should actually be handled by a new station instance).  In any case, if an instrument is swapped out, we want the previous and future runs to relate to the same location.  It is not clear if we would want to mix the runs with the different instruments in a single processing job ... if we did using FC class as an interface would be useful
-Metadata standards changes:  Generally how to handle multiple runs in the new vs the old metadata?
When the time are explicitly enumerated it's pretty straight forward, but when the stream comes back broken up we need to detect and build runs on the fly or repair /mend time series

Run merging requirements
-must handle an arbitrary number of runs
-must handle decimation
Nan filling is a general solution with two potential complications
A big gaps could overload ram
B filtering edge effects

Ideally we want a model that is completely general (for disjoint time series).  The TSCollection is associated with a list of time intervals ℐ0 = {(a,b)_i such that all data to be processed are in the Union of  (a,b)_i).  The individual elements of ℐ0 are normally acquisition runs, or intervals properly contained in acquisition runs, but we want to be careful not to exclude the case of joining acquisition runs via some gap-fill technique.  For example, a few long acquisition runs, with only a short gap in between may want to be processed for very long periods (longer than either acquisition run can yield alone).
A companion set of intervals, where synthetic data (interp, iawrw, etc) can be overlain on the original set.

The place where this will be implemented in the code is the function process_mth5_run in aurora/pipelines/process_mth5.py
The current function structure is:
def process_mth5_run(
    run_cfg,
    run_id,
    units="MT",
    show_plot=False,
    z_file_path=None,
    return_collection=True,
    **kwargs,
):

To support multiple runs we could replace run_id (currently a string) with optionally with a list of strings, each specifying a run.  Implementing this change does not look too complicated.  The function structure would stay very similar.  Instead of extracting a single run, and STFT and process, we would instead extract each run in the list, and STFT each individually.  Then the STFTs would be merged together in one xarray of spectral measurements and that array would be passed to the TF estimation method.
This solution should work in general for single station processing.
For multiple station processing there is one more layer to consider here.  The run labels will not in general be the same for different stations.  We would need an iterable of runs for the station of interest, and also an iterable of runs for the remote reference station.  The determination of which runs will be processed is currently not supported.

This is done in frequency domain. Issue  #152 is still open about doing this in time domain.


Add flag to ignore potential FieldPermissionErrors in validate_draft

The validate_draft needs to schema.load(...) the (already stored) metadata instead of schema.dump(...), because the latter does not validate the object to serialize anymore since version 3.0.0rc9.
However, the RDMRecordSchema defines field-level permissions for loading.
This is usually okay because it is typically just the record/draft's creator/owner who can preview the draft.
However, it breaks the share-by-link feature if used to grant preview permissions, because the link does not (and should not) give update_draft permissions.
So when some person (who is not the owner of the record/draft) accesses the preview page via such a shared link, they will not have the required update_draft permission, and the schema.load(...) operation will fail due to a FieldPermissionError (regardless of whether the draft is valid or not).
This PR fixes that issue by adding a flag that allows to ignore these field-level permissions.
Note: This does not circumvent any permission checks, because they are typically already performed elsewhere (e.g. in the service calls used by the view functions' decorators).
Link: Relevant discussion in Discord

On second thought... Probably it would be better to prevent the checking of field-level permissions here entirely as opposed to catching the FieldPermissionError.
I am afraid that otherwise, the raising of the permission error could potentially mask other errors due to breaking out of normal program control flow.
I'm thinking about setting a no-op field_permission_check in the context to prevent the construction of the default one in ServiceSchemaWrapper._build_context(...)


Supports iOS 18+ runtime downloads

This PR attempts to port the logic from https://github.com/XcodesOrg/XcodesApp/pull/622 to the CLI tool.
Fixes #384
The logic in the downloadAndInstallRuntime was modified to now switch over the runtime's content type.  The previous existing package and disk image installs were left unchanged, but the .cryptexDiskImage case is now handled by the downloadAndInstallUsingXcodeBuild function.
This function does 3 main things (broken into some smaller helper functions for those).

Check that we're using a new enough version of Xcode
Start downloading using Xcodebuild and create an AsyncStream of the progress
Write out that progress to the console

Testing:
In order to test this out you will need to have xcode 16.1 or newer installed.
Things I tested and seemed to work for me:

try to install a runtime with the correct xcode selected
try to install a cryptex runtime with a too low version selected

Caveats:
I'm not sure what happens to the underlying xcodebuild install process if you cancel the command from the terminal with CMD+C.
When the selected runtime is already installed, the tool will still go through the download process but complete quickly:
Downloading Runtime iOS 18.1: 0%
Downloading Runtime iOS 18.1: 0%
Downloading Runtime iOS 18.1: 0%
Downloading Runtime iOS 18.1: 0%
Finished

It might be worth following up in a future PR to check if the runtime is actually already installed instead of doing this.

@MattKiazyk guessing you’re busy with other work stuff, just wanted to bump this in case it got lost in the shuffle. Let me know if there’s anything else I can do

@spadafiva sorry was trying to get login back up and working first. I'll look at this right away. Ok if I make any changes to your PR needed and just merge?

@spadafiva sorry was trying to get login back up and working first. I'll look at this right away. Ok if I make any changes to your PR needed and just merge?

Sounds great!  Thanks!  Also, if there's anything I can to do help with the login stuff, would love to help out if I can.

@spadafiva sorry was trying to get login back up and working first. I'll look at this right away. Ok if I make any changes to your PR needed and just merge?

Sounds great! Thanks! Also, if there's anything I can to do help with the login stuff, would love to help out if I can.

PR https://github.com/XcodesOrg/xcodes/pull/393 is up that includes it, if you'd like to test.

Also, @MattKiazyk, just in case it's not clear, thanks so much for maintaining the very useful tool.  Me (and the the rest of the team) definitely appreciate how useful it is and the hard work you've put into maintaining it.

@MattKiazyk  could you add documentation on how to download runtimes, I am trying to automated a CLI pipeline and I want to download runtimes first before installing it
when I try  this I get
xcodes runtimes download "iOS 18.1"
Error: Downloading runtime iOS 18.1 is not supported at this time. Please use `xcodes runtimes install "iOS 18.1"` instead.

why does it need to check if xcode installed first, I am just trying to download the package, otherwise I would have used install command

@MattKiazyk could you add documentation on how to download runtimes, I am trying to automated a CLI pipeline and I want to download runtimes first before installing it
when I try this I get
xcodes runtimes download "iOS 18.1"
Error: Downloading runtime iOS 18.1 is not supported at this time. Please use `xcodes runtimes install "iOS 18.1"` instead.

why does it need to check if xcode installed first, I am just trying to download the package, otherwise I would have used install command

iOS 18.1 can't be ** just downloaded ** since it relies on the built in xcodebuild command now due to the changes on apple's side.  So you can only install, it's not possible to download without installing.

To clarify - Xcodes currently only wraps the install command of xcodebuild
There is a xcodebuild -exportPath command available to export the runtime, but xcodes hasn't implemented that yet.


Showcase Submission for challenges/179-wolfram-ca

Thank you Mahdad Borhani for your contribution! A member of the Coding Train team will review it shortly.

CA Accidentally found Sierpinski Triangle
Mahdad Borhani

First one, great work!


Remove TransportExecutor tests

These tests were created when we didn't have analyzer / planner
implementations but wanted to have integration tests for the execution
layer.
This commit removes those tests because they're hard to maintain and
meanwhile we've added full-stack integration tests which cover the
execution as well.

@dobe please review


[shell] warn when removing non-existent package

Summary
How was it tested?

Current dependencies on/for this PR:

main

PR #230   👈

This comment was auto-generated by Graphite.

@gcurtis @LucilleH Should the warning be to stdout or stderr?


Make icons

I want two 24px square icons, in light-ish gray, one for my user logo and one for the moon.
These will (eventually) be used on the footer of my site.

I'm not going to make an icon to move into night mode.  The site is just going to be night mode all the time. Better for people's eyes, better on the environment.


Define api-sync data response model versions

It's quite clear from https://github.com/jsdelivr/api/issues/56 that this project does not differentiate between api "versions". This needs to be fixed so we can have have reliable endpoints.

Currently, the same api-sync database is used by both versions, so the data model is a mix of both versions, and each api response needs to be formatted depending on the used version. This "formatting" means that for every project, we need to select which properties should be returned and change their structure if there's a difference between versions (e.g. assets).
This isn't ideal, but works, as long as the method of building a list of projects on the CDN doesn't change. Ironically, to make a change like #46 without changing behavior of v1, we'd have to add code to v1 to filter out the new projects on every request. This approach is maybe easier in the short-term, but every change in api-sync means more complex code in all api versions, and a chance of introducing a breaking change if something is overlooked.
The only way I can see to fix this is having a separate database for each API version.

the data model is a mix of both versions

Then you clearly do not understand what API versioning is or rather what it is intended to solve. You cannot call these "versions". At this rate, the differences between v1 and v2 are really just "ideas" of versioning. They are not associated, in any way, with what is actually consumed by an endpoint.
https://www.mnot.net/blog/2011/10/25/web_api_versioning_smackdown
https://www.mnot.net/blog/2012/12/04/api-evolution

This "formatting" means that for every project, we need to select which properties should be returned and change their structure if there's a difference between versions

Yes. What you're referring to as "formatting" is actually what API versioning is. I understand that at some point the idea of what the response data model is for v1 and v2 is going to differ. This is how APIs evolve and become "better".
What jsDelivr are failing to realize (and produce) is that if it wishes to "mix" (backwards compatible) features or response data model properties/keys, then you have to duplicate code to provide the same "effect". You cannot just simple change the existing response data modal.
The point is:
You cannot change or remove existing parameters/keys from an API. Period.
That would constitute an API as "unstable" and "unreliable" (which has been par for the course). If you wish to cleanup or migrate something in the data response model, you would have to do so in a new version because it would be a "major break" from what existing code what written for. An example of what constitutes a "major break":
https://developer.github.com/v3/versions/#differences-from-beta-version

Ironically, to make a change like #46 without changing behavior of v1, we'd have to add code to v1 to filter out the new projects on every request.

No you don't. Real API versioning means that you have multiple code bases (branches, projects, etc.). Any code, and I mean any, that even remote touches the API should be "version aware" so it can produce the correct response data model for each API "version" it needs to. There is never a need to "filter stuff out" if you work in a specific version's code base from the beginning.

The only way I can see to fix this is having a separate database for each API version.

Exactly! As I stated in the other issue, jsDelivr is authoritative here. The reason jsDelivr is authoritative is because it is the one that is taking an existing source, parsing it and then reconstructing it into whatever response data model it's outputting.
Thus, this means that jsDelivr is now that one creating a new source (because it does not reflect the original data you parsed). However you choose store this newly constructed data is up to you really, but my guess is that keeping two different databases would be the easiest solution.
This all being said, I would imagine that if you really don't want to keep two database then you'll probably have to obfuscate this project to an even more "internal" tool and create a new intermediate "response" project that is responsible for constructing the appropriate versioned endpoints (e.g. api-response or whatever).

Then you clearly do not understand what API versioning is or rather what it is intended to solve.

Actually, I perfectly understand what API versioning is, and I agree with most of your points. I started working on this project about a week ago, and my comment above was just a summary of the current situation.
@jimaek thoughts?

@MartinKolarik, I'm sorry, I didn't me "you" specifically... I meant more of how this project as a whole has treated "versioning". I'm still trying to learn how to not personalize and escalate problems with my responses. Please bear with me. Has just been a very frustrating past 24hrs (on my end).

I am really sorry for the troubles that this change caused. When I reviewed the PR I didn't realize that it would have impact on v1 as well. If I knew that at the time under no circumstances I would merge it.
Thats the whole point of v2, to do all the breaking changes there and leave v1 as is with all of its problems as is.
I take the responsibility here and will make sure nothing similar happens ever again.
Also since I am not a node.js developer I cant comment on what is the best way to implement that functionality. From my end that requirement is that it needs to work on v2 and leave v1 alone.
But I think maintaining 2 DB files would not be that hard or require any maintenance in the future.
We can then map each json file to v1 and v2 respectfully.
Is that as easy as I think it is? Are there better solutions?

Is that as easy as I think it is? Are there better solutions?

It's not that hard, and I think it's the most robust solution. The biggest downside is it would double memory usage which is already relatively high, but it shouldn't be a big problem.

I didn't realize that it would have impact on v1 as well.

Yes, which is why different code bases (branches, all [sub-]projects, etc.) is really important for "versioning" APIs. It helps diminish the "manual human error" aspect of things. If the PR had been merged into a hypothetical v2 branch for instance, this issue would never have occurred (since the hypothetical v1 branch would be untouched).

Also since I am not a node.js developer I cant comment on what is the best way to implement that functionality

Interesting. I'm curious then, why was Node.js chosen and by whom? I have some experience with Node.js, but my speciality is more front end (JS) related.

From my end that requirement is that it needs to work on v2 and leave v1 alone.
But I think maintaining 2 DB files would not be that hard or require any maintenance in the future.
We can then map each json file to v1 and v2 respectfully.

Yes!

Are there better solutions?

Technically speaking, I have no idea ATM since I'm not all that familiar with all the internals of jsDelivr. However from a architectural/QA perspective, perhaps one of the simplest "solutions" would be for me to "officially" help out a bit?
I'm really good at seeing the "big picture" of things. Also, considering that I'm actually already quite heavily invested in needing/keeping this service, would it be fair to ask (at the very least) if maybe y'all ping me when any "bootstrap/bootswatch" stuff is about to happen before it's actually deployed?

@MartinKolarik The RAM usage should not be that big. The bootstrap repo and DB are very small compared to other CDNs we have. If you agree on this solution then lets do that. Unless you can think of something even easier to implement that works.

Interesting. I'm curious then, why was Node.js chosen and by whom? I have some experience with Node.js, but my speciality is more front end (JS) related.

The original API was written by a contributor for free. He knew node.js best so he used that. It made no sense to re-write everything in PHP or something else when he became less active.

I'm really good at seeing the "big picture" of things. Also, considering that I'm actually already quite heavily invested in needing/keeping this service, would it be fair to ask (at the very least) if maybe y'all ping me when any "bootstrap/bootswatch" stuff is about to happen before it's actually deployed?
I would love that. You can simply subscribe to the 2 API related repos to get emails about everything happening. And I will try to ping you in the comments when its related to bootstrap.
Btw do you have any feedback for v2 in general? https://github.com/jsdelivr/api/tree/v2
Since its not live yet we can still change anything we want.

The RAM usage should not be that big. The bootstrap repo and DB are very small compared to other CDNs we have.

If we were to do this, I meant for all CDNs, to completely separate the versions. There's no point in doing it only for bootstrap.

Why not? The rest dont have any issues.

If we were to do this, I meant for all CDNs, to completely separate the versions. There's no point in doing it only for bootstrap.

Agreed. There shouldn't be special cases.

Why not? The rest dont have any issues.

Because this isn't a "bootstrap/bootswatch" specific problem, this is an "API versioning" problem for jsDelivr itself. Every time a new version is created, you have to essentially fork the previous version and create a new database for that new version. Thus, this would affect all projects.

The original API was written by a contributor for free. He knew node.js best so he used that. It made no sense to re-write everything in PHP or something else when he became less active.

Agreed. I was just curious. I would certainly be willing to help out here (over time). My recent involvement with publishing some node.js/grunt based packages has been fun and a great learning curve.

I would love that. You can simply subscribe to the 2 API related repos to get emails about everything happening. And I will try to ping you in the comments when its related to bootstrap.

Yes. I've held off because my inbox is generally already overflowing from the various projects I'm apart of. I would perhaps prefer manual pings (is there an gitter/IRC channel y'all use by chance?) when it's particularly related to bootstrap for now. Perhaps over time (when I have the time), I will become more involved.

Btw do you have any feedback for v2 in general? https://github.com/jsdelivr/api/tree/v2
Since its not live yet we can still change anything we want.

I haven't looked at any of the internal code yet. And since there's no working v2 URL, even for beta, I haven't really seen any real output. Perhaps I can spend some time this weekend to get some local instances of all these projects up and running. Maybe even start creating issues/submitting some PRs?

@jimaek See my first comment. They do, the issues just weren't that serious so far. E.g. when I added the repository field, I also had to update v1 code to exclude that field from v1.

@markcarver

And since there's no working v2 URL, even for beta, I haven't really seen any real output. Perhaps I can spend some time this weekend to get some local instances of all these projects up and running.

https://jsdelivr-api.herokuapp.com/v2

@MartinKolarik If you believe thats the best way then lets do it.
@markcarver We are all here https://gitter.im/jsdelivr/jsdelivr
Also regarding v2 you can just check the README for most of the stuff and tell us what you think. And Martin left the beta URL


fabric8-rbac rolebinding is over-permissive

Cluster-admin, really?
I admit I haven't done a deep dive on the code, but surely something that gets, lists and watches cluster state doesn't need permission to edit and delete everything in the cluster!

I agree. This should be addressed soon...

Related: https://github.com/spekt8/spekt8/issues/11
And I mentioned this as an example of a major security risk (for the reason @switchboardOp mentioned, as well as the fact that this also grants all pods in the default namespace cluster-admin, which means any pod running in the same namespace could manage any resource (including other namespaces) in the cluster...) in a recent blog post.

Over a year and no progress?


Conversion of SYM database fails if color field is used

If the SYM database contains an entry with a color field the conversion to another format fails.
E.g.
python -m cantools convert data/color_test.sym data/color_test.dbc
fails with the error message:
error: SYM: "Invalid syntax at line 9, column 7: "Color=>>!<<C67F43h""
color_test.sym.zip
FormatVersion=6.0 // Do not edit this line!
Title="ColorTest"

{SENDRECEIVE}

[ID_with_color]
ID=001h
Len=1
Color=C67F43h
Var=b1Test unsigned 0,1

I think that the HEXNUMBER regex is to restricted for using for parsing the color field.
Adding a separate regex for the color field should be fine: https://github.com/cantools/cantools/compare/master...miebka:cantools:fix-sym-db-with-color-field
If this proposal is fine for you, I'll start a PR.

Just Realized that this issue is the same as https://github.com/cantools/cantools/issues/458#issue-1315236005


flowzone: Support build metadata in semvers for device repositories

Device repositories use build meta-data so let's not remove it from the version used in versioning.
Validated in https://github.com/balena-os/balena-connectcore/pull/247

More review comments in zulip (internal)

@balena-ci I self-certify!


[MB-10958] Rename duty_station_names table to duty_location_names

Jira ticket for this change
Summary
This is a continuation of the effort to rename duty station to duty location everywhere.
I was mostly able to plagiarize @leia-sefkin's PR for renaming duty_locations.
To avoid any downtime, I created a view with the old table name that older versions of the code will be able to use.
I'm not leaving behind any code that references the old table name, so this view can safely deleted after this branch is deployed.
what does the duty_station_names table do?
This table has alternative names for duty locations that can be used in search boxes.
For example, we have a record in duty_locations for "JB Elmendorf-Richardson", which is sometimes abbreviated as "JBER".
So we've got a record in duty_location_names with the name JBER that points to the duty_locations record for "JB Elmendorf-Richardson".
If you type "JBER" into a duty location search box, the first result should be "JB Elmendorf-Richardson"
Setup to Run Your Code

testing instructions
Terminal 1
Make sure the migration works
make db_dev_reset
make db_dev_migrate

Terminal 2
Start the UI locally.
make client_run

Terminal 3
Start the Go server locally.
make server_run

Additional steps

Run through customer onboarding until you get to a duty location search box

Try a few searches. Make sure you don't get any errors, and try a few searches for things in duty_location_names to make sure that they come up right.

here are some examples:

search
expected result

Las Vegas Army Airfield
Nellis AFB

National Training Center
Fort Irwin

USARAK
Fort Wainwright

Verification Steps for Author
These are to be checked by the author.

[ ] Have the Jira acceptance criteria been met for this change?

Verification Steps for Reviewers
Database
Any new migrations/schema changes:

[ ] Follows our guidelines for Zero-Downtime Deploys
[ ] Have been communicated to #g-database
[ ] Secure migrations have been tested following the instructions in our docs

Messages

:book:
:link: MB-10958

  Generated by :no_entry_sign: dangerJS against 17e1adb3097bc8786a3e9873a5585629511daa04


username changing

right now its disabled in the auth UI. kratos supports its fine. hangar needs work.
maybe we can remove the owner name from the project table to make it easier?

lets keep owner name, its protected via a fkey
maybe a trigger can do that automagically?

Do we need anything more than an ON UPDATE CASCADE?


Filter pg query spans

I would like to be able to filter pg queries only to slow queries. Is this already possible to do?
I saw a related issue here: https://github.com/open-telemetry/opentelemetry-js-contrib/issues/499
Thanks!

I think it would be needed to implement a SpanProcessor and/or SpanExporter which does this instead of using that ones from SDK.

I agree I think a custom spanprocessor is likely the best place for this.

You could simply extend the standard batch processor and then add your logic into export function where you can check for those things and either export it or ignore it.

Thanks - will dig into this and close for now!


Weird git log parsing issue

Run on master in Node core:
$ changelog-maker --start-ref=66cb4bcf0 --end-ref=66cb4bcf0
* [[`66cb4bcf0c`](https://github.com/nodejs/node/commit/66cb4bcf0c)] - Event emitters support symbols as event names. The process object (cjihrig) [#4798](https://github.com/nodejs/node/pull/4798)

$ git log 66cb4bcf0c | head
commit 66cb4bcf0c032adc0f6abf7452150875c8a82243
Author: cjihrig<EMAIL_ADDRESS>Date:   Thu Jan 21 13:07:25 2016 -0500

    process: support symbol events

    Event emitters support symbols as event names. The process object
    assumes that the event name is a string, and examines the first
    three characters to check for signals. This causes an exception
    if the event name is a symbol. This commit ensures that the

i.e. it's not picking up process: support symbol events as the summary of this commit

@rvagg Want me to take a look or are you on it?

I noted it here cause I encountered it but don't have time to investigate, churning out releases atm.
the problem is likely in https://github.com/rvagg/commit-stream

Not sure if you're happy with that fix. It works though, but assumes that the PR-URL rows are not lower case.

all good, will figure out a compromise if it comes up again as not all-caps


Integrate ponzu with my existing Gin-Gonic framework

Hi, i would like to install Ponzu in my Golang with Gin-gonic framework for my CMS, is it possible ? Because when i see the structure of Ponzu, it seems like a different framework

Closing this issue. It appears to be answered/resolved. Please reopen if not the case.


Use GH actions instead of Travis

With this change, we are just changing the platform to run the tests before starting with major changes to better support newer Ruby versions. The next step will be to try again something like #240, ensuring that we support newer Ruby versions and dropping the support to EOL versions.

@olleolleolle Since you're the most active contributor around, I'd like to know your thoughts about this before merging it.


exclusion_labels cause panic

Describe the bug
The configure like this:

stack:

Expected behavior
start success
Actual behavior
panic
Steps to reproduce
Minimal yet complete reproducer code (or GitHub URL to code)
Environment

MOSN Version
latest

https://github.com/mosn/mosn/pull/2310


Add ton connect sdk

While the Tangem app already has wallet connect for etherium, which allows you to manage all of your crypto assets inside eth network, it would be nice to see ton connect feature. Toncoin is already on 11th place on CMC, yet you can’t perform basic actions such as Jetton transfers inside Tangem app.

Thank you for reaching out and for your suggestion! We would love to add support for TonConnect, but its implementation is a bit more complex compared to WalletConnect, mainly due to the lack of an SDK and the need to set up custom backend. However, we're keeping a close eye on developments, and it’s something we may consider in the future.


App hangs after trackEvent is called

Run the code below and the app won't exit after console.log()
var appInsights = require("applicationinsights");

var c = appInsights.getClient("key");
c.trackEvent('some event', {'version': 'foo'});
console.log('All done');

I suspect this is because it is waiting to send messages in background. If you force termination with "process.exit()", the messages will not be delivered.

Thanks @bragma that sounds correct. @PeterJausovec your use case sounds similar to @SofianHn's. We added a flag to the sender for "offline mode" which causes data to be written to disk in some cases instead of sent to the server. Enabling this might resolve your issue.
https://github.com/Microsoft/ApplicationInsights-node.js/blob/master/Library/Sender.ts#L35

I chatted with @BogdanBe a week or so ago and he mentioned the issue was a timer that was not being disposed, hence not ending the process.
The workaround for me was to call setAutoCollectPerformance(false);.

@PeterJausovec  This is similar to a problem with calling "dispose" manually (which I use in my tests). But I'll open another issue for that.

The app seems to be able to close if client.sendPendingData(); is called. This seems to be in line with the suspicion over waiting for sending.

I've verified that using sendPendingData addresses the OP's problem.
    var c = appInsights.getClient("key");
    c.trackEvent('some event', { 'version': 'foo' });
    c.sendPendingData();
    console.log('All done');


Fix metadata encoding

This should fix the encoding of metadata tags for #120

The only thing I am not sure about: Should we read keys as UTF8 as well? Usually tag keys are always ASCII, so I think that UTF8 is not needed there (and I assume that most formats do not support more than ASCII for keys, but that is just me guessing).

Isn't utf8 backwards compatible with ascii? Afaik, ascii characters in utf8 keep same bytes. I think utf8 would be the more incompasing encoding.

I think we should also encode parameters passed to ffmpeg as Utf8 (see latest changeset). Usually these will all be ASCII, but while we are at it, I'd clean this up as well.

Looks good!

Merged.


Missing type declaration files for the package

VS Code complains about missing type declaration files. The .d.ts files seem needed even if the package code contained JSDoc.

Fixed in v0.3.0 (without a PR).


iOS example not working

I've followed all the steps specified in this page https://github.com/socketio/socket.io-client-cpp/blob/master/examples/iOS/README.md
This is the output after running bash ./boost.sh https://www.dropbox.com/s/ccs2803tegro0t6/socket.io-client-cpp_iOS_ErrorLog.txt?dl=0
The specific error part is:
Framework: Building /Users/juan/Documents/sio/socket.io-client-cpp/examples/iOS/SioChatDemo/boost/osx/framework/boost.framework from /Users/juan/Documents/sio/socket.io-client-cpp/examples/iOS/SioChatDemo/boost/osx/build...
Framework: Setting up directories...
Framework: Creating symlinks...
Lipoing library into /Users/juan/Documents/sio/socket.io-client-cpp/examples/iOS/SioChatDemo/boost/osx/framework/boost.framework/Versions/A/boost...
fatal error: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/lipo: empty archive with no architecture specification: /Users/juan/Documents/sio/socket.io-client-cpp/examples/iOS/SioChatDemo/boost/osx/build/i386/libboost.a (can't determine architecture for it)

Aborted: Lipo /Users/juan/Documents/sio/socket.io-client-cpp/examples/iOS/SioChatDemo/boost/osx/framework failed

Do I have to install anything else to make this work?
I'm on a MacBook Pro with a recently installed OSX Yosemite (10.10.3) and xCode v6.3.2
Or is there any other way to get the libsioclient.a sio_client.h and sio_message.h files?
PD: I've tried to get help from https://socketio.slack.com/ but nobody would help
Thanks

Seems you're using a OSX framework for iOS target?

Hi,
I'm just following all the instructions on this page https://github.com/socketio/socket.io-client-cpp/blob/master/examples/iOS/README.md
Is there a setting I have to change somewhere? Or the script in that page are incorrect? Or do I have to install boost from another repository and then use it here?

The script works for me.
/Users/juan/Documents/sio/socket.io-client-cpp/examples/iOS/SioChatDemo/boost/osx/build/i386/libboost.a should be /Users/juan/Documents/sio/socket.io-client-cpp/examples/iOS/SioChatDemo/boost/ios/build/i386/libboost.a

I commented line 372 and now it completes without errors:
#buildFramework $OSXFRAMEWORKDIR $OSXBUILDDIR

Thanks @iglooJuan .


Empty TargetFramework breaks the build

I have the following content in my csproj
<PropertyGroup>
  <TargetFramework /> <!-- used to override the default value specified in Directory.Build.props -->
  <TargetFrameworks>netstandard2.0;net8.0</TargetFrameworks>
</PropertyGroup>

And the build is broken
10>------ Build started: Project: Extensions, Configuration: Debug Any CPU ------
10>C:\.nuget\packages\nugetizer\1.0.5\buildMultiTargeting\NuGetizer.targets(14,3): error MSB4020: The value "" of the "Project" attribute in element <Import> is invalid.
10>Done building project "Extensions.csproj" -- FAILED.

If I'll remove <TargetFramework /> then everything will work as expected. As being said, it's needed to override the default value that comes from Directory.Build.props.
BTW calling nugetize from the command line shows another error NuGetizer.targets(14,3): error MSB4020: ╨╖╨╜╨░╤З╨╡╨╜╨╕╨╡ "" ╨░╤В╤А╨╕╨▒╤Г╤В╨░ "Project" ╨▓ ╤Н╨╗╨╡╨╝╨╡╨╜╤В╨╡ <Import> ╨╜╨╡╨┤╨╛╨┐╤Г╤Б╤В╨╕╨╝╨╛., so it looks like errors in russian are not displayed correctly.

Closing for now since I couldn't repro. Please reopen if you can provide a reliable (and ideally isolated) repro.
Thanks!


pythonPackages.license-expression: fix build

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @kirelagin

Fixed!

[detached HEAD 82e1d6fc19b] pythonPackages.license-expression: fix build
Author: Yorick<EMAIL_ADDRESS>Date: Sat Sep 21 15:10:41 2019 +0200
1 file changed, 1 insertion(+)
Press Enter to continue
[detached HEAD 05f275f4510] pythonPackages.license-expression: make patchShebangs more specific
Author: Yorick<EMAIL_ADDRESS>Date: Mon Sep 23 13:50:31 2019 +0200
1 file changed, 1 insertion(+), 1 deletion(-)


remove CDeprecationWarning in context of celery 6.0.0

Description
This pull request removes the CDeprecationWarning of Celery that configuration variables will be changed with version 6.0.0 of celery.
CELERY_BROKER_URL -> removed
BROKER_URL -> broker_url
CELERY_ACCEPT_CONTENT -> accept_content
CELERY_RESULT_SERIALIZER -> result_serializer
CELERY_TASK_SERIALIZER -> task_serializer
This change made it necessary to modify the part where the configuration variables are added to the global configuration because it is no longer possible to search over variables starting with 'CELERY_'.
This change must also be made in invenio_app_rdm/config.py

see https://github.com/inveniosoftware/invenio-app-rdm/pull/1370


Unbreak dsniff by partially reverting a commit to libpcap

Motivation for this change
In current master, dsniff is broken. This is because in commit 34aff7f6973743a5e6e672c01016c4280d471453 we changed our libpcap package to no longer provide the static library libpcap.a.
This pull request reverts the addition of rm -f $out/lib/libpcap.a in the libpcap build, thereby unbreaking dsniff, but I'm not sure whether this is the right approach. @matthewbauer, perhaps you can comment on this? According to your commit message, you just wanted to strip more things. Perhaps the removal of the static library was in error?
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

We typically build static separately. If it is however being built already anyway, you could create a "static" output and move it there.

Thank you for your review, @FRidh! Indeed, the static library seems to be built anyway. I believe that multiple outputs are above my current paygrade.
I'm now using dontDisableStatic, and have dsniff override this attribute to true, in a similar fashion as with several other libraries dsniff depends on. Is that better?


Add: add docker compose config

Fixes #95.
Changes proposed in this pull request:
before we use docker compose, please install docker first : https://docs.docker.com/compose/install/
usage is as following :

access the docker folder (cd docker)

launch the environment by docker compose (docker-compose up -d)

access mysql / etcd / zookeeper as you want

if there is conflict on port, just modify the mapper port in docker-compose.yml and then launch docker compose again(docker-compose up -d)

if you want to stop these environment, use command docker-compose stop

to clean the docker container , you could use docker rm docker ps -a -q (be careful)

hi, i have reviewed, it's OK , thanks for contribution.


There is no certificate created yet

Hey guys, we tried to run nr1 nerdpack:serve but we got this error
There is no certificate created yet.
Error: An error ocurred while performing the operation
    at CallocService._buildRequest (/usr/local/lib/newrelic-cli/node_modules/@datanerd/3pp-cli-utils/src/ServiceFacade.js:149:23)

But I didn't find anything related, could you help us to fix this?
Thanks

@rv-vsilva have you created a profile first? this is not a cloud-optimize specific error, but something to do with the cli configuration.

Thanks! Yes... I'm trying to validate if the provided key is working. I will close the issue as this is not related.


PathIcon dont showing inside of Button or ListBoxItem

Describe the bug
Switching themes for testing, and appears a problem with the visibility of PathIcon in FluentAvalonia. In Avalonia.Fluent theme shows correctly, but not in FluentAvalonia. Tested inside a Button an a ListBoxItem. Using DevTools the PathIcon don even show. Using ListBoxItem I can check PathIcon is there after selecting in DevTools but in the interface is transparent. Changing Background and Foreground dont have any effect. Any workaround is welcome.
Screenshots

Expected behaviour

Desktop/Platform (please complete the following information):

OS: Windows 10
FluentAvalonia Version 2.0.0-preview4
Avalonia Version 11-preview4

Additional context
Add any other context about the problem here.

FluentAvalonia has it's own PathIcon. I think it was renamed to FAPathIcon now in order to be distinct from Avalonia. If you want to render Avalonias PathIcons, you have to add a Style on your own. The original can be found here: https://github.com/AvaloniaUI/Avalonia/blob/master/src/Avalonia.Themes.Fluent/Controls/PathIcon.xaml
@amwx do you want to add support for this control? If so, I can open a PR where I copy over the Style linked above.

You are right just tested before even read this comment. But I was trying to stick with the base PathIcon because this way I dont have to do any code change. Any way, the other thing stopping the use of this library was a performance problem I had with ItemPresenter some time ago and this already go away then I think is a good time to make a migration. I really like the hard work done in this. Feel free to close this issue if will stick with the internal FAPathIcon.

@amwx do you want to add support for this control? If so, I can open a PR where I copy over the Style linked above.

Because I have an alternative, let's leave it for now, but if demand grows for it then we can do that in the future.
@alex6dj
I'm not sure how FA was leading to perf issues with ItemsPresenter, but ItemsControls should be getting better in preview5 after that refactor. Also, if perf is an issue, you could looking into using IconSource over FAIconElement. The idea there is similar to flyouts where you can declare the icon once and use it everywhere, which is probably really useful for your case of using them in an ItemsControl, ex:
<UserControl.Resources>
    <ui:PathIconSource x:Key="DeleteIcon" Data="M..." />
</UserControl.Resources>

<!-- Usage -->
<Button>
    <ui:IconSourceElement IconSource="{StaticResource DeleteIcon}" />
</Button>

Will also move to discussion as this may be useful to others


Installation fails if the package contains '-'

Issue
The installation fails when the package contains a '-' character in the name. The following line of code causes it:
https://github.com/tox-dev/tox-uv/blob/main/src/tox_uv/_installer.py#L88
The error message I got:
Caused by: Package metadata name gooddata-sdk does not match given name gooddata
Environment
Provide at least:

OS: 14.2 (23C64)

Output of pip list of the host Python, where tox is installed
Package             Version
------------------- -------
cachetools          5.3.3
chardet             5.2.0
colorama            0.4.6
distlib             0.3.8
filelock            3.13.1
gooddata-api-client 1.14.0
gooddata-dbt        1.14.0
gooddata-pandas     1.14.0
gooddata-sdk        1.14.0
packaging           23.2
pip                 24.0
platformdirs        4.2.0
pluggy              1.4.0
pyproject-api       1.6.1
setuptools          69.1.1
tox                 4.14.0
tox-uv              1.5.0
uv                  0.1.15
virtualenv          20.25.1

PR welcome 😊

Can you please provide the full output of your error?  Now I think your build backend is generating an invalid wheel file name, so is a bug there - see https://peps.python.org/pep-0427/#escaping-and-unicode

I tried the new version – 1.5.1, and it works now. Thank you for the fix.