Draft_6455 flagged by Veracode CWE-331 replace Random with SecureRandom

Our veracode scan flagged usage of Random in Draft_6455.java as a vulnerability.
https://cwe.mitre.org/data/definitions/331.html
According to Websocket Protocol:
For example, each masking could be drawn from a cryptographically strong random number generator. If the same key is used or a decipherable pattern exists for how the next key is chosen, the attacker can send a message that, when masked, could appear to be an HTTP request (by taking the message the attacker wishes to see on the wire and masking it with the next masking key to be used, the masking key will effectively unmask the data when the client applies it).
According to this specification the library should be using SecureRandom to prevent brute force attacks.
Environment(please complete the following information):

Version used: 1.5.1
Java version: 1.8
Operating System and version: Android
Endpoint Name and version:
Link to your project:

Additional context
Add any other context about the problem here.

Can @TooTallNate delete this issue and open a security advisory?

@PhilipRoman I also tried to ping @TooTallNate but he did not respond yet.
The same issue was raised here but looking at the spec again I would not say that it is only used to defeat proxies.
The masking key is a 32-bit value chosen at random by the client. When preparing a masked frame, the client MUST pick a fresh masking key from the set of allowed 32-bit values. The masking key needs to be unpredictable; thus, the masking key MUST be derived from a strong source of entropy, and the masking key for a given frame MUST NOT make it simple for a server/proxy to predict the masking key for a subsequent frame. The unpredictability of the masking key is essential to prevent authors of malicious applications from selecting the bytes that appear on the wire.  RFC 4086 [RFC4086] discusses what entails a suitable source of entropy for security-sensitive applications.
What do you think?
Pushed #1133 with the change.
Best regards,
Marcel


Don't kill all processes when testing os.kill

Ticket
Resolves #117
Changes

Spin up test process to kill rather than using a random pid

Context for reviewers
@chouinar discovered this bug (see ticket description)
Testing
CI and also ran poetry run pytest (didn't address other test failures when running outside container, will look at those nest)

Oh yeah the security thing makes sense because I'm intentionally doing a bunch of weird things in order to test out the audit logging functionality. I think in the context of this file it's ok to ignore the security linting issues so I'll add some ignore statements in that file.


Contributors

This is issue to have a conversation with bot when you are lonely or you wanna manage the contributors. 🥂

@all-contributors please add @znut for code, documentation, test

@all-contributors please add @nickyshannon for code, review, test and please add @matmalkowski for review

@all-contributors please add @nickyshannon for code, review, test

@all-contributors please add @matmalkowski for review

@all-contributors please add @Nielsie for code,test

@all-contributors add @Nielsie for code,test

@all-contributors please add @Nielsie for code, test

@all-contributors please add @PoomSmart for code, doc, test, review

@all-contributors please add @dinujubd for code, test

@all-contributors please add @HasanAJ for code

@all-contributors please add @Ullidtz for code, test, doc

@all-contributors please add @kingdomax for code

@all-contributors please add @thammarith for doc


error: Command PhaseScriptExecution failed with a nonzero exit code (ios)

Description
During integration an error occurred with Sentry(https://scr.abz.agency/6quNZwqp) because two libraries were installed after the pod install command
After that we downgraded Sentry (React Native) and the conflicts disappeared
At the moment there is an error with launching the script
Tried to get rid of it this way:

We got rid of "EXCLUDED_ARCHS[sdk=*]" = arm64; in the main target and Reteno SDK
Executed pod deintegrate && pod cache clean --all && pod install (also considering M1 architecture arch -x86_64 ...)
Сhange values in the Architecture block (https://scr.abz.agency/6quNz4wz)
change values in Upload Debug Symbols to Sentry block (main target) and delete it (https://scr.abz.agency/v1uEOe8g)
Changed values in node_modules/react-native/scripts/find-node-for-xcode.sh on line 7 to set +e
In ios/.xcode.env for NODE_BINARY set path to Node.js (which node)

Version: 1.0.0
Output of npx react-native info
System:
    OS: macOS 12.6
    CPU: (8) arm64 Apple M1
    Memory: 455.86 MB / 16.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 16.15.0 - ~/.nvm/versions/node/v16.15.0/bin/node
    Yarn: 1.22.18 - ~/.nvm/versions/node/v16.15.0/bin/yarn
    npm: 8.5.5 - ~/.nvm/versions/node/v16.15.0/bin/npm
    Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
  Managers:
    CocoaPods: 1.11.3 - /opt/homebrew/bin/pod
  SDKs:
    iOS SDK:
      Platforms: DriverKit 21.4, iOS 16.0, macOS 12.3, tvOS 16.0, watchOS 9.0
    Android SDK: Not Found
  IDEs:
    Android Studio: 2021.3 AI-213.7172.25.2113.9014738
    Xcode: 14.0/14A309 - /usr/bin/xcodebuild
  Languages:
    Java: 11.0.15 - /usr/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: 18.1.0 => 18.1.0
    react-native: 0.70.6 => 0.70.6
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

Сode example, Screenshot

Screenshot of the current error https://scr.abz.agency/d5uyOWkR
Screenshot of the main targeting https://scr.abz.agency/rRu5OxdW
Example package.json

  "dependencies": {
    "@codler/react-native-keyboard-aware-scroll-view": "^2.0.0",
    "@eabdullazyanov/react-native-sms-user-consent": "^1.0.10",
    "@invertase/react-native-apple-authentication": "^2.2.2",
    "@miblanchard/react-native-slider": "^2.1.0",
    "@react-native-async-storage/async-storage": "^1.15.3",
    "@react-native-community/checkbox": "^0.5.13",
    "@react-native-community/clipboard": "^1.5.1",
    "@react-native-community/datetimepicker": "^6.3.1",
    "@react-native-community/masked-view": "^0.1.10",
    "@react-native-community/netinfo": "^6.0.0",
    "@react-native-community/push-notification-ios": "^1.10.1",
    "@react-native-firebase/app": "^16.4.6",
    "@react-native-firebase/dynamic-links": "^16.4.6",
    "@react-native-firebase/messaging": "^16.4.6",
    "@react-native-google-signin/google-signin": "^7.2.2",
    "@react-native-seoul/masonry-list": "^1.3.2",
    "@react-navigation/bottom-tabs": "^6.4.0",
    "@react-navigation/core": "^6.4.0",
    "@react-navigation/drawer": "^6.5.0",
    "@react-navigation/native": "^6.0.13",
    "@react-navigation/stack": "^6.3.4",
    "@sentry/react-native": "^4.7.1",
    "abortcontroller-polyfill": "^1.7.3",
    "babel-plugin-module-resolver": "^4.1.0",
    "formik": "^2.2.6",
    "jwt-decode": "^3.1.2",
    "lottie-react-native": "^5.1.4",
    "mixpanel-react-native": "^2.1.0",
    "moment": "^2.29.3",
    "parse-domain": "^3.0.3",
    "prop-types": "^15.7.2",
    "react": "18.1.0",
    "react-native": "0.70.6",
    "react-native-android-open-settings": "^1.3.0",
    "react-native-appsflyer": "^6.3.20",
    "react-native-circular-progress": "^1.3.7",
    "react-native-device-info": "^8.1.3",
    "react-native-dotenv": "^3.3.1",
    "react-native-element-dropdown": "^1.8.10",
    "react-native-fast-image": "^8.6.3",
    "react-native-fbsdk-next": "^11.1.0",
    "react-native-gesture-handler": "^2.8.0",
    "react-native-get-random-values": "^1.8.0",
    "react-native-googleanalytics": "^1.0.0",
    "react-native-highlight-overlay": "^1.3.0",
    "react-native-iphone-x-helper": "^1.3.1",
    "react-native-keyboard-aware-scroll-view": "^0.9.5",
    "react-native-linear-gradient": "^2.5.6",
    "react-native-play-install-referrer": "^1.1.7",
    "react-native-progress": "^5.0.0",
    "react-native-push-notification": "^8.1.1",
    "react-native-reanimated": "^2.13.0",
    "react-native-responsive-screen": "^1.4.2",
    "react-native-safe-area-context": "^3.2.0",
    "react-native-screens": "^3.1.1",
    "react-native-scroll-into-view": "^2.0.2",
    "react-native-share-menu": "^6.0.0",
    "react-native-shared-group-preferences": "^1.1.23",
    "react-native-snap-carousel": "^3.9.1",
    "react-native-splash-screen": "^3.2.0",
    "react-native-svg": "^12.1.1",
    "react-native-svg-transformer": "^0.14.3",
    "react-native-swipe-gestures": "^1.0.5",
    "react-native-toast-message": "^2.1.5",
    "react-native-url-polyfill": "^1.3.0",
    "react-native-uuid": "^2.0.1",
    "react-native-video": "^5.1.1",
    "react-native-webview": "^11.26.0",
    "react-translate": "^7.0.1",
    "reteno-react-native-sdk": "^1.0.0",
    "smartlook-react-native-wrapper": "^1.2.8",
    "uuid": "^9.0.0",
    "yup": "^0.32.11",
    "yup-phone": "^1.3.2"
  },
  "devDependencies": {
    "@babel/core": "^7.8.4",
    "@babel/runtime": "^7.8.4",
    "@react-native-community/eslint-config": "^1.1.0",
    "avo": "^3.2.2",
    "babel-jest": "^25.1.0",
    "deprecated-react-native-prop-types": "^2.3.0",
    "eslint": "^7.32.0",
    "eslint-config-prettier": "^8.5.0",
    "eslint-plugin-react": "^7.23.2",
    "jest": "^25.1.0",
    "jetifier": "^2.0.0",
    "metro-react-native-babel-preset": "0.72.3",
    "patch-package": "^6.5.0",
    "prettier": "2.6.2",
    "react-native-codegen": "^0.72.0",
    "react-test-renderer": "18.1.0"
  },

Hello @abz-denys-z
Thank you for contacting.
I've created test project with your dependencies from package.json, and for now I can not reproduce your issue.
Could you please help me a little bit here:

Can you please provide your Podfile dependencies in comments?
On which phase script do you have this PhaseScriptExecution error? Is it Bundle React Native code and images or something else?

Can you please provide your Podfile dependencies in comments?

require_relative '../node_modules/react-native/scripts/react_native_pods'
require_relative '../node_modules/@react-native-community/cli-platform-ios/native_modules'
platform :ios, '12.4'
install! 'cocoapods', :deterministic_uuids => false
use_frameworks! :linkage => :static

target 'matin_target' do
  config = use_native_modules!
  # Flags change depending on the env values.
  flags = get_default_flags()
  pod 'Firebase', :modular_headers => true
  pod 'FirebaseCore', :modular_headers => true
  pod 'GoogleUtilities', :modular_headers => true
  pod 'Reteno', '1.3.0'
  $RNFirebaseAsStaticFramework = true

  use_react_native!(
    :path => config[:reactNativePath],
    # Hermes is now enabled by default. Disable by setting this flag to false.
    # Upcoming versions of React Native may rely on get_default_flags(), but
    # we make it explicit here to aid in the React Native upgrade process.
    :hermes_enabled => true,
    :fabric_enabled => flags[:fabric_enabled],
    # Enables Flipper.
    #
    # Note that if you have use_frameworks! enabled, Flipper will not work and
    # you should disable the next line.
#     :flipper_configuration => FlipperConfiguration.enabled(["Debug"]),
    # An absolute path to your application root.
    :app_path => "#{Pod::Config.instance.installation_root}/.."
  )
  pod 'react-native-splash-screen', :path => '../node_modules/react-native-splash-screen'
  target 'targetTests' do
    inherit! :complete
    # Pods for testing
  end

#   use_flipper!({ 'Flipper' => '0.125.0', 'Flipper-Folly' => '2.6.10', 'Flipper-RSocket' => '1.4.3' })
  post_install do |installer|
    react_native_post_install(
      installer,
      # Set `mac_catalyst_enabled` to `true` in order to apply patches
      # necessary for Mac Catalyst builds
      :mac_catalyst_enabled => false
    )
    installer.pods_project.targets.each do |target|
          target.build_configurations.each do |config|
            config.build_settings['APPLICATION_EXTENSION_API_ONLY'] = 'NO'
#             config.build_settings['ONLY_ACTIVE_ARCH'] = 'YES'
#             config.build_settings['SDKROOT'] = 'iphoneos'
#             config.build_settings["EXCLUDED_ARCHS[sdk=iphonesimulator*]"] = "arm64"
          end
        end
    __apply_Xcode_12_5_M1_post_install_workaround(installer)
  end
end

target 'share' do
  use_react_native!(:hermes_enabled => true)

  pod 'RNShareMenu', :path => '../node_modules/react-native-share-menu'
  # Manually link packages here to keep your extension bundle size minimal
end

target 'notificationsReteno' do
  pod 'Reteno', '1.3.0'
end

On which phase script do you have this PhaseScriptExecution error? Is it Bundle React Native code and images or something else?

If I understand correctly, I can check here (https://scr.abz.agency/8Lug0Lnk)
If so, the same state for the Run command
@valentynhalkinreteno I hope this helps you to reproduce my mistake too

@valentynhalkinreteno Also perhaps useful, I went by the documentation name AppDelegate.mm

@valentynhalkinreteno The reason seems to be that it can't find the Node when the application starts (https://scr.abz.agency/X6u5Rmk1)
After running the command
ln -s $(which node) /usr/local/bin/node
The error did not go away (https://scr.abz.agency/QwujnNx6)
Strange that there were no similar errors before
Example code in the Bundle React Native code and images block
export SENTRY_PROPERTIES=sentry.properties
export EXTRA_PACKAGER_ARGS="--sourcemap-output $DERIVED_FILE_DIR/main.jsbundle.map"

set -e

WITH_ENVIRONMENT="../node_modules/react-native/scripts/xcode/with-environment.sh"
../node_modules/@sentry/cli/bin/sentry-cli react-native xcode
  REACT_NATIVE_XCODE="../node_modules/react-native/scripts/react-native-xcode.sh"

/bin/sh -c "$WITH_ENVIRONMENT $REACT_NATIVE_XCODE"

/bin/sh<EMAIL_ADDRESS>


Greek test data contains ambiguous sentence

The Greek test data contains the following sentence:
https://github.com/pemistahl/lingua/blob/7e415ae84f16bc881c6731a69b1bac1b7d6ce013/src/accuracyReport/resources/language-testdata/sentences/el.txt#L768
The sentence is rather short and half of it is English, so personally I don't think it is that useful for the accuracy report.
In fact Lingua does not seem to be certain about the language either: If you look at the history of the accuracy report you will see that it changed multiple times from ~100% to < 100% with English being detected. The underlying cause for these inconsistent results is that HashMaps are used with Enums as key, but that might be worth a separate issue.

I changed the algorithms multiple times during this time period, so I rather think that this is the cause of the changing accuracy values. Enums as keys for maps do not pose any problems. Why should they? Enums are hashable, so I always get the same value in return for the same key.

Actually this is not so problematic so feel free to close this issue, the point was that this specific sentence does not add much value, or rather that it might be somewhat questionable to consider this as Greek.

Enums as keys for maps do not pose any problems. Why should they? Enums are hashable, so I always get the same value in return for the same key.

I was not aware of this either, but they actually inherit Object.hashCode() and therefore their hash value is arbitrary (accross multiple runs), see also this StackOverflow question. Maybe you are right and some of the accuracy changes came from other refactoring, but when you run the accuracy tests repeatedly without any changes you will notice accuracy report differences (though not guaranteed, you might need multiple tries).

The sentences used as test data are randomly extracted from the corpus so it is possible that ambiguous sentences are chosen. But the number of these sentences is not statistically significant, so I don't care. But now I've replaced all hash maps with those that preserve insertion order, just to be sure that they were not the cause for the accuracy changes you mentioned. With that being said, I'm closing this issue now.


tc.js uses different interfaces for up and down

For  down is calls tc with "ifb0": https://github.com/sitespeedio/throttle/blob/master/lib/tc.js#L61
For upd it calls tc with iFace: https://github.com/sitespeedio/throttle/blob/master/lib/tc.js#L76

It's a bug, right?

Yeah, this  looks strange, and I guess it will not work if you are not using ifb0 then? I think this was ported directly from the  settings from WPT. Let me have look before I release the next version.


External storage is not available.

External browser (inner SD) shows empty list when browsing for files

What is the path to your inner SD?


gather-logs fails when bzip2 is not installed

Expected Behavior
chef-server-ctl gather-logs should produce a .tar.bz2 of the log files
Current Behavior
On systems without bzip2 installed,  chef-server-ctl gather-logs fails.
chef-server-ctl gather-logs
tar (child): bzip2: Cannot exec: No such file or directory
tar (child): Error is not recoverable: exiting now

Steps to Reproduce (for bugs)
(RHEL)

rpm -e bzip2
chef-server-ctl gather-logs

Your Environment

Chef Server Version: chef-server-core-12.17.15-1.el7.x86_64
Operating System and Version: RHEL 7

This was fixed in 2019


How to search podcast episodes of a particular episode?

Is your feature request related to a problem? Please describe.
Wonderful work, thank you!

How could one search for all episodes containing substrings: self-hosted in the podcast: Hacker Public Radio? (In generalised format, so different substrings for different podcasts).
how could one search all episodes in Spotify matching substring: pizza, and sort them on date?
Would it be possible to export the search results as a playlist (sorted on episode publishing date)?
Would it be possible to download the search result as a playlist (sorted on episode publishing date)?

Please note, these are quite some questions and no is a perfectly fine answer :)
Describe the solution you'd like
An instruction on how to do something like:
python -m spotify_dlx --episodes `self-hosting AND collabora` sort:date_ascending export:playlist

And/or
python -m spotify_dlx --episodes `self-hosting AND collabora` sort:date_ascending export:download

Describe alternatives you've considered
I tried running an arbitrary search command for self-hosted,  yet did not find any episodes listed.
Additional context
My main concern is being able to transparently query the Spotify database (without nudging).
Once again, thank you for making such a nice CLI!
Ps. I thought perhaps these links might be relevant for obtaining the spotify database (segments):
https://machinelearningknowledge.ai/tutorial-how-to-use-spotipy-api-to-scrape-spotify-data/
https://spotifyscraper.readthedocs.io/en/latest/

@a-t-0 Thank you for the good issue.
Let me check it out. I'm going to reply by the end of this month.

Any progress on this? I'm currently working on a tool to transcribe podcast episodes and want to add functionality to download spotify podcasts. As far as I understand this package uses librespot to stream audio is that correct? Let me know if I can help, I'd gladly submit a pull request!

@benearnthof for completeness, I did not pickup work on this issue, nor do I expect to in the near future, so if you are able to send a pull request with the feature, I would greatly appreciate it!


Normalize to HTTPS protocol

We don't have any option to get https... protocol if we didn't pass it. Only if your inout will start with https://example.com you could get output with https. Also I want to discuss about making it default to support security in web, so people still use unsafety  way they will have to do more setup, by that way we will force them to use https .

Make WEB safe again.

I too wish we could just default to normalizing to HTTPS, but that would not work in practice as http always works, but a lot of URLs don't work when using https.
What's your use-case for wanting it to normalize to https?

I was using that generator for project, There is asked for my web-page url. I inputed example.com and after I created I found my package.json has http://example.com. But I has https. So I decided to open PR to fix it. After I saw that it using that module I came here but I didn't found any option for that. SO that fix help me to fix another fix =)

Ok. I guess we could add a normalizeHttp method which would be mutually exclusive to normalizeHttps.


Add tmp db devices

Description
Return the tmp endpoint to validate device db info that is not returning correctly
Fixes # (issue)
Type of change
What is it?

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Documentation update
[ ] Tests update
[ ] Refactor

Checklist:

[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] I run go fmt ./... to check that my code is properly formatted
[ ] I run go vet ./... to check that my code is free of common Go style mistakes

/retest

/retest

/retest

Codecov Report

Merging #761 (f3eff4d) into main (df9b471) will decrease coverage by 0.01%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #761      +/-   ##
==========================================
- Coverage   31.44%   31.42%   -0.02%
==========================================
  Files          44       44
  Lines        4704     4706       +2
==========================================
  Hits         1479     1479
- Misses       3023     3025       +2
  Partials      202      202

Impacted Files
Coverage Δ

pkg/routes/devicegroups.go
39.13% <0.00%> (-0.25%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update df9b471...f3eff4d. Read the comment docs.


Please add a screen shot

I'd like to add this to awesome-zsh-plugins, but I prefer to add themes with screen shots so that users can see what they look like without having to install them.
Thanks!

I will add one in the next commit.

Cool, thanks. Let me know when you're ready for it to be added by closing this issue or making a PR on  awesome-zsh-plugins

I hope the last commit, fix this issue.

Adding in https://github.com/unixorn/awesome-zsh-plugins/pull/1685

Ok, thanks!


Skip ahead to future rounds when justified

Implement a rebroadcast protocol improvement where upon receiving sufficient justification a participant jumps ahead to future rounds. Justification from a future rounds is considered sufficient when the participant receives:

at least one CONVERGE message, and
a weak quorum of PREPARE messages

for that round.
Fixes #241

Codecov Report
Attention: Patch coverage is 48.00000% with 13 lines in your changes are missing coverage. Please review.

Project coverage is 71.85%. Comparing base (add8260) to head (b242e35).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #276      +/-   ##
==========================================
- Coverage   72.00%   71.85%   -0.16%
==========================================
  Files          32       32
  Lines        2390     2405      +15
==========================================
+ Hits         1721     1728       +7
- Misses        537      544       +7
- Partials      132      133       +1

Files
Coverage Δ

gpbft/gpbft.go
83.46% <48.00%> (-0.91%)
:arrow_down:

@anorth I would love your early feedback on this please to confirm that I am on the right track. Reading the latest FIP I am infering my way around the rebroadcast changes, specifically around beginNextRound and how it overlaps with skipToRound.

@anorth this PR is ready for review. I believe to test that skip rounds functions correctly we need the rest of rebroadcast implementation. Please let me know if I have missed anything or there are tests that you would like to see done as part of this PR.  Otherwise, my vote would be to revisit the testing after rebroadcast is implemented.


Router Refactoring + Nested Routing Support (Tab Routes)

This pull request contains all of the commits that my previous pull request had, plus additional commits for tab routes, so I closed the last one.
Building on the event-driven routing system I added in the previous pull request, tabs now listen for route changes and update themselves appropriately. I also made some more changes to the routing code. The biggest change is that rather than extending the findMatchingRoute and parseRoutes functions with non-trivial nested route logic, I thought we could use universal-router for our route resolution logic so we don't have to re-invent the wheel. universal-router is pretty small and focused on route resolution. It seems to be growing in popularity and is designed to be used in place of both vue-router and react-router. Let me know if you don't like universal-router and want to keep and extend the existing routing code instead. All of the functionality that the previous routing code had (hashes, query strings, etc.) are still supported.
I have pulled all of these changes into Framework7 React, and as you can see in the kitchen sink, nested routing (and routing in general) works just fine. Framework7 React no longer has duplicate code for routing and no longer has duplicate Pages and View components. Every single component in Framework7 React is now a converted Vue component.
#38

@nolimits4web , I think I might need some clarification about scenarios for going back.
The current code has this:
if (options.isBack) {
  view.router.back(options);
}

However, I'm not entirely sure how that code would ever be reached because of this code that happens before that:
if (url && pageElement || !url || url === '#') {
  return true;
}

Normally, back buttons will have a URL of '#', and I'm not sure how it would work if they had a different URL. Can you clarify?
I would actually like to have the ability for back buttons to have another URL besides '#' and automatically animate a back transition to the page for that URL rather than just going back to whatever the previous page in the history is. Maybe that already works and I'm just not aware of it.
However, if going back to another URL doesn't work yet, then I should probably strip out the extra code for calling view.router.back for now.


Make sure that users use an API key to download the URDF

Users should be required to provide an API key to download a URDF

actually, i don't think this is that important


fix: long knowledge gets cutoff

Closes #139

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


BUG: Token list doesn't show crvUSD or 3crv on the EurE Offramp Bot. Please check all bots.

BUG: Token list doesn't show crvUSD or 3crv on the EurE Offramp Bot. Please check all bots. Able to reproduce. Token 3crv does not show up in token list for Palomabot or Curvebot. It shows up for Palomaswap.
List of Bots that fail to show crvUSD or 3CRV
https://www.curvebot.fi/curve-leverage-lending/
https://www.palomabot.ai/euros/
https://www.curvebot.fi/curve-limit-order/
https://www.curvebot.fi/curve-stop-loss/
https://www.curvebot.fi/curve-lending/
https://www.curvebot.fi/curve-momentum/bot
https://www.palomabot.ai/uniswapv3-twap/

Fixed with https://github.com/VolumeFi/palomabot/pull/339

@jamie088 ticket updated.

Fixed with https://github.com/VolumeFi/palomabot/pull/341


Dynamic component type feature

Issue: #64
I added dynamic identifiers for the components in addition of the original type identifiers, while keeping the interface of World and EntityBuilder backwards compatible.
The both identifiers are equal, so that there can be multiple components with the same dynamic id but different type id.
(I also added a simple test case for the feature)

@csherratt want to review it?
I've taken a look, fine with that as long as it doesn't break the existing API.

Looks ok to me. But this may need to be tweaked in a follow up change. The problem being that if you want to use string names for component_ids you will end up doing a clone() of the strings to fetch anything. Might not be the end of the world.
This is a breaking change. The break is pretty small, just World => World<()> but it is still a breaking change.


New Relic monitoring

Seems like a better fit than DataDog.
https://docs.newrelic.com/docs/alerts-applied-intelligence/new-relic-alerts/learn-alerts/introduction-alerts/
https://docs.newrelic.com/docs/accounts/install-new-relic/partner-based-installation/heroku-install-new-relic-add/#heroku-nodejs
https://docs.newrelic.com/docs/apm/agents/nodejs-agent/hosting-services/nodejs-agent-heroku/
https://elements.heroku.com/addons/newrelic#pricing
https://docs.newrelic.com/docs/apm/agents/nodejs-agent/hosting-services/nodejs-agent-heroku/#variables
https://docs.newrelic.com/docs/apm/agents/nodejs-agent/extend-your-instrumentation/nodejs-custom-metrics/#example

Using the api seems a lot simpler than figuring out how to use their integrations:
https://docs.newrelic.com/docs/logs/log-api/introduction-log-api/
https://docs.newrelic.com/docs/data-apis/ingest-apis/metric-api/report-metrics-metric-api/


Only send changed accounts to listeners

After implementing a provider for this interface, I found that the deleted type of account diff was not needed since deleted is basically equivalent to notifying subscribed txpools that the account's new nonce and balance is 0.

That makes sense, actually. For internal representation we could equate non-existent accounts to those with zero nonce/zero balance.


add a date input to Template schema and Entities form

Description
Feature
Wanted to open this to drop some thoughts...
This adds a Date input that submits a string like "2020-04-21" to the JSON data schema. Question: Should it be a string or do we/can we cast it to date before saving?
If it had Date and Time components, it would be fairly critical that it gets cast to a datetime with appropriate timezone information... for certain data needs, at least.
As "just a date", you can imagine it more broadly doesn't get altered for timezones. For instance, it could be a birthday. Your birthday doesn't change dependant on your location.
So maybe we have this Date field... as is... and we also have:

a Time field that... does not? have timezone information?
a DateTime field that absolutely does have timezone information.

Date = Birthdays, annual holidays, that sort of thing - no TZ info
Time = Routine... I guess? - no TZ info
DateTime = Very specific event setting - yes, TZ info
Checklist

[x] I have read the Contributing Guide and Code of Conduct

The question then is... how?
Casting to a datetime with timezone information... to be saved as UTC and converted back to user time at retrieval...
Time to start looking at those Content Entry validations: app/models/concerns/content_entry_validator.rb

Be aware of JSON primitive types. JSON only understands string, number, boolean and null, and our app will discard the nulls (this is fine - Postgres doesn't support them).
So for dates and times, you can opt for STRING or NUMBER.
String Options

ISO 8601

Number Options

UNIX Time

## ISO 8601 Looks Like the Way to Go
I'm leaning in favour of ISO 8601 because it can be sorted alphabetically and supports dates between 0000-01-01 and 9999-12-31. It can also be expanded... which is... interesting...

To represent years before 0000 or after 9999, the standard also permits the expansion of the year representation but only by prior agreement between the sender and the receiver.[20] An expanded year representation [±YYYYY] must have an agreed-upon number of extra year digits beyond the four-digit minimum, and it must be prefixed with a + or − sign[21] instead of the more common AD/BC (or CE/BCE) notation; by convention 1 BC is labelled +0000, 2 BC is labeled −0001, and so on

Of note: only by prior agreement between the sender and the receiver
Meaning a range of -99999-01-01 to +99999-12-31 could be supported. Greater even, with additional digits. Applications for this include documenting ancient history, predictions about the distant future, fantasy and sci-fi settings...
...but it would need to be an advanced option. I mean something that the user specifically sets up, so that they - as the sending and receiving party - know what data to expect.
The default should remain 0000-01-01 to 9999-12-31, the standard ISO 8601 format.
Also... sorting must break for formats which include - and +, right? A quick test in a Ruby console indicates that '+' will always be sorted before '-' alphabetically (incorrect for purpose), and indeed BC or negative dates are ordered most recent to most distant (incorrect for purpose). That's a problem: Negative dates break sorting Something to be aware of if ever expanding to support that.
Also note, Postgres' native datetime and date formats support dates between 4,713 BC and 294,276 AD, and 4,713 BC and 5,874,897 AD respectively. I have no idea why.
For more info, including YYYY-MM and --MM-DD support, see: https://en.wikipedia.org/wiki/ISO_8601#Dates

Opened for Review
Go ahead and add compatible fields. Date is easily queried anyway; I've limited the min and max to acceptable values anyway - alphabetical sorting is immediately fit for purpose.
Will think on more advanced querying in a later issue.


Update markdownit references

@nuxt/markdownit was broken so I updated these references to @nuxtjs/markdownit

Summary

Test plan

A picture of a cute animal (not mandatory but encouraged)

Thanks!


[experiment] Add tmate on failure.

[ ] Closes #xxxx
[ ] Tests added / passed
[ ] Passes pre-commit run --all-files

@jrbourbeau Thanks, yes, that's exactly what I used, but tmate server seems to be having problems, so it didn't help a whole lot.


chore(docs): custom and built-in event logging class at the same time

SUMMARY

There was lack of documentation for using built-in DB based event logger along with custom JSON logger so I've added that.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

[x] Has associated issue: https://github.com/apache/superset/issues/15548
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

Thanks for this contribution @wiktor2200. In the interest of keeping the documentation as compact and to-the-point as possible, I'm unsure if we need to document how to extend the DBEventLogger (most Superset admins should know this). However, it could be a good idea to mention in the docs that when using a custom event logger, events will no longer be populated in the logs table, and that one will need to extend the DBEventLogger class to do this.
Ping @srinify for thoughts on this?

I totally agree, it's not rocket science to add it, but it's worth to mention that using custom will stop logging to logs table and info that it could be quite easily added.

Hi @villebro! I've updated this doc file as you suggested. Removed additional part, leaving only notice about running custom classes simultaneously. Please take a look.


Add health status endpoint

Close #96
ping @erikschul @fmierlo
This adds an argument --info/-i which specifies an address and port (e.g. localhost:9080), which exposes a HTTP server that provides health status metric of the server.
Currently two endpoints are implemented:
/metrics: Exposes information of the wireguard daemon, this provides the same information you would get with wg show. This shows an example of what the response would look like.
/readyz: This responds with a json which shows the last time a pong is received from an IP specified with CheckAlive. When CheckAlive is set, a ping is sent out to addresses in CheckAlive per CheckAliveInterval seconds (defaults to 5) via wireguard. If a pong has not been received from one of the addresses within the last CheckAliveInterval seconds (+2 seconds for some leeway to account for latency), then it would respond with a 503, otherwise a 200.
For example:
[Interface]
PrivateKey = censored
Address = <IP_ADDRESS>/32
DNS = <IP_ADDRESS>
CheckAlive = <IP_ADDRESS>, <IP_ADDRESS>
CheckAlive = 3

[Peer]
PublicKey = censored
AllowedIPs = <IP_ADDRESS>/0
Endpoint = <IP_ADDRESS>:51820

[Socks5]
BindAddress = <IP_ADDRESS>:25344

/readyz would respond with
< HTTP/1.1 503 Service Unavailable
< Date: Thu, 11 Apr 2024 00:54:59 GMT
< Content-Length: 35
< Content-Type: text/plain; charset=utf-8
<
{"<IP_ADDRESS>":1712796899,"<IP_ADDRESS>":0}

And for:
[Interface]
PrivateKey = censored
Address = <IP_ADDRESS>/32
DNS = <IP_ADDRESS>
CheckAlive = <IP_ADDRESS>

/readyz would respond with
< HTTP/1.1 200 OK
< Date: Thu, 11 Apr 2024 00:56:21 GMT
< Content-Length: 23
< Content-Type: text/plain; charset=utf-8
<
{"<IP_ADDRESS>":1712796979}

If nothing is set for CheckAlive, an empty JSON object with 200 will be the response.
The peer which the ICMP ping packet is routed to depends on the AllowedIPs set for each peers.

Looks good!
for
CheckAlive = 3

I assume you meant
CheckAliveInterval = 3


No module named 'logmod'

Here it is:
Original exception was:
Traceback (most recent call last):
  File "http.py", line 1, in <module>
    import diesel
  File "/usr/local/lib/python3.4/dist-packages/diesel/__init__.py", line 2, in <module>
    from logmod import log, levels as loglevels, set_log_level
ImportError: No module named 'logmod'

This error
Steps to reproduce (uses one of the examples from the Diesel website:
sudo pip3 install diesel
git clone https://gist.github.com/39dad2b6500837a7e834.git
cd 39dad2b6500837a7e834
python3 dieseltest.py

Please feel free to ask if I can help fixing this issue or if you need any additional info!

Here it is:
Original exception was:
Traceback (most recent call last):
  File "http.py", line 1, in <module>
    import diesel
  File "/usr/local/lib/python3.4/dist-packages/diesel/__init__.py", line 2, in <module>
    from logmod import log, levels as loglevels, set_log_level
ImportError: No module named 'logmod'

This error
Steps to reproduce (uses one of the examples from the Diesel website:
sudo pip3 install diesel
git clone https://gist.github.com/39dad2b6500837a7e834.git
cd 39dad2b6500837a7e834
python3 dieseltest.py

Please feel free to ask if I can help fixing this issue or if you need any additional info!

Ah, looks like you're running on Python 3. diesel 3.x doesn't support Python 3.
It's not all bad news though - I'm doing some work in a diesel4 branch and will be targeting Python 3 support there. I think @msabramo has done some work toward Python 3 compatibility and I hope to incorporate that.

Closing this in favor of #97. We'll track Python 3 support there.


Make ignored dependent configuration warnings consistent between CLI options and TOML config

Description
Dependent options specified on the command line will trigger warnings, while the same options specified in a TOML file don't.
For example:
WARN  | Besu | --min-gas-price has been ignored because --miner-enabled was not defined on the command line.
^ This message is displayed when the CLI options are misconfigured, but not when the same configuration is used in a TOML file.
It likely affects CLI options being verified in CommandLineUtils, which may include:

GraphQL options
Metrics options
Mining options
P2P options
PrivacyParameters
Privacy TLS
RPC options
Sync options

Acceptance Criteria
Warnings for ignored options will be displayed when using both CLI options and TOML configuration.

This line - when using toml the stringValues() method returns an empty collection but when on command line it has the expected value for the given option.
https://github.com/hyperledger/besu/blob/master/besu/src/main/java/org/hyperledger/besu/cli/util/CommandLineUtils.java#L102


Shuffle

Is shuffle going to be at the end of each round (if it's going to be done in that instance?)

The shuffle will be done every n rounds, n still undecided. However, there is no guarantee for n to remain consistent. This means you will only know that we are adding the old cards back into the deck and shuffling when 'SHUFFLE' is broadcasted

Shuffling now set to: n% chance after each round + guaranteed shuffle if their aren't a minimum of  m cards per player in the deck.

Values are still undecided, but currently:
n = 20%
m = 21


[GNB] Gnashing Fang into Continuation does not appear to function

As of <IP_ADDRESS>, Gnashing Fang -> Continuation does not appear to be functional. I believe this was intended to be fixed by #195.
I am seeing the same issue as the previous. I expect Gnashing Fang to switch to the appropriate Continuation, but this does not seem to happen.
WrathDebug.txt
Edit to add: Every other continuation option (Burst Strike > Hypervelocity, Fated Circle > Fated Brand) works correctly. It's just GF that doesn't.

@Akechi-kun any idea?


Logout page ng-model doesn't have Click To Here Visible for redirect to application

This is what i get as a logout page.

Everything is empty here. in model

Dup of the issue you also opened in IdentityServer.


[Integration]Services trail dynamic chart

What is the integration resource ?
A new Services trail dynamic-chart widget (visualization) is needed to add the capability for showing a clear and interactive visualization of the services-trails transaction breakdown
This widget will take the partial services-network graph that describes the specific interaction of the spans within a single trace transaction
The new Traces Gantt-chart widget widget should be:

UX appealing
Aware of external dashboard filters (such as time , attributes)
Easy to configure by customers

What is the integration source protocol ?

Data-Prepper's otel-v1-apm-span-* index containing the services span info
Data-Prepper's otel-v1-apm-service-map index containing the services relations info

Which agents would you use to ship this data ?

Data prepper exporter
Jaeger exporter

Which Dashboards would you be using ?
This is a vega-visualization component that is both configurable and agile for updates without any code changes
https://github.com/opensearch-project/opensearch-catalog/assets/48943349/4da96637-8923-4707-9d2d-a767f699089a

done - these are the ndjson flow assets


Error while launching the language server

I have followed the Development Setup,
pnpm install
pnpm run build

But I have encountered several errors:
extension\src\index.ts → extension/dist/extension/index.browser.js...
> node_modules/.pnpm/minimatch@3.1.2/node_modules/minimatch/minimatch.js:4:47: error: Plugin "rollup" returned a non-absolute path: path (set a namespace if this is not a file path)
4 │ var path = (function () { try { return require('path') } catch (e) {}}()) || {
╵                                                ~~~~~~

[!] (plugin esbuild) Error: Build failed with 1 error:
node_modules/.pnpm/minimatch@3.1.2/node_modules/minimatch/minimatch.js:4:47: error: Plugin "rollup" returned a non-absolute path: path (set a namespace if this is not a file path)
Error: Build failed with 1 error:
node_modules/.pnpm/minimatch@3.1.2/node_modules/minimatch/minimatch.js:4:47: error: Plugin "rollup" returned a non-absolute path: path (set a namespace if this is not a file path)
at failureErrorWithLog (C:\Users\xxx\Downloads\workspace\grammarly\node_modules\.pnpm\esbuild@0.12.29\node_modules\esbuild\lib\main.js:1475:15)
at C:\Users\xxx\Downloads\workspace\grammarly\node_modules\.pnpm\esbuild@0.12.29\node_modules\esbuild\lib\main.js:1133:28
at runOnEndCallbacks (C:\Users\xxx\Downloads\workspace\grammarly\node_modules\.pnpm\esbuild@0.12.29\node_modules\esbuild\lib\main.js:923:63)
at buildResponseToResult (C:\Users\xxx\Downloads\workspace\grammarly\node_modules\.pnpm\esbuild@0.12.29\node_modules\esbuild\lib\main.js:1131:7)
at C:\Users\xxx\Downloads\workspace\grammarly\node_modules\.pnpm\esbuild@0.12.29\node_modules\esbuild\lib\main.js:1240:14
at C:\Users\xxx\Downloads\workspace\grammarly\node_modules\.pnpm\esbuild@0.12.29\node_modules\esbuild\lib\main.js:611:9
at handleIncomingPacket (C:\Users\xxx\Downloads\workspace\grammarly\node_modules\.pnpm\esbuild@0.12.29\node_modules\esbuild\lib\main.js:708:9)
at Socket.readFromStdout (C:\Users\xxx\Downloads\workspace\grammarly\node_modules\.pnpm\esbuild@0.12.29\node_modules\esbuild\lib\main.js:578:7)
at Socket.emit (node:events:526:28)
at addChunk (node:internal/streams/readable:315:12)

And if I tried to start the language server, I get:
C:\Users\xxx\Downloads\workspace\grammarly\packages\grammarly-languageserver\dist\index.cjs.js:6
const fetch = require('node-fetch');
^

Error [ERR_REQUIRE_ESM]: require() of ES Module<EMAIL_ADDRESS>from C:\Users\xxx\Downloads\workspace\_backup\grammarly\packages\grammarly-languageserver\dist\index.cjs.js not supported.
Instead change the require of index.js in C:\Users\xxx\Downloads\workspace\grammarly\packages\grammarly-languageserver\dist\index.cjs.js to a dynamic import() which is available in all CommonJS modules.
at Object.<anonymous> (C:\Users\xxx\Downloads\workspace\grammarly\packages\grammarly-languageserver\dist\index.cjs.js:6:15)
at Object.<anonymous> (C:\Users\xxx\Downloads\workspace\grammarly\packages\grammarly-languageserver\bin\server.js:3:16) {
code: ←[32m'ERR_REQUIRE_ESM'←[39m

Any idea are appreciated!

In rollup.config.js, I am using unix paths.

Thanks! ❤ The first issue is resolved after merging upstream.
But still could not get rid of the second error while starting the language server! 😖

The next error is:
node:internal/process/promises:279
triggerUncaughtException(err, true /* fromPromise */);
^

Error [ERR_REQUIRE_ESM]: require() of ES Module<EMAIL_ADDRESS>from C:\Users\xxx\Downloads\workspace\grammarly-language-server\packages\grammarly-languageserver\dist\index.cjs.js not supported.
Instead change the require of index.js in C:\Users\xxx\Downloads\workspace\grammarly-language-server\packages\grammarly-languageserver\dist\index.cjs.js to a dynamic import() which is available in all CommonJS modules.
at C:\Users\xxx\Downloads\workspace\grammarly-language-server\packages\grammarly-languageserver\dist\index.cjs.js:37:145
at async C:\Users\xxx\Downloads\workspace\grammarly-language-server\packages\grammarly-languageserver\dist\index.cjs.js:37:64 {
code: 'ERR_REQUIRE_ESM'
}

Let me know if I should stop informing you the new error! I am not trying burden you on this error! 😖 But I think it would be nice to have someone to help you with the test? 😅

Continue reporting 😅
I guess I need to separate web extension.

I think the error is caused by node-fetch v3. Any chance to use the previous node-fetch version ^2.6.1? 😖

Yes. It will be fixed by #240


Rendering changelog for 0.6.3 - [merged]

In GitLab by @wtbarnes on Nov 5, 2021, 08:10
Merges changelog-0.6.3 -> master

In GitLab by @wtbarnes on Nov 5, 2021, 08:17
resolved all threads

In GitLab by @wtbarnes on Nov 5, 2021, 08:11
enabled an automatic merge when the pipeline for 8f9239f97ecebc1cb5feca303eaeec698627d979 succeeds

0.6.3 (2021-11-05)
==================

I forgot to change the towncrier settings.

In GitLab by @wtbarnes on Nov 5, 2021, 08:17
Commented on CHANGELOG.rst line 2
changed this line in version 2 of the diff

In GitLab by @wtbarnes on Nov 5, 2021, 08:11
approved this merge request

In GitLab by @wtbarnes on Nov 5, 2021, 08:17
approved this merge request

In GitLab by @codecov on Nov 5, 2021, 08:21
Codecov Report

Merging #143 (1759c11) into master (82663db) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #143   +/-   ##
=======================================
  Coverage   95.87%   95.87%
=======================================
  Files          19       19
  Lines         606      606
=======================================
  Hits          581      581
  Misses         25       25

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 82663db...1759c11. Read the comment docs.

In GitLab by @wtbarnes on Nov 5, 2021, 08:17
added 1 commit
1759c11a - Apply 1 suggestion(s) to 1 file(s)
Compare with previous version

In GitLab by @wtbarnes on Nov 5, 2021, 08:17
enabled an automatic merge when the pipeline for 1759c11aab9fc828ed686c96314c5d5e3abb2d12 succeeds

In GitLab by @wtbarnes on Nov 5, 2021, 08:40
mentioned in commit 9b0896a4f9592565ee9f1281a8dfefd4b8dbdc7b

In GitLab by @wtbarnes on Nov 5, 2021, 08:40
picked the changes into the branch cherry-pick-40f5daf1 with commit 9b0896a4f9592565ee9f1281a8dfefd4b8dbdc7b

In GitLab by @wtbarnes on Nov 5, 2021, 08:38
mentioned in commit 40f5daf154a498d968acca61dbe18d584e1c9bc8


2022 Day 19 retrospective

There must be a better heuristics to keep the number of states limited: https://github.com/jp7677/adventofcode/blob/main/2022/src/test/kotlin/Day19.kt#L53

Solved (kind of) with https://github.com/jp7677/adventofcode/commit/5df36f0cf70948dd9df5a3f768f9955a1aebd0e9


Players cannot see when another player opens any wooden door, except standard oak

Players cannot see when another player opens any wooden door, except standard oak. The old standard door opens and closes for everyone to see. The acacia one and any other, doesn't make a sound or looks like it opens and closes.

i believe this can be closed

Tested. Works fine. :)


Avoid top-level with ...; in pkgs/development/lisp*

Description of changes
Using with at a top-level scope is an anti-pattern. The tracking issue is #208242. This is a pure refactor: there is no functional change contained in this PR.
I tried out the other strategy of replacing top-level with in this PR. If symbol foo was pulled implicitly from attrset pkgs, I replaced foo with pkgs.foo. Prior to this change, this file was a mix of both styles (foo and pkgs.foo), and now it's just one.
There are no rebuilds when I run nixpkgs-review rev HEAD, so I've targeted master with this PR.
Things done

[x] Tested compilation of all packages that depend on this change using nixpkgs-review rev HEAD.
[x] Fits CONTRIBUTING.md.

I get that. I mean, you're doing a refactor, and I appreciate you're doing it conservatively, but in this case we could as well make an opinionated choice - the original motivation was increasing clarity and readability. And again, I think judicious use of with can help with that.

I'm sorry, I find a with scope going over 90% of the lines of the file, mixed in with use of pkgs. within that scope to not be code I wish to produce. I can't apply that opinionated feedback in this PR, as it's not an opinion I share.
The only place I find with to make sense is where the scope is minimal: a list, a small set like meta, the like. If it scrolls off the screen while reading the file, or won't be present in the diff because it's far away, it's effectively a top-level with. To me, that's a judicious use.
You can see evidence of that confusion when code authors introduce smaller with scopes that were already covered by some larger one. with lib at the top scope, followed by with lib in the meta section. Use of pkgs. in a list when there's a top-level with pkgs;.
The other possible use of with pkgs; that I could have transformed in this PR is landing with pkgs; in front of every nativeBuildInputs or buildInputs. I chose not to do that since virtually every one of these lists contain just one member, and adding pkgs. is shorter.

Yeah, fair.

This PR is obviated by #309696.


Nodes and edges details

We need endpoints to retrieve details for network nodes, clusters and edges. All these values will be calculated on the aggregated winning bids of the parts involved filtered by the query of the network:

GET  /network/:id/nodes/:id

total income
average competition
percent of data missing
type
actors (the correspondiing actor id, an array if the node is cluster)
nodes (in case this is a cluster)
list of winning bids exchanged with the following attrs for each bid:

lot title
tender title
bid value
number of bids for the lot
award date
bidders (nodes)

id
label
nodes
actors

buyers (nodes

GET /network/:id:/clusters/:id

same as above

GET /network/:id/edges/:id

total money exhanged
average competition
percent of data missing
bids exchanged - with attrs as above

These have been developed in #77 but due to time constraint have not been tested so I renamed the issue to reflect that.


ckeditor_upload error

Reverse for 'ckeditor_upload' not found. 'ckeditor_upload' is not a valid view function or pattern name.
I had an error like this can anybody help me with this error

ckeditor_uploader in place of ckeditor_upload ?

Your urls.py file must be properly configured. login_required decorator #ghj#

please share your urls.py file. For example I customize my urls.py for login_required decorator.

I found the problem. I SHOULD INCLUDE URLS IN MAIN urls.py IN THE PROJECT NOT IN ANOTHER URLS EXISTS IN INCLUDED APPS

I found the same problem. and it is solved by using re_path in url.py
django==2.1.4
url.py
from django.urls import path, include, re_path
urlpatterns = [
    path('blog/', include(('blog.urls', 'blog'), namespace='blog')),
    re_path(r'^ckeditor/', include('ckeditor_uploader.urls')),
]

I found the same problem. and it is solved by using re_path in main urls.py
django==2.1.4
urls.py
from django.urls import path, include, re_path
urlpatterns = [
    path('admin/', admin.site.urls),
    path('blog/', include(('blog.urls', 'blog'), namespace='blog')),
    re_path(r'^ckeditor/', include('ckeditor_uploader.urls')),
]

Thank you @pranjal0819 it solved my problem.

Follow the same logic as @pranjal0819, the other solution is just include:
path('ckeditor/', include('ckeditor_uploader.urls')),
inside the urlpatters[], instead adding the re_path method.


[BUG] v<IP_ADDRESS> Windows cannot retrieve the telemetry from IoT Hub

Describe the bug
Azure IoT Explorer <IP_ADDRESS> Windows edition cannot retrieve the telemetry from IoT Hub.
To Reproduce
Steps to reproduce the behavior:

Go to 'Home > IoT Hub > Devices > DeviceId > Telemetry'
Click on 'Start'
It shows  'Receiving events ....', but no data is showing up and just hangs there.
It seems this issue doesn't exist on Windows edition <IP_ADDRESS>.

can you verify your routing settings in hub are correct by trying to watch telemetry from the CLI ? az iot hub monitor-events

Please check if the issue still happens in https://github.com/Azure/azure-iot-explorer/releases/tag/v0.14.8
We are not able repro the issue on our side.


Docs should be update about MutatingAdmissionWebhook and ValidatingAdmissionWebhook

This is a Bug Report
It's not a bug, just an outdated doc thing.
Problem:
The MutatingWebhookConfiguration and ValidatingWebhookConfiguration APIs have been promoted to admissionregistration.k8s.io/v1 in v1.16. But the docs still show that they are in beta state at admission-controllers/mutatingadmissionwebhook and admission-controllers/validatingadmissionwebhook.
Proposed Solution:

Remove the feature-state description from the two plug-ins.
Confirm the descriptions of the two plug-ins if they need an update too.

Page to Update:
https://kubernetes.io/docs/reference/access-authn-authz/admission-controllers

I'm investigating this issue, hope I can send a PR for this after someone triaged/confirmed it.
/assign

I'm investigating this issue, hope I can send a PR for this after someone triaged/confirmed it.
/assign

/triage accepted

/triage accepted


RuntimeWarning: Negative areas founds: 3   warnings.warn("Negative areas founds: %d" % neg_area_idx.size, RuntimeWarning))

I add a non-local block to the backbone and train the network following "e2e_mask_rcnn_R-50-RPN_1x.yaml".
However, I am not sure how to set the learning rate of the extra introduced non-local block. I just do not change the weight initializer and the learning rate setting related code.
Here I provide the change that I make,
First, I insert a non_local module within the function add_stage_w_non_local,

def add_stage_w_non_local(inplanes, outplanes, innerplanes, nblocks, dilation=1, stride_init=2, choice=1):
    """Make a stage consist of `nblocks` residual blocks.
    Returns:
        - stage module: an nn.Sequentail module of residual blocks
        - final output dimension
    """
    res_blocks = []
    stride = stride_init
    for _block_id in range(nblocks):
        res_blocks.append(add_residual_block(
            inplanes, outplanes, innerplanes, dilation, stride
        ))
        inplanes = outplanes
        stride = 1

    if _block_id == (nblocks-1):
        if choice == 1:
           context_block = BaseOC_Module(in_channels=outplanes, out_channels=outplanes, key_channels=outplanes//2,
                value_channels=outplanes//2, dropout=0, sizes=([1]))
        elif choice == 2:
            context_block = GN_BaseOC_Module(in_channels=outplanes, out_channels=outplanes, key_channels=outplanes//2,
                value_channels=outplanes//2, dropout=0, sizes=([1]))
        elif choice == 3:
            context_block = BaseOC_Context_Module(in_channels=outplanes, out_channels=outplanes, key_channels=outplanes//2,
                value_channels=outplanes//2, dropout=0, sizes=([1]))
        elif choice == 4:
            context_block = GN_BaseOC_Context_Module(in_channels=outplanes, out_channels=outplanes, key_channels=outplanes//2,
                value_channels=outplanes//2, dropout=0, sizes=([1]))

    return nn.Sequential(*res_blocks, context_block), outplanes

Then, I modify the backbone definition like below by replacing the add_stage with add_stage_w_non_local when we compute the self.res4.
class NL_ResNet_convX_body(nn.Module):
    def __init__(self, block_counts, choice=1):
        super().__init__()
        self.block_counts = block_counts
        self.convX = len(block_counts) + 1
        self.num_layers = (sum(block_counts) + 3 * (self.convX == 4)) * 3 + 2

        self.res1 = globals()[cfg.RESNETS.STEM_FUNC]()
        dim_in = 64
        dim_bottleneck = cfg.RESNETS.NUM_GROUPS * cfg.RESNETS.WIDTH_PER_GROUP
        self.res2, dim_in = add_stage(dim_in, 256, dim_bottleneck, block_counts[0],
                                      dilation=1, stride_init=1)
        self.res3, dim_in = add_stage(dim_in, 512, dim_bottleneck * 2, block_counts[1],
                                      dilation=1, stride_init=2)
        self.res4, dim_in = add_stage_w_non_local(dim_in, 1024, dim_bottleneck * 4, block_counts[2],
                                      dilation=1, stride_init=2, choice=choice)
        if len(block_counts) == 4:
            stride_init = 2 if cfg.RESNETS.RES5_DILATION == 1 else 1
            self.res5, dim_in = add_stage(dim_in, 2048, dim_bottleneck * 8, block_counts[3],
                                          cfg.RESNETS.RES5_DILATION, stride_init)
            self.spatial_scale = 1 / 32 * cfg.RESNETS.RES5_DILATION
        else:
            self.spatial_scale = 1 / 16  # final feature scale wrt. original image scale

        self.dim_out = dim_in

        self._init_modules()

Expected results
[][e2e_nl_mask_rcnn_R-50-FPN_1x.yaml][Step 37061 / 90000]
		loss: 0.046611, lr: 0.020000 time: 2.231452, eta: 1 day, 8:48:53
		accuracy_cls: 0.996273
		loss_cls: 0.009185, loss_bbox: 0.005711, loss_mask: 0.029372
		loss_rpn_cls: 0.000334, loss_rpn_bbox: 0.000816
		loss_rpn_cls_fpn2: 0.000087, loss_rpn_cls_fpn3: 0.000020, loss_rpn_cls_fpn4: 0.000014, loss_rpn_cls_fpn5: 0.000018, loss_rpn_cls_fpn6: 0.000026
		loss_rpn_bbox_fpn2: 0.000322, loss_rpn_bbox_fpn3: 0.000078, loss_rpn_bbox_fpn4: 0.000065, loss_rpn_bbox_fpn5: 0.000059, loss_rpn_bbox_fpn6: 0.000192
/teamscratch/msravcshare/yuyua/code/segmentation/PANet/lib/utils/boxes.py:66: RuntimeWarning: Negative areas founds: 3
  warnings.warn("Negative areas founds: %d" % neg_area_idx.size, RuntimeWarning)
/teamscratch/msravcshare/yuyua/code/segmentation/PANet/lib/modeling/generate_proposals.py:181: RuntimeWarning: invalid value encountered in greater_equal
  (x_ctr < im_info[1]) & (y_ctr < im_info[0]))[0]
/teamscratch/msravcshare/yuyua/code/segmentation/PANet/lib/modeling/generate_proposals.py:181: RuntimeWarning: invalid value encountered in less
  (x_ctr < im_info[1]) & (y_ctr < im_info[0]))[0]
[][e2e_nl_mask_rcnn_R-50-FPN_1x.yaml][Step 37081 / 90000]
		loss: nan, lr: 0.020000 time: 2.231213, eta: 1 day, 8:47:55
		accuracy_cls: 0.941802
		loss_cls: nan, loss_bbox: nan, loss_mask: nan
		loss_rpn_cls: nan, loss_rpn_bbox: nan
		loss_rpn_cls_fpn2: nan, loss_rpn_cls_fpn3: nan, loss_rpn_cls_fpn4: nan, loss_rpn_cls_fpn5: nan, loss_rpn_cls_fpn6: nan
		loss_rpn_bbox_fpn2: nan, loss_rpn_bbox_fpn3: nan, loss_rpn_bbox_fpn4: nan, loss_rpn_bbox_fpn5: nan, loss_rpn_bbox_fpn6: nan
/root/miniconda3/lib/python3.6/site-packages/numpy/lib/function_base.py:4033: RuntimeWarning: Invalid value encountered in median
  r = func(a, **kwargs)
[][e2e_nl_mask_rcnn_R-50-FPN_1x.yaml][Step 37101 / 90000]
		loss: nan, lr: 0.020000 time: 2.230715, eta: 1 day, 8:46:44
		accuracy_cls: 0.000000
		loss_cls: nan, loss_bbox: nan, loss_mask: nan
		loss_rpn_cls: nan, loss_rpn_bbox: nan
		loss_rpn_cls_fpn2: nan, loss_rpn_cls_fpn3: nan, loss_rpn_cls_fpn4: nan, loss_rpn_cls_fpn5: nan, loss_rpn_cls_fpn6: nan
		loss_rpn_bbox_fpn2: nan, loss_rpn_bbox_fpn3: nan, loss_rpn_bbox_fpn4: nan, loss_rpn_bbox_fpn5: nan, loss_rpn_bbox_fpn6: nan

System information

Operating system: Ubuntu16.04
CUDA version: 8.0
cuDNN version: 7.0
python version: 3.6
pytorch version: 0.4.1

I am trying the solution by Ross. Solution

@PkuRainBow
hello, have you fixed the problem?
btw, which context model are you using?
Thank you.

@Redaimao I have solved this problem. I use the Res50-FPN as the backbone.

@PkuRainBow
Would you mind give details on how to implement it?
and also please share some details on context module.
Thanks a lot!

@PkuRainBow
hello, do you have implemented the performance of maskrnn with non local. (increase about 1 point )


Syntax / Nested fields in Dev

Hey Kazupon
I have this use case
v-model="client.description"
v-validate:client.description.required

Does validator 2.0 support nested properties?
Is their no way to change v2 to automatically get the binding from v-model, so that we could just write
v-model="client.description"
v-validate:required

Also for this:
    ID: <input type="text" v-validate:id.minlength.maxlength="{ minlength: 3, maxlength: 16 }">

Couldn't we get:
    ID: <input type="text" v-validate:id.minlength(3).maxlength(16)>

You can do something like:
<validator name="clientValidator">
  <input v-model="client.description" v-validate:description.required />
</validator>

And then in your Vue instance, this.$clientValidator.description will contain the value of the input field and all the relevant validation data for the field.

Sorry for the late reply.
In v2.0, I decided that don't support the nested property, because application design become complex. Vue is the component oriented. I think that you can implement like the comment of @bradstewart, also use the component.

Ah ok, makes sense, thanks guys =)


Replace "Windows Communication Foundation (WCF)" token with plain text, part 4

For #4801
Replaces tokens in the docs/framework/wcf/feature-details directory

I will make the remaining changes in another PR. The remaining instances are scattered across a number of directories, so it would be easier to merge these four existing PRs first and then I'll create another PR with the remaining changes and delete the file. That also means that we will not have any merge conflicts.

That sounds like a good way to proceed, @Mackiovello. Thanks.

Thanks, @Mackiovello, for these 4 PRs. I've merged the first three, and will merge this one now.


Update Package.swift

Fixed #2

This package no longer builds because of this PR. SwiftSoup requires iOS 16 now.


Update Defaults for Nightly and Release

Update Defaults for Nightly and Release
PublishToMaestro and Signing should be on by default

/azp run TransportPackage-Foundation-PR


VS2013 version

Could we have a VS2013 version, please?

I'm sorry, but we're not planning to add support for VS 2013 for these samples.  You can download and install Visual Studio 2015 Community edition for free.
https://www.visualstudio.com/products/visual-studio-community-vs

Pity. Thanks for the reply.


Add trigger block to app.conf to stop restart on splunk indexers.

Is your feature request related to a problem? Please describe.
When Eventgen is installed on indexers, splunk sees an eventgen.conf file that it's unaware of and triggers a restart.
Describe the solution you'd like
Add a [triggers] block to app.conf to make sure there is no restart caused by the conf file existance.

fixed in #421


Tell us how we can improve CAMP!

It's never great hear that customers didn't like our product & we understand your perspective matters a lot! Please share your feedback on how we can improve your CAMP experience.
Tell us about:

Why do you use CAMP?
What do you not like about CAMP?
What do you want to see more of?
What role (admin, leadership, engineer, etc) do you belong to & which other stakeholders in your or use CAMP?
Any other feedback that you want us to work on.

Interested in discussing more?
Leave your email address and we will reach out to you or drop us an email at<EMAIL_ADDRESS>

Does CAMP Report still work? Myself and a colleague are having issues generating report. Yet, we have been using the same command used prior to this and before never had any issues...


Improved test coverage

This PR improves test coverage by:

Chopping out unused Bb version checks
Covering the cases for Backbone.Deferred and Backbone.$.Deferred
Checking a number of old bug reports

Close #201
Close #187

Coverage increased (+6.6%) to 89.683% when pulling 13a9e7bafeff654c2843d93bbc482695be4f1c78 on scott-w:master into 9edd1e74723baa4decc100ac9e5e347a6f0733ba on jeromegn:master.


[Refactor] Some code refactoring

What type of PR is this:

[ ] BugFix
[ ] Feature
[ ] Enhancement
[x] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[ ] 3.0
[ ] 2.5
[ ] 2.4
[ ] 2.3

[FE PR Coverage Check]
:disappointed: fail : 5 / 78 (06.41%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/lake/compaction/CompactionJob.java
0
10
00.00%
[36, 39, 47, 51, 67, 71, 75, 87, 95, 96]

:large_blue_circle:
com/starrocks/lake/compaction/CompactionTask.java
0
13
00.00%
[38, 39, 40, 41, 42, 45, 49, 53, 57, 58, 60, 63, 67]

:large_blue_circle:
com/starrocks/lake/backup/LakeBackupJob.java
0
16
00.00%
[137, 139, 140, 141, 142, 160, 162, 163, 164, 165, 166, 196, 198, 199, 200, 201]

:large_blue_circle:
com/starrocks/lake/backup/LakeRestoreJob.java
0
5
00.00%
[209, 211, 212, 213, 214]

:large_blue_circle:
com/starrocks/rpc/BrpcProxy.java
0
5
00.00%
[89, 90, 91, 92, 94]

:large_blue_circle:
com/starrocks/lake/compaction/CompactionScheduler.java
1
21
04.76%
[143, 157, 186, 285, 286, 288, 289, 290, 291, 292, 298, 309, 311, 312, 313, 316, 323, 324, 326, 376]

:large_blue_circle:
com/starrocks/lake/Utils.java
4
8
50.00%
[172, 173, 174, 175]

@Mergifyio rebase main

[FE PR Coverage Check]
:disappointed: fail : 5 / 78 (06.41%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/lake/compaction/CompactionJob.java
0
10
00.00%
[36, 39, 47, 51, 67, 71, 75, 87, 95, 96]

:large_blue_circle:
com/starrocks/lake/compaction/CompactionTask.java
0
13
00.00%
[38, 39, 40, 41, 42, 45, 49, 53, 57, 58, 60, 63, 67]

:large_blue_circle:
com/starrocks/lake/backup/LakeBackupJob.java
0
16
00.00%
[137, 139, 140, 141, 142, 160, 162, 163, 164, 165, 166, 196, 198, 199, 200, 201]

:large_blue_circle:
com/starrocks/lake/backup/LakeRestoreJob.java
0
5
00.00%
[209, 211, 212, 213, 214]

:large_blue_circle:
com/starrocks/rpc/BrpcProxy.java
0
5
00.00%
[89, 90, 91, 92, 94]

:large_blue_circle:
com/starrocks/lake/compaction/CompactionScheduler.java
1
21
04.76%
[143, 157, 186, 285, 286, 288, 289, 290, 291, 292, 298, 309, 311, 312, 313, 316, 323, 324, 326, 376]

:large_blue_circle:
com/starrocks/lake/Utils.java
4
8
50.00%
[172, 173, 174, 175]

[FE PR Coverage Check]
:disappointed: fail : 5 / 80 (06.25%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/lake/compaction/CompactionJob.java
0
10
00.00%
[36, 39, 47, 51, 67, 71, 75, 87, 95, 96]

:large_blue_circle:
com/starrocks/lake/compaction/CompactionTask.java
0
13
00.00%
[38, 39, 40, 41, 42, 45, 49, 53, 57, 58, 60, 63, 67]

:large_blue_circle:
com/starrocks/lake/backup/LakeBackupJob.java
0
16
00.00%
[137, 139, 140, 141, 142, 160, 162, 163, 164, 165, 166, 196, 198, 199, 200, 201]

:large_blue_circle:
com/starrocks/lake/backup/LakeRestoreJob.java
0
5
00.00%
[209, 211, 212, 213, 214]

:large_blue_circle:
com/starrocks/rpc/BrpcProxy.java
0
3
00.00%
[89, 90, 91]

:large_blue_circle:
com/starrocks/rpc/RpcException.java
0
4
00.00%
[28, 29, 32, 33]

:large_blue_circle:
com/starrocks/lake/compaction/CompactionScheduler.java
1
21
04.76%
[143, 157, 186, 285, 286, 288, 289, 290, 291, 292, 298, 309, 311, 312, 313, 316, 323, 324, 326, 376]

:large_blue_circle:
com/starrocks/lake/Utils.java
4
8
50.00%
[172, 173, 174, 175]

[FE PR Coverage Check]
:disappointed: fail : 5 / 80 (06.25%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/lake/compaction/CompactionJob.java
0
10
00.00%
[36, 39, 47, 51, 67, 71, 75, 87, 95, 96]

:large_blue_circle:
com/starrocks/lake/compaction/CompactionTask.java
0
13
00.00%
[38, 39, 40, 41, 42, 45, 49, 53, 57, 58, 60, 63, 67]

:large_blue_circle:
com/starrocks/lake/backup/LakeBackupJob.java
0
16
00.00%
[137, 139, 140, 141, 142, 160, 162, 163, 164, 165, 166, 196, 198, 199, 200, 201]

:large_blue_circle:
com/starrocks/lake/backup/LakeRestoreJob.java
0
5
00.00%
[209, 211, 212, 213, 214]

:large_blue_circle:
com/starrocks/rpc/BrpcProxy.java
0
3
00.00%
[89, 90, 91]

:large_blue_circle:
com/starrocks/rpc/RpcException.java
0
4
00.00%
[28, 29, 32, 33]

:large_blue_circle:
com/starrocks/lake/compaction/CompactionScheduler.java
1
21
04.76%
[143, 157, 186, 285, 286, 288, 289, 290, 291, 292, 298, 309, 311, 312, 313, 316, 323, 324, 326, 376]

:large_blue_circle:
com/starrocks/lake/Utils.java
4
8
50.00%
[172, 173, 174, 175]

@Mergifyio backport branch-3.0


Building iOS: Undefined symbols for architecture arm64

Plugin Version or Commit ID
v0.10.1
Unity Version
2021.3.7f1
Your Host OS
macOS 12.4 (Monterey)
Target Platform
iOS
[Windows Only] Visual Studio C++ and Windows SDK Version
No response
[Linux Only] GCC/G++ and GLIBC Version
No response
[Android Only] Android Build Tools and NDK Version
No response
[iOS Only] XCode Version
Xcode 13.4.x
Command Sequences
build for iOS
Log
ld: warning: object file (/Users/[REDACTED]/git/xcodebuild/Libraries/lib_burst_generated.a(lib_burst_generated_part_0_globals.o)) was built for newer iOS version (15.5) than being linked (12.0)
Undefined symbols for architecture arm64:
"_glReadPixels", referenced from:
_Gl_ReadPixels_mE20D483BE5ADD7B85929FC4602F7EF734C31705D in Mediapipe.Runtime.o
_UnsafeNativeMethods_glReadPixels_mBDD92D903AFA6B21E4187F39DCED58FB56E4BB4E in Mediapipe.Runtime.o
(maybe you meant: _UnsafeNativeMethods_glReadPixels_mBDD92D903AFA6B21E4187F39DCED58FB56E4BB4E)
"_glFlush", referenced from:
_Gl_Flush_mA9D5ECA06470361D7940768395B3475EBE22FF6E in Mediapipe.Runtime.o
_UnsafeNativeMethods_glFlush_m5E5824AC4B242F7F029A8D0B1CE4A08E910BDFD7 in Mediapipe.Runtime.o
(maybe you meant: _UnsafeNativeMethods_glFlush_m5E5824AC4B242F7F029A8D0B1CE4A08E910BDFD7)
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
Additional Context
Hi,
When building for iOS I get errors (Undefined symbols for architecture arm64) (please take a look in log).
Please help :)

Solution: Needed to modify in Unity Editor inspector Framework Dependencies for MediaPipeUnity.framework and set OpenGLES to true with checkbox.


T265 frame_id-s for odometry message and TF

Hi.
I'm trying to fuse T265 odometry with other localization data using robot_localization.
For this I need odometry message with correct frame_id-s specified (e.g. header.frame_id = "map" and child_frame_id="camera_link").
But current version publishes TF with the same frame_id-s - cluttering with robot_localization output.
So, to avoid this T265's TF camera_link need to have an option to be detached from camera_pose_frame. And odometry message to have child_frame_id different from TF's counterpart.
Thanks.

As a more general question.
I don't want to feed T265 with wheel odometry to improve VSLAM.
I want to feed T265 odometry to robot_localization to fuse with all other odometry sensors - wheel, GPS, other IMU-s following REP105.
Do you see any benefits in doing it your way (feeding wheel odometry to T265)?

Hi.
I'm trying to fuse T265 odometry with other localization data using robot_localization.
For this I need odometry message with correct frame_id-s specified (e.g. header.frame_id = "map" and child_frame_id="camera_link").
But current version publishes TF with the same frame_id-s - cluttering with robot_localization output.
So, to avoid this T265's TF camera_link need to have an option to be detached from camera_pose_frame. And odometry message to have child_frame_id different from TF's counterpart.
Thanks.

Not sure I understand. You can change the frame id's with launch params odom_frame_id and pose_frame_id. Does that help?

As a more general question.
I don't want to feed T265 with wheel odometry to improve VSLAM.
I want to feed T265 odometry to robot_localization to fuse with all other odometry sensors - wheel, GPS, other IMU-s following REP105.
Do you see any benefits in doing it your way (feeding wheel odometry to T265)?

The obvious benefit is saving on your machine's CPU. Other that that, it's a matter of which algorithm works best for you.
There is a disclaimer that without the additional information of the wheel odometry the device cannot be reliable over time. Since this device is meant to give reasonable performance as a stand alone and without additional computation power from the host, it offers the option to give it the additional information.

Of course, saving host's resources is obvious. Another benefit is that T265's relocalization should work better with better odometry.
But there are disadvantages too. Like, in order to fuse with GPS or other odometry sources (e.g., 2nd IMU), or to follow REP-105 (which is usually the case for outdoor robots at least), I need to use smth like robot_localization anyway.

Hi.
I'm trying to fuse T265 odometry with other localization data using robot_localization.
For this I need odometry message with correct frame_id-s specified (e.g. header.frame_id = "map" and child_frame_id="camera_link").
But current version publishes TF with the same frame_id-s - cluttering with robot_localization output.
So, to avoid this T265's TF camera_link need to have an option to be detached from camera_pose_frame. And odometry message to have child_frame_id different from TF's counterpart.
Thanks.

Not sure I understand. You can change the frame id's with launch params odom_frame_id and pose_frame_id. Does that help?

I mean that, in order to follow REP-105 and use robot_localization, one needs to have Realsense's TF part and odometry message published with different frame_id-s. Otherwise Realsense's TF clutters with that of robot_localization. Or there should be an option to turn off publishing of odom_frame_id -> pose_frame_id TF link. Or even better - to have both options, and an option to detach odom_frame_id -> pose_frame_id TF link from the rest of T265's TF frames.

I've issued PR696
I did not yet try to combine the output of T265 into another localization node so I hope you can check this minimal correction and see if it enables your work.


Use gradle property supported Python version in .test-infra

Followup of #26049
context: https://github.com/apache/beam/pull/25970#discussion_r1159957270
Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

run seed job

run seed job

run seed job


Add support for directly lance datasets as input to lance.write_dataset

When writing a dataset previously loaded by lance.dataset, the process segfaults. The workaround is to convert a dataset to a table before writing it.
This sample python code triggers the segfault
import lance

import pandas as pd
import pyarrow as pa
import pyarrow.dataset

df = pd.DataFrame({"a": [5], "b": [10]})
uri = "/tmp/test.parquet"
tbl = pa.Table.from_pandas(df)
pa.dataset.write_dataset(tbl, uri, format='parquet')

parquet = pa.dataset.dataset(uri, format='parquet')
lance.write_dataset(parquet, "/tmp/test.lance")

dataset = lance.dataset("/tmp/test.lance")
assert isinstance(dataset, pa.dataset.Dataset)

lance.write_dataset(dataset, "/tmp/test.lance")

Currently, the pyo3 code for writing a dataset requires a block_on call using tokio runtime. If the input dataset is also a LanceDataset, then the reading also requires a block_on call. This causes tokio to not be happy.
Instead the solution should be that the pyo3 interface should be converted to async and the blocking happens in python to convert to Table or write a dataset

FYI the segfault from GC's repro actually has to do with this line:
https://github.com/lancedb/lance/blob/b974900b78a02a9b67580db637dba928a1c2f070/python/python/lance/dataset.py#L1015-L1016
Passing a LanceDataset to pa.dataset.Scanner.from_dataset() isn't safe.


Not Found create_gt_database.py

Hi there,
When I was trying to generate ann_file using the following command:
python -m tools.create_data nuscenes \ --root-path /path/to/nuscenes --out-dir ./data/nuscenes_mmdet3d-t-keyframes/ \ --extra-tag nuscenes --only_info
It returns as follows:
    from data_converter.create_gt_database import create_groundtruth_database
ModuleNotFoundError: No module named 'data_converter.create_gt_database'

I traced back the data_converter but I did not find the related definition about create_gt_database. Could you uploud any auxiliary files for reference?

We apologize for our negligence. we found that the pkl generated by this function is actually useless, so we did not provide this part of the code. We have modified the code and you can pull it again~

Code may not change


Issue with training

I have followed the instructions listed in the README and completed the training. However, I ran into a few issues during the training.

During training of RealBasicVSR Net, the model started giving NaN losses after iteration 220000. Attaching the training logs for the same - RealBasicVSR Net.log, RealBasicVSR.log.
I used the model iter_220000 as the initialization for RealBasicVSR GAN model. After model training was completed, the images generated during inference seem to be of very poor quality. I have included a few sample generated images from the VideoLQ dataset. The same is reproducible even on images from the Vid4 dataset.

No changes have been made to the source code. The code commit ID used is fa3d3284664b05341867f51149c12e10a002fc0f from Jan 17, 2022.
Could you please let me know how this can be resolved? Also please let me know if any more information is required from my side in order to debug this.

From the log it seems that you are using 1 GPU? I think the problem may result from the unstable gradient. In our experiments, we use 8 GPU with batch size = 1 for each GPU. The batch size could be too small if only one GPU is used.
Maybe you can try increase the batch size to 2 and reduce the length from 15 to 8 to see if it is better.

Hi @ckkelvinchan . You're right. I am using 1 GPU for my training.
Let me try out your suggestion and see if it helps. Thank you!

Hi @ckkelvinchan . You're right. I am using 1 GPU for my training.
Let me try out your suggestion and see if it helps. Thank you!

dose the larger batchsize helps?


Travis not installing master versions of both sunpycube and sunpy

IRISpy currently relies on the master branch development versions of both sunpy and sunpycube.  Therefore they both need to be installed via Travis in order to properly test IRISpy.  This is typicallu done in the irispy/travis.yml file by including git+https://github.com/sunpy/sunpy.git  the list of PIP_DEPENDENCIES.  However, this does not seem to work when two repos need to be installed in this way.  This needs to be resolved so that IRISpy can be automatically tested.
See PR #40

This may be caused by a packaging bug in cube...


typo

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

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

TTYL, MSBOT;

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

Thanks! #sign-off

@cherylmc Hi Cheryl Please work with the contributor to resolve the merge conflict so that a merge is possible. Thanks. #hold-off

Hi @4c74356b41  - it turns out the PM already made changes that corrected this. Thanks for noticing it and letting us know, though. I'm going to go ahead and close this PR. #please-close

#please-close


Scope validation

Validate scopes specifically for ONC context.

Looks good.  I added functionality to our modules so you can specify default values on variables, which is nice because we can set different default scopes on each of the launches.  The one downside to this right now is that you used to be able to check what scopes were used last time when starting a new test, but now it just overwrites them.  We can see how annoying this is in the future and perhaps update it. But I think it is an improvement at least for now.
I also tweaked the tests slightly.


Noetic Playing Around Issues

Found a few things:

After added a new mode, there is a Add View button, but that button doesn't do anything
Running just insitu there are no topics to view... but I can still add views and filters (once it Seg faulted after doing so)

Pushed a fix, Add View button now properly opens the Add View Dialog. Views can no longer be created with an empty topic. I'll merge into noetic once the PR is tested and reviewed.


new access mode

closes #156
The PR change the way users can write mosaicJSON using the backends. The changes also add access mode to the backend object to better define read/write modes.
# Write Mosaic
### before
with FileBackend("my_path.json.gz", mosaic_def=mymosaic) as mosaic:
    mosaic.write()

### now
with FileBackend("my_path.json.gz", mode="w") as mosaic:
    mosaic.write(mymosaic)

For most of the backend, access mode are either:

r: read-only
r+: read-update
w: write

All backends must have the _available_modes variable set to indicate which mode are supported:
https://github.com/developmentseed/cogeo-mosaic/blob/7242abc8af39eb7eebb48db195a0cc7e029e8bc3/cogeo_mosaic/backends/web.py#L27
By default the backends are opened with r read-only mode.
mosaic_def is now outside the init method (breaking) and must be provided using the .write() method (if the backend is opened in w mode.
cc @kylebarron

# Write Mosaic
### before
with FileBackend("my_path.json.gz", mosaic_def=mymosaic) as mosaic:
    mosaic.write()

### now
with FileBackend("my_path.json.gz", mode="w") as mosaic:
    mosaic.write(mymosaic)

# Read Mosaic
### before
with FileBackend("my_path.json.gz") as mosaic:
     ...

### now
with FileBackend("my_path.json.gz", mode="r") as mosaic: # mode is optional because we default to 'r'
     ...

# Update Mosaic
### before
with FileBackend("my_path.json.gz") as mosaic:
     mosaic.update(anothermosaic)

### now
with FileBackend("my_path.json.gz", mode="r+") as mosaic:
         mosaic.update(anothermosaic)

not moving forward with this because it kinda complicate everything.
Why?
as pointed out by @kylebarron you cannot really do multiple .write() in a row, so the current flow/design is OK


Adding across DST results in a difference of an hour

// create a date outside of Daylight Savings Time
var m = moment(new Date(2011, 0, 1, 0, 0, 0));
m.format('h:mm a');
// 12:00 am

// change it to a date inside Daylight Savings Time
m.add('weeks', 20);
m.format('h:mm a');
// 1:00 am

If we cross the DST line by adding days, this also occurs
// the day before DST in the US
var m = moment(new Date(2011, 2, 12, 5, 0, 0));
m.format('h:mm a');
// 5:00 am

// DST day in the US
m.add('days', 1);
m.format('h:mm a');
// 6:00 am

If you go the other direction, you lose an hour.
var m = moment(new Date(2011, 2, 13, 5, 0, 0));
m.format('h:mm a');
// 5:00 am

m.subtract('days', 1);
m.format('h:mm a');
// 6:00 am

I am hesitant to call this a bug, but I feel that you should at least be aware of this behavior.  I think that this happens at the JavaScript level, and not by moment itself.
Perhaps moment could provide some helper functions like isDST or something like that to help for dealing with DST.

Here is a possible implementation of isDST.
  var dayOne = function(year) {
    return moment(new Date(year, 1, 0, 0, 0, 0));
  };

  moment.fn.isDST = function() {
    return dayOne(this.year())._d.getTimezoneOffset() !== this._d.getTimezoneOffset();
  };

I agree, adding a isDST function would be a good addition.
Regarding the adding and subtracting of days, I think i will need to update the following line to address this.
https://github.com/timrwood/moment/blob/c47d75d5fe9095f2b68f8d1f972dd501c155a719/moment.js#L46
I will do some investigation to see what the native js behavior is for adding time using setDate, setMonth, and setHours instead of just using setTime.

I think the behavior of this should be the following:
If adding days, weeks, months, or years, the hours should be the same as the original hours.
// the day before DST in the US
var m = moment(new Date(2011, 2, 12, 5, 0, 0));
m.format('h:mm a');
// 5:00 am

// DST day in the US
m.add('days', 1);
m.format('h:mm a');
// 5:00 am

If adding hours, minutes, seconds, or milliseconds, the assumption is that you want precision to the hour, and will result in a different hour.
// the day before DST in the US
var m = moment(new Date(2011, 2, 12, 5, 0, 0));
m.format('h:mm a');
// 5:00 am

// DST day in the US
m.add('hours', 24);
m.format('h:mm a');
// 6:00 am

I'll add this to the documentation as well.

This will go out in the 1.2.0 release.


Problem reproducing liveTV DASH streams with large timescale value

Hello,
our customer is an IPTV provider and wants to use Shaka player on smartTV devices: Samsung and LG.
However, they are using a very large timescale in the DASH manifest file (10000000), which we know that is generally not recommended for JavaScript players. Our customers is using these streams with these setting for years for other devices (set top box, mobile, etc.) with other players. For that reason they are very afraid of changing the streams (lowe the timescale) in order not to affect other devices/players.
Some of the TV channels work properly, however there are a number of other channels that present issues:

shaka player on any device reports "gaps", like this "Jumping forward 0.12310194969177246 seconds because of gap starting at<PHONE_NUMBER>.815654 and ending at<PHONE_NUMBER>.858355" We belive these are not real gaps in the stream source, but gaps which a product of calculations with overflow caused by high value of the timescale. This is not a very big problem though on most of the devices, since the player resumes reproduction immediately after reporting the gap and this negligible for the user experience
shaka player on smartTVs however freezes when these "gaps" happen. The most affected are Samsung/Tizen3 devices.

Is there any possibility to change in the player that the overflow does not happen?
If not, then is it possible to make some improvements in the player to avoid freezing on smartTVS?

The JavaScript language has no integer type.  All numbers are double-precision floats, which means integer precision within that is limited to 53 bits.  If the timescale is so large that the integers for DASH's $Time$ template exceeds 2^53, then rounding will occur at the JavaScript language level, and the wrong URLs can be generated.  This may also cause other issues we are unaware of.
Because of that, if a very large timescale causes an integer timestamp to overflow 2^53, the content is not supported by Shaka Player.  This is mentioned in the README (I know it can be hard to find anything there), and you can refer to #1667 for the original discovery and discussion of this.
Does this help?

Hello, I understand that nothing can be addressed here in Shaka projects, so if it is the case then yes please clos it.
Out customer refuses to reduce the timescale value, so we need to switch to a commercial player, that can find out a work around for freezing, stalling and looping.

In #1667, we said that we did not want to include a third-party BigInteger library, due to file-size concerns.
However, a BigInt type was added to the JavaScript language, in the ECMAScript 2020 specification. According to MDN, it is now supported on every browser besides IE. The Closure Compiler supports ES 2020 too, apparently; see here.
That support graph does not mention some of the environments we officially support, such as Tizen or ChromeCast, so we would need to do some testing to see if it's actually an option for us.
I think that, if we do find that all of our supported platforms implement BigInt, it might be reasonable to change the timescale to use BigInts instead of numbers.

According to MDN, Chrome added BigInt support in M67 (in 2018).  According to Tizen docs, Samsung only moved from Chrome M63 to M69 in their 2020 model year devices.  So if anything, we're lucky that Chrome introduced support so far ahead of the ratification of the spec, since Tizen is always ~2 years behind in Chrome releases.
If we adopt BigInt:

It will not be a high priority for the team.  It could be done much sooner if someone from the community did the work.
If BigInt became a hard requirement, that would not be backward compatible with earlier releases.  So BigInt would have to be optional to avoid a bump to Shaka v5.
A BigInt polyfill such as https://github.com/peterolson/BigInteger.js would be required for older platforms to play large timescales.  This one adds 5% to the size of Shaka Player.

For backward compatibility, I would suggest that:

If a device doesn't have native BigInt or a polyfill installed, we should fall back to Number and still be able to play content with reasonable timescales.
If a device doesn't have native BigInt or a polyfill installed, and the timescale is large (threshold TBD), we should refuse to play the content and throw a specific error code.  The docs for the error code should point people at a polyfill.

If we do it this way, it would not be considered breaking compatibility, and would not require a bump to Shaka v5.
I'll convert this into a low-priority feature request and mark it as seeking a PR.


inline zprint directives

Some lint/formatting tools accept inline directives / configuration that comes right before the code,
e.g.:
clj-kondo:
#_{:clj-kondo/ignore [:unresolved-symbol]}
(+ foo bar)

python yapf formatter:
x = [
"first",
1, 2
3, 4
]  # yapf: disable

The use case is, most of the time I'd like to format bindings as pairs but sometimes I'd like it to format as flow and insert blank lines between each binding, esp. when there are lambdas that spans several lines.
Could zprint support something like this:
; zprint: {flow?: true :nl-separator? true}
; or
#_{:zprint {:flow? true :nl-separator? true}}
(let [some-var
      some-value

      some-fn
      (fn []
           ....)]
  ... )

Using comments is slightly better than using clojure ignore (#_) reader macro because in a editor the former is colored as comments so less distracting.

Easily done!  There is a "file comment API" which does exactly what you want -- you can see the cljdoc here.   This interprets ;!zprint {...} as a zprint options map, with some special controls which indicate how much of the associated file is affected by the options map.
Probably I should add this to the "I want to change..." section of the docs.
Thanks for the suggestion!

Cool! Yeah this should be better linked in a obvious location.


Add Allocs example to README

People often complain that Julia doesn't have enough tools for tracking down allocations. This package, together with Profile.Allocs, actually seems pretty great for that to me though -- but you might not be able to figure out how from a casual glance at the README without watching the JuliaCon talk.
This PR adds a simple allocation profiling example that mirrors the top-line cpu profiling example just above it in the README.
This PR also updates the readme CI badge to point to the current github actions CI instead of the old Travis.

Codecov Report

Merging #76 (cab09e8) into master (82bebb5) will decrease coverage by 1.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #76      +/-   ##
==========================================
- Coverage   96.61%   95.59%   -1.02%
==========================================
  Files           3        3
  Lines         295      295
==========================================
- Hits          285      282       -3
- Misses         10       13       +3

Impacted Files
Coverage Δ

src/PProf.jl
96.80% <0.00%> (-2.41%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Plugin not useful in IDEA 2019.1

Only part that is functional is the mongo explorer.  View Collection Content not working.  No errors given.

FLS

:( just started working with mongo. This plugin looked like what I was looking for. All the other GUIs are lacking...

Idea 2019.2 same problem,
collections are listed but 'view collection content' doesn't works
Additional info about selected collection is display correctly

idea 2019.2  same problem ,  view collection content  don't work

using PyCharm 2019.2.1
successful connect to DB and view collection stats
failed viewing collection content. No error, no apparent response from IDE.

Hi,
the plugin has been fixed. please download this release and tell me whether it works on your IDE.
Thanks

It seems to be ok (see #269)


CODE RUB: Skip the execution of Post Type, Reaction Acceptance test

Can we skip the execution of Type Acceptance test as it is incomplete?
https://github.com/cjdutoit/Glory2Him.Api/blob/master/G2H.Api.Web.Tests.Acceptance/Apis/PostTypes/PostTypesApiTests.Logic.cs
https://github.com/cjdutoit/Glory2Him.Api/blob/master/G2H.Api.Web.Tests.Acceptance/Apis/Reactions/ReactionsApiTests.cs

@ShriHumrudha can you please add a bit more detail here so I can see if I understand you correctly.
These are lookups, so they will not have anything more than the GetAllPostTypes or GetPostTypeById, so I think they are complete in terms of functionality unless I am not understanding you.

@ShriHumrudha can you please add a bit more detail here so I can see if I understand you correctly.
These are lookups, so they will not have anything more than the GetAllPostTypes or GetPostTypeById, so I think they are complete in terms of functionality unless I am not understanding you.

Acceptance test are for end-to-end testing. To test your get calls, you need to post the record and then read it, then delete it after verification.

@ShriHumrudha,  OK, these will never have the POST/PUT/DELETE Controller actions as the these lookups is special.
The lookups is seeded based on the respective ENUM's (PostTypeId, ReactionId, StatusId) that are the primary keys, so each of them are restricted to the items defined in the enums.
The reason I created the lookups in this way is so I could have a strongly typed reference in code via the enum for state/status comparisons without the need to use magic strings.  It also gives me the option of having some extended properties like "Name" that I can access for reports with no dependency on a display name attribute on the enum.
In terms of setup, I have created / seeded the items by exposing the three lookup services from the DI in the ApiBroker.  Having access to these allowed me to seed the database in the event that any of the enums is not in the database.

I think it is still very useful to have these acceptance tests for the GET All and GET By Id as this shows that those two controller actions fully work, the DI registrations is complete for all the things implemented in them.
Would it be acceptable to keep these and just add the tear down / delete after verification in the same way as I do the setup as this is the only bit we are missing?   What do you think?